- 
- 
+
+
- Prowler is the Open Cloud Security Platform trusted by thousands to automate security and compliance in any cloud environment. With hundreds of ready-to-use checks and compliance frameworks, Prowler delivers real-time, customizable monitoring and seamless integrations, making cloud security simple, scalable, and cost-effective for organizations of any size. + Prowler is the Open Cloud Security Platform trusted by thousands to automate security and compliance in any cloud environment. With thousands of ready-to-use checks and compliance frameworks, Prowler delivers real-time, customizable monitoring and seamless integrations, making cloud security simple, scalable, and cost-effective for organizations of any size.
Secure ANY cloud at AI Speed at prowler.com
@@ -21,9 +21,9 @@
- 
-
+
+
+
- 
+
(Next.js)"] + api["Prowler API
(Django REST Framework)"] + worker["API Worker
(Celery)"] + beat["API Scheduler
(Celery Beat)"] + mcp["Prowler MCP Server
(Lighthouse AI tools)"] + end + + sdk["Prowler SDK
(Python)"] + + subgraph DATA["Data Layer"] + pg[("PostgreSQL")] + valkey[("Valkey / Redis")] + neo4j[("Neo4j")] + end + + providers["Providers"] + + user --> ui + user --> cli + ui -->|REST| api + ui -->|MCP HTTP| mcp + mcp -->|REST| api + api --> pg + api --> valkey + beat -->|enqueue jobs| valkey + valkey -->|dispatch| worker + worker --> pg + worker -->|Attack Paths| neo4j + worker -->|invokes| sdk + cli --> sdk + + sdk --> providers +``` + + ## Prowler CLI -**Running Prowler** +### Running Prowler Prowler can be executed across various environments, offering flexibility to meet your needs. It can be run from: diff --git a/action.yml b/action.yml index a93c67d4e8..2be0649402 100644 --- a/action.yml +++ b/action.yml @@ -22,7 +22,7 @@ inputs: required: false default: json-ocsf push-to-cloud: - description: Push scan findings to Prowler Cloud. Requires the PROWLER_CLOUD_API_KEY environment variable. See https://docs.prowler.com/user-guide/tutorials/prowler-app-import-findings#using-the-cli + description: Push scan findings to Prowler Cloud. Requires the PROWLER_CLOUD_API_KEY environment variable. See https://docs.prowler.com/user-guide/tutorials/prowler-import-findings#using-the-cli required: false default: "false" flags: @@ -299,7 +299,7 @@ runs: echo "" echo "**Get started in 3 steps:**" echo "1. Create an account at [cloud.prowler.com](https://cloud.prowler.com)" - echo "2. Generate a Prowler Cloud API key ([docs](https://docs.prowler.com/user-guide/tutorials/prowler-app-import-findings#using-the-cli))" + echo "2. Generate a Prowler Cloud API key ([docs](https://docs.prowler.com/user-guide/tutorials/prowler-import-findings#using-the-cli))" echo "3. Add \`PROWLER_CLOUD_API_KEY\` to your GitHub secrets and set \`push-to-cloud: true\` on this action" echo "" echo "See [prowler.com/pricing](https://prowler.com/pricing) for plan details." diff --git a/api/.env.example b/api/.env.example index 0be5388790..f97d868890 100644 --- a/api/.env.example +++ b/api/.env.example @@ -24,6 +24,9 @@ DJANGO_THROTTLE_TOKEN_OBTAIN=50/minute # Decide whether to allow Django manage database table partitions DJANGO_MANAGE_DB_PARTITIONS=[True|False] DJANGO_CELERY_DEADLOCK_ATTEMPTS=5 +# Optional: bound Celery's prefork pool size. Unset → Celery uses os.cpu_count(). +# Useful on Kubernetes nodes with many CPUs where unbounded prefork balloons memory. +# DJANGO_CELERY_WORKER_CONCURRENCY=4 DJANGO_BROKER_VISIBILITY_TIMEOUT=86400 DJANGO_SENTRY_DSN= diff --git a/api/AGENTS.md b/api/AGENTS.md index b03dc5803c..0483e55c04 100644 --- a/api/AGENTS.md +++ b/api/AGENTS.md @@ -10,7 +10,7 @@ > - [`jsonapi`](../skills/jsonapi/SKILL.md) - Strict JSON:API v1.1 spec compliance > - [`pytest`](../skills/pytest/SKILL.md) - Generic pytest patterns -### Auto-invoke Skills +## Auto-invoke Skills When performing these actions, ALWAYS invoke the corresponding skill FIRST: @@ -81,7 +81,7 @@ When performing these actions, ALWAYS invoke the corresponding skill FIRST: ## DECISION TREES ### Serializer Selection -``` +```text Read →
remote 404 body
" + response = httpx.Response( + 404, + request=httpx.Request("GET", "https://provider.example/v1/models"), + ) + + with patch("tasks.jobs.lighthouse_providers.openai.OpenAI") as mock_openai: + mock_client = MagicMock() + mock_client.models.list.side_effect = openai.NotFoundError( + remote_body, + response=response, + body=remote_body, + ) + mock_openai.return_value = mock_client + + eager_result = check_lighthouse_provider_connection_task.apply( + kwargs={ + "provider_config_id": str(provider_cfg.id), + "tenant_id": str(tenants_fixture[0].id), + } + ) + + assert eager_result.successful() + result = eager_result.result + assert result == {"connected": False, "error": "Provider connection failed"} + assert remote_body not in result["error"] + provider_cfg.refresh_from_db() + assert provider_cfg.is_active is False + + def test_openai_compatible_connection_masks_remote_auth_error( + self, tenants_fixture + ): + provider_cfg = LighthouseProviderConfiguration( + tenant_id=tenants_fixture[0].id, + provider_type=LighthouseProviderConfiguration.LLMProviderChoices.OPENAI_COMPATIBLE, + base_url="https://93.184.216.34/api/v1", + is_active=True, + ) + provider_cfg.credentials_decoded = {"api_key": "compatible-key"} + provider_cfg.save() + remote_body = {"error": {"message": "remote auth detail"}} + response = httpx.Response( + 401, + request=httpx.Request("GET", "https://provider.example/v1/models"), + ) + + with patch("tasks.jobs.lighthouse_providers.openai.OpenAI") as mock_openai: + mock_client = MagicMock() + mock_client.models.list.side_effect = openai.AuthenticationError( + "Unauthorized", + response=response, + body=remote_body, + ) + mock_openai.return_value = mock_client + + eager_result = check_lighthouse_provider_connection_task.apply( + kwargs={ + "provider_config_id": str(provider_cfg.id), + "tenant_id": str(tenants_fixture[0].id), + } + ) + + assert eager_result.successful() + result = eager_result.result + assert result == {"connected": False, "error": "API key is invalid or missing"} + assert "remote auth detail" not in result["error"] + provider_cfg.refresh_from_db() + assert provider_cfg.is_active is False + + def test_openai_compatible_network_backend_uses_validated_ip(self, monkeypatch): + backend = _LighthouseOpenAICompatibleNetworkBackend() + stream = MagicMock() + + def resolve_to_public_ip(host, port): + del host, port + return ("93.184.216.34",) + + monkeypatch.setattr( + "tasks.jobs.lighthouse_providers.resolve_lighthouse_openai_compatible_host", + resolve_to_public_ip, + ) + + with patch( + "tasks.jobs.lighthouse_providers.httpcore.SyncBackend.connect_tcp", + return_value=stream, + ) as mock_connect_tcp: + result = backend.connect_tcp("provider.example", 443, timeout=1.0) + + assert result is stream + assert mock_connect_tcp.call_args.args[:2] == ("93.184.216.34", 443) + assert mock_connect_tcp.call_args.kwargs["timeout"] == 1.0 + def test_check_connection_provider_does_not_exist(self, tenants_fixture): """Test that checking non-existent provider raises DoesNotExist.""" non_existent_id = str(uuid.uuid4()) @@ -1740,7 +1946,7 @@ class TestRefreshLighthouseProviderModelsTask: ( LighthouseProviderConfiguration.LLMProviderChoices.OPENAI_COMPATIBLE, {"api_key": "sk-test123"}, - "https://openrouter.ai/api/v1", + "https://93.184.216.34/api/v1", {"model-1": "Model One", "model-2": "Model Two"}, 2, ), @@ -1820,6 +2026,106 @@ class TestRefreshLighthouseProviderModelsTask: == expected_count ) + def test_refresh_models_rejects_metadata_base_url_without_request( + self, tenants_fixture + ): + provider_cfg = LighthouseProviderConfiguration( + tenant_id=tenants_fixture[0].id, + provider_type=LighthouseProviderConfiguration.LLMProviderChoices.OPENAI_COMPATIBLE, + base_url="https://169.254.169.254/latest/meta-data", + is_active=True, + ) + provider_cfg.credentials_decoded = {"api_key": "compatible-key"} + provider_cfg.save() + + with patch( + "tasks.jobs.lighthouse_providers._fetch_openai_compatible_models" + ) as mock_fetch: + eager_result = refresh_lighthouse_provider_models_task.apply( + kwargs={ + "provider_config_id": str(provider_cfg.id), + "tenant_id": str(tenants_fixture[0].id), + } + ) + + assert eager_result.successful() + result = eager_result.result + assert result["created"] == 0 + assert result["updated"] == 0 + assert result["deleted"] == 0 + assert "base url" in result["error"].lower() + mock_fetch.assert_not_called() + + def test_refresh_models_disables_redirects(self, tenants_fixture): + provider_cfg = LighthouseProviderConfiguration( + tenant_id=tenants_fixture[0].id, + provider_type=LighthouseProviderConfiguration.LLMProviderChoices.OPENAI_COMPATIBLE, + base_url="https://93.184.216.34/api/v1", + is_active=True, + ) + provider_cfg.credentials_decoded = {"api_key": "compatible-key"} + provider_cfg.save() + + with patch("tasks.jobs.lighthouse_providers.openai.OpenAI") as mock_openai: + mock_client = MagicMock() + mock_client.models.list.return_value = MagicMock(data=[]) + mock_openai.return_value = mock_client + + eager_result = refresh_lighthouse_provider_models_task.apply( + kwargs={ + "provider_config_id": str(provider_cfg.id), + "tenant_id": str(tenants_fixture[0].id), + } + ) + + assert eager_result.successful() + result = eager_result.result + assert result["created"] == 0 + assert result["updated"] == 0 + assert result["deleted"] == 0 + http_client = mock_openai.call_args.kwargs["http_client"] + assert http_client.follow_redirects is False + assert http_client.trust_env is False + + def test_refresh_models_masks_remote_http_error(self, tenants_fixture): + provider_cfg = LighthouseProviderConfiguration( + tenant_id=tenants_fixture[0].id, + provider_type=LighthouseProviderConfiguration.LLMProviderChoices.OPENAI_COMPATIBLE, + base_url="https://93.184.216.34/api/v1", + is_active=True, + ) + provider_cfg.credentials_decoded = {"api_key": "compatible-key"} + provider_cfg.save() + remote_body = "remote 404 body
" + response = httpx.Response( + 404, + request=httpx.Request("GET", "https://provider.example/v1/models"), + ) + + with patch("tasks.jobs.lighthouse_providers.openai.OpenAI") as mock_openai: + mock_client = MagicMock() + mock_client.models.list.side_effect = openai.NotFoundError( + remote_body, + response=response, + body=remote_body, + ) + mock_openai.return_value = mock_client + + eager_result = refresh_lighthouse_provider_models_task.apply( + kwargs={ + "provider_config_id": str(provider_cfg.id), + "tenant_id": str(tenants_fixture[0].id), + } + ) + + assert eager_result.successful() + result = eager_result.result + assert result["created"] == 0 + assert result["updated"] == 0 + assert result["deleted"] == 0 + assert result["error"] == "Provider connection failed" + assert remote_body not in result["error"] + def test_refresh_models_mixed_operations(self, tenants_fixture): """Test mixed create, update, and delete operations.""" # Create provider configuration @@ -1920,11 +2226,11 @@ class TestCleanupOrphanScheduledScans: ) def test_cleanup_deletes_orphan_when_both_available_and_scheduled_exist( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that AVAILABLE scan is deleted when SCHEDULED also exists.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Create orphan AVAILABLE scan @@ -1960,11 +2266,11 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=scheduled_scan.id).exists() def test_cleanup_does_not_delete_when_only_available_exists( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that AVAILABLE scan is NOT deleted when no SCHEDULED exists.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Create only AVAILABLE scan (normal first scan scenario) @@ -1989,11 +2295,11 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=available_scan.id).exists() def test_cleanup_does_not_delete_when_only_scheduled_exists( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that nothing is deleted when only SCHEDULED exists.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Create only SCHEDULED scan (normal subsequent scan scenario) @@ -2018,11 +2324,11 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=scheduled_scan.id).exists() def test_cleanup_returns_zero_when_no_scans_exist( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that cleanup returns 0 when no scans exist.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Execute cleanup with no scans @@ -2035,11 +2341,11 @@ class TestCleanupOrphanScheduledScans: assert deleted_count == 0 def test_cleanup_deletes_multiple_orphan_available_scans( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that multiple AVAILABLE orphan scans are all deleted.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Create multiple orphan AVAILABLE scans @@ -2084,12 +2390,11 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=scheduled_scan.id).exists() def test_cleanup_does_not_affect_different_provider( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider_pair ): """Test that cleanup only affects scans for the specified provider.""" tenant = tenants_fixture[0] - provider1 = providers_fixture[0] - provider2 = providers_fixture[1] + provider1, provider2 = aws_provider_pair periodic_task1 = self._create_periodic_task(provider1.id, tenant.id) periodic_task2 = self._create_periodic_task(provider2.id, tenant.id) @@ -2134,12 +2439,10 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=scheduled_scan_p1.id).exists() assert Scan.objects.filter(id=available_scan_p2.id).exists() - def test_cleanup_does_not_affect_manual_scans( - self, tenants_fixture, providers_fixture - ): + def test_cleanup_does_not_affect_manual_scans(self, tenants_fixture, aws_provider): """Test that cleanup only affects SCHEDULED trigger scans, not MANUAL.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) # Create orphan AVAILABLE scheduled scan @@ -2185,11 +2488,11 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=manual_scan.id).exists() def test_cleanup_does_not_affect_different_scheduler_task( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Test that cleanup only affects scans with the specified scheduler_task_id.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task1 = self._create_periodic_task(provider.id, tenant.id) # Create another periodic task @@ -2243,6 +2546,51 @@ class TestCleanupOrphanScheduledScans: assert Scan.objects.filter(id=scheduled_scan.id).exists() assert Scan.objects.filter(id=available_scan_other_task.id).exists() + def test_cleanup_keeps_db_queued_scheduled_scans( + self, tenants_fixture, aws_provider + ): + """DB-queued scheduled scans have a task and must not be deleted as orphans.""" + tenant = tenants_fixture[0] + provider = aws_provider + periodic_task = self._create_periodic_task(provider.id, tenant.id) + task_result = TaskResult.objects.create( + task_id=str(uuid.uuid4()), + task_name="scan-perform", + status="QUEUED", + ) + queued_task = Task.objects.create( + id=task_result.task_id, + task_runner_task=task_result, + tenant_id=tenant.id, + ) + queued_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Queued scheduled scan", + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.AVAILABLE, + scheduler_task_id=periodic_task.id, + task=queued_task, + ) + scheduled_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Daily scheduled scan", + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.SCHEDULED, + scheduler_task_id=periodic_task.id, + ) + + deleted_count = _cleanup_orphan_scheduled_scans( + tenant_id=str(tenant.id), + provider_id=str(provider.id), + scheduler_task_id=periodic_task.id, + ) + + assert deleted_count == 0 + assert Scan.objects.filter(id=queued_scan.id).exists() + assert Scan.objects.filter(id=scheduled_scan.id).exists() + @pytest.mark.django_db class TestPerformScheduledScanTask: @@ -2284,19 +2632,19 @@ class TestPerformScheduledScanTask: task_id=task_id, task_name="scan-perform-scheduled", status="STARTED", - date_created=datetime.now(timezone.utc), + date_created=datetime.now(UTC), ) Task.objects.create( id=task_id, task_runner_task=task_result, tenant_id=tenant_id ) return task_result - def test_skip_when_scheduled_scan_executing( - self, tenants_fixture, providers_fixture + def test_queues_scheduled_scan_when_scheduled_scan_is_executing( + self, tenants_fixture, aws_provider ): - """Skip a scheduled run when another scheduled scan is already executing.""" + """Queue a scheduled run when another scheduled scan is executing.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) task_id = str(uuid.uuid4()) self._create_task_result(tenant.id, task_id) @@ -2321,8 +2669,16 @@ class TestPerformScheduledScanTask: mock_scan.assert_not_called() mock_complete_tasks.assert_not_called() - assert result["id"] == str(executing_scan.id) - assert result["state"] == StateChoices.EXECUTING + assert result["id"] != str(executing_scan.id) + assert result["state"] == StateChoices.AVAILABLE + queued_scheduled_scan = Scan.objects.get( + tenant_id=tenant.id, + provider=provider, + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.AVAILABLE, + ) + assert result["id"] == str(queued_scheduled_scan.id) + assert queued_scheduled_scan.task.task_runner_task.status == "QUEUED" assert ( Scan.objects.filter( tenant_id=tenant.id, @@ -2330,15 +2686,141 @@ class TestPerformScheduledScanTask: trigger=Scan.TriggerChoices.SCHEDULED, state=StateChoices.SCHEDULED, ).count() - == 0 + == 1 + ) + + def test_queues_scheduled_scan_when_manual_scan_is_pending( + self, tenants_fixture, aws_provider + ): + """Queue one scheduled run when a manual scan is already dispatched.""" + tenant = tenants_fixture[0] + provider = aws_provider + self._create_periodic_task(provider.id, tenant.id) + task_id = str(uuid.uuid4()) + self._create_task_result(tenant.id, task_id) + manual_task_result = TaskResult.objects.create( + task_id=str(uuid.uuid4()), + task_name="scan-perform", + status=states.PENDING, + ) + manual_task = Task.objects.create( + id=manual_task_result.task_id, + task_runner_task=manual_task_result, + tenant_id=tenant.id, + ) + manual_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Manual scan", + trigger=Scan.TriggerChoices.MANUAL, + state=StateChoices.AVAILABLE, + task=manual_task, + ) + + with ( + patch("tasks.tasks.perform_prowler_scan") as mock_scan, + patch("tasks.tasks._perform_scan_complete_tasks") as mock_complete_tasks, + self._override_task_request(perform_scheduled_scan_task, id=task_id), + ): + result = perform_scheduled_scan_task.run( + tenant_id=str(tenant.id), provider_id=str(provider.id) + ) + + mock_scan.assert_not_called() + mock_complete_tasks.assert_not_called() + assert result["id"] != str(manual_scan.id) + assert result["state"] == StateChoices.AVAILABLE + queued_scheduled_scan = Scan.objects.get( + tenant_id=tenant.id, + provider=provider, + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.AVAILABLE, + ) + assert result["id"] == str(queued_scheduled_scan.id) + assert queued_scheduled_scan.task.task_runner_task.status == "QUEUED" + scheduled_scan = Scan.objects.get( + tenant_id=tenant.id, + provider=provider, + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.SCHEDULED, + ) + assert scheduled_scan.scheduled_at > datetime.now(UTC) + + def test_coalesces_scheduled_scan_when_one_is_already_queued( + self, tenants_fixture, aws_provider + ): + """Reuse the existing queued scheduled scan instead of adding another.""" + tenant = tenants_fixture[0] + provider = aws_provider + periodic_task = self._create_periodic_task(provider.id, tenant.id) + task_id = str(uuid.uuid4()) + self._create_task_result(tenant.id, task_id) + manual_task_result = TaskResult.objects.create( + task_id=str(uuid.uuid4()), + task_name="scan-perform", + status=states.PENDING, + ) + manual_task = Task.objects.create( + id=manual_task_result.task_id, + task_runner_task=manual_task_result, + tenant_id=tenant.id, + ) + Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Manual scan", + trigger=Scan.TriggerChoices.MANUAL, + state=StateChoices.AVAILABLE, + task=manual_task, + ) + queued_task_result = TaskResult.objects.create( + task_id=str(uuid.uuid4()), + task_name="scan-perform", + status="QUEUED", + ) + queued_task = Task.objects.create( + id=queued_task_result.task_id, + task_runner_task=queued_task_result, + tenant_id=tenant.id, + ) + queued_scheduled_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Daily scheduled scan", + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.AVAILABLE, + scheduler_task_id=periodic_task.id, + task=queued_task, + ) + + with ( + patch("tasks.tasks.perform_prowler_scan") as mock_scan, + patch("tasks.tasks._perform_scan_complete_tasks") as mock_complete_tasks, + self._override_task_request(perform_scheduled_scan_task, id=task_id), + ): + result = perform_scheduled_scan_task.run( + tenant_id=str(tenant.id), provider_id=str(provider.id) + ) + + mock_scan.assert_not_called() + mock_complete_tasks.assert_not_called() + assert result["id"] == str(queued_scheduled_scan.id) + assert ( + Scan.objects.filter( + tenant_id=tenant.id, + provider=provider, + trigger=Scan.TriggerChoices.SCHEDULED, + state=StateChoices.AVAILABLE, + ).count() + == 1 ) def test_creates_next_scheduled_scan_after_completion( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Create a next scheduled scan after a successful run completes.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider self._create_periodic_task(provider.id, tenant.id) task_id = str(uuid.uuid4()) self._create_task_result(tenant.id, task_id) @@ -2372,7 +2854,7 @@ class TestPerformScheduledScanTask: state=StateChoices.SCHEDULED, ) assert scheduled_scans.count() == 1 - assert scheduled_scans.first().scheduled_at > datetime.now(timezone.utc) + assert scheduled_scans.first().scheduled_at > datetime.now(UTC) assert ( Scan.objects.filter( tenant_id=tenant.id, @@ -2392,12 +2874,47 @@ class TestPerformScheduledScanTask: == 1 ) + def test_next_scheduled_scan_failure_does_not_mask_completed_scan( + self, tenants_fixture, aws_provider, caplog + ): + """Keep scheduled scan success when next-run creation fails.""" + tenant = tenants_fixture[0] + provider = aws_provider + self._create_periodic_task(provider.id, tenant.id) + task_id = str(uuid.uuid4()) + self._create_task_result(tenant.id, task_id) + + def _complete_scan(tenant_id, scan_id, provider_id): + scan_instance = Scan.objects.get(id=scan_id) + scan_instance.state = StateChoices.COMPLETED + scan_instance.save() + return {"status": "ok"} + + with ( + patch("tasks.tasks.perform_prowler_scan", side_effect=_complete_scan), + patch("tasks.tasks._perform_scan_complete_tasks"), + patch( + "tasks.tasks._get_or_create_next_scheduled_scan", + side_effect=RuntimeError("scheduler unavailable"), + ), + patch("tasks.tasks._dispatch_next_queued_provider_scan") as mock_dispatch, + self._override_task_request(perform_scheduled_scan_task, id=task_id), + caplog.at_level("ERROR"), + ): + result = perform_scheduled_scan_task.run( + tenant_id=str(tenant.id), provider_id=str(provider.id) + ) + + assert result == {"status": "ok"} + mock_dispatch.assert_called_once_with(str(tenant.id), str(provider.id)) + assert "Failed to ensure next scheduled scan" in caplog.text + def test_dedupes_multiple_scheduled_scans_before_run( - self, tenants_fixture, providers_fixture + self, tenants_fixture, aws_provider ): """Ensure duplicated scheduled scans are removed before executing.""" tenant = tenants_fixture[0] - provider = providers_fixture[0] + provider = aws_provider periodic_task = self._create_periodic_task(provider.id, tenant.id) task_id = str(uuid.uuid4()) self._create_task_result(tenant.id, task_id) @@ -2408,7 +2925,7 @@ class TestPerformScheduledScanTask: name="Daily scheduled scan", trigger=Scan.TriggerChoices.SCHEDULED, state=StateChoices.SCHEDULED, - scheduled_at=datetime.now(timezone.utc), + scheduled_at=datetime.now(UTC), scheduler_task_id=periodic_task.id, ) duplicate_scan = Scan.objects.create( @@ -2506,6 +3023,104 @@ class TestPerformScanTask: mock_scan.assert_not_called() mock_complete_tasks.assert_not_called() + def test_dispatches_next_queued_scan_after_completion( + self, + tenants_fixture, + aws_provider, + django_capture_on_commit_callbacks, + ): + """Dispatch the next queued scan for the provider after completion.""" + tenant = tenants_fixture[0] + provider = aws_provider + current_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Running scan", + trigger=Scan.TriggerChoices.MANUAL, + state=StateChoices.AVAILABLE, + ) + queued_task_result = TaskResult.objects.create( + task_id=str(uuid.uuid4()), + task_name="scan-perform", + status="QUEUED", + ) + queued_task = Task.objects.create( + id=queued_task_result.task_id, + task_runner_task=queued_task_result, + tenant_id=tenant.id, + ) + queued_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Queued scan", + trigger=Scan.TriggerChoices.MANUAL, + state=StateChoices.AVAILABLE, + task=queued_task, + ) + + def _complete_scan(tenant_id, scan_id, provider_id, checks_to_execute=None): + scan_instance = Scan.objects.get(id=scan_id) + scan_instance.state = StateChoices.COMPLETED + scan_instance.save() + return {"status": "ok"} + + with ( + patch("tasks.tasks.perform_prowler_scan", side_effect=_complete_scan), + patch("tasks.tasks._perform_scan_complete_tasks"), + patch("tasks.tasks.perform_scan_task.apply_async") as mock_apply_async, + ): + with django_capture_on_commit_callbacks(execute=True): + result = perform_scan_task.run( + tenant_id=str(tenant.id), + scan_id=str(current_scan.id), + provider_id=str(provider.id), + ) + + queued_task_result.refresh_from_db() + assert result == {"status": "ok"} + assert queued_task_result.status == states.PENDING + mock_apply_async.assert_called_once_with( + kwargs={ + "tenant_id": str(tenant.id), + "scan_id": str(queued_scan.id), + "provider_id": str(provider.id), + }, + task_id=str(queued_task.id), + ) + + def test_dispatch_failure_does_not_mask_completed_scan( + self, tenants_fixture, aws_provider, caplog + ): + """Keep scan success when queued dispatch fails after completion.""" + tenant = tenants_fixture[0] + provider = aws_provider + current_scan = Scan.objects.create( + tenant_id=tenant.id, + provider=provider, + name="Running scan", + trigger=Scan.TriggerChoices.MANUAL, + state=StateChoices.AVAILABLE, + ) + + with ( + patch("tasks.tasks.perform_prowler_scan", return_value={"status": "ok"}), + patch("tasks.tasks._perform_scan_complete_tasks"), + patch( + "tasks.tasks._dispatch_next_queued_provider_scan", + side_effect=RuntimeError("dispatch unavailable"), + ) as mock_dispatch, + caplog.at_level("ERROR"), + ): + result = perform_scan_task.run( + tenant_id=str(tenant.id), + scan_id=str(current_scan.id), + provider_id=str(provider.id), + ) + + assert result == {"status": "ok"} + mock_dispatch.assert_called_once_with(str(tenant.id), str(provider.id)) + assert "Failed to dispatch next queued scan" in caplog.text + @pytest.mark.django_db class TestReaggregateAllFindingGroupSummaries: @@ -2538,7 +3153,7 @@ class TestReaggregateAllFindingGroupSummaries: scan_id_today_p1 = uuid.uuid4() scan_id_yesterday_p1 = uuid.uuid4() scan_id_today_p2 = uuid.uuid4() - today = datetime.now(tz=timezone.utc) + today = datetime.now(tz=UTC) yesterday = today - timedelta(days=1) mock_outer_group_result = MagicMock() @@ -2619,7 +3234,7 @@ class TestReaggregateAllFindingGroupSummaries: provider_id = uuid.uuid4() latest_scan_today = uuid.uuid4() earlier_scan_today = uuid.uuid4() - today_late = datetime.now(tz=timezone.utc) + today_late = datetime.now(tz=UTC) today_early = today_late - timedelta(hours=4) mock_outer_group_result = MagicMock() @@ -2672,3 +3287,37 @@ class TestReaggregateAllFindingGroupSummaries: assert result == {"scans_reaggregated": 0} mock_group.assert_not_called() mock_chain.assert_not_called() + + +class TestTaskTimeLimits: + """The per-task limits in task_annotations must actually take effect. + + Celery applies a "*" annotation after the per-task one, so a "*" entry would + silently overwrite every specific limit and cap long scans at the default. The + default is set as the global limit instead, and these per-task limits must win. + """ + + def test_long_running_tasks_exceed_the_default_limit(self): + from config.celery import celery_app + + default = celery_app.conf.task_time_limit + for name in ( + "scan-perform", + "scan-perform-scheduled", + "attack-paths-scan-perform", + "provider-deletion", + "tenant-deletion", + ): + assert celery_app.tasks[name].time_limit > default + + def test_connection_checks_stay_below_the_default_limit(self): + from config.celery import celery_app + + default = celery_app.conf.task_time_limit + for name in ( + "provider-connection-check", + "integration-connection-check", + "lighthouse-connection-check", + "lighthouse-provider-connection-check", + ): + assert celery_app.tasks[name].time_limit < default diff --git a/api/src/backend/tasks/tests/test_utils.py b/api/src/backend/tasks/tests/test_utils.py index cc7b7f188b..e6b5544a1c 100644 --- a/api/src/backend/tasks/tests/test_utils.py +++ b/api/src/backend/tasks/tests/test_utils.py @@ -1,4 +1,4 @@ -from datetime import datetime, timedelta, timezone +from datetime import UTC, datetime, timedelta from unittest.mock import patch import pytest @@ -29,7 +29,7 @@ class TestGetNextExecutionDatetime: task_id="abc123", task_name="scan-perform-scheduled", status="SUCCESS", - date_created=datetime.now(timezone.utc) - timedelta(hours=1), + date_created=datetime.now(UTC) - timedelta(hours=1), result="Success", ) return task_result diff --git a/api/src/backend/tasks/utils.py b/api/src/backend/tasks/utils.py index eded5bfb9a..cac9a10f0d 100644 --- a/api/src/backend/tasks/utils.py +++ b/api/src/backend/tasks/utils.py @@ -1,12 +1,11 @@ import json -from datetime import datetime, timedelta, timezone +from datetime import UTC, datetime, timedelta from enum import Enum +from api.models import Scan, StateChoices from django_celery_beat.models import PeriodicTask from django_celery_results.models import TaskResult -from api.models import Scan, StateChoices - SCHEDULED_SCAN_NAME = "Daily scheduled scan" @@ -45,9 +44,9 @@ def get_next_execution_datetime(task_id: int, provider_id: str) -> datetime: interval = periodic_task_instance.interval current_scheduled_time = datetime.combine( - datetime.now(timezone.utc).date(), + datetime.now(UTC).date(), task_instance.date_created.time(), - tzinfo=timezone.utc, + tzinfo=UTC, ) return current_scheduled_time + timedelta(**{interval.period: interval.every}) @@ -104,6 +103,7 @@ def _get_or_create_scheduled_scan( trigger=Scan.TriggerChoices.SCHEDULED, state__in=(StateChoices.SCHEDULED, StateChoices.AVAILABLE), scheduler_task_id=scheduler_task_id, + task__isnull=True, ).order_by("scheduled_at", "inserted_at") ) diff --git a/api/tests/performance/scenarios/compliance.py b/api/tests/performance/scenarios/compliance.py index ae4e030a59..9692c3aac2 100644 --- a/api/tests/performance/scenarios/compliance.py +++ b/api/tests/performance/scenarios/compliance.py @@ -90,7 +90,7 @@ class APIUser(APIUserBase): def compliance_overviews_default(self): provider_type, scan_info = _get_random_scan() name = f"/compliance-overviews ({provider_type})" - endpoint = f"/compliance-overviews?" f"filter[scan_id]={scan_info['scan_id']}" + endpoint = f"/compliance-overviews?filter[scan_id]={scan_info['scan_id']}" self.client.get(endpoint, headers=get_auth_headers(self.token), name=name) @task(2) @@ -122,7 +122,6 @@ class APIUser(APIUserBase): compliance_id = _get_random_compliance_id(provider_type) name = f"/compliance-overviews/attributes ({compliance_id})" endpoint = ( - f"/compliance-overviews/attributes" - f"?filter[compliance_id]={compliance_id}" + f"/compliance-overviews/attributes?filter[compliance_id]={compliance_id}" ) self.client.get(endpoint, headers=get_auth_headers(self.token), name=name) diff --git a/api/tests/performance/scenarios/findings.py b/api/tests/performance/scenarios/findings.py index acd32f2497..7741d1df4c 100644 --- a/api/tests/performance/scenarios/findings.py +++ b/api/tests/performance/scenarios/findings.py @@ -80,7 +80,7 @@ class APIUser(APIUserBase): @task(3) def findings_metadata(self): - endpoint = f"/findings/metadata?" f"filter[inserted_at]={TARGET_INSERTED_AT}" + endpoint = f"/findings/metadata?filter[inserted_at]={TARGET_INSERTED_AT}" self.client.get( endpoint, headers=get_auth_headers(self.token), name="/findings/metadata" ) @@ -98,7 +98,7 @@ class APIUser(APIUserBase): @task def findings_metadata_scan_small(self): - endpoint = f"/findings/metadata?" f"&filter[scan]={self.s_scan_id}" + endpoint = f"/findings/metadata?&filter[scan]={self.s_scan_id}" self.client.get( endpoint, headers=get_auth_headers(self.token), @@ -118,7 +118,7 @@ class APIUser(APIUserBase): @task def findings_metadata_scan_medium(self): - endpoint = f"/findings/metadata?" f"&filter[scan]={self.m_scan_id}" + endpoint = f"/findings/metadata?&filter[scan]={self.m_scan_id}" self.client.get( endpoint, headers=get_auth_headers(self.token), @@ -150,7 +150,7 @@ class APIUser(APIUserBase): @task def findings_metadata_scan_large(self): - endpoint = f"/findings/metadata?" f"&filter[scan]={self.l_scan_id}" + endpoint = f"/findings/metadata?&filter[scan]={self.l_scan_id}" self.client.get( endpoint, headers=get_auth_headers(self.token), diff --git a/api/tests/performance/scenarios/resources.py b/api/tests/performance/scenarios/resources.py index dabf99c3f2..43e13fad92 100644 --- a/api/tests/performance/scenarios/resources.py +++ b/api/tests/performance/scenarios/resources.py @@ -97,7 +97,7 @@ class APIUser(APIUserBase): name = "/resources?filter[scan_id] - 50k" page_number = self._next_page(name) endpoint = ( - f"/resources?page[number]={page_number}" f"&filter[scan]={self.s_scan_id}" + f"/resources?page[number]={page_number}&filter[scan]={self.s_scan_id}" ) self.client.get(endpoint, headers=get_auth_headers(self.token), name=name) @@ -116,7 +116,7 @@ class APIUser(APIUserBase): name = "/resources?filter[scan_id] - 250k" page_number = self._next_page(name) endpoint = ( - f"/resources?page[number]={page_number}" f"&filter[scan]={self.m_scan_id}" + f"/resources?page[number]={page_number}&filter[scan]={self.m_scan_id}" ) self.client.get(endpoint, headers=get_auth_headers(self.token), name=name) @@ -135,7 +135,7 @@ class APIUser(APIUserBase): name = "/resources?filter[scan_id] - 500k" page_number = self._next_page(name) endpoint = ( - f"/resources?page[number]={page_number}" f"&filter[scan]={self.l_scan_id}" + f"/resources?page[number]={page_number}&filter[scan]={self.l_scan_id}" ) self.client.get(endpoint, headers=get_auth_headers(self.token), name=name) diff --git a/api/tests/performance/utils/helpers.py b/api/tests/performance/utils/helpers.py index 08144a5c4b..29ce2a47fc 100644 --- a/api/tests/performance/utils/helpers.py +++ b/api/tests/performance/utils/helpers.py @@ -153,9 +153,9 @@ def get_dynamic_filters_pairs( f"{host}/{endpoint}/metadata?{metadata_filters}", headers=get_auth_headers(token), ) - assert ( - response.status_code == 200 - ), f"Failed to get resource filters values: {response.text}" + assert response.status_code == 200, ( + f"Failed to get resource filters values: {response.text}" + ) attributes = response.json()["data"]["attributes"] return { diff --git a/api/towncrier.toml b/api/towncrier.toml new file mode 100644 index 0000000000..528e6129ec --- /dev/null +++ b/api/towncrier.toml @@ -0,0 +1,39 @@ +[tool.towncrier] +directory = "changelog.d" +filename = "CHANGELOG.md" +start_string = "\n" +title_format = "## [{version}] ({name})" +issue_format = "[(#{issue})](https://github.com/prowler-cloud/prowler/pull/{issue})" +template = "../.github/towncrier/template.md.jinja" +underlines = ["", "", ""] +ignore = [".gitkeep", "README.md"] + +[[tool.towncrier.type]] +directory = "added" +name = "🚀 Added" +showcontent = true + +[[tool.towncrier.type]] +directory = "changed" +name = "🔄 Changed" +showcontent = true + +[[tool.towncrier.type]] +directory = "deprecated" +name = "⚠️ Deprecated" +showcontent = true + +[[tool.towncrier.type]] +directory = "removed" +name = "❌ Removed" +showcontent = true + +[[tool.towncrier.type]] +directory = "fixed" +name = "🐞 Fixed" +showcontent = true + +[[tool.towncrier.type]] +directory = "security" +name = "🔐 Security" +showcontent = true diff --git a/api/uv.lock b/api/uv.lock index 03993172d9..de878d9dc9 100644 --- a/api/uv.lock +++ b/api/uv.lock @@ -16,7 +16,7 @@ constraints = [ { name = "aiobotocore", specifier = "==2.25.1" }, { name = "aiofiles", specifier = "==24.1.0" }, { name = "aiohappyeyeballs", specifier = "==2.6.1" }, - { name = "aiohttp", specifier = "==3.13.5" }, + { name = "aiohttp", specifier = "==3.14.0" }, { name = "aioitertools", specifier = "==0.13.0" }, { name = "aiosignal", specifier = "==1.4.0" }, { name = "alibabacloud-actiontrail20200706", specifier = "==2.4.1" }, @@ -61,9 +61,8 @@ constraints = [ { name = "astroid", specifier = "==3.2.4" }, { name = "async-timeout", specifier = "==5.0.1" }, { name = "attrs", specifier = "==25.4.0" }, - { name = "authlib", specifier = "==1.6.9" }, + { name = "authlib", specifier = "==1.6.12" }, { name = "autopep8", specifier = "==2.3.2" }, - { name = "awsipranges", specifier = "==0.3.3" }, { name = "azure-cli-core", specifier = "==2.83.0" }, { name = "azure-cli-telemetry", specifier = "==1.1.0" }, { name = "azure-common", specifier = "==1.1.28" }, @@ -111,7 +110,7 @@ constraints = [ { name = "blinker", specifier = "==1.9.0" }, { name = "boto3", specifier = "==1.40.61" }, { name = "botocore", specifier = "==1.40.61" }, - { name = "cartography", specifier = "==0.135.0" }, + { name = "cartography", specifier = "==0.138.1" }, { name = "celery", specifier = "==5.6.2" }, { name = "certifi", specifier = "==2026.1.4" }, { name = "cffi", specifier = "==2.0.0" }, @@ -136,7 +135,6 @@ constraints = [ { name = "debugpy", specifier = "==1.8.20" }, { name = "decorator", specifier = "==5.2.1" }, { name = "defusedxml", specifier = "==0.7.1" }, - { name = "detect-secrets", specifier = "==1.5.0" }, { name = "dill", specifier = "==0.4.1" }, { name = "distro", specifier = "==1.9.0" }, { name = "dj-rest-auth", specifier = "==7.0.1" }, @@ -146,6 +144,7 @@ constraints = [ { name = "django-celery-results", specifier = "==2.6.0" }, { name = "django-cors-headers", specifier = "==4.4.0" }, { name = "django-environ", specifier = "==0.11.2" }, + { name = "django-eventstream", specifier = "==5.3.3" }, { name = "django-filter", specifier = "==24.3" }, { name = "django-guid", specifier = "==3.5.0" }, { name = "django-postgres-extra", specifier = "==2.0.9" }, @@ -163,7 +162,7 @@ constraints = [ { name = "drf-simple-apikey", specifier = "==2.2.1" }, { name = "drf-spectacular", specifier = "==0.27.2" }, { name = "drf-spectacular-jsonapi", specifier = "==0.5.1" }, - { name = "dulwich", specifier = "==0.23.0" }, + { name = "dulwich", specifier = "==1.2.5" }, { name = "duo-client", specifier = "==5.5.0" }, { name = "durationpy", specifier = "==0.10" }, { name = "email-validator", specifier = "==2.2.0" }, @@ -190,7 +189,7 @@ constraints = [ { name = "grpc-google-iam-v1", specifier = "==0.14.3" }, { name = "grpcio", specifier = "==1.76.0" }, { name = "grpcio-status", specifier = "==1.76.0" }, - { name = "gunicorn", specifier = "==23.0.0" }, + { name = "gunicorn", specifier = "==26.0.0" }, { name = "h11", specifier = "==0.16.0" }, { name = "h2", specifier = "==4.3.0" }, { name = "hpack", specifier = "==4.1.0" }, @@ -199,8 +198,8 @@ constraints = [ { name = "httpx", specifier = "==0.28.1" }, { name = "humanfriendly", specifier = "==10.0" }, { name = "hyperframe", specifier = "==6.1.0" }, - { name = "iamdata", specifier = "==0.1.202602021" }, - { name = "idna", specifier = "==3.11" }, + { name = "iamdata", specifier = "==0.1.202605131" }, + { name = "idna", specifier = "==3.15" }, { name = "importlib-metadata", specifier = "==8.7.1" }, { name = "inflection", specifier = "==0.5.1" }, { name = "iniconfig", specifier = "==2.3.0" }, @@ -218,6 +217,7 @@ constraints = [ { name = "jsonschema", specifier = "==4.23.0" }, { name = "jsonschema-specifications", specifier = "==2025.9.1" }, { name = "keystoneauth1", specifier = "==5.13.0" }, + { name = "kingfisher-bin", specifier = "==1.104.0" }, { name = "kiwisolver", specifier = "==1.4.9" }, { name = "knack", specifier = "==0.11.0" }, { name = "kombu", specifier = "==5.6.2" }, @@ -252,7 +252,7 @@ constraints = [ { name = "neo4j", specifier = "==6.1.0" }, { name = "nest-asyncio", specifier = "==1.6.0" }, { name = "nltk", specifier = "==3.9.4" }, - { name = "numpy", specifier = "==2.0.2" }, + { name = "numpy", specifier = "==2.2.6" }, { name = "oauthlib", specifier = "==3.3.1" }, { name = "oci", specifier = "==2.169.0" }, { name = "openai", specifier = "==1.109.1" }, @@ -281,7 +281,7 @@ constraints = [ { name = "psutil", specifier = "==7.2.2" }, { name = "psycopg2-binary", specifier = "==2.9.9" }, { name = "py-deviceid", specifier = "==0.1.1" }, - { name = "py-iam-expand", specifier = "==0.1.0" }, + { name = "py-iam-expand", specifier = "==0.3.0" }, { name = "py-ocsf-models", specifier = "==0.8.1" }, { name = "pyasn1", specifier = "==0.6.3" }, { name = "pyasn1-modules", specifier = "==0.4.2" }, @@ -291,7 +291,7 @@ constraints = [ { name = "pydantic-core", specifier = "==2.41.5" }, { name = "pygithub", specifier = "==2.8.0" }, { name = "pygments", specifier = "==2.20.0" }, - { name = "pyjwt", specifier = "==2.12.1" }, + { name = "pyjwt", specifier = "==2.13.0" }, { name = "pylint", specifier = "==3.2.5" }, { name = "pymsalruntime", specifier = "==0.18.1" }, { name = "pynacl", specifier = "==1.6.2" }, @@ -327,7 +327,7 @@ constraints = [ { name = "rpds-py", specifier = "==0.30.0" }, { name = "rsa", specifier = "==4.9.1" }, { name = "ruamel-yaml", specifier = "==0.19.1" }, - { name = "ruff", specifier = "==0.5.0" }, + { name = "ruff", specifier = "==0.15.11" }, { name = "s3transfer", specifier = "==0.14.0" }, { name = "scaleway", specifier = "==2.10.3" }, { name = "scaleway-core", specifier = "==2.10.3" }, @@ -357,12 +357,14 @@ constraints = [ { name = "uritemplate", specifier = "==4.2.0" }, { name = "urllib3", specifier = "==2.7.0" }, { name = "uuid6", specifier = "==2024.7.10" }, + { name = "uvicorn", specifier = "==0.49.0" }, + { name = "uvloop", specifier = "==0.22.1" }, { name = "vine", specifier = "==5.1.0" }, { name = "vulture", specifier = "==2.14" }, { name = "wcwidth", specifier = "==0.5.3" }, { name = "websocket-client", specifier = "==1.9.0" }, { name = "werkzeug", specifier = "==3.1.7" }, - { name = "workos", specifier = "==6.0.4" }, + { name = "workos", specifier = "==6.0.8" }, { name = "wrapt", specifier = "==1.17.3" }, { name = "xlsxwriter", specifier = "==3.2.9" }, { name = "xmlsec", specifier = "==1.3.17" }, @@ -374,8 +376,11 @@ constraints = [ { name = "zstd", specifier = "==1.5.7.3" }, ] overrides = [ + { name = "azure-mgmt-containerservice", specifier = "==34.1.0" }, + { name = "dulwich", specifier = "==1.2.5" }, { name = "microsoft-kiota-abstractions", specifier = "==1.9.9" }, { name = "okta", specifier = "==3.4.2" }, + { name = "pyjwt", extras = ["crypto"], specifier = "==2.13.0" }, ] [[package]] @@ -393,7 +398,7 @@ version = "1.2.7" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "cryptography" }, - { name = "pyjwt" }, + { name = "pyjwt", extra = ["crypto"] }, { name = "python-dateutil" }, { name = "requests" }, ] @@ -467,7 +472,7 @@ wheels = [ [[package]] name = "aiohttp" -version = "3.13.5" +version = "3.14.0" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "aiohappyeyeballs" }, @@ -476,44 +481,47 @@ dependencies = [ { name = "frozenlist" }, { name = "multidict" }, { name = "propcache" }, + { name = "typing-extensions" }, { name = "yarl" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/77/9a/152096d4808df8e4268befa55fba462f440f14beab85e8ad9bf990516918/aiohttp-3.13.5.tar.gz", hash = "sha256:9d98cc980ecc96be6eb4c1994ce35d28d8b1f5e5208a23b421187d1209dbb7d1", size = 7858271, upload-time = "2026-03-31T22:01:03.343Z" } +sdist = { url = "https://files.pythonhosted.org/packages/ee/ab/93ce242f899b68c51b0578c027aafa791ab3614cb9345fa5d37b5f5c8e3e/aiohttp-3.14.0.tar.gz", hash = "sha256:2882de819734c715fd1b9c11c97e09fa020d14438203d1d354d8ed1702791c9b", size = 7940674, upload-time = "2026-06-01T19:41:02.763Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/d6/f5/a20c4ac64aeaef1679e25c9983573618ff765d7aa829fa2b84ae7573169e/aiohttp-3.13.5-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:7ab7229b6f9b5c1ba4910d6c41a9eb11f543eadb3f384df1b4c293f4e73d44d6", size = 757513, upload-time = "2026-03-31T21:57:02.146Z" }, - { url = "https://files.pythonhosted.org/packages/75/0a/39fa6c6b179b53fcb3e4b3d2b6d6cad0180854eda17060c7218540102bef/aiohttp-3.13.5-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:8f14c50708bb156b3a3ca7230b3d820199d56a48e3af76fa21c2d6087190fe3d", size = 506748, upload-time = "2026-03-31T21:57:04.275Z" }, - { url = "https://files.pythonhosted.org/packages/87/ec/e38ce072e724fd7add6243613f8d1810da084f54175353d25ccf9f9c7e5a/aiohttp-3.13.5-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:e7d2f8616f0ff60bd332022279011776c3ac0faa0f1b463f7bb12326fbc97a1c", size = 501673, upload-time = "2026-03-31T21:57:06.208Z" }, - { url = "https://files.pythonhosted.org/packages/ba/ba/3bc7525d7e2beaa11b309a70d48b0d3cfc3c2089ec6a7d0820d59c657053/aiohttp-3.13.5-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:a2567b72e1ffc3ab25510db43f355b29eeada56c0a622e58dcdb19530eb0a3cb", size = 1763757, upload-time = "2026-03-31T21:57:07.882Z" }, - { url = "https://files.pythonhosted.org/packages/5e/ab/e87744cf18f1bd78263aba24924d4953b41086bd3a31d22452378e9028a0/aiohttp-3.13.5-cp311-cp311-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl", hash = "sha256:fb0540c854ac9c0c5ad495908fdfd3e332d553ec731698c0e29b1877ba0d2ec6", size = 1720152, upload-time = "2026-03-31T21:57:09.946Z" }, - { url = "https://files.pythonhosted.org/packages/6b/f3/ed17a6f2d742af17b50bae2d152315ed1b164b07a5fd5cc1754d99e4dfa5/aiohttp-3.13.5-cp311-cp311-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:c9883051c6972f58bfc4ebb2116345ee2aa151178e99c3f2b2bbe2af712abd13", size = 1818010, upload-time = "2026-03-31T21:57:12.157Z" }, - { url = "https://files.pythonhosted.org/packages/53/06/ecbc63dc937192e2a5cb46df4d3edb21deb8225535818802f210a6ea5816/aiohttp-3.13.5-cp311-cp311-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:2294172ce08a82fb7c7273485895de1fa1186cc8294cfeb6aef4af42ad261174", size = 1907251, upload-time = "2026-03-31T21:57:14.023Z" }, - { url = "https://files.pythonhosted.org/packages/7e/a5/0521aa32c1ddf3aa1e71dcc466be0b7db2771907a13f18cddaa45967d97b/aiohttp-3.13.5-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:3a807cabd5115fb55af198b98178997a5e0e57dead43eb74a93d9c07d6d4a7dc", size = 1759969, upload-time = "2026-03-31T21:57:16.146Z" }, - { url = "https://files.pythonhosted.org/packages/f6/78/a38f8c9105199dd3b9706745865a8a59d0041b6be0ca0cc4b2ccf1bab374/aiohttp-3.13.5-cp311-cp311-manylinux_2_31_riscv64.manylinux_2_39_riscv64.whl", hash = "sha256:aa6d0d932e0f39c02b80744273cd5c388a2d9bc07760a03164f229c8e02662f6", size = 1616871, upload-time = "2026-03-31T21:57:17.856Z" }, - { url = "https://files.pythonhosted.org/packages/6f/41/27392a61ead8ab38072105c71aa44ff891e71653fe53d576a7067da2b4e8/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:60869c7ac4aaabe7110f26499f3e6e5696eae98144735b12a9c3d9eae2b51a49", size = 1739844, upload-time = "2026-03-31T21:57:19.679Z" }, - { url = "https://files.pythonhosted.org/packages/6e/55/5564e7ae26d94f3214250009a0b1c65a0c6af4bf88924ccb6fdab901de28/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_armv7l.whl", hash = "sha256:26d2f8546f1dfa75efa50c3488215a903c0168d253b75fba4210f57ab77a0fb8", size = 1731969, upload-time = "2026-03-31T21:57:22.006Z" }, - { url = "https://files.pythonhosted.org/packages/6d/c5/705a3929149865fc941bcbdd1047b238e4a72bcb215a9b16b9d7a2e8d992/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_ppc64le.whl", hash = "sha256:f1162a1492032c82f14271e831c8f4b49f2b6078f4f5fc74de2c912fa225d51d", size = 1795193, upload-time = "2026-03-31T21:57:24.256Z" }, - { url = "https://files.pythonhosted.org/packages/a6/19/edabed62f718d02cff7231ca0db4ef1c72504235bc467f7b67adb1679f48/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_riscv64.whl", hash = "sha256:8b14eb3262fad0dc2f89c1a43b13727e709504972186ff6a99a3ecaa77102b6c", size = 1606477, upload-time = "2026-03-31T21:57:26.364Z" }, - { url = "https://files.pythonhosted.org/packages/de/fc/76f80ef008675637d88d0b21584596dc27410a990b0918cb1e5776545b5b/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_s390x.whl", hash = "sha256:ca9ac61ac6db4eb6c2a0cd1d0f7e1357647b638ccc92f7e9d8d133e71ed3c6ac", size = 1813198, upload-time = "2026-03-31T21:57:28.316Z" }, - { url = "https://files.pythonhosted.org/packages/e5/67/5b3ac26b80adb20ea541c487f73730dc8fa107d632c998f25bbbab98fcda/aiohttp-3.13.5-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:7996023b2ed59489ae4762256c8516df9820f751cf2c5da8ed2fb20ee50abab3", size = 1752321, upload-time = "2026-03-31T21:57:30.549Z" }, - { url = "https://files.pythonhosted.org/packages/88/06/e4a2e49255ea23fa4feeb5ab092d90240d927c15e47b5b5c48dff5a9ce29/aiohttp-3.13.5-cp311-cp311-win32.whl", hash = "sha256:77dfa48c9f8013271011e51c00f8ada19851f013cde2c48fca1ba5e0caf5bb06", size = 439069, upload-time = "2026-03-31T21:57:32.388Z" }, - { url = "https://files.pythonhosted.org/packages/c0/43/8c7163a596dab4f8be12c190cf467a1e07e4734cf90eebb39f7f5d53fc6a/aiohttp-3.13.5-cp311-cp311-win_amd64.whl", hash = "sha256:d3a4834f221061624b8887090637db9ad4f61752001eae37d56c52fddade2dc8", size = 462859, upload-time = "2026-03-31T21:57:34.455Z" }, - { url = "https://files.pythonhosted.org/packages/be/6f/353954c29e7dcce7cf00280a02c75f30e133c00793c7a2ed3776d7b2f426/aiohttp-3.13.5-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:023ecba036ddd840b0b19bf195bfae970083fd7024ce1ac22e9bba90464620e9", size = 748876, upload-time = "2026-03-31T21:57:36.319Z" }, - { url = "https://files.pythonhosted.org/packages/f5/1b/428a7c64687b3b2e9cd293186695affc0e1e54a445d0361743b231f11066/aiohttp-3.13.5-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:15c933ad7920b7d9a20de151efcd05a6e38302cbf0e10c9b2acb9a42210a2416", size = 499557, upload-time = "2026-03-31T21:57:38.236Z" }, - { url = "https://files.pythonhosted.org/packages/29/47/7be41556bfbb6917069d6a6634bb7dd5e163ba445b783a90d40f5ac7e3a7/aiohttp-3.13.5-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:ab2899f9fa2f9f741896ebb6fa07c4c883bfa5c7f2ddd8cf2aafa86fa981b2d2", size = 500258, upload-time = "2026-03-31T21:57:39.923Z" }, - { url = "https://files.pythonhosted.org/packages/67/84/c9ecc5828cb0b3695856c07c0a6817a99d51e2473400f705275a2b3d9239/aiohttp-3.13.5-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:a60eaa2d440cd4707696b52e40ed3e2b0f73f65be07fd0ef23b6b539c9c0b0b4", size = 1749199, upload-time = "2026-03-31T21:57:41.938Z" }, - { url = "https://files.pythonhosted.org/packages/f0/d3/3c6d610e66b495657622edb6ae7c7fd31b2e9086b4ec50b47897ad6042a9/aiohttp-3.13.5-cp312-cp312-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl", hash = "sha256:55b3bdd3292283295774ab585160c4004f4f2f203946997f49aac032c84649e9", size = 1721013, upload-time = "2026-03-31T21:57:43.904Z" }, - { url = "https://files.pythonhosted.org/packages/49/a0/24409c12217456df0bae7babe3b014e460b0b38a8e60753d6cb339f6556d/aiohttp-3.13.5-cp312-cp312-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:c2b2355dc094e5f7d45a7bb262fe7207aa0460b37a0d87027dcf21b5d890e7d5", size = 1781501, upload-time = "2026-03-31T21:57:46.285Z" }, - { url = "https://files.pythonhosted.org/packages/98/9d/b65ec649adc5bccc008b0957a9a9c691070aeac4e41cea18559fef49958b/aiohttp-3.13.5-cp312-cp312-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:b38765950832f7d728297689ad78f5f2cf79ff82487131c4d26fe6ceecdc5f8e", size = 1878981, upload-time = "2026-03-31T21:57:48.734Z" }, - { url = "https://files.pythonhosted.org/packages/57/d8/8d44036d7eb7b6a8ec4c5494ea0c8c8b94fbc0ed3991c1a7adf230df03bf/aiohttp-3.13.5-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:b18f31b80d5a33661e08c89e202edabf1986e9b49c42b4504371daeaa11b47c1", size = 1767934, upload-time = "2026-03-31T21:57:51.171Z" }, - { url = "https://files.pythonhosted.org/packages/31/04/d3f8211f273356f158e3464e9e45484d3fb8c4ce5eb2f6fe9405c3273983/aiohttp-3.13.5-cp312-cp312-manylinux_2_31_riscv64.manylinux_2_39_riscv64.whl", hash = "sha256:33add2463dde55c4f2d9635c6ab33ce154e5ecf322bd26d09af95c5f81cfa286", size = 1566671, upload-time = "2026-03-31T21:57:53.326Z" }, - { url = "https://files.pythonhosted.org/packages/41/db/073e4ebe00b78e2dfcacff734291651729a62953b48933d765dc513bf798/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:327cc432fdf1356fb4fbc6fe833ad4e9f6aacb71a8acaa5f1855e4b25910e4a9", size = 1705219, upload-time = "2026-03-31T21:57:55.385Z" }, - { url = "https://files.pythonhosted.org/packages/48/45/7dfba71a2f9fd97b15c95c06819de7eb38113d2cdb6319669195a7d64270/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_armv7l.whl", hash = "sha256:7c35b0bf0b48a70b4cb4fc5d7bed9b932532728e124874355de1a0af8ec4bc88", size = 1743049, upload-time = "2026-03-31T21:57:57.341Z" }, - { url = "https://files.pythonhosted.org/packages/18/71/901db0061e0f717d226386a7f471bb59b19566f2cae5f0d93874b017271f/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_ppc64le.whl", hash = "sha256:df23d57718f24badef8656c49743e11a89fd6f5358fa8a7b96e728fda2abf7d3", size = 1749557, upload-time = "2026-03-31T21:57:59.626Z" }, - { url = "https://files.pythonhosted.org/packages/08/d5/41eebd16066e59cd43728fe74bce953d7402f2b4ddfdfef2c0e9f17ca274/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_riscv64.whl", hash = "sha256:02e048037a6501a5ec1f6fc9736135aec6eb8a004ce48838cb951c515f32c80b", size = 1558931, upload-time = "2026-03-31T21:58:01.972Z" }, - { url = "https://files.pythonhosted.org/packages/30/e6/4a799798bf05740e66c3a1161079bda7a3dd8e22ca392481d7a7f9af82a6/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_s390x.whl", hash = "sha256:31cebae8b26f8a615d2b546fee45d5ffb76852ae6450e2a03f42c9102260d6fe", size = 1774125, upload-time = "2026-03-31T21:58:04.007Z" }, - { url = "https://files.pythonhosted.org/packages/84/63/7749337c90f92bc2cb18f9560d67aa6258c7060d1397d21529b8004fcf6f/aiohttp-3.13.5-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:888e78eb5ca55a615d285c3c09a7a91b42e9dd6fc699b166ebd5dee87c9ccf14", size = 1732427, upload-time = "2026-03-31T21:58:06.337Z" }, - { url = "https://files.pythonhosted.org/packages/98/de/cf2f44ff98d307e72fb97d5f5bbae3bfcb442f0ea9790c0bf5c5c2331404/aiohttp-3.13.5-cp312-cp312-win32.whl", hash = "sha256:8bd3ec6376e68a41f9f95f5ed170e2fcf22d4eb27a1f8cb361d0508f6e0557f3", size = 433534, upload-time = "2026-03-31T21:58:08.712Z" }, - { url = "https://files.pythonhosted.org/packages/aa/ca/eadf6f9c8fa5e31d40993e3db153fb5ed0b11008ad5d9de98a95045bed84/aiohttp-3.13.5-cp312-cp312-win_amd64.whl", hash = "sha256:110e448e02c729bcebb18c60b9214a87ba33bac4a9fa5e9a5f139938b56c6cb1", size = 460446, upload-time = "2026-03-31T21:58:10.945Z" }, + { url = "https://files.pythonhosted.org/packages/67/47/7727bfe8db93f8835a001bd4359d8480cc68d1259b8bce334668f8be97bd/aiohttp-3.14.0-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:54bf3522d6f7351e55f89a62d5c2bf138ad557b031670266c5df604ae88e0b5a", size = 759147, upload-time = "2026-06-01T19:37:12.918Z" }, + { url = "https://files.pythonhosted.org/packages/eb/f2/cd3fedff6fade73d71df9ec908c210cec518ef90fd00289250684b90aecf/aiohttp-3.14.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:0746d9fb0ac4fdef643a84494efe3f06d50335dd8c7a530228b86448aae0a803", size = 513705, upload-time = "2026-06-01T19:37:14.633Z" }, + { url = "https://files.pythonhosted.org/packages/5a/fe/49746b6b610144a06323bebd8e1211a390310d8c69b98dd6d52df341bc3e/aiohttp-3.14.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:9f3a96b6d39a4872222beee72e1df41d2ff886ae96152cf3e757ef8c5673ef0e", size = 509627, upload-time = "2026-06-01T19:37:16.385Z" }, + { url = "https://files.pythonhosted.org/packages/4c/3f/28f2f6cf3d5c0e7b01b27140d0e7873fd11fb341169ad3ce78ad04aba628/aiohttp-3.14.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:d336820adbb914debbc90a1d8c1bfc4bea55996aecf64866a989d35d1f9fd903", size = 1769293, upload-time = "2026-06-01T19:37:18.067Z" }, + { url = "https://files.pythonhosted.org/packages/97/6f/2e5f1b525d5474b12b3c60abf733a755845f3bceff21542081ada515f837/aiohttp-3.14.0-cp311-cp311-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl", hash = "sha256:71b2604c9bfc1b115547d63a094d5244b3f02799833513a99a68aaa7b167c4cb", size = 1732363, upload-time = "2026-06-01T19:37:20.138Z" }, + { url = "https://files.pythonhosted.org/packages/a8/ce/596120faa85ca7b19cd061e3f2f3be23aa8f11a0aedf9191db9e0da1bd76/aiohttp-3.14.0-cp311-cp311-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:610d68800435903e303ca0542b9d3e4eb72a12ff33a6d471a070c1d81eebd3c2", size = 1840375, upload-time = "2026-06-01T19:37:22.104Z" }, + { url = "https://files.pythonhosted.org/packages/72/3c/a7ffe05a757a4a7867643da69357ec41f506879fbd1b231d2ed90af246b2/aiohttp-3.14.0-cp311-cp311-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:514db9a79337068981ee2137310283a07b4b885c584991097a91a4da419bcb81", size = 1921484, upload-time = "2026-06-01T19:37:24.068Z" }, + { url = "https://files.pythonhosted.org/packages/93/fa/2c861170bbd4a491de93a69e081db1d971092569e0d593a98ef62c384dc1/aiohttp-3.14.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:c452d17eeb95d563fc8b936f3050301dbd1d268126c4632d8b70ede9696202ee", size = 1774153, upload-time = "2026-06-01T19:37:26.256Z" }, + { url = "https://files.pythonhosted.org/packages/9d/da/1d2f5a165f47ec9b1f69d37b8b977fdc4d501aa72ffb7930db27bb9e49ea/aiohttp-3.14.0-cp311-cp311-manylinux_2_31_riscv64.manylinux_2_39_riscv64.whl", hash = "sha256:ed94a81506e3d1bdbad5108f497a58f2a2354aedb4ca314d5326f07d1fd1ac2d", size = 1632569, upload-time = "2026-06-01T19:37:28.192Z" }, + { url = "https://files.pythonhosted.org/packages/46/1d/7a6e295c4257252f70f69e90864fdad74b6a1293054fb3f9e65a15de6d63/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:1394dce36e0f0d260ac0b555a654de19cb989f3c1b8bdd24f505314dfea18a00", size = 1740325, upload-time = "2026-06-01T19:37:30.08Z" }, + { url = "https://files.pythonhosted.org/packages/f1/7e/e1899b1ca3ec62f1eab2a5cbde14039b97493f7f53eb88d9b668562ffa8d/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_armv7l.whl", hash = "sha256:d1467d1e7b48a73ca7237e0ee4335f3d02b923dbc27b82fd254bc301c97d4026", size = 1748691, upload-time = "2026-06-01T19:37:32.211Z" }, + { url = "https://files.pythonhosted.org/packages/ec/54/4e6b61c1fe7d3433f82bcc6bd7e4d7c683a742a10c9b12a025fd3695c047/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_ppc64le.whl", hash = "sha256:6a5f3532125233c261cf61f32df4059cfcf482eb793c7d3db8452e3142028b86", size = 1814477, upload-time = "2026-06-01T19:37:34.173Z" }, + { url = "https://files.pythonhosted.org/packages/9c/38/86fd51be2e08d8e45c83d879d255f10391903cd9fe2a16512f7591a15873/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_riscv64.whl", hash = "sha256:3ea81eb518a2ecb319d8ec6d1424a37c773f6634bd87d6985eb606b2faac419f", size = 1623393, upload-time = "2026-06-01T19:37:36.281Z" }, + { url = "https://files.pythonhosted.org/packages/78/49/466e947a42a88ee23c486d036e7e5d1b097f1bafd8084ad9c9a0a92f0f43/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_s390x.whl", hash = "sha256:32e735c3182de7b64f6941a4ede48b38c7f47d9437bd615dd30b5bda8fa1bc93", size = 1824097, upload-time = "2026-06-01T19:37:38.421Z" }, + { url = "https://files.pythonhosted.org/packages/f3/89/35f3410bc284682338a1be6b6ea0c5abfa05f063942cfaa9256608440434/aiohttp-3.14.0-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:c21ca9a1c63d4509158f478aeb9d02914dcc52adc68d1bc9dee2452284ee5996", size = 1764790, upload-time = "2026-06-01T19:37:40.755Z" }, + { url = "https://files.pythonhosted.org/packages/42/80/2d4291bd5724d3d17e5951aff5a3e02281483fb47295f0788276ee66cd73/aiohttp-3.14.0-cp311-cp311-win32.whl", hash = "sha256:19ca5fc84130675ba11c6ca5c7da5cb65f7bf8a32cdd2b616bf49cd334688aae", size = 454176, upload-time = "2026-06-01T19:37:42.837Z" }, + { url = "https://files.pythonhosted.org/packages/59/ed/41d0ad4f6ececffc32bdf1f7b494e5498f7ca5c849ea2e3cc9bbd1668251/aiohttp-3.14.0-cp311-cp311-win_amd64.whl", hash = "sha256:d488e6e9d3bb8ba5ae7066d5be885ae9670eba021b8c6ccb9a3a568e6b19d6e5", size = 479334, upload-time = "2026-06-01T19:37:44.776Z" }, + { url = "https://files.pythonhosted.org/packages/d1/86/c0b5e305c770053f8c3d069bb52b8196917ba91949d1962d52eb307fb0d2/aiohttp-3.14.0-cp311-cp311-win_arm64.whl", hash = "sha256:8b93618102caf12801638a01a2b478a55410ddd71bd41cfaf6f707953a49ac43", size = 450262, upload-time = "2026-06-01T19:37:46.461Z" }, + { url = "https://files.pythonhosted.org/packages/89/97/2b6889bfb6b6847520d50d95eb8c4307a45e28aaca39faf4a9454b3d1b2f/aiohttp-3.14.0-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:b29518c9c2ec7e373e68259206a137c7f4f5439c58baaec4b5ab3ab799850a4e", size = 750194, upload-time = "2026-06-01T19:37:48.164Z" }, + { url = "https://files.pythonhosted.org/packages/21/e2/62634b7fff918ed98c3c6b2f0e70d520f7f28846cb412d451b04354c6459/aiohttp-3.14.0-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:dbec68ce61b64cb73cab4d33df9433427b1713c8bcccb181dce695c1b6f8e87c", size = 506966, upload-time = "2026-06-01T19:37:50.014Z" }, + { url = "https://files.pythonhosted.org/packages/dd/fb/5ce075150828c797a5106f1c2fb26034e709d4289b9d2bf8b07f1e59fac6/aiohttp-3.14.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:3cdf534aa455593e589302990c5097aa5c92c06c4262a20da22934f9186a5fff", size = 507527, upload-time = "2026-06-01T19:37:51.96Z" }, + { url = "https://files.pythonhosted.org/packages/01/d5/405a0ae4e6b081754a3609c1c97c63a950e000a2def16046f1e736933a0e/aiohttp-3.14.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:cb6c657104393b5fbff01a5f59b2023db74058a8077d94475d6c25d03882a108", size = 1762420, upload-time = "2026-06-01T19:37:53.839Z" }, + { url = "https://files.pythonhosted.org/packages/ae/1d/e05a7c896b15a6bc6fb8fc5319eb437861c2c49c34559ef928add6590315/aiohttp-3.14.0-cp312-cp312-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl", hash = "sha256:46fbbec4e4fab7428d4396a3823f9320e4560aa3113b89eeebce712c27c9ed5a", size = 1733672, upload-time = "2026-06-01T19:37:55.791Z" }, + { url = "https://files.pythonhosted.org/packages/cc/22/a72f7c459e195fa41bf4f7abd1f925b91fe91f8097e51c654229ba144a33/aiohttp-3.14.0-cp312-cp312-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:2c2c7e05dd5335b298085abf45ddf98673934c3ee1c083d0b9ea13d4186ad500", size = 1805064, upload-time = "2026-06-01T19:37:57.931Z" }, + { url = "https://files.pythonhosted.org/packages/80/50/e85bdaba0be59ca4838005ebfef4048fcdd5f35a02b07057a9a123394440/aiohttp-3.14.0-cp312-cp312-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:3c7139100fbaae76515b73051d8f0aa3a3ff02e415eec8a8eee8e2223d9ba955", size = 1902125, upload-time = "2026-06-01T19:38:00.225Z" }, + { url = "https://files.pythonhosted.org/packages/19/d8/51de5c6b971c27bb1ef620293b8d1ca611ec78736b34b3f6ccf68e4c8785/aiohttp-3.14.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:78d6f9286a629ce52728430afe18f8ed2b6c39a1fddb3802d7244b9983910ad2", size = 1783112, upload-time = "2026-06-01T19:38:02.641Z" }, + { url = "https://files.pythonhosted.org/packages/73/ae/b4402bfde77e43dfb1b6ccff83c7b7ab63ed06b50c4754f0c5423fb374fe/aiohttp-3.14.0-cp312-cp312-manylinux_2_31_riscv64.manylinux_2_39_riscv64.whl", hash = "sha256:cc3c3e12cdaeb92d7dcf13db00e9f6b1956b910e47256e696df1cfa946d02159", size = 1586356, upload-time = "2026-06-01T19:38:04.637Z" }, + { url = "https://files.pythonhosted.org/packages/bc/05/750a3265ca4dc54a460bd0cb1121a8f2ce9171fce4a135fb47ea7fd594d2/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:4d6a998191f5ebe3b8c28463ff72bc030250008b3193c402464efadd08b5ca02", size = 1723119, upload-time = "2026-06-01T19:38:06.713Z" }, + { url = "https://files.pythonhosted.org/packages/37/01/8c0812c50b3b1b1c37b323bf170d6be8847a8f234060485b7d1e71953f60/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_armv7l.whl", hash = "sha256:0fc2b75ae8d169d853be2862d960be8550da6c5c65711d5476407eb3fdb006bd", size = 1757216, upload-time = "2026-06-01T19:38:08.736Z" }, + { url = "https://files.pythonhosted.org/packages/47/2a/50fb98028a26887cbe48dcc1df92a90825615bc73b5584301304090cded8/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_ppc64le.whl", hash = "sha256:16eee56bcc72d04600bc56c1759982c2385ec0b41d3fd3521f836bf64a0957ef", size = 1770500, upload-time = "2026-06-01T19:38:11.111Z" }, + { url = "https://files.pythonhosted.org/packages/bd/32/0ffd598a2fa2b9a423daf242e700cfdabda35d6e602394ad9ae58972c1c7/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_riscv64.whl", hash = "sha256:5a2e7ca615c3ddc15b82687e05a624e5f5cba3f1d6c20cb81172d70ea498451e", size = 1576224, upload-time = "2026-06-01T19:38:13.391Z" }, + { url = "https://files.pythonhosted.org/packages/0b/f9/b9fc381dd9b66afb33f2634c40e229d106467be0afcabe79648631ab6712/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_s390x.whl", hash = "sha256:f0b7b8bbbec3ce9467ee0ebe334622fd90624f593edd3136c567811453fc4fae", size = 1794252, upload-time = "2026-06-01T19:38:15.498Z" }, + { url = "https://files.pythonhosted.org/packages/a8/fb/05d9214c975f23225a8cd5c439325e338c7c377b315480ef3871db51f54e/aiohttp-3.14.0-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:5ba10966d4f03dd96a14365be4b8e37c327c76f11c3ca867116966cdd9f98066", size = 1760193, upload-time = "2026-06-01T19:38:17.624Z" }, + { url = "https://files.pythonhosted.org/packages/d9/4b/02992fc4fb9e1b6673ee3f888a8e587a6447afda1f6f4aca776c148c2876/aiohttp-3.14.0-cp312-cp312-win32.whl", hash = "sha256:101df7779c80c0636014a6b2c6642acd3efb5b355d48347c9d7dfb720aee9430", size = 448650, upload-time = "2026-06-01T19:38:19.545Z" }, + { url = "https://files.pythonhosted.org/packages/39/e9/246532214c3abda518477cbaaf16d420295ad8effa5233844cbb38f299ab/aiohttp-3.14.0-cp312-cp312-win_amd64.whl", hash = "sha256:b0a5747586d4467efd1f932710b269131c9717a872dce082cd92a00c1c13123a", size = 476145, upload-time = "2026-06-01T19:38:21.505Z" }, + { url = "https://files.pythonhosted.org/packages/2b/c3/63f8c20090048915711598b0adf475b149216d736157961de06480a45b15/aiohttp-3.14.0-cp312-cp312-win_arm64.whl", hash = "sha256:5f1c5be60add78fabb4aacd13c5a348ae79d2fcbfc7fa78da8f1eb192273b370", size = 444250, upload-time = "2026-06-01T19:38:24.027Z" }, ] [[package]] @@ -1043,15 +1051,6 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/9e/43/53afb8ba17218f19b77c7834128566c5bbb100a0ad9ba2e8e89d089d7079/autopep8-2.3.2-py2.py3-none-any.whl", hash = "sha256:ce8ad498672c845a0c3de2629c15b635ec2b05ef8177a6e7c91c74f3e9b51128", size = 45807, upload-time = "2025-01-14T14:46:15.466Z" }, ] -[[package]] -name = "awsipranges" -version = "0.3.3" -source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/19/2e/6efa95f995369da828715f41705686cd214b9259ed758266942553d40441/awsipranges-0.3.3.tar.gz", hash = "sha256:4f0b3f22a9dc1163c85b513bed812b6c92bdacd674e6a7b68252a3c25b99e2c0", size = 16739, upload-time = "2022-02-10T21:08:32.825Z" } -wheels = [ - { url = "https://files.pythonhosted.org/packages/83/ce/5c9a8bf91bdc9592a409c99e58fd99f2727ab8d634719c0ad796021b76d7/awsipranges-0.3.3-py3-none-any.whl", hash = "sha256:f3d7a54aeaf7fe310beb5d377a4034a63a51b72677ae6af3e0967bc4de7eedaf", size = 18106, upload-time = "2022-02-10T21:08:31.497Z" }, -] - [[package]] name = "azure-cli-core" version = "2.83.0" @@ -1074,7 +1073,7 @@ dependencies = [ { name = "pkginfo" }, { name = "psutil", marker = "sys_platform != 'cygwin'" }, { name = "py-deviceid" }, - { name = "pyjwt" }, + { name = "pyjwt", extra = ["crypto"] }, { name = "pyopenssl" }, { name = "requests", extra = ["socks"] }, ] @@ -1409,6 +1408,20 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/3d/66/0d8ae9ca4d75e57746026a1f9a10a7e25029511c128cf20166fce516bda9/azure_mgmt_logic-10.0.0-py3-none-any.whl", hash = "sha256:525c78afedf3edb35eb0a16152c8beba89769ee1bc6af01bcdc42842a551e443", size = 235433, upload-time = "2022-06-13T01:38:27.333Z" }, ] +[[package]] +name = "azure-mgmt-managementgroups" +version = "1.1.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "azure-mgmt-core" }, + { name = "isodate" }, + { name = "typing-extensions" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/fd/73/ac5e064ed7343e1b3172f32f09be3efca906087218d3046b5038f2f394ed/azure_mgmt_managementgroups-1.1.0.tar.gz", hash = "sha256:e6199baf118890ba2bda35dda83a88861c0b1bbef126311b20ec12eed9681951", size = 60101, upload-time = "2026-02-13T03:45:45.439Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/92/bc/993158de03cc0a49f2cf8192615ffedbc508c417cb3522e88f6652b714cc/azure_mgmt_managementgroups-1.1.0-py3-none-any.whl", hash = "sha256:140934589559ef6afcac6f1d24f995588a1965aaa89d47851c1cc639fafb1942", size = 83586, upload-time = "2026-02-13T03:45:46.836Z" }, +] + [[package]] name = "azure-mgmt-monitor" version = "6.0.2" @@ -1728,7 +1741,7 @@ wheels = [ [[package]] name = "cartography" -version = "0.135.0" +version = "0.138.1" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "adal" }, @@ -1748,6 +1761,7 @@ dependencies = [ { name = "azure-mgmt-eventhub" }, { name = "azure-mgmt-keyvault" }, { name = "azure-mgmt-logic" }, + { name = "azure-mgmt-managementgroups" }, { name = "azure-mgmt-monitor" }, { name = "azure-mgmt-network" }, { name = "azure-mgmt-resource" }, @@ -1756,6 +1770,7 @@ dependencies = [ { name = "azure-mgmt-storage" }, { name = "azure-mgmt-synapse" }, { name = "azure-mgmt-web" }, + { name = "azure-storage-blob" }, { name = "azure-synapse-artifacts" }, { name = "backoff" }, { name = "boto3" }, @@ -1767,8 +1782,12 @@ dependencies = [ { name = "duo-client" }, { name = "google-api-python-client" }, { name = "google-auth" }, + { name = "google-cloud-aiplatform" }, + { name = "google-cloud-artifact-registry" }, { name = "google-cloud-asset" }, { name = "google-cloud-resource-manager" }, + { name = "google-cloud-run" }, + { name = "google-cloud-storage" }, { name = "httpx" }, { name = "kubernetes" }, { name = "marshmallow" }, @@ -1794,9 +1813,9 @@ dependencies = [ { name = "workos" }, { name = "xmltodict" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/39/47/606851d2403a983b63813b9e95427a5dd896e49bc5a501868c041262e9a5/cartography-0.135.0.tar.gz", hash = "sha256:3f500cd22c3b392d00e8b49f62acc95fd4dcd559ce514aafe2eb8101133c7a49", size = 9106458, upload-time = "2026-04-10T16:25:34.898Z" } +sdist = { url = "https://files.pythonhosted.org/packages/51/cd/0eb6a5a3c89cc179801d902ade9719af1a583c516c00f50d72b8207db1eb/cartography-0.138.1.tar.gz", hash = "sha256:356e946a0bcac899cba293d57803c71bd35fdeabe623f5f67d9405d7a643af9f", size = 9756966, upload-time = "2026-06-19T22:11:32.411Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/b1/e1/99a26b3e662202be77961aba73338e1448623490710b81783e53a4bbef15/cartography-0.135.0-py3-none-any.whl", hash = "sha256:c62c32a6917b8f23a8b98fe2b6c7c4a918b50f55918482966c4dae1cf5f538e1", size = 1590545, upload-time = "2026-04-10T16:25:37.669Z" }, + { url = "https://files.pythonhosted.org/packages/a8/15/4447ec968825b2a19cba26ecb74964208aa3f941d9181a7782572e30b43d/cartography-0.138.1-py3-none-any.whl", hash = "sha256:88ec0898ea1a1b3f4653be9a3e7e61144f5cee20384b9040e92039617d39f029", size = 2014725, upload-time = "2026-06-19T22:11:29.886Z" }, ] [[package]] @@ -2226,16 +2245,15 @@ wheels = [ ] [[package]] -name = "detect-secrets" -version = "1.5.0" +name = "deprecated" +version = "1.3.1" source = { registry = "https://pypi.org/simple" } dependencies = [ - { name = "pyyaml" }, - { name = "requests" }, + { name = "wrapt" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/69/67/382a863fff94eae5a0cf05542179169a1c49a4c8784a9480621e2066ca7d/detect_secrets-1.5.0.tar.gz", hash = "sha256:6bb46dcc553c10df51475641bb30fd69d25645cc12339e46c824c1e0c388898a", size = 97351, upload-time = "2024-05-06T17:46:19.721Z" } +sdist = { url = "https://files.pythonhosted.org/packages/49/85/12f0a49a7c4ffb70572b6c2ef13c90c88fd190debda93b23f026b25f9634/deprecated-1.3.1.tar.gz", hash = "sha256:b1b50e0ff0c1fddaa5708a2c6b0a6588bb09b892825ab2b214ac9ea9d92a5223", size = 2932523, upload-time = "2025-10-30T08:19:02.757Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/4e/5e/4f5fe4b89fde1dc3ed0eb51bd4ce4c0bca406246673d370ea2ad0c58d747/detect_secrets-1.5.0-py3-none-any.whl", hash = "sha256:e24e7b9b5a35048c313e983f76c4bd09dad89f045ff059e354f9943bf45aa060", size = 120341, upload-time = "2024-05-06T17:46:16.628Z" }, + { url = "https://files.pythonhosted.org/packages/84/d0/205d54408c08b13550c733c4b85429e7ead111c7f0014309637425520a9a/deprecated-1.3.1-py2.py3-none-any.whl", hash = "sha256:597bfef186b6f60181535a29fbe44865ce137a5079f295b479886c82729d5f3f", size = 11298, upload-time = "2025-10-30T08:19:00.758Z" }, ] [[package]] @@ -2360,6 +2378,19 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/c4/f1/468b49cccba3b42dda571063a14c668bb0b53a1d5712426d18e36663bd53/django_environ-0.11.2-py2.py3-none-any.whl", hash = "sha256:0ff95ab4344bfeff693836aa978e6840abef2e2f1145adff7735892711590c05", size = 19141, upload-time = "2023-09-01T21:02:59.88Z" }, ] +[[package]] +name = "django-eventstream" +version = "5.3.3" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "django" }, + { name = "django-grip" }, + { name = "gripcontrol" }, + { name = "pyjwt", extra = ["crypto"] }, + { name = "six" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/f2/49/ec6cbc24f3f30465370df7096cfea9722bad2b0c1f35a7ff5d45fb96cff6/django_eventstream-5.3.3.tar.gz", hash = "sha256:6880b03298eebf18c1b736b972fb862eaf631dfbb79f8b27496418a3495d08dc", size = 47622, upload-time = "2025-10-23T00:22:40.291Z" } + [[package]] name = "django-filter" version = "24.3" @@ -2372,6 +2403,19 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/09/b1/92f1c30b47c1ebf510c35a2ccad9448f73437e5891bbd2b4febe357cc3de/django_filter-24.3-py3-none-any.whl", hash = "sha256:c4852822928ce17fb699bcfccd644b3574f1a2d80aeb2b4ff4f16b02dd49dc64", size = 95011, upload-time = "2024-08-02T13:27:55.616Z" }, ] +[[package]] +name = "django-grip" +version = "3.5.2" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "django" }, + { name = "gripcontrol" }, + { name = "pubcontrol" }, + { name = "six" }, + { name = "werkzeug" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/cb/d0/2c7b04fa864073cd8cb324f8674672162282d97540d56732cbd3a9ae5bca/django-grip-3.5.2.tar.gz", hash = "sha256:1ee1601492cd110256bd03e4a68797a9fbefa27c15f5a838bf245df97db0450c", size = 7626, upload-time = "2025-03-24T18:53:58.677Z" } + [[package]] name = "django-guid" version = "3.5.0" @@ -2457,7 +2501,7 @@ source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "django" }, { name = "djangorestframework" }, - { name = "pyjwt" }, + { name = "pyjwt", extra = ["crypto"] }, ] sdist = { url = "https://files.pythonhosted.org/packages/a8/27/2874a325c11112066139769f7794afae238a07ce6adf96259f08fd37a9d7/djangorestframework_simplejwt-5.5.1.tar.gz", hash = "sha256:e72c5572f51d7803021288e2057afcbd03f17fe11d484096f40a460abc76e87f", size = 101265, upload-time = "2025-07-21T16:52:25.026Z" } wheels = [ @@ -2487,6 +2531,15 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/e3/26/57c6fb270950d476074c087527a558ccb6f4436657314bfb6cdf484114c4/docker-7.1.0-py3-none-any.whl", hash = "sha256:c96b93b7f0a746f9e77d325bcfb87422a3d8bd4f03136ae8a85b37f1898d5fc0", size = 147774, upload-time = "2024-05-23T11:13:55.01Z" }, ] +[[package]] +name = "docstring-parser" +version = "0.18.0" +source = { registry = "https://pypi.org/simple" } +sdist = { url = "https://files.pythonhosted.org/packages/e0/4d/f332313098c1de1b2d2ff91cf2674415cc7cddab2ca1b01ae29774bd5fdf/docstring_parser-0.18.0.tar.gz", hash = "sha256:292510982205c12b1248696f44959db3cdd1740237a968ea1e2e7a900eeb2015", size = 29341, upload-time = "2026-04-14T04:09:19.867Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/a7/5f/ed01f9a3cdffbd5a008556fc7b2a08ddb1cc6ace7effa7340604b1d16699/docstring_parser-0.18.0-py3-none-any.whl", hash = "sha256:b3fcbed555c47d8479be0796ef7e19c2670d428d72e96da63f3a40122860374b", size = 22484, upload-time = "2026-04-14T04:09:18.638Z" }, +] + [[package]] name = "dogpile-cache" version = "1.5.0" @@ -2576,24 +2629,27 @@ wheels = [ [[package]] name = "dulwich" -version = "0.23.0" +version = "1.2.5" source = { registry = "https://pypi.org/simple" } dependencies = [ + { name = "typing-extensions", marker = "python_full_version < '3.12'" }, { name = "urllib3" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/4b/ac/ba58cf420640c7bc77ae8e1b31e174d83c9117750c63cf9ea3b5e202e5c4/dulwich-0.23.0.tar.gz", hash = "sha256:0aa6c2489dd5e978b27e9b75983b7331a66c999f0efc54ebe37cab808ed322ae", size = 575116, upload-time = "2025-06-21T17:56:47.494Z" } +sdist = { url = "https://files.pythonhosted.org/packages/7f/85/ceb8ecff5cdeee4ceeebb86b599476dee559041dacc6c2c50cc0d4711549/dulwich-1.2.5.tar.gz", hash = "sha256:0395b2c8924c3424bafe2d9c1edd5348cc4b21ce9c1d6655bf01f9a5c47164c8", size = 1253230, upload-time = "2026-05-28T22:27:55.17Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/ae/11/f6bbba8583f69cf19ef4bd7f5fde1a6b5ccaf8b6951781cec8db247116f4/dulwich-0.23.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:d68498fdda13ab00791b483daab3bcfe9f9721c037aa458695e6ad81640c57cc", size = 972658, upload-time = "2025-06-21T17:56:13.505Z" }, - { url = "https://files.pythonhosted.org/packages/2b/9d/2720e0ab58666378a33c752a61543f936cd6b06dfe5d84a2215ddc0914b0/dulwich-0.23.0-cp311-cp311-manylinux_2_28_aarch64.whl", hash = "sha256:cb7bb930b12471a1cfcea4b3d25a671dc0ad32573f0ad25684684298959a1527", size = 1049813, upload-time = "2025-06-21T17:56:14.884Z" }, - { url = "https://files.pythonhosted.org/packages/e5/f3/81d8075141dfcc0a0449c2093596e58d3e11444e3af54e819eca63b84dd0/dulwich-0.23.0-cp311-cp311-manylinux_2_28_x86_64.whl", hash = "sha256:a2abbce32fd2bc7902bcc5f69b10bf22576810de21651baaa864b78fd7aec261", size = 1051639, upload-time = "2025-06-21T17:56:16.437Z" }, - { url = "https://files.pythonhosted.org/packages/4f/0d/c06ccb227b096aef5906142fe78b5c79f9070a0ea6152fc219941186d540/dulwich-0.23.0-cp311-cp311-win32.whl", hash = "sha256:9e3151f10ce2a9ff91bca64c74345217f53bdd947dc958032343822009832f7a", size = 642918, upload-time = "2025-06-21T17:56:18.373Z" }, - { url = "https://files.pythonhosted.org/packages/d7/1c/1e99aa34c9aead9e641b2d9934f0a3d00257f75027cf5cdecc8a1a6c18ae/dulwich-0.23.0-cp311-cp311-win_amd64.whl", hash = "sha256:3ae9f1d9dc92d4e9a3f89ba2c55221f7b6442c5dd93b3f6f539a3c9eb3f37bdd", size = 659010, upload-time = "2025-06-21T17:56:19.947Z" }, - { url = "https://files.pythonhosted.org/packages/4a/d7/1e6fba0235babe912e8467b036062e37d11672cbbeb0d8074f9d4559057b/dulwich-0.23.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:52cdef66a7994d29528ca79ca59452518bbba3fd56a9c61c61f6c467c1c7956e", size = 960292, upload-time = "2025-06-21T17:56:21.308Z" }, - { url = "https://files.pythonhosted.org/packages/4b/6a/23f0c487ec03f2752600cab4a8e0dedb38186246c475bf3fa90a8db830d5/dulwich-0.23.0-cp312-cp312-manylinux_2_28_aarch64.whl", hash = "sha256:d473888a6ab9ed5d4a4c3f053cbe5b77f72d54b6efdf5688fed76094316e571e", size = 1047892, upload-time = "2025-06-21T17:56:22.989Z" }, - { url = "https://files.pythonhosted.org/packages/c7/e2/8f3d216be5fd0ee1180d917b59b34b54b9896384cf139f319b5d3a8f16b4/dulwich-0.23.0-cp312-cp312-manylinux_2_28_x86_64.whl", hash = "sha256:19fcf20224c641a61c774da92f098fbaae9938c7e17a52841e64092adf7e78f9", size = 1048699, upload-time = "2025-06-21T17:56:24.602Z" }, - { url = "https://files.pythonhosted.org/packages/8f/c4/18e6223cd4ad1ae9334eb4e6aa5952fd8f5c3d75762918eb90c209fec4ba/dulwich-0.23.0-cp312-cp312-win32.whl", hash = "sha256:7fc8b76b704ef35cd001e993e3aa4e1d666a2064bf467c07c560f12b2959dcaf", size = 641268, upload-time = "2025-06-21T17:56:26.18Z" }, - { url = "https://files.pythonhosted.org/packages/b8/9c/65bfbbac62d8a2967e13f6a1512371c5eb6b906a61fb6dead992669cad0e/dulwich-0.23.0-cp312-cp312-win_amd64.whl", hash = "sha256:cb0566b888b578325350b4d67c61a0de35d417e9877560e3a6df88cae4576a59", size = 657837, upload-time = "2025-06-21T17:56:27.821Z" }, - { url = "https://files.pythonhosted.org/packages/35/31/49318ee9db4b402e6d8b9b01bd4cae9298f59e1bb9bd56cf4a94e48fa069/dulwich-0.23.0-py3-none-any.whl", hash = "sha256:d8da6694ca332bb48775e35ee2215aa4673821164a91b83062f699c69f7cd135", size = 313776, upload-time = "2025-06-21T17:56:46.221Z" }, + { url = "https://files.pythonhosted.org/packages/4a/4a/654ae1671610fdf6b65a64586ad67ddd8550d4d08a632b2a4b9614754b6d/dulwich-1.2.5-cp311-cp311-macosx_10_12_x86_64.whl", hash = "sha256:556593fd11637f80f6018bee1916b1a84f5b420423b470ebb3f1a782ad6ef081", size = 1399277, upload-time = "2026-05-28T22:27:00.801Z" }, + { url = "https://files.pythonhosted.org/packages/85/d8/06ee3bc8eded4bd7adf8adf0c9ea5f19bf96f7e5e626bfaf7311cde4208a/dulwich-1.2.5-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:a70477c991e96cfe8fdd7c866e7251faf71b38bfeb51d6f27554c9cce1caabf3", size = 1382310, upload-time = "2026-05-28T22:27:02.216Z" }, + { url = "https://files.pythonhosted.org/packages/07/17/a03adf50b9095f9f5d863393f21d585dea39bdc4fdf60788ff3a9407a512/dulwich-1.2.5-cp311-cp311-manylinux_2_28_aarch64.whl", hash = "sha256:9008ef25cabd379cda4fa86000fc38ca14b72afe17db798a8c85c0b2b7ce4d1e", size = 1470993, upload-time = "2026-05-28T22:27:04.075Z" }, + { url = "https://files.pythonhosted.org/packages/60/58/1dc352d2a5e80befe4338af7208febb44bcfd7496b0dde5ac6dacb07b031/dulwich-1.2.5-cp311-cp311-manylinux_2_28_x86_64.whl", hash = "sha256:a5549f4afc973e0a15ea6b0244d57f848d3f3ee13dac557eb311024aebebf128", size = 1497820, upload-time = "2026-05-28T22:27:05.549Z" }, + { url = "https://files.pythonhosted.org/packages/c1/a8/e058959a87e7df7753b112ef66a43ccbc57338c1bbdc23a0edf3833396df/dulwich-1.2.5-cp311-cp311-win32.whl", hash = "sha256:5108acead814d1de8b6262d6d8fb90af7e82f5a4d83788b6b48e39d01800a92f", size = 1066549, upload-time = "2026-05-28T22:27:06.832Z" }, + { url = "https://files.pythonhosted.org/packages/33/91/ff0b444f686718635348986bd73dfce42e947912417893de35de399b878b/dulwich-1.2.5-cp311-cp311-win_amd64.whl", hash = "sha256:5e067b7feceb7034bc99e7c7143a704f1d97d4be7027d9a0aa5a83c0657ff091", size = 1079481, upload-time = "2026-05-28T22:27:08.33Z" }, + { url = "https://files.pythonhosted.org/packages/19/22/4f75770bbe5521cac61c4820ef46d4fbf8c2175d3519ba3d0378d4ba798e/dulwich-1.2.5-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:701a9ecf7a8a44f5e2459e46befa93530cf36a8b1ae3140aefc007db1d7d0207", size = 1396522, upload-time = "2026-05-28T22:27:09.997Z" }, + { url = "https://files.pythonhosted.org/packages/e5/b1/c07c347681c0cf6acd4b189bf6e8d6207c71a1347b7a1e865eb40faa46b9/dulwich-1.2.5-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:2f90d68bfa97c4ca71de7507984365aefe27b6d248cb28dc99644d0f3ae8c60b", size = 1334826, upload-time = "2026-05-28T22:27:11.582Z" }, + { url = "https://files.pythonhosted.org/packages/13/80/6818eb7ce492e18ab2efa92ab901d173b4b0b159e5681c1424f329600c40/dulwich-1.2.5-cp312-cp312-manylinux_2_28_aarch64.whl", hash = "sha256:00b54a1d56ddbacdd8eadd6d4787a51b3a05fefa30eadbf9165fd283a00b90ed", size = 1416616, upload-time = "2026-05-28T22:27:13.195Z" }, + { url = "https://files.pythonhosted.org/packages/14/a7/9790e60d19870f6554f7583722bb324c1355784316f20aeda1c0b5b1491a/dulwich-1.2.5-cp312-cp312-manylinux_2_28_x86_64.whl", hash = "sha256:d8f7ea8f47e38e5b0de3fab97e07e9c9161ffddc90b3964512cab2b7749df4e6", size = 1441354, upload-time = "2026-05-28T22:27:14.683Z" }, + { url = "https://files.pythonhosted.org/packages/91/44/0ea8a69c24aa1254ff5996d682eae2eab287d471b937dcdb26d9ea9720b4/dulwich-1.2.5-cp312-cp312-win32.whl", hash = "sha256:8929134acf4ff967203df7600b38535f9b5b590462067a7e30dbce01acb97af9", size = 1017058, upload-time = "2026-05-28T22:27:16.121Z" }, + { url = "https://files.pythonhosted.org/packages/bd/9c/2fcddda7faec3bae52db7c64bfcb5dc756f597f33fae90e8d4e4b4d3b39b/dulwich-1.2.5-cp312-cp312-win_amd64.whl", hash = "sha256:9693d2c9e226b2ea855c1dc3a87e2f4d972f7523fc0f7924e5997e9f4c23d97f", size = 1031731, upload-time = "2026-05-28T22:27:17.633Z" }, + { url = "https://files.pythonhosted.org/packages/07/4b/4a18a59ad230581cd0ef460e96001f90762e566dc2dfdba22aa358eb5a0e/dulwich-1.2.5-py3-none-any.whl", hash = "sha256:1679b376433a0fc7f36586afda1d4ed7427afa7a79d4bf17e5014474eea69fa4", size = 686745, upload-time = "2026-05-28T22:27:53.695Z" }, ] [[package]] @@ -2824,6 +2880,11 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/83/1d/d6466de3a5249d35e832a52834115ca9d1d0de6abc22065f049707516d47/google_auth-2.48.0-py3-none-any.whl", hash = "sha256:2e2a537873d449434252a9632c28bfc268b0adb1e53f9fb62afc5333a975903f", size = 236499, upload-time = "2026-01-26T19:22:45.099Z" }, ] +[package.optional-dependencies] +requests = [ + { name = "requests" }, +] + [[package]] name = "google-auth-httplib2" version = "0.2.0" @@ -2850,6 +2911,46 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/ca/94/24b010493660dd55e2d9769ae7ef44164aebd7e1f4a9266cf9459affd687/google_cloud_access_context_manager-0.3.0-py3-none-any.whl", hash = "sha256:5d15ad51547f06c281e35f16b4ffcb3e98bb2d898b01470f88b94edfb2eeb0a3", size = 58852, upload-time = "2025-10-17T02:30:33.768Z" }, ] +[[package]] +name = "google-cloud-aiplatform" +version = "1.153.1" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "docstring-parser" }, + { name = "google-api-core", extra = ["grpc"] }, + { name = "google-auth" }, + { name = "google-cloud-bigquery" }, + { name = "google-cloud-resource-manager" }, + { name = "google-cloud-storage" }, + { name = "google-genai" }, + { name = "packaging" }, + { name = "proto-plus" }, + { name = "protobuf" }, + { name = "pydantic" }, + { name = "typing-extensions" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/d5/97/1779e66ab845550bc602364311ea093ba156cb805a1c31b7c4d6f25b5863/google_cloud_aiplatform-1.153.1.tar.gz", hash = "sha256:445b6c683d5c630f174d81ae1f69f7da9e27e4d4ec5b70c5fe96de5c1247cfbc", size = 11011349, upload-time = "2026-05-15T06:34:14.851Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/16/01/8a1900e7a742ed480e6037ac4f6541466cb981d81bd4cbd34a9d46204ea1/google_cloud_aiplatform-1.153.1-py2.py3-none-any.whl", hash = "sha256:033fa1595a7e8ed1d97066e261e630f38fbc60e10c98c6487cf228fe9c7ec151", size = 9170782, upload-time = "2026-05-15T06:34:10.887Z" }, +] + +[[package]] +name = "google-cloud-artifact-registry" +version = "1.21.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-api-core", extra = ["grpc"] }, + { name = "google-auth" }, + { name = "grpc-google-iam-v1" }, + { name = "grpcio" }, + { name = "proto-plus" }, + { name = "protobuf" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/13/2b/24e6956789bc1244efb18143aa4f124e03d870228e5bfd065c04d38a4d6b/google_cloud_artifact_registry-1.21.0.tar.gz", hash = "sha256:546e51eb5d463a6e5c668be6727d14f8ec82bc798031398006b2213d703e184c", size = 315219, upload-time = "2026-03-30T22:50:38.875Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/e1/8c/a5c68031728f38d3306bad5ac10c0ca670cbdf414db308ddefa2c47f2b34/google_cloud_artifact_registry-1.21.0-py3-none-any.whl", hash = "sha256:a07079035438fd0f2e7264d4318b388650495f011db575405c18c9881449025c", size = 250544, upload-time = "2026-03-30T22:48:49.345Z" }, +] + [[package]] name = "google-cloud-asset" version = "4.2.0" @@ -2870,6 +2971,37 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/05/88/9a43fae1d2fed94d7f5f46b6f4c44bd15e5ea0e8657632108b5ec5f53d9d/google_cloud_asset-4.2.0-py3-none-any.whl", hash = "sha256:fd7ea04c64948a4779790343204cd5b41d4772d6ab1d05a9125e28a637ac0862", size = 282707, upload-time = "2026-01-09T14:53:03.081Z" }, ] +[[package]] +name = "google-cloud-bigquery" +version = "3.41.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-api-core", extra = ["grpc"] }, + { name = "google-auth" }, + { name = "google-cloud-core" }, + { name = "google-resumable-media" }, + { name = "packaging" }, + { name = "python-dateutil" }, + { name = "requests" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/ce/13/6515c7aab55a4a0cf708ffd309fb9af5bab54c13e32dc22c5acd6497193c/google_cloud_bigquery-3.41.0.tar.gz", hash = "sha256:2217e488b47ed576360c9b2cc07d59d883a54b83167c0ef37f915c26b01a06fe", size = 513434, upload-time = "2026-03-30T22:50:55.347Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/40/33/1d3902efadef9194566d499d61507e1f038454e0b55499d2d7f8ab2a4fee/google_cloud_bigquery-3.41.0-py3-none-any.whl", hash = "sha256:2a5b5a737b401cbd824a6e5eac7554100b878668d908e6548836b5d8aaa4dcaa", size = 262343, upload-time = "2026-03-30T22:48:45.444Z" }, +] + +[[package]] +name = "google-cloud-core" +version = "2.6.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-api-core" }, + { name = "google-auth" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/a8/dd/1eef226e470369b26824a505c34482c0b493bc35fe8e0c6b003b5feca21a/google_cloud_core-2.6.0.tar.gz", hash = "sha256:e76149739f90fac1fc6757c09f47eaccb3145b54adbd7759b0f7c4b235f46c83", size = 36001, upload-time = "2026-05-07T08:04:04.124Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/84/4a/98da8930ab109c73d9a5d13782a9ebb81ea8c111f6d534a567b71d23e52b/google_cloud_core-2.6.0-py3-none-any.whl", hash = "sha256:6d63ac8e5eca6d9e4319d0a1e2265fadcd7f1049904378caecfa01cf52dd869e", size = 29390, upload-time = "2026-05-07T08:02:34.672Z" }, +] + [[package]] name = "google-cloud-org-policy" version = "1.16.0" @@ -2919,6 +3051,93 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/94/ff/4b28bcc791d9d7e4ac8fea00fbd90ccb236afda56746a3b4564d2ae45df3/google_cloud_resource_manager-1.16.0-py3-none-any.whl", hash = "sha256:fb9a2ad2b5053c508e1c407ac31abfd1a22e91c32876c1892830724195819a28", size = 400218, upload-time = "2026-01-15T13:02:47.378Z" }, ] +[[package]] +name = "google-cloud-run" +version = "0.16.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-api-core", extra = ["grpc"] }, + { name = "google-auth" }, + { name = "grpc-google-iam-v1" }, + { name = "grpcio" }, + { name = "proto-plus" }, + { name = "protobuf" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/b7/89/dcaf0dc97e39b41e446456ceb60657ab025de79cfccd39cbd739d1a9849e/google_cloud_run-0.16.0.tar.gz", hash = "sha256:d52cf4e6ad3702ae48caccf6abcab543afee6f61c2a6ec753cc62a31e5b629f1", size = 514452, upload-time = "2026-03-26T22:17:05.589Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/fa/c7/46153dc13713b5e4276d86f28ff4563332f9e4bae5ebc83abc5bfd994801/google_cloud_run-0.16.0-py3-none-any.whl", hash = "sha256:d7d2dd7307130fde2a0ce27e96d580dd23b7b2d973b6484b94d902e6b2618860", size = 459112, upload-time = "2026-03-26T22:16:00.018Z" }, +] + +[[package]] +name = "google-cloud-storage" +version = "3.10.1" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-api-core" }, + { name = "google-auth" }, + { name = "google-cloud-core" }, + { name = "google-crc32c" }, + { name = "google-resumable-media" }, + { name = "requests" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/4c/47/205eb8e9a1739b5345843e5a425775cbdc472cc38e7eda082ba5b8d02450/google_cloud_storage-3.10.1.tar.gz", hash = "sha256:97db9aa4460727982040edd2bd13ff3d5e2260b5331ad22895802da1fc2a5286", size = 17309950, upload-time = "2026-03-23T09:35:23.409Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/ad/ff/ca9ab2417fa913d75aae38bf40bf856bb2749a604b2e0f701b37cfcd23cc/google_cloud_storage-3.10.1-py3-none-any.whl", hash = "sha256:a72f656759b7b99bda700f901adcb3425a828d4a29f911bc26b3ea79c5b1217f", size = 324453, upload-time = "2026-03-23T09:35:21.368Z" }, +] + +[[package]] +name = "google-crc32c" +version = "1.8.0" +source = { registry = "https://pypi.org/simple" } +sdist = { url = "https://files.pythonhosted.org/packages/03/41/4b9c02f99e4c5fb477122cd5437403b552873f014616ac1d19ac8221a58d/google_crc32c-1.8.0.tar.gz", hash = "sha256:a428e25fb7691024de47fecfbff7ff957214da51eddded0da0ae0e0f03a2cf79", size = 14192, upload-time = "2025-12-16T00:35:25.142Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/5d/ef/21ccfaab3d5078d41efe8612e0ed0bfc9ce22475de074162a91a25f7980d/google_crc32c-1.8.0-cp311-cp311-macosx_12_0_arm64.whl", hash = "sha256:014a7e68d623e9a4222d663931febc3033c5c7c9730785727de2a81f87d5bab8", size = 31298, upload-time = "2025-12-16T00:20:32.241Z" }, + { url = "https://files.pythonhosted.org/packages/c5/b8/f8413d3f4b676136e965e764ceedec904fe38ae8de0cdc52a12d8eb1096e/google_crc32c-1.8.0-cp311-cp311-macosx_12_0_x86_64.whl", hash = "sha256:86cfc00fe45a0ac7359e5214a1704e51a99e757d0272554874f419f79838c5f7", size = 30872, upload-time = "2025-12-16T00:33:58.785Z" }, + { url = "https://files.pythonhosted.org/packages/f6/fd/33aa4ec62b290477181c55bb1c9302c9698c58c0ce9a6ab4874abc8b0d60/google_crc32c-1.8.0-cp311-cp311-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:19b40d637a54cb71e0829179f6cb41835f0fbd9e8eb60552152a8b52c36cbe15", size = 33243, upload-time = "2025-12-16T00:40:21.46Z" }, + { url = "https://files.pythonhosted.org/packages/71/03/4820b3bd99c9653d1a5210cb32f9ba4da9681619b4d35b6a052432df4773/google_crc32c-1.8.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:17446feb05abddc187e5441a45971b8394ea4c1b6efd88ab0af393fd9e0a156a", size = 33608, upload-time = "2025-12-16T00:40:22.204Z" }, + { url = "https://files.pythonhosted.org/packages/7c/43/acf61476a11437bf9733fb2f70599b1ced11ec7ed9ea760fdd9a77d0c619/google_crc32c-1.8.0-cp311-cp311-win_amd64.whl", hash = "sha256:71734788a88f551fbd6a97be9668a0020698e07b2bf5b3aa26a36c10cdfb27b2", size = 34439, upload-time = "2025-12-16T00:35:20.458Z" }, + { url = "https://files.pythonhosted.org/packages/e9/5f/7307325b1198b59324c0fa9807cafb551afb65e831699f2ce211ad5c8240/google_crc32c-1.8.0-cp312-cp312-macosx_12_0_arm64.whl", hash = "sha256:4b8286b659c1335172e39563ab0a768b8015e88e08329fa5321f774275fc3113", size = 31300, upload-time = "2025-12-16T00:21:56.723Z" }, + { url = "https://files.pythonhosted.org/packages/21/8e/58c0d5d86e2220e6a37befe7e6a94dd2f6006044b1a33edf1ff6d9f7e319/google_crc32c-1.8.0-cp312-cp312-macosx_12_0_x86_64.whl", hash = "sha256:2a3dc3318507de089c5384cc74d54318401410f82aa65b2d9cdde9d297aca7cb", size = 30867, upload-time = "2025-12-16T00:38:31.302Z" }, + { url = "https://files.pythonhosted.org/packages/ce/a9/a780cc66f86335a6019f557a8aaca8fbb970728f0efd2430d15ff1beae0e/google_crc32c-1.8.0-cp312-cp312-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:14f87e04d613dfa218d6135e81b78272c3b904e2a7053b841481b38a7d901411", size = 33364, upload-time = "2025-12-16T00:40:22.96Z" }, + { url = "https://files.pythonhosted.org/packages/21/3f/3457ea803db0198c9aaca2dd373750972ce28a26f00544b6b85088811939/google_crc32c-1.8.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:cb5c869c2923d56cb0c8e6bcdd73c009c36ae39b652dbe46a05eb4ef0ad01454", size = 33740, upload-time = "2025-12-16T00:40:23.96Z" }, + { url = "https://files.pythonhosted.org/packages/df/c0/87c2073e0c72515bb8733d4eef7b21548e8d189f094b5dad20b0ecaf64f6/google_crc32c-1.8.0-cp312-cp312-win_amd64.whl", hash = "sha256:3cc0c8912038065eafa603b238abf252e204accab2a704c63b9e14837a854962", size = 34437, upload-time = "2025-12-16T00:35:21.395Z" }, + { url = "https://files.pythonhosted.org/packages/52/c5/c171e4d8c44fec1422d801a6d2e5d7ddabd733eeda505c79730ee9607f07/google_crc32c-1.8.0-pp311-pypy311_pp73-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:87fa445064e7db928226b2e6f0d5304ab4cd0339e664a4e9a25029f384d9bb93", size = 28615, upload-time = "2025-12-16T00:40:29.298Z" }, + { url = "https://files.pythonhosted.org/packages/9c/97/7d75fe37a7a6ed171a2cf17117177e7aab7e6e0d115858741b41e9dd4254/google_crc32c-1.8.0-pp311-pypy311_pp73-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:f639065ea2042d5c034bf258a9f085eaa7af0cd250667c0635a3118e8f92c69c", size = 28800, upload-time = "2025-12-16T00:40:30.322Z" }, +] + +[[package]] +name = "google-genai" +version = "1.68.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "anyio" }, + { name = "distro" }, + { name = "google-auth", extra = ["requests"] }, + { name = "httpx" }, + { name = "pydantic" }, + { name = "requests" }, + { name = "sniffio" }, + { name = "tenacity" }, + { name = "typing-extensions" }, + { name = "websockets" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/9c/2c/f059982dbcb658cc535c81bbcbe7e2c040d675f4b563b03cdb01018a4bc3/google_genai-1.68.0.tar.gz", hash = "sha256:ac30c0b8bc630f9372993a97e4a11dae0e36f2e10d7c55eacdca95a9fa14ca96", size = 511285, upload-time = "2026-03-18T01:03:18.243Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/84/de/7d3ee9c94b74c3578ea4f88d45e8de9405902f857932334d81e89bce3dfa/google_genai-1.68.0-py3-none-any.whl", hash = "sha256:a1bc9919c0e2ea2907d1e319b65471d3d6d58c54822039a249fe1323e4178d15", size = 750912, upload-time = "2026-03-18T01:03:15.983Z" }, +] + +[[package]] +name = "google-resumable-media" +version = "2.9.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "google-crc32c" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/00/4b/0b235beccc310d0a48adbc7246b719d173cca6c88c572dfa4b090e39143c/google_resumable_media-2.9.0.tar.gz", hash = "sha256:f7cfb224846a9dd444d125115dfbe8ef02a2b893e78f087762fe716a255a734b", size = 2164534, upload-time = "2026-05-07T08:04:44.236Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/07/73/3518e63deb1667c5409a4579e28daf5e84479a87a72c547e0487f7883dcd/google_resumable_media-2.9.0-py3-none-any.whl", hash = "sha256:c8901e88e389af8bed64d9696c74d8bad961865eb2236e13e0bfca9bb0a65ca3", size = 81507, upload-time = "2026-05-07T08:03:23.809Z" }, +] + [[package]] name = "googleapis-common-protos" version = "1.72.0" @@ -2980,6 +3199,17 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/c8/ab/717c58343cf02c5265b531384b248787e04d8160b8afe53d9eec053d7b44/greenlet-3.3.1-cp312-cp312-win_arm64.whl", hash = "sha256:bfb2d1763d777de5ee495c85309460f6fd8146e50ec9d0ae0183dbf6f0a829d1", size = 226403, upload-time = "2026-01-23T15:31:39.372Z" }, ] +[[package]] +name = "gripcontrol" +version = "4.4.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "pubcontrol" }, + { name = "pyjwt", extra = ["crypto"] }, + { name = "six" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/4f/51/1cbf88384fbe97a1454fb0adddcdca8cb90ceb99c3250274c334db844f4f/gripcontrol-4.4.0.tar.gz", hash = "sha256:44ee6fe244a02870aa4e5bc810138ccaf5070dce5eb149b8ee9e27b960a95c2d", size = 12526, upload-time = "2026-05-14T21:19:28.49Z" } + [[package]] name = "grpc-google-iam-v1" version = "0.14.3" @@ -3041,14 +3271,14 @@ wheels = [ [[package]] name = "gunicorn" -version = "23.0.0" +version = "26.0.0" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "packaging" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/34/72/9614c465dc206155d93eff0ca20d42e1e35afc533971379482de953521a4/gunicorn-23.0.0.tar.gz", hash = "sha256:f014447a0101dc57e294f6c18ca6b40227a4c90e9bdb586042628030cba004ec", size = 375031, upload-time = "2024-08-10T20:25:27.378Z" } +sdist = { url = "https://files.pythonhosted.org/packages/6d/b7/a4a3f632f823e432ce6bc65f62961b7980c898c77f075a2f7118cb3846fe/gunicorn-26.0.0.tar.gz", hash = "sha256:ca9346f85e3a4aeeb64d491045c16b9a35647abd37ea15efe53080eb8b090baf", size = 727286, upload-time = "2026-05-05T06:38:25.529Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/cb/7d/6dac2a6e1eba33ee43f318edbed4ff29151a49b5d37f080aad1e6469bca4/gunicorn-23.0.0-py3-none-any.whl", hash = "sha256:ec400d38950de4dfd418cff8328b2c8faed0edb0d517d3394e457c317908ca4d", size = 85029, upload-time = "2024-08-10T20:25:24.996Z" }, + { url = "https://files.pythonhosted.org/packages/e6/40/9c2384fc2be4ad25dd4a49decd5ad9ea5a3639814c11bd40ab77cb9f0a14/gunicorn-26.0.0-py3-none-any.whl", hash = "sha256:40233d26a5f0d1872916188c276e21641155111c2853f0c2cd55260aec0d24fc", size = 212009, upload-time = "2026-05-05T06:38:23.007Z" }, ] [[package]] @@ -3150,20 +3380,20 @@ wheels = [ [[package]] name = "iamdata" -version = "0.1.202602021" +version = "0.1.202605131" source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/93/5e/8179963b7a528c548824a8e4088150509d9fa8571dd622b7399f6d2d5680/iamdata-0.1.202602021.tar.gz", hash = "sha256:c24265fc3694076f65da91a8aa9361b60da25f7b8cfd8ba4ddd6aa1b9bb5153e", size = 771233, upload-time = "2026-02-02T05:49:56.76Z" } +sdist = { url = "https://files.pythonhosted.org/packages/cc/ea/d68e25aa4392e8a9f8e6523adc95a5fb86baf98d052efa2cec4d4a00e7ce/iamdata-0.1.202605131.tar.gz", hash = "sha256:ab4e8f1ea080394157848fecd0ca643633e35b2e0cb1965c9ed9bdd673afe00c", size = 793465, upload-time = "2026-05-13T05:57:10.607Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/74/9e/ae7a3019aa5a27d70412b74da4f0304695efa5d9a88f0689f37ea2602ea2/iamdata-0.1.202602021-py3-none-any.whl", hash = "sha256:48419662d75dd0e1ea22b9cc98fd70201d4c72760c6897acc46ad9ab90633d18", size = 1226614, upload-time = "2026-02-02T05:49:54.735Z" }, + { url = "https://files.pythonhosted.org/packages/f6/93/03396b477b0faa9f1a12142209b59aa13d0fe4f64e2be47883f607789c14/iamdata-0.1.202605131-py3-none-any.whl", hash = "sha256:350e317d96fb8c8ddf30aa6da222788d302af5f13c9e357b59f9eefe50b8af5a", size = 1259166, upload-time = "2026-05-13T05:57:09.093Z" }, ] [[package]] name = "idna" -version = "3.11" +version = "3.15" source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/6f/6d/0703ccc57f3a7233505399edb88de3cbd678da106337b9fcde432b65ed60/idna-3.11.tar.gz", hash = "sha256:795dafcc9c04ed0c1fb032c2aa73654d8e8c5023a7df64a53f39190ada629902", size = 194582, upload-time = "2025-10-12T14:55:20.501Z" } +sdist = { url = "https://files.pythonhosted.org/packages/82/77/7b3966d0b9d1d31a36ddf1746926a11dface89a83409bf1483f0237aa758/idna-3.15.tar.gz", hash = "sha256:ca962446ea538f7092a95e057da437618e886f4d349216d2b1e294abfdb65fdc", size = 199245, upload-time = "2026-05-12T22:45:57.011Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/0e/61/66938bbb5fc52dbdf84594873d5b51fb1f7c7794e9c0f5bd885f30bc507b/idna-3.11-py3-none-any.whl", hash = "sha256:771a87f49d9defaf64091e6e6fe9c18d4833f140bd19464795bc32d966ca37ea", size = 71008, upload-time = "2025-10-12T14:55:18.883Z" }, + { url = "https://files.pythonhosted.org/packages/d2/23/408243171aa9aaba178d3e2559159c24c1171a641aa83b67bdd3394ead8e/idna-3.15-py3-none-any.whl", hash = "sha256:048adeaf8c2d788c40fee287673ccaa74c24ffd8dcf09ffa555a2fbb59f10ac8", size = 72340, upload-time = "2026-05-12T22:45:55.733Z" }, ] [[package]] @@ -3382,6 +3612,19 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/dd/99/76476a1057b349c860bae72e45d6ef438feb877c84ee7d565faf464e54c3/keystoneauth1-5.13.0-py3-none-any.whl", hash = "sha256:5ab81412eb0923ceb9c602cc3decce514b399523cb83d16b409ed3b0f9b03d41", size = 343585, upload-time = "2026-01-19T10:47:00.762Z" }, ] +[[package]] +name = "kingfisher-bin" +version = "1.104.0" +source = { registry = "https://pypi.org/simple" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/1e/2b/324212f1baf482a7d4b66a2edf33073336735b67bb6b04a38d18fd9e67fb/kingfisher_bin-1.104.0-py3-none-macosx_10_9_x86_64.whl", hash = "sha256:8e3840e67004a971fef80aba240ee5c3c5f7a3a343a6d1083a2751aaf866d5d3", size = 14057606, upload-time = "2026-06-22T03:03:01.419Z" }, + { url = "https://files.pythonhosted.org/packages/21/0a/cbf964da5102657cb9be4a59db7c9f7807ef88f9419673b7486daba785d3/kingfisher_bin-1.104.0-py3-none-macosx_11_0_arm64.whl", hash = "sha256:b838313411fa2166a318a45aec2cfcc238e2f30f5292e309ca1129a73180c851", size = 12468386, upload-time = "2026-06-22T03:03:03.951Z" }, + { url = "https://files.pythonhosted.org/packages/0b/a0/cc7ef0ac28f147cdfc9d80e4239fff11c1329831c6f57510c929e848753c/kingfisher_bin-1.104.0-py3-none-manylinux_2_17_aarch64.musllinux_1_2_aarch64.whl", hash = "sha256:0a94abbf2154ef8a3b4845cc0240e2321cdc19e0f5c7f585ea5252e76b242f68", size = 13943188, upload-time = "2026-06-22T03:03:06.378Z" }, + { url = "https://files.pythonhosted.org/packages/17/79/827cfd7787885798a00b5ab905bdc866ef6f8deeff0f708679b06bc9baaa/kingfisher_bin-1.104.0-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl", hash = "sha256:f381274b946f7f68ed72911770fff72024f2192c6e2e2158f2a7fbfda8c482fb", size = 14757594, upload-time = "2026-06-22T03:03:08.66Z" }, + { url = "https://files.pythonhosted.org/packages/da/93/b0061fc69cd10382f647f9266823f213fd0b3f168f8b5bd9151a2370abb1/kingfisher_bin-1.104.0-py3-none-win_amd64.whl", hash = "sha256:f228d0dd61a738673b1c536e965a5661a83b1ee6ca64186a46ba6ea81ab4fd0b", size = 27697957, upload-time = "2026-06-22T03:03:11.268Z" }, + { url = "https://files.pythonhosted.org/packages/a5/fb/f062665b4eb3f77e799cb6335e56bc2945aea83787888a6c1ab329858d0a/kingfisher_bin-1.104.0-py3-none-win_arm64.whl", hash = "sha256:a7774d9d11815ca946bd80b8c9df0f1d39c36cb5a21def3323b99d148dc63065", size = 26063704, upload-time = "2026-06-22T03:03:14.08Z" }, +] + [[package]] name = "kiwisolver" version = "1.4.9" @@ -3475,6 +3718,20 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/08/10/9f8af3e6f569685ce3af7faab51c8dd9d93b9c38eba339ca31c746119447/kubernetes-32.0.1-py2.py3-none-any.whl", hash = "sha256:35282ab8493b938b08ab5526c7ce66588232df00ef5e1dbe88a419107dc10998", size = 1988070, upload-time = "2025-02-18T21:06:31.391Z" }, ] +[[package]] +name = "linode-api4" +version = "5.45.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "deprecated" }, + { name = "polling" }, + { name = "requests" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/b2/b5/fce03d9b81008dcc0fe4961ce10e140ac3ae5ab17f2cdd659763e4964c0d/linode_api4-5.45.0.tar.gz", hash = "sha256:af8a0a5638345ad467447112dcf5d58ec47e7dd192b89ce0c8537a1e5c435d04", size = 283375, upload-time = "2026-06-11T18:05:13.671Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/18/38/19e3c8f7b7a9dbeea2aa5af61f70162bff5131b3d39acbe73e8d0dd12972/linode_api4-5.45.0-py3-none-any.whl", hash = "sha256:3cc2650b13d8d3bc7735fa8e92a639669618f320471dc8e519db778c6020eacd", size = 158336, upload-time = "2026-06-11T18:05:11.799Z" }, +] + [[package]] name = "lxml" version = "6.1.0" @@ -3966,30 +4223,30 @@ wheels = [ [[package]] name = "numpy" -version = "2.0.2" +version = "2.2.6" source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/a9/75/10dd1f8116a8b796cb2c737b674e02d02e80454bda953fa7e65d8c12b016/numpy-2.0.2.tar.gz", hash = "sha256:883c987dee1880e2a864ab0dc9892292582510604156762362d9326444636e78", size = 18902015, upload-time = "2024-08-26T20:19:40.945Z" } +sdist = { url = "https://files.pythonhosted.org/packages/76/21/7d2a95e4bba9dc13d043ee156a356c0a8f0c6309dff6b21b4d71a073b8a8/numpy-2.2.6.tar.gz", hash = "sha256:e29554e2bef54a90aa5cc07da6ce955accb83f21ab5de01a62c8478897b264fd", size = 20276440, upload-time = "2025-05-17T22:38:04.611Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/8b/cf/034500fb83041aa0286e0fb16e7c76e5c8b67c0711bb6e9e9737a717d5fe/numpy-2.0.2-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:49ca4decb342d66018b01932139c0961a8f9ddc7589611158cb3c27cbcf76448", size = 21169137, upload-time = "2024-08-26T20:07:45.345Z" }, - { url = "https://files.pythonhosted.org/packages/4a/d9/32de45561811a4b87fbdee23b5797394e3d1504b4a7cf40c10199848893e/numpy-2.0.2-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:11a76c372d1d37437857280aa142086476136a8c0f373b2e648ab2c8f18fb195", size = 13703552, upload-time = "2024-08-26T20:08:06.666Z" }, - { url = "https://files.pythonhosted.org/packages/c1/ca/2f384720020c7b244d22508cb7ab23d95f179fcfff33c31a6eeba8d6c512/numpy-2.0.2-cp311-cp311-macosx_14_0_arm64.whl", hash = "sha256:807ec44583fd708a21d4a11d94aedf2f4f3c3719035c76a2bbe1fe8e217bdc57", size = 5298957, upload-time = "2024-08-26T20:08:15.83Z" }, - { url = "https://files.pythonhosted.org/packages/0e/78/a3e4f9fb6aa4e6fdca0c5428e8ba039408514388cf62d89651aade838269/numpy-2.0.2-cp311-cp311-macosx_14_0_x86_64.whl", hash = "sha256:8cafab480740e22f8d833acefed5cc87ce276f4ece12fdaa2e8903db2f82897a", size = 6905573, upload-time = "2024-08-26T20:08:27.185Z" }, - { url = "https://files.pythonhosted.org/packages/a0/72/cfc3a1beb2caf4efc9d0b38a15fe34025230da27e1c08cc2eb9bfb1c7231/numpy-2.0.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a15f476a45e6e5a3a79d8a14e62161d27ad897381fecfa4a09ed5322f2085669", size = 13914330, upload-time = "2024-08-26T20:08:48.058Z" }, - { url = "https://files.pythonhosted.org/packages/ba/a8/c17acf65a931ce551fee11b72e8de63bf7e8a6f0e21add4c937c83563538/numpy-2.0.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:13e689d772146140a252c3a28501da66dfecd77490b498b168b501835041f951", size = 19534895, upload-time = "2024-08-26T20:09:16.536Z" }, - { url = "https://files.pythonhosted.org/packages/ba/86/8767f3d54f6ae0165749f84648da9dcc8cd78ab65d415494962c86fac80f/numpy-2.0.2-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:9ea91dfb7c3d1c56a0e55657c0afb38cf1eeae4544c208dc465c3c9f3a7c09f9", size = 19937253, upload-time = "2024-08-26T20:09:46.263Z" }, - { url = "https://files.pythonhosted.org/packages/df/87/f76450e6e1c14e5bb1eae6836478b1028e096fd02e85c1c37674606ab752/numpy-2.0.2-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:c1c9307701fec8f3f7a1e6711f9089c06e6284b3afbbcd259f7791282d660a15", size = 14414074, upload-time = "2024-08-26T20:10:08.483Z" }, - { url = "https://files.pythonhosted.org/packages/5c/ca/0f0f328e1e59f73754f06e1adfb909de43726d4f24c6a3f8805f34f2b0fa/numpy-2.0.2-cp311-cp311-win32.whl", hash = "sha256:a392a68bd329eafac5817e5aefeb39038c48b671afd242710b451e76090e81f4", size = 6470640, upload-time = "2024-08-26T20:10:19.732Z" }, - { url = "https://files.pythonhosted.org/packages/eb/57/3a3f14d3a759dcf9bf6e9eda905794726b758819df4663f217d658a58695/numpy-2.0.2-cp311-cp311-win_amd64.whl", hash = "sha256:286cd40ce2b7d652a6f22efdfc6d1edf879440e53e76a75955bc0c826c7e64dc", size = 15910230, upload-time = "2024-08-26T20:10:43.413Z" }, - { url = "https://files.pythonhosted.org/packages/45/40/2e117be60ec50d98fa08c2f8c48e09b3edea93cfcabd5a9ff6925d54b1c2/numpy-2.0.2-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:df55d490dea7934f330006d0f81e8551ba6010a5bf035a249ef61a94f21c500b", size = 20895803, upload-time = "2024-08-26T20:11:13.916Z" }, - { url = "https://files.pythonhosted.org/packages/46/92/1b8b8dee833f53cef3e0a3f69b2374467789e0bb7399689582314df02651/numpy-2.0.2-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:8df823f570d9adf0978347d1f926b2a867d5608f434a7cff7f7908c6570dcf5e", size = 13471835, upload-time = "2024-08-26T20:11:34.779Z" }, - { url = "https://files.pythonhosted.org/packages/7f/19/e2793bde475f1edaea6945be141aef6c8b4c669b90c90a300a8954d08f0a/numpy-2.0.2-cp312-cp312-macosx_14_0_arm64.whl", hash = "sha256:9a92ae5c14811e390f3767053ff54eaee3bf84576d99a2456391401323f4ec2c", size = 5038499, upload-time = "2024-08-26T20:11:43.902Z" }, - { url = "https://files.pythonhosted.org/packages/e3/ff/ddf6dac2ff0dd50a7327bcdba45cb0264d0e96bb44d33324853f781a8f3c/numpy-2.0.2-cp312-cp312-macosx_14_0_x86_64.whl", hash = "sha256:a842d573724391493a97a62ebbb8e731f8a5dcc5d285dfc99141ca15a3302d0c", size = 6633497, upload-time = "2024-08-26T20:11:55.09Z" }, - { url = "https://files.pythonhosted.org/packages/72/21/67f36eac8e2d2cd652a2e69595a54128297cdcb1ff3931cfc87838874bd4/numpy-2.0.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:c05e238064fc0610c840d1cf6a13bf63d7e391717d247f1bf0318172e759e692", size = 13621158, upload-time = "2024-08-26T20:12:14.95Z" }, - { url = "https://files.pythonhosted.org/packages/39/68/e9f1126d757653496dbc096cb429014347a36b228f5a991dae2c6b6cfd40/numpy-2.0.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:0123ffdaa88fa4ab64835dcbde75dcdf89c453c922f18dced6e27c90d1d0ec5a", size = 19236173, upload-time = "2024-08-26T20:12:44.049Z" }, - { url = "https://files.pythonhosted.org/packages/d1/e9/1f5333281e4ebf483ba1c888b1d61ba7e78d7e910fdd8e6499667041cc35/numpy-2.0.2-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:96a55f64139912d61de9137f11bf39a55ec8faec288c75a54f93dfd39f7eb40c", size = 19634174, upload-time = "2024-08-26T20:13:13.634Z" }, - { url = "https://files.pythonhosted.org/packages/71/af/a469674070c8d8408384e3012e064299f7a2de540738a8e414dcfd639996/numpy-2.0.2-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:ec9852fb39354b5a45a80bdab5ac02dd02b15f44b3804e9f00c556bf24b4bded", size = 14099701, upload-time = "2024-08-26T20:13:34.851Z" }, - { url = "https://files.pythonhosted.org/packages/d0/3d/08ea9f239d0e0e939b6ca52ad403c84a2bce1bde301a8eb4888c1c1543f1/numpy-2.0.2-cp312-cp312-win32.whl", hash = "sha256:671bec6496f83202ed2d3c8fdc486a8fc86942f2e69ff0e986140339a63bcbe5", size = 6174313, upload-time = "2024-08-26T20:13:45.653Z" }, - { url = "https://files.pythonhosted.org/packages/b2/b5/4ac39baebf1fdb2e72585c8352c56d063b6126be9fc95bd2bb5ef5770c20/numpy-2.0.2-cp312-cp312-win_amd64.whl", hash = "sha256:cfd41e13fdc257aa5778496b8caa5e856dc4896d4ccf01841daee1d96465467a", size = 15606179, upload-time = "2024-08-26T20:14:08.786Z" }, + { url = "https://files.pythonhosted.org/packages/da/a8/4f83e2aa666a9fbf56d6118faaaf5f1974d456b1823fda0a176eff722839/numpy-2.2.6-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:f9f1adb22318e121c5c69a09142811a201ef17ab257a1e66ca3025065b7f53ae", size = 21176963, upload-time = "2025-05-17T21:31:19.36Z" }, + { url = "https://files.pythonhosted.org/packages/b3/2b/64e1affc7972decb74c9e29e5649fac940514910960ba25cd9af4488b66c/numpy-2.2.6-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:c820a93b0255bc360f53eca31a0e676fd1101f673dda8da93454a12e23fc5f7a", size = 14406743, upload-time = "2025-05-17T21:31:41.087Z" }, + { url = "https://files.pythonhosted.org/packages/4a/9f/0121e375000b5e50ffdd8b25bf78d8e1a5aa4cca3f185d41265198c7b834/numpy-2.2.6-cp311-cp311-macosx_14_0_arm64.whl", hash = "sha256:3d70692235e759f260c3d837193090014aebdf026dfd167834bcba43e30c2a42", size = 5352616, upload-time = "2025-05-17T21:31:50.072Z" }, + { url = "https://files.pythonhosted.org/packages/31/0d/b48c405c91693635fbe2dcd7bc84a33a602add5f63286e024d3b6741411c/numpy-2.2.6-cp311-cp311-macosx_14_0_x86_64.whl", hash = "sha256:481b49095335f8eed42e39e8041327c05b0f6f4780488f61286ed3c01368d491", size = 6889579, upload-time = "2025-05-17T21:32:01.712Z" }, + { url = "https://files.pythonhosted.org/packages/52/b8/7f0554d49b565d0171eab6e99001846882000883998e7b7d9f0d98b1f934/numpy-2.2.6-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:b64d8d4d17135e00c8e346e0a738deb17e754230d7e0810ac5012750bbd85a5a", size = 14312005, upload-time = "2025-05-17T21:32:23.332Z" }, + { url = "https://files.pythonhosted.org/packages/b3/dd/2238b898e51bd6d389b7389ffb20d7f4c10066d80351187ec8e303a5a475/numpy-2.2.6-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ba10f8411898fc418a521833e014a77d3ca01c15b0c6cdcce6a0d2897e6dbbdf", size = 16821570, upload-time = "2025-05-17T21:32:47.991Z" }, + { url = "https://files.pythonhosted.org/packages/83/6c/44d0325722cf644f191042bf47eedad61c1e6df2432ed65cbe28509d404e/numpy-2.2.6-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:bd48227a919f1bafbdda0583705e547892342c26fb127219d60a5c36882609d1", size = 15818548, upload-time = "2025-05-17T21:33:11.728Z" }, + { url = "https://files.pythonhosted.org/packages/ae/9d/81e8216030ce66be25279098789b665d49ff19eef08bfa8cb96d4957f422/numpy-2.2.6-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:9551a499bf125c1d4f9e250377c1ee2eddd02e01eac6644c080162c0c51778ab", size = 18620521, upload-time = "2025-05-17T21:33:39.139Z" }, + { url = "https://files.pythonhosted.org/packages/6a/fd/e19617b9530b031db51b0926eed5345ce8ddc669bb3bc0044b23e275ebe8/numpy-2.2.6-cp311-cp311-win32.whl", hash = "sha256:0678000bb9ac1475cd454c6b8c799206af8107e310843532b04d49649c717a47", size = 6525866, upload-time = "2025-05-17T21:33:50.273Z" }, + { url = "https://files.pythonhosted.org/packages/31/0a/f354fb7176b81747d870f7991dc763e157a934c717b67b58456bc63da3df/numpy-2.2.6-cp311-cp311-win_amd64.whl", hash = "sha256:e8213002e427c69c45a52bbd94163084025f533a55a59d6f9c5b820774ef3303", size = 12907455, upload-time = "2025-05-17T21:34:09.135Z" }, + { url = "https://files.pythonhosted.org/packages/82/5d/c00588b6cf18e1da539b45d3598d3557084990dcc4331960c15ee776ee41/numpy-2.2.6-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:41c5a21f4a04fa86436124d388f6ed60a9343a6f767fced1a8a71c3fbca038ff", size = 20875348, upload-time = "2025-05-17T21:34:39.648Z" }, + { url = "https://files.pythonhosted.org/packages/66/ee/560deadcdde6c2f90200450d5938f63a34b37e27ebff162810f716f6a230/numpy-2.2.6-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:de749064336d37e340f640b05f24e9e3dd678c57318c7289d222a8a2f543e90c", size = 14119362, upload-time = "2025-05-17T21:35:01.241Z" }, + { url = "https://files.pythonhosted.org/packages/3c/65/4baa99f1c53b30adf0acd9a5519078871ddde8d2339dc5a7fde80d9d87da/numpy-2.2.6-cp312-cp312-macosx_14_0_arm64.whl", hash = "sha256:894b3a42502226a1cac872f840030665f33326fc3dac8e57c607905773cdcde3", size = 5084103, upload-time = "2025-05-17T21:35:10.622Z" }, + { url = "https://files.pythonhosted.org/packages/cc/89/e5a34c071a0570cc40c9a54eb472d113eea6d002e9ae12bb3a8407fb912e/numpy-2.2.6-cp312-cp312-macosx_14_0_x86_64.whl", hash = "sha256:71594f7c51a18e728451bb50cc60a3ce4e6538822731b2933209a1f3614e9282", size = 6625382, upload-time = "2025-05-17T21:35:21.414Z" }, + { url = "https://files.pythonhosted.org/packages/f8/35/8c80729f1ff76b3921d5c9487c7ac3de9b2a103b1cd05e905b3090513510/numpy-2.2.6-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:f2618db89be1b4e05f7a1a847a9c1c0abd63e63a1607d892dd54668dd92faf87", size = 14018462, upload-time = "2025-05-17T21:35:42.174Z" }, + { url = "https://files.pythonhosted.org/packages/8c/3d/1e1db36cfd41f895d266b103df00ca5b3cbe965184df824dec5c08c6b803/numpy-2.2.6-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:fd83c01228a688733f1ded5201c678f0c53ecc1006ffbc404db9f7a899ac6249", size = 16527618, upload-time = "2025-05-17T21:36:06.711Z" }, + { url = "https://files.pythonhosted.org/packages/61/c6/03ed30992602c85aa3cd95b9070a514f8b3c33e31124694438d88809ae36/numpy-2.2.6-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:37c0ca431f82cd5fa716eca9506aefcabc247fb27ba69c5062a6d3ade8cf8f49", size = 15505511, upload-time = "2025-05-17T21:36:29.965Z" }, + { url = "https://files.pythonhosted.org/packages/b7/25/5761d832a81df431e260719ec45de696414266613c9ee268394dd5ad8236/numpy-2.2.6-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:fe27749d33bb772c80dcd84ae7e8df2adc920ae8297400dabec45f0dedb3f6de", size = 18313783, upload-time = "2025-05-17T21:36:56.883Z" }, + { url = "https://files.pythonhosted.org/packages/57/0a/72d5a3527c5ebffcd47bde9162c39fae1f90138c961e5296491ce778e682/numpy-2.2.6-cp312-cp312-win32.whl", hash = "sha256:4eeaae00d789f66c7a25ac5f34b71a7035bb474e679f410e5e1a94deb24cf2d4", size = 6246506, upload-time = "2025-05-17T21:37:07.368Z" }, + { url = "https://files.pythonhosted.org/packages/36/fa/8c9210162ca1b88529ab76b41ba02d433fd54fecaf6feb70ef9f124683f1/numpy-2.2.6-cp312-cp312-win_amd64.whl", hash = "sha256:c1f9540be57940698ed329904db803cf7a402f3fc200bfe599334c9bd84a40b2", size = 12614190, upload-time = "2025-05-17T21:37:26.213Z" }, ] [[package]] @@ -4031,7 +4288,7 @@ dependencies = [ { name = "pycryptodomex" }, { name = "pydantic" }, { name = "pydash" }, - { name = "pyjwt" }, + { name = "pyjwt", extra = ["crypto"] }, { name = "python-dateutil" }, { name = "pyyaml" }, { name = "requests" }, @@ -4294,6 +4551,12 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/41/f5/65b66420c275e9b26513fdd6d84687403d11ac8be4650b67d1e5572b8f48/policyuniverse-1.5.1.20231109-py2.py3-none-any.whl", hash = "sha256:0b0ece0ee8285af31fc39ce09c82a551ca62e62bc2842e23952503bccb973321", size = 484251, upload-time = "2023-11-30T19:12:43.463Z" }, ] +[[package]] +name = "polling" +version = "0.3.2" +source = { registry = "https://pypi.org/simple" } +sdist = { url = "https://files.pythonhosted.org/packages/8f/c5/4249317962180d97ec7a60fe38aa91f86216533bd478a427a5468945c5c9/polling-0.3.2.tar.gz", hash = "sha256:3afd62320c99b725c70f379964bf548b302fc7f04d4604e6c315d9012309cc9a", size = 5189, upload-time = "2021-05-22T19:48:41.466Z" } + [[package]] name = "portalocker" version = "2.10.1" @@ -4410,8 +4673,8 @@ wheels = [ [[package]] name = "prowler" -version = "5.27.0" -source = { git = "https://github.com/prowler-cloud/prowler.git?rev=master#0abbb7fc590eaf7de6ed354dd5a217bca261d2b0" } +version = "5.35.0" +source = { git = "https://github.com/prowler-cloud/prowler.git?rev=master#f5ea116763aeffede9f399c8934fc280eaccd315" } dependencies = [ { name = "alibabacloud-actiontrail20200706" }, { name = "alibabacloud-credentials" }, @@ -4427,7 +4690,6 @@ dependencies = [ { name = "alibabacloud-tea-openapi" }, { name = "alibabacloud-vpc20160428" }, { name = "alive-progress" }, - { name = "awsipranges" }, { name = "azure-identity" }, { name = "azure-keyvault-keys" }, { name = "azure-mgmt-apimanagement" }, @@ -4463,13 +4725,14 @@ dependencies = [ { name = "dash" }, { name = "dash-bootstrap-components" }, { name = "defusedxml" }, - { name = "detect-secrets" }, { name = "dulwich" }, { name = "google-api-python-client" }, { name = "google-auth-httplib2" }, { name = "h2" }, { name = "jsonschema" }, + { name = "kingfisher-bin" }, { name = "kubernetes" }, + { name = "linode-api4" }, { name = "markdown" }, { name = "microsoft-kiota-abstractions" }, { name = "msgraph-sdk" }, @@ -4484,9 +4747,14 @@ dependencies = [ { name = "pygithub" }, { name = "python-dateutil" }, { name = "pytz" }, + { name = "scaleway" }, { name = "schema" }, { name = "shodan" }, { name = "slack-sdk" }, + { name = "stackit-core" }, + { name = "stackit-iaas" }, + { name = "stackit-objectstorage" }, + { name = "stackit-resourcemanager" }, { name = "tabulate" }, { name = "tzlocal" }, { name = "uuid6" }, @@ -4494,7 +4762,7 @@ dependencies = [ [[package]] name = "prowler-api" -version = "1.29.0" +version = "1.37.0" source = { virtual = "." } dependencies = [ { name = "cartography" }, @@ -4507,6 +4775,7 @@ dependencies = [ { name = "django-celery-results" }, { name = "django-cors-headers" }, { name = "django-environ" }, + { name = "django-eventstream" }, { name = "django-filter" }, { name = "django-guid" }, { name = "django-postgres-extra" }, @@ -4533,6 +4802,8 @@ dependencies = [ { name = "sentry-sdk", extra = ["django"] }, { name = "sqlparse" }, { name = "uuid6" }, + { name = "uvicorn-worker" }, + { name = "uvloop" }, { name = "werkzeug" }, { name = "xmlsec" }, ] @@ -4561,7 +4832,7 @@ dev = [ [package.metadata] requires-dist = [ - { name = "cartography", specifier = "==0.135.0" }, + { name = "cartography", specifier = "==0.138.1" }, { name = "celery", specifier = "==5.6.2" }, { name = "defusedxml", specifier = "==0.7.1" }, { name = "dj-rest-auth", extras = ["with-social", "jwt"], specifier = "==7.0.1" }, @@ -4571,6 +4842,7 @@ requires-dist = [ { name = "django-celery-results", specifier = "==2.6.0" }, { name = "django-cors-headers", specifier = "==4.4.0" }, { name = "django-environ", specifier = "==0.11.2" }, + { name = "django-eventstream", specifier = "==5.3.3" }, { name = "django-filter", specifier = "==24.3" }, { name = "django-guid", specifier = "==3.5.0" }, { name = "django-postgres-extra", specifier = "==2.0.9" }, @@ -4583,7 +4855,7 @@ requires-dist = [ { name = "drf-spectacular-jsonapi", specifier = "==0.5.1" }, { name = "fonttools", specifier = "==4.62.1" }, { name = "gevent", specifier = "==25.9.1" }, - { name = "gunicorn", specifier = "==23.0.0" }, + { name = "gunicorn", specifier = "==26.0.0" }, { name = "h2", specifier = "==4.3.0" }, { name = "lxml", specifier = "==6.1.0" }, { name = "markdown", specifier = "==3.10.2" }, @@ -4597,6 +4869,8 @@ requires-dist = [ { name = "sentry-sdk", extras = ["django"], specifier = "==2.56.0" }, { name = "sqlparse", specifier = "==0.5.5" }, { name = "uuid6", specifier = "==2024.7.10" }, + { name = "uvicorn-worker", specifier = "==0.4.0" }, + { name = "uvloop", specifier = "==0.22.1" }, { name = "werkzeug", specifier = "==3.1.7" }, { name = "xmlsec", specifier = "==1.3.17" }, ] @@ -4618,7 +4892,7 @@ dev = [ { name = "pytest-env", specifier = "==1.1.3" }, { name = "pytest-randomly", specifier = "==3.15.0" }, { name = "pytest-xdist", specifier = "==3.6.1" }, - { name = "ruff", specifier = "==0.5.0" }, + { name = "ruff", specifier = "==0.15.11" }, { name = "tqdm", specifier = "==4.67.1" }, { name = "vulture", specifier = "==2.14" }, ] @@ -4671,6 +4945,16 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/7b/08/9c66c269b0d417a0af9fb969535f0371b8c538633535a7a6a5ca3f9231e2/psycopg2_binary-2.9.9-cp312-cp312-win_amd64.whl", hash = "sha256:81ff62668af011f9a48787564ab7eded4e9fb17a4a6a74af5ffa6a457400d2ab", size = 1163864, upload-time = "2023-10-28T09:37:28.155Z" }, ] +[[package]] +name = "pubcontrol" +version = "3.5.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "pyjwt", extra = ["crypto"] }, + { name = "requests" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/25/6a/02202a247214a6ffd5148ab1b16aca1c334b40dca211bca0442c8b7c7447/pubcontrol-3.5.0.tar.gz", hash = "sha256:a5ec6b3f53edfd005675518e5e4cc23b34122776835ae7c6dbd1db173d1ff0cb", size = 18199, upload-time = "2023-07-05T19:11:40.477Z" } + [[package]] name = "py-deviceid" version = "0.1.1" @@ -4682,14 +4966,14 @@ wheels = [ [[package]] name = "py-iam-expand" -version = "0.1.0" +version = "0.3.0" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "iamdata" }, ] -sdist = { url = "https://files.pythonhosted.org/packages/22/99/8d31a30b37825577275bb3663885b55075fba80257fcd6813b85d3aaffa8/py_iam_expand-0.1.0.tar.gz", hash = "sha256:5a2884dc267ac59a02c3a80fefc0b34c309dac681baa0f87c436067c6cf53a96", size = 10228, upload-time = "2025-04-30T07:15:35.304Z" } +sdist = { url = "https://files.pythonhosted.org/packages/a3/08/f6e11a029b81f0bec4b7b1f18704aadf509a882cc386c90ef1ac043c18cc/py_iam_expand-0.3.0.tar.gz", hash = "sha256:4ccfe25f40ba0633a152c4f86b49cde8972ee3d4b6009b017a4310cc4b9e64c7", size = 10234, upload-time = "2026-02-24T09:47:47.772Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/79/19/482c2e0768cda7afaed07918e4fbd951e2418255fb5d1d9b35b284871716/py_iam_expand-0.1.0-py3-none-any.whl", hash = "sha256:b845ce7b50ac895b02b4f338e09c62a68ea51849794f76e189b02009bd388510", size = 12522, upload-time = "2025-04-30T07:15:33.799Z" }, + { url = "https://files.pythonhosted.org/packages/5a/dd/4056d0bc3d6317039d2dd2ee7cd6a5389575603e270399a8f9f20e11e721/py_iam_expand-0.3.0-py3-none-any.whl", hash = "sha256:94c0a1e9dd60316ce60ddc0cdc9a046119bde335b5bb9593ee29224857860d5a", size = 12527, upload-time = "2026-02-24T09:47:45.602Z" }, ] [[package]] @@ -4873,11 +5157,11 @@ wheels = [ [[package]] name = "pyjwt" -version = "2.12.1" +version = "2.13.0" source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/c2/27/a3b6e5bf6ff856d2509292e95c8f57f0df7017cf5394921fc4e4ef40308a/pyjwt-2.12.1.tar.gz", hash = "sha256:c74a7a2adf861c04d002db713dd85f84beb242228e671280bf709d765b03672b", size = 102564, upload-time = "2026-03-13T19:27:37.25Z" } +sdist = { url = "https://files.pythonhosted.org/packages/3b/81/58d0ac84e1ef3a3843791d6954d94c0b33d526c75eeb1efbce9d0a4c4077/pyjwt-2.13.0.tar.gz", hash = "sha256:41571c89ca91598c79e8ef18a2d07367d4810fbbd6f637794879baf1b7703423", size = 107515, upload-time = "2026-05-21T19:54:36.618Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/e5/7a/8dd906bd22e79e47397a61742927f6747fe93242ef86645ee9092e610244/pyjwt-2.12.1-py3-none-any.whl", hash = "sha256:28ca37c070cad8ba8cd9790cd940535d40274d22f80ab87f3ac6a713e6e8454c", size = 29726, upload-time = "2026-03-13T19:27:35.677Z" }, + { url = "https://files.pythonhosted.org/packages/a3/5e/ecf12fdb62546d64385c158514e9b2b671f7832108ef2ecd2020ce0af2d1/pyjwt-2.13.0-py3-none-any.whl", hash = "sha256:66adcc2aff09b3f1bbd95fc1e1577df8ac8723c978552fd43304c8a290ac5728", size = 31274, upload-time = "2026-05-21T19:54:35.362Z" }, ] [package.optional-dependencies] @@ -5367,27 +5651,27 @@ wheels = [ [[package]] name = "ruff" -version = "0.5.0" +version = "0.15.11" source = { registry = "https://pypi.org/simple" } -sdist = { url = "https://files.pythonhosted.org/packages/28/9a/dde343d95ecd0747207e4e8d143c373ef961cbd6b78c61a659f67582dbd2/ruff-0.5.0.tar.gz", hash = "sha256:eb641b5873492cf9bd45bc9c5ae5320648218e04386a5f0c264ad6ccce8226a1", size = 2587996, upload-time = "2024-06-27T15:42:16.137Z" } +sdist = { url = "https://files.pythonhosted.org/packages/e4/8d/192f3d7103816158dfd5ea50d098ef2aec19194e6cbccd4b3485bdb2eb2d/ruff-0.15.11.tar.gz", hash = "sha256:f092b21708bf0e7437ce9ada249dfe688ff9a0954fc94abab05dcea7dcd29c33", size = 4637264, upload-time = "2026-04-16T18:46:26.58Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/55/5d/0d9510720d61df753df39bf24a96d6c141080c94fe6025568747fbea856a/ruff-0.5.0-py3-none-linux_armv6l.whl", hash = "sha256:ee770ea8ab38918f34e7560a597cc0a8c9a193aaa01bfbd879ef43cb06bd9c4c", size = 9434156, upload-time = "2024-06-27T15:40:40.824Z" }, - { url = "https://files.pythonhosted.org/packages/be/5a/7f466f5449dce168c2d956ad4a207d62dc7b76836d46f1c04249a4daaf34/ruff-0.5.0-py3-none-macosx_10_12_x86_64.whl", hash = "sha256:38f3b8327b3cb43474559d435f5fa65dacf723351c159ed0dc567f7ab735d1b6", size = 8536948, upload-time = "2024-06-27T15:40:47.907Z" }, - { url = "https://files.pythonhosted.org/packages/e2/a2/afc6952d5a0199e7e6c0a2051d6f4780fb70376f5bd07f27838f8bc0cf47/ruff-0.5.0-py3-none-macosx_11_0_arm64.whl", hash = "sha256:7594f8df5404a5c5c8f64b8311169879f6cf42142da644c7e0ba3c3f14130370", size = 8107163, upload-time = "2024-06-27T15:41:06.887Z" }, - { url = "https://files.pythonhosted.org/packages/34/54/ea77237405b7573298f5cc00045d1aceab609841d3cc88de3d7c3d2a6163/ruff-0.5.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:adc7012d6ec85032bc4e9065110df205752d64010bed5f958d25dbee9ce35de3", size = 9877009, upload-time = "2024-06-27T15:41:11.28Z" }, - { url = "https://files.pythonhosted.org/packages/56/db/3f74873bc0ca915f79d26575e549eb5e633022d56315d314e6f9c0fa596a/ruff-0.5.0-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:d505fb93b0fabef974b168d9b27c3960714d2ecda24b6ffa6a87ac432905ea38", size = 9219926, upload-time = "2024-06-27T15:41:15.032Z" }, - { url = "https://files.pythonhosted.org/packages/57/08/1052c80f3f44321631a8c1337e55883dd7a7b02b4efe5c9282258db42358/ruff-0.5.0-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:9dc5cfd3558f14513ed0d5b70ce531e28ea81a8a3b1b07f0f48421a3d9e7d80a", size = 10031146, upload-time = "2024-06-27T15:41:20.601Z" }, - { url = "https://files.pythonhosted.org/packages/8f/a2/f7c01c4a02b87998c9e1379ec8d7345d6a45f8b34e326e8700c13da391c3/ruff-0.5.0-py3-none-manylinux_2_17_ppc64.manylinux2014_ppc64.whl", hash = "sha256:db3ca35265de239a1176d56a464b51557fce41095c37d6c406e658cf80bbb362", size = 10770796, upload-time = "2024-06-27T15:41:24.665Z" }, - { url = "https://files.pythonhosted.org/packages/12/a1/5f45ab0948a202da7fe13c6e0678f907bd88caacc7e4f4909603d3774051/ruff-0.5.0-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:b1a321c4f68809fddd9b282fab6a8d8db796b270fff44722589a8b946925a2a8", size = 10364804, upload-time = "2024-06-27T15:41:29.153Z" }, - { url = "https://files.pythonhosted.org/packages/7e/40/83f88d5bda41496a90871ec82dd82545def4c4683e1c2f4a42f5a168ae3e/ruff-0.5.0-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:2c4dfcd8d34b143916994b3876b63d53f56724c03f8c1a33a253b7b1e6bf2a7d", size = 11241308, upload-time = "2024-06-27T15:41:33.569Z" }, - { url = "https://files.pythonhosted.org/packages/af/79/8a57016a761d11491b913460a3d1545cdbe96dca6acb1279102814c9147b/ruff-0.5.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:81e5facfc9f4a674c6a78c64d38becfbd5e4f739c31fcd9ce44c849f1fad9e4c", size = 10064506, upload-time = "2024-06-27T15:41:38.21Z" }, - { url = "https://files.pythonhosted.org/packages/67/34/fd7cd8be0d8cd4bcce0dbef807933f6c9685d5dc2549b729da7ee7a7a5cc/ruff-0.5.0-py3-none-musllinux_1_2_aarch64.whl", hash = "sha256:e589e27971c2a3efff3fadafb16e5aef7ff93250f0134ec4b52052b673cf988d", size = 9866155, upload-time = "2024-06-27T15:41:42.551Z" }, - { url = "https://files.pythonhosted.org/packages/7b/54/8a654417265fe91de3ff303274a9d4d64774496eaa2eadd7da8e88a48b82/ruff-0.5.0-py3-none-musllinux_1_2_armv7l.whl", hash = "sha256:d2ffbc3715a52b037bcb0f6ff524a9367f642cdc5817944f6af5479bbb2eb50e", size = 9285874, upload-time = "2024-06-27T15:41:46.991Z" }, - { url = "https://files.pythonhosted.org/packages/86/39/564161e306b12ab40d2b6be0a0bc843c692a8295cc7101fa930db89e1e7e/ruff-0.5.0-py3-none-musllinux_1_2_i686.whl", hash = "sha256:cd096e23c6a4f9c819525a437fa0a99d1c67a1b6bb30948d46f33afbc53596cf", size = 9645133, upload-time = "2024-06-27T15:41:52.535Z" }, - { url = "https://files.pythonhosted.org/packages/3b/67/3203d56ee41d3dee8d94c7926b298b13a150f105a55fef38b75ccf5e0901/ruff-0.5.0-py3-none-musllinux_1_2_x86_64.whl", hash = "sha256:46e193b36f2255729ad34a49c9a997d506e58f08555366b2108783b3064a0e1e", size = 10143022, upload-time = "2024-06-27T15:41:56.879Z" }, - { url = "https://files.pythonhosted.org/packages/71/2e/1bab3c5a3929f348cdc086a3f3013ea0b8823ec3d273f3334ef621f4f83f/ruff-0.5.0-py3-none-win32.whl", hash = "sha256:49141d267100f5ceff541b4e06552e98527870eafa1acc9dec9139c9ec5af64c", size = 7735210, upload-time = "2024-06-27T15:42:02.173Z" }, - { url = "https://files.pythonhosted.org/packages/48/05/04bf25784ba73abf0e639065fd7a785c005c895c4bf64aa2729d26a1984f/ruff-0.5.0-py3-none-win_amd64.whl", hash = "sha256:e9118f60091047444c1b90952736ee7b1792910cab56e9b9a9ac20af94cd0440", size = 8536440, upload-time = "2024-06-27T15:42:08.275Z" }, - { url = "https://files.pythonhosted.org/packages/63/ab/a10ab4a751514d4f954079fbd2f645cc0c5982a18f510ab411048a2a5409/ruff-0.5.0-py3-none-win_arm64.whl", hash = "sha256:ed5c4df5c1fb4518abcb57725b576659542bdbe93366f4f329e8f398c4b71178", size = 7949476, upload-time = "2024-06-27T15:42:12.464Z" }, + { url = "https://files.pythonhosted.org/packages/02/1e/6aca3427f751295ab011828e15e9bf452200ac74484f1db4be0197b8170b/ruff-0.15.11-py3-none-linux_armv6l.whl", hash = "sha256:e927cfff503135c558eb581a0c9792264aae9507904eb27809cdcff2f2c847b7", size = 10607943, upload-time = "2026-04-16T18:46:05.967Z" }, + { url = "https://files.pythonhosted.org/packages/e7/26/1341c262e74f36d4e84f3d6f4df0ac68cd53331a66bfc5080daa17c84c0b/ruff-0.15.11-py3-none-macosx_10_12_x86_64.whl", hash = "sha256:7a1b5b2938d8f890b76084d4fa843604d787a912541eae85fd7e233398bbb73e", size = 10988592, upload-time = "2026-04-16T18:46:00.742Z" }, + { url = "https://files.pythonhosted.org/packages/03/71/850b1d6ffa9564fbb6740429bad53df1094082fe515c8c1e74b6d8d05f18/ruff-0.15.11-py3-none-macosx_11_0_arm64.whl", hash = "sha256:d4176f3d194afbdaee6e41b9ccb1a2c287dba8700047df474abfbe773825d1cb", size = 10338501, upload-time = "2026-04-16T18:46:03.723Z" }, + { url = "https://files.pythonhosted.org/packages/f2/11/cc1284d3e298c45a817a6aadb6c3e1d70b45c9b36d8d9cce3387b495a03a/ruff-0.15.11-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:3b17c886fb88203ced3afe7f14e8d5ae96e9d2f4ccc0ee66aa19f2c2675a27e4", size = 10670693, upload-time = "2026-04-16T18:46:41.941Z" }, + { url = "https://files.pythonhosted.org/packages/ce/9e/f8288b034ab72b371513c13f9a41d9ba3effac54e24bfb467b007daee2ca/ruff-0.15.11-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:49fafa220220afe7758a487b048de4c8f9f767f37dfefad46b9dd06759d003eb", size = 10416177, upload-time = "2026-04-16T18:46:21.717Z" }, + { url = "https://files.pythonhosted.org/packages/85/71/504d79abfd3d92532ba6bbe3d1c19fada03e494332a59e37c7c2dabae427/ruff-0.15.11-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:f2ab8427e74a00d93b8bda1307b1e60970d40f304af38bccb218e056c220120d", size = 11221886, upload-time = "2026-04-16T18:46:15.086Z" }, + { url = "https://files.pythonhosted.org/packages/43/5a/947e6ab7a5ad603d65b474be15a4cbc6d29832db5d762cd142e4e3a74164/ruff-0.15.11-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:195072c0c8e1fc8f940652073df082e37a5d9cb43b4ab1e4d0566ab8977a13b7", size = 12075183, upload-time = "2026-04-16T18:46:07.944Z" }, + { url = "https://files.pythonhosted.org/packages/9f/a1/0b7bb6268775fdd3a0818aee8efd8f5b4e231d24dd4d528ced2534023182/ruff-0.15.11-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:a3a0996d486af3920dec930a2e7daed4847dfc12649b537a9335585ada163e9e", size = 11516575, upload-time = "2026-04-16T18:46:31.687Z" }, + { url = "https://files.pythonhosted.org/packages/30/c3/bb5168fc4d233cc06e95f482770d0f3c87945a0cd9f614b90ea8dc2f2833/ruff-0.15.11-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:1bef2cb556d509259f1fe440bb9cd33c756222cf0a7afe90d15edf0866702431", size = 11306537, upload-time = "2026-04-16T18:46:36.988Z" }, + { url = "https://files.pythonhosted.org/packages/e4/92/4cfae6441f3967317946f3b788136eecf093729b94d6561f963ed810c82e/ruff-0.15.11-py3-none-manylinux_2_31_riscv64.whl", hash = "sha256:030d921a836d7d4a12cf6e8d984a88b66094ccb0e0f17ddd55067c331191bf19", size = 11296813, upload-time = "2026-04-16T18:46:24.182Z" }, + { url = "https://files.pythonhosted.org/packages/43/26/972784c5dde8313acde8ac71ba8ac65475b85db4a2352a76c9934361f9bc/ruff-0.15.11-py3-none-musllinux_1_2_aarch64.whl", hash = "sha256:0e783b599b4577788dbbb66b9addcef87e9a8832f4ce0c19e34bf55543a2f890", size = 10633136, upload-time = "2026-04-16T18:46:39.802Z" }, + { url = "https://files.pythonhosted.org/packages/5b/53/3985a4f185020c2f367f2e08a103032e12564829742a1b417980ce1514a0/ruff-0.15.11-py3-none-musllinux_1_2_armv7l.whl", hash = "sha256:ae90592246625ba4a34349d68ec28d4400d75182b71baa196ddb9f82db025ef5", size = 10424701, upload-time = "2026-04-16T18:46:10.381Z" }, + { url = "https://files.pythonhosted.org/packages/d3/57/bf0dfb32241b56c83bb663a826133da4bf17f682ba8c096973065f6e6a68/ruff-0.15.11-py3-none-musllinux_1_2_i686.whl", hash = "sha256:1f111d62e3c983ed20e0ca2e800f8d77433a5b1161947df99a5c2a3fb60514f0", size = 10873887, upload-time = "2026-04-16T18:46:29.157Z" }, + { url = "https://files.pythonhosted.org/packages/02/05/e48076b2a57dc33ee8c7a957296f97c744ca891a8ffb4ffb1aaa3b3f517d/ruff-0.15.11-py3-none-musllinux_1_2_x86_64.whl", hash = "sha256:06f483d6646f59eaffba9ae30956370d3a886625f511a3108994000480621d1c", size = 11404316, upload-time = "2026-04-16T18:46:19.462Z" }, + { url = "https://files.pythonhosted.org/packages/88/27/0195d15fe7a897cbcba0904792c4b7c9fdd958456c3a17d2ea6093716a9a/ruff-0.15.11-py3-none-win32.whl", hash = "sha256:476a2aa56b7da0b73a3ee80b6b2f0e19cce544245479adde7baa65466664d5f3", size = 10655535, upload-time = "2026-04-16T18:46:12.47Z" }, + { url = "https://files.pythonhosted.org/packages/3a/5e/c927b325bd4c1d3620211a4b96f47864633199feed60fa936025ab27e090/ruff-0.15.11-py3-none-win_amd64.whl", hash = "sha256:8b6756d88d7e234fb0c98c91511aae3cd519d5e3ed271cae31b20f39cb2a12a3", size = 11779692, upload-time = "2026-04-16T18:46:17.268Z" }, + { url = "https://files.pythonhosted.org/packages/63/b6/aeadee5443e49baa2facd51131159fd6301cc4ccfc1541e4df7b021c37dd/ruff-0.15.11-py3-none-win_arm64.whl", hash = "sha256:063fed18cc1bbe0ee7393957284a6fe8b588c6a406a285af3ee3f46da2391ee4", size = 11032614, upload-time = "2026-04-16T18:46:34.487Z" }, ] [[package]] @@ -5526,6 +5810,67 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/49/4b/359f28a903c13438ef59ebeee215fb25da53066db67b305c125f1c6d2a25/sqlparse-0.5.5-py3-none-any.whl", hash = "sha256:12a08b3bf3eec877c519589833aed092e2444e68240a3577e8e26148acc7b1ba", size = 46138, upload-time = "2025-12-19T07:17:46.573Z" }, ] +[[package]] +name = "stackit-core" +version = "0.2.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "cryptography" }, + { name = "pydantic" }, + { name = "pyjwt", extra = ["crypto"] }, + { name = "requests" }, + { name = "urllib3" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/24/90/20f9ec7387eec4067cfd3d29055d0e2b5e1e0322c601a7f48125fd8ea35f/stackit_core-0.2.0.tar.gz", hash = "sha256:b8af91877cdb060d6969a303d8cf20bc0b33b345afd91f679c44a987381e2d47", size = 8987, upload-time = "2025-06-12T08:24:45.251Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/ab/b4/7b53187ce68956870d864ccb9ccfb68066c9df9de1c9568fd2feb03c4504/stackit_core-0.2.0-py3-none-any.whl", hash = "sha256:04632fc6742790d08ddfcb7f2313e04d1254827397a80250f838a2f81b92645b", size = 10240, upload-time = "2025-06-12T08:24:44.214Z" }, +] + +[[package]] +name = "stackit-iaas" +version = "1.4.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "pydantic" }, + { name = "python-dateutil" }, + { name = "requests" }, + { name = "stackit-core" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/52/07/24e65278300d5c3cb19cb1660bff924c80812cf8aad3e715f826bae5aa80/stackit_iaas-1.4.0.tar.gz", hash = "sha256:93523b23442350c7ebefd9129485c4c2a539f694a9c36a0f8edfaba9862057ea", size = 116236, upload-time = "2026-05-13T09:43:15.996Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/08/51/2201164d7bfacf47539888c735f10f6320c188252384957aa1b23121a210/stackit_iaas-1.4.0-py3-none-any.whl", hash = "sha256:3f4a32321b57ac238f73e5d660c6428186b92cc0425c1f0783ba801e377149d9", size = 316588, upload-time = "2026-05-13T09:43:14.943Z" }, +] + +[[package]] +name = "stackit-objectstorage" +version = "1.4.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "pydantic" }, + { name = "python-dateutil" }, + { name = "requests" }, + { name = "stackit-core" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/90/80/b790756af40a5c6d979dd688b2557394ac54b594eb4c08edc33157ba890f/stackit_objectstorage-1.4.0.tar.gz", hash = "sha256:4a3812b4de102b199f061706a802909f9e53ae9b0858769d5bd720f814c8bdbe", size = 31814, upload-time = "2026-05-13T09:43:05.027Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/68/f1/ffa8d5e2ec9f818c72a6f045691364eb4e927ee86641993a70882d00205a/stackit_objectstorage-1.4.0-py3-none-any.whl", hash = "sha256:1a3285c6840d95cff591d84fd21803575cb0d010c398e6575ed92987b9c39866", size = 65061, upload-time = "2026-05-13T09:43:04.13Z" }, +] + +[[package]] +name = "stackit-resourcemanager" +version = "0.8.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "pydantic" }, + { name = "python-dateutil" }, + { name = "requests" }, + { name = "stackit-core" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/23/2d/f458f18e48ed2b1c83df52cff7dbdfd5dd904fb2980ffd9385876e47bbd9/stackit_resourcemanager-0.8.0.tar.gz", hash = "sha256:f44542beab4130857f5a7f465cf02defeef657bdf63c1beeb3102f0ba3c003fe", size = 33943, upload-time = "2026-05-13T09:43:08.667Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/c7/9c/38a74d0f7a89b4320f6d2366fb660638bda8860daa08748b12c713d84381/stackit_resourcemanager-0.8.0-py3-none-any.whl", hash = "sha256:dd04bb8353d041a137c4dcba190beabded7acfaff1bc98b218fce20a99389ebc", size = 81288, upload-time = "2026-05-13T09:43:07.81Z" }, +] + [[package]] name = "statsd" version = "4.0.1" @@ -5730,6 +6075,52 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/d3/3e/4ae6af487ce5781ed71d5fe10aca72e7cbc4d4f45afc31b120287082a8dd/uuid6-2024.7.10-py3-none-any.whl", hash = "sha256:93432c00ba403751f722829ad21759ff9db051dea140bf81493271e8e4dd18b7", size = 6376, upload-time = "2024-07-10T16:39:36.148Z" }, ] +[[package]] +name = "uvicorn" +version = "0.49.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "click" }, + { name = "h11" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/c4/1f/fa18009dea8469069cca78a4e877a008ab78f08b064bfc9ab891579077ff/uvicorn-0.49.0.tar.gz", hash = "sha256:ebf4271aa580d9de97f93192d4595176df6e91f9aae919ca73e4fc07df1e66a3", size = 91284, upload-time = "2026-06-03T22:01:30.448Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/88/fa/e1388bbcf24ef3274f45c0c1c7b501fd14971037c1b6ee23610553307497/uvicorn-0.49.0-py3-none-any.whl", hash = "sha256:ba3d14c3ee7e41c6c654c46c9eb489d33213cdd30aa1696eab1374337c13f68f", size = 71376, upload-time = "2026-06-03T22:01:29.037Z" }, +] + +[[package]] +name = "uvicorn-worker" +version = "0.4.0" +source = { registry = "https://pypi.org/simple" } +dependencies = [ + { name = "gunicorn" }, + { name = "uvicorn" }, +] +sdist = { url = "https://files.pythonhosted.org/packages/80/59/9101b9c0680fd80e9d26c07deb822a5d18a324339fcf9cd017885ee808ad/uvicorn_worker-0.4.0.tar.gz", hash = "sha256:8ee5306070d8f38dce124adce488c3c0b50f20cf0c0222b12c66188da7214493", size = 9361, upload-time = "2025-09-20T10:47:01.218Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/90/25/09cd7a90c8bb7fb693be0d6704fccd5f9778d5513214b7a01cc4a94ff314/uvicorn_worker-0.4.0-py3-none-any.whl", hash = "sha256:e2ed952cef976f5e9e429d7269640bbcafbd36c80aa80f1003c8c77a6797abde", size = 5364, upload-time = "2025-09-20T10:46:59.776Z" }, +] + +[[package]] +name = "uvloop" +version = "0.22.1" +source = { registry = "https://pypi.org/simple" } +sdist = { url = "https://files.pythonhosted.org/packages/06/f0/18d39dbd1971d6d62c4629cc7fa67f74821b0dc1f5a77af43719de7936a7/uvloop-0.22.1.tar.gz", hash = "sha256:6c84bae345b9147082b17371e3dd5d42775bddce91f885499017f4607fdaf39f", size = 2443250, upload-time = "2025-10-16T22:17:19.342Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/c7/d5/69900f7883235562f1f50d8184bb7dd84a2fb61e9ec63f3782546fdbd057/uvloop-0.22.1-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:c60ebcd36f7b240b30788554b6f0782454826a0ed765d8430652621b5de674b9", size = 1352420, upload-time = "2025-10-16T22:16:21.187Z" }, + { url = "https://files.pythonhosted.org/packages/a8/73/c4e271b3bce59724e291465cc936c37758886a4868787da0278b3b56b905/uvloop-0.22.1-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:3b7f102bf3cb1995cfeaee9321105e8f5da76fdb104cdad8986f85461a1b7b77", size = 748677, upload-time = "2025-10-16T22:16:22.558Z" }, + { url = "https://files.pythonhosted.org/packages/86/94/9fb7fad2f824d25f8ecac0d70b94d0d48107ad5ece03769a9c543444f78a/uvloop-0.22.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:53c85520781d84a4b8b230e24a5af5b0778efdb39142b424990ff1ef7c48ba21", size = 3753819, upload-time = "2025-10-16T22:16:23.903Z" }, + { url = "https://files.pythonhosted.org/packages/74/4f/256aca690709e9b008b7108bc85fba619a2bc37c6d80743d18abad16ee09/uvloop-0.22.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:56a2d1fae65fd82197cb8c53c367310b3eabe1bbb9fb5a04d28e3e3520e4f702", size = 3804529, upload-time = "2025-10-16T22:16:25.246Z" }, + { url = "https://files.pythonhosted.org/packages/7f/74/03c05ae4737e871923d21a76fe28b6aad57f5c03b6e6bfcfa5ad616013e4/uvloop-0.22.1-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:40631b049d5972c6755b06d0bfe8233b1bd9a8a6392d9d1c45c10b6f9e9b2733", size = 3621267, upload-time = "2025-10-16T22:16:26.819Z" }, + { url = "https://files.pythonhosted.org/packages/75/be/f8e590fe61d18b4a92070905497aec4c0e64ae1761498cad09023f3f4b3e/uvloop-0.22.1-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:535cc37b3a04f6cd2c1ef65fa1d370c9a35b6695df735fcff5427323f2cd5473", size = 3723105, upload-time = "2025-10-16T22:16:28.252Z" }, + { url = "https://files.pythonhosted.org/packages/3d/ff/7f72e8170be527b4977b033239a83a68d5c881cc4775fca255c677f7ac5d/uvloop-0.22.1-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:fe94b4564e865d968414598eea1a6de60adba0c040ba4ed05ac1300de402cd42", size = 1359936, upload-time = "2025-10-16T22:16:29.436Z" }, + { url = "https://files.pythonhosted.org/packages/c3/c6/e5d433f88fd54d81ef4be58b2b7b0cea13c442454a1db703a1eea0db1a59/uvloop-0.22.1-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:51eb9bd88391483410daad430813d982010f9c9c89512321f5b60e2cddbdddd6", size = 752769, upload-time = "2025-10-16T22:16:30.493Z" }, + { url = "https://files.pythonhosted.org/packages/24/68/a6ac446820273e71aa762fa21cdcc09861edd3536ff47c5cd3b7afb10eeb/uvloop-0.22.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:700e674a166ca5778255e0e1dc4e9d79ab2acc57b9171b79e65feba7184b3370", size = 4317413, upload-time = "2025-10-16T22:16:31.644Z" }, + { url = "https://files.pythonhosted.org/packages/5f/6f/e62b4dfc7ad6518e7eff2516f680d02a0f6eb62c0c212e152ca708a0085e/uvloop-0.22.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:7b5b1ac819a3f946d3b2ee07f09149578ae76066d70b44df3fa990add49a82e4", size = 4426307, upload-time = "2025-10-16T22:16:32.917Z" }, + { url = "https://files.pythonhosted.org/packages/90/60/97362554ac21e20e81bcef1150cb2a7e4ffdaf8ea1e5b2e8bf7a053caa18/uvloop-0.22.1-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:e047cc068570bac9866237739607d1313b9253c3051ad84738cbb095be0537b2", size = 4131970, upload-time = "2025-10-16T22:16:34.015Z" }, + { url = "https://files.pythonhosted.org/packages/99/39/6b3f7d234ba3964c428a6e40006340f53ba37993f46ed6e111c6e9141d18/uvloop-0.22.1-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:512fec6815e2dd45161054592441ef76c830eddaad55c8aa30952e6fe1ed07c0", size = 4296343, upload-time = "2025-10-16T22:16:35.149Z" }, +] + [[package]] name = "vine" version = "5.1.0" @@ -5766,6 +6157,38 @@ wheels = [ { url = "https://files.pythonhosted.org/packages/34/db/b10e48aa8fff7407e67470363eac595018441cf32d5e1001567a7aeba5d2/websocket_client-1.9.0-py3-none-any.whl", hash = "sha256:af248a825037ef591efbf6ed20cc5faa03d3b47b9e5a2230a529eeee1c1fc3ef", size = 82616, upload-time = "2025-10-07T21:16:34.951Z" }, ] +[[package]] +name = "websockets" +version = "16.0" +source = { registry = "https://pypi.org/simple" } +sdist = { url = "https://files.pythonhosted.org/packages/04/24/4b2031d72e840ce4c1ccb255f693b15c334757fc50023e4db9537080b8c4/websockets-16.0.tar.gz", hash = "sha256:5f6261a5e56e8d5c42a4497b364ea24d94d9563e8fbd44e78ac40879c60179b5", size = 179346, upload-time = "2026-01-10T09:23:47.181Z" } +wheels = [ + { url = "https://files.pythonhosted.org/packages/f2/db/de907251b4ff46ae804ad0409809504153b3f30984daf82a1d84a9875830/websockets-16.0-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:31a52addea25187bde0797a97d6fc3d2f92b6f72a9370792d65a6e84615ac8a8", size = 177340, upload-time = "2026-01-10T09:22:34.539Z" }, + { url = "https://files.pythonhosted.org/packages/f3/fa/abe89019d8d8815c8781e90d697dec52523fb8ebe308bf11664e8de1877e/websockets-16.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:417b28978cdccab24f46400586d128366313e8a96312e4b9362a4af504f3bbad", size = 175022, upload-time = "2026-01-10T09:22:36.332Z" }, + { url = "https://files.pythonhosted.org/packages/58/5d/88ea17ed1ded2079358b40d31d48abe90a73c9e5819dbcde1606e991e2ad/websockets-16.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:af80d74d4edfa3cb9ed973a0a5ba2b2a549371f8a741e0800cb07becdd20f23d", size = 175319, upload-time = "2026-01-10T09:22:37.602Z" }, + { url = "https://files.pythonhosted.org/packages/d2/ae/0ee92b33087a33632f37a635e11e1d99d429d3d323329675a6022312aac2/websockets-16.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:08d7af67b64d29823fed316505a89b86705f2b7981c07848fb5e3ea3020c1abe", size = 184631, upload-time = "2026-01-10T09:22:38.789Z" }, + { url = "https://files.pythonhosted.org/packages/c8/c5/27178df583b6c5b31b29f526ba2da5e2f864ecc79c99dae630a85d68c304/websockets-16.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:7be95cfb0a4dae143eaed2bcba8ac23f4892d8971311f1b06f3c6b78952ee70b", size = 185870, upload-time = "2026-01-10T09:22:39.893Z" }, + { url = "https://files.pythonhosted.org/packages/87/05/536652aa84ddc1c018dbb7e2c4cbcd0db884580bf8e95aece7593fde526f/websockets-16.0-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:d6297ce39ce5c2e6feb13c1a996a2ded3b6832155fcfc920265c76f24c7cceb5", size = 185361, upload-time = "2026-01-10T09:22:41.016Z" }, + { url = "https://files.pythonhosted.org/packages/6d/e2/d5332c90da12b1e01f06fb1b85c50cfc489783076547415bf9f0a659ec19/websockets-16.0-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:1c1b30e4f497b0b354057f3467f56244c603a79c0d1dafce1d16c283c25f6e64", size = 184615, upload-time = "2026-01-10T09:22:42.442Z" }, + { url = "https://files.pythonhosted.org/packages/77/fb/d3f9576691cae9253b51555f841bc6600bf0a983a461c79500ace5a5b364/websockets-16.0-cp311-cp311-win32.whl", hash = "sha256:5f451484aeb5cafee1ccf789b1b66f535409d038c56966d6101740c1614b86c6", size = 178246, upload-time = "2026-01-10T09:22:43.654Z" }, + { url = "https://files.pythonhosted.org/packages/54/67/eaff76b3dbaf18dcddabc3b8c1dba50b483761cccff67793897945b37408/websockets-16.0-cp311-cp311-win_amd64.whl", hash = "sha256:8d7f0659570eefb578dacde98e24fb60af35350193e4f56e11190787bee77dac", size = 178684, upload-time = "2026-01-10T09:22:44.941Z" }, + { url = "https://files.pythonhosted.org/packages/84/7b/bac442e6b96c9d25092695578dda82403c77936104b5682307bd4deb1ad4/websockets-16.0-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:71c989cbf3254fbd5e84d3bff31e4da39c43f884e64f2551d14bb3c186230f00", size = 177365, upload-time = "2026-01-10T09:22:46.787Z" }, + { url = "https://files.pythonhosted.org/packages/b0/fe/136ccece61bd690d9c1f715baaeefd953bb2360134de73519d5df19d29ca/websockets-16.0-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:8b6e209ffee39ff1b6d0fa7bfef6de950c60dfb91b8fcead17da4ee539121a79", size = 175038, upload-time = "2026-01-10T09:22:47.999Z" }, + { url = "https://files.pythonhosted.org/packages/40/1e/9771421ac2286eaab95b8575b0cb701ae3663abf8b5e1f64f1fd90d0a673/websockets-16.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:86890e837d61574c92a97496d590968b23c2ef0aeb8a9bc9421d174cd378ae39", size = 175328, upload-time = "2026-01-10T09:22:49.809Z" }, + { url = "https://files.pythonhosted.org/packages/18/29/71729b4671f21e1eaa5d6573031ab810ad2936c8175f03f97f3ff164c802/websockets-16.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:9b5aca38b67492ef518a8ab76851862488a478602229112c4b0d58d63a7a4d5c", size = 184915, upload-time = "2026-01-10T09:22:51.071Z" }, + { url = "https://files.pythonhosted.org/packages/97/bb/21c36b7dbbafc85d2d480cd65df02a1dc93bf76d97147605a8e27ff9409d/websockets-16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:e0334872c0a37b606418ac52f6ab9cfd17317ac26365f7f65e203e2d0d0d359f", size = 186152, upload-time = "2026-01-10T09:22:52.224Z" }, + { url = "https://files.pythonhosted.org/packages/4a/34/9bf8df0c0cf88fa7bfe36678dc7b02970c9a7d5e065a3099292db87b1be2/websockets-16.0-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:a0b31e0b424cc6b5a04b8838bbaec1688834b2383256688cf47eb97412531da1", size = 185583, upload-time = "2026-01-10T09:22:53.443Z" }, + { url = "https://files.pythonhosted.org/packages/47/88/4dd516068e1a3d6ab3c7c183288404cd424a9a02d585efbac226cb61ff2d/websockets-16.0-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:485c49116d0af10ac698623c513c1cc01c9446c058a4e61e3bf6c19dff7335a2", size = 184880, upload-time = "2026-01-10T09:22:55.033Z" }, + { url = "https://files.pythonhosted.org/packages/91/d6/7d4553ad4bf1c0421e1ebd4b18de5d9098383b5caa1d937b63df8d04b565/websockets-16.0-cp312-cp312-win32.whl", hash = "sha256:eaded469f5e5b7294e2bdca0ab06becb6756ea86894a47806456089298813c89", size = 178261, upload-time = "2026-01-10T09:22:56.251Z" }, + { url = "https://files.pythonhosted.org/packages/c3/f0/f3a17365441ed1c27f850a80b2bc680a0fa9505d733fe152fdf5e98c1c0b/websockets-16.0-cp312-cp312-win_amd64.whl", hash = "sha256:5569417dc80977fc8c2d43a86f78e0a5a22fee17565d78621b6bb264a115d4ea", size = 178693, upload-time = "2026-01-10T09:22:57.478Z" }, + { url = "https://files.pythonhosted.org/packages/72/07/c98a68571dcf256e74f1f816b8cc5eae6eb2d3d5cfa44d37f801619d9166/websockets-16.0-pp311-pypy311_pp73-macosx_10_15_x86_64.whl", hash = "sha256:349f83cd6c9a415428ee1005cadb5c2c56f4389bc06a9af16103c3bc3dcc8b7d", size = 174947, upload-time = "2026-01-10T09:23:36.166Z" }, + { url = "https://files.pythonhosted.org/packages/7e/52/93e166a81e0305b33fe416338be92ae863563fe7bce446b0f687b9df5aea/websockets-16.0-pp311-pypy311_pp73-macosx_11_0_arm64.whl", hash = "sha256:4a1aba3340a8dca8db6eb5a7986157f52eb9e436b74813764241981ca4888f03", size = 175260, upload-time = "2026-01-10T09:23:37.409Z" }, + { url = "https://files.pythonhosted.org/packages/56/0c/2dbf513bafd24889d33de2ff0368190a0e69f37bcfa19009ef819fe4d507/websockets-16.0-pp311-pypy311_pp73-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:f4a32d1bd841d4bcbffdcb3d2ce50c09c3909fbead375ab28d0181af89fd04da", size = 176071, upload-time = "2026-01-10T09:23:39.158Z" }, + { url = "https://files.pythonhosted.org/packages/a5/8f/aea9c71cc92bf9b6cc0f7f70df8f0b420636b6c96ef4feee1e16f80f75dd/websockets-16.0-pp311-pypy311_pp73-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:0298d07ee155e2e9fda5be8a9042200dd2e3bb0b8a38482156576f863a9d457c", size = 176968, upload-time = "2026-01-10T09:23:41.031Z" }, + { url = "https://files.pythonhosted.org/packages/9a/3f/f70e03f40ffc9a30d817eef7da1be72ee4956ba8d7255c399a01b135902a/websockets-16.0-pp311-pypy311_pp73-win_amd64.whl", hash = "sha256:a653aea902e0324b52f1613332ddf50b00c06fdaf7e92624fbf8c77c78fa5767", size = 178735, upload-time = "2026-01-10T09:23:42.259Z" }, + { url = "https://files.pythonhosted.org/packages/6f/28/258ebab549c2bf3e64d2b0217b973467394a9cea8c42f70418ca2c5d0d2e/websockets-16.0-py3-none-any.whl", hash = "sha256:1637db62fad1dc833276dded54215f2c7fa46912301a24bd94d45d46a011ceec", size = 171598, upload-time = "2026-01-10T09:23:45.395Z" }, +] + [[package]] name = "werkzeug" version = "3.1.7" @@ -5780,16 +6203,16 @@ wheels = [ [[package]] name = "workos" -version = "6.0.4" +version = "6.0.8" source = { registry = "https://pypi.org/simple" } dependencies = [ { name = "cryptography" }, { name = "httpx" }, - { name = "pyjwt" }, + { name = "pyjwt", extra = ["crypto"] }, ] -sdist = { url = "https://files.pythonhosted.org/packages/3c/2f/99fb8718274116c5c146c745755620fd5c5943f78ca52ca9b17e94348286/workos-6.0.4.tar.gz", hash = "sha256:b0bfe8fd212b8567422c4ea3732eb33608794033eb3a69900c6b04db183c32d6", size = 172217, upload-time = "2026-04-16T03:09:28.583Z" } +sdist = { url = "https://files.pythonhosted.org/packages/ca/0d/0a7f78912657f99412c788932ea1f3f4089916e77bdef7d2463842febe08/workos-6.0.8.tar.gz", hash = "sha256:43aa3f1992a0a4ca8933d9b6e5ada846dd3b1fe0ee10e64c876ee2000fc6090d", size = 178137, upload-time = "2026-04-24T18:48:03.203Z" } wheels = [ - { url = "https://files.pythonhosted.org/packages/fa/f1/d2ab661e6dc2828a4c73e38f12630c3b109cfe2bc664ab70631c04f0db4b/workos-6.0.4-py3-none-any.whl", hash = "sha256:548668b3702673536f853ba72a7b5bbbc269e467aaf9ac4f477b6e0177df5e21", size = 511418, upload-time = "2026-04-16T03:09:27.098Z" }, + { url = "https://files.pythonhosted.org/packages/b2/3f/3d96da80d650b2f97d58af626053354584f619dbb769051e118bd9cd1ca5/workos-6.0.8-py3-none-any.whl", hash = "sha256:a00dd4930333aded2babbba824f8032eea05c5ca8c44d04a3fa068cf6be6e21a", size = 524505, upload-time = "2026-04-24T18:48:01.389Z" }, ] [[package]] diff --git a/claude_plugins/prowler/.claude-plugin/plugin.json b/claude_plugins/prowler/.claude-plugin/plugin.json new file mode 100644 index 0000000000..c77187c3b0 --- /dev/null +++ b/claude_plugins/prowler/.claude-plugin/plugin.json @@ -0,0 +1,30 @@ +{ + "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", + "name": "prowler", + "version": "0.1.0", + "description": "Prowler for Claude Code — cloud security and compliance skills powered by the Prowler MCP server. Bundles compliance triage and remediation; more skills coming.", + "author": { + "name": "Prowler", + "email": "support@prowler.com", + "url": "https://prowler.com" + }, + "homepage": "https://docs.prowler.com", + "repository": "https://github.com/prowler-cloud/prowler", + "license": "Apache-2.0", + "keywords": [ + "prowler", + "security", + "compliance", + "cloud-security", + "mcp" + ], + "userConfig": { + "api_key": { + "type": "string", + "title": "Prowler API key", + "description": "API key token used to authenticate with Prowler (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server) via the Prowler MCP server. Create one at https://cloud.prowler.com.", + "sensitive": true, + "required": true + } + } +} diff --git a/claude_plugins/prowler/.mcp.json b/claude_plugins/prowler/.mcp.json new file mode 100644 index 0000000000..9788b6d982 --- /dev/null +++ b/claude_plugins/prowler/.mcp.json @@ -0,0 +1,9 @@ +{ + "prowler": { + "type": "http", + "url": "https://mcp.prowler.com/mcp", + "headers": { + "Authorization": "Bearer ${user_config.api_key}" + } + } +} diff --git a/claude_plugins/prowler/README.md b/claude_plugins/prowler/README.md new file mode 100644 index 0000000000..6e204fbe44 --- /dev/null +++ b/claude_plugins/prowler/README.md @@ -0,0 +1,80 @@ +# Prowler for Claude Code + +End-to-end cloud security and compliance from inside [Claude Code](https://www.claude.com/product/claude-code), powered by the [Prowler MCP server](https://docs.prowler.com/projects/prowler-mcp/). The plugin lets Claude walk a Prowler Cloud-connected account through a compliance assessment and remediate findings until the chosen security or industry framework is compliant. + +> **Preview**: this plugin is under active development. Report issues at — [FAIL]
+**Description**:
+**Findings** ():
+- [FAIL] ``
+
+## Manual review requirements
+- **** — [PENDING]:
+````
+
+### 2.1 Generate or refresh the report
+
+Resolve the report path for the current `compliance_id` and provider account.
+
+If the file does not exist, call `prowler_get_compliance_framework_state_details` for the target scan, render the template above, and write the file with one initialization entry in the activity log.
+
+If the file exists, read it and compare its `Scan ID` to the target scan from section 1.3. When the scan matches, reuse the file and summarize remaining `[FAIL]` and `[IN PROGRESS]` items in chat.
+
+> **Checkpoint — Report refresh** *(conditional: the file's `Scan ID` differs from the current target scan)*
+>
+> Tell the user the report on disk was generated from a different scan and ask whether to refresh it from the new scan. Wait for the answer.
+
+On confirmation, regenerate the failed-requirements section from the new `prowler_get_compliance_framework_state_details` response, carry forward the **Global remediation approach** block and the full activity log, and append an activity-log entry noting the scan change.
+
+Once the file is current, surface the top failing requirements in chat: sort by finding count descending, show the top 5 with their codes and counts, and point to the file path for the full list.
+
+## 3. Remediation loop
+
+### 3.1 Define the global remediation approach
+
+Two modes are available:
+
+- **Claude-assisted** (default when the user has not specified): per-requirement confirmation. For each requirement Claude shows the target resource, exact commands, side effects, and reversibility, then waits for explicit go-ahead before applying.
+- **Claude autonomous**: no per-requirement gate, but Claude still presents one batch-level fix plan up front (§3.2) and waits for a single confirmation, and pauses if a finding looks not applicable, requires a paid feature, or has wide blast radius (breaks dev workflow, forces collaborator changes, is hard to reverse).
+
+If the user phrases their request as "just do it" or similar, treat that as autonomous **with** the batch-plan confirmation still required — the confirmation is a property of the skill, not the user's verbosity preference.
+
+> **Checkpoint — Global remediation approach**
+>
+> Ask the user which tool to use for fixes (Terraform, gh / az / aws CLI, web console, mixed...) and which mode to operate in. Wait for the answer before continuing. This checkpoint is non-negotiable: never assume a default tool, and never assume autonomous mode.
+
+Once answered, write the values into the **Global remediation approach** block of the report file.
+
+> **Checkpoint — Overwriting an existing approach** *(conditional: the block is already populated from a previous session)*
+>
+> Show the previous values and the new ones, and ask the user to confirm before overwriting. Wait for the answer.
+
+### 3.2 Present the batch fix plan *(autonomous mode only)*
+
+In **assisted** mode, skip this section — the per-requirement gate in §3.3 confirms each fix as it comes up. Only run §3.2 in **autonomous** mode, where the loop will otherwise apply fixes without further input.
+
+Before touching anything, post a single chat summary covering every `[FAIL]` requirement:
+
+- Group findings that share a fix (e.g. ten branch-protection requirements satisfied by one PUT call → present as one group).
+- For each group: target resource, exact tool calls, side effects, reversibility.
+- Call out findings that look **not applicable** to this target (e.g. an Organization-only check evaluated against a User account, a feature gated by a paid plan, a resource type the user doesn't have) and propose `[SKIPPED]` with the reason.
+- Call out findings that require manual user action Claude cannot perform.
+
+> **Checkpoint — Batch fix plan approval** *(conditional: autonomous mode)*
+>
+> Post the grouped plan and wait for explicit confirmation. Do not start any fix before the user replies.
+
+Once approved, the loop proceeds through the batch without further prompts unless something deviates from the approved plan.
+
+### 3.3 Pick the first FAIL requirement and inspect its findings
+
+Pick the first `[FAIL]` requirement at the top of the failed-requirements section. Move its status and every finding under it to `[IN PROGRESS]`, and add a `**Fix plan**:` sub-bullet describing what will be done.
+
+Call `prowler_get_finding_details` for each `finding_id` to retrieve the failing resource and the Prowler Hub's remediation guidance for that check using the tool `prowler_hub_get_check_details` with the `check_id` from the finding details. Summarize the guidance in chat, and append it to the `**Fix plan**` note for each finding.
+
+If a finding does not apply to the target resource (Organization-only check on a User account, paid-tier feature, missing resource type, etc.), set the requirement status to `[SKIPPED]` with the reason, log it in the activity log, and move on without attempting the fix — even if it was missed during §3.2.
+
+> **Checkpoint — Per-requirement approval** *(conditional: assisted mode)*
+>
+> Post the per-requirement plan in chat — resource, command, side effects, reversibility — and wait for confirmation before moving to §3.4. In **autonomous** mode, post the plan for transparency but proceed unless it deviates from the batch plan agreed in §3.2.
+
+### 3.4 Diagnose, fix, verify
+
+Read the remediation guidance returned in §3.3, identify the root cause, and apply the fix using the tool defined in the **Global remediation approach** block. After applying, verify via the same tool that applied the fix or via a provider API call when applicable. If the re-read shows the change did not land, leave the status at `[IN PROGRESS]`, surface the error to the user, and stop the loop for this requirement.
+
+When the change is in place, append a `**Fix applied**: ` sub-bullet to the requirement, move each fixed finding to `[FIXED-UNVERIFIED]`, and add one activity-log entry describing the change. If no programmatic verification was possible (e.g. web console action), note in the activity log that confirmation depends on the rescan in §3.5.
+
+### 3.5 Loop
+
+Move to the next `[FAIL]` requirement and repeat from section 3.3.
+
+> **Checkpoint — Rescan trigger** *(conditional: no `[FAIL]` requirements remain; all are `[FIXED-UNVERIFIED]` or `[SKIPPED]`)*
+>
+> Summarize what was applied, list any `[SKIPPED]` items with reasons, and ask whether to trigger a fresh scan with `prowler_trigger_scan` to verify the fixes end-to-end. Wait for the answer.
+
+On confirmation, trigger the rescan. When it completes, restart section 2.1 with the carry-forward path — requirements no longer in the new FAIL list move to `[PASS]`, anything still failing reverts to `[FAIL]` with the previous fix attempt visible in the activity log.
diff --git a/contrib/aws/multi-account-securityhub/Dockerfile b/contrib/aws/multi-account-securityhub/Dockerfile
index 1cc6c326b7..7e5e7f5182 100644
--- a/contrib/aws/multi-account-securityhub/Dockerfile
+++ b/contrib/aws/multi-account-securityhub/Dockerfile
@@ -1,7 +1,7 @@
# Build command
# docker build --platform=linux/amd64 --no-cache -t prowler:latest .
-ARG PROWLER_VERSION=latest
+ARG PROWLER_VERSION=latest@sha256:ebb4ab999f10cb7e7c256226c2873de9b3bf2f3d855f385e0164bcf34104bfba
FROM toniblyx/prowler:${PROWLER_VERSION}
diff --git a/contrib/inventory-graph/lib/inventory_output.py b/contrib/inventory-graph/lib/inventory_output.py
index 359e7eb91f..459dc37cdb 100644
--- a/contrib/inventory-graph/lib/inventory_output.py
+++ b/contrib/inventory-graph/lib/inventory_output.py
@@ -16,7 +16,6 @@ from typing import Optional
from prowler.lib.logger import logger
from lib.models import ConnectivityGraph
-
# ---------------------------------------------------------------------------
# JSON output
# ---------------------------------------------------------------------------
diff --git a/contrib/k8s/helm/prowler-api/values.yaml b/contrib/k8s/helm/prowler-api/values.yaml
index 81eda5f690..a6074c7852 100644
--- a/contrib/k8s/helm/prowler-api/values.yaml
+++ b/contrib/k8s/helm/prowler-api/values.yaml
@@ -28,7 +28,7 @@ containers:
image:
repository: prowlercloud/prowler-api
pullPolicy: IfNotPresent
- command: ["../docker-entrypoint.sh", "beat"]
+ command: ["/home/prowler/docker-entrypoint.sh", "beat"]
secrets:
POSTGRES_HOST:
@@ -438,6 +438,34 @@ mainConfig:
# Minimum number of Availability Zones that an ELBv2 must be in
elbv2_min_azs: 2
+ # AWS Post-Quantum TLS Configuration
+ # aws.acmpca_certificate_authority_pqc_key_algorithm
+ acmpca_pqc_key_algorithms:
+ - "ML_DSA_44"
+ - "ML_DSA_65"
+ - "ML_DSA_87"
+ # aws.cloudfront_distributions_pqc_tls_enabled
+ cloudfront_pqc_min_protocol_versions:
+ - "TLSv1.3_2025"
+ # aws.apigateway_domain_name_pqc_tls_enabled
+ apigateway_pqc_tls_allowed_policies:
+ - "SecurityPolicy_TLS13_1_2_FIPS_PFS_PQ_2025_09"
+ - "SecurityPolicy_TLS13_1_2_PFS_PQ_2025_09"
+ - "SecurityPolicy_TLS13_1_2_PQ_2025_09"
+
+ # AWS Post-Quantum SSH Key Exchange Configuration
+ # aws.transfer_server_pqc_ssh_kex_enabled
+ transfer_pqc_ssh_allowed_policies:
+ - "TransferSecurityPolicy-2025-03"
+ - "TransferSecurityPolicy-FIPS-2025-03"
+ - "TransferSecurityPolicy-AS2Restricted-2025-07"
+
+
+ # aws.rolesanywhere_trust_anchor_pqc_pki
+ rolesanywhere_pqc_pca_key_algorithms:
+ - "ML_DSA_44"
+ - "ML_DSA_65"
+ - "ML_DSA_87"
# AWS Secrets Configuration
# Patterns to ignore in the secrets checks
diff --git a/contrib/k8s/helm/prowler-app/templates/api/configmap.yaml b/contrib/k8s/helm/prowler-app/templates/api/configmap.yaml
index 8e219a9271..a76982d403 100644
--- a/contrib/k8s/helm/prowler-app/templates/api/configmap.yaml
+++ b/contrib/k8s/helm/prowler-app/templates/api/configmap.yaml
@@ -7,4 +7,4 @@ metadata:
data:
{{- range $key, $value := .Values.api.djangoConfig }}
{{ $key }}: {{ $value | quote }}
- {{- end }}
\ No newline at end of file
+ {{- end }}
diff --git a/contrib/k8s/helm/prowler-app/templates/api/role.yaml b/contrib/k8s/helm/prowler-app/templates/api/role.yaml
index 172b035076..f55d3c7dc9 100644
--- a/contrib/k8s/helm/prowler-app/templates/api/role.yaml
+++ b/contrib/k8s/helm/prowler-app/templates/api/role.yaml
@@ -26,4 +26,4 @@ roleRef:
subjects:
- kind: ServiceAccount
name: {{ include "prowler.api.serviceAccountName" . }}
- namespace: {{ .Release.Namespace }}
\ No newline at end of file
+ namespace: {{ .Release.Namespace }}
diff --git a/contrib/k8s/helm/prowler-app/templates/ui/configmap.yaml b/contrib/k8s/helm/prowler-app/templates/ui/configmap.yaml
index 38d6e65ee3..856770722a 100644
--- a/contrib/k8s/helm/prowler-app/templates/ui/configmap.yaml
+++ b/contrib/k8s/helm/prowler-app/templates/ui/configmap.yaml
@@ -11,8 +11,7 @@ data:
{{- else }}
AUTH_URL: {{ .Values.ui.authUrl | quote }}
{{- end }}
- API_BASE_URL: "http://{{ include "prowler.fullname" . }}-api:{{ .Values.api.service.port }}/api/v1"
- NEXT_PUBLIC_API_BASE_URL: "http://{{ include "prowler.fullname" . }}-api:{{ .Values.api.service.port }}/api/v1"
- NEXT_PUBLIC_API_DOCS_URL: "http://{{ include "prowler.fullname" . }}-api:{{ .Values.api.service.port }}/api/v1/docs"
+ UI_API_BASE_URL: "http://{{ include "prowler.fullname" . }}-api:{{ .Values.api.service.port }}/api/v1"
+ UI_API_DOCS_URL: "http://{{ include "prowler.fullname" . }}-api:{{ .Values.api.service.port }}/api/v1/docs"
AUTH_TRUST_HOST: "true"
UI_PORT: {{ .Values.ui.service.port | quote }}
diff --git a/contrib/k8s/helm/prowler-app/values.yaml b/contrib/k8s/helm/prowler-app/values.yaml
index 9acca09f2a..ed390af29e 100644
--- a/contrib/k8s/helm/prowler-app/values.yaml
+++ b/contrib/k8s/helm/prowler-app/values.yaml
@@ -440,7 +440,7 @@ worker_beat:
tag: ""
command:
- - ../docker-entrypoint.sh
+ - /home/prowler/docker-entrypoint.sh
args:
- beat
diff --git a/contrib/k8s/helm/prowler-ui/values.yaml b/contrib/k8s/helm/prowler-ui/values.yaml
index d4f2dbe137..aca0178b3a 100644
--- a/contrib/k8s/helm/prowler-ui/values.yaml
+++ b/contrib/k8s/helm/prowler-ui/values.yaml
@@ -21,8 +21,8 @@ fullnameOverride: ""
secrets:
SITE_URL: http://localhost:3000
- API_BASE_URL: http://prowler-api:8080/api/v1
- NEXT_PUBLIC_API_DOCS_URL: http://prowler-api:8080/api/v1/docs
+ UI_API_BASE_URL: http://prowler-api:8080/api/v1
+ UI_API_DOCS_URL: http://prowler-api:8080/api/v1/docs
AUTH_TRUST_HOST: True
UI_PORT: 3000
# openssl rand -base64 32
diff --git a/contrib/reverse-proxy/docker-compose.reverse-proxy.yml b/contrib/reverse-proxy/docker-compose.reverse-proxy.yml
index 08c52f3558..cb6bd9c3a2 100644
--- a/contrib/reverse-proxy/docker-compose.reverse-proxy.yml
+++ b/contrib/reverse-proxy/docker-compose.reverse-proxy.yml
@@ -16,7 +16,7 @@
services:
nginx:
- image: nginx:alpine
+ image: nginx:alpine@sha256:54f2a904c251d5a34adf545a72d32515a15e08418dae0266e23be2e18c66fefa
container_name: prowler-nginx
restart: unless-stopped
ports:
diff --git a/dashboard/__main__.py b/dashboard/__main__.py
index 664ce3bfa5..6a36bda7ed 100644
--- a/dashboard/__main__.py
+++ b/dashboard/__main__.py
@@ -20,7 +20,7 @@ print_banner()
print(
f"{Fore.GREEN}Loading all CSV files from the folder {folder_path_overview} ...\n{Style.RESET_ALL}"
)
-cli.show_server_banner = lambda *x: click.echo(
+cli.show_server_banner = lambda *_: click.echo(
f"{Fore.YELLOW}NOTE:{Style.RESET_ALL} If you are using {Fore.GREEN}{Style.BRIGHT}Prowler Cloud{Style.RESET_ALL} with the S3 integration or that integration \nfrom {Fore.CYAN}{Style.BRIGHT}Prowler CLI{Style.RESET_ALL} and you want to use your data from your S3 bucket,\nrun: `{orange_color}aws s3 cp s3:///output/csv ./output --recursive{Style.RESET_ALL}`\nand then run `prowler dashboard` again to load the new files."
)
@@ -33,148 +33,187 @@ dashboard = dash.Dash(
title="Prowler Dashboard",
)
-# Logo
-prowler_logo = html.Img(
- src="https://cdn.prod.website-files.com/68c4ec3f9fb7b154fbcb6e36/68ffb46d40ed7faa37a592a5_prowler-logo.png",
- alt="Prowler Logo",
+# ``use_pages`` above already imported dashboard/pages/cloud.py and registered
+# every /cloud/* route. Import its metadata now (after app instantiation) so
+# the sidebar and the gated pages share a single source of truth.
+from dashboard.pages.cloud import CLOUD_FEATURES_BY_SLUG # noqa: E402
+
+ICON_DIR = "/assets/images/icons/cloud"
+
+# Official marketing "PROWLER / LOCAL DASHBOARD" lockup (white wordmark + teal
+# gradient sublabel) shown in the expanded sidebar. Vector SVG so it stays crisp
+# at any DPI. The sublabel is right-anchored (text-anchor="end"), so a font
+# fallback widens it leftward rather than clipping at the edge.
+prowler_lockup = html.Img(
+ src=f"{ICON_DIR}/prowler-lockup.svg",
+ alt="Prowler Local Dashboard",
+ className="pc-brand-lockup",
)
-menu_icons = {
- "overview": "/assets/images/icons/overview.svg",
- "compliance": "/assets/images/icons/compliance.svg",
-}
+# Compact brand mark shown only when the sidebar collapses to its icon rail.
+prowler_mark = html.Img(
+ src=f"{ICON_DIR}/prowler-mark.svg",
+ alt="Prowler",
+ className="pc-brand-mark",
+)
+
+# Locally functional destinations (Overview + Compliance).
+DASHBOARD_ITEMS = [
+ {"label": "Overview", "route": "/", "icon": f"{ICON_DIR}/overview.svg"},
+ {
+ "label": "Compliance",
+ "route": "/compliance",
+ "icon": f"{ICON_DIR}/compliance.svg",
+ },
+]
+
+# Gated navigation groups reference the shared feature metadata by slug so the
+# sidebar and the informational pages never drift apart.
+GATED_GROUPS = [
+ ("Upgrade to Prowler Cloud", ["lighthouse-ai", "attack-paths", "findings"]),
+ ("Configuration", ["alerts", "mutelist", "integrations"]),
+ ("Workspace", ["organization"]),
+]
+
+HELP_LINKS = [
+ {
+ "title": "Help",
+ "url": "https://github.com/prowler-cloud/prowler/issues",
+ "icon": f"{ICON_DIR}/help.svg",
+ },
+ {
+ "title": "Docs",
+ "url": "https://docs.prowler.com",
+ "icon": f"{ICON_DIR}/docs.svg",
+ },
+]
-# Function to generate navigation links
-def generate_nav_links(current_path):
- nav_links = []
- for page in dash.page_registry.values():
- # Gets the icon URL based on the page name
- icon_url = menu_icons.get(page["name"].lower())
- is_active = (
- " bg-prowler-stone-950 border-r-4 border-solid border-prowler-lime"
- if current_path == page["relative_path"]
- else ""
- )
- link_class = f"block hover:bg-prowler-stone-950 hover:border-r-4 hover:border-solid hover:border-prowler-lime{is_active}"
+def _mask_style(icon_url):
+ """Inline style rendering a recolorable mask icon from a local asset."""
+ return {
+ "WebkitMaskImage": f"url({icon_url})",
+ "maskImage": f"url({icon_url})",
+ }
- link_content = html.Span(
+
+def _nav_icon(icon_url):
+ return html.Span(className="pc-ico", style=_mask_style(icon_url))
+
+
+def _nav_item(label, route, icon_url, current_path, gated=False):
+ is_active = current_path == route
+ class_name = "pc-nav-item pc-active" if is_active else "pc-nav-item"
+
+ content = [
+ _nav_icon(icon_url),
+ html.Span(label, className="pc-nav-label"),
+ ]
+ if gated:
+ content.append(html.Span("Prowler Cloud", className="pc-pill"))
+
+ return dcc.Link(content, href=route, className=class_name)
+
+
+def _section_label(title):
+ return html.Div(title, className="pc-section")
+
+
+def generate_sidebar(current_path):
+ children = [
+ # Brand lockup: full wordmark when expanded, compact mark when collapsed.
+ html.Div(
+ [prowler_lockup, prowler_mark],
+ className="pc-brand",
+ ),
+ # Dashboards section — the only locally functional destinations.
+ _section_label("Dashboards"),
+ html.Nav(
[
- html.Img(src=icon_url, className="w-5"),
- html.Span(
- page["name"], className="font-medium text-base leading-6 text-white"
- ),
+ _nav_item(item["label"], item["route"], item["icon"], current_path)
+ for item in DASHBOARD_ITEMS
],
- className="flex justify-center lg:justify-normal items-center gap-x-3 py-2 px-3",
- )
-
- nav_link = html.Li(
- dcc.Link(link_content, href=page["relative_path"], className=link_class)
- )
- nav_links.append(nav_link)
- return nav_links
-
-
-def generate_help_menu():
- help_links = [
- {
- "title": "Help",
- "url": "https://github.com/prowler-cloud/prowler/issues",
- "icon": "/assets/images/icons/help.png",
- },
- {
- "title": "Docs",
- "url": "https://docs.prowler.com",
- "icon": "/assets/images/icons/docs.png",
- },
+ className="pc-nav",
+ ),
]
- link_class = "block hover:bg-prowler-stone-950 hover:border-r-4 hover:border-solid hover:border-prowler-lime"
-
- menu_items = []
- for link in help_links:
- menu_item = html.Li(
- html.A(
- html.Span(
- [
- html.Img(src=link["icon"], className="w-5"),
- html.Span(
- link["title"],
- className="font-medium text-base leading-6 text-white",
- ),
- ],
- className="flex items-center gap-x-3 py-2 px-3",
- ),
- href=link["url"],
- target="_blank",
- className=link_class,
+ # Gated groups (Prowler Cloud only).
+ for section_title, slugs in GATED_GROUPS:
+ children.append(_section_label(section_title))
+ children.append(
+ html.Nav(
+ [
+ _nav_item(
+ CLOUD_FEATURES_BY_SLUG[slug]["nav_label"],
+ CLOUD_FEATURES_BY_SLUG[slug]["route"],
+ CLOUD_FEATURES_BY_SLUG[slug]["icon"],
+ current_path,
+ gated=True,
+ )
+ for slug in slugs
+ ],
+ className="pc-nav",
)
)
- menu_items.append(menu_item)
- return menu_items
+ # Help and Docs pinned to the bottom, separated by a neutral top border.
+ children.append(
+ html.Nav(
+ [
+ html.A(
+ [
+ _nav_icon(link["icon"]),
+ html.Span(link["title"], className="pc-nav-label"),
+ ],
+ href=link["url"],
+ target="_blank",
+ rel="noopener noreferrer",
+ className="pc-nav-item",
+ )
+ for link in HELP_LINKS
+ ],
+ className="pc-nav pc-footer",
+ )
+ )
+
+ return html.Div(children, className="pc-sidebar pc-font")
# Layout
dashboard.layout = html.Div(
[
- dcc.Location(id="url", refresh=False),
html.Link(rel="icon", href="assets/favicon.ico"),
- # Placeholder for dynamic navigation bar
html.Div(
[
+ # Dynamic sidebar (rebuilt on navigation for active state).
+ html.Div(id="navigation-bar"),
+ # Main pane hosting the routed page content.
html.Div(
- id="navigation-bar", className="bg-prowler-stone-900 min-w-36 z-10"
- ),
- html.Div(
- [
+ html.Div(
dash.page_container,
- ],
+ className="pc-main-inner",
+ ),
id="content_select",
- className="bg-prowler-white w-full col-span-11 h-screen mx-auto overflow-y-scroll no-scrollbar px-10 py-7",
+ className="pc-main pc-font no-scrollbar",
),
],
- className="grid custom-grid 2xl:custom-grid-large h-screen",
+ className="pc-shell",
),
],
className="h-screen mx-auto",
)
-# Callback to update navigation bar
-@dashboard.callback(Output("navigation-bar", "children"), [Input("url", "pathname")])
+# Callback to update navigation bar.
+#
+# Triggered off Dash Pages' own location (``_pages_location``) rather than a
+# separate ``dcc.Location``. A standalone ``dcc.Location(id="url")`` stops
+# emitting ``pathname`` when navigating between two pages that render an
+# identical component tree — every ``/cloud/*`` gated page shares the same
+# ``build_cloud_layout`` structure — which left the active highlight stuck on
+# the first gated page visited. ``_pages_location`` fires on every route change.
+@dashboard.callback(
+ Output("navigation-bar", "children"), [Input("_pages_location", "pathname")]
+)
def update_nav_bar(pathname):
- return html.Div(
- [
- html.Div([prowler_logo], className="mb-8 px-3"),
- html.H6(
- "Dashboards",
- className="px-3 text-prowler-stone-500 text-sm opacity-90 font-regular mb-2",
- ),
- html.Nav(
- [html.Ul(generate_nav_links(pathname), className="")],
- className="flex flex-col gap-y-6",
- ),
- html.Nav(
- [
- html.A(
- [
- html.Span(
- [
- html.Img(src="assets/favicon.ico", className="w-5"),
- "Subscribe to Prowler Cloud",
- ],
- className="flex items-center gap-x-3 text-white",
- ),
- ],
- href="https://prowler.com/",
- target="_blank",
- className="block p-3 uppercase text-xs hover:bg-prowler-stone-950 hover:border-r-4 hover:border-solid hover:border-prowler-lime",
- ),
- html.Ul(generate_help_menu(), className=""),
- ],
- className="flex flex-col gap-y-6 mt-auto",
- ),
- ],
- className="flex flex-col bg-prowler-stone-900 py-7 h-full",
- )
+ return generate_sidebar(pathname)
diff --git a/dashboard/assets/cloud-pages.css b/dashboard/assets/cloud-pages.css
new file mode 100644
index 0000000000..53052eabda
--- /dev/null
+++ b/dashboard/assets/cloud-pages.css
@@ -0,0 +1,389 @@
+/*
+ * Prowler Local Dashboard — Cloud upsell chrome & gated pages.
+ * These styles are self-contained (not dependent on the precompiled Tailwind
+ * bundle) so pixel specs from the PRD render reliably without a rebuild.
+ */
+
+@import url("https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap");
+
+:root {
+ --pc-btn: #6ee7b7;
+ --pc-btn-hover: #99f6e4;
+ --pc-btn-press: #34d399;
+ --pc-grad-start: #2ee59b;
+ --pc-grad-end: #62dff0;
+ --pc-text: #020617;
+ --pc-text-2: #27272a;
+ --pc-sidebar-bg: #27272a;
+ --pc-pane-bg: #fdfdfd;
+ --pc-border: #e5e5e5;
+ --pc-teal-accent: #2ee59b;
+ --pc-sidebar-w: 264px;
+ --pc-sidebar-w-collapsed: 82px;
+}
+
+.pc-font {
+ font-family: "Inter", system-ui, -apple-system, "Segoe UI", Roboto,
+ Helvetica, Arial, sans-serif;
+}
+
+/* ----------------------------------------------------------------- Shell */
+
+.pc-shell {
+ display: flex;
+ height: 100vh;
+ width: 100%;
+ overflow: hidden;
+}
+
+.pc-main {
+ flex: 1 1 auto;
+ height: 100vh;
+ overflow-y: auto;
+ background: var(--pc-pane-bg);
+}
+
+.pc-main-inner {
+ padding: 28px 40px 64px;
+}
+
+/* --------------------------------------------------------------- Sidebar */
+
+.pc-sidebar {
+ flex: 0 0 var(--pc-sidebar-w);
+ width: var(--pc-sidebar-w);
+ background: var(--pc-sidebar-bg);
+ height: 100vh;
+ display: flex;
+ flex-direction: column;
+ padding: 22px 0 16px;
+ overflow-y: auto;
+ overflow-x: hidden;
+}
+
+.pc-sidebar::-webkit-scrollbar {
+ display: none;
+}
+
+.pc-brand {
+ display: flex;
+ align-items: center;
+ gap: 10px;
+ padding: 0 18px;
+ margin-bottom: 22px;
+}
+
+.pc-brand-lockup {
+ width: 190px;
+ height: auto;
+ display: block;
+}
+
+/* Compact mark is only revealed on the collapsed icon rail (see media query). */
+.pc-brand-mark {
+ width: 30px;
+ height: 30px;
+ flex: 0 0 auto;
+ display: none;
+}
+
+.pc-section {
+ color: #8a8a90;
+ font-size: 11px;
+ font-weight: 600;
+ letter-spacing: 0.07em;
+ text-transform: uppercase;
+ padding: 0 18px;
+ margin: 18px 0 8px;
+}
+
+.pc-nav {
+ display: flex;
+ flex-direction: column;
+ gap: 2px;
+}
+
+.pc-nav-item {
+ display: flex;
+ align-items: center;
+ gap: 10px;
+ padding: 9px 12px;
+ margin: 0 8px;
+ color: #ffffff;
+ font-size: 14px;
+ font-weight: 500;
+ text-decoration: none;
+ border-radius: 8px;
+ border-left: 3px solid transparent;
+ overflow: hidden;
+ transition: background 0.15s ease;
+}
+
+.pc-nav-item:hover {
+ background: rgba(255, 255, 255, 0.07);
+}
+
+.pc-nav-item.pc-active {
+ background: rgba(255, 255, 255, 0.09);
+ border-left-color: var(--pc-teal-accent);
+}
+
+.pc-nav-label {
+ flex: 0 1 auto;
+ min-width: 0;
+ white-space: nowrap;
+ overflow: hidden;
+ text-overflow: ellipsis;
+}
+
+/* Icon rendered as a recolorable mask so one asset serves any color. */
+.pc-ico {
+ width: 20px;
+ height: 20px;
+ flex: 0 0 auto;
+ display: inline-block;
+ background-color: currentColor;
+ -webkit-mask-repeat: no-repeat;
+ mask-repeat: no-repeat;
+ -webkit-mask-position: center;
+ mask-position: center;
+ -webkit-mask-size: contain;
+ mask-size: contain;
+}
+
+.pc-pill {
+ flex: 0 0 auto;
+ margin-left: auto;
+ display: inline-flex;
+ align-items: center;
+ background: linear-gradient(
+ 112deg,
+ var(--pc-grad-start) 3.5%,
+ var(--pc-grad-end) 98.8%
+ );
+ color: var(--pc-text);
+ font-size: 10px;
+ font-weight: 700;
+ letter-spacing: 0.02em;
+ line-height: 1;
+ padding: 3px 8px;
+ border-radius: 9999px;
+ white-space: nowrap;
+}
+
+.pc-footer {
+ margin-top: auto;
+ padding-top: 12px;
+ border-top: 1px solid rgba(255, 255, 255, 0.1);
+}
+
+/* -------------------------------------------------------- Gated page body */
+
+.pc-page {
+ max-width: 1120px;
+ margin: 0 auto;
+}
+
+.pc-page-header {
+ border-bottom: 1px solid var(--pc-border);
+ padding-bottom: 18px;
+ margin-bottom: 28px;
+}
+
+.pc-page-title-row {
+ display: flex;
+ align-items: center;
+ gap: 12px;
+}
+
+/* In the page header the badge sits right next to the title (not pushed to the
+ far right like the sidebar pills) and is uppercased for emphasis. */
+.pc-page-title-row .pc-pill {
+ margin-left: 0;
+ text-transform: uppercase;
+ letter-spacing: 0.04em;
+}
+
+.pc-page-title {
+ font-size: 24px;
+ font-weight: 700;
+ color: var(--pc-text);
+ margin: 0;
+}
+
+.pc-page-subtitle {
+ font-size: 15px;
+ line-height: 24px;
+ color: #52525b;
+ margin: 8px 0 0;
+}
+
+/* ----------------------------------------------------------- Upgrade card */
+
+.pc-card {
+ position: relative;
+ background: #ffffff;
+ border: 1px solid var(--pc-border);
+ border-radius: 18px;
+ padding: 56px 40px;
+ overflow: hidden;
+}
+
+.pc-card-glow {
+ position: absolute;
+ top: 0;
+ left: 50%;
+ transform: translateX(-50%);
+ width: 560px;
+ height: 240px;
+ background: radial-gradient(
+ ellipse at top,
+ rgba(46, 229, 155, 0.2),
+ rgba(98, 223, 240, 0.06) 45%,
+ transparent 72%
+ );
+ pointer-events: none;
+}
+
+.pc-card-body {
+ position: relative;
+ z-index: 1;
+ display: flex;
+ flex-direction: column;
+ align-items: center;
+ text-align: center;
+}
+
+.pc-feature-icon {
+ width: 64px;
+ height: 64px;
+ border-radius: 16px;
+ background: linear-gradient(
+ 135deg,
+ rgba(46, 229, 155, 0.16),
+ rgba(98, 223, 240, 0.14)
+ );
+ border: 1px solid rgba(46, 229, 155, 0.3);
+ display: flex;
+ align-items: center;
+ justify-content: center;
+ color: var(--pc-text);
+ margin-bottom: 22px;
+}
+
+.pc-feature-icon .pc-ico {
+ width: 30px;
+ height: 30px;
+}
+
+.pc-avail {
+ color: #0e9f6e;
+ font-size: 12px;
+ font-weight: 700;
+ letter-spacing: 0.09em;
+ text-transform: uppercase;
+ margin-bottom: 8px;
+}
+
+.pc-card-title {
+ font-size: 24px;
+ font-weight: 700;
+ color: var(--pc-text);
+ margin: 0 0 14px;
+}
+
+.pc-card-desc {
+ font-size: 15px;
+ line-height: 24px;
+ color: var(--pc-text-2);
+ max-width: 560px;
+ margin: 0 0 26px;
+}
+
+.pc-benefits {
+ list-style: none;
+ padding: 0;
+ margin: 0 0 30px;
+ text-align: left;
+}
+
+.pc-benefit {
+ display: flex;
+ align-items: flex-start;
+ gap: 10px;
+ padding: 7px 0;
+ font-size: 15px;
+ line-height: 22px;
+ color: var(--pc-text-2);
+}
+
+.pc-benefit-check {
+ flex: 0 0 auto;
+ width: 18px;
+ height: 18px;
+ margin-top: 2px;
+ color: var(--pc-btn-press);
+}
+
+.pc-cta {
+ display: inline-flex;
+ align-items: center;
+ justify-content: center;
+ background: var(--pc-btn);
+ color: var(--pc-text);
+ font-size: 15px;
+ font-weight: 700;
+ padding: 12px 24px;
+ border-radius: 12px;
+ border: 1px solid var(--pc-btn-press);
+ text-decoration: none;
+ cursor: pointer;
+ transition: background 0.15s ease;
+}
+
+.pc-cta:hover {
+ background: var(--pc-btn-hover);
+ color: var(--pc-text);
+}
+
+.pc-cta:active {
+ background: var(--pc-btn-press);
+}
+
+/* --------------------------------------------------- Responsive collapse */
+
+@media (max-width: 900px) {
+ .pc-sidebar {
+ flex-basis: var(--pc-sidebar-w-collapsed);
+ width: var(--pc-sidebar-w-collapsed);
+ }
+
+ .pc-brand {
+ justify-content: center;
+ padding: 0 8px;
+ }
+
+ .pc-brand-lockup {
+ display: none;
+ }
+
+ .pc-brand-mark {
+ display: block;
+ }
+
+ .pc-section,
+ .pc-nav-label,
+ .pc-pill {
+ display: none;
+ }
+
+ .pc-nav-item {
+ justify-content: center;
+ margin: 0 6px;
+ padding: 10px 0;
+ }
+
+ .pc-main-inner {
+ padding: 20px 18px 48px;
+ }
+}
diff --git a/dashboard/assets/images/icons/cloud/alerts.svg b/dashboard/assets/images/icons/cloud/alerts.svg
new file mode 100644
index 0000000000..6109e378ab
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/alerts.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/attack-paths.svg b/dashboard/assets/images/icons/cloud/attack-paths.svg
new file mode 100644
index 0000000000..b856c6ea2f
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/attack-paths.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/check.svg b/dashboard/assets/images/icons/cloud/check.svg
new file mode 100644
index 0000000000..a5f8ed0c8a
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/check.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/compliance.svg b/dashboard/assets/images/icons/cloud/compliance.svg
new file mode 100644
index 0000000000..e70ebda28c
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/compliance.svg
@@ -0,0 +1,4 @@
+
diff --git a/dashboard/assets/images/icons/cloud/docs.svg b/dashboard/assets/images/icons/cloud/docs.svg
new file mode 100644
index 0000000000..efc3dfc61b
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/docs.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/findings.svg b/dashboard/assets/images/icons/cloud/findings.svg
new file mode 100644
index 0000000000..93fc42a516
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/findings.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/help.svg b/dashboard/assets/images/icons/cloud/help.svg
new file mode 100644
index 0000000000..2b3f1024e8
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/help.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/integrations.svg b/dashboard/assets/images/icons/cloud/integrations.svg
new file mode 100644
index 0000000000..e7a2d07603
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/integrations.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/lighthouse-ai.svg b/dashboard/assets/images/icons/cloud/lighthouse-ai.svg
new file mode 100644
index 0000000000..1c510ac1fc
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/lighthouse-ai.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/mutelist.svg b/dashboard/assets/images/icons/cloud/mutelist.svg
new file mode 100644
index 0000000000..1d498fa9e3
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/mutelist.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/organization.svg b/dashboard/assets/images/icons/cloud/organization.svg
new file mode 100644
index 0000000000..1f3d1da9f5
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/organization.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/overview.svg b/dashboard/assets/images/icons/cloud/overview.svg
new file mode 100644
index 0000000000..809e63d945
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/overview.svg
@@ -0,0 +1,4 @@
+
diff --git a/dashboard/assets/images/icons/cloud/prowler-lockup.svg b/dashboard/assets/images/icons/cloud/prowler-lockup.svg
new file mode 100644
index 0000000000..9daee36463
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/prowler-lockup.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/assets/images/icons/cloud/prowler-mark.svg b/dashboard/assets/images/icons/cloud/prowler-mark.svg
new file mode 100644
index 0000000000..eb30d44be8
--- /dev/null
+++ b/dashboard/assets/images/icons/cloud/prowler-mark.svg
@@ -0,0 +1 @@
+
diff --git a/dashboard/common_methods.py b/dashboard/common_methods.py
index a2f9ffe89b..b9f59513a5 100644
--- a/dashboard/common_methods.py
+++ b/dashboard/common_methods.py
@@ -1538,6 +1538,186 @@ def get_section_container_iso(data, section_1, section_2):
return html.Div(section_containers, className="compliance-data-layout")
+def _status_bar(success, failed, classname):
+ """Build the stacked PASS/FAIL bar shown next to an accordion title."""
+ fig = go.Figure(
+ data=[
+ go.Bar(
+ name="Failed",
+ x=[failed],
+ y=[""],
+ orientation="h",
+ marker=dict(color="#e77676"),
+ width=[0.8],
+ ),
+ go.Bar(
+ name="Success",
+ x=[success],
+ y=[""],
+ orientation="h",
+ marker=dict(color="#45cc6e"),
+ width=[0.8],
+ ),
+ ]
+ )
+ fig.update_layout(
+ barmode="stack",
+ margin=dict(l=10, r=10, t=10, b=10),
+ paper_bgcolor="rgba(0,0,0,0)",
+ plot_bgcolor="rgba(0,0,0,0)",
+ showlegend=False,
+ width=350,
+ height=30,
+ xaxis=dict(showticklabels=False, showgrid=False, zeroline=False),
+ yaxis=dict(showticklabels=False, showgrid=False, zeroline=False),
+ annotations=[
+ dict(
+ x=success + failed,
+ y=0,
+ xref="x",
+ yref="y",
+ text=str(success),
+ showarrow=False,
+ font=dict(color="#45cc6e", size=14),
+ xanchor="left",
+ yanchor="middle",
+ ),
+ dict(
+ x=0,
+ y=0,
+ xref="x",
+ yref="y",
+ text=str(failed),
+ showarrow=False,
+ font=dict(color="#e77676", size=14),
+ xanchor="right",
+ yanchor="middle",
+ ),
+ ],
+ )
+ fig.add_annotation(
+ x=failed,
+ y=0.3,
+ text="|",
+ showarrow=False,
+ xanchor="center",
+ yanchor="middle",
+ font=dict(size=20),
+ )
+ return dcc.Graph(figure=fig, config={"staticPlot": True}, className=classname)
+
+
+def get_section_containers_generic(data, section_col, id_col):
+ """Two-level view: section -> requirement id (+ description) -> checks.
+
+ Sorts lexicographically so arbitrary requirement IDs never crash the
+ version-aware sort used by the CIS renderer.
+ """
+ data["STATUS"] = data["STATUS"].apply(map_status_to_icon)
+ data[section_col] = data[section_col].astype(str)
+ data[id_col] = data[id_col].astype(str)
+ data.sort_values(by=[section_col, id_col], inplace=True)
+
+ counts_section = data.groupby([section_col, "STATUS"]).size().unstack(fill_value=0)
+ counts_id = (
+ data.groupby([section_col, id_col, "STATUS"]).size().unstack(fill_value=0)
+ )
+
+ def count(counts, key, emoji):
+ return counts.loc[key, emoji] if emoji in counts.columns else 0
+
+ has_description = "REQUIREMENTS_DESCRIPTION" in data.columns
+ table_cols = ["CHECKID", "STATUS", "REGION", "ACCOUNTID", "RESOURCEID"]
+
+ section_containers = []
+ for section in data[section_col].unique():
+ graph_div = html.Div(
+ _status_bar(
+ count(counts_section, section, pass_emoji),
+ count(counts_section, section, fail_emoji),
+ "info-bar",
+ ),
+ className="graph-section",
+ )
+
+ internal_items = []
+ for req_id in data[data[section_col] == section][id_col].unique():
+ specific_data = data[
+ (data[section_col] == section) & (data[id_col] == req_id)
+ ]
+ data_table = dash_table.DataTable(
+ data=specific_data.to_dict("records"),
+ columns=[
+ {"name": i, "id": i}
+ for i in table_cols
+ if i in specific_data.columns
+ ],
+ style_table={"overflowX": "auto"},
+ style_as_list_view=True,
+ style_cell={"textAlign": "left", "padding": "5px"},
+ )
+ graph_div_req = html.Div(
+ _status_bar(
+ count(counts_id, (section, req_id), pass_emoji),
+ count(counts_id, (section, req_id), fail_emoji),
+ "info-bar-child",
+ ),
+ className="graph-section-req",
+ )
+
+ title = req_id
+ if has_description:
+ title = (
+ f"{req_id} - {specific_data['REQUIREMENTS_DESCRIPTION'].iloc[0]}"
+ )
+ if len(title) > 130:
+ title = title[:130] + " ..."
+
+ internal_items.append(
+ html.Div(
+ [
+ graph_div_req,
+ dbc.Accordion(
+ [
+ dbc.AccordionItem(
+ title=title,
+ children=[
+ html.Div(
+ [data_table],
+ className="inner-accordion-content",
+ )
+ ],
+ )
+ ],
+ start_collapsed=True,
+ flush=True,
+ ),
+ ],
+ className="accordion-inner--child",
+ )
+ )
+
+ section_containers.append(
+ html.Div(
+ [
+ graph_div,
+ dbc.Accordion(
+ [
+ dbc.AccordionItem(
+ title=f"{section}", children=internal_items
+ )
+ ],
+ start_collapsed=True,
+ flush=True,
+ ),
+ ],
+ className="accordion-inner",
+ )
+ )
+
+ return html.Div(section_containers, className="compliance-data-layout")
+
+
def get_section_containers_format4(data, section_1):
data["STATUS"] = data["STATUS"].apply(map_status_to_icon)
diff --git a/dashboard/compliance/aws_ai_security_framework_aws.py b/dashboard/compliance/aws_ai_security_framework_aws.py
new file mode 100644
index 0000000000..ece9bdf9cb
--- /dev/null
+++ b/dashboard/compliance/aws_ai_security_framework_aws.py
@@ -0,0 +1,27 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_3_levels
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ aux = data[
+ [
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "REQUIREMENTS_ATTRIBUTES_SUBSECTION",
+ "NAME",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ]
+
+ return get_section_containers_3_levels(
+ aux,
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "REQUIREMENTS_ATTRIBUTES_SUBSECTION",
+ "NAME",
+ )
diff --git a/dashboard/compliance/cis_2_0_1_kubernetes.py b/dashboard/compliance/cis_2_0_1_kubernetes.py
new file mode 100644
index 0000000000..94558f33ad
--- /dev/null
+++ b/dashboard/compliance/cis_2_0_1_kubernetes.py
@@ -0,0 +1,24 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_cis
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ aux = data[
+ [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ].copy()
+
+ return get_section_containers_cis(
+ aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
+ )
diff --git a/dashboard/compliance/cis_5_0_gcp.py b/dashboard/compliance/cis_5_0_gcp.py
new file mode 100644
index 0000000000..94558f33ad
--- /dev/null
+++ b/dashboard/compliance/cis_5_0_gcp.py
@@ -0,0 +1,24 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_cis
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ aux = data[
+ [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ].copy()
+
+ return get_section_containers_cis(
+ aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
+ )
diff --git a/dashboard/compliance/cis_6_0_azure.py b/dashboard/compliance/cis_6_0_azure.py
new file mode 100644
index 0000000000..9d33cc67a8
--- /dev/null
+++ b/dashboard/compliance/cis_6_0_azure.py
@@ -0,0 +1,25 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_cis
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+
+ aux = data[
+ [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ].copy()
+
+ return get_section_containers_cis(
+ aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
+ )
diff --git a/dashboard/compliance/cis_7_0_aws.py b/dashboard/compliance/cis_7_0_aws.py
new file mode 100644
index 0000000000..94558f33ad
--- /dev/null
+++ b/dashboard/compliance/cis_7_0_aws.py
@@ -0,0 +1,24 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_cis
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ aux = data[
+ [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ].copy()
+
+ return get_section_containers_cis(
+ aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
+ )
diff --git a/dashboard/compliance/cis_7_0_m365.py b/dashboard/compliance/cis_7_0_m365.py
new file mode 100644
index 0000000000..94558f33ad
--- /dev/null
+++ b/dashboard/compliance/cis_7_0_m365.py
@@ -0,0 +1,24 @@
+import warnings
+
+from dashboard.common_methods import get_section_containers_cis
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ aux = data[
+ [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "REQUIREMENTS_ATTRIBUTES_SECTION",
+ "CHECKID",
+ "STATUS",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+ ].copy()
+
+ return get_section_containers_cis(
+ aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
+ )
diff --git a/dashboard/compliance/generic.py b/dashboard/compliance/generic.py
new file mode 100644
index 0000000000..f7d68bb52a
--- /dev/null
+++ b/dashboard/compliance/generic.py
@@ -0,0 +1,44 @@
+import warnings
+
+from dashboard.common_methods import (
+ get_section_containers_format4,
+ get_section_containers_generic,
+)
+
+warnings.filterwarnings("ignore")
+
+
+def get_table(data):
+ # Discover REQUIREMENTS_ATTRIBUTES_* columns at runtime.
+ attr_cols = [c for c in data.columns if c.startswith("REQUIREMENTS_ATTRIBUTES_")]
+
+ # Section column (in priority order):
+ # 1. REQUIREMENTS_ATTRIBUTES_SECTION — most common convention
+ # 2. First discovered attribute column — covers novel schemas
+ # 3. None — no section, group flat by requirement id
+ if "REQUIREMENTS_ATTRIBUTES_SECTION" in attr_cols:
+ section_col = "REQUIREMENTS_ATTRIBUTES_SECTION"
+ elif attr_cols:
+ section_col = attr_cols[0]
+ else:
+ section_col = None
+
+ base_cols = [
+ "REQUIREMENTS_ID",
+ "REQUIREMENTS_DESCRIPTION",
+ "STATUS",
+ "CHECKID",
+ "REGION",
+ "ACCOUNTID",
+ "RESOURCEID",
+ ]
+
+ # Two levels (section -> requirement id) when a section distinct from the
+ # id exists; otherwise group flat by requirement id.
+ if section_col and section_col != "REQUIREMENTS_ID":
+ needed = [section_col] + base_cols
+ aux = data[[c for c in needed if c in data.columns]].copy()
+ return get_section_containers_generic(aux, section_col, "REQUIREMENTS_ID")
+
+ aux = data[[c for c in base_cols if c in data.columns]].copy()
+ return get_section_containers_format4(aux, "REQUIREMENTS_ID")
diff --git a/dashboard/lib/layouts.py b/dashboard/lib/layouts.py
index 930432b6c4..6d1e7947fa 100644
--- a/dashboard/lib/layouts.py
+++ b/dashboard/lib/layouts.py
@@ -156,7 +156,7 @@ def create_layout_compliance(
html.Img(src="assets/favicon.ico", className="w-5 mr-3"),
html.Span("Subscribe to Prowler Cloud"),
],
- href="https://prowler.pro/",
+ href="https://cloud.prowler.com/sign-up?utm_source=prowler-local-dashboard&utm_content=compliance",
target="_blank",
className="text-prowler-stone-900 inline-flex px-4 py-2 text-xs font-bold uppercase transition-all rounded-lg text-gray-900 hover:bg-prowler-stone-900/10 border-solid border-1 hover:border-prowler-stone-900/10 hover:border-solid hover:border-1 border-prowler-stone-900/10",
),
diff --git a/dashboard/pages/cloud.py b/dashboard/pages/cloud.py
new file mode 100644
index 0000000000..49778f8e26
--- /dev/null
+++ b/dashboard/pages/cloud.py
@@ -0,0 +1,265 @@
+"""Prowler Cloud upsell (gated) informational pages.
+
+These routes live inside the Local Dashboard but do NOT reproduce any Prowler
+Cloud functionality. Each renders the same reusable upgrade template with a
+feature-specific name, icon, description, benefit bullets and UTM-tagged CTA.
+All copy in ``CLOUD_FEATURES`` is normative — do not change wording,
+capitalization or punctuation without Product approval.
+"""
+
+import dash
+from dash import html
+
+# Shared subtitle used across every gated page header.
+CLOUD_SUBTITLE = "Discover more ways to protect and operate your cloud."
+
+# Base Prowler Cloud URL; the UTM content value identifies the feature.
+CLOUD_CTA_BASE = (
+ "https://cloud.prowler.com/sign-up?utm_source=prowler-local-dashboard&utm_content="
+)
+
+# Path to the recolorable checkmark mask used for benefit bullets.
+CHECK_ICON = "/assets/images/icons/cloud/check.svg"
+
+
+# Normative feature definitions. ``icon`` points to a local mask asset so no
+# external requests are needed and the glyph recolors per context.
+CLOUD_FEATURES = [
+ {
+ "slug": "lighthouse-ai",
+ "route": "/cloud/lighthouse-ai",
+ "nav_label": "Lighthouse AI",
+ "page_title": "Lighthouse AI",
+ "card_title": "Unlock Lighthouse AI",
+ "description": (
+ "Work with an AI security analyst that understands your cloud "
+ "posture and helps turn risk into action."
+ ),
+ "benefits": [
+ "Ask questions about your security posture in plain language",
+ "Investigate findings with context from your connected providers",
+ "Move from insight to remediation faster",
+ ],
+ "utm_content": "lighthouse-ai",
+ "icon": "/assets/images/icons/cloud/lighthouse-ai.svg",
+ },
+ {
+ "slug": "attack-paths",
+ "route": "/cloud/attack-paths",
+ "nav_label": "Attack Paths",
+ "page_title": "Attack Paths",
+ "card_title": "Unlock Attack Paths",
+ "description": (
+ "Visualize the paths an attacker could take through connected "
+ "resources before risk becomes compromise."
+ ),
+ "benefits": [
+ "See exploitable relationships across your AWS environment",
+ "Focus remediation on the paths with the greatest impact",
+ "Explore each scan as a point-in-time security graph",
+ ],
+ "utm_content": "attack-paths",
+ "icon": "/assets/images/icons/cloud/attack-paths.svg",
+ },
+ {
+ "slug": "findings",
+ "route": "/cloud/findings",
+ "nav_label": "Findings",
+ "page_title": "Findings",
+ "card_title": "Unlock Findings",
+ "description": (
+ "Filter, investigate, and prioritize security findings across "
+ "providers and scans from one workspace."
+ ),
+ "benefits": [
+ "Search and filter findings across all connected accounts",
+ "Track status, severity, ownership, and remediation context",
+ "Triage findings and share a consistent source of truth with your security team",
+ ],
+ "utm_content": "findings",
+ "icon": "/assets/images/icons/cloud/findings.svg",
+ },
+ {
+ "slug": "alerts",
+ "route": "/cloud/alerts",
+ "nav_label": "Alerts",
+ "page_title": "Alerts",
+ "card_title": "Unlock Alerts",
+ "description": (
+ "Create alert rules and stay informed when scan results reveal "
+ "the risks your team cares about."
+ ),
+ "benefits": [
+ "Define alerts around the findings that matter most",
+ "Route security signals to the right responders",
+ "Reduce the time between detection and action",
+ ],
+ "utm_content": "alerts",
+ "icon": "/assets/images/icons/cloud/alerts.svg",
+ },
+ {
+ "slug": "mutelist",
+ "route": "/cloud/mutelist",
+ "nav_label": "Mutelist",
+ "page_title": "Mutelist",
+ "card_title": "Unlock Mutelist",
+ "description": (
+ "Quiet expected findings, document accepted risk, and keep your "
+ "team focused on actionable work."
+ ),
+ "benefits": [
+ "Create reusable rules for known exceptions",
+ "Keep muted findings available for audit and review",
+ "Cut noise without losing security context",
+ ],
+ "utm_content": "mutelist",
+ "icon": "/assets/images/icons/cloud/mutelist.svg",
+ },
+ {
+ "slug": "integrations",
+ "route": "/cloud/integrations",
+ "nav_label": "Integrations",
+ "page_title": "Integrations",
+ "card_title": "Unlock Integrations",
+ "description": (
+ "Connect Prowler to your security workflow so findings and scan "
+ "data reach the tools your team already uses."
+ ),
+ "benefits": [
+ "Connect ticketing, notification, and cloud security services",
+ "Automate the handoff from detection to response",
+ "Keep teams aligned without manual exports",
+ ],
+ "utm_content": "integrations",
+ "icon": "/assets/images/icons/cloud/integrations.svg",
+ },
+ {
+ "slug": "organization",
+ "route": "/cloud/organization",
+ "nav_label": "Organization",
+ "page_title": "Organization",
+ "card_title": "Unlock Organization",
+ "description": (
+ "Manage users, roles, and invitations while organizing cloud "
+ "security work across your team."
+ ),
+ "benefits": [
+ "Invite teammates into a shared security workspace",
+ "Control access with role-based permissions",
+ "Coordinate security operations across accounts and teams",
+ ],
+ "utm_content": "organization",
+ "icon": "/assets/images/icons/cloud/organization.svg",
+ },
+]
+
+# Convenience lookup for the navigation builder in ``__main__``.
+CLOUD_FEATURES_BY_SLUG = {feature["slug"]: feature for feature in CLOUD_FEATURES}
+
+
+def _mask_style(icon_url):
+ """Return the inline style that renders a recolorable mask icon."""
+ return {
+ "WebkitMaskImage": f"url({icon_url})",
+ "maskImage": f"url({icon_url})",
+ }
+
+
+def _benefit_item(text):
+ return html.Li(
+ [
+ html.Span(
+ className="pc-ico pc-benefit-check",
+ style=_mask_style(CHECK_ICON),
+ ),
+ html.Span(text),
+ ],
+ className="pc-benefit",
+ )
+
+
+def build_cloud_layout(feature):
+ """Build the reusable gated informational page for a single feature."""
+ cta_url = f"{CLOUD_CTA_BASE}{feature['utm_content']}"
+
+ return html.Div(
+ html.Div(
+ [
+ # Page header: title + Prowler Cloud badge + shared subtitle.
+ html.Div(
+ [
+ html.Div(
+ [
+ html.H1(
+ feature["page_title"],
+ className="pc-page-title",
+ ),
+ html.Span("Prowler Cloud", className="pc-pill"),
+ ],
+ className="pc-page-title-row",
+ ),
+ html.P(CLOUD_SUBTITLE, className="pc-page-subtitle"),
+ ],
+ className="pc-page-header",
+ ),
+ # Centered upgrade card.
+ html.Div(
+ [
+ html.Div(className="pc-card-glow"),
+ html.Div(
+ [
+ html.Div(
+ html.Span(
+ className="pc-ico",
+ style=_mask_style(feature["icon"]),
+ ),
+ className="pc-feature-icon",
+ ),
+ html.Div(
+ "Available in Prowler Cloud",
+ className="pc-avail",
+ ),
+ html.H2(
+ feature["card_title"],
+ className="pc-card-title",
+ ),
+ html.P(
+ feature["description"],
+ className="pc-card-desc",
+ ),
+ html.Ul(
+ [
+ _benefit_item(benefit)
+ for benefit in feature["benefits"]
+ ],
+ className="pc-benefits",
+ ),
+ html.A(
+ "Upgrade to Prowler Cloud",
+ href=cta_url,
+ target="_blank",
+ rel="noopener noreferrer",
+ className="pc-cta",
+ ),
+ ],
+ className="pc-card-body",
+ ),
+ ],
+ className="pc-card",
+ ),
+ ],
+ className="pc-page pc-font",
+ ),
+ )
+
+
+# Register one page per gated feature. A distinct module key keeps each entry
+# unique in Dash's page registry while sharing the same template.
+for _feature in CLOUD_FEATURES:
+ dash.register_page(
+ f"cloud_{_feature['slug'].replace('-', '_')}",
+ path=_feature["route"],
+ name=_feature["nav_label"],
+ title=f"Prowler Dashboard - {_feature['page_title']}",
+ layout=build_cloud_layout(_feature),
+ )
diff --git a/dashboard/pages/compliance.py b/dashboard/pages/compliance.py
index c1da9f611e..773dd095da 100644
--- a/dashboard/pages/compliance.py
+++ b/dashboard/pages/compliance.py
@@ -215,6 +215,58 @@ else:
)
+def _ensure_scope_columns(data):
+ """Guarantee ACCOUNTID and REGION exist.
+
+ Scope columns always sit between DESCRIPTION and ASSESSMENTDATE, so derive
+ them positionally for any provider (e.g. Okta's ORGANIZATIONDOMAIN) and
+ fall back to "-" to avoid a KeyError.
+ """
+ cols = list(data.columns)
+ scope = []
+ if "DESCRIPTION" in cols and "ASSESSMENTDATE" in cols:
+ start, end = cols.index("DESCRIPTION") + 1, cols.index("ASSESSMENTDATE")
+ scope = [c for c in cols[start:end] if c not in ("ACCOUNTID", "REGION")]
+
+ if "ACCOUNTID" not in data.columns:
+ if scope:
+ data.rename(columns={scope.pop(0): "ACCOUNTID"}, inplace=True)
+ else:
+ data["ACCOUNTID"] = "-"
+ if "REGION" not in data.columns:
+ if scope:
+ data.rename(columns={scope.pop(0): "REGION"}, inplace=True)
+ else:
+ data["REGION"] = "-"
+ return data
+
+
+def _dispatch_compliance_renderer(data, analytics_input):
+ """Resolve the compliance renderer module and return (table, deduped_data).
+
+ Tries to import the framework-specific builtin module. On
+ ModuleNotFoundError (dynamic/external provider with no dedicated module),
+ falls back to the generic renderer. Any other ImportError is re-raised.
+ get_table() is called OUTSIDE the try block so errors inside the renderer
+ surface as real exceptions rather than being swallowed.
+ """
+ current = analytics_input.replace(".", "_")
+ target = f"dashboard.compliance.{current}"
+ try:
+ module = importlib.import_module(target)
+ except ModuleNotFoundError as exc:
+ if exc.name != target:
+ raise
+ from dashboard.compliance import generic as module
+ dedup_columns = ["CHECKID", "STATUS", "RESOURCEID", "STATUSEXTENDED"]
+ if "MUTED" in data.columns:
+ dedup_columns.insert(2, "MUTED")
+ data = data.drop_duplicates(subset=dedup_columns)
+ if "threatscore" in analytics_input:
+ data = get_threatscore_mean_by_pillar(data)
+ return module.get_table(data), data
+
+
@callback(
[
Output("output", "children"),
@@ -292,7 +344,7 @@ def display_data(
data.rename(columns={"TENANCYID": "ACCOUNTID"}, inplace=True)
# Filter the chosen level of the CIS
- if is_level_1:
+ if is_level_1 and "REQUIREMENTS_ATTRIBUTES_PROFILE" in data.columns:
data = data[data["REQUIREMENTS_ATTRIBUTES_PROFILE"].str.contains("Level 1")]
# Rename the column PROJECTID to ACCOUNTID for GCP
@@ -314,6 +366,9 @@ def display_data(
data.rename(columns={"SUBSCRIPTION": "ACCOUNTID"}, inplace=True)
data["REGION"] = "-"
+ # Normalize scope columns for any remaining (e.g. dynamic) provider.
+ data = _ensure_scope_columns(data)
+
# Filter ACCOUNT
if account_filter == ["All"]:
updated_cloud_account_values = data["ACCOUNTID"].unique()
@@ -409,36 +464,7 @@ def display_data(
# Check cases where the compliance start with AWS_
if "aws_" in analytics_input:
analytics_input = analytics_input + "_aws"
- try:
- current = analytics_input.replace(".", "_")
- compliance_module = importlib.import_module(
- f"dashboard.compliance.{current}"
- )
- # Build subset list based on available columns
- dedup_columns = ["CHECKID", "STATUS", "RESOURCEID", "STATUSEXTENDED"]
- if "MUTED" in data.columns:
- dedup_columns.insert(2, "MUTED")
- data = data.drop_duplicates(subset=dedup_columns)
-
- if "threatscore" in analytics_input:
- data = get_threatscore_mean_by_pillar(data)
-
- table = compliance_module.get_table(data)
- except ModuleNotFoundError:
- table = html.Div(
- [
- html.H5(
- "No data found for this compliance",
- className="card-title",
- style={"text-align": "left", "color": "black"},
- )
- ],
- style={
- "width": "99%",
- "margin-right": "0.8%",
- "margin-bottom": "10px",
- },
- )
+ table, data = _dispatch_compliance_renderer(data, analytics_input)
df = data.copy()
# Remove Muted rows
diff --git a/dashboard/pages/overview.py b/dashboard/pages/overview.py
index 665aa8e195..8f786412d9 100644
--- a/dashboard/pages/overview.py
+++ b/dashboard/pages/overview.py
@@ -1538,7 +1538,7 @@ def filter_data(
html.Img(src="assets/favicon.ico", className="w-5 mr-3"),
html.Span("Subscribe to Prowler Cloud"),
],
- href="https://prowler.pro/",
+ href="https://cloud.prowler.com/sign-up?utm_source=prowler-local-dashboard&utm_content=overview",
target="_blank",
className="text-prowler-stone-900 inline-flex px-4 py-2 text-xs font-bold uppercase transition-all rounded-lg text-gray-900 hover:bg-prowler-stone-900/10 border-solid border-1 hover:border-prowler-stone-900/10 hover:border-solid hover:border-1 border-prowler-stone-900/10",
),
diff --git a/docker-compose-dev.yml b/docker-compose-dev.yml
index 2020c7d21a..d737298183 100644
--- a/docker-compose-dev.yml
+++ b/docker-compose-dev.yml
@@ -1,6 +1,6 @@
services:
api-dev-init:
- image: busybox:1.37.0
+ image: busybox:1.37.0@sha256:9532d8c39891ca2ecde4d30d7710e01fb739c87a8b9299685c63704296b16028
volumes:
- ./_data/api:/data
command: ["sh", "-c", "chown -R 1000:1000 /data"]
@@ -64,7 +64,7 @@ services:
condition: service_healthy
postgres:
- image: postgres:16.3-alpine3.20
+ image: postgres:16.3-alpine3.20@sha256:36ed71227ae36305d26382657c0b96cbaf298427b3f1eaeb10d77a6dea3eec41
hostname: "postgres-db"
volumes:
- ./_data/postgres:/var/lib/postgresql/data
@@ -88,7 +88,7 @@ services:
retries: 5
valkey:
- image: valkey/valkey:7-alpine3.19
+ image: valkey/valkey:7-alpine3.19@sha256:4054fe7fc607b9326ac7c4691ed26e9670d2ff17a9fb28c2577adecf928acbcc
hostname: "valkey"
volumes:
- ./_data/valkey:/data
@@ -104,7 +104,7 @@ services:
retries: 3
neo4j:
- image: graphstack/dozerdb:5.26.3.0
+ image: graphstack/dozerdb:5.26.3.0@sha256:a77526ea3918fdc46d1fff70c4aea7d71d3874a26ecec059179d6775845b1247
hostname: "neo4j"
volumes:
- ./_data/neo4j:/data
@@ -139,6 +139,8 @@ services:
worker-dev:
image: prowler-api-dev
+ # Give Celery soft shutdown time to drain/re-queue in-flight tasks on stop.
+ stop_grace_period: 120s
build:
context: ./api
dockerfile: Dockerfile
@@ -183,7 +185,7 @@ services:
soft: 65536
hard: 65536
entrypoint:
- - "../docker-entrypoint.sh"
+ - "/home/prowler/docker-entrypoint.sh"
- "beat"
mcp-server:
diff --git a/docker-compose.yml b/docker-compose.yml
index a9d2e03c3d..6cb5ac237d 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -6,7 +6,7 @@
#
services:
api-init:
- image: busybox:1.37.0
+ image: busybox:1.37.0@sha256:9532d8c39891ca2ecde4d30d7710e01fb739c87a8b9299685c63704296b16028
volumes:
- ./_data/api:/data
command: ["sh", "-c", "chown -R 1000:1000 /data"]
@@ -60,7 +60,7 @@ services:
start_period: 60s
postgres:
- image: postgres:16.3-alpine3.20
+ image: postgres:16.3-alpine3.20@sha256:36ed71227ae36305d26382657c0b96cbaf298427b3f1eaeb10d77a6dea3eec41
hostname: "postgres-db"
volumes:
- ./_data/postgres:/var/lib/postgresql/data
@@ -80,7 +80,7 @@ services:
retries: 5
valkey:
- image: valkey/valkey:7-alpine3.19
+ image: valkey/valkey:7-alpine3.19@sha256:4054fe7fc607b9326ac7c4691ed26e9670d2ff17a9fb28c2577adecf928acbcc
hostname: "valkey"
volumes:
- ./_data/valkey:/data
@@ -96,7 +96,7 @@ services:
retries: 3
neo4j:
- image: graphstack/dozerdb:5.26.3.0
+ image: graphstack/dozerdb:5.26.3.0@sha256:a77526ea3918fdc46d1fff70c4aea7d71d3874a26ecec059179d6775845b1247
hostname: "neo4j"
volumes:
- ./_data/neo4j:/data
@@ -129,6 +129,8 @@ services:
worker:
image: prowlercloud/prowler-api:${PROWLER_API_VERSION:-stable}
+ # Give Celery soft shutdown time to drain/re-queue in-flight tasks on stop.
+ stop_grace_period: 120s
env_file:
- path: .env
required: false
@@ -158,7 +160,7 @@ services:
soft: 65536
hard: 65536
entrypoint:
- - "../docker-entrypoint.sh"
+ - "/home/prowler/docker-entrypoint.sh"
- "beat"
mcp-server:
diff --git a/docs/AGENTS.md b/docs/AGENTS.md
index 826c6d63f4..45bd3f04fa 100644
--- a/docs/AGENTS.md
+++ b/docs/AGENTS.md
@@ -78,11 +78,25 @@ b. National security is of the utmost concern nowadays.
Prowler Features are considered proper nouns. They are to be referenced without articles in all pieces of writing.
-This is a list of Prowler Features:
+Prowler ships two product families. Use these names exactly; the former names Prowler App (now Prowler Local Server) and Prowler Enterprise (now Prowler Private Cloud) must not appear in new writing. The only allowed former-name notes are on the Prowler Product Families page (`getting-started/products/index.mdx`) and in the site-wide banner, which document the mapping.
+
+Prowler Products:
+
+* **Prowler Cloud**
+* **Prowler Private Cloud** (formerly Prowler Enterprise)
+* **Prowler Hub**
+* **Prowler Lighthouse AI**
+* **Prowler MCP**
+
+Open Source projects:
-* **Prowler App**
* **Prowler CLI**
+* **Prowler Local Server** (formerly Prowler App)
+* **Prowler Local Dashboard** (the Prowler CLI dashboard)
* **Prowler SDK**
+
+Other Prowler Features:
+
* **Built-in Compliance Checks**
* **Multi-cloud Security Scanning**
* **Autonomous Cloud Security Analyst (AI)**
@@ -97,8 +111,6 @@ This is a list of Prowler Features:
* **AI-Generated Detections & Remediations**
* **Prowler Studio**
* **Custom Security Policies**
-* **Prowler Cloud**
-* **Prowler Registry**
* **Open Source & Full APIs**
---
@@ -134,13 +146,13 @@ Example 1 is vague and even potentially ambiguous. Verbs state your purpose and
Explicit use of second-person pronouns (you) and possessives (your) should be minimized whenever possible. Those constructions are best reserved for cases when instructions are directly given in an imperative form:
-**Example of Improvement Through Avoiding Second Person Pronouns**
+### Example of Improvement Through Avoiding Second Person Pronouns
**Original:**
-Prowler App can be installed in different ways, depending on your environment:
+Prowler Local Server can be installed in different ways, depending on your environment:
**Improved Version:**
-Prowler App offers flexible installation methods tailored to various environments:
+Prowler Local Server offers flexible installation methods tailored to various environments:
---
@@ -236,7 +248,7 @@ The use of bullet points is highly recommended when:
* Information can be logically divided into multiple categories, each sharing characteristics, features, or other relevant classifications.
* Items are significant enough as standalone concepts to deserve their own bullet point.
-**Example of Improvement Through Bullet Points**
+#### Example of Improvement Through Bullet Points
**Original:**
It contains hundreds of controls covering CIS, NIST 800, NIST CSF, CISA, RBI, FedRAMS, PCI-DSS, GDPR, HIPAA, FFIEC, SOC2, GXP, AWS Well-Architected Framework Security Pillar, AWS Foundational Technical Review (FTR), ENS (Spanish National Security Scheme), and your custom security frameworks.
@@ -262,7 +274,7 @@ There are several options for punctuating bullet points. Regardless of the style
* **No punctuation (minimalistic):** This strategy is suitable when no verbs are involved and is best used to highlight products or features in isolation. For example:
- Prowler App is composed of three key components:
+ Prowler Local Server is composed of three key components:
* Prowler UI
* Prowler API
* Prowler SDK
@@ -271,7 +283,7 @@ There are several options for punctuating bullet points. Regardless of the style
* **Periods for full sentences:** This approach works best when each bullet point forms a full sentence or includes verbs. For example:
- Prowler App is composed of three key components:
+ Prowler Local Server is composed of three key components:
* Prowler UI, a web-based interface, built with Next.js, providing a user-friendly experience for executing Prowler scans and visualizing results.
* Prowler API, a backend service, developed with Django REST Framework, responsible for running Prowler scans and storing the generated results.
* Prowler SDK, a Python SDK designed to extend the functionality of the Prowler CLI for advanced capabilities.
@@ -539,6 +551,43 @@ Tag-Based Scanning allows filtering resources by AWS tags during security assess
---
+## AppliesTo Banner for Product Scope
+
+The AppliesTo component states which products a guide covers and links to the product families page. It is located at `docs/snippets/applies-to.mdx`.
+
+### When to Use the AppliesTo Banner
+
+Use it on web UI tutorial pages that apply to more than one product (for example, a guide written for Prowler Cloud whose steps also work on Prowler Local Server). Do not combine it with the SubscriptionBanner: pages carrying the SubscriptionBanner already state their availability.
+
+### How to Use the AppliesTo Banner
+
+```mdx
+import { AppliesTo } from "/snippets/applies-to.mdx"
+
+"] a span::after` selector to the Cloud marker rule in `docs/style.css` for every page whose content is subscription-gated. The `li` id equals the page URL path. Pages where only one section is gated (for example the Support page, where only the Support Desk carries the SubscriptionBanner) get no marker.
+* Navigation groups: add a selector only when every page in the group is subscription-gated. One sanctioned exception: the Prowler MCP group is marked because the hosted server at `mcp.prowler.com` includes tools for Prowler Cloud-specific features, and its overview page explains the free local alternative. Nested groups render as `li[data-title=""]` with a button toggle, so use `li[data-title=""] > button span:first-child::after`. Top-level groups render as `h3` headings without `data-title`, which means name collisions with top-level groups resolve themselves; a gated top-level group (always expanded) is selected through its sibling list with `:has()`, like the Security tab group. Do not use `:has()` on child links of nested groups: collapsed groups do not render their children.
+
+Do not use the `icon` field for this marker (icons render before the label and misalign the sidebar), and do not use `"tag"` on navigation groups (group-level tags crash `mint broken-links` with a stack overflow, verified with mint 4.2.689). The SVG stroke uses the fixed brand green `#10B981` on purpose: it must be visible on both themes without `currentColor` support.
+
+The marker meaning is explained on the Prowler Product Families page at `getting-started/products/index.mdx`: keep that note in place.
+
+---
+
## Avoid Assumptions Regarding Audience’s Expertise
### Understand Your Audience’s Expertise
diff --git a/docs/README.md b/docs/README.md
index 595f79bc5a..7934972c9b 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -5,7 +5,7 @@ This repository contains the Prowler Open Source documentation powered by [Mintl
## Documentation Structure
- **Getting Started**: Overview, installation, and basic usage guides
-- **User Guide**: Comprehensive guides for Prowler App, CLI, providers, and compliance
+- **User Guide**: Comprehensive guides for Prowler Cloud, Prowler Local Server, Prowler CLI, providers, and compliance
- **Developer Guide**: Technical documentation for developers contributing to Prowler
## Local Development
@@ -13,7 +13,7 @@ This repository contains the Prowler Open Source documentation powered by [Mintl
Install a reviewed version of the [Mintlify CLI](https://www.npmjs.com/package/mint) to preview documentation changes locally:
```bash
-npm install --global mint@4.2.560
+npm install --global mint@4.2.689
```
Run the following command at the root of your documentation (where `mint.json` is located):
diff --git a/docs/developer-guide/ai-skills.mdx b/docs/developer-guide/ai-skills.mdx
index 6a0787dac8..ceb154d027 100644
--- a/docs/developer-guide/ai-skills.mdx
+++ b/docs/developer-guide/ai-skills.mdx
@@ -8,7 +8,77 @@ This guide explains the AI Skills system that provides on-demand context and pat
**What are AI Skills?** Skills are structured instructions that help AI agents (Claude Code, Cursor, Copilot, etc.) understand Prowler's conventions, patterns, and best practices.
-## Architecture Overview
+Skills live in the [`skills/`](https://github.com/prowler-cloud/prowler/tree/master/skills) directory of the Prowler OSS repository. Each skill is a folder containing a `SKILL.md` file with its patterns and metadata.
+
+## Installation
+
+To enable skills for the supported AI coding assistants, run the setup script from the repository root:
+
+```bash
+./skills/setup.sh
+```
+
+The script creates symlinks so each tool finds the skills in its expected location:
+
+| Tool | Created by setup |
+|------|------------------|
+| Claude Code | `.claude/skills/` symlink and `CLAUDE.md` |
+| Gemini CLI | `.gemini/skills/` symlink and `GEMINI.md` |
+| Codex (OpenAI) | `.codex/skills/` symlink (uses `AGENTS.md` natively) |
+| GitHub Copilot | `.github/copilot-instructions.md` symlink to `AGENTS.md` |
+
+After running the setup, restart the AI coding assistant to load the skills.
+
+## Using Skills
+
+AI agents discover skills automatically and load them when a request matches a skill trigger. To load a skill manually during a session, point the agent to the skill's `SKILL.md` file:
+
+```text
+Read skills/{skill-name}/SKILL.md
+```
+
+For the full list of available skills, their triggers, and the Auto-invoke mappings, see the [`skills/README.md`](https://github.com/prowler-cloud/prowler/blob/master/skills/README.md) and [`AGENTS.md`](https://github.com/prowler-cloud/prowler/blob/master/AGENTS.md) in the repository.
+
+## Available Skills
+
+| Type | Skills |
+|------|--------|
+| **Generic** | typescript, react-19, nextjs-16, tailwind-4, pytest, playwright, django-drf, zod-4, zustand-5, ai-sdk-5, vitest, tdd |
+| **Prowler** | prowler, prowler-sdk-check, prowler-api, prowler-ui, prowler-mcp, prowler-provider, prowler-compliance, prowler-compliance-review, prowler-docs, prowler-pr, prowler-ci, prowler-attack-paths-query |
+| **Testing** | prowler-test-sdk, prowler-test-api, prowler-test-ui |
+| **Meta** | skill-creator, skill-sync |
+
+
+This table is a snapshot. The repository is the source of truth: see [`skills/README.md`](https://github.com/prowler-cloud/prowler/blob/master/skills/README.md) for the current, complete list.
+
+
+## Skill Structure
+
+Each skill follows the [Agent Skills spec](https://agentskills.io):
+
+```text
+skills/{skill-name}/
+├── SKILL.md # Patterns, rules, decision trees
+├── assets/ # Code templates, schemas
+└── references/ # Links to local docs (single source of truth)
+```
+
+## Key Design Decisions
+
+1. **Self-contained skills** - Critical patterns inline for fast loading
+2. **Local doc references** - No web URLs, points to `docs/developer-guide/*.mdx`
+3. **Single source of truth** - Skills reference docs, no duplication
+4. **On-demand loading** - AI loads only what's needed for the task
+
+## Creating New Skills
+
+Use the `skill-creator` meta-skill to create new skills that follow the Agent Skills spec. See [`AGENTS.md`](https://github.com/prowler-cloud/prowler/blob/master/AGENTS.md) for the full list of available skills and their triggers.
+
+## How Skills Work
+
+The diagrams below explain the internals of the skill system. They are useful for understanding the design, but are not required to install or use skills.
+
+### Architecture Overview
```mermaid
graph LR
@@ -28,7 +98,7 @@ graph LR
style F fill:#1a4d2e,stroke:#66bb6a,color:#fff
```
-## How It Works
+### Request Lifecycle
```mermaid
sequenceDiagram
@@ -68,7 +138,7 @@ sequenceDiagram
A->>U: Creates check with correct patterns
```
-## Before vs After
+### With and Without Skills
```mermaid
graph TD
@@ -96,7 +166,7 @@ graph TD
style AFTER fill:#1a4d1a,stroke:#66bb6a,color:#fff
```
-## Complete Architecture
+### Full Component Map
```mermaid
flowchart TB
@@ -110,7 +180,7 @@ flowchart TB
subgraph GENERIC["Generic Skills"]
G1["typescript"]
G2["react-19"]
- G3["nextjs-15"]
+ G3["nextjs-16"]
G4["tailwind-4"]
G5["pytest"]
G6["playwright"]
@@ -186,34 +256,3 @@ flowchart TB
style STRUCTURE fill:#5c3d1a,stroke:#ffb74d,color:#fff
style DOCS fill:#1a3d4d,stroke:#4dd0e1,color:#fff
```
-
-## Skills Included
-
-| Type | Skills |
-|------|--------|
-| **Generic** | typescript, react-19, nextjs-15, tailwind-4, pytest, playwright, django-drf, zod-4, zustand-5, ai-sdk-5 |
-| **Prowler** | prowler, prowler-sdk-check, prowler-api, prowler-ui, prowler-mcp, prowler-provider, prowler-compliance, prowler-compliance-review, prowler-docs, prowler-pr, prowler-ci |
-| **Testing** | prowler-test-sdk, prowler-test-api, prowler-test-ui |
-| **Meta** | skill-creator, skill-sync |
-
-## Skill Structure
-
-Each skill follows the [Agent Skills spec](https://agentskills.io):
-
-```
-skills/{skill-name}/
-├── SKILL.md # Patterns, rules, decision trees
-├── assets/ # Code templates, schemas
-└── references/ # Links to local docs (single source of truth)
-```
-
-## Key Design Decisions
-
-1. **Self-contained skills** - Critical patterns inline for fast loading
-2. **Local doc references** - No web URLs, points to `docs/developer-guide/*.mdx`
-3. **Single source of truth** - Skills reference docs, no duplication
-4. **On-demand loading** - AI loads only what's needed for the task
-
-## Creating New Skills
-
-Use the `skill-creator` meta-skill to create new skills that follow the Agent Skills spec. See `AGENTS.md` for the full list of available skills and their triggers.
diff --git a/docs/developer-guide/checks.mdx b/docs/developer-guide/checks.mdx
index 2f0f45cd96..5334799d36 100644
--- a/docs/developer-guide/checks.mdx
+++ b/docs/developer-guide/checks.mdx
@@ -445,3 +445,5 @@ The metadata structure is enforced in code using a Pydantic model. For reference
## Specific Check Patterns
Details for specific providers can be found in documentation pages named using the pattern `-details`.
+
+Checks that scan resources for plaintext secrets follow a dedicated batched structure. Refer to [Secret-Scanning Checks](/developer-guide/secret-scanning-checks) before creating or updating one.
diff --git a/docs/developer-guide/configurable-checks.mdx b/docs/developer-guide/configurable-checks.mdx
index 76b339601d..f550ff4f52 100644
--- a/docs/developer-guide/configurable-checks.mdx
+++ b/docs/developer-guide/configurable-checks.mdx
@@ -40,9 +40,184 @@ When adding a new configurable check to Prowler, update the following files:
# aws.awslambda_function_vpc_multi_az
lambda_min_azs: 2
```
+- **Provider Schema:** Add the typed field to the provider's Pydantic schema in `prowler/config/schema/.py`. This is required: the loader validates user configs against these schemas and the shipped `config.yaml` must round-trip with zero warnings. See [Adding a Parameter to the Provider Schema](#adding-a-parameter-to-the-provider-schema) below.
- **Test Fixtures:** If tests depend on this configuration, add the variable to `tests/config/fixtures/config.yaml`.
-- **Documentation:** Document the new variable in the list of configurable checks in `docs/tutorials/configuration_file.md`.
+- **Documentation:** Document the new variable in the list of configurable checks in [Configuration File](/user-guide/cli/tutorials/configuration_file) (`docs/user-guide/cli/tutorials/configuration_file.mdx`).
For a complete list of checks that already support configuration, see the [Configuration File Tutorial](/user-guide/cli/tutorials/configuration_file).
+
+Because a configurable check's verdict depends on the `audit_config` value it reads, a compliance requirement can lose meaning if the scan ran with a looser threshold than the control demands. Compliance frameworks can guard against this with **configuration guardrails**: a requirement declares the strictest configuration it tolerates and is forced to FAIL when the scan's config falls short. See [Configuration Guardrails for Requirements](/developer-guide/security-compliance-framework#configuration-guardrails-for-requirements).
+
+
+## Adding a Parameter to the Provider Schema
+
+Most providers have a typed Pydantic schema in `prowler/config/schema/`, registered in `prowler/config/schema/registry.py`. When a config is loaded and the provider has a registered schema, `validate_provider_config` checks each user-supplied key against it, logs a warning, and drops any field that fails validation. The consumer's `.get(key, default)` then falls back to the built-in default. Providers without a registered schema are passed through unchanged.
+
+This catches typos in a value (for example, `0.2` typed as `20`, or `"medium"` for an enum that expects `"MEDIUM"`). It does NOT catch typos in a key name: `disalowed_regions` (one `l` missing) is treated as an unknown key and passes through untouched, because third-party check plugins legitimately rely on unknown keys being preserved. Reviewers should still check that any new key the YAML adds is named exactly the same as the field on the schema.
+
+### Where to Add the Field
+
+1. Open `prowler/config/schema/.py` (for example, `aws.py`).
+2. Add a field on the provider's schema class. Always make it `Optional[...] = None` so the absence of the key is valid.
+3. Apply the tightest type the value allows. Examples below.
+
+If you are introducing an entirely new provider rather than a new parameter, also add an entry mapping the provider name to its schema class in `prowler/config/schema/registry.py`. The loader uses that registry to find the schema for the provider it is loading.
+
+### Choosing the Right Type
+
+| Value kind | Field declaration |
+|---|---|
+| Boolean toggle | `Optional[bool] = None` |
+| Strictly positive integer (days, counts) | `Optional[int] = Field(default=None, gt=0)` |
+| Fraction in 0..1 (threshold) | `Optional[float] = Field(default=None, ge=0.0, le=1.0)` |
+| Closed set of strings | `Optional[Literal["A", "B", "C"]] = None` |
+| Free-form string | `Optional[str] = None` |
+| List of strings or ints | `Optional[list[str]] = None` |
+
+Prefer `Literal[...]` over `str` whenever the value is one of a known set. Prefer `Field(gt=0)` over `int` whenever zero or negative would be nonsensical. The point of the schema is to catch real-world mistakes that previously passed silently.
+
+### Custom Validators (Only When Needed)
+
+If the value has structural rules beyond type and range, add a `field_validator`. Examples already in `aws.py`:
+
+- `_validate_port_range` rejects ports outside `0..65535`.
+- `_validate_account_ids` rejects anything that isn't a 12-digit AWS account ID.
+- `_validate_trusted_ips` rejects entries that aren't a valid IP or CIDR.
+
+Raise `ValueError` from the validator. The framework converts the error into a warning and drops the offending key.
+
+### Example: Adding a New Parameter
+
+Say a new check needs `max_iam_role_session_hours`, a strictly positive integer that defaults to 12 in code.
+
+1. **Schema** (`prowler/config/schema/aws.py`):
+ ```python
+ # IAM
+ max_iam_role_session_hours: Optional[int] = Field(default=None, gt=0)
+ ```
+2. **Shipped config** (`prowler/config/config.yaml`):
+ ```yaml
+ # aws.iam_role_session_duration_within_limit
+ max_iam_role_session_hours: 12
+ ```
+3. **Consumer** (the check):
+ ```python
+ max_hours = iam_client.audit_config.get("max_iam_role_session_hours", 12)
+ ```
+4. **Tests** in `tests/config/schema/aws_schema_test.py`:
+ - one test for a valid value that round-trips,
+ - one test for an invalid value (zero, negative, wrong type) that is dropped.
+
+### What the Loader Guarantees
+
+- **Unknown keys pass through.** Third-party check plugins can introduce arbitrary keys without schema edits; they will not be filtered.
+- **Invalid values never crash the run.** They produce a single warning per field and the key is dropped.
+- **Coerced values are normalized.** A YAML-quoted `"180"` for an `int` field arrives downstream as the integer `180`.
+- **The shipped `config.yaml` must round-trip cleanly.** The integration test `test_shipped_default_config_loads_without_warnings` will fail if a key is added to the YAML without a matching schema field, so the two stay in sync.
+
+## Configuration Value Limits
+
+Configurable thresholds enforce hard limits. A value outside the documented range is **dropped with a warning** and the check falls back to its built-in default (the same as if the key were absent). These bounds are intentionally conservative: they are not the absolute service maxima but the range that still produces a meaningful security check.
+
+Use this section as the reference when upgrading an existing config: if a value you set is being rejected, it is outside the range below.
+
+Only fields with a numeric range, a fixed value set, or a length cap are listed. Fields typed as free-form strings or lists (for example `disallowed_regions`, `secrets_ignore_patterns`, `trusted_account_ids`) have no range limit — they are validated for shape only (a 12-digit account ID, a valid IP/CIDR, a dotted version string), not for magnitude.
+
+### AWS
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `max_unused_access_keys_days` | `30..180` days | CIS AWS 1.13 recommends 45; NIST IA-5 ≤90 |
+| `max_console_access_days` | `30..180` days | CIS AWS 1.12 recommends 45 |
+| `max_unused_sagemaker_access_days` | `7..180` days | |
+| `max_security_group_rules` | `1..1000` | AWS hard limit is 1000 rules per security group |
+| `max_ec2_instance_age_in_days` | `1..1095` days | 3 years |
+| `ec2_high_risk_ports` | each port `1..65535` | port 0 is reserved |
+| `max_idle_disconnect_timeout_in_seconds` | `60..1800` s | NIST AC-12: cap at 30 min |
+| `max_disconnect_timeout_in_seconds` | `60..3600` s | |
+| `max_session_duration_seconds` | `600..86400` s | 10 min .. 24 h (AppStream per-session hard limit) |
+| `lambda_min_azs` | `1..6` | |
+| `recommended_cdk_bootstrap_version` | `1..100` | |
+| `log_group_retention_days` | one of `1, 3, 5, 7, 14, 30, 60, 90, 120, 150, 180, 365, 400, 545, 731, 1096, 1827, 2192, 2557, 2922, 3288, 3653` | only the CloudWatch Logs API-accepted retention values |
+| `threat_detection_privilege_escalation_threshold` | `0.0..1.0` | fraction of suspicious actions |
+| `threat_detection_privilege_escalation_minutes` | `5..43200` min | under 5 min the signal is mostly false positives |
+| `threat_detection_enumeration_threshold` | `0.0..1.0` | |
+| `threat_detection_enumeration_minutes` | `5..43200` min | |
+| `threat_detection_llm_jacking_threshold` | `0.0..1.0` | |
+| `threat_detection_llm_jacking_minutes` | `5..43200` min | |
+| `days_to_expire_threshold` (ACM) | `7..365` days | PCI-DSS 4.2.1.1: alert ≥30 days before expiry |
+| `elb_min_azs` | `1..6` | |
+| `elbv2_min_azs` | `1..6` | |
+| `minimum_snapshot_retention_period` | `1..35` days | ElastiCache service hard limit |
+| `max_days_secret_unused` | `7..365` days | |
+| `max_days_secret_unrotated` | `1..180` days | NIST IA-5: rotate quarterly; CIS ≤90 |
+| `min_kinesis_stream_retention_hours` | `24..8760` h | 1 day .. 1 year |
+| `shodan_api_key` | ≤512 chars | |
+
+### Azure
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `vm_backup_min_daily_retention_days` | `7..9999` days | Azure Backup hard limit; under 7 days defeats DR/ransomware recovery |
+| `apim_threat_detection_llm_jacking_threshold` | `0.0..1.0` | fraction of suspicious actions |
+| `apim_threat_detection_llm_jacking_minutes` | `5..43200` min | under 5 min the signal is mostly false positives |
+| `shodan_api_key` | ≤512 chars | |
+
+### GCP
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `mig_min_zones` | `1..5` | |
+| `max_snapshot_age_days` | `1..1095` days | 3 years |
+| `max_unused_account_days` | `30..365` days | |
+| `storage_min_retention_days` | `1..3650` days | |
+| `shodan_api_key` | ≤512 chars | |
+
+### Kubernetes
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `audit_log_maxbackup` | `2..1000` | CIS Kubernetes 1.2.18 recommends ≥10 |
+| `audit_log_maxsize` | `10..10000` MB | CIS Kubernetes 1.2.19 recommends ≥100 MB |
+| `audit_log_maxage` | `7..3650` days | CIS Kubernetes 1.2.17 recommends ≥30 days |
+
+### M365
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `sign_in_frequency` | `1..168` h | 1 h .. 7 days; Conditional Access baseline for admins ≤24 h |
+| `recommended_mailtips_large_audience_threshold` | `5..10000` | Microsoft default 25 |
+| `audit_log_age` | `30..3650` days | M365 E3 default 90 days; SEC/FINRA require ≥7 years |
+
+### GitHub
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `inactive_not_archived_days_threshold` | `30..3650` days | CIS GitHub recommends 180 |
+
+### Cloudflare
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `max_retries` | `0..10` | 0 disables retries |
+
+### MongoDB Atlas
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `max_service_account_secret_validity_hours` | `1..720` h | 1 h .. 30 days |
+
+### Vercel
+
+| Key | Allowed range | Notes |
+|---|---|---|
+| `days_to_expire_threshold` | `7..365` days | PCI-DSS 4.2.1.1: alert ≥30 days before expiry |
+| `stale_token_threshold_days` | `30..3650` days | NIST AC-2(3) typical window 30..90 days |
+| `stale_invitation_threshold_days` | `7..365` days | |
+| `max_owner_percentage` | `1..50` % | guidance recommends ≤25% |
+| `max_owners` | `1..1000` | absolute cap, overrides percentage for large teams |
+
+These bounds live in the provider schemas under `prowler/config/schema/`; each field's `Field(ge=..., le=...)` (or `field_validator`) is the source of truth and the descriptions there carry the full rationale.
+
This approach ensures that checks are easily configurable, making Prowler highly adaptable to different environments and requirements.
diff --git a/docs/developer-guide/documentation.mdx b/docs/developer-guide/documentation.mdx
index d0fb808af2..fd045a1751 100644
--- a/docs/developer-guide/documentation.mdx
+++ b/docs/developer-guide/documentation.mdx
@@ -8,9 +8,9 @@ Prowler documentation is built using [Mintlify](https://www.mintlify.com/docs),
The Prowler documentation is organized into several sections. The main ones are:
-- **Getting Started**: Provides an overview of the Prowler platform and its different solutions, including Prowler Cloud/App, Prowler CLI, Prowler MCP Server, Prowler Hub, and Prowler Lighthouse AI. This section helps new users understand which Prowler solution best fits their needs and includes product comparisons.
+- **Getting Started**: Provides an overview of the Prowler platform and its two product families, Prowler Products (Prowler Cloud, Prowler Hub, Prowler MCP, Prowler Lighthouse AI) and Open Source (Prowler CLI, Prowler Local Server). This section helps new users understand which Prowler solution best fits their needs and includes product comparisons.
-- **Guides**: Contains practical tutorials and how-to guides organized by product (Prowler Cloud/App, CLI) and provider (AWS, Azure, GCP, Kubernetes, Microsoft 365, GitHub, etc.). This section covers authentication, integrations, compliance, and advanced usage scenarios.
+- **Guides**: Contains practical tutorials and how-to guides organized by product (Prowler Cloud, CLI) and provider (AWS, Azure, GCP, Kubernetes, Microsoft 365, GitHub, etc.). This section covers authentication, integrations, compliance, and advanced usage scenarios.
- **Developer Guide**: Documentation for contributors looking to extend Prowler functionality. This includes guides on creating providers, services, checks, output formats, integrations, and compliance frameworks. Provider-specific implementation details and testing strategies are also covered here.
diff --git a/docs/developer-guide/end2end-testing.mdx b/docs/developer-guide/end2end-testing.mdx
index 0a62251531..df99de6fee 100644
--- a/docs/developer-guide/end2end-testing.mdx
+++ b/docs/developer-guide/end2end-testing.mdx
@@ -1,12 +1,12 @@
---
-title: 'End-2-End Tests for Prowler App'
+title: 'End-2-End Tests for Prowler Local Server'
---
-End-to-end (E2E) tests validate complete user flows in Prowler App (UI + API). These tests are implemented with [Playwright](https://playwright.dev/) under the `ui/tests` folder and are designed to run against a Prowler App environment.
+End-to-end (E2E) tests validate complete user flows in Prowler Local Server (UI + API). These tests are implemented with [Playwright](https://playwright.dev/) under the `ui/tests` folder and are designed to run against a Prowler Local Server environment.
## General Recommendations
-When adding or maintaining E2E tests for Prowler App, follow these guidelines:
+When adding or maintaining E2E tests for Prowler Local Server, follow these guidelines:
1. **Test real user journeys**
Focus on full workflows (for example, sign-up → login → add provider → launch scan) instead of low-level UI details already covered by unit or integration tests.
@@ -19,8 +19,8 @@ When adding or maintaining E2E tests for Prowler App, follow these guidelines:
3. **Use a Page Model (Page Object Model)**
- Encapsulate selectors and common actions in page classes instead of repeating them in each test.
- Leverage and extend the existing Playwright page models in `ui/tests`—such as `ProvidersPage`, `ScansPage`, and others—which are all based on the shared `BasePage`.
- - Page models for Prowler App pages should be placed in their respective entity folders (for example, `ui/tests/providers/providers-page.ts`).
- - Page models for external pages (not part of Prowler App) should be grouped in the `external` folder (for example, `ui/tests/external/github-page.ts`).
+ - Page models for Prowler Local Server pages should be placed in their respective entity folders (for example, `ui/tests/providers/providers-page.ts`).
+ - Page models for external pages (not part of Prowler Local Server) should be grouped in the `external` folder (for example, `ui/tests/external/github-page.ts`).
- This approach improves readability, reduces duplication, and makes refactors safer.
4. **Reuse authentication states (StorageState)**
@@ -193,7 +193,7 @@ When adding or maintaining E2E tests for Prowler App, follow these guidelines:
## Running Prowler Tests
-E2E tests for Prowler App run from the `ui` project using Playwright. The Playwright configuration lives in `ui/playwright.config.ts` and defines:
+E2E tests for Prowler Local Server run from the `ui` project using Playwright. The Playwright configuration lives in `ui/playwright.config.ts` and defines:
- `testDir: "./tests"` – location of E2E test files (relative to the `ui` project root, so `ui/tests`).
- `webServer` – how to start the Next.js development server and connect to Prowler API.
@@ -221,11 +221,11 @@ Before running E2E tests:
```
- **Ensure Prowler API is available**
- - By default, Playwright uses `NEXT_PUBLIC_API_BASE_URL=http://localhost:8080/api/v1` (configured in `playwright.config.ts`).
+ - By default, Playwright uses `UI_API_BASE_URL=http://localhost:8080/api/v1` (configured in `playwright.config.ts`).
- Start Prowler API so it is reachable on that URL (for example, via `docker-compose-dev.yml` or the development orchestration used locally).
- - If a different API URL is required, set `NEXT_PUBLIC_API_BASE_URL` accordingly before running the tests.
+ - If a different API URL is required, set `UI_API_BASE_URL` accordingly before running the tests.
-- **Ensure Prowler App UI is available**
+- **Ensure Prowler Local Server UI is available**
- Playwright automatically starts the Next.js server through the `webServer` block in `playwright.config.ts` (`pnpm run dev` by default).
- If the UI is already running on `http://localhost:3000`, Playwright will reuse the existing server when `reuseExistingServer` is `true`.
@@ -246,7 +246,7 @@ Before running E2E tests:
### Executing Tests
-To execute E2E tests for Prowler App:
+To execute E2E tests for Prowler Local Server:
1. **Run the full E2E suite (headless)**
diff --git a/docs/developer-guide/environment-variables.mdx b/docs/developer-guide/environment-variables.mdx
new file mode 100644
index 0000000000..913444d84b
--- /dev/null
+++ b/docs/developer-guide/environment-variables.mdx
@@ -0,0 +1,71 @@
+---
+title: 'Environment Variable Naming Convention'
+---
+
+Prowler is a monorepo composed of several runtime components — Prowler Local Server (the web user interface), Prowler API (the backend), Prowler SDK, and Prowler MCP Server (Model Context Protocol) — that frequently share a single `.env` file. To keep that shared configuration unambiguous, each component namespaces its environment variables with a component-specific prefix.
+
+## Component Prefixes
+
+Each component owns a dedicated prefix for the environment variables it reads:
+
+| Component | Prefix | Status |
+|-----------|--------|--------|
+| Prowler Local Server (web UI) | `UI_` | Adopted |
+| Prowler API (backend) | `API_` | Planned |
+| Prowler SDK | `SDK_` | Planned |
+| Prowler MCP Server | `MCP_` | Planned |
+
+## Why Component Prefixes Matter
+
+Component prefixes solve three concrete problems in a shared configuration file:
+
+- **Collisions in a shared `.env`:** Several components historically read identically named variables. The API base URL, for example, is consumed by more than one component, so a single unprefixed name is ambiguous. A component prefix removes that ambiguity.
+- **Explicit ownership:** A prefix states, at a glance, which component consumes a variable.
+- **Reduced accidental exposure:** For Prowler Local Server, scoping browser-facing configuration under one intentional prefix prevents server-only values from leaking into the client bundle.
+
+## Prowler Local Server
+
+Prowler Local Server has adopted the `UI_` prefix. Its public configuration is resolved from the container environment at runtime rather than inlined at build time, so a single pre-built image serves any deployment. For the operational details on changing these values without rebuilding the image, see [Troubleshooting](/troubleshooting).
+
+The former build-time variables map to the new runtime variables as follows:
+
+| Former variable | New variable |
+|-----------------|--------------|
+| `NEXT_PUBLIC_API_BASE_URL` | `UI_API_BASE_URL` |
+| `NEXT_PUBLIC_API_DOCS_URL` | `UI_API_DOCS_URL` |
+| `NEXT_PUBLIC_GOOGLE_TAG_MANAGER_ID` | `UI_GOOGLE_TAG_MANAGER_ID` |
+| `NEXT_PUBLIC_SENTRY_DSN`, `SENTRY_DSN` | `UI_SENTRY_DSN` |
+| `NEXT_PUBLIC_SENTRY_ENVIRONMENT`, `SENTRY_ENVIRONMENT` | `UI_SENTRY_ENVIRONMENT` |
+
+The build-time-only Sentry variables used for source-map upload — `SENTRY_ORG`, `SENTRY_PROJECT`, `SENTRY_AUTH_TOKEN`, and `SENTRY_RELEASE` — keep their names, as they are not part of Prowler Local Server's runtime configuration.
+
+## Enabling Third-Party Integrations
+
+Prowler Local Server gates each optional third-party integration behind an explicit enable flag. When an integration is configured through its new `UI_*` variables, it loads only when its flag is set to the exact string `"true"`; any other value, including unset, leaves it off. This default-off behavior keeps a deployment free of third-party egress unless it opts in. Deployments still using the deprecated legacy variable names keep loading without the flag, for backward compatibility (see [Deprecated Names](#deprecated-names)).
+
+| Integration | Enable flag | Required configuration when enabled |
+|-------------|-------------|-------------------------------------|
+| Sentry (error monitoring) | `UI_SENTRY_ENABLED` | `UI_SENTRY_DSN` |
+| Google Tag Manager | `UI_GOOGLE_TAG_MANAGER_ENABLED` | `UI_GOOGLE_TAG_MANAGER_ID` |
+| PostHog (product analytics) | `UI_POSTHOG_ENABLED` | `UI_POSTHOG_KEY` and `UI_POSTHOG_HOST` |
+
+When an integration is enabled but its required configuration is missing, Prowler Local Server fails fast at server startup with a clear error, so a misconfigured container never starts silently. A new `UI_*` value set while its enable flag is not `"true"` is ignored, and the server logs a one-time startup warning noting that the integration will not load. Legacy names follow the backward-compatible rule described in [Deprecated Names](#deprecated-names).
+
+PostHog support is currently limited to configuration validation: Prowler Local Server reads and validates the PostHog variables but does not yet load a PostHog client.
+
+
+Configuring an integration through the new `UI_*` variables now requires its enable flag. A deployment that adopted `UI_SENTRY_DSN` or `UI_GOOGLE_TAG_MANAGER_ID` must also set `UI_SENTRY_ENABLED=true` or `UI_GOOGLE_TAG_MANAGER_ENABLED=true` to keep the integration active. Deployments still using the legacy names (`NEXT_PUBLIC_*`, or `POSTHOG_KEY` and `POSTHOG_HOST`) keep working without the flag.
+
+
+## Upcoming Breaking Change
+
+
+Adopting the `API_`, `SDK_`, and `MCP_` prefixes for Prowler API, Prowler SDK, and Prowler MCP Server is a planned breaking change in a future release. Migrate environment configuration to the new names when upgrading.
+
+
+Prowler API, Prowler SDK, and Prowler MCP Server have not yet adopted the convention. In a future release, the variables each of these components reads will be namespaced under `API_`, `SDK_`, and `MCP_` respectively. The per-component mapping from current to prefixed names will be documented when each change is released.
+
+## Deprecated Names
+
+- **Prowler Local Server:** The bare server-side `SENTRY_DSN` and `SENTRY_ENVIRONMENT` are no longer read; the server and edge runtimes now read `UI_SENTRY_DSN` and `UI_SENTRY_ENVIRONMENT`. The former `NEXT_PUBLIC_*` names — and, for PostHog, the unprefixed `POSTHOG_KEY` and `POSTHOG_HOST` — are deprecated but stay backward compatible: they are read at runtime regardless of the enable flag, so an existing deployment keeps its integration active without opting in. The new `UI_*` names, by contrast, load only when the matching enable flag is set to `"true"`. These legacy names will be removed in a future release, so migrate to the `UI_*` runtime variables — and set the enable flag — on the running container.
+- **Prowler API, Prowler SDK, and Prowler MCP Server:** The current, unprefixed variable names are deprecated. They continue to work today and will be removed once the prefixed convention is adopted for each component, as described in [Upcoming Breaking Change](#upcoming-breaking-change).
diff --git a/docs/developer-guide/introduction.mdx b/docs/developer-guide/introduction.mdx
index 117640c669..08c38ee17c 100644
--- a/docs/developer-guide/introduction.mdx
+++ b/docs/developer-guide/introduction.mdx
@@ -108,6 +108,39 @@ uv sync
source .venv/bin/activate
```
+### Running the Local API Development Stack
+
+For API development, Prowler provides a Makefile-based local stack in addition to the manual and Docker Compose workflows documented in the API README. PostgreSQL, Valkey, and Neo4j run with Docker Compose, while Django and the Celery worker run natively through `uv`.
+
+Before using this method, ensure `docker compose`, `tmux`, and `uv` are installed.
+
+This workflow is designed for macOS and should also work on Linux when Docker, `tmux`, and `uv` are available. Windows requires script changes before it can be supported.
+
+To start the local API stack, run:
+
+```shell
+make dev
+```
+
+This command starts the required services, creates a `tmux` session with panes for the API, worker, and PostgreSQL logs, waits until the API responds, and prints the API URL and log file paths. The API is available at:
+
+```text
+http://localhost:8080/api/v1
+```
+
+Use these commands to manage the stack:
+
+```shell
+make dev-setup # Bootstrap dependencies, migrations, and fixtures
+make dev-attach # Attach to the tmux session
+make dev-launch # Start the stack on fixed ports and attach
+make dev-stop # Stop the tmux session and containers
+make dev-clean # Remove stopped development containers
+make dev-wipe # Stop everything and delete local development data
+make dev-status # Show development container status
+```
+
+The UI is not started by this workflow. Start it separately by following the UI development instructions in the `ui/` directory.
### Pre-Commit Hooks
@@ -207,7 +240,7 @@ prowler/
├── README.md # Project overview and getting started
├── Makefile # Common development commands
├── Dockerfile # SDK Docker container
-├── docker-compose.yml # Prowler App Docker compose
+├── docker-compose.yml # Prowler Local Server Docker compose
└── ... # Other supporting files
```
diff --git a/docs/developer-guide/lighthouse-architecture.mdx b/docs/developer-guide/lighthouse-architecture.mdx
index e8acc6278c..e12eff9549 100644
--- a/docs/developer-guide/lighthouse-architecture.mdx
+++ b/docs/developer-guide/lighthouse-architecture.mdx
@@ -132,7 +132,7 @@ The MCP client manages connections to the Prowler MCP Server using a singleton p
- **Connection Management**: Retry logic with configurable attempts and delays
- **Tool Discovery**: Fetches available tools from MCP server on initialization
-- **Authentication Injection**: Automatically adds JWT tokens to `prowler_app_*` tool calls
+- **Authentication Injection**: Automatically adds JWT tokens to `prowler_*` tool calls
- **Reconnection**: Supports forced reconnection after server restarts
Key constants:
@@ -141,10 +141,14 @@ Key constants:
- `RECONNECT_INTERVAL_MS`: 5 minutes before retry after failure
```typescript
-// Authentication injection for Prowler App tools
+// Authentication injection for core prowler_ tools (Hub/Docs excluded)
private handleBeforeToolCall = ({ name, args }) => {
- // Only inject auth for prowler_app_* tools (user-specific data)
- if (!name.startsWith("prowler_app_")) {
+ // Only inject auth for prowler_* tools (user-specific data).
+ // The legacy prowler_app_ prefix is also accepted for a resilient rollout.
+ if (
+ !name.startsWith("prowler_") &&
+ !name.startsWith("prowler_app_")
+ ) {
return { args };
}
@@ -307,15 +311,15 @@ MCP tools are organized into three namespaces based on authentication requiremen
| Namespace | Auth Required | Description |
|-----------|---------------|-------------|
-| `prowler_app_*` | Yes (JWT) | Prowler Cloud/App tools for findings, providers, scans, resources |
+| `prowler_*` | Yes (JWT) | Prowler Cloud, Prowler Private Cloud, and Prowler Local Server tools for findings, providers, scans, resources |
| `prowler_hub_*` | No | Security checks catalog, compliance frameworks |
| `prowler_docs_*` | No | Documentation search and retrieval |
### Authentication Flow
-1. User authenticates with Prowler App, receiving a JWT token
+1. User authenticates with Prowler Local Server, receiving a JWT token
2. Token is stored in session and propagated via `authContextStorage`
-3. MCP client injects `Authorization: Bearer ` header for `prowler_app_*` calls
+3. MCP client injects `Authorization: Bearer ` header for `prowler_*` calls
4. MCP Server validates token and applies RLS filtering
### Tool Execution Pattern
@@ -323,7 +327,7 @@ MCP tools are organized into three namespaces based on authentication requiremen
The agent uses meta-tools rather than direct tool registration:
```
-Agent needs data → describe_tool("prowler_app_search_findings")
+Agent needs data → describe_tool("prowler_search_findings")
→ Returns parameter schema → execute_tool with parameters
→ MCP client adds auth header → MCP Server executes
→ Results returned to agent → Agent continues reasoning
diff --git a/docs/developer-guide/llm-details.mdx b/docs/developer-guide/llm-details.mdx
index 3647552c0f..3dc0f2653d 100644
--- a/docs/developer-guide/llm-details.mdx
+++ b/docs/developer-guide/llm-details.mdx
@@ -101,4 +101,4 @@ The LLM provider seamlessly integrates with Prowler's existing infrastructure:
- **Output Formats**: Supports all Prowler output formats (JSON, CSV, HTML, etc.)
- **Compliance Frameworks**: Integrates with Prowler's compliance reporting
- **Fixer Integration**: Supports automated remediation recommendations
-- **Dashboard Integration**: Compatible with Prowler App for centralized management
+- **Dashboard Integration**: Compatible with Prowler Cloud and Prowler Local Server for centralized management
diff --git a/docs/developer-guide/mcp-server.mdx b/docs/developer-guide/mcp-server.mdx
index 4174f0f730..6d409ccc02 100644
--- a/docs/developer-guide/mcp-server.mdx
+++ b/docs/developer-guide/mcp-server.mdx
@@ -18,11 +18,15 @@ The Prowler MCP Server brings the entire Prowler ecosystem to AI assistants thro
The server follows a modular architecture with three independent sub-servers:
-| Sub-Server | Auth Required | Description |
-|------------|---------------|-------------|
-| Prowler App | Yes | Full access to Prowler Cloud and Self-Managed features |
-| Prowler Hub | No | Security checks catalog with **over 1000 checks**, fixers, and **70+ compliance frameworks** |
-| Prowler Documentation | No | Full-text search and retrieval of official documentation |
+| Sub-Server | Tool Prefix | Auth Required | Description |
+|------------|-------------|---------------|-------------|
+| Prowler | `prowler_` | Yes | Full access to Prowler Cloud, Prowler Private Cloud, and Prowler Local Server features |
+| Prowler Hub | `prowler_hub_` | No | Security checks catalog with **over 2,000 checks**, fixers, and **70+ compliance frameworks** |
+| Prowler Documentation | `prowler_docs_` | No | Full-text search and retrieval of official documentation |
+
+
+The core Prowler sub-server is served under the `prowler_` tool prefix, while its source lives in the `prowler_app/` module for historical reasons. Tool names use the prefix; import paths use the module.
+
For a complete list of tools and their descriptions, see the [Tools Reference](/getting-started/basic-usage/prowler-mcp-tools).
@@ -53,9 +57,9 @@ mcp_server/prowler_mcp_server/
The MCP Server uses two patterns for tool registration:
1. **Direct Decorators** (Prowler Hub/Docs): Tools are registered using `@mcp.tool()` decorators
-2. **Auto-Discovery** (Prowler App): All public methods of `BaseTool` subclasses are auto-registered
+2. **Auto-Discovery** (`prowler_app`): All public methods of `BaseTool` subclasses are auto-registered
-## Adding Tools to Prowler App
+## Adding Tools to the `prowler_app` Sub-Server
### Step 1: Create the Tool Class
@@ -413,7 +417,7 @@ uv run prowler-mcp
uv run prowler-mcp --transport http --host 0.0.0.0 --port 8000
# Run with environment variables
-PROWLER_APP_API_KEY="pk_xxx" uv run prowler-mcp
+PROWLER_API_KEY="pk_xxx" uv run prowler-mcp
```
For complete installation and deployment options, see:
diff --git a/docs/developer-guide/provider.mdx b/docs/developer-guide/provider.mdx
index d3e7d3631f..af621c005a 100644
--- a/docs/developer-guide/provider.mdx
+++ b/docs/developer-guide/provider.mdx
@@ -3211,21 +3211,18 @@ class YourProviderAPITestCase(APITestCase):
#### 2.6.1. Add your mocked provider to the tests
-If needed, add your mocked provider to the tests config file so you can use it on the tests.
+If needed, add a named provider fixture or extend the provider factory defaults so tests can request only the provider they need.
**File:** `api/src/backend/conftest.py`
```python
@pytest.fixture
-def providers_fixture(tenants_fixture):
- tenant, *_ = tenants_fixture
- providerX = Provider.objects.create(
+def your_provider(provider_factory):
+ return provider_factory(
provider="your_provider",
uid="your_uid",
alias="your_alias",
- tenant_id=tenant.id,
)
- return provider1, provider2, provider3, ... providerX
```
### 2.7. Compliance and Output Support
@@ -3421,7 +3418,7 @@ Use existing providers as templates, this will help you to understand better the
- **Documentation & Maintenance**
- **README Updates**: Update provider-specific documentation
- - **Changelog**: Document changes and new features
+ - **Changelog**: Document changes and new features with a fragment under `prowler/changelog.d/` (see the [Pull Request Template](https://github.com/prowler-cloud/prowler/blob/master/.github/pull_request_template.md))
- **Examples**: Provide usage examples and common scenarios
- **Troubleshooting**: Include common issues and solutions
- **Documentation**: Update the provider documentation to include your new tool provider in the examples and implementation guidance.
diff --git a/docs/developer-guide/prowler-studio.mdx b/docs/developer-guide/prowler-studio.mdx
index a4a2a609b5..b89eea7175 100644
--- a/docs/developer-guide/prowler-studio.mdx
+++ b/docs/developer-guide/prowler-studio.mdx
@@ -5,7 +5,7 @@ title: 'Prowler Studio'
**Prowler Studio is an AI workflow that ensures Claude Code follows Prowler's skills, guardrails, and best practices when creating new security checks.** What lands in the resulting pull request is consistent, tested, and ready for human review — not half-correct boilerplate that needs to be rewritten.
-**Contributor Tool**: Prowler Studio is a workflow for advanced contributors adding new Prowler security checks. It is not part of Prowler Cloud, Prowler App, or Prowler CLI.
+**Contributor Tool**: Prowler Studio is a workflow for advanced contributors adding new Prowler security checks. It is not part of Prowler Cloud, Prowler Local Server, or Prowler CLI.
diff --git a/docs/developer-guide/secret-scanning-checks.mdx b/docs/developer-guide/secret-scanning-checks.mdx
new file mode 100644
index 0000000000..5044366b7e
--- /dev/null
+++ b/docs/developer-guide/secret-scanning-checks.mdx
@@ -0,0 +1,119 @@
+---
+title: 'Secret-Scanning Checks'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+
+Since Prowler 5.32.0 the secret-scanning checks scan with Kingfisher. Earlier versions used the `detect-secrets` library.
+
+
+## Overview
+
+Secret detection runs through a single helper in `prowler/lib/utils/utils.py`:
+
+- **`detect_secrets_scan_batch(payloads, excluded_secrets=..., validate=...)`** scans many payloads in chunked subprocess invocations and returns a `{key: [findings]}` dictionary. To scan a single payload, pass a one-entry mapping (for example, `{0: data}`).
+
+Every Kingfisher invocation carries a fixed process-startup cost (around 100 ms). Scanning once per resource would spawn thousands of subprocesses on large accounts (for example, thousands of CloudWatch log groups). `detect_secrets_scan_batch` amortizes that cost: it writes each payload to a temporary file as it consumes them, runs one subprocess per chunk (500 payloads by default), and maps the findings back to each payload by key.
+
+## The Batched Structure
+
+Every secret-scanning check follows three phases.
+
+### Phase 1: Collect
+
+Define a generator that yields `(key, payload)` for each scannable unit. The generator builds payload strings only — it does not call Kingfisher. Lazy yielding keeps memory and temporary-disk usage bounded to a single chunk, which matters when an account holds thousands of resources.
+
+### Phase 2: Batch
+
+Call `detect_secrets_scan_batch` once with the generator. The helper consumes it in chunks, runs Kingfisher per chunk, and returns the keys that produced findings mapped to their finding lists.
+
+### Phase 3: Report
+
+Iterate the resources, look up the findings by key, and build one report per resource. Emit a finding for **every** iterated resource — never drop one silently. When a resource's payload cannot be prepared for scanning (for example, user data that fails to base64-decode or decompress), report it as `MANUAL` with a status explaining the scan could not inspect it, rather than omitting it or claiming `PASS`.
+
+```python
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.example.example_client import example_client
+
+
+class example_resource_no_secrets(Check):
+ def execute(self):
+ findings = []
+ excluded = example_client.audit_config.get("secrets_ignore_patterns", [])
+ validate = example_client.audit_config.get("secrets_validate", False)
+ resources = list(example_client.resources)
+
+ # Phase 1: collect — builds strings only, no scan.
+ def payloads():
+ for index, resource in enumerate(resources):
+ if resource.scannable_data:
+ yield index, serialize(resource)
+
+ # Phase 2: batch — one call, chunked subprocesses.
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=excluded, validate=validate
+ )
+
+ # Phase 3: report — look up findings by key.
+ for index, resource in enumerate(resources):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=resource)
+ report.status = "PASS"
+ report.status_extended = f"No secrets found in {resource.name}."
+ detect_secrets_output = batch_results.get(index)
+ if detect_secrets_output:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Potential secret found in {resource.name} -> ..."
+ )
+ annotate_verified_secrets(report, detect_secrets_output)
+ findings.append(report)
+
+ return findings
+```
+
+## Choosing the Key
+
+The key maps each finding back to its source. Two shapes cover every check:
+
+- **One payload per resource:** use the resource index. This fits checks that serialize a single payload per resource, such as launch configurations, CloudFormation outputs, SSM documents, Step Functions definitions, and OpenStack metadata.
+- **Several payloads per resource:** use a `(resource_index, fragment)` tuple, where the fragment identifies the variable, log stream, container, file, or version. Phase 3 groups the per-fragment findings to build the resource report. This fits CloudWatch log streams, ECS containers, CodeBuild variables, Glue arguments, and Lambda code files.
+
+Derive the indices from the same `list(...)` of resources in both Phase 1 and Phase 3 so the order stays stable and the keys align.
+
+## Preserving Per-Payload Results
+
+`detect_secrets_scan_batch` runs Kingfisher with `--no-dedup`, so a secret that appears in more than one payload is reported for each one. This reproduces the result of scanning each payload individually. Build payload strings exactly as a single scan would: serialize the same data and keep line ordering, because messages often map a finding's `line_number` back to a variable name or metadata key.
+
+## Validation and Severity
+
+`detect_secrets_scan_batch` accepts `validate`, read from `secrets_validate` in the provider configuration or the `--scan-secrets-validate` flag. When enabled, Kingfisher confirms whether each secret is live, and confirmed secrets carry `is_verified: True`.
+
+After marking a report as `FAIL`, pass the findings to `annotate_verified_secrets(report, findings)`. When any secret is verified, the helper escalates the finding to critical severity and appends a note that the secret was confirmed live. Validation stays off by default because it sends the discovered secret to the provider API.
+
+## Excluded Secrets
+
+`detect_secrets_scan_batch` applies `secrets_ignore_patterns` — regular expressions from the provider configuration — against each finding's source line and drops the matches, mirroring single-scan behavior.
+
+## Testing
+
+To assert on the verified-secret path, mock `detect_secrets_scan_batch` in the check module and return the keyed dictionary. For a single resource scanned at index `0`:
+
+```python
+mock.patch(
+ "prowler.providers.aws.services.example.example_resource_no_secrets.example_resource_no_secrets.detect_secrets_scan_batch",
+ return_value={
+ 0: [{"type": "...", "line_number": 1, "is_verified": True}]
+ },
+)
+```
+
+Most tests need no mock at all: they seed resources that contain example secrets and assert on the `FAIL` status and message, which exercises the real batched path. Refer to the [Testing](/developer-guide/unit-testing) documentation for the general structure.
diff --git a/docs/developer-guide/security-compliance-framework.mdx b/docs/developer-guide/security-compliance-framework.mdx
index 431849689f..2eeabebe2a 100644
--- a/docs/developer-guide/security-compliance-framework.mdx
+++ b/docs/developer-guide/security-compliance-framework.mdx
@@ -2,40 +2,231 @@
title: 'Creating a New Security Compliance Framework in Prowler'
---
-This guide explains how to add a new security compliance framework to Prowler, end to end. It covers directory layout, the JSON schema, check mapping conventions, the Pydantic models that validate each framework, the CSV output formatter, local validation, testing, and the pull request process.
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+This guide explains how to add a new security compliance framework to Prowler, end to end. It covers directory layout, the two supported JSON schemas (universal and legacy), the Pydantic models that validate each framework, check mapping conventions, output formatting, local validation, testing, and the pull request process.
## Introduction
-A compliance framework in Prowler maps a public or custom control catalog (for example CIS, NIST 800-53, PCI DSS, HIPAA, ENS, CCC) to the security checks that Prowler already runs. Each requirement links to zero, one or more Prowler checks. When a scan executes, findings are aggregated per requirement to produce the compliance report rendered by Prowler CLI and Prowler Cloud.
+A compliance framework in Prowler maps a public or custom control catalog (for example CIS, NIST 800-53, PCI DSS, HIPAA, ENS, CCC, DORA) to the security checks that Prowler already runs. Each requirement links to zero, one or more Prowler checks. When a scan executes, findings are aggregated per requirement to produce the compliance report rendered by Prowler CLI and Prowler Cloud.
-Prowler ships with 85+ compliance frameworks across All Providers. The catalog lives under `prowler/compliance//` (or `prowler/compliance/` for universal compliance frameworks)
+Prowler ships 85+ compliance frameworks across all providers. The catalog lives under `prowler/compliance//` (legacy, per-provider) or `prowler/compliance/` (universal, multi-provider).
-A compliance framework must represent the **complete state** of the source catalog. Every requirement defined by the framework has to be present in the JSON file, even when none of the existing Prowler checks can automate it. In that case, leave `Checks` as an empty array, but do not omit the requirement.
+A compliance framework must represent the **complete state** of the source catalog. Every requirement defined by the framework has to be present in the JSON file, even when no Prowler check can automate it. In that case, leave the requirement's check list empty, but do not omit the requirement.
Requirement coverage feeds the compliance percentage calculations and the metadata surfaces (dashboards, widgets, exports). Missing requirements skew those metrics and break the report as a faithful snapshot of the framework.
+### Two supported schemas
+
+| Schema | When to use | File location | Discovered as |
+| --- | --- | --- | --- |
+| **Universal (recommended for new frameworks)** | Multi-provider frameworks, or single-provider frameworks that benefit from declarative table/PDF rendering | `prowler/compliance/.json` (top-level) | Available for **every** provider whose key appears in any `requirement.checks` dict |
+| **Legacy provider-specific** | Single-provider frameworks with framework-specific attribute classes already declared in the codebase (CIS, ENS, ISO 27001, etc.) | `prowler/compliance//__.json` | Available only under that provider |
+
+Auto-discovery happens in `get_bulk_compliance_frameworks_universal(provider)` (`prowler/lib/check/compliance_models.py`), which scans **both** the top-level `prowler/compliance/` directory and every per-provider sub-directory. Legacy frameworks are transparently converted to the universal `ComplianceFramework` model via `adapt_legacy_to_universal()` before being returned, so the rest of Prowler — CLI table rendering, CSV/OCSF outputs, PDF generation — works the same regardless of the source schema.
+
+> The legacy entry-point `Compliance.get_bulk(provider)` (used by older code paths) only scans per-provider sub-directories. Universal top-level files are picked up exclusively via the universal loader; this matters if you are wiring a new code path against the legacy API.
+
+For **new** frameworks, prefer the universal schema: it requires no Python code changes, supports multiple providers in a single file, and table/PDF rendering is driven entirely from declarative configuration inside the JSON.
+
+> All Pydantic models in `compliance_models.py` are imported from `pydantic.v1`. Subclasses you add for the legacy schema must use `from pydantic.v1 import BaseModel`.
+
### Prerequisites
Before adding a new framework, complete the following checks:
-- **Verify the framework is not already supported.** Inspect `prowler/compliance//` for an existing JSON file matching the name and version.
+- **Verify the framework is not already supported.** Inspect `prowler/compliance/` and every `prowler/compliance//` for an existing JSON file matching the name and version.
- **Confirm the required checks exist.** Every requirement that can be automated must point to one or more existing Prowler checks. For each missing check, implement it first by following the [Prowler Checks](/developer-guide/checks) guide.
-- **Review a reference framework.** Use an existing framework with a similar structure as your template. `cis_2.0_aws.json` is the canonical reference for CIS-style frameworks. `ccc_aws.json`, `ens_rd2022_aws.json`, and `nist_800_53_revision_5_aws.json` illustrate other attribute shapes.
+- **Review a reference framework.** Use an existing framework with a similar structure as your template:
+ - Universal: `prowler/compliance/dora_2022_2554.json`, `prowler/compliance/csa_ccm_4.0.json`.
+ - Legacy: `prowler/compliance/aws/cis_2.0_aws.json` (canonical CIS shape), `prowler/compliance/aws/ccc_aws.json`, `prowler/compliance/aws/ens_rd2022_aws.json`, `prowler/compliance/aws/nist_800_53_revision_5_aws.json`.
-## Four-Layer Architecture
+## Universal Compliance Framework
-A compliance framework spans four layers. A complete contribution must touch each layer that applies.
+### Where the file lives
-- **Layer 1 – Schema validation:** The Pydantic models in `prowler/lib/check/compliance_models.py` define the canonical schema for each attribute shape (CIS, ENS, Mitre, CCC, C5, CSA CCM, ISO 27001, KISA ISMS-P, AWS Well-Architected, Prowler ThreatScore, and a generic fallback).
-- **Layer 2 – JSON catalog:** The framework JSON file in `prowler/compliance//` lists every requirement and maps it to checks.
-- **Layer 3 – Output formatter:** The Python module in `prowler/lib/outputs/compliance//` builds the CSV row model, the per-provider transformer, and the CLI summary table.
-- **Layer 4 – Output dispatchers:** The dispatchers in `prowler/lib/outputs/compliance/compliance.py` and `prowler/lib/outputs/compliance/compliance_output.py` route findings to the right formatter based on the framework identifier.
+Place the file at the top level of the compliance directory:
-The rest of this guide walks each layer in order.
+```
+prowler/compliance/.json
+```
-## Directory Structure and File Naming
+Examples in the repository: `prowler/compliance/csa_ccm_4.0.json`, `prowler/compliance/dora_2022_2554.json`.
+
+The file is auto-discovered — there is **no** need to register it in any `__init__.py`, modify `prowler/lib/outputs/`, or update any other Python module. The framework key Prowler CLI accepts via `--compliance` is the basename of the JSON file without `.json` (`dora_2022_2554.json` → `dora_2022_2554`).
+
+### Top-level structure
+
+```json
+{
+ "framework": "",
+ "name": "",
+ "version": "",
+ "description": "",
+ "icon": "",
+ "attributes_metadata": [ /* see below */ ],
+ "outputs": { /* see below — optional */ },
+ "requirements": [ /* see below */ ]
+}
+```
+
+A `provider` field at the top level is **optional**. The framework's effective provider list is derived by `ComplianceFramework.get_providers()` (`compliance_models.py`) from the union of all keys appearing in `requirement.checks` across all requirements; the explicit `provider` field is used **only as a fallback** when no requirement carries any `checks` key. This is what enables a single file (e.g. `dora_2022_2554.json`) to cover AWS today and add Azure / GCP / etc. tomorrow without restructuring.
+
+Provider keys inside `requirement.checks` must match the directory names under `prowler/providers/`. The valid keys at present are: `aws`, `azure`, `gcp`, `m365`, `kubernetes`, `iac`, `github`, `googleworkspace`, `alibabacloud`, `cloudflare`, `mongodbatlas`, `nhn`, `openstack`, `oraclecloud`, `llm`. Comparison in `supports_provider()` is case-insensitive, but lowercase is the convention used everywhere in the repository.
+
+### `attributes_metadata`
+
+Declares the shape of the per-requirement `attributes` dict. When this field is present, the root validator `validate_attributes_against_metadata` (`compliance_models.py`) enforces the schema at load time and rejects:
+
+- Missing keys marked `required: true`.
+- Keys present in `attributes` but not declared in `attributes_metadata` (typo / drift guard).
+- Values that violate a declared `enum`.
+- Values whose Python type does not match a declared `int`, `float` or `bool`.
+
+The runtime type check **only** covers `int`, `float` and `bool`. For `str`, `list_str` and `list_dict` the type is documentation-only — non-conforming values won't fail validation. If `attributes_metadata` is omitted, **no per-requirement validation runs at all**.
+
+```json
+"attributes_metadata": [
+ {
+ "key": "Pillar",
+ "label": "Pillar",
+ "type": "str",
+ "required": true,
+ "enum": [
+ "ICT Risk Management",
+ "ICT-Related Incident Reporting",
+ "Digital Operational Resilience Testing",
+ "ICT Third-Party Risk Management",
+ "Information Sharing"
+ ],
+ "output_formats": { "csv": true, "ocsf": true }
+ },
+ {
+ "key": "Article",
+ "label": "Article",
+ "type": "str",
+ "required": true,
+ "output_formats": { "csv": true, "ocsf": true }
+ }
+]
+```
+
+Per attribute:
+
+- `key` (required): attribute name as it will appear in `requirement.attributes`.
+- `label`: human-readable label used in CSV headers and PDF.
+- `type`: one of `str`, `int`, `float`, `bool`, `list_str`, `list_dict`. Defaults to `str`.
+- `enum`: optional list of allowed values; non-conforming values are rejected at load time.
+- `required`: if `true`, every requirement must include this key with a non-null value.
+- `enum_display` / `enum_order`: optional per-enum-value visual metadata (label, abbreviation, color, icon) and explicit ordering for PDF rendering.
+- `output_formats`: `{ "csv": , "ocsf": }` — toggles inclusion in each output format. Both default to `true`.
+
+### `outputs`
+
+Optional. Controls how the framework is rendered in the console table and in the generated PDF report. Skipping it falls back to sensible defaults.
+
+```json
+"outputs": {
+ "table_config": {
+ "group_by": "Pillar"
+ },
+ "pdf_config": {
+ "language": "en",
+ "primary_color": "#003399",
+ "secondary_color": "#0055A5",
+ "bg_color": "#F0F4FA",
+ "group_by_field": "Pillar",
+ "sections": [ "ICT Risk Management", "ICT-Related Incident Reporting", "..." ],
+ "section_short_names": { "ICT Risk Management": "ICT Risk Mgmt" },
+ "charts": [
+ {
+ "id": "pillar_compliance",
+ "type": "horizontal_bar",
+ "group_by": "Pillar",
+ "title": "Compliance Score by Pillar",
+ "y_label": "Pillar",
+ "x_label": "Compliance %",
+ "value_source": "compliance_percent",
+ "color_mode": "by_value"
+ }
+ ],
+ "filter": { "only_failed": true, "include_manual": false }
+ }
+}
+```
+
+`table_config.group_by` must reference an attribute key declared in `attributes_metadata`. The same applies to `pdf_config.group_by_field` and to every `charts[].group_by`.
+
+For frameworks with weighted scoring (e.g. ThreatScore) declare `pdf_config.scoring` with `risk_field` / `weight_field` / `risk_boost_factor`. For column splitting (e.g. CIS Level 1 vs Level 2) use `table_config.split_by`.
+
+### `requirements`
+
+```json
+"requirements": [
+ {
+ "id": "DORA-Art5",
+ "name": "Governance and organisation",
+ "description": "Financial entities shall have a sound, comprehensive and well-documented ICT internal governance and control framework. ...",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 5",
+ "ArticleTitle": "Governance and organisation"
+ },
+ "checks": {
+ "aws": [
+ "iam_avoid_root_usage",
+ "iam_no_root_access_key",
+ "iam_root_mfa_enabled"
+ ],
+ "azure": [],
+ "gcp": []
+ }
+ }
+]
+```
+
+Per requirement:
+
+- `id` (required): unique identifier within the framework.
+- `description` (required): the requirement text as authored by the framework.
+- `name`: short title shown alongside the id.
+- `attributes`: flat dict; keys must conform to `attributes_metadata`.
+- `checks`: dict keyed by provider name (the same lowercase keys listed in the previous section). Each value is a list of Prowler check names that evidence this requirement for that provider. The list **may be empty** and the dict itself defaults to `{}` if omitted; either way the requirement is still loaded and listed by `--list-compliance-requirements`, it just has zero checks to execute. Note: there is **no automatic check-existence validation** at load time — referencing a non-existent check name will silently produce a requirement with no findings. Validate this yourself (see "Validating Your Framework" below).
+- `config_requirements`: optional list of configuration guardrails. Each entry asserts that a configurable check referenced by this requirement ran with a configuration strict enough to actually satisfy the requirement; otherwise the requirement is forced to FAIL. See [Configuration Guardrails for Requirements](#configuration-guardrails-for-requirements) for the full schema and semantics. In the universal schema the field name is lowercase (`config_requirements`); legacy files use `ConfigRequirements`.
+
+For MITRE-style frameworks, additional optional fields are available on the requirement: `tactics`, `sub_techniques`, `platforms`, `technique_url` (these are populated automatically when adapting a legacy MITRE JSON to the universal model).
+
+### Multi-provider frameworks
+
+A single universal file can cover any number of providers. The framework appears under each provider's `--list-compliance` output as long as **at least one** requirement has that provider key in its `checks` dict.
+
+When extending an existing universal framework with a new provider, the only change required is editing `requirement.checks`:
+
+```diff
+ "checks": {
+ "aws": ["iam_avoid_root_usage", "iam_no_root_access_key"],
++ "azure": ["entra_policy_ensure_mfa_for_admin_roles"]
+ }
+```
+
+No code changes, no new file, no registration step.
+
+## Legacy Provider-Specific Compliance Framework
+
+The legacy schema is still fully supported and remains the format used by most frameworks shipped today (CIS, NIST, ISO 27001, FedRAMP, PCI DSS, GDPR, HIPAA, ENS, etc.). It binds a framework to a single provider and validates each requirement against a framework-specific Pydantic attribute class.
+
+The legacy schema spans **four layers** — a complete contribution must touch every layer that applies:
+
+- **Layer 1 — Schema validation:** the Pydantic models in `prowler/lib/check/compliance_models.py` define the canonical schema for each attribute shape.
+- **Layer 2 — JSON catalog:** the framework JSON file in `prowler/compliance//` lists every requirement and maps it to checks.
+- **Layer 3 — Output formatter:** the Python module in `prowler/lib/outputs/compliance//` builds the CSV row model, the per-provider transformer, and the CLI summary table.
+- **Layer 4 — Output dispatchers:** the dispatchers in `prowler/lib/outputs/compliance/compliance.py` and `prowler/lib/outputs/compliance/compliance_output.py` route findings to the right formatter based on the framework identifier.
+
+The universal schema collapses Layers 3 and 4 into declarative configuration inside the JSON — that is the main reason it is preferred for new contributions.
+
+### Directory structure and file naming
Compliance frameworks live at:
@@ -46,8 +237,8 @@ prowler/compliance//__.json
The filename conventions are:
- All lowercase, words separated with underscores.
-- `` is a supported provider identifier: `aws`, `azure`, `gcp`, `kubernetes`, `m365`, `github`, `googleworkspace`, `alibabacloud`, `oraclecloud`, `cloudflare`, `mongodbatlas`, `nhn`, `openstack`, `iac`, `llm`.
-- `` is optional. Omit it when the framework has no versioning, as in `ccc_aws.json`.
+- `` is a supported provider identifier (same lowercase list as the universal section above).
+- `` is optional but recommended. Omit only when the framework has no versioning (e.g. `ccc_aws.json`).
- The file basename (without `.json`) is the framework key that Prowler CLI accepts via `--compliance`.
Examples:
@@ -62,48 +253,51 @@ The output formatter directory mirrors the framework name:
```
prowler/lib/outputs/compliance//
-├── .py # CLI summary-table dispatcher
+├── .py # CLI summary-table dispatcher
├── _.py # Per-provider transformer class
├── models.py # Pydantic CSV row model
└── __init__.py
```
-## JSON Schema Reference
+### JSON schema reference
-Every compliance file is a JSON document with the following top-level keys.
+Every legacy compliance file is a JSON document with the following top-level keys. `Framework`, `Name` and `Provider` are validated non-empty by the root validator `framework_and_provider_must_not_be_empty` (`compliance_models.py`).
| Field | Type | Required | Description |
|---|---|---|---|
| `Framework` | string | Yes | Canonical framework identifier, for example `CIS`, `NIST-800-53-Revision-5`, `ENS`, `CCC`. |
-| `Name` | string | Yes | Human-readable framework name displayed by Prowler App. |
-| `Version` | string | Yes | Framework version, for example `2.0`. Use an empty string only for frameworks without versioning. See [Version Handling](#version-handling). |
+| `Name` | string | Yes | Human-readable framework name displayed by Prowler Cloud and Prowler Local Server. |
+| `Version` | string | Yes (recommended) | Framework version, e.g. `2.0`. See [Version Handling](#version-handling). |
| `Provider` | string | Yes | Upper-cased provider identifier: `AWS`, `AZURE`, `GCP`, `KUBERNETES`, `M365`, `GITHUB`, `GOOGLEWORKSPACE`, and so on. |
| `Description` | string | Yes | Short description of the framework's scope and purpose. |
| `Requirements` | array | Yes | List of [requirement objects](#requirement-object). |
-### Requirement Object
+#### Requirement Object
Each entry in `Requirements` describes one control or requirement.
| Field | Type | Required | Description |
|---|---|---|---|
| `Id` | string | Yes | Unique identifier within the framework, for example `1.10` or `CCC.Core.CN01.AR01`. |
-| `Name` | string | No | Optional human-readable name used by frameworks that distinguish control name from description, such as NIST. |
+| `Name` | string | No | Optional human-readable name (frameworks like NIST distinguish control name from description). |
| `Description` | string | Yes | Verbatim description from the source framework. |
| `Attributes` | array | Yes | List of [attribute objects](#attribute-objects). The shape depends on the framework. |
| `Checks` | array of strings | Yes | Prowler check identifiers that automate the requirement. Leave the list empty when the control cannot be automated. |
+| `ConfigRequirements` | array of objects | No | Optional [configuration guardrails](#configuration-guardrails-for-requirements). Each entry asserts that a configurable check ran with a configuration strict enough to satisfy the requirement; when it did not, the requirement is forced to FAIL. |
-### Attribute Objects
+#### Attribute Objects
-Attributes carry the metadata that Prowler App and the CSV output display for each requirement. The object shape is framework-specific and is validated by a dedicated Pydantic model in `prowler/lib/check/compliance_models.py`. The most common shapes are summarized below.
+`Attributes` is parsed against the union declared in `Compliance_Requirement.Attributes` (`compliance_models.py`). Pydantic v1 tries each member of the union in declaration order and falls back to `Generic_Compliance_Requirement_Attribute` (the last entry) when nothing else matches — so a brand-new shape that doesn't match any existing class will silently be accepted as Generic, losing its specific fields.
-#### CIS_Requirement_Attribute
+As of today, the registered attribute classes are: `CIS_Requirement_Attribute`, `ENS_Requirement_Attribute`, `ASDEssentialEight_Requirement_Attribute`, `ISO27001_2013_Requirement_Attribute`, `AWS_Well_Architected_Requirement_Attribute`, `KISA_ISMSP_Requirement_Attribute`, `Prowler_ThreatScore_Requirement_Attribute`, `CCC_Requirement_Attribute`, `C5Germany_Requirement_Attribute`, `CSA_CCM_Requirement_Attribute`, and `Generic_Compliance_Requirement_Attribute` (fallback). MITRE-style frameworks use the separate `Mitre_Requirement` model with `Tactics` / `SubTechniques` / `Platforms` / `TechniqueURL` at the requirement top level. The most common shapes are summarized below.
+
+##### CIS_Requirement_Attribute
Used by every CIS benchmark.
| Field | Type | Required | Notes |
|---|---|---|---|
-| `Section` | string | Yes | Top-level section, for example `1 Identity and Access Management`. |
+| `Section` | string | Yes | Top-level section, e.g. `1 Identity and Access Management`. |
| `SubSection` | string | No | Optional second-level grouping. |
| `Profile` | enum | Yes | One of `Level 1`, `Level 2`, `E3 Level 1`, `E3 Level 2`, `E5 Level 1`, `E5 Level 2`. |
| `AssessmentStatus` | enum | Yes | `Manual` or `Automated`. |
@@ -116,7 +310,7 @@ Used by every CIS benchmark.
| `DefaultValue` | string | No | Default configuration value, when relevant. |
| `References` | string | Yes | Colon-separated list of reference URLs. |
-#### ENS_Requirement_Attribute
+##### ENS_Requirement_Attribute
Used by the Spanish ENS (Esquema Nacional de Seguridad) frameworks.
@@ -132,13 +326,13 @@ Used by the Spanish ENS (Esquema Nacional de Seguridad) frameworks.
| `ModoEjecucion` | string | Yes | Execution mode (`manual`, `automático`, `híbrido`). |
| `Dependencias` | array of strings | Yes | Ids of prerequisite controls. Empty list when none. |
-#### CCC_Requirement_Attribute
+##### CCC_Requirement_Attribute
Used by the Common Cloud Controls Catalog.
| Field | Type | Required | Notes |
|---|---|---|---|
-| `FamilyName` | string | Yes | Control family, for example `Data`. |
+| `FamilyName` | string | Yes | Control family, e.g. `Data`. |
| `FamilyDescription` | string | Yes | Description of the family. |
| `Section` | string | Yes | Section title. |
| `SubSection` | string | Yes | Subsection title, or empty string. |
@@ -148,9 +342,9 @@ Used by the Common Cloud Controls Catalog.
| `SectionThreatMappings` | array of objects | Yes | Each entry has `ReferenceId` and `Identifiers`. |
| `SectionGuidelineMappings` | array of objects | Yes | Each entry has `ReferenceId` and `Identifiers`. |
-#### Generic_Compliance_Requirement_Attribute
+##### Generic_Compliance_Requirement_Attribute
-The fallback attribute model used when no framework-specific schema applies (for example NIST 800-53, PCI DSS, GDPR, HIPAA).
+The fallback attribute model used when no framework-specific schema applies (e.g. NIST 800-53, PCI DSS, GDPR, HIPAA). It is **always the last** element of the `Compliance_Requirement.Attributes` Union; that ordering is load-bearing.
| Field | Type | Required | Notes |
|---|---|---|---|
@@ -158,17 +352,17 @@ The fallback attribute model used when no framework-specific schema applies (for
| `Section` | string | No | Section name. |
| `SubSection` | string | No | Subsection name. |
| `SubGroup` | string | No | Subgroup name. |
-| `Service` | string | No | Affected service, for example `aws`, `iam`. |
+| `Service` | string | No | Affected service, e.g. `iam`. |
| `Type` | string | No | Control type. |
| `Comment` | string | No | Free-form comment. |
-Additional per-framework attribute models exist for `AWS_Well_Architected_Requirement_Attribute`, `ISO27001_2013_Requirement_Attribute`, `Mitre_Requirement_Attribute_`, `KISA_ISMSP_Requirement_Attribute`, `Prowler_ThreatScore_Requirement_Attribute`, `C5Germany_Requirement_Attribute`, and `CSA_CCM_Requirement_Attribute`. Consult `prowler/lib/check/compliance_models.py` for their full field sets.
+For the remaining attribute classes (`AWS_Well_Architected_Requirement_Attribute`, `ISO27001_2013_Requirement_Attribute`, `Mitre_Requirement_Attribute_`, `KISA_ISMSP_Requirement_Attribute`, `Prowler_ThreatScore_Requirement_Attribute`, `C5Germany_Requirement_Attribute`, `CSA_CCM_Requirement_Attribute`) consult `prowler/lib/check/compliance_models.py` for the full field sets.
-The `Attributes` field is a Pydantic `Union`. The generic attribute model must remain the last element of that Union, otherwise Pydantic v1 silently coerces every framework into the generic shape and your specialized fields are dropped.
+The `Attributes` field is a Pydantic `Union`. The generic attribute model **must** remain the last element of that Union — otherwise Pydantic v1 silently coerces every framework into the generic shape and your specialized fields are dropped. Adding a brand-new attribute shape requires inserting the Pydantic class **before** `Generic_Compliance_Requirement_Attribute`.
-## Minimal Working Example
+#### Minimal working example
The following snippet is a complete, valid framework file named `my_framework_1.0_aws.json`, saved at `prowler/compliance/aws/my_framework_1.0_aws.json`. It uses the generic attribute shape for simplicity.
@@ -214,26 +408,26 @@ The following snippet is a complete, valid framework file named `my_framework_1.
}
```
-## Mapping Checks to Requirements
+### Mapping checks to requirements
Each requirement links to the Prowler checks that, together, produce a PASS or FAIL verdict for that control.
-- **Include every requirement from the source catalog.** The framework file must mirror the full control list, one-to-one. Compliance percentages, dashboards, and exported metadata are computed against the total requirement count, so omitting an unmappable control inflates coverage and misrepresents the framework.
-- List every check by its canonical identifier, the value of `CheckID` inside the check's `.metadata.json` file.
+- **Include every requirement from the source catalog.** The framework file must mirror the full control list, one-to-one. Compliance percentages, dashboards, and exported metadata are computed against the total requirement count.
+- List every check by its canonical identifier — the value of `CheckID` inside the check's `.metadata.json` file.
- One requirement can reference multiple checks. The requirement is evaluated as FAIL when any referenced check produces a FAIL finding for a resource in scope.
-- Leave `Checks` as an empty array when the requirement cannot be automated. The requirement still appears in the report, contributes to the total, and resolves to `MANUAL`. An empty mapping is valid; a missing requirement is not.
+- Leave `Checks` (legacy) or `checks.` (universal) as an empty array when the requirement cannot be automated. The requirement still appears in the report and contributes to the total.
- Reuse checks across requirements when the same control applies in multiple places. Do not duplicate check logic to match framework structure.
-- Avoid referencing checks from a different provider. A compliance file is bound to one provider, and cross-provider checks will never match findings in the scan.
+- Avoid referencing checks from a different provider. A legacy compliance file is bound to one provider, and cross-provider checks will never match findings in the scan.
-To discover available checks, run:
+To discover available checks:
```bash
uv run python prowler-cli.py --list-checks
```
-## Supporting Multiple Providers
+### Supporting multiple providers (legacy)
-Each compliance file targets a single provider. To cover several providers with the same framework (for example CIS across AWS, Azure, and GCP), ship one JSON file per provider:
+The legacy schema binds each file to a single provider. To cover several providers with the same framework, ship one JSON file per provider:
```
prowler/compliance/aws/cis_2.0_aws.json
@@ -241,15 +435,15 @@ prowler/compliance/azure/cis_2.0_azure.json
prowler/compliance/gcp/cis_2.0_gcp.json
```
-Keep the `Framework` and `Version` values identical across the files so the dispatcher matches them, and change only the `Provider`, `Checks`, and provider-specific metadata.
+Keep the `Framework` and `Version` values identical across the files so the dispatcher matches them; change only the `Provider`, `Checks`, and provider-specific metadata. The CIS output formatter already supports every provider listed above.
-The CIS output formatter already supports every provider listed above. For a brand-new framework that spans several providers, add one transformer per provider in `prowler/lib/outputs/compliance//` and extend the summary-table dispatcher accordingly. See [Output Formatter](#output-formatter).
+For a brand-new framework that spans several providers, **prefer the universal schema** — it covers every provider from a single file. If you must use the legacy schema, add one transformer per provider in `prowler/lib/outputs/compliance//` and extend the summary-table dispatcher accordingly. See [Output Formatter](#output-formatter).
-## Output Formatter
+### Output formatter
-Prowler renders every compliance framework in two forms: a detailed CSV report written to disk, and a summary table printed in the CLI. Both are produced by the output formatter package for the framework.
+Legacy frameworks render in two forms: a detailed CSV report written to disk, and a summary table printed in the CLI. Both are produced by the output formatter package for the framework. Universal frameworks do **not** need a Python output formatter — the `outputs` config inside the JSON drives rendering — so this section applies only to the legacy schema.
-For a new framework named `my_framework`, create:
+For a new legacy framework named `my_framework`, create:
```
prowler/lib/outputs/compliance/my_framework/
@@ -259,19 +453,19 @@ prowler/lib/outputs/compliance/my_framework/
└── models.py # CSV row Pydantic model
```
-### Step 1 – Define the CSV Row Model
+#### Step 1 — Define the CSV row model
In `models.py`, declare a Pydantic v1 model with one field per CSV column. Use existing models such as `AWSCISModel` in `prowler/lib/outputs/compliance/cis/models.py` as the reference. Fields typically include `Provider`, `Description`, `AccountId`, `Region`, `AssessmentDate`, `Requirements_Id`, `Requirements_Description`, one `Requirements_Attributes_*` field per attribute key, plus the finding fields `Status`, `StatusExtended`, `ResourceId`, `ResourceName`, `CheckId`, `Muted`, `Framework`, `Name`.
-### Step 2 – Implement the Transformer Class
+#### Step 2 — Implement the transformer
In `my_framework_aws.py`, subclass `ComplianceOutput` from `prowler.lib.outputs.compliance.compliance_output` and implement `transform(findings, compliance, compliance_name)`. Iterate over `findings`, match each finding to the requirements it satisfies through `finding.compliance.get(compliance_name, [])`, and append one row per attribute to `self._data`.
-### Step 3 – Add the Summary-Table Dispatcher
+#### Step 3 — Add the summary-table dispatcher
In `my_framework.py`, implement `get_my_framework_table(findings, bulk_checks_metadata, compliance_framework, output_filename, output_directory, compliance_overview)` following the pattern in `prowler/lib/outputs/compliance/cis/cis.py`.
-### Step 4 – Register the Framework in the Dispatchers
+#### Step 4 — Register the framework in the dispatchers
- Add the dispatcher call in `prowler/lib/outputs/compliance/compliance.py`, inside `display_compliance_table`, with a branch such as `elif "my_framework" in compliance_framework:`.
- Register the CSV model and transformer in `prowler/lib/outputs/compliance/compliance_output.py` so the CSV file is emitted during the scan.
@@ -280,58 +474,278 @@ In `my_framework.py`, implement `get_my_framework_table(findings, bulk_checks_me
For NIST-style catalogs that use `Generic_Compliance_Requirement_Attribute`, no custom formatter is needed. The generic formatter in `prowler/lib/outputs/compliance/generic/` handles them automatically, provided the JSON validates against the generic attribute schema.
-## Version Handling
+### Legacy-to-universal adapter
+
+At load time, every legacy file is transparently adapted to a `ComplianceFramework` via `adapt_legacy_to_universal()` (`compliance_models.py`), which: (a) flattens the first element of `Attributes` into a flat `attributes` dict, (b) wraps `Checks` as `{provider_lower: [...]}`, (c) infers `attributes_metadata` from the matched Pydantic class via `_infer_attribute_metadata()`. The rest of Prowler (CSV/OCSF/PDF output, CLI table) then treats both formats identically.
+
+Loader-error behaviour differs between the two entry points:
+
+- `load_compliance_framework()` (legacy) is **fail-fast**: it calls `sys.exit(1)` on any `ValidationError` (`compliance_models.py`).
+- `load_compliance_framework_universal()` is more lenient — it logs the error and returns `None`, so `get_bulk_compliance_frameworks_universal()` simply skips the broken file and keeps loading the rest.
+
+## Configuration Guardrails for Requirements
+
+
+Guardrails are an **optional** safety net for configurable checks. A requirement that maps only to non-configurable checks does not need them. When the field is absent, behavior is unchanged.
+
+
+### Where guardrails are declared
+
+The field is attached to each requirement and exists in both schemas:
+
+- **Legacy** (`prowler/compliance//...`): `ConfigRequirements`, a list of objects, validated against the `Compliance_Requirement_ConfigConstraint` Pydantic model (`prowler/lib/check/compliance_models.py`).
+- **Universal** (`prowler/compliance/...`): `config_requirements`, the same list of objects as plain dicts on `UniversalComplianceRequirement`.
+
+When a legacy file is adapted to the universal model, `adapt_legacy_to_universal()` copies `ConfigRequirements` into `config_requirements` (`compliance_models.py`), so downstream code only ever reads one shape.
+
+### Constraint schema
+
+Each entry in the list is a single constraint with the following fields:
+
+| Field | Type | Required | Description |
+|---|---|---|---|
+| `Check` | string | Yes | The configurable check this constraint guards. Should be one of the requirement's `Checks`. Used only to build a human-readable reason. |
+| `ConfigKey` | string | Yes | The `audit_config` key the check reads (for example `max_unused_access_keys_days`). |
+| `Operator` | enum | Yes | How to compare the applied value against `Value`. One of `lte`, `gte`, `eq`, `in`, `subset`, `superset`. |
+| `Value` | bool, int, float, string, or list | Yes | The strictest configuration the requirement tolerates. The accepted Python type depends on the operator (see below). |
+| `Provider` | string | No | The provider this constraint applies to (e.g. `aws`). **Required for universal (multi-provider) frameworks**, where the same requirement maps checks across providers — the constraint is only evaluated when the scanned provider matches. Single-provider (legacy) frameworks omit it. |
+
+### Operators
+
+| Operator | Applied value satisfies the guardrail when… | Typical use |
+|---|---|---|
+| `lte` | `applied <= Value` | Maximum-age / maximum-count thresholds (e.g. `max_unused_access_keys_days <= 45`). |
+| `gte` | `applied >= Value` | Minimum-retention / minimum-count thresholds. |
+| `eq` | `applied == Value` | Boolean toggles or an exact required value (e.g. `mute_non_default_regions == false`). |
+| `in` | `applied` is one of `Value` (a list) | The applied scalar must belong to an allowed set. |
+| `subset` | `set(applied) <= set(Value)` | **Allowlist** configs — every applied value must already be permitted. Widening the allowlist with a weaker value (e.g. adding TLS `1.0` to `recommended_minimal_tls_versions`) breaks the guardrail. |
+| `superset` | `set(applied) >= set(Value)` | **Denylist** configs — every forbidden value must remain forbidden. Removing an entry from a denylist (e.g. dropping a weak algorithm from `insecure_key_algorithms`) breaks the guardrail. |
+
+
+`subset` / `superset` require both the applied value and `Value` to be lists; any other type is treated as not satisfied. For `eq` against a boolean, declare `Value` as a JSON boolean (`false`, not `0`) — the model keeps booleans distinct from integers.
+
+
+### How guardrails are evaluated
+
+All evaluation lives in one shared module, `prowler/lib/check/compliance_config_eval.py`, consumed by every compliance output (CSV, OCSF, and the CLI tables) and reused by the Prowler API backend so the rule is defined exactly once.
+
+1. The applied configuration is the scan-global `audit_config` (the same mapping for every resource and region), resolved via `get_scan_audit_config()`.
+2. For each requirement that declares constraints, `evaluate_config_constraints()` walks the list and returns `(is_compliant, reason)`. The requirement is compliant when **every** explicitly-set key satisfies its constraint.
+3. A constraint tagged with a `Provider` that does **not** match the provider being scanned (resolved via `get_scan_provider_type()`) is **skipped**. This scopes a universal framework's constraints to the right provider, so a guardrail authored for an AWS check never affects a GCP or Azure scan of the same requirement. Untagged constraints (legacy single-provider frameworks) always apply.
+4. A constraint whose `ConfigKey` is **not present** in `audit_config` is **skipped** — the check's built-in default is assumed to already match what the requirement expects. This is why nothing changes for the default configuration.
+5. When a constraint is violated, the finding's status is overridden to `FAIL` and a plain-language explanation is prepended to `status_extended` (via `apply_config_status()`). The message opens with `Configuration not valid for this requirement.` and names the check, the value the scan applied, what the requirement needs and how to fix it. For the table generators, `get_effective_status()` applies the same FAIL roll-up so per-section counts stay consistent.
+
+
+Guardrails only ever make a result **stricter** (they can turn PASS into FAIL); they never relax a real FAIL into PASS. A requirement with no constraints, or whose keys all use defaults, is reported exactly as before.
+
+
+### Example: legacy framework
+
+From `prowler/compliance/aws/cis_6.0_aws.json`, requirement 2.11 declares two guardrails — one per configurable check it maps to:
+
+```json title="prowler/compliance/aws/cis_6.0_aws.json"
+{
+ "Id": "2.11",
+ "Description": "Ensure credentials unused for 45 days or more are disabled.",
+ "Checks": [
+ "iam_user_accesskey_unused",
+ "iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
+ "Attributes": [ /* ... */ ]
+}
+```
+
+A boolean guardrail from the same file: requirement 2.5 (IAM Access Analyzer) only holds when regions are not muted, so a scan with `mute_non_default_regions: true` cannot be trusted for it:
+
+```json
+"ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+]
+```
+
+### Example: universal framework
+
+The universal schema uses the lowercase `config_requirements` key with the identical object shape:
+
+```json
+{
+ "id": "MF-2.1",
+ "name": "Restrict TLS to modern versions",
+ "description": "Endpoints must negotiate only TLS 1.2 or higher.",
+ "checks": {
+ "aws": ["elbv2_listener_ssl_listeners"]
+ },
+ "config_requirements": [
+ {
+ "Check": "elbv2_listener_ssl_listeners",
+ "Provider": "aws",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": ["TLS 1.2", "TLS 1.3"]
+ }
+ ]
+}
+```
+
+Each constraint declares the `Provider` it targets so the guardrail is only evaluated on scans of that provider — essential for universal frameworks like CSA CCM and DORA, where one requirement maps checks across `aws`, `azure`, `gcp` and more. Because the operator is `subset`, adding `"TLS 1.0"` to `recommended_minimal_tls_versions` widens the allowlist beyond `["TLS 1.2", "TLS 1.3"]` and the requirement is forced to FAIL.
+
+### What the user sees
+
+With a loosened config, the affected requirement's findings report:
+
+```text
+Status: FAIL
+StatusExtended: Configuration not valid for this requirement. The check
+ iam_user_accesskey_unused has max_unused_access_keys_days set
+ to 120, but the requirement needs a value of 45 or lower.
+ Update it to 45 or lower.
+```
+
+The same `Configuration not valid for this requirement.` message appears identically across the CSV, OCSF, and console-table outputs.
+
+### Authoring guidelines
+
+- Declare a guardrail only for keys whose value actually changes whether the requirement is met. Most configurable checks do not need one.
+- Set `Value` to the **strictest** configuration the control tolerates — the same number the control text cites (CIS 45 days, NIST ≤90, and so on).
+- Keep `ConfigKey` spelled exactly as the check reads it from `audit_config`; an unknown key is never present in the config and the constraint is silently skipped.
+- In a **universal (multi-provider) framework**, always set `Provider` to the provider that owns `Check` — otherwise the guardrail would leak onto scans of the other providers the requirement maps. Legacy single-provider files omit it.
+- Pick the operator from the value's role: a max threshold is `lte`, a min threshold is `gte`, a toggle is `eq`, an allowlist is `subset`, a denylist is `superset`.
+- An unrecognized operator does **not** block the requirement — a malformed constraint is treated as satisfied rather than failing the whole framework. Validate your JSON with the tests below.
+
+### Testing guardrails
+
+The shared evaluator and the per-output integration are covered by:
+
+- `tests/lib/check/compliance_config_eval_test.py` — operator semantics, skipped-key behavior, and the FAIL override.
+- `tests/lib/check/compliance_config_constraint_model_test.py` — model validation (types, operator enum, bool-vs-int).
+- `tests/lib/check/compliance_config_requirements_data_test.py` — sanity-checks the guardrails shipped in the JSON catalog.
+- Per-output tests under `tests/lib/outputs/compliance/` (CIS AWS/Azure, ENS AWS, OCSF, universal table) confirm the override reaches each format.
+
+Run them with:
+
+```bash
+uv run pytest -n auto \
+ tests/lib/check/compliance_config_eval_test.py \
+ tests/lib/check/compliance_config_constraint_model_test.py \
+ tests/lib/check/compliance_config_requirements_data_test.py \
+ tests/lib/outputs/compliance/
+```
+
+## Version handling
Prowler matches frameworks by concatenating `Framework` and `Version`. A missing or empty `Version` collapses several frameworks to the same key and breaks CLI filtering with `--compliance`.
-- Always set `Version` to a non-empty string, even for frameworks that rename editions rather than version them. Use the edition identifier (for example `RD2022`, `v2025.10`, `4.0`).
+- Always set `Version` (or `version` for universal frameworks) to a non-empty string, even for frameworks that rename editions rather than version them. Use the edition identifier (for example `RD2022`, `v2025.10`, `4.0`, `2022/2554`).
- When the source catalog has no version, use the first year of adoption or the release date.
-- Make sure the version substring embedded in the filename matches `Version`, because the CLI dispatcher reads `compliance_framework.split("_")[1]` to select the correct version.
+- For **legacy** files, make sure the version substring embedded in the filename matches `Version`, because the CLI dispatcher reads `compliance_framework.split("_")[1]` to select the correct version.
-## Validating the Framework Locally
+## Validating Your Framework
-Follow the steps below before opening a pull request.
+Before opening a PR, validate the JSON loads cleanly against the model and that every referenced check actually exists.
-### 1. Run the Compliance Model Validator
+### 1. Schema validation
+
+For **universal** frameworks, load the file and inspect what was parsed. The framework key inside `bulk` is the **basename of the JSON file** (without `.json`); for `prowler/compliance/dora_2022_2554.json` that key is `dora_2022_2554`, for `prowler/compliance/aws/cis_5.0_aws.json` it is `cis_5.0_aws`.
+
+```python
+from prowler.lib.check.compliance_models import (
+ load_compliance_framework_universal,
+ get_bulk_compliance_frameworks_universal,
+)
+
+fw = load_compliance_framework_universal("prowler/compliance/.json")
+assert fw is not None, "load returned None — check the logs for the validation error"
+print(fw.framework, len(fw.requirements), fw.get_providers())
+
+bulk = get_bulk_compliance_frameworks_universal("aws")
+assert "" in bulk
+```
+
+### 2. Check existence cross-check
+
+There is **no automatic check-existence validation** at load time. Cross-check that every check name in your framework maps to a real check directory:
+
+```python
+import os
+real = set()
+for svc in os.listdir("prowler/providers/aws/services"):
+ svc_path = f"prowler/providers/aws/services/{svc}"
+ if not os.path.isdir(svc_path):
+ continue
+ for entry in os.listdir(svc_path):
+ if os.path.isfile(f"{svc_path}/{entry}/{entry}.metadata.json"):
+ real.add(entry)
+
+referenced = {c for r in fw.requirements for c in r.checks.get("aws", [])}
+missing = referenced - real
+assert not missing, f"checks referenced in framework but not found in repo: {sorted(missing)}"
+```
+
+### 3. CLI smoke test
```bash
uv run python prowler-cli.py --list-compliance
```
-The framework must appear in the output. A validation error indicates a schema mismatch between the JSON file and the attribute model.
-
-### 2. Run a Scan Filtered by the Framework
+The framework must appear in the output. A validation error indicates a schema mismatch.
```bash
uv run python prowler-cli.py \
- --compliance __ \
+ --compliance \
--log-level ERROR
```
Verify that:
- Prowler produces a CSV file under `output/compliance/` with the expected name.
-- The CLI summary table lists every section in the framework.
+- The CLI summary table lists every section / pillar of the framework.
- Findings roll up under the expected requirements.
-### 3. Inspect the CSV Output
+### 4. Inspect the CSV output
Open the generated CSV and confirm:
-- All columns defined in `models.py` appear.
-- Every requirement has at least one row per scanned resource.
-- Values such as `Requirements_Attributes_Section` reflect the JSON content.
+- All columns defined in `models.py` (legacy) or in `attributes_metadata` (universal) appear.
+- Every requirement has at least one row per scanned resource (when there are findings).
+- Attribute values such as `Requirements_Attributes_Section` reflect the JSON content.
-### 4. Verify the Framework in Prowler App
+### 5. Verify the Framework in Prowler Local Server
-Launch Prowler App locally (`docker compose up` from the repository root) and run a scan with the new compliance framework. Confirm the compliance page renders the requirements, sections, and status widgets correctly.
+Launch Prowler Local Server (`docker compose up` from the repository root) and run a scan with the new compliance framework. Confirm the compliance page renders the requirements, sections, and status widgets correctly.
## Testing
Compliance contributions require two layers of tests.
- **Schema tests** exercise the Pydantic models. Extend `tests/lib/check/universal_compliance_models_test.py` with a case that loads the new JSON file and asserts the attribute type matches the expected model.
-- **Output tests** exercise the transformer. Mirror the structure under `tests/lib/outputs/compliance//` with fixtures that feed synthetic findings through the transformer and assert the resulting CSV rows.
+- **Output tests** (legacy frameworks only) exercise the transformer. Mirror the structure under `tests/lib/outputs/compliance//` with fixtures that feed synthetic findings through the transformer and assert the resulting CSV rows.
Run the suite with:
@@ -342,7 +756,20 @@ uv run pytest -n auto tests/lib/check/universal_compliance_models_test.py \
For guidance on writing Prowler SDK tests, refer to [Unit Testing](/developer-guide/unit-testing).
-## Submitting the Pull Request
+## Running and listing your framework
+
+Once the file is in place, the CLI auto-discovers it:
+
+```sh
+prowler --list-compliance # framework appears in the list
+prowler --compliance --list-checks
+prowler --compliance # full scan + compliance report
+prowler --compliance --list-compliance-requirements
+```
+
+For end-user-facing tutorials (recommended for high-profile frameworks), add a dedicated page under `docs/user-guide/compliance/tutorials/` and register it in the `"Compliance"` group of `docs/docs.json`. See `docs/user-guide/compliance/tutorials/threatscore.mdx` as a reference.
+
+## Submitting the pull request
Before opening the pull request:
@@ -351,29 +778,32 @@ Before opening the pull request:
uv run pre-commit run --all-files
uv run pytest -n auto
```
-2. Add a changelog entry under the `### 🚀 Added` section of `prowler/CHANGELOG.md`, describing the new framework and the providers it covers.
-3. Follow the [Pull Request Template](https://github.com/prowler-cloud/prowler/blob/master/.github/pull_request_template.md) and set the PR title using Conventional Commits, for example `feat(compliance): add My Framework 1.0 for AWS`.
+2. Add a changelog fragment `prowler/changelog.d/.added.md`, describing the new framework and the providers it covers (no PR link in the text; it is attached automatically at release time).
+3. Follow the [Pull Request Template](https://github.com/prowler-cloud/prowler/blob/master/.github/pull_request_template.md) and set the PR title using Conventional Commits, e.g. `feat(compliance): add My Framework 1.0 for AWS`.
4. Request review from the compliance codeowners listed in `.github/CODEOWNERS`.
## Troubleshooting
The following issues are the most common when contributing a compliance framework.
-- **`ValidationError: field required` during scan.** The JSON is missing a required attribute field. Re-check the matching Pydantic model in `prowler/lib/check/compliance_models.py`.
-- **All attributes collapse to `Generic_Compliance_Requirement_Attribute` values.** The Pydantic `Union` is ordered incorrectly, or the JSON matches only the generic shape. Move the generic model to the last Union position and ensure every required field is present in the JSON.
-- **`--compliance` filter does not find the framework.** The filename does not match the expected pattern `__.json`, the version is empty, or the file lives outside `prowler/compliance//`.
-- **CLI summary table is empty but the CSV is populated.** The dispatcher branch in `prowler/lib/outputs/compliance/compliance.py` is missing or its substring match does not catch the framework key.
-- **CSV file is missing after the scan.** The transformer class is not registered in `prowler/lib/outputs/compliance/compliance_output.py`, or `transform()` raises silently. Run the scan with `--log-level DEBUG`.
-- **Findings do not roll up under a requirement.** A check listed in `Checks` either does not exist for that provider or is spelled incorrectly. Run `--list-checks | grep ` to confirm.
+- **`ValidationError: field required` during scan (legacy).** The JSON is missing a required attribute field. Re-check the matching Pydantic model in `prowler/lib/check/compliance_models.py`.
+- **All attributes collapse to `Generic_Compliance_Requirement_Attribute` values (legacy).** The Pydantic `Union` is ordered incorrectly, or the JSON matches only the generic shape. Keep the generic model in the last Union position and ensure every required field is present in the JSON.
+- **`attributes_metadata validation failed` (universal).** The root validator in `compliance_models.py` rejected the file. The error message lists each offending requirement; common causes are unknown attribute keys (typo or missing entry in `attributes_metadata`), enum violations, or missing required keys.
+- **`--compliance` filter does not find the framework.** For legacy: the filename does not match `__.json`, the version is empty, or the file lives outside `prowler/compliance//`. For universal: the file is not at the top level of `prowler/compliance/` or it loaded as `None` (check logs for the validation error).
+- **CLI summary table is empty but the CSV is populated (legacy).** The dispatcher branch in `prowler/lib/outputs/compliance/compliance.py` is missing or its substring match does not catch the framework key.
+- **CSV file is missing after the scan (legacy).** The transformer class is not registered in `prowler/lib/outputs/compliance/compliance_output.py`, or `transform()` raises silently. Run the scan with `--log-level DEBUG`.
+- **Findings do not roll up under a requirement.** A check listed in `Checks` either does not exist for that provider or is spelled incorrectly. Run `--list-checks | grep ` to confirm, or run the check-existence cross-check from "Validating Your Framework".
-## Reference Examples
+## Reference examples
Use the following files as templates when modeling a new contribution.
-- `prowler/compliance/aws/cis_2.0_aws.json` – CIS attribute shape.
-- `prowler/compliance/aws/nist_800_53_revision_5_aws.json` – Generic attribute shape.
-- `prowler/compliance/aws/ccc_aws.json` – CCC attribute shape.
-- `prowler/compliance/azure/ens_rd2022_azure.json` – ENS attribute shape.
-- `prowler/lib/check/compliance_models.py` – Canonical Pydantic schemas.
-- `prowler/lib/outputs/compliance/cis/` – Reference implementation of a multi-provider output formatter.
-- `prowler/lib/outputs/compliance/generic/` – Reference implementation of a generic output formatter.
+- `prowler/compliance/dora_2022_2554.json` — universal schema, single-provider populated (AWS), ready to extend with more providers.
+- `prowler/compliance/csa_ccm_4.0.json` — universal schema, multi-provider populated (AWS, Azure, GCP, AlibabaCloud, OracleCloud).
+- `prowler/compliance/aws/cis_2.0_aws.json` — legacy CIS attribute shape.
+- `prowler/compliance/aws/nist_800_53_revision_5_aws.json` — legacy generic attribute shape.
+- `prowler/compliance/aws/ccc_aws.json` — legacy CCC attribute shape.
+- `prowler/compliance/azure/ens_rd2022_azure.json` — legacy ENS attribute shape.
+- `prowler/lib/check/compliance_models.py` — canonical Pydantic schemas for both formats.
+- `prowler/lib/outputs/compliance/cis/` — reference implementation of a multi-provider legacy output formatter.
+- `prowler/lib/outputs/compliance/generic/` — reference implementation of a legacy generic output formatter.
diff --git a/docs/developer-guide/server-sent-events.mdx b/docs/developer-guide/server-sent-events.mdx
new file mode 100644
index 0000000000..c91f27227f
--- /dev/null
+++ b/docs/developer-guide/server-sent-events.mdx
@@ -0,0 +1,241 @@
+---
+title: 'Server-Sent Events (SSE)'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+
+The platform ships the SSE **infrastructure** (`api.sse`) and wiring. No feature endpoint streams over SSE out of the box — this guide shows how to build one on top of the shared base.
+
+
+## When to use SSE
+
+| Need | Use |
+|------|-----|
+| Server pushes incremental updates, client only reads | **SSE** |
+| Bidirectional, low-latency messaging (chat both ways, games) | WebSocket |
+| Client asks, server answers once | Plain REST |
+
+SSE is the right tool when the **client only consumes**: scan progress, long-running job checkpoints, streamed LLM tokens, cross-client resource-sync notifications. It rides on plain HTTP, reconnects automatically in the browser via the native [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource) API, and needs no extra protocol.
+
+## How it works
+
+SSE is wired through [`django-eventstream`](https://github.com/fanout/django_eventstream) and a small platform layer in `api/src/backend/api/sse/`:
+
+| Piece | File | Responsibility |
+|-------|------|----------------|
+| `BaseSSEViewSet` | `api/sse/base_views.py` | Base DRF viewset a feature subclasses. The feature implements `get_channels`; the base handles auth, the tenant transaction, and delegates streaming to `django-eventstream`. |
+| `SSEChannelManager` | `api/sse/channelmanager.py` | Registered in `settings.EVENTSTREAM_CHANNELMANAGER_CLASS`. Reads the channel set off the request and enforces the platform-wide tenant gate. |
+| `SSEAuthentication` | `api/authentication.py` | Same JWT/API-key stack as the rest of the API, plus an `?access_token=` fallback for browser `EventSource` clients. Lives with the other authentication classes, not in the `sse` package. |
+| `make_channel_name` / `tenant_id_from_channel` | `api/sse/utils.py` | Single source of truth for the channel-name format, so publishers and the channel manager agree byte-for-byte. |
+| Settings | `config/settings/eventstream.py` | Valkey Pub/Sub backend (dedicated DB), channel manager, allowed headers. |
+
+### Transport: the server runs on ASGI
+
+SSE connections are long-lived. Holding one open per synchronous worker would exhaust the worker pool, so the API runs under Gunicorn's native **`asgi` worker** (`config.asgi:application`). Streams are parked on the event loop while ordinary CRUD endpoints keep their synchronous execution (Django runs sync views in a thread-sensitive executor under ASGI). This is configured in `config/guniconf.py` and used by both the dev and production entrypoints — no separate server process is needed.
+
+### The data flow
+
+```
+publisher (Celery task / view) subscriber (browser, CLI)
+ │ │
+ │ send_event(channel, "scan.progress", …) │ GET …/event-stream
+ ▼ ▼
+ Valkey Pub/Sub ◄────────────────────► BaseSSEViewSet.list
+ (EVENTSTREAM_VALKEY_DB) → get_channels() (RLS-scoped)
+ → SSEChannelManager (tenant gate)
+ → StreamingHttpResponse (text/event-stream)
+```
+
+A publisher anywhere in the system (most often a Celery task) calls `send_event(channel, event_type, payload)`. `django-eventstream` fans it out over Valkey Pub/Sub to every connection subscribed to that channel.
+
+## Adding an SSE endpoint to your feature
+
+The example below streams progress for a long-running **scan**. Adapt the resource, prefix, and event names to your feature.
+
+
+
+
+
+Channels follow the format `::`, built only through `make_channel_name`. The prefix is owned by your feature and may contain hyphens but **never colons** (the parser splits on `:`).
+
+```python
+CHANNEL_PREFIX = "scan-progress"
+```
+
+The tenant id is baked into every channel name. That is what lets the platform enforce cross-tenant isolation without knowing anything about your feature.
+
+
+
+
+
+Create the viewset for the SSE sub-resource. The only required method is `get_channels`; it runs inside the tenant transaction set up by the base class, so any database lookup inside it is automatically RLS-scoped.
+
+```python
+# scans/event_streams.py
+from api.sse import BaseSSEViewSet, make_channel_name
+from django.shortcuts import get_object_or_404
+from scans.models import Scan
+
+CHANNEL_PREFIX = "scan-progress"
+
+
+class ScanEventStreamViewSet(BaseSSEViewSet):
+ def get_queryset(self):
+ # RLS already scopes to the tenant; narrow further as needed
+ # (e.g. only scans the requesting user may see).
+ return Scan.objects.filter(tenant_id=self.request.tenant_id)
+
+ def get_channels(self) -> set[str]:
+ scan = get_object_or_404(self.get_queryset(), pk=self.kwargs["scan_pk"])
+ return {make_channel_name(CHANNEL_PREFIX, scan.tenant_id, scan.id)}
+```
+
+
+`get_channels` **must raise** the relevant DRF exception (`NotFound`, `PermissionDenied`, `NotAuthenticated`) when authorization fails — `get_object_or_404` does this for you. Returning an empty set surfaces as django-eventstream's confusing "No channels specified" error instead of the real cause.
+
+
+
+
+
+
+Mount the endpoint as an `event-stream` sub-resource. Keep it **outside the DRF router**, which would force the URL into a list/detail convention. Route the `get` method to the viewset's `list` action.
+
+```python
+# scans/urls.py
+path(
+ "scans//event-stream",
+ ScanEventStreamViewSet.as_view({"get": "list"}),
+ name="scan-event-stream",
+),
+```
+
+
+
+
+
+A feature owns its event types in `//events.py`: one `publish_` function per event type, each body a **single** `send_event` call so the wire-level string lives in exactly one place.
+
+```python
+# scans/events.py
+from django_eventstream import send_event
+
+
+def publish_progress(channel: str, checked: int, total: int) -> None:
+ send_event(channel, "scan.progress", {"checked": checked, "total": total})
+
+
+def publish_end(channel: str, scan_id: str) -> None:
+ # Terminal event carries the canonical id so reconnecting clients
+ # can refetch the persisted resource over REST.
+ send_event(channel, "scan.end", {"scan_id": scan_id})
+
+
+def publish_error(channel: str, code: str, detail: str) -> None:
+ send_event(channel, "scan.error", {"code": code, "detail": detail})
+```
+
+There is no platform-side enum, registry, or dispatch table — **the naming convention is the contract** (see below).
+
+
+
+
+
+Wherever the work happens — usually a Celery task — build the channel the same way and publish:
+
+```python
+from api.sse import make_channel_name
+from scans.events import publish_progress, publish_end
+
+channel = make_channel_name("scan-progress", scan.tenant_id, scan.id)
+publish_progress(channel, checked=42, total=100)
+...
+publish_end(channel, scan_id=str(scan.id))
+```
+
+
+
+
+
+## Event naming convention
+
+Every event uses an event type of the form **`.`** (lowercased, dot-separated). The verb comes from this platform-wide vocabulary — if you need a verb that is not listed, document the addition in this guide so the catalog stays discoverable.
+
+| Verb | When to use |
+|------|-------------|
+| `delta` | An incremental piece of a stream the client concatenates (LLM text tokens, audio chunks). Standard term across OpenAI / Anthropic / LiteLLM / Vercel AI SDK. |
+| `start` | Begin marker for a compound operation (e.g. a tool call whose execution will be reported by a matching `end`). |
+| `end` | Terminal marker. Carries the canonical resource id so reconnecting clients can refetch persisted state via REST. |
+| `progress` | Periodic checkpoint with quantifiable completion, e.g. `{"checked": 42, "total": 100}`. |
+| `created` / `updated` / `deleted` | Resource-lifecycle events for cross-client sync streams. |
+| `error` | Terminal failure. Carries a stable `code` for client switching and a human-readable `detail`. |
+
+
+Payloads are **flat JSON**. The wire-level `event:` field already names the event type, so do **not** wrap the payload in `{"type": ..., "data": ...}`. Include the canonical resource UUID on terminal events so reconnecting clients can reconcile via REST.
+
+
+## Authentication
+
+SSE endpoints use the same authentication stack as the rest of the API. Non-browser clients (CLI, programmatic) send the standard `Authorization` header — JWT or API key.
+
+Browser `EventSource` is the only widely available SSE client API and it **cannot set custom headers**. For that case only, the endpoint accepts a JWT via the `?access_token=` query parameter. The header always wins when present — a header is intentional, while a query parameter can leak into referers and logs, so it is consulted only as a fallback.
+
+```javascript
+// Browser
+const es = new EventSource(
+ `/api/v1/scans/${scanId}/event-stream?access_token=${jwt}`
+);
+```
+
+```bash
+# CLI / programmatic — header, exactly like every other endpoint
+curl -N -H "Authorization: Bearer $JWT" \
+ https:///api/v1/scans/$SCAN_ID/event-stream
+```
+
+## Tenant isolation & security model
+
+Authorization is enforced at two layers:
+
+1. **At connect**, `get_channels` runs under the regular DRF stack inside the tenant transaction (`rls_transaction`). Resource lookups are RLS-scoped, so a user cannot even resolve a channel for a resource they cannot see. Narrow the queryset further (e.g. `created_by=request.user`) when a resource is per-user within a tenant.
+2. **After connect**, `SSEChannelManager.can_read_channel` re-verifies tenant membership by parsing the tenant id embedded in the channel name. Cross-tenant subscription is rejected even if a URL-level check ever has a bug. A malformed channel name is treated as "not authorized".
+
+Because the tenant id lives inside the channel name, this gate works for any feature without the platform knowing anything about it.
+
+## Reconnect & state recovery
+
+The platform deliberately ships **without server-side replay** (`is_channel_reliable` returns `False`). When a client reconnects, it does **not** receive missed events. Instead:
+
+- Terminal events (`*.end`) carry the canonical resource **UUID**.
+- On reconnect, the client refetches the authoritative state from the normal REST endpoint using that id.
+
+Design your event payloads accordingly: deltas are ephemeral and concatenated in-flight; the durable truth always lives behind a REST resource.
+
+## Local development
+
+- The dev and production entrypoints both launch Gunicorn with the `asgi` worker (`config.asgi:application`). In dev, `DJANGO_DEBUG=True` enables hot reload; `preload_app` is automatically disabled under debug so edited code is picked up.
+- SSE uses a **dedicated Valkey database** (`EVENTSTREAM_VALKEY_DB`, default `2`) kept separate from the Celery broker so a noisy broker cannot crowd out streaming traffic. It reuses the same `VALKEY_*` connection settings as the rest of the platform.
+
+| Env var | Default | Purpose |
+|---------|---------|---------|
+| `EVENTSTREAM_VALKEY_DB` | `2` | Valkey DB index for the SSE Pub/Sub bus |
+| `DJANGO_WORKER_CLASS` | `asgi` | Gunicorn worker class |
+
+Test the stream end to end with `curl -N` (disable buffering) and an auth header:
+
+```bash
+curl -N -H "Authorization: Bearer $JWT" \
+ http://localhost:8080/api/v1/scans/$SCAN_ID/event-stream
+```
+
+## Testing
+
+The platform basis is covered by `api/tests/test_sse.py` (channel parsing, the tenant gate, and auth precedence). For a feature endpoint, test:
+
+- `get_channels` returns the expected channel for an authorized resource and raises `NotFound`/`PermissionDenied` otherwise.
+- Each `publish_` helper emits the correct event type and flat payload (mock `send_event`).
+- The producer builds the channel with `make_channel_name` using the resource's own `tenant_id`.
diff --git a/docs/developer-guide/stackit-details.mdx b/docs/developer-guide/stackit-details.mdx
new file mode 100644
index 0000000000..58a5cf19a5
--- /dev/null
+++ b/docs/developer-guide/stackit-details.mdx
@@ -0,0 +1,730 @@
+---
+title: 'StackIT Provider'
+---
+
+This page details the [StackIT Cloud](https://www.stackit.de/) provider implementation in Prowler.
+
+By default, Prowler audits a single StackIT project per scan. To configure it, provide the project ID and either a service account key file path or inline service account key JSON.
+
+## StackIT Provider Classes Architecture
+
+The StackIT provider implementation follows the general [Provider structure](/developer-guide/provider). This section focuses on the StackIT-specific implementation, highlighting how the generic provider concepts are realized for StackIT in Prowler. For a full overview of the provider pattern, base classes, and extension guidelines, see [Provider documentation](/developer-guide/provider).
+
+### `StackitProvider` (Main Class)
+
+- **Location:** [`prowler/providers/stackit/stackit_provider.py`](https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/stackit/stackit_provider.py)
+- **Base Class:** Inherits from `Provider` (see [base class details](https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/common/provider.py)).
+- **Purpose:** Central orchestrator for StackIT-specific logic, API authentication, credential validation, and configuration.
+- **Key StackIT Responsibilities:**
+ - Initializes StackIT SDK authentication via a service account key file or inline service account key JSON. The SDK mints and refreshes access tokens internally.
+ - Validates the service account credentials and project ID (UUID format validation).
+ - Loads and manages configuration, mutelist, and fixer settings.
+ - Provides properties and methods for downstream StackIT service classes to access credentials, identity, and configuration data.
+
+### Data Models
+
+- **Location:** [`prowler/providers/stackit/models.py`](https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/stackit/models.py)
+- **Purpose:** Define structured data for StackIT identity and output configuration.
+- **Key StackIT Models:**
+ - `StackITIdentityInfo`: Holds StackIT identity metadata, including project ID and project name (fetched automatically from Resource Manager API).
+ - `StackITOutputOptions`: Customizes default output filenames so StackIT reports include the audited project ID.
+ - IaaS resource models such as `SecurityGroup` and `SecurityGroupRule` are defined in the IaaS service module.
+
+### StackIT Services
+
+- **Location:** [`prowler/providers/stackit/services/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/stackit/services)
+- **Purpose:** Implement StackIT service clients and resource collection logic following the generic [service pattern](/developer-guide/services#service-base-class).
+- **Current Implementation:** The `IaaSService` collects security groups, rules, and network interface usage across supported StackIT regions.
+
+### Exception Handling
+
+- **Location:** [`prowler/providers/stackit/exceptions/exceptions.py`](https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/stackit/exceptions/exceptions.py)
+- **Purpose:** Custom exception classes for StackIT-specific error handling, such as credential validation, API connection, and configuration errors.
+- **Key Exception Classes:**
+ - `StackITBaseException`: Base exception for all StackIT provider errors.
+ - `StackITCredentialsError`: Raised when credentials are invalid or missing.
+ - `StackITInvalidProjectIdError`: Raised when project ID is invalid or not in UUID format.
+ - `StackITAPIError`: Raised when StackIT API calls fail.
+
+## Authentication
+
+### Service Account Creation and Key Generation
+
+StackIT uses service account keys for API authentication. Service account keys are RSA key-pair based and provide secure, short-lived access tokens.
+
+### Creating a Service Account Key
+
+#### Method 1: Via StackIT Portal
+
+1. **Navigate to Service Accounts**
+ - Go to the [StackIT Portal](https://portal.stackit.cloud/)
+ - Select your project
+ - Click **Service Accounts** in the left sidebar
+
+2. **Create or Select Service Account**
+ - If you don't have a service account, click **Create Service Account**
+ - Provide a name and description
+ - Assign necessary permissions:
+ - For IaaS security checks: `iaas.viewer` or `project.owner`
+ - For comprehensive audits: `project.owner`
+
+3. **Generate Service Account Key**
+ - Select your service account
+ - Navigate to **Service Account Keys**
+ - Click **Create key**
+ - Choose one of the following options:
+ - **STACKIT-generated key pair** (Recommended): Let STACKIT automatically generate an RSA key-pair
+ - **User-provided key pair**: Upload your own RSA 2048 public key
+
+4. **Download and Save the Key**
+ - Download the generated service account key file (JSON format)
+ - **Important**: Save the key securely - it contains your private key and will only be available once
+ - Store the key file in a secure location (e.g., `~/.stackit/sa_key.json`)
+
+#### Method 2: Via StackIT CLI
+
+```bash
+# Install STACKIT CLI (if not already installed)
+# Follow instructions at: https://github.com/stackitcloud/stackit-cli
+
+# Create service account key (STACKIT-generated)
+stackit service-account key create --email my-service-account@example.com
+
+# Or create with your own RSA 2048 public key
+# First, generate your RSA key pair:
+openssl genrsa -out private-key.pem 2048
+openssl rsa -in private-key.pem -pubout -out public-key.pem
+
+# Then create the key with your public key:
+stackit service-account key create \
+ --email my-service-account@example.com \
+ --public-key "$(cat public-key.pem)"
+```
+
+### Finding Your Project ID
+
+Your StackIT project ID is a UUID that can be found:
+
+1. In the StackIT Portal URL when viewing your project: `https://portal.stackit.cloud/projects/{PROJECT_ID}/...`
+2. In the project settings page
+3. Using the StackIT CLI: `stackit project list`
+
+### Passing the Service Account Key to Prowler
+
+Prowler accepts the service account credentials in two equivalent forms; both go through the same StackIT SDK flow and refresh access tokens internally.
+
+#### Option 1: Key File Path (key persisted on disk)
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+
+prowler stackit
+```
+
+Or as CLI flags:
+
+```bash
+prowler stackit \
+ --stackit-service-account-key-path ~/.stackit/sa-key.json \
+ --stackit-project-id 12345678-1234-1234-1234-123456789abc
+```
+
+#### Option 2: Inline Key Content (CI/CD, secret managers)
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY="$(vault kv get -field=key stackit/sa)"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+
+prowler stackit
+```
+
+Prefer the environment variable over the matching `--stackit-service-account-key` CLI flag; passing the secret on the command line leaks it through process listings and shell history.
+
+### Credential Lookup Order
+
+Prowler resolves credentials in this order:
+
+1. **Command-line arguments**:
+ - `--stackit-service-account-key`
+ - `--stackit-service-account-key-path`
+ - `--stackit-project-id`
+2. **Environment variables**:
+ - `STACKIT_SERVICE_ACCOUNT_KEY`
+ - `STACKIT_SERVICE_ACCOUNT_KEY_PATH`
+ - `STACKIT_PROJECT_ID`
+
+When both the inline key and the key file path are set, the inline content takes precedence.
+
+## Configuration
+
+### Command-Line Arguments
+
+StackIT-specific command-line arguments:
+
+| Argument | Description | Required | Default |
+|----------|-------------|----------|---------|
+| `--stackit-service-account-key-path` | Path to a StackIT service account key JSON file | Yes* | `$STACKIT_SERVICE_ACCOUNT_KEY_PATH` |
+| `--stackit-service-account-key` | Inline JSON content of a StackIT service account key (preferred env var: `STACKIT_SERVICE_ACCOUNT_KEY`) | Yes* | `$STACKIT_SERVICE_ACCOUNT_KEY` |
+| `--stackit-project-id` | StackIT project ID (UUID format) | Yes* | `$STACKIT_PROJECT_ID` |
+| `--stackit-region` | StackIT region(s) to scan | No | All available regions |
+
+\* Required unless provided via environment variables.
+
+### Input Validation
+
+The StackIT provider performs comprehensive input validation:
+
+- **Service Account Credentials**:
+ - At least one of `service_account_key_path` (file path) or `service_account_key` (inline JSON) must be supplied; both empty raises `StackITNonExistentTokenError`
+ - When both are provided the inline content takes precedence
+ - The key file path is logged as-is; the inline content is redacted in the credentials box
+
+- **Project ID**:
+ - Must not be empty
+ - Must be a valid UUID format (e.g., `12345678-1234-1234-1234-123456789abc`)
+ - Validated using Python's UUID constructor
+
+Invalid credentials will result in clear error messages before any API calls are made.
+
+## Available Services
+
+### IaaS (Infrastructure as a Service)
+
+- **Service Class:** `IaaSService`
+- **Location:** [`prowler/providers/stackit/services/iaas/iaas_service.py`](https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/stackit/services/iaas/iaas_service.py)
+- **SDK:** Uses the [stackit-iaas](https://pypi.org/project/stackit-iaas/) Python SDK
+- **Purpose:** Manages IaaS resources including security groups, servers, and network interfaces.
+
+**Supported Resources:**
+- Security Groups and Rules
+- Servers (Virtual Machines)
+- Network Interfaces (NICs)
+
+**Key Features:**
+- Automatic discovery of all security groups in the project
+- Security rule parsing with support for unrestricted access detection
+- Network interface analysis to determine whether security groups are in use
+- By default, reports only security groups attached to at least one NIC; `--scan-unused-services` includes unused security groups too
+
+## Available Checks
+
+The StackIT provider currently implements 4 security checks focused on network security:
+
+### 1. iaas_security_group_ssh_unrestricted
+
+- **Severity:** High
+- **Description:** Detects security groups that allow unrestricted SSH access (port 22) from the internet.
+- **Risk:** Unrestricted SSH access increases the attack surface and risk of brute-force attacks.
+- **Detection Logic:**
+ - Checks for ingress rules allowing TCP port 22
+ - Flags rules with `ip_range=None` or `ip_range="0.0.0.0/0"` or `ip_range="::/0"`
+ - Reports security groups attached to NICs by default, or all security groups when `--scan-unused-services` is enabled
+
+### 2. iaas_security_group_rdp_unrestricted
+
+- **Severity:** High
+- **Description:** Detects security groups that allow unrestricted RDP access (port 3389) from the internet.
+- **Risk:** Unrestricted RDP access enables potential unauthorized remote desktop access.
+- **Detection Logic:**
+ - Checks for ingress rules allowing TCP port 3389
+ - Flags unrestricted IP ranges (None, 0.0.0.0/0, ::/0)
+ - Reports security groups attached to NICs by default, or all security groups when `--scan-unused-services` is enabled
+
+### 3. iaas_security_group_database_unrestricted
+
+- **Severity:** High
+- **Description:** Detects security groups that allow unrestricted access to common database ports.
+- **Monitored Ports:**
+ - MySQL: 3306
+ - PostgreSQL: 5432
+ - MongoDB: 27017
+ - Redis: 6379
+ - SQL Server: 1433
+ - CouchDB: 5984
+- **Risk:** Unrestricted database access can lead to data breaches and unauthorized data access.
+
+### 4. iaas_security_group_all_traffic_unrestricted
+
+- **Severity:** Critical
+- **Description:** Detects security groups that allow all traffic from the internet.
+- **Detection Logic:**
+ - Checks for rules with `port_range=None` (all ports)
+ - Checks for rules with port range covering 0-65535 or 1-65535
+ - Flags unrestricted IP ranges
+ - Critical security misconfiguration requiring immediate remediation
+
+### Important Implementation Notes
+
+**Self-Referencing Security Group Rules:**
+
+Security group rules with `remoteSecurityGroupId` set are automatically filtered out from unrestricted access checks. These rules only allow traffic from instances within the same security group (self-referencing), not from the internet, and are therefore not flagged as security risks.
+
+**Rule Display Names:**
+
+All findings include user-friendly rule descriptions when available. If a security group rule has a description field set (the name shown in the StackIT UI), it will be displayed in the finding message along with the rule ID:
+- With description: `'Allow SSH from office' (sgr-abc123)`
+- Without description: `'sgr-abc123'`
+
+**Network Interface (NIC) Usage Filtering:**
+
+The IaaS service lists project NICs and records the security group IDs attached to them. Checks use that signal to decide whether a security group is in use:
+
+1. **Default behavior:** Report security groups attached to at least one NIC.
+2. **`--scan-unused-services`:** Report every security group, including unused ones.
+3. **FAIL logic:** Internet exposure is driven by security group rules that allow unrestricted source ranges, not by the presence of a public IP on the NIC.
+
+**Unrestricted IP Ranges:**
+
+The StackIT API represents "unrestricted" in two ways:
+- **`ip_range=null`**: No IP restriction specified (implicit unrestricted)
+- **`ip_range="0.0.0.0/0"` or `"::/0"`**: Explicitly configured to allow all IPs
+
+Both are flagged as unrestricted. A `null` value is **more permissive** than an explicit range and applies to all protocols/ports if other fields are also `null`.
+
+## Requirements
+
+### Python Version
+
+- **Minimum:** Python 3.10+
+- **Reason:** The StackIT SDK requires Python 3.10 or higher
+
+### Dependencies
+
+The StackIT provider requires the following Python packages (automatically installed with Prowler):
+
+- **stackit-core** (v0.2.0): Core SDK for StackIT API authentication and configuration
+- **stackit-iaas** (v1.4.0): IaaS service SDK for managing compute resources
+- **stackit-resourcemanager** (v0.8.0): Resource Manager SDK for fetching project metadata (e.g., project names)
+
+These dependencies are defined in `pyproject.toml` and installed automatically with:
+
+```bash
+poetry install
+```
+
+**Note:** The `stackit-resourcemanager` package enables automatic retrieval of project names for display in reports. If this package is not available, Prowler will still function normally but project names will be empty in the output.
+
+## Region Support
+
+### Supported Regions
+
+- **Available Regions:** `eu01` (Germany South) and `eu02` (Austria West)
+- **Default:** All scans use both `eu01` and `eu02` regions by default.
+
+### Multi-Region Scanning
+
+Prowler supports scanning multiple StackIT regions in a single execution. By default, it will scan all regions defined in the `stackit_regions_by_service.json` configuration file.
+
+### CLI Argument
+
+You can specify which regions to scan using the `--stackit-region` argument:
+
+```bash
+# Scan only eu01
+prowler stackit --stackit-region eu01
+
+# Scan both eu01 and eu02
+prowler stackit --stackit-region eu01 eu02
+```
+
+### Implementation Details
+
+- **Regional Clients:** Prowler generates a separate API client for each audited region.
+- **Service Iteration:** Each service (e.g., IaaS) iterates through the regional clients to fetch and audit resources.
+- **Identity Tracking:** The `audited_regions` are stored in the identity model for reporting.
+
+### Future Enhancements
+
+As StackIT adds more regions, they can be easily added to Prowler by updating the `prowler/providers/stackit/stackit_regions_by_service.json` file without requiring code changes.
+
+## Command Examples
+
+### Scan Specific Regions
+
+Scan only the `eu01` region:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --stackit-region eu01
+```
+
+Scan multiple regions:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --stackit-region eu01 eu02
+```
+
+### Scan Specific Checks
+
+Run only SSH unrestricted check:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --checks iaas_security_group_ssh_unrestricted
+```
+
+### Scan All Security Group Checks
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --services iaas
+```
+
+### Output Formats
+
+Generate JSON output:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --output-formats json
+```
+
+Generate HTML report:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --output-formats html
+```
+
+## Known Limitations
+
+### Current Limitations
+
+1. **Single Project Scope**: Only one project can be scanned at a time
+2. **Service Coverage**: Only the IaaS service is currently implemented
+3. **Check Coverage**: Limited to security group network security checks (4 checks total)
+4. **No Compliance Frameworks**: Compliance framework mappings are not yet implemented
+
+### Planned Enhancements
+
+- Multi-project scanning capability
+- Additional IaaS checks (volume encryption, server public IP exposure, backup status)
+- Compliance framework mappings (CIS, custom StackIT best practices)
+- StackIT CLI remediation examples in metadata
+
+## Troubleshooting
+
+### Authentication Errors
+
+**Error:** `StackIT service account key was rejected`
+
+**Solutions:**
+1. Re-issue the service account key in the StackIT Portal
+2. Verify the service account key file or inline JSON content is complete
+3. Check that the service account has the necessary permissions (`iaas.viewer` or `project.owner`)
+4. Ensure the service account key is provided through `STACKIT_SERVICE_ACCOUNT_KEY_PATH`, `STACKIT_SERVICE_ACCOUNT_KEY`, or the matching CLI arguments
+
+**Error:** `StackIT credentials not found or are invalid`
+
+**Solutions:**
+1. Ensure the project ID and one service account credential source are provided
+2. Check that credentials are set via environment variables or command-line arguments
+3. Verify there are no extra spaces or newlines in the credentials
+
+**Error:** `Invalid StackIT project ID format`
+
+**Solutions:**
+1. Verify the project ID is a valid UUID format: `12345678-1234-1234-1234-123456789abc`
+2. Copy the project ID directly from the StackIT Portal
+3. Ensure there are no extra spaces or quotes around the UUID
+
+### API Connection Errors
+
+**Error:** `Failed to connect to StackIT API`
+
+**Solutions:**
+1. Check your internet connection
+2. Verify the StackIT API endpoint is accessible from your network
+3. Check if there are any firewall rules blocking HTTPS connections
+4. Review the full error message for specific API error codes
+
+**Error:** `HTTP 403 Forbidden`
+
+**Solutions:**
+1. Verify the service account has the correct permissions
+2. Ensure the project ID is correct and you have access to it
+3. Check that the service account is enabled (not disabled or expired)
+4. Verify the service account key has not been revoked
+
+**Error:** `HTTP 404 Not Found`
+
+**Solutions:**
+1. Verify the project ID exists and is correct
+2. Check that the IaaS service is enabled in your project
+3. Ensure you're using the correct region (eu01)
+
+### Empty Results
+
+**Issue:** No security groups or findings reported
+
+**Solutions:**
+1. Verify that security groups exist in your project
+2. Check that the IaaS service is properly configured
+3. Ensure the service account has `iaas.viewer` permission
+4. Check Prowler logs for any API errors (use `--log-level DEBUG`)
+
+### Debug Mode
+
+Enable debug logging for detailed troubleshooting:
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+
+prowler stackit \
+ --stackit-project-id "your-project-id" \
+ --log-level DEBUG
+```
+
+This will show:
+- API authentication details (with inline service account keys redacted)
+- Resource discovery progress
+- Security rule parsing details
+- Any API errors or warnings
+
+## Specific Patterns in StackIT Services
+
+The generic service pattern is described in [service page](/developer-guide/services#service-structure-and-initialisation). You can find all the currently implemented services in the following locations:
+
+- Directly in the code, in location [`prowler/providers/stackit/services/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/stackit/services)
+- In the [Prowler Hub](https://hub.prowler.com/) for a more human-readable view.
+
+The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other StackIT services as reference.
+
+### StackIT Service Common Patterns
+
+- Services communicate with StackIT using the StackIT Python SDK, you can find the documentation [here](https://github.com/stackitcloud/stackit-sdk-python).
+- Service constructors receive a `StackitProvider` instance and use it to access credentials, identity, and configuration.
+- The provider builds StackIT SDK `Configuration` objects from the service account key path or inline key content.
+- Resource containers **must** be initialized in the constructor, typically as lists or dictionaries.
+- Do not manipulate `os.environ` for credentials inside services. Use the provider session and SDK configuration helpers.
+- All StackIT resources are represented as Pydantic `BaseModel` classes, providing type safety and structured access to resource attributes.
+- StackIT SDK calls are wrapped in try/except blocks, with specific handling for API errors, always logging errors.
+- **Centralized Error Handling**: Use `provider.handle_api_error(exception)` for consistent authentication error detection across all services.
+- **SDK Warning Suppression**: StackIT SDK prints deprecation warnings to stderr - use the `suppress_stderr()` context manager during SDK initialization and API calls.
+- **Unrestricted Access Detection**: In StackIT API, `None` values mean "allow all" (more permissive than explicit 0.0.0.0/0).
+ - `protocol=None` → All protocols allowed
+ - `ip_range=None` → All source IPs allowed (unrestricted!)
+ - `port_range=None` → All ports allowed
+ - `remote_security_group_id` set → Only allows traffic from the same security group (not unrestricted!)
+
+### IaaS Service Specific Patterns
+
+**Security Group Discovery:**
+```python
+# List all security groups
+security_groups = client.list_security_groups(
+ project_id=self.project_id,
+ region=region,
+)
+
+# List network interfaces to determine security group usage
+nics = client.list_project_nics(
+ project_id=self.project_id,
+ region=region,
+)
+
+# Checks report in-use security groups by default. Use --scan-unused-services
+# to include security groups that are not attached to any NIC.
+```
+
+**Centralized Authentication Error Handling:**
+```python
+def _handle_api_call(self, api_function, *args, **kwargs):
+ """Wrapper for API calls with centralized error handling."""
+ try:
+ with suppress_stderr(): # Suppress SDK warnings
+ return api_function(*args, **kwargs)
+ except Exception as e:
+ # Use centralized error handler from provider
+ self.provider.handle_api_error(e) # Detects 401 and raises StackITInvalidTokenError
+```
+
+**Unrestricted Access Detection:**
+```python
+def is_unrestricted(rule):
+ """Check if a rule allows unrestricted access."""
+ # Filter out self-referencing rules
+ if rule.remote_security_group_id is not None:
+ return False
+ # Check for unrestricted IP ranges
+ return rule.ip_range is None or rule.ip_range in ["0.0.0.0/0", "::/0"]
+
+def is_tcp(rule):
+ """Check if a rule applies to TCP protocol."""
+ # None means all protocols (including TCP)
+ return rule.protocol is None or rule.protocol.lower() in ["tcp", "all"]
+
+def includes_port(rule, port):
+ """Check if a rule includes a specific port."""
+ # None means all ports
+ if rule.port_range is None:
+ return True
+ return rule.port_range.min <= port <= rule.port_range.max
+```
+
+## Specific Patterns in StackIT Checks
+
+The StackIT checks pattern is described in [checks page](/developer-guide/checks). You can find all the currently implemented checks:
+
+- Directly in the code, within each service folder, each check has its own folder named after the name of the check. (e.g. [`prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted))
+- In the [Prowler Hub](https://hub.prowler.com/) for a more human-readable view.
+
+The best reference to understand how to implement a new check is following the [check creation documentation](/developer-guide/checks#creating-a-check) and taking other similar StackIT checks as reference.
+
+### Check Report Class
+
+The `CheckReportStackIT` class models a single finding for a StackIT resource in a check report. It is defined in [`prowler/lib/check/models.py`](https://github.com/prowler-cloud/prowler/blob/master/prowler/lib/check/models.py) and inherits from the generic `Check_Report` base class.
+
+#### Purpose
+
+`CheckReportStackIT` extends the base report structure with StackIT-specific fields, enabling detailed tracking of the resource, project, and location associated with each finding.
+
+#### Constructor and Attribute Population
+
+When you instantiate `CheckReportStackIT`, you must provide the check metadata and a resource object. The class will attempt to automatically populate its StackIT-specific attributes from the resource, using the following logic:
+
+- **`resource_id`**:
+ - Uses `resource.id` if present.
+ - Otherwise, uses `resource.resource_id` if present.
+ - Defaults to an empty string if none are available.
+
+- **`resource_name`**:
+ - Uses `resource.name` if present.
+ - Defaults to an empty string if not available.
+
+- **`project_id`**:
+ - Uses `resource.project_id` if present.
+ - Defaults to an empty string if not available (should be set in check logic).
+
+- **`location`**:
+ - Uses `resource.region` if present.
+ - Otherwise, uses `resource.location` if present.
+ - Defaults to an empty string if not available.
+
+If the resource object does not contain the required attributes, you must set them manually in the check logic.
+
+Other attributes are inherited from the `Check_Report` class, from which you **always** have to set the `status` and `status_extended` attributes in the check logic.
+
+#### Example Usage
+
+```python
+from prowler.lib.check.models import CheckReportStackIT
+
+report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group
+)
+report.status = "FAIL"
+report.status_extended = f"Security group {security_group.name} allows unrestricted SSH access from the internet."
+report.resource_id = security_group.id
+report.resource_name = security_group.name
+report.project_id = security_group.project_id
+report.location = security_group.region
+```
+
+### Common Check Pattern
+
+```python
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+class iaas_security_group_ssh_unrestricted(Check):
+ """Check if IaaS security groups allow unrestricted SSH access."""
+
+ def execute(self):
+ findings = []
+
+ for security_group in iaas_client.security_groups:
+ if not (iaas_client.scan_unused_services or security_group.in_use):
+ continue
+
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group
+ )
+ report.status = "PASS"
+ report.status_extended = f"Security group {security_group.name} does not allow unrestricted SSH access."
+
+ # Check each rule
+ for rule in security_group.rules:
+ if (rule.is_ingress() and
+ rule.is_tcp() and
+ rule.includes_port(22) and
+ rule.is_unrestricted()):
+ report.status = "FAIL"
+ report.status_extended = f"Security group {security_group.name} allows unrestricted SSH access from the internet."
+ break
+
+ findings.append(report)
+
+ return findings
+```
+
+## Resources
+
+### Official StackIT Documentation
+
+- **StackIT Portal**: [https://portal.stackit.cloud/](https://portal.stackit.cloud/)
+- **StackIT Documentation**: [https://docs.stackit.cloud/](https://docs.stackit.cloud/)
+- **StackIT API Documentation**: [https://docs.api.eu01.stackit.cloud/](https://docs.api.eu01.stackit.cloud/)
+
+### Python SDK
+
+- **StackIT Python SDK (GitHub)**: [https://github.com/stackitcloud/stackit-sdk-python](https://github.com/stackitcloud/stackit-sdk-python)
+- **stackit-core (PyPI)**: [https://pypi.org/project/stackit-core/](https://pypi.org/project/stackit-core/)
+- **stackit-iaas (PyPI)**: [https://pypi.org/project/stackit-iaas/](https://pypi.org/project/stackit-iaas/)
+- **IaaS Models**: [https://github.com/stackitcloud/stackit-sdk-python/tree/main/services/iaas/src/stackit/iaas/models](https://github.com/stackitcloud/stackit-sdk-python/tree/main/services/iaas/src/stackit/iaas/models)
+
+### Prowler Resources
+
+- **Provider Implementation**: [`prowler/providers/stackit/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/stackit/)
+- **IaaS Service**: [`prowler/providers/stackit/services/iaas/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/stackit/services/iaas/)
+- **Prowler Hub**: [https://hub.prowler.com/](https://hub.prowler.com/)
+- **GitHub Issues**: [https://github.com/prowler-cloud/prowler/issues](https://github.com/prowler-cloud/prowler/issues)
+
+## Contributing
+
+If you'd like to contribute to the StackIT provider:
+
+1. **Add New Checks**: Follow the [check creation guide](/developer-guide/checks#creating-a-check) and use existing StackIT checks as templates
+2. **Enhance Services**: Implement additional IaaS resource discovery or add new services
+3. **Improve Documentation**: Add metadata enhancements, CLI remediation examples, or Terraform code samples
+4. **Report Issues**: Submit bug reports or feature requests on [GitHub](https://github.com/prowler-cloud/prowler/issues)
+
+### Quick Start for Contributors
+
+1. **Install dependencies**: `poetry install` (includes stackit-core and stackit-iaas)
+2. **Set credentials**: Export `STACKIT_SERVICE_ACCOUNT_KEY_PATH` and `STACKIT_PROJECT_ID`
+3. **Run checks**: `prowler stackit`
+4. **View code**: Start in `prowler/providers/stackit/`
+5. **Add checks**: Create new check directories under `services/iaas/`
+6. **Run tests**: `poetry run pytest tests/providers/stackit/ -v`
+
+### Code Quality Standards
+
+The StackIT provider should follow the same quality expectations as the rest of the Prowler SDK:
+
+- Keep service and check logic covered by unit tests.
+- Redact inline service account keys from generated output.
+- Keep documentation aligned with the implemented services and checks.
+- Follow existing provider, service, and check patterns before adding StackIT-specific abstractions.
diff --git a/docs/docs.json b/docs/docs.json
index e39ccb67ea..b9bc195182 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -38,55 +38,73 @@
{
"group": "Welcome",
"pages": [
- "introduction"
+ "introduction",
+ "getting-started/products/index"
]
},
{
- "group": "Prowler Cloud",
+ "group": "Prowler Products",
"pages": [
- "getting-started/products/prowler-cloud",
- "getting-started/products/prowler-cloud-pricing",
- "getting-started/products/prowler-cloud-aws-marketplace",
- "getting-started/goto/prowler-cloud",
- "getting-started/goto/prowler-api-reference"
+ {
+ "group": "Prowler Cloud",
+ "pages": [
+ "getting-started/products/prowler-cloud",
+ "getting-started/products/prowler-cloud-pricing",
+ "getting-started/products/prowler-cloud-aws-marketplace",
+ "getting-started/goto/prowler-cloud",
+ "getting-started/goto/prowler-api-reference"
+ ]
+ },
+ {
+ "group": "Prowler Lighthouse AI",
+ "pages": [
+ "getting-started/products/prowler-cloud-lighthouse"
+ ]
+ },
+ {
+ "group": "Prowler Hub",
+ "pages": [
+ "getting-started/products/prowler-hub",
+ "getting-started/goto/prowler-hub"
+ ]
+ },
+ {
+ "group": "Prowler MCP",
+ "pages": [
+ "getting-started/products/prowler-mcp",
+ "getting-started/basic-usage/prowler-mcp",
+ "getting-started/basic-usage/prowler-mcp-tools",
+ "getting-started/installation/prowler-mcp"
+ ]
+ },
+ {
+ "group": "Prowler for AI Agents",
+ "pages": [
+ "getting-started/products/prowler-claude-code-plugin"
+ ]
+ }
]
},
{
- "group": "Prowler CLI",
+ "group": "Open Source",
"pages": [
- "getting-started/products/prowler-cli",
- "getting-started/installation/prowler-cli",
- "getting-started/basic-usage/prowler-cli"
- ]
- },
- {
- "group": "Prowler App",
- "pages": [
- "getting-started/products/prowler-app",
- "getting-started/installation/prowler-app",
- "getting-started/basic-usage/prowler-app"
- ]
- },
- {
- "group": "Prowler Lighthouse AI",
- "pages": [
- "getting-started/products/prowler-lighthouse-ai"
- ]
- },
- {
- "group": "Prowler MCP Server",
- "pages": [
- "getting-started/products/prowler-mcp",
- "getting-started/installation/prowler-mcp",
- "getting-started/basic-usage/prowler-mcp",
- "getting-started/basic-usage/prowler-mcp-tools"
- ]
- },
- {
- "group": "Prowler Hub",
- "pages": [
- "getting-started/products/prowler-hub",
- "getting-started/goto/prowler-hub"
+ {
+ "group": "Prowler CLI",
+ "pages": [
+ "getting-started/products/prowler-cli",
+ "getting-started/installation/prowler-cli",
+ "getting-started/basic-usage/prowler-cli"
+ ]
+ },
+ {
+ "group": "Prowler Local Server",
+ "pages": [
+ "getting-started/products/prowler-app",
+ "getting-started/installation/prowler-app",
+ "getting-started/basic-usage/prowler-app"
+ ]
+ },
+ "getting-started/products/prowler-sdk"
]
},
{
@@ -105,32 +123,38 @@
"tab": "Guides",
"groups": [
{
- "group": "Prowler Cloud/App",
+ "group": "Prowler Cloud",
"pages": [
"user-guide/tutorials/prowler-app",
{
- "group": "Authentication",
+ "group": "Authentication & Access",
"pages": [
+ "user-guide/tutorials/prowler-app-api-keys",
+ "user-guide/tutorials/prowler-app-multi-tenant",
+ "user-guide/tutorials/prowler-app-sso",
"user-guide/tutorials/prowler-app-social-login",
- "user-guide/tutorials/prowler-app-sso"
+ "user-guide/tutorials/prowler-app-rbac"
]
},
- "user-guide/tutorials/prowler-app-rbac",
- "user-guide/tutorials/prowler-app-multi-tenant",
- "user-guide/tutorials/prowler-app-api-keys",
- "user-guide/tutorials/prowler-app-import-findings",
- "user-guide/tutorials/prowler-app-alerts",
{
- "group": "Mutelist",
- "expanded": true,
+ "group": "Compliance",
"pages": [
- "user-guide/tutorials/prowler-app-simple-mutelist",
- "user-guide/tutorials/prowler-app-mute-findings"
+ "user-guide/compliance/tutorials/compliance",
+ "user-guide/compliance/tutorials/cross-provider-compliance",
+ "user-guide/compliance/tutorials/threatscore"
+ ]
+ },
+ {
+ "group": "Findings",
+ "pages": [
+ "user-guide/tutorials/prowler-alerts",
+ "user-guide/tutorials/prowler-app-attack-paths",
+ "user-guide/tutorials/prowler-app-finding-groups",
+ "user-guide/tutorials/prowler-app-findings-triage"
]
},
{
"group": "Integrations",
- "expanded": true,
"pages": [
"user-guide/tutorials/prowler-app-s3-integration",
"user-guide/tutorials/prowler-app-security-hub-integration",
@@ -138,33 +162,64 @@
]
},
{
- "group": "AWS Organizations",
- "expanded": true,
+ "group": "Mutelist",
"pages": [
- "user-guide/tutorials/prowler-cloud-aws-organizations"
+ "user-guide/tutorials/prowler-app-mute-findings",
+ "user-guide/tutorials/prowler-app-simple-mutelist"
]
},
{
- "group": "Lighthouse AI",
+ "group": "Providers",
"pages": [
- "user-guide/tutorials/prowler-app-lighthouse",
- "user-guide/tutorials/prowler-app-lighthouse-multi-llm"
+ "user-guide/tutorials/prowler-cloud-aws-organizations",
+ "user-guide/tutorials/prowler-cloud-azure-management-groups",
+ "user-guide/tutorials/prowler-cloud-gcp-organizations"
+ ]
+ },
+ {
+ "group": "Scans",
+ "pages": [
+ "user-guide/tutorials/prowler-app-scan-configuration",
+ "user-guide/tutorials/prowler-import-findings",
+ "user-guide/tutorials/prowler-scan-scheduling"
]
},
- "user-guide/tutorials/prowler-app-attack-paths",
- "user-guide/tutorials/prowler-app-finding-groups",
- "user-guide/tutorials/prowler-cloud-public-ips",
{
"group": "Tutorials",
"pages": [
- "user-guide/tutorials/prowler-app-sso-entra",
- "user-guide/tutorials/prowler-app-sso-google-workspace",
+ "user-guide/tutorials/aws-organizations-bulk-provisioning",
"user-guide/tutorials/bulk-provider-provisioning",
- "user-guide/tutorials/aws-organizations-bulk-provisioning"
+ "user-guide/tutorials/prowler-app-sso-entra",
+ "user-guide/tutorials/prowler-app-sso-google-workspace"
]
}
]
},
+ {
+ "group": "Prowler Lighthouse AI",
+ "pages": [
+ {
+ "group": "Prowler Cloud",
+ "pages": [
+ "user-guide/tutorials/prowler-cloud-lighthouse-multi-llm"
+ ]
+ },
+ {
+ "group": "Prowler Local Server",
+ "pages": [
+ "getting-started/products/prowler-lighthouse-ai",
+ "user-guide/tutorials/prowler-app-lighthouse",
+ "user-guide/tutorials/prowler-app-lighthouse-multi-llm"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Prowler for AI Agents",
+ "pages": [
+ "getting-started/products/prowler-claude-code-plugin"
+ ]
+ },
{
"group": "CI/CD",
"pages": [
@@ -206,6 +261,13 @@
{
"group": "Providers",
"pages": [
+ {
+ "group": "Alibaba Cloud",
+ "pages": [
+ "user-guide/providers/alibabacloud/getting-started-alibabacloud",
+ "user-guide/providers/alibabacloud/authentication"
+ ]
+ },
{
"group": "AWS",
"pages": [
@@ -229,9 +291,31 @@
"user-guide/providers/azure/authentication",
"user-guide/providers/azure/use-non-default-cloud",
"user-guide/providers/azure/subscriptions",
+ "user-guide/providers/azure/resource-groups",
"user-guide/providers/azure/create-prowler-service-principal"
]
},
+ {
+ "group": "Cloudflare",
+ "pages": [
+ "user-guide/providers/cloudflare/getting-started-cloudflare",
+ "user-guide/providers/cloudflare/authentication"
+ ]
+ },
+ {
+ "group": "E2E Networks",
+ "pages": [
+ "user-guide/providers/e2enetworks/getting-started-e2enetworks",
+ "user-guide/providers/e2enetworks/authentication"
+ ]
+ },
+ {
+ "group": "GitHub",
+ "pages": [
+ "user-guide/providers/github/getting-started-github",
+ "user-guide/providers/github/authentication"
+ ]
+ },
{
"group": "Google Cloud",
"pages": [
@@ -243,10 +327,24 @@
]
},
{
- "group": "Alibaba Cloud",
+ "group": "Google Workspace",
"pages": [
- "user-guide/providers/alibabacloud/getting-started-alibabacloud",
- "user-guide/providers/alibabacloud/authentication"
+ "user-guide/providers/googleworkspace/getting-started-googleworkspace",
+ "user-guide/providers/googleworkspace/authentication"
+ ]
+ },
+ {
+ "group": "IaC",
+ "pages": [
+ "user-guide/providers/iac/getting-started-iac",
+ "user-guide/providers/iac/authentication"
+ ]
+ },
+ {
+ "group": "Image",
+ "pages": [
+ "user-guide/providers/image/getting-started-image",
+ "user-guide/providers/image/authentication"
]
},
{
@@ -256,6 +354,19 @@
"user-guide/providers/kubernetes/misc"
]
},
+ {
+ "group": "Linode",
+ "pages": [
+ "user-guide/providers/linode/getting-started-linode",
+ "user-guide/providers/linode/authentication"
+ ]
+ },
+ {
+ "group": "LLM",
+ "pages": [
+ "user-guide/providers/llm/getting-started-llm"
+ ]
+ },
{
"group": "Microsoft 365",
"pages": [
@@ -264,27 +375,6 @@
"user-guide/providers/microsoft365/use-of-powershell"
]
},
- {
- "group": "Google Workspace",
- "pages": [
- "user-guide/providers/googleworkspace/getting-started-googleworkspace",
- "user-guide/providers/googleworkspace/authentication"
- ]
- },
- {
- "group": "GitHub",
- "pages": [
- "user-guide/providers/github/getting-started-github",
- "user-guide/providers/github/authentication"
- ]
- },
- {
- "group": "IaC",
- "pages": [
- "user-guide/providers/iac/getting-started-iac",
- "user-guide/providers/iac/authentication"
- ]
- },
{
"group": "MongoDB Atlas",
"pages": [
@@ -293,30 +383,11 @@
]
},
{
- "group": "Cloudflare",
+ "group": "Okta",
"pages": [
- "user-guide/providers/cloudflare/getting-started-cloudflare",
- "user-guide/providers/cloudflare/authentication"
- ]
- },
- {
- "group": "Image",
- "pages": [
- "user-guide/providers/image/getting-started-image",
- "user-guide/providers/image/authentication"
- ]
- },
- {
- "group": "LLM",
- "pages": [
- "user-guide/providers/llm/getting-started-llm"
- ]
- },
- {
- "group": "Oracle Cloud Infrastructure",
- "pages": [
- "user-guide/providers/oci/getting-started-oci",
- "user-guide/providers/oci/authentication"
+ "user-guide/providers/okta/getting-started-okta",
+ "user-guide/providers/okta/authentication",
+ "user-guide/providers/okta/retry-configuration"
]
},
{
@@ -326,6 +397,13 @@
"user-guide/providers/openstack/authentication"
]
},
+ {
+ "group": "Oracle Cloud Infrastructure",
+ "pages": [
+ "user-guide/providers/oci/getting-started-oci",
+ "user-guide/providers/oci/authentication"
+ ]
+ },
{
"group": "Scaleway",
"pages": [
@@ -333,29 +411,22 @@
"user-guide/providers/scaleway/authentication"
]
},
+ {
+ "group": "StackIT",
+ "pages": [
+ "user-guide/providers/stackit/getting-started-stackit",
+ "user-guide/providers/stackit/authentication"
+ ]
+ },
{
"group": "Vercel",
"pages": [
"user-guide/providers/vercel/getting-started-vercel",
"user-guide/providers/vercel/authentication"
]
- },
- {
- "group": "Okta",
- "pages": [
- "user-guide/providers/okta/getting-started-okta",
- "user-guide/providers/okta/authentication"
- ]
}
]
},
- {
- "group": "Compliance",
- "pages": [
- "user-guide/compliance/tutorials/compliance",
- "user-guide/compliance/tutorials/threatscore"
- ]
- },
{
"group": "Cookbooks",
"pages": [
@@ -376,13 +447,15 @@
"developer-guide/provider",
"developer-guide/services",
"developer-guide/checks",
+ "developer-guide/secret-scanning-checks",
"developer-guide/outputs",
"developer-guide/integrations",
"developer-guide/security-compliance-framework",
"developer-guide/lighthouse-architecture",
"developer-guide/mcp-server",
"developer-guide/ai-skills",
- "developer-guide/prowler-studio"
+ "developer-guide/prowler-studio",
+ "developer-guide/server-sent-events"
]
},
{
@@ -395,13 +468,15 @@
"developer-guide/kubernetes-details",
"developer-guide/m365-details",
"developer-guide/github-details",
- "developer-guide/llm-details"
+ "developer-guide/llm-details",
+ "developer-guide/stackit-details"
]
},
{
"group": "Miscellaneous",
"pages": [
"developer-guide/documentation",
+ "developer-guide/environment-variables",
{
"group": "Testing",
"pages": [
@@ -459,10 +534,6 @@
"tab": "Changelog",
"icon": "github",
"href": "https://github.com/prowler-cloud/prowler/releases"
- },
- {
- "tab": "Public Roadmap",
- "href": "https://roadmap.prowler.com/"
}
],
"global": {
@@ -498,6 +569,13 @@
}
]
},
+ "banner": {
+ "content": "Prowler App is now Prowler Local Server, and Prowler Enterprise is now Prowler Private Cloud. See [Prowler product families](/getting-started/products).",
+ "dismissible": false
+ },
+ "markdown": {
+ "instructions": "Prowler product naming: Prowler App is now Prowler Local Server, and Prowler Enterprise is now Prowler Private Cloud. Always use the current names when answering. The full product reference is at /getting-started/products: Open Source projects are Prowler CLI, Prowler Local Server, Prowler Local Dashboard, and Prowler SDK; Prowler Products are Prowler Cloud, Prowler Private Cloud, Prowler Hub, Prowler Lighthouse AI, and Prowler MCP."
+ },
"analytics": {
"ga4": {
"measurementId": "G-KBKV70W5Y2"
@@ -570,6 +648,18 @@
{
"source": "/contact",
"destination": "/support"
+ },
+ {
+ "source": "/user-guide/tutorials/prowler-app-import-findings",
+ "destination": "/user-guide/tutorials/prowler-import-findings"
+ },
+ {
+ "source": "/user-guide/tutorials/prowler-app-alerts",
+ "destination": "/user-guide/tutorials/prowler-alerts"
+ },
+ {
+ "source": "/user-guide/tutorials/prowler-cloud-public-ips",
+ "destination": "/security/networking"
}
]
}
diff --git a/docs/getting-started/basic-usage/prowler-app.mdx b/docs/getting-started/basic-usage/prowler-app.mdx
index bc39353dcc..0f4cf80a91 100644
--- a/docs/getting-started/basic-usage/prowler-app.mdx
+++ b/docs/getting-started/basic-usage/prowler-app.mdx
@@ -2,7 +2,7 @@
title: 'Basic Usage'
---
-## Access Prowler App
+## Access Prowler Local Server
After [installation](/getting-started/installation/prowler-app), navigate to [http://localhost:3000](http://localhost:3000) and sign up with email and password.
@@ -28,7 +28,7 @@ This mechanism ensures that the first user in a newly created tenant has adminis
## Log In
-Access Prowler App by logging in with **email and password**.
+Access Prowler Local Server by logging in with **email and password**.
@@ -62,7 +62,7 @@ Review findings during scan execution in the following sections:
- **Compliance** – Displays compliance insights based on security frameworks.
-> For detailed usage instructions, refer to the [Prowler App Guide](/user-guide/tutorials/prowler-app).
+> For detailed usage instructions, refer to the [Prowler Cloud guide](/user-guide/tutorials/prowler-app), which also applies to Prowler Local Server.
Prowler will automatically scan all configured providers every **24 hours**, ensuring your cloud environment stays continuously monitored.
diff --git a/docs/getting-started/basic-usage/prowler-mcp-tools.mdx b/docs/getting-started/basic-usage/prowler-mcp-tools.mdx
index ec11680dd5..acb50c9e81 100644
--- a/docs/getting-started/basic-usage/prowler-mcp-tools.mdx
+++ b/docs/getting-started/basic-usage/prowler-mcp-tools.mdx
@@ -10,7 +10,7 @@ Complete reference guide for all tools available in the Prowler MCP Server. Tool
|----------|------------|------------------------|
| Prowler Hub | 10 tools | No |
| Prowler Documentation | 2 tools | No |
-| Prowler Cloud/App | 32 tools | Yes |
+| Prowler Cloud, Private Cloud & Local Server | 32 tools | Yes |
## Tool Naming Convention
@@ -18,11 +18,11 @@ All tools follow a consistent naming pattern with prefixes:
- `prowler_hub_*` - Prowler Hub catalog and compliance tools
- `prowler_docs_*` - Prowler documentation search and retrieval
-- `prowler_app_*` - Prowler Cloud and App (Self-Managed) management tools
+- `prowler_*` - Prowler Cloud, Prowler Private Cloud & Prowler Local Server management tools
-## Prowler Cloud/App Tools
+## Prowler Tools
-Manage Prowler Cloud or Prowler App (Self-Managed) features. **Requires authentication.**
+Manage your Prowler deployment — Prowler Cloud, Prowler Private Cloud, or Prowler Local Server. **Requires authentication.**
These tools require a valid API key. See the [Configuration Guide](/getting-started/basic-usage/prowler-mcp) for authentication setup.
@@ -32,44 +32,44 @@ These tools require a valid API key. See the [Configuration Guide](/getting-star
Tools for searching, viewing, and analyzing security findings across all cloud providers.
-- **`prowler_app_search_security_findings`** - Search and filter security findings with advanced filtering options (severity, status, provider, region, service, check ID, date range, muted status)
-- **`prowler_app_get_finding_details`** - Get comprehensive details about a specific finding including remediation guidance, check metadata, and resource relationships
-- **`prowler_app_get_findings_overview`** - Get aggregate statistics and trends about security findings as a markdown report
+- **`prowler_search_security_findings`** - Search and filter security findings with advanced filtering options (severity, status, provider, region, service, check ID, date range, muted status)
+- **`prowler_get_finding_details`** - Get comprehensive details about a specific finding including remediation guidance, check metadata, and resource relationships
+- **`prowler_get_findings_overview`** - Get aggregate statistics and trends about security findings as a markdown report
### Finding Groups Management
Tools for listing finding groups aggregated by check ID, viewing complete group counters, and drilling down into affected resources.
-- **`prowler_app_list_finding_groups`** - List latest or historical finding groups with filters for provider, region, service, resource, category, check, severity, status, muted state, delta, date range, and sorting
-- **`prowler_app_get_finding_group_details`** - Get complete details for a specific finding group including counters, description, timestamps, and impacted providers
-- **`prowler_app_list_finding_group_resources`** - List actionable unmuted resources affected by a finding group by default, including nested resource and provider data plus the `finding_id` for remediation details. Set `include_muted` to include suppressed resources
+- **`prowler_list_finding_groups`** - List latest or historical finding groups with filters for provider, region, service, resource, category, check, severity, status, muted state, delta, date range, and sorting
+- **`prowler_get_finding_group_details`** - Get complete details for a specific finding group including counters, description, timestamps, and impacted providers
+- **`prowler_list_finding_group_resources`** - List actionable unmuted resources affected by a finding group by default, including nested resource and provider data plus the `finding_id` for remediation details. Set `include_muted` to include suppressed resources
### Provider Management
Tools for managing cloud provider connections in Prowler.
-- **`prowler_app_search_providers`** - Search and view configured providers with their connection status
-- **`prowler_app_connect_provider`** - Register and connect a provider with credentials for security scanning
-- **`prowler_app_delete_provider`** - Permanently remove a provider from Prowler
+- **`prowler_search_providers`** - Search and view configured providers with their connection status
+- **`prowler_connect_provider`** - Register and connect a provider with credentials for security scanning
+- **`prowler_delete_provider`** - Permanently remove a provider from Prowler
### Scan Management
Tools for managing and monitoring security scans.
-- **`prowler_app_list_scans`** - List and filter security scans across all providers
-- **`prowler_app_get_scan`** - Get comprehensive details about a specific scan (progress, duration, resource counts)
-- **`prowler_app_trigger_scan`** - Trigger a manual security scan for a provider
-- **`prowler_app_schedule_daily_scan`** - Schedule automated daily scans for continuous monitoring
-- **`prowler_app_update_scan`** - Update scan name for better organization
+- **`prowler_list_scans`** - List and filter security scans across all providers
+- **`prowler_get_scan`** - Get comprehensive details about a specific scan (progress, duration, resource counts)
+- **`prowler_trigger_scan`** - Trigger a manual security scan for a provider
+- **`prowler_schedule_daily_scan`** - Schedule automated daily scans for continuous monitoring
+- **`prowler_update_scan`** - Update scan name for better organization
### Resources Management
Tools for searching, viewing, and analyzing cloud resources discovered by Prowler.
-- **`prowler_app_list_resources`** - List and filter cloud resources with advanced filtering options (provider, region, service, resource type, tags)
-- **`prowler_app_get_resource`** - Get comprehensive details about a specific resource including configuration, metadata, and finding relationships
-- **`prowler_app_get_resource_events`** - Get the timeline of cloud API actions performed on a resource (AWS CloudTrail). Shows who did what and when, with full request/response payloads
-- **`prowler_app_get_resources_overview`** - Get aggregate statistics about cloud resources as a markdown report
+- **`prowler_list_resources`** - List and filter cloud resources with advanced filtering options (provider, region, service, resource type, tags)
+- **`prowler_get_resource`** - Get comprehensive details about a specific resource including configuration, metadata, and finding relationships
+- **`prowler_get_resource_events`** - Get the timeline of cloud API actions performed on a resource (AWS CloudTrail). Shows who did what and when, with full request/response payloads
+- **`prowler_get_resources_overview`** - Get aggregate statistics about cloud resources as a markdown report
### Muting Management
@@ -77,33 +77,33 @@ Tools for managing finding muting, including pattern-based bulk muting (mutelist
#### Mutelist (Pattern-Based Muting)
-- **`prowler_app_get_mutelist`** - Retrieve the current mutelist configuration for the tenant
-- **`prowler_app_set_mutelist`** - Create or update the mutelist configuration for pattern-based bulk muting
-- **`prowler_app_delete_mutelist`** - Remove the mutelist configuration from the tenant
+- **`prowler_get_mutelist`** - Retrieve the current mutelist configuration for the tenant
+- **`prowler_set_mutelist`** - Create or update the mutelist configuration for pattern-based bulk muting
+- **`prowler_delete_mutelist`** - Remove the mutelist configuration from the tenant
#### Mute Rules (Finding-Specific Muting)
-- **`prowler_app_list_mute_rules`** - Search and filter mute rules with pagination support
-- **`prowler_app_get_mute_rule`** - Retrieve comprehensive details about a specific mute rule
-- **`prowler_app_create_mute_rule`** - Create a new mute rule to mute specific findings with documentation and audit trail
-- **`prowler_app_update_mute_rule`** - Update a mute rule's name, reason, or enabled status
-- **`prowler_app_delete_mute_rule`** - Delete a mute rule from the system
+- **`prowler_list_mute_rules`** - Search and filter mute rules with pagination support
+- **`prowler_get_mute_rule`** - Retrieve comprehensive details about a specific mute rule
+- **`prowler_create_mute_rule`** - Create a new mute rule to mute specific findings with documentation and audit trail
+- **`prowler_update_mute_rule`** - Update a mute rule's name, reason, or enabled status
+- **`prowler_delete_mute_rule`** - Delete a mute rule from the system
### Attack Paths Analysis
Tools for analyzing privilege escalation chains and security misconfigurations using graph-based analysis. Attack Paths maps relationships between cloud resources, permissions, and security findings to detect how privileges can be escalated and how misconfigurations can be exploited.
-- **`prowler_app_list_attack_paths_scans`** - List Attack Paths scans with filtering by provider, provider type, and scan state (available, scheduled, executing, completed, failed, cancelled)
-- **`prowler_app_list_attack_paths_queries`** - Discover available Attack Paths queries for a completed scan, including query names, descriptions, and required parameters
-- **`prowler_app_run_attack_paths_query`** - Execute an Attack Paths query against a completed scan and retrieve graph results with nodes (cloud resources, findings, virtual nodes) and relationships (access paths, role assumptions, security group memberships)
-- **`prowler_app_get_attack_paths_cartography_schema`** - Retrieve the Cartography graph schema (node labels, relationships, properties) for writing accurate custom openCypher queries
+- **`prowler_list_attack_paths_scans`** - List Attack Paths scans with filtering by provider, provider type, and scan state (available, scheduled, executing, completed, failed, cancelled)
+- **`prowler_list_attack_paths_queries`** - Discover available Attack Paths queries for a completed scan, including query names, descriptions, and required parameters
+- **`prowler_run_attack_paths_query`** - Execute an Attack Paths query against a completed scan and retrieve graph results with nodes (cloud resources, findings, virtual nodes) and relationships (access paths, role assumptions, security group memberships)
+- **`prowler_get_attack_paths_cartography_schema`** - Retrieve the Cartography graph schema (node labels, relationships, properties) for writing accurate custom openCypher queries
### Compliance Management
Tools for viewing compliance status and framework details across all cloud providers.
-- **`prowler_app_get_compliance_overview`** - Get high-level compliance status across all frameworks for a specific scan or provider, including pass/fail statistics per framework
-- **`prowler_app_get_compliance_framework_state_details`** - Get detailed requirement-level breakdown for a specific compliance framework, including failed requirements and associated finding IDs
+- **`prowler_get_compliance_overview`** - Get high-level compliance status across all frameworks for a specific scan or provider, including pass/fail statistics per framework
+- **`prowler_get_compliance_framework_state_details`** - Get detailed requirement-level breakdown for a specific compliance framework, including failed requirements and associated finding IDs
## Prowler Hub Tools
@@ -145,7 +145,7 @@ Search and access official Prowler documentation. **No authentication required.*
- Use natural language to interact with the tools through your AI assistant
- Tools can be combined for complex workflows
- Filter options are available on most list tools
-- Authentication is only required for Prowler Cloud/App tools
+- Authentication is only required for Prowler tools (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server)
## Additional Resources
diff --git a/docs/getting-started/basic-usage/prowler-mcp.mdx b/docs/getting-started/basic-usage/prowler-mcp.mdx
index 2c32dbdbfc..120e5c038b 100644
--- a/docs/getting-started/basic-usage/prowler-mcp.mdx
+++ b/docs/getting-started/basic-usage/prowler-mcp.mdx
@@ -7,10 +7,10 @@ Configure your MCP client to connect to Prowler MCP Server.
## Step 1: Get Your API Key
-**Authentication is optional**: Prowler Hub and Prowler Documentation features work without authentication. An API key is only required for Prowler Cloud and Prowler App (Self-Managed) features.
+**Authentication is optional**: Prowler Hub and Prowler Documentation features work without authentication. An API key is only required for Prowler tools (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server).
-To use Prowler Cloud or Prowler App (Self-Managed) features. To get the API key, please refer to the [API Keys](/user-guide/tutorials/prowler-app-api-keys) guide.
+An API key authenticates the Prowler tools (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server). To get the API key, please refer to the [API Keys](/user-guide/tutorials/prowler-app-api-keys) guide.
Keep the API key secure. Never share it publicly or commit it to version control.
@@ -18,12 +18,14 @@ Keep the API key secure. Never share it publicly or commit it to version control
## Step 2: Configure Your MCP Host/Client
-Choose the configuration based on your deployment:
+Most users should use the **Cloud MCP Server** — it needs no installation and is maintained by Prowler. The [Local MCP Server](#local-mcp-server-configuration) configuration is provided afterwards for users who run the server themselves.
-- **HTTP Mode**: Prowler Cloud MCP Server or self-hosted Prowler MCP Server.
-- **STDIO Mode**: Local installation only (runs as subprocess of your MCP client).
+- **Cloud MCP Server (HTTP)**: the managed server at `https://mcp.prowler.com/mcp` (or your own self-hosted HTTP server).
+- **Local MCP Server (STDIO)**: local installation only (runs as a subprocess of your MCP client).
-### HTTP Mode
+## Cloud MCP Server Configuration (Recommended)
+
+Connect to the **Cloud MCP Server** at `https://mcp.prowler.com/mcp` over HTTP. This is the recommended path — no installation, always up to date. The same configuration works for a self-hosted HTTP server: just swap the URL.
@@ -61,10 +63,10 @@ Choose the configuration based on your deployment:
"args": [
"https://mcp.prowler.com/mcp", // or your self-hosted Prowler MCP Server URL
"--header",
- "Authorization: Bearer ${PROWLER_APP_API_KEY}"
+ "Authorization: Bearer ${PROWLER_API_KEY}"
],
"env": {
- "PROWLER_APP_API_KEY": ""
+ "PROWLER_API_KEY": ""
}
}
}
@@ -96,10 +98,10 @@ Choose the configuration based on your deployment:
"args": [
"https://mcp.prowler.com/mcp",
"--header",
- "Authorization: Bearer ${PROWLER_APP_API_KEY}"
+ "Authorization: Bearer ${PROWLER_API_KEY}"
],
"env": {
- "PROWLER_APP_API_KEY": ""
+ "PROWLER_API_KEY": ""
}
}
}
@@ -110,8 +112,8 @@ Choose the configuration based on your deployment:
Run the following command:
```bash
- export PROWLER_APP_API_KEY=""
- claude mcp add --transport http prowler https://mcp.prowler.com/mcp --header "Authorization: Bearer $PROWLER_APP_API_KEY" --scope user
+ export PROWLER_API_KEY=""
+ claude mcp add --transport http prowler https://mcp.prowler.com/mcp --header "Authorization: Bearer $PROWLER_API_KEY" --scope user
```
@@ -137,9 +139,9 @@ Choose the configuration based on your deployment:
-### STDIO Mode
+## Local MCP Server Configuration
-STDIO mode is only available when running the MCP server locally.
+STDIO mode is only available when running the **Local MCP Server** on your own machine. See the [Installation guide](/getting-started/installation/prowler-mcp) to set it up first.
@@ -152,7 +154,7 @@ STDIO mode is only available when running the MCP server locally.
"command": "uvx",
"args": ["/absolute/path/to/prowler/mcp_server/"],
"env": {
- "PROWLER_APP_API_KEY": "",
+ "PROWLER_API_KEY": "",
"API_BASE_URL": "https://api.prowler.com/api/v1"
}
}
@@ -179,7 +181,7 @@ STDIO mode is only available when running the MCP server locally.
"--rm",
"-i",
"--env",
- "PROWLER_APP_API_KEY=",
+ "PROWLER_API_KEY=",
"--env",
"API_BASE_URL=https://api.prowler.com/api/v1",
"prowlercloud/prowler-mcp"
@@ -205,7 +207,7 @@ Restart your MCP client and start asking questions:
## Authentication Methods
-Prowler MCP Server supports two authentication methods to connect to Prowler Cloud or Prowler App (Self-Managed):
+Prowler MCP Server supports two authentication methods to connect to Prowler (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server):
### API Key (Recommended)
diff --git a/docs/getting-started/installation/prowler-app.mdx b/docs/getting-started/installation/prowler-app.mdx
index f2ac07da72..1994b8ad0f 100644
--- a/docs/getting-started/installation/prowler-app.mdx
+++ b/docs/getting-started/installation/prowler-app.mdx
@@ -4,9 +4,9 @@ title: "Installation"
### Installation
-Prowler App offers flexible installation methods tailored to various environments.
+Prowler Local Server offers flexible installation methods tailored to various environments.
-Refer to the [Prowler App Tutorial](/user-guide/tutorials/prowler-app) for detailed usage instructions.
+Refer to the [Prowler Cloud guide](/user-guide/tutorials/prowler-app) for detailed usage instructions.
Prowler configuration is based on `.env` files. Every version of Prowler can have differences on that file, so, please, use the file that corresponds with that version or repository branch or tag.
@@ -20,7 +20,8 @@ Refer to the [Prowler App Tutorial](/user-guide/tutorials/prowler-app) for detai
_Commands_:
- ```bash
+
+ ```bash macOS/Linux
VERSION=$(curl -s https://api.github.com/repos/prowler-cloud/prowler/releases/latest | jq -r .tag_name)
curl -sLO "https://raw.githubusercontent.com/prowler-cloud/prowler/refs/tags/${VERSION}/docker-compose.yml"
# Environment variables can be customized in the .env file. Using default values in production environments is not recommended.
@@ -28,6 +29,15 @@ Refer to the [Prowler App Tutorial](/user-guide/tutorials/prowler-app) for detai
docker compose up -d
```
+ ```powershell Windows PowerShell
+ $VERSION = (Invoke-RestMethod -Uri "https://api.github.com/repos/prowler-cloud/prowler/releases/latest").tag_name
+ Invoke-WebRequest -Uri "https://raw.githubusercontent.com/prowler-cloud/prowler/refs/tags/$VERSION/docker-compose.yml" -OutFile "docker-compose.yml"
+ # Environment variables can be customized in the .env file. Using default values in production environments is not recommended.
+ Invoke-WebRequest -Uri "https://raw.githubusercontent.com/prowler-cloud/prowler/refs/tags/$VERSION/.env" -OutFile ".env"
+ docker compose up -d
+ ```
+
+
For a secure setup, the API auto-generates a unique key pair, `DJANGO_TOKEN_SIGNING_KEY` and `DJANGO_TOKEN_VERIFYING_KEY`, and stores it in `~/.config/prowler-api` (non-container) or the bound Docker volume in `_data/api` (container). Never commit or reuse static/default keys. To rotate keys, delete the stored key files and restart the API.
@@ -99,17 +109,17 @@ Refer to the [Prowler App Tutorial](/user-guide/tutorials/prowler-app) for detai
pnpm start
```
- > Enjoy Prowler App at http://localhost:3000 by signing up with your email and password.
+ > Enjoy Prowler Local Server at http://localhost:3000 by signing up with your email and password.
- Google and GitHub authentication is only available in [Prowler Cloud](https://prowler.com).
+ Google and GitHub authentication works out of the box in [Prowler Cloud](https://prowler.com). In Prowler Local Server it requires OAuth credentials: see [Social Login Configuration](/user-guide/tutorials/prowler-app-social-login).
-### Updating Prowler App
+### Updating Prowler Local Server
-Upgrade Prowler App installation using one of two options:
+Upgrade Prowler Local Server installation using one of two options:
#### Option 1: Updating the Environment File
@@ -118,12 +128,12 @@ To update the environment file:
Edit the `.env` file and change version values:
```env
-PROWLER_UI_VERSION="5.27.0"
-PROWLER_API_VERSION="5.27.0"
+PROWLER_UI_VERSION="5.35.0"
+PROWLER_API_VERSION="5.35.0"
```
- You can find the latest versions of Prowler App in the [Releases Github section](https://github.com/prowler-cloud/prowler/releases) or in the [Container Versions](#container-versions) section of this documentation.
+ You can find the latest versions of Prowler Local Server in the [Releases Github section](https://github.com/prowler-cloud/prowler/releases) or in the [Container Versions](#container-versions) section of this documentation.
@@ -162,7 +172,7 @@ docker compose up -d
### Container Versions
-The available versions of Prowler App are the following:
+The available versions of Prowler Local Server are the following:
- `latest`: in sync with `master` branch (please note that it is not a stable version)
- `v4-latest`: in sync with `v4` branch (please note that it is not a stable version)
@@ -174,6 +184,6 @@ The available versions of Prowler App are the following:
The container images are available here:
-- Prowler App:
+- Prowler Local Server:
- [DockerHub - Prowler UI](https://hub.docker.com/r/prowlercloud/prowler-ui/tags)
- [DockerHub - Prowler API](https://hub.docker.com/r/prowlercloud/prowler-api/tags)
diff --git a/docs/getting-started/installation/prowler-cli.mdx b/docs/getting-started/installation/prowler-cli.mdx
index 2c79eda37c..eae3d54ab1 100644
--- a/docs/getting-started/installation/prowler-cli.mdx
+++ b/docs/getting-started/installation/prowler-cli.mdx
@@ -4,7 +4,7 @@ title: 'Installation'
## Installation
-To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler is available as a project in [PyPI](https://pypi.org/project/prowler/):
+To install Prowler as a Python package, use `Python >= 3.10, <= 3.13`. Prowler is available as a project in [PyPI](https://pypi.org/project/prowler/):
@@ -12,7 +12,7 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
_Requirements_:
- * `Python >= 3.10, <= 3.12`
+ * `Python >= 3.10, <= 3.13`
* `pipx` installed: [pipx installation](https://pipx.pypa.io/stable/installation/).
* AWS, GCP, Azure and/or Kubernetes credentials
@@ -30,7 +30,7 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
_Requirements_:
- * `Python >= 3.10, <= 3.12`
+ * `Python >= 3.10, <= 3.13`
* `Python pip >= 21.0.0`
* AWS, GCP, Azure, M365 and/or Kubernetes credentials
@@ -40,12 +40,6 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
pip install prowler
prowler -v
```
-
- To upgrade Prowler to the latest version:
-
- ``` bash
- pip install --upgrade prowler
- ```
_Requirements_:
@@ -87,7 +81,7 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
_Requirements_:
- * `Python >= 3.10, <= 3.12`
+ * `Python >= 3.10, <= 3.13`
* AWS, GCP, Azure and/or Kubernetes credentials
_Commands_:
@@ -102,8 +96,8 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
_Requirements_:
- * `Ubuntu 23.04` or above. For older Ubuntu versions, check [pipx installation](https://docs.prowler.com/projects/prowler-open-source/en/latest/#__tabbed_1_1) and ensure `Python >= 3.10, <= 3.12` is installed.
- * `Python >= 3.10, <= 3.12`
+ * `Ubuntu 23.04` or above. For older Ubuntu versions, check [pipx installation](https://docs.prowler.com/projects/prowler-open-source/en/latest/#__tabbed_1_1) and ensure `Python >= 3.10, <= 3.13` is installed.
+ * `Python >= 3.10, <= 3.13`
* AWS, GCP, Azure and/or Kubernetes credentials
_Commands_:
@@ -170,6 +164,68 @@ To install Prowler as a Python package, use `Python >= 3.10, <= 3.12`. Prowler i
+## Updating Prowler CLI
+
+Upgrade Prowler CLI to the latest release using the same method chosen for installation:
+
+
+
+ ```bash
+ pipx upgrade prowler
+ prowler -v
+ ```
+
+
+ ```bash
+ pip install --upgrade prowler
+ prowler -v
+ ```
+
+
+ Pull the desired image tag to fetch the latest version:
+
+ ```bash
+ docker pull toniblyx/prowler:latest
+ ```
+
+
+ Replace `latest` with a specific release tag (for example, `stable` or ``) to pin a version. Refer to the [Container Versions](#container-versions) section for the full list of available tags.
+
+
+
+ Pull the latest changes and sync the environment:
+
+ ```bash
+ cd prowler
+ git pull
+ uv sync
+ uv run python prowler-cli.py -v
+ ```
+
+
+ To upgrade to a specific release, check out the corresponding tag before syncing: `git checkout `.
+
+
+
+ ```bash
+ brew upgrade prowler
+ prowler -v
+ ```
+
+
+ Both AWS CloudShell and Azure CloudShell install Prowler with `pipx`, so the upgrade command is the same:
+
+ ```bash
+ pipx upgrade prowler
+ prowler -v
+ ```
+
+
+
+
+ To install a specific version instead of the latest release, pin it explicitly. For example, with `pipx`: `pipx install prowler==`, or with `pip`: `pip install prowler==`. The available releases are listed in the [Releases GitHub section](https://github.com/prowler-cloud/prowler/releases).
+
+
## Container Versions
The available versions of Prowler CLI are the following:
diff --git a/docs/getting-started/installation/prowler-mcp.mdx b/docs/getting-started/installation/prowler-mcp.mdx
index 7bf766e143..5be469b5b2 100644
--- a/docs/getting-started/installation/prowler-mcp.mdx
+++ b/docs/getting-started/installation/prowler-mcp.mdx
@@ -5,12 +5,12 @@ title: "Installation"
There are **two ways** to use Prowler MCP Server:
-
+
**No installation required** - Just configuration
Use `https://mcp.prowler.com/mcp`
-
+
**Local installation** - Full control
Install via Docker, PyPI, or source code
@@ -18,8 +18,8 @@ There are **two ways** to use Prowler MCP Server:
-For "Option 1: Managed by Prowler", go directly to the [Configuration Guide](/getting-started/basic-usage/prowler-mcp#hosted-server-configuration-recommended) to set up your Claude Desktop, Cursor, or other MCP client.
-**This guide is focused on local installation, "Option 2: Run Locally"**.
+For the Cloud MCP Server, go directly to the [Configuration Guide](/getting-started/basic-usage/prowler-mcp#cloud-mcp-server-configuration-recommended) to set up your Claude Desktop, Cursor, or other MCP client.
+**This guide is focused on local installation, the Local MCP Server**.
## Installation Methods
@@ -51,7 +51,7 @@ Choose one of the following installation methods:
```bash
docker run --rm -i \
- -e PROWLER_APP_API_KEY="pk_your_api_key" \
+ -e PROWLER_API_KEY="pk_your_api_key" \
-e API_BASE_URL="https://api.prowler.com/api/v1" \
prowlercloud/prowler-mcp
```
@@ -141,6 +141,45 @@ Choose one of the following installation methods:
---
+## Updating Prowler MCP Server
+
+When running the Local MCP Server, upgrade to the latest version using the same method chosen for installation. The Cloud MCP Server (`https://mcp.prowler.com/mcp`) is always kept up to date by Prowler and requires no action.
+
+
+
+ Pull the latest image and restart the container:
+
+ ```bash
+ docker pull prowlercloud/prowler-mcp
+ ```
+
+
+ Recreate any running container after pulling the new image so the updated version takes effect.
+
+
+
+ Pull the latest changes and sync the dependencies:
+
+ ```bash
+ cd prowler/mcp_server
+ git pull
+ uv sync
+ uv run prowler-mcp --help
+ ```
+
+
+ Pull the latest source and rebuild the image:
+
+ ```bash
+ cd prowler/mcp_server
+ git pull
+ docker build -t prowler-mcp .
+ ```
+
+
+
+---
+
## Command Line Options
The Prowler MCP Server supports the following command-line arguments:
@@ -180,19 +219,19 @@ Configure the server using environment variables:
| Variable | Description | Required | Default |
|----------|-------------|----------|---------|
-| `PROWLER_APP_API_KEY` | Prowler API key | Only for STDIO mode | - |
+| `PROWLER_API_KEY` | Prowler API key | Only for STDIO mode | - |
| `API_BASE_URL` | Custom Prowler API endpoint | No | `https://api.prowler.com/api/v1` |
| `PROWLER_MCP_TRANSPORT_MODE` | Default transport mode (overwritten by `--transport` argument) | No | `stdio` |
```bash macOS/Linux
-export PROWLER_APP_API_KEY="pk_your_api_key_here"
+export PROWLER_API_KEY="pk_your_api_key_here"
export API_BASE_URL="https://api.prowler.com/api/v1"
export PROWLER_MCP_TRANSPORT_MODE="http"
```
```bash Windows PowerShell
-$env:PROWLER_APP_API_KEY="pk_your_api_key_here"
+$env:PROWLER_API_KEY="pk_your_api_key_here"
$env:API_BASE_URL="https://api.prowler.com/api/v1"
$env:PROWLER_MCP_TRANSPORT_MODE="http"
```
@@ -207,7 +246,7 @@ Never commit your API key to version control. Use environment variables or secur
For convenience, create a `.env` file in the `mcp_server` directory:
```bash .env
-PROWLER_APP_API_KEY=pk_your_api_key_here
+PROWLER_API_KEY=pk_your_api_key_here
API_BASE_URL=https://api.prowler.com/api/v1
PROWLER_MCP_TRANSPORT_MODE=stdio
```
diff --git a/docs/getting-started/products/index.mdx b/docs/getting-started/products/index.mdx
new file mode 100644
index 0000000000..c14ea37471
--- /dev/null
+++ b/docs/getting-started/products/index.mdx
@@ -0,0 +1,52 @@
+---
+title: 'Prowler Product Families'
+description: 'Official names for Prowler Open Source projects and Prowler Products, including former product names.'
+boost: 2
+---
+
+Prowler ships two product families: Prowler Products, operated or licensed by the Prowler team, and Open Source projects, free to run and extend. This page is the reference for every official name. If a page or blog post uses a former name, the [Former Names](#former-names) table maps it to the current one.
+
+
+Read the [public announcement of the Prowler product families](https://prowler-workspace.slack.com/archives/C03JUQVM33L/p1784120677833319) in our Slack community.
+
+
+## Prowler Products
+
+| Name | Description |
+|------|-------------|
+| [Prowler Cloud](/getting-started/products/prowler-cloud) | Managed cloud security platform operated by the Prowler team. See [pricing](https://prowler.com/pricing). |
+| Prowler Private Cloud | Prowler Cloud deployed in your own environment. Formerly Prowler Enterprise. See [pricing](https://prowler.com/pricing). |
+| [Prowler Hub](https://hub.prowler.com) | Free public library of versioned checks, cloud service artifacts, and compliance frameworks. |
+| [Prowler Lighthouse AI](/getting-started/products/prowler-cloud-lighthouse) | AI security analyst capabilities within Prowler Cloud and Prowler Private Cloud. |
+| [Prowler MCP](/getting-started/products/prowler-mcp) | MCP server that connects AI assistants and agents to Prowler, including IDE plugins such as [Prowler for Claude Code](/getting-started/products/prowler-claude-code-plugin). |
+
+{/* Unreleased products. Uncomment these rows in the Prowler Products table when announced:
+| Prowler Registry | Distribution service for Prowler content such as checks and compliance frameworks. Free and paid tiers. |
+| Prowler Local Registry | Prowler Registry running in your own environment. Paid. |
+*/}
+
+
+Throughout this documentation, the green cloud icon in the sidebar marks sections and pages for capabilities that require a Prowler Cloud or Prowler Private Cloud [subscription](https://prowler.com/pricing).
+
+
+Products without a documentation page here are available through the Prowler team. [Contact us](https://prowler.com/contact) for details.
+
+## Open Source Projects
+
+| Name | Description |
+|------|-------------|
+| [Prowler CLI](/getting-started/products/prowler-cli) | Command line tool to run security scans across all supported providers. |
+| [Prowler Local Server](/getting-started/products/prowler-app) | Self-hosted web application and API to run scans, visualize findings, and manage cloud providers. Formerly Prowler App. |
+| [Prowler Local Dashboard](/user-guide/cli/tutorials/dashboard) | Local web dashboard to visualize scan results from Prowler CLI CSV outputs. Shipped with Prowler CLI. |
+| [Prowler SDK](/getting-started/products/prowler-sdk) | Python library that powers Prowler CLI and Prowler Local Server. Part of the [prowler repository](https://github.com/prowler-cloud/prowler). |
+
+## Former Names
+
+| Former name | Current name |
+|-------------|--------------|
+| Prowler App | [Prowler Local Server](/getting-started/products/prowler-app) |
+| Prowler Enterprise | Prowler Private Cloud |
+
+## Prowler for MSPs and MSSPs
+
+Prowler partners with managed service providers (MSPs) and managed security service providers (MSSPs) that operate Prowler for their customers. Visit [partners.prowler.com](https://partners.prowler.com) to become a partner.
diff --git a/docs/getting-started/products/prowler-app.mdx b/docs/getting-started/products/prowler-app.mdx
index 2df6015d06..76af591ba0 100644
--- a/docs/getting-started/products/prowler-app.mdx
+++ b/docs/getting-started/products/prowler-app.mdx
@@ -2,16 +2,16 @@
title: 'Overview'
---
-Prowler App is a web application that simplifies running Prowler. It provides:
+Prowler Local Server is a self-hosted web application that simplifies running Prowler. It provides:
- **User-friendly interface** for configuring and executing scans
- Dashboard to **view results** and manage **security findings**
-
+
## Components
-Prowler App consists of four main components:
+Prowler Local Server consists of four main components:
- **Prowler UI**: User-friendly web interface for running Prowler and viewing results, powered by Next.js
- **Prowler API**: Backend API that executes Prowler scans and stores results, built with Django REST Framework
@@ -26,4 +26,42 @@ Supporting infrastructure includes:
- **Valkey**: In-memory database serving as message broker for Celery workers
- **Neo4j**: Graph database used by the Attack Paths feature to combine cloud inventory with Prowler findings (currently populated by AWS scans)
-
+```mermaid
+flowchart TB
+ user([User / Security Team])
+ cli([Prowler CLI])
+
+ subgraph APP["Prowler Local Server"]
+ ui["Prowler UI
(Next.js)"]
+ api["Prowler API
(Django REST Framework)"]
+ worker["API Worker
(Celery)"]
+ beat["API Scheduler
(Celery Beat)"]
+ mcp["Prowler MCP Server
(Lighthouse AI tools)"]
+ end
+
+ sdk["Prowler SDK
(Python)"]
+
+ subgraph DATA["Data Layer"]
+ pg[("PostgreSQL")]
+ valkey[("Valkey / Redis")]
+ neo4j[("Neo4j")]
+ end
+
+ providers["Providers"]
+
+ user --> ui
+ user --> cli
+ ui -->|REST| api
+ ui -->|MCP HTTP| mcp
+ mcp -->|REST| api
+ api --> pg
+ api --> valkey
+ beat -->|enqueue jobs| valkey
+ valkey -->|dispatch| worker
+ worker --> pg
+ worker -->|Attack Paths| neo4j
+ worker -->|invokes| sdk
+ cli --> sdk
+
+ sdk --> providers
+```
diff --git a/docs/getting-started/products/prowler-claude-code-plugin.mdx b/docs/getting-started/products/prowler-claude-code-plugin.mdx
new file mode 100644
index 0000000000..99c92a1488
--- /dev/null
+++ b/docs/getting-started/products/prowler-claude-code-plugin.mdx
@@ -0,0 +1,102 @@
+---
+title: 'Prowler for Claude Code'
+sidebarTitle: 'Claude Code'
+---
+
+End-to-end cloud security and compliance from inside [Claude Code](https://www.claude.com/product/claude-code), powered by the [Prowler MCP server](/getting-started/products/prowler-mcp). The plugin lets Claude walk a Prowler Cloud-connected account through a compliance assessment and remediate findings until the chosen security or industry framework is compliant.
+
+
+**Preview**: this plugin is under active development. Please report issues on [GitHub](https://github.com/prowler-cloud/prowler/issues) or join the [Slack community](https://goto.prowler.com/slack) for feedback.
+
+
+## Requirements
+
+
+
+ Installed and signed in. See the [official install guide](https://www.claude.com/product/claude-code).
+
+
+ The free tier is enough to start. Sign up at [cloud.prowler.com](https://cloud.prowler.com).
+
+
+ Create one at [cloud.prowler.com/profile](https://cloud.prowler.com/profile).
+
+
+
+## Installation
+
+
+
+ Inside a Claude Code session:
+
+ ```text
+ /plugin marketplace add prowler-cloud/prowler
+ /plugin install prowler@prowler-plugins
+ ```
+
+
+ If you already have the repository checked out:
+
+ ```text
+ /plugin marketplace add /absolute/path/to/prowler
+ /plugin install prowler@prowler-plugins
+ ```
+
+
+
+## Configuration
+
+On first install, Claude Code prompts for your **Prowler API key**. The value is stored securely (macOS keychain or `~/.claude/.credentials.json`) and used to authenticate against Prowler Cloud.
+
+
+To rotate the key, uninstall and reinstall the plugin — Claude Code will prompt again.
+
+
+## Verify the installation
+
+In a Claude Code session:
+
+```text
+/mcp → "prowler" appears as a connected server
+/plugin → "prowler" enabled, skill listed as prowler:framework-compliance-triage
+```
+
+If `/mcp` reports the `prowler` server as failed, the most common cause is a rejected API key — re-issue one in Prowler Cloud and reinstall the plugin so it re-prompts.
+
+## Usage
+
+Open a conversation that mentions the framework you want to comply with. Examples:
+
+- *"Make my AWS production account compliant with CIS 4.0."*
+- *"Make my current Terraform project compliant with Prowler ThreatScore Compliance Framework based on the latest scan results."*
+- *"Help me get to 100% on PCI-DSS for this GCP project."*
+
+You pick a **primary tool** (Terraform, gh / az / aws CLI, web console, or mixed) and a **mode**:
+
+
+
+ Claude shows each fix — target resource, exact commands, side effects, reversibility — and waits for your go-ahead before applying.
+
+
+ Claude presents a single up-front plan grouped by shared fixes, waits for one confirmation, then proceeds. It pauses mid-loop if a fix has wide blast radius or a finding is not applicable.
+
+
+
+Claude tracks progress in a markdown report under `.prowler/` at your project root — one file per framework × account. Open it any time to see exactly where the flow is. When all findings are addressed, Claude proposes a fresh Prowler scan to verify everything end-to-end.
+
+## Uninstalling
+
+```text
+/plugin uninstall prowler@prowler-plugins
+/plugin marketplace remove prowler-plugins
+```
+
+The stored API key is removed automatically.
+
+## Troubleshooting
+
+| Symptom | Likely cause | Fix |
+| --- | --- | --- |
+| `/mcp` shows `prowler` as failed | Rejected API key | Generate a new one in Prowler Cloud and reinstall the plugin to re-prompt. |
+| Skill not invoked when expected | The skill description didn't match the prompt | Mention the framework name plus "compliance" or "compliant" in your prompt. |
+| "Framework not supported" | Prowler Hub does not list the framework for that provider | Open an issue or PR at [github.com/prowler-cloud/prowler](https://github.com/prowler-cloud/prowler). |
diff --git a/docs/getting-started/products/prowler-cli.mdx b/docs/getting-started/products/prowler-cli.mdx
index ac4f37c291..fa75e0456e 100644
--- a/docs/getting-started/products/prowler-cli.mdx
+++ b/docs/getting-started/products/prowler-cli.mdx
@@ -9,12 +9,12 @@ prowler
```
-## Prowler Dashboard
+## Prowler Local Dashboard
```console
prowler dashboard
```
-
+
Prowler includes hundreds of security controls aligned with widely recognized industry frameworks and standards, including:
diff --git a/docs/getting-started/products/prowler-cloud-lighthouse.mdx b/docs/getting-started/products/prowler-cloud-lighthouse.mdx
new file mode 100644
index 0000000000..d32118d468
--- /dev/null
+++ b/docs/getting-started/products/prowler-cloud-lighthouse.mdx
@@ -0,0 +1,154 @@
+---
+title: 'Overview'
+---
+
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+Prowler Cloud runs an enhanced version of Lighthouse AI in Open Source repository, the Agentic Cloud Defender that helps teams understand, prioritize, and remediate security findings across cloud environments.
+
+
+
+## What's New
+
+The Agentic Cloud Defender does more than answer questions, it helps teams **find and remediate what actually matters**, cutting through the noise to focus on the risk that counts. Prowler Cloud sharpens Lighthouse AI with the following improvements over the open-source version:
+
+
+
+ Conversations are saved and can be revisited or resumed at any time.
+
+
+ An upgraded default model delivers stronger reasoning and tool calling.
+
+
+ Switch between the standard interface and a chat-first agentic view.
+
+
+ Open Lighthouse AI as a side panel from any page to get help in context.
+
+
+ Credentials are validated automatically when a provider is configured.
+
+
+
+## Chat View
+
+Lighthouse AI is no longer a separate section in the left navigation. Prowler Cloud now offers two application views: a normal view for browsing dashboards, findings, and configuration, and an agentic chat view, powered by Lighthouse AI, for conversational, multi-step security analysis. Conversations are saved automatically, so earlier sessions can be reopened and resumed at any time.
+
+Promoting the chat to a top-level view gives Lighthouse AI the room it needs for a fully agentic workflow and makes the Agentic Cloud Defender a primary way to work in Prowler Cloud.
+
+
+
+### Side Panel
+
+You do not have to switch to the full chat view to reach Lighthouse AI. A side panel is available on every page of Prowler Cloud. While collapsed it stays out of the way; open it from any dashboard, findings list, or configuration screen to ask questions without leaving what you are working on. Open it using the Lighthouse AI button, circled in red in the image below.
+
+
+
+Once open, the panel slides in alongside your current page and shares the same agent, tools, and persistent chat sessions as the full Chat View, so a conversation started in the panel can be reopened and continued later from either place.
+
+
+
+- **Available everywhere:** Summon the assistant from any page while you keep working in the normal view.
+- **Context-aware help:** Ask about the findings, resources, or compliance data you are currently looking at.
+- **Continuous sessions:** Conversations opened in the side panel are saved alongside the rest of your chat history.
+
+### Tool Usage
+
+Lighthouse AI on Prowler Cloud renders the agent's work as it happens, so responses are easier to follow and to trust. Tool calls and reasoning steps appear in the order they occur within the conversation.
+
+- **Ordered steps:** Tool calls and reasoning are shown in sequence, reflecting how the agent reached its answer.
+- **Tool visibility:** The data tools invoked to retrieve findings and other Prowler information are displayed as the agent uses them.
+- **Thought process:** The agent's reasoning is presented alongside its actions, and can be expanded to review the full chain of steps.
+
+
+
+## Configuration
+
+Configure Lighthouse AI on Prowler Cloud from **Configuration** → **Lighthouse AI**:
+
+1. Click the desired provider (OpenAI, Amazon Bedrock, or OpenAI Compatible).
+2. Enter the required credentials.
+3. Click **Save**. The connection is validated automatically before the provider becomes available.
+
+
+
+### Business Context
+
+At the top of the configuration page, the optional **Business Context** field lets teams add environment priorities, compliance requirements, and ownership details, so responses align with organizational needs.
+
+Lighthouse AI on Prowler Cloud supports OpenAI, Amazon Bedrock, and OpenAI-compatible providers, with GPT-5.5 as the default. For per-provider setup and how to switch the default provider or model, see [Using Multiple LLM Providers](/user-guide/tutorials/prowler-cloud-lighthouse-multi-llm).
+
+## Capabilities
+
+Lighthouse AI works through the [Prowler MCP Server](/getting-started/products/prowler-mcp), which gives the agent a growing catalog of tools to explore and act on your security data. These actions run inside Prowler and never modify your cloud resources. Everything the agent can do maps to one of the following capability areas.
+
+### Findings and Finding Groups
+
+- Search and filter security findings across every connected provider by severity, status, region, service, check, date range, and muted state.
+- Retrieve full finding details, including remediation guidance, check metadata, and affected resources.
+- Summarize findings with aggregate statistics and trends.
+- Browse finding groups aggregated by check and drill down into the specific resources each group affects.
+
+### Resources
+
+- List and filter cloud resources by provider, region, service, resource type, and tags.
+- Inspect a resource's configuration, metadata, and related findings.
+- Review the timeline of cloud API actions performed on a resource (AWS CloudTrail), including who did what and when.
+- Get an aggregate overview of the resources Prowler has discovered.
+
+### Compliance
+
+- Review high-level compliance status across all frameworks, with pass/fail statistics per framework.
+- Get a requirement-level breakdown for a specific framework, including failed requirements and their associated findings.
+
+### Attack Paths
+
+- List Attack Paths scans and discover the queries available for each completed scan.
+- Run graph-based queries to reveal privilege-escalation chains and exploitable misconfigurations.
+- Retrieve the Cartography graph schema to build accurate custom queries.
+
+### Scans and Providers
+
+- List, inspect, and rename security scans across providers.
+- Trigger manual scans and schedule automated daily scans for continuous monitoring.
+- Search connected providers and check their connection status, connect new providers, or remove existing ones.
+
+### Muting
+
+- Manage the mutelist for pattern-based bulk muting.
+- Create, update, list, and delete finding-specific mute rules, each with a documented reason and audit trail.
+
+### Security Check Catalog and Documentation
+
+- Browse and search the Prowler Hub catalog of security checks and compliance frameworks, including check code and automated fixers.
+- Search and retrieve official Prowler documentation to answer how-to and product questions.
+
+For the complete list of underlying tools, see the [Prowler MCP Tools Reference](/getting-started/basic-usage/prowler-mcp-tools).
+
+## FAQ
+
+**Which LLM providers are supported?**
+
+OpenAI (GPT models, including the default GPT-5.5), Amazon Bedrock (Claude, Llama, Titan, and others), and any OpenAI-compatible service such as OpenRouter.
+
+**Can Lighthouse AI change my cloud environment?**
+
+No. Lighthouse AI cannot modify the resources in your connected cloud providers (AWS, Azure, GCP, and others). It has read-only access to that environment and no tools to change it, even when the connected cloud credentials would allow it.
+
+**Can Lighthouse AI change my Prowler Cloud environment?**
+
+Yes. Lighthouse AI can take action within Prowler Cloud itself, such as connecting or removing providers, triggering and scheduling scans, and managing mute rules and the mutelist. See [Capabilities](#capabilities) for the full list of what it can do. These actions only affect your Prowler Cloud workspace, never the resources in your cloud providers.
+
+## Looking for the Open Source Version?
+
+Lighthouse AI is also available in the open-source Prowler Local Server. For its capabilities, FAQs, and limitations, see the open-source documentation.
+
+
+ Capabilities, FAQs, and limitations for Lighthouse AI in the open-source Prowler Local Server
+
+
+## Getting Help
+
+For issues or suggestions with Lighthouse AI on Prowler Cloud, request support at [support.prowler.com](https://support.prowler.com) or [reach out through our Slack channel](https://goto.prowler.com/slack).
diff --git a/docs/getting-started/products/prowler-lighthouse-ai.mdx b/docs/getting-started/products/prowler-lighthouse-ai.mdx
index 4e2eed8538..6cb6edf502 100644
--- a/docs/getting-started/products/prowler-lighthouse-ai.mdx
+++ b/docs/getting-started/products/prowler-lighthouse-ai.mdx
@@ -8,11 +8,16 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
Prowler Lighthouse AI is a Cloud Security Analyst chatbot that helps you understand, prioritize, and remediate security findings in your cloud environments. It's designed to provide security expertise for teams without dedicated resources, acting as your 24/7 virtual cloud security analyst.
-
+
-
- Learn how to configure Lighthouse AI with your preferred LLM provider
-
+
+
+ Discover the enhanced Cloud experience: persistent chat sessions, GPT-5.5 by default, a dedicated agentic view, and transparent reasoning
+
+
+ Learn how to configure Lighthouse AI with your preferred LLM provider
+
+
## Capabilities
@@ -26,7 +31,7 @@ Ask questions in plain English about your security findings. Examples:
- "Show me all S3 buckets with public access."
- "What security issues were found in my production accounts?"
-
+
### Detailed Remediation Guidance
@@ -36,7 +41,7 @@ Get tailored step-by-step instructions for fixing security issues:
- Commands or console steps to implement fixes
- Alternative approaches with different solutions
-
+
### Enhanced Context and Analysis
@@ -46,9 +51,9 @@ Lighthouse AI can provide additional context to help you understand the findings
- Provide risk assessments based on your environment and context
- Connect related findings to show broader security patterns
-
+
-
+
## Important Notes
diff --git a/docs/getting-started/products/prowler-mcp.mdx b/docs/getting-started/products/prowler-mcp.mdx
index 762b088326..93159b2e7d 100644
--- a/docs/getting-started/products/prowler-mcp.mdx
+++ b/docs/getting-started/products/prowler-mcp.mdx
@@ -8,6 +8,31 @@ title: "Overview"
**Preview Feature**: This MCP server is currently under active development. Features and functionality may change. We welcome your feedback—please report any issues on [GitHub](https://github.com/prowler-cloud/prowler/issues) or join our [Slack community](https://goto.prowler.com/slack) to discuss and share your thoughts.
+## Quickest Way to Connect: Cloud MCP Server
+
+The fastest way to get started is the **Cloud MCP Server** at `https://mcp.prowler.com/mcp` — no installation, always up to date, and maintained by Prowler. Just point your MCP client at the URL and authenticate with a [Prowler API key](/user-guide/tutorials/prowler-app-api-keys) as a Bearer token:
+
+```json
+{
+ "mcpServers": {
+ "prowler": {
+ "url": "https://mcp.prowler.com/mcp",
+ "headers": {
+ "Authorization": "Bearer "
+ }
+ }
+ }
+}
+```
+
+
+ Step-by-step setup for Claude Desktop, Claude Code, Cursor, and other clients.
+
+
+
+Prefer to run it yourself? The **Local MCP Server** runs on your own machine or infrastructure. The Cloud MCP Server additionally provides tools for Prowler Cloud-specific features such as [Alerts](/user-guide/tutorials/prowler-alerts), [Scan Scheduling](/user-guide/tutorials/prowler-scan-scheduling), and [Findings Triage](/user-guide/tutorials/prowler-app-findings-triage). See [Cloud vs Local MCP Server](#cloud-vs-local-mcp-server).
+
+
## What is the Model Context Protocol?
The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) is an open standard developed by Anthropic that enables AI assistants to securely connect to external data sources and tools. It functions as a universal adapter enabling AI assistants to interact with various services through a standardized interface.
@@ -16,9 +41,9 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) is an open s
The Prowler MCP Server provides three main integration points:
-### 1. Prowler Cloud and Prowler App (Self-Managed)
+### 1. Prowler Cloud, Private Cloud & Local Server
-Full access to Prowler Cloud platform and self-managed Prowler App for:
+Full access to your Prowler deployment — Prowler Cloud, Prowler Private Cloud, or Prowler Local Server — for:
- **Findings Analysis**: Query, filter, and analyze security findings across all your cloud environments
- **Provider Management**: Create, configure, and manage your configured Prowler providers (AWS, Azure, GCP, etc.)
- **Scan Orchestration**: Trigger on-demand scans and schedule recurring security assessments
@@ -29,7 +54,7 @@ Full access to Prowler Cloud platform and self-managed Prowler App for:
### 2. Prowler Hub
Access to Prowler's comprehensive security knowledge base:
-- **Security Checks Catalog**: Browse and search **over 1000 security checks** across multiple cloud providers.
+- **Security Checks Catalog**: Browse and search **over 2,000 security checks** across multiple cloud providers.
- **Check Implementation**: View the Python code that powers each security check.
- **Automated Fixers**: Access remediation scripts for common security issues.
- **Compliance Frameworks**: Explore mappings to **over 70 compliance standards and frameworks**.
@@ -44,12 +69,53 @@ Search and retrieve official Prowler documentation:
## MCP Server Architecture
-The following diagram illustrates the Prowler MCP Server architecture and its integration points:
+The following diagram illustrates the Prowler MCP Server architecture and its integration points. MCP clients connect to either the **Cloud MCP Server** (recommended) or a **Local MCP Server**; both expose the same tools and reach the same Prowler backends:
-
+```mermaid
+flowchart LR
+ subgraph HOSTS["MCP Clients"]
+ chat["Chat Interfaces
(Claude Desktop, LobeChat)"]
+ ide["IDEs and Code Editors
(Claude Code, Cursor)"]
+ apps["Other AI Applications
(5ire, custom agents)"]
+ end
+
+ subgraph SERVERS["Prowler MCP Server"]
+ direction TB
+ cloud["☁️ Cloud MCP Server (Recommended)
mcp.prowler.com/mcp · HTTP
Managed by Prowler · always up to date
Adds Cloud-only tools (Alerts,
Scan Scheduling, Findings Triage)"]
+ local["💻 Local MCP Server
Self-run · STDIO or HTTP
Python 3.12+ or Docker
You manage updates"]
+ end
+
+ subgraph TOOLS["Prowler MCP Tools"]
+ prowler_tools["prowler_* tools
(API key or JWT auth)
Findings · Providers · Scans
Resources · Muting · Compliance
Attack Paths"]
+ hub_tools["prowler_hub_* tools
(no auth)
Checks Catalog · Check Code
Fixers · Compliance Frameworks"]
+ docs_tools["prowler_docs_* tools
(no auth)
Search · Document Retrieval"]
+ end
+
+ api["Prowler API (REST)
Cloud · Private Cloud · Local Server"]
+ hub["hub.prowler.com
(REST)"]
+ docs["docs.prowler.com
(Mintlify)"]
+
+ chat -->|HTTP| cloud
+ ide -->|HTTP| cloud
+ apps -->|HTTP| cloud
+ chat -->|STDIO or HTTP| local
+ ide -->|STDIO or HTTP| local
+ apps -->|STDIO or HTTP| local
+
+ cloud --> prowler_tools
+ cloud --> hub_tools
+ cloud --> docs_tools
+ local --> prowler_tools
+ local --> hub_tools
+ local --> docs_tools
+
+ prowler_tools -->|REST| api
+ hub_tools -->|REST| hub
+ docs_tools -->|REST| docs
+```
The architecture shows how AI assistants connect through the MCP protocol to access Prowler's three main components:
-- Prowler Cloud/App for security operations
+- Prowler Cloud, Prowler Private Cloud, or Prowler Local Server for security operations
- Prowler Hub for security knowledge
- Prowler Documentation for guidance and reference.
@@ -88,8 +154,8 @@ REQUIREMENTS:
DATA TO FETCH:
Use these MCP tools in this order:
-1. Prowler app list providers - To get all available configured provider in the account
-2. Prowler app get latest findings - To get findings information, if there are so many you can use the filter_fields to get less information, or pagination to get in different batches
+1. Prowler list providers - To get all available configured provider in the account
+2. Prowler get latest findings - To get findings information, if there are so many you can use the filter_fields to get less information, or pagination to get in different batches
3. For most critical findings you can get more context and remediation with Prowler Hub to get remediations for example
DESIGN REQUIREMENTS:
@@ -126,65 +192,48 @@ Generate the complete HTML file and display it
>
-## Deployment Options
+## Cloud vs Local MCP Server
-Prowler MCP Server can be used in three ways:
+There are two ways to run the Prowler MCP Server. For almost everyone, the **Cloud MCP Server** is the right choice — it needs no installation and is maintained by Prowler. The **Local MCP Server** exists for users who need to run it on their own machine or infrastructure.
-### 1. Prowler Cloud MCP Server
+| | ☁️ **Cloud MCP Server** (Recommended) | 💻 **Local MCP Server** |
+|---|---|---|
+| **Endpoint** | `https://mcp.prowler.com/mcp` | Runs on your machine or infrastructure |
+| **Setup** | Just configure your MCP client | Install via Docker, or source |
+| **Transport** | HTTP | STDIO (subprocess) or self-hosted HTTP |
+| **Maintenance** | Managed by Prowler, always up to date | You manage updates |
+| **Requirements** | None (just an MCP client) | Python 3.12+ or Docker |
+| **Cloud-only tools** | ✅ Alerts, Scan Scheduling, Findings Triage | ❌ Not available |
+| **Authentication** | API key or JWT token | API key/JWT (HTTP) or env vars (STDIO) |
-**Use Prowler's managed MCP server at `https://mcp.prowler.com/mcp`**
+### ☁️ Cloud MCP Server (Recommended)
-- No installation required.
-- Managed and maintained by Prowler team.
-- Authentication to Prowler Cloud or Prowler App (self-managed) via API key or JWT token.
+Prowler's managed MCP server at `https://mcp.prowler.com/mcp`. No installation, always up to date, and it includes tools for Prowler Cloud-specific features such as Alerts, Scan Scheduling, and Findings Triage. This is the path we recommend for nearly all users — go straight to the [Configuration guide](/getting-started/basic-usage/prowler-mcp#cloud-mcp-server-configuration-recommended).
-### 2. Local STDIO Mode
+### 💻 Local MCP Server
-**Run the server locally on your machine**
+Run the server yourself when you need full control over the deployment. It connects to Prowler Cloud, Prowler Private Cloud, or Prowler Local Server and can run in two modes:
-- Runs as a subprocess of your MCP client.
-- Possibility to connect to a self-hosted Prowler App (e.g. self-hosted Prowler App).
-- Authentication to Prowler Cloud or Prowler App (self-managed) via environment variables.
-- Requires Python 3.12+ or Docker.
+- **STDIO mode** — the server runs as a subprocess of your MCP client. Authentication via environment variables.
+- **Self-hosted HTTP mode** — deploy your own remote HTTP server. Authentication via API key or JWT token.
-### 3. Self-Hosted HTTP Mode
-
-**Deploy your own remote MCP server**
-
-- Full control over deployment.
-- Possibility to connect to a self-hosted Prowler App (e.g. self-hosted Prowler App).
-- Authentication to Prowler App (self-managed) via API key or JWT token.
-- Requires Python 3.12+ or Docker.
-
-## Requirements
-
-Requirements vary based on deployment option:
-
-**For Prowler Cloud MCP Server:**
-- Prowler Cloud account and API key (only for Prowler Cloud/App features)
-
-**For self-hosted STDIO/HTTP Mode:**
-- Python 3.12+ or Docker
-- Network access to:
- - `https://hub.prowler.com` (for Prowler Hub)
- - `https://docs.prowler.com` (for Prowler Documentation)
- - Prowler Cloud API or self-hosted Prowler App API (for Prowler Cloud/App features)
+Both require Python 3.12+ or Docker, plus network access to `https://hub.prowler.com` (Prowler Hub), `https://docs.prowler.com` (Prowler Documentation), and the Prowler API or Prowler Local Server API (Prowler features). See the [Installation guide](/getting-started/installation/prowler-mcp) to get started.
-**No Authentication Required**: Prowler Hub and Prowler Documentation features work without authentication in both deployment options. A Prowler API key is only required to access Prowler Cloud or Prowler App (Self-Managed) features.
+**No Authentication Required**: Prowler Hub and Prowler Documentation features work without authentication on both the Cloud and Local MCP Server. A Prowler API key is only required to access Prowler features (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server).
## Next Steps
-
- Install the Prowler MCP Server using uv or Docker
-
- Configure your MCP client to connect to the server
+ Connect your MCP client to the Cloud MCP Server
+
+
+ Explore all available tools and capabilities
-
- Explore all available tools and capabilities
+
+ Run the Local MCP Server yourself using Docker, source, or uvx
diff --git a/docs/getting-started/products/prowler-sdk.mdx b/docs/getting-started/products/prowler-sdk.mdx
new file mode 100644
index 0000000000..b19f576e12
--- /dev/null
+++ b/docs/getting-started/products/prowler-sdk.mdx
@@ -0,0 +1,11 @@
+---
+title: 'Prowler SDK'
+---
+
+Prowler SDK is the Python library that powers Prowler CLI and Prowler Local Server. It implements the providers, services, and security checks that every Prowler product runs.
+
+To use or extend Prowler SDK, start with the Developer Guide:
+
+
+ Providers, services, checks, and testing: everything needed to work with Prowler SDK.
+
diff --git a/docs/images/compliance/prowler-app-cross-provider-detail.png b/docs/images/compliance/prowler-app-cross-provider-detail.png
new file mode 100644
index 0000000000..8ee82562e2
Binary files /dev/null and b/docs/images/compliance/prowler-app-cross-provider-detail.png differ
diff --git a/docs/images/compliance/prowler-app-cross-provider-overview.png b/docs/images/compliance/prowler-app-cross-provider-overview.png
new file mode 100644
index 0000000000..d818da1b80
Binary files /dev/null and b/docs/images/compliance/prowler-app-cross-provider-overview.png differ
diff --git a/docs/images/compliance/prowler-app-cross-provider-report.png b/docs/images/compliance/prowler-app-cross-provider-report.png
new file mode 100644
index 0000000000..e3b45ef74e
Binary files /dev/null and b/docs/images/compliance/prowler-app-cross-provider-report.png differ
diff --git a/docs/images/compliance/prowler-app-cross-provider-requirements-accordion.png b/docs/images/compliance/prowler-app-cross-provider-requirements-accordion.png
new file mode 100644
index 0000000000..cd87e3ee35
Binary files /dev/null and b/docs/images/compliance/prowler-app-cross-provider-requirements-accordion.png differ
diff --git a/docs/images/compliance/prowler-app-cross-provider-tab.png b/docs/images/compliance/prowler-app-cross-provider-tab.png
new file mode 100644
index 0000000000..b3aa8ed2b5
Binary files /dev/null and b/docs/images/compliance/prowler-app-cross-provider-tab.png differ
diff --git a/docs/images/icons/cloud-bold.svg b/docs/images/icons/cloud-bold.svg
new file mode 100644
index 0000000000..623bb36c11
--- /dev/null
+++ b/docs/images/icons/cloud-bold.svg
@@ -0,0 +1 @@
+
diff --git a/docs/images/lighthouse-architecture.mmd b/docs/images/lighthouse-architecture.mmd
index 47407544e9..6798801fb8 100644
--- a/docs/images/lighthouse-architecture.mmd
+++ b/docs/images/lighthouse-architecture.mmd
@@ -15,7 +15,7 @@ flowchart TB
llm["LLM Provider
(OpenAI / Bedrock / OpenAI-compatible)"]
subgraph MCP["Prowler MCP Server"]
- app_tools["prowler_app_* tools
(auth required)"]
+ app_tools["prowler_* tools
(auth required)"]
hub_tools["prowler_hub_* tools
(no auth)"]
docs_tools["prowler_docs_* tools
(no auth)"]
end
@@ -29,7 +29,7 @@ flowchart TB
agent <-->|LLM API| llm
agent --> metatools
metatools --> mcpclient
- mcpclient -->|MCP HTTP · Bearer token
for prowler_app_* only| app_tools
+ mcpclient -->|MCP HTTP · Bearer token
for prowler_* only| app_tools
mcpclient -->|MCP HTTP| hub_tools
mcpclient -->|MCP HTTP| docs_tools
app_tools -->|REST| api
diff --git a/docs/images/organizations/authentication-details.png b/docs/images/organizations/authentication-details.png
index 2b4ae782cf..aec5060afd 100644
Binary files a/docs/images/organizations/authentication-details.png and b/docs/images/organizations/authentication-details.png differ
diff --git a/docs/images/organizations/onboarding-flow.svg b/docs/images/organizations/onboarding-flow.svg
index f6e11fc0a3..b5ba7858a0 100644
--- a/docs/images/organizations/onboarding-flow.svg
+++ b/docs/images/organizations/onboarding-flow.svg
@@ -3,41 +3,37 @@
+
+
Onboarding Flow
- 1
- Create Management
- Account Role
- Quick Create or Manual
- Allows Prowler to
- discover your org
- structure
+ Start the Wizard
+ In Prowler Cloud
+ Enter your Org ID
+ and OU/root target
-
-
-
2
- Deploy StackSet
- In AWS Console
- Creates ProwlerScan
- role in every
- member account
+ Deploy the Roles
+ Single CF Stack
+ Management role +
+ StackSet to members
+ in one CF stack
3
- Run the Wizard
- In Prowler Cloud
- Discovers accounts,
- tests connections
+ Discover & Connect
+ In Prowler Cloud
+ Discovers accounts,
+ tests connections
4
- Launch Scans
- Automatic
- Scans run on all
- connected accounts
- on your schedule
+ Launch Scans
+ Automatic
+ Scans run on all
+ connected accounts
+ on your schedule
- Steps 1 and 2 are done once in AWS | Steps 3 and 4 are done in Prowler Cloud
+ Step 2 runs once in AWS | Steps 1, 3 and 4 are in Prowler Cloud
diff --git a/docs/images/organizations/two-roles-architecture.svg b/docs/images/organizations/two-roles-architecture.svg
index c67588b049..f8c40d5b21 100644
--- a/docs/images/organizations/two-roles-architecture.svg
+++ b/docs/images/organizations/two-roles-architecture.svg
@@ -47,7 +47,7 @@
Deploy: Quick Create link or Manual
+ Deploy: single stack or standalone
Deploy: via CloudFormation StackSet
+ Deploy: StackSet (single stack)
Prowler discovers
diff --git a/docs/images/products/prowler-app-architecture.mmd b/docs/images/products/prowler-app-architecture.mmd
index 0c13d580c3..da99d0ab96 100644
--- a/docs/images/products/prowler-app-architecture.mmd
+++ b/docs/images/products/prowler-app-architecture.mmd
@@ -1,8 +1,10 @@
+%% Source of truth for the architecture diagram.
+%% Inlined as native mermaid blocks in the root README.md and in docs/getting-started/products/prowler-app.mdx: keep all copies in sync.
flowchart TB
user([User / Security Team])
cli([Prowler CLI])
- subgraph APP["Prowler App"]
+ subgraph APP["Prowler Local Server"]
ui["Prowler UI
(Next.js)"]
api["Prowler API
(Django REST Framework)"]
worker["API Worker
(Celery)"]
diff --git a/docs/images/prowler-app/attack-paths/execute-query.png b/docs/images/prowler-app/attack-paths/execute-query.png
index 3872f0de2f..683c7c5bd3 100644
Binary files a/docs/images/prowler-app/attack-paths/execute-query.png and b/docs/images/prowler-app/attack-paths/execute-query.png differ
diff --git a/docs/images/prowler-app/attack-paths/fullscreen-mode.png b/docs/images/prowler-app/attack-paths/fullscreen-mode.png
index c5156925ba..190d973638 100644
Binary files a/docs/images/prowler-app/attack-paths/fullscreen-mode.png and b/docs/images/prowler-app/attack-paths/fullscreen-mode.png differ
diff --git a/docs/images/prowler-app/attack-paths/graph-filtered.png b/docs/images/prowler-app/attack-paths/graph-filtered.png
index 3ff4822a26..3eddf04473 100644
Binary files a/docs/images/prowler-app/attack-paths/graph-filtered.png and b/docs/images/prowler-app/attack-paths/graph-filtered.png differ
diff --git a/docs/images/prowler-app/attack-paths/graph-visualization.png b/docs/images/prowler-app/attack-paths/graph-visualization.png
index 2ea160a6b2..d7f2a747eb 100644
Binary files a/docs/images/prowler-app/attack-paths/graph-visualization.png and b/docs/images/prowler-app/attack-paths/graph-visualization.png differ
diff --git a/docs/images/prowler-app/attack-paths/navigation.png b/docs/images/prowler-app/attack-paths/navigation.png
index d133c7f6b4..0526e05e5c 100644
Binary files a/docs/images/prowler-app/attack-paths/navigation.png and b/docs/images/prowler-app/attack-paths/navigation.png differ
diff --git a/docs/images/prowler-app/attack-paths/node-details.png b/docs/images/prowler-app/attack-paths/node-details.png
index 9343eedd7d..8b02128604 100644
Binary files a/docs/images/prowler-app/attack-paths/node-details.png and b/docs/images/prowler-app/attack-paths/node-details.png differ
diff --git a/docs/images/prowler-app/attack-paths/query-parameters.png b/docs/images/prowler-app/attack-paths/query-parameters.png
index 9f44f81838..683c7c5bd3 100644
Binary files a/docs/images/prowler-app/attack-paths/query-parameters.png and b/docs/images/prowler-app/attack-paths/query-parameters.png differ
diff --git a/docs/images/prowler-app/attack-paths/query-selector.png b/docs/images/prowler-app/attack-paths/query-selector.png
index d8b7414156..828183fdbf 100644
Binary files a/docs/images/prowler-app/attack-paths/query-selector.png and b/docs/images/prowler-app/attack-paths/query-selector.png differ
diff --git a/docs/images/prowler-app/attack-paths/scan-list-table.png b/docs/images/prowler-app/attack-paths/scan-list-table.png
index 092b539dd0..45d0af41dc 100644
Binary files a/docs/images/prowler-app/attack-paths/scan-list-table.png and b/docs/images/prowler-app/attack-paths/scan-list-table.png differ
diff --git a/docs/images/prowler-app/findings-triage/findings-triage-note-modal.png b/docs/images/prowler-app/findings-triage/findings-triage-note-modal.png
new file mode 100644
index 0000000000..9d7926997d
Binary files /dev/null and b/docs/images/prowler-app/findings-triage/findings-triage-note-modal.png differ
diff --git a/docs/images/prowler-app/findings-triage/findings-triage-status-dropdown.png b/docs/images/prowler-app/findings-triage/findings-triage-status-dropdown.png
new file mode 100644
index 0000000000..7fb7790610
Binary files /dev/null and b/docs/images/prowler-app/findings-triage/findings-triage-status-dropdown.png differ
diff --git a/docs/images/prowler-app/findings-triage/findings-triage-table.png b/docs/images/prowler-app/findings-triage/findings-triage-table.png
new file mode 100644
index 0000000000..c8fa79e379
Binary files /dev/null and b/docs/images/prowler-app/findings-triage/findings-triage-table.png differ
diff --git a/docs/images/prowler-app/lighthouse-config.png b/docs/images/prowler-app/lighthouse/oss/config.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-config.png
rename to docs/images/prowler-app/lighthouse/oss/config.png
diff --git a/docs/images/prowler-app/lighthouse-configuration.png b/docs/images/prowler-app/lighthouse/oss/configuration.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-configuration.png
rename to docs/images/prowler-app/lighthouse/oss/configuration.png
diff --git a/docs/images/prowler-app/lighthouse-feature1.png b/docs/images/prowler-app/lighthouse/oss/feature1.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-feature1.png
rename to docs/images/prowler-app/lighthouse/oss/feature1.png
diff --git a/docs/images/prowler-app/lighthouse-feature2.png b/docs/images/prowler-app/lighthouse/oss/feature2.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-feature2.png
rename to docs/images/prowler-app/lighthouse/oss/feature2.png
diff --git a/docs/images/prowler-app/lighthouse-feature3.png b/docs/images/prowler-app/lighthouse/oss/feature3.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-feature3.png
rename to docs/images/prowler-app/lighthouse/oss/feature3.png
diff --git a/docs/images/prowler-app/lighthouse-intro.png b/docs/images/prowler-app/lighthouse/oss/intro.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-intro.png
rename to docs/images/prowler-app/lighthouse/oss/intro.png
diff --git a/docs/images/prowler-app/lighthouse-set-default-provider.png b/docs/images/prowler-app/lighthouse/oss/set-default-provider.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-set-default-provider.png
rename to docs/images/prowler-app/lighthouse/oss/set-default-provider.png
diff --git a/docs/images/prowler-app/lighthouse-switch-models.png b/docs/images/prowler-app/lighthouse/oss/switch-models.png
similarity index 100%
rename from docs/images/prowler-app/lighthouse-switch-models.png
rename to docs/images/prowler-app/lighthouse/oss/switch-models.png
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/chat-animation.gif b/docs/images/prowler-app/lighthouse/prowler-cloud/chat-animation.gif
new file mode 100644
index 0000000000..c2e69c4816
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/chat-animation.gif differ
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/config-page.png b/docs/images/prowler-app/lighthouse/prowler-cloud/config-page.png
new file mode 100644
index 0000000000..ad1b812e03
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/config-page.png differ
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/main-chat-page.png b/docs/images/prowler-app/lighthouse/prowler-cloud/main-chat-page.png
new file mode 100644
index 0000000000..7a83637285
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/main-chat-page.png differ
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-closed.png b/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-closed.png
new file mode 100644
index 0000000000..c36da34a95
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-closed.png differ
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-open.png b/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-open.png
new file mode 100644
index 0000000000..fd10f5a00b
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/side-panel-open.png differ
diff --git a/docs/images/prowler-app/lighthouse/prowler-cloud/tool-usage.png b/docs/images/prowler-app/lighthouse/prowler-cloud/tool-usage.png
new file mode 100644
index 0000000000..ae637b3ff3
Binary files /dev/null and b/docs/images/prowler-app/lighthouse/prowler-cloud/tool-usage.png differ
diff --git a/docs/images/prowler-app/rbac/provider_group.png b/docs/images/prowler-app/rbac/provider_group.png
index 878306e02f..8698cc9c41 100644
Binary files a/docs/images/prowler-app/rbac/provider_group.png and b/docs/images/prowler-app/rbac/provider_group.png differ
diff --git a/docs/images/prowler-app/rbac/provider_group_edit.png b/docs/images/prowler-app/rbac/provider_group_edit.png
index 5de9649578..3d37b329b7 100644
Binary files a/docs/images/prowler-app/rbac/provider_group_edit.png and b/docs/images/prowler-app/rbac/provider_group_edit.png differ
diff --git a/docs/images/prowler-app/rbac/provider_group_edit_1.png b/docs/images/prowler-app/rbac/provider_group_edit_1.png
index ed4a090eed..4369983a20 100644
Binary files a/docs/images/prowler-app/rbac/provider_group_edit_1.png and b/docs/images/prowler-app/rbac/provider_group_edit_1.png differ
diff --git a/docs/images/prowler-app/rbac/provider_group_remove.png b/docs/images/prowler-app/rbac/provider_group_remove.png
index 580a8533cf..f504617159 100644
Binary files a/docs/images/prowler-app/rbac/provider_group_remove.png and b/docs/images/prowler-app/rbac/provider_group_remove.png differ
diff --git a/docs/images/prowler-app/rbac/role_create_1.png b/docs/images/prowler-app/rbac/role_create_1.png
index a96b0ac9ef..b88fe990db 100644
Binary files a/docs/images/prowler-app/rbac/role_create_1.png and b/docs/images/prowler-app/rbac/role_create_1.png differ
diff --git a/docs/images/prowler-app/scan-scheduling/edit-scan-schedule.png b/docs/images/prowler-app/scan-scheduling/edit-scan-schedule.png
new file mode 100644
index 0000000000..e76809b810
Binary files /dev/null and b/docs/images/prowler-app/scan-scheduling/edit-scan-schedule.png differ
diff --git a/docs/images/prowler-app/scan-scheduling/launch-scan-schedule.png b/docs/images/prowler-app/scan-scheduling/launch-scan-schedule.png
new file mode 100644
index 0000000000..980b16bf7f
Binary files /dev/null and b/docs/images/prowler-app/scan-scheduling/launch-scan-schedule.png differ
diff --git a/docs/images/prowler-app/scan-scheduling/providers-scan-schedule.png b/docs/images/prowler-app/scan-scheduling/providers-scan-schedule.png
new file mode 100644
index 0000000000..a7dab3310c
Binary files /dev/null and b/docs/images/prowler-app/scan-scheduling/providers-scan-schedule.png differ
diff --git a/docs/images/prowler-app/scan-scheduling/scheduled-scans-tab.png b/docs/images/prowler-app/scan-scheduling/scheduled-scans-tab.png
new file mode 100644
index 0000000000..26b4b160ec
Binary files /dev/null and b/docs/images/prowler-app/scan-scheduling/scheduled-scans-tab.png differ
diff --git a/docs/images/prowler_mcp_schema.mmd b/docs/images/prowler_mcp_schema.mmd
index 96973546f6..2b8508cd18 100644
--- a/docs/images/prowler_mcp_schema.mmd
+++ b/docs/images/prowler_mcp_schema.mmd
@@ -1,29 +1,40 @@
flowchart LR
- subgraph HOSTS["MCP Hosts"]
+ subgraph HOSTS["MCP Clients"]
chat["Chat Interfaces
(Claude Desktop, LobeChat)"]
ide["IDEs and Code Editors
(Claude Code, Cursor)"]
apps["Other AI Applications
(5ire, custom agents)"]
end
- subgraph MCP["Prowler MCP Server"]
- app_tools["prowler_app_* tools
(JWT or API key auth)
Findings · Providers · Scans
Resources · Muting · Compliance
Attack Paths"]
+ subgraph SERVERS["Prowler MCP Server"]
+ direction TB
+ cloud["☁️ Cloud MCP Server (Recommended)
mcp.prowler.com/mcp · HTTP
Managed by Prowler · always up to date
Adds Cloud-only tools (Alerts,
Scan Scheduling, Findings Triage)"]
+ local["💻 Local MCP Server
Self-run · STDIO or HTTP
Python 3.12+ or Docker
You manage updates"]
+ end
+
+ subgraph TOOLS["Prowler MCP Tools"]
+ prowler_tools["prowler_* tools
(API key or JWT auth)
Findings · Providers · Scans
Resources · Muting · Compliance
Attack Paths"]
hub_tools["prowler_hub_* tools
(no auth)
Checks Catalog · Check Code
Fixers · Compliance Frameworks"]
docs_tools["prowler_docs_* tools
(no auth)
Search · Document Retrieval"]
end
- api["Prowler API
(REST)"]
+ api["Prowler API (REST)
Cloud · Private Cloud · Local Server"]
hub["hub.prowler.com
(REST)"]
docs["docs.prowler.com
(Mintlify)"]
- chat -->|STDIO or HTTP| app_tools
- chat -->|STDIO or HTTP| hub_tools
- chat -->|STDIO or HTTP| docs_tools
- ide -->|STDIO or HTTP| app_tools
- ide -->|STDIO or HTTP| hub_tools
- ide -->|STDIO or HTTP| docs_tools
- apps -->|STDIO or HTTP| app_tools
- apps -->|STDIO or HTTP| hub_tools
- apps -->|STDIO or HTTP| docs_tools
- app_tools -->|REST| api
+ chat -->|HTTP| cloud
+ ide -->|HTTP| cloud
+ apps -->|HTTP| cloud
+ chat -->|STDIO or HTTP| local
+ ide -->|STDIO or HTTP| local
+ apps -->|STDIO or HTTP| local
+
+ cloud --> prowler_tools
+ cloud --> hub_tools
+ cloud --> docs_tools
+ local --> prowler_tools
+ local --> hub_tools
+ local --> docs_tools
+
+ prowler_tools -->|REST| api
hub_tools -->|REST| hub
docs_tools -->|REST| docs
diff --git a/docs/images/prowler_mcp_schema.png b/docs/images/prowler_mcp_schema.png
deleted file mode 100644
index 8a8884fa5e..0000000000
Binary files a/docs/images/prowler_mcp_schema.png and /dev/null differ
diff --git a/docs/introduction.mdx b/docs/introduction.mdx
index c8dc5c649e..9307fa351a 100644
--- a/docs/introduction.mdx
+++ b/docs/introduction.mdx
@@ -1,21 +1,36 @@
# What is Prowler?
-**Prowler** is the world’s most widely used open-source cloud security platform that **automates security and compliance** across any cloud environment. With hundreds of ready-to-use security checks, remediation guidance, and compliance frameworks, Prowler delivers AI-driven, customizable, and easy-to-use monitoring and integrations, making cloud security simple, scalable, and cost-effective for organizations of any size.
+**Prowler** is the world’s most widely used open-source cloud security platform that **automates security and compliance** across any cloud environment. With thousands of ready-to-use security checks, remediation guidance, and compliance frameworks, Prowler delivers AI-driven, customizable, and easy-to-use monitoring and integrations, making cloud security simple, scalable, and cost-effective for organizations of any size.
+Prowler ships two product families: Prowler Products, operated or licensed by the Prowler team, and Open Source projects, free to run and extend. See [Prowler product families](/getting-started/products) for every official name, including former names.
+
+### Prowler Products
+
-
- Command Line Interface
-
-
- Web Application
-
-
- A managed service built on top of Prowler App.
+
+ Managed cloud security platform operated by the Prowler team.
- A public library of versioned checks, cloud service artifacts, and compliance frameworks.
+ Free public library of versioned checks, cloud service artifacts, and compliance frameworks.
+
+
+ MCP server that connects AI assistants and agents to Prowler.
+
+
+ Prowler Private Cloud, Prowler Lighthouse AI, and more.
+
+
+
+### Open Source
+
+
+
+ Command line tool to run security scans across all supported providers.
+
+
+ Self-hosted web application and API.
@@ -31,11 +46,14 @@ Prowler supports a wide range of providers organized by category:
| [AWS](/user-guide/providers/aws/getting-started-aws) | Official | Accounts | UI, API, CLI |
| [Azure](/user-guide/providers/azure/getting-started-azure) | Official | Subscriptions | UI, API, CLI |
| [Cloudflare](/user-guide/providers/cloudflare/getting-started-cloudflare) | Official | Accounts | UI, API, CLI |
+| [E2E Networks](/user-guide/providers/e2enetworks/getting-started-e2enetworks) | [Contact us](https://prowler.com/contact) | Projects | CLI |
| [Google Cloud](/user-guide/providers/gcp/getting-started-gcp) | Official | Projects | UI, API, CLI |
-| **NHN** | Unofficial | Tenants | CLI |
+| [Linode](/user-guide/providers/linode/getting-started-linode) | [Contact us](https://prowler.com/contact) | Accounts | CLI |
+| **NHN** | [Contact us](https://prowler.com/contact) | Tenants | CLI |
| [OpenStack](/user-guide/providers/openstack/getting-started-openstack) | Official | Projects | UI, API, CLI |
| [Oracle Cloud](/user-guide/providers/oci/getting-started-oci) | Official | Tenancies / Compartments | UI, API, CLI |
-| [Scaleway](/user-guide/providers/scaleway/getting-started-scaleway) [Contact us](https://prowler.com/contact) | Unofficial | Organizations | CLI |
+| [Scaleway](/user-guide/providers/scaleway/getting-started-scaleway) | [Contact us](https://prowler.com/contact) | Organizations | CLI |
+| [StackIT](/user-guide/providers/stackit/getting-started-stackit) | [Contact us](https://prowler.com/contact) | Projects | CLI |
### Infrastructure as Code Providers
@@ -67,7 +85,7 @@ Prowler supports a wide range of providers organized by category:
| ------------------------------------------------------------------- | -------- | -------------------- | --------- |
| [Image](/user-guide/providers/image/getting-started-image) | Official | Container Images / Registries | CLI, API |
-### Custom Providers (Prowler Cloud Enterprise Only)
+### Custom Providers (Prowler Private Cloud Only)
| Provider | Support | Audit Scope/Entities | Interface |
| -------------------- | -------- | -------------------- | --------- |
diff --git a/docs/scripts/generate_provider_cards.py b/docs/scripts/generate_provider_cards.py
new file mode 100644
index 0000000000..1b35755507
--- /dev/null
+++ b/docs/scripts/generate_provider_cards.py
@@ -0,0 +1,155 @@
+#!/usr/bin/env python3
+"""Generate docs/snippets/provider-cards.mdx from provider getting-started pages.
+
+Scans docs/user-guide/providers//getting-started-*.mdx, keeps only the
+providers that Prowler Cloud and Prowler Local Server actually support (source of truth: the
+`ProviderChoices` enum in api/src/backend/api/models.py — CLI-only providers
+such as Linode/LLM/Scaleway/StackIT are excluded), reads the frontmatter
+`title`, derives a display name, and emits a snippet exporting a
+`ProviderCards` component. Wired into pre-commit so the snippet stays in sync
+whenever a provider page or the API enum changes.
+"""
+
+from __future__ import annotations
+
+import ast
+import re
+import sys
+from pathlib import Path
+
+REPO_ROOT = Path(__file__).resolve().parents[2]
+PROVIDERS_DIR = REPO_ROOT / "docs" / "user-guide" / "providers"
+SNIPPET_PATH = REPO_ROOT / "docs" / "snippets" / "provider-cards.mdx"
+API_MODELS_PATH = REPO_ROOT / "api" / "src" / "backend" / "api" / "models.py"
+
+# Docs folder names that don't match the API enum key. Keep tiny — only rename
+# entries when the docs folder disagrees with the API-side identifier.
+DOCS_DIR_TO_API_KEY = {
+ "microsoft365": "m365",
+ "oci": "oraclecloud",
+}
+
+# Folder-name → Mintlify icon override. Providers not listed fall back to
+# DEFAULT_ICON. Add an entry only when the default looks wrong for a provider.
+ICON_OVERRIDES = {
+ "alibabacloud": "cloud",
+ "aws": "aws",
+ "azure": "microsoft",
+ "cloudflare": "cloudflare",
+ "gcp": "google",
+ "github": "github",
+ "googleworkspace": "users",
+ "iac": "code",
+ "image": "docker",
+ "kubernetes": "dharmachakra",
+ "microsoft365": "briefcase",
+ "mongodbatlas": "leaf",
+ "oci": "database",
+ "okta": "key",
+ "openstack": "cubes",
+ "vercel": "triangle",
+}
+DEFAULT_ICON = "cloud"
+
+TITLE_RE = re.compile(r"^\s*title\s*:\s*['\"](?P.+?)['\"]\s*$", re.MULTILINE)
+NAME_CLEANUP_RE = re.compile(
+ r"^Getting Started [Ww]ith (?:the )?(?P<name>.+?)(?: on Prowler)?(?: Provider)?$"
+)
+
+
+def app_supported_provider_keys() -> set[str]:
+ """Return the set of provider keys declared in the API's ProviderChoices enum.
+
+ Uses ast rather than regex so formatting changes, decorators, comments, or
+ multi-line values in the enum body don't silently drop or invent providers.
+ """
+ tree = ast.parse(API_MODELS_PATH.read_text(encoding="utf-8"))
+ for node in ast.walk(tree):
+ if not (isinstance(node, ast.ClassDef) and node.name == "ProviderChoices"):
+ continue
+ keys: set[str] = set()
+ for item in node.body:
+ if not isinstance(item, ast.Assign):
+ continue
+ value = item.value
+ # Django TextChoices members look like: NAME = "key", _("Label")
+ # which parses as an ast.Tuple whose first element is the key.
+ if isinstance(value, ast.Tuple) and value.elts:
+ first = value.elts[0]
+ if isinstance(first, ast.Constant) and isinstance(first.value, str):
+ keys.add(first.value)
+ return keys
+ raise RuntimeError(
+ f"Could not locate ProviderChoices class in {API_MODELS_PATH.relative_to(REPO_ROOT)}"
+ )
+
+
+def extract_title(mdx_path: Path) -> str:
+ text = mdx_path.read_text(encoding="utf-8")
+ match = TITLE_RE.search(text)
+ if not match:
+ raise ValueError(f"No frontmatter title in {mdx_path}")
+ return match.group("title")
+
+
+def display_name(title: str) -> str:
+ match = NAME_CLEANUP_RE.match(title)
+ return match.group("name") if match else title
+
+
+def collect_providers() -> list[dict]:
+ supported = app_supported_provider_keys()
+ providers = []
+ for provider_dir in sorted(PROVIDERS_DIR.iterdir()):
+ if not provider_dir.is_dir():
+ continue
+ api_key = DOCS_DIR_TO_API_KEY.get(provider_dir.name, provider_dir.name)
+ if api_key not in supported:
+ continue
+ pages = sorted(provider_dir.glob("getting-started-*.mdx"))
+ if not pages:
+ continue
+ page = pages[0]
+ name = display_name(extract_title(page))
+ href = f"/user-guide/providers/{provider_dir.name}/{page.stem}"
+ icon = ICON_OVERRIDES.get(provider_dir.name, DEFAULT_ICON)
+ providers.append({"name": name, "href": href, "icon": icon})
+ providers.sort(key=lambda p: p["name"].lower())
+ return providers
+
+
+def render_snippet(providers: list[dict]) -> str:
+ cards = "\n".join(
+ f' <Card title="{p["name"]}" icon="{p["icon"]}" href="{p["href"]}" />'
+ for p in providers
+ )
+ return (
+ "{/* AUTO-GENERATED by docs/scripts/generate_provider_cards.py — do not edit by hand. */}\n"
+ "{/* Regenerated on pre-commit whenever any provider getting-started page changes. */}\n"
+ "\n"
+ "export const ProviderCards = () => (\n"
+ " <Columns cols={3}>\n"
+ f"{cards}\n"
+ " </Columns>\n"
+ ");\n"
+ )
+
+
+def main() -> int:
+ providers = collect_providers()
+ if not providers:
+ print("No provider getting-started pages found", file=sys.stderr)
+ return 1
+ new_content = render_snippet(providers)
+ current = SNIPPET_PATH.read_text(encoding="utf-8") if SNIPPET_PATH.exists() else ""
+ if new_content == current:
+ return 0
+ SNIPPET_PATH.write_text(new_content, encoding="utf-8")
+ print(
+ f"Regenerated {SNIPPET_PATH.relative_to(REPO_ROOT)} ({len(providers)} providers)"
+ )
+ return 1 # signal pre-commit that the file changed
+
+
+if __name__ == "__main__":
+ sys.exit(main())
diff --git a/docs/security/index.mdx b/docs/security/index.mdx
index 30364d5b82..45b39d608b 100644
--- a/docs/security/index.mdx
+++ b/docs/security/index.mdx
@@ -27,7 +27,7 @@ All Prowler code goes through the same security pipeline, whether running on Pro
| **Updates** | Automatic | Manual |
<Note>
-Self-Managed includes Prowler App and Prowler CLI. They can run anywhere — any cloud provider, any region, on-premises, or air-gapped environments. Full control over data residency and infrastructure decisions. See the [Prowler App Installation Guide](/getting-started/installation/prowler-app) to get started.
+Self-Managed includes Prowler Local Server and Prowler CLI. They can run anywhere — any cloud provider, any region, on-premises, or air-gapped environments. Full control over data residency and infrastructure decisions. See the [Prowler Local Server Installation Guide](/getting-started/installation/prowler-app) to get started.
</Note>
---
diff --git a/docs/security/networking.mdx b/docs/security/networking.mdx
index 767e6ac4bf..eb00c9a840 100644
--- a/docs/security/networking.mdx
+++ b/docs/security/networking.mdx
@@ -16,6 +16,18 @@ Resolve the egress IP via DNS:
dig egress.prowler.com +short
```
+<Note>
+The egress IP address is stable, but it is recommended to periodically verify it remains current by querying `egress.prowler.com`.
+</Note>
+
+## Use Cases
+
+Allowlisting Prowler Cloud's egress IP address enables:
+
+- **Credential Usage Control**: Restrict where cloud provider credentials can be used from across AWS, Azure, GCP, and other providers
+- **Kubernetes Security**: Limit inbound HTTPS traffic to clusters by allowing only Prowler Cloud's IP address
+- **Compliance Requirements**: Meet security policies requiring allowlisting of external services
+
## Contact
For questions about networking, visit the [Support page](/support).
diff --git a/docs/security/software-security.mdx b/docs/security/software-security.mdx
index eb3afc606f..64c2645d3f 100644
--- a/docs/security/software-security.mdx
+++ b/docs/security/software-security.mdx
@@ -101,6 +101,28 @@ Dependencies are scanned against public vulnerability databases on every pull re
- Per-vulnerability ignores live in [`osv-scanner.toml`](https://github.com/prowler-cloud/prowler/blob/master/osv-scanner.toml) at the repo root, each with a reason and an expiry date.
- **Trivy:** scans container images for OS-package and application-dependency vulnerabilities. Runs in [`sdk-container-checks.yml`](https://github.com/prowler-cloud/prowler/blob/master/.github/workflows/sdk-container-checks.yml), [`api-container-checks.yml`](https://github.com/prowler-cloud/prowler/blob/master/.github/workflows/api-container-checks.yml), [`ui-container-checks.yml`](https://github.com/prowler-cloud/prowler/blob/master/.github/workflows/ui-container-checks.yml), and [`mcp-container-checks.yml`](https://github.com/prowler-cloud/prowler/blob/master/.github/workflows/mcp-container-checks.yml). Trivy uploads SARIF to the GitHub Security tab and posts a scan summary on the PR.
- **Dependabot:** [configured](https://github.com/prowler-cloud/prowler/blob/master/.github/dependabot.yml) for monthly updates of the SDK Python dependencies, GitHub Actions, Docker base images, and pre-commit hooks. Dependabot opens pull requests for known security advisories, so critical patches reach the team without delay. A 7-day default cooldown reduces exposure to compromised package releases.
+- **Renovate:** [configured](https://github.com/prowler-cloud/prowler/blob/master/.github/renovate.json) dependency update automation is transitioning from Dependabot to **Renovate** to gain finer control over update cadence, grouping, and per-component scope. Both tools currently run in parallel during the migration.
+
+#### Renovate (Primary)
+
+Configuration: [`.github/renovate.json`](https://github.com/prowler-cloud/prowler/blob/master/.github/renovate.json)
+
+- **Coverage:** Python (SDK, API, MCP Server), npm (UI), GitHub Actions, Docker images, and Pre-commit hooks
+- **Range Strategy:** Versions are pinned to ensure reproducible builds
+- **Vulnerability Alerts:** GitHub Security Advisories generate immediate pull requests that bypass rate limits and scheduled windows, labeled `security` for prioritized triage
+
+#### Dependabot (Legacy)
+
+Configuration: [`.github/dependabot.yml`](https://github.com/prowler-cloud/prowler/blob/master/.github/dependabot.yml)
+
+Dependabot remains active for the SDK and shared automation ecosystems until the Renovate migration completes:
+
+- **Python (pip):** Monthly updates for SDK
+- **GitHub Actions:** Monthly updates for workflow dependencies
+- **Docker:** Monthly updates for base images
+- **Pre-commit:** Monthly updates for hook revisions
+
+Dependabot is paused for the API and UI; Renovate now handles those components. Even when paused, Dependabot continues to open pull requests for security vulnerabilities, ensuring critical patches are never delayed.
### JavaScript/TypeScript (UI)
@@ -136,7 +158,7 @@ The MCP Server has a small direct-dependency surface and does not yet declare a
The UI uses [pnpm](https://pnpm.io) with supply-chain controls configured in [`ui/pnpm-workspace.yaml`](https://github.com/prowler-cloud/prowler/blob/master/ui/pnpm-workspace.yaml).
- **Minimum release age** (`minimumReleaseAge: 1440`): packages must publish at least 24 hours before install. This reduces exposure during the window when a compromised release has not yet been detected and yanked.
-- **Lifecycle script allow-list** (`strictDepBuilds: true` + `allowBuilds`): only explicitly approved packages may run `install` or `postinstall` scripts (currently `sharp`, `esbuild`, `@sentry/cli`, `@heroui/shared-utils`, `unrs-resolver`, `msw`). Any unlisted package with lifecycle scripts fails the install.
+- **Lifecycle script allow-list** (`strictDepBuilds: true` + `allowBuilds`): only explicitly approved packages may run `install` or `postinstall` scripts (currently `sharp`, `esbuild`, `@sentry/cli`, `unrs-resolver`, `msw`). Any unlisted package with lifecycle scripts fails the install.
- **Trust policy** (`trustPolicy: no-downgrade`): the install fails when a package's trust evidence drops, for example after a new publisher takes over.
- **Block exotic subdeps** (`blockExoticSubdeps: true`): transitive dependencies cannot ship as git URLs or tarballs. Every package in the tree resolves from the configured registry.
- **Transitive overrides** in [`ui/package.json`](https://github.com/prowler-cloud/prowler/blob/master/ui/package.json) force specific versions for transitive packages (`lodash`, `serialize-javascript`, `qs`, `rollup`, `minimatch`, `ajv`, and others).
diff --git a/docs/snippets/applies-to.mdx b/docs/snippets/applies-to.mdx
new file mode 100644
index 0000000000..0ce22af78d
--- /dev/null
+++ b/docs/snippets/applies-to.mdx
@@ -0,0 +1,14 @@
+export const AppliesTo = ({ products = ["Prowler Cloud", "Prowler Private Cloud", "Prowler Local Server"] }) => {
+ return (
+ <Info>
+ This guide applies to{" "}
+ {products.map((name, index) => (
+ <span key={name}>
+ {index > 0 && (index === products.length - 1 ? (products.length > 2 ? ", and " : " and ") : ", ")}
+ <b>{name}</b>
+ </span>
+ ))}
+ . See <a href="/getting-started/products">Prowler product families</a>.
+ </Info>
+ );
+};
diff --git a/docs/snippets/provider-cards.mdx b/docs/snippets/provider-cards.mdx
new file mode 100644
index 0000000000..f469616cde
--- /dev/null
+++ b/docs/snippets/provider-cards.mdx
@@ -0,0 +1,23 @@
+{/* AUTO-GENERATED by docs/scripts/generate_provider_cards.py — do not edit by hand. */}
+{/* Regenerated on pre-commit whenever any provider getting-started page changes. */}
+
+export const ProviderCards = () => (
+ <Columns cols={3}>
+ <Card title="Alibaba Cloud" icon="cloud" href="/user-guide/providers/alibabacloud/getting-started-alibabacloud" />
+ <Card title="AWS" icon="aws" href="/user-guide/providers/aws/getting-started-aws" />
+ <Card title="Azure" icon="microsoft" href="/user-guide/providers/azure/getting-started-azure" />
+ <Card title="Cloudflare" icon="cloudflare" href="/user-guide/providers/cloudflare/getting-started-cloudflare" />
+ <Card title="GCP" icon="google" href="/user-guide/providers/gcp/getting-started-gcp" />
+ <Card title="GitHub" icon="github" href="/user-guide/providers/github/getting-started-github" />
+ <Card title="Google Workspace" icon="users" href="/user-guide/providers/googleworkspace/getting-started-googleworkspace" />
+ <Card title="IaC" icon="code" href="/user-guide/providers/iac/getting-started-iac" />
+ <Card title="Image" icon="docker" href="/user-guide/providers/image/getting-started-image" />
+ <Card title="Kubernetes" icon="dharmachakra" href="/user-guide/providers/kubernetes/getting-started-k8s" />
+ <Card title="Microsoft 365" icon="briefcase" href="/user-guide/providers/microsoft365/getting-started-m365" />
+ <Card title="MongoDB Atlas" icon="leaf" href="/user-guide/providers/mongodbatlas/getting-started-mongodbatlas" />
+ <Card title="Okta" icon="key" href="/user-guide/providers/okta/getting-started-okta" />
+ <Card title="OpenStack" icon="cubes" href="/user-guide/providers/openstack/getting-started-openstack" />
+ <Card title="Oracle Cloud Infrastructure (OCI)" icon="database" href="/user-guide/providers/oci/getting-started-oci" />
+ <Card title="Vercel" icon="triangle" href="/user-guide/providers/vercel/getting-started-vercel" />
+ </Columns>
+);
diff --git a/docs/snippets/subscription-banner.mdx b/docs/snippets/subscription-banner.mdx
new file mode 100644
index 0000000000..90d9b651b5
--- /dev/null
+++ b/docs/snippets/subscription-banner.mdx
@@ -0,0 +1,8 @@
+export const SubscriptionBanner = ({ children, label = "feature" }) => {
+ return (
+ <Note>
+ This {label} is available exclusively in <b>Prowler Cloud</b> and <b>Prowler Private Cloud</b> with a <a href="https://prowler.com/pricing">subscription</a>.
+ {children}
+ </Note>
+ );
+};
diff --git a/docs/style.css b/docs/style.css
index 5c626fb06b..9a1ed19a0f 100644
--- a/docs/style.css
+++ b/docs/style.css
@@ -66,3 +66,59 @@
color: #000000;
border: none;
}
+
+/* Cloud marker: subscription-gated sections and pages (Prowler Cloud / Prowler Private Cloud).
+ Rendered as a trailing ::after glyph so sidebar labels stay left-aligned.
+ Nested groups render as li[data-title] with a button toggle; top-level groups
+ render as h3 headings. Every ungated group that shares a name with a gated one
+ (Providers, Prowler Cloud, Prowler Lighthouse AI) is top-level,
+ so plain li[data-title] selectors match only the gated nested groups, folded
+ or unfolded. The Security tab group is top-level (h3) and always expanded,
+ so it is selected through its sibling list content with :has().
+ Pages are selected by their li id, which equals the page URL. The strict
+ > div > div > span:first-child path targets the title span only, never the
+ nested spans of a tag pill such as Coming Soon.
+ Icon source: /images/icons/cloud-bold.svg. See AGENTS.md "Cloud Marker" convention. */
+li[data-title="Prowler Cloud"] > button span:first-child::after,
+li[data-title="Prowler Lighthouse AI"] > button span:first-child::after,
+li[data-title="Providers"] > button span:first-child::after,
+li[data-title="Scans"] > button span:first-child::after,
+li[data-title="Prowler MCP"] > button span:first-child::after,
+div:has(+ ul a[href="/security/encryption"]) h3 span::after,
+li[id="/user-guide/compliance/tutorials/cross-provider-compliance"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-alerts"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-app-findings-triage"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-app-scan-configuration"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-cloud-aws-organizations"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-cloud-azure-management-groups"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-cloud-gcp-organizations"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-cloud-lighthouse-multi-llm"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-import-findings"] a > div > div > span:first-child::after,
+li[id="/user-guide/tutorials/prowler-scan-scheduling"] a > div > div > span:first-child::after {
+ content: "";
+ display: inline-block;
+ width: 0.875rem;
+ height: 0.875rem;
+ margin-left: 0.375rem;
+ vertical-align: -0.125rem;
+ background: url("/images/icons/cloud-bold.svg") no-repeat center / contain;
+}
+/* Wider sidebar: +2rem over the theme default (18rem) so gated labels with the
+ cloud marker fit on one line. The content column offsets are coupled to the
+ sidebar width and must shift by the same amount, hence the two companion
+ overrides selected by their Tailwind arbitrary-value class substrings. */
+@media (min-width: 1024px) {
+ #sidebar {
+ width: 20rem !important;
+ }
+
+ div[class*="pl-[23.7rem]"] {
+ padding-left: 25.7rem !important;
+ }
+}
+
+@media (min-width: 1280px) {
+ div[class*="(100%-28rem)"] {
+ width: calc(100% - 30rem) !important;
+ }
+}
diff --git a/docs/support.mdx b/docs/support.mdx
index 6999d5efbf..07c9843e12 100644
--- a/docs/support.mdx
+++ b/docs/support.mdx
@@ -3,23 +3,25 @@ title: 'Support'
description: 'Get help with Prowler'
---
-## Lighthouse AI
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
-Lighthouse AI is a Cloud Security Analyst chatbot powered by [Prowler MCP](/getting-started/products/prowler-mcp), your 24/7 virtual cloud security analyst. It can:
+## Prowler Lighthouse AI
+
+Prowler Lighthouse AI is your 24/7 cloud security analyst chatbot, the agentic cloud defender. Powered by [Prowler MCP](/getting-started/products/prowler-mcp), it can:
- **Query your security data**: Findings, compliance status, resources, and remediation guidance
-- **Search Prowler Hub**: Over 1,000 security checks and 70+ compliance frameworks
+- **Search Prowler Hub**: Over 2,000 security checks and 70+ compliance frameworks
- **Access documentation**: Search and retrieve Prowler docs contextually
-Available in Prowler Cloud and Prowler App.
+Available in Prowler Cloud, Prowler Private Cloud, and Prowler Local Server.
-[Learn more about Lighthouse AI](/getting-started/products/prowler-lighthouse-ai)
+[Learn more about Prowler Lighthouse AI](/getting-started/products/prowler-cloud-lighthouse)
## Support Desk
-> Available to **Prowler Cloud** customers.
+<SubscriptionBanner label="service" />
-For Prowler Cloud customers, submit support requests through our support desk. We'll route your request to the right team and respond via email.
+Submit support requests through our support desk. We'll route your request to the right team and respond via email.
<Card title="Submit a request" icon="ticket" href="https://support.prowler.com">
Contact our support team
diff --git a/docs/troubleshooting.mdx b/docs/troubleshooting.mdx
index 9d60c57321..9e0c849796 100644
--- a/docs/troubleshooting.mdx
+++ b/docs/troubleshooting.mdx
@@ -2,7 +2,11 @@
title: 'Troubleshooting'
---
-## Running `prowler` I get `[File: utils.py:15] [Module: utils] CRITICAL: path/redacted: OSError[13]`
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+## Prowler CLI
+
+### Running `prowler` I get `[File: utils.py:15] [Module: utils] CRITICAL: path/redacted: OSError[13]`
That is an error related to file descriptors or opened files allowed by your operating system.
@@ -14,13 +18,15 @@ This error is also related with a lack of system requirements. To improve perfor
See section [Logging](/user-guide/cli/tutorials/logging) for further information or [contact us](/contact).
-## Common Issues with Docker Compose Installation
+## Prowler Local Server
+
+Common issues with the Docker Compose installation of Prowler Local Server.
### Problem adding AWS Provider using "Connect assuming IAM Role" in Docker
See [GitHub Issue #7745](https://github.com/prowler-cloud/prowler/issues/7745) for more details.
-When running Prowler App via Docker, you may encounter errors such as `Provider not set`, `AWS assume role error - Unable to locate credentials`, or `Provider has no secret` when trying to add an AWS Provider using the "Connect assuming IAM Role" option. This typically happens because the container does not have access to the necessary AWS credentials or profiles.
+When running Prowler Local Server via Docker, you may encounter errors such as `Provider not set`, `AWS assume role error - Unable to locate credentials`, or `Provider has no secret` when trying to add an AWS Provider using the "Connect assuming IAM Role" option. This typically happens because the container does not have access to the necessary AWS credentials or profiles.
**Workaround:**
@@ -51,7 +57,7 @@ AWS_PROFILE=prowler-profile
### Scans Complete but Reports Are Missing or Compliance Data Is Empty (`Too many open files` Error)
-When running Prowler App via Docker Compose, scans may complete successfully but reports are not available for download, compliance data shows as empty, or 404 errors appear when trying to access scan reports. Checking the `worker` container logs may reveal errors like `[Errno 24] Too many open files`.
+When running Prowler Local Server via Docker Compose, scans may complete successfully but reports are not available for download, compliance data shows as empty, or 404 errors appear when trying to access scan reports. Checking the `worker` container logs may reveal errors like `[Errno 24] Too many open files`.
This issue occurs because the default file descriptor limits in Docker containers are too low for Prowler's operations. The default `docker-compose.yml` already includes `ulimits` configuration with `nofile` set to `65536` for the `worker` and `worker-beat` services to prevent this issue.
@@ -81,6 +87,39 @@ docker compose down
docker compose up -d
```
+### Worker Uses Too Much Memory on Hosts with Many CPUs
+
+<VersionBadge version="5.31.0" />
+
+When Prowler Local Server runs on a machine or Kubernetes node with many CPUs,
+the Celery worker may create one prefork process per detected CPU if concurrency
+is not configured explicitly. Each process loads the SDK runtime and cloud
+provider clients, so idle memory can be high and worker containers can be
+terminated by their memory limit.
+
+Set `DJANGO_CELERY_WORKER_CONCURRENCY` in the worker runtime environment to cap
+the number of prefork processes:
+
+```yaml
+services:
+ worker:
+ environment:
+ DJANGO_CELERY_WORKER_CONCURRENCY: "4"
+```
+
+For Kubernetes deployments, set the same variable on the worker Deployment:
+
+```yaml
+env:
+ - name: DJANGO_CELERY_WORKER_CONCURRENCY
+ value: "4"
+```
+
+Lower values reduce idle memory and the number of tasks a worker can run in
+parallel. Increase the value only when the worker has enough memory for the
+expected scan workload. Leaving the variable unset preserves Celery's default
+CPU-based concurrency.
+
### API Container Fails to Start with JWT Key Permission Error
See [GitHub Issue #8897](https://github.com/prowler-cloud/prowler/issues/8897) for more details.
@@ -161,7 +200,7 @@ A fix addressing this permission issue is being evaluated in [PR #9953](https://
### Scan Stuck in Executing State After Worker Crash
-When running Prowler App via Docker Compose, a scan may remain indefinitely in the `executing` state if the worker process crashes (for example, due to an Out of Memory condition) before it can update the scan status. Since it is not currently possible to cancel a scan in `executing` state through the UI, the workaround is to manually update the scan record in the database.
+When running Prowler Local Server via Docker Compose, a scan may remain indefinitely in the `executing` state if the worker process crashes (for example, due to an Out of Memory condition) before it can update the scan status. Since it is not currently possible to cancel a scan in `executing` state through the UI, the workaround is to manually update the scan record in the database.
**Root Cause:**
@@ -201,35 +240,29 @@ When running Prowler behind a reverse proxy (nginx, Traefik, etc.) or load balan
**Root Cause:**
-Next.js environment variables prefixed with `NEXT_PUBLIC_` are **bundled at build time**, not runtime. The pre-built Docker images from Docker Hub (`prowlercloud/prowler-ui:stable`) are built with default internal URLs. Simply setting `NEXT_PUBLIC_API_BASE_URL` in your `.env` file or environment variables and restarting the container will **NOT** work because these values are already compiled into the JavaScript bundle.
+The API base and docs URLs are resolved from the container environment **at runtime**. A single pre-built Docker image (`prowlercloud/prowler-ui:stable`) therefore serves any environment: point the URLs at your external domain and restart the container — no rebuild is required.
**Solution:**
-You must **rebuild** the UI Docker image with your external URL:
-
-```bash
-# Clone the repository (if you haven't already)
-git clone https://github.com/prowler-cloud/prowler.git
-cd prowler/ui
-
-# Build with your external URL as a build argument
-docker build \
- --build-arg NEXT_PUBLIC_API_BASE_URL=https://prowler.example.com/api/v1 \
- --build-arg NEXT_PUBLIC_API_DOCS_URL=https://prowler.example.com/api/v1/docs \
- -t prowler-ui-custom:latest \
- --target prod \
- .
-```
-
-Then update your `docker-compose.yml` to use your custom image instead of the pre-built one:
+Set the runtime environment variables to your external URL and restart the UI container:
```yaml
services:
ui:
- image: prowler-ui-custom:latest # Use your custom-built image
+ image: prowlercloud/prowler-ui:stable
+ environment:
+ UI_API_BASE_URL: https://prowler.example.com/api/v1
+ UI_API_DOCS_URL: https://prowler.example.com/api/v1/docs
# ... rest of configuration
```
+The same values can be supplied through your `.env` file:
+
+```bash
+UI_API_BASE_URL=https://prowler.example.com/api/v1
+UI_API_DOCS_URL=https://prowler.example.com/api/v1/docs
+```
+
<Note>
-The `NEXT_PUBLIC_` prefix is a Next.js convention that exposes environment variables to the browser. Since the browser bundle is compiled during `docker build`, these variables must be provided as build arguments, not runtime environment variables.
+Earlier releases inlined these values into the JavaScript bundle at build time (via the `NEXT_PUBLIC_` prefix) and required a rebuild with `--build-arg`. That is no longer necessary: `UI_API_BASE_URL` and `UI_API_DOCS_URL` are read at container start, so updating them and restarting is sufficient.
</Note>
diff --git a/docs/user-guide/cli/tutorials/configuration_file.mdx b/docs/user-guide/cli/tutorials/configuration_file.mdx
index 38dad9ac3e..e637ea9c9a 100644
--- a/docs/user-guide/cli/tutorials/configuration_file.mdx
+++ b/docs/user-guide/cli/tutorials/configuration_file.mdx
@@ -2,6 +2,8 @@
title: "Configuration File"
---
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
Several Prowler's checks have user configurable variables that can be modified in a common **configuration file**. This file can be found in the following [path](https://github.com/prowler-cloud/prowler/blob/master/prowler/config/config.yaml):
```
@@ -10,71 +12,191 @@ prowler/config/config.yaml
Additionally, you can input a custom configuration file using the `--config-file` argument.
+<Note>
+Numeric thresholds enforce hard limits. A value outside the accepted range is dropped with a warning and the check falls back to its built-in default. See [Configuration Value Limits](/developer-guide/configurable-checks#configuration-value-limits) for the exact range of every bounded option (max-days caps, percentages, counts, etc.).
+</Note>
+
## AWS
### Configurable Checks
+
The following list includes all the AWS checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|--------------------------------------------------|-----------------|
-| `acm_certificates_expiration_check` | `days_to_expire_threshold` | Integer |
-| `appstream_fleet_maximum_session_duration` | `max_session_duration_seconds` | Integer |
-| `appstream_fleet_session_disconnect_timeout` | `max_disconnect_timeout_in_seconds` | Integer |
-| `appstream_fleet_session_idle_disconnect_timeout` | `max_idle_disconnect_timeout_in_seconds` | Integer |
-| `autoscaling_find_secrets_ec2_launch_configuration` | `secrets_ignore_patterns` | List of Strings |
-| `awslambda_function_no_secrets_in_code` | `secrets_ignore_patterns` | List of Strings |
-| `awslambda_function_no_secrets_in_variables` | `secrets_ignore_patterns` | List of Strings |
-| `awslambda_function_using_supported_runtimes` | `obsolete_lambda_runtimes` | Integer |
-| `awslambda_function_vpc_is_in_multi_azs` | `lambda_min_azs` | Integer |
-| `cloudformation_stack_outputs_find_secrets` | `secrets_ignore_patterns` | List of Strings |
-| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_actions` | List of Strings |
-| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_entropy` | Integer |
-| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_minutes` | Integer |
-| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_actions` | List of Strings |
-| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_entropy` | Integer |
-| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_minutes` | Integer |
-| `cloudwatch_log_group_no_secrets_in_logs` | `secrets_ignore_patterns` | List of Strings |
-| `cloudwatch_log_group_retention_policy_specific_days_enabled` | `log_group_retention_days` | Integer |
-| `codebuild_github_allowed_organizations` | `github_allowed_organizations` | List of Strings |
-| `codebuild_project_no_secrets_in_variables` | `excluded_sensitive_environment_variables` | List of Strings |
-| `codebuild_project_no_secrets_in_variables` | `secrets_ignore_patterns` | List of Strings |
-| `config_recorder_all_regions_enabled` | `mute_non_default_regions` | Boolean |
-| `drs_job_exist` | `mute_non_default_regions` | Boolean |
-| `ec2_elastic_ip_shodan` | `shodan_api_key` | String |
-| `ec2_instance_older_than_specific_days` | `max_ec2_instance_age_in_days` | Integer |
-| `ec2_instance_secrets_user_data` | `secrets_ignore_patterns` | List of Strings |
-| `ec2_launch_template_no_secrets` | `secrets_ignore_patterns` | List of Strings |
-| `ec2_securitygroup_allow_ingress_from_internet_to_any_port` | `ec2_allowed_instance_owners` | List of Strings |
-| `ec2_securitygroup_allow_ingress_from_internet_to_any_port` | `ec2_allowed_interface_types` | List of Strings |
-| `ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports`| `ec2_high_risk_ports` | List of Integer |
-| `ec2_securitygroup_with_many_ingress_egress_rules` | `max_security_group_rules` | Integer |
-| `ecs_task_definitions_no_environment_secrets` | `secrets_ignore_patterns` | List of Strings |
-| `ecr_repositories_scan_vulnerabilities_in_latest_image` | `ecr_repository_vulnerability_minimum_severity` | String |
-| `eks_cluster_uses_a_supported_version` | `eks_cluster_oldest_version_supported` | String |
-| `eks_control_plane_logging_all_types_enabled` | `eks_required_log_types` | List of Strings |
-| `elasticache_redis_cluster_backup_enabled` | `minimum_snapshot_retention_period` | Integer |
-| `elb_is_in_multiple_az` | `elb_min_azs` | Integer |
-| `elbv2_is_in_multiple_az` | `elbv2_min_azs` | Integer |
-| `guardduty_is_enabled` | `mute_non_default_regions` | Boolean |
-| `iam_user_access_not_stale_to_sagemaker` | `max_unused_sagemaker_access_days` | Integer |
-| `iam_user_accesskey_unused` | `max_unused_access_keys_days` | Integer |
-| `iam_user_console_access_unused` | `max_console_access_days` | Integer |
-| `organizations_delegated_administrators` | `organizations_trusted_delegated_administrators` | List of Strings |
-| `organizations_scp_check_deny_regions` | `organizations_enabled_regions` | List of Strings |
-| `rds_instance_backup_enabled` | `check_rds_instance_replicas` | Boolean |
-| `securityhub_enabled` | `mute_non_default_regions` | Boolean |
-| `secretsmanager_secret_unused` | `max_days_secret_unused` | Integer |
-| `secretsmanager_secret_rotated_periodically` | `max_days_secret_unrotated` | Integer |
-| `ssm_document_secrets` | `secrets_ignore_patterns` | List of Strings |
-| `trustedadvisor_premium_support_plan_subscribed` | `verify_premium_support_plans` | Boolean |
-| `dynamodb_table_cross_account_access` | `trusted_account_ids` | List of Strings |
-| `eventbridge_bus_cross_account_access` | `trusted_account_ids` | List of Strings |
-| `eventbridge_schema_registry_cross_account_access` | `trusted_account_ids` | List of Strings |
-| `s3_bucket_cross_account_access` | `trusted_account_ids` | List of Strings |
-| `ssm_documents_set_as_public` | `trusted_account_ids` | List of Strings |
-| `vpc_endpoint_connections_trust_boundaries` | `trusted_account_ids` | List of Strings |
-| `vpc_endpoint_services_allowed_principals_trust_boundaries` | `trusted_account_ids` | List of Strings |
-| `opensearch_service_domains_not_publicly_accessible` | `trusted_ips` | List of Strings |
+| Check Name | Value | Type | Default |
+|------------------------------------------------------------------------|---------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| `accessanalyzer_enabled` | `mute_non_default_regions` | Boolean | `False` |
+| `acm_certificates_expiration_check` | `days_to_expire_threshold` | Integer | `7` |
+| `acm_certificates_with_secure_key_algorithms` | `insecure_key_algorithms` | List of Strings | `["RSA-1024", "P-192"]` |
+| `acmpca_certificate_authority_pqc_key_algorithm` | `acmpca_pqc_key_algorithms` | List of Strings | `["ML_DSA_44", "ML_DSA_65", "ML_DSA_87"]` |
+| `apigateway_domain_name_pqc_tls_enabled` | `apigateway_pqc_tls_allowed_policies` | List of Strings | `["SecurityPolicy_TLS13_1_2_FIPS_PFS_PQ_2025_09", "SecurityPolicy_TLS13_1_2_PFS_PQ_2025_09", "SecurityPolicy_TLS13_1_2_PQ_2025_09"]` |
+| `apigateway_restapi_no_secrets_in_stage_variables` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `appstream_fleet_maximum_session_duration` | `max_session_duration_seconds` | Integer | `36000` |
+| `appstream_fleet_session_disconnect_timeout` | `max_disconnect_timeout_in_seconds` | Integer | `300` |
+| `appstream_fleet_session_idle_disconnect_timeout` | `max_idle_disconnect_timeout_in_seconds` | Integer | `600` |
+| `autoscaling_find_secrets_ec2_launch_configuration` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `awslambda_function_no_secrets_in_code` | `secrets_ignore_files` | List of Strings | `[]` |
+| `awslambda_function_no_secrets_in_code` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `awslambda_function_no_secrets_in_variables` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `awslambda_function_using_supported_runtimes` | `obsolete_lambda_runtimes` | List of Strings | See `config.yaml` |
+| `awslambda_function_vpc_multi_az` | `lambda_min_azs` | Integer | `2` |
+| `cloudformation_stack_cdktoolkit_bootstrap_version` | `recommended_cdk_bootstrap_version` | Integer | `21` |
+| `cloudformation_stack_outputs_find_secrets` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `cloudfront_distributions_pqc_tls_enabled` | `cloudfront_pqc_min_protocol_versions` | List of Strings | `["TLSv1.3_2025"]` |
+| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_actions` | List of Strings | See `config.yaml` |
+| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_minutes` | Integer | `1440` |
+| `cloudtrail_threat_detection_enumeration` | `threat_detection_enumeration_threshold` | Float | `0.3` |
+| `cloudtrail_threat_detection_llm_jacking` | `threat_detection_llm_jacking_actions` | List of Strings | See `config.yaml` |
+| `cloudtrail_threat_detection_llm_jacking` | `threat_detection_llm_jacking_minutes` | Integer | `1440` |
+| `cloudtrail_threat_detection_llm_jacking` | `threat_detection_llm_jacking_threshold` | Float | `0.4` |
+| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_actions` | List of Strings | See `config.yaml` |
+| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_minutes` | Integer | `1440` |
+| `cloudtrail_threat_detection_privilege_escalation` | `threat_detection_privilege_escalation_threshold` | Float | `0.2` |
+| `cloudwatch_log_group_no_secrets_in_logs` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `cloudwatch_log_group_retention_policy_specific_days_enabled` | `log_group_retention_days` | Integer | `365` |
+| `codebuild_project_no_secrets_in_variables` | `excluded_sensitive_environment_variables` | List of Strings | `[]` |
+| `codebuild_project_no_secrets_in_variables` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `codebuild_project_uses_allowed_github_organizations` | `codebuild_github_allowed_organizations` | List of Strings | `[]` |
+| `config_delegated_admin_and_org_aggregator_all_regions` | `mute_non_default_regions` | Boolean | `False` |
+| `config_recorder_all_regions_enabled` | `mute_non_default_regions` | Boolean | `False` |
+| `documentdb_cluster_backup_enabled` | `minimum_backup_retention_period` | Integer | `7` |
+| `drs_job_exist` | `mute_non_default_regions` | Boolean | `False` |
+| `dynamodb_table_cross_account_access` | `trusted_account_ids` | List of Strings | `[]` |
+| `ec2_elastic_ip_shodan` | `shodan_api_key` | String | `null` |
+| `ec2_instance_older_than_specific_days` | `max_ec2_instance_age_in_days` | Integer | `180` |
+| `ec2_instance_secrets_user_data` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `ec2_launch_template_no_secrets` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `ec2_securitygroup_allow_ingress_from_internet_to_any_port` | `ec2_allowed_instance_owners` | List of Strings | `["amazon-elb"]` |
+| `ec2_securitygroup_allow_ingress_from_internet_to_any_port` | `ec2_allowed_interface_types` | List of Strings | `["api_gateway_managed", "vpc_endpoint"]` |
+| `ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports` | `ec2_high_risk_ports` | List of Integer | `[25, 110, 135, 143, 445, 3000, 4333, 5000, 5500, 8080, 8088]` |
+| `ec2_securitygroup_with_many_ingress_egress_rules` | `max_security_group_rules` | Integer | `50` |
+| `ecr_repositories_scan_vulnerabilities_in_latest_image` | `ecr_repository_vulnerability_minimum_severity` | String | `"MEDIUM"` |
+| `ecs_service_fargate_latest_platform_version` | `fargate_linux_latest_version` | String | `"1.4.0"` |
+| `ecs_service_fargate_latest_platform_version` | `fargate_windows_latest_version` | String | `"1.0.0"` |
+| `ecs_task_definitions_no_environment_secrets` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `eks_cluster_uses_a_supported_version` | `eks_cluster_oldest_version_supported` | String | `"1.28"` |
+| `eks_control_plane_logging_all_types_enabled` | `eks_required_log_types` | List of Strings | `["api", "audit", "authenticator", "controllerManager", "scheduler"]` |
+| `elasticache_redis_cluster_backup_enabled` | `minimum_snapshot_retention_period` | Integer | `7` |
+| `elb_is_in_multiple_az` | `elb_min_azs` | Integer | `2` |
+| `elbv2_is_in_multiple_az` | `elbv2_min_azs` | Integer | `2` |
+| `elbv2_listener_pqc_tls_enabled` | `elbv2_listener_pqc_tls_allowed_policies` | List of Strings | See `config.yaml` |
+| `eventbridge_bus_cross_account_access` | `trusted_account_ids` | List of Strings | `[]` |
+| `eventbridge_schema_registry_cross_account_access` | `trusted_account_ids` | List of Strings | `[]` |
+| `glue_etl_jobs_no_secrets_in_arguments` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `guardduty_delegated_admin_enabled_all_regions` | `mute_non_default_regions` | Boolean | `False` |
+| `guardduty_is_enabled` | `mute_non_default_regions` | Boolean | `False` |
+| `iam_role_access_not_stale_to_bedrock` | `max_unused_bedrock_access_days` | Integer | `60` |
+| `iam_user_access_not_stale_to_bedrock` | `max_unused_bedrock_access_days` | Integer | `60` |
+| `iam_user_access_not_stale_to_sagemaker` | `max_unused_sagemaker_access_days` | Integer | `90` |
+| `iam_user_accesskey_unused` | `max_unused_access_keys_days` | Integer | `45` |
+| `iam_user_console_access_unused` | `max_console_access_days` | Integer | `45` |
+| `kinesis_stream_data_retention_period` | `min_kinesis_stream_retention_hours` | Integer | `168` |
+| `neptune_cluster_backup_enabled` | `minimum_backup_retention_period` | Integer | `7` |
+| `opensearch_service_domains_not_publicly_accessible` | `trusted_ips` | List of Strings | `[]` |
+| `organizations_delegated_administrators` | `organizations_trusted_delegated_administrators` | List of Strings | `[]` |
+| `organizations_scp_check_deny_regions` | `organizations_enabled_regions` | List of Strings | `[]` |
+| `rds_instance_backup_enabled` | `check_rds_instance_replicas` | Boolean | `False` |
+| `rolesanywhere_trust_anchor_pqc_pki` | `rolesanywhere_pqc_pca_key_algorithms` | List of Strings | `["ML_DSA_44", "ML_DSA_65", "ML_DSA_87"]` |
+| `s3_bucket_cross_account_access` | `trusted_account_ids` | List of Strings | `[]` |
+| `s3_bucket_object_public` | `s3_bucket_object_public_enabled` | Boolean | `False` |
+| `s3_bucket_object_public` | `s3_bucket_object_public_max_objects` | Integer | `100` |
+| `s3_bucket_object_public` | `s3_bucket_object_public_sample_size` | Integer | `3` |
+| `secretsmanager_has_restrictive_resource_policy` | `organizations_trusted_ids` | List of Strings | `[]` |
+| `secretsmanager_secret_rotated_periodically` | `max_days_secret_unrotated` | Integer | `90` |
+| `secretsmanager_secret_unused` | `max_days_secret_unused` | Integer | `90` |
+| `securityhub_delegated_admin_enabled_all_regions` | `mute_non_default_regions` | Boolean | `False` |
+| `securityhub_enabled` | `mute_non_default_regions` | Boolean | `False` |
+| `ssm_document_secrets` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `ssm_documents_set_as_public` | `trusted_account_ids` | List of Strings | `[]` |
+| `stepfunctions_statemachine_no_secrets_in_definition` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `transfer_server_pqc_ssh_kex_enabled` | `transfer_pqc_ssh_allowed_policies` | List of Strings | `["TransferSecurityPolicy-2025-03", "TransferSecurityPolicy-FIPS-2025-03", "TransferSecurityPolicy-AS2Restricted-2025-07"]` |
+| `trustedadvisor_premium_support_plan_subscribed` | `verify_premium_support_plans` | Boolean | `True` |
+| `vpc_endpoint_connections_trust_boundaries` | `trusted_account_ids` | List of Strings | `[]` |
+| `vpc_endpoint_services_allowed_principals_trust_boundaries` | `trusted_account_ids` | List of Strings | `[]` |
+
+### Resource Scan Limit
+
+<VersionBadge version="5.32.0" />
+
+Some AWS services accumulate large numbers of resources (EBS snapshots, backup recovery points, CloudWatch log groups, Lambda functions, ECS task definitions, and CodeArtifact packages). Scanning every resource increases scan time, cost, API throttling, and finding volume. By default, Prowler scans every resource. Configure a positive resource scan limit to cap how many resources Prowler analyzes for these high-volume AWS resource paths.
+
+The global default applies to the supported resources below and is overridable per resource. The default global value is `0`, which disables the limit and scans every resource. A global `null` value is also unlimited. For per-resource values, `null` means inherit the global default; set `0` or a negative value to disable that resource limit explicitly. Positive values enable limits.
+
+<Warning>
+When positive resource scan limits are configured, compliance results are based only on the selected resources, not on the full set of matching resources in the account. Treat compliance summaries and percentages as partial evidence, because unselected resources are not analyzed and can change the real compliance posture.
+</Warning>
+
+#### Global Behavior
+
+Resource scan limits select resources for analysis. They do not cap, prioritize, or reorder findings.
+
+* **`0`, negative, or global `null` values:** Disable the limit and keep the legacy behavior for that resource path. Prowler analyzes every discovered matching resource.
+* **Positive values:** Select at most that many resources for the affected resource path. A selected resource can produce zero, one, or many findings.
+* **No PASS/FAIL prioritization:** Prowler does not inspect the compliance result before selecting resources. Limits do not prefer failed resources, passed resources, or resources with more findings.
+* **Latest-first where possible:** When AWS exposes timestamps or useful ordering, Prowler selects the newest resources first. When AWS only exposes API order, Prowler preserves that API order and documents the behavior as best effort.
+* **Findings are downstream:** Checks only evaluate the resources exposed by the service client after selection. Findings from unselected resources are not produced because those resources are not analyzed.
+
+Exact list API call reduction depends on each AWS API's ordering and pagination capabilities. When Prowler must enumerate candidates locally to select the latest resources, list calls may still read candidates, but expensive per-resource enrichment calls are bounded to the selected resources for the supported paths below.
+
+#### Full Collections Versus Limited Analysis Sets
+
+Some checks need lightweight evidence from a complete resource collection to avoid incorrect cross-service conclusions, while other checks perform primary analysis on a limited resource set.
+
+Prowler keeps full lightweight collections where they are needed for cross-service evidence. For example:
+
+* **Lambda security groups and regions:** Prowler records security groups used by all discovered Lambda functions and the regions where functions exist before it limits Lambda functions for primary Lambda checks. This helps Amazon EC2 and Amazon Inspector checks avoid false positives such as treating Lambda security groups as unused or assuming a region has no Lambda functions.
+* **CloudWatch `all_log_groups`:** Prowler records all discovered CloudWatch log groups in `all_log_groups` before limiting the primary `log_groups` analysis set. Other services can still resolve log group evidence, while CloudWatch log group checks only analyze the selected log groups.
+
+This split is intentional. It reduces expensive per-resource analysis calls without discarding lightweight context that other services need for accurate results.
+
+#### Supported AWS Resource Limits
+
+| Value | Scope | Type |
+|-------|-------|------|
+| `max_scanned_resources_per_service` | Global default for all supported high-volume AWS resources (default `0`, disabled/unlimited) | Integer |
+| `max_ebs_snapshots` | EBS snapshots (`ec2_ebs_*` checks) | Integer |
+| `max_backup_recovery_points` | Backup recovery points (`backup_recovery_point_*`) | Integer |
+| `max_cloudwatch_log_groups` | CloudWatch log groups (`cloudwatch_log_group_*`) | Integer |
+| `max_lambda_functions` | Lambda functions (`awslambda_function_*`) | Integer |
+| `max_ecs_task_definitions` | ECS task definitions (`ecs_task_definitions_*`) | Integer |
+| `max_codeartifact_packages` | CodeArtifact packages (`codeartifact_packages_*`) | Integer |
+
+#### Resource Limit Behavior By Resource Path
+
+| Resource Path | What Prowler Discovers | What A Positive Limit Selects For Analysis | Ordering And Latest Behavior | AWS Calls Reduced | Drawbacks And Consequences |
+|---------------|------------------------|--------------------------------------------|------------------------------|-------------------|----------------------------|
+| EBS snapshots (`max_ebs_snapshots`) | Prowler lists self-owned snapshots and keeps lightweight evidence that volumes and regions have snapshots. | The selected EBS snapshots exposed to `ec2_ebs_*` checks. | Prowler sorts discovered snapshots by `StartTime` newest first, then applies the limit. Snapshots without a timestamp sort last. | Bounds expensive per-snapshot public attribute checks to selected snapshots. Snapshot listing still runs so Prowler can choose the newest snapshots and keep volume/region evidence. | Older unselected snapshots are not analyzed by snapshot checks. A public, unencrypted, or otherwise noncompliant older snapshot can be missed when the limit is lower than the number of snapshots. |
+| Backup recovery points (`max_backup_recovery_points`) | Prowler lists backup vaults, plans, selections, and recovery point candidates in discovered vaults. | The selected recovery points exposed to `backup_recovery_point_*` checks and tag hydration. | Prowler sorts discovered recovery points by `CreationDate` newest first across vaults, then applies the limit. Recovery points without a timestamp sort last. | Bounds recovery point tag calls to selected recovery points. Vault and recovery point list calls still run so Prowler can choose the newest points. | Older unselected recovery points are not analyzed. A nonencrypted or otherwise noncompliant older recovery point can be missed. |
+| CloudWatch log groups (`max_cloudwatch_log_groups`) | Prowler lists log groups into both `all_log_groups` and the primary `log_groups` collection. `all_log_groups` remains available as lightweight cross-service evidence. | The selected log groups exposed to `cloudwatch_log_group_*` checks, tag hydration, and log event retrieval for checks that need log contents. | Prowler sorts discovered log groups by `creationTime` newest first, then applies the limit. Log groups without a creation time sort last. | Bounds tag calls and log event retrieval to selected log groups. Log group listing still runs to build `all_log_groups` and choose newest log groups. | Older unselected log groups are not analyzed by CloudWatch log group checks. Retention, encryption, or secrets-in-logs issues in older log groups can be missed, although cross-service evidence can still use `all_log_groups`. |
+| Lambda functions (`max_lambda_functions`) | Prowler lists Lambda functions and records lightweight security group and region evidence for all discovered functions. | The selected Lambda functions exposed to `awslambda_function_*` checks and per-function enrichment such as tags, policies, function URLs, and event source mappings. | Prowler sorts discovered functions by `LastModified` newest first, then applies the limit. Functions without `LastModified` sort last. | Bounds per-function enrichment calls to selected functions. Function listing still runs to choose newest functions and keep security group/region evidence. | Older unselected functions are not analyzed by Lambda checks. Runtime, policy, URL, environment secret, or dead-letter queue issues in older functions can be missed. Cross-service checks can still use full Lambda security group and region evidence to avoid false positives. |
+| ECS task definitions (`max_ecs_task_definitions`) | Prowler lists ECS task definition ARN candidates in each region. Candidate ARNs can remain visible and discoverable through AWS list operations, even when not all are described. | The selected task definitions that Prowler describes and exposes to `ecs_task_definitions_*` checks. | Selection is not random. Prowler calls `ListTaskDefinitions` with `sort=DESC`, which asks AWS to return task definition ARNs in descending family and revision order. Prowler then interleaves regional candidate lists to avoid starving later regions before applying the limit. This selects the latest task definition revisions according to the ARN order AWS provides, while preserving regional fairness. | Bounds `DescribeTaskDefinition` calls to selected task definitions. Prowler may still list candidates so it can select the bounded set and keep discovery deterministic. | Unselected task definitions are not described or analyzed. Issues in older task definition revisions, or in lower-priority families outside the selected AWS `sort=DESC` order, can be missed. Because ECS ordering is family/revision based rather than a registration timestamp sort across every family, this is latest-first according to AWS task definition ARN ordering, not a global newest-by-time guarantee. |
+| CodeArtifact packages (`max_codeartifact_packages`) | Prowler lists CodeArtifact repositories and lazily lists packages inside them. | The selected packages exposed to `codeartifact_packages_*` checks, including latest-version metadata for those packages. | AWS `ListPackages` does not provide a newest-package timestamp ordering in this path. Prowler preserves repository order and package API order, then applies the limit. Latest package version metadata is retrieved for selected packages with `sortBy=PUBLISHED_TIME` and `maxResults=1`. | Bounds `ListPackageVersions` calls to selected packages and can stop package listing once the limit is reached. Repository listing still runs. | Package selection is best effort by API order, not newest package order. Packages outside the selected repository/API order are not analyzed, so origin restriction or latest-version issues can be missed. |
+
+Use limits when scan duration, API throttling, or cost are more important than exhaustive coverage for these high-volume resources. Keep limits disabled when you need complete evidence for every resource in the affected checks.
+
+### Validating Discovered Secrets
+
+<VersionBadge version="5.32.0" />
+
+By default, the secret-scanning checks run fully offline: secrets are detected but never sent anywhere. Setting `secrets_validate` to `True` additionally confirms whether each discovered secret is live by authenticating with it against the corresponding provider API. The discovered secret itself serves as the credential, so Prowler requires no additional permissions to validate it.
+
+`secrets_validate` applies to every AWS secret-scanning check listed above (those that accept `secrets_ignore_patterns`). The `--scan-secrets-validate` CLI flag is provider-wide: it also enables validation for the secret-scanning checks of other providers, such as the OpenStack metadata checks.
+
+To enable validation through the configuration file, set the value under the `aws` section:
+
+```yaml
+aws:
+ secrets_validate: True
+```
+
+To enable validation for a single scan (any provider), use Prowler CLI:
+
+```
+prowler aws --scan-secrets-validate
+```
+
+<Warning>
+Secret validation makes outbound network calls that authenticate with each discovered secret. The credential is exercised against the provider, so the call appears in the audited account's logs and can trigger its monitoring (for example, AWS CloudTrail records the validation request). Validation stays disabled by default so that scans remain fully offline.
+</Warning>
## Azure
@@ -82,19 +204,20 @@ The following list includes all the AWS checks with configurable variables that
### Configurable Checks
The following list includes all the Azure checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|--------------------------------------------------|-----------------|
-| `network_public_ip_shodan` | `shodan_api_key` | String |
-| `app_ensure_php_version_is_latest` | `php_latest_version` | String |
-| `app_ensure_python_version_is_latest` | `python_latest_version` | String |
-| `app_ensure_java_version_is_latest` | `java_latest_version` | String |
-| `sqlserver_recommended_minimal_tls_version` | `recommended_minimal_tls_versions` | List of Strings |
-| `vm_sufficient_daily_backup_retention_period` | `vm_backup_min_daily_retention_days` | Integer |
-| `vm_desired_sku_size` | `desired_vm_sku_sizes` | List of Strings |
-| `defender_attack_path_notifications_properly_configured` | `defender_attack_path_minimal_risk_level` | String |
-| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_threshold` | Float |
-| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_minutes` | Integer |
-| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_actions` | List of Strings |
+| Check Name | Value | Type | Default |
+|----------------------------------------------------------|-------------------------------------------------|-----------------|------------------------------------------------------------|
+| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_actions` | List of Strings | See `config.yaml` |
+| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_minutes` | Integer | `1440` |
+| `apim_threat_detection_llm_jacking` | `apim_threat_detection_llm_jacking_threshold` | Float | `0.1` |
+| `app_ensure_java_version_is_latest` | `java_latest_version` | String | `"17"` |
+| `app_ensure_php_version_is_latest` | `php_latest_version` | String | `"8.2"` |
+| `app_ensure_python_version_is_latest` | `python_latest_version` | String | `"3.12"` |
+| `defender_attack_path_notifications_properly_configured` | `defender_attack_path_minimal_risk_level` | String | `"High"` |
+| `network_public_ip_shodan` | `shodan_api_key` | String | `null` |
+| `sqlserver_recommended_minimal_tls_version` | `recommended_minimal_tls_versions` | List of Strings | `["1.2", "1.3"]` |
+| `storage_smb_channel_encryption_with_secure_algorithm` | `recommended_smb_channel_encryption_algorithms` | List of Strings | `["AES-256-GCM"]` |
+| `vm_desired_sku_size` | `desired_vm_sku_sizes` | List of Strings | `["Standard_A8_v2", "Standard_DS3_v2", "Standard_D4s_v3"]` |
+| `vm_sufficient_daily_backup_retention_period` | `vm_backup_min_daily_retention_days` | Integer | `7` |
## GCP
@@ -102,23 +225,28 @@ The following list includes all the Azure checks with configurable variables tha
### Configurable Checks
The following list includes all the GCP checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|--------------------------------------------------|-----------------|
-| `compute_configuration_changes` | `compute_audit_log_lookback_days` | Integer |
-| `compute_instance_group_multiple_zones` | `mig_min_zones` | Integer |
+| Check Name | Value | Type | Default |
+|---------------------------------------------------|-----------------------------------|---------|---------|
+| `cloudstorage_bucket_sufficient_retention_period` | `storage_min_retention_days` | Integer | `90` |
+| `compute_instance_group_multiple_zones` | `mig_min_zones` | Integer | `2` |
+| `compute_public_address_shodan` | `shodan_api_key` | String | `null` |
+| `compute_snapshot_not_outdated` | `max_snapshot_age_days` | Integer | `90` |
+| `iam_sa_user_managed_key_unused` | `max_unused_account_days` | Integer | `180` |
+| `iam_service_account_unused` | `max_unused_account_days` | Integer | `180` |
+| `secretmanager_secret_rotation_enabled` | `secretmanager_max_rotation_days` | Integer | `90` |
## Kubernetes
### Configurable Checks
The following list includes all the Kubernetes checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|--------------------------------------------------|-----------------|
-| `audit_log_maxbackup` | `audit_log_maxbackup` | String |
-| `audit_log_maxsize` | `audit_log_maxsize` | String |
-| `audit_log_maxage` | `audit_log_maxage` | String |
-| `apiserver_strong_ciphers` | `apiserver_strong_ciphers` | String |
-| `kubelet_strong_ciphers_only` | `kubelet_strong_ciphers` | String |
+| Check Name | Value | Type | Default |
+|-------------------------------------|----------------------------|-----------------|----------------------------------------------------------------------------------------|
+| `apiserver_audit_log_maxage_set` | `audit_log_maxage` | Integer | `30` |
+| `apiserver_audit_log_maxbackup_set` | `audit_log_maxbackup` | Integer | `10` |
+| `apiserver_audit_log_maxsize_set` | `audit_log_maxsize` | Integer | `100` |
+| `apiserver_strong_ciphers_only` | `apiserver_strong_ciphers` | List of Strings | `["TLS_AES_128_GCM_SHA256", "TLS_AES_256_GCM_SHA384", "TLS_CHACHA20_POLY1305_SHA256"]` |
+| `kubelet_strong_ciphers_only` | `kubelet_strong_ciphers` | List of Strings | See `config.yaml` |
## M365
@@ -126,11 +254,13 @@ The following list includes all the Kubernetes checks with configurable variable
### Configurable Checks
The following list includes all the Microsoft 365 checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|--------------------------------------------------|-----------------|
-| `entra_admin_users_sign_in_frequency_enabled` | `sign_in_frequency` | Integer |
-| `teams_external_file_sharing_restricted` | `allowed_cloud_storage_services` | List of Strings |
-| `exchange_organization_mailtips_enabled` | `recommended_mailtips_large_audience_threshold` | Integer |
+| Check Name | Value | Type | Default |
+|--------------------------------------------------------------------|-------------------------------------------------|-----------------|--------------------|
+| `defender_malware_policy_comprehensive_attachments_filter_applied` | `recommended_blocked_file_types` | List of Strings | See check defaults |
+| `entra_admin_users_sign_in_frequency_enabled` | `sign_in_frequency` | Integer | `4` |
+| `exchange_organization_mailtips_enabled` | `recommended_mailtips_large_audience_threshold` | Integer | `25` |
+| `exchange_user_mailbox_auditing_enabled` | `audit_log_age` | Integer | `90` |
+| `teams_external_file_sharing_restricted` | `allowed_cloud_storage_services` | List of Strings | `[]` |
## GitHub
@@ -138,34 +268,76 @@ The following list includes all the Microsoft 365 checks with configurable varia
### Configurable Checks
The following list includes all the GitHub checks with configurable variables that can be changed in the configuration yaml file:
-| Check Name | Value | Type |
-|--------------------------------------------|---------------------------------------------|---------|
-| `repository_inactive_not_archived` | `inactive_not_archived_days_threshold` | Integer |
+| Check Name | Value | Type | Default |
+|------------------------------------|----------------------------------------|---------|---------|
+| `repository_inactive_not_archived` | `inactive_not_archived_days_threshold` | Integer | `180` |
## Vercel
### Configurable Checks
The following list includes all the Vercel checks with configurable variables that can be changed in the configuration YAML file:
-| Check Name | Value | Type |
-|-----------------------------------------------------|------------------------------------|-----------------|
-| `authentication_no_stale_tokens` | `stale_token_threshold_days` | Integer |
-| `authentication_token_not_expired` | `days_to_expire_threshold` | Integer |
-| `deployment_production_uses_stable_target` | `stable_branches` | List of Strings |
-| `domain_ssl_certificate_valid` | `days_to_expire_threshold` | Integer |
-| `project_environment_no_secrets_in_plain_type` | `secret_suffixes` | List of Strings |
-| `team_member_role_least_privilege` | `max_owner_percentage` | Integer |
-| `team_member_role_least_privilege` | `max_owners` | Integer |
-| `team_no_stale_invitations` | `stale_invitation_threshold_days` | Integer |
+| Check Name | Value | Type | Default |
+|------------------------------------------------|-----------------------------------|-----------------|--------------------------------------------------------------------------|
+| `authentication_no_stale_tokens` | `stale_token_threshold_days` | Integer | `90` |
+| `authentication_token_not_expired` | `days_to_expire_threshold` | Integer | `7` |
+| `deployment_production_uses_stable_target` | `stable_branches` | List of Strings | `["main", "master"]` |
+| `domain_ssl_certificate_valid` | `days_to_expire_threshold` | Integer | `7` |
+| `project_environment_no_secrets_in_plain_type` | `secret_suffixes` | List of Strings | `["_KEY", "_SECRET", "_TOKEN", "_PASSWORD", "_API_KEY", "_PRIVATE_KEY"]` |
+| `team_member_role_least_privilege` | `max_owner_percentage` | Integer | `20` |
+| `team_member_role_least_privilege` | `max_owners` | Integer | `3` |
+| `team_no_stale_invitations` | `stale_invitation_threshold_days` | Integer | `30` |
## Okta
### Configurable Checks
The following list includes all the Okta checks with configurable variables that can be changed in the configuration YAML file:
-| Check Name | Value | Type |
-|---------------------------------------------------------------|------------------------------------|---------|
-| `signon_global_session_idle_timeout_15min` | `okta_max_session_idle_minutes` | Integer |
+| Check Name | Value | Type | Default |
+|--------------------------------------------------------|-----------------------------------------------|-----------------|---------|
+| `application_admin_console_session_idle_timeout_15min` | `okta_admin_console_idle_timeout_max_minutes` | Integer | `15` |
+| `idp_smart_card_dod_approved_ca` | `okta_dod_approved_ca_issuer_patterns` | List of Strings | `[]` |
+| `signon_global_session_idle_timeout_15min` | `okta_max_session_idle_minutes` | Integer | `15` |
+| `signon_global_session_lifetime_18h` | `okta_max_session_lifetime_minutes` | Integer | `1080` |
+| `user_inactivity_automation_35d_enabled` | `okta_user_inactivity_max_days` | Integer | `35` |
+
+## Alibaba Cloud
+
+### Configurable Checks
+The following list includes all the Alibaba Cloud checks with configurable variables that can be changed in the configuration YAML file:
+
+| Check Name | Value | Type | Default |
+|--------------------------------------|--------------------------------|---------|---------|
+| `cs_kubernetes_cluster_check_recent` | `max_cluster_check_days` | Integer | `7` |
+| `cs_kubernetes_cluster_check_weekly` | `max_cluster_check_days` | Integer | `7` |
+| `ram_user_console_access_unused` | `max_console_access_days` | Integer | `90` |
+| `rds_instance_sql_audit_retention` | `min_rds_audit_retention_days` | Integer | `180` |
+| `sls_logstore_retention_period` | `min_log_retention_days` | Integer | `365` |
+
+
+## MongoDB Atlas
+
+### Configurable Checks
+The following list includes all the MongoDB Atlas checks with configurable variables that can be changed in the configuration YAML file:
+
+| Check Name | Value | Type | Default |
+|----------------------------------------------------|---------------------------------------------|---------|---------|
+| `organizations_service_account_secrets_expiration` | `max_service_account_secret_validity_hours` | Integer | `8` |
+
+
+## OpenStack
+
+### Configurable Checks
+The following list includes all the OpenStack checks with configurable variables that can be changed in the configuration YAML file:
+
+| Check Name | Value | Type | Default |
+|---------------------------------------------------|---------------------------|-----------------|---------|
+| `blockstorage_snapshot_metadata_sensitive_data` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `blockstorage_volume_metadata_sensitive_data` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `compute_instance_metadata_sensitive_data` | `secrets_ignore_patterns` | List of Strings | `[]` |
+| `image_not_shared_with_multiple_projects` | `image_sharing_threshold` | Integer | `5` |
+| `objectstorage_container_metadata_sensitive_data` | `secrets_ignore_patterns` | List of Strings | `[]` |
+
## Config YAML File Structure
@@ -179,6 +351,19 @@ aws:
# AWS Global Configuration
# aws.mute_non_default_regions --> Set to True to muted failed findings in non-default regions for AccessAnalyzer, GuardDuty, SecurityHub, DRS and Config
mute_non_default_regions: False
+
+ # AWS Resource Scan Limit Configuration
+ # Disabled by default: scan every resource unless a positive limit is configured.
+ # Findings are not capped. Set to 0 (or a negative value) to disable the limit.
+ # aws.max_scanned_resources_per_service --> global default for all services below
+ max_scanned_resources_per_service: 0
+ # Per-service overrides. Leave as null to fall back to the global default.
+ max_ebs_snapshots: null
+ max_backup_recovery_points: null
+ max_cloudwatch_log_groups: null
+ max_lambda_functions: null
+ max_ecs_task_definitions: null
+ max_codeartifact_packages: null
# If you want to mute failed findings only in specific regions, create a file with the following syntax and run it with `prowler aws -w mutelist.yaml`:
# Mutelist:
# Accounts:
@@ -534,6 +719,18 @@ azure:
"1.3"
]
+ # Azure Storage
+ # azure.storage_smb_channel_encryption_with_secure_algorithm
+ # List of SMB channel encryption algorithms allowed on file shares. A storage
+ # account passes only if every enabled algorithm is in this list. Defaults to
+ # the value required by CIS (AES-256-GCM only, excluding weaker AES-128 ciphers).
+ recommended_smb_channel_encryption_algorithms:
+ [
+ "AES-256-GCM",
+ # "AES-128-CCM",
+ # "AES-128-GCM",
+ ]
+
# Azure Virtual Machines
# azure.vm_desired_sku_size
# List of desired VM SKU sizes that are allowed in the organization
diff --git a/docs/user-guide/cli/tutorials/dashboard.mdx b/docs/user-guide/cli/tutorials/dashboard.mdx
index 0fe3c69fed..abb3872657 100644
--- a/docs/user-guide/cli/tutorials/dashboard.mdx
+++ b/docs/user-guide/cli/tutorials/dashboard.mdx
@@ -1,8 +1,8 @@
---
-title: "Dashboard"
+title: "Prowler Local Dashboard"
---
-Prowler allows you to run your own local dashboards using the csv outputs provided by Prowler
+Prowler Local Dashboard is a local web dashboard built from the CSV outputs produced by Prowler CLI. Launch it with:
```sh
prowler dashboard
@@ -12,7 +12,7 @@ prowler dashboard
You can expose the `dashboard` server in another address using the `HOST` environment variable.
</Note>
-To run Prowler local dashboard with Docker, use:
+To run Prowler Local Dashboard with Docker, use:
```sh
docker run -v /your/local/dir/prowler-output:/home/prowler/output --env HOST=0.0.0.0 --publish 127.0.0.1:11666:11666 toniblyx/prowler:latest dashboard
diff --git a/docs/user-guide/cli/tutorials/integrations.mdx b/docs/user-guide/cli/tutorials/integrations.mdx
index f3e698d799..bfd53b0c3c 100644
--- a/docs/user-guide/cli/tutorials/integrations.mdx
+++ b/docs/user-guide/cli/tutorials/integrations.mdx
@@ -33,7 +33,7 @@ To configure the Slack Integration, follow the next steps:
2. Optionally, create a Slack Channel (you can use an existing one)
3. Integrate the created Slack App to your Slack channel:
- - Click on the channel, go to the Integrations tab, and Add an App.
+ - Click the channel, go to the Integrations tab, and Add an App.
4. Set the following environment variables that Prowler will read:
diff --git a/docs/user-guide/cli/tutorials/parallel-execution.mdx b/docs/user-guide/cli/tutorials/parallel-execution.mdx
index 93b8ef381b..d659116b50 100644
--- a/docs/user-guide/cli/tutorials/parallel-execution.mdx
+++ b/docs/user-guide/cli/tutorials/parallel-execution.mdx
@@ -184,7 +184,7 @@ $combinedCsv | Export-Csv -Path "CombinedCSV.csv" -NoTypeInformation
## TODO: Additional Improvements
-Some services need to instantiate another service to perform a check. For instance, `cloudwatch` will instantiate Prowler's `iam` service to perform the `cloudwatch_cross_account_sharing_disabled` check. When the `iam` service is instantiated, it will perform the `__init__` function, and pull all the information required for that service. This provides an opportunity for an improvement in the above script to group related services together so that the `iam` services (or any other cross-service references) isn't repeatedily instantiated by grouping dependant services together. A complete mapping between these services still needs to be further investigated, but these are the cross-references that have been noted:
+Some services need to instantiate another service to perform a check. For instance, `cloudwatch` will instantiate Prowler's `iam` service to perform the `cloudwatch_cross_account_sharing_disabled` check. When the `iam` service is instantiated, it will perform the `__init__` function, and pull all the information required for that service. This provides an opportunity for an improvement in the above script to group related services together so that the `iam` services (or any other cross-service references) aren't repeatedly instantiated by grouping dependent services together. A complete mapping between these services still needs to be further investigated, but these are the cross-references that have been noted:
* inspector2 needs lambda and ec2
* cloudwatch needs iam
diff --git a/docs/user-guide/cli/tutorials/pentesting.mdx b/docs/user-guide/cli/tutorials/pentesting.mdx
index 0ad5313611..a9a8c728df 100644
--- a/docs/user-guide/cli/tutorials/pentesting.mdx
+++ b/docs/user-guide/cli/tutorials/pentesting.mdx
@@ -6,20 +6,34 @@ Prowler has some checks that analyse pentesting risks (Secrets, Internet Exposed
## Detect Secrets
-Prowler uses `detect-secrets` library to search for any secrets that are stores in plaintext within your environment.
+Prowler scans for secrets stored in plaintext within the audited environment using [Kingfisher](https://github.com/mongodb/kingfisher), an open-source secret-scanning engine. By default these scans run fully offline, so no data leaves the audited environment. Discovered secrets can optionally be validated against the provider APIs to confirm whether they are live — see [Validating Discovered Secrets](/user-guide/cli/tutorials/configuration_file#validating-discovered-secrets).
-The actual checks that have this functionality are the following:
+The checks with this functionality are the following.
+AWS:
+
+- apigateway\_restapi\_no\_secrets\_in\_stage\_variables
- autoscaling\_find\_secrets\_ec2\_launch\_configuration
- awslambda\_function\_no\_secrets\_in\_code
- awslambda\_function\_no\_secrets\_in\_variables
- cloudformation\_stack\_outputs\_find\_secrets
+- cloudwatch\_log\_group\_no\_secrets\_in\_logs
+- codebuild\_project\_no\_secrets\_in\_variables
- ec2\_instance\_secrets\_user\_data
- ec2\_launch\_template\_no\_secrets
- ecs\_task\_definitions\_no\_environment\_secrets
+- glue\_etl\_jobs\_no\_secrets\_in\_arguments
- ssm\_document\_secrets
+- stepfunctions\_statemachine\_no\_secrets\_in\_definition
-To execute detect-secrets related checks, you can run the following command:
+OpenStack:
+
+- compute\_instance\_metadata\_sensitive\_data
+- blockstorage\_volume\_metadata\_sensitive\_data
+- blockstorage\_snapshot\_metadata\_sensitive\_data
+- objectstorage\_container\_metadata\_sensitive\_data
+
+To execute the secret-scanning checks, run the following command:
```console
prowler <provider> --categories secrets
diff --git a/docs/user-guide/cli/tutorials/reporting.mdx b/docs/user-guide/cli/tutorials/reporting.mdx
index 19a14c9ae2..47e46dc2aa 100644
--- a/docs/user-guide/cli/tutorials/reporting.mdx
+++ b/docs/user-guide/cli/tutorials/reporting.mdx
@@ -114,7 +114,7 @@ The CSV format follows a standardized structure across all providers. The follow
#### CSV Headers Mapping
-The following table shows the mapping between the CSV headers and the the providers fields:
+The following table shows the mapping between the CSV headers and the providers fields:
| Open Source Consolidated| AWS| GCP| AZURE| KUBERNETES
|----------|----------|----------|----------|----------
diff --git a/docs/user-guide/compliance/tutorials/compliance.mdx b/docs/user-guide/compliance/tutorials/compliance.mdx
index 63b2502b25..6c13f60529 100644
--- a/docs/user-guide/compliance/tutorials/compliance.mdx
+++ b/docs/user-guide/compliance/tutorials/compliance.mdx
@@ -1,14 +1,15 @@
---
title: 'Compliance'
-description: 'Run security checks against compliance frameworks, review posture across providers, and download CSV or PDF reports from Prowler Cloud, Prowler App, and Prowler CLI.'
+sidebarTitle: 'Overview'
+description: 'Run security checks against compliance frameworks, review posture across providers, and download CSV or PDF reports from Prowler Cloud and Prowler Local Server, or CSV reports from Prowler CLI.'
---
-Prowler maps every security check to one or more industry-standard compliance frameworks, so a single scan produces both technical findings and framework-aligned evidence. The same evaluation runs identically whether scans are launched from Prowler Cloud, Prowler App, or Prowler CLI.
+Prowler maps every security check to one or more industry-standard compliance frameworks, so a single scan produces both technical findings and framework-aligned evidence. The same evaluation runs identically whether scans are launched from Prowler Cloud, Prowler Local Server, or Prowler CLI.
Out of the box, Prowler covers frameworks such as CIS Benchmarks, NIST 800-53, NIST CSF, NIS2, ENS RD2022, ISO 27001, PCI-DSS, SOC 2, GDPR, HIPAA, AWS Well-Architected, BSI C5, CSA CCM, MITRE ATT&CK, KISA ISMS-P, FedRAMP, and Prowler ThreatScore. The full catalog is available at [Prowler Hub](https://hub.prowler.com/compliance).
<Note>
-For the unified compliance score methodology used across frameworks, see [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore).
+For the unified compliance score methodology used across frameworks, see [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore).
</Note>
<CardGroup cols={2}>
@@ -20,15 +21,15 @@ For the unified compliance score methodology used across frameworks, see [Prowle
</Card>
</CardGroup>
-## Prowler Cloud
+## Prowler Cloud and Prowler Local Server
-The Compliance section in Prowler Cloud and Prowler App centralizes compliance posture across every connected provider. It aggregates scan results, surfaces Prowler ThreatScore, and exposes detailed requirement-level evidence for each supported framework.
+The Compliance section in Prowler Cloud and Prowler Local Server centralizes compliance posture across every connected provider. It aggregates scan results, surfaces Prowler ThreatScore, and exposes detailed requirement-level evidence for each supported framework.
### Accessing the Compliance Section
To open the compliance overview, follow these steps:
-1. Sign in to Prowler Cloud at [cloud.prowler.com](https://cloud.prowler.com/sign-in) or to a self-hosted Prowler App instance.
+1. Sign in to Prowler Cloud at [cloud.prowler.com](https://cloud.prowler.com/sign-in) or to a Prowler Local Server instance.
2. Select **Compliance** from the left navigation.
The page lists every framework evaluated by the most recent completed scan of the selected provider.
@@ -74,7 +75,7 @@ When the selected scan includes Prowler ThreatScore data, a dedicated card appea
Selecting the card opens the ThreatScore framework detail page, covered in [Working With the Framework Detail Page](#working-with-the-framework-detail-page).
-For a complete explanation of the methodology, formula, and weighting, see [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore).
+For a complete explanation of the methodology, formula, and weighting, see [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore).
### Exploring the Framework Grid
@@ -169,7 +170,7 @@ Region filters disable the per-card download dropdown to avoid generating partia
#### Downloading the Full Scan Output
-To export every framework, finding, and resource at once, use the **Scan Jobs** section instead. The ZIP archive contains the CSV, JSON-OCSF, and HTML reports plus a `compliance/` subfolder with one CSV per framework. See [Prowler App — Getting Started](/user-guide/tutorials/prowler-app) for details.
+To export every framework, finding, and resource at once, use the **Scan Jobs** section instead. The ZIP archive contains the CSV, JSON-OCSF, and HTML reports plus a `compliance/` subfolder with one CSV per framework. See [Prowler Cloud — Getting Started](/user-guide/tutorials/prowler-app) for details.
### API Access
@@ -262,6 +263,7 @@ To request a new framework or contribute one, see [Creating a New Security Compl
## Related Documentation
-* [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore)
+* [Cross-Provider Compliance](/user-guide/compliance/tutorials/cross-provider-compliance)
+* [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore)
* [Creating a New Security Compliance Framework in Prowler](/developer-guide/security-compliance-framework)
-* [Prowler App — Getting Started](/user-guide/tutorials/prowler-app)
+* [Prowler Cloud — Getting Started](/user-guide/tutorials/prowler-app)
diff --git a/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx b/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx
new file mode 100644
index 0000000000..545f5fb834
--- /dev/null
+++ b/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx
@@ -0,0 +1,209 @@
+---
+title: 'Cross-Provider Compliance'
+sidebarTitle: 'Cross-Provider Compliance'
+description: 'Aggregate a single universal compliance framework across every connected provider in Prowler Cloud, review a consolidated roll-up and per-provider breakdown, and download a combined PDF report.'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+<VersionBadge version="5.34.0" />
+
+Cross-Provider Compliance consolidates a single **universal compliance framework** across all of your connected providers into one unified view. Instead of reviewing the same framework on AWS, Azure, Google Cloud, and every other provider as separate reports, Prowler takes the most recent completed scan of every compatible provider, aggregates them by requirement, and produces a single roll-up posture with a per-provider breakdown and a combined executive PDF.
+
+<SubscriptionBanner />
+
+## What Is a Universal Compliance Framework
+
+Most Prowler compliance frameworks target a single provider (for example, CIS AWS or CIS Azure). A **universal** framework declares its requirements once in a single JSON and maps each requirement to checks for many providers at the same time, so the same CSA CCM control maps to both AWS and Azure checks. Universal frameworks live at the top of the compliance catalog (`prowler/compliance/<framework>.json`), as opposed to the legacy per-provider frameworks under `prowler/compliance/<provider>/`. For real definitions, see [`csa_ccm_4.0.json`](https://github.com/prowler-cloud/prowler/blob/master/prowler/compliance/csa_ccm_4.0.json), [`cis_controls_8.1.json`](https://github.com/prowler-cloud/prowler/blob/master/prowler/compliance/cis_controls_8.1.json), and [`dora_2022_2554.json`](https://github.com/prowler-cloud/prowler/blob/master/prowler/compliance/dora_2022_2554.json) in the Prowler repository.
+
+Prowler currently ships three universal frameworks: [CSA CCM](https://hub.prowler.com/compliance/csa_ccm_4.0), [CIS Controls](https://hub.prowler.com/compliance/cis_controls_8.1), and [DORA](https://hub.prowler.com/compliance/dora_2022_2554). Each framework page on Prowler Hub lists the full requirement-to-check mapping per provider.
+
+## How Cross-Provider Compliance Works
+
+Cross-Provider Compliance uses this structure to answer a single question: **"How compliant is my whole estate against this framework, regardless of provider?"** For a chosen universal framework, Prowler Cloud:
+
+1. Selects **one scan per compatible provider**: by default, the latest completed scan of each provider the framework supports and that you are allowed to see.
+2. Aggregates the requirement results across those scans, folding multiple accounts of the same provider type together.
+3. Computes a **roll-up status** for each requirement and an overall pass / fail / manual summary for the framework.
+4. Exposes a **per-provider breakdown** so you can see exactly which provider is failing a given control.
+
+<Note>
+Cross-Provider Compliance never mixes different frameworks. It aggregates one universal framework at a time across providers. To review a single provider in isolation, use the standard per-scan [Compliance](/user-guide/compliance/tutorials/compliance) view.
+</Note>
+
+### Supported Universal Frameworks
+
+The Cross-Provider Compliance view currently supports the following universal frameworks. The compatible providers are the ones each framework declares checks for; a provider only contributes to the roll-up when it has a completed scan.
+
+| Framework | Version | Compatible providers |
+|-----------|---------|----------------------|
+| [**CSA CCM**](https://hub.prowler.com/compliance/csa_ccm_4.0) (Cloud Controls Matrix) | 4.0 | AWS, Azure, Google Cloud, Alibaba Cloud, Oracle Cloud |
+| [**CIS Controls**](https://hub.prowler.com/compliance/cis_controls_8.1) | 8.1 | AWS, Azure, Google Cloud, Microsoft 365, Kubernetes, GitHub, Google Workspace, Okta, Oracle Cloud, Alibaba Cloud, Cloudflare, MongoDB Atlas, OpenStack, Vercel |
+| [**DORA**](https://hub.prowler.com/compliance/dora_2022_2554) (Digital Operational Resilience Act) | 2022/2554 | AWS, Azure, Google Cloud, Alibaba Cloud, Cloudflare |
+
+The catalog grows as new universal frameworks ship in Prowler. Browse the full compliance catalog at [Prowler Hub](https://hub.prowler.com/compliance).
+
+## Accessing the Cross-Provider View
+
+<Steps>
+ <Step title="Open the Compliance section">
+ Sign in to Prowler Cloud at [cloud.prowler.com](https://cloud.prowler.com/sign-in) and select **Compliance** from the left navigation.
+ </Step>
+ <Step title="Switch to the Cross-provider tab">
+ At the top of the Compliance page, select the **Cross-provider** tab. The **Per Scan** tab (the default) keeps the single-provider compliance experience unchanged.
+ </Step>
+</Steps>
+
+<img src="/images/compliance/prowler-app-cross-provider-tab.png" alt="Compliance page showing the Per Scan and Cross-provider tabs, with the Cross-provider tab highlighted" width="900" />
+
+<Note>
+Cross-Provider Compliance requires at least one completed scan for a compatible provider. If no compatible provider has finished a scan yet, the page shows a notice prompting you to launch or wait for a scan to complete.
+</Note>
+
+## Exploring the Overview
+
+The overview presents one card per supported universal framework, each summarizing the consolidated posture across every contributing provider.
+
+<img src="/images/compliance/prowler-app-cross-provider-overview.png" alt="Cross-Provider Compliance overview showing the provider filters and the framework grid (CSA CCM, CIS Controls, DORA) with per-provider chips, scores, and failed/manual counts" width="900" />
+
+Each **framework card** includes:
+
+* **Framework logo, name, and version:** Identifies the universal standard (CSA CCM, CIS Controls, DORA).
+* **Score:** The percentage of passing requirements over the total evaluated, aggregated across every contributing provider. Color coding follows three thresholds: red for severely low compliance, amber for partial compliance, and green for healthy posture.
+* **Passing Requirements:** A `passed / total` counter with the aggregated roll-up.
+* **Provider chips:** One icon per compatible provider. Providers with a completed scan appear active with their passing percentage; providers without a scan appear dimmed with a "no completed scan yet" tooltip so coverage gaps are obvious at a glance.
+* **Failed and manual counts:** The number of failing and manual requirements in the roll-up.
+
+Select any card to open the framework detail page.
+
+### Filtering the Roll-Up
+
+The filters bar controls which providers and accounts feed every card and detail view. Cross-Provider Compliance supports three filters:
+
+* **Provider type:** Narrow the roll-up to specific provider types (for example, only AWS and Azure).
+* **Provider / account:** Narrow to specific connected accounts.
+* **Provider group:** Narrow to accounts within one or more provider groups.
+
+Select **Clear filters** to reset all filters. Filters applied on the overview are carried through into the detail page and the PDF report so the view stays consistent end to end.
+
+<Note>
+Filters narrow **which providers contribute** to the aggregation. They do not change how a requirement rolls up (see [Understanding the Roll-Up Status](#understanding-the-roll-up-status)).
+</Note>
+
+## Working With the Framework Detail Page
+
+The detail page provides the full breakdown for a single universal framework: aggregate metrics, provider coverage, top failing sections, and a requirement-by-requirement view with per-provider status.
+
+<img src="/images/compliance/prowler-app-cross-provider-detail.png" alt="Cross-Provider Compliance detail page for CSA CCM 4.0 showing the header with providers scanned and the Report button, the filters, and the Requirements Status, Provider Coverage, and Top Failed Sections summary cards" width="900" />
+
+### Header
+
+The header shows the framework name and version, a link to the framework page on [Prowler Hub](https://hub.prowler.com/compliance), and a summary such as *"X of Y compatible providers scanned · N scans aggregated"* so you always know the coverage behind the numbers. The **Report** button in the top-right generates and downloads the combined PDF (see [Downloading the Combined PDF Report](#downloading-the-combined-pdf-report)).
+
+### Summary Cards
+
+Below the header, three summary cards condense the framework state:
+
+* **Requirements Status:** Donut chart with `Pass`, `Fail`, and `Manual` counts plus the total number of requirements, reflecting the consolidated roll-up.
+* **Provider Coverage:** Shows which compatible providers contributed a scan and their individual posture, so coverage gaps and per-provider weak spots are visible at a glance.
+* **Top Failed Sections:** Ranks the framework sections with the highest number of failing requirements, with deep links into the requirements accordion.
+
+### Requirements Accordion
+
+The accordion organizes every requirement of the framework. For each requirement you see:
+
+* **Requirement ID and title:** The official identifier from the framework.
+* **Roll-up status badge:** A single `Pass`, `Fail`, or `Manual` badge representing the consolidated status across all contributing providers.
+* **Per-provider status:** The status each contributing provider returned for that requirement, so a single failing provider is immediately attributable.
+* **Provider-labeled checks:** When you expand a requirement, the underlying checks are labeled with the provider they belong to (each universal requirement maps to different check IDs per provider).
+
+Expand a requirement to review the failing checks per provider, the affected resources, and remediation guidance. Findings are queried across every contributing scan and merged into a single table.
+
+<img src="/images/compliance/prowler-app-cross-provider-requirements-accordion.png" alt="Expanded DORA requirement showing the per-provider Fail badges for AWS, Azure, and Google Cloud, the requirement description and attributes, the checks count, and the merged findings table with a Provider column" width="900" />
+
+## Understanding the Roll-Up Status
+
+Cross-Provider Compliance rolls up results in two stages, with a strict **FAIL > PASS > MANUAL** precedence.
+
+**Per provider, per requirement:**
+
+* If any check fails → the provider contributes **FAIL** for that requirement.
+* Else if every check passes → **PASS**.
+* Otherwise (no pass/fail evidence) → **MANUAL**.
+
+Multiple accounts of the same provider type (for example, three AWS accounts) are folded together first, so a failure in any one account marks that provider type as failing.
+
+**Across providers, per requirement (the roll-up badge):**
+
+* If at least one contributing provider is **FAIL** → the requirement is **FAIL**.
+* Else if at least one contributing provider is **PASS** → **PASS**.
+* Otherwise → **MANUAL**.
+
+<Note>
+Only providers that **actually contributed a result** for a requirement are counted. A provider that has a scan in the aggregation but produced no result for a specific requirement (for example, because the framework maps no checks to that provider for that control) does **not** degrade the requirement to Manual. This keeps the roll-up focused on real evidence.
+</Note>
+
+### How Scans Are Selected
+
+By default, Cross-Provider Compliance auto-selects the **latest completed scan** of each compatible provider you are allowed to see. This means:
+
+* The view always reflects your most recent posture per provider, without any manual scan selection.
+* Adding a new compatible provider and running a scan automatically brings it into the roll-up.
+* Provider visibility follows your role: you only ever see providers your permissions allow, and the roll-up is scoped accordingly.
+
+## Downloading the Combined PDF Report
+
+The **Report** button on the detail page generates a single PDF that combines every contributing provider's latest scan for the framework into one executive document: a cover page listing all providers and accounts, an executive summary with the consolidated roll-up, charts, a requirements index, and detailed findings grouped by requirement, provider, and account.
+
+### The Report Follows Your Filters
+
+A report covers the exact set of scans your current filters resolve to. The provider type, provider / account, and provider group filters applied on the detail page determine which providers contribute, and the auto-select rule pins each contributing provider's latest completed scan. The PDF is built from that resolved scan set together with the framework.
+
+As a result, each filter combination produces its own report. For example:
+
+* No filters → a report covering every compatible provider that has a completed scan.
+* `Provider type = AWS, Azure` → a report covering only your AWS and Azure scans.
+* `Provider group = Production` → a report covering only the accounts in that group.
+
+Changing the filters and generating again produces a different, independent report. Each combination is tracked on its own, so switching filters back and forth never overwrites a previously generated report.
+
+<Note>
+Region filtering is **not** supported for the combined PDF report. The report recomputes status live across every region of the contributing scans, so a region-scoped request is rejected rather than producing a report that contradicts a region-filtered view.
+</Note>
+
+### Generating and Reusing a Report
+
+Because the report aggregates many scans, it is generated **asynchronously**:
+
+<Steps>
+ <Step title="Start the report">
+ Select **Report → Generate new report…**, optionally give it a name, and confirm. Prowler starts a background job and shows a "Report generation started" confirmation.
+ </Step>
+ <Step title="Wait for completion">
+ The button shows a "Generating report…" state while the job runs. Generation continues in the background: you can navigate away, and a toast notification appears when the report is ready, even after a page reload.
+ </Step>
+ <Step title="Download">
+ When the report is ready, select **Download** from the notification, or use **Report → Download latest** at any time to fetch the most recent report for the current filters.
+ </Step>
+</Steps>
+
+<img src="/images/compliance/prowler-app-cross-provider-report.png" alt="Report dropdown on the Cross-Provider Compliance detail page showing the Generate new report option" width="420" />
+
+A report already generated for a given set of filters does not need to be generated again. When you open the detail page with a filter combination that was reported before, Prowler detects the existing report and surfaces **Report → Download latest** so you can download it immediately, without launching a new job. You only need to generate a fresh report when:
+
+* You apply a filter combination that has never been reported before, or
+* A contributing provider has run a new scan since the report was generated. The report is tied to the specific scans it was built from, so a newer scan makes the previous report stale; Prowler recognizes it no longer matches the current selection and offers to generate an up-to-date one.
+
+"Download latest" reuses an existing report only when it matches the framework, the exact resolved scan set for the current filters, and the same report options. This guarantees the PDF you download reflects the posture you are looking at, rather than a report generated for a different filter or an older scan.
+
+<Note>
+The PDF detail section renders only **failed** requirements by default so the report stays focused as an executive/auditor document. As with every Prowler PDF, the detail section is capped at the first 100 failed findings per check; use the per-scan CSV or JSON-OCSF exports for the complete, untruncated list. See [Downloading Compliance Reports](/user-guide/compliance/tutorials/compliance#downloading-compliance-reports) for the full PDF behavior and the `DJANGO_PDF_MAX_FINDINGS_PER_CHECK` setting.
+</Note>
+
+## Related Documentation
+
+* [Compliance](/user-guide/compliance/tutorials/compliance)
+* [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore)
+* [Creating a New Security Compliance Framework in Prowler](/developer-guide/security-compliance-framework)
+* [Prowler Cloud — Getting Started](/user-guide/tutorials/prowler-app)
diff --git a/docs/user-guide/compliance/tutorials/threatscore.mdx b/docs/user-guide/compliance/tutorials/threatscore.mdx
index bb5a006342..8d790cf90d 100644
--- a/docs/user-guide/compliance/tutorials/threatscore.mdx
+++ b/docs/user-guide/compliance/tutorials/threatscore.mdx
@@ -1,19 +1,17 @@
---
-title: "Prowler ThreatScore Documentation"
+title: "Prowler ThreatScore"
---
-
-
-
## Introduction
-The **Prowler ThreatScore** is a comprehensive compliance scoring system that provides a unified metric for assessing your organization's security posture across compliance frameworks. It aggregates findings from individual security checks into a single, normalized score ranging from 0 to 100.
+Prowler ThreatScore is a comprehensive compliance scoring system that provides a unified metric for assessing security posture across compliance frameworks. It aggregates findings from individual security checks into a single, normalized score ranging from 0 to 100.
### Purpose
-- **Unified View**: Get a single metric representing overall compliance health
-- **Risk Prioritization**: Understand which areas pose the highest security risks
-- **Progress Tracking**: Monitor improvements in compliance posture over time
-- **Executive Reporting**: Provide clear, quantifiable security metrics to stakeholders
+
+- **Unified view:** A single metric represents overall compliance health.
+- **Risk prioritization:** Highlights which areas pose the highest security risks.
+- **Progress tracking:** Monitors improvements in compliance posture over time.
+- **Executive reporting:** Delivers clear, quantifiable security metrics to stakeholders.
## How ThreatScore Works
@@ -29,7 +27,7 @@ Pass Rate = (Number of PASS findings) / (Total findings)
The total number of checks performed (both PASS and FAIL) for a requirement. This represents the amount of evidence available - more findings provide greater confidence in the assessment.
### 3. Weight (`weight_i`)
-A numerical value (1-1000) representing the business importance or criticality of the requirement within your organization's context.
+A numerical value (1-1000) representing the business importance or criticality of the requirement within the organizational context.
### 4. Risk Level (`risk_i`)
A severity rating (1-5) indicating the potential impact of non-compliance with this requirement.
@@ -380,7 +378,7 @@ This comprehensive example demonstrates how:
### Example 4: Impact of Parameter Changes
-Using the scenario, let's see how parameter changes affect the score:
+Using the scenario, the following changes show how parameter adjustments affect the score:
#### Scenario A: Increase Encryption Risk Level
diff --git a/docs/user-guide/cookbooks/cicd-pipeline.mdx b/docs/user-guide/cookbooks/cicd-pipeline.mdx
index ee7d49eb91..11295b1f29 100644
--- a/docs/user-guide/cookbooks/cicd-pipeline.mdx
+++ b/docs/user-guide/cookbooks/cicd-pipeline.mdx
@@ -6,7 +6,7 @@ title: 'Run Prowler in CI/CD and Send Findings to Prowler Cloud'
For new projects, use the official [Prowler GitHub Action](/user-guide/tutorials/prowler-app-github-action) — a Docker-based reusable action that runs scans, optionally pushes findings to Prowler Cloud, and uploads SARIF results to GitHub Code Scanning. The GitHub Actions examples below document the legacy pip-based flow.
</Warning>
-This cookbook demonstrates how to integrate Prowler into CI/CD pipelines so that security scans run automatically and findings are sent to Prowler Cloud via [Import Findings](/user-guide/tutorials/prowler-app-import-findings). Examples cover GitHub Actions and GitLab CI.
+This cookbook demonstrates how to integrate Prowler into CI/CD pipelines so that security scans run automatically and findings are sent to Prowler Cloud via [Import Findings](/user-guide/tutorials/prowler-import-findings). Examples cover GitHub Actions and GitLab CI.
## Prerequisites
@@ -19,7 +19,7 @@ This cookbook demonstrates how to integrate Prowler into CI/CD pipelines so that
Prowler CLI provides the `--push-to-cloud` flag, which uploads scan results directly to Prowler Cloud after a scan completes. Combined with the `PROWLER_CLOUD_API_KEY` environment variable, this enables fully automated ingestion without manual file uploads.
-For full details on the flag and API, refer to the [Import Findings](/user-guide/tutorials/prowler-app-import-findings) documentation.
+For full details on the flag and API, refer to the [Import Findings](/user-guide/tutorials/prowler-import-findings) documentation.
<Note>
The examples in this guide use AWS as the target provider, but the same approach applies to any provider supported by Prowler (Azure, GCP, Kubernetes, and others). Replace `prowler aws` with the desired provider command (e.g., `prowler gcp`, `prowler azure`) and configure the corresponding credentials in the CI/CD environment.
@@ -127,7 +127,7 @@ Add the following to `.gitlab-ci.yml`:
```yaml
prowler-scan:
- image: python:3.12-slim
+ image: python:3.13-slim
stage: test
script:
- pip install prowler
@@ -154,7 +154,7 @@ stages:
- security
.prowler-base:
- image: python:3.12-slim
+ image: python:3.13-slim
stage: security
before_script:
- pip install prowler
@@ -195,7 +195,7 @@ By default, Prowler exits with a non-zero code when it finds failing checks. Thi
* **GitLab CI**: Add `allow_failure: true` to the job
<Note>
-Ingestion failures (e.g., network issues reaching Prowler Cloud) do not affect the Prowler exit code. The scan completes normally and only a warning is emitted. See [Import Findings troubleshooting](/user-guide/tutorials/prowler-app-import-findings#troubleshooting) for details.
+Ingestion failures (e.g., network issues reaching Prowler Cloud) do not affect the Prowler exit code. The scan completes normally and only a warning is emitted. See [Import Findings troubleshooting](/user-guide/tutorials/prowler-import-findings#troubleshooting) for details.
</Note>
### Caching Prowler Installation
diff --git a/docs/user-guide/cookbooks/kubernetes-in-cluster.mdx b/docs/user-guide/cookbooks/kubernetes-in-cluster.mdx
index 765bcf9313..661eeb17da 100644
--- a/docs/user-guide/cookbooks/kubernetes-in-cluster.mdx
+++ b/docs/user-guide/cookbooks/kubernetes-in-cluster.mdx
@@ -2,7 +2,7 @@
title: 'Run Kubernetes In-Cluster and Send Findings to Prowler Cloud'
---
-This cookbook walks through deploying Prowler inside a Kubernetes cluster on a recurring schedule and automatically sending findings to Prowler Cloud via [Import Findings](/user-guide/tutorials/prowler-app-import-findings). By the end, security scan results from the cluster appear in Prowler Cloud without any manual file uploads.
+This cookbook walks through deploying Prowler inside a Kubernetes cluster on a recurring schedule and automatically sending findings to Prowler Cloud via [Import Findings](/user-guide/tutorials/prowler-import-findings). By the end, security scan results from the cluster appear in Prowler Cloud without any manual file uploads.
## Prerequisites
@@ -181,7 +181,7 @@ Once the job completes and findings are pushed:
2. Open the "Scans" section to verify the ingestion job status
3. Browse findings under the Kubernetes provider
-For details on the ingestion workflow and status tracking, refer to the [Import Findings](/user-guide/tutorials/prowler-app-import-findings) documentation.
+For details on the ingestion workflow and status tracking, refer to the [Import Findings](/user-guide/tutorials/prowler-import-findings) documentation.
## Tips and Troubleshooting
@@ -204,4 +204,4 @@ For details on the ingestion workflow and status tracking, refer to the [Import
--namespace prowler-ns
```
-* **Failed uploads**: If the push to Prowler Cloud fails, the scan still completes and findings are saved locally in the container. Check the [Import Findings troubleshooting section](/user-guide/tutorials/prowler-app-import-findings#troubleshooting) for common error messages.
+* **Failed uploads**: If the push to Prowler Cloud fails, the scan still completes and findings are saved locally in the container. Check the [Import Findings troubleshooting section](/user-guide/tutorials/prowler-import-findings#troubleshooting) for common error messages.
diff --git a/docs/user-guide/cookbooks/powerbi-cis-benchmarks.mdx b/docs/user-guide/cookbooks/powerbi-cis-benchmarks.mdx
index 9b9e41ed93..15985aab28 100644
--- a/docs/user-guide/cookbooks/powerbi-cis-benchmarks.mdx
+++ b/docs/user-guide/cookbooks/powerbi-cis-benchmarks.mdx
@@ -14,7 +14,7 @@ The template and its source files live in the Prowler repository under [`contrib
The setup requires the following components:
* **Microsoft Power BI Desktop:** free download from Microsoft.
-* **Prowler compliance CSV exports:** produced by Prowler CLI or downloaded from Prowler Cloud or Prowler App.
+* **Prowler compliance CSV exports:** produced by Prowler CLI or downloaded from Prowler Cloud or Prowler Local Server.
* **Local directory:** holds the CSV exports that the template ingests at load time.
## Supported CIS Benchmarks
@@ -40,7 +40,7 @@ Download and install Microsoft Power BI Desktop from the official Microsoft site
### Step 2: Generate Compliance CSV Exports
-Compliance CSV exports can be generated through Prowler CLI or downloaded from Prowler Cloud and Prowler App.
+Compliance CSV exports can be generated through Prowler CLI or downloaded from Prowler Cloud and Prowler Local Server.
#### Option A: Prowler CLI
@@ -55,7 +55,7 @@ prowler kubernetes --compliance cis_1.12_kubernetes
The compliance CSV exports are written to `output/compliance/` by default.
-#### Option B: Prowler Cloud or Prowler App
+#### Option B: Prowler Cloud or Prowler Local Server
Open the Compliance section, select the desired CIS Benchmark, and download the CSV export.
@@ -160,7 +160,7 @@ A full walkthrough is available on YouTube:
<CardGroup cols={2}>
<Card title="Compliance Frameworks" icon="shield-check" href="/user-guide/compliance/tutorials/compliance">
- Review the Compliance workflow across Prowler Cloud, Prowler App, and Prowler CLI.
+ Review the Compliance workflow across Prowler Cloud, Prowler Local Server, and Prowler CLI.
</Card>
<Card title="Prowler Dashboard" icon="chart-line" href="/user-guide/cli/tutorials/dashboard">
Explore the built-in local dashboard for Prowler CSV exports.
diff --git a/docs/user-guide/providers/alibabacloud/getting-started-alibabacloud.mdx b/docs/user-guide/providers/alibabacloud/getting-started-alibabacloud.mdx
index 36520a8f8c..ce9778a3b5 100644
--- a/docs/user-guide/providers/alibabacloud/getting-started-alibabacloud.mdx
+++ b/docs/user-guide/providers/alibabacloud/getting-started-alibabacloud.mdx
@@ -32,14 +32,14 @@ Before you begin, make sure you have:
### Step 1: Get Your Alibaba Cloud Account ID
1. Log in to the [Alibaba Cloud Console](https://home.console.alibabacloud.com/)
-2. Click on your profile avatar in the top-right corner
+2. Click your profile avatar in the top-right corner
3. Locate and copy your Account ID
### Step 2: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to "Configuration" > "Providers"
diff --git a/docs/user-guide/providers/aws/authentication.mdx b/docs/user-guide/providers/aws/authentication.mdx
index 22deb6ab99..e3c20ca99d 100644
--- a/docs/user-guide/providers/aws/authentication.mdx
+++ b/docs/user-guide/providers/aws/authentication.mdx
@@ -7,9 +7,9 @@ Prowler requires AWS credentials to function properly. Authentication is availab
- Static Credentials
- Assumed Role
-When using **Assumed Role**, the Prowler UI exposes two credential sources for calling `sts:AssumeRole`. The labels differ between Prowler Cloud and self-hosted Prowler App, but both map to the same underlying credential types:
+When using **Assumed Role**, the Prowler UI exposes two credential sources for calling `sts:AssumeRole`. The labels differ between Prowler Cloud and Prowler Local Server, but both map to the same underlying credential types:
-- **AWS SDK Default** (shown as *"Prowler Cloud will assume your IAM role"* in Prowler Cloud and *"AWS SDK Default"* in self-hosted Prowler App): Prowler uses the credentials already available to the API and worker containers through the [AWS SDK default credential chain](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html). This is the default in Prowler Cloud and requires extra configuration in self-hosted Prowler App (see [Configuring AWS SDK Default for Self-Hosted Prowler App](#configuring-aws-sdk-default-for-self-hosted-prowler-app)).
+- **AWS SDK Default** (shown as *"Prowler Cloud will assume your IAM role"* in Prowler Cloud and *"AWS SDK Default"* in Prowler Local Server): Prowler uses the credentials already available to the API and worker containers through the [AWS SDK default credential chain](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html). This is the default in Prowler Cloud and requires extra configuration in Prowler Local Server (see [Configuring AWS SDK Default for Prowler Local Server](#configuring-aws-sdk-default-for-prowler-local-server)).
- **Access & Secret Key**: You paste an IAM user's `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and optionally `AWS_SESSION_TOKEN` into the form. Prowler uses those keys to call `sts:AssumeRole`.
## Required Permissions
@@ -81,9 +81,9 @@ This method grants permanent access and is the recommended setup for production
---
-## Configuring AWS SDK Default for Self-Hosted Prowler App
+## Configuring AWS SDK Default for Prowler Local Server
-When self-hosting Prowler App with Docker Compose, the API and worker containers do not have AWS credentials by default. Selecting **AWS SDK Default** without configuring those credentials produces:
+When running Prowler Local Server with Docker Compose, the API and worker containers do not have AWS credentials by default. Selecting **AWS SDK Default** without configuring those credentials produces:
```
AWSAssumeRoleError[1012]: AWS assume role error - An error occurred (InvalidClientTokenId) when calling the AssumeRole operation: The security token included in the request is invalid.
@@ -116,7 +116,7 @@ docker compose up -d --force-recreate api worker worker-beat
### Option 2: IAM Role (Host with Instance Metadata)
-If you run Prowler App on an EC2 instance, ECS task, or EKS pod with an attached IAM role that can assume the scan role, no extra configuration is needed — `boto3` resolves credentials through instance or task metadata automatically.
+If you run Prowler Local Server on an EC2 instance, ECS task, or EKS pod with an attached IAM role that can assume the scan role, no extra configuration is needed — `boto3` resolves credentials through instance or task metadata automatically.
### Trust Policy: Align `IAMPrincipal` With Your Identity
diff --git a/docs/user-guide/providers/aws/getting-started-aws.mdx b/docs/user-guide/providers/aws/getting-started-aws.mdx
index f0c5ab882a..11516e88b3 100644
--- a/docs/user-guide/providers/aws/getting-started-aws.mdx
+++ b/docs/user-guide/providers/aws/getting-started-aws.mdx
@@ -18,7 +18,7 @@ title: 'Getting Started With AWS on Prowler'
### Step 2: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to "Configuration" > "Providers"
@@ -67,7 +67,7 @@ This method grants permanent access and is the recommended setup for production
For detailed instructions on how to create the role, see [Authentication > Assume Role](/user-guide/providers/aws/authentication#assume-role-recommended).
-7. Once the role is created, go to the **IAM Console**, click on the "ProwlerScan" role to open its details:
+7. Once the role is created, go to the **IAM Console**, click the "ProwlerScan" role to open its details:
@@ -75,13 +75,13 @@ For detailed instructions on how to create the role, see [Authentication > Assum
-9. Paste the ARN into the corresponding field in Prowler Cloud or Prowler App
+9. Paste the ARN into the corresponding field in Prowler Cloud or Prowler Local Server
10. Select the credential source Prowler should use to call `sts:AssumeRole`. The option label differs between deployments but both map to the same `aws-sdk-default` credential type:
- - **"Prowler Cloud will assume your IAM role"** (default in Prowler Cloud) / **"AWS SDK Default"** (in self-hosted Prowler App): Prowler uses the credentials available in the API and worker environment through the [AWS SDK default credential chain](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html). In self-hosted Prowler App, these containers have no AWS credentials by default — see [Configuring AWS SDK Default for Self-Hosted Prowler App](/user-guide/providers/aws/authentication#configuring-aws-sdk-default-for-self-hosted-prowler-app) before choosing this option, or the connection test will fail with `InvalidClientTokenId`.
+ - **"Prowler Cloud will assume your IAM role"** (default in Prowler Cloud) / **"AWS SDK Default"** (in Prowler Local Server): Prowler uses the credentials available in the API and worker environment through the [AWS SDK default credential chain](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html). In Prowler Local Server, these containers have no AWS credentials by default — see [Configuring AWS SDK Default for Prowler Local Server](/user-guide/providers/aws/authentication#configuring-aws-sdk-default-for-prowler-local-server) before choosing this option, or the connection test will fail with `InvalidClientTokenId`.
- **Access & Secret Key**: Paste an IAM user's `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` (and optional `AWS_SESSION_TOKEN`) into the form. The IAM principal must be allowed to assume the target role and must match the `IAMPrincipal` parameter of the scan role template (default: `role/prowler*`).
11. Click "Next", then "Launch Scan"
@@ -110,7 +110,7 @@ AWS accounts can also be configured using static credentials (not recommended fo
For detailed instructions on how to create the credentials, see [Authentication > Credentials](/user-guide/providers/aws/authentication#credentials).
-1. Complete the form in Prowler Cloud or Prowler App and click "Next"
+1. Complete the form in Prowler Cloud or Prowler Local Server and click "Next"
diff --git a/docs/user-guide/providers/aws/organizations.mdx b/docs/user-guide/providers/aws/organizations.mdx
index bbdedef50b..b48df1c442 100644
--- a/docs/user-guide/providers/aws/organizations.mdx
+++ b/docs/user-guide/providers/aws/organizations.mdx
@@ -2,10 +2,12 @@
title: 'AWS Organizations in Prowler'
---
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
<Info>
**Using Prowler Cloud?** You can onboard your entire AWS Organization through the UI with automatic account discovery, OU-aware tree selection, and bulk connection testing — no scripts or YAML files required.
-See [AWS Organizations in Prowler Cloud](/user-guide/tutorials/prowler-cloud-aws-organizations) for the full walkthrough.
+See [AWS Organizations](/user-guide/tutorials/prowler-cloud-aws-organizations) in Prowler Cloud for the full walkthrough.
</Info>
Prowler can integrate with AWS Organizations to manage the visibility and onboarding of accounts centrally.
@@ -71,11 +73,43 @@ The additional fields in CSV header output are as follows:
## Deploying Prowler IAM Roles Across AWS Organizations
+<VersionBadge version="5.35.0" />
+
When onboarding multiple AWS accounts into Prowler Cloud, it is important to deploy the Prowler Scan IAM Role in each account. The most efficient way to do this across an AWS Organization is by leveraging AWS CloudFormation StackSets, which rolls out infrastructure—like IAM roles—to all accounts centrally from the Management or Delegated Admin account.
-When using Infrastructure as Code (IaC), Terraform is recommended to manage this deployment systematically.
+### Native CloudFormation StackSet Deployment (Recommended)
-### Recommended Approach
+The [Prowler Scan IAM Role CloudFormation template](https://github.com/prowler-cloud/prowler/blob/master/permissions/templates/cloudformation/prowler-scan-role.yml) can deploy the role across your entire AWS Organization on its own—no third-party modules required. When launched in the **Management Account** (or a **Delegated Administrator** account) with `DeployStackSet=true` and `EnableOrganizations=true`, it creates a service-managed CloudFormation StackSet that rolls the ProwlerScan role out to every account under the target Organizational Unit (or the organization root), and keeps new accounts covered automatically through auto-deployment.
+
+To deploy from the CloudFormation console: open **CloudFormation → Create stack → With new resources**, choose **Upload a template file** and select `prowler-scan-role.yml` (or paste its S3 URL), then set the parameters below on the **Specify stack details** step. Leave the **Configure stack options** step at its defaults.
+
+Deploy a single CloudFormation Stack in the Management Account with the following parameters:
+
+| Parameter | Description | Default |
+| --- | --- | --- |
+| `ExternalId` | External ID provided by Prowler Cloud to secure role assumption. | — |
+| `DeployLocalRole` | Create the ProwlerScan role in this (Management) account. | `true` |
+| `DeployStackSet` | Create a service-managed StackSet that deploys the role to member accounts. | `false` |
+| `AWSOrganizationalUnitId` | Target OU (`ou-xxxx-yyyyyyyy`) or organization root (`r-xxxx`) for the StackSet. Required when `DeployStackSet=true`. | `""` |
+| `DeployFromDelegatedAdmin` | Set to `true` when deploying from a Delegated Administrator account instead of the Management Account (uses `CallAs: DELEGATED_ADMIN`). | `false` |
+| `EnableOrganizations` | Add AWS Organizations permissions to the Management Account role: read-only account discovery plus the StackSet-management permissions the deployment needs. Set to `true` when deploying in the Management Account. | `false` |
+| `FailureTolerancePercentage` | Percentage of accounts in which the StackSet operation can fail before CloudFormation stops the operation. | `10` |
+| `RetainStacksOnAccountRemoval` | Keep the role in an account after it leaves the Organization or OU. | `false` |
+
+<Warning>
+On the review step, select **"I acknowledge that AWS CloudFormation might create IAM resources with custom names"** — the template provisions the named `ProwlerScan` IAM role, so the stack requires the `CAPABILITY_NAMED_IAM` capability and fails without this acknowledgment. (The quick-create link handles this for you.)
+</Warning>
+
+<Note>
+The service-managed StackSet does **not** deploy to the Management Account itself. Keeping `DeployLocalRole=true` ensures the role also exists there, so a single stack covers both the Management and member accounts.
+
+Trusted access for CloudFormation StackSets must be enabled in the Organization (see the note at the top of this page) before `DeployStackSet` will work.
+
+Deploying for the CLI or a self-hosted Prowler (not Prowler Cloud)? Also set `AccountId` to the account you assume the role from and `IAMPrincipal` to your identity — the defaults target Prowler Cloud. See [Aligning the trust policy with your identity](/user-guide/providers/aws/authentication#trust-policy-align-iamprincipal-with-your-identity).
+
+</Note>
+
+### Alternative: Deploy with Terraform
- **Use StackSets** from the **Management Account** (or a Delegated Admin/Security Account).
- **Use Terraform** to orchestrate the deployment.
diff --git a/docs/user-guide/providers/aws/regions-and-partitions.mdx b/docs/user-guide/providers/aws/regions-and-partitions.mdx
index 377612013e..8556ccc74e 100644
--- a/docs/user-guide/providers/aws/regions-and-partitions.mdx
+++ b/docs/user-guide/providers/aws/regions-and-partitions.mdx
@@ -64,7 +64,7 @@ When more than one source is set, precedence is:
3. `aws.disallowed_regions` in `config.yaml`
<Note>
-For self-hosted App or API-triggered scans, set `PROWLER_AWS_DISALLOWED_REGIONS` in the runtime environment of the backend scan containers such as `api` and `worker`. The `ui` container does not enforce AWS region selection.
+For Prowler Local Server or API-triggered scans, set `PROWLER_AWS_DISALLOWED_REGIONS` in the runtime environment of the backend scan containers such as `api` and `worker`. The `ui` container does not enforce AWS region selection.
</Note>
diff --git a/docs/user-guide/providers/aws/role-assumption.mdx b/docs/user-guide/providers/aws/role-assumption.mdx
index b714beafbd..54dd0e214a 100644
--- a/docs/user-guide/providers/aws/role-assumption.mdx
+++ b/docs/user-guide/providers/aws/role-assumption.mdx
@@ -77,6 +77,15 @@ The template requires the following parameters:
- **AccountId:** *(Optional)* AWS Account ID that will assume the role (default: Prowler Cloud account)
- **IAMPrincipal:** *(Optional)* The IAM principal allowed to assume the role (default: `role/prowler*`)
+<Warning>
+From the CLI you assume the role with **your own** identity, not from Prowler Cloud. The `AccountId` and `IAMPrincipal` defaults target Prowler Cloud, so set **`AccountId`** to the account you run Prowler from and **`IAMPrincipal`** to your identity (for example `role/<name>` or `user/<name>`). Otherwise `sts:AssumeRole` fails with `AccessDenied`. See [Aligning the trust policy with your identity](/user-guide/providers/aws/authentication#trust-policy-align-iamprincipal-with-your-identity).
+</Warning>
+
+<Note>
+To deploy the role across an entire AWS Organization from a single stack (Management Account role plus a service-managed StackSet for the member accounts), the template also accepts `DeployLocalRole`, `DeployStackSet`, `AWSOrganizationalUnitId`, `DeployFromDelegatedAdmin`, `EnableOrganizations`, `FailureTolerancePercentage`, and `RetainStacksOnAccountRemoval`. See [AWS Organizations in Prowler](/user-guide/providers/aws/organizations#native-cloudformation-stackset-deployment-recommended) for the full parameter reference.
+
+</Note>
+
When running Prowler CLI, include the External ID using the `-I/--external-id` flag:
```sh
diff --git a/docs/user-guide/providers/azure/authentication.mdx b/docs/user-guide/providers/azure/authentication.mdx
index 852e79d115..f41e9dd9b3 100644
--- a/docs/user-guide/providers/azure/authentication.mdx
+++ b/docs/user-guide/providers/azure/authentication.mdx
@@ -2,9 +2,9 @@
title: 'Azure Authentication in Prowler'
---
-Prowler for Azure supports multiple authentication types. Authentication methods vary between Prowler App and Prowler CLI:
+Prowler for Azure supports multiple authentication types. Authentication methods vary between Prowler Cloud and Prowler CLI:
-**Prowler App:**
+**Prowler Cloud:**
- [**Service Principal Application**](#service-principal-application-authentication-recommended)
@@ -210,13 +210,15 @@ For more detailed guidance on subscription management and permissions:
The following security checks require the `ProwlerRole` permissions for execution. Ensure the role is assigned to the identity assumed by Prowler before running these checks:
- `app_function_access_keys_configured`
+- `app_function_application_insights_enabled`
- `app_function_ftps_deployment_disabled`
+- `app_function_latest_runtime_version`
---
## Service Principal Application Authentication (Recommended)
-This method is required for Prowler App and recommended for Prowler CLI.
+This method is required for Prowler Cloud and recommended for Prowler CLI.
### Creating the Service Principal
For more information, see [Creating Prowler Service Principal](/user-guide/providers/azure/create-prowler-service-principal).
diff --git a/docs/user-guide/providers/azure/getting-started-azure.mdx b/docs/user-guide/providers/azure/getting-started-azure.mdx
index 66b3b14e3a..034e8eacfe 100644
--- a/docs/user-guide/providers/azure/getting-started-azure.mdx
+++ b/docs/user-guide/providers/azure/getting-started-azure.mdx
@@ -16,7 +16,7 @@ Government cloud subscriptions (Azure Government) are not currently supported, b
</Note>
### Prerequisites
-Before setting up Azure in Prowler App, you need to create a Service Principal with proper permissions.
+Before setting up Azure in Prowler Cloud, you need to create a Service Principal with proper permissions.
For detailed instructions on how to create the Service Principal and configure permissions, see [Authentication > Service Principal](/user-guide/providers/azure/authentication#service-principal-application-authentication-recommended).
@@ -34,12 +34,12 @@ For detailed instructions on how to create the Service Principal and configure p
### Step 2: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Navigate to `Configuration` > `Providers`
-3. Click on `Add Provider`
+3. Click `Add Provider`
@@ -53,14 +53,14 @@ For detailed instructions on how to create the Service Principal and configure p
### Step 3: Add Credentials to Prowler Cloud
-For Azure, Prowler App uses a service principal application to authenticate. For more information about the process of creating and adding permissions to a service principal refer to this [section](/user-guide/providers/azure/authentication). When you finish creating and adding the [Entra](/user-guide/providers/azure/create-prowler-service-principal#assigning-proper-permissions) and [Subscription](/user-guide/providers/azure/subscriptions) scope permissions to the service principal, enter the `Tenant ID`, `Client ID` and `Client Secret` of the service principal application.
+For Azure, Prowler Cloud uses a service principal application to authenticate. For more information about the process of creating and adding permissions to a service principal refer to this [section](/user-guide/providers/azure/authentication). When you finish creating and adding the [Entra](/user-guide/providers/azure/create-prowler-service-principal#assigning-proper-permissions) and [Subscription](/user-guide/providers/azure/subscriptions) scope permissions to the service principal, enter the `Tenant ID`, `Client ID` and `Client Secret` of the service principal application.
1. Go to your App Registration overview and copy the `Client ID` and `Tenant ID`
-2. Go to Prowler App and paste:
+2. Go to Prowler Cloud and paste:
- `Client ID`
- `Tenant ID`
diff --git a/docs/user-guide/providers/azure/resource-groups.mdx b/docs/user-guide/providers/azure/resource-groups.mdx
new file mode 100644
index 0000000000..0dbda18235
--- /dev/null
+++ b/docs/user-guide/providers/azure/resource-groups.mdx
@@ -0,0 +1,47 @@
+---
+title: 'Azure Resource Group Scope'
+---
+
+Prowler supports narrowing security scans to specific resource groups within Azure subscriptions. This is useful when you want to audit only a subset of resources rather than scanning an entire subscription.
+
+By default, Prowler scans all resource groups it has permission to access. Passing `--azure-resource-group` limits the scan to only the specified resource groups across all accessible subscriptions.
+
+## Configuring Resource Group Scoped Scans
+
+To restrict a scan to one or more resource groups, pass them as arguments using the `--azure-resource-group` flag:
+
+```console
+prowler azure --az-cli-auth --azure-resource-group <resource-group-1> <resource-group-2> ... <resource-group-N>
+```
+
+For example, to scan only `rg-production` and `rg-staging`:
+
+```console
+prowler azure --az-cli-auth --azure-resource-group rg-production rg-staging
+```
+
+This works with all supported authentication methods:
+
+```console
+# Service Principal
+prowler azure --sp-env-auth --azure-resource-group rg-production
+
+# Browser
+prowler azure --browser-auth --tenant-id <tenant-id> --azure-resource-group rg-production
+
+# Managed Identity
+prowler azure --managed-identity-auth --azure-resource-group rg-production
+```
+
+## How It Works
+
+When `--azure-resource-group` is provided, Prowler validates each specified resource group against all accessible subscriptions. A resource group is included in the scan if it exists in **at least one** subscription.
+
+- If a resource group is found in one or more subscriptions, it will be scanned in those subscriptions only.
+- If a resource group is **not found in any** subscription, Prowler logs a warning and skips it.
+- If **none** of the provided resource groups are found across any subscription, Prowler logs a warning and no resource group scoped checks will run.
+- Resource group names are matched case-insensitively, so `MyGroup` and `mygroup` are treated as the same group, mirroring Azure's own behavior.
+
+<Warning>
+If `--azure-resource-group` is used, checks that apply to specific resources are limited to the relevant resource groups. But if checks that apply to tenant or subscription scope (identity, policy, or subscription-level configuration checks) are involved, then these checks will run in their natural scope.
+</Warning>
diff --git a/docs/user-guide/providers/azure/subscriptions.mdx b/docs/user-guide/providers/azure/subscriptions.mdx
index 8fa6c73740..efd37c13e5 100644
--- a/docs/user-guide/providers/azure/subscriptions.mdx
+++ b/docs/user-guide/providers/azure/subscriptions.mdx
@@ -17,7 +17,7 @@ prowler azure --az-cli-auth --subscription-ids <subscription ID 1> <subscription
Prowler allows you to specify one or more subscriptions for scanning (up to N), enabling flexible audit configurations.
<Warning>
-The multi-subscription feature is available only in the CLI. In Prowler App, each scan is limited to a single subscription.
+The multi-subscription feature is available only in the CLI. In Prowler Cloud, each scan is limited to a single subscription.
</Warning>
## Assigning Permissions for Subscription Scans
diff --git a/docs/user-guide/providers/cloudflare/authentication.mdx b/docs/user-guide/providers/cloudflare/authentication.mdx
index fe69656a04..37e2ffafef 100644
--- a/docs/user-guide/providers/cloudflare/authentication.mdx
+++ b/docs/user-guide/providers/cloudflare/authentication.mdx
@@ -56,8 +56,8 @@ Template URLs only pre-fill the token creation form. Review the permissions, con
### Step 1: Create a User API Token
1. Log into the [Cloudflare Dashboard](https://dash.cloudflare.com).
-2. Click on the profile icon in the top right corner, then select "My Profile".
-3. Click on the **API Tokens** tab.
+2. Click the profile icon in the top right corner, then select "My Profile".
+3. Click the **API Tokens** tab.
4. Click **Create Token**, then select **Create Custom Token** at the bottom of the page.
5. Configure the token with the following settings:
- **Token name:** A descriptive name (e.g., "Prowler Security Scanner")
@@ -102,8 +102,8 @@ API Keys provide full access to the Cloudflare account. While supported, this me
### Step 1: Get the Global API Key
1. Log into the [Cloudflare Dashboard](https://dash.cloudflare.com).
-2. Click on the profile icon in the top right corner, then select "My Profile".
-3. Click on the **API Tokens** tab.
+2. Click the profile icon in the top right corner, then select "My Profile".
+3. Click the **API Tokens** tab.
4. Scroll down to the **API Keys** section.
5. Click **View** next to **Global API Key**.
6. Enter the account password to reveal the key, then copy it.
diff --git a/docs/user-guide/providers/cloudflare/getting-started-cloudflare.mdx b/docs/user-guide/providers/cloudflare/getting-started-cloudflare.mdx
index c4303b4d50..9af3dbe589 100644
--- a/docs/user-guide/providers/cloudflare/getting-started-cloudflare.mdx
+++ b/docs/user-guide/providers/cloudflare/getting-started-cloudflare.mdx
@@ -50,7 +50,7 @@ The Account ID is a 32-character hexadecimal string (e.g., `372e67954025e0ba6aaa
### Step 2: Open Prowler Cloud
-1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app).
+1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
2. Navigate to "Configuration" > "Providers".
diff --git a/docs/user-guide/providers/e2enetworks/authentication.mdx b/docs/user-guide/providers/e2enetworks/authentication.mdx
new file mode 100644
index 0000000000..67d031861d
--- /dev/null
+++ b/docs/user-guide/providers/e2enetworks/authentication.mdx
@@ -0,0 +1,99 @@
+---
+title: "E2E Networks Authentication in Prowler"
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+<VersionBadge version="5.34.0" />
+
+Prowler for E2E Networks authenticates against the E2E Networks MyAccount API using an **API key**, an **auth token**, and a numeric **project ID**. Set the API key and auth token as environment variables to avoid exposing secrets in shell history or process listings. Compatibility CLI flags are still accepted, but Prowler warns when secret values are passed directly on the command line.
+
+## Required Credentials
+
+Prowler requires read access to the E2E Networks project. The following values are needed:
+
+| Credential | Environment Variable | Description |
+|------------|----------------------|-------------|
+| API Key | `E2E_NETWORKS_API_KEY` | Identifies the MyAccount API key used for requests |
+| Auth Token | `E2E_NETWORKS_AUTH_TOKEN` | Bearer token authorizing the API key |
+| Project ID | `E2E_NETWORKS_PROJECT_ID` | Numeric ID of the project to scan |
+| Region | `E2E_NETWORKS_REGION` | Optional region to scan (defaults to all regions: Delhi, Chennai) |
+
+<Warning>
+The project ID must be an integer. A missing or non-numeric project ID stops the scan before any resource is read.
+</Warning>
+
+---
+
+## API Credentials
+
+### Step 1: Create the API Key and Auth Token
+
+1. Log into the [E2E Networks MyAccount portal](https://myaccount.e2enetworks.com).
+2. Open the **API Tokens** section under the account settings.
+3. Create a new API token and copy both the API key and the auth token.
+4. Copy the values immediately — the auth token is not shown again.
+
+### Step 2: Find the Project ID
+
+Select the target project in MyAccount and copy its numeric project ID from the project settings or the API context.
+
+### Step 3: Configure Authentication
+
+Export the credentials as environment variables:
+
+```bash
+export E2E_NETWORKS_API_KEY="your-api-key"
+export E2E_NETWORKS_AUTH_TOKEN="your-auth-token"
+export E2E_NETWORKS_PROJECT_ID="your-project-id"
+```
+
+Then run Prowler:
+
+```bash
+prowler e2enetworks
+```
+
+---
+
+## Verifying Authentication
+
+To confirm that Prowler can reach the E2E Networks project, run a scan against a single location:
+
+```bash
+prowler e2enetworks --region Delhi
+```
+
+A successful run reports findings for the discovered resources. A failed run displays an error message indicating the credential or connectivity issue.
+
+---
+
+## CI/CD Integration
+
+For automated pipelines, set the credentials as secret environment variables:
+
+**GitHub Actions:**
+
+```yaml
+env:
+ E2E_NETWORKS_API_KEY: ${{ secrets.E2E_NETWORKS_API_KEY }}
+ E2E_NETWORKS_AUTH_TOKEN: ${{ secrets.E2E_NETWORKS_AUTH_TOKEN }}
+ E2E_NETWORKS_PROJECT_ID: ${{ secrets.E2E_NETWORKS_PROJECT_ID }}
+
+steps:
+ - name: Run Prowler
+ run: prowler e2enetworks
+```
+
+**GitLab CI:**
+
+```yaml
+variables:
+ E2E_NETWORKS_API_KEY: $E2E_NETWORKS_API_KEY
+ E2E_NETWORKS_AUTH_TOKEN: $E2E_NETWORKS_AUTH_TOKEN
+ E2E_NETWORKS_PROJECT_ID: $E2E_NETWORKS_PROJECT_ID
+
+prowler_scan:
+ script:
+ - prowler e2enetworks
+```
diff --git a/docs/user-guide/providers/e2enetworks/getting-started-e2enetworks.mdx b/docs/user-guide/providers/e2enetworks/getting-started-e2enetworks.mdx
new file mode 100644
index 0000000000..6b67f4e32c
--- /dev/null
+++ b/docs/user-guide/providers/e2enetworks/getting-started-e2enetworks.mdx
@@ -0,0 +1,66 @@
+---
+title: 'Getting Started With E2E Networks on Prowler'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+<VersionBadge version="5.34.0" />
+
+Prowler for E2E Networks scans E2E Networks infrastructure for security misconfigurations across compute nodes, networking, security groups, load balancers, storage, and managed databases.
+
+<Note>
+E2E Networks support in Prowler is community-maintained. For commercial support or to request additional service coverage, [contact us](https://prowler.com/contact).
+</Note>
+
+## Prerequisites
+
+Set up authentication for E2E Networks with the [E2E Networks Authentication](/user-guide/providers/e2enetworks/authentication) guide before starting:
+
+- Create an E2E Networks API key and auth token from the MyAccount API Tokens section
+- Note the numeric project ID of the project to scan
+
+## Prowler CLI
+
+### Run Prowler for E2E Networks
+
+Once authenticated, export the credentials as environment variables and run Prowler for E2E Networks. Environment variables keep secrets out of shell history and process listings:
+
+```bash
+export E2E_NETWORKS_API_KEY="your-api-key"
+export E2E_NETWORKS_AUTH_TOKEN="your-auth-token"
+export E2E_NETWORKS_PROJECT_ID="your-project-id"
+prowler e2enetworks
+```
+
+### Run Specific Checks
+
+```bash
+prowler e2enetworks --checks node_encryption_enabled storage_block_volume_not_orphaned
+```
+
+### Run a Specific Service
+
+```bash
+prowler e2enetworks --services node
+```
+
+### Scan Specific Regions
+
+Use `--region` (aliases `--filter-region` and `-f`) to limit the scan to one or more E2E Networks regions. When the flag is omitted, Prowler reads `E2E_NETWORKS_REGION` and otherwise scans all regions (Delhi, Chennai).
+
+```bash
+prowler e2enetworks --region Delhi Chennai
+```
+
+## Available Services
+
+Prowler for E2E Networks currently supports the following services:
+
+| Service | Description |
+|---------|-------------|
+| `database` | Managed database clusters and their backup, network, and encryption settings |
+| `loadbalancer` | Application load balancers and their TLS, health-check, and protection settings |
+| `network` | Virtual Private Clouds, peering, and reserved public IP addresses |
+| `node` | Compute nodes and their encryption, protection, and network configuration |
+| `securitygroup` | Security groups and their inbound and default traffic rules |
+| `storage` | Block volumes and file storage (EFS/EPFS) with their protection settings |
diff --git a/docs/user-guide/providers/gcp/authentication.mdx b/docs/user-guide/providers/gcp/authentication.mdx
index 9447d73a20..ce01c1ba23 100644
--- a/docs/user-guide/providers/gcp/authentication.mdx
+++ b/docs/user-guide/providers/gcp/authentication.mdx
@@ -55,7 +55,7 @@ This method uses the Google Cloud CLI to authenticate and is suitable for develo
### Setup Application Default Credentials
-1. In the [GCP Console](https://console.cloud.google.com/), click on "Activate Cloud Shell"
+1. In the [GCP Console](https://console.cloud.google.com/), click "Activate Cloud Shell"
@@ -89,7 +89,7 @@ This method uses the Google Cloud CLI to authenticate and is suitable for develo
-8. Extract the following values for Prowler Cloud/App:
+8. Extract the following values for Prowler Cloud or Prowler Local Server:
- `client_id`
- `client_secret`
@@ -138,6 +138,10 @@ To keep permissions focused:
4. Continue through the wizard and finish. No principals need to be granted access in step 3 unless you want other identities to impersonate this account.
+<Note>
+To use this service account with `--organization-id`, additionally grant `roles/cloudasset.viewer` at the organization node and enable the Cloud Asset API in the service account's host project. See [Scanning a Specific GCP Organization](./organization). Without these, organization-wide scans silently fall back to listing only the projects accessible to the service account.
+</Note>
+
### Step 3: Generate a JSON Key
1. Open the newly created service account, move to the **Keys** tab, and choose **Add key > Create new key**.
diff --git a/docs/user-guide/providers/gcp/getting-started-gcp.mdx b/docs/user-guide/providers/gcp/getting-started-gcp.mdx
index e16114e19a..f40542a151 100644
--- a/docs/user-guide/providers/gcp/getting-started-gcp.mdx
+++ b/docs/user-guide/providers/gcp/getting-started-gcp.mdx
@@ -13,7 +13,7 @@ title: 'Getting Started With GCP on Prowler'
### Step 2: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to "Configuration" > "Providers"
@@ -66,7 +66,7 @@ For Google Cloud, first enter your `GCP Project ID` and then select the authenti
2. Once authenticated, get the `Client ID`, `Client Secret` and `Refresh Token` from `~/.config/gcloud/application_default_credentials`.
- 3. Paste the `Client ID`, `Client Secret` and `Refresh Token` into Prowler App.
+ 3. Paste the `Client ID`, `Client Secret` and `Refresh Token` into Prowler Cloud.
<img src="/images/gcp-credentials.png" alt="GCP Credentials" width="700" />
diff --git a/docs/user-guide/providers/gcp/organization.mdx b/docs/user-guide/providers/gcp/organization.mdx
index 6f4f7658e5..6790be5827 100644
--- a/docs/user-guide/providers/gcp/organization.mdx
+++ b/docs/user-guide/providers/gcp/organization.mdx
@@ -11,8 +11,19 @@ prowler gcp --organization-id organization-id
```
<Warning>
-Ensure the credentials used have one of the following roles at the organization level:
-Cloud Asset Viewer (`roles/cloudasset.viewer`), or Cloud Asset Owner (`roles/cloudasset.owner`).
+Ensure the credentials used have one of the following roles bound **at the organization node** (not at a project): Cloud Asset Viewer (`roles/cloudasset.viewer`) or Cloud Asset Owner (`roles/cloudasset.owner`). The role must be bound directly on the organization so the Cloud Asset API can enumerate projects across the whole hierarchy.
+
+```bash
+gcloud organizations add-iam-policy-binding <organization-id> \
+ --member="serviceAccount:<service-account-email>" \
+ --role="roles/cloudasset.viewer"
+```
+
+The Cloud Asset API (`cloudasset.googleapis.com`) must also be enabled in the project that owns the credentials (the service account's host project, or the quota project for user credentials):
+
+```bash
+gcloud services enable cloudasset.googleapis.com --project <credentials-project-id>
+```
</Warning>
<Note>
diff --git a/docs/user-guide/providers/github/authentication.mdx b/docs/user-guide/providers/github/authentication.mdx
index 0b5ab6b720..1546bf284a 100644
--- a/docs/user-guide/providers/github/authentication.mdx
+++ b/docs/user-guide/providers/github/authentication.mdx
@@ -12,7 +12,7 @@ Prowler offers three authentication methods. Fine-Grained Personal Access Tokens
| Method | Best For | Key Benefit |
|--------|----------|-------------|
-| [**Fine-Grained Personal Access Token**](#fine-grained-personal-access-token-recommended) | Individual users, quick setup | Simple, user-scoped access |
+| [**Fine-Grained Personal Access Token**](#fine-grained-personal-access-token-recommended-for-individual-use) | Individual users, quick setup | Simple, user-scoped access |
| [**GitHub App**](#github-app-credentials) | Organizations, automation, CI/CD | Organization-scoped, no personal account dependency |
| [**OAuth App Token**](#oauth-app-token) | Delegated user authorization | User-consented access flows |
@@ -271,7 +271,7 @@ Store the `.pem` private key securely. Anyone with this key can authenticate as
## Prowler Cloud Authentication
-For step-by-step setup instructions for Prowler Cloud, see the [Getting Started Guide](/user-guide/providers/github/getting-started-github#prowler-cloudapp).
+For step-by-step setup instructions for Prowler Cloud, see the [Getting Started Guide](/user-guide/providers/github/getting-started-github#prowler-cloud-and-prowler-local-server).
### Using Personal Access Token
@@ -301,7 +301,7 @@ For step-by-step setup instructions for Prowler Cloud, see the [Getting Started
3. Enter your GitHub App ID and upload the private key (`.pem` file).
-For complete step-by-step instructions, see the [Getting Started Guide](/user-guide/providers/github/getting-started-github#prowler-cloudapp).
+For complete step-by-step instructions, see the [Getting Started Guide](/user-guide/providers/github/getting-started-github#prowler-cloud-and-prowler-local-server).
---
diff --git a/docs/user-guide/providers/github/getting-started-github.mdx b/docs/user-guide/providers/github/getting-started-github.mdx
index 079f9a1d7b..09acdfe0c9 100644
--- a/docs/user-guide/providers/github/getting-started-github.mdx
+++ b/docs/user-guide/providers/github/getting-started-github.mdx
@@ -16,7 +16,7 @@ Prowler can scan either:
</Note>
<CardGroup cols={2}>
- <Card title="Prowler Cloud/App" icon="cloud" href="#prowler-cloudapp">
+ <Card title="Prowler Cloud & Local Server" icon="cloud" href="#prowler-cloud-and-prowler-local-server">
Web-based interface with centralized management
</Card>
<Card title="Prowler CLI" icon="terminal" href="#prowler-cli">
@@ -26,7 +26,7 @@ Prowler can scan either:
---
-## Prowler Cloud/App
+## Prowler Cloud and Prowler Local Server
<iframe width="560" height="380" src="https://www.youtube-nocookie.com/embed/9ETI84Xpu2g" title="Prowler Cloud Onboarding Github" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="1"></iframe>
@@ -34,7 +34,7 @@ Prowler can scan either:
### Prerequisites
-Before adding GitHub to Prowler Cloud/App, ensure you have:
+Before adding GitHub to Prowler Cloud or Prowler Local Server, ensure you have:
1. **GitHub Account Access**
- Personal GitHub account, OR
@@ -46,9 +46,9 @@ Before adding GitHub to Prowler Cloud/App, ensure you have:
- OAuth App Token
- GitHub App Credentials (Not Recommended - limited data access)
-### Step 1: Access Prowler Cloud/App
+### Step 1: Access Prowler Cloud or Prowler Local Server
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to **Configuration** → **Providers**
diff --git a/docs/user-guide/providers/googleworkspace/authentication.mdx b/docs/user-guide/providers/googleworkspace/authentication.mdx
index efed268b9a..049b4fb4ae 100644
--- a/docs/user-guide/providers/googleworkspace/authentication.mdx
+++ b/docs/user-guide/providers/googleworkspace/authentication.mdx
@@ -18,7 +18,7 @@ Prowler requests the following read-only OAuth 2.0 scopes:
| `https://www.googleapis.com/auth/admin.directory.domain.readonly` | Read access to domain information |
| `https://www.googleapis.com/auth/admin.directory.customer.readonly` | Read access to customer information (Customer ID) |
| `https://www.googleapis.com/auth/admin.directory.orgunit.readonly` | Read access to organizational unit hierarchy (identifies the root OU for policy filtering) |
-| `https://www.googleapis.com/auth/cloud-identity.policies.readonly` | Read access to domain-level application policies (required for Calendar, Gmail, Chat, and Drive service checks) |
+| `https://www.googleapis.com/auth/cloud-identity.policies.readonly` | Read access to domain-level application policies (required for Calendar, Chat, Drive, Gmail, Groups, Marketplace, Security, and Sites service checks) |
| `https://www.googleapis.com/auth/admin.directory.rolemanagement.readonly` | Read access to admin roles and role assignments |
<Warning>
@@ -40,7 +40,7 @@ In the [Google Cloud Console](https://console.cloud.google.com), select the targ
| API | Required For |
|-----|--------------|
| **Admin SDK API** | Directory service checks (users, roles, domains) |
-| **Cloud Identity API** | Calendar, Gmail, Chat, and Drive service checks (domain-level application policies) |
+| **Cloud Identity API** | All service checks except Directory (domain-level application policies) |
For each API:
@@ -49,7 +49,7 @@ For each API:
3. Click **Enable**
<Note>
-Both APIs must be enabled in the same GCP project that hosts the Service Account. Calendar, Gmail, Chat, and Drive checks will return no findings if the Cloud Identity API is not enabled.
+Both APIs must be enabled in the same GCP project that hosts the Service Account. All service checks except Directory will return no findings if the Cloud Identity API is not enabled.
</Note>
### Step 3: Create a Service Account
@@ -178,7 +178,7 @@ If Prowler connects but returns empty results or permission errors for specific
### Policy API Checks Return No Findings
-If the Directory checks run successfully but the Calendar, Gmail, Chat, or Drive checks return no findings, the Cloud Identity Policy API is not reachable for this Service Account. Verify:
+If the Directory checks run successfully but other service checks (Calendar, Chat, Drive, Gmail, Groups, Marketplace, Security, Sites) return no findings, the Cloud Identity Policy API is not reachable for this Service Account. Verify:
- The **Cloud Identity API** is enabled in the GCP project hosting the Service Account (Step 2)
- The scope `https://www.googleapis.com/auth/cloud-identity.policies.readonly` is included in the Domain-Wide Delegation OAuth scopes list in the Admin Console (Step 5)
diff --git a/docs/user-guide/providers/googleworkspace/getting-started-googleworkspace.mdx b/docs/user-guide/providers/googleworkspace/getting-started-googleworkspace.mdx
index 8931c43ebd..01e6e89986 100644
--- a/docs/user-guide/providers/googleworkspace/getting-started-googleworkspace.mdx
+++ b/docs/user-guide/providers/googleworkspace/getting-started-googleworkspace.mdx
@@ -42,7 +42,7 @@ The Customer ID starts with the letter "C" followed by alphanumeric characters (
### Step 2: Open Prowler Cloud
-1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app).
+1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
2. Navigate to "Configuration" > "Providers".
diff --git a/docs/user-guide/providers/iac/getting-started-iac.mdx b/docs/user-guide/providers/iac/getting-started-iac.mdx
index d1e978dc75..9a941c633d 100644
--- a/docs/user-guide/providers/iac/getting-started-iac.mdx
+++ b/docs/user-guide/providers/iac/getting-started-iac.mdx
@@ -24,7 +24,7 @@ Prowler IaC provider scans the following Infrastructure as Code configurations f
## How It Works
-- Prowler App leverages [Trivy](https://trivy.dev/docs/latest/guide/coverage/iac/#scanner) to scan local directories (or specified paths) for supported IaC files, or scans remote repositories.
+- Prowler Cloud leverages [Trivy](https://trivy.dev/docs/latest/guide/coverage/iac/#scanner) to scan local directories (or specified paths) for supported IaC files, or scans remote repositories.
- No cloud credentials or authentication are required for local scans.
- For remote repository scans, authentication can be provided via [git URL](https://git-scm.com/docs/git-clone#_git_urls), CLI flags or environment variables.
- Check the [IaC Authentication](/user-guide/providers/iac/authentication) page for more details.
@@ -37,11 +37,11 @@ Prowler IaC provider scans the following Infrastructure as Code configurations f
### Supported Scanners
-Scanner selection is not configurable in Prowler App. Default scanners, misconfig and secret, run automatically during each scan.
+Scanner selection is not configurable in Prowler Cloud. Default scanners, misconfig and secret, run automatically during each scan.
-### Step 1: Access Prowler Cloud/App
+### Step 1: Access Prowler Cloud or Prowler Local Server
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to "Configuration" > "Providers"
diff --git a/docs/user-guide/providers/image/getting-started-image.mdx b/docs/user-guide/providers/image/getting-started-image.mdx
index b9c305d0ef..6382f10e5c 100644
--- a/docs/user-guide/providers/image/getting-started-image.mdx
+++ b/docs/user-guide/providers/image/getting-started-image.mdx
@@ -33,7 +33,7 @@ Prowler Cloud does not support scanner selection. The vulnerability, secret, and
### Step 1: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Navigate to "Configuration" > "Providers"
diff --git a/docs/user-guide/providers/kubernetes/getting-started-k8s.mdx b/docs/user-guide/providers/kubernetes/getting-started-k8s.mdx
index 9ca791110f..c62ec2b8a1 100644
--- a/docs/user-guide/providers/kubernetes/getting-started-k8s.mdx
+++ b/docs/user-guide/providers/kubernetes/getting-started-k8s.mdx
@@ -4,9 +4,9 @@ title: 'Getting Started with Kubernetes'
## Prowler Cloud
-### Step 1: Access Prowler Cloud/App
+### Step 1: Access Prowler Cloud or Prowler Local Server
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app)
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app)
2. Go to "Configuration" > "Providers"
@@ -21,7 +21,11 @@ title: 'Getting Started with Kubernetes'
### Step 2: Configure Kubernetes Authentication
-For Kubernetes, Prowler App uses a `kubeconfig` file to authenticate. Paste the contents of your `kubeconfig` file into the `Kubeconfig content` field.
+For Kubernetes, Prowler Cloud uses a `kubeconfig` file to authenticate. Paste the contents of your `kubeconfig` file into the `Kubeconfig content` field.
+
+<Note>
+Kubeconfigs that use `users[].user.exec` authentication are not supported in Prowler Cloud or Prowler Local Server. For security reasons, Prowler Cloud does not run commands declared by uploaded kubeconfigs. Use kubeconfig credentials that do not rely on `exec` authentication, such as the ServiceAccount token flow documented below.
+</Note>
By default, the `kubeconfig` file is located at `~/.kube/config`.
diff --git a/docs/user-guide/providers/linode/authentication.mdx b/docs/user-guide/providers/linode/authentication.mdx
new file mode 100644
index 0000000000..3ebb7ef326
--- /dev/null
+++ b/docs/user-guide/providers/linode/authentication.mdx
@@ -0,0 +1,97 @@
+---
+title: "Linode Authentication in Prowler"
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+<VersionBadge version="5.31.0" />
+
+Prowler for Linode uses a **Personal Access Token** (PAT) for authentication. Prowler reads the token **exclusively** from the `LINODE_TOKEN` environment variable, so the secret is never exposed in shell history or process listings. There are no credential CLI flags.
+
+## Required Permissions
+
+Prowler requires read-only access to your Linode account. The following OAuth scopes are needed on the Personal Access Token:
+
+| Scope | Access | Description |
+|-------|--------|-------------|
+| `account` | `Read Only` | Required to list users and verify account identity |
+| `linodes` | `Read Only` | Required to list instances and their configurations |
+| `firewall` | `Read Only` | Required to list firewalls and their rules |
+
+<Warning>
+Ensure the token has all required scopes. Missing permissions will cause some checks to fail or return incomplete results.
+</Warning>
+
+---
+
+## Personal Access Token
+
+### Step 1: Create a Personal Access Token
+
+1. Log into the [Linode Cloud Manager](https://cloud.linode.com).
+2. Click your username in the top-right corner, then select **API Tokens** under the "My Profile" section.
+3. Click **Create a Personal Access Token**.
+4. Configure the token:
+ - **Label:** A descriptive name (e.g., "Prowler Security Scanner")
+ - **Expiry:** Set an appropriate expiration (e.g., 6 months)
+ - **Permissions:** Set the following scopes to **Read Only**:
+ - Account
+ - Linodes
+ - Firewall
+ - All other scopes can be set to **No Access**
+5. Click **Create Token**.
+6. Copy the token immediately — it will not be shown again.
+
+### Step 2: Configure Authentication
+
+Set the `LINODE_TOKEN` environment variable:
+
+```bash
+export LINODE_TOKEN="your-personal-access-token"
+```
+
+Then run Prowler:
+
+```bash
+prowler linode
+```
+
+---
+
+## Verifying Authentication
+
+To verify that Prowler can connect to your Linode account, run:
+
+```bash
+prowler linode --list-checks
+```
+
+If authentication succeeds, you will see a list of available checks. If it fails, Prowler will display an error message indicating the credentials issue.
+
+---
+
+## CI/CD Integration
+
+For automated pipelines, set the token as a secret environment variable:
+
+**GitHub Actions:**
+
+```yaml
+env:
+ LINODE_TOKEN: ${{ secrets.LINODE_TOKEN }}
+
+steps:
+ - name: Run Prowler
+ run: prowler linode
+```
+
+**GitLab CI:**
+
+```yaml
+variables:
+ LINODE_TOKEN: $LINODE_TOKEN
+
+prowler_scan:
+ script:
+ - prowler linode
+```
diff --git a/docs/user-guide/providers/linode/getting-started-linode.mdx b/docs/user-guide/providers/linode/getting-started-linode.mdx
new file mode 100644
index 0000000000..128fdf1c90
--- /dev/null
+++ b/docs/user-guide/providers/linode/getting-started-linode.mdx
@@ -0,0 +1,61 @@
+---
+title: 'Getting Started With Linode on Prowler'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+<VersionBadge version="5.31.0" />
+
+Prowler for Linode scans your Linode infrastructure for security misconfigurations, including compute settings, networking rules, user account security, and more.
+
+<Note>
+Linode support in Prowler is community-maintained. For commercial support or to request additional service coverage, [contact us](https://prowler.com/contact).
+</Note>
+
+## Prerequisites
+
+Set up authentication for Linode with the [Linode Authentication](/user-guide/providers/linode/authentication) guide before starting:
+
+- Create a Linode Personal Access Token with read-only permissions
+- The token requires at minimum: `account:read_only`, `linodes:read_only`, and `firewall:read_only` scopes
+
+## Prowler CLI
+
+### Run Prowler for Linode
+
+Once authenticated with a Personal Access Token, set the `LINODE_TOKEN` environment variable and run Prowler for Linode. Prowler reads the token exclusively from the environment variable, so the secret is never exposed in shell history or process listings:
+
+```bash
+export LINODE_TOKEN="your-personal-access-token"
+prowler linode
+```
+
+### Run Specific Checks
+
+```bash
+prowler linode --checks compute_instance_backups_enabled compute_instance_watchdog_enabled
+```
+
+### Run a Specific Service
+
+```bash
+prowler linode --services networking
+```
+
+### Scan Specific Regions
+
+Use `--region` (alias `--filter-region` / `-f`) to limit the scan to one or more Linode regions. Region-less resources (account administration and Cloud Firewalls) are always scanned; only regional resources such as instances are filtered. When the flag is omitted, all regions are scanned.
+
+```bash
+prowler linode --region eu-central us-east
+```
+
+## Available Services
+
+Prowler for Linode currently supports the following services:
+
+| Service | Description |
+|---------|-------------|
+| `administration` | Account administration includes users and access controls such as two-factor authentication |
+| `compute` | Compute includes Linode instances and their workload configuration |
+| `networking` | Networking includes Cloud Firewalls and their stateful network rules |
diff --git a/docs/user-guide/providers/microsoft365/getting-started-m365.mdx b/docs/user-guide/providers/microsoft365/getting-started-m365.mdx
index a21b796b5c..fd791cbbca 100644
--- a/docs/user-guide/providers/microsoft365/getting-started-m365.mdx
+++ b/docs/user-guide/providers/microsoft365/getting-started-m365.mdx
@@ -41,7 +41,7 @@ Set up authentication for Microsoft 365 with the [Microsoft 365 Authentication](
### Step 2: Open Prowler Cloud
-1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app).
+1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
2. Navigate to "Configuration" > "Providers".
diff --git a/docs/user-guide/providers/mongodbatlas/getting-started-mongodbatlas.mdx b/docs/user-guide/providers/mongodbatlas/getting-started-mongodbatlas.mdx
index c68bfac9c2..2fb415a11b 100644
--- a/docs/user-guide/providers/mongodbatlas/getting-started-mongodbatlas.mdx
+++ b/docs/user-guide/providers/mongodbatlas/getting-started-mongodbatlas.mdx
@@ -15,12 +15,12 @@ Before you begin, make sure you have:
3. An **API Key pair** (public and private keys) with appropriate permissions:
- **Organization Read Only**: Provides read-only access to everything in the organization, including all projects in the organization. This permission is sufficient for most security checks.
- **Organization Owner**: Required to audit the [Auditing configuration](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/group/endpoint-auditing) for projects. Database auditing tracks database operations and security events, including authentication attempts, data definition language (DDL) changes, user and role modifications, and privilege grants. This configuration is essential for security monitoring, forensics, and compliance. Without **Organization Owner** permission, the `projects_auditing_enabled` check cannot retrieve the audit configuration status.
-4. Prowler App access (cloud or self-hosted) or the Prowler CLI (`pip install prowler`).
+4. Access to Prowler Cloud or Prowler Local Server, or Prowler CLI (`pip install prowler`).
For detailed instructions on creating API keys, see the [MongoDB Atlas authentication guide](./authentication.mdx).
<Warning>
-If **Require IP Access List for the Atlas Administration API** is enabled in your organization settings, you **must** add the IP address of the host running Prowler (or the public IP of Prowler Cloud) to the organization IP Access List or Atlas will reject every API call. You can manage this under **Settings → Organization Settings → Security**. See step 7 of the [authentication guide](./authentication.mdx) for detailed instructions, and refer to the [Prowler Cloud public IP list](../../tutorials/prowler-cloud-public-ips) when using Prowler Cloud.
+If **Require IP Access List for the Atlas Administration API** is enabled in the organization settings, add the IP address of the host running Prowler (or the public IP of Prowler Cloud) to the organization IP Access List or Atlas will reject every API call. Manage this under **Settings → Organization Settings → Security**. See step 7 of the [authentication guide](./authentication.mdx) for detailed instructions, and refer to the [Prowler Cloud egress IPs](/security/networking) when using Prowler Cloud.
</Warning>
<CardGroup cols={2}>
@@ -53,7 +53,7 @@ If **Require IP Access List for the Atlas Administration API** is enabled in you
### Step 3: Test the connection and start scanning
-1. Click **Test connection** to ensure Prowler App can reach the Atlas API.
+1. Click **Test connection** to ensure Prowler Cloud can reach the Atlas API.
2. Save the credentials. The provider will appear in the list with its current connection status.
3. Launch a scan from the provider row or from the **Scans** page.
@@ -108,6 +108,6 @@ prowler mongodbatlas --atlas-project-id <project-id>
- Combine flags (for example, `--checks` or `--services`) just like with other providers.
- Use `--output-modes` to export findings in JSON, CSV, ASFF, etc.
-- Rotate API keys regularly and update the stored credentials in Prowler App to maintain connectivity.
+- Rotate API keys regularly and update the stored credentials in Prowler Cloud to maintain connectivity.
For more examples (filters, outputs, scheduling), refer back to the [MongoDB Atlas documentation hub](./authentication.mdx) and the main Prowler CLI usage guide.
diff --git a/docs/user-guide/providers/oci/authentication.mdx b/docs/user-guide/providers/oci/authentication.mdx
index f977a80eb2..cc0e75cded 100644
--- a/docs/user-guide/providers/oci/authentication.mdx
+++ b/docs/user-guide/providers/oci/authentication.mdx
@@ -55,7 +55,7 @@ After running `oci session authenticate`, you need to manually add your user OCI
**Get your user OCID from the OCI Console:**
-Navigate to: **Identity & Security** → **Users** → Click on your username → Copy the OCID
+Navigate to: **Identity & Security** → **Users** → Click your username → Copy the OCID
@@ -434,7 +434,7 @@ prowler oci --oci-config-file /path/to/config
**Cause**: Insufficient IAM permissions
-**Solution**: Add required policies (see [Required Permissions](./getting-started-oci.md#required-permissions))
+**Solution**: Add required policies (see [Required Permissions](/user-guide/providers/oci/getting-started-oci#required-permissions))
### Configuration Validation
diff --git a/docs/user-guide/providers/oci/getting-started-oci.mdx b/docs/user-guide/providers/oci/getting-started-oci.mdx
index fc9fb620bf..6a8c8de3e9 100644
--- a/docs/user-guide/providers/oci/getting-started-oci.mdx
+++ b/docs/user-guide/providers/oci/getting-started-oci.mdx
@@ -6,7 +6,7 @@ Prowler supports security scanning of Oracle Cloud Infrastructure (OCI) environm
## Prowler Cloud
-The following steps apply to Prowler Cloud and the self-hosted Prowler App.
+The following steps apply to Prowler Cloud and Prowler Local Server.
### Step 1: Collect OCI Identifiers
1. Sign in to the [OCI Console](https://cloud.oracle.com/) and open **Tenancy Details** to copy the Tenancy OCID.
@@ -15,14 +15,14 @@ The following steps apply to Prowler Cloud and the self-hosted Prowler App.
4. Note the **Region** identifier to scan (for example, `us-ashburn-1`).
### Step 2: Access Prowler Cloud
-1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app).
+1. Navigate to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
2. Go to **Configuration** → **Providers** and click **Add Provider**.
3. Select **Oracle Cloud** and enter the **Tenancy OCID** and an optional alias, then choose **Next**.
### Step 3: Add OCI API Key Credentials
-Prowler App connects to OCI with API key credentials. Provide:
+Prowler Cloud connects to OCI with API key credentials. Provide:
- **User OCID** for the API key owner
- **Fingerprint** of the API key
@@ -58,7 +58,7 @@ Before you begin, ensure you have:
### Authentication
-Prowler supports multiple authentication methods for OCI. For detailed authentication setup, see the [OCI Authentication Guide](./authentication).
+Prowler supports multiple authentication methods for OCI. For detailed authentication setup, see the [OCI Authentication Guide](/user-guide/providers/oci/authentication).
**Note:** OCI Session Authentication and Config File Authentication both use the same `~/.oci/config` file. The difference is how the config file is generated - automatically via browser (session auth) or manually with API keys.
@@ -78,7 +78,7 @@ The easiest and most secure method is using OCI session authentication, which au
**Get your user OCID from the OCI Console:**
- Navigate to: **Identity & Security** → **Users** → Click on your username → Copy the OCID
+ Navigate to: **Identity & Security** → **Users** → Click your username → Copy the OCID
@@ -107,7 +107,7 @@ The easiest and most secure method is using OCI session authentication, which au
#### Alternative: Manual API Key Setup
-If you prefer to manually generate API keys instead of using browser-based session authentication, see the detailed instructions in the [Authentication Guide](./authentication#config-file-authentication-manual-api-key-setup).
+If you prefer to manually generate API keys instead of using browser-based session authentication, see the detailed instructions in the [Authentication Guide](/user-guide/providers/oci/authentication#config-file-authentication-manual-api-key-setup).
**Note:** Both methods use the same `~/.oci/config` file - the difference is that manual setup uses static API keys while session authentication uses temporary session tokens.
diff --git a/docs/user-guide/providers/okta/authentication.mdx b/docs/user-guide/providers/okta/authentication.mdx
index a30bae3810..8f664160a2 100644
--- a/docs/user-guide/providers/okta/authentication.mdx
+++ b/docs/user-guide/providers/okta/authentication.mdx
@@ -20,7 +20,7 @@ Prowler authenticates to Okta as a **service application** using **OAuth 2.0 wit
| Method | Status | Use Case |
|---|---|---|
-| **OAuth 2.0 (private-key JWT)** | Supported | Production scans, CI/CD, Prowler App. |
+| **OAuth 2.0 (private-key JWT)** | Supported | Production scans, CI/CD, Prowler Cloud. |
The private-key JWT flow is the only supported authentication method in the initial release. The service application proves possession of a private key on every token request; Okta returns a short-lived access token, refreshed automatically by the SDK.
@@ -30,23 +30,65 @@ If a different authentication method is needed (SSWS API token, OAuth with user
### Required OAuth Scopes
-For the initial check (`signon_global_session_idle_timeout_15min`) only one scope is required:
+The bundled checks require the following read-only scopes:
- `okta.policies.read`
+- `okta.brands.read`
+- `okta.apps.read`
+- `okta.authenticators.read`
+- `okta.networkZones.read`
+- `okta.apiTokens.read`
+- `okta.roles.read`
+- `okta.groups.read`
+- `okta.logStreams.read`
+- `okta.idps.read`
-Additional scopes will be needed as more services and checks are added, this are the current ones needed:
+Additional scopes will be needed as more services and checks are added. These are the current ones needed:
| Scope | Used by |
|---|---|
-| `okta.policies.read` | Sign-on / password / authentication policies |
+| `okta.policies.read` | Sign-on, password, authentication, and `USER_LIFECYCLE` (Workflow > Automations) policies |
+| `okta.brands.read` | Sign-in page customizations (DOD Notice and Consent Banner check) |
+| `okta.apps.read` | First-party app settings (Okta Admin Console session), integrated app inventory, and the Authentication Policies bound to Okta applications |
+| `okta.authenticators.read` | Okta authenticator configuration, including Okta Verify and Smart Card IdP |
+| `okta.networkZones.read` | Network Zone inventory, anonymized-proxy blocklist checks, and API token Network Zone validation |
+| `okta.apiTokens.read` | API token metadata and token network conditions |
+| `okta.roles.read` | Admin role assignments for API token owners (both direct and group-inherited) |
+| `okta.groups.read` | Group memberships of API token owners, used to resolve admin roles inherited via group assignment (e.g. Super Admin granted through the default admin group) |
+| `okta.logStreams.read` | Log Stream configuration (`/api/v1/logStreams`) |
+| `okta.idps.read` | Identity Providers, including Smart Card (X509) IdPs (`/api/v1/idps`) |
### Required Admin Role
-The service application must be assigned the built-in **Read-Only Administrator** role.
+The service application must be assigned **one** of the following Okta admin roles:
-Okta's Management API enforces a two-layer authorization model: an OAuth **scope** decides which API endpoints the token can call, and an **admin role** decides whether the call returns data. With only a scope granted, the token mint succeeds but every read returns `403 Forbidden`. The Read-Only Administrator role is the minimum that lets the granted `okta.*.read` scopes actually return configuration data to Prowler's checks — without it, the credential probe at provider startup fails and the scan never gets to evaluate any check.
+- **Read-Only Administrator** — covers every `signon` check and runs `application_authentication_policy_network_zone_enforced` against the apps it can see. **Visibility caveat:** under Read-Only Administrator the `/api/v1/apps` endpoint returns only the apps the service application is itself assigned to — typically just the service app's own row (for example, `Prowler Scanner`). The check still produces a finding for that app, but the rest of the org's app inventory is invisible at this role level.
+- **Super Administrator** — required additionally to evaluate five application-service checks that target Okta's first-party apps (Okta Admin Console, Okta Dashboard). With Super Administrator, `application_authentication_policy_network_zone_enforced` also evaluates the full org-wide app inventory instead of the service-app-only slice.
-Read-Only Administrator is intentionally the narrowest role that satisfies this requirement and aligns with the least-privilege guidance in DISA STIG.
+Okta's Management API enforces a two-layer authorization model: an OAuth **scope** decides which API endpoints the token can call, and an **admin role** decides whether the call returns data. With only a scope granted, the token mint succeeds but every read returns `403 Forbidden`. Read-Only Administrator is the minimum role that lets the granted `okta.*.read` scopes return configuration data to Prowler's checks; without it, the credential probe at provider startup fails and the scan never gets to evaluate any check.
+
+#### When Super Administrator is required
+
+Four checks need to resolve the Authentication Policy bound to Okta's first-party apps (Okta Admin Console, Okta Dashboard) and depend on `/api/v1/apps` returning those system apps — which Okta restricts to Super Administrator:
+
+| Check | STIG |
+|---|---|
+| `application_admin_console_mfa_required` | V-273193 |
+| `application_admin_console_phishing_resistant_authentication` | V-273191 |
+| `application_dashboard_mfa_required` | V-273194 |
+| `application_dashboard_phishing_resistant_authentication` | V-273190 |
+
+Okta filters the first-party apps (`saasure`, `okta_enduser`) out of `/api/v1/apps` for every role below Super Administrator, so `okta.apps.read` alone is not enough. The `okta.apps.manageFirstPartyApps` permission exists only in the paid Okta Identity Governance role `ACCESS_REQUESTS_ADMIN` and cannot be added to custom roles ([Okta Permissions Catalog](https://developer.okta.com/docs/api/openapi/okta-management/guides/permissions)).
+
+A fifth check — `application_admin_console_session_idle_timeout_15min` (STIG V-273187) — also requires Super Administrator: it calls `GET /api/v1/first-party-app-settings/admin-console`, which returns `403 E0000006` for every role below Super Administrator.
+
+`user_inactivity_automation_35d_enabled` (STIG V-273188) reads `USER_LIFECYCLE` policies (`list_policies(type='USER_LIFECYCLE')`) using the `okta.policies.read` scope. The Read-Only Administrator role is enough to list them; no Super Administrator requirement.
+
+When the service app runs with Read-Only Administrator, the checks listed in this section return **MANUAL** instead of PASS/FAIL — the rest of the scan keeps running.
+
+<Note>
+Read-Only Administrator stays the recommended default for the least-privilege framing that aligns with DISA STIG. Assign Super Administrator on a separate run when full coverage of the first-party app checks is needed.
+</Note>
## Step-by-Step Setup
@@ -96,19 +138,21 @@ Okta displays the private key **only once**. If you close the modal without copy
### 5. Grant the required OAuth scopes
-On the app, open the **Okta API Scopes** tab and click **Grant** on every scope Prowler needs. For the initial release, granting only `okta.policies.read` is sufficient.
+On the app, open the **Okta API Scopes** tab and click **Grant** on every scope Prowler needs. The bundled checks require `okta.policies.read`, `okta.brands.read`, `okta.apps.read`, `okta.authenticators.read`, `okta.networkZones.read`, `okta.apiTokens.read`, `okta.roles.read`, `okta.groups.read`, `okta.logStreams.read`, and `okta.idps.read`.
-### 6. Assign the Read-Only Administrator role
+### 6. Assign an admin role
On the app, open the **Admin roles** tab and click **Edit assignments → Add assignment**:
-- **Role:** Read-Only Administrator
+- **Role:** Read-Only Administrator (default) — covers every `signon` check and runs the per-app network-zone check against the apps the service app can see (typically only the service app's own row).
- **Resources:** All resources
Save the changes.
+To additionally evaluate the first-party application checks (Okta Admin Console / Okta Dashboard idle timeout, MFA, and phishing-resistant authentication) and to widen the per-app network-zone check to the full org-wide app inventory, assign **Super Administrator** instead. Without Super Administrator, the five first-party checks return MANUAL and the network-zone check is limited to the service app's own visibility — the rest of the scan still runs. See [Required Admin Role](#required-admin-role) for the full breakdown.
+
### 7. [Optional] Verify DPoP setting
@@ -130,8 +174,8 @@ export OKTA_PRIVATE_KEY_FILE="/secure/path/to/prowler-okta.pem"
# or
export OKTA_PRIVATE_KEY="$(cat /secure/path/to/prowler-okta.pem)"
-# Optional — defaults to "okta.policies.read"
-export OKTA_SCOPES="okta.policies.read"
+# Optional — defaults to "okta.policies.read,okta.brands.read,okta.apps.read,okta.authenticators.read,okta.networkZones.read,okta.apiTokens.read,okta.roles.read,okta.groups.read,okta.logStreams.read,okta.idps.read"
+export OKTA_SCOPES="okta.policies.read,okta.brands.read,okta.apps.read,okta.authenticators.read,okta.networkZones.read,okta.apiTokens.read,okta.roles.read,okta.groups.read,okta.logStreams.read,okta.idps.read"
uv run python prowler-cli.py okta
```
@@ -172,8 +216,12 @@ Prowler validates credentials at startup by listing one sign-on policy. This err
Raised when the credential probe succeeds at the OAuth layer but the request is rejected because the service app lacks the required scope or admin role:
-- **`invalid_scope`** — the `okta.policies.read` scope is not granted on the service app. Grant it from **Okta API Scopes**.
-- **`Forbidden` / `not authorized`** — the **Read-Only Administrator** role is not assigned to the service app. Assign it from **Admin roles**.
+- **`invalid_scope`** — one of the requested scopes (`okta.policies.read`, `okta.brands.read`, `okta.apps.read`, `okta.authenticators.read`, `okta.networkZones.read`, `okta.apiTokens.read`, `okta.roles.read`, `okta.groups.read`, `okta.logStreams.read`, and `okta.idps.read`) is not granted on the service app. Grant the missing scope from **Okta API Scopes**.
+- **`Forbidden` / `not authorized`** — no admin role is assigned to the service app. Assign **Read-Only Administrator** (or **Super Administrator** for the first-party application checks) from **Admin roles**.
+
+### Application-service checks return MANUAL on first-party apps
+
+When the service app runs with Read-Only Administrator, the five application-service checks targeting the Okta Admin Console and Okta Dashboard return MANUAL. This is by design — Okta restricts the underlying endpoints (`/api/v1/first-party-app-settings/{appName}` and `/api/v1/apps` for first-party app `name` values `saasure` / `okta_enduser`) to **Super Administrator**. Assign the Super Administrator role to the service app to evaluate those checks. See [Required Admin Role](#required-admin-role) for the full list.
### `invalid_dpop_proof`
diff --git a/docs/user-guide/providers/okta/getting-started-okta.mdx b/docs/user-guide/providers/okta/getting-started-okta.mdx
index 6486736bd5..dbe63807d7 100644
--- a/docs/user-guide/providers/okta/getting-started-okta.mdx
+++ b/docs/user-guide/providers/okta/getting-started-okta.mdx
@@ -12,7 +12,7 @@ Set up authentication for Okta with the [Okta Authentication](/user-guide/provid
- An Okta organization. The UI examples below use **Identity Engine** terminology such as **Global Session Policy**; Classic Engine exposes the equivalent sign-on policy concepts under older names.
- A **Super Administrator** account on that organization for the one-time service-app setup.
-- An **API Services** app integration in the Okta Admin Console with the `okta.policies.read` scope granted and the **Read-Only Administrator** role assigned.
+- An **API Services** app integration in the Okta Admin Console with the `okta.policies.read`, `okta.brands.read`, `okta.apps.read`, `okta.authenticators.read`, `okta.networkZones.read`, `okta.apiTokens.read`, `okta.roles.read`, `okta.groups.read`, `okta.logStreams.read`, and `okta.idps.read` scopes granted and an admin role assigned. **Read-Only Administrator** covers the Sign-On, Network, API Token, User, System Log, and Identity Provider checks, and runs the per-app application network-zone check against the apps the service app can see (under Read-Only Administrator that is typically only the service app's own row — the rest of the org's app inventory stays invisible). **Super Administrator** is required additionally to evaluate the five first-party application checks (Okta Admin Console / Okta Dashboard idle timeout, MFA, phishing-resistant authentication) and to widen the application network-zone check to the full app inventory — see [Okta Authentication](/user-guide/providers/okta/authentication#required-admin-role) for the full breakdown.
- Python 3.10+ and Prowler 5.27.0 or later installed locally.
<CardGroup cols={2}>
@@ -26,10 +26,51 @@ Set up authentication for Okta with the [Okta Authentication](/user-guide/provid
## Prowler Cloud
+<VersionBadge version="5.28.0" />
+
+### Step 1: Add the Provider
+
+1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
+2. Navigate to "Configuration" > "Providers".
+
+ 
+
+3. Click "Add Provider".
+
+ 
+
+4. Select "Okta".
+
+ 
+
+5. Enter the **Org Domain** of the target Okta organization and an optional alias, then click "Next".
+
+ 
+
<Note>
-Prowler Cloud onboarding for Okta is coming soon. Track the [Prowler GitHub repository](https://github.com/prowler-cloud/prowler) for release updates. Use the [Prowler CLI](#prowler-cli) workflow below in the meantime.
+The Org Domain must be the bare hostname of an Okta-managed organization — for example, `acme.okta.com`, `acme.oktapreview.com`, `acme.okta-emea.com`, `acme.okta-gov.com`, `acme.okta.mil`, `acme.okta-miltest.com`, or `acme.trex-govcloud.com`. Omit the `https://` scheme, any path, and any trailing slash.
</Note>
+### Step 2: Provide Credentials
+
+Prowler Cloud authenticates to Okta with the **OAuth 2.0 Private Key JWT** flow exposed by an Okta **API Services** app. The service application, keypair, scope grants, and Read-Only Administrator role are set up once in the Okta Admin Console — full instructions are in the [Okta Authentication](/user-guide/providers/okta/authentication) guide.
+
+1. Enter the **Client ID** of the Okta API Services app (for example, `0oa123456789abcdef`).
+2. Paste the **Private Key** whose matching public key (JWK) is registered on the service app. Both PEM-encoded RSA keys and JWK JSON documents are accepted.
+3. Click "Next".
+
+ 
+
+<Note>
+The private key is transmitted over TLS and stored as an encrypted secret in the backend. Rotate or revoke the matching public key from the Okta Admin Console at any time to invalidate the credential without changes on the Prowler side.
+</Note>
+
+### Step 3: Launch the Scan
+
+1. Review the connection summary. Prowler Cloud runs a credential probe against the Okta Management API before saving — a failed probe surfaces the underlying Okta error (`invalid_scope`, `Forbidden`, invalid credentials, etc.) so the configuration can be corrected before the first scan.
+2. Choose the scan schedule: run a single scan or set up daily scans (every 24 hours).
+3. Click **Launch Scan** to start auditing the Okta organization.
+
---
## Prowler CLI
@@ -44,8 +85,8 @@ Follow the [Okta Authentication](/user-guide/providers/okta/authentication) guid
export OKTA_ORG_DOMAIN="acme.okta.com"
export OKTA_CLIENT_ID="0oa1234567890abcdef"
export OKTA_PRIVATE_KEY_FILE="/secure/path/to/prowler-okta.pem"
-# Optional — defaults to "okta.policies.read"
-export OKTA_SCOPES="okta.policies.read"
+# Optional — defaults to "okta.policies.read,okta.brands.read,okta.apps.read,okta.authenticators.read,okta.networkZones.read,okta.apiTokens.read,okta.roles.read,okta.groups.read,okta.logStreams.read,okta.idps.read"
+export OKTA_SCOPES="okta.policies.read,okta.brands.read,okta.apps.read,okta.authenticators.read,okta.networkZones.read,okta.apiTokens.read,okta.roles.read,okta.groups.read,okta.logStreams.read,okta.idps.read"
```
The private key file may contain either a PEM-encoded RSA key or a JWK JSON document.
@@ -87,6 +128,9 @@ okta:
# okta.signon_global_session_idle_timeout_15min
# Defaults to 15 minutes per DISA STIG V-273186.
okta_max_session_idle_minutes: 15
+ # okta.application_admin_console_session_idle_timeout_15min
+ # Defaults to 15 minutes per DISA STIG V-273187.
+ okta_admin_console_idle_timeout_max_minutes: 15
```
To use a custom configuration:
@@ -99,9 +143,16 @@ prowler okta --config-file /path/to/config.yaml
Prowler for Okta includes security checks across the following services:
-| Service | Description |
-| ----------- | ----------------------------------------------------------------------------------- |
-| **Sign-On** | Global session policy controls (idle timeout, lifetime, rule priority and ordering) |
+| Service | Description |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Sign-On** | Global session policy controls (idle timeout, lifetime, rule priority and ordering) |
+| **Application** | Okta Admin Console sign-on settings plus Authentication Policy controls for Okta applications (session idle, MFA, phishing resistance, network zones) |
+| **Authenticator** | Password Policy controls plus Okta Verify FIPS and Smart Card IdP authenticator status |
+| **Network** | Network Zone blocklists for anonymized proxy sources |
+| **API Token** | API token owner-role validation and Network Zone restrictions |
+| **User** | User lifecycle automations (inactivity-based deprovisioning) |
+| **System Log** | Log Stream configuration that off-loads audit records to a central SIEM |
+| **Identity Provider** | Identity Providers, including Smart Card (X509) IdP status and certificate-chain visibility |
## Troubleshooting
@@ -113,20 +164,29 @@ This is stricter than simply finding the same timeout value somewhere else in th
### Default Scopes
-Prowler requests a fixed set of OAuth scopes on every token exchange. The default is a single scope that covers the bundled initial check:
+Prowler requests a fixed set of OAuth scopes on every token exchange. The defaults cover every bundled check across the Sign-On, Application, Authenticator, Network, API Token, User, System Log, and Identity Provider services:
- `okta.policies.read`
+- `okta.brands.read`
+- `okta.apps.read`
+- `okta.authenticators.read`
+- `okta.networkZones.read`
+- `okta.apiTokens.read`
+- `okta.roles.read`
+- `okta.groups.read`
+- `okta.logStreams.read`
+- `okta.idps.read`
-The service app must have that scope granted in the **Okta API Scopes** tab. When the granted set is narrower than the requested set, the token request fails with an `invalid_scope` error and the scan stops at provider initialization.
+The service app must have these scopes granted in the **Okta API Scopes** tab. `okta.groups.read` is required so the API token Super Admin check can resolve admin roles inherited via group membership; without it the check falls back to direct-only role assignments and emits a best-effort caveat. When the granted set is narrower than the requested set, the token request fails with an `invalid_scope` error and the scan stops at provider initialization.
When additional checks are enabled — or when running against a service app that exposes a different scope set — override the default with `OKTA_SCOPES` (comma-separated string for the env var) or `--okta-scopes` (space-separated list for the CLI):
```bash
# Environment variable — comma-separated
-export OKTA_SCOPES="okta.policies.read,okta.apps.read,okta.users.read"
+export OKTA_SCOPES="okta.policies.read,okta.brands.read,okta.apps.read,okta.authenticators.read,okta.networkZones.read,okta.apiTokens.read,okta.roles.read,okta.groups.read,okta.logStreams.read,okta.idps.read,okta.users.read"
# CLI flag — space-separated
-prowler okta --okta-scopes okta.policies.read okta.apps.read okta.users.read
+prowler okta --okta-scopes okta.policies.read okta.brands.read okta.apps.read okta.authenticators.read okta.networkZones.read okta.apiTokens.read okta.roles.read okta.groups.read okta.logStreams.read okta.idps.read okta.users.read
```
For the full catalog of OAuth scopes exposed by the Okta Management API, refer to the [Okta OAuth 2.0 scopes documentation](https://developer.okta.com/docs/api/oauth2/).
diff --git a/docs/user-guide/providers/okta/images/okta-credentials-form.png b/docs/user-guide/providers/okta/images/okta-credentials-form.png
new file mode 100644
index 0000000000..c37553c59d
Binary files /dev/null and b/docs/user-guide/providers/okta/images/okta-credentials-form.png differ
diff --git a/docs/user-guide/providers/okta/images/okta-org-domain-form.png b/docs/user-guide/providers/okta/images/okta-org-domain-form.png
new file mode 100644
index 0000000000..fb145d2877
Binary files /dev/null and b/docs/user-guide/providers/okta/images/okta-org-domain-form.png differ
diff --git a/docs/user-guide/providers/okta/images/select-okta-provider.png b/docs/user-guide/providers/okta/images/select-okta-provider.png
new file mode 100644
index 0000000000..1a854bab37
Binary files /dev/null and b/docs/user-guide/providers/okta/images/select-okta-provider.png differ
diff --git a/docs/user-guide/providers/okta/retry-configuration.mdx b/docs/user-guide/providers/okta/retry-configuration.mdx
new file mode 100644
index 0000000000..1575cf6329
--- /dev/null
+++ b/docs/user-guide/providers/okta/retry-configuration.mdx
@@ -0,0 +1,123 @@
+---
+title: "Okta Rate Limit Configuration in Prowler"
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+
+<VersionBadge version="5.32.0" />
+
+Prowler's Okta Provider manages API rate limits with two complementary controls:
+
+- **Request throttling (proactive):** Prowler paces outbound requests through a shared limiter so scans stay under Okta's rate limits and rarely trigger a rate-limit response in the first place.
+- **Retries (reactive):** When Okta still returns a rate-limit response (HTTP 429), the official Okta Python SDK reads the `X-Rate-Limit-Reset` header and waits until the window resets before retrying. This acts as a safety net for occasional bursts.
+
+Both controls are configurable through the configuration file or command line flags.
+
+## Request Throttling (Requests per Second)
+
+Throttling is the primary control for avoiding rate limits. Prowler limits the aggregate number of Okta API requests per second across every service in a scan.
+
+### Using the Command Line Flag
+
+```bash
+prowler okta --okta-requests-per-second 4
+```
+
+Set the value to `0` to disable throttling.
+
+### Using the Configuration File
+
+```yaml
+okta:
+ # Maximum aggregate Okta API requests per second. Default: 4. Set to 0 to disable.
+ okta_requests_per_second: 4
+```
+
+Okta enforces rate limits per endpoint, so this single global cap is a deliberately simple control. Lower the value if scans still hit limits on large organizations; raise it to scan faster when the organization has generous limits.
+
+## Retries
+
+Retries cover the cases throttling does not prevent, such as short bursts or per-endpoint limits lower than the global cap.
+
+### Using the Command Line Flag
+
+```bash
+prowler okta --okta-retries-max-attempts 8
+```
+
+### Using the Configuration File
+
+```yaml
+okta:
+ # Maximum retries on HTTP 429. Default: 5.
+ okta_max_retries: 8
+ # Per-request timeout in seconds. Default: 300.
+ okta_request_timeout: 300
+```
+
+The command line flags override the configuration file values.
+
+## How It Works
+
+- **Automatic detection:** The Okta SDK retries the retryable statuses 429, 503, and 504.
+- **Reset-aware backoff:** On a 429 response the SDK sleeps until the `X-Rate-Limit-Reset` window before each retry, rather than using a fixed delay.
+- **Bounded attempts:** `okta_max_retries` caps how many times a single request is retried. The Okta SDK default is 2, which is often too low for large organizations, so Prowler defaults to 5.
+
+## Request Timeout
+
+The `okta_request_timeout` setting plays a dual role in the Okta SDK:
+
+- It is the per-request socket timeout, bounding how long a single HTTP call can hang.
+- It is also the total wall-clock budget for the whole retry-and-backoff loop of one request.
+
+For this reason, the value defaults to 300 seconds rather than 0 (no timeout). A value of 0 leaves hung connections unbounded, while a value that is too low cuts the rate-limit waits short and reintroduces the errors. As a guideline, keep `okta_request_timeout` greater than or equal to `okta_max_retries` multiplied by 60 when raising the retry count, because Okta reset windows are typically up to one minute.
+
+## Error Example Handled
+
+```
+Okta HTTP 429: Too Many Requests. Hit rate limit. Retry request in 42 seconds.
+```
+
+## Validation
+
+### Debug Logging
+
+To confirm that throttling and retries are active, run a scan with debug logging:
+
+```bash
+prowler okta --okta-requests-per-second 4 --log-level DEBUG --log-file debuglogs.txt
+```
+
+### Check the Messages
+
+```bash
+grep -i "throttling\|rate limit\|retry" debuglogs.txt
+```
+
+### Expected Output
+
+When throttling is enabled, Prowler logs the configured rate at startup:
+
+```
+Okta request throttling enabled at 4 req/s
+```
+
+If a rate limit is still hit, the SDK logs the backoff:
+
+```
+Hit rate limit. Retry request in 42 seconds.
+```
+
+## Troubleshooting
+
+If scans continue to hit rate limits:
+
+1. Lower `--okta-requests-per-second` so requests are paced more conservatively.
+2. Raise `--okta-retries-max-attempts` (and keep `okta_request_timeout` proportionally large) so the safety net absorbs more bursts.
+3. Review the rate-limit allocation for the Okta organization and request an increase if needed.
+4. Verify throttling and retry behavior with debug logging.
+
+## Official References
+
+- [Okta Rate Limits](https://developer.okta.com/docs/reference/rate-limits/)
+- [Okta SDK for Python](https://github.com/okta/okta-sdk-python)
diff --git a/docs/user-guide/providers/stackit/authentication.mdx b/docs/user-guide/providers/stackit/authentication.mdx
new file mode 100644
index 0000000000..dabc407c50
--- /dev/null
+++ b/docs/user-guide/providers/stackit/authentication.mdx
@@ -0,0 +1,100 @@
+---
+title: 'StackIT Authentication'
+---
+
+Prowler authenticates with StackIT using a **service account key file**. The StackIT SDK signs the RSA challenge in the key file and mints/refreshes access tokens internally for the life of the scan, so no manual token rotation is needed.
+
+## Service Account Key
+
+StackIT uses RSA key-pair based service account keys. They are issued once, must be stored securely, and are read by the SDK on every scan to mint short-lived access tokens transparently.
+
+### Option 1: Create the Key via the StackIT Portal
+
+1. Open the [StackIT Portal](https://portal.stackit.cloud/) and select your project.
+2. In the left sidebar, click **Service Accounts**.
+3. Create a service account if you do not have one already. Assign:
+ - `iaas.viewer` for the IaaS security group checks currently shipped, or
+ - `project.owner` if you want to cover any future service Prowler adds.
+4. Open the service account and go to **Service Account Keys**.
+5. Click **Create key** and choose **STACKIT-generated key pair** (recommended). Download the resulting JSON file and store it securely (for example, `~/.stackit/sa-key.json`). The private material is only shown once.
+
+### Option 2: Create the Key via the StackIT CLI
+
+```bash
+# Install the StackIT CLI from https://github.com/stackitcloud/stackit-cli first
+stackit service-account key create --email my-service-account@example.com
+```
+
+## Project ID
+
+Your StackIT project ID is a UUID. You can find it in:
+
+1. The portal URL when viewing the project: `https://portal.stackit.cloud/projects/{PROJECT_ID}/...`
+2. The project settings page
+3. `stackit project list`
+
+## Passing Credentials to Prowler
+
+You can give Prowler either the **path** to the key file on disk or the **inline JSON content** of the key. Both go through the same StackIT SDK flow and refresh access tokens internally.
+
+### Option A: Key File Path (workstation, persistent agents)
+
+Recommended when the key is stored on disk.
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+
+prowler stackit
+```
+
+Or as CLI flags:
+
+```bash
+prowler stackit \
+ --stackit-service-account-key-path ~/.stackit/sa-key.json \
+ --stackit-project-id 12345678-1234-1234-1234-123456789abc
+```
+
+<Note>
+Keep the key file outside of source control and lock it down with `chmod 600 ~/.stackit/sa-key.json`. Anyone with the JSON can mint access tokens for the service account.
+</Note>
+
+### Option B: Inline Key Content (CI/CD, secret managers)
+
+Recommended when the key is fetched at run time from a secret manager (GitHub Actions secret, AWS Secrets Manager, HashiCorp Vault, etc.) and you do not want to write it to disk.
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY="$(vault kv get -field=key stackit/sa)"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+
+prowler stackit
+```
+
+<Note>
+Prefer the `STACKIT_SERVICE_ACCOUNT_KEY` environment variable over the matching CLI flag (`--stackit-service-account-key`); passing the secret on the command line leaks it through process listings and shell history.
+</Note>
+
+When both the inline content and a key path are set, the inline content wins.
+
+## Credential Lookup Order
+
+Prowler resolves credentials in this order:
+
+1. CLI arguments: `--stackit-service-account-key`, `--stackit-service-account-key-path`, `--stackit-project-id`
+2. Environment variables: `STACKIT_SERVICE_ACCOUNT_KEY`, `STACKIT_SERVICE_ACCOUNT_KEY_PATH`, `STACKIT_PROJECT_ID`
+
+When both the inline key and the key file path are set, the inline content takes precedence.
+
+## Token Lifetime
+
+Access tokens are minted on demand by the SDK from the key file and refreshed before they expire. There is nothing to rotate while Prowler is running.
+
+## Troubleshooting
+
+| Symptom | Likely Cause | Fix |
+|---------|--------------|-----|
+| `401 Unauthorized` during scan | Key file is missing fields, the public key is no longer registered, or the key was revoked | Re-issue the service account key in the StackIT portal and update `STACKIT_SERVICE_ACCOUNT_KEY_PATH` |
+| `403 Forbidden` during scan | Service account lacks role on the project | Re-check role assignment in the StackIT portal; `iaas.viewer` is the minimum for the shipped IaaS checks |
+| `StackIT project ID must be a valid UUID` | The project ID is not in UUID format | Copy the UUID from the portal URL or `stackit project list` |
+| `StackIT service account credentials are required` | None of the four credential inputs is set | Export `STACKIT_SERVICE_ACCOUNT_KEY_PATH` or `STACKIT_SERVICE_ACCOUNT_KEY` (or use their CLI counterparts) before running Prowler |
diff --git a/docs/user-guide/providers/stackit/getting-started-stackit.mdx b/docs/user-guide/providers/stackit/getting-started-stackit.mdx
new file mode 100644
index 0000000000..6c56008a89
--- /dev/null
+++ b/docs/user-guide/providers/stackit/getting-started-stackit.mdx
@@ -0,0 +1,141 @@
+---
+title: 'Getting Started With StackIT'
+---
+
+Prowler supports [StackIT](https://www.stackit.de/) from the CLI. This guide walks you through the requirements and how to run scans.
+
+<Note>
+StackIT support in Prowler is community-maintained. For commercial support or to request additional service coverage, [contact us](https://prowler.com/contact).
+</Note>
+
+## Prerequisites
+
+Before running Prowler with the StackIT provider, ensure you have:
+
+1. A StackIT account with at least one project
+2. A StackIT service account key file with permissions on the project (`iaas.viewer` is enough for the currently shipped IaaS checks; `project.owner` works for any future service). See the [Authentication guide](/user-guide/providers/stackit/authentication) for the full setup.
+3. Access to Prowler CLI (see [Installation](/getting-started/installation/prowler-cli))
+
+## Prowler CLI
+
+### Step 1: Point Prowler at the Service Account Key
+
+Prowler authenticates with a StackIT service account key. The SDK signs the RSA challenge in the key and refreshes access tokens internally for the life of the scan, so there is no manual token rotation.
+
+**On a workstation or persistent agent** (key on disk):
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY_PATH="$HOME/.stackit/sa-key.json"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+```
+
+**In CI/CD** (key in a secret manager, never written to disk):
+
+```bash
+export STACKIT_SERVICE_ACCOUNT_KEY="$(vault kv get -field=key stackit/sa)"
+export STACKIT_PROJECT_ID="12345678-1234-1234-1234-123456789abc"
+```
+
+CLI flags work too:
+
+```bash
+prowler stackit \
+ --stackit-service-account-key-path ~/.stackit/sa-key.json \
+ --stackit-project-id 12345678-1234-1234-1234-123456789abc
+```
+
+<Note>
+For the inline key, prefer the `STACKIT_SERVICE_ACCOUNT_KEY` env var over the matching CLI flag; passing the secret on the command line leaks it through process listings and shell history.
+
+Keep the key file outside of source control and lock it down with `chmod 600 ~/.stackit/sa-key.json`. Anyone with the JSON can mint access tokens for the service account.
+</Note>
+
+### Step 2: Run Your First Scan
+
+```bash
+prowler stackit
+```
+
+Prowler will discover and audit the project's IaaS security groups across the available StackIT regions.
+
+**Scan specific regions:**
+
+```bash
+prowler stackit --stackit-region eu01 eu02
+```
+
+**Run specific security checks:**
+
+```bash
+prowler stackit --checks iaas_security_group_ssh_unrestricted
+
+# List all available checks
+prowler stackit --list-checks
+```
+
+**Filter by check severity:**
+
+```bash
+prowler stackit --severity critical high
+```
+
+**Generate specific output formats:**
+
+```bash
+# JSON only
+prowler stackit --output-modes json
+
+# CSV and HTML
+prowler stackit --output-modes csv html
+
+# Custom output directory
+prowler stackit --output-directory /path/to/reports/
+```
+
+**Use a mutelist to suppress findings:**
+
+```yaml
+# mutelist.yaml
+Mutelist:
+ Accounts:
+ "12345678-1234-1234-1234-123456789abc":
+ Checks:
+ iaas_security_group_ssh_unrestricted:
+ Regions:
+ - "*"
+ Resources:
+ - "test-sg-id"
+ Tags: []
+```
+
+```bash
+prowler stackit --mutelist-file mutelist.yaml
+```
+
+### Step 3: Review the Results
+
+Prowler outputs findings to the console and writes reports to the `output/` directory by default:
+
+- CSV: `output/prowler-output-stackit-{project_id}-{timestamp}.csv`
+- JSON: `output/prowler-output-stackit-{project_id}-{timestamp}.json`
+- HTML: `output/prowler-output-stackit-{project_id}-{timestamp}.html`
+
+## Supported StackIT Services
+
+| Service | StackIT API | Description | Example Checks |
+|---------|-------------|-------------|----------------|
+| **IaaS** | `iaas` | Virtual machines, network interfaces, security groups | `iaas_security_group_ssh_unrestricted`, `iaas_security_group_rdp_unrestricted`, `iaas_security_group_database_unrestricted`, `iaas_security_group_all_traffic_unrestricted` |
+
+Additional services will be added in future releases. Track progress in the [Prowler release notes](https://github.com/prowler-cloud/prowler/releases).
+
+## Troubleshooting
+
+### Authentication Errors
+
+If the scan fails with a 401 error, the service account key is no longer valid (revoked, rotated or the key file is incomplete). Re-issue the key in the [StackIT portal](https://portal.stackit.cloud/) and update `STACKIT_SERVICE_ACCOUNT_KEY_PATH`.
+
+### Permission Errors
+
+If checks fail with a 403 error, the service account is missing the required role on the project. Re-check the role assignment in the StackIT portal (`iaas.viewer` is the minimum for the shipped IaaS checks).
+
+For detailed setup steps, see the [Authentication guide](/user-guide/providers/stackit/authentication).
diff --git a/docs/user-guide/providers/vercel/getting-started-vercel.mdx b/docs/user-guide/providers/vercel/getting-started-vercel.mdx
index c39c5f1e6a..da02019b6f 100644
--- a/docs/user-guide/providers/vercel/getting-started-vercel.mdx
+++ b/docs/user-guide/providers/vercel/getting-started-vercel.mdx
@@ -28,7 +28,7 @@ Set up authentication for Vercel with the [Vercel Authentication](/user-guide/pr
### Step 1: Add the Provider
-1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler App](/user-guide/tutorials/prowler-app).
+1. Go to [Prowler Cloud](https://cloud.prowler.com/) or launch [Prowler Local Server](/user-guide/tutorials/prowler-app).
2. Navigate to "Configuration" > "Providers".
diff --git a/docs/user-guide/tutorials/aws-organizations-bulk-provisioning.mdx b/docs/user-guide/tutorials/aws-organizations-bulk-provisioning.mdx
index 88a084dd17..188ac3540d 100644
--- a/docs/user-guide/tutorials/aws-organizations-bulk-provisioning.mdx
+++ b/docs/user-guide/tutorials/aws-organizations-bulk-provisioning.mdx
@@ -9,9 +9,9 @@ The tool, `aws_org_generator.py`, complements the [Bulk Provider Provisioning
<Note>
**Native AWS Organizations support is now available in Prowler Cloud.** You can onboard all accounts via the UI wizard — with automatic discovery, hierarchical tree selection, connection testing, and bulk scan launch — without any scripts or YAML files.
-See [AWS Organizations in Prowler Cloud](/user-guide/tutorials/prowler-cloud-aws-organizations).
+See [AWS Organizations](/user-guide/tutorials/prowler-cloud-aws-organizations) in Prowler Cloud.
-The CLI-based tool below remains useful for self-hosted Prowler App and advanced automation scenarios.
+The CLI-based tool below remains useful for Prowler Local Server and advanced automation scenarios.
</Note>
{/* TODO: Add screenshot of the tool in action */}
@@ -32,9 +32,9 @@ The AWS Organizations Bulk Provisioning tool simplifies multi-account onboarding
* Python 3.7 or higher
* AWS credentials with Organizations read access
* ProwlerRole (or custom role) deployed across all target accounts
-* Prowler API key (from Prowler Cloud or self-hosted Prowler App)
- * For self-hosted Prowler App, remember to [point to your API base URL](./bulk-provider-provisioning#custom-api-endpoints)
- * Learn how to create API keys: [Prowler App API Keys](../tutorials/prowler-app-api-keys)
+* Prowler API key (from Prowler Cloud or Prowler Local Server)
+ * For Prowler Local Server, remember to [point to your API base URL](./bulk-provider-provisioning#custom-api-endpoints)
+ * Learn how to create API keys: [Prowler Cloud API Keys](../tutorials/prowler-app-api-keys)
### Deploying ProwlerRole Across AWS Organizations
@@ -97,13 +97,13 @@ export PROWLER_API_KEY="pk_example-api-key"
To create an API key:
-1. Log in to Prowler Cloud or Prowler App
+1. Log in to Prowler Cloud or Prowler Local Server
2. Click **Profile** → **Account**
3. Click **Create API Key**
4. Provide a descriptive name and optionally set an expiration date
5. Copy the generated API key (it will only be shown once)
-For detailed instructions, see: [Prowler App API Keys](../tutorials/prowler-app-api-keys)
+For detailed instructions, see: [Prowler Cloud API Keys](../tutorials/prowler-app-api-keys)
## Basic Usage
@@ -272,6 +272,8 @@ python aws_org_generator.py \
4. Deploy to all organizational units
5. Use a unique external ID (e.g., `prowler-org-2024-abc123`)
+ Alternatively, deploy the same template as a **single stack** with `DeployStackSet=true` and `AWSOrganizationalUnitId` set to your root/OU ID — it creates the StackSet for you. See [Native CloudFormation StackSet Deployment](../providers/aws/organizations#native-cloudformation-stackset-deployment-recommended).
+
{/* TODO: Add screenshot of CloudFormation StackSets deployment */}
</Step>
@@ -324,7 +326,7 @@ python aws_org_generator.py \
</Step>
<Step title="Run Bulk Provisioning">
- Provision all accounts to Prowler Cloud or Prowler App:
+ Provision all accounts to Prowler Cloud or Prowler Local Server:
```bash
# Set Prowler API key
@@ -487,7 +489,7 @@ grep "provider: aws" aws-org-accounts.yaml | wc -l
<Card title="Bulk Provider Provisioning" icon="terminal" href="/user-guide/tutorials/bulk-provider-provisioning">
Learn how to bulk provision providers in Prowler.
</Card>
- <Card title="Prowler App" icon="pen-to-square" href="/user-guide/tutorials/prowler-app">
+ <Card title="Prowler Cloud" icon="pen-to-square" href="/user-guide/tutorials/prowler-app">
Detailed instructions on how to use Prowler.
</Card>
</Columns>
diff --git a/docs/user-guide/tutorials/bulk-provider-provisioning.mdx b/docs/user-guide/tutorials/bulk-provider-provisioning.mdx
index 3ad5d9c0d5..cc759b6f85 100644
--- a/docs/user-guide/tutorials/bulk-provider-provisioning.mdx
+++ b/docs/user-guide/tutorials/bulk-provider-provisioning.mdx
@@ -10,7 +10,7 @@ The tool is available in the Prowler repository at: [util/prowler-bulk-provision
## Overview
-The Bulk Provider Provisioning tool automates the creation of cloud providers in Prowler App or Prowler Cloud by:
+The Bulk Provider Provisioning tool automates the creation of cloud providers in Prowler Cloud or Prowler Local Server by:
* Reading provider configurations from YAML files
* Creating providers with appropriate authentication credentials
@@ -26,9 +26,9 @@ The Bulk Provider Provisioning tool automates the creation of cloud providers in
### Requirements
* Python 3.7 or higher
-* Prowler API key (from Prowler Cloud or self-hosted Prowler App)
- * For self-hosted Prowler App, remember to [point to your API base URL](#custom-api-endpoints)
- * Learn how to create API keys: [Prowler App API Keys](../tutorials/prowler-app-api-keys)
+* Prowler API key (from Prowler Cloud or Prowler Local Server)
+ * For Prowler Local Server, remember to [point to your API base URL](#custom-api-endpoints)
+ * Learn how to create API keys: [Prowler Cloud API Keys](../tutorials/prowler-app-api-keys)
* Authentication credentials for target cloud providers
### Installation
@@ -51,13 +51,13 @@ export PROWLER_API_KEY="pk_example-api-key"
To create an API key:
-1. Log in to Prowler Cloud or Prowler App
+1. Log in to Prowler Cloud or Prowler Local Server
2. Click **Profile** → **Account**
3. Click **Create API Key**
4. Provide a descriptive name and optionally set an expiration date
5. Copy the generated API key (it will only be shown once)
-For detailed instructions, see: [Prowler App API Keys](../tutorials/prowler-app-api-keys)
+For detailed instructions, see: [Prowler Cloud API Keys](../tutorials/prowler-app-api-keys)
## Configuration File Structure
@@ -261,7 +261,7 @@ python prowler_bulk_provisioning.py providers.yaml --concurrency 10
### Custom API Endpoints
-For self-hosted Prowler App installations:
+For Prowler Local Server installations:
```bash
python prowler_bulk_provisioning.py providers.yaml \
diff --git a/docs/user-guide/tutorials/prowler-app-alerts.mdx b/docs/user-guide/tutorials/prowler-alerts.mdx
similarity index 98%
rename from docs/user-guide/tutorials/prowler-app-alerts.mdx
rename to docs/user-guide/tutorials/prowler-alerts.mdx
index f607844f97..fc205b72be 100644
--- a/docs/user-guide/tutorials/prowler-app-alerts.mdx
+++ b/docs/user-guide/tutorials/prowler-alerts.mdx
@@ -1,17 +1,17 @@
---
title: 'Alerts'
+sidebarTitle: 'Alerts'
description: 'Create email alerts from Prowler Cloud findings to monitor relevant security changes after scans or in daily digests.'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
<VersionBadge version="5.26.0" />
Alerts notify recipients by email when security findings match saved filter conditions. Use Alerts to track high-priority findings, monitor specific providers or services, and keep teams informed about scan results that match defined criteria.
-<Note>
-This feature is available exclusively in **Prowler Cloud** with a paid subscription.
-</Note>
+<SubscriptionBanner />
## Prerequisites
diff --git a/docs/user-guide/tutorials/prowler-app-api-keys.mdx b/docs/user-guide/tutorials/prowler-app-api-keys.mdx
index 4e51e62bac..c7d5f86ec4 100644
--- a/docs/user-guide/tutorials/prowler-app-api-keys.mdx
+++ b/docs/user-guide/tutorials/prowler-app-api-keys.mdx
@@ -3,14 +3,17 @@ title: 'API Keys'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.13.0" />
-API key authentication in Prowler App provides an alternative to JWT tokens and empowers automation, CI/CD pipelines, and third-party integrations. This guide explains how to create, manage, and safeguard API keys when working with the Prowler API.
+<AppliesTo />
+
+API key authentication in Prowler Cloud provides an alternative to JWT tokens and empowers automation, CI/CD pipelines, and third-party integrations. This guide explains how to create, manage, and safeguard API keys when working with the Prowler API.
## API Key Advantages
-- **Programmatic access:** Enables automated workflows and scripts to interact with Prowler App.
+- **Programmatic access:** Enables automated workflows and scripts to interact with Prowler Cloud.
- **Long-lived authentication:** Allows optional expiration dates, with a default of 1 year.
- **Granular control:** Supports multiple keys with distinct names and purposes.
- **Secure automation:** Simplifies safe integration into CI/CD pipelines and infrastructure-as-code tooling.
@@ -19,7 +22,7 @@ API key authentication in Prowler App provides an alternative to JWT tokens and
API keys provide a secure authentication mechanism for accessing the Prowler API:
-1. API keys are created through Prowler App with a user-defined name and optional expiration date.
+1. API keys are created through Prowler Cloud with a user-defined name and optional expiration date.
2. The full API key appears only once upon creation and cannot be retrieved later.
3. Each API key consists of a prefix (visible in the interface) and an encrypted secret portion.
4. Requests include the API key in the header as `Authorization: Api-Key <api-key>`.
@@ -63,13 +66,13 @@ Creating, viewing, or managing API keys requires the **MANAGE_ACCOUNT** RBAC per
Without this permission, the API Keys section remains hidden. Access requests should be routed through the tenant administrator.
-For more information about RBAC permissions, refer to the [Prowler App RBAC documentation](/user-guide/tutorials/prowler-app-rbac).
+For more information about RBAC permissions, refer to the [Prowler Cloud RBAC documentation](/user-guide/tutorials/prowler-app-rbac).
## Creating API Keys
-Follow these steps to create an API key in Prowler App:
+Follow these steps to create an API key in Prowler Cloud:
-1. Navigate to **Profile** → **Account** in Prowler App.
+1. Navigate to **Profile** → **Account** in Prowler Cloud.
2. Select the **Create API Key** button.
@@ -206,7 +209,7 @@ When using API keys in CI/CD pipelines:
* Ensure the key has not been revoked by checking the Revoked column in the API Keys list.
* Confirm that the key has not expired by reviewing the expiration date.
* Confirm that the correct API key format is in use, including both prefix and secret portions.
-* Verify that the key prefix matches what is displayed in Prowler App.
+* Verify that the key prefix matches what is displayed in Prowler Cloud.
### API Key Not Working After Creation
diff --git a/docs/user-guide/tutorials/prowler-app-attack-paths.mdx b/docs/user-guide/tutorials/prowler-app-attack-paths.mdx
index ad0b1fcce1..22e56e5634 100644
--- a/docs/user-guide/tutorials/prowler-app-attack-paths.mdx
+++ b/docs/user-guide/tutorials/prowler-app-attack-paths.mdx
@@ -3,13 +3,16 @@ title: "Attack Paths"
description: "Identify privilege escalation chains and security misconfigurations across cloud environments using graph-based analysis."
---
-import { VersionBadge } from "/snippets/version-badge.mdx"
+import { VersionBadge } from "/snippets/version-badge.mdx";
+import { AppliesTo } from "/snippets/applies-to.mdx";
<VersionBadge version="5.17.0" />
+<AppliesTo />
+
Attack Paths analyzes relationships between cloud resources, permissions, and security findings to detect how privileges can be escalated and how misconfigurations can be exploited by threat actors.
-By mapping these relationships as a graph, Attack Paths reveals risks that individual security checks cannot detect on their own — such as an IAM role that can escalate its own permissions, or a chain of policies that grants unintended access to sensitive resources.
+By mapping these relationships as a graph, Attack Paths reveals risks that individual security checks cannot detect on their own, such as an IAM role that can escalate its own permissions, or a chain of policies that grants unintended access to sensitive resources.
<Note>
Attack Paths is currently available for **AWS** providers. Support for
@@ -20,14 +23,14 @@ By mapping these relationships as a graph, Attack Paths reveals risks that indiv
The following prerequisites are required for Attack Paths:
-- **An AWS provider is configured** with valid credentials in Prowler App. For setup instructions, see [Getting Started with AWS](/user-guide/providers/aws/getting-started-aws).
-- **At least one scan has completed** on the configured AWS provider. Attack Paths scans run automatically alongside regular security scans — no separate configuration is required.
+- **An AWS provider is configured** with valid credentials in Prowler Cloud. For setup instructions, see [Getting Started with AWS](/user-guide/providers/aws/getting-started-aws).
+- **At least one scan has completed** on the configured AWS provider and produced graph data. Attack Paths scans run automatically alongside regular security scans, no separate configuration is required.
## How Attack Paths Scans Work
Attack Paths scans are generated automatically when a security scan runs on an AWS provider. Each completed scan produces graph data that maps relationships between IAM principals, policies, trust configurations, and other resources.
-Once the scan finishes and the graph data is ready, the scan appears in the Attack Paths scan table with a **Completed** status. Scans that are still processing display as **Executing** or **Scheduled**.
+Once the scan finishes and graph data is ready, the scan appears in the Attack Paths scan table with a **Completed** status and a check in the **Graph** column. Scans that are still queued or running remain visible, but they cannot be selected until graph data is ready.
<Note>
Since Prowler scans all configured providers every **24 hours** by default,
@@ -41,25 +44,28 @@ To open Attack Paths, click **Attack Paths** in the left navigation menu.
<img
src="/images/prowler-app/attack-paths/navigation.png"
alt="Attack Paths navigation menu entry"
- width="700"
+ width="320"
/>
-The main interface is divided into two areas:
+The Attack Paths page guides you through the workflow on one page:
-- **Left panel:** A table listing all available Attack Paths scans
-- **Right panel:** The query selector, parameter form, and execute controls
+- Select a scan with graph data.
+- Choose a built-in query or a custom openCypher query.
+- Add parameters when the selected query requires them.
+- Execute the query and explore the resulting graph.
## Selecting a Scan
The scans table displays all Attack Paths scans with the following columns:
-- **Provider / Account:** The AWS provider alias and account identifier
-- **Last scan date:** When the scan completed
-- **Status:** Current state of the scan (Completed, Executing, Scheduled, or Failed)
-- **Progress:** Completion percentage for in-progress scans
-- **Duration:** Total scan time
+- **Select:** A radio button used to choose a scan. The radio button is disabled when graph data is not available.
+- **Provider:** The AWS provider alias and account identifier.
+- **Last Scan Date:** When the scan completed.
+- **Status:** Current state of the scan, such as **Completed**, **Executing**, **Scheduled**, or **Failed**.
+- **Graph:** Whether Attack Paths graph data is available for the scan.
+- **Duration:** Total scan time.
-To select a scan for analysis, click **Select** on any row with a **Completed** status.
+To select a scan for analysis, click the radio button on any row with a **Completed** status and available graph data.
<img
src="/images/prowler-app/attack-paths/scan-list-table.png"
@@ -68,19 +74,18 @@ To select a scan for analysis, click **Select** on any row with a **Completed**
/>
<Note>
- Only scans with a **Completed** status and ready graph data can be selected.
- Scans that are still executing or have failed appear with disabled action
- buttons.
+ Only scans with graph data can be selected. Disabled rows include a tooltip
+ that explains why the graph is not available yet.
</Note>
## Choosing a Query
-After selecting a scan, the right panel activates a query dropdown. Each query targets a specific type of privilege escalation or misconfiguration pattern.
+After selecting a scan, the query selector becomes available. Each query targets a specific privilege escalation, exposure, inventory, or misconfiguration pattern.
To choose a query, click the dropdown and select from the available options. Each option displays:
-- **Query name:** A descriptive title (e.g., "IAM Privilege Escalation via AssumeRole")
-- **Short description:** A brief summary of what the query detects
+- **Query name:** A descriptive title, such as **Internet-Exposed EC2 with Sensitive S3 Access**.
+- **Short description:** A brief summary of what the query detects.
<img
src="/images/prowler-app/attack-paths/query-selector.png"
@@ -88,16 +93,17 @@ To choose a query, click the dropdown and select from the available options. Eac
width="700"
/>
-Once selected, a description card appears below the dropdown with additional context about the query, including attribution links to external references when available.
+Once selected, a description panel appears below the dropdown with more context about the query.
## Configuring Query Parameters
-Some queries accept optional or required parameters to narrow the scope of the analysis. When a query has parameters, a dynamic form appears below the query description.
+Some queries accept optional or required parameters to narrow the scope of the analysis. When a query has parameters, a form appears below the query description.
-- **Required fields** are marked with an asterisk (\*) and must be filled before executing
-- **Optional fields** refine the query results but are not mandatory
+- **Required fields** are marked with an asterisk (\*) and must be filled before executing.
+- **Optional fields** refine the query results but are not mandatory.
+- Queries without parameters show no parameter form.
-If a query requires no parameters, the form displays a message confirming that the query is ready to execute.
+For example, **Internet-Exposed EC2 with Sensitive S3 Access** uses **Tag key** and **Tag value** fields to identify sensitive S3 buckets.
<img
src="/images/prowler-app/attack-paths/query-parameters.png"
@@ -117,7 +123,7 @@ Custom queries are sandboxed to keep the graph database safe and responsive:
- **Read-only:** Only read operations are allowed. Statements that mutate the graph (`CREATE`, `MERGE`, `SET`, `DELETE`, `REMOVE`, `DROP`, `LOAD CSV`, `CALL { ... }` writes, etc.) are rejected before execution.
- **Length limit:** Each query is capped at **10,000 characters**.
-- **Scoped to the selected scan:** Results are automatically scoped to the provider and scan selected on the left panel. There is no need to filter by tenant or scan identifier in the query body.
+- **Scoped to the selected scan:** Results are automatically scoped to the provider and scan selected in the scan table. There is no need to filter by tenant or scan identifier in the query body.
### Example Queries
@@ -145,11 +151,10 @@ LIMIT 25
**IAM principals with wildcard Allow statements:**
```cypher
-MATCH (principal:AWSPrincipal)--(policy:AWSPolicy)--(stmt:AWSPolicyStatement)
-WHERE stmt.effect = 'Allow'
- AND ANY(action IN stmt.action WHERE action = '*')
-RETURN principal.arn AS principal, policy.arn AS policy,
- stmt.action AS actions, stmt.resource AS resources
+MATCH (principal:AWSPrincipal)-[:POLICY]->(policy:AWSPolicy)-[:STATEMENT]->(stmt:AWSPolicyStatement {effect: 'Allow'})
+MATCH (stmt)-[:HAS_ACTION]->(a:AWSPolicyStatementActionItem)
+WHERE a.value = '*'
+RETURN DISTINCT principal.arn AS principal, policy.arn AS policy
LIMIT 25
```
@@ -173,9 +178,89 @@ RETURN r.name AS role_name, r.arn AS role_arn, p.arn AS trusted_service
LIMIT 25
```
+### Working with List-Typed Properties
+
+Some Cartography node properties carry a list of values, such as `action`, `resource`, `notaction`, and `notresource` on `AWSPolicyStatement` nodes, the algorithms on `KMSKey`, the container-definition lists on `ECSContainerDefinition`, and many others. The Attack Paths graph models each such property as a set of child item nodes connected to the parent by a typed edge. To read the values, traverse the edge; the parent does not carry the list as a single field.
+
+The naming convention for any list-typed property on a parent label is:
+
+- **Child label:** `<ParentLabel><PropertyPascal>Item`. Example: `AWSPolicyStatement.resource` resolves to `AWSPolicyStatementResourceItem`.
+- **Edge type:** `HAS_<PROPERTY_UPPER>`. Example: `resource` resolves to `HAS_RESOURCE`.
+- **Child property:** `value` for scalar lists (one string per list element). List-of-dict properties (rare; for example `SecretsManagerSecretVersion.tags`) carry the original dict keys as named fields on the child node.
+
+To express "at least one item in the list satisfies a predicate", traverse the `HAS_*` edge in its own `MATCH` clause and apply the predicate in the attached `WHERE`. `RETURN DISTINCT` collapses duplicate parent rows produced when multiple child items satisfy the filter:
+
+```cypher
+MATCH (stmt:AWSPolicyStatement {effect: 'Allow'})
+MATCH (stmt)-[:HAS_ACTION]->(a:AWSPolicyStatementActionItem)
+WHERE toLower(a.value) STARTS WITH 's3:get'
+ OR toLower(a.value) STARTS WITH 's3:list'
+RETURN DISTINCT stmt
+LIMIT 25
+```
+
+To check whether every item in the list satisfies a predicate, count the counter-examples and require zero, together with a guard that ensures at least one item is attached. This is the one case where the pattern-comprehension form is the right tool:
+
+```cypher
+MATCH (stmt:AWSPolicyStatement)
+WHERE size([
+ (stmt)-[:HAS_ACTION]->(a:AWSPolicyStatementActionItem)
+ WHERE NOT toLower(a.value) STARTS WITH 's3:'
+ | a
+ ]) = 0
+ AND size([(stmt)-[:HAS_ACTION]->(a:AWSPolicyStatementActionItem) | a]) > 0
+RETURN stmt
+LIMIT 25
+```
+
+For the "is any item of this list a substring of a dynamic value" case, such as "does any resource pattern in this policy match a target role ARN", add the `HAS_*` traversal as its own `MATCH` and check the substring relationship between the item value and the dynamic node in `WHERE`:
+
+```cypher
+MATCH (role:AWSRole)
+WHERE role.name = 'Admin'
+MATCH (principal:AWSPrincipal)-[:POLICY]->(:AWSPolicy)-[:STATEMENT]->(stmt:AWSPolicyStatement {effect: 'Allow'})
+MATCH (stmt)-[:HAS_RESOURCE]->(r:AWSPolicyStatementResourceItem)
+WHERE r.value = '*'
+ OR r.value CONTAINS role.name
+ OR role.arn CONTAINS r.value
+RETURN DISTINCT principal.arn AS principal, stmt, role
+LIMIT 25
+```
+
+To return the list of values directly, collect them from the child items:
+
+```cypher
+MATCH (stmt:AWSPolicyStatement {effect: 'Allow'})
+OPTIONAL MATCH (stmt)-[:HAS_ACTION]->(a:AWSPolicyStatementActionItem)
+RETURN stmt, collect(a.value) AS actions
+LIMIT 25
+```
+
+### Working with JSON-Encoded Properties
+
+Some Cartography properties represent nested objects, most notably `condition` on `AWSPolicyStatement` and `S3PolicyStatement` nodes. In the Attack Paths graph, object-typed properties are stored as JSON-encoded strings to keep the schema portable across graph backends. The value looks like:
+
+```
+'{"StringEquals":{"aws:SourceAccount":"123456789012"}}'
+```
+
+There is no JSON parser available at query time, so use `CONTAINS` for substring checks against keys or known values:
+
+```cypher
+MATCH (stmt:AWSPolicyStatement)
+WHERE stmt.effect = 'Allow'
+ AND stmt.condition CONTAINS '"aws:SourceAccount"'
+RETURN stmt
+LIMIT 25
+```
+
+When a query needs to inspect the structured members of a condition (for example, evaluate every operator and key), fetch the rows first and parse the JSON in application code. Cypher cannot navigate JSON object keys or values.
+
### Tips for Writing Queries
- Start small with `LIMIT` to inspect the shape of the data before broadening the pattern.
+- Traverse `HAS_*` edges to reach list-typed property values (for example `action`, `resource`). The parent node does not carry the list as a single field; see [Working with List-Typed Properties](#working-with-list-typed-properties) for the patterns.
+- On large scans, avoid broad disconnected patterns such as `MATCH (a:Label), (b:OtherLabel)`. Bind one side with a selective predicate first, and use `WITH DISTINCT` between expanding traversals when duplicates are possible.
- Use `RETURN` projections (`RETURN n.name, n.region`) instead of returning whole nodes to keep responses compact.
- Combine resource nodes with `ProwlerFinding` nodes via `HAS_FINDING` to correlate misconfigurations with the affected resources.
- When a query times out or returns no rows, simplify the pattern step by step until the first variant runs successfully, then add constraints back.
@@ -192,64 +277,88 @@ In addition to the upstream schema, Prowler enriches the graph with:
- **`ProwlerFinding`** nodes representing Prowler check results, linked to affected resources via `HAS_FINDING` relationships.
- **`Internet`** nodes used to model exposure paths from the public internet to internal resources.
+- **List-typed properties** such as `action` or `resource` on `AWSPolicyStatement`, the algorithm lists on `KMSKey`, and similar lists on other node types are modeled as child item nodes linked by typed `HAS_*` edges. See [Working with List-Typed Properties](#working-with-list-typed-properties) for the read pattern.
+- **Object-typed properties** such as `condition` on `AWSPolicyStatement` are stored as JSON-encoded strings. See [Working with JSON-Encoded Properties](#working-with-json-encoded-properties) for the read pattern.
<Note>
AI assistants connected through Prowler MCP Server can fetch the exact
Cartography schema for the active scan via the
- `prowler_app_get_attack_paths_cartography_schema` tool. This guarantees that
+ `prowler_get_attack_paths_cartography_schema` tool. This guarantees that
generated queries match the schema version pinned by the running Prowler
release.
</Note>
## Executing a Query
-To run the selected query against the scan data, click **Execute Query**. The button displays a loading state while the query processes.
+To run the selected query against the scan data, click **Execute Query**. The button is disabled until a query is selected and all required parameters are valid.
+
+The button displays a loading state while the query runs. After the query completes, the graph appears below the query builder.
If the query returns no results, an informational message appears. Common reasons include:
-- **No matching patterns found:** The scanned environment does not contain the privilege escalation chain the query targets
-- **Insufficient permissions:** The scan credentials may not have captured all the data the query needs
+- **No matching patterns found:** The scanned environment does not contain the pattern the query targets.
+- **Not enough permissions:** The scan credentials may not have captured all the data the query needs.
+- **Server unavailable:** The graph service may be temporarily unavailable.
<img
src="/images/prowler-app/attack-paths/execute-query.png"
- alt="Attack Paths right panel with query selected and execute button"
+ alt="Attack Paths query builder with query selected and execute button"
width="700"
/>
## Exploring the Graph
-After a successful execution, the graph visualization renders below the query builder in a full-width panel. The graph maps relationships between cloud resources, IAM entities, and security findings.
+After a successful execution, the graph visualization renders below the query builder. The graph maps relationships between cloud resources, IAM entities, public exposure, and security findings.
### Node Types
-- **Resource nodes** (rounded pills): Represent cloud resources such as IAM roles, policies, EC2 instances, and S3 buckets. Each resource type has a distinct color.
-- **Finding nodes** (hexagons): Represent Prowler security findings linked to resources in the graph. Colors indicate severity level (critical, high, medium, low).
+- **Provider root nodes:** Represent the AWS account or provider root for the selected scan.
+- **Resource nodes:** Represent cloud resources such as IAM roles, policies, EC2 instances, security groups, and S3 buckets.
+- **Internet nodes:** Represent exposure from the public internet.
+- **Finding nodes:** Represent Prowler findings linked to resources. Finding colors indicate risk level, such as critical, high, medium, or low.
### Edge Types
-- **Solid lines:** Direct relationships between resources (e.g., a role attached to a policy)
-- **Dashed lines:** Connections between resources and their associated findings
+- **Normal edges:** Direct relationships between graph nodes, such as role-to-policy or resource-to-security-group relationships.
+- **Finding edges:** Dashed relationships between resources and their associated findings.
+- **Highlighted paths:** Green edges that show the active path when you hover a node or focus a finding.
-A **legend** at the bottom of the graph lists all node types and edge types present in the current view.
+The standard graph view includes a minimap and a legend below the canvas. The legend shows the provider roots, visible node types, finding risk levels, node states, and edge types present in the current view.
<img
src="/images/prowler-app/attack-paths/graph-visualization.png"
- alt="Attack Paths graph showing nodes, edges, and legend"
+ alt="Attack Paths graph showing nodes and edges"
width="700"
/>
## Interacting with the Graph
-### Filtering by Node
+The graph banner describes the main interactions:
-Click any node in the graph to filter the view and display only paths that pass through that node. When a filter is active:
+- Click a finding to focus its connected path.
+- Click a resource with findings to show or hide its related findings.
+- Hover a node to highlight its connected path.
-- An information banner shows which node is selected
-- Click **Back to Full View** to restore the complete graph
+### Showing Related Findings
+
+Resource nodes with related findings are clickable. Click one of these resources to show its finding nodes. Click the resource again to hide them.
+
+The graph automatically fits the selected resource and its related findings when the findings are shown.
+
+### Focusing a Finding Path
+
+Click a finding node to focus the graph on the path connected to that finding. When the graph is focused:
+
+- The graph shows **Back to Full View**.
+- The status banner shows the selected finding.
+- The graph keeps only the connected path in view.
+- The finding detail drawer opens.
+
+After you close the drawer, the graph remains focused on the selected path.
<img
src="/images/prowler-app/attack-paths/graph-filtered.png"
- alt="Attack Paths graph filtered to show paths through a selected node"
+ alt="Attack Paths graph focused on a selected finding path"
width="700"
/>
@@ -258,29 +367,29 @@ Click any node in the graph to filter the view and display only paths that pass
The toolbar in the top-right corner of the graph provides:
- **Zoom in / Zoom out:** Adjust the zoom level
-- **Fit to screen:** Reset the view to fit all nodes
-- **Export:** Download the current graph as an SVG file
-- **Fullscreen:** Open the graph in a full-screen modal with a side-by-side node detail panel
+- **Fit graph to view:** Reset the view to fit the visible graph
+- **Export graph:** Download the current graph as a PNG file
+- **Fullscreen:** Open the graph in a full-size modal
<Note>
Use **Ctrl + Scroll** (or **Cmd + Scroll** on macOS) to zoom directly within
the graph area.
</Note>
-## Viewing Node Details
+## Viewing Finding Details
-Click any node to open the **Node Details** panel below the graph. This panel displays:
+Click a finding node to open the finding detail drawer. The drawer uses the same finding detail layout as the Findings page and includes:
-- **Node type:** The resource category (e.g., "IAM Role," "EC2 Instance")
-- **Properties:** All attributes of the selected node, including identifiers, timestamps, and configuration details
-- **Related findings** (for resource nodes): A list of Prowler findings linked to the resource, with severity, title, and status
-- **Affected resources** (for finding nodes): A list of resources associated with the finding
+- The finding title, status, and severity.
+- The affected resource summary.
+- Overview, remediation, evidence, related findings, scans, and events tabs when data is available.
+- A Lighthouse AI action when the account has access to Lighthouse AI.
-For finding nodes, a "View Finding" button links directly to the finding detail page for further investigation.
+Resource nodes do not open a node detail panel. When a resource has related findings, clicking it expands or collapses those finding nodes in the graph.
<img
src="/images/prowler-app/attack-paths/node-details.png"
- alt="Attack Paths node detail panel showing properties and related findings"
+ alt="Attack Paths finding detail drawer"
width="700"
/>
@@ -288,16 +397,28 @@ For finding nodes, a "View Finding" button links directly to the finding detail
To expand the graph for detailed exploration, click the fullscreen icon in the graph toolbar. The fullscreen modal provides:
-- The full graph visualization with all zoom and export controls
-- A side panel for node details that appears when a node is selected
-- All filtering and interaction capabilities available in the standard view
+- The graph in a full-size modal.
+- The same zoom, fit, and export controls.
+- The same node expansion, finding focus, hover highlight, and minimap interactions available in the standard view.
<img
src="/images/prowler-app/attack-paths/fullscreen-mode.png"
- alt="Attack Paths fullscreen mode with graph and node detail side panel"
+ alt="Attack Paths fullscreen graph mode"
width="700"
/>
+## Available Queries
+
+The query selector includes custom openCypher and built-in AWS queries for common security investigation workflows. Available queries are loaded from the selected scan and may change as new query packs are added.
+
+Available queries include:
+
+- **Custom openCypher query:** Write and run a read-only graph query.
+- **Exposure queries:** Find internet-exposed EC2 instances, load balancers, open security groups, and resources by public IP.
+- **Inventory queries:** List resources such as RDS instances.
+- **Misconfiguration queries:** Find unencrypted RDS instances, public S3 buckets, and wildcard IAM statements.
+- **Privilege escalation queries:** Detect IAM and AWS service paths based on known attack techniques, including queries based on [pathfinding.cloud](https://pathfinding.cloud) research by Datadog.
+
## Using Attack Paths with the MCP Server and Lighthouse AI
Attack Paths capabilities are also available through the [Prowler MCP Server](/getting-started/products/prowler-mcp), enabling interaction with Attack Paths data via AI assistants like Claude Desktop, Cursor, and other MCP clients.
@@ -306,10 +427,10 @@ Attack Paths capabilities are also available through the [Prowler MCP Server](/g
The following MCP tools are available for Attack Paths:
-- **`prowler_app_list_attack_paths_scans`** - List and filter Attack Paths scans
-- **`prowler_app_list_attack_paths_queries`** - Discover available queries for a completed scan
-- **`prowler_app_run_attack_paths_query`** - Execute a query and retrieve graph results with nodes and relationships
-- **`prowler_app_get_attack_paths_cartography_schema`** - Retrieve the Cartography graph schema for custom openCypher queries
+- **`prowler_list_attack_paths_scans`** - List and filter Attack Paths scans.
+- **`prowler_list_attack_paths_queries`** - Discover available queries for a completed scan.
+- **`prowler_run_attack_paths_query`** - Execute a query and retrieve graph results with nodes and relationships.
+- **`prowler_get_attack_paths_cartography_schema`** - Retrieve the Cartography graph schema for custom openCypher queries.
### Example Questions
@@ -324,111 +445,8 @@ Ask through the MCP Server or Lighthouse AI:
- "Are there any CloudFormation stacks that could be hijacked for privilege escalation?"
- "Show me all roles that can be assumed for lateral movement"
-### Supported Queries
-
-Attack Paths currently supports the following built-in queries for AWS:
-
-#### Custom Attack Path Queries
-
-| Query | Description |
-|---|---|
-| **Internet-Exposed EC2 with Sensitive S3 Access** | Find SSH-exposed EC2 instances that can assume roles to read tagged sensitive S3 buckets |
-
-#### Basic Resource Queries
-
-| Query | Description |
-|---|---|
-| **RDS Instances Inventory** | List all provisioned RDS database instances in the account |
-| **Unencrypted RDS Instances** | Find RDS instances with storage encryption disabled |
-| **S3 Buckets with Anonymous Access** | Find S3 buckets that allow anonymous access |
-| **IAM Statements Allowing All Actions** | Find IAM policy statements that allow all actions via wildcard (\*) |
-| **IAM Statements Allowing Policy Deletion** | Find IAM policy statements that allow iam:DeletePolicy |
-| **IAM Statements Allowing Create Actions** | Find IAM policy statements that allow any create action |
-
-#### Network Exposure Queries
-
-| Query | Description |
-|---|---|
-| **Internet-Exposed EC2 Instances** | Find EC2 instances flagged as exposed to the internet |
-| **Open Security Groups on Internet-Facing Resources** | Find internet-facing resources with security groups allowing inbound from 0.0.0.0/0 |
-| **Internet-Exposed Classic Load Balancers** | Find Classic Load Balancers exposed to the internet with their listeners |
-| **Internet-Exposed ALB/NLB Load Balancers** | Find ELBv2 (ALB/NLB) load balancers exposed to the internet with their listeners |
-| **Resource Lookup by Public IP** | Find the AWS resource associated with a given public IP address |
-
-#### Privilege Escalation Queries
-
-These queries are based on research from [pathfinding.cloud](https://pathfinding.cloud) by Datadog.
-
-| Query | Description |
-|---|---|
-| **App Runner Service Creation with Privileged Role (APPRUNNER-001)** | Create an App Runner service with a privileged IAM role to gain its permissions |
-| **App Runner Service Update for Role Access (APPRUNNER-002)** | Update an existing App Runner service to leverage its already-attached privileged role |
-| **Bedrock Code Interpreter with Privileged Role (BEDROCK-001)** | Create a Bedrock AgentCore Code Interpreter with a privileged role attached |
-| **Bedrock Code Interpreter Session Hijacking (BEDROCK-002)** | Start a session on an existing Bedrock code interpreter to exfiltrate its privileged role credentials |
-| **CloudFormation Stack Creation with Privileged Role (CLOUDFORMATION-001)** | Create a CloudFormation stack with a privileged role to provision arbitrary AWS resources |
-| **CloudFormation Stack Update for Role Access (CLOUDFORMATION-002)** | Update an existing CloudFormation stack to leverage its already-attached privileged service role |
-| **CloudFormation StackSet Creation with Privileged Role (CLOUDFORMATION-003)** | Create a CloudFormation StackSet with a privileged execution role to provision arbitrary resources across accounts |
-| **CloudFormation StackSet Update with Privileged Role (CLOUDFORMATION-004)** | Update an existing CloudFormation StackSet to inject malicious resources using a privileged execution role |
-| **CloudFormation Change Set Privilege Escalation (CLOUDFORMATION-005)** | Create and execute a change set on an existing stack to leverage its privileged service role |
-| **CodeBuild Project Creation with Privileged Role (CODEBUILD-001)** | Create a CodeBuild project with a privileged role to execute arbitrary code via a malicious buildspec |
-| **CodeBuild Buildspec Override for Role Access (CODEBUILD-002)** | Start a build on an existing CodeBuild project with a buildspec override to execute code with its privileged role |
-| **CodeBuild Batch Buildspec Override for Role Access (CODEBUILD-003)** | Start a batch build on an existing CodeBuild project with a buildspec override to execute code with its privileged role |
-| **CodeBuild Batch Project Creation with Privileged Role (CODEBUILD-004)** | Create a CodeBuild project configured for batch builds with a privileged role to execute arbitrary code via a malicious buildspec |
-| **Data Pipeline Creation with Privileged Role (DATAPIPELINE-001)** | Create a Data Pipeline with a privileged role to execute arbitrary commands on provisioned infrastructure |
-| **EC2 Instance Launch with Privileged Role (EC2-001)** | Launch EC2 instances with privileged IAM roles to gain their permissions via IMDS |
-| **EC2 Role Hijacking via UserData Injection (EC2-002)** | Inject malicious scripts into EC2 instance userData to gain the attached role's permissions |
-| **Spot Instance Launch with Privileged Role (EC2-003)** | Launch EC2 Spot Instances with privileged IAM roles to gain their permissions via IMDS |
-| **Launch Template Poisoning for Role Access (EC2-004)** | Inject malicious userData into launch templates that reference privileged roles, no PassRole needed |
-| **EC2 Instance Connect SSH Access for Role Credentials (EC2INSTANCECONNECT-003)** | Push a temporary SSH key to an EC2 instance via Instance Connect to access its attached role credentials through IMDS |
-| **ECS Service Creation with Privileged Role (ECS-001 - New Cluster)** | Create an ECS cluster and service with a privileged Fargate task role to execute arbitrary code |
-| **ECS Task Execution with Privileged Role (ECS-002 - New Cluster)** | Create an ECS cluster and run a one-off Fargate task with a privileged role to execute arbitrary code |
-| **ECS Service Creation with Privileged Role (ECS-003 - Existing Cluster)** | Deploy a Fargate service with a privileged role on an existing ECS cluster |
-| **ECS Task Execution with Privileged Role (ECS-004 - Existing Cluster)** | Run a one-off Fargate task with a privileged role on an existing ECS cluster |
-| **ECS Task Start with Privileged Role on EC2 (ECS-005 - Existing Cluster)** | Register a task definition with a privileged role and start it on an EC2 container instance to execute arbitrary code |
-| **ECS Exec Container Hijacking for Role Credentials (ECS-006)** | Shell into a running ECS container via ECS Exec to steal the attached task role's credentials |
-| **Glue Dev Endpoint with Privileged Role (GLUE-001)** | Create a Glue development endpoint with a privileged role attached to gain its permissions |
-| **Glue Dev Endpoint SSH Hijacking via Update (GLUE-002)** | Update an existing Glue development endpoint to inject an SSH public key and access its attached role credentials |
-| **Glue Job Creation with Privileged Role (GLUE-003)** | Create a Glue job with a privileged role and start it to execute arbitrary code with that role's permissions |
-| **Glue Job Creation with Scheduled Trigger and Privileged Role (GLUE-004)** | Create a Glue job with a privileged role and a scheduled trigger to persistently execute arbitrary code |
-| **Glue Job Hijacking via Update with Privileged Role (GLUE-005)** | Update an existing Glue job to attach a privileged role and inject malicious code, then start it to gain that role's permissions |
-| **Glue Job Hijacking with Scheduled Trigger and Privileged Role (GLUE-006)** | Update an existing Glue job to attach a privileged role and inject malicious code, then create a scheduled trigger for persistent automated execution |
-| **Policy Version Override for Self-Escalation (IAM-001)** | Create a new version of an attached policy with administrative permissions, instantly escalating the principal's own privileges |
-| **Access Key Creation for Lateral Movement (IAM-002)** | Create access keys for other IAM users to gain their permissions and move laterally across the account |
-| **Access Key Rotation Attack for Lateral Movement (IAM-003)** | Delete and recreate access keys for other IAM users to bypass the two-key limit and gain their permissions |
-| **Console Login Profile Creation for Lateral Movement (IAM-004)** | Create console login profiles for other IAM users to access the AWS Console with their permissions |
-| **Inline Policy Injection for Self-Escalation (IAM-005)** | Attach an inline policy with administrative permissions to your own role, instantly escalating privileges |
-| **Console Password Override for Lateral Movement (IAM-006)** | Change the console password of other IAM users to log in as them and gain their permissions |
-| **Inline Policy Injection on User for Self-Escalation (IAM-007)** | Attach an inline policy with administrative permissions to your own IAM user, instantly escalating privileges |
-| **Managed Policy Attachment on User for Self-Escalation (IAM-008)** | Attach existing managed policies with administrative permissions to your own IAM user, instantly escalating privileges |
-| **Managed Policy Attachment on Role for Self-Escalation (IAM-009)** | Attach existing managed policies with administrative permissions to your own IAM role, instantly escalating privileges |
-| **Managed Policy Attachment on Group for Self-Escalation (IAM-010)** | Attach existing managed policies with administrative permissions to a group you belong to, escalating privileges for all group members |
-| **Inline Policy Injection on Group for Self-Escalation (IAM-011)** | Attach an inline policy with administrative permissions to a group you belong to, escalating privileges for all group members |
-| **Trust Policy Hijacking for Role Assumption (IAM-012)** | Modify a role's trust policy to allow yourself to assume it, gaining the role's permissions |
-| **Group Membership Hijacking for Privilege Escalation (IAM-013)** | Add yourself to a privileged IAM group to inherit its permissions, gaining access to all policies attached to the group |
-| **Managed Policy Attachment with Role Assumption for Lateral Movement (IAM-014)** | Attach administrative managed policies to another role you can assume, then assume it to gain elevated privileges |
-| **Managed Policy Attachment with Access Key Creation for Lateral Movement (IAM-015)** | Attach administrative managed policies to another IAM user and create access keys for them to gain programmatic access with elevated privileges |
-| **Policy Version Override with Role Assumption for Lateral Movement (IAM-016)** | Create a new version of a customer-managed policy attached to another role with administrative permissions, then assume that role to gain elevated access |
-| **Inline Policy Injection with Role Assumption for Lateral Movement (IAM-017)** | Attach an inline policy with administrative permissions to another role you can assume, then assume it to gain elevated privileges |
-| **Inline Policy Injection with Access Key Creation for Lateral Movement (IAM-018)** | Attach an inline policy with administrative permissions to another IAM user and create access keys for them to gain programmatic access with elevated privileges |
-| **Managed Policy Attachment with Trust Policy Hijacking for Privilege Escalation (IAM-019)** | Attach administrative managed policies to a role and modify its trust policy to allow yourself to assume it, gaining elevated privileges without prior assume-role access |
-| **Policy Version Override with Trust Policy Hijacking for Privilege Escalation (IAM-020)** | Create a new version of a customer-managed policy attached to a role with administrative permissions and modify its trust policy to assume it, without prior assume-role access |
-| **Inline Policy Injection with Trust Policy Hijacking for Privilege Escalation (IAM-021)** | Add an inline policy with administrative permissions to a role and modify its trust policy to allow yourself to assume it, gaining elevated privileges without prior assume-role access |
-| **Lambda Function Creation with Privileged Role (LAMBDA-001)** | Create a Lambda function with a privileged IAM role and invoke it to execute code with that role's permissions |
-| **Lambda Function Creation with Event Source Trigger (LAMBDA-002)** | Create a Lambda function with a privileged IAM role and an event source mapping to trigger it automatically, executing code with the role's permissions |
-| **Lambda Function Code Injection (LAMBDA-003)** | Modify the code of an existing Lambda function to execute arbitrary commands with the function's execution role permissions |
-| **Lambda Function Code Injection with Direct Invocation (LAMBDA-004)** | Modify the code of an existing Lambda function and invoke it directly to execute arbitrary commands with the function's execution role permissions |
-| **Lambda Function Code Injection with Resource Policy Grant (LAMBDA-005)** | Modify the code of an existing Lambda function and grant yourself invocation permission via its resource-based policy to execute code with the function's execution role |
-| **Lambda Function Creation with Resource Policy Invocation (LAMBDA-006)** | Create a Lambda function with a privileged IAM role and grant yourself invocation permission via its resource-based policy to execute code with the role's permissions |
-| **SageMaker Notebook Creation with Privileged Role (SAGEMAKER-001)** | Create a SageMaker notebook instance with a privileged IAM role to execute arbitrary code with the role's permissions via the Jupyter environment |
-| **SageMaker Training Job Creation with Privileged Role (SAGEMAKER-002)** | Create a SageMaker training job with a privileged IAM role to execute arbitrary container code with the role's permissions |
-| **SageMaker Processing Job Creation with Privileged Role (SAGEMAKER-003)** | Create a SageMaker processing job with a privileged IAM role to execute arbitrary container code with the role's permissions |
-| **SageMaker Presigned Notebook URL for Privilege Escalation (SAGEMAKER-004)** | Generate a presigned URL to access an existing SageMaker notebook instance and execute code with its execution role's permissions |
-| **SageMaker Notebook Lifecycle Config Injection (SAGEMAKER-005)** | Inject a malicious lifecycle configuration into an existing SageMaker notebook to execute code with the notebook's execution role during startup |
-| **SSM Session Access for EC2 Role Credentials (SSM-001)** | Start an SSM session on an EC2 instance to access its attached role credentials through IMDS |
-| **SSM Send Command for EC2 Role Credentials (SSM-002)** | Execute commands on an EC2 instance via SSM Run Command to access its attached role credentials through IMDS |
-| **Role Assumption for Privilege Escalation (STS-001)** | Assume IAM roles with elevated permissions by exploiting bidirectional trust between the starting principal and the target role |
-
These tools enable workflows such as:
+
- Asking an AI assistant to identify privilege escalation paths in a specific AWS account
- Automating attack path analysis across multiple scans
- Combining attack path data with findings and compliance information for comprehensive security reports
diff --git a/docs/user-guide/tutorials/prowler-app-finding-groups.mdx b/docs/user-guide/tutorials/prowler-app-finding-groups.mdx
index e1bf83a50f..c5234bb41f 100644
--- a/docs/user-guide/tutorials/prowler-app-finding-groups.mdx
+++ b/docs/user-guide/tutorials/prowler-app-finding-groups.mdx
@@ -1,12 +1,16 @@
---
title: 'Finding Groups'
+sidebarTitle: 'Groups'
description: 'Organize and triage security findings by check to reduce noise and prioritize remediation effectively.'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.23.0" />
+<AppliesTo />
+
Finding Groups transforms security findings triage by grouping them by check instead of displaying a flat list. This dramatically reduces noise and enables faster, more effective prioritization.
## Triage Challenges with Flat Finding Lists
@@ -112,7 +116,7 @@ This provides full context without leaving the drawer.
## Getting Started
-1. Navigate to the **Findings** section in Prowler Cloud/App.
+1. Navigate to the **Findings** section in Prowler Cloud.
2. Toggle to the **Grouped View** to see findings organized by check.
3. Select any group row to expand and see affected resources.
4. Select a resource to open the detail drawer with full context.
diff --git a/docs/user-guide/tutorials/prowler-app-findings-triage.mdx b/docs/user-guide/tutorials/prowler-app-findings-triage.mdx
new file mode 100644
index 0000000000..bbceaef992
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-app-findings-triage.mdx
@@ -0,0 +1,125 @@
+---
+title: "Findings Triage"
+sidebarTitle: 'Triage'
+description: "Track finding review status and team notes in Prowler Cloud."
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+<VersionBadge version="5.32.0" />
+
+Findings Triage lets teams track review status and notes for individual findings in Prowler Cloud. Use it to record investigation state, remediation work, accepted risk, or false positive decisions without leaving the Findings workflow.
+
+<SubscriptionBanner />
+
+## What Is Findings Triage?
+
+Findings Triage adds a **Triage** status and team note workflow to individual finding rows. It is available from:
+
+- Expanded rows in **Finding Groups**
+- Standalone finding tables
+- Finding and resource detail drawers, including related findings tables
+
+Finding Groups rows do not show triage controls because a group row represents several findings. Expand a group to work with each affected resource.
+
+
+
+## Required Permissions
+
+To update triage statuses and notes, the user role must have the **Manage Scans** permission. For more information, see [Role-Based Access Control (RBAC)](/user-guide/tutorials/prowler-app-rbac).
+
+Users without this permission can still see existing triage context when it is available, but cannot change statuses or save notes.
+
+## Triage Statuses
+
+The status selector includes manual statuses. Prowler also sets automatic statuses after scans.
+
+| Status | Type | Use It When |
+| --- | --- | --- |
+| **Open** | Manual | A failed finding has not been reviewed yet. A failed finding with no saved triage state also appears as **Open**. |
+| **Under Review** | Manual | A team is investigating the finding. |
+| **Remediating** | Manual | Work is in progress to fix the finding. |
+| **Risk Accepted** | Manual | The team accepts the risk and wants to mute the finding. |
+| **False Positive** | Manual | The finding does not apply and should be muted. |
+| **Resolved** | Automatic | A finding changed from `FAIL` to `PASS` in a later scan. A passed finding with no saved triage state also appears as **Resolved**. |
+| **Reopened** | Automatic | A finding changed from `PASS` to `FAIL` in a later scan. |
+
+
+
+Resolved and Reopened are not manual selector options.
+
+These automatic states keep triage tied to the finding UID across scans, even when each scan creates a new finding snapshot.
+
+## Change a Triage Status
+
+<Steps>
+ <Step title="Open Findings">
+ Go to **Findings** in Prowler Cloud.
+ </Step>
+ <Step title="Select an individual finding">
+ Expand a Finding Group, open a resource findings table, or use a standalone finding row.
+ </Step>
+ <Step title="Open the triage selector">
+ In the **Triage** column, click the current status.
+ </Step>
+ <Step title="Choose a status">
+ Select **Open**, **Under Review**, **Remediating**, **Risk Accepted**, or **False Positive**.
+ </Step>
+</Steps>
+
+Changing a finding to **Risk Accepted** or **False Positive** will mute the finding. Prowler asks for confirmation and creates a mute rule for the finding.
+
+## Add or Edit a Triage Note
+
+Triage notes are visible only to the team in the current organization. Each note supports up to 500 characters.
+
+<Steps>
+ <Step title="Open the finding actions menu">
+ On an individual finding row, click the actions menu.
+ </Step>
+ <Step title="Open the note modal">
+ Click **Add Triage Note**. If a note already exists, click **Open note**.
+ </Step>
+ <Step title="Set status and note text">
+ Optionally change the status, then write the note.
+ </Step>
+ <Step title="Save changes">
+ Click **Save changes**.
+ </Step>
+</Steps>
+
+
+
+To remove an existing note, clear the note text and save the change.
+
+## Mutelist Behavior
+
+Findings Triage uses Mutelist when a status means the finding should be muted:
+
+- **Risk Accepted** creates a mute rule because the team accepts the finding as a known risk.
+- **False Positive** creates a mute rule because the finding should not count as an active issue.
+
+Use [Simple Mutelist](/user-guide/tutorials/prowler-app-simple-mutelist) to review, disable, or delete mute rules created through this workflow. For pattern-based muting, use [Advanced Mutelist](/user-guide/tutorials/prowler-app-mute-findings).
+
+<Warning>
+Muting a finding does not fix the underlying configuration. Review the finding before using **Risk Accepted** or **False Positive**.
+</Warning>
+
+## Troubleshooting
+
+### Triage controls do not appear
+
+Make sure the row is an individual finding row. Finding Groups rows do not show triage controls. Expand a group to see affected resources and their triage controls.
+
+### Changes cannot be saved
+
+Confirm that the user role has **Manage Scans** permission. Prowler Local Server does not support Findings Triage writes.
+
+### Resolved or Reopened is missing from the selector
+
+This is expected. Prowler sets **Resolved** and **Reopened** automatically from scan result changes.
+
+### Risk Accepted or False Positive muted a finding
+
+This is expected. Those statuses create a mute rule through Mutelist.
diff --git a/docs/user-guide/tutorials/prowler-app-github-action.mdx b/docs/user-guide/tutorials/prowler-app-github-action.mdx
index 5b80511b89..c874a37164 100644
--- a/docs/user-guide/tutorials/prowler-app-github-action.mdx
+++ b/docs/user-guide/tutorials/prowler-app-github-action.mdx
@@ -18,7 +18,7 @@ Source: [`prowler-cloud/prowler`](https://github.com/prowler-cloud/prowler) · M
| `provider` | yes | — | Cloud provider to scan (`aws`, `azure`, `gcp`, `github`, `kubernetes`, `iac`, `cloudflare`, etc.) |
| `image-tag` | no | `stable` | Docker image tag — `stable` (latest release), `latest` (master, not stable), or `<x.y.z>` (pinned). See [available tags](https://hub.docker.com/r/prowlercloud/prowler/tags). |
| `output-formats` | no | `json-ocsf` | Output format(s) for scan results. Space-separated (e.g. `sarif json-ocsf`) |
-| `push-to-cloud` | no | `false` | Push findings to [Prowler Cloud](/user-guide/tutorials/prowler-app-import-findings). When `true`, `PROWLER_CLOUD_API_KEY` is auto-forwarded |
+| `push-to-cloud` | no | `false` | Push findings to [Prowler Cloud](/user-guide/tutorials/prowler-import-findings). When `true`, `PROWLER_CLOUD_API_KEY` is auto-forwarded |
| `flags` | no | `""` | Additional CLI flags (e.g. `--severity critical high`). Values with spaces can be quoted: `--resource-tag 'Environment=My Server'` |
| `extra-env` | no | `""` | Space-, newline-, or comma-separated list of env var **names** to forward to the container (see [Authentication](#authentication)) |
| `upload-sarif` | no | `false` | Upload SARIF results to GitHub Code Scanning |
@@ -43,7 +43,7 @@ Source: [`prowler-cloud/prowler`](https://github.com/prowler-cloud/prowler) · M
### Push findings to Prowler Cloud
-Send scan results directly to [Prowler Cloud](/user-guide/tutorials/prowler-app-import-findings) for centralized visibility, compliance tracking, and team collaboration.
+Send scan results directly to [Prowler Cloud](/user-guide/tutorials/prowler-import-findings) for centralized visibility, compliance tracking, and team collaboration.
```yaml
- uses: prowler-cloud/prowler@5.25
diff --git a/docs/user-guide/tutorials/prowler-app-jira-integration.mdx b/docs/user-guide/tutorials/prowler-app-jira-integration.mdx
index 01779a6a96..83554ee8c0 100644
--- a/docs/user-guide/tutorials/prowler-app-jira-integration.mdx
+++ b/docs/user-guide/tutorials/prowler-app-jira-integration.mdx
@@ -1,13 +1,17 @@
---
title: "Jira Integration"
+sidebarTitle: 'Jira'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.12.0" />
-Prowler App enables automatic export of security findings to Jira, providing seamless integration with Atlassian's work item tracking and project management platform. This comprehensive guide demonstrates how to configure and manage Jira integrations to streamline security incident management and enhance team collaboration across security workflows.
+<AppliesTo />
-Integrating Prowler App with Jira provides:
+Prowler Cloud enables automatic export of security findings to Jira, providing seamless integration with Atlassian's work item tracking and project management platform. This comprehensive guide demonstrates how to configure and manage Jira integrations to streamline security incident management and enhance team collaboration across security workflows.
+
+Integrating Prowler Cloud with Jira provides:
* **Streamlined management:** Convert security findings directly into actionable Jira work items
* **Enhanced team collaboration:** Leverage existing project management workflows for security remediation
@@ -22,9 +26,9 @@ When enabled and configured:
## Configuration
-To configure Jira integration in Prowler App:
+To configure Jira integration in Prowler Cloud:
-1. Navigate to **Integrations** in the Prowler App interface
+1. Navigate to **Integrations** in Prowler Cloud
2. Locate the **Jira** card and click **Manage**, then select **Add integration**
@@ -50,7 +54,7 @@ Once configured successfully, the integration is ready to send findings to Jira.
To manually send individual findings to Jira:
-1. Navigate to the **Findings** section in Prowler App
+1. Navigate to the **Findings** section in Prowler Cloud
2. Select one finding you want to export
3. Click the action button on the table row and select **Send to Jira**
4. Select the Jira integration and project
diff --git a/docs/user-guide/tutorials/prowler-app-lighthouse-multi-llm.mdx b/docs/user-guide/tutorials/prowler-app-lighthouse-multi-llm.mdx
index 0a0179ee79..eee7564bcb 100644
--- a/docs/user-guide/tutorials/prowler-app-lighthouse-multi-llm.mdx
+++ b/docs/user-guide/tutorials/prowler-app-lighthouse-multi-llm.mdx
@@ -1,5 +1,6 @@
---
title: 'Using Multiple LLM Providers with Lighthouse'
+sidebarTitle: 'Multiple LLM Providers'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
@@ -32,13 +33,13 @@ All three providers can be configured for a tenant, but only one can be set as t
When visiting Lighthouse AI chat, the default provider's default model loads automatically. Users can switch to any available LLM model (including those from non-default providers) using the dropdown in chat.
-<img src="/images/prowler-app/lighthouse-switch-models.png" alt="Switch models in Lighthouse AI chat interface" />
+<img src="/images/prowler-app/lighthouse/oss/switch-models.png" alt="Switch models in Lighthouse AI chat interface" />
## Configuring Providers
Navigate to **Configuration** → **Lighthouse AI** to see all three provider options with a **Connect** button under each.
-<img src="/images/prowler-app/lighthouse-configuration.png" alt="Prowler Lighthouse Configuration" />
+<img src="/images/prowler-app/lighthouse/oss/configuration.png" alt="Prowler Lighthouse Configuration" />
### Connecting a Provider
@@ -128,6 +129,25 @@ To connect a provider:
3. Configure in Lighthouse AI:
- **API Key**: OpenRouter API key
- **Base URL**: `https://openrouter.ai/api/v1`
+
+ ### Base URL Validation
+
+ To prevent server-side request forgery (SSRF), Prowler API validates the base URL before connecting to it:
+
+ - The URL must use HTTPS.
+ - The host must resolve to a public IP address. Private, loopback, link-local, and cloud metadata addresses are rejected.
+
+ <Warning>
+ This validation can break configurations that point to internal endpoints, such as a self-hosted Ollama server. This is intentional: it fixes a security issue where the Prowler API could be directed to internal services. Internal endpoints must now be allowed explicitly through `LIGHTHOUSE_AI_OPENAI_COMPATIBLE_ALLOWED_HOSTS`.
+ </Warning>
+
+ To allow internal endpoints, set a comma-separated list of hostnames or IP addresses in the Prowler API environment (for Docker Compose deployments, the shared `.env` file):
+
+ ```bash
+ LIGHTHOUSE_AI_OPENAI_COMPATIBLE_ALLOWED_HOSTS=custom-openai.internal,10.0.0.20
+ ```
+
+ Hosts in this list skip the public-endpoint validation. HTTPS is still required, so the endpoint needs a certificate the Prowler API trusts.
</Tab>
</Tabs>
@@ -139,7 +159,7 @@ To set a different provider as default:
2. Click **Configure** under the desired provider to set as default
3. Click **Set as Default**
-<img src="/images/prowler-app/lighthouse-set-default-provider.png" alt="Set default LLM provider" />
+<img src="/images/prowler-app/lighthouse/oss/set-default-provider.png" alt="Set default LLM provider" />
## Updating Provider Credentials
diff --git a/docs/user-guide/tutorials/prowler-app-lighthouse.mdx b/docs/user-guide/tutorials/prowler-app-lighthouse.mdx
index b119893cb5..5b4a0f5847 100644
--- a/docs/user-guide/tutorials/prowler-app-lighthouse.mdx
+++ b/docs/user-guide/tutorials/prowler-app-lighthouse.mdx
@@ -8,6 +8,10 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
Prowler Lighthouse AI integrates Large Language Models (LLMs) with Prowler security findings data.
+<Info>
+Using Prowler Cloud? Lighthouse AI on Prowler Cloud adds persistent chat sessions, GPT-5.5 as the default model, a dedicated agentic (chat) view, and transparent reasoning. See [Lighthouse AI on Prowler Cloud](/getting-started/products/prowler-cloud-lighthouse).
+</Info>
+
Behind the scenes, Lighthouse AI works as follows:
- Lighthouse AI runs as a [Langchain agent](https://docs.langchain.com/oss/javascript/langchain/agents) in NextJS
@@ -15,7 +19,7 @@ Behind the scenes, Lighthouse AI works as follows:
- The agent accesses Prowler data through [Prowler MCP](https://docs.prowler.com/getting-started/products/prowler-mcp), which exposes tools from multiple sources, including:
- Prowler Hub
- Prowler Docs
- - Prowler App
+ - Prowler Local Server
- Instead of calling every tool directly, the agent uses two meta-tools:
- `describe_tool` to retrieve a tool schema and parameter requirements.
- `execute_tool` to run the selected tool with the required input.
@@ -47,7 +51,7 @@ Getting started with Prowler Lighthouse AI is easy:
For detailed configuration instructions for each provider, see [Using Multiple LLM Providers with Lighthouse](/user-guide/tutorials/prowler-app-lighthouse-multi-llm).
</Note>
-<img src="/images/prowler-app/lighthouse-configuration.png" alt="Lighthouse AI Configuration" />
+<img src="/images/prowler-app/lighthouse/oss/configuration.png" alt="Lighthouse AI Configuration" />
### Adding Business Context
diff --git a/docs/user-guide/tutorials/prowler-app-multi-tenant.mdx b/docs/user-guide/tutorials/prowler-app-multi-tenant.mdx
index 26f73000b3..8de9365fe9 100644
--- a/docs/user-guide/tutorials/prowler-app-multi-tenant.mdx
+++ b/docs/user-guide/tutorials/prowler-app-multi-tenant.mdx
@@ -1,12 +1,16 @@
---
title: 'Managing Organizations (Multi-Tenant)'
+sidebarTitle: 'Organizations'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.23.0" />
-Prowler App supports multi-tenancy through **Organizations**, allowing users to belong to multiple isolated environments within a single account. Each organization maintains its own providers, scans, findings, and user memberships, ensuring complete data separation between teams or business units.
+<AppliesTo />
+
+Prowler Cloud supports multi-tenancy through **Organizations**, allowing users to belong to multiple isolated environments within a single account. Each organization maintains its own providers, scans, findings, and user memberships, ensuring complete data separation between teams or business units.
## Key Concepts
@@ -67,7 +71,14 @@ The currently active organization is indicated by an **Active** badge. Switching
## Editing an Organization Name
-Organization owners with the **Manage Account** permission can rename an organization:
+Renaming an organization requires **both** of the following conditions to be met:
+
+* The user's **membership role** in that organization must be `owner` (visible as the `owner` badge in the Organizations card).
+* The user must have a role that grants the **Manage Account** permission.
+
+Users who only meet one of the two conditions will not see the **Edit** button. For example, a user whose membership role is `member` will not see the **Edit** button even if their role grants `Manage Account`.
+
+To rename an organization:
1. Navigate to the **Profile** page.
@@ -121,7 +132,7 @@ When invited to join an organization, the invited user receives a link to accept
1. Open the invitation link.
-2. If already authenticated, the invitation is accepted automatically and the user is redirected to Prowler App.
+2. If already authenticated, the invitation is accepted automatically and the user is redirected to Prowler Cloud.
3. If not authenticated, choose **I have an account -- Sign in**, authenticate with existing credentials, and the invitation is accepted upon sign-in.
@@ -175,6 +186,6 @@ If the expelled organization was the user's **only** organization, the account i
| View organizations | Any authenticated user |
| Create an organization | Any authenticated user |
| Switch organizations | Any authenticated user |
-| Edit organization name | Organization owner with **Manage Account** permission |
-| Delete an organization | Organization owner with **Manage Account** permission; must belong to more than one organization |
+| Edit organization name | Membership role `owner` **and** a role with **Manage Account** permission |
+| Delete an organization | Membership role `owner` **and** a role with **Manage Account** permission; must belong to more than one organization |
| Expel a user from an organization | Organization owner (no additional permission required); last remaining owner cannot expel themselves |
diff --git a/docs/user-guide/tutorials/prowler-app-mute-findings.mdx b/docs/user-guide/tutorials/prowler-app-mute-findings.mdx
index 82623b54cf..c2ada47e9c 100644
--- a/docs/user-guide/tutorials/prowler-app-mute-findings.mdx
+++ b/docs/user-guide/tutorials/prowler-app-mute-findings.mdx
@@ -1,11 +1,14 @@
---
-title: 'Advanced Mutelist (YAML)'
+title: 'Advanced Mutelist'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.9.0" />
-Prowler App allows users to mute specific findings to focus on the most critical security issues. This guide demonstrates how to use the Advanced Mutelist feature with YAML configuration for complex, pattern-based muting rules.
+<AppliesTo />
+
+Prowler Cloud allows users to mute specific findings to focus on the most critical security issues. This guide demonstrates how to use the Advanced Mutelist feature with YAML configuration for complex, pattern-based muting rules.
<Note>
For muting individual findings without YAML configuration, use [Simple Mutelist](/user-guide/tutorials/prowler-app-simple-mutelist) to mute findings directly from the Findings table.
@@ -31,8 +34,8 @@ Advanced Mutelist requires the **Manage Account** permission. See [RBAC Administ
Before muting findings, ensure:
-- Valid access to Prowler App with appropriate permissions
-- A provider added to the Prowler App
+- Valid access to Prowler Cloud with appropriate permissions
+- A provider added to Prowler Cloud
- Understanding of the security implications of muting specific findings
<Warning>
@@ -43,7 +46,7 @@ Muting findings does not resolve underlying security issues. Review each finding
To configure Advanced Mutelist:
-1. Log into Prowler App
+1. Log into Prowler Cloud
2. Navigate to the Providers page
3. Connect a provider to enable Mutelist configuration
@@ -423,7 +426,7 @@ Mutelist:
### Priority: Advanced vs. Simple Mutelist
-When both Advanced Mutelist (YAML) and [Simple Mutelist](/user-guide/tutorials/prowler-app-simple-mutelist) rules match the same finding, the **Advanced Mutelist takes higher priority**. The finding will be muted with the reason "Muted by mutelist". If a finding is not matched by the Advanced Mutelist but matches a Simple Mutelist rule, the Simple rule's custom justification is used instead.
+When both Advanced Mutelist and [Simple Mutelist](/user-guide/tutorials/prowler-app-simple-mutelist) rules match the same finding, the **Advanced Mutelist takes higher priority**. The finding will be muted with the reason "Muted by mutelist". If a finding is not matched by the Advanced Mutelist but matches a Simple Mutelist rule, the Simple rule's custom justification is used instead.
### Best Practices
@@ -436,7 +439,7 @@ When both Advanced Mutelist (YAML) and [Simple Mutelist](/user-guide/tutorials/p
### Validation
-Prowler App validates your mutelist configuration and will display errors for:
+Prowler Cloud validates the mutelist configuration and will display errors for:
- Invalid YAML syntax
- Missing required fields
diff --git a/docs/user-guide/tutorials/prowler-app-rbac.mdx b/docs/user-guide/tutorials/prowler-app-rbac.mdx
index cccbbc27cc..4533e0423c 100644
--- a/docs/user-guide/tutorials/prowler-app-rbac.mdx
+++ b/docs/user-guide/tutorials/prowler-app-rbac.mdx
@@ -1,12 +1,16 @@
---
title: 'Managing Users and Role-Based Access Control (RBAC)'
+sidebarTitle: 'Users & RBAC'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.1.0" />
-**Prowler App** supports multiple users within a single tenant, enabling seamless collaboration by allowing team members to easily share insights and manage security findings.
+<AppliesTo />
+
+**Prowler Cloud** supports multiple users within a single tenant, enabling seamless collaboration by allowing team members to easily share insights and manage security findings.
[Roles](#roles) help you control user permissions, determining what actions each user can perform and the data they can access within Prowler. By default, each account includes an immutable **admin** role, ensuring that your account always retains administrative access.
@@ -40,6 +44,11 @@ Follow these steps to edit a user of your account:
<img src="/images/prowler-app/rbac/user_edit_details.png" alt="Edit User Details" width="700" />
+<Note>
+Users can edit their own account details. Editing another user's account details requires the **Invite and Manage Users** or **admin** permission.
+
+</Note>
+
#### Removing a User
Follow these steps to remove a user of your account:
@@ -47,7 +56,11 @@ Follow these steps to remove a user of your account:
1. Navigate to **Users** from the side menu.
2. Click the delete button of your current user.
-> **Note: Each user will be able to delete himself and not others, regardless of his permissions.**
+> **Note: Each user can only delete their own account, regardless of their permissions. For this reason, the delete button is only shown on your own row and not on other users' rows.**
+
+Deleting a user removes the **entire user account** from Prowler, not just its membership in your organization. Because a single account can belong to more than one tenant, allowing one administrator to delete it outright could affect organizations they don't manage and irreversibly remove another person's identity. To keep this destructive action under the control of the account owner, the API only permits a user to delete themselves (it rejects any other target with a `400` response), and the UI mirrors this by showing the delete button exclusively on your own row.
+
+To remove **another** user from your organization, use the [_Expel from organization_](/user-guide/tutorials/prowler-app-multi-tenant#expelling-a-user-from-an-organization) action instead. Expelling removes the user's membership, role grants, and active sessions for your tenant only, and deletes the underlying account just for that user if your organization was their last remaining membership. This action is reserved for tenant **owners**.
<img src="/images/prowler-app/rbac/user_remove.png" alt="Remove User" width="700" />
@@ -115,7 +128,7 @@ To resend the invitation to the user, it is necessary to explicitly **delete the
## Managing Groups and Roles
-The Roles section in Prowler is designed to facilitate the assignment of custom user privileges. This section allows administrators to define roles with specific permissions for Prowler administrative tasks and Account visibility.
+Roles combine administrative permissions with provider visibility. Administrative permissions control the actions a role can perform. Provider Groups and Unlimited Visibility control the providers, resources, findings, scans, and compliance results the role can access.
<Note>
**Only users that have the _Manage Account_ or _admin_ permission can access this section.**
@@ -123,47 +136,53 @@ The Roles section in Prowler is designed to facilitate the assignment of custom
</Note>
### Provider Groups
-Provider Groups control visibility across specific providers. When creating a new role, you can assign specific groups to define their Provider visibility. This ensures that users with that role have access only to the Providers that are required.
+Provider Groups limit visibility to selected providers. Assigning one or more Provider Groups to a role grants access to the providers in those groups and their resources, findings, scans, and compliance results.
-By default, a new user role does not have visibility into any group.
+New roles have no provider visibility by default. Assign at least one Provider Group or enable **Unlimited Visibility** before assigning the role to users who need access to provider data.
-Alternatively, to grant the role unlimited visibility across all providers, check the Grant Unlimited Visibility checkbox.
+**Unlimited Visibility** grants organization-wide visibility across every provider, regardless of the Provider Groups assigned to the role. It does not grant administrative permissions.
#### Creating a Provider Group
Follow these steps to create a provider group in your account:
-1. Navigate to **Provider Groups** from the side menu..
+1. Click **Providers** in the side menu.
-2. In this view you can select the provider groups you want to assign to one or more roles.
+2. Select the **Provider Groups** tab.
-3. Click the **Create Group** button on the center of the screen.
+3. Enter a group name in the **Create a new provider group** form.
- <img src="/images/prowler-app/rbac/provider_group.png" alt="Create Provider Group" width="700" />
+4. Select the providers that the group controls. Optionally, select the roles that should use the group.
+
+5. Click **Create Group**.
+
+ <img src="/images/prowler-app/rbac/provider_group.png" alt="Create a Provider Group" width="700" />
#### Editing a Provider Group
Follow these steps to edit a provider group on your account:
-1. Navigate to **Provider Groups** from the side menu.
+1. Click **Providers** in the side menu and select the **Provider Groups** tab.
-2. Click the edit button of the provider group you want to modify.
+2. Open the actions menu for the Provider Group and click **Edit Provider Group**.
- <img src="/images/prowler-app/rbac/provider_group_edit.png" alt="Edit Provider Group" width="700" />
+ <img src="/images/prowler-app/rbac/provider_group_edit.png" alt="Edit Provider Group action" width="300" />
-3. Change the provider group parameters you need and save the changes.
+3. Update the group name, providers, or roles, and save the changes.
- <img src="/images/prowler-app/rbac/provider_group_edit_1.png" alt="Edit Provider Group Details" width="700" />
+ <img src="/images/prowler-app/rbac/provider_group_edit_1.png" alt="Edit Provider Group form" width="700" />
#### Removing a Provider Group
-Follow these steps to remove a provider group of your account:
+Follow these steps to remove a provider group from your account:
-1. Navigate to **Provider Groups** from the side menu.
+1. Click **Providers** in the side menu and select the **Provider Groups** tab.
-2. Click on the delete button of the provider group you want to remove.
+2. Open the actions menu for the Provider Group and click **Delete Provider Group**.
- <img src="/images/prowler-app/rbac/provider_group_remove.png" alt="Remove Provider Group" width="700" />
+3. Confirm the deletion.
+
+ <img src="/images/prowler-app/rbac/provider_group_remove.png" alt="Delete Provider Group confirmation" width="700" />
### Roles
@@ -173,19 +192,20 @@ Follow these steps to create a role for your account:
1. Navigate to **Roles** from the side menu.
-2. Click on the **Add Role** button on the top right-hand corner of the screen.
+2. Click **Add Role**.
- <img src="/images/prowler-app/rbac/role_create.png" alt="Create Role" width="700" />
+3. Enter the role name and select the required administrative permissions.
-3. In the Add Role screen, enter the role name, the administration permissions and the groups of providers to which the Role will have access to.
-
-4. In the Groups and Account Visibility section, you will see a list of available groups with checkboxes next to them. To assign a group to the user role, simply click the checkbox next to the group name. If you need to assign multiple groups, repeat the process for each group you wish to add.
+4. Configure **Visibility**:
+ - To grant organization-wide visibility, select **Enable Unlimited Visibility for this role**.
+ - To limit visibility, leave Unlimited Visibility cleared and select one or more Provider Groups.
<img src="/images/prowler-app/rbac/role_create_1.png" alt="Role parameters" width="700" />
+5. Click **Add Role**.
<Note>
-To assign read-only access, select only the `Unlimited Visibility` permission when creating the role. Then, go to the Users page and assign this role to the appropriate user.
+To grant read-only access across the organization, enable **Unlimited Visibility** without selecting administrative permissions. Then, assign the role from the **Users** page.
</Note>
#### Editing a Role
@@ -194,25 +214,21 @@ Follow these steps to edit a role on your account:
1. Navigate to **Roles** from the side menu.
-2. Click on the edit button of the role you want to modify.
+2. Open the actions menu for the role and click **Edit Role**.
- <img src="/images/prowler-app/rbac/role_edit.png" alt="Edit Role" width="700" />
-
-3. Adjust the settings as needed and save the changes.
-
- <img src="/images/prowler-app/rbac/role_edit_details.png" alt="Edit Role Details" width="700" />
+3. Update the role name, administrative permissions, Unlimited Visibility setting, or Provider Groups.
+4. Save the changes.
#### Removing a Role
-Follow these steps to remove a role of your account:
+Follow these steps to remove a role from your account:
1. Navigate to **Roles** from the side menu.
-2. Click on the delete button of the role you want to remove.
-
- <img src="/images/prowler-app/rbac/role_remove.png" alt="Remove Role" width="700" />
+2. Open the actions menu for the role and click **Delete Role**.
+3. Confirm the deletion.
## RBAC Administrative Permissions
@@ -222,8 +238,8 @@ Assign administrative permissions by selecting from the following options:
|------------|-------|-------------|
| Invite and Manage Users | All | Invite new users and manage existing ones. |
| Manage Account | All | Adjust account settings, delete users and read/manage users permissions. |
-| Manage Scans | All | Run and review scans. |
-| Manage Providers | All | Add or modify connected providers. |
+| Manage Scans | All | Run and review scans, and manage [Scan Configuration](/user-guide/tutorials/prowler-app-scan-configuration) settings. |
+| Manage Providers | All | Add or modify connected providers, and attach or detach providers from a [Scan Configuration](/user-guide/tutorials/prowler-app-scan-configuration) (in addition to Manage Scans). |
| Manage Integrations | All | Add or modify the Prowler Integrations. |
| Manage Ingestions | Prowler Cloud | Allow or deny the ability to submit findings ingestion batches via the API. |
| Manage Billing | Prowler Cloud | Access and manage billing settings and subscription information. |
@@ -239,7 +255,7 @@ To grant all administrative permissions, select the **Grant all admin permission
The following permissions are available exclusively in **Prowler Cloud**:
-**Manage Ingestions:** Submit and manage findings ingestion jobs via the API. Required to upload OCSF scan results using the `--push-to-cloud` CLI flag or the ingestion endpoints. See [Import Findings](/user-guide/tutorials/prowler-app-import-findings) for details.
+**Manage Ingestions:** Submit and manage findings ingestion jobs via the API. Required to upload OCSF scan results using the `--push-to-cloud` CLI flag or the ingestion endpoints. See [Import Findings](/user-guide/tutorials/prowler-import-findings) for details.
**Manage Billing:** Access and manage billing settings, subscription plans, and payment methods.
diff --git a/docs/user-guide/tutorials/prowler-app-s3-integration.mdx b/docs/user-guide/tutorials/prowler-app-s3-integration.mdx
index 284b10eaaf..9b7d7a9a2e 100644
--- a/docs/user-guide/tutorials/prowler-app-s3-integration.mdx
+++ b/docs/user-guide/tutorials/prowler-app-s3-integration.mdx
@@ -1,12 +1,16 @@
---
title: 'Amazon S3 Integration'
+sidebarTitle: 'Amazon S3'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.10.0" />
-**Prowler App** allows automatic export of scan results to Amazon S3 buckets, providing seamless integration with existing data workflows and storage infrastructure. This comprehensive guide demonstrates configuration and management of Amazon S3 integrations to streamline security finding management and reporting.
+<AppliesTo />
+
+**Prowler Cloud** allows automatic export of scan results to Amazon S3 buckets, providing seamless integration with existing data workflows and storage infrastructure. This comprehensive guide demonstrates configuration and management of Amazon S3 integrations to streamline security finding management and reporting.
When enabled and configured, scan results are automatically stored in the configured bucket. Results are provided in `csv`, `html` and `json-ocsf` formats, offering flexibility for custom integrations:
@@ -201,7 +205,7 @@ Replace `<SOURCE ACCOUNT ID>` with the AWS account ID that contains the IAM role
</Note>
### Available Templates
-**Prowler App** provides Infrastructure as Code (IaC) templates to automate IAM role setup with S3 integration permissions.
+**Prowler Cloud** provides Infrastructure as Code (IaC) templates to automate IAM role setup with S3 integration permissions.
<Note>
Templates are optional. Custom IAM roles or static credentials can be used instead.
@@ -259,8 +263,8 @@ If using Prowler's CloudFormation template, execute the following command to upd
- `EnableS3Integration`: Select "true"
- `S3IntegrationBucketName`: Your bucket name
- `S3IntegrationBucketAccountId`: Bucket owner's AWS account ID
-5. In the "Configure stack options" screen, again, leave everything as it is and click on "Next"
-6. Finally, under "Review Prowler", at the bottom click on "Submit"
+5. In the "Configure stack options" screen, again, leave everything as it is and click "Next"
+6. Finally, under "Review Prowler", at the bottom click "Submit"
#### Terraform
@@ -278,7 +282,7 @@ If using Prowler's CloudFormation template, execute the following command to upd
3. Edit `terraform.tfvars` with your specific values:
```hcl
- # Required: External ID from Prowler App
+ # Required: External ID from Prowler Cloud
external_id = "your-unique-external-id-here"
# S3 Integration Configuration
@@ -310,11 +314,11 @@ For detailed information, refer to the [Terraform README](https://github.com/pro
## Configuration
-Once the required permissions are set up, proceed to configure the S3 integration in **Prowler App**.
+Once the required permissions are set up, proceed to configure the S3 integration in **Prowler Cloud**.
1. Navigate to "Integrations"
-2. Locate the Amazon S3 Integration card and click on the "Configure" button
+2. Locate the Amazon S3 Integration card and click the "Configure" button
3. Click the "Add Integration" button
diff --git a/docs/user-guide/tutorials/prowler-app-scan-configuration.mdx b/docs/user-guide/tutorials/prowler-app-scan-configuration.mdx
new file mode 100644
index 0000000000..60e0db2f4c
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-app-scan-configuration.mdx
@@ -0,0 +1,231 @@
+---
+title: 'Scan Configuration'
+sidebarTitle: 'Configuration'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+<VersionBadge version="5.32.0" />
+
+Scan Configuration lets you override, per provider, specific values in the default configuration Prowler's checks use during a scan. Each configuration can modify how specific checks behave, such as thresholds, allowed values, and retention windows, or exclude checks and services from the scan scope. Attach it to the providers that should use it on their next scan.
+
+<SubscriptionBanner />
+
+## What Is a Scan Configuration?
+
+A Scan Configuration lets you **override specific values, per provider**, on top of Prowler's defaults. It's merged with those defaults, not a full replacement:
+
+- A provider type you don't add a section for keeps using `config.yaml` untouched.
+- **A provider type you do add a section for has its keys merged over `config.yaml` for that provider.** Only the keys you set are overridden; every key you leave out keeps its default from `config.yaml`, because each check falls back to the default configuration when a value isn't provided. See [How It's Applied](#how-its-applied) for details.
+- It is stored per organization and applied to the **providers you attach** to it.
+- **Attaching a provider is optional at creation time.** You can save a Scan Configuration with no providers attached and associate them later, either from the configuration's editor or from the **Providers** page (see [Attaching Providers](#attaching-providers)). It has no effect on any scan until at least one provider is attached.
+- A provider can be attached to **at most one** Scan Configuration at a time.
+- Changes take effect on the provider's **next scan** and do not re-run past scans.
+
+
+<Note>
+The full set of configurable values and their defaults lives in [`prowler/config/config.yaml`](https://github.com/prowler-cloud/prowler/blob/master/prowler/config/config.yaml). For what each key means and which checks read it, see the [Configuration File tutorial](/user-guide/cli/tutorials/configuration_file).
+</Note>
+
+## Required Permissions
+
+Scan Configuration access is governed by Role-Based Access Control (RBAC). See [RBAC Administrative Permissions](/user-guide/tutorials/prowler-app-rbac#rbac-administrative-permissions) for details on each permission.
+
+- **Viewing** a Scan Configuration doesn't require any specific permission.
+- **Creating, editing, and deleting** a Scan Configuration requires the **Manage Scans** permission.
+- **Attaching or detaching providers** requires the **Manage Providers** permission as well, in addition to Manage Scans. This applies to explicit changes to the attached providers, and to deleting a Scan Configuration that still has providers attached (deleting it detaches them too).
+- Attaching or detaching a provider also requires that provider to be **visible to your role**. Visibility comes from the [Provider Groups](/user-guide/tutorials/prowler-app-rbac#provider-groups) assigned to your role, or from **Unlimited Visibility**. You can't attach a provider you can't see, and you can't detach one either, whether by removing it from the list or by deleting the Scan Configuration it's attached to.
+
+## Config Schema
+
+The YAML follows the structure of `config.yaml`: a mapping keyed by provider, with each provider section holding the keys you want to change. You only list the keys you want to override; they're merged over that provider's `config.yaml` defaults.
+
+```yaml
+aws:
+ max_unused_access_keys_days: 30
+ max_console_access_days: 30
+ max_security_group_rules: 25
+
+azure:
+ defender_attack_path_minimal_risk_level: "Critical"
+
+gcp:
+ storage_min_retention_days: 30
+```
+
+### Limiting the Scan Scope
+
+<VersionBadge version="5.35.0" />
+
+Use `excluded_checks` to skip individual checks and `excluded_services` to skip every check in a service for the matching provider type:
+
+```yaml
+aws:
+ excluded_checks:
+ - s3_bucket_public_access
+ excluded_services:
+ - ec2
+```
+
+<Warning>
+When a Scan Configuration excludes checks or services, Prowler calculates overviews, aggregations, and other result-based information from the reduced scan scope. The displayed information reflects only the checks and services that ran, not a complete assessment of the provider. Consider the applied Scan Configuration when interpreting totals and security posture.
+</Warning>
+
+## Creating a Scan Configuration
+
+<Steps>
+ <Step title="Open the editor">
+ On the **Scan** page (under **Configuration**), click **New Scan Configuration**.
+ </Step>
+ <Step title="Name it">
+ Give the configuration a descriptive **Name** (3–100 characters), e.g. `stricter-iam-aws`.
+ </Step>
+ <Step title="Write the configuration file">
+ In the **Configuration (YAML)** field, add the keys you want to change, grouped by provider. Only the keys you set are overridden; every other key keeps its `config.yaml` default. The editor is pre-filled with a representative default placeholder you can use as a starting point.
+ </Step>
+ <Step title="Attach providers (optional)">
+ Under **Attach to providers**, pick the providers that should use this configuration. This is optional, you can save without any provider and attach them later, either by editing this configuration or from the **Providers** page (see [Attaching Providers](#attaching-providers)).
+ </Step>
+ <Step title="Save">
+ Click **Save**. The server validates the configuration values and, if everything is valid, stores it and attaches the selected providers.
+ </Step>
+</Steps>
+
+<Tip>
+You don't need to fill in every provider. A section you don't include leaves that provider's `config.yaml` untouched. Within a section you do include, only add the keys you want to change; the rest keep their `config.yaml` defaults. The placeholder shown in the editor is just an example; if you leave the field with only the placeholder (greyed-out) text, nothing is saved.
+</Tip>
+
+## How Validation Works
+
+Prowler checks your configuration in two stages, the same way the Advanced Mutelist editor does:
+
+1. **As you type: is it well-formed?** The editor checks that what you've written is valid YAML. If something is off, you'll see an `Invalid YAML format` message and **Save** stays disabled until you fix it. Once it's clean, it shows **Valid YAML format**.
+2. **When you save: are the values allowed?** Saving checks that each value is one Prowler accepts, the right type, within range, and one of the allowed options where a key only takes a fixed set of choices. If a value isn't allowed, the editor points to the exact key and explains why, right beneath the field, so you can correct it and save again.
+
+For example, `azure.defender_attack_path_minimal_risk_level` only accepts `Low`, `Medium`, `High`, or `Critical`. Saving any other value returns an inline error like:
+
+```
+azure.defender_attack_path_minimal_risk_level: Input should be 'Low', 'Medium', 'High' or 'Critical'
+```
+
+<Warning>
+**Valid YAML format** only means the text is well-formed; it doesn't mean your values are accepted. Those are checked when you save.
+
+Be careful with indentation. A line like `azure: defender_attack_path_minimal_risk_level: Critical` (no line break and indent after `azure:`) is still valid YAML, but Prowler reads it as one long key name instead of a setting inside the `azure` section, so the value is silently ignored. Always nest provider keys:
+
+```yaml
+azure:
+ defender_attack_path_minimal_risk_level: "Critical"
+```
+</Warning>
+
+<Info>
+Prowler won't flag a section or key it doesn't recognize. It accepts them without error, so custom checks and plugins can add their own settings. The trade-off: a typo in a key or section name isn't rejected either, and that misspelled setting simply won't apply. Double-check your spelling against `config.yaml`.
+</Info>
+
+## Attaching Providers
+
+A Scan Configuration only has an effect once it's attached to one or more providers. There are two ways to manage attachments.
+
+### From the Scan Config Editor
+
+In the **Attach to providers** field, select the providers that should use this configuration. Providers already attached to **another** configuration are hidden from the selector, since each provider can belong to only one configuration at a time.
+
+### From the Provider's Row Menu
+
+You can also manage a provider's configuration from **Providers**:
+
+<Steps>
+ <Step title="Open the provider menu">
+ On the **Providers** page, open the **⋮** menu on a provider row.
+ </Step>
+ <Step title="Click **Edit Scan Configuration**.">
+ </Step>
+ <Step title="Pick a configuration">
+ In the dialog, pick a configuration from the dropdown to apply it (picking a different one moves the provider), or pick **Default** to detach it and go back to the built-in `config.yaml` defaults. Then click **Save**.
+ </Step>
+</Steps>
+
+<Note>
+This dialog only **associates or disassociates** an existing configuration. To create or edit the configuration's YAML, use the **Scan Config** view (a link is provided in the dialog).
+</Note>
+
+<Info>
+Because a provider can belong to only one configuration, associating a provider that is already attached elsewhere **moves** it to the new configuration automatically; it is removed from the previous one.
+</Info>
+
+## Editing and Deleting
+
+On the **Scan Config** page, open the **⋮** menu on a configuration row:
+
+- **Edit:** Choose **Edit** to open the editor, change its name, YAML, or attached providers, and click **Update**. Editing the YAML always happens here, never from the provider row.
+- **Delete:** Choose **Delete** (in the danger zone) and confirm. Providers that were attached fall back to the built-in defaults from `config.yaml` on their next scan.
+
+## How It's Applied
+
+When a scan runs for a provider:
+
+1. If the provider is attached to a Scan Configuration **and that configuration has a section for the provider's type** (e.g. `aws` for an AWS provider), Prowler merges that section over `config.yaml` for that provider's scan: the keys you set win, and every key you didn't set keeps its `config.yaml` default.
+2. If the provider is attached to a Scan Configuration, but that configuration **has no section for the provider's type** (for example, a configuration that only defines an `aws` section, attached to a GCP provider), the scan uses the built-in defaults from `config.yaml` for that provider, exactly as if no Scan Configuration were attached at all.
+3. If the provider isn't attached to any Scan Configuration, the built-in defaults from `config.yaml` are used.
+
+<Note>
+The merge is per key. A key you don't set keeps its `config.yaml` default, because each check falls back to the default configuration when a value isn't provided. You only need to list the keys you want to change.
+</Note>
+
+<Tip>
+A single Scan Configuration can hold sections for several provider types at once (see [Config Schema](#config-schema)) and be attached to providers of different types. Each provider only ever picks up the section matching its own type; the rest of the YAML is ignored for that provider.
+</Tip>
+
+## Effect on Compliance Results
+
+Some compliance requirements only hold if the checks they map to ran with a strict-enough configuration. For example, a requirement expecting unused access keys to be disabled within 45 days loses its meaning if a Scan Configuration raises `max_unused_access_keys_days` to 120: the check would still PASS, but the requirement wouldn't really be met.
+
+When a scan's applied configuration doesn't meet a requirement's expectations, Prowler marks that requirement as **FAIL** on the Compliance page, even if every individual finding passed. The requirement shows an info icon (and, when expanded, an inline alert) with:
+
+> Marked as FAIL because the applied scan configuration does not meet this requirement, even though all findings passed.
+
+This only affects requirements built around a configurable check that declares this kind of expectation; requirements without one are never affected by an attached Scan Configuration.
+
+## Common Examples
+
+Each example below shows only the keys being changed for that provider.
+
+<Note>
+Only the keys shown are overridden. Every other key for that provider keeps its `config.yaml` default (see [How It's Applied](#how-its-applied)).
+</Note>
+
+**Stricter IAM (Identity and Access Management) hygiene for AWS:**
+
+```yaml
+aws:
+ max_unused_access_keys_days: 30
+ max_console_access_days: 30
+ max_unused_sagemaker_access_days: 45
+```
+
+**Raise Azure Defender attack-path sensitivity:**
+
+```yaml
+azure:
+ defender_attack_path_minimal_risk_level: "Critical"
+```
+
+**Tighten GCP storage retention and key rotation:**
+
+```yaml
+gcp:
+ storage_min_retention_days: 30
+ secretmanager_max_rotation_days: 30
+```
+
+## Troubleshooting
+
+### A Provider Doesn't Appear in the Selector
+
+The provider is already attached to another Scan Configuration. Detach it there first, or use the provider row menu to move it.
+
+### You Can't Attach or Detach Providers
+
+If you can edit the configuration but not change its providers, or an error mentions a provider ID that "wasn't found", you're missing the **Manage Providers** permission or the provider isn't visible to your role. A provider outside your visibility is reported the same way as one that doesn't exist, so it isn't revealed to roles that shouldn't see it. See [Required Permissions](#required-permissions).
diff --git a/docs/user-guide/tutorials/prowler-app-security-hub-integration.mdx b/docs/user-guide/tutorials/prowler-app-security-hub-integration.mdx
index 592ff2b26d..977ad8e6f1 100644
--- a/docs/user-guide/tutorials/prowler-app-security-hub-integration.mdx
+++ b/docs/user-guide/tutorials/prowler-app-security-hub-integration.mdx
@@ -1,13 +1,17 @@
---
title: "AWS Security Hub Integration"
+sidebarTitle: 'AWS Security Hub'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.11.0" />
-Prowler App enables automatic export of security findings to AWS Security Hub, providing seamless integration with AWS's native security and compliance service. This comprehensive guide demonstrates how to configure and manage AWS Security Hub integrations to centralize security findings and enhance compliance tracking across AWS environments.
+<AppliesTo />
-Integrating Prowler App with AWS Security Hub provides:
+Prowler Cloud enables automatic export of security findings to AWS Security Hub, providing seamless integration with AWS's native security and compliance service. This comprehensive guide demonstrates how to configure and manage AWS Security Hub integrations to centralize security findings and enhance compliance tracking across AWS environments.
+
+Integrating Prowler Cloud with AWS Security Hub provides:
* **Centralized security visibility:** Consolidate findings from multiple AWS accounts and regions
* **Native AWS integration:** Leverage existing AWS security workflows and compliance frameworks
@@ -30,7 +34,7 @@ Refer to [AWS Security Hub pricing](https://aws.amazon.com/security-hub/pricing/
</Note>
## Prerequisites
-Before configuring AWS Security Hub Integration in Prowler App, complete these steps:
+Before configuring AWS Security Hub Integration in Prowler Cloud, complete these steps:
### AWS Security Hub Setup
@@ -42,9 +46,9 @@ Configure AWS credentials by following the [AWS authentication setup guide](/use
## Configuration
-To configure AWS Security Hub integration in Prowler App:
+To configure AWS Security Hub integration in Prowler Cloud:
-1. Navigate to **Integrations** in the Prowler App interface
+1. Navigate to **Integrations** in Prowler Cloud
2. Locate the **AWS Security Hub** card and click **Manage**, then select **Add integration**
diff --git a/docs/user-guide/tutorials/prowler-app-simple-mutelist.mdx b/docs/user-guide/tutorials/prowler-app-simple-mutelist.mdx
index c0bd7db9b4..4b0d59e24a 100644
--- a/docs/user-guide/tutorials/prowler-app-simple-mutelist.mdx
+++ b/docs/user-guide/tutorials/prowler-app-simple-mutelist.mdx
@@ -3,10 +3,13 @@ title: "Simple Mutelist"
---
import { VersionBadge } from "/snippets/version-badge.mdx";
+import { AppliesTo } from "/snippets/applies-to.mdx";
<VersionBadge version="5.16.0" />
-Prowler App provides Simple Mutelist, an intuitive way to mute findings directly from the Findings page without writing YAML configuration. This feature streamlines the muting workflow by allowing individual or bulk muting with just a few clicks.
+<AppliesTo />
+
+Prowler Cloud provides Simple Mutelist, an intuitive way to mute findings directly from the Findings page without writing YAML configuration. This feature streamlines the muting workflow by allowing individual or bulk muting with just a few clicks.
## What Is Simple Mutelist?
diff --git a/docs/user-guide/tutorials/prowler-app-social-login.mdx b/docs/user-guide/tutorials/prowler-app-social-login.mdx
index 45fe8ec62f..62de6fbc9c 100644
--- a/docs/user-guide/tutorials/prowler-app-social-login.mdx
+++ b/docs/user-guide/tutorials/prowler-app-social-login.mdx
@@ -1,12 +1,16 @@
---
title: 'Social Login Configuration'
+sidebarTitle: 'Social Login'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.5.0" />
-**Prowler App** supports social login using Google and GitHub OAuth providers. This document guides you through configuring the required environment variables to enable social authentication.
+<AppliesTo />
+
+Prowler supports social login using Google and GitHub OAuth providers. In **Prowler Cloud** social login is available out of the box. In **Prowler Local Server**, enable it by configuring the environment variables described in this guide.
<img src="/images/prowler-app/social-login/social_login_buttons.png" alt="Social login buttons" width="700" />
## Configuring Social Login Credentials
diff --git a/docs/user-guide/tutorials/prowler-app-sso-entra.mdx b/docs/user-guide/tutorials/prowler-app-sso-entra.mdx
index 37f3bbdda5..07cf4709be 100644
--- a/docs/user-guide/tutorials/prowler-app-sso-entra.mdx
+++ b/docs/user-guide/tutorials/prowler-app-sso-entra.mdx
@@ -2,7 +2,11 @@
title: 'Entra ID Configuration'
---
-This page provides instructions for creating and configuring a Microsoft Entra ID (formerly Azure AD) application to use SAML SSO with Prowler App.
+import { AppliesTo } from "/snippets/applies-to.mdx"
+
+<AppliesTo />
+
+This page provides instructions for creating and configuring a Microsoft Entra ID (formerly Azure AD) application to use SAML SSO with Prowler Cloud.
You can find a walkthrough video [here](https://www.youtube.com/watch?v=zegqm55oJVk).
@@ -28,7 +32,7 @@ You can find a walkthrough video [here](https://www.youtube.com/watch?v=zegqm55o
-6. Enter the "Identifier (Entity ID)" and "Reply URL (Assertion Consumer Service URL)". These values can be obtained from the SAML SSO integration setup in Prowler App. For detailed instructions, refer to the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso) page.
+6. Enter the "Identifier (Entity ID)" and "Reply URL (Assertion Consumer Service URL)". These values can be obtained from the SAML SSO integration setup in Prowler Cloud. For detailed instructions, refer to the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso) page.
@@ -44,4 +48,4 @@ You can find a walkthrough video [here](https://www.youtube.com/watch?v=zegqm55o
-10. Save the downloaded Metadata XML to a file. To complete the setup, upload this file during the Prowler App integration. (See the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso) page for details).
+10. Save the downloaded Metadata XML to a file. To complete the setup, upload this file during the SAML SSO integration setup in Prowler Cloud. (See the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso) page for details).
diff --git a/docs/user-guide/tutorials/prowler-app-sso-google-workspace.mdx b/docs/user-guide/tutorials/prowler-app-sso-google-workspace.mdx
index 2a349c0204..ce0e5edc79 100644
--- a/docs/user-guide/tutorials/prowler-app-sso-google-workspace.mdx
+++ b/docs/user-guide/tutorials/prowler-app-sso-google-workspace.mdx
@@ -2,20 +2,24 @@
title: 'SAML SSO: Google Workspace'
---
-This page explains how to configure SAML-based Single Sign-On (SSO) in Prowler App using **Google Workspace** as the Identity Provider (IdP). The setup is divided into two parts: create a custom SAML app in Google Admin Console, then complete the configuration in Prowler App.
+import { AppliesTo } from "/snippets/applies-to.mdx"
+
+<AppliesTo />
+
+This page explains how to configure SAML-based Single Sign-On (SSO) in Prowler Cloud using **Google Workspace** as the Identity Provider (IdP). The setup is divided into two parts: create a custom SAML app in Google Admin Console, then complete the configuration in Prowler Cloud.
<Info>
**Parallel Setup Required**
-Google Admin Console requires the ACS URL and Entity ID from Prowler App, while Prowler App displays these values only after opening the SAML configuration dialog. To work around this, open Prowler App in a separate browser tab, navigate to the profile page, open the "Configure SAML SSO" dialog, and copy the ACS URL and Entity ID before proceeding with the Google configuration.
+Google Admin Console requires the ACS URL and Entity ID from Prowler Cloud, while Prowler Cloud displays these values only after opening the SAML configuration dialog. To work around this, open Prowler Cloud in a separate browser tab, navigate to the profile page, open the "Configure SAML SSO" dialog, and copy the ACS URL and Entity ID before proceeding with the Google configuration.
</Info>
## Prerequisites
- **Google Workspace**: Super Admin access (or delegated admin with app management permissions).
-- **Prowler App**: Administrator access to the organization (role with "Manage Account" permission).
-- Prowler App version **5.9.0** or later.
+- **Prowler Cloud**: Administrator access to the organization (role with "Manage Account" permission).
+- Prowler version **5.9.0** or later.
---
@@ -44,7 +48,7 @@ On the **Google Identity Provider details** screen:
1. Google displays two options:
- **Option 1**: Click "Download Metadata" to save the XML file directly. This is the recommended approach.
- **Option 2**: Manually copy the **SSO URL**, **Entity ID**, and **Certificate**.
-2. Download the metadata. This file is required to complete the Prowler App configuration in Part B.
+2. Download the metadata. This file is required to complete the configuration in Prowler Cloud (Part B).
3. Click "Continue".
@@ -52,18 +56,18 @@ On the **Google Identity Provider details** screen:
<Warning>
**Save the Metadata File**
-Download and save the IdP metadata XML file before proceeding. This file cannot be easily retrieved later and is required to complete the SAML configuration in Prowler App.
+Download and save the IdP metadata XML file before proceeding. This file cannot be easily retrieved later and is required to complete the SAML configuration in Prowler Cloud.
</Warning>
### Step 4: Configure the Service Provider Details
-Enter the following values obtained from the SAML SSO configuration dialog in Prowler App (see [Part B, Step 1](#step-1-open-the-saml-configuration-dialog) for details on where to find them):
+Enter the following values obtained from the SAML SSO configuration dialog in Prowler Cloud (see [Part B, Step 1](#step-1-open-the-saml-configuration-dialog) for details on where to find them):
| Google Workspace Field | Value |
|------------------------|-------|
-| **ACS URL** | The Assertion Consumer Service (ACS) URL displayed in Prowler App (e.g., `https://api.prowler.com/api/v1/accounts/saml/your-domain.com/acs/`). Self-hosted deployments use a different base URL. |
-| **Entity ID** | The Audience URI displayed in Prowler App (e.g., `urn:prowler.com:sp`). |
+| **ACS URL** | The Assertion Consumer Service (ACS) URL displayed in Prowler Cloud (e.g., `https://api.prowler.com/api/v1/accounts/saml/your-domain.com/acs/`). Prowler Local Server deployments use a different base URL. |
+| **Entity ID** | The Audience URI displayed in Prowler Cloud (e.g., `urn:prowler.com:sp`). |
| **Name ID format** | Select `EMAIL` from the dropdown. |
| **Name ID** | Select `Basic Information > Primary email` from the dropdown. |
@@ -82,7 +86,7 @@ Click "Add mapping" for each entry:
| `Basic Information > First name` | `firstName` | Yes | |
| `Basic Information > Last name` | `lastName` | Yes | |
| `Employee Details > Department` | `userType` | No | Determines the Prowler role. **Case-sensitive.** |
-| `Employee Details > Organization` | `organization` | No | Company name displayed in Prowler App profile. |
+| `Employee Details > Organization` | `organization` | No | Company name displayed in the user profile in Prowler Cloud. |
<Info>
**Remember the Mapped Fields**
@@ -98,7 +102,7 @@ Click "Finish" to create the SAML app.
<Info>
**Dynamic Updates**
-Prowler App updates user attributes each time a user logs in. Any changes made in Google Workspace are reflected on the next login.
+Prowler Cloud updates user attributes each time a user logs in. Any changes made in Google Workspace are reflected on the next login.
</Info>
@@ -108,10 +112,10 @@ Prowler App updates user attributes each time a user logs in. Any changes made i
The `userType` attribute controls which Prowler role is assigned to the user:
- If `userType` matches an existing Prowler role name, the user receives that role automatically.
-- If `userType` does not match any existing role, Prowler App creates a new role with that name **without permissions**.
-- If `userType` is not set, the user receives the `no_permissions` role.
+- If `userType` does not match any existing role, Prowler Cloud creates a new role with that name **with read-only access** (visibility over all providers, no management permissions). A Prowler administrator can adjust its permissions afterward through the [RBAC Management](/user-guide/tutorials/prowler-app-rbac) tab.
+- If `userType` is not set, the user's existing roles are left unchanged.
-In all cases where the resulting role has no permissions, a Prowler administrator must configure the appropriate permissions through the [RBAC Management](/user-guide/tutorials/prowler-app-rbac) tab. The `userType` value is **case-sensitive** - for example, `Backend` and `backend` are treated as different roles.
+The `userType` value is **case-sensitive** - for example, `Backend` and `backend` are treated as different roles.
</Warning>
@@ -148,13 +152,13 @@ If attempting to use the "Test SAML login" option in Google Admin Console and re
---
-## Part B - Prowler App Configuration
+## Part B - Prowler Cloud Configuration
### Step 1: Open the SAML Configuration Dialog
1. Navigate to the profile settings page:
- **Prowler Cloud**: `https://cloud.prowler.com/profile`
- - **Self-hosted**: `http://{your-domain}/profile`
+ - **Prowler Local Server**: `http://{your-domain}/profile`
2. Find the "SAML SSO Integration" card and click "Enable" (or "Update" if already configured).
3. The "Configure SAML SSO" dialog opens, displaying:
- **ACS URL**: The Assertion Consumer Service URL (copy this value for Part A, Step 4). This URL updates dynamically when the email domain is entered.
@@ -162,21 +166,21 @@ If attempting to use the "Test SAML login" option in Google Admin Console and re
- **Name ID Format**: The expected format (`urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`).
- **Supported Assertion Attributes**: The list of accepted attributes (`firstName`, `lastName`, `userType`, `organization`).
-
+
### Step 2: Enter the Email Domain and Upload Metadata
-1. Enter the **email domain** for the organization (e.g., `prowler.cloud`). Prowler App uses this domain to identify users who should authenticate via SAML. The ACS URL updates automatically to reflect the configured domain.
+1. Enter the **email domain** for the organization (e.g., `prowler.cloud`). Prowler Cloud uses this domain to identify users who should authenticate via SAML. The ACS URL updates automatically to reflect the configured domain.
2. Upload the **metadata XML file** downloaded in Part A, Step 3.
3. Click "Save".
-
+
### Step 3: Verify the Enabled Status
The "SAML SSO Integration" card should now display a **"Status: Enabled"** indicator with a checkmark, confirming that the configuration is complete.
-
+
---
@@ -214,30 +218,30 @@ To test the `userType` → role mapping, set the **Department** attribute in the
1. Navigate to the Prowler login page.
2. Click "Continue with SAML SSO".
3. Enter an email from the configured domain (e.g., `adrian@prowler.cloud`).
-4. Click "Log in". The browser redirects to Google for authentication and returns to Prowler App upon success.
+4. Click "Log in". The browser redirects to Google for authentication and returns to Prowler Cloud upon success.
-
+
### Verify User Profile and Role Mapping
-After a successful SSO login, the user profile in Prowler App reflects the attributes sent by Google Workspace:
+After a successful SSO login, the user profile in Prowler Cloud reflects the attributes sent by Google Workspace:
- **Name**: Populated from the `firstName` and `lastName` attributes.
-- **Role**: Created automatically from the `userType` attribute (e.g., `Backend`). If the role did not exist previously, it is created with no permissions by default.
-- **Permissions**: In the screenshot below, the user has no permissions because the `Backend` role did not exist prior to login and was created automatically without any permissions. To resolve this, a Prowler administrator can either:
- - Assign the appropriate permissions to the new role via the [RBAC Management](/user-guide/tutorials/prowler-app-rbac) tab.
+- **Role**: Created automatically from the `userType` attribute (e.g., `Backend`). If the role did not exist previously, it is created with read-only access by default.
+- **Permissions**: If the assigned permissions need to be adjusted, a Prowler administrator can either:
+ - Edit the permissions of the new role via the [RBAC Management](/user-guide/tutorials/prowler-app-rbac) tab.
- Set the `userType` attribute in the IdP to match an existing Prowler role that already has the desired permissions. The updated role is applied on the next SAML login.
For more details on role assignment behavior and attribute mapping, refer to the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso#configure-attribute-mapping-in-the-idp) page.
-
+
### IdP-Initiated SSO (from Google)
1. Sign in to Google Workspace with an account that has access to the Prowler SAML app.
2. Open the Google Workspace app launcher (the grid icon in the top-right corner of any Google page).
-3. Click the Prowler app tile.
-4. The browser redirects directly to Prowler App, authenticated.
+3. Click the Prowler tile.
+4. The browser redirects directly to Prowler Cloud, authenticated.
For more information on the SSO login flows, refer to the [SAML SSO Configuration](/user-guide/tutorials/prowler-app-sso#idp-initiated-sso) page.
@@ -270,7 +274,7 @@ Prowler does not allow two tenants to share the same email domain. If the domain
<Info>
**Just-in-Time Provisioning**
-Users who authenticate via SAML for the first time are automatically created in Prowler App. No prior invitation is needed. User attributes (`firstName`, `lastName`, `userType`) are updated on every login from the Google directory.
+Users who authenticate via SAML for the first time are automatically created in Prowler Cloud. No prior invitation is needed. User attributes (`firstName`, `lastName`, `userType`) are updated on every login from the Google directory.
</Info>
@@ -278,10 +282,10 @@ Users who authenticate via SAML for the first time are automatically created in
## Quick Summary
-1. In **Google Admin Console**, create a custom SAML app using the ACS URL and Entity ID from Prowler App.
+1. In **Google Admin Console**, create a custom SAML app using the ACS URL and Entity ID from Prowler Cloud.
2. Configure **attribute mapping**: `firstName`, `lastName`, and optionally `userType` and `organization`.
3. **Download the metadata XML** from Google.
4. **Enable the app** in Google Workspace for the relevant users or groups.
-5. In **Prowler App**, enter the email domain, upload the metadata XML, and save.
+5. In **Prowler Cloud**, enter the email domain, upload the metadata XML, and save.
6. Verify the SAML SSO Integration shows **"Status: Enabled"**.
7. Test login via "Continue with SAML SSO" on the Prowler login page.
diff --git a/docs/user-guide/tutorials/prowler-app-sso.mdx b/docs/user-guide/tutorials/prowler-app-sso.mdx
index d4d2c18d11..bb993942cd 100644
--- a/docs/user-guide/tutorials/prowler-app-sso.mdx
+++ b/docs/user-guide/tutorials/prowler-app-sso.mdx
@@ -1,18 +1,22 @@
---
title: 'SAML Single Sign-On (SSO)'
+sidebarTitle: 'SAML SSO'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { AppliesTo } from "/snippets/applies-to.mdx"
<VersionBadge version="5.9.0" />
-This guide provides comprehensive instructions to configure SAML-based Single Sign-On (SSO) in Prowler App. This configuration allows users to authenticate using the organization's Identity Provider (IdP).
+<AppliesTo />
+
+This guide provides comprehensive instructions to configure SAML-based Single Sign-On (SSO) in Prowler Cloud. This configuration allows users to authenticate using the organization's Identity Provider (IdP).
This document is divided into two main sections:
-- **[User Guide](#user-guide-configuration)**: For organization administrators to configure SAML SSO through Prowler App.
+- **[User Guide](#user-guide-configuration)**: For organization administrators to configure SAML SSO through Prowler Cloud.
-- **[Developer and Administrator Guide](#developer-and-administrator-guide)**: For developers and system administrators running self-hosted Prowler App instances, providing technical details on environment configuration, API usage, and testing.
+- **[Developer and Administrator Guide](#developer-and-administrator-guide)**: For developers and system administrators running Prowler Local Server instances, providing technical details on environment configuration, API usage, and testing.
---
@@ -43,7 +47,7 @@ If the SAML configuration is removed, users who previously authenticated via SAM
#### Step 1: Access Profile Settings
-To access the account settings, click the "Account" button in the top-right corner of Prowler App, or navigate directly to `https://cloud.prowler.com/profile` (or `http://localhost:3000/profile` for local setups).
+To access the account settings, click the "Account" button in the top-right corner of Prowler Cloud, or navigate directly to `https://cloud.prowler.com/profile` (or `http://localhost:3000/profile` for local setups).
@@ -63,12 +67,12 @@ Choose a Method:
<Tabs>
<Tab title="Generic Method">
- Prowler App displays the SAML configuration information needed to configure the IdP. Use this information to create a new SAML application in the IdP.
+ Prowler Cloud displays the SAML configuration information needed to configure the IdP. Use this information to create a new SAML application in the IdP.
1. **Assertion Consumer Service (ACS) URL**: The endpoint in Prowler that will receive the SAML assertion from the IdP.
2. **Audience URI (Entity ID)**: A unique identifier for the Prowler application (Service Provider).
- To configure the IdP, copy the **ACS URL** and **Audience URI** from Prowler App and use them to set up a new SAML application.
+ To configure the IdP, copy the **ACS URL** and **Audience URI** from Prowler Cloud and use them to set up a new SAML application.
@@ -81,13 +85,13 @@ Choose a Method:
**Configure Attribute Mapping in the IdP**
- For Prowler App to correctly identify and provision users, configure the IdP to send the following attributes in the SAML assertion:
+ For Prowler Cloud to correctly identify and provision users, configure the IdP to send the following attributes in the SAML assertion:
| Attribute Name | Description | Required |
|----------------|---------------------------------------------------------------------------------------------------------|----------|
| `firstName` | The user's first name. | Yes |
| `lastName` | The user's last name. | Yes |
- | `userType` | Determines which Prowler role the user receives (e.g., `admin`, `auditor`). If a role with that name already exists, the user receives it automatically; if it does not exist, Prowler App creates a new role with that name without permissions. If `userType` is not defined, the user is assigned the `no_permissions` role. Role permissions can be edited in the [RBAC Management tab](/user-guide/tutorials/prowler-app-rbac). | No |
+ | `userType` | Determines which Prowler role the user receives (e.g., `admin`, `auditor`). If a role with that name already exists, the user receives it automatically; if it does not exist, Prowler Cloud creates a new role with that name with read-only access (visibility over all providers, no management permissions). If `userType` is not defined, the user's existing roles are left unchanged. Role permissions can be edited in the [RBAC Management tab](/user-guide/tutorials/prowler-app-rbac). | No |
| `organization` | The user's company name. | No |
<Info>
@@ -98,9 +102,15 @@ Choose a Method:
</Info>
<Warning>
+ **Single-Value `userType` Required**
+
+ Map `userType` to an IdP attribute that always contains a single value. If the IdP sends multiple values, Prowler Cloud uses only the first value and does not assign multiple roles or select the highest-privilege role.
+
+ </Warning>
+ <Warning>
**Dynamic Updates**
- Prowler App updates these attributes each time a user logs in. Any changes made in the Identity Provider (IdP) will be reflected when the user logs in again.
+ Prowler Cloud updates these attributes each time a user logs in. Any changes made in the Identity Provider (IdP) will be reflected when the user logs in again.
</Warning>
@@ -132,34 +142,31 @@ Choose a Method:
- 7. **Configure User Attributes in Okta**: Okta acts as the central source for user profile information. Prowler App maps the following Okta user profile attributes during each SAML login:
+ 7. **Configure User Attributes in Okta**: Okta acts as the central source for user profile information. Prowler Cloud maps the following Okta user profile attributes during each SAML login:
- * **First name** (`firstName`): Maps to the user's first name in Prowler App.
- * **Last name** (`lastName`): Maps to the user's last name in Prowler App.
+ * **First name** (`firstName`): Maps to the user's first name in Prowler Cloud.
+ * **Last name** (`lastName`): Maps to the user's last name in Prowler Cloud.
- * **Organization** (`organization`): Maps to the company name displayed in Prowler App. This attribute is optional.
- * **User type** (`userType`): Determines the Prowler role assigned to the user. This attribute is **case-sensitive** and must match the exact name of an existing role in Prowler App.
+ * **Organization** (`organization`): Maps to the company name displayed in Prowler Cloud. This attribute is optional.
+ * **User type** (`userType`): Determines the Prowler role assigned to the user. This attribute is **case-sensitive**: if it matches the exact name of an existing role in Prowler Cloud the user receives that role; if no role with that name exists, a new one is created with read-only access.
- To modify these values, edit the user's profile directly in the Okta admin console under the "Profile" tab. Changes are reflected in Prowler App the next time the user logs in via SAML.
+ To modify these values, edit the user's profile directly in the Okta admin console under the "Profile" tab. Changes are reflected in Prowler Cloud the next time the user logs in via SAML.
<Warning>
**User Type and Role Assignment**
The `userType` attribute controls which Prowler role is assigned to the user:
- * If a role with the specified name already exists in Prowler App, the user automatically receives that role.
- * If the role does not exist, Prowler App creates a new role with that exact name but without any permissions, preventing the user from performing any actions.
- * If `userType` is not defined in the user's Okta profile, the user is assigned the `no_permissions` role.
+ * If a role with the specified name already exists in Prowler Cloud, the user automatically receives that role.
+ * If the role does not exist, Prowler Cloud creates a new role with that exact name with read-only access: the user can see all providers and their findings but cannot manage anything. A Prowler administrator (a user whose role includes the "Manage Account" permission) can adjust its permissions afterward through the [RBAC Management tab](/user-guide/tutorials/prowler-app-rbac).
+ * If `userType` is not defined in the user's Okta profile, the user's existing roles in Prowler Cloud are left unchanged.
+ * `userType` must contain a single value. If the IdP sends multiple values, Prowler Cloud uses only the first value and does not assign multiple roles.
- In all cases where the resulting role has no permissions, a Prowler administrator (a user whose role includes the "Manage Account" permission) must configure the appropriate permissions through the [RBAC Management tab](/user-guide/tutorials/prowler-app-rbac).
-
- This behavior is intentional: by defaulting to no permissions, Prowler App ensures that a misconfiguration in Okta cannot inadvertently grant elevated access.
-
- **Example:** To assign the `IT` role to a user, set the `userType` value to `IT` in Okta. If a role named `IT` already exists in Prowler App, the user receives it automatically upon login. If it does not exist, Prowler App creates a new role called `IT` without permissions, and a Prowler administrator must configure the desired permissions for it.
+ **Example:** To assign the `IT` role to a user, set the `userType` value to `IT` in Okta. If a role named `IT` already exists in Prowler Cloud, the user receives it automatically upon login. If it does not exist, Prowler Cloud creates a new role called `IT` with read-only access, and a Prowler administrator can adjust its permissions as needed.
</Warning>
@@ -175,11 +182,11 @@ Choose a Method:
Once the IdP is configured, it provides a **metadata XML file**. This file contains the IdP's configuration information, such as its public key and login URL.
-To complete the Prowler App configuration:
+To complete the Prowler Cloud configuration:
1. Return to the Prowler SAML configuration page.
-2. Enter the **email domain** for the organization (e.g., `mycompany.com`). Prowler App uses this to identify users who should authenticate via SAML.
+2. Enter the **email domain** for the organization (e.g., `mycompany.com`). Prowler Cloud uses this to identify users who should authenticate via SAML.
3. Upload the **metadata XML file** downloaded from the IdP.
@@ -207,7 +214,7 @@ SAML SSO can be disabled by removing the existing configuration from the integra
Once SAML SSO is configured, users can access Prowler Cloud directly from their Identity Provider's dashboard:
1. Navigate to the IdP dashboard or portal
-2. Click on the Prowler Cloud application tile
+2. Click the Prowler Cloud application tile
3. The system automatically authenticates users and redirects them to Prowler Cloud
This method is convenient for users who primarily work from the IdP portal and prefer a seamless single-click access.
@@ -222,7 +229,7 @@ Users can also initiate the login process directly from Prowler's login page:
3. Enter their email address from the configured domain
4. The system redirects users to the IdP for authentication
-5. After successful authentication, users are returned to Prowler App
+5. After successful authentication, users are returned to Prowler Cloud
This method is useful when users bookmark Prowler or navigate directly to the application.
@@ -230,11 +237,11 @@ This method is useful when users bookmark Prowler or navigate directly to the ap
## Developer and Administrator Guide
-This section provides technical details for developers and administrators of self-hosted Prowler instances.
+This section provides technical details for developers and administrators of Prowler Local Server instances.
### Environment Configuration
-For self-hosted deployments, several environment variables must be configured to ensure SAML SSO functions correctly. These variables are typically set in an `.env` file.
+For Prowler Local Server deployments, several environment variables must be configured to ensure SAML SSO functions correctly. These variables are typically set in an `.env` file.
| Variable | Description | Example |
|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
diff --git a/docs/user-guide/tutorials/prowler-app.mdx b/docs/user-guide/tutorials/prowler-app.mdx
index 5e99a41ae7..6c3131d136 100644
--- a/docs/user-guide/tutorials/prowler-app.mdx
+++ b/docs/user-guide/tutorials/prowler-app.mdx
@@ -1,34 +1,34 @@
---
title: 'Prowler Cloud'
+sidebarTitle: 'Getting Started'
---
+import { ProviderCards } from "/snippets/provider-cards.mdx"
+
**Prowler Cloud** is a web application that simplifies running Prowler. This tutorial will guide you through setting up and using it.
-We refer to **Prowler App** as the self-hosted version of **Prowler Cloud**.
+**Prowler Local Server** is the self-hosted version of **Prowler Cloud**. See [Prowler product families](/getting-started/products) for every official product name.
## Accessing Prowler Cloud and API Documentation
If you are a [Prowler Cloud](https://cloud.prowler.com/sign-in) user, you can access API docs at [https://api.prowler.com/api/v1/docs](https://api.prowler.com/api/v1/docs)
<Note>
-**For Prowler App users**
+**For Prowler Local Server users**
-After [installing](/getting-started/installation/prowler-app) **Prowler App**, access it at [http://localhost:3000](http://localhost:3000).
+After [installing](/getting-started/installation/prowler-app) **Prowler Local Server**, access it at [http://localhost:3000](http://localhost:3000).
To view the auto-generated **Prowler API** documentation, navigate to [http://localhost:8080/api/v1/docs](http://localhost:8080/api/v1/docs). This documentation provides details on available endpoints, parameters, and responses.
</Note>
-## **Step 1: Sign Up**
-
-### **Sign Up with Email**
-
+## Step 1: Sign Up
+### Sign Up with Email
To get started, sign up using your email and password:
<img src="/images/sign-up-button.png" alt="Sign Up Button" width="320" />
<img src="/images/sign-up.png" alt="Sign Up" width="285" />
-### **Sign Up with Social Login**
-
+### Sign Up with Social Login
If Social Login is enabled, you can sign up using your preferred provider (e.g., Google, GitHub).
<Note>
@@ -44,16 +44,14 @@ If your email is not registered, a new account will be created using your social
See [how to configure Social Login for Prowler](/user-guide/tutorials/prowler-app-social-login) to enable this feature in your own deployments.
</Note>
-## **Step 2: Log In**
-
-Once registered, log in with your email and password to access Prowler App.
+## Step 2: Log In
+Once registered, log in with your email and password to access Prowler Cloud.
<img src="/images/log-in.png" alt="Log In" width="350" />
Upon logging in, the Overview page will display. At this stage, no data is present: add a provider to begin scanning your cloud environment.
-## **Step 3: Add a Provider**
-
+## Step 3: Add a Provider
To perform security scans, link a cloud provider account. Prowler supports the following providers and more:
- **AWS**
@@ -77,48 +75,21 @@ Steps to add a provider:
<img src="/images/add-provider.png" alt="Add Provider" width="700" />
-## **Step 4: Configure the Provider**
-
+## Step 4: Configure the Provider
Select the cloud provider to scan and configure authentication credentials. Each provider has specific requirements and authentication methods.
<img src="/images/select-provider.png" alt="Select a Provider" width="700" />
For detailed instructions on configuring credentials for each provider, refer to the provider-specific getting started guides:
-<Columns cols={3}>
- <Card title="AWS" icon="aws" href="/user-guide/providers/aws/getting-started-aws">
- Configure AWS authentication using IAM Access Keys or Assumed Role credentials.
- </Card>
- <Card title="Azure" icon="microsoft" href="/user-guide/providers/azure/getting-started-azure">
- Set up Azure authentication using Service Principal credentials.
- </Card>
- <Card title="Google Cloud" icon="google" href="/user-guide/providers/gcp/getting-started-gcp">
- Configure GCP authentication with Service Account or Application Default Credentials.
- </Card>
- <Card title="Oracle Cloud Infrastructure" icon="cloud" href="/user-guide/providers/oci/getting-started-oci">
- Connect OCI with API key credentials to scan compartments and regions.
- </Card>
- <Card title="Kubernetes" icon="cloud" href="/user-guide/providers/kubernetes/getting-started-k8s">
- Set up Kubernetes authentication using kubeconfig files for cluster access.
- </Card>
- <Card title="Microsoft 365" icon="microsoft" href="/user-guide/providers/microsoft365/getting-started-m365">
- Configure M365 authentication with Application Certificate or Client Secret.
- </Card>
- <Card title="GitHub" icon="github" href="/user-guide/providers/github/getting-started-github">
- Set up GitHub authentication using Personal Access Token, OAuth App, or GitHub App.
- </Card>
- <Card title="Infrastructure as Code" icon="code" href="/user-guide/providers/iac/getting-started-iac">
- Scan IaC public or private repositories for security issues.
- </Card>
-</Columns>
-## **Step 5: Test Connection**
+<ProviderCards />
-After adding your credentials of your cloud account, click the `Launch` button to verify that Prowler App can successfully connect to your provider:
+## Step 5: Test Connection
+After adding your credentials of your cloud account, click the `Launch` button to verify that Prowler can successfully connect to your provider:
<img src="/images/test-connection-button.png" alt="Test Connection" width="700" />
-## **Step 6: Scan started**
-
+## Step 6: Scan Started
After successfully adding and testing your credentials, Prowler will start scanning your cloud environment, click the `Go to Scans` button to see the progress:
<img src="/images/provider-added.png" alt="Start Now" width="700" />
@@ -127,8 +98,7 @@ After successfully adding and testing your credentials, Prowler will start scann
Prowler will automatically scan all configured providers every **24 hours**, ensuring your cloud environment stays continuously monitored.
</Note>
-## **Step 7: Monitor Scan Progress**
-
+## Step 7: Monitor Scan Progress
Track the progress of your scan in the `Scans` section:
<img src="/images/scan-progress.png" alt="Scan Progress" width="700" />
@@ -146,8 +116,7 @@ Each dashboard handles scan data differently:
When a new scan completes or a new data ingestion is processed, the dashboards automatically reflect the updated results.
</Note>
-## **Step 8: Analyze the Findings**
-
+## Step 8: Analyze the Findings
While the scan is running, start exploring the findings in these sections:
- **Overview**: High-level summary of the scans.
@@ -168,8 +137,7 @@ While the scan is running, start exploring the findings in these sections:
To view all `new` findings that have not been seen prior to this scan, click the `Delta` filter and select `new`. To view all `changed` findings that have had a status change (from `PASS` to `FAIL` for example), click the `Delta` filter and select `changed`.
-## **Step 9: Download the Outputs**
-
+## Step 9: Download the Outputs
Once a scan is complete, navigate to the Scan Jobs section to download the output files generated by Prowler:
<img src="/images/scan_jobs_section.png" alt="Scan Jobs section" width="700" />
@@ -190,8 +158,7 @@ The `zip` file unpacks into a folder named like `prowler-output-<provider_id>-<t
For more information about the API endpoint used by the UI to download the ZIP archive, refer to: [Prowler API Reference - Download Scan Output](https://api.prowler.com/api/v1/docs#tag/Scan/operation/scans_report_retrieve)
</Note>
-## **Step 10: Download specified compliance report**
-
+## Step 10: Download Specified Compliance Report
Once your scan has finished, you don’t need to grab the entire ZIP—just pull down the specific compliance report you want:
- Navigate to the **Compliance** section of the UI.
diff --git a/docs/user-guide/tutorials/prowler-cloud-aws-organizations.mdx b/docs/user-guide/tutorials/prowler-cloud-aws-organizations.mdx
index d9c17aaa5f..8b2124e004 100644
--- a/docs/user-guide/tutorials/prowler-cloud-aws-organizations.mdx
+++ b/docs/user-guide/tutorials/prowler-cloud-aws-organizations.mdx
@@ -1,17 +1,20 @@
---
-title: 'AWS Organizations in Prowler Cloud'
+title: 'AWS Organizations'
description: 'Onboard all AWS accounts in your Organization through a single guided wizard'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
<VersionBadge version="5.19.0" />
-Prowler Cloud enables you to onboard all AWS accounts in your Organization through a single guided wizard. Instead of connecting accounts one by one, you can discover every account in your AWS Organization, select the ones you want to monitor, test connectivity, and launch scans — all from the Prowler Cloud UI.
+Prowler Cloud onboards every AWS account in your Organization through a single guided wizard. Instead of connecting accounts one by one, you can discover every account in your AWS Organization, select the ones you want to monitor, test connectivity, and launch scans — all from the Prowler Cloud UI.
-<Note>
-This feature is **exclusively available in Prowler Cloud**. For CLI-based multi-account scanning, see [AWS Organizations in Prowler CLI](/user-guide/providers/aws/organizations).
-</Note>
+<SubscriptionBanner>
+For CLI-based multi-account scanning, see [AWS Organizations in Prowler CLI](/user-guide/providers/aws/organizations).
+</SubscriptionBanner>
+
+To follow this guide you need an active [Prowler Cloud](https://cloud.prowler.com) account and access to your AWS Organization [management account](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html) (or a registered delegated administrator account).
## Overview
@@ -22,227 +25,19 @@ This feature is **exclusively available in Prowler Cloud**. For CLI-based multi-
| **Individual accounts** | A few AWS accounts | Connect each account one by one with its own IAM role. |
| **AWS Organizations** | 10+ accounts, or any org-managed environment | Connect once to your management account, discover all member accounts automatically, and scan them in bulk. |
-### How it works
+### How It Works
-Before using the AWS Organizations wizard, you need to deploy **two IAM roles** in your AWS environment. The onboarding follows this sequence:
+<VersionBadge version="5.35.0" />
+
+Onboarding deploys the **ProwlerScan Identity and Access Management (IAM) role** in your management account and in every member account. A **single CloudFormation stack** — launched from the wizard's **Create Stack in Management Account** button ([Step 2](#step-2-authenticate-with-your-management-account)) — creates the management account role **and** a service-managed StackSet that rolls the role out to your member accounts in one operation. Prefer to deploy the roles yourself? See [Deploy the Roles Manually](#deploy-the-roles-manually).
<Frame>
- <img src="/images/organizations/onboarding-flow.svg" alt="Onboarding flow: 1. Create Management Account Role (Quick Create or Manual), 2. Deploy StackSet, 3. Run the Wizard, 4. Launch Scans" />
+ <img src="/images/organizations/onboarding-flow.svg" alt="Onboarding flow: 1. Start the Wizard, 2. Deploy the Roles (single CloudFormation stack), 3. Discover and Connect, 4. Launch Scans" />
</Frame>
-## Key Concepts
+## Step 1: Start the Organization Wizard
-### What is an External ID?
-
-An **External ID** is a security token that Prowler generates unique to your tenant. When Prowler assumes the IAM role in your AWS account, it presents this External ID to prove its identity.
-
-This prevents the [confused deputy problem](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) — a scenario where an unauthorized party could trick AWS into granting access to your account. By requiring the External ID, only your specific Prowler tenant can assume the role.
-
-You don't need to create the External ID yourself — Prowler generates it automatically and displays it in the wizard for you to copy.
-
-### Two Roles Architecture
-
-Prowler requires **two separate IAM roles** deployed in different places, each with a distinct purpose:
-
-| Role | Where it lives | What it does | How to deploy it |
-|------|---------------|--------------|------------------|
-| **ProwlerScan** (management account) | Your management (root) account only | Discovers the Organization structure **and** scans the management account. Has additional Organizations discovery permissions. | Via **Quick Create** link or **manually** in the IAM Console ([Step 1](#step-1-create-the-management-account-role)). Cannot be deployed via StackSet. |
-| **ProwlerScan** (member accounts) | Every member account | Scans the account for security findings. | Via **CloudFormation StackSet** ([Step 2](#step-2-deploy-the-cloudformation-stackset)). Automated across all accounts. |
-
-<Frame caption="Both roles share the same name `ProwlerScan`. The management account role includes additional Organization discovery permissions.">
- <img src="/images/organizations/two-roles-architecture.svg" alt="Two Roles Architecture: ProwlerScan in management account (Quick Create or Manual, discovery + scanning) and ProwlerScan in member accounts (via StackSet, scanning only)" />
-</Frame>
-
-<Note>
-**Same name, different permissions.** Both roles are named `ProwlerScan` — Prowler expects a consistent role name across all accounts. The management account role has the same scanning permissions as member accounts, plus additional Organizations discovery permissions (see [Step 1](#step-1-create-the-management-account-role) for the full list).
-</Note>
-
-### What is a CloudFormation StackSet?
-
-A [CloudFormation StackSet](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/what-is-cfnstacksets.html) lets you deploy the same CloudFormation template across multiple AWS accounts in a single operation. Prowler uses a StackSet to deploy the **ProwlerScan** IAM role into every member account of your organization, so you don't have to create the role manually in each account.
-
-## Prerequisites
-
-### Prowler Cloud Account
-
-You need an active [Prowler Cloud](https://cloud.prowler.com) account. Each AWS account you connect will count as a provider in your subscription. See [Billing Impact](#billing-impact) for details.
-
-### AWS Organization Enabled
-
-Your AWS environment must have [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html) enabled. You will need access to the **management account** (or a delegated administrator account) to provide the Organization ID and IAM Role ARN.
-
-## Step 1: Create the Management Account Role
-
-The first role you need to create is the **management account role**. This role allows Prowler to discover your Organization structure — listing accounts, OUs, and hierarchy.
-
-<Warning>
-**StackSets do not deploy to the management account.** Organizational CloudFormation StackSets with service-managed permissions only target member accounts — this is an AWS limitation, not a Prowler one. You must create the management account role separately, either via the Quick Create link ([Option A](#option-a-quick-create-link-fastest)) or manually ([Option B](#option-b-create-the-role-manually)).
-</Warning>
-
-<Note>
-**The role must be named `ProwlerScan`** — the same name as the role deployed to member accounts via StackSet. Prowler expects a consistent role name across all accounts in the Organization. If you use a different name, connection tests and scans will fail for the management account.
-</Note>
-
-### Option A: Quick Create Link (Fastest)
-
-The Prowler wizard provides a one-click link that opens the AWS Console with the CloudFormation template pre-configured. This creates a **CloudFormation Stack** (not a StackSet) that deploys the ProwlerScan role with Organizations permissions enabled in your management account.
-
-<Tip>
-**[Open Quick Create Stack in AWS Console →](https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/quickcreate?templateURL=https%3A%2F%2Fprowler-cloud-public.s3.eu-west-1.amazonaws.com%2Fpermissions%2Ftemplates%2Faws%2Fcloudformation%2Fprowler-scan-role.yml&stackName=Prowler¶m_EnableOrganizations=true)**
-
-Opens the CloudFormation Console with the Prowler scan role template and `EnableOrganizations=true` pre-filled. You will need to enter the **ExternalId** parameter manually — copy it from the Prowler wizard ([Step 4](#step-4-authenticate-with-your-management-account)).
-</Tip>
-
-1. Click **[Open Quick Create Stack in AWS Console →](https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/quickcreate?templateURL=https%3A%2F%2Fprowler-cloud-public.s3.eu-west-1.amazonaws.com%2Fpermissions%2Ftemplates%2Faws%2Fcloudformation%2Fprowler-scan-role.yml&stackName=Prowler¶m_EnableOrganizations=true)** or use the **Create Stack in Management Account** button in the Prowler wizard (which also pre-fills the ExternalId).
-2. Enter the **ExternalId** parameter if not pre-filled.
-3. Check **"I acknowledge that AWS CloudFormation might create IAM resources with custom names"** and click **Create stack**.
-4. Wait for the stack to reach **CREATE_COMPLETE** status.
-
-Take note of the **Role ARN** from the stack's **Outputs** tab — you will need it in the wizard.
-
-### Option B: Create the Role Manually
-
-1. Sign in to the [AWS IAM Console](https://console.aws.amazon.com/iam/) in your **management account**.
-
-2. Go to **Roles > Create role** and select **Custom trust policy**.
-
-3. Paste the following trust policy. This allows Prowler Cloud to assume the role using your tenant's External ID (you will get this from the Prowler wizard in [Step 3](#step-3-start-the-organization-wizard)):
-
-```json
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Effect": "Allow",
- "Principal": {
- "AWS": "arn:aws:iam::232136659152:root"
- },
- "Action": "sts:AssumeRole",
- "Condition": {
- "StringEquals": {
- "sts:ExternalId": "<YOUR_EXTERNAL_ID>"
- },
- "StringLike": {
- "aws:PrincipalArn": "arn:aws:iam::232136659152:role/prowler*"
- }
- }
- }
- ]
-}
-```
-
-Replace `<YOUR_EXTERNAL_ID>` with the External ID shown in the Prowler wizard.
-
-4. Attach the following AWS managed policies:
- - **SecurityAudit**
- - **ViewOnlyAccess**
-
- This allows Prowler to also scan the management account for security findings, just like any other account.
-
-5. Create an additional inline policy with the following permissions. These are specific to the management account and allow Prowler to discover your Organization structure:
-
-```json
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "ProwlerOrganizationDiscovery",
- "Effect": "Allow",
- "Action": [
- "organizations:DescribeAccount",
- "organizations:DescribeOrganization",
- "organizations:ListAccounts",
- "organizations:ListAccountsForParent",
- "organizations:ListOrganizationalUnitsForParent",
- "organizations:ListRoots",
- "organizations:ListTagsForResource"
- ],
- "Resource": "*"
- },
- {
- "Sid": "ProwlerStackSetManagement",
- "Effect": "Allow",
- "Action": [
- "organizations:RegisterDelegatedAdministrator",
- "iam:CreateServiceLinkedRole"
- ],
- "Resource": "*"
- }
- ]
-}
-```
-
-<Tip>
-You can optionally restrict the `Resource` field to your specific Organization ARN (e.g., `arn:aws:organizations::123456789012:organization/o-abc123def4`) instead of `"*"` to minimize the blast radius.
-</Tip>
-
-6. Name the role **`ProwlerScan`** and click **Create role**. Take note of the **Role ARN** — you will need it in the Prowler wizard.
-
-The ARN follows this format: `arn:aws:iam::<account-id>:role/ProwlerScan`
-
-<Warning>
-The role **must** be named `ProwlerScan`. Do not use a different name.
-</Warning>
-
-<Note>
-If you just created the role, it may take up to **60 seconds** for AWS to propagate it. If you get an error in the Prowler wizard, wait a moment and try again.
-</Note>
-
-## Step 2: Deploy the CloudFormation StackSet
-
-After creating the management account role, the next step is to deploy the **ProwlerScan** role to your member accounts using a CloudFormation StackSet. This is the recommended method for consistent, scalable deployment across your entire organization.
-
-The StackSet uses **service-managed permissions**, which means AWS Organizations handles the cross-account deployment automatically — you don't need to create execution roles manually in each account. The StackSet deploys the ProwlerScan IAM role in every target member account, enabling Prowler to assume that role for cross-account scanning.
-
-<Note>
-**Trusted access required:** CloudFormation StackSets must have trusted access enabled in your management account. Verify this in the AWS Console under **AWS Organizations > Settings > Trusted access for AWS CloudFormation StackSets**.
-</Note>
-
-<Warning>
-**The Quick Create link creates a Stack, not a StackSet.** The link in the Prowler wizard creates a CloudFormation **Stack** that deploys the ProwlerScan role in your management account only ([Step 1](#step-1-create-the-management-account-role)). To deploy the role across **member accounts**, you must create a StackSet manually as described below. AWS does not support Quick Create links for StackSets.
-</Warning>
-
-<Tip>
-**[Open StackSets Console →](https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacksets/create)**
-
-Opens the CloudFormation StackSets creation page directly. You will need to paste the template URL and ExternalId manually.
-</Tip>
-
-1. Click the link above or navigate to **CloudFormation > StackSets > Create StackSet** in your management account.
-2. Choose **Service-managed permissions**.
-3. Select **Amazon S3 URL** as the template source and paste the following URL:
- ```
- https://prowler-cloud-public.s3.eu-west-1.amazonaws.com/permissions/templates/aws/cloudformation/prowler-scan-role.yml
- ```
-4. Set the **ExternalId** parameter to the External ID shown in the Prowler wizard.
-5. Choose your deployment targets (entire organization or specific OUs).
-6. Select the AWS regions where you want the role deployed.
-7. Click **Create StackSet**.
-
-### Verify StackSet Deployment
-
-After deploying, verify that all stack instances completed successfully:
-
-1. In the CloudFormation Console, go to **StackSets** and select your Prowler StackSet.
-2. Click the **Stack instances** tab.
-3. Confirm that all instances show **Status: CURRENT** and **Stack status: CREATE_COMPLETE**.
-
-Deployment typically takes **2–5 minutes** for medium-sized organizations. Large organizations (500+ accounts) may take longer.
-
-<Note>
-**Prefer Terraform?** You can deploy the ProwlerScan role using Terraform instead. See the [StackSets deployment guide](/user-guide/providers/aws/organizations#deploying-prowler-iam-roles-across-aws-organizations) for the Terraform module.
-</Note>
-
-### Key Considerations
-
-- **Service-managed permissions**: Always select **Service-managed permissions** when creating the StackSet. This lets AWS Organizations manage the deployment automatically across current and future member accounts.
-- **Least privilege**: The ProwlerScan role deployed by the StackSet uses `SecurityAudit` and `ViewOnlyAccess` — AWS managed policies that grant read-only access — plus a small set of additional read-only permissions for services not covered by those policies. See the [CloudFormation template](https://prowler-cloud-public.s3.eu-west-1.amazonaws.com/permissions/templates/aws/cloudformation/prowler-scan-role.yml) for the full list. Prowler does not make any changes to your accounts.
-- **New accounts**: When you add new accounts to your AWS Organization, the StackSet automatically deploys the ProwlerScan role to them if you targeted the organization root or the relevant OU. Combined with Prowler's 6-hour automatic sync, new accounts are onboarded end-to-end without manual intervention.
-- **Management account**: Organizational StackSets **do not deploy to the management account itself**. If you want to scan the management account, you need to create the ProwlerScan role there separately using a regular CloudFormation Stack.
-
-## Step 3: Start the Organization Wizard
-
-Now that both roles are deployed — the management account role (Step 1) and the ProwlerScan role in member accounts (Step 2) — you can start the Prowler wizard.
+The Prowler wizard walks you through the entire flow: deploying both roles from a single CloudFormation stack, discovering your accounts, testing connectivity, and launching scans.
### Open the Wizard
@@ -279,29 +74,50 @@ Now that both roles are deployed — the management account role (Step 1) and th
Click **Next** to proceed to the authentication phase.
-## Step 4: Authenticate with Your Management Account
+## Step 2: Authenticate with Your Management Account
-The wizard's **Authentication Details** page guides you through three actions: deploying the roles in AWS, entering the management account Role ARN, and confirming the deployment.
+The **Authentication Details** page guides you through three actions: deploying the roles in AWS, entering the deployment account Role ARN, and confirming the deployment. The deployment account is either the management account or, when delegated administrator mode is selected, the delegated administrator account.
### External ID
-The wizard displays a **Prowler External ID** at the top — auto-generated and unique to your tenant. Click the copy icon to copy it. You will need this External ID for both the management account Stack and the member accounts StackSet.
+The wizard displays a **Prowler External ID** at the top — auto-generated and unique to your tenant. Click the copy icon to copy it. The External ID is pre-filled into the deployment link, and the single stack applies it to both the management account role and the member-account StackSet. Learn more in [What Is an External ID?](#what-is-an-external-id).
### Deploy the Roles
-The wizard provides two deployment actions:
+<VersionBadge version="5.35.0" />
-1. **Create Stack in Management Account** — opens a Quick Create link that deploys the ProwlerScan role with `EnableOrganizations=true` in your management account ([Step 1](#step-1-create-the-management-account-role)). The External ID is pre-filled.
+The wizard deploys the deployment account role and the member-account StackSet in a **single** CloudFormation Stack:
-2. **Open StackSets Console** — links to the CloudFormation StackSets console where you create a StackSet for member accounts ([Step 2](#step-2-deploy-the-cloudformation-stackset)). Copy the template URL shown in the wizard and paste the External ID manually.
+<Note>
+**Prefer to use your own role?** You do not have to use the Quick Create template. Create the ProwlerScan role yourself — through the IAM Console, Terraform, or your own CloudFormation [(Following this guide)](#deploy-the-roles-manually) — and paste its ARN into the Role ARN field below. The role must use the external ID from the earlier step and include the trust policy and permissions described in [Deploy the Roles Manually](#deploy-the-roles-manually).
+</Note>
+
+1. **Organizational Unit or Root ID** — enter the AWS OU (`ou-xxxx-yyyyyyyy`) or organization root (`r-xxxx`) you want to onboard. Prowler rolls the ProwlerScan role out to every member account under this target. Find it in the [AWS Organizations Console](https://console.aws.amazon.com/organizations/); use the **root ID** (`r-`) to cover the entire organization or an **OU ID** (`ou-`) to target a specific unit.
+
+2. *(Optional)* Check **"I'm deploying from a delegated administrator account"** if you launch the stack from a delegated administrator account instead of the management account.
+
+3. **Create Stack in Management Account** — or **Create Stack in Delegated Administrator Account** when delegated administrator mode is selected — opens a Quick Create link that deploys, in a single stack: the ProwlerScan role in the account where you launch the stack (`DeployLocalRole`, with `EnableOrganizations=true`) **and** a service-managed StackSet (`DeployStackSet`) that rolls the role out to your member accounts. The External ID, OU/Root ID, and deployment options are pre-filled.
<Frame>
- <img src="/images/organizations/authentication-details.png" alt="Authentication Details form showing External ID, two deployment buttons (Create Stack in Management Account and Open StackSets Console), Management Account Role ARN field, and deployment confirmation checkbox" />
+ <img src="/images/organizations/authentication-details.png" alt="Authentication Details form showing External ID, Organizational Unit or Root ID field, delegated administrator checkbox, deployment account stack button, deployment account Role ARN field, and deployment confirmation checkbox" />
</Frame>
-### Enter the Management Account Role ARN
+<Tip>
+**Finding your Organizational Unit or Root ID.** In the [AWS Organizations Console](https://console.aws.amazon.com/organizations/) the root (`r-…`) and OU (`ou-…`) IDs appear in the account tree, or run these from your management account:
-Paste the **Role ARN** of the management account role you created in [Step 1](#step-1-create-the-management-account-role) into the **Management Account Role ARN** field.
+```bash
+# Root ID — deploys the role to the entire organization
+aws organizations list-roots --query 'Roots[0].Id' --output text
+
+# OU IDs under the root — to target a specific unit instead
+aws organizations list-organizational-units-for-parent --parent-id r-xxxx \
+ --query 'OrganizationalUnits[].{Name:Name,Id:Id}' --output table
+```
+</Tip>
+
+### Enter the Deployment Account Role ARN
+
+Paste the **Role ARN** created by the stack above into the **Management Account Role ARN** field or, when delegated administrator mode is selected, the **Delegated Administrator Account Role ARN** field.
The ARN follows this format:
```
@@ -311,12 +127,16 @@ arn:aws:iam::<account-id>:role/ProwlerScan
For example: `arn:aws:iam::123456789012:role/ProwlerScan`
<Frame>
- <img src="/images/organizations/role-arn-field.png" alt="Management Account Role ARN field in the Authentication Details form" />
+ <img src="/images/organizations/role-arn-field.png" alt="Deployment account Role ARN field in the Authentication Details form" />
</Frame>
+<Note>
+It may take up to **60 seconds** for AWS to generate the IAM Role ARN after the stack completes. If the wizard reports an error, wait a moment and try again.
+</Note>
+
### Confirm and Discover
-1. Check the box: **"The Stack and StackSet have been successfully deployed in AWS"**.
+1. Check the box: **"The Stack has been successfully deployed in AWS"**.
2. Click **Authenticate**.
Here's what happens behind the scenes:
@@ -324,7 +144,7 @@ Here's what happens behind the scenes:
- An asynchronous discovery is triggered to query your AWS Organization structure.
- You will see a **"Gathering AWS Accounts..."** spinner — this typically takes **30 seconds to 2 minutes** depending on your organization size.
-## Step 5: Select Accounts to Scan
+## Step 3: Select Accounts to Scan
### Understanding the Tree View
@@ -335,6 +155,7 @@ Once discovery completes, the wizard displays a **hierarchical tree view** of yo
</Frame>
- The tree supports up to **5 levels of nesting** (Root > OUs > Sub-OUs > Accounts).
+- If you deployed the stack for just one OU, that OU will be preselected in the tree.
- **Selecting an OU** automatically selects all accounts within it.
- **Individual overrides**: deselect specific accounts even if the parent OU is selected.
- The header shows **"X of Y accounts selected"** to track your selection.
@@ -351,14 +172,12 @@ Only **ACTIVE** accounts can be selected for scanning:
| **CLOSED** | No | Account has been closed. |
<Note>
-**Your existing data is safe.** If an AWS account is already connected to Prowler as an individual provider, it will appear in the tree with a checkmark indicator.
+**Your existing data is safe.** If an AWS account is already connected to Prowler as an individual provider, it appears in the tree with a checkmark indicator.
When you proceed:
- The existing provider is **linked** to the organization — it is **not** duplicated.
- All your **historical scan data and findings are preserved** — nothing is overwritten.
- There is **no additional billing** — the existing provider is reused.
-
-This is completely safe. You are simply associating the account with the organization for easier management.
</Note>
### Custom Aliases
@@ -367,14 +186,9 @@ You can edit the display name for each account before connecting. This alias is
### Blocked Accounts
-Some accounts may appear as **blocked** (grayed out, not selectable). This happens when:
-- The account is **already linked to a different organization** in Prowler (`linked_to_other_organization`).
+Some accounts may appear as **blocked** (grayed out, not selectable) when the account is **already linked to a different organization** in Prowler (`linked_to_other_organization`). Hover over the blocked account to see the specific reason.
-Hover over the blocked account to see the specific reason.
-
-## Step 6: Test Connections
-
-### How Connection Testing Works
+## Step 4: Test Connections
Click **Test Connections** to verify that Prowler can assume the **ProwlerScan** role in each selected member account.
@@ -382,157 +196,225 @@ Click **Test Connections** to verify that Prowler can assume the **ProwlerScan**
<img src="/images/organizations/test-connections.png" alt="Connection testing in progress with spinners on each account" />
</Frame>
-- Each account shows a real-time status indicator:
- - **Spinner** — test in progress
- - **Green checkmark (✓)** — connection successful
- - **Red icon (✗)** — connection failed (hover to see the error)
-
-### All Tests Pass
+Each account shows a real-time status indicator:
+- **Spinner** — test in progress
+- **Green checkmark (✓)** — connection successful
+- **Red icon (✗)** — connection failed (hover to see the error)
If every account connects successfully, you automatically advance to the next step.
-### Some Tests Fail
+### When Some Tests Fail
-An error banner appears: **"There was a problem connecting to some accounts."**
-
-You have two options:
+An error banner appears: **"There was a problem connecting to some accounts."** You have two options:
**a) Fix and retry:**
1. Go to the AWS Console and verify the StackSet deployed to the failing accounts.
2. Check that the External ID in the StackSet matches the one shown in Prowler.
3. Return to Prowler and click **Test Connections** — only the **failed accounts are re-tested** (smart retry). Accounts that already passed are not tested again.
-<Frame>
- <img src="/images/organizations/test-connections-button.png" alt="Test Connections button" />
-</Frame>
-
**b) Skip and continue:**
-Click **Skip Connection Validation** to proceed with only the accounts that connected successfully. The failed accounts will not be scanned.
+Click **Skip Connection Validation** to proceed with only the accounts that connected successfully. The failed accounts will not be scanned. This option is only available when at least one account connected successfully.
<Frame>
<img src="/images/organizations/connection-failures-skip.png" alt="Connection test results showing failed accounts with error banner and Skip Connection Validation button" />
</Frame>
-<Note>
-**Skip Connection Validation** is only available when at least one account connected successfully.
-</Note>
+If **no accounts** connected successfully, you cannot proceed. Fix the underlying connection issues — see [Troubleshooting](#troubleshooting) — and retry before launching scans.
-### All Tests Fail
+## Step 5: Launch Scans
-If **no accounts** connected successfully, you cannot proceed:
+The Organizations wizard uses the same schedule controls described in [Scan Scheduling](/user-guide/tutorials/prowler-scan-scheduling#schedule-options).
-> *"No accounts connected successfully. Fix the connection errors and retry before launching scans."*
-
-You must fix the underlying connection issues before continuing. See [Updating Credentials](#updating-credentials) below.
-
-### Updating Credentials
-
-If connection tests fail, here's how to fix common issues:
-
-1. Open the [CloudFormation Console](https://console.aws.amazon.com/cloudformation/) and check that your StackSet instances show **CREATE_COMPLETE** for the failing accounts. If not, update the StackSet to include the missing OUs.
-2. Compare the **ExternalId** parameter in your StackSet with the External ID displayed in the Prowler wizard. They must match exactly.
-3. After fixing the issue in AWS, return to Prowler and click **Test Connections**. Only the previously failed accounts will be re-tested.
-
-## Step 7: Launch Scans
-
-### Choose Scan Schedule
-
-| Schedule Option | Description |
-|-----------------|-------------|
-| **Scan Daily (every 24 hours)** | Creates a recurring daily scan for all connected accounts (default). |
-| **Run a single scan (no recurring schedule)** | Launches a one-time scan. |
-
-### Launch
-
-Click **Launch scan**. A toast notification confirms: *"Scan Launched — Daily scan scheduled for X accounts"* with a link to the Scans page. You will be redirected to the **Providers** page.
-
-Scans are only launched for accounts that are accessible (passed connection testing) and were selected.
+Click **Save**, **Save and launch scan**, or **Launch scan**, depending on the selected schedule option. A toast notification confirms whether the schedule was saved, scans were launched, or both, and includes a link to the **Scans** page. Prowler then redirects to the **Providers** page. Scans launch only for accounts that passed connection testing and were selected.
<Frame>
<img src="/images/organizations/launch-scan.png" alt="Launch Scan step showing Accounts Connected confirmation, scan schedule selector, and Launch scan button" />
</Frame>
-### What Happens Next
-
+After launching:
- Scans appear in the **Scans** page as they start and complete.
- Results populate the **Overview** and **Findings** pages.
-- Prowler runs an **automatic sync every 6 hours** to detect new accounts added to your Organization or accounts that have been removed. New accounts are onboarded automatically based on the parent OU configuration.
+- Prowler runs an **automatic sync every 6 hours** to detect accounts added to or removed from your Organization. New accounts under the targeted OU or root are onboarded automatically.
## Billing Impact
Each AWS account you connect through the Organizations wizard counts as one **provider** in your Prowler Cloud subscription.
- **Already-connected accounts**: if an account was already linked as a provider, adding it to the organization does **not** incur additional billing. The existing provider is reused.
-- **Large organizations**: connecting a 500-account organization will result in up to 500 providers on your subscription. Review your plan limits before proceeding.
+- **Large organizations**: connecting a 500-account organization results in up to 500 providers on your subscription. Review your plan limits before proceeding.
- **Deleted providers**: if you later remove an account, the deleted provider no longer counts toward your subscription.
-For pricing details, see [Prowler Cloud Pricing](/getting-started/products/prowler-cloud-pricing).
+For pricing details, see [Prowler Cloud Pricing](https://prowler.com/pricing).
## Troubleshooting
-### Invalid AWS Organization ID
+### Only Some Accounts Connect
-*"Must be a valid AWS Organization ID"*
+Discovery succeeds and the tree view appears, but only one account — or a handful — passes the connection test. This almost always means the ProwlerScan role reached the deployment account but not every member account.
-- Verify the Organization ID format: `o-` followed by 10–32 lowercase alphanumeric characters (e.g., `o-abc123def4`)
-- Copy it directly from the [AWS Organizations Console](https://console.aws.amazon.com/organizations/) to avoid typos
+- **Confirm the StackSet deployed.** Open the [CloudFormation Console](https://console.aws.amazon.com/cloudformation/) in the deployment account, select your Prowler StackSet, open the **Stack instances** tab, and confirm every instance shows **Status: CURRENT** and **Stack status: CREATE_COMPLETE**. Instances still in progress or in a failed state explain the missing accounts.
+- **Check the targeted OU or root.** The single stack only rolls the role out to accounts under the **Organizational Unit or Root ID** you entered in [Step 2](#step-2-authenticate-with-your-management-account). Accounts in other OUs are not covered — redeploy targeting the organization root (`r-`) or add the missing OUs.
+- **Verify the deployment account.** The role is created only in the account where you launched the stack. If you deployed from a **delegated administrator account**, confirm that account is a **registered delegated administrator** for CloudFormation StackSets (registered through AWS Organizations), not just a regular member account. A regular member account cannot create a service-managed StackSet, so only its own role is created — leaving every other account without the role.
+- **Suspended accounts** cannot be scanned. Deselect them and proceed.
-### Invalid IAM Role ARN
+### No Accounts Connect
-*"Must be a valid IAM Role ARN"*
+No account passes the connection test.
-- Verify the ARN format: `arn:aws:iam::<12-digit-account-id>:role/<role-name>`
-- Copy the ARN directly from the [IAM Console](https://console.aws.amazon.com/iam/) in your management account
+- **External ID mismatch.** Compare the **ExternalId** parameter in your StackSet with the External ID shown in the Prowler wizard. They must match exactly.
+- **StackSet not deployed.** Confirm the StackSet exists and its instances reached **CREATE_COMPLETE**. If you deployed the roles manually, verify [trusted access for CloudFormation StackSets](#member-account-role-stackset) is enabled.
+- **IP-based policies.** If your accounts restrict access by IP, allow the [Prowler Cloud egress IPs](/security/networking).
-### Authentication Failed
+### Authentication Fails or Times Out
-*"Authentication failed. Please verify the StackSet deployment and Role ARN"*
+*"Authentication failed. Please verify the StackSet deployment and Role ARN"* or *"Authentication timed out"*
-- Verify the management account role exists and was created in [Step 1](#step-1-create-the-management-account-role)
-- Confirm the trust policy includes the correct External ID from the wizard
-- Check the role has all Organizations discovery permissions listed in [Step 1](#step-1-create-the-management-account-role)
-- Double-check the Role ARN format and account ID for typos
+- Verify the deployment account role exists and is named exactly `ProwlerScan`.
+- Confirm the trust policy includes the correct External ID from the wizard.
+- Check the role has the Organizations discovery permissions listed in [Deploy the Roles Manually](#management-account-role).
+- Double-check the Role ARN format and account ID for typos.
+- Retry — the role can take up to **60 seconds** to propagate, and a second attempt often succeeds. For very large organizations (500+ accounts), allow extra time for discovery.
-### Authentication Timed Out
+### Invalid Organization ID or Role ARN
-*"Authentication timed out"*
+*"Must be a valid AWS Organization ID"* or *"Must be a valid IAM Role ARN"*
-- Retry the authentication step — the second attempt often succeeds
-- Check for AWS API rate limiting on the Organizations service
-- For very large organizations (500+ accounts), allow extra time for discovery
-
-### Connection Test Fails for All Accounts
-
-No accounts pass the connection test.
-
-- Verify the CloudFormation StackSet was deployed — complete [Step 2](#step-2-deploy-the-cloudformation-stackset) and wait for stack instances to reach **CREATE_COMPLETE**
-- Check that the **ExternalId** parameter in the StackSet matches the External ID shown in the Prowler wizard
-- If your accounts use IP-based IAM policies, allow [Prowler Cloud public IPs](/user-guide/tutorials/prowler-cloud-public-ips)
-
-### Connection Test Fails for Some Accounts
-
-Some accounts show a red icon while others pass.
-
-- Expand the StackSet deployment to include the OUs containing the failing accounts
-- Suspended accounts cannot be scanned — deselect them and proceed
-- Ensure the [STS regional endpoint](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html) is enabled in the account's region
-- After fixing, click **Test Connections** — only the failed accounts will be re-tested
-
-### No Accounts Connected Successfully
-
-*"No accounts connected successfully. Fix the connection errors and retry before launching scans."*
-
-- Hover over the red icon on each account to see the specific error
-- Fix the underlying issues using the guidance above
-- Click **Test Connections** to retry
+- Organization ID format: `o-` followed by 10–32 lowercase alphanumeric characters (e.g., `o-abc123def4`).
+- Role ARN format: `arn:aws:iam::<12-digit-account-id>:role/ProwlerScan`.
+- Copy both directly from the AWS Console to avoid typos.
### Failed to Apply Discovery
*"Failed to apply discovery"*
-- Check the `blocked_reasons` field for any blocked accounts
-- Retry the operation
-- If the error persists, contact [Prowler Support](mailto:support@prowler.com)
+- Check the `blocked_reasons` field for any blocked accounts and retry the operation.
+- If the error persists, contact [Prowler Support](mailto:support@prowler.com).
+
+## Deploy the Roles Manually
+
+The wizard's **Create Stack** button is the fastest path, but you can create both roles yourself — for example with Terraform or your own CloudFormation — and paste the management account Role ARN into [Step 2](#step-2-authenticate-with-your-management-account). Both roles must be named `ProwlerScan`, since Prowler expects a consistent role name across all accounts.
+
+<Note>
+**Prefer Terraform?** You can deploy the ProwlerScan role across the organization with Terraform instead of CloudFormation. See the [StackSets deployment guide](/user-guide/providers/aws/organizations#deploying-prowler-iam-roles-across-aws-organizations) for the module.
+</Note>
+
+### Management Account Role
+
+The management account role lets Prowler discover your Organization structure — listing accounts, OUs, and hierarchy — and scan the management account itself. StackSets with service-managed permissions do not deploy to the management account, so this role is always created separately from the member-account StackSet.
+
+1. Sign in to the [AWS IAM Console](https://console.aws.amazon.com/iam/) in your **management account** (or delegated administrator account).
+2. Go to **Roles > Create role** and select **Custom trust policy**.
+3. Paste the following trust policy, replacing `<YOUR_EXTERNAL_ID>` with the External ID shown in the Prowler wizard:
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Principal": {
+ "AWS": "arn:aws:iam::232136659152:root"
+ },
+ "Action": "sts:AssumeRole",
+ "Condition": {
+ "StringEquals": {
+ "sts:ExternalId": "<YOUR_EXTERNAL_ID>"
+ },
+ "StringLike": {
+ "aws:PrincipalArn": "arn:aws:iam::232136659152:role/prowler*"
+ }
+ }
+ }
+ ]
+}
+```
+
+4. Attach the AWS managed policies **SecurityAudit** and **ViewOnlyAccess** so Prowler can scan the management account for security findings.
+5. Add an inline policy with the Organizations discovery permissions:
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Sid": "ProwlerOrganizationDiscovery",
+ "Effect": "Allow",
+ "Action": [
+ "organizations:DescribeAccount",
+ "organizations:DescribeOrganization",
+ "organizations:ListAccounts",
+ "organizations:ListAccountsForParent",
+ "organizations:ListOrganizationalUnitsForParent",
+ "organizations:ListRoots",
+ "organizations:ListTagsForResource"
+ ],
+ "Resource": "*"
+ },
+ {
+ "Sid": "ProwlerStackSetManagement",
+ "Effect": "Allow",
+ "Action": [
+ "organizations:RegisterDelegatedAdministrator",
+ "iam:CreateServiceLinkedRole"
+ ],
+ "Resource": "*"
+ }
+ ]
+}
+```
+
+<Tip>
+You can restrict the `Resource` field to your specific Organization ARN (e.g., `arn:aws:organizations::123456789012:organization/o-abc123def4`) instead of `"*"` to minimize the blast radius.
+</Tip>
+
+6. Name the role **`ProwlerScan`** and click **Create role**. The ARN follows the format `arn:aws:iam::<account-id>:role/ProwlerScan` — paste it into the wizard.
+
+### Member Account Role (StackSet)
+
+Deploy the ProwlerScan role to every member account with a [CloudFormation StackSet](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/what-is-cfnstacksets.html), so you don't create the role manually in each account.
+
+<Note>
+**Trusted access required.** CloudFormation StackSets must have trusted access enabled in your management account. Verify this under **AWS Organizations > Settings > Trusted access for AWS CloudFormation StackSets**.
+</Note>
+
+1. In your management account, navigate to **CloudFormation > StackSets > Create StackSet** ([open directly](https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacksets/create)).
+2. Choose **Service-managed permissions** so AWS Organizations deploys the role automatically across current and future member accounts.
+3. Select **Amazon S3 URL** as the template source and paste:
+ ```
+ https://prowler-cloud-public.s3.eu-west-1.amazonaws.com/permissions/templates/aws/cloudformation/prowler-scan-role.yml
+ ```
+4. Set the **ExternalId** parameter to the External ID shown in the Prowler wizard.
+5. Choose your deployment targets (entire organization or specific OUs) and regions, then click **Create StackSet**.
+6. Open the **Stack instances** tab and confirm every instance shows **Status: CURRENT** and **Stack status: CREATE_COMPLETE**. Deployment typically takes **2–5 minutes**; large organizations (500+ accounts) may take longer.
+
+The StackSet role uses read-only access only (`SecurityAudit`, `ViewOnlyAccess`, plus a small set of additional read-only permissions). Prowler makes no changes to your accounts. See the [CloudFormation template](https://prowler-cloud-public.s3.eu-west-1.amazonaws.com/permissions/templates/aws/cloudformation/prowler-scan-role.yml) for the full list. When you add new accounts under the targeted OU or root, the StackSet deploys the role automatically, and Prowler's 6-hour sync onboards them end-to-end.
+
+## Key Concepts
+
+### What Is an External ID?
+
+An **External ID** is a security token that Prowler generates unique to your tenant. When Prowler assumes the IAM role in your AWS account, it presents this External ID to prove its identity.
+
+This prevents the [confused deputy problem](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) — a scenario where an unauthorized party could trick AWS into granting access to your account. By requiring the External ID, only your specific Prowler tenant can assume the role. Prowler generates it automatically and displays it in the wizard for you to copy.
+
+### Two Roles Architecture
+
+Prowler uses **two IAM roles**, both named `ProwlerScan` but deployed in different places:
+
+| Role | Where it lives | What it does |
+|------|---------------|--------------|
+| **ProwlerScan** (management account) | Your management (or delegated administrator) account | Discovers the Organization structure **and** scans that account. Includes additional Organizations discovery permissions. |
+| **ProwlerScan** (member accounts) | Every member account | Scans the account for security findings. |
+
+Both roles share the name `ProwlerScan` because Prowler expects a consistent role name across all accounts. The single CloudFormation stack in [Step 2](#step-2-authenticate-with-your-management-account) deploys both at once.
+
+<Frame caption="Both roles share the same name `ProwlerScan`. The management account role includes additional Organization discovery permissions.">
+ <img src="/images/organizations/two-roles-architecture.svg" alt="Two Roles Architecture: ProwlerScan in management account (discovery + scanning) and ProwlerScan in member accounts (via StackSet, scanning only)" />
+</Frame>
+
+### What Is a CloudFormation StackSet?
+
+A [CloudFormation StackSet](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/what-is-cfnstacksets.html) deploys the same CloudFormation template across multiple AWS accounts in a single operation. Prowler uses a service-managed StackSet to deploy the **ProwlerScan** IAM role into every member account of your organization, so you don't create the role manually in each account. StackSets do not deploy to the management account, which is why that role is created separately.
## What's Next
diff --git a/docs/user-guide/tutorials/prowler-cloud-azure-management-groups.mdx b/docs/user-guide/tutorials/prowler-cloud-azure-management-groups.mdx
new file mode 100644
index 0000000000..98cfe095ce
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-cloud-azure-management-groups.mdx
@@ -0,0 +1,11 @@
+---
+title: 'Azure Management Groups'
+description: 'Onboard all Azure subscriptions in your management groups through a single guided wizard'
+tag: "Coming Soon"
+---
+
+Onboarding Azure management groups through a single guided wizard is coming soon to Prowler Cloud.
+
+Today, Azure subscriptions are onboarded individually. See [Getting Started with Azure](/user-guide/providers/azure/getting-started-azure) and [Bulk Provider Provisioning](/user-guide/tutorials/bulk-provider-provisioning) to automate onboarding multiple subscriptions.
+
+Keep an eye on the [changelog](https://github.com/prowler-cloud/prowler/releases) for updates.
diff --git a/docs/user-guide/tutorials/prowler-cloud-gcp-organizations.mdx b/docs/user-guide/tutorials/prowler-cloud-gcp-organizations.mdx
new file mode 100644
index 0000000000..c0c11747a9
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-cloud-gcp-organizations.mdx
@@ -0,0 +1,11 @@
+---
+title: 'GCP Organizations'
+description: 'Onboard all GCP projects in your organization through a single guided wizard'
+tag: "Coming Soon"
+---
+
+Onboarding a full GCP organization through a single guided wizard is coming soon to Prowler Cloud.
+
+Today, GCP projects are onboarded individually. See [Getting Started with GCP](/user-guide/providers/gcp/getting-started-gcp) and [Bulk Provider Provisioning](/user-guide/tutorials/bulk-provider-provisioning) to automate onboarding multiple projects.
+
+Keep an eye on the [changelog](https://github.com/prowler-cloud/prowler/releases) for updates.
diff --git a/docs/user-guide/tutorials/prowler-cloud-lighthouse-multi-llm.mdx b/docs/user-guide/tutorials/prowler-cloud-lighthouse-multi-llm.mdx
new file mode 100644
index 0000000000..0cb251df1f
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-cloud-lighthouse-multi-llm.mdx
@@ -0,0 +1,82 @@
+---
+title: 'Using Multiple LLM Providers'
+sidebarTitle: 'Multiple LLM Providers'
+---
+
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+Lighthouse AI on Prowler Cloud supports multiple Large Language Model (LLM) providers, so teams can choose the option that best fits their infrastructure, compliance requirements, and cost considerations. This guide explains how to configure and manage providers for Lighthouse AI on Prowler Cloud.
+
+<SubscriptionBanner />
+
+For a feature overview, see [Lighthouse AI on Prowler Cloud](/getting-started/products/prowler-cloud-lighthouse).
+
+## Supported Providers
+
+- **OpenAI:** GPT models, including the default GPT-5.5.
+- **Amazon Bedrock:** AWS-hosted access to Claude, Llama, Titan, and other models.
+- **OpenAI Compatible:** Any service exposing an OpenAI-compatible API endpoint, such as OpenRouter.
+
+## Model Requirements
+
+Lighthouse AI requires models that support all of the following:
+
+- **Text input:** Ability to receive text prompts.
+- **Text output:** Ability to generate text responses.
+- **Tool calling:** Ability to invoke tools to retrieve data from Prowler.
+
+Models without these capabilities are not going to work well.
+
+## Configuring Providers
+
+Navigate to **Configuration** → **Lighthouse AI** to see the available providers, each with its own connection option.
+
+To connect a provider:
+
+1. Click the desired provider.
+2. Enter the required credentials.
+3. Click **Save**. The connection is validated automatically before the provider becomes available.
+
+<img src="/images/prowler-app/lighthouse/prowler-cloud/config-page.png" alt="Lighthouse AI configuration page in Prowler Cloud" />
+
+The required information differs per provider:
+
+<Tabs>
+ <Tab title="OpenAI">
+ - **API Key:** OpenAI API key (starts with `sk-` or `sk-proj-`), created from the [OpenAI platform](https://platform.openai.com/api-keys).
+
+ Confirm the OpenAI account has sufficient credits and that the default GPT-5.5 model is not blocked in the organization settings.
+ </Tab>
+ <Tab title="Amazon Bedrock">
+ Connect using either an Amazon Bedrock API key or AWS IAM credentials.
+
+ **Amazon Bedrock API key**
+ - **Bedrock API Key:** The key generated from Amazon Bedrock.
+ - **AWS Region:** Region where Bedrock is available.
+
+ **AWS IAM Access Keys**
+ - **AWS Access Key ID** and **AWS Secret Access Key** for the IAM user.
+ - **AWS Region:** Region where Bedrock is available.
+ - The IAM user requires the `AmazonBedrockLimitedAccess` managed policy.
+ </Tab>
+ <Tab title="OpenAI Compatible">
+ Connect to any service exposing an OpenAI-compatible API endpoint that Prowler Cloud can reach over the Internet.
+
+ - **API Key:** API key from the compatible service.
+ - **Base URL:** API endpoint URL including the version (for example, `https://openrouter.ai/api/v1`).
+
+ ### Example: OpenRouter
+
+ 1. Create an account at [OpenRouter](https://openrouter.ai/).
+ 2. Generate an API key from the OpenRouter dashboard.
+ 3. Enter the API key and set the base URL to `https://openrouter.ai/api/v1`.
+ </Tab>
+</Tabs>
+
+## Model Recommendations
+
+GPT-5.5 is the default and recommended model for Lighthouse AI on Prowler Cloud. Models from Amazon Bedrock and OpenAI-compatible endpoints can also be used, but performance is not guaranteed. Ensure any selected model supports text input, text output, and tool calling.
+
+## Getting Help
+
+For issues or suggestions with Lighthouse AI on Prowler Cloud, request support at [support.prowler.com](https://support.prowler.com) or [reach out through our Slack channel](https://goto.prowler.com/slack).
diff --git a/docs/user-guide/tutorials/prowler-cloud-public-ips.mdx b/docs/user-guide/tutorials/prowler-cloud-public-ips.mdx
deleted file mode 100644
index f3b285056c..0000000000
--- a/docs/user-guide/tutorials/prowler-cloud-public-ips.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 'Prowler Cloud Public IPs'
----
-
-## Overview
-
-Prowler Cloud uses a dedicated egress IPv4 address for all outbound connections to customer infrastructure. This enables organizations to implement network-level security controls by whitelisting Prowler's IP address.
-
-## Use Cases
-
-Whitelisting Prowler's egress IP address enables:
-
-- **Credential Usage Control**: Restrict where cloud provider credentials can be used from across AWS, Azure, GCP, and other providers
-- **Kubernetes Security**: Limit inbound HTTPS traffic to clusters by allowing only Prowler's IP address
-- **Compliance Requirements**: Meet security policies requiring allowlisting of external services
-
-## Query the Egress IP Address
-
-Retrieve Prowler Cloud's current egress IP address using the following command:
-
-```bash
-dig egress.prowler.com +short
-```
-
-This command returns the IPv4 address that Prowler Cloud uses for all outbound connections to customer infrastructure.
-
-<Note>
-The egress IP address is stable, but it is recommended to periodically verify it remains current by querying `egress.prowler.com`.
-</Note>
diff --git a/docs/user-guide/tutorials/prowler-app-import-findings.mdx b/docs/user-guide/tutorials/prowler-import-findings.mdx
similarity index 96%
rename from docs/user-guide/tutorials/prowler-app-import-findings.mdx
rename to docs/user-guide/tutorials/prowler-import-findings.mdx
index 9f1002c2a9..530cd160ee 100644
--- a/docs/user-guide/tutorials/prowler-app-import-findings.mdx
+++ b/docs/user-guide/tutorials/prowler-import-findings.mdx
@@ -1,19 +1,19 @@
---
title: 'Import Findings'
+sidebarTitle: 'Import Findings'
description: 'Upload OCSF scan results to Prowler Cloud from external sources or the CLI'
---
import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
<VersionBadge version="5.19.0" />
Findings Ingestion enables uploading OCSF (Open Cybersecurity Schema Framework) scan results to Prowler Cloud. This feature supports importing findings from Prowler CLI output files that use the [Detection Finding](https://schema.ocsf.io/classes/detection_finding) class.
-<Note>
-This feature is available exclusively in **Prowler Cloud** with a paid subscription.
-</Note>
+<SubscriptionBanner />
-## OCSF Detection Finding format
+## OCSF Detection Finding Format
The ingestion API accepts `.ocsf.json` files containing a JSON array of OCSF Detection Finding records. Each finding represents a security check result from Prowler.
@@ -130,11 +130,11 @@ The ingestion API accepts `.ocsf.json` files containing a JSON array of OCSF Det
Only **Detection Finding** (`class_uid: 2004`) records are accepted. Other OCSF classes are not supported for ingestion.
</Note>
-## Required permissions
+## Required Permissions
The **Manage Ingestions** RBAC permission controls access to the ingestion endpoints. Without this permission, findings cannot be submitted via the API or `--push-to-cloud`.
-For more information about RBAC permissions, refer to the [Prowler App RBAC documentation](/user-guide/tutorials/prowler-app-rbac).
+For more information about RBAC permissions, refer to the [Prowler Cloud RBAC documentation](/user-guide/tutorials/prowler-app-rbac).
## Using the CLI
@@ -145,7 +145,7 @@ The `--push-to-cloud` flag uploads scan results directly to Prowler Cloud after
- A valid Prowler Cloud API key (see [API Keys](/user-guide/tutorials/prowler-app-api-keys))
- The `PROWLER_CLOUD_API_KEY` environment variable configured
-### Basic usage
+### Basic Usage
```bash
export PROWLER_CLOUD_API_KEY="pk_your_api_key_here"
@@ -153,7 +153,7 @@ export PROWLER_CLOUD_API_KEY="pk_your_api_key_here"
prowler aws --push-to-cloud
```
-### Combining with output formats
+### Combining with Output Formats
When using `--push-to-cloud` with custom output formats that exclude OCSF, Prowler generates a temporary OCSF file for upload:
@@ -169,7 +169,7 @@ When default output formats include OCSF, Prowler reuses the existing file. Defa
prowler aws --services accessanalyzer --push-to-cloud -o /tmp/scan-output
```
-### CLI output examples
+### CLI Output Examples
**Successful upload:**
```
@@ -228,7 +228,7 @@ curl -X POST \
https://api.prowler.com/api/v1/ingestions
```
-### Submit an ingestion batch
+### Submit an Ingestion Batch
Upload a `.ocsf.json` file containing a JSON array of OCSF Detection Finding records. See [OCSF Detection Finding format](#ocsf-detection-finding-format) for the expected structure.
@@ -266,7 +266,7 @@ curl -X POST \
}
```
-### Get ingestion status
+### Get Ingestion Status
Monitor the progress of an ingestion job.
@@ -304,7 +304,7 @@ curl -X GET \
}
```
-### List ingestion jobs
+### List Ingestion Jobs
Retrieve a list of ingestion jobs for the tenant.
@@ -332,7 +332,7 @@ curl -X GET \
"https://api.prowler.com/api/v1/ingestions?filter[status]=completed&page[size]=10"
```
-### Get ingestion errors
+### Get Ingestion Errors
Retrieve error details for a specific ingestion job.
@@ -346,7 +346,7 @@ curl -X GET \
https://api.prowler.com/api/v1/ingestions/3650fef9-8e5f-4808-a95f-74f0afae8499/errors
```
-## Ingestion status values
+## Ingestion Status Values
| Status | Description |
|--------|-------------|
@@ -355,7 +355,7 @@ curl -X GET \
| `completed` | All records processed successfully |
| `failed` | Job encountered errors during processing |
-## CI/CD integration
+## CI/CD Integration
Automate findings ingestion in CI/CD pipelines by setting the API key as a secret.
@@ -391,7 +391,7 @@ prowler_scan:
PROWLER_CLOUD_API_KEY: $PROWLER_CLOUD_API_KEY
```
-## Billing impact
+## Billing Impact
Each unique cloud account discovered in ingested OCSF findings counts as one **provider** in the Prowler Cloud subscription.
diff --git a/docs/user-guide/tutorials/prowler-scan-scheduling.mdx b/docs/user-guide/tutorials/prowler-scan-scheduling.mdx
new file mode 100644
index 0000000000..f909ed2fa0
--- /dev/null
+++ b/docs/user-guide/tutorials/prowler-scan-scheduling.mdx
@@ -0,0 +1,107 @@
+---
+title: 'Scan Scheduling'
+sidebarTitle: 'Scheduling'
+description: 'Create, edit, and monitor recurring scans in Prowler Cloud and Prowler Private Cloud.'
+---
+
+import { VersionBadge } from "/snippets/version-badge.mdx"
+import { SubscriptionBanner } from "/snippets/subscription-banner.mdx"
+
+<VersionBadge version="5.31.0" />
+
+Scan Scheduling lets Prowler run recurring scans for connected providers. Use it to keep findings, compliance results, and resource inventory up to date without launching every scan manually.
+
+<SubscriptionBanner />
+
+## Prerequisites
+
+Before creating or editing scan schedules, ensure that:
+
+* At least one provider is connected.
+* The user role includes the **Manage Scans** permission, configured through Role-Based Access Control (RBAC). See [RBAC Administrative Permissions](/user-guide/tutorials/prowler-app-rbac#rbac-administrative-permissions) for details.
+
+## Schedule Options
+
+A Prowler Cloud or Prowler Private Cloud subscription supports the following custom recurring schedule options. Prowler Local Server runs a daily scan automatically and does not expose custom cadence controls.
+
+| Schedule Option | Description | Prowler Cloud & Prowler Private Cloud | Prowler Local Server |
+|-----------------|-------------|---------------------------------------|----------------------|
+| Daily | Runs one scan every day at the selected time. | Yes | Automatic |
+| Every 48 hours | Runs one scan every 48 hours, anchored to the selected time. | Yes | — |
+| Weekly | Runs one scan every week on the selected day and time. | Yes | — |
+| Monthly | Runs one scan every month on the selected day, from day 1 to day 28. | Yes | — |
+
+The scan time is always selected on the hour (for example, 14:00); minutes cannot be set. The schedule time uses the browser timezone when the schedule is saved. Prowler displays the next scheduled scan in that timezone.
+
+## Create a Schedule From Scans
+
+To create a schedule from the **Scans** page:
+
+1. Navigate to **Scans**.
+2. Click **Launch Scan**.
+3. Select a connected provider.
+4. Select **On a schedule**.
+5. Choose the **Scan Time** and **Repeats** values.
+6. Optional: select **Launch an initial scan now for immediate findings** to run a scan immediately after saving the recurring schedule.
+7. Click **Save Schedule**.
+
+<Frame>
+ <img src="/images/prowler-app/scan-scheduling/launch-scan-schedule.png" alt="Launch A Scan modal showing On a schedule mode, weekly schedule controls, and Save Schedule button" />
+</Frame>
+
+After the schedule is saved, Prowler shows a confirmation toast with a link to the **Scheduled** tab.
+
+## Edit Schedules From Providers
+
+The **Providers** page shows each provider's current schedule in the **Scan Schedule** column. Providers without a recurring schedule show **None**.
+
+<Frame>
+ <img src="/images/prowler-app/scan-scheduling/providers-scan-schedule.png" alt="Providers table showing the Scan Schedule column with Daily and None schedule states" />
+</Frame>
+
+To edit a provider schedule:
+
+1. Navigate to **Providers**.
+2. Open the provider row actions menu.
+3. Click **Edit Scan Schedule**.
+4. Update the schedule fields.
+5. Click **Save**.
+
+<Frame>
+ <img src="/images/prowler-app/scan-scheduling/edit-scan-schedule.png" alt="Edit Scan Schedule modal showing a weekly provider schedule and Remove Scan Schedule action" />
+</Frame>
+
+To stop automatic scans for a provider, click **Remove Scan Schedule** in the edit modal. Removing a schedule stops future automatic scans; existing completed scan results remain available.
+
+## Bulk Edit Schedules
+
+Use bulk schedule editing when several providers need the same recurring cadence.
+
+To bulk edit provider schedules:
+
+1. Navigate to **Providers**.
+2. Select the provider rows that should receive the same schedule.
+3. Open the selected-row actions menu.
+4. Click **Edit Scan Schedule (N)**, where **N** is the number of selected providers.
+5. Save the schedule.
+
+For AWS Organizations and Organizational Unit rows, **Edit Scan Schedule** applies the schedule to the connected child providers in that group.
+
+<Warning>
+Bulk schedule edits apply one schedule to every selected provider. If the wrong providers are selected, Prowler applies the same cadence to unintended providers. To recover, reopen bulk edit with the correct selection or update affected provider schedules individually.
+</Warning>
+
+## Review Scheduled Scans
+
+To review upcoming scheduled scans:
+
+1. Navigate to **Scans**.
+2. Click the **Scheduled** tab.
+
+The **Scheduled** tab shows configured schedules, next scan time, and last scan time. Pending rows represent configured schedules that have not started their next scan yet.
+
+<Frame>
+ <img src="/images/prowler-app/scan-scheduling/scheduled-scans-tab.png" alt="Scans Scheduled tab showing pending scheduled scans, schedule cadence, next scan, and last scan columns" />
+</Frame>
+
+To edit a schedule from this tab, open the row actions menu and click **Edit Scan Schedule**.
diff --git a/mcp_server/.env.template b/mcp_server/.env.template
index 11b8caa724..10aabd84cf 100644
--- a/mcp_server/.env.template
+++ b/mcp_server/.env.template
@@ -1,3 +1,3 @@
-PROWLER_APP_API_KEY="pk_your_api_key_here"
+PROWLER_API_KEY="pk_your_api_key_here"
API_BASE_URL="https://api.prowler.com/api/v1"
PROWLER_MCP_TRANSPORT_MODE="stdio"
diff --git a/mcp_server/AGENTS.md b/mcp_server/AGENTS.md
index c8f77bd4b1..1d3d808e6a 100644
--- a/mcp_server/AGENTS.md
+++ b/mcp_server/AGENTS.md
@@ -2,7 +2,7 @@
> **Skills Reference**: See [`prowler-mcp`](../skills/prowler-mcp/SKILL.md)
-### Auto-invoke Skills
+## Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
@@ -25,7 +25,7 @@ The Prowler MCP Server provides AI agents access to the Prowler ecosystem throug
## CRITICAL RULES
### Tool Implementation
-- ALWAYS: Extend `BaseTool` ABC for Prowler App tools (auto-registration)
+- ALWAYS: Extend `BaseTool` ABC for Prowler tools (auto-registration)
- ALWAYS: Use `@mcp.tool()` decorator for Hub/Docs tools
- NEVER: Manually register BaseTool subclasses
- NEVER: Import tools directly in server.py
@@ -56,7 +56,7 @@ await prowler_mcp_server.import_server(docs_mcp_server, prefix="prowler_docs")
### Tool Naming
- `prowler_hub_*` - Catalog and compliance (no auth)
- `prowler_docs_*` - Documentation search (no auth)
-- `prowler_app_*` - Cloud/App management (auth required)
+- `prowler_*` - Prowler Cloud, Private Cloud & Local Server management (auth required)
---
@@ -68,7 +68,7 @@ Python 3.12+ | FastMCP 2.13.1 | httpx (async) | Pydantic | uv
## PROJECT STRUCTURE
-```
+```text
mcp_server/prowler_mcp_server/
├── server.py # Main orchestration
├── prowler_hub/server.py # Hub tools (no auth)
diff --git a/mcp_server/CHANGELOG.md b/mcp_server/CHANGELOG.md
index 4679f37581..5898f816c9 100644
--- a/mcp_server/CHANGELOG.md
+++ b/mcp_server/CHANGELOG.md
@@ -2,6 +2,32 @@
All notable changes to the **Prowler MCP Server** are documented in this file.
+<!-- changelog: release notes start -->
+
+## [0.8.0] (Prowler v5.35.0)
+
+### 🔄 Changed
+
+- Core Prowler tool namespace from the `prowler_app_*` prefix to `prowler_*` [(#12017)](https://github.com/prowler-cloud/prowler/pull/12017)
+
+---
+
+## [0.7.2] (Prowler v5.28.1)
+
+### 🐞 Fixed
+
+- Preserve authorization header in HTTP mode [(#11366)](https://github.com/prowler-cloud/prowler/pull/11366)
+
+---
+
+## [0.7.1] (Prowler v5.28.0)
+
+### 🔐 Security
+
+- `fastmcp` from 2.14.0 to 3.2.4 for GHSA-5h2m-4q8j-pqpj, GHSA-rww4-4w9c-7733, and GHSA-vv7q-7jx5-f767, which also pulls fixed `jaraco.context`, `python-multipart`, `starlette`, and drops the vulnerable `lupa`/`urllib3` transitive deps [(#11284)](https://github.com/prowler-cloud/prowler/pull/11284)
+
+---
+
## [0.7.0] (Prowler v5.27.0)
### 🚀 Added
@@ -36,6 +62,8 @@ All notable changes to the **Prowler MCP Server** are documented in this file.
- Attack Path tool to get Neo4j DB schema [(#10321)](https://github.com/prowler-cloud/prowler/pull/10321)
+---
+
## [0.4.0] (Prowler v5.19.0)
### 🚀 Added
diff --git a/mcp_server/Dockerfile b/mcp_server/Dockerfile
index d8377a1762..195bfe1eae 100644
--- a/mcp_server/Dockerfile
+++ b/mcp_server/Dockerfile
@@ -1,7 +1,7 @@
# =============================================================================
# Build stage - Install dependencies and build the application
# =============================================================================
-FROM ghcr.io/astral-sh/uv:python3.13-alpine@sha256:8f53782bb232ab0b5558f3071e86e2bbfde884e18815f2b19cc57f2d336e9ee2 AS builder
+FROM ghcr.io/astral-sh/uv:0.11.21-python3.13-alpine3.23@sha256:f09cc61ffc001f202701fdeae14dbdd50f6ca4cfcf248f41fd3234a302c8534f AS builder
WORKDIR /app
@@ -25,7 +25,7 @@ RUN --mount=type=cache,target=/root/.cache/uv \
# =============================================================================
# Final stage - Minimal runtime environment
# =============================================================================
-FROM python:3.13-alpine@sha256:bb1f2fdb1065c85468775c9d680dcd344f6442a2d1181ef7916b60a623f11d40
+FROM python:3.13.14-alpine3.23@sha256:9fdbf2e3e82628351513560b121e2ee6ce31cac212be9e070c5a5e2769fb5e76
LABEL maintainer="https://github.com/prowler-cloud"
diff --git a/mcp_server/README.md b/mcp_server/README.md
index 644e4be31c..c0e4fdb0fe 100644
--- a/mcp_server/README.md
+++ b/mcp_server/README.md
@@ -6,9 +6,9 @@
## Key Capabilities
-### Prowler Cloud and Prowler App (Self-Managed)
+### Prowler Cloud, Prowler Private Cloud & Prowler Local Server
-Full access to Prowler Cloud platform and self-managed Prowler App for:
+Full access to your Prowler data (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server) for:
- **Findings Analysis**: Query, filter, and analyze security findings across all your cloud environments
- **Finding Groups Analysis**: Triage findings grouped by check ID and drill down into affected resources
- **Provider Management**: Create, configure, and manage your configured Prowler providers (AWS, Azure, GCP, etc.)
@@ -49,7 +49,7 @@ For comprehensive guides and tutorials, see the official documentation:
Prowler MCP Server can be used in three ways:
-### 1. Prowler Cloud MCP Server (Recommended)
+### 1. Hosted Prowler MCP (Recommended)
**Use Prowler's managed MCP server at `https://mcp.prowler.com/mcp`**
@@ -83,14 +83,14 @@ npm install --save-exact mcp-remote@0.1.38
### 2. Local STDIO Mode
-**Run the server locally on your machine**
+Run the server locally on your machine:
- Runs as a subprocess of your MCP client
- Requires Python 3.12+ or Docker
### 3. Self-Hosted HTTP Mode
-**Deploy your own remote MCP server**
+Deploy your own remote MCP server:
- Full control over deployment
- Requires Python 3.12+ or Docker
@@ -126,13 +126,13 @@ For complete tool descriptions and parameters, see the [Tools Reference](https:/
### Tool Naming Convention
All tools follow a consistent naming pattern with prefixes:
-- `prowler_app_*` - Prowler Cloud and App (Self-Managed) management tools
+- `prowler_*` - Prowler Cloud, Prowler Private Cloud & Prowler Local Server management tools
- `prowler_hub_*` - Prowler Hub catalog and compliance tools
- `prowler_docs_*` - Prowler documentation search and retrieval
## Architecture
-```
+```text
prowler_mcp_server/
├── server.py # Main orchestrator (imports sub-servers with prefixes)
├── main.py # CLI entry point
@@ -146,7 +146,7 @@ prowler_mcp_server/
**Key Features:**
- **Modular Design**: Three independent sub-servers with prefixed namespacing
-- **Auto-Discovery**: Prowler App tools are automatically discovered and registered
+- **Auto-Discovery**: Prowler tools are automatically discovered and registered
- **LLM Optimization**: Response models minimize token usage by excluding empty values
- **Dual Transport**: Supports both STDIO (local) and HTTP (remote) modes
@@ -154,34 +154,37 @@ prowler_mcp_server/
The Prowler MCP Server enables powerful workflows through AI assistants:
-**Security Operations**
+### Security Operations
+
- "Show me all critical findings from my AWS production accounts"
- "Register my new AWS account in Prowler and run a scheduled scan every day"
- "List all muted findings and detect what findgings are muted by a not enough good reason in relation to their severity"
-**Security Research**
+### Security Research
+
- "Explain what the S3 bucket public access Prowler check does"
- "Find all Prowler checks related to encryption at rest"
- "What is the latest version of the CIS that Prowler is covering per provider?"
-**Documentation & Learning**
+### Documentation & Learning
+
- "How do I configure Prowler to scan my GCP organization?"
- "What authentication methods does Prowler support for Azure?"
- "How can I contribute with a new security check to Prowler?"
## Requirements
-**For Prowler Cloud MCP Server:**
-- Prowler Cloud account and API key (only for Prowler Cloud/App features)
+**For the hosted Prowler MCP:**
+- Prowler Cloud account and API key (only for Prowler features)
**For self-hosted STDIO/HTTP Mode:**
- Python 3.12+ or Docker
- Network access to:
- `https://hub.prowler.com` (for Prowler Hub)
- `https://docs.prowler.com` (for Prowler Documentation)
- - Prowler Cloud API or self-hosted Prowler App API (for Prowler Cloud/App features)
+ - Prowler Cloud API or Prowler Local Server API (for Prowler features)
-> **No Authentication Required**: Prowler Hub and Prowler Documentation features work without authentication. A Prowler API key is only required to access Prowler Cloud or Prowler App (Self-Managed) features.
+> **No Authentication Required**: Prowler Hub and Prowler Documentation features work without authentication. A Prowler API key is only required to access Prowler features (Prowler Cloud, Prowler Private Cloud, or Prowler Local Server).
## Configuring MCP Hosts
@@ -197,7 +200,7 @@ For developers looking to extend the MCP server with new tools or features:
## Related Products
- **[Prowler Hub](https://hub.prowler.com)**: Browse security checks and compliance frameworks
-- **[Prowler Cloud](https://cloud.prowler.com)**: Managed Prowler platform
+- **[Prowler Cloud](https://cloud.prowler.com)**: Fully managed Prowler in the cloud
- **[Lighthouse AI](https://docs.prowler.com/getting-started/products/prowler-lighthouse-ai)**: AI security analyst
## License
diff --git a/tests/__init__.py b/mcp_server/changelog.d/.gitkeep
similarity index 100%
rename from tests/__init__.py
rename to mcp_server/changelog.d/.gitkeep
diff --git a/mcp_server/changelog.d/README.md b/mcp_server/changelog.d/README.md
new file mode 100644
index 0000000000..0853174f30
--- /dev/null
+++ b/mcp_server/changelog.d/README.md
@@ -0,0 +1,10 @@
+# Changelog fragments
+
+Each PR adds one small file here instead of editing `CHANGELOG.md` directly, so concurrent PRs never conflict.
+
+- Filename: `<slug>.<type>.md`, e.g. `my-new-check.added.md` (slug is free-form: letters, digits, `.`, `_`, `-`)
+- `<type>` is one of: `added`, `changed`, `deprecated`, `removed`, `fixed`, `security`
+- Content: one line with the changelog entry text, without the PR link and without a trailing period (the PR link is attached automatically at release time)
+- A PR adds as many fragment files as entries it needs, freely mixing types (one file per entry); same-type entries just use different slugs
+
+Fragments are compiled into `CHANGELOG.md` when a release is prepared. Full conventions: `skills/prowler-changelog/SKILL.md`.
diff --git a/mcp_server/prowler_mcp_server/__init__.py b/mcp_server/prowler_mcp_server/__init__.py
index fe7af2dcea..1956a6ec41 100644
--- a/mcp_server/prowler_mcp_server/__init__.py
+++ b/mcp_server/prowler_mcp_server/__init__.py
@@ -5,7 +5,7 @@ This package provides MCP tools for accessing:
- Prowler Hub: All security artifacts (detections, remediations and frameworks) supported by Prowler
"""
-__version__ = "0.5.0"
+__version__ = "0.8.0"
__author__ = "Prowler Team"
__email__ = "engineering@prowler.com"
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/__init__.py b/mcp_server/prowler_mcp_server/prowler_app/models/__init__.py
index 899ab4e866..1b15e35ac9 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/__init__.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/__init__.py
@@ -1,4 +1,4 @@
-"""Pydantic models for Prowler App MCP Server."""
+"""Pydantic models for Prowler MCP Server."""
from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from prowler_mcp_server.prowler_app.models.findings import (
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/attack_paths.py b/mcp_server/prowler_mcp_server/prowler_app/models/attack_paths.py
index cfd704eeca..bbe2eb7401 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/attack_paths.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/attack_paths.py
@@ -12,9 +12,10 @@ for optimal LLM token usage.
from typing import Any, Literal
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel, ConfigDict, Field
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class AttackPathScan(MinimalSerializerMixin, BaseModel):
"""Simplified attack paths scan representation for list operations.
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/compliance.py b/mcp_server/prowler_mcp_server/prowler_app/models/compliance.py
index 4dfe5c4839..c68bd0df85 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/compliance.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/compliance.py
@@ -2,7 +2,6 @@
from typing import Any, Literal
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import (
BaseModel,
ConfigDict,
@@ -11,6 +10,8 @@ from pydantic import (
model_serializer,
)
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class ComplianceRequirementAttribute(MinimalSerializerMixin, BaseModel):
"""Requirement attributes including associated check IDs.
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/finding_groups.py b/mcp_server/prowler_mcp_server/prowler_app/models/finding_groups.py
index 9ff9822977..c2429012c3 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/finding_groups.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/finding_groups.py
@@ -6,7 +6,6 @@ from pydantic import Field
from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
-
FindingStatus = Literal["FAIL", "PASS", "MANUAL"]
FindingSeverity = Literal["critical", "high", "medium", "low", "informational"]
FindingDelta = Literal["new", "changed"]
@@ -76,9 +75,7 @@ class SimplifiedFindingGroup(MinimalSerializerMixin):
)
muted_count: int = Field(description="Total muted findings in this group", ge=0)
new_count: int = Field(description="Number of new non-muted findings", ge=0)
- changed_count: int = Field(
- description="Number of changed non-muted findings", ge=0
- )
+ changed_count: int = Field(description="Number of changed non-muted findings", ge=0)
first_seen_at: str | None = Field(
default=None, description="First time this group was detected"
)
@@ -109,18 +106,12 @@ class DetailedFindingGroup(SimplifiedFindingGroup):
new_pass_count: int = Field(description="New non-muted PASS findings", ge=0)
new_pass_muted_count: int = Field(description="New muted PASS findings", ge=0)
new_manual_count: int = Field(description="New non-muted MANUAL findings", ge=0)
- new_manual_muted_count: int = Field(
- description="New muted MANUAL findings", ge=0
- )
- changed_fail_count: int = Field(
- description="Changed non-muted FAIL findings", ge=0
- )
+ new_manual_muted_count: int = Field(description="New muted MANUAL findings", ge=0)
+ changed_fail_count: int = Field(description="Changed non-muted FAIL findings", ge=0)
changed_fail_muted_count: int = Field(
description="Changed muted FAIL findings", ge=0
)
- changed_pass_count: int = Field(
- description="Changed non-muted PASS findings", ge=0
- )
+ changed_pass_count: int = Field(description="Changed non-muted PASS findings", ge=0)
changed_pass_muted_count: int = Field(
description="Changed muted PASS findings", ge=0
)
@@ -237,7 +228,7 @@ class FindingGroupResource(MinimalSerializerMixin):
resource: FindingGroupResourceInfo = Field(description="Affected resource")
provider: FindingGroupProviderInfo = Field(description="Affected provider")
finding_id: str = Field(
- description="Finding UUID to use with prowler_app_get_finding_details"
+ description="Finding UUID to use with prowler_get_finding_details"
)
status: FindingStatus = Field(description="Finding status for this resource")
severity: FindingSeverity = Field(description="Finding severity")
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/findings.py b/mcp_server/prowler_mcp_server/prowler_app/models/findings.py
index 5ef8702ce4..1373e36294 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/findings.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/findings.py
@@ -2,9 +2,10 @@
from typing import Literal
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel, ConfigDict, Field
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class CheckRemediation(MinimalSerializerMixin, BaseModel):
"""Remediation information for a security check."""
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/muting.py b/mcp_server/prowler_mcp_server/prowler_app/models/muting.py
index 779acdde5e..e50a150d20 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/muting.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/muting.py
@@ -2,9 +2,10 @@
from typing import Any
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel, ConfigDict, Field
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class MutelistResponse(MinimalSerializerMixin, BaseModel):
"""Simplified mutelist response with Prowler configuration.
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/providers.py b/mcp_server/prowler_mcp_server/prowler_app/models/providers.py
index 07f3be1d37..af9509a963 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/providers.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/providers.py
@@ -2,9 +2,10 @@
from typing import Any, Literal
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class SimplifiedProvider(MinimalSerializerMixin, BaseModel):
"""Simplified provider for list/search operations."""
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/resources.py b/mcp_server/prowler_mcp_server/prowler_app/models/resources.py
index 823134794f..13cb1ed4dd 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/resources.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/resources.py
@@ -1,8 +1,9 @@
"""Pydantic models for simplified resources responses."""
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class SimplifiedResource(MinimalSerializerMixin, BaseModel):
"""Simplified resource with only LLM-relevant information for list operations."""
diff --git a/mcp_server/prowler_mcp_server/prowler_app/models/scans.py b/mcp_server/prowler_mcp_server/prowler_app/models/scans.py
index 696ac7837d..f8eef988ce 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/models/scans.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/models/scans.py
@@ -11,9 +11,10 @@ for optimal LLM token usage.
from typing import Any, Literal
-from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
from pydantic import BaseModel, ConfigDict, Field
+from prowler_mcp_server.prowler_app.models.base import MinimalSerializerMixin
+
class SimplifiedScan(MinimalSerializerMixin, BaseModel):
"""Simplified scan representation for list operations.
diff --git a/mcp_server/prowler_mcp_server/prowler_app/server.py b/mcp_server/prowler_mcp_server/prowler_app/server.py
index 39b22d095c..e8e854144f 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/server.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/server.py
@@ -1,4 +1,5 @@
from fastmcp import FastMCP
+
from prowler_mcp_server.prowler_app.utils.tool_loader import load_all_tools
# Initialize MCP server
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/__init__.py b/mcp_server/prowler_mcp_server/prowler_app/tools/__init__.py
index 4d740b6efe..8b5be76076 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/__init__.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/__init__.py
@@ -1,4 +1,4 @@
-"""Domain-specific tools for Prowler App MCP Server.
+"""Domain-specific tools for Prowler MCP Server.
Each module in this package contains a BaseTool subclass that registers
and implements tools for a specific domain (findings, providers, scans, etc.).
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/attack_paths.py b/mcp_server/prowler_mcp_server/prowler_app/tools/attack_paths.py
index ff9b8045a4..5bd66760fa 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/attack_paths.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/attack_paths.py
@@ -1,4 +1,4 @@
-"""Attack Paths tools for Prowler App MCP Server.
+"""Attack Paths tools for Prowler MCP Server.
This module provides tools for analyzing Attack Paths data from Neo4j graph database.
Attack Paths help identify security risks by tracing potential attack vectors
@@ -7,6 +7,8 @@ through cloud infrastructure relationships.
from typing import Any, Literal
+from pydantic import Field
+
from prowler_mcp_server.prowler_app.models.attack_paths import (
AttackPathCartographySchema,
AttackPathQuery,
@@ -14,23 +16,22 @@ from prowler_mcp_server.prowler_app.models.attack_paths import (
AttackPathScansListResponse,
)
from prowler_mcp_server.prowler_app.tools.base import BaseTool
-from pydantic import Field
class AttackPathsTools(BaseTool):
"""Tools for Attack Paths analysis.
Provides tools for:
- - prowler_app_list_attack_paths_scans: Find completed scans ready for analysis
- - prowler_app_list_attack_paths_queries: Discover available queries for a scan
- - prowler_app_run_attack_paths_query: Execute query and analyze attack paths
+ - prowler_list_attack_paths_scans: Find completed scans ready for analysis
+ - prowler_list_attack_paths_queries: Discover available queries for a scan
+ - prowler_run_attack_paths_query: Execute query and analyze attack paths
"""
async def list_attack_paths_scans(
self,
provider_id: list[str] = Field(
default=[],
- description="Filter by Prowler's internal UUID(s) (v4) for specific provider(s). Use `prowler_app_search_providers` tool to find provider IDs",
+ description="Filter by Prowler's internal UUID(s) (v4) for specific provider(s). Use `prowler_search_providers` tool to find provider IDs",
),
provider_type: list[str] = Field(
default=[],
@@ -72,8 +73,8 @@ class AttackPathsTools(BaseTool):
Workflow:
1. Use this tool to find completed attack paths scans
- 2. Use prowler_app_list_attack_paths_queries to see available queries for a scan
- 3. Use prowler_app_run_attack_paths_query to execute analysis
+ 2. Use prowler_list_attack_paths_queries to see available queries for a scan
+ 3. Use prowler_run_attack_paths_query to execute analysis
"""
try:
# Validate pagination
@@ -112,7 +113,7 @@ class AttackPathsTools(BaseTool):
async def list_attack_paths_queries(
self,
scan_id: str = Field(
- description="UUID of a COMPLETED attack paths scan. Use `prowler_app_list_attack_paths_scans` with state=['completed'] to find scan IDs"
+ description="UUID of a COMPLETED attack paths scan. Use `prowler_list_attack_paths_scans` with state=['completed'] to find scan IDs"
),
) -> list[dict[str, Any]]:
"""Discover available Attack Paths queries for a completed scan.
@@ -132,9 +133,9 @@ class AttackPathsTools(BaseTool):
- aws-ec2-instances-internet-exposed: Find internet-exposed EC2 instances
Workflow:
- 1. Use prowler_app_list_attack_paths_scans to find a completed scan
+ 1. Use prowler_list_attack_paths_scans to find a completed scan
2. Use this tool to discover available queries
- 3. Use prowler_app_run_attack_paths_query with query_id and any required parameters
+ 3. Use prowler_run_attack_paths_query with query_id and any required parameters
"""
try:
api_response = await self.api_client.get(
@@ -157,7 +158,7 @@ class AttackPathsTools(BaseTool):
description="UUID of a COMPLETED attack paths scan. The scan must be in 'completed' state"
),
query_id: str = Field(
- description="Query ID to execute (e.g., 'aws-internet-exposed-ec2-sensitive-s3-access'). Use `prowler_app_list_attack_paths_queries` to discover available queries"
+ description="Query ID to execute (e.g., 'aws-internet-exposed-ec2-sensitive-s3-access'). Use `prowler_list_attack_paths_queries` to discover available queries"
),
parameters: dict[str, str] = Field(
default_factory=dict,
@@ -193,7 +194,7 @@ class AttackPathsTools(BaseTool):
Workflow:
1. Ensure scan is completed
- 2. List available queries (use prowler_app_list_attack_paths_queries)
+ 2. List available queries (use prowler_list_attack_paths_queries)
3. Execute this tool with appropriate parameters
4. Analyze the returned graph for security insights
"""
@@ -230,7 +231,7 @@ class AttackPathsTools(BaseTool):
async def get_attack_paths_cartography_schema(
self,
scan_id: str = Field(
- description="UUID of a COMPLETED attack paths scan. Use `prowler_app_list_attack_paths_scans` with state=['completed'] to find scan IDs"
+ description="UUID of a COMPLETED attack paths scan. Use `prowler_list_attack_paths_scans` with state=['completed'] to find scan IDs"
),
) -> dict[str, Any]:
"""Retrieve the Cartography graph schema for a completed attack paths scan.
@@ -252,10 +253,10 @@ class AttackPathsTools(BaseTool):
- schema_content: Full Cartography schema markdown with node/relationship definitions
Workflow:
- 1. Use prowler_app_list_attack_paths_scans to find a completed scan
+ 1. Use prowler_list_attack_paths_scans to find a completed scan
2. Use this tool to get the schema for the scan's provider
3. Use the schema to craft custom openCypher queries
- 4. Execute queries with prowler_app_run_attack_paths_query
+ 4. Execute queries with prowler_run_attack_paths_query
"""
try:
api_response = await self.api_client.get(
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/compliance.py b/mcp_server/prowler_mcp_server/prowler_app/tools/compliance.py
index 81f16a83e9..33cdd22a69 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/compliance.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/compliance.py
@@ -1,4 +1,4 @@
-"""Compliance framework tools for Prowler App MCP Server.
+"""Compliance framework tools for Prowler MCP Server.
This module provides tools for viewing compliance status and requirement details
across all cloud providers.
@@ -6,13 +6,14 @@ across all cloud providers.
from typing import Any
+from pydantic import Field
+
from prowler_mcp_server.prowler_app.models.compliance import (
ComplianceFrameworksListResponse,
ComplianceRequirementAttributesListResponse,
ComplianceRequirementsListResponse,
)
from prowler_mcp_server.prowler_app.tools.base import BaseTool
-from pydantic import Field
class ComplianceTools(BaseTool):
@@ -49,7 +50,7 @@ class ComplianceTools(BaseTool):
if not scans_data:
raise ValueError(
f"No completed scans found for provider {provider_id}. "
- "Run a scan first using prowler_app_trigger_scan."
+ "Run a scan first using prowler_trigger_scan."
)
scan_id = scans_data[0]["id"]
@@ -59,11 +60,11 @@ class ComplianceTools(BaseTool):
self,
scan_id: str | None = Field(
default=None,
- description="UUID of a specific scan to get compliance data for. Required if provider_id is not specified. Use `prowler_app_list_scans` to find scan IDs.",
+ description="UUID of a specific scan to get compliance data for. Required if provider_id is not specified. Use `prowler_list_scans` to find scan IDs.",
),
provider_id: str | None = Field(
default=None,
- description="Prowler's internal UUID (v4) for a specific provider. If provided without scan_id, the tool will automatically find the latest completed scan for this provider. Use `prowler_app_search_providers` tool to find provider IDs.",
+ description="Prowler's internal UUID (v4) for a specific provider. If provided without scan_id, the tool will automatically find the latest completed scan for this provider. Use `prowler_search_providers` tool to find provider IDs.",
),
) -> dict[str, Any]:
"""Get high-level compliance overview across all frameworks for a specific scan.
@@ -89,11 +90,11 @@ class ComplianceTools(BaseTool):
Workflow:
1. Use this tool to get an overview of all compliance frameworks
- 2. Use prowler_app_get_compliance_framework_state_details with a specific compliance_id to see which requirements failed
+ 2. Use prowler_get_compliance_framework_state_details with a specific compliance_id to see which requirements failed
"""
if not scan_id and not provider_id:
return {
- "error": "Either scan_id or provider_id must be provided. Use prowler_app_search_providers to find provider IDs or prowler_app_list_scans to find scan IDs."
+ "error": "Either scan_id or provider_id must be provided. Use prowler_search_providers to find provider IDs or prowler_list_scans to find scan IDs."
}
elif scan_id and provider_id:
return {
@@ -253,7 +254,7 @@ class ComplianceTools(BaseTool):
async def get_compliance_framework_state_details(
self,
compliance_id: str = Field(
- description="Compliance framework ID to get details for (e.g., 'cis_1.5_aws', 'pci_dss_v4.0_aws'). You can get compliance IDs from prowler_app_get_compliance_overview or consulting Prowler Hub/Prowler Documentation that you can also find in form of tools in this MCP Server",
+ description="Compliance framework ID to get details for (e.g., 'cis_1.5_aws', 'pci_dss_v4.0_aws'). You can get compliance IDs from prowler_get_compliance_overview or consulting Prowler Hub/Prowler Documentation that you can also find in form of tools in this MCP Server",
),
scan_id: str | None = Field(
default=None,
@@ -261,14 +262,14 @@ class ComplianceTools(BaseTool):
),
provider_id: str | None = Field(
default=None,
- description="Prowler's internal UUID (v4) for a specific provider. If provided without scan_id, the tool will automatically find the latest completed scan for this provider. Use `prowler_app_search_providers` tool to find provider IDs.",
+ description="Prowler's internal UUID (v4) for a specific provider. If provided without scan_id, the tool will automatically find the latest completed scan for this provider. Use `prowler_search_providers` tool to find provider IDs.",
),
) -> dict[str, Any]:
"""Get detailed requirement-level breakdown for a specific compliance framework.
IMPORTANT: This tool returns DETAILED requirement information for a single compliance framework,
focusing on FAILED requirements and their associated FAILED finding IDs.
- Use this after prowler_app_get_compliance_overview to drill down into specific frameworks.
+ Use this after prowler_get_compliance_overview to drill down into specific frameworks.
The markdown report includes:
@@ -279,7 +280,7 @@ class ComplianceTools(BaseTool):
2. Failed Requirements Breakdown:
- Each failed requirement's ID and description
- Associated failed finding IDs for each failed requirement
- - Use prowler_app_get_finding_details with these finding IDs for more details and remediation guidance
+ - Use prowler_get_finding_details with these finding IDs for more details and remediation guidance
Default behavior:
- Requires either scan_id OR provider_id
@@ -288,14 +289,14 @@ class ComplianceTools(BaseTool):
- Only shows failed requirements with their associated failed finding IDs
Workflow:
- 1. Use prowler_app_get_compliance_overview to identify frameworks with failures
+ 1. Use prowler_get_compliance_overview to identify frameworks with failures
2. Use this tool with the compliance_id to see failed requirements and their finding IDs
- 3. Use prowler_app_get_finding_details with the finding IDs to get remediation guidance
+ 3. Use prowler_get_finding_details with the finding IDs to get remediation guidance
"""
# Validate that either scan_id or provider_id is provided
if not scan_id and not provider_id:
return {
- "error": "Either scan_id or provider_id must be provided. Use prowler_app_search_providers to find provider IDs or prowler_app_list_scans to find scan IDs."
+ "error": "Either scan_id or provider_id must be provided. Use prowler_search_providers to find provider IDs or prowler_list_scans to find scan IDs."
}
# Resolve provider_id to latest scan_id if needed
@@ -394,7 +395,7 @@ class ComplianceTools(BaseTool):
report_lines.append("**Failed Finding IDs**: None found")
report_lines.append("")
report_lines.append(
- "*Use `prowler_app_get_finding_details` with these finding IDs to get remediation guidance.*"
+ "*Use `prowler_get_finding_details` with these finding IDs to get remediation guidance.*"
)
report_lines.append("")
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/finding_groups.py b/mcp_server/prowler_mcp_server/prowler_app/tools/finding_groups.py
index 363e45d970..05adf8db2b 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/finding_groups.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/finding_groups.py
@@ -1,4 +1,4 @@
-"""Finding Groups tools for Prowler App MCP Server.
+"""Finding Groups tools for Prowler MCP Server.
This module provides read-only tools for finding group triage and drill-downs.
"""
@@ -15,7 +15,6 @@ from prowler_mcp_server.prowler_app.models.finding_groups import (
)
from prowler_mcp_server.prowler_app.tools.base import BaseTool
-
StatusFilter = Literal["FAIL", "PASS", "MANUAL"]
SeverityFilter = Literal["critical", "high", "medium", "low", "informational"]
DeltaFilter = Literal["new", "changed"]
@@ -234,8 +233,8 @@ class FindingGroupsTools(BaseTool):
`date_to`, this uses `/finding-groups` with a maximum 2-day date window.
Use this tool to find noisy or high-impact checks, then call
- prowler_app_get_finding_group_details for complete counters or
- prowler_app_list_finding_group_resources to drill into affected resources.
+ prowler_get_finding_group_details for complete counters or
+ prowler_list_finding_group_resources to drill into affected resources.
"""
try:
self.api_client.validate_page_size(page_size)
@@ -424,7 +423,7 @@ class FindingGroupsTools(BaseTool):
Default behavior returns FAIL, unmuted resources so the result is
actionable. Set `include_muted=True` to include accepted/suppressed
resources too. Each row includes nested resource and provider data plus
- `finding_id`. Use `prowler_app_get_finding_details(finding_id)` to
+ `finding_id`. Use `prowler_get_finding_details(finding_id)` to
retrieve complete remediation guidance for a specific resource finding.
"""
try:
@@ -464,9 +463,7 @@ class FindingGroupsTools(BaseTool):
clean_params = self.api_client.build_filter_params(params)
api_response = await self.api_client.get(endpoint, params=clean_params)
- response = FindingGroupResourcesListResponse.from_api_response(
- api_response
- )
+ response = FindingGroupResourcesListResponse.from_api_response(api_response)
return response.model_dump()
except Exception as e:
self.logger.error(f"Error listing finding group resources: {e}")
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/findings.py b/mcp_server/prowler_mcp_server/prowler_app/tools/findings.py
index ec492c6a43..b556101cab 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/findings.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/findings.py
@@ -1,4 +1,4 @@
-"""Security Findings tools for Prowler App MCP Server.
+"""Security Findings tools for Prowler MCP Server.
This module provides tools for searching, viewing, and analyzing security findings
across all cloud providers.
@@ -92,7 +92,7 @@ class FindingsTools(BaseTool):
"""Search and filter security findings across all cloud providers with rich filtering capabilities.
IMPORTANT: This tool returns LIGHTWEIGHT findings. Use this for fast searching and filtering across many findings.
- For complete details use prowler_app_get_finding_details on specific findings.
+ For complete details use prowler_get_finding_details on specific findings.
Default behavior:
- Returns latest findings from most recent scans (no date parameters needed)
@@ -111,7 +111,7 @@ class FindingsTools(BaseTool):
Workflow:
1. Use this tool to search and filter findings by severity, status, provider, service, region, etc.
- 2. Use prowler_app_get_finding_details with the finding 'id' to get complete information about the finding
+ 2. Use prowler_get_finding_details with the finding 'id' to get complete information about the finding
"""
# Validate page_size parameter
self.api_client.validate_page_size(page_size)
@@ -187,9 +187,9 @@ class FindingsTools(BaseTool):
"""Retrieve comprehensive details about a specific security finding by its ID.
IMPORTANT: This tool returns COMPLETE finding details.
- Use this after finding a specific finding via prowler_app_search_security_findings
+ Use this after finding a specific finding via prowler_search_security_findings
- This tool provides ALL information that prowler_app_search_security_findings returns PLUS:
+ This tool provides ALL information that prowler_search_security_findings returns PLUS:
1. Check Metadata (information about the check script that generated the finding):
- title: Human-readable phrase used to summarize the check
@@ -217,7 +217,7 @@ class FindingsTools(BaseTool):
- resource_ids: List of UUIDs for cloud resources associated with this finding
Workflow:
- 1. Use prowler_app_search_security_findings to browse and filter findings
+ 1. Use prowler_search_security_findings to browse and filter findings
2. Use this tool with the finding 'id' to get remediation guidance and complete context
"""
params = {
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/muting.py b/mcp_server/prowler_mcp_server/prowler_app/tools/muting.py
index 639f1ec3b7..37e1504165 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/muting.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/muting.py
@@ -1,4 +1,4 @@
-"""Muting tools for Prowler App MCP Server.
+"""Muting tools for Prowler MCP Server.
This module provides tools for managing finding muting in Prowler, including:
- Mutelist management (pattern-based bulk muting)
@@ -43,7 +43,7 @@ class MutingTools(BaseTool):
Workflow:
1. Use this tool to check if a mutelist is configured
2. Examine current muting patterns before making updates
- 3. Use prowler_app_set_mutelist to create or update the configuration
+ 3. Use prowler_set_mutelist to create or update the configuration
"""
self.logger.info("Retrieving mutelist configuration...")
@@ -61,7 +61,7 @@ class MutingTools(BaseTool):
if len(data) == 0:
return {
"error": "No mutelist found",
- "message": "No mutelist configuration exists for this tenant. Use prowler_app_set_mutelist to create one.",
+ "message": "No mutelist configuration exists for this tenant. Use prowler_set_mutelist to create one.",
}
# Return the first (and only) mutelist
@@ -116,10 +116,10 @@ Structure:
- Exceptions: Accounts, Regions, Resources to exclude from muting
Workflow:
- 1. Use prowler_app_get_mutelist to check existing configuration
+ 1. Use prowler_get_mutelist to check existing configuration
2. Build configuration object following Prowler mutelist format
3. Use this tool to create or update the mutelist
- 4. Verify with prowler_app_get_mutelist
+ 4. Verify with prowler_get_mutelist
"""
self.logger.info("Setting mutelist configuration...")
@@ -171,12 +171,12 @@ Structure:
"""Remove the mutelist configuration from the tenant.
WARNING: This is a destructive operation that cannot be undone.
- - The mutelist will need to be re-created with prowler_app_set_mutelist
+ - The mutelist will need to be re-created with prowler_set_mutelist
- New findings from future scans will NOT be muted by the deleted mutelist
- Previously muted findings remain muted (deletion doesn't un-mute them)
Workflow:
- 1. Use prowler_app_get_mutelist to confirm what will be deleted
+ 1. Use prowler_get_mutelist to confirm what will be deleted
2. Use this tool to permanently remove the mutelist
3. New scans will no longer apply mutelist-based muting
"""
@@ -229,7 +229,7 @@ Structure:
"""Search and filter mute rules with pagination support.
IMPORTANT: This tool returns LIGHTWEIGHT mute rules without the full list of finding UIDs.
- Use prowler_app_get_mute_rule to get complete details including all finding UIDs and creator information.
+ Use prowler_get_mute_rule to get complete details including all finding UIDs and creator information.
Default behavior:
- Returns all mute rules (both enabled and disabled)
@@ -237,15 +237,15 @@ Structure:
- Includes basic rule information without full finding UID lists
Each mute rule includes:
- - Core identification: id (UUID for prowler_app_get_mute_rule), name
+ - Core identification: id (UUID for prowler_get_mute_rule), name
- Contextual information: reason, enabled status
- State tracking: finding_count (number of findings currently muted)
- Temporal data: inserted_at, updated_at timestamps
Workflow:
1. Use this tool to search and filter mute rules by name, enabled status, or keywords
- 2. Use prowler_app_get_mute_rule with the mute rule 'id' to get complete details including all finding UIDs
- 3. Use prowler_app_update_mute_rule or prowler_app_delete_mute_rule to modify rules
+ 2. Use prowler_get_mute_rule with the mute rule 'id' to get complete details including all finding UIDs
+ 3. Use prowler_update_mute_rule or prowler_delete_mute_rule to modify rules
"""
self.logger.info("Listing mute rules...")
self.api_client.validate_page_size(page_size)
@@ -289,17 +289,17 @@ Structure:
"""Retrieve comprehensive details about a specific mute rule by its ID.
IMPORTANT: This tool returns COMPLETE mute rule details including the full list of finding UIDs.
- Use this after finding a rule via prowler_app_list_mute_rules.
+ Use this after finding a rule via prowler_list_mute_rules.
- This tool provides ALL information that prowler_app_list_mute_rules returns PLUS:
+ This tool provides ALL information that prowler_list_mute_rules returns PLUS:
- finding_uids: Complete list of finding UIDs that are muted by this rule
- user_creator_id: UUID of the user who created the rule (audit trail)
Workflow:
- 1. Use prowler_app_list_mute_rules to find rules by name or filter criteria
+ 1. Use prowler_list_mute_rules to find rules by name or filter criteria
2. Use this tool with the rule 'id' to get complete details
3. Examine finding_uids list to understand which findings are muted
- 4. Use prowler_app_update_mute_rule or prowler_app_delete_mute_rule to modify if needed
+ 4. Use prowler_update_mute_rule or prowler_delete_mute_rule to modify if needed
"""
self.logger.info(f"Retrieving mute rule {rule_id}...")
@@ -323,7 +323,7 @@ Structure:
description="Reason for muting these findings. Document why this security issue is acceptable or intentional (e.g., 'Development environment with controlled access', 'Legacy application requires IMDSv1')."
),
finding_ids: list[str] = Field(
- description="List of finding IDs (UUIDs) to mute. Get these from the prowler_app_search_security_findings tool. Must provide at least 1 finding ID."
+ description="List of finding IDs (UUIDs) to mute. Get these from the prowler_search_security_findings tool. Must provide at least 1 finding ID."
),
) -> dict[str, Any]:
"""Create a new mute rule to mute specific findings with documentation and audit trail.
@@ -337,15 +337,15 @@ Structure:
- Records creator for audit trail
The mute rule includes:
- - Core identification: id (UUID for prowler_app_get_mute_rule), name, reason
+ - Core identification: id (UUID for prowler_get_mute_rule), name, reason
- Configuration: enabled status, finding_uids list
- Audit trail: user_creator_id (UUID of the Prowler user from the tenant that created the rule), timestamps when the rule was created and last modified
Workflow:
- 1. Use prowler_app_search_security_findings to identify findings to mute
+ 1. Use prowler_search_security_findings to identify findings to mute
2. Use this tool with finding IDs, descriptive name, and documented reason
- 3. Verify with prowler_app_get_mute_rule to confirm rule creation
- 4. Check findings are muted with prowler_app_search_security_findings (filter by muted=true)
+ 3. Verify with prowler_get_mute_rule to confirm rule creation
+ 4. Check findings are muted with prowler_search_security_findings (filter by muted=true)
"""
self.logger.info(f"Creating mute rule '{name}'...")
@@ -399,9 +399,9 @@ Structure:
- enabled: Toggle rule active status (doesn't affect already-muted findings)
Workflow:
- 1. Use prowler_app_get_mute_rule to see current rule state
+ 1. Use prowler_get_mute_rule to see current rule state
2. Use this tool to update name, reason, or enabled status
- 3. Verify changes with prowler_app_get_mute_rule
+ 3. Verify changes with prowler_get_mute_rule
"""
self.logger.info(f"Updating mute rule {rule_id}...")
@@ -451,9 +451,9 @@ Structure:
- Cannot be undone - rule must be recreated to restore
Workflow:
- 1. Use prowler_app_get_mute_rule to review what will be deleted
+ 1. Use prowler_get_mute_rule to review what will be deleted
2. Use this tool to permanently remove the rule
- 3. Verify deletion with prowler_app_list_mute_rules (rule should no longer appear)
+ 3. Verify deletion with prowler_list_mute_rules (rule should no longer appear)
"""
self.logger.info(f"Deleting mute rule {rule_id}...")
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/providers.py b/mcp_server/prowler_mcp_server/prowler_app/tools/providers.py
index b22d57d7b9..3ba417d677 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/providers.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/providers.py
@@ -1,4 +1,4 @@
-"""Provider Management tools for Prowler App MCP Server.
+"""Provider Management tools for Prowler MCP Server.
This module provides tools for managing provider connections,
including searching, connecting, and deleting providers.
@@ -19,9 +19,9 @@ class ProvidersTools(BaseTool):
"""Tools for provider management operations
Provides tools for:
- - prowler_app_search_providers: Search and view configured providers with their connection status
- - prowler_app_connect_provider: Connect or register a provider for security scanning in Prowler
- - prowler_app_delete_provider: Permanently remove a provider from Prowler
+ - prowler_search_providers: Search and view configured providers with their connection status
+ - prowler_connect_provider: Connect or register a provider for security scanning in Prowler
+ - prowler_delete_provider: Permanently remove a provider from Prowler
"""
async def search_providers(
@@ -145,7 +145,7 @@ class ProvidersTools(BaseTool):
) -> dict[str, Any]:
"""Register a provider to be scanned with Prowler.
- This tool will register a provider in Prowler App, even if the UID is wrong.
+ This tool will register a provider in Prowler, even if the UID is wrong.
If the provider is already registered, it will be updated with the new provided alias or credentials if provided.
If credentials are provided, they will be added to the indicated provider, if the provider does not exist, it will be created and the credentials will be added to it.
If the connection test is successful, the provider will be connected.
@@ -292,13 +292,13 @@ class ProvidersTools(BaseTool):
async def delete_provider(
self,
provider_id: str = Field(
- description="Prowler's internal UUID (v4) for the provider to permanently remove, generated when the provider was registered in the system. Use `prowler_app_search_providers` tool to find the provider_id if you only know the alias or the provider's own identifier (provider_uid)"
+ description="Prowler's internal UUID (v4) for the provider to permanently remove, generated when the provider was registered in the system. Use `prowler_search_providers` tool to find the provider_id if you only know the alias or the provider's own identifier (provider_uid)"
),
) -> dict[str, Any]:
"""Permanently remove a registered provider from Prowler.
WARNING: This is a destructive operation that cannot be undone. The provider will need to be
- re-added with prowler_app_connect_provider if you want to scan it again.
+ re-added with prowler_connect_provider if you want to scan it again.
The tool always returns the deletion status and message.
"""
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/resources.py b/mcp_server/prowler_mcp_server/prowler_app/tools/resources.py
index 042232e6a5..88fcca25ae 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/resources.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/resources.py
@@ -1,4 +1,4 @@
-"""Cloud Resources tools for Prowler App MCP Server.
+"""Cloud Resources tools for Prowler MCP Server.
This module provides tools for searching, viewing, and analyzing cloud resources
across all providers.
@@ -6,6 +6,8 @@ across all providers.
from typing import Any
+from pydantic import Field
+
from prowler_mcp_server.prowler_app.models.resources import (
DetailedResource,
ResourceEventsResponse,
@@ -13,7 +15,6 @@ from prowler_mcp_server.prowler_app.models.resources import (
ResourcesMetadataResponse,
)
from prowler_mcp_server.prowler_app.tools.base import BaseTool
-from pydantic import Field
class ResourcesTools(BaseTool):
@@ -85,7 +86,7 @@ class ResourcesTools(BaseTool):
IMPORTANT: This tool returns LIGHTWEIGHT resource information. Use this for fast searching
and filtering across many resources. For complete configuration details, metadata, and finding
- relationships, use prowler_app_get_resource on specific resources of interest.
+ relationships, use prowler_get_resource on specific resources of interest.
This is the primary tool for browsing resources with rich filtering capabilities.
Returns current state by default (latest scan per provider). Specify dates to query
@@ -101,16 +102,16 @@ class ResourcesTools(BaseTool):
- With dates: queries historical resource state (2-day maximum range between date_from and date_to)
Each resource includes:
- - Core identification: id (UUID for prowler_app_get_resource), uid, name
+ - Core identification: id (UUID for prowler_get_resource), uid, name
- Location context: region, service, type
- Security context: failed_findings_count (number of active security issues)
- Tags: tags associated with the resource
Useful Workflow:
1. Use this tool to search and filter resources by provider, region, service, tags, etc.
- 2. Use prowler_app_get_resource with the resource 'id' to get complete configuration and metadata
- 3. Use prowler_app_search_security_findings to find security issues for specific resources
- 4. Use prowler_app_get_finding_details to get details about the security issues for specific resources
+ 2. Use prowler_get_resource with the resource 'id' to get complete configuration and metadata
+ 3. Use prowler_search_security_findings to find security issues for specific resources
+ 4. Use prowler_get_finding_details to get details about the security issues for specific resources
"""
# Validate page_size parameter
self.api_client.validate_page_size(page_size)
@@ -176,15 +177,15 @@ class ResourcesTools(BaseTool):
async def get_resource(
self,
resource_id: str = Field(
- description="Prowler's internal UUID (v4) for the resource to retrieve, generated when the resource was discovered in the system. Use `prowler_app_list_resources` tool to find the right ID"
+ description="Prowler's internal UUID (v4) for the resource to retrieve, generated when the resource was discovered in the system. Use `prowler_list_resources` tool to find the right ID"
),
) -> dict[str, Any]:
"""Retrieve comprehensive details about a specific resource by its ID.
IMPORTANT: This tool provides COMPLETE resource details with all available information.
- Use this after finding a specific resource via prowler_app_list_resources.
+ Use this after finding a specific resource via prowler_list_resources.
- This tool provides ALL information that prowler_app_list_resources returns PLUS:
+ This tool provides ALL information that prowler_list_resources returns PLUS:
1. Configuration Details:
- metadata: Provider-specific configuration (tags, policies, encryption settings, network rules)
@@ -196,12 +197,12 @@ class ResourcesTools(BaseTool):
3. Security Relationships:
- finding_ids: Prowler's internal UUIDs (v4) of all security findings associated with this resource
- - Use prowler_app_get_finding_details on these IDs to get remediation guidance
+ - Use prowler_get_finding_details on these IDs to get remediation guidance
Useful Workflow:
- 1. Use prowler_app_list_resources to browse and filter across many resources
+ 1. Use prowler_list_resources to browse and filter across many resources
2. Use this tool to drill down into specific resources of interest
- 3. Use prowler_app_get_finding_details to get details about the security issues for specific resources
+ 3. Use prowler_get_finding_details to get details about the security issues for specific resources
"""
params = {}
@@ -347,7 +348,7 @@ class ResourcesTools(BaseTool):
async def get_resource_events(
self,
resource_id: str = Field(
- description="Prowler's internal UUID (v4) for the resource. Use `prowler_app_list_resources` to find the right ID, or get it from a finding's resource relationship via `prowler_app_get_finding_details`."
+ description="Prowler's internal UUID (v4) for the resource. Use `prowler_list_resources` to find the right ID, or get it from a finding's resource relationship via `prowler_get_finding_details`."
),
lookback_days: int = Field(
default=90,
@@ -385,8 +386,8 @@ class ResourcesTools(BaseTool):
- Identifying unauthorized or unexpected modifications
Workflows:
- 1. Resource browsing: prowler_app_list_resources → find resource → this tool for event history
- 2. Incident investigation: prowler_app_get_finding_details → get resource ID from finding → this tool to identify who caused the issue, what they changed, and when
+ 1. Resource browsing: prowler_list_resources → find resource → this tool for event history
+ 2. Incident investigation: prowler_get_finding_details → get resource ID from finding → this tool to identify who caused the issue, what they changed, and when
"""
params = {
"lookback_days": lookback_days,
diff --git a/mcp_server/prowler_mcp_server/prowler_app/tools/scans.py b/mcp_server/prowler_mcp_server/prowler_app/tools/scans.py
index 1df636ffc0..21d1431b71 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/tools/scans.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/tools/scans.py
@@ -1,4 +1,4 @@
-"""Security Scans tools for Prowler App MCP Server.
+"""Security Scans tools for Prowler MCP Server.
This module provides tools for managing and monitoring Prowler security scans.
"""
@@ -20,18 +20,18 @@ class ScansTools(BaseTool):
"""Tools for security scan operations.
Provides tools for:
- - prowler_app_list_scans: Search and filter scans with rich filtering capabilities
- - prowler_app_get_scan: Get comprehensive details about a specific scan
- - prowler_app_trigger_scan: Trigger manual security scans for providers
- - prowler_app_schedule_daily_scan: Schedule automated daily scans for continuous monitoring
- - prowler_app_update_scan: Update scan names for better organization
+ - prowler_list_scans: Search and filter scans with rich filtering capabilities
+ - prowler_get_scan: Get comprehensive details about a specific scan
+ - prowler_trigger_scan: Trigger manual security scans for providers
+ - prowler_schedule_daily_scan: Schedule automated daily scans for continuous monitoring
+ - prowler_update_scan: Update scan names for better organization
"""
async def list_scans(
self,
provider_id: list[str] = Field(
default=[],
- description="Filter by Prowler's internal UUID(s) (v4) for specific provider(s), generated when the provider was registered. Use `prowler_app_search_providers` tool to find provider IDs",
+ description="Filter by Prowler's internal UUID(s) (v4) for specific provider(s), generated when the provider was registered. Use `prowler_search_providers` tool to find provider IDs",
),
provider_type: list[str] = Field(
default=[],
@@ -56,7 +56,7 @@ class ScansTools(BaseTool):
),
trigger: Literal["manual", "scheduled"] | None = Field(
default=None,
- description="Filter by how the scan was initiated. Options: 'manual' (user-initiated via prowler_app_trigger_scan), 'scheduled' (automated via prowler_app_schedule_daily_scan)",
+ description="Filter by how the scan was initiated. Options: 'manual' (user-initiated via prowler_trigger_scan), 'scheduled' (automated via prowler_schedule_daily_scan)",
),
name: str | None = Field(
default=None,
@@ -75,7 +75,7 @@ class ScansTools(BaseTool):
IMPORTANT: This tool returns LIGHTWEIGHT scan information. Use this for fast searching and filtering
across many scans. For complete scan details including progress, duration, and resource counts,
- use prowler_app_get_scan on specific scans of interest.
+ use prowler_get_scan on specific scans of interest.
Default behavior:
- Returns all scans
@@ -83,15 +83,15 @@ class ScansTools(BaseTool):
- Includes all scan states (available, scheduled, executing, completed, failed, cancelled)
Each scan includes:
- - Core identification: id (UUID for prowler_app_get_scan), name
+ - Core identification: id (UUID for prowler_get_scan), name
- Execution context: state, trigger (manual/scheduled)
- Temporal data: started_at, completed_at
- Provider relationship: provider_id
Workflow:
1. Use this tool to search and filter scans by provider, state, or date range
- 2. Use prowler_app_get_scan with the scan 'id' to get progress, duration, and resource counts
- 3. Use prowler_app_search_security_findings filtered by scan dates to analyze scan results
+ 2. Use prowler_get_scan with the scan 'id' to get progress, duration, and resource counts
+ 3. Use prowler_search_security_findings filtered by scan dates to analyze scan results
"""
# Validate pagination
self.api_client.validate_page_size(page_size)
@@ -128,15 +128,15 @@ class ScansTools(BaseTool):
async def get_scan(
self,
scan_id: str = Field(
- description="Prowler's internal UUID (v4) for the scan to retrieve, generated when the scan was created (e.g., '123e4567-e89b-12d3-a456-426614174000'). Use `prowler_app_list_scans` tool to find scan IDs"
+ description="Prowler's internal UUID (v4) for the scan to retrieve, generated when the scan was created (e.g., '123e4567-e89b-12d3-a456-426614174000'). Use `prowler_list_scans` tool to find scan IDs"
),
) -> dict[str, Any]:
"""Retrieve comprehensive details about a specific scan by its ID.
IMPORTANT: This tool returns COMPLETE scan details.
- Use this after finding a specific scan via prowler_app_list_scans.
+ Use this after finding a specific scan via prowler_list_scans.
- This tool provides ALL information that prowler_app_list_scans returns PLUS:
+ This tool provides ALL information that prowler_list_scans returns PLUS:
1. Execution Details:
- progress: Scan completion progress as percentage (0-100%)
@@ -155,9 +155,9 @@ class ScansTools(BaseTool):
- Understanding scan scheduling patterns
Workflow:
- 1. Use prowler_app_list_scans to browse and filter scans
+ 1. Use prowler_list_scans to browse and filter scans
2. Use this tool with the scan 'id' to monitor progress or view detailed results
- 3. For completed scans, use prowler_app_search_security_findings filtered by date to analyze findings
+ 3. For completed scans, use prowler_search_security_findings filtered by date to analyze findings
"""
# Fetch scan with all fields
params = {
@@ -172,7 +172,7 @@ class ScansTools(BaseTool):
async def trigger_scan(
self,
provider_id: str = Field(
- description="Prowler's internal UUID (v4) for the provider to scan, generated when the provider was registered in the system (e.g., '4d0e2614-6385-4fa7-bf0b-c2e2f75c6877'). Use `prowler_app_search_providers` tool to find the provider ID"
+ description="Prowler's internal UUID (v4) for the provider to scan, generated when the provider was registered in the system (e.g., '4d0e2614-6385-4fa7-bf0b-c2e2f75c6877'). Use `prowler_search_providers` tool to find the provider ID"
),
name: str | None = Field(
default=None,
@@ -182,14 +182,14 @@ class ScansTools(BaseTool):
"""Trigger a manual security scan for a provider.
IMPORTANT: This tool returns immediately once the scan is created.
- The scan will continue running in the background. Use `prowler_app_get_scan`
+ The scan will continue running in the background. Use `prowler_get_scan`
with the returned scan ID to monitor progress and check when it completes.
Example Useful Workflow:
- 1. Use `prowler_app_search_providers` to find the provider_id you want to scan
+ 1. Use `prowler_search_providers` to find the provider_id you want to scan
2. Use this tool to trigger the scan
- 3. Use `prowler_app_get_scan` with the returned scan 'id' to monitor progress
- 4. Once completed, use `prowler_app_search_security_findings` to analyze results
+ 3. Use `prowler_get_scan` with the returned scan 'id' to monitor progress
+ 4. Once completed, use `prowler_search_security_findings` to analyze results
"""
try:
# Build request data
@@ -231,7 +231,7 @@ class ScansTools(BaseTool):
return ScanCreationResult(
scan=scan_info,
status="success",
- message=f"Scan {scan_id} created successfully. The scan may take some time to complete. Use prowler_app_get_scan tool with this ID to monitor progress.",
+ message=f"Scan {scan_id} created successfully. The scan may take some time to complete. Use prowler_get_scan tool with this ID to monitor progress.",
).model_dump()
except Exception as e:
@@ -245,7 +245,7 @@ class ScansTools(BaseTool):
async def schedule_daily_scan(
self,
provider_id: str = Field(
- description="Prowler's internal UUID (v4) for the provider to scan, generated when the provider was registered in the system (e.g., '4d0e2614-6385-4fa7-bf0b-c2e2f75c6877'). Use `prowler_app_search_providers` tool to find the provider ID"
+ description="Prowler's internal UUID (v4) for the provider to scan, generated when the provider was registered in the system (e.g., '4d0e2614-6385-4fa7-bf0b-c2e2f75c6877'). Use `prowler_search_providers` tool to find the provider ID"
),
) -> dict[str, Any]:
"""Schedule automated daily scans for a provider for continuous security monitoring.
@@ -256,17 +256,17 @@ class ScansTools(BaseTool):
you're not actively using the system.
IMPORTANT: This tool returns immediately once the daily schedule is created.
- The schedule will be set up in the background. Use `prowler_app_list_scans`
+ The schedule will be set up in the background. Use `prowler_list_scans`
filtered by provider_id and trigger='scheduled' to view scheduled scans.
IMPORTANT: This creates a PERSISTENT schedule. The provider will be scanned
automatically every 24 hours until the provider is deleted.
Example Useful Workflow:
- 1. Use `prowler_app_search_providers` to find the provider_id you want to monitor
+ 1. Use `prowler_search_providers` to find the provider_id you want to monitor
2. Use this tool to create the daily schedule
- 3. Use `prowler_app_list_scans` filtered by provider_id to view scheduled and completed scans
- 4. Monitor findings over time with `prowler_app_search_security_findings`
+ 3. Use `prowler_list_scans` filtered by provider_id to view scheduled and completed scans
+ 4. Monitor findings over time with `prowler_search_security_findings`
"""
self.logger.info(f"Creating daily schedule for provider {provider_id}")
task_response = await self.api_client.post(
@@ -285,7 +285,7 @@ class ScansTools(BaseTool):
)
if task_state == "available":
- return_message = "Daily schedule created successfully. The schedule is being set up in the background. Use prowler_app_list_scans with provider_id filter to view scheduled scans."
+ return_message = "Daily schedule created successfully. The schedule is being set up in the background. Use prowler_list_scans with provider_id filter to view scheduled scans."
else:
return_message = "Daily schedule creation failed. Please try again later."
@@ -297,7 +297,7 @@ class ScansTools(BaseTool):
async def update_scan(
self,
scan_id: str = Field(
- description="Prowler's internal UUID (v4) for the scan to update, generated when the scan was created (e.g., '123e4567-e89b-12d3-a456-426614174000'). Use `prowler_app_list_scans` tool to find the scan ID if you only know the provider or scan name. Returns an error if the scan ID is invalid or not found."
+ description="Prowler's internal UUID (v4) for the scan to update, generated when the scan was created (e.g., '123e4567-e89b-12d3-a456-426614174000'). Use `prowler_list_scans` tool to find the scan ID if you only know the provider or scan name. Returns an error if the scan ID is invalid or not found."
),
name: str = Field(
description="New human-friendly name for the scan (3-100 characters). Use descriptive names to improve organization and tracking, e.g., 'Production Security Audit - Q4 2025', 'Post-Deployment Compliance Check'. IMPORTANT: Only the scan name can be updated - other attributes (state, progress, duration) are read-only and managed by the system."
@@ -309,7 +309,7 @@ class ScansTools(BaseTool):
(state, progress, duration, etc.) are read-only and managed by the system.
Example Useful Workflow:
- 1. Use `prowler_app_list_scans` to find the scan you want to rename
+ 1. Use `prowler_list_scans` to find the scan you want to rename
2. Use this tool with the scan 'id' and new name
"""
api_response = await self.api_client.patch(
diff --git a/mcp_server/prowler_mcp_server/prowler_app/utils/api_client.py b/mcp_server/prowler_mcp_server/prowler_app/utils/api_client.py
index 4b6d0e77f5..187364bee1 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/utils/api_client.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/utils/api_client.py
@@ -1,12 +1,13 @@
-"""Shared API client utilities for Prowler App tools."""
+"""Shared API client utilities for Prowler tools."""
import asyncio
from datetime import datetime, timedelta
-from enum import Enum
-from typing import Any, Dict
+from enum import StrEnum
+from typing import Any
from urllib.parse import urlparse
import httpx
+
from prowler_mcp_server import __version__
from prowler_mcp_server.lib.logger import logger
from prowler_mcp_server.prowler_app.utils.auth import ProwlerAppAuth
@@ -14,7 +15,7 @@ from prowler_mcp_server.prowler_app.utils.auth import ProwlerAppAuth
ALLOWED_EXTERNAL_DOMAINS: frozenset[str] = frozenset({"raw.githubusercontent.com"})
-class HTTPMethod(str, Enum):
+class HTTPMethod(StrEnum):
"""HTTP methods enum."""
GET = "GET"
@@ -30,7 +31,7 @@ class SingletonMeta(type):
All calls to the constructor return the same instance.
"""
- _instances: Dict[type, Any] = {}
+ _instances: dict[type, Any] = {}
def __call__(cls, *args, **kwargs):
"""Control instance creation to ensure singleton behavior."""
diff --git a/mcp_server/prowler_mcp_server/prowler_app/utils/auth.py b/mcp_server/prowler_mcp_server/prowler_app/utils/auth.py
index 32ab72e574..eff5d3a117 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/utils/auth.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/utils/auth.py
@@ -2,15 +2,15 @@ import base64
import json
import os
from datetime import datetime
-from typing import Dict, Optional
from fastmcp.server.dependencies import get_http_headers
+
from prowler_mcp_server import __version__
from prowler_mcp_server.lib.logger import logger
class ProwlerAppAuth:
- """Handles authentication for Prowler App API using API keys or JWT tokens."""
+ """Handles authentication for Prowler API using API keys or JWT tokens."""
def __init__(
self,
@@ -18,21 +18,25 @@ class ProwlerAppAuth:
base_url: str = os.getenv("API_BASE_URL", "https://api.prowler.com/api/v1"),
):
self.base_url = base_url.rstrip("/")
- logger.info(f"Using Prowler App API base URL: {self.base_url}")
+ logger.info(f"Using Prowler API base URL: {self.base_url}")
self.mode = mode
- self.access_token: Optional[str] = None
- self.api_key: Optional[str] = None
+ self.access_token: str | None = None
+ self.api_key: str | None = None
if mode == "stdio": # STDIO mode
- self.api_key = os.getenv("PROWLER_APP_API_KEY")
+ # PROWLER_API_KEY is the current variable; PROWLER_APP_API_KEY is kept
+ # as a backward-compatible fallback so existing setups keep working.
+ self.api_key = os.getenv("PROWLER_API_KEY") or os.getenv(
+ "PROWLER_APP_API_KEY"
+ )
if not self.api_key:
- raise ValueError("PROWLER_APP_API_KEY environment variable is required")
+ raise ValueError("PROWLER_API_KEY environment variable is required")
if not self.api_key.startswith("pk_"):
- raise ValueError("Prowler App API key format is incorrect")
+ raise ValueError("Prowler API key format is incorrect")
- def _parse_jwt(self, token: str) -> Optional[Dict]:
+ def _parse_jwt(self, token: str) -> dict | None:
"""Parse JWT token and return payload
Args:
@@ -68,7 +72,7 @@ class ProwlerAppAuth:
async def authenticate(self) -> str:
"""Authenticate and return token (API key for STDIO, API key or JWT for HTTP)."""
if self.mode == "http":
- headers = get_http_headers()
+ headers = get_http_headers(include={"authorization"})
authorization_header = headers.get("authorization", None)
if not authorization_header:
@@ -109,7 +113,7 @@ class ProwlerAppAuth:
else:
return await self.authenticate()
- def get_headers(self, token: str) -> Dict[str, str]:
+ def get_headers(self, token: str) -> dict[str, str]:
"""Get headers for API requests with authentication."""
if token.startswith("pk_"):
authorization_header = f"Api-Key {token}"
diff --git a/mcp_server/prowler_mcp_server/prowler_app/utils/tool_loader.py b/mcp_server/prowler_mcp_server/prowler_app/utils/tool_loader.py
index 834bcaef7f..3a00474b5f 100644
--- a/mcp_server/prowler_mcp_server/prowler_app/utils/tool_loader.py
+++ b/mcp_server/prowler_mcp_server/prowler_app/utils/tool_loader.py
@@ -8,22 +8,32 @@ import importlib
import pkgutil
from fastmcp import FastMCP
+
from prowler_mcp_server.lib.logger import logger
from prowler_mcp_server.prowler_app.tools.base import BaseTool
-def load_all_tools(mcp: FastMCP) -> None:
- """Auto-discover and load all BaseTool subclasses from the tools package.
+def load_all_tools(
+ mcp: FastMCP,
+ tools_package: str = "prowler_mcp_server.prowler_app.tools",
+) -> None:
+ """Auto-discover and load all BaseTool subclasses from a tools package.
This function:
- 1. Dynamically imports all Python modules in the tools package
- 2. Discovers all concrete BaseTool subclasses
+ 1. Dynamically imports all Python modules in the given tools package
+ 2. Discovers all concrete BaseTool subclasses defined in that package
3. Instantiates each tool class
4. Registers all tools with the provided FastMCP instance
+ ``BaseTool.__subclasses__()`` returns every subclass in the process, so the
+ discovered classes are filtered by ``__module__`` prefix. This keeps sibling
+ sub-servers (e.g. ``prowler_app`` and ``prowler_cloud``) from cross-registering
+ each other's tools, regardless of import order.
+
Args:
mcp: The FastMCP instance to register tools with
- TOOLS_PACKAGE: The package path containing tool modules (default: prowler_mcp_server.prowler_app.tools)
+ tools_package: The package path containing tool modules
+ (default: prowler_mcp_server.prowler_app.tools)
Example:
from fastmcp import FastMCP
@@ -32,7 +42,7 @@ def load_all_tools(mcp: FastMCP) -> None:
app = FastMCP("prowler-app")
load_all_tools(app)
"""
- TOOLS_PACKAGE = "prowler_mcp_server.prowler_app.tools"
+ TOOLS_PACKAGE = tools_package
logger.info(f"Auto-discovering tools from package: {TOOLS_PACKAGE}")
# Import the tools package
@@ -58,11 +68,14 @@ def load_all_tools(mcp: FastMCP) -> None:
except Exception as e:
logger.error(f"Failed to import module {module_name}: {e}")
- # Discover all concrete BaseTool subclasses
+ # Discover all concrete BaseTool subclasses defined in this package only.
+ # __subclasses__() is process-wide, so filter by module to avoid sibling
+ # sub-servers cross-registering each other's tools.
concrete_tools = [
tool_class
for tool_class in BaseTool.__subclasses__()
if not getattr(tool_class, "__abstractmethods__", None)
+ and tool_class.__module__.startswith(TOOLS_PACKAGE)
]
logger.info(f"Discovered {len(concrete_tools)} tool classes")
diff --git a/mcp_server/prowler_mcp_server/prowler_documentation/search_engine.py b/mcp_server/prowler_mcp_server/prowler_documentation/search_engine.py
index a366c39c30..ba6f2a12e7 100644
--- a/mcp_server/prowler_mcp_server/prowler_documentation/search_engine.py
+++ b/mcp_server/prowler_mcp_server/prowler_documentation/search_engine.py
@@ -1,7 +1,8 @@
import httpx
-from prowler_mcp_server import __version__
from pydantic import BaseModel, Field
+from prowler_mcp_server import __version__
+
class SearchResult(BaseModel):
"""Search result model."""
diff --git a/mcp_server/prowler_mcp_server/server.py b/mcp_server/prowler_mcp_server/server.py
index e6cf399e72..a46ca12672 100644
--- a/mcp_server/prowler_mcp_server/server.py
+++ b/mcp_server/prowler_mcp_server/server.py
@@ -1,44 +1,43 @@
-import asyncio
-
from fastmcp import FastMCP
+from starlette.responses import JSONResponse
+
from prowler_mcp_server import __version__
from prowler_mcp_server.lib.logger import logger
-from starlette.responses import JSONResponse
prowler_mcp_server = FastMCP("prowler-mcp-server")
-async def setup_main_server():
+def setup_main_server():
"""Set up the main Prowler MCP server with all available integrations."""
- # Import Prowler Hub tools with prowler_hub_ prefix
+ # Mount Prowler Hub tools with prowler_hub_ namespace
try:
- logger.info("Importing Prowler Hub server...")
+ logger.info("Mounting Prowler Hub server...")
from prowler_mcp_server.prowler_hub.server import hub_mcp_server
- await prowler_mcp_server.import_server(hub_mcp_server, prefix="prowler_hub")
- logger.info("Successfully imported Prowler Hub server")
+ prowler_mcp_server.mount(hub_mcp_server, namespace="prowler_hub")
+ logger.info("Successfully mounted Prowler Hub server")
except Exception as e:
- logger.error(f"Failed to import Prowler Hub server: {e}")
+ logger.error(f"Failed to mount Prowler Hub server: {e}")
- # Import Prowler App tools with prowler_app_ prefix
+ # Mount core Prowler tools with prowler_ namespace
try:
- logger.info("Importing Prowler App server...")
+ logger.info("Mounting Prowler tools server...")
from prowler_mcp_server.prowler_app.server import app_mcp_server
- await prowler_mcp_server.import_server(app_mcp_server, prefix="prowler_app")
- logger.info("Successfully imported Prowler App server")
+ prowler_mcp_server.mount(app_mcp_server, namespace="prowler")
+ logger.info("Successfully mounted Prowler tools server")
except Exception as e:
- logger.error(f"Failed to import Prowler App server: {e}")
+ logger.error(f"Failed to mount Prowler tools server: {e}")
- # Import Prowler Documentation tools with prowler_docs_ prefix
+ # Mount Prowler Documentation tools with prowler_docs_ namespace
try:
- logger.info("Importing Prowler Documentation server...")
+ logger.info("Mounting Prowler Documentation server...")
from prowler_mcp_server.prowler_documentation.server import docs_mcp_server
- await prowler_mcp_server.import_server(docs_mcp_server, prefix="prowler_docs")
- logger.info("Successfully imported Prowler Documentation server")
+ prowler_mcp_server.mount(docs_mcp_server, namespace="prowler_docs")
+ logger.info("Successfully mounted Prowler Documentation server")
except Exception as e:
- logger.error(f"Failed to import Prowler Documentation server: {e}")
+ logger.error(f"Failed to mount Prowler Documentation server: {e}")
# Response follows the IETF Health Check Response Format
@@ -60,13 +59,6 @@ async def health_check(_request) -> JSONResponse:
)
-# Get or create the event loop
-try:
- loop = asyncio.get_running_loop()
- # If we have a running loop, schedule the setup as a task
- loop.create_task(setup_main_server())
-except RuntimeError:
- # No running loop, use asyncio.run (for standalone execution)
- asyncio.run(setup_main_server())
+setup_main_server()
app = prowler_mcp_server.http_app()
diff --git a/mcp_server/pyproject.toml b/mcp_server/pyproject.toml
index 1d18dfdc8e..f27e08b743 100644
--- a/mcp_server/pyproject.toml
+++ b/mcp_server/pyproject.toml
@@ -4,25 +4,46 @@ requires = ["setuptools>=61.0", "wheel"]
[dependency-groups]
dev = [
- "pytest==8.3.5"
+ "bandit==1.8.3",
+ "pytest==9.0.3",
+ "ruff==0.15.11",
+ "vulture==2.14"
]
[project]
dependencies = [
- "fastmcp==2.14.0",
+ "fastmcp==3.2.4",
"httpx==0.28.1"
]
description = "MCP server for Prowler ecosystem"
name = "prowler-mcp"
readme = "README.md"
requires-python = ">=3.12"
-version = "0.5.0"
+version = "0.8.0"
[project.scripts]
prowler-mcp = "prowler_mcp_server.main:main"
+[tool.pytest]
+
[tool.pytest.ini_options]
testpaths = ["tests"]
+# Shared ruff baseline (kept in sync with api/pyproject.toml).
+# target-version tracks this project's lowest supported Python.
+[tool.ruff]
+target-version = "py312"
+
+[tool.ruff.lint]
+# Defaults (E4/E7/E9, F) plus import sorting, modern-syntax upgrades, and
+# comprehension lints — all mechanically auto-fixable. flake8-bugbear (B) is a
+# good next step but needs manual cleanup, so it is left out of the shared
+# baseline for now.
+extend-select = [
+ "I", # isort — import ordering
+ "UP", # pyupgrade — modern syntax for the min supported Python
+ "C4" # flake8-comprehensions
+]
+
[tool.uv]
package = true
diff --git a/mcp_server/towncrier.toml b/mcp_server/towncrier.toml
new file mode 100644
index 0000000000..528e6129ec
--- /dev/null
+++ b/mcp_server/towncrier.toml
@@ -0,0 +1,39 @@
+[tool.towncrier]
+directory = "changelog.d"
+filename = "CHANGELOG.md"
+start_string = "<!-- changelog: release notes start -->\n"
+title_format = "## [{version}] ({name})"
+issue_format = "[(#{issue})](https://github.com/prowler-cloud/prowler/pull/{issue})"
+template = "../.github/towncrier/template.md.jinja"
+underlines = ["", "", ""]
+ignore = [".gitkeep", "README.md"]
+
+[[tool.towncrier.type]]
+directory = "added"
+name = "🚀 Added"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "changed"
+name = "🔄 Changed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "deprecated"
+name = "⚠️ Deprecated"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "removed"
+name = "❌ Removed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "fixed"
+name = "🐞 Fixed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "security"
+name = "🔐 Security"
+showcontent = true
diff --git a/mcp_server/uv.lock b/mcp_server/uv.lock
index 6d6d271cd9..a9afbeafd7 100644
--- a/mcp_server/uv.lock
+++ b/mcp_server/uv.lock
@@ -2,6 +2,18 @@ version = 1
revision = 3
requires-python = ">=3.12"
+[[package]]
+name = "aiofile"
+version = "3.9.0"
+source = { registry = "https://pypi.org/simple" }
+dependencies = [
+ { name = "caio" },
+]
+sdist = { url = "https://files.pythonhosted.org/packages/67/e2/d7cb819de8df6b5c1968a2756c3cb4122d4fa2b8fc768b53b7c9e5edb646/aiofile-3.9.0.tar.gz", hash = "sha256:e5ad718bb148b265b6df1b3752c4d1d83024b93da9bd599df74b9d9ffcf7919b", size = 17943, upload-time = "2024-10-08T10:39:35.846Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/50/25/da1f0b4dd970e52bf5a36c204c107e11a0c6d3ed195eba0bfbc664c312b2/aiofile-3.9.0-py3-none-any.whl", hash = "sha256:ce2f6c1571538cbdfa0143b04e16b208ecb0e9cb4148e528af8a640ed51cc8aa", size = 19539, upload-time = "2024-10-08T10:39:32.955Z" },
+]
+
[[package]]
name = "annotated-types"
version = "0.7.0"
@@ -13,64 +25,100 @@ wheels = [
[[package]]
name = "anyio"
-version = "4.10.0"
+version = "4.13.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "idna" },
- { name = "sniffio" },
{ name = "typing-extensions", marker = "python_full_version < '3.13'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/f1/b4/636b3b65173d3ce9a38ef5f0522789614e590dab6a8d505340a4efe4c567/anyio-4.10.0.tar.gz", hash = "sha256:3f3fae35c96039744587aa5b8371e7e8e603c0702999535961dd336026973ba6", size = 213252, upload-time = "2025-08-04T08:54:26.451Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/19/14/2c5dd9f512b66549ae92767a9c7b330ae88e1932ca57876909410251fe13/anyio-4.13.0.tar.gz", hash = "sha256:334b70e641fd2221c1505b3890c69882fe4a2df910cba14d97019b90b24439dc", size = 231622, upload-time = "2026-03-24T12:59:09.671Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/6f/12/e5e0282d673bb9746bacfb6e2dba8719989d3660cdb2ea79aee9a9651afb/anyio-4.10.0-py3-none-any.whl", hash = "sha256:60e474ac86736bbfd6f210f7a61218939c318f43f9972497381f1c5e930ed3d1", size = 107213, upload-time = "2025-08-04T08:54:24.882Z" },
+ { url = "https://files.pythonhosted.org/packages/da/42/e921fccf5015463e32a3cf6ee7f980a6ed0f395ceeaa45060b61d86486c2/anyio-4.13.0-py3-none-any.whl", hash = "sha256:08b310f9e24a9594186fd75b4f73f4a4152069e3853f1ed8bfbf58369f4ad708", size = 114353, upload-time = "2026-03-24T12:59:08.246Z" },
]
[[package]]
name = "attrs"
-version = "25.3.0"
+version = "26.1.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/5a/b0/1367933a8532ee6ff8d63537de4f1177af4bff9f3e829baf7331f595bb24/attrs-25.3.0.tar.gz", hash = "sha256:75d7cefc7fb576747b2c81b4442d4d4a1ce0900973527c011d1030fd3bf4af1b", size = 812032, upload-time = "2025-03-13T11:10:22.779Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/9a/8e/82a0fe20a541c03148528be8cac2408564a6c9a0cc7e9171802bc1d26985/attrs-26.1.0.tar.gz", hash = "sha256:d03ceb89cb322a8fd706d4fb91940737b6642aa36998fe130a9bc96c985eff32", size = 952055, upload-time = "2026-03-19T14:22:25.026Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/77/06/bb80f5f86020c4551da315d78b3ab75e8228f89f0162f2c3a819e407941a/attrs-25.3.0-py3-none-any.whl", hash = "sha256:427318ce031701fea540783410126f03899a97ffc6f61596ad581ac2e40e3bc3", size = 63815, upload-time = "2025-03-13T11:10:21.14Z" },
+ { url = "https://files.pythonhosted.org/packages/64/b4/17d4b0b2a2dc85a6df63d1157e028ed19f90d4cd97c36717afef2bc2f395/attrs-26.1.0-py3-none-any.whl", hash = "sha256:c647aa4a12dfbad9333ca4e71fe62ddc36f4e63b2d260a37a8b83d2f043ac309", size = 67548, upload-time = "2026-03-19T14:22:23.645Z" },
]
[[package]]
name = "authlib"
-version = "1.6.9"
+version = "1.7.2"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "cryptography" },
+ { name = "joserfc" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/af/98/00d3dd826d46959ad8e32af2dbb2398868fd9fd0683c26e56d0789bd0e68/authlib-1.6.9.tar.gz", hash = "sha256:d8f2421e7e5980cc1ddb4e32d3f5fa659cfaf60d8eaf3281ebed192e4ab74f04", size = 165134, upload-time = "2026-03-02T07:44:01.998Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/36/98/7d93f30d029643c0275dbc0bd6d5a6f670661ee6c9a94d93af7ab4887600/authlib-1.7.2.tar.gz", hash = "sha256:2cea25fefcd4e7173bdf1372c0afc265c8034b23a8cd5dcb6a9164b826c64231", size = 176511, upload-time = "2026-05-06T08:10:23.116Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/53/23/b65f568ed0c22f1efacb744d2db1a33c8068f384b8c9b482b52ebdbc3ef6/authlib-1.6.9-py2.py3-none-any.whl", hash = "sha256:f08b4c14e08f0861dc18a32357b33fbcfd2ea86cfe3fe149484b4d764c4a0ac3", size = 244197, upload-time = "2026-03-02T07:44:00.307Z" },
+ { url = "https://files.pythonhosted.org/packages/fb/95/adcb68e20c34162e9135f370d6e31737719c2b6f94bc953fe7ed1f10fe21/authlib-1.7.2-py2.py3-none-any.whl", hash = "sha256:3e1faedc9d87e7d56a164eca3ccb6ace0d61b94abe83e92242f8dc8bba9b4a9f", size = 259548, upload-time = "2026-05-06T08:10:21.436Z" },
+]
+
+[[package]]
+name = "bandit"
+version = "1.8.3"
+source = { registry = "https://pypi.org/simple" }
+dependencies = [
+ { name = "colorama", marker = "sys_platform == 'win32'" },
+ { name = "pyyaml" },
+ { name = "rich" },
+ { name = "stevedore" },
+]
+sdist = { url = "https://files.pythonhosted.org/packages/1a/a5/144a45f8e67df9d66c3bc3f7e69a39537db8bff1189ab7cff4e9459215da/bandit-1.8.3.tar.gz", hash = "sha256:f5847beb654d309422985c36644649924e0ea4425c76dec2e89110b87506193a", size = 4232005, upload-time = "2025-02-17T05:24:57.031Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/88/85/db74b9233e0aa27ec96891045c5e920a64dd5cbccd50f8e64e9460f48d35/bandit-1.8.3-py3-none-any.whl", hash = "sha256:28f04dc0d258e1dd0f99dee8eefa13d1cb5e3fde1a5ab0c523971f97b289bcd8", size = 129078, upload-time = "2025-02-17T05:24:54.068Z" },
]
[[package]]
name = "beartype"
-version = "0.22.6"
+version = "0.22.9"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/88/e2/105ceb1704cb80fe4ab3872529ab7b6f365cf7c74f725e6132d0efcf1560/beartype-0.22.6.tar.gz", hash = "sha256:97fbda69c20b48c5780ac2ca60ce3c1bb9af29b3a1a0216898ffabdd523e48f4", size = 1588975, upload-time = "2025-11-20T04:47:14.736Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/c7/94/1009e248bbfbab11397abca7193bea6626806be9a327d399810d523a07cb/beartype-0.22.9.tar.gz", hash = "sha256:8f82b54aa723a2848a56008d18875f91c1db02c32ef6a62319a002e3e25a975f", size = 1608866, upload-time = "2025-12-13T06:50:30.72Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/98/c9/ceecc71fe2c9495a1d8e08d44f5f31f5bca1350d5b2e27a4b6265424f59e/beartype-0.22.6-py3-none-any.whl", hash = "sha256:0584bc46a2ea2a871509679278cda992eadde676c01356ab0ac77421f3c9a093", size = 1324807, upload-time = "2025-11-20T04:47:11.837Z" },
+ { url = "https://files.pythonhosted.org/packages/71/cc/18245721fa7747065ab478316c7fea7c74777d07f37ae60db2e84f8172e8/beartype-0.22.9-py3-none-any.whl", hash = "sha256:d16c9bbc61ea14637596c5f6fbff2ee99cbe3573e46a716401734ef50c3060c2", size = 1333658, upload-time = "2025-12-13T06:50:28.266Z" },
]
[[package]]
name = "cachetools"
-version = "6.2.2"
+version = "7.1.1"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/fb/44/ca1675be2a83aeee1886ab745b28cda92093066590233cc501890eb8417a/cachetools-6.2.2.tar.gz", hash = "sha256:8e6d266b25e539df852251cfd6f990b4bc3a141db73b939058d809ebd2590fc6", size = 31571, upload-time = "2025-11-13T17:42:51.465Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/ff/e2/85f227594656000ff4d8adadae91a21f536d4a84c6c716a86bd6685874be/cachetools-7.1.1.tar.gz", hash = "sha256:27bdf856d68fd3c71c26c01b5edc312124ed427524d1ddb31aa2b7746fe20d4b", size = 40202, upload-time = "2026-05-03T20:00:29.391Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/e6/46/eb6eca305c77a4489affe1c5d8f4cae82f285d9addd8de4ec084a7184221/cachetools-6.2.2-py3-none-any.whl", hash = "sha256:6c09c98183bf58560c97b2abfcedcbaf6a896a490f534b031b661d3723b45ace", size = 11503, upload-time = "2025-11-13T17:42:50.232Z" },
+ { url = "https://files.pythonhosted.org/packages/bf/0f/f897abe4ea0a8c408ae65c8c83bffab4936ad65d6032d4fb4cd35bbdc3ee/cachetools-7.1.1-py3-none-any.whl", hash = "sha256:0335cd7a0952d2b22327441fb0628139e234c565559eeb91a8a4ac7551c5353d", size = 16775, upload-time = "2026-05-03T20:00:27.857Z" },
+]
+
+[[package]]
+name = "caio"
+version = "0.9.25"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/92/88/b8527e1b00c1811db339a1df8bd1ae49d146fcea9d6a5c40e3a80aaeb38d/caio-0.9.25.tar.gz", hash = "sha256:16498e7f81d1d0f5a4c0ad3f2540e65fe25691376e0a5bd367f558067113ed10", size = 26781, upload-time = "2025-12-26T15:21:36.501Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/d3/25/79c98ebe12df31548ba4eaf44db11b7cad6b3e7b4203718335620939083c/caio-0.9.25-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:fb7ff95af4c31ad3f03179149aab61097a71fd85e05f89b4786de0359dffd044", size = 36983, upload-time = "2025-12-26T15:21:36.075Z" },
+ { url = "https://files.pythonhosted.org/packages/a3/2b/21288691f16d479945968a0a4f2856818c1c5be56881d51d4dac9b255d26/caio-0.9.25-cp312-cp312-manylinux2010_x86_64.manylinux2014_x86_64.manylinux_2_12_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:97084e4e30dfa598449d874c4d8e0c8d5ea17d2f752ef5e48e150ff9d240cd64", size = 82012, upload-time = "2025-12-26T15:22:20.983Z" },
+ { url = "https://files.pythonhosted.org/packages/03/c4/8a1b580875303500a9c12b9e0af58cb82e47f5bcf888c2457742a138273c/caio-0.9.25-cp312-cp312-manylinux_2_34_aarch64.whl", hash = "sha256:4fa69eba47e0f041b9d4f336e2ad40740681c43e686b18b191b6c5f4c5544bfb", size = 81502, upload-time = "2026-03-04T22:08:22.381Z" },
+ { url = "https://files.pythonhosted.org/packages/d1/1c/0fe770b8ffc8362c48134d1592d653a81a3d8748d764bec33864db36319d/caio-0.9.25-cp312-cp312-manylinux_2_34_x86_64.whl", hash = "sha256:6bebf6f079f1341d19f7386db9b8b1f07e8cc15ae13bfdaff573371ba0575d69", size = 80200, upload-time = "2026-03-04T22:08:23.382Z" },
+ { url = "https://files.pythonhosted.org/packages/31/57/5e6ff127e6f62c9f15d989560435c642144aa4210882f9494204bc892305/caio-0.9.25-cp313-cp313-macosx_10_13_universal2.whl", hash = "sha256:d6c2a3411af97762a2b03840c3cec2f7f728921ff8adda53d7ea2315a8563451", size = 36979, upload-time = "2025-12-26T15:21:35.484Z" },
+ { url = "https://files.pythonhosted.org/packages/a3/9f/f21af50e72117eb528c422d4276cbac11fb941b1b812b182e0a9c70d19c5/caio-0.9.25-cp313-cp313-manylinux2010_x86_64.manylinux2014_x86_64.manylinux_2_12_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:0998210a4d5cd5cb565b32ccfe4e53d67303f868a76f212e002a8554692870e6", size = 81900, upload-time = "2025-12-26T15:22:21.919Z" },
+ { url = "https://files.pythonhosted.org/packages/9c/12/c39ae2a4037cb10ad5eb3578eb4d5f8c1a2575c62bba675f3406b7ef0824/caio-0.9.25-cp313-cp313-manylinux_2_34_aarch64.whl", hash = "sha256:1a177d4777141b96f175fe2c37a3d96dec7911ed9ad5f02bac38aaa1c936611f", size = 81523, upload-time = "2026-03-04T22:08:25.187Z" },
+ { url = "https://files.pythonhosted.org/packages/22/59/f8f2e950eb4f1a5a3883e198dca514b9d475415cb6cd7b78b9213a0dd45a/caio-0.9.25-cp313-cp313-manylinux_2_34_x86_64.whl", hash = "sha256:9ed3cfb28c0e99fec5e208c934e5c157d0866aa9c32aa4dc5e9b6034af6286b7", size = 80243, upload-time = "2026-03-04T22:08:26.449Z" },
+ { url = "https://files.pythonhosted.org/packages/69/ca/a08fdc7efdcc24e6a6131a93c85be1f204d41c58f474c42b0670af8c016b/caio-0.9.25-cp314-cp314-macosx_10_15_universal2.whl", hash = "sha256:fab6078b9348e883c80a5e14b382e6ad6aabbc4429ca034e76e730cf464269db", size = 36978, upload-time = "2025-12-26T15:21:41.055Z" },
+ { url = "https://files.pythonhosted.org/packages/5e/6c/d4d24f65e690213c097174d26eda6831f45f4734d9d036d81790a27e7b78/caio-0.9.25-cp314-cp314-manylinux2010_x86_64.manylinux2014_x86_64.manylinux_2_12_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:44a6b58e52d488c75cfaa5ecaa404b2b41cc965e6c417e03251e868ecd5b6d77", size = 81832, upload-time = "2025-12-26T15:22:22.757Z" },
+ { url = "https://files.pythonhosted.org/packages/87/a4/e534cf7d2d0e8d880e25dd61e8d921ffcfe15bd696734589826f5a2df727/caio-0.9.25-cp314-cp314-manylinux_2_34_aarch64.whl", hash = "sha256:628a630eb7fb22381dd8e3c8ab7f59e854b9c806639811fc3f4310c6bd711d79", size = 81565, upload-time = "2026-03-04T22:08:27.483Z" },
+ { url = "https://files.pythonhosted.org/packages/3f/ed/bf81aeac1d290017e5e5ac3e880fd56ee15e50a6d0353986799d1bc5cfd5/caio-0.9.25-cp314-cp314-manylinux_2_34_x86_64.whl", hash = "sha256:0ba16aa605ccb174665357fc729cf500679c2d94d5f1458a6f0d5ca48f2060a7", size = 80071, upload-time = "2026-03-04T22:08:28.751Z" },
+ { url = "https://files.pythonhosted.org/packages/86/93/1f76c8d1bafe3b0614e06b2195784a3765bbf7b0a067661af9e2dd47fc33/caio-0.9.25-py3-none-any.whl", hash = "sha256:06c0bb02d6b929119b1cfbe1ca403c768b2013a369e2db46bfa2a5761cf82e40", size = 19087, upload-time = "2025-12-26T15:22:00.221Z" },
]
[[package]]
name = "certifi"
-version = "2025.8.3"
+version = "2026.4.22"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/dc/67/960ebe6bf230a96cda2e0abcf73af550ec4f090005363542f0765df162e0/certifi-2025.8.3.tar.gz", hash = "sha256:e564105f78ded564e3ae7c923924435e1daa7463faeab5bb932bc53ffae63407", size = 162386, upload-time = "2025-08-03T03:07:47.08Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/25/ee/6caf7a40c36a1220410afe15a1cc64993a1f864871f698c0f93acb72842a/certifi-2026.4.22.tar.gz", hash = "sha256:8d455352a37b71bf76a79caa83a3d6c25afee4a385d632127b6afb3963f1c580", size = 137077, upload-time = "2026-04-22T11:26:11.191Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/e5/48/1549795ba7742c948d2ad169c1c8cdbae65bc450d6cd753d124b17c8cd32/certifi-2025.8.3-py3-none-any.whl", hash = "sha256:f6c12493cfb1b06ba2ff328595af9350c65d6644968e5d3a2ffd78699af217a5", size = 161216, upload-time = "2025-08-03T03:07:45.777Z" },
+ { url = "https://files.pythonhosted.org/packages/22/30/7cd8fdcdfbc5b869528b079bfb76dcdf6056b1a2097a662e5e8c04f42965/certifi-2026.4.22-py3-none-any.whl", hash = "sha256:3cb2210c8f88ba2318d29b0388d1023c8492ff72ecdde4ebdaddbb13a31b1c4a", size = 135707, upload-time = "2026-04-22T11:26:09.372Z" },
]
[[package]]
@@ -130,67 +178,16 @@ wheels = [
{ url = "https://files.pythonhosted.org/packages/ae/3a/dbeec9d1ee0844c679f6bb5d6ad4e9f198b1224f4e7a32825f47f6192b0c/cffi-2.0.0-cp314-cp314t-win_arm64.whl", hash = "sha256:0a1527a803f0a659de1af2e1fd700213caba79377e27e4693648c2923da066f9", size = 184195, upload-time = "2025-09-08T23:23:43.004Z" },
]
-[[package]]
-name = "charset-normalizer"
-version = "3.4.3"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/83/2d/5fd176ceb9b2fc619e63405525573493ca23441330fcdaee6bef9460e924/charset_normalizer-3.4.3.tar.gz", hash = "sha256:6fce4b8500244f6fcb71465d4a4930d132ba9ab8e71a7859e6a5d59851068d14", size = 122371, upload-time = "2025-08-09T07:57:28.46Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/e9/5e/14c94999e418d9b87682734589404a25854d5f5d0408df68bc15b6ff54bb/charset_normalizer-3.4.3-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:e28e334d3ff134e88989d90ba04b47d84382a828c061d0d1027b1b12a62b39b1", size = 205655, upload-time = "2025-08-09T07:56:08.475Z" },
- { url = "https://files.pythonhosted.org/packages/7d/a8/c6ec5d389672521f644505a257f50544c074cf5fc292d5390331cd6fc9c3/charset_normalizer-3.4.3-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:0cacf8f7297b0c4fcb74227692ca46b4a5852f8f4f24b3c766dd94a1075c4884", size = 146223, upload-time = "2025-08-09T07:56:09.708Z" },
- { url = "https://files.pythonhosted.org/packages/fc/eb/a2ffb08547f4e1e5415fb69eb7db25932c52a52bed371429648db4d84fb1/charset_normalizer-3.4.3-cp312-cp312-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:c6fd51128a41297f5409deab284fecbe5305ebd7e5a1f959bee1c054622b7018", size = 159366, upload-time = "2025-08-09T07:56:11.326Z" },
- { url = "https://files.pythonhosted.org/packages/82/10/0fd19f20c624b278dddaf83b8464dcddc2456cb4b02bb902a6da126b87a1/charset_normalizer-3.4.3-cp312-cp312-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:3cfb2aad70f2c6debfbcb717f23b7eb55febc0bb23dcffc0f076009da10c6392", size = 157104, upload-time = "2025-08-09T07:56:13.014Z" },
- { url = "https://files.pythonhosted.org/packages/16/ab/0233c3231af734f5dfcf0844aa9582d5a1466c985bbed6cedab85af9bfe3/charset_normalizer-3.4.3-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:1606f4a55c0fd363d754049cdf400175ee96c992b1f8018b993941f221221c5f", size = 151830, upload-time = "2025-08-09T07:56:14.428Z" },
- { url = "https://files.pythonhosted.org/packages/ae/02/e29e22b4e02839a0e4a06557b1999d0a47db3567e82989b5bb21f3fbbd9f/charset_normalizer-3.4.3-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:027b776c26d38b7f15b26a5da1044f376455fb3766df8fc38563b4efbc515154", size = 148854, upload-time = "2025-08-09T07:56:16.051Z" },
- { url = "https://files.pythonhosted.org/packages/05/6b/e2539a0a4be302b481e8cafb5af8792da8093b486885a1ae4d15d452bcec/charset_normalizer-3.4.3-cp312-cp312-musllinux_1_2_ppc64le.whl", hash = "sha256:42e5088973e56e31e4fa58eb6bd709e42fc03799c11c42929592889a2e54c491", size = 160670, upload-time = "2025-08-09T07:56:17.314Z" },
- { url = "https://files.pythonhosted.org/packages/31/e7/883ee5676a2ef217a40ce0bffcc3d0dfbf9e64cbcfbdf822c52981c3304b/charset_normalizer-3.4.3-cp312-cp312-musllinux_1_2_s390x.whl", hash = "sha256:cc34f233c9e71701040d772aa7490318673aa7164a0efe3172b2981218c26d93", size = 158501, upload-time = "2025-08-09T07:56:18.641Z" },
- { url = "https://files.pythonhosted.org/packages/c1/35/6525b21aa0db614cf8b5792d232021dca3df7f90a1944db934efa5d20bb1/charset_normalizer-3.4.3-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:320e8e66157cc4e247d9ddca8e21f427efc7a04bbd0ac8a9faf56583fa543f9f", size = 153173, upload-time = "2025-08-09T07:56:20.289Z" },
- { url = "https://files.pythonhosted.org/packages/50/ee/f4704bad8201de513fdc8aac1cabc87e38c5818c93857140e06e772b5892/charset_normalizer-3.4.3-cp312-cp312-win32.whl", hash = "sha256:fb6fecfd65564f208cbf0fba07f107fb661bcd1a7c389edbced3f7a493f70e37", size = 99822, upload-time = "2025-08-09T07:56:21.551Z" },
- { url = "https://files.pythonhosted.org/packages/39/f5/3b3836ca6064d0992c58c7561c6b6eee1b3892e9665d650c803bd5614522/charset_normalizer-3.4.3-cp312-cp312-win_amd64.whl", hash = "sha256:86df271bf921c2ee3818f0522e9a5b8092ca2ad8b065ece5d7d9d0e9f4849bcc", size = 107543, upload-time = "2025-08-09T07:56:23.115Z" },
- { url = "https://files.pythonhosted.org/packages/65/ca/2135ac97709b400c7654b4b764daf5c5567c2da45a30cdd20f9eefe2d658/charset_normalizer-3.4.3-cp313-cp313-macosx_10_13_universal2.whl", hash = "sha256:14c2a87c65b351109f6abfc424cab3927b3bdece6f706e4d12faaf3d52ee5efe", size = 205326, upload-time = "2025-08-09T07:56:24.721Z" },
- { url = "https://files.pythonhosted.org/packages/71/11/98a04c3c97dd34e49c7d247083af03645ca3730809a5509443f3c37f7c99/charset_normalizer-3.4.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:41d1fc408ff5fdfb910200ec0e74abc40387bccb3252f3f27c0676731df2b2c8", size = 146008, upload-time = "2025-08-09T07:56:26.004Z" },
- { url = "https://files.pythonhosted.org/packages/60/f5/4659a4cb3c4ec146bec80c32d8bb16033752574c20b1252ee842a95d1a1e/charset_normalizer-3.4.3-cp313-cp313-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:1bb60174149316da1c35fa5233681f7c0f9f514509b8e399ab70fea5f17e45c9", size = 159196, upload-time = "2025-08-09T07:56:27.25Z" },
- { url = "https://files.pythonhosted.org/packages/86/9e/f552f7a00611f168b9a5865a1414179b2c6de8235a4fa40189f6f79a1753/charset_normalizer-3.4.3-cp313-cp313-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:30d006f98569de3459c2fc1f2acde170b7b2bd265dc1943e87e1a4efe1b67c31", size = 156819, upload-time = "2025-08-09T07:56:28.515Z" },
- { url = "https://files.pythonhosted.org/packages/7e/95/42aa2156235cbc8fa61208aded06ef46111c4d3f0de233107b3f38631803/charset_normalizer-3.4.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:416175faf02e4b0810f1f38bcb54682878a4af94059a1cd63b8747244420801f", size = 151350, upload-time = "2025-08-09T07:56:29.716Z" },
- { url = "https://files.pythonhosted.org/packages/c2/a9/3865b02c56f300a6f94fc631ef54f0a8a29da74fb45a773dfd3dcd380af7/charset_normalizer-3.4.3-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:6aab0f181c486f973bc7262a97f5aca3ee7e1437011ef0c2ec04b5a11d16c927", size = 148644, upload-time = "2025-08-09T07:56:30.984Z" },
- { url = "https://files.pythonhosted.org/packages/77/d9/cbcf1a2a5c7d7856f11e7ac2d782aec12bdfea60d104e60e0aa1c97849dc/charset_normalizer-3.4.3-cp313-cp313-musllinux_1_2_ppc64le.whl", hash = "sha256:fdabf8315679312cfa71302f9bd509ded4f2f263fb5b765cf1433b39106c3cc9", size = 160468, upload-time = "2025-08-09T07:56:32.252Z" },
- { url = "https://files.pythonhosted.org/packages/f6/42/6f45efee8697b89fda4d50580f292b8f7f9306cb2971d4b53f8914e4d890/charset_normalizer-3.4.3-cp313-cp313-musllinux_1_2_s390x.whl", hash = "sha256:bd28b817ea8c70215401f657edef3a8aa83c29d447fb0b622c35403780ba11d5", size = 158187, upload-time = "2025-08-09T07:56:33.481Z" },
- { url = "https://files.pythonhosted.org/packages/70/99/f1c3bdcfaa9c45b3ce96f70b14f070411366fa19549c1d4832c935d8e2c3/charset_normalizer-3.4.3-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:18343b2d246dc6761a249ba1fb13f9ee9a2bcd95decc767319506056ea4ad4dc", size = 152699, upload-time = "2025-08-09T07:56:34.739Z" },
- { url = "https://files.pythonhosted.org/packages/a3/ad/b0081f2f99a4b194bcbb1934ef3b12aa4d9702ced80a37026b7607c72e58/charset_normalizer-3.4.3-cp313-cp313-win32.whl", hash = "sha256:6fb70de56f1859a3f71261cbe41005f56a7842cc348d3aeb26237560bfa5e0ce", size = 99580, upload-time = "2025-08-09T07:56:35.981Z" },
- { url = "https://files.pythonhosted.org/packages/9a/8f/ae790790c7b64f925e5c953b924aaa42a243fb778fed9e41f147b2a5715a/charset_normalizer-3.4.3-cp313-cp313-win_amd64.whl", hash = "sha256:cf1ebb7d78e1ad8ec2a8c4732c7be2e736f6e5123a4146c5b89c9d1f585f8cef", size = 107366, upload-time = "2025-08-09T07:56:37.339Z" },
- { url = "https://files.pythonhosted.org/packages/8e/91/b5a06ad970ddc7a0e513112d40113e834638f4ca1120eb727a249fb2715e/charset_normalizer-3.4.3-cp314-cp314-macosx_10_13_universal2.whl", hash = "sha256:3cd35b7e8aedeb9e34c41385fda4f73ba609e561faedfae0a9e75e44ac558a15", size = 204342, upload-time = "2025-08-09T07:56:38.687Z" },
- { url = "https://files.pythonhosted.org/packages/ce/ec/1edc30a377f0a02689342f214455c3f6c2fbedd896a1d2f856c002fc3062/charset_normalizer-3.4.3-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:b89bc04de1d83006373429975f8ef9e7932534b8cc9ca582e4db7d20d91816db", size = 145995, upload-time = "2025-08-09T07:56:40.048Z" },
- { url = "https://files.pythonhosted.org/packages/17/e5/5e67ab85e6d22b04641acb5399c8684f4d37caf7558a53859f0283a650e9/charset_normalizer-3.4.3-cp314-cp314-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl", hash = "sha256:2001a39612b241dae17b4687898843f254f8748b796a2e16f1051a17078d991d", size = 158640, upload-time = "2025-08-09T07:56:41.311Z" },
- { url = "https://files.pythonhosted.org/packages/f1/e5/38421987f6c697ee3722981289d554957c4be652f963d71c5e46a262e135/charset_normalizer-3.4.3-cp314-cp314-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:8dcfc373f888e4fb39a7bc57e93e3b845e7f462dacc008d9749568b1c4ece096", size = 156636, upload-time = "2025-08-09T07:56:43.195Z" },
- { url = "https://files.pythonhosted.org/packages/a0/e4/5a075de8daa3ec0745a9a3b54467e0c2967daaaf2cec04c845f73493e9a1/charset_normalizer-3.4.3-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:18b97b8404387b96cdbd30ad660f6407799126d26a39ca65729162fd810a99aa", size = 150939, upload-time = "2025-08-09T07:56:44.819Z" },
- { url = "https://files.pythonhosted.org/packages/02/f7/3611b32318b30974131db62b4043f335861d4d9b49adc6d57c1149cc49d4/charset_normalizer-3.4.3-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:ccf600859c183d70eb47e05a44cd80a4ce77394d1ac0f79dbd2dd90a69a3a049", size = 148580, upload-time = "2025-08-09T07:56:46.684Z" },
- { url = "https://files.pythonhosted.org/packages/7e/61/19b36f4bd67f2793ab6a99b979b4e4f3d8fc754cbdffb805335df4337126/charset_normalizer-3.4.3-cp314-cp314-musllinux_1_2_ppc64le.whl", hash = "sha256:53cd68b185d98dde4ad8990e56a58dea83a4162161b1ea9272e5c9182ce415e0", size = 159870, upload-time = "2025-08-09T07:56:47.941Z" },
- { url = "https://files.pythonhosted.org/packages/06/57/84722eefdd338c04cf3030ada66889298eaedf3e7a30a624201e0cbe424a/charset_normalizer-3.4.3-cp314-cp314-musllinux_1_2_s390x.whl", hash = "sha256:30a96e1e1f865f78b030d65241c1ee850cdf422d869e9028e2fc1d5e4db73b92", size = 157797, upload-time = "2025-08-09T07:56:49.756Z" },
- { url = "https://files.pythonhosted.org/packages/72/2a/aff5dd112b2f14bcc3462c312dce5445806bfc8ab3a7328555da95330e4b/charset_normalizer-3.4.3-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:d716a916938e03231e86e43782ca7878fb602a125a91e7acb8b5112e2e96ac16", size = 152224, upload-time = "2025-08-09T07:56:51.369Z" },
- { url = "https://files.pythonhosted.org/packages/b7/8c/9839225320046ed279c6e839d51f028342eb77c91c89b8ef2549f951f3ec/charset_normalizer-3.4.3-cp314-cp314-win32.whl", hash = "sha256:c6dbd0ccdda3a2ba7c2ecd9d77b37f3b5831687d8dc1b6ca5f56a4880cc7b7ce", size = 100086, upload-time = "2025-08-09T07:56:52.722Z" },
- { url = "https://files.pythonhosted.org/packages/ee/7a/36fbcf646e41f710ce0a563c1c9a343c6edf9be80786edeb15b6f62e17db/charset_normalizer-3.4.3-cp314-cp314-win_amd64.whl", hash = "sha256:73dc19b562516fc9bcf6e5d6e596df0b4eb98d87e4f79f3ae71840e6ed21361c", size = 107400, upload-time = "2025-08-09T07:56:55.172Z" },
- { url = "https://files.pythonhosted.org/packages/8a/1f/f041989e93b001bc4e44bb1669ccdcf54d3f00e628229a85b08d330615c5/charset_normalizer-3.4.3-py3-none-any.whl", hash = "sha256:ce571ab16d890d23b5c278547ba694193a45011ff86a9162a71307ed9f86759a", size = 53175, upload-time = "2025-08-09T07:57:26.864Z" },
-]
-
[[package]]
name = "click"
-version = "8.3.0"
+version = "8.3.3"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "colorama", marker = "sys_platform == 'win32'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/46/61/de6cd827efad202d7057d93e0fed9294b96952e188f7384832791c7b2254/click-8.3.0.tar.gz", hash = "sha256:e7b8232224eba16f4ebe410c25ced9f7875cb5f3263ffc93cc3e8da705e229c4", size = 276943, upload-time = "2025-09-18T17:32:23.696Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/bb/63/f9e1ea081ce35720d8b92acde70daaedace594dc93b693c869e0d5910718/click-8.3.3.tar.gz", hash = "sha256:398329ad4837b2ff7cbe1dd166a4c0f8900c3ca3a218de04466f38f6497f18a2", size = 328061, upload-time = "2026-04-22T15:11:27.506Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/db/d3/9dcc0f5797f070ec8edf30fbadfb200e71d9db6b84d211e3b2085a7589a0/click-8.3.0-py3-none-any.whl", hash = "sha256:9b9f285302c6e3064f4330c05f05b81945b2a39544279343e6e7c5f27a9baddc", size = 107295, upload-time = "2025-09-18T17:32:22.42Z" },
-]
-
-[[package]]
-name = "cloudpickle"
-version = "3.1.2"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/27/fb/576f067976d320f5f0114a8d9fa1215425441bb35627b1993e5afd8111e5/cloudpickle-3.1.2.tar.gz", hash = "sha256:7fda9eb655c9c230dab534f1983763de5835249750e85fbcef43aaa30a9a2414", size = 22330, upload-time = "2025-11-03T09:25:26.604Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/88/39/799be3f2f0f38cc727ee3b4f1445fe6d5e4133064ec2e4115069418a5bb6/cloudpickle-3.1.2-py3-none-any.whl", hash = "sha256:9acb47f6afd73f60dc1df93bb801b472f05ff42fa6c84167d25cb206be1fbf4a", size = 22228, upload-time = "2025-11-03T09:25:25.534Z" },
+ { url = "https://files.pythonhosted.org/packages/ae/44/c1221527f6a71a01ec6fbad7fa78f1d50dfa02217385cf0fa3eec7087d59/click-8.3.3-py3-none-any.whl", hash = "sha256:a2bf429bb3033c89fa4936ffb35d5cb471e3719e1f3c8a7c3fff0b8314305613", size = 110502, upload-time = "2026-04-22T15:11:25.044Z" },
]
[[package]]
@@ -204,60 +201,60 @@ wheels = [
[[package]]
name = "cryptography"
-version = "47.0.0"
+version = "48.0.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "cffi", marker = "platform_python_implementation != 'PyPy'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/ef/b2/7ffa7fe8207a8c42147ffe70c3e360b228160c1d85dc3faff16aaa3244c0/cryptography-47.0.0.tar.gz", hash = "sha256:9f8e55fe4e63613a5e1cc5819030f27b97742d720203a087802ce4ce9ceb52bb", size = 830863, upload-time = "2026-04-24T19:54:57.056Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/9f/a9/db8f313fdcd85d767d4973515e1db101f9c71f95fced83233de224673757/cryptography-48.0.0.tar.gz", hash = "sha256:5c3932f4436d1cccb036cb0eaef46e6e2db91035166f1ad6505c3c9d5a635920", size = 832984, upload-time = "2026-05-04T22:59:38.133Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/a4/98/40dfe932134bdcae4f6ab5927c87488754bf9eb79297d7e0070b78dd58e9/cryptography-47.0.0-cp311-abi3-macosx_10_9_universal2.whl", hash = "sha256:160ad728f128972d362e714054f6ba0067cab7fb350c5202a9ae8ae4ce3ef1a0", size = 7912214, upload-time = "2026-04-24T19:53:03.864Z" },
- { url = "https://files.pythonhosted.org/packages/34/c6/2733531243fba725f58611b918056b277692f1033373dcc8bd01af1c05d4/cryptography-47.0.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:b9a8943e359b7615db1a3ba587994618e094ff3d6fa5a390c73d079ce18b3973", size = 4644617, upload-time = "2026-04-24T19:53:06.909Z" },
- { url = "https://files.pythonhosted.org/packages/00/e3/b27be1a670a9b87f855d211cf0e1174a5d721216b7616bd52d8581d912ed/cryptography-47.0.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:f5c15764f261394b22aef6b00252f5195f46f2ca300bec57149474e2538b31f8", size = 4668186, upload-time = "2026-04-24T19:53:09.053Z" },
- { url = "https://files.pythonhosted.org/packages/81/b9/8443cfe5d17d482d348cee7048acf502bb89a51b6382f06240fd290d4ca3/cryptography-47.0.0-cp311-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:9c59ab0e0fa3a180a5a9c59f3a5abe3ef90d474bc56d7fadfbe80359491b615b", size = 4651244, upload-time = "2026-04-24T19:53:11.217Z" },
- { url = "https://files.pythonhosted.org/packages/5d/5e/13ed0cdd0eb88ba159d6dd5ebfece8cb901dbcf1ae5ac4072e28b55d3153/cryptography-47.0.0-cp311-abi3-manylinux_2_28_ppc64le.whl", hash = "sha256:34b4358b925a5ea3e14384ca781a2c0ef7ac219b57bb9eacc4457078e2b19f92", size = 5252906, upload-time = "2026-04-24T19:53:13.532Z" },
- { url = "https://files.pythonhosted.org/packages/64/16/ed058e1df0f33d440217cd120d41d5dda9dd215a80b8187f68483185af82/cryptography-47.0.0-cp311-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:0024b87d47ae2399165a6bfb20d24888881eeab83ae2566d62467c5ff0030ce7", size = 4701842, upload-time = "2026-04-24T19:53:15.618Z" },
- { url = "https://files.pythonhosted.org/packages/02/e0/3d30986b30fdbd9e969abbdf8ba00ed0618615144341faeb57f395a084fe/cryptography-47.0.0-cp311-abi3-manylinux_2_31_armv7l.whl", hash = "sha256:1e47422b5557bb82d3fff997e8d92cff4e28b9789576984f08c248d2b3535d93", size = 4289313, upload-time = "2026-04-24T19:53:17.755Z" },
- { url = "https://files.pythonhosted.org/packages/df/fd/32db38e3ad0cb331f0691cb4c7a8a6f176f679124dee746b3af6633db4d9/cryptography-47.0.0-cp311-abi3-manylinux_2_34_aarch64.whl", hash = "sha256:6f29f36582e6151d9686235e586dd35bb67491f024767d10b842e520dc6a07ac", size = 4650964, upload-time = "2026-04-24T19:53:20.062Z" },
- { url = "https://files.pythonhosted.org/packages/86/53/5395d944dfd48cb1f67917f533c609c34347185ef15eb4308024c876f274/cryptography-47.0.0-cp311-abi3-manylinux_2_34_ppc64le.whl", hash = "sha256:a9b761f012a943b7de0e828843c5688d0de94a0578d44d6c85a1bae32f87791f", size = 5207817, upload-time = "2026-04-24T19:53:22.498Z" },
- { url = "https://files.pythonhosted.org/packages/34/4f/e5711b28e1901f7d480a2b1b688b645aa4c77c73f10731ed17e7f7db3f0d/cryptography-47.0.0-cp311-abi3-manylinux_2_34_x86_64.whl", hash = "sha256:4e1de79e047e25d6e9f8cea71c86b4a53aced64134f0f003bbcbf3655fd172c8", size = 4701544, upload-time = "2026-04-24T19:53:24.356Z" },
- { url = "https://files.pythonhosted.org/packages/22/22/c8ddc25de3010fc8da447648f5a092c40e7a8fadf01dd6d255d9c0b9373d/cryptography-47.0.0-cp311-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:ef6b3634087f18d2155b1e8ce264e5345a753da2c5fa9815e7d41315c90f8318", size = 4783536, upload-time = "2026-04-24T19:53:26.665Z" },
- { url = "https://files.pythonhosted.org/packages/66/b6/d4a68f4ea999c6d89e8498579cba1c5fcba4276284de7773b17e4fa69293/cryptography-47.0.0-cp311-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:11dbb9f50a0f1bb9757b3d8c27c1101780efb8f0bdecfb12439c22a74d64c001", size = 4926106, upload-time = "2026-04-24T19:53:28.686Z" },
- { url = "https://files.pythonhosted.org/packages/54/ed/5f524db1fade9c013aa618e1c99c6ed05e8ffc9ceee6cda22fed22dda3f4/cryptography-47.0.0-cp311-abi3-win32.whl", hash = "sha256:7fda2f02c9015db3f42bb8a22324a454516ed10a8c29ca6ece6cdbb5efe2a203", size = 3258581, upload-time = "2026-04-24T19:53:31.058Z" },
- { url = "https://files.pythonhosted.org/packages/b2/dc/1b901990b174786569029f67542b3edf72ac068b6c3c8683c17e6a2f5363/cryptography-47.0.0-cp311-abi3-win_amd64.whl", hash = "sha256:f5c3296dab66202f1b18a91fa266be93d6aa0c2806ea3d67762c69f60adc71aa", size = 3775309, upload-time = "2026-04-24T19:53:33.054Z" },
- { url = "https://files.pythonhosted.org/packages/14/88/7aa18ad9c11bc87689affa5ce4368d884b517502d75739d475fc6f4a03c7/cryptography-47.0.0-cp314-cp314t-macosx_10_9_universal2.whl", hash = "sha256:be12cb6a204f77ed968bcefe68086eb061695b540a3dd05edac507a3111b25f0", size = 7904299, upload-time = "2026-04-24T19:53:35.003Z" },
- { url = "https://files.pythonhosted.org/packages/07/55/c18f75724544872f234678fdedc871391722cb34a2aee19faa9f63100bb2/cryptography-47.0.0-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:2ebd84adf0728c039a3be2700289378e1c164afc6748df1a5ed456767bef9ba7", size = 4631180, upload-time = "2026-04-24T19:53:37.517Z" },
- { url = "https://files.pythonhosted.org/packages/ee/65/31a5cc0eaca99cec5bafffe155d407115d96136bb161e8b49e0ef73f09a7/cryptography-47.0.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:7f68d6fbc7fbbcfb0939fea72c3b96a9f9a6edfc0e1b1d29778a2066030418b1", size = 4653529, upload-time = "2026-04-24T19:53:39.775Z" },
- { url = "https://files.pythonhosted.org/packages/e5/bc/641c0519a495f3bfd0421b48d7cd325c4336578523ccd76ea322b6c29c7a/cryptography-47.0.0-cp314-cp314t-manylinux_2_28_aarch64.whl", hash = "sha256:6651d32eff255423503aa276739da98c30f26c40cbeffcc6048e0d54ef704c0c", size = 4638570, upload-time = "2026-04-24T19:53:42.129Z" },
- { url = "https://files.pythonhosted.org/packages/2b/f2/300327b0a47f6dc94dd8b71b57052aefe178bb51745073d73d80604f11ab/cryptography-47.0.0-cp314-cp314t-manylinux_2_28_ppc64le.whl", hash = "sha256:3fb8fa48075fad7193f2e5496135c6a76ac4b2aa5a38433df0a539296b377829", size = 5238019, upload-time = "2026-04-24T19:53:44.577Z" },
- { url = "https://files.pythonhosted.org/packages/e9/5a/5b5cf994391d4bf9d9c7efd4c66aabe4d95227256627f8fea6cff7dfadbd/cryptography-47.0.0-cp314-cp314t-manylinux_2_28_x86_64.whl", hash = "sha256:11438c7518132d95f354fa01a4aa2f806d172a061a7bed18cf18cbdacdb204d7", size = 4686832, upload-time = "2026-04-24T19:53:47.015Z" },
- { url = "https://files.pythonhosted.org/packages/dc/2c/ae950e28fd6475c852fc21a44db3e6b5bcc1261d1e370f2b6e42fa800fef/cryptography-47.0.0-cp314-cp314t-manylinux_2_31_armv7l.whl", hash = "sha256:8c1a736bbb3288005796c3f7ccb9453360d7fed483b13b9f468aea5171432923", size = 4269301, upload-time = "2026-04-24T19:53:48.97Z" },
- { url = "https://files.pythonhosted.org/packages/67/fb/6a39782e150ffe5cc1b0018cb6ddc48bf7ca62b498d7539ffc8a758e977d/cryptography-47.0.0-cp314-cp314t-manylinux_2_34_aarch64.whl", hash = "sha256:f1557695e5c2b86e204f6ce9470497848634100787935ab7adc5397c54abd7ab", size = 4638110, upload-time = "2026-04-24T19:53:51.011Z" },
- { url = "https://files.pythonhosted.org/packages/8e/d7/0b3c71090a76e5c203164a47688b697635ece006dcd2499ab3a4dbd3f0bd/cryptography-47.0.0-cp314-cp314t-manylinux_2_34_ppc64le.whl", hash = "sha256:f9a034b642b960767fb343766ae5ba6ad653f2e890ddd82955aef288ffea8736", size = 5194988, upload-time = "2026-04-24T19:53:52.962Z" },
- { url = "https://files.pythonhosted.org/packages/63/33/63a961498a9df51721ab578c5a2622661411fc520e00bd83b0cc64eb20c4/cryptography-47.0.0-cp314-cp314t-manylinux_2_34_x86_64.whl", hash = "sha256:b1c76fca783aa7698eb21eb14f9c4aa09452248ee54a627d125025a43f83e7a7", size = 4686563, upload-time = "2026-04-24T19:53:55.274Z" },
- { url = "https://files.pythonhosted.org/packages/b7/bf/5ee5b145248f92250de86145d1c1d6edebbd57a7fe7caa4dedb5d4cf06a1/cryptography-47.0.0-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:4f7722c97826770bab8ae92959a2e7b20a5e9e9bf4deae68fd86c3ca457bab52", size = 4770094, upload-time = "2026-04-24T19:53:57.753Z" },
- { url = "https://files.pythonhosted.org/packages/92/43/21d220b2da5d517773894dacdcdb5c682c28d3fffce65548cb06e87d5501/cryptography-47.0.0-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:09f6d7bf6724f8db8b32f11eccf23efc8e759924bc5603800335cf8859a3ddbd", size = 4913811, upload-time = "2026-04-24T19:54:00.236Z" },
- { url = "https://files.pythonhosted.org/packages/31/98/dc4ad376ac5f1a1a7d4a83f7b0c6f2bcad36b5d2d8f30aeb482d3a7d9582/cryptography-47.0.0-cp314-cp314t-win32.whl", hash = "sha256:6eebcaf0df1d21ce1f90605c9b432dd2c4f4ab665ac29a40d5e3fc68f51b5e63", size = 3237158, upload-time = "2026-04-24T19:54:02.606Z" },
- { url = "https://files.pythonhosted.org/packages/bc/da/97f62d18306b5133468bc3f8cc73a3111e8cdc8cf8d3e69474d6e5fd2d1b/cryptography-47.0.0-cp314-cp314t-win_amd64.whl", hash = "sha256:51c9313e90bd1690ec5a75ed047c27c0b8e6c570029712943d6116ef9a90620b", size = 3758706, upload-time = "2026-04-24T19:54:04.433Z" },
- { url = "https://files.pythonhosted.org/packages/e0/34/a4fae8ae7c3bc227460c9ae43f56abf1b911da0ec29e0ebac53bb0a4b6b7/cryptography-47.0.0-cp38-abi3-macosx_10_9_universal2.whl", hash = "sha256:14432c8a9bcb37009784f9594a62fae211a2ae9543e96c92b2a8e4c3cd5cd0c4", size = 7904072, upload-time = "2026-04-24T19:54:06.411Z" },
- { url = "https://files.pythonhosted.org/packages/01/64/d7b1e54fdb69f22d24a64bb3e88dc718b31c7fb10ef0b9691a3cf7eeea6e/cryptography-47.0.0-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:07efe86201817e7d3c18781ca9770bc0db04e1e48c994be384e4602bc38f8f27", size = 4635767, upload-time = "2026-04-24T19:54:08.519Z" },
- { url = "https://files.pythonhosted.org/packages/8b/7b/cca826391fb2a94efdcdfe4631eb69306ee1cff0b22f664a412c90713877/cryptography-47.0.0-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:2b45761c6ec22b7c726d6a829558777e32d0f1c8be7c3f3480f9c912d5ee8a10", size = 4654350, upload-time = "2026-04-24T19:54:10.795Z" },
- { url = "https://files.pythonhosted.org/packages/4c/65/4b57bcc823f42a991627c51c2f68c9fd6eb1393c1756aac876cba2accae2/cryptography-47.0.0-cp38-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:edd4da498015da5b9f26d38d3bfc2e90257bfa9cbed1f6767c282a0025ae649b", size = 4643394, upload-time = "2026-04-24T19:54:13.275Z" },
- { url = "https://files.pythonhosted.org/packages/f4/c4/2c5fbeea70adbbca2bbae865e1d605d6a4a7f8dbd9d33eaf69645087f06c/cryptography-47.0.0-cp38-abi3-manylinux_2_28_ppc64le.whl", hash = "sha256:9af828c0d5a65c70ec729cd7495a4bf1a67ecb66417b8f02ff125ab8a6326a74", size = 5225777, upload-time = "2026-04-24T19:54:15.18Z" },
- { url = "https://files.pythonhosted.org/packages/7e/b8/ac57107ef32749d2b244e36069bb688792a363aaaa3acc9e3cf84c130315/cryptography-47.0.0-cp38-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:256d07c78a04d6b276f5df935a9923275f53bd1522f214447fdf365494e2d515", size = 4688771, upload-time = "2026-04-24T19:54:17.835Z" },
- { url = "https://files.pythonhosted.org/packages/56/fc/9f1de22ff8be99d991f240a46863c52d475404c408886c5a38d2b5c3bb26/cryptography-47.0.0-cp38-abi3-manylinux_2_31_armv7l.whl", hash = "sha256:5d0e362ff51041b0c0d219cc7d6924d7b8996f57ce5712bdcef71eb3c65a59cc", size = 4270753, upload-time = "2026-04-24T19:54:19.963Z" },
- { url = "https://files.pythonhosted.org/packages/00/68/d70c852797aa68e8e48d12e5a87170c43f67bb4a59403627259dd57d15de/cryptography-47.0.0-cp38-abi3-manylinux_2_34_aarch64.whl", hash = "sha256:1581aef4219f7ca2849d0250edaa3866212fb74bf5667284f46aa92f9e65c1ca", size = 4642911, upload-time = "2026-04-24T19:54:21.818Z" },
- { url = "https://files.pythonhosted.org/packages/a5/51/661cbee74f594c5d97ff82d34f10d5551c085ca4668645f4606ebd22bd5d/cryptography-47.0.0-cp38-abi3-manylinux_2_34_ppc64le.whl", hash = "sha256:a49a3eb5341b9503fa3000a9a0db033161db90d47285291f53c2a9d2cd1b7f76", size = 5181411, upload-time = "2026-04-24T19:54:24.376Z" },
- { url = "https://files.pythonhosted.org/packages/94/87/f2b6c374a82cf076cfa1416992ac8e8ec94d79facc37aec87c1a5cb72352/cryptography-47.0.0-cp38-abi3-manylinux_2_34_x86_64.whl", hash = "sha256:2207a498b03275d0051589e326b79d4cf59985c99031b05bb292ac52631c37fe", size = 4688262, upload-time = "2026-04-24T19:54:26.946Z" },
- { url = "https://files.pythonhosted.org/packages/14/e2/8b7462f4acf21ec509616f0245018bb197194ab0b65c2ea21a0bdd53c0eb/cryptography-47.0.0-cp38-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:7a02675e2fabd0c0fc04c868b8781863cbf1967691543c22f5470500ff840b31", size = 4775506, upload-time = "2026-04-24T19:54:28.926Z" },
- { url = "https://files.pythonhosted.org/packages/70/75/158e494e4c08dc05e039da5bb48553826bd26c23930cf8d3cd5f21fa8921/cryptography-47.0.0-cp38-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:80887c5cbd1774683cb126f0ab4184567f080071d5acf62205acb354b4b753b7", size = 4912060, upload-time = "2026-04-24T19:54:30.869Z" },
- { url = "https://files.pythonhosted.org/packages/06/bd/0a9d3edbf5eadbac926d7b9b3cd0c4be584eeeae4a003d24d9eda4affbbd/cryptography-47.0.0-cp38-abi3-win32.whl", hash = "sha256:ed67ea4e0cfb5faa5bc7ecb6e2b8838f3807a03758eec239d6c21c8769355310", size = 3248487, upload-time = "2026-04-24T19:54:33.494Z" },
- { url = "https://files.pythonhosted.org/packages/60/80/5681af756d0da3a599b7bdb586fac5a1540f1bcefd2717a20e611ddade45/cryptography-47.0.0-cp38-abi3-win_amd64.whl", hash = "sha256:835d2d7f47cdc53b3224e90810fb1d36ca94ea29cc1801fb4c1bc43876735769", size = 3755737, upload-time = "2026-04-24T19:54:35.408Z" },
+ { url = "https://files.pythonhosted.org/packages/df/3d/01f6dd9190170a5a241e0e98c2d04be3664a9e6f5b9b872cde63aff1c3dd/cryptography-48.0.0-cp311-abi3-macosx_10_9_universal2.whl", hash = "sha256:0c558d2cdffd8f4bbb30fc7134c74d2ca9a476f830bb053074498fbc86f41ed6", size = 8001587, upload-time = "2026-05-04T22:57:36.803Z" },
+ { url = "https://files.pythonhosted.org/packages/b2/6e/e90527eef33f309beb811cf7c982c3aeffcce8e3edb178baa4ca3ae4a6fa/cryptography-48.0.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:f5333311663ea94f75dd408665686aaf426563556bb5283554a3539177e03b8c", size = 4690433, upload-time = "2026-05-04T22:57:40.373Z" },
+ { url = "https://files.pythonhosted.org/packages/90/04/673510ed51ddff56575f306cf1617d80411ee76831ccd3097599140efdfe/cryptography-48.0.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:7995ef305d7165c3f11ae07f2517e5a4f1d5c18da1376a0a9ed496336b69e5f3", size = 4710620, upload-time = "2026-05-04T22:57:42.935Z" },
+ { url = "https://files.pythonhosted.org/packages/14/d5/e9c4ef932c8d800490c34d8bd589d64a31d5890e27ec9e9ad532be893294/cryptography-48.0.0-cp311-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:40ba1f85eaa6959837b1d51c9767e230e14612eea4ef110ee8854ada22da1bf5", size = 4696283, upload-time = "2026-05-04T22:57:45.294Z" },
+ { url = "https://files.pythonhosted.org/packages/0c/29/174b9dfb60b12d59ecfc6cfa04bc88c21b42a54f01b8aae09bb6e51e4c7f/cryptography-48.0.0-cp311-abi3-manylinux_2_28_ppc64le.whl", hash = "sha256:369a6348999f94bbd53435c894377b20ab95f25a9065c283570e70150d8abc3c", size = 5296573, upload-time = "2026-05-04T22:57:47.933Z" },
+ { url = "https://files.pythonhosted.org/packages/95/38/0d29a6fd7d0d1373f0c0c88a04ba20e359b257753ac497564cd660fc1d55/cryptography-48.0.0-cp311-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:a0e692c683f4df67815a2d258b324e66f4738bd7a96a218c826dce4f4bd05d8f", size = 4743677, upload-time = "2026-05-04T22:57:50.067Z" },
+ { url = "https://files.pythonhosted.org/packages/30/be/eef653013d5c63b6a490529e0316f9ac14a37602965d4903efed1399f32b/cryptography-48.0.0-cp311-abi3-manylinux_2_31_armv7l.whl", hash = "sha256:18349bbc56f4743c8b12dc32e2bccb2cf83ee8b69a3bba74ef8ae857e26b3d25", size = 4330808, upload-time = "2026-05-04T22:57:52.301Z" },
+ { url = "https://files.pythonhosted.org/packages/84/9e/500463e87abb7a0a0f9f256ec21123ecde0a7b5541a15e840ea54551fd81/cryptography-48.0.0-cp311-abi3-manylinux_2_34_aarch64.whl", hash = "sha256:7e8eac43dfca5c4cccc6dad9a80504436fca53bb9bc3100a2386d730fbe6b602", size = 4695941, upload-time = "2026-05-04T22:57:54.603Z" },
+ { url = "https://files.pythonhosted.org/packages/e3/dc/7303087450c2ec9e7fbb750e17c2abfbc658f23cbd0e54009509b7cc4091/cryptography-48.0.0-cp311-abi3-manylinux_2_34_ppc64le.whl", hash = "sha256:9ccdac7d40688ecb5a3b4a604b8a88c8002e3442d6c60aead1db2a89a041560c", size = 5252579, upload-time = "2026-05-04T22:57:57.207Z" },
+ { url = "https://files.pythonhosted.org/packages/d0/c0/7101d3b7215edcdc90c45da544961fd8ed2d6448f77577460fa75a8443f7/cryptography-48.0.0-cp311-abi3-manylinux_2_34_x86_64.whl", hash = "sha256:bd72e68b06bb1e96913f97dd4901119bc17f39d4586a5adf2d3e47bc2b9d58b5", size = 4743326, upload-time = "2026-05-04T22:57:59.535Z" },
+ { url = "https://files.pythonhosted.org/packages/ac/d8/5b833bad13016f562ab9d063d68199a4bd121d18458e439515601d3357ec/cryptography-48.0.0-cp311-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:59baa2cb386c4f0b9905bd6eb4c2a79a69a128408fd31d32ca4d7102d4156321", size = 4826672, upload-time = "2026-05-04T22:58:01.996Z" },
+ { url = "https://files.pythonhosted.org/packages/98/e1/7074eb8bf3c135558c73fc2bcf0f5633f912e6fb87e868a55c454080ef09/cryptography-48.0.0-cp311-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:9249e3cd978541d665967ac2cb2787fd6a62bddf1e75b3e347a594d7dacf4f74", size = 4972574, upload-time = "2026-05-04T22:58:03.968Z" },
+ { url = "https://files.pythonhosted.org/packages/04/70/e5a1b41d325f797f39427aa44ef8baf0be500065ab6d8e10369d850d4a4f/cryptography-48.0.0-cp311-abi3-win32.whl", hash = "sha256:9c459db21422be75e2809370b829a87eb37f74cd785fc4aa9ea1e5f43b47cda4", size = 3294868, upload-time = "2026-05-04T22:58:06.467Z" },
+ { url = "https://files.pythonhosted.org/packages/f4/ac/8ac51b4a5fc5932eb7ee5c517ba7dc8cd834f0048962b6b352f00f41ebf9/cryptography-48.0.0-cp311-abi3-win_amd64.whl", hash = "sha256:5b012212e08b8dd5edc78ef54da83dd9892fd9105323b3993eff6bea65dc21d7", size = 3817107, upload-time = "2026-05-04T22:58:08.845Z" },
+ { url = "https://files.pythonhosted.org/packages/6b/84/70e3feea9feea87fd7cbe77efb2712ae1e3e6edf10749dc6e95f4e60e455/cryptography-48.0.0-cp314-cp314t-macosx_10_9_universal2.whl", hash = "sha256:3cb07a3ed6431663cd321ea8a000a1314c74211f823e4177fefa2255e057d1ec", size = 7986556, upload-time = "2026-05-04T22:58:11.172Z" },
+ { url = "https://files.pythonhosted.org/packages/89/6e/18e07a618bb5442ba10cf4df16e99c071365528aa570dfcb8c02e25a303b/cryptography-48.0.0-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:8c7378637d7d88016fa6791c159f698b3d3eed28ebf844ac36b9dc04a14dae18", size = 4684776, upload-time = "2026-05-04T22:58:13.712Z" },
+ { url = "https://files.pythonhosted.org/packages/be/6a/4ea3b4c6c6759794d5ee2103c304a5076dc4b19ae1f9fe47dba439e159e9/cryptography-48.0.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:cc90c0b39b2e3c65ef52c804b72e3c58f8a04ab2a1871272798e5f9572c17d20", size = 4698121, upload-time = "2026-05-04T22:58:16.448Z" },
+ { url = "https://files.pythonhosted.org/packages/2f/59/6ff6ad6cae03bb887da2a5860b2c9805f8dac969ef01ce563336c49bd1d1/cryptography-48.0.0-cp314-cp314t-manylinux_2_28_aarch64.whl", hash = "sha256:76341972e1eff8b4bea859f09c0d3e64b96ce931b084f9b9b7db8ef364c30eff", size = 4690042, upload-time = "2026-05-04T22:58:18.544Z" },
+ { url = "https://files.pythonhosted.org/packages/ca/b4/fc334ed8cfd705aca282fe4d8f5ae64a8e0f74932e9feecb344610cf6e4d/cryptography-48.0.0-cp314-cp314t-manylinux_2_28_ppc64le.whl", hash = "sha256:55b7718303bf06a5753dcdccf2f3945cf18ad7bffde41b61226e4db31ab89a9c", size = 5282526, upload-time = "2026-05-04T22:58:20.75Z" },
+ { url = "https://files.pythonhosted.org/packages/11/08/9f8c5386cc4cd90d8255c7cdd0f5baf459a08502a09de30dc51f553d38dc/cryptography-48.0.0-cp314-cp314t-manylinux_2_28_x86_64.whl", hash = "sha256:a64697c641c7b1b2178e573cbc31c7c6684cd56883a478d75143dbb7118036db", size = 4733116, upload-time = "2026-05-04T22:58:23.627Z" },
+ { url = "https://files.pythonhosted.org/packages/b8/77/99307d7574045699f8805aa500fa0fb83422d115b5400a064ddd306d7750/cryptography-48.0.0-cp314-cp314t-manylinux_2_31_armv7l.whl", hash = "sha256:561215ea3879cb1cbbf272867e2efda62476f240fb58c64de6b393ae19246741", size = 4316030, upload-time = "2026-05-04T22:58:25.581Z" },
+ { url = "https://files.pythonhosted.org/packages/fd/36/a608b98337af3cb2aff4818e406649d30572b7031918b04c87d979495348/cryptography-48.0.0-cp314-cp314t-manylinux_2_34_aarch64.whl", hash = "sha256:ad64688338ed4bc1a6618076ba75fd7194a5f1797ac60b47afe926285adb3166", size = 4689640, upload-time = "2026-05-04T22:58:27.747Z" },
+ { url = "https://files.pythonhosted.org/packages/dd/a6/825010a291b4438aecc1f568bc428189fc1175515223632477c07dc0a6df/cryptography-48.0.0-cp314-cp314t-manylinux_2_34_ppc64le.whl", hash = "sha256:906cbf0670286c6e0044156bc7d4af9cbb0ef6db9f73e52c3ec56ba6bdde5336", size = 5237657, upload-time = "2026-05-04T22:58:29.848Z" },
+ { url = "https://files.pythonhosted.org/packages/b9/09/4e76a09b4caa29aad535ddc806f5d4c5d01885bd978bd984fbc6ca032cae/cryptography-48.0.0-cp314-cp314t-manylinux_2_34_x86_64.whl", hash = "sha256:ea8990436d914540a40ab24b6a77c0969695ed52f4a4874c5137ccf7045a7057", size = 4732362, upload-time = "2026-05-04T22:58:32.009Z" },
+ { url = "https://files.pythonhosted.org/packages/18/78/444fa04a77d0cb95f417dda20d450e13c56ba8e5220fc892a1658f44f882/cryptography-48.0.0-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:c18684a7f0cc9a3cb60328f496b8e3372def7c5d2df39ac267878b05565aaaae", size = 4819580, upload-time = "2026-05-04T22:58:34.254Z" },
+ { url = "https://files.pythonhosted.org/packages/38/85/ea67067c70a1fd4be2c63d35eeed82658023021affccc7b17705f8527dd2/cryptography-48.0.0-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:9be5aafa5736574f8f15f262adc81b2a9869e2cfe9014d52a44633905b40d52c", size = 4963283, upload-time = "2026-05-04T22:58:36.376Z" },
+ { url = "https://files.pythonhosted.org/packages/75/54/cc6d0f3deac3e81c7f847e8a189a12b6cdd65059b43dad25d4316abd849a/cryptography-48.0.0-cp314-cp314t-win32.whl", hash = "sha256:c17dfe85494deaeddc5ce251aebd1d60bbe6afc8b62071bb0b469431a000124f", size = 3270954, upload-time = "2026-05-04T22:58:38.791Z" },
+ { url = "https://files.pythonhosted.org/packages/49/67/cc947e288c0758a4e5473d1dcb743037ab7785541265a969240b8885441a/cryptography-48.0.0-cp314-cp314t-win_amd64.whl", hash = "sha256:27241b1dc9962e056062a8eef1991d02c3a24569c95975bd2322a8a52c6e5e12", size = 3797313, upload-time = "2026-05-04T22:58:40.746Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/63/61d4a4e1c6b6bab6ce1e213cd36a24c415d90e76d78c5eb8577c5541d2e8/cryptography-48.0.0-cp39-abi3-macosx_10_9_universal2.whl", hash = "sha256:58d00498e8933e4a194f3076aee1b4a97dfec1a6da444535755822fe5d8b0b86", size = 7983482, upload-time = "2026-05-04T22:58:43.769Z" },
+ { url = "https://files.pythonhosted.org/packages/d5/ac/f5b5995b87770c693e2596559ffafe195b4033a57f14a82268a2842953f3/cryptography-48.0.0-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl", hash = "sha256:614d0949f4790582d2cc25553abd09dd723025f0c0e7c67376a1d77196743d6e", size = 4683266, upload-time = "2026-05-04T22:58:46.064Z" },
+ { url = "https://files.pythonhosted.org/packages/ec/c6/8b14f67e18338fbc4adb76f66c001f5c3610b3e2d1837f268f47a347dbbb/cryptography-48.0.0-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl", hash = "sha256:7ce4bfae76319a532a2dc68f82cc32f5676ee792a983187dac07183690e5c66f", size = 4696228, upload-time = "2026-05-04T22:58:48.22Z" },
+ { url = "https://files.pythonhosted.org/packages/ea/73/f808fbae9514bd91b47875b003f13e284c8c6bdfd904b7944e803937eec1/cryptography-48.0.0-cp39-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:2eb992bbd4661238c5a397594c83f5b4dc2bc5b848c365c8f991b6780efcc5c7", size = 4689097, upload-time = "2026-05-04T22:58:50.9Z" },
+ { url = "https://files.pythonhosted.org/packages/93/01/d86632d7d28db8ae83221995752eeb6639ffb374c2d22955648cf8d52797/cryptography-48.0.0-cp39-abi3-manylinux_2_28_ppc64le.whl", hash = "sha256:22a5cb272895dce158b2cacdfdc3debd299019659f42947dbdac6f32d68fe832", size = 5283582, upload-time = "2026-05-04T22:58:53.017Z" },
+ { url = "https://files.pythonhosted.org/packages/02/e1/50edc7a50334807cc4791fc4a0ce7468b4a1416d9138eab358bfc9a3d70b/cryptography-48.0.0-cp39-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:2b4d59804e8408e2fea7d1fbaf218e5ec984325221db76e6a241a9abd6cdd95c", size = 4730479, upload-time = "2026-05-04T22:58:55.611Z" },
+ { url = "https://files.pythonhosted.org/packages/6f/af/99a582b1b1641ff5911ac559beb45097cf79efd4ead4657f578ef1af2d47/cryptography-48.0.0-cp39-abi3-manylinux_2_31_armv7l.whl", hash = "sha256:984a20b0f62a26f48a3396c72e4bc34c66e356d356bf370053066b3b6d54634a", size = 4326481, upload-time = "2026-05-04T22:58:57.607Z" },
+ { url = "https://files.pythonhosted.org/packages/90/ee/89aa26a06ef0a7d7611788ffd571a7c50e368cc6a4d5eef8b4884e866edb/cryptography-48.0.0-cp39-abi3-manylinux_2_34_aarch64.whl", hash = "sha256:5a5ed8fde7a1d09376ca0b40e68cd59c69fe23b1f9768bd5824f54681626032a", size = 4688713, upload-time = "2026-05-04T22:59:00.077Z" },
+ { url = "https://files.pythonhosted.org/packages/70/ba/bcb1b0bb7a33d4c7c0c4d4c7874b4a62ae4f56113a5f4baefa362dfb1f0f/cryptography-48.0.0-cp39-abi3-manylinux_2_34_ppc64le.whl", hash = "sha256:8cd666227ef7af430aa5914a9910e0ddd703e75f039cef0825cd0da71b6b711a", size = 5238165, upload-time = "2026-05-04T22:59:02.317Z" },
+ { url = "https://files.pythonhosted.org/packages/c9/70/ca4003b1ce5ca3dc3186ada51908c8a9b9ff7d5cab83cc0d43ee14ec144f/cryptography-48.0.0-cp39-abi3-manylinux_2_34_x86_64.whl", hash = "sha256:9071196d81abc88b3516ac8cdfad32e2b66dd4a5393a8e68a961e9161ddc6239", size = 4729947, upload-time = "2026-05-04T22:59:05.255Z" },
+ { url = "https://files.pythonhosted.org/packages/44/a0/4ec7cf774207905aef1a8d11c3750d5a1db805eb380ee4e16df317870128/cryptography-48.0.0-cp39-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:1e2d54c8be6152856a36f0882ab231e70f8ec7f14e93cf87db8a2ed056bf160c", size = 4822059, upload-time = "2026-05-04T22:59:07.802Z" },
+ { url = "https://files.pythonhosted.org/packages/1e/75/a2e55f99c16fcac7b5d6c1eb19ad8e00799854d6be5ca845f9259eae1681/cryptography-48.0.0-cp39-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:a5da777e32ffed6f85a7b2b3f7c5cbc88c146bfcd0a1d7baf5fcc6c52ee35dd4", size = 4960575, upload-time = "2026-05-04T22:59:09.851Z" },
+ { url = "https://files.pythonhosted.org/packages/b8/23/6e6f32143ab5d8b36ca848a502c4bcd477ae75b9e1677e3530d669062578/cryptography-48.0.0-cp39-abi3-win32.whl", hash = "sha256:77a2ccbbe917f6710e05ba9adaa25fb5075620bf3ea6fb751997875aff4ae4bd", size = 3279117, upload-time = "2026-05-04T22:59:12.019Z" },
+ { url = "https://files.pythonhosted.org/packages/9d/9a/0fea98a70cf1749d41d738836f6349d97945f7c89433a259a6c2642eefeb/cryptography-48.0.0-cp39-abi3-win_amd64.whl", hash = "sha256:16cd65b9330583e4619939b3a3843eec1e6e789744bb01e7c7e2e62e33c239c8", size = 3792100, upload-time = "2026-05-04T22:59:14.884Z" },
]
[[package]]
name = "cyclopts"
-version = "4.2.5"
+version = "4.12.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "attrs" },
@@ -265,18 +262,9 @@ dependencies = [
{ name = "rich" },
{ name = "rich-rst" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/94/f0/5a83ac365800969552a7eb261b03860dea38647fb6cc31574bdbcdc9f0f5/cyclopts-4.2.5.tar.gz", hash = "sha256:91aff5da5b8b841ccb32b5142c2d12fd93678fbc9eba7ef7319452323e24d6d4", size = 149497, upload-time = "2025-11-22T02:33:37.526Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/a4/c3/d3f095120329616cc364af2bedcffd518d4db18c978f2f6c892d29e6af2f/cyclopts-4.12.0.tar.gz", hash = "sha256:86bfb5b35cb078decc1cca6c1be41f9a0e6202dc43b4f6056d5cfc6d1f4a69d1", size = 176123, upload-time = "2026-05-13T13:26:31.243Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/b6/00/a9b81bdba88e2904602e970e46ffd18b6a833d902f18d91bdce6fc271c49/cyclopts-4.2.5-py3-none-any.whl", hash = "sha256:361be316ce7f6ce674cad8d34bf6c5e39c34daaeceae40632a55b599472975c7", size = 185196, upload-time = "2025-11-22T02:33:36.103Z" },
-]
-
-[[package]]
-name = "diskcache"
-version = "5.6.3"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/3f/21/1c1ffc1a039ddcc459db43cc108658f32c57d271d7289a2794e401d0fdb6/diskcache-5.6.3.tar.gz", hash = "sha256:2c3a3fa2743d8535d832ec61c2054a1641f41775aa7c556758a109941e33e4fc", size = 67916, upload-time = "2023-08-31T06:12:00.316Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/3f/27/4570e78fc0bf5ea0ca45eb1de3818a23787af9b390c0b0a0033a1b8236f9/diskcache-5.6.3-py3-none-any.whl", hash = "sha256:5e31b2d5fbad117cc363ebaf6b689474db18a1f6438bc82358b024abd4c2ca19", size = 45550, upload-time = "2023-08-31T06:11:58.822Z" },
+ { url = "https://files.pythonhosted.org/packages/4e/d0/17b6b7d5f64dea337a7a409a1e4e0eeceda724046b9acd158fd1aa2f2328/cyclopts-4.12.0-py3-none-any.whl", hash = "sha256:ee03d2b9ef790d866cb3823a7e54b2be5252c82d34536579846fce068b30c38f", size = 213706, upload-time = "2026-05-13T13:26:29.744Z" },
]
[[package]]
@@ -290,20 +278,20 @@ wheels = [
[[package]]
name = "docstring-parser"
-version = "0.17.0"
+version = "0.18.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/b2/9d/c3b43da9515bd270df0f80548d9944e389870713cc1fe2b8fb35fe2bcefd/docstring_parser-0.17.0.tar.gz", hash = "sha256:583de4a309722b3315439bb31d64ba3eebada841f2e2cee23b99df001434c912", size = 27442, upload-time = "2025-07-21T07:35:01.868Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/e0/4d/f332313098c1de1b2d2ff91cf2674415cc7cddab2ca1b01ae29774bd5fdf/docstring_parser-0.18.0.tar.gz", hash = "sha256:292510982205c12b1248696f44959db3cdd1740237a968ea1e2e7a900eeb2015", size = 29341, upload-time = "2026-04-14T04:09:19.867Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/55/e2/2537ebcff11c1ee1ff17d8d0b6f4db75873e3b0fb32c2d4a2ee31ecb310a/docstring_parser-0.17.0-py3-none-any.whl", hash = "sha256:cf2569abd23dce8099b300f9b4fa8191e9582dda731fd533daf54c4551658708", size = 36896, upload-time = "2025-07-21T07:35:00.684Z" },
+ { url = "https://files.pythonhosted.org/packages/a7/5f/ed01f9a3cdffbd5a008556fc7b2a08ddb1cc6ace7effa7340604b1d16699/docstring_parser-0.18.0-py3-none-any.whl", hash = "sha256:b3fcbed555c47d8479be0796ef7e19c2670d428d72e96da63f3a40122860374b", size = 22484, upload-time = "2026-04-14T04:09:18.638Z" },
]
[[package]]
name = "docutils"
-version = "0.22.2"
+version = "0.22.4"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/4a/c0/89fe6215b443b919cb98a5002e107cb5026854ed1ccb6b5833e0768419d1/docutils-0.22.2.tar.gz", hash = "sha256:9fdb771707c8784c8f2728b67cb2c691305933d68137ef95a75db5f4dfbc213d", size = 2289092, upload-time = "2025-09-20T17:55:47.994Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/ae/b6/03bb70946330e88ffec97aefd3ea75ba575cb2e762061e0e62a213befee8/docutils-0.22.4.tar.gz", hash = "sha256:4db53b1fde9abecbb74d91230d32ab626d94f6badfc575d6db9194a49df29968", size = 2291750, upload-time = "2025-12-18T19:00:26.443Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/66/dd/f95350e853a4468ec37478414fc04ae2d61dad7a947b3015c3dcc51a09b9/docutils-0.22.2-py3-none-any.whl", hash = "sha256:b0e98d679283fc3bb0ead8a5da7f501baa632654e7056e9c5846842213d674d8", size = 632667, upload-time = "2025-09-20T17:55:43.052Z" },
+ { url = "https://files.pythonhosted.org/packages/02/10/5da547df7a391dcde17f59520a231527b8571e6f46fc8efb02ccb370ab12/docutils-0.22.4-py3-none-any.whl", hash = "sha256:d0013f540772d1420576855455d050a2180186c91c15779301ac2ccb3eeb68de", size = 633196, upload-time = "2025-12-18T19:00:18.077Z" },
]
[[package]]
@@ -321,59 +309,56 @@ wheels = [
[[package]]
name = "exceptiongroup"
-version = "1.3.0"
+version = "1.3.1"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "typing-extensions", marker = "python_full_version < '3.13'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/0b/9f/a65090624ecf468cdca03533906e7c69ed7588582240cfe7cc9e770b50eb/exceptiongroup-1.3.0.tar.gz", hash = "sha256:b241f5885f560bc56a59ee63ca4c6a8bfa46ae4ad651af316d4e81817bb9fd88", size = 29749, upload-time = "2025-05-10T17:42:51.123Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/50/79/66800aadf48771f6b62f7eb014e352e5d06856655206165d775e675a02c9/exceptiongroup-1.3.1.tar.gz", hash = "sha256:8b412432c6055b0b7d14c310000ae93352ed6754f70fa8f7c34141f91c4e3219", size = 30371, upload-time = "2025-11-21T23:01:54.787Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/36/f4/c6e662dade71f56cd2f3735141b265c3c79293c109549c1e6933b0651ffc/exceptiongroup-1.3.0-py3-none-any.whl", hash = "sha256:4d111e6e0c13d0644cad6ddaa7ed0261a0b36971f6d23e7ec9b4b9097da78a10", size = 16674, upload-time = "2025-05-10T17:42:49.33Z" },
-]
-
-[[package]]
-name = "fakeredis"
-version = "2.33.0"
-source = { registry = "https://pypi.org/simple" }
-dependencies = [
- { name = "redis" },
- { name = "sortedcontainers" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/5f/f9/57464119936414d60697fcbd32f38909bb5688b616ae13de6e98384433e0/fakeredis-2.33.0.tar.gz", hash = "sha256:d7bc9a69d21df108a6451bbffee23b3eba432c21a654afc7ff2d295428ec5770", size = 175187, upload-time = "2025-12-16T19:45:52.269Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/6e/78/a850fed8aeef96d4a99043c90b818b2ed5419cd5b24a4049fd7cfb9f1471/fakeredis-2.33.0-py3-none-any.whl", hash = "sha256:de535f3f9ccde1c56672ab2fdd6a8efbc4f2619fc2f1acc87b8737177d71c965", size = 119605, upload-time = "2025-12-16T19:45:51.08Z" },
-]
-
-[package.optional-dependencies]
-lua = [
- { name = "lupa" },
+ { url = "https://files.pythonhosted.org/packages/8a/0e/97c33bf5009bdbac74fd2beace167cab3f978feb69cc36f1ef79360d6c4e/exceptiongroup-1.3.1-py3-none-any.whl", hash = "sha256:a7a39a3bd276781e98394987d3a5701d0c4edffb633bb7a5144577f82c773598", size = 16740, upload-time = "2025-11-21T23:01:53.443Z" },
]
[[package]]
name = "fastmcp"
-version = "2.14.0"
+version = "3.2.4"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "authlib" },
{ name = "cyclopts" },
{ name = "exceptiongroup" },
+ { name = "griffelib" },
{ name = "httpx" },
+ { name = "jsonref" },
{ name = "jsonschema-path" },
{ name = "mcp" },
{ name = "openapi-pydantic" },
+ { name = "opentelemetry-api" },
+ { name = "packaging" },
{ name = "platformdirs" },
- { name = "py-key-value-aio", extra = ["disk", "keyring", "memory"] },
+ { name = "py-key-value-aio", extra = ["filetree", "keyring", "memory"] },
{ name = "pydantic", extra = ["email"] },
- { name = "pydocket" },
{ name = "pyperclip" },
{ name = "python-dotenv" },
+ { name = "pyyaml" },
{ name = "rich" },
+ { name = "uncalled-for" },
{ name = "uvicorn" },
+ { name = "watchfiles" },
{ name = "websockets" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/35/50/9bb042a2d290ccadb35db3580ac507f192e1a39c489eb8faa167cd5e3b57/fastmcp-2.14.0.tar.gz", hash = "sha256:c1f487b36a3e4b043dbf3330e588830047df2e06f8ef0920d62dfb34d0905727", size = 8232562, upload-time = "2025-12-11T23:04:27.134Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/9c/13/29544fbc6dfe45ea38046af0067311e0bad7acc7d1f2ad38bb08f2409fe2/fastmcp-3.2.4.tar.gz", hash = "sha256:083ecb75b44a4169e7fc0f632f94b781bdb0ff877c6b35b9877cbb566fd4d4d1", size = 28746127, upload-time = "2026-04-14T01:42:24.174Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/54/73/b5656172a6beb2eacec95f04403ddea1928e4b22066700fd14780f8f45d1/fastmcp-2.14.0-py3-none-any.whl", hash = "sha256:7b374c0bcaf1ef1ef46b9255ea84c607f354291eaf647ff56a47c69f5ec0c204", size = 398965, upload-time = "2025-12-11T23:04:25.587Z" },
+ { url = "https://files.pythonhosted.org/packages/cf/76/b310d52fa0e30d39bd937eb58ec2c1f1ea1b5f519f0575e9dd9612f01deb/fastmcp-3.2.4-py3-none-any.whl", hash = "sha256:e6c9c429171041455e47ab94bb3f83c4657622a0ec28922f6940053959bd58a9", size = 728599, upload-time = "2026-04-14T01:42:26.85Z" },
+]
+
+[[package]]
+name = "griffelib"
+version = "2.0.2"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/9d/82/74f4a3310cdabfbb10da554c3a672847f1ed33c6f61dd472681ce7f1fe67/griffelib-2.0.2.tar.gz", hash = "sha256:3cf20b3bc470e83763ffbf236e0076b1211bac1bc67de13daf494640f2de707e", size = 166461, upload-time = "2026-03-27T11:34:51.091Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/11/8c/c9138d881c79aa0ea9ed83cbd58d5ca75624378b38cee225dcf5c42cc91f/griffelib-2.0.2-py3-none-any.whl", hash = "sha256:925c857658fb1ba40c0772c37acbc2ab650bd794d9c1b9726922e36ea4117ea1", size = 142357, upload-time = "2026-03-27T11:34:46.275Z" },
]
[[package]]
@@ -415,20 +400,20 @@ wheels = [
[[package]]
name = "httpx-sse"
-version = "0.4.1"
+version = "0.4.3"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/6e/fa/66bd985dd0b7c109a3bcb89272ee0bfb7e2b4d06309ad7b38ff866734b2a/httpx_sse-0.4.1.tar.gz", hash = "sha256:8f44d34414bc7b21bf3602713005c5df4917884f76072479b21f68befa4ea26e", size = 12998, upload-time = "2025-06-24T13:21:05.71Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/0f/4c/751061ffa58615a32c31b2d82e8482be8dd4a89154f003147acee90f2be9/httpx_sse-0.4.3.tar.gz", hash = "sha256:9b1ed0127459a66014aec3c56bebd93da3c1bc8bb6618c8082039a44889a755d", size = 15943, upload-time = "2025-10-10T21:48:22.271Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/25/0a/6269e3473b09aed2dab8aa1a600c70f31f00ae1349bee30658f7e358a159/httpx_sse-0.4.1-py3-none-any.whl", hash = "sha256:cba42174344c3a5b06f255ce65b350880f962d99ead85e776f23c6618a377a37", size = 8054, upload-time = "2025-06-24T13:21:04.772Z" },
+ { url = "https://files.pythonhosted.org/packages/d2/fd/6668e5aec43ab844de6fc74927e155a3b37bf40d7c3790e49fc0406b6578/httpx_sse-0.4.3-py3-none-any.whl", hash = "sha256:0ac1c9fe3c0afad2e0ebb25a934a59f4c7823b60792691f779fad2c5568830fc", size = 8960, upload-time = "2025-10-10T21:48:21.158Z" },
]
[[package]]
name = "idna"
-version = "3.10"
+version = "3.15"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/f1/70/7703c29685631f5a7590aa73f1f1d3fa9a380e654b86af429e0934a32f7d/idna-3.10.tar.gz", hash = "sha256:12f65c9b470abda6dc35cf8e63cc574b1c52b11df2c86030af0ac09b01b13ea9", size = 190490, upload-time = "2024-09-15T18:07:39.745Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/82/77/7b3966d0b9d1d31a36ddf1746926a11dface89a83409bf1483f0237aa758/idna-3.15.tar.gz", hash = "sha256:ca962446ea538f7092a95e057da437618e886f4d349216d2b1e294abfdb65fdc", size = 199245, upload-time = "2026-05-12T22:45:57.011Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/76/c6/c88e154df9c4e1a2a66ccf0005a88dfb2650c1dffb6f5ce603dfbd452ce3/idna-3.10-py3-none-any.whl", hash = "sha256:946d195a0d259cbba61165e88e65941f16e9b36ea6ddb97f00452bae8b1287d3", size = 70442, upload-time = "2024-09-15T18:07:37.964Z" },
+ { url = "https://files.pythonhosted.org/packages/d2/23/408243171aa9aaba178d3e2559159c24c1171a641aa83b67bdd3394ead8e/idna-3.15-py3-none-any.whl", hash = "sha256:048adeaf8c2d788c40fee287673ccaa74c24ffd8dcf09ffa555a2fbb59f10ac8", size = 72340, upload-time = "2026-05-12T22:45:55.733Z" },
]
[[package]]
@@ -466,23 +451,23 @@ wheels = [
[[package]]
name = "jaraco-context"
-version = "6.0.1"
+version = "6.1.2"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/df/ad/f3777b81bf0b6e7bc7514a1656d3e637b2e8e15fab2ce3235730b3e7a4e6/jaraco_context-6.0.1.tar.gz", hash = "sha256:9bae4ea555cf0b14938dc0aee7c9f32ed303aa20a3b73e7dc80111628792d1b3", size = 13912, upload-time = "2024-08-20T03:39:27.358Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/af/50/4763cd07e722bb6285316d390a164bc7e479db9d90daa769f22578f698b4/jaraco_context-6.1.2.tar.gz", hash = "sha256:f1a6c9d391e661cc5b8d39861ff077a7dc24dc23833ccee564b234b81c82dfe3", size = 16801, upload-time = "2026-03-20T22:13:33.922Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/ff/db/0c52c4cf5e4bd9f5d7135ec7669a3a767af21b3a308e1ed3674881e52b62/jaraco.context-6.0.1-py3-none-any.whl", hash = "sha256:f797fc481b490edb305122c9181830a3a5b76d84ef6d1aef2fb9b47ab956f9e4", size = 6825, upload-time = "2024-08-20T03:39:25.966Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/58/bc8954bda5fcda97bd7c19be11b85f91973d67a706ed4a3aec33e7de22db/jaraco_context-6.1.2-py3-none-any.whl", hash = "sha256:bf8150b79a2d5d91ae48629d8b427a8f7ba0e1097dd6202a9059f29a36379535", size = 7871, upload-time = "2026-03-20T22:13:32.808Z" },
]
[[package]]
name = "jaraco-functools"
-version = "4.3.0"
+version = "4.4.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "more-itertools" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/f7/ed/1aa2d585304ec07262e1a83a9889880701079dde796ac7b1d1826f40c63d/jaraco_functools-4.3.0.tar.gz", hash = "sha256:cfd13ad0dd2c47a3600b439ef72d8615d482cedcff1632930d6f28924d92f294", size = 19755, upload-time = "2025-08-18T20:05:09.91Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/0f/27/056e0638a86749374d6f57d0b0db39f29509cce9313cf91bdc0ac4d91084/jaraco_functools-4.4.0.tar.gz", hash = "sha256:da21933b0417b89515562656547a77b4931f98176eb173644c0d35032a33d6bb", size = 19943, upload-time = "2025-12-21T09:29:43.6Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/b4/09/726f168acad366b11e420df31bf1c702a54d373a83f968d94141a8c3fde0/jaraco_functools-4.3.0-py3-none-any.whl", hash = "sha256:227ff8ed6f7b8f62c56deff101545fa7543cf2c8e7b82a7c2116e672f29c26e8", size = 10408, upload-time = "2025-08-18T20:05:08.69Z" },
+ { url = "https://files.pythonhosted.org/packages/fd/c4/813bb09f0985cb21e959f21f2464169eca882656849adf727ac7bb7e1767/jaraco_functools-4.4.0-py3-none-any.whl", hash = "sha256:9eec1e36f45c818d9bf307c8948eb03b2b56cd44087b3cdc989abca1f20b9176", size = 10481, upload-time = "2025-12-21T09:29:42.27Z" },
]
[[package]]
@@ -494,9 +479,30 @@ wheels = [
{ url = "https://files.pythonhosted.org/packages/b2/a3/e137168c9c44d18eff0376253da9f1e9234d0239e0ee230d2fee6cea8e55/jeepney-0.9.0-py3-none-any.whl", hash = "sha256:97e5714520c16fc0a45695e5365a2e11b81ea79bba796e26f9f1d178cb182683", size = 49010, upload-time = "2025-02-27T18:51:00.104Z" },
]
+[[package]]
+name = "joserfc"
+version = "1.6.5"
+source = { registry = "https://pypi.org/simple" }
+dependencies = [
+ { name = "cryptography" },
+]
+sdist = { url = "https://files.pythonhosted.org/packages/3b/dc/5f768c2e391e9afabe5d18e3221346deb5fb6338565f1ccc9e7c6d7befdd/joserfc-1.6.5.tar.gz", hash = "sha256:1482a7db78fb4602e44ed89e51b599d052e091288c7c532c5b694e20149dec48", size = 231881, upload-time = "2026-05-06T04:58:13.408Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/54/3b/ad1cb22e75c963b1f07c8a2329bf47227ce7e4361df5eb2fb101b2ce33ef/joserfc-1.6.5-py3-none-any.whl", hash = "sha256:e9878a0f8243fe7b95e11fdda81374ca9f7a689e302751579d3dfdeec559675e", size = 70464, upload-time = "2026-05-06T04:58:11.668Z" },
+]
+
+[[package]]
+name = "jsonref"
+version = "1.1.0"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/aa/0d/c1f3277e90ccdb50d33ed5ba1ec5b3f0a242ed8c1b1a85d3afeb68464dca/jsonref-1.1.0.tar.gz", hash = "sha256:32fe8e1d85af0fdefbebce950af85590b22b60f9e95443176adbde4e1ecea552", size = 8814, upload-time = "2023-01-16T16:10:04.455Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/0c/ec/e1db9922bceb168197a558a2b8c03a7963f1afe93517ddd3cf99f202f996/jsonref-1.1.0-py3-none-any.whl", hash = "sha256:590dc7773df6c21cbf948b5dac07a72a251db28b0238ceecce0a2abfa8ec30a9", size = 9425, upload-time = "2023-01-16T16:10:02.255Z" },
+]
+
[[package]]
name = "jsonschema"
-version = "4.25.1"
+version = "4.26.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "attrs" },
@@ -504,24 +510,23 @@ dependencies = [
{ name = "referencing" },
{ name = "rpds-py" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/74/69/f7185de793a29082a9f3c7728268ffb31cb5095131a9c139a74078e27336/jsonschema-4.25.1.tar.gz", hash = "sha256:e4a9655ce0da0c0b67a085847e00a3a51449e1157f4f75e9fb5aa545e122eb85", size = 357342, upload-time = "2025-08-18T17:03:50.038Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/b3/fc/e067678238fa451312d4c62bf6e6cf5ec56375422aee02f9cb5f909b3047/jsonschema-4.26.0.tar.gz", hash = "sha256:0c26707e2efad8aa1bfc5b7ce170f3fccc2e4918ff85989ba9ffa9facb2be326", size = 366583, upload-time = "2026-01-07T13:41:07.246Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/bf/9c/8c95d856233c1f82500c2450b8c68576b4cf1c871db3afac5c34ff84e6fd/jsonschema-4.25.1-py3-none-any.whl", hash = "sha256:3fba0169e345c7175110351d456342c364814cfcf3b964ba4587f22915230a63", size = 90040, upload-time = "2025-08-18T17:03:48.373Z" },
+ { url = "https://files.pythonhosted.org/packages/69/90/f63fb5873511e014207a475e2bb4e8b2e570d655b00ac19a9a0ca0a385ee/jsonschema-4.26.0-py3-none-any.whl", hash = "sha256:d489f15263b8d200f8387e64b4c3a75f06629559fb73deb8fdfb525f2dab50ce", size = 90630, upload-time = "2026-01-07T13:41:05.306Z" },
]
[[package]]
name = "jsonschema-path"
-version = "0.3.4"
+version = "0.4.6"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "pathable" },
{ name = "pyyaml" },
{ name = "referencing" },
- { name = "requests" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/6e/45/41ebc679c2a4fced6a722f624c18d658dee42612b83ea24c1caf7c0eb3a8/jsonschema_path-0.3.4.tar.gz", hash = "sha256:8365356039f16cc65fddffafda5f58766e34bebab7d6d105616ab52bc4297001", size = 11159, upload-time = "2025-01-24T14:33:16.547Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/01/86/cfee6dd25843bec0760f456599a4f7e7e40221a934b9229fda0662c859bc/jsonschema_path-0.4.6.tar.gz", hash = "sha256:c89eb635f4d497c9ac328eeff359c489755838806a7d033510a692e9576f5c4b", size = 15302, upload-time = "2026-04-27T18:57:08.412Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/cb/58/3485da8cb93d2f393bce453adeef16896751f14ba3e2024bc21dc9597646/jsonschema_path-0.3.4-py3-none-any.whl", hash = "sha256:f502191fdc2b22050f9a81c9237be9d27145b9001c55842bece5e94e382e52f8", size = 14810, upload-time = "2025-01-24T14:33:14.652Z" },
+ { url = "https://files.pythonhosted.org/packages/6c/43/3d3065c05a04bb550c143bfbb8e4fd7022cd327e1082bf257bac74923783/jsonschema_path-0.4.6-py3-none-any.whl", hash = "sha256:451354b5311fa955c3144e6e4e255388c751c0121c5570ec5bb9291dd42d08c9", size = 19565, upload-time = "2026-04-27T18:57:06.792Z" },
]
[[package]]
@@ -553,73 +558,21 @@ wheels = [
{ url = "https://files.pythonhosted.org/packages/81/db/e655086b7f3a705df045bf0933bdd9c2f79bb3c97bfef1384598bb79a217/keyring-25.7.0-py3-none-any.whl", hash = "sha256:be4a0b195f149690c166e850609a477c532ddbfbaed96a404d4e43f8d5e2689f", size = 39160, upload-time = "2025-11-16T16:26:08.402Z" },
]
-[[package]]
-name = "lupa"
-version = "2.6"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/b8/1c/191c3e6ec6502e3dbe25a53e27f69a5daeac3e56de1f73c0138224171ead/lupa-2.6.tar.gz", hash = "sha256:9a770a6e89576be3447668d7ced312cd6fd41d3c13c2462c9dc2c2ab570e45d9", size = 7240282, upload-time = "2025-10-24T07:20:29.738Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/94/86/ce243390535c39d53ea17ccf0240815e6e457e413e40428a658ea4ee4b8d/lupa-2.6-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:47ce718817ef1cc0c40d87c3d5ae56a800d61af00fbc0fad1ca9be12df2f3b56", size = 951707, upload-time = "2025-10-24T07:18:03.884Z" },
- { url = "https://files.pythonhosted.org/packages/86/85/cedea5e6cbeb54396fdcc55f6b741696f3f036d23cfaf986d50d680446da/lupa-2.6-cp312-cp312-macosx_11_0_universal2.whl", hash = "sha256:7aba985b15b101495aa4b07112cdc08baa0c545390d560ad5cfde2e9e34f4d58", size = 1916703, upload-time = "2025-10-24T07:18:05.6Z" },
- { url = "https://files.pythonhosted.org/packages/24/be/3d6b5f9a8588c01a4d88129284c726017b2089f3a3fd3ba8bd977292fea0/lupa-2.6-cp312-cp312-macosx_11_0_x86_64.whl", hash = "sha256:b766f62f95b2739f2248977d29b0722e589dcf4f0ccfa827ccbd29f0148bd2e5", size = 985152, upload-time = "2025-10-24T07:18:08.561Z" },
- { url = "https://files.pythonhosted.org/packages/eb/23/9f9a05beee5d5dce9deca4cb07c91c40a90541fc0a8e09db4ee670da550f/lupa-2.6-cp312-cp312-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl", hash = "sha256:00a934c23331f94cb51760097ebfab14b005d55a6b30a2b480e3c53dd2fa290d", size = 1159599, upload-time = "2025-10-24T07:18:10.346Z" },
- { url = "https://files.pythonhosted.org/packages/40/4e/e7c0583083db9d7f1fd023800a9767d8e4391e8330d56c2373d890ac971b/lupa-2.6-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:21de9f38bd475303e34a042b7081aabdf50bd9bafd36ce4faea2f90fd9f15c31", size = 1038686, upload-time = "2025-10-24T07:18:12.112Z" },
- { url = "https://files.pythonhosted.org/packages/1c/9f/5a4f7d959d4feba5e203ff0c31889e74d1ca3153122be4a46dca7d92bf7c/lupa-2.6-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:cf3bda96d3fc41237e964a69c23647d50d4e28421111360274d4799832c560e9", size = 2071956, upload-time = "2025-10-24T07:18:14.572Z" },
- { url = "https://files.pythonhosted.org/packages/92/34/2f4f13ca65d01169b1720176aedc4af17bc19ee834598c7292db232cb6dc/lupa-2.6-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:5a76ead245da54801a81053794aa3975f213221f6542d14ec4b859ee2e7e0323", size = 1057199, upload-time = "2025-10-24T07:18:16.379Z" },
- { url = "https://files.pythonhosted.org/packages/35/2a/5f7d2eebec6993b0dcd428e0184ad71afb06a45ba13e717f6501bfed1da3/lupa-2.6-cp312-cp312-musllinux_1_2_i686.whl", hash = "sha256:8dd0861741caa20886ddbda0a121d8e52fb9b5bb153d82fa9bba796962bf30e8", size = 1173693, upload-time = "2025-10-24T07:18:18.153Z" },
- { url = "https://files.pythonhosted.org/packages/e4/29/089b4d2f8e34417349af3904bb40bec40b65c8731f45e3fd8d497ca573e5/lupa-2.6-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:239e63948b0b23023f81d9a19a395e768ed3da6a299f84e7963b8f813f6e3f9c", size = 2164394, upload-time = "2025-10-24T07:18:20.403Z" },
- { url = "https://files.pythonhosted.org/packages/f3/1b/79c17b23c921f81468a111cad843b076a17ef4b684c4a8dff32a7969c3f0/lupa-2.6-cp312-cp312-win32.whl", hash = "sha256:325894e1099499e7a6f9c351147661a2011887603c71086d36fe0f964d52d1ce", size = 1420647, upload-time = "2025-10-24T07:18:23.368Z" },
- { url = "https://files.pythonhosted.org/packages/b8/15/5121e68aad3584e26e1425a5c9a79cd898f8a152292059e128c206ee817c/lupa-2.6-cp312-cp312-win_amd64.whl", hash = "sha256:c735a1ce8ee60edb0fe71d665f1e6b7c55c6021f1d340eb8c865952c602cd36f", size = 1688529, upload-time = "2025-10-24T07:18:25.523Z" },
- { url = "https://files.pythonhosted.org/packages/28/1d/21176b682ca5469001199d8b95fa1737e29957a3d185186e7a8b55345f2e/lupa-2.6-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:663a6e58a0f60e7d212017d6678639ac8df0119bc13c2145029dcba084391310", size = 947232, upload-time = "2025-10-24T07:18:27.878Z" },
- { url = "https://files.pythonhosted.org/packages/ce/4c/d327befb684660ca13cf79cd1f1d604331808f9f1b6fb6bf57832f8edf80/lupa-2.6-cp313-cp313-macosx_11_0_universal2.whl", hash = "sha256:d1f5afda5c20b1f3217a80e9bc1b77037f8a6eb11612fd3ada19065303c8f380", size = 1908625, upload-time = "2025-10-24T07:18:29.944Z" },
- { url = "https://files.pythonhosted.org/packages/66/8e/ad22b0a19454dfd08662237a84c792d6d420d36b061f239e084f29d1a4f3/lupa-2.6-cp313-cp313-macosx_11_0_x86_64.whl", hash = "sha256:26f2b3c085fe76e9119e48c1013c1cccdc1f51585d456858290475aa38e7089e", size = 981057, upload-time = "2025-10-24T07:18:31.553Z" },
- { url = "https://files.pythonhosted.org/packages/5c/48/74859073ab276bd0566c719f9ca0108b0cfc1956ca0d68678d117d47d155/lupa-2.6-cp313-cp313-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl", hash = "sha256:60d2f902c7b96fb8ab98493dcff315e7bb4d0b44dc9dd76eb37de575025d5685", size = 1156227, upload-time = "2025-10-24T07:18:33.981Z" },
- { url = "https://files.pythonhosted.org/packages/09/6c/0e9ded061916877253c2266074060eb71ed99fb21d73c8c114a76725bce2/lupa-2.6-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:a02d25dee3a3250967c36590128d9220ae02f2eda166a24279da0b481519cbff", size = 1035752, upload-time = "2025-10-24T07:18:36.32Z" },
- { url = "https://files.pythonhosted.org/packages/dd/ef/f8c32e454ef9f3fe909f6c7d57a39f950996c37a3deb7b391fec7903dab7/lupa-2.6-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:6eae1ee16b886b8914ff292dbefbf2f48abfbdee94b33a88d1d5475e02423203", size = 2069009, upload-time = "2025-10-24T07:18:38.072Z" },
- { url = "https://files.pythonhosted.org/packages/53/dc/15b80c226a5225815a890ee1c11f07968e0aba7a852df41e8ae6fe285063/lupa-2.6-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:b0edd5073a4ee74ab36f74fe61450148e6044f3952b8d21248581f3c5d1a58be", size = 1056301, upload-time = "2025-10-24T07:18:40.165Z" },
- { url = "https://files.pythonhosted.org/packages/31/14/2086c1425c985acfb30997a67e90c39457122df41324d3c179d6ee2292c6/lupa-2.6-cp313-cp313-musllinux_1_2_i686.whl", hash = "sha256:0c53ee9f22a8a17e7d4266ad48e86f43771951797042dd51d1494aaa4f5f3f0a", size = 1170673, upload-time = "2025-10-24T07:18:42.426Z" },
- { url = "https://files.pythonhosted.org/packages/10/e5/b216c054cf86576c0191bf9a9f05de6f7e8e07164897d95eea0078dca9b2/lupa-2.6-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:de7c0f157a9064a400d828789191a96da7f4ce889969a588b87ec80de9b14772", size = 2162227, upload-time = "2025-10-24T07:18:46.112Z" },
- { url = "https://files.pythonhosted.org/packages/59/2f/33ecb5bedf4f3bc297ceacb7f016ff951331d352f58e7e791589609ea306/lupa-2.6-cp313-cp313-win32.whl", hash = "sha256:ee9523941ae0a87b5b703417720c5d78f72d2f5bc23883a2ea80a949a3ed9e75", size = 1419558, upload-time = "2025-10-24T07:18:48.371Z" },
- { url = "https://files.pythonhosted.org/packages/f9/b4/55e885834c847ea610e111d87b9ed4768f0afdaeebc00cd46810f25029f6/lupa-2.6-cp313-cp313-win_amd64.whl", hash = "sha256:b1335a5835b0a25ebdbc75cf0bda195e54d133e4d994877ef025e218c2e59db9", size = 1683424, upload-time = "2025-10-24T07:18:50.976Z" },
- { url = "https://files.pythonhosted.org/packages/66/9d/d9427394e54d22a35d1139ef12e845fd700d4872a67a34db32516170b746/lupa-2.6-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:dcb6d0a3264873e1653bc188499f48c1fb4b41a779e315eba45256cfe7bc33c1", size = 953818, upload-time = "2025-10-24T07:18:53.378Z" },
- { url = "https://files.pythonhosted.org/packages/10/41/27bbe81953fb2f9ecfced5d9c99f85b37964cfaf6aa8453bb11283983721/lupa-2.6-cp314-cp314-macosx_11_0_universal2.whl", hash = "sha256:a37e01f2128f8c36106726cb9d360bac087d58c54b4522b033cc5691c584db18", size = 1915850, upload-time = "2025-10-24T07:18:55.259Z" },
- { url = "https://files.pythonhosted.org/packages/a3/98/f9ff60db84a75ba8725506bbf448fb085bc77868a021998ed2a66d920568/lupa-2.6-cp314-cp314-macosx_11_0_x86_64.whl", hash = "sha256:458bd7e9ff3c150b245b0fcfbb9bd2593d1152ea7f0a7b91c1d185846da033fe", size = 982344, upload-time = "2025-10-24T07:18:57.05Z" },
- { url = "https://files.pythonhosted.org/packages/41/f7/f39e0f1c055c3b887d86b404aaf0ca197b5edfd235a8b81b45b25bac7fc3/lupa-2.6-cp314-cp314-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl", hash = "sha256:052ee82cac5206a02df77119c325339acbc09f5ce66967f66a2e12a0f3211cad", size = 1156543, upload-time = "2025-10-24T07:18:59.251Z" },
- { url = "https://files.pythonhosted.org/packages/9e/9c/59e6cffa0d672d662ae17bd7ac8ecd2c89c9449dee499e3eb13ca9cd10d9/lupa-2.6-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:96594eca3c87dd07938009e95e591e43d554c1dbd0385be03c100367141db5a8", size = 1047974, upload-time = "2025-10-24T07:19:01.449Z" },
- { url = "https://files.pythonhosted.org/packages/23/c6/a04e9cef7c052717fcb28fb63b3824802488f688391895b618e39be0f684/lupa-2.6-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:e8faddd9d198688c8884091173a088a8e920ecc96cda2ffed576a23574c4b3f6", size = 2073458, upload-time = "2025-10-24T07:19:03.369Z" },
- { url = "https://files.pythonhosted.org/packages/e6/10/824173d10f38b51fc77785228f01411b6ca28826ce27404c7c912e0e442c/lupa-2.6-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:daebb3a6b58095c917e76ba727ab37b27477fb926957c825205fbda431552134", size = 1067683, upload-time = "2025-10-24T07:19:06.2Z" },
- { url = "https://files.pythonhosted.org/packages/b6/dc/9692fbcf3c924d9c4ece2d8d2f724451ac2e09af0bd2a782db1cef34e799/lupa-2.6-cp314-cp314-musllinux_1_2_i686.whl", hash = "sha256:f3154e68972befe0f81564e37d8142b5d5d79931a18309226a04ec92487d4ea3", size = 1171892, upload-time = "2025-10-24T07:19:08.544Z" },
- { url = "https://files.pythonhosted.org/packages/84/ff/e318b628d4643c278c96ab3ddea07fc36b075a57383c837f5b11e537ba9d/lupa-2.6-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:e4dadf77b9fedc0bfa53417cc28dc2278a26d4cbd95c29f8927ad4d8fe0a7ef9", size = 2166641, upload-time = "2025-10-24T07:19:10.485Z" },
- { url = "https://files.pythonhosted.org/packages/12/f7/a6f9ec2806cf2d50826980cdb4b3cffc7691dc6f95e13cc728846d5cb793/lupa-2.6-cp314-cp314-win32.whl", hash = "sha256:cb34169c6fa3bab3e8ac58ca21b8a7102f6a94b6a5d08d3636312f3f02fafd8f", size = 1456857, upload-time = "2025-10-24T07:19:37.989Z" },
- { url = "https://files.pythonhosted.org/packages/c5/de/df71896f25bdc18360fdfa3b802cd7d57d7fede41a0e9724a4625b412c85/lupa-2.6-cp314-cp314-win_amd64.whl", hash = "sha256:b74f944fe46c421e25d0f8692aef1e842192f6f7f68034201382ac440ef9ea67", size = 1731191, upload-time = "2025-10-24T07:19:40.281Z" },
- { url = "https://files.pythonhosted.org/packages/47/3c/a1f23b01c54669465f5f4c4083107d496fbe6fb45998771420e9aadcf145/lupa-2.6-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:0e21b716408a21ab65723f8841cf7f2f37a844b7a965eeabb785e27fca4099cf", size = 999343, upload-time = "2025-10-24T07:19:12.519Z" },
- { url = "https://files.pythonhosted.org/packages/c5/6d/501994291cb640bfa2ccf7f554be4e6914afa21c4026bd01bff9ca8aac57/lupa-2.6-cp314-cp314t-macosx_11_0_universal2.whl", hash = "sha256:589db872a141bfff828340079bbdf3e9a31f2689f4ca0d88f97d9e8c2eae6142", size = 2000730, upload-time = "2025-10-24T07:19:14.869Z" },
- { url = "https://files.pythonhosted.org/packages/53/a5/457ffb4f3f20469956c2d4c4842a7675e884efc895b2f23d126d23e126cc/lupa-2.6-cp314-cp314t-macosx_11_0_x86_64.whl", hash = "sha256:cd852a91a4a9d4dcbb9a58100f820a75a425703ec3e3f049055f60b8533b7953", size = 1021553, upload-time = "2025-10-24T07:19:17.123Z" },
- { url = "https://files.pythonhosted.org/packages/51/6b/36bb5a5d0960f2a5c7c700e0819abb76fd9bf9c1d8a66e5106416d6e9b14/lupa-2.6-cp314-cp314t-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl", hash = "sha256:0334753be028358922415ca97a64a3048e4ed155413fc4eaf87dd0a7e2752983", size = 1133275, upload-time = "2025-10-24T07:19:20.51Z" },
- { url = "https://files.pythonhosted.org/packages/19/86/202ff4429f663013f37d2229f6176ca9f83678a50257d70f61a0a97281bf/lupa-2.6-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:661d895cd38c87658a34780fac54a690ec036ead743e41b74c3fb81a9e65a6aa", size = 1038441, upload-time = "2025-10-24T07:19:22.509Z" },
- { url = "https://files.pythonhosted.org/packages/a7/42/d8125f8e420714e5b52e9c08d88b5329dfb02dcca731b4f21faaee6cc5b5/lupa-2.6-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:6aa58454ccc13878cc177c62529a2056be734da16369e451987ff92784994ca7", size = 2058324, upload-time = "2025-10-24T07:19:24.979Z" },
- { url = "https://files.pythonhosted.org/packages/2b/2c/47bf8b84059876e877a339717ddb595a4a7b0e8740bacae78ba527562e1c/lupa-2.6-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:1425017264e470c98022bba8cff5bd46d054a827f5df6b80274f9cc71dafd24f", size = 1060250, upload-time = "2025-10-24T07:19:27.262Z" },
- { url = "https://files.pythonhosted.org/packages/c2/06/d88add2b6406ca1bdec99d11a429222837ca6d03bea42ca75afa169a78cb/lupa-2.6-cp314-cp314t-musllinux_1_2_i686.whl", hash = "sha256:224af0532d216e3105f0a127410f12320f7c5f1aa0300bdf9646b8d9afb0048c", size = 1151126, upload-time = "2025-10-24T07:19:29.522Z" },
- { url = "https://files.pythonhosted.org/packages/b4/a0/89e6a024c3b4485b89ef86881c9d55e097e7cb0bdb74efb746f2fa6a9a76/lupa-2.6-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:9abb98d5a8fd27c8285302e82199f0e56e463066f88f619d6594a450bf269d80", size = 2153693, upload-time = "2025-10-24T07:19:31.379Z" },
- { url = "https://files.pythonhosted.org/packages/b6/36/a0f007dc58fc1bbf51fb85dcc82fcb1f21b8c4261361de7dab0e3d8521ef/lupa-2.6-cp314-cp314t-win32.whl", hash = "sha256:1849efeba7a8f6fb8aa2c13790bee988fd242ae404bd459509640eeea3d1e291", size = 1590104, upload-time = "2025-10-24T07:19:33.514Z" },
- { url = "https://files.pythonhosted.org/packages/7d/5e/db903ce9cf82c48d6b91bf6d63ae4c8d0d17958939a4e04ba6b9f38b8643/lupa-2.6-cp314-cp314t-win_amd64.whl", hash = "sha256:fc1498d1a4fc028bc521c26d0fad4ca00ed63b952e32fb95949bda76a04bad52", size = 1913818, upload-time = "2025-10-24T07:19:36.039Z" },
-]
-
[[package]]
name = "markdown-it-py"
-version = "4.0.0"
+version = "4.2.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "mdurl" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/5b/f5/4ec618ed16cc4f8fb3b701563655a69816155e79e24a17b651541804721d/markdown_it_py-4.0.0.tar.gz", hash = "sha256:cb0a2b4aa34f932c007117b194e945bd74e0ec24133ceb5bac59009cda1cb9f3", size = 73070, upload-time = "2025-08-11T12:57:52.854Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/06/ff/7841249c247aa650a76b9ee4bbaeae59370dc8bfd2f6c01f3630c35eb134/markdown_it_py-4.2.0.tar.gz", hash = "sha256:04a21681d6fbb623de53f6f364d352309d4094dd4194040a10fd51833e418d49", size = 82454, upload-time = "2026-05-07T12:08:28.36Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/94/54/e7d793b573f298e1c9013b8c4dade17d481164aa517d1d7148619c2cedbf/markdown_it_py-4.0.0-py3-none-any.whl", hash = "sha256:87327c59b172c5011896038353a81343b6754500a08cd7a4973bb48c6d578147", size = 87321, upload-time = "2025-08-11T12:57:51.923Z" },
+ { url = "https://files.pythonhosted.org/packages/b3/81/4da04ced5a082363ecfa159c010d200ecbd959ae410c10c0264a38cac0f5/markdown_it_py-4.2.0-py3-none-any.whl", hash = "sha256:9f7ebbcd14fe59494226453aed97c1070d83f8d24b6fc3a3bcf9a38092641c4a", size = 91687, upload-time = "2026-05-07T12:08:27.182Z" },
]
[[package]]
name = "mcp"
-version = "1.26.0"
+version = "1.27.1"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "anyio" },
@@ -637,9 +590,9 @@ dependencies = [
{ name = "typing-inspection" },
{ name = "uvicorn", marker = "sys_platform != 'emscripten'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/fc/6d/62e76bbb8144d6ed86e202b5edd8a4cb631e7c8130f3f4893c3f90262b10/mcp-1.26.0.tar.gz", hash = "sha256:db6e2ef491eecc1a0d93711a76f28dec2e05999f93afd48795da1c1137142c66", size = 608005, upload-time = "2026-01-24T19:40:32.468Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/38/83/d1efe7c2980d8a3afa476f4e3d42d53dd54c0ab94c27bee5d755b45c8b73/mcp-1.27.1.tar.gz", hash = "sha256:0f47e1820f8f8f941466b39749eb1d1839a04caddca2bc60e9d46e8a99914924", size = 608458, upload-time = "2026-05-08T16:50:12.601Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/fd/d9/eaa1f80170d2b7c5ba23f3b59f766f3a0bb41155fbc32a69adfa1adaaef9/mcp-1.26.0-py3-none-any.whl", hash = "sha256:904a21c33c25aa98ddbeb47273033c435e595bbacfdb177f4bd87f6dceebe1ca", size = 233615, upload-time = "2026-01-24T19:40:30.652Z" },
+ { url = "https://files.pythonhosted.org/packages/fd/73/42d9596facebdb533b7f0b86c1b0364ef350d1f8ba78b1052e8a58b48b65/mcp-1.27.1-py3-none-any.whl", hash = "sha256:1af3c4203b329430fde7a87b4fcb6392a041f5cb851fd68fc674016ab4e7c06f", size = 216260, upload-time = "2026-05-08T16:50:10.547Z" },
]
[[package]]
@@ -653,11 +606,11 @@ wheels = [
[[package]]
name = "more-itertools"
-version = "10.8.0"
+version = "11.0.2"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/ea/5d/38b681d3fce7a266dd9ab73c66959406d565b3e85f21d5e66e1181d93721/more_itertools-10.8.0.tar.gz", hash = "sha256:f638ddf8a1a0d134181275fb5d58b086ead7c6a72429ad725c67503f13ba30bd", size = 137431, upload-time = "2025-09-02T15:23:11.018Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/a2/f7/139d22fef48ac78127d18e01d80cf1be40236ae489769d17f35c3d425293/more_itertools-11.0.2.tar.gz", hash = "sha256:392a9e1e362cbc106a2457d37cabf9b36e5e12efd4ebff1654630e76597df804", size = 144659, upload-time = "2026-04-09T15:01:33.297Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/a4/8e/469e5a4a2f5855992e425f3cb33804cc07bf18d48f2db061aec61ce50270/more_itertools-10.8.0-py3-none-any.whl", hash = "sha256:52d4362373dcf7c52546bc4af9a86ee7c4579df9a8dc268be0a2f949d376cc9b", size = 69667, upload-time = "2025-09-02T15:23:09.635Z" },
+ { url = "https://files.pythonhosted.org/packages/cb/98/6af411189d9413534c3eb691182bff1f5c6d44ed2f93f2edfe52a1bbceb8/more_itertools-11.0.2-py3-none-any.whl", hash = "sha256:6e35b35f818b01f691643c6c611bc0902f2e92b46c18fffa77ae1e7c46e912e4", size = 71939, upload-time = "2026-04-09T15:01:32.21Z" },
]
[[package]]
@@ -674,15 +627,15 @@ wheels = [
[[package]]
name = "opentelemetry-api"
-version = "1.39.1"
+version = "1.41.1"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "importlib-metadata" },
{ name = "typing-extensions" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/97/b9/3161be15bb8e3ad01be8be5a968a9237c3027c5be504362ff800fca3e442/opentelemetry_api-1.39.1.tar.gz", hash = "sha256:fbde8c80e1b937a2c61f20347e91c0c18a1940cecf012d62e65a7caf08967c9c", size = 65767, upload-time = "2025-12-11T13:32:39.182Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/fa/fc/b7564cbef36601aef0d6c9bc01f7badb64be8e862c2e1c3c5c3b43b53e4f/opentelemetry_api-1.41.1.tar.gz", hash = "sha256:0ad1814d73b875f84494387dae86ce0b12c68556331ce6ce8fe789197c949621", size = 71416, upload-time = "2026-04-24T13:15:38.262Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/cf/df/d3f1ddf4bb4cb50ed9b1139cc7b1c54c34a1e7ce8fd1b9a37c0d1551a6bd/opentelemetry_api-1.39.1-py3-none-any.whl", hash = "sha256:2edd8463432a7f8443edce90972169b195e7d6a05500cd29e6d13898187c9950", size = 66356, upload-time = "2025-12-11T13:32:17.304Z" },
+ { url = "https://files.pythonhosted.org/packages/29/59/3e7118ed140f76b0982ba4321bdaed1997a0473f9720de2d10788a577033/opentelemetry_api-1.41.1-py3-none-any.whl", hash = "sha256:a22df900e75c76dc08440710e51f52f1aa6b451b429298896023e60db5b3139f", size = 69007, upload-time = "2026-04-24T13:15:15.662Z" },
]
[[package]]
@@ -696,29 +649,20 @@ wheels = [
[[package]]
name = "pathable"
-version = "0.4.4"
+version = "0.5.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/67/93/8f2c2075b180c12c1e9f6a09d1a985bc2036906b13dff1d8917e395f2048/pathable-0.4.4.tar.gz", hash = "sha256:6905a3cd17804edfac7875b5f6c9142a218c7caef78693c2dbbbfbac186d88b2", size = 8124, upload-time = "2025-01-10T18:43:13.247Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/72/55/b748445cb4ea6b125626f15379be7c96d1035d4fa3e8fee362fa92298abf/pathable-0.5.0.tar.gz", hash = "sha256:d81938348a1cacb525e7c75166270644782c0fb9c8cecc16be033e71427e0ef1", size = 16655, upload-time = "2026-02-20T08:47:00.748Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/7d/eb/b6260b31b1a96386c0a880edebe26f89669098acea8e0318bff6adb378fd/pathable-0.4.4-py3-none-any.whl", hash = "sha256:5ae9e94793b6ef5a4cbe0a7ce9dbbefc1eec38df253763fd0aeeacf2762dbbc2", size = 9592, upload-time = "2025-01-10T18:43:11.88Z" },
-]
-
-[[package]]
-name = "pathvalidate"
-version = "3.3.1"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/fa/2a/52a8da6fe965dea6192eb716b357558e103aea0a1e9a8352ad575a8406ca/pathvalidate-3.3.1.tar.gz", hash = "sha256:b18c07212bfead624345bb8e1d6141cdcf15a39736994ea0b94035ad2b1ba177", size = 63262, upload-time = "2025-06-15T09:07:20.736Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/9a/70/875f4a23bfc4731703a5835487d0d2fb999031bd415e7d17c0ae615c18b7/pathvalidate-3.3.1-py3-none-any.whl", hash = "sha256:5263baab691f8e1af96092fa5137ee17df5bdfbd6cff1fcac4d6ef4bc2e1735f", size = 24305, upload-time = "2025-06-15T09:07:19.117Z" },
+ { url = "https://files.pythonhosted.org/packages/52/96/5a770e5c461462575474468e5af931cff9de036e7c2b4fea23c1c58d2cbe/pathable-0.5.0-py3-none-any.whl", hash = "sha256:646e3d09491a6351a0c82632a09c02cdf70a252e73196b36d8a15ba0a114f0a6", size = 16867, upload-time = "2026-02-20T08:46:59.536Z" },
]
[[package]]
name = "platformdirs"
-version = "4.5.0"
+version = "4.9.6"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/61/33/9611380c2bdb1225fdef633e2a9610622310fed35ab11dac9620972ee088/platformdirs-4.5.0.tar.gz", hash = "sha256:70ddccdd7c99fc5942e9fc25636a8b34d04c24b335100223152c2803e4063312", size = 21632, upload-time = "2025-10-08T17:44:48.791Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/9f/4a/0883b8e3802965322523f0b200ecf33d31f10991d0401162f4b23c698b42/platformdirs-4.9.6.tar.gz", hash = "sha256:3bfa75b0ad0db84096ae777218481852c0ebc6c727b3168c1b9e0118e458cf0a", size = 29400, upload-time = "2026-04-09T00:04:10.812Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/73/cb/ac7874b3e5d58441674fb70742e6c374b28b0c7cb988d37d991cde47166c/platformdirs-4.5.0-py3-none-any.whl", hash = "sha256:e578a81bb873cbb89a41fcc904c7ef523cc18284b7e3b3ccf06aca1403b7ebd3", size = 18651, upload-time = "2025-10-08T17:44:47.223Z" },
+ { url = "https://files.pythonhosted.org/packages/75/a6/a0a304dc33b49145b21f4808d763822111e67d1c3a32b524a1baf947b6e1/platformdirs-4.9.6-py3-none-any.whl", hash = "sha256:e61adb1d5e5cb3441b4b7710bea7e4c12250ca49439228cc1021c00dcfac0917", size = 21348, upload-time = "2026-04-09T00:04:09.463Z" },
]
[[package]]
@@ -730,18 +674,9 @@ wheels = [
{ url = "https://files.pythonhosted.org/packages/54/20/4d324d65cc6d9205fabedc306948156824eb9f0ee1633355a8f7ec5c66bf/pluggy-1.6.0-py3-none-any.whl", hash = "sha256:e920276dd6813095e9377c0bc5566d94c932c33b27a3e3945d8389c374dd4746", size = 20538, upload-time = "2025-05-15T12:30:06.134Z" },
]
-[[package]]
-name = "prometheus-client"
-version = "0.24.1"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/f0/58/a794d23feb6b00fc0c72787d7e87d872a6730dd9ed7c7b3e954637d8f280/prometheus_client-0.24.1.tar.gz", hash = "sha256:7e0ced7fbbd40f7b84962d5d2ab6f17ef88a72504dcf7c0b40737b43b2a461f9", size = 85616, upload-time = "2026-01-14T15:26:26.965Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/74/c3/24a2f845e3917201628ecaba4f18bab4d18a337834c1df2a159ee9d22a42/prometheus_client-0.24.1-py3-none-any.whl", hash = "sha256:150db128af71a5c2482b36e588fc8a6b95e498750da4b17065947c16070f4055", size = 64057, upload-time = "2026-01-14T15:26:24.42Z" },
-]
-
[[package]]
name = "prowler-mcp"
-version = "0.5.0"
+version = "0.8.0"
source = { editable = "." }
dependencies = [
{ name = "fastmcp" },
@@ -750,35 +685,43 @@ dependencies = [
[package.dev-dependencies]
dev = [
+ { name = "bandit" },
{ name = "pytest" },
+ { name = "ruff" },
+ { name = "vulture" },
]
[package.metadata]
requires-dist = [
- { name = "fastmcp", specifier = "==2.14.0" },
+ { name = "fastmcp", specifier = "==3.2.4" },
{ name = "httpx", specifier = "==0.28.1" },
]
[package.metadata.requires-dev]
-dev = [{ name = "pytest", specifier = "==8.3.5" }]
+dev = [
+ { name = "bandit", specifier = "==1.8.3" },
+ { name = "pytest", specifier = "==9.0.3" },
+ { name = "ruff", specifier = "==0.15.11" },
+ { name = "vulture", specifier = "==2.14" },
+]
[[package]]
name = "py-key-value-aio"
-version = "0.3.0"
+version = "0.4.4"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "beartype" },
- { name = "py-key-value-shared" },
+ { name = "typing-extensions" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/93/ce/3136b771dddf5ac905cc193b461eb67967cf3979688c6696e1f2cdcde7ea/py_key_value_aio-0.3.0.tar.gz", hash = "sha256:858e852fcf6d696d231266da66042d3355a7f9871650415feef9fca7a6cd4155", size = 50801, upload-time = "2025-11-17T16:50:04.711Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/04/3c/0397c072a38d4bc580994b42e0c90c5f44f679303489e4376289534735e5/py_key_value_aio-0.4.4.tar.gz", hash = "sha256:e3012e6243ed7cc09bb05457bd4d03b1ba5c2b1ca8700096b3927db79ffbbe55", size = 92300, upload-time = "2026-02-16T21:21:43.245Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/99/10/72f6f213b8f0bce36eff21fda0a13271834e9eeff7f9609b01afdc253c79/py_key_value_aio-0.3.0-py3-none-any.whl", hash = "sha256:1c781915766078bfd608daa769fefb97e65d1d73746a3dfb640460e322071b64", size = 96342, upload-time = "2025-11-17T16:50:03.801Z" },
+ { url = "https://files.pythonhosted.org/packages/32/69/f1b537ee70b7def42d63124a539ed3026a11a3ffc3086947a1ca6e861868/py_key_value_aio-0.4.4-py3-none-any.whl", hash = "sha256:18e17564ecae61b987f909fc2cd41ee2012c84b4b1dcb8c055cf8b4bc1bf3f5d", size = 152291, upload-time = "2026-02-16T21:21:44.241Z" },
]
[package.optional-dependencies]
-disk = [
- { name = "diskcache" },
- { name = "pathvalidate" },
+filetree = [
+ { name = "aiofile" },
+ { name = "anyio" },
]
keyring = [
{ name = "keyring" },
@@ -786,35 +729,19 @@ keyring = [
memory = [
{ name = "cachetools" },
]
-redis = [
- { name = "redis" },
-]
-
-[[package]]
-name = "py-key-value-shared"
-version = "0.3.0"
-source = { registry = "https://pypi.org/simple" }
-dependencies = [
- { name = "beartype" },
- { name = "typing-extensions" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/7b/e4/1971dfc4620a3a15b4579fe99e024f5edd6e0967a71154771a059daff4db/py_key_value_shared-0.3.0.tar.gz", hash = "sha256:8fdd786cf96c3e900102945f92aa1473138ebe960ef49da1c833790160c28a4b", size = 11666, upload-time = "2025-11-17T16:50:06.849Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/51/e4/b8b0a03ece72f47dce2307d36e1c34725b7223d209fc679315ffe6a4e2c3/py_key_value_shared-0.3.0-py3-none-any.whl", hash = "sha256:5b0efba7ebca08bb158b1e93afc2f07d30b8f40c2fc12ce24a4c0d84f42f9298", size = 19560, upload-time = "2025-11-17T16:50:05.954Z" },
-]
[[package]]
name = "pycparser"
-version = "2.23"
+version = "3.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/fe/cf/d2d3b9f5699fb1e4615c8e32ff220203e43b248e1dfcc6736ad9057731ca/pycparser-2.23.tar.gz", hash = "sha256:78816d4f24add8f10a06d6f05b4d424ad9e96cfebf68a4ddc99c65c0720d00c2", size = 173734, upload-time = "2025-09-09T13:23:47.91Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/1b/7d/92392ff7815c21062bea51aa7b87d45576f649f16458d78b7cf94b9ab2e6/pycparser-3.0.tar.gz", hash = "sha256:600f49d217304a5902ac3c37e1281c9fe94e4d0489de643a9504c5cdfdfc6b29", size = 103492, upload-time = "2026-01-21T14:26:51.89Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/a0/e3/59cd50310fc9b59512193629e1984c1f95e5c8ae6e5d8c69532ccc65a7fe/pycparser-2.23-py3-none-any.whl", hash = "sha256:e5c6e8d3fbad53479cab09ac03729e0a9faf2bee3db8208a550daf5af81a5934", size = 118140, upload-time = "2025-09-09T13:23:46.651Z" },
+ { url = "https://files.pythonhosted.org/packages/0c/c3/44f3fbbfa403ea2a7c779186dc20772604442dde72947e7d01069cbe98e3/pycparser-3.0-py3-none-any.whl", hash = "sha256:b727414169a36b7d524c1c3e31839a521725078d7b2ff038656844266160a992", size = 48172, upload-time = "2026-01-21T14:26:50.693Z" },
]
[[package]]
name = "pydantic"
-version = "2.11.9"
+version = "2.13.4"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "annotated-types" },
@@ -822,9 +749,9 @@ dependencies = [
{ name = "typing-extensions" },
{ name = "typing-inspection" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/ff/5d/09a551ba512d7ca404d785072700d3f6727a02f6f3c24ecfd081c7cf0aa8/pydantic-2.11.9.tar.gz", hash = "sha256:6b8ffda597a14812a7975c90b82a8a2e777d9257aba3453f973acd3c032a18e2", size = 788495, upload-time = "2025-09-13T11:26:39.325Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/18/a5/b60d21ac674192f8ab0ba4e9fd860690f9b4a6e51ca5df118733b487d8d6/pydantic-2.13.4.tar.gz", hash = "sha256:c40756b57adaa8b1efeeced5c196f3f3b7c435f90e84ea7f443901bec8099ef6", size = 844775, upload-time = "2026-05-06T13:43:05.343Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/3e/d3/108f2006987c58e76691d5ae5d200dd3e0f532cb4e5fa3560751c3a1feba/pydantic-2.11.9-py3-none-any.whl", hash = "sha256:c42dd626f5cfc1c6950ce6205ea58c93efa406da65f479dcb4029d5934857da2", size = 444855, upload-time = "2025-09-13T11:26:36.909Z" },
+ { url = "https://files.pythonhosted.org/packages/fd/7b/122376b1fd3c62c1ed9dc80c931ace4844b3c55407b6fb2d199377c9736f/pydantic-2.13.4-py3-none-any.whl", hash = "sha256:45a282cde31d808236fd7ea9d919b128653c8b38b393d1c4ab335c62924d9aba", size = 472262, upload-time = "2026-05-06T13:43:02.641Z" },
]
[package.optional-dependencies]
@@ -834,79 +761,91 @@ email = [
[[package]]
name = "pydantic-core"
-version = "2.33.2"
+version = "2.46.4"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "typing-extensions" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/ad/88/5f2260bdfae97aabf98f1778d43f69574390ad787afb646292a638c923d4/pydantic_core-2.33.2.tar.gz", hash = "sha256:7cb8bc3605c29176e1b105350d2e6474142d7c1bd1d9327c4a9bdb46bf827acc", size = 435195, upload-time = "2025-04-23T18:33:52.104Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/9d/56/921726b776ace8d8f5db44c4ef961006580d91dc52b803c489fafd1aa249/pydantic_core-2.46.4.tar.gz", hash = "sha256:62f875393d7f270851f20523dd2e29f082bcc82292d66db2b64ea71f64b6e1c1", size = 471464, upload-time = "2026-05-06T13:37:06.98Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/18/8a/2b41c97f554ec8c71f2a8a5f85cb56a8b0956addfe8b0efb5b3d77e8bdc3/pydantic_core-2.33.2-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:a7ec89dc587667f22b6a0b6579c249fca9026ce7c333fc142ba42411fa243cdc", size = 2009000, upload-time = "2025-04-23T18:31:25.863Z" },
- { url = "https://files.pythonhosted.org/packages/a1/02/6224312aacb3c8ecbaa959897af57181fb6cf3a3d7917fd44d0f2917e6f2/pydantic_core-2.33.2-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:3c6db6e52c6d70aa0d00d45cdb9b40f0433b96380071ea80b09277dba021ddf7", size = 1847996, upload-time = "2025-04-23T18:31:27.341Z" },
- { url = "https://files.pythonhosted.org/packages/d6/46/6dcdf084a523dbe0a0be59d054734b86a981726f221f4562aed313dbcb49/pydantic_core-2.33.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:4e61206137cbc65e6d5256e1166f88331d3b6238e082d9f74613b9b765fb9025", size = 1880957, upload-time = "2025-04-23T18:31:28.956Z" },
- { url = "https://files.pythonhosted.org/packages/ec/6b/1ec2c03837ac00886ba8160ce041ce4e325b41d06a034adbef11339ae422/pydantic_core-2.33.2-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:eb8c529b2819c37140eb51b914153063d27ed88e3bdc31b71198a198e921e011", size = 1964199, upload-time = "2025-04-23T18:31:31.025Z" },
- { url = "https://files.pythonhosted.org/packages/2d/1d/6bf34d6adb9debd9136bd197ca72642203ce9aaaa85cfcbfcf20f9696e83/pydantic_core-2.33.2-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:c52b02ad8b4e2cf14ca7b3d918f3eb0ee91e63b3167c32591e57c4317e134f8f", size = 2120296, upload-time = "2025-04-23T18:31:32.514Z" },
- { url = "https://files.pythonhosted.org/packages/e0/94/2bd0aaf5a591e974b32a9f7123f16637776c304471a0ab33cf263cf5591a/pydantic_core-2.33.2-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:96081f1605125ba0855dfda83f6f3df5ec90c61195421ba72223de35ccfb2f88", size = 2676109, upload-time = "2025-04-23T18:31:33.958Z" },
- { url = "https://files.pythonhosted.org/packages/f9/41/4b043778cf9c4285d59742281a769eac371b9e47e35f98ad321349cc5d61/pydantic_core-2.33.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:8f57a69461af2a5fa6e6bbd7a5f60d3b7e6cebb687f55106933188e79ad155c1", size = 2002028, upload-time = "2025-04-23T18:31:39.095Z" },
- { url = "https://files.pythonhosted.org/packages/cb/d5/7bb781bf2748ce3d03af04d5c969fa1308880e1dca35a9bd94e1a96a922e/pydantic_core-2.33.2-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:572c7e6c8bb4774d2ac88929e3d1f12bc45714ae5ee6d9a788a9fb35e60bb04b", size = 2100044, upload-time = "2025-04-23T18:31:41.034Z" },
- { url = "https://files.pythonhosted.org/packages/fe/36/def5e53e1eb0ad896785702a5bbfd25eed546cdcf4087ad285021a90ed53/pydantic_core-2.33.2-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:db4b41f9bd95fbe5acd76d89920336ba96f03e149097365afe1cb092fceb89a1", size = 2058881, upload-time = "2025-04-23T18:31:42.757Z" },
- { url = "https://files.pythonhosted.org/packages/01/6c/57f8d70b2ee57fc3dc8b9610315949837fa8c11d86927b9bb044f8705419/pydantic_core-2.33.2-cp312-cp312-musllinux_1_1_armv7l.whl", hash = "sha256:fa854f5cf7e33842a892e5c73f45327760bc7bc516339fda888c75ae60edaeb6", size = 2227034, upload-time = "2025-04-23T18:31:44.304Z" },
- { url = "https://files.pythonhosted.org/packages/27/b9/9c17f0396a82b3d5cbea4c24d742083422639e7bb1d5bf600e12cb176a13/pydantic_core-2.33.2-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:5f483cfb75ff703095c59e365360cb73e00185e01aaea067cd19acffd2ab20ea", size = 2234187, upload-time = "2025-04-23T18:31:45.891Z" },
- { url = "https://files.pythonhosted.org/packages/b0/6a/adf5734ffd52bf86d865093ad70b2ce543415e0e356f6cacabbc0d9ad910/pydantic_core-2.33.2-cp312-cp312-win32.whl", hash = "sha256:9cb1da0f5a471435a7bc7e439b8a728e8b61e59784b2af70d7c169f8dd8ae290", size = 1892628, upload-time = "2025-04-23T18:31:47.819Z" },
- { url = "https://files.pythonhosted.org/packages/43/e4/5479fecb3606c1368d496a825d8411e126133c41224c1e7238be58b87d7e/pydantic_core-2.33.2-cp312-cp312-win_amd64.whl", hash = "sha256:f941635f2a3d96b2973e867144fde513665c87f13fe0e193c158ac51bfaaa7b2", size = 1955866, upload-time = "2025-04-23T18:31:49.635Z" },
- { url = "https://files.pythonhosted.org/packages/0d/24/8b11e8b3e2be9dd82df4b11408a67c61bb4dc4f8e11b5b0fc888b38118b5/pydantic_core-2.33.2-cp312-cp312-win_arm64.whl", hash = "sha256:cca3868ddfaccfbc4bfb1d608e2ccaaebe0ae628e1416aeb9c4d88c001bb45ab", size = 1888894, upload-time = "2025-04-23T18:31:51.609Z" },
- { url = "https://files.pythonhosted.org/packages/46/8c/99040727b41f56616573a28771b1bfa08a3d3fe74d3d513f01251f79f172/pydantic_core-2.33.2-cp313-cp313-macosx_10_12_x86_64.whl", hash = "sha256:1082dd3e2d7109ad8b7da48e1d4710c8d06c253cbc4a27c1cff4fbcaa97a9e3f", size = 2015688, upload-time = "2025-04-23T18:31:53.175Z" },
- { url = "https://files.pythonhosted.org/packages/3a/cc/5999d1eb705a6cefc31f0b4a90e9f7fc400539b1a1030529700cc1b51838/pydantic_core-2.33.2-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:f517ca031dfc037a9c07e748cefd8d96235088b83b4f4ba8939105d20fa1dcd6", size = 1844808, upload-time = "2025-04-23T18:31:54.79Z" },
- { url = "https://files.pythonhosted.org/packages/6f/5e/a0a7b8885c98889a18b6e376f344da1ef323d270b44edf8174d6bce4d622/pydantic_core-2.33.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:0a9f2c9dd19656823cb8250b0724ee9c60a82f3cdf68a080979d13092a3b0fef", size = 1885580, upload-time = "2025-04-23T18:31:57.393Z" },
- { url = "https://files.pythonhosted.org/packages/3b/2a/953581f343c7d11a304581156618c3f592435523dd9d79865903272c256a/pydantic_core-2.33.2-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:2b0a451c263b01acebe51895bfb0e1cc842a5c666efe06cdf13846c7418caa9a", size = 1973859, upload-time = "2025-04-23T18:31:59.065Z" },
- { url = "https://files.pythonhosted.org/packages/e6/55/f1a813904771c03a3f97f676c62cca0c0a4138654107c1b61f19c644868b/pydantic_core-2.33.2-cp313-cp313-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1ea40a64d23faa25e62a70ad163571c0b342b8bf66d5fa612ac0dec4f069d916", size = 2120810, upload-time = "2025-04-23T18:32:00.78Z" },
- { url = "https://files.pythonhosted.org/packages/aa/c3/053389835a996e18853ba107a63caae0b9deb4a276c6b472931ea9ae6e48/pydantic_core-2.33.2-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:0fb2d542b4d66f9470e8065c5469ec676978d625a8b7a363f07d9a501a9cb36a", size = 2676498, upload-time = "2025-04-23T18:32:02.418Z" },
- { url = "https://files.pythonhosted.org/packages/eb/3c/f4abd740877a35abade05e437245b192f9d0ffb48bbbbd708df33d3cda37/pydantic_core-2.33.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:9fdac5d6ffa1b5a83bca06ffe7583f5576555e6c8b3a91fbd25ea7780f825f7d", size = 2000611, upload-time = "2025-04-23T18:32:04.152Z" },
- { url = "https://files.pythonhosted.org/packages/59/a7/63ef2fed1837d1121a894d0ce88439fe3e3b3e48c7543b2a4479eb99c2bd/pydantic_core-2.33.2-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:04a1a413977ab517154eebb2d326da71638271477d6ad87a769102f7c2488c56", size = 2107924, upload-time = "2025-04-23T18:32:06.129Z" },
- { url = "https://files.pythonhosted.org/packages/04/8f/2551964ef045669801675f1cfc3b0d74147f4901c3ffa42be2ddb1f0efc4/pydantic_core-2.33.2-cp313-cp313-musllinux_1_1_aarch64.whl", hash = "sha256:c8e7af2f4e0194c22b5b37205bfb293d166a7344a5b0d0eaccebc376546d77d5", size = 2063196, upload-time = "2025-04-23T18:32:08.178Z" },
- { url = "https://files.pythonhosted.org/packages/26/bd/d9602777e77fc6dbb0c7db9ad356e9a985825547dce5ad1d30ee04903918/pydantic_core-2.33.2-cp313-cp313-musllinux_1_1_armv7l.whl", hash = "sha256:5c92edd15cd58b3c2d34873597a1e20f13094f59cf88068adb18947df5455b4e", size = 2236389, upload-time = "2025-04-23T18:32:10.242Z" },
- { url = "https://files.pythonhosted.org/packages/42/db/0e950daa7e2230423ab342ae918a794964b053bec24ba8af013fc7c94846/pydantic_core-2.33.2-cp313-cp313-musllinux_1_1_x86_64.whl", hash = "sha256:65132b7b4a1c0beded5e057324b7e16e10910c106d43675d9bd87d4f38dde162", size = 2239223, upload-time = "2025-04-23T18:32:12.382Z" },
- { url = "https://files.pythonhosted.org/packages/58/4d/4f937099c545a8a17eb52cb67fe0447fd9a373b348ccfa9a87f141eeb00f/pydantic_core-2.33.2-cp313-cp313-win32.whl", hash = "sha256:52fb90784e0a242bb96ec53f42196a17278855b0f31ac7c3cc6f5c1ec4811849", size = 1900473, upload-time = "2025-04-23T18:32:14.034Z" },
- { url = "https://files.pythonhosted.org/packages/a0/75/4a0a9bac998d78d889def5e4ef2b065acba8cae8c93696906c3a91f310ca/pydantic_core-2.33.2-cp313-cp313-win_amd64.whl", hash = "sha256:c083a3bdd5a93dfe480f1125926afcdbf2917ae714bdb80b36d34318b2bec5d9", size = 1955269, upload-time = "2025-04-23T18:32:15.783Z" },
- { url = "https://files.pythonhosted.org/packages/f9/86/1beda0576969592f1497b4ce8e7bc8cbdf614c352426271b1b10d5f0aa64/pydantic_core-2.33.2-cp313-cp313-win_arm64.whl", hash = "sha256:e80b087132752f6b3d714f041ccf74403799d3b23a72722ea2e6ba2e892555b9", size = 1893921, upload-time = "2025-04-23T18:32:18.473Z" },
- { url = "https://files.pythonhosted.org/packages/a4/7d/e09391c2eebeab681df2b74bfe6c43422fffede8dc74187b2b0bf6fd7571/pydantic_core-2.33.2-cp313-cp313t-macosx_11_0_arm64.whl", hash = "sha256:61c18fba8e5e9db3ab908620af374db0ac1baa69f0f32df4f61ae23f15e586ac", size = 1806162, upload-time = "2025-04-23T18:32:20.188Z" },
- { url = "https://files.pythonhosted.org/packages/f1/3d/847b6b1fed9f8ed3bb95a9ad04fbd0b212e832d4f0f50ff4d9ee5a9f15cf/pydantic_core-2.33.2-cp313-cp313t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:95237e53bb015f67b63c91af7518a62a8660376a6a0db19b89acc77a4d6199f5", size = 1981560, upload-time = "2025-04-23T18:32:22.354Z" },
- { url = "https://files.pythonhosted.org/packages/6f/9a/e73262f6c6656262b5fdd723ad90f518f579b7bc8622e43a942eec53c938/pydantic_core-2.33.2-cp313-cp313t-win_amd64.whl", hash = "sha256:c2fc0a768ef76c15ab9238afa6da7f69895bb5d1ee83aeea2e3509af4472d0b9", size = 1935777, upload-time = "2025-04-23T18:32:25.088Z" },
+ { url = "https://files.pythonhosted.org/packages/ce/8c/af022f0af448d7747c5154288d46b5f2bc5f17366eaa0e23e9aa04d59f3b/pydantic_core-2.46.4-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:3245406455a5d98187ec35530fd772b1d799b26667980872c8d4614991e2c4a2", size = 2106158, upload-time = "2026-05-06T13:38:57.215Z" },
+ { url = "https://files.pythonhosted.org/packages/19/95/6195171e385007300f0f5574592e467c568becce2d937a0b6804f218bc49/pydantic_core-2.46.4-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:962ccbab7b642487b1d8b7df90ef677e03134cf1fd8880bf698649b22a69371f", size = 1951724, upload-time = "2026-05-06T13:37:02.697Z" },
+ { url = "https://files.pythonhosted.org/packages/8e/bc/f47d1ff9cbb1620e1b5b697eef06010035735f07820180e74178226b27b3/pydantic_core-2.46.4-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:8233f2947cf85404441fd7e0085f53b10c93e0ee78611099b5c7237e36aacbf7", size = 1975742, upload-time = "2026-05-06T13:37:09.448Z" },
+ { url = "https://files.pythonhosted.org/packages/5b/11/9b9a5b0306345664a2da6410877af6e8082481b5884b3ddd78d47c6013ce/pydantic_core-2.46.4-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:3a233125ac121aa3ffba9a2b59edfc4a985a76092dc8279586ab4b71390875e7", size = 2052418, upload-time = "2026-05-06T13:37:38.234Z" },
+ { url = "https://files.pythonhosted.org/packages/f1/b7/a65fec226f5d78fc39f4a13c4cc0c768c22b113438f60c14adc9d2865038/pydantic_core-2.46.4-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:5b712b53160b79a5850310b912a5ef8e57e56947c8ad690c227f5c9d7e561712", size = 2232274, upload-time = "2026-05-06T13:38:27.753Z" },
+ { url = "https://files.pythonhosted.org/packages/68/f0/92039db98b907ef49269a8271f67db9cb78ae2fc68062ef7e4e77adb5f61/pydantic_core-2.46.4-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:9401557acd873c3a7f3eb9383edef8ac4968f9510e340f4808d427e75667e7b4", size = 2309940, upload-time = "2026-05-06T13:38:05.353Z" },
+ { url = "https://files.pythonhosted.org/packages/5f/97/2aab507d3d00ca626e8e57c1eac6a79e4e5fbcc63eb99733ff55d1717f65/pydantic_core-2.46.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:926c9541b14b12b1681dca8a0b75feb510b06c6341b70a8e500c2fdcff837cce", size = 2094516, upload-time = "2026-05-06T13:39:10.577Z" },
+ { url = "https://files.pythonhosted.org/packages/22/37/a8aca44d40d737dde2bc05b3c6c07dff0de07ce6f82e9f3167aeaf4d5dea/pydantic_core-2.46.4-cp312-cp312-manylinux_2_31_riscv64.whl", hash = "sha256:56cb4851bcaf3d117eddcef4fe66afd750a50274b0da8e22be256d10e5611987", size = 2136854, upload-time = "2026-05-06T13:40:22.59Z" },
+ { url = "https://files.pythonhosted.org/packages/24/99/fcef1b79238c06a8cbec70819ac722ba76e02bc8ada9b0fd66eba40da01b/pydantic_core-2.46.4-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:c68fcd102d71ea85c5b2dfac3f4f8476eff42a9e078fd5faefff6d145063536b", size = 2180306, upload-time = "2026-05-06T13:40:10.666Z" },
+ { url = "https://files.pythonhosted.org/packages/ae/6c/fc44000918855b42779d007ae63b0532794739027b2f417321cddbc44f6a/pydantic_core-2.46.4-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:b2f69dec1725e79a012d920df1707de5caf7ed5e08f3be4435e25803efc47458", size = 2190044, upload-time = "2026-05-06T13:40:43.231Z" },
+ { url = "https://files.pythonhosted.org/packages/6b/65/d9cadc9f1920d7a127ad2edba16c1db7916e59719285cd6c94600b0080ba/pydantic_core-2.46.4-cp312-cp312-musllinux_1_1_armv7l.whl", hash = "sha256:8d0820e8192167f80d88d64038e609c31452eeca865b4e1d9950a27a4609b00b", size = 2329133, upload-time = "2026-05-06T13:39:57.365Z" },
+ { url = "https://files.pythonhosted.org/packages/d0/cf/c873d91679f3a30bcf5e7ac280ce5573483e72295307685120d0d5ad3416/pydantic_core-2.46.4-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:fbdb89b3e1c94a30cc5edfce477c6e6a5dc4d8f84665b455c27582f211a1c72c", size = 2374464, upload-time = "2026-05-06T13:38:06.976Z" },
+ { url = "https://files.pythonhosted.org/packages/47/bd/6f2fc8188f31bf10590f1e98e7b306336161fac930a8c514cd7bd828c7dc/pydantic_core-2.46.4-cp312-cp312-win32.whl", hash = "sha256:9aa768456404a8bf48a4406685ac2bec8e72b62c69313734fa3b73cf33b3a894", size = 1974823, upload-time = "2026-05-06T13:40:47.985Z" },
+ { url = "https://files.pythonhosted.org/packages/40/8c/985c1d41ea1107c2534abd9870e4ed5c8e7669b5c308297835c001e7a1c4/pydantic_core-2.46.4-cp312-cp312-win_amd64.whl", hash = "sha256:e9c26f834c65f5752f3f06cb08cb86a913ceb7274d0db6e267808a708b46bc89", size = 2072919, upload-time = "2026-05-06T13:39:21.153Z" },
+ { url = "https://files.pythonhosted.org/packages/c4/ba/f463d006e0c47373ca7ec5e1a261c59dc01ef4d62b2657af925fb0deee3a/pydantic_core-2.46.4-cp312-cp312-win_arm64.whl", hash = "sha256:4fc73cb559bdb54b1134a706a2802a4cddd27a0633f5abb7e53056268751ac6a", size = 2027604, upload-time = "2026-05-06T13:39:03.753Z" },
+ { url = "https://files.pythonhosted.org/packages/51/a2/5d30b469c5267a17b39dec53208222f76a8d351dfac4af661888c5aee77d/pydantic_core-2.46.4-cp313-cp313-macosx_10_12_x86_64.whl", hash = "sha256:5d5902252db0d3cedf8d4a1bc68f70eeb430f7e4c7104c8c476753519b423008", size = 2106306, upload-time = "2026-05-06T13:37:48.029Z" },
+ { url = "https://files.pythonhosted.org/packages/c1/81/4fa520eaffa8bd7d1525e644cd6d39e7d60b1592bc5b516693c7340b50f1/pydantic_core-2.46.4-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:c94f0688e7b8d0a67abf40e57a7eaaecd17cc9586706a31b76c031f63df052b4", size = 1951906, upload-time = "2026-05-06T13:37:17.012Z" },
+ { url = "https://files.pythonhosted.org/packages/03/d5/fd02da45b659668b05923b17ba3a0100a0a3d5541e3bd8fcc4ecb711309e/pydantic_core-2.46.4-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:f027324c56cd5406ca49c124b0db10e56c69064fec039acc571c29020cc87c76", size = 1976802, upload-time = "2026-05-06T13:37:35.113Z" },
+ { url = "https://files.pythonhosted.org/packages/21/f2/95727e1368be3d3ed485eaab7adbd7dda408f33f7a36e8b48e0144002b91/pydantic_core-2.46.4-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:e739fee756ba1010f8bcccb534252e85a35fe45ae92c295a06059ce58b74ccd3", size = 2052446, upload-time = "2026-05-06T13:37:12.313Z" },
+ { url = "https://files.pythonhosted.org/packages/9c/86/5d99feea3f77c7234b8718075b23db11532773c1a0dbd9b9490215dc2eeb/pydantic_core-2.46.4-cp313-cp313-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:9d56801be94b86a9da183e5f3766e6310752b99ff647e38b09a9500d88e46e76", size = 2232757, upload-time = "2026-05-06T13:39:01.149Z" },
+ { url = "https://files.pythonhosted.org/packages/d2/3a/508ac615935ef7588cf6d9e9b91309fdc2da751af865e02a9098de88258c/pydantic_core-2.46.4-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:2412e734dcb48da14d4e4006b82b46b74f2518b8a26ee7e58c6844a6cd6d03c4", size = 2309275, upload-time = "2026-05-06T13:37:41.406Z" },
+ { url = "https://files.pythonhosted.org/packages/07/f8/41db9de19d7987d6b04715a02b3b40aea467000275d9d758ffaa31af7d50/pydantic_core-2.46.4-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:9551187363ffc0de2a00b2e47c25aeaeb1020b69b668762966df15fc5659dd5a", size = 2094467, upload-time = "2026-05-06T13:39:18.847Z" },
+ { url = "https://files.pythonhosted.org/packages/2c/e2/f35033184cb11d0052daf4416e8e10a502ea2ac006fc4f459aee872727d1/pydantic_core-2.46.4-cp313-cp313-manylinux_2_31_riscv64.whl", hash = "sha256:0186750b482eefa11d7f435892b09c5c606193ef3375bcf94aa00ae6bfb66262", size = 2134417, upload-time = "2026-05-06T13:40:17.944Z" },
+ { url = "https://files.pythonhosted.org/packages/7e/7b/6ceeb1cc90e193862f444ebe373d8fdf613f0a82572dde03fb10734c6c71/pydantic_core-2.46.4-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:5855698a4856556d86e8e6cd8434bc3ac0314ee8e12089ae0e143f64c6256e4e", size = 2179782, upload-time = "2026-05-06T13:40:32.618Z" },
+ { url = "https://files.pythonhosted.org/packages/5a/f2/c8d7773ede6af08036423a00ae0ceffce266c3c52a096c435d68c896083f/pydantic_core-2.46.4-cp313-cp313-musllinux_1_1_aarch64.whl", hash = "sha256:cbaf13819775b7f769bf4a1f066cb6df7a28d4480081a589828ef190226881cd", size = 2188782, upload-time = "2026-05-06T13:36:51.018Z" },
+ { url = "https://files.pythonhosted.org/packages/59/31/0c864784e31f09f05cdd87606f08923b9c9e7f6e51dd27f20f62f975ce9f/pydantic_core-2.46.4-cp313-cp313-musllinux_1_1_armv7l.whl", hash = "sha256:633147d34cf4550417f12e2b1a0383973bdf5cdfde212cb09e9a581cf10820be", size = 2328334, upload-time = "2026-05-06T13:40:37.764Z" },
+ { url = "https://files.pythonhosted.org/packages/c2/eb/4f6c8a41efa30baa755590f4141abf3a8c370fab610915733e74134a7270/pydantic_core-2.46.4-cp313-cp313-musllinux_1_1_x86_64.whl", hash = "sha256:82cf5301172168103724d49a1444d3378cb20cdee30b116a1bd6031236298a5d", size = 2372986, upload-time = "2026-05-06T13:39:34.152Z" },
+ { url = "https://files.pythonhosted.org/packages/5b/24/b375a480d53113860c299764bfe9f349a3dc9108b3adc0d7f0d786492ebf/pydantic_core-2.46.4-cp313-cp313-win32.whl", hash = "sha256:9fa8ae11da9e2b3126c6426f147e0fba88d96d65921799bb30c6abd1cb2c97fb", size = 1973693, upload-time = "2026-05-06T13:37:55.072Z" },
+ { url = "https://files.pythonhosted.org/packages/7e/e8/cff247591966f2d22ec8c003cd7587e27b7ba7b81ab2fb888e3ab75dc285/pydantic_core-2.46.4-cp313-cp313-win_amd64.whl", hash = "sha256:6b3ace8194b0e5204818c92802dcdca7fc6d88aabbb799d7c795540d9cd6d292", size = 2071819, upload-time = "2026-05-06T13:38:49.139Z" },
+ { url = "https://files.pythonhosted.org/packages/c6/1a/f4aee670d5670e9e148e0c82c7db98d780be566c6e6a97ee8035528ca0b3/pydantic_core-2.46.4-cp313-cp313-win_arm64.whl", hash = "sha256:184c081504d17f1c1066e430e117142b2c77d9448a97f7b65c6ac9fd9aee238d", size = 2027411, upload-time = "2026-05-06T13:40:45.796Z" },
+ { url = "https://files.pythonhosted.org/packages/8d/74/228a26ddad29c6672b805d9fd78e8d251cd04004fa7eed0e622096cd0250/pydantic_core-2.46.4-cp314-cp314-macosx_10_12_x86_64.whl", hash = "sha256:428e04521a40150c85216fc8b85e8d39fece235a9cf5e383761238c7fa9b96fb", size = 2102079, upload-time = "2026-05-06T13:38:41.019Z" },
+ { url = "https://files.pythonhosted.org/packages/ad/1f/8970b150a4b4365623ae00fc88603491f763c627311ae8031e3111356d6e/pydantic_core-2.46.4-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:23ace664830ee0bfe014a0c7bc248b1f7f25ed7ad103852c317624a1083af462", size = 1952179, upload-time = "2026-05-06T13:36:59.812Z" },
+ { url = "https://files.pythonhosted.org/packages/95/30/5211a831ae054928054b2f79731661087a2bc5c01e825c672b3a4a8f1b3e/pydantic_core-2.46.4-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ce5c1d2a8b27468f433ca974829c44060b8097eedc39933e3c206a90ee49c4a9", size = 1978926, upload-time = "2026-05-06T13:37:39.933Z" },
+ { url = "https://files.pythonhosted.org/packages/57/e9/689668733b1eb67adeef047db3c2e8788fcf65a7fd9c9e2b46b7744fe245/pydantic_core-2.46.4-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:7283d57845ecf5a163403eb0702dfc220cc4fbdd18919cb5ccea4f95ee1cdab4", size = 2046785, upload-time = "2026-05-06T13:38:01.995Z" },
+ { url = "https://files.pythonhosted.org/packages/60/d9/6715260422ff50a2109878fd24d948a6c3446bb2664f34ee78cd972b3acd/pydantic_core-2.46.4-cp314-cp314-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:8daafc69c93ee8a0204506a3b6b30f586ef54028f52aeeeb5c4cfc5184fd5914", size = 2228733, upload-time = "2026-05-06T13:40:50.371Z" },
+ { url = "https://files.pythonhosted.org/packages/18/ae/fdb2f64316afca925640f8e70bb1a564b0ec2721c1389e25b8eb4bf9a299/pydantic_core-2.46.4-cp314-cp314-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:cd2213145bcc2ba85884d0ac63d222fece9209678f77b9b4d76f054c561adb28", size = 2307534, upload-time = "2026-05-06T13:37:21.531Z" },
+ { url = "https://files.pythonhosted.org/packages/89/1d/8eff589b45bb8190a9d12c49cfad0f176a5cbd1534908a6b5125e2886239/pydantic_core-2.46.4-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:7a5f930472650a82629163023e630d160863fce524c616f4e5186e5de9d9a49b", size = 2099732, upload-time = "2026-05-06T13:39:31.942Z" },
+ { url = "https://files.pythonhosted.org/packages/06/d5/ee5a3366637fee41dee51a1fc91562dcf12ddbc68fda34e6b253da2324bb/pydantic_core-2.46.4-cp314-cp314-manylinux_2_31_riscv64.whl", hash = "sha256:c1b3f518abeca3aa13c712fd202306e145abf59a18b094a6bafb2d2bbf59192c", size = 2129627, upload-time = "2026-05-06T13:37:25.033Z" },
+ { url = "https://files.pythonhosted.org/packages/94/33/2414be571d2c6a6c4d08be21f9292b6d3fdb08949a97b6dfe985017821db/pydantic_core-2.46.4-cp314-cp314-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:1a7dd0b3ee80d90150e3495a3a13ac34dbcbfd4f012996a6a1d8900e91b5c0fb", size = 2179141, upload-time = "2026-05-06T13:37:14.046Z" },
+ { url = "https://files.pythonhosted.org/packages/7b/79/7daa95be995be0eecc4cf75064cb33f9bbbfe3fe0158caf2f0d4a996a5c7/pydantic_core-2.46.4-cp314-cp314-musllinux_1_1_aarch64.whl", hash = "sha256:3fb702cd90b0446a3a1c5e470bfa0dd23c0233b676a9099ddcc964fa6ca13898", size = 2184325, upload-time = "2026-05-06T13:36:53.615Z" },
+ { url = "https://files.pythonhosted.org/packages/9f/cb/d0a382f5c0de8a222dc61c65348e0ce831b1f68e0a018450d31c2cace3a5/pydantic_core-2.46.4-cp314-cp314-musllinux_1_1_armv7l.whl", hash = "sha256:b8458003118a712e66286df6a707db01c52c0f52f7db8e4a38f0da1d3b94fc4e", size = 2323990, upload-time = "2026-05-06T13:40:29.971Z" },
+ { url = "https://files.pythonhosted.org/packages/05/db/d9ba624cc4a5aced1598e88c04fdbd8310c8a69b9d38b9a3d39ce3a61ed7/pydantic_core-2.46.4-cp314-cp314-musllinux_1_1_x86_64.whl", hash = "sha256:372429a130e469c9cd698925ce5fc50940b7a1336b0d82038e63d5bbc4edc519", size = 2369978, upload-time = "2026-05-06T13:37:23.027Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/20/d15df15ba918c423461905802bfd2981c3af0bfa0e40d05e13edbfa48bc3/pydantic_core-2.46.4-cp314-cp314-win32.whl", hash = "sha256:85bb3611ff1802f3ee7fdd7dbff26b56f343fb432d57a4728fdd49b6ef35e2f4", size = 1966354, upload-time = "2026-05-06T13:38:03.499Z" },
+ { url = "https://files.pythonhosted.org/packages/fc/b6/6b8de4c0a7d7ab3004c439c80c5c1e0a3e8d78bbae19379b01960383d9e5/pydantic_core-2.46.4-cp314-cp314-win_amd64.whl", hash = "sha256:811ff8e9c313ab425368bcbb36e5c4ebd7108c2bbf4e4089cfbb0b01eff63fac", size = 2072238, upload-time = "2026-05-06T13:39:40.807Z" },
+ { url = "https://files.pythonhosted.org/packages/32/36/51eb763beec1f4cf59b1db243a7dcc39cbb41230f050a09b9d69faaf0a48/pydantic_core-2.46.4-cp314-cp314-win_arm64.whl", hash = "sha256:bfec22eab3c8cc2ceec0248aec886624116dc079afa027ecc8ad4a7e62010f8a", size = 2018251, upload-time = "2026-05-06T13:37:26.72Z" },
+ { url = "https://files.pythonhosted.org/packages/e8/91/855af51d625b23aa987116a19e231d2aaef9c4a415273ddc189b79a45fee/pydantic_core-2.46.4-cp314-cp314t-macosx_10_12_x86_64.whl", hash = "sha256:af8244b2bef6aaad6d92cda81372de7f8c8d36c9f0c3ea36e827c60e7d9467a0", size = 2099593, upload-time = "2026-05-06T13:39:47.682Z" },
+ { url = "https://files.pythonhosted.org/packages/fb/1b/8784a54c65edb5f49f0a14d6977cf1b209bba85a4c77445b255c2de58ab3/pydantic_core-2.46.4-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:5a4330cdbc57162e4b3aa303f588ba752257694c9c9be3e7ebb11b4aca659b5d", size = 1935226, upload-time = "2026-05-06T13:40:40.428Z" },
+ { url = "https://files.pythonhosted.org/packages/e8/e7/1955d28d1afc56dd4b3ad7cc0cf39df1b9852964cf16e5d13912756d6d6b/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:29c61fc04a3d840155ff08e475a04809278972fe6aef51e2720554e96367e34b", size = 1974605, upload-time = "2026-05-06T13:37:32.029Z" },
+ { url = "https://files.pythonhosted.org/packages/93/e2/3fedbf0ba7a22850e6e9fd78117f1c0f10f950182344d8a6c535d468fdd8/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:c50f2528cf200c5eed56faf3f4e22fcd5f38c157a8b78576e6ba3168ec35f000", size = 2030777, upload-time = "2026-05-06T13:38:55.239Z" },
+ { url = "https://files.pythonhosted.org/packages/f8/61/46be275fcaaba0b4f5b9669dd852267ce1ff616592dccf7a7845588df091/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:0cbe8b01f948de4286c74cdd6c667aceb38f5c1e26f0693b3983d9d74887c65e", size = 2236641, upload-time = "2026-05-06T13:37:08.096Z" },
+ { url = "https://files.pythonhosted.org/packages/60/db/12e93e46a8bac9988be3c016860f83293daea8c716c029c9ace279036f2f/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:617d7e2ca7dcb8c5cf6bcb8c59b8832c94b36196bbf1cbd1bfb56ed341905edd", size = 2286404, upload-time = "2026-05-06T13:40:20.221Z" },
+ { url = "https://files.pythonhosted.org/packages/e2/4a/4d8b19008f38d31c53b8219cfedc2e3d5de5fe99d90076b7e767de29274f/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:7027560ee92211647d0d34e3f7cd6f50da56399d26a9c8ad0da286d3869a53f3", size = 2109219, upload-time = "2026-05-06T13:38:12.153Z" },
+ { url = "https://files.pythonhosted.org/packages/88/70/3cbc40978fefb7bb09c6708d40d4ad1a5d70fd7213c3d17f971de868ec1f/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_31_riscv64.whl", hash = "sha256:f99626688942fb746e545232e7726926f3be91b5975f8b55327665fafda991c7", size = 2110594, upload-time = "2026-05-06T13:40:02.971Z" },
+ { url = "https://files.pythonhosted.org/packages/9d/20/b8d36736216e29491125531685b2f9e61aa5b4b2599893f8268551da3338/pydantic_core-2.46.4-cp314-cp314t-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:fc3e9034a63de20e15e8ade85358bc6efc614008cab72898b4b4952bea0509ff", size = 2159542, upload-time = "2026-05-06T13:39:27.506Z" },
+ { url = "https://files.pythonhosted.org/packages/1d/a2/367df868eb584dacf6bf82a389272406d7178e301c4ac82545ab98bc2dd9/pydantic_core-2.46.4-cp314-cp314t-musllinux_1_1_aarch64.whl", hash = "sha256:97e7cf2be5c77b7d1a9713a05605d49460d02c6078d38d8bef3cbe323c548424", size = 2168146, upload-time = "2026-05-06T13:38:31.93Z" },
+ { url = "https://files.pythonhosted.org/packages/c1/b8/4460f77f7e201893f649a29ab355dddd3beee8a97bcb1a320db414f9a06e/pydantic_core-2.46.4-cp314-cp314t-musllinux_1_1_armv7l.whl", hash = "sha256:3bf92c5d0e00fefaab325a4d27828fe6b6e2a21848686b5b60d2d9eeb09d76c6", size = 2306309, upload-time = "2026-05-06T13:37:44.717Z" },
+ { url = "https://files.pythonhosted.org/packages/64/c4/be2639293acd87dc8ddbcec41a73cee9b2ebf996fe6d892a1a74e88ad3f7/pydantic_core-2.46.4-cp314-cp314t-musllinux_1_1_x86_64.whl", hash = "sha256:3ecbc122d18468d06ca279dc26a8c2e2d5acb10943bb35e36ae92096dc3b5565", size = 2369736, upload-time = "2026-05-06T13:37:05.645Z" },
+ { url = "https://files.pythonhosted.org/packages/30/a6/9f9f380dbb301f67023bf8f707aaa75daadf84f7152d95c410fd7e81d994/pydantic_core-2.46.4-cp314-cp314t-win32.whl", hash = "sha256:e846ae7835bf0703ae43f534ab79a867146dadd59dc9ca5c8b53d5c8f7c9ef02", size = 1955575, upload-time = "2026-05-06T13:38:51.116Z" },
+ { url = "https://files.pythonhosted.org/packages/40/1f/f1eb9eb350e795d1af8586289746f5c5677d16043040d63710e22abc43c9/pydantic_core-2.46.4-cp314-cp314t-win_amd64.whl", hash = "sha256:2108ba5c1c1eca18030634489dc544844144ee36357f2f9f780b93e7ddbb44b5", size = 2051624, upload-time = "2026-05-06T13:38:21.672Z" },
+ { url = "https://files.pythonhosted.org/packages/f6/d2/42dd53d0a85c27606f316d3aa5d2869c4e8470a5ed6dec30e4a1abe19192/pydantic_core-2.46.4-cp314-cp314t-win_arm64.whl", hash = "sha256:4fcbe087dbc2068af7eda3aa87634eba216dbda64d1ae73c8684b621d33f6596", size = 2017325, upload-time = "2026-05-06T13:40:52.723Z" },
+ { url = "https://files.pythonhosted.org/packages/9d/1d/8987ad40f65ae1432753072f214fb5c74fe47ffbd0698bb9cbbb585664f8/pydantic_core-2.46.4-graalpy312-graalpy250_312_native-macosx_10_12_x86_64.whl", hash = "sha256:1d8ba486450b14f3b1d63bc521d410ec7565e52f887b9fb671791886436a42f7", size = 2095527, upload-time = "2026-05-06T13:39:52.283Z" },
+ { url = "https://files.pythonhosted.org/packages/64/d3/84c282a7eee1d3ac4c0377546ef5a1ea436ce26840d9ac3b7ed54a377507/pydantic_core-2.46.4-graalpy312-graalpy250_312_native-macosx_11_0_arm64.whl", hash = "sha256:3009f12e4e90b7f88b4f9adb1b0c4a3d58fe7820f3238c190047209d148026df", size = 1936024, upload-time = "2026-05-06T13:40:15.671Z" },
+ { url = "https://files.pythonhosted.org/packages/d7/ca/eac61596cdeb4d7e174d3dc0bd8a6238f14f75f97a24e7b7db4c7e7340a0/pydantic_core-2.46.4-graalpy312-graalpy250_312_native-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ad785e92e6dc634c21555edc8bd6b64957ab844541bcb96a1366c202951ae526", size = 1990696, upload-time = "2026-05-06T13:38:34.717Z" },
+ { url = "https://files.pythonhosted.org/packages/fa/c3/7c8b240552251faf6b3a957db200fcfbbcec36763c050428b601e0c9b83b/pydantic_core-2.46.4-graalpy312-graalpy250_312_native-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:00c603d540afdd6b80eb39f078f33ebd46211f02f33e34a32d9f053bba711de0", size = 2147590, upload-time = "2026-05-06T13:39:29.883Z" },
]
[[package]]
name = "pydantic-settings"
-version = "2.10.1"
+version = "2.14.1"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "pydantic" },
{ name = "python-dotenv" },
{ name = "typing-inspection" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/68/85/1ea668bbab3c50071ca613c6ab30047fb36ab0da1b92fa8f17bbc38fd36c/pydantic_settings-2.10.1.tar.gz", hash = "sha256:06f0062169818d0f5524420a360d632d5857b83cffd4d42fe29597807a1614ee", size = 172583, upload-time = "2025-06-24T13:26:46.841Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/07/60/1d1e59c9c90d54591469ada7d268251f71c24bdb765f1a8a832cee8c6653/pydantic_settings-2.14.1.tar.gz", hash = "sha256:e874d3bec7e787b0c9958277956ed9b4dd5de6a80e162188fdaff7c5e26fd5fa", size = 235551, upload-time = "2026-05-08T13:40:06.542Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/58/f0/427018098906416f580e3cf1366d3b1abfb408a0652e9f31600c24a1903c/pydantic_settings-2.10.1-py3-none-any.whl", hash = "sha256:a60952460b99cf661dc25c29c0ef171721f98bfcb52ef8d9ea4c943d7c8cc796", size = 45235, upload-time = "2025-06-24T13:26:45.485Z" },
-]
-
-[[package]]
-name = "pydocket"
-version = "0.17.2"
-source = { registry = "https://pypi.org/simple" }
-dependencies = [
- { name = "cloudpickle" },
- { name = "fakeredis", extra = ["lua"] },
- { name = "opentelemetry-api" },
- { name = "prometheus-client" },
- { name = "py-key-value-aio", extra = ["memory", "redis"] },
- { name = "python-json-logger" },
- { name = "redis" },
- { name = "rich" },
- { name = "typer" },
- { name = "typing-extensions" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/90/17/1fb6309e40bbee999c5d881b8213a1078968412d855e064a9a94cfb9eeef/pydocket-0.17.2.tar.gz", hash = "sha256:8f02c68952701eb1b3a70d439b76392d15f1eb9568d0bde6a69997ea5c79c89f", size = 329829, upload-time = "2026-01-26T16:07:56.217Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/53/74/4c9b70753d5721165047e6428ac239ca083118474794deaca5a27d0ab212/pydocket-0.17.2-py3-none-any.whl", hash = "sha256:f43743b84b4e3d614d99b0cad2deebab028104c217745406ecf9e1efb8926e04", size = 91628, upload-time = "2026-01-26T16:07:55.018Z" },
+ { url = "https://files.pythonhosted.org/packages/ae/8d/f1af3832f5e6eb13ba94ee809e72b8ecb5eef226d27ee0bef7d963d943c7/pydantic_settings-2.14.1-py3-none-any.whl", hash = "sha256:6e3c7edfd8277687cdc598f56e5cff0e9bfff0910a3749deaa8d4401c3a2b9de", size = 60964, upload-time = "2026-05-08T13:40:04.958Z" },
]
[[package]]
@@ -920,11 +859,11 @@ wheels = [
[[package]]
name = "pyjwt"
-version = "2.12.1"
+version = "2.13.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/c2/27/a3b6e5bf6ff856d2509292e95c8f57f0df7017cf5394921fc4e4ef40308a/pyjwt-2.12.1.tar.gz", hash = "sha256:c74a7a2adf861c04d002db713dd85f84beb242228e671280bf709d765b03672b", size = 102564, upload-time = "2026-03-13T19:27:37.25Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/3b/81/58d0ac84e1ef3a3843791d6954d94c0b33d526c75eeb1efbce9d0a4c4077/pyjwt-2.13.0.tar.gz", hash = "sha256:41571c89ca91598c79e8ef18a2d07367d4810fbbd6f637794879baf1b7703423", size = 107515, upload-time = "2026-05-21T19:54:36.618Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/e5/7a/8dd906bd22e79e47397a61742927f6747fe93242ef86645ee9092e610244/pyjwt-2.12.1-py3-none-any.whl", hash = "sha256:28ca37c070cad8ba8cd9790cd940535d40274d22f80ab87f3ac6a713e6e8454c", size = 29726, upload-time = "2026-03-13T19:27:35.677Z" },
+ { url = "https://files.pythonhosted.org/packages/a3/5e/ecf12fdb62546d64385c158514e9b2b671f7832108ef2ecd2020ce0af2d1/pyjwt-2.13.0-py3-none-any.whl", hash = "sha256:66adcc2aff09b3f1bbd95fc1e1577df8ac8723c978552fd43304c8a290ac5728", size = 31274, upload-time = "2026-05-21T19:54:35.362Z" },
]
[package.optional-dependencies]
@@ -934,53 +873,45 @@ crypto = [
[[package]]
name = "pyperclip"
-version = "1.10.0"
+version = "1.11.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/15/99/25f4898cf420efb6f45f519de018f4faea5391114a8618b16736ef3029f1/pyperclip-1.10.0.tar.gz", hash = "sha256:180c8346b1186921c75dfd14d9048a6b5d46bfc499778811952c6dd6eb1ca6be", size = 12193, upload-time = "2025-09-18T00:54:00.384Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/e8/52/d87eba7cb129b81563019d1679026e7a112ef76855d6159d24754dbd2a51/pyperclip-1.11.0.tar.gz", hash = "sha256:244035963e4428530d9e3a6101a1ef97209c6825edab1567beac148ccc1db1b6", size = 12185, upload-time = "2025-09-26T14:40:37.245Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/1e/bc/22540e73c5f5ae18f02924cd3954a6c9a4aa6b713c841a94c98335d333a1/pyperclip-1.10.0-py3-none-any.whl", hash = "sha256:596fbe55dc59263bff26e61d2afbe10223e2fccb5210c9c96a28d6887cfcc7ec", size = 11062, upload-time = "2025-09-18T00:53:59.252Z" },
+ { url = "https://files.pythonhosted.org/packages/df/80/fc9d01d5ed37ba4c42ca2b55b4339ae6e200b456be3a1aaddf4a9fa99b8c/pyperclip-1.11.0-py3-none-any.whl", hash = "sha256:299403e9ff44581cb9ba2ffeed69c7aa96a008622ad0c46cb575ca75b5b84273", size = 11063, upload-time = "2025-09-26T14:40:36.069Z" },
]
[[package]]
name = "pytest"
-version = "8.3.5"
+version = "9.0.3"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "colorama", marker = "sys_platform == 'win32'" },
{ name = "iniconfig" },
{ name = "packaging" },
{ name = "pluggy" },
+ { name = "pygments" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/ae/3c/c9d525a414d506893f0cd8a8d0de7706446213181570cdbd766691164e40/pytest-8.3.5.tar.gz", hash = "sha256:f4efe70cc14e511565ac476b57c279e12a855b11f48f212af1080ef2263d3845", size = 1450891, upload-time = "2025-03-02T12:54:54.503Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/7d/0d/549bd94f1a0a402dc8cf64563a117c0f3765662e2e668477624baeec44d5/pytest-9.0.3.tar.gz", hash = "sha256:b86ada508af81d19edeb213c681b1d48246c1a91d304c6c81a427674c17eb91c", size = 1572165, upload-time = "2026-04-07T17:16:18.027Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/30/3d/64ad57c803f1fa1e963a7946b6e0fea4a70df53c1a7fed304586539c2bac/pytest-8.3.5-py3-none-any.whl", hash = "sha256:c69214aa47deac29fad6c2a4f590b9c4a9fdb16a403176fe154b79c0b4d4d820", size = 343634, upload-time = "2025-03-02T12:54:52.069Z" },
+ { url = "https://files.pythonhosted.org/packages/d4/24/a372aaf5c9b7208e7112038812994107bc65a84cd00e0354a88c2c77a617/pytest-9.0.3-py3-none-any.whl", hash = "sha256:2c5efc453d45394fdd706ade797c0a81091eccd1d6e4bccfcd476e2b8e0ab5d9", size = 375249, upload-time = "2026-04-07T17:16:16.13Z" },
]
[[package]]
name = "python-dotenv"
-version = "1.1.1"
+version = "1.2.2"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/f6/b0/4bc07ccd3572a2f9df7e6782f52b0c6c90dcbb803ac4a167702d7d0dfe1e/python_dotenv-1.1.1.tar.gz", hash = "sha256:a8a6399716257f45be6a007360200409fce5cda2661e3dec71d23dc15f6189ab", size = 41978, upload-time = "2025-06-24T04:21:07.341Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/82/ed/0301aeeac3e5353ef3d94b6ec08bbcabd04a72018415dcb29e588514bba8/python_dotenv-1.2.2.tar.gz", hash = "sha256:2c371a91fbd7ba082c2c1dc1f8bf89ca22564a087c2c287cd9b662adde799cf3", size = 50135, upload-time = "2026-03-01T16:00:26.196Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/5f/ed/539768cf28c661b5b068d66d96a2f155c4971a5d55684a514c1a0e0dec2f/python_dotenv-1.1.1-py3-none-any.whl", hash = "sha256:31f23644fe2602f88ff55e1f5c79ba497e01224ee7737937930c448e4d0e24dc", size = 20556, upload-time = "2025-06-24T04:21:06.073Z" },
-]
-
-[[package]]
-name = "python-json-logger"
-version = "4.0.0"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/29/bf/eca6a3d43db1dae7070f70e160ab20b807627ba953663ba07928cdd3dc58/python_json_logger-4.0.0.tar.gz", hash = "sha256:f58e68eb46e1faed27e0f574a55a0455eecd7b8a5b88b85a784519ba3cff047f", size = 17683, upload-time = "2025-10-06T04:15:18.984Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/51/e5/fecf13f06e5e5f67e8837d777d1bc43fac0ed2b77a676804df5c34744727/python_json_logger-4.0.0-py3-none-any.whl", hash = "sha256:af09c9daf6a813aa4cc7180395f50f2a9e5fa056034c9953aec92e381c5ba1e2", size = 15548, upload-time = "2025-10-06T04:15:17.553Z" },
+ { url = "https://files.pythonhosted.org/packages/0b/d7/1959b9648791274998a9c3526f6d0ec8fd2233e4d4acce81bbae76b44b2a/python_dotenv-1.2.2-py3-none-any.whl", hash = "sha256:1d8214789a24de455a8b8bd8ae6fe3c6b69a5e3d64aa8a8e5d68e694bbcb285a", size = 22101, upload-time = "2026-03-01T16:00:25.09Z" },
]
[[package]]
name = "python-multipart"
-version = "0.0.20"
+version = "0.0.28"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/f3/87/f44d7c9f274c7ee665a29b885ec97089ec5dc034c7f3fafa03da9e39a09e/python_multipart-0.0.20.tar.gz", hash = "sha256:8dd0cab45b8e23064ae09147625994d090fa46f5b0d1e13af944c331a7fa9d13", size = 37158, upload-time = "2024-12-16T19:45:46.972Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/82/54/a85eb421fbdd5007bc5af39d0f4ed9fa609e0fedbfdc2adcf0b34526870e/python_multipart-0.0.28.tar.gz", hash = "sha256:8550da197eac0f7ab748961fc9509b999fa2662ea25cef857f05249f6893c0f8", size = 45314, upload-time = "2026-05-10T11:05:16.596Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/45/58/38b5afbc1a800eeea951b9285d3912613f2603bdf897a4ab0f4bd7f405fc/python_multipart-0.0.20-py3-none-any.whl", hash = "sha256:8a62d3a8335e06589fe01f2a3e178cdcc632f3fbe0d492ad9ee0ec35aab1f104", size = 24546, upload-time = "2024-12-16T19:45:44.423Z" },
+ { url = "https://files.pythonhosted.org/packages/f3/a2/43bbc5860b5034e2af4ef99a0e04d726ff329c43e192ef3abaa8d7ecfce5/python_multipart-0.0.28-py3-none-any.whl", hash = "sha256:10faac07eb966c3f48dc415f9dee46c04cb10d58d30a35677db8027c825ed9b6", size = 29438, upload-time = "2026-05-10T11:05:15.052Z" },
]
[[package]]
@@ -1010,173 +941,194 @@ wheels = [
[[package]]
name = "pyyaml"
-version = "6.0.2"
+version = "6.0.3"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/54/ed/79a089b6be93607fa5cdaedf301d7dfb23af5f25c398d5ead2525b063e17/pyyaml-6.0.2.tar.gz", hash = "sha256:d584d9ec91ad65861cc08d42e834324ef890a082e591037abe114850ff7bbc3e", size = 130631, upload-time = "2024-08-06T20:33:50.674Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/05/8e/961c0007c59b8dd7729d542c61a4d537767a59645b82a0b521206e1e25c2/pyyaml-6.0.3.tar.gz", hash = "sha256:d76623373421df22fb4cf8817020cbb7ef15c725b9d5e45f17e189bfc384190f", size = 130960, upload-time = "2025-09-25T21:33:16.546Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/86/0c/c581167fc46d6d6d7ddcfb8c843a4de25bdd27e4466938109ca68492292c/PyYAML-6.0.2-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:c70c95198c015b85feafc136515252a261a84561b7b1d51e3384e0655ddf25ab", size = 183873, upload-time = "2024-08-06T20:32:25.131Z" },
- { url = "https://files.pythonhosted.org/packages/a8/0c/38374f5bb272c051e2a69281d71cba6fdb983413e6758b84482905e29a5d/PyYAML-6.0.2-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:ce826d6ef20b1bc864f0a68340c8b3287705cae2f8b4b1d932177dcc76721725", size = 173302, upload-time = "2024-08-06T20:32:26.511Z" },
- { url = "https://files.pythonhosted.org/packages/c3/93/9916574aa8c00aa06bbac729972eb1071d002b8e158bd0e83a3b9a20a1f7/PyYAML-6.0.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1f71ea527786de97d1a0cc0eacd1defc0985dcf6b3f17bb77dcfc8c34bec4dc5", size = 739154, upload-time = "2024-08-06T20:32:28.363Z" },
- { url = "https://files.pythonhosted.org/packages/95/0f/b8938f1cbd09739c6da569d172531567dbcc9789e0029aa070856f123984/PyYAML-6.0.2-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:9b22676e8097e9e22e36d6b7bda33190d0d400f345f23d4065d48f4ca7ae0425", size = 766223, upload-time = "2024-08-06T20:32:30.058Z" },
- { url = "https://files.pythonhosted.org/packages/b9/2b/614b4752f2e127db5cc206abc23a8c19678e92b23c3db30fc86ab731d3bd/PyYAML-6.0.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:80bab7bfc629882493af4aa31a4cfa43a4c57c83813253626916b8c7ada83476", size = 767542, upload-time = "2024-08-06T20:32:31.881Z" },
- { url = "https://files.pythonhosted.org/packages/d4/00/dd137d5bcc7efea1836d6264f049359861cf548469d18da90cd8216cf05f/PyYAML-6.0.2-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:0833f8694549e586547b576dcfaba4a6b55b9e96098b36cdc7ebefe667dfed48", size = 731164, upload-time = "2024-08-06T20:32:37.083Z" },
- { url = "https://files.pythonhosted.org/packages/c9/1f/4f998c900485e5c0ef43838363ba4a9723ac0ad73a9dc42068b12aaba4e4/PyYAML-6.0.2-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:8b9c7197f7cb2738065c481a0461e50ad02f18c78cd75775628afb4d7137fb3b", size = 756611, upload-time = "2024-08-06T20:32:38.898Z" },
- { url = "https://files.pythonhosted.org/packages/df/d1/f5a275fdb252768b7a11ec63585bc38d0e87c9e05668a139fea92b80634c/PyYAML-6.0.2-cp312-cp312-win32.whl", hash = "sha256:ef6107725bd54b262d6dedcc2af448a266975032bc85ef0172c5f059da6325b4", size = 140591, upload-time = "2024-08-06T20:32:40.241Z" },
- { url = "https://files.pythonhosted.org/packages/0c/e8/4f648c598b17c3d06e8753d7d13d57542b30d56e6c2dedf9c331ae56312e/PyYAML-6.0.2-cp312-cp312-win_amd64.whl", hash = "sha256:7e7401d0de89a9a855c839bc697c079a4af81cf878373abd7dc625847d25cbd8", size = 156338, upload-time = "2024-08-06T20:32:41.93Z" },
- { url = "https://files.pythonhosted.org/packages/ef/e3/3af305b830494fa85d95f6d95ef7fa73f2ee1cc8ef5b495c7c3269fb835f/PyYAML-6.0.2-cp313-cp313-macosx_10_13_x86_64.whl", hash = "sha256:efdca5630322a10774e8e98e1af481aad470dd62c3170801852d752aa7a783ba", size = 181309, upload-time = "2024-08-06T20:32:43.4Z" },
- { url = "https://files.pythonhosted.org/packages/45/9f/3b1c20a0b7a3200524eb0076cc027a970d320bd3a6592873c85c92a08731/PyYAML-6.0.2-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:50187695423ffe49e2deacb8cd10510bc361faac997de9efef88badc3bb9e2d1", size = 171679, upload-time = "2024-08-06T20:32:44.801Z" },
- { url = "https://files.pythonhosted.org/packages/7c/9a/337322f27005c33bcb656c655fa78325b730324c78620e8328ae28b64d0c/PyYAML-6.0.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:0ffe8360bab4910ef1b9e87fb812d8bc0a308b0d0eef8c8f44e0254ab3b07133", size = 733428, upload-time = "2024-08-06T20:32:46.432Z" },
- { url = "https://files.pythonhosted.org/packages/a3/69/864fbe19e6c18ea3cc196cbe5d392175b4cf3d5d0ac1403ec3f2d237ebb5/PyYAML-6.0.2-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:17e311b6c678207928d649faa7cb0d7b4c26a0ba73d41e99c4fff6b6c3276484", size = 763361, upload-time = "2024-08-06T20:32:51.188Z" },
- { url = "https://files.pythonhosted.org/packages/04/24/b7721e4845c2f162d26f50521b825fb061bc0a5afcf9a386840f23ea19fa/PyYAML-6.0.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:70b189594dbe54f75ab3a1acec5f1e3faa7e8cf2f1e08d9b561cb41b845f69d5", size = 759523, upload-time = "2024-08-06T20:32:53.019Z" },
- { url = "https://files.pythonhosted.org/packages/2b/b2/e3234f59ba06559c6ff63c4e10baea10e5e7df868092bf9ab40e5b9c56b6/PyYAML-6.0.2-cp313-cp313-musllinux_1_1_aarch64.whl", hash = "sha256:41e4e3953a79407c794916fa277a82531dd93aad34e29c2a514c2c0c5fe971cc", size = 726660, upload-time = "2024-08-06T20:32:54.708Z" },
- { url = "https://files.pythonhosted.org/packages/fe/0f/25911a9f080464c59fab9027482f822b86bf0608957a5fcc6eaac85aa515/PyYAML-6.0.2-cp313-cp313-musllinux_1_1_x86_64.whl", hash = "sha256:68ccc6023a3400877818152ad9a1033e3db8625d899c72eacb5a668902e4d652", size = 751597, upload-time = "2024-08-06T20:32:56.985Z" },
- { url = "https://files.pythonhosted.org/packages/14/0d/e2c3b43bbce3cf6bd97c840b46088a3031085179e596d4929729d8d68270/PyYAML-6.0.2-cp313-cp313-win32.whl", hash = "sha256:bc2fa7c6b47d6bc618dd7fb02ef6fdedb1090ec036abab80d4681424b84c1183", size = 140527, upload-time = "2024-08-06T20:33:03.001Z" },
- { url = "https://files.pythonhosted.org/packages/fa/de/02b54f42487e3d3c6efb3f89428677074ca7bf43aae402517bc7cca949f3/PyYAML-6.0.2-cp313-cp313-win_amd64.whl", hash = "sha256:8388ee1976c416731879ac16da0aff3f63b286ffdd57cdeb95f3f2e085687563", size = 156446, upload-time = "2024-08-06T20:33:04.33Z" },
-]
-
-[[package]]
-name = "redis"
-version = "7.1.0"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/43/c8/983d5c6579a411d8a99bc5823cc5712768859b5ce2c8afe1a65b37832c81/redis-7.1.0.tar.gz", hash = "sha256:b1cc3cfa5a2cb9c2ab3ba700864fb0ad75617b41f01352ce5779dabf6d5f9c3c", size = 4796669, upload-time = "2025-11-19T15:54:39.961Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/89/f0/8956f8a86b20d7bb9d6ac0187cf4cd54d8065bc9a1a09eb8011d4d326596/redis-7.1.0-py3-none-any.whl", hash = "sha256:23c52b208f92b56103e17c5d06bdc1a6c2c0b3106583985a76a18f83b265de2b", size = 354159, upload-time = "2025-11-19T15:54:38.064Z" },
+ { url = "https://files.pythonhosted.org/packages/d1/33/422b98d2195232ca1826284a76852ad5a86fe23e31b009c9886b2d0fb8b2/pyyaml-6.0.3-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:7f047e29dcae44602496db43be01ad42fc6f1cc0d8cd6c83d342306c32270196", size = 182063, upload-time = "2025-09-25T21:32:11.445Z" },
+ { url = "https://files.pythonhosted.org/packages/89/a0/6cf41a19a1f2f3feab0e9c0b74134aa2ce6849093d5517a0c550fe37a648/pyyaml-6.0.3-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:fc09d0aa354569bc501d4e787133afc08552722d3ab34836a80547331bb5d4a0", size = 173973, upload-time = "2025-09-25T21:32:12.492Z" },
+ { url = "https://files.pythonhosted.org/packages/ed/23/7a778b6bd0b9a8039df8b1b1d80e2e2ad78aa04171592c8a5c43a56a6af4/pyyaml-6.0.3-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:9149cad251584d5fb4981be1ecde53a1ca46c891a79788c0df828d2f166bda28", size = 775116, upload-time = "2025-09-25T21:32:13.652Z" },
+ { url = "https://files.pythonhosted.org/packages/65/30/d7353c338e12baef4ecc1b09e877c1970bd3382789c159b4f89d6a70dc09/pyyaml-6.0.3-cp312-cp312-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:5fdec68f91a0c6739b380c83b951e2c72ac0197ace422360e6d5a959d8d97b2c", size = 844011, upload-time = "2025-09-25T21:32:15.21Z" },
+ { url = "https://files.pythonhosted.org/packages/8b/9d/b3589d3877982d4f2329302ef98a8026e7f4443c765c46cfecc8858c6b4b/pyyaml-6.0.3-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:ba1cc08a7ccde2d2ec775841541641e4548226580ab850948cbfda66a1befcdc", size = 807870, upload-time = "2025-09-25T21:32:16.431Z" },
+ { url = "https://files.pythonhosted.org/packages/05/c0/b3be26a015601b822b97d9149ff8cb5ead58c66f981e04fedf4e762f4bd4/pyyaml-6.0.3-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:8dc52c23056b9ddd46818a57b78404882310fb473d63f17b07d5c40421e47f8e", size = 761089, upload-time = "2025-09-25T21:32:17.56Z" },
+ { url = "https://files.pythonhosted.org/packages/be/8e/98435a21d1d4b46590d5459a22d88128103f8da4c2d4cb8f14f2a96504e1/pyyaml-6.0.3-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:41715c910c881bc081f1e8872880d3c650acf13dfa8214bad49ed4cede7c34ea", size = 790181, upload-time = "2025-09-25T21:32:18.834Z" },
+ { url = "https://files.pythonhosted.org/packages/74/93/7baea19427dcfbe1e5a372d81473250b379f04b1bd3c4c5ff825e2327202/pyyaml-6.0.3-cp312-cp312-win32.whl", hash = "sha256:96b533f0e99f6579b3d4d4995707cf36df9100d67e0c8303a0c55b27b5f99bc5", size = 137658, upload-time = "2025-09-25T21:32:20.209Z" },
+ { url = "https://files.pythonhosted.org/packages/86/bf/899e81e4cce32febab4fb42bb97dcdf66bc135272882d1987881a4b519e9/pyyaml-6.0.3-cp312-cp312-win_amd64.whl", hash = "sha256:5fcd34e47f6e0b794d17de1b4ff496c00986e1c83f7ab2fb8fcfe9616ff7477b", size = 154003, upload-time = "2025-09-25T21:32:21.167Z" },
+ { url = "https://files.pythonhosted.org/packages/1a/08/67bd04656199bbb51dbed1439b7f27601dfb576fb864099c7ef0c3e55531/pyyaml-6.0.3-cp312-cp312-win_arm64.whl", hash = "sha256:64386e5e707d03a7e172c0701abfb7e10f0fb753ee1d773128192742712a98fd", size = 140344, upload-time = "2025-09-25T21:32:22.617Z" },
+ { url = "https://files.pythonhosted.org/packages/d1/11/0fd08f8192109f7169db964b5707a2f1e8b745d4e239b784a5a1dd80d1db/pyyaml-6.0.3-cp313-cp313-macosx_10_13_x86_64.whl", hash = "sha256:8da9669d359f02c0b91ccc01cac4a67f16afec0dac22c2ad09f46bee0697eba8", size = 181669, upload-time = "2025-09-25T21:32:23.673Z" },
+ { url = "https://files.pythonhosted.org/packages/b1/16/95309993f1d3748cd644e02e38b75d50cbc0d9561d21f390a76242ce073f/pyyaml-6.0.3-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:2283a07e2c21a2aa78d9c4442724ec1eb15f5e42a723b99cb3d822d48f5f7ad1", size = 173252, upload-time = "2025-09-25T21:32:25.149Z" },
+ { url = "https://files.pythonhosted.org/packages/50/31/b20f376d3f810b9b2371e72ef5adb33879b25edb7a6d072cb7ca0c486398/pyyaml-6.0.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:ee2922902c45ae8ccada2c5b501ab86c36525b883eff4255313a253a3160861c", size = 767081, upload-time = "2025-09-25T21:32:26.575Z" },
+ { url = "https://files.pythonhosted.org/packages/49/1e/a55ca81e949270d5d4432fbbd19dfea5321eda7c41a849d443dc92fd1ff7/pyyaml-6.0.3-cp313-cp313-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:a33284e20b78bd4a18c8c2282d549d10bc8408a2a7ff57653c0cf0b9be0afce5", size = 841159, upload-time = "2025-09-25T21:32:27.727Z" },
+ { url = "https://files.pythonhosted.org/packages/74/27/e5b8f34d02d9995b80abcef563ea1f8b56d20134d8f4e5e81733b1feceb2/pyyaml-6.0.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:0f29edc409a6392443abf94b9cf89ce99889a1dd5376d94316ae5145dfedd5d6", size = 801626, upload-time = "2025-09-25T21:32:28.878Z" },
+ { url = "https://files.pythonhosted.org/packages/f9/11/ba845c23988798f40e52ba45f34849aa8a1f2d4af4b798588010792ebad6/pyyaml-6.0.3-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:f7057c9a337546edc7973c0d3ba84ddcdf0daa14533c2065749c9075001090e6", size = 753613, upload-time = "2025-09-25T21:32:30.178Z" },
+ { url = "https://files.pythonhosted.org/packages/3d/e0/7966e1a7bfc0a45bf0a7fb6b98ea03fc9b8d84fa7f2229e9659680b69ee3/pyyaml-6.0.3-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:eda16858a3cab07b80edaf74336ece1f986ba330fdb8ee0d6c0d68fe82bc96be", size = 794115, upload-time = "2025-09-25T21:32:31.353Z" },
+ { url = "https://files.pythonhosted.org/packages/de/94/980b50a6531b3019e45ddeada0626d45fa85cbe22300844a7983285bed3b/pyyaml-6.0.3-cp313-cp313-win32.whl", hash = "sha256:d0eae10f8159e8fdad514efdc92d74fd8d682c933a6dd088030f3834bc8e6b26", size = 137427, upload-time = "2025-09-25T21:32:32.58Z" },
+ { url = "https://files.pythonhosted.org/packages/97/c9/39d5b874e8b28845e4ec2202b5da735d0199dbe5b8fb85f91398814a9a46/pyyaml-6.0.3-cp313-cp313-win_amd64.whl", hash = "sha256:79005a0d97d5ddabfeeea4cf676af11e647e41d81c9a7722a193022accdb6b7c", size = 154090, upload-time = "2025-09-25T21:32:33.659Z" },
+ { url = "https://files.pythonhosted.org/packages/73/e8/2bdf3ca2090f68bb3d75b44da7bbc71843b19c9f2b9cb9b0f4ab7a5a4329/pyyaml-6.0.3-cp313-cp313-win_arm64.whl", hash = "sha256:5498cd1645aa724a7c71c8f378eb29ebe23da2fc0d7a08071d89469bf1d2defb", size = 140246, upload-time = "2025-09-25T21:32:34.663Z" },
+ { url = "https://files.pythonhosted.org/packages/9d/8c/f4bd7f6465179953d3ac9bc44ac1a8a3e6122cf8ada906b4f96c60172d43/pyyaml-6.0.3-cp314-cp314-macosx_10_13_x86_64.whl", hash = "sha256:8d1fab6bb153a416f9aeb4b8763bc0f22a5586065f86f7664fc23339fc1c1fac", size = 181814, upload-time = "2025-09-25T21:32:35.712Z" },
+ { url = "https://files.pythonhosted.org/packages/bd/9c/4d95bb87eb2063d20db7b60faa3840c1b18025517ae857371c4dd55a6b3a/pyyaml-6.0.3-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:34d5fcd24b8445fadc33f9cf348c1047101756fd760b4dacb5c3e99755703310", size = 173809, upload-time = "2025-09-25T21:32:36.789Z" },
+ { url = "https://files.pythonhosted.org/packages/92/b5/47e807c2623074914e29dabd16cbbdd4bf5e9b2db9f8090fa64411fc5382/pyyaml-6.0.3-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:501a031947e3a9025ed4405a168e6ef5ae3126c59f90ce0cd6f2bfc477be31b7", size = 766454, upload-time = "2025-09-25T21:32:37.966Z" },
+ { url = "https://files.pythonhosted.org/packages/02/9e/e5e9b168be58564121efb3de6859c452fccde0ab093d8438905899a3a483/pyyaml-6.0.3-cp314-cp314-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:b3bc83488de33889877a0f2543ade9f70c67d66d9ebb4ac959502e12de895788", size = 836355, upload-time = "2025-09-25T21:32:39.178Z" },
+ { url = "https://files.pythonhosted.org/packages/88/f9/16491d7ed2a919954993e48aa941b200f38040928474c9e85ea9e64222c3/pyyaml-6.0.3-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:c458b6d084f9b935061bc36216e8a69a7e293a2f1e68bf956dcd9e6cbcd143f5", size = 794175, upload-time = "2025-09-25T21:32:40.865Z" },
+ { url = "https://files.pythonhosted.org/packages/dd/3f/5989debef34dc6397317802b527dbbafb2b4760878a53d4166579111411e/pyyaml-6.0.3-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:7c6610def4f163542a622a73fb39f534f8c101d690126992300bf3207eab9764", size = 755228, upload-time = "2025-09-25T21:32:42.084Z" },
+ { url = "https://files.pythonhosted.org/packages/d7/ce/af88a49043cd2e265be63d083fc75b27b6ed062f5f9fd6cdc223ad62f03e/pyyaml-6.0.3-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:5190d403f121660ce8d1d2c1bb2ef1bd05b5f68533fc5c2ea899bd15f4399b35", size = 789194, upload-time = "2025-09-25T21:32:43.362Z" },
+ { url = "https://files.pythonhosted.org/packages/23/20/bb6982b26a40bb43951265ba29d4c246ef0ff59c9fdcdf0ed04e0687de4d/pyyaml-6.0.3-cp314-cp314-win_amd64.whl", hash = "sha256:4a2e8cebe2ff6ab7d1050ecd59c25d4c8bd7e6f400f5f82b96557ac0abafd0ac", size = 156429, upload-time = "2025-09-25T21:32:57.844Z" },
+ { url = "https://files.pythonhosted.org/packages/f4/f4/a4541072bb9422c8a883ab55255f918fa378ecf083f5b85e87fc2b4eda1b/pyyaml-6.0.3-cp314-cp314-win_arm64.whl", hash = "sha256:93dda82c9c22deb0a405ea4dc5f2d0cda384168e466364dec6255b293923b2f3", size = 143912, upload-time = "2025-09-25T21:32:59.247Z" },
+ { url = "https://files.pythonhosted.org/packages/7c/f9/07dd09ae774e4616edf6cda684ee78f97777bdd15847253637a6f052a62f/pyyaml-6.0.3-cp314-cp314t-macosx_10_13_x86_64.whl", hash = "sha256:02893d100e99e03eda1c8fd5c441d8c60103fd175728e23e431db1b589cf5ab3", size = 189108, upload-time = "2025-09-25T21:32:44.377Z" },
+ { url = "https://files.pythonhosted.org/packages/4e/78/8d08c9fb7ce09ad8c38ad533c1191cf27f7ae1effe5bb9400a46d9437fcf/pyyaml-6.0.3-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:c1ff362665ae507275af2853520967820d9124984e0f7466736aea23d8611fba", size = 183641, upload-time = "2025-09-25T21:32:45.407Z" },
+ { url = "https://files.pythonhosted.org/packages/7b/5b/3babb19104a46945cf816d047db2788bcaf8c94527a805610b0289a01c6b/pyyaml-6.0.3-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:6adc77889b628398debc7b65c073bcb99c4a0237b248cacaf3fe8a557563ef6c", size = 831901, upload-time = "2025-09-25T21:32:48.83Z" },
+ { url = "https://files.pythonhosted.org/packages/8b/cc/dff0684d8dc44da4d22a13f35f073d558c268780ce3c6ba1b87055bb0b87/pyyaml-6.0.3-cp314-cp314t-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl", hash = "sha256:a80cb027f6b349846a3bf6d73b5e95e782175e52f22108cfa17876aaeff93702", size = 861132, upload-time = "2025-09-25T21:32:50.149Z" },
+ { url = "https://files.pythonhosted.org/packages/b1/5e/f77dc6b9036943e285ba76b49e118d9ea929885becb0a29ba8a7c75e29fe/pyyaml-6.0.3-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl", hash = "sha256:00c4bdeba853cc34e7dd471f16b4114f4162dc03e6b7afcc2128711f0eca823c", size = 839261, upload-time = "2025-09-25T21:32:51.808Z" },
+ { url = "https://files.pythonhosted.org/packages/ce/88/a9db1376aa2a228197c58b37302f284b5617f56a5d959fd1763fb1675ce6/pyyaml-6.0.3-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:66e1674c3ef6f541c35191caae2d429b967b99e02040f5ba928632d9a7f0f065", size = 805272, upload-time = "2025-09-25T21:32:52.941Z" },
+ { url = "https://files.pythonhosted.org/packages/da/92/1446574745d74df0c92e6aa4a7b0b3130706a4142b2d1a5869f2eaa423c6/pyyaml-6.0.3-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:16249ee61e95f858e83976573de0f5b2893b3677ba71c9dd36b9cf8be9ac6d65", size = 829923, upload-time = "2025-09-25T21:32:54.537Z" },
+ { url = "https://files.pythonhosted.org/packages/f0/7a/1c7270340330e575b92f397352af856a8c06f230aa3e76f86b39d01b416a/pyyaml-6.0.3-cp314-cp314t-win_amd64.whl", hash = "sha256:4ad1906908f2f5ae4e5a8ddfce73c320c2a1429ec52eafd27138b7f1cbe341c9", size = 174062, upload-time = "2025-09-25T21:32:55.767Z" },
+ { url = "https://files.pythonhosted.org/packages/f1/12/de94a39c2ef588c7e6455cfbe7343d3b2dc9d6b6b2f40c4c6565744c873d/pyyaml-6.0.3-cp314-cp314t-win_arm64.whl", hash = "sha256:ebc55a14a21cb14062aa4162f906cd962b28e2e9ea38f9b4391244cd8de4ae0b", size = 149341, upload-time = "2025-09-25T21:32:56.828Z" },
]
[[package]]
name = "referencing"
-version = "0.36.2"
+version = "0.37.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "attrs" },
{ name = "rpds-py" },
{ name = "typing-extensions", marker = "python_full_version < '3.13'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/2f/db/98b5c277be99dd18bfd91dd04e1b759cad18d1a338188c936e92f921c7e2/referencing-0.36.2.tar.gz", hash = "sha256:df2e89862cd09deabbdba16944cc3f10feb6b3e6f18e902f7cc25609a34775aa", size = 74744, upload-time = "2025-01-25T08:48:16.138Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/22/f5/df4e9027acead3ecc63e50fe1e36aca1523e1719559c499951bb4b53188f/referencing-0.37.0.tar.gz", hash = "sha256:44aefc3142c5b842538163acb373e24cce6632bd54bdb01b21ad5863489f50d8", size = 78036, upload-time = "2025-10-13T15:30:48.871Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/c1/b1/3baf80dc6d2b7bc27a95a67752d0208e410351e3feb4eb78de5f77454d8d/referencing-0.36.2-py3-none-any.whl", hash = "sha256:e8699adbbf8b5c7de96d8ffa0eb5c158b3beafce084968e2ea8bb08c6794dcd0", size = 26775, upload-time = "2025-01-25T08:48:14.241Z" },
-]
-
-[[package]]
-name = "requests"
-version = "2.33.1"
-source = { registry = "https://pypi.org/simple" }
-dependencies = [
- { name = "certifi" },
- { name = "charset-normalizer" },
- { name = "idna" },
- { name = "urllib3" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/5f/a4/98b9c7c6428a668bf7e42ebb7c79d576a1c3c1e3ae2d47e674b468388871/requests-2.33.1.tar.gz", hash = "sha256:18817f8c57c6263968bc123d237e3b8b08ac046f5456bd1e307ee8f4250d3517", size = 134120, upload-time = "2026-03-30T16:09:15.531Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/d7/8e/7540e8a2036f79a125c1d2ebadf69ed7901608859186c856fa0388ef4197/requests-2.33.1-py3-none-any.whl", hash = "sha256:4e6d1ef462f3626a1f0a0a9c42dd93c63bad33f9f1c1937509b8c5c8718ab56a", size = 64947, upload-time = "2026-03-30T16:09:13.83Z" },
+ { url = "https://files.pythonhosted.org/packages/2c/58/ca301544e1fa93ed4f80d724bf5b194f6e4b945841c5bfd555878eea9fcb/referencing-0.37.0-py3-none-any.whl", hash = "sha256:381329a9f99628c9069361716891d34ad94af76e461dcb0335825aecc7692231", size = 26766, upload-time = "2025-10-13T15:30:47.625Z" },
]
[[package]]
name = "rich"
-version = "14.1.0"
+version = "15.0.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "markdown-it-py" },
{ name = "pygments" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/fe/75/af448d8e52bf1d8fa6a9d089ca6c07ff4453d86c65c145d0a300bb073b9b/rich-14.1.0.tar.gz", hash = "sha256:e497a48b844b0320d45007cdebfeaeed8db2a4f4bcf49f15e455cfc4af11eaa8", size = 224441, upload-time = "2025-07-25T07:32:58.125Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/c0/8f/0722ca900cc807c13a6a0c696dacf35430f72e0ec571c4275d2371fca3e9/rich-15.0.0.tar.gz", hash = "sha256:edd07a4824c6b40189fb7ac9bc4c52536e9780fbbfbddf6f1e2502c31b068c36", size = 230680, upload-time = "2026-04-12T08:24:00.75Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/e3/30/3c4d035596d3cf444529e0b2953ad0466f6049528a879d27534700580395/rich-14.1.0-py3-none-any.whl", hash = "sha256:536f5f1785986d6dbdea3c75205c473f970777b4a0d6c6dd1b696aa05a3fa04f", size = 243368, upload-time = "2025-07-25T07:32:56.73Z" },
+ { url = "https://files.pythonhosted.org/packages/82/3b/64d4899d73f91ba49a8c18a8ff3f0ea8f1c1d75481760df8c68ef5235bf5/rich-15.0.0-py3-none-any.whl", hash = "sha256:33bd4ef74232fb73fe9279a257718407f169c09b78a87ad3d296f548e27de0bb", size = 310654, upload-time = "2026-04-12T08:24:02.83Z" },
]
[[package]]
name = "rich-rst"
-version = "1.3.1"
+version = "1.3.2"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "docutils" },
{ name = "rich" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/b0/69/5514c3a87b5f10f09a34bb011bc0927bc12c596c8dae5915604e71abc386/rich_rst-1.3.1.tar.gz", hash = "sha256:fad46e3ba42785ea8c1785e2ceaa56e0ffa32dbe5410dec432f37e4107c4f383", size = 13839, upload-time = "2024-04-30T04:40:38.125Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/bc/6d/a506aaa4a9eaa945ed8ab2b7347859f53593864289853c5d6d62b77246e0/rich_rst-1.3.2.tar.gz", hash = "sha256:a1196fdddf1e364b02ec68a05e8ff8f6914fee10fbca2e6b6735f166bb0da8d4", size = 14936, upload-time = "2025-10-14T16:49:45.332Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/fd/bc/cc4e3dbc5e7992398dcb7a8eda0cbcf4fb792a0cdb93f857b478bf3cf884/rich_rst-1.3.1-py3-none-any.whl", hash = "sha256:498a74e3896507ab04492d326e794c3ef76e7cda078703aa592d1853d91098c1", size = 11621, upload-time = "2024-04-30T04:40:32.619Z" },
+ { url = "https://files.pythonhosted.org/packages/13/2f/b4530fbf948867702d0a3f27de4a6aab1d156f406d72852ab902c4d04de9/rich_rst-1.3.2-py3-none-any.whl", hash = "sha256:a99b4907cbe118cf9d18b0b44de272efa61f15117c61e39ebdc431baf5df722a", size = 12567, upload-time = "2025-10-14T16:49:42.953Z" },
]
[[package]]
name = "rpds-py"
-version = "0.27.1"
+version = "0.30.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/e9/dd/2c0cbe774744272b0ae725f44032c77bdcab6e8bcf544bffa3b6e70c8dba/rpds_py-0.27.1.tar.gz", hash = "sha256:26a1c73171d10b7acccbded82bf6a586ab8203601e565badc74bbbf8bc5a10f8", size = 27479, upload-time = "2025-08-27T12:16:36.024Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/20/af/3f2f423103f1113b36230496629986e0ef7e199d2aa8392452b484b38ced/rpds_py-0.30.0.tar.gz", hash = "sha256:dd8ff7cf90014af0c0f787eea34794ebf6415242ee1d6fa91eaba725cc441e84", size = 69469, upload-time = "2025-11-30T20:24:38.837Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/bd/fe/38de28dee5df58b8198c743fe2bea0c785c6d40941b9950bac4cdb71a014/rpds_py-0.27.1-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:ae2775c1973e3c30316892737b91f9283f9908e3cc7625b9331271eaaed7dc90", size = 361887, upload-time = "2025-08-27T12:13:10.233Z" },
- { url = "https://files.pythonhosted.org/packages/7c/9a/4b6c7eedc7dd90986bf0fab6ea2a091ec11c01b15f8ba0a14d3f80450468/rpds_py-0.27.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:2643400120f55c8a96f7c9d858f7be0c88d383cd4653ae2cf0d0c88f668073e5", size = 345795, upload-time = "2025-08-27T12:13:11.65Z" },
- { url = "https://files.pythonhosted.org/packages/6f/0e/e650e1b81922847a09cca820237b0edee69416a01268b7754d506ade11ad/rpds_py-0.27.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:16323f674c089b0360674a4abd28d5042947d54ba620f72514d69be4ff64845e", size = 385121, upload-time = "2025-08-27T12:13:13.008Z" },
- { url = "https://files.pythonhosted.org/packages/1b/ea/b306067a712988e2bff00dcc7c8f31d26c29b6d5931b461aa4b60a013e33/rpds_py-0.27.1-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:9a1f4814b65eacac94a00fc9a526e3fdafd78e439469644032032d0d63de4881", size = 398976, upload-time = "2025-08-27T12:13:14.368Z" },
- { url = "https://files.pythonhosted.org/packages/2c/0a/26dc43c8840cb8fe239fe12dbc8d8de40f2365e838f3d395835dde72f0e5/rpds_py-0.27.1-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:7ba32c16b064267b22f1850a34051121d423b6f7338a12b9459550eb2096e7ec", size = 525953, upload-time = "2025-08-27T12:13:15.774Z" },
- { url = "https://files.pythonhosted.org/packages/22/14/c85e8127b573aaf3a0cbd7fbb8c9c99e735a4a02180c84da2a463b766e9e/rpds_py-0.27.1-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:e5c20f33fd10485b80f65e800bbe5f6785af510b9f4056c5a3c612ebc83ba6cb", size = 407915, upload-time = "2025-08-27T12:13:17.379Z" },
- { url = "https://files.pythonhosted.org/packages/ed/7b/8f4fee9ba1fb5ec856eb22d725a4efa3deb47f769597c809e03578b0f9d9/rpds_py-0.27.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:466bfe65bd932da36ff279ddd92de56b042f2266d752719beb97b08526268ec5", size = 386883, upload-time = "2025-08-27T12:13:18.704Z" },
- { url = "https://files.pythonhosted.org/packages/86/47/28fa6d60f8b74fcdceba81b272f8d9836ac0340570f68f5df6b41838547b/rpds_py-0.27.1-cp312-cp312-manylinux_2_31_riscv64.whl", hash = "sha256:41e532bbdcb57c92ba3be62c42e9f096431b4cf478da9bc3bc6ce5c38ab7ba7a", size = 405699, upload-time = "2025-08-27T12:13:20.089Z" },
- { url = "https://files.pythonhosted.org/packages/d0/fd/c5987b5e054548df56953a21fe2ebed51fc1ec7c8f24fd41c067b68c4a0a/rpds_py-0.27.1-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:f149826d742b406579466283769a8ea448eed82a789af0ed17b0cd5770433444", size = 423713, upload-time = "2025-08-27T12:13:21.436Z" },
- { url = "https://files.pythonhosted.org/packages/ac/ba/3c4978b54a73ed19a7d74531be37a8bcc542d917c770e14d372b8daea186/rpds_py-0.27.1-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:80c60cfb5310677bd67cb1e85a1e8eb52e12529545441b43e6f14d90b878775a", size = 562324, upload-time = "2025-08-27T12:13:22.789Z" },
- { url = "https://files.pythonhosted.org/packages/b5/6c/6943a91768fec16db09a42b08644b960cff540c66aab89b74be6d4a144ba/rpds_py-0.27.1-cp312-cp312-musllinux_1_2_i686.whl", hash = "sha256:7ee6521b9baf06085f62ba9c7a3e5becffbc32480d2f1b351559c001c38ce4c1", size = 593646, upload-time = "2025-08-27T12:13:24.122Z" },
- { url = "https://files.pythonhosted.org/packages/11/73/9d7a8f4be5f4396f011a6bb7a19fe26303a0dac9064462f5651ced2f572f/rpds_py-0.27.1-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:a512c8263249a9d68cac08b05dd59d2b3f2061d99b322813cbcc14c3c7421998", size = 558137, upload-time = "2025-08-27T12:13:25.557Z" },
- { url = "https://files.pythonhosted.org/packages/6e/96/6772cbfa0e2485bcceef8071de7821f81aeac8bb45fbfd5542a3e8108165/rpds_py-0.27.1-cp312-cp312-win32.whl", hash = "sha256:819064fa048ba01b6dadc5116f3ac48610435ac9a0058bbde98e569f9e785c39", size = 221343, upload-time = "2025-08-27T12:13:26.967Z" },
- { url = "https://files.pythonhosted.org/packages/67/b6/c82f0faa9af1c6a64669f73a17ee0eeef25aff30bb9a1c318509efe45d84/rpds_py-0.27.1-cp312-cp312-win_amd64.whl", hash = "sha256:d9199717881f13c32c4046a15f024971a3b78ad4ea029e8da6b86e5aa9cf4594", size = 232497, upload-time = "2025-08-27T12:13:28.326Z" },
- { url = "https://files.pythonhosted.org/packages/e1/96/2817b44bd2ed11aebacc9251da03689d56109b9aba5e311297b6902136e2/rpds_py-0.27.1-cp312-cp312-win_arm64.whl", hash = "sha256:33aa65b97826a0e885ef6e278fbd934e98cdcfed80b63946025f01e2f5b29502", size = 222790, upload-time = "2025-08-27T12:13:29.71Z" },
- { url = "https://files.pythonhosted.org/packages/cc/77/610aeee8d41e39080c7e14afa5387138e3c9fa9756ab893d09d99e7d8e98/rpds_py-0.27.1-cp313-cp313-macosx_10_12_x86_64.whl", hash = "sha256:e4b9fcfbc021633863a37e92571d6f91851fa656f0180246e84cbd8b3f6b329b", size = 361741, upload-time = "2025-08-27T12:13:31.039Z" },
- { url = "https://files.pythonhosted.org/packages/3a/fc/c43765f201c6a1c60be2043cbdb664013def52460a4c7adace89d6682bf4/rpds_py-0.27.1-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:1441811a96eadca93c517d08df75de45e5ffe68aa3089924f963c782c4b898cf", size = 345574, upload-time = "2025-08-27T12:13:32.902Z" },
- { url = "https://files.pythonhosted.org/packages/20/42/ee2b2ca114294cd9847d0ef9c26d2b0851b2e7e00bf14cc4c0b581df0fc3/rpds_py-0.27.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:55266dafa22e672f5a4f65019015f90336ed31c6383bd53f5e7826d21a0e0b83", size = 385051, upload-time = "2025-08-27T12:13:34.228Z" },
- { url = "https://files.pythonhosted.org/packages/fd/e8/1e430fe311e4799e02e2d1af7c765f024e95e17d651612425b226705f910/rpds_py-0.27.1-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:d78827d7ac08627ea2c8e02c9e5b41180ea5ea1f747e9db0915e3adf36b62dcf", size = 398395, upload-time = "2025-08-27T12:13:36.132Z" },
- { url = "https://files.pythonhosted.org/packages/82/95/9dc227d441ff2670651c27a739acb2535ccaf8b351a88d78c088965e5996/rpds_py-0.27.1-cp313-cp313-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:ae92443798a40a92dc5f0b01d8a7c93adde0c4dc965310a29ae7c64d72b9fad2", size = 524334, upload-time = "2025-08-27T12:13:37.562Z" },
- { url = "https://files.pythonhosted.org/packages/87/01/a670c232f401d9ad461d9a332aa4080cd3cb1d1df18213dbd0d2a6a7ab51/rpds_py-0.27.1-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:c46c9dd2403b66a2a3b9720ec4b74d4ab49d4fabf9f03dfdce2d42af913fe8d0", size = 407691, upload-time = "2025-08-27T12:13:38.94Z" },
- { url = "https://files.pythonhosted.org/packages/03/36/0a14aebbaa26fe7fab4780c76f2239e76cc95a0090bdb25e31d95c492fcd/rpds_py-0.27.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:2efe4eb1d01b7f5f1939f4ef30ecea6c6b3521eec451fb93191bf84b2a522418", size = 386868, upload-time = "2025-08-27T12:13:40.192Z" },
- { url = "https://files.pythonhosted.org/packages/3b/03/8c897fb8b5347ff6c1cc31239b9611c5bf79d78c984430887a353e1409a1/rpds_py-0.27.1-cp313-cp313-manylinux_2_31_riscv64.whl", hash = "sha256:15d3b4d83582d10c601f481eca29c3f138d44c92187d197aff663a269197c02d", size = 405469, upload-time = "2025-08-27T12:13:41.496Z" },
- { url = "https://files.pythonhosted.org/packages/da/07/88c60edc2df74850d496d78a1fdcdc7b54360a7f610a4d50008309d41b94/rpds_py-0.27.1-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:4ed2e16abbc982a169d30d1a420274a709949e2cbdef119fe2ec9d870b42f274", size = 422125, upload-time = "2025-08-27T12:13:42.802Z" },
- { url = "https://files.pythonhosted.org/packages/6b/86/5f4c707603e41b05f191a749984f390dabcbc467cf833769b47bf14ba04f/rpds_py-0.27.1-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:a75f305c9b013289121ec0f1181931975df78738cdf650093e6b86d74aa7d8dd", size = 562341, upload-time = "2025-08-27T12:13:44.472Z" },
- { url = "https://files.pythonhosted.org/packages/b2/92/3c0cb2492094e3cd9baf9e49bbb7befeceb584ea0c1a8b5939dca4da12e5/rpds_py-0.27.1-cp313-cp313-musllinux_1_2_i686.whl", hash = "sha256:67ce7620704745881a3d4b0ada80ab4d99df390838839921f99e63c474f82cf2", size = 592511, upload-time = "2025-08-27T12:13:45.898Z" },
- { url = "https://files.pythonhosted.org/packages/10/bb/82e64fbb0047c46a168faa28d0d45a7851cd0582f850b966811d30f67ad8/rpds_py-0.27.1-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:9d992ac10eb86d9b6f369647b6a3f412fc0075cfd5d799530e84d335e440a002", size = 557736, upload-time = "2025-08-27T12:13:47.408Z" },
- { url = "https://files.pythonhosted.org/packages/00/95/3c863973d409210da7fb41958172c6b7dbe7fc34e04d3cc1f10bb85e979f/rpds_py-0.27.1-cp313-cp313-win32.whl", hash = "sha256:4f75e4bd8ab8db624e02c8e2fc4063021b58becdbe6df793a8111d9343aec1e3", size = 221462, upload-time = "2025-08-27T12:13:48.742Z" },
- { url = "https://files.pythonhosted.org/packages/ce/2c/5867b14a81dc217b56d95a9f2a40fdbc56a1ab0181b80132beeecbd4b2d6/rpds_py-0.27.1-cp313-cp313-win_amd64.whl", hash = "sha256:f9025faafc62ed0b75a53e541895ca272815bec18abe2249ff6501c8f2e12b83", size = 232034, upload-time = "2025-08-27T12:13:50.11Z" },
- { url = "https://files.pythonhosted.org/packages/c7/78/3958f3f018c01923823f1e47f1cc338e398814b92d83cd278364446fac66/rpds_py-0.27.1-cp313-cp313-win_arm64.whl", hash = "sha256:ed10dc32829e7d222b7d3b93136d25a406ba9788f6a7ebf6809092da1f4d279d", size = 222392, upload-time = "2025-08-27T12:13:52.587Z" },
- { url = "https://files.pythonhosted.org/packages/01/76/1cdf1f91aed5c3a7bf2eba1f1c4e4d6f57832d73003919a20118870ea659/rpds_py-0.27.1-cp313-cp313t-macosx_10_12_x86_64.whl", hash = "sha256:92022bbbad0d4426e616815b16bc4127f83c9a74940e1ccf3cfe0b387aba0228", size = 358355, upload-time = "2025-08-27T12:13:54.012Z" },
- { url = "https://files.pythonhosted.org/packages/c3/6f/bf142541229374287604caf3bb2a4ae17f0a580798fd72d3b009b532db4e/rpds_py-0.27.1-cp313-cp313t-macosx_11_0_arm64.whl", hash = "sha256:47162fdab9407ec3f160805ac3e154df042e577dd53341745fc7fb3f625e6d92", size = 342138, upload-time = "2025-08-27T12:13:55.791Z" },
- { url = "https://files.pythonhosted.org/packages/1a/77/355b1c041d6be40886c44ff5e798b4e2769e497b790f0f7fd1e78d17e9a8/rpds_py-0.27.1-cp313-cp313t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:fb89bec23fddc489e5d78b550a7b773557c9ab58b7946154a10a6f7a214a48b2", size = 380247, upload-time = "2025-08-27T12:13:57.683Z" },
- { url = "https://files.pythonhosted.org/packages/d6/a4/d9cef5c3946ea271ce2243c51481971cd6e34f21925af2783dd17b26e815/rpds_py-0.27.1-cp313-cp313t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:e48af21883ded2b3e9eb48cb7880ad8598b31ab752ff3be6457001d78f416723", size = 390699, upload-time = "2025-08-27T12:13:59.137Z" },
- { url = "https://files.pythonhosted.org/packages/3a/06/005106a7b8c6c1a7e91b73169e49870f4af5256119d34a361ae5240a0c1d/rpds_py-0.27.1-cp313-cp313t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:6f5b7bd8e219ed50299e58551a410b64daafb5017d54bbe822e003856f06a802", size = 521852, upload-time = "2025-08-27T12:14:00.583Z" },
- { url = "https://files.pythonhosted.org/packages/e5/3e/50fb1dac0948e17a02eb05c24510a8fe12d5ce8561c6b7b7d1339ab7ab9c/rpds_py-0.27.1-cp313-cp313t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:08f1e20bccf73b08d12d804d6e1c22ca5530e71659e6673bce31a6bb71c1e73f", size = 402582, upload-time = "2025-08-27T12:14:02.034Z" },
- { url = "https://files.pythonhosted.org/packages/cb/b0/f4e224090dc5b0ec15f31a02d746ab24101dd430847c4d99123798661bfc/rpds_py-0.27.1-cp313-cp313t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:0dc5dceeaefcc96dc192e3a80bbe1d6c410c469e97bdd47494a7d930987f18b2", size = 384126, upload-time = "2025-08-27T12:14:03.437Z" },
- { url = "https://files.pythonhosted.org/packages/54/77/ac339d5f82b6afff1df8f0fe0d2145cc827992cb5f8eeb90fc9f31ef7a63/rpds_py-0.27.1-cp313-cp313t-manylinux_2_31_riscv64.whl", hash = "sha256:d76f9cc8665acdc0c9177043746775aa7babbf479b5520b78ae4002d889f5c21", size = 399486, upload-time = "2025-08-27T12:14:05.443Z" },
- { url = "https://files.pythonhosted.org/packages/d6/29/3e1c255eee6ac358c056a57d6d6869baa00a62fa32eea5ee0632039c50a3/rpds_py-0.27.1-cp313-cp313t-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:134fae0e36022edad8290a6661edf40c023562964efea0cc0ec7f5d392d2aaef", size = 414832, upload-time = "2025-08-27T12:14:06.902Z" },
- { url = "https://files.pythonhosted.org/packages/3f/db/6d498b844342deb3fa1d030598db93937a9964fcf5cb4da4feb5f17be34b/rpds_py-0.27.1-cp313-cp313t-musllinux_1_2_aarch64.whl", hash = "sha256:eb11a4f1b2b63337cfd3b4d110af778a59aae51c81d195768e353d8b52f88081", size = 557249, upload-time = "2025-08-27T12:14:08.37Z" },
- { url = "https://files.pythonhosted.org/packages/60/f3/690dd38e2310b6f68858a331399b4d6dbb9132c3e8ef8b4333b96caf403d/rpds_py-0.27.1-cp313-cp313t-musllinux_1_2_i686.whl", hash = "sha256:13e608ac9f50a0ed4faec0e90ece76ae33b34c0e8656e3dceb9a7db994c692cd", size = 587356, upload-time = "2025-08-27T12:14:10.034Z" },
- { url = "https://files.pythonhosted.org/packages/86/e3/84507781cccd0145f35b1dc32c72675200c5ce8d5b30f813e49424ef68fc/rpds_py-0.27.1-cp313-cp313t-musllinux_1_2_x86_64.whl", hash = "sha256:dd2135527aa40f061350c3f8f89da2644de26cd73e4de458e79606384f4f68e7", size = 555300, upload-time = "2025-08-27T12:14:11.783Z" },
- { url = "https://files.pythonhosted.org/packages/e5/ee/375469849e6b429b3516206b4580a79e9ef3eb12920ddbd4492b56eaacbe/rpds_py-0.27.1-cp313-cp313t-win32.whl", hash = "sha256:3020724ade63fe320a972e2ffd93b5623227e684315adce194941167fee02688", size = 216714, upload-time = "2025-08-27T12:14:13.629Z" },
- { url = "https://files.pythonhosted.org/packages/21/87/3fc94e47c9bd0742660e84706c311a860dcae4374cf4a03c477e23ce605a/rpds_py-0.27.1-cp313-cp313t-win_amd64.whl", hash = "sha256:8ee50c3e41739886606388ba3ab3ee2aae9f35fb23f833091833255a31740797", size = 228943, upload-time = "2025-08-27T12:14:14.937Z" },
- { url = "https://files.pythonhosted.org/packages/70/36/b6e6066520a07cf029d385de869729a895917b411e777ab1cde878100a1d/rpds_py-0.27.1-cp314-cp314-macosx_10_12_x86_64.whl", hash = "sha256:acb9aafccaae278f449d9c713b64a9e68662e7799dbd5859e2c6b3c67b56d334", size = 362472, upload-time = "2025-08-27T12:14:16.333Z" },
- { url = "https://files.pythonhosted.org/packages/af/07/b4646032e0dcec0df9c73a3bd52f63bc6c5f9cda992f06bd0e73fe3fbebd/rpds_py-0.27.1-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:b7fb801aa7f845ddf601c49630deeeccde7ce10065561d92729bfe81bd21fb33", size = 345676, upload-time = "2025-08-27T12:14:17.764Z" },
- { url = "https://files.pythonhosted.org/packages/b0/16/2f1003ee5d0af4bcb13c0cf894957984c32a6751ed7206db2aee7379a55e/rpds_py-0.27.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:fe0dd05afb46597b9a2e11c351e5e4283c741237e7f617ffb3252780cca9336a", size = 385313, upload-time = "2025-08-27T12:14:19.829Z" },
- { url = "https://files.pythonhosted.org/packages/05/cd/7eb6dd7b232e7f2654d03fa07f1414d7dfc980e82ba71e40a7c46fd95484/rpds_py-0.27.1-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:b6dfb0e058adb12d8b1d1b25f686e94ffa65d9995a5157afe99743bf7369d62b", size = 399080, upload-time = "2025-08-27T12:14:21.531Z" },
- { url = "https://files.pythonhosted.org/packages/20/51/5829afd5000ec1cb60f304711f02572d619040aa3ec033d8226817d1e571/rpds_py-0.27.1-cp314-cp314-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:ed090ccd235f6fa8bb5861684567f0a83e04f52dfc2e5c05f2e4b1309fcf85e7", size = 523868, upload-time = "2025-08-27T12:14:23.485Z" },
- { url = "https://files.pythonhosted.org/packages/05/2c/30eebca20d5db95720ab4d2faec1b5e4c1025c473f703738c371241476a2/rpds_py-0.27.1-cp314-cp314-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:bf876e79763eecf3e7356f157540d6a093cef395b65514f17a356f62af6cc136", size = 408750, upload-time = "2025-08-27T12:14:24.924Z" },
- { url = "https://files.pythonhosted.org/packages/90/1a/cdb5083f043597c4d4276eae4e4c70c55ab5accec078da8611f24575a367/rpds_py-0.27.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:12ed005216a51b1d6e2b02a7bd31885fe317e45897de81d86dcce7d74618ffff", size = 387688, upload-time = "2025-08-27T12:14:27.537Z" },
- { url = "https://files.pythonhosted.org/packages/7c/92/cf786a15320e173f945d205ab31585cc43969743bb1a48b6888f7a2b0a2d/rpds_py-0.27.1-cp314-cp314-manylinux_2_31_riscv64.whl", hash = "sha256:ee4308f409a40e50593c7e3bb8cbe0b4d4c66d1674a316324f0c2f5383b486f9", size = 407225, upload-time = "2025-08-27T12:14:28.981Z" },
- { url = "https://files.pythonhosted.org/packages/33/5c/85ee16df5b65063ef26017bef33096557a4c83fbe56218ac7cd8c235f16d/rpds_py-0.27.1-cp314-cp314-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:0b08d152555acf1f455154d498ca855618c1378ec810646fcd7c76416ac6dc60", size = 423361, upload-time = "2025-08-27T12:14:30.469Z" },
- { url = "https://files.pythonhosted.org/packages/4b/8e/1c2741307fcabd1a334ecf008e92c4f47bb6f848712cf15c923becfe82bb/rpds_py-0.27.1-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:dce51c828941973a5684d458214d3a36fcd28da3e1875d659388f4f9f12cc33e", size = 562493, upload-time = "2025-08-27T12:14:31.987Z" },
- { url = "https://files.pythonhosted.org/packages/04/03/5159321baae9b2222442a70c1f988cbbd66b9be0675dd3936461269be360/rpds_py-0.27.1-cp314-cp314-musllinux_1_2_i686.whl", hash = "sha256:c1476d6f29eb81aa4151c9a31219b03f1f798dc43d8af1250a870735516a1212", size = 592623, upload-time = "2025-08-27T12:14:33.543Z" },
- { url = "https://files.pythonhosted.org/packages/ff/39/c09fd1ad28b85bc1d4554a8710233c9f4cefd03d7717a1b8fbfd171d1167/rpds_py-0.27.1-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:3ce0cac322b0d69b63c9cdb895ee1b65805ec9ffad37639f291dd79467bee675", size = 558800, upload-time = "2025-08-27T12:14:35.436Z" },
- { url = "https://files.pythonhosted.org/packages/c5/d6/99228e6bbcf4baa764b18258f519a9035131d91b538d4e0e294313462a98/rpds_py-0.27.1-cp314-cp314-win32.whl", hash = "sha256:dfbfac137d2a3d0725758cd141f878bf4329ba25e34979797c89474a89a8a3a3", size = 221943, upload-time = "2025-08-27T12:14:36.898Z" },
- { url = "https://files.pythonhosted.org/packages/be/07/c802bc6b8e95be83b79bdf23d1aa61d68324cb1006e245d6c58e959e314d/rpds_py-0.27.1-cp314-cp314-win_amd64.whl", hash = "sha256:a6e57b0abfe7cc513450fcf529eb486b6e4d3f8aee83e92eb5f1ef848218d456", size = 233739, upload-time = "2025-08-27T12:14:38.386Z" },
- { url = "https://files.pythonhosted.org/packages/c8/89/3e1b1c16d4c2d547c5717377a8df99aee8099ff050f87c45cb4d5fa70891/rpds_py-0.27.1-cp314-cp314-win_arm64.whl", hash = "sha256:faf8d146f3d476abfee026c4ae3bdd9ca14236ae4e4c310cbd1cf75ba33d24a3", size = 223120, upload-time = "2025-08-27T12:14:39.82Z" },
- { url = "https://files.pythonhosted.org/packages/62/7e/dc7931dc2fa4a6e46b2a4fa744a9fe5c548efd70e0ba74f40b39fa4a8c10/rpds_py-0.27.1-cp314-cp314t-macosx_10_12_x86_64.whl", hash = "sha256:ba81d2b56b6d4911ce735aad0a1d4495e808b8ee4dc58715998741a26874e7c2", size = 358944, upload-time = "2025-08-27T12:14:41.199Z" },
- { url = "https://files.pythonhosted.org/packages/e6/22/4af76ac4e9f336bfb1a5f240d18a33c6b2fcaadb7472ac7680576512b49a/rpds_py-0.27.1-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:84f7d509870098de0e864cad0102711c1e24e9b1a50ee713b65928adb22269e4", size = 342283, upload-time = "2025-08-27T12:14:42.699Z" },
- { url = "https://files.pythonhosted.org/packages/1c/15/2a7c619b3c2272ea9feb9ade67a45c40b3eeb500d503ad4c28c395dc51b4/rpds_py-0.27.1-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a9e960fc78fecd1100539f14132425e1d5fe44ecb9239f8f27f079962021523e", size = 380320, upload-time = "2025-08-27T12:14:44.157Z" },
- { url = "https://files.pythonhosted.org/packages/a2/7d/4c6d243ba4a3057e994bb5bedd01b5c963c12fe38dde707a52acdb3849e7/rpds_py-0.27.1-cp314-cp314t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:62f85b665cedab1a503747617393573995dac4600ff51869d69ad2f39eb5e817", size = 391760, upload-time = "2025-08-27T12:14:45.845Z" },
- { url = "https://files.pythonhosted.org/packages/b4/71/b19401a909b83bcd67f90221330bc1ef11bc486fe4e04c24388d28a618ae/rpds_py-0.27.1-cp314-cp314t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:fed467af29776f6556250c9ed85ea5a4dd121ab56a5f8b206e3e7a4c551e48ec", size = 522476, upload-time = "2025-08-27T12:14:47.364Z" },
- { url = "https://files.pythonhosted.org/packages/e4/44/1a3b9715c0455d2e2f0f6df5ee6d6f5afdc423d0773a8a682ed2b43c566c/rpds_py-0.27.1-cp314-cp314t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:f2729615f9d430af0ae6b36cf042cb55c0936408d543fb691e1a9e36648fd35a", size = 403418, upload-time = "2025-08-27T12:14:49.991Z" },
- { url = "https://files.pythonhosted.org/packages/1c/4b/fb6c4f14984eb56673bc868a66536f53417ddb13ed44b391998100a06a96/rpds_py-0.27.1-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:1b207d881a9aef7ba753d69c123a35d96ca7cb808056998f6b9e8747321f03b8", size = 384771, upload-time = "2025-08-27T12:14:52.159Z" },
- { url = "https://files.pythonhosted.org/packages/c0/56/d5265d2d28b7420d7b4d4d85cad8ef891760f5135102e60d5c970b976e41/rpds_py-0.27.1-cp314-cp314t-manylinux_2_31_riscv64.whl", hash = "sha256:639fd5efec029f99b79ae47e5d7e00ad8a773da899b6309f6786ecaf22948c48", size = 400022, upload-time = "2025-08-27T12:14:53.859Z" },
- { url = "https://files.pythonhosted.org/packages/8f/e9/9f5fc70164a569bdd6ed9046486c3568d6926e3a49bdefeeccfb18655875/rpds_py-0.27.1-cp314-cp314t-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:fecc80cb2a90e28af8a9b366edacf33d7a91cbfe4c2c4544ea1246e949cfebeb", size = 416787, upload-time = "2025-08-27T12:14:55.673Z" },
- { url = "https://files.pythonhosted.org/packages/d4/64/56dd03430ba491db943a81dcdef115a985aac5f44f565cd39a00c766d45c/rpds_py-0.27.1-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:42a89282d711711d0a62d6f57d81aa43a1368686c45bc1c46b7f079d55692734", size = 557538, upload-time = "2025-08-27T12:14:57.245Z" },
- { url = "https://files.pythonhosted.org/packages/3f/36/92cc885a3129993b1d963a2a42ecf64e6a8e129d2c7cc980dbeba84e55fb/rpds_py-0.27.1-cp314-cp314t-musllinux_1_2_i686.whl", hash = "sha256:cf9931f14223de59551ab9d38ed18d92f14f055a5f78c1d8ad6493f735021bbb", size = 588512, upload-time = "2025-08-27T12:14:58.728Z" },
- { url = "https://files.pythonhosted.org/packages/dd/10/6b283707780a81919f71625351182b4f98932ac89a09023cb61865136244/rpds_py-0.27.1-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:f39f58a27cc6e59f432b568ed8429c7e1641324fbe38131de852cd77b2d534b0", size = 555813, upload-time = "2025-08-27T12:15:00.334Z" },
- { url = "https://files.pythonhosted.org/packages/04/2e/30b5ea18c01379da6272a92825dd7e53dc9d15c88a19e97932d35d430ef7/rpds_py-0.27.1-cp314-cp314t-win32.whl", hash = "sha256:d5fa0ee122dc09e23607a28e6d7b150da16c662e66409bbe85230e4c85bb528a", size = 217385, upload-time = "2025-08-27T12:15:01.937Z" },
- { url = "https://files.pythonhosted.org/packages/32/7d/97119da51cb1dd3f2f3c0805f155a3aa4a95fa44fe7d78ae15e69edf4f34/rpds_py-0.27.1-cp314-cp314t-win_amd64.whl", hash = "sha256:6567d2bb951e21232c2f660c24cf3470bb96de56cdcb3f071a83feeaff8a2772", size = 230097, upload-time = "2025-08-27T12:15:03.961Z" },
+ { url = "https://files.pythonhosted.org/packages/03/e7/98a2f4ac921d82f33e03f3835f5bf3a4a40aa1bfdc57975e74a97b2b4bdd/rpds_py-0.30.0-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:a161f20d9a43006833cd7068375a94d035714d73a172b681d8881820600abfad", size = 375086, upload-time = "2025-11-30T20:22:17.93Z" },
+ { url = "https://files.pythonhosted.org/packages/4d/a1/bca7fd3d452b272e13335db8d6b0b3ecde0f90ad6f16f3328c6fb150c889/rpds_py-0.30.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:6abc8880d9d036ecaafe709079969f56e876fcf107f7a8e9920ba6d5a3878d05", size = 359053, upload-time = "2025-11-30T20:22:19.297Z" },
+ { url = "https://files.pythonhosted.org/packages/65/1c/ae157e83a6357eceff62ba7e52113e3ec4834a84cfe07fa4b0757a7d105f/rpds_py-0.30.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ca28829ae5f5d569bb62a79512c842a03a12576375d5ece7d2cadf8abe96ec28", size = 390763, upload-time = "2025-11-30T20:22:21.661Z" },
+ { url = "https://files.pythonhosted.org/packages/d4/36/eb2eb8515e2ad24c0bd43c3ee9cd74c33f7ca6430755ccdb240fd3144c44/rpds_py-0.30.0-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:a1010ed9524c73b94d15919ca4d41d8780980e1765babf85f9a2f90d247153dd", size = 408951, upload-time = "2025-11-30T20:22:23.408Z" },
+ { url = "https://files.pythonhosted.org/packages/d6/65/ad8dc1784a331fabbd740ef6f71ce2198c7ed0890dab595adb9ea2d775a1/rpds_py-0.30.0-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:f8d1736cfb49381ba528cd5baa46f82fdc65c06e843dab24dd70b63d09121b3f", size = 514622, upload-time = "2025-11-30T20:22:25.16Z" },
+ { url = "https://files.pythonhosted.org/packages/63/8e/0cfa7ae158e15e143fe03993b5bcd743a59f541f5952e1546b1ac1b5fd45/rpds_py-0.30.0-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:d948b135c4693daff7bc2dcfc4ec57237a29bd37e60c2fabf5aff2bbacf3e2f1", size = 414492, upload-time = "2025-11-30T20:22:26.505Z" },
+ { url = "https://files.pythonhosted.org/packages/60/1b/6f8f29f3f995c7ffdde46a626ddccd7c63aefc0efae881dc13b6e5d5bb16/rpds_py-0.30.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:47f236970bccb2233267d89173d3ad2703cd36a0e2a6e92d0560d333871a3d23", size = 394080, upload-time = "2025-11-30T20:22:27.934Z" },
+ { url = "https://files.pythonhosted.org/packages/6d/d5/a266341051a7a3ca2f4b750a3aa4abc986378431fc2da508c5034d081b70/rpds_py-0.30.0-cp312-cp312-manylinux_2_31_riscv64.whl", hash = "sha256:2e6ecb5a5bcacf59c3f912155044479af1d0b6681280048b338b28e364aca1f6", size = 408680, upload-time = "2025-11-30T20:22:29.341Z" },
+ { url = "https://files.pythonhosted.org/packages/10/3b/71b725851df9ab7a7a4e33cf36d241933da66040d195a84781f49c50490c/rpds_py-0.30.0-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:a8fa71a2e078c527c3e9dc9fc5a98c9db40bcc8a92b4e8858e36d329f8684b51", size = 423589, upload-time = "2025-11-30T20:22:31.469Z" },
+ { url = "https://files.pythonhosted.org/packages/00/2b/e59e58c544dc9bd8bd8384ecdb8ea91f6727f0e37a7131baeff8d6f51661/rpds_py-0.30.0-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:73c67f2db7bc334e518d097c6d1e6fed021bbc9b7d678d6cc433478365d1d5f5", size = 573289, upload-time = "2025-11-30T20:22:32.997Z" },
+ { url = "https://files.pythonhosted.org/packages/da/3e/a18e6f5b460893172a7d6a680e86d3b6bc87a54c1f0b03446a3c8c7b588f/rpds_py-0.30.0-cp312-cp312-musllinux_1_2_i686.whl", hash = "sha256:5ba103fb455be00f3b1c2076c9d4264bfcb037c976167a6047ed82f23153f02e", size = 599737, upload-time = "2025-11-30T20:22:34.419Z" },
+ { url = "https://files.pythonhosted.org/packages/5c/e2/714694e4b87b85a18e2c243614974413c60aa107fd815b8cbc42b873d1d7/rpds_py-0.30.0-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:7cee9c752c0364588353e627da8a7e808a66873672bcb5f52890c33fd965b394", size = 563120, upload-time = "2025-11-30T20:22:35.903Z" },
+ { url = "https://files.pythonhosted.org/packages/6f/ab/d5d5e3bcedb0a77f4f613706b750e50a5a3ba1c15ccd3665ecc636c968fd/rpds_py-0.30.0-cp312-cp312-win32.whl", hash = "sha256:1ab5b83dbcf55acc8b08fc62b796ef672c457b17dbd7820a11d6c52c06839bdf", size = 223782, upload-time = "2025-11-30T20:22:37.271Z" },
+ { url = "https://files.pythonhosted.org/packages/39/3b/f786af9957306fdc38a74cef405b7b93180f481fb48453a114bb6465744a/rpds_py-0.30.0-cp312-cp312-win_amd64.whl", hash = "sha256:a090322ca841abd453d43456ac34db46e8b05fd9b3b4ac0c78bcde8b089f959b", size = 240463, upload-time = "2025-11-30T20:22:39.021Z" },
+ { url = "https://files.pythonhosted.org/packages/f3/d2/b91dc748126c1559042cfe41990deb92c4ee3e2b415f6b5234969ffaf0cc/rpds_py-0.30.0-cp312-cp312-win_arm64.whl", hash = "sha256:669b1805bd639dd2989b281be2cfd951c6121b65e729d9b843e9639ef1fd555e", size = 230868, upload-time = "2025-11-30T20:22:40.493Z" },
+ { url = "https://files.pythonhosted.org/packages/ed/dc/d61221eb88ff410de3c49143407f6f3147acf2538c86f2ab7ce65ae7d5f9/rpds_py-0.30.0-cp313-cp313-macosx_10_12_x86_64.whl", hash = "sha256:f83424d738204d9770830d35290ff3273fbb02b41f919870479fab14b9d303b2", size = 374887, upload-time = "2025-11-30T20:22:41.812Z" },
+ { url = "https://files.pythonhosted.org/packages/fd/32/55fb50ae104061dbc564ef15cc43c013dc4a9f4527a1f4d99baddf56fe5f/rpds_py-0.30.0-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:e7536cd91353c5273434b4e003cbda89034d67e7710eab8761fd918ec6c69cf8", size = 358904, upload-time = "2025-11-30T20:22:43.479Z" },
+ { url = "https://files.pythonhosted.org/packages/58/70/faed8186300e3b9bdd138d0273109784eea2396c68458ed580f885dfe7ad/rpds_py-0.30.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:2771c6c15973347f50fece41fc447c054b7ac2ae0502388ce3b6738cd366e3d4", size = 389945, upload-time = "2025-11-30T20:22:44.819Z" },
+ { url = "https://files.pythonhosted.org/packages/bd/a8/073cac3ed2c6387df38f71296d002ab43496a96b92c823e76f46b8af0543/rpds_py-0.30.0-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:0a59119fc6e3f460315fe9d08149f8102aa322299deaa5cab5b40092345c2136", size = 407783, upload-time = "2025-11-30T20:22:46.103Z" },
+ { url = "https://files.pythonhosted.org/packages/77/57/5999eb8c58671f1c11eba084115e77a8899d6e694d2a18f69f0ba471ec8b/rpds_py-0.30.0-cp313-cp313-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:76fec018282b4ead0364022e3c54b60bf368b9d926877957a8624b58419169b7", size = 515021, upload-time = "2025-11-30T20:22:47.458Z" },
+ { url = "https://files.pythonhosted.org/packages/e0/af/5ab4833eadc36c0a8ed2bc5c0de0493c04f6c06de223170bd0798ff98ced/rpds_py-0.30.0-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:692bef75a5525db97318e8cd061542b5a79812d711ea03dbc1f6f8dbb0c5f0d2", size = 414589, upload-time = "2025-11-30T20:22:48.872Z" },
+ { url = "https://files.pythonhosted.org/packages/b7/de/f7192e12b21b9e9a68a6d0f249b4af3fdcdff8418be0767a627564afa1f1/rpds_py-0.30.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:9027da1ce107104c50c81383cae773ef5c24d296dd11c99e2629dbd7967a20c6", size = 394025, upload-time = "2025-11-30T20:22:50.196Z" },
+ { url = "https://files.pythonhosted.org/packages/91/c4/fc70cd0249496493500e7cc2de87504f5aa6509de1e88623431fec76d4b6/rpds_py-0.30.0-cp313-cp313-manylinux_2_31_riscv64.whl", hash = "sha256:9cf69cdda1f5968a30a359aba2f7f9aa648a9ce4b580d6826437f2b291cfc86e", size = 408895, upload-time = "2025-11-30T20:22:51.87Z" },
+ { url = "https://files.pythonhosted.org/packages/58/95/d9275b05ab96556fefff73a385813eb66032e4c99f411d0795372d9abcea/rpds_py-0.30.0-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:a4796a717bf12b9da9d3ad002519a86063dcac8988b030e405704ef7d74d2d9d", size = 422799, upload-time = "2025-11-30T20:22:53.341Z" },
+ { url = "https://files.pythonhosted.org/packages/06/c1/3088fc04b6624eb12a57eb814f0d4997a44b0d208d6cace713033ff1a6ba/rpds_py-0.30.0-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:5d4c2aa7c50ad4728a094ebd5eb46c452e9cb7edbfdb18f9e1221f597a73e1e7", size = 572731, upload-time = "2025-11-30T20:22:54.778Z" },
+ { url = "https://files.pythonhosted.org/packages/d8/42/c612a833183b39774e8ac8fecae81263a68b9583ee343db33ab571a7ce55/rpds_py-0.30.0-cp313-cp313-musllinux_1_2_i686.whl", hash = "sha256:ba81a9203d07805435eb06f536d95a266c21e5b2dfbf6517748ca40c98d19e31", size = 599027, upload-time = "2025-11-30T20:22:56.212Z" },
+ { url = "https://files.pythonhosted.org/packages/5f/60/525a50f45b01d70005403ae0e25f43c0384369ad24ffe46e8d9068b50086/rpds_py-0.30.0-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:945dccface01af02675628334f7cf49c2af4c1c904748efc5cf7bbdf0b579f95", size = 563020, upload-time = "2025-11-30T20:22:58.2Z" },
+ { url = "https://files.pythonhosted.org/packages/0b/5d/47c4655e9bcd5ca907148535c10e7d489044243cc9941c16ed7cd53be91d/rpds_py-0.30.0-cp313-cp313-win32.whl", hash = "sha256:b40fb160a2db369a194cb27943582b38f79fc4887291417685f3ad693c5a1d5d", size = 223139, upload-time = "2025-11-30T20:23:00.209Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/e1/485132437d20aa4d3e1d8b3fb5a5e65aa8139f1e097080c2a8443201742c/rpds_py-0.30.0-cp313-cp313-win_amd64.whl", hash = "sha256:806f36b1b605e2d6a72716f321f20036b9489d29c51c91f4dd29a3e3afb73b15", size = 240224, upload-time = "2025-11-30T20:23:02.008Z" },
+ { url = "https://files.pythonhosted.org/packages/24/95/ffd128ed1146a153d928617b0ef673960130be0009c77d8fbf0abe306713/rpds_py-0.30.0-cp313-cp313-win_arm64.whl", hash = "sha256:d96c2086587c7c30d44f31f42eae4eac89b60dabbac18c7669be3700f13c3ce1", size = 230645, upload-time = "2025-11-30T20:23:03.43Z" },
+ { url = "https://files.pythonhosted.org/packages/ff/1b/b10de890a0def2a319a2626334a7f0ae388215eb60914dbac8a3bae54435/rpds_py-0.30.0-cp313-cp313t-macosx_10_12_x86_64.whl", hash = "sha256:eb0b93f2e5c2189ee831ee43f156ed34e2a89a78a66b98cadad955972548be5a", size = 364443, upload-time = "2025-11-30T20:23:04.878Z" },
+ { url = "https://files.pythonhosted.org/packages/0d/bf/27e39f5971dc4f305a4fb9c672ca06f290f7c4e261c568f3dea16a410d47/rpds_py-0.30.0-cp313-cp313t-macosx_11_0_arm64.whl", hash = "sha256:922e10f31f303c7c920da8981051ff6d8c1a56207dbdf330d9047f6d30b70e5e", size = 353375, upload-time = "2025-11-30T20:23:06.342Z" },
+ { url = "https://files.pythonhosted.org/packages/40/58/442ada3bba6e8e6615fc00483135c14a7538d2ffac30e2d933ccf6852232/rpds_py-0.30.0-cp313-cp313t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:cdc62c8286ba9bf7f47befdcea13ea0e26bf294bda99758fd90535cbaf408000", size = 383850, upload-time = "2025-11-30T20:23:07.825Z" },
+ { url = "https://files.pythonhosted.org/packages/14/14/f59b0127409a33c6ef6f5c1ebd5ad8e32d7861c9c7adfa9a624fc3889f6c/rpds_py-0.30.0-cp313-cp313t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:47f9a91efc418b54fb8190a6b4aa7813a23fb79c51f4bb84e418f5476c38b8db", size = 392812, upload-time = "2025-11-30T20:23:09.228Z" },
+ { url = "https://files.pythonhosted.org/packages/b3/66/e0be3e162ac299b3a22527e8913767d869e6cc75c46bd844aa43fb81ab62/rpds_py-0.30.0-cp313-cp313t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1f3587eb9b17f3789ad50824084fa6f81921bbf9a795826570bda82cb3ed91f2", size = 517841, upload-time = "2025-11-30T20:23:11.186Z" },
+ { url = "https://files.pythonhosted.org/packages/3d/55/fa3b9cf31d0c963ecf1ba777f7cf4b2a2c976795ac430d24a1f43d25a6ba/rpds_py-0.30.0-cp313-cp313t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:39c02563fc592411c2c61d26b6c5fe1e51eaa44a75aa2c8735ca88b0d9599daa", size = 408149, upload-time = "2025-11-30T20:23:12.864Z" },
+ { url = "https://files.pythonhosted.org/packages/60/ca/780cf3b1a32b18c0f05c441958d3758f02544f1d613abf9488cd78876378/rpds_py-0.30.0-cp313-cp313t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:51a1234d8febafdfd33a42d97da7a43f5dcb120c1060e352a3fbc0c6d36e2083", size = 383843, upload-time = "2025-11-30T20:23:14.638Z" },
+ { url = "https://files.pythonhosted.org/packages/82/86/d5f2e04f2aa6247c613da0c1dd87fcd08fa17107e858193566048a1e2f0a/rpds_py-0.30.0-cp313-cp313t-manylinux_2_31_riscv64.whl", hash = "sha256:eb2c4071ab598733724c08221091e8d80e89064cd472819285a9ab0f24bcedb9", size = 396507, upload-time = "2025-11-30T20:23:16.105Z" },
+ { url = "https://files.pythonhosted.org/packages/4b/9a/453255d2f769fe44e07ea9785c8347edaf867f7026872e76c1ad9f7bed92/rpds_py-0.30.0-cp313-cp313t-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:6bdfdb946967d816e6adf9a3d8201bfad269c67efe6cefd7093ef959683c8de0", size = 414949, upload-time = "2025-11-30T20:23:17.539Z" },
+ { url = "https://files.pythonhosted.org/packages/a3/31/622a86cdc0c45d6df0e9ccb6becdba5074735e7033c20e401a6d9d0e2ca0/rpds_py-0.30.0-cp313-cp313t-musllinux_1_2_aarch64.whl", hash = "sha256:c77afbd5f5250bf27bf516c7c4a016813eb2d3e116139aed0096940c5982da94", size = 565790, upload-time = "2025-11-30T20:23:19.029Z" },
+ { url = "https://files.pythonhosted.org/packages/1c/5d/15bbf0fb4a3f58a3b1c67855ec1efcc4ceaef4e86644665fff03e1b66d8d/rpds_py-0.30.0-cp313-cp313t-musllinux_1_2_i686.whl", hash = "sha256:61046904275472a76c8c90c9ccee9013d70a6d0f73eecefd38c1ae7c39045a08", size = 590217, upload-time = "2025-11-30T20:23:20.885Z" },
+ { url = "https://files.pythonhosted.org/packages/6d/61/21b8c41f68e60c8cc3b2e25644f0e3681926020f11d06ab0b78e3c6bbff1/rpds_py-0.30.0-cp313-cp313t-musllinux_1_2_x86_64.whl", hash = "sha256:4c5f36a861bc4b7da6516dbdf302c55313afa09b81931e8280361a4f6c9a2d27", size = 555806, upload-time = "2025-11-30T20:23:22.488Z" },
+ { url = "https://files.pythonhosted.org/packages/f9/39/7e067bb06c31de48de3eb200f9fc7c58982a4d3db44b07e73963e10d3be9/rpds_py-0.30.0-cp313-cp313t-win32.whl", hash = "sha256:3d4a69de7a3e50ffc214ae16d79d8fbb0922972da0356dcf4d0fdca2878559c6", size = 211341, upload-time = "2025-11-30T20:23:24.449Z" },
+ { url = "https://files.pythonhosted.org/packages/0a/4d/222ef0b46443cf4cf46764d9c630f3fe4abaa7245be9417e56e9f52b8f65/rpds_py-0.30.0-cp313-cp313t-win_amd64.whl", hash = "sha256:f14fc5df50a716f7ece6a80b6c78bb35ea2ca47c499e422aa4463455dd96d56d", size = 225768, upload-time = "2025-11-30T20:23:25.908Z" },
+ { url = "https://files.pythonhosted.org/packages/86/81/dad16382ebbd3d0e0328776d8fd7ca94220e4fa0798d1dc5e7da48cb3201/rpds_py-0.30.0-cp314-cp314-macosx_10_12_x86_64.whl", hash = "sha256:68f19c879420aa08f61203801423f6cd5ac5f0ac4ac82a2368a9fcd6a9a075e0", size = 362099, upload-time = "2025-11-30T20:23:27.316Z" },
+ { url = "https://files.pythonhosted.org/packages/2b/60/19f7884db5d5603edf3c6bce35408f45ad3e97e10007df0e17dd57af18f8/rpds_py-0.30.0-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:ec7c4490c672c1a0389d319b3a9cfcd098dcdc4783991553c332a15acf7249be", size = 353192, upload-time = "2025-11-30T20:23:29.151Z" },
+ { url = "https://files.pythonhosted.org/packages/bf/c4/76eb0e1e72d1a9c4703c69607cec123c29028bff28ce41588792417098ac/rpds_py-0.30.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:f251c812357a3fed308d684a5079ddfb9d933860fc6de89f2b7ab00da481e65f", size = 384080, upload-time = "2025-11-30T20:23:30.785Z" },
+ { url = "https://files.pythonhosted.org/packages/72/87/87ea665e92f3298d1b26d78814721dc39ed8d2c74b86e83348d6b48a6f31/rpds_py-0.30.0-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:ac98b175585ecf4c0348fd7b29c3864bda53b805c773cbf7bfdaffc8070c976f", size = 394841, upload-time = "2025-11-30T20:23:32.209Z" },
+ { url = "https://files.pythonhosted.org/packages/77/ad/7783a89ca0587c15dcbf139b4a8364a872a25f861bdb88ed99f9b0dec985/rpds_py-0.30.0-cp314-cp314-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:3e62880792319dbeb7eb866547f2e35973289e7d5696c6e295476448f5b63c87", size = 516670, upload-time = "2025-11-30T20:23:33.742Z" },
+ { url = "https://files.pythonhosted.org/packages/5b/3c/2882bdac942bd2172f3da574eab16f309ae10a3925644e969536553cb4ee/rpds_py-0.30.0-cp314-cp314-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:4e7fc54e0900ab35d041b0601431b0a0eb495f0851a0639b6ef90f7741b39a18", size = 408005, upload-time = "2025-11-30T20:23:35.253Z" },
+ { url = "https://files.pythonhosted.org/packages/ce/81/9a91c0111ce1758c92516a3e44776920b579d9a7c09b2b06b642d4de3f0f/rpds_py-0.30.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:47e77dc9822d3ad616c3d5759ea5631a75e5809d5a28707744ef79d7a1bcfcad", size = 382112, upload-time = "2025-11-30T20:23:36.842Z" },
+ { url = "https://files.pythonhosted.org/packages/cf/8e/1da49d4a107027e5fbc64daeab96a0706361a2918da10cb41769244b805d/rpds_py-0.30.0-cp314-cp314-manylinux_2_31_riscv64.whl", hash = "sha256:b4dc1a6ff022ff85ecafef7979a2c6eb423430e05f1165d6688234e62ba99a07", size = 399049, upload-time = "2025-11-30T20:23:38.343Z" },
+ { url = "https://files.pythonhosted.org/packages/df/5a/7ee239b1aa48a127570ec03becbb29c9d5a9eb092febbd1699d567cae859/rpds_py-0.30.0-cp314-cp314-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:4559c972db3a360808309e06a74628b95eaccbf961c335c8fe0d590cf587456f", size = 415661, upload-time = "2025-11-30T20:23:40.263Z" },
+ { url = "https://files.pythonhosted.org/packages/70/ea/caa143cf6b772f823bc7929a45da1fa83569ee49b11d18d0ada7f5ee6fd6/rpds_py-0.30.0-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:0ed177ed9bded28f8deb6ab40c183cd1192aa0de40c12f38be4d59cd33cb5c65", size = 565606, upload-time = "2025-11-30T20:23:42.186Z" },
+ { url = "https://files.pythonhosted.org/packages/64/91/ac20ba2d69303f961ad8cf55bf7dbdb4763f627291ba3d0d7d67333cced9/rpds_py-0.30.0-cp314-cp314-musllinux_1_2_i686.whl", hash = "sha256:ad1fa8db769b76ea911cb4e10f049d80bf518c104f15b3edb2371cc65375c46f", size = 591126, upload-time = "2025-11-30T20:23:44.086Z" },
+ { url = "https://files.pythonhosted.org/packages/21/20/7ff5f3c8b00c8a95f75985128c26ba44503fb35b8e0259d812766ea966c7/rpds_py-0.30.0-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:46e83c697b1f1c72b50e5ee5adb4353eef7406fb3f2043d64c33f20ad1c2fc53", size = 553371, upload-time = "2025-11-30T20:23:46.004Z" },
+ { url = "https://files.pythonhosted.org/packages/72/c7/81dadd7b27c8ee391c132a6b192111ca58d866577ce2d9b0ca157552cce0/rpds_py-0.30.0-cp314-cp314-win32.whl", hash = "sha256:ee454b2a007d57363c2dfd5b6ca4a5d7e2c518938f8ed3b706e37e5d470801ed", size = 215298, upload-time = "2025-11-30T20:23:47.696Z" },
+ { url = "https://files.pythonhosted.org/packages/3e/d2/1aaac33287e8cfb07aab2e6b8ac1deca62f6f65411344f1433c55e6f3eb8/rpds_py-0.30.0-cp314-cp314-win_amd64.whl", hash = "sha256:95f0802447ac2d10bcc69f6dc28fe95fdf17940367b21d34e34c737870758950", size = 228604, upload-time = "2025-11-30T20:23:49.501Z" },
+ { url = "https://files.pythonhosted.org/packages/e8/95/ab005315818cc519ad074cb7784dae60d939163108bd2b394e60dc7b5461/rpds_py-0.30.0-cp314-cp314-win_arm64.whl", hash = "sha256:613aa4771c99f03346e54c3f038e4cc574ac09a3ddfb0e8878487335e96dead6", size = 222391, upload-time = "2025-11-30T20:23:50.96Z" },
+ { url = "https://files.pythonhosted.org/packages/9e/68/154fe0194d83b973cdedcdcc88947a2752411165930182ae41d983dcefa6/rpds_py-0.30.0-cp314-cp314t-macosx_10_12_x86_64.whl", hash = "sha256:7e6ecfcb62edfd632e56983964e6884851786443739dbfe3582947e87274f7cb", size = 364868, upload-time = "2025-11-30T20:23:52.494Z" },
+ { url = "https://files.pythonhosted.org/packages/83/69/8bbc8b07ec854d92a8b75668c24d2abcb1719ebf890f5604c61c9369a16f/rpds_py-0.30.0-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:a1d0bc22a7cdc173fedebb73ef81e07faef93692b8c1ad3733b67e31e1b6e1b8", size = 353747, upload-time = "2025-11-30T20:23:54.036Z" },
+ { url = "https://files.pythonhosted.org/packages/ab/00/ba2e50183dbd9abcce9497fa5149c62b4ff3e22d338a30d690f9af970561/rpds_py-0.30.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:0d08f00679177226c4cb8c5265012eea897c8ca3b93f429e546600c971bcbae7", size = 383795, upload-time = "2025-11-30T20:23:55.556Z" },
+ { url = "https://files.pythonhosted.org/packages/05/6f/86f0272b84926bcb0e4c972262f54223e8ecc556b3224d281e6598fc9268/rpds_py-0.30.0-cp314-cp314t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:5965af57d5848192c13534f90f9dd16464f3c37aaf166cc1da1cae1fd5a34898", size = 393330, upload-time = "2025-11-30T20:23:57.033Z" },
+ { url = "https://files.pythonhosted.org/packages/cb/e9/0e02bb2e6dc63d212641da45df2b0bf29699d01715913e0d0f017ee29438/rpds_py-0.30.0-cp314-cp314t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:9a4e86e34e9ab6b667c27f3211ca48f73dba7cd3d90f8d5b11be56e5dbc3fb4e", size = 518194, upload-time = "2025-11-30T20:23:58.637Z" },
+ { url = "https://files.pythonhosted.org/packages/ee/ca/be7bca14cf21513bdf9c0606aba17d1f389ea2b6987035eb4f62bd923f25/rpds_py-0.30.0-cp314-cp314t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:e5d3e6b26f2c785d65cc25ef1e5267ccbe1b069c5c21b8cc724efee290554419", size = 408340, upload-time = "2025-11-30T20:24:00.2Z" },
+ { url = "https://files.pythonhosted.org/packages/c2/c7/736e00ebf39ed81d75544c0da6ef7b0998f8201b369acf842f9a90dc8fce/rpds_py-0.30.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:626a7433c34566535b6e56a1b39a7b17ba961e97ce3b80ec62e6f1312c025551", size = 383765, upload-time = "2025-11-30T20:24:01.759Z" },
+ { url = "https://files.pythonhosted.org/packages/4a/3f/da50dfde9956aaf365c4adc9533b100008ed31aea635f2b8d7b627e25b49/rpds_py-0.30.0-cp314-cp314t-manylinux_2_31_riscv64.whl", hash = "sha256:acd7eb3f4471577b9b5a41baf02a978e8bdeb08b4b355273994f8b87032000a8", size = 396834, upload-time = "2025-11-30T20:24:03.687Z" },
+ { url = "https://files.pythonhosted.org/packages/4e/00/34bcc2565b6020eab2623349efbdec810676ad571995911f1abdae62a3a0/rpds_py-0.30.0-cp314-cp314t-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:fe5fa731a1fa8a0a56b0977413f8cacac1768dad38d16b3a296712709476fbd5", size = 415470, upload-time = "2025-11-30T20:24:05.232Z" },
+ { url = "https://files.pythonhosted.org/packages/8c/28/882e72b5b3e6f718d5453bd4d0d9cf8df36fddeb4ddbbab17869d5868616/rpds_py-0.30.0-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:74a3243a411126362712ee1524dfc90c650a503502f135d54d1b352bd01f2404", size = 565630, upload-time = "2025-11-30T20:24:06.878Z" },
+ { url = "https://files.pythonhosted.org/packages/3b/97/04a65539c17692de5b85c6e293520fd01317fd878ea1995f0367d4532fb1/rpds_py-0.30.0-cp314-cp314t-musllinux_1_2_i686.whl", hash = "sha256:3e8eeb0544f2eb0d2581774be4c3410356eba189529a6b3e36bbbf9696175856", size = 591148, upload-time = "2025-11-30T20:24:08.445Z" },
+ { url = "https://files.pythonhosted.org/packages/85/70/92482ccffb96f5441aab93e26c4d66489eb599efdcf96fad90c14bbfb976/rpds_py-0.30.0-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:dbd936cde57abfee19ab3213cf9c26be06d60750e60a8e4dd85d1ab12c8b1f40", size = 556030, upload-time = "2025-11-30T20:24:10.956Z" },
+ { url = "https://files.pythonhosted.org/packages/20/53/7c7e784abfa500a2b6b583b147ee4bb5a2b3747a9166bab52fec4b5b5e7d/rpds_py-0.30.0-cp314-cp314t-win32.whl", hash = "sha256:dc824125c72246d924f7f796b4f63c1e9dc810c7d9e2355864b3c3a73d59ade0", size = 211570, upload-time = "2025-11-30T20:24:12.735Z" },
+ { url = "https://files.pythonhosted.org/packages/d0/02/fa464cdfbe6b26e0600b62c528b72d8608f5cc49f96b8d6e38c95d60c676/rpds_py-0.30.0-cp314-cp314t-win_amd64.whl", hash = "sha256:27f4b0e92de5bfbc6f86e43959e6edd1425c33b5e69aab0984a72047f2bcf1e3", size = 226532, upload-time = "2025-11-30T20:24:14.634Z" },
+]
+
+[[package]]
+name = "ruff"
+version = "0.15.11"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/e4/8d/192f3d7103816158dfd5ea50d098ef2aec19194e6cbccd4b3485bdb2eb2d/ruff-0.15.11.tar.gz", hash = "sha256:f092b21708bf0e7437ce9ada249dfe688ff9a0954fc94abab05dcea7dcd29c33", size = 4637264, upload-time = "2026-04-16T18:46:26.58Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/02/1e/6aca3427f751295ab011828e15e9bf452200ac74484f1db4be0197b8170b/ruff-0.15.11-py3-none-linux_armv6l.whl", hash = "sha256:e927cfff503135c558eb581a0c9792264aae9507904eb27809cdcff2f2c847b7", size = 10607943, upload-time = "2026-04-16T18:46:05.967Z" },
+ { url = "https://files.pythonhosted.org/packages/e7/26/1341c262e74f36d4e84f3d6f4df0ac68cd53331a66bfc5080daa17c84c0b/ruff-0.15.11-py3-none-macosx_10_12_x86_64.whl", hash = "sha256:7a1b5b2938d8f890b76084d4fa843604d787a912541eae85fd7e233398bbb73e", size = 10988592, upload-time = "2026-04-16T18:46:00.742Z" },
+ { url = "https://files.pythonhosted.org/packages/03/71/850b1d6ffa9564fbb6740429bad53df1094082fe515c8c1e74b6d8d05f18/ruff-0.15.11-py3-none-macosx_11_0_arm64.whl", hash = "sha256:d4176f3d194afbdaee6e41b9ccb1a2c287dba8700047df474abfbe773825d1cb", size = 10338501, upload-time = "2026-04-16T18:46:03.723Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/11/cc1284d3e298c45a817a6aadb6c3e1d70b45c9b36d8d9cce3387b495a03a/ruff-0.15.11-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:3b17c886fb88203ced3afe7f14e8d5ae96e9d2f4ccc0ee66aa19f2c2675a27e4", size = 10670693, upload-time = "2026-04-16T18:46:41.941Z" },
+ { url = "https://files.pythonhosted.org/packages/ce/9e/f8288b034ab72b371513c13f9a41d9ba3effac54e24bfb467b007daee2ca/ruff-0.15.11-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:49fafa220220afe7758a487b048de4c8f9f767f37dfefad46b9dd06759d003eb", size = 10416177, upload-time = "2026-04-16T18:46:21.717Z" },
+ { url = "https://files.pythonhosted.org/packages/85/71/504d79abfd3d92532ba6bbe3d1c19fada03e494332a59e37c7c2dabae427/ruff-0.15.11-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:f2ab8427e74a00d93b8bda1307b1e60970d40f304af38bccb218e056c220120d", size = 11221886, upload-time = "2026-04-16T18:46:15.086Z" },
+ { url = "https://files.pythonhosted.org/packages/43/5a/947e6ab7a5ad603d65b474be15a4cbc6d29832db5d762cd142e4e3a74164/ruff-0.15.11-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:195072c0c8e1fc8f940652073df082e37a5d9cb43b4ab1e4d0566ab8977a13b7", size = 12075183, upload-time = "2026-04-16T18:46:07.944Z" },
+ { url = "https://files.pythonhosted.org/packages/9f/a1/0b7bb6268775fdd3a0818aee8efd8f5b4e231d24dd4d528ced2534023182/ruff-0.15.11-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:a3a0996d486af3920dec930a2e7daed4847dfc12649b537a9335585ada163e9e", size = 11516575, upload-time = "2026-04-16T18:46:31.687Z" },
+ { url = "https://files.pythonhosted.org/packages/30/c3/bb5168fc4d233cc06e95f482770d0f3c87945a0cd9f614b90ea8dc2f2833/ruff-0.15.11-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:1bef2cb556d509259f1fe440bb9cd33c756222cf0a7afe90d15edf0866702431", size = 11306537, upload-time = "2026-04-16T18:46:36.988Z" },
+ { url = "https://files.pythonhosted.org/packages/e4/92/4cfae6441f3967317946f3b788136eecf093729b94d6561f963ed810c82e/ruff-0.15.11-py3-none-manylinux_2_31_riscv64.whl", hash = "sha256:030d921a836d7d4a12cf6e8d984a88b66094ccb0e0f17ddd55067c331191bf19", size = 11296813, upload-time = "2026-04-16T18:46:24.182Z" },
+ { url = "https://files.pythonhosted.org/packages/43/26/972784c5dde8313acde8ac71ba8ac65475b85db4a2352a76c9934361f9bc/ruff-0.15.11-py3-none-musllinux_1_2_aarch64.whl", hash = "sha256:0e783b599b4577788dbbb66b9addcef87e9a8832f4ce0c19e34bf55543a2f890", size = 10633136, upload-time = "2026-04-16T18:46:39.802Z" },
+ { url = "https://files.pythonhosted.org/packages/5b/53/3985a4f185020c2f367f2e08a103032e12564829742a1b417980ce1514a0/ruff-0.15.11-py3-none-musllinux_1_2_armv7l.whl", hash = "sha256:ae90592246625ba4a34349d68ec28d4400d75182b71baa196ddb9f82db025ef5", size = 10424701, upload-time = "2026-04-16T18:46:10.381Z" },
+ { url = "https://files.pythonhosted.org/packages/d3/57/bf0dfb32241b56c83bb663a826133da4bf17f682ba8c096973065f6e6a68/ruff-0.15.11-py3-none-musllinux_1_2_i686.whl", hash = "sha256:1f111d62e3c983ed20e0ca2e800f8d77433a5b1161947df99a5c2a3fb60514f0", size = 10873887, upload-time = "2026-04-16T18:46:29.157Z" },
+ { url = "https://files.pythonhosted.org/packages/02/05/e48076b2a57dc33ee8c7a957296f97c744ca891a8ffb4ffb1aaa3b3f517d/ruff-0.15.11-py3-none-musllinux_1_2_x86_64.whl", hash = "sha256:06f483d6646f59eaffba9ae30956370d3a886625f511a3108994000480621d1c", size = 11404316, upload-time = "2026-04-16T18:46:19.462Z" },
+ { url = "https://files.pythonhosted.org/packages/88/27/0195d15fe7a897cbcba0904792c4b7c9fdd958456c3a17d2ea6093716a9a/ruff-0.15.11-py3-none-win32.whl", hash = "sha256:476a2aa56b7da0b73a3ee80b6b2f0e19cce544245479adde7baa65466664d5f3", size = 10655535, upload-time = "2026-04-16T18:46:12.47Z" },
+ { url = "https://files.pythonhosted.org/packages/3a/5e/c927b325bd4c1d3620211a4b96f47864633199feed60fa936025ab27e090/ruff-0.15.11-py3-none-win_amd64.whl", hash = "sha256:8b6756d88d7e234fb0c98c91511aae3cd519d5e3ed271cae31b20f39cb2a12a3", size = 11779692, upload-time = "2026-04-16T18:46:17.268Z" },
+ { url = "https://files.pythonhosted.org/packages/63/b6/aeadee5443e49baa2facd51131159fd6301cc4ccfc1541e4df7b021c37dd/ruff-0.15.11-py3-none-win_arm64.whl", hash = "sha256:063fed18cc1bbe0ee7393957284a6fe8b588c6a406a285af3ee3f46da2391ee4", size = 11032614, upload-time = "2026-04-16T18:46:34.487Z" },
]
[[package]]
@@ -1192,71 +1144,39 @@ wheels = [
{ url = "https://files.pythonhosted.org/packages/b7/46/f5af3402b579fd5e11573ce652019a67074317e18c1935cc0b4ba9b35552/secretstorage-3.5.0-py3-none-any.whl", hash = "sha256:0ce65888c0725fcb2c5bc0fdb8e5438eece02c523557ea40ce0703c266248137", size = 15554, upload-time = "2025-11-23T19:02:51.545Z" },
]
-[[package]]
-name = "shellingham"
-version = "1.5.4"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/58/15/8b3609fd3830ef7b27b655beb4b4e9c62313a4e8da8c676e142cc210d58e/shellingham-1.5.4.tar.gz", hash = "sha256:8dbca0739d487e5bd35ab3ca4b36e11c4078f3a234bfce294b0a0291363404de", size = 10310, upload-time = "2023-10-24T04:13:40.426Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/e0/f9/0595336914c5619e5f28a1fb793285925a8cd4b432c9da0a987836c7f822/shellingham-1.5.4-py2.py3-none-any.whl", hash = "sha256:7ecfff8f2fd72616f7481040475a65b2bf8af90a56c89140852d1120324e8686", size = 9755, upload-time = "2023-10-24T04:13:38.866Z" },
-]
-
-[[package]]
-name = "sniffio"
-version = "1.3.1"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/a2/87/a6771e1546d97e7e041b6ae58d80074f81b7d5121207425c964ddf5cfdbd/sniffio-1.3.1.tar.gz", hash = "sha256:f4324edc670a0f49750a81b895f35c3adb843cca46f0530f79fc1babb23789dc", size = 20372, upload-time = "2024-02-25T23:20:04.057Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/e9/44/75a9c9421471a6c4805dbf2356f7c181a29c1879239abab1ea2cc8f38b40/sniffio-1.3.1-py3-none-any.whl", hash = "sha256:2f6da418d1f1e0fddd844478f41680e794e6051915791a034ff65e5f100525a2", size = 10235, upload-time = "2024-02-25T23:20:01.196Z" },
-]
-
-[[package]]
-name = "sortedcontainers"
-version = "2.4.0"
-source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/e8/c4/ba2f8066cceb6f23394729afe52f3bf7adec04bf9ed2c820b39e19299111/sortedcontainers-2.4.0.tar.gz", hash = "sha256:25caa5a06cc30b6b83d11423433f65d1f9d76c4c6a0c90e3379eaa43b9bfdb88", size = 30594, upload-time = "2021-05-16T22:03:42.897Z" }
-wheels = [
- { url = "https://files.pythonhosted.org/packages/32/46/9cb0e58b2deb7f82b84065f37f3bffeb12413f947f9388e4cac22c4621ce/sortedcontainers-2.4.0-py2.py3-none-any.whl", hash = "sha256:a163dcaede0f1c021485e957a39245190e74249897e2ae4b2aa38595db237ee0", size = 29575, upload-time = "2021-05-16T22:03:41.177Z" },
-]
-
[[package]]
name = "sse-starlette"
-version = "3.0.2"
+version = "3.4.4"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "anyio" },
+ { name = "starlette" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/42/6f/22ed6e33f8a9e76ca0a412405f31abb844b779d52c5f96660766edcd737c/sse_starlette-3.0.2.tar.gz", hash = "sha256:ccd60b5765ebb3584d0de2d7a6e4f745672581de4f5005ab31c3a25d10b52b3a", size = 20985, upload-time = "2025-07-27T09:07:44.565Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/f7/2b/58abc2d1fd397e7dde08e947e05c884d8ef2f78d5e2588c17a12d42d6994/sse_starlette-3.4.4.tar.gz", hash = "sha256:07e0fa0460138baf25cdd5fb28683472c3995dc1642225191b3832d62526bcb0", size = 31819, upload-time = "2026-05-12T17:37:17.019Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/ef/10/c78f463b4ef22eef8491f218f692be838282cd65480f6e423d7730dfd1fb/sse_starlette-3.0.2-py3-none-any.whl", hash = "sha256:16b7cbfddbcd4eaca11f7b586f3b8a080f1afe952c15813455b162edea619e5a", size = 11297, upload-time = "2025-07-27T09:07:43.268Z" },
+ { url = "https://files.pythonhosted.org/packages/dc/67/805710444ea8cc75fbf70b920ed431a560c4bf9c57f7d5a3117213189399/sse_starlette-3.4.4-py3-none-any.whl", hash = "sha256:3f4dd50d8aed2771a091f3a83000323fc3844541c16b4fe585ae2420cc6df973", size = 16514, upload-time = "2026-05-12T17:37:15.601Z" },
]
[[package]]
name = "starlette"
-version = "0.48.0"
+version = "1.3.1"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "anyio" },
{ name = "typing-extensions", marker = "python_full_version < '3.13'" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/a7/a5/d6f429d43394057b67a6b5bbe6eae2f77a6bf7459d961fdb224bf206eee6/starlette-0.48.0.tar.gz", hash = "sha256:7e8cee469a8ab2352911528110ce9088fdc6a37d9876926e73da7ce4aa4c7a46", size = 2652949, upload-time = "2025-09-13T08:41:05.699Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/eb/e3/7c1dc7381d9f8ab7d854328ebfa884e62cb3f3d8549ddfd37c7814f42afa/starlette-1.3.1.tar.gz", hash = "sha256:05d0213193f2fbaae60e2ecb593b4add4262ad4e46536b54abe36f11a71724e0", size = 2703240, upload-time = "2026-06-12T09:23:11.602Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/be/72/2db2f49247d0a18b4f1bb9a5a39a0162869acf235f3a96418363947b3d46/starlette-0.48.0-py3-none-any.whl", hash = "sha256:0764ca97b097582558ecb498132ed0c7d942f233f365b86ba37770e026510659", size = 73736, upload-time = "2025-09-13T08:41:03.869Z" },
+ { url = "https://files.pythonhosted.org/packages/ec/bb/2799cc2ede3ed41131f8975621e7213dfc7ef4acbbaadfa440f32500c370/starlette-1.3.1-py3-none-any.whl", hash = "sha256:c7372aae11c3c3f26a42df7bd626cec2f47d03483d261d369516a615a53714c6", size = 73632, upload-time = "2026-06-12T09:23:10.017Z" },
]
[[package]]
-name = "typer"
-version = "0.21.1"
+name = "stevedore"
+version = "5.7.0"
source = { registry = "https://pypi.org/simple" }
-dependencies = [
- { name = "click" },
- { name = "rich" },
- { name = "shellingham" },
- { name = "typing-extensions" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/36/bf/8825b5929afd84d0dabd606c67cd57b8388cb3ec385f7ef19c5cc2202069/typer-0.21.1.tar.gz", hash = "sha256:ea835607cd752343b6b2b7ce676893e5a0324082268b48f27aa058bdb7d2145d", size = 110371, upload-time = "2026-01-06T11:21:10.989Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/a2/6d/90764092216fa560f6587f83bb70113a8ba510ba436c6476a2b47359057c/stevedore-5.7.0.tar.gz", hash = "sha256:31dd6fe6b3cbe921e21dcefabc9a5f1cf848cf538a1f27543721b8ca09948aa3", size = 516200, upload-time = "2026-02-20T13:27:06.765Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/a0/1d/d9257dd49ff2ca23ea5f132edf1281a0c4f9de8a762b9ae399b670a59235/typer-0.21.1-py3-none-any.whl", hash = "sha256:7985e89081c636b88d172c2ee0cfe33c253160994d47bdfdc302defd7d1f1d01", size = 47381, upload-time = "2026-01-06T11:21:09.824Z" },
+ { url = "https://files.pythonhosted.org/packages/69/06/36d260a695f383345ab5bbc3fd447249594ae2fa8dfd19c533d5ae23f46b/stevedore-5.7.0-py3-none-any.whl", hash = "sha256:fd25efbb32f1abb4c9e502f385f0018632baac11f9ee5d1b70f88cc5e22ad4ed", size = 54483, upload-time = "2026-02-20T13:27:05.561Z" },
]
[[package]]
@@ -1270,74 +1190,167 @@ wheels = [
[[package]]
name = "typing-inspection"
-version = "0.4.1"
+version = "0.4.2"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "typing-extensions" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/f8/b1/0c11f5058406b3af7609f121aaa6b609744687f1d158b3c3a5bf4cc94238/typing_inspection-0.4.1.tar.gz", hash = "sha256:6ae134cc0203c33377d43188d4064e9b357dba58cff3185f22924610e70a9d28", size = 75726, upload-time = "2025-05-21T18:55:23.885Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/55/e3/70399cb7dd41c10ac53367ae42139cf4b1ca5f36bb3dc6c9d33acdb43655/typing_inspection-0.4.2.tar.gz", hash = "sha256:ba561c48a67c5958007083d386c3295464928b01faa735ab8547c5692e87f464", size = 75949, upload-time = "2025-10-01T02:14:41.687Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/17/69/cd203477f944c353c31bade965f880aa1061fd6bf05ded0726ca845b6ff7/typing_inspection-0.4.1-py3-none-any.whl", hash = "sha256:389055682238f53b04f7badcb49b989835495a96700ced5dab2d8feae4b26f51", size = 14552, upload-time = "2025-05-21T18:55:22.152Z" },
+ { url = "https://files.pythonhosted.org/packages/dc/9b/47798a6c91d8bdb567fe2698fe81e0c6b7cb7ef4d13da4114b41d239f65d/typing_inspection-0.4.2-py3-none-any.whl", hash = "sha256:4ed1cacbdc298c220f1bd249ed5287caa16f34d44ef4e9c3d0cbad5b521545e7", size = 14611, upload-time = "2025-10-01T02:14:40.154Z" },
]
[[package]]
-name = "urllib3"
-version = "2.5.0"
+name = "uncalled-for"
+version = "0.3.2"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/15/22/9ee70a2574a4f4599c47dd506532914ce044817c7752a79b6a51286319bc/urllib3-2.5.0.tar.gz", hash = "sha256:3fc47733c7e419d4bc3f6b3dc2b4f890bb743906a30d56ba4a5bfa4bbff92760", size = 393185, upload-time = "2025-06-18T14:07:41.644Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/b5/82/345cc927f7fbdae6065e7768759932fcc827fc20b29b45dfbafa2f1f7da4/uncalled_for-0.3.2.tar.gz", hash = "sha256:89f5dbcd71e2b8f47c030b1fa302e6cce2ec795d1ac565eeb6525c5fe55cb8a2", size = 50032, upload-time = "2026-05-06T13:38:25.204Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/a7/c2/fe1e52489ae3122415c51f387e221dd0773709bad6c6cdaa599e8a2c5185/urllib3-2.5.0-py3-none-any.whl", hash = "sha256:e6b01673c0fa6a13e374b50871808eb3bf7046c4b125b216f6bf1cc604cff0dc", size = 129795, upload-time = "2025-06-18T14:07:40.39Z" },
+ { url = "https://files.pythonhosted.org/packages/3b/25/2c87754f3a9e692315f7b811244090e68f362979fc8886b3fbd2985a1d8c/uncalled_for-0.3.2-py3-none-any.whl", hash = "sha256:0ff60b142c7d1f8070bde9d42afaa70aedc77dcc10998c227687e9c15713418e", size = 11444, upload-time = "2026-05-06T13:38:24.025Z" },
]
[[package]]
name = "uvicorn"
-version = "0.36.0"
+version = "0.46.0"
source = { registry = "https://pypi.org/simple" }
dependencies = [
{ name = "click" },
{ name = "h11" },
]
-sdist = { url = "https://files.pythonhosted.org/packages/ef/5e/f0cd46063a02fd8515f0e880c37d2657845b7306c16ce6c4ffc44afd9036/uvicorn-0.36.0.tar.gz", hash = "sha256:527dc68d77819919d90a6b267be55f0e76704dca829d34aea9480be831a9b9d9", size = 80032, upload-time = "2025-09-20T01:07:14.418Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/1f/93/041fca8274050e40e6791f267d82e0e2e27dd165627bd640d3e0e378d877/uvicorn-0.46.0.tar.gz", hash = "sha256:fb9da0926999cc6cb22dc7cd71a94a632f078e6ae47ff683c5c420750fb7413d", size = 88758, upload-time = "2026-04-23T07:16:00.151Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/96/06/5cc0542b47c0338c1cb676b348e24a1c29acabc81000bced518231dded6f/uvicorn-0.36.0-py3-none-any.whl", hash = "sha256:6bb4ba67f16024883af8adf13aba3a9919e415358604ce46780d3f9bdc36d731", size = 67675, upload-time = "2025-09-20T01:07:12.984Z" },
+ { url = "https://files.pythonhosted.org/packages/31/a3/5b1562db76a5a488274b2332a97199b32d0442aca0ed193697fd47786316/uvicorn-0.46.0-py3-none-any.whl", hash = "sha256:bbebbcbed972d162afca128605223022bedd345b7bc7855ce66deb31487a9048", size = 70926, upload-time = "2026-04-23T07:15:58.355Z" },
+]
+
+[[package]]
+name = "vulture"
+version = "2.14"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/8e/25/925f35db758a0f9199113aaf61d703de891676b082bd7cf73ea01d6000f7/vulture-2.14.tar.gz", hash = "sha256:cb8277902a1138deeab796ec5bef7076a6e0248ca3607a3f3dee0b6d9e9b8415", size = 58823, upload-time = "2024-12-08T17:39:43.319Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/a0/56/0cc15b8ff2613c1d5c3dc1f3f576ede1c43868c1bc2e5ccaa2d4bcd7974d/vulture-2.14-py2.py3-none-any.whl", hash = "sha256:d9a90dba89607489548a49d557f8bac8112bd25d3cbc8aeef23e860811bd5ed9", size = 28915, upload-time = "2024-12-08T17:39:40.573Z" },
+]
+
+[[package]]
+name = "watchfiles"
+version = "1.1.1"
+source = { registry = "https://pypi.org/simple" }
+dependencies = [
+ { name = "anyio" },
+]
+sdist = { url = "https://files.pythonhosted.org/packages/c2/c9/8869df9b2a2d6c59d79220a4db37679e74f807c559ffe5265e08b227a210/watchfiles-1.1.1.tar.gz", hash = "sha256:a173cb5c16c4f40ab19cecf48a534c409f7ea983ab8fed0741304a1c0a31b3f2", size = 94440, upload-time = "2025-10-14T15:06:21.08Z" }
+wheels = [
+ { url = "https://files.pythonhosted.org/packages/74/d5/f039e7e3c639d9b1d09b07ea412a6806d38123f0508e5f9b48a87b0a76cc/watchfiles-1.1.1-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:8c89f9f2f740a6b7dcc753140dd5e1ab9215966f7a3530d0c0705c83b401bd7d", size = 404745, upload-time = "2025-10-14T15:04:46.731Z" },
+ { url = "https://files.pythonhosted.org/packages/a5/96/a881a13aa1349827490dab2d363c8039527060cfcc2c92cc6d13d1b1049e/watchfiles-1.1.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:bd404be08018c37350f0d6e34676bd1e2889990117a2b90070b3007f172d0610", size = 391769, upload-time = "2025-10-14T15:04:48.003Z" },
+ { url = "https://files.pythonhosted.org/packages/4b/5b/d3b460364aeb8da471c1989238ea0e56bec24b6042a68046adf3d9ddb01c/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:8526e8f916bb5b9a0a777c8317c23ce65de259422bba5b31325a6fa6029d33af", size = 449374, upload-time = "2025-10-14T15:04:49.179Z" },
+ { url = "https://files.pythonhosted.org/packages/b9/44/5769cb62d4ed055cb17417c0a109a92f007114a4e07f30812a73a4efdb11/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:2edc3553362b1c38d9f06242416a5d8e9fe235c204a4072e988ce2e5bb1f69f6", size = 459485, upload-time = "2025-10-14T15:04:50.155Z" },
+ { url = "https://files.pythonhosted.org/packages/19/0c/286b6301ded2eccd4ffd0041a1b726afda999926cf720aab63adb68a1e36/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:30f7da3fb3f2844259cba4720c3fc7138eb0f7b659c38f3bfa65084c7fc7abce", size = 488813, upload-time = "2025-10-14T15:04:51.059Z" },
+ { url = "https://files.pythonhosted.org/packages/c7/2b/8530ed41112dd4a22f4dcfdb5ccf6a1baad1ff6eed8dc5a5f09e7e8c41c7/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:f8979280bdafff686ba5e4d8f97840f929a87ed9cdf133cbbd42f7766774d2aa", size = 594816, upload-time = "2025-10-14T15:04:52.031Z" },
+ { url = "https://files.pythonhosted.org/packages/ce/d2/f5f9fb49489f184f18470d4f99f4e862a4b3e9ac2865688eb2099e3d837a/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:dcc5c24523771db3a294c77d94771abcfcb82a0e0ee8efd910c37c59ec1b31bb", size = 475186, upload-time = "2025-10-14T15:04:53.064Z" },
+ { url = "https://files.pythonhosted.org/packages/cf/68/5707da262a119fb06fbe214d82dd1fe4a6f4af32d2d14de368d0349eb52a/watchfiles-1.1.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:1db5d7ae38ff20153d542460752ff397fcf5c96090c1230803713cf3147a6803", size = 456812, upload-time = "2025-10-14T15:04:55.174Z" },
+ { url = "https://files.pythonhosted.org/packages/66/ab/3cbb8756323e8f9b6f9acb9ef4ec26d42b2109bce830cc1f3468df20511d/watchfiles-1.1.1-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:28475ddbde92df1874b6c5c8aaeb24ad5be47a11f87cde5a28ef3835932e3e94", size = 630196, upload-time = "2025-10-14T15:04:56.22Z" },
+ { url = "https://files.pythonhosted.org/packages/78/46/7152ec29b8335f80167928944a94955015a345440f524d2dfe63fc2f437b/watchfiles-1.1.1-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:36193ed342f5b9842edd3532729a2ad55c4160ffcfa3700e0d54be496b70dd43", size = 622657, upload-time = "2025-10-14T15:04:57.521Z" },
+ { url = "https://files.pythonhosted.org/packages/0a/bf/95895e78dd75efe9a7f31733607f384b42eb5feb54bd2eb6ed57cc2e94f4/watchfiles-1.1.1-cp312-cp312-win32.whl", hash = "sha256:859e43a1951717cc8de7f4c77674a6d389b106361585951d9e69572823f311d9", size = 272042, upload-time = "2025-10-14T15:04:59.046Z" },
+ { url = "https://files.pythonhosted.org/packages/87/0a/90eb755f568de2688cb220171c4191df932232c20946966c27a59c400850/watchfiles-1.1.1-cp312-cp312-win_amd64.whl", hash = "sha256:91d4c9a823a8c987cce8fa2690923b069966dabb196dd8d137ea2cede885fde9", size = 288410, upload-time = "2025-10-14T15:05:00.081Z" },
+ { url = "https://files.pythonhosted.org/packages/36/76/f322701530586922fbd6723c4f91ace21364924822a8772c549483abed13/watchfiles-1.1.1-cp312-cp312-win_arm64.whl", hash = "sha256:a625815d4a2bdca61953dbba5a39d60164451ef34c88d751f6c368c3ea73d404", size = 278209, upload-time = "2025-10-14T15:05:01.168Z" },
+ { url = "https://files.pythonhosted.org/packages/bb/f4/f750b29225fe77139f7ae5de89d4949f5a99f934c65a1f1c0b248f26f747/watchfiles-1.1.1-cp313-cp313-macosx_10_12_x86_64.whl", hash = "sha256:130e4876309e8686a5e37dba7d5e9bc77e6ed908266996ca26572437a5271e18", size = 404321, upload-time = "2025-10-14T15:05:02.063Z" },
+ { url = "https://files.pythonhosted.org/packages/2b/f9/f07a295cde762644aa4c4bb0f88921d2d141af45e735b965fb2e87858328/watchfiles-1.1.1-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:5f3bde70f157f84ece3765b42b4a52c6ac1a50334903c6eaf765362f6ccca88a", size = 391783, upload-time = "2025-10-14T15:05:03.052Z" },
+ { url = "https://files.pythonhosted.org/packages/bc/11/fc2502457e0bea39a5c958d86d2cb69e407a4d00b85735ca724bfa6e0d1a/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:14e0b1fe858430fc0251737ef3824c54027bedb8c37c38114488b8e131cf8219", size = 449279, upload-time = "2025-10-14T15:05:04.004Z" },
+ { url = "https://files.pythonhosted.org/packages/e3/1f/d66bc15ea0b728df3ed96a539c777acfcad0eb78555ad9efcaa1274688f0/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:f27db948078f3823a6bb3b465180db8ebecf26dd5dae6f6180bd87383b6b4428", size = 459405, upload-time = "2025-10-14T15:05:04.942Z" },
+ { url = "https://files.pythonhosted.org/packages/be/90/9f4a65c0aec3ccf032703e6db02d89a157462fbb2cf20dd415128251cac0/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:059098c3a429f62fc98e8ec62b982230ef2c8df68c79e826e37b895bc359a9c0", size = 488976, upload-time = "2025-10-14T15:05:05.905Z" },
+ { url = "https://files.pythonhosted.org/packages/37/57/ee347af605d867f712be7029bb94c8c071732a4b44792e3176fa3c612d39/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:bfb5862016acc9b869bb57284e6cb35fdf8e22fe59f7548858e2f971d045f150", size = 595506, upload-time = "2025-10-14T15:05:06.906Z" },
+ { url = "https://files.pythonhosted.org/packages/a8/78/cc5ab0b86c122047f75e8fc471c67a04dee395daf847d3e59381996c8707/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:319b27255aacd9923b8a276bb14d21a5f7ff82564c744235fc5eae58d95422ae", size = 474936, upload-time = "2025-10-14T15:05:07.906Z" },
+ { url = "https://files.pythonhosted.org/packages/62/da/def65b170a3815af7bd40a3e7010bf6ab53089ef1b75d05dd5385b87cf08/watchfiles-1.1.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:c755367e51db90e75b19454b680903631d41f9e3607fbd941d296a020c2d752d", size = 456147, upload-time = "2025-10-14T15:05:09.138Z" },
+ { url = "https://files.pythonhosted.org/packages/57/99/da6573ba71166e82d288d4df0839128004c67d2778d3b566c138695f5c0b/watchfiles-1.1.1-cp313-cp313-musllinux_1_1_aarch64.whl", hash = "sha256:c22c776292a23bfc7237a98f791b9ad3144b02116ff10d820829ce62dff46d0b", size = 630007, upload-time = "2025-10-14T15:05:10.117Z" },
+ { url = "https://files.pythonhosted.org/packages/a8/51/7439c4dd39511368849eb1e53279cd3454b4a4dbace80bab88feeb83c6b5/watchfiles-1.1.1-cp313-cp313-musllinux_1_1_x86_64.whl", hash = "sha256:3a476189be23c3686bc2f4321dd501cb329c0a0469e77b7b534ee10129ae6374", size = 622280, upload-time = "2025-10-14T15:05:11.146Z" },
+ { url = "https://files.pythonhosted.org/packages/95/9c/8ed97d4bba5db6fdcdb2b298d3898f2dd5c20f6b73aee04eabe56c59677e/watchfiles-1.1.1-cp313-cp313-win32.whl", hash = "sha256:bf0a91bfb5574a2f7fc223cf95eeea79abfefa404bf1ea5e339c0c1560ae99a0", size = 272056, upload-time = "2025-10-14T15:05:12.156Z" },
+ { url = "https://files.pythonhosted.org/packages/1f/f3/c14e28429f744a260d8ceae18bf58c1d5fa56b50d006a7a9f80e1882cb0d/watchfiles-1.1.1-cp313-cp313-win_amd64.whl", hash = "sha256:52e06553899e11e8074503c8e716d574adeeb7e68913115c4b3653c53f9bae42", size = 288162, upload-time = "2025-10-14T15:05:13.208Z" },
+ { url = "https://files.pythonhosted.org/packages/dc/61/fe0e56c40d5cd29523e398d31153218718c5786b5e636d9ae8ae79453d27/watchfiles-1.1.1-cp313-cp313-win_arm64.whl", hash = "sha256:ac3cc5759570cd02662b15fbcd9d917f7ecd47efe0d6b40474eafd246f91ea18", size = 277909, upload-time = "2025-10-14T15:05:14.49Z" },
+ { url = "https://files.pythonhosted.org/packages/79/42/e0a7d749626f1e28c7108a99fb9bf524b501bbbeb9b261ceecde644d5a07/watchfiles-1.1.1-cp313-cp313t-macosx_10_12_x86_64.whl", hash = "sha256:563b116874a9a7ce6f96f87cd0b94f7faf92d08d0021e837796f0a14318ef8da", size = 403389, upload-time = "2025-10-14T15:05:15.777Z" },
+ { url = "https://files.pythonhosted.org/packages/15/49/08732f90ce0fbbc13913f9f215c689cfc9ced345fb1bcd8829a50007cc8d/watchfiles-1.1.1-cp313-cp313t-macosx_11_0_arm64.whl", hash = "sha256:3ad9fe1dae4ab4212d8c91e80b832425e24f421703b5a42ef2e4a1e215aff051", size = 389964, upload-time = "2025-10-14T15:05:16.85Z" },
+ { url = "https://files.pythonhosted.org/packages/27/0d/7c315d4bd5f2538910491a0393c56bf70d333d51bc5b34bee8e68e8cea19/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ce70f96a46b894b36eba678f153f052967a0d06d5b5a19b336ab0dbbd029f73e", size = 448114, upload-time = "2025-10-14T15:05:17.876Z" },
+ { url = "https://files.pythonhosted.org/packages/c3/24/9e096de47a4d11bc4df41e9d1e61776393eac4cb6eb11b3e23315b78b2cc/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:cb467c999c2eff23a6417e58d75e5828716f42ed8289fe6b77a7e5a91036ca70", size = 460264, upload-time = "2025-10-14T15:05:18.962Z" },
+ { url = "https://files.pythonhosted.org/packages/cc/0f/e8dea6375f1d3ba5fcb0b3583e2b493e77379834c74fd5a22d66d85d6540/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:836398932192dae4146c8f6f737d74baeac8b70ce14831a239bdb1ca882fc261", size = 487877, upload-time = "2025-10-14T15:05:20.094Z" },
+ { url = "https://files.pythonhosted.org/packages/ac/5b/df24cfc6424a12deb41503b64d42fbea6b8cb357ec62ca84a5a3476f654a/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:743185e7372b7bc7c389e1badcc606931a827112fbbd37f14c537320fca08620", size = 595176, upload-time = "2025-10-14T15:05:21.134Z" },
+ { url = "https://files.pythonhosted.org/packages/8f/b5/853b6757f7347de4e9b37e8cc3289283fb983cba1ab4d2d7144694871d9c/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:afaeff7696e0ad9f02cbb8f56365ff4686ab205fcf9c4c5b6fdfaaa16549dd04", size = 473577, upload-time = "2025-10-14T15:05:22.306Z" },
+ { url = "https://files.pythonhosted.org/packages/e1/f7/0a4467be0a56e80447c8529c9fce5b38eab4f513cb3d9bf82e7392a5696b/watchfiles-1.1.1-cp313-cp313t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:3f7eb7da0eb23aa2ba036d4f616d46906013a68caf61b7fdbe42fc8b25132e77", size = 455425, upload-time = "2025-10-14T15:05:23.348Z" },
+ { url = "https://files.pythonhosted.org/packages/8e/e0/82583485ea00137ddf69bc84a2db88bd92ab4a6e3c405e5fb878ead8d0e7/watchfiles-1.1.1-cp313-cp313t-musllinux_1_1_aarch64.whl", hash = "sha256:831a62658609f0e5c64178211c942ace999517f5770fe9436be4c2faeba0c0ef", size = 628826, upload-time = "2025-10-14T15:05:24.398Z" },
+ { url = "https://files.pythonhosted.org/packages/28/9a/a785356fccf9fae84c0cc90570f11702ae9571036fb25932f1242c82191c/watchfiles-1.1.1-cp313-cp313t-musllinux_1_1_x86_64.whl", hash = "sha256:f9a2ae5c91cecc9edd47e041a930490c31c3afb1f5e6d71de3dc671bfaca02bf", size = 622208, upload-time = "2025-10-14T15:05:25.45Z" },
+ { url = "https://files.pythonhosted.org/packages/c3/f4/0872229324ef69b2c3edec35e84bd57a1289e7d3fe74588048ed8947a323/watchfiles-1.1.1-cp314-cp314-macosx_10_12_x86_64.whl", hash = "sha256:d1715143123baeeaeadec0528bb7441103979a1d5f6fd0e1f915383fea7ea6d5", size = 404315, upload-time = "2025-10-14T15:05:26.501Z" },
+ { url = "https://files.pythonhosted.org/packages/7b/22/16d5331eaed1cb107b873f6ae1b69e9ced582fcf0c59a50cd84f403b1c32/watchfiles-1.1.1-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:39574d6370c4579d7f5d0ad940ce5b20db0e4117444e39b6d8f99db5676c52fd", size = 390869, upload-time = "2025-10-14T15:05:27.649Z" },
+ { url = "https://files.pythonhosted.org/packages/b2/7e/5643bfff5acb6539b18483128fdc0ef2cccc94a5b8fbda130c823e8ed636/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:7365b92c2e69ee952902e8f70f3ba6360d0d596d9299d55d7d386df84b6941fb", size = 449919, upload-time = "2025-10-14T15:05:28.701Z" },
+ { url = "https://files.pythonhosted.org/packages/51/2e/c410993ba5025a9f9357c376f48976ef0e1b1aefb73b97a5ae01a5972755/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:bfff9740c69c0e4ed32416f013f3c45e2ae42ccedd1167ef2d805c000b6c71a5", size = 460845, upload-time = "2025-10-14T15:05:30.064Z" },
+ { url = "https://files.pythonhosted.org/packages/8e/a4/2df3b404469122e8680f0fcd06079317e48db58a2da2950fb45020947734/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:b27cf2eb1dda37b2089e3907d8ea92922b673c0c427886d4edc6b94d8dfe5db3", size = 489027, upload-time = "2025-10-14T15:05:31.064Z" },
+ { url = "https://files.pythonhosted.org/packages/ea/84/4587ba5b1f267167ee715b7f66e6382cca6938e0a4b870adad93e44747e6/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:526e86aced14a65a5b0ec50827c745597c782ff46b571dbfe46192ab9e0b3c33", size = 595615, upload-time = "2025-10-14T15:05:32.074Z" },
+ { url = "https://files.pythonhosted.org/packages/6a/0f/c6988c91d06e93cd0bb3d4a808bcf32375ca1904609835c3031799e3ecae/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:04e78dd0b6352db95507fd8cb46f39d185cf8c74e4cf1e4fbad1d3df96faf510", size = 474836, upload-time = "2025-10-14T15:05:33.209Z" },
+ { url = "https://files.pythonhosted.org/packages/b4/36/ded8aebea91919485b7bbabbd14f5f359326cb5ec218cd67074d1e426d74/watchfiles-1.1.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:5c85794a4cfa094714fb9c08d4a218375b2b95b8ed1666e8677c349906246c05", size = 455099, upload-time = "2025-10-14T15:05:34.189Z" },
+ { url = "https://files.pythonhosted.org/packages/98/e0/8c9bdba88af756a2fce230dd365fab2baf927ba42cd47521ee7498fd5211/watchfiles-1.1.1-cp314-cp314-musllinux_1_1_aarch64.whl", hash = "sha256:74d5012b7630714b66be7b7b7a78855ef7ad58e8650c73afc4c076a1f480a8d6", size = 630626, upload-time = "2025-10-14T15:05:35.216Z" },
+ { url = "https://files.pythonhosted.org/packages/2a/84/a95db05354bf2d19e438520d92a8ca475e578c647f78f53197f5a2f17aaf/watchfiles-1.1.1-cp314-cp314-musllinux_1_1_x86_64.whl", hash = "sha256:8fbe85cb3201c7d380d3d0b90e63d520f15d6afe217165d7f98c9c649654db81", size = 622519, upload-time = "2025-10-14T15:05:36.259Z" },
+ { url = "https://files.pythonhosted.org/packages/1d/ce/d8acdc8de545de995c339be67711e474c77d643555a9bb74a9334252bd55/watchfiles-1.1.1-cp314-cp314-win32.whl", hash = "sha256:3fa0b59c92278b5a7800d3ee7733da9d096d4aabcfabb9a928918bd276ef9b9b", size = 272078, upload-time = "2025-10-14T15:05:37.63Z" },
+ { url = "https://files.pythonhosted.org/packages/c4/c9/a74487f72d0451524be827e8edec251da0cc1fcf111646a511ae752e1a3d/watchfiles-1.1.1-cp314-cp314-win_amd64.whl", hash = "sha256:c2047d0b6cea13b3316bdbafbfa0c4228ae593d995030fda39089d36e64fc03a", size = 287664, upload-time = "2025-10-14T15:05:38.95Z" },
+ { url = "https://files.pythonhosted.org/packages/df/b8/8ac000702cdd496cdce998c6f4ee0ca1f15977bba51bdf07d872ebdfc34c/watchfiles-1.1.1-cp314-cp314-win_arm64.whl", hash = "sha256:842178b126593addc05acf6fce960d28bc5fae7afbaa2c6c1b3a7b9460e5be02", size = 277154, upload-time = "2025-10-14T15:05:39.954Z" },
+ { url = "https://files.pythonhosted.org/packages/47/a8/e3af2184707c29f0f14b1963c0aace6529f9d1b8582d5b99f31bbf42f59e/watchfiles-1.1.1-cp314-cp314t-macosx_10_12_x86_64.whl", hash = "sha256:88863fbbc1a7312972f1c511f202eb30866370ebb8493aef2812b9ff28156a21", size = 403820, upload-time = "2025-10-14T15:05:40.932Z" },
+ { url = "https://files.pythonhosted.org/packages/c0/ec/e47e307c2f4bd75f9f9e8afbe3876679b18e1bcec449beca132a1c5ffb2d/watchfiles-1.1.1-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:55c7475190662e202c08c6c0f4d9e345a29367438cf8e8037f3155e10a88d5a5", size = 390510, upload-time = "2025-10-14T15:05:41.945Z" },
+ { url = "https://files.pythonhosted.org/packages/d5/a0/ad235642118090f66e7b2f18fd5c42082418404a79205cdfca50b6309c13/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:3f53fa183d53a1d7a8852277c92b967ae99c2d4dcee2bfacff8868e6e30b15f7", size = 448408, upload-time = "2025-10-14T15:05:43.385Z" },
+ { url = "https://files.pythonhosted.org/packages/df/85/97fa10fd5ff3332ae17e7e40e20784e419e28521549780869f1413742e9d/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:6aae418a8b323732fa89721d86f39ec8f092fc2af67f4217a2b07fd3e93c6101", size = 458968, upload-time = "2025-10-14T15:05:44.404Z" },
+ { url = "https://files.pythonhosted.org/packages/47/c2/9059c2e8966ea5ce678166617a7f75ecba6164375f3b288e50a40dc6d489/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:f096076119da54a6080e8920cbdaac3dbee667eb91dcc5e5b78840b87415bd44", size = 488096, upload-time = "2025-10-14T15:05:45.398Z" },
+ { url = "https://files.pythonhosted.org/packages/94/44/d90a9ec8ac309bc26db808a13e7bfc0e4e78b6fc051078a554e132e80160/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:00485f441d183717038ed2e887a7c868154f216877653121068107b227a2f64c", size = 596040, upload-time = "2025-10-14T15:05:46.502Z" },
+ { url = "https://files.pythonhosted.org/packages/95/68/4e3479b20ca305cfc561db3ed207a8a1c745ee32bf24f2026a129d0ddb6e/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:a55f3e9e493158d7bfdb60a1165035f1cf7d320914e7b7ea83fe22c6023b58fc", size = 473847, upload-time = "2025-10-14T15:05:47.484Z" },
+ { url = "https://files.pythonhosted.org/packages/4f/55/2af26693fd15165c4ff7857e38330e1b61ab8c37d15dc79118cdba115b7a/watchfiles-1.1.1-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:8c91ed27800188c2ae96d16e3149f199d62f86c7af5f5f4d2c61a3ed8cd3666c", size = 455072, upload-time = "2025-10-14T15:05:48.928Z" },
+ { url = "https://files.pythonhosted.org/packages/66/1d/d0d200b10c9311ec25d2273f8aad8c3ef7cc7ea11808022501811208a750/watchfiles-1.1.1-cp314-cp314t-musllinux_1_1_aarch64.whl", hash = "sha256:311ff15a0bae3714ffb603e6ba6dbfba4065ab60865d15a6ec544133bdb21099", size = 629104, upload-time = "2025-10-14T15:05:49.908Z" },
+ { url = "https://files.pythonhosted.org/packages/e3/bd/fa9bb053192491b3867ba07d2343d9f2252e00811567d30ae8d0f78136fe/watchfiles-1.1.1-cp314-cp314t-musllinux_1_1_x86_64.whl", hash = "sha256:a916a2932da8f8ab582f242c065f5c81bed3462849ca79ee357dd9551b0e9b01", size = 622112, upload-time = "2025-10-14T15:05:50.941Z" },
]
[[package]]
name = "websockets"
-version = "15.0.1"
+version = "16.0"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/21/e6/26d09fab466b7ca9c7737474c52be4f76a40301b08362eb2dbc19dcc16c1/websockets-15.0.1.tar.gz", hash = "sha256:82544de02076bafba038ce055ee6412d68da13ab47f0c60cab827346de828dee", size = 177016, upload-time = "2025-03-05T20:03:41.606Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/04/24/4b2031d72e840ce4c1ccb255f693b15c334757fc50023e4db9537080b8c4/websockets-16.0.tar.gz", hash = "sha256:5f6261a5e56e8d5c42a4497b364ea24d94d9563e8fbd44e78ac40879c60179b5", size = 179346, upload-time = "2026-01-10T09:23:47.181Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/51/6b/4545a0d843594f5d0771e86463606a3988b5a09ca5123136f8a76580dd63/websockets-15.0.1-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:3e90baa811a5d73f3ca0bcbf32064d663ed81318ab225ee4f427ad4e26e5aff3", size = 175437, upload-time = "2025-03-05T20:02:16.706Z" },
- { url = "https://files.pythonhosted.org/packages/f4/71/809a0f5f6a06522af902e0f2ea2757f71ead94610010cf570ab5c98e99ed/websockets-15.0.1-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:592f1a9fe869c778694f0aa806ba0374e97648ab57936f092fd9d87f8bc03665", size = 173096, upload-time = "2025-03-05T20:02:18.832Z" },
- { url = "https://files.pythonhosted.org/packages/3d/69/1a681dd6f02180916f116894181eab8b2e25b31e484c5d0eae637ec01f7c/websockets-15.0.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:0701bc3cfcb9164d04a14b149fd74be7347a530ad3bbf15ab2c678a2cd3dd9a2", size = 173332, upload-time = "2025-03-05T20:02:20.187Z" },
- { url = "https://files.pythonhosted.org/packages/a6/02/0073b3952f5bce97eafbb35757f8d0d54812b6174ed8dd952aa08429bcc3/websockets-15.0.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:e8b56bdcdb4505c8078cb6c7157d9811a85790f2f2b3632c7d1462ab5783d215", size = 183152, upload-time = "2025-03-05T20:02:22.286Z" },
- { url = "https://files.pythonhosted.org/packages/74/45/c205c8480eafd114b428284840da0b1be9ffd0e4f87338dc95dc6ff961a1/websockets-15.0.1-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:0af68c55afbd5f07986df82831c7bff04846928ea8d1fd7f30052638788bc9b5", size = 182096, upload-time = "2025-03-05T20:02:24.368Z" },
- { url = "https://files.pythonhosted.org/packages/14/8f/aa61f528fba38578ec553c145857a181384c72b98156f858ca5c8e82d9d3/websockets-15.0.1-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:64dee438fed052b52e4f98f76c5790513235efaa1ef7f3f2192c392cd7c91b65", size = 182523, upload-time = "2025-03-05T20:02:25.669Z" },
- { url = "https://files.pythonhosted.org/packages/ec/6d/0267396610add5bc0d0d3e77f546d4cd287200804fe02323797de77dbce9/websockets-15.0.1-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:d5f6b181bb38171a8ad1d6aa58a67a6aa9d4b38d0f8c5f496b9e42561dfc62fe", size = 182790, upload-time = "2025-03-05T20:02:26.99Z" },
- { url = "https://files.pythonhosted.org/packages/02/05/c68c5adbf679cf610ae2f74a9b871ae84564462955d991178f95a1ddb7dd/websockets-15.0.1-cp312-cp312-musllinux_1_2_i686.whl", hash = "sha256:5d54b09eba2bada6011aea5375542a157637b91029687eb4fdb2dab11059c1b4", size = 182165, upload-time = "2025-03-05T20:02:30.291Z" },
- { url = "https://files.pythonhosted.org/packages/29/93/bb672df7b2f5faac89761cb5fa34f5cec45a4026c383a4b5761c6cea5c16/websockets-15.0.1-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:3be571a8b5afed347da347bfcf27ba12b069d9d7f42cb8c7028b5e98bbb12597", size = 182160, upload-time = "2025-03-05T20:02:31.634Z" },
- { url = "https://files.pythonhosted.org/packages/ff/83/de1f7709376dc3ca9b7eeb4b9a07b4526b14876b6d372a4dc62312bebee0/websockets-15.0.1-cp312-cp312-win32.whl", hash = "sha256:c338ffa0520bdb12fbc527265235639fb76e7bc7faafbb93f6ba80d9c06578a9", size = 176395, upload-time = "2025-03-05T20:02:33.017Z" },
- { url = "https://files.pythonhosted.org/packages/7d/71/abf2ebc3bbfa40f391ce1428c7168fb20582d0ff57019b69ea20fa698043/websockets-15.0.1-cp312-cp312-win_amd64.whl", hash = "sha256:fcd5cf9e305d7b8338754470cf69cf81f420459dbae8a3b40cee57417f4614a7", size = 176841, upload-time = "2025-03-05T20:02:34.498Z" },
- { url = "https://files.pythonhosted.org/packages/cb/9f/51f0cf64471a9d2b4d0fc6c534f323b664e7095640c34562f5182e5a7195/websockets-15.0.1-cp313-cp313-macosx_10_13_universal2.whl", hash = "sha256:ee443ef070bb3b6ed74514f5efaa37a252af57c90eb33b956d35c8e9c10a1931", size = 175440, upload-time = "2025-03-05T20:02:36.695Z" },
- { url = "https://files.pythonhosted.org/packages/8a/05/aa116ec9943c718905997412c5989f7ed671bc0188ee2ba89520e8765d7b/websockets-15.0.1-cp313-cp313-macosx_10_13_x86_64.whl", hash = "sha256:5a939de6b7b4e18ca683218320fc67ea886038265fd1ed30173f5ce3f8e85675", size = 173098, upload-time = "2025-03-05T20:02:37.985Z" },
- { url = "https://files.pythonhosted.org/packages/ff/0b/33cef55ff24f2d92924923c99926dcce78e7bd922d649467f0eda8368923/websockets-15.0.1-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:746ee8dba912cd6fc889a8147168991d50ed70447bf18bcda7039f7d2e3d9151", size = 173329, upload-time = "2025-03-05T20:02:39.298Z" },
- { url = "https://files.pythonhosted.org/packages/31/1d/063b25dcc01faa8fada1469bdf769de3768b7044eac9d41f734fd7b6ad6d/websockets-15.0.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:595b6c3969023ecf9041b2936ac3827e4623bfa3ccf007575f04c5a6aa318c22", size = 183111, upload-time = "2025-03-05T20:02:40.595Z" },
- { url = "https://files.pythonhosted.org/packages/93/53/9a87ee494a51bf63e4ec9241c1ccc4f7c2f45fff85d5bde2ff74fcb68b9e/websockets-15.0.1-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:3c714d2fc58b5ca3e285461a4cc0c9a66bd0e24c5da9911e30158286c9b5be7f", size = 182054, upload-time = "2025-03-05T20:02:41.926Z" },
- { url = "https://files.pythonhosted.org/packages/ff/b2/83a6ddf56cdcbad4e3d841fcc55d6ba7d19aeb89c50f24dd7e859ec0805f/websockets-15.0.1-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:0f3c1e2ab208db911594ae5b4f79addeb3501604a165019dd221c0bdcabe4db8", size = 182496, upload-time = "2025-03-05T20:02:43.304Z" },
- { url = "https://files.pythonhosted.org/packages/98/41/e7038944ed0abf34c45aa4635ba28136f06052e08fc2168520bb8b25149f/websockets-15.0.1-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:229cf1d3ca6c1804400b0a9790dc66528e08a6a1feec0d5040e8b9eb14422375", size = 182829, upload-time = "2025-03-05T20:02:48.812Z" },
- { url = "https://files.pythonhosted.org/packages/e0/17/de15b6158680c7623c6ef0db361da965ab25d813ae54fcfeae2e5b9ef910/websockets-15.0.1-cp313-cp313-musllinux_1_2_i686.whl", hash = "sha256:756c56e867a90fb00177d530dca4b097dd753cde348448a1012ed6c5131f8b7d", size = 182217, upload-time = "2025-03-05T20:02:50.14Z" },
- { url = "https://files.pythonhosted.org/packages/33/2b/1f168cb6041853eef0362fb9554c3824367c5560cbdaad89ac40f8c2edfc/websockets-15.0.1-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:558d023b3df0bffe50a04e710bc87742de35060580a293c2a984299ed83bc4e4", size = 182195, upload-time = "2025-03-05T20:02:51.561Z" },
- { url = "https://files.pythonhosted.org/packages/86/eb/20b6cdf273913d0ad05a6a14aed4b9a85591c18a987a3d47f20fa13dcc47/websockets-15.0.1-cp313-cp313-win32.whl", hash = "sha256:ba9e56e8ceeeedb2e080147ba85ffcd5cd0711b89576b83784d8605a7df455fa", size = 176393, upload-time = "2025-03-05T20:02:53.814Z" },
- { url = "https://files.pythonhosted.org/packages/1b/6c/c65773d6cab416a64d191d6ee8a8b1c68a09970ea6909d16965d26bfed1e/websockets-15.0.1-cp313-cp313-win_amd64.whl", hash = "sha256:e09473f095a819042ecb2ab9465aee615bd9c2028e4ef7d933600a8401c79561", size = 176837, upload-time = "2025-03-05T20:02:55.237Z" },
- { url = "https://files.pythonhosted.org/packages/fa/a8/5b41e0da817d64113292ab1f8247140aac61cbf6cfd085d6a0fa77f4984f/websockets-15.0.1-py3-none-any.whl", hash = "sha256:f7a866fbc1e97b5c617ee4116daaa09b722101d4a3c170c787450ba409f9736f", size = 169743, upload-time = "2025-03-05T20:03:39.41Z" },
+ { url = "https://files.pythonhosted.org/packages/84/7b/bac442e6b96c9d25092695578dda82403c77936104b5682307bd4deb1ad4/websockets-16.0-cp312-cp312-macosx_10_13_universal2.whl", hash = "sha256:71c989cbf3254fbd5e84d3bff31e4da39c43f884e64f2551d14bb3c186230f00", size = 177365, upload-time = "2026-01-10T09:22:46.787Z" },
+ { url = "https://files.pythonhosted.org/packages/b0/fe/136ccece61bd690d9c1f715baaeefd953bb2360134de73519d5df19d29ca/websockets-16.0-cp312-cp312-macosx_10_13_x86_64.whl", hash = "sha256:8b6e209ffee39ff1b6d0fa7bfef6de950c60dfb91b8fcead17da4ee539121a79", size = 175038, upload-time = "2026-01-10T09:22:47.999Z" },
+ { url = "https://files.pythonhosted.org/packages/40/1e/9771421ac2286eaab95b8575b0cb701ae3663abf8b5e1f64f1fd90d0a673/websockets-16.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:86890e837d61574c92a97496d590968b23c2ef0aeb8a9bc9421d174cd378ae39", size = 175328, upload-time = "2026-01-10T09:22:49.809Z" },
+ { url = "https://files.pythonhosted.org/packages/18/29/71729b4671f21e1eaa5d6573031ab810ad2936c8175f03f97f3ff164c802/websockets-16.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:9b5aca38b67492ef518a8ab76851862488a478602229112c4b0d58d63a7a4d5c", size = 184915, upload-time = "2026-01-10T09:22:51.071Z" },
+ { url = "https://files.pythonhosted.org/packages/97/bb/21c36b7dbbafc85d2d480cd65df02a1dc93bf76d97147605a8e27ff9409d/websockets-16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:e0334872c0a37b606418ac52f6ab9cfd17317ac26365f7f65e203e2d0d0d359f", size = 186152, upload-time = "2026-01-10T09:22:52.224Z" },
+ { url = "https://files.pythonhosted.org/packages/4a/34/9bf8df0c0cf88fa7bfe36678dc7b02970c9a7d5e065a3099292db87b1be2/websockets-16.0-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:a0b31e0b424cc6b5a04b8838bbaec1688834b2383256688cf47eb97412531da1", size = 185583, upload-time = "2026-01-10T09:22:53.443Z" },
+ { url = "https://files.pythonhosted.org/packages/47/88/4dd516068e1a3d6ab3c7c183288404cd424a9a02d585efbac226cb61ff2d/websockets-16.0-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:485c49116d0af10ac698623c513c1cc01c9446c058a4e61e3bf6c19dff7335a2", size = 184880, upload-time = "2026-01-10T09:22:55.033Z" },
+ { url = "https://files.pythonhosted.org/packages/91/d6/7d4553ad4bf1c0421e1ebd4b18de5d9098383b5caa1d937b63df8d04b565/websockets-16.0-cp312-cp312-win32.whl", hash = "sha256:eaded469f5e5b7294e2bdca0ab06becb6756ea86894a47806456089298813c89", size = 178261, upload-time = "2026-01-10T09:22:56.251Z" },
+ { url = "https://files.pythonhosted.org/packages/c3/f0/f3a17365441ed1c27f850a80b2bc680a0fa9505d733fe152fdf5e98c1c0b/websockets-16.0-cp312-cp312-win_amd64.whl", hash = "sha256:5569417dc80977fc8c2d43a86f78e0a5a22fee17565d78621b6bb264a115d4ea", size = 178693, upload-time = "2026-01-10T09:22:57.478Z" },
+ { url = "https://files.pythonhosted.org/packages/cc/9c/baa8456050d1c1b08dd0ec7346026668cbc6f145ab4e314d707bb845bf0d/websockets-16.0-cp313-cp313-macosx_10_13_universal2.whl", hash = "sha256:878b336ac47938b474c8f982ac2f7266a540adc3fa4ad74ae96fea9823a02cc9", size = 177364, upload-time = "2026-01-10T09:22:59.333Z" },
+ { url = "https://files.pythonhosted.org/packages/7e/0c/8811fc53e9bcff68fe7de2bcbe75116a8d959ac699a3200f4847a8925210/websockets-16.0-cp313-cp313-macosx_10_13_x86_64.whl", hash = "sha256:52a0fec0e6c8d9a784c2c78276a48a2bdf099e4ccc2a4cad53b27718dbfd0230", size = 175039, upload-time = "2026-01-10T09:23:01.171Z" },
+ { url = "https://files.pythonhosted.org/packages/aa/82/39a5f910cb99ec0b59e482971238c845af9220d3ab9fa76dd9162cda9d62/websockets-16.0-cp313-cp313-macosx_11_0_arm64.whl", hash = "sha256:e6578ed5b6981005df1860a56e3617f14a6c307e6a71b4fff8c48fdc50f3ed2c", size = 175323, upload-time = "2026-01-10T09:23:02.341Z" },
+ { url = "https://files.pythonhosted.org/packages/bd/28/0a25ee5342eb5d5f297d992a77e56892ecb65e7854c7898fb7d35e9b33bd/websockets-16.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:95724e638f0f9c350bb1c2b0a7ad0e83d9cc0c9259f3ea94e40d7b02a2179ae5", size = 184975, upload-time = "2026-01-10T09:23:03.756Z" },
+ { url = "https://files.pythonhosted.org/packages/f9/66/27ea52741752f5107c2e41fda05e8395a682a1e11c4e592a809a90c6a506/websockets-16.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:c0204dc62a89dc9d50d682412c10b3542d748260d743500a85c13cd1ee4bde82", size = 186203, upload-time = "2026-01-10T09:23:05.01Z" },
+ { url = "https://files.pythonhosted.org/packages/37/e5/8e32857371406a757816a2b471939d51c463509be73fa538216ea52b792a/websockets-16.0-cp313-cp313-musllinux_1_2_aarch64.whl", hash = "sha256:52ac480f44d32970d66763115edea932f1c5b1312de36df06d6b219f6741eed8", size = 185653, upload-time = "2026-01-10T09:23:06.301Z" },
+ { url = "https://files.pythonhosted.org/packages/9b/67/f926bac29882894669368dc73f4da900fcdf47955d0a0185d60103df5737/websockets-16.0-cp313-cp313-musllinux_1_2_x86_64.whl", hash = "sha256:6e5a82b677f8f6f59e8dfc34ec06ca6b5b48bc4fcda346acd093694cc2c24d8f", size = 184920, upload-time = "2026-01-10T09:23:07.492Z" },
+ { url = "https://files.pythonhosted.org/packages/3c/a1/3d6ccdcd125b0a42a311bcd15a7f705d688f73b2a22d8cf1c0875d35d34a/websockets-16.0-cp313-cp313-win32.whl", hash = "sha256:abf050a199613f64c886ea10f38b47770a65154dc37181bfaff70c160f45315a", size = 178255, upload-time = "2026-01-10T09:23:09.245Z" },
+ { url = "https://files.pythonhosted.org/packages/6b/ae/90366304d7c2ce80f9b826096a9e9048b4bb760e44d3b873bb272cba696b/websockets-16.0-cp313-cp313-win_amd64.whl", hash = "sha256:3425ac5cf448801335d6fdc7ae1eb22072055417a96cc6b31b3861f455fbc156", size = 178689, upload-time = "2026-01-10T09:23:10.483Z" },
+ { url = "https://files.pythonhosted.org/packages/f3/1d/e88022630271f5bd349ed82417136281931e558d628dd52c4d8621b4a0b2/websockets-16.0-cp314-cp314-macosx_10_15_universal2.whl", hash = "sha256:8cc451a50f2aee53042ac52d2d053d08bf89bcb31ae799cb4487587661c038a0", size = 177406, upload-time = "2026-01-10T09:23:12.178Z" },
+ { url = "https://files.pythonhosted.org/packages/f2/78/e63be1bf0724eeb4616efb1ae1c9044f7c3953b7957799abb5915bffd38e/websockets-16.0-cp314-cp314-macosx_10_15_x86_64.whl", hash = "sha256:daa3b6ff70a9241cf6c7fc9e949d41232d9d7d26fd3522b1ad2b4d62487e9904", size = 175085, upload-time = "2026-01-10T09:23:13.511Z" },
+ { url = "https://files.pythonhosted.org/packages/bb/f4/d3c9220d818ee955ae390cf319a7c7a467beceb24f05ee7aaaa2414345ba/websockets-16.0-cp314-cp314-macosx_11_0_arm64.whl", hash = "sha256:fd3cb4adb94a2a6e2b7c0d8d05cb94e6f1c81a0cf9dc2694fb65c7e8d94c42e4", size = 175328, upload-time = "2026-01-10T09:23:14.727Z" },
+ { url = "https://files.pythonhosted.org/packages/63/bc/d3e208028de777087e6fb2b122051a6ff7bbcca0d6df9d9c2bf1dd869ae9/websockets-16.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:781caf5e8eee67f663126490c2f96f40906594cb86b408a703630f95550a8c3e", size = 185044, upload-time = "2026-01-10T09:23:15.939Z" },
+ { url = "https://files.pythonhosted.org/packages/ad/6e/9a0927ac24bd33a0a9af834d89e0abc7cfd8e13bed17a86407a66773cc0e/websockets-16.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:caab51a72c51973ca21fa8a18bd8165e1a0183f1ac7066a182ff27107b71e1a4", size = 186279, upload-time = "2026-01-10T09:23:17.148Z" },
+ { url = "https://files.pythonhosted.org/packages/b9/ca/bf1c68440d7a868180e11be653c85959502efd3a709323230314fda6e0b3/websockets-16.0-cp314-cp314-musllinux_1_2_aarch64.whl", hash = "sha256:19c4dc84098e523fd63711e563077d39e90ec6702aff4b5d9e344a60cb3c0cb1", size = 185711, upload-time = "2026-01-10T09:23:18.372Z" },
+ { url = "https://files.pythonhosted.org/packages/c4/f8/fdc34643a989561f217bb477cbc47a3a07212cbda91c0e4389c43c296ebf/websockets-16.0-cp314-cp314-musllinux_1_2_x86_64.whl", hash = "sha256:a5e18a238a2b2249c9a9235466b90e96ae4795672598a58772dd806edc7ac6d3", size = 184982, upload-time = "2026-01-10T09:23:19.652Z" },
+ { url = "https://files.pythonhosted.org/packages/dd/d1/574fa27e233764dbac9c52730d63fcf2823b16f0856b3329fc6268d6ae4f/websockets-16.0-cp314-cp314-win32.whl", hash = "sha256:a069d734c4a043182729edd3e9f247c3b2a4035415a9172fd0f1b71658a320a8", size = 177915, upload-time = "2026-01-10T09:23:21.458Z" },
+ { url = "https://files.pythonhosted.org/packages/8a/f1/ae6b937bf3126b5134ce1f482365fde31a357c784ac51852978768b5eff4/websockets-16.0-cp314-cp314-win_amd64.whl", hash = "sha256:c0ee0e63f23914732c6d7e0cce24915c48f3f1512ec1d079ed01fc629dab269d", size = 178381, upload-time = "2026-01-10T09:23:22.715Z" },
+ { url = "https://files.pythonhosted.org/packages/06/9b/f791d1db48403e1f0a27577a6beb37afae94254a8c6f08be4a23e4930bc0/websockets-16.0-cp314-cp314t-macosx_10_15_universal2.whl", hash = "sha256:a35539cacc3febb22b8f4d4a99cc79b104226a756aa7400adc722e83b0d03244", size = 177737, upload-time = "2026-01-10T09:23:24.523Z" },
+ { url = "https://files.pythonhosted.org/packages/bd/40/53ad02341fa33b3ce489023f635367a4ac98b73570102ad2cdd770dacc9a/websockets-16.0-cp314-cp314t-macosx_10_15_x86_64.whl", hash = "sha256:b784ca5de850f4ce93ec85d3269d24d4c82f22b7212023c974c401d4980ebc5e", size = 175268, upload-time = "2026-01-10T09:23:25.781Z" },
+ { url = "https://files.pythonhosted.org/packages/74/9b/6158d4e459b984f949dcbbb0c5d270154c7618e11c01029b9bbd1bb4c4f9/websockets-16.0-cp314-cp314t-macosx_11_0_arm64.whl", hash = "sha256:569d01a4e7fba956c5ae4fc988f0d4e187900f5497ce46339c996dbf24f17641", size = 175486, upload-time = "2026-01-10T09:23:27.033Z" },
+ { url = "https://files.pythonhosted.org/packages/e5/2d/7583b30208b639c8090206f95073646c2c9ffd66f44df967981a64f849ad/websockets-16.0-cp314-cp314t-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl", hash = "sha256:50f23cdd8343b984957e4077839841146f67a3d31ab0d00e6b824e74c5b2f6e8", size = 185331, upload-time = "2026-01-10T09:23:28.259Z" },
+ { url = "https://files.pythonhosted.org/packages/45/b0/cce3784eb519b7b5ad680d14b9673a31ab8dcb7aad8b64d81709d2430aa8/websockets-16.0-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl", hash = "sha256:152284a83a00c59b759697b7f9e9cddf4e3c7861dd0d964b472b70f78f89e80e", size = 186501, upload-time = "2026-01-10T09:23:29.449Z" },
+ { url = "https://files.pythonhosted.org/packages/19/60/b8ebe4c7e89fb5f6cdf080623c9d92789a53636950f7abacfc33fe2b3135/websockets-16.0-cp314-cp314t-musllinux_1_2_aarch64.whl", hash = "sha256:bc59589ab64b0022385f429b94697348a6a234e8ce22544e3681b2e9331b5944", size = 186062, upload-time = "2026-01-10T09:23:31.368Z" },
+ { url = "https://files.pythonhosted.org/packages/88/a8/a080593f89b0138b6cba1b28f8df5673b5506f72879322288b031337c0b8/websockets-16.0-cp314-cp314t-musllinux_1_2_x86_64.whl", hash = "sha256:32da954ffa2814258030e5a57bc73a3635463238e797c7375dc8091327434206", size = 185356, upload-time = "2026-01-10T09:23:32.627Z" },
+ { url = "https://files.pythonhosted.org/packages/c2/b6/b9afed2afadddaf5ebb2afa801abf4b0868f42f8539bfe4b071b5266c9fe/websockets-16.0-cp314-cp314t-win32.whl", hash = "sha256:5a4b4cc550cb665dd8a47f868c8d04c8230f857363ad3c9caf7a0c3bf8c61ca6", size = 178085, upload-time = "2026-01-10T09:23:33.816Z" },
+ { url = "https://files.pythonhosted.org/packages/9f/3e/28135a24e384493fa804216b79a6a6759a38cc4ff59118787b9fb693df93/websockets-16.0-cp314-cp314t-win_amd64.whl", hash = "sha256:b14dc141ed6d2dde437cddb216004bcac6a1df0935d79656387bd41632ba0bbd", size = 178531, upload-time = "2026-01-10T09:23:35.016Z" },
+ { url = "https://files.pythonhosted.org/packages/6f/28/258ebab549c2bf3e64d2b0217b973467394a9cea8c42f70418ca2c5d0d2e/websockets-16.0-py3-none-any.whl", hash = "sha256:1637db62fad1dc833276dded54215f2c7fa46912301a24bd94d45d46a011ceec", size = 171598, upload-time = "2026-01-10T09:23:45.395Z" },
]
[[package]]
name = "zipp"
-version = "3.23.0"
+version = "3.23.1"
source = { registry = "https://pypi.org/simple" }
-sdist = { url = "https://files.pythonhosted.org/packages/e3/02/0f2892c661036d50ede074e376733dca2ae7c6eb617489437771209d4180/zipp-3.23.0.tar.gz", hash = "sha256:a07157588a12518c9d4034df3fbbee09c814741a33ff63c05fa29d26a2404166", size = 25547, upload-time = "2025-06-08T17:06:39.4Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/30/21/093488dfc7cc8964ded15ab726fad40f25fd3d788fd741cc1c5a17d78ee8/zipp-3.23.1.tar.gz", hash = "sha256:32120e378d32cd9714ad503c1d024619063ec28aad2248dc6672ad13edfa5110", size = 25965, upload-time = "2026-04-13T23:21:46.6Z" }
wheels = [
- { url = "https://files.pythonhosted.org/packages/2e/54/647ade08bf0db230bfea292f893923872fd20be6ac6f53b2b936ba839d75/zipp-3.23.0-py3-none-any.whl", hash = "sha256:071652d6115ed432f5ce1d34c336c0adfd6a884660d1e9712a256d3d3bd4b14e", size = 10276, upload-time = "2025-06-08T17:06:38.034Z" },
+ { url = "https://files.pythonhosted.org/packages/08/8a/0861bec20485572fbddf3dfba2910e38fe249796cb73ecdeb74e07eeb8d3/zipp-3.23.1-py3-none-any.whl", hash = "sha256:0b3596c50a5c700c9cb40ba8d86d9f2cc4807e9bedb06bcdf7fac85633e444dc", size = 10378, upload-time = "2026-04-13T23:21:45.386Z" },
]
diff --git a/osv-scanner.toml b/osv-scanner.toml
new file mode 100644
index 0000000000..59408b8709
--- /dev/null
+++ b/osv-scanner.toml
@@ -0,0 +1,31 @@
+# osv-scanner per-vulnerability ignore list.
+#
+# Each [[IgnoredVulns]] entry must include a `reason` explaining why the
+# finding is accepted and an `ignoreUntil` date so the suppression auto-expires
+# and gets re-evaluated. See https://github.com/google/osv-scanner for the
+# config schema.
+
+[[IgnoredVulns]]
+id = "PYSEC-2025-183"
+ignoreUntil = 2026-08-20T00:00:00Z
+reason = """
+CVE-2025-45768 is disputed by the pyjwt maintainers. The advisory describes
+weak encryption, but the underlying issue is that callers may pick a short
+HMAC secret — key-length enforcement is the application's responsibility, not
+a defect in the library. We are on pyjwt 2.13.0 (which now also emits an
+InsecureKeyLengthWarning for short HMAC secrets) and enforce key strength in
+our own auth code, so this advisory does not apply.
+Re-evaluate when a non-disputed advisory or upstream fix lands.
+"""
+
+[[IgnoredVulns]]
+id = "PYSEC-2026-89"
+ignoreUntil = 2026-08-20T00:00:00Z
+reason = """
+False positive caused by a malformed PYSEC record. The equivalent GitHub
+Security Advisory (GHSA-5wmx-573v-2qwq) for CVE-2025-69534 declares the issue
+fixed in markdown 3.8.1. We are on markdown==3.10.2 (latest release, includes
+the fix), but the PYSEC entry's range is [{introduced: "0"}, {}] with no
+closing "fixed" event, so osv-scanner flags every version. There is no newer
+release to upgrade to. Re-evaluate once the PYSEC record is corrected upstream.
+"""
diff --git a/permissions/prowler-additions-policy.json b/permissions/prowler-additions-policy.json
index 906f06fbfb..6c58f6e184 100644
--- a/permissions/prowler-additions-policy.json
+++ b/permissions/prowler-additions-policy.json
@@ -4,6 +4,8 @@
{
"Action": [
"account:Get*",
+ "amplify:ListApps",
+ "amplify:ListBranches",
"appstream:Describe*",
"appstream:List*",
"backup:List*",
@@ -15,6 +17,9 @@
"codebuild:BatchGet*",
"codebuild:ListReportGroups",
"cognito-idp:GetUserPoolMfaConfig",
+ "datapipeline:DescribePipelines",
+ "datapipeline:GetPipelineDefinition",
+ "datapipeline:ListPipelines",
"dlm:Get*",
"drs:Describe*",
"ds:Get*",
@@ -36,7 +41,11 @@
"lightsail:GetRelationalDatabases",
"macie2:GetMacieSession",
"macie2:GetAutomatedDiscoveryConfiguration",
+ "rolesanywhere:ListTagsForResource",
+ "rolesanywhere:ListTrustAnchors",
"s3:GetAccountPublicAccessBlock",
+ "s3:GetObjectAcl",
+ "s3:ListBucket",
"shield:DescribeProtection",
"shield:GetSubscriptionState",
"securityhub:BatchImportFindings",
@@ -61,7 +70,9 @@
],
"Resource": [
"arn:*:apigateway:*::/restapis/*",
- "arn:*:apigateway:*::/apis/*"
+ "arn:*:apigateway:*::/apis/*",
+ "arn:*:apigateway:*::/domainnames",
+ "arn:*:apigateway:*::/domainnames/*"
],
"Sid": "AllowAPIGatewayReadOnly"
}
diff --git a/permissions/templates/cloudformation/prowler-scan-role.yml b/permissions/templates/cloudformation/prowler-scan-role.yml
index 395fed6424..c9eee71950 100644
--- a/permissions/templates/cloudformation/prowler-scan-role.yml
+++ b/permissions/templates/cloudformation/prowler-scan-role.yml
@@ -1,27 +1,24 @@
AWSTemplateFormatVersion: "2010-09-09"
-# You can invoke CloudFormation and pass the principal ARN from a command line like this:
-# aws cloudformation create-stack \
-# --capabilities CAPABILITY_IAM --capabilities CAPABILITY_NAMED_IAM \
-# --template-body "file://prowler-scan-role.yaml" \
-# --stack-name "ProwlerScanRole" \
-# --parameters "ParameterKey=ExternalId,ParameterValue=ProvidedExternalID"
-
Description: |
- This template creates the ProwlerScan IAM Role in this account with
- all read-only permissions to scan your account for security issues.
+ This template creates the ProwlerScan IAM Role either locally in this account or across
+ multiple accounts via StackSets. It can deploy both simultaneously or just one option.
+ The role includes all read-only permissions to scan your accounts for security issues.
Contains two AWS managed policies (SecurityAudit and ViewOnlyAccess) and an inline policy.
- It sets the trust policy on that IAM Role to permit Prowler to assume that role.
This template is designed to be used in Prowler Cloud, but can also be used in other Prowler deployments.
+
If you are deploying this template to be used in Prowler Cloud please do not edit the AccountId, IAMPrincipal and ExternalId parameters.
+
Parameters:
+ # Core Prowler IAM Role Parameters
ExternalId:
Description: |
- This is the External ID that Prowler will use to assume the role ProwlerScan IAM Role.
+ This is the External ID that Prowler will use to assume the ProwlerScan IAM Role.
Type: String
MinLength: 1
AllowedPattern: ".+"
ConstraintDescription: "ExternalId must not be empty."
+
AccountId:
Description: |
AWS Account ID that will assume the role created, if you are deploying this template to be used in Prowler Cloud please do not edit this.
@@ -31,11 +28,13 @@ Parameters:
MaxLength: 12
AllowedPattern: "[0-9]{12}"
ConstraintDescription: "AccountId must be a valid AWS Account ID."
+
IAMPrincipal:
Description: |
The IAM principal type and name that will be allowed to assume the role created, leave an * for all the IAM principals in your AWS account. If you are deploying this template to be used in Prowler Cloud please do not edit this.
Type: String
Default: role/prowler*
+
EnableOrganizations:
Description: |
Enable AWS Organizations discovery permissions. Set to true only when deploying this role in the management account.
@@ -45,6 +44,7 @@ Parameters:
AllowedValues:
- true
- false
+
EnableS3Integration:
Description: |
Enable S3 integration for storing Prowler scan reports.
@@ -53,25 +53,102 @@ Parameters:
AllowedValues:
- true
- false
+
S3IntegrationBucketName:
Description: |
The S3 bucket name where Prowler will store scan reports for your cloud providers.
Type: String
Default: ""
+
S3IntegrationBucketAccountId:
Description: |
The AWS Account ID owner of the S3 Bucket.
Type: String
Default: ""
+ # Deployment Control Parameters
+ DeployStackSet:
+ Description: |
+ Set to true to deploy the ProwlerScan role across multiple accounts using StackSets.
+ Requires delegated administrator permissions for CloudFormation StackSets.
+ Type: String
+ Default: false
+ AllowedValues:
+ - true
+ - false
+
+ DeployLocalRole:
+ Description: |
+ Set to true to deploy the ProwlerScan role in this account (the account where this template is deployed).
+ Can be used independently or in conjunction with StackSet deployment.
+ Type: String
+ Default: true
+ AllowedValues:
+ - true
+ - false
+
+ # StackSet Configuration Parameters
+ AWSOrganizationalUnitId:
+ Description: |
+ AWS Organizations OU to deploy this stackset to (e.g., ou-xxxx-yyyyyyyy or r-xxxx for root).
+ Only required if DeployStackSet is true.
+ Type: String
+ Default: ""
+ AllowedPattern: '^(ou-[a-z0-9]{4,32}-[a-z0-9]{8,32}|r-[a-z0-9]{4,32})?$'
+
+ RetainStacksOnAccountRemoval:
+ Description: |
+ When an account is removed from the Organization or OU, should the ProwlerScan role remain in that account?
+ False (Recommended for security): Automatically deletes the role when accounts leave, following principle of least privilege.
+ True: Retains the role even after account removal, useful if accounts may temporarily leave and rejoin.
+ Type: String
+ Default: false
+ AllowedValues:
+ - true
+ - false
+
+ DeployFromDelegatedAdmin:
+ Description: |
+ Is this StackSet being deployed from a Delegated Administrator account (not the Organization Management Account)?
+ True: Deploying from a delegated admin account - uses CallAs: DELEGATED_ADMIN.
+ False: Deploying from the Organization Management Account - omits CallAs property.
+ Only required if DeployStackSet is true.
+ Type: String
+ Default: false
+ AllowedValues:
+ - true
+ - false
+
+ FailureTolerancePercentage:
+ Description: |
+ The percentage of accounts in which stack operations can fail before CloudFormation stops the operation.
+ Only applies when DeployStackSet is true.
+ Type: Number
+ Default: 10
+ MinValue: 0
+ MaxValue: 100
+
Conditions:
OrganizationsEnabled: !Equals [!Ref EnableOrganizations, true]
S3IntegrationEnabled: !Equals [!Ref EnableS3Integration, true]
+ DeployStackSetEnabled: !Equals [!Ref DeployStackSet, true]
+ DeployLocalRoleEnabled: !Equals [!Ref DeployLocalRole, true]
+ UseDelegatedAdmin: !Equals [!Ref DeployFromDelegatedAdmin, true]
+Rules:
+ S3IntegrationRequiresParams:
+ RuleCondition: !Equals [!Ref EnableS3Integration, "true"]
+ Assertions:
+ - Assert: !Not [!Equals [!Ref S3IntegrationBucketName, ""]]
+ AssertDescription: "S3IntegrationBucketName is required when EnableS3Integration is true."
+ - Assert: !Not [!Equals [!Ref S3IntegrationBucketAccountId, ""]]
+ AssertDescription: "S3IntegrationBucketAccountId is required when EnableS3Integration is true."
Resources:
+ # Local ProwlerScan Role (deployed in this account)
ProwlerScan:
Type: AWS::IAM::Role
+ Condition: DeployLocalRoleEnabled
Properties:
RoleName: ProwlerScan
AssumeRolePolicyDocument:
@@ -88,8 +165,8 @@ Resources:
"aws:PrincipalArn": !Sub "arn:${AWS::Partition}:iam::${AccountId}:${IAMPrincipal}"
MaxSessionDuration: 3600
ManagedPolicyArns:
- - "arn:aws:iam::aws:policy/SecurityAudit"
- - "arn:aws:iam::aws:policy/job-function/ViewOnlyAccess"
+ - !Sub "arn:${AWS::Partition}:iam::aws:policy/SecurityAudit"
+ - !Sub "arn:${AWS::Partition}:iam::aws:policy/job-function/ViewOnlyAccess"
Policies:
- PolicyName: ProwlerScan
PolicyDocument:
@@ -99,9 +176,12 @@ Resources:
Effect: Allow
Action:
- "account:Get*"
+ - "amplify:ListApps"
+ - "amplify:ListBranches"
- "appstream:Describe*"
- "appstream:List*"
- "backup:List*"
+ - "backup:Get*"
- "bedrock:List*"
- "bedrock:Get*"
- "cloudtrail:GetInsightSelectors"
@@ -109,6 +189,9 @@ Resources:
- "codebuild:BatchGet*"
- "codebuild:ListReportGroups"
- "cognito-idp:GetUserPoolMfaConfig"
+ - "datapipeline:DescribePipelines"
+ - "datapipeline:GetPipelineDefinition"
+ - "datapipeline:ListPipelines"
- "dlm:Get*"
- "drs:Describe*"
- "ds:Get*"
@@ -124,15 +207,17 @@ Resources:
- "glue:GetConnections"
- "glue:GetSecurityConfiguration*"
- "glue:SearchTables"
+ - "glue:GetMLTransforms"
- "lambda:GetFunction*"
- "logs:FilterLogEvents"
- "lightsail:GetRelationalDatabases"
- "macie2:GetMacieSession"
- "macie2:GetAutomatedDiscoveryConfiguration"
+ - "rolesanywhere:ListTagsForResource"
+ - "rolesanywhere:ListTrustAnchors"
- "s3:GetAccountPublicAccessBlock"
- "shield:DescribeProtection"
- "shield:GetSubscriptionState"
- - "securityhub:BatchImportFindings"
- "securityhub:GetFindings"
- "servicecatalog:Describe*"
- "servicecatalog:List*"
@@ -143,13 +228,20 @@ Resources:
- "tag:GetTagKeys"
- "wellarchitected:List*"
Resource: "*"
+ - Sid: AllowSecurityHubImportFindings
+ Effect: Allow
+ Action:
+ - "securityhub:BatchImportFindings"
+ Resource: "*"
- Sid: AllowAPIGatewayReadOnly
Effect: Allow
Action:
- "apigateway:GET"
Resource:
- - "arn:*:apigateway:*::/restapis/*"
- - "arn:*:apigateway:*::/apis/*"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/restapis/*"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/apis/*"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/domainnames"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/domainnames/*"
- !If
- OrganizationsEnabled
- PolicyName: ProwlerOrganizations
@@ -171,8 +263,12 @@ Resources:
Effect: Allow
Action:
- "organizations:RegisterDelegatedAdministrator"
- - "iam:CreateServiceLinkedRole"
Resource: "*"
+ - Sid: AllowCreateStackSetSLR
+ Effect: Allow
+ Action:
+ - "iam:CreateServiceLinkedRole"
+ Resource: !Sub "arn:${AWS::Partition}:iam::*:role/aws-service-role/member.org.stacksets.cloudformation.amazonaws.com/*"
- !Ref AWS::NoValue
- !If
- S3IntegrationEnabled
@@ -215,12 +311,287 @@ Resources:
- Key: "Name"
Value: "ProwlerScan"
+ # StackSet for deploying ProwlerScan role across multiple accounts
+ ProwlerScanStackSet:
+ Type: AWS::CloudFormation::StackSet
+ Condition: DeployStackSetEnabled
+ Properties:
+ StackSetName: !Sub "${AWS::StackName}-ProwlerScan-StackSet"
+ Description: Organizational StackSet to Deploy ProwlerScan IAM Role across accounts
+ PermissionModel: SERVICE_MANAGED
+ CallAs: !If [UseDelegatedAdmin, DELEGATED_ADMIN, !Ref "AWS::NoValue"]
+ Capabilities:
+ - CAPABILITY_NAMED_IAM
+ AutoDeployment:
+ Enabled: True
+ RetainStacksOnAccountRemoval: !Ref RetainStacksOnAccountRemoval
+ OperationPreferences:
+ FailureTolerancePercentage: !Ref FailureTolerancePercentage
+ MaxConcurrentPercentage: 100
+ Parameters:
+ - ParameterKey: ExternalId
+ ParameterValue: !Ref ExternalId
+ - ParameterKey: AccountId
+ ParameterValue: !Ref AccountId
+ - ParameterKey: IAMPrincipal
+ ParameterValue: !Ref IAMPrincipal
+ - ParameterKey: EnableOrganizations
+ ParameterValue: !Ref EnableOrganizations
+ - ParameterKey: EnableS3Integration
+ ParameterValue: !Ref EnableS3Integration
+ - ParameterKey: S3IntegrationBucketName
+ ParameterValue: !Ref S3IntegrationBucketName
+ - ParameterKey: S3IntegrationBucketAccountId
+ ParameterValue: !Ref S3IntegrationBucketAccountId
+ StackInstancesGroup:
+ - DeploymentTargets:
+ OrganizationalUnitIds:
+ - !Ref AWSOrganizationalUnitId
+ Regions:
+ - us-east-1
+ TemplateBody: |
+ AWSTemplateFormatVersion: "2010-09-09"
+
+ Description: |
+ This template creates the ProwlerScan IAM Role in this account with
+ all read-only permissions to scan your account for security issues.
+ Contains two AWS managed policies (SecurityAudit and ViewOnlyAccess) and an inline policy.
+ It sets the trust policy on that IAM Role to permit Prowler to assume that role.
+ This template is designed to be used in Prowler Cloud, but can also be used in other Prowler deployments.
+
+ ** DEPLOYED VIA SERVICE-MANAGED STACKSET **
+ This stack was automatically deployed across your organization using CloudFormation StackSets
+ with SERVICE_MANAGED permissions. It will auto-deploy to new accounts and can be centrally managed.
+
+ Parameters:
+ ExternalId:
+ Description: |
+ This is the External ID that Prowler will use to assume the role ProwlerScan IAM Role.
+ Type: String
+ MinLength: 1
+ AllowedPattern: ".+"
+ ConstraintDescription: "ExternalId must not be empty."
+ AccountId:
+ Description: |
+ AWS Account ID that will assume the role created, if you are deploying this template to be used in Prowler Cloud please do not edit this.
+ Type: String
+ Default: "232136659152"
+ MinLength: 12
+ MaxLength: 12
+ AllowedPattern: "[0-9]{12}"
+ ConstraintDescription: "AccountId must be a valid AWS Account ID."
+ IAMPrincipal:
+ Description: |
+ The IAM principal type and name that will be allowed to assume the role created, leave an * for all the IAM principals in your AWS account. If you are deploying this template to be used in Prowler Cloud please do not edit this.
+ Type: String
+ Default: role/prowler*
+ EnableOrganizations:
+ Description: |
+ Enable AWS Organizations discovery permissions. Set to true only when deploying this role in the management account.
+ This adds read-only Organizations permissions (e.g. ListAccounts, DescribeOrganization) and StackSet management permissions.
+ Type: String
+ Default: false
+ AllowedValues:
+ - true
+ - false
+ EnableS3Integration:
+ Description: |
+ Enable S3 integration for storing Prowler scan reports.
+ Type: String
+ Default: false
+ AllowedValues:
+ - true
+ - false
+ S3IntegrationBucketName:
+ Description: |
+ The S3 bucket name where Prowler will store scan reports for your cloud providers.
+ Type: String
+ Default: ""
+ S3IntegrationBucketAccountId:
+ Description: |
+ The AWS Account ID owner of the S3 Bucket.
+ Type: String
+ Default: ""
+
+ Conditions:
+ OrganizationsEnabled: !Equals [!Ref EnableOrganizations, true]
+ S3IntegrationEnabled: !Equals [!Ref EnableS3Integration, true]
+
+ Resources:
+ ProwlerScan:
+ Type: AWS::IAM::Role
+ Properties:
+ RoleName: ProwlerScan
+ AssumeRolePolicyDocument:
+ Version: "2012-10-17"
+ Statement:
+ - Effect: Allow
+ Principal:
+ AWS: !Sub "arn:${AWS::Partition}:iam::${AccountId}:root"
+ Action: "sts:AssumeRole"
+ Condition:
+ StringEquals:
+ "sts:ExternalId": !Sub ${ExternalId}
+ StringLike:
+ "aws:PrincipalArn": !Sub "arn:${AWS::Partition}:iam::${AccountId}:${IAMPrincipal}"
+ MaxSessionDuration: 3600
+ ManagedPolicyArns:
+ - !Sub "arn:${AWS::Partition}:iam::aws:policy/SecurityAudit"
+ - !Sub "arn:${AWS::Partition}:iam::aws:policy/job-function/ViewOnlyAccess"
+ Policies:
+ - PolicyName: ProwlerScan
+ PolicyDocument:
+ Version: "2012-10-17"
+ Statement:
+ - Sid: AllowMoreReadOnly
+ Effect: Allow
+ Action:
+ - "account:Get*"
+ - "appstream:Describe*"
+ - "appstream:List*"
+ - "backup:List*"
+ - "backup:Get*"
+ - "bedrock:List*"
+ - "bedrock:Get*"
+ - "cloudtrail:GetInsightSelectors"
+ - "codeartifact:List*"
+ - "codebuild:BatchGet*"
+ - "codebuild:ListReportGroups"
+ - "cognito-idp:GetUserPoolMfaConfig"
+ - "dlm:Get*"
+ - "drs:Describe*"
+ - "ds:Get*"
+ - "ds:Describe*"
+ - "ds:List*"
+ - "dynamodb:GetResourcePolicy"
+ - "ec2:GetEbsEncryptionByDefault"
+ - "ec2:GetSnapshotBlockPublicAccessState"
+ - "ec2:GetInstanceMetadataDefaults"
+ - "ecr:Describe*"
+ - "ecr:GetRegistryScanningConfiguration"
+ - "elasticfilesystem:DescribeBackupPolicy"
+ - "glue:GetConnections"
+ - "glue:GetSecurityConfiguration*"
+ - "glue:SearchTables"
+ - "glue:GetMLTransforms"
+ - "lambda:GetFunction*"
+ - "logs:FilterLogEvents"
+ - "lightsail:GetRelationalDatabases"
+ - "macie2:GetMacieSession"
+ - "macie2:GetAutomatedDiscoveryConfiguration"
+ - "s3:GetAccountPublicAccessBlock"
+ - "shield:DescribeProtection"
+ - "shield:GetSubscriptionState"
+ - "securityhub:GetFindings"
+ - "servicecatalog:Describe*"
+ - "servicecatalog:List*"
+ - "ssm:GetDocument"
+ - "ssm-incidents:List*"
+ - "states:ListTagsForResource"
+ - "support:Describe*"
+ - "tag:GetTagKeys"
+ - "wellarchitected:List*"
+ Resource: "*"
+ - Sid: AllowSecurityHubImportFindings
+ Effect: Allow
+ Action:
+ - "securityhub:BatchImportFindings"
+ Resource: "*"
+ - Sid: AllowAPIGatewayReadOnly
+ Effect: Allow
+ Action:
+ - "apigateway:GET"
+ Resource:
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/restapis/*"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/apis/*"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/domainnames"
+ - !Sub "arn:${AWS::Partition}:apigateway:*::/domainnames/*"
+ - !If
+ - OrganizationsEnabled
+ - PolicyName: ProwlerOrganizations
+ PolicyDocument:
+ Version: "2012-10-17"
+ Statement:
+ - Sid: AllowOrganizationsReadOnly
+ Effect: Allow
+ Action:
+ - "organizations:DescribeAccount"
+ - "organizations:DescribeOrganization"
+ - "organizations:ListAccounts"
+ - "organizations:ListAccountsForParent"
+ - "organizations:ListOrganizationalUnitsForParent"
+ - "organizations:ListRoots"
+ - "organizations:ListTagsForResource"
+ Resource: "*"
+ - Sid: AllowStackSetManagement
+ Effect: Allow
+ Action:
+ - "organizations:RegisterDelegatedAdministrator"
+ Resource: "*"
+ - Sid: AllowCreateStackSetSLR
+ Effect: Allow
+ Action:
+ - "iam:CreateServiceLinkedRole"
+ Resource: !Sub "arn:${AWS::Partition}:iam::*:role/aws-service-role/member.org.stacksets.cloudformation.amazonaws.com/*"
+ - !Ref AWS::NoValue
+ - !If
+ - S3IntegrationEnabled
+ - PolicyName: S3Integration
+ PolicyDocument:
+ Version: "2012-10-17"
+ Statement:
+ - Effect: Allow
+ Action:
+ - "s3:PutObject"
+ Resource:
+ - !Sub "arn:${AWS::Partition}:s3:::${S3IntegrationBucketName}/*"
+ Condition:
+ StringEquals:
+ "s3:ResourceAccount": !Sub ${S3IntegrationBucketAccountId}
+ - Effect: Allow
+ Action:
+ - "s3:ListBucket"
+ Resource:
+ - !Sub "arn:${AWS::Partition}:s3:::${S3IntegrationBucketName}"
+ Condition:
+ StringEquals:
+ "s3:ResourceAccount": !Sub ${S3IntegrationBucketAccountId}
+ - Effect: Allow
+ Action:
+ - "s3:DeleteObject"
+ Resource:
+ - !Sub "arn:${AWS::Partition}:s3:::${S3IntegrationBucketName}/*test-prowler-connection.txt"
+ Condition:
+ StringEquals:
+ "s3:ResourceAccount": !Sub ${S3IntegrationBucketAccountId}
+ - !Ref AWS::NoValue
+ Tags:
+ - Key: "Service"
+ Value: "https://prowler.com"
+ - Key: "Support"
+ Value: "support@prowler.com"
+ - Key: "CloudFormation"
+ Value: "true"
+ - Key: "Name"
+ Value: "ProwlerScan"
+
+ Outputs:
+ ProwlerScanRoleArn:
+ Description: "ARN of the ProwlerScan IAM Role"
+ Value: !GetAtt ProwlerScan.Arn
+ Export:
+ Name: !Sub "${AWS::StackName}-ProwlerScanRoleArn"
+
Metadata:
- AWS::CloudFormation::StackName: "Prowler"
AWS::CloudFormation::Interface:
ParameterGroups:
- Label:
- default: Required
+ default: Deployment Options
+ Parameters:
+ - DeployLocalRole
+ - DeployStackSet
+ - Label:
+ default: Required Prowler Configuration
Parameters:
- ExternalId
- AccountId
@@ -228,14 +599,27 @@ Metadata:
- EnableOrganizations
- EnableS3Integration
- Label:
- default: Optional
+ default: Optional S3 Integration
Parameters:
- S3IntegrationBucketName
- S3IntegrationBucketAccountId
+ - Label:
+ default: StackSet Configuration (Required if DeployStackSet is true)
+ Parameters:
+ - AWSOrganizationalUnitId
+ - DeployFromDelegatedAdmin
+ - RetainStacksOnAccountRemoval
+ - FailureTolerancePercentage
Outputs:
- ProwlerScanRoleArn:
- Description: "ARN of the ProwlerScan IAM Role"
+ LocalProwlerScanRoleArn:
+ Condition: DeployLocalRoleEnabled
+ Description: "ARN of the ProwlerScan IAM Role deployed locally in this account"
Value: !GetAtt ProwlerScan.Arn
Export:
Name: !Sub "${AWS::StackName}-ProwlerScanRoleArn"
+
+ StackSetId:
+ Condition: DeployStackSetEnabled
+ Description: "StackSet ID for the ProwlerScan role deployment across accounts"
+ Value: !Ref ProwlerScanStackSet
diff --git a/permissions/templates/terraform/README.md b/permissions/templates/terraform/README.md
index ec41103e5e..1bb037daa2 100644
--- a/permissions/templates/terraform/README.md
+++ b/permissions/templates/terraform/README.md
@@ -28,12 +28,12 @@ This Terraform configuration creates the necessary IAM role and policies to allo
### Usage Examples
-#### Basic deployment (without S3 integration):
+#### Basic deployment (without S3 integration)
```bash
terraform apply -var="external_id=your-external-id-here"
```
-#### With S3 integration enabled:
+#### With S3 integration enabled
```bash
terraform apply \
-var="external_id=your-external-id-here" \
@@ -42,14 +42,14 @@ terraform apply \
-var="s3_integration_bucket_account_id=123456789012"
```
-#### Using terraform.tfvars file (Recommended):
+#### Using terraform.tfvars file (Recommended)
```bash
cp terraform.tfvars.example terraform.tfvars
# Edit the file with your values
terraform apply
```
-#### Command line variables (Alternative):
+#### Command line variables (Alternative)
```bash
terraform apply -var="external_id=your-external-id-here"
```
diff --git a/prowler/AGENTS.md b/prowler/AGENTS.md
index 9c0895d3a1..ab3ba1ce67 100644
--- a/prowler/AGENTS.md
+++ b/prowler/AGENTS.md
@@ -7,7 +7,7 @@
> - [`prowler-compliance`](../skills/prowler-compliance/SKILL.md) - Compliance framework structure
> - [`pytest`](../skills/pytest/SKILL.md) - Generic pytest patterns
-### Auto-invoke Skills
+## Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
@@ -44,7 +44,7 @@ The Prowler SDK is the core Python engine powering cloud security assessments ac
### Provider Architecture
-```
+```text
prowler/providers/{provider}/
├── {provider}_provider.py # Main provider class
├── models.py # Provider-specific models
@@ -91,7 +91,7 @@ Python 3.10+ | uv | pytest | moto (AWS mocking) | Pre-commit hooks (black, flake
## PROJECT STRUCTURE
-```
+```text
prowler/
├── __main__.py # CLI entry point
├── config/ # Global configuration
diff --git a/prowler/CHANGELOG.md b/prowler/CHANGELOG.md
index ce0b5cb581..408c76d3e1 100644
--- a/prowler/CHANGELOG.md
+++ b/prowler/CHANGELOG.md
@@ -2,16 +2,343 @@
All notable changes to the **Prowler SDK** are documented in this file.
-## [5.28.0] (Prowler UNRELEASED)
+<!-- changelog: release notes start -->
+
+## [5.35.0] (Prowler v5.35.0)
### 🚀 Added
-- `entra_app_registration_client_secret_unused` check for M365 provider [(#11232)](https://github.com/prowler-cloud/prowler/pull/11232)
-- `cloudsql_instance_cmek_encryption_enabled` check for GCP provider [(#11023)](https://github.com/prowler-cloud/prowler/pull/11023)
+- `excluded_checks` and `excluded_services` in scan configurations to narrow the execution scope [(#12028)](https://github.com/prowler-cloud/prowler/pull/12028)
+
+### 🔐 Security
+
+- Jira tenant information requests validate site names and do not follow redirects [(#12012)](https://github.com/prowler-cloud/prowler/pull/12012)
---
-## [5.27.1] (Prowler UNRELEASED)
+## [5.34.0] (Prowler v5.34.0)
+
+### 🚀 Added
+
+- `elbv2_listener_pqc_tls_enabled` check for AWS provider, verifying that ELBv2 listeners use post-quantum TLS policies [(#11254)](https://github.com/prowler-cloud/prowler/pull/11254)
+- `iaas_server_public_ip_attached` check for STACKIT provider, flagging IaaS servers that have a public IP address directly attached to a network interface [(#11549)](https://github.com/prowler-cloud/prowler/pull/11549)
+- Changelog fragment workflow for SDK, API, UI, and MCP Server releases, including PR attribution, fragment validation, release compilation, and preserved section ordering [(#11572)](https://github.com/prowler-cloud/prowler/pull/11572)
+- E2E Networks provider with 27 checks across compute nodes, networking, security groups, load balancers, block/file storage, and managed databases [(#11654)](https://github.com/prowler-cloud/prowler/pull/11654)
+- `datapipeline_pipeline_no_secrets_in_definition` check for AWS provider, scanning Data Pipeline object fields, parameter objects, and parameter values for hardcoded secrets with Kingfisher [(#11821)](https://github.com/prowler-cloud/prowler/pull/11821)
+- `amplify_app_no_secrets_in_environment` check for AWS provider, scanning Amplify app and branch environment variables and build settings for hardcoded secrets [(#11825)](https://github.com/prowler-cloud/prowler/pull/11825)
+- `ec2_ami_account_block_public_access` check for AWS provider, verifying AMI block public access is enabled at the account level in each Region so AMIs cannot be shared publicly [(#11828)](https://github.com/prowler-cloud/prowler/pull/11828)
+- `core_readonly_root_filesystem_enabled` check for Kubernetes provider, verifying that every container in each Pod explicitly sets `readOnlyRootFilesystem: true` in its security context [(#11835)](https://github.com/prowler-cloud/prowler/pull/11835)
+- `core_minimize_hostpath_volume_mounts` check for Kubernetes provider, detecting Pods that use `hostPath` volumes [(#11837)](https://github.com/prowler-cloud/prowler/pull/11837)
+- `app_function_ensure_http_is_redirected_to_https` check for Azure provider, verifying that Function Apps enforce HTTPS-only traffic [(#11929)](https://github.com/prowler-cloud/prowler/pull/11929)
+
+### 🔄 Changed
+
+- Add missing trailing newlines to compliance, region, and fixture data files for POSIX compliance [(#11765)](https://github.com/prowler-cloud/prowler/pull/11765)
+- Oracle Cloud API key authentication now uses an internal bootstrap region when no explicit scan region filter is provided [(#11853)](https://github.com/prowler-cloud/prowler/pull/11853)
+- Redesign the local dashboard sidebar and informational pages [(#11972)](https://github.com/prowler-cloud/prowler/pull/11972)
+
+---
+
+## [5.33.2] (Prowler v5.33.2)
+
+### 🐞 Fixed
+
+- EC2 AMI loading now targets Amazon-owned AMIs used by audited instances, reducing AWS API calls during EC2 scans [(#11958)](https://github.com/prowler-cloud/prowler/pull/11958)
+- `ec2_instance_account_imdsv2_enabled` findings now use regional resource ARNs, preventing findings from different AWS Regions from collapsing into one resource [(#11966)](https://github.com/prowler-cloud/prowler/pull/11966)
+
+---
+
+## [5.33.1] (Prowler v5.33.1)
+
+### 🐞 Fixed
+
+- ECS task definition resource limits now select the latest task definitions by registration date instead of relying on ARN ordering [(#11891)](https://github.com/prowler-cloud/prowler/pull/11891)
+- `dlm_ebs_snapshot_lifecycle_policy_exists` no longer initializes the full EC2 inventory just to detect EBS snapshots, avoiding slow scans when checking DLM lifecycle policies [(#11900)](https://github.com/prowler-cloud/prowler/pull/11900)
+- `dms_instance_no_public_access` no longer initializes the full EC2 service when there are no DMS replication instances [(#11902)](https://github.com/prowler-cloud/prowler/pull/11902)
+- `organizations_scp_check_deny_regions` no longer reports false `FAIL` for AWS Organizations that restrict regions with Allow-based SCPs; the Allow path now checks the statement `Effect` instead of an always-false comparison that made it unreachable [(#11915)](https://github.com/prowler-cloud/prowler/pull/11915)
+- Jira issue creation failures now preserve safe structured response details from Jira [(#11925)](https://github.com/prowler-cloud/prowler/pull/11925)
+- Azure Function App optional permission failures now log as warnings, and Function App environment variable fields use the correct spelling internally [(#11926)](https://github.com/prowler-cloud/prowler/pull/11926)
+
+---
+
+## [5.33.0] (Prowler v5.33.0)
+
+### 🐞 Fixed
+
+- Azure resource group scoped scans now keep subscription entries when scoped resource listing fails, clarify helper documentation and test organization, and align the resource group documentation example with the described values [(#11796)](https://github.com/prowler-cloud/prowler/pull/11796)
+- Azure `postgresql_flexible_server_log_retention_days_greater_3` check now queries the `logfiles.retention_days` configuration parameter instead of `log_retention_days` (which only exists on the retired Single Server), fixing false `FAIL` results on every Flexible Server regardless of the actual retention value [(#11761)](https://github.com/prowler-cloud/prowler/pull/11761)
+
+---
+
+## [5.32.1] (Prowler v5.32.1)
+
+### 🐞 Fixed
+
+- `KeyError: 'MANUAL'` crash while rendering the compliance summary table (e.g. CIS Microsoft 365) when a framework has manual, checks-less requirements with a Level 1/Level 2 profile; `MANUAL` findings are now skipped in the PASS/FAIL section tally instead of raising [(#11822)](https://github.com/prowler-cloud/prowler/issues/11822)
+
+---
+
+## [5.32.0] (Prowler v5.32.0)
+
+### 🚀 Added
+
+- `exchange_application_access_policy_restricts_mailbox_apps` check for M365 provider, verifying every service principal with Microsoft Graph application-level Exchange mailbox permissions is restricted by an Exchange Online Application Access Policy, preventing tenant-wide mailbox access by unscoped applications [(#11247)](https://github.com/prowler-cloud/prowler/pull/11247)
+- Per-requirement configuration validation for compliance frameworks via `ConfigRequirements`, so a requirement is reported as FAIL when its configurable checks ran with a configuration too loose to satisfy it (applied across all compliance outputs: CSV, OCSF, and console tables) [(#11669)](https://github.com/prowler-cloud/prowler/pull/11669)
+- `entra_conditional_access_policy_explicitly_targets_azure_devops` check for M365 provider, verifying at least one enabled Conditional Access policy explicitly includes the Azure DevOps cloud application instead of relying on a broad "All cloud apps" policy [(#11182)](https://github.com/prowler-cloud/prowler/pull/11182)
+- `entra_conditional_access_policy_no_exclusion_gaps` check for M365 provider, verifying every user, group, role, or application excluded from an enabled Conditional Access policy stays in scope of another enabled policy [(#11577)](https://github.com/prowler-cloud/prowler/pull/11577)
+- `entra_conditional_access_policy_groups_management_restricted` check for M365 provider, verifying every security group referenced by an enabled or report-only Conditional Access policy is management-restricted or role-assignable [(#11342)](https://github.com/prowler-cloud/prowler/pull/11342)
+- `stepfunctions_statemachine_encrypted_with_cmk` check for AWS provider, verifying that each Step Functions state machine uses a customer-managed KMS key for encryption at rest rather than the default AWS-owned key [(#11538)](https://github.com/prowler-cloud/prowler/pull/11538)
+- CIS Controls v8.1 universal compliance framework mapping existing checks across 18 providers (AWS, Azure, GCP, Kubernetes, M365, GitHub, AlibabaCloud, OracleCloud, GoogleWorkspace, Okta, Cloudflare, Vercel, MongoDB Atlas, OpenStack, Linode, StackIT, NHN, and Scaleway) to the 18 CIS Critical Security Controls and their Safeguards [(#11700)](https://github.com/prowler-cloud/prowler/pull/11700)
+- CIS Microsoft 365 Foundations Benchmark v7.0.0 compliance framework for the M365 provider [(#11699)](https://github.com/prowler-cloud/prowler/pull/11699)
+- `waf_regional_webacl_logging_enabled` check for AWS provider, verifying that each AWS WAF Classic Regional Web ACL has logging enabled to a Kinesis Data Firehose stream [(#11539)](https://github.com/prowler-cloud/prowler/pull/11539)
+- `sdk_only` provider property (default `true`) and `Provider.get_app_providers()`, so a provider (built-in or external) stays CLI/SDK-only and hidden from the app unless it declares `sdk_only = False` [(#11427)](https://github.com/prowler-cloud/prowler/pull/11427)
+- `Provider.get_scan_arguments()`, `Provider.get_connection_arguments()` and `Provider.get_credentials_schema()` contract methods, so a provider persisted as a stored uid plus a secret dict can be constructed and validated programmatically (to be consumed by the API in a later change) [(#11578)](https://github.com/prowler-cloud/prowler/pull/11578)
+- Okta API request throttling to proactively stay under rate limits, configurable via `okta_requests_per_second` in the config file and the `--okta-requests-per-second` CLI flag, plus configurable retries via `okta_max_retries` / `--okta-retries-max-attempts` as a safety net [(#11702)](https://github.com/prowler-cloud/prowler/pull/11702)
+- CIS Amazon Web Services Foundations Benchmark v7.0.0 compliance framework for the AWS provider, adding the new Organizations section (2.1.1-2.1.6), resource policy (2.21), web front-end access logging (4.10), and VPC Endpoints (6.8) recommendations [(#11707)](https://github.com/prowler-cloud/prowler/pull/11707)
+- CIS Microsoft Azure Foundations Benchmark v6.0.0 compliance framework for the Azure provider [(#11708)](https://github.com/prowler-cloud/prowler/pull/11708)
+- CIS Google Cloud Platform Foundation Benchmark v5.0.0 compliance framework for the GCP provider [(#11714)](https://github.com/prowler-cloud/prowler/pull/11714)
+- CIS Kubernetes Benchmark v2.0.1 compliance framework for the Kubernetes provider [(#11722)](https://github.com/prowler-cloud/prowler/pull/11722)
+- CIS GitHub Benchmark v1.2.0 compliance framework for the GitHub provider [(#11719)](https://github.com/prowler-cloud/prowler/pull/11719)
+- AWS Bedrock AgentCore privilege escalation paths in the IAM privilege escalation checks, covering Runtime, Harness, Code Interpreter and Custom Browser [(#11726)](https://github.com/prowler-cloud/prowler/pull/11726)
+- `--scan-secrets-validate` flag and `aws.secrets_validate` configuration option to optionally validate the secrets discovered by the secret-scanning checks against the provider APIs; secrets confirmed to be live are reported as critical [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- `apigateway_restapi_no_secrets_in_stage_variables` check for AWS provider, scanning API Gateway REST API stage variables for hardcoded secrets such as passwords, API keys, and tokens [(#11188)](https://github.com/prowler-cloud/prowler/pull/11188)
+- `s3_bucket_object_public` check for AWS provider, spot-checking a configurable sample of object ACLs in each bucket and flagging objects granted to the AllUsers or AuthenticatedUsers groups; disabled by default and opted into via the `s3_bucket_object_public_enabled` configuration option [(#9517)](https://github.com/prowler-cloud/prowler/pull/9517)
+- Azure provider now supports `--azure-resource-group` to scope resource-level checks to specific resource groups across all accessible subscriptions [(#10657)](https://github.com/prowler-cloud/prowler/pull/10657)
+
+### 🔄 Changed
+
+- Replaced the `detect-secrets` library with [Kingfisher](https://github.com/mongodb/kingfisher) as the engine for the secret-scanning checks; scans run fully offline by default and obvious placeholder values are no longer reported as findings [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- Removed the `detect_secrets_plugins` configuration option, which is no longer used by the new secret-scanning engine [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- `awslambda_function_no_secrets_in_code` now supports a `secrets_ignore_files` audit-config option to skip files inside the deployment package by glob pattern (e.g. `*.deps.json`), suppressing .NET dependency-manifest false positives without masking real secrets [(#11222)](https://github.com/prowler-cloud/prowler/pull/11222)
+- AWS scans for EBS snapshots, Backup recovery points, CloudWatch log groups, Lambda functions, ECS task definitions, and CodeArtifact packages now support configurable resource analysis limits via `aws.max_scanned_resources_per_service`; limits are disabled by default and only positive values cap analyzed resources [(#11228)](https://github.com/prowler-cloud/prowler/pull/11228)
+
+### 🐞 Fixed
+
+- GitHub `repository_has_codeowners_file` check no longer flags archived repositories, since they are read-only and cannot be updated without first being unarchived, making the finding not actionable [(#11735)](https://github.com/prowler-cloud/prowler/pull/11735)
+- Report secret-scanning checks as `MANUAL` instead of `PASS` when the scanner fails (non-zero exit, timeout, unparseable output or missing binary), so a scanner failure is no longer indistinguishable from "no secrets found" [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- Avoid a false `FAIL` in `cloudwatch_log_group_no_secrets_in_logs` when a multiline event's secrets are all removed by `secrets_ignore_patterns` during the rescan [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- Key the `cloudwatch_log_group_no_secrets_in_logs` secret scan by log group ARN instead of name, so same-named log groups and streams in different regions no longer collide and reuse each other's findings [(#11694)](https://github.com/prowler-cloud/prowler/pull/11694)
+- Compliance frameworks contributed by several external packages under the same provider are now merged instead of overwritten, so every entry-point directory a provider contributes is discovered [(#11578)](https://github.com/prowler-cloud/prowler/pull/11578)
+- Azure PostgreSQL flexible server collection no longer drops the remaining servers in a subscription when one server fails to collect; the `connection_throttle.enable` parameter (removed in PostgreSQL 16+) is treated as absent only when the Azure SDK reports it as not found, so unexpected lookup failures are not silently reported as throttling disabled [(#11595)](https://github.com/prowler-cloud/prowler/pull/11595)
+- Azure `keyvault_logging_enabled` now accepts Key Vault diagnostic settings that enable the explicit `AuditEvent` category, avoiding false failures when Azure returns category-based logs without category groups [(#11660)](https://github.com/prowler-cloud/prowler/pull/11660)
+- GitHub default branch protection checks now evaluate repository rulesets in addition to classic branch protection, avoiding false positives for repositories that enforce protection through rulesets [(#11723)](https://github.com/prowler-cloud/prowler/pull/11723)
+- Okta, Alibaba Cloud and OpenStack scan-config sections are now validated against a registered schema instead of being silently accepted, so their configurable thresholds (session/idle timeouts, retention days, image-sharing and secret-scanning settings) log a warning and fall back to the built-in default whenever a value is out of range [(#11725)](https://github.com/prowler-cloud/prowler/pull/11725)
+
+---
+
+## [5.31.1] (Prowler v5.31.1)
+
+### 🐞 Fixed
+
+- Alibaba Cloud `ram_password_policy_number` and `cs_kubernetes_cluster_check_weekly` checks not being loaded due to missing implementation and package files [(#11683)](https://github.com/prowler-cloud/prowler/pull/11683)
+
+---
+
+## [5.31.0] (Prowler v5.31.0)
+
+### 🚀 Added
+
+- Support for Python 3.13 [(#9293)](https://github.com/prowler-cloud/prowler/pull/9293)
+- `securityhub_delegated_admin_enabled_all_regions` check for AWS provider, verifying that Security Hub has a delegated administrator, is active in all opted-in regions, and has organization auto-enable on [(#11259)](https://github.com/prowler-cloud/prowler/pull/11259)
+- `config_delegated_admin_and_org_aggregator_all_regions` check for AWS provider, verifying that AWS Config has a delegated administrator and an organization aggregator covering all AWS regions [(#11259)](https://github.com/prowler-cloud/prowler/pull/11259)
+- `sagemaker_clarify_exists` check for AWS provider [(#11211)](https://github.com/prowler-cloud/prowler/pull/11211)
+- `cloudsql_instance_high_availability_enabled` check for GCP provider, verifying Cloud SQL primary instances use `REGIONAL` availability for automatic zone failover [(#11024)](https://github.com/prowler-cloud/prowler/pull/11024)
+- `cloudfunction_function_inside_vpc` check for GCP provider, verifying Cloud Functions have a Serverless VPC Access connector for private egress [(#11021)](https://github.com/prowler-cloud/prowler/pull/11021)
+- `cloudfunction_function_not_publicly_accessible` check for GCP provider, detecting Cloud Functions with `allUsers` or `allAuthenticatedUsers` IAM invocation bindings [(#11022)](https://github.com/prowler-cloud/prowler/pull/11022)
+- `secretmanager_secret_not_publicly_accessible` check for GCP provider, detecting Secret Manager secrets with public IAM bindings [(#11025)](https://github.com/prowler-cloud/prowler/pull/11025)
+- `secretmanager_secret_rotation_enabled` check for GCP provider, verifying Secret Manager secrets have automatic rotation configured within 90 days [(#11026)](https://github.com/prowler-cloud/prowler/pull/11026)
+- `identity_storage_service_level_admins_scoped` check for OCI provider CIS 3.1 control 1.15, ensuring storage service-level administrators exclude delete permissions [(#11523)](https://github.com/prowler-cloud/prowler/pull/11523)
+- `cosmosdb_account_automatic_failover_enabled` check for Azure provider [(#11031)](https://github.com/prowler-cloud/prowler/pull/11031)
+- `cosmosdb_account_backup_policy_continuous` check for Azure provider [(#11032)](https://github.com/prowler-cloud/prowler/pull/11032)
+- `cosmosdb_account_minimum_tls_version` check for Azure provider, verifying Cosmos DB accounts enforce TLS 1.2 or higher for client connections [(#11033)](https://github.com/prowler-cloud/prowler/pull/11033)
+- `cosmosdb_account_public_network_access_disabled` check for Azure provider, verifying Cosmos DB accounts have public network access disabled so connectivity is restricted to private endpoints or VNet service endpoints [(#11034)](https://github.com/prowler-cloud/prowler/pull/11034)
+- `databricks_workspace_public_network_access_disabled` check for Azure provider, verifying Databricks workspaces have public network access disabled so connectivity is restricted to Azure Private Link private endpoints [(#11035)](https://github.com/prowler-cloud/prowler/pull/11035)
+- `databricks_workspace_no_public_ip_enabled` check for Azure provider, verifying Databricks workspaces use secure cluster connectivity (no public IP) so compute nodes are not assigned public IP addresses [(#11036)](https://github.com/prowler-cloud/prowler/pull/11036)
+- `defender_ensure_defender_cspm_is_on` check for Azure provider, verifying Microsoft Defender Cloud Security Posture Management (CSPM) is enabled on the Standard tier [(#11037)](https://github.com/prowler-cloud/prowler/pull/11037)
+- `mysql_flexible_server_geo_redundant_backup_enabled` check for Azure provider, verifying MySQL Flexible Servers have geo-redundant backup enabled so backups are replicated to the paired region [(#11041)](https://github.com/prowler-cloud/prowler/pull/11041)
+- `mysql_flexible_server_high_availability_enabled` check for Azure provider, verifying MySQL Flexible Servers have high availability enabled for automatic failover to a standby replica [(#11042)](https://github.com/prowler-cloud/prowler/pull/11042)
+- `postgresql_flexible_server_geo_redundant_backup_enabled` check for Azure provider, verifying PostgreSQL Flexible Servers have geo-redundant backup enabled so backups are replicated to the paired region [(#11045)](https://github.com/prowler-cloud/prowler/pull/11045)
+- `postgresql_flexible_server_high_availability_enabled` check for Azure provider, verifying PostgreSQL Flexible Servers have high availability enabled for automatic failover to a standby replica [(#11046)](https://github.com/prowler-cloud/prowler/pull/11046)
+- `aks_cluster_azure_monitor_enabled` check for Azure provider, verifying AKS clusters have Azure Monitor (Container Insights) enabled for metrics, logs, and alerting [(#11029)](https://github.com/prowler-cloud/prowler/pull/11029)
+- `aks_cluster_local_accounts_disabled` check for Azure provider, verifying AKS clusters have local accounts disabled so authentication is forced through Microsoft Entra ID [(#11030)](https://github.com/prowler-cloud/prowler/pull/11030)
+- `network_subnet_nsg_associated` check for Azure provider, verifying virtual network subnets have a network security group associated to enforce traffic filtering [(#11043)](https://github.com/prowler-cloud/prowler/pull/11043)
+- `network_vnet_ddos_protection_enabled` check for Azure provider, verifying virtual networks have Azure DDoS Network Protection enabled [(#11044)](https://github.com/prowler-cloud/prowler/pull/11044)
+- `entra_app_registration_credential_not_expired` check for Azure provider, verifying Entra ID app registration secrets and certificates are not expired, expiring within 30 days, or without an expiration date [(#11038)](https://github.com/prowler-cloud/prowler/pull/11038)
+- `entra_authentication_methods_policy_strong_auth_enforced` check for Azure provider, verifying the Entra ID authentication methods policy enforces MFA registration and enables at least one strong method (Microsoft Authenticator, FIDO2, or X.509 certificate) [(#11039)](https://github.com/prowler-cloud/prowler/pull/11039)
+- `entra_user_with_recent_sign_in` check for Azure provider, detecting stale enabled accounts that have not signed in within the last 90 days (requires Entra ID P1/P2 licensing for sign-in activity) [(#11040)](https://github.com/prowler-cloud/prowler/pull/11040)
+- `aks_cluster_auto_upgrade_enabled` check for Azure provider [(#11027)](https://github.com/prowler-cloud/prowler/pull/11027)
+- Public `Provider.get_class()` method that resolves a provider class by name for both built-in and external (entry-point) providers [(#11398)](https://github.com/prowler-cloud/prowler/pull/11398)
+- Jira timeout preventing the calls from hanging indefinitely when the Jira endpoint is unreachable or slow [(#11602)](https://github.com/prowler-cloud/prowler/pull/11602)
+- TLS certificate verification in the `codepipeline_project_repo_private` check, which previously used an unverified SSL context, leaving the repository-visibility probe open to MITM tampering [(#11603)](https://github.com/prowler-cloud/prowler/pull/11603)
+- Support for Linode cloud provider, with compute, networking and administration services [(#11633)](https://github.com/prowler-cloud/prowler/pull/11633)
+- DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) compliance coverage for the Azure provider, mapping existing Azure checks across the five DORA pillars [(#11551)](https://github.com/prowler-cloud/prowler/pull/11551)
+- Rename DORA to DORA_2022_2554 to follow the naming <name>_<version> in compliance frameworks [(#11551)](https://github.com/prowler-cloud/prowler/pull/11551)
+- `entra_directory_sync_object_takeover_blocked` check for the M365 provider, verifying that hybrid Entra tenants block cloud object takeover through both soft-match and hard-match directory synchronization [(#11098)](https://github.com/prowler-cloud/prowler/pull/11098)
+- `entra_conditional_access_policy_no_deleted_object_references` check for M365 provider [(#11236)](https://github.com/prowler-cloud/prowler/pull/11236)
+- `aks_cluster_defender_enabled` check for Azure provider, verifying that AKS clusters have Microsoft Defender security monitoring enabled [(#11028)](https://github.com/prowler-cloud/prowler/pull/11028)
+- `recovery_vault_has_protected_items` check for Azure provider, verifying that Recovery Services vaults have at least one protected backup item [(#11048)](https://github.com/prowler-cloud/prowler/pull/11048)
+- DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) compliance coverage for the GCP provider, mapping existing GCP checks across the five DORA pillars [(#11642)](https://github.com/prowler-cloud/prowler/pull/11642)
+- DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) compliance coverage for the Cloudflare provider, mapping existing Cloudflare edge/network checks across the applicable DORA pillars [(#11645)](https://github.com/prowler-cloud/prowler/pull/11645)
+- DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) compliance coverage for the AlibabaCloud provider, mapping existing AlibabaCloud checks across the applicable DORA pillars [(#11646)](https://github.com/prowler-cloud/prowler/pull/11646)
+- `cloudfront_distributions_pqc_tls_enabled` check for AWS provider to verify CloudFront distributions enforce a post-quantum TLS 1.3 security policy [(#11317)](https://github.com/prowler-cloud/prowler/pull/11317)
+- `apigateway_domain_name_pqc_tls_enabled` check for AWS provider to verify API Gateway custom domain names use a post-quantum TLS security policy [(#11316)](https://github.com/prowler-cloud/prowler/pull/11316)
+- `transfer_server_pqc_ssh_kex_enabled` check for AWS provider to verify Transfer Family servers use a post-quantum hybrid SSH key exchange security policy [(#11315)](https://github.com/prowler-cloud/prowler/pull/11315)
+- `acmpca_certificate_authority_pqc_key_algorithm` check and new `acmpca` service for AWS provider to verify AWS Private CA certificate authorities use a post-quantum (ML-DSA) key algorithm [(#11318)](https://github.com/prowler-cloud/prowler/pull/11318)
+- `rolesanywhere_trust_anchor_pqc_pki` check and new `rolesanywhere` service for AWS provider to verify IAM Roles Anywhere trust anchors are backed by a post-quantum (ML-DSA) PKI [(#11319)](https://github.com/prowler-cloud/prowler/pull/11319)
+- Kubernetes core checks for container CPU limits, CPU requests, memory limits, memory requests, fixed image tags, liveness probes, and readiness probes [(#11373)](https://github.com/prowler-cloud/prowler/pull/11373)
+- `recovery_vault_backup_policy_retention_adequate` check for Azure provider, verifying Recovery Services backup policies retain daily backups for at least 30 days [(#11047)](https://github.com/prowler-cloud/prowler/pull/11047)
+
+### 🔄 Changed
+
+- Replaced the unmaintained `awsipranges` dependency with a small standard-library helper for the `route53_dangling_ip_subdomain_takeover` check [(#9293)](https://github.com/prowler-cloud/prowler/pull/9293)
+
+### 🐞 Fixed
+
+- Azure PostgreSQL flexible server inventory no longer aborts the whole subscription when the `connection_throttle.enable` parameter is missing (e.g. PostgreSQL v18), and logs the expected "Entra ID authentication not enabled" case as a warning instead of an error, so servers are still scanned [(#11045)](https://github.com/prowler-cloud/prowler/pull/11045)
+- `iam_policy_allows_privilege_escalation` now includes the `privilege-escalation` category [(#11648)](https://github.com/prowler-cloud/prowler/pull/11648)
+
+### 🔐 Security
+
+- `pytest` from 8.3.5 to 9.0.3, patching a known vulnerability in the SDK test dependency [(#11291)](https://github.com/prowler-cloud/prowler/pull/11291)
+- `black` from 25.1.0 to 26.3.1, patching a known vulnerability in the SDK formatter dependency [(#11290)](https://github.com/prowler-cloud/prowler/pull/11290)
+- `microsoft-kiota-*` to 1.9.9 and `aiohttp` to 3.14.0, patching known CVEs [(#11596)](https://github.com/prowler-cloud/prowler/pull/11596)
+- Container base image bumped to `python:3.12.13-slim-bookworm` (patches `libgnutls30` CVE-2026-33845 and CVE-2026-42010) and `trivy` bumped to 0.71.0 (patches embedded `golang.org/x/crypto` and Go stdlib CVEs); `.trivyignore` documents remaining bookworm criticals with no-fix or not-affected rationale [(#11592)](https://github.com/prowler-cloud/prowler/pull/11592)
+
+---
+
+## [5.30.3] (Prowler v5.30.3)
+
+### 🐞 Fixed
+
+- CLI compliance summary tables no longer undercount findings mapped to multiple sections nor double-count a single finding mapped to several requirements within the same group/split, and the Provider column no longer leaks a value from another framework [(#11567)](https://github.com/prowler-cloud/prowler/pull/11567)
+
+---
+
+## [5.30.2] (Prowler v5.30.2)
+
+### 🐞 Fixed
+
+- GCP `logging_log_metric_filter_and_alert_*` checks now credit org-level aggregated sinks filtered to the Admin Activity audit stream [(#11575)](https://github.com/prowler-cloud/prowler/pull/11575)
+- A broken built-in provider no longer aborts the CLI when a different provider was invoked [(#11618)](https://github.com/prowler-cloud/prowler/pull/11618)
+- GCP organization scans with `--organization-id` no longer silently fall back to the credentials' host project when the Cloud Asset API call fails [(#11280)](https://github.com/prowler-cloud/prowler/pull/11280)
+
+---
+
+## [5.30.0] (Prowler v5.30.0)
+
+### 🚀 Added
+
+- DISA Okta IDaaS STIG V1R2 compliance framework for the Okta provider, with a dedicated CSV output formatter and terminal summary table [(#11428)](https://github.com/prowler-cloud/prowler/pull/11428)
+- `sagemaker_models_monitor_enabled` check for AWS provider, verifying that each SageMaker monitoring schedule is in the `Scheduled` state so data and model drift is actively detected [(#11278)](https://github.com/prowler-cloud/prowler/pull/11278)
+- DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) universal compliance framework with AWS provider coverage across the five DORA pillars [(#11131)](https://github.com/prowler-cloud/prowler/pull/11131)
+- Okta authenticator and password policy checks for STIG-aligned hardening requirements [(#11465)](https://github.com/prowler-cloud/prowler/pull/11465)
+- Okta network zone check to detect whether anonymized proxy traffic is blocked [(#11463)](https://github.com/prowler-cloud/prowler/pull/11463)
+- Okta API token checks for super admin ownership and network zone restrictions [(#11464)](https://github.com/prowler-cloud/prowler/pull/11464)
+- Support for external/custom providers, checks, and compliance frameworks without modifying core code [(#10700)](https://github.com/prowler-cloud/prowler/pull/10700)
+- `elbv2_alb_drop_invalid_header_fields_enabled` check for AWS provider, verifying Application Load Balancers have `routing.http.drop_invalid_header_fields.enabled` set to `true` to mitigate HTTP desync attacks (AWS FSBP ELB.4) [(#11471)](https://github.com/prowler-cloud/prowler/pull/11471)
+- `user`, `systemlog` and `idp` service for Okta provider with `user_inactivity_automation_35d_enabled`, `systemlog_streaming_enabled` and `idp_smart_card_dod_approved_ca` checks [(#11496)](https://github.com/prowler-cloud/prowler/pull/11496)
+- External multi-provider compliance frameworks can be registered via the `prowler.compliance.universal` entry point group [(#11490)](https://github.com/prowler-cloud/prowler/pull/11490)
+- AWS AI Security Framework support in the CLI dashboard [(#11475)](https://github.com/prowler-cloud/prowler/pull/11475)
+- `entra_service_principal_privileged_role_no_owners` check for M365 provider, failing when a service principal with a permanent Tier 0 directory role has owners on the service principal or its parent app registration [(#11070)](https://github.com/prowler-cloud/prowler/issues/11070)
+- `kms_key_rotation_max_90_days` check for GCP provider, verifying KMS customer-managed keys are rotated every 90 days or less in line with the CIS Benchmark [(#11516)](https://github.com/prowler-cloud/prowler/pull/11516)
+- `exchange_mailbox_primary_smtp_uses_custom_domain` check for M365 provider [(#11215)](https://github.com/prowler-cloud/prowler/pull/11215)
+- `bedrock_agent_role_least_privilege` check for AWS provider, flagging Bedrock Agent execution roles with full-access managed policies, broad `Resource:*` inline statements, or missing permissions boundaries [(#11335)](https://github.com/prowler-cloud/prowler/pull/11335)
+- STACKIT ObjectStorage service with Object Lock, default retention policy, and access key expiration checks [(#11397)](https://github.com/prowler-cloud/prowler/pull/11397)
+
+### 🐞 Fixed
+
+- `load_and_validate_config_file` now unwraps namespaced config for every built-in and external provider, and no longer leaks the full file as the provider's config when the file is namespaced [(#10700)](https://github.com/prowler-cloud/prowler/pull/10700)
+- `entra_users_mfa_capable` no longer flags pre-provisioned users with future `employeeHireDate`; future-hire date comparisons now tolerate naive datetimes [(#11511)](https://github.com/prowler-cloud/prowler/pull/11511)
+- M365 Admin Center group enumeration now follows Microsoft Graph pagination so group-scoped checks include groups beyond the first page [(#11510)](https://github.com/prowler-cloud/prowler/pull/11510)
+- GCP `kms_key_rotation_enabled` check now only verifies that automatic key rotation is enabled (any interval) instead of enforcing a 90-day period, resolving the mismatch between the check and its documentation; the CIS, Prowler ThreatScore, and CCC requirements that mandate a 90-day maximum were remapped to the new `kms_key_rotation_max_90_days` check [(#11516)](https://github.com/prowler-cloud/prowler/pull/11516)
+- AWS CloudWatch log metric filter checks now validate `filterPattern` clauses regardless of order [(#11345)](https://github.com/prowler-cloud/prowler/pull/11345)
+- AWS `bedrock_api_key_no_long_term_credentials` now applies severity per finding (never-expires keys correctly flag as critical, no leak across findings) and aligns title and wording with AWS guidance to prefer short-term Bedrock API keys [(#11526)](https://github.com/prowler-cloud/prowler/pull/11526)
+
+### 🔐 Security
+
+- `dulwich` from 0.23.0 to 1.2.5 and `pyjwt` from 2.12.1 to 2.13.0, patching `GHSA-897w-fcg9-f6xj` (arbitrary file write) and `PYSEC-2026-179` (HMAC/JWK key confusion) [(#11499)](https://github.com/prowler-cloud/prowler/pull/11499)
+
+---
+
+## [5.29.3] (Prowler v5.29.3)
+
+### 🐞 Fixed
+
+- GCP `logging_sink_created` now recognizes organization-level aggregated sinks with `includeChildren=True`, avoiding false failures for covered projects [(#11355)](https://github.com/prowler-cloud/prowler/pull/11355)
+- GCP `logging_log_metric_filter_and_alert_*` checks now recognize organization-level aggregated sinks with `includeChildren=True`, no longer false-failing projects covered by a central bucket-scoped metric + alert [(#11488)](https://github.com/prowler-cloud/prowler/pull/11488)
+- Jira integration no longer fails with `400 INVALID_INPUT` when a finding has empty fields [(#11474)](https://github.com/prowler-cloud/prowler/pull/11474)
+- GCP `iam_service_account_unused` now passes disabled service accounts instead of failing them, since a disabled account cannot authenticate or be used [(#11467)](https://github.com/prowler-cloud/prowler/pull/11467)
+
+---
+
+## [5.29.1] (Prowler v5.29.1)
+
+### 🐞 Fixed
+
+- OCSF output writer now re-raises I/O errors (e.g. `ENOSPC`) instead of logging them per finding and leaving a truncated file [(#11421)](https://github.com/prowler-cloud/prowler/pull/11421)
+
+---
+
+## [5.29.0] (Prowler v5.29.0)
+
+### 🚀 Added
+
+- `application` service for Okta provider with `application_admin_console_session_idle_timeout_15min`, `application_admin_console_mfa_required`, `application_admin_console_phishing_resistant_authentication`, `application_dashboard_mfa_required`, `application_dashboard_phishing_resistant_authentication`, and `application_authentication_policy_network_zone_enforced` checks [(#11358)](https://github.com/prowler-cloud/prowler/pull/11358)
+- AWS AI Security Framework compliance for AWS provider [(#11353)](https://github.com/prowler-cloud/prowler/pull/11353)
+- `storage_account_public_network_access_disabled` check for Azure provider and remapped the Azure CIS "Public Network Access is Disabled" requirements to it [(#11334)](https://github.com/prowler-cloud/prowler/pull/11334)
+- StackIT provider with service account key authentication [(#9237)](https://github.com/prowler-cloud/prowler/pull/9237)
+- 8 Rules service checks for Google Workspace provider using the Cloud Identity Policy API [(#11379)](https://github.com/prowler-cloud/prowler/pull/11379)
+- 12 Security service checks for Google Workspace provider using the Cloud Identity Policy API [(#11356)](https://github.com/prowler-cloud/prowler/pull/11356)
+
+### ⚠️ Deprecated
+
+- `s3_bucket_default_encryption` check for AWS provider since SSE-S3 is automatically applied to all S3 buckets by AWS as of January 5, 2023 and can no longer be disabled [(#11230)](https://github.com/prowler-cloud/prowler/pull/11230)
+
+### 🐞 Fixed
+
+- Broken documentation URLs in Google Workspace check metadata [(#11405)](https://github.com/prowler-cloud/prowler/pull/11405)
+- ENS RD 311/2022 (AWS) compliance mapping: `vpc_different_regions` was uncorrectly mapped under the `mp.com.4` family (Network segregation). That check is now mapped to a new `op.cont.2.aws.vpc.1` requirement under the Continuity of Service control [(#11372)](https://github.com/prowler-cloud/prowler/pull/11372)
+- Compliance CSV row count now matches the UI per requirement by sourcing rows from the framework JSON's `requirement.Checks` instead of the stale `finding.compliance` snapshot [(#11370)](https://github.com/prowler-cloud/prowler/pull/11370)
+- OpenStack provider exception codes moved from the `10000-10999` range, shared with the AlibabaCloud provider, to the free `17000-17999` range to keep error codes unambiguous [(#11382)](https://github.com/prowler-cloud/prowler/pull/11382)
+- Azure provider authentication against sovereign clouds (`AzureChinaCloud`, `AzureUSGovernment`) [(#10284)](https://github.com/prowler-cloud/prowler/pull/10284)
+
+---
+
+## [5.28.1] (Prowler v5.28.1)
+
+### 🐞 Fixed
+
+- `compute_project_os_login_enabled` and `compute_project_os_login_2fa_enabled` checks for GCP provider no longer false-FAIL on projects where the `enable-oslogin` / `enable-oslogin-2fa` metadata is not set explicitly but is inherited automatically from the `constraints/compute.requireOsLogin` org policy. The policy controller writes the inherited value in lowercase (`"true"`), but the service-layer parser compared it to the uppercase string literal `"TRUE"`. Comparison is now case-insensitive [(#11341)](https://github.com/prowler-cloud/prowler/pull/11341)
+- `storage_smb_channel_encryption_with_secure_algorithm` check for Azure provider no longer passes when a storage account allows a weak SMB channel encryption algorithm (e.g. `AES-128-CCM`/`AES-128-GCM`) alongside `AES-256-GCM`; it now requires every enabled algorithm to be in the recommended list, configurable via `azure.recommended_smb_channel_encryption_algorithms` (defaults to `AES-256-GCM` only, as required by CIS) [(#11327)](https://github.com/prowler-cloud/prowler/pull/11327)
+- Azure and M365 providers crashing with `RuntimeError: There is no current event loop` on Python 3.12 when called from threads without an active event loop (e.g. Celery workers) [(#11360)](https://github.com/prowler-cloud/prowler/pull/11360)
+
+---
+
+## [5.28.0] (Prowler v5.28.0)
+
+### 🚀 Added
+
+- Sites, Additional Google services, and Marketplace checks for Google Workspace provider using the Cloud Identity Policy API [(#11281)](https://github.com/prowler-cloud/prowler/pull/11281)
+- `entra_app_registration_client_secret_unused` check for M365 provider [(#11232)](https://github.com/prowler-cloud/prowler/pull/11232)
+- `cloudsql_instance_cmek_encryption_enabled` check for GCP provider [(#11023)](https://github.com/prowler-cloud/prowler/pull/11023)
+- Google Workspace Groups service with 3 new checks [(#11186)](https://github.com/prowler-cloud/prowler/pull/11186)
+- `ses_identity_dkim_enabled` check for AWS provider [(#10923)](https://github.com/prowler-cloud/prowler/pull/10923)
+- `sagemaker_models_registry_in_use` check for AWS provider, verifying that at least one SageMaker Model Package Group has an approved model package to enforce ML governance workflows [(#11196)](https://github.com/prowler-cloud/prowler/pull/11196)
+- `signon_dod_warning_banner_configured`, `signon_global_session_lifetime_18h`, `signon_global_session_cookies_not_persistent` and `signon_global_session_policy_network_zone_enforced` checks for Okta provider [(#11224)](https://github.com/prowler-cloud/prowler/pull/11224)
+
+### 🔄 Changed
+
+- `OktaProvider.test_connection` accepts an optional `provider_id` (org domain) and raises `OktaInvalidProviderIdError` (14007) when it doesn't match the authenticated org — guards against stored UID drifting from the credentials' org [(#11184)](https://github.com/prowler-cloud/prowler/pull/11184)
+- Use single-quoted strings for credential variables in the M365 provider PowerShell session, following PowerShell best practices for literal values [(#9997)](https://github.com/prowler-cloud/prowler/pull/9997)
+
+### 🐞 Fixed
+
+- OCI Audit service configuration lookup when the configured region differs from the tenancy home region [(#10347)](https://github.com/prowler-cloud/prowler/pull/10347)
+- Container image now uses an absolute `ENTRYPOINT` (`/home/prowler/.venv/bin/prowler`) so it works under any runtime `--workdir`. The relative entrypoint was breaking the official GitHub Action (`prowler-cloud/prowler@v5.27.0`) and any `docker run` with a custom `-w` [(#11313)](https://github.com/prowler-cloud/prowler/pull/11313)
+
+---
+
+## [5.27.1] (Prowler v5.27.1)
### 🐞 Fixed
@@ -28,6 +355,7 @@ All notable changes to the **Prowler SDK** are documented in this file.
- `entra_service_principal_no_secrets_for_permanent_tier0_roles` check for M365 provider [(#10788)](https://github.com/prowler-cloud/prowler/pull/10788)
- `iam_user_access_not_stale_to_sagemaker` check for AWS provider with configurable `max_unused_sagemaker_access_days` (default 90) [(#11000)](https://github.com/prowler-cloud/prowler/pull/11000)
- `cloudtrail_bedrock_logging_enabled` check for AWS provider [(#10858)](https://github.com/prowler-cloud/prowler/pull/10858)
+- Per-provider scan configuration schema with bounds validation that drops out-of-range values with a warning on config load [(#11518)](https://github.com/prowler-cloud/prowler/pull/11518)
- Okta provider with OAuth 2.0 authentication and `signon_global_session_idle_timeout_15min` check [(#11079)](https://github.com/prowler-cloud/prowler/pull/11079)
- `sagemaker_domain_sso_configured` check for AWS provider [(#11094)](https://github.com/prowler-cloud/prowler/pull/11094)
- Scaleway provider with `iam_api_keys_no_root_owned` check [(#11166)](https://github.com/prowler-cloud/prowler/pull/11166)
@@ -71,7 +399,6 @@ All notable changes to the **Prowler SDK** are documented in this file.
- `bedrock_prompt_management_exists` check for AWS provider [(#10878)](https://github.com/prowler-cloud/prowler/pull/10878)
- 8 Gmail attachment safety and spoofing protection checks for Google Workspace provider using the Cloud Identity Policy API [(#10980)](https://github.com/prowler-cloud/prowler/pull/10980)
- `bedrock_prompt_encrypted_with_cmk` check for AWS provider [(#10905)](https://github.com/prowler-cloud/prowler/pull/10905)
-
### 🔄 Changed
- Azure Network Watcher flow log checks now require workspace-backed Traffic Analytics for `network_flow_log_captured_sent` and align metadata with VNet-compatible flow log guidance [(#10645)](https://github.com/prowler-cloud/prowler/pull/10645)
diff --git a/prowler/__main__.py b/prowler/__main__.py
index 3328905153..12f4b24cac 100644
--- a/prowler/__main__.py
+++ b/prowler/__main__.py
@@ -10,7 +10,6 @@ from colorama import Fore, Style
from colorama import init as colorama_init
from prowler.config.config import (
- EXTERNAL_TOOL_PROVIDERS,
cloud_api_base_url,
csv_file_suffix,
get_available_compliance_frameworks,
@@ -20,7 +19,7 @@ from prowler.config.config import (
orange_color,
sarif_file_suffix,
)
-from prowler.lib.banner import print_banner
+from prowler.lib.banner import print_banner, print_prowler_cloud_banner
from prowler.lib.check.check import (
exclude_checks_to_run,
exclude_services_to_run,
@@ -85,11 +84,6 @@ from prowler.lib.outputs.compliance.compliance import (
display_compliance_table,
process_universal_compliance_frameworks,
)
-from prowler.lib.outputs.compliance.csa.csa_alibabacloud import AlibabaCloudCSA
-from prowler.lib.outputs.compliance.csa.csa_aws import AWSCSA
-from prowler.lib.outputs.compliance.csa.csa_azure import AzureCSA
-from prowler.lib.outputs.compliance.csa.csa_gcp import GCPCSA
-from prowler.lib.outputs.compliance.csa.csa_oraclecloud import OracleCloudCSA
from prowler.lib.outputs.compliance.ens.ens_aws import AWSENS
from prowler.lib.outputs.compliance.ens.ens_azure import AzureENS
from prowler.lib.outputs.compliance.ens.ens_gcp import GCPENS
@@ -108,6 +102,9 @@ from prowler.lib.outputs.compliance.mitre_attack.mitre_attack_azure import (
AzureMitreAttack,
)
from prowler.lib.outputs.compliance.mitre_attack.mitre_attack_gcp import GCPMitreAttack
+from prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig_okta import (
+ OktaIDaaSSTIG,
+)
from prowler.lib.outputs.compliance.prowler_threatscore.prowler_threatscore_alibaba import (
ProwlerThreatScoreAlibaba,
)
@@ -143,6 +140,7 @@ from prowler.providers.azure.models import AzureOutputOptions
from prowler.providers.cloudflare.models import CloudflareOutputOptions
from prowler.providers.common.provider import Provider
from prowler.providers.common.quick_inventory import run_provider_quick_inventory
+from prowler.providers.e2enetworks.models import E2eNetworksOutputOptions
from prowler.providers.gcp.models import GCPOutputOptions
from prowler.providers.github.models import GithubOutputOptions
from prowler.providers.googleworkspace.models import GoogleWorkspaceOutputOptions
@@ -150,6 +148,7 @@ from prowler.providers.iac.models import IACOutputOptions
from prowler.providers.image.exceptions.exceptions import ImageBaseException
from prowler.providers.image.models import ImageOutputOptions
from prowler.providers.kubernetes.models import KubernetesOutputOptions
+from prowler.providers.linode.models import LinodeOutputOptions
from prowler.providers.llm.models import LLMOutputOptions
from prowler.providers.m365.models import M365OutputOptions
from prowler.providers.mongodbatlas.models import MongoDBAtlasOutputOptions
@@ -158,6 +157,7 @@ from prowler.providers.okta.models import OktaOutputOptions
from prowler.providers.openstack.models import OpenStackOutputOptions
from prowler.providers.oraclecloud.models import OCIOutputOptions
from prowler.providers.scaleway.models import ScalewayOutputOptions
+from prowler.providers.stackit.models import StackITOutputOptions
from prowler.providers.vercel.models import VercelOutputOptions
@@ -204,14 +204,15 @@ def prowler():
if not args.no_banner:
legend = args.verbose or getattr(args, "fixer", None)
- print_banner(legend)
+ print_banner(legend, provider)
# We treat the compliance framework as another output format
if compliance_framework:
args.output_formats.extend(compliance_framework)
- # If no input compliance framework, set all, unless a specific service or check is input
- # Skip for IAC and LLM providers that don't use compliance frameworks
- elif default_execution and provider not in ["iac", "llm"]:
+ # If no input compliance framework, set all, unless a specific service or check is input.
+ # Skip for tool-wrapper providers (iac, llm, image, and any external plug-in
+ # declaring `is_external_tool_provider = True`) — they don't use compliance frameworks.
+ elif default_execution and not Provider.is_tool_wrapper_provider(provider):
args.output_formats.extend(get_available_compliance_frameworks(provider))
# Set Logger configuration
@@ -249,7 +250,7 @@ def prowler():
universal_frameworks = {}
# Skip compliance frameworks for external-tool providers
- if provider not in EXTERNAL_TOOL_PROVIDERS:
+ if not Provider.is_tool_wrapper_provider(provider):
bulk_compliance_frameworks = Compliance.get_bulk(provider)
# Complete checks metadata with the compliance framework specification
bulk_checks_metadata = update_checks_metadata_with_compliance(
@@ -317,7 +318,7 @@ def prowler():
sys.exit()
# Skip service and check loading for external-tool providers
- if provider not in EXTERNAL_TOOL_PROVIDERS:
+ if not Provider.is_tool_wrapper_provider(provider):
# Import custom checks from folder
if checks_folder:
custom_checks = parse_checks_from_folder(global_provider, checks_folder)
@@ -416,6 +417,10 @@ def prowler():
output_options = OCIOutputOptions(
args, bulk_checks_metadata, global_provider.identity
)
+ elif provider == "stackit":
+ output_options = StackITOutputOptions(
+ args, bulk_checks_metadata, global_provider.identity
+ )
elif provider == "alibabacloud":
output_options = AlibabaCloudOutputOptions(
args, bulk_checks_metadata, global_provider.identity
@@ -428,6 +433,10 @@ def prowler():
output_options = VercelOutputOptions(
args, bulk_checks_metadata, global_provider.identity
)
+ elif provider == "e2enetworks":
+ output_options = E2eNetworksOutputOptions(
+ args, bulk_checks_metadata, global_provider.identity
+ )
elif provider == "okta":
output_options = OktaOutputOptions(
args, bulk_checks_metadata, global_provider.identity
@@ -436,6 +445,24 @@ def prowler():
output_options = ScalewayOutputOptions(
args, bulk_checks_metadata, global_provider.identity
)
+ elif provider == "linode":
+ output_options = LinodeOutputOptions(
+ args, bulk_checks_metadata, global_provider.identity
+ )
+ else:
+ # Dynamic fallback: any external/custom provider
+ try:
+ output_options = global_provider.get_output_options(
+ args, bulk_checks_metadata
+ )
+ except NotImplementedError:
+ # No provider-specific OutputOptions: use the generic default so the
+ # run still produces output instead of aborting.
+ from prowler.providers.common.models import default_output_options
+
+ output_options = default_output_options(
+ global_provider, args, bulk_checks_metadata
+ )
# Run the quick inventory for the provider if available
if hasattr(args, "quick_inventory") and args.quick_inventory:
@@ -445,7 +472,7 @@ def prowler():
# Execute checks
findings = []
- if provider in EXTERNAL_TOOL_PROVIDERS:
+ if Provider.is_tool_wrapper_provider(provider):
# For external-tool providers, run the scan directly
if provider == "llm":
@@ -455,12 +482,19 @@ def prowler():
findings = global_provider.run_scan(streaming_callback=streaming_callback)
else:
- # Original behavior for IAC and Image
- try:
+ if provider == "image":
+ try:
+ findings = global_provider.run()
+ except ImageBaseException as error:
+ logger.critical(f"{error}")
+ sys.exit(1)
+ else:
+ # IAC and external tool-wrapper providers registered via entry
+ # points. Unexpected failures propagate to the outer except
+ # Exception backstop further down in this file — keeping the
+ # branch free of an Image-specific catch that would otherwise
+ # mislead plug-in authors reading this code.
findings = global_provider.run()
- except ImageBaseException as error:
- logger.critical(f"{error}")
- sys.exit(1)
# Note: External tool providers don't support granular progress tracking since
# they run external tools as a black box and return all findings at once.
# Progress tracking would just be 0% → 100%.
@@ -801,18 +835,6 @@ def prowler():
)
generated_outputs["compliance"].append(c5)
c5.batch_write_data_to_file()
- elif compliance_name == "csa_ccm_4.0_aws":
- filename = (
- f"{output_options.output_directory}/compliance/"
- f"{output_options.output_filename}_{compliance_name}.csv"
- )
- csa_ccm_4_0_aws = AWSCSA(
- findings=finding_outputs,
- compliance=bulk_compliance_frameworks[compliance_name],
- file_path=filename,
- )
- generated_outputs["compliance"].append(csa_ccm_4_0_aws)
- csa_ccm_4_0_aws.batch_write_data_to_file()
else:
filename = (
f"{output_options.output_directory}/compliance/"
@@ -916,18 +938,6 @@ def prowler():
)
generated_outputs["compliance"].append(c5_azure)
c5_azure.batch_write_data_to_file()
- elif compliance_name == "csa_ccm_4.0_azure":
- filename = (
- f"{output_options.output_directory}/compliance/"
- f"{output_options.output_filename}_{compliance_name}.csv"
- )
- csa_ccm_4_0_azure = AzureCSA(
- findings=finding_outputs,
- compliance=bulk_compliance_frameworks[compliance_name],
- file_path=filename,
- )
- generated_outputs["compliance"].append(csa_ccm_4_0_azure)
- csa_ccm_4_0_azure.batch_write_data_to_file()
else:
filename = (
f"{output_options.output_directory}/compliance/"
@@ -1031,18 +1041,6 @@ def prowler():
)
generated_outputs["compliance"].append(c5_gcp)
c5_gcp.batch_write_data_to_file()
- elif compliance_name == "csa_ccm_4.0_gcp":
- filename = (
- f"{output_options.output_directory}/compliance/"
- f"{output_options.output_filename}_{compliance_name}.csv"
- )
- csa_ccm_4_0_gcp = GCPCSA(
- findings=finding_outputs,
- compliance=bulk_compliance_frameworks[compliance_name],
- file_path=filename,
- )
- generated_outputs["compliance"].append(csa_ccm_4_0_gcp)
- csa_ccm_4_0_gcp.batch_write_data_to_file()
else:
filename = (
f"{output_options.output_directory}/compliance/"
@@ -1277,18 +1275,6 @@ def prowler():
)
generated_outputs["compliance"].append(cis)
cis.batch_write_data_to_file()
- elif compliance_name == "csa_ccm_4.0_oraclecloud":
- filename = (
- f"{output_options.output_directory}/compliance/"
- f"{output_options.output_filename}_{compliance_name}.csv"
- )
- csa_ccm_4_0_oraclecloud = OracleCloudCSA(
- findings=finding_outputs,
- compliance=bulk_compliance_frameworks[compliance_name],
- file_path=filename,
- )
- generated_outputs["compliance"].append(csa_ccm_4_0_oraclecloud)
- csa_ccm_4_0_oraclecloud.batch_write_data_to_file()
else:
filename = (
f"{output_options.output_directory}/compliance/"
@@ -1317,18 +1303,6 @@ def prowler():
)
generated_outputs["compliance"].append(cis)
cis.batch_write_data_to_file()
- elif compliance_name == "csa_ccm_4.0_alibabacloud":
- filename = (
- f"{output_options.output_directory}/compliance/"
- f"{output_options.output_filename}_{compliance_name}.csv"
- )
- csa_ccm_4_0_alibabacloud = AlibabaCloudCSA(
- findings=finding_outputs,
- compliance=bulk_compliance_frameworks[compliance_name],
- file_path=filename,
- )
- generated_outputs["compliance"].append(csa_ccm_4_0_alibabacloud)
- csa_ccm_4_0_alibabacloud.batch_write_data_to_file()
elif compliance_name == "prowler_threatscore_alibabacloud":
filename = (
f"{output_options.output_directory}/compliance/"
@@ -1353,6 +1327,57 @@ def prowler():
)
generated_outputs["compliance"].append(generic_compliance)
generic_compliance.batch_write_data_to_file()
+ elif provider == "okta":
+ for compliance_name in input_compliance_frameworks:
+ if compliance_name.startswith("okta_idaas_stig"):
+ # Generate Okta IDaaS STIG Finding Object
+ filename = (
+ f"{output_options.output_directory}/compliance/"
+ f"{output_options.output_filename}_{compliance_name}.csv"
+ )
+ okta_idaas_stig = OktaIDaaSSTIG(
+ findings=finding_outputs,
+ compliance=bulk_compliance_frameworks[compliance_name],
+ file_path=filename,
+ )
+ generated_outputs["compliance"].append(okta_idaas_stig)
+ okta_idaas_stig.batch_write_data_to_file()
+ else:
+ filename = (
+ f"{output_options.output_directory}/compliance/"
+ f"{output_options.output_filename}_{compliance_name}.csv"
+ )
+ generic_compliance = GenericCompliance(
+ findings=finding_outputs,
+ compliance=bulk_compliance_frameworks[compliance_name],
+ file_path=filename,
+ )
+ generated_outputs["compliance"].append(generic_compliance)
+ generic_compliance.batch_write_data_to_file()
+ else:
+ # Dynamic fallback: any external/custom provider
+ try:
+ global_provider.generate_compliance_output(
+ finding_outputs,
+ bulk_compliance_frameworks,
+ input_compliance_frameworks,
+ output_options,
+ generated_outputs,
+ )
+ except NotImplementedError:
+ # Last resort: generic compliance
+ for compliance_name in input_compliance_frameworks:
+ filename = (
+ f"{output_options.output_directory}/compliance/"
+ f"{output_options.output_filename}_{compliance_name}.csv"
+ )
+ generic_compliance = GenericCompliance(
+ findings=finding_outputs,
+ compliance=bulk_compliance_frameworks[compliance_name],
+ file_path=filename,
+ )
+ generated_outputs["compliance"].append(generic_compliance)
+ generic_compliance.batch_write_data_to_file()
# AWS Security Hub Integration
if provider == "aws":
@@ -1461,6 +1486,10 @@ def prowler():
f"\nDetailed compliance results are in {Fore.YELLOW}{output_options.output_directory}/compliance/{Style.RESET_ALL}\n"
)
+ # Promote Prowler Cloud as the last thing the user sees after the results
+ if not args.no_banner and not args.only_logs:
+ print_prowler_cloud_banner(provider)
+
# If custom checks were passed, remove the modules
if checks_folder:
remove_custom_checks_module(checks_folder, provider)
diff --git a/tests/config/__init__.py b/prowler/changelog.d/.gitkeep
similarity index 100%
rename from tests/config/__init__.py
rename to prowler/changelog.d/.gitkeep
diff --git a/prowler/changelog.d/README.md b/prowler/changelog.d/README.md
new file mode 100644
index 0000000000..0853174f30
--- /dev/null
+++ b/prowler/changelog.d/README.md
@@ -0,0 +1,10 @@
+# Changelog fragments
+
+Each PR adds one small file here instead of editing `CHANGELOG.md` directly, so concurrent PRs never conflict.
+
+- Filename: `<slug>.<type>.md`, e.g. `my-new-check.added.md` (slug is free-form: letters, digits, `.`, `_`, `-`)
+- `<type>` is one of: `added`, `changed`, `deprecated`, `removed`, `fixed`, `security`
+- Content: one line with the changelog entry text, without the PR link and without a trailing period (the PR link is attached automatically at release time)
+- A PR adds as many fragment files as entries it needs, freely mixing types (one file per entry); same-type entries just use different slugs
+
+Fragments are compiled into `CHANGELOG.md` when a release is prepared. Full conventions: `skills/prowler-changelog/SKILL.md`.
diff --git a/prowler/changelog.d/alibabacloud-security-group-policy-case.fixed.md b/prowler/changelog.d/alibabacloud-security-group-policy-case.fixed.md
new file mode 100644
index 0000000000..cef4ff076c
--- /dev/null
+++ b/prowler/changelog.d/alibabacloud-security-group-policy-case.fixed.md
@@ -0,0 +1 @@
+Alibaba Cloud SSH and RDP security group checks no longer produce false negatives when allowed rules use capitalized `Policy="Accept"` values
diff --git a/prowler/changelog.d/bucket-validation-syntaxwarning.fixed.md b/prowler/changelog.d/bucket-validation-syntaxwarning.fixed.md
new file mode 100644
index 0000000000..ceba09541c
--- /dev/null
+++ b/prowler/changelog.d/bucket-validation-syntaxwarning.fixed.md
@@ -0,0 +1 @@
+Fix invalid escape sequence `SyntaxWarning` raised on startup by the S3 bucket name validation regex
diff --git a/prowler/changelog.d/grouped-jira-dispatch.changed.md b/prowler/changelog.d/grouped-jira-dispatch.changed.md
new file mode 100644
index 0000000000..8dd2e43ab5
--- /dev/null
+++ b/prowler/changelog.d/grouped-jira-dispatch.changed.md
@@ -0,0 +1 @@
+Jira output rendering supports grouped Finding Group issues with caller-provided links and capped or uncapped finding copy
diff --git a/prowler/changelog.d/sagemaker-notebook-no-secrets.added.md b/prowler/changelog.d/sagemaker-notebook-no-secrets.added.md
new file mode 100644
index 0000000000..4789aa6aaf
--- /dev/null
+++ b/prowler/changelog.d/sagemaker-notebook-no-secrets.added.md
@@ -0,0 +1 @@
+`sagemaker_notebook_instance_no_secrets` check for AWS provider, scanning SageMaker notebook instance lifecycle configuration scripts (`OnCreate` and `OnStart`) for hardcoded secrets such as API keys, passwords, tokens, and connection strings
diff --git a/prowler/compliance/alibabacloud/cis_2.0_alibabacloud.json b/prowler/compliance/alibabacloud/cis_2.0_alibabacloud.json
index 7cda08efbb..9a05c1997f 100644
--- a/prowler/compliance/alibabacloud/cis_2.0_alibabacloud.json
+++ b/prowler/compliance/alibabacloud/cis_2.0_alibabacloud.json
@@ -109,6 +109,14 @@
],
"Checks": [
"ram_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "ram_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -841,6 +849,14 @@
],
"Checks": [
"sls_logstore_retention_period"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sls_logstore_retention_period",
+ "ConfigKey": "min_log_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
]
},
{
@@ -1353,6 +1369,14 @@
],
"Checks": [
"rds_instance_sql_audit_retention"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "rds_instance_sql_audit_retention",
+ "ConfigKey": "min_rds_audit_retention_days",
+ "Operator": "gte",
+ "Value": 180
+ }
]
},
{
@@ -1551,6 +1575,14 @@
],
"Checks": [
"cs_kubernetes_cluster_check_recent"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "cs_kubernetes_cluster_check_recent",
+ "ConfigKey": "max_cluster_check_days",
+ "Operator": "lte",
+ "Value": 7
+ }
]
},
{
diff --git a/prowler/compliance/alibabacloud/csa_ccm_4.0_alibabacloud.json b/prowler/compliance/alibabacloud/csa_ccm_4.0_alibabacloud.json
deleted file mode 100644
index 060b6e819e..0000000000
--- a/prowler/compliance/alibabacloud/csa_ccm_4.0_alibabacloud.json
+++ /dev/null
@@ -1,7305 +0,0 @@
-{
- "Framework": "CSA-CCM",
- "Name": "CSA Cloud Controls Matrix (CCM) v4.0.13",
- "Version": "4.0",
- "Provider": "alibabacloud",
- "Description": "The Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing, composed of 197 control objectives structured in 17 domains covering all key aspects of cloud technology. The CCM can be used as a tool for the systematic assessment of a cloud implementation, and provides guidance on which security controls should be implemented by which actor within the cloud supply chain.",
- "Requirements": [
- {
- "Id": "A&A-02",
- "Description": "Conduct independent audit and assurance assessments according to relevant standards at least annually.",
- "Name": "Independent Assessments",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC4.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AAC-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.2",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.2.1",
- "27002: 18.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.35",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-2",
- "CA-2(1)",
- "CA-2(2)",
- "CA-7",
- "CA-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition"
- ]
- },
- {
- "Id": "A&A-04",
- "Description": "Verify compliance with all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit.",
- "Name": "Requirements Compliance",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01",
- "GRM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.18.2.2",
- "27002: 18.2.2",
- "27001: A.18.2.3",
- "27002: 18.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-3",
- "DE.DP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition"
- ]
- },
- {
- "Id": "AIS-04",
- "Description": "Define and implement a SDLC process for application design, development, deployment, and operation in accordance with security requirements defined by the organization.",
- "Name": "Secure Application Design and Development",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27017: 14.1.1",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.14.2.1",
- "27002: 14.2.1",
- "27017: 14.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.8",
- "27001: A.8.25",
- "27001: A.8.26",
- "27001: A.8.28"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PL-8",
- "PL-8(1)",
- "SA-3",
- "SA-3(1)",
- "SA-4",
- "SA-4(2)",
- "SA-4(3)",
- "SA-4(8)",
- "SA-4(9)",
- "SA-5",
- "SA-8",
- "SA-8(1)-(7)",
- "SA-8(9)-(13)",
- "SA-8(15)-(20)",
- "SA-8(22)",
- "SA-8(24)-(28)",
- "SA-8(30)-(33)",
- "SA-17",
- "SA-17(1)-(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-6",
- "PR.DS-7",
- "PR.IP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1",
- "6.2.3",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "AIS-05",
- "Description": "Implement a testing strategy, including criteria for acceptance of new information systems, upgrades and new versions, which provides application security assurance and maintains compliance while enabling organizational speed of delivery goals. Automate when applicable and possible.",
- "Name": "Automated Application Security Testing",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.12",
- "16.13"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.3",
- "SD2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.8",
- "27001: A.14.2.9",
- "27001: A.12.1.2",
- "27002: 12.1.2",
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27001: A.14.2.2",
- "27002: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.25",
- "27001: A.8.29",
- "27001: A.8.32",
- "27002: 8.25 (e)",
- "27002: 8.32 (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SA-11",
- "SA-11(1)-(9)",
- "SI-6",
- "SI-6(2)",
- "SI-6(3)",
- "SI-10",
- "SI-10(1)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.IP-12",
- "DE.CM-8"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "PR.PS-01",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A.3.2.2",
- "A.3.2.2.1",
- "6.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.4",
- "6.4.1",
- "6.4.2",
- "6.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_vulnerability_scan_enabled"
- ]
- },
- {
- "Id": "AIS-07",
- "Description": "Define and implement a process to remediate application security vulnerabilities, automating remediation when possible.",
- "Name": "Application Vulnerability Remediation",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1",
- "CC7.4",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.2",
- "16.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27001: A.12.6.1",
- "27002: 12.6.1",
- "27017: 12.6.1",
- "27018: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.26",
- "27001: A.8.8",
- "27002: 5.26 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-2",
- "SI-2(2)-(6)",
- "SA-11",
- "SA-11(2)",
- "SA-15",
- "SA-15(1)-(3)",
- "SA-15(5)-(8)",
- "SA-15(10)-(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.IP-12",
- "DE.CM-8",
- "RS.AN-5",
- "RS.MI-3",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.2",
- "6.5",
- "6.5.1-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "11.3.1",
- "11.3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_vulnerability_scan_enabled"
- ]
- },
- {
- "Id": "BCR-08",
- "Description": "Periodically backup data stored in the cloud. Ensure the confidentiality, integrity and availability of the backup, and verify data restoration from backup for resiliency.",
- "Name": "Backup",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "A1.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "11.1",
- "11.2",
- "11.3",
- "11.4",
- "11.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27017: 12.3",
- "27018: 12.3.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.13",
- "27001: A.5.23",
- "27001: A.5.30",
- "27002: 8.13",
- "27002: 5.23 2nd (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-4",
- "CP-4(4)",
- "CP-6",
- "CP-6(1)-(3)",
- "CP-9",
- "CP-9(1)",
- "CP-9(2)",
- "CP-10",
- "CP-10(2)",
- "CP-10(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-4",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-11",
- "RC.RP-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.5.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "10.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "BCR-09",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain a disaster response plan to recover from natural and man-made disasters. Update the plan at least annually or upon significant changes.",
- "Name": "Disaster Response Plan",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9",
- "1.6.1",
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.4",
- "BC2.1",
- "BC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.29",
- "27001: A.5.30",
- "27002: 5.29",
- "27002: 5.30"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2(1)",
- "CP-2(2)",
- "CP-2(3)",
- "CP-2(5)",
- "CP-2(6)",
- "CP-2(7)",
- "CP-2(8)",
- "PE-13",
- "PE-13(1)",
- "PE-13(2)",
- "PE-13(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-9",
- "PR.IP-10",
- "RC.IM-1",
- "RC.IM-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-04"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "BCR-11",
- "Description": "Supplement business-critical equipment with redundant equipment independently located at a reasonable minimum distance in accordance with applicable industry standards.",
- "Name": "Equipment Redundancy",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-06"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.20",
- "27001: A.7.11",
- "27001: A.8.14",
- "27002: 5.20 (t)",
- "27002: 8.14 (c)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "CP-4(3)",
- "CP-6",
- "CP-6(1)",
- "CP-7",
- "CP-8",
- "CP-8(1)-(3)",
- "CP-9",
- "CP-9(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.BE-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.OC-04",
- "GV.OC-05",
- "PR.IR-03"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "CCC-04",
- "Description": "Restrict the unauthorized addition, removal, update, and management of organization assets.",
- "Name": "Unauthorized Change Protection",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "CCC-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.1",
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4",
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.1.4",
- "27002: 12.1.4",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27001: A.14.2.2",
- "27017: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.3",
- "27001: A.8.4",
- "27001: A.8.15",
- "27001: A.8.31",
- "27001: A.8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(4)",
- "CM-3",
- "CM-3(1)",
- "CM-3(5)",
- "CM-3(7)",
- "CM-3(8)",
- "CM-5",
- "CM-5(1)",
- "CM-5(4)",
- "CM-5(5)",
- "CM-6",
- "CM-6(1)",
- "CM-6(2)",
- "CM-7",
- "CM-7(1)",
- "CM-7(4)",
- "CM-7(5)",
- "CM-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.MA-1",
- "PR.MA-2",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04",
- "ID.AM-08",
- "PR.PS-02",
- "PR.PS-03",
- "PR.PS-05",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.1",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_multi_region_enabled"
- ]
- },
- {
- "Id": "CCC-07",
- "Description": "Implement detection measures with proactive notification in case of changes deviating from the established baseline.",
- "Name": "Detection of Baseline Deviation",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.1",
- "1.5.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.2",
- "27001: A.14.2.4",
- "27001: A.12.4.1",
- "27002: 12.4.1 (g)",
- "27001: A.5.1.1",
- "27017: 5.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.9",
- "27001: A.8.15",
- "27002: 8.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(2)",
- "SI-2",
- "SI-2(2)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.MA-1",
- "PR.IP-1",
- "DE.DP-4",
- "PR.IP-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01",
- "DE.CM-09",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.3",
- "6.4.5.4",
- "11.5",
- "11.5.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "11.5.2",
- "11.6.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition",
- "sls_security_group_changes_alert_enabled",
- "sls_vpc_changes_alert_enabled",
- "sls_vpc_network_route_changes_alert_enabled",
- "sls_customer_created_cmk_changes_alert_enabled",
- "sls_cloud_firewall_changes_alert_enabled",
- "sls_management_console_authentication_failures_alert_enabled",
- "sls_rds_instance_configuration_changes_alert_enabled"
- ]
- },
- {
- "Id": "CEK-03",
- "Description": "Provide cryptographic protection to data at-rest and in-transit, using cryptographic libraries certified to approved standards.",
- "Name": "Data Encryption",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-03",
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6",
- "3.1",
- "3.11",
- "11.3",
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.1",
- "27001: A.18.1.2",
- "27001: A.18.1.3",
- "27001: A.18.1.4",
- "27001: A.18.1.5",
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.18",
- "27002: 18",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27001: A.14.1.3",
- "27002 14.1.3 c)",
- "27001 - A.10.1.1",
- "27017 - 10.1.1",
- "27001 - A.10.1.2",
- "27017 - 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.24",
- "27002: 8.24 Other Information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19",
- "AC-19(5)",
- "SC-8",
- "SC-8(1)",
- "SC-8(3)",
- "SC-8(4)",
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)-(3)",
- "SI-4",
- "SI-4(10)",
- "SI-7",
- "SI-7(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "Requirement 3",
- "2.2.3",
- "2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ecs_attached_disk_encrypted",
- "ecs_unattached_disk_encrypted",
- "rds_instance_tde_enabled",
- "rds_instance_ssl_enabled",
- "oss_bucket_secure_transport_enabled"
- ]
- },
- {
- "Id": "CEK-04",
- "Description": "Use encryption algorithms that are appropriate for data protection, considering the classification of data, associated risks, and usability of the encryption technology.",
- "Name": "Encryption Algorithm",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.2",
- "27002: 8.2",
- "27001: A.8.3",
- "27001: A.10.1.1",
- "27002: 10.1.1 (b)",
- "27001: A.10.1.2",
- "27002: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.24",
- "27001: A.5.12",
- "27001: A.5.13",
- "27002: 8.24 General (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A2",
- "Requirement 3",
- "2.3",
- "2.2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "CEK-08",
- "Description": "CSPs must provide the capability for CSCs to manage their own data encryption keys.",
- "Name": "CSC Key Management Capability",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27017: 10.1",
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.23",
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-9",
- "CP-9(8)",
- "SA-9",
- "SA-9(6)",
- "SC-12",
- "SC-12(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.AM-6",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-05"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "rds_instance_tde_key_custom"
- ]
- },
- {
- "Id": "CEK-10",
- "Description": "Generate Cryptographic keys using industry accepted cryptographic libraries specifying the algorithm strength and the random number generator used.",
- "Name": "Key Generation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "TS2.3",
- "SY1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27002: 10.1.1 (e)",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2",
- "27002: 10.1.2 (a)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24",
- "27002: 8.24 (d), Key management (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2.3",
- "3.6.1",
- "PCI Glossary - Cryptographic Key Generation"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.6.1.1",
- "3.7.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "rds_instance_tde_key_custom"
- ]
- },
- {
- "Id": "CEK-12",
- "Description": "Rotate cryptographic keys in accordance with the calculated cryptoperiod, which includes provisions for considering the risk of information disclosure and legal and regulatory requirements.",
- "Name": "Key Rotation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2 e)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (e,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_rotate_access_key_90_days"
- ]
- },
- {
- "Id": "CEK-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.",
- "Name": "Key Destruction",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27017: 10.1.2",
- "27001: A.10.1.2",
- "27002: 10.1.2 (j)",
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (j,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.IP-6",
- "ID.GV-3",
- "PR.DS-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "ID.AM-08",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.6.4",
- "3.6.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DCS-06",
- "Description": "Catalogue and track all relevant physical and logical assets located at all of the CSP's sites within a secured system.",
- "Name": "Assets Cataloguing and Tracking",
- "Attributes": [
- {
- "Section": "Datacenter Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DCS - 01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "1.1",
- "2.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27017: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-8",
- "CM-8(1)",
- "CM-8(2)",
- "CM-8(4)",
- "CM-8(7)",
- "CM-8(8)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4",
- "9.7.1",
- "9.9.1",
- "9.9.1.a",
- "9.9.1.b",
- "9.9.1.c",
- "12.3.3",
- "12.3.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1.1",
- "6.3.2",
- "9.4.2",
- "9.4.3",
- "12.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_all_assets_agent_installed"
- ]
- },
- {
- "Id": "DSP-02",
- "Description": "Apply industry accepted methods for the secure disposal of data from storage media such that data is not recoverable by any forensic means.",
- "Name": "Secure Disposal",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3",
- "CC6.4",
- "CC6.5",
- "CC6.7",
- "P4.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-07"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.3",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.3.2",
- "27002: 8.3.2",
- "27001: A.11.2.7",
- "27002: 11.2.7"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.7.10",
- "27001: A.7.14",
- "27001: A.8.10",
- "27002: 7.10 (Secure reuse or disposal)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-22",
- "SI-12",
- "SI-12(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-10",
- "PR.PS-02",
- "PR.PS-03",
- "ID.AM-08"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1",
- "9.8",
- "9.8.1",
- "9.8.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "3.7.5",
- "9.4.7"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-03",
- "Description": "Create and maintain a data inventory, at least for any sensitive data and personal data.",
- "Name": "Data Inventory",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2",
- "1.3.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-12",
- "CM-12(1)",
- "PM-5",
- "PM-5(1)",
- "SI-12",
- "SI-12(1)",
- "SI-19",
- "SI-19(1)",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "9.4.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_all_assets_agent_installed"
- ]
- },
- {
- "Id": "DSP-04",
- "Description": "Classify data according to its type and sensitivity level.",
- "Name": "Data Classification",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "C1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.2.1",
- "27002: 8.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-16",
- "AC-16(9)",
- "PM-22",
- "PM-23",
- "PT-2",
- "PT-2(1)",
- "SI-18",
- "SI-18(2)",
- "SI-19",
- "SI-19(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-05",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "9.4.2",
- "9.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-07",
- "Description": "Develop systems, products, and business practices based upon a principle of security by design and industry best practices.",
- "Name": "Data Protection by Design and Default",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "PI1.2",
- "PI1.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.1",
- "5.3.2",
- "5.3.3",
- "5.3.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.2",
- "IM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002:14.1.1",
- "27001: A.14.2.5",
- "27002:14.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.27",
- "27001: A.8.28",
- "27001: A.8.29",
- "27002: 5.8 (Information security requirements a-i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-17",
- "PM-24",
- "PM-25",
- "PT-2",
- "PT-2(2)",
- "SA-3",
- "SA-4",
- "SA-5",
- "SA-8",
- "SA-8(9)",
- "SA-8(13)",
- "SA-8(18)",
- "SA-8(20)",
- "SA-8(22)",
- "SA-8(23)",
- "SA-8(33)",
- "SA-15",
- "SA-15(12)",
- "SC-3",
- "SC-3(3)",
- "SC-7",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(4)",
- "SC-28",
- "SC-28(1)",
- "SI-12",
- "SI-12(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "oss_bucket_not_publicly_accessible",
- "rds_instance_no_public_access_whitelist"
- ]
- },
- {
- "Id": "DSP-10",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope as permitted by the respective laws and regulations.",
- "Name": "Sensitive Data Transfer",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.12",
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "9.5.1",
- "9.5.2",
- "9.5.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.8.3.3",
- "27002: 8.3.3",
- "27001: A.13.2.3",
- "27002: 13.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.7.10"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-4",
- "AC-4(23)-(25)",
- "CA-3",
- "CA-3(6)",
- "CA-6",
- "CA-6(1)",
- "CA-6(2)",
- "SC-4",
- "SC-4(2)",
- "SC-7",
- "SC-7(10)",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-16",
- "SC-16(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.DS-5",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.IR-01",
- "ID.AM-03",
- "GV.OC-03",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "4.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.1.1",
- "4.2.1",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "oss_bucket_secure_transport_enabled",
- "rds_instance_ssl_enabled"
- ]
- },
- {
- "Id": "DSP-16",
- "Description": "Data retention, archiving and deletion is managed in accordance with business requirements, applicable laws and regulations.",
- "Name": "Data Retention and Deletion",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "C1.1",
- "C1.2",
- "CC3.1",
- "P4.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.4",
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.10",
- "27002: 5.33 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-12",
- "SI-12(1)-(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)",
- "SI-19",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-3",
- "PR.IP-6",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "GV.OC-03",
- "GV.SC-10",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "sls_logstore_retention_period",
- "rds_instance_sql_audit_retention"
- ]
- },
- {
- "Id": "DSP-17",
- "Description": "Define and implement, processes, procedures and technical measures to protect sensitive data throughout it's lifecycle.",
- "Name": "Sensitive Data Protection",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSC-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.1",
- "CC6.1",
- "CC6.3",
- "CC6.7",
- "CC8.1",
- "C1.1",
- "P2.0",
- "P3.0",
- "P4.0",
- "P5.0",
- "P6.0"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.1",
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.3",
- "9.1.1",
- "9.2.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001:A.18.1.4",
- "27002:18.1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.11",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PM-22",
- "PM-24",
- "PT-7",
- "PT-7(1)",
- "PT-7(2)",
- "PT-8",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.0 (including all subsections)",
- "4.0 (including all subsections)"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.1.1",
- "4.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "oss_bucket_not_publicly_accessible",
- "rds_instance_no_public_access_whitelist",
- "ecs_attached_disk_encrypted",
- "ecs_unattached_disk_encrypted",
- "rds_instance_tde_enabled"
- ]
- },
- {
- "Id": "GRC-05",
- "Description": "Develop and implement an Information Security Program, which includes programs for all the relevant domains of the CCM.",
- "Name": "Information Security Program",
- "Attributes": [
- {
- "Section": "Governance, Risk and Compliance",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "14.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SG2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-1",
- "PM-3",
- "PM-14",
- "PL-2",
- "PM-18",
- "PM-31"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.4.1",
- "A.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.4.1",
- "A3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition"
- ]
- },
- {
- "Id": "IAM-02",
- "Description": "Establish, document, approve, communicate, implement, apply, evaluate and maintain strong password policies and procedures. Review and update the policies and procedures at least annually.",
- "Name": "Strong Password Policy and Procedures",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-12",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "4.1.2",
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1",
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.7.2.2",
- "27002: 7.2.2",
- "27001: A.9.2.6",
- "27002: 9.2.6",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.17",
- "27001: A.6.3",
- "27001: A.8.5",
- "27001: A.5.37"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-3",
- "AC-3(3)",
- "AC-12",
- "AC-12(1)",
- "IA-2",
- "IA-2(10)",
- "IA-5",
- "IA-5(1)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.AC-1",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.4",
- "12.1",
- "12.1.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.1.1",
- "8.3.8"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_password_policy_minimum_length",
- "ram_password_policy_lowercase",
- "ram_password_policy_uppercase",
- "ram_password_policy_number",
- "ram_password_policy_symbol",
- "ram_password_policy_password_reuse_prevention",
- "ram_password_policy_max_password_age",
- "ram_password_policy_max_login_attempts"
- ]
- },
- {
- "Id": "IAM-03",
- "Description": "Manage, store, and review the information of system identities, and level of access.",
- "Name": "Identity Inventory",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-04",
- "IAM-08",
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27001: A.9.4.1",
- "27002: 9.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.5.15",
- "27001: A.5.16",
- "27001: A.5.18",
- "27001: A.7.4",
- "27001: A.8.15",
- "27001: A.8.2",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "AU-16",
- "AU-16(1)",
- "IA-4",
- "IA-4(8)",
- "IA-4(9)",
- "IA-5",
- "IA-5(5)",
- "IA-8",
- "IA-8(4)",
- "PM-5(1)",
- "SA-8",
- "SA-8(22)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-04",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4.a"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_user_console_access_unused"
- ]
- },
- {
- "Id": "IAM-04",
- "Description": "Employ the separation of duties principle when implementing information system access.",
- "Name": "Separation of Duties",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC1.3",
- "CC5.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.2",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.6.1.2",
- "27002: 6.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18",
- "27001: A.5.3",
- "27001: A.8.2"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-6",
- "AC-6(1)-(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4",
- "6.4.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_policy_attached_only_to_group_or_roles"
- ]
- },
- {
- "Id": "IAM-05",
- "Description": "Employ the least privilege principle when implementing information system access.",
- "Name": "Least Privilege",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-06",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.1",
- "27002: 9.1.1",
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.8.2",
- "27002: 5.15 (Other information 2nd (a))"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "IA-12",
- "IA-12(2)",
- "IA-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1",
- "7.1.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2",
- "7.2.5",
- "7.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_policy_no_administrative_privileges"
- ]
- },
- {
- "Id": "IAM-07",
- "Description": "De-provision or respectively modify access of movers / leavers or system identity changes in a timely manner in order to effectively adopt and communicate identity and access management policies.",
- "Name": "User Access Changes and Revocation",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.3",
- "6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(1)",
- "AC-2(2)",
- "AC-2(6)",
- "AC-2(8)",
- "AC-3",
- "AC-3(8)",
- "AC-6",
- "AC-6(7)",
- "AU-10",
- "AU-10(4)",
- "AU-16",
- "AU-16(1)",
- "CM-7",
- "CM-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.IP-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-04",
- "GV.SC-10",
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.5",
- "8.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_user_console_access_unused"
- ]
- },
- {
- "Id": "IAM-08",
- "Description": "Review and revalidate user access for least privilege and separation of duties with a frequency that is commensurate with organizational risk tolerance.",
- "Name": "User Access Review",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27001: A.9.2.6",
- "27001: A.9.4.1",
- "27017: 9.4.1",
- "27001: A.6.1.2",
- "27001: A 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.3",
- "27001: A.5.18",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "AC-6(8)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5.1",
- "7.2.5",
- "7.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_user_console_access_unused",
- "ram_rotate_access_key_90_days"
- ]
- },
- {
- "Id": "IAM-09",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the segregation of privileged access roles such that administrative access to data, encryption and key management capabilities and logging capabilities are distinct and separated.",
- "Name": "Segregation of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.1",
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-3(7)",
- "AC-6(4)",
- "AC-6(8)",
- "IA-5",
- "IA-5(6)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.3",
- "3.5.2",
- "7.1.2",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.7.6",
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_policy_attached_only_to_group_or_roles",
- "ram_no_root_access_key"
- ]
- },
- {
- "Id": "IAM-10",
- "Description": "Define and implement an access process to ensure privileged access roles and rights are granted for a time limited period, and implement procedures to prevent the culmination of segregated privileged access.",
- "Name": "Management of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "6.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3",
- "27001: A.9.4.4",
- "27002: 9.4.4",
- "27017: 9.4.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(7)",
- "AC-3",
- "AC-3(4)",
- "AC-3(11)",
- "AC-3(13)",
- "AC-3(14)",
- "AC-6",
- "AC-6(4)",
- "AC-6(5)",
- "AC-6(8)",
- "AC-12",
- "AC-12(3)",
- "AC-17",
- "AC-17(4)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_no_root_access_key",
- "ram_policy_no_administrative_privileges"
- ]
- },
- {
- "Id": "IAM-12",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the logging infrastructure is read-only for all with write access, including privileged access roles, and that the ability to disable it is controlled through a procedure that ensures the segregation of duties and break glass procedures.",
- "Name": "Safeguard Logs Integrity",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.3"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1",
- "27018: 12.4.1",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27017: 12.4.2",
- "27018: 12.4.2",
- "27001: A.12.4.3",
- "27002: 12.4.3",
- "27017: 12.4.3",
- "27018: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.18",
- "27002: 8.15 Protection of Logs"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(11)",
- "AC-2(12)",
- "IA-8",
- "IA-8(4)",
- "SA-8",
- "SA-8(22)",
- "SC-34",
- "SC-34(1)",
- "SC-34(2)",
- "SC-36",
- "SI-4",
- "SI-4(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_oss_bucket_not_publicly_accessible"
- ]
- },
- {
- "Id": "IAM-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure users are identifiable through unique IDs or which can associate individuals to the usage of user IDs.",
- "Name": "Uniquely Identifiable Users",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.1",
- "27002: 9.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(14)",
- "AC-24",
- "AC-24(2)",
- "AU-10",
- "AU-10(1)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-4",
- "IA-4(1)",
- "SA-8",
- "SA-8(22)",
- "SC-23",
- "SC-23(3)",
- "SC-40(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1",
- "8.2",
- "8.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.1",
- "8.2.2",
- "8.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_user_mfa_enabled_console_access"
- ]
- },
- {
- "Id": "IAM-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for authenticating access to systems, application and data assets, including multifactor authentication for at least privileged user and sensitive data access. Adopt digital certificates or alternatives which achieve an equivalent level of security for system identities.",
- "Name": "Strong Authentication",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.3",
- "6.5",
- "12.5",
- "12.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4",
- "SA1.8"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27017: 9.1.2",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.9.4.2",
- "27002: 9.4.2",
- "27017: 9.4.2",
- "27018: 9.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.17",
- "27001: A.8.5",
- "27001: A.8.24",
- "27002: 8.5",
- "27002: 8.24 other information (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(5)",
- "AC-7",
- "AC-7(4)",
- "AU-10",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(8)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5",
- "IA-5(2)",
- "IA-5(7)",
- "IA-5(9)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-5(14)-(16)",
- "IA-8",
- "IA-8(1)",
- "IA-8(6)",
- "SC-23",
- "SC-23(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3",
- "8.1.6",
- "8.2",
- "8.3",
- "8.3.2",
- "12.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "8.3.1",
- "8.3.2",
- "8.4.1",
- "8.4.2",
- "8.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_user_mfa_enabled_console_access"
- ]
- },
- {
- "Id": "IAM-15",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the secure management of passwords.",
- "Name": "Passwords Management",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27018: 9.2.4",
- "27001: A.9.3.1",
- "27002: 9.3.1",
- "27017: 9.3.1",
- "27018: 9.3.1",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.17"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IA-4",
- "IA-4(8)",
- "IA-5",
- "IA-5(1)",
- "IA-5(8)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.2",
- "8.2.1-6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.2",
- "2.3.1",
- "8.3.5",
- "8.3.6",
- "8.3.7",
- "8.3.8",
- "8.3.9",
- "8.3.10",
- "8.3.10.1",
- "8.6.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_password_policy_minimum_length",
- "ram_password_policy_password_reuse_prevention",
- "ram_password_policy_max_password_age"
- ]
- },
- {
- "Id": "IAM-16",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to verify access to data and system functions is authorized.",
- "Name": "Authorization Mechanisms",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27002: 9.2.5",
- "27017: 9.2.5",
- "27018: 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(5)",
- "AC-4",
- "AC-4(17)",
- "AC-4(21)",
- "AC-4(22)",
- "AC-6",
- "AC-6(8)",
- "AC-6(9)",
- "AC-12",
- "AC-12(1)",
- "AC-20",
- "AC-20(1)",
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5(1)",
- "IA-5(2)",
- "IA-5(5)",
- "IA-5(8)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-8",
- "IA-8(1)",
- "IA-8(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.AC-6",
- "PR.AC-7",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03",
- "PR.AA-04",
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.3",
- "7.1.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.4",
- "7.2.3",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ram_policy_no_administrative_privileges",
- "cs_kubernetes_rbac_enabled"
- ]
- },
- {
- "Id": "IPY-03",
- "Description": "Implement cryptographically secure and standardized network protocols for the management, import and export of data.",
- "Name": "Secure Interoperability and Portability Management",
- "Attributes": [
- {
- "Section": "Interoperability & Portability",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IPY-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.2",
- "NC1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1",
- "27001: A.15.1.1",
- "27002: 15.1.1",
- "27017: 15.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.19",
- "27001: A.5.23",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PT-2",
- "PT-2(2)",
- "SA-4",
- "SC-16",
- "SC-16(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.1",
- "1.2.5",
- "1.2.6",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "oss_bucket_secure_transport_enabled"
- ]
- },
- {
- "Id": "IVS-02",
- "Description": "Plan and monitor the availability, quality, and adequate capacity of resources in order to deliver the required system performance as determined by the business.",
- "Name": "Capacity and Resource Planning",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-04"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.3",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.12.1.3",
- "27002: 12.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.3 (b)",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.8.6",
- "27001: A.8.14"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "SC-5",
- "SC-5(2)",
- "SC-4",
- "SI-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-04",
- "GV.OC-04"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "IVS-03",
- "Description": "Monitor, encrypt and restrict communications between environments to only authenticated and authorized connections, as justified by the business. Review these configurations at least annually, and support them by a documented justification of all allowed services, protocols, ports, and compensating controls.",
- "Name": "Network Security",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-06"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.8",
- "3.1",
- "12.2",
- "13.6",
- "13.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: A.5.15 2nd c)",
- "27002: 8.20",
- "27002: 8.21",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-1",
- "SC-4",
- "SC-7",
- "SC-7(4)",
- "SC-7(5)",
- "SC-7(8)",
- "SC-7(9)",
- "SC-7(11)",
- "SC-8",
- "SC-8(1)",
- "SC-11",
- "SC-12",
- "SC-16",
- "SC-23",
- "SC-29",
- "SC-29(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-5",
- "PR.AC-7",
- "PR.PT-4",
- "DE.CM-1",
- "DE.CM-7",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-01",
- "PR.AA-03",
- "PR.AA-05",
- "DE.CM-01",
- "PR.DS-02",
- "ID.AM-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "1.1.6",
- "1.2",
- "1.2.3",
- "2.2",
- "4.1.1",
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.5",
- "1.2.6",
- "1.2.7",
- "1.4.2",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1",
- "10.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "vpc_flow_logs_enabled",
- "ecs_securitygroup_restrict_ssh_internet",
- "ecs_securitygroup_restrict_rdp_internet"
- ]
- },
- {
- "Id": "IVS-04",
- "Description": "Harden host and guest OS, hypervisor or infrastructure control plane according to their respective best practices, and supported by technical controls, as part of a security baseline.",
- "Name": "OS Hardening and Base Controls",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.8",
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-07",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "4.1",
- "4.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.3",
- "SY1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.14.2.2",
- "27002: 14.2.2",
- "27001: A.14.2.3",
- "27001 A.14.2.4",
- "27018: 12.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: 8.20",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(1)",
- "SC-29",
- "SC-29(1)",
- "SC-2",
- "SC-7",
- "SC-7(12)",
- "SC-30",
- "SC-34",
- "SC-35",
- "SC-39",
- "SC-44"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-1",
- "PR.PT-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ecs_instance_latest_os_patches_applied",
- "ecs_instance_endpoint_protection_installed"
- ]
- },
- {
- "Id": "IVS-06",
- "Description": "Design, develop, deploy and configure applications and infrastructures such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented and segregated, monitored and restricted from other tenants.",
- "Name": "Segmentation and Segregation",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-09"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.3.4",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.20",
- "27001: A.8.3",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.22",
- "27002: 5.15 (b)",
- "27002: 8.3 (b)",
- "27002: 8.16 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-3",
- "SC-7",
- "SC-7(20)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.AC-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.6",
- "8.3.1",
- "10.8",
- "11.3",
- "A3.2.1",
- "A3.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A1.1.1",
- "A1.1.2",
- "A1.1.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cs_kubernetes_network_policy_enabled",
- "cs_kubernetes_private_cluster_enabled",
- "ecs_instance_no_legacy_network"
- ]
- },
- {
- "Id": "IVS-07",
- "Description": "Use secure and encrypted communication channels when migrating servers, services, applications, or data to cloud environments. Such channels must include only up-to-date and approved protocols.",
- "Name": "Migration to Cloud Environments",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-10"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM1.4",
- "NC1.4",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27017: 13.1.1",
- "27018: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27017: 13.1.2",
- "27018: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3",
- "27018: 13.1.3",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27017: 13.2.1",
- "27018: 13.2.1",
- "27001: A.13.2.2",
- "27002: 13.2.2",
- "27017: 13.2.2",
- "27018: 13.2.2",
- "27001: A.13.2.3",
- "27002: 13.2.3",
- "27017: 13.2.3",
- "27018: 13.2.3",
- "27001: A.13.2.4",
- "27002: 13.2.4",
- "27017: 13.2.4",
- "27018: 13.2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.20",
- "27001: A.8.24",
- "27002: 8.20 (e)",
- "27002: 8.24 Guidance (b,f), other information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-17",
- "AC-20",
- "SC-7",
- "SC-7(28)",
- "SC-8",
- "SC-8(1)",
- "SC-12",
- "SC-23",
- "SC-29",
- "SI-7",
- "SI-7(1)-(3)",
- "SI-7(5)-(10)",
- "SI-7(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "rds_instance_ssl_enabled"
- ]
- },
- {
- "Id": "IVS-09",
- "Description": "Define, implement and evaluate processes, procedures and defense-in-depth techniques for protection, detection, and timely response to network-based attacks.",
- "Name": "Network Defense",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.6",
- "CC6.8",
- "CC7.1",
- "CC7.2",
- "CC7.5"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-13"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "13.3",
- "13.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3",
- "5.2.4",
- "5.2.5",
- "5.2.7",
- "5.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.11.1.4",
- "27002: 11.1.4",
- "27017: 11.1.4",
- "27018: 16.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.5.24",
- "27001: A.5.26",
- "27001: A.8.8",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.26",
- "27002: 8.8 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-8",
- "PL-8(1)",
- "SC-5",
- "SC-5(1)",
- "SC-5(3)",
- "SC-7",
- "SC-7(13)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.DP-1",
- "DE.CM-1",
- "DE.CM-7",
- "PR.AC-5",
- "RS.MI-2",
- "PR.DS-2",
- "RS.RP-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "DE.CM-01",
- "PR.IR-01",
- "RS.MA-01",
- "RS.MI-01",
- "RS.MI-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.6",
- "1.1",
- "1.2",
- "1.3",
- "1.5",
- "12.10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.1.1",
- "1.3.1",
- "1.3.2",
- "1.3.3",
- "1.4.1",
- "1.4.2",
- "1.4.3",
- "1.4.4",
- "1.4.5",
- "1.5.1",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition",
- "sls_cloud_firewall_changes_alert_enabled"
- ]
- },
- {
- "Id": "LOG-02",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the security and retention of audit logs.",
- "Name": "Audit Logs Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1",
- "8.9",
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.3",
- "5.1.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-4",
- "AU-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-08",
- "PR.DS-11",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.7"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4",
- "10.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_oss_bucket_not_publicly_accessible",
- "sls_logstore_retention_period"
- ]
- },
- {
- "Id": "LOG-03",
- "Description": "Identify and monitor security-related events within applications and the underlying infrastructure. Define and implement a system to generate alerts to responsible stakeholders based on such events and corresponding metrics.",
- "Name": "Security Monitoring and Alerting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03",
- "SEF-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "5.2.7",
- "1.6.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2",
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-3",
- "DE.AE-5",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-4",
- "DE.CM-5",
- "DE.CM-6",
- "DE.CM-7",
- "DE.DP-1",
- "DE.DP-4",
- "DE.AE-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2",
- "10.4.1.1",
- "10.4.2.1",
- "10.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition",
- "securitycenter_notification_enabled_high_risk",
- "sls_unauthorized_api_calls_alert_enabled",
- "sls_root_account_usage_alert_enabled",
- "sls_management_console_signin_without_mfa_alert_enabled"
- ]
- },
- {
- "Id": "LOG-04",
- "Description": "Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.",
- "Name": "Audit Logs Access and Accountability",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.1",
- "4.1.2",
- "4.1.3",
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27001: A.12.4.1",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(4)",
- "AU-9(6)",
- "AU-10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.1",
- "10.2.1",
- "10.2.3",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1.3",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_oss_bucket_not_publicly_accessible"
- ]
- },
- {
- "Id": "LOG-05",
- "Description": "Monitor security audit logs to detect activity outside of typical or expected patterns. Establish and follow a defined process to review and take appropriate and timely actions on detected anomalies.",
- "Name": "Audit Logs Monitoring and Response",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.8",
- "8.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "1.6.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.3",
- "27002: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-6",
- "AU-6(1)",
- "AU-6(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-3",
- "PR.PT-1",
- "RS.AN-1",
- "RS.CO-1.",
- "DE.AE-1",
- "DE.AE-5",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6",
- "10.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.1.1",
- "10.4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "sls_unauthorized_api_calls_alert_enabled",
- "sls_root_account_usage_alert_enabled",
- "sls_management_console_signin_without_mfa_alert_enabled",
- "sls_ram_role_changes_alert_enabled",
- "sls_security_group_changes_alert_enabled",
- "sls_vpc_changes_alert_enabled",
- "sls_vpc_network_route_changes_alert_enabled",
- "sls_management_console_authentication_failures_alert_enabled",
- "sls_customer_created_cmk_changes_alert_enabled",
- "sls_oss_bucket_policy_changes_alert_enabled",
- "sls_oss_permission_changes_alert_enabled",
- "sls_cloud_firewall_changes_alert_enabled",
- "sls_rds_instance_configuration_changes_alert_enabled"
- ]
- },
- {
- "Id": "LOG-07",
- "Description": "Establish, document and implement which information meta/data system events should be logged. Review and update the scope at least annually or whenever there is a change in the threat environment.",
- "Name": "Logging Scope",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-14",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.SC-4",
- "PR.PT-1",
- "ID.GV-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_multi_region_enabled",
- "vpc_flow_logs_enabled"
- ]
- },
- {
- "Id": "LOG-08",
- "Description": "Generate audit records containing relevant security information.",
- "Name": "Log Records",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-3",
- "AU-3(1)",
- "AU-3(3)",
- "AU-6",
- "AU-6(8)",
- "AU-12",
- "AU-12(1)",
- "AU-12(2)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-6",
- "DE.CM-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_multi_region_enabled",
- "vpc_flow_logs_enabled",
- "oss_bucket_logging_enabled",
- "rds_instance_sql_audit_enabled",
- "cs_kubernetes_log_service_enabled",
- "rds_instance_postgresql_log_connections_enabled",
- "rds_instance_postgresql_log_disconnections_enabled",
- "rds_instance_postgresql_log_duration_enabled"
- ]
- },
- {
- "Id": "LOG-09",
- "Description": "The information system protects audit records from unauthorized access, modification, and deletion.",
- "Name": "Log Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04",
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(2)",
- "AU-9(3)",
- "AU-9(4)",
- "AU-12(3)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_oss_bucket_not_publicly_accessible"
- ]
- },
- {
- "Id": "LOG-10",
- "Description": "Establish and maintain a monitoring and internal reporting capability over the operations of cryptographic, encryption and key management policies, processes, procedures, and controls.",
- "Name": "Encryption Monitoring and Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.1.1",
- "10.2.1",
- "10.4.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "sls_customer_created_cmk_changes_alert_enabled"
- ]
- },
- {
- "Id": "LOG-11",
- "Description": "Log and monitor key lifecycle management events to enable auditing and reporting on usage of cryptographic keys.",
- "Name": "Transaction/Activity Logging",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "actiontrail_multi_region_enabled"
- ]
- },
- {
- "Id": "LOG-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the reporting of anomalies and failures of the monitoring system and provide immediate notification to the accountable party.",
- "Name": "Failures and Anomalies Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.16.1.2",
- "27017: 16.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.24",
- "27001: A.6.8",
- "27002: 6.8 (g)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-6",
- "AU-6(3)",
- "AU-6(4)",
- "AU-6(5)",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-3",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.3",
- "10.7.1",
- "10.7.2",
- "10.7.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition",
- "securitycenter_notification_enabled_high_risk"
- ]
- },
- {
- "Id": "SEF-03",
- "Description": "'Establish, document, approve, communicate, apply, evaluate and maintain a security incident response plan, which includes but is not limited to: relevant internal departments, impacted CSCs, and other business critical relationships (such as supply-chain) that may be impacted.'",
- "Name": "Incident Response Plans",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2",
- "CC7.3",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2",
- "17.4"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27017: CLD.12.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.5.26",
- "27002: 5.26 (e,f)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-1",
- "IR-2",
- "IR-2(1)-(3)",
- "IR-3",
- "IR-3(1)-(3)",
- "IR-4",
- "IR-4(1)-(15)",
- "IR-5",
- "IR-5(1)",
- "IR-6",
- "IR-6(1)-(3)",
- "IR-7",
- "IR-7(1)",
- "IR-7(2)",
- "IR-8",
- "IR-8(1)",
- "IR-9",
- "IR-9(1)-(4)",
- "PM-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.CO-1",
- "RS.CO-4",
- "ID.AM-6",
- "ID.GV-2",
- "ID.SC-5",
- "PR.IP-9",
- "PR.IP10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AT-01",
- "PR.AT-02",
- "RS.MA-01",
- "GV.SC-08",
- "ID.IM-02",
- "ID.IM-04",
- "RC.RP-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "12.10.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "SEF-06",
- "Description": "Define, implement and evaluate processes, procedures and technical measures supporting business processes to triage security-related events.",
- "Name": "Event Triage Processes",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.4",
- "27002: 16.1.4",
- "27017: 16.1.4",
- "27018: 16.1.4",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.25"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(3)",
- "CA-7(4)",
- "CA-7(5)",
- "CA-7(6)",
- "IR-4",
- "IR-4(1)",
- "IR-4(3)",
- "IR-4(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-4",
- "RS.RP-1",
- "RS.AN-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "RS.MA-02",
- "RS.MA-03",
- "RS.AN-03",
- "DE.AE-02",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "RS.MI-02",
- "RC.RP-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition"
- ]
- },
- {
- "Id": "SEF-08",
- "Description": "Maintain points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities.",
- "Name": "Points of Contact Maintenance",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.2",
- "27001: A.6.1.3",
- "27002: 6.1.3",
- "27017: 6.1.3",
- "27018: 6.1.3",
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.18.1.1",
- "27002: 18.1.1",
- "27017: 18.1.1",
- "27018: 18.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.5",
- "27001: A.5.24",
- "27002: 5.24 Incident management procedure (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-4",
- "IR-4(8)",
- "IR-6",
- "IR-6(3)",
- "IR-7",
- "IR-7(2)",
- "PM-21",
- "PM-23",
- "PM-26"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-2",
- "RS.CO-3",
- "RS.CO-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-02",
- "RS.CO-02",
- "RS.CO-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-02",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually.",
- "Name": "Malware Protection Policy and Procedures",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.8"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-01",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "9.7",
- "10.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.2",
- "TS1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.12.2.1",
- "27001: A.6.2.1",
- "27002: 6.2.1 (h)",
- "27001: A.6.2.2",
- "27002: 6.2.2 (j)",
- "27001: A.7.2.2",
- "27002: 7.2.2 (d)",
- "27001: A.10.1.1",
- "27002: 10.1.1 (g)",
- "27001: A.13.2.1",
- "27002: 13.2.1 (b)",
- "27001: A.15.1.2",
- "27017: 15.1.2",
- "27001: A.12.2.1",
- "27002: 12.2.1 (a),(d)",
- "27017: CLD.9.5.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.7",
- "27001: A.5.37",
- "27001: A.8.7",
- "27002: 5.7 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-3",
- "RA-3(3)",
- "RA-5",
- "RA-5(3)",
- "RA-5(5)",
- "SI-3",
- "SI-3(4)",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "DE.CM-4",
- "DE.CM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "DE.CM-01",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.4",
- "12.1",
- "12.1.1",
- "12.3.1",
- "12.5.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.1.1",
- "12.1.2",
- "5.1.1",
- "5.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ecs_instance_endpoint_protection_installed"
- ]
- },
- {
- "Id": "TVM-03",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to enable both scheduled and emergency responses to vulnerability identifications, based on the identified risk.",
- "Name": "Vulnerability Remediation Schedule",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC7.1",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.2",
- "7.7",
- "17.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "TM2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.2.1",
- "27001: A.12.6.1",
- "27002: 12.6.1(c)(d)(j)",
- "27018: 12.6.1(k)(i)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.8.7",
- "27001: A.8.8",
- "27001: A.8.32",
- "27002: 8.7",
- "27002: 8.8",
- "27002: 8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-31",
- "RA-3",
- "RA-3(1)",
- "RA-5",
- "RA-5(2)-(4)",
- "RA-5(6)",
- "SI-3",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.AN-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.1.a",
- "6.1.b"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.1.1",
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ecs_instance_latest_os_patches_applied"
- ]
- },
- {
- "Id": "TVM-04",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to update detection tools, threat signatures, and indicators of compromise on a weekly, or more frequent basis.",
- "Name": "Detection Updates",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.3",
- "TS1.4",
- "TM1.3",
- "TM1.4",
- "IM1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1.1",
- "27002: 5.1.1 (h)",
- "27001: A.12.6.1",
- "27002: 12.6.1 (b),(c)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1",
- "27001: A.8.8",
- "27001: A.8.15",
- "27001: A.8.16",
- "27002: 5.1",
- "27002: 5.37",
- "27002: 8.8",
- "27002: 8.15 (d)",
- "27002: 8.16 (d,e)",
- "27002: 8.31 2nd (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-7",
- "CM-7(4)",
- "RA-3",
- "RA-3(3)",
- "RA-5(2)",
- "SA-10",
- "SA-10(5)",
- "SA-11",
- "SA-11(2)",
- "SI-2",
- "SI-2(4)",
- "SI-3",
- "SI-3(4)",
- "SI-4",
- "SI-4(9)",
- "SI-4(24)",
- "SI-8",
- "SI-8(2)",
- "SI-8(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-02",
- "ID.RA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.2",
- "5.2a",
- "5.2b",
- "5.2c"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "5.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_advanced_or_enterprise_edition",
- "securitycenter_vulnerability_scan_enabled"
- ]
- },
- {
- "Id": "TVM-05",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to identify updates for applications which use third party or open source libraries according to the organization's vulnerability management policy.",
- "Name": "External Library Vulnerabilities",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "SD2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.6.2",
- "27002: 12.6.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A 5.6",
- "27001: A.8.19",
- "27001: A.8.8",
- "27001: A.8.28",
- "27001: A.8.31",
- "27002: 5.6 (c)",
- "27001: 8.19",
- "27001: 8.8",
- "27001: 8.28",
- "27001: 8.31"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(3)",
- "SA-11",
- "SA-11(2)",
- "SA-11(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-03",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.2",
- "6.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_vulnerability_scan_enabled"
- ]
- },
- {
- "Id": "TVM-07",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the detection of vulnerabilities on organizationally managed assets at least monthly.",
- "Name": "Vulnerability Identification",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.1",
- "7.5",
- "7.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.6",
- "27001: A.12.6.1",
- "27002: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.8",
- "27002: 8.8"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(4)",
- "RA-5(5)",
- "SA-11",
- "SA-11(5)",
- "SA-15(5)",
- "SC-7",
- "SC-7(10)",
- "SI-3(8)",
- "SI-3(10)",
- "SI-7",
- "SI-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.RA-1",
- "DE.CM-8",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "11.2",
- "11.2.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "11.3.2",
- "11.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securitycenter_vulnerability_scan_enabled",
- "securitycenter_advanced_or_enterprise_edition"
- ]
- },
- {
- "Id": "UEM-08",
- "Description": "Protect information from unauthorized disclosure on managed endpoint devices with storage encryption.",
- "Name": "Storage Encryption",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "MOS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "3.1.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "PA1.2",
- "PA1.3",
- "PA1.5",
- "PA2.2",
- "PM1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.11.2.7",
- "27002: 11.2.7",
- "27001: A.18.1.1",
- "27017: 18.1.1",
- "27001: A.12.3.1",
- "27017: 12.3.1",
- "27018: A.11.4",
- "27018: A.11.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.1",
- "27002: 8.1 (h)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.4",
- "3.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.5.1",
- "3.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ecs_attached_disk_encrypted",
- "ecs_unattached_disk_encrypted"
- ]
- },
- {
- "Id": "UEM-11",
- "Description": "Configure managed endpoints with Data Loss Prevention (DLP) technologies and rules in accordance with a risk assessment.",
- "Name": "Data Loss Prevention",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.5",
- "PA2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27002: 12.3",
- "27001: A.8.3.1",
- "27002: 8.3.1",
- "27001: A.12.2",
- "27002: 12.2",
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001: A.6.1.1",
- "27017: 6.1.1",
- "27018: 12.3.1",
- "27018: 10.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-7",
- "SC-7(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.DS-10",
- "PR.PS-01",
- "ID.AM-08",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A3.2.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A3.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": []
- }
- ]
-}
diff --git a/prowler/compliance/alibabacloud/prowler_threatscore_alibabacloud.json b/prowler/compliance/alibabacloud/prowler_threatscore_alibabacloud.json
index ca7a030dc2..0bfd47df7e 100644
--- a/prowler/compliance/alibabacloud/prowler_threatscore_alibabacloud.json
+++ b/prowler/compliance/alibabacloud/prowler_threatscore_alibabacloud.json
@@ -47,6 +47,14 @@
"Checks": [
"ram_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "ram_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
+ ],
"Attributes": [
{
"Title": "Inactive users disabled for console access",
@@ -399,6 +407,14 @@
"LevelOfRisk": 3,
"Weight": 10
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "cs_kubernetes_cluster_check_weekly",
+ "ConfigKey": "max_cluster_check_days",
+ "Operator": "lte",
+ "Value": 7
+ }
]
},
{
@@ -695,6 +711,14 @@
"Checks": [
"rds_instance_sql_audit_retention"
],
+ "ConfigRequirements": [
+ {
+ "Check": "rds_instance_sql_audit_retention",
+ "ConfigKey": "min_rds_audit_retention_days",
+ "Operator": "gte",
+ "Value": 180
+ }
+ ],
"Attributes": [
{
"Title": "RDS SQL audit retention configured",
diff --git a/prowler/compliance/aws/asd_essential_eight_aws.json b/prowler/compliance/aws/asd_essential_eight_aws.json
index 00b39817e3..dd39c44268 100644
--- a/prowler/compliance/aws/asd_essential_eight_aws.json
+++ b/prowler/compliance/aws/asd_essential_eight_aws.json
@@ -13,6 +13,14 @@
"config_recorder_all_regions_enabled",
"inspector2_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Patch applications",
@@ -260,6 +268,14 @@
"config_recorder_all_regions_enabled",
"inspector2_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "2 Patch operating systems",
@@ -742,6 +758,14 @@
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Restrict administrative privileges",
diff --git a/prowler/compliance/aws/aws_account_security_onboarding_aws.json b/prowler/compliance/aws/aws_account_security_onboarding_aws.json
index 1d038537f0..1910bac223 100644
--- a/prowler/compliance/aws/aws_account_security_onboarding_aws.json
+++ b/prowler/compliance/aws/aws_account_security_onboarding_aws.json
@@ -37,6 +37,26 @@
"guardduty_is_enabled",
"accessanalyzer_enabled",
"macie_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -259,6 +279,20 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -514,6 +548,14 @@
"Checks": [
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -530,6 +572,20 @@
"securityhub_enabled",
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -666,6 +722,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -680,6 +744,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -694,6 +766,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -708,6 +788,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -722,6 +810,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -736,6 +832,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -762,6 +866,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -777,6 +889,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_centrally_managed"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -792,6 +912,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -807,6 +935,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -822,6 +958,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -837,6 +981,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -852,6 +1004,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -867,6 +1027,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -882,6 +1050,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -897,6 +1073,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -912,6 +1096,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/aws_ai_security_framework_aws.json b/prowler/compliance/aws/aws_ai_security_framework_aws.json
new file mode 100644
index 0000000000..9b87f7464d
--- /dev/null
+++ b/prowler/compliance/aws/aws_ai_security_framework_aws.json
@@ -0,0 +1,1198 @@
+{
+ "Framework": "AWS-AI-Security-Framework",
+ "Name": "AWS AI Security Framework",
+ "Version": "1.0",
+ "Provider": "AWS",
+ "Description": "Security compliance framework based on the AWS AI Security Framework blog post (2025). Organizes controls across three security layers (Infrastructure, Identity & Data, AI Application), three deployment phases (Foundational, Enhanced, Advanced), and three AI use cases (AI that Answers, AI that Connects, AI that Acts). Maps existing Prowler checks to AI workload security requirements and identifies gaps requiring new checks.",
+ "Requirements": [
+ {
+ "Id": "AISF-INFRA-01",
+ "Description": "Ensure VPC endpoints provide private connectivity for Bedrock APIs, preventing AI traffic from traversing the public internet.",
+ "Name": "Bedrock VPC Private Connectivity",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Network Isolation",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_vpc_endpoints_configured"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-02",
+ "Description": "Ensure VPCs have Network Firewall enabled to inspect and filter AI workload traffic, with logging, multi-AZ deployment, and proper default actions for both full and fragmented packets.",
+ "Name": "Network Firewall for AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Network Firewall",
+ "Service": "networkfirewall",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "networkfirewall_in_all_vpc",
+ "networkfirewall_logging_enabled",
+ "networkfirewall_multi_az",
+ "networkfirewall_policy_default_action_full_packets",
+ "networkfirewall_policy_default_action_fragmented_packets",
+ "networkfirewall_policy_rule_group_associated",
+ "networkfirewall_deletion_protection"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-03",
+ "Description": "Ensure WAFv2 Web ACLs are configured with rules and logging to protect AI application endpoints from HTTP-based attacks including prompt injection patterns at the perimeter.",
+ "Name": "WAF Protection for AI Endpoints",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Web Application Firewall",
+ "Service": "wafv2",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "wafv2_webacl_with_rules",
+ "wafv2_webacl_logging_enabled",
+ "wafv2_webacl_rule_logging_enabled",
+ "apigateway_restapi_waf_acl_attached",
+ "cognito_user_pool_waf_acl_attached"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-04",
+ "Description": "Ensure AWS Shield Advanced is enabled to protect internet-facing AI application infrastructure from DDoS attacks.",
+ "Name": "DDoS Protection for AI Infrastructure",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "DDoS Protection",
+ "Service": "shield",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "shield_advanced_protection_in_cloudfront_distributions",
+ "shield_advanced_protection_in_internet_facing_load_balancers",
+ "shield_advanced_protection_in_classic_load_balancers",
+ "shield_advanced_protection_in_route53_hosted_zones",
+ "shield_advanced_protection_in_associated_elastic_ips",
+ "shield_advanced_protection_in_global_accelerators"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-05",
+ "Description": "Ensure all data at rest is encrypted with AES-256 across AI workload storage including S3 buckets, EBS volumes, RDS instances, SageMaker notebooks, and Bedrock prompts using customer-managed KMS keys where possible.",
+ "Name": "Encryption at Rest for AI Data",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Encryption at Rest",
+ "Service": "kms",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "s3_bucket_default_encryption",
+ "s3_bucket_kms_encryption",
+ "ec2_ebs_default_encryption",
+ "ec2_ebs_volume_encryption",
+ "rds_instance_storage_encrypted",
+ "sagemaker_notebook_instance_encryption_enabled",
+ "sagemaker_training_jobs_volume_and_output_encryption_enabled",
+ "bedrock_model_invocation_logs_encryption_enabled",
+ "cloudtrail_kms_encryption_enabled",
+ "cloudwatch_log_group_kms_encryption_enabled",
+ "eks_cluster_kms_cmk_encryption_in_secrets_enabled",
+ "dynamodb_tables_kms_cmk_encryption_enabled",
+ "sns_topics_kms_encryption_at_rest_enabled",
+ "sqs_queues_server_side_encryption_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-06",
+ "Description": "Ensure all data in transit uses TLS 1.2 or higher, including API communications, inter-container traffic for ML training, and connections between AI application components.",
+ "Name": "Encryption in Transit for AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Encryption in Transit",
+ "Service": "multiple",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "s3_bucket_secure_transport_policy",
+ "sagemaker_training_jobs_intercontainer_encryption_enabled",
+ "elbv2_ssl_listeners",
+ "elbv2_insecure_ssl_ciphers",
+ "cloudfront_distributions_https_enabled",
+ "cloudfront_distributions_using_deprecated_ssl_protocols",
+ "opensearch_service_domains_https_communications_enforced",
+ "opensearch_service_domains_node_to_node_encryption_enabled",
+ "apigateway_restapi_client_certificate_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-07",
+ "Description": "Ensure customer-managed KMS keys are in use, rotation is enabled, and keys are not scheduled for unintentional deletion to maintain control over AI data encryption.",
+ "Name": "Customer-Managed Key Governance",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Key Management",
+ "Service": "kms",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "kms_cmk_are_used",
+ "kms_cmk_rotation_enabled",
+ "kms_cmk_not_deleted_unintentionally",
+ "kms_key_not_publicly_accessible"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-08",
+ "Description": "Ensure VPC endpoints enforce trust boundaries, subnets do not assign public IPs by default, and flow logs are enabled for all VPCs hosting AI workloads.",
+ "Name": "VPC Security for AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "VPC Security",
+ "Service": "vpc",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "vpc_flow_logs_enabled",
+ "vpc_subnet_no_public_ip_by_default",
+ "vpc_subnet_separate_private_public",
+ "vpc_endpoint_connections_trust_boundaries",
+ "vpc_endpoint_services_allowed_principals_trust_boundaries",
+ "vpc_endpoint_for_ec2_enabled",
+ "vpc_peering_routing_tables_with_least_privilege"
+ ]
+ },
+ {
+ "Id": "AISF-INFRA-09",
+ "Description": "Ensure hardware-enforced compute isolation is in use for AI workloads. AWS Nitro System provides isolation with no operator access to customer data during model inference and training.",
+ "Name": "Hardware-Enforced Compute Isolation",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Compute Isolation",
+ "Service": "ec2",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-IAM-01",
+ "Description": "Ensure MFA is enforced for all users accessing AI services, including root account hardware MFA, IAM user MFA for console access, and Cognito user pool MFA for AI application end users.",
+ "Name": "Multi-Factor Authentication for AI Access",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Authentication",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_root_mfa_enabled",
+ "iam_root_hardware_mfa_enabled",
+ "iam_user_mfa_enabled_console_access",
+ "iam_user_hardware_mfa_enabled",
+ "iam_administrator_access_with_mfa",
+ "cognito_user_pool_mfa_enabled",
+ "cognito_user_pool_advanced_security_enabled",
+ "cognito_user_pool_blocks_compromised_credentials_sign_in_attempts",
+ "cognito_user_pool_blocks_potential_malicious_sign_in_attempts"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-02",
+ "Description": "Ensure least-privilege access is enforced for all AI service identities. No administrative privileges should be attached to IAM entities that interact with Bedrock, SageMaker, or other AI services.",
+ "Name": "Least Privilege for AI Identities",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Authorization",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_aws_attached_policy_no_administrative_privileges",
+ "iam_customer_attached_policy_no_administrative_privileges",
+ "iam_inline_policy_no_administrative_privileges",
+ "iam_policy_allows_privilege_escalation",
+ "iam_inline_policy_allows_privilege_escalation",
+ "iam_role_administratoraccess_policy",
+ "iam_user_administrator_access_policy",
+ "iam_group_administrator_access_policy",
+ "iam_policy_attached_only_to_group_or_roles",
+ "iam_no_custom_policy_permissive_role_assumption",
+ "bedrock_full_access_policy_attached",
+ "bedrock_api_key_no_administrative_privileges"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-03",
+ "Description": "Ensure temporary and scoped credentials are used for AI service access. Long-term access keys should be avoided, rotated within 90 days when necessary, and unused keys should be disabled.",
+ "Name": "Temporary Scoped Credentials",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Credential Management",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_user_with_temporary_credentials",
+ "iam_rotate_access_key_90_days",
+ "iam_user_accesskey_unused",
+ "iam_user_no_setup_initial_access_key",
+ "iam_user_two_active_access_key",
+ "iam_user_console_access_unused",
+ "bedrock_api_key_no_long_term_credentials"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-04",
+ "Description": "Ensure root account is properly secured with no active access keys and minimal usage, as root credentials in AI environments could grant unrestricted access to all AI models, data, and agent configurations.",
+ "Name": "Root Account Security",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Root Account",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_no_root_access_key",
+ "iam_avoid_root_usage",
+ "iam_root_credentials_management_enabled",
+ "cloudwatch_log_metric_filter_root_usage"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-05",
+ "Description": "Ensure IAM roles used for AI services prevent cross-service confused deputy attacks and stale access to Bedrock and SageMaker is reviewed regularly.",
+ "Name": "AI Service Role Security",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Service Roles",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_role_cross_service_confused_deputy_prevention",
+ "iam_role_access_not_stale_to_bedrock",
+ "iam_user_access_not_stale_to_bedrock",
+ "iam_role_cross_account_readonlyaccess_policy"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-06",
+ "Description": "Ensure strong password policies are enforced with minimum length, complexity requirements, expiration, and reuse prevention for all human identities accessing AI services.",
+ "Name": "Password Policy for AI Service Access",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Password Policy",
+ "Service": "iam",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "iam_password_policy_minimum_length_14",
+ "iam_password_policy_uppercase",
+ "iam_password_policy_lowercase",
+ "iam_password_policy_number",
+ "iam_password_policy_symbol",
+ "iam_password_policy_reuse_24",
+ "iam_password_policy_expires_passwords_within_90_days_or_less",
+ "cognito_user_pool_password_policy_minimum_length_14",
+ "cognito_user_pool_password_policy_lowercase",
+ "cognito_user_pool_password_policy_uppercase",
+ "cognito_user_pool_password_policy_number",
+ "cognito_user_pool_password_policy_symbol"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-07",
+ "Description": "Ensure Cognito user pools are properly configured for AI application user authentication with advanced security features, token revocation, self-registration controls, and WAF protection.",
+ "Name": "Cognito User Authentication for AI Apps",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "User Authentication",
+ "Service": "cognito",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "cognito_user_pool_mfa_enabled",
+ "cognito_user_pool_advanced_security_enabled",
+ "cognito_user_pool_self_registration_disabled",
+ "cognito_user_pool_deletion_protection_enabled",
+ "cognito_user_pool_client_token_revocation_enabled",
+ "cognito_user_pool_client_prevent_user_existence_errors",
+ "cognito_user_pool_temporary_password_expiration",
+ "cognito_user_pool_waf_acl_attached",
+ "cognito_identity_pool_guest_access_disabled"
+ ]
+ },
+ {
+ "Id": "AISF-IAM-08",
+ "Description": "Ensure API Gateway endpoints serving AI applications have proper authorization configured to authenticate and authorize every request to the model layer.",
+ "Name": "API Authorization for AI Endpoints",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "API Authorization",
+ "Service": "apigateway",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "apigateway_restapi_authorizers_enabled",
+ "apigateway_restapi_public_with_authorizer",
+ "apigatewayv2_api_authorizers_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-DATA-01",
+ "Description": "Ensure Amazon Macie is enabled with automated sensitive data discovery to classify and protect enterprise data before it is made available to AI systems through RAG or other patterns.",
+ "Name": "Data Classification for AI",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Data Classification",
+ "Service": "macie",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "macie_is_enabled",
+ "macie_automated_sensitive_data_discovery_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-DATA-02",
+ "Description": "Ensure IAM Access Analyzer is enabled to validate access policies and identify unintended access to resources used by AI workloads.",
+ "Name": "Access Analysis for AI Resources",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Access Analysis",
+ "Service": "accessanalyzer",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "accessanalyzer_enabled",
+ "accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "Id": "AISF-DATA-03",
+ "Description": "Ensure Secrets Manager is used for AI application credentials with automatic rotation enabled, restrictive resource policies, and no public access.",
+ "Name": "Secrets Management for AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Secrets Management",
+ "Service": "secretsmanager",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "secretsmanager_automatic_rotation_enabled",
+ "secretsmanager_secret_rotated_periodically",
+ "secretsmanager_has_restrictive_resource_policy",
+ "secretsmanager_not_publicly_accessible",
+ "secretsmanager_secret_unused"
+ ]
+ },
+ {
+ "Id": "AISF-DATA-04",
+ "Description": "Ensure S3 buckets used for AI training data, model artifacts, RAG knowledge bases, and inference logs have public access blocked, encryption enabled, secure transport enforced, and access logging configured.",
+ "Name": "S3 Data Protection for AI",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Storage Security",
+ "Service": "s3",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "s3_account_level_public_access_blocks",
+ "s3_bucket_level_public_access_block",
+ "s3_bucket_public_access",
+ "s3_bucket_policy_public_write_access",
+ "s3_bucket_default_encryption",
+ "s3_bucket_kms_encryption",
+ "s3_bucket_secure_transport_policy",
+ "s3_bucket_server_access_logging_enabled",
+ "s3_bucket_object_versioning",
+ "s3_bucket_acl_prohibited",
+ "s3_bucket_cross_account_access"
+ ]
+ },
+ {
+ "Id": "AISF-DATA-05",
+ "Description": "Ensure no secrets or credentials are hardcoded in Lambda functions, ECS task definitions, or EC2 instances used as part of AI application architectures.",
+ "Name": "No Hardcoded Secrets in AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Secret Hygiene",
+ "Service": "multiple",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "awslambda_function_no_secrets_in_code",
+ "awslambda_function_no_secrets_in_variables",
+ "ecs_task_definitions_no_environment_secrets",
+ "ec2_instance_secrets_user_data",
+ "cloudwatch_log_group_no_secrets_in_logs"
+ ]
+ },
+ {
+ "Id": "AISF-DATA-06",
+ "Description": "Ensure the AWS Organization has opted out of all AI services data usage and child accounts cannot override this policy, preventing AWS from using customer data for AI service improvement.",
+ "Name": "AI Services Data Opt-Out",
+ "Attributes": [
+ {
+ "Section": "Identity and Data Security",
+ "SubSection": "Data Governance",
+ "Service": "organizations",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "organizations_opt_out_ai_services_policy"
+ ]
+ },
+ {
+ "Id": "AISF-AI-01",
+ "Description": "Ensure Amazon Bedrock has at least one guardrail configured to provide content filtering, prompt injection defense, PII filtering, and topic restrictions for foundation model interactions.",
+ "Name": "Bedrock Guardrails Configuration",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Content Filtering",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_guardrails_configured"
+ ]
+ },
+ {
+ "Id": "AISF-AI-02",
+ "Description": "Ensure Bedrock guardrails have prompt attack filter strength set to HIGH to detect and block prompt injection attempts, the #1 risk in OWASP Top 10 for LLM Applications.",
+ "Name": "Prompt Injection Defense",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Prompt Security",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_guardrail_prompt_attack_filter_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-AI-03",
+ "Description": "Ensure Bedrock guardrails block or mask sensitive information (PII) in both model inputs and outputs to prevent data leakage through AI responses.",
+ "Name": "PII and Sensitive Data Filtering",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Output Filtering",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_guardrail_sensitive_information_filter_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-AI-04",
+ "Description": "Ensure all Bedrock agents have guardrails enabled to protect agent sessions from prompt injection, data exfiltration, and unauthorized actions during agentic workflows.",
+ "Name": "Agent Guardrail Protection",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Security",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_agent_guardrail_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-AI-05",
+ "Description": "Ensure Bedrock model invocation logging is enabled to maintain an immutable audit trail of all model interactions, enabling incident investigation and behavioral analysis.",
+ "Name": "Model Invocation Logging",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "AI Audit Logging",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_model_invocation_logging_enabled",
+ "bedrock_model_invocation_logs_encryption_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-AI-06",
+ "Description": "Ensure CloudTrail is configured to log all Bedrock API calls for security auditing, enabling detection of unauthorized model access, configuration changes, and potential LLM jacking.",
+ "Name": "Bedrock API Audit Trail",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "AI Audit Logging",
+ "Service": "cloudtrail",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "cloudtrail_threat_detection_llm_jacking"
+ ]
+ },
+ {
+ "Id": "AISF-AI-07",
+ "Description": "Ensure Bedrock prompts are encrypted at rest with customer-managed KMS keys and Prompt Management is used for centralized prompt governance.",
+ "Name": "Prompt Encryption and Management",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Prompt Management",
+ "Service": "bedrock",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "bedrock_prompt_encrypted_with_cmk",
+ "bedrock_prompt_management_exists"
+ ]
+ },
+ {
+ "Id": "AISF-AI-08",
+ "Description": "Ensure Bedrock Automated Reasoning Checks are configured to provide formal verification of model responses against source documents, achieving up to 99% verification accuracy against hallucinations.",
+ "Name": "Automated Reasoning for Output Validation",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Output Validation",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AI-09",
+ "Description": "Ensure Bedrock Contextual Grounding is configured to validate semantic consistency of model responses against sanctioned source documents, preventing hallucinated or fabricated outputs.",
+ "Name": "Contextual Grounding for RAG Validation",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Output Validation",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AI-10",
+ "Description": "Ensure Bedrock Knowledge Bases used for RAG patterns have proper security controls including encryption with customer-managed keys and VPC configuration for private data access.",
+ "Name": "Knowledge Base Security for RAG",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "RAG Security",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AI-11",
+ "Description": "Ensure WAF AI Activity Dashboard is configured to monitor and analyze AI-specific traffic patterns, providing visibility into potential attacks targeting AI endpoints.",
+ "Name": "WAF AI Activity Monitoring",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "AI Traffic Monitoring",
+ "Service": "wafv2",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AGENT-01",
+ "Description": "Ensure every AI agent has its own identity with scoped credentials and independent authorization per request, following zero-trust principles. Agent identities must be separate from human user identities.",
+ "Name": "Agent Identity and Authentication",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AGENT-02",
+ "Description": "Ensure Bedrock AgentCore Cedar Policies enforce provable least-privilege authorization on every tool call and data access made by AI agents.",
+ "Name": "Agent Least-Privilege Authorization",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AGENT-03",
+ "Description": "Ensure AI agents have behavioral monitoring and observability configured to detect scope violations, anomalous actions, and drift from expected behavior patterns.",
+ "Name": "Agent Behavioral Monitoring",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AGENT-04",
+ "Description": "Ensure a central agent registry exists to catalog all AI agents, their permissions, data access patterns, and operational boundaries for governance at scale.",
+ "Name": "Agent Registry and Catalog",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-AGENT-05",
+ "Description": "Ensure human-in-the-loop approval is required for high-consequence agent actions such as financial transactions, data deletion, or privilege changes.",
+ "Name": "Human Approval for Critical Agent Actions",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Agent Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-ML-01",
+ "Description": "Ensure SageMaker models have network isolation enabled to prevent models from making unauthorized network calls during inference.",
+ "Name": "ML Model Network Isolation",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "ML Platform Security",
+ "Service": "sagemaker",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "sagemaker_models_network_isolation_enabled",
+ "sagemaker_models_vpc_settings_configured"
+ ]
+ },
+ {
+ "Id": "AISF-ML-02",
+ "Description": "Ensure SageMaker notebook instances are secured with encryption, VPC settings, no direct internet access, and root access disabled.",
+ "Name": "SageMaker Notebook Security",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "ML Platform Security",
+ "Service": "sagemaker",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "sagemaker_notebook_instance_encryption_enabled",
+ "sagemaker_notebook_instance_vpc_settings_configured",
+ "sagemaker_notebook_instance_without_direct_internet_access_configured",
+ "sagemaker_notebook_instance_root_access_disabled"
+ ]
+ },
+ {
+ "Id": "AISF-ML-03",
+ "Description": "Ensure SageMaker training jobs have network isolation, VPC configuration, inter-container traffic encryption, and volume encryption enabled to protect training data and model weights.",
+ "Name": "ML Training Job Security",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "ML Platform Security",
+ "Service": "sagemaker",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "sagemaker_training_jobs_network_isolation_enabled",
+ "sagemaker_training_jobs_vpc_settings_configured",
+ "sagemaker_training_jobs_intercontainer_encryption_enabled",
+ "sagemaker_training_jobs_volume_and_output_encryption_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-ML-04",
+ "Description": "Ensure SageMaker Model Registry is in use with approved model packages and SSO authentication is configured for SageMaker domains.",
+ "Name": "Model Governance and Registry",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "ML Platform Security",
+ "Service": "sagemaker",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "sagemaker_models_registry_in_use",
+ "sagemaker_domain_sso_configured"
+ ]
+ },
+ {
+ "Id": "AISF-ML-05",
+ "Description": "Ensure SageMaker Model Monitor is configured for continuous model quality and bias monitoring, and SageMaker Clarify is used for bias detection in AI/ML workloads.",
+ "Name": "Model Monitoring and Bias Detection",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "ML Platform Security",
+ "Service": "sagemaker",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-DETECT-01",
+ "Description": "Ensure CloudTrail is enabled in all regions with multi-region logging, management event recording, log file validation, and CloudWatch integration for comprehensive AI workload audit trails.",
+ "Name": "Comprehensive Audit Logging",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "Audit Logging",
+ "Service": "cloudtrail",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "cloudtrail_multi_region_enabled",
+ "cloudtrail_multi_region_enabled_logging_management_events",
+ "cloudtrail_log_file_validation_enabled",
+ "cloudtrail_cloudwatch_logging_enabled",
+ "cloudtrail_kms_encryption_enabled",
+ "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
+ "cloudtrail_logs_s3_bucket_access_logging_enabled",
+ "cloudtrail_insights_exist"
+ ]
+ },
+ {
+ "Id": "AISF-DETECT-02",
+ "Description": "Ensure GuardDuty is enabled across all regions with delegated admin, S3 protection, EKS monitoring, Lambda protection, and malware protection to detect AI-specific threat patterns.",
+ "Name": "GuardDuty Threat Detection",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "Threat Detection",
+ "Service": "guardduty",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "guardduty_is_enabled",
+ "guardduty_no_high_severity_findings",
+ "guardduty_centrally_managed",
+ "guardduty_delegated_admin_enabled_all_regions",
+ "guardduty_s3_protection_enabled",
+ "guardduty_eks_audit_log_enabled",
+ "guardduty_eks_runtime_monitoring_enabled",
+ "guardduty_lambda_protection_enabled",
+ "guardduty_rds_protection_enabled",
+ "guardduty_ec2_malware_protection_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_delegated_admin_enabled_all_regions",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "Id": "AISF-DETECT-03",
+ "Description": "Ensure CloudTrail-based threat detection is monitoring for LLM jacking, privilege escalation, and enumeration activity that could indicate attacks against AI infrastructure.",
+ "Name": "AI-Specific Threat Detection",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "AI Threat Detection",
+ "Service": "cloudtrail",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "cloudtrail_threat_detection_llm_jacking",
+ "cloudtrail_threat_detection_privilege_escalation",
+ "cloudtrail_threat_detection_enumeration"
+ ]
+ },
+ {
+ "Id": "AISF-DETECT-04",
+ "Description": "Ensure Security Hub is enabled with standards and integrations configured to aggregate and prioritize security findings across all AI workload services.",
+ "Name": "Security Hub Centralized Findings",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "Security Aggregation",
+ "Service": "securityhub",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "Id": "AISF-DETECT-05",
+ "Description": "Ensure CloudWatch metric filters and alarms are configured for critical security events including IAM policy changes, unauthorized API calls, console sign-in without MFA, KMS key deletion, and network changes.",
+ "Name": "Security Event Alerting",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "Security Alerting",
+ "Service": "cloudwatch",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "cloudwatch_log_metric_filter_policy_changes",
+ "cloudwatch_log_metric_filter_unauthorized_api_calls",
+ "cloudwatch_log_metric_filter_sign_in_without_mfa",
+ "cloudwatch_log_metric_filter_root_usage",
+ "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk",
+ "cloudwatch_log_metric_filter_security_group_changes",
+ "cloudwatch_changes_to_network_acls_alarm_configured",
+ "cloudwatch_changes_to_vpcs_alarm_configured",
+ "cloudwatch_log_metric_filter_authentication_failures",
+ "cloudwatch_log_metric_filter_aws_organizations_changes"
+ ]
+ },
+ {
+ "Id": "AISF-DETECT-06",
+ "Description": "Ensure Amazon Detective is enabled for AI security incident investigation, providing full decision chain reconstruction from prompt to data access to action.",
+ "Name": "AI Incident Investigation",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "Incident Investigation",
+ "Service": "detective",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-DETECT-07",
+ "Description": "Ensure GuardDuty Extended Threat Detection is enabled for AI-specific patterns including anomalous Bedrock API usage, model access from unusual locations, and potential data exfiltration through AI channels.",
+ "Name": "GuardDuty AI Threat Patterns",
+ "Attributes": [
+ {
+ "Section": "Threat Detection and Monitoring",
+ "SubSection": "AI Threat Detection",
+ "Service": "guardduty",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-GOV-01",
+ "Description": "Ensure AWS Config recorder is enabled in all regions to continuously monitor and record AI resource configurations, detect drift, and enforce compliance rules.",
+ "Name": "Configuration Compliance Monitoring",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "Configuration Management",
+ "Service": "config",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "config_recorder_all_regions_enabled",
+ "config_recorder_using_aws_service_role"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "Id": "AISF-GOV-02",
+ "Description": "Ensure the AWS account is part of an AWS Organization with proper governance controls including SCPs to restrict operations to approved regions and delegated administrators are trusted.",
+ "Name": "Organization Governance",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "Account Governance",
+ "Service": "organizations",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "organizations_account_part_of_organizations",
+ "organizations_scp_check_deny_regions",
+ "organizations_delegated_administrators",
+ "organizations_tags_policies_enabled_and_attached"
+ ]
+ },
+ {
+ "Id": "AISF-GOV-03",
+ "Description": "Ensure security contact information is registered and current for AI workload incident response communication.",
+ "Name": "Security Contact Information",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "Incident Response",
+ "Service": "account",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "account_maintain_current_contact_details",
+ "account_maintain_different_contact_details_to_security_billing_and_operations",
+ "account_security_contact_information_is_registered"
+ ]
+ },
+ {
+ "Id": "AISF-GOV-04",
+ "Description": "Ensure AWS Control Tower is enabled with landing zone configured to automate account governance and enforce security baselines across all accounts hosting AI workloads.",
+ "Name": "Control Tower Automated Governance",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "Automated Governance",
+ "Service": "controltower",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-GOV-05",
+ "Description": "Maintain an inventory of all AI workloads including approved and shadow AI usage. Document model selections, their governance requirements, and security evaluations.",
+ "Name": "AI Workload Inventory and Audit",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "AI Governance",
+ "Service": "multiple",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-GOV-06",
+ "Description": "Ensure AI-specific threat models are developed before production deployment, covering prompt injection, jailbreaks, data exfiltration, model poisoning, and adversarial attacks.",
+ "Name": "AI Threat Modeling",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "AI Governance",
+ "Service": "multiple",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-GOV-07",
+ "Description": "Ensure incident response plans include AI-specific scenarios covering prompt injection, model manipulation, data exfiltration through AI, LLM jacking, and agent scope violations.",
+ "Name": "AI Incident Response Planning",
+ "Attributes": [
+ {
+ "Section": "Governance and Compliance",
+ "SubSection": "Incident Response",
+ "Service": "multiple",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-RUNTIME-01",
+ "Description": "Ensure EKS clusters used for AI agent runtimes are properly secured with private endpoints, network policies, supported versions, control plane logging, and secrets encryption.",
+ "Name": "EKS Security for AI Runtimes",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Container Runtime Security",
+ "Service": "eks",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "eks_cluster_not_publicly_accessible",
+ "eks_cluster_private_nodes_enabled",
+ "eks_cluster_network_policy_enabled",
+ "eks_cluster_uses_a_supported_version",
+ "eks_control_plane_logging_all_types_enabled",
+ "eks_cluster_kms_cmk_encryption_in_secrets_enabled",
+ "eks_cluster_deletion_protection_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-RUNTIME-02",
+ "Description": "Ensure ECS tasks used for AI workloads have no public IPs, no privileged containers, read-only root filesystems, logging enabled, and no secrets in environment variables.",
+ "Name": "ECS Security for AI Workloads",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Container Runtime Security",
+ "Service": "ecs",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "ecs_service_no_assign_public_ip",
+ "ecs_task_set_no_assign_public_ip",
+ "ecs_task_definitions_no_privileged_containers",
+ "ecs_task_definitions_containers_readonly_access",
+ "ecs_task_definitions_logging_enabled",
+ "ecs_task_definitions_no_environment_secrets",
+ "ecs_task_definitions_host_namespace_not_shared",
+ "ecs_cluster_container_insights_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-RUNTIME-03",
+ "Description": "Ensure Lambda functions used in AI architectures are deployed in VPCs, not publicly accessible, use supported runtimes, have no secrets in code or variables, and use CMK-encrypted environment variables.",
+ "Name": "Lambda Security for AI Functions",
+ "Attributes": [
+ {
+ "Section": "Infrastructure Security",
+ "SubSection": "Serverless Runtime Security",
+ "Service": "awslambda",
+ "Type": "Automated"
+ }
+ ],
+ "Checks": [
+ "awslambda_function_inside_vpc",
+ "awslambda_function_not_publicly_accessible",
+ "awslambda_function_url_public",
+ "awslambda_function_no_secrets_in_code",
+ "awslambda_function_no_secrets_in_variables",
+ "awslambda_function_using_supported_runtimes",
+ "awslambda_function_env_vars_not_encrypted_with_cmk",
+ "awslambda_function_url_cors_policy",
+ "awslambda_function_invoke_api_operations_cloudtrail_logging_enabled"
+ ]
+ },
+ {
+ "Id": "AISF-MODEL-01",
+ "Description": "Perform security evaluation of foundation models before deployment, including assessment of input sanitization, access controls, bias audits, privacy disclosure, data poisoning resilience, adversarial resilience, and prompt injection defenses.",
+ "Name": "Model Security Evaluation",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Model Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ },
+ {
+ "Id": "AISF-MODEL-02",
+ "Description": "Ensure model selection is appropriate for the use case with CISO involvement in evaluation. Customer-facing agents require different model security profiles than internal summarization tools.",
+ "Name": "Model Selection Governance",
+ "Attributes": [
+ {
+ "Section": "AI Application Security",
+ "SubSection": "Model Governance",
+ "Service": "bedrock",
+ "Type": "Manual"
+ }
+ ],
+ "Checks": []
+ }
+ ]
+}
diff --git a/prowler/compliance/aws/aws_foundational_security_best_practices_aws.json b/prowler/compliance/aws/aws_foundational_security_best_practices_aws.json
index a64a421c8a..b58a74bcaa 100644
--- a/prowler/compliance/aws/aws_foundational_security_best_practices_aws.json
+++ b/prowler/compliance/aws/aws_foundational_security_best_practices_aws.json
@@ -20,6 +20,14 @@
"SectionDescription": "This section contains recommendations for configuring ACM resources.",
"Service": "ACM"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_expiration_check",
+ "ConfigKey": "days_to_expire_threshold",
+ "Operator": "gte",
+ "Value": 30
+ }
]
},
{
@@ -29,6 +37,17 @@
"Checks": [
"acm_certificates_with_secure_key_algorithms"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"ItemId": "ACM.2",
@@ -777,6 +796,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "Config.1",
@@ -892,6 +919,14 @@
"Checks": [
"documentdb_cluster_backup_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "documentdb_cluster_backup_enabled",
+ "ConfigKey": "minimum_backup_retention_period",
+ "Operator": "gte",
+ "Value": 7
+ }
+ ],
"Attributes": [
{
"ItemId": "DocumentDB.2",
@@ -1863,7 +1898,9 @@
"Id": "ELB.4",
"Name": "Application load balancers should be configured to drop HTTP headers",
"Description": "This control evaluates AWS Application Load Balancers (ALB) to ensure they are configured to drop invalid HTTP headers. The control fails if the value of routing.http.drop_invalid_header_fields.enabled is set to false. By default, ALBs are not configured to drop invalid HTTP header values. Removing these header values prevents HTTP desync attacks.",
- "Checks": [],
+ "Checks": [
+ "elbv2_alb_drop_invalid_header_fields_enabled"
+ ],
"Attributes": [
{
"ItemId": "ELB.4",
@@ -1957,6 +1994,14 @@
"SectionDescription": "This section contains recommendations for configuring ELB resources.",
"Service": "ELB"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "elb_is_in_multiple_az",
+ "ConfigKey": "elb_min_azs",
+ "Operator": "gte",
+ "Value": 2
+ }
]
},
{
@@ -1991,6 +2036,14 @@
"SectionDescription": "This section contains recommendations for configuring ELB resources.",
"Service": "ELB"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "elbv2_is_in_multiple_az",
+ "ConfigKey": "elbv2_min_azs",
+ "Operator": "gte",
+ "Value": 2
+ }
]
},
{
@@ -2368,6 +2421,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "GuardDuty.1",
@@ -2545,6 +2606,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
+ ],
"Attributes": [
{
"ItemId": "IAM.8",
@@ -2633,6 +2708,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"ItemId": "IAM.22",
@@ -2789,6 +2878,40 @@
"SectionDescription": "This section contains recommendations for configuring Lambda resources.",
"Service": "Lambda"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "awslambda_function_using_supported_runtimes",
+ "ConfigKey": "obsolete_lambda_runtimes",
+ "Operator": "superset",
+ "Value": [
+ "java8",
+ "go1.x",
+ "provided",
+ "python3.6",
+ "python2.7",
+ "python3.7",
+ "python3.8",
+ "nodejs4.3",
+ "nodejs4.3-edge",
+ "nodejs6.10",
+ "nodejs",
+ "nodejs8.10",
+ "nodejs10.x",
+ "nodejs12.x",
+ "nodejs14.x",
+ "nodejs16.x",
+ "dotnet5.0",
+ "dotnet6",
+ "dotnet7",
+ "dotnetcore1.0",
+ "dotnetcore2.0",
+ "dotnetcore2.1",
+ "dotnetcore3.1",
+ "ruby2.5",
+ "ruby2.7"
+ ]
+ }
]
},
{
@@ -2949,6 +3072,14 @@
"Checks": [
"neptune_cluster_backup_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "neptune_cluster_backup_enabled",
+ "ConfigKey": "minimum_backup_retention_period",
+ "Operator": "gte",
+ "Value": 7
+ }
+ ],
"Attributes": [
{
"ItemId": "Neptune.5",
diff --git a/prowler/compliance/aws/aws_foundational_technical_review_aws.json b/prowler/compliance/aws/aws_foundational_technical_review_aws.json
index 691a8ba7f1..9d8e3cfdc8 100644
--- a/prowler/compliance/aws/aws_foundational_technical_review_aws.json
+++ b/prowler/compliance/aws/aws_foundational_technical_review_aws.json
@@ -176,6 +176,14 @@
"iam_user_with_temporary_credentials",
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/aws_well_architected_framework_security_pillar_aws.json b/prowler/compliance/aws/aws_well_architected_framework_security_pillar_aws.json
index 94c50eb68a..9dd009afb3 100644
--- a/prowler/compliance/aws/aws_well_architected_framework_security_pillar_aws.json
+++ b/prowler/compliance/aws/aws_well_architected_framework_security_pillar_aws.json
@@ -585,6 +585,14 @@
"cloudtrail_multi_region_enabled",
"vpc_flow_logs_enabled",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -646,6 +654,20 @@
"guardduty_no_high_severity_findings",
"macie_is_enabled",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -778,6 +800,14 @@
"guardduty_is_enabled",
"vpc_flow_logs_enabled",
"apigateway_restapi_authorizers_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1151,6 +1181,10 @@
"elb_insecure_ssl_ciphers",
"elb_ssl_listeners",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_ssl_listeners",
"s3_bucket_secure_transport_policy"
]
diff --git a/prowler/compliance/aws/c5_aws.json b/prowler/compliance/aws/c5_aws.json
index 8847469154..269a5ce308 100644
--- a/prowler/compliance/aws/c5_aws.json
+++ b/prowler/compliance/aws/c5_aws.json
@@ -382,6 +382,14 @@
"cloudtrail_multi_region_enabled",
"config_recorder_all_regions_enabled",
"s3_multi_region_access_point_public_access_block"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2234,6 +2242,14 @@
"vpc_different_regions",
"autoscaling_group_multiple_az",
"storagegateway_gateway_fault_tolerant"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2261,6 +2277,14 @@
"organizations_scp_check_deny_regions",
"s3_multi_region_access_point_public_access_block",
"vpc_different_regions"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2308,6 +2332,14 @@
"organizations_scp_check_deny_regions",
"s3_multi_region_access_point_public_access_block",
"vpc_different_regions"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2978,6 +3010,14 @@
"guardduty_is_enabled",
"athena_workgroup_enforce_configuration",
"shield_advanced_protection_in_global_accelerators"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -3481,6 +3521,14 @@
"cloudtrail_cloudwatch_logging_enabled",
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4299,6 +4347,14 @@
"guardduty_no_high_severity_findings",
"guardduty_rds_protection_enabled",
"guardduty_s3_protection_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4920,6 +4976,17 @@
"elbv2_nlb_tls_termination_enabled",
"transfer_server_in_transit_encryption_enabled",
"kafka_cluster_mutual_tls_authentication_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -4946,6 +5013,17 @@
"elbv2_nlb_tls_termination_enabled",
"transfer_server_in_transit_encryption_enabled",
"kafka_cluster_mutual_tls_authentication_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -5220,6 +5298,14 @@
"rds_instance_default_admin",
"accessanalyzer_enabled",
"efs_access_point_enforce_user_identity"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5737,6 +5823,14 @@
"Checks": [
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6100,6 +6194,17 @@
"cloudfront_distributions_origin_traffic_encrypted",
"glue_development_endpoints_job_bookmark_encryption_enabled",
"cloudtrail_kms_encryption_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6196,6 +6301,17 @@
"elb_ssl_listeners_use_acm_certificate",
"iam_no_expired_server_certificates_stored",
"rds_instance_certificate_expiration"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6307,6 +6423,17 @@
"elb_ssl_listeners_use_acm_certificate",
"iam_no_expired_server_certificates_stored",
"rds_instance_certificate_expiration"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6393,6 +6520,14 @@
"sns_topics_not_publicly_accessible",
"sqs_queues_not_publicly_accessible",
"vpc_peering_routing_tables_with_least_privilege"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6412,6 +6547,14 @@
"ec2_instance_profile_attached",
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6587,6 +6730,17 @@
"kms_cmk_not_multi_region",
"kms_key_not_publicly_accessible",
"ec2_ebs_volume_encryption"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6809,6 +6963,17 @@
"secretsmanager_not_publicly_accessible",
"secretsmanager_secret_rotated_periodically",
"secretsmanager_secret_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6842,6 +7007,17 @@
],
"Checks": [
"acm_certificates_with_secure_key_algorithms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6915,6 +7091,17 @@
"secretsmanager_secret_rotated_periodically",
"secretsmanager_secret_unused",
"acm_certificates_with_secure_key_algorithms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -6937,6 +7124,17 @@
"secretsmanager_secret_rotated_periodically",
"secretsmanager_secret_unused",
"acm_certificates_with_secure_key_algorithms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -8042,6 +8240,14 @@
"cloudtrail_multi_region_enabled",
"cloudtrail_multi_region_enabled_logging_management_events",
"cloudtrail_log_file_validation_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -8810,6 +9016,14 @@
"guardduty_is_enabled",
"cloudtrail_log_file_validation_enabled",
"ssmincidents_enabled_with_plans"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -9732,6 +9946,14 @@
"accessanalyzer_enabled_without_findings",
"cloudfront_distributions_s3_origin_access_control",
"cloudtrail_logs_s3_bucket_access_logging_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -10367,6 +10589,14 @@
"Checks": [
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -10457,6 +10687,14 @@
"ec2_instance_profile_attached",
"iam_role_cross_account_readonlyaccess_policy",
"iam_securityaudit_role_created"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/ccc_aws.json b/prowler/compliance/aws/ccc_aws.json
index d1a20ee3d0..ef31bfe1ea 100644
--- a/prowler/compliance/aws/ccc_aws.json
+++ b/prowler/compliance/aws/ccc_aws.json
@@ -49,6 +49,10 @@
"elb_insecure_ssl_ciphers",
"elb_ssl_listeners",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_ssl_listeners",
"elbv2_nlb_tls_termination_enabled",
"s3_bucket_secure_transport_policy",
@@ -272,6 +276,17 @@
"acm_certificates_expiration_check",
"acm_certificates_with_secure_key_algorithms",
"acm_certificates_transparency_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -791,6 +806,17 @@
],
"Checks": [
"acm_certificates_with_secure_key_algorithms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -1501,6 +1527,14 @@
"iam_policy_no_full_access_to_kms",
"iam_policy_no_full_access_to_cloudtrail",
"iam_policy_attached_only_to_group_or_roles"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1663,6 +1697,14 @@
"cloudwatch_changes_to_network_route_tables_alarm_configured",
"cloudwatch_changes_to_vpcs_alarm_configured",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1788,6 +1830,14 @@
"cloudtrail_threat_detection_enumeration",
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4308,6 +4358,14 @@
],
"Checks": [
"acm_certificates_expiration_check"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_expiration_check",
+ "ConfigKey": "days_to_expire_threshold",
+ "Operator": "gte",
+ "Value": 30
+ }
]
},
{
@@ -6173,6 +6231,20 @@
"Checks": [
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -6269,6 +6341,14 @@
"cloudwatch_log_metric_filter_root_usage",
"cloudwatch_log_metric_filter_sign_in_without_mfa",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6371,6 +6451,14 @@
"Checks": [
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/cis_1.4_aws.json b/prowler/compliance/aws/cis_1.4_aws.json
index 3efc29fd5b..b373a04665 100644
--- a/prowler/compliance/aws/cis_1.4_aws.json
+++ b/prowler/compliance/aws/cis_1.4_aws.json
@@ -75,6 +75,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -265,6 +279,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -736,6 +758,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
diff --git a/prowler/compliance/aws/cis_1.5_aws.json b/prowler/compliance/aws/cis_1.5_aws.json
index f7307bb7f4..6a60d786a2 100644
--- a/prowler/compliance/aws/cis_1.5_aws.json
+++ b/prowler/compliance/aws/cis_1.5_aws.json
@@ -75,6 +75,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -265,6 +279,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -802,6 +824,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
@@ -1054,6 +1084,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Monitoring",
diff --git a/prowler/compliance/aws/cis_2.0_aws.json b/prowler/compliance/aws/cis_2.0_aws.json
index 4f8c4b2c23..e255bd43e1 100644
--- a/prowler/compliance/aws/cis_2.0_aws.json
+++ b/prowler/compliance/aws/cis_2.0_aws.json
@@ -75,6 +75,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -265,6 +279,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -802,6 +824,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
@@ -1054,6 +1084,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Monitoring",
diff --git a/prowler/compliance/aws/cis_3.0_aws.json b/prowler/compliance/aws/cis_3.0_aws.json
index dd4c75a2f7..5540bc40cf 100644
--- a/prowler/compliance/aws/cis_3.0_aws.json
+++ b/prowler/compliance/aws/cis_3.0_aws.json
@@ -75,6 +75,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -265,6 +279,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -756,6 +778,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
@@ -1008,6 +1038,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Monitoring",
diff --git a/prowler/compliance/aws/cis_4.0_aws.json b/prowler/compliance/aws/cis_4.0_aws.json
index 0c40f8ac09..c8787ef409 100644
--- a/prowler/compliance/aws/cis_4.0_aws.json
+++ b/prowler/compliance/aws/cis_4.0_aws.json
@@ -254,6 +254,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -431,6 +445,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -750,6 +772,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
@@ -1234,6 +1264,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Monitoring",
diff --git a/prowler/compliance/aws/cis_5.0_aws.json b/prowler/compliance/aws/cis_5.0_aws.json
index e870878c6b..0c8d46e170 100644
--- a/prowler/compliance/aws/cis_5.0_aws.json
+++ b/prowler/compliance/aws/cis_5.0_aws.json
@@ -232,6 +232,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -409,6 +423,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "1 Identity and Access Management",
@@ -728,6 +750,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 Logging",
@@ -1212,6 +1242,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Monitoring",
diff --git a/prowler/compliance/aws/cis_6.0_aws.json b/prowler/compliance/aws/cis_6.0_aws.json
index 643c192b7b..7ad62a4b65 100644
--- a/prowler/compliance/aws/cis_6.0_aws.json
+++ b/prowler/compliance/aws/cis_6.0_aws.json
@@ -232,6 +232,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Section": "2 Identity and Access Management",
@@ -409,6 +423,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "2 Identity and Access Management",
@@ -728,6 +750,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "4 Logging",
@@ -1212,6 +1242,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "5 Monitoring",
diff --git a/prowler/compliance/aws/cis_7.0_aws.json b/prowler/compliance/aws/cis_7.0_aws.json
new file mode 100644
index 0000000000..a927c375bb
--- /dev/null
+++ b/prowler/compliance/aws/cis_7.0_aws.json
@@ -0,0 +1,1610 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS Amazon Web Services Foundations Benchmark v7.0.0",
+ "Version": "7.0",
+ "Provider": "AWS",
+ "Description": "The CIS Amazon Web Services Foundations Benchmark provides prescriptive guidance for configuring security options for a subset of Amazon Web Services with an emphasis on foundational, testable, and architecture agnostic settings.",
+ "Requirements": [
+ {
+ "Id": "2.1.1",
+ "Description": "Ensure centralized root access in AWS Organizations",
+ "Checks": [
+ "iam_root_credentials_management_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure centralized root access management is enabled to manage and secure root user credentials for member accounts in AWS Organizations. This allows the management account and an optional delegated administrator account to centrally delete, prevent recovery of, and if necessary, perform short-lived, scoped root-required actions in member accounts without maintaining long-term root user credentials in each account.",
+ "RationaleStatement": "The AWS account root user is a powerful, default administrative identity that is difficult to manage safely across many accounts. When each member account manages its own root credentials, organizations often end up with numerous long-lived root passwords, access keys, and MFA devices that are hard to inventory, rotate, and protect. Centralized root access management lets security teams remove or avoid creating root user credentials in member accounts, centrally review and manage any remaining root credentials, and perform necessary root-only tasks via short-term, task-scoped root sessions. This significantly reduces privileged credential sprawl, supports least privilege and dedicated administrator models, and improves visibility and auditability of root-level activity across the organization.",
+ "ImpactStatement": "Enabling centralized root access management changes how root user access is obtained and used in member accounts, but it does not automatically remove existing root credentials. Organizations must plan when and how to delete or disable any existing root passwords, access keys, signing certificates, and MFA devices in member accounts and update any workflows that still rely on direct root sign-in. Security and operations teams will need to use centrally initiated, short-lived root sessions for exceptional tasks that truly require root. This may require procedural changes and additional training, but it significantly reduces long-lived privileged credential sprawl across the organization.",
+ "RemediationProcedure": "1. Sign in to the AWS Management Console with the management account. 2. In the console search bar, type Organizations and open AWS Organizations. - On the Overview page, confirm that an Organization exists and that this account is listed as the Management account. 3. In AWS Organizations, choose Services. Locate AWS Identity and Access Management in the list and, if it is not already enabled, choose Enable trusted access and confirm. - This allows IAM to integrate with AWS Organizations to manage root access centrally. 4. In the console search bar, type IAM and open IAM. In the left navigation pane, choose Root access management. If you see Root access management is disabled, choose Enable. - In the enable dialog, confirm that you want to - \"Root credentials management\" and if desired - \"Privileged root actions in member accounts\" - In the Delegated administrator field, enter the account ID of the account that will manage root user access and take privileged actions on member accounts. AWS recommends using an account intended for security or management purposes, not a general workload account. - When you enable centralized root access in the console, IAM also enables trusted access for IAM in AWS Organizations if it isn't already enabled. - Choose Enable to save the configuration.",
+ "AuditProcedure": "1. Sign in to the AWS Management Console with the management account. 2. In the console search bar, type Organizations and open AWS Organizations. - On the Overview page, confirm that an Organization exists and that this account is listed as the Management account. 3. In AWS Organizations, choose Services. - Confirm that AWS Identity and Access Management appears in the list of services with trusted access enabled. 4. In the console search bar, type IAM and open IAM. In the left navigation pane, choose Root access management. Check the status banner. - If you see that Root access management is enabled and the feature card shows that root credentials management is turned on for member accounts, the organization has centralized root access management enabled. - If you see Root access management is disabled with an option to Enable, centralized root access is not yet enabled. 5. (Optional) On the same Root access management page, review the Delegated administrator information (if shown). - Confirm that the delegated account (if present) is a security or management-focused account, not a general workload account.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.2",
+ "Description": "Ensure authorization guardrails for all AWS Organization accounts",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that one or more baseline authorization policies such as Service Control Policies (SCPs) and/or Resource Control Policies (RCPs) are attached to all member accounts in AWS Organizations in accordance with organizational security requirements. Authorization policies act as preventive permission guardrails: SCPs define the maximum available permissions for IAM principals within accounts, while RCPs define the maximum available permissions for resources within accounts. These policies can enforce security invariants such as preventing disabling of key security services, restricting use of unapproved AWS Regions, or blocking external access to sensitive resources.",
+ "RationaleStatement": "Authorization policies do not grant permissions but instead set organization-wide limits on what actions principals can perform (SCPs) and what access can be granted to resources (RCPs), regardless of local IAM or resource-based policies. Without baseline guardrail authorization policies, each account can grant excessive or inconsistent permissions that disable logging, weaken security services, allow use of unapproved Regions and services, or permit unintended external access to resources. Attaching standard authorization policies to all member accounts enforces preventive, centralized control over high-risk actions and access patterns, supports least-privilege and role-based access control at scale, and helps ensure that all accounts and resources operate within the organization's defined security baseline.",
+ "ImpactStatement": "Enforcing baseline authorization policies for all member accounts can initially block some existing patterns, such as use of unapproved Regions, disabling security services, or granting broader permissions than the guardrails allow. Teams may need to adjust IAM policies, deployment pipelines, and exception processes so legitimate use cases remain possible within the new guardrails. This can introduce short-term operational overhead and require careful testing, especially when attaching new policies at the root or OU level.",
+ "RemediationProcedure": "Design or confirm baseline guardrail SCPs. 1. From the AWS Organizations console, go to Policies → Service control policies. - If you already have standard guardrail SCPs that implement your security baseline, note their names. - If you do not have such policies, choose Create policy and create at least one baseline guardrail SCP that encodes non-negotiable security requirements. 2. Do the same step as above but for RCPs if needed. From the AWS Organizations console, go to Policies → Resource control policies. 3. Attach guardrail authorization policies to the root and/or OUs. In AWS Organizations, choose AWS accounts, then select the Root of the organization. - Go to the Policies tab, then within section for Service control policies, choose Attach, and select the baseline guardrail SCP(s) you identified or created in step 1. - If using RCPs, then within section for Resource control policies, choose Attach, and select the baseline guardrail RCP(s) you identified or created in step 2. - If your design uses different guardrails per OU (for example, stricter policies for production OU), select each OU in turn and attach the appropriate guardrail SCPs and RCPs to those OUs. - AWS recommends testing authorization policies in a staging OU before attaching them broadly to the root to avoid unintended service disruption.",
+ "AuditProcedure": "Pre-requisite: you must run these CLI commands in the management account for the AWS Organization. 1. Before auditing, document or confirm your organization's baseline guardrail requirements. Common examples include: - Prevent disabling CloudTrail, AWS Config, GuardDuty, or Security Hub - Restrict usage to approved AWS Regions only - Protect central security or logging roles from modification - Deny external principal access to sensitive resources 2. List all SCPs and RCPs in the organization: ``` aws organizations list-policies --filter SERVICE_CONTROL_POLICY aws organizations list-policies --filter RESOURCE_CONTROL_POLICY ``` This returns a list of SCP/RCP policy IDs and names. 3. For each SCP/RCP, retrieve and review the policy document to determine if it implements your baseline guardrail requirements: ``` aws organizations describe-policy --policy-id <policy-id> ``` Review the `Content` field in the output to confirm the policy enforces organizational security requirements. If no SCPs/RCPs exist that implement your documented baseline guardrail requirements, note this as a gap and proceed to remediation. 4. List all accounts in the organization and note the account IDs: ``` aws organizations list-accounts --query 'Accounts[?Status==`ACTIVE`].[Id,Name]' --output table ``` 5. For each baseline guardrail Authorization policy identified in Step 2, list the accounts and OUs to which it is attached: ``` aws organizations list-targets-for-policy --policy-id <policy-id> ``` The output shows `TargetId` values representing accounts, OUs, or the root. 6. Compare the list of attached targets to your full account list. - If the policy is attached to the root, all accounts in the organization inherit it and this policy passes for coverage. - If the policy is attached to specific OUs, verify that all active member accounts belong to those OUs. - If the policy is attached to individual accounts, verify that all active member accounts are included. The environment passes this recommendation if: - All baseline guardrail authorization policies required by organizational security requirements exist. - Each baseline guardrail authorization policy is attached to all active member accounts either directly or via OU/root inheritance.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.3",
+ "Description": "Ensure Organizations management account is not used for workloads",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the AWS Organizations management account is used only for organizational governance tasks and does not host production workloads, applications, or business data. The management account is the most privileged account in an AWS Organization and performs sensitive administrative functions such as creating and managing member accounts, applying service control policies (SCPs), and managing consolidated billing. Workloads, applications, and associated data should be deployed in dedicated member accounts, not in the management account.",
+ "RationaleStatement": "The management account has unique privileges that cannot be restricted by SCPs, making it the highest-risk account in an organization. Deploying workloads or storing business data in the management account increases the attack surface and blast radius of a compromise. If a workload vulnerability or misconfiguration occurs in the management account, it could grant attackers access to organization-wide administrative capabilities.",
+ "ImpactStatement": "Restricting the management account to governance-only use may require creating new member accounts, redesigning existing account boundaries, and migrating workloads and data out of the management account. This can introduce short-term complexity and operational overhead. However, it reduces the blast radius of a compromise, simplifies security controls in the most privileged account, and aligns the environment with AWS multi-account and workload-isolation best practices.",
+ "RemediationProcedure": "1. Inventory all workload resources currently in the management account (compute, storage, databases, application services). 2. For each class of workload resource (for example, production, non-production, shared services), create or confirm dedicated member accounts within the organization and place them into the appropriate OUs. 3. For each workload resource, design a migration plan to the appropriate member account. - Execute the migrations in phases, starting with lower-risk environments (for example, development/test) before production. 4. Review and adjust IAM roles and permissions in the management account so that only personnel responsible for organization governance and security have access 5. Update architecture diagrams, runbooks, and onboarding processes to state that new workloads must be deployed only into designated workload accounts, not the management account.",
+ "AuditProcedure": "1. Confirm which AWS account is the management account for the organization (for example, via AWS Organizations \"Overview\" page or organizational documentation). 2. Ensure you have read-only access to review resources in this account. 3. Use your organization's standard discovery methods (for example, AWS Config, CMDB/asset inventory, or CSPM) to obtain a list of services and resources running in the management account. - At a minimum, identify compute, storage, database, and application services (for example, EC2, Lambda, ECS, S3, RDS, DynamoDB, API Gateway, load balancers). 4. For each identified resource, determine whether it is: - Governance/security: resources that support centralized management, logging, audit, or security (for example, org-wide CloudTrail, Config aggregator, Security Hub or GuardDuty delegated admin, billing/cost tooling). - Workload/business: resources that support business applications, production or non-production workloads, or customer-facing systems. 5. If any workload/business resources are present in the management account, record this as a gap and document the affected services and resource types",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.4",
+ "Description": "Ensure Organizational Units are structured by environment and sensitivity",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that AWS Organizations Organizational Units (OUs) are structured primarily by environment (for example, production, non-production, sandbox) and sensitivity (for example, security, logging, shared services, regulated workloads), rather than mirroring the corporate org chart. OUs should group accounts that share similar security requirements and controls so that appropriate authorization policies and other guardrails can be applied consistently at the OU level.",
+ "RationaleStatement": "A clear OU structure based on environment and sensitivity makes it easier to apply consistent guardrails and centralized security controls to accounts that have similar risk profiles and compliance needs. Poorly defined or ad-hoc OU structures complicate policy management, increase the chance of misapplied controls, and can lead to mixing workloads with different data sensitivities under the same set of controls.",
+ "ImpactStatement": "Restructuring OUs by environment and sensitivity can require moving accounts, changing inherited policies, and updating automation that assumes existing OU paths. This may introduce short-term operational overhead, including policy revalidation, testing of workloads under new guardrails, and coordination with application and platform teams to avoid unintended service disruption.",
+ "RemediationProcedure": "1. Work with security, platform, and application teams to agree on a small set of top-level OUs such as: - Security / Management - Shared Services / Infrastructure - Prod - Non-Prod (dev, test, staging) - You may also define dedicated OUs for highly regulated workloads. 2. In the AWS Organizations console (management account), navigate to AWS Accounts. Under the root, create the agreed top-level OUs. If needed, create child OUs under these. 3. Export or list all existing accounts and their current OUs. Create a simple mapping from each account to its target OU based on environment and sensitivity. 4. In the AWS Organizations console (management account), navigate to AWS Accounts. Move accounts into the new environment/sensitivity-based OUs according to your mapping. - Start with low-risk accounts (for example, sandbox and non-production) to validate effects of inherited policies and guardrails before moving production and high-sensitivity accounts. 5. After accounts have been moved, remove old OUs that no longer reflect the target structure. - Ensure no active accounts remain directly under the root unless explicitly justified and documented. 6. Update architecture docs, onboarding runbooks, and account request processes to require new accounts to be created in the correct OU based on environment and sensitivity.",
+ "AuditProcedure": "1. From the management account, use AWS Organizations console to obtain: - The full OU hierarchy (root, top-level and child OUs). - The list of accounts in each OU. 2. Review top-level and key OUs and determine whether they are clearly aligned to: - Environment (for example, production, non-production, sandbox). - Sensitivity/function (for example, security, logging, shared services, regulated). - Note any OUs whose purpose is unclear or that appear to be organized mainly by department or owner rather than environment/sensitivity. 3. For each environment/sensitivity OU, select a sample of accounts and verify that their primary workloads match the OU's stated purpose. - Note any accounts that mix production and non-production workloads in the same OU when separate OUs are defined. - Note any accounts that place highly sensitive or regulated workloads in OUs that are intended for lower-sensitivity use.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.5",
+ "Description": "Ensure delegated admin manages AWS Organizations policies",
+ "Checks": [
+ "organizations_delegated_administrators"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that a dedicated member account is configured as a delegated administrator for AWS Organizations to manage organization policies (SCPs, RCPs, tag policies, backup policies, AI opt-out policies) and other Organizations features, instead of performing these tasks directly from the management account. The delegated administrator for AWS Organizations is configured via a resource-based delegation policy in the management account, which grants specific member accounts limited permissions to perform Organizations policy and account management actions across the organization. This allows policy management, OU operations, and other governance tasks to be handled from purpose-built accounts without requiring broad access to the management account.",
+ "RationaleStatement": "The management account has unique and high privileges to manage AWS Organizations (for example, creating/deleting accounts, managing org structures) and is not subject to guardrails like SCPs. Without a delegated administrator for Organizations, all policy management, OU changes, and account governance must be performed directly from the management account. This results in concentrating operational activity in the most powerful account. Configuring a dedicated member account as a delegated administrator for Organizations policy management distributes these tasks to a purpose-built AWS account that can be protected by SCPs and other controls, reduces the number of users and roles that need management-account access, and supports separation of duties while maintaining centralized control over organization-wide features.",
+ "ImpactStatement": "Configuring a delegated administrator for AWS Organizations requires creating or identifying a dedicated member account for policy management and granting it specific permissions via a resource-based delegation policy. Existing workflows, automation, and user access patterns that currently perform Organizations policy tasks directly from the management account must be updated to use the delegated account instead. This introduces short-term operational overhead and testing to ensure policy creation, attachment, and management continue to function correctly from the new account.",
+ "RemediationProcedure": "1. Identify a dedicated member account for governance/policy management (for example, create a new \"Policy Management\" account or use an existing Security account) 2. You must be in the management account with permissions to manage Organizations resource policies. Navigate to AWS Organizations console, then click on Settings and browse to \"Delegated administrator for AWS Organizations\" section. 3. If no policy exists, click on Delegate. If a policy exists, choose Edit policy. - In the policy editor, paste or construct a delegation policy statement mentioning the Principal as the AWS account Root which is being delegated access to, and the Actions with the list of least-privileged permissions that could be performed by the delegated AWS account. - Save and validate the delegation policy. 4. Sign in to the delegated administrator account and open the AWS Organizations console. - Confirm that policy management (Policies, Attach/Detach, etc.) is accessible and that users/roles in this account can perform Organizations tasks without management-account access. 5. Grant IAM roles/users in the delegated admin account only the permissions needed for Organizations policy management. 6. Update procedures so that routine Organizations policy tasks are performed from the delegated account, reserving the management account for tasks that only it can perform",
+ "AuditProcedure": "1. Sign in to the AWS Organizations console. From the AWS Accounts section, verify that this is the management account for the organization. 2. In the AWS Organizations console, navigate to Settings. Scroll to the Delegated administrator for AWS Organizations section 3. Review the delegation policy status: - If a delegation policy is configured and shows one or more member accounts registered to manage Organizations policies, proceed to step 4. - If no delegation policy is configured or the section shows No delegated administrator (or equivalent), the audit fails because Organizations management is performed directly from the management account. 4. In the Delegated administrator section, note the account IDs registered for Organizations policy management. Confirm that the delegated accounts are purpose-built governance, security, or policy management accounts, not general workload, sandbox, or development accounts. 5. View the delegation policy details to confirm it grants appropriate least-privilege permissions for policy types (for example, SCPs, tag policies, backup policies) and actions (CreatePolicy, AttachPolicy, UpdatePolicy, etc.).",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.6",
+ "Description": "Ensure delegated admins manage AWS Organizations-integrated services",
+ "Checks": [
+ "organizations_delegated_administrators"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that AWS services (such as AWS CloudTrail) which integrate with AWS Organizations and support delegated administration are managed through delegated administrator member accounts instead of directly from the Organizations management account. For each such service, the management account should enable trusted access and register a purpose-built member account as the delegated administrator, so that this account can perform service-level administration across all organization accounts.",
+ "RationaleStatement": "The management account has unique and high privileges to manage AWS Organizations (for example, creating/deleting accounts, managing org structures) and is not subject to guardrails like SCPs. Without delegated administrators, organization-wide security, logging, and management services must be operated directly from the management account, concentrating operational activity and credentials in the most privileged account in the organization. Registering member accounts as delegated administrators for AWS services distributes service-specific administration to dedicated security, logging, or operations accounts that can be restricted by SCPs, monitored like other workload accounts, and aligned with team responsibilities, while reducing day-to-day use of the management account.",
+ "ImpactStatement": "Configuring a delegated administrator for AWS Services that integrate with AWS Organizations requires creating or identifying a dedicated member account for policy management and granting it specific permissions. Existing workflows, automation, and user access patterns that currently perform tasks directly from the management account must be updated to use the delegated account instead. This introduces short-term operational overhead and testing to ensure policy creation, attachment, and management continue to function correctly from the new account.",
+ "RemediationProcedure": "Note: This remediation section uses AWS CloudTrail as a concrete example. You must perform similar procedure for all other AWS services that integrate with AWS Organizations and support delegated administration that are in use in your environment. 1. In the management account, verify that trusted access for CloudTrail is enabled in AWS Organizations (AWS Organizations → Services). 2. In the management account CloudTrail console, choose Settings in the left navigation pane. Scroll to Organization delegated administrators. 3. Click on \"Register administrator\" - Enter the account ID of the designated Logging or Security account. - Click on Register administrator. CloudTrail will automatically create the necessary service-linked roles and register the account. 4. In the delegated administrator account, open the CloudTrail console and confirm that the organization trail is visible and administrative actions are accessible. 5. Update operational runbooks so that routine CloudTrail administration is performed from the delegated admin account, not the management account.",
+ "AuditProcedure": "Note: This audit uses AWS CloudTrail as a concrete example. You must perform similar audits for all other AWS services that integrate with AWS Organizations and support delegated administration that are in use in your environment. 1. Sign in to the management account and open the CloudTrail console. 2. In the left navigation pane, choose Trails. - Verify that there is at least one organization trail (trail with Apply trail to all accounts in my organization or equivalent setting enabled) - If CloudTrail is only configured as single-account trails and no organization trail is in use, note that delegated admin for CloudTrail is not in scope and this recommendation is not applicable for CloudTrail in this environment. 3. In the same management account CloudTrail console, choose Settings in the left navigation pane, and scroll to the Organization delegated administrators section. 4. Verify the configuration for Organization delegated administrators: - Verify that at least one member account ID (not the management account) is listed as a delegated administrator for CloudTrail. - Verify that the account(s) are appropriate for security/logging operations (for example, a named Security or Logging account, not a sandbox or general workload account). - If the section shows \"No delegated administrators\" when an organization trail is in use, CloudTrail is effectively administered from the management account and this is a gap.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2",
+ "Description": "Maintain current AWS account contact details",
+ "Checks": [
+ "account_maintain_current_contact_details"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure contact email and telephone details for AWS accounts are current and map to more than one individual in your organization. An AWS account supports a number of contact details, and AWS will use these to contact the account owner if activity judged to be in breach of the Acceptable Use Policy or indicative of a likely security compromise is observed by the AWS Abuse team. Contact details should not be for a single individual, as circumstances may arise where that individual is unavailable. Email contact details should point to a mail alias which forwards email to multiple individuals within the organization; where feasible, phone contact details should point to a PABX hunt group or other call-forwarding system.",
+ "RationaleStatement": "If an AWS account is observed to be behaving in a prohibited or suspicious manner, AWS will attempt to contact the account owner by email and phone using the contact details listed. If this is unsuccessful and the account behavior needs urgent mitigation, proactive measures may be taken, including throttling of traffic between the account exhibiting suspicious behavior and the AWS API endpoints and the Internet. This will result in impaired service to and from the account in question, so it is in both the customers' and AWS's best interests that prompt contact can be established. This is best achieved by setting AWS account contact details to point to resources which have multiple individuals as recipients, such as email aliases and PABX hunt groups.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "This activity can only be performed via the AWS Console, with a user who has permission to read and write Billing information (aws-portal:\\*Billing). **From Console:** 1. Sign in to the AWS Management Console and open the `Billing and Cost Management` console at https://console.aws.amazon.com/billing/home#/. 2. On the navigation bar, choose your account name, and then choose `Account`. 3. On the `Account Settings` page, next to `Account Settings`, choose `Edit`. 4. Next to the field that you need to update, choose `Edit`. 5. After you have entered your changes, choose `Save changes`. 6. After you have made your changes, choose `Done`. 7. To edit your contact information, under `Contact Information`, choose `Edit`. 8. For the fields that you want to change, type your updated information, and then choose `Update`. **From Command Line:** 1. Run the following command: ``` aws account put-contact-information --contact-information '{\"AddressLine1\": \"<AddressLine 1>\", \"AddressLine2\": \"<AddressLine 2>\", \"City\": \"<City>\", \"CompanyName\": \"<Company Name>\", \"CountryCode\": \"<Country Code>\", \"FullName\": \"<Full Name>\", \"PhoneNumber\": \"<Phone Number>\", \"PostalCode\": \"<Postal Code>\", \"StateOrRegion\": \"<State or Region>\"}' ```",
+ "AuditProcedure": "This activity can only be performed via the AWS Console, with a user who has permission to read and write Billing information (aws-portal:\\*Billing). 1. Sign in to the AWS Management Console and open the `Billing and Cost Management` console at https://console.aws.amazon.com/billing/home#/. 2. On the navigation bar, choose your account name, and then choose `Account`. 3. On the `Account Settings` page, review and verify the current details. 4. Under `Contact Information`, review and verify the current details.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-account-payment.html#contact-info",
+ "DefaultValue": "By default, AWS account contact information (email and telephone) is set to the values provided at account creation. These usually reference a single individual rather than a shared alias or group contact."
+ }
+ ]
+ },
+ {
+ "Id": "2.3",
+ "Description": "Ensure security contact information is registered",
+ "Checks": [
+ "account_security_contact_information_is_registered"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "AWS provides customers with the option of specifying the contact information for account's security team. It is recommended that this information be provided.",
+ "RationaleStatement": "Specifying security-specific contact information will help ensure that security advisories sent by AWS reach the team in your organization that is best equipped to respond to them.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to establish security contact information: **From Console:** 1. Click on your account name at the top right corner of the console. 2. From the drop-down menu Click `My Account` 3. Scroll down to the `Alternate Contacts` section 4. Enter contact information in the `Security` section **From Command Line:** Run the following command with the following input parameters: --email-address, --name, and --phone-number. ``` aws account put-alternate-contact --alternate-contact-type SECURITY ``` **Note:** Consider specifying an internal email distribution list to ensure emails are regularly monitored by more than one individual.",
+ "AuditProcedure": "Perform the following to determine if security contact information is present: **From Console:** 1. Click on your account name at the top right corner of the console 2. From the drop-down menu Click `My Account` 3. Scroll down to the `Alternate Contacts` section 4. Ensure contact information is specified in the `Security` section **From Command Line:** 1. Run the following command: ``` aws account get-alternate-contact --alternate-contact-type SECURITY ``` 2. Ensure proper contact information is specified for the `Security` contact.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4",
+ "Description": "Ensure no 'root' user account access key exists",
+ "Checks": [
+ "iam_no_root_access_key"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The 'root' user account is the most privileged user in an AWS account. AWS Access Keys provide programmatic access to a given AWS account. It is recommended that all access keys associated with the 'root' user account be deleted.",
+ "RationaleStatement": "Deleting access keys associated with the 'root' user account limits vectors by which the account can be compromised. Additionally, deleting the 'root' access keys encourages the creation and use of role based accounts that are least privileged.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to delete active 'root' user access keys. **From Console:** 1. Sign in to the AWS Management Console as 'root' and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). 2. Click on `<root_account>` at the top right and select `My Security Credentials` from the drop down list. 3. On the pop out screen Click on `Continue to Security Credentials`. 4. Click on `Access Keys` (Access Key ID and Secret Access Key). 5. If there are active keys, under `Status`, click `Delete` (Note: Deleted keys cannot be recovered). Note: While a key can be made inactive, this inactive key will still show up in the CLI command from the audit procedure, and may lead to the root user being falsely flagged as being non-compliant.",
+ "AuditProcedure": "Perform the following to determine if the 'root' user account has access keys: **From Console:** 1. Login to the AWS Management Console. 2. Click `Services`. 3. Click `IAM`. 4. Click on `Credential Report`. 5. This will download a `.csv` file which contains credential usage for all IAM users within an AWS Account - open this file. 6. For the `<root_account>` user, ensure the `access_key_1_active` and `access_key_2_active` fields are set to `FALSE`. **From Command Line:** Run the following command: ``` aws iam get-account-summary | grep AccountAccessKeysPresent ``` If no 'root' access keys exist the output will show `AccountAccessKeysPresent: 0,`. If the output shows a 1, then 'root' keys exist and should be deleted.",
+ "AdditionalInformation": "- IAM User account root for us-gov cloud regions is not enabled by default. However, on request to AWS support enables 'root' access only through access-keys (CLI, API methods) for us-gov cloud region. - Implement regular checks and alerts for any creation of new root access keys to promptly address any unauthorized or accidental creation.",
+ "References": "http://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html:http://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html:http://docs.aws.amazon.com/IAM/latest/APIReference/API_GetAccountSummary.html:https://aws.amazon.com/blogs/security/an-easier-way-to-determine-the-presence-of-aws-account-access-keys/",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.5",
+ "Description": "Ensure MFA is enabled for the 'root' user account",
+ "Checks": [
+ "iam_root_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The 'root' user account is the most privileged user in an AWS account. Multi-factor Authentication (MFA) adds an extra layer of protection on top of a username and password. With MFA enabled, when a user signs in to an AWS website, they will be prompted for their username and password as well as for an authentication code from their AWS MFA device. **Note:** When virtual MFA is used for 'root' accounts, it is recommended that the device used is NOT a personal device, but rather a dedicated mobile device (tablet or phone) that is kept charged and secured, independent of any individual personal devices (non-personal virtual MFA). This lessens the risks of losing access to the MFA due to device loss, device trade-in, or if the individual owning the device is no longer employed at the company. Where an AWS Organization is using centralized root access, root credentials can be removed from member accounts. In that case it is neither possible nor necessary to configure root MFA in the member account.",
+ "RationaleStatement": "Enabling MFA provides increased security for console access as it requires the authenticating principal to possess a device that emits a time-sensitive key and have knowledge of a credential.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**Note:** To manage MFA devices for the 'root' AWS account, you must use your 'root' account credentials to sign in to AWS. You cannot manage MFA devices for the 'root' account using other credentials. Perform the following to establish MFA for the 'root' user account: 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). 2. Choose `Dashboard` , and under `Security Status` , expand `Activate MFA` on your root account. 3. Choose `Activate MFA` 4. In the wizard, choose `A virtual MFA` device and then choose `Next Step` . 5. IAM generates and displays configuration information for the virtual MFA device, including a QR code graphic. The graphic is a representation of the 'secret configuration key' that is available for manual entry on devices that do not support QR codes. 6. Open your virtual MFA application. (For a list of apps that you can use for hosting virtual MFA devices, see [Virtual MFA Applications](http://aws.amazon.com/iam/details/mfa/#Virtual_MFA_Applications).) If the virtual MFA application supports multiple accounts (multiple virtual MFA devices), choose the option to create a new account (a new virtual MFA device). 7. Determine whether the MFA app supports QR codes, and then do one of the following: - Use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to Scan code, and then use the device's camera to scan the code. - In the Manage MFA Device wizard, choose Show secret key for manual configuration, and then type the secret configuration key into your MFA application. When you are finished, the virtual MFA device starts generating one-time passwords. In the Manage MFA Device wizard, in the Authentication Code 1 box, type the one-time password that currently appears in the virtual MFA device. Wait up to 30 seconds for the device to generate a new one-time password. Then type the second one-time password into the Authentication Code 2 box. Choose Assign Virtual MFA.",
+ "AuditProcedure": "Perform the following to determine if the 'root' user account is enabled and has MFA setup: **From Console:** 1. Login to the AWS Management Console 2. Click `Services` 3. Click `IAM` 4. Click on `Credential Report` 5. This will download a `.csv` file which contains credential usage for all IAM users within an AWS Account - open this file 6. For the `<root_account>` user, ensure the `mfa_active` field is set to `TRUE` or the `password_enabled` field is set to `FALSE` **From Command Line:** 1. Run the following command: ``` aws iam get-account-summary | grep AccountMFAEnabled aws iam get-account-summary | grep AccountPasswordPresent ``` 2. Ensure the AccountMFAEnabled property is set to 1 or the AccountPasswordPresent property is set to 0",
+ "AdditionalInformation": "IAM User account root for us-gov cloud regions does not have console access. This recommendation is not applicable for us-gov cloud regions.",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#id_root-user_manage_mfa:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_enable_virtual.html#enable-virt-mfa-for-root:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-enable-root-access.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.6",
+ "Description": "Ensure hardware MFA is enabled for the 'root' user account",
+ "Checks": [
+ "iam_root_hardware_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "The 'root' user account is the most privileged user in an AWS account. MFA adds an extra layer of protection on top of a user name and password. With MFA enabled, when a user signs in to an AWS website, they will be prompted for their user name and password as well as for an authentication code from their AWS MFA device. For Level 2, it is recommended that the 'root' user account be protected with a hardware MFA. Where an AWS Organization is using centralized root access, root credentials can be removed from member accounts. In that case it is neither possible nor necessary to configure root MFA in the member account.",
+ "RationaleStatement": "A hardware MFA has a smaller attack surface than a virtual MFA. For example, a hardware MFA does not suffer the attack surface introduced by the mobile smartphone on which a virtual MFA resides. **Note**: Using hardware MFA for numerous AWS accounts may create a logistical device management issue. If this is the case, consider implementing this Level 2 recommendation selectively for the highest security AWS accounts, while applying the Level 1 recommendation to the remaining accounts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**Note:** To manage MFA devices for the AWS 'root' user account, you must use your 'root' account credentials to sign in to AWS. You cannot manage MFA devices for the 'root' account using other credentials. Perform the following to establish a hardware MFA for the 'root' user account: 1. Open the AWS Management Console and sign in using your root user credentials. 2. On the right side of the navigation bar, choose your account name, and choose Security credentials. 3. In the Multi-Factor Authentication (MFA) section, choose Assign MFA device. 4. In the wizard, type a Device name, choose Authenticator app, and then choose Next. IAM generates and displays configuration information for the virtual MFA device, including a QR code graphic. The graphic is a representation of the secret configuration key that is available for manual entry on devices that do not support QR codes. 5. Open the virtual MFA app on the device. If the virtual MFA app supports multiple virtual MFA devices or accounts, choose the option to create a new virtual MFA device or account. 6. The easiest way to configure the app is to use the app to scan the QR code. If you cannot scan the code, you can type the configuration information manually. The QR code and secret configuration key generated by IAM are tied to your AWS account. To use the QR code to configure the virtual MFA device, from the wizard, choose Show QR code. Then follow the app instructions for scanning the code. For example, you might need to choose the camera icon or choose a command like Scan account barcode, and then use the device's camera to scan the QR code. To manual entry secret key on devices, in the Set up device wizard, choose Show secret key, and then type the secret key into your MFA app. 7. In the wizard, in the MFA code 1 box, type the one-time password that currently appears in the virtual MFA device. Wait up to 30 seconds for the device to generate a new one-time password. Then type the second one-time password into the MFA code 2 box. Choose Add MFA. Remediation for this recommendation is not available through AWS CLI.",
+ "AuditProcedure": "Perform the following to determine if the 'root' user account has a hardware MFA setup: 1. Run the following command to determine if the 'root' account has MFA setup: ``` aws iam get-account-summary | grep \"AccountMFAEnabled\" aws iam get-account-summary | grep \"AccountPasswordPresent\" ``` The `AccountMFAEnabled` property is set to `1` will ensure that the 'root' user account has MFA (Virtual or Hardware) Enabled. `AccountPasswordPresent` set to `0` indicates that the `root` console credential has been removed. If `AccountMFAEnabled` property is set to `0` and `AccountPasswordPresent` is set to `1` the account is not compliant with this recommendation. 2. If `AccountMFAEnabled` property is set to `1`, determine 'root' account has Hardware MFA enabled. Run the following command to list all virtual MFA devices: ``` aws iam list-virtual-mfa-devices ``` If the output contains one MFA with the following Serial Number, it means the MFA is virtual, not hardware and the account is not compliant with this recommendation: `SerialNumber: arn:aws:iam::_<aws_account_number>_:mfa/root-account-mfa-device`",
+ "AdditionalInformation": "IAM User account 'root' for us-gov cloud regions does not have console access. This control is not applicable for us-gov cloud regions.",
+ "References": "CCE-78911-5:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_enable_virtual.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_enable_physical.html#enable-hw-mfa-for-root:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-enable-root-access.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/enable-virt-mfa-for-root.html",
+ "DefaultValue": "By default, the AWS root user does not have a hardware MFA device assigned. MFA must be explicitly configured, and if enabled by default it will be virtual (software-based), not hardware."
+ }
+ ]
+ },
+ {
+ "Id": "2.7",
+ "Description": "Eliminate use of the 'root' user for administrative and daily tasks",
+ "Checks": [
+ "iam_avoid_root_usage"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "With the creation of an AWS account, a 'root user' is created that cannot be disabled or deleted. That user has unrestricted access to and control over all resources in the AWS account. It is highly recommended that the use of this account be avoided for everyday tasks.",
+ "RationaleStatement": "The 'root user' has unrestricted access to and control over all account resources. Use of it is inconsistent with the principles of least privilege and separation of duties, and can lead to unnecessary harm due to error or account compromise.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you find that the 'root' user account is being used for daily activities, including administrative tasks that do not require the 'root' user: 1. Change the 'root' user password. 2. Deactivate or delete any access keys associated with the 'root' user. Remember, anyone who has 'root' user credentials for your AWS account has unrestricted access to and control of all the resources in your account, including billing information.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console at `https://console.aws.amazon.com/iam/`. 2. In the left pane, click `Credential Report`. 3. Click on `Download Report`. 4. Open or Save the file locally. 5. Locate the `<root account>` under the user column. 6. Review `password_last_used, access_key_1_last_used_date, access_key_2_last_used_date` to determine when the 'root user' was last used. **From Command Line:** Run the following CLI commands to provide a credential report for determining the last time the 'root user' was used: ``` aws iam generate-credential-report ``` ``` aws iam get-credential-report --query 'Content' --output text | base64 -d | cut -d, -f1,5,11,16 | grep -B1 '<root_account>' ``` Review `password_last_used`, `access_key_1_last_used_date`, `access_key_2_last_used_date` to determine when the _root user_ was last used. **Note:** There are a few conditions under which the use of the 'root' user account is required. Please see the reference links for all of the tasks that require use of the 'root' user.",
+ "AdditionalInformation": "The 'root' user for us-gov cloud regions is not enabled by default. However, on request to AWS support, they can enable the 'root' user and grant access only through access-keys (CLI, API methods) for us-gov cloud region. If the 'root' user for us-gov cloud regions is enabled, this recommendation is applicable. Monitoring usage of the 'root' user can be accomplished by implementing recommendation 3.3 Ensure a log metric filter and alarm exist for usage of the 'root' user.",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html:https://docs.aws.amazon.com/general/latest/gr/aws_tasks-that-require-root.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.8",
+ "Description": "Ensure IAM password policy requires minimum length of 14 or greater",
+ "Checks": [
+ "iam_password_policy_minimum_length_14"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Password policies are, in part, used to enforce password complexity requirements. IAM password policies can be used to ensure passwords are at least a given length. It is recommended that the password policy require a minimum password length 14.",
+ "RationaleStatement": "Setting a password complexity policy increases account resiliency against brute force login attempts.",
+ "ImpactStatement": "Enforcing a minimum password length of 14 characters enhances security by making passwords more resistant to brute force attacks. However, it may require users to create longer and potentially more complex passwords, which could impact user convenience.",
+ "RemediationProcedure": "Perform the following to set the password policy as prescribed: **From Console:** 1. Login to AWS Console (with appropriate permissions to View Identity Access Management Account Settings) 2. Go to IAM Service on the AWS Console 3. Click on Account Settings on the Left Pane 4. Set Minimum password length to `14` or greater. 5. Click Apply password policy **From Command Line:** ``` aws iam update-account-password-policy --minimum-password-length 14 ``` Note: All commands starting with aws iam update-account-password-policy can be combined into a single command.",
+ "AuditProcedure": "Perform the following to ensure the password policy is configured as prescribed: **From Console:** 1. Login to AWS Console (with appropriate permissions to View Identity Access Management Account Settings) 2. Go to IAM Service on the AWS Console 3. Click on Account Settings on the Left Pane 4. Ensure Minimum password length is set to 14 or greater. **From Command Line:** ``` aws iam get-account-password-policy ``` Ensure the output of the above command includes MinimumPasswordLength: 14 (or higher)",
+ "AdditionalInformation": "Ensure the password policy also includes requirements for password complexity, such as the inclusion of uppercase letters, lowercase letters, numbers, and special characters: ``` aws iam update-account-password-policy --require-uppercase-characters --require-lowercase-characters --require-numbers --require-symbols ```",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_passwords_account-policy.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#configure-strong-password-policy",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.9",
+ "Description": "Ensure IAM password policy prevents password reuse",
+ "Checks": [
+ "iam_password_policy_reuse_24"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "IAM password policies can prevent the reuse of a given password by the same user. It is recommended that the password policy prevent the reuse of passwords.",
+ "RationaleStatement": "Preventing password reuse increases account resiliency against brute force login attempts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to set the password policy as prescribed: **From Console:** 1. Login to AWS Console (with appropriate permissions to View Identity Access Management Account Settings) 2. Go to IAM Service on the AWS Console 3. Click on Account Settings on the Left Pane 4. Check Prevent password reuse 5. Set Number of passwords to remember is set to `24` **From Command Line:** ``` aws iam update-account-password-policy --password-reuse-prevention 24 ``` Note: All commands starting with aws iam update-account-password-policy can be combined into a single command.",
+ "AuditProcedure": "Perform the following to ensure the password policy is configured as prescribed: **From Console:** 1. Login to AWS Console (with appropriate permissions to View Identity Access Management Account Settings) 2. Go to IAM Service on the AWS Console 3. Click on Account Settings on the Left Pane 4. Ensure Prevent password reuse is checked 5. Ensure Number of passwords to remember is set to 24 **From Command Line:** ``` aws iam get-account-password-policy ``` Ensure the output of the above command includes PasswordReusePrevention: 24",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_passwords_account-policy.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#configure-strong-password-policy",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.10",
+ "Description": "Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password",
+ "Checks": [
+ "iam_user_mfa_enabled_console_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Multi-Factor Authentication (MFA) adds an extra layer of authentication assurance beyond traditional credentials. With MFA enabled, when a user signs in to the AWS Console, they will be prompted for their user name and password as well as for an authentication code from their physical or virtual MFA token. It is recommended that MFA be enabled for all accounts that have a console password.",
+ "RationaleStatement": "Enabling MFA provides increased security for console access as it requires the authenticating principal to possess a device that displays a time-sensitive key and have knowledge of a credential.",
+ "ImpactStatement": "AWS will soon end support for SMS multi-factor authentication (MFA). New customers are not allowed to use this feature. We recommend that existing customers switch to an alternative method of MFA.",
+ "RemediationProcedure": "Perform the following to enable MFA: **From Console:** 1. Sign in to the AWS Management Console and open the IAM console at 'https://console.aws.amazon.com/iam/' 2. In the left pane, select `Users`. 3. In the `User Name` list, choose the name of the intended MFA user. 4. Choose the `Security Credentials` tab, and then choose `Manage MFA Device`. 5. In the `Manage MFA Device wizard`, choose `Virtual MFA` device, and then choose `Continue`. IAM generates and displays configuration information for the virtual MFA device, including a QR code graphic. The graphic is a representation of the 'secret configuration key' that is available for manual entry on devices that do not support QR codes. 6. Open your virtual MFA application. (For a list of apps that you can use for hosting virtual MFA devices, see Virtual MFA Applications at https://aws.amazon.com/iam/details/mfa/#Virtual_MFA_Applications). If the virtual MFA application supports multiple accounts (multiple virtual MFA devices), choose the option to create a new account (a new virtual MFA device). 7. Determine whether the MFA app supports QR codes, and then do one of the following: - Use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to Scan code, and then use the device's camera to scan the code. - In the Manage MFA Device wizard, choose Show secret key for manual configuration, and then type the secret configuration key into your MFA application. When you are finished, the virtual MFA device starts generating one-time passwords. 8. In the `Manage MFA Device wizard`, in the `MFA Code 1 box`, type the `one-time password` that currently appears in the virtual MFA device. Wait up to 30 seconds for the device to generate a new one-time password. Then type the second `one-time password` into the `MFA Code 2 box`. 9. Click `Assign MFA`.",
+ "AuditProcedure": "Perform the following to determine if a MFA device is enabled for all IAM users having a console password: **From Console:** 1. Open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). 2. In the left pane, select `Users` 3. If the `MFA` or `Password age` columns are not visible in the table, click the gear icon at the upper right corner of the table and ensure a checkmark is next to both, then click `Close`. 4. Ensure that for each user where the `Password age` column shows a password age, the `MFA` column shows `Virtual`, `U2F Security Key`, or `Hardware`. **From Command Line:** 1. Run the following command (OSX/Linux/UNIX) to generate a list of all IAM users along with their password and MFA status: ``` aws iam generate-credential-report ``` ``` aws iam get-credential-report --query 'Content' --output text | base64 -d | cut -d, -f1,4,8 ``` 2. The output of this command will produce a table similar to the following: ``` user,password_enabled,mfa_active elise,false,false brandon,true,true rakesh,false,false helene,false,false paras,true,true anitha,false,false ``` 3. For any column having `password_enabled` set to `true` , ensure `mfa_active` is also set to `true.`",
+ "AdditionalInformation": "**Forced IAM User Self-Service Remediation** Amazon has published a pattern that requires users to set up MFA through self-service before they gain access to their complete set of permissions. Until they complete this step, they cannot access their full permissions. This pattern can be used for new AWS accounts. It can also be applied to existing accounts; it is recommended that users receive instructions and a grace period to complete MFA enrollment before active enforcement on existing AWS accounts.",
+ "References": "https://tools.ietf.org/html/rfc6238:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#enable-mfa-for-privileged-users:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_enable_virtual.html:https://blogs.aws.amazon.com/security/post/Tx2SJJYE082KBUK/How-to-Delegate-Management-of-Multi-Factor-Authentication-to-AWS-IAM-Users",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.11",
+ "Description": "Ensure credentials unused for 45 days or more are disabled",
+ "Checks": [
+ "iam_user_accesskey_unused",
+ "iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS IAM users can access AWS resources using different types of credentials, such as passwords or access keys. It is recommended that all credentials that have been unused for 45 days or more be deactivated or removed.",
+ "RationaleStatement": "Disabling or removing unnecessary credentials will reduce the window of opportunity for credentials associated with a compromised or abandoned account to be used.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** Perform the following to manage Unused Password (IAM user console access) 1. Login to the AWS Management Console: 2. Click `Services` 3. Click `IAM` 4. Click on `Users` 5. Click on `Security Credentials` 6. Select user whose `Console last sign-in` is greater than 45 days 7. Click `Security credentials` 8. In section `Sign-in credentials`, `Console password` click `Manage` 9. Under Console Access select `Disable` 10. Click `Apply` Perform the following to deactivate Access Keys: 1. Login to the AWS Management Console: 2. Click `Services` 3. Click `IAM` 4. Click on `Users` 5. Click on `Security Credentials` 6. Select any access keys that are over 45 days old and that have been used and - Click on `Make Inactive` 7. Select any access keys that are over 45 days old and that have not been used and - Click the X to `Delete`",
+ "AuditProcedure": "Perform the following to determine if unused credentials exist: **From Console:** 1. Login to the AWS Management Console 2. Click `Services` 3. Click `IAM` 4. Click on `Users` 5. Click the `Settings` (gear) icon. 6. Select `Console last sign-in`, `Access key last used`, and `Access Key Id` 7. Click on `Close` 8. Check and ensure that `Console last sign-in` is less than 45 days ago. **Note** - `Never` means the user has never logged in. 9. Check and ensure that `Access key age` is less than 45 days and that `Access key last used` does not say `None` If the user hasn't signed into the Console in the last 45 days or Access keys are over 45 days old refer to the remediation. **From Command Line:** **Download Credential Report:** 1. Run the following commands: ``` aws iam generate-credential-report aws iam get-credential-report --query 'Content' --output text | base64 -d | cut -d, -f1,4,5,6,9,10,11,14,15,16 | grep -v '^<root_account>' ``` **Ensure unused credentials do not exist:** 2. For each user having `password_enabled` set to `TRUE` , ensure `password_last_used_date` is less than `45` days ago. - When `password_enabled` is set to `TRUE` and `password_last_used` is set to `No_Information` , ensure `password_last_changed` is less than 45 days ago. 3. For each user having an `access_key_1_active` or `access_key_2_active` to `TRUE` , ensure the corresponding `access_key_n_last_used_date` is less than `45` days ago. - When a user having an `access_key_x_active` (where x is 1 or 2) to `TRUE` and corresponding access_key_x_last_used_date is set to `N/A`, ensure `access_key_x_last_rotated` is less than 45 days ago.",
+ "AdditionalInformation": "<root_account> is excluded in the audit since the root account should not be used for day-to-day business and would likely be unused for more than 45 days.",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#remove-credentials:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_finding-unused.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_passwords_admin-change-user.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.12",
+ "Description": "Ensure access keys are rotated every 90 days or less",
+ "Checks": [
+ "iam_rotate_access_key_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Access keys consist of an access key ID and secret access key, which are used to sign programmatic requests that you make to AWS. AWS users need their own access keys to make programmatic calls to AWS from the AWS Command Line Interface (AWS CLI), Tools for Windows PowerShell, the AWS SDKs, or direct HTTP calls using the APIs for individual AWS services. It is recommended that all access keys be rotated regularly.",
+ "RationaleStatement": "Rotating access keys will reduce the window of opportunity for an access key that is associated with a compromised or terminated account to be used. Access keys should be rotated to ensure that data cannot be accessed with an old key which might have been lost, cracked, or stolen.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to rotate access keys: **From Console:** 1. Go to the Management Console (https://console.aws.amazon.com/iam) 2. Click on `Users` 3. Click on `Security Credentials` 4. As an Administrator - Click on `Make Inactive` for keys that have not been rotated in `90` Days 5. As an IAM User - Click on `Make Inactive` or `Delete` for keys which have not been rotated or used in `90` Days 6. Click on `Create Access Key` 7. Update programmatic calls with new Access Key credentials **From Command Line:** 1. While the first access key is still active, create a second access key, which is active by default. Run the following command: ``` aws iam create-access-key --user-name <iam_user> ``` At this point, the user has two active access keys. 2. Update all applications and tools to use the new access key. 3. Determine whether the first access key is still in use by using this command: ``` aws iam get-access-key-last-used --access-key-id <iam_access_key_id> ``` 4. One approach is to wait several days and then check the old access key for any use before proceeding. Even if step 3 indicates no use of the old key, it is recommended that you do not immediately delete the first access key. Instead, change the state of the first access key to Inactive using this command: ``` aws iam update-access-key --user-name <iam_user> --access-key-id <iam_access_key_id> --status Inactive ``` 5. Use only the new access key to confirm that your applications are working. Any applications and tools that still use the original access key will stop working at this point because they no longer have access to AWS resources. If you find such an application or tool, you can switch its state back to Active to reenable the first access key. Then return to step 2 and update this application to use the new key. 6. After you wait some period of time to ensure that all applications and tools have been updated, you can delete the first access key with this command: ``` aws iam delete-access-key --user-name <iam_user> --access-key-id <iam_access_key_id> ```",
+ "AuditProcedure": "Perform the following to determine if access keys are rotated as prescribed: **From Console:** 1. Go to the Management Console (https://console.aws.amazon.com/iam) 2. Click on `Users` 3. For each user, go to `Security Credentials` 4. Review each key under `Access Keys` 5. For each key that shows `Active` for status, ensure that `Created` is less than or equal to `90 days ago`. **From Command Line:** ``` aws iam generate-credential-report aws iam get-credential-report --query 'Content' --output text | base64 -d ``` The `access_key_1_last_rotated` and the `access_key_2_last_rotated` fields in this file notes the date and time, in ISO 8601 date-time format, when the user's access key was created or last changed. If the user does not have an active access key, the value in this field is N/A (not applicable).",
+ "AdditionalInformation": "",
+ "References": "CCE-78902-4:https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#rotate-credentials:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_finding-unused.html:https://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html",
+ "DefaultValue": "By default, AWS does not enforce access key rotation. Access keys remain valid until they are manually deactivated or deleted."
+ }
+ ]
+ },
+ {
+ "Id": "2.13",
+ "Description": "Ensure IAM users receive permissions only through groups",
+ "Checks": [
+ "iam_policy_attached_only_to_group_or_roles"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "IAM users are granted access to services, functions, and data through IAM policies. There are four ways to define policies for a user: 1) Edit the user policy directly, also known as an inline or user policy; 2) attach a policy directly to a user; 3) add the user to an IAM group that has an attached policy; 4) add the user to an IAM group that has an inline policy. Only the third implementation is recommended.",
+ "RationaleStatement": "Assigning IAM policies solely through groups unifies permissions management into a single, flexible layer that is consistent with organizational functional roles. By unifying permissions management, the likelihood of excessive permissions is reduced.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** Perform the following to create an IAM group and assign a policy to it: 1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/. 2. In the navigation pane, click `Groups` and then click `Create New Group`. 3. In the `Group Name` box, type the name of the group and then click `Next Step`. 4. In the list of policies, select the check box for each policy that you want to apply to all members of the group. Then click `Next Step`. 5. Click `Create Group`. Perform the following to add a user to a given group: 1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/. 2. In the navigation pane, click `Groups`. 3. Select the group to add a user to. 4. Click `Add Users To Group`. 5. Select the users to be added to the group. 6. Click `Add Users`. Perform the following to remove a direct association between a user and policy: 1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/. 2. In the left navigation pane, click on Users. 3. For each user: - Select the user - Click on the `Permissions` tab - Expand `Permissions policies` - Click `X` for each policy; then click Detach or Remove (depending on policy type) **From Command Line:** 1. Create the IAM user group: ``` aws iam create-group --group-name <new_IAM_group_name> ``` 2. Attach the policy to the IAM user group: ``` aws iam attach-group-policy --group-name <new_IAM_group_name> --policy-arn <IAM_policy_ARN> ``` 3. Perform the following to add a user to a given group: ``` aws iam add-user-to-group --user-name <IAM_user_name> --group-name <new_IAM_group_name> ``` 4. Perform the following to remove a direct association between a user and policy: ``` aws iam detach-user-policy --user-name <IAM_user_name> --policy-arn <IAM_policy_ARN> ``` 5. Delete an inline policy from an IAM user: ``` aws iam delete-user-policy --user-name <IAM_user_name> --policy-name <IAM_policy_name> ```",
+ "AuditProcedure": "Perform the following to determine if an inline policy is set or a policy is directly attached to users: 1. Run the following to get a list of IAM users: ``` aws iam list-users --query 'Users[*].UserName' --output text ``` 2. For each user returned, run the following command to determine if any policies are attached to them: ``` aws iam list-attached-user-policies --user-name <iam_user> aws iam list-user-policies --user-name <iam_user> ``` 3. If any policies are returned, the user has an inline policy or direct policy attachment.",
+ "AdditionalInformation": "",
+ "References": "http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html:http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html:CCE-78912-3",
+ "DefaultValue": "By default, AWS allows IAM policies to be attached directly to users, groups, or roles. There is no restriction preventing direct user policies unless explicitly enforced by organizational standards."
+ }
+ ]
+ },
+ {
+ "Id": "2.14",
+ "Description": "Ensure IAM policies that allow full \"*:*\" administrative privileges are not attached",
+ "Checks": [
+ "iam_aws_attached_policy_no_administrative_privileges",
+ "iam_customer_attached_policy_no_administrative_privileges"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "IAM policies are the means by which privileges are granted to users, groups, or roles. It is recommended and considered standard security advice to grant least privilege—that is, granting only the permissions required to perform a task. Determine what users need to do, and then craft policies for them that allow the users to perform only those tasks, instead of granting full administrative privileges.",
+ "RationaleStatement": "It's more secure to start with a minimum set of permissions and grant additional permissions as necessary, rather than starting with permissions that are too lenient and then attempting to tighten them later. Providing full administrative privileges instead of restricting access to the minimum set of permissions required for the user exposes resources to potentially unwanted actions. IAM policies that contain a statement with `Effect: Allow` and `Action: *` over `Resource: *` should be removed.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** Perform the following to detach the policy that has full administrative privileges: 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). 2. In the navigation pane, click Policies and then search for the policy name found in the audit step. 3. Select the policy that needs to be deleted. 4. In the policy action menu, select `Detach`. 5. Select all Users, Groups, Roles that have this policy attached. 6. Click `Detach Policy`. 7. Select the newly detached policy and select `Delete`. **From Command Line:** Perform the following to detach the policy that has full administrative privileges as found in the audit step: 1. Lists all IAM users, groups, and roles that the specified managed policy is attached to. ``` aws iam list-entities-for-policy --policy-arn <policy_arn> ``` 2. Detach the policy from all IAM Users: ``` aws iam detach-user-policy --user-name <iam_user> --policy-arn <policy_arn> ``` 3. Detach the policy from all IAM Groups: ``` aws iam detach-group-policy --group-name <iam_group> --policy-arn <policy_arn> ``` 4. Detach the policy from all IAM Roles: ``` aws iam detach-role-policy --role-name <iam_role> --policy-arn <policy_arn> ```",
+ "AuditProcedure": "Perform the following to determine existing policies: **From Command Line:** 1. Run the following to get a list of IAM policies: ``` aws iam list-policies --only-attached --output text ``` 2. For each policy returned, run the following command to determine if any policy is allowing full administrative privileges on the account: ``` aws iam get-policy-version --policy-arn <policy_arn> --version-id <version> ``` 3. In the output, the policy should not contain any Statement block with `Effect: Allow` and `Action` set to `*` and `Resource` set to `*`.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html:https://docs.aws.amazon.com/cli/latest/reference/iam/index.html#cli-aws-iam",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.15",
+ "Description": "Ensure a support role has been created to manage incidents with AWS Support",
+ "Checks": [
+ "iam_support_role_created"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS provides a support center that can be used for incident notification and response, as well as technical support and customer services. Create an IAM Role, with the appropriate policy assigned, to allow authorized users to manage incidents with AWS Support.",
+ "RationaleStatement": "By implementing least privilege for access control, an IAM Role will require an appropriate IAM Policy to allow Support Center Access in order to manage Incidents with AWS Support.",
+ "ImpactStatement": "All AWS Support plans include an unlimited number of account and billing support cases, with no long-term contracts. Support billing calculations are performed on a per-account basis for all plans. Enterprise Support plan customers have the option to include multiple enabled accounts in an aggregated monthly billing calculation. Monthly charges for the Business and Enterprise support plans are based on each month's AWS usage charges, subject to a monthly minimum, billed in advance. When assigning rights, keep in mind that other policies may grant access to Support as well. This may include AdministratorAccess and other policies including customer managed policies. Utilizing the AWS managed 'AWSSupportAccess' role is one simple way of ensuring that this permission is properly granted. To better support the principle of separation of duties, it would be best to only attach this role where necessary.",
+ "RemediationProcedure": "**From Command Line:** 1. Create an IAM role for managing incidents with AWS: - Create a trust relationship policy document that allows <iam_user> to manage AWS incidents, and save it locally as /tmp/TrustPolicy.json: ``` { Version: 2012-10-17, Statement: [ { Effect: Allow, Principal: { AWS: <iam_user> }, Action: sts:AssumeRole } ] } ``` 2. Create the IAM role using the above trust policy: ``` aws iam create-role --role-name <aws_support_iam_role> --assume-role-policy-document file:///tmp/TrustPolicy.json ``` 3. Attach 'AWSSupportAccess' managed policy to the created IAM role: ``` aws iam attach-role-policy --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess --role-name <aws_support_iam_role> ```",
+ "AuditProcedure": "**From Command Line:** 1. List IAM policies, filter for the 'AWSSupportAccess' managed policy, and note the Arn element value: ``` aws iam list-policies --query Policies[?PolicyName == 'AWSSupportAccess'] ``` 2. Check if the 'AWSSupportAccess' policy is attached to any role: ``` aws iam list-entities-for-policy --policy-arn arn:aws:iam::aws:policy/AWSSupportAccess ``` 3. In the output, ensure `PolicyRoles` does not return empty. 'Example: Example: PolicyRoles: [ ]' If it returns empty refer to the remediation below.",
+ "AdditionalInformation": "AWSSupportAccess policy is a global AWS resource. It has same ARN as `arn:aws:iam::aws:policy/AWSSupportAccess` for every account.",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html:https://aws.amazon.com/premiumsupport/pricing/:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/list-policies.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/attach-role-policy.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/list-entities-for-policy.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.16",
+ "Description": "Ensure IAM instance roles are used for AWS resource access from instances",
+ "Checks": [
+ "ec2_instance_profile_attached"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS access from within AWS instances can be done by either encoding AWS keys into AWS API calls or by assigning the instance to a role which has an appropriate permissions policy for the required access. AWS Access means accessing the APIs of AWS in order to access AWS resources or manage AWS account resources.",
+ "RationaleStatement": "AWS IAM roles reduce the risks associated with sharing and rotating credentials that can be used outside of AWS itself. Compromised credentials can be used from outside the AWS account to which they provide access. In contrast, to leverage role permissions, an attacker would need to gain and maintain access to a specific instance to use the privileges associated with it. Additionally, if credentials are encoded into compiled applications or other hard-to-change mechanisms, they are even less likely to be properly rotated due to the risks of service disruption. As time passes, credentials that cannot be rotated are more likely to be known by an increasing number of individuals who no longer work for the organization that owns the credentials.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** 1. Sign in to the AWS Management Console and navigate to the EC2 dashboard at `https://console.aws.amazon.com/ec2/`. 2. In the left navigation panel, choose `Instances`. 3. Select the EC2 instance you want to modify. 4. Click `Actions`. 5. Click `Security`. 6. Click `Modify IAM role`. 7. Click `Create new IAM role` if a new IAM role is required. 8. Select the IAM role you want to attach to your instance in the `IAM role` dropdown. 9. Click `Update IAM role`. 10. Repeat steps 3 to 9 for each EC2 instance in your AWS account that requires an IAM role to be attached. **From Command Line:** 1. Run the `describe-instances` command to list all EC2 instance IDs in the selected AWS region: ``` aws ec2 describe-instances --region <region-name> --query 'Reservations[*].Instances[*].InstanceId' ``` 2. Run the `associate-iam-instance-profile` command to attach an instance profile (which is attached to an IAM role) to the EC2 instance: ``` aws ec2 associate-iam-instance-profile --region <region-name> --instance-id <Instance-ID> --iam-instance-profile Name=Instance-Profile-Name ``` 3. Run the `describe-instances` command again for the recently modified EC2 instance. The command output should return the instance profile ARN and ID: ``` aws ec2 describe-instances --region <region-name> --instance-id <Instance-ID> --query 'Reservations[*].Instances[*].IamInstanceProfile' ``` 4. Repeat steps 2 and 3 for each EC2 instance in your AWS account that requires an IAM role to be attached.",
+ "AuditProcedure": "First, check if the instance has any API secrets stored using Secret Scanning. Currently, AWS does not have a solution for this. You can use open-source tools like TruffleHog to scan for secrets in the EC2 instance. If a secret is found, then assign the role to the instance. **From Console:** 1. Sign in to the AWS Management Console and navigate to the EC2 dashboard at `https://console.aws.amazon.com/ec2/`. 2. In the left navigation panel, choose `Instances`. 3. Select the EC2 instance you want to examine. 4. Select `Actions`. 5. Select `View details`. 6. Select `Security` in the lower panel. - If the value for **Instance profile arn** is an instance profile ARN, then an instance profile (that contains an IAM role) is attached. - If the value for **IAM Role** is blank, no role is attached. - If the value for **IAM Role** contains a role, a role is attached. - If the value for **IAM Role** is No roles attached to instance profile: <Instance-Profile-Name>, then an instance profile is attached to the instance, but it does not contain an IAM role. 7. Repeat steps 3 to 6 for each EC2 instance in your AWS account. **From Command Line:** 1. Run the `describe-instances` command to list all EC2 instance IDs in the selected AWS region: ``` aws ec2 describe-instances --region <region-name> --query 'Reservations[*].Instances[*].InstanceId' ``` 2. Run the `describe-instances` command again for each EC2 instance using the `IamInstanceProfile` identifier in the query filter to check if an IAM role is attached: ``` aws ec2 describe-instances --region <region-name> --instance-id <Instance-ID> --query 'Reservations[*].Instances[*].IamInstanceProfile' ``` 3. If an IAM role is attached, the command output will show the IAM instance profile ARN and ID. 4. Repeat steps 2 and 3 for each EC2 instance in your AWS account.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2.html:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.17",
+ "Description": "Ensure that all expired SSL/TLS certificates stored in AWS IAM are removed",
+ "Checks": [
+ "iam_no_expired_server_certificates_stored"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "To enable HTTPS connections to your website or application in AWS, you need an SSL/TLS server certificate. You can use AWS Certificate Manager (ACM) or IAM to store and deploy server certificates. Use IAM as a certificate manager only when you must support HTTPS connections in a region that is not supported by ACM. IAM securely encrypts your private keys and stores the encrypted version in IAM SSL certificate storage. IAM supports deploying server certificates in all regions, but you must obtain your certificate from an external provider for use with AWS. You cannot upload an ACM certificate to IAM. Additionally, you cannot manage your certificates from the IAM Console.",
+ "RationaleStatement": "Removing expired SSL/TLS certificates eliminates the risk that an invalid certificate will be deployed accidentally to a resource such as AWS Elastic Load Balancer (ELB), which can damage the credibility of the application/website behind the ELB. As a best practice, it is recommended to delete expired certificates.",
+ "ImpactStatement": "Deleting the certificate could have implications for your application if you are using an expired server certificate with Elastic Load Balancing, CloudFront, etc. You must make configurations in the respective services to ensure there is no interruption in application functionality.",
+ "RemediationProcedure": "**From Console:** Removing expired certificates via AWS Management Console is not currently supported. To delete SSL/TLS certificates stored in IAM through the AWS API, use the Command Line Interface (CLI). **From Command Line:** To delete an expired certificate, run the following command by replacing <CERTIFICATE_NAME> with the name of the certificate to delete: ``` aws iam delete-server-certificate --server-certificate-name <CERTIFICATE_NAME> ``` When the preceding command is successful, it does not return any output.",
+ "AuditProcedure": "**From Console:** Getting the certificate expiration information via the AWS Management Console is not currently supported. To request information about the SSL/TLS certificates stored in IAM through the AWS API, use the Command Line Interface (CLI). **From Command Line:** Run the `list-server-certificates` command to list all the IAM-stored server certificates: ``` aws iam list-server-certificates ``` The command output should return an array that contains all the SSL/TLS certificates currently stored in IAM and their metadata (name, ID, expiration date, etc): ``` { ServerCertificateMetadataList: [ { ServerCertificateId: EHDGFRW7EJFYTE88D, ServerCertificateName: MyServerCertificate, Expiration: 2018-07-10T23:59:59Z, Path: /, Arn: arn:aws:iam::012345678910:server-certificate/MySSLCertificate, UploadDate: 2018-06-10T11:56:08Z } ] } ``` Verify the `ServerCertificateName` and `Expiration` parameter value (expiration date) for each SSL/TLS certificate returned by the list-server-certificates command and determine if there are any expired server certificates currently stored in AWS IAM. If so, use the AWS API to remove them. If this command returns: ``` { { ServerCertificateMetadataList: [] } ``` This means that there are no expired certificates; it **does not** mean that no certificates exist.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/delete-server-certificate.html",
+ "DefaultValue": "By default, expired certificates will not be deleted."
+ }
+ ]
+ },
+ {
+ "Id": "2.18",
+ "Description": "Ensure that IAM External Access Analyzer is enabled for all regions",
+ "Checks": [
+ "accessanalyzer_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable the IAM External Access Analyzer regarding all resources in each active AWS region. IAM Access Analyzer is a technology introduced at AWS reinvent 2019. After the Analyzer is enabled in IAM, scan results are displayed on the console showing the accessible resources. Scans show resources that other accounts and federated users can access, such as KMS keys and IAM roles. The results allow you to determine whether an unintended user is permitted, making it easier for administrators to monitor least privilege access. Access Analyzer analyzes only the policies that are applied to resources in the same AWS Region.",
+ "RationaleStatement": "AWS IAM External Access Analyzer helps you identify the resources in your organization and accounts, such as Amazon S3 buckets or IAM roles, that are shared with external entities. This allows you to identify unintended access to your resources and data. Access Analyzer identifies resources that are shared with external principals by using logic-based reasoning to analyze the resource-based policies in your AWS environment. IAM External Access Analyzer continuously monitors all policies for S3 buckets, IAM roles, KMS (Key Management Service) keys, AWS Lambda functions, Amazon SQS (Simple Queue Service) queues and more",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** Perform the following to enable IAM Access Analyzer for IAM policies: 1. Open the IAM console at `https://console.aws.amazon.com/iam/.` 2. Choose `Access analyzer`. 3. Choose `Create external access analyzer`. 4. On the `Create analyzer` page, confirm that the `Region` displayed is the Region where you want to enable Access Analyzer. 5. Optionally enter a name for the analyzer. 6. Optionally add any tags that you want to apply to the analyzer. 7. Choose `Create Analyzer`. 8. Repeat these step for each active region. **From Command Line:** Run the following command: ``` aws accessanalyzer list-analyzers --type ORGANIZATION ``` Repeat this command for each active region. **Note:** The IAM Access Analyzer is successfully configured only when the account you use has the necessary permissions.",
+ "AuditProcedure": "**From Console:** 1. Open the IAM console at `https://console.aws.amazon.com/iam/` 2. Under `Access analyzer` choose `Analyzer Settings` 3. On the `Analyzer Settings` page, there will be a list of analyzers. 4. Look for analyzers where the `Finding type` is `External Access`. **From Command Line:** 1. Run the following command: ``` aws accessanalyzer list-analyzers --type ORGANIZATION | grep status ``` 2. Ensure that at least one Analyzer's `status` is set to `ACTIVE`. 3. Repeat the steps above for each active region. If an Access Analyzer is not listed for each region or the status is not set to active refer to the remediation procedure below.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html:https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-getting-started.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/accessanalyzer/get-analyzer.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/accessanalyzer/create-analyzer.html",
+ "DefaultValue": "By default, IAM External Access Analyzer is not enabled in any region. An analyzer must be explicitly created and activated for each region where monitoring is required."
+ }
+ ]
+ },
+ {
+ "Id": "2.19",
+ "Description": "Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments",
+ "Checks": [
+ "iam_check_saml_providers_sts"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "In multi-account environments, IAM user centralization facilitates greater user control. User access beyond the initial account is then provided via role assumption. Centralization of users can be accomplished through federation with an external identity provider or through the use of AWS Organizations.",
+ "RationaleStatement": "Centralizing IAM user management to a single identity store reduces complexity and thus the likelihood of access management errors.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "The remediation procedure will vary based on each individual organization's implementation of identity federation and/or AWS Organizations, with the acceptance criteria that no non-service IAM users and non-root accounts are present outside the account providing centralized IAM user management.",
+ "AuditProcedure": "For multi-account AWS environments with an external identity provider: 1. Determine the master account for identity federation or IAM user management 2. Login to that account through the AWS Management Console 3. Click `Services` 4. Click `IAM` 5. Click `Identity providers` 6. Verify the configuration For multi-account AWS environments with an external identity provider, as well as for those implementing AWS Organizations without an external identity provider: 1. Determine all accounts that should not have local users present 2. Log into the AWS Management Console 3. Switch role into each identified account 4. Click `Services` 5. Click `IAM` 6. Click `Users` 7. Confirm that no IAM users representing individuals are present",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.20",
+ "Description": "Ensure access to AWSCloudShellFullAccess is restricted",
+ "Checks": [
+ "iam_policy_cloudshell_admin_not_attached"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "AWS CloudShell is a convenient way of running CLI commands against AWS services; a managed IAM policy ('AWSCloudShellFullAccess') provides full access to CloudShell, which allows file upload and download capability between a user's local system and the CloudShell environment. Within the CloudShell environment, a user has sudo permissions and can access the internet. Therefore, it is feasible to install file transfer software, for example, and move data from CloudShell to external internet servers.",
+ "RationaleStatement": "Access to this policy should be restricted, as it presents a potential channel for data exfiltration by malicious cloud admins who are given full permissions to the service. AWS documentation describes how to create a more restrictive IAM policy that denies file transfer permissions.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console** 1. Open the IAM console at https://console.aws.amazon.com/iam/ 2. In the left pane, select Policies 3. Search for and select AWSCloudShellFullAccess 4. On the Entities attached tab, for each item, check the box and select Detach",
+ "AuditProcedure": "**From Console** 1. Open the IAM console at https://console.aws.amazon.com/iam/ 2. In the left pane, select Policies 3. Search for and select AWSCloudShellFullAccess 4. On the Entities attached tab, ensure that there are no entities using this policy **From Command Line** 1. List IAM policies, filter for the 'AWSCloudShellFullAccess' managed policy, and note the Arn element value: ``` aws iam list-policies --query Policies[?PolicyName == 'AWSCloudShellFullAccess'] ``` 2. Check if the 'AWSCloudShellFullAccess' policy is attached to any role: ``` aws iam list-entities-for-policy --policy-arn arn:aws:iam::aws:policy/AWSCloudShellFullAccess ``` 3. In the output, ensure PolicyRoles returns empty. 'Example: Example: PolicyRoles: [ ]' If it does not return empty, refer to the remediation below. **Note:** Keep in mind that other policies may grant access.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/cloudshell/latest/userguide/sec-auth-with-identities.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.21",
+ "Description": "Ensure AWS resource policies do not allow unrestricted access using 'Principal': '*'",
+ "Checks": [
+ "s3_bucket_policy_public_write_access",
+ "sqs_queues_not_publicly_accessible",
+ "sns_topics_not_publicly_accessible",
+ "awslambda_function_not_publicly_accessible",
+ "kms_key_not_publicly_accessible",
+ "glacier_vaults_policy_public_access",
+ "secretsmanager_not_publicly_accessible",
+ "eventbridge_bus_exposed"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure AWS resource-based policies, such as Amazon S3 bucket policies, Amazon SQS queue policies, Amazon SNS topic policies, and AWS Lambda resource policies, do not grant unrestricted access using \"Principal\": \"*\" with \"Effect\": \"Allow\" unless the policy includes restrictive conditions that limit access to specific trusted identities, accounts, services, or network boundaries.",
+ "RationaleStatement": "Resource-based policies are evaluated alongside identity-based IAM policies during authorization decisions. When a policy statement specifies \"Principal\": \"*\" with \"Effect\": \"Allow\", it grants the specified permissions to any AWS principal unless additional conditions restrict the request. This may unintentionally allow access from users, roles, or services in any AWS account. Such broad access significantly increases the risk of unauthorized data access, resource abuse, or data exfiltration.",
+ "ImpactStatement": "Unrestricted resource-based policies may expose data or services to unauthorized access, potentially leading to data breaches, service misuse, or unintended public exposure.",
+ "RemediationProcedure": "If a resource policy contains `\"Principal\": \"*\"` with `\"Effect\": \"Allow\"` and lacks sufficient restrictions, modify the policy to limit access. **OPTION 1 - Restrict the Principal:** Replace the wildcard principal (`\"Principal\": \"*\"`) with a specific account, role, user, or service. Example Non-Compliant Policy: ``` {\"Version\": \"2012-10-17\", \"Statement\": [{\"Sid\": \"AllowPublicAccess\", \"Effect\": \"Allow\", \"Principal\": \"*\", \"Action\": \"sqs:SendMessage\", \"Resource\": \"arn:aws:sqs:us-east-1:123456789012:my-queue\"}]} ``` Steps: 1. Retrieve the current policy: ``` aws sqs get-queue-attributes --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-queue --attribute-names Policy --query 'Attributes.Policy' ``` 2. Update the policy with a specific principal: ``` aws sqs set-queue-attributes --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-queue --attributes '{\"Policy\": \"{\\\"Version\\\":\\\"2012-10-17\\\",\\\"Statement\\\":[{\\\"Sid\\\":\\\"AllowSpecificAccount\\\",\\\"Effect\\\":\\\"Allow\\\",\\\"Principal\\\":{\\\"AWS\\\":\\\"arn:aws:iam::345678901234:root\\\"},\\\"Action\\\":\\\"sqs:SendMessage\\\",\\\"Resource\\\":\\\"arn:aws:sqs:us-east-1:123456789012:my-queue\\\"}]}\"}' ``` Resulting Compliant Policy: ``` {\"Version\": \"2012-10-17\", \"Statement\": [{\"Sid\": \"AllowSpecificAccount\", \"Effect\": \"Allow\", \"Principal\": {\"AWS\": \"arn:aws:iam::345678901234:root\"}, \"Action\": \"sqs:SendMessage\", \"Resource\": \"arn:aws:sqs:us-east-1:123456789012:my-queue\"}]} ``` **OPTION 2 - Restrict Using Conditions:** If a wildcard principal is required, add restrictive conditions. Example compliant policy: ``` {\"Version\": \"2012-10-17\", \"Statement\": [{\"Sid\": \"AllowServiceIntegration\", \"Effect\": \"Allow\", \"Principal\": \"*\", \"Action\": \"sqs:SendMessage\", \"Resource\": \"arn:aws:sqs:us-east-1:123456789012:my-queue\", \"Condition\": {\"StringEquals\": {\"aws:SourceAccount\": \"345678901234\"}}}]} ```",
+ "AuditProcedure": "1. Identify resources that support resource-based policies within the AWS account, such as S3 buckets, SQS queues, SNS topics, and Lambda functions. 2. Retrieve the resource policies for each resource. Example CLI commands: SQS Queue Policies: ``` aws sqs get-queue-attributes --queue-url https://sqs.region.amazonaws.com/account/QUEUE --attribute-names Policy ``` S3 Bucket Policies: ``` aws s3api get-bucket-policy --bucket YOUR-BUCKET-NAME ``` SNS Topic Policies: ``` aws sns get-topic-attributes --topic-arn TOPIC-ARN --query \"Attributes.Policy\" --output text ``` 3. Inspect the retrieved policies and identify statements containing: - `\"Effect\": \"Allow\"` AND `\"Principal\": \"*\"` OR - `\"Principal\": {\"AWS\": \"*\"}` 4. Evaluate whether the statement includes restrictive conditions such as: - `aws:SourceArn` - `aws:SourceAccount` - `aws:PrincipalArn` - Other service-specific condition keys 5. Determine audit status: - Compliant: Wildcard principals are present only when restrictive conditions limit access to trusted principals or services - Non-Compliant: Wildcard principals are used without sufficient restrictions",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, AWS does not prevent the use of \"Principal\": \"*\" in resource-based policies. Policies may allow unrestricted access unless explicitly restricted through policy definitions or organizational controls. It is the responsibility of the customer to ensure that resource policies are properly scoped and do not grant unintended public or cross-account access."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.1",
+ "Description": "Ensure S3 Bucket Policy is set to deny HTTP requests",
+ "Checks": [
+ "s3_bucket_secure_transport_policy"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.1 Simple Storage Service (S3)",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "At the Amazon S3 bucket level, you can configure permissions through a bucket policy, making the objects accessible only through HTTPS.",
+ "RationaleStatement": "By default, Amazon S3 allows both HTTP and HTTPS requests. To ensure that access to Amazon S3 objects is only permitted through HTTPS, you must explicitly deny HTTP requests. Bucket policies that allow HTTPS requests without explicitly denying HTTP requests will not comply with this recommendation.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Select the check box next to the Bucket. 3. Click on 'Permissions'. 4. Click 'Bucket Policy'. 5. Add either of the following to the existing policy, filling in the required information: ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: arn:aws:s3:::<bucket_name>/*, Condition: { Bool: { aws:SecureTransport: false } } } ``` or ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: [ arn:aws:s3:::<bucket_name>, arn:aws:s3:::<bucket_name>/* ], Condition: { NumericLessThan: { s3:TlsVersion: 1.2 } } } ``` 6. Save 7. Repeat for all the buckets in your AWS account that contain sensitive data. **From Console** Using AWS Policy Generator: 1. Repeat steps 1-4 above. 2. Click on `Policy Generator` at the bottom of the Bucket Policy Editor. 3. Select Policy Type `S3 Bucket Policy`. 4. Add Statements: - `Effect` = Deny - `Principal` = * - `AWS Service` = Amazon S3 - `Actions` = * - `Amazon Resource Name` = <ARN of the S3 Bucket> 5. Generate Policy. 6. Copy the text and add it to the Bucket Policy. **From Command Line:** 1. Export the bucket policy to a json file: ``` aws s3api get-bucket-policy --bucket <bucket_name> --query Policy --output text > policy.json ``` 2. Modify the policy.json file by adding either of the following: ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: arn:aws:s3:::<bucket_name>/*, Condition: { Bool: { aws:SecureTransport: false } } } ``` or ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: [ arn:aws:s3:::<bucket_name>, arn:aws:s3:::<bucket_name>/* ], Condition: { NumericLessThan: { s3:TlsVersion: 1.2 } } } ``` 3. Apply this modified policy back to the S3 bucket: ``` aws s3api put-bucket-policy --bucket <bucket_name> --policy file://policy.json ```",
+ "AuditProcedure": "To allow access to HTTPS, you can use a bucket policy with the effect `allow` and a condition that checks for the key `aws:SecureTransport: true`. This means that HTTPS requests are allowed, but it does not deny HTTP requests. To explicitly deny HTTP access, ensure that there is also a bucket policy with the effect `deny` that contains the key `aws:SecureTransport: false`. You may also require TLS by setting a policy to deny any version lower than the one you wish to require, using the condition `NumericLessThan` and the key `s3:TlsVersion: 1.2`. **From Console:** 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Select the check box next to the Bucket. 3. Click on 'Permissions', then click on `Bucket Policy`. 4. Ensure that a policy is listed that matches either: ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: arn:aws:s3:::<bucket_name>/*, Condition: { Bool: { aws:SecureTransport: false } } } ``` or ``` { Sid: <optional>, Effect: Deny, Principal: *, Action: s3:*, Resource: [ arn:aws:s3:::<bucket_name>, arn:aws:s3:::<bucket_name>/* ], Condition: { NumericLessThan: { s3:TlsVersion: 1.2 } } } ``` `<optional>` and `<bucket_name>` will be specific to your account, and TLS version will be site/policy specific to your organisation. 5. Repeat for all the buckets in your AWS account. **From Command Line:** 1. List all of the S3 Buckets ``` aws s3 ls ``` 2. Using the list of buckets, run this command on each of them: ``` aws s3api get-bucket-policy --bucket <bucket_name> | grep aws:SecureTransport ``` or ``` aws s3api get-bucket-policy --bucket <bucket_name> | grep s3:TlsVersion ``` NOTE : If an error is thrown by the CLI, it means no policy has been configured for the specified S3 bucket, and that by default it is allowing both HTTP and HTTPS requests. 3. Confirm that `aws:SecureTransport` is set to false (such as `aws:SecureTransport:false`) or that `s3:TlsVersion` has a site-specific value. 4. Confirm that the policy line has Effect set to Deny 'Effect:Deny'",
+ "AdditionalInformation": "",
+ "References": "https://aws.amazon.com/premiumsupport/knowledge-center/s3-bucket-policy-for-config-rule/:https://aws.amazon.com/blogs/security/how-to-use-bucket-policies-and-apply-defense-in-depth-to-help-secure-your-amazon-s3-data/:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/get-bucket-policy.html",
+ "DefaultValue": "Both HTTP and HTTPS requests are allowed."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.2",
+ "Description": "Ensure MFA Delete is enabled on S3 buckets",
+ "Checks": [
+ "s3_bucket_no_mfa_delete"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.1 Simple Storage Service (S3)",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Once MFA Delete is enabled on your sensitive and classified S3 bucket, it requires the user to provide two forms of authentication.",
+ "RationaleStatement": "Adding MFA delete to an S3 bucket requires additional authentication when you change the version state of your bucket or delete an object version, adding another layer of security in the event your security credentials are compromised or unauthorized access is granted.",
+ "ImpactStatement": "Enabling MFA delete on an S3 bucket could require additional administrator oversight. Enabling MFA delete may impact other services that automate the creation and/or deletion of S3 buckets.",
+ "RemediationProcedure": "Perform the steps below to enable MFA delete on an S3 bucket: **Note:** - You cannot enable MFA Delete using the AWS Management Console; you must use the AWS CLI or API. - You must use your 'root' account to enable MFA Delete on S3 buckets. **From Command line:** 1. Run the s3api `put-bucket-versioning` command: ``` aws s3api put-bucket-versioning --profile my-root-profile --bucket Bucket_Name --versioning-configuration Status=Enabled,MFADelete=Enabled --mfa “arn:aws:iam::aws_account_id:mfa/root-account-mfa-device passcode” ```",
+ "AuditProcedure": "Perform the steps below to confirm that MFA delete is configured on an S3 bucket: **From Console:** 1. Login to the S3 console at `https://console.aws.amazon.com/s3/`. 2. Click the `check` box next to the name of the bucket you want to confirm. 3. In the window under `Properties`: - Confirm that Versioning is `Enabled` - Confirm that MFA Delete is `Enabled` **From Command Line:** 1. Run the `get-bucket-versioning` command: ``` aws s3api get-bucket-versioning --bucket my-bucket ``` Example output: ``` <VersioningConfiguration xmlns=http://s3.amazonaws.com/doc/2006-03-01/> <Status>Enabled</Status> <MfaDelete>Enabled</MfaDelete> </VersioningConfiguration> ``` If the console or CLI output does not show that Versioning and MFA Delete are `enabled`, please refer to the remediation below.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete:https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMFADelete.html:https://aws.amazon.com/blogs/security/securing-access-to-aws-using-mfa-part-3/:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_lost-or-broken.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.3",
+ "Description": "Ensure all data in Amazon S3 has been discovered, classified, and secured when necessary",
+ "Checks": [
+ "macie_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.1 Simple Storage Service (S3)",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Amazon S3 buckets can contain sensitive data that, for security purposes, should be discovered, monitored, classified, and protected. Macie, along with other third-party tools, can automatically provide an inventory of Amazon S3 buckets.",
+ "RationaleStatement": "Using a cloud service or third-party software to continuously monitor and automate the process of data discovery and classification for S3 buckets through machine learning and pattern matching is a strong defense in protecting that information. Amazon Macie is a fully managed data security and privacy service that uses machine learning and pattern matching to discover and protect your sensitive data in AWS.",
+ "ImpactStatement": "There is a cost associated with using Amazon Macie, and there is typically a cost associated with third-party tools that perform similar processes and provide protection.",
+ "RemediationProcedure": "Perform the steps below to enable and configure Amazon Macie: **From Console:** 1. Log on to the Macie console at `https://console.aws.amazon.com/macie/`. 2. Click `Get started`. 3. Click `Enable Macie`. Set up a repository for sensitive data discovery results: 1. In the left pane, under Settings, click `Discovery results`. 2. Make sure `Create bucket` is selected. 3. Create a bucket and enter a name for it. The name must be unique across all S3 buckets, and it must start with a lowercase letter or a number. 4. Click `Advanced`. 5. For block all public access, make sure `Yes` is selected. 6. For KMS encryption, specify the AWS KMS key that you want to use to encrypt the results. The key must be a symmetric customer master key (CMK) that is in the same region as the S3 bucket. 7. Click `Save`. Create a job to discover sensitive data: 1. In the left pane, click `S3 buckets`. Macie displays a list of all the S3 buckets for your account. 2. Check the box for each bucket that you want Macie to analyze as part of the job. 3. Click `Create job`. 4. Click `Quick create`. 5. For the Name and Description step, enter a name and, optionally, a description of the job. 6. Click `Next`. 7. For the Review and create step, click `Submit`. Review your findings: 1. In the left pane, click `Findings`. 2. To view the details of a specific finding, choose any field other than the check box for the finding. If you are using a third-party tool to manage and protect your S3 data, follow the vendor documentation for implementing and configuring that tool.",
+ "AuditProcedure": "Perform the following steps to determine if Macie is running: **From Console:** 1. Login to the Macie console at https://console.aws.amazon.com/macie/. 2. In the left hand pane, click on `By job` under findings. 3. Confirm that you have a job set up for your S3 buckets. When you log into the Macie console, if you are not taken to the summary page and do not have a job set up and running, then refer to the remediation procedure below. If you are using a third-party tool to manage and protect your S3 data, you meet this recommendation.",
+ "AdditionalInformation": "",
+ "References": "https://aws.amazon.com/macie/getting-started/:https://docs.aws.amazon.com/workspaces/latest/adminguide/data-protection.html:https://docs.aws.amazon.com/macie/latest/user/data-classification.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.4",
+ "Description": "Ensure that S3 is configured with 'Block Public Access' enabled",
+ "Checks": [
+ "s3_bucket_level_public_access_block",
+ "s3_account_level_public_access_blocks"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.1 Simple Storage Service (S3)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Amazon S3 provides `Block public access (bucket settings)` and `Block public access (account settings)` to help you manage public access to Amazon S3 resources. By default, S3 buckets and objects are created with public access disabled. However, an IAM principal with sufficient S3 permissions can enable public access at the bucket and/or object level. While enabled, `Block public access (bucket settings)` prevents an individual bucket and its contained objects from becoming publicly accessible. Similarly, `Block public access (account settings)` prevents all buckets and their contained objects from becoming publicly accessible across the entire account.",
+ "RationaleStatement": "Amazon S3 `Block public access (bucket settings)` prevents the accidental or malicious public exposure of data contained within the respective bucket(s). Amazon S3 `Block public access (account settings)` prevents the accidental or malicious public exposure of data contained within all buckets of the respective AWS account. Whether to block public access to all or some buckets is an organizational decision that should be based on data sensitivity, least privilege, and use case.",
+ "ImpactStatement": "When you apply Block Public Access settings to an account, the settings apply to all AWS regions globally. The settings may not take effect in all regions immediately or simultaneously, but they will eventually propagate to all regions.",
+ "RemediationProcedure": "**If utilizing Block Public Access (bucket settings)** **From Console:** 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Select the check box next to a bucket. 3. Click 'Edit public access settings'. 4. Click 'Block all public access' 5. Repeat for all the buckets in your AWS account that contain sensitive data. **From Command Line:** 1. List all of the S3 buckets: ``` aws s3 ls ``` 2. Enable Block Public Access on a specific bucket: ``` aws s3api put-public-access-block --bucket <bucket-name> --public-access-block-configuration BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true ``` **If utilizing Block Public Access (account settings)** **From Console:** If the output reads `true` for the separate configuration settings, then Block Public Access is enabled on the account. 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Click `Block Public Access (account settings)`. 3. Click `Edit` to change the block public access settings for all the buckets in your AWS account. 4. Update the settings and click `Save`. For details about each setting, pause on the `i` icons. 5. When you're asked for confirmation, enter `confirm`. Then click `Confirm` to save your changes. **From Command Line:** To enable Block Public Access for this account, run the following command: ``` aws s3control put-public-access-block --public-access-block-configuration BlockPublicAcls=true, IgnorePublicAcls=true, BlockPublicPolicy=true, RestrictPublicBuckets=true --account-id <account-id> ```",
+ "AuditProcedure": "**If utilizing Block Public Access (bucket settings)** **From Console:** 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Select the check box next to a bucket. 3. Click on 'Edit public access settings'. 4. Ensure that the block public access settings are configured appropriately for this bucket. 5. Repeat for all the buckets in your AWS account. **From Command Line:** 1. List all of the S3 buckets: ``` aws s3 ls ``` 2. Find the public access settings for a specific bucket: ``` aws s3api get-public-access-block --bucket <bucket-name> ``` Output if Block Public Access is enabled: ``` { PublicAccessBlockConfiguration: { BlockPublicAcls: true, IgnorePublicAcls: true, BlockPublicPolicy: true, RestrictPublicBuckets: true } } ``` If the output reads `false` for the separate configuration settings, then proceed with the remediation. **If utilizing Block Public Access (account settings)** **From Console:** 1. Login to the AWS Management Console and open the Amazon S3 console using https://console.aws.amazon.com/s3/. 2. Choose `Block public access (account settings)`. 3. Ensure that the block public access settings are configured appropriately for your AWS account. **From Command Line:** To check the block public access settings for this account, run the following command: `aws s3control get-public-access-block --account-id <account-id> --region <region-name>` Output if Block Public Access is enabled: ``` { PublicAccessBlockConfiguration: { IgnorePublicAcls: true, BlockPublicPolicy: true, BlockPublicAcls: true, RestrictPublicBuckets: true } } ``` If the output reads `false` for the separate configuration settings, then proceed with the remediation.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonS3/latest/user-guide/block-public-access-account.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.1",
+ "Description": "Ensure that encryption-at-rest is enabled for RDS instances",
+ "Checks": [
+ "rds_instance_storage_encrypted"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.2 Relational Database Service (RDS)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Amazon RDS encrypted DB instances use the industry-standard AES-256 encryption algorithm to encrypt your data on the server that hosts your Amazon RDS DB instances. After your data is encrypted, Amazon RDS handles the authentication of access and the decryption of your data transparently, with minimal impact on performance.",
+ "RationaleStatement": "Databases are likely to hold sensitive and critical data; therefore, it is highly recommended to implement encryption to protect your data from unauthorized access or disclosure. With RDS encryption enabled, the data stored on the instance's underlying storage, the automated backups, read replicas, and snapshots are all encrypted.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and open the RDS dashboard at https://console.aws.amazon.com/rds/. 2. In the left navigation panel, click on `Databases`. 3. Select the Database instance that needs to be encrypted. 4. Click the `Actions` button placed at the top right and select `Take Snapshot`. 5. On the Take Snapshot page, enter the name of the database for which you want to take a snapshot in the `Snapshot Name` field and click on `Take Snapshot`. 6. Select the newly created snapshot, click the `Action` button placed at the top right, and select `Copy snapshot` from the Action menu. 7. On the Make Copy of DB Snapshot page, perform the following: - In the `New DB Snapshot Identifier` field, enter a name for the new snapshot. - Check `Copy Tags`. The new snapshot must have the same tags as the source snapshot. - Select `Yes` from the `Enable Encryption` dropdown list to enable encryption. You can choose to use the AWS default encryption key or a custom key from the Master Key dropdown list. 8. Click `Copy Snapshot` to create an encrypted copy of the selected instance's snapshot. 9. Select the new Snapshot Encrypted Copy and click the `Action` button located at the top right. Then, select the `Restore Snapshot` option from the Action menu. This will restore the encrypted snapshot to a new database instance. 10. On the Restore DB Instance page, enter a unique name for the new database instance in the DB Instance Identifier field. 11. Review the instance configuration details and click `Restore DB Instance`. 12. As the new instance provisioning process is completed, you can update the application configuration to refer to the endpoint of the new encrypted database instance. Once the database endpoint is changed at the application level, you can remove the unencrypted instance. **From Command Line:** 1. Run the `describe-db-instances` command to list the names of all RDS database instances in the selected AWS region. The command output should return database instance identifiers: ``` aws rds describe-db-instances --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. Check if the specified RDS instance is encrypted. If it shows false, it means it is not yet encrypted: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-name> --query 'DBInstances[*].StorageEncrypted' ``` 3. Run the `create-db-snapshot` command to create a snapshot for a selected database instance. The command output will return the `new snapshot` with name DB Snapshot Name: ``` aws rds create-db-snapshot --region <region-name> --db-snapshot-identifier <db-snapshot-name> --db-instance-identifier <db-name> ``` 4. Now run the `list-aliases` command to list the KMS key aliases available in a specified region. The command output should return each `key alias currently available`. For our RDS encryption activation process, locate the ID of the AWS default KMS key: ``` aws kms list-aliases --region <region-name> ``` 5. Run the `copy-db-snapshot` command using the default KMS key ID for the RDS instances returned earlier to create an encrypted copy of the database instance snapshot. The command output will return the `encrypted instance snapshot configuration`: ``` aws rds copy-db-snapshot --region <region-name> --source-db-snapshot-identifier <db-snapshot-name> --target-db-snapshot-identifier <db-snapshot-name-encrypted> --copy-tags --kms-key-id <kms-id-for-rds> ``` 6. Run the `restore-db-instance-from-db-snapshot` command to restore the encrypted snapshot created in the previous step to a new database instance. If successful, the command output should return the configuration of the new encrypted database instance. If using the default VPC for the database network: ``` aws rds restore-db-instance-from-db-snapshot --region <region-name> --db-instance-identifier <db-name-encrypted> --db-snapshot-identifier <db-snapshot-name-encrypted> ``` If you created your own VPC and Subnets, you need to create a DB subnet group: ``` aws rds create-db-subnet-group --db-subnet-group-name <db-subnet-group-name> --db-subnet-group-description <db-subnet-group-description> --subnet-ids '[\"<subnet-id-1>\",\"<subnet-id-2>\",\"<subnet-id-3>\"]' ``` Restore the encrypted snapshot to an RDS database instance using the specified DB subnet group. The new instance will be encrypted using the KMS key specified during the snapshot copy: ``` aws rds restore-db-instance-from-db-snapshot --region <region-name> --db-subnet-group-name <db-subnet-group-name> --db-instance-identifier <db-name-encrypted> --db-snapshot-identifier <db-snapshot-name-encrypted> ``` 7. Run the `describe-db-instances` command to list all RDS database names available in the selected AWS region. The output will return the database instance identifier names. Select the encrypted database name that we just created, `db-name-encrypted`: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 8. Run the `describe-db-instances` command again using the RDS instance identifier returned earlier to determine if the selected database instance is encrypted. The command output should indicate that the encryption status is `True`: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-name-encrypted> --query 'DBInstances[*].StorageEncrypted' ```",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and open the RDS dashboard at https://console.aws.amazon.com/rds/. 2. In the navigation pane, under RDS dashboard, click `Databases`. 3. Select the RDS instance that you want to examine. 4. Click `Instance Name` to see details, then select the `Configuration` tab. 5. Under Configuration Details, in the Storage pane, search for the `Encryption Enabled` status. 6. If the current status is set to `Disabled`, encryption is not enabled for the selected RDS database instance. 7. Repeat steps 2 to 6 to verify the encryption status of other RDS instances in the same region. 8. Change the region from the top of the navigation bar, and repeat the audit steps for other regions. **From Command Line:** 1. Run the `describe-db-instances` command to list all the RDS database instance names available in the selected AWS region. The output will return each database instance identifier (name): ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. Run the `describe-db-instances` command again, using an RDS instance identifier returned from step 1, to determine if the selected database instance is encrypted. The output should return the encryption status `True` or `False`: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-name> --query 'DBInstances[*].StorageEncrypted' ``` 3. If the StorageEncrypted parameter value is `False`, encryption is not enabled for the selected RDS database instance. 4. Repeat steps 1 to 3 to audit each RDS instance, and change the region to verify RDS instances in other regions.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.html:https://aws.amazon.com/blogs/database/selecting-the-right-encryption-options-for-amazon-rds-and-amazon-aurora-database-engines/#:~:text=With%20RDS%2Dencrypted%20resources%2C%20data,transparent%20to%20your%20database%20engine.:https://aws.amazon.com/rds/features/security/:https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-subnet-group.html",
+ "DefaultValue": "By default, Amazon RDS instances are created without encryption at rest. Encryption must be explicitly enabled at instance creation or by restoring from an encrypted snapshot."
+ }
+ ]
+ },
+ {
+ "Id": "3.2.2",
+ "Description": "Ensure the Auto Minor Version Upgrade feature is enabled for RDS instances",
+ "Checks": [
+ "rds_instance_minor_version_upgrade_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.2 Relational Database Service (RDS)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that RDS database instances have the Auto Minor Version Upgrade flag enabled to automatically receive minor engine upgrades during the specified maintenance window. This way, RDS instances can obtain new features, bug fixes, and security patches for their database engines.",
+ "RationaleStatement": "AWS RDS will occasionally deprecate minor engine versions and provide new ones for upgrades. When the last version number within a release is replaced, the changed version is considered minor. With the Auto Minor Version Upgrade feature enabled, version upgrades will occur automatically during the specified maintenance window, allowing your RDS instances to receive new features, bug fixes, and security patches for their database engines.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** 1. Log in to the AWS management console and navigate to the RDS dashboard at https://console.aws.amazon.com/rds/. 2. In the left navigation panel, click `Databases`. 3. Select the RDS instance that you want to update. 4. Click on the `Modify` button located at the top right side. 5. On the `Modify DB Instance: <instance identifier>` page, In the `Maintenance` section, select `Auto minor version upgrade` and click the `Yes` radio button. 6. At the bottom of the page, click `Continue`, and check `Apply Immediately` to apply the changes immediately, or select `Apply during the next scheduled maintenance window` to avoid any downtime. 7. Review the changes and click `Modify DB Instance`. The instance status should change from available to modifying and back to available. Once the feature is enabled, the `Auto Minor Version Upgrade` status should change to `Yes`. **From Command Line:** 1. Run the `describe-db-instances` command to list all RDS database instance names available in the selected AWS region: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. The command output should return each database instance identifier. 3. Run the `modify-db-instance` command to modify the configuration of a selected RDS instance. This command will apply the changes immediately. Remove `--apply-immediately` to apply changes during the next scheduled maintenance window and avoid any downtime: ``` aws rds modify-db-instance --region <region-name> --db-instance-identifier <db-instance-identifier> --auto-minor-version-upgrade --apply-immediately ``` 4. The command output should reveal the new configuration metadata for the RDS instance, including the `AutoMinorVersionUpgrade` parameter value. 5. Run the `describe-db-instances` command to check if the Auto Minor Version Upgrade feature has been successfully enabled: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-instance-identifier> --query 'DBInstances[*].AutoMinorVersionUpgrade' ``` 6. The command output should return the feature's current status set to `true`, indicating that the feature is `enabled`, and that the minor engine upgrades will be applied to the selected RDS instance.",
+ "AuditProcedure": "**From Console:** 1. Log in to the AWS management console and navigate to the RDS dashboard at https://console.aws.amazon.com/rds/. 2. In the left navigation panel, click `Databases`. 3. Select the RDS instance that you want to examine. 4. Click on the `Maintenance and backups` panel. 5. Under the `Maintenance` section, search for the Auto Minor Version Upgrade status. - If the current status is `Disabled`, it means that the feature is not enabled, and the minor engine upgrades released will not be applied to the selected RDS instance. **From Command Line:** 1. Run the `describe-db-instances` command to list all RDS database names available in the selected AWS region: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. The command output should return each database instance identifier. 3. Run the `describe-db-instances` command again using a RDS instance identifier returned earlier to determine the Auto Minor Version Upgrade status for the selected instance: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-instance-identifier> --query 'DBInstances[*].AutoMinorVersionUpgrade' ``` 4. The command output should return the current status of the feature. If the current status is set to `true`, the feature is enabled and the minor engine upgrades will be applied to the selected RDS instance.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_RDS_Managing.html:https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html:https://aws.amazon.com/rds/faqs/",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.3",
+ "Description": "Ensure that RDS instances are not publicly accessible",
+ "Checks": [
+ "rds_instance_no_public_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.2 Relational Database Service (RDS)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure and verify that the RDS database instances provisioned in your AWS account restrict unauthorized access in order to minimize security risks. To restrict access to any RDS database instance, you must disable the Publicly Accessible flag for the database and update the VPC security group associated with the instance.",
+ "RationaleStatement": "Ensure that no public-facing RDS database instances are provisioned in your AWS account, and restrict unauthorized access in order to minimize security risks. When the RDS instance allows unrestricted access (0.0.0.0/0), anyone and anything on the Internet can establish a connection to your database, which can increase the opportunity for malicious activities such as brute force attacks, PostgreSQL injections, or DoS/DDoS attacks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** 1. Log in to the AWS management console and navigate to the RDS dashboard at https://console.aws.amazon.com/rds/. 2. Under the navigation panel, on the RDS dashboard, click `Databases`. 3. Select the RDS instance that you want to update. 4. Click `Modify` from the dashboard top menu. 5. On the Modify DB Instance panel, under the `Connectivity` section, click on `Additional connectivity configuration` and update the value for `Publicly Accessible` to `Not publicly accessible` to restrict public access. 6. Follow the below steps to update subnet configurations: - Select the `Connectivity and security` tab, and click the VPC attribute value inside the `Networking` section. - Select the `Details` tab from the VPC dashboard's bottom panel and click the Route table configuration attribute value. - On the Route table details page, select the Routes tab from the dashboard's bottom panel and click `Edit routes`. - On the Edit routes page, update the Destination of Target which is set to `igw-xxxxx` and click `Save` routes. 7. On the Modify DB Instance panel, click `Continue`, and in the Scheduling of modifications section, perform one of the following actions based on your requirements: - Select `Apply during the next scheduled maintenance window` to apply the changes automatically during the next scheduled maintenance window. - Select `Apply immediately` to apply the changes right away. With this option, any pending modifications will be asynchronously applied as soon as possible, regardless of the maintenance window setting for this RDS database instance. Note that any changes available in the pending modifications queue are also applied. If any of the pending modifications require downtime, choosing this option can cause unexpected downtime for the application. 8. Repeat steps 3-7 for each RDS instance in the current region. 9. Change the AWS region from the navigation bar to repeat the process for other regions. **From Command Line:** 1. Run the `describe-db-instances` command to list all available RDS database identifiers in the selected AWS region: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. The command output should return each database instance identifier. 3. Run the `modify-db-instance` command to modify the configuration of a selected RDS instance, disabling the `Publicly Accessible` flag for that instance. This command uses the `apply-immediately` flag. If you want to avoid any downtime, the `--no-apply-immediately` flag can be used: ``` aws rds modify-db-instance --region <region-name> --db-instance-identifier <db-instance-name> --no-publicly-accessible --apply-immediately ``` 4. The command output should reveal the `PubliclyAccessible` configuration under pending values, to be applied at the specified time. 5. Updating the Internet Gateway destination via the AWS CLI is not currently supported. To update information about the Internet Gateway, please use the AWS Console procedure. 6. Repeat steps 1-5 for each RDS instance provisioned in the current region. 7. Change the AWS region by using the --region filter to repeat the process for other regions.",
+ "AuditProcedure": "**From Console:** 1. Log in to the AWS management console and navigate to the RDS dashboard at https://console.aws.amazon.com/rds/. 2. Under the navigation panel, on the RDS dashboard, click `Databases`. 3. Select the RDS instance that you want to examine. 4. Click `Instance Name` from the dashboard, under `Connectivity and Security`. 5. In the `Security` section, check if the Publicly Accessible flag status is set to `Yes`. 6. Follow the steps below to check database subnet access: - In the `networking` section, click the subnet link under `Subnets`. - The link will redirect you to the VPC Subnets page. - Select the subnet listed on the page and click the `Route Table` tab from the dashboard bottom panel. - If the route table contains any entries with the destination CIDR block set to `0.0.0.0/0` and an `Internet Gateway` attached, the selected RDS database instance was provisioned inside a public subnet; therefore, it is not running within a logically isolated environment and can be accessed from the Internet. 7. Repeat steps 3-6 to determine the configuration of other RDS database instances provisioned in the current region. 8. Change the AWS region from the navigation bar and repeat the audit process for other regions. **From Command Line:** 1. Run the `describe-db-instances` command to list all available RDS database names in the selected AWS region: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. The command output should return each database instance `identifier`. 3. Run the `describe-db-instances` command again, using the `PubliclyAccessible` parameter as a query filter to reveal the status of the database instance's Publicly Accessible flag: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-instance-name> --query 'DBInstances[*].PubliclyAccessible' ``` 4. Check the Publicly Accessible parameter status. If the Publicly Accessible flag is set to `Yes`, then the selected RDS database instance is publicly accessible and insecure. Follow the steps mentioned below to check database subnet access. 5. Run the `describe-db-instances` command again using the RDS database instance identifier that you want to check, along with the appropriate filtering to describe the VPC subnet(s) associated with the selected instance: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-instance-name> --query 'DBInstances[*].DBSubnetGroup.Subnets[]' ``` - The command output should list the subnets available in the selected database subnet group. 6. Run the `describe-route-tables` command using the ID of the subnet returned in the previous step to describe the routes of the VPC route table associated with the selected subnet: ``` aws ec2 describe-route-tables --region <region-name> --filters Name=association.subnet-id,Values=<subnet-id> --query 'RouteTables[*].Routes[]' ``` - If the command returns the route table associated with the database instance subnet ID, check the values of the `GatewayId` and `DestinationCidrBlock` attributes returned in the output. If the route table contains any entries with the `GatewayId` value set to `igw-xxxxxxxx` and the `DestinationCidrBlock` value set to `0.0.0.0/0`, the selected RDS database instance was provisioned within a public subnet. - Or, if the command returns empty results, the route table is implicitly associated with the subnet; therefore, the audit process continues with the next step. 7. Run the `describe-db-instances` command again using the RDS database instance identifier that you want to check, along with the appropriate filtering to describe the VPC ID associated with the selected instance: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-instance-name> --query 'DBInstances[*].DBSubnetGroup.VpcId' ``` - The command output should show the VPC ID in the selected database subnet group. 8. Now run the `describe-route-tables` command using the ID of the VPC returned in the previous step to describe the routes of the VPC's main route table that is implicitly associated with the selected subnet: ``` aws ec2 describe-route-tables --region <region-name> --filters Name=vpc-id,Values=<vpc-id> Name=association.main,Values=true --query 'RouteTables[*].Routes[]' ``` - The command output returns the VPC main route table implicitly associated with the database instance subnet ID. Check the values of the `GatewayId` and `DestinationCidrBlock` attributes returned in the output. If the route table contains any entries with the `GatewayId` value set to `igw-xxxxxxxx` and the `DestinationCidrBlock` value set to `0.0.0.0/0`, the selected RDS database instance was provisioned inside a public subnet; therefore, it is not running within a logically isolated environment and does not adhere to AWS security best practices.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.html:https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html:https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html:https://aws.amazon.com/rds/faqs/",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.4",
+ "Description": "Ensure Multi-AZ deployments are used for enhanced availability in Amazon RDS",
+ "Checks": [
+ "rds_cluster_multi_az",
+ "rds_instance_multi_az"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.2 Relational Database Service (RDS)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Amazon RDS offers Multi-AZ deployments that provide enhanced availability and durability for your databases, using synchronous replication to replicate data to a standby instance in a different Availability Zone (AZ). In the event of an infrastructure failure, Amazon RDS automatically fails over to the standby to minimize downtime and ensure business continuity.",
+ "RationaleStatement": "Database availability is crucial for maintaining service uptime, particularly for applications that are critical to the business. Implementing Multi-AZ deployments with Amazon RDS ensures that your databases are protected against unplanned outages due to hardware failures, network issues, or other disruptions. This configuration enhances both the availability and durability of your database, making it a highly recommended practice for production environments.",
+ "ImpactStatement": "Multi-AZ deployments may increase costs due to the additional resources required to maintain a standby instance; however, the benefits of increased availability and reduced risk of downtime outweigh these costs for critical applications.",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and open the RDS dashboard at [AWS RDS Console](https://console.aws.amazon.com/rds/). 2. In the left navigation pane, click on `Databases`. 3. Select the database instance that needs Multi-AZ deployment to be enabled. 4. Click the `Modify` button at the top right. 5. Scroll down to the `Availability & Durability` section. 6. Under `Multi-AZ deployment`, select `Yes` to enable. 7. Review the changes and click `Continue`. 8. On the `Review` page, choose `Apply immediately` to make the change without waiting for the next maintenance window, or `Apply during the next scheduled maintenance window`. 9. Click `Modify DB Instance` to apply the changes. **From Command Line:** 1. Run the following command to modify the RDS instance and enable Multi-AZ: ``` aws rds modify-db-instance --region <region-name> --db-instance-identifier <db-name> --multi-az --apply-immediately ``` 2. Confirm that the Multi-AZ deployment is enabled by running the following command: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-name> --query 'DBInstances[*].MultiAZ' ``` - The output should return `True`, indicating that Multi-AZ is enabled. 3. Repeat the procedure for other instances as necessary.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and open the RDS dashboard at [AWS RDS Console](https://console.aws.amazon.com/rds/). 2. In the navigation pane, under `Databases`, select the RDS instance you want to examine. 3. Click the `Instance Name` to see details, then navigate to the `Configuration` tab. 4. Under the `Availability & Durability` section, check the `Multi-AZ` status. - If Multi-AZ deployment is enabled, it will display `Yes`. - If it is disabled, the status will display `No`. 5. Repeat steps 2-4 to verify the Multi-AZ status of other RDS instances in the same region. 6. Change the region from the top of the navigation bar and repeat the audit for other regions. **From Command Line:** 1. Run the following command to list all RDS instances in the selected AWS region: ``` aws rds describe-db-instances --region <region-name> --query 'DBInstances[*].DBInstanceIdentifier' ``` 2. Run the following command using the instance identifier returned earlier to check the Multi-AZ status: ``` aws rds describe-db-instances --region <region-name> --db-instance-identifier <db-name> --query 'DBInstances[*].MultiAZ' ``` - If the output is `True`, Multi-AZ is enabled. - If the output is `False`, Multi-AZ is not enabled. 3. Repeat steps 1 and 2 to audit each RDS instance, and change regions to verify in other regions.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.3.1",
+ "Description": "Ensure that encryption is enabled for EFS file systems",
+ "Checks": [
+ "efs_encryption_at_rest_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Storage",
+ "SubSection": "3.3 Elastic File System (EFS)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "EFS data should be encrypted at rest using AWS KMS (Key Management Service).",
+ "RationaleStatement": "Data should be encrypted at rest to reduce the risk of a data breach via direct access to the storage device.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**It is important to note that EFS file system data-at-rest encryption must be turned on when creating the file system. If an EFS file system has been created without data-at-rest encryption enabled, then you must create another EFS file system with the correct configuration and transfer the data.** **Steps to create an EFS file system with data encrypted at rest:** **From Console:** 1. Login to the AWS Management Console and Navigate to the `Elastic File System (EFS)` dashboard. 2. Select `File Systems` from the left navigation panel. 3. Click the `Create File System` button from the dashboard top menu to start the file system setup process. 4. On the `Configure file system access` configuration page, perform the following actions: - Choose an appropriate VPC from the VPC dropdown list. - Within the `Create mount targets` section, check the boxes for all of the Availability Zones (AZs) within the selected VPC. These will be your mount targets. - Click `Next step` to continue. 5. Perform the following on the `Configure optional settings` page: - Create `tags` to describe your new file system. - Choose `performance mode` based on your requirements. - Check the `Enable encryption` box and choose `aws/elasticfilesystem` from the `Select KMS master key` dropdown list to enable encryption for the new file system, using the default master key provided and managed by AWS KMS. - Click `Next step` to continue. 6. Review the file system configuration details on the `review and create` page and then click `Create File System` to create your new AWS EFS file system. 7. Copy the data from the old unencrypted EFS file system onto the newly created encrypted file system. 8. Remove the unencrypted file system as soon as your data migration to the newly created encrypted file system is completed. 9. Change the AWS region from the navigation bar and repeat the entire process for the other AWS regions. **From CLI:** 1. Run the `describe-file-systems` command to view the configuration information for the selected unencrypted file system identified in the Audit steps: ``` aws efs describe-file-systems --region <region> --file-system-id <file-system-id> ``` 2. The command output should return the configuration information. 3. To provision a new AWS EFS file system, you need to generate a universally unique identifier (UUID) to create the token required by the `create-file-system` command. To create the required token, you can use a randomly generated UUID from https://www.uuidgenerator.net. 4. Run the `create-file-system` command using the unique token created at the previous step: ``` aws efs create-file-system --region <region> --creation-token <uuid> --performance-mode generalPurpose --encrypted ``` 5. The command output should return the new file system configuration metadata. 6. Run the `create-mount-target` command using the EFS file system ID returned from step 4 as the identifier and the ID of the Availability Zone (AZ) that will represent the mount target: ``` aws efs create-mount-target --region <region> --file-system-id <file-system-id> --subnet-id <subnet-id> ``` 7. The command output should return the new mount target metadata. 8. Now you can mount your file system from an EC2 instance. 9. Copy the data from the old unencrypted EFS file system to the newly created encrypted file system. 10. Remove the unencrypted file system as soon as your data migration to the newly created encrypted file system is completed: ``` aws efs delete-file-system --region <region> --file-system-id <unencrypted-file-system-id> ``` 11. Change the AWS region by updating the --region and repeat the entire process for the other AWS regions.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and Navigate to the Elastic File System (EFS) dashboard. 2. Select `File Systems` from the left navigation panel. 3. Each item on the list has a visible Encrypted field that displays data at rest encryption status. 4. Validate that this field reads `Encrypted` for all EFS file systems in all AWS regions. **From CLI:** 1. Run the `describe-file-systems` command using custom query filters to list the identifiers of all AWS EFS file systems currently available within the selected region: ``` aws efs describe-file-systems --region <region> --output table --query 'FileSystems[*].FileSystemId' ``` 2. The command output should return a table with the requested file system IDs. 3. Run the `describe-file-systems` command using the ID of the file system that you want to examine as `file-system-id` and the necessary query filters: ``` aws efs describe-file-systems --region <region> --file-system-id <file-system-id> --query 'FileSystems[*].Encrypted' ``` 4. The command output should return the file system encryption status as `true` or `false`. If the returned value is `false`, the selected AWS EFS file system is not encrypted and if the returned value is `true`, the selected AWS EFS file system is encrypted.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/efs/latest/ug/encryption-at-rest.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/efs/index.html#efs",
+ "DefaultValue": "EFS file system data is encrypted at rest by default when creating a file system through the Console. However, encryption at rest is not enabled by default when creating a new file system using the AWS CLI, API, or SDKs."
+ }
+ ]
+ },
+ {
+ "Id": "4.1",
+ "Description": "Ensure CloudTrail is enabled in all regions",
+ "Checks": [
+ "cloudtrail_multi_region_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "AWS CloudTrail is a web service that records AWS API calls for your account and delivers log files to you. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service. CloudTrail provides a history of AWS API calls for an account, including API calls made via the Management Console, SDKs, command line tools, and higher-level AWS services (such as CloudFormation).",
+ "RationaleStatement": "The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. Additionally, - ensuring that a multi-region trail exists will help detect unexpected activity occurring in otherwise unused regions - ensuring that a multi-region trail exists will ensure that `Global Service Logging` is enabled for a trail by default to capture recordings of events generated on AWS global services - for a multi-region trail, ensuring that management events are configured for all types of Read/Writes ensures the recording of management operations that are performed on all resources in an AWS account",
+ "ImpactStatement": "S3 lifecycle features can be used to manage the accumulation and management of logs over time. See the following AWS resource for more information on these features: 1. https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html",
+ "RemediationProcedure": "Perform the following to enable global (Multi-region) CloudTrail logging: **From Console:** 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail). 2. Click on `Trails` in the left navigation pane. 3. Click `Get Started Now` if it is presented, then: - Click `Add new trail`. - Enter a trail name in the `Trail name` box. - A trail created in the console is a multi-region trail by default. - Specify an S3 bucket name in the `S3 bucket` box. - Specify the AWS KMS alias under the `Log file SSE-KMS encryption` section, or create a new key. - Click `Next`. 4. Ensure the `Management events` check box is selected. 5. Ensure both `Read` and `Write` are checked under API activity. 6. Click `Next`. 7. Review your trail settings and click `Create trail`. **From Command Line:** Create a multi-region trail: ``` aws cloudtrail create-trail --name <trail-name> --bucket-name <s3-bucket-for-cloudtrail> --is-multi-region-trail ``` Enable multi-region on an existing trail: ``` aws cloudtrail update-trail --name <trail-name> --is-multi-region-trail ``` **Note:** Creating a CloudTrail trail via the CLI without providing any overriding options configures all `read` and `write` `Management Events` to be logged by default.",
+ "AuditProcedure": "Perform the following to determine if CloudTrail is enabled for all regions: **From Console:** 1. Sign in to the AWS Management Console and open the CloudTrail console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail) 2. Click on `Trails` in the left navigation pane - You will be presented with a list of trails across all regions 3. Ensure that at least one Trail has `Yes` specified in the `Multi-region trail` column 4. Click on a trail via the link in the `Name` column 5. Ensure `Logging` is set to `ON` 6. Ensure `Multi-region trail` is set to `Yes` 7. In the section `Management Events`, ensure that `API activity` set to `ALL` **From Command Line:** 1. List all trails: ``` aws cloudtrail describe-trails ``` 2. Ensure `IsMultiRegionTrail` is set to `true`: ``` aws cloudtrail get-trail-status --name <trail-name> ``` 3. Ensure `IsLogging` is set to `true`: ``` aws cloudtrail get-event-selectors --trail-name <trail-name> ``` 4. Ensure there is at least one `fieldSelector` for a trail that equals `Management`: - This should NOT output any results for Field: readOnly. If either `true` or `false` is returned, one of the checkboxes (`read` or `write`) is not selected. Example of correct output: ``` TrailARN: <your_trail_ARN>, AdvancedEventSelectors: [ { Name: Management events selector, FieldSelectors: [ { Field: eventCategory, Equals: [ Management ] ```",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-management-events:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/logging-management-and-data-events-with-cloudtrail.html?icmpid=docs_cloudtrail_console#logging-management-events:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-supported-services.html#cloud-trail-supported-services-data-events",
+ "DefaultValue": "Not Enabled"
+ }
+ ]
+ },
+ {
+ "Id": "4.2",
+ "Description": "Ensure CloudTrail log file validation is enabled",
+ "Checks": [
+ "cloudtrail_log_file_validation_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "CloudTrail log file validation creates a digitally signed digest file containing a hash of each log that CloudTrail writes to S3. These digest files can be used to determine whether a log file was changed, deleted, or remained unchanged after CloudTrail delivered the log. It is recommended that file validation be enabled for all CloudTrails.",
+ "RationaleStatement": "Enabling log file validation will provide additional integrity checks for CloudTrail logs.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to enable log file validation on a given trail: **From Console:** 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail). 2. Click on `Trails` in the left navigation pane. 3. Click on the target trail. 4. Within the `General details` section, click `edit`. 5. Under `Advanced settings`, check the `enable` box under `Log file validation`. 6. Click `Save changes`. **From Command Line:** Enable log file validation on a trail: ``` aws cloudtrail update-trail --name <trail_name> --enable-log-file-validation ``` Note that periodic validation of logs using these digests can be carried out by running the following command: ``` aws cloudtrail validate-logs --trail-arn <trail_arn> --start-time <start_time> --end-time <end_time> ```",
+ "AuditProcedure": "Perform the following on each trail to determine if log file validation is enabled: **From Console:** 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail). 2. Click on `Trails` in the left navigation pane. 3. For every trail: - Click on a trail via the link in the `Name` column. - Under the `General details` section, ensure `Log file validation` is set to `Enabled`. **From Command Line:** List all trails: ``` aws cloudtrail describe-trails ``` Ensure `LogFileValidationEnabled` is set to `true` for each trail.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-log-file-validation-enabling.html",
+ "DefaultValue": "Not Enabled"
+ }
+ ]
+ },
+ {
+ "Id": "4.3",
+ "Description": "Ensure AWS Config is enabled in all regions",
+ "Checks": [
+ "config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS Config is a web service that performs configuration management of supported AWS resources within your account and delivers log files to you. The recorded information includes the configuration items (AWS resources), relationships between configuration items (AWS resources), and any configuration changes between resources. It is recommended that AWS Config be enabled in all regions.",
+ "RationaleStatement": "The AWS configuration item history captured by AWS Config enables security analysis, resource change tracking, and compliance auditing.",
+ "ImpactStatement": "Enabling AWS Config in all regions provides comprehensive visibility into resource configurations, enhancing security and compliance monitoring. However, this may incur additional costs and require proper configuration management.",
+ "RemediationProcedure": "To implement AWS Config configuration: **From Console:** 1. Select the region you want to focus on in the top right of the console. 2. Click `Services`. 3. Click `Config`. 4. If a Config Recorder is enabled in this region, navigate to the Settings page from the navigation menu on the left-hand side. If a Config Recorder is not yet enabled in this region, select Get Started. 5. Select Record all resources supported in this region. 6. Choose to include global resources (IAM resources). 7. Specify an S3 bucket in the same account or in another managed AWS account. 8. Create an SNS Topic from the same AWS account or another managed AWS account. **From Command Line:** 1. Ensure there is an appropriate S3 bucket, SNS topic, and IAM role per the [AWS Config Service prerequisites](http://docs.aws.amazon.com/config/latest/developerguide/gs-cli-prereq.html). 2. Run this command to create a new configuration recorder: ``` aws configservice put-configuration-recorder --configuration-recorder name=<config-recorder-name>,roleARN=arn:aws:iam::<account-id>:role/<iam-role> --recording-group allSupported=true,includeGlobalResourceTypes=true ``` 3. Create a delivery channel configuration file locally which specifies the channel attributes, populated from the prerequisites set up previously: ``` { name: <delivery-channel-name>, s3BucketName: <bucket-name>, snsTopicARN: arn:aws:sns:<region>:<account-id>:<sns-topic>, configSnapshotDeliveryProperties: { deliveryFrequency: Twelve_Hours } } ``` 4. Run this command to create a new delivery channel, referencing the json configuration file made in the previous step: ``` aws configservice put-delivery-channel --delivery-channel file://<delivery-channel-file>.json ``` 5. Start the configuration recorder by running the following command: ``` aws configservice start-configuration-recorder --configuration-recorder-name <config-recorder-name> ```",
+ "AuditProcedure": "Process to evaluate AWS Config configuration per region: **From Console:** 1. Sign in to the AWS Management Console and open the AWS Config console at [https://console.aws.amazon.com/config/](https://console.aws.amazon.com/config/). 1. On the top right of the console select the target region. 1. If a Config Recorder is enabled in this region, you should navigate to the Settings page from the navigation menu on the left-hand side. If a Config Recorder is not yet enabled in this region, proceed to the remediation steps. 1. Ensure Record all resources supported in this region is checked. 1. Ensure Include global resources (e.g., AWS IAM resources) is checked, unless it is enabled in another region (this is only required in one region). 1. Ensure the correct S3 bucket has been defined. 1. Ensure the correct SNS topic has been defined. 1. Repeat steps 2 to 7 for each region. **From Command Line:** 1. Run this command to show all AWS Config Recorders and their properties: ``` aws configservice describe-configuration-recorders ``` 2. Evaluate the output to ensure that all recorders have a `recordingGroup` object which includes `allSupported: true`. Additionally, ensure that at least one recorder has `includeGlobalResourceTypes: true`. **Note:** There is one more parameter, ResourceTypes, in the recordingGroup object. We don't need to check it, as whenever we set allSupported to true, AWS enforces the resource types to be empty (ResourceTypes: []). Sample output: ``` { ConfigurationRecorders: [ { recordingGroup: { allSupported: true, resourceTypes: [], includeGlobalResourceTypes: true }, roleARN: arn:aws:iam::<AWS_Account_ID>:role/service-role/<config-role-name>, name: default } ] } ``` 3. Run this command to show the status for all AWS Config Recorders: ``` aws configservice describe-configuration-recorder-status ``` 4. In the output, find recorders with `name` key matching the recorders that were evaluated in step 2. Ensure that they include `recording: true` and `lastStatus: SUCCESS`.",
+ "AdditionalInformation": "",
+ "References": "https://awscli.amazonaws.com/v2/documentation/api/latest/reference/configservice/describe-configuration-recorder-status.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/configservice/describe-configuration-recorders.html:https://docs.aws.amazon.com/config/latest/developerguide/gs-cli-prereq.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.4",
+ "Description": "Ensure that server access logging is enabled on the CloudTrail S3 bucket",
+ "Checks": [
+ "cloudtrail_logs_s3_bucket_access_logging_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Server access logging generates a log that contains access records for each request made to your S3 bucket. An access log record contains details about the request, such as the request type, the resources specified in the request worked, and the time and date the request was processed. It is recommended that server access logging be enabled on the CloudTrail S3 bucket.",
+ "RationaleStatement": "By enabling server access logging on target S3 buckets, it is possible to capture all events that may affect objects within any target bucket. Configuring the logs to be placed in a separate bucket allows access to log information that can be useful in security and incident response workflows.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to enable server access logging: **From Console:** 1. Sign in to the AWS Management Console and open the S3 console at [https://console.aws.amazon.com/s3](https://console.aws.amazon.com/s3). 2. Under `All Buckets` click on the target S3 bucket. 3. Click on `Properties` in the top right of the console. 4. Under `Bucket: <bucket-name>`, click `Logging`. 5. Configure bucket logging: - Check the `Enabled` box. - Select a Target Bucket from the list. - Enter a Target Prefix. 6. Click `Save`. **From Command Line:** 1. Get the name of the S3 bucket that CloudTrail is logging to: ``` aws cloudtrail describe-trails --region <region-name> --query trailList[*].S3BucketName ``` 2. Copy and add the target bucket name at `<bucket-name>`, the prefix for the log file at `<log-file-prefix>`, and optionally add an email address in the following template, then save it as `<file-name>.json`: ``` { LoggingEnabled: { TargetBucket: <bucket-name>, TargetPrefix: <log-file-prefix>, TargetGrants: [ { Grantee: { Type: AmazonCustomerByEmail, EmailAddress: <email-address> }, Permission: FULL_CONTROL } ] } } ``` 3. Run the `put-bucket-logging` command with bucket name and `<file-name>.json` as input; for more information, refer to [put-bucket-logging](https://docs.aws.amazon.com/cli/latest/reference/s3api/put-bucket-logging.html): ``` aws s3api put-bucket-logging --bucket <bucket-name> --bucket-logging-status file://<file-name>.json ```",
+ "AuditProcedure": "Perform the following ensure that the CloudTrail S3 bucket has access logging is enabled: **From Console:** 1. Go to the Amazon CloudTrail console at [https://console.aws.amazon.com/cloudtrail/home](https://console.aws.amazon.com/cloudtrail/home). 2. In the API activity history pane on the left, click `Trails`. 3. In the Trails pane, note the bucket names in the S3 bucket column. 4. Sign in to the AWS Management Console and open the S3 console at [https://console.aws.amazon.com/s3](https://console.aws.amazon.com/s3). 5. Under `All Buckets` click on a target S3 bucket. 6. Click on `Properties` in the top right of the console. 7. Under `Bucket: <bucket-name>`, click `Logging`. 8. Ensure `Enabled` is checked. **From Command Line:** 1. Get the name of the S3 bucket that CloudTrail is logging to: ``` aws cloudtrail describe-trails --query 'trailList[*].S3BucketName' ``` 2. Ensure logging is enabled on the bucket: ``` aws s3api get-bucket-logging --bucket <s3-bucket-for-cloudtrail> ``` Ensure the command does not return an empty output. Sample output for a bucket with logging enabled: ``` { LoggingEnabled: { TargetPrefix: <log-file-prefix>, TargetBucket: <logging-bucket> } } ```",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerLogs.html:https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html",
+ "DefaultValue": "Logging is disabled."
+ }
+ ]
+ },
+ {
+ "Id": "4.5",
+ "Description": "Ensure CloudTrail logs are encrypted at rest using KMS CMKs",
+ "Checks": [
+ "cloudtrail_kms_encryption_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS CloudTrail is a web service that records AWS API calls for an account and makes those logs available to users and resources in accordance with IAM policies. AWS Key Management Service (KMS) is a managed service that helps create and control the encryption keys used to encrypt account data, and uses Hardware Security Modules (HSMs) to protect the security of encryption keys. CloudTrail logs can be configured to leverage server side encryption (SSE) and KMS customer-created master keys (CMK) to further protect CloudTrail logs. It is recommended that CloudTrail be configured to use SSE-KMS.",
+ "RationaleStatement": "Configuring CloudTrail to use SSE-KMS provides additional confidentiality controls on log data, as a given user must have S3 read permission on the corresponding log bucket and must be granted decrypt permission by the CMK policy.",
+ "ImpactStatement": "Customer-created keys incur an additional cost. See https://aws.amazon.com/kms/pricing/ for more information.",
+ "RemediationProcedure": "Perform the following to configure CloudTrail to use SSE-KMS: **From Console:** 1. Sign in to the AWS Management Console and open the CloudTrail console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail). 2. In the left navigation pane, choose `Trails`. 3. Click on a trail. 4. Under the `S3` section, click the edit button (pencil icon). 5. Click `Advanced`. 6. Select an existing CMK from the `KMS key Id` drop-down menu. - **Note:** Ensure the CMK is located in the same region as the S3 bucket. - **Note:** You will need to apply a KMS key policy on the selected CMK in order for CloudTrail, as a service, to encrypt and decrypt log files using the CMK provided. View the AWS documentation for [editing the selected CMK Key policy](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/create-kms-key-policy-for-cloudtrail.html). 7. Click `Save`. 8. You will see a notification message stating that you need to have decryption permissions on the specified KMS key to decrypt log files. 9. Click `Yes`. **From Command Line:** Run the following command to specify a KMS key ID to use with a trail: ``` aws cloudtrail update-trail --name <trail-name> --kms-key-id <cloudtrail-kms-key> ``` Run the following command to attach a key policy to a specified KMS key: ``` aws kms put-key-policy --key-id <cloudtrail-kms-key> --policy <cloudtrail-kms-key-policy> ```",
+ "AuditProcedure": "Perform the following to determine if CloudTrail is configured to use SSE-KMS: **From Console:** 1. Sign in to the AWS Management Console and open the CloudTrail console at [https://console.aws.amazon.com/cloudtrail](https://console.aws.amazon.com/cloudtrail). 2. In the left navigation pane, choose `Trails`. 3. Select a trail. 4. In the `General details` section, select `Edit` to edit the trail configuration. 5. Ensure the box at `Log file SSE-KMS encryption` is checked and that a valid `AWS KMS alias` of a KMS key is entered in the respective text box. **From Command Line:** 1. Run the following command: ``` aws cloudtrail describe-trails ``` 2. For each trail listed, SSE-KMS is enabled if the trail has a `KmsKeyId` property defined.",
+ "AdditionalInformation": "Three statements that need to be added to the CMK policy: 1. Enable CloudTrail to describe CMK properties: ``` { \"Sid\": \"Allow CloudTrail access\", \"Effect\": \"Allow\", \"Principal\": { \"Service\": \"cloudtrail.amazonaws.com\" }, \"Action\": \"kms:DescribeKey\", \"Resource\": \"*\" } ``` 2. Granting encrypt permissions: ``` { \"Sid\": \"Allow CloudTrail to encrypt logs\", \"Effect\": \"Allow\", \"Principal\": { \"Service\": \"cloudtrail.amazonaws.com\" }, \"Action\": \"kms:GenerateDataKey*\", \"Resource\": \"*\", \"Condition\": { \"StringLike\": { \"kms:EncryptionContext:aws:cloudtrail:arn\": [ \"arn:aws:cloudtrail:*:aws-account-id:trail/*\" ] } } } ``` 3. Granting decrypt permissions: ``` { \"Sid\": \"Enable CloudTrail log decrypt permissions\", \"Effect\": \"Allow\", \"Principal\": { \"AWS\": \"arn:aws:iam::aws-account-id:user/username\" }, \"Action\": \"kms:Decrypt\", \"Resource\": \"*\", \"Condition\": { \"Null\": { \"kms:EncryptionContext:aws:cloudtrail:arn\": \"false\" } } } ```",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/encrypting-cloudtrail-log-files-with-aws-kms.html:https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html:CCE-78919-8:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/update-trail.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/kms/put-key-policy.html",
+ "DefaultValue": "By default, CloudTrail logs are not encrypted with a KMS CMK. Logs may be encrypted with SSE-S3, but this does not provide the same level of control or auditing as KMS CMKs."
+ }
+ ]
+ },
+ {
+ "Id": "4.6",
+ "Description": "Ensure rotation for customer-created symmetric CMKs is enabled",
+ "Checks": [
+ "kms_cmk_rotation_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "AWS Key Management Service (KMS) allows customers to rotate the backing key, which is key material stored within the KMS that is tied to the key ID of the customer-created customer master key (CMK). The backing key is used to perform cryptographic operations such as encryption and decryption. Automated key rotation currently retains all prior backing keys so that decryption of encrypted data can occur transparently. It is recommended that CMK key rotation be enabled for symmetric keys. Key rotation cannot be enabled for any asymmetric CMK.",
+ "RationaleStatement": "Rotating encryption keys helps reduce the potential impact of a compromised key, as data encrypted with a new key cannot be accessed with a previous key that may have been exposed. Keys should be rotated every year or upon an event that could result in the compromise of that key.",
+ "ImpactStatement": "Creation, management, and storage of CMKs may require additional time from an administrator.",
+ "RemediationProcedure": "**From Console:** 1. Sign in to the AWS Management Console and open the KMS console at: [https://console.aws.amazon.com/kms](https://console.aws.amazon.com/kms). 2. In the left navigation pane, click `Customer-managed keys`. 3. Select a key with `Key spec = SYMMETRIC_DEFAULT` that does not have automatic rotation enabled. 4. Select the `Key rotation` tab. 5. Check the `Automatically rotate this KMS key every year` box. 6. Click `Save`. 7. Repeat steps 3–6 for all customer-managed CMKs that do not have automatic rotation enabled. **From Command Line:** 1. Run the following command to enable key rotation: ``` aws kms enable-key-rotation --key-id <kms-key-id> ```",
+ "AuditProcedure": "**From Console:** 1. Sign in to the AWS Management Console and open the KMS console at: [https://console.aws.amazon.com/kms](https://console.aws.amazon.com/kms). 2. In the left navigation pane, click `Customer-managed keys`. 3. Select a customer-managed CMK where `Key spec = SYMMETRIC_DEFAULT`. 4. Select the `Key rotation` tab. 5. Ensure the `Automatically rotate this KMS key every year` box is checked. 6. Repeat steps 3–5 for all customer-managed CMKs where `Key spec = SYMMETRIC_DEFAULT`. **From Command Line:** 1. Run the following command to get a list of all keys and their associated `KeyIds`: ``` aws kms list-keys ``` 2. For each key, note the KeyId and run the following command: ``` describe-key --key-id <kms-key-id> ``` 3. If the response contains `KeySpec = SYMMETRIC_DEFAULT`, run the following command: ``` aws kms get-key-rotation-status --key-id <kms-key-id> ``` 4. Ensure `KeyRotationEnabled` is set to `true`. 5. Repeat steps 2–4 for all remaining CMKs.",
+ "AdditionalInformation": "",
+ "References": "https://aws.amazon.com/kms/pricing/:https://csrc.nist.gov/publications/detail/sp/800-57-part-1/rev-5/final",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.7",
+ "Description": "Ensure VPC flow logging is enabled in all VPCs",
+ "Checks": [
+ "vpc_flow_logs_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "VPC Flow Logs is a feature that enables you to capture information about the IP traffic going to and from network interfaces in your VPC. After you've created a flow log, you can view and retrieve its data in Amazon CloudWatch Logs. It is recommended that VPC Flow Logs be enabled for packet Rejects for VPCs.",
+ "RationaleStatement": "VPC Flow Logs provide visibility into network traffic that traverses the VPC and can be used to detect anomalous traffic or gain insights during security workflows.",
+ "ImpactStatement": "By default, CloudWatch Logs will store logs indefinitely unless a specific retention period is defined for the log group. When choosing the number of days to retain, keep in mind that the average time it takes for an organization to realize they have been breached is 210 days (at the time of this writing). Since additional time is required to research a breach, a minimum retention policy of 365 days allows for detection and investigation. You may also wish to archive the logs to a cheaper storage service rather than simply deleting them. See the following AWS resource to manage CloudWatch Logs retention periods: 1. https://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/SettingLogRetention.html",
+ "RemediationProcedure": "Perform the following to enable VPC Flow Logs: **From Console:** 1. Sign into the management console. 2. Select `Services`, then select `VPC`. 3. In the left navigation pane, select `Your VPCs`. 4. Select a VPC. 5. In the right pane, select the `Flow Logs` tab. 6. If no Flow Log exists, click `Create Flow Log`. 7. For Filter, select `Reject`. 8. Enter a `Role` and `Destination Log Group`. 9. Click `Create Log Flow`. 10. Click on `CloudWatch Logs Group`. **Note:** Setting the filter to Reject will dramatically reduce the accumulation of logging data for this recommendation and provide sufficient information for the purposes of breach detection, research, and remediation. However, during periods of least privilege security group engineering, setting the filter to All can be very helpful in discovering existing traffic flows required for the proper operation of an already running environment. **From Command Line:** 1. Create a policy document, name it `role_policy_document.json`, and paste the following content: ``` { Version: 2012-10-17, Statement: [ { Sid: test, Effect: Allow, Principal: { Service: ec2.amazonaws.com }, Action: sts:AssumeRole } ] } ``` 2. Create another policy document, name it `iam_policy.json`, and paste the following content: ``` { Version: 2012-10-17, Statement: [ { Effect: Allow, Action:[ logs:CreateLogGroup, logs:CreateLogStream, logs:DescribeLogGroups, logs:DescribeLogStreams, logs:PutLogEvents, logs:GetLogEvents, logs:FilterLogEvents ], Resource: * } ] } ``` 3. Run the following command to create an IAM role: ``` aws iam create-role --role-name <aws-support-iam-role> --assume-role-policy-document file://<file-path>role_policy_document.json ``` 4. Run the following command to create an IAM policy: ``` aws iam create-policy --policy-name <iam-policy-name> --policy-document file://<file-path>iam-policy.json ``` 5. Run the `attach-group-policy` command, using the IAM policy ARN returned from the previous step to attach the policy to the IAM role: ``` aws iam attach-group-policy --policy-arn arn:aws:iam::<aws-account-id>:policy/<iam-policy-name> --group-name <group-name> ``` - If the command succeeds, no output is returned. 6. Run the `describe-vpcs` command to get a list of VPCs in the selected region: ``` aws ec2 describe-vpcs --region <region> ``` - The command output should return a list of VPCs in the selected region. 7. Run the `create-flow-logs` command to create a flow log for a VPC: ``` aws ec2 create-flow-logs --resource-type VPC --resource-ids <vpc-id> --traffic-type REJECT --log-group-name <log-group-name> --deliver-logs-permission-arn <iam-role-arn> ``` 8. Repeat step 7 for other VPCs in the selected region. 9. Change the region by updating --region, and repeat the remediation procedure for each region.",
+ "AuditProcedure": "Perform the following to determine if VPC Flow logs are enabled: **From Console:** 1. Sign into the management console. 2. Select `Services`, then select `VPC`. 3. In the left navigation pane, select `Your VPCs`. 4. Select a VPC. 5. In the right pane, select the `Flow Logs` tab. 6. Ensure a Log Flow exists that has `Active` in the `Status` column. **From Command Line:** 1. Run the `describe-vpcs` command (OSX/Linux/UNIX) to list the VPC networks available in the current AWS region: ``` aws ec2 describe-vpcs --region <region> --query Vpcs[].VpcId ``` 2. The command output returns the `VpcId` of VPCs available in the selected region. 3. Run the `describe-flow-logs` command (OSX/Linux/UNIX) using the VPC ID to determine if the selected virtual network has the Flow Logs feature enabled: ``` aws ec2 describe-flow-logs --filter Name=resource-id,Values=<vpc-id> ``` - If there are no Flow Logs created for the selected VPC, the command output will return an empty list `[]`. 4. Repeat step 3 for other VPCs in the same region. 5. Change the region by updating `--region`, and repeat steps 1-4 for each region.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.8",
+ "Description": "Ensure that object-level logging for write events is enabled for S3 buckets",
+ "Checks": [
+ "cloudtrail_s3_dataevents_write_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "S3 object-level API operations, such as GetObject, DeleteObject, and PutObject, are referred to as data events. By default, CloudTrail trails do not log data events, so it is recommended to enable object-level logging for S3 buckets.",
+ "RationaleStatement": "Enabling object-level logging will help you meet data compliance requirements within your organization, perform comprehensive security analyses, monitor specific patterns of user behavior in your AWS account, or take immediate actions on any object-level API activity within your S3 buckets using Amazon CloudWatch Events.",
+ "ImpactStatement": "Enabling logging for these object-level events may significantly increase the number of events logged and may incur additional costs.",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and navigate to the S3 dashboard at `https://console.aws.amazon.com/s3/`. 2. In the left navigation panel, click `buckets`, and then click the name of the S3 bucket you want to examine. 3. Click the `Properties` tab to see the bucket configuration in detail. 4. In the `AWS CloudTrail data events` section, select the trail name for recording activity. You can choose an existing trail or create a new one by clicking the `Configure in CloudTrail` button or navigating to the [CloudTrail console](https://console.aws.amazon.com/cloudtrail/). 5. Once the trail is selected, select the `Data Events` check box. 6. Select `S3` from the `Data event type` drop-down. 7. Select `Log all events` from the `Log selector template` drop-down. 8. Repeat steps 2-7 to enable object-level logging of write events for other S3 buckets. **From Command Line:** 1. To enable `object-level` data events logging for S3 buckets within your AWS account, run the `put-event-selectors` command using the name of the trail that you want to reconfigure as identifier: ``` aws cloudtrail put-event-selectors --region <region-name> --trail-name <trail-name> --event-selectors '[{ ReadWriteType: WriteOnly, IncludeManagementEvents:true, DataResources: [{ Type: AWS::S3::Object, Values: [arn:aws:s3:::<s3-bucket-name>/] }] }]' ``` 2. The command output will be `object-level` event trail configuration. 3. If you want to enable it for all buckets at once, change the Values parameter to `[arn:aws:s3]` in the previous command. 4. Repeat step 1 for each s3 bucket to update `object-level` logging of write events. 5. Change the AWS region by updating the `--region` command parameter, and perform the process for the other regions.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and navigate to the CloudTrail dashboard at `https://console.aws.amazon.com/cloudtrail/`. 2. In the left panel, click `Trails`, and then click the name of the trail that you want to examine. 3. Review `General details`. 4. Confirm that `Multi-region trail` is set to `Yes`. 5. Scroll down to `Data events` and confirm the configuration: - If `advanced event selectors` is being used, it should read: ``` Data Events: S3 Log selector template Log all events ``` - If `basic event selectors` is being used, it should read: ``` Data events: S3 Bucket Name: All current and future S3 buckets Write: Enabled ``` 6. Repeat steps 2-5 to verify that each trail has multi-region enabled and is configured to log data events. If a trail does not have multi-region enabled and data event logging configured, refer to the remediation steps. **From Command Line:** 1. Run the `list-trails` command to list all trails: ``` aws cloudtrail list-trails ``` 2. The command output will be a list of trails: ``` TrailARN: arn:aws:cloudtrail:<region>:<account#>:trail/<trail-name>, Name: <trail-name>, HomeRegion: <region> ``` 3. Run the `get-trail` command to determine whether a trail is a multi-region trail: ``` aws cloudtrail get-trail --name <trail-name> --region <region-name> ``` 4. The command output should include: `IsMultiRegionTrail: true`. 5. Run the `get-event-selectors` command, using the `Name` of the trail and the `region` returned in step 2, to determine if data event logging is configured: ``` aws cloudtrail get-event-selectors --region <home-region> --trail-name <trail-name> --query EventSelectors[*].DataResources[] ``` 6. The command output should be an array that includes the S3 bucket defined for data event logging: ``` Type: AWS::S3::Object, Values: [ arn:aws:s3 ``` 7. If the `get-event-selectors` command returns an empty array, data events are not included in the trail's logging configuration; therefore, object-level API operations performed on S3 buckets within your AWS account are not being recorded. 8. Repeat steps 1-7 to verify that each trail has multi-region enabled and is configured to log data events. If a trail does not have multi-region enabled and data event logging configured, refer to the remediation steps.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonS3/latest/user-guide/enable-cloudtrail-events.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.9",
+ "Description": "Ensure that object-level logging for read events is enabled for S3 buckets",
+ "Checks": [
+ "cloudtrail_s3_dataevents_read_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "S3 object-level API operations, such as GetObject, DeleteObject, and PutObject, are referred to as data events. By default, CloudTrail trails do not log data events, so it is recommended to enable object-level logging for S3 buckets.",
+ "RationaleStatement": "Enabling object-level logging will help you meet data compliance requirements within your organization, perform comprehensive security analyses, monitor specific patterns of user behavior in your AWS account, or take immediate actions on any object-level API activity within your S3 buckets using Amazon CloudWatch Events.",
+ "ImpactStatement": "Enabling logging for these object-level events may significantly increase the number of events logged and may incur additional costs.",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and navigate to S3 dashboard at `https://console.aws.amazon.com/s3/`. 2. In the left navigation panel, click `buckets` and then click the name of the S3 bucket that you want to examine. 3. Click the `Properties` tab to see the bucket configuration in detail. 4. In the `AWS Cloud Trail data events` section, select the trail name for recording activity. You can choose an existing trail or create a new one by clicking the `Configure in CloudTrail` button or navigating to the [CloudTrail console](https://console.aws.amazon.com/cloudtrail/). 5. Once the trail is selected, select the `Data Events` check box. 6. Select `S3` from the `Data event type` drop-down. 7. Select `Log all events` from the `Log selector template` drop-down. 8. Repeat steps 2-7 to enable object-level logging of read events for other S3 buckets. **From Command Line:** 1. To enable `object-level` data events logging for S3 buckets within your AWS account, run the `put-event-selectors` command using the name of the trail that you want to reconfigure as identifier: ``` aws cloudtrail put-event-selectors --region <region-name> --trail-name <trail-name> --event-selectors '[{ ReadWriteType: ReadOnly, IncludeManagementEvents:true, DataResources: [{ Type: AWS::S3::Object, Values: [arn:aws:s3:::<s3-bucket-name>/] }] }]' ``` 2. The command output will be `object-level` event trail configuration. 3. If you want to enable it for all buckets at once, change the Values parameter to `[arn:aws:s3]` in the previous command. 4. Repeat step 1 for each s3 bucket to update `object-level` logging of read events. 5. Change the AWS region by updating the `--region` command parameter, and perform the process for the other regions.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and navigate to the CloudTrail dashboard at `https://console.aws.amazon.com/cloudtrail/`. 2. In the left panel, click `Trails`, and then click the name of the trail that you want to examine. 3. Review `General details`. 4. Confirm that `Multi-region trail` is set to `Yes` 5. Scroll down to `Data events` 5. Scroll down to `Data events` and confirm the configuration: - If `advanced event selectors` is being used, it should read: ``` Data Events: S3 Log selector template Log all events ``` - If `basic event selectors` is being used, it should read: ``` Data events: S3 Bucket Name: All current and future S3 buckets Read: Enabled ``` 6. Repeat steps 2-5 to verify that each trail has multi-region enabled and is configured to log data events. If a trail does not have multi-region enabled and data event logging configured, refer to the remediation steps. **From Command Line:** 1. Run the `describe-trails` command to list all trail names: ``` aws cloudtrail describe-trails --region <region-name> --output table --query trailList[*].Name ``` 2. The command output will be table of the trail names. 3. Run the `get-event-selectors` command using the name of a trail returned at the previous step and custom query filters to determine if data event logging is configured: ``` aws cloudtrail get-event-selectors --region <region-name> --trail-name <trail-name> --query EventSelectors[*].DataResources[] ``` 4. The command output should be an array that includes the S3 bucket defined for data event logging. 5. If the `get-event-selectors` command returns an empty array, data events are not included in the trail's logging configuration; therefore, object-level API operations performed on S3 buckets within your AWS account are not being recorded. 6. Repeat steps 1-5 to verify the configuration of each trail. 7. Change the AWS region by updating the `--region` command parameter, and perform the audit process for other regions.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AmazonS3/latest/user-guide/enable-cloudtrail-events.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.10",
+ "Description": "Ensure all AWS-managed web front-end services have access logging enabled",
+ "Checks": [
+ "cloudfront_distributions_logging_enabled",
+ "elbv2_logging_enabled",
+ "apigateway_restapi_logging_enabled",
+ "apigatewayv2_api_access_logging_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Logging",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that access logging is enabled for all AWS-managed web front-end services that terminate or front HTTP(S) traffic, including Amazon CloudFront distributions, Application Load Balancers (ALB), Network Load Balancers (NLB), and Amazon API Gateway REST/HTTP API stages with public endpoints. Access logs must be enabled with delivery to a designated S3 bucket or CloudWatch Logs destination that is protected with appropriate access controls. This control requires logging of request details such as client IP address, timestamp, HTTP method, requested URI, response status code, bytes transferred, and user agent for every request processed by these services. CloudTrail provides management event logging for these resources, but access logs are required to capture the actual HTTP request/response activity at the network edge layers.",
+ "RationaleStatement": "AWS-managed web front-end services (CloudFront, ALB/NLB, API Gateway) represent the primary HTTP(S) ingress points into AWS accounts and are the first line of defense against web attacks, reconnaissance, and abuse attempts. CloudTrail logs management actions (create/update/delete) and data events but does not capture the content of HTTP requests/responses or client activity, leaving a critical visibility gap for security monitoring and incident response. Access logs from these services enable reconstruction of all web traffic, detection of anomalous patterns, forensic analysis of incidents, and compliance proof that internet-facing entry points were monitored. Without these logs, security teams cannot distinguish legitimate traffic from attacks or prove access patterns during audits.",
+ "ImpactStatement": "Enabling access logging incurs additional storage costs for log delivery and retention, as well as minor configuration overhead for creating dedicated logging buckets, IAM roles, and retention policies. Costs can be managed through lifecycle policies, log sampling, and tiered storage classes.",
+ "RemediationProcedure": "Following instructions enable standard access logging for CloudFront distributions using the AWS Management Console. 1. Open the CloudFront console from the AWS Management Console. 2. Click Distributions in the left navigation and click on the Distribution ID needing remediation. 3. Go to the \"Logging\" tab and click on \"Create access log delivery\" - Select \"Deliver to\" for your preferred location: S3 or CloudWatch log group - Select the ARN of your log destination resource - Click on Submit 4. Confirm if you see the access log destination in the logging tab",
+ "AuditProcedure": "As an example with CloudFront, verify following the below steps if access logging is enabled: 1. Open the CloudFront console from the AWS Management Console. 2. Click Distributions in the left navigation. 3. For each Distribution ID (e.g., E123ABC...), click the Distribution ID and go to the \"Logging\" tab 4. Check if one or more \"Access log destinations\" are present with a destination type of S3 or CloudWatch log group.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1",
+ "Description": "Ensure unauthorized API calls are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_unauthorized_api_calls"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for unauthorized API calls.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring unauthorized API calls will help reduce the time it takes to detect malicious activity and can alert you to potential security incidents.",
+ "ImpactStatement": "This alert may be triggered by normal read-only console activities that attempt to opportunistically gather optional information but gracefully fail if they lack the necessary permissions. If an excessive number of alerts are generated, then an organization may wish to consider adding read access to the limited IAM user permissions solely to reduce the number of alerts. In some cases, doing this may allow users to actually view some areas of the system; any additional access granted should be reviewed for alignment with the original limited IAM user intent.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for unauthorized API calls and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <unauthorized-api-calls-metric> --metric-transformations metricName=unauthorized_api_calls_metric,metricNamespace=CISBenchmark,metricValue=1 --filter-pattern { ($.errorCode =*UnauthorizedOperation) || ($.errorCode =AccessDenied*) && ($.sourceIPAddress!=delivery.logs.amazonaws.com) && ($.eventName!=HeadBucket) } ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name unauthorized_api_calls_alarm --metric-name unauthorized_api_calls_metric --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace CISBenchmark --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.errorCode =*UnauthorizedOperation) || ($.errorCode =AccessDenied*) && ($.sourceIPAddress!=delivery.logs.amazonaws.com) && ($.eventName!=HeadBucket) }, ``` 4. Note the `<unauthorized-api-calls-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<unauthorized-api-calls-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query MetricAlarms[?MetricName == <unauthorized-api-calls-metric>] ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://aws.amazon.com/sns/:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2",
+ "Description": "Ensure management console sign-in without MFA is monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_sign_in_without_mfa"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for console logins that are not protected by multi-factor authentication (MFA).",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring for single-factor console logins will increase visibility into accounts that are not protected by MFA. These type of accounts are more susceptible to compromise and unauthorized access.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for AWS Management Console sign-ins without MFA and uses the `<trail-log-group-name>` taken from audit step 1. ``` aws logs put-metric-filter --log-group-name <trail-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) }' ``` Or, to reduce false positives in case Single Sign-On (SSO) is used in the organization: ``` aws logs put-metric-filter --log-group-name <trail-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) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name `<no-mfa-console-signin-alarm>` --metric-name `<no-mfa-console-signin-metric>` --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: ``` aws cloudtrail describe-trails ``` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: ``` aws cloudtrail get-trail-status --name <trail-name> ``` - ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: ``` aws cloudtrail get-event-selectors --trail-name <trail-name> ``` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = ConsoleLogin) && ($.additionalEventData.MFAUsed != Yes) } ``` Or, to reduce false positives in case Single Sign-On (SSO) is used in the organization: ``` filterPattern: { ($.eventName = ConsoleLogin) && ($.additionalEventData.MFAUsed != Yes) && ($.userIdentity.type = IAMUser) && ($.responseElements.ConsoleLogin = Success) } ``` 4. Note the `<no-mfa-console-signin-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<no-mfa-console-signin-metric>` captured in step 4. ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName== <no-mfa-console-signin-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored Filter pattern set to `{ ($.eventName = ConsoleLogin) && ($.additionalEventData.MFAUsed != Yes) && ($.userIdentity.type = IAMUser) && ($.responseElements.ConsoleLogin = Success}`: - reduces false alarms raised when a user logs in via SSO",
+ "References": "https://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/viewing_metrics_with_cloudwatch.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.3",
+ "Description": "Ensure usage of the 'root' account is monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_root_usage"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for 'root' login attempts to detect unauthorized use or attempts to use the root account.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring 'root' account logins will provide visibility into the use of a fully privileged account and the opportunity to reduce its usage.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for 'root' account usage and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name `<trail-log-group-name>` --filter-name `<root-usage-metric>` --metric-transformations metricName= `<root-usage-metric>` ,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ $.userIdentity.type = Root && $.userIdentity.invokedBy NOT EXISTS && $.eventType != AwsServiceEvent }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name `<root-usage-alarm>` --metric-name `<root-usage-metric>` --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns_topic_arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: ``` aws cloudtrail describe-trails ``` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: ``` aws cloudtrail get-trail-status --name <trail-name> ``` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: ``` aws cloudtrail get-event-selectors --trail-name <trail-name> ``` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { $.userIdentity.type = Root && $.userIdentity.invokedBy NOT EXISTS && $.eventType != AwsServiceEvent } ``` 4. Note the `<root-usage-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<root-usage-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<root-usage-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.4",
+ "Description": "Ensure IAM policy changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_policy_changes"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for changes made to Identity and Access Management (IAM) policies.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to IAM policies will help ensure authentication and authorization controls remain intact.",
+ "ImpactStatement": "Monitoring these changes may result in a number of false positives, especially in larger environments. This alert may require more tuning than others to eliminate some of those erroneous notifications.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for IAM policy changes and the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name `<trail-log-group-name>` --filter-name `<iam-changes-metric>` --metric-transformations metricName= `<iam-changes-metric>`,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{($.eventName=DeleteGroupPolicy)||($.eventName=DeleteRolePolicy)||($.eventName=DeleteUserPolicy)||($.eventName=PutGroupPolicy)||($.eventName=PutRolePolicy)||($.eventName=PutUserPolicy)||($.eventName=CreatePolicy)||($.eventName=DeletePolicy)||($.eventName=CreatePolicyVersion)||($.eventName=DeletePolicyVersion)||($.eventName=AttachRolePolicy)||($.eventName=DetachRolePolicy)||($.eventName=AttachUserPolicy)||($.eventName=DetachUserPolicy)||($.eventName=AttachGroupPolicy)||($.eventName=DetachGroupPolicy)}' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name `<iam-changes-alarm>` --metric-name `<iam-changes-metric>` --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrails: ``` aws cloudtrail describe-trails ``` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: ``` aws cloudtrail get-trail-status --name <trail-name> ``` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: ``` aws cloudtrail get-event-selectors --trail-name <trail-name> ``` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: {($.eventName=DeleteGroupPolicy)||($.eventName=DeleteRolePolicy)||($.eventName=DeleteUserPolicy)||($.eventName=PutGroupPolicy)||($.eventName=PutRolePolicy)||($.eventName=PutUserPolicy)||($.eventName=CreatePolicy)||($.eventName=DeletePolicy)||($.eventName=CreatePolicyVersion)||($.eventName=DeletePolicyVersion)||($.eventName=AttachRolePolicy)||($.eventName=DetachRolePolicy)||($.eventName=AttachUserPolicy)||($.eventName=DetachUserPolicy)||($.eventName=AttachGroupPolicy)||($.eventName=DetachGroupPolicy)} ``` 4. Note the `<iam-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<iam-change-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<iam-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.5",
+ "Description": "Ensure CloudTrail configuration changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be used to detect changes to CloudTrail's configurations.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to CloudTrail's configuration will help ensure sustained visibility into the activities performed in the AWS account.",
+ "ImpactStatement": "Ensuring that changes to CloudTrail configurations are monitored enhances security by maintaining the integrity of logging mechanisms. Automated monitoring can provide real-time alerts; however, it may require additional setup and resources to configure and manage these alerts effectively. These steps can be performed manually within a company's existing SIEM platform in cases where CloudTrail logs are monitored outside of the AWS monitoring tools in CloudWatch.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for CloudTrail configuration changes and the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <cloudtrail-cfg-changes-metric> --metric-transformations metricName=<cloudtrail-cfg-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = CreateTrail) || ($.eventName = UpdateTrail) || ($.eventName = DeleteTrail) || ($.eventName = StartLogging) || ($.eventName = StopLogging) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <cloudtrail-cfg-changes-alarm> --metric-name <cloudtrail-cfg-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = CreateTrail) || ($.eventName = UpdateTrail) || ($.eventName = DeleteTrail) || ($.eventName = StartLogging) || ($.eventName = StopLogging) } ``` 4. Note the `<cloudtrail-cfg-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<cloudtrail-cfg-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<cloudtrail-cfg-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.6",
+ "Description": "Ensure AWS Management Console authentication failures are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_authentication_failures"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for failed console authentication attempts.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring failed console logins may decrease the lead time to detect an attempt to brute-force a credential, which may provide an indicator, such as the source IP address, that can be used in other event correlations.",
+ "ImpactStatement": "Monitoring for these failures may generate a large number of alerts, especially in larger environments.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for AWS management Console login failures and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <console-signin-failure-metric> --metric-transformations metricName=<console-signin-failure-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = ConsoleLogin) && ($.errorMessage = Failed authentication) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <console-signin-failure-alarm> --metric-name <console-signin-failure-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = ConsoleLogin) && ($.errorMessage = Failed authentication) } ``` 4. Note the `<console-signin-failure-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<console-signin-failure-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<console-signin-failure-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.7",
+ "Description": "Ensure disabling or scheduled deletion of customer created CMKs is monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for customer-created CMKs that have changed state to disabled or are scheduled for deletion.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Data encrypted with disabled or deleted keys will no longer be accessible. Changes in the state of a CMK should be monitored to ensure that the change is intentional.",
+ "ImpactStatement": "Creation, storage, and management of CMK may require additional labor compared to the use of AWS-managed keys.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for CMKs that have been disabled or scheduled for deletion and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <disable-or-delete-cmk-changes-metric> --metric-transformations metricName=<disable-or-delete-cmk-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{($.eventSource = kms.amazonaws.com) && (($.eventName=DisableKey)||($.eventName=ScheduleKeyDeletion)) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <disable-or-delete-cmk-changes-alarm> --metric-name <disable-or-delete-cmk-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: {($.eventSource = kms.amazonaws.com) && (($.eventName=DisableKey)||($.eventName=ScheduleKeyDeletion)) } ``` 4. Note the `<disable-or-delete-cmk-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<disable-or-delete-cmk-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<disable-or-delete-cmk-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.8",
+ "Description": "Ensure S3 bucket policy changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_for_s3_bucket_policy_changes"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for changes to S3 bucket policies.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to S3 bucket policies may reduce the time it takes to detect and correct permissive policies on sensitive S3 buckets.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for changes to S3 bucket policies and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <s3-bucket-policy-changes-metric> --metric-transformations metricName=<s3-bucket-policy-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventSource = s3.amazonaws.com) && (($.eventName = PutBucketAcl) || ($.eventName = PutBucketPolicy) || ($.eventName = PutBucketCors) || ($.eventName = PutBucketLifecycle) || ($.eventName = PutBucketReplication) || ($.eventName = DeleteBucketPolicy) || ($.eventName = DeleteBucketCors) || ($.eventName = DeleteBucketLifecycle) || ($.eventName = DeleteBucketReplication)) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <s3-bucket-policy-changes-alarm> --metric-name <s3-bucket-policy-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventSource = s3.amazonaws.com) && (($.eventName = PutBucketAcl) || ($.eventName = PutBucketPolicy) || ($.eventName = PutBucketCors) || ($.eventName = PutBucketLifecycle) || ($.eventName = PutBucketReplication) || ($.eventName = DeleteBucketPolicy) || ($.eventName = DeleteBucketCors) || ($.eventName = DeleteBucketLifecycle) || ($.eventName = DeleteBucketReplication)) } ``` 4. Note the `<s3-bucket-policy-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<s3-bucket-policy-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<s3-bucket-policy-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.9",
+ "Description": "Ensure AWS Config configuration changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for detecting changes to AWS Config's configurations.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to the AWS Config configuration will help ensure sustained visibility of the configuration items within the AWS account.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for AWS Configuration changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <aws-config-changes-metric> --metric-transformations metricName=<aws-config-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventSource = config.amazonaws.com) && (($.eventName=StopConfigurationRecorder)||($.eventName=DeleteDeliveryChannel)||($.eventName=PutDeliveryChannel)||($.eventName=PutConfigurationRecorder)) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <aws-config-changes-alarm> --metric-name <aws-config-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventSource = config.amazonaws.com) && (($.eventName=StopConfigurationRecorder)||($.eventName=DeleteDeliveryChannel)||($.eventName=PutDeliveryChannel)||($.eventName=PutConfigurationRecorder)) } ``` 4. Note the `<aws-config-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<aws-config-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<aws-config-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.10",
+ "Description": "Ensure security group changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_security_group_changes"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. Security groups are stateful packet filters that control ingress and egress traffic within a VPC. It is recommended that a metric filter and alarm be established to detect changes to security groups.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to security groups will help ensure that resources and services are not unintentionally exposed.",
+ "ImpactStatement": "This may require additional 'tuning' to eliminate false positives and filter out expected activity so that anomalies are easier to detect.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for security groups changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <security-group-changes-metric> --metric-transformations metricName=<security-group-changes-metric>,metricNamespace=CISBenchmark,metricValue=1 --filter-pattern { ($.eventName = AuthorizeSecurityGroupIngress) || ($.eventName = AuthorizeSecurityGroupEgress) || ($.eventName = RevokeSecurityGroupIngress) || ($.eventName = RevokeSecurityGroupEgress) || ($.eventName = CreateSecurityGroup) || ($.eventName = DeleteSecurityGroup) || ($.eventName = ModifySecurityGroupRules) } ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <security-group-changes-alarm> --metric-name <security-group-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace CISBenchmark --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = AuthorizeSecurityGroupIngress) || ($.eventName = AuthorizeSecurityGroupEgress) || ($.eventName = RevokeSecurityGroupIngress) || ($.eventName = RevokeSecurityGroupEgress) || ($.eventName = CreateSecurityGroup) || ($.eventName = DeleteSecurityGroup) || ($.eventName = ModifySecurityGroupRules) } ``` 4. Note the `<security-group-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<security-group-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query MetricAlarms[?MetricName==<security-group-changes-metric>] ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored AWS has recently introduced a new API, ModifySecurityGroupRules, which modifies the rules of a security group.",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html:https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifySecurityGroupRules.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.11",
+ "Description": "Ensure Network Access Control List (NACL) changes are monitored",
+ "Checks": [
+ "cloudwatch_changes_to_network_acls_alarm_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. NACLs are used as a stateless packet filter to control ingress and egress traffic for subnets within a VPC. It is recommended that a metric filter and alarm be established for any changes made to NACLs.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to NACLs will help ensure that AWS resources and services are not unintentionally exposed.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for NACL changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <nacl-changes-metric> --metric-transformations metricName=<nacl-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = CreateNetworkAcl) || ($.eventName = CreateNetworkAclEntry) || ($.eventName = DeleteNetworkAcl) || ($.eventName = DeleteNetworkAclEntry) || ($.eventName = ReplaceNetworkAclEntry) || ($.eventName = ReplaceNetworkAclAssociation) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <nacl-changes-alarm> --metric-name <nacl-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = CreateNetworkAcl) || ($.eventName = CreateNetworkAclEntry) || ($.eventName = DeleteNetworkAcl) || ($.eventName = DeleteNetworkAclEntry) || ($.eventName = ReplaceNetworkAclEntry) || ($.eventName = ReplaceNetworkAclAssociation) } ``` 4. Note the `<nacl-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<nacl-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<nacl-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.12",
+ "Description": "Ensure changes to network gateways are monitored",
+ "Checks": [
+ "cloudwatch_changes_to_network_gateways_alarm_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. Network gateways are required to send and receive traffic to a destination outside of a VPC. It is recommended that a metric filter and alarm be established for changes to network gateways.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to network gateways will help ensure that all ingress/egress traffic traverses the VPC border via a controlled path.",
+ "ImpactStatement": "Monitoring changes to network gateways helps detect unauthorized modifications that could compromise network security. Implementing automated monitoring and alerts can improve incident response times, but it may require additional configuration and maintenance efforts.",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for network gateways changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <network-gw-changes-metric> --metric-transformations metricName=<network-gw-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = CreateCustomerGateway) || ($.eventName = DeleteCustomerGateway) || ($.eventName = AttachInternetGateway) || ($.eventName = CreateInternetGateway) || ($.eventName = DeleteInternetGateway) || ($.eventName = DetachInternetGateway) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <network-gw-changes-alarm> --metric-name <network-gw-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ``` 5. Implement logging and alerting mechanisms: ``` aws sns create-topic --name NetworkGatewayChangesAlerts ```` ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol email --notification-endpoint <email-address> ``` ``` aws cloudwatch put-metric-alarm --alarm-name NetworkGatewayChangesAlarm --metric-name GatewayChanges --namespace AWS/EC2 --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = CreateCustomerGateway) || ($.eventName = DeleteCustomerGateway) || ($.eventName = AttachInternetGateway) || ($.eventName = CreateInternetGateway) || ($.eventName = DeleteInternetGateway) || ($.eventName = DetachInternetGateway) } ``` 4. Note the `<network-gw-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<network-gw-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<network-gw-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>` 8. Ensure automated monitoring is enabled: ``` aws cloudwatch put-metric-alarm --alarm-name NetworkGatewayChanges --metric-name GatewayChanges --namespace AWS/EC2 --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --alarm-actions <sns-topic-arn> ```",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.13",
+ "Description": "Ensure route table changes are monitored",
+ "Checks": [
+ "cloudwatch_changes_to_network_route_tables_alarm_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. Routing tables are used to route network traffic between subnets and to network gateways. It is recommended that a metric filter and alarm be established for changes to route tables.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring changes to route tables will help ensure that all VPC traffic flows through the expected path and prevent any accidental or intentional modifications that may lead to uncontrolled network traffic. An alarm should be triggered every time an AWS API call is performed to create, replace, delete, or disassociate a route table.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for route table changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-pattern '{ ($.eventName = CreateRoute) || ($.eventName = CreateRouteTable) || ($.eventName = ReplaceRoute) || ($.eventName = ReplaceRouteTableAssociation) || ($.eventName = DeleteRouteTable) || ($.eventName = DeleteRoute) || ($.eventName = DisassociateRouteTable) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <route-table-changes-alarm> --metric-name <route-table-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: {($.eventSource = ec2.amazonaws.com) && ($.eventName = CreateRoute) || ($.eventName = CreateRouteTable) || ($.eventName = ReplaceRoute) || ($.eventName = ReplaceRouteTableAssociation) || ($.eventName = DeleteRouteTable) || ($.eventName = DeleteRoute) || ($.eventName = DisassociateRouteTable) } ``` 4. Note the `<route-table-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<route-table-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<route-table-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.14",
+ "Description": "Ensure VPC changes are monitored",
+ "Checks": [
+ "cloudwatch_changes_to_vpcs_alarm_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is possible to have more than one VPC within an account; additionally, it is also possible to create a peer connection between two VPCs, enabling network traffic to route between them. It is recommended that a metric filter and alarm be established for changes made to VPCs.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. VPCs in AWS are logically isolated virtual networks that can be used to launch AWS resources. Monitoring changes to VPC configurations will help ensure that VPC traffic flow is not negatively impacted. Changes to VPCs can affect network accessibility from the public internet and additionally impact VPC traffic flow to and from the resources launched in the VPC.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for VPC changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <vpc-changes-metric> --metric-transformations metricName=<vpc-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = CreateVpc) || ($.eventName = DeleteVpc) || ($.eventName = ModifyVpcAttribute) || ($.eventName = AcceptVpcPeeringConnection) || ($.eventName = CreateVpcPeeringConnection) || ($.eventName = DeleteVpcPeeringConnection) || ($.eventName = RejectVpcPeeringConnection) || ($.eventName = AttachClassicLinkVpc) || ($.eventName = DetachClassicLinkVpc) || ($.eventName = DisableVpcClassicLink) || ($.eventName = EnableVpcClassicLink) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <vpc-changes-alarm> --metric-name <vpc-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventName = CreateVpc) || ($.eventName = DeleteVpc) || ($.eventName = ModifyVpcAttribute) || ($.eventName = AcceptVpcPeeringConnection) || ($.eventName = CreateVpcPeeringConnection) || ($.eventName = DeleteVpcPeeringConnection) || ($.eventName = RejectVpcPeeringConnection) || ($.eventName = AttachClassicLinkVpc) || ($.eventName = DetachClassicLinkVpc) || ($.eventName = DisableVpcClassicLink) || ($.eventName = EnableVpcClassicLink) } ``` 4. Note the `<vpc-changes-metric>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<vpc-changes-metric>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<vpc-changes-metric>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html:https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.15",
+ "Description": "Ensure AWS Organizations changes are monitored",
+ "Checks": [
+ "cloudwatch_log_metric_filter_aws_organizations_changes"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for changes made to AWS Organizations in the master AWS account.",
+ "RationaleStatement": "CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting. Monitoring AWS Organizations changes can help you prevent unwanted, accidental, or intentional modifications that may lead to unauthorized access or other security breaches. This monitoring technique helps ensure that any unexpected changes made within your AWS Organizations can be investigated and that any unwanted changes can be rolled back.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription: 1. Create a metric filter based on the provided filter pattern that checks for AWS Organizations changes and uses the `<trail-log-group-name>` taken from audit step 1: ``` aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <organizations-changes> --metric-transformations metricName=<organizations-changes>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventSource = organizations.amazonaws.com) && (($.eventName = AcceptHandshake) || ($.eventName = AttachPolicy) || ($.eventName = CreateAccount) || ($.eventName = CreateOrganizationalUnit) || ($.eventName = CreatePolicy) || ($.eventName = DeclineHandshake) || ($.eventName = DeleteOrganization) || ($.eventName = DeleteOrganizationalUnit) || ($.eventName = DeletePolicy) || ($.eventName = DetachPolicy) || ($.eventName = DisablePolicyType) || ($.eventName = EnablePolicyType) || ($.eventName = InviteAccountToOrganization) || ($.eventName = LeaveOrganization) || ($.eventName = MoveAccount) || ($.eventName = RemoveAccountFromOrganization) || ($.eventName = UpdatePolicy) || ($.eventName = UpdateOrganizationalUnit)) }' ``` **Note**: You can choose your own `metricName` and `metricNamespace` strings. Using the same `metricNamespace` for all Foundations Benchmark metrics will group them together. 2. Create an SNS topic that the alarm will notify: ``` aws sns create-topic --name <sns-topic-name> ``` **Note**: You can execute this command once and then reuse the same topic for all monitoring alarms. **Note**: Capture the `TopicArn` that is displayed when creating the SNS topic in step 2. 3. Create an SNS subscription for the topic created in step 2: ``` aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints> ``` **Note**: You can execute this command once and then reuse the same subscription for all monitoring alarms. 4. Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2: ``` aws cloudwatch put-metric-alarm --alarm-name <organizations-changes> --metric-name <organizations-changes> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn> ```",
+ "AuditProcedure": "If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured: 1. Identify the log group name that is configured for use with the active multi-region CloudTrail trail: - List all CloudTrail trails: `aws cloudtrail describe-trails` - Identify multi-region CloudTrail trails: `Trails with IsMultiRegionTrail set to true` - Note the value associated with Name:`<trail-name>` - Note the `<trail-log-group-name>` within the value associated with CloudWatchLogsLogGroupArn - Example: `arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*` - Ensure the identified multi-region CloudTrail trail is active: - `aws cloudtrail get-trail-status --name <trail-name>` - Ensure `IsLogging` is set to `TRUE` - Ensure the identified multi-region CloudTrail trail captures all management events: - `aws cloudtrail get-event-selectors --trail-name <trail-name>` - Ensure there is at least one `event selector` for a trail with `IncludeManagementEvents` set to `true` and `ReadWriteType` set to `All` 2. Get a list of all associated metric filters for the `<trail-log-group-name>` captured in step 1: ``` aws logs describe-metric-filters --log-group-name <trail-log-group-name> ``` 3. Ensure the output from the above command contains the following: ``` filterPattern: { ($.eventSource = organizations.amazonaws.com) && (($.eventName = AcceptHandshake) || ($.eventName = AttachPolicy) || ($.eventName = CreateAccount) || ($.eventName = CreateOrganizationalUnit) || ($.eventName = CreatePolicy) || ($.eventName = DeclineHandshake) || ($.eventName = DeleteOrganization) || ($.eventName = DeleteOrganizationalUnit) || ($.eventName = DeletePolicy) || ($.eventName = DetachPolicy) || ($.eventName = DisablePolicyType) || ($.eventName = EnablePolicyType) || ($.eventName = InviteAccountToOrganization) || ($.eventName = LeaveOrganization) || ($.eventName = MoveAccount) || ($.eventName = RemoveAccountFromOrganization) || ($.eventName = UpdatePolicy) || ($.eventName = UpdateOrganizationalUnit)) } ``` 4. Note the `<organizations-changes>` value associated with the `filterPattern` from step 3. 5. Get a list of CloudWatch alarms, and filter on the `<organizations-changes>` captured in step 4: ``` aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName==<organizations-changes>]' ``` 6. Note the `AlarmActions` value; this will provide the SNS topic ARN value. 7. Ensure there is at least one active subscriber to the SNS topic: ``` aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn> ``` - At least one subscription should have SubscriptionArn with a valid AWS ARN. - Example of valid SubscriptionArn: `arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>`",
+ "AdditionalInformation": "Configuring a log metric filter and alarm on a multi-region (global) CloudTrail trail: - ensures that activities from all regions (both used and unused) are monitored - ensures that activities on all supported global services are monitored - ensures that all management events across all regions are monitored",
+ "References": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html:https://docs.aws.amazon.com/organizations/latest/userguide/orgs_security_incident-response.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.16",
+ "Description": "Ensure AWS Security Hub is enabled",
+ "Checks": [
+ "securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Security Hub collects security data from various AWS accounts, services, and supported third-party partner products, helping you analyze your security trends and identify the highest-priority security issues. When you enable Security Hub, it begins to consume, aggregate, organize, and prioritize findings from the AWS services that you have enabled, such as Amazon GuardDuty, Amazon Inspector, and Amazon Macie. You can also enable integrations with AWS partner security products.",
+ "RationaleStatement": "AWS Security Hub provides you with a comprehensive view of your security state in AWS and helps you check your environment against security industry standards and best practices, enabling you to quickly assess the security posture across your AWS accounts.",
+ "ImpactStatement": "It is recommended that AWS Security Hub be enabled in all regions. AWS Security Hub requires that AWS Config be enabled.",
+ "RemediationProcedure": "To grant the permissions required to enable Security Hub, attach the Security Hub managed policy `AWSSecurityHubFullAccess` to an IAM user, group, or role. Enabling Security Hub: **From Console:** 1. Use the credentials of the IAM identity to sign in to the Security Hub console. 2. When you open the Security Hub console for the first time, choose `Go to Security Hub`. 3. The `Security standards` section on the welcome page lists supported security standards. Check the box for a standard to enable it. 3. Choose `Enable Security Hub`. **From Command Line:** 1. Run the `enable-security-hub` command, including `--enable-default-standards` to enable the default standards: ``` aws securityhub enable-security-hub --enable-default-standards ``` 2. To enable Security Hub without the default standards, include `--no-enable-default-standards`: ``` aws securityhub enable-security-hub --no-enable-default-standards ```",
+ "AuditProcedure": "Follow this process to evaluate AWS Security Hub configuration per region: **From Console:** 1. Sign in to the AWS Management Console and open the AWS Security Hub console at https://console.aws.amazon.com/securityhub/. 2. On the top right of the console, select the target Region. 3. If the Security Hub > Summary page is displayed, then Security Hub is set up for the selected region. 4. If presented with Setup Security Hub or Get Started With Security Hub, refer to the remediation steps. 5. Repeat steps 2 to 4 for each region. **From Command Line:** Run the following command to verify the Security Hub status: ``` aws securityhub describe-hub ``` This will list the Security Hub status by region. Check for a 'SubscribedAt' value. Example output: ``` { HubArn: <security-hub-arn>, SubscribedAt: 2022-08-19T17:06:42.398Z, AutoEnableControls: true } ``` An error will be returned if Security Hub is not enabled. Example error: ``` An error occurred (InvalidAccessException) when calling the DescribeHub operation: Account <Account ID> is not subscribed to AWS Security Hub ```",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-get-started.html:https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-enable.html#securityhub-enable-api:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/securityhub/enable-security-hub.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1",
+ "Description": "Ensure EBS volume encryption is enabled in all regions",
+ "Checks": [
+ "ec2_ebs_default_encryption"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "SubSection": "6.1 Elastic Compute Cloud (EC2)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Elastic Compute Cloud (EC2) supports encryption at rest when using the Elastic Block Store (EBS) service. While disabled by default, forcing encryption at EBS volume creation is supported.",
+ "RationaleStatement": "Encrypting data at rest reduces the likelihood of unintentional exposure and can nullify the impact of disclosure if the encryption remains unbroken.",
+ "ImpactStatement": "Losing access to or removing the KMS key used by the EBS volumes will result in the inability to access the volumes.",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console and open the Amazon EC2 console using https://console.aws.amazon.com/ec2/. 2. Under `Account attributes`, click `EBS encryption`. 3. Click `Manage`. 4. Check the `Enable` box. 5. Click `Update EBS encryption`. 6. Repeat for each region in which EBS volume encryption is not enabled by default. **Note:** EBS volume encryption is configured per region. **From Command Line:** 1. Run the following command: ``` aws --region <region> ec2 enable-ebs-encryption-by-default ``` 2. Verify that `EbsEncryptionByDefault: true` is displayed. 3. Repeat for each region in which EBS volume encryption is not enabled by default. **Note:** EBS volume encryption is configured per region.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console and open the Amazon EC2 console using https://console.aws.amazon.com/ec2/. 2. Under `Settings`, click `EBS encryption`. 3. Verify `Always encrypt new EBS volumes` displays `Enabled`. 4. Repeat for each region in use. **Note:** EBS volume encryption is configured per region. **From Command Line:** 1. Run the following command: ``` aws --region <region> ec2 get-ebs-encryption-by-default ``` 2. Verify that `EbsEncryptionByDefault: true` is displayed. 3. Repeat for each region in use. **Note:** EBS volume encryption is configured per region.",
+ "AdditionalInformation": "Default EBS volume encryption only applies to newly created EBS volumes; existing EBS volumes are **not** converted automatically.",
+ "References": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html:https://aws.amazon.com/blogs/aws/new-opt-in-to-default-encryption-for-new-ebs-volumes/",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2",
+ "Description": "Ensure CIFS access is restricted to trusted networks to prevent unauthorized access",
+ "Checks": [
+ "ec2_instance_port_cifs_exposed_to_internet"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "SubSection": "6.1 Elastic Compute Cloud (EC2)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Common Internet File System (CIFS) is a network file-sharing protocol that allows systems to share files over a network. However, unrestricted CIFS access can expose your data to unauthorized users, leading to potential security risks. It is important to restrict CIFS access to only trusted networks and users to prevent unauthorized access and data breaches.",
+ "RationaleStatement": "Allowing unrestricted CIFS access can lead to significant security vulnerabilities, as it may allow unauthorized users to access sensitive files and data. By restricting CIFS access to known and trusted networks, you can minimize the risk of unauthorized access and protect sensitive data from exposure to potential attackers. Implementing proper network access controls and permissions is essential for maintaining the security and integrity of your file-sharing systems.",
+ "ImpactStatement": "Restricting CIFS access may require additional configuration and management effort. However, the benefits of enhanced security and reduced risk of unauthorized access to sensitive data far outweigh the potential challenges.",
+ "RemediationProcedure": "**From Console:** 1. Login to the AWS Management Console. 2. Navigate to the EC2 Dashboard and select the Security Groups section under `Network & Security`. 3. Identify the security group that allows unrestricted ingress on port 445. 4. Select the security group and click the `Edit Inbound Rules` button. 5. Locate the rule allowing unrestricted access on port 445 (typically listed as `0.0.0.0/0` or `::/0`). 6. Modify the rule to restrict access to specific IP ranges or trusted networks only. 7. Save the changes to the security group. **From Command Line:** 1. Run the following command to remove or modify the unrestricted rule for CIFS access: ``` aws ec2 revoke-security-group-ingress --region <region-name> --group-id <security-group-id> --protocol tcp --port 445 --cidr 0.0.0.0/0 ``` - Optionally, run the `authorise-security-group-ingress` command to create a new rule, specifying a trusted CIDR range instead of `0.0.0.0/0`. 2. Confirm the changes by describing the security group again and ensuring the unrestricted access rule has been removed or appropriately restricted: ``` aws ec2 describe-security-groups --region <region-name> --group-ids <security-group-id> --query 'SecurityGroups[*].IpPermissions[?ToPort==`445`].{CIDR:IpRanges[*].CidrIp,Port:ToPort}' ``` 3. Repeat the remediation for other security groups and regions as necessary.",
+ "AuditProcedure": "**From Console:** 1. Login to the AWS Management Console. 2. Navigate to the EC2 Dashboard and select the Security Groups section under `Network & Security`. 3. Identify the security groups associated with instances or resources that may be using CIFS. 4. Review the inbound rules of each security group to check for rules that allow unrestricted access on port 445 (the port used by CIFS). - Specifically, look for inbound rules that allow access from `0.0.0.0/0` or `::/0` on port 445. 5. Document any instances where unrestricted access is allowed and verify whether it is necessary for the specific use case. **From Command Line:** 1. Run the following command to list all security groups and identify those associated with CIFS: ``` aws ec2 describe-security-groups --region <region-name> --query 'SecurityGroups[*].GroupId' ``` 2. Check for any inbound rules that allow unrestricted access on port 445 using the following command: ``` aws ec2 describe-security-groups --region <region-name> --group-ids <security-group-id> --query 'SecurityGroups[*].IpPermissions[?ToPort==`445`].{CIDR:IpRanges[*].CidrIp,Port:ToPort}' ``` - Look for `0.0.0.0/0` or `::/0` in the output, which indicates unrestricted access. 3. Repeat the audit for other regions and security groups as necessary.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.2",
+ "Description": "Ensure no Network ACLs allow ingress from 0.0.0.0/0 to remote server administration ports",
+ "Checks": [
+ "ec2_networkacl_allow_ingress_any_port",
+ "ec2_networkacl_allow_ingress_tcp_port_22",
+ "ec2_networkacl_allow_ingress_tcp_port_3389"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The Network Access Control List (NACL) function provides stateless filtering of ingress and egress network traffic to AWS resources. It is recommended that no NACL allows unrestricted ingress access to remote server administration ports, such as SSH on port `22` and RDP on port `3389`, using either the TCP (6), UDP (17), or ALL (-1) protocols.",
+ "RationaleStatement": "Public access to remote server administration ports, such as 22 (when used for SSH, not SFTP) and 3389, increases the attack surface of resources and unnecessarily raises the risk of resource compromise.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Console:** Perform the following steps to remediate a network ACL: 1. Login to the AWS VPC Console at https://console.aws.amazon.com/vpc/home. 2. In the left pane, click `Network ACLs`. 3. For each network ACL that needs remediation, perform the following: - Select the network ACL. - Click the `Inbound Rules` tab. - Click `Edit inbound rules`. - Either A) update the Source field to a range other than 0.0.0.0/0, or B) click `Delete` to remove the offending inbound rule. - Click `Save`.",
+ "AuditProcedure": "**From Console:** Perform the following steps to determine if the account is configured as prescribed: 1. Login to the AWS VPC Console at https://console.aws.amazon.com/vpc/home. 2. In the left pane, click `Network ACLs`. 3. For each network ACL, perform the following: - Select the network ACL. - Click the `Inbound Rules` tab. - Ensure that no rule exists which has a port range that includes port `22` or `3389`, uses the protocols TCP (6), UDP (17), or ALL (-1), or other remote server administration ports for your environment, has a `Source` of `0.0.0.0/0`, and shows `ALLOW`. **Note:** A port value of `ALL` or a port range such as `0-3389` includes port `22`, `3389`, and potentially other remote server administration ports.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html:https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Security.html#VPC_Security_Comparison",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.3",
+ "Description": "Ensure no security groups allow ingress from 0.0.0.0/0 to remote server administration ports",
+ "Checks": [
+ "ec2_securitygroup_allow_ingress_from_internet_to_all_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_3389"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Security groups provide stateful filtering of ingress and egress network traffic to AWS resources. It is recommended that no security group allows unrestricted ingress access to remote server administration ports, such as SSH on port `22` and RDP on port `3389`, using either the TCP (6), UDP (17), or ALL (-1) protocols.",
+ "RationaleStatement": "Public access to remote server administration ports, such as 22 (when used for SSH, not SFTP) and 3389, increases the attack surface of resources and unnecessarily raises the risk of resource compromise.",
+ "ImpactStatement": "When updating an existing environment, ensure that administrators have access to remote server administration ports through another mechanism before removing access by deleting the 0.0.0.0/0 inbound rule.",
+ "RemediationProcedure": "Perform the following to implement the prescribed state: 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. In the left pane, click `Security Groups`. 3. For each security group, perform the following: - Select the security group. - Click the `Inbound Rules` tab. - Click the `Edit inbound rules` button. - Identify the rules to be edited or removed. - Either A) update the Source field to a range other than 0.0.0.0/0, or B) click `Delete` to remove the offending inbound rule. - Click `Save rules`.",
+ "AuditProcedure": "Perform the following to determine if the account is configured as prescribed: 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. In the left pane, click `Security Groups`. 3. For each security group, perform the following: - Select the security group. - Click the `Inbound Rules` tab. - Ensure that no rule exists which has a port range including port `22` or `3389`, uses the protocols TCP (6), UDP (17), or ALL (-1), or other remote server administration ports for your environment, and has a `Source` of `0.0.0.0/0`. **Note:** A port value of `ALL` or a port range such as `0-3389` includes port `22`, `3389`, and potentially other remote server administration ports.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html#deleting-security-group-rule",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.4",
+ "Description": "Ensure no security groups allow ingress from ::/0 to remote server administration ports",
+ "Checks": [
+ "ec2_securitygroup_allow_ingress_from_internet_to_all_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_3389"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Security groups provide stateful filtering of ingress and egress network traffic to AWS resources. It is recommended that no security group allows unrestricted ingress access to remote server administration ports, such as SSH on port `22` and RDP on port `3389`.",
+ "RationaleStatement": "Public access to remote server administration ports, such as 22 (when used for SSH, not SFTP) and 3389, increases attack surface of resources and unnecessarily raises the risk of resource compromise.",
+ "ImpactStatement": "When updating an existing environment, ensure that administrators have access to remote server administration ports through another mechanism before removing access by deleting the ::/0 inbound rule.",
+ "RemediationProcedure": "Perform the following to implement the prescribed state: 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. In the left pane, click `Security Groups`. 3. For each security group, perform the following: - Select the security group. - Click the `Inbound Rules` tab. - Click the `Edit inbound rules` button. - Identify the rules to be edited or removed. - Either A) update the Source field to a range other than ::/0, or B) Click `Delete` to remove the offending inbound rule. - Click `Save rules`.",
+ "AuditProcedure": "Perform the following to determine if the account is configured as prescribed: 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. In the left pane, click `Security Groups`. 3. For each security group, perform the following: - Select the security group. - Click the `Inbound Rules` tab. - Ensure that no rule exists which has a port range including port `22`, `3389`, or other remote server administration ports for your environment, and has a `Source` of `::/0`. **Note:** A port value of `ALL` or a port range such as `0-3389` includes port `22`, `3389`, and potentially other remote server administration ports.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html#deleting-security-group-rule",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.5",
+ "Description": "Ensure the default security group of every VPC restricts all traffic",
+ "Checks": [
+ "ec2_securitygroup_default_restrict_traffic"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "A VPC comes with a default security group whose initial settings deny all inbound traffic, allow all outbound traffic, and allow all traffic between instances assigned to the security group. If a security group is not specified when an instance is launched, it is automatically assigned to this default security group. Security groups provide stateful filtering of ingress/egress network traffic to AWS resources. It is recommended that the default security group restrict all traffic, both inbound and outbound. The default VPC in every region should have its default security group updated to comply with the following: - No inbound rules. - No outbound rules. Any newly created VPCs will automatically contain a default security group that will need remediation to comply with this recommendation. **Note:** When implementing this recommendation, VPC flow logging is invaluable in determining the least privilege port access required by systems to work properly, as it can log all packet acceptances and rejections occurring under the current security groups. This dramatically reduces the primary barrier to least privilege engineering by discovering the minimum ports required by systems in the environment. Even if the VPC flow logging recommendation in this benchmark is not adopted as a permanent security measure, it should be used during any period of discovery and engineering for least privileged security groups.",
+ "RationaleStatement": "Configuring all VPC default security groups to restrict all traffic will encourage the development of least privilege security groups and promote the mindful placement of AWS resources into security groups, which will, in turn, reduce the exposure of those resources.",
+ "ImpactStatement": "Implementing this recommendation in an existing VPC that contains operating resources requires extremely careful migration planning, as the default security groups are likely enabling many ports that are unknown. Enabling VPC flow logging (for accepted connections) in an existing environment that is known to be breach-free will reveal the current pattern of ports being used for each instance to communicate successfully. The migration process should include: - Analyzing VPC flow logs to understand current traffic patterns. - Creating least privilege security groups based on the analyzed data. - Testing the new security group rules in a staging environment before applying them to production.",
+ "RemediationProcedure": "Perform the following to implement the prescribed state: **Security Group Members** 1. Identify AWS resources that exist within the default security group. 2. Create a set of least-privilege security groups for those resources. 3. Place the resources in those security groups, removing the resources noted in step 1 from the default security group. **Security Group State** 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. Repeat the following steps for all VPCs, including the default VPC in each AWS region: 3. In the left pane, click `Security Groups`. 4. For each default security group, perform the following: - Select the `default` security group. - Click the `Inbound Rules` tab. - Remove any inbound rules. - Click the `Outbound Rules` tab. - Remove any Outbound rules. **Recommended** IAM groups allow you to edit the name field. After remediating default group rules for all VPCs in all regions, edit this field to add text similar to DO NOT USE. DO NOT ADD RULES.",
+ "AuditProcedure": "Perform the following to determine if the account is configured as prescribed: **Security Group State** 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. Repeat the following steps for all VPCs, including the default VPC in each AWS region: 3. In the left pane, click `Security Groups`. 4. For each default security group, perform the following: - Select the `default` security group. - Click the `Inbound Rules` tab and ensure no rules exist. - Click the `Outbound Rules` tab and ensure no rules exist. **Security Group Members** 1. Login to the AWS VPC Console at [https://console.aws.amazon.com/vpc/home](https://console.aws.amazon.com/vpc/home). 2. Repeat the following steps for all default groups in all VPCs, including the default VPC in each AWS region: 3. In the left pane, click `Security Groups`. 4. Copy the ID of the default security group. 5. Change to the EC2 Management Console at https://console.aws.amazon.com/ec2/v2/home. 6. In the filter column type `Security Group ID : <security-group-id-from-step-4>`.",
+ "AdditionalInformation": "",
+ "References": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html#default-security-group",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.6",
+ "Description": "Ensure routing tables for VPC peering are \"least access\"",
+ "Checks": [
+ "vpc_peering_routing_tables_with_least_privilege"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Once a VPC peering connection is established, routing tables must be updated to enable any connections between the peered VPCs. These routes can be as specific as desired, even allowing for the peering of a VPC to only a single host on the other side of the connection.",
+ "RationaleStatement": "Being highly selective in peering routing tables is a very effective way to minimize the impact of a breach, as resources outside of these routes are inaccessible to the peered VPC.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Remove and add route table entries to ensure that the least number of subnets or hosts required to accomplish the purpose of peering are routable. **From Command Line:** 1. For each `<route-table-id>` that contains routes that are non-compliant with your routing policy (granting more access than desired), delete the non-compliant route: ``` aws ec2 delete-route --route-table-id <route-table-id> --destination-cidr-block <non-compliant-destination-cidr> ``` 2. Create a new compliant route: ``` aws ec2 create-route --route-table-id <route-table-id> --destination-cidr-block <compliant-destination-cidr> --vpc-peering-connection-id <peering-connection-id> ```",
+ "AuditProcedure": "Review the routing tables of peered VPCs to determine whether they route all subnets of each VPC and whether this is necessary to accomplish the intended purposes of peering the VPCs. **From Command Line:** 1. List all the route tables from a VPC and check if the GatewayId is pointing to a `<peering-connection-id>` (e.g., pcx-1a2b3c4d) and if the DestinationCidrBlock is as specific as desired: ``` aws ec2 describe-route-tables --filter Name=vpc-id,Values=<vpc-id> --query RouteTables[*].{RouteTableId:RouteTableId, VpcId:VpcId, Routes:Routes, AssociatedSubnets:Associations[*].SubnetId} ```",
+ "AdditionalInformation": "If an organization has an AWS Transit Gateway implemented in its VPC architecture, it should look to apply the recommendation above for a least access routing architecture at the AWS Transit Gateway level, in combination with what must be implemented at the standard VPC route table. More specifically, to route traffic between two or more VPCs via a Transit Gateway, VPCs must have an attachment to a Transit Gateway route table as well as a route. Therefore, to avoid routing traffic between VPCs, an attachment to the Transit Gateway route table should only be added where there is an intention to route traffic between the VPCs. As Transit Gateways are capable of hosting multiple route tables, it is possible to group VPCs by attaching them to a common route table.",
+ "References": "https://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/peering-configurations-partial-access.html:https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-vpc-peering-connection.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.7",
+ "Description": "Ensure that the EC2 Metadata Service only allows IMDSv2",
+ "Checks": [
+ "ec2_instance_imdsv2_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "When enabling the Metadata Service on AWS EC2 instances, users have the option of using either Instance Metadata Service Version 1 (IMDSv1; a request/response method) or Instance Metadata Service Version 2 (IMDSv2; a session-oriented method).",
+ "RationaleStatement": "Instance metadata is data about your instance that you can use to configure or manage the running instance. Instance metadata is divided into [categories](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html), such as host name, events, and security groups. When enabling the Metadata Service on AWS EC2 instances, users have the option of using either Instance Metadata Service Version 1 (IMDSv1; a request/response method) or Instance Metadata Service Version 2 (IMDSv2; a session-oriented method). With IMDSv2, every request is now protected by session authentication. A session begins and ends a series of requests that software running on an EC2 instance uses to access the locally stored EC2 instance metadata and credentials. Allowing Version 1 of the service may open EC2 instances to Server-Side Request Forgery (SSRF) attacks, so Amazon recommends utilizing Version 2 for better instance security.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "From Console: 1. Sign in to the AWS Management Console and navigate to the EC2 dashboard at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 2. In the left navigation panel, under the `INSTANCES` section, choose `Instances`. 3. Select the EC2 instance that you want to examine. 4. Choose `Actions > Instance Settings > Modify instance metadata options`. 5. Set `Instance metadata service` to `Enable`. 6. Set `IMDSv2` to `Required`. 7. Repeat steps 1-6 to perform the remediation process for other EC2 instances in all applicable AWS region(s). From Command Line: 1. Run the `describe-instances` command, applying the appropriate filters to list the IDs of all existing EC2 instances currently available in the selected region: ``` aws ec2 describe-instances --region <region-name> --output table --query Reservations[*].Instances[*].InstanceId ``` 2. The command output should return a table with the requested instance IDs. 3. Run the `modify-instance-metadata-options` command with an instance ID obtained from the previous step to update the Instance Metadata Version: ``` aws ec2 modify-instance-metadata-options --instance-id <instance-id> --http-tokens required --region <region-name> ``` 4. Repeat steps 1-3 to perform the remediation process for other EC2 instances in the same AWS region. 5. Change the region by updating `--region` and repeat the process for other regions.",
+ "AuditProcedure": "From Console: 1. Sign in to the AWS Management Console and navigate to the EC2 dashboard at https://console.aws.amazon.com/ec2/. 2. In the left navigation panel, under the `INSTANCES` section, choose `Instances`. 3. Select the EC2 instance that you want to examine. 4. Check the `IMDSv2` status, and ensure that it is set to `Required`. From Command Line: 1. Run the `describe-instances` command using appropriate filters to list the IDs of all existing EC2 instances currently available in the selected region: ``` aws ec2 describe-instances --region <region-name> --output table --query Reservations[*].Instances[*].InstanceId ``` 2. The command output should return a table with the requested instance IDs. 3. Run the `describe-instances` command using the instance ID returned in the previous step and apply custom filtering to determine whether the selected instance is using IMDSv2: ``` aws ec2 describe-instances --region <region-name> --instance-ids <instance-id> --query Reservations[*].Instances[*].MetadataOptions --output table ``` 4. Ensure that for all EC2 instances, `HttpTokens` is set to `required` and `State` is set to `applied`. 5. Repeat steps 3 and 4 to verify the other EC2 instances provisioned within the current region. 6. Repeat steps 1–5 to perform the audit process for other AWS regions.",
+ "AdditionalInformation": "",
+ "References": "https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/:https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.8",
+ "Description": "Ensure VPC Endpoints are used for access to AWS Services",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Amazon VPCs use VPC endpoints (gateway or interface endpoints) for access to AWS services such as Amazon S3 and DynamoDB, so that traffic from workloads to AWS services stays on the Amazon private network instead of traversing the public internet. VPC endpoints provide private connectivity between VPCs and supported AWS services without requiring an internet gateway, NAT gateway, or public IP addresses.",
+ "RationaleStatement": "Accessing AWS services over the public internet increases exposure to network-level threats, relies on internet routing, and makes it harder to tightly control egress paths. Using VPC endpoints allows workloads to reach AWS services over the Amazon private network, which reduces reliance on internet gateways and NAT gateways, simplifies egress filtering, and helps enforce data-perimeter and \"private-only\" patterns for sensitive workloads.",
+ "ImpactStatement": "Enforcing the use of VPC endpoints may require changes to existing network architectures, including creating and managing endpoints in each VPC, updating route tables, adjusting security groups, and potentially removing or tightening some internet/NAT gateway paths. This can introduce additional operational overhead and cost (per-endpoint charges for interface endpoints) and may require updates to IaC templates and deployment pipelines.",
+ "RemediationProcedure": "In this example, we are going to add S3 gateway endpoint and SQS interface endpoint to a VPC. You can follow similar remediation instructions for other services. 1. Create S3 Gateway Endpoint ``` aws ec2 create-vpc-endpoint --region REGION --route-table-ids ROUTE_TABLE_ID --vpc-id VPC_ID --service-name com.amazonaws.REGION.s3 --vpc-endpoint-type Gateway --query \"VpcEndpoint.VpcEndpointId\" --output text ``` - Provide values for REGION, ROUTE_TABLE_ID, VPC_ID - AWS automatically creates the routes for the AWS service in the route table provided as part of above command. 2. Verify that the gateway routes have been adequately created ``` aws ec2 describe-route-tables --region REGION --route-table-ids ROUTE_TABLE_ID --query \"RouteTables[0].Routes[?DestinationPrefixListId=='pl-xxxxxxxx']\" ``` - Provide values for REGION, ROUTE_TABLE_ID - pl-xxxxxxxx: replace with the specific prefix list for S3 in that region 3. Create an SQS Interface Endpoint ``` aws ec2 create-vpc-endpoint --vpc-id VPC_ID --service-name com.amazonaws.REGION.sqs --vpc-endpoint-type Interface --subnet-ids PRIVATE_SUBNET_1_ID PRIVATE_SUBNET_2_ID --security-group-ids SECURITY_GROUP_ID --vpc-endpoint-policy VPC_ENDPOINT_POLICY --query \"VpcEndpoint.VpcEndpointId\" --output text ``` - SECURITY_GROUP_ID: Update security groups for interface endpoint. Ensure the interface endpoint security group allows inbound traffic from your workloads. - VPC_ENDPOINT_POLICY: Create a restrictive Endpoint policy to ensure only certain AWS services could be reached and only specific actions can be performed. - AWS automatically creates Elastic Network Interfaces (ENIs) for the interface endpoint which allows any traffic from PRIVATE_SUBNET_1_ID PRIVATE_SUBNET_2_ID intended for SQS to be routed through the Interface Gateway. 4. Test and validate endpoint connectivity from an EC2 instance in a private subnet: - Test S3 (gateway endpoint) ``` aws s3 ls s3://your-test-bucket --region REGION ``` - Test SQS (interface endpoint) ``` aws sqs list-queues --region REGION ```",
+ "AuditProcedure": "1. Identify in-scope VPCs and services. - Determine which VPCs host production or sensitive workloads that should access AWS services securely via endpoints. - For those VPCs, identify the AWS services they depend on (for example, S3 for data storage, DynamoDB for database, etc.). 2. For each in-scope VPC, check for existing VPC endpoints. ``` aws ec2 describe-vpc-endpoints --region REGION --filters \"Name=vpc-id,Values=VPC_ID\" --query \"VpcEndpoints[*].[VpcEndpointId,VpcEndpointType,ServiceName,State]\" --output table ``` - Provide the REGION and VPC_ID - `VpcEndpointType` tells you whether the endpoint is Gateway or Interface. - `ServiceName` shows which AWS service the endpoint is for (for example, com.amazonaws.us-east-1.s3, com.amazonaws.us-east-1.dynamodb, com.amazonaws.us-east-1.ssm). 3. For each interface endpoint, verify subnet attachment across relevant AZs/subnets. ``` aws ec2 describe-vpc-endpoints --region REGION --vpc-endpoint-ids INTERFACE_ENDPOINT_ID --query \"VpcEndpoints[*].[VpcEndpointId,ServiceName,SubnetIds,State]\" --output json ``` - Provide the REGION and INTERFACE_ENDPOINT_ID 4. For each gateway endpoint, verify that the route tables for the relevant subnets send traffic to the endpoint (via the AWS-managed prefix list), not via internet/NAT gateways. - Identify relevant subnets in the VPC that need to have a route to gateway endpoint: ``` aws ec2 describe-subnets --region REGION --filters \"Name=vpc-id,Values=,VPC_ID\" --query \"Subnets[*].[SubnetId,AvailabilityZone,MapPublicIpOnLaunch,CidrBlock]\" --output table ``` - Provide the REGION and VPC_ID - For each relevant subnet, identify the route table associated with it: ``` aws ec2 describe-route-tables --region REGION --filters \"Name=association.subnet-id,Values=SUBNET_ID\" --query \"RouteTables[*].RouteTableId\" --output text ``` - Provide the REGION and SUBNET_ID - For each route table associated with relevant subnets, inspect routes: ``` aws ec2 describe-route-tables --region REGION --route-table-ids ROUTE_TABLE_ID --query \"RouteTables[0].Routes[*].[DestinationPrefixListId,GatewayId,NatGatewayId,State]\" --output table ``` - Provide the REGION and ROUTE_TABLE_ID For S3/DynamoDB gateway endpoints, you should see a `DestinationPrefixListId` (for example, pl-xxxxxxxx) with `GatewayId` equal to the endpoint (vpce-xxxx). If S3/DynamoDB are used by workloads in those subnets but traffic is only routed via igw-xxxx or nat-xxxx (and no prefix-list/endpoint route exists), then VPC endpoints are not being used for securing network traffic for these services.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/aws/cisa_aws.json b/prowler/compliance/aws/cisa_aws.json
index fa8e27a061..27b06a1ea4 100644
--- a/prowler/compliance/aws/cisa_aws.json
+++ b/prowler/compliance/aws/cisa_aws.json
@@ -136,6 +136,20 @@
"ec2_securitygroup_default_restrict_traffic",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
"ec2_securitygroup_allow_ingress_from_internet_to_all_ports"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -367,6 +381,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/csa_ccm_4.0_aws.json b/prowler/compliance/aws/csa_ccm_4.0_aws.json
deleted file mode 100644
index 98d87112c9..0000000000
--- a/prowler/compliance/aws/csa_ccm_4.0_aws.json
+++ /dev/null
@@ -1,7617 +0,0 @@
-{
- "Framework": "CSA-CCM",
- "Name": "CSA Cloud Controls Matrix (CCM) v4.0.13",
- "Version": "4.0",
- "Provider": "AWS",
- "Description": "The Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing, composed of 197 control objectives structured in 17 domains covering all key aspects of cloud technology. The CCM can be used as a tool for the systematic assessment of a cloud implementation, and provides guidance on which security controls should be implemented by which actor within the cloud supply chain.",
- "Requirements": [
- {
- "Id": "A&A-02",
- "Description": "Conduct independent audit and assurance assessments according to relevant standards at least annually.",
- "Name": "Independent Assessments",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC4.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AAC-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.2",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.2.1",
- "27002: 18.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.35",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-2",
- "CA-2(1)",
- "CA-2(2)",
- "CA-7",
- "CA-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securityhub_enabled"
- ]
- },
- {
- "Id": "A&A-04",
- "Description": "Verify compliance with all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit.",
- "Name": "Requirements Compliance",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01",
- "GRM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.18.2.2",
- "27002: 18.2.2",
- "27001: A.18.2.3",
- "27002: 18.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-3",
- "DE.DP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securityhub_enabled",
- "config_recorder_all_regions_enabled"
- ]
- },
- {
- "Id": "AIS-04",
- "Description": "Define and implement a SDLC process for application design, development, deployment, and operation in accordance with security requirements defined by the organization.",
- "Name": "Secure Application Design and Development",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27017: 14.1.1",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.14.2.1",
- "27002: 14.2.1",
- "27017: 14.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.8",
- "27001: A.8.25",
- "27001: A.8.26",
- "27001: A.8.28"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PL-8",
- "PL-8(1)",
- "SA-3",
- "SA-3(1)",
- "SA-4",
- "SA-4(2)",
- "SA-4(3)",
- "SA-4(8)",
- "SA-4(9)",
- "SA-5",
- "SA-8",
- "SA-8(1)-(7)",
- "SA-8(9)-(13)",
- "SA-8(15)-(20)",
- "SA-8(22)",
- "SA-8(24)-(28)",
- "SA-8(30)-(33)",
- "SA-17",
- "SA-17(1)-(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-6",
- "PR.DS-7",
- "PR.IP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1",
- "6.2.3",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "codebuild_project_source_repo_url_no_sensitive_credentials",
- "codebuild_project_no_secrets_in_variables"
- ]
- },
- {
- "Id": "AIS-05",
- "Description": "Implement a testing strategy, including criteria for acceptance of new information systems, upgrades and new versions, which provides application security assurance and maintains compliance while enabling organizational speed of delivery goals. Automate when applicable and possible.",
- "Name": "Automated Application Security Testing",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.12",
- "16.13"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.3",
- "SD2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.8",
- "27001: A.14.2.9",
- "27001: A.12.1.2",
- "27002: 12.1.2",
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27001: A.14.2.2",
- "27002: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.25",
- "27001: A.8.29",
- "27001: A.8.32",
- "27002: 8.25 (e)",
- "27002: 8.32 (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SA-11",
- "SA-11(1)-(9)",
- "SI-6",
- "SI-6(2)",
- "SI-6(3)",
- "SI-10",
- "SI-10(1)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.IP-12",
- "DE.CM-8"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "PR.PS-01",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A.3.2.2",
- "A.3.2.2.1",
- "6.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.4",
- "6.4.1",
- "6.4.2",
- "6.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "inspector2_is_enabled",
- "ecr_repositories_scan_vulnerabilities_in_latest_image",
- "ecr_registry_scan_images_on_push_enabled"
- ]
- },
- {
- "Id": "AIS-07",
- "Description": "Define and implement a process to remediate application security vulnerabilities, automating remediation when possible.",
- "Name": "Application Vulnerability Remediation",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1",
- "CC7.4",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.2",
- "16.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27001: A.12.6.1",
- "27002: 12.6.1",
- "27017: 12.6.1",
- "27018: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.26",
- "27001: A.8.8",
- "27002: 5.26 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-2",
- "SI-2(2)-(6)",
- "SA-11",
- "SA-11(2)",
- "SA-15",
- "SA-15(1)-(3)",
- "SA-15(5)-(8)",
- "SA-15(10)-(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.IP-12",
- "DE.CM-8",
- "RS.AN-5",
- "RS.MI-3",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.2",
- "6.5",
- "6.5.1-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "11.3.1",
- "11.3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "inspector2_is_enabled",
- "inspector2_active_findings_exist"
- ]
- },
- {
- "Id": "BCR-08",
- "Description": "Periodically backup data stored in the cloud. Ensure the confidentiality, integrity and availability of the backup, and verify data restoration from backup for resiliency.",
- "Name": "Backup",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "A1.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "11.1",
- "11.2",
- "11.3",
- "11.4",
- "11.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27017: 12.3",
- "27018: 12.3.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.13",
- "27001: A.5.23",
- "27001: A.5.30",
- "27002: 8.13",
- "27002: 5.23 2nd (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-4",
- "CP-4(4)",
- "CP-6",
- "CP-6(1)-(3)",
- "CP-9",
- "CP-9(1)",
- "CP-9(2)",
- "CP-10",
- "CP-10(2)",
- "CP-10(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-4",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-11",
- "RC.RP-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.5.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "10.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "backup_plans_exist",
- "backup_vaults_exist",
- "backup_vaults_encrypted",
- "backup_recovery_point_encrypted",
- "dynamodb_tables_pitr_enabled",
- "dynamodb_table_protected_by_backup_plan",
- "ec2_ebs_volume_snapshots_exists",
- "ec2_ebs_volume_protected_by_backup_plan",
- "efs_have_backup_enabled",
- "rds_instance_backup_enabled",
- "rds_instance_protected_by_backup_plan",
- "rds_cluster_protected_by_backup_plan",
- "redshift_cluster_automated_snapshot",
- "s3_bucket_object_versioning",
- "documentdb_cluster_backup_enabled",
- "neptune_cluster_backup_enabled",
- "elasticache_redis_cluster_backup_enabled",
- "fsx_file_system_copy_tags_to_backups_enabled",
- "lightsail_instance_automated_snapshots",
- "dlm_ebs_snapshot_lifecycle_policy_exists"
- ]
- },
- {
- "Id": "BCR-09",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain a disaster response plan to recover from natural and man-made disasters. Update the plan at least annually or upon significant changes.",
- "Name": "Disaster Response Plan",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9",
- "1.6.1",
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.4",
- "BC2.1",
- "BC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.29",
- "27001: A.5.30",
- "27002: 5.29",
- "27002: 5.30"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2(1)",
- "CP-2(2)",
- "CP-2(3)",
- "CP-2(5)",
- "CP-2(6)",
- "CP-2(7)",
- "CP-2(8)",
- "PE-13",
- "PE-13(1)",
- "PE-13(2)",
- "PE-13(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-9",
- "PR.IP-10",
- "RC.IM-1",
- "RC.IM-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-04"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "drs_job_exist",
- "ssmincidents_enabled_with_plans"
- ]
- },
- {
- "Id": "BCR-11",
- "Description": "Supplement business-critical equipment with redundant equipment independently located at a reasonable minimum distance in accordance with applicable industry standards.",
- "Name": "Equipment Redundancy",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-06"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.20",
- "27001: A.7.11",
- "27001: A.8.14",
- "27002: 5.20 (t)",
- "27002: 8.14 (c)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "CP-4(3)",
- "CP-6",
- "CP-6(1)",
- "CP-7",
- "CP-8",
- "CP-8(1)-(3)",
- "CP-9",
- "CP-9(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.BE-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.OC-04",
- "GV.OC-05",
- "PR.IR-03"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "rds_instance_multi_az",
- "rds_cluster_multi_az",
- "elbv2_is_in_multiple_az",
- "elb_is_in_multiple_az",
- "autoscaling_group_multiple_az",
- "autoscaling_group_multiple_instance_types",
- "ec2_ebs_volume_protected_by_backup_plan",
- "elasticache_redis_cluster_multi_az_enabled",
- "elasticache_redis_cluster_automatic_failover_enabled",
- "opensearch_service_domains_fault_tolerant_data_nodes",
- "opensearch_service_domains_fault_tolerant_master_nodes",
- "dynamodb_accelerator_cluster_multi_az",
- "documentdb_cluster_multi_az_enabled",
- "neptune_cluster_multi_az",
- "efs_multi_az_enabled",
- "vpc_vpn_connection_tunnels_up",
- "directconnect_connection_redundancy",
- "directconnect_virtual_interface_redundancy",
- "networkfirewall_multi_az",
- "vpc_endpoint_multi_az_enabled",
- "awslambda_function_vpc_multi_az",
- "redshift_cluster_multi_az_enabled"
- ]
- },
- {
- "Id": "CCC-04",
- "Description": "Restrict the unauthorized addition, removal, update, and management of organization assets.",
- "Name": "Unauthorized Change Protection",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "CCC-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.1",
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4",
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.1.4",
- "27002: 12.1.4",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27001: A.14.2.2",
- "27017: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.3",
- "27001: A.8.4",
- "27001: A.8.15",
- "27001: A.8.31",
- "27001: A.8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(4)",
- "CM-3",
- "CM-3(1)",
- "CM-3(5)",
- "CM-3(7)",
- "CM-3(8)",
- "CM-5",
- "CM-5(1)",
- "CM-5(4)",
- "CM-5(5)",
- "CM-6",
- "CM-6(1)",
- "CM-6(2)",
- "CM-7",
- "CM-7(1)",
- "CM-7(4)",
- "CM-7(5)",
- "CM-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.MA-1",
- "PR.MA-2",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04",
- "ID.AM-08",
- "PR.PS-02",
- "PR.PS-03",
- "PR.PS-05",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.1",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_multi_region_enabled",
- "cloudtrail_log_file_validation_enabled",
- "s3_bucket_object_lock",
- "cloudwatch_log_metric_filter_aws_organizations_changes",
- "servicecatalog_portfolio_shared_within_organization_only"
- ]
- },
- {
- "Id": "CCC-07",
- "Description": "Implement detection measures with proactive notification in case of changes deviating from the established baseline.",
- "Name": "Detection of Baseline Deviation",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.1",
- "1.5.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.2",
- "27001: A.14.2.4",
- "27001: A.12.4.1",
- "27002: 12.4.1 (g)",
- "27001: A.5.1.1",
- "27017: 5.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.9",
- "27001: A.8.15",
- "27002: 8.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(2)",
- "SI-2",
- "SI-2(2)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.MA-1",
- "PR.IP-1",
- "DE.DP-4",
- "PR.IP-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01",
- "DE.CM-09",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.3",
- "6.4.5.4",
- "11.5",
- "11.5.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "11.5.2",
- "11.6.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "config_recorder_all_regions_enabled",
- "guardduty_is_enabled",
- "securityhub_enabled",
- "cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled",
- "cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled",
- "cloudwatch_changes_to_network_acls_alarm_configured",
- "cloudwatch_changes_to_network_gateways_alarm_configured",
- "cloudwatch_changes_to_network_route_tables_alarm_configured",
- "cloudwatch_log_metric_filter_authentication_failures",
- "cloudwatch_log_metric_filter_aws_organizations_changes",
- "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk"
- ]
- },
- {
- "Id": "CEK-03",
- "Description": "Provide cryptographic protection to data at-rest and in-transit, using cryptographic libraries certified to approved standards.",
- "Name": "Data Encryption",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-03",
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6",
- "3.1",
- "3.11",
- "11.3",
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.1",
- "27001: A.18.1.2",
- "27001: A.18.1.3",
- "27001: A.18.1.4",
- "27001: A.18.1.5",
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.18",
- "27002: 18",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27001: A.14.1.3",
- "27002 14.1.3 c)",
- "27001 - A.10.1.1",
- "27017 - 10.1.1",
- "27001 - A.10.1.2",
- "27017 - 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.24",
- "27002: 8.24 Other Information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19",
- "AC-19(5)",
- "SC-8",
- "SC-8(1)",
- "SC-8(3)",
- "SC-8(4)",
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)-(3)",
- "SI-4",
- "SI-4(10)",
- "SI-7",
- "SI-7(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "Requirement 3",
- "2.2.3",
- "2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ec2_ebs_volume_encryption",
- "ec2_ebs_default_encryption",
- "ec2_ebs_snapshots_encrypted",
- "s3_bucket_default_encryption",
- "s3_bucket_kms_encryption",
- "s3_bucket_secure_transport_policy",
- "rds_instance_storage_encrypted",
- "rds_cluster_storage_encrypted",
- "rds_instance_transport_encrypted",
- "rds_snapshots_encrypted",
- "efs_encryption_at_rest_enabled",
- "dynamodb_tables_kms_cmk_encryption_enabled",
- "dynamodb_accelerator_cluster_encryption_enabled",
- "dynamodb_accelerator_cluster_in_transit_encryption_enabled",
- "kinesis_stream_encrypted_at_rest",
- "firehose_stream_encrypted_at_rest",
- "sns_topics_kms_encryption_at_rest_enabled",
- "sqs_queues_server_side_encryption_enabled",
- "cloudtrail_kms_encryption_enabled",
- "cloudwatch_log_group_kms_encryption_enabled",
- "opensearch_service_domains_encryption_at_rest_enabled",
- "opensearch_service_domains_node_to_node_encryption_enabled",
- "opensearch_service_domains_https_communications_enforced",
- "redshift_cluster_encrypted_at_rest",
- "redshift_cluster_in_transit_encryption_enabled",
- "documentdb_cluster_storage_encrypted",
- "neptune_cluster_storage_encrypted",
- "neptune_cluster_snapshot_encrypted",
- "elasticache_redis_cluster_rest_encryption_enabled",
- "elasticache_redis_cluster_in_transit_encryption_enabled",
- "kafka_cluster_in_transit_encryption_enabled",
- "kafka_cluster_encryption_at_rest_uses_cmk",
- "kafka_connector_in_transit_encryption_enabled",
- "dms_endpoint_ssl_enabled",
- "dms_endpoint_redis_in_transit_encryption_enabled",
- "elb_ssl_listeners",
- "elbv2_ssl_listeners",
- "elbv2_insecure_ssl_ciphers",
- "elbv2_nlb_tls_termination_enabled",
- "cloudfront_distributions_https_enabled",
- "cloudfront_distributions_origin_traffic_encrypted",
- "cloudfront_distributions_custom_ssl_certificate",
- "transfer_server_in_transit_encryption_enabled",
- "sagemaker_notebook_instance_encryption_enabled",
- "sagemaker_training_jobs_volume_and_output_encryption_enabled",
- "workspaces_volume_encryption_enabled",
- "storagegateway_fileshare_encryption_enabled",
- "backup_vaults_encrypted",
- "backup_recovery_point_encrypted",
- "athena_workgroup_encryption",
- "glue_data_catalogs_connection_passwords_encryption_enabled",
- "glue_data_catalogs_metadata_encryption_enabled",
- "glue_etl_jobs_amazon_s3_encryption_enabled",
- "glue_etl_jobs_cloudwatch_logs_encryption_enabled",
- "glue_etl_jobs_job_bookmark_encryption_enabled",
- "glue_development_endpoints_s3_encryption_enabled",
- "glue_development_endpoints_cloudwatch_logs_encryption_enabled",
- "glue_development_endpoints_job_bookmark_encryption_enabled",
- "glue_ml_transform_encrypted_at_rest",
- "bedrock_model_invocation_logs_encryption_enabled",
- "bedrock_prompt_encrypted_with_cmk",
- "codebuild_project_s3_logs_encrypted",
- "codebuild_report_group_export_encrypted"
- ]
- },
- {
- "Id": "CEK-04",
- "Description": "Use encryption algorithms that are appropriate for data protection, considering the classification of data, associated risks, and usability of the encryption technology.",
- "Name": "Encryption Algorithm",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.2",
- "27002: 8.2",
- "27001: A.8.3",
- "27001: A.10.1.1",
- "27002: 10.1.1 (b)",
- "27001: A.10.1.2",
- "27002: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.24",
- "27001: A.5.12",
- "27001: A.5.13",
- "27002: 8.24 General (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A2",
- "Requirement 3",
- "2.3",
- "2.2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "acm_certificates_with_secure_key_algorithms",
- "elb_insecure_ssl_ciphers",
- "elbv2_insecure_ssl_ciphers",
- "cloudfront_distributions_using_deprecated_ssl_protocols"
- ]
- },
- {
- "Id": "CEK-08",
- "Description": "CSPs must provide the capability for CSCs to manage their own data encryption keys.",
- "Name": "CSC Key Management Capability",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27017: 10.1",
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.23",
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-9",
- "CP-9(8)",
- "SA-9",
- "SA-9(6)",
- "SC-12",
- "SC-12(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.AM-6",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-05"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_cmk_are_used",
- "s3_bucket_kms_encryption",
- "dynamodb_tables_kms_cmk_encryption_enabled",
- "kms_key_not_publicly_accessible",
- "kms_cmk_not_multi_region"
- ]
- },
- {
- "Id": "CEK-10",
- "Description": "Generate Cryptographic keys using industry accepted cryptographic libraries specifying the algorithm strength and the random number generator used.",
- "Name": "Key Generation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "TS2.3",
- "SY1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27002: 10.1.1 (e)",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2",
- "27002: 10.1.2 (a)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24",
- "27002: 8.24 (d), Key management (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2.3",
- "3.6.1",
- "PCI Glossary - Cryptographic Key Generation"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.6.1.1",
- "3.7.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_cmk_are_used"
- ]
- },
- {
- "Id": "CEK-12",
- "Description": "Rotate cryptographic keys in accordance with the calculated cryptoperiod, which includes provisions for considering the risk of information disclosure and legal and regulatory requirements.",
- "Name": "Key Rotation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2 e)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (e,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_cmk_rotation_enabled",
- "iam_rotate_access_key_90_days",
- "secretsmanager_automatic_rotation_enabled",
- "secretsmanager_secret_rotated_periodically"
- ]
- },
- {
- "Id": "CEK-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.",
- "Name": "Key Destruction",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27017: 10.1.2",
- "27001: A.10.1.2",
- "27002: 10.1.2 (j)",
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (j,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.IP-6",
- "ID.GV-3",
- "PR.DS-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "ID.AM-08",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.6.4",
- "3.6.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_cmk_not_deleted_unintentionally"
- ]
- },
- {
- "Id": "DCS-06",
- "Description": "Catalogue and track all relevant physical and logical assets located at all of the CSP's sites within a secured system.",
- "Name": "Assets Cataloguing and Tracking",
- "Attributes": [
- {
- "Section": "Datacenter Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DCS - 01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "1.1",
- "2.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27017: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-8",
- "CM-8(1)",
- "CM-8(2)",
- "CM-8(4)",
- "CM-8(7)",
- "CM-8(8)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4",
- "9.7.1",
- "9.9.1",
- "9.9.1.a",
- "9.9.1.b",
- "9.9.1.c",
- "12.3.3",
- "12.3.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1.1",
- "6.3.2",
- "9.4.2",
- "9.4.3",
- "12.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "config_recorder_all_regions_enabled",
- "resourceexplorer2_indexes_found"
- ]
- },
- {
- "Id": "DSP-02",
- "Description": "Apply industry accepted methods for the secure disposal of data from storage media such that data is not recoverable by any forensic means.",
- "Name": "Secure Disposal",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3",
- "CC6.4",
- "CC6.5",
- "CC6.7",
- "P4.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-07"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.3",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.3.2",
- "27002: 8.3.2",
- "27001: A.11.2.7",
- "27002: 11.2.7"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.7.10",
- "27001: A.7.14",
- "27001: A.8.10",
- "27002: 7.10 (Secure reuse or disposal)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-22",
- "SI-12",
- "SI-12(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-10",
- "PR.PS-02",
- "PR.PS-03",
- "ID.AM-08"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1",
- "9.8",
- "9.8.1",
- "9.8.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "3.7.5",
- "9.4.7"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "s3_bucket_lifecycle_enabled",
- "dlm_ebs_snapshot_lifecycle_policy_exists",
- "ecr_repositories_lifecycle_policy_enabled"
- ]
- },
- {
- "Id": "DSP-03",
- "Description": "Create and maintain a data inventory, at least for any sensitive data and personal data.",
- "Name": "Data Inventory",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2",
- "1.3.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-12",
- "CM-12(1)",
- "PM-5",
- "PM-5(1)",
- "SI-12",
- "SI-12(1)",
- "SI-19",
- "SI-19(1)",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "9.4.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "macie_is_enabled",
- "macie_automated_sensitive_data_discovery_enabled",
- "config_recorder_all_regions_enabled"
- ]
- },
- {
- "Id": "DSP-04",
- "Description": "Classify data according to its type and sensitivity level.",
- "Name": "Data Classification",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "C1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.2.1",
- "27002: 8.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-16",
- "AC-16(9)",
- "PM-22",
- "PM-23",
- "PT-2",
- "PT-2(1)",
- "SI-18",
- "SI-18(2)",
- "SI-19",
- "SI-19(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-05",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "9.4.2",
- "9.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "macie_is_enabled",
- "macie_automated_sensitive_data_discovery_enabled"
- ]
- },
- {
- "Id": "DSP-07",
- "Description": "Develop systems, products, and business practices based upon a principle of security by design and industry best practices.",
- "Name": "Data Protection by Design and Default",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "PI1.2",
- "PI1.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.1",
- "5.3.2",
- "5.3.3",
- "5.3.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.2",
- "IM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002:14.1.1",
- "27001: A.14.2.5",
- "27002:14.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.27",
- "27001: A.8.28",
- "27001: A.8.29",
- "27002: 5.8 (Information security requirements a-i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-17",
- "PM-24",
- "PM-25",
- "PT-2",
- "PT-2(2)",
- "SA-3",
- "SA-4",
- "SA-5",
- "SA-8",
- "SA-8(9)",
- "SA-8(13)",
- "SA-8(18)",
- "SA-8(20)",
- "SA-8(22)",
- "SA-8(23)",
- "SA-8(33)",
- "SA-15",
- "SA-15(12)",
- "SC-3",
- "SC-3(3)",
- "SC-7",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(4)",
- "SC-28",
- "SC-28(1)",
- "SI-12",
- "SI-12(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ec2_ebs_default_encryption",
- "s3_account_level_public_access_blocks",
- "s3_bucket_level_public_access_block",
- "ec2_ebs_snapshot_account_block_public_access",
- "rds_instance_no_public_access",
- "rds_snapshots_public_access"
- ]
- },
- {
- "Id": "DSP-10",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope as permitted by the respective laws and regulations.",
- "Name": "Sensitive Data Transfer",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.12",
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "9.5.1",
- "9.5.2",
- "9.5.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.8.3.3",
- "27002: 8.3.3",
- "27001: A.13.2.3",
- "27002: 13.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.7.10"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-4",
- "AC-4(23)-(25)",
- "CA-3",
- "CA-3(6)",
- "CA-6",
- "CA-6(1)",
- "CA-6(2)",
- "SC-4",
- "SC-4(2)",
- "SC-7",
- "SC-7(10)",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-16",
- "SC-16(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.DS-5",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.IR-01",
- "ID.AM-03",
- "GV.OC-03",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "4.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.1.1",
- "4.2.1",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "s3_bucket_secure_transport_policy",
- "opensearch_service_domains_https_communications_enforced",
- "redshift_cluster_in_transit_encryption_enabled",
- "rds_instance_transport_encrypted",
- "transfer_server_in_transit_encryption_enabled",
- "kafka_cluster_mutual_tls_authentication_enabled"
- ]
- },
- {
- "Id": "DSP-16",
- "Description": "Data retention, archiving and deletion is managed in accordance with business requirements, applicable laws and regulations.",
- "Name": "Data Retention and Deletion",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "C1.1",
- "C1.2",
- "CC3.1",
- "P4.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.4",
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.10",
- "27002: 5.33 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-12",
- "SI-12(1)-(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)",
- "SI-19",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-3",
- "PR.IP-6",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "GV.OC-03",
- "GV.SC-10",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "s3_bucket_lifecycle_enabled",
- "cloudwatch_log_group_retention_policy_specific_days_enabled",
- "kinesis_stream_data_retention_period",
- "ecr_repositories_lifecycle_policy_enabled"
- ]
- },
- {
- "Id": "DSP-17",
- "Description": "Define and implement, processes, procedures and technical measures to protect sensitive data throughout it's lifecycle.",
- "Name": "Sensitive Data Protection",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSC-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.1",
- "CC6.1",
- "CC6.3",
- "CC6.7",
- "CC8.1",
- "C1.1",
- "P2.0",
- "P3.0",
- "P4.0",
- "P5.0",
- "P6.0"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.1",
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.3",
- "9.1.1",
- "9.2.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001:A.18.1.4",
- "27002:18.1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.11",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PM-22",
- "PM-24",
- "PT-7",
- "PT-7(1)",
- "PT-7(2)",
- "PT-8",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.0 (including all subsections)",
- "4.0 (including all subsections)"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.1.1",
- "4.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "s3_account_level_public_access_blocks",
- "s3_bucket_public_access",
- "s3_bucket_policy_public_write_access",
- "ec2_ebs_public_snapshot",
- "rds_snapshots_public_access",
- "rds_instance_no_public_access",
- "ec2_ebs_volume_encryption",
- "s3_bucket_default_encryption",
- "rds_instance_storage_encrypted",
- "secretsmanager_not_publicly_accessible",
- "macie_is_enabled"
- ]
- },
- {
- "Id": "GRC-05",
- "Description": "Develop and implement an Information Security Program, which includes programs for all the relevant domains of the CCM.",
- "Name": "Information Security Program",
- "Attributes": [
- {
- "Section": "Governance, Risk and Compliance",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "14.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SG2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-1",
- "PM-3",
- "PM-14",
- "PL-2",
- "PM-18",
- "PM-31"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.4.1",
- "A.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.4.1",
- "A3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "securityhub_enabled",
- "guardduty_is_enabled"
- ]
- },
- {
- "Id": "IAM-02",
- "Description": "Establish, document, approve, communicate, implement, apply, evaluate and maintain strong password policies and procedures. Review and update the policies and procedures at least annually.",
- "Name": "Strong Password Policy and Procedures",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-12",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "4.1.2",
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1",
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.7.2.2",
- "27002: 7.2.2",
- "27001: A.9.2.6",
- "27002: 9.2.6",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.17",
- "27001: A.6.3",
- "27001: A.8.5",
- "27001: A.5.37"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-3",
- "AC-3(3)",
- "AC-12",
- "AC-12(1)",
- "IA-2",
- "IA-2(10)",
- "IA-5",
- "IA-5(1)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.AC-1",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.4",
- "12.1",
- "12.1.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.1.1",
- "8.3.8"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_password_policy_minimum_length_14",
- "iam_password_policy_lowercase",
- "iam_password_policy_uppercase",
- "iam_password_policy_number",
- "iam_password_policy_symbol",
- "iam_password_policy_reuse_24",
- "iam_password_policy_expires_passwords_within_90_days_or_less",
- "cognito_user_pool_password_policy_minimum_length_14",
- "cognito_user_pool_password_policy_lowercase",
- "cognito_user_pool_password_policy_uppercase",
- "cognito_user_pool_password_policy_number",
- "cognito_user_pool_password_policy_symbol"
- ]
- },
- {
- "Id": "IAM-03",
- "Description": "Manage, store, and review the information of system identities, and level of access.",
- "Name": "Identity Inventory",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-04",
- "IAM-08",
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27001: A.9.4.1",
- "27002: 9.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.5.15",
- "27001: A.5.16",
- "27001: A.5.18",
- "27001: A.7.4",
- "27001: A.8.15",
- "27001: A.8.2",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "AU-16",
- "AU-16(1)",
- "IA-4",
- "IA-4(8)",
- "IA-4(9)",
- "IA-5",
- "IA-5(5)",
- "IA-8",
- "IA-8(4)",
- "PM-5(1)",
- "SA-8",
- "SA-8(22)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-04",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4.a"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_sagemaker",
- "iam_user_accesskey_unused",
- "iam_user_console_access_unused",
- "iam_user_two_active_access_key"
- ]
- },
- {
- "Id": "IAM-04",
- "Description": "Employ the separation of duties principle when implementing information system access.",
- "Name": "Separation of Duties",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC1.3",
- "CC5.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.2",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.6.1.2",
- "27002: 6.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18",
- "27001: A.5.3",
- "27001: A.8.2"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-6",
- "AC-6(1)-(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4",
- "6.4.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_policy_attached_only_to_group_or_roles",
- "iam_securityaudit_role_created",
- "iam_support_role_created"
- ]
- },
- {
- "Id": "IAM-05",
- "Description": "Employ the least privilege principle when implementing information system access.",
- "Name": "Least Privilege",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-06",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.1",
- "27002: 9.1.1",
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.8.2",
- "27002: 5.15 (Other information 2nd (a))"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "IA-12",
- "IA-12(2)",
- "IA-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1",
- "7.1.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2",
- "7.2.5",
- "7.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_inline_policy_no_wildcard_marketplace_subscribe",
- "iam_policy_no_wildcard_marketplace_subscribe",
- "iam_aws_attached_policy_no_administrative_privileges",
- "iam_customer_attached_policy_no_administrative_privileges",
- "iam_inline_policy_no_administrative_privileges",
- "iam_customer_unattached_policy_no_administrative_privileges",
- "iam_policy_allows_privilege_escalation",
- "iam_inline_policy_allows_privilege_escalation",
- "iam_no_custom_policy_permissive_role_assumption",
- "iam_role_administratoraccess_policy",
- "iam_user_administrator_access_policy",
- "iam_group_administrator_access_policy",
- "iam_administrator_access_with_mfa"
- ]
- },
- {
- "Id": "IAM-07",
- "Description": "De-provision or respectively modify access of movers / leavers or system identity changes in a timely manner in order to effectively adopt and communicate identity and access management policies.",
- "Name": "User Access Changes and Revocation",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.3",
- "6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(1)",
- "AC-2(2)",
- "AC-2(6)",
- "AC-2(8)",
- "AC-3",
- "AC-3(8)",
- "AC-6",
- "AC-6(7)",
- "AU-10",
- "AU-10(4)",
- "AU-16",
- "AU-16(1)",
- "CM-7",
- "CM-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.IP-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-04",
- "GV.SC-10",
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.5",
- "8.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_sagemaker",
- "iam_user_accesskey_unused",
- "iam_user_console_access_unused",
- "iam_user_no_setup_initial_access_key"
- ]
- },
- {
- "Id": "IAM-08",
- "Description": "Review and revalidate user access for least privilege and separation of duties with a frequency that is commensurate with organizational risk tolerance.",
- "Name": "User Access Review",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27001: A.9.2.6",
- "27001: A.9.4.1",
- "27017: 9.4.1",
- "27001: A.6.1.2",
- "27001: A 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.3",
- "27001: A.5.18",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "AC-6(8)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5.1",
- "7.2.5",
- "7.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_bedrock",
- "iam_user_access_not_stale_to_sagemaker",
- "iam_user_accesskey_unused",
- "iam_user_console_access_unused",
- "iam_rotate_access_key_90_days",
- "secretsmanager_secret_unused"
- ]
- },
- {
- "Id": "IAM-09",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the segregation of privileged access roles such that administrative access to data, encryption and key management capabilities and logging capabilities are distinct and separated.",
- "Name": "Segregation of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.1",
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-3(7)",
- "AC-6(4)",
- "AC-6(8)",
- "IA-5",
- "IA-5(6)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.3",
- "3.5.2",
- "7.1.2",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.7.6",
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_policy_attached_only_to_group_or_roles",
- "iam_role_administratoraccess_policy",
- "iam_avoid_root_usage",
- "iam_no_root_access_key"
- ]
- },
- {
- "Id": "IAM-10",
- "Description": "Define and implement an access process to ensure privileged access roles and rights are granted for a time limited period, and implement procedures to prevent the culmination of segregated privileged access.",
- "Name": "Management of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "6.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3",
- "27001: A.9.4.4",
- "27002: 9.4.4",
- "27017: 9.4.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(7)",
- "AC-3",
- "AC-3(4)",
- "AC-3(11)",
- "AC-3(13)",
- "AC-3(14)",
- "AC-6",
- "AC-6(4)",
- "AC-6(5)",
- "AC-6(8)",
- "AC-12",
- "AC-12(3)",
- "AC-17",
- "AC-17(4)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_avoid_root_usage",
- "iam_no_root_access_key",
- "iam_role_cross_account_readonlyaccess_policy",
- "iam_role_cross_service_confused_deputy_prevention",
- "iam_inline_policy_allows_privilege_escalation",
- "iam_policy_allows_privilege_escalation"
- ]
- },
- {
- "Id": "IAM-12",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the logging infrastructure is read-only for all with write access, including privileged access roles, and that the ability to disable it is controlled through a procedure that ensures the segregation of duties and break glass procedures.",
- "Name": "Safeguard Logs Integrity",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.3"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1",
- "27018: 12.4.1",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27017: 12.4.2",
- "27018: 12.4.2",
- "27001: A.12.4.3",
- "27002: 12.4.3",
- "27017: 12.4.3",
- "27018: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.18",
- "27002: 8.15 Protection of Logs"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(11)",
- "AC-2(12)",
- "IA-8",
- "IA-8(4)",
- "SA-8",
- "SA-8(22)",
- "SC-34",
- "SC-34(1)",
- "SC-34(2)",
- "SC-36",
- "SI-4",
- "SI-4(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_log_file_validation_enabled",
- "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
- "cloudtrail_logs_s3_bucket_access_logging_enabled",
- "cloudtrail_kms_encryption_enabled",
- "cloudtrail_bucket_requires_mfa_delete"
- ]
- },
- {
- "Id": "IAM-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure users are identifiable through unique IDs or which can associate individuals to the usage of user IDs.",
- "Name": "Uniquely Identifiable Users",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.1",
- "27002: 9.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(14)",
- "AC-24",
- "AC-24(2)",
- "AU-10",
- "AU-10(1)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-4",
- "IA-4(1)",
- "SA-8",
- "SA-8(22)",
- "SC-23",
- "SC-23(3)",
- "SC-40(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1",
- "8.2",
- "8.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.1",
- "8.2.2",
- "8.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_user_mfa_enabled_console_access",
- "iam_check_saml_providers_sts"
- ]
- },
- {
- "Id": "IAM-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for authenticating access to systems, application and data assets, including multifactor authentication for at least privileged user and sensitive data access. Adopt digital certificates or alternatives which achieve an equivalent level of security for system identities.",
- "Name": "Strong Authentication",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.3",
- "6.5",
- "12.5",
- "12.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4",
- "SA1.8"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27017: 9.1.2",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.9.4.2",
- "27002: 9.4.2",
- "27017: 9.4.2",
- "27018: 9.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.17",
- "27001: A.8.5",
- "27001: A.8.24",
- "27002: 8.5",
- "27002: 8.24 other information (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(5)",
- "AC-7",
- "AC-7(4)",
- "AU-10",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(8)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5",
- "IA-5(2)",
- "IA-5(7)",
- "IA-5(9)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-5(14)-(16)",
- "IA-8",
- "IA-8(1)",
- "IA-8(6)",
- "SC-23",
- "SC-23(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3",
- "8.1.6",
- "8.2",
- "8.3",
- "8.3.2",
- "12.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "8.3.1",
- "8.3.2",
- "8.4.1",
- "8.4.2",
- "8.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_root_mfa_enabled",
- "iam_root_hardware_mfa_enabled",
- "iam_user_mfa_enabled_console_access",
- "iam_user_hardware_mfa_enabled",
- "cognito_user_pool_mfa_enabled"
- ]
- },
- {
- "Id": "IAM-15",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the secure management of passwords.",
- "Name": "Passwords Management",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27018: 9.2.4",
- "27001: A.9.3.1",
- "27002: 9.3.1",
- "27017: 9.3.1",
- "27018: 9.3.1",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.17"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IA-4",
- "IA-4(8)",
- "IA-5",
- "IA-5(1)",
- "IA-5(8)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.2",
- "8.2.1-6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.2",
- "2.3.1",
- "8.3.5",
- "8.3.6",
- "8.3.7",
- "8.3.8",
- "8.3.9",
- "8.3.10",
- "8.3.10.1",
- "8.6.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_password_policy_minimum_length_14",
- "iam_password_policy_reuse_24",
- "iam_password_policy_expires_passwords_within_90_days_or_less",
- "cognito_user_pool_password_policy_minimum_length_14",
- "cognito_user_pool_temporary_password_expiration"
- ]
- },
- {
- "Id": "IAM-16",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to verify access to data and system functions is authorized.",
- "Name": "Authorization Mechanisms",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27002: 9.2.5",
- "27017: 9.2.5",
- "27018: 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(5)",
- "AC-4",
- "AC-4(17)",
- "AC-4(21)",
- "AC-4(22)",
- "AC-6",
- "AC-6(8)",
- "AC-6(9)",
- "AC-12",
- "AC-12(1)",
- "AC-20",
- "AC-20(1)",
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5(1)",
- "IA-5(2)",
- "IA-5(5)",
- "IA-5(8)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-8",
- "IA-8(1)",
- "IA-8(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.AC-6",
- "PR.AC-7",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03",
- "PR.AA-04",
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.3",
- "7.1.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.4",
- "7.2.3",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_aws_attached_policy_no_administrative_privileges",
- "iam_customer_attached_policy_no_administrative_privileges",
- "iam_inline_policy_no_administrative_privileges",
- "apigateway_restapi_authorizers_enabled",
- "apigatewayv2_api_authorizers_enabled",
- "awslambda_function_not_publicly_accessible",
- "awslambda_function_url_public",
- "cognito_user_pool_waf_acl_attached"
- ]
- },
- {
- "Id": "IPY-03",
- "Description": "Implement cryptographically secure and standardized network protocols for the management, import and export of data.",
- "Name": "Secure Interoperability and Portability Management",
- "Attributes": [
- {
- "Section": "Interoperability & Portability",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IPY-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.2",
- "NC1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1",
- "27001: A.15.1.1",
- "27002: 15.1.1",
- "27017: 15.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.19",
- "27001: A.5.23",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PT-2",
- "PT-2(2)",
- "SA-4",
- "SC-16",
- "SC-16(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.1",
- "1.2.5",
- "1.2.6",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "s3_bucket_secure_transport_policy"
- ]
- },
- {
- "Id": "IVS-02",
- "Description": "Plan and monitor the availability, quality, and adequate capacity of resources in order to deliver the required system performance as determined by the business.",
- "Name": "Capacity and Resource Planning",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-04"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.3",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.12.1.3",
- "27002: 12.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.3 (b)",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.8.6",
- "27001: A.8.14"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "SC-5",
- "SC-5(2)",
- "SC-4",
- "SI-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-04",
- "GV.OC-04"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "autoscaling_group_multiple_az",
- "autoscaling_group_multiple_instance_types"
- ]
- },
- {
- "Id": "IVS-03",
- "Description": "Monitor, encrypt and restrict communications between environments to only authenticated and authorized connections, as justified by the business. Review these configurations at least annually, and support them by a documented justification of all allowed services, protocols, ports, and compensating controls.",
- "Name": "Network Security",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-06"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.8",
- "3.1",
- "12.2",
- "13.6",
- "13.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: A.5.15 2nd c)",
- "27002: 8.20",
- "27002: 8.21",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-1",
- "SC-4",
- "SC-7",
- "SC-7(4)",
- "SC-7(5)",
- "SC-7(8)",
- "SC-7(9)",
- "SC-7(11)",
- "SC-8",
- "SC-8(1)",
- "SC-11",
- "SC-12",
- "SC-16",
- "SC-23",
- "SC-29",
- "SC-29(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-5",
- "PR.AC-7",
- "PR.PT-4",
- "DE.CM-1",
- "DE.CM-7",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-01",
- "PR.AA-03",
- "PR.AA-05",
- "DE.CM-01",
- "PR.DS-02",
- "ID.AM-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "1.1.6",
- "1.2",
- "1.2.3",
- "2.2",
- "4.1.1",
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.5",
- "1.2.6",
- "1.2.7",
- "1.4.2",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1",
- "10.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "vpc_flow_logs_enabled",
- "ec2_securitygroup_default_restrict_traffic",
- "ec2_securitygroup_allow_ingress_from_internet_to_all_ports",
- "ec2_securitygroup_allow_ingress_from_internet_to_any_port",
- "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
- "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_3389",
- "ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports",
- "ec2_networkacl_allow_ingress_any_port",
- "ec2_networkacl_allow_ingress_tcp_port_22",
- "ec2_networkacl_allow_ingress_tcp_port_3389",
- "ec2_securitygroup_allow_wide_open_public_ipv4",
- "vpc_peering_routing_tables_with_least_privilege",
- "vpc_subnet_no_public_ip_by_default"
- ]
- },
- {
- "Id": "IVS-04",
- "Description": "Harden host and guest OS, hypervisor or infrastructure control plane according to their respective best practices, and supported by technical controls, as part of a security baseline.",
- "Name": "OS Hardening and Base Controls",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.8",
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-07",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "4.1",
- "4.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.3",
- "SY1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.14.2.2",
- "27002: 14.2.2",
- "27001: A.14.2.3",
- "27001 A.14.2.4",
- "27018: 12.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: 8.20",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(1)",
- "SC-29",
- "SC-29(1)",
- "SC-2",
- "SC-7",
- "SC-7(12)",
- "SC-30",
- "SC-34",
- "SC-35",
- "SC-39",
- "SC-44"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-1",
- "PR.PT-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ec2_instance_imdsv2_enabled",
- "ec2_instance_account_imdsv2_enabled",
- "ec2_launch_template_imdsv2_required",
- "ec2_instance_managed_by_ssm",
- "ssm_managed_compliant_patching"
- ]
- },
- {
- "Id": "IVS-06",
- "Description": "Design, develop, deploy and configure applications and infrastructures such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented and segregated, monitored and restricted from other tenants.",
- "Name": "Segmentation and Segregation",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-09"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.3.4",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.20",
- "27001: A.8.3",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.22",
- "27002: 5.15 (b)",
- "27002: 8.3 (b)",
- "27002: 8.16 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-3",
- "SC-7",
- "SC-7(20)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.AC-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.6",
- "8.3.1",
- "10.8",
- "11.3",
- "A3.2.1",
- "A3.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A1.1.1",
- "A1.1.2",
- "A1.1.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ec2_securitygroup_default_restrict_traffic",
- "vpc_subnet_separate_private_public",
- "vpc_peering_routing_tables_with_least_privilege",
- "ec2_instance_public_ip",
- "awslambda_function_inside_vpc",
- "sagemaker_notebook_instance_vpc_settings_configured",
- "sagemaker_models_vpc_settings_configured",
- "sagemaker_training_jobs_vpc_settings_configured"
- ]
- },
- {
- "Id": "IVS-07",
- "Description": "Use secure and encrypted communication channels when migrating servers, services, applications, or data to cloud environments. Such channels must include only up-to-date and approved protocols.",
- "Name": "Migration to Cloud Environments",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-10"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM1.4",
- "NC1.4",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27017: 13.1.1",
- "27018: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27017: 13.1.2",
- "27018: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3",
- "27018: 13.1.3",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27017: 13.2.1",
- "27018: 13.2.1",
- "27001: A.13.2.2",
- "27002: 13.2.2",
- "27017: 13.2.2",
- "27018: 13.2.2",
- "27001: A.13.2.3",
- "27002: 13.2.3",
- "27017: 13.2.3",
- "27018: 13.2.3",
- "27001: A.13.2.4",
- "27002: 13.2.4",
- "27017: 13.2.4",
- "27018: 13.2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.20",
- "27001: A.8.24",
- "27002: 8.20 (e)",
- "27002: 8.24 Guidance (b,f), other information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-17",
- "AC-20",
- "SC-7",
- "SC-7(28)",
- "SC-8",
- "SC-8(1)",
- "SC-12",
- "SC-23",
- "SC-29",
- "SI-7",
- "SI-7(1)-(3)",
- "SI-7(5)-(10)",
- "SI-7(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "dms_endpoint_ssl_enabled"
- ]
- },
- {
- "Id": "IVS-09",
- "Description": "Define, implement and evaluate processes, procedures and defense-in-depth techniques for protection, detection, and timely response to network-based attacks.",
- "Name": "Network Defense",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.6",
- "CC6.8",
- "CC7.1",
- "CC7.2",
- "CC7.5"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-13"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "13.3",
- "13.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3",
- "5.2.4",
- "5.2.5",
- "5.2.7",
- "5.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.11.1.4",
- "27002: 11.1.4",
- "27017: 11.1.4",
- "27018: 16.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.5.24",
- "27001: A.5.26",
- "27001: A.8.8",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.26",
- "27002: 8.8 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-8",
- "PL-8(1)",
- "SC-5",
- "SC-5(1)",
- "SC-5(3)",
- "SC-7",
- "SC-7(13)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.DP-1",
- "DE.CM-1",
- "DE.CM-7",
- "PR.AC-5",
- "RS.MI-2",
- "PR.DS-2",
- "RS.RP-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "DE.CM-01",
- "PR.IR-01",
- "RS.MA-01",
- "RS.MI-01",
- "RS.MI-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.6",
- "1.1",
- "1.2",
- "1.3",
- "1.5",
- "12.10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.1.1",
- "1.3.1",
- "1.3.2",
- "1.3.3",
- "1.4.1",
- "1.4.2",
- "1.4.3",
- "1.4.4",
- "1.4.5",
- "1.5.1",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "networkfirewall_in_all_vpc",
- "networkfirewall_logging_enabled",
- "networkfirewall_policy_rule_group_associated",
- "wafv2_webacl_with_rules",
- "wafv2_webacl_logging_enabled",
- "elbv2_waf_acl_attached",
- "cloudfront_distributions_using_waf",
- "guardduty_is_enabled",
- "shield_advanced_protection_in_cloudfront_distributions",
- "shield_advanced_protection_in_internet_facing_load_balancers"
- ]
- },
- {
- "Id": "LOG-02",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the security and retention of audit logs.",
- "Name": "Audit Logs Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1",
- "8.9",
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.3",
- "5.1.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-4",
- "AU-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-08",
- "PR.DS-11",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.7"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4",
- "10.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_log_file_validation_enabled",
- "cloudtrail_kms_encryption_enabled",
- "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
- "cloudtrail_logs_s3_bucket_access_logging_enabled",
- "cloudtrail_bucket_requires_mfa_delete",
- "cloudwatch_log_group_kms_encryption_enabled",
- "cloudwatch_log_group_not_publicly_accessible",
- "s3_bucket_object_lock"
- ]
- },
- {
- "Id": "LOG-03",
- "Description": "Identify and monitor security-related events within applications and the underlying infrastructure. Define and implement a system to generate alerts to responsible stakeholders based on such events and corresponding metrics.",
- "Name": "Security Monitoring and Alerting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03",
- "SEF-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "5.2.7",
- "1.6.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2",
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-3",
- "DE.AE-5",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-4",
- "DE.CM-5",
- "DE.CM-6",
- "DE.CM-7",
- "DE.DP-1",
- "DE.DP-4",
- "DE.AE-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2",
- "10.4.1.1",
- "10.4.2.1",
- "10.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "guardduty_is_enabled",
- "securityhub_enabled",
- "cloudwatch_alarm_actions_enabled",
- "cloudwatch_alarm_actions_alarm_state_configured",
- "cloudwatch_log_metric_filter_unauthorized_api_calls",
- "cloudwatch_log_metric_filter_root_usage",
- "cloudwatch_log_metric_filter_sign_in_without_mfa"
- ]
- },
- {
- "Id": "LOG-04",
- "Description": "Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.",
- "Name": "Audit Logs Access and Accountability",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.1",
- "4.1.2",
- "4.1.3",
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27001: A.12.4.1",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(4)",
- "AU-9(6)",
- "AU-10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.1",
- "10.2.1",
- "10.2.3",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1.3",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
- "cloudwatch_log_group_not_publicly_accessible"
- ]
- },
- {
- "Id": "LOG-05",
- "Description": "Monitor security audit logs to detect activity outside of typical or expected patterns. Establish and follow a defined process to review and take appropriate and timely actions on detected anomalies.",
- "Name": "Audit Logs Monitoring and Response",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.8",
- "8.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "1.6.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.3",
- "27002: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-6",
- "AU-6(1)",
- "AU-6(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-3",
- "PR.PT-1",
- "RS.AN-1",
- "RS.CO-1.",
- "DE.AE-1",
- "DE.AE-5",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6",
- "10.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.1.1",
- "10.4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudwatch_log_metric_filter_unauthorized_api_calls",
- "cloudwatch_log_metric_filter_root_usage",
- "cloudwatch_log_metric_filter_sign_in_without_mfa",
- "cloudwatch_log_metric_filter_policy_changes",
- "cloudwatch_log_metric_filter_security_group_changes",
- "cloudwatch_changes_to_network_acls_alarm_configured",
- "cloudwatch_changes_to_network_gateways_alarm_configured",
- "cloudwatch_changes_to_network_route_tables_alarm_configured",
- "cloudwatch_changes_to_vpcs_alarm_configured",
- "cloudwatch_log_metric_filter_authentication_failures",
- "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk",
- "cloudwatch_log_metric_filter_for_s3_bucket_policy_changes",
- "cloudwatch_log_metric_filter_aws_organizations_changes",
- "guardduty_no_high_severity_findings"
- ]
- },
- {
- "Id": "LOG-07",
- "Description": "Establish, document and implement which information meta/data system events should be logged. Review and update the scope at least annually or whenever there is a change in the threat environment.",
- "Name": "Logging Scope",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-14",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.SC-4",
- "PR.PT-1",
- "ID.GV-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_bedrock_logging_enabled",
- "cloudtrail_multi_region_enabled",
- "cloudtrail_multi_region_enabled_logging_management_events",
- "cloudtrail_s3_dataevents_read_enabled",
- "cloudtrail_s3_dataevents_write_enabled",
- "vpc_flow_logs_enabled",
- "awslambda_function_invoke_api_operations_cloudtrail_logging_enabled"
- ]
- },
- {
- "Id": "LOG-08",
- "Description": "Generate audit records containing relevant security information.",
- "Name": "Log Records",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-3",
- "AU-3(1)",
- "AU-3(3)",
- "AU-6",
- "AU-6(8)",
- "AU-12",
- "AU-12(1)",
- "AU-12(2)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-6",
- "DE.CM-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_multi_region_enabled",
- "cloudtrail_cloudwatch_logging_enabled",
- "vpc_flow_logs_enabled",
- "s3_bucket_server_access_logging_enabled",
- "elb_logging_enabled",
- "elbv2_logging_enabled",
- "cloudfront_distributions_logging_enabled",
- "route53_public_hosted_zones_cloudwatch_logging_enabled",
- "wafv2_webacl_logging_enabled",
- "redshift_cluster_audit_logging",
- "rds_cluster_integration_cloudwatch_logs",
- "rds_instance_integration_cloudwatch_logs",
- "opensearch_service_domains_audit_logging_enabled",
- "eks_control_plane_logging_all_types_enabled",
- "apigateway_restapi_logging_enabled",
- "apigatewayv2_api_access_logging_enabled",
- "networkfirewall_logging_enabled",
- "mq_broker_logging_enabled",
- "documentdb_cluster_cloudwatch_log_export",
- "neptune_cluster_integration_cloudwatch_logs",
- "codebuild_project_logging_enabled",
- "glue_etl_jobs_logging_enabled",
- "stepfunctions_statemachine_logging_enabled",
- "datasync_task_logging_enabled",
- "ec2_client_vpn_endpoint_connection_logging_enabled",
- "elasticbeanstalk_environment_cloudwatch_logging_enabled"
- ]
- },
- {
- "Id": "LOG-09",
- "Description": "The information system protects audit records from unauthorized access, modification, and deletion.",
- "Name": "Log Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04",
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(2)",
- "AU-9(3)",
- "AU-9(4)",
- "AU-12(3)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_log_file_validation_enabled",
- "cloudtrail_kms_encryption_enabled",
- "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
- "cloudwatch_log_group_kms_encryption_enabled",
- "cloudwatch_log_group_not_publicly_accessible"
- ]
- },
- {
- "Id": "LOG-10",
- "Description": "Establish and maintain a monitoring and internal reporting capability over the operations of cryptographic, encryption and key management policies, processes, procedures, and controls.",
- "Name": "Encryption Monitoring and Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.1.1",
- "10.2.1",
- "10.4.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_cmk_rotation_enabled",
- "acm_certificates_expiration_check"
- ]
- },
- {
- "Id": "LOG-11",
- "Description": "Log and monitor key lifecycle management events to enable auditing and reporting on usage of cryptographic keys.",
- "Name": "Transaction/Activity Logging",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudtrail_s3_dataevents_read_enabled",
- "cloudtrail_s3_dataevents_write_enabled",
- "cloudtrail_multi_region_enabled_logging_management_events"
- ]
- },
- {
- "Id": "LOG-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the reporting of anomalies and failures of the monitoring system and provide immediate notification to the accountable party.",
- "Name": "Failures and Anomalies Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.16.1.2",
- "27017: 16.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.24",
- "27001: A.6.8",
- "27002: 6.8 (g)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-6",
- "AU-6(3)",
- "AU-6(4)",
- "AU-6(5)",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-3",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.3",
- "10.7.1",
- "10.7.2",
- "10.7.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "guardduty_is_enabled",
- "guardduty_no_high_severity_findings",
- "cloudwatch_alarm_actions_enabled",
- "cloudwatch_alarm_actions_alarm_state_configured"
- ]
- },
- {
- "Id": "SEF-03",
- "Description": "'Establish, document, approve, communicate, apply, evaluate and maintain a security incident response plan, which includes but is not limited to: relevant internal departments, impacted CSCs, and other business critical relationships (such as supply-chain) that may be impacted.'",
- "Name": "Incident Response Plans",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2",
- "CC7.3",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2",
- "17.4"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27017: CLD.12.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.5.26",
- "27002: 5.26 (e,f)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-1",
- "IR-2",
- "IR-2(1)-(3)",
- "IR-3",
- "IR-3(1)-(3)",
- "IR-4",
- "IR-4(1)-(15)",
- "IR-5",
- "IR-5(1)",
- "IR-6",
- "IR-6(1)-(3)",
- "IR-7",
- "IR-7(1)",
- "IR-7(2)",
- "IR-8",
- "IR-8(1)",
- "IR-9",
- "IR-9(1)-(4)",
- "PM-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.CO-1",
- "RS.CO-4",
- "ID.AM-6",
- "ID.GV-2",
- "ID.SC-5",
- "PR.IP-9",
- "PR.IP10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AT-01",
- "PR.AT-02",
- "RS.MA-01",
- "GV.SC-08",
- "ID.IM-02",
- "ID.IM-04",
- "RC.RP-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "12.10.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ssmincidents_enabled_with_plans"
- ]
- },
- {
- "Id": "SEF-06",
- "Description": "Define, implement and evaluate processes, procedures and technical measures supporting business processes to triage security-related events.",
- "Name": "Event Triage Processes",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.4",
- "27002: 16.1.4",
- "27017: 16.1.4",
- "27018: 16.1.4",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.25"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(3)",
- "CA-7(4)",
- "CA-7(5)",
- "CA-7(6)",
- "IR-4",
- "IR-4(1)",
- "IR-4(3)",
- "IR-4(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-4",
- "RS.RP-1",
- "RS.AN-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "RS.MA-02",
- "RS.MA-03",
- "RS.AN-03",
- "DE.AE-02",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "RS.MI-02",
- "RC.RP-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "guardduty_is_enabled",
- "securityhub_enabled"
- ]
- },
- {
- "Id": "SEF-08",
- "Description": "Maintain points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities.",
- "Name": "Points of Contact Maintenance",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.2",
- "27001: A.6.1.3",
- "27002: 6.1.3",
- "27017: 6.1.3",
- "27018: 6.1.3",
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.18.1.1",
- "27002: 18.1.1",
- "27017: 18.1.1",
- "27018: 18.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.5",
- "27001: A.5.24",
- "27002: 5.24 Incident management procedure (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-4",
- "IR-4(8)",
- "IR-6",
- "IR-6(3)",
- "IR-7",
- "IR-7(2)",
- "PM-21",
- "PM-23",
- "PM-26"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-2",
- "RS.CO-3",
- "RS.CO-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-02",
- "RS.CO-02",
- "RS.CO-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "account_maintain_current_contact_details",
- "account_security_contact_information_is_registered",
- "account_maintain_different_contact_details_to_security_billing_and_operations"
- ]
- },
- {
- "Id": "TVM-02",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually.",
- "Name": "Malware Protection Policy and Procedures",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.8"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-01",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "9.7",
- "10.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.2",
- "TS1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.12.2.1",
- "27001: A.6.2.1",
- "27002: 6.2.1 (h)",
- "27001: A.6.2.2",
- "27002: 6.2.2 (j)",
- "27001: A.7.2.2",
- "27002: 7.2.2 (d)",
- "27001: A.10.1.1",
- "27002: 10.1.1 (g)",
- "27001: A.13.2.1",
- "27002: 13.2.1 (b)",
- "27001: A.15.1.2",
- "27017: 15.1.2",
- "27001: A.12.2.1",
- "27002: 12.2.1 (a),(d)",
- "27017: CLD.9.5.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.7",
- "27001: A.5.37",
- "27001: A.8.7",
- "27002: 5.7 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-3",
- "RA-3(3)",
- "RA-5",
- "RA-5(3)",
- "RA-5(5)",
- "SI-3",
- "SI-3(4)",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "DE.CM-4",
- "DE.CM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "DE.CM-01",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.4",
- "12.1",
- "12.1.1",
- "12.3.1",
- "12.5.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.1.1",
- "12.1.2",
- "5.1.1",
- "5.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "guardduty_ec2_malware_protection_enabled"
- ]
- },
- {
- "Id": "TVM-03",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to enable both scheduled and emergency responses to vulnerability identifications, based on the identified risk.",
- "Name": "Vulnerability Remediation Schedule",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC7.1",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.2",
- "7.7",
- "17.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "TM2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.2.1",
- "27001: A.12.6.1",
- "27002: 12.6.1(c)(d)(j)",
- "27018: 12.6.1(k)(i)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.8.7",
- "27001: A.8.8",
- "27001: A.8.32",
- "27002: 8.7",
- "27002: 8.8",
- "27002: 8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-31",
- "RA-3",
- "RA-3(1)",
- "RA-5",
- "RA-5(2)-(4)",
- "RA-5(6)",
- "SI-3",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.AN-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.1.a",
- "6.1.b"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.1.1",
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ssm_managed_compliant_patching",
- "rds_instance_minor_version_upgrade_enabled",
- "rds_cluster_minor_version_upgrade_enabled",
- "redshift_cluster_automatic_upgrades",
- "elasticbeanstalk_environment_managed_updates_enabled",
- "dms_instance_minor_version_upgrade_enabled",
- "elasticache_redis_cluster_auto_minor_version_upgrades",
- "memorydb_cluster_auto_minor_version_upgrades",
- "mq_broker_auto_minor_version_upgrades",
- "opensearch_service_domains_updated_to_the_latest_service_software_version",
- "kafka_cluster_uses_latest_version"
- ]
- },
- {
- "Id": "TVM-04",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to update detection tools, threat signatures, and indicators of compromise on a weekly, or more frequent basis.",
- "Name": "Detection Updates",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.3",
- "TS1.4",
- "TM1.3",
- "TM1.4",
- "IM1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1.1",
- "27002: 5.1.1 (h)",
- "27001: A.12.6.1",
- "27002: 12.6.1 (b),(c)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1",
- "27001: A.8.8",
- "27001: A.8.15",
- "27001: A.8.16",
- "27002: 5.1",
- "27002: 5.37",
- "27002: 8.8",
- "27002: 8.15 (d)",
- "27002: 8.16 (d,e)",
- "27002: 8.31 2nd (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-7",
- "CM-7(4)",
- "RA-3",
- "RA-3(3)",
- "RA-5(2)",
- "SA-10",
- "SA-10(5)",
- "SA-11",
- "SA-11(2)",
- "SI-2",
- "SI-2(4)",
- "SI-3",
- "SI-3(4)",
- "SI-4",
- "SI-4(9)",
- "SI-4(24)",
- "SI-8",
- "SI-8(2)",
- "SI-8(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-02",
- "ID.RA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.2",
- "5.2a",
- "5.2b",
- "5.2c"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "5.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "guardduty_is_enabled",
- "inspector2_is_enabled"
- ]
- },
- {
- "Id": "TVM-05",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to identify updates for applications which use third party or open source libraries according to the organization's vulnerability management policy.",
- "Name": "External Library Vulnerabilities",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "SD2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.6.2",
- "27002: 12.6.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A 5.6",
- "27001: A.8.19",
- "27001: A.8.8",
- "27001: A.8.28",
- "27001: A.8.31",
- "27002: 5.6 (c)",
- "27001: 8.19",
- "27001: 8.8",
- "27001: 8.28",
- "27001: 8.31"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(3)",
- "SA-11",
- "SA-11(2)",
- "SA-11(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-03",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.2",
- "6.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "inspector2_is_enabled",
- "ecr_repositories_scan_vulnerabilities_in_latest_image",
- "ecr_registry_scan_images_on_push_enabled"
- ]
- },
- {
- "Id": "TVM-07",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the detection of vulnerabilities on organizationally managed assets at least monthly.",
- "Name": "Vulnerability Identification",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.1",
- "7.5",
- "7.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.6",
- "27001: A.12.6.1",
- "27002: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.8",
- "27002: 8.8"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(4)",
- "RA-5(5)",
- "SA-11",
- "SA-11(5)",
- "SA-15(5)",
- "SC-7",
- "SC-7(10)",
- "SI-3(8)",
- "SI-3(10)",
- "SI-7",
- "SI-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.RA-1",
- "DE.CM-8",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "11.2",
- "11.2.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "11.3.2",
- "11.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "inspector2_is_enabled",
- "inspector2_active_findings_exist",
- "guardduty_is_enabled",
- "ecr_repositories_scan_vulnerabilities_in_latest_image"
- ]
- },
- {
- "Id": "UEM-08",
- "Description": "Protect information from unauthorized disclosure on managed endpoint devices with storage encryption.",
- "Name": "Storage Encryption",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "MOS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "3.1.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "PA1.2",
- "PA1.3",
- "PA1.5",
- "PA2.2",
- "PM1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.11.2.7",
- "27002: 11.2.7",
- "27001: A.18.1.1",
- "27017: 18.1.1",
- "27001: A.12.3.1",
- "27017: 12.3.1",
- "27018: A.11.4",
- "27018: A.11.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.1",
- "27002: 8.1 (h)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.4",
- "3.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.5.1",
- "3.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "ec2_ebs_volume_encryption",
- "ec2_ebs_default_encryption",
- "workspaces_volume_encryption_enabled"
- ]
- },
- {
- "Id": "UEM-11",
- "Description": "Configure managed endpoints with Data Loss Prevention (DLP) technologies and rules in accordance with a risk assessment.",
- "Name": "Data Loss Prevention",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.5",
- "PA2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27002: 12.3",
- "27001: A.8.3.1",
- "27002: 8.3.1",
- "27001: A.12.2",
- "27002: 12.2",
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001: A.6.1.1",
- "27017: 6.1.1",
- "27018: 12.3.1",
- "27018: 10.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-7",
- "SC-7(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.DS-10",
- "PR.PS-01",
- "ID.AM-08",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A3.2.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A3.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "macie_is_enabled",
- "macie_automated_sensitive_data_discovery_enabled"
- ]
- }
- ]
-}
diff --git a/prowler/compliance/aws/ens_rd2022_aws.json b/prowler/compliance/aws/ens_rd2022_aws.json
index 8548e59a89..f81b8a3eea 100644
--- a/prowler/compliance/aws/ens_rd2022_aws.json
+++ b/prowler/compliance/aws/ens_rd2022_aws.json
@@ -598,6 +598,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -624,6 +632,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -755,6 +771,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -781,6 +805,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -913,6 +945,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -940,6 +980,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -966,6 +1014,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1743,6 +1799,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1821,6 +1885,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1873,6 +1945,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1925,6 +2005,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1951,6 +2039,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1977,6 +2073,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2003,6 +2107,14 @@
],
"Checks": [
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2056,6 +2168,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2082,6 +2202,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2366,7 +2494,11 @@
}
],
"Checks": [
- "elbv2_insecure_ssl_ciphers"
+ "elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled"
]
},
{
@@ -2389,7 +2521,11 @@
}
],
"Checks": [
- "elbv2_insecure_ssl_ciphers"
+ "elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled"
]
},
{
@@ -2539,8 +2675,7 @@
}
],
"Checks": [
- "vpc_subnet_separate_private_public",
- "vpc_different_regions"
+ "vpc_subnet_separate_private_public"
]
},
{
@@ -2593,8 +2728,8 @@
}
],
"Checks": [
- "vpc_subnet_different_az",
- "vpc_different_regions"
+ "vpc_different_regions",
+ "vpc_subnet_different_az"
]
},
{
@@ -4262,6 +4397,29 @@
],
"Checks": []
},
+ {
+ "Id": "op.cont.2.aws.vpc.1",
+ "Description": "Plan de continuidad",
+ "Attributes": [
+ {
+ "IdGrupoControl": "op.cont.2",
+ "Marco": "operacional",
+ "Categoria": "continuidad del servicio",
+ "DescripcionControl": "Distribución de las VPCs entre múltiples regiones y zonas de disponibilidad de AWS para garantizar la continuidad del servicio ante fallos regionales o zonales.",
+ "Nivel": "alto",
+ "Tipo": "requisito",
+ "Dimensiones": [
+ "disponibilidad"
+ ],
+ "ModoEjecucion": "automático",
+ "Dependencias": []
+ }
+ ],
+ "Checks": [
+ "vpc_different_regions",
+ "vpc_subnet_different_az"
+ ]
+ },
{
"Id": "op.cont.3.aws.drs.1",
"Description": "Pruebas periódicas",
@@ -4282,6 +4440,14 @@
],
"Checks": [
"drs_job_exist"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/fedramp_20x_ksi_low_aws.json b/prowler/compliance/aws/fedramp_20x_ksi_low_aws.json
index 6c6c500582..15763ef48e 100644
--- a/prowler/compliance/aws/fedramp_20x_ksi_low_aws.json
+++ b/prowler/compliance/aws/fedramp_20x_ksi_low_aws.json
@@ -37,6 +37,14 @@
"ssm_managed_compliant_patching",
"ssm_managed_instance_compliance_association_compliant",
"ssm_managed_instance_compliance_patch_compliant"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -146,6 +154,20 @@
"inspector2_active_findings_exist",
"securityhub_enabled",
"sns_topics_kms_encryption_at_rest_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -205,6 +227,14 @@
"resourceexplorer_indexes_found",
"ssm_managed_instance_compliance_association_compliant",
"trustedadvisor_premium_support_plan_subscribed"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -349,6 +379,14 @@
"config_recorder_all_regions_enabled",
"inspector2_is_enabled",
"resourceexplorer_indexes_found"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
}
]
diff --git a/prowler/compliance/aws/fedramp_low_revision_4_aws.json b/prowler/compliance/aws/fedramp_low_revision_4_aws.json
index 9824798552..059de69675 100644
--- a/prowler/compliance/aws/fedramp_low_revision_4_aws.json
+++ b/prowler/compliance/aws/fedramp_low_revision_4_aws.json
@@ -46,6 +46,20 @@
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -115,6 +129,20 @@
"ec2_networkacl_allow_ingress_any_port",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
"ec2_networkacl_allow_ingress_any_port"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -173,6 +201,14 @@
],
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 90
+ }
]
},
{
@@ -198,6 +234,20 @@
"rds_instance_enhanced_monitoring_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -251,6 +301,14 @@
"guardduty_is_enabled",
"ssm_managed_compliant_patching",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -336,6 +394,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -373,6 +445,14 @@
"rds_instance_multi_az",
"redshift_cluster_automated_snapshot",
"s3_bucket_object_versioning"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/fedramp_moderate_revision_4_aws.json b/prowler/compliance/aws/fedramp_moderate_revision_4_aws.json
index c914a58b2c..13c4624572 100644
--- a/prowler/compliance/aws/fedramp_moderate_revision_4_aws.json
+++ b/prowler/compliance/aws/fedramp_moderate_revision_4_aws.json
@@ -36,6 +36,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -65,6 +79,20 @@
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -82,6 +110,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -140,6 +182,20 @@
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -191,6 +247,38 @@
"iam_user_access_not_stale_to_sagemaker",
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_role_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_sagemaker",
+ "ConfigKey": "max_unused_sagemaker_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -371,6 +459,20 @@
"ec2_networkacl_allow_ingress_any_port",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
"ec2_networkacl_allow_ingress_any_port"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -507,6 +609,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -575,6 +691,14 @@
],
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 90
+ }
]
},
{
@@ -631,6 +755,20 @@
"rds_instance_enhanced_monitoring_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -720,6 +858,14 @@
"guardduty_is_enabled",
"ssm_managed_compliant_patching",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -887,6 +1033,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -909,6 +1069,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -927,6 +1101,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -945,6 +1133,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -961,6 +1163,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -995,6 +1205,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1061,6 +1285,14 @@
"guardduty_is_enabled",
"rds_instance_multi_az",
"s3_bucket_object_versioning"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1145,6 +1377,10 @@
"Checks": [
"apigateway_restapi_client_certificate_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"opensearch_service_domains_node_to_node_encryption_enabled",
"s3_bucket_secure_transport_policy"
@@ -1164,6 +1400,10 @@
"Checks": [
"apigateway_restapi_client_certificate_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"opensearch_service_domains_node_to_node_encryption_enabled",
"s3_bucket_secure_transport_policy"
@@ -1279,6 +1519,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1301,6 +1549,20 @@
"guardduty_is_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1328,6 +1590,20 @@
"guardduty_is_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1355,6 +1631,20 @@
"guardduty_is_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1382,6 +1672,20 @@
"guardduty_is_enabled",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1408,6 +1712,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/ffiec_aws.json b/prowler/compliance/aws/ffiec_aws.json
index 23ab8953b6..4a2a1b943e 100644
--- a/prowler/compliance/aws/ffiec_aws.json
+++ b/prowler/compliance/aws/ffiec_aws.json
@@ -37,6 +37,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -74,6 +82,20 @@
"cloudtrail_cloudwatch_logging_enabled",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -148,6 +170,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -166,6 +202,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -183,6 +233,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -237,6 +301,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -254,6 +332,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -367,6 +459,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -386,6 +486,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -404,6 +518,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -487,6 +615,10 @@
"Checks": [
"apigateway_restapi_client_certificate_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"s3_bucket_secure_transport_policy"
]
@@ -823,6 +955,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -868,6 +1014,20 @@
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/gdpr_aws.json b/prowler/compliance/aws/gdpr_aws.json
index 930af1db58..a97a11e3dc 100644
--- a/prowler/compliance/aws/gdpr_aws.json
+++ b/prowler/compliance/aws/gdpr_aws.json
@@ -59,6 +59,14 @@
"cloudwatch_log_metric_filter_security_group_changes",
"cloudwatch_log_metric_filter_unauthorized_api_calls",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -85,6 +93,14 @@
"kms_cmk_rotation_enabled",
"redshift_cluster_audit_logging",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/gxp_21_cfr_part_11_aws.json b/prowler/compliance/aws/gxp_21_cfr_part_11_aws.json
index 39534c4fdc..76ad0c74a5 100644
--- a/prowler/compliance/aws/gxp_21_cfr_part_11_aws.json
+++ b/prowler/compliance/aws/gxp_21_cfr_part_11_aws.json
@@ -266,6 +266,10 @@
"ec2_ebs_default_encryption",
"efs_encryption_at_rest_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"opensearch_service_domains_encryption_at_rest_enabled",
"opensearch_service_domains_node_to_node_encryption_enabled",
@@ -347,6 +351,20 @@
"cloudtrail_cloudwatch_logging_enabled",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
}
]
diff --git a/prowler/compliance/aws/gxp_eu_annex_11_aws.json b/prowler/compliance/aws/gxp_eu_annex_11_aws.json
index 1ceb3f817b..fdca6d1747 100644
--- a/prowler/compliance/aws/gxp_eu_annex_11_aws.json
+++ b/prowler/compliance/aws/gxp_eu_annex_11_aws.json
@@ -19,6 +19,14 @@
"Checks": [
"cloudtrail_multi_region_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -146,6 +154,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -238,6 +254,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -253,6 +277,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/hipaa_aws.json b/prowler/compliance/aws/hipaa_aws.json
index 036489d712..9eb243e6cc 100644
--- a/prowler/compliance/aws/hipaa_aws.json
+++ b/prowler/compliance/aws/hipaa_aws.json
@@ -19,6 +19,20 @@
"Checks": [
"config_recorder_all_regions_enabled",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -102,6 +116,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -161,6 +189,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -328,6 +370,20 @@
"guardduty_is_enabled",
"cloudwatch_log_metric_filter_authentication_failures",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -373,6 +429,20 @@
"cloudwatch_log_metric_filter_authentication_failures",
"cloudwatch_log_metric_filter_root_usage",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -402,6 +472,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -514,6 +598,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -649,6 +747,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -756,6 +868,20 @@
"s3_bucket_secure_transport_policy",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/iso27001_2013_aws.json b/prowler/compliance/aws/iso27001_2013_aws.json
index ad31ea0af4..c7ce030024 100644
--- a/prowler/compliance/aws/iso27001_2013_aws.json
+++ b/prowler/compliance/aws/iso27001_2013_aws.json
@@ -35,7 +35,11 @@
],
"Checks": [
"elb_insecure_ssl_ciphers",
- "elbv2_insecure_ssl_ciphers"
+ "elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled"
]
},
{
@@ -308,6 +312,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -872,6 +884,38 @@
"iam_user_access_not_stale_to_sagemaker",
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_role_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_sagemaker",
+ "ConfigKey": "max_unused_sagemaker_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -1049,6 +1093,20 @@
"Checks": [
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -1258,6 +1316,20 @@
"Checks": [
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
diff --git a/prowler/compliance/aws/iso27001_2022_aws.json b/prowler/compliance/aws/iso27001_2022_aws.json
index d47bfcf1d1..563b856317 100644
--- a/prowler/compliance/aws/iso27001_2022_aws.json
+++ b/prowler/compliance/aws/iso27001_2022_aws.json
@@ -20,6 +20,14 @@
"Checks": [
"securityhub_enabled",
"wellarchitected_workload_no_high_or_medium_risks"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -277,6 +285,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -331,6 +347,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -362,6 +386,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -378,6 +410,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -424,6 +464,14 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"guardduty_centrally_managed"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -472,6 +520,14 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"guardduty_centrally_managed"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -490,6 +546,14 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"guardduty_centrally_managed"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1004,6 +1068,14 @@
"organizations_account_part_of_organizations",
"accessanalyzer_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1080,6 +1152,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1111,6 +1191,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1749,6 +1837,14 @@
"vpc_default_security_group_closed",
"vpc_flow_logs_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/kisa_isms_p_2023_aws.json b/prowler/compliance/aws/kisa_isms_p_2023_aws.json
index d172e615dd..65a6e8c8b8 100644
--- a/prowler/compliance/aws/kisa_isms_p_2023_aws.json
+++ b/prowler/compliance/aws/kisa_isms_p_2023_aws.json
@@ -1211,6 +1211,14 @@
"rds_instance_default_admin",
"redshift_cluster_non_default_database_name"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -1416,6 +1424,14 @@
"iam_user_administrator_access_policy",
"organizations_delegated_administrators"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -1486,6 +1502,14 @@
"ssm_documents_set_as_public",
"vpc_endpoint_services_allowed_principals_trust_boundaries"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -2040,6 +2064,10 @@
"elb_ssl_listeners",
"elb_ssl_listeners_use_acm_certificate",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_nlb_tls_termination_enabled",
"elbv2_ssl_listeners",
"glue_data_catalogs_connection_passwords_encryption_enabled",
@@ -2079,6 +2107,17 @@
"transfer_server_in_transit_encryption_enabled",
"workspaces_volume_encryption_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -2816,6 +2855,20 @@
"wafv2_webacl_rule_logging_enabled",
"wafv2_webacl_with_rules"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -3090,6 +3143,10 @@
"elb_ssl_listeners_use_acm_certificate",
"elbv2_desync_mitigation_mode",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_internet_facing",
"elbv2_listeners_underneath",
"elbv2_logging_enabled",
@@ -3313,6 +3370,47 @@
"workspaces_volume_encryption_enabled",
"workspaces_vpc_2private_1public_subnets_nat"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -3705,6 +3803,14 @@
"s3_bucket_event_notifications_enabled",
"trustedadvisor_errors_and_warnings"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -3823,6 +3929,14 @@
"s3_bucket_object_lock",
"s3_bucket_object_versioning"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
@@ -3860,6 +3974,14 @@
"Checks": [
"drs_job_exist"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. Control Measures Requirements",
diff --git a/prowler/compliance/aws/kisa_isms_p_2023_korean_aws.json b/prowler/compliance/aws/kisa_isms_p_2023_korean_aws.json
index 1748d96442..b99a36d38e 100644
--- a/prowler/compliance/aws/kisa_isms_p_2023_korean_aws.json
+++ b/prowler/compliance/aws/kisa_isms_p_2023_korean_aws.json
@@ -1211,6 +1211,14 @@
"rds_instance_default_admin",
"redshift_cluster_non_default_database_name"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -1416,6 +1424,14 @@
"iam_user_administrator_access_policy",
"organizations_delegated_administrators"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -1485,6 +1501,14 @@
"ssm_documents_set_as_public",
"vpc_endpoint_services_allowed_principals_trust_boundaries"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -2042,6 +2066,10 @@
"elb_ssl_listeners",
"elb_ssl_listeners_use_acm_certificate",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_nlb_tls_termination_enabled",
"elbv2_ssl_listeners",
"glue_data_catalogs_connection_passwords_encryption_enabled",
@@ -2081,6 +2109,17 @@
"transfer_server_in_transit_encryption_enabled",
"workspaces_volume_encryption_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -2819,6 +2858,20 @@
"wafv2_webacl_rule_logging_enabled",
"wafv2_webacl_with_rules"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -3093,6 +3146,10 @@
"elb_ssl_listeners_use_acm_certificate",
"elbv2_desync_mitigation_mode",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elbv2_internet_facing",
"elbv2_listeners_underneath",
"elbv2_logging_enabled",
@@ -3316,6 +3373,47 @@
"workspaces_volume_encryption_enabled",
"workspaces_vpc_2private_1public_subnets_nat"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -3708,6 +3806,14 @@
"s3_bucket_event_notifications_enabled",
"trustedadvisor_errors_and_warnings"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -3826,6 +3932,14 @@
"s3_bucket_object_lock",
"s3_bucket_object_versioning"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
@@ -3863,6 +3977,14 @@
"Checks": [
"drs_job_exist"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Domain": "2. 보호대책 요구사항",
diff --git a/prowler/compliance/aws/mitre_attack_aws.json b/prowler/compliance/aws/mitre_attack_aws.json
index 3d1d5fd378..3ac8cf0432 100644
--- a/prowler/compliance/aws/mitre_attack_aws.json
+++ b/prowler/compliance/aws/mitre_attack_aws.json
@@ -35,6 +35,32 @@
"awslambda_function_not_publicly_accessible",
"ec2_instance_public_ip"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudEndure Disaster Recovery",
@@ -200,6 +226,26 @@
"organizations_scp_check_deny_regions",
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "Amazon GuardDuty",
@@ -348,6 +394,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -393,6 +447,26 @@
"guardduty_is_enabled",
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -444,6 +518,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -557,6 +639,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -634,6 +724,26 @@
"inspector2_is_enabled",
"inspector2_active_findings_exist"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -821,6 +931,26 @@
"inspector2_is_enabled",
"inspector2_active_findings_exist"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -984,6 +1114,14 @@
"cloudfront_distributions_https_enabled",
"s3_bucket_secure_transport_policy"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudWatch",
@@ -1057,6 +1195,14 @@
"ssm_document_secrets",
"secretsmanager_automatic_rotation_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudHSM",
@@ -1143,6 +1289,14 @@
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_sql_server_1433_1434",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_telnet_23"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Network Firewall",
@@ -1218,6 +1372,14 @@
"s3_bucket_default_encryption",
"rds_instance_storage_encrypted"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -1264,6 +1426,20 @@
"securityhub_enabled",
"macie_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -1441,6 +1617,20 @@
"s3_bucket_object_versioning",
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudEndure Disaster Recovery",
@@ -1518,6 +1708,20 @@
"efs_have_backup_enabled",
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudEndure Disaster Recovery",
@@ -1566,6 +1770,20 @@
"drs_job_exist",
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudEndure Disaster Recovery",
@@ -1639,6 +1857,14 @@
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_sql_server_1433_1434",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_telnet_23"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Shield",
@@ -1686,6 +1912,14 @@
"drs_job_exist",
"rds_instance_backup_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudEndure Disaster Recovery",
@@ -1743,6 +1977,20 @@
"cloudwatch_log_metric_filter_sign_in_without_mfa",
"cloudwatch_log_metric_filter_unauthorized_api_calls"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS CloudWatch",
@@ -1819,6 +2067,20 @@
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_sql_server_1433_1434",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_telnet_23"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Config",
@@ -1910,6 +2172,20 @@
"iam_policy_no_full_access_to_cloudtrail",
"iam_policy_no_full_access_to_kms"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS Organizations",
@@ -1993,6 +2269,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "Amazon GuardDuty",
@@ -2071,6 +2355,14 @@
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_sql_server_1433_1434",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_telnet_23"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"AWSService": "AWS IoT Device Defender",
diff --git a/prowler/compliance/aws/nis2_aws.json b/prowler/compliance/aws/nis2_aws.json
index d7f193c6c0..3a4d567d25 100644
--- a/prowler/compliance/aws/nis2_aws.json
+++ b/prowler/compliance/aws/nis2_aws.json
@@ -597,6 +597,14 @@
"accessanalyzer_enabled",
"cloudwatch_log_metric_filter_root_usage"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "3 INCIDENT HANDLING (ARTICLE 21(2), POINT (B), OF DIRECTIVE (EU) 2022/2555)",
@@ -1511,6 +1519,17 @@
"Checks": [
"acm_certificates_with_secure_key_algorithms"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "9 CRYPTOGRAPHY (ARTICLE 21(2), POINT (H), OF DIRECTIVE (EU) 2022/2555)",
@@ -1528,6 +1547,17 @@
"route53_domains_privacy_protection_enabled",
"iam_no_expired_server_certificates_stored"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "9 CRYPTOGRAPHY (ARTICLE 21(2), POINT (H), OF DIRECTIVE (EU) 2022/2555)",
@@ -1645,6 +1675,14 @@
"efs_access_point_enforce_user_identity",
"efs_not_publicly_accessible"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "11 ACCESS CONTROL (ARTICLE 21(2), POINTS (I) AND (J), OF DIRECTIVE (EU) 2022/2555)",
@@ -1676,6 +1714,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "11 ACCESS CONTROL (ARTICLE 21(2), POINTS (I) AND (J), OF DIRECTIVE (EU) 2022/2555)",
@@ -1726,6 +1772,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "11 ACCESS CONTROL (ARTICLE 21(2), POINTS (I) AND (J), OF DIRECTIVE (EU) 2022/2555)",
diff --git a/prowler/compliance/aws/nist_800_171_revision_2_aws.json b/prowler/compliance/aws/nist_800_171_revision_2_aws.json
index 8e28ee383d..31c45c6ae3 100644
--- a/prowler/compliance/aws/nist_800_171_revision_2_aws.json
+++ b/prowler/compliance/aws/nist_800_171_revision_2_aws.json
@@ -230,6 +230,20 @@
"rds_instance_integration_cloudwatch_logs",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -321,6 +335,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -344,6 +372,14 @@
"guardduty_is_enabled",
"rds_instance_integration_cloudwatch_logs",
"s3_bucket_server_access_logging_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -383,6 +419,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -400,6 +450,20 @@
"cloudtrail_cloudwatch_logging_enabled",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -653,6 +717,10 @@
"apigateway_restapi_client_certificate_enabled",
"ec2_ebs_volume_encryption",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"opensearch_service_domains_node_to_node_encryption_enabled",
"s3_bucket_default_encryption",
"s3_bucket_secure_transport_policy"
@@ -684,6 +752,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -712,6 +794,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -729,6 +825,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -746,6 +856,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -769,6 +893,20 @@
"guardduty_is_enabled",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -806,6 +944,20 @@
"ec2_networkacl_allow_ingress_any_port",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
"ec2_networkacl_allow_ingress_any_port"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1025,6 +1177,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1044,6 +1210,20 @@
"securityhub_enabled",
"ssm_managed_compliant_patching",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1061,6 +1241,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1076,6 +1270,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1102,6 +1304,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1128,6 +1344,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
}
]
diff --git a/prowler/compliance/aws/nist_800_53_revision_4_aws.json b/prowler/compliance/aws/nist_800_53_revision_4_aws.json
index deb2a3cc25..8bd36a3910 100644
--- a/prowler/compliance/aws/nist_800_53_revision_4_aws.json
+++ b/prowler/compliance/aws/nist_800_53_revision_4_aws.json
@@ -27,6 +27,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -47,6 +61,38 @@
"iam_user_access_not_stale_to_sagemaker",
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_role_access_not_stale_to_bedrock",
+ "ConfigKey": "max_unused_bedrock_access_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_user_access_not_stale_to_sagemaker",
+ "ConfigKey": "max_unused_sagemaker_access_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
@@ -73,6 +119,20 @@
"rds_instance_integration_cloudwatch_logs",
"redshift_cluster_audit_logging",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -90,6 +150,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -125,6 +199,20 @@
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -270,6 +358,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -399,6 +501,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -421,6 +537,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -534,6 +664,20 @@
"guardduty_is_enabled",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -827,6 +971,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -860,6 +1012,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1110,6 +1276,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1133,6 +1307,20 @@
"ec2_instance_imdsv2_enabled",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1155,6 +1343,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1177,6 +1379,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1194,6 +1410,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1218,6 +1448,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/nist_800_53_revision_5_aws.json b/prowler/compliance/aws/nist_800_53_revision_5_aws.json
index 858df01fd9..70864860bf 100644
--- a/prowler/compliance/aws/nist_800_53_revision_5_aws.json
+++ b/prowler/compliance/aws/nist_800_53_revision_5_aws.json
@@ -220,6 +220,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -944,6 +952,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1629,6 +1645,14 @@
"Checks": [
"cloudtrail_multi_region_enabled",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1828,6 +1852,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1906,6 +1944,20 @@
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2290,6 +2342,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2352,6 +2418,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2387,6 +2467,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2466,6 +2560,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2487,6 +2595,20 @@
"guardduty_is_enabled",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2522,6 +2644,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -2904,6 +3040,14 @@
"guardduty_is_enabled",
"ssm_managed_compliant_patching",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4079,6 +4223,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4095,6 +4247,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4149,6 +4309,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4184,6 +4358,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4199,6 +4387,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4270,6 +4466,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4286,6 +4496,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4303,6 +4521,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4320,6 +4546,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4336,6 +4570,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4353,6 +4595,14 @@
"Checks": [
"guardduty_is_enabled",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4369,6 +4619,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4385,6 +4643,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4401,6 +4667,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4418,6 +4692,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4435,6 +4717,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4516,6 +4806,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4558,6 +4856,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4575,6 +4881,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4591,6 +4905,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -4607,6 +4929,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5262,6 +5592,10 @@
"Checks": [
"apigateway_restapi_client_certificate_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"opensearch_service_domains_node_to_node_encryption_enabled",
"s3_bucket_secure_transport_policy"
@@ -5549,6 +5883,9 @@
],
"Checks": [
"elbv2_insecure_ssl_ciphers",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners"
]
},
@@ -5677,6 +6014,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5844,6 +6189,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5884,6 +6237,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5901,6 +6262,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5918,6 +6287,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5934,6 +6311,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5950,6 +6335,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -5982,6 +6375,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6006,6 +6407,14 @@
"rds_instance_integration_cloudwatch_logs",
"redshift_cluster_audit_logging",
"s3_bucket_server_access_logging_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6022,6 +6431,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6039,6 +6456,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6056,6 +6481,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6072,6 +6505,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6108,6 +6549,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6124,6 +6573,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6191,6 +6648,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6207,6 +6672,14 @@
],
"Checks": [
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6227,6 +6700,14 @@
"cloudwatch_changes_to_network_route_tables_alarm_configured",
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -6247,6 +6728,14 @@
"cloudwatch_changes_to_network_route_tables_alarm_configured",
"cloudwatch_changes_to_vpcs_alarm_configured",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/nist_csf_1.1_aws.json b/prowler/compliance/aws/nist_csf_1.1_aws.json
index a55097e70c..9921efce56 100644
--- a/prowler/compliance/aws/nist_csf_1.1_aws.json
+++ b/prowler/compliance/aws/nist_csf_1.1_aws.json
@@ -48,6 +48,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -99,6 +113,20 @@
"guardduty_no_high_severity_findings",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -144,6 +172,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -179,6 +221,26 @@
"cloudwatch_log_metric_filter_unauthorized_api_calls",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -201,6 +263,20 @@
"guardduty_is_enabled",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -218,6 +294,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -243,6 +333,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -265,6 +369,20 @@
"guardduty_is_enabled",
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -291,6 +409,20 @@
"s3_bucket_server_access_logging_enabled",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -316,6 +448,20 @@
"guardduty_is_enabled",
"guardduty_no_high_severity_findings",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -349,6 +495,14 @@
"Checks": [
"config_recorder_all_regions_enabled",
"ec2_instance_managed_by_ssm"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -454,6 +608,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -471,6 +639,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -488,6 +670,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -523,6 +719,26 @@
"cloudwatch_log_metric_filter_unauthorized_api_calls",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -554,6 +770,26 @@
"cloudwatch_log_metric_filter_unauthorized_api_calls",
"rds_instance_enhanced_monitoring_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -827,6 +1063,20 @@
"sagemaker_notebook_instance_without_direct_internet_access_configured",
"securityhub_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -881,6 +1131,14 @@
"Checks": [
"ec2_instance_managed_by_ssm",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1035,6 +1293,14 @@
"ec2_instance_managed_by_ssm",
"ssm_managed_compliant_patching",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/nist_csf_2.0_aws.json b/prowler/compliance/aws/nist_csf_2.0_aws.json
index e890b08573..c06eeec11d 100644
--- a/prowler/compliance/aws/nist_csf_2.0_aws.json
+++ b/prowler/compliance/aws/nist_csf_2.0_aws.json
@@ -72,6 +72,20 @@
"securityhub_enabled",
"wellarchitected_workload_no_high_or_medium_risks",
"servicecatalog_portfolio_shared_within_organization_only"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -322,6 +336,26 @@
"wellarchitected_workload_no_high_or_medium_risks",
"organizations_delegated_administrators",
"organizations_tags_policies_enabled_and_attached"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -352,6 +386,26 @@
"vpc_flow_logs_enabled",
"iam_root_mfa_enabled",
"iam_root_credentials_management_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -408,6 +462,20 @@
"accessanalyzer_enabled",
"guardduty_no_high_severity_findings",
"trustedadvisor_errors_and_warnings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -442,6 +510,26 @@
"organizations_scp_check_deny_regions",
"organizations_tags_policies_enabled_and_attached",
"organizations_delegated_administrators"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -574,6 +662,14 @@
"opensearch_service_domains_encryption_at_rest_enabled",
"redshift_cluster_encrypted_at_rest",
"sns_topics_kms_encryption_at_rest_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -610,6 +706,17 @@
"iam_inline_policy_allows_privilege_escalation",
"ssm_documents_set_as_public",
"s3_bucket_shadow_resource_vulnerability"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -726,6 +833,14 @@
"iam_role_administratoraccess_policy",
"iam_policy_no_full_access_to_cloudtrail",
"iam_policy_no_full_access_to_kms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -853,6 +968,14 @@
"iam_customer_unattached_policy_no_administrative_privileges",
"accessanalyzer_enabled",
"cognito_user_pool_password_policy_symbol"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1224,6 +1347,14 @@
"inspector2_active_findings_exist",
"secretsmanager_automatic_rotation_enabled",
"secretsmanager_secret_rotated_periodically"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1265,6 +1396,14 @@
"Checks": [
"ssmincidents_enabled_with_plans",
"drs_job_exist"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "drs_job_exist",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1283,6 +1422,14 @@
"inspector2_is_enabled",
"guardduty_is_enabled",
"inspector2_active_findings_exist"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1329,6 +1476,14 @@
"vpc_flow_logs_enabled",
"config_recorder_all_regions_enabled",
"config_recorder_using_aws_service_role"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1540,6 +1695,14 @@
"guardduty_is_enabled",
"inspector2_is_enabled",
"accessanalyzer_enabled_without_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1662,6 +1825,14 @@
"guardduty_rds_protection_enabled",
"guardduty_lambda_protection_enabled",
"guardduty_eks_runtime_monitoring_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/pci_3.2.1_aws.json b/prowler/compliance/aws/pci_3.2.1_aws.json
index c240548f6a..ca8e968bf9 100644
--- a/prowler/compliance/aws/pci_3.2.1_aws.json
+++ b/prowler/compliance/aws/pci_3.2.1_aws.json
@@ -628,6 +628,14 @@
"ssm_managed_compliant_patching",
"ec2_elastic_ip_unassigned"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "2.4",
@@ -643,6 +651,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "2.4.a",
@@ -2413,6 +2429,14 @@
"cloudtrail_log_file_validation_enabled",
"s3_bucket_cross_region_replication"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "10.5",
@@ -2430,6 +2454,14 @@
"s3_bucket_object_versioning",
"cloudtrail_log_file_validation_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "10.5.2",
@@ -2616,6 +2648,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.4",
@@ -2631,6 +2671,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.4.a",
@@ -2646,6 +2694,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.4.b",
@@ -2661,6 +2717,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.4.c",
@@ -2676,6 +2740,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.5",
@@ -2691,6 +2763,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.5.a",
@@ -2706,6 +2786,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"ItemId": "11.5.b",
diff --git a/prowler/compliance/aws/pci_4.0_aws.json b/prowler/compliance/aws/pci_4.0_aws.json
index dc8fab9140..e21b543556 100644
--- a/prowler/compliance/aws/pci_4.0_aws.json
+++ b/prowler/compliance/aws/pci_4.0_aws.json
@@ -4403,6 +4403,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. ",
@@ -9281,6 +9289,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity. ",
@@ -9363,6 +9379,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.4.1: Audit logs are reviewed to identify anomalies or suspicious activity. ",
@@ -9459,6 +9483,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.4.2: Audit logs are reviewed to identify anomalies or suspicious activity. ",
@@ -9551,6 +9583,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "10.5.1: Audit log history is retained and available for analysis. ",
@@ -10179,6 +10219,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.6.3: Time-synchronization mechanisms support consistent time settings across all systems. ",
@@ -10343,6 +10391,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.7.1: Failures of critical security control systems are detected, reported, and responded to promptly. ",
@@ -10451,6 +10507,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "10.7.2: Failures of critical security control systems are detected, reported, and responded to promptly. ",
@@ -10625,6 +10689,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "11.5.1.1: Network intrusions and unexpected file changes are detected and responded to. ",
@@ -10653,6 +10725,14 @@
"Checks": [
"guardduty_is_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "11.5.1: Network intrusions and unexpected file changes are detected and responded to. ",
@@ -11445,6 +11525,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.2.1: Storage of account data is kept to a minimum. ",
@@ -11567,6 +11655,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.1.1: Sensitive authentication data (SAD) is not stored after authorization. ",
@@ -11689,6 +11785,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.1.3: Sensitive authentication data (SAD) is not stored after authorization. ",
@@ -11811,6 +11915,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.2: Sensitive authentication data (SAD) is not stored after authorization. ",
@@ -11933,6 +12045,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.3: Sensitive authentication data (SAD) is not stored after authorization. ",
@@ -13573,6 +13693,17 @@
"Checks": [
"acm_certificates_with_secure_key_algorithms"
],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "3.7.1: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented. ",
@@ -15001,6 +15132,14 @@
"Checks": [
"cloudwatch_log_group_retention_policy_specific_days_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored. ",
@@ -22504,6 +22643,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities. ",
@@ -23000,6 +23147,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Section": "A3.5.1: Suspicious events are identified and responded to. ",
diff --git a/prowler/compliance/aws/prowler_threatscore_aws.json b/prowler/compliance/aws/prowler_threatscore_aws.json
index 902beb8abd..c8c093907a 100644
--- a/prowler/compliance/aws/prowler_threatscore_aws.json
+++ b/prowler/compliance/aws/prowler_threatscore_aws.json
@@ -174,6 +174,20 @@
"iam_user_accesskey_unused",
"iam_user_console_access_unused"
],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45
+ },
+ {
+ "Check": "iam_user_console_access_unused",
+ "ConfigKey": "max_console_access_days",
+ "Operator": "lte",
+ "Value": 45
+ }
+ ],
"Attributes": [
{
"Title": "IAM credentials unused disabled",
@@ -336,6 +350,14 @@
"Checks": [
"accessanalyzer_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Title": "Access Analyzer enabled",
@@ -1541,6 +1563,14 @@
"Checks": [
"config_recorder_all_regions_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Title": "AWS Config is enabled",
@@ -1829,6 +1859,14 @@
"Checks": [
"securityhub_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ],
"Attributes": [
{
"Title": "Security Hub enabled",
diff --git a/prowler/compliance/aws/rbi_cyber_security_framework_aws.json b/prowler/compliance/aws/rbi_cyber_security_framework_aws.json
index b4566a8929..554b40cdad 100644
--- a/prowler/compliance/aws/rbi_cyber_security_framework_aws.json
+++ b/prowler/compliance/aws/rbi_cyber_security_framework_aws.json
@@ -40,6 +40,10 @@
"ec2_instance_public_ip",
"efs_encryption_at_rest_enabled",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"elb_ssl_listeners",
"ec2_ebs_default_encryption",
"emr_cluster_master_nodes_no_public_ip",
@@ -182,6 +186,14 @@
"securityhub_enabled",
"vpc_flow_logs_enabled",
"opensearch_service_domains_audit_logging_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/secnumcloud_3.2_aws.json b/prowler/compliance/aws/secnumcloud_3.2_aws.json
index 1e157b47c7..8075dc3610 100644
--- a/prowler/compliance/aws/secnumcloud_3.2_aws.json
+++ b/prowler/compliance/aws/secnumcloud_3.2_aws.json
@@ -202,6 +202,14 @@
"Checks": [
"config_recorder_all_regions_enabled",
"ec2_instance_managed_by_ssm"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -323,6 +331,14 @@
"iam_role_administratoraccess_policy",
"iam_user_administrator_access_policy",
"iam_user_two_active_access_key"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -474,6 +490,10 @@
"elbv2_ssl_listeners",
"elb_insecure_ssl_ciphers",
"elbv2_insecure_ssl_ciphers",
+ "elbv2_listener_pqc_tls_enabled",
+ "cloudfront_distributions_pqc_tls_enabled",
+ "apigateway_domain_name_pqc_tls_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"redshift_cluster_in_transit_encryption_enabled",
"elasticache_redis_cluster_in_transit_encryption_enabled",
"dynamodb_accelerator_cluster_in_transit_encryption_enabled",
@@ -560,6 +580,17 @@
"Checks": [
"acm_certificates_expiration_check",
"acm_certificates_with_secure_key_algorithms"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ }
]
},
{
@@ -732,6 +763,14 @@
"config_recorder_all_regions_enabled",
"cloudtrail_multi_region_enabled",
"cloudtrail_multi_region_enabled_logging_management_events"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -771,6 +810,14 @@
"guardduty_lambda_protection_enabled",
"guardduty_eks_audit_log_enabled",
"guardduty_eks_runtime_monitoring_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -908,6 +955,20 @@
"cloudwatch_changes_to_network_gateways_alarm_configured",
"cloudwatch_changes_to_network_route_tables_alarm_configured",
"cloudwatch_changes_to_vpcs_alarm_configured"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1011,6 +1072,14 @@
"config_recorder_all_regions_enabled",
"config_recorder_using_aws_service_role",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1057,6 +1126,14 @@
"Checks": [
"guardduty_is_enabled",
"vpc_flow_logs_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1088,6 +1165,14 @@
"Checks": [
"config_recorder_all_regions_enabled",
"cloudtrail_multi_region_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1265,6 +1350,20 @@
"guardduty_is_enabled",
"securityhub_enabled",
"cloudwatch_alarm_actions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1415,6 +1514,14 @@
"Checks": [
"backup_plans_exist",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1478,6 +1585,20 @@
"Checks": [
"securityhub_enabled",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -1495,6 +1616,14 @@
"Checks": [
"inspector2_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/aws/soc2_aws.json b/prowler/compliance/aws/soc2_aws.json
index 5a027d0416..c0041a9dae 100644
--- a/prowler/compliance/aws/soc2_aws.json
+++ b/prowler/compliance/aws/soc2_aws.json
@@ -43,6 +43,14 @@
"cloudtrail_s3_dataevents_write_enabled",
"cloudtrail_multi_region_enabled",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -61,6 +69,26 @@
"guardduty_is_enabled",
"securityhub_enabled",
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -80,6 +108,14 @@
"ssm_managed_compliant_patching",
"guardduty_no_high_severity_findings",
"guardduty_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -116,6 +152,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -133,6 +177,14 @@
"Checks": [
"guardduty_is_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -312,6 +364,20 @@
"Checks": [
"guardduty_is_enabled",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -331,6 +397,20 @@
"securityhub_enabled",
"ec2_instance_managed_by_ssm",
"ssm_managed_compliant_patching"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -367,6 +447,20 @@
"guardduty_is_enabled",
"apigateway_restapi_logging_enabled",
"ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -399,6 +493,20 @@
"cloudwatch_log_group_retention_policy_specific_days_enabled",
"vpc_flow_logs_enabled",
"guardduty_no_high_severity_findings"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -426,6 +534,20 @@
"redshift_cluster_automated_snapshot",
"s3_bucket_object_versioning",
"securityhub_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -463,6 +585,14 @@
],
"Checks": [
"config_recorder_all_regions_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
@@ -600,6 +730,14 @@
"rds_cluster_integration_cloudwatch_logs",
"glue_etl_jobs_logging_enabled",
"stepfunctions_statemachine_logging_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
]
},
{
diff --git a/prowler/compliance/azure/c5_azure.json b/prowler/compliance/azure/c5_azure.json
index 4ac3b4dd53..6fff7a3691 100644
--- a/prowler/compliance/azure/c5_azure.json
+++ b/prowler/compliance/azure/c5_azure.json
@@ -2681,6 +2681,17 @@
"app_function_latest_runtime_version",
"mysql_flexible_server_minimum_tls_version_12",
"sqlserver_recommended_minimal_tls_version"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -2705,6 +2716,17 @@
"app_function_latest_runtime_version",
"mysql_flexible_server_minimum_tls_version_12",
"sqlserver_recommended_minimal_tls_version"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -3903,6 +3925,17 @@
"app_ensure_php_version_is_latest",
"storage_ensure_minimum_tls_version_12",
"storage_smb_protocol_version_is_latest"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -4352,6 +4385,17 @@
"sqlserver_recommended_minimal_tls_version",
"sqlserver_tde_encrypted_with_cmk",
"sqlserver_tde_encryption_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -5743,6 +5787,17 @@
"storage_ensure_minimum_tls_version_12",
"sqlserver_tde_encrypted_with_cmk",
"sqlserver_tde_encryption_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -5770,6 +5825,17 @@
"storage_ensure_minimum_tls_version_12",
"sqlserver_tde_encrypted_with_cmk",
"sqlserver_tde_encryption_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -6513,6 +6579,17 @@
"mysql_flexible_server_minimum_tls_version_12",
"sqlserver_recommended_minimal_tls_version",
"storage_ensure_minimum_tls_version_12"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/azure/ccc_azure.json b/prowler/compliance/azure/ccc_azure.json
index cb87346d13..661d38302f 100644
--- a/prowler/compliance/azure/ccc_azure.json
+++ b/prowler/compliance/azure/ccc_azure.json
@@ -56,6 +56,25 @@
"app_ensure_using_http20",
"app_ftp_deployment_disabled",
"app_function_ftps_deployment_disabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ },
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
]
},
{
@@ -726,6 +745,16 @@
],
"Checks": [
"storage_smb_channel_encryption_with_secure_algorithm"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/azure/cis_2.0_azure.json b/prowler/compliance/azure/cis_2.0_azure.json
index 73f4dc3611..59bd153352 100644
--- a/prowler/compliance/azure/cis_2.0_azure.json
+++ b/prowler/compliance/azure/cis_2.0_azure.json
@@ -2714,7 +2714,8 @@
"Id": "6.6",
"Description": "Ensure that Network Watcher is 'Enabled'",
"Checks": [
- "network_watcher_enabled"
+ "network_watcher_enabled",
+ "network_vnet_ddos_protection_enabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/cis_2.1_azure.json b/prowler/compliance/azure/cis_2.1_azure.json
index 805c81bbd8..a663e5be18 100644
--- a/prowler/compliance/azure/cis_2.1_azure.json
+++ b/prowler/compliance/azure/cis_2.1_azure.json
@@ -1383,7 +1383,7 @@
"Id": "3.7",
"Description": "Ensure that 'Public Network Access' is `Disabled' for storage accounts",
"Checks": [
- "storage_blob_public_access_level_is_disabled"
+ "storage_account_public_network_access_disabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/cis_3.0_azure.json b/prowler/compliance/azure/cis_3.0_azure.json
index 47344c19ee..107c495d05 100644
--- a/prowler/compliance/azure/cis_3.0_azure.json
+++ b/prowler/compliance/azure/cis_3.0_azure.json
@@ -1651,7 +1651,7 @@
"Id": "4.6",
"Description": "Ensure that 'Public Network Access' is 'Disabled' for storage accounts",
"Checks": [
- "storage_blob_public_access_level_is_disabled"
+ "storage_account_public_network_access_disabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/cis_4.0_azure.json b/prowler/compliance/azure/cis_4.0_azure.json
index ba15a661ef..5f3e4502f1 100644
--- a/prowler/compliance/azure/cis_4.0_azure.json
+++ b/prowler/compliance/azure/cis_4.0_azure.json
@@ -253,6 +253,18 @@
"References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications:https://learn.microsoft.com/en-us/azure/defender-for-cloud/how-to-manage-attack-path:https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-attack-path",
"DefaultValue": ""
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_attack_path_notifications_properly_configured",
+ "ConfigKey": "defender_attack_path_minimal_risk_level",
+ "Operator": "in",
+ "Value": [
+ "Low",
+ "Medium",
+ "High"
+ ]
+ }
]
},
{
@@ -375,6 +387,16 @@
"Checks": [
"storage_smb_channel_encryption_with_secure_algorithm"
],
+ "ConfigRequirements": [
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "10 Storage Services",
@@ -3021,7 +3043,7 @@
"Id": "10.3.2.2",
"Description": "Ensure that 'Public Network Access' is 'Disabled' for storage accounts",
"Checks": [
- "storage_blob_public_access_level_is_disabled"
+ "storage_account_public_network_access_disabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/cis_5.0_azure.json b/prowler/compliance/azure/cis_5.0_azure.json
index 49b18f9326..71e43aeee9 100644
--- a/prowler/compliance/azure/cis_5.0_azure.json
+++ b/prowler/compliance/azure/cis_5.0_azure.json
@@ -1974,7 +1974,9 @@
{
"Id": "7.11",
"Description": "Ensure subnets are associated with network security groups",
- "Checks": [],
+ "Checks": [
+ "network_subnet_nsg_associated"
+ ],
"Attributes": [
{
"Section": "7 Networking Services",
@@ -2094,7 +2096,9 @@
{
"Id": "8.1.1.1",
"Description": "Ensure Microsoft Defender CSPM is set to 'On'",
- "Checks": [],
+ "Checks": [
+ "defender_ensure_defender_cspm_is_on"
+ ],
"Attributes": [
{
"Section": "8 Security Services",
@@ -2610,6 +2614,18 @@
"References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications:https://learn.microsoft.com/en-us/azure/defender-for-cloud/how-to-manage-attack-path:https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-attack-path",
"DefaultValue": ""
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_attack_path_notifications_properly_configured",
+ "ConfigKey": "defender_attack_path_minimal_risk_level",
+ "Operator": "in",
+ "Value": [
+ "Low",
+ "Medium",
+ "High"
+ ]
+ }
]
},
{
@@ -2931,7 +2947,9 @@
{
"Id": "8.5",
"Description": "Ensure Azure DDoS Network Protection is enabled on virtual networks",
- "Checks": [],
+ "Checks": [
+ "network_vnet_ddos_protection_enabled"
+ ],
"Attributes": [
{
"Section": "8 Security Services",
@@ -3000,6 +3018,16 @@
"Checks": [
"storage_smb_channel_encryption_with_secure_algorithm"
],
+ "ConfigRequirements": [
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "9 Storage Services",
@@ -3182,7 +3210,7 @@
"Id": "9.3.2.2",
"Description": "Ensure that 'Public Network Access' is 'Disabled' for storage accounts",
"Checks": [
- "storage_blob_public_access_level_is_disabled"
+ "storage_account_public_network_access_disabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/cis_6.0_azure.json b/prowler/compliance/azure/cis_6.0_azure.json
new file mode 100644
index 0000000000..625a0c18fa
--- /dev/null
+++ b/prowler/compliance/azure/cis_6.0_azure.json
@@ -0,0 +1,2863 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS Microsoft Azure Foundations Benchmark v6.0.0",
+ "Version": "6.0",
+ "Provider": "Azure",
+ "Description": "The CIS Azure Foundations Benchmark provides prescriptive guidance for configuring security options for a subset of Azure with an emphasis on foundational, testable, and architecture agnostic settings.",
+ "Requirements": [
+ {
+ "Id": "2.1.1",
+ "Description": "Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet)",
+ "Checks": [
+ "databricks_workspace_vnet_injection_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet)",
+ "RationaleStatement": "Using a customer-managed VNet ensures better control over network security and aligns with zero-trust architecture principles. It allows for: - Restricted outbound internet access to prevent unauthorized data exfiltration. - Integration with on-premises networks via VPN or ExpressRoute for hybrid connectivity. - Fine-grained NSG policies to restrict access at the subnet level. - Private Link for secure API access, avoiding public internet exposure.",
+ "ImpactStatement": "- Requires additional configuration during Databricks workspace deployment. - Might increase operational overhead for network maintenance. - May impact connectivity if misconfigured (e.g., restrictive NSG rules or missing routes).",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Delete the existing Databricks workspace (migration required). 1. Create a new Databricks workspace with VNet Injection: 1. Go to Azure Portal Create Databricks Workspace. 1. Select Advanced Networking. 1. Choose Deploy into your own Virtual Network. 1. Specify a customer-managed VNet and associated subnets. 1. Enable Private Link for secure API access. **Remediate from Azure CLI** Deploy a new Databricks workspace in a custom VNet: ``` az databricks workspace create --name <databricks-workspace-name> \\ --resource-group <resource-group-name> \\ --location <region> \\ --managed-resource-group <managed-rg-name> \\ --enable-no-public-ip true \\ --network-security-group-rule NoAzureServices \\ --public-network-access Disabled \\ --custom-virtual-network-id /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Network/virtualNetworks/<vnet-name> ``` Ensure NSG Rules are correctly configured: ``` az network nsg rule create --resource-group <resource-group-name> \\ --nsg-name <nsg-name> \\ --name DenyAllOutbound \\ --direction Outbound \\ --access Deny \\ --priority 4096 ``` **Remediate from PowerShell** ``` New-AzDatabricksWorkspace -ResourceGroupName <resource-group-name> -Name <databricks-workspace-name> -Location <region> -ManagedResourceGroupName <managed-rg-name> -CustomVirtualNetworkId /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Network/virtualNetworks/<vnet-name> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to Azure Portal Search for Databricks Workspaces. 1. Select the Databricks Workspace to audit. 1. Under Networking, check if the workspace is deployed in a Customer-Managed VNet. 1. If the Virtual Network field shows Databricks-Managed VNet, it is non-compliant. 1. Verify NSG rules and Private Endpoints for fine-grained access control. **Audit from Azure CLI** Run the following command to check if Databricks is using a customer-managed VNet: ``` az network vnet show --resource-group <resource-group-name> --name <vnet-name> ``` Ensure that Databricks subnets are present in the VNet configuration. Validate NSG rules attached to the Databricks subnets. **Audit from PowerShell** ``` Get-AzDatabricksWorkspace -ResourceGroupName <resource-group-name> -Name <databricks-workspace-name> | Select-Object VirtualNetworkId ``` If VirtualNetworkId is null or shows a Databricks-Managed VNet, it is non-compliant. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [9c25c9e4-ee12-4882-afd2-11fb9d87893f](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%9c25c9e4-ee12-4882-afd2-11fb9d87893f) **- Name:** 'Azure Databricks Workspaces should be in a virtual network'",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, Azure Databricks uses a Databricks-Managed VNet."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.2",
+ "Description": "Ensure that Network Security Groups are Configured for Databricks Subnets",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Network Security Groups are Configured for Databricks Subnets",
+ "RationaleStatement": "Using NSGs with both explicit allow and deny rules provides clear documentation and control over permitted and prohibited traffic. While Azure NSGs implicitly deny all traffic not explicitly allowed, defining explicit deny rules for known malicious or unnecessary sources enhances clarity, simplifies troubleshooting, and supports compliance audits.",
+ "ImpactStatement": "* NSGs require periodic maintenance to ensure rule accuracy. * Misconfigured NSGs could inadvertently block required traffic.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Assign NSG to Databricks subnets under Networking > NSG Settings.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to Virtual Networks > Subnets, and review NSG assignments. **Audit from Azure CLI** ``` az network nsg list --query [].{Name:name, Rules:securityRules} ``` **Audit from PowerShell** ``` Get-AzNetworkSecurityGroup -ResourceGroupName <resource-group-name> ```",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/azure-databricks-security-baseline:https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/vnet-inject#network-security-group-rules",
+ "DefaultValue": "By default, Databricks subnets do not have NSGs assigned."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.3",
+ "Description": "Ensure that Traffic is Encrypted Between Cluster Worker Nodes",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Traffic is Encrypted Between Cluster Worker Nodes",
+ "RationaleStatement": "* Protects sensitive data during transit between cluster nodes, mitigating risks of data interception or unauthorized access. * Aligns with organizational security policies and compliance requirements that mandate encryption of data in transit. * Enhances overall security posture by ensuring that all inter-node communications within the cluster are encrypted.",
+ "ImpactStatement": "* Enabling encryption may introduce a performance penalty due to the computational overhead associated with encrypting and decrypting traffic. This can result in longer query execution times, especially for data-intensive operations. * Implementing encryption requires creating and managing init scripts, which adds complexity to cluster configuration and maintenance. * The shared encryption secret is derived from the hash of the keystore stored in DBFS. If the keystore is updated or rotated, all running clusters must be restarted to prevent authentication failures between Spark workers and drivers.",
+ "RemediationProcedure": "Create a JKS keystore: 1. Generate a Java KeyStore (JKS) file that will be used for SSL/TLS encryption. 2. Upload the keystore file to a secure directory in DBFS (e.g. /dbfs/<keystore-directory>/jetty_ssl_driver_keystore.jks). Develop an init script: 3. Create an init script that performs the following tasks: - Retrieves the JKS keystore file and password. - Derives a shared encryption secret from the keystore. - Configures Spark driver and executor settings to enable encryption. 4. Example init script: ``` #!/bin/bash set -euo pipefail keystore_dbfs_file=/dbfs/<keystore-directory>/jetty_ssl_driver_keystore.jks max_attempts=30 while [ ! -f ${keystore_dbfs_file} ]; do if [ $max_attempts == 0 ]; then echo ERROR: Unable to find the file : $keystore_dbfs_file. Failing the script. exit 1 fi sleep 2s ((max_attempts--)) done sasl_secret=$(sha256sum $keystore_dbfs_file | cut -d' ' -f1) if [ -z ${sasl_secret} ]; then echo ERROR: Unable to derive the secret. Failing the script. exit 1 fi local_keystore_file=$DB_HOME/keys/jetty_ssl_driver_keystore.jks local_keystore_password=gb1gQqZ9ZIHS if [[ $DB_IS_DRIVER = TRUE ]]; then driver_conf=${DB_HOME}/driver/conf/spark-branch.conf echo Configuring driver conf at $driver_conf if [ ! -e $driver_conf ]; then echo spark.authenticate true >> $driver_conf echo spark.authenticate.secret $sasl_secret >> $driver_conf echo spark.authenticate.enableSaslEncryption true >> $driver_conf echo spark.network.crypto.enabled true >> $driver_conf echo spark.network.crypto.keyLength 256 >> $driver_conf echo spark.network.crypto.keyFactoryAlgorithm PBKDF2WithHmacSHA1 >> $driver_conf echo spark.io.encryption.enabled true >> $driver_conf echo spark.ssl.enabled true >> $driver_conf echo spark.ssl.keyPassword $local_keystore_password >> $driver_conf echo spark.ssl.keyStore $local_keystore_file >> $driver_conf echo spark.ssl.keyStorePassword $local_keystore_password >> $driver_conf echo spark.ssl.protocol TLSv1.3 >> $driver_conf fi fi executor_conf=${DB_HOME}/conf/spark.executor.extraJavaOptions echo Configuring executor conf at $executor_conf if [ ! -e $executor_conf ]; then echo -Dspark.authenticate=true >> $executor_conf echo -Dspark.authenticate.secret=$sasl_secret >> $executor_conf echo -Dspark.authenticate.enableSaslEncryption=true >> $executor_conf echo -Dspark.network.crypto.enabled=true >> $executor_conf echo -Dspark.network.crypto.keyLength=256 >> $executor_conf echo -Dspark.network.crypto.keyFactoryAlgorithm=PBKDF2WithHmacSHA1 >> $executor_conf echo -Dspark.io.encryption.enabled=true >> $executor_conf echo -Dspark.ssl.enabled=true >> $executor_conf echo -Dspark.ssl.keyPassword=$local_keystore_password >> $executor_conf echo -Dspark.ssl.keyStore=$local_keystore_file >> $executor_conf echo -Dspark.ssl.keyStorePassword=$local_keystore_password >> $executor_conf echo -Dspark.ssl.protocol=TLSv1.3 >> $executor_conf fi ``` 5. Save.",
+ "AuditProcedure": "**Audit from Azure Portal** Review cluster init scripts: 1. Navigate to your Azure Databricks workspace, go to the Clusters section, select a cluster, and check the Advanced Options for any init scripts that configure encryption settings. Verify spark configuration: 2. Ensure that the following Spark configurations are set: ``` spark.authenticate true spark.authenticate.enableSaslEncryption true spark.network.crypto.enabled true spark.network.crypto.keyLength 256 spark.network.crypto.keyFactoryAlgorithm PBKDF2WithHmacSHA1 spark.io.encryption.enabled true ``` These settings can be found in the cluster's Spark configuration properties. Check keystone management: 3. Verify that the Java KeyStore (JKS) file is securely stored in DBFS and that its integrity is maintained. 4. Ensure that the keystore password is securely managed and not hardcoded in scripts.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/security/keys/encrypt-otw",
+ "DefaultValue": "By default, traffic is not encrypted between cluster worker nodes."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.4",
+ "Description": "Ensure that Users and Groups are Synced from Microsoft Entra ID to Azure Databricks",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Users and Groups are Synced from Microsoft Entra ID to Azure Databricks",
+ "RationaleStatement": "Syncing users and groups from Microsoft Entra ID centralizes access control, enforces the least privilege principle by automatically revoking unnecessary access, reduces administrative overhead by eliminating manual user management, and ensures auditability and compliance with industry regulations.",
+ "ImpactStatement": "SCIM provisioning requires role mapping to avoid misconfigured user privileges.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Enable provisioning in Azure Portal: 1. Go to `Microsoft Entra ID`. 1. Under `Manage`, click `Enterprise applications`. 1. Click the name of the Azure Databricks SCIM application. 1. Under `Provisioning`, select `Automatic` and enter the SCIM endpoint and API token from Databricks. Enable provisioning in Databricks: 5. Navigate to `Admin Console` > `Identity and Access Management`. 6. Enable SCIM provisioning and generate an API token. Configure role assignments: 7. Ensure groups from Entra ID are mapped to appropriate Databricks roles. 8. Restrict administrative privileges to designated security groups. Regularly monitor sync logs: 9. Periodically review sync logs in Microsoft Entra ID and Databricks Admin Console. 10. Configure Azure Monitor alerts for provisioning failures. Disable manual user creation in Databricks: 11. Ensure that all user management is controlled via SCIM sync from Entra ID. 12. Disable personal access token usage for authentication. **Remediate from Azure CLI** Enable SCIM User and Group Provisioning in Azure Databricks: ``` az ad app update --id <databricks-app-id> --set provisioning.provisioningMode=Automatic ```",
+ "AuditProcedure": "**Audit from Azure Portal** Verify SCIM provisioning is enabled: 1. Go to `Microsoft Entra ID`. 1. Under `Manage`, click `Enterprise applications`. 1. Click the name of the Azure Databricks SCIM application. 1. Under `Provisioning`, confirm that SCIM provisioning is enabled and running. Check user sync status in Azure Portal: 5. Under `Provisioning Logs`, verify the last successful sync and any failed entries. Check user sync status in Databricks: 6. Go to `Admin Console` > `Identity and Access Management`. 7. Confirm that Users and Groups match those assigned in Microsoft Entra ID. Ensure role-based access control (RBAC) mapping is correct: 8. Verify that users are assigned appropriate Databricks roles (e.g. Admin, User, Contributor). 9. Confirm that groups are mapped to workspace access roles.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/administration-guide/users-groups/scim/aad",
+ "DefaultValue": "By default, Azure Databricks does not sync users and groups from Microsoft Entra ID."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.5",
+ "Description": "Ensure that Unity Catalog is Configured for Azure Databricks",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Unity Catalog is Configured for Azure Databricks",
+ "RationaleStatement": "* Enforces centralized access control policies and reduces data security risks. * Enables identity-based authentication via Microsoft Entra ID. * Improves compliance with industry regulations (e.g. GDPR, HIPAA, SOC 2) by providing audit logs and access visibility. * Prevents unauthorized data access through table-, row-, and column-level security (RLS & CLS).",
+ "ImpactStatement": "* Improperly configured permissions may lead to data exfiltration or unauthorized access. * Unity Catalog requires structured governance policies to be effective and prevent overly permissive access.",
+ "RemediationProcedure": "Use the remediation procedure written in this article: https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/get-started.",
+ "AuditProcedure": "Method 1: Verify unity catalog deployment: 1. As an Azure Databricks account admin, log into the account console. 1. Click Workspaces. 1. Find your workspace and check the Metastore column. If a metastore name is present, your workspace is attached to a Unity Catalog metastore and therefore enabled for Unity Catalog. Method 2: Run a SQL query to confirm Unity Catalog enablement Run the following SQL query in the SQL query editor or a notebook that is attached to a Unity Catalog-enabled compute resource. No admin role is required. ``` SELECT CURRENT_METASTORE(); ``` If the query returns a metastore ID like the following, then your workspace is attached to a Unity Catalog metastore and therefore enabled for Unity Catalog.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/:https://learn.microsoft.com/en-us/azure/databricks/admin/users-groups/:https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/enable-workspaces",
+ "DefaultValue": "New workspaces have Unity Catalog enabled by default. Existing workspaces may require manual enablement."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.6",
+ "Description": "Ensure that Usage is Restricted and Expiry is Enforced for Databricks Personal Access Tokens",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Usage is Restricted and Expiry is Enforced for Databricks Personal Access Tokens",
+ "RationaleStatement": "Restricting usage and enforcing expiry for personal access tokens reduces exposure to long-lived tokens, minimizes the risk of API abuse if compromised, and aligns with security best practices through controlled issuance and enforced expiry.",
+ "ImpactStatement": "If revoked improperly, applications relying on these tokens may fail, requiring a remediation plan for token rotation. Increased administrative effort is required to track and manage API tokens effectively.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Disable personal access tokens: If your workspace does not require PATs, you can disable them entirely to prevent their use.",
+ "AuditProcedure": "Azure Databricks administrators can monitor and revoke personal access tokens within their workspace. Detailed instructions are available in the Monitor and Revoke Personal Access Tokens section of the Microsoft documentation: https://learn.microsoft.com/en-us/azure/databricks/admin/access-control/tokens. To evaluate the usage of personal access tokens in your Azure Databricks account, you can utilize the provided notebook that lists all PATs not rotated or updated in the last 90 days, allowing you to identify tokens that may require revocation. This process is detailed here: https://docs.azure.cn/en-us/databricks/security/auth/oauth-pat-usage. Implementing diagnostic logging provides a comprehensive reference of audit log services and events, enabling you to track activities related to personal access tokens. More information can be found in the diagnostic log reference section: https://docs.azure.cn/en-us/databricks/security/auth/oauth-pat-usage.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/administration-guide/access-control/tokens:https://learn.microsoft.com/en-us/azure/databricks/dev-tools/auth/",
+ "DefaultValue": "By default, personal access tokens are enabled and users can create the Personal access token and their expiry time."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.7",
+ "Description": "Ensure that Diagnostic Log Delivery is Configured for Azure Databricks",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Diagnostic Log Delivery is Configured for Azure Databricks",
+ "RationaleStatement": "Diagnostic logging provides visibility into security and operational activities within Databricks workspaces while maintaining an audit trail for forensic investigations, and it supports compliance with regulatory standards that require logging and monitoring.",
+ "ImpactStatement": "Logs consume storage and may require additional monitoring tools, leading to increased operational overhead and costs. Incomplete log configurations may result in missing critical events, reducing monitoring effectiveness.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Enable diagnostic logging for Azure Databricks: 1. Navigate to your Azure Databricks workspace. 1. In the left-hand menu, select `Monitoring` > `Diagnostic settings`. 1. Click `+ Add diagnostic setting`. 1. Under `Category details`, select the log categories you wish to capture, such as AuditLogs, Clusters, Notebooks, and Jobs. 1. Choose a destination for the logs: - `Log Analytics workspace`: For advanced querying and monitoring. - `Storage account`: For long-term retention. - `Event Hub`: For integration with third-party systems. 1. Provide a `Name` for the diagnostic setting. 1. Click `Save`. Implement log retention policies: 1. Navigate to your Log Analytics workspace. 1. Under `General`, select `Usage and estimated costs`. 1. Click `Data Retention`. 1. Adjust the retention period slider to the desired number of days (up to 730 days). 1. Click `OK`. Monitor logs for anomalies: 1. Navigate to `Azure Monitor`. 1. Select `Alerts` > `+ New alert rule`. 1. Under `Scope`, specify the Databricks resource. 1. Define `Condition` based on log queries that identify anomalies (e.g. unauthorized access attempts). 1. Configure `Actions` to notify stakeholders or trigger automated responses. 1. Provide an Alert rule `name` and `description`. 1. Click `Create alert rule`. **Remediate from Azure CLI** Enable diagnostic logging for Azure Databricks: ``` az monitor diagnostic-settings create --name DatabricksLogging --resource <databricks-resource-id> --logs '[{category: AuditLogs, enabled: true}, {category: Clusters, enabled: true}, {category: Notebooks, enabled: true}, {category: Jobs, enabled: true}]' --workspace <log-analytics-id> ``` Implement log retention policies: ``` az monitor log-analytics workspace update --resource-group <resource-group> --name <log-analytics-name> --retention-time 365 ``` Monitor logs for anomalies: ``` az monitor activity-log alert create --name DatabricksAnomalyAlert --resource-group <resource-group> --scopes <databricks-resource-id> --condition contains 'UnauthorizedAccess' ```",
+ "AuditProcedure": "**Audit from Azure Portal** Check if diagnostic logging is enabled for the Databricks workspace: 1. Go to `Azure Databricks`. 1. Select a workspace. 1. In the left-hand menu, select `Monitoring` > `Diagnostic settings`. 1. Verify if a diagnostic setting is configured. If not, diagnostic logging is not enabled. Ensure that logging is enabled for the following categories:",
+ "AdditionalInformation": "* Ensure that the Azure Databricks workspace is on the Premium plan to utilize diagnostic logging features. * Regularly review and update alert rules to adapt to evolving security threats and operational requirements.",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/admin/account-settings/audit-log-delivery:https://learn.microsoft.com/en-us/troubleshoot/azure/azure-monitor/log-analytics/billing/configure-data-retention",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.8",
+ "Description": "Ensure Critical Data in Azure Databricks is Encrypted with Customer-managed Keys (CMK)",
+ "Checks": [
+ "databricks_workspace_cmk_encryption_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Critical Data in Azure Databricks is Encrypted with Customer-managed Keys (CMK)",
+ "RationaleStatement": "By default in Azure, data at rest tends to be encrypted using Microsoft Managed Keys. If your organization wants to control and manage encryption keys for compliance and defense-in-depth, Customer Managed Keys can be established. While it is possible to automate the assessment of this recommendation, the assessment status for this recommendation remains 'Manual' due to ideally limited scope. The scope of application - which workloads CMK is applied to - should be carefully considered to account for organizational capacity and targeted to workloads with specific need for CMK.",
+ "ImpactStatement": "If the key expires due to setting the 'activation date' and 'expiration date', the key must be rotated manually. Using Customer Managed Keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed.",
+ "RemediationProcedure": "NOTE: These remediations assume that an Azure KeyVault already exists in the subscription. Remediate from Azure CLI 1. Create a dedicated key: az keyvault key create --vault-name <keyvault-name> --name <key-name> -protection <software or hsm> 2. Assign permissions to Databricks: az keyvault set-policy --name <keyvault-name> --resource-group <resourcegroup-name> --spn <databricks-spn> --key-permissions get wrapKey unwrapKey 3. Enable encryption with CMK: az databricks workspace update --name <databricks-workspace-name> --resourcegroup <resource-group-name> --key-source Microsoft.KeyVault --key-name <key-name> --keyvault-uri <keyvault-uri> Remediate from PowerShell $Key = Add-AzKeyVaultKey -VaultName <keyvault-name> -Name <key-name> Destination <software or hsm> Set-AzDatabricksWorkspace -ResourceGroupName <resource-group-name> WorkspaceName <databricks-workspace-name> -EncryptionKeySource Microsoft.KeyVault -KeyVaultUri $Key.Id",
+ "AuditProcedure": "Audit: Audit from Azure Portal 1. Go to Azure Portal → Databricks Workspaces. 2. Select a Databricks Workspace and go to Encryption settings. 3. Check if customer-managed keys (CMK) are enabled under Managed Disk Encryption .4. If CMK is not enabled, the workspace is non-compliant. Audit from Azure CLI Run the following command to check encryption settings for Databricks workspace: az databricks workspace show --name <databricks-workspace-name> --resourcegroup <resource-group-name> --query encryption Ensure that keySource is set to Microsoft.KeyVault. Audit from PowerShell Get-AzDatabricksWorkspace -ResourceGroupName <resource-group-name> -Name <databricks-workspace-name> | Select-Object Encryption Verify that encryption is set to Customer-Managed Keys (CMK). Audit from Databricks CLI databricks workspace get-metadata --workspace-id <workspace-id> Ensure that encryption settings reflect a CMK setup.",
+ "AdditionalInformation": "This recommendation is based on the Common Reference Recommendation Ensure critical data is encrypted with customer-managed keys (CMK).",
+ "References": "https://docs.microsoft.com/en-us/azure/security/fundamentals/data-encryption-best-practices#protect-data-at-rest:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-5-use-customer-managed-key-option-in-data-at-rest-encryption-when-required",
+ "DefaultValue": "By default, Encryption type is set to Microsoft Managed Keys."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.9",
+ "Description": "Ensure 'No Public IP' is Set to 'Enabled'",
+ "Checks": [
+ "databricks_workspace_no_public_ip_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'No Public IP' is Set to 'Enabled'",
+ "RationaleStatement": "Enabling secure cluster connectivity limits exposure to the public internet, improving security and reducing the risk of external attacks.",
+ "ImpactStatement": "Enabling secure cluster connectivity requires careful network configuration. Before secure cluster connectivity can be enabled, Azure Databricks workspaces must be deployed in a customer-managed virtual network (VNet injection).",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings`, click `Networking`. 4. Under `Network access`, next to `Deploy Azure Databricks workspace with Secure Cluster Connectivity (No Public IP)`, click the radio button next to `Enabled`. 5. Click `Save`. 6. Repeat steps 1-5 for each workspace requiring remediation. **Remediate from Azure CLI** For each workspace requiring remediation, run the following command to set enableNoPublicIp to true: ``` az databricks workspace update --resource-group <resource-group> --name <workspace> --enable-no-public-ip true ``` **Remediate from PowerShell** For each workspace requiring remediation, run the following command to set EnableNoPublicIP to True: ``` Update-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace> -EnableNoPublicIP ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings`, click `Networking`. 4. Under `Network access`, ensure that `Deploy Azure Databricks workspace with Secure Cluster Connectivity (No Public IP)` is set to `Enabled`. 5. Repeat steps 1-4 for each workspace. **Audit from Azure CLI** Run the following command to list workspaces: ``` az databricks workspace list ``` For each workspace, run the following command to get the enableNoPublicIp setting: ``` az databricks workspace show --resource-group <resource-group> --name <workspace> --query parameters.enableNoPublicIp.value ``` Ensure that `true` is returned. **Audit from PowerShell** Run the following command to list workspaces: ``` Get-AzDatabricksWorkspace ``` Run the following command to get the workspace in a resource group with a given name: ``` $workspace = Get-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace> ``` Run the following command to get the EnableNoPublicIp setting: ``` $workspace.EnableNoPublicIP ``` Ensure that `True` is returned. **Audit from Azure Policy** - **Policy ID:** [51c1490f-3319-459c-bbbc-7f391bbed753] **- Name:** 'Azure Databricks Clusters should disable public IP'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/secure-cluster-connectivity:https://learn.microsoft.com/en-us/cli/azure/databricks/workspace:https://learn.microsoft.com/en-us/powershell/module/az.databricks",
+ "DefaultValue": "No Public IP is set to Enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.10",
+ "Description": "Ensure 'Allow Public Network Access' is set to 'Disabled'",
+ "Checks": [
+ "databricks_workspace_public_network_access_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Allow Public Network Access' is set to 'Disabled'",
+ "RationaleStatement": "Disabling public network access improves security by ensuring that Azure Databricks workspaces are not exposed on the public internet.",
+ "ImpactStatement": "Prior to disabling public network access, it is strongly recommended that virtual network integration is completed or private endpoints/links are set up. Disabling public network access restricts access to the service and will require the configuration of a virtual network and/or private endpoints for any services or users needing access within trusted networks.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings` click `Networking`. 4. Under `Network access`, next to `Allow Public Network Access`, click the radio button next to `Disabled`. 5. Click `Save`. 6. Repeat steps 1-5 for each workspace requiring remediation. **Remediate from Azure CLI** For each workspace requiring remediation, run the following command to set publicNetworkAccess to Disabled: ``` az databricks workspace update --resource-group <resource-group> --name <workspace> --public-network-access Disabled ``` **Remediate from PowerShell** For each workspace requiring remediation, run the following command to set PublicNetworkAccess to Disabled: ``` Update-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace> -PublicNetworkAccess Disabled ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings` click `Networking`. 4. Under `Network access`, ensure `Allow Public Network Access` is set to `Disabled`. 5. Repeat steps 1-4 for each workspace. **Audit from Azure CLI** Run the following command to list workspaces: ``` az databricks workspace list ``` For each workspace, run the following command to get the publicNetworkAccess setting: ``` az databricks workspace show --resource-group <resource-group> --name <workspace> --query publicNetworkAccess ``` Ensure that `Disabled` is returned. **Audit from PowerShell** Run the following command to list workspaces: ``` Get-AzDatabricksWorkspace ``` Run the following command to get the PublicNetworkAccess setting: ``` $workspace = Get-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace> $workspace.PublicNetworkAccess ``` Ensure that `Disabled` is returned. **Audit from Azure Policy** - **Policy ID:** [0e7849de-b939-4c50-ab48-fc6b0f5eeba2] **- Name:** 'Azure Databricks Workspaces should disable public network access'",
+ "AdditionalInformation": "This recommendation is based on the Common Reference Recommendation Ensure public network access is Disabled.",
+ "References": "https://learn.microsoft.com/en-us/cli/azure/databricks/workspace:https://learn.microsoft.com/en-us/powershell/module/az.databricks",
+ "DefaultValue": "Allow Public Network Access is set to Enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.11",
+ "Description": "Ensure Private Endpoints are used to access Azure Databricks workspaces",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Private Endpoints are used to access Azure Databricks workspaces",
+ "RationaleStatement": "Using private endpoints for Azure Databricks workspaces ensures that all communication between clients, services, and data sources occurs over a secure, private IP space within an Azure Virtual Network (VNet). This approach eliminates exposure to the public internet, significantly reducing the attack surface and aligning with Zero Trust principles.",
+ "ImpactStatement": "If an Azure Virtual Network is not implemented correctly, this may result in the loss of critical network traffic. Private endpoints are charged per hour of use. Before a private endpoint can be configured, Azure Databricks workspaces must be deployed in a customer-managed virtual network, must have secure cluster connectivity enabled, and must be on the Premium pricing tier.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings`, click `Networking`. 4. Click `Private endpoint connections`. 5. Click `+ Private endpoint`. 6. Under `Project details`, select a Subscription and a Resource group. 7. Under `Instance details`, provide a Name, Network Interface Name, and select a Region. 8. Click `Next : Resource >`. 9. Select a Target sub-resource. 10. Click `Next : Virtual Network >`. 11. Under `Networking`, select a Virtual network and a Subnet. 12. Optionally, configure Private IP configuration and Application security group. 13. Click `Next : DNS >`. 14. Optionally, configure Private DNS integration. 15. Click `Next : Tags >`. 16. Optionally, configure tags. 17. Click `Next : Review + create >`. 18. Click `Create`. 19. Repeat steps 1-18 for each workspace requiring remediation. **Remediate from Azure CLI** For each workspace requiring remediation, run the following command to create a private endpoint connection: ``` az network private-endpoint create --resource-group <resource-group> --name <private-endpoint> --location <location> --vnet-name <virtual-network> --subnet <subnet> --private-connection-resource-id <workspace> --connection-name <private-endpoint-connection> --group-id <browser_authentication|databricks_ui_api> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Azure Databricks`. 2. Click the name of a workspace. 3. Under `Settings`, click `Networking`. 4. Click `Private endpoint connections`. 5. Ensure a private endpoint connection exists with a connection state of `Approved`. 6. Repeat steps 1-5 for each workspace. **Audit from Azure CLI** Run the following command to list workspaces: ``` az databricks workspace list ``` For each workspace, run the following command to get the privateEndpointConnections configuration: ``` az databricks workspace show --resource-group <resource-group> --name <workspace> --query privateEndpointConnections ``` Ensure a private endpoint connection is returned with a privateLinkServiceConnectionState status of `Approved`. **Audit from PowerShell** Run the following command to list workspaces: ``` Get-AzDatabricksWorkspace ``` Run the following command to get the PrivateEndpointConnection configuration: ``` $workspace = Get-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace> $workspace.PrivateEndpointConnection | Select-Object -Property Id,PrivateLinkServiceConnectionStateStatus ``` Ensure a private endpoint connection is returned with a PrivateLinkServiceConnectionStateStatus of `Approved`. **Audit from Azure Policy** - **Policy ID:** [258823f2-4595-4b52-b333-cc96192710d8] **- Name:** 'Azure Databricks Workspaces should use private link'",
+ "AdditionalInformation": "This recommendation is based on the Common Reference Recommendation Ensure Private Endpoints are used to access {service}.",
+ "References": "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/private-link:https://learn.microsoft.com/en-us/cli/azure/databricks/workspace:https://learn.microsoft.com/en-us/powershell/module/az.databricks",
+ "DefaultValue": "Private endpoints are not configured for Azure Databricks workspaces by default."
+ }
+ ]
+ },
+ {
+ "Id": "2.1.12",
+ "Description": "Ensure Azure Databricks groups are reviewed periodically",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Analytics Services",
+ "SubSection": "2.1 Azure Databricks",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Azure Databricks groups are reviewed periodically",
+ "RationaleStatement": "To ensure accurate privileges for your Azure Databricks implementation, your organization should review all users and permission assignments on a regular interval.",
+ "ImpactStatement": "Administrative overhead of user management.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select `Azure Databricks`. 1. Select the Databricks implementation you wish to audit. 1. Select `Access control (IAM)`. 1. Scroll down and select `Add role assignment`. 1. Search for the role you wish to add. Then select `Next`. 1. Select the group members you wish to add. Then select `Next`. 1. Review the info you have chosen, then select `Review + assign`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select `Azure Databricks`. 1. Select the Databricks implementation you wish to audit. 1. Select `Access control (IAM)`. 1. In the horizontal menu select `Role assignments`. 1. Audit the list for each role and its assignment to each user.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/azure-databricks-security-baseline:https://learn.microsoft.com/en-us/azure/databricks/security/auth/",
+ "DefaultValue": "By default Azure Databricks only has the Owner user and role assigned."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.1",
+ "Description": "Ensure only MFA Enabled Identities can Access Privileged Virtual Machine",
+ "Checks": [
+ "entra_user_with_vm_access_has_mfa"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Compute Services",
+ "SubSection": "3.1 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure only MFA Enabled Identities can Access Privileged Virtual Machine",
+ "RationaleStatement": "Integrating multi-factor authentication (MFA) as part of the organizational policy can greatly reduce the risk of an identity gaining control of valid credentials that may be used for additional tactics such as initial access, lateral movement, and collecting information. MFA can also be used to restrict access to cloud resources and APIs. An Adversary may log into accessible cloud services within a compromised environment using Valid Accounts that are synchronized to move laterally and perform actions with the virtual machine's managed identity. The adversary may then perform management actions or access cloud-hosted resources as the logged-on managed identity.",
+ "ImpactStatement": "This recommendation requires the Entra ID P2 license to implement. Ensure that identities provisioned to a virtual machine utilize an RBAC/ABAC group and are allocated a role using Azure PIM, and that the role settings require MFA or use another third-party PAM solution for accessing virtual machines.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Log in to the Azure portal. 2. This can be remediated by enabling MFA for user, Removing user access or Reducing access of managed identities attached to virtual machines. - Case I : Enable MFA for users having access on virtual machines. 1. Go to `Microsoft Entra ID`. 1. For `Per-user MFA`: 1. Under `Manage`, click `Users`. 1. Click `Per-user MFA`. 1. For each user requiring remediation, check the box next to their name. 1. Click `Enable MFA`. 1. Click `Enable`. 1. For `Conditional Access`: 1. Under `Manage`, click `Security`. 1. Under `Protect`, click `Conditional Access`. 1. Update the Conditional Access policy requiring MFA for all users, removing each user requiring remediation from the `Exclude` list. - Case II : Removing user access on a virtual machine. 1. Select the `Subscription`, then click on `Access control (IAM)`. 2. Select `Role assignments` and search for `Virtual Machine Administrator Login` or `Virtual Machine User Login` or any role that provides access to log into virtual machines. 3. Click on `Role Name`, Select `Assignments`, and remove identities with no MFA configured. - Case III : Reducing access of managed identities attached to virtual machines. 1. Select the `Subscription`, then click on `Access control (IAM)`. 2. Select `Role Assignments` from the top menu and apply filters on `Assignment type` as `Privileged administrator roles` and `Type` as `Virtual Machines`. 3. Click on `Role Name`, Select `Assignments`, and remove identities access make sure this follows the least privileges principal.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Log in to the Azure portal. 1. Select the `Subscription`, then click on `Access control (IAM)`. 1. Click `Role : All` and click `All` to display the drop-down menu. 1. Type `Virtual Machine Administrator Login` and select `Virtual Machine Administrator Login`. 1. Review the list of identities that have been assigned the `Virtual Machine Administrator Login` role. 1. Go to `Microsoft Entra ID`. 1. For `Per-user MFA`: 1. Under `Manage`, click `Users`. 1. Click `Per-user MFA`. 1. Ensure that none of the identities assigned the `Virtual Machine Administrator Login` role from step 4 have `Status` set to `disabled`. 1. For `Conditional Access`: 1. Under `Manage`, click `Security`. 1. Under `Protect`, click `Conditional Access`. 1. Ensure that none of the identities assigned the `Virtual Machine Administrator Login` role from step 4 are exempt from a Conditional Access policy requiring MFA for all users.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.1",
+ "Description": "Ensure that 'security defaults' is Enabled in Microsoft Entra ID",
+ "Checks": [
+ "entra_security_defaults_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.1 Security Defaults (Per-User MFA)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'security defaults' is Enabled in Microsoft Entra ID",
+ "RationaleStatement": "Security defaults provide secure default settings that we manage on behalf of organizations to keep customers safe until they are ready to manage their own identity security settings. For example, doing the following: - Requiring all users and admins to register for MFA. - Challenging users with MFA - when necessary, based on factors such as location, device, role, and task. - Disabling authentication from legacy authentication clients, which cant do MFA.",
+ "ImpactStatement": "This recommendation should be implemented initially and then may be overridden by other service/product specific CIS Benchmarks. Administrators should also be aware that certain configurations in Microsoft Entra ID may impact other Microsoft services such as Microsoft 365.",
+ "RemediationProcedure": "**Remediate from Azure Portal** To enable security defaults in your directory: 1. From Azure Home select the Portal Menu. 1. Browse to `Microsoft Entra ID` > `Properties`. 1. Select `Manage security defaults`. 1. Under `Security defaults`, select `Enabled (recommended)`. 1. Select `Save`.",
+ "AuditProcedure": "**Audit from Azure Portal** To ensure security defaults is enabled in your directory: 1. From Azure Home select the Portal Menu. 2. Browse to `Microsoft Entra ID` > `Properties`. 3. Select `Manage security defaults`. 4. Under `Security defaults`, verify that `Enabled (recommended)` is selected.",
+ "AdditionalInformation": "This recommendation differs from the [Microsoft 365 Benchmark](https://workbench.cisecurity.org/benchmarks/5741). This is because the potential impact associated with disabling Security Defaults is dependent upon the security settings implemented in the environment. It is recommended that organizations disabling Security Defaults implement appropriate security settings to replace the settings configured by Security Defaults.",
+ "References": "https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults:https://techcommunity.microsoft.com/t5/azure-active-directory-identity/introducing-security-defaults/ba-p/1061414:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-2-protect-identity-and-authentication-systems",
+ "DefaultValue": "If your tenant was created on or after October 22, 2019, security defaults may already be enabled in your tenant."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2",
+ "Description": "Ensure that 'Require Multifactor Authentication to register or join devices with Microsoft Entra' is set to 'Yes'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.1 Security Defaults (Per-User MFA)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'Require Multifactor Authentication to register or join devices with Microsoft Entra' is set to 'Yes'",
+ "RationaleStatement": "Multi-factor authentication is recommended when adding devices to Microsoft Entra ID. When set to `Yes`, users who are adding devices from the internet must first use the second method of authentication before their device is successfully added to the directory. This ensures that rogue devices are not added to the domain using a compromised user account.",
+ "ImpactStatement": "A slight impact of additional overhead, as Administrators will now have to approve every access to the domain.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, select `Devices` 1. Under `Manage`, select `Device settings` 1. Under `Microsoft Entra join and registration settings`, set `Require Multifactor Authentication to register or join devices with Microsoft Entra` to `Yes` 1. Click `Save`",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, select `Devices` 1. Under `Manage`, select `Device settings` 1. Under `Microsoft Entra join and registration settings`, ensure that `Require Multifactor Authentication to register or join devices with Microsoft Entra` is set to `Yes`",
+ "AdditionalInformation": "If Conditional Access is available, this recommendation should be bypassed in favor of the Conditional Access implementation of requiring Multifactor Authentication to register or join devices with Microsoft Entra. https://learn.microsoft.com/en-us/entra/identity/conditional-access/how-to-policy-mfa-device-register-join",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/how-to-policy-mfa-device-register-join:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-6-use-strong-authentication-controls",
+ "DefaultValue": "By default, `Require Multifactor Authentication to register or join devices with Microsoft Entra` is set to `No`."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3",
+ "Description": "Ensure that 'multifactor authentication' is 'enabled' For All Users",
+ "Checks": [
+ "entra_privileged_user_has_mfa",
+ "entra_non_privileged_user_has_mfa"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.1 Security Defaults (Per-User MFA)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'multifactor authentication' is 'enabled' For All Users",
+ "RationaleStatement": "Multifactor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Multifactor authentication provides additional assurance that the individual attempting to gain access is who they claim to be. With multifactor authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk.",
+ "ImpactStatement": "Users would require two forms of authentication before any access is granted. Additional administrative time will be required for managing dual forms of authentication when enabling multifactor authentication.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Manage`, click `Users`. 1. Click `Per-user MFA` from the top menu. 1. Click the box next to a user with `Status` `disabled`. 1. Click `Enable MFA`. 1. Click `Enable`. 1. Repeat steps 1-6 for each user requiring remediation. **Other options within Azure Portal** - [https://docs.microsoft.com/en-us/azure/active-directory/authentication/tutorial-enable-azure-mfa](https://docs.microsoft.com/en-us/azure/active-directory/authentication/tutorial-enable-azure-mfa) - [https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-mfasettings](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-mfasettings) - [https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-admin-mfa](https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-admin-mfa) - [https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-getstarted#enable-multi-factor-authentication-with-conditional-access](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-getstarted#enable-multi-factor-authentication-with-conditional-access)",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Manage`, click `Users`. 1. Click `Per-user MFA` from the top menu. 1. Ensure that `Status` is `enabled` for all users. **Audit from REST API** Run the following Graph PowerShell command: ``` get-mguser -All | where {$_.StrongAuthenticationMethods.Count -eq 0} | Select-Object -Property UserPrincipalName ``` If the output contains any `UserPrincipalName`, then this recommendation is non-compliant.",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/multi-factor-authentication/multi-factor-authentication:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mandatory-multifactor-authentication:https://azure.microsoft.com/en-us/blog/announcing-mandatory-multi-factor-authentication-for-azure-sign-in/:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-4-authenticate-server-and-services",
+ "DefaultValue": "Multifactor authentication is not enabled for all users by default. Starting in 2024, multifactor authentication is enabled for administrative accounts by default."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4",
+ "Description": "Ensure that 'Allow users to remember multifactor authentication on devices they trust' is Disabled",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.1 Security Defaults (Per-User MFA)",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'Allow users to remember multifactor authentication on devices they trust' is Disabled",
+ "RationaleStatement": "Remembering Multi-Factor Authentication (MFA) for devices and browsers allows users to have the option to bypass MFA for a set number of days after performing a successful sign-in using MFA. This can enhance usability by minimizing the number of times a user may need to perform two-step verification on the same device. However, if an account or device is compromised, remembering MFA for trusted devices may affect security. Hence, it is recommended that users not be allowed to bypass MFA.",
+ "ImpactStatement": "For every login attempt, the user will be required to perform multi-factor authentication.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, click `Users` 1. Click the `Per-user MFA` button on the top bar 1. Click on `Service settings` 1. Uncheck the box next to `Allow users to remember multi-factor authentication on devices they trust` 1. Click `Save`",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, click `Users` 1. Click the `Per-user MFA` button on the top bar 1. Click on `Service settings` 1. Ensure that `Allow users to remember multi-factor authentication on devices they trust` is not enabled",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-mfasettings#remember-multi-factor-authentication-for-devices-that-users-trust:https://docs.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-identity-management#im-4-use-strong-authentication-controls-for-all-azure-active-directory-based-access:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-6-use-strong-authentication-controls",
+ "DefaultValue": "By default, `Allow users to remember multi-factor authentication on devices they trust` is disabled."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.1",
+ "Description": "Ensure that Azure Admin Accounts Are Not Used for Daily Operations",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Azure Admin Accounts Are Not Used for Daily Operations",
+ "RationaleStatement": "Using admin accounts for daily operations increases the risk of accidental misconfigurations and security breaches.",
+ "ImpactStatement": "Minor administrative overhead includes managing separate accounts, enforcing stricter access controls, and potential licensing costs for advanced security features.",
+ "RemediationProcedure": "If admin accounts are being used for daily operations, consider the following: - Monitor and alert on unusual activity. - Enforce the principle of least privilege. - Revoke any unnecessary administrative access. - Use Conditional Access to limit access to resources. - Ensure that administrators have separate admin and user accounts. - Use Microsoft Entra ID Protection helps organizations detect, investigate, and remediate identity-based risks. - Use Privileged Identity Management (PIM) in Microsoft Entra ID to limit standing administrator access to privileged roles, discover who has access, and review privileged access.",
+ "AuditProcedure": "**Audit from Azure Portal** Monitor: 1. Go to `Monitor`. 1. Click `Activity log`. 1. Review the activity log and ensure that admin accounts are not being used for daily operations. Microsoft Entra ID: 1. Go to `Microsoft Entra ID`. 1. Under `Monitoring`, click `Sign-in logs`. 1. Review the sign-in logs and ensure that admin accounts are not being accessed more frequently than necessary.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/security/privileged-access-workstations/critical-impact-accounts",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.3.2",
+ "Description": "Ensure that Guest Users are Reviewed on a Regular Basis",
+ "Checks": [
+ "entra_policy_guest_users_access_restrictions"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Guest Users are Reviewed on a Regular Basis",
+ "RationaleStatement": "Guest users are typically added outside your employee on-boarding/off-boarding process and could potentially be overlooked indefinitely. To prevent this, guest users should be reviewed on a regular basis. During this audit, guest users should also be determined to not have administrative privileges.",
+ "ImpactStatement": "Before removing guest users, determine their use and scope. Like removing any user, there may be unforeseen consequences to systems if an account is removed without careful consideration.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, select `Users` 1. Click on `Add filter` 1. Select `User type` 1. Select `Guest` from the Value dropdown 1. Click `Apply` 1. Check the box next to all `Guest` users that are no longer required or are inactive 1. Click `Delete` 1. Click `OK` **Remediate from Azure CLI** Before deleting the user, set it to inactive using the ID from the Audit Procedure to determine if there are any dependent systems. ``` az ad user update --id <exampleaccountid@domain.com> --account-enabled {false} ``` After determining that there are no dependent systems, delete the user. ``` Remove-AzureADUser -ObjectId <exampleaccountid@domain.com> ``` **Remediate from Azure PowerShell** Before deleting the user, set it to inactive using the ID from the Audit Procedure to determine if there are any dependent systems. ``` Set-AzureADUser -ObjectId <exampleaccountid@domain.com> -AccountEnabled false ``` After determining that there are no dependent systems, delete the user. ``` PS C:\\>Remove-AzureADUser -ObjectId <exampleaccountid@domain.com> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Entra ID` 1. Under `Manage`, select `Users` 1. Click on `Add filter` 1. Select `User type` 1. Select `Guest` from the Value dropdown 1. Click `Apply` 1. Audit the listed guest users **Audit from Azure CLI** ``` az ad user list --query [?userType=='Guest'] ``` Ensure all users listed are still required and not inactive. **Audit from Azure PowerShell** ``` Get-AzureADUser |Where-Object {$_.UserType -like Guest} |Select-Object DisplayName, UserPrincipalName, UserType -Unique ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [e9ac8f8e-ce22-4355-8f04-99b911d6be52](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fe9ac8f8e-ce22-4355-8f04-99b911d6be52) **- Name:** 'Guest accounts with read permissions on Azure resources should be removed' - **Policy ID:** [94e1c2ac-cbbe-4cac-a2b5-389c812dee87](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F94e1c2ac-cbbe-4cac-a2b5-389c812dee87) **- Name:** 'Guest accounts with write permissions on Azure resources should be removed' - **Policy ID:** [339353f6-2387-4a45-abe4-7f529d121046](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F339353f6-2387-4a45-abe4-7f529d121046) **- Name:** 'Guest accounts with owner permissions on Azure resources should be removed'",
+ "AdditionalInformation": "It is good practice to use a dynamic security group to manage guest users. To create the dynamic security group: 1. Navigate to the 'Microsoft Entra ID' blade in the Azure Portal 2. Select the 'Groups' item 3. Create new 4. Type of 'dynamic' 5. Use the following dynamic selection rule. (user.userType -eq Guest) 6. Once the group has been created, select access reviews option and create a new access review with a period of monthly and send to relevant administrators for review.",
+ "References": "https://learn.microsoft.com/en-us/entra/external-id/user-properties:https://learn.microsoft.com/en-us/entra/fundamentals/how-to-create-delete-users#delete-a-user:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-4-review-and-reconcile-user-access-regularly:https://www.microsoft.com/en-us/security/business/identity-access-management/azure-ad-pricing:https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-manage-inactive-user-accounts:https://learn.microsoft.com/en-us/entra/fundamentals/users-restore",
+ "DefaultValue": "By default no guest users are created."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.3",
+ "Description": "Ensure That Use of the 'User Access Administrator' Role is Restricted",
+ "Checks": [
+ "iam_role_user_access_admin_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Use of the 'User Access Administrator' Role is Restricted",
+ "RationaleStatement": "The User Access Administrator role provides extensive access control privileges. Unnecessary assignments heighten the risk of privilege escalation and unauthorized access. Removing the role immediately after use minimizes security exposure.",
+ "ImpactStatement": "Increased administrative effort to manage and remove role assignments appropriately.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Subscriptions`. 1. Select a subscription. 1. Select `Access control (IAM)`. 1. Look for the following banner at the top of the page: `Action required: X users have elevated access in your tenant. You should take immediate action and remove all role assignments with elevated access.` 1. Click `View role assignments`. 1. Click `Remove`. **Remediate from Azure CLI** Run the following command: ``` az role assignment delete --role User Access Administrator --scope / ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Subscriptions`. 1. Select a subscription. 1. Select `Access control (IAM)`. 1. Look for the following banner at the top of the page: `Action required: X users have elevated access in your tenant. You should take immediate action and remove all role assignments with elevated access.` If the banner is displayed, the `User Access Administrator` is assigned. **Audit from Azure CLI** Run the following command: ``` az role assignment list --role User Access Administrator --scope / ``` Ensure that the command does not return any `User Access Administrator` role assignment information.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles:https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.3.4",
+ "Description": "Ensure that All 'Privileged' Role Assignments are Periodically Reviewed",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that All 'Privileged' Role Assignments are Periodically Reviewed",
+ "RationaleStatement": "Privileged roles are crown jewel assets that can be used by malicious insiders, threat actors, and even through mistake to significantly damage an organization. These roles should be periodically reviewed to identify lingering permissions assignment and detect lateral movement through privilege escalation.",
+ "ImpactStatement": "Increased administrative effort to manage and remove role assignments appropriately.",
+ "RemediationProcedure": "Review privileged role assignments and remove any that are no longer necessary or appropriate. Use Azure PIM (Privileged Identity Management) to implement just-in-time access for privileged roles.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 2. Select `Subscriptions`. 3. Select a subscription. 4. Select `Access control (IAM)`. 5. Look for the number under the word `Privileged` accompanied by a link titled `View Assignments`. Click the `View assignments` link. 6. For each privileged role listed, evaluate whether the assignment is appropriate and current for each User, Group, or App assigned to each privileged role. NOTE: Determining 'appropriate' assignments requires a clear understanding of your organization's personnel, systems, policy, and security requirements.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.3.5",
+ "Description": "Ensure Disabled User Accounts do not Have Read, Write, or Owner Permissions",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Disabled User Accounts do not Have Read, Write, or Owner Permissions",
+ "RationaleStatement": "Disabled accounts should not retain access to resources, as this poses a security risk. Removing role assignments mitigates potential unauthorized access and enforces the principle of least privilege.",
+ "ImpactStatement": "Ensure disabled accounts are not relied on for break glass or automated processes before removing roles to avoid service disruption.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Entra ID`. 2. Under `Manage`, click `Users`. 3. Click `Add filter`. 4. Click `Account enabled`. 5. Click the toggle switch to set the value to `No`. 6. Click `Apply`. 7. Click the `Display name` of a disabled user account with read, write, or owner roles assigned. 8. Click `Azure role assignments`. 9. Click the name of a read, write, or owner role. 10. Click `Assignments`. 11. Click `Remove` in the row for the disabled user account. 12. Click `Yes`. 13. Repeat steps 7-12 for disabled user accounts requiring remediation. **Remediate from PowerShell** ``` Remove-AzRoleAssignment -ObjectId $user.ObjectId -RoleDefinitionName <role-definition-name> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Entra ID`. 2. Under `Manage`, click `Users`. 3. Click `Add filter`. 4. Click `Account enabled`. 5. Click the toggle switch to set the value to `No`. 6. Click `Apply`. 7. Click the `Display name` of a disabled user account. 8. Click `Azure role assignments`. 9. Ensure that no read, write, or owner roles are assigned to the user account. 10. Repeat steps 7-9 for each disabled user account. **Audit from PowerShell** ``` Connect-AzureAD Get-AzureADUser $user = Get-AzureADUser -ObjectId <object-id> $user.AccountEnabled ``` If AccountEnabled is False, run: ``` Get-AzRoleAssignment -ObjectId $user.ObjectId ``` **Audit from Azure Policy** - **Policy ID:** [0cfea604-3201-4e14-88fc-fae4c427a6c5] - Name: 'Blocked accounts with owner permissions on Azure resources should be removed' - **Policy ID:** [8d7e1fde-fe26-4b5f-8108-f8e432cbc2be] - Name: 'Blocked accounts with read and write permissions on Azure resources should be removed'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/az.resources/get-azaduser:https://learn.microsoft.com/en-us/powershell/module/az.resources/get-azroleassignment:https://learn.microsoft.com/en-us/powershell/module/az.resources/remove-azroleassignment",
+ "DefaultValue": "Disabled user accounts retain their prior role assignments."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.6",
+ "Description": "Ensure 'Tenant Creator' Role Assignments are Periodically Reviewed",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure 'Tenant Creator' Role Assignments are Periodically Reviewed",
+ "RationaleStatement": "Unnecessary assignments increase the risk of privilege escalation and unauthorized access. This recommendation should be applied alongside the recommendation 'Ensure that Restrict non-admin users from creating tenants is set to Yes'.",
+ "ImpactStatement": "Verify that the Tenant Creator role is no longer required by any assignments before removal to avoid disruption of critical functions.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Entra ID`. 2. Under `Manage`, click `Roles and administrators`. 3. In the search bar, type `Tenant Creator`. 4. Click the role. 5. Click the name of an assignment. 6. Check the box next to the `Tenant Creator` role. 7. Click `X Remove assignments`. 8. Click `Yes`. 9. Repeat steps 1-8 for each assignment requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Entra ID`. 2. Under `Manage`, click `Roles and administrators`. 3. In the search bar, type `Tenant Creator`. 4. Click the role. 5. Review the assignments and ensure that they are appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-check-tenant-creation-permission:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#tenant-creator",
+ "DefaultValue": "The Tenant Creator role is not assigned by default."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.7",
+ "Description": "Ensure All Non-privileged Role Assignments are Periodically Reviewed",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "SubSection": "5.3 Periodic Identity Reviews",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure All Non-privileged Role Assignments are Periodically Reviewed",
+ "RationaleStatement": "To ensure the principle of least privilege is followed, non-privileged role assignments should be reviewed periodically to confirm that users are granted only the minimum level of permissions they need to perform their tasks.",
+ "ImpactStatement": "Increased administrative effort to manage and remove role assignments appropriately.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Subscriptions`. 2. Click the name of a subscription. 3. Click `Access control (IAM)`. 4. Click `Role assignments`. 5. Click `Job function roles`. 6. Check the box next to any inappropriate assignments. 7. Click `Delete`. 8. Click `Yes`. 9. Repeat steps 1-8 for each subscription.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Subscriptions`. 2. Click the name of a subscription. 3. Click `Access control (IAM)`. 4. Click `Role assignments`. 5. Click `Job function roles`. 6. For each role, ensure the assignments are appropriate. 7. Repeat steps 1-6 for each subscription.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments",
+ "DefaultValue": "Users do not have non-privileged roles assigned to them by default."
+ }
+ ]
+ },
+ {
+ "Id": "5.4",
+ "Description": "Ensure that No Custom Subscription Administrator Roles Exist",
+ "Checks": [
+ "iam_subscription_roles_owner_custom_not_created"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that No Custom Subscription Administrator Roles Exist",
+ "RationaleStatement": "Custom roles in Azure with administrative access can obfuscate the permissions granted and introduce complexity and blind spots to the management of privileged identities. For less mature security programs without regular identity audits, the creation of Custom roles should be avoided entirely. For more mature security programs with regular identity audits, Custom Roles should be audited for use and assignment, used minimally, and the principle of least privilege should be observed when granting permissions",
+ "ImpactStatement": "Subscriptions will need to be handled by Administrators with permissions.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Subscriptions`. 1. Select a subscription. 1. Select `Access control (IAM)`. 1. Select `Roles`. 1. Click `Type` and select `Custom role` from the drop-down menu. 1. Check the box next to each role which grants subscription administrator privileges. 1. Select `Delete`. 1. Select `Yes`. **Remediate from Azure CLI** List custom roles: ``` az role definition list --custom-role-only True ``` Check for entries with `assignableScope` of the `subscription`, and an action of `*`. To remove a violating role: ``` az role definition delete --name <role name> ``` Note that any role assignments must be removed before a custom role can be deleted. Ensure impact is assessed before deleting a custom role granting subscription administrator privileges.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Subscriptions`. 1. Select a subscription. 1. Select `Access control (IAM)`. 1. Select `Roles`. 1. Click `Type` and select `Custom role` from the drop-down menu. 1. Select `View` next to a role. 1. Select `JSON`. 1. Check for `assignableScopes` set to the subscription, and `actions` set to `*`. 1. Repeat steps 7-9 for each custom role. **Audit from Azure CLI** List custom roles: ``` az role definition list --custom-role-only True ``` Check for entries with `assignableScope` of the `subscription`, and an action of `*` **Audit from PowerShell** ``` Connect-AzAccount Get-AzRoleDefinition |Where-Object {($_.IsCustom -eq $true) -and ($_.Actions.contains('*'))} ``` Check the output for `AssignableScopes` value set to the subscription. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [a451c1ef-c6ca-483d-87ed-f49761e3ffb5](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fa451c1ef-c6ca-483d-87ed-f49761e3ffb5) **- Name:** 'Audit usage of custom RBAC roles'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/billing/billing-add-change-azure-subscription-administrator:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-1-separate-and-limit-highly-privilegedadministrative-users:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-3-manage-lifecycle-of-identities-and-entitlements:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-2-define-and-implement-enterprise-segmentationseparation-of-duties-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-6-define-and-implement-identity-and-privileged-access-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-7-follow-just-enough-administration-least-privilege-principle",
+ "DefaultValue": "By default, no custom owner roles are created."
+ }
+ ]
+ },
+ {
+ "Id": "5.5",
+ "Description": "Ensure that a Custom Role is Assigned Permissions for Administering Resource Locks",
+ "Checks": [
+ "iam_custom_role_has_permissions_to_administer_resource_locks"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that a Custom Role is Assigned Permissions for Administering Resource Locks",
+ "RationaleStatement": "Given that the resource lock functionality is outside of standard Role-Based Access Control (RBAC), it would be prudent to create a resource lock administrator role to prevent inadvertent unlocking of resources.",
+ "ImpactStatement": "By adding this role, specific permissions may be granted for managing only resource locks rather than needing to provide the broad Owner or User Access Administrator role, reducing the risk of the user being able to cause unintentional damage.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. In the Azure portal, navigate to a subscription or resource group. 1. Click `Access control (IAM)`. 1. Click `+ Add`. 1. Click `Add custom role`. 1. In the `Custom role name` field enter `Resource Lock Administrator`. 1. In the `Description` field enter `Can Administer Resource Locks`. 1. For `Baseline permissions` select `Start from scratch`. 1. Click `Next`. 1. Click `Add permissions`. 1. In the `Search for a permission` box, type `Microsoft.Authorization/locks`. 1. Click the result. 1. Check the box next to `Permission`. 1. Click `Add`. 1. Click `Review + create`. 1. Click `Create`. 1. Click `OK`. 1. Click `+ Add`. 1. Click `Add role assignment`. 1. In the `Search by role name, description, permission, or ID` box, type `Resource Lock Administrator`. 1. Select the role. 1. Click `Next`. 1. Click `+ Select members`. 1. Select appropriate members. 1. Click `Select`. 1. Click `Review + assign`. 1. Click `Review + assign` again. 1. Repeat steps 1-26 for each subscription or resource group requiring remediation. **Remediate from PowerShell:** Below is a PowerShell definition for a resource lock administrator role created at an Azure Management group level ``` Import-Module Az.Accounts Connect-AzAccount $role = Get-AzRoleDefinition User Access Administrator $role.Id = $null $role.Name = Resource Lock Administrator $role.Description = Can Administer Resource Locks $role.Actions.Clear() $role.Actions.Add(Microsoft.Authorization/locks/*) $role.AssignableScopes.Clear() * Scope at the Management group level Management group $role.AssignableScopes.Add(/providers/Microsoft.Management/managementGroups/MG-Name) New-AzRoleDefinition -Role $role Get-AzureRmRoleDefinition Resource Lock Administrator ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. In the Azure portal, navigate to a subscription or resource group. 1. Click `Access control (IAM)`. 1. Click `Roles`. 1. Click `Type : All`. 1. Click to view the drop-down menu. 1. Select `Custom role`. 1. Click `View` in the `Details` column of a custom role. 1. Review the role permissions. 1. Click `Assignments` and review the assignments. 1. Click the `X` to exit the custom role details page. 1. Repeat steps 7-10. Ensure that at least one custom role exists that assigns the `Microsoft.Authorization/locks` permission to appropriate members. 1. Repeat steps 1-11 for each subscription or resource group.",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles:https://docs.microsoft.com/en-us/azure/role-based-access-control/check-access:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-1-separate-and-limit-highly-privilegedadministrative-users:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-7-follow-just-enough-administration-least-privilege-principle:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-3-manage-lifecycle-of-identities-and-entitlements:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-2-define-and-implement-enterprise-segmentationseparation-of-duties-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-6-define-and-implement-identity-and-privileged-access-strategy",
+ "DefaultValue": "A role for administering resource locks does not exist by default."
+ }
+ ]
+ },
+ {
+ "Id": "5.6",
+ "Description": "Ensure that 'Subscription leaving Microsoft Entra tenant' and 'Subscription entering Microsoft Entra tenant' is set to 'Permit no one'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'Subscription leaving Microsoft Entra tenant' and 'Subscription entering Microsoft Entra tenant' is set to 'Permit no one'",
+ "RationaleStatement": "Permissions to move subscriptions in and out of a Microsoft Entra tenant must only be given to appropriate administrative personnel. A subscription that is moved into a Microsoft Entra tenant may be within a folder to which other users have elevated permissions. This prevents loss of data or unapproved changes of the objects within by potential bad actors.",
+ "ImpactStatement": "Subscriptions will need to have these settings turned off to be moved.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From the Azure Portal Home select the portal menu 1. Select `Subscriptions` 1. In the `Advanced options` drop-down menu, select `Manage Policies` 1. Set `Subscription leaving Microsoft Entra tenant` and `Subscription entering Microsoft Entra tenant` to `Permit no one` 1. Click `Save changes`",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From the Azure Portal Home select the portal menu 1. Select `Subscriptions` 1. In the `Advanced options` drop-down menu, select `Manage Policies` 1. Ensure `Subscription leaving Microsoft Entra tenant` and `Subscription entering Microsoft Entra tenant` are set to `Permit no one`",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/manage-azure-subscription-policy:https://learn.microsoft.com/en-us/entra/fundamentals/how-subscriptions-associated-directory:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-2-protect-identity-and-authentication-systems",
+ "DefaultValue": "By default `Subscription leaving Microsoft Entra tenant` and `Subscription entering Microsoft Entra tenant` are set to `Allow everyone (default)`"
+ }
+ ]
+ },
+ {
+ "Id": "5.7",
+ "Description": "Ensure there are between 2 and 3 Subscription Owners",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Identity Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure there are between 2 and 3 Subscription Owners",
+ "RationaleStatement": "If groups are used, ensure their membership is tightly controlled and regularly reviewed to avoid privilege sprawl. This includes user accounts, Entra ID groups, service principals, and managed identities.",
+ "ImpactStatement": "Implementation may require changes in administrative workflows or the redistribution of roles and responsibilities.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Subscriptions`. 2. Click the name of a subscription. 3. Click `Access Controls (IAM)`. 4. Click `Role assignments`. 5. Click `Role : All`. 6. Click `Owner`. 7. Check the box next to members from whom the owner role should be removed. 8. Click `Delete`. 9. Click `Yes`. 10. Repeat for each subscription requiring remediation. **Remediate from Azure CLI** ``` az role assignment delete --ids <role-assignment-ids> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Subscriptions`. 2. Click the name of a subscription. 3. Click `Access Controls (IAM)`. 4. Click `Role assignments`. 5. Click `Role : All`. 6. Click the arrow next to `All`. 7. Click `Owner`. 8. Ensure a minimum of 2 and a maximum of 3 members are returned. 9. Repeat steps 1-8 for each subscription. **Audit from Azure CLI** ``` az role assignment list --role Owner --scope /subscriptions/<subscription-id> --query \"[].{PrincipalName:principalName, Type:principalType}\" ``` Ensure a minimum of 2 and a maximum of 3 members are returned. **Audit from PowerShell** ``` Get-AzRoleAssignment -RoleDefinitionName Owner -Scope /subscriptions/<subscription-id> ``` **Audit from Azure Policy** - **Policy ID:** [09024ccc-0c5f-475e-9457-b7c0d9ed487b] - Name: 'There should be more than one owner assigned to your subscription' - **Policy ID:** [4f11b553-d42e-4e3a-89be-32ca364cad4c] - Name: 'A maximum of 3 owners should be designated for your subscription'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/cli/azure/role/assignment:https://learn.microsoft.com/en-us/powershell/module/az.resources/get-azroleassignment:https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/privileged#owner",
+ "DefaultValue": "A subscription has 1 owner by default."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.1",
+ "Description": "Ensure that a 'Diagnostic Setting' Exists for Subscription Activity Logs",
+ "Checks": [
+ "monitor_diagnostic_settings_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that a 'Diagnostic Setting' Exists for Subscription Activity Logs",
+ "RationaleStatement": "A diagnostic setting controls how a diagnostic log is exported. By default, logs are retained only for 90 days. Diagnostic settings should be defined so that logs can be exported and stored for a longer duration to analyze security activities within an Azure subscription.",
+ "ImpactStatement": "Diagnostic settings incur costs based on the amount of data collected and the destination.",
+ "RemediationProcedure": "**Remediate from Azure Portal** To enable Diagnostic Settings on a Subscription: 1. Go to `Monitor` 2. Click on `Activity log` 3. Click on `Export Activity Logs` 4. Click `+ Add diagnostic setting` 5. Enter a `Diagnostic setting name` 6. Select `Categories` for the diagnostic setting 7. Select the appropriate `Destination details` (this may be Log Analytics, Storage Account, Event Hub, or Partner solution) 8. Click `Save` To enable Diagnostic Settings on a specific resource: 1. Go to `Monitoring` 1. Click `Diagnostic settings` 1. Select `Add diagnostic setting` 1. Enter a `Diagnostic setting name` 1. Select the appropriate log, metric, and destination (this may be Log Analytics, Storage Account, Event Hub, or Partner solution) 1. Click `Save` Repeat these step for all resources as needed. **Remediate from Azure CLI** To configure Diagnostic Settings on a Subscription: ``` az monitor diagnostic-settings subscription create --subscription <subscription id> --name <diagnostic settings name> --location <location> <[--event-hub <event hub ID> --event-hub-auth-rule <event hub auth rule ID>] [--storage-account <storage account ID>] [--workspace <log analytics workspace ID>] --logs <JSON encoded categories> (e.g. [{category:Security,enabled:true},{category:Administrative,enabled:true},{category:Alert,enabled:true},{category:Policy,enabled:true}]) ``` To configure Diagnostic Settings on a specific resource: ``` az monitor diagnostic-settings create --subscription <subscription ID> --resource <resource ID> --name <diagnostic settings name> <[--event-hub <event hub ID> --event-hub-rule <event hub auth rule ID>] [--storage-account <storage account ID>] [--workspace <log analytics workspace ID>] --logs <resource specific JSON encoded log settings> --metrics <metric settings (shorthand|json-file|yaml-file)> ``` **Remediate from PowerShell** To configure Diagnostic Settings on a subscription: ``` $logCategories = @(); $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Administrative -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Security -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category ServiceHealth -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Alert -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Recommendation -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Policy -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Autoscale -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category ResourceHealth -Enabled $true New-AzSubscriptionDiagnosticSetting -SubscriptionId <subscription ID> -Name <Diagnostic settings name> <[-EventHubAuthorizationRule <event hub auth rule ID> -EventHubName <event hub name>] [-StorageAccountId <storage account ID>] [-WorkSpaceId <log analytics workspace ID>] [-MarketplacePartner ID <full ARM Marketplace resource ID>]> -Log $logCategories ``` To configure Diagnostic Settings on a specific resource: ``` $logCategories = @() $logCategories += New-AzDiagnosticSettingLogSettingsObject -Category <resource specific log category> -Enabled $true Repeat command and variable assignment for each Log category specific to the resource where this Diagnostic Setting will get configured. $metricCategories = @() $metricCategories += New-AzDiagnosticSettingMetricSettingsObject -Enabled $true [-Category <resource specific metric category | AllMetrics>] [-RetentionPolicyDay <Integer>] [-RetentionPolicyEnabled $true] Repeat command and variable assignment for each Metric category or use the 'AllMetrics' category. New-AzDiagnosticSetting -ResourceId <resource ID> -Name <Diagnostic settings name> -Log $logCategories -Metric $metricCategories [-EventHubAuthorizationRuleId <event hub auth rule ID> -EventHubName <event hub name>] [-StorageAccountId <storage account ID>] [-WorkspaceId <log analytics workspace ID>] [-MarketplacePartnerId <full ARM marketplace resource ID>]>",
+ "AuditProcedure": "**Audit from Azure Portal** To identify Diagnostic Settings on a subscription: 1. Go to `Monitor` 2. Click `Activity Log` 3. Click `Export Activity Logs` 4. Select a `Subscription` 5. Ensure a `Diagnostic setting` exists for the selected Subscription To identify Diagnostic Settings on specific resources: 1. Go to `Monitoring` 2. Click `Diagnostic settings` 3. Ensure a `Diagnostic setting` exists for all appropriate resources. **Audit from Azure CLI** To identify Diagnostic Settings on a subscription: ``` az monitor diagnostic-settings subscription list --subscription <subscription ID> ``` To identify Diagnostic Settings on a resource ``` az monitor diagnostic-settings list --resource <resource Id> ``` **Audit from PowerShell** To identify Diagnostic Settings on a Subscription: ``` Get-AzDiagnosticSetting -SubscriptionId <subscription ID> ``` To identify Diagnostic Settings on a specific resource: ``` Get-AzDiagnosticSetting -ResourceId <resource ID> ```",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-activity-logs#export-the-activity-log-with-a-log-profile:https://learn.microsoft.com/en-us/cli/azure/monitor/diagnostic-settings?view=azure-cli-latest:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, diagnostic setting is not set."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.2",
+ "Description": "Ensure Diagnostic Setting Captures Appropriate Categories",
+ "Checks": [
+ "monitor_diagnostic_setting_with_appropriate_categories"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Diagnostic Setting Captures Appropriate Categories",
+ "RationaleStatement": "A diagnostic setting controls how the diagnostic log is exported. Capturing the diagnostic setting categories for appropriate control/management plane activities allows proper alerting.",
+ "ImpactStatement": "Enabling additional categories may increase storage costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Monitor`. 1. Click `Activity log`. 1. Click on `Export Activity Logs`. 1. Select the `Subscription` from the drop down menu. 1. Click `Edit setting` next to a diagnostic setting. 1. Check the following categories: `Administrative, Alert, Policy, and Security`. 1. Choose the destination details according to your organization's needs. 1. Click `Save`. **Remediate from Azure CLI** ``` az monitor diagnostic-settings subscription create --subscription <subscription id> --name <diagnostic settings name> --location <location> <[--event-hub <event hub ID> --event-hub-auth-rule <event hub auth rule ID>] [--storage-account <storage account ID>] [--workspace <log analytics workspace ID>] --logs [{category:Security,enabled:true},{category:Administrative,enabled:true},{category:Alert,enabled:true},{category:Policy,enabled:true}] ``` **Remediate from PowerShell** ``` $logCategories = @(); $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Administrative -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Security -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Alert -Enabled $true $logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Policy -Enabled $true New-AzSubscriptionDiagnosticSetting -SubscriptionId <subscription ID> -Name <Diagnostic settings name> <[-EventHubAuthorizationRule <event hub auth rule ID> -EventHubName <event hub name>] [-StorageAccountId <storage account ID>] [-WorkSpaceId <log analytics workspace ID>] [-MarketplacePartner ID <full ARM Marketplace resource ID>]> -Log $logCategories ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Monitor`. 1. Click `Activity log`. 1. Click on `Export Activity Logs`. 1. Select the appropriate `Subscription`. 1. Click `Edit setting` next to a diagnostic setting. 1. Ensure that the following categories are checked: `Administrative, Alert, Policy, and Security`. **Audit from Azure CLI** Ensure the categories `'Administrative', 'Alert', 'Policy', and 'Security'` set to: 'enabled: true' ``` az monitor diagnostic-settings subscription list --subscription <subscription ID> ``` **Audit from PowerShell** Ensure the categories Administrative, Alert, Policy, and Security are set to Enabled:True ``` Get-AzSubscriptionDiagnosticSetting -Subscription <subscriptionID> ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [3b980d31-7904-4bb7-8575-5665739a8052](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F3b980d31-7904-4bb7-8575-5665739a8052) **- Name:** 'An activity log alert should exist for specific Security operations' - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations' - **Policy ID:** [c5447c04-a4d7-4ba8-a263-c9ee321a6858](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc5447c04-a4d7-4ba8-a263-c9ee321a6858) **- Name:** 'An activity log alert should exist for specific Policy operations'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings:https://docs.microsoft.com/en-us/azure/azure-monitor/samples/resource-manager-diagnostic-settings:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation:https://learn.microsoft.com/en-us/cli/azure/monitor/diagnostic-settings?view=azure-cli-latest:https://learn.microsoft.com/en-us/powershell/module/az.monitor/new-azsubscriptiondiagnosticsetting?view=azps-9.2.0",
+ "DefaultValue": "When the diagnostic setting is created using Azure Portal, by default no categories are selected."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.3",
+ "Description": "Ensure the Storage Account Containing the Container with Activity Logs is Encrypted with Customer-managed Key (CMK)",
+ "Checks": [
+ "monitor_storage_account_with_activity_logs_cmk_encrypted"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure the Storage Account Containing the Container with Activity Logs is Encrypted with Customer-managed Key (CMK)",
+ "RationaleStatement": "Configuring the storage account with the activity log export container to use CMKs provides additional confidentiality controls on log data, as a given user must have read permission on the corresponding storage account and must be granted decrypt permission by the CMK.",
+ "ImpactStatement": "**NOTE:** You must have your key vault setup to utilize this. All Audit Logs will be encrypted with a key you provide. You will need to set up customer managed keys separately, and you will select which key to use via the instructions here. You will be responsible for the lifecycle of the keys, and will need to manually replace them at your own determined intervals to keep the data secure.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Monitor`. 1. Select `Activity log`. 1. Select `Export Activity Logs`. 1. Select a `Subscription`. 1. Note the name of the `Storage Account` for the diagnostic setting. 1. Navigate to `Storage accounts`. 1. Click on the storage account. 1. Under `Security + networking`, click `Encryption`. 1. Next to `Encryption type`, select `Customer-managed keys`. 1. Complete the steps to configure a customer-managed key for encryption of the storage account. **Remediate from Azure CLI** ``` az storage account update --name <name of the storage account> --resource-group <resource group for a storage account> --encryption-key-source=Microsoft.Keyvault --encryption-key-vault <Key Vault URI> --encryption-key-name <KeyName> --encryption-key-version <Key Version> ``` **Remediate from PowerShell** ``` Set-AzStorageAccount -ResourceGroupName <resource group name> -Name <storage account name> -KeyvaultEncryption -KeyVaultUri <key vault URI> -KeyName <key name> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Monitor`. 1. Select `Activity log`. 1. Select `Export Activity Logs`. 1. Select a `Subscription`. 1. Note the name of the `Storage Account` for the diagnostic setting. 1. Navigate to `Storage accounts`. 1. Click on the storage account name noted in Step 5. 1. Under `Security + networking`, click `Encryption`. 1. Ensure `Customer-managed keys` is selected and a key is set. **Audit from Azure CLI** 1. Get storage account id configured with log profile: ``` az monitor diagnostic-settings subscription list --subscription <subscription id> --query 'value[*].storageAccountId' ``` 2. Ensure the storage account is encrypted with CMK: ``` az storage account list --query [?name=='<Storage Account Name>'] ``` In command output ensure `keySource` is set to `Microsoft.Keyvault` and `keyVaultProperties` is not set to `null` **Audit from PowerShell** ``` Get-AzStorageAccount -ResourceGroupName <resource group name> -Name <storage account name>|select-object -ExpandProperty encryption|format-list ``` Ensure the value of `KeyVaultProperties` is not `null` or empty, and ensure `KeySource` is not set to `Microsoft.Storage`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [fbb99e8e-e444-4da0-9ff1-75c92f5a85b2](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ffbb99e8e-e444-4da0-9ff1-75c92f5a85b2) **- Name:** 'Storage account containing the container with activity logs must be encrypted with BYOK'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-5-use-customer-managed-key-option-in-data-at-rest-encryption-when-required:https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log?tabs=cli#managing-legacy-log-profiles",
+ "DefaultValue": "By default, for a storage account `keySource` is set to `Microsoft.Storage` allowing encryption with vendor Managed key and not a Customer Managed Key."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.4",
+ "Description": "Ensure that Logging for Azure Key Vault is 'Enabled'",
+ "Checks": [
+ "keyvault_logging_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Logging for Azure Key Vault is 'Enabled'",
+ "RationaleStatement": "Monitoring how and when key vaults are accessed, and by whom, enables an audit trail of interactions with confidential information, keys, and certificates managed by Azure Key Vault. Enabling logging for Key Vault saves information in a user provided destination of either an Azure storage account or Log Analytics workspace. The same destination can be used for collecting logs for multiple Key Vaults.",
+ "ImpactStatement": "Enabling logging incurs costs based on the volume of logs generated.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. Select a Key vault. 3. Under `Monitoring`, select `Diagnostic settings`. 4. Click `Edit setting` to update an existing diagnostic setting, or `Add diagnostic setting` to create a new one. 5. If creating a new diagnostic setting, provide a name. 6. Configure an appropriate destination. 7. Under `Category groups`, check `audit` and `allLogs`. 8. Click `Save`. **Remediate from Azure CLI** To update an existing `Diagnostic Settings` ``` az monitor diagnostic-settings update --name <diagnostic_setting_name> --resource <key_vault_id> ``` To create a new `Diagnostic Settings` ``` az monitor diagnostic-settings create --name <diagnostic_setting_name> --resource <key_vault_id> --logs [{category:audit,enabled:true},{category:allLogs,enabled:true}] --metrics [{category:AllMetrics,enabled:true}] <[--event-hub <event_hub_ID> --event-hub-rule <event_hub_auth_rule_ID> | --storage-account <storage_account_ID> |--workspace <log_analytics_workspace_ID> | --marketplace-partner-id <solution_resource_ID>]> ``` **Remediate from PowerShell** Create the `Log` settings object ``` $logSettings = @() $logSettings += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -Category audit $logSettings += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -Category allLogs ``` Create the `Metric` settings object ``` $metricSettings = @() $metricSettings += New-AzDiagnosticSettingMetricSettingsObject -Enabled $true -Category AllMetrics ``` Create the `Diagnostic Settings` for each `Key Vault` ``` New-AzDiagnosticSetting -Name <diagnostic_setting_name> -ResourceId <key_vault_id> -Log $logSettings -Metric $metricSettings [-StorageAccountId <storage_account_ID> | -EventHubName <event_hub_name> -EventHubAuthorizationRuleId <event_hub_auth_rule_ID> | -WorkSpaceId <log analytics workspace ID> | -MarketPlacePartnerId <full resource ID for third-party solution>] ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 1. For each Key vault, under `Monitoring`, go to `Diagnostic settings`. 1. Click `Edit setting` next to a diagnostic setting. 1. Ensure that a destination is configured. 1. Under `Category groups`, ensure that `audit` and `allLogs` are checked. **Audit from Azure CLI** List all key vaults ``` az keyvault list ``` For each keyvault `id` ``` az monitor diagnostic-settings list --resource <id> ``` Ensure that `storageAccountId` reflects your desired destination and that `categoryGroup` and `enabled` are set as follows in the sample outputs below. ``` logs: [ { categoryGroup: audit, enabled: true, }, { categoryGroup: allLogs, enabled: true, } ``` **Audit from PowerShell** List the key vault(s) in the subscription ``` Get-AzKeyVault ``` For each key vault, run the following: ``` Get-AzDiagnosticSetting -ResourceId <key_vault_id> ``` Ensure that `StorageAccountId`, `ServiceBusRuleId`, `MarketplacePartnerId`, or `WorkspaceId` is set as appropriate. Also, ensure that `enabled` is set to `true`, and that `categoryGroup` reflects both `audit` and `allLogs` category groups. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [cf820ca0-f99e-4f3e-84fb-66e913812d21](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fcf820ca0-f99e-4f3e-84fb-66e913812d21) **- Name:** 'Resource logs in Key Vault should be enabled'",
+ "AdditionalInformation": "**DEPRECATION WARNING** Retention rules for Key Vault logging is being migrated to Azure Storage Lifecycle Management. Retention rules should be set based on the needs of your organization and security or compliance frameworks. Please visit [https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy?tabs=portal](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy?tabs=portal) for detail on migrating your retention rules. Microsoft has provided the following deprecation timeline: March 31, 2023 – The Diagnostic Settings Storage Retention feature will no longer be available to configure new retention rules for log data. This includes using the portal, CLI PowerShell, and ARM and Bicep templates. If you have configured retention settings, you'll still be able to see and change them in the portal. March 31, 2024 – You will no longer be able to use the API (CLI, Powershell, or templates), or Azure portal to configure retention setting unless you're changing them to 0. Existing retention rules will still be respected. September 30, 2025 – All retention functionality for the Diagnostic Settings Storage Retention feature will be disabled across all environments.",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/general/howto-logging:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-8-ensure-security-of-key-and-certificate-repository:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, Diagnostic AuditEvent logging is not enabled for Key Vault instances."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.5",
+ "Description": "Ensure that Network Security Group Flow Logs are Captured and Sent to Log Analytics",
+ "Checks": [
+ "network_flow_log_captured_sent"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Network Security Group Flow Logs are Captured and Sent to Log Analytics",
+ "RationaleStatement": "Network Flow Logs provide valuable insight into the flow of traffic around your network and feed into both Azure Monitor and Azure Sentinel (if in use), permitting the generation of visual flow diagrams to aid with analyzing for lateral movement, etc.",
+ "ImpactStatement": "The impact of configuring NSG Flow logs is primarily one of cost and configuration. If deployed, it will create storage accounts that hold minimal amounts of data on a 5-day lifecycle before feeding to Log Analytics Workspace. This will increase the amount of data stored and used by Azure Monitor.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Existing NSG flow logs can still be reviewed under `Network Watcher` > `Flow logs`. If you already have NSG flow logs configured, ensure they remain enabled and that `Traffic Analytics` sends data to a `Log Analytics Workspace` until migration is complete. Azure no longer allows creation of new NSG flow logs after June 30, 2025. For new or migrated deployments, create `Virtual network` flow logs instead: 1. Navigate to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Select `+ Create`. 1. Select the desired Subscription. 1. For `Flow log type`, select `Virtual network`. 1. Select `+ Select target resource`. 1. Select `Virtual network`. 1. Select a virtual network. 1. Click `Confirm selection`. 1. Select or create a new Storage Account. 1. If using a v2 storage account, input the retention in days to retain the log. 1. Click `Next`. 1. Under `Analytics`, for `Flow log version`, select `Version 2`. 1. Check the box next to `Enable traffic analytics`. 1. Select a processing interval. 1. Select a `Log Analytics Workspace`. 1. Select `Next`. 1. Optionally add Tags. 1. Select `Review + create`. 1. Select `Create`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down, select `Flow log type`. 1. Review existing `Network security group` flow logs, if any remain, to ensure they are enabled and configured to send logs to a `Log Analytics Workspace`. 1. Review `Virtual network` flow logs for new or migrated coverage. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [27960feb-a23c-4577-8d36-ef8b5f35e0be](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F27960feb-a23c-4577-8d36-ef8b5f35e0be) **- Name:** 'All flow log resources should be in enabled state' - **Policy ID:** [c251913d-7d24-4958-af87-478ed3b9ba41](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc251913d-7d24-4958-af87-478ed3b9ba41) **- Name:** 'Flow logs should be configured for every network security group' - **Policy ID:** [4c3c6c5f-0d47-4402-99b8-aa543dd8bcee](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F4c3c6c5f-0d47-4402-99b8-aa543dd8bcee) **- Name:** 'Flow logs should be configured for every virtual network'",
+ "AdditionalInformation": "On September 30, 2027, NSG flow logs will be retired, and creating new NSG flow logs has not been possible since June 30, 2025. Azure recommends migrating to virtual network flow logs, which address NSG flow log limitations. After retirement, traffic analytics using NSG flow logs will no longer be supported, and existing NSG flow log resources will be deleted. Previously collected NSG flow log records will remain available per their retention policies. For details, see the official announcement: https://azure.microsoft.com/en-gb/updates?id=Azure-NSG-flow-logs-Retirement.",
+ "References": "https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-nsg-flow-logging-portal:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-4-enable-network-logging-for-security-investigation",
+ "DefaultValue": "By default Network Security Group logs are not sent to Log Analytics."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.6",
+ "Description": "Ensure that Virtual Network Flow Logs are Captured and Sent to Log Analytics",
+ "Checks": [
+ "network_flow_log_captured_sent"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Virtual Network Flow Logs are Captured and Sent to Log Analytics",
+ "RationaleStatement": "Virtual network flow logs provide critical visibility into traffic patterns. Sending logs to a Log Analytics workspace enables centralized analysis, correlation, and alerting for faster threat detection and response.",
+ "ImpactStatement": "* Virtual network flow logs are charged per gigabyte of network flow logs collected and come with a free tier of 5 GB/month per subscription. * If traffic analytics is enabled with virtual network flow logs, traffic analytics pricing applies at per gigabyte processing rates. * The storage of logs is charged separately.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, click `Flow logs`. 1. Click `+ Create`. 1. Select a subscription. 1. Next to `Flow log type`, select `Virtual network`. 1. Click `+ Select target resource`. 1. Select `Virtual network`. 1. Select a virtual network. 1. Click `Confirm selection`. 1. Select a storage account, or create a new storage account. 1. Set the retention in days for the storage account. 1. Click `Next`. 1. Under `Analytics`, for `Flow logs version`, select `Version 2`. 1. Check the box next to `Enable traffic analytics`. 1. Select a processing interval. 1. Select a `Log Analytics Workspace`. 1. Click `Next`. 1. Optionally, add `Tags`. 1. Click `Review + create`. 1. Click `Create`. 1. Repeat steps 1-20 for each subscription or virtual network requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down menu, select `Flow log type`. 1. From the `Value` drop-down menu, check `Virtual network` only. 1. Click `Apply`. 1. Ensure that at least one virtual network flow log is listed and is configured to send logs to a `Log Analytics Workspace`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [2f080164-9f4d-497e-9db6-416dc9f7b48a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F2f080164-9f4d-497e-9db6-416dc9f7b48a) **- Name:** 'Network Watcher flow logs should have traffic analytics enabled' - **Policy ID:** [4c3c6c5f-0d47-4402-99b8-aa543dd8bcee](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F4c3c6c5f-0d47-4402-99b8-aa543dd8bcee) **- Name:** 'Audit flow logs configuration for every virtual network'",
+ "AdditionalInformation": "On September 30, 2027, NSG flow logs will be retired, and creating new NSG flow logs will no longer be possible after June 30, 2025. Azure recommends migrating to virtual network flow logs, which address NSG flow log limitations. After retirement, traffic analytics using NSG flow logs will no longer be supported, and existing NSG flow log resources will be deleted. Previously collected NSG flow log records will remain available per their retention policies. For details, see the official announcement: https://azure.microsoft.com/en-gb/updates?id=Azure-NSG-flow-logs-Retirement.",
+ "References": "https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-overview:https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-cli",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.7",
+ "Description": "Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Graph Activity Logs to an Appropriate Destination",
+ "Checks": [
+ "monitor_diagnostic_settings_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Graph Activity Logs to an Appropriate Destination",
+ "RationaleStatement": "Microsoft Graph activity logs provide visibility into HTTP requests made to the Microsoft Graph service, helping detect unauthorized access, suspicious activity, and security threats. Configuring diagnostic settings in Microsoft Entra ensures these logs are collected and sent to an appropriate destination for monitoring, analysis, and retention.",
+ "ImpactStatement": "A Microsoft Entra ID P1 or P2 tenant license is required to access the Microsoft Graph activity logs. The amount of data logged and, thus, the cost incurred can vary significantly depending on the tenant size and the applications in your tenant that interact with the Microsoft Graph APIs. See the following pricing calculations for respective services: - Log Analytics: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs#pricing-model. - Azure Storage: https://azure.microsoft.com/en-gb/pricing/details/storage/blobs/. - Event Hubs: https://azure.microsoft.com/en-gb/pricing/details/event-hubs/",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Monitoring`, click `Diagnostic settings`. 1. Click `+ Add diagnostic setting`. 1. Provide a `Diagnostic setting name`. 1. Under `Logs > Categories`, check the box next to `MicrosoftGraphActivityLogs`. 1. Configure an appropriate destination for the logs. 1. Click `Save`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Monitoring`, click `Diagnostic settings`. 1. Next to each diagnostic setting, click `Edit setting`, and review the selected log categories and destination details. 1. Ensure that at least one diagnostic setting is configured to send `MicrosoftGraphActivityLogs` to an appropriate destination.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-configure-diagnostic-settings:https://learn.microsoft.com/en-us/graph/microsoft-graph-activity-logs-overview:https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs#pricing-model:https://azure.microsoft.com/en-gb/pricing/details/storage/blobs/:https://azure.microsoft.com/en-gb/pricing/details/event-hubs/",
+ "DefaultValue": "By default, Microsoft Entra diagnostic settings do not exist."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.8",
+ "Description": "Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Entra Activity Logs to an Appropriate Destination",
+ "Checks": [
+ "monitor_diagnostic_settings_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Entra Activity Logs to an Appropriate Destination",
+ "RationaleStatement": "Microsoft Entra activity logs enables you to assess many aspects of your Microsoft Entra tenant. Configuring diagnostic settings in Microsoft Entra ensures these logs are collected and sent to an appropriate destination for monitoring, analysis, and retention.",
+ "ImpactStatement": "To export sign-in data, your organization needs an Azure AD P1 or P2 license. The amount of data logged and, thus, the cost incurred can vary significantly depending on the tenant size. See the following pricing calculations for respective services: - Log Analytics: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs#pricing-model. - Azure Storage: https://azure.microsoft.com/en-gb/pricing/details/storage/blobs/. - Event Hubs: https://azure.microsoft.com/en-gb/pricing/details/event-hubs/",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Monitoring`, click `Diagnostic settings`. 1. Click `+ Add diagnostic setting`. 1. Provide a `Diagnostic setting name`. 1. Under `Logs > Categories`, check the box next to each of the following logs: - `AuditLogs` - `SignInLogs` - `NonInteractiveUserSignInLogs` - `ServicePrincipalSignInLogs` - `ManagedIdentitySignInLogs` - `ProvisioningLogs` - `ADFSSignInLogs` - `RiskyUsers` - `UserRiskEvents` - `NetworkAccessTrafficLogs` - `RiskyServicePrincipals` - `ServicePrincipalRiskEvents` - `EnrichedOffice365AuditLogs` - `MicrosoftGraphActivityLogs` - `RemoteNetworkHealthLogs` - `NetworkAccessAlerts` 1. Configure an appropriate destination for the logs. 1. Click `Save`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Entra ID`. 1. Under `Monitoring`, click `Diagnostic settings`. 1. Next to each diagnostic setting, click `Edit setting`, and review the selected log categories and destination details. 1. Ensure that at least one diagnostic setting is configured to send the following logs to an appropriate destination: - `AuditLogs` - `SignInLogs` - `NonInteractiveUserSignInLogs` - `ServicePrincipalSignInLogs` - `ManagedIdentitySignInLogs` - `ProvisioningLogs` - `ADFSSignInLogs` - `RiskyUsers` - `UserRiskEvents` - `NetworkAccessTrafficLogs` - `RiskyServicePrincipals` - `ServicePrincipalRiskEvents` - `EnrichedOffice365AuditLogs` - `MicrosoftGraphActivityLogs` - `RemoteNetworkHealthLogs` - `NetworkAccessAlerts`",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-configure-diagnostic-settings:https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-access-activity-logs?tabs=microsoft-entra-activity-logs%2Carchive-activity-logs-to-a-storage-account",
+ "DefaultValue": "By default, Microsoft Entra diagnostic settings do not exist."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1.9",
+ "Description": "Ensure that Intune Logs are Captured and Sent to Log Analytics",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Intune Logs are Captured and Sent to Log Analytics",
+ "RationaleStatement": "Intune includes built-in logs that provide information about your environments. Sending logs to a Log Analytics workspace enables centralized analysis, correlation, and alerting for faster threat detection and response.",
+ "ImpactStatement": "A Microsoft Intune plan is required to access Intune: https://www.microsoft.com/en-gb/security/business/microsoft-intune-pricing. The amount of data logged and, thus, the cost incurred can vary significantly depending on the tenant size. For information on Log Analytics workspace costs, visit: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Intune`. 1. Click `Reports`. 1. Under `Azure monitor`, click `Diagnostic settings`. 1. Click `+ Add diagnostic setting`. 1. Provide a `Diagnostic setting name`. 1. Under `Logs > Categories`, check the box next to each of the following logs: - `AuditLogs` - `OperationalLogs` - `DeviceComplianceOrg` - `Devices` - `Windows365AuditLogs` 1. Under `Destination details`, check the box next to `Send to Log Analytics workspace`. 1. Select a `Subscription`. 1. Select a `Log Analytics workspace`. 1. Click `Save`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Intune`. 1. Click `Reports`. 1. Under `Azure monitor`, click `Diagnostic settings`. 1. Next to each diagnostic setting, click `Edit setting`, and review the selected log categories and destination details. 1. Ensure that at least one diagnostic setting is configured to send the following logs to a Log Analytics workspace: - `AuditLogs` - `OperationalLogs` - `DeviceComplianceOrg` - `Devices` - `Windows365AuditLogs`",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/mem/intune/fundamentals/review-logs-using-azure-monitor:https://www.microsoft.com/en-gb/security/business/microsoft-intune-pricing:https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs",
+ "DefaultValue": "By default, Intune diagnostic settings do not exist."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.1",
+ "Description": "Ensure that Activity Log Alert Exists for Create Policy Assignment",
+ "Checks": [
+ "monitor_alert_create_policy_assignment"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Create Policy Assignment",
+ "RationaleStatement": "Monitoring for create policy assignment events gives insight into changes done in Azure policy - assignments and can reduce the time it takes to detect unsolicited changes.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Create policy assignment (Policy assignment)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Authorization/policyAssignments/write and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription ID> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Authorization/policyAssignments/write -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Get the `Action Group` information and store it in a variable, then create a new `Action` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` variable. ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Authorization/policyAssignments/write` ``` New-AzActivityLogAlert -Name <activity alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Authorization/policyAssignments/write`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Create policy assignment'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription ID> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Authorization/policyAssignments/write` in the output. If it's missing, generate a finding. **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Authorization/policyAssignments/write}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` If the output is empty, an `alert rule` for `Create Policy Assignments` is not configured. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [c5447c04-a4d7-4ba8-a263-c9ee321a6858](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc5447c04-a4d7-4ba8-a263-c9ee321a6858) **- Name:** 'An activity log alert should exist for specific Policy operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation:https://docs.microsoft.com/en-in/rest/api/policy/policy-assignments:https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-log",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.2",
+ "Description": "Ensure that Activity Log Alert exists for Delete Policy Assignment",
+ "Checks": [
+ "monitor_alert_delete_policy_assignment"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert exists for Delete Policy Assignment",
+ "RationaleStatement": "Monitoring for delete policy assignment events gives insight into changes done in azure policy - assignments and can reduce the time it takes to detect unsolicited changes.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Delete policy assignment (Policy assignment)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Authorization/policyAssignments/delete and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the conditions object ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Authorization/policyAssignments/delete -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Action` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` variable. ``` $scope = /subscriptions/<subscription id> ``` Create the `Activity Log Alert Rule` for `Microsoft.Authorization/policyAssignments/delete`. ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Authorization/policyAssignments/delete`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Delete policy assignment'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription ID> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Authorization/policyAssignments/delete` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Authorization/policyAssignments/delete}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [c5447c04-a4d7-4ba8-a263-c9ee321a6858](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc5447c04-a4d7-4ba8-a263-c9ee321a6858) **- Name:** 'An activity log alert should exist for specific Policy operations'",
+ "AdditionalInformation": "This log alert also applies for Azure Blueprints.",
+ "References": "https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation:https://azure.microsoft.com/en-us/services/blueprints/",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.3",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Network Security Group",
+ "Checks": [
+ "monitor_alert_create_update_nsg"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Network Security Group",
+ "RationaleStatement": "Monitoring for Create or Update Network Security Group events gives insight into network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Create or Update Network Security Group (Network Security Group)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Network/networkSecurityGroups/write and level=verbose --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Network/networkSecurityGroups/write -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription id> ``` Create the `Activity Log Alert Rule` for `Microsoft.Network/networkSecurityGroups/write` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Network/networkSecurityGroups/write`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Create or Update Network Security Group'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription ID> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Network/networkSecurityGroups/write` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Network/networkSecurityGroups/write}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.4",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Network Security Group",
+ "Checks": [
+ "monitor_alert_delete_nsg"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Network Security Group",
+ "RationaleStatement": "Monitoring for Delete Network Security Group events gives insight into network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Delete Network Security Group (Network Security Group)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Network/networkSecurityGroups/delete and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Network/networkSecurityGroups/delete -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription id> ``` Create the `Activity Log Alert Rule` for `Microsoft.Network/networkSecurityGroups/delete` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Network/networkSecurityGroups/delete`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Delete Network Security Group'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription ID> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Network/networkSecurityGroups/delete` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Network/networkSecurityGroups/delete}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.5",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Security Solution",
+ "Checks": [
+ "monitor_alert_create_update_security_solution"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Security Solution",
+ "RationaleStatement": "Monitoring for Create or Update Security Solution events gives insight into changes to the active security solutions and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Create or Update Security Solutions (Security Solutions)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Security/securitySolutions/write and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Security/securitySolutions/write -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Security/securitySolutions/write` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Security/securitySolutions/write`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Create or Update Security Solutions'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Security/securitySolutions/write` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Security/securitySolutions/write}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.6",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Security Solution",
+ "Checks": [
+ "monitor_alert_delete_security_solution"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Security Solution",
+ "RationaleStatement": "Monitoring for Delete Security Solution events gives insight into changes to the active security solutions and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "Alert rules incur minimal costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Delete Security Solutions (Security Solutions)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Security/securitySolutions/delete and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Security/securitySolutions/delete -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Security/securitySolutions/delete` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Security/securitySolutions/delete`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Delete Security Solutions'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Security/securitySolutions/delete` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Security/securitySolutions/delete}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.7",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update SQL Server Firewall Rule",
+ "Checks": [
+ "monitor_alert_create_update_sqlserver_fr"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update SQL Server Firewall Rule",
+ "RationaleStatement": "Monitoring for Create or Update SQL Server Firewall Rule events gives insight into network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "There will be a substantial increase in log size if there are a large number of administrative actions on a server.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Create/Update server firewall rule (Server Firewall Rule)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Sql/servers/firewallRules/write and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Sql/servers/firewallRules/write -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Sql/servers/firewallRules/write` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Sql/servers/firewallRules/write`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Create/Update server firewall rule'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Sql/servers/firewallRules/write` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Sql/servers/firewallRules/write}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.8",
+ "Description": "Ensure that Activity Log Alert Exists for Delete SQL Server Firewall Rule",
+ "Checks": [
+ "monitor_alert_delete_sqlserver_fr"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Delete SQL Server Firewall Rule",
+ "RationaleStatement": "Monitoring for Delete SQL Server Firewall Rule events gives insight into SQL network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "There will be a substantial increase in log size if there are a large number of administrative actions on a server.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Delete server firewall rule (Server Firewall Rule)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Sql/servers/firewallRules/delete and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Sql/servers/firewallRules/delete -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Sql/servers/firewallRules/delete` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Sql/servers/firewallRules/delete`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Delete server firewall rule'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Sql/servers/firewallRules/delete` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Sql/servers/firewallRules/delete}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b954148f-4c11-4c38-8221-be76711e194a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb954148f-4c11-4c38-8221-be76711e194a) **- Name:** 'An activity log alert should exist for specific Administrative operations'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.9",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Public IP Address rule",
+ "Checks": [
+ "monitor_alert_create_update_public_ip_address_rule"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Create or Update Public IP Address rule",
+ "RationaleStatement": "Monitoring for Create or Update Public IP Address events gives insight into network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "There will be a substantial increase in log size if there are a large number of administrative actions on a server.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Create or Update Public Ip Address (Public Ip Address)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Network/publicIPAddresses/write and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Network/publicIPAddresses/write -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Network/publicIPAddresses/write` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Network/publicIPAddresses/write`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Create or Update Public Ip Address'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Network/publicIPAddresses/write` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Network/publicIPAddresses/write}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [1513498c-3091-461a-b321-e9b433218d28](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F1513498c-3091-461a-b321-e9b433218d28) **- Name:** 'Enable logging by category group for Public IP addresses (microsoft.network/publicipaddresses) to Log Analytics'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.10",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Public IP Address rule",
+ "Checks": [
+ "monitor_alert_delete_public_ip_address_rule"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Activity Log Alert Exists for Delete Public IP Address rule",
+ "RationaleStatement": "Monitoring for Delete Public IP Address events gives insight into network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "There will be a substantial increase in log size if there are a large number of administrative actions on a server.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Select `Alerts`. 1. Select `Create`. 1. Select `Alert rule`. 1. Choose a subscription. 1. Select `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Delete Public Ip Address (Public Ip Address)`. 1. Click `Apply`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. **Remediate from Azure CLI** ``` az monitor activity-log alert create --resource-group <resource group name> --condition category=Administrative and operationName=Microsoft.Network/publicIPAddresses/delete and level=<verbose | information | warning | error | critical> --scope /subscriptions/<subscription ID> --name <activity log rule name> --subscription <subscription id> --action-group <action group ID> ``` **Remediate from PowerShell** Create the `Conditions` object. ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Administrative -Field category $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Microsoft.Network/publicIPAddresses/delete -Field operationName $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal Verbose -Field level ``` Retrieve the `Action Group` information and store in a variable, then create the `Actions` object. ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource group name> -Name <action group name> $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object ``` $scope = /subscriptions/<subscription ID> ``` Create the `Activity Log Alert Rule` for `Microsoft.Network/publicIPAddresses/delete` ``` New-AzActivityLogAlert -Name <activity log alert rule name> -ResourceGroupName <resource group name> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription ID> -Enabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the `Monitor` blade. 1. Click on `Alerts`. 1. In the Alerts window, click on `Alert rules`. 1. Ensure an alert rule exists where the Condition column contains `Operation name=Microsoft.Network/publicIPAddresses/delete`. 1. Click on the Alert `Name` associated with the previous step. 1. Ensure the `Condition` panel displays the text `Whenever the Activity Log has an event with Category='Administrative', Operation name='Delete Public Ip Address'` and does not filter on `Level`, `Status` or `Caller`. 1. Ensure the `Actions` panel displays an Action group is assigned to notify the appropriate personnel in your organization. **Audit from Azure CLI** ``` az monitor activity-log alert list --subscription <subscription Id> --query [].{Name:name,Enabled:enabled,Condition:condition.allOf,Actions:actions} ``` Look for `Microsoft.Network/publicIPAddresses/delete` in the output **Audit from PowerShell** ``` Get-AzActivityLogAlert -SubscriptionId <subscription ID>|where-object {$_.ConditionAllOf.Equal -match Microsoft.Network/publicIPAddresses/delete}|select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [1513498c-3091-461a-b321-e9b433218d28](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F1513498c-3091-461a-b321-e9b433218d28) **- Name:** 'Enable logging by category group for Public IP addresses (microsoft.network/publicipaddresses) to Log Analytics'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/updates/classic-alerting-monitoring-retirement:https://docs.microsoft.com/en-in/azure/azure-monitor/platform/alerts-activity-log:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/createorupdate:https://docs.microsoft.com/en-in/rest/api/monitor/activitylogalerts/listbysubscriptionid:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2.11",
+ "Description": "Ensure that an Activity Log Alert Exists for Service Health",
+ "Checks": [
+ "monitor_alert_service_health_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that an Activity Log Alert Exists for Service Health",
+ "RationaleStatement": "Monitoring for Service Health events provides insight into service issues, planned maintenance, security advisories, and other changes that may affect the Azure services and regions in use.",
+ "ImpactStatement": "There is no charge for creating activity log alert rules.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Monitor`. 1. Click `Alerts`. 1. Click `+ Create`. 1. Select `Alert rule` from the drop-down menu. 1. Choose a subscription. 1. Click `Apply`. 1. Select the `Condition` tab. 1. Click `See all signals`. 1. Select `Service health`. 1. Click `Apply`. 1. Open the drop-down menu next to `Event types`. 1. Check the box next to `Select all`. 1. Select the `Actions` tab. 1. Click `Select action groups` to select an existing action group, or `Create action group` to create a new action group. 1. Follow the prompts to choose or create an action group. 1. Select the `Details` tab. 1. Select a `Resource group`, provide an `Alert rule name` and an optional `Alert rule description`. 1. Click `Review + create`. 1. Click `Create`. 1. Repeat steps 1-19 for each subscription requiring remediation. **Remediate from Azure CLI** For each subscription requiring remediation, run the following command to create a `ServiceHealth` alert rule for a subscription: ``` az monitor activity-log alert create --subscription <subscription-id> --resource-group <resource-group> --name <alert-rule> --condition category=ServiceHealth and properties.incidentType=Incident --scope /subscriptions/<subscription-id> --action-group <action-group> ``` **Remediate from PowerShell** Create the `Conditions` object: ``` $conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Field category -Equal ServiceHealth $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Field properties.incidentType -Equal Incident ``` Retrieve the `Action Group` information and store in a variable: ``` $actionGroup = Get-AzActionGroup -ResourceGroupName <resource-group> -Name <action-group> ``` Create the `Actions` object: ``` $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id ``` Create the `Scope` object: ``` $scope = /subscriptions/<subscription-id> ``` Create the activity log alert rule: ``` New-AzActivityLogAlert -Name <alert-rule> -ResourceGroupName <resource-group> -Condition $conditions -Scope $scope -Location global -Action $actionObject -Subscription <subscription-id> -Enabled $true ``` Repeat for each subscription requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Monitor`. 1. Click `Alerts`. 1. Click `Alert rules`. 1. Ensure an alert rule exists for a subscription with `Condition` set to `Service names=All, Event types=All` and `Target resource type` set to `Subscription`. 1. If an alert rule is found for step 4, click the name of the alert rule. 1. Ensure the `Actions` panel displays an action group configured to notify appropriate personnel. 1. Repeat steps 1-6 for each subscription. **Audit from Azure CLI** Run the following command to list activity log alerts: ``` az monitor activity-log alert list --subscription <subscription-id> ``` For each activity log alert, run the following command: ``` az monitor activity-log alert show --subscription <subscription-id> --resource-group <resource-group> --activity-log-alert-name <activity-log-alert> ``` Ensure an alert exists for `ServiceHealth` with `scopes` set to a subscription ID. Repeat for each subscription. **Audit from PowerShell** Run the following command to locate `ServiceHealth` alert rules for a subscription: ``` Get-AzActivityLogAlert -SubscriptionId <subscription-id> | where-object {$_.ConditionAllOf.Equal -match ServiceHealth} | select-object Location,Name,Enabled,ResourceGroupName,ConditionAllOf ``` Ensure that at least one `ServiceHealth` alert rule is returned. Repeat for each subscription.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/service-health/overview:https://learn.microsoft.com/en-us/azure/service-health/alerts-activity-log-service-notifications-portal:https://azure.microsoft.com/en-gb/pricing/details/monitor/#faq:https://learn.microsoft.com/en-us/cli/azure/monitor/activity-log/alert:https://learn.microsoft.com/en-us/powershell/module/az.monitor/get-azactivitylogalert:https://learn.microsoft.com/en-us/powershell/module/az.monitor/new-azactivitylogalert",
+ "DefaultValue": "By default, no monitoring alerts are created."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.3.1",
+ "Description": "Ensure Application Insights are Configured",
+ "Checks": [
+ "appinsights_ensure_is_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Application Insights are Configured",
+ "RationaleStatement": "Configuring Application Insights provides additional data not found elsewhere within Azure as part of a much larger logging and monitoring program within an organization's Information Security practice. The types and contents of these logs will act as both a potential cost saving measure (application performance) and a means to potentially confirm the source of a potential incident (trace logging). Metrics and Telemetry data provide organizations with a proactive approach to cost savings by monitoring an application's performance, while the trace logging data provides necessary details in a reactive incident response scenario by helping organizations identify the potential source of an incident within their application.",
+ "ImpactStatement": "Because Application Insights relies on a Log Analytics Workspace, an organization will incur additional expenses when using this service.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to `Application Insights`. 2. Under the `Basics` tab within the `PROJECT DETAILS` section, select the `Subscription`. 3. Select the `Resource group`. 4. Within the `INSTANCE DETAILS`, enter a `Name`. 5. Select a `Region`. 6. Next to `Resource Mode`, select `Workspace-based`. 7. Within the `WORKSPACE DETAILS`, select the `Subscription` for the log analytics workspace. 8. Select the appropriate `Log Analytics Workspace`. 9. Click `Next:Tags >`. 10. Enter the appropriate `Tags` as `Name`, `Value` pairs. 11. Click `Next:Review+Create`. 12. Click `Create`. **Remediate from Azure CLI** ``` az monitor app-insights component create --app <app name> --resource-group <resource group name> --location <location> --kind web --retention-time <INT days to retain logs> --workspace <log analytics workspace ID> --subscription <subscription ID> ``` **Remediate from PowerShell** ``` New-AzApplicationInsights -Kind web -ResourceGroupName <resource group name> -Name <app insights name> -location <location> -RetentionInDays <INT days to retain logs> -SubscriptionID <subscription ID> -WorkspaceResourceId <log analytics workspace ID> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to `Application Insights`. 2. Ensure an `Application Insights` service is configured and exists. **Audit from Azure CLI** ``` az monitor app-insights component show --query [].{ID:appId, Name:name, Tenant:tenantId, Location:location, Provisioning_State:provisioningState} ``` Ensure the above command produces output, otherwise `Application Insights` has not been configured. **Audit from PowerShell** ``` Get-AzApplicationInsights|select location,name,appid,provisioningState,tenantid ```",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview",
+ "DefaultValue": "Application Insights are not enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.4",
+ "Description": "Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it",
+ "Checks": [
+ "monitor_diagnostic_settings_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it",
+ "RationaleStatement": "A lack of monitoring reduces the visibility into the data plane, and therefore an organization's ability to detect reconnaissance, authorization attempts or other malicious activity. Unlike Activity Logs, Resource Logs are not enabled by default. Specifically, without monitoring it would be impossible to tell which entities had accessed a data store that was breached. In addition, alerts for failed attempts to access APIs for Web Services or Databases are only possible when logging is enabled.",
+ "ImpactStatement": "Costs for monitoring varies with Log Volume. Not every resource needs to have logging enabled. It is important to determine the security classification of the data being processed by the given resource and adjust the logging based on which events need to be tracked. This is typically determined by governance and compliance requirements.",
+ "RemediationProcedure": "Azure Subscriptions should log every access and operation for all resources. Logs should be sent to Storage and a Log Analytics Workspace or equivalent third-party system. Logs should be kept in readily-accessible storage for a minimum of one year, and then moved to inexpensive cold storage for a duration of time as necessary. If retention policies are set but storing logs in a Storage Account is disabled (for example, if only Event Hubs or Log Analytics options are selected), the retention policies have no effect. Enable all monitoring at first, and then be more aggressive moving data to cold storage if the volume of data becomes a cost concern. **Remediate from Azure Portal** The specific steps for configuring resources within the Azure console vary depending on resource, but typically the steps are: 1. Go to the resource 2. Click on Diagnostic settings 3. In the blade that appears, click Add diagnostic setting 4. Configure the diagnostic settings 5. Click on Save **Remediate from Azure CLI** For each `resource`, run the following making sure to use a `resource` appropriate JSON encoded `category` for the `--logs` option. ``` az monitor diagnostic-settings create --name <diagnostic settings name> --resource <resource ID> --logs [{category:<resource specific category>,enabled:true,rentention-policy:{enabled:true,days:180}}] --metrics [{category:AllMetrics,enabled:true,retention-policy:{enabled:true,days:180}}] <[--event-hub <event hub ID> --event-hub-rule <event hub auth rule ID> | --storage-account <storage account ID> |--workspace <log analytics workspace ID> | --marketplace-partner-id <full resource ID of third-party solution>]> ``` **Remediate from PowerShell** Create the `log` settings object ``` $logSettings = @() $logSettings += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -RetentionPolicyDay 180 -RetentionPolicyEnabled $true -Category <resource specific category> $logSettings += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -RetentionPolicyDay 180 -RetentionPolicyEnabled $true -Category <resource specific category number 2> ``` Create the `metric` settings object ``` $metricSettings = @() $metricSettings += New-AzDiagnosticSettingMetricSettingsObject -Enabled $true -RetentionPolicyDay 180 -RetentionPolicyEnabled $true -Category AllMetrics ``` Create the diagnostic setting for a specific resource ``` New-AzDiagnosticSetting -Name <diagnostic settings name> -ResourceId <resource ID> -Log $logSettings -Metric $metricSettings ```",
+ "AuditProcedure": "**Audit from Azure Portal** The specific steps for configuring resources within the Azure console vary depending on resource, but typically the steps are: 1. Go to the resource 2. Click on Diagnostic settings 3. In the blade that appears, click Add diagnostic setting 4. Configure the diagnostic settings 5. Click on Save **Audit from Azure CLI** List all `resources` for a `subscription` ``` az resource list --subscription <subscription id> ``` For each `resource` run the following ``` az monitor diagnostic-settings list --resource <resource ID> ``` An empty result means a `diagnostic settings` is not configured for that resource. An error message means a `diagnostic settings` is not supported for that resource. **Audit from PowerShell** Get a list of `resources` in a `subscription` context and store in a variable ``` $resources = Get-AzResource ``` Loop through each `resource` to determine if a diagnostic setting is configured or not. ``` foreach ($resource in $resources) {$diagnosticSetting = Get-AzDiagnosticSetting -ResourceId $resource.id -ErrorAction SilentlyContinue; if ([string]::IsNullOrEmpty($diagnosticSetting)) {$message = Diagnostic Settings not configured for resource: + $resource.Name;Write-Output $message}else{$diagnosticSetting}} ``` A result of `Diagnostic Settings not configured for resource: <resource name>` means a `diagnostic settings` is not configured for that resource. Otherwise, the output of the above command will show configured `Diagnostic Settings` for a resource. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [cf820ca0-f99e-4f3e-84fb-66e913812d21](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fcf820ca0-f99e-4f3e-84fb-66e913812d21) **- Name:** 'Resource logs in Key Vault should be enabled' - **Policy ID:** [91a78b24-f231-4a8a-8da9-02c35b2b6510](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F91a78b24-f231-4a8a-8da9-02c35b2b6510) **- Name:** 'App Service apps should have resource logs enabled' - **Policy ID:** [428256e6-1fac-4f48-a757-df34c2b3336d](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F428256e6-1fac-4f48-a757-df34c2b3336d) **- Name:** 'Resource logs in Batch accounts should be enabled' - **Policy ID:** [057ef27e-665e-4328-8ea3-04b3122bd9fb](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F057ef27e-665e-4328-8ea3-04b3122bd9fb) **- Name:** 'Resource logs in Azure Data Lake Store should be enabled' - **Policy ID:** [c95c74d9-38fe-4f0d-af86-0c7d626a315c](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc95c74d9-38fe-4f0d-af86-0c7d626a315c) **- Name:** 'Resource logs in Data Lake Analytics should be enabled' - **Policy ID:** [83a214f7-d01a-484b-91a9-ed54470c9a6a](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F83a214f7-d01a-484b-91a9-ed54470c9a6a) **- Name:** 'Resource logs in Event Hub should be enabled' - **Policy ID:** [383856f8-de7f-44a2-81fc-e5135b5c2aa4](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F383856f8-de7f-44a2-81fc-e5135b5c2aa4) **- Name:** 'Resource logs in IoT Hub should be enabled' - **Policy ID:** [34f95f76-5386-4de7-b824-0d8478470c9d](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F34f95f76-5386-4de7-b824-0d8478470c9d) **- Name:** 'Resource logs in Logic Apps should be enabled' - **Policy ID:** [b4330a05-a843-4bc8-bf9a-cacce50c67f4](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb4330a05-a843-4bc8-bf9a-cacce50c67f4) **- Name:** 'Resource logs in Search services should be enabled' - **Policy ID:** [f8d36e2f-389b-4ee4-898d-21aeb69a0f45](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff8d36e2f-389b-4ee4-898d-21aeb69a0f45) **- Name:** 'Resource logs in Service Bus should be enabled' - **Policy ID:** [f9be5368-9bf5-4b84-9e0a-7850da98bb46](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff9be5368-9bf5-4b84-9e0a-7850da98bb46) **- Name:** 'Resource logs in Azure Stream Analytics should be enabled'",
+ "AdditionalInformation": "For an up-to-date list of Azure resources which support Azure Monitor, refer to the Supported Log Categories reference.",
+ "References": "https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-3-enable-logging-for-security-investigation:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-5-centralize-security-log-management-and-analysis:https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/monitor-azure-resource:Supported Log Categories: https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-categories:Logs and Audit - Fundamentals: https://docs.microsoft.com/en-us/azure/security/fundamentals/log-audit:Collecting Logs: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-activity-logs:Key Vault Logging: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-logging:Monitor Diagnostic Settings: https://docs.microsoft.com/en-us/cli/azure/monitor/diagnostic-settings?view=azure-cli-latest:Overview of Diagnostic Logs: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-logs-overview:Supported Services for Diagnostic Logs: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-logs-schema:Diagnostic Logs for CDNs: https://docs.microsoft.com/en-us/azure/cdn/cdn-azure-diagnostic-logs",
+ "DefaultValue": "By default, Azure Monitor Resource Logs are 'Disabled' for all resources."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.5",
+ "Description": "Ensure Basic, Free, and Consumption SKUs are not used on Production artifacts requiring monitoring and SLA",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "SubSection": "6.1 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Basic, Free, and Consumption SKUs are not used on Production artifacts requiring monitoring and SLA",
+ "RationaleStatement": "Typically, production workloads need to be monitored and should have an SLA with Microsoft, using Basic SKUs for any deployed product will mean that that these capabilities do not exist. The following resource types should use standard SKUs as a minimum. - Public IP Addresses - Network Load Balancers - REDIS Cache - SQL PaaS Databases - VPN Gateways",
+ "ImpactStatement": "The impact of enforcing Standard SKU's is twofold 1) There will be a cost increase 2) The monitoring and service level agreements will be available and will support the production service. All resources should be either tagged or in separate Management Groups/Subscriptions",
+ "RemediationProcedure": "Each resource has its own process for upgrading from basic to standard SKUs that should be followed if required. - Public IP Address: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade. - Basic Load Balancer: https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-basic-upgrade-guidance. - Azure Cache for Redis: https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-scale. - Azure SQL Database: https://learn.microsoft.com/en-us/azure/azure-sql/database/scale-resources. - VPN Gateway: https://learn.microsoft.com/en-us/azure/vpn-gateway/gateway-sku-resize.",
+ "AuditProcedure": "This needs to be audited by Azure Policy (one for each resource type) and denied for each artifact that is production. **Audit from Azure Portal** 1. Open `Azure Resource Graph Explorer` 1. Click `New query` 1. Paste the following into the query window: ``` Resources | where sku contains 'Basic' or sku contains 'consumption' | order by type ``` 4. Click `Run query` then evaluate the results in the results window. 5. Ensure that no production artifacts are returned. **Audit from Azure CLI** ``` az graph query -q Resources | where sku contains 'Basic' or sku contains 'consumption' | order by type ``` Alternatively, to filter on a specific resource group: ``` az graph query -q Resources | where resourceGroup == '<resourceGroupName>' | where sku contains 'Basic' or sku contains 'consumption' | order by type ``` Ensure that no production artifacts are returned. **Audit from PowerShell** ``` Get-AzResource | ?{ $_.Sku -EQ Basic} ``` Ensure that no production artifacts are returned.",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/support/plans:https://azure.microsoft.com/en-us/support/plans/response/:https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade:https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-basic-upgrade-guidance:https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-scale:https://learn.microsoft.com/en-us/azure/azure-sql/database/scale-resources:https://learn.microsoft.com/en-us/azure/vpn-gateway/gateway-sku-resize",
+ "DefaultValue": "Policy should enforce standard SKUs for the following artifacts: - Public IP Addresses - Network Load Balancers - REDIS Cache - SQL PaaS Databases - VPN Gateways"
+ }
+ ]
+ },
+ {
+ "Id": "6.2",
+ "Description": "Ensure that Resource Locks are set for Mission-Critical Azure Resources",
+ "Checks": [
+ "iam_custom_role_has_permissions_to_administer_resource_locks"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Management and Governance Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Resource Locks are set for Mission-Critical Azure Resources",
+ "RationaleStatement": "As an administrator, it may be necessary to lock a subscription, resource group, or resource to prevent other users in the organization from accidentally deleting or modifying critical resources. The lock level can be set to to `CanNotDelete` or `ReadOnly` to achieve this purpose. - `CanNotDelete` means authorized users can still read and modify a resource, but they cannot delete the resource. - `ReadOnly` means authorized users can read a resource, but they cannot delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role.",
+ "ImpactStatement": "There can be unintended outcomes of locking a resource. Applying a lock to a parent service will cause it to be inherited by all resources within. Conversely, applying a lock to a resource may not apply to connected storage, leaving it unlocked. Please see the documentation for further information.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the specific Azure Resource or Resource Group. 2. For each mission critical resource, click on `Locks`. 3. Click `Add`. 4. Give the lock a name and a description, then select the type, `Read-only` or `Delete` as appropriate. 5. Click OK. **Remediate from Azure CLI** To lock a resource, provide the name of the resource, its resource type, and its resource group name. ``` az lock create --name <LockName> --lock-type <CanNotDelete/Read-only> --resource-group <resourceGroupName> --resource-name <resourceName> --resource-type <resourceType> ``` **Remediate from PowerShell** ``` Get-AzResourceLock -ResourceName <Resource Name> -ResourceType <Resource Type> -ResourceGroupName <Resource Group Name> -Locktype <CanNotDelete/Read-only> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the specific Azure Resource or Resource Group. 2. Click on `Locks`. 3. Ensure the lock is defined with name and description, with type `Read-only` or `Delete` as appropriate. **Audit from Azure CLI** Review the list of all locks set currently: ``` az lock list --resource-group <resourcegroupname> --resource-name <resourcename> --namespace <Namespace> --resource-type <type> --parent ``` **Audit from PowerShell** Run the following command to list all resources. ``` Get-AzResource ``` For each resource, run the following command to check for Resource Locks. ``` Get-AzResourceLock -ResourceName <Resource Name> -ResourceType <Resource Type> -ResourceGroupName <Resource Group Name> ``` Review the output of the `Properties` setting. Compliant settings will have the `CanNotDelete` or `ReadOnly` value.",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-lock-resources:https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-subscription-governance#azure-resource-locks:https://docs.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-asset-management#am-4-limit-access-to-asset-management",
+ "DefaultValue": "By default, no locks are set."
+ }
+ ]
+ },
+ {
+ "Id": "7.1",
+ "Description": "Ensure that RDP Access from the Internet is Evaluated and Restricted",
+ "Checks": [
+ "network_rdp_internet_access_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that RDP Access from the Internet is Evaluated and Restricted",
+ "RationaleStatement": "The potential security problem with using RDP over the Internet is that attackers can use various brute force techniques to gain access to Azure Virtual Machines. Once the attackers gain access, they can use a virtual machine as a launch point for compromising other machines on an Azure Virtual Network or even attack networked devices outside of Azure.",
+ "ImpactStatement": "Restricting RDP access may require alternative methods for remote administration such as VPN or Azure Bastion.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Network security groups`. 1. Under `Settings`, click `Inbound security rules`. 1. Check the box next to any inbound security rule matching: - Port: `3389` or range including 3389 - Protocol: `TCP` or `Any` - Source: `0.0.0.0/0`, `Internet`, or `Any` - Action: `Allow` 1. Click `Delete`. 1. Click `Yes`. **Remediate from Azure CLI** For each network security group rule requiring remediation, run the following command to delete a rule: ``` az network nsg rule delete --resource-group <resource-group> --nsg-name <network-security-group> --name <rule> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Network security groups`. 1. Under `Settings`, click `Inbound security rules`. 1. Ensure that no inbound security rule exists that matches the following: - Port: `3389` or range including 3389 - Protocol: `TCP` or `Any` - Source: `0.0.0.0/0`, `Internet`, or `Any` - Action: `Allow` 1. Repeat steps 1-3 for each network security group. To audit from Azure Resource Graph: 1. Go to `Resource Graph Explorer`. 1. Click `New query`. 1. Paste the following into the query window: ``` resources | where type =~ microsoft.network/networksecuritygroups | project id, name, securityRule = properties.securityRules | mv-expand securityRule | extend access = securityRule.properties.access, direction = securityRule.properties.direction, protocol = securityRule.properties.protocol, destinationPort = case(isempty(securityRule.properties.destinationPortRange), securityRule.properties.destinationPortRanges, securityRule.properties.destinationPortRange), sourceAddress = case(isempty(securityRule.properties.sourceAddressPrefix), securityRule.properties.sourceAddressPrefixes, securityRule.properties.sourceAddressPrefix) | where access =~ Allow and direction =~ Inbound and protocol in~ (tcp, ) | mv-expand destinationPort | mv-expand sourceAddress | extend destinationPortMin = toint(split(destinationPort, -)[0]), destinationPortMax = toint(split(destinationPort, -)[-1]) | where (destinationPortMin <= 3389 and destinationPortMax >= 3389) or destinationPort == | where sourceAddress in~ (*, 0.0.0.0, internet, any) or sourceAddress endswith /0 ``` 1. Click `Run query`. 1. Ensure that no results are returned. **Audit from Azure CLI** List network security groups with non-default security rules: ``` az network nsg list --query [*].[name,securityRules] ``` Ensure that no network security group has an inbound security rule that matches the following: ``` access : Allow destinationPortRange : 3389, *, or <range-including-3389> direction : Inbound protocol : TCP or * sourceAddressPrefix : 0.0.0.0/0, Internet, or * ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [22730e10-96f6-4aac-ad84-9383d35b5917](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F22730e10-96f6-4aac-ad84-9383d35b5917) **- Name:** 'Management ports should be closed on your virtual machines'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security/azure-security-network-security-best-practices#disable-rdpssh-access-to-azure-virtual-machines:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-1-establish-network-segmentation-boundaries:Express Route: https://docs.microsoft.com/en-us/azure/expressroute/:Site-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal:Point-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal",
+ "DefaultValue": "By default, RDP access from internet is not `enabled`."
+ }
+ ]
+ },
+ {
+ "Id": "7.2",
+ "Description": "Ensure that SSH Access from the Internet is Evaluated and Restricted",
+ "Checks": [
+ "network_ssh_internet_access_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that SSH Access from the Internet is Evaluated and Restricted",
+ "RationaleStatement": "The potential security problem with using SSH over the Internet is that attackers can use various brute force techniques to gain access to Azure Virtual Machines. Once the attackers gain access, they can use a virtual machine as a launch point for compromising other machines on the Azure Virtual Network or even attack networked devices outside of Azure.",
+ "ImpactStatement": "Restricting SSH access may require alternative methods for remote administration such as VPN or Azure Bastion.",
+ "RemediationProcedure": "Where SSH is not explicitly required and narrowly configured for resources attached to the Network Security Group, Internet-level access to your Azure resources should be restricted or eliminated. For internal access to relevant resources, configure an encrypted network tunnel such as: [ExpressRoute](https://docs.microsoft.com/en-us/azure/expressroute/) [Site-to-site VPN](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal) [Point-to-site VPN](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal)",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Open the `Networking` blade for the specific Virtual machine in Azure portal 2. Verify that the `INBOUND PORT RULES` **does not** have a rule for SSH such as - port = `22`, - protocol = `TCP` OR `ANY`, - Source = `Any` OR `Internet` **Audit from Azure CLI** List Network security groups with corresponding non-default Security rules: ``` az network nsg list --query [*].[name,securityRules] ``` Ensure that none of the NSGs have security rule as below ``` access : Allow destinationPortRange : 22 or * or [port range containing 22] direction : Inbound protocol : TCP or * sourceAddressPrefix : * or 0.0.0.0 or <nw>/0 or /0 or internet or any ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [22730e10-96f6-4aac-ad84-9383d35b5917](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F22730e10-96f6-4aac-ad84-9383d35b5917) **- Name:** 'Management ports should be closed on your virtual machines'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security/azure-security-network-security-best-practices#disable-rdpssh-access-to-azure-virtual-machines:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-1-establish-network-segmentation-boundaries:Express Route: https://docs.microsoft.com/en-us/azure/expressroute/:Site-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal:Point-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal",
+ "DefaultValue": "By default, SSH access from internet is not `enabled`."
+ }
+ ]
+ },
+ {
+ "Id": "7.3",
+ "Description": "Ensure that UDP Port Access from the Internet is Evaluated and Restricted",
+ "Checks": [
+ "network_udp_internet_access_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that UDP Port Access from the Internet is Evaluated and Restricted",
+ "RationaleStatement": "The potential security problem with broadly exposing UDP services over the Internet is that attackers can use DDoS amplification techniques to reflect spoofed UDP traffic from Azure Virtual Machines. The most common types of these attacks use exposed DNS, NTP, SSDP, SNMP, CLDAP and other UDP-based services as amplification sources for disrupting services of other machines on the Azure Virtual Network or even attack networked devices outside of Azure.",
+ "ImpactStatement": "Restricting UDP access may impact services that legitimately require UDP traffic.",
+ "RemediationProcedure": "Where UDP is not explicitly required and narrowly configured for resources attached to the Network Security Group, Internet-level access to your Azure resources should be restricted or eliminated. For internal access to relevant resources, configure an encrypted network tunnel such as: [ExpressRoute](https://docs.microsoft.com/en-us/azure/expressroute/) [Site-to-site VPN](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal) [Point-to-site VPN](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal)",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Open the `Networking` blade for the specific Virtual machine in Azure portal 2. Verify that the `INBOUND PORT RULES` **does not** have a rule for UDP such as - protocol = `UDP`, - Source = `Any` OR `Internet` **Audit from Azure CLI** List Network security groups with corresponding non-default Security rules: ``` az network nsg list --query [*].[name,securityRules] ``` Ensure that none of the NSGs have security rule as below ``` access : Allow destinationPortRange : * or [port range containing 53, 123, 161, 389, 1900, or other vulnerable UDP-based services] direction : Inbound protocol : UDP sourceAddressPrefix : * or 0.0.0.0 or <nw>/0 or /0 or internet or any ```",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security/fundamentals/network-best-practices#secure-your-critical-azure-service-resources-to-only-your-virtual-networks:https://docs.microsoft.com/en-us/azure/security/fundamentals/ddos-best-practices:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-1-establish-network-segmentation-boundaries:ExpressRoute: https://docs.microsoft.com/en-us/azure/expressroute/:Site-to-site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal:Point-to-site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal",
+ "DefaultValue": "By default, UDP access from internet is not `enabled`."
+ }
+ ]
+ },
+ {
+ "Id": "7.4",
+ "Description": "Ensure that HTTP(S) Access from the Internet is Evaluated and Restricted",
+ "Checks": [
+ "network_http_internet_access_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that HTTP(S) Access from the Internet is Evaluated and Restricted",
+ "RationaleStatement": "The potential security problem with using HTTP(S) over the Internet is that attackers can use various brute force techniques to gain access to Azure resources. Once the attackers gain access, they can use the resource as a launch point for compromising other resources within the Azure tenant.",
+ "ImpactStatement": "Restricting HTTP(S) access may require proper configuration of web application firewalls and load balancers.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Virtual machines`. 2. For each VM, open the `Networking` blade. 3. Click on `Inbound port rules`. 4. Delete the rule with: * Port = 80/443 OR \\[port range containing 80/443\\] * Protocol = TCP OR Any * Source = Any (\\*) OR IP Addresses(0.0.0.0/0) OR Service Tag(Internet) * Action = Allow **Remediate from Azure CLI** 1. Run below command to list network security groups: ``` az network nsg list --subscription <subscription-id> --output table ``` 2. For each network security group, run below command to list the rules associated with the specified port: ``` az network nsg rule list --resource-group <resource-group> --nsg-name <nsg-name> --query [?destinationPortRange=='80 or 443'] ``` 3. Run the below command to delete the rule with: * Port = 80/443 OR \\[port range containing 80/443\\] * Protocol = TCP OR * * Source = Any (\\*) OR IP Addresses(0.0.0.0/0) OR Service Tag(Internet) * Action = Allow ``` az network nsg rule delete --resource-group <resource-group> --nsg-name <nsg-name> --name <rule-name> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. For each VM, open the Networking blade 2. Verify that the INBOUND PORT RULES does not have a rule for HTTP(S) such as - port = `80`/ `443`, - protocol = `TCP`, - Source = `Any` OR `Internet` **Audit from Azure CLI** List Network security groups with corresponding non-default Security rules: ``` az network nsg list --query [*].[name,securityRules] ``` Ensure that none of the NSGs have security rule as below ``` access : Allow destinationPortRange : 80/443 or * or [port range containing 80/443] direction : Inbound protocol : TCP sourceAddressPrefix : * or 0.0.0.0 or <nw>/0 or /0 or internet or any ```",
+ "AdditionalInformation": "",
+ "References": "Express Route: https://docs.microsoft.com/en-us/azure/expressroute/:Site-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal:Point-to-Site VPN: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-1-establish-network-segmentation-boundaries",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "7.5",
+ "Description": "Ensure that Network Security Group Flow Log Retention Days is Set to Greater than or equal to 90",
+ "Checks": [
+ "network_flow_log_more_than_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Network Security Group Flow Log Retention Days is Set to Greater than or equal to 90",
+ "RationaleStatement": "Virtual network flow logs provide critical visibility into traffic patterns. Logs can be used to check for anomalies and give insight into suspected breaches.",
+ "ImpactStatement": "* Virtual network flow logs are charged per gigabyte of network flow logs collected and come with a free tier of 5 GB/month per subscription. * If traffic analytics is enabled with virtual network flow logs, traffic analytics pricing applies at per gigabyte processing rates. * The storage of logs is charged separately, and the cost will depend on the amount of logs and the retention period.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down menu, select `Flow log type`. 1. From the `Value` drop-down menu, check `Virtual network` only. 1. Click `Apply`. 1. Click the name of a virtual network flow log. 1. Under `Storage Account`, set `Retention days` to `0`, `90`, or a number greater than 90. If `Retention days` is set to `0`, the logs are retained indefinitely with no retention policy. 1. Repeat steps 7 and 8 for each virtual network flow log requiring remediation. **Remediate from Azure CLI** Run the following command update the retention policy for a flow log in a network watcher, setting `retention` to `0`, `90`, or a number greater than 90: ``` az network watcher flow-log update --location <location> --name <flow-log> --retention <number-of-days> ``` Repeat for each virtual network flow log requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down menu, select `Flow log type`. 1. From the `Value` drop-down menu, check `Virtual network` only. 1. Click `Apply`. 1. Click the name of a virtual network flow log. 1. Under `Storage Account`, ensure that `Retention days` is set to `0`, `90`, or a number greater than 90. If `Retention days` is set to `0`, the logs are retained indefinitely with no retention policy. 1. Repeat steps 7 and 8 for each virtual network flow log. **Audit from Azure CLI** Run the following command to list network watchers: ``` az network watcher list ``` Run the following command to list the name and retention policy of flow logs in a network watcher: ``` az network watcher flow-log list --location <location> --query [*].[name,retentionPolicy] ``` For each flow log, ensure that `days` is set to `0`, `90`, or a number greater than 90. If `days` is set to `0`, the logs are retained indefinitely with no retention policy. Repeat for each network watcher.",
+ "AdditionalInformation": "As network security group flow logs are on the retirement path, Azure recommends migrating to virtual network flow logs.",
+ "References": "https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-portal:https://learn.microsoft.com/en-us/cli/azure/network/watcher/flow-log",
+ "DefaultValue": "When a virtual network flow log is created using the Azure CLI, retention days is set to 0 by default. When creating via the Azure Portal, retention days must be specified by the creator."
+ }
+ ]
+ },
+ {
+ "Id": "7.6",
+ "Description": "Ensure that Network Watcher is 'Enabled' for Azure Regions That are in Use",
+ "Checks": [
+ "network_watcher_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Network Watcher is 'Enabled' for Azure Regions That are in Use",
+ "RationaleStatement": "Network diagnostic and visualization tools available with Network Watcher help users understand, diagnose, and gain insights to the network in Azure.",
+ "ImpactStatement": "There are additional costs per transaction to run and store network data. For high-volume networks these charges will add up quickly.",
+ "RemediationProcedure": "Opting out of Network Watcher automatic enablement is a permanent change. Once you opt-out you cannot opt-in without contacting support. To manually enable Network Watcher in each region where you want to use Network Watcher capabilities, follow the steps below. **Remediate from Azure Portal** 1. Use the Search bar to search for and click on the `Network Watcher` service. 1. Click `Create`. 1. Select a `Region` from the drop-down menu. 1. Click `Add`. **Remediate from Azure CLI** ``` az network watcher configure --locations <region> --enabled true --resource-group <resource_group> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Use the Search bar to search for and click on the `Network Watcher` service. 1. From the Overview menu item, review each Network Watcher listed, and ensure that a network watcher is listed for each region in use by the subscription. **Audit from Azure CLI** ``` az network watcher list --query [].{Location:location,State:provisioningState} -o table ``` This will list all network watchers and their provisioning state. Ensure `provisioningState` is `Succeeded` for each network watcher. ``` az account list-locations --query [?metadata.regionType=='Physical'].{Name:name,DisplayName:regionalDisplayName} -o table ``` This will list all physical regions that exist in the subscription. Compare this list to the previous one to ensure that for each region in use, a network watcher exists with `provisioningState` set to `Succeeded`. **Audit from PowerShell** Get a list of Network Watchers ``` Get-AzNetworkWatcher ``` Make sure each watcher is set with the `ProvisioningState` setting set to `Succeeded` and all `Locations` that are in use by the subscription are using a watcher. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b6e2945c-0b7b-40f5-9233-7a5323b5cdc6](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb6e2945c-0b7b-40f5-9233-7a5323b5cdc6) **- Name:** 'Network Watcher should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview:https://learn.microsoft.com/en-us/cli/azure/network/watcher?view=azure-cli-latest:https://learn.microsoft.com/en-us/cli/azure/network/watcher?view=azure-cli-latest#az-network-watcher-configure:https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-create:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-4-enable-network-logging-for-security-investigation:https://azure.microsoft.com/en-ca/pricing/details/network-watcher/",
+ "DefaultValue": "Network Watcher is automatically enabled. When you create or update a virtual network in your subscription, Network Watcher will be enabled automatically in your Virtual Network's region. There is no impact to your resources or associated charge for automatically enabling Network Watcher."
+ }
+ ]
+ },
+ {
+ "Id": "7.7",
+ "Description": "Ensure that Public IP Addresses are Evaluated on a Periodic Basis",
+ "Checks": [
+ "network_public_ip_shodan"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Public IP Addresses are Evaluated on a Periodic Basis",
+ "RationaleStatement": "Public IP Addresses allocated to the tenant should be periodically reviewed for necessity. Public IP Addresses that are not intentionally assigned and controlled present a publicly facing vector for threat actors and significant risk to the tenant.",
+ "ImpactStatement": "Regular reviews require administrative effort.",
+ "RemediationProcedure": "Remediation will vary significantly depending on your organization's security requirements for the resources attached to each individual Public IP address.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Open the `All Resources` blade 2. Click on `Add Filter` 3. In the Add Filter window, select the following: Filter: `Type` Operator: `Equals` Value: `Public IP address` 4. Click the `Apply` button 5. For each Public IP address in the list, use Overview (or Properties) to review the `Associated to:` field and determine if the associated resource is still relevant to your tenant environment. If the associated resource is relevant, ensure that additional controls exist to mitigate risk (e.g. Firewalls, VPNs, Traffic Filtering, Virtual Gateway Appliances, Web Application Firewalls, etc.) on all subsequently attached resources. **Audit from Azure CLI** List all Public IP addresses: ``` az network public-ip list ``` For each Public IP address in the output, review the `name` property and determine if the associated resource is still relevant to your tenant environment. If the associated resource is relevant, ensure that additional controls exist to mitigate risk (e.g. Firewalls, VPNs, Traffic Filtering, Virtual Gateway Appliances, Web Application Firewalls, etc.) on all subsequently attached resources.",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/cli/azure/network/public-ip?view=azure-cli-latest:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security",
+ "DefaultValue": "During Virtual Machine and Application creation, a setting may create and attach a public IP."
+ }
+ ]
+ },
+ {
+ "Id": "7.8",
+ "Description": "Ensure that Virtual Network Flow Log Retention Days is Set to Greater than or Equal to 90",
+ "Checks": [
+ "network_flow_log_more_than_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Virtual Network Flow Log Retention Days is Set to Greater than or Equal to 90",
+ "RationaleStatement": "Virtual network flow logs provide critical visibility into traffic patterns. Logs can be used to check for anomalies and give insight into suspected breaches.",
+ "ImpactStatement": "* Virtual network flow logs are charged per gigabyte of network flow logs collected and come with a free tier of 5 GB/month per subscription. * If traffic analytics is enabled with virtual network flow logs, traffic analytics pricing applies at per gigabyte processing rates. * The storage of logs is charged separately, and the cost will depend on the amount of logs and the retention period.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down menu, select `Flow log type`. 1. From the `Value` drop-down menu, check `Virtual network` only. 1. Click `Apply`. 1. Click the name of a virtual network flow log. 1. Under `Storage Account`, set `Retention days` to `0`, `90`, or a number greater than 90. If `Retention days` is set to `0`, the logs are retained indefinitely with no retention policy. 1. Repeat steps 7 and 8 for each virtual network flow log requiring remediation. **Remediate from Azure CLI** Run the following command update the retention policy for a flow log in a network watcher, setting `retention` to `0`, `90`, or a number greater than 90: ``` az network watcher flow-log update --location <location> --name <flow-log> --retention <number-of-days> ``` Repeat for each virtual network flow log requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Network Watcher`. 1. Under `Logs`, select `Flow logs`. 1. Click `Add filter`. 1. From the `Filter` drop-down menu, select `Flow log type`. 1. From the `Value` drop-down menu, check `Virtual network` only. 1. Click `Apply`. 1. Click the name of a virtual network flow log. 1. Under `Storage Account`, ensure that `Retention days` is set to `0`, `90`, or a number greater than 90. If `Retention days` is set to `0`, the logs are retained indefinitely with no retention policy. 1. Repeat steps 7 and 8 for each virtual network flow log. **Audit from Azure CLI** Run the following command to list network watchers: ``` az network watcher list ``` Run the following command to list the name and retention policy of flow logs in a network watcher: ``` az network watcher flow-log list --location <location> --query [*].[name,retentionPolicy] ``` For each flow log, ensure that `days` is set to `0`, `90`, or a number greater than 90. If `days` is set to `0`, the logs are retained indefinitely with no retention policy. Repeat for each network watcher.",
+ "AdditionalInformation": "As network security group flow logs are on the retirement path, Azure recommends migrating to virtual network flow logs.",
+ "References": "https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-portal:https://learn.microsoft.com/en-us/cli/azure/network/watcher/flow-log",
+ "DefaultValue": "When a virtual network flow log is created using the Azure CLI, retention days is set to 0 by default. When creating via the Azure Portal, retention days must be specified by the creator."
+ }
+ ]
+ },
+ {
+ "Id": "7.9",
+ "Description": "Ensure 'Authentication type' is Set to 'Azure Active Directory' only for Azure VPN Gateway Point-to-Site Configuration",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Authentication type' is Set to 'Azure Active Directory' only for Azure VPN Gateway Point-to-Site Configuration",
+ "RationaleStatement": "Microsoft Entra ID authentication provides strong security and centralized identity management, and reduces risks associated with static credentials and certificate management.",
+ "ImpactStatement": "Azure VPN Gateways incur hourly charges, with additional costs for point-to-site connections and data transfer. Pricing varies by SKU and usage. Refer to https://azure.microsoft.com/en-us/pricing/details/vpn-gateway/ for details.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Virtual network gateways`. 2. Under `VPN gateway`, click `VPN gateways`. 3. Click the name of a VPN gateway. 4. Under `Settings`, click `Point-to-site configuration`. 5. Ensure `Authentication type` click to expand the drop-down menu. 6. Check the box next to `Azure Active Directory`, and uncheck the boxes next to `Azure certificate` and `RADIUS authentication`. 7. Provide a `Tenant`, `Audience`, and `Issuer` for the Azure Active Directory configuration. 8. Click `Save`. 9. Repeat steps 1-8 for each VPN gateway requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Virtual network gateways`. 2. Under `VPN gateway`, click `VPN gateways`. 3. Click the name of a VPN gateway. 4. Under `Settings`, click `Point-to-site configuration`. 5. Ensure `Authentication type` is set to `Azure Active Directory` only. 6. Repeat steps 1-5 for each VPN gateway. **Audit from Azure Policy** - **Policy ID:** 21a6bc25-125e-4d13-b82d-2e19b7208ab7 - **Name:** 'VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways:https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-entra-gateway:https://learn.microsoft.com/en-us/azure/vpn-gateway/openvpn-azure-ad-tenant",
+ "DefaultValue": "'Authentication type' is selected during creation of point-to-site configuration."
+ }
+ ]
+ },
+ {
+ "Id": "7.10",
+ "Description": "Ensure Azure Web Application Firewall (WAF) is Enabled on Azure Application Gateway",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Azure Web Application Firewall (WAF) is Enabled on Azure Application Gateway",
+ "RationaleStatement": "Using Azure Web Application Firewall with Azure Application Gateway reduces exposure to external threats by mitigating attacks on public facing applications.",
+ "ImpactStatement": "The WAF V2 tier for Azure Application Gateways costs more than the Basic and Standard V2 tiers. Pricing includes a fixed hourly charge plus a charge per capacity-unit hour. Refer to https://azure.microsoft.com/en-gb/pricing/details/application-gateway/ for details.",
+ "RemediationProcedure": "**Note:** Basic tier application gateways cannot be upgraded to the WAF V2 tier. Create a new WAF V2 tier application gateway to replace a Basic tier application gateway. **Remediate from Azure Portal** To remediate a Standard V2 tier application gateway: 1. Go to `Application gateways`. 2. Click `Add filter`. 3. From the `Filter` drop-down menu, select `SKU size`. 4. Check the box next to `Standard_v2` only. 5. Click `Apply`. 6. Click the name of an application gateway. 7. Under `Settings`, click `Web application firewall`. 8. Under `Configure`, next to `Tier`, click `WAF V2`. 9. Select an existing or create a new WAF policy. 10. Click `Save`. 11. Repeat steps 1-10 for each Standard V2 tier application gateway requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. In the `Overview`, under `Essentials`, ensure `Tier` is set to `WAF V2`. 4. Repeat steps 1-3 for each application gateway. **Audit from Azure CLI** Run the following command to list application gateways: ``` az network application-gateway list ``` For each application gateway, run the following command to get the firewall policy id: ``` az network application-gateway show --resource-group <resource-group> --name <application-gateway> --query firewallPolicy.id ``` Ensure a firewall policy id is returned. **Audit from Azure Policy** - **Policy ID:** 564feb30-bf6a-4854-b4bb-0d2d2d1e6c66 - **Name:** 'Web Application Firewall (WAF) should be enabled for Application Gateway'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/application-gateway/features:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway:https://azure.microsoft.com/en-us/pricing/details/application-gateway",
+ "DefaultValue": "Azure Web Application Firewall is enabled by default for the WAF V2 tier of Azure Application Gateway. It is not available in the Basic tier. Application gateways deployed using the Standard V2 tier can be upgraded to the WAF V2 tier to enable Azure Web Application Firewall."
+ }
+ ]
+ },
+ {
+ "Id": "7.11",
+ "Description": "Ensure Subnets Are Associated with Network Security Groups",
+ "Checks": [
+ "network_subnet_nsg_associated"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Subnets Are Associated with Network Security Groups",
+ "RationaleStatement": "Unprotected subnets can expose resources to unauthorized access.",
+ "ImpactStatement": "Minor administrative effort is required to ensure subnets are associated with network security groups. There is no cost to create or use network security groups.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Virtual networks`. 2. Click the name of a virtual network. 3. Under `Settings`, click `Subnets`. 4. Click the name of a subnet. 5. Under `Security`, next to `Network security group`, click `None` to display the drop-down menu. 6. Select a network security group. 7. Click `Save`. 8. Repeat steps 1-7 for each virtual network and subnet requiring remediation. **Remediate from Azure CLI** For each subnet requiring remediation, run the following command to associate it with a network security group: ``` az network vnet subnet update --resource-group <resource-group> --vnet-name <virtual-network> --name <subnet> --network-security-group <network-security-group> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Virtual networks`. 2. Click the name of a virtual network. 3. Under `Settings`, click `Subnets`. 4. Click the name of a subnet. 5. Under `Security`, ensure `Network security group` is not set to `None`. 6. Repeat steps 1-5 for each virtual network and subnet. **Audit from Azure CLI** Run the following command to list virtual networks: ``` az network vnet list ``` For each virtual network, run the following command to list subnets: ``` az network vnet show --resource-group <resource-group> --name <virtual-network> --query subnets ``` For each subnet, run the following command to get the network security group id: ``` az network vnet subnet show --resource-group <resource-group> --vnet-name <virtual-network> --name <subnet> --query networkSecurityGroup.id ``` Ensure a network security group id is returned. **Audit from Azure Policy** - **Policy ID:** e71308d3-144b-4262-b144-efdc3cc90517 - **Name:** 'Subnets should be associated with a Network Security Group'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview:https://learn.microsoft.com/en-us/cli/azure/network/vnet",
+ "DefaultValue": "By default, a subnet is not associated with a network security group."
+ }
+ ]
+ },
+ {
+ "Id": "7.12",
+ "Description": "Ensure the SSL Policy's 'Min protocol version' is Set to 'TLSv1_2' or Higher on Azure Application Gateway",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure the SSL Policy's 'Min protocol version' is Set to 'TLSv1_2' or Higher on Azure Application Gateway",
+ "RationaleStatement": "TLS 1.0 and 1.1 are outdated and vulnerable to security risks. Since TLS 1.2 and TLS 1.3 provide enhanced security and improved performance, it is highly recommended to use TLS 1.2 or higher whenever possible.",
+ "ImpactStatement": "Using the latest TLS version may affect compatibility with clients and backend services.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Listeners`. 4. Under `SSL Policy`, next to the Selected SSL Policy name, click `change`. 5. Select an appropriate SSL policy with a `Min protocol version` of `TLSv1_2` or higher. 6. Click `Save`. 7. Repeat steps 1-6 for each application gateway requiring remediation. **Remediate from Azure CLI** Run the following command to list available SSL policy options: ``` az network application-gateway ssl-policy list-options ``` Run the following command to list available predefined SSL policies: ``` az network application-gateway ssl-policy predefined list ``` For each application gateway requiring remediation, run the following command to set a predefined SSL policy: ``` az network application-gateway ssl-policy set --resource-group <resource-group> --gateway-name <application-gateway> --name <ssl-policy> --policy-type Predefined ``` Alternatively, run the following command to set a custom SSL policy: ``` az network application-gateway ssl-policy set --resource-group <resource-group> --gateway-name <application-gateway> --policy-type Custom --min-protocol-version <min-protocol-version> --cipher-suites <cipher-suites> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Listeners`. 4. Under `SSL Policy`, ensure `Min protocol version` is set to `TLSv1_2` or higher. 5. Repeat steps 1-4 for each application gateway. **Audit from Azure CLI** Run the following command to list application gateways: ``` az network application-gateway list ``` For each application gateway, run the following command to get the SSL policy: ``` az network application-gateway ssl-policy show --resource-group <resource-group> --gateway-name <application-gateway> ``` For each SSL policy, run the following command to get the minProtocolVersion: ``` az network application-gateway ssl-policy predefined show --name <ssl-policy> --query minProtocolVersion ``` Ensure `TLSv1_2` or higher is returned.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-ssl-policy-overview:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway",
+ "DefaultValue": "Min protocol version is set to TLSv1_2 by default."
+ }
+ ]
+ },
+ {
+ "Id": "7.13",
+ "Description": "Ensure 'HTTP2' is Set to 'Enabled' on Azure Application Gateway",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'HTTP2' is Set to 'Enabled' on Azure Application Gateway",
+ "RationaleStatement": "Enabling HTTP/2 supports use of modern encrypted connections.",
+ "ImpactStatement": "Clients and backend services that do not support HTTP/2 will fall back to HTTP/1.1.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Configuration`. 4. Under `HTTP2`, click `Enabled`. 5. Click `Save`. 6. Repeat steps 1-5 for each application gateway requiring remediation. **Remediate from Azure CLI** For each application gateway requiring remediation, run the following command to enable HTTP2: ``` az network application-gateway update --resource-group <resource-group> --name <application-gateway> --http2 Enabled ``` **Remediate from PowerShell** Run the following command to get the application gateway in a resource group with a given name: ``` $gateway = Get-AzApplicationGateway -ResourceGroupName <resource-group> -Name <application-gateway> ``` Run the following command to enable HTTP2: ``` $gateway.EnableHttp2 = $true ``` Run the following command to apply the update: ``` Set-AzApplicationGateway -ApplicationGateway $gateway ``` Repeat for each application gateway requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Configuration`. 4. Ensure `HTTP2` is set to `Enabled`. 5. Repeat steps 1-4 for each application gateway. **Audit from Azure CLI** Run the following command to list application gateways: ``` az network application-gateway list ``` For each application gateway, run the following command to get the HTTP2 setting: ``` az network application-gateway show --resource-group <resource-group> --name <application-gateway> --query enableHttp2 ``` Ensure `true` is returned. **Audit from PowerShell** Run the following command to list application gateways: ``` Get-AzApplicationGateway ``` Run the following command to get the application gateway in a resource group with a given name: ``` $gateway = Get-AzApplicationGateway -ResourceGroupName <resource-group> -Name <application-gateway> ``` Run the following command to get the HTTP2 setting: ``` $gateway.EnableHttp2 ``` Ensure that `True` is returned. Repeat for each application gateway.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/application-gateway/features#websocket-and-http2-traffic:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway:https://learn.microsoft.com/en-us/powershell/module/az.network/get-azapplicationgateway:https://learn.microsoft.com/en-us/powershell/module/az.network/set-azapplicationgateway",
+ "DefaultValue": "HTTP2 is enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "7.14",
+ "Description": "Ensure Request Body Inspection is Enabled in Azure Web Application Firewall policy on Azure Application Gateway",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Request Body Inspection is Enabled in Azure Web Application Firewall policy on Azure Application Gateway",
+ "RationaleStatement": "Enabling request body inspection strengthens security by allowing the Web Application Firewall to detect common attacks, such as SQL injection and cross-site scripting.",
+ "ImpactStatement": "Minor performance impact on the Web Application Firewall. Additional effort may be required to monitor findings.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Web application firewall`. 4. Under `Associated web application firewall policy`, click the policy name. 5. Under `Settings`, click `Policy settings`. 6. Check the box next to `Enforce request body inspection`. 7. Click `Save`. 8. Repeat steps 1-7 for each application gateway and firewall policy requiring remediation. **Remediate from Azure CLI** For each firewall policy requiring remediation, run the following command to enable request body inspection: ``` az network application-gateway waf-policy update --ids <firewall-policy> --policy-settings request-body-check=true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Web application firewall`. 4. Under `Associated web application firewall policy`, click the policy name. 5. Under `Settings`, click `Policy settings`. 6. Ensure the box next to `Enforce request body inspection` is checked. 7. Repeat steps 1-6 for each application gateway. **Audit from Azure CLI** Run the following command to list application gateways: ``` az network application-gateway list ``` For each application gateway, run the following command to get the firewall policy id: ``` az network application-gateway show --resource-group <resource-group> --name <application-gateway> --query firewallPolicy.id ``` For each firewall policy, run the following command to get the request body inspection setting: ``` az network application-gateway waf-policy show --ids <firewall-policy> --query policySettings.requestBodyCheck ``` Ensure `true` is returned. **Audit from Azure Policy** - **Policy ID:** ca85ef9a-741d-461d-8b7a-18c2da82c666 - **Name:** 'Azure Web Application Firewall on Azure Application Gateway should have request body inspection enabled'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-gb/azure/web-application-firewall/ag/application-gateway-waf-request-size-limits#request-body-inspection:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway/waf-policy",
+ "DefaultValue": "Request body inspection is enabled by default on Azure Application Gateways with Web Application Firewall."
+ }
+ ]
+ },
+ {
+ "Id": "7.15",
+ "Description": "Ensure Bot Protection is Enabled in Azure Web Application Firewall Policy on Azure Application Gateway",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Bot Protection is Enabled in Azure Web Application Firewall Policy on Azure Application Gateway",
+ "RationaleStatement": "Internet traffic from bots can scrape, scan, and search for application vulnerabilities. Enabling bot protection stops requests from known malicious IP addresses and enhances the overall security of your application by reducing exposure to automated attacks.",
+ "ImpactStatement": "May require monitoring to identify false positives.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Web application firewall`. 4. Under `Associated web application firewall policy`, click the policy name. 5. Under `Settings`, click `Managed rules`. 6. Click `Assign`. 7. Under `Bot Management ruleset`, click to display the drop-down menu. 8. Select a `Microsoft_BotManagerRuleSet`. 9. Click `Save`. 10. Click `X` to close the panel. 11. Repeat steps 1-10 for each application gateway and firewall policy requiring remediation. **Remediate from Azure CLI** For each firewall policy requiring remediation, run the following command to enable bot protection: ``` az network application-gateway waf-policy managed-rule rule-set add --resource-group <resource-group> --policy-name <firewall-policy> --type Microsoft_BotManagerRuleSet --version <0.1|1.0|1.1> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Application gateways`. 2. Click the name of an application gateway. 3. Under `Settings`, click `Web application firewall`. 4. Under `Associated web application firewall policy`, click the policy name. 5. Under `Settings`, click `Managed rules`. 6. Ensure a `Rule Id` containing `Microsoft_BotManagerRuleSet` is listed. 7. Click the `>` to expand the row. 8. Ensure the `Status` for `Malicious Bots` is set to `Enabled`. 9. Repeat steps 1-8 for each application gateway. **Audit from Azure CLI** Run the following command to list application gateways: ``` az network application-gateway list ``` For each application gateway, run the following command to get the firewall policy id: ``` az network application-gateway show --resource-group <resource-group> --name <application-gateway> --query firewallPolicy.id ``` For each firewall policy, run the following command to get the managed rule sets: ``` az network application-gateway waf-policy show --ids <firewall-policy> --query managedRules.managedRuleSets ``` Ensure a managed rule set with `ruleSetType` of `Microsoft_BotManagerRuleSet` is returned, and that no `ruleGroupOverrides` for `ruleGroupName` `KnownBadBots` with `state` `Disabled` are returned. **Audit from Azure Policy** - **Policy ID:** ebea0d86-7fbd-42e3-8a46-27e7568c2525 - **Name:** 'Bot Protection should be enabled for Azure Application Gateway WAF'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/bot-protection-overview:https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/bot-protection:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway/waf-policy:https://learn.microsoft.com/en-us/cli/azure/network/application-gateway/waf-policy/managed-rule/rule-set",
+ "DefaultValue": "Bot protection is disabled by default on Azure Application Gateways with Web Application Firewall."
+ }
+ ]
+ },
+ {
+ "Id": "7.16",
+ "Description": "Ensure Azure Network Security Perimeter is Used to Secure Azure Platform-as-a-service Resources",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 Networking Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Azure Network Security Perimeter is Used to Secure Azure Platform-as-a-service Resources",
+ "RationaleStatement": "Network security perimeter denies public access to PaaS resources, reducing exposure and mitigating data exfiltration risks.",
+ "ImpactStatement": "Implementation requires administrative effort to configure and maintain network security perimeter profiles and resource assignments. Azure does not list any additional charges for using network security perimeters.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Create and associate PaaS resources with a new network security perimeter: 1. Go to `Network Security Perimeters`. 2. Click `+ Create`. 3. Select a `Subscription` and `Resource group`, provide a `Name`, select a `Region`, and provide a `Profile name`. 4. Click `Next`. 5. Click `+ Add`. 6. Check the box next to a PaaS resource to associate it with the network security perimeter. 7. Click `Select`. 8. Click `Next`. 9. Configure appropriate `Inbound access rules` for your organization. 10. Click `Next`. 11. Configure appropriate `Outbound access rules` for your organization. 12. Click `Review + create`. 13. Click `Create`. **Remediate from Azure CLI** Use `az network perimeter profile list` or `az network perimeter profile create` to list existing or create a new network security perimeter profile. For each PaaS resource requiring association with a network security perimeter, run the following command: ``` az network perimeter association create --resource-group <resource-group> --perimeter-name <network-security-perimeter> --association-name <association> --private-link-resource \"{id:<paas-resource-id>}\" --profile \"{<profile-id>}\" ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Resource groups`. 2. Click the name of a resource group. 3. Take note of PaaS resources. 4. Go to `Network Security Perimeters`. 5. Click the name of a network security perimeter. 6. Under `Settings`, click `Associated resources`. 7. Take note of the associated resources. 8. Repeat steps 1-7 and ensure each PaaS resource is associated with a network security perimeter. **Audit from Azure CLI** Run the following command to list resource groups: ``` az group list ``` For each resource group, run the following command to list resources: ``` az resource list --resource-group <resource-group> ``` Take note of PaaS resources. For each resource group, run the following command to list network security perimeters: ``` az network perimeter list --resource-group <resource-group> ``` For each network security perimeter, run the following command to list resources: ``` az network perimeter association list --resource-group <resource-group> --perimeter-name <network-security-perimeter> ``` Ensure each PaaS resource is associated with a network security perimeter.",
+ "AdditionalInformation": "The current list of resources that can be associated with a network security perimeter are as follows: Azure Monitor, Azure AI Search, Cosmos DB, Event Hubs, Key Vault, SQL DB, Storage, Azure OpenAI Service. While network security perimeter is generally available, Cosmos DB, SQL DB, and Azure OpenAI Service are in public preview.",
+ "References": "https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts:https://learn.microsoft.com/en-us/azure/private-link/create-network-security-perimeter-portal:https://learn.microsoft.com/en-us/cli/azure/group:https://learn.microsoft.com/en-us/cli/azure/resource:https://learn.microsoft.com/en-us/cli/azure/network/perimeter",
+ "DefaultValue": "PaaS resources are not associated with a network security perimeter by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.1.1",
+ "Description": "Ensure Microsoft Defender CSPM is Set to 'On'",
+ "Checks": [
+ "defender_ensure_defender_cspm_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Microsoft Defender CSPM is Set to 'On'",
+ "RationaleStatement": "Microsoft Defender CSPM provides detailed visibility into the security state of assets and workloads and offers hardening guidance to help improve security posture.",
+ "ImpactStatement": "Enabling Microsoft Defender CSPM incurs hourly charges for each billable compute, database, and storage resource. This can lead to significant costs in larger environments. Careful planning and cost analysis are recommended before enabling the service. Refer to https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/#pricing for pricing information.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, click `Environment settings`. 3. Click the name of a subscription. 4. Select the `Defender plans` blade. 5. Under `Cloud Security Posture Management (CSPM)`, in the row for `Defender CSPM`, set the toggle switch for `Status` to `On`. 6. Click `Save`. **Remediate from Azure CLI** Run the following command to enable Defender CSPM: ``` az security pricing create --name CloudPosture --tier Standard --extensions name=ApiPosture isEnabled=true ``` **Remediate from PowerShell** Run the following command to enable Defender CSPM: ``` Set-AzSecurityPricing -Name CloudPosture -PricingTier Standard -Extension '[{\"name\":\"ApiPosture\",\"isEnabled\":\"True\"}]' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, click `Environment settings`. 3. Click the name of a subscription. 4. Select the `Defender plans` blade. 5. Under `Cloud Security Posture Management (CSPM)`, in the row for `Defender CSPM`, ensure `Status` is set to `On`. **Audit from Azure CLI** Run the following command to get the CloudPosture plan pricing tier: ``` az security pricing show --name CloudPosture --query pricingTier ``` Ensure `Standard` is returned. **Audit from PowerShell** Run the following command to get the CloudPosture plan pricing tier: ``` Get-AzSecurityPricing -Name CloudPosture | Select-Object PricingTier ``` Ensure `Standard` is returned. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [1f90fc71-a595-4066-8974-d4d0802e8ef0](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F1f90fc71-a595-4066-8974-d4d0802e8ef0) **- Name:** 'Microsoft Defender CSPM should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-cloud-security-posture-management:https://learn.microsoft.com/en-us/azure/defender-for-cloud/tutorial-enable-cspm-plan:https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/#pricing:https://learn.microsoft.com/en-us/cli/azure/security/pricing:https://learn.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/powershell/module/az.security/set-azsecuritypricing",
+ "DefaultValue": "Defender CSPM is disabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.2.1",
+ "Description": "Ensure Microsoft Defender for APIs is Set to 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_app_services_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Microsoft Defender for APIs is Set to 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for App Service allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Turning on Microsoft Defender for App Service incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud` 2. Under `Management`, select `Environment Settings` 3. Click on the subscription name 4. Select `Defender plans` 5. Set `App Service` Status to `On` 6. Select `Save` **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n Appservices --tier 'standard' ``` **Remediate from PowerShell** Run the following command: ``` Set-AzSecurityPricing -Name AppServices -PricingTier Standard ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud` 2. Under `Management`, select `Environment Settings` 3. Click on the subscription name 4. Select `Defender plans` 5. Ensure Status is `On` for `App Service` **Audit from Azure CLI** Run the following command: ``` az security pricing show -n AppServices ``` Ensure `-PricingTier` is set to `Standard` **Audit from PowerShell** Run the following command: ``` Get-AzSecurityPricing -Name 'AppServices' |Select-Object Name,PricingTier ``` Ensure the `-PricingTier` is set to `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [2913021d-f2fd-4f3d-b958-22354e2bdbcb](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F2913021d-f2fd-4f3d-b958-22354e2bdbcb) **- Name:** 'Azure Defender for App Service should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.3.1",
+ "Description": "Ensure that Defender for Servers is Set to 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_server_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Defender for Servers is Set to 'On'",
+ "RationaleStatement": "Enabling Defender for Servers allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Enabling Defender for Servers in Microsoft Defender for Cloud incurs an additional cost per resource. Refer to https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/ and https://azure.microsoft.com/en-us/pricing/calculator/ to estimate potential costs. - Plan 1: Subscription only - Plan 2: Subscription and workspace",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on a subscription name. 1. Click `Defender plans` in the left pane. 1. Under `Cloud Workload Protection (CWP)`, locate `Servers` in the Plan column, set Status to `On`. 1. Select `Save`. 1. Repeat steps 1-6 for each subscription requiring remediation. **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n VirtualMachines --tier 'standard' ``` **Remediate from PowerShell** Run the following command: ``` Set-AzSecurityPricing -Name 'VirtualMachines' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on a subscription name. 1. Select `Defender plans` in the left pane. 1. Under `Cloud Workload Protection (CWP)`, locate `Servers` in the Plan column, ensure Status is set to `On`. 1. Repeat steps 1-5 for each subscription. **Audit from Azure CLI** Run the following command: ``` az security pricing show -n VirtualMachines --query pricingTier ``` If the tenant is licensed and enabled, the output will indicate `Standard`. **Audit from PowerShell** Run the following command: ``` Get-AzSecurityPricing -Name 'VirtualMachines' |Select-Object Name,PricingTier ``` If the tenant is licensed and enabled, the `-PricingTier` parameter will indicate `Standard`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [4da35fc9-c9e7-4960-aec9-797fe7d9051d](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F4da35fc9-c9e7-4960-aec9-797fe7d9051d) **- Name:** 'Azure Defender for servers should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-servers-overview:https://learn.microsoft.com/en-us/azure/defender-for-cloud/plan-defender-for-servers:https://learn.microsoft.com/en-us/rest/api/defenderforcloud/pricings/list:https://learn.microsoft.com/en-us/rest/api/defenderforcloud/pricings/update:https://learn.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/powershell/module/az.security/set-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-endpoint-security#es-1-use-endpoint-detection-and-response-edr",
+ "DefaultValue": "By default, the Defender for Servers plan is disabled."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.3.2",
+ "Description": "Ensure that 'Vulnerability assessment for machines' Component Status is set to 'On'",
+ "Checks": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'Vulnerability assessment for machines' Component Status is set to 'On'",
+ "RationaleStatement": "Vulnerability assessment for machines scans for various security-related configurations and events such as system updates, OS vulnerabilities, and endpoint protection, then produces alerts on threat and vulnerability findings.",
+ "ImpactStatement": "Microsoft Defender for Servers plan 2 licensing is required, and configuration of Azure Arc introduces complexity beyond this recommendation.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Defender for Cloud` 1. Under `Management`, select `Environment Settings` 1. Select a subscription 1. Click on `Settings & Monitoring` 1. Set the `Status` of `Vulnerability assessment for machines` to `On` 1. Click `Continue` Repeat the above for any additional subscriptions.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Defender for Cloud` 1. Under `Management`, select `Environment Settings` 1. Select a subscription 1. Click on `Settings & monitoring` 1. Ensure that `Vulnerability assessment for machines` is set to `On` Repeat the above for any additional subscriptions.",
+ "AdditionalInformation": "While this feature is generally available as of publication, it is not yet available for Azure Government tenants.",
+ "References": "https://docs.microsoft.com/en-us/azure/defender-for-cloud/enable-data-collection?tabs=autoprovision-va:https://msdn.microsoft.com/en-us/library/mt704062.aspx:https://msdn.microsoft.com/en-us/library/mt704063.aspx:https://docs.microsoft.com/en-us/rest/api/securitycenter/autoprovisioningsettings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/autoprovisioningsettings/create:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-posture-vulnerability-management#pv-5-perform-vulnerability-assessments",
+ "DefaultValue": "By default, `Automatic provisioning of monitoring agent` is set to `Off`."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.3.3",
+ "Description": "Ensure that 'Endpoint protection' Component Status is set to 'On'",
+ "Checks": [
+ "defender_assessments_vm_endpoint_protection_installed"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Endpoint protection' Component Status is set to 'On'",
+ "RationaleStatement": "Microsoft Defender for Endpoint integration brings comprehensive Endpoint Detection and Response (EDR) capabilities within Microsoft Defender for Cloud. This integration helps to spot abnormalities, as well as detect and respond to advanced attacks on endpoints monitored by Microsoft Defender for Cloud. MDE works only with Standard Tier subscriptions.",
+ "ImpactStatement": "Endpoint protection requires licensing and is included in these plans: - Defender for Servers plan 1 - Defender for Servers plan 2",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment Settings`. 1. Click on the subscription name. 1. Click `Settings & monitoring`. 1. Set the `Status` for `Endpoint protection` to `On`. 1. Click `Continue`. **Remediate from Azure CLI** Use the below command to enable Standard pricing tier for Storage Accounts ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X PUT -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/<subscriptionID>/providers/Microsoft.Security/settings/WDATP?api-version=2021-06-01 -d@input.json' ``` Where input.json contains the Request body json data as mentioned below. ``` { id: /subscriptions/<Your_Subscription_Id>/providers/Microsoft.Security/settings/WDATP, kind: DataExportSettings, type: Microsoft.Security/settings, properties: { enabled: true } } ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment Settings`. 1. Click on the subscription name. 1. Click `Settings & monitoring`. 1. Ensure the `Status` for `Endpoint protection` is set to `On`. **Audit from Azure CLI** Ensure the output of the below command is `True` ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X GET -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/<subscriptionID>/providers/Microsoft.Security/settings?api-version=2021-06-01' | jq '.|.value[] | select(.name==WDATP)'|jq '.properties.enabled' ``` **Audit from PowerShell** Run the following commands to login and audit this check ``` Connect-AzAccount Set-AzContext -Subscription <subscriptionID> Get-AzSecuritySetting | Select-Object name,enabled |where-object {$_.name -eq WDATP} ``` **PowerShell Output - Non-Compliant** ``` Name Enabled ---- ------- WDATP False ``` **PowerShell Output - Compliant** ``` Name Enabled ---- ------- WDATP True ```",
+ "AdditionalInformation": "**IMPORTANT:** When enabling integration between DfE & DfC it needs to be taken into account that this will have some side effects that may be undesirable. 1. For server 2019 & above if defender is installed (default for these server SKUs) this will trigger a deployment of the new unified agent and link to any of the extended configuration in the Defender portal. 1. If the new unified agent is required for server SKUs of Win 2016 or Linux and lower there is additional integration that needs to be switched on and agents need to be aligned. NOTE: Microsoft Defender for Endpoint (MDE) was formerly known as Windows Defender Advanced Threat Protection (WDATP). There are a number of places (e.g. Azure CLI) where the WDATP acronym is still used within Azure.",
+ "References": "https://docs.microsoft.com/en-in/azure/defender-for-cloud/integration-defender-for-endpoint?tabs=windows:https://docs.microsoft.com/en-us/rest/api/securitycenter/settings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/settings/update:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-endpoint-security#es-1-use-endpoint-detection-and-response-edr:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-endpoint-security#es-2-use-modern-anti-malware-software",
+ "DefaultValue": "By default, Endpoint protection is `off`."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.3.4",
+ "Description": "Ensure that 'Agentless scanning for machines' Component Status is Set to 'On'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'Agentless scanning for machines' Component Status is Set to 'On'",
+ "RationaleStatement": "The Microsoft Defender for Cloud agentless machine scanner provides threat detection, vulnerability detection, and discovery of sensitive information.",
+ "ImpactStatement": "Agentless scanning for machines requires licensing and is included in these plans: - Defender CSPM - Defender for Servers plan 2",
+ "RemediationProcedure": "**Audit from Azure Portal** 1. From the Azure Portal `Home` page, select `Microsoft Defender for Cloud` 1. Under `Management` select `Environment Settings` 1. Select a subscription 1. Under `Settings` > `Defender Plans`, click `Settings & monitoring` 1. Under the Component column, locate the row for `Agentless scanning for machines` 1. Select `On` 1. Click `Continue` in the top left Repeat the above for any additional subscriptions.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From the Azure Portal `Home` page, select `Microsoft Defender for Cloud` 1. Under `Management` select `Environment Settings` 1. Select a subscription 1. Under `Settings` > `Defender Plans`, click `Settings & monitoring` 1. Under the Component column, locate the row for `Agentless scanning for machines` 1. Ensure that `On` is selected Repeat the above for any additional subscriptions.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-agentless-data-collection:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response#ir-2-preparation---setup-incident-notification:https://learn.microsoft.com/en-us/azure/defender-for-cloud/enable-agentless-scanning-vms",
+ "DefaultValue": "By default, Agentless scanning for machines is `off`."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.3.5",
+ "Description": "Ensure that 'File Integrity Monitoring' Component Status is Set to 'On'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that 'File Integrity Monitoring' Component Status is Set to 'On'",
+ "RationaleStatement": "FIM provides a detection mechanism for compromised files. When FIM is enabled, critical system files are monitored for changes that might indicate a threat actor is attempting to modify system files for lateral compromise within a host operating system.",
+ "ImpactStatement": "File Integrity Monitoring requires licensing and is included in these plans: - Defender for Servers plan 2",
+ "RemediationProcedure": "**Audit from Azure Portal** 1. From the Azure Portal `Home` page, select `Microsoft Defender for Cloud` 1. Under `Management` select `Environment Settings` 1. Select a subscription 1. Under `Settings` > `Defender Plans`, click `Settings & monitoring` 1. Under the Component column, locate the row for `File Integrity Monitoring` 1. Select `On` 1. Click `Continue` in the top left Repeat the above for any additional subscriptions.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From the Azure Portal `Home` page, select `Microsoft Defender for Cloud` 1. Under `Management` select `Environment Settings` 1. Select a subscription 1. Under `Settings` > `Defender Plans`, click `Settings & monitoring` 1. Under the Component column, locate the row for `File Integrity Monitoring` 1. Ensure that `On` is selected Repeat the above for any additional subscriptions.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/file-integrity-monitoring-overview:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response#ir-2-preparation---setup-incident-notification:https://learn.microsoft.com/en-us/azure/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint",
+ "DefaultValue": "By default, File Integrity Monitoring is `Off`."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.4.1",
+ "Description": "Ensure That Microsoft Defender for Containers Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_containers_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Containers Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for Containers enhances defense-in-depth by providing advanced threat detection, vulnerability assessment, and security monitoring for containerized environments, leveraging insights from the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Microsoft Defender for Containers incurs a charge per vCore. Refer to https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/ and https://azure.microsoft.com/en-us/pricing/calculator/ to estimate potential costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, click `Environment settings`. 1. Click the name of a subscription. 1. Under `Settings`, click `Defender plans`. 1. Under `Cloud Workload Protection (CWP)`, in the row for `Containers`, click `On` in the `Status` column. 1. If `Monitoring coverage` displays `Partial`, click `Settings` under `Partial`. 1. Set the status of each of the components to `On`. 1. Click `Continue`. 1. Click `Save`. 1. Repeat steps 1-9 for each subscription. **Remediate from Azure CLI** **Note:** Microsoft Defender for Container Registries ('ContainerRegistry') is deprecated and has been replaced by Microsoft Defender for Containers ('Containers'). Run the below command to enable the Microsoft Defender for Containers plan and its components: ``` az security pricing create -n 'Containers' --tier 'standard' --extensions name=ContainerRegistriesVulnerabilityAssessments isEnabled=True --extensions name=AgentlessDiscoveryForKubernetes isEnabled=True --extensions name=AgentlessVmScanning isEnabled=True --extensions name=ContainerSensor isEnabled=True ``` **Remediate from PowerShell** **Note:** Microsoft Defender for Container Registries ('ContainerRegistry') is deprecated and has been replaced by Microsoft Defender for Containers ('Containers'). Run the below command to enable the Microsoft Defender for Containers plan and its components: ``` Set-AzSecurityPricing -Name 'Containers' -PricingTier 'Standard' -Extension '[{name:ContainerRegistriesVulnerabilityAssessments,isEnabled:True},{name:AgentlessDiscoveryForKubernetes,isEnabled:True},{name:AgentlessVmScanning,isEnabled:True},{name:ContainerSensor,isEnabled:True}]' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, click `Environment settings`. 1. Click the name of a subscription. 1. Under `Settings`, click `Defender plans`. 1. Under `Cloud Workload Protection (CWP)`, in the row for `Containers`, ensure that the `Status` is set to `On` and `Monitoring coverage` displays `Full`. 1. Repeat steps 1-5 for each subscription. **Audit from Azure CLI** For Microsoft Defender for Container Registries (deprecated), run the following command: ``` az security pricing show --name ContainerRegistry --query pricingTier ``` Ensure that the command returns `Standard`. For Microsoft Defender for Containers, run the following command: ``` az security pricing show --name Containers --query [pricingTier,extensions[*].[name,isEnabled]] ``` Ensure that the command returns `Standard`, and that each of the extensions (ContainerRegistriesVulnerabilityAssessments, AgentlessDiscoveryForKubernetes, AgentlessVmScanning, ContainerSensor) returns `True`. Repeat for each subscription. **Audit from PowerShell** For Microsoft Defender for Container Registries (deprecated), run the following command: ``` Get-AzSecurityPricing -Name 'ContainerRegistry' | Select-Object Name,PricingTier ``` Ensure the command returns `PricingTier` `Standard`. For Microsoft Defender for Containers, run the following command: ``` Get-AzSecurityPricing -Name 'Containers' ``` Ensure that `PricingTier` is set to `Standard`, and that each of the extensions (ContainerRegistriesVulnerabilityAssessments, AgentlessDiscoveryForKubernetes, AgentlessVmScanning, ContainerSensor) has `isEnabled` set to `True`. Repeat for each subscription. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [1c988dd6-ade4-430f-a608-2a3e5b0a6d38](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F1c988dd6-ade4-430f-a608-2a3e5b0a6d38) **- Name:** 'Microsoft Defender for Containers should be enabled'",
+ "AdditionalInformation": "The Azure Policy 'Microsoft Defender for Containers should be enabled' checks only that the `pricingTier` for `Containers` is set to `Standard`. It does not check the status of the plan's components.",
+ "References": "https://learn.microsoft.com/en-us/cli/azure/security/pricing:https://learn.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/powershell/module/az.security/set-azsecuritypricing:https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-containers-introduction:https://learn.microsoft.com/en-us/azure/defender-for-cloud/tutorial-enable-containers-azure:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "The Microsoft Defender for Containers plan is disabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.5.1",
+ "Description": "Ensure That Microsoft Defender for Storage Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_storage_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Storage Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for Storage allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Turning on Microsoft Defender for Storage incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Set `Status` to `On` for `Storage`. 6. Select `Save`. **Remediate from Azure CLI** Ensure the output of the below command is Standard ``` az security pricing create -n StorageAccounts --tier 'standard' ``` **Remediate from PowerShell** ``` Set-AzSecurityPricing -Name 'StorageAccounts' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Ensure `Status` is set to `On` for `Storage`. **Audit from Azure CLI** Ensure the output of the below command is Standard ``` az security pricing show -n StorageAccounts ``` **Audit from PowerShell** ``` Get-AzSecurityPricing -Name 'StorageAccounts' | Select-Object Name,PricingTier ``` Ensure output for `Name PricingTier` is `StorageAccounts Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [640d2586-54d2-465f-877f-9ffc1d2109f4](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F640d2586-54d2-465f-877f-9ffc1d2109f4) **- Name:** 'Microsoft Defender for Storage should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.5.2",
+ "Description": "Ensure Advanced Threat Protection Alerts for Storage Accounts Are Monitored",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Advanced Threat Protection Alerts for Storage Accounts Are Monitored",
+ "RationaleStatement": "Enabling Microsoft Defender for Storage without a monitoring process limits its value. Continuous monitoring and alert triage ensure that detected threats are acted upon quickly, reducing risk exposure.",
+ "ImpactStatement": "Requires integration effort with SIEM or alerting tools and a defined incident response process. The amount of data logged and, thus, the cost incurred can vary significantly depending on the tenant size and the applications in your tenant that interact with the Microsoft Graph APIs. See pricing: Log Analytics (https://learn.microsoft.com/en-us/azure/azure-monitor/logs/cost-logs#pricing-model), Azure Storage (https://azure.microsoft.com/en-us/pricing/details/storage/blobs/), Event Hubs (https://azure.microsoft.com/en-us/pricing/details/event-hubs/).",
+ "RemediationProcedure": "Connect Microsoft Defender for Cloud to a SIEM such as Microsoft Sentinel or another log analytics solution. **Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, click `Environment Settings`. 3. Expand the Tenant Root Group(s) to reveal subscriptions. For each subscription listed: 1. Click the subscription name to open the Defender Plans settings 2. In the settings on the left, click `Continuous Export` 3. Select either `Event Hub`, `Log Analytics Workspace`, or both depending on your environment. 4. Set `Export enabled` to `On` 5. Under `Exported data types`, ensure that at least `Security Alerts (Medium and High)` is checked. 6. Under `Export target`, set the target Event Hub or Log Analytics Workspace which is tied to a SIEM that is configured to monitor and alert for security alerts. Ensure security alerts are included in the security operations workflow and incident response plan.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, click `Environment Settings`. 3. Expand the Tenant Root Group(s) to reveal subscriptions. For each subscription listed: 1. Click the subscription name to open the Defender Plans settings 2. In the settings on the left, click `Continuous Export` Ensure that `Export enabled` is set to `On` and delivering at least `Security Alerts (Medium and High)` to an Event Hub or Log Analytics Workspace which is tied to a SIEM that is configured to monitor and alert for security alerts.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/azure/defender-for-cloud/alerts-overview:https://learn.microsoft.com/azure/sentinel/connect-defender-for-cloud:https://learn.microsoft.com/en-us/azure/defender-for-cloud/continuous-export",
+ "DefaultValue": "By default, continuous export is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.6.1",
+ "Description": "Ensure That Microsoft Defender for App Services Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_app_services_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for App Services Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for App Service allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Turning on Microsoft Defender for App Service incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud` 2. Under `Management`, select `Environment Settings` 3. Click on the subscription name 4. Select `Defender plans` 5. Set `App Service` Status to `On` 6. Select `Save` **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n Appservices --tier 'standard' ``` **Remediate from PowerShell** Run the following command: ``` Set-AzSecurityPricing -Name AppServices -PricingTier Standard ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud` 2. Under `Management`, select `Environment Settings` 3. Click on the subscription name 4. Select `Defender plans` 5. Ensure Status is `On` for `App Service` **Audit from Azure CLI** Run the following command: ``` az security pricing show -n AppServices ``` Ensure `-PricingTier` is set to `Standard` **Audit from PowerShell** Run the following command: ``` Get-AzSecurityPricing -Name 'AppServices' |Select-Object Name,PricingTier ``` Ensure the `-PricingTier` is set to `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [2913021d-f2fd-4f3d-b958-22354e2bdbcb](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F2913021d-f2fd-4f3d-b958-22354e2bdbcb) **- Name:** 'Azure Defender for App Service should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.7.1",
+ "Description": "Ensure That Microsoft Defender for Azure Cosmos DB Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_cosmosdb_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Azure Cosmos DB Is Set To 'On'",
+ "RationaleStatement": "In scanning Azure Cosmos DB requests within a subscription, requests are compared to a heuristic list of potential security threats. These threats could be a result of a security breach within your services, thus scanning for them could prevent a potential security threat from being introduced.",
+ "ImpactStatement": "Enabling Microsoft Defender for Azure Cosmos DB requires enabling Microsoft Defender for your subscription. Both will incur additional charges.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. On the `Database` row click on `Select types >`. 6. Set the toggle switch next to `Azure Cosmos DB` to `On`. 7. Click `Continue`. 8. Click `Save`. **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n 'CosmosDbs' --tier 'standard' ``` **Remediate from PowerShell** Use the below command to enable Standard pricing tier for Azure Cosmos DB ``` Set-AzSecurityPricing -Name 'CosmosDbs' -PricingTier 'Standard ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. On the `Database` row click on `Select types >`. 6. Ensure the toggle switch next to `Azure Cosmos DB` is set to `On`. **Audit from Azure CLI** Ensure the output of the below command is Standard ``` az security pricing show -n CosmosDbs --query pricingTier ``` **Audit from PowerShell** ``` Get-AzSecurityPricing -Name 'CosmosDbs' | Select-Object Name,PricingTier ``` Ensure output of `-PricingTier` is `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [adbe85b5-83e6-4350-ab58-bf3a4f736e5e](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fadbe85b5-83e6-4350-ab58-bf3a4f736e5e) **- Name:** 'Microsoft Defender for Azure Cosmos DB should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/:https://docs.microsoft.com/en-us/azure/defender-for-cloud/enable-enhanced-security:https://docs.microsoft.com/en-us/azure/defender-for-cloud/alerts-overview:https://docs.microsoft.com/en-us/security/benchmark/azure/baselines/cosmos-db-security-baseline:https://docs.microsoft.com/en-us/azure/defender-for-cloud/quickstart-enable-database-protections:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender for Azure Cosmos DB is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.7.2",
+ "Description": "Ensure That Microsoft Defender for Open-Source Relational Databases Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_os_relational_databases_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Open-Source Relational Databases Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for Open-source relational databases allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Turning on Microsoft Defender for Open-source relational databases incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Click `Select types >` in the row for `Databases`. 6. Set the toggle switch next to `Open-source relational databases` to `On`. 7. Select `Continue`. 8. Select `Save`. **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n 'OpenSourceRelationalDatabases' --tier 'standard' ``` **Remediate from PowerShell** Use the below command to enable Standard pricing tier for Open-source relational databases ``` set-azsecuritypricing -name OpenSourceRelationalDatabases -pricingtier Standard ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment Settings`. 1. Click on the subscription name. 1. Select the `Defender plans` blade. 1. Click `Select types >` in the row for `Databases`. 1. Ensure the toggle switch next to `Open-source relational databases` is set to `On`. **Audit from Azure CLI** Run the following command: ``` az security pricing show -n OpenSourceRelationalDatabases --query pricingTier ``` **Audit from PowerShell** ``` Get-AzSecurityPricing | Where-Object {$_.Name -eq 'OpenSourceRelationalDatabases'} | Select-Object Name, PricingTier ``` Ensure output for `Name PricingTier` is `OpenSourceRelationalDatabases Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [0a9fbe0d-c5c4-4da8-87d8-f4fd77338835](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F0a9fbe0d-c5c4-4da8-87d8-f4fd77338835) **- Name:** 'Azure Defender for open-source relational databases should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-2-monitor-anomalies-and-threats-targeting-sensitive-data:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.7.3",
+ "Description": "Ensure That Microsoft Defender for (Managed Instance) Azure SQL Databases Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_azure_sql_databases_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for (Managed Instance) Azure SQL Databases Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for Azure SQL Databases allows for greater defense-in-depth, includes functionality for discovering and classifying sensitive data, surfacing and mitigating potential database vulnerabilities, and detecting anomalous activities that could indicate a threat to your database.",
+ "ImpactStatement": "Turning on Microsoft Defender for Azure SQL Databases incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Click `Select types >` in the row for `Databases`. 6. Set the toggle switch next to `Azure SQL Databases` to `On`. 7. Select `Continue`. 8. Select `Save`. **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n SqlServers --tier 'standard' ``` **Remediate from PowerShell** Run the following command: ``` Set-AzSecurityPricing -Name 'SqlServers' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Click `Select types >` in the row for `Databases`. 6. Ensure the toggle switch next to `Azure SQL Databases` is set to `On`. **Audit from Azure CLI** Run the following command: ``` az security pricing show -n SqlServers ``` Ensure `-PricingTier` is set to `Standard` **Audit from PowerShell** Run the following command: ``` Get-AzSecurityPricing -Name 'SqlServers' | Select-Object Name,PricingTier ``` Ensure the `-PricingTier` is set to `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [7fe3b40f-802b-4cdd-8bd4-fd799c948cc2](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F7fe3b40f-802b-4cdd-8bd4-fd799c948cc2) **- Name:** 'Azure Defender for Azure SQL Database servers should be enabled' - **Policy ID:** [abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fabfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) **- Name:** 'Azure Defender for SQL should be enabled for unprotected SQL Managed Instances'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-2-monitor-anomalies-and-threats-targeting-sensitive-data:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.7.4",
+ "Description": "Ensure That Microsoft Defender for SQL Servers on Machines Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_sql_servers_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for SQL Servers on Machines Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for SQL servers on machines allows for greater defense-in-depth, functionality for discovering and classifying sensitive data, surfacing and mitigating potential database vulnerabilities, and detecting anomalous activities that could indicate a threat to your database.",
+ "ImpactStatement": "Turning on Microsoft Defender for SQL servers on machines incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Click `Select types >` in the row for `Databases`. 6. Set the toggle switch next to `SQL servers on machines` to `On`. 7. Select `Continue`. 8. Select `Save`. **Remediate from Azure CLI** Run the following command: ``` az security pricing create -n SqlServerVirtualMachines --tier 'standard' ``` **Remediate from PowerShell** Run the following command: ``` Set-AzSecurityPricing -Name 'SqlServerVirtualMachines' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Click `Select types >` in the row for `Databases`. 6. Ensure the toggle switch next to `SQL servers on machines` is set to `On`. **Audit from Azure CLI** Ensure Defender for SQL is licensed with the following command: ``` az security pricing show -n SqlServerVirtualMachines ``` Ensure the 'PricingTier' is set to 'Standard' **Audit from PowerShell** Run the following command: ``` Get-AzSecurityPricing -Name 'SqlServerVirtualMachines' | Select-Object Name,PricingTier ``` Ensure the 'PricingTier' is set to 'Standard' **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [6581d072-105e-4418-827f-bd446d56421b](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F6581d072-105e-4418-827f-bd446d56421b) **- Name:** 'Azure Defender for SQL servers on machines should be enabled' - **Policy ID:** [abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fabfb4388-5bf4-4ad7-ba82-2cd2f41ceae9) **- Name:** 'Azure Defender for SQL should be enabled for unprotected Azure SQL servers'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/defender-for-sql-usage:https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-2-monitor-anomalies-and-threats-targeting-sensitive-data:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.8.1",
+ "Description": "Ensure That Microsoft Defender for Key Vault Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_keyvault_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Key Vault Is Set To 'On'",
+ "RationaleStatement": "Enabling Microsoft Defender for Key Vault allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).",
+ "ImpactStatement": "Turning on Microsoft Defender for Key Vault incurs an additional cost per resource.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Select `On` under `Status` for `Key Vault`. 6. Select `Save`. **Remediate from Azure CLI** Enable Standard pricing tier for Key Vault: ``` az security pricing create -n 'KeyVaults' --tier 'Standard' ``` **Remediate from PowerShell** Enable Standard pricing tier for Key Vault: ``` Set-AzSecurityPricing -Name 'KeyVaults' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Ensure `Status` is set to `On` for `Key Vault`. **Audit from Azure CLI** Ensure the output of the below command is Standard ``` az security pricing show -n 'KeyVaults' --query 'pricingTier' ``` **Audit from PowerShell** ``` Get-AzSecurityPricing -Name 'KeyVaults' | Select-Object Name,PricingTier ``` Ensure output for `PricingTier` is `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [0e6763cc-5078-4e64-889d-ff4d9a839047](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F0e6763cc-5078-4e64-889d-ff4d9a839047) **- Name:** 'Azure Defender for Key Vault should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update:https://docs.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender plan is off."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.9.1",
+ "Description": "Ensure That Microsoft Defender for Resource Manager Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_defender_for_arm_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Microsoft Defender for Resource Manager Is Set To 'On'",
+ "RationaleStatement": "Scanning resource requests lets you be alerted every time there is suspicious activity in order to prevent a security threat from being introduced.",
+ "ImpactStatement": "Enabling Microsoft Defender for Resource Manager requires enabling Microsoft Defender for your subscription. Both will incur additional charges.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Select `On` under `Status` for `Resource Manager`. 6. Select `Save. **Remediate from Azure CLI** Use the below command to enable Standard pricing tier for Defender for Resource Manager ``` az security pricing create -n 'Arm' --tier 'Standard' ``` **Remediate from PowerShell** Use the below command to enable Standard pricing tier for Defender for Resource Manager ``` Set-AzSecurityPricing -Name 'Arm' -PricingTier 'Standard' ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender for Cloud`. 2. Under `Management`, select `Environment Settings`. 3. Click on the subscription name. 4. Select the `Defender plans` blade. 5. Ensure `Status` is set to `On` for `Resource Manager`. **Audit from Azure CLI** Ensure the output of the below command is Standard ``` az security pricing show -n 'Arm' --query 'pricingTier' ``` **Audit from PowerShell** ``` Get-AzSecurityPricing -Name 'Arm' | Select-Object Name,PricingTier ``` Ensure the output of `PricingTier` is `Standard` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [c3d20c29-b36d-48fe-808b-99a87530ad99](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc3d20c29-b36d-48fe-808b-99a87530ad99) **- Name:** 'Azure Defender for Resource Manager should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/defender-for-cloud/enable-enhanced-security:https://docs.microsoft.com/en-us/azure/defender-for-cloud/defender-for-resource-manager-introduction:https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/:https://docs.microsoft.com/en-us/azure/defender-for-cloud/alerts-overview:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities",
+ "DefaultValue": "By default, Microsoft Defender for Resource Manager is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.10",
+ "Description": "Ensure that Microsoft Defender for Cloud is Configured to Check VM Operating Systems for Updates",
+ "Checks": [
+ "defender_ensure_system_updates_are_applied"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Microsoft Defender for Cloud is Configured to Check VM Operating Systems for Updates",
+ "RationaleStatement": "Windows and Linux virtual machines should be kept updated to: - Address a specific bug or flaw - Improve an OS or applications general stability - Fix a security vulnerability Microsoft Defender for Cloud retrieves a list of available security and critical updates from Windows Update or Windows Server Update Services (WSUS), depending on which service is configured on a Windows VM. The security center also checks for the latest updates in Linux systems. If a VM is missing a system update, the security center will recommend system updates be applied.",
+ "ImpactStatement": "Running Microsoft Defender for Cloud incurs additional charges for each resource monitored. Please see attached reference for exact charges per hour.",
+ "RemediationProcedure": "Follow Microsoft Azure documentation to apply security patches from the security center. Alternatively, you can employ your own patch assessment and management tool to periodically assess, report, and install the required security patches for your OS.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Defender for Cloud` 1. Then the `Recommendations` blade 1. Ensure that there are no recommendations for `System updates should be installed on your machines (powered by Update Center)` Alternatively, you can employ your own patch assessment and management tool to periodically assess, report and install the required security patches for your OS. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [f85bf3e0-d513-442e-89c3-1784ad63382b](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff85bf3e0-d513-442e-89c3-1784ad63382b) **- Name:** 'System updates should be installed on your machines (powered by Update Center)' - **Policy ID:** [bd876905-5b84-4f73-ab2d-2e7a7c4568d9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fbd876905-5b84-4f73-ab2d-2e7a7c4568d9) **- Name:** 'Machines should be configured to periodically check for missing system updates'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-posture-vulnerability-management#pv-6-rapidly-and-automatically-remediate-vulnerabilities:https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/:https://docs.microsoft.com/en-us/azure/defender-for-cloud/deploy-vulnerability-assessment-vm",
+ "DefaultValue": "By default, patches are not automatically deployed."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.11",
+ "Description": "Ensure that non-deprecated Microsoft Cloud Security Benchmark policies are not set to 'Disabled'",
+ "Checks": [
+ "policy_ensure_asc_enforcement_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that non-deprecated Microsoft Cloud Security Benchmark policies are not set to 'Disabled'",
+ "RationaleStatement": "A security policy defines the desired configuration of resources in your environment and helps ensure compliance with company or regulatory security requirements. The MCSB Policy Initiative a set of security recommendations based on best practices and is associated with every subscription by default. When a policy Effect is set to `Audit`, policies in the MCSB ensure that Defender for Cloud evaluates relevant resources for supported recommendations. To ensure that policies within the MCSB are not being missed when the Policy Initiative is evaluated, none of the policies should have an Effect of `Disabled`.",
+ "ImpactStatement": "Policies within the MCSB default to an effect of `Audit` and will evaluate—but not enforce—policy recommendations. Ensuring these policies are set to `Audit` simply ensures that the evaluation occurs to allow administrators to understand where an improvement may be possible. Administrators will need to determine if the recommendations are relevant and desirable for their environment, then manually take action to resolve the status if desired.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Management Group or Subscription. 1. Click on `Security policies` in the left column. 1. Click on `Microsoft cloud security benchmark` 1. Click `Add Filter` and select `Effect` 1. Check the `Disabled` box to search for all disabled policies 1. Click `Apply` 1. Click the blue ellipsis `...` to the right of a policy name. 1. Click `Manage effect and parameters`. 1. Under `Policy effect`, select the radio button next to `Audit`. 1. Click `Save`. 1. Click `Refresh`. 1. Repeat steps 10-14 until all disabled policies are updated. 1. Repeat steps 1-15 for each Management Group or Subscription requiring remediation.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Management Group or Subscription. 1. Click on `Security policies` in the left column. 1. Click on `Microsoft cloud security benchmark`. 1. Click `Add filter` and select `Effect`. 1. Check the `Disabled` box to search for all disabled policies. 1. Click `Apply`. 1. Ensure that no policies are displayed, signifying that there are no disabled policies. 1. Repeat steps 1-10 for each Management Group or Subscription.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-in/azure/defender-for-cloud/security-policy-concept:https://docs.microsoft.com/en-us/azure/security-center/security-center-policies:https://learn.microsoft.com/en-us/azure/defender-for-cloud/implement-security-recommendations:https://learn.microsoft.com/en-us/rest/api/policy/policy-assignments/get:https://learn.microsoft.com/en-us/rest/api/policy/policy-assignments/create:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-7-define-and-implement-logging-threat-detection-and-incident-response-strategy",
+ "DefaultValue": "By default, the MCSB policy initiative is assigned on all subscriptions, and **most** policies will have an effect of `Audit`. Some policies will have a default effect of `Disabled`."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.12",
+ "Description": "Ensure That 'All users with the following roles' is Set to 'Owner'",
+ "Checks": [
+ "defender_ensure_notify_emails_to_owners"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That 'All users with the following roles' is Set to 'Owner'",
+ "RationaleStatement": "Enabling security alert emails to subscription owners ensures that they receive security alert emails from Microsoft. This ensures that they are aware of any potential security issues and can mitigate the risk in a timely fashion.",
+ "ImpactStatement": "Owners will receive email notifications for security alerts.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Defender for Cloud` 1. Under `Management`, select `Environment Settings` 1. Click on the appropriate Management Group, Subscription, or Workspace 1. Click on `Email notifications` 1. In the drop down of the `All users with the following roles` field select `Owner` 1. Click `Save` **Remediate from Azure CLI** Use the below command to set `Send email also to subscription owners` to `On`. ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X PUT -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts/default1?api-version=2017-08-01-preview -d@input.json' ``` Where `input.json` contains the data below, replacing `validEmailAddress` with a single email address or multiple comma-separated email addresses: ``` { id: /subscriptions/<Your_Subscription_Id>/providers/Microsoft.Security/securityContacts/default1, name: default1, type: Microsoft.Security/securityContacts, properties: { email: <validEmailAddress>, alertNotifications: On, alertsToAdmins: On, notificationsByRole: Owner } } ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu 1. Select `Microsoft Defender for Cloud` 1. Under `Management`, select `Environment Settings` 1. Click on the appropriate Management Group, Subscription, or Workspace 1. Click on `Email notifications` 1. Ensure that `All users with the following roles` is set to `Owner` **Audit from Azure CLI** Ensure the command below returns state of `On` and that `Owner` appears in roles. ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X GET -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts?api-version=2020-01-01-preview'| jq '.[] | select(.name==default).properties.notificationsByRole' ```",
+ "AdditionalInformation": "Excluding any entries in the input.json properties block disables the specific setting by default.",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-provide-security-contact-details:https://docs.microsoft.com/en-us/rest/api/securitycenter/securitycontacts/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/security-contacts:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response#ir-2-preparation---setup-incident-notification",
+ "DefaultValue": "By default, `Owner` is selected"
+ }
+ ]
+ },
+ {
+ "Id": "8.1.13",
+ "Description": "Ensure 'Additional email addresses' is Configured with a Security Contact Email",
+ "Checks": [
+ "defender_additional_email_configured_with_a_security_contact"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Additional email addresses' is Configured with a Security Contact Email",
+ "RationaleStatement": "Microsoft Defender for Cloud emails the Subscription Owner to notify them about security alerts. Adding your Security Contact's email address to the 'Additional email addresses' field ensures that your organization's Security Team is included in these alerts. This ensures that the proper people are aware of any potential compromise in order to mitigate the risk in a timely fashion.",
+ "ImpactStatement": "Security contacts will receive email notifications.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment Settings`. 1. Click on the appropriate Management Group, Subscription, or Workspace. 1. Click on `Email notifications`. 1. Enter a valid security contact email address (or multiple addresses separated by commas) in the `Additional email addresses` field. 1. Click `Save`. **Remediate from Azure CLI** Use the below command to set `Security contact emails` to `On`. ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X PUT -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts/default?api-version=2020-01-01-preview -d@input.json' ``` Where `input.json` contains the data below, replacing `validEmailAddress` with a single email address or multiple comma-separated email addresses: ``` { id: /subscriptions/<Your_Subscription_Id>/providers/Microsoft.Security/securityContacts/default, name: default, type: Microsoft.Security/securityContacts, properties: { email: <validEmailAddress>, alertNotifications: On, alertsToAdmins: On } } ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment Settings`. 1. Click on the appropriate Management Group, Subscription, or Workspace. 1. Click on `Email notifications`. 1. Ensure that a valid security contact email address is listed in the `Additional email addresses` field. **Audit from Azure CLI** Ensure the output of the below command is not empty and is set with appropriate email ids: ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X GET -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts?api-version=2020-01-01-preview' | jq '.|.[] | select(.name==default)'|jq '.properties.emails' ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) **- Name:** 'Subscriptions should have a contact email address for security issues'",
+ "AdditionalInformation": "Excluding any entries in the input.json properties block disables the specific setting by default.",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-provide-security-contact-details:https://docs.microsoft.com/en-us/rest/api/securitycenter/securitycontacts/list:https://docs.microsoft.com/en-us/rest/api/securitycenter/security-contacts:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response#ir-2-preparation---setup-incident-notification",
+ "DefaultValue": "By default, there are no additional email addresses entered."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.14",
+ "Description": "Ensure that 'Notify about alerts with the following severity (or higher)' is Enabled",
+ "Checks": [
+ "defender_ensure_notify_alerts_severity_is_high"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Notify about alerts with the following severity (or higher)' is Enabled",
+ "RationaleStatement": "Enabling security alert emails ensures that security alert emails are sent by Microsoft. This ensures that the right people are aware of any potential security issues and can mitigate the risk.",
+ "ImpactStatement": "Enabling security alert emails can cause alert fatigue, increasing the risk of missing important alerts. Select an appropriate severity level to manage notifications. Azure aims to reduce alert fatigue by limiting the daily email volume per severity level. Learn more: https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications#email-frequency.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Subscription. 1. Click on `Email notifications`. 1. Under `Notification types`, check box next to `Notify about alerts with the following severity (or higher)` and select an appropriate severity level from the drop-down menu. 1. Click `Save`. 1. Repeat steps 1-7 for each Subscription requiring remediation. **Remediate from Azure CLI** Use the below command to enable `Send email notification for high severity alerts`: ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X PUT -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/<$0>/providers/Microsoft.Security/securityContacts/default1?api-version=2017-08-01-preview -d@input.json' ``` Where `input.json` contains the data below, replacing `validEmailAddress` with a single email address or multiple comma-separated email addresses: ``` { id: /subscriptions/<subscriptionId>/providers/Microsoft.Security/securityContacts/default, name: default, type: Microsoft.Security/securityContacts, properties: { email: <validEmailAddress>, alertNotifications: On, alertsToAdmins: On } } ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Subscription. 1. Click on `Email notifications`. 1. Under `Notification types`, ensure that the box next to `Notify about alerts with the following severity (or higher)` is checked, and an appropriate severity level is selected. 1. Repeat steps 1-6 for each Subscription. **Audit from Azure CLI** Including a Subscription ID at the `$0` in `/subscriptions/$0/providers`, ensure the below command returns `state: On`, and that `minimalSeverity` is set to an appropriate severity level: ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X GET -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts?api-version=2020-01-01-preview' | jq '.|.[] | select(.name==default)'|jq '.properties.alertNotifications' ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [6e2593d9-add6-4083-9c9b-4b7d2188c899](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F6e2593d9-add6-4083-9c9b-4b7d2188c899) **- Name:** 'Email notification for high severity alerts should be enabled'",
+ "AdditionalInformation": "Excluding any entries in the `input.json` properties block disables the specific setting by default. This recommendation has been updated to reflect recent changes to Microsoft REST APIs for getting and updating security contact information.",
+ "References": "https://docs.microsoft.com/en-us/azure/security-center/security-center-provide-security-contact-details:https://docs.microsoft.com/en-us/rest/api/securitycenter/security-contacts:https://docs.microsoft.com/en-us/rest/api/securitycenter/securitycontacts/list:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response#ir-2-preparation---setup-incident-notification",
+ "DefaultValue": "By default, subscription owners receive email notifications for high-severity alerts."
+ }
+ ]
+ },
+ {
+ "Id": "8.1.15",
+ "Description": "Ensure that 'Notify about attack paths with the following risk level (or higher)' is Enabled",
+ "Checks": [
+ "defender_attack_path_notifications_properly_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Notify about attack paths with the following risk level (or higher)' is Enabled",
+ "RationaleStatement": "Enabling attack path emails ensures that attack path emails are sent by Microsoft. This ensures that the right people are aware of any potential security issues and can mitigate the risk.",
+ "ImpactStatement": "Enabling attack path emails can cause alert fatigue, increasing the risk of missing important alerts. Select an appropriate risk level to manage notifications. Azure aims to reduce alert fatigue by limiting the daily email volume per risk level. Learn more: https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications#email-frequency.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Subscription. 1. Click on `Email notifications`. 1. Under Notification types, check the box next to `Notify about attack paths with the following risk level (or higher)`, and select an appropriate risk level from the drop-down menu. 1. Repeat steps 1-6 for each Subscription.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home select the Portal Menu. 1. Select `Microsoft Defender for Cloud`. 1. Under `Management`, select `Environment settings`. 1. Click on the appropriate Subscription. 1. Click on `Email notifications`. 1. Under Notification types, ensure that the box next to `Notify about attack paths with the following risk level (or higher)` is checked, and an appropriate risk level is selected. 1. Repeat steps 1-6 for each Subscription. **Audit from Azure CLI** Including a Subscription ID at the `$0` in `/subscriptions/$0/providers`, ensure the below command returns `sourceType: AttackPath`, and that `minimalRiskLevel` is set to an appropriate risk level: ``` az account get-access-token --query {subscription:subscription,accessToken:accessToken} --out tsv | xargs -L1 bash -c 'curl -X GET -H Authorization: Bearer $1 -H Content-Type: application/json https://management.azure.com/subscriptions/$0/providers/Microsoft.Security/securityContacts?api-version=2023-12-01-preview' | jq '.|.[]' ```",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications:https://learn.microsoft.com/en-us/azure/defender-for-cloud/how-to-manage-attack-path:https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-attack-path",
+ "DefaultValue": ""
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_attack_path_notifications_properly_configured",
+ "ConfigKey": "defender_attack_path_minimal_risk_level",
+ "Operator": "in",
+ "Value": [
+ "Low",
+ "Medium",
+ "High"
+ ]
+ }
+ ]
+ },
+ {
+ "Id": "8.1.16",
+ "Description": "Ensure that Microsoft Defender External Attack Surface Monitoring (EASM) is Enabled",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.1 Microsoft Defender for Cloud",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Microsoft Defender External Attack Surface Monitoring (EASM) is Enabled",
+ "RationaleStatement": "This tool can monitor the externally exposed resources of an organization, provide valuable insights, and export these findings in a variety of formats (including CSV) for use in vulnerability management operations and red/purple team exercises.",
+ "ImpactStatement": "Microsoft Defender EASM workspaces are currently available as Azure Resources with a 30-day free trial period but can quickly accrue significant charges. The costs are calculated daily as (Number of billable inventory items) x (item cost per day; approximately: $0.017). Estimated cost is not provided within the tool, and users are strongly advised to contact their Microsoft sales representative for pricing and set a calendar reminder for the end of the trial period. For an EASM workspace having an Inventory of 5k-10k billable items (IP addresses, hostnames, SSL certificates, etc) a typical cost might be approximately $85-170 per day or $2500-5000 USD/month at the time of publication. If the workspace is deleted by the last day of a free trial period, no charges are billed.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Microsoft Defender EASM`. 1. Click `+ Create`. 1. Under `Project details`, select a subscription. 1. Select or create a resource group. 1. Under `Instance details`, enter a name for the workspace. 1. Select a region. 1. Click `Review + create`. 1. Click `Create`. 1. Once the deployment has completed, go to `Microsoft Defender EASM`. 1. Click the workspace name. 1. Configure the workspace appropriately for your environment and organization.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Microsoft Defender EASM`. 1. Ensure that at least one Microsoft Defender EASM workspace is listed. 1. Click the name of a workspace. 1. Ensure the workspace is configured appropriately for your environment and organization. 1. Repeat steps 3-4 for each workspace.",
+ "AdditionalInformation": "Microsoft added its Defender for External Attack Surface management (EASM) offering to Azure following its 2022 acquisition of EASM SaaS tool company RiskIQ.",
+ "References": "https://learn.microsoft.com/en-us/azure/external-attack-surface-management/:https://learn.microsoft.com/en-us/azure/external-attack-surface-management/deploying-the-defender-easm-azure-resource:https://www.microsoft.com/en-us/security/blog/2022/08/02/microsoft-announces-new-solutions-for-threat-intelligence-and-attack-surface-management/",
+ "DefaultValue": "Microsoft Defender EASM is an optional, paid Azure Resource that must be created and configured inside a Subscription and Resource Group."
+ }
+ ]
+ },
+ {
+ "Id": "8.2.1",
+ "Description": "Ensure That Microsoft Defender for IoT Hub Is Set To 'On'",
+ "Checks": [
+ "defender_ensure_iot_hub_defender_is_on"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.2 Microsoft Defender for IoT",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure That Microsoft Defender for IoT Hub Is Set To 'On'",
+ "RationaleStatement": "IoT devices are very rarely patched and can be potential attack vectors for enterprise networks. Updating their network configuration to use a central security hub allows for detection of these breaches.",
+ "ImpactStatement": "Enabling Microsoft Defender for IoT will incur additional charges dependent on the level of usage.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `IoT Hub`. 2. Select an `IoT Hub` to validate. 3. Select `Overview` in `Defender for IoT`. 4. Click on `Secure your IoT solution`, and complete the onboarding.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `IoT Hub`. 2. Select an `IoT Hub` to validate. 3. Select `Overview` in `Defender for IoT`. 4. The Threat prevention and Threat detection screen will appear, if `Defender for IoT` is Enabled.",
+ "AdditionalInformation": "There are additional configurations for Microsoft Defender for IoT that allow for types of deployments called hybrid or local. Both run on your physical infrastructure. These are complicated setups and are primarily outside of the scope of a purely Azure benchmark. Please see the references to consider these options for your organization.",
+ "References": "https://azure.microsoft.com/en-us/services/iot-defender/#overview:https://docs.microsoft.com/en-us/azure/defender-for-iot/:https://azure.microsoft.com/en-us/pricing/details/iot-defender/:https://docs.microsoft.com/en-us/security/benchmark/azure/baselines/defender-for-iot-security-baseline:https://docs.microsoft.com/en-us/cli/azure/iot?view=azure-cli-latest:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-logging-threat-detection#lt-1-enable-threat-detection-capabilities:https://learn.microsoft.com/en-us/azure/defender-for-iot/device-builders/quickstart-onboard-iot-hub",
+ "DefaultValue": "By default, Microsoft Defender for IoT is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.1",
+ "Description": "Ensure that the Expiration Date is Set for all Keys in Key Vaults using RBAC",
+ "Checks": [
+ "keyvault_rbac_key_expiration_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the Expiration Date is Set for all Keys in Key Vaults using RBAC",
+ "RationaleStatement": "Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The `exp` (expiration date) attribute identifies the expiration date on or after which the key MUST NOT be used for encryption of new data, wrapping of new keys, and signing. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration date for all keys to help enforce the key rotation. This ensures that the keys cannot be used beyond their assigned lifetimes.",
+ "ImpactStatement": "Keys cannot be used beyond their assigned expiration dates respectively. Keys need to be rotated periodically wherever they are used.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Keys`. 3. In the main pane, ensure that an appropriate `Expiration date` is set for any keys that are `Enabled`. **Remediate from Azure CLI** Update the `Expiration date` for the key using the below command: ``` az keyvault key set-attributes --name <keyName> --vault-name <vaultName> --expires Y-m-d'T'H:M:S'Z' ``` **Note:** To view the expiration date on all keys in a Key Vault using Microsoft API, the List Key permission is required. To update the expiration date for the keys: 1. Go to the Key vault, click on Access Control (IAM). 2. Click on Add role assignment and assign the role of Key Vault Crypto Officer to the appropriate user. **Remediate from PowerShell** ``` Set-AzKeyVaultKeyAttribute -VaultName <VaultName> -Name <KeyName> -Expires <DateTime> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Keys`. 3. In the main pane, ensure that an appropriate `Expiration date` is set for any keys that are `Enabled`. **Audit from Azure CLI** Get a list of all the key vaults in your Azure environment by running the following command: ``` az keyvault list ``` Then for each key vault listed ensure that the output of the below command contains Key ID (kid), enabled status as `true` and Expiration date (expires) is not empty or null: ``` az keyvault key list --vault-name <VaultName> --query '[*].{kid:kid,enabled:attributes.enabled,expires:attributes.expires}' ``` **Audit from PowerShell** Retrieve a list of Azure Key vaults: ``` Get-AzKeyVault ``` For each Key vault run the following command to determine which vaults are configured to use RBAC. ``` Get-AzKeyVault -VaultName <VaultName> ``` For each Key vault with the `EnableRbacAuthorizatoin` setting set to `True`, run the following command. ``` Get-AzKeyVaultKey -VaultName <VaultName> ``` Make sure the `Expires` setting is configured with a value as appropriate wherever the `Enabled` setting is set to `True`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0) **- Name:** 'Key Vault keys should have an expiration date'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/key-vault-whatis:https://docs.microsoft.com/en-us/rest/api/keyvault/about-keys--secrets-and-certificates#key-vault-keys:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-6-use-a-secure-key-management-process:https://docs.microsoft.com/en-us/powershell/module/az.keyvault/set-azkeyvaultkeyattribute?view=azps-0.10.0",
+ "DefaultValue": "By default, keys do not expire."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.2",
+ "Description": "Ensure that the Expiration Date is set for All Keys in Key Vaults using access policies (legacy)",
+ "Checks": [
+ "keyvault_key_expiration_set_in_non_rbac"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the Expiration Date is set for All Keys in Key Vaults using access policies (legacy)",
+ "RationaleStatement": "Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The `exp` (expiration date) attribute identifies the expiration date on or after which the key MUST NOT be used for a cryptographic operation. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration date for all keys. This ensures that the keys cannot be used beyond their assigned lifetimes.",
+ "ImpactStatement": "Keys cannot be used beyond their assigned expiration dates respectively. Keys need to be rotated periodically wherever they are used.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Keys`. 3. In the main pane, ensure that the status of the key is `Enabled`. 4. For each enabled key, ensure that an appropriate `Expiration date` is set. **Remediate from Azure CLI** Update the `Expiration date` for the key using the below command: ``` az keyvault key set-attributes --name <keyName> --vault-name <vaultName> --expires Y-m-d'T'H:M:S'Z' ``` **Note:** To view the expiration date on all keys in a Key Vault using Microsoft API, the List Key permission is required. To update the expiration date for the keys: 1. Go to Key vault, click on `Access policies`. 2. Click on `Create` and add an access policy with the `Update` permission (in the Key Permissions - Key Management Operations section). **Remediate from PowerShell** ``` Set-AzKeyVaultKeyAttribute -VaultName <Vault Name> -Name <Key Name> -Expires <DateTime> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Keys`. 3. In the main pane, ensure that the status of the key is `Enabled`. 4. For each enabled key, ensure that an appropriate `Expiration date` is set. **Audit from Azure CLI** Get a list of all the key vaults in your Azure environment by running the following command: ``` az keyvault list ``` For each key vault, ensure that the output of the below command contains Key ID (kid), enabled status as `true` and Expiration date (expires) is not empty or null: ``` az keyvault key list --vault-name <KEYVAULTNAME> --query '[*].{kid:kid,enabled:attributes.enabled,expires:attributes.expires}' ``` **Audit from PowerShell** Retrieve a list of Azure Key vaults: ``` Get-AzKeyVault ``` For each Key vault, run the following command to determine which vaults are configured to not use RBAC: ``` Get-AzKeyVault -VaultName <Vault Name> ``` For each Key vault with the `EnableRbacAuthorizatoin` setting set to `False` or empty, run the following command. ``` Get-AzKeyVaultKey -VaultName <Vault Name> ``` Make sure the `Expires` setting is configured with a value as appropriate wherever the `Enabled` setting is set to `True`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0) **- Name:** 'Key Vault keys should have an expiration date'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/key-vault-whatis:https://docs.microsoft.com/en-us/rest/api/keyvault/about-keys--secrets-and-certificates#key-vault-keys:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-6-use-a-secure-key-management-process:https://docs.microsoft.com/en-us/powershell/module/az.keyvault/set-azkeyvaultkeyattribute?view=azps-0.10.0",
+ "DefaultValue": "By default, keys do not expire."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.3",
+ "Description": "Ensure that the Expiration Date is set for All Secrets in Key Vaults using RBAC",
+ "Checks": [
+ "keyvault_rbac_secret_expiration_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the Expiration Date is set for All Secrets in Key Vaults using RBAC",
+ "RationaleStatement": "The Azure Key Vault enables users to store and keep secrets within the Microsoft Azure environment. Secrets in the Azure Key Vault are octet sequences with a maximum size of 25k bytes each. The `exp` (expiration date) attribute identifies the expiration date on or after which the secret MUST NOT be used. By default, secrets never expire. It is thus recommended to rotate secrets in the key vault and set an explicit expiration date for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes.",
+ "ImpactStatement": "Secrets cannot be used beyond their assigned expiry date respectively. Secrets need to be rotated periodically wherever they are used.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Secrets`. 3. In the main pane, ensure that the status of the secret is `Enabled`. 4. For each enabled secret, ensure that an appropriate `Expiration date` is set. **Remediate from Azure CLI** Update the Expiration date for the secret using the below command: ``` az keyvault secret set-attributes --name <secret_name> --vault-name <vault_name> --expires Y-m-d'T'H:M:S'Z' ``` Note: To view the expiration date on all secrets in a Key Vault using Microsoft API, the `List Secret` permission is required. To update the expiration date for the secrets: 1. Go to the Key vault, click on `Access Control (IAM)`. 2. Click on `Add role assignment` and assign the role of `Key Vault Secrets Officer` to the appropriate user. **Remediate from PowerShell** ``` Set-AzKeyVaultSecretAttribute -VaultName <vault_name> -Name <secret_name> -Expires <date_time> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Secrets`. 3. In the main pane, ensure that the status of the secret is `Enabled`. 4. For each enabled secret, ensure that an appropriate `Expiration date` is set. **Audit from Azure CLI** Ensure that the output of the below command contains ID (id), enabled status as `true` and Expiration date (expires) is not empty or null: ``` az keyvault secret list --vault-name <KEYVAULTNAME> --query '[*].{kid:kid,enabled:attributes.enabled,expires:attributes.expires}' ``` **Audit from PowerShell** Retrieve a list of Key vaults: ``` Get-AzKeyVault ``` For each Key vault, run the following command to determine which vaults are configured to use RBAC: ``` Get-AzKeyVault -VaultName <Vault Name> ``` For each Key vault with the `EnableRbacAuthorization` setting set to `True`, run the following command: ``` Get-AzKeyVaultSecret -VaultName <Vault Name> ``` Make sure the `Expires` setting is configured with a value as appropriate wherever the `Enabled` setting is set to `True`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [98728c90-32c7-4049-8429-847dc0f4fe37](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F98728c90-32c7-4049-8429-847dc0f4fe37) **- Name:** 'Key Vault secrets should have an expiration date'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/key-vault-whatis:https://docs.microsoft.com/en-us/rest/api/keyvault/about-keys--secrets-and-certificates#key-vault-secrets:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-6-use-a-secure-key-management-process:https://docs.microsoft.com/en-us/powershell/module/az.keyvault/set-azkeyvaultsecretattribute?view=azps-0.10.0",
+ "DefaultValue": "By default, secrets do not expire."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.4",
+ "Description": "Ensure that the Expiration Date is set for All Secrets in Key Vaults using access policies (legacy)",
+ "Checks": [
+ "keyvault_non_rbac_secret_expiration_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the Expiration Date is set for All Secrets in Key Vaults using access policies (legacy)",
+ "RationaleStatement": "The Azure Key Vault enables users to store and keep secrets within the Microsoft Azure environment. Secrets in the Azure Key Vault are octet sequences with a maximum size of 25k bytes each. The `exp` (expiration date) attribute identifies the expiration date on or after which the secret MUST NOT be used. By default, secrets never expire. It is thus recommended to rotate secrets in the key vault and set an explicit expiration date for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes.",
+ "ImpactStatement": "Secrets cannot be used beyond their assigned expiry date respectively. Secrets need to be rotated periodically wherever they are used.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Secrets`. 3. In the main pane, ensure that the status of the secret is `Enabled`. 4. Set an appropriate `Expiration date` on all secrets. **Remediate from Azure CLI** Update the `Expiration date` for the secret using the below command: ``` az keyvault secret set-attributes --name <secret_name> --vault-name <vault_name> --expires Y-m-d'T'H:M:S'Z' ``` Note: To view the expiration date on all secrets in a Key Vault using Microsoft API, the `List` Secret permission is required. To update the expiration date for the secrets: 1. Go to Key vault, click on `Access policies`. 2. Click on `Create` and add an access policy with the `Update` permission (in the Secret Permissions - Secret Management Operations section). **Remediate from PowerShell** For each Key vault with the `EnableRbacAuthorization` setting set to `False` or empty, run the following command. ``` Set-AzKeyVaultSecret -VaultName <vault_name> -Name <secret_name> -Expires <date_time> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. For each Key vault, click on `Secrets`. 3. In the main pane, ensure that the status of the secret is `Enabled`. 4. Set an appropriate `Expiration date` on all secrets. **Audit from Azure CLI** Get a list of all the key vaults in your Azure environment by running the following command: ``` az keyvault list ``` For each key vault, ensure that the output of the below command contains ID (id), enabled status as `true` and Expiration date (expires) is not empty or null: ``` az keyvault secret list --vault-name <KEYVALUTNAME> --query '[*].{kid:kid,enabled:attributes.enabled,expires:attributes.expires}' ``` **Audit from PowerShell** Retrieve a list of Key vaults: ``` Get-AzKeyVault ``` For each Key vault run the following command to determine which vaults are configured to use RBAC: ``` Get-AzKeyVault -VaultName <Vault Name> ``` For each Key Vault with the `EnableRbacAuthorization` setting set to `False` or empty, run the following command. ``` Get-AzKeyVaultSecret -VaultName <Vault Name> ``` Make sure the `Expires` setting is configured with a value as appropriate wherever the `Enabled` setting is set to `True`. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [98728c90-32c7-4049-8429-847dc0f4fe37](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F98728c90-32c7-4049-8429-847dc0f4fe37) **- Name:** 'Key Vault secrets should have an expiration date'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/key-vault-whatis:https://docs.microsoft.com/en-us/rest/api/keyvault/about-keys--secrets-and-certificates#key-vault-secrets:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-6-use-a-secure-key-management-process:https://docs.microsoft.com/en-us/powershell/module/az.keyvault/set-azkeyvaultsecret?view=azps-7.4.0",
+ "DefaultValue": "By default, secrets do not expire."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.5",
+ "Description": "Ensure 'Purge protection' is Set to 'Enabled'",
+ "Checks": [
+ "keyvault_recoverable"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Purge protection' is Set to 'Enabled'",
+ "RationaleStatement": "Users may accidentally run delete/purge commands on a key vault, or an attacker or malicious user may do so deliberately in order to cause disruption. Deleting or purging a key vault leads to immediate data loss, as keys encrypting data and secrets/certificates allowing access/services will become inaccessible. Enabling purge protection ensures that even if a key vault is deleted, the key vault and its objects remain recoverable during the configurable retention period. If no action is taken, the key vault and its objects will be purged once the retention period elapses.",
+ "ImpactStatement": "Once purge protection is enabled for a key vault, it cannot be disabled.",
+ "RemediationProcedure": "**Note:** Once enabled, purge protection cannot be disabled. **Remediate from Azure Portal** 1. Go to `Key Vaults`. 2. Click the name of a key vault. 3. Under `Settings`, click `Properties`. 4. Select the radio button next to `Enable purge protection (enforce a mandatory retention period for deleted vaults and vault objects)`. 5. Click `Save`. 6. Repeat steps 1-5 for each key vault requiring remediation. **Remediate from Azure CLI** For each key vault requiring remediation, run the following command to enable purge protection: ``` az resource update --resource-group <resource-group> --name <key-vault> --resource-type \"Microsoft.KeyVault/vaults\" --set properties.enablePurgeProtection=true ``` **Remediate from PowerShell** For each key vault requiring remediation, run the following command to enable purge protection: ``` Update-AzKeyVault -ResourceGroupName <resource-group> -VaultName <key-vault> -EnablePurgeProtection ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key Vaults`. 2. Click the name of a key vault. 3. Under `Settings`, click `Properties`. 4. Next to `Purge protection`, ensure that `Enable purge protection (enforce a mandatory retention period for deleted vaults and vault objects)` is selected. 5. Repeat steps 1-4 for each key vault. **Audit from Azure CLI** Run the following command to list key vaults: ``` az resource list --query \"[?type=='Microsoft.KeyVault/vaults']\" ``` For each key vault, run the following command to get the purge protection setting: ``` az resource show --resource-group <resource-group> --name <key-vault> --resource-type \"Microsoft.KeyVault/vaults\" --query properties.enablePurgeProtection ``` Ensure that `true` is returned. **Audit from PowerShell** Run the following command to list key vaults: ``` Get-AzKeyVault ``` For each key vault, run the following command to get the key vault details: ``` Get-AzKeyVault -ResourceGroupName <resource-group> -VaultName <key-vault> ``` Ensure `Purge Protection Enabled?` is set to `True`. **Audit from Azure Policy** - **Policy ID:** 0b60c0b2-2dc2-4e1c-b5c9-abbed971de53 - **Name:** 'Key vaults should have deletion protection enabled'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/key-vault/general/key-vault-recovery:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-8-define-and-implement-backup-and-recovery-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-8-ensure-security-of-key-and-certificate-repository",
+ "DefaultValue": "Purge protection is disabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.6",
+ "Description": "Ensure that Role Based Access Control for Azure Key Vault is Enabled",
+ "Checks": [
+ "keyvault_rbac_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Role Based Access Control for Azure Key Vault is Enabled",
+ "RationaleStatement": "The new RBAC permissions model for Key Vaults enables a much finer grained access control for key vault secrets, keys, certificates, etc., than the vault access policy. This in turn will permit the use of privileged identity management over these roles, thus securing the key vaults with JIT Access management.",
+ "ImpactStatement": "Implementation needs to be properly designed from the ground up, as this is a fundamental change to the way key vaults are accessed/managed. Changing permissions to key vaults will result in loss of service as permissions are re-applied. For the least amount of downtime, map your current groups and users to their corresponding permission needs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** Key Vaults can be configured to use `Azure role-based access control` on creation. For existing Key Vaults: 1. From Azure Home open the Portal Menu in the top left corner 2. Select `Key Vaults` 3. Select a Key Vault to audit 4. Select `Access configuration` 5. Set the Permission model radio button to `Azure role-based access control`, taking note of the warning message 6. Click `Save` 7. Select `Access Control (IAM)` 8. Select the `Role Assignments` tab 9. Reapply permissions as needed to groups or users **Remediate from Azure CLI** To enable RBAC Authorization for each Key Vault, run the following Azure CLI command: ``` az keyvault update --resource-group <resource_group> --name <vault_name> --enable-rbac-authorization true ``` **Remediate from PowerShell** To enable RBAC authorization on each Key Vault, run the following PowerShell command: ``` Update-AzKeyVault -ResourceGroupName <resource_group> -VaultName <vault_name> -EnableRbacAuthorization $True ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home open the Portal Menu in the top left corner 2. Select Key Vaults 3. Select a Key Vault to audit 4. Select Access configuration 5. Ensure the Permission Model radio button is set to `Azure role-based access control` **Audit from Azure CLI** Run the following command for each Key Vault in each Resource Group: ``` az keyvault show --resource-group <resource_group> --name <vault_name> ``` Ensure the `enableRbacAuthorization` setting is set to `true` within the output of the above command. **Audit from PowerShell** Run the following PowerShell command: ``` Get-AzKeyVault -Vaultname <vault_name> -ResourceGroupName <resource_group> ``` Ensure the `Enabled For RBAC Authorization` setting is set to `True` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [12d4fa5e-1f9f-4c21-97a9-b99b3c6611b5](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F12d4fa5e-1f9f-4c21-97a9-b99b3c6611b5) **- Name:** 'Azure Key Vault should use RBAC permission model'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-gb/azure/key-vault/general/rbac-migration#vault-access-policy-to-azure-rbac-migration-steps:https://docs.microsoft.com/en-gb/azure/role-based-access-control/role-assignments-portal?tabs=current:https://docs.microsoft.com/en-gb/azure/role-based-access-control/overview:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-8-ensure-security-of-key-and-certificate-repository",
+ "DefaultValue": "The default value for Access control in Key Vaults is Vault Policy."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.7",
+ "Description": "Ensure Public Network Access is Disabled",
+ "Checks": [
+ "keyvault_private_endpoints"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Public Network Access is Disabled",
+ "RationaleStatement": "Disabling public network access improves security by ensuring that a service is not exposed on the public internet. Removing a point of interconnection from the internet edge to your key vault can strengthen the network security boundary of your system and reduce the risk of exposing the control plane or vault objects to untrusted clients. Although Azure resources are never truly isolated from the public internet, disabling the public endpoint removes a line of sight from the public internet and increases the effort required for an attack.",
+ "ImpactStatement": "NOTE: Prior to disabling public network access, it is strongly recommended that, for each key vault, either: virtual network integration is completed OR private endpoints/links are set up as described in 'Ensure Private Endpoints are used to access Azure Key Vault.' Disabling public network access restricts access to the service. This enhances security but will require the configuration of a virtual network and/or private endpoints for any services or users needing access within trusted networks.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. Click the name of a key vault. 3. Under `Settings`, click `Networking`. 4. Under `Firewalls and virtual networks`, next to `Allow access from:`, click the radio button next to `Disable public access`. 5. Click `Apply`. 6. Repeat steps 1-5 for each key vault requiring remediation. **Remediate from Azure CLI** For each key vault requiring remediation, run the following command to disable public network access: ``` az keyvault update --resource-group <resource-group> --name <key-vault> --public-network-access Disabled ``` **Remediate from PowerShell** For each key vault requiring remediation, run the following command to disable public network access: ``` Update-AzKeyVault -ResourceGroupName <resource-group> -VaultName <vault-name> -PublicNetworkAccess \"Disabled\" ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. Click the name of a key vault. 3. Under `Settings`, click `Networking`. 4. Under `Firewalls and virtual networks`, ensure that `Allow access from:` is set to `Disable public access`. 5. Repeat steps 1-4 for each key vault. **Audit from Azure CLI** Run the following command to list key vaults: ``` az keyvault list ``` For each key vault, run the following command to get the public network access setting: ``` az keyvault show --resource-group <resource-group> --name <key-vault> --query properties.publicNetworkAccess ``` Ensure that `Disabled` is returned. **Audit from PowerShell** Run the following command to list key vaults: ``` Get-AzKeyVault ``` Run the following command to get the key vault in a resource group with a given name: ``` $vault = Get-AzKeyVault -ResourceGroupName <resource-group> -Name <key-vault> ``` Run the following command to get the public network access setting for the key vault: ``` $vault.PublicNetworkAccess ``` Ensure that `Disabled` is returned. Repeat for each key vault. **Audit from Azure Policy** - **Policy ID:** 405c5871-3e91-4644-8a63-58e19d68ff5b - **Name:** 'Azure Key Vault should disable public network access'",
+ "AdditionalInformation": "This Common Reference Recommendation is referenced in the following Service Recommendations: - Storage Services > Storage Accounts > Networking > **Ensure that 'Public Network Access' is 'Disabled' for storage accounts**",
+ "References": "https://learn.microsoft.com/en-us/azure/key-vault/general/network-security:https://learn.microsoft.com/en-us/azure/key-vault/general/private-link-service",
+ "DefaultValue": "Public network access is enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.8",
+ "Description": "Ensure Private Endpoints are Used to Access Azure Key Vault",
+ "Checks": [
+ "keyvault_private_endpoints"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Private Endpoints are Used to Access Azure Key Vault",
+ "RationaleStatement": "Private endpoints will keep network requests to Azure Key Vault limited to the endpoints attached to the resources that are whitelisted to communicate with each other. Assigning the Key Vault to a network without an endpoint will allow other resources on that network to view all traffic from the Key Vault to its destination. In spite of the complexity in configuration, this is recommended for high security secrets.",
+ "ImpactStatement": "Incorrect or poorly-timed changing of network configuration could result in service interruption. There are also additional costs tiers for running a private endpoint per petabyte or more of networking traffic.",
+ "RemediationProcedure": "**Please see the additional information about the requirements needed before starting this remediation procedure.** **Remediate from Azure Portal** 1. From Azure Home open the Portal Menu in the top left. 2. Select Key Vaults. 3. Select a Key Vault to audit. 4. Select `Networking` in the left column. 5. Select `Private endpoint connections` from the top row. 6. Select `+ Create`. 7. Select the subscription the Key Vault is within, and other desired configuration. 8. Select `Next`. 9. For resource type select `Microsoft.KeyVault/vaults`. 10. Select the Key Vault to associate the Private Endpoint with. 11. Select `Next`. 12. In the `Virtual Networking` field, select the network to assign the Endpoint. 13. Select other configuration options as desired, including an existing or new application security group. 14. Select `Next`. 15. Select the private DNS the Private Endpoints will use. 16. Select `Next`. 17. Optionally add `Tags`. 18. Select `Next : Review + Create`. 19. Review the information and select `Create`. Follow the Audit Procedure to determine if it has successfully applied. 20. Repeat steps 3-19 for each Key Vault. **Remediate from Azure CLI** 1. To create an endpoint, run the following command: ``` az network private-endpoint create --resource-group <resourceGroup --vnet-name <vnetName> --subnet <subnetName> --name <PrivateEndpointName> --private-connection-resource-id /subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<resourceGroup>/providers/Microsoft.KeyVault/vaults/<keyVaultName> --group-ids vault --connection-name <privateLinkConnectionName> --location <azureRegion> --manual-request ``` 2. To manually approve the endpoint request, run the following command: ``` az keyvault private-endpoint-connection approve --resource-group <resourceGroup> --vault-name <keyVaultName> –name <privateLinkName> ``` 3. Determine the Private Endpoint's IP address to connect the Key Vault to the Private DNS you have previously created: 4. Look for the property networkInterfaces then id; the value must be placed in the variable <privateEndpointNIC> within step 7. ``` az network private-endpoint show -g <resourceGroupName> -n <privateEndpointName> ``` 5. Look for the property networkInterfaces then id; the value must be placed on <privateEndpointNIC> in step 7. ``` az network nic show --ids <privateEndpointName> ``` 6. Create a Private DNS record within the DNS Zone you created for the Private Endpoint: ``` az network private-dns record-set a add-record -g <resourcecGroupName> -z privatelink.vaultcore.azure.net -n <keyVaultName> -a <privateEndpointNIC> ``` 7. nslookup the private endpoint to determine if the DNS record is correct: ``` nslookup <keyVaultName>.vault.azure.net nslookup <keyVaultName>.privatelink.vaultcore.azure.n ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. From Azure Home open the Portal Menu in the top left. 2. Select Key Vaults. 3. Select a Key Vault to audit. 4. Select `Networking` in the left column. 5. Select `Private endpoint connections` from the top row. 6. View if there is an endpoint attached. **Audit from Azure CLI** Run the following command within a subscription for each Key Vault you wish to audit. ``` az keyvault show --name <keyVaultName> ``` Ensure that `privateEndpointConnections` is not `null`. **Audit from PowerShell** Run the following command within a subscription for each Key Vault you wish to audit. ``` Get-AzPrivateEndpointConnection -PrivateLinkResourceId '/subscriptions/<subscriptionNumber>/resourceGroups/<resourceGroup>/providers/Microsoft.KeyVault/vaults/<keyVaultName>/' ``` Ensure that the response contains details of a private endpoint. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [a6abeaec-4d90-4a02-805f-6b26c4d3fbe9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fa6abeaec-4d90-4a02-805f-6b26c4d3fbe9) **- Name:** 'Azure Key Vaults should use private link'",
+ "AdditionalInformation": "This recommendation assumes that you have created a Resource Group containing a Virtual Network that the services are already associated with and configured private DNS. A Bastion on the virtual network is also required, and the service to which you are connecting must already have a Private Endpoint. For information concerning the installation of these services, please see the attached documentation. Microsoft's own documentation lists the requirements as: A Key Vault. An Azure virtual network. A subnet in the virtual network. Owner or contributor permissions for both the Key Vault and the virtual network.",
+ "References": "https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview:https://docs.microsoft.com/en-us/azure/storage/common/storage-private-endpoints:https://azure.microsoft.com/en-us/pricing/details/private-link/:https://docs.microsoft.com/en-us/azure/key-vault/general/private-link-service?tabs=portal:https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal:https://docs.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal:https://docs.microsoft.com/en-us/azure/bastion/bastion-overview:https://docs.microsoft.com/azure/dns/private-dns-getstarted-cli#create-an-additional-dns-record:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-8-ensure-security-of-key-and-certificate-repository",
+ "DefaultValue": "By default, Private Endpoints are not enabled for any services within Azure."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.9",
+ "Description": "Ensure Automatic Key Rotation is Enabled within Azure Key Vault",
+ "Checks": [
+ "keyvault_key_rotation_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Automatic Key Rotation is Enabled within Azure Key Vault",
+ "RationaleStatement": "Automatic key rotation reduces risk by ensuring that keys are rotated without manual intervention. Azure and NIST recommend that keys be rotated every two years or less. Refer to 'Table 1: Suggested cryptoperiods for key types' on page 46 of the following document for more information: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf.",
+ "ImpactStatement": "There is an additional cost for each scheduled key rotation.",
+ "RemediationProcedure": "**Note:** Azure CLI and PowerShell use the ISO8601 duration format for time spans. The format is `P<timespanInISO8601Format>(Y,M,D)`. The leading P is required and is referred to as `period`. The `(Y,M,D)` are for the duration of Year, Month, and Day, respectively. A time frame of 2 years, 2 months, 2 days would be `P2Y2M2D`. For Azure CLI and PowerShell, it is easiest to supply the policy flags in a `.json file`, for example: ``` { lifetimeActions: [ { trigger: { timeAfterCreate: P<timespanInISO8601Format>(Y,M,D), timeBeforeExpiry : null }, action: { type: Rotate } }, { trigger: { timeBeforeExpiry : P<timespanInISO8601Format>(Y,M,D) }, action: { type: Notify } } ], attributes: { expiryTime: P<timespanInISO8601Format>(Y,M,D) } } ``` **Remediate from Azure Portal** 1. Go to `Key Vaults`. 1. Select a Key Vault. 1. Under `Objects`, select `Keys`. 1. Select a key. 1. From the top row, select `Rotation policy`. 1. Select an appropriate `Expiry time`. 1. Set `Enable auto rotation` to `Enabled`. 1. Set an appropriate `Rotation option` and `Rotation time`. 1. Optionally, set a `Notification time`. 1. Click `Save`. 1. Repeat steps 1-10 for each Key Vault and Key. **Remediate from Azure CLI** Run the following command for each key to enable automatic rotation: ``` az keyvault key rotation-policy update --vault-name <vault-name> --name <key-name> --value <path/to/policy.json> ``` **Remediate from PowerShell** Run the following command for each key to enable automatic rotation: ``` Set-AzKeyVaultKeyRotationPolicy -VaultName <vault-name> -Name <key-name> -PolicyPath <path/to/policy.json> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key Vaults`. 1. Select a Key Vault. 1. Under `Objects`, select `Keys`. 1. Select a key. 1. From the top row, select `Rotation policy`. 1. Ensure `Enable auto rotation` is set to `Enabled`. 1. Ensure the `Rotation time` is set to an appropriate value. 1. Repeat steps 1-7 for each Key Vault and Key. **Audit from Azure CLI** Run the following command: ``` az keyvault key rotation-policy show --vault-name <vault-name> --name <key-name> ``` Ensure that the response contains a `lifetimeAction` of `Rotate` and that `timeAfterCreate` is set to an appropriate value. **Audit from PowerShell** Run the following command: ``` Get-AzKeyVaultKeyRotationPolicy -VaultName <vault-name> -Name <key-name> ``` Ensure that the response contains a `LifetimeAction` of `Rotate` and that `TimeAfterCreate` is set to an appropriate value. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [d8cf8476-a2ec-4916-896e-992351803c44](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fd8cf8476-a2ec-4916-896e-992351803c44) **- Name:** 'Keys should have a rotation policy ensuring that their rotation is scheduled within the specified number of days after creation.'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/key-vault/keys/how-to-configure-key-rotation:https://docs.microsoft.com/en-us/azure/storage/common/customer-managed-keys-overview#update-the-key-version:https://docs.microsoft.com/en-us/azure/virtual-machines/windows/disks-enable-customer-managed-keys-powershell#set-up-an-azure-key-vault-and-diskencryptionset-optionally-with-automatic-key-rotation:https://azure.microsoft.com/en-us/updates/public-preview-automatic-key-rotation-of-customermanaged-keys-for-encrypting-azure-managed-disks/:https://docs.microsoft.com/en-us/cli/azure/keyvault/key/rotation-policy?view=azure-cli-latest#az-keyvault-key-rotation-policy-update:https://docs.microsoft.com/en-us/powershell/module/az.keyvault/set-azkeyvaultkeyrotationpolicy?view=azps-8.1.0:https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/scalar-data-types/timespan:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-6-use-a-secure-key-management-process:https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf",
+ "DefaultValue": "By default, automatic key rotation is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "8.3.10",
+ "Description": "Ensure that Azure Key Vault Managed HSM is Used when Required",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Azure Key Vault Managed HSM is Used when Required",
+ "RationaleStatement": "Managed HSM is a fully managed, highly available, single-tenant service that ensures FIPS 140-2 Level 3 compliance. It provides centralized key management, isolated access control, and private endpoints for secure access. Integrated with Azure services, it supports migration from Key Vault, ensures data residency, and offers monitoring and auditing for enhanced security.",
+ "ImpactStatement": "Managed HSM incurs a cost of $0.40 to $5 per month for each actively used HSM-protected key, depending on the key type and quantity. Each key version is billed separately. Additionally, there is an hourly usage fee of $3.20 per Managed HSM pool.",
+ "RemediationProcedure": "**Remediate from Azure CLI** Run the following command to set `oid` to be the `OID` of the signed-in user: ``` $oid = az ad signed-in-user show --query id -o tsv ``` Alternatively, prepare a space-separated list of OIDs to be provided as the `administrators` of the HSM. Run the following command to create a Managed HSM: ``` az keyvault create --resource-group <resource-group> --hsm-name <hsm-name> --retention-days <retention-days> --administrators $oid ``` The command can take several minutes to complete. After the HSM has been created, it must be activated before it can be used. Activation requires providing a minimum of three and a maximum of ten RSA key pairs, as well as the minimum number of keys required to decrypt the security domain (called a quorum). OpenSSL can be used to generate the self-signed certificates, for example: ``` openssl req -newkey rsa:2048 -nodes -keyout cert_1.key -x509 -days 365 -out cert_1.cer ``` Run the following command to download the security domain and activate the Managed HSM: ``` az keyvault security-domain download --hsm-name <managed-hsm> --sd-wrapping-keys <key-1> <key-2> <key-3> --sd-quorum <quorum> --security-domain-file <managed-hsm-security-domain>.json ``` Store the security domain file and the RSA key pairs securely. They will be required for disaster recovery or for creating another Managed HSM that shares the same security domain so that the two can share keys. The Managed HSM will now be in an active state and ready for use.",
+ "AuditProcedure": "**Audit from Azure CLI** Run the following command to list key vaults: ``` az keyvault list --query [*].[name,type] ``` Ensure that at least one key vault with type `Microsoft.KeyVault/managedHSMs` exists.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/security/fundamentals/key-management-choose:https://learn.microsoft.com/en-us/azure/key-vault/managed-hsm/overview:https://azure.microsoft.com/en-gb/pricing/details/key-vault/:https://learn.microsoft.com/en-us/azure/key-vault/managed-hsm/quick-create-cli:https://learn.microsoft.com/en-us/cli/azure/keyvault",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "8.3.11",
+ "Description": "Ensure Certificate 'Validity Period (in months)' is Less Than or Equal to '12'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.3 Key Vault",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Certificate 'Validity Period (in months)' is Less Than or Equal to '12'",
+ "RationaleStatement": "Limiting certificate validity reduces the risk of misuse if compromised and helps ensure timely renewal, improving security and reliability.",
+ "ImpactStatement": "Minor administrative effort required to ensure certificate renewal and lifecycle management.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Key vaults`. 2. Click the name of a key vault. 3. Under `Objects`, click `Certificates`. 4. Click the name of a certificate. 5. Click `Issuance Policy`. 6. Set `Validity Period (in months)` to an integer between 1 and 12, inclusive. 7. Click `Save`. 8. Repeat steps 1-7 for each key vault and certificate requiring remediation. **Remediate from PowerShell** For each certificate requiring remediation, run the following command to set ValidityInMonths to an integer between 1 and 12, inclusive: ``` Set-AzKeyVaultCertificatePolicy -VaultName $vault.VaultName -Name <certificate-name> -ValidityInMonths <validity-in-months> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Key vaults`. 2. Click the name of a key vault. 3. Under `Objects`, click `Certificates`. 4. Click the name of a certificate. 5. Click `Issuance Policy`. 6. Ensure that `Validity Period (in months)` is set to 12 or less. 7. Repeat steps 1-6 for each key vault and certificate. **Audit from Azure CLI** Run the following command to list key vaults: ``` az keyvault list ``` For each key vault, run the following command to list certificates: ``` az keyvault certificate list --vault-name <key-vault-name> ``` For each certificate, run the following command to get the certificate policy's validityInMonths setting: ``` az keyvault certificate show --id <certificate-id> --query policy.x509CertificateProperties.validityInMonths ``` Ensure that 12 or less is returned. **Audit from PowerShell** Run the following command to list key vaults: ``` Get-AzKeyVault ``` Run the following command to get the key vault with a given name: ``` $vault = Get-AzKeyVault -Name <key-vault-name> ``` Run the following command to list certificates in the key vault: ``` Get-AzKeyVaultCertificate -VaultName $vault.VaultName ``` Run the following command to get the policy of a certificate with a given name: ``` $certificate = Get-AzKeyVaultCertificatePolicy -VaultName $vault.VaultName -Name <certificate-name> ``` Run the following command to get the certificate policy's ValidityInMonths setting: ``` $certificate.ValidityInMonths ``` Ensure that 12 or less is returned. Repeat for each key vault and certificate. **Audit from Azure Policy** - **Policy ID:** 0a075868-4c26-42ef-914c-5bc007359560 - **Name:** 'Certificates should have the specified maximum validity period'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/key-vault/certificates/about-certificates:https://learn.microsoft.com/en-us/cli/azure/keyvault:https://learn.microsoft.com/en-us/powershell/module/az.keyvault",
+ "DefaultValue": "Validity Period (in months) is set to 12 by default."
+ }
+ ]
+ },
+ {
+ "Id": "8.4.1",
+ "Description": "Ensure an Azure Bastion Host Exists",
+ "Checks": [
+ "network_bastion_host_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "SubSection": "8.4 Azure Bastion",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure an Azure Bastion Host Exists",
+ "RationaleStatement": "The Azure Bastion service allows organizations a more secure means of accessing Azure Virtual Machines over the Internet without assigning public IP addresses to those Virtual Machines. The Azure Bastion service provides Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to Virtual Machines using TLS within a web browser, thus preventing organizations from opening up 3389/TCP and 22/TCP to the Internet on Azure Virtual Machines. Additional benefits of the Bastion service includes Multi-Factor Authentication, Conditional Access Policies, and any other hardening measures configured within Azure Active Directory using a central point of access.",
+ "ImpactStatement": "The Azure Bastion service incurs additional costs and requires a specific virtual network configuration. The `Standard` tier offers additional configuration options compared to the `Basic` tier and may incur additional costs for those added features.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Click on `Bastions` 2. Select the `Subscription` 3. Select the `Resource group` 4. Type a `Name` for the new Bastion host 5. Select a `Region` 6. Choose `Standard` next to `Tier` 7. Use the slider to set the `Instance count` 8. Select the `Virtual network` or `Create new` 9. Select the `Subnet` named `AzureBastionSubnet`. Create a `Subnet` named `AzureBastionSubnet` using a `/26` CIDR range if it doesn't already exist. 10. Select the appropriate `Public IP address` option. 11. If `Create new` is selected for the `Public IP address` option, provide a `Public IP address name`. 12. If `Use existing` is selected for `Public IP address` option, select an IP address from `Choose public IP address` 13. Click `Next: Tags >` 14. Configure the appropriate `Tags` 15. Click `Next: Advanced >` 16. Select the appropriate `Advanced` options 17. Click `Next: Review + create >` 18. Click `Create` **Remediate from Azure CLI** ``` az network bastion create --location <location> --name <name of bastion host> --public-ip-address <public IP address name or ID> --resource-group <resource group name or ID> --vnet-name <virtual network containing subnet called AzureBastionSubnet> --scale-units <integer> --sku Standard [--disable-copy-paste true|false] [--enable-ip-connect true|false] [--enable-tunneling true|false] ``` **Remediate from PowerShell** Create the appropriate `Virtual network` settings and `Public IP Address` settings. ``` $subnetName = AzureBastionSubnet $subnet = New-AzVirtualNetworkSubnetConfig -Name $subnetName -AddressPrefix <IP address range in CIDR notation making sure to use a /26> $virtualNet = New-AzVirtualNetwork -Name <virtual network name> -ResourceGroupName <resource group name> -Location <location> -AddressPrefix <IP address range in CIDR notation> -Subnet $subnet $publicip = New-AzPublicIpAddress -ResourceGroupName <resource group name> -Name <public IP address name> -Location <location> -AllocationMethod Dynamic -Sku Standard ``` Create the `Azure Bastion` service using the information within the created variables from above. ``` New-AzBastion -ResourceGroupName <resource group name> -Name <bastion name> -PublicIpAddress $publicip -VirtualNetwork $virtualNet -Sku Standard -ScaleUnit <integer> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Click on `Bastions` 2. Ensure there is at least one `Bastion` host listed under the `Name` column **Audit from Azure CLI** **Note:** The Azure CLI `network bastion` module is in `Preview` as of this writing ``` az network bastion list --subscription <subscription ID> ``` Ensure the output of the above command is not empty. **Audit from PowerShell** Retrieve the `Bastion` host(s) information for a specific `Resource Group` ``` Get-AzBastion -ResourceGroupName <resource group name> ``` Ensure the output of the above command is not empty.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/bastion/bastion-overview#sku:https://learn.microsoft.com/en-us/powershell/module/az.network/get-azbastion?view=azps-9.2.0:https://learn.microsoft.com/en-us/cli/azure/network/bastion?view=azure-cli-latest",
+ "DefaultValue": "By default, the Azure Bastion service is not configured."
+ }
+ ]
+ },
+ {
+ "Id": "8.5",
+ "Description": "Ensure Azure DDoS Network Protection is Enabled on Virtual Networks",
+ "Checks": [
+ "network_vnet_ddos_protection_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Security Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Azure DDoS Network Protection is Enabled on Virtual Networks",
+ "RationaleStatement": "Virtual networks and resources are protected against attacks, helping to ensure reliability and availability for critical workloads.",
+ "ImpactStatement": "Azure DDoS Network Protection incurs a significant fixed monthly charge, with additional charges if more than 100 public IP resources are protected. Careful consideration and analysis should be applied before enabling DDoS protection. Refer to https://azure.microsoft.com/en-us/pricing/details/ddos-protection for detailed pricing information.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Virtual networks`. 2. Click the name of a virtual network. 3. Under `Settings`, click `DDoS protection`. 4. Next to `DDoS Network Protection`, click `Enable`. 5. Provide a DDoS protection plan resource ID, or select a DDoS protection plan from the drop-down menu. 6. Click `Save`. 7. Repeat steps 1-6 for each virtual network requiring remediation. **Remediate from Azure CLI** For each virtual network requiring remediation, run the following command to enable DDoS protection: ``` az network vnet update --resource-group <resource-group> --name <virtual-network> --ddos-protection true --ddos-protection-plan <ddos-protection-plan> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Virtual networks`. 2. Click the name of a virtual network. 3. Under `Settings`, click `DDoS protection`. 4. Ensure `DDoS Network Protection` is set to `Enable`. 5. Repeat steps 1-4 for each virtual network. **Audit from Azure CLI** Run the following command to list virtual networks: ``` az network vnet list ``` For each virtual network, run the following command to get the DDoS protection setting: ``` az network vnet show --resource-group <resource-group> --name <virtual-network> --query enableDdosProtection ``` Ensure `true` is returned. **Audit from Azure Policy** - **Policy ID:** a7aca53f-2ed4-4466-a25e-0b45ade68efd - **Name:** 'Azure DDoS Protection should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/ddos-protection/ddos-protection-overview:https://learn.microsoft.com/en-us/azure/ddos-protection/manage-ddos-protection:https://azure.microsoft.com/en-us/pricing/details/ddos-protection:https://learn.microsoft.com/en-us/cli/azure/network/vnet",
+ "DefaultValue": "DDoS protection is disabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "9.1.1",
+ "Description": "Ensure Soft Delete for Azure File Shares is Enabled",
+ "Checks": [
+ "storage_ensure_file_shares_soft_delete_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.1 Azure Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Soft Delete for Azure File Shares is Enabled",
+ "RationaleStatement": "Important data could be accidentally deleted or removed by a malicious actor. With soft delete enabled, the data is retained for the defined retention period before permanent deletion, allowing for recovery of the data.",
+ "ImpactStatement": "When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account with file shares, under `Data storage`, click `File shares`. 1. Under `File share settings`, click the value next to `Soft delete`. 1. Under `Soft delete for all file shares`, click the toggle to set it to `Enabled`. 1. Under `Retention policies`, set an appropriate number of days to retain soft deleted data between 1 and 365, inclusive. 1. Click `Save`. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable soft delete for file shares and set an appropriate number of days for deleted data to be retained, between 1 and 365, inclusive: ``` az storage account file-service-properties update --account-name <storage-account> --enable-delete-retention true --delete-retention-days <retention-days> ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to enable soft delete for file shares and set an appropriate number of days for deleted data to be retained, between 1 and 365, inclusive: ``` Update-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -AccountName <storage-account> -EnableShareDeleteRetentionPolicy $true -ShareRetentionDays <retention-days> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account with file shares, under `Data storage`, click on `File shares`. 1. Under `File share settings`, ensure the value for `Soft delete` shows a number of days between 1 and 365, inclusive. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` Run the following command to determine if a storage account has file shares: ``` az storage share list --account-name <storage-account> ``` For each storage account with file shares, run the following command: ``` az storage account file-service-properties show --resource-group <resource-group> --account-name <storage-account> ``` Ensure that under `shareDeleteRetentionPolicy`, `enabled` is set to `true`, and `days` is set to an appropriate value between 1 and 365, inclusive. **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount -ResourceGroupName <resource-group> ``` With a storage account context set, run the following command to determine if a storage account has file shares: ``` Get-AzStorageShare ``` For each storage account with file shares, run the following command: ``` Get-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -AccountName <storage-account> ``` Ensure that `ShareDeleteRetentionPolicy.Enabled` is set to `True` and `ShareDeleteRetentionPolicy.Days` is set to an appropriate value between 1 and 365, inclusive.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/files/storage-files-enable-soft-delete:https://learn.microsoft.com/en-us/cli/azure/storage/account/file-service-properties:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstoragefileserviceproperty:https://learn.microsoft.com/en-us/powershell/module/az.storage/update-azstoragefileserviceproperty:https://learn.microsoft.com/en-us/azure/storage/files/storage-files-prevent-file-share-deletion",
+ "DefaultValue": "Soft delete is enabled by default at the storage account file share setting level."
+ }
+ ]
+ },
+ {
+ "Id": "9.1.2",
+ "Description": "Ensure 'SMB protocol version' is Set to 'SMB 3.1.1' or Higher for SMB file shares",
+ "Checks": [
+ "storage_smb_protocol_version_is_latest"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.1 Azure Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'SMB protocol version' is Set to 'SMB 3.1.1' or Higher for SMB file shares",
+ "RationaleStatement": "Using the latest supported SMB protocol version enhances the security of SMB file shares by preventing the exploitation of known vulnerabilities in outdated SMB versions.",
+ "ImpactStatement": "Using the latest SMB protocol version may impact client compatibility.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Data storage`, click `File shares`. 1. Under `File share settings`, click the link next to `Security`. 1. If `Profile` is set to `Maximum compatibility`, click the drop-down menu and select `Maximum security` or `Custom`. 1. If selecting `Custom`, under `SMB protocol versions`, uncheck the boxes next to `SMB 2.1` and `SMB 3.0`. 1. Click `Save`. 1. Repeat steps 1-7 for each storage account requiring remediation. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to set the SMB protocol version: ``` az storage account file-service-properties update --resource-group <resource-group> --account-name <storage-account> --versions SMB3.1.1 ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to set the SMB protocol version: ``` Update-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -StorageAccountName <storage-account> -SmbProtocolVersion SMB3.1.1 ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Data storage`, click `File shares`. 1. Under `File share settings`, click the link next to `Security`. 1. Under `SMB protocol versions`, ensure that `SMB3.1.1` is the only checked protocol version. 1. Repeat steps 1-5 for each storage account. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` For each storage account, run the following command: ``` az storage account file-service-properties show --resource-group <resource-group> --account-name <storage-account> ``` Ensure that under `protocolSettings` > `smb`, `versions` is set to `SMB3.1.1;` only. **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount ``` Run the following command to get the file service properties for a storage account in a resource group with a given name: ``` $storageaccountfileservice = Get-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -AccountName <storage-account> ``` Run the following command to get the SMB protocol version setting: ``` $storageaccountfileservice.ProtocolSettings.Smb.Versions ``` Ensure that the command returns `SMB3.1.1` only. Repeat for each storage account.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/well-architected/service-guides/azure-files#recommendations-for-smb-file-shares:https://learn.microsoft.com/en-us/azure/storage/files/files-smb-protocol#smb-security-settings:https://learn.microsoft.com/en-us/cli/azure/storage/account/file-service-properties:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstoragefileserviceproperty:https://learn.microsoft.com/en-us/powershell/module/az.storage/update-azstoragefileserviceproperty",
+ "DefaultValue": "By default, all SMB versions are allowed."
+ }
+ ]
+ },
+ {
+ "Id": "9.1.3",
+ "Description": "Ensure 'SMB channel encryption' is Set to 'AES-256-GCM' or Higher for SMB file shares",
+ "Checks": [
+ "storage_smb_channel_encryption_with_secure_algorithm"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.1 Azure Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'SMB channel encryption' is Set to 'AES-256-GCM' or Higher for SMB file shares",
+ "RationaleStatement": "AES-256-GCM encryption enhances the security of data transmitted over SMB channels by safeguarding it from unauthorized interception and tampering.",
+ "ImpactStatement": "Using the AES-256-GCM SMB channel encryption may impact client compatibility.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Data storage`, click `File shares`. 1. Under `File share settings`, click the link next to `Security`. 1. If `Profile` is set to `Maximum compatibility`, click the drop-down menu and select `Maximum security` or `Custom`. 1. If selecting `Custom`, under `SMB channel encryption`, uncheck the boxes next to `AES-128-CCM` and `AES-128-GCM`. 1. Click `Save`. 1. Repeat steps 1-7 for each storage account requiring remediation. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to set the SMB channel encryption: ``` az storage account file-service-properties update --resource-group <resource-group> --account-name <storage-account> --channel-encryption AES-256-GCM ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to set the SMB channel encryption: ``` Update-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -StorageAccountName <storage-account> -SmbChannelEncryption AES-256-GCM ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Data storage`, click `File shares`. 1. Under `File share settings`, click the link next to `Security`. 1. Under `SMB channel encryption`, ensure that `AES-256-GCM`, or higher, is the only checked SMB channel encryption setting. 1. Repeat steps 1-5 for each storage account. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` For each storage account, run the following command: ``` az storage account file-service-properties show --resource-group <resource-group> --account-name <storage-account> ``` Ensure that under `protocolSettings` > `smb`, `channelEncryption` is set to `AES-256-GCM;`, or higher, only. **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount ``` Run the following command to get the file service properties for a storage account in a resource group with a given name: ``` $storageaccountfileservice = Get-AzStorageFileServiceProperty -ResourceGroupName <resource-group> -AccountName <storage-account> ``` Run the following command to get the SMB channel encryption setting: ``` $storageaccountfileservice.ProtocolSettings.Smb.ChannelEncryption ``` Ensure that the command returns `AES-256-GCM`, or higher, only. Repeat for each storage account.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/well-architected/service-guides/azure-files#recommendations-for-smb-file-shares:https://learn.microsoft.com/en-us/azure/storage/files/files-smb-protocol?tabs=azure-portal#smb-security-settings:https://learn.microsoft.com/en-us/cli/azure/storage/account/file-service-properties:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstoragefileserviceproperty:https://learn.microsoft.com/en-us/powershell/module/az.storage/update-azstoragefileserviceproperty",
+ "DefaultValue": "By default, the following SMB channel encryption algorithms are allowed: - AES-128-CCM - AES-128-GCM - AES-256-GCM"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
+ ]
+ },
+ {
+ "Id": "9.2.1",
+ "Description": "Ensure That Soft Delete for Blobs on Azure Blob Storage Storage Accounts is Enabled",
+ "Checks": [
+ "storage_ensure_soft_delete_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.2 Azure Blob Storage",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Soft Delete for Blobs on Azure Blob Storage Storage Accounts is Enabled",
+ "RationaleStatement": "Blobs can be deleted incorrectly. An attacker or malicious user may do this deliberately in order to cause disruption. Deleting an Azure storage blob results in immediate data loss. Enabling this configuration for Azure storage accounts ensures that even if blobs are deleted from the storage account, the blobs are recoverable for a specific period of time, which is defined in the Retention policies, ranging from 7 to 365 days.",
+ "ImpactStatement": "All soft-deleted data is billed at the same rate as active data. Additional costs may be incurred for deleted blobs until the soft delete period ends and the data is permanently removed.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each Storage Account with blob storage, under `Data management`, go to `Data protection`. 1. Check the box next to `Enable soft delete for blobs`. 1. Set the retention period to a sufficient length for your organization. 1. Click `Save`. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable soft delete for blobs: ``` az storage blob service-properties delete-policy update --days-retained <retention-days> --account-name <storage-account> --enable true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each Storage Account with blob storage, under `Data management`, go to `Data protection`. 1. Ensure that `Enable soft delete for blobs` is checked. 1. Ensure that the retention period is a sufficient length for your organization. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` Run the following command to determine if a storage account has containers: ``` az storage container list --account-name <storage-account> ``` For each storage account with containers, ensure that the output of the below command contains `enabled: true` and `days` is not `null`: ``` az storage blob service-properties delete-policy show --account-name <storage-account> ```",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/blobs/soft-delete-blob-overview",
+ "DefaultValue": "Soft delete for blob storage is **enabled** by default on storage accounts created via the Azure Portal, and **disabled** by default on storage accounts created via Azure CLI or PowerShell."
+ }
+ ]
+ },
+ {
+ "Id": "9.2.2",
+ "Description": "Ensure that Soft Delete for Containers on Azure Blob Storage Storage Accounts is Enabled",
+ "Checks": [
+ "storage_ensure_soft_delete_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.2 Azure Blob Storage",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that Soft Delete for Containers on Azure Blob Storage Storage Accounts is Enabled",
+ "RationaleStatement": "Blobs can be deleted incorrectly. An attacker or malicious user may do this deliberately in order to cause disruption. Deleting an Azure storage blob results in immediate data loss. Enabling this configuration for Azure storage accounts ensures that even if blobs are deleted from the storage account, the blobs are recoverable for a specific period of time, which is defined in the Retention policies, ranging from 7 to 365 days.",
+ "ImpactStatement": "All soft-deleted data is billed at the same rate as active data. Additional costs may be incurred for deleted blobs until the soft delete period ends and the data is permanently removed.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each Storage Account with blob storage, under `Data management`, go to `Data protection`. 1. Check the box next to `Enable soft delete for blobs`. 1. Set the retention period to a sufficient length for your organization. 1. Click `Save`. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable soft delete for blobs: ``` az storage blob service-properties delete-policy update --days-retained <retention-days> --account-name <storage-account> --enable true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each Storage Account with blob storage, under `Data management`, go to `Data protection`. 1. Ensure that `Enable soft delete for blobs` is checked. 1. Ensure that the retention period is a sufficient length for your organization. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` Run the following command to determine if a storage account has containers: ``` az storage container list --account-name <storage-account> ``` For each storage account with containers, ensure that the output of the below command contains `enabled: true` and `days` is not `null`: ``` az storage blob service-properties delete-policy show --account-name <storage-account> ```",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/blobs/soft-delete-blob-overview",
+ "DefaultValue": "Soft delete for blob storage is **enabled** by default on storage accounts created via the Azure Portal, and **disabled** by default on storage accounts created via Azure CLI or PowerShell."
+ }
+ ]
+ },
+ {
+ "Id": "9.2.3",
+ "Description": "Ensure 'Versioning' is Set to 'Enabled' on Azure Blob Storage Storage Accounts",
+ "Checks": [
+ "storage_blob_versioning_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.2 Azure Blob Storage",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Versioning' is Set to 'Enabled' on Azure Blob Storage Storage Accounts",
+ "RationaleStatement": "Blob versioning safeguards data integrity and enables recovery by retaining previous versions of stored objects, facilitating quick restoration from accidental deletion, modification, or malicious activity.",
+ "ImpactStatement": "Enabling blob versioning for a storage account creates a new version with each write operation to a blob, which can increase storage costs. To control these costs, a lifecycle management policy can be applied to automatically delete older versions.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account with blob storage. 1. In the `Overview` page, on the `Properties` tab, under `Blob service`, click `Disabled` next to `Versioning`. 1. Under `Tracking`, check the box next to `Enable versioning for blobs`. 1. Select the radio button next to `Keep all versions` or `Delete versions after (in days)`. 1. If selecting to delete versions, enter a number of in the box after which to delete blob versions. 1. Click `Save`. 1. Repeat steps 1-7 for each storage account with blob storage. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable blob versioning: ``` az storage account blob-service-properties update --account-name <storage-account> --enable-versioning true ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to enable blob versioning: ``` Update-AzStorageBlobServiceProperty -ResourceGroupName <resource-group> -StorageAccountName <storage-account> -IsVersioningEnabled $true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account with blob storage. 1. In the `Overview` page, on the `Properties` tab, under `Blob service`, ensure `Versioning` is set to `Enabled`. 1. Repeat steps 1-3 for each storage account with blob storage. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` Run the following command to determine if a storage account has containers: ``` az storage container list --account-name <storage-account> ``` For each storage account with containers, ensure that the output of the below command contains `isVersioningEnabled: true`: ``` az storage account blob-service-properties show --account-name <storage-account> ``` **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount ``` Run the following command to create an Azure Storage context for a storage account: ``` $context = New-AzStorageContext -StorageAccountName <storage-account> ``` Run the following command to list containers for the storage account: ``` Get-AzStorageContainer -Context $context ``` If the storage account has containers, run the following command to get the blob service properties of the storage account: ``` $account = Get-AzStorageBlobServiceProperty -ResourceGroupName <resource-group> -AccountName <storage-account> ``` Run the following command to get the blob versioning setting for the storage account: ``` $account.IsVersioningEnabled ``` Ensure that the command returns `True`. Repeat for each storage account. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [c36a325b-ae04-4863-ad4f-19c6678f8e08](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc36a325b-ae04-4863-ad4f-19c6678f8e08) **- Name:** 'Configure your Storage account to enable blob versioning'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/cli/azure/storage/account:https://learn.microsoft.com/en-us/cli/azure/storage/account/blob-service-properties:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstorageaccount:https://learn.microsoft.com/en-us/powershell/module/az.storage/new-azstoragecontext:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstoragecontainer:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstorageblobserviceproperty:https://learn.microsoft.com/en-us/powershell/module/az.storage/update-azstorageblobserviceproperty:https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview:https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview",
+ "DefaultValue": "Blob versioning is disabled by default on storage accounts."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.1.1",
+ "Description": "Ensure That 'Enable key rotation reminders' is Enabled for Each Storage Account",
+ "Checks": [
+ "storage_infrastructure_encryption_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That 'Enable key rotation reminders' is Enabled for Each Storage Account",
+ "RationaleStatement": "Reminders such as those generated by this recommendation will help maintain a regular and healthy cadence for activities which improve the overall efficacy of a security program. Cryptographic key rotation periods will vary depending on your organization's security requirements and the type of data which is being stored in the Storage Account. For example, PCI DSS mandates that cryptographic keys be replaced or rotated 'regularly,' and advises that keys for static data stores be rotated every 'few months.' For the purposes of this recommendation, 90 days will be prescribed for the reminder. Review and adjustment of the 90 day period is recommended, and may even be necessary. Your organization's security requirements should dictate the appropriate setting.",
+ "ImpactStatement": "This recommendation only creates a periodic reminder to regenerate access keys. Regenerating access keys can affect services in Azure as well as the organization's applications that are dependent on the storage account. All clients that use the access key to access the storage account must be updated to use the new key.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts` 1. For each Storage Account that is not compliant, under `Security + networking`, go to `Access keys` 1. Click `Set rotation reminder` 1. Check `Enable key rotation reminders` 1. In the `Send reminders` field select `Custom`, then set the `Remind me every` field to `90` and the period drop down to `Days` 1. Click `Save` **Remediate from Powershell** ``` $rgName = <resource group name for the storage> $accountName = <storage account name> $account = Get-AzStorageAccount -ResourceGroupName $rgName -Name $accountName if ($account.KeyCreationTime.Key1 -eq $null -or $account.KeyCreationTime.Key2 -eq $null){ Write-output (You must regenerate both keys at least once before setting expiration policy) } else { $account = Set-AzStorageAccount -ResourceGroupName $rgName -Name $accountName -KeyExpirationPeriodInDay 90 } $account.KeyPolicy.KeyExpirationPeriodInDays ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts` 2. For each Storage Account, under `Security + networking`, go to `Access keys` 3. If the button `Edit rotation reminder` is displayed, the Storage Account is compliant. Click `Edit rotation reminder` and review the `Remind me every` field for a desirable periodic setting that fits your security program's needs. If the button `Set rotation reminder` is displayed, the Storage Account is not compliant. **Audit from Powershell** ``` $rgName = <resource group name for the storage> $accountName = <storage account name> $account = Get-AzStorageAccount -ResourceGroupName $rgName -Name $accountName Write-Output $accountName -> Write-Output Expiration Reminder set to: $($account.KeyPolicy.KeyExpirationPeriodInDays) Days Write-Output Key1 Last Rotated: $($account.KeyCreationTime.Key1.ToShortDateString()) Write-Output Key2 Last Rotated: $($account.KeyCreationTime.Key2.ToShortDateString()) ``` Key rotation is recommended if the creation date for any key is empty. If the reminder is set, the period in days will be returned. The recommended period is 90 days. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [044985bb-afe1-42cd-8a36-9d5d42424537](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F044985bb-afe1-42cd-8a36-9d5d42424537) **- Name:** 'Storage account keys should not be expired'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/storage-create-storage-account#regenerate-storage-access-keys:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-1-separate-and-limit-highly-privilegedadministrative-users:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-3-manage-application-identities-securely-and-automatically:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-6-define-and-implement-identity-and-privileged-access-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-8-restrict-the-exposure-of-credentials-and-secrets:https://www.pcidssguide.com/pci-dss-key-rotation-requirements/:https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf",
+ "DefaultValue": "By default, Key rotation reminders are not configured."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.1.2",
+ "Description": "Ensure That Storage Account Access keys are Periodically Regenerated",
+ "Checks": [
+ "storage_key_rotation_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure That Storage Account Access keys are Periodically Regenerated",
+ "RationaleStatement": "When a storage account is created, Azure generates two 512-bit storage access keys which are used for authentication when the storage account is accessed. Rotating these keys periodically ensures that any inadvertent access or exposure does not result from the compromise of these keys. Cryptographic key rotation periods will vary depending on your organization's security requirements and the type of data which is being stored in the Storage Account. For example, PCI DSS mandates that cryptographic keys be replaced or rotated 'regularly,' and advises that keys for static data stores be rotated every 'few months.' For the purposes of this recommendation, 90 days will be prescribed for the reminder. Review and adjustment of the 90 day period is recommended, and may even be necessary. Your organization's security requirements should dictate the appropriate setting.",
+ "ImpactStatement": "Regenerating access keys can affect services in Azure as well as the organization's applications that are dependent on the storage account. All clients who use the access key to access the storage account must be updated to use the new key.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 2. For each Storage Account with outdated keys, under `Security + networking`, go to `Access keys`. 3. Click `Rotate key` next to the outdated key, then click `Yes` to the prompt confirming that you want to regenerate the access key. After Azure regenerates the Access Key, you can confirm that `Access keys` reflects a `Last rotated` date of `(0 days ago)`.",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 2. For each Storage Account, under `Security + networking`, go to `Access keys`. 3. Review the date and days in the `Last rotated` field for **each** key. If the `Last rotated` field indicates a number or days greater than 90 [or greater than your organization's period of validity], the key should be rotated. **Audit from Azure CLI** 1. Get a list of storage accounts ``` az storage account list --subscription <subscription-id> ``` Make a note of `id`, `name` and `resourceGroup`. 2. For every storage account make sure that key is regenerated in the past 90 days. ``` az monitor activity-log list --namespace Microsoft.Storage --offset 90d --query [?contains(authorization.action, 'regenerateKey')] --resource-id <resource id> ``` The output should contain ``` authorization/scope: <your_storage_account> AND authorization/action: Microsoft.Storage/storageAccounts/regeneratekey/action AND status/localizedValue: Succeeded status/Value: Succeeded ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [044985bb-afe1-42cd-8a36-9d5d42424537](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F044985bb-afe1-42cd-8a36-9d5d42424537) **- Name:** 'Storage account keys should not be expired'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/storage-create-storage-account#regenerate-storage-access-keys:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-1-separate-and-limit-highly-privilegedadministrative-users:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-2-protect-identity-and-authentication-systems:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-6-define-and-implement-identity-and-privileged-access-strategy:https://www.pcidssguide.com/pci-dss-key-rotation-requirements/:https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf",
+ "DefaultValue": "By default, access keys are not regenerated periodically."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.1.3",
+ "Description": "Ensure 'Allow storage account key access' for Azure Storage Accounts is 'Disabled'",
+ "Checks": [
+ "storage_account_key_access_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Allow storage account key access' for Azure Storage Accounts is 'Disabled'",
+ "RationaleStatement": "Microsoft Entra ID provides superior security and ease of use compared to Shared Key and is recommended by Microsoft. To require clients to use Microsoft Entra ID for authorizing requests, you can disallow requests to the storage account that are authorized with Shared Key.",
+ "ImpactStatement": "When you disallow Shared Key authorization for a storage account, any requests to the account that are authorized with Shared Key, including shared access signatures (SAS), will be denied. Client applications that currently access the storage account using the Shared Key will no longer function.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click on a storage account. 1. Under `Settings`, click `Configuration`. 1. Under `Allow storage account key access`, click the radio button next to `Disabled`. 1. Click `Save`. 1. Repeat steps 1-5 for each storage account requiring remediation. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to disallow shared key authorization: ``` az storage account update --resource-group <resource-group> --name <storage-account> --allow-shared-key-access false ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to disallow shared key authorization: ``` Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> -AllowSharedKeyAccess $false ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click on a storage account. 1. Under `Settings`, click `Configuration`. 1. Under `Allow storage account key access`, ensure that the radio button next to `Disabled` is selected. 1. Repeat steps 1-4 for each storage account. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` For each storage account, run the following command: ``` az storage account show --resource-group <resource-group> --name <storage-account> ``` Ensure that `allowSharedKeyAccess` is set to `false`. **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount ``` Run the following command to get the storage account in a resource group with a given name: ``` $storageAccount = Get-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> ``` Run the following command to get the shared key access setting for the storage account: ``` $storageAccount.allowSharedKeyAccess ``` Ensure that the command returns `False`. Repeat for each storage account. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54) **- Name:** 'Storage accounts should prevent shared key access'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/common/shared-key-authorization-prevent:https://learn.microsoft.com/en-us/cli/azure/storage/account:https://learn.microsoft.com/en-us/powershell/module/az.storage/get-azstorageaccount:https://learn.microsoft.com/en-us/powershell/module/az.storage/set-azstorageaccount",
+ "DefaultValue": "The AllowSharedKeyAccess property of a storage account is not set by default and does not return a value until you explicitly set it. The storage account permits requests that are authorized with the Shared Key when the property value is **null** or when it is **true**."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.2.1",
+ "Description": "Ensure Private Endpoints are Used to Access Storage Accounts",
+ "Checks": [
+ "storage_ensure_private_endpoints_in_storage_accounts"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Private Endpoints are Used to Access Storage Accounts",
+ "RationaleStatement": "Securing traffic between services through encryption protects the data from easy interception and reading.",
+ "ImpactStatement": "If an Azure Virtual Network is not implemented correctly, this may result in the loss of critical network traffic. Private endpoints are charged per hour of use. Refer to https://azure.microsoft.com/en-us/pricing/details/private-link/ and https://azure.microsoft.com/en-us/pricing/calculator/ to estimate potential costs.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Open the `Storage Accounts` blade 1. For each listed Storage Account, perform the following: 1. Under the `Security + networking` heading, click on `Networking` 1. Click on the `Private endpoint connections` tab at the top of the networking window 1. Click the `+ Private endpoint` button 1. In the `1 - Basics` tab/step: - `Enter a name` that will be easily recognizable as associated with the Storage Account (*Note*: The Network Interface Name will be automatically completed, but you can customize it if needed.) - Ensure that the `Region` matches the region of the Storage Account - Click `Next` 1. In the `2 - Resource` tab/step: - Select the `target sub-resource` based on what type of storage resource is being made available - Click `Next` 1. In the `3 - Virtual Network` tab/step: - Select the `Virtual network` that your Storage Account will be connecting to - Select the `Subnet` that your Storage Account will be connecting to - (Optional) Select other network settings as appropriate for your environment - Click `Next` 1. In the `4 - DNS` tab/step: - (Optional) Select other DNS settings as appropriate for your environment - Click `Next` 1. In the `5 - Tags` tab/step: - (Optional) Set any tags that are relevant to your organization - Click `Next` 1. In the `6 - Review + create` tab/step: - A validation attempt will be made and after a few moments it should indicate `Validation Passed` - if it does not pass, double-check your settings before beginning more in depth troubleshooting. - If validation has passed, click `Create` then wait for a few minutes for the scripted deployment to complete. Repeat the above procedure for each Private Endpoint required within every Storage Account. **Remediate from PowerShell** ``` $storageAccount = Get-AzStorageAccount -ResourceGroupName '<ResourceGroupName>' -Name '<storageaccountname>' $privateEndpointConnection = @{ Name = 'connectionName' PrivateLinkServiceId = $storageAccount.Id GroupID = blob|blob_secondary|file|file_secondary|table|table_secondary|queue|queue_secondary|web|web_secondary|dfs|dfs_secondary } $privateLinkServiceConnection = New-AzPrivateLinkServiceConnection @privateEndpointConnection $virtualNetDetails = Get-AzVirtualNetwork -ResourceGroupName '<ResourceGroupName>' -Name '<name>' $privateEndpoint = @{ ResourceGroupName = '<ResourceGroupName>' Name = '<PrivateEndpointName>' Location = '<location>' Subnet = $virtualNetDetails.Subnets[0] PrivateLinkServiceConnection = $privateLinkServiceConnection } New-AzPrivateEndpoint @privateEndpoint ``` **Remediate from Azure CLI** ``` az network private-endpoint create --resource-group <ResourceGroupName --location <location> --name <private endpoint name> --vnet-name <VNET Name> --subnet <subnet name> --private-connection-resource-id <storage account ID> --connection-name <private link service connection name> --group-id <blob|blob_secondary|file|file_secondary|table|table_secondary|queue|queue_secondary|web|web_secondary|dfs|dfs_secondary> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Open the `Storage Accounts` blade. 1. For each listed Storage Account, perform the following check: 1. Under the `Security + networking` heading, click on `Networking`. 1. Click on the `Private endpoint connections` tab at the top of the networking window. 1. Ensure that for each VNet that the Storage Account must be accessed from, a unique Private Endpoint is deployed and the `Connection state` for each Private Endpoint is `Approved`. Repeat the procedure for each Storage Account. **Audit from PowerShell** ``` $storageAccount = Get-AzStorageAccount -ResourceGroup '<ResourceGroupName>' -Name '<storageaccountname>' Get-AzPrivateEndpoint -ResourceGroup '<ResourceGroupName>'|Where-Object {$_.PrivateLinkServiceConnectionsText -match $storageAccount.id} ``` If the results of the second command returns information, the Storage Account is using a Private Endpoint and complies with this Benchmark, otherwise if the results of the second command are empty, the Storage Account generates a finding. **Audit from Azure CLI** ``` az storage account show --name '<storage account name>' --query privateEndpointConnections[0].id ``` If the above command returns data, the Storage Account complies with this Benchmark, otherwise if the results are empty, the Storage Account generates a finding. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [6edd7eda-6dd8-40f7-810d-67160c639cd9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F6edd7eda-6dd8-40f7-810d-67160c639cd9) **- Name:** 'Storage accounts should use private link'",
+ "AdditionalInformation": "A NAT gateway is the recommended solution for outbound internet access. This recommendation is based on the Common Reference Recommendation `Ensure Private Endpoints are used to access {service}`, from the `Common Reference Recommendations > Networking > Private Endpoints` section.",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/storage-private-endpoints:https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview:https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-portal:https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-cli?tabs=dynamic-ip:https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-powershell?tabs=dynamic-ip:https://docs.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-2-secure-cloud-native-services-with-network-controls",
+ "DefaultValue": "By default, Private Endpoints are not created for Storage Accounts."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.2.2",
+ "Description": "Ensure that 'Public Network Access' is 'Disabled' for Storage Accounts",
+ "Checks": [
+ "storage_account_public_network_access_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Public Network Access' is 'Disabled' for Storage Accounts",
+ "RationaleStatement": "The default network configuration for a storage account permits a user with appropriate permissions to configure public network access to containers and blobs in a storage account. Keep in mind that public access to a container is always turned off by default and must be explicitly configured to permit anonymous requests. It grants read-only access to these resources without sharing the account key, and without requiring a shared access signature. It is recommended not to provide public network access to storage accounts until, and unless, it is strongly desired. A shared access signature token or Azure AD RBAC should be used for providing controlled and timed access to blob containers.",
+ "ImpactStatement": "Access will have to be managed using shared access signatures or via Azure AD RBAC. For classic storage accounts (to be retired on August 31, 2024), each container in the account must be configured to block anonymous access. Either configure all containers or to configure at the storage account level, migrate to the Azure Resource Manager deployment model.",
+ "RemediationProcedure": "**Remediate from Azure Portal** First, follow Microsoft documentation and create shared access signature tokens for your blob containers. Then, 1. Go to `Storage Accounts`. 1. For each storage account, under the `Security + networking` section, click `Networking`. 1. Set `Public network access` to `Disabled`. 1. Click `Save`. **Remediate from Azure CLI** Set 'Public Network Access' to `Disabled` on the storage account ``` az storage account update --name <storage-account> --resource-group <resource-group> --public-network-access Disabled ``` **Remediate from PowerShell** For each Storage Account, run the following to set the `PublicNetworkAccess` setting to `Disabled` ``` Set-AzStorageAccount -ResourceGroupName <resource group name> -Name <storage account name> -PublicNetworkAccess Disabled ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 2. For each storage account, under the `Security + networking` section, click `Networking`. 3. Ensure the `Public network access` setting is set to `Disabled`. **Audit from Azure CLI** Ensure `publicNetworkAccess` is `Disabled` ``` az storage account show --name <storage-account> --resource-group <resource-group> --query {publicNetworkAccess:publicNetworkAccess} ``` **Audit from PowerShell** For each Storage Account, ensure `PublicNetworkAccess` is `Disabled` ``` Get-AzStorageAccount -Name <storage account name> -ResourceGroupName <resource group name> |select PublicNetworkAccess ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [b2982f36-99f2-4db5-8eff-283140c09693](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb2982f36-99f2-4db5-8eff-283140c09693) **- Name:** 'Storage accounts should disable public network access'",
+ "AdditionalInformation": "This recommendation is based on the Common Reference Recommendation `Ensure public network access is Disabled`, from the `Common Reference Recommendations > Networking > Virtual Networks (VNets)` section.",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/blobs/storage-manage-access-to-resources:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-2-define-and-implement-enterprise-segmentationseparation-of-duties-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-2-secure-cloud-native-services-with-network-controls:https://docs.microsoft.com/en-us/azure/storage/blobs/assign-azure-role-data-access:https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal",
+ "DefaultValue": "By default, `Public Network Access` is set to `Enabled from all networks` for the Storage Account."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.2.3",
+ "Description": "Ensure Default Network Access Rule for Storage Accounts is Set to Deny",
+ "Checks": [
+ "storage_default_network_access_rule_is_denied"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Default Network Access Rule for Storage Accounts is Set to Deny",
+ "RationaleStatement": "Storage accounts should be configured to deny access to traffic from all networks (including internet traffic). Access can be granted to traffic from specific Azure Virtual networks, allowing a secure network boundary for specific applications to be built. Access can also be granted to public internet IP address ranges to enable connections from specific internet or on-premises clients. When network rules are configured, only applications from allowed networks can access a storage account. When calling from an allowed network, applications continue to require proper authorization (a valid access key or SAS token) to access the storage account.",
+ "ImpactStatement": "All allowed networks will need to be whitelisted on each specific network, creating administrative overhead. This may result in loss of network connectivity, so do not turn on for critical resources during business hours.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Security + networking`, click `Networking`. 1. Click the `Firewalls and virtual networks` heading. 1. Set `Public network access` to `Enabled from selected virtual networks and IP addresses`. 1. Add rules to allow traffic from specific networks and IP addresses. 1. Click `Save`. **Remediate from Azure CLI** Use the below command to update `default-action` to `Deny`. ``` az storage account update --name <StorageAccountName> --resource-group <resourceGroupName> --default-action Deny ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to Storage Accounts. 2. For each storage account, under `Security + networking`, click `Networking`. 4. Click the `Firewalls and virtual networks` heading. 3. Ensure that `Public network access` is not set to `Enabled from all networks`. **Audit from Azure CLI** Ensure `defaultAction` is not set to ` Allow`. ``` az storage account list --query '[*].networkRuleSet' ``` **Audit from PowerShell** ``` Connect-AzAccount Set-AzContext -Subscription <subscription ID> Get-AzStorageAccountNetworkRuleset -ResourceGroupName <resource group> -Name <storage account name> |Select-Object DefaultAction ``` PowerShell Result - Non-Compliant ``` DefaultAction : Allow ``` PowerShell Result - Compliant ``` DefaultAction : Deny ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [34c877ad-507e-4c82-993e-3452a6e0ad3c](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F34c877ad-507e-4c82-993e-3452a6e0ad3c) **- Name:** 'Storage accounts should restrict network access' - **Policy ID:** [2a1a9cdf-e04d-429a-8416-3bfb72a1b26f](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F2a1a9cdf-e04d-429a-8416-3bfb72a1b26f) **- Name:** 'Storage accounts should restrict network access using virtual network rules'",
+ "AdditionalInformation": "This recommendation is based on the Common Reference Recommendation `Ensure Network Access Rules are set to Deny-by-default`, from the `Common Reference Recommendations > Networking > Virtual Networks (VNets)` section.",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-governance-strategy#gs-2-define-and-implement-enterprise-segmentationseparation-of-duties-strategy:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-2-secure-cloud-native-services-with-network-controls",
+ "DefaultValue": "By default, Storage Accounts will accept connections from clients on any network."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.3.1",
+ "Description": "Ensure that 'Default to Microsoft Entra authorization in the Azure portal' is Set to 'Enabled'",
+ "Checks": [
+ "storage_default_to_entra_authorization_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Default to Microsoft Entra authorization in the Azure portal' is Set to 'Enabled'",
+ "RationaleStatement": "Microsoft Entra ID provides superior security and ease of use over Shared Key.",
+ "ImpactStatement": "Users will need appropriate RBAC permissions to access storage data.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Settings`, click `Configuration`. 1. Under `Default to Microsoft Entra authorization in the Azure portal`, click the radio button next to `Enabled`. 1. Click `Save`. 1. Repeat steps 1-5 for each storage account requiring remediation. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable `defaultToOAuthAuthentication`: ``` az storage account update --resource-group <resource-group> --name <storage-account> --set defaultToOAuthAuthentication=true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click the name of a storage account. 1. Under `Settings`, click `Configuration`. 1. Ensure that `Default to Microsoft Entra authorization in the Azure portal` is set to `Enabled`. 1. Repeat steps 1-4 for each storage account. **Audit from Azure CLI** Run the following command to get the `name` and `defaultToOAuthAuthentication` setting for each storage account: ``` az storage account list --query [*].[name,defaultToOAuthAuthentication] ``` Ensure that `true` is returned for each storage account.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-data-operations-portal#default-to-microsoft-entra-authorization-in-the-azure-portal:https://learn.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest",
+ "DefaultValue": "By default, `defaultToOAuthAuthentication` is disabled."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.4",
+ "Description": "Ensure that 'Secure transfer required' is Set to 'Enabled'",
+ "Checks": [
+ "storage_secure_transfer_required_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Secure transfer required' is Set to 'Enabled'",
+ "RationaleStatement": "The secure transfer option enhances the security of a storage account by only allowing requests to the storage account by a secure connection. For example, when calling REST APIs to access storage accounts, the connection must use HTTPS. Any requests using HTTP will be rejected when 'secure transfer required' is enabled. When using the Azure files service, connection without encryption will fail, including scenarios using SMB 2.1, SMB 3.0 without encryption, and some flavors of the Linux SMB client. Because Azure storage doesnt support HTTPS for custom domain names, this option is not applied when using a custom domain name.",
+ "ImpactStatement": "Applications using HTTP will need to be updated to use HTTPS.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Set `Secure transfer required` to `Enabled`. 1. Click `Save`. **Remediate from Azure CLI** Use the below command to enable `Secure transfer required` for a `Storage Account` ``` az storage account update --name <storageAccountName> --resource-group <resourceGroupName> --https-only true ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Ensure that `Secure transfer required` is set to `Enabled`. **Audit from Azure CLI** Use the below command to ensure the `Secure transfer required` is enabled for all the `Storage Accounts` by ensuring the output contains `true` for each of the `Storage Accounts`. ``` az storage account list --query [*].[name,enableHttpsTrafficOnly] ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [404c3081-a854-4457-ae30-26a93ef643f9](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F404c3081-a854-4457-ae30-26a93ef643f9) **- Name:** 'Secure transfer to storage accounts should be enabled'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/blobs/security-recommendations#encryption-in-transit:https://docs.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest#az_storage_account_list:https://docs.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest#az_storage_account_update:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-3-encrypt-sensitive-data-in-transit",
+ "DefaultValue": "By default, `Secure transfer required` is set to `Disabled`."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.5",
+ "Description": "Ensure 'Allow trusted Microsoft services to access this resource' is Enabled for Storage Account Access",
+ "Checks": [
+ "storage_ensure_azure_services_are_trusted_to_access_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Allow trusted Microsoft services to access this resource' is Enabled for Storage Account Access",
+ "RationaleStatement": "Turning on firewall rules for a storage account will block access to incoming requests for data, including from other Azure services. We can re-enable this functionality by allowing access to `trusted Azure services` through networking exceptions.",
+ "ImpactStatement": "This creates authentication credentials for services that need access to storage resources so that services will no longer need to communicate via network request. There may be a temporary loss of communication as you set each Storage Account. It is recommended to not do this on mission-critical resources during business hours.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Security + networking`, click `Networking`. 1. Click on the `Firewalls and virtual networks` heading. 1. Under `Exceptions`, check the box next to `Allow Azure services on the trusted services list to access this storage account`. 1. Click `Save`. **Remediate from Azure CLI** Use the below command to update `bypass` to `Azure services`. ``` az storage account update --name <StorageAccountName> --resource-group <resourceGroupName> --bypass AzureServices ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Security + networking`, click `Networking`. 1. Click on the `Firewalls and virtual networks` heading. 1. Under `Exceptions`, ensure that `Allow Azure services on the trusted services list to access this storage account` is checked. **Audit from Azure CLI** Ensure `bypass` contains `AzureServices` ``` az storage account list --query '[*].networkRuleSet' ``` **Audit from PowerShell** ``` Connect-AzAccount Set-AzContext -Subscription <subscription ID> Get-AzStorageAccountNetworkRuleset -ResourceGroupName <resource group> -Name <storage account name> |Select-Object Bypass ``` If the response from the above command is `None`, the storage account configuration is out of compliance with this check. If the response is `AzureServices`, the storage account configuration is in compliance with this check. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [c9d007d0-c057-4772-b18c-01e546713bcd](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc9d007d0-c057-4772-b18c-01e546713bcd) **- Name:** 'Storage accounts should allow access from trusted Microsoft services'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-2-secure-cloud-native-services-with-network-controls",
+ "DefaultValue": "By default, Storage Accounts will accept connections from clients on any network."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.6",
+ "Description": "Ensure the 'Minimum TLS version' for Storage Accounts is Set to 'Version 1.2'",
+ "Checks": [
+ "storage_ensure_minimum_tls_version_12"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure the 'Minimum TLS version' for Storage Accounts is Set to 'Version 1.2'",
+ "RationaleStatement": "TLS 1.0 has known vulnerabilities and has been replaced by later versions of the TLS protocol. Continued use of this legacy protocol affects the security of data in transit.",
+ "ImpactStatement": "When set to TLS 1.2 all requests must leverage this version of the protocol. Applications leveraging legacy versions of the protocol will fail.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Set the `Minimum TLS version` to `Version 1.2`. 1. Click `Save`. **Remediate from Azure CLI** ``` az storage account update \\ --name <storage-account> \\ --resource-group <resource-group> \\ --min-tls-version TLS1_2 ``` **Remediate from PowerShell** To set the minimum TLS version, run the following command: ``` Set-AzStorageAccount -AccountName <STORAGEACCOUNTNAME> ` -ResourceGroupName <RESOURCEGROUPNAME> ` -MinimumTlsVersion TLS1_2 ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Ensure that the `Minimum TLS version` is set to `Version 1.2`. **Audit from Azure CLI** Get a list of all storage accounts and their resource groups ``` az storage account list | jq '.[] | {name, resourceGroup}' ``` Then query the minimumTLSVersion field ``` az storage account show \\ --name <storage-account> \\ --resource-group <resource-group> \\ --query minimumTlsVersion \\ --output tsv ``` **Audit from PowerShell** To get the minimum TLS version, run the following command: ``` (Get-AzStorageAccount -Name <STORAGEACCOUNTNAME> -ResourceGroupName <RESOURCEGROUPNAME>).MinimumTlsVersion ``` **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [fe83a0eb-a853-422d-aac2-1bffd182c5d0](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ffe83a0eb-a853-422d-aac2-1bffd182c5d0) **- Name:** 'Storage accounts should have the specified minimum TLS version'",
+ "AdditionalInformation": "",
+ "References": "https://docs.microsoft.com/en-us/azure/storage/common/transport-layer-security-configure-minimum-version?tabs=portal:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-data-protection#dp-3-encrypt-sensitive-data-in-transit",
+ "DefaultValue": "If a storage account is created through the portal, the MinimumTlsVersion property for that storage account will be set to TLS 1.2. If a storage account is created through PowerShell or CLI, the MinimumTlsVersion property for that storage account will not be set, and defaults to TLS 1.0."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.7",
+ "Description": "Ensure 'Cross Tenant Replication' is Not Enabled",
+ "Checks": [
+ "storage_cross_tenant_replication_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure 'Cross Tenant Replication' is Not Enabled",
+ "RationaleStatement": "Disabling Cross Tenant Replication minimizes the risk of unauthorized data access and ensures that data governance policies are strictly adhered to. This control is especially critical for organizations with stringent data security and privacy requirements, as it prevents the accidental sharing of sensitive information.",
+ "ImpactStatement": "Disabling Cross Tenant Replication may affect data availability and sharing across different Azure tenants. Ensure that this change aligns with your organizational data sharing and availability requirements.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Data management`, click `Object replication`. 1. Click `Advanced settings`. 1. Uncheck `Allow cross-tenant replication`. 1. Click `OK`. **Remediate from Azure CLI** Replace the information within <> with appropriate values: ``` az storage account update --name <storageAccountName> --resource-group <resourceGroupName> --allow-cross-tenant-replication false ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Data management`, click `Object replication`. 1. Click `Advanced settings`. 1. Ensure `Allow cross-tenant replication` is not checked. **Audit from Azure CLI** ``` az storage account list --query [*].[name,allowCrossTenantReplication] ``` The value of `false` should be returned for each storage account listed. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [92a89a79-6c52-4a7e-a03f-61306fc49312](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F92a89a79-6c52-4a7e-a03f-61306fc49312) **- Name:** 'Storage accounts should prevent cross tenant object replication'",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-prevent-cross-tenant-policies?tabs=portal",
+ "DefaultValue": "For new storage accounts created after Dec 15, 2023 cross tenant replication is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.8",
+ "Description": "Ensure that 'Allow Blob Anonymous Access' is Set to 'Disabled'",
+ "Checks": [
+ "storage_blob_public_access_level_is_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that 'Allow Blob Anonymous Access' is Set to 'Disabled'",
+ "RationaleStatement": "If Allow Blob Anonymous Access is enabled, blobs can be accessed by adding the blob name to the URL to see the contents. An attacker can enumerate a blob using methods, such as brute force, and access them. Exfiltration of data by brute force enumeration of items from a storage account may occur if this setting is set to 'Enabled'.",
+ "ImpactStatement": "Additional consideration may be required for exceptional circumstances where elements of a storage account require public accessibility. In these circumstances, it is highly recommended that all data stored in the public facing storage account be reviewed for sensitive or potentially compromising data, and that sensitive or compromising data is never stored in these storage accounts.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Set `Allow Blob Anonymous Access` to `Disabled`. 1. Click `Save`. **Remediate from Powershell** For every storage account in scope, run the following: ``` $storageAccount = Get-AzStorageAccount -ResourceGroupName <yourResourceGroup> -Name <yourStorageAccountName> $storageAccount.AllowBlobPublicAccess = $false Set-AzStorageAccount -InputObject $storageAccount ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage Accounts`. 1. For each storage account, under `Settings`, click `Configuration`. 1. Ensure `Allow Blob Anonymous Access` is set to `Disabled`. **Audit from Azure CLI** For every storage account in scope: ``` az storage account show --name <yourStorageAccountName> --query allowBlobPublicAccess ``` Ensure that every storage account in scope returns `false` for the allowBlobPublicAccess setting. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [4fa4b6c0-31ca-4c0d-b10d-24b96f62a751](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F4fa4b6c0-31ca-4c0d-b10d-24b96f62a751) **- Name:** 'Storage account public access should be disallowed'",
+ "AdditionalInformation": "Azure Storage accounts that use the classic deployment model will be retired on August 31, 2024.",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent?tabs=portal:https://learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent?source=recommendations&tabs=portal:Classic Storage Accounts: https://learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent-classic?tabs=portal",
+ "DefaultValue": "Disabled"
+ }
+ ]
+ },
+ {
+ "Id": "9.3.9",
+ "Description": "Ensure Azure Resource Manager Delete Locks are Applied to Azure Storage Accounts",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Azure Resource Manager Delete Locks are Applied to Azure Storage Accounts",
+ "RationaleStatement": "Applying a _Delete_ lock on storage accounts protects the availability of data by preventing the accidental or unauthorized deletion of the entire storage account. It is a fundamental protective control that can prevent data loss",
+ "ImpactStatement": "- Prevents the deletion of the Storage account Resource entirely. - Prevents the deletion of the parent Resource Group containing the locked Storage account resource. - Does not prevent other control plane operations, including modification of configurations, network settings, containers, and access. - Does not prevent deletion of containers or other objects within the storage account.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the storage account in the Azure portal. 1. Under the `Settings` section, select `Locks`. 1. Select `Add`. 1. Provide a Name, and choose `Delete` for the type of lock. 1. Add a note about the lock if desired. **Remediate from Azure CLI** Replace the information within <> with appropriate values: ``` az lock create --name <lock> \\ --resource-group <resource-group> \\ --resource <storage-account> \\ --lock-type CanNotDelete \\ --resource-type Microsoft.Storage/storageAccounts ``` **Remediate from PowerShell** Replace the information within <> with appropriate values: ``` New-AzResourceLock -LockLevel CanNotDelete ` -LockName <lock> ` -ResourceName <storage-account> ` -ResourceType Microsoft.Storage/storageAccounts ` -ResourceGroupName <resource-group> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the storage account in the Azure portal. 1. For each storage account, under `Settings`, click `Locks`. 1. Ensure that a `Delete` lock exists on the storage account. **Audit from Azure CLI** ``` az lock list --resource-group <resource-group> \\ --resource-name <storage-account> \\ --resource-type Microsoft.Storage/storageAccounts ``` **Audit from PowerShell** ``` Get-AzResourceLock -ResourceGroupName <RESOURCEGROUPNAME> ` -ResourceName <STORAGEACCOUNTNAME> ` -ResourceType Microsoft.Storage/storageAccounts ``` **Audit from Azure Policy** There is currently no built-in Microsoft policy to audit resource locks on storage accounts. Custom and community policy definitions can check for the existence of a “Microsoft.Authorization/locks” resource with an AuditIfNotExists effect.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/common/lock-account-resource:https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources",
+ "DefaultValue": "By default, no locks are applied to Azure resources, including storage accounts. Locks must be manually configured after resource creation."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.10",
+ "Description": "Ensure Azure Resource Manager ReadOnly Locks are Considered for Azure Storage Accounts",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure Azure Resource Manager ReadOnly Locks are Considered for Azure Storage Accounts",
+ "RationaleStatement": "Applying a `ReadOnly` lock on storage accounts protects the confidentiality and availability of data by preventing the accidental or unauthorized deletion of the entire storage account and modification of the account, container properties, or access permissions. It can offer enhanced protection for blob and queue workloads with tradeoffs in usability and compatibility for clients using account shared access keys.",
+ "ImpactStatement": "- Prevents the deletion of the Storage account Resource entirely. - Prevents the deletion of the parent Resource Group containing the locked Storage account resource. - Prevents clients from obtaining the storage account shared access keys using a `listKeys` operation. - Requires Entra credentials to access blob and queue data in the Portal. - Data in Azure Files or the Table service may be inaccessible to clients using the account shared access keys. - Prevents modification of account properties, network settings, containers, and RBAC assignments. - Does not prevent access using existing account shared access keys issued to clients. - Does not prevent deletion of containers or other objects within the storage account.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Navigate to the storage account in the Azure portal. 1. Under the `Settings` section, select `Locks`. 1. Select `Add`. 1. Provide a Name, and choose `ReadOnly` for the type of lock. 1. Add a note about the lock if desired. **Remediate from Azure CLI** Replace the information within <> with appropriate values: ``` az lock create --name <lock> \\ --resource-group <resource-group> \\ --resource <storage-account> \\ --lock-type ReadOnly \\ --resource-type Microsoft.Storage/storageAccounts ``` **Remediate from PowerShell** Replace the information within <> with appropriate values: ``` New-AzResourceLock -LockLevel ReadOnly ` -LockName <lock> ` -ResourceName <storage-account> ` -ResourceType Microsoft.Storage/storageAccounts ` -ResourceGroupName <resource-group> ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Navigate to the storage account in the Azure portal. 1. For each storage account, under `Settings`, click `Locks`. 1. Ensure that a `ReadOnly` lock exists on the storage account. **Audit from Azure CLI** ``` az lock list --resource-group <resource-group> \\ --resource-name <storage-account> \\ --resource-type Microsoft.Storage/storageAccounts ``` **Audit from PowerShell** ``` Get-AzResourceLock -ResourceGroupName <RESOURCEGROUPNAME> ` -ResourceName <STORAGEACCOUNTNAME> ` -ResourceType Microsoft.Storage/storageAccounts ``` **Audit from Azure Policy** There is currently no built-in Microsoft policy to audit resource locks on storage accounts. Custom and community policy definitions can check for the existence of a “Microsoft.Authorization/locks” resource with an AuditIfNotExists effect.",
+ "AdditionalInformation": "",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/common/lock-account-resource:https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources:https://github.com/Azure/azure-rest-api-specs/tree/main/specification/storage",
+ "DefaultValue": "By default, no locks are applied to Azure resources, including storage accounts. Locks must be manually configured after resource creation."
+ }
+ ]
+ },
+ {
+ "Id": "9.3.11",
+ "Description": "Ensure Redundancy is Set to 'geo-redundant storage (GRS)' on Critical Azure Storage Accounts",
+ "Checks": [
+ "storage_geo_redundant_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "9 Storage Services",
+ "SubSection": "9.3 Storage Accounts",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure Redundancy is Set to 'geo-redundant storage (GRS)' on Critical Azure Storage Accounts",
+ "RationaleStatement": "Enabling GRS protects critical data from regional failures by maintaining a copy in a geographically separate location. This significantly reduces the risk of data loss, supports business continuity, and meets high availability requirements for disaster recovery.",
+ "ImpactStatement": "Enabling geo-redundant storage on Azure storage accounts increases costs due to cross-region data replication.",
+ "RemediationProcedure": "**Remediate from Azure Portal** 1. Go to `Storage accounts`. 1. Click on a storage account. 1. Under `Data management`, click `Redundancy`. 1. From the `Redundancy` drop-down menu, select `Geo-redundant storage (GRS)`. 1. Click `Save`. 1. Repeat steps 1-5 for each storage account requiring remediation. **Remediate from Azure CLI** For each storage account requiring remediation, run the following command to enable geo-redundant storage: ``` az storage account update --resource-group <resource-group> --name <storage-account> --sku Standard_GRS ``` **Remediate from PowerShell** For each storage account requiring remediation, run the following command to enable geo-redundant storage: ``` Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> -SkuName Standard_GRS ```",
+ "AuditProcedure": "**Audit from Azure Portal** 1. Go to `Storage accounts`. 1. Click on a storage account. 1. Under `Data management`, click `Redundancy`. 1. Ensure that `Redundancy` is set to `Geo-redundant storage (GRS)`. 1. Repeat steps 1-4 for each storage account. **Audit from Azure CLI** Run the following command to list storage accounts: ``` az storage account list ``` For each storage account, run the following command: ``` az storage account show --resource-group <resource-group> --name <storage-account> ``` Under `sku`, ensure that `name` is set to `Standard_GRS`. **Audit from PowerShell** Run the following command to list storage accounts: ``` Get-AzStorageAccount ``` Run the following command to get the storage account in a resource group with a given name: ``` $storageAccount = Get-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> ``` Run the following command to get the redundancy setting for the storage account: ``` $storageAccount.SKU.Name ``` Ensure that the command returns `Standard_GRS`. Repeat for each storage account. **Audit from Azure Policy** If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions - **Policy ID:** [bf045164-79ba-4215-8f95-f8048dc1780b](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fbf045164-79ba-4215-8f95-f8048dc1780b) **- Name:** 'Geo-redundant storage should be enabled for Storage Accounts'",
+ "AdditionalInformation": "When choosing the best redundancy option, weigh the trade-offs between lower costs and higher availability. Key factors to consider include: - The method of data replication within the primary region. - The replication of data from a primary to a geographically distant secondary region for protection against regional disasters (geo-replication). - The necessity for read access to replicated data in the secondary region during an outage in the primary region (geo-replication with read access).",
+ "References": "https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy:https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration:https://learn.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest#az-storage-account-update:https://learn.microsoft.com/en-us/powershell/module/az.storage/set-azstorageaccount?view=azps-12.4.0:https://learn.microsoft.com/en-us/azure/storage/common/storage-disaster-recovery-guidance",
+ "DefaultValue": "When creating a storage account in the Azure Portal, the default redundancy setting is geo-redundant storage (GRS). Using the Azure CLI, the default is read-access geo-redundant storage (RA-GRS). In PowerShell, a redundancy level must be explicitly specified during account creation."
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/azure/csa_ccm_4.0_azure.json b/prowler/compliance/azure/csa_ccm_4.0_azure.json
deleted file mode 100644
index b4505ac089..0000000000
--- a/prowler/compliance/azure/csa_ccm_4.0_azure.json
+++ /dev/null
@@ -1,7548 +0,0 @@
-{
- "Framework": "CSA-CCM",
- "Name": "CSA Cloud Controls Matrix (CCM) v4.0.13",
- "Version": "4.0",
- "Provider": "Azure",
- "Description": "The Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing, composed of 197 control objectives structured in 17 domains covering all key aspects of cloud technology. The CCM can be used as a tool for the systematic assessment of a cloud implementation, and provides guidance on which security controls should be implemented by which actor within the cloud supply chain.",
- "Requirements": [
- {
- "Id": "A&A-02",
- "Description": "Conduct independent audit and assurance assessments according to relevant standards at least annually.",
- "Name": "Independent Assessments",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC4.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AAC-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.2",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.2.1",
- "27002: 18.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.35",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-2",
- "CA-2(1)",
- "CA-2(2)",
- "CA-7",
- "CA-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_databases_is_on",
- "defender_ensure_defender_for_keyvault_is_on",
- "defender_ensure_defender_for_server_is_on"
- ]
- },
- {
- "Id": "A&A-04",
- "Description": "Verify compliance with all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit.",
- "Name": "Requirements Compliance",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01",
- "GRM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.18.2.2",
- "27002: 18.2.2",
- "27001: A.18.2.3",
- "27002: 18.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-3",
- "DE.DP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_databases_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_mcas_is_enabled",
- "monitor_diagnostic_settings_exists",
- "policy_ensure_asc_enforcement_enabled"
- ]
- },
- {
- "Id": "AIS-04",
- "Description": "Define and implement a SDLC process for application design, development, deployment, and operation in accordance with security requirements defined by the organization.",
- "Name": "Secure Application Design and Development",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27017: 14.1.1",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.14.2.1",
- "27002: 14.2.1",
- "27017: 14.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.8",
- "27001: A.8.25",
- "27001: A.8.26",
- "27001: A.8.28"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PL-8",
- "PL-8(1)",
- "SA-3",
- "SA-3(1)",
- "SA-4",
- "SA-4(2)",
- "SA-4(3)",
- "SA-4(8)",
- "SA-4(9)",
- "SA-5",
- "SA-8",
- "SA-8(1)-(7)",
- "SA-8(9)-(13)",
- "SA-8(15)-(20)",
- "SA-8(22)",
- "SA-8(24)-(28)",
- "SA-8(30)-(33)",
- "SA-17",
- "SA-17(1)-(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-6",
- "PR.DS-7",
- "PR.IP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1",
- "6.2.3",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_ensure_auth_is_set_up",
- "app_ftp_deployment_disabled",
- "app_function_access_keys_configured",
- "app_function_ftps_deployment_disabled",
- "app_register_with_identity"
- ]
- },
- {
- "Id": "AIS-05",
- "Description": "Implement a testing strategy, including criteria for acceptance of new information systems, upgrades and new versions, which provides application security assurance and maintains compliance while enabling organizational speed of delivery goals. Automate when applicable and possible.",
- "Name": "Automated Application Security Testing",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.12",
- "16.13"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.3",
- "SD2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.8",
- "27001: A.14.2.9",
- "27001: A.12.1.2",
- "27002: 12.1.2",
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27001: A.14.2.2",
- "27002: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.25",
- "27001: A.8.29",
- "27001: A.8.32",
- "27002: 8.25 (e)",
- "27002: 8.32 (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SA-11",
- "SA-11(1)-(9)",
- "SI-6",
- "SI-6(2)",
- "SI-6(3)",
- "SI-10",
- "SI-10(1)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.IP-12",
- "DE.CM-8"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "PR.PS-01",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A.3.2.2",
- "A.3.2.2.1",
- "6.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.4",
- "6.4.1",
- "6.4.2",
- "6.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
- "defender_container_images_resolved_vulnerabilities",
- "defender_container_images_scan_enabled",
- "defender_ensure_defender_for_containers_is_on",
- "sqlserver_va_periodic_recurring_scans_enabled",
- "sqlserver_vulnerability_assessment_enabled"
- ]
- },
- {
- "Id": "AIS-07",
- "Description": "Define and implement a process to remediate application security vulnerabilities, automating remediation when possible.",
- "Name": "Application Vulnerability Remediation",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1",
- "CC7.4",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.2",
- "16.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27001: A.12.6.1",
- "27002: 12.6.1",
- "27017: 12.6.1",
- "27018: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.26",
- "27001: A.8.8",
- "27002: 5.26 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-2",
- "SI-2(2)-(6)",
- "SA-11",
- "SA-11(2)",
- "SA-15",
- "SA-15(1)-(3)",
- "SA-15(5)-(8)",
- "SA-15(10)-(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.IP-12",
- "DE.CM-8",
- "RS.AN-5",
- "RS.MI-3",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.2",
- "6.5",
- "6.5.1-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "11.3.1",
- "11.3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_container_images_resolved_vulnerabilities",
- "defender_container_images_scan_enabled",
- "defender_ensure_defender_for_containers_is_on",
- "sqlserver_va_scan_reports_configured",
- "sqlserver_vulnerability_assessment_enabled"
- ]
- },
- {
- "Id": "BCR-08",
- "Description": "Periodically backup data stored in the cloud. Ensure the confidentiality, integrity and availability of the backup, and verify data restoration from backup for resiliency.",
- "Name": "Backup",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "A1.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "11.1",
- "11.2",
- "11.3",
- "11.4",
- "11.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27017: 12.3",
- "27018: 12.3.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.13",
- "27001: A.5.23",
- "27001: A.5.30",
- "27002: 8.13",
- "27002: 5.23 2nd (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-4",
- "CP-4(4)",
- "CP-6",
- "CP-6(1)-(3)",
- "CP-9",
- "CP-9(1)",
- "CP-9(2)",
- "CP-10",
- "CP-10(2)",
- "CP-10(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-4",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-11",
- "RC.RP-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.5.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "10.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "storage_ensure_encryption_with_customer_managed_keys",
- "vm_backup_enabled",
- "vm_sufficient_daily_backup_retention_period"
- ]
- },
- {
- "Id": "BCR-09",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain a disaster response plan to recover from natural and man-made disasters. Update the plan at least annually or upon significant changes.",
- "Name": "Disaster Response Plan",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9",
- "1.6.1",
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.4",
- "BC2.1",
- "BC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.29",
- "27001: A.5.30",
- "27002: 5.29",
- "27002: 5.30"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2(1)",
- "CP-2(2)",
- "CP-2(3)",
- "CP-2(5)",
- "CP-2(6)",
- "CP-2(7)",
- "CP-2(8)",
- "PE-13",
- "PE-13(1)",
- "PE-13(2)",
- "PE-13(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-9",
- "PR.IP-10",
- "RC.IM-1",
- "RC.IM-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-04"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_server_is_on",
- "vm_backup_enabled"
- ]
- },
- {
- "Id": "BCR-11",
- "Description": "Supplement business-critical equipment with redundant equipment independently located at a reasonable minimum distance in accordance with applicable industry standards.",
- "Name": "Equipment Redundancy",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-06"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.20",
- "27001: A.7.11",
- "27001: A.8.14",
- "27002: 5.20 (t)",
- "27002: 8.14 (c)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "CP-4(3)",
- "CP-6",
- "CP-6(1)",
- "CP-7",
- "CP-8",
- "CP-8(1)-(3)",
- "CP-9",
- "CP-9(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.BE-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.OC-04",
- "GV.OC-05",
- "PR.IR-03"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "storage_blob_versioning_is_enabled",
- "storage_geo_redundant_enabled",
- "vm_scaleset_associated_with_load_balancer",
- "vm_scaleset_not_empty"
- ]
- },
- {
- "Id": "CCC-04",
- "Description": "Restrict the unauthorized addition, removal, update, and management of organization assets.",
- "Name": "Unauthorized Change Protection",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "CCC-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.1",
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4",
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.1.4",
- "27002: 12.1.4",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27001: A.14.2.2",
- "27017: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.3",
- "27001: A.8.4",
- "27001: A.8.15",
- "27001: A.8.31",
- "27001: A.8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(4)",
- "CM-3",
- "CM-3(1)",
- "CM-3(5)",
- "CM-3(7)",
- "CM-3(8)",
- "CM-5",
- "CM-5(1)",
- "CM-5(4)",
- "CM-5(5)",
- "CM-6",
- "CM-6(1)",
- "CM-6(2)",
- "CM-7",
- "CM-7(1)",
- "CM-7(4)",
- "CM-7(5)",
- "CM-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.MA-1",
- "PR.MA-2",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04",
- "ID.AM-08",
- "PR.PS-02",
- "PR.PS-03",
- "PR.PS-05",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.1",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_custom_role_has_permissions_to_administer_resource_locks",
- "monitor_alert_create_policy_assignment",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_diagnostic_settings_exists",
- "policy_ensure_asc_enforcement_enabled",
- "storage_ensure_soft_delete_is_enabled"
- ]
- },
- {
- "Id": "CCC-07",
- "Description": "Implement detection measures with proactive notification in case of changes deviating from the established baseline.",
- "Name": "Detection of Baseline Deviation",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.1",
- "1.5.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.2",
- "27001: A.14.2.4",
- "27001: A.12.4.1",
- "27002: 12.4.1 (g)",
- "27001: A.5.1.1",
- "27017: 5.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.9",
- "27001: A.8.15",
- "27002: 8.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(2)",
- "SI-2",
- "SI-2(2)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.MA-1",
- "PR.IP-1",
- "DE.DP-4",
- "PR.IP-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01",
- "DE.CM-09",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.3",
- "6.4.5.4",
- "11.5",
- "11.5.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "11.5.2",
- "11.6.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_wdatp_is_enabled",
- "monitor_alert_create_policy_assignment",
- "monitor_alert_create_update_nsg",
- "monitor_alert_create_update_public_ip_address_rule",
- "monitor_alert_create_update_security_solution",
- "monitor_alert_create_update_sqlserver_fr",
- "monitor_alert_delete_nsg",
- "monitor_alert_delete_policy_assignment",
- "monitor_alert_delete_public_ip_address_rule",
- "monitor_alert_delete_security_solution",
- "monitor_alert_delete_sqlserver_fr",
- "monitor_diagnostic_settings_exists",
- "policy_ensure_asc_enforcement_enabled"
- ]
- },
- {
- "Id": "CEK-03",
- "Description": "Provide cryptographic protection to data at-rest and in-transit, using cryptographic libraries certified to approved standards.",
- "Name": "Data Encryption",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-03",
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6",
- "3.1",
- "3.11",
- "11.3",
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.1",
- "27001: A.18.1.2",
- "27001: A.18.1.3",
- "27001: A.18.1.4",
- "27001: A.18.1.5",
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.18",
- "27002: 18",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27001: A.14.1.3",
- "27002 14.1.3 c)",
- "27001 - A.10.1.1",
- "27017 - 10.1.1",
- "27001 - A.10.1.2",
- "27017 - 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.24",
- "27002: 8.24 Other Information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19",
- "AC-19(5)",
- "SC-8",
- "SC-8(1)",
- "SC-8(3)",
- "SC-8(4)",
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)-(3)",
- "SI-4",
- "SI-4(10)",
- "SI-7",
- "SI-7(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "Requirement 3",
- "2.2.3",
- "2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_minimum_tls_version_12",
- "databricks_workspace_cmk_encryption_enabled",
- "mysql_flexible_server_ssl_connection_enabled",
- "postgresql_flexible_server_enforce_ssl_enabled",
- "sqlserver_tde_encrypted_with_cmk",
- "sqlserver_tde_encryption_enabled",
- "storage_ensure_encryption_with_customer_managed_keys",
- "storage_infrastructure_encryption_is_enabled",
- "storage_secure_transfer_required_is_enabled",
- "storage_smb_channel_encryption_with_secure_algorithm",
- "vm_ensure_attached_disks_encrypted_with_cmk",
- "vm_ensure_unattached_disks_encrypted_with_cmk"
- ]
- },
- {
- "Id": "CEK-04",
- "Description": "Use encryption algorithms that are appropriate for data protection, considering the classification of data, associated risks, and usability of the encryption technology.",
- "Name": "Encryption Algorithm",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.2",
- "27002: 8.2",
- "27001: A.8.3",
- "27001: A.10.1.1",
- "27002: 10.1.1 (b)",
- "27001: A.10.1.2",
- "27002: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.24",
- "27001: A.5.12",
- "27001: A.5.13",
- "27002: 8.24 General (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A2",
- "Requirement 3",
- "2.3",
- "2.2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_minimum_tls_version_12",
- "keyvault_key_rotation_enabled",
- "mysql_flexible_server_minimum_tls_version_12",
- "postgresql_flexible_server_enforce_ssl_enabled",
- "sqlserver_recommended_minimal_tls_version",
- "storage_ensure_minimum_tls_version_12",
- "storage_smb_protocol_version_is_latest"
- ]
- },
- {
- "Id": "CEK-08",
- "Description": "CSPs must provide the capability for CSCs to manage their own data encryption keys.",
- "Name": "CSC Key Management Capability",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27017: 10.1",
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.23",
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-9",
- "CP-9(8)",
- "SA-9",
- "SA-9(6)",
- "SC-12",
- "SC-12(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.AM-6",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-05"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "databricks_workspace_cmk_encryption_enabled",
- "keyvault_access_only_through_private_endpoints",
- "keyvault_private_endpoints",
- "keyvault_rbac_enabled",
- "storage_ensure_encryption_with_customer_managed_keys"
- ]
- },
- {
- "Id": "CEK-10",
- "Description": "Generate Cryptographic keys using industry accepted cryptographic libraries specifying the algorithm strength and the random number generator used.",
- "Name": "Key Generation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "TS2.3",
- "SY1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27002: 10.1.1 (e)",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2",
- "27002: 10.1.2 (a)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24",
- "27002: 8.24 (d), Key management (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2.3",
- "3.6.1",
- "PCI Glossary - Cryptographic Key Generation"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.6.1.1",
- "3.7.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_rbac_enabled",
- "storage_ensure_encryption_with_customer_managed_keys"
- ]
- },
- {
- "Id": "CEK-12",
- "Description": "Rotate cryptographic keys in accordance with the calculated cryptoperiod, which includes provisions for considering the risk of information disclosure and legal and regulatory requirements.",
- "Name": "Key Rotation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2 e)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (e,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_key_expiration_set_in_non_rbac",
- "keyvault_key_rotation_enabled",
- "keyvault_non_rbac_secret_expiration_set",
- "keyvault_rbac_key_expiration_set",
- "keyvault_rbac_secret_expiration_set",
- "storage_key_rotation_90_days"
- ]
- },
- {
- "Id": "CEK-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.",
- "Name": "Key Destruction",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27017: 10.1.2",
- "27001: A.10.1.2",
- "27002: 10.1.2 (j)",
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (j,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.IP-6",
- "ID.GV-3",
- "PR.DS-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "ID.AM-08",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.6.4",
- "3.6.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_recoverable"
- ]
- },
- {
- "Id": "DCS-06",
- "Description": "Catalogue and track all relevant physical and logical assets located at all of the CSP's sites within a secured system.",
- "Name": "Assets Cataloguing and Tracking",
- "Attributes": [
- {
- "Section": "Datacenter Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DCS - 01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "1.1",
- "2.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27017: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-8",
- "CM-8(1)",
- "CM-8(2)",
- "CM-8(4)",
- "CM-8(7)",
- "CM-8(8)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4",
- "9.7.1",
- "9.9.1",
- "9.9.1.a",
- "9.9.1.b",
- "9.9.1.c",
- "12.3.3",
- "12.3.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1.1",
- "6.3.2",
- "9.4.2",
- "9.4.3",
- "12.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_mcas_is_enabled",
- "monitor_diagnostic_settings_exists",
- "policy_ensure_asc_enforcement_enabled"
- ]
- },
- {
- "Id": "DSP-02",
- "Description": "Apply industry accepted methods for the secure disposal of data from storage media such that data is not recoverable by any forensic means.",
- "Name": "Secure Disposal",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3",
- "CC6.4",
- "CC6.5",
- "CC6.7",
- "P4.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-07"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.3",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.3.2",
- "27002: 8.3.2",
- "27001: A.11.2.7",
- "27002: 11.2.7"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.7.10",
- "27001: A.7.14",
- "27001: A.8.10",
- "27002: 7.10 (Secure reuse or disposal)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-22",
- "SI-12",
- "SI-12(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-10",
- "PR.PS-02",
- "PR.PS-03",
- "ID.AM-08"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1",
- "9.8",
- "9.8.1",
- "9.8.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "3.7.5",
- "9.4.7"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "storage_ensure_file_shares_soft_delete_is_enabled",
- "storage_ensure_soft_delete_is_enabled",
- "vm_sufficient_daily_backup_retention_period"
- ]
- },
- {
- "Id": "DSP-03",
- "Description": "Create and maintain a data inventory, at least for any sensitive data and personal data.",
- "Name": "Data Inventory",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2",
- "1.3.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-12",
- "CM-12(1)",
- "PM-5",
- "PM-5(1)",
- "SI-12",
- "SI-12(1)",
- "SI-19",
- "SI-19(1)",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "9.4.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_storage_is_on",
- "defender_ensure_mcas_is_enabled",
- "monitor_diagnostic_settings_exists",
- "policy_ensure_asc_enforcement_enabled"
- ]
- },
- {
- "Id": "DSP-04",
- "Description": "Classify data according to its type and sensitivity level.",
- "Name": "Data Classification",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "C1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.2.1",
- "27002: 8.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-16",
- "AC-16(9)",
- "PM-22",
- "PM-23",
- "PT-2",
- "PT-2(1)",
- "SI-18",
- "SI-18(2)",
- "SI-19",
- "SI-19(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-05",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "9.4.2",
- "9.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_storage_is_on"
- ]
- },
- {
- "Id": "DSP-07",
- "Description": "Develop systems, products, and business practices based upon a principle of security by design and industry best practices.",
- "Name": "Data Protection by Design and Default",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "PI1.2",
- "PI1.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.1",
- "5.3.2",
- "5.3.3",
- "5.3.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.2",
- "IM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002:14.1.1",
- "27001: A.14.2.5",
- "27002:14.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.27",
- "27001: A.8.28",
- "27001: A.8.29",
- "27002: 5.8 (Information security requirements a-i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-17",
- "PM-24",
- "PM-25",
- "PT-2",
- "PT-2(2)",
- "SA-3",
- "SA-4",
- "SA-5",
- "SA-8",
- "SA-8(9)",
- "SA-8(13)",
- "SA-8(18)",
- "SA-8(20)",
- "SA-8(22)",
- "SA-8(23)",
- "SA-8(33)",
- "SA-15",
- "SA-15(12)",
- "SC-3",
- "SC-3(3)",
- "SC-7",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(4)",
- "SC-28",
- "SC-28(1)",
- "SI-12",
- "SI-12(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "aisearch_service_not_publicly_accessible",
- "aks_clusters_public_access_disabled",
- "containerregistry_not_publicly_accessible",
- "cosmosdb_account_firewall_use_selected_networks",
- "sqlserver_unrestricted_inbound_access",
- "storage_blob_public_access_level_is_disabled",
- "storage_default_network_access_rule_is_denied",
- "storage_ensure_private_endpoints_in_storage_accounts",
- "vm_ensure_attached_disks_encrypted_with_cmk",
- "vm_ensure_unattached_disks_encrypted_with_cmk"
- ]
- },
- {
- "Id": "DSP-10",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope as permitted by the respective laws and regulations.",
- "Name": "Sensitive Data Transfer",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.12",
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "9.5.1",
- "9.5.2",
- "9.5.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.8.3.3",
- "27002: 8.3.3",
- "27001: A.13.2.3",
- "27002: 13.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.7.10"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-4",
- "AC-4(23)-(25)",
- "CA-3",
- "CA-3(6)",
- "CA-6",
- "CA-6(1)",
- "CA-6(2)",
- "SC-4",
- "SC-4(2)",
- "SC-7",
- "SC-7(10)",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-16",
- "SC-16(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.DS-5",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.IR-01",
- "ID.AM-03",
- "GV.OC-03",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "4.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.1.1",
- "4.2.1",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_ensure_http_is_redirected_to_https",
- "app_ensure_using_http20",
- "sqlserver_recommended_minimal_tls_version",
- "storage_ensure_minimum_tls_version_12",
- "storage_secure_transfer_required_is_enabled"
- ]
- },
- {
- "Id": "DSP-16",
- "Description": "Data retention, archiving and deletion is managed in accordance with business requirements, applicable laws and regulations.",
- "Name": "Data Retention and Deletion",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "C1.1",
- "C1.2",
- "CC3.1",
- "P4.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.4",
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.10",
- "27002: 5.33 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-12",
- "SI-12(1)-(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)",
- "SI-19",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-3",
- "PR.IP-6",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "GV.OC-03",
- "GV.SC-10",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "monitor_storage_account_with_activity_logs_cmk_encrypted",
- "monitor_storage_account_with_activity_logs_is_private",
- "postgresql_flexible_server_log_retention_days_greater_3",
- "sqlserver_auditing_retention_90_days",
- "storage_ensure_file_shares_soft_delete_is_enabled",
- "storage_ensure_soft_delete_is_enabled"
- ]
- },
- {
- "Id": "DSP-17",
- "Description": "Define and implement, processes, procedures and technical measures to protect sensitive data throughout it's lifecycle.",
- "Name": "Sensitive Data Protection",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSC-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.1",
- "CC6.1",
- "CC6.3",
- "CC6.7",
- "CC8.1",
- "C1.1",
- "P2.0",
- "P3.0",
- "P4.0",
- "P5.0",
- "P6.0"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.1",
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.3",
- "9.1.1",
- "9.2.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001:A.18.1.4",
- "27002:18.1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.11",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PM-22",
- "PM-24",
- "PT-7",
- "PT-7(1)",
- "PT-7(2)",
- "PT-8",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.0 (including all subsections)",
- "4.0 (including all subsections)"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.1.1",
- "4.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "containerregistry_not_publicly_accessible",
- "cosmosdb_account_firewall_use_selected_networks",
- "defender_ensure_defender_for_storage_is_on",
- "sqlserver_tde_encrypted_with_cmk",
- "sqlserver_tde_encryption_enabled",
- "sqlserver_unrestricted_inbound_access",
- "storage_account_key_access_disabled",
- "storage_blob_public_access_level_is_disabled",
- "storage_cross_tenant_replication_disabled",
- "storage_default_network_access_rule_is_denied",
- "storage_default_to_entra_authorization_enabled",
- "storage_ensure_encryption_with_customer_managed_keys",
- "vm_ensure_attached_disks_encrypted_with_cmk"
- ]
- },
- {
- "Id": "GRC-05",
- "Description": "Develop and implement an Information Security Program, which includes programs for all the relevant domains of the CCM.",
- "Name": "Information Security Program",
- "Attributes": [
- {
- "Section": "Governance, Risk and Compliance",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "14.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SG2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-1",
- "PM-3",
- "PM-14",
- "PL-2",
- "PM-18",
- "PM-31"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.4.1",
- "A.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.4.1",
- "A3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_arm_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_databases_is_on",
- "defender_ensure_defender_for_dns_is_on",
- "defender_ensure_defender_for_keyvault_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_mcas_is_enabled",
- "defender_ensure_wdatp_is_enabled"
- ]
- },
- {
- "Id": "IAM-02",
- "Description": "Establish, document, approve, communicate, implement, apply, evaluate and maintain strong password policies and procedures. Review and update the policies and procedures at least annually.",
- "Name": "Strong Password Policy and Procedures",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-12",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "4.1.2",
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1",
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.7.2.2",
- "27002: 7.2.2",
- "27001: A.9.2.6",
- "27002: 9.2.6",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.17",
- "27001: A.6.3",
- "27001: A.8.5",
- "27001: A.5.37"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-3",
- "AC-3(3)",
- "AC-12",
- "AC-12(1)",
- "IA-2",
- "IA-2(10)",
- "IA-5",
- "IA-5(1)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.AC-1",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.4",
- "12.1",
- "12.1.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.1.1",
- "8.3.8"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_privileged_user_has_mfa",
- "entra_security_defaults_enabled"
- ]
- },
- {
- "Id": "IAM-03",
- "Description": "Manage, store, and review the information of system identities, and level of access.",
- "Name": "Identity Inventory",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-04",
- "IAM-08",
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27001: A.9.4.1",
- "27002: 9.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.5.15",
- "27001: A.5.16",
- "27001: A.5.18",
- "27001: A.7.4",
- "27001: A.8.15",
- "27001: A.8.2",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "AU-16",
- "AU-16(1)",
- "IA-4",
- "IA-4(8)",
- "IA-4(9)",
- "IA-5",
- "IA-5(5)",
- "IA-8",
- "IA-8(4)",
- "PM-5(1)",
- "SA-8",
- "SA-8(22)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-04",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4.a"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_global_admin_in_less_than_five_users"
- ]
- },
- {
- "Id": "IAM-04",
- "Description": "Employ the separation of duties principle when implementing information system access.",
- "Name": "Separation of Duties",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC1.3",
- "CC5.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.2",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.6.1.2",
- "27002: 6.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18",
- "27001: A.5.3",
- "27001: A.8.2"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-6",
- "AC-6(1)-(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4",
- "6.4.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_policy_default_users_cannot_create_security_groups",
- "entra_policy_ensure_default_user_cannot_create_apps",
- "iam_role_user_access_admin_restricted",
- "iam_subscription_roles_owner_custom_not_created"
- ]
- },
- {
- "Id": "IAM-05",
- "Description": "Employ the least privilege principle when implementing information system access.",
- "Name": "Least Privilege",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-06",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.1",
- "27002: 9.1.1",
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.8.2",
- "27002: 5.15 (Other information 2nd (a))"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "IA-12",
- "IA-12(2)",
- "IA-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1",
- "7.1.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2",
- "7.2.5",
- "7.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_function_identity_without_admin_privileges",
- "entra_policy_ensure_default_user_cannot_create_apps",
- "entra_policy_ensure_default_user_cannot_create_tenants",
- "entra_policy_restricts_user_consent_for_apps",
- "iam_custom_role_has_permissions_to_administer_resource_locks",
- "iam_subscription_roles_owner_custom_not_created"
- ]
- },
- {
- "Id": "IAM-07",
- "Description": "De-provision or respectively modify access of movers / leavers or system identity changes in a timely manner in order to effectively adopt and communicate identity and access management policies.",
- "Name": "User Access Changes and Revocation",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.3",
- "6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(1)",
- "AC-2(2)",
- "AC-2(6)",
- "AC-2(8)",
- "AC-3",
- "AC-3(8)",
- "AC-6",
- "AC-6(7)",
- "AU-10",
- "AU-10(4)",
- "AU-16",
- "AU-16(1)",
- "CM-7",
- "CM-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.IP-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-04",
- "GV.SC-10",
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.5",
- "8.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_global_admin_in_less_than_five_users"
- ]
- },
- {
- "Id": "IAM-08",
- "Description": "Review and revalidate user access for least privilege and separation of duties with a frequency that is commensurate with organizational risk tolerance.",
- "Name": "User Access Review",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27001: A.9.2.6",
- "27001: A.9.4.1",
- "27017: 9.4.1",
- "27001: A.6.1.2",
- "27001: A 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.3",
- "27001: A.5.18",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "AC-6(8)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5.1",
- "7.2.5",
- "7.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_global_admin_in_less_than_five_users",
- "keyvault_non_rbac_secret_expiration_set",
- "keyvault_rbac_secret_expiration_set",
- "storage_key_rotation_90_days"
- ]
- },
- {
- "Id": "IAM-09",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the segregation of privileged access roles such that administrative access to data, encryption and key management capabilities and logging capabilities are distinct and separated.",
- "Name": "Segregation of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.1",
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-3(7)",
- "AC-6(4)",
- "AC-6(8)",
- "IA-5",
- "IA-5(6)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.3",
- "3.5.2",
- "7.1.2",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.7.6",
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_global_admin_in_less_than_five_users",
- "entra_policy_guest_invite_only_for_admin_roles",
- "entra_policy_guest_users_access_restrictions",
- "iam_custom_role_has_permissions_to_administer_resource_locks",
- "iam_subscription_roles_owner_custom_not_created"
- ]
- },
- {
- "Id": "IAM-10",
- "Description": "Define and implement an access process to ensure privileged access roles and rights are granted for a time limited period, and implement procedures to prevent the culmination of segregated privileged access.",
- "Name": "Management of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "6.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3",
- "27001: A.9.4.4",
- "27002: 9.4.4",
- "27017: 9.4.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(7)",
- "AC-3",
- "AC-3(4)",
- "AC-3(11)",
- "AC-3(13)",
- "AC-3(14)",
- "AC-6",
- "AC-6(4)",
- "AC-6(5)",
- "AC-6(8)",
- "AC-12",
- "AC-12(3)",
- "AC-17",
- "AC-17(4)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_conditional_access_policy_require_mfa_for_management_api",
- "entra_global_admin_in_less_than_five_users",
- "entra_user_with_vm_access_has_mfa",
- "iam_role_user_access_admin_restricted",
- "iam_subscription_roles_owner_custom_not_created",
- "vm_jit_access_enabled"
- ]
- },
- {
- "Id": "IAM-12",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the logging infrastructure is read-only for all with write access, including privileged access roles, and that the ability to disable it is controlled through a procedure that ensures the segregation of duties and break glass procedures.",
- "Name": "Safeguard Logs Integrity",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.3"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1",
- "27018: 12.4.1",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27017: 12.4.2",
- "27018: 12.4.2",
- "27001: A.12.4.3",
- "27002: 12.4.3",
- "27017: 12.4.3",
- "27018: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.18",
- "27002: 8.15 Protection of Logs"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(11)",
- "AC-2(12)",
- "IA-8",
- "IA-8(4)",
- "SA-8",
- "SA-8(22)",
- "SC-34",
- "SC-34(1)",
- "SC-34(2)",
- "SC-36",
- "SI-4",
- "SI-4(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_trusted_named_locations_exists",
- "keyvault_logging_enabled",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_storage_account_with_activity_logs_is_private"
- ]
- },
- {
- "Id": "IAM-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure users are identifiable through unique IDs or which can associate individuals to the usage of user IDs.",
- "Name": "Uniquely Identifiable Users",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.1",
- "27002: 9.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(14)",
- "AC-24",
- "AC-24(2)",
- "AU-10",
- "AU-10(1)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-4",
- "IA-4(1)",
- "SA-8",
- "SA-8(22)",
- "SC-23",
- "SC-23(3)",
- "SC-40(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1",
- "8.2",
- "8.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.1",
- "8.2.2",
- "8.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_conditional_access_policy_require_mfa_for_management_api",
- "entra_non_privileged_user_has_mfa",
- "entra_privileged_user_has_mfa",
- "entra_security_defaults_enabled",
- "postgresql_flexible_server_entra_id_authentication_enabled",
- "sqlserver_azuread_administrator_enabled"
- ]
- },
- {
- "Id": "IAM-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for authenticating access to systems, application and data assets, including multifactor authentication for at least privileged user and sensitive data access. Adopt digital certificates or alternatives which achieve an equivalent level of security for system identities.",
- "Name": "Strong Authentication",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.3",
- "6.5",
- "12.5",
- "12.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4",
- "SA1.8"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27017: 9.1.2",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.9.4.2",
- "27002: 9.4.2",
- "27017: 9.4.2",
- "27018: 9.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.17",
- "27001: A.8.5",
- "27001: A.8.24",
- "27002: 8.5",
- "27002: 8.24 other information (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(5)",
- "AC-7",
- "AC-7(4)",
- "AU-10",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(8)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5",
- "IA-5(2)",
- "IA-5(7)",
- "IA-5(9)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-5(14)-(16)",
- "IA-8",
- "IA-8(1)",
- "IA-8(6)",
- "SC-23",
- "SC-23(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3",
- "8.1.6",
- "8.2",
- "8.3",
- "8.3.2",
- "12.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "8.3.1",
- "8.3.2",
- "8.4.1",
- "8.4.2",
- "8.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_non_privileged_user_has_mfa",
- "entra_privileged_user_has_mfa",
- "entra_security_defaults_enabled",
- "entra_user_with_vm_access_has_mfa"
- ]
- },
- {
- "Id": "IAM-15",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the secure management of passwords.",
- "Name": "Passwords Management",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27018: 9.2.4",
- "27001: A.9.3.1",
- "27002: 9.3.1",
- "27017: 9.3.1",
- "27018: 9.3.1",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.17"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IA-4",
- "IA-4(8)",
- "IA-5",
- "IA-5(1)",
- "IA-5(8)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.2",
- "8.2.1-6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.2",
- "2.3.1",
- "8.3.5",
- "8.3.6",
- "8.3.7",
- "8.3.8",
- "8.3.9",
- "8.3.10",
- "8.3.10.1",
- "8.6.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "entra_privileged_user_has_mfa",
- "entra_security_defaults_enabled"
- ]
- },
- {
- "Id": "IAM-16",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to verify access to data and system functions is authorized.",
- "Name": "Authorization Mechanisms",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27002: 9.2.5",
- "27017: 9.2.5",
- "27018: 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(5)",
- "AC-4",
- "AC-4(17)",
- "AC-4(21)",
- "AC-4(22)",
- "AC-6",
- "AC-6(8)",
- "AC-6(9)",
- "AC-12",
- "AC-12(1)",
- "AC-20",
- "AC-20(1)",
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5(1)",
- "IA-5(2)",
- "IA-5(5)",
- "IA-5(8)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-8",
- "IA-8(1)",
- "IA-8(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.AC-6",
- "PR.AC-7",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03",
- "PR.AA-04",
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.3",
- "7.1.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.4",
- "7.2.3",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "aks_cluster_rbac_enabled",
- "app_function_identity_is_configured",
- "app_function_identity_without_admin_privileges",
- "app_function_not_publicly_accessible",
- "entra_policy_user_consent_for_verified_apps",
- "iam_subscription_roles_owner_custom_not_created"
- ]
- },
- {
- "Id": "IPY-03",
- "Description": "Implement cryptographically secure and standardized network protocols for the management, import and export of data.",
- "Name": "Secure Interoperability and Portability Management",
- "Attributes": [
- {
- "Section": "Interoperability & Portability",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IPY-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.2",
- "NC1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1",
- "27001: A.15.1.1",
- "27002: 15.1.1",
- "27017: 15.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.19",
- "27001: A.5.23",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PT-2",
- "PT-2(2)",
- "SA-4",
- "SC-16",
- "SC-16(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.1",
- "1.2.5",
- "1.2.6",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "storage_ensure_azure_services_are_trusted_to_access_is_enabled",
- "storage_secure_transfer_required_is_enabled"
- ]
- },
- {
- "Id": "IVS-02",
- "Description": "Plan and monitor the availability, quality, and adequate capacity of resources in order to deliver the required system performance as determined by the business.",
- "Name": "Capacity and Resource Planning",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-04"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.3",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.12.1.3",
- "27002: 12.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.3 (b)",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.8.6",
- "27001: A.8.14"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "SC-5",
- "SC-5(2)",
- "SC-4",
- "SI-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-04",
- "GV.OC-04"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "vm_scaleset_associated_with_load_balancer",
- "vm_scaleset_not_empty"
- ]
- },
- {
- "Id": "IVS-03",
- "Description": "Monitor, encrypt and restrict communications between environments to only authenticated and authorized connections, as justified by the business. Review these configurations at least annually, and support them by a documented justification of all allowed services, protocols, ports, and compensating controls.",
- "Name": "Network Security",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-06"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.8",
- "3.1",
- "12.2",
- "13.6",
- "13.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: A.5.15 2nd c)",
- "27002: 8.20",
- "27002: 8.21",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-1",
- "SC-4",
- "SC-7",
- "SC-7(4)",
- "SC-7(5)",
- "SC-7(8)",
- "SC-7(9)",
- "SC-7(11)",
- "SC-8",
- "SC-8(1)",
- "SC-11",
- "SC-12",
- "SC-16",
- "SC-23",
- "SC-29",
- "SC-29(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-5",
- "PR.AC-7",
- "PR.PT-4",
- "DE.CM-1",
- "DE.CM-7",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-01",
- "PR.AA-03",
- "PR.AA-05",
- "DE.CM-01",
- "PR.DS-02",
- "ID.AM-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "1.1.6",
- "1.2",
- "1.2.3",
- "2.2",
- "4.1.1",
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.5",
- "1.2.6",
- "1.2.7",
- "1.4.2",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1",
- "10.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "aks_clusters_created_with_private_nodes",
- "aks_clusters_public_access_disabled",
- "aks_network_policy_enabled",
- "network_bastion_host_exists",
- "network_flow_log_captured_sent",
- "network_flow_log_more_than_90_days",
- "network_http_internet_access_restricted",
- "network_rdp_internet_access_restricted",
- "network_ssh_internet_access_restricted",
- "network_udp_internet_access_restricted",
- "network_watcher_enabled"
- ]
- },
- {
- "Id": "IVS-04",
- "Description": "Harden host and guest OS, hypervisor or infrastructure control plane according to their respective best practices, and supported by technical controls, as part of a security baseline.",
- "Name": "OS Hardening and Base Controls",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.8",
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-07",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "4.1",
- "4.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.3",
- "SY1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.14.2.2",
- "27002: 14.2.2",
- "27001: A.14.2.3",
- "27001 A.14.2.4",
- "27018: 12.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: 8.20",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(1)",
- "SC-29",
- "SC-29(1)",
- "SC-2",
- "SC-7",
- "SC-7(12)",
- "SC-30",
- "SC-34",
- "SC-35",
- "SC-39",
- "SC-44"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-1",
- "PR.PT-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_assessments_vm_endpoint_protection_installed",
- "defender_ensure_system_updates_are_applied",
- "vm_ensure_using_managed_disks",
- "vm_linux_enforce_ssh_authentication",
- "vm_trusted_launch_enabled"
- ]
- },
- {
- "Id": "IVS-06",
- "Description": "Design, develop, deploy and configure applications and infrastructures such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented and segregated, monitored and restricted from other tenants.",
- "Name": "Segmentation and Segregation",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-09"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.3.4",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.20",
- "27001: A.8.3",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.22",
- "27002: 5.15 (b)",
- "27002: 8.3 (b)",
- "27002: 8.16 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-3",
- "SC-7",
- "SC-7(20)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.AC-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.6",
- "8.3.1",
- "10.8",
- "11.3",
- "A3.2.1",
- "A3.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A1.1.1",
- "A1.1.2",
- "A1.1.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_function_not_publicly_accessible",
- "app_function_vnet_integration_enabled",
- "containerregistry_uses_private_link",
- "cosmosdb_account_use_private_endpoints",
- "databricks_workspace_vnet_injection_enabled",
- "network_http_internet_access_restricted",
- "storage_ensure_private_endpoints_in_storage_accounts"
- ]
- },
- {
- "Id": "IVS-07",
- "Description": "Use secure and encrypted communication channels when migrating servers, services, applications, or data to cloud environments. Such channels must include only up-to-date and approved protocols.",
- "Name": "Migration to Cloud Environments",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-10"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM1.4",
- "NC1.4",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27017: 13.1.1",
- "27018: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27017: 13.1.2",
- "27018: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3",
- "27018: 13.1.3",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27017: 13.2.1",
- "27018: 13.2.1",
- "27001: A.13.2.2",
- "27002: 13.2.2",
- "27017: 13.2.2",
- "27018: 13.2.2",
- "27001: A.13.2.3",
- "27002: 13.2.3",
- "27017: 13.2.3",
- "27018: 13.2.3",
- "27001: A.13.2.4",
- "27002: 13.2.4",
- "27017: 13.2.4",
- "27018: 13.2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.20",
- "27001: A.8.24",
- "27002: 8.20 (e)",
- "27002: 8.24 Guidance (b,f), other information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-17",
- "AC-20",
- "SC-7",
- "SC-7(28)",
- "SC-8",
- "SC-8(1)",
- "SC-12",
- "SC-23",
- "SC-29",
- "SI-7",
- "SI-7(1)-(3)",
- "SI-7(5)-(10)",
- "SI-7(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "mysql_flexible_server_ssl_connection_enabled",
- "postgresql_flexible_server_enforce_ssl_enabled"
- ]
- },
- {
- "Id": "IVS-09",
- "Description": "Define, implement and evaluate processes, procedures and defense-in-depth techniques for protection, detection, and timely response to network-based attacks.",
- "Name": "Network Defense",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.6",
- "CC6.8",
- "CC7.1",
- "CC7.2",
- "CC7.5"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-13"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "13.3",
- "13.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3",
- "5.2.4",
- "5.2.5",
- "5.2.7",
- "5.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.11.1.4",
- "27002: 11.1.4",
- "27017: 11.1.4",
- "27018: 16.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.5.24",
- "27001: A.5.26",
- "27001: A.8.8",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.26",
- "27002: 8.8 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-8",
- "PL-8(1)",
- "SC-5",
- "SC-5(1)",
- "SC-5(3)",
- "SC-7",
- "SC-7(13)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.DP-1",
- "DE.CM-1",
- "DE.CM-7",
- "PR.AC-5",
- "RS.MI-2",
- "PR.DS-2",
- "RS.RP-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "DE.CM-01",
- "PR.IR-01",
- "RS.MA-01",
- "RS.MI-01",
- "RS.MI-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.6",
- "1.1",
- "1.2",
- "1.3",
- "1.5",
- "12.10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.1.1",
- "1.3.1",
- "1.3.2",
- "1.3.3",
- "1.4.1",
- "1.4.2",
- "1.4.3",
- "1.4.4",
- "1.4.5",
- "1.5.1",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_arm_is_on",
- "defender_ensure_defender_for_dns_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_iot_hub_defender_is_on",
- "defender_ensure_wdatp_is_enabled",
- "network_flow_log_captured_sent",
- "network_watcher_enabled",
- "sqlserver_microsoft_defender_enabled",
- "vm_jit_access_enabled"
- ]
- },
- {
- "Id": "LOG-02",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the security and retention of audit logs.",
- "Name": "Audit Logs Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1",
- "8.9",
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.3",
- "5.1.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-4",
- "AU-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-08",
- "PR.DS-11",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.7"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4",
- "10.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_logging_enabled",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_storage_account_with_activity_logs_cmk_encrypted",
- "monitor_storage_account_with_activity_logs_is_private",
- "storage_ensure_encryption_with_customer_managed_keys",
- "storage_ensure_soft_delete_is_enabled"
- ]
- },
- {
- "Id": "LOG-03",
- "Description": "Identify and monitor security-related events within applications and the underlying infrastructure. Define and implement a system to generate alerts to responsible stakeholders based on such events and corresponding metrics.",
- "Name": "Security Monitoring and Alerting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03",
- "SEF-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "5.2.7",
- "1.6.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2",
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-3",
- "DE.AE-5",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-4",
- "DE.CM-5",
- "DE.CM-6",
- "DE.CM-7",
- "DE.DP-1",
- "DE.DP-4",
- "DE.AE-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2",
- "10.4.1.1",
- "10.4.2.1",
- "10.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_attack_path_notifications_properly_configured",
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_notify_alerts_severity_is_high",
- "defender_ensure_notify_emails_to_owners",
- "defender_ensure_wdatp_is_enabled",
- "monitor_alert_create_update_security_solution",
- "monitor_alert_service_health_exists"
- ]
- },
- {
- "Id": "LOG-04",
- "Description": "Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.",
- "Name": "Audit Logs Access and Accountability",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.1",
- "4.1.2",
- "4.1.3",
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27001: A.12.4.1",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(4)",
- "AU-9(6)",
- "AU-10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.1",
- "10.2.1",
- "10.2.3",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1.3",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "monitor_storage_account_with_activity_logs_is_private"
- ]
- },
- {
- "Id": "LOG-05",
- "Description": "Monitor security audit logs to detect activity outside of typical or expected patterns. Establish and follow a defined process to review and take appropriate and timely actions on detected anomalies.",
- "Name": "Audit Logs Monitoring and Response",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.8",
- "8.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "1.6.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.3",
- "27002: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-6",
- "AU-6(1)",
- "AU-6(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-3",
- "PR.PT-1",
- "RS.AN-1",
- "RS.CO-1.",
- "DE.AE-1",
- "DE.AE-5",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6",
- "10.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.1.1",
- "10.4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "monitor_alert_create_policy_assignment",
- "monitor_alert_create_update_nsg",
- "monitor_alert_create_update_public_ip_address_rule",
- "monitor_alert_create_update_security_solution",
- "monitor_alert_create_update_sqlserver_fr",
- "monitor_alert_delete_nsg",
- "monitor_alert_delete_policy_assignment",
- "monitor_alert_delete_public_ip_address_rule",
- "monitor_alert_delete_security_solution",
- "monitor_alert_delete_sqlserver_fr",
- "monitor_alert_service_health_exists"
- ]
- },
- {
- "Id": "LOG-07",
- "Description": "Establish, document and implement which information meta/data system events should be logged. Review and update the scope at least annually or whenever there is a change in the threat environment.",
- "Name": "Logging Scope",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-14",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.SC-4",
- "PR.PT-1",
- "ID.GV-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_function_application_insights_enabled",
- "appinsights_ensure_is_configured",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_diagnostic_settings_exists",
- "network_flow_log_captured_sent",
- "network_flow_log_more_than_90_days"
- ]
- },
- {
- "Id": "LOG-08",
- "Description": "Generate audit records containing relevant security information.",
- "Name": "Log Records",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-3",
- "AU-3(1)",
- "AU-3(3)",
- "AU-6",
- "AU-6(8)",
- "AU-12",
- "AU-12(1)",
- "AU-12(2)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-6",
- "DE.CM-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_function_application_insights_enabled",
- "app_http_logs_enabled",
- "appinsights_ensure_is_configured",
- "keyvault_logging_enabled",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_diagnostic_settings_exists",
- "mysql_flexible_server_audit_log_connection_activated",
- "mysql_flexible_server_audit_log_enabled",
- "network_flow_log_captured_sent",
- "network_flow_log_more_than_90_days",
- "postgresql_flexible_server_log_checkpoints_on",
- "postgresql_flexible_server_log_connections_on",
- "postgresql_flexible_server_log_disconnections_on",
- "postgresql_flexible_server_log_retention_days_greater_3",
- "sqlserver_auditing_enabled",
- "sqlserver_auditing_retention_90_days"
- ]
- },
- {
- "Id": "LOG-09",
- "Description": "The information system protects audit records from unauthorized access, modification, and deletion.",
- "Name": "Log Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04",
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(2)",
- "AU-9(3)",
- "AU-9(4)",
- "AU-12(3)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_logging_enabled",
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_storage_account_with_activity_logs_cmk_encrypted",
- "monitor_storage_account_with_activity_logs_is_private",
- "storage_ensure_encryption_with_customer_managed_keys"
- ]
- },
- {
- "Id": "LOG-10",
- "Description": "Establish and maintain a monitoring and internal reporting capability over the operations of cryptographic, encryption and key management policies, processes, procedures, and controls.",
- "Name": "Encryption Monitoring and Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.1.1",
- "10.2.1",
- "10.4.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "keyvault_key_expiration_set_in_non_rbac",
- "keyvault_key_rotation_enabled",
- "keyvault_rbac_key_expiration_set"
- ]
- },
- {
- "Id": "LOG-11",
- "Description": "Log and monitor key lifecycle management events to enable auditing and reporting on usage of cryptographic keys.",
- "Name": "Transaction/Activity Logging",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "monitor_diagnostic_setting_with_appropriate_categories",
- "monitor_diagnostic_settings_exists"
- ]
- },
- {
- "Id": "LOG-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the reporting of anomalies and failures of the monitoring system and provide immediate notification to the accountable party.",
- "Name": "Failures and Anomalies Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.16.1.2",
- "27017: 16.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.24",
- "27001: A.6.8",
- "27002: 6.8 (g)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-6",
- "AU-6(3)",
- "AU-6(4)",
- "AU-6(5)",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-3",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.3",
- "10.7.1",
- "10.7.2",
- "10.7.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_container_images_resolved_vulnerabilities",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_notify_alerts_severity_is_high",
- "defender_ensure_notify_emails_to_owners",
- "defender_ensure_wdatp_is_enabled",
- "monitor_alert_service_health_exists"
- ]
- },
- {
- "Id": "SEF-03",
- "Description": "'Establish, document, approve, communicate, apply, evaluate and maintain a security incident response plan, which includes but is not limited to: relevant internal departments, impacted CSCs, and other business critical relationships (such as supply-chain) that may be impacted.'",
- "Name": "Incident Response Plans",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2",
- "CC7.3",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2",
- "17.4"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27017: CLD.12.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.5.26",
- "27002: 5.26 (e,f)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-1",
- "IR-2",
- "IR-2(1)-(3)",
- "IR-3",
- "IR-3(1)-(3)",
- "IR-4",
- "IR-4(1)-(15)",
- "IR-5",
- "IR-5(1)",
- "IR-6",
- "IR-6(1)-(3)",
- "IR-7",
- "IR-7(1)",
- "IR-7(2)",
- "IR-8",
- "IR-8(1)",
- "IR-9",
- "IR-9(1)-(4)",
- "PM-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.CO-1",
- "RS.CO-4",
- "ID.AM-6",
- "ID.GV-2",
- "ID.SC-5",
- "PR.IP-9",
- "PR.IP10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AT-01",
- "PR.AT-02",
- "RS.MA-01",
- "GV.SC-08",
- "ID.IM-02",
- "ID.IM-04",
- "RC.RP-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "12.10.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_attack_path_notifications_properly_configured",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_notify_alerts_severity_is_high"
- ]
- },
- {
- "Id": "SEF-06",
- "Description": "Define, implement and evaluate processes, procedures and technical measures supporting business processes to triage security-related events.",
- "Name": "Event Triage Processes",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.4",
- "27002: 16.1.4",
- "27017: 16.1.4",
- "27018: 16.1.4",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.25"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(3)",
- "CA-7(4)",
- "CA-7(5)",
- "CA-7(6)",
- "IR-4",
- "IR-4(1)",
- "IR-4(3)",
- "IR-4(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-4",
- "RS.RP-1",
- "RS.AN-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "RS.MA-02",
- "RS.MA-03",
- "RS.AN-03",
- "DE.AE-02",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "RS.MI-02",
- "RC.RP-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_app_services_is_on",
- "defender_ensure_defender_for_azure_sql_databases_is_on",
- "defender_ensure_defender_for_databases_is_on",
- "defender_ensure_defender_for_keyvault_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_mcas_is_enabled",
- "defender_ensure_wdatp_is_enabled"
- ]
- },
- {
- "Id": "SEF-08",
- "Description": "Maintain points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities.",
- "Name": "Points of Contact Maintenance",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.2",
- "27001: A.6.1.3",
- "27002: 6.1.3",
- "27017: 6.1.3",
- "27018: 6.1.3",
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.18.1.1",
- "27002: 18.1.1",
- "27017: 18.1.1",
- "27018: 18.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.5",
- "27001: A.5.24",
- "27002: 5.24 Incident management procedure (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-4",
- "IR-4(8)",
- "IR-6",
- "IR-6(3)",
- "IR-7",
- "IR-7(2)",
- "PM-21",
- "PM-23",
- "PM-26"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-2",
- "RS.CO-3",
- "RS.CO-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-02",
- "RS.CO-02",
- "RS.CO-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_additional_email_configured_with_a_security_contact",
- "defender_ensure_notify_emails_to_owners"
- ]
- },
- {
- "Id": "TVM-02",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually.",
- "Name": "Malware Protection Policy and Procedures",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.8"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-01",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "9.7",
- "10.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.2",
- "TS1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.12.2.1",
- "27001: A.6.2.1",
- "27002: 6.2.1 (h)",
- "27001: A.6.2.2",
- "27002: 6.2.2 (j)",
- "27001: A.7.2.2",
- "27002: 7.2.2 (d)",
- "27001: A.10.1.1",
- "27002: 10.1.1 (g)",
- "27001: A.13.2.1",
- "27002: 13.2.1 (b)",
- "27001: A.15.1.2",
- "27017: 15.1.2",
- "27001: A.12.2.1",
- "27002: 12.2.1 (a),(d)",
- "27017: CLD.9.5.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.7",
- "27001: A.5.37",
- "27001: A.8.7",
- "27002: 5.7 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-3",
- "RA-3(3)",
- "RA-5",
- "RA-5(3)",
- "RA-5(5)",
- "SI-3",
- "SI-3(4)",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "DE.CM-4",
- "DE.CM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "DE.CM-01",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.4",
- "12.1",
- "12.1.1",
- "12.3.1",
- "12.5.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.1.1",
- "12.1.2",
- "5.1.1",
- "5.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_assessments_vm_endpoint_protection_installed",
- "defender_auto_provisioning_log_analytics_agent_vms_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_wdatp_is_enabled"
- ]
- },
- {
- "Id": "TVM-03",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to enable both scheduled and emergency responses to vulnerability identifications, based on the identified risk.",
- "Name": "Vulnerability Remediation Schedule",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC7.1",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.2",
- "7.7",
- "17.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "TM2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.2.1",
- "27001: A.12.6.1",
- "27002: 12.6.1(c)(d)(j)",
- "27018: 12.6.1(k)(i)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.8.7",
- "27001: A.8.8",
- "27001: A.8.32",
- "27002: 8.7",
- "27002: 8.8",
- "27002: 8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-31",
- "RA-3",
- "RA-3(1)",
- "RA-5",
- "RA-5(2)-(4)",
- "RA-5(6)",
- "SI-3",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.AN-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.1.a",
- "6.1.b"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.1.1",
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "app_ensure_java_version_is_latest",
- "app_ensure_php_version_is_latest",
- "app_ensure_python_version_is_latest",
- "app_function_latest_runtime_version",
- "defender_ensure_system_updates_are_applied"
- ]
- },
- {
- "Id": "TVM-04",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to update detection tools, threat signatures, and indicators of compromise on a weekly, or more frequent basis.",
- "Name": "Detection Updates",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.3",
- "TS1.4",
- "TM1.3",
- "TM1.4",
- "IM1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1.1",
- "27002: 5.1.1 (h)",
- "27001: A.12.6.1",
- "27002: 12.6.1 (b),(c)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1",
- "27001: A.8.8",
- "27001: A.8.15",
- "27001: A.8.16",
- "27002: 5.1",
- "27002: 5.37",
- "27002: 8.8",
- "27002: 8.15 (d)",
- "27002: 8.16 (d,e)",
- "27002: 8.31 2nd (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-7",
- "CM-7(4)",
- "RA-3",
- "RA-3(3)",
- "RA-5(2)",
- "SA-10",
- "SA-10(5)",
- "SA-11",
- "SA-11(2)",
- "SI-2",
- "SI-2(4)",
- "SI-3",
- "SI-3(4)",
- "SI-4",
- "SI-4(9)",
- "SI-4(24)",
- "SI-8",
- "SI-8(2)",
- "SI-8(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-02",
- "ID.RA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.2",
- "5.2a",
- "5.2b",
- "5.2c"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "5.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
- "defender_container_images_scan_enabled",
- "defender_ensure_defender_for_containers_is_on",
- "defender_ensure_defender_for_cosmosdb_is_on",
- "defender_ensure_defender_for_os_relational_databases_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_defender_for_sql_servers_is_on",
- "defender_ensure_wdatp_is_enabled"
- ]
- },
- {
- "Id": "TVM-05",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to identify updates for applications which use third party or open source libraries according to the organization's vulnerability management policy.",
- "Name": "External Library Vulnerabilities",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "SD2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.6.2",
- "27002: 12.6.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A 5.6",
- "27001: A.8.19",
- "27001: A.8.8",
- "27001: A.8.28",
- "27001: A.8.31",
- "27002: 5.6 (c)",
- "27001: 8.19",
- "27001: 8.8",
- "27001: 8.28",
- "27001: 8.31"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(3)",
- "SA-11",
- "SA-11(2)",
- "SA-11(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-03",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.2",
- "6.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_container_images_resolved_vulnerabilities",
- "defender_container_images_scan_enabled",
- "defender_ensure_defender_for_containers_is_on",
- "sqlserver_va_emails_notifications_admins_enabled",
- "sqlserver_va_periodic_recurring_scans_enabled",
- "sqlserver_va_scan_reports_configured",
- "sqlserver_vulnerability_assessment_enabled"
- ]
- },
- {
- "Id": "TVM-07",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the detection of vulnerabilities on organizationally managed assets at least monthly.",
- "Name": "Vulnerability Identification",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.1",
- "7.5",
- "7.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.6",
- "27001: A.12.6.1",
- "27002: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.8",
- "27002: 8.8"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(4)",
- "RA-5(5)",
- "SA-11",
- "SA-11(5)",
- "SA-15(5)",
- "SC-7",
- "SC-7(10)",
- "SI-3(8)",
- "SI-3(10)",
- "SI-7",
- "SI-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.RA-1",
- "DE.CM-8",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "11.2",
- "11.2.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "11.3.2",
- "11.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
- "defender_container_images_resolved_vulnerabilities",
- "defender_container_images_scan_enabled",
- "defender_ensure_defender_for_containers_is_on",
- "defender_ensure_defender_for_server_is_on",
- "defender_ensure_wdatp_is_enabled",
- "sqlserver_microsoft_defender_enabled",
- "sqlserver_vulnerability_assessment_enabled"
- ]
- },
- {
- "Id": "UEM-08",
- "Description": "Protect information from unauthorized disclosure on managed endpoint devices with storage encryption.",
- "Name": "Storage Encryption",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "MOS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "3.1.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "PA1.2",
- "PA1.3",
- "PA1.5",
- "PA2.2",
- "PM1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.11.2.7",
- "27002: 11.2.7",
- "27001: A.18.1.1",
- "27017: 18.1.1",
- "27001: A.12.3.1",
- "27017: 12.3.1",
- "27018: A.11.4",
- "27018: A.11.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.1",
- "27002: 8.1 (h)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.4",
- "3.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.5.1",
- "3.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "databricks_workspace_cmk_encryption_enabled",
- "storage_infrastructure_encryption_is_enabled",
- "vm_ensure_attached_disks_encrypted_with_cmk",
- "vm_ensure_unattached_disks_encrypted_with_cmk"
- ]
- },
- {
- "Id": "UEM-11",
- "Description": "Configure managed endpoints with Data Loss Prevention (DLP) technologies and rules in accordance with a risk assessment.",
- "Name": "Data Loss Prevention",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.5",
- "PA2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27002: 12.3",
- "27001: A.8.3.1",
- "27002: 8.3.1",
- "27001: A.12.2",
- "27002: 12.2",
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001: A.6.1.1",
- "27017: 6.1.1",
- "27018: 12.3.1",
- "27018: 10.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-7",
- "SC-7(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.DS-10",
- "PR.PS-01",
- "ID.AM-08",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A3.2.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A3.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "defender_ensure_defender_for_storage_is_on",
- "defender_ensure_mcas_is_enabled"
- ]
- }
- ]
-}
diff --git a/prowler/compliance/azure/fedramp_20x_ksi_low_azure.json b/prowler/compliance/azure/fedramp_20x_ksi_low_azure.json
index c845f75f60..655f649abe 100644
--- a/prowler/compliance/azure/fedramp_20x_ksi_low_azure.json
+++ b/prowler/compliance/azure/fedramp_20x_ksi_low_azure.json
@@ -328,6 +328,7 @@
"Checks": [
"entra_non_privileged_user_has_mfa",
"entra_privileged_user_has_mfa",
+ "entra_user_with_recent_sign_in",
"entra_user_with_vm_access_has_mfa",
"iam_custom_role_has_permissions_to_administer_resource_locks",
"iam_role_user_access_admin_restricted",
diff --git a/prowler/compliance/azure/hipaa_azure.json b/prowler/compliance/azure/hipaa_azure.json
index 332d081590..62ffe2fdad 100644
--- a/prowler/compliance/azure/hipaa_azure.json
+++ b/prowler/compliance/azure/hipaa_azure.json
@@ -182,6 +182,7 @@
}
],
"Checks": [
+ "entra_user_with_recent_sign_in",
"storage_key_rotation_90_days",
"keyvault_key_rotation_enabled",
"keyvault_rbac_key_expiration_set",
@@ -430,6 +431,7 @@
}
],
"Checks": [
+ "recovery_vault_backup_policy_retention_adequate",
"vm_backup_enabled",
"vm_sufficient_daily_backup_retention_period",
"storage_blob_versioning_is_enabled",
@@ -438,7 +440,10 @@
"storage_geo_redundant_enabled",
"keyvault_recoverable",
"sqlserver_auditing_retention_90_days",
- "postgresql_flexible_server_log_retention_days_greater_3"
+ "postgresql_flexible_server_log_retention_days_greater_3",
+ "cosmosdb_account_backup_policy_continuous",
+ "mysql_flexible_server_geo_redundant_backup_enabled",
+ "postgresql_flexible_server_geo_redundant_backup_enabled"
]
},
{
@@ -762,6 +767,17 @@
"mysql_flexible_server_minimum_tls_version_12",
"mysql_flexible_server_ssl_connection_enabled",
"postgresql_flexible_server_enforce_ssl_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -814,6 +830,17 @@
"mysql_flexible_server_ssl_connection_enabled",
"postgresql_flexible_server_enforce_ssl_enabled",
"databricks_workspace_cmk_encryption_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
}
]
diff --git a/prowler/compliance/azure/iso27001_2022_azure.json b/prowler/compliance/azure/iso27001_2022_azure.json
index 0051795890..23392533de 100644
--- a/prowler/compliance/azure/iso27001_2022_azure.json
+++ b/prowler/compliance/azure/iso27001_2022_azure.json
@@ -271,6 +271,7 @@
}
],
"Checks": [
+ "aks_cluster_local_accounts_disabled",
"defender_ensure_defender_for_containers_is_on",
"defender_ensure_defender_for_cosmosdb_is_on",
"defender_ensure_defender_for_databases_is_on",
@@ -284,6 +285,7 @@
"defender_ensure_notify_alerts_severity_is_high",
"entra_policy_guest_users_access_restrictions",
"entra_policy_restricts_user_consent_for_apps",
+ "entra_user_with_recent_sign_in",
"entra_users_cannot_create_microsoft_365_groups",
"iam_custom_role_has_permissions_to_administer_resource_locks",
"monitor_alert_create_update_security_solution",
@@ -332,7 +334,8 @@
"entra_policy_guest_invite_only_for_admin_roles",
"entra_policy_guest_users_access_restrictions",
"entra_policy_restricts_user_consent_for_apps",
- "entra_policy_user_consent_for_verified_apps"
+ "entra_policy_user_consent_for_verified_apps",
+ "entra_user_with_recent_sign_in"
]
},
{
@@ -1102,6 +1105,7 @@
}
],
"Checks": [
+ "entra_authentication_methods_policy_strong_auth_enforced",
"entra_conditional_access_policy_require_mfa_for_management_app",
"entra_non_privileged_user_has_mfa entra_privileged_user_has_mfa",
"entra_user_with_vm_access_has_mfa",
@@ -1266,7 +1270,12 @@
"Check_Summary": "Backup copies of information, software and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup."
}
],
- "Checks": []
+ "Checks": [
+ "cosmosdb_account_backup_policy_continuous",
+ "mysql_flexible_server_geo_redundant_backup_enabled",
+ "postgresql_flexible_server_geo_redundant_backup_enabled",
+ "recovery_vault_backup_policy_retention_adequate"
+ ]
},
{
"Id": "A.8.14",
@@ -1293,7 +1302,12 @@
"storage_ensure_private_endpoints_in_storage_accounts",
"storage_secure_transfer_required_is_enabled",
"vm_ensure_using_managed_disks",
- "vm_trusted_launch_enabled"
+ "vm_trusted_launch_enabled",
+ "cosmosdb_account_automatic_failover_enabled",
+ "mysql_flexible_server_geo_redundant_backup_enabled",
+ "mysql_flexible_server_high_availability_enabled",
+ "postgresql_flexible_server_geo_redundant_backup_enabled",
+ "postgresql_flexible_server_high_availability_enabled"
]
},
{
@@ -1337,6 +1351,8 @@
}
],
"Checks": [
+ "aks_cluster_azure_monitor_enabled",
+ "defender_ensure_defender_cspm_is_on",
"monitor_alert_create_policy_assignment",
"monitor_alert_create_update_nsg",
"monitor_alert_create_update_public_ip_address_rule",
@@ -1407,6 +1423,9 @@
"aks_network_policy_enabled",
"containerregistry_not_publicly_accessible",
"cosmosdb_account_firewall_use_selected_networks",
+ "cosmosdb_account_public_network_access_disabled",
+ "databricks_workspace_no_public_ip_enabled",
+ "databricks_workspace_public_network_access_disabled",
"network_bastion_host_exists",
"network_flow_log_captured_sent",
"network_flow_log_more_than_90_days",
@@ -1414,7 +1433,9 @@
"network_public_ip_shodan",
"network_rdp_internet_access_restricted",
"network_ssh_internet_access_restricted",
+ "network_subnet_nsg_associated",
"network_udp_internet_access_restricted",
+ "network_vnet_ddos_protection_enabled",
"network_watcher_enabled"
]
},
@@ -1468,6 +1489,7 @@
"network_public_ip_shodan",
"network_rdp_internet_access_restricted",
"network_ssh_internet_access_restricted",
+ "network_subnet_nsg_associated",
"network_udp_internet_access_restricted",
"network_watcher_enabled"
]
@@ -1500,6 +1522,8 @@
],
"Checks": [
"app_minimum_tls_version_12",
+ "cosmosdb_account_minimum_tls_version",
+ "entra_app_registration_credential_not_expired",
"monitor_storage_account_with_activity_logs_cmk_encrypted",
"sqlserver_tde_encrypted_with_cmk",
"sqlserver_tde_encryption_enabled",
diff --git a/prowler/compliance/azure/mitre_attack_azure.json b/prowler/compliance/azure/mitre_attack_azure.json
index 92ddd72713..8b338da534 100644
--- a/prowler/compliance/azure/mitre_attack_azure.json
+++ b/prowler/compliance/azure/mitre_attack_azure.json
@@ -212,6 +212,7 @@
"Description": "Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop.[1] Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.",
"TechniqueURL": "https://attack.mitre.org/techniques/T1078/",
"Checks": [
+ "entra_app_registration_credential_not_expired",
"entra_conditional_access_policy_require_mfa_for_management_api",
"entra_global_admin_in_less_than_five_users",
"entra_non_privileged_user_has_mfa",
diff --git a/prowler/compliance/azure/nis2_azure.json b/prowler/compliance/azure/nis2_azure.json
index 5c48c22f6b..0ae814fad7 100644
--- a/prowler/compliance/azure/nis2_azure.json
+++ b/prowler/compliance/azure/nis2_azure.json
@@ -1133,6 +1133,17 @@
"defender_ensure_defender_for_dns_is_on",
"sqlserver_tde_encryption_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "6 SECURITY IN NETWORK AND INFORMATION SYSTEMS ACQUISITION, DEVELOPMENT AND MAINTENANCE (ARTICLE 21(2), POINT (E), OF DIRECTIVE (EU) 2022/2555)",
@@ -1164,6 +1175,17 @@
"network_udp_internet_access_restricted",
"network_watcher_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "6 SECURITY IN NETWORK AND INFORMATION SYSTEMS ACQUISITION, DEVELOPMENT AND MAINTENANCE (ARTICLE 21(2), POINT (E), OF DIRECTIVE (EU) 2022/2555)",
@@ -1887,6 +1909,17 @@
"sqlserver_tde_encrypted_with_cmk",
"sqlserver_tde_encryption_enabled"
],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
+ ],
"Attributes": [
{
"Section": "12 ASSET MANAGEMENT (ARTICLE 21(2), POINT (I), OF DIRECTIVE (EU) 2022/2555)",
diff --git a/prowler/compliance/azure/prowler_threatscore_azure.json b/prowler/compliance/azure/prowler_threatscore_azure.json
index a65a7f60e8..a030bb845b 100644
--- a/prowler/compliance/azure/prowler_threatscore_azure.json
+++ b/prowler/compliance/azure/prowler_threatscore_azure.json
@@ -459,7 +459,7 @@
"Id": "2.2.6",
"Description": "Ensure that 'Public Network Access' is 'Disabled' for storage accounts",
"Checks": [
- "storage_blob_public_access_level_is_disabled"
+ "storage_account_public_network_access_disabled"
],
"Attributes": [
{
diff --git a/prowler/compliance/azure/secnumcloud_3.2_azure.json b/prowler/compliance/azure/secnumcloud_3.2_azure.json
index ef8c94113e..3f2e8c7603 100644
--- a/prowler/compliance/azure/secnumcloud_3.2_azure.json
+++ b/prowler/compliance/azure/secnumcloud_3.2_azure.json
@@ -339,6 +339,7 @@
}
],
"Checks": [
+ "entra_authentication_methods_policy_strong_auth_enforced",
"entra_non_privileged_user_has_mfa",
"entra_privileged_user_has_mfa",
"entra_security_defaults_enabled"
@@ -439,6 +440,25 @@
"postgresql_flexible_server_enforce_ssl_enabled",
"mysql_flexible_server_ssl_connection_enabled",
"mysql_flexible_server_minimum_tls_version_12"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ },
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
]
},
{
@@ -493,7 +513,8 @@
"keyvault_non_rbac_secret_expiration_set",
"keyvault_logging_enabled",
"keyvault_private_endpoints",
- "keyvault_access_only_through_private_endpoints"
+ "keyvault_access_only_through_private_endpoints",
+ "entra_app_registration_credential_not_expired"
]
},
{
diff --git a/prowler/compliance/azure/soc2_azure.json b/prowler/compliance/azure/soc2_azure.json
index d8936f5485..c3b4db6e39 100644
--- a/prowler/compliance/azure/soc2_azure.json
+++ b/prowler/compliance/azure/soc2_azure.json
@@ -241,7 +241,8 @@
"app_function_not_publicly_accessible",
"containerregistry_not_publicly_accessible",
"network_public_ip_shodan",
- "storage_blob_public_access_level_is_disabled"
+ "storage_blob_public_access_level_is_disabled",
+ "entra_app_registration_credential_not_expired"
]
},
{
@@ -265,6 +266,17 @@
"sqlserver_tde_encryption_enabled",
"sqlserver_unrestricted_inbound_access",
"storage_secure_transfer_required_is_enabled"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
@@ -307,7 +319,19 @@
"app_minimum_tls_version_12",
"mysql_flexible_server_minimum_tls_version_12",
"sqlserver_recommended_minimal_tls_version",
- "storage_ensure_minimum_tls_version_12"
+ "storage_ensure_minimum_tls_version_12",
+ "network_subnet_nsg_associated"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/cis_controls_8.1.json b/prowler/compliance/cis_controls_8.1.json
new file mode 100644
index 0000000000..c03d9e806b
--- /dev/null
+++ b/prowler/compliance/cis_controls_8.1.json
@@ -0,0 +1,4554 @@
+{
+ "framework": "CIS-Controls",
+ "name": "CIS Controls v8.1",
+ "version": "8.1",
+ "description": "The CIS Critical Security Controls (CIS Controls) v8.1 are a prioritized set of Safeguards to mitigate the most prevalent cyber-attacks against systems and networks. They are organized into 18 top-level Controls and mapped to three Implementation Groups (IG1, IG2, IG3). This is a cross-provider mapping of Prowler checks to the CIS Controls Safeguards that can be assessed automatically against cloud and platform configurations.",
+ "icon": "cisecurity",
+ "attributes_metadata": [
+ {
+ "key": "Section",
+ "label": "CIS Control",
+ "type": "str",
+ "required": true,
+ "enum": [
+ "1. Inventory and Control of Enterprise Assets",
+ "2. Inventory and Control of Software Assets",
+ "3. Data Protection",
+ "4. Secure Configuration of Enterprise Assets and Software",
+ "5. Account Management",
+ "6. Access Control Management",
+ "7. Continuous Vulnerability Management",
+ "8. Audit Log Management",
+ "9. Email and Web Browser Protections",
+ "10. Malware Defenses",
+ "11. Data Recovery",
+ "12. Network Infrastructure Management",
+ "13. Network Monitoring and Defense",
+ "14. Security Awareness and Skills Training",
+ "15. Service Provider Management",
+ "16. Application Software Security",
+ "17. Incident Response Management",
+ "18. Penetration Testing"
+ ],
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ },
+ {
+ "key": "Function",
+ "label": "Security Function",
+ "type": "str",
+ "required": false,
+ "enum": [
+ "Identify",
+ "Protect",
+ "Detect",
+ "Respond",
+ "Recover",
+ "Govern"
+ ],
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ },
+ {
+ "key": "AssetType",
+ "label": "Asset Type",
+ "type": "str",
+ "required": false,
+ "enum": [
+ "Data",
+ "Devices",
+ "Documentation",
+ "Network",
+ "Software",
+ "Users"
+ ],
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ },
+ {
+ "key": "ImplementationGroups",
+ "label": "Implementation Groups",
+ "type": "list_str",
+ "required": false,
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ }
+ ],
+ "outputs": {
+ "table_config": {
+ "group_by": "Section"
+ },
+ "pdf_config": {
+ "language": "en",
+ "primary_color": "#cc0000",
+ "secondary_color": "#7a1f1f",
+ "bg_color": "#FAF0F0",
+ "group_by_field": "Section",
+ "sections": [
+ "1. Inventory and Control of Enterprise Assets",
+ "2. Inventory and Control of Software Assets",
+ "3. Data Protection",
+ "4. Secure Configuration of Enterprise Assets and Software",
+ "5. Account Management",
+ "6. Access Control Management",
+ "7. Continuous Vulnerability Management",
+ "8. Audit Log Management",
+ "9. Email and Web Browser Protections",
+ "10. Malware Defenses",
+ "11. Data Recovery",
+ "12. Network Infrastructure Management",
+ "13. Network Monitoring and Defense",
+ "14. Security Awareness and Skills Training",
+ "15. Service Provider Management",
+ "16. Application Software Security",
+ "17. Incident Response Management",
+ "18. Penetration Testing"
+ ],
+ "section_short_names": {
+ "1. Inventory and Control of Enterprise Assets": "CIS 1",
+ "2. Inventory and Control of Software Assets": "CIS 2",
+ "3. Data Protection": "CIS 3",
+ "4. Secure Configuration of Enterprise Assets and Software": "CIS 4",
+ "5. Account Management": "CIS 5",
+ "6. Access Control Management": "CIS 6",
+ "7. Continuous Vulnerability Management": "CIS 7",
+ "8. Audit Log Management": "CIS 8",
+ "9. Email and Web Browser Protections": "CIS 9",
+ "10. Malware Defenses": "CIS 10",
+ "11. Data Recovery": "CIS 11",
+ "12. Network Infrastructure Management": "CIS 12",
+ "13. Network Monitoring and Defense": "CIS 13",
+ "14. Security Awareness and Skills Training": "CIS 14",
+ "15. Service Provider Management": "CIS 15",
+ "16. Application Software Security": "CIS 16",
+ "17. Incident Response Management": "CIS 17",
+ "18. Penetration Testing": "CIS 18"
+ },
+ "charts": [
+ {
+ "id": "section_compliance",
+ "type": "horizontal_bar",
+ "group_by": "Section",
+ "title": "Compliance Score by CIS Control",
+ "y_label": "CIS Control",
+ "x_label": "Compliance %",
+ "value_source": "compliance_percent",
+ "color_mode": "by_value"
+ }
+ ],
+ "filter": {
+ "only_failed": true,
+ "include_manual": false
+ }
+ }
+ },
+ "requirements": [
+ {
+ "id": "1.1",
+ "name": "Establish and Maintain Detailed Enterprise Asset Inventory",
+ "description": "Establish and maintain an accurate, detailed, and up-to-date inventory of all enterprise assets with the potential to store or process data, to include: end-user devices (including portable and mobile), network devices, non-computing/IoT devices, and servers. Ensure the inventory records the network address (if static), hardware address, machine name, enterprise asset owner, department for each asset, and whether the asset has been approved to connect to the network. For mobile end-user devices, MDM type tools can support this process, where appropriate. This inventory includes assets connected to the infrastructure physically, virtually, remotely, and those within cloud environments. Additionally, it includes assets that are regularly connected to the enterprise's network infrastructure, even if they are not under control of the enterprise. Review and update the inventory of all enterprise assets bi-annually, or more frequently.",
+ "attributes": {
+ "Section": "1. Inventory and Control of Enterprise Assets",
+ "Function": "Identify",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "config_recorder_all_regions_enabled",
+ "resourceexplorer2_indexes_found"
+ ],
+ "gcp": [
+ "iam_cloud_asset_inventory_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "1.2",
+ "name": "Address Unauthorized Assets",
+ "description": "Ensure that a process exists to address unauthorized assets on a weekly basis. The enterprise may choose to remove the asset from the network, deny the asset from connecting remotely to the network, or quarantine the asset.",
+ "attributes": {
+ "Section": "1. Inventory and Control of Enterprise Assets",
+ "Function": "Respond",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "1.3",
+ "name": "Utilize an Active Discovery Tool",
+ "description": "Utilize an active discovery tool to identify assets connected to the enterprise's network. Configure the active discovery tool to execute daily, or more frequently.",
+ "attributes": {
+ "Section": "1. Inventory and Control of Enterprise Assets",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "1.4",
+ "name": "Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory",
+ "description": "Use DHCP logging on all DHCP servers or Internet Protocol (IP) address management tools to update the enterprise's asset inventory. Review and use logs to update the enterprise's asset inventory weekly, or more frequently.",
+ "attributes": {
+ "Section": "1. Inventory and Control of Enterprise Assets",
+ "Function": "Identify",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "1.5",
+ "name": "Use a Passive Asset Discovery Tool",
+ "description": "Use a passive discovery tool to identify assets connected to the enterprise's network. Review and use scans to update the enterprise's asset inventory at least weekly, or more frequently.",
+ "attributes": {
+ "Section": "1. Inventory and Control of Enterprise Assets",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "2.1",
+ "name": "Establish and Maintain a Software Inventory",
+ "description": "Establish and maintain a detailed inventory of all licensed software installed on enterprise assets. The software inventory must document the title, publisher, initial install/use date, and business purpose for each entry; where appropriate, include the Uniform Resource Locator (URL), app store(s), version(s), deployment mechanism, decommission date, and number of licenses. Review and update the software inventory bi-annually, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "2.2",
+ "name": "Ensure Authorized Software is Currently Supported",
+ "description": "Ensure that only currently supported software is designated as authorized in the software inventory for enterprise assets. If software is unsupported, yet necessary for the fulfillment of the enterprise's mission, document an exception detailing mitigating controls and residual risk acceptance. For any unsupported software without an exception documentation, designate as unauthorized. Review the software list to verify software support at least monthly, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "awslambda_function_using_supported_runtimes",
+ "ec2_instance_with_outdated_ami",
+ "eks_cluster_uses_a_supported_version",
+ "kafka_cluster_uses_latest_version",
+ "rds_instance_deprecated_engine_version"
+ ]
+ }
+ },
+ {
+ "id": "2.3",
+ "name": "Address Unauthorized Software",
+ "description": "Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Respond",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "2.4",
+ "name": "Utilize Automated Software Inventory Tools",
+ "description": "Utilize software inventory tools, when possible, throughout the enterprise to automate the discovery and documentation of installed software.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Detect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "2.5",
+ "name": "Allowlist Authorized Software",
+ "description": "Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "googleworkspace": [
+ "chat_apps_installation_disabled",
+ "marketplace_apps_access_restricted",
+ "security_app_access_restricted"
+ ],
+ "m365": [
+ "entra_admin_consent_workflow_enabled",
+ "entra_policy_restricts_user_consent_for_apps",
+ "entra_thirdparty_integrated_apps_not_allowed"
+ ]
+ }
+ },
+ {
+ "id": "2.6",
+ "name": "Allowlist Authorized Libraries",
+ "description": "Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, and .so files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "2.7",
+ "name": "Allowlist Authorized Scripts",
+ "description": "Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, and .py files are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.",
+ "attributes": {
+ "Section": "2. Inventory and Control of Software Assets",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.1",
+ "name": "Establish and Maintain a Data Management Process",
+ "description": "Establish and maintain a documented data management process. In the process, address data sensitivity, data owner, handling of data, data retention limits, and disposal requirements, based on sensitivity and retention standards for the enterprise. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Govern",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.2",
+ "name": "Establish and Maintain a Data Inventory",
+ "description": "Establish and maintain a data inventory based on the enterprise's data management process. Inventory sensitive data, at a minimum. Review and update inventory annually, at a minimum, with a priority on sensitive data.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Identify",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "macie_automated_sensitive_data_discovery_enabled",
+ "macie_is_enabled"
+ ]
+ }
+ },
+ {
+ "id": "3.3",
+ "name": "Configure Data Access Control Lists",
+ "description": "Configure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "actiontrail_oss_bucket_not_publicly_accessible",
+ "oss_bucket_not_publicly_accessible",
+ "rds_instance_no_public_access_whitelist"
+ ],
+ "aws": [
+ "awslambda_function_not_publicly_accessible",
+ "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
+ "cloudwatch_log_group_not_publicly_accessible",
+ "codebuild_project_not_publicly_accessible",
+ "dynamodb_table_cross_account_access",
+ "ec2_ami_public",
+ "ecr_repositories_not_publicly_accessible",
+ "efs_access_point_enforce_root_directory",
+ "efs_access_point_enforce_user_identity",
+ "efs_mount_target_not_publicly_accessible",
+ "efs_not_publicly_accessible",
+ "eventbridge_bus_cross_account_access",
+ "eventbridge_bus_exposed",
+ "glacier_vaults_policy_public_access",
+ "glue_data_catalogs_not_publicly_accessible",
+ "kms_key_not_publicly_accessible",
+ "s3_access_point_public_access_block",
+ "s3_account_level_public_access_blocks",
+ "s3_bucket_acl_prohibited",
+ "s3_bucket_cross_account_access",
+ "s3_bucket_level_public_access_block",
+ "s3_bucket_policy_public_write_access",
+ "s3_bucket_public_access",
+ "s3_bucket_public_list_acl",
+ "s3_bucket_public_write_acl",
+ "s3_multi_region_access_point_public_access_block",
+ "secretsmanager_has_restrictive_resource_policy",
+ "secretsmanager_not_publicly_accessible",
+ "ses_identity_not_publicly_accessible",
+ "sns_topics_not_publicly_accessible",
+ "sqs_queues_not_publicly_accessible",
+ "ssm_documents_set_as_public"
+ ],
+ "azure": [
+ "cosmosdb_account_firewall_use_selected_networks",
+ "cosmosdb_account_use_aad_and_rbac",
+ "keyvault_rbac_enabled",
+ "sqlserver_unrestricted_inbound_access",
+ "storage_account_key_access_disabled",
+ "storage_account_public_network_access_disabled",
+ "storage_blob_public_access_level_is_disabled",
+ "storage_default_network_access_rule_is_denied"
+ ],
+ "gcp": [
+ "bigquery_dataset_public_access",
+ "cloudfunction_function_not_publicly_accessible",
+ "cloudsql_instance_public_access",
+ "cloudstorage_bucket_public_access",
+ "cloudstorage_bucket_uniform_bucket_level_access",
+ "compute_image_not_publicly_shared",
+ "kms_key_not_publicly_accessible",
+ "secretmanager_secret_not_publicly_accessible"
+ ],
+ "github": [
+ "organization_default_repository_permission_strict"
+ ],
+ "googleworkspace": [
+ "calendar_external_sharing_primary_calendar",
+ "calendar_external_sharing_secondary_calendar",
+ "chat_external_file_sharing_disabled",
+ "chat_external_messaging_restricted",
+ "chat_external_spaces_restricted",
+ "chat_internal_file_sharing_disabled",
+ "drive_access_checker_recipients_only",
+ "drive_internal_users_distribute_content",
+ "drive_publishing_files_disabled",
+ "drive_shared_drive_disable_download_print_copy",
+ "drive_shared_drive_managers_cannot_override",
+ "drive_shared_drive_members_only_access",
+ "drive_sharing_allowlisted_domains",
+ "gmail_auto_forwarding_disabled",
+ "gmail_mail_delegation_disabled",
+ "groups_external_access_restricted",
+ "groups_view_conversations_restricted"
+ ],
+ "kubernetes": [
+ "core_no_secrets_envs",
+ "rbac_minimize_secret_access"
+ ],
+ "m365": [
+ "admincenter_external_calendar_sharing_disabled",
+ "admincenter_groups_not_public_visibility",
+ "admincenter_organization_customer_lockbox_enabled",
+ "sharepoint_external_sharing_managed",
+ "sharepoint_external_sharing_restricted",
+ "sharepoint_guest_sharing_restricted",
+ "teams_external_domains_restricted",
+ "teams_external_file_sharing_restricted",
+ "teams_external_users_cannot_start_conversations",
+ "teams_unmanaged_communication_disabled"
+ ],
+ "mongodbatlas": [
+ "clusters_authentication_enabled"
+ ],
+ "openstack": [
+ "image_not_publicly_visible",
+ "image_not_shared_with_multiple_projects",
+ "objectstorage_container_acl_not_globally_shared",
+ "objectstorage_container_listing_disabled",
+ "objectstorage_container_public_read_acl_disabled",
+ "objectstorage_container_write_acl_restricted"
+ ],
+ "oraclecloud": [
+ "analytics_instance_access_restricted",
+ "database_autonomous_database_access_restricted",
+ "integration_instance_access_restricted",
+ "objectstorage_bucket_not_publicly_accessible"
+ ],
+ "vercel": [
+ "project_deployment_protection_enabled",
+ "project_password_protection_enabled",
+ "project_production_deployment_protection_enabled",
+ "team_member_role_least_privilege"
+ ]
+ }
+ },
+ {
+ "id": "3.4",
+ "name": "Enforce Data Retention",
+ "description": "Retain data according to the enterprise's documented data management process. Data retention must include both minimum and maximum timelines.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ecr_repositories_lifecycle_policy_enabled",
+ "kinesis_stream_data_retention_period",
+ "s3_bucket_lifecycle_enabled"
+ ],
+ "gcp": [
+ "cloudstorage_bucket_lifecycle_management_enabled",
+ "cloudstorage_bucket_sufficient_retention_period"
+ ],
+ "stackit": [
+ "objectstorage_bucket_object_lock_enabled",
+ "objectstorage_bucket_retention_policy"
+ ]
+ }
+ },
+ {
+ "id": "3.5",
+ "name": "Securely Dispose of Data",
+ "description": "Securely dispose of data as outlined in the enterprise's documented data management process. Ensure the disposal process and method are commensurate with the data sensitivity.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.6",
+ "name": "Encrypt Data on End-User Devices",
+ "description": "Encrypt data on end-user devices containing sensitive data. Example implementations can include: Windows BitLocker®, Apple FileVault®, Linux® dm-crypt.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.7",
+ "name": "Establish and Maintain a Data Classification Scheme",
+ "description": "Establish and maintain an overall data classification scheme for the enterprise. Enterprises may use labels, such as \"Sensitive,\" \"Confidential,\" and \"Public,\" and classify their data according to those labels. Review and update the classification scheme annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Identify",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.8",
+ "name": "Document Data Flows",
+ "description": "Document data flows. Data flow documentation includes service provider data flows and should be based on the enterprise's data management process. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Identify",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.9",
+ "name": "Encrypt Data on Removable Media",
+ "description": "Encrypt data on removable media.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.10",
+ "name": "Encrypt Sensitive Data in Transit",
+ "description": "Encrypt sensitive data in transit. Example implementations can include: Transport Layer Security (TLS) and Open Secure Shell (OpenSSH).",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "oss_bucket_secure_transport_enabled",
+ "rds_instance_ssl_enabled"
+ ],
+ "aws": [
+ "cloudfront_distributions_https_enabled",
+ "cloudfront_distributions_origin_traffic_encrypted",
+ "cloudfront_distributions_using_deprecated_ssl_protocols",
+ "dms_endpoint_redis_in_transit_encryption_enabled",
+ "dms_endpoint_ssl_enabled",
+ "dynamodb_accelerator_cluster_in_transit_encryption_enabled",
+ "elasticache_redis_cluster_in_transit_encryption_enabled",
+ "elb_insecure_ssl_ciphers",
+ "elb_ssl_listeners",
+ "elb_ssl_listeners_use_acm_certificate",
+ "elbv2_insecure_ssl_ciphers",
+ "elbv2_nlb_tls_termination_enabled",
+ "elbv2_ssl_listeners",
+ "glue_database_connections_ssl_enabled",
+ "kafka_cluster_in_transit_encryption_enabled",
+ "kafka_connector_in_transit_encryption_enabled",
+ "opensearch_service_domains_https_communications_enforced",
+ "opensearch_service_domains_node_to_node_encryption_enabled",
+ "rds_instance_transport_encrypted",
+ "redshift_cluster_in_transit_encryption_enabled",
+ "s3_bucket_secure_transport_policy",
+ "sagemaker_training_jobs_intercontainer_encryption_enabled",
+ "sns_subscription_not_using_http_endpoints",
+ "transfer_server_in_transit_encryption_enabled"
+ ],
+ "azure": [
+ "app_ensure_http_is_redirected_to_https",
+ "app_minimum_tls_version_12",
+ "cosmosdb_account_minimum_tls_version",
+ "mysql_flexible_server_minimum_tls_version_12",
+ "mysql_flexible_server_ssl_connection_enabled",
+ "postgresql_flexible_server_enforce_ssl_enabled",
+ "sqlserver_recommended_minimal_tls_version",
+ "storage_ensure_minimum_tls_version_12",
+ "storage_secure_transfer_required_is_enabled",
+ "storage_smb_channel_encryption_with_secure_algorithm"
+ ],
+ "cloudflare": [
+ "zone_automatic_https_rewrites_enabled",
+ "zone_hsts_enabled",
+ "zone_https_redirect_enabled",
+ "zone_min_tls_version_secure",
+ "zone_ssl_strict",
+ "zone_tls_1_3_enabled",
+ "zone_universal_ssl_enabled"
+ ],
+ "gcp": [
+ "cloudsql_instance_ssl_connections"
+ ],
+ "kubernetes": [
+ "apiserver_etcd_cafile_set",
+ "apiserver_etcd_tls_config",
+ "apiserver_kubelet_cert_auth",
+ "apiserver_kubelet_tls_auth",
+ "apiserver_strong_ciphers_only",
+ "apiserver_tls_config",
+ "etcd_no_auto_tls",
+ "etcd_no_peer_auto_tls",
+ "etcd_peer_tls_config",
+ "etcd_tls_encryption",
+ "kubelet_strong_ciphers_only",
+ "kubelet_tls_cert_and_key"
+ ],
+ "mongodbatlas": [
+ "clusters_tls_enabled"
+ ],
+ "oraclecloud": [
+ "compute_instance_in_transit_encryption_enabled"
+ ],
+ "vercel": [
+ "domain_ssl_certificate_valid"
+ ]
+ }
+ },
+ {
+ "id": "3.11",
+ "name": "Encrypt Sensitive Data at Rest",
+ "description": "Encrypt sensitive data at rest on servers, applications, and databases. Storage-layer encryption, also known as server-side encryption, meets the minimum requirement of this Safeguard. Additional encryption methods may include application-layer encryption, also known as client-side encryption, where access to the data storage device(s) does not permit access to the plain-text data.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ecs_attached_disk_encrypted",
+ "ecs_unattached_disk_encrypted",
+ "rds_instance_tde_enabled",
+ "rds_instance_tde_key_custom"
+ ],
+ "aws": [
+ "apigateway_restapi_cache_encrypted",
+ "athena_workgroup_encryption",
+ "awslambda_function_env_vars_not_encrypted_with_cmk",
+ "backup_recovery_point_encrypted",
+ "backup_vaults_encrypted",
+ "bedrock_model_invocation_logs_encryption_enabled",
+ "bedrock_prompt_encrypted_with_cmk",
+ "cloudtrail_kms_encryption_enabled",
+ "cloudwatch_log_group_kms_encryption_enabled",
+ "codebuild_project_s3_logs_encrypted",
+ "codebuild_report_group_export_encrypted",
+ "documentdb_cluster_storage_encrypted",
+ "dynamodb_accelerator_cluster_encryption_enabled",
+ "dynamodb_tables_kms_cmk_encryption_enabled",
+ "ec2_ebs_default_encryption",
+ "ec2_ebs_snapshots_encrypted",
+ "ec2_ebs_volume_encryption",
+ "efs_encryption_at_rest_enabled",
+ "eks_cluster_kms_cmk_encryption_in_secrets_enabled",
+ "elasticache_redis_cluster_rest_encryption_enabled",
+ "firehose_stream_encrypted_at_rest",
+ "glue_data_catalogs_connection_passwords_encryption_enabled",
+ "glue_data_catalogs_metadata_encryption_enabled",
+ "glue_development_endpoints_s3_encryption_enabled",
+ "glue_etl_jobs_amazon_s3_encryption_enabled",
+ "glue_etl_jobs_cloudwatch_logs_encryption_enabled",
+ "glue_ml_transform_encrypted_at_rest",
+ "kafka_cluster_encryption_at_rest_uses_cmk",
+ "kinesis_stream_encrypted_at_rest",
+ "neptune_cluster_snapshot_encrypted",
+ "neptune_cluster_storage_encrypted",
+ "opensearch_service_domains_encryption_at_rest_enabled",
+ "rds_cluster_storage_encrypted",
+ "rds_instance_storage_encrypted",
+ "rds_snapshots_encrypted",
+ "redshift_cluster_encrypted_at_rest",
+ "s3_bucket_default_encryption",
+ "s3_bucket_kms_encryption",
+ "sagemaker_notebook_instance_encryption_enabled",
+ "sagemaker_training_jobs_volume_and_output_encryption_enabled",
+ "sns_topics_kms_encryption_at_rest_enabled",
+ "sqs_queues_server_side_encryption_enabled",
+ "stepfunctions_statemachine_encrypted_with_cmk",
+ "storagegateway_fileshare_encryption_enabled",
+ "workspaces_volume_encryption_enabled"
+ ],
+ "azure": [
+ "databricks_workspace_cmk_encryption_enabled",
+ "monitor_storage_account_with_activity_logs_cmk_encrypted",
+ "sqlserver_tde_encrypted_with_cmk",
+ "sqlserver_tde_encryption_enabled",
+ "storage_ensure_encryption_with_customer_managed_keys",
+ "storage_infrastructure_encryption_is_enabled",
+ "vm_ensure_attached_disks_encrypted_with_cmk",
+ "vm_ensure_unattached_disks_encrypted_with_cmk"
+ ],
+ "gcp": [
+ "bigquery_dataset_cmk_encryption",
+ "bigquery_table_cmk_encryption",
+ "cloudsql_instance_cmek_encryption_enabled",
+ "compute_instance_encryption_with_csek_enabled",
+ "dataproc_encrypted_with_cmks_disabled"
+ ],
+ "kubernetes": [
+ "apiserver_encryption_provider_config_set"
+ ],
+ "linode": [
+ "compute_instance_disk_encryption_enabled"
+ ],
+ "mongodbatlas": [
+ "clusters_encryption_at_rest_enabled"
+ ],
+ "openstack": [
+ "blockstorage_volume_encryption_enabled"
+ ],
+ "oraclecloud": [
+ "blockstorage_block_volume_encrypted_with_cmk",
+ "blockstorage_boot_volume_encrypted_with_cmk",
+ "filestorage_file_system_encrypted_with_cmk",
+ "objectstorage_bucket_encrypted_with_cmk"
+ ],
+ "vercel": [
+ "project_environment_no_secrets_in_plain_type"
+ ]
+ }
+ },
+ {
+ "id": "3.12",
+ "name": "Segment Data Processing and Storage Based on Sensitivity",
+ "description": "Segment data processing and storage based on the sensitivity of the data. Do not process sensitive data on enterprise assets intended for lower sensitivity data.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "3.13",
+ "name": "Deploy a Data Loss Prevention Solution",
+ "description": "Implement an automated tool, such as a host-based Data Loss Prevention (DLP) tool to identify all sensitive data stored, processed, or transmitted through enterprise assets, including those located onsite or at a remote service provider, and update the enterprise's data inventory.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "macie_automated_sensitive_data_discovery_enabled",
+ "macie_is_enabled"
+ ],
+ "googleworkspace": [
+ "security_dlp_drive_rules_configured"
+ ],
+ "openstack": [
+ "blockstorage_snapshot_metadata_sensitive_data",
+ "blockstorage_volume_metadata_sensitive_data",
+ "compute_instance_metadata_sensitive_data",
+ "objectstorage_container_metadata_sensitive_data"
+ ]
+ }
+ },
+ {
+ "id": "3.14",
+ "name": "Log Sensitive Data Access",
+ "description": "Log sensitive data access, including modification and disposal.",
+ "attributes": {
+ "Section": "3. Data Protection",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "oss_bucket_logging_enabled",
+ "rds_instance_sql_audit_enabled"
+ ],
+ "aws": [
+ "cloudtrail_s3_dataevents_read_enabled",
+ "cloudtrail_s3_dataevents_write_enabled",
+ "opensearch_service_domains_audit_logging_enabled"
+ ],
+ "azure": [
+ "keyvault_logging_enabled",
+ "mysql_flexible_server_audit_log_enabled",
+ "sqlserver_auditing_enabled"
+ ],
+ "gcp": [
+ "cloudstorage_audit_logs_enabled"
+ ],
+ "m365": [
+ "exchange_organization_mailbox_auditing_enabled",
+ "exchange_user_mailbox_auditing_enabled",
+ "purview_audit_log_search_enabled"
+ ],
+ "mongodbatlas": [
+ "projects_auditing_enabled"
+ ],
+ "oraclecloud": [
+ "objectstorage_bucket_logging_enabled"
+ ]
+ }
+ },
+ {
+ "id": "4.1",
+ "name": "Establish and Maintain a Secure Configuration Process",
+ "description": "Establish and maintain a documented secure configuration process for enterprise assets (end-user devices, including portable and mobile, non-computing/IoT devices, and servers) and software (operating systems and applications). Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "policy_ensure_asc_enforcement_enabled"
+ ],
+ "kubernetes": [
+ "apiserver_request_timeout_set",
+ "controllermanager_garbage_collection",
+ "kubelet_conf_file_ownership",
+ "kubelet_conf_file_permissions",
+ "kubelet_config_yaml_ownership",
+ "kubelet_config_yaml_permissions",
+ "kubelet_event_record_qps",
+ "kubelet_service_file_ownership_root",
+ "kubelet_service_file_permissions",
+ "kubelet_streaming_connection_timeout"
+ ],
+ "openstack": [
+ "compute_instance_config_drive_enabled",
+ "compute_instance_locked_status_enabled",
+ "compute_instance_trusted_image_certificates",
+ "image_secure_boot_enabled",
+ "image_signature_verification_enabled"
+ ]
+ }
+ },
+ {
+ "id": "4.2",
+ "name": "Establish and Maintain a Secure Configuration Process for Network Infrastructure",
+ "description": "Establish and maintain a documented secure configuration process for network devices. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "4.3",
+ "name": "Configure Automatic Session Locking on Enterprise Assets",
+ "description": "Configure automatic session locking on enterprise assets after a defined period of inactivity. For general purpose operating systems, the period must not exceed 15 minutes. For mobile end-user devices, the period must not exceed 2 minutes.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "appstream_fleet_maximum_session_duration",
+ "appstream_fleet_session_disconnect_timeout",
+ "appstream_fleet_session_idle_disconnect_timeout"
+ ],
+ "googleworkspace": [
+ "security_session_duration_limited"
+ ],
+ "m365": [
+ "entra_admin_users_sign_in_frequency_enabled",
+ "entra_conditional_access_policy_corporate_device_sign_in_frequency_enforced",
+ "entra_intune_enrollment_sign_in_frequency_every_time"
+ ],
+ "okta": [
+ "application_admin_console_session_idle_timeout_15min",
+ "signon_global_session_cookies_not_persistent",
+ "signon_global_session_idle_timeout_15min",
+ "signon_global_session_lifetime_18h"
+ ]
+ }
+ },
+ {
+ "id": "4.4",
+ "name": "Implement and Manage a Firewall on Servers",
+ "description": "Implement and manage a firewall on servers, where supported. Example implementations include a virtual firewall, operating system firewall, or a third-party firewall agent.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ecs_securitygroup_restrict_rdp_internet",
+ "ecs_securitygroup_restrict_ssh_internet"
+ ],
+ "aws": [
+ "ec2_instance_port_cassandra_exposed_to_internet",
+ "ec2_instance_port_cifs_exposed_to_internet",
+ "ec2_instance_port_elasticsearch_kibana_exposed_to_internet",
+ "ec2_instance_port_ftp_exposed_to_internet",
+ "ec2_instance_port_kafka_exposed_to_internet",
+ "ec2_instance_port_kerberos_exposed_to_internet",
+ "ec2_instance_port_ldap_exposed_to_internet",
+ "ec2_instance_port_memcached_exposed_to_internet",
+ "ec2_instance_port_mongodb_exposed_to_internet",
+ "ec2_instance_port_mysql_exposed_to_internet",
+ "ec2_instance_port_oracle_exposed_to_internet",
+ "ec2_instance_port_postgresql_exposed_to_internet",
+ "ec2_instance_port_rdp_exposed_to_internet",
+ "ec2_instance_port_redis_exposed_to_internet",
+ "ec2_instance_port_sqlserver_exposed_to_internet",
+ "ec2_instance_port_ssh_exposed_to_internet",
+ "ec2_instance_port_telnet_exposed_to_internet",
+ "ec2_securitygroup_allow_ingress_from_internet_to_all_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_any_port",
+ "ec2_securitygroup_allow_ingress_from_internet_to_any_port_from_ip",
+ "ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_3389",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_cassandra_7199_9160_8888",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_elasticsearch_kibana_9200_9300_5601",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_ftp_20_21",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_kafka_9092",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_memcached_11211",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_mongodb_27017_27018",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_mysql_3306",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_oracle_1521_2483",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_postgres_5432",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_redis_6379",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_sql_server_1433_1434",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_telnet_23",
+ "ec2_securitygroup_allow_wide_open_public_ipv4",
+ "ec2_securitygroup_default_restrict_traffic",
+ "ec2_securitygroup_with_many_ingress_egress_rules"
+ ],
+ "azure": [
+ "network_subnet_nsg_associated",
+ "network_rdp_internet_access_restricted",
+ "network_ssh_internet_access_restricted"
+ ],
+ "gcp": [
+ "compute_firewall_rdp_access_from_the_internet_allowed",
+ "compute_firewall_ssh_access_from_the_internet_allowed"
+ ],
+ "kubernetes": [
+ "kubelet_manage_iptables"
+ ],
+ "linode": [
+ "networking_firewall_assigned_to_devices",
+ "networking_firewall_default_inbound_policy_drop",
+ "networking_firewall_default_outbound_policy_drop",
+ "networking_firewall_inbound_rules_configured",
+ "networking_firewall_outbound_rules_configured",
+ "networking_firewall_status_enabled"
+ ],
+ "mongodbatlas": [
+ "organizations_api_access_list_required",
+ "projects_network_access_list_exposed_to_internet"
+ ],
+ "nhn": [
+ "compute_instance_security_groups"
+ ],
+ "openstack": [
+ "compute_instance_security_groups_attached",
+ "networking_port_security_disabled",
+ "networking_security_group_allows_all_ingress_from_internet",
+ "networking_security_group_allows_rdp_from_internet",
+ "networking_security_group_allows_ssh_from_internet"
+ ],
+ "oraclecloud": [
+ "network_default_security_list_restricts_traffic",
+ "network_security_group_ingress_from_internet_to_rdp_port",
+ "network_security_group_ingress_from_internet_to_ssh_port",
+ "network_security_list_ingress_from_internet_to_rdp_port",
+ "network_security_list_ingress_from_internet_to_ssh_port"
+ ],
+ "stackit": [
+ "iaas_security_group_all_traffic_unrestricted",
+ "iaas_security_group_database_unrestricted",
+ "iaas_security_group_rdp_unrestricted",
+ "iaas_security_group_ssh_unrestricted"
+ ],
+ "vercel": [
+ "security_custom_rules_configured",
+ "security_ip_blocking_rules_configured",
+ "security_waf_enabled"
+ ]
+ }
+ },
+ {
+ "id": "4.5",
+ "name": "Implement and Manage a Firewall on End-User Devices",
+ "description": "Implement and manage a host-based firewall or port-filtering tool on end-user devices, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "4.6",
+ "name": "Securely Manage Enterprise Assets and Software",
+ "description": "Securely manage enterprise assets and software. Example implementations include managing configuration through version-controlled Infrastructure-as-Code (IaC) and accessing administrative interfaces over secure network protocols, such as Secure Shell (SSH) and Hypertext Transfer Protocol Secure (HTTPS). Do not use insecure management protocols, such as Telnet (Teletype Network) and HTTP, unless operationally essential.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "oss_bucket_secure_transport_enabled",
+ "rds_instance_ssl_enabled"
+ ],
+ "aws": [
+ "autoscaling_group_launch_configuration_requires_imdsv2",
+ "ec2_instance_account_imdsv2_enabled",
+ "ec2_instance_imdsv2_enabled",
+ "ec2_instance_managed_by_ssm",
+ "ec2_launch_template_imdsv2_required"
+ ],
+ "azure": [
+ "app_client_certificates_on",
+ "app_ensure_http_is_redirected_to_https",
+ "storage_secure_transfer_required_is_enabled",
+ "vm_linux_enforce_ssh_authentication"
+ ],
+ "cloudflare": [
+ "zone_automatic_https_rewrites_enabled",
+ "zone_https_redirect_enabled",
+ "zone_min_tls_version_secure",
+ "zone_ssl_strict"
+ ],
+ "gcp": [
+ "compute_instance_block_project_wide_ssh_keys_disabled",
+ "compute_project_os_login_enabled"
+ ],
+ "kubernetes": [
+ "controllermanager_bind_address",
+ "scheduler_bind_address"
+ ],
+ "mongodbatlas": [
+ "clusters_tls_enabled"
+ ],
+ "openstack": [
+ "compute_instance_key_based_authentication"
+ ],
+ "oraclecloud": [
+ "compute_instance_legacy_metadata_endpoint_disabled"
+ ]
+ }
+ },
+ {
+ "id": "4.7",
+ "name": "Manage Default Accounts on Enterprise Assets and Software",
+ "description": "Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_no_root_access_key"
+ ],
+ "aws": [
+ "iam_avoid_root_usage",
+ "iam_no_root_access_key",
+ "iam_root_credentials_management_enabled",
+ "rds_cluster_default_admin",
+ "rds_instance_default_admin",
+ "redshift_cluster_non_default_username"
+ ],
+ "azure": [
+ "aks_cluster_local_accounts_disabled",
+ "containerregistry_admin_user_disabled",
+ "cosmosdb_account_use_aad_and_rbac",
+ "storage_account_key_access_disabled"
+ ],
+ "gcp": [
+ "compute_instance_default_service_account_in_use",
+ "compute_instance_default_service_account_in_use_with_full_api_access",
+ "gke_cluster_no_default_service_account"
+ ],
+ "kubernetes": [
+ "apiserver_anonymous_requests",
+ "kubelet_disable_anonymous_auth"
+ ],
+ "m365": [
+ "exchange_shared_mailbox_sign_in_disabled"
+ ],
+ "nhn": [
+ "compute_instance_login_user"
+ ],
+ "oraclecloud": [
+ "identity_tenancy_admin_users_no_api_keys"
+ ],
+ "scaleway": [
+ "iam_api_keys_no_root_owned"
+ ]
+ }
+ },
+ {
+ "id": "4.8",
+ "name": "Uninstall or Disable Unnecessary Services on Enterprise Assets and Software",
+ "description": "Uninstall or disable unnecessary services on enterprise assets and software, such as an unused file sharing service, web application module, or service function.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "cs_kubernetes_dashboard_disabled"
+ ],
+ "azure": [
+ "app_ftp_deployment_disabled",
+ "app_function_ftps_deployment_disabled"
+ ],
+ "gcp": [
+ "compute_instance_ip_forwarding_is_enabled",
+ "compute_instance_serial_ports_in_use"
+ ],
+ "googleworkspace": [
+ "chat_incoming_webhooks_disabled",
+ "drive_desktop_access_disabled",
+ "gmail_per_user_outbound_gateway_disabled",
+ "gmail_pop_imap_access_disabled",
+ "security_less_secure_apps_disabled",
+ "sites_service_disabled"
+ ],
+ "kubernetes": [
+ "apiserver_disable_profiling",
+ "controllermanager_disable_profiling",
+ "kubelet_disable_read_only_port",
+ "scheduler_profiling"
+ ],
+ "m365": [
+ "exchange_transport_config_smtp_auth_disabled",
+ "teams_email_sending_to_channel_disabled"
+ ],
+ "oraclecloud": [
+ "compute_instance_legacy_metadata_endpoint_disabled"
+ ],
+ "vercel": [
+ "project_auto_expose_system_env_disabled",
+ "project_directory_listing_disabled"
+ ]
+ }
+ },
+ {
+ "id": "4.9",
+ "name": "Configure Trusted DNS Servers on Enterprise Assets",
+ "description": "Configure trusted DNS servers on network infrastructure. Example implementations include configuring network devices to use enterprise-controlled DNS servers and/or reputable externally accessible DNS servers.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "cloudflare": [
+ "zone_dnssec_enabled"
+ ]
+ }
+ },
+ {
+ "id": "4.10",
+ "name": "Enforce Automatic Device Lockout on Portable End-User Devices",
+ "description": "Enforce automatic device lockout following a predetermined threshold of local failed authentication attempts on portable end-user devices, where supported. For laptops, do not allow more than 20 failed authentication attempts; for tablets and smartphones, no more than 10 failed authentication attempts. Example implementations include Microsoft® InTune Device Lock and Apple® Configuration Profile maxFailedAttempts.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "4.11",
+ "name": "Enforce Remote Wipe Capability on Portable End-User Devices",
+ "description": "Remotely wipe enterprise data from enterprise-owned portable end-user devices when deemed appropriate such as lost or stolen devices, or when an individual no longer supports the enterprise.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "4.12",
+ "name": "Separate Enterprise Workspaces on Mobile End-User Devices",
+ "description": "Ensure separate enterprise workspaces are used on mobile end-user devices, where supported. Example implementations include using an Apple® Configuration Profile or Android™ Work Profile to separate enterprise applications and data from personal applications and data.",
+ "attributes": {
+ "Section": "4. Secure Configuration of Enterprise Assets and Software",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "5.1",
+ "name": "Establish and Maintain an Inventory of Accounts",
+ "description": "Establish and maintain an inventory of all accounts managed in the enterprise. The inventory must at a minimum include user, administrator, and service accounts. The inventory, at a minimum, should contain the person's name, username, start/stop dates, and department. Validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Identify",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "5.2",
+ "name": "Use Unique Passwords",
+ "description": "Use unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-character password for accounts using Multi-Factor Authentication (MFA) and a 14-character password for accounts not using MFA.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_password_policy_lowercase",
+ "ram_password_policy_minimum_length",
+ "ram_password_policy_number",
+ "ram_password_policy_password_reuse_prevention",
+ "ram_password_policy_symbol",
+ "ram_password_policy_uppercase"
+ ],
+ "aws": [
+ "cognito_user_pool_password_policy_lowercase",
+ "cognito_user_pool_password_policy_minimum_length_14",
+ "cognito_user_pool_password_policy_number",
+ "cognito_user_pool_password_policy_symbol",
+ "cognito_user_pool_password_policy_uppercase",
+ "iam_password_policy_lowercase",
+ "iam_password_policy_minimum_length_14",
+ "iam_password_policy_number",
+ "iam_password_policy_reuse_24",
+ "iam_password_policy_symbol",
+ "iam_password_policy_uppercase"
+ ],
+ "googleworkspace": [
+ "security_password_policy_strong"
+ ],
+ "okta": [
+ "authenticator_password_common_password_check",
+ "authenticator_password_complexity_lowercase",
+ "authenticator_password_complexity_number",
+ "authenticator_password_complexity_symbol",
+ "authenticator_password_complexity_uppercase",
+ "authenticator_password_history_5",
+ "authenticator_password_minimum_length_15"
+ ],
+ "oraclecloud": [
+ "identity_password_policy_minimum_length_14",
+ "identity_password_policy_prevents_reuse"
+ ]
+ }
+ },
+ {
+ "id": "5.3",
+ "name": "Disable Dormant Accounts",
+ "description": "Delete or disable any dormant accounts after a period of 45 days of inactivity, where supported.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_user_console_access_unused"
+ ],
+ "aws": [
+ "iam_user_accesskey_unused",
+ "iam_user_console_access_unused"
+ ],
+ "azure": [
+ "entra_user_with_recent_sign_in"
+ ],
+ "gcp": [
+ "iam_sa_user_managed_key_unused",
+ "iam_service_account_unused"
+ ],
+ "okta": [
+ "user_inactivity_automation_35d_enabled"
+ ],
+ "vercel": [
+ "authentication_no_stale_tokens"
+ ]
+ }
+ },
+ {
+ "id": "5.4",
+ "name": "Restrict Administrator Privileges to Dedicated Administrator Accounts",
+ "description": "Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_policy_no_administrative_privileges"
+ ],
+ "aws": [
+ "iam_aws_attached_policy_no_administrative_privileges",
+ "iam_customer_attached_policy_no_administrative_privileges",
+ "iam_group_administrator_access_policy",
+ "iam_inline_policy_no_administrative_privileges",
+ "iam_role_administratoraccess_policy",
+ "iam_user_administrator_access_policy"
+ ],
+ "azure": [
+ "app_function_identity_without_admin_privileges",
+ "entra_global_admin_in_less_than_five_users",
+ "iam_role_user_access_admin_restricted",
+ "iam_subscription_roles_owner_custom_not_created"
+ ],
+ "gcp": [
+ "iam_sa_no_administrative_privileges"
+ ],
+ "googleworkspace": [
+ "directory_super_admin_count",
+ "directory_super_admin_only_admin_roles"
+ ],
+ "kubernetes": [
+ "rbac_cluster_admin_usage"
+ ],
+ "m365": [
+ "admincenter_users_admins_reduced_license_footprint",
+ "admincenter_users_between_two_and_four_global_admins",
+ "entra_admin_portals_access_restriction",
+ "entra_admin_users_cloud_only"
+ ],
+ "okta": [
+ "apitoken_not_super_admin"
+ ],
+ "oraclecloud": [
+ "identity_iam_admins_cannot_update_tenancy_admins",
+ "identity_service_level_admins_exist",
+ "identity_tenancy_admin_permissions_limited",
+ "identity_tenancy_admin_users_no_api_keys"
+ ],
+ "scaleway": [
+ "iam_api_keys_no_root_owned"
+ ],
+ "vercel": [
+ "team_member_role_least_privilege"
+ ]
+ }
+ },
+ {
+ "id": "5.5",
+ "name": "Establish and Maintain an Inventory of Service Accounts",
+ "description": "Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Identify",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "5.6",
+ "name": "Centralize Account Management",
+ "description": "Centralize account management through a directory or identity service.",
+ "attributes": {
+ "Section": "5. Account Management",
+ "Function": "Govern",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "iam_check_saml_providers_sts"
+ ],
+ "azure": [
+ "cosmosdb_account_use_aad_and_rbac",
+ "postgresql_flexible_server_entra_id_authentication_enabled",
+ "sqlserver_azuread_administrator_enabled",
+ "storage_default_to_entra_authorization_enabled"
+ ],
+ "vercel": [
+ "team_directory_sync_enabled",
+ "team_saml_sso_enabled"
+ ]
+ }
+ },
+ {
+ "id": "6.1",
+ "name": "Establish an Access Granting Process",
+ "description": "Establish and follow a documented process, preferably automated, for granting access to enterprise assets upon new hire or role change of a user.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "vercel": [
+ "team_directory_sync_enabled"
+ ]
+ }
+ },
+ {
+ "id": "6.2",
+ "name": "Establish an Access Revoking Process",
+ "description": "Establish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user. Disabling accounts, instead of deleting accounts, may be necessary to preserve audit trails.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "vercel": [
+ "team_directory_sync_enabled"
+ ]
+ }
+ },
+ {
+ "id": "6.3",
+ "name": "Require MFA for Externally-Exposed Applications",
+ "description": "Require all externally-exposed enterprise or third-party applications to enforce MFA, where supported. Enforcing MFA through a directory service or SSO provider is a satisfactory implementation of this Safeguard.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_user_mfa_enabled_console_access"
+ ],
+ "aws": [
+ "cognito_user_pool_mfa_enabled",
+ "iam_user_hardware_mfa_enabled",
+ "iam_user_mfa_enabled_console_access"
+ ],
+ "azure": [
+ "entra_authentication_methods_policy_strong_auth_enforced",
+ "entra_non_privileged_user_has_mfa",
+ "entra_security_defaults_enabled"
+ ],
+ "github": [
+ "organization_members_mfa_required"
+ ],
+ "googleworkspace": [
+ "security_2sv_enforced",
+ "security_advanced_protection_configured"
+ ],
+ "linode": [
+ "administration_user_2fa_enabled"
+ ],
+ "m365": [
+ "entra_conditional_access_policy_mfa_enforced_for_guest_users",
+ "entra_users_mfa_capable",
+ "entra_users_mfa_enabled"
+ ],
+ "mongodbatlas": [
+ "organizations_mfa_required"
+ ],
+ "okta": [
+ "application_dashboard_mfa_required",
+ "application_dashboard_phishing_resistant_authentication"
+ ],
+ "oraclecloud": [
+ "identity_user_mfa_enabled_console_access"
+ ]
+ }
+ },
+ {
+ "id": "6.4",
+ "name": "Require MFA for Remote Network Access",
+ "description": "Require MFA for remote network access.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "directoryservice_radius_server_security_protocol",
+ "directoryservice_supported_mfa_radius_enabled"
+ ],
+ "azure": [
+ "entra_user_with_vm_access_has_mfa",
+ "entra_security_defaults_enabled",
+ "entra_non_privileged_user_has_mfa"
+ ],
+ "gcp": [
+ "compute_project_os_login_2fa_enabled"
+ ],
+ "github": [
+ "organization_members_mfa_required"
+ ],
+ "linode": [
+ "administration_user_2fa_enabled"
+ ],
+ "m365": [
+ "entra_users_mfa_enabled",
+ "entra_legacy_authentication_blocked"
+ ],
+ "mongodbatlas": [
+ "organizations_mfa_required"
+ ]
+ }
+ },
+ {
+ "id": "6.5",
+ "name": "Require MFA for Administrative Access",
+ "description": "Require MFA for all administrative access accounts, where supported, on all enterprise assets, whether managed on-site or through a service provider.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ram_user_mfa_enabled_console_access"
+ ],
+ "aws": [
+ "iam_administrator_access_with_mfa",
+ "iam_root_hardware_mfa_enabled",
+ "iam_root_mfa_enabled"
+ ],
+ "azure": [
+ "entra_conditional_access_policy_require_mfa_for_admin_portals",
+ "entra_conditional_access_policy_require_mfa_for_management_api",
+ "entra_privileged_user_has_mfa",
+ "entra_user_with_vm_access_has_mfa"
+ ],
+ "github": [
+ "organization_members_mfa_required"
+ ],
+ "googleworkspace": [
+ "security_2sv_hardware_keys_admins"
+ ],
+ "linode": [
+ "administration_user_2fa_enabled"
+ ],
+ "m365": [
+ "entra_admin_users_mfa_enabled",
+ "entra_admin_users_phishing_resistant_mfa_enabled",
+ "entra_break_glass_account_fido2_security_key_registered"
+ ],
+ "mongodbatlas": [
+ "organizations_mfa_required"
+ ],
+ "okta": [
+ "application_admin_console_mfa_required",
+ "application_admin_console_phishing_resistant_authentication"
+ ],
+ "vercel": [
+ "team_saml_sso_enforced",
+ "team_saml_sso_enabled"
+ ]
+ }
+ },
+ {
+ "id": "6.6",
+ "name": "Establish and Maintain an Inventory of Authentication and Authorization Systems",
+ "description": "Establish and maintain an inventory of the enterprise's authentication and authorization systems, including those hosted on-site or at a remote service provider. Review and update the inventory, at a minimum, annually, or more frequently.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "6.7",
+ "name": "Centralize Access Control",
+ "description": "Centralize access control for all enterprise assets through a directory service or SSO provider, where supported.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "dms_endpoint_neptune_iam_authorization_enabled",
+ "iam_check_saml_providers_sts",
+ "neptune_cluster_iam_authentication_enabled",
+ "opensearch_service_domains_use_cognito_authentication_for_kibana",
+ "rds_cluster_iam_authentication_enabled",
+ "rds_instance_iam_authentication_enabled",
+ "sagemaker_domain_sso_configured"
+ ],
+ "azure": [
+ "aks_cluster_local_accounts_disabled",
+ "cosmosdb_account_use_aad_and_rbac",
+ "postgresql_flexible_server_entra_id_authentication_enabled",
+ "sqlserver_azuread_administrator_enabled"
+ ],
+ "m365": [
+ "entra_all_apps_conditional_access_coverage",
+ "entra_conditional_access_policy_all_apps_all_users",
+ "entra_password_hash_sync_enabled"
+ ],
+ "vercel": [
+ "team_directory_sync_enabled",
+ "team_saml_sso_enabled",
+ "team_saml_sso_enforced"
+ ]
+ }
+ },
+ {
+ "id": "6.8",
+ "name": "Define and Maintain Role-Based Access Control",
+ "description": "Define and maintain role-based access control, through determining and documenting the access rights necessary for each role within the enterprise to successfully carry out its assigned duties. Perform access control reviews of enterprise assets to validate that all privileges are authorized, on a recurring schedule at a minimum annually, or more frequently.",
+ "attributes": {
+ "Section": "6. Access Control Management",
+ "Function": "Govern",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "cs_kubernetes_rbac_enabled",
+ "ram_policy_attached_only_to_group_or_roles",
+ "ram_policy_no_administrative_privileges"
+ ],
+ "aws": [
+ "accessanalyzer_enabled",
+ "accessanalyzer_enabled_without_findings",
+ "bedrock_agent_role_least_privilege",
+ "bedrock_api_key_no_administrative_privileges",
+ "ec2_instance_profile_attached",
+ "iam_inline_policy_allows_privilege_escalation",
+ "iam_inline_policy_no_full_access_to_cloudtrail",
+ "iam_inline_policy_no_full_access_to_kms",
+ "iam_inline_policy_no_wildcard_marketplace_subscribe",
+ "iam_no_custom_policy_permissive_role_assumption",
+ "iam_policy_allows_privilege_escalation",
+ "iam_policy_no_full_access_to_cloudtrail",
+ "iam_policy_no_full_access_to_kms",
+ "iam_policy_no_wildcard_marketplace_subscribe",
+ "iam_role_cross_account_readonlyaccess_policy",
+ "iam_role_cross_service_confused_deputy_prevention",
+ "iam_user_with_temporary_credentials"
+ ],
+ "azure": [
+ "aks_cluster_rbac_enabled",
+ "cosmosdb_account_use_aad_and_rbac",
+ "entra_policy_default_users_cannot_create_security_groups",
+ "entra_policy_ensure_default_user_cannot_create_apps",
+ "iam_role_user_access_admin_restricted",
+ "iam_subscription_roles_owner_custom_not_created",
+ "keyvault_rbac_enabled"
+ ],
+ "gcp": [
+ "iam_account_access_approval_enabled",
+ "iam_no_service_roles_at_project_level",
+ "iam_role_kms_enforce_separation_of_duties",
+ "iam_role_sa_enforce_separation_of_duties",
+ "iam_sa_no_administrative_privileges"
+ ],
+ "github": [
+ "organization_default_repository_permission_strict",
+ "organization_repository_creation_limited",
+ "organization_repository_deletion_limited"
+ ],
+ "kubernetes": [
+ "apiserver_auth_mode_include_node",
+ "apiserver_auth_mode_include_rbac",
+ "apiserver_auth_mode_not_always_allow",
+ "controllermanager_service_account_credentials",
+ "kubelet_authorization_mode",
+ "rbac_minimize_csr_approval_access",
+ "rbac_minimize_node_proxy_subresource_access",
+ "rbac_minimize_pod_creation_access",
+ "rbac_minimize_pv_creation_access",
+ "rbac_minimize_service_account_token_creation",
+ "rbac_minimize_webhook_config_access",
+ "rbac_minimize_wildcard_use_roles"
+ ],
+ "m365": [
+ "entra_admin_portals_access_restriction",
+ "entra_app_registration_no_unused_privileged_permissions",
+ "entra_policy_guest_users_access_restrictions",
+ "entra_service_principal_privileged_role_no_owners"
+ ],
+ "oraclecloud": [
+ "identity_no_resources_in_root_compartment",
+ "identity_non_root_compartment_exists",
+ "identity_service_level_admins_exist",
+ "identity_storage_service_level_admins_scoped",
+ "identity_tenancy_admin_permissions_limited"
+ ],
+ "vercel": [
+ "team_member_role_least_privilege"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "7.1",
+ "name": "Establish and Maintain a Vulnerability Management Process",
+ "description": "Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "7.2",
+ "name": "Establish and Maintain a Remediation Process",
+ "description": "Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "7.3",
+ "name": "Perform Automated Operating System Patch Management",
+ "description": "Perform operating system updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ecs_instance_latest_os_patches_applied"
+ ],
+ "aws": [
+ "ssm_managed_compliant_patching"
+ ],
+ "azure": [
+ "aks_cluster_auto_upgrade_enabled",
+ "defender_ensure_system_updates_are_applied"
+ ]
+ }
+ },
+ {
+ "id": "7.4",
+ "name": "Perform Automated Application Patch Management",
+ "description": "Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "dms_instance_minor_version_upgrade_enabled",
+ "elasticache_redis_cluster_auto_minor_version_upgrades",
+ "elasticbeanstalk_environment_managed_updates_enabled",
+ "memorydb_cluster_auto_minor_version_upgrades",
+ "mq_broker_auto_minor_version_upgrades",
+ "rds_cluster_minor_version_upgrade_enabled",
+ "rds_instance_minor_version_upgrade_enabled",
+ "redshift_cluster_automatic_upgrades"
+ ],
+ "azure": [
+ "app_ensure_java_version_is_latest",
+ "app_ensure_php_version_is_latest",
+ "app_ensure_python_version_is_latest",
+ "app_function_latest_runtime_version"
+ ]
+ }
+ },
+ {
+ "id": "7.5",
+ "name": "Perform Automated Vulnerability Scans of Internal Enterprise Assets",
+ "description": "Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "securitycenter_vulnerability_scan_enabled"
+ ],
+ "aws": [
+ "ecr_registry_scan_images_on_push_enabled",
+ "ecr_repositories_scan_images_on_push_enabled",
+ "ecr_repositories_scan_vulnerabilities_in_latest_image",
+ "inspector2_is_enabled"
+ ],
+ "azure": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
+ "defender_container_images_scan_enabled",
+ "sqlserver_va_emails_notifications_admins_enabled",
+ "sqlserver_va_periodic_recurring_scans_enabled",
+ "sqlserver_va_scan_reports_configured",
+ "sqlserver_vulnerability_assessment_enabled"
+ ],
+ "gcp": [
+ "artifacts_container_analysis_enabled",
+ "gcr_container_scanning_enabled"
+ ],
+ "github": [
+ "repository_dependency_scanning_enabled"
+ ]
+ }
+ },
+ {
+ "id": "7.6",
+ "name": "Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets",
+ "description": "Perform automated vulnerability scans of externally-exposed enterprise assets. Perform scans on a monthly, or more frequent, basis.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "inspector2_is_enabled"
+ ],
+ "azure": [
+ "network_public_ip_shodan"
+ ]
+ }
+ },
+ {
+ "id": "7.7",
+ "name": "Remediate Detected Vulnerabilities",
+ "description": "Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.",
+ "attributes": {
+ "Section": "7. Continuous Vulnerability Management",
+ "Function": "Respond",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "inspector2_active_findings_exist"
+ ],
+ "azure": [
+ "defender_container_images_resolved_vulnerabilities"
+ ]
+ }
+ },
+ {
+ "id": "8.1",
+ "name": "Establish and Maintain an Audit Log Management Process",
+ "description": "Establish and maintain a documented audit log management process that defines the enterprise's logging requirements. At a minimum, address the collection, review, and retention of audit logs for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "8.2",
+ "name": "Collect Audit Logs",
+ "description": "Collect audit logs. Ensure that logging, per the enterprise's audit log management process, has been enabled across enterprise assets.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "actiontrail_multi_region_enabled",
+ "cs_kubernetes_log_service_enabled",
+ "oss_bucket_logging_enabled",
+ "rds_instance_sql_audit_enabled",
+ "vpc_flow_logs_enabled"
+ ],
+ "aws": [
+ "apigateway_restapi_logging_enabled",
+ "apigatewayv2_api_access_logging_enabled",
+ "appsync_field_level_logging_enabled",
+ "athena_workgroup_logging_enabled",
+ "awslambda_function_invoke_api_operations_cloudtrail_logging_enabled",
+ "bedrock_model_invocation_logging_enabled",
+ "cloudfront_distributions_logging_enabled",
+ "cloudtrail_bedrock_logging_enabled",
+ "cloudtrail_cloudwatch_logging_enabled",
+ "cloudtrail_logs_s3_bucket_access_logging_enabled",
+ "cloudtrail_multi_region_enabled",
+ "cloudtrail_multi_region_enabled_logging_management_events",
+ "codebuild_project_logging_enabled",
+ "config_recorder_all_regions_enabled",
+ "datasync_task_logging_enabled",
+ "directoryservice_directory_log_forwarding_enabled",
+ "dms_replication_task_source_logging_enabled",
+ "dms_replication_task_target_logging_enabled",
+ "documentdb_cluster_cloudwatch_log_export",
+ "ec2_client_vpn_endpoint_connection_logging_enabled",
+ "ecs_task_definitions_logging_enabled",
+ "eks_control_plane_logging_all_types_enabled",
+ "elasticbeanstalk_environment_cloudwatch_logging_enabled",
+ "elb_logging_enabled",
+ "elbv2_logging_enabled",
+ "mq_broker_logging_enabled",
+ "neptune_cluster_integration_cloudwatch_logs",
+ "networkfirewall_logging_enabled",
+ "opensearch_service_domains_cloudwatch_logging_enabled",
+ "rds_cluster_integration_cloudwatch_logs",
+ "rds_instance_integration_cloudwatch_logs",
+ "redshift_cluster_audit_logging",
+ "s3_bucket_server_access_logging_enabled",
+ "stepfunctions_statemachine_logging_enabled",
+ "vpc_flow_logs_enabled",
+ "waf_global_webacl_logging_enabled",
+ "wafv2_webacl_logging_enabled"
+ ],
+ "azure": [
+ "app_function_application_insights_enabled",
+ "app_http_logs_enabled",
+ "appinsights_ensure_is_configured",
+ "defender_auto_provisioning_log_analytics_agent_vms_on",
+ "keyvault_logging_enabled",
+ "monitor_diagnostic_settings_exists",
+ "mysql_flexible_server_audit_log_enabled",
+ "network_flow_log_captured_sent",
+ "postgresql_flexible_server_log_checkpoints_on",
+ "postgresql_flexible_server_log_connections_on",
+ "sqlserver_auditing_enabled"
+ ],
+ "gcp": [
+ "cloudstorage_audit_logs_enabled",
+ "cloudstorage_bucket_logging_enabled",
+ "compute_loadbalancer_logging_enabled",
+ "iam_audit_logs_enabled",
+ "logging_sink_created"
+ ],
+ "googleworkspace": [
+ "gmail_comprehensive_mail_storage_enabled"
+ ],
+ "kubernetes": [
+ "apiserver_audit_log_path_set"
+ ],
+ "m365": [
+ "exchange_mailbox_audit_bypass_disabled",
+ "exchange_organization_mailbox_auditing_enabled",
+ "exchange_user_mailbox_auditing_enabled",
+ "purview_audit_log_search_enabled"
+ ],
+ "mongodbatlas": [
+ "projects_auditing_enabled"
+ ],
+ "okta": [
+ "systemlog_streaming_enabled"
+ ],
+ "oraclecloud": [
+ "network_vcn_subnet_flow_logs_enabled",
+ "objectstorage_bucket_logging_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "8.3",
+ "name": "Ensure Adequate Audit Log Storage",
+ "description": "Ensure that logging destinations maintain adequate storage to comply with the enterprise's audit log management process.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "kubernetes": [
+ "apiserver_audit_log_maxbackup_set",
+ "apiserver_audit_log_maxsize_set"
+ ]
+ }
+ },
+ {
+ "id": "8.4",
+ "name": "Standardize Time Synchronization",
+ "description": "Standardize time synchronization. Configure at least two synchronized time sources across enterprise assets, where supported.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "8.5",
+ "name": "Collect Detailed Audit Logs",
+ "description": "Configure detailed audit logging for enterprise assets containing sensitive data. Include event source, date, username, timestamp, source addresses, destination addresses, and other useful elements that could assist in a forensic investigation.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "rds_instance_postgresql_log_connections_enabled",
+ "rds_instance_postgresql_log_disconnections_enabled",
+ "rds_instance_postgresql_log_duration_enabled"
+ ],
+ "aws": [
+ "cloudtrail_s3_dataevents_read_enabled",
+ "cloudtrail_s3_dataevents_write_enabled",
+ "opensearch_service_domains_audit_logging_enabled"
+ ],
+ "azure": [
+ "monitor_diagnostic_setting_with_appropriate_categories",
+ "mysql_flexible_server_audit_log_connection_activated",
+ "postgresql_flexible_server_log_connections_on",
+ "postgresql_flexible_server_log_disconnections_on"
+ ],
+ "gcp": [
+ "cloudsql_instance_postgres_enable_pgaudit_flag",
+ "cloudsql_instance_postgres_log_connections_flag",
+ "cloudsql_instance_postgres_log_disconnections_flag",
+ "cloudsql_instance_postgres_log_error_verbosity_flag",
+ "cloudsql_instance_postgres_log_min_duration_statement_flag",
+ "cloudsql_instance_postgres_log_min_error_statement_flag",
+ "cloudsql_instance_postgres_log_min_messages_flag",
+ "cloudsql_instance_postgres_log_statement_flag"
+ ],
+ "m365": [
+ "exchange_user_mailbox_auditing_enabled"
+ ],
+ "mongodbatlas": [
+ "projects_auditing_enabled"
+ ]
+ }
+ },
+ {
+ "id": "8.6",
+ "name": "Collect DNS Query Audit Logs",
+ "description": "Collect DNS query audit logs on enterprise assets, where appropriate and supported.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "route53_public_hosted_zones_cloudwatch_logging_enabled"
+ ],
+ "gcp": [
+ "compute_network_dns_logging_enabled"
+ ]
+ }
+ },
+ {
+ "id": "8.7",
+ "name": "Collect URL Request Audit Logs",
+ "description": "Collect URL request audit logs on enterprise assets, where appropriate and supported.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "app_http_logs_enabled"
+ ],
+ "gcp": [
+ "compute_loadbalancer_logging_enabled"
+ ]
+ }
+ },
+ {
+ "id": "8.8",
+ "name": "Collect Command-Line Audit Logs",
+ "description": "Collect command-line audit logs. Example implementations include collecting audit logs from PowerShell®, BASH™, and remote administrative terminals.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "8.9",
+ "name": "Centralize Audit Logs",
+ "description": "Centralize, to the extent possible, audit log collection and retention across enterprise assets in accordance with the documented audit log management process. Example implementations primarily include leveraging a SIEM tool to centralize multiple log sources.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "cloudtrail_cloudwatch_logging_enabled",
+ "config_delegated_admin_and_org_aggregator_all_regions"
+ ],
+ "azure": [
+ "defender_auto_provisioning_log_analytics_agent_vms_on",
+ "network_flow_log_captured_sent"
+ ],
+ "gcp": [
+ "logging_sink_created"
+ ],
+ "m365": [
+ "purview_audit_log_search_enabled"
+ ],
+ "okta": [
+ "systemlog_streaming_enabled"
+ ]
+ }
+ },
+ {
+ "id": "8.10",
+ "name": "Retain Audit Logs",
+ "description": "Retain audit logs across enterprise assets for a minimum of 90 days.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "rds_instance_sql_audit_retention",
+ "sls_logstore_retention_period"
+ ],
+ "aws": [
+ "cloudwatch_log_group_retention_policy_specific_days_enabled"
+ ],
+ "azure": [
+ "network_flow_log_more_than_90_days",
+ "postgresql_flexible_server_log_retention_days_greater_3",
+ "sqlserver_auditing_retention_90_days"
+ ],
+ "gcp": [
+ "cloudstorage_bucket_log_retention_policy_lock"
+ ],
+ "kubernetes": [
+ "apiserver_audit_log_maxage_set"
+ ],
+ "m365": [
+ "exchange_user_mailbox_auditing_enabled"
+ ],
+ "oraclecloud": [
+ "audit_log_retention_period_365_days"
+ ]
+ }
+ },
+ {
+ "id": "8.11",
+ "name": "Conduct Audit Log Reviews",
+ "description": "Conduct reviews of audit logs to detect anomalies or abnormal events that could indicate a potential threat. Conduct reviews on a weekly, or more frequent, basis.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "sls_cloud_firewall_changes_alert_enabled",
+ "sls_customer_created_cmk_changes_alert_enabled",
+ "sls_management_console_authentication_failures_alert_enabled",
+ "sls_management_console_signin_without_mfa_alert_enabled",
+ "sls_oss_bucket_policy_changes_alert_enabled",
+ "sls_oss_permission_changes_alert_enabled",
+ "sls_ram_role_changes_alert_enabled",
+ "sls_rds_instance_configuration_changes_alert_enabled",
+ "sls_root_account_usage_alert_enabled",
+ "sls_security_group_changes_alert_enabled",
+ "sls_unauthorized_api_calls_alert_enabled",
+ "sls_vpc_changes_alert_enabled",
+ "sls_vpc_network_route_changes_alert_enabled"
+ ],
+ "aws": [
+ "cloudtrail_insights_exist",
+ "cloudwatch_changes_to_network_acls_alarm_configured",
+ "cloudwatch_changes_to_network_gateways_alarm_configured",
+ "cloudwatch_changes_to_network_route_tables_alarm_configured",
+ "cloudwatch_changes_to_vpcs_alarm_configured",
+ "cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled",
+ "cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled",
+ "cloudwatch_log_metric_filter_authentication_failures",
+ "cloudwatch_log_metric_filter_aws_organizations_changes",
+ "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk",
+ "cloudwatch_log_metric_filter_for_s3_bucket_policy_changes",
+ "cloudwatch_log_metric_filter_policy_changes",
+ "cloudwatch_log_metric_filter_root_usage",
+ "cloudwatch_log_metric_filter_security_group_changes",
+ "cloudwatch_log_metric_filter_sign_in_without_mfa",
+ "cloudwatch_log_metric_filter_unauthorized_api_calls"
+ ],
+ "azure": [
+ "monitor_alert_create_policy_assignment",
+ "monitor_alert_create_update_nsg",
+ "monitor_alert_create_update_public_ip_address_rule",
+ "monitor_alert_create_update_security_solution",
+ "monitor_alert_create_update_sqlserver_fr",
+ "monitor_alert_delete_nsg",
+ "monitor_alert_delete_policy_assignment",
+ "monitor_alert_delete_public_ip_address_rule",
+ "monitor_alert_delete_security_solution",
+ "monitor_alert_delete_sqlserver_fr",
+ "monitor_alert_service_health_exists"
+ ],
+ "gcp": [
+ "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled"
+ ],
+ "googleworkspace": [
+ "rules_admin_privilege_granted_alert_configured",
+ "rules_gmail_employee_spoofing_alert_configured",
+ "rules_government_backed_attacks_alert_configured",
+ "rules_leaked_password_alert_configured",
+ "rules_password_changed_alert_configured",
+ "rules_suspicious_activity_suspension_alert_configured",
+ "rules_suspicious_login_alert_configured",
+ "rules_suspicious_programmatic_login_alert_configured"
+ ],
+ "oraclecloud": [
+ "events_rule_cloudguard_problems",
+ "events_rule_iam_group_changes",
+ "events_rule_iam_policy_changes",
+ "events_rule_identity_provider_changes",
+ "events_rule_idp_group_mapping_changes",
+ "events_rule_local_user_authentication",
+ "events_rule_network_gateway_changes",
+ "events_rule_network_security_group_changes",
+ "events_rule_route_table_changes",
+ "events_rule_security_list_changes",
+ "events_rule_user_changes",
+ "events_rule_vcn_changes"
+ ]
+ }
+ },
+ {
+ "id": "8.12",
+ "name": "Collect Service Provider Logs",
+ "description": "Collect service provider logs, where supported. Example implementations include collecting authentication and authorization events, data creation and disposal events, and user management events.",
+ "attributes": {
+ "Section": "8. Audit Log Management",
+ "Function": "Detect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "actiontrail_multi_region_enabled"
+ ],
+ "aws": [
+ "cloudtrail_multi_region_enabled",
+ "cloudtrail_multi_region_enabled_logging_management_events"
+ ],
+ "azure": [
+ "monitor_diagnostic_settings_exists"
+ ],
+ "gcp": [
+ "iam_audit_logs_enabled"
+ ],
+ "m365": [
+ "purview_audit_log_search_enabled"
+ ],
+ "okta": [
+ "systemlog_streaming_enabled"
+ ]
+ }
+ },
+ {
+ "id": "9.1",
+ "name": "Ensure Use of Only Fully Supported Browsers and Email Clients",
+ "description": "Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "9.2",
+ "name": "Use DNS Filtering Services",
+ "description": "Use DNS filtering services on all end-user devices, including remote and on-premises assets, to block access to known malicious domains.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "9.3",
+ "name": "Maintain and Enforce Network-Based URL Filters",
+ "description": "Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "googleworkspace": [
+ "gmail_shortener_scanning_enabled",
+ "gmail_untrusted_link_warnings_enabled"
+ ],
+ "m365": [
+ "defender_safelinks_policy_enabled"
+ ]
+ }
+ },
+ {
+ "id": "9.4",
+ "name": "Restrict Unnecessary or Unauthorized Browser and Email Client Extensions",
+ "description": "Restrict, either through uninstalling or disabling, any unauthorized or unnecessary browser or email client plugins, extensions, and add-on applications.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "m365": [
+ "exchange_mailbox_policy_additional_storage_restricted",
+ "exchange_roles_assignment_policy_addins_disabled"
+ ]
+ }
+ },
+ {
+ "id": "9.5",
+ "name": "Implement DMARC",
+ "description": "To lower the chance of spoofed or modified emails from valid domains, implement DMARC policy and verification, starting with implementing the Sender Policy Framework (SPF) and the DomainKeys Identified Mail (DKIM) standards.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "ses_identity_dkim_enabled"
+ ],
+ "cloudflare": [
+ "zone_record_dkim_exists",
+ "zone_record_dmarc_exists",
+ "zone_record_spf_exists"
+ ],
+ "googleworkspace": [
+ "gmail_groups_spoofing_protection_enabled",
+ "gmail_inbound_domain_spoofing_protection_enabled",
+ "gmail_unauthenticated_email_protection_enabled"
+ ],
+ "m365": [
+ "defender_antiphishing_policy_configured",
+ "defender_domain_dkim_enabled"
+ ]
+ }
+ },
+ {
+ "id": "9.6",
+ "name": "Block Unnecessary File Types",
+ "description": "Block unnecessary file types attempting to enter the enterprise's email gateway.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "googleworkspace": [
+ "gmail_anomalous_attachment_protection_enabled",
+ "gmail_script_attachment_protection_enabled"
+ ],
+ "m365": [
+ "defender_malware_policy_common_attachments_filter_enabled",
+ "defender_malware_policy_comprehensive_attachments_filter_applied"
+ ]
+ }
+ },
+ {
+ "id": "9.7",
+ "name": "Deploy and Maintain Email Server Anti-Malware Protections",
+ "description": "Deploy and maintain email server anti-malware protections, such as attachment scanning and/or sandboxing.",
+ "attributes": {
+ "Section": "9. Email and Web Browser Protections",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "googleworkspace": [
+ "gmail_encrypted_attachment_protection_enabled",
+ "gmail_enhanced_pre_delivery_scanning_enabled",
+ "gmail_external_image_scanning_enabled"
+ ],
+ "m365": [
+ "defender_atp_safe_attachments_and_docs_configured",
+ "defender_malware_policy_notifications_internal_users_malware_enabled",
+ "defender_safe_attachments_policy_enabled"
+ ]
+ }
+ },
+ {
+ "id": "10.1",
+ "name": "Deploy and Maintain Anti-Malware Software",
+ "description": "Deploy and maintain anti-malware software on all enterprise assets.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "ecs_instance_endpoint_protection_installed",
+ "securitycenter_all_assets_agent_installed"
+ ],
+ "aws": [
+ "guardduty_ec2_malware_protection_enabled"
+ ],
+ "azure": [
+ "defender_assessments_vm_endpoint_protection_installed",
+ "defender_ensure_defender_for_server_is_on"
+ ],
+ "m365": [
+ "defender_atp_safe_attachments_and_docs_configured",
+ "defender_malware_policy_common_attachments_filter_enabled",
+ "defender_safe_attachments_policy_enabled",
+ "defender_zap_for_teams_enabled"
+ ]
+ }
+ },
+ {
+ "id": "10.2",
+ "name": "Configure Automatic Anti-Malware Signature Updates",
+ "description": "Configure automatic updates for anti-malware signature files on all enterprise assets.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "10.3",
+ "name": "Disable Autorun and Autoplay for Removable Media",
+ "description": "Disable autorun and autoplay auto-execute functionality for removable media.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "10.4",
+ "name": "Configure Automatic Anti-Malware Scanning of Removable Media",
+ "description": "Configure anti-malware software to automatically scan removable media.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "10.5",
+ "name": "Enable Anti-Exploitation Features",
+ "description": "Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "vm_trusted_launch_enabled"
+ ],
+ "openstack": [
+ "image_secure_boot_enabled"
+ ],
+ "oraclecloud": [
+ "compute_instance_secure_boot_enabled"
+ ]
+ }
+ },
+ {
+ "id": "10.6",
+ "name": "Centrally Manage Anti-Malware Software",
+ "description": "Centrally manage anti-malware software.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "securitycenter_advanced_or_enterprise_edition",
+ "securitycenter_all_assets_agent_installed"
+ ],
+ "aws": [
+ "guardduty_centrally_managed",
+ "guardduty_delegated_admin_enabled_all_regions"
+ ],
+ "azure": [
+ "aks_cluster_defender_enabled",
+ "defender_ensure_defender_for_containers_is_on",
+ "defender_ensure_defender_for_storage_is_on"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_delegated_admin_enabled_all_regions",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "10.7",
+ "name": "Use Behavior-Based Anti-Malware Software",
+ "description": "Use behavior-based anti-malware software.",
+ "attributes": {
+ "Section": "10. Malware Defenses",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "cloudtrail_threat_detection_enumeration",
+ "cloudtrail_threat_detection_llm_jacking",
+ "cloudtrail_threat_detection_privilege_escalation",
+ "guardduty_eks_runtime_monitoring_enabled",
+ "guardduty_is_enabled",
+ "guardduty_lambda_protection_enabled",
+ "guardduty_rds_protection_enabled",
+ "guardduty_s3_protection_enabled"
+ ],
+ "azure": [
+ "defender_ensure_mcas_is_enabled",
+ "defender_ensure_wdatp_is_enabled"
+ ],
+ "m365": [
+ "defender_atp_safe_attachments_and_docs_configured",
+ "defender_safe_attachments_policy_enabled",
+ "defender_zap_for_teams_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "11.1",
+ "name": "Establish and Maintain a Data Recovery Process",
+ "description": "Establish and maintain a documented data recovery process that includes detailed backup procedures. In the process, address the scope of data recovery activities, recovery prioritization, and the security of backup data. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "11. Data Recovery",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "11.2",
+ "name": "Perform Automated Backups",
+ "description": "Perform automated backups of in-scope enterprise assets. Run backups weekly, or more frequently, based on the sensitivity of the data.",
+ "attributes": {
+ "Section": "11. Data Recovery",
+ "Function": "Recover",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "backup_plans_exist",
+ "backup_vaults_exist",
+ "dlm_ebs_snapshot_lifecycle_policy_exists",
+ "documentdb_cluster_backup_enabled",
+ "drs_job_exist",
+ "dynamodb_table_protected_by_backup_plan",
+ "dynamodb_tables_pitr_enabled",
+ "ec2_ebs_volume_protected_by_backup_plan",
+ "ec2_ebs_volume_snapshots_exists",
+ "efs_have_backup_enabled",
+ "elasticache_redis_cluster_backup_enabled",
+ "lightsail_instance_automated_snapshots",
+ "neptune_cluster_backup_enabled",
+ "rds_cluster_backtrack_enabled",
+ "rds_cluster_protected_by_backup_plan",
+ "rds_instance_backup_enabled",
+ "rds_instance_protected_by_backup_plan",
+ "redshift_cluster_automated_snapshot",
+ "s3_bucket_object_versioning"
+ ],
+ "azure": [
+ "cosmosdb_account_backup_policy_continuous",
+ "mysql_flexible_server_geo_redundant_backup_enabled",
+ "postgresql_flexible_server_geo_redundant_backup_enabled",
+ "recovery_vault_has_protected_items",
+ "vm_backup_enabled",
+ "vm_sufficient_daily_backup_retention_period"
+ ],
+ "gcp": [
+ "cloudsql_instance_automated_backups",
+ "cloudstorage_bucket_soft_delete_enabled",
+ "cloudstorage_bucket_versioning_enabled"
+ ],
+ "linode": [
+ "compute_instance_backups_enabled"
+ ],
+ "mongodbatlas": [
+ "clusters_backup_enabled"
+ ],
+ "openstack": [
+ "blockstorage_volume_backup_exists",
+ "objectstorage_container_versioning_enabled"
+ ],
+ "oraclecloud": [
+ "objectstorage_bucket_versioning_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "drs_job_exist",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "11.3",
+ "name": "Protect Recovery Data",
+ "description": "Protect recovery data with equivalent controls to the original data. Reference encryption or data separation, based on requirements.",
+ "attributes": {
+ "Section": "11. Data Recovery",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "backup_recovery_point_encrypted",
+ "backup_vaults_encrypted",
+ "documentdb_cluster_public_snapshot",
+ "ec2_ebs_public_snapshot",
+ "ec2_ebs_snapshot_account_block_public_access",
+ "ec2_ebs_snapshots_encrypted",
+ "neptune_cluster_public_snapshot",
+ "neptune_cluster_snapshot_encrypted",
+ "rds_snapshots_encrypted",
+ "rds_snapshots_public_access",
+ "s3_bucket_no_mfa_delete",
+ "s3_bucket_object_lock"
+ ],
+ "azure": [
+ "storage_ensure_file_shares_soft_delete_is_enabled",
+ "storage_ensure_soft_delete_is_enabled"
+ ],
+ "stackit": [
+ "objectstorage_bucket_object_lock_enabled"
+ ]
+ }
+ },
+ {
+ "id": "11.4",
+ "name": "Establish and Maintain an Isolated Instance of Recovery Data",
+ "description": "Establish and maintain an isolated instance of recovery data. Example implementations include, version controlling backup destinations through offline, cloud, or off-site systems or services.",
+ "attributes": {
+ "Section": "11. Data Recovery",
+ "Function": "Recover",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "s3_bucket_cross_region_replication"
+ ],
+ "azure": [
+ "mysql_flexible_server_geo_redundant_backup_enabled",
+ "postgresql_flexible_server_geo_redundant_backup_enabled",
+ "storage_geo_redundant_enabled"
+ ]
+ }
+ },
+ {
+ "id": "11.5",
+ "name": "Test Data Recovery",
+ "description": "Test backup recovery quarterly, or more frequently, for a sampling of in-scope enterprise assets.",
+ "attributes": {
+ "Section": "11. Data Recovery",
+ "Function": "Recover",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "12.1",
+ "name": "Ensure Network Infrastructure is Up-to-Date",
+ "description": "Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network as a service (Naas) offerings. Review software versions monthly, or more frequently, to verify software support.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "12.2",
+ "name": "Establish and Maintain a Secure Network Architecture",
+ "description": "Design and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum. Example implementations may include documentation, policy, and design components.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "cs_kubernetes_private_cluster_enabled",
+ "ecs_instance_no_legacy_network"
+ ],
+ "aws": [
+ "appstream_fleet_default_internet_access_disabled",
+ "autoscaling_group_launch_configuration_no_public_ip",
+ "awslambda_function_inside_vpc",
+ "dms_instance_no_public_access",
+ "ec2_instance_public_ip",
+ "ec2_launch_template_no_public_ip",
+ "ec2_transitgateway_auto_accept_vpc_attachments",
+ "ecs_service_no_assign_public_ip",
+ "ecs_task_set_no_assign_public_ip",
+ "eks_cluster_not_publicly_accessible",
+ "eks_cluster_private_nodes_enabled",
+ "elasticache_cluster_uses_public_subnet",
+ "elb_internet_facing",
+ "elbv2_internet_facing",
+ "emr_cluster_account_public_block_enabled",
+ "emr_cluster_master_nodes_no_public_ip",
+ "emr_cluster_publicly_accesible",
+ "kafka_cluster_is_public",
+ "lightsail_database_public",
+ "lightsail_instance_public",
+ "mq_broker_not_publicly_accessible",
+ "neptune_cluster_uses_public_subnet",
+ "opensearch_service_domains_not_publicly_accessible",
+ "rds_instance_inside_vpc",
+ "rds_instance_no_public_access",
+ "redshift_cluster_public_access",
+ "sagemaker_models_vpc_settings_configured",
+ "sagemaker_notebook_instance_vpc_settings_configured",
+ "sagemaker_notebook_instance_without_direct_internet_access_configured",
+ "sagemaker_training_jobs_vpc_settings_configured",
+ "vpc_endpoint_connections_trust_boundaries",
+ "vpc_endpoint_services_allowed_principals_trust_boundaries",
+ "vpc_peering_routing_tables_with_least_privilege",
+ "vpc_subnet_no_public_ip_by_default",
+ "vpc_subnet_separate_private_public"
+ ],
+ "azure": [
+ "aisearch_service_not_publicly_accessible",
+ "aks_clusters_public_access_disabled",
+ "app_function_not_publicly_accessible",
+ "containerregistry_not_publicly_accessible",
+ "containerregistry_uses_private_link",
+ "cosmosdb_account_public_network_access_disabled",
+ "cosmosdb_account_use_private_endpoints",
+ "databricks_workspace_public_network_access_disabled",
+ "keyvault_access_only_through_private_endpoints",
+ "keyvault_private_endpoints",
+ "storage_account_public_network_access_disabled",
+ "storage_ensure_private_endpoints_in_storage_accounts"
+ ],
+ "gcp": [
+ "cloudfunction_function_inside_vpc",
+ "cloudsql_instance_private_ip_assignment",
+ "cloudsql_instance_public_ip",
+ "cloudstorage_uses_vpc_service_controls",
+ "compute_instance_public_ip",
+ "compute_instance_single_network_interface",
+ "compute_network_default_in_use",
+ "compute_network_not_legacy"
+ ],
+ "mongodbatlas": [
+ "projects_network_access_list_exposed_to_internet"
+ ],
+ "nhn": [
+ "compute_instance_public_ip",
+ "network_vpc_subnet_has_external_router"
+ ],
+ "openstack": [
+ "compute_instance_isolated_private_network"
+ ],
+ "oraclecloud": [
+ "analytics_instance_access_restricted",
+ "database_autonomous_database_access_restricted",
+ "integration_instance_access_restricted",
+ "objectstorage_bucket_not_publicly_accessible"
+ ]
+ }
+ },
+ {
+ "id": "12.3",
+ "name": "Securely Manage Network Infrastructure",
+ "description": "Securely manage network infrastructure. Example implementations include version-controlled Infrastructure-as-Code (IaC), and the use of secure network protocols, such as SSH and HTTPS.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "gcp": [
+ "dns_dnssec_disabled",
+ "dns_rsasha1_in_use_to_key_sign_in_dnssec",
+ "dns_rsasha1_in_use_to_zone_sign_in_dnssec"
+ ]
+ }
+ },
+ {
+ "id": "12.4",
+ "name": "Establish and Maintain Architecture Diagram(s)",
+ "description": "Establish and maintain architecture diagram(s) and/or other network system documentation. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "12.5",
+ "name": "Centralize Network Authentication, Authorization, and Auditing (AAA)",
+ "description": "Centralize network AAA.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "12.6",
+ "name": "Use of Secure Network Management and Communication Protocols",
+ "description": "Adopt secure network management protocols (e.g., 802.1X) and secure communication protocols (e.g., Wi-Fi Protected Access 2 (WPA2) Enterprise or more secure alternatives).",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "app_minimum_tls_version_12",
+ "cosmosdb_account_minimum_tls_version",
+ "mysql_flexible_server_minimum_tls_version_12",
+ "sqlserver_recommended_minimal_tls_version",
+ "storage_ensure_minimum_tls_version_12",
+ "storage_smb_protocol_version_is_latest"
+ ],
+ "cloudflare": [
+ "zone_automatic_https_rewrites_enabled",
+ "zone_hsts_enabled",
+ "zone_https_redirect_enabled",
+ "zone_min_tls_version_secure",
+ "zone_ssl_strict",
+ "zone_tls_1_3_enabled",
+ "zone_universal_ssl_enabled"
+ ],
+ "kubernetes": [
+ "apiserver_client_ca_file_set",
+ "controllermanager_root_ca_file_set",
+ "controllermanager_rotate_kubelet_server_cert",
+ "etcd_client_cert_auth",
+ "etcd_peer_client_cert_auth",
+ "etcd_unique_ca",
+ "kubelet_client_ca_file_set",
+ "kubelet_rotate_certificates"
+ ]
+ }
+ },
+ {
+ "id": "12.7",
+ "name": "Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure",
+ "description": "Require users to authenticate to enterprise-managed VPN and authentication services prior to accessing enterprise resources on end-user devices.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "ec2_client_vpn_endpoint_connection_logging_enabled"
+ ]
+ }
+ },
+ {
+ "id": "12.8",
+ "name": "Establish and Maintain Dedicated Computing Resources for All Administrative Work",
+ "description": "Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative tasks or tasks requiring administrative access. The computing resources should be segmented from the enterprise's primary network and not be allowed internet access.",
+ "attributes": {
+ "Section": "12. Network Infrastructure Management",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "network_bastion_host_exists",
+ "vm_jit_access_enabled"
+ ]
+ }
+ },
+ {
+ "id": "13.1",
+ "name": "Centralize Security Event Alerting",
+ "description": "Centralize security event alerting across enterprise assets for log correlation and analysis. Best practice implementation requires the use of a SIEM, which includes vendor-defined event correlation alerts. A log analytics platform configured with security-relevant correlation alerts also satisfies this Safeguard.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "securitycenter_notification_enabled_high_risk",
+ "sls_cloud_firewall_changes_alert_enabled",
+ "sls_customer_created_cmk_changes_alert_enabled",
+ "sls_management_console_authentication_failures_alert_enabled",
+ "sls_management_console_signin_without_mfa_alert_enabled",
+ "sls_oss_bucket_policy_changes_alert_enabled",
+ "sls_oss_permission_changes_alert_enabled",
+ "sls_ram_role_changes_alert_enabled",
+ "sls_rds_instance_configuration_changes_alert_enabled",
+ "sls_root_account_usage_alert_enabled",
+ "sls_security_group_changes_alert_enabled",
+ "sls_unauthorized_api_calls_alert_enabled",
+ "sls_vpc_changes_alert_enabled",
+ "sls_vpc_network_route_changes_alert_enabled"
+ ],
+ "aws": [
+ "cloudwatch_alarm_actions_alarm_state_configured",
+ "cloudwatch_alarm_actions_enabled",
+ "securityhub_delegated_admin_enabled_all_regions",
+ "securityhub_enabled"
+ ],
+ "azure": [
+ "defender_additional_email_configured_with_a_security_contact",
+ "defender_attack_path_notifications_properly_configured",
+ "defender_ensure_notify_alerts_severity_is_high",
+ "defender_ensure_notify_emails_to_owners",
+ "monitor_alert_create_update_security_solution"
+ ],
+ "googleworkspace": [
+ "rules_admin_privilege_granted_alert_configured",
+ "rules_gmail_employee_spoofing_alert_configured",
+ "rules_government_backed_attacks_alert_configured",
+ "rules_leaked_password_alert_configured",
+ "rules_password_changed_alert_configured",
+ "rules_suspicious_activity_suspension_alert_configured",
+ "rules_suspicious_login_alert_configured",
+ "rules_suspicious_programmatic_login_alert_configured"
+ ],
+ "oraclecloud": [
+ "events_notification_topic_and_subscription_exists",
+ "events_rule_cloudguard_problems",
+ "events_rule_iam_group_changes",
+ "events_rule_iam_policy_changes",
+ "events_rule_identity_provider_changes",
+ "events_rule_idp_group_mapping_changes",
+ "events_rule_local_user_authentication",
+ "events_rule_network_gateway_changes",
+ "events_rule_network_security_group_changes",
+ "events_rule_route_table_changes",
+ "events_rule_security_list_changes",
+ "events_rule_user_changes",
+ "events_rule_vcn_changes"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "13.2",
+ "name": "Deploy a Host-Based Intrusion Detection Solution",
+ "description": "Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Detect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "securitycenter_all_assets_agent_installed",
+ "ecs_instance_endpoint_protection_installed"
+ ],
+ "azure": [
+ "defender_ensure_defender_for_server_is_on",
+ "defender_ensure_wdatp_is_enabled"
+ ]
+ }
+ },
+ {
+ "id": "13.3",
+ "name": "Deploy a Network Intrusion Detection Solution",
+ "description": "Deploy a network intrusion detection solution on enterprise assets, where appropriate. Example implementations include the use of a Network Intrusion Detection System (NIDS) or equivalent cloud service provider (CSP) service.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "guardduty_eks_audit_log_enabled",
+ "guardduty_eks_runtime_monitoring_enabled",
+ "guardduty_is_enabled"
+ ],
+ "azure": [
+ "defender_ensure_defender_for_dns_is_on"
+ ],
+ "oraclecloud": [
+ "cloudguard_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "13.4",
+ "name": "Perform Traffic Filtering Between Network Segments",
+ "description": "Perform traffic filtering between network segments, where appropriate.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "cs_kubernetes_network_policy_enabled"
+ ],
+ "aws": [
+ "ec2_networkacl_allow_ingress_any_port",
+ "ec2_networkacl_allow_ingress_tcp_port_22",
+ "ec2_networkacl_allow_ingress_tcp_port_3389",
+ "networkfirewall_in_all_vpc",
+ "vpc_peering_routing_tables_with_least_privilege"
+ ],
+ "azure": [
+ "network_http_internet_access_restricted",
+ "network_rdp_internet_access_restricted",
+ "network_ssh_internet_access_restricted",
+ "network_subnet_nsg_associated",
+ "network_udp_internet_access_restricted"
+ ],
+ "gcp": [
+ "compute_firewall_rdp_access_from_the_internet_allowed",
+ "compute_firewall_ssh_access_from_the_internet_allowed"
+ ],
+ "linode": [
+ "networking_firewall_default_inbound_policy_drop",
+ "networking_firewall_default_outbound_policy_drop",
+ "networking_firewall_inbound_rules_configured",
+ "networking_firewall_outbound_rules_configured"
+ ],
+ "mongodbatlas": [
+ "projects_network_access_list_exposed_to_internet"
+ ],
+ "openstack": [
+ "networking_security_group_allows_all_ingress_from_internet",
+ "networking_security_group_allows_rdp_from_internet",
+ "networking_security_group_allows_ssh_from_internet"
+ ],
+ "oraclecloud": [
+ "network_default_security_list_restricts_traffic",
+ "network_security_group_ingress_from_internet_to_rdp_port",
+ "network_security_group_ingress_from_internet_to_ssh_port",
+ "network_security_list_ingress_from_internet_to_rdp_port",
+ "network_security_list_ingress_from_internet_to_ssh_port"
+ ],
+ "stackit": [
+ "iaas_security_group_all_traffic_unrestricted",
+ "iaas_security_group_database_unrestricted",
+ "iaas_security_group_rdp_unrestricted",
+ "iaas_security_group_ssh_unrestricted"
+ ]
+ }
+ },
+ {
+ "id": "13.5",
+ "name": "Manage Access Control for Remote Assets",
+ "description": "Manage access control for assets remotely connecting to enterprise resources. Determine amount of access to enterprise resources based on: up-to-date anti-malware software installed, configuration compliance with the enterprise's secure configuration process, and ensuring the operating system and applications are up-to-date.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "m365": [
+ "entra_conditional_access_policy_compliant_device_hybrid_joined_device_mfa_required",
+ "entra_conditional_access_policy_mdm_compliant_device_required",
+ "entra_managed_device_required_for_authentication",
+ "intune_device_compliance_policy_unassigned_devices_not_compliant_by_default",
+ "sharepoint_onedrive_sync_restricted_unmanaged_devices"
+ ]
+ }
+ },
+ {
+ "id": "13.6",
+ "name": "Collect Network Traffic Flow Logs",
+ "description": "Collect network traffic flow logs and/or network traffic to review and alert upon from network devices.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "alibabacloud": [
+ "vpc_flow_logs_enabled"
+ ],
+ "aws": [
+ "vpc_flow_logs_enabled"
+ ],
+ "azure": [
+ "network_flow_log_captured_sent",
+ "network_flow_log_more_than_90_days",
+ "network_watcher_enabled"
+ ],
+ "gcp": [
+ "compute_subnet_flow_logs_enabled"
+ ],
+ "oraclecloud": [
+ "network_vcn_subnet_flow_logs_enabled"
+ ]
+ }
+ },
+ {
+ "id": "13.7",
+ "name": "Deploy a Host-Based Intrusion Prevention Solution",
+ "description": "Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Devices",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "defender_ensure_wdatp_is_enabled",
+ "defender_ensure_defender_for_server_is_on"
+ ]
+ }
+ },
+ {
+ "id": "13.8",
+ "name": "Deploy a Network Intrusion Prevention Solution",
+ "description": "Deploy a network intrusion prevention solution, where appropriate. Example implementations include the use of a Network Intrusion Prevention System (NIPS) or equivalent CSP service.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "networkfirewall_in_all_vpc",
+ "networkfirewall_policy_default_action_fragmented_packets",
+ "networkfirewall_policy_default_action_full_packets",
+ "networkfirewall_policy_rule_group_associated",
+ "shield_advanced_protection_in_associated_elastic_ips",
+ "shield_advanced_protection_in_classic_load_balancers",
+ "shield_advanced_protection_in_cloudfront_distributions",
+ "shield_advanced_protection_in_global_accelerators",
+ "shield_advanced_protection_in_internet_facing_load_balancers",
+ "shield_advanced_protection_in_route53_hosted_zones"
+ ],
+ "azure": [
+ "network_vnet_ddos_protection_enabled"
+ ],
+ "cloudflare": [
+ "zone_bot_fight_mode_enabled",
+ "zone_firewall_blocking_rules_configured",
+ "zone_rate_limiting_enabled",
+ "zone_waf_enabled",
+ "zone_waf_owasp_ruleset_enabled"
+ ],
+ "vercel": [
+ "security_managed_rulesets_enabled",
+ "security_rate_limiting_configured",
+ "security_waf_enabled"
+ ]
+ }
+ },
+ {
+ "id": "13.9",
+ "name": "Deploy Port-Level Access Control",
+ "description": "Deploy port-level access control. Port-level access control utilizes 802.1x, or similar network access control protocols, such as certificates, and may incorporate user and/or device authentication.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "13.10",
+ "name": "Perform Application Layer Filtering",
+ "description": "Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or gateway.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "apigateway_restapi_waf_acl_attached",
+ "cloudfront_distributions_using_waf",
+ "cognito_user_pool_waf_acl_attached",
+ "elbv2_waf_acl_attached",
+ "waf_global_rule_with_conditions",
+ "waf_global_rulegroup_not_empty",
+ "waf_global_webacl_with_rules",
+ "waf_regional_rule_with_conditions",
+ "waf_regional_rulegroup_not_empty",
+ "waf_regional_webacl_with_rules",
+ "wafv2_webacl_with_rules"
+ ],
+ "cloudflare": [
+ "dns_record_proxied",
+ "zone_bot_fight_mode_enabled",
+ "zone_browser_integrity_check_enabled",
+ "zone_firewall_blocking_rules_configured",
+ "zone_rate_limiting_enabled",
+ "zone_waf_enabled",
+ "zone_waf_owasp_ruleset_enabled"
+ ],
+ "vercel": [
+ "security_custom_rules_configured",
+ "security_ip_blocking_rules_configured",
+ "security_managed_rulesets_enabled",
+ "security_rate_limiting_configured",
+ "security_waf_enabled"
+ ]
+ }
+ },
+ {
+ "id": "13.11",
+ "name": "Tune Security Event Alerting Thresholds",
+ "description": "Tune security event alerting thresholds monthly, or more frequently.",
+ "attributes": {
+ "Section": "13. Network Monitoring and Defense",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.1",
+ "name": "Establish and Maintain a Security Awareness Program",
+ "description": "Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise's workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.2",
+ "name": "Train Workforce Members to Recognize Social Engineering Attacks",
+ "description": "Train workforce members to recognize social engineering attacks, such as phishing, business email compromise (BEC), pretexting, and tailgating.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.3",
+ "name": "Train Workforce Members on Authentication Best Practices",
+ "description": "Train workforce members on authentication best practices. Example topics include MFA, password composition, and credential management.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.4",
+ "name": "Train Workforce on Data Handling Best Practices",
+ "description": "Train workforce members on how to identify and properly store, transfer, archive, and destroy sensitive data. This also includes training workforce members on clear screen and desk best practices, such as locking their screen when they step away from their enterprise asset, erasing physical and virtual whiteboards at the end of meetings, and storing data and assets securely.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.5",
+ "name": "Train Workforce Members on Causes of Unintentional Data Exposure",
+ "description": "Train workforce members to be aware of causes for unintentional data exposure. Example topics include mis-delivery of sensitive data, losing a portable end-user device, or publishing data to unintended audiences.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.6",
+ "name": "Train Workforce Members on Recognizing and Reporting Security Incidents",
+ "description": "Train workforce members to be able to recognize a potential incident and be able to report such an incident.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.7",
+ "name": "Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates",
+ "description": "Train workforce to understand how to verify and report out-of-date software patches or any failures in automated processes and tools. Part of this training should include notifying IT personnel of any failures in automated processes and tools.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.8",
+ "name": "Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks",
+ "description": "Train workforce members on the dangers of connecting to, and transmitting data over, insecure networks for enterprise activities. If the enterprise has remote workers, training must include guidance to ensure that all users securely configure their home network infrastructure.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "14.9",
+ "name": "Conduct Role-Specific Security Awareness and Skills Training",
+ "description": "Conduct role-specific security awareness and skills training. Example implementations include secure system administration courses for IT professionals, OWASP® Top 10 vulnerability awareness and prevention training for web application developers, and advanced social engineering awareness training for high-profile roles.",
+ "attributes": {
+ "Section": "14. Security Awareness and Skills Training",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.1",
+ "name": "Establish and Maintain an Inventory of Service Providers",
+ "description": "Establish and maintain an inventory of service providers. The inventory is to list all known service providers, include classification(s), and designate an enterprise contact for each service provider. Review and update the inventory annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Identify",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.2",
+ "name": "Establish and Maintain a Service Provider Management Policy",
+ "description": "Establish and maintain a service provider management policy. Ensure the policy addresses the classification, inventory, assessment, monitoring, and decommissioning of service providers. Review and update the policy annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.3",
+ "name": "Classify Service Providers",
+ "description": "Classify service providers. Classification consideration may include one or more characteristics, such as data sensitivity, data volume, availability requirements, applicable regulations, inherent risk, and mitigated risk. Update and review classifications annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Govern",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.4",
+ "name": "Ensure Service Provider Contracts Include Security Requirements",
+ "description": "Ensure service provider contracts include security requirements. Example requirements may include minimum security program requirements, security incident and/or data breach notification and response, data encryption requirements, and data disposal commitments. These security requirements must be consistent with the enterprise's service provider management policy. Review service provider contracts annually to ensure contracts are not missing security requirements.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.5",
+ "name": "Assess Service Providers",
+ "description": "Assess service providers consistent with the enterprise's service provider management policy. Assessment scope may vary based on classification(s), and may include review of standardized assessment reports, such as Service Organization Control 2 (SOC 2) and Payment Card Industry (PCI) Attestation of Compliance (AoC), customized questionnaires, or other appropriately rigorous processes. Reassess service providers annually, at a minimum, or with new and renewed contracts.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Govern",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.6",
+ "name": "Monitor Service Providers",
+ "description": "Monitor service providers consistent with the enterprise's service provider management policy. Monitoring may include periodic reassessment of service provider compliance, monitoring service provider release notes, and dark web monitoring.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Govern",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "15.7",
+ "name": "Securely Decommission Service Providers",
+ "description": "Securely decommission service providers. Example considerations include user and service account deactivation, termination of data flows, and secure disposal of enterprise data within service provider systems.",
+ "attributes": {
+ "Section": "15. Service Provider Management",
+ "Function": "Protect",
+ "AssetType": "Data",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "16.1",
+ "name": "Establish and Maintain a Secure Application Development Process",
+ "description": "Establish and maintain a secure application development process. In the process, address such items as: secure application design standards, secure coding practices, developer training, vulnerability management, security of third-party code, and application security testing procedures. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "github": [
+ "repository_default_branch_deletion_disabled",
+ "repository_default_branch_disallows_force_push",
+ "repository_default_branch_dismisses_stale_reviews",
+ "repository_default_branch_protection_applies_to_admins",
+ "repository_default_branch_protection_enabled",
+ "repository_default_branch_requires_codeowners_review",
+ "repository_default_branch_requires_conversation_resolution",
+ "repository_default_branch_requires_linear_history",
+ "repository_default_branch_requires_multiple_approvals",
+ "repository_default_branch_requires_signed_commits",
+ "repository_default_branch_status_checks_required",
+ "repository_has_codeowners_file"
+ ]
+ }
+ },
+ {
+ "id": "16.2",
+ "name": "Establish and Maintain a Process to Accept and Address Software Vulnerabilities",
+ "description": "Establish and maintain a process to accept and address reports of software vulnerabilities, including providing a means for external entities to report. The process is to include such items as: a vulnerability handling policy that identifies reporting process, responsible party for handling vulnerability reports, and a process for intake, assignment, remediation, and remediation testing. As part of the process, use a vulnerability tracking system that includes severity ratings and metrics for measuring timing for identification, analysis, and remediation of vulnerabilities. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard. Third-party application developers need to consider this an externally-facing policy that helps to set expectations for outside stakeholders.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "github": [
+ "repository_public_has_securitymd_file"
+ ]
+ }
+ },
+ {
+ "id": "16.3",
+ "name": "Perform Root Cause Analysis on Security Vulnerabilities",
+ "description": "Perform root cause analysis on security vulnerabilities. When reviewing vulnerabilities, root cause analysis is the task of evaluating underlying issues that create vulnerabilities in code, and allows development teams to move beyond just fixing individual vulnerabilities as they arise.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Detect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "16.4",
+ "name": "Establish and Manage an Inventory of Third-Party Software Components",
+ "description": "Establish and manage an updated inventory of third-party components used in development, often referred to as a \"bill of materials,\" as well as components slated for future use. This inventory is to include any risks that each third-party component could pose. Evaluate the list at least monthly to identify any changes or updates to these components, and validate that the component is still supported.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Identify",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "github": [
+ "repository_dependency_scanning_enabled"
+ ]
+ }
+ },
+ {
+ "id": "16.5",
+ "name": "Use Up-to-Date and Trusted Third-Party Software Components",
+ "description": "Use up-to-date and trusted third-party software components. When possible, choose established and proven frameworks and libraries that provide adequate security. Acquire these components from trusted sources or evaluate the software for vulnerabilities before use.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "codeartifact_packages_external_public_publishing_disabled"
+ ],
+ "github": [
+ "repository_dependency_scanning_enabled"
+ ]
+ }
+ },
+ {
+ "id": "16.6",
+ "name": "Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities",
+ "description": "Establish and maintain a severity rating system and process for application vulnerabilities that facilitates prioritizing the order in which discovered vulnerabilities are fixed. This process includes setting a minimum level of security acceptability for releasing code or applications. Severity ratings bring a systematic way of triaging vulnerabilities that improves risk management and helps ensure the most severe bugs are fixed first. Review and update the system and process annually.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "16.7",
+ "name": "Use Standard Hardening Configuration Templates for Application Infrastructure",
+ "description": "Use standard, industry-recommended hardening configuration templates for application infrastructure components. This includes underlying servers, databases, and web servers, and applies to cloud containers, Platform as a Service (PaaS) components, and SaaS components. Do not allow in-house developed software to weaken configuration hardening.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "azure": [
+ "app_ensure_using_http20",
+ "app_ftp_deployment_disabled",
+ "app_minimum_tls_version_12"
+ ],
+ "gcp": [
+ "cloudsql_instance_mysql_local_infile_flag",
+ "cloudsql_instance_mysql_skip_show_database_flag",
+ "cloudsql_instance_sqlserver_contained_database_authentication_flag",
+ "cloudsql_instance_sqlserver_cross_db_ownership_chaining_flag",
+ "cloudsql_instance_sqlserver_external_scripts_enabled_flag",
+ "cloudsql_instance_sqlserver_remote_access_flag",
+ "compute_instance_shielded_vm_enabled",
+ "gke_cluster_no_default_service_account"
+ ],
+ "kubernetes": [
+ "apiserver_always_pull_images_plugin",
+ "apiserver_deny_service_external_ips",
+ "apiserver_event_rate_limit",
+ "apiserver_namespace_lifecycle_plugin",
+ "apiserver_no_always_admit_plugin",
+ "apiserver_node_restriction_plugin",
+ "apiserver_security_context_deny_plugin",
+ "core_image_tag_fixed",
+ "core_minimize_admission_hostport_containers",
+ "core_minimize_admission_windows_hostprocess_containers",
+ "core_minimize_allowPrivilegeEscalation_containers",
+ "core_minimize_containers_added_capabilities",
+ "core_minimize_containers_capabilities_assigned",
+ "core_minimize_hostIPC_containers",
+ "core_minimize_hostNetwork_containers",
+ "core_minimize_hostPID_containers",
+ "core_minimize_net_raw_capability_admission",
+ "core_minimize_privileged_containers",
+ "core_minimize_root_containers_admission",
+ "core_seccomp_profile_docker_default"
+ ],
+ "vercel": [
+ "project_auto_expose_system_env_disabled",
+ "project_directory_listing_disabled",
+ "project_git_fork_protection_enabled"
+ ]
+ }
+ },
+ {
+ "id": "16.8",
+ "name": "Separate Production and Non-Production Systems",
+ "description": "Maintain separate environments for production and non-production systems.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "vercel": [
+ "deployment_production_uses_stable_target",
+ "project_deployment_protection_enabled",
+ "project_environment_no_overly_broad_target",
+ "project_environment_production_vars_not_in_preview"
+ ]
+ }
+ },
+ {
+ "id": "16.9",
+ "name": "Train Developers in Application Security Concepts and Secure Coding",
+ "description": "Ensure that all software development personnel receive training in writing secure code for their specific development environment and responsibilities. Training can include general security principles and application security standard practices. Conduct training at least annually and design in a way to promote security within the development team, and build a culture of security among the developers.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "16.10",
+ "name": "Apply Secure Design Principles in Application Architectures",
+ "description": "Apply secure design principles in application architectures. Secure design principles include the concept of least privilege and enforcing mediation to validate every operation that the user makes, promoting the concept of \"never trust user input.\" Examples include ensuring that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ranges or formats. Secure design also means minimizing the application infrastructure attack surface, such as turning off unprotected ports and services, removing unnecessary programs and files, and renaming or removing default accounts.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "apigateway_restapi_authorizers_enabled",
+ "apigateway_restapi_public_with_authorizer",
+ "apigatewayv2_api_authorizers_enabled",
+ "appsync_graphql_api_no_api_key_authentication",
+ "cognito_user_pool_client_prevent_user_existence_errors",
+ "ecs_task_definitions_containers_readonly_access",
+ "ecs_task_definitions_host_namespace_not_shared",
+ "ecs_task_definitions_host_networking_mode_users",
+ "ecs_task_definitions_no_privileged_containers",
+ "elb_desync_mitigation_mode",
+ "elbv2_alb_drop_invalid_header_fields_enabled",
+ "elbv2_desync_mitigation_mode",
+ "sagemaker_notebook_instance_root_access_disabled"
+ ]
+ }
+ },
+ {
+ "id": "16.11",
+ "name": "Leverage Vetted Modules or Services for Application Security Components",
+ "description": "Leverage vetted modules or services for application security components, such as identity management, encryption, auditing, and logging. Using platform features in critical security functions will reduce developers' workload and minimize the likelihood of design or implementation errors. Modern operating systems provide effective mechanisms for identification, authentication, and authorization and make those mechanisms available to applications. Use only standardized, currently accepted, and extensively reviewed encryption algorithms. Operating systems also provide mechanisms to create and maintain secure audit logs.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "secretsmanager_automatic_rotation_enabled",
+ "secretsmanager_secret_rotated_periodically"
+ ],
+ "azure": [
+ "app_ensure_auth_is_set_up",
+ "app_function_access_keys_configured",
+ "app_function_identity_is_configured",
+ "app_register_with_identity"
+ ],
+ "vercel": [
+ "team_directory_sync_enabled",
+ "team_saml_sso_enabled"
+ ]
+ }
+ },
+ {
+ "id": "16.12",
+ "name": "Implement Code-Level Security Checks",
+ "description": "Apply static and dynamic analysis tools within the application life cycle to verify that secure coding practices are being followed.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "awslambda_function_no_secrets_in_code",
+ "inspector2_is_enabled"
+ ],
+ "github": [
+ "githubactions_workflow_security_scan",
+ "repository_secret_scanning_enabled"
+ ]
+ }
+ },
+ {
+ "id": "16.13",
+ "name": "Conduct Application Penetration Testing",
+ "description": "Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Detect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "16.14",
+ "name": "Conduct Threat Modeling",
+ "description": "Conduct threat modeling. Threat modeling is the process of identifying and addressing application security design flaws within a design, before code is created. It is conducted through specially trained individuals who evaluate the application design and gauge security risks for each entry point and access level. The goal is to map out the application, architecture, and infrastructure in a structured way to understand its weaknesses.",
+ "attributes": {
+ "Section": "16. Application Software Security",
+ "Function": "Protect",
+ "AssetType": "Software",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.1",
+ "name": "Designate Personnel to Manage Incident Handling",
+ "description": "Designate one key person, and at least one backup, who will manage the enterprise's incident handling process. Management personnel are responsible for the coordination and documentation of incident response and recovery efforts and can consist of employees internal to the enterprise, service providers, or a hybrid approach. If using a service provider, designate at least one person internal to the enterprise to oversee any third-party work. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Respond",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.2",
+ "name": "Establish and Maintain Contact Information for Reporting Security Incidents",
+ "description": "Establish and maintain contact information for parties that need to be informed of security incidents. Contacts may include internal staff, service providers, law enforcement, cyber insurance providers, relevant government agencies, Information Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify contacts annually to ensure that information is up-to-date.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "account_maintain_current_contact_details",
+ "account_maintain_different_contact_details_to_security_billing_and_operations",
+ "account_security_contact_information_is_registered"
+ ],
+ "gcp": [
+ "iam_organization_essential_contacts_configured"
+ ],
+ "mongodbatlas": [
+ "organizations_security_contact_defined"
+ ]
+ }
+ },
+ {
+ "id": "17.3",
+ "name": "Establish and Maintain an Enterprise Process for Reporting Incidents",
+ "description": "Establish and maintain an documented enterprise process for the workforce to report security incidents. The process includes reporting timeframe, personnel to report to, mechanism for reporting, and the minimum information to be reported. Ensure the process is publicly available to all of the workforce. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG1",
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.4",
+ "name": "Establish and Maintain an Incident Response Process",
+ "description": "Establish and maintain a documented incident response process that addresses roles and responsibilities, compliance requirements, and a communication plan. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {
+ "aws": [
+ "ssmincidents_enabled_with_plans"
+ ]
+ }
+ },
+ {
+ "id": "17.5",
+ "name": "Assign Key Roles and Responsibilities",
+ "description": "Assign key roles and responsibilities for incident response, including staff from legal, IT, information security, facilities, public relations, human resources, incident responders, analysts, and relevant third parties. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Respond",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.6",
+ "name": "Define Mechanisms for Communicating During Incident Response",
+ "description": "Determine which primary and secondary mechanisms will be used to communicate and report during a security incident. Mechanisms can include phone calls, emails, secure chat, or notification letters. Keep in mind that certain mechanisms, such as emails, can be affected during a security incident. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Respond",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.7",
+ "name": "Conduct Routine Incident Response Exercises",
+ "description": "Plan and conduct routine incident response exercises and scenarios for key personnel involved in the incident response process to prepare for responding to real-world incidents. Exercises need to test communication channels, decision making, and workflows. Conduct testing on an annual basis, at a minimum.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Recover",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.8",
+ "name": "Conduct Post-Incident Reviews",
+ "description": "Conduct post-incident reviews. Post-incident reviews help prevent incident recurrence through identifying lessons learned and follow-up action.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Recover",
+ "AssetType": "Users",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "17.9",
+ "name": "Establish and Maintain Security Incident Thresholds",
+ "description": "Establish and maintain security incident thresholds, including, at a minimum, differentiating between an incident and an event. Examples can include: abnormal activity, security vulnerability, security weakness, data breach, privacy incident, etc. Review annually, or when significant enterprise changes occur that could impact this Safeguard.",
+ "attributes": {
+ "Section": "17. Incident Response Management",
+ "Function": "Recover",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "18.1",
+ "name": "Establish and Maintain a Penetration Testing Program",
+ "description": "Establish and maintain a penetration testing program appropriate to the size, complexity, industry, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.",
+ "attributes": {
+ "Section": "18. Penetration Testing",
+ "Function": "Govern",
+ "AssetType": "Documentation",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "18.2",
+ "name": "Perform Periodic External Penetration Tests",
+ "description": "Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.",
+ "attributes": {
+ "Section": "18. Penetration Testing",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "18.3",
+ "name": "Remediate Penetration Test Findings",
+ "description": "Remediate penetration test findings based on the enterprise's documented vulnerability remediation process. This should include determining a timeline and level of effort based on the impact and prioritization of each identified finding.",
+ "attributes": {
+ "Section": "18. Penetration Testing",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG2",
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "18.4",
+ "name": "Validate Security Measures",
+ "description": "Validate security measures after each penetration test. If deemed necessary, modify rulesets and capabilities to detect the techniques used during testing.",
+ "attributes": {
+ "Section": "18. Penetration Testing",
+ "Function": "Protect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ },
+ {
+ "id": "18.5",
+ "name": "Perform Periodic Internal Penetration Tests",
+ "description": "Perform periodic internal penetration tests based on program requirements, no less than annually. The testing may be clear box or opaque box.",
+ "attributes": {
+ "Section": "18. Penetration Testing",
+ "Function": "Detect",
+ "AssetType": "Network",
+ "ImplementationGroups": [
+ "IG3"
+ ]
+ },
+ "checks": {}
+ }
+ ]
+}
diff --git a/prowler/compliance/csa_ccm_4.0.json b/prowler/compliance/csa_ccm_4.0.json
index e014c5f408..1cb7428e51 100644
--- a/prowler/compliance/csa_ccm_4.0.json
+++ b/prowler/compliance/csa_ccm_4.0.json
@@ -229,7 +229,16 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "A&A-04",
@@ -334,7 +343,23 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "AIS-04",
@@ -978,7 +1003,16 @@
"defender_ensure_defender_for_server_is_on",
"vm_backup_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "drs_job_exist",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "BCR-11",
@@ -1087,7 +1121,9 @@
"storage_blob_versioning_is_enabled",
"storage_geo_redundant_enabled",
"vm_scaleset_associated_with_load_balancer",
- "vm_scaleset_not_empty"
+ "vm_scaleset_not_empty",
+ "cosmosdb_account_automatic_failover_enabled",
+ "cosmosdb_account_backup_policy_continuous"
],
"gcp": [
"compute_instance_automatic_restart_enabled",
@@ -1414,7 +1450,30 @@
"events_rule_security_list_changes",
"events_rule_vcn_changes"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "CEK-03",
@@ -1600,6 +1659,7 @@
"cloudfront_distributions_origin_traffic_encrypted",
"cloudfront_distributions_custom_ssl_certificate",
"transfer_server_in_transit_encryption_enabled",
+ "transfer_server_pqc_ssh_kex_enabled",
"sagemaker_notebook_instance_encryption_enabled",
"sagemaker_training_jobs_volume_and_output_encryption_enabled",
"workspaces_volume_encryption_enabled",
@@ -1656,7 +1716,18 @@
"filestorage_file_system_encrypted_with_cmk",
"objectstorage_bucket_encrypted_with_cmk"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "Provider": "azure",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
+ ]
},
{
"id": "CEK-04",
@@ -1783,6 +1854,7 @@
"acm_certificates_with_secure_key_algorithms",
"elb_insecure_ssl_ciphers",
"elbv2_insecure_ssl_ciphers",
+ "transfer_server_pqc_ssh_kex_enabled",
"cloudfront_distributions_using_deprecated_ssl_protocols"
],
"azure": [
@@ -1798,7 +1870,29 @@
"dns_rsasha1_in_use_to_key_sign_in_dnssec",
"dns_rsasha1_in_use_to_zone_sign_in_dnssec"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "Provider": "aws",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ },
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "Provider": "azure",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
+ ]
},
{
"id": "CEK-08",
@@ -2341,7 +2435,16 @@
"alibabacloud": [
"securitycenter_all_assets_agent_installed"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "DSP-02",
@@ -2579,7 +2682,16 @@
"alibabacloud": [
"securitycenter_all_assets_agent_installed"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "DSP-04",
@@ -2993,7 +3105,19 @@
"oraclecloud": [
"compute_instance_in_transit_encryption_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "Provider": "azure",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ }
+ ]
},
{
"id": "DSP-16",
@@ -3399,7 +3523,23 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "IAM-02",
@@ -6251,7 +6391,16 @@
"cloudguard_enabled",
"events_rule_cloudguard_problems"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "LOG-02",
@@ -6554,7 +6703,23 @@
"events_notification_topic_and_subscription_exists",
"events_rule_local_user_authentication"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "LOG-04",
@@ -7598,7 +7763,16 @@
"events_rule_cloudguard_problems",
"events_notification_topic_and_subscription_exists"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "SEF-03",
@@ -7876,7 +8050,23 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "SEF-08",
@@ -8457,7 +8647,16 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "TVM-05",
@@ -8725,7 +8924,16 @@
"oraclecloud": [
"cloudguard_enabled"
]
- }
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
},
{
"id": "UEM-08",
diff --git a/prowler/compliance/dora_2022_2554.json b/prowler/compliance/dora_2022_2554.json
new file mode 100644
index 0000000000..3b828059da
--- /dev/null
+++ b/prowler/compliance/dora_2022_2554.json
@@ -0,0 +1,1421 @@
+{
+ "framework": "DORA",
+ "name": "Digital Operational Resilience Act (Regulation (EU) 2022/2554)",
+ "version": "2022/2554",
+ "description": "The Digital Operational Resilience Act (DORA) is a European Union regulation (Regulation (EU) 2022/2554) that sets a uniform framework for the digital operational resilience of the EU financial sector. Mandatory since 17 January 2025, it applies to financial entities (banks, insurers, investment firms, payment institutions, etc.) and to ICT third-party service providers. DORA is structured around five pillars: ICT risk management, ICT-related incident reporting, digital operational resilience testing, ICT third-party risk management, and information sharing. This Prowler mapping covers the technical controls auditable from cloud configuration; the organisational, contractual and supervisory obligations defined in DORA must be addressed outside of Prowler.",
+ "icon": "dora",
+ "attributes_metadata": [
+ {
+ "key": "Pillar",
+ "label": "Pillar",
+ "type": "str",
+ "required": true,
+ "enum": [
+ "ICT Risk Management",
+ "ICT-Related Incident Reporting",
+ "Digital Operational Resilience Testing",
+ "ICT Third-Party Risk Management",
+ "Information Sharing"
+ ],
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ },
+ {
+ "key": "Article",
+ "label": "Article",
+ "type": "str",
+ "required": true,
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ },
+ {
+ "key": "ArticleTitle",
+ "label": "Article Title",
+ "type": "str",
+ "required": true,
+ "output_formats": {
+ "csv": true,
+ "ocsf": true
+ }
+ }
+ ],
+ "outputs": {
+ "table_config": {
+ "group_by": "Pillar"
+ },
+ "pdf_config": {
+ "language": "en",
+ "primary_color": "#003399",
+ "secondary_color": "#0055A5",
+ "bg_color": "#F0F4FA",
+ "group_by_field": "Pillar",
+ "sections": [
+ "ICT Risk Management",
+ "ICT-Related Incident Reporting",
+ "Digital Operational Resilience Testing",
+ "ICT Third-Party Risk Management",
+ "Information Sharing"
+ ],
+ "section_short_names": {
+ "ICT Risk Management": "ICT Risk Mgmt",
+ "ICT-Related Incident Reporting": "Incident Reporting",
+ "Digital Operational Resilience Testing": "Resilience Testing",
+ "ICT Third-Party Risk Management": "Third-Party Risk",
+ "Information Sharing": "Info Sharing"
+ },
+ "charts": [
+ {
+ "id": "pillar_compliance",
+ "type": "horizontal_bar",
+ "group_by": "Pillar",
+ "title": "Compliance Score by DORA Pillar",
+ "y_label": "Pillar",
+ "x_label": "Compliance %",
+ "value_source": "compliance_percent",
+ "color_mode": "by_value"
+ }
+ ],
+ "filter": {
+ "only_failed": true,
+ "include_manual": false
+ }
+ }
+ },
+ "requirements": [
+ {
+ "id": "DORA-Art5",
+ "name": "Governance and organisation",
+ "description": "Financial entities shall have a sound, comprehensive and well-documented ICT internal governance and control framework. Senior management is accountable for ICT risk and shall enforce strong identity, authentication and least-privilege policies for privileged identities, including the root account.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 5",
+ "ArticleTitle": "Governance and organisation"
+ },
+ "checks": {
+ "aws": [
+ "iam_avoid_root_usage",
+ "iam_no_root_access_key",
+ "iam_root_mfa_enabled",
+ "iam_root_hardware_mfa_enabled",
+ "iam_root_credentials_management_enabled",
+ "iam_password_policy_minimum_length_14",
+ "iam_password_policy_lowercase",
+ "iam_password_policy_uppercase",
+ "iam_password_policy_number",
+ "iam_password_policy_symbol",
+ "iam_password_policy_reuse_24",
+ "iam_password_policy_expires_passwords_within_90_days_or_less",
+ "iam_securityaudit_role_created",
+ "iam_support_role_created",
+ "organizations_account_part_of_organizations",
+ "iam_user_mfa_enabled_console_access",
+ "iam_user_hardware_mfa_enabled"
+ ],
+ "azure": [
+ "entra_global_admin_in_less_than_five_users",
+ "entra_privileged_user_has_mfa",
+ "entra_non_privileged_user_has_mfa",
+ "entra_user_with_vm_access_has_mfa",
+ "entra_security_defaults_enabled",
+ "entra_conditional_access_policy_require_mfa_for_admin_portals",
+ "entra_conditional_access_policy_require_mfa_for_management_api",
+ "entra_policy_default_users_cannot_create_security_groups",
+ "entra_policy_ensure_default_user_cannot_create_apps",
+ "entra_policy_ensure_default_user_cannot_create_tenants",
+ "entra_users_cannot_create_microsoft_365_groups",
+ "iam_subscription_roles_owner_custom_not_created",
+ "iam_role_user_access_admin_restricted",
+ "iam_custom_role_has_permissions_to_administer_resource_locks"
+ ],
+ "gcp": [
+ "compute_project_os_login_enabled",
+ "compute_project_os_login_2fa_enabled",
+ "iam_no_service_roles_at_project_level",
+ "iam_sa_no_administrative_privileges",
+ "iam_role_kms_enforce_separation_of_duties",
+ "iam_role_sa_enforce_separation_of_duties",
+ "iam_organization_essential_contacts_configured",
+ "iam_account_access_approval_enabled",
+ "iam_service_account_unused",
+ "compute_instance_default_service_account_in_use",
+ "compute_instance_default_service_account_in_use_with_full_api_access",
+ "gke_cluster_no_default_service_account"
+ ],
+ "alibabacloud": [
+ "ram_no_root_access_key",
+ "ram_user_mfa_enabled_console_access",
+ "ram_user_console_access_unused",
+ "ram_rotate_access_key_90_days",
+ "ram_password_policy_minimum_length",
+ "ram_password_policy_lowercase",
+ "ram_password_policy_uppercase",
+ "ram_password_policy_number",
+ "ram_password_policy_symbol",
+ "ram_password_policy_password_reuse_prevention",
+ "ram_password_policy_max_password_age",
+ "ram_password_policy_max_login_attempts",
+ "ram_policy_attached_only_to_group_or_roles",
+ "ram_policy_no_administrative_privileges"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art6",
+ "name": "ICT risk management framework",
+ "description": "Financial entities shall have an ICT risk management framework that is sound, comprehensive and well-documented, enabling them to address ICT risk quickly, efficiently and comprehensively and to ensure a high level of digital operational resilience. This includes continuous configuration recording, security findings aggregation and an enterprise-wide visibility plane.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 6",
+ "ArticleTitle": "ICT risk management framework"
+ },
+ "checks": {
+ "aws": [
+ "config_recorder_all_regions_enabled",
+ "config_recorder_using_aws_service_role",
+ "securityhub_enabled",
+ "accessanalyzer_enabled",
+ "accessanalyzer_enabled_without_findings",
+ "organizations_delegated_administrators",
+ "guardduty_centrally_managed",
+ "guardduty_delegated_admin_enabled_all_regions"
+ ],
+ "azure": [
+ "defender_ensure_defender_for_server_is_on",
+ "defender_ensure_defender_for_containers_is_on",
+ "defender_ensure_defender_for_storage_is_on",
+ "defender_ensure_defender_for_app_services_is_on",
+ "defender_ensure_defender_for_azure_sql_databases_is_on",
+ "defender_ensure_defender_for_sql_servers_is_on",
+ "defender_ensure_defender_for_databases_is_on",
+ "defender_ensure_defender_for_os_relational_databases_is_on",
+ "defender_ensure_defender_for_keyvault_is_on",
+ "defender_ensure_defender_for_arm_is_on",
+ "defender_ensure_defender_for_dns_is_on",
+ "defender_ensure_defender_for_cosmosdb_is_on",
+ "defender_ensure_mcas_is_enabled",
+ "defender_ensure_wdatp_is_enabled",
+ "defender_auto_provisioning_log_analytics_agent_vms_on",
+ "policy_ensure_asc_enforcement_enabled"
+ ],
+ "gcp": [
+ "iam_cloud_asset_inventory_enabled",
+ "iam_audit_logs_enabled",
+ "logging_sink_created",
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "iam_organization_essential_contacts_configured"
+ ],
+ "alibabacloud": [
+ "securitycenter_advanced_or_enterprise_edition",
+ "securitycenter_all_assets_agent_installed",
+ "securitycenter_vulnerability_scan_enabled",
+ "actiontrail_multi_region_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_delegated_admin_enabled_all_regions",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art7",
+ "name": "ICT systems, protocols and tools",
+ "description": "Financial entities shall use and maintain updated ICT systems, protocols and tools that are appropriate to the magnitude of operations supporting ICT functions, technologically resilient, and adequately equipped to securely process data. Cryptographic primitives, certificate hygiene and network segmentation are core to this requirement.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 7",
+ "ArticleTitle": "ICT systems, protocols and tools"
+ },
+ "checks": {
+ "aws": [
+ "acm_certificates_with_secure_key_algorithms",
+ "acm_certificates_transparency_logs_enabled",
+ "acm_certificates_expiration_check",
+ "ec2_ebs_default_encryption",
+ "kms_cmk_rotation_enabled",
+ "s3_bucket_secure_transport_policy",
+ "s3_bucket_default_encryption",
+ "s3_bucket_kms_encryption",
+ "vpc_subnet_separate_private_public",
+ "vpc_subnet_no_public_ip_by_default",
+ "elb_insecure_ssl_ciphers",
+ "elbv2_insecure_ssl_ciphers",
+ "elb_ssl_listeners",
+ "elbv2_ssl_listeners",
+ "cloudfront_distributions_using_deprecated_ssl_protocols",
+ "cloudfront_distributions_https_enabled",
+ "rds_instance_transport_encrypted"
+ ],
+ "azure": [
+ "storage_ensure_minimum_tls_version_12",
+ "storage_secure_transfer_required_is_enabled",
+ "storage_smb_channel_encryption_with_secure_algorithm",
+ "storage_smb_protocol_version_is_latest",
+ "app_minimum_tls_version_12",
+ "app_ensure_http_is_redirected_to_https",
+ "app_ensure_using_http20",
+ "sqlserver_recommended_minimal_tls_version",
+ "mysql_flexible_server_minimum_tls_version_12",
+ "mysql_flexible_server_ssl_connection_enabled",
+ "postgresql_flexible_server_enforce_ssl_enabled",
+ "keyvault_key_rotation_enabled",
+ "storage_key_rotation_90_days",
+ "aks_network_policy_enabled"
+ ],
+ "gcp": [
+ "cloudsql_instance_ssl_connections",
+ "compute_instance_encryption_with_csek_enabled",
+ "compute_instance_confidential_computing_enabled",
+ "bigquery_dataset_cmk_encryption",
+ "bigquery_table_cmk_encryption",
+ "dataproc_encrypted_with_cmks_disabled",
+ "kms_key_rotation_enabled",
+ "kms_key_rotation_max_90_days",
+ "dns_dnssec_disabled",
+ "dns_rsasha1_in_use_to_key_sign_in_dnssec",
+ "dns_rsasha1_in_use_to_zone_sign_in_dnssec",
+ "compute_network_not_legacy",
+ "compute_network_default_in_use",
+ "compute_instance_single_network_interface"
+ ],
+ "cloudflare": [
+ "zone_universal_ssl_enabled",
+ "zone_ssl_strict",
+ "zone_min_tls_version_secure",
+ "zone_tls_1_3_enabled",
+ "zone_hsts_enabled",
+ "zone_https_redirect_enabled",
+ "zone_automatic_https_rewrites_enabled",
+ "zone_development_mode_disabled",
+ "zone_record_caa_exists",
+ "zone_dnssec_enabled"
+ ],
+ "alibabacloud": [
+ "oss_bucket_secure_transport_enabled",
+ "rds_instance_ssl_enabled",
+ "rds_instance_tde_enabled",
+ "rds_instance_tde_key_custom",
+ "ecs_attached_disk_encrypted",
+ "ecs_unattached_disk_encrypted",
+ "ecs_instance_no_legacy_network"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "Provider": "aws",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": [
+ "RSA-1024",
+ "P-192"
+ ]
+ },
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "Provider": "azure",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": [
+ "1.2",
+ "1.3"
+ ]
+ },
+ {
+ "Check": "storage_smb_channel_encryption_with_secure_algorithm",
+ "Provider": "azure",
+ "ConfigKey": "recommended_smb_channel_encryption_algorithms",
+ "Operator": "subset",
+ "Value": [
+ "AES-256-GCM"
+ ]
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art8",
+ "name": "Identification",
+ "description": "Financial entities shall identify, classify and adequately document all ICT supported business functions, roles and responsibilities, the information assets and ICT assets supporting them, and their interdependencies. They shall on a continuous basis identify all sources of ICT risk, in particular the risk exposure to and from other financial entities.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 8",
+ "ArticleTitle": "Identification"
+ },
+ "checks": {
+ "aws": [
+ "accessanalyzer_enabled",
+ "accessanalyzer_enabled_without_findings",
+ "macie_is_enabled",
+ "macie_automated_sensitive_data_discovery_enabled",
+ "ec2_securitygroup_not_used",
+ "ec2_elastic_ip_unassigned",
+ "ec2_networkacl_unused",
+ "secretsmanager_secret_unused"
+ ],
+ "azure": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
+ "network_watcher_enabled",
+ "network_public_ip_shodan",
+ "vm_scaleset_not_empty"
+ ],
+ "gcp": [
+ "iam_cloud_asset_inventory_enabled",
+ "iam_service_account_unused",
+ "iam_sa_user_managed_key_unused",
+ "apikeys_key_exists",
+ "compute_instance_suspended_without_persistent_disks",
+ "compute_public_address_shodan"
+ ],
+ "cloudflare": [
+ "dns_record_no_wildcard",
+ "dns_record_no_internal_ip",
+ "dns_record_cname_target_valid"
+ ],
+ "alibabacloud": [
+ "securitycenter_all_assets_agent_installed",
+ "ram_user_console_access_unused"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art9",
+ "name": "Protection and prevention",
+ "description": "Financial entities shall continuously monitor and control the security and functioning of ICT systems and tools and minimise the impact of ICT risk by deploying appropriate ICT security tools, policies and procedures. Encryption at rest and in transit, blocking of public exposure, network access controls, secret management and instance hardening are central to this article.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 9",
+ "ArticleTitle": "Protection and prevention"
+ },
+ "checks": {
+ "aws": [
+ "kms_key_not_publicly_accessible",
+ "ec2_ebs_volume_encryption",
+ "ec2_ebs_snapshots_encrypted",
+ "ec2_ebs_public_snapshot",
+ "ec2_ebs_snapshot_account_block_public_access",
+ "s3_account_level_public_access_blocks",
+ "s3_bucket_level_public_access_block",
+ "s3_bucket_public_access",
+ "s3_bucket_policy_public_write_access",
+ "s3_bucket_public_write_acl",
+ "s3_bucket_public_list_acl",
+ "s3_bucket_acl_prohibited",
+ "s3_access_point_public_access_block",
+ "ec2_securitygroup_default_restrict_traffic",
+ "ec2_securitygroup_allow_ingress_from_internet_to_all_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_any_port",
+ "ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22",
+ "ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_3389",
+ "rds_instance_storage_encrypted",
+ "rds_cluster_storage_encrypted",
+ "rds_instance_no_public_access",
+ "rds_snapshots_public_access",
+ "secretsmanager_not_publicly_accessible",
+ "secretsmanager_has_restrictive_resource_policy",
+ "secretsmanager_automatic_rotation_enabled",
+ "dynamodb_tables_kms_cmk_encryption_enabled",
+ "sns_topics_kms_encryption_at_rest_enabled",
+ "sns_topics_not_publicly_accessible",
+ "ec2_instance_imdsv2_enabled",
+ "ec2_instance_account_imdsv2_enabled",
+ "efs_encryption_at_rest_enabled",
+ "awslambda_function_not_publicly_accessible"
+ ],
+ "azure": [
+ "storage_account_public_network_access_disabled",
+ "storage_blob_public_access_level_is_disabled",
+ "storage_default_network_access_rule_is_denied",
+ "storage_ensure_private_endpoints_in_storage_accounts",
+ "storage_ensure_encryption_with_customer_managed_keys",
+ "storage_infrastructure_encryption_is_enabled",
+ "storage_account_key_access_disabled",
+ "storage_default_to_entra_authorization_enabled",
+ "containerregistry_not_publicly_accessible",
+ "containerregistry_uses_private_link",
+ "cosmosdb_account_use_private_endpoints",
+ "cosmosdb_account_firewall_use_selected_networks",
+ "keyvault_private_endpoints",
+ "keyvault_access_only_through_private_endpoints",
+ "keyvault_rbac_enabled",
+ "app_function_not_publicly_accessible",
+ "aisearch_service_not_publicly_accessible",
+ "aks_clusters_public_access_disabled",
+ "aks_clusters_created_with_private_nodes",
+ "sqlserver_unrestricted_inbound_access",
+ "postgresql_flexible_server_allow_access_services_disabled",
+ "vm_ensure_attached_disks_encrypted_with_cmk",
+ "vm_ensure_unattached_disks_encrypted_with_cmk",
+ "vm_ensure_using_managed_disks",
+ "vm_trusted_launch_enabled",
+ "vm_linux_enforce_ssh_authentication",
+ "vm_jit_access_enabled",
+ "sqlserver_tde_encryption_enabled",
+ "sqlserver_tde_encrypted_with_cmk",
+ "databricks_workspace_cmk_encryption_enabled",
+ "network_ssh_internet_access_restricted",
+ "network_rdp_internet_access_restricted",
+ "network_http_internet_access_restricted",
+ "network_udp_internet_access_restricted",
+ "network_bastion_host_exists"
+ ],
+ "gcp": [
+ "kms_key_not_publicly_accessible",
+ "bigquery_dataset_public_access",
+ "bigquery_dataset_cmk_encryption",
+ "bigquery_table_cmk_encryption",
+ "cloudstorage_bucket_public_access",
+ "cloudstorage_bucket_uniform_bucket_level_access",
+ "cloudstorage_uses_vpc_service_controls",
+ "cloudsql_instance_public_access",
+ "cloudsql_instance_public_ip",
+ "cloudsql_instance_private_ip_assignment",
+ "cloudsql_instance_ssl_connections",
+ "cloudsql_instance_cmek_encryption_enabled",
+ "compute_firewall_ssh_access_from_the_internet_allowed",
+ "compute_firewall_rdp_access_from_the_internet_allowed",
+ "compute_instance_public_ip",
+ "compute_instance_shielded_vm_enabled",
+ "compute_instance_confidential_computing_enabled",
+ "compute_instance_serial_ports_in_use",
+ "compute_instance_block_project_wide_ssh_keys_disabled",
+ "compute_instance_ip_forwarding_is_enabled",
+ "compute_instance_encryption_with_csek_enabled",
+ "compute_image_not_publicly_shared",
+ "dataproc_encrypted_with_cmks_disabled",
+ "kms_key_rotation_enabled",
+ "gke_cluster_no_default_service_account",
+ "cloudfunction_function_inside_vpc",
+ "apikeys_api_restrictions_configured",
+ "apikeys_api_restricted_with_gemini_api",
+ "cloudsql_instance_mysql_local_infile_flag",
+ "cloudsql_instance_mysql_skip_show_database_flag",
+ "cloudsql_instance_sqlserver_contained_database_authentication_flag",
+ "cloudsql_instance_sqlserver_cross_db_ownership_chaining_flag",
+ "cloudsql_instance_sqlserver_external_scripts_enabled_flag",
+ "cloudsql_instance_sqlserver_remote_access_flag",
+ "cloudsql_instance_sqlserver_trace_flag",
+ "cloudsql_instance_sqlserver_user_connections_flag",
+ "cloudsql_instance_sqlserver_user_options_flag"
+ ],
+ "cloudflare": [
+ "zone_universal_ssl_enabled",
+ "zone_ssl_strict",
+ "zone_min_tls_version_secure",
+ "zone_tls_1_3_enabled",
+ "zone_hsts_enabled",
+ "zone_https_redirect_enabled",
+ "zone_automatic_https_rewrites_enabled",
+ "zone_record_caa_exists",
+ "zone_dnssec_enabled",
+ "zone_waf_enabled",
+ "zone_waf_owasp_ruleset_enabled",
+ "zone_firewall_blocking_rules_configured",
+ "zone_browser_integrity_check_enabled",
+ "zone_bot_fight_mode_enabled",
+ "zone_rate_limiting_enabled",
+ "zone_challenge_passage_configured",
+ "zone_ip_geolocation_enabled",
+ "dns_record_proxied",
+ "dns_record_no_internal_ip",
+ "dns_record_no_wildcard",
+ "dns_record_cname_target_valid",
+ "zone_record_spf_exists",
+ "zone_record_dkim_exists",
+ "zone_record_dmarc_exists"
+ ],
+ "alibabacloud": [
+ "oss_bucket_not_publicly_accessible",
+ "oss_bucket_secure_transport_enabled",
+ "actiontrail_oss_bucket_not_publicly_accessible",
+ "ecs_attached_disk_encrypted",
+ "ecs_unattached_disk_encrypted",
+ "ecs_securitygroup_restrict_ssh_internet",
+ "ecs_securitygroup_restrict_rdp_internet",
+ "ecs_instance_endpoint_protection_installed",
+ "rds_instance_no_public_access_whitelist",
+ "rds_instance_ssl_enabled",
+ "rds_instance_tde_enabled",
+ "rds_instance_tde_key_custom",
+ "cs_kubernetes_network_policy_enabled",
+ "cs_kubernetes_eni_multiple_ip_enabled",
+ "cs_kubernetes_private_cluster_enabled",
+ "cs_kubernetes_rbac_enabled",
+ "cs_kubernetes_dashboard_disabled"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art10",
+ "name": "Detection",
+ "description": "Financial entities shall have in place mechanisms to promptly detect anomalous activities, including ICT network performance issues and ICT-related incidents, and to identify potential single points of failure. Threat detection across compute, identity, storage and the API control plane is required for timely detection.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 10",
+ "ArticleTitle": "Detection"
+ },
+ "checks": {
+ "aws": [
+ "guardduty_is_enabled",
+ "guardduty_no_high_severity_findings",
+ "guardduty_ec2_malware_protection_enabled",
+ "guardduty_lambda_protection_enabled",
+ "guardduty_rds_protection_enabled",
+ "guardduty_s3_protection_enabled",
+ "guardduty_eks_audit_log_enabled",
+ "guardduty_eks_runtime_monitoring_enabled",
+ "securityhub_enabled",
+ "cloudtrail_threat_detection_enumeration",
+ "cloudtrail_threat_detection_llm_jacking",
+ "cloudtrail_threat_detection_privilege_escalation",
+ "cloudtrail_insights_exist",
+ "inspector2_is_enabled",
+ "inspector2_active_findings_exist",
+ "ec2_elastic_ip_shodan"
+ ],
+ "azure": [
+ "defender_ensure_defender_for_server_is_on",
+ "defender_ensure_defender_for_containers_is_on",
+ "defender_ensure_defender_for_storage_is_on",
+ "defender_ensure_defender_for_keyvault_is_on",
+ "defender_ensure_defender_for_arm_is_on",
+ "defender_ensure_defender_for_dns_is_on",
+ "defender_ensure_defender_for_azure_sql_databases_is_on",
+ "defender_ensure_defender_for_sql_servers_is_on",
+ "defender_ensure_wdatp_is_enabled",
+ "defender_ensure_mcas_is_enabled",
+ "defender_container_images_scan_enabled",
+ "defender_container_images_resolved_vulnerabilities",
+ "sqlserver_microsoft_defender_enabled",
+ "apim_threat_detection_llm_jacking"
+ ],
+ "gcp": [
+ "compute_public_address_shodan",
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "compute_subnet_flow_logs_enabled",
+ "compute_network_dns_logging_enabled",
+ "cloudstorage_bucket_logging_enabled",
+ "compute_loadbalancer_logging_enabled",
+ "logging_sink_created"
+ ],
+ "cloudflare": [
+ "zone_bot_fight_mode_enabled",
+ "zone_browser_integrity_check_enabled",
+ "zone_rate_limiting_enabled"
+ ],
+ "alibabacloud": [
+ "securitycenter_vulnerability_scan_enabled",
+ "securitycenter_notification_enabled_high_risk",
+ "securitycenter_all_assets_agent_installed",
+ "ecs_instance_endpoint_protection_installed",
+ "cs_kubernetes_cloudmonitor_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art11",
+ "name": "Response and recovery",
+ "description": "Financial entities shall put in place a comprehensive ICT business continuity policy, including ICT response and recovery plans, that ensures the continuity of ICT-supported critical or important functions. Operational alarming, automated event routing and tested recovery actions are essential.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 11",
+ "ArticleTitle": "Response and recovery"
+ },
+ "checks": {
+ "aws": [
+ "cloudwatch_alarm_actions_enabled",
+ "cloudwatch_alarm_actions_alarm_state_configured",
+ "eventbridge_global_endpoint_event_replication_enabled",
+ "sns_subscription_not_using_http_endpoints",
+ "backup_plans_exist",
+ "backup_vaults_exist",
+ "rds_instance_critical_event_subscription",
+ "rds_cluster_critical_event_subscription"
+ ],
+ "azure": [
+ "monitor_alert_service_health_exists",
+ "monitor_alert_create_update_security_solution",
+ "monitor_alert_delete_security_solution",
+ "defender_additional_email_configured_with_a_security_contact",
+ "defender_ensure_notify_alerts_severity_is_high",
+ "defender_ensure_notify_emails_to_owners",
+ "defender_attack_path_notifications_properly_configured",
+ "vm_backup_enabled",
+ "vm_sufficient_daily_backup_retention_period"
+ ],
+ "gcp": [
+ "compute_instance_automatic_restart_enabled",
+ "compute_instance_group_autohealing_enabled",
+ "compute_instance_on_host_maintenance_migrate",
+ "cloudsql_instance_high_availability_enabled",
+ "cloudsql_instance_automated_backups",
+ "compute_instance_deletion_protection_enabled",
+ "compute_instance_group_load_balancer_attached",
+ "compute_instance_preemptible_vm_disabled"
+ ],
+ "alibabacloud": [
+ "securitycenter_notification_enabled_high_risk",
+ "cs_kubernetes_cluster_check_recent",
+ "cs_kubernetes_cluster_check_weekly"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art12",
+ "name": "Backup policies and procedures, restoration and recovery procedures and methods",
+ "description": "Financial entities shall develop and document backup policies and procedures specifying the scope of data subject to backup and the minimum frequency of the backup, as well as restoration and recovery procedures and methods. Backups must be encrypted, retained, and resources must be designed for recoverability across availability zones and regions.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 12",
+ "ArticleTitle": "Backup policies and procedures, restoration and recovery procedures and methods"
+ },
+ "checks": {
+ "aws": [
+ "backup_plans_exist",
+ "backup_vaults_exist",
+ "backup_vaults_encrypted",
+ "backup_recovery_point_encrypted",
+ "backup_reportplans_exist",
+ "rds_instance_backup_enabled",
+ "rds_cluster_protected_by_backup_plan",
+ "rds_instance_protected_by_backup_plan",
+ "rds_instance_multi_az",
+ "rds_cluster_multi_az",
+ "rds_cluster_backtrack_enabled",
+ "rds_instance_deletion_protection",
+ "rds_cluster_deletion_protection",
+ "rds_snapshots_encrypted",
+ "s3_bucket_object_versioning",
+ "s3_bucket_object_lock",
+ "s3_bucket_cross_region_replication",
+ "s3_bucket_no_mfa_delete",
+ "dynamodb_tables_pitr_enabled",
+ "dynamodb_table_deletion_protection_enabled",
+ "ec2_ebs_volume_protected_by_backup_plan",
+ "ec2_ebs_volume_snapshots_exists",
+ "autoscaling_group_multiple_az",
+ "elb_is_in_multiple_az",
+ "elbv2_is_in_multiple_az",
+ "cloudfront_distributions_multiple_origin_failover_configured",
+ "dynamodb_table_protected_by_backup_plan"
+ ],
+ "azure": [
+ "vm_backup_enabled",
+ "vm_sufficient_daily_backup_retention_period",
+ "vm_ensure_using_managed_disks",
+ "storage_ensure_soft_delete_is_enabled",
+ "storage_ensure_file_shares_soft_delete_is_enabled",
+ "storage_blob_versioning_is_enabled",
+ "storage_geo_redundant_enabled",
+ "keyvault_recoverable"
+ ],
+ "gcp": [
+ "cloudsql_instance_automated_backups",
+ "cloudsql_instance_high_availability_enabled",
+ "cloudstorage_bucket_versioning_enabled",
+ "cloudstorage_bucket_soft_delete_enabled",
+ "cloudstorage_bucket_lifecycle_management_enabled",
+ "cloudstorage_bucket_sufficient_retention_period",
+ "compute_instance_group_multiple_zones",
+ "compute_instance_disk_auto_delete_disabled",
+ "compute_instance_deletion_protection_enabled",
+ "compute_snapshot_not_outdated",
+ "compute_instance_suspended_without_persistent_disks"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art13",
+ "name": "Learning and evolving",
+ "description": "Financial entities shall have in place capabilities and staff to gather information on vulnerabilities and cyber threats, perform post ICT-related incident reviews, and continuously feed lessons learnt back into the ICT risk assessment process. Findings aggregation and continuous insights drive this cycle.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 13",
+ "ArticleTitle": "Learning and evolving"
+ },
+ "checks": {
+ "aws": [
+ "securityhub_enabled",
+ "guardduty_no_high_severity_findings",
+ "inspector2_active_findings_exist",
+ "accessanalyzer_enabled_without_findings",
+ "cloudtrail_insights_exist"
+ ],
+ "azure": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
+ "defender_assessments_vm_endpoint_protection_installed",
+ "defender_container_images_resolved_vulnerabilities",
+ "defender_container_images_scan_enabled",
+ "defender_ensure_system_updates_are_applied",
+ "sqlserver_vulnerability_assessment_enabled",
+ "sqlserver_va_periodic_recurring_scans_enabled",
+ "sqlserver_va_scan_reports_configured"
+ ],
+ "gcp": [
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "iam_cloud_asset_inventory_enabled",
+ "logging_sink_created"
+ ],
+ "alibabacloud": [
+ "securitycenter_vulnerability_scan_enabled",
+ "securitycenter_all_assets_agent_installed",
+ "ecs_instance_latest_os_patches_applied"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art14",
+ "name": "Communication",
+ "description": "As part of the ICT risk management framework, financial entities shall have in place crisis communication plans enabling a responsible disclosure of ICT-related incidents or major vulnerabilities to clients, counterparts and the public. Reliable, encrypted and access-controlled notification channels are required.",
+ "attributes": {
+ "Pillar": "ICT Risk Management",
+ "Article": "Article 14",
+ "ArticleTitle": "Communication"
+ },
+ "checks": {
+ "aws": [
+ "sns_topics_kms_encryption_at_rest_enabled",
+ "sns_topics_not_publicly_accessible",
+ "sns_subscription_not_using_http_endpoints",
+ "eventbridge_bus_exposed",
+ "eventbridge_bus_cross_account_access",
+ "eventbridge_schema_registry_cross_account_access",
+ "cloudwatch_alarm_actions_enabled",
+ "cloudwatch_alarm_actions_alarm_state_configured"
+ ],
+ "azure": [
+ "defender_additional_email_configured_with_a_security_contact",
+ "defender_ensure_notify_emails_to_owners",
+ "defender_ensure_notify_alerts_severity_is_high",
+ "defender_attack_path_notifications_properly_configured",
+ "monitor_alert_service_health_exists"
+ ],
+ "gcp": [
+ "iam_organization_essential_contacts_configured",
+ "logging_sink_created",
+ "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled"
+ ],
+ "alibabacloud": [
+ "securitycenter_notification_enabled_high_risk"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art17",
+ "name": "ICT-related incident management process",
+ "description": "Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents. Comprehensive trail logging, log integrity protection, retention and centralisation of ICT events are foundational requirements.",
+ "attributes": {
+ "Pillar": "ICT-Related Incident Reporting",
+ "Article": "Article 17",
+ "ArticleTitle": "ICT-related incident management process"
+ },
+ "checks": {
+ "aws": [
+ "cloudtrail_multi_region_enabled",
+ "cloudtrail_multi_region_enabled_logging_management_events",
+ "cloudtrail_kms_encryption_enabled",
+ "cloudtrail_log_file_validation_enabled",
+ "cloudtrail_cloudwatch_logging_enabled",
+ "cloudtrail_logs_s3_bucket_access_logging_enabled",
+ "cloudtrail_logs_s3_bucket_is_not_publicly_accessible",
+ "cloudtrail_s3_dataevents_read_enabled",
+ "cloudtrail_s3_dataevents_write_enabled",
+ "cloudtrail_bucket_requires_mfa_delete",
+ "cloudtrail_bedrock_logging_enabled",
+ "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "cloudwatch_log_group_kms_encryption_enabled",
+ "cloudwatch_log_group_no_secrets_in_logs",
+ "cloudwatch_log_group_not_publicly_accessible",
+ "vpc_flow_logs_enabled",
+ "ec2_client_vpn_endpoint_connection_logging_enabled",
+ "route53_public_hosted_zones_cloudwatch_logging_enabled",
+ "elb_logging_enabled",
+ "elbv2_logging_enabled",
+ "cloudfront_distributions_logging_enabled",
+ "s3_bucket_server_access_logging_enabled"
+ ],
+ "azure": [
+ "monitor_diagnostic_settings_exists",
+ "monitor_diagnostic_setting_with_appropriate_categories",
+ "monitor_storage_account_with_activity_logs_is_private",
+ "monitor_storage_account_with_activity_logs_cmk_encrypted",
+ "network_flow_log_captured_sent",
+ "network_flow_log_more_than_90_days",
+ "keyvault_logging_enabled",
+ "sqlserver_auditing_enabled",
+ "sqlserver_auditing_retention_90_days",
+ "mysql_flexible_server_audit_log_enabled",
+ "mysql_flexible_server_audit_log_connection_activated",
+ "postgresql_flexible_server_log_checkpoints_on",
+ "postgresql_flexible_server_log_connections_on",
+ "postgresql_flexible_server_log_disconnections_on",
+ "postgresql_flexible_server_log_retention_days_greater_3",
+ "app_http_logs_enabled",
+ "app_function_application_insights_enabled",
+ "appinsights_ensure_is_configured"
+ ],
+ "gcp": [
+ "iam_audit_logs_enabled",
+ "cloudstorage_audit_logs_enabled",
+ "logging_sink_created",
+ "cloudstorage_bucket_logging_enabled",
+ "cloudstorage_bucket_log_retention_policy_lock",
+ "cloudstorage_bucket_sufficient_retention_period",
+ "compute_subnet_flow_logs_enabled",
+ "compute_network_dns_logging_enabled",
+ "compute_loadbalancer_logging_enabled",
+ "cloudsql_instance_postgres_enable_pgaudit_flag",
+ "cloudsql_instance_postgres_log_connections_flag",
+ "cloudsql_instance_postgres_log_disconnections_flag",
+ "cloudsql_instance_postgres_log_statement_flag",
+ "cloudsql_instance_postgres_log_min_messages_flag",
+ "cloudsql_instance_postgres_log_error_verbosity_flag",
+ "cloudsql_instance_postgres_log_min_error_statement_flag",
+ "cloudsql_instance_postgres_log_min_duration_statement_flag"
+ ],
+ "alibabacloud": [
+ "actiontrail_multi_region_enabled",
+ "actiontrail_oss_bucket_not_publicly_accessible",
+ "oss_bucket_logging_enabled",
+ "sls_logstore_retention_period",
+ "vpc_flow_logs_enabled",
+ "cs_kubernetes_log_service_enabled",
+ "rds_instance_sql_audit_enabled",
+ "rds_instance_sql_audit_retention",
+ "rds_instance_postgresql_log_connections_enabled",
+ "rds_instance_postgresql_log_disconnections_enabled",
+ "rds_instance_postgresql_log_duration_enabled"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art18",
+ "name": "Classification of ICT-related incidents and cyber threats",
+ "description": "Financial entities shall classify ICT-related incidents and shall determine their impact based on criteria such as the number of clients affected, duration, geographical spread, data losses, and criticality of the services affected. Severity-aware threat detection across the estate underpins this classification.",
+ "attributes": {
+ "Pillar": "ICT-Related Incident Reporting",
+ "Article": "Article 18",
+ "ArticleTitle": "Classification of ICT-related incidents and cyber threats"
+ },
+ "checks": {
+ "aws": [
+ "guardduty_no_high_severity_findings",
+ "guardduty_centrally_managed",
+ "guardduty_delegated_admin_enabled_all_regions",
+ "securityhub_enabled",
+ "inspector2_active_findings_exist",
+ "accessanalyzer_enabled_without_findings",
+ "cloudtrail_threat_detection_enumeration",
+ "cloudtrail_threat_detection_llm_jacking",
+ "cloudtrail_threat_detection_privilege_escalation"
+ ],
+ "azure": [
+ "defender_ensure_notify_alerts_severity_is_high",
+ "defender_attack_path_notifications_properly_configured",
+ "defender_ensure_defender_for_server_is_on",
+ "defender_ensure_wdatp_is_enabled",
+ "defender_ensure_mcas_is_enabled",
+ "sqlserver_microsoft_defender_enabled",
+ "apim_threat_detection_llm_jacking"
+ ],
+ "gcp": [
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "compute_public_address_shodan",
+ "iam_cloud_asset_inventory_enabled",
+ "iam_audit_logs_enabled"
+ ],
+ "alibabacloud": [
+ "securitycenter_notification_enabled_high_risk",
+ "securitycenter_vulnerability_scan_enabled"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_delegated_admin_enabled_all_regions",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art19",
+ "name": "Reporting of major ICT-related incidents and voluntary notification of significant cyber threats",
+ "description": "Financial entities shall report major ICT-related incidents to the relevant competent authority and may, on a voluntary basis, notify significant cyber threats. Detective metric filters, change-tracking alarms and reliable notification topics are needed to surface and route reportable events.",
+ "attributes": {
+ "Pillar": "ICT-Related Incident Reporting",
+ "Article": "Article 19",
+ "ArticleTitle": "Reporting of major ICT-related incidents and voluntary notification of significant cyber threats"
+ },
+ "checks": {
+ "aws": [
+ "cloudwatch_log_metric_filter_authentication_failures",
+ "cloudwatch_log_metric_filter_unauthorized_api_calls",
+ "cloudwatch_log_metric_filter_root_usage",
+ "cloudwatch_log_metric_filter_sign_in_without_mfa",
+ "cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk",
+ "cloudwatch_log_metric_filter_for_s3_bucket_policy_changes",
+ "cloudwatch_log_metric_filter_policy_changes",
+ "cloudwatch_log_metric_filter_security_group_changes",
+ "cloudwatch_log_metric_filter_aws_organizations_changes",
+ "cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled",
+ "cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled",
+ "cloudwatch_changes_to_network_acls_alarm_configured",
+ "cloudwatch_changes_to_network_gateways_alarm_configured",
+ "cloudwatch_changes_to_network_route_tables_alarm_configured",
+ "cloudwatch_changes_to_vpcs_alarm_configured",
+ "sns_subscription_not_using_http_endpoints"
+ ],
+ "azure": [
+ "monitor_alert_create_policy_assignment",
+ "monitor_alert_delete_policy_assignment",
+ "monitor_alert_create_update_nsg",
+ "monitor_alert_delete_nsg",
+ "monitor_alert_create_update_security_solution",
+ "monitor_alert_delete_security_solution",
+ "monitor_alert_create_update_sqlserver_fr",
+ "monitor_alert_delete_sqlserver_fr",
+ "monitor_alert_create_update_public_ip_address_rule",
+ "monitor_alert_delete_public_ip_address_rule",
+ "monitor_alert_service_health_exists",
+ "defender_additional_email_configured_with_a_security_contact"
+ ],
+ "gcp": [
+ "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled",
+ "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled",
+ "iam_organization_essential_contacts_configured",
+ "logging_sink_created"
+ ],
+ "alibabacloud": [
+ "sls_management_console_authentication_failures_alert_enabled",
+ "sls_management_console_signin_without_mfa_alert_enabled",
+ "sls_root_account_usage_alert_enabled",
+ "sls_unauthorized_api_calls_alert_enabled",
+ "sls_ram_role_changes_alert_enabled",
+ "sls_oss_bucket_policy_changes_alert_enabled",
+ "sls_oss_permission_changes_alert_enabled",
+ "sls_rds_instance_configuration_changes_alert_enabled",
+ "sls_security_group_changes_alert_enabled",
+ "sls_vpc_changes_alert_enabled",
+ "sls_vpc_network_route_changes_alert_enabled",
+ "sls_cloud_firewall_changes_alert_enabled",
+ "sls_customer_created_cmk_changes_alert_enabled"
+ ]
+ }
+ },
+ {
+ "id": "DORA-Art24",
+ "name": "General requirements for the performance of digital operational resilience testing",
+ "description": "Financial entities shall establish, maintain and review a sound and comprehensive digital operational resilience testing programme, as an integral part of the ICT risk management framework. Continuous vulnerability discovery, configuration assessment and instance manageability are foundational.",
+ "attributes": {
+ "Pillar": "Digital Operational Resilience Testing",
+ "Article": "Article 24",
+ "ArticleTitle": "General requirements for the performance of digital operational resilience testing"
+ },
+ "checks": {
+ "aws": [
+ "inspector2_is_enabled",
+ "inspector2_active_findings_exist",
+ "securityhub_enabled",
+ "ec2_instance_managed_by_ssm",
+ "ec2_instance_with_outdated_ami",
+ "ssm_managed_compliant_patching"
+ ],
+ "azure": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
+ "defender_ensure_system_updates_are_applied",
+ "defender_container_images_scan_enabled",
+ "defender_assessments_vm_endpoint_protection_installed",
+ "sqlserver_vulnerability_assessment_enabled",
+ "sqlserver_va_periodic_recurring_scans_enabled",
+ "vm_ensure_using_approved_images",
+ "vm_desired_sku_size"
+ ],
+ "gcp": [
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "compute_instance_shielded_vm_enabled",
+ "compute_snapshot_not_outdated",
+ "compute_public_address_shodan"
+ ],
+ "alibabacloud": [
+ "securitycenter_vulnerability_scan_enabled",
+ "securitycenter_advanced_or_enterprise_edition",
+ "ecs_instance_latest_os_patches_applied",
+ "cs_kubernetes_cluster_check_recent",
+ "cs_kubernetes_cluster_check_weekly"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art25",
+ "name": "Testing of ICT tools and systems",
+ "description": "Financial entities shall ensure that tests are undertaken on ICT tools and systems, on critical ICT systems supporting all critical or important functions, at least yearly. Vulnerability assessments, deprecated component detection and certificate hygiene must be tracked.",
+ "attributes": {
+ "Pillar": "Digital Operational Resilience Testing",
+ "Article": "Article 25",
+ "ArticleTitle": "Testing of ICT tools and systems"
+ },
+ "checks": {
+ "aws": [
+ "inspector2_is_enabled",
+ "inspector2_active_findings_exist",
+ "guardduty_is_enabled",
+ "guardduty_no_high_severity_findings",
+ "config_recorder_all_regions_enabled",
+ "ec2_instance_with_outdated_ami",
+ "ec2_instance_managed_by_ssm",
+ "ec2_instance_paravirtual_type",
+ "rds_instance_deprecated_engine_version",
+ "acm_certificates_expiration_check",
+ "rds_instance_certificate_expiration",
+ "iam_no_expired_server_certificates_stored",
+ "ssm_managed_compliant_patching"
+ ],
+ "azure": [
+ "defender_auto_provisioning_vulnerabilty_assessments_machines_on",
+ "defender_container_images_resolved_vulnerabilities",
+ "sqlserver_vulnerability_assessment_enabled",
+ "sqlserver_va_periodic_recurring_scans_enabled",
+ "sqlserver_va_scan_reports_configured",
+ "sqlserver_va_emails_notifications_admins_enabled",
+ "keyvault_key_expiration_set_in_non_rbac",
+ "keyvault_rbac_key_expiration_set",
+ "keyvault_non_rbac_secret_expiration_set",
+ "keyvault_rbac_secret_expiration_set",
+ "app_ensure_java_version_is_latest",
+ "app_ensure_php_version_is_latest",
+ "app_ensure_python_version_is_latest",
+ "app_function_latest_runtime_version",
+ "storage_smb_protocol_version_is_latest"
+ ],
+ "gcp": [
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "compute_snapshot_not_outdated",
+ "compute_network_not_legacy",
+ "dns_rsasha1_in_use_to_key_sign_in_dnssec",
+ "dns_rsasha1_in_use_to_zone_sign_in_dnssec",
+ "apikeys_key_rotated_in_90_days",
+ "iam_sa_user_managed_key_rotate_90_days"
+ ],
+ "cloudflare": [
+ "zone_min_tls_version_secure"
+ ],
+ "alibabacloud": [
+ "securitycenter_vulnerability_scan_enabled",
+ "ecs_instance_latest_os_patches_applied",
+ "ecs_instance_no_legacy_network"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "config_recorder_all_regions_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art28",
+ "name": "General principles (ICT third-party risk)",
+ "description": "Financial entities shall manage ICT third-party risk as an integral component of ICT risk within their ICT risk management framework. Cross-account access, trust boundaries, organization-level controls and dependency visibility are critical to monitor third-party exposure on AWS.",
+ "attributes": {
+ "Pillar": "ICT Third-Party Risk Management",
+ "Article": "Article 28",
+ "ArticleTitle": "General principles (ICT third-party risk)"
+ },
+ "checks": {
+ "aws": [
+ "iam_role_cross_service_confused_deputy_prevention",
+ "iam_role_cross_account_readonlyaccess_policy",
+ "iam_no_custom_policy_permissive_role_assumption",
+ "accessanalyzer_enabled",
+ "accessanalyzer_enabled_without_findings",
+ "s3_bucket_cross_account_access",
+ "dynamodb_table_cross_account_access",
+ "eventbridge_bus_cross_account_access",
+ "eventbridge_schema_registry_cross_account_access",
+ "cloudwatch_cross_account_sharing_disabled",
+ "organizations_delegated_administrators",
+ "organizations_account_part_of_organizations",
+ "organizations_scp_check_deny_regions",
+ "vpc_endpoint_connections_trust_boundaries",
+ "vpc_endpoint_services_allowed_principals_trust_boundaries",
+ "vpc_peering_routing_tables_with_least_privilege",
+ "awslambda_function_using_cross_account_layers"
+ ],
+ "azure": [
+ "entra_policy_guest_users_access_restrictions",
+ "entra_policy_guest_invite_only_for_admin_roles",
+ "entra_policy_restricts_user_consent_for_apps",
+ "entra_policy_user_consent_for_verified_apps",
+ "storage_cross_tenant_replication_disabled",
+ "containerregistry_uses_private_link",
+ "cosmosdb_account_use_private_endpoints",
+ "keyvault_access_only_through_private_endpoints",
+ "aks_clusters_created_with_private_nodes"
+ ],
+ "gcp": [
+ "bigquery_dataset_public_access",
+ "cloudstorage_bucket_public_access",
+ "kms_key_not_publicly_accessible",
+ "cloudstorage_uses_vpc_service_controls",
+ "cloudfunction_function_inside_vpc",
+ "iam_sa_no_user_managed_keys",
+ "iam_sa_no_administrative_privileges",
+ "iam_no_service_roles_at_project_level",
+ "apikeys_api_restrictions_configured",
+ "apikeys_api_restricted_with_gemini_api",
+ "compute_image_not_publicly_shared",
+ "iam_cloud_asset_inventory_enabled"
+ ],
+ "cloudflare": [
+ "zone_record_caa_exists",
+ "dns_record_cname_target_valid"
+ ],
+ "alibabacloud": [
+ "ram_policy_no_administrative_privileges",
+ "oss_bucket_not_publicly_accessible",
+ "actiontrail_oss_bucket_not_publicly_accessible"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art30",
+ "name": "Key contractual provisions",
+ "description": "Contractual arrangements with ICT third-party service providers shall be set out in writing and include, at minimum, agreed service levels and clear allocation of rights and obligations. Privilege boundaries, least-privilege policies and absence of administrative wildcards are the technical guardrails that enforce these contractual constraints inside AWS.",
+ "attributes": {
+ "Pillar": "ICT Third-Party Risk Management",
+ "Article": "Article 30",
+ "ArticleTitle": "Key contractual provisions"
+ },
+ "checks": {
+ "aws": [
+ "iam_aws_attached_policy_no_administrative_privileges",
+ "iam_customer_attached_policy_no_administrative_privileges",
+ "iam_customer_unattached_policy_no_administrative_privileges",
+ "iam_inline_policy_no_administrative_privileges",
+ "iam_inline_policy_allows_privilege_escalation",
+ "iam_policy_allows_privilege_escalation",
+ "iam_inline_policy_no_full_access_to_cloudtrail",
+ "iam_inline_policy_no_full_access_to_kms",
+ "iam_policy_no_full_access_to_cloudtrail",
+ "iam_policy_no_full_access_to_kms",
+ "iam_role_administratoraccess_policy",
+ "iam_user_administrator_access_policy",
+ "iam_group_administrator_access_policy",
+ "iam_administrator_access_with_mfa",
+ "iam_policy_attached_only_to_group_or_roles",
+ "accessanalyzer_enabled"
+ ],
+ "azure": [
+ "iam_subscription_roles_owner_custom_not_created",
+ "iam_role_user_access_admin_restricted",
+ "iam_custom_role_has_permissions_to_administer_resource_locks",
+ "entra_global_admin_in_less_than_five_users",
+ "app_function_identity_without_admin_privileges",
+ "entra_policy_default_users_cannot_create_security_groups",
+ "entra_policy_ensure_default_user_cannot_create_apps"
+ ],
+ "gcp": [
+ "iam_sa_no_administrative_privileges",
+ "iam_no_service_roles_at_project_level",
+ "iam_role_kms_enforce_separation_of_duties",
+ "iam_role_sa_enforce_separation_of_duties",
+ "iam_sa_no_user_managed_keys",
+ "compute_instance_default_service_account_in_use",
+ "compute_instance_default_service_account_in_use_with_full_api_access",
+ "gke_cluster_no_default_service_account",
+ "iam_account_access_approval_enabled",
+ "apikeys_api_restrictions_configured"
+ ],
+ "alibabacloud": [
+ "ram_policy_no_administrative_privileges",
+ "ram_policy_attached_only_to_group_or_roles",
+ "ram_no_root_access_key"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "accessanalyzer_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ },
+ {
+ "id": "DORA-Art45",
+ "name": "Information-sharing arrangements on cyber threat information and intelligence",
+ "description": "Financial entities may exchange amongst themselves cyber threat information and intelligence, including indicators of compromise, tactics, techniques and procedures, cyber security alerts and configuration tools. Centralised threat detection, sensitive data discovery and trail-based intelligence enable participation in such information-sharing arrangements.",
+ "attributes": {
+ "Pillar": "Information Sharing",
+ "Article": "Article 45",
+ "ArticleTitle": "Information-sharing arrangements on cyber threat information and intelligence"
+ },
+ "checks": {
+ "aws": [
+ "guardduty_is_enabled",
+ "guardduty_centrally_managed",
+ "securityhub_enabled",
+ "macie_is_enabled",
+ "macie_automated_sensitive_data_discovery_enabled",
+ "cloudtrail_threat_detection_enumeration",
+ "cloudtrail_threat_detection_llm_jacking",
+ "cloudtrail_threat_detection_privilege_escalation",
+ "accessanalyzer_enabled_without_findings"
+ ],
+ "azure": [
+ "defender_ensure_mcas_is_enabled",
+ "defender_ensure_wdatp_is_enabled",
+ "defender_ensure_defender_for_server_is_on",
+ "defender_attack_path_notifications_properly_configured",
+ "sqlserver_microsoft_defender_enabled",
+ "apim_threat_detection_llm_jacking"
+ ],
+ "gcp": [
+ "iam_cloud_asset_inventory_enabled",
+ "iam_audit_logs_enabled",
+ "gcr_container_scanning_enabled",
+ "artifacts_container_analysis_enabled",
+ "compute_public_address_shodan",
+ "logging_sink_created"
+ ],
+ "alibabacloud": [
+ "securitycenter_advanced_or_enterprise_edition",
+ "securitycenter_notification_enabled_high_risk",
+ "actiontrail_multi_region_enabled",
+ "sls_logstore_retention_period"
+ ]
+ },
+ "config_requirements": [
+ {
+ "Check": "guardduty_is_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ },
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": false
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/gcp/ccc_gcp.json b/prowler/compliance/gcp/ccc_gcp.json
index df6b15bc5c..520b6b534a 100644
--- a/prowler/compliance/gcp/ccc_gcp.json
+++ b/prowler/compliance/gcp/ccc_gcp.json
@@ -889,7 +889,7 @@
}
],
"Checks": [
- "kms_key_rotation_enabled"
+ "kms_key_rotation_max_90_days"
]
},
{
@@ -924,6 +924,14 @@
"cloudsql_instance_automated_backups",
"cloudstorage_bucket_log_retention_policy_lock",
"cloudstorage_bucket_sufficient_retention_period"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "cloudstorage_bucket_sufficient_retention_period",
+ "ConfigKey": "storage_min_retention_days",
+ "Operator": "gte",
+ "Value": 30
+ }
]
},
{
@@ -5841,6 +5849,20 @@
"Checks": [
"iam_sa_user_managed_key_unused",
"iam_service_account_unused"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "iam_sa_user_managed_key_unused",
+ "ConfigKey": "max_unused_account_days",
+ "Operator": "lte",
+ "Value": 90
+ },
+ {
+ "Check": "iam_service_account_unused",
+ "ConfigKey": "max_unused_account_days",
+ "Operator": "lte",
+ "Value": 90
+ }
]
},
{
diff --git a/prowler/compliance/gcp/cis_2.0_gcp.json b/prowler/compliance/gcp/cis_2.0_gcp.json
index d391bcc271..dd9eb62a96 100644
--- a/prowler/compliance/gcp/cis_2.0_gcp.json
+++ b/prowler/compliance/gcp/cis_2.0_gcp.json
@@ -150,7 +150,7 @@
"Id": "1.10",
"Description": "Google Cloud Key Management Service stores cryptographic keys in a hierarchical structure designed for useful and elegant access control management. The format for the rotation schedule depends on the client library that is used. For the gcloud command-line tool, the next rotation time must be in `ISO` or `RFC3339` format, and the rotation period must be in the form `INTEGERUNIT`, where units can be one of seconds (s), minutes (m), hours (h) or days (d).",
"Checks": [
- "kms_key_rotation_enabled"
+ "kms_key_rotation_max_90_days"
],
"Attributes": [
{
diff --git a/prowler/compliance/gcp/cis_3.0_gcp.json b/prowler/compliance/gcp/cis_3.0_gcp.json
index b8d796c35a..958a2a9bc3 100644
--- a/prowler/compliance/gcp/cis_3.0_gcp.json
+++ b/prowler/compliance/gcp/cis_3.0_gcp.json
@@ -201,7 +201,7 @@
"Id": "1.10",
"Description": "Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days",
"Checks": [
- "kms_key_rotation_enabled"
+ "kms_key_rotation_max_90_days"
],
"Attributes": [
{
diff --git a/prowler/compliance/gcp/cis_4.0_gcp.json b/prowler/compliance/gcp/cis_4.0_gcp.json
index 5cd97a87da..d7a3c5d7a2 100644
--- a/prowler/compliance/gcp/cis_4.0_gcp.json
+++ b/prowler/compliance/gcp/cis_4.0_gcp.json
@@ -201,7 +201,7 @@
"Id": "1.10",
"Description": "Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days",
"Checks": [
- "kms_key_rotation_enabled"
+ "kms_key_rotation_max_90_days"
],
"Attributes": [
{
diff --git a/prowler/compliance/gcp/cis_5.0_gcp.json b/prowler/compliance/gcp/cis_5.0_gcp.json
new file mode 100644
index 0000000000..edc962ff0c
--- /dev/null
+++ b/prowler/compliance/gcp/cis_5.0_gcp.json
@@ -0,0 +1,2097 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS Google Cloud Platform Foundation Benchmark v5.0.0",
+ "Version": "5.0",
+ "Provider": "GCP",
+ "Description": "The CIS Google Cloud Platform Foundations Benchmark provides prescriptive guidance for configuring security options for a subset of GCP with an emphasis on foundational, testable, and architecture agnostic settings.",
+ "Requirements": [
+ {
+ "Id": "1.1.1",
+ "Description": "Ensure Super Admin Email Address Is Not Tied To A Single User",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "It is recommended that the super admin role is assigned to a dedicated email address (e.g., gcp-superadmin@company.com) rather than to individual user email addresses (e.g., john.doe@company.com). The dedicated super admin email should be a separate user account used exclusively for super admin level administrative tasks. When the GCP organization resource is created, existing super administrator accounts from Google Workspace or Cloud Identity automatically gain access to manage the organization. The super admin role has unrestricted access to all GCP organization resources and settings. Using individual user email addresses for super admin access creates security and operational risks.",
+ "RationaleStatement": "Using a dedicated email address for super admin accounts rather than individual user emails significantly reduces the risk of phishing attacks, as individual user accounts receive daily business emails and are high-value phishing targets, while a dedicated super admin email address not used for daily communications has minimal exposure to credential compromise. Dedicated super admin accounts can enforce stronger authentication requirements such as hardware security keys and shorter session timeouts without impacting day-to-day productivity. When employees leave the organization or change roles, super admin access remains continuous through the dedicated account rather than being tied to departing personnel. Separating super admin access from daily user activities prevents accidental misuse of elevated privileges and provides clear audit separation, supporting segregation of duties.",
+ "ImpactStatement": "Creating a new dedicated super admin account requires coordination with Google Workspace or Cloud Identity administrators. Existing super admin accounts tied to individual users should be replaced with the dedicated account, and individual user accounts should be removed from the super admin role once migration is complete.",
+ "AuditProcedure": "**From Google Cloud Admin Console**\n\n1. Navigate to the Google Admin console at https://admin.google.com\n2. Go to `Account` --> `Admin roles` in the left navigation menu\n3. Click on `Super Admin` role\n4. Review the list of users assigned the Super Admin role\n5. Verify that the super admin role is assigned to a dedicated email address (e.g., gcp-superadmin@company.com) and that individual user email addresses are NOT assigned the Super Admin role directly.",
+ "RemediationProcedure": "**From Google Cloud Admin Console**\n\n1. Create a dedicated super admin user account: in the Google Admin console go to `Directory` -> `Users`, click `Add new user` and configure a dedicated address (e.g., gcp-superadmin@company.com). Enforce 2-Step Verification with a hardware security key.\n2. Assign the Super Admin role to the dedicated account: go to `Account` --> `Admin roles`, click `Super Admin` role, `Assigned Admins` --> `Assign users`, select the dedicated account and click `Assign role`.\n3. Remove individual user accounts from the Super Admin role: for each individual user email address, select the user, click `Unassign role` and confirm the removal. Verify that only the dedicated super admin account remains assigned.",
+ "AdditionalInformation": "",
+ "References": "",
+ "SubSection": "1.1 Organization Resource",
+ "DefaultValue": "When you first sign up for Google Workspace or Cloud Identity, the person who completes the signup process automatically becomes the first super administrator, typically resulting in an individual user's email address being assigned the super admin role by default."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.2",
+ "Description": "Ensure Super Admin Account Is Not Used For Google Cloud Administration",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "It is recommended that super admin accounts are not granted any IAM roles in Google Cloud Platform and are used exclusively for identity management in Google Workspace or Cloud Identity. Google Cloud administration should be performed using separate regular user accounts that are granted appropriate GCP IAM roles such as Organization Administrator. The Super Admin role and GCP resource management are two separate privilege domains that should not be combined in a single account.",
+ "RationaleStatement": "Separating super admin accounts from GCP administration is critical because Super Admin privileges are irrevocable and can override almost any setting in both Workspace and GCP. If a super admin account is granted GCP permissions and compromised through phishing, an attacker gains full control over both the email domain and the entire cloud infrastructure. Super admin accounts not granted GCP IAM permissions cannot be used to directly manipulate cloud resources even if compromised, limiting blast radius to identity management functions only. This separation enforces least privilege and reduces the attack surface by ensuring the most powerful account type is isolated from daily cloud operations.",
+ "ImpactStatement": "Organizations must create separate regular user accounts in Workspace/Cloud Identity for GCP administration. These accounts will be granted appropriate GCP IAM roles for cloud resource management. Existing super admin accounts that have been granted GCP IAM roles must have those permissions removed.",
+ "AuditProcedure": "**From Google Cloud Admin Console**\n\n1. In the Google Admin console (https://admin.google.com), go to `Account` -> `Admin roles`, click `Super Admin` role and note all user accounts assigned the Super Admin role.\n2. In the Google Cloud Console (https://console.cloud.google.com), go to `IAM & Admin` -> `IAM` at the organization level and review all IAM policy bindings.\n3. Verify that none of the super admin accounts appear in the IAM permissions list and that they have NO IAM roles granted at organization, folder, or project levels.",
+ "RemediationProcedure": "**From Google Cloud Admin Console**\n\n1. Create a separate regular user account for GCP administration in `Directory` -> `Users` (do NOT assign it the Super Admin role).\n2. Grant GCP IAM roles to that cloud admin account in the Cloud Console under `IAM & Admin` -> `IAM` (e.g., Organization Administrator).\n3. Delete all GCP IAM bindings for super admin users: in `IAM & Admin` -> `IAM` at the organization level, edit each super admin principal and remove all assigned roles. Repeat for all folders and projects.",
+ "AdditionalInformation": "",
+ "References": "",
+ "SubSection": "1.1 Organization Resource",
+ "DefaultValue": "By default, super administrator accounts from Google Workspace or Cloud Identity gain access to manage the GCP organization resource when it is created."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.3",
+ "Description": "Ensure Folders Are Structured By Environment And Sensitivity",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that GCP Resource Manager folders are structured primarily by environment (for example, production, non-production, sandbox) and sensitivity (for example, security, logging, shared services, regulated workloads), rather than mirroring the corporate org chart. Folders should group projects that share similar security requirements and controls so that appropriate Organization Policies, IAM policies, and other guardrails can be applied consistently at the folder level.",
+ "RationaleStatement": "A clear folder structure based on environment and sensitivity makes it easier to apply consistent guardrails and centralized security controls to projects that have similar risk profiles and compliance needs. Folders enable hierarchical policy inheritance where stricter controls can be applied to production folders while development folders can have more relaxed policies. Poorly defined or ad-hoc folder structures complicate policy management, increase the chance of misapplied controls, and can lead to mixing workloads with different data sensitivities. Without proper folder segregation, a compromised development project can be used to pivot into production resources and compliance auditing becomes significantly more complex.",
+ "ImpactStatement": "Restructuring folders by environment and sensitivity can require moving projects, changing inherited Organization Policies and IAM policies, and updating automation that assumes existing folder paths. This may introduce short-term operational overhead, including policy revalidation, testing of workloads under new guardrails, and coordination with application and platform teams.",
+ "AuditProcedure": "**From Google Cloud Admin Console**\n\n1. In the Cloud Console (https://console.cloud.google.com), select your organization and go to `IAM & Admin` -> `Manage resources` to view the organization hierarchy.\n2. Review and document the folder hierarchy (organization -> folders -> sub-folders -> projects).\n3. Evaluate whether top-level and key folders are clearly aligned to environment (production, non-production, sandbox) and sensitivity/function (security, logging, shared services, regulated).\n4. For each environment/sensitivity folder, sample projects and verify their primary workloads match the folder's stated purpose. Note any folders organized mainly by department/owner or that mix production and non-production workloads.",
+ "RemediationProcedure": "**From Google Cloud Admin Console**\n\n1. Work with security, platform, and application teams to agree on a small set of top-level folders (e.g., Security/Management, Shared Services/Infrastructure, Prod, Non-Prod). Define dedicated folders for highly regulated workloads.\n2. Create the folder structure under `IAM & Admin` -> `Manage resources` using `CREATE FOLDER`.\n3. Map each project to its target folder based on environment and sensitivity.\n4. Move projects to the environment/sensitivity-based folders (start with low-risk sandbox/non-production projects, test workloads, then proceed with production).\n5. Remove old folders that no longer reflect the target structure and update architecture docs and onboarding runbooks.",
+ "AdditionalInformation": "",
+ "References": "",
+ "SubSection": "1.1 Organization Resource"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.4",
+ "Description": "Ensure Organization Policies Are Configured For Centralized Constraints",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that one or more baseline Organization Policies are configured at the organization or folder level in accordance with enterprise security requirements. Organization Policies act as preventive guardrails that set centralized constraints on how resources can be configured across all projects within the organization hierarchy. These policies can enforce security invariants such as preventing public IP addresses on compute instances, requiring OS Login for SSH access, restricting resource locations to approved regions, enforcing uniform bucket-level access on Cloud Storage, or limiting IAM policy member domains to prevent external sharing.",
+ "RationaleStatement": "Organization Policies do not grant permissions but instead set organization-wide limits on resource configurations and service usage, regardless of local project-level IAM policies. Without baseline guardrail Organization Policies, each project can configure resources inconsistently, disable security features, use unapproved regions, allow public access to resources, or share data with external domains. Configuring standard Organization Policies at the organization or folder level enforces preventive, centralized control over high-risk configurations and supports consistent security posture at scale. Organization Policies are inherited down the resource hierarchy (organization -> folder -> project), making them an effective mechanism for enforcing security controls across large numbers of projects.",
+ "ImpactStatement": "Enforcing baseline Organization Policies can initially block some existing resource configurations, such as use of unapproved regions, creation of resources with public IPs, or external domain sharing. Teams may need to adjust deployment pipelines, Terraform configurations, and exception processes. Organizations should test policies in non-production folders before applying them broadly.",
+ "AuditProcedure": "**From Google Cloud Admin Console**\n\nPre-requisite: Document your organization's baseline guardrail requirements (e.g., constraints/gcp.resourceLocations, constraints/compute.requireOsLogin, constraints/compute.vmExternalIpAccess, constraints/storage.uniformBucketLevelAccess, constraints/iam.allowedPolicyMemberDomains).\n\n1. In the Cloud Console (https://console.cloud.google.com), select your organization and go to `IAM & Admin` -> `Organization Policies`. Review the policies set at the organization level and verify baseline security constraints are configured (enforced, exceptions, configured values).\n2. Verify policies are not overridden or disabled at folder or project levels (look for policies marked as `Customized`).\n3. Compare your documented baseline requirements against the configured Organization Policies and identify gaps.",
+ "RemediationProcedure": "IMPORTANT: Before enforcing Organization Policies, use dry run mode to preview which resources would be blocked and review violations in Cloud Asset Inventory before actual enforcement.\n\n**From Google Cloud Admin Console**\n\n1. In `IAM & Admin` -> `Organization Policies`, review existing policies and identify gaps based on your security requirements.\n2. For each baseline constraint, search for the constraint, click `Manage policy`, select `Override parent's policy` and configure it (boolean: `Enforcement On`; list: choose Deny all/Allow all or Custom values). Click `Set policy` and verify it shows as `Enforced`.\n3. Configure folder-level policies if different constraints are needed per environment, ensuring folder-level policies do not weaken organization-level security controls unless explicitly approved.",
+ "AdditionalInformation": "",
+ "References": "",
+ "SubSection": "1.1 Organization Resource"
+ }
+ ]
+ },
+ {
+ "Id": "1.2",
+ "Description": "Ensure that Corporate Login Credentials are Used",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use corporate login credentials instead of consumer accounts, such as Gmail accounts.",
+ "RationaleStatement": "It is recommended fully-managed corporate Google accounts be used for increased visibility, auditing, and controlling access to Cloud Platform resources. Email accounts based outside of the user's organization, such as consumer accounts, should not be used for business purposes.",
+ "ImpactStatement": "There will be increased overhead as maintaining accounts will now be required. For smaller organizations, this will not be an issue, but will balloon with size.",
+ "RemediationProcedure": "Remove all consumer Google accounts from IAM policies. Follow the documentation and setup corporate login accounts. **Prevention:** To ensure that no email addresses outside the organization can be granted IAM permissions to its Google Cloud projects, folders or organization, turn on the Organization Policy for `Domain Restricted Sharing`. Learn more at: [https://cloud.google.com/resource-manager/docs/organization-policy/restricting-domains](https://cloud.google.com/resource-manager/docs/organization-policy/restricting-domains)",
+ "AuditProcedure": "For each Google Cloud Platform project, list the accounts that have been granted access to that project: **From Google Cloud CLI** gcloud projects get-iam-policy PROJECT_ID Also list the accounts added on each folder: gcloud resource-manager folders get-iam-policy FOLDER_ID And list your organization's IAM policy: gcloud organizations get-iam-policy ORGANIZATION_ID No email accounts outside the organization domain should be granted permissions in the IAM policies. This excludes Google-owned service accounts.",
+ "AdditionalInformation": "",
+ "References": "https://support.google.com/work/android/answer/6371476:https://cloud.google.com/sdk/gcloud/reference/projects/get-iam-policy:https://cloud.google.com/sdk/gcloud/reference/resource-manager/folders/get-iam-policy:https://cloud.google.com/sdk/gcloud/reference/organizations/get-iam-policy:https://cloud.google.com/resource-manager/docs/organization-policy/restricting-domains:https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints",
+ "DefaultValue": "By default, no email addresses outside the organization's domain have access to its Google Cloud deployments, but any user email account can be added to the IAM policy for Google Cloud Platform projects, folders, or organizations.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.3",
+ "Description": "Ensure that Multi-Factor Authentication is 'Enabled' for All Non-Service Accounts",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Setup multi-factor authentication for Google Cloud Platform accounts.",
+ "RationaleStatement": "Multi-factor authentication requires more than one mechanism to authenticate a user. This secures user logins from attackers exploiting stolen or weak credentials.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** For each Google Cloud Platform project: 1. Identify non-service accounts. 1. Setup multi-factor authentication for each account.",
+ "AuditProcedure": "**From Google Cloud Console** For each Google Cloud Platform project, folder, or organization: 1. Identify non-service accounts. 1. Manually verify that multi-factor authentication for each account is set.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/solutions/securing-gcp-account-u2f:https://support.google.com/accounts/answer/185839",
+ "DefaultValue": "By default, multi-factor authentication is not set.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.4",
+ "Description": "Ensure that Security Key Enforcement is Enabled for All Admin Accounts",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Setup Security Key Enforcement for Google Cloud Platform admin accounts.",
+ "RationaleStatement": "Google Cloud Platform users with Organization Administrator roles have the highest level of privilege in the organization. These accounts should be protected with the strongest form of two-factor authentication: Security Key Enforcement. Ensure that admins use Security Keys to log in instead of weaker second factors like SMS or one-time passwords (OTP). Security Keys are actual physical keys used to access Google Organization Administrator Accounts. They send an encrypted signature rather than a code, ensuring that logins cannot be phished.",
+ "ImpactStatement": "If an organization administrator loses access to their security key, the user could lose access to their account. For this reason, it is important to set up backup security keys.",
+ "RemediationProcedure": "1. Identify users with the Organization Administrator role. 2. Setup Security Key Enforcement for each account. Learn more at: [https://cloud.google.com/security-key/](https://cloud.google.com/security-key/)",
+ "AuditProcedure": "1. Identify users with Organization Administrator privileges: gcloud organizations get-iam-policy ORGANIZATION_ID Look for members granted the role roles/resourcemanager.organizationAdmin. 2. Manually verify that Security Key Enforcement has been enabled for each account.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/security-key/:https://gsuite.google.com/learn-more/key_for_working_smarter_faster_and_more_securely.html",
+ "DefaultValue": "By default, Security Key Enforcement is not enabled for Organization Administrators.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.5",
+ "Description": "Ensure That There Are Only GCP-Managed Service Account Keys for Each Service Account",
+ "Checks": [
+ "iam_sa_no_user_managed_keys"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "User-managed service accounts should not have user-managed keys.",
+ "RationaleStatement": "Anyone who has access to the keys will be able to access resources through the service account. GCP-managed keys are used by Cloud Platform services such as App Engine and Compute Engine. These keys cannot be downloaded. Google will keep the keys and automatically rotate them on an approximately weekly basis. User-managed keys are created, downloadable, and managed by users. They expire 10 years from creation. For user-managed keys, the user has to take ownership of key management activities which include: - Key storage - Key distribution - Key revocation - Key rotation - Protecting the keys from unauthorized users - Key recovery Even with key owner precautions, keys can be easily leaked by common development malpractices like checking keys into the source code or leaving them in the Downloads directory, or accidentally leaving them on support blogs/channels. It is recommended to prevent user-managed service account keys.",
+ "ImpactStatement": "Deleting user-managed service account keys may break communication with the applications using the corresponding keys.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the IAM page in the GCP Console using `https://console.cloud.google.com/iam-admin/iam` 2. In the left navigation pane, click `Service accounts`. All service accounts and their corresponding keys are listed. 3. Click the service account. 4. Click the `edit` and delete the keys. **From Google Cloud CLI** To delete a user managed Service Account Key, gcloud iam service-accounts keys delete --iam-account=<user-managed-service-account-EMAIL> <KEY-ID> **Prevention:** You can disable service account key creation through the `Disable service account key creation` Organization policy by visiting [https://console.cloud.google.com/iam-admin/orgpolicies/iam-disableServiceAccountKeyCreation](https://console.cloud.google.com/iam-admin/orgpolicies/iam-disableServiceAccountKeyCreation). Learn more at: [https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts](https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts) In addition, if you do not need to have service accounts in your project, you can also prevent the creation of service accounts through the `Disable service account creation` Organization policy: [https://console.cloud.google.com/iam-admin/orgpolicies/iam-disableServiceAccountCreation](https://console.cloud.google.com/iam-admin/orgpolicies/iam-disableServiceAccountCreation).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the IAM page in the GCP Console using `https://console.cloud.google.com/iam-admin/iam` 2. In the left navigation pane, click `Service accounts`. All service accounts and their corresponding keys are listed. 3. Click the service accounts and check if keys exist. **From Google Cloud CLI** List All the service accounts: gcloud iam service-accounts list Identify user-managed service accounts which have an account `EMAIL` ending with `iam.gserviceaccount.com` For each user-managed service account, list the keys managed by the user: gcloud iam service-accounts keys list --iam-account=<Service Account> --managed-by=user No keys should be listed.",
+ "AdditionalInformation": "A user-managed key cannot be created on GCP-Managed Service Accounts.",
+ "References": "https://cloud.google.com/iam/docs/understanding-service-accounts#managing_service_account_keys:https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts",
+ "DefaultValue": "By default, there are no user-managed keys created for user-managed service accounts.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.6",
+ "Description": "Ensure That Service Account Has No Admin Privileges",
+ "Checks": [
+ "iam_sa_no_administrative_privileges"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "A service account is a special Google account that belongs to an application or a VM, instead of to an individual end-user. The application uses the service account to call the service's Google API so that users aren't directly involved. It's recommended not to use admin access for ServiceAccount.",
+ "RationaleStatement": "Service accounts represent service-level security of the Resources (application or a VM) which can be determined by the roles assigned to it. Enrolling ServiceAccount with Admin rights gives full access to an assigned application or a VM. A ServiceAccount Access holder can perform critical actions like delete, update change settings, etc. without user intervention. For this reason, it's recommended that service accounts not have Admin rights.",
+ "ImpactStatement": "Removing `*Admin` or `*admin` or `Editor` or `Owner` role assignments from service accounts may break functionality that uses impacted service accounts. Required role(s) should be assigned to impacted service accounts in order to restore broken functionalities.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `IAM & admin/IAM` using `https://console.cloud.google.com/iam-admin/iam` 2. Under the `IAM` Tab look for `VIEW BY PRINCIPALS` 3. Filter `PRINCIPALS` using `type : Service account` 4. Look for the Service Account with the Principal nomenclature: `SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com` 5. Identify `User-Managed user created` service account with roles containing `*Admin` or `*admin` or role matching `Editor` or role matching `Owner` under `Role` Column. 6. Click on `Edit (Pencil Icon)` for the Service Account, it will open all the roles which are assigned to the Service Account. 7. Click the `Delete bin` icon to remove the role from the Principal (service account in this case) **From Google Cloud CLI** gcloud projects get-iam-policy PROJECT_ID --format json > iam.json 1. Using a text editor, Remove `Role` which contains `roles/*Admin` or `roles/*admin` or matched `roles/editor` or matches 'roles/owner`. Add a role to the bindings array that defines the group members and the role for those members. For example, to grant the role roles/appengine.appViewer to the `ServiceAccount` which is roles/editor, you would change the example shown below as follows: { bindings: [ { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, ], role: roles/appengine.appViewer }, { members: [ user:email1@gmail.com ], role: roles/owner }, { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, serviceAccount:123456789012-compute@developer.gserviceaccount.com ], role: roles/editor } ], etag: BwUjMhCsNvY= } 2. Update the project's IAM policy: gcloud projects set-iam-policy PROJECT_ID iam.json ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `IAM & admin/IAM` using `https://console.cloud.google.com/iam-admin/iam` 2. Under the `IAM` Tab look for `VIEW BY PRINCIPALS` 3. Filter `PRINCIPALS` using `type : Service account` 4. Look for the Service Account with the nomenclature: `SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com` 5. Ensure that there are no such Service Accounts with roles containing `*Admin` or `*admin` or role matching `Editor` or role matching `Owner` under `Role` column. **From Google Cloud CLI** 1. Get the policy that you want to modify, and write it to a JSON file: gcloud projects get-iam-policy PROJECT_ID --format json > iam.json 2. The contents of the JSON file will look similar to the following. Note that `role` of members group associated with each `serviceaccount` does not contain `*Admin` or `*admin` or does not match `roles/editor` or does not match `roles/owner`. This recommendation is only applicable to `User-Managed user-created` service accounts. These accounts have the nomenclature: `SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com`. Note that some Google-managed, Google-created service accounts have the same naming format, and should be excluded (e.g., `appsdev-apps-dev-script-auth@system.gserviceaccount.com` which needs the Owner role). **Sample Json output:** { bindings: [ { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, ], role: roles/appengine.appAdmin }, { members: [ user:email1@gmail.com ], role: roles/owner }, { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, serviceAccount:123456789012-compute@developer.gserviceaccount.com ], role: roles/editor } ], etag: BwUjMhCsNvY=, version: 1 }",
+ "AdditionalInformation": "Default (user-managed but not user-created) service accounts have the `Editor (roles/editor)` role assigned to them to support GCP services they offer. Such Service accounts are: `PROJECT_NUMBER-compute@developer.gserviceaccount.com`, `PROJECT_ID@appspot.gserviceaccount.com`.",
+ "References": "https://cloud.google.com/sdk/gcloud/reference/iam/service-accounts/:https://cloud.google.com/iam/docs/understanding-roles:https://cloud.google.com/iam/docs/understanding-service-accounts",
+ "DefaultValue": "User Managed (and not user-created) default service accounts have the `Editor (roles/editor)` role assigned to them to support GCP services they offer. By default, there are no roles assigned to `User Managed User created` service accounts.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.7",
+ "Description": "Ensure That IAM Users Are Not Assigned the Service Account User or Service Account Token Creator Roles at Project Level",
+ "Checks": [
+ "iam_no_service_roles_at_project_level"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to assign the `Service Account User (iam.serviceAccountUser)` and `Service Account Token Creator (iam.serviceAccountTokenCreator)` roles to a user for a specific service account rather than assigning the role to a user at project level.",
+ "RationaleStatement": "A service account is a special Google account that belongs to an application or a virtual machine (VM), instead of to an individual end-user. Application/VM-Instance uses the service account to call the service's Google API so that users aren't directly involved. In addition to being an identity, a service account is a resource that has IAM policies attached to it. These policies determine who can use the service account. Users with IAM roles to update the App Engine and Compute Engine instances (such as App Engine Deployer or Compute Instance Admin) can effectively run code as the service accounts used to run these instances, and indirectly gain access to all the resources for which the service accounts have access. Similarly, SSH access to a Compute Engine instance may also provide the ability to execute code as that instance/Service account. Based on business needs, there could be multiple user-managed service accounts configured for a project. Granting the `iam.serviceAccountUser` or `iam.serviceAccountTokenCreator` roles to a user for a project gives the user access to all service accounts in the project, including service accounts that may be created in the future. This can result in elevation of privileges by using service accounts and corresponding `Compute Engine instances`. In order to implement `least privileges` best practices, IAM users should not be assigned the `Service Account User` or `Service Account Token Creator` roles at the project level. Instead, these roles should be assigned to a user for a specific service account, giving that user access to the service account. The `Service Account User` allows a user to bind a service account to a long-running job service, whereas the `Service Account Token Creator` role allows a user to directly impersonate (or assert) the identity of a service account.",
+ "ImpactStatement": "After revoking `Service Account User` or `Service Account Token Creator` roles at the project level from all impacted user account(s), these roles should be assigned to a user(s) for specific service account(s) according to business needs.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the IAM page in the GCP Console by visiting: [https://console.cloud.google.com/iam-admin/iam](https://console.cloud.google.com/iam-admin/iam). 2. Click on the filter table text bar. Type `Role: Service Account User` 3. Click the `Delete Bin` icon in front of the role `Service Account User` for every user listed as a result of a filter. 4. Click on the filter table text bar. Type `Role: Service Account Token Creator` 5. Click the `Delete Bin` icon in front of the role `Service Account Token Creator` for every user listed as a result of a filter. **From Google Cloud CLI** 1. Using a text editor, remove the bindings with the `roles/iam.serviceAccountUser` or `roles/iam.serviceAccountTokenCreator`. For example, you can use the iam.json file shown below as follows: { bindings: [ { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, ], role: roles/appengine.appViewer }, { members: [ user:email1@gmail.com ], role: roles/owner }, { members: [ serviceAccount:our-project-123@appspot.gserviceaccount.com, serviceAccount:123456789012-compute@developer.gserviceaccount.com ], role: roles/editor } ], etag: BwUjMhCsNvY= } 2. Update the project's IAM policy: gcloud projects set-iam-policy PROJECT_ID iam.json ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the IAM page in the GCP Console by visiting [https://console.cloud.google.com/iam-admin/iam](https://console.cloud.google.com/iam-admin/iam) 2. Click on the filter table text bar, Type `Role: Service Account User`. 3. Ensure no user is listed as a result of the filter. 4. Click on the filter table text bar, Type `Role: Service Account Token Creator`. 3. Ensure no user is listed as a result of the filter. **From Google Cloud CLI** To ensure IAM users are not assigned Service Account User role at the project level: gcloud projects get-iam-policy PROJECT_ID --format json | jq '.bindings[].role' | grep roles/iam.serviceAccountUser gcloud projects get-iam-policy PROJECT_ID --format json | jq '.bindings[].role' | grep roles/iam.serviceAccountTokenCreator These commands should not return any output.",
+ "AdditionalInformation": "To assign the role `roles/iam.serviceAccountUser` or `roles/iam.serviceAccountTokenCreator` to a user role on a service account instead of a project: 1. Go to [https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts) 2. Select ` Target Project` 3. Select `target service account`. Click `Permissions` on the top bar. It will open permission pane on right side of the page 4. Add desired members with `Service Account User` or `Service Account Token Creator` role.",
+ "References": "https://cloud.google.com/iam/docs/service-accounts:https://cloud.google.com/iam/docs/granting-roles-to-service-accounts:https://cloud.google.com/iam/docs/understanding-roles:https://cloud.google.com/iam/docs/granting-changing-revoking-access:https://console.cloud.google.com/iam-admin/iam",
+ "DefaultValue": "By default, users do not have the Service Account User or Service Account Token Creator role assigned at project level.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.8",
+ "Description": "Ensure User-Managed/External Keys for Service Accounts Are Rotated Every 90 Days or Fewer",
+ "Checks": [
+ "iam_sa_user_managed_key_rotate_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Service Account keys consist of a key ID (Private_key_Id) and Private key, which are used to sign programmatic requests users make to Google cloud services accessible to that particular service account. It is recommended that all Service Account keys are regularly rotated.",
+ "RationaleStatement": "Rotating Service Account keys will reduce the window of opportunity for an access key that is associated with a compromised or terminated account to be used. Service Account keys should be rotated to ensure that data cannot be accessed with an old key that might have been lost, cracked, or stolen. Each service account is associated with a key pair managed by Google Cloud Platform (GCP). It is used for service-to-service authentication within GCP. Google rotates the keys daily. GCP provides the option to create one or more user-managed (also called external key pairs) key pairs for use from outside GCP (for example, for use with Application Default Credentials). When a new key pair is created, the user is required to download the private key (which is not retained by Google). With external keys, users are responsible for keeping the private key secure and other management operations such as key rotation. External keys can be managed by the IAM API, gcloud command-line tool, or the Service Accounts page in the Google Cloud Platform Console. GCP facilitates up to 10 external service account keys per service account to facilitate key rotation.",
+ "ImpactStatement": "Rotating service account keys will break communication for dependent applications. Dependent applications need to be configured manually with the new key `ID` displayed in the `Service account keys` section and the `private key` downloaded by the user.",
+ "RemediationProcedure": "**From Google Cloud Console** **Delete any external (user-managed) Service Account Key older than 90 days:** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the Section `Service Account Keys`, for every external (user-managed) service account key where `creation date` is greater than or equal to the past 90 days, click `Delete Bin Icon` to `Delete Service Account key` **Create a new external (user-managed) Service Account Key for a Service Account:** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. Click `Create Credentials` and Select `Service Account Key`. 3. Choose the service account in the drop-down list for which an External (user-managed) Service Account key needs to be created. 4. Select the desired key type format among `JSON` or `P12`. 5. Click `Create`. It will download the `private key`. Keep it safe. 6. Click `Close` if prompted. 7. The site will redirect to the `APIs & ServicesCredentials` page. Make a note of the new `ID` displayed in the `Service account keys` section.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `Service Account Keys`, for every External (user-managed) service account key listed ensure the `creation date` is within the past 90 days. **From Google Cloud CLI** 1. List all Service accounts from a project. gcloud iam service-accounts list 2. For every service account list service account keys. gcloud iam service-accounts keys list --iam-account [Service_Account_Email_Id] --format=json 3. Ensure every service account key for a service account has a `validAfterTime` value within the past 90 days.",
+ "AdditionalInformation": "For user-managed Service Account key(s), key management is entirely the user's responsibility.",
+ "References": "https://cloud.google.com/iam/docs/understanding-service-accounts#managing_service_account_keys:https://cloud.google.com/sdk/gcloud/reference/iam/service-accounts/keys/list:https://cloud.google.com/iam/docs/service-accounts",
+ "DefaultValue": "GCP does not provide an automation option for External (user-managed) Service key rotation.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.9",
+ "Description": "Ensure That Separation of Duties Is Enforced While Assigning Service Account Related Roles to Users",
+ "Checks": [
+ "iam_role_kms_enforce_separation_of_duties"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that the principle of 'Separation of Duties' is enforced while assigning service-account related roles to users.",
+ "RationaleStatement": "The built-in/predefined IAM role `Service Account admin` allows the user/identity to create, delete, and manage service account(s). The built-in/predefined IAM role `Service Account User` allows the user/identity (with adequate privileges on Compute and App Engine) to assign service account(s) to Apps/Compute Instances. Separation of duties is the concept of ensuring that one individual does not have all necessary permissions to be able to complete a malicious action. In Cloud IAM - service accounts, this could be an action such as using a service account to access resources that user should not normally have access to. Separation of duties is a business control typically used in larger organizations, meant to help avoid security or privacy incidents and errors. It is considered best practice. No user should have `Service Account Admin` and `Service Account User` roles assigned at the same time.",
+ "ImpactStatement": "The removed role should be assigned to a different user based on business needs.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `IAM & Admin/IAM` using `https://console.cloud.google.com/iam-admin/iam`. 2. For any member having both `Service Account Admin` and `Service account User` roles granted/assigned, click the `Delete Bin` icon to remove either role from the member. Removal of a role should be done based on the business requirements.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `IAM & Admin/IAM` using `https://console.cloud.google.com/iam-admin/iam`. 2. Ensure no member has the roles `Service Account Admin` and `Service account User` assigned together. **From Google Cloud CLI** 1. List all users and role assignments: gcloud projects get-iam-policy [Project_ID] --format json | jq -r '[ ([Service_Account_Admin_and_User] | (., map(length*-))), ( [ .bindings[] | select(.role == roles/iam.serviceAccountAdmin or .role == roles/iam.serviceAccountUser).members[] ] | group_by(.) | map({User: ., Count: length}) | .[] | select(.Count == 2).User | unique ) ] | .[] | @tsv' 2. All common users listed under `Service_Account_Admin_and_User` are assigned both the `roles/iam.serviceAccountAdmin` and `roles/iam.serviceAccountUser` roles.",
+ "AdditionalInformation": "Users granted with Owner (roles/owner) and Editor (roles/editor) have privileges equivalent to `Service Account Admin` and `Service Account User`. To avoid the misuse, Owner and Editor roles should be granted to very limited users and Use of these primitive privileges should be minimal. These requirements are addressed in separate recommendations.",
+ "References": "https://cloud.google.com/iam/docs/service-accounts:https://cloud.google.com/iam/docs/understanding-roles:https://cloud.google.com/iam/docs/granting-roles-to-service-accounts",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.10",
+ "Description": "Ensure That Cloud KMS Cryptokeys Are Not Anonymously or Publicly Accessible",
+ "Checks": [
+ "kms_key_not_publicly_accessible"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that the IAM policy on Cloud KMS `cryptokeys` should restrict anonymous and/or public access.",
+ "RationaleStatement": "Granting permissions to `allUsers` or `allAuthenticatedUsers` allows anyone to access the dataset. Such access might not be desirable if sensitive data is stored at the location. In this case, ensure that anonymous and/or public access to a Cloud KMS `cryptokey` is not allowed.",
+ "ImpactStatement": "Removing the binding for `allUsers` and `allAuthenticatedUsers` members denies accessing `cryptokeys` to anonymous or public users.",
+ "RemediationProcedure": "**From Google Cloud CLI** 1. List all Cloud KMS `Cryptokeys`. gcloud kms keys list --keyring=[key_ring_name] --location=global --format=json | jq '.[].name' 2. Remove IAM policy binding for a KMS key to remove access to `allUsers` and `allAuthenticatedUsers` using the below command. gcloud kms keys remove-iam-policy-binding [key_name] --keyring=[key_ring_name] --location=global --member='allAuthenticatedUsers' --role='[role]' gcloud kms keys remove-iam-policy-binding [key_name] --keyring=[key_ring_name] --location=global --member='allUsers' --role='[role]' ",
+ "AuditProcedure": "**From Google Cloud CLI** 1. List all Cloud KMS `Cryptokeys`. gcloud kms keys list --keyring=[key_ring_name] --location=global --format=json | jq '.[].name' 2. Ensure the below command's output does not contain `allUsers` or `allAuthenticatedUsers`. gcloud kms keys get-iam-policy [key_name] --keyring=[key_ring_name] --location=global --format=json | jq '.bindings[].members[]' ",
+ "AdditionalInformation": "[key_ring_name] : Is the resource ID of the key ring, which is the fully-qualified Key ring name. This value is case-sensitive and in the form: projects/PROJECT_ID/locations/LOCATION/keyRings/KEY_RING You can retrieve the key ring resource ID using the Cloud Console: 1. Open the `Cryptographic Keys` page in the Cloud Console. 2. For the key ring whose resource ID you are retrieving, click the `More icon (3 vertical dots)`. 3. Click `Copy Resource ID`. The resource ID for the key ring is copied to your clipboard. [key_name] : Is the resource ID of the key, which is the fully-qualified CryptoKey name. This value is case-sensitive and in the form: projects/PROJECT_ID/locations/LOCATION/keyRings/KEY_RING/cryptoKeys/KEY You can retrieve the key resource ID using the Cloud Console: 1. Open the `Cryptographic Keys` page in the Cloud Console. 2. Click the name of the key ring that contains the key. 3. For the key whose resource ID you are retrieving, click the `More icon (3 vertical dots)`. 4. Click `Copy Resource ID`. The resource ID for the key is copied to your clipboard. [role] : The role to remove the member from.",
+ "References": "https://cloud.google.com/sdk/gcloud/reference/kms/keys/remove-iam-policy-binding:https://cloud.google.com/sdk/gcloud/reference/kms/keys/set-iam-policy:https://cloud.google.com/sdk/gcloud/reference/kms/keys/get-iam-policy:https://cloud.google.com/kms/docs/object-hierarchy#key_resource_id",
+ "DefaultValue": "By default Cloud KMS does not allow access to `allUsers` or `allAuthenticatedUsers`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.11",
+ "Description": "Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days",
+ "Checks": [
+ "kms_key_rotation_max_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Google Cloud Key Management Service stores cryptographic keys in a hierarchical structure designed for useful and elegant access control management. The format for the rotation schedule depends on the client library that is used. For the gcloud command-line tool, the next rotation time must be in `ISO` or `RFC3339` format, and the rotation period must be in the form `INTEGER[UNIT]`, where units can be one of seconds (s), minutes (m), hours (h) or days (d).",
+ "RationaleStatement": "Set a key rotation period and starting time. A key can be created with a specified `rotation period`, which is the time between when new key versions are generated automatically. A key can also be created with a specified next rotation time. A key is a named object representing a `cryptographic key` used for a specific purpose. The key material, the actual bits used for `encryption`, can change over time as new key versions are created. A key is used to protect some `corpus of data`. A collection of files could be encrypted with the same key and people with `decrypt` permissions on that key would be able to decrypt those files. Therefore, it's necessary to make sure the `rotation period` is set to a specific time.",
+ "ImpactStatement": "After a successful key rotation, the older key version is required in order to decrypt the data encrypted by that previous key version.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Cryptographic Keys` by visiting: [https://console.cloud.google.com/security/kms](https://console.cloud.google.com/security/kms). 2. Click on the specific key ring 3. From the list of keys, choose the specific key and Click on `Right side pop up the blade (3 dots)`. 4. Click on `Edit rotation period`. 5. On the pop-up window, `Select a new rotation period` in days which should be less than 90 and then choose `Starting on` date (date from which the rotation period begins). **From Google Cloud CLI** 1. Update and schedule rotation by `ROTATION_PERIOD` and `NEXT_ROTATION_TIME` for each key: gcloud kms keys update new --keyring=KEY_RING --location=LOCATION --next-rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Cryptographic Keys` by visiting: [https://console.cloud.google.com/security/kms](https://console.cloud.google.com/security/kms). 2. Click on each key ring, then ensure each key in the keyring has `Next Rotation` set for less than 90 days from the current date. **From Google Cloud CLI** 1. Ensure rotation is scheduled by `ROTATION_PERIOD` and `NEXT_ROTATION_TIME` for each key : gcloud kms keys list --keyring=<KEY_RING> --location=<LOCATION> --format=json'(rotationPeriod)' Ensure outcome values for `rotationPeriod` and `nextRotationTime` satisfy the below criteria: `rotationPeriod is <= 129600m` `rotationPeriod is <= 7776000s` `rotationPeriod is <= 2160h` `rotationPeriod is <= 90d` `nextRotationTime is <= 90days` from current DATE",
+ "AdditionalInformation": "- Key rotation does NOT re-encrypt already encrypted data with the newly generated key version. If you suspect unauthorized use of a key, you should re-encrypt the data protected by that key and then disable or schedule destruction of the prior key version. - It is not recommended to rely solely on irregular rotation, but rather to use irregular rotation if needed in conjunction with a regular rotation schedule.",
+ "References": "https://cloud.google.com/kms/docs/key-rotation#frequency_of_key_rotation:https://cloud.google.com/kms/docs/re-encrypt-data",
+ "DefaultValue": "By default, KMS encryption keys are rotated every 90 days.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.12",
+ "Description": "Ensure That Separation of Duties Is Enforced While Assigning KMS Related Roles to Users",
+ "Checks": [
+ "iam_role_kms_enforce_separation_of_duties"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that the principle of 'Separation of Duties' is enforced while assigning KMS related roles to users.",
+ "RationaleStatement": "The built-in/predefined IAM role `Cloud KMS Admin` allows the user/identity to create, delete, and manage service account(s). The built-in/predefined IAM role `Cloud KMS CryptoKey Encrypter/Decrypter` allows the user/identity (with adequate privileges on concerned resources) to encrypt and decrypt data at rest using an encryption key(s). The built-in/predefined IAM role `Cloud KMS CryptoKey Encrypter` allows the user/identity (with adequate privileges on concerned resources) to encrypt data at rest using an encryption key(s). The built-in/predefined IAM role `Cloud KMS CryptoKey Decrypter` allows the user/identity (with adequate privileges on concerned resources) to decrypt data at rest using an encryption key(s). Separation of duties is the concept of ensuring that one individual does not have all necessary permissions to be able to complete a malicious action. In Cloud KMS, this could be an action such as using a key to access and decrypt data a user should not normally have access to. Separation of duties is a business control typically used in larger organizations, meant to help avoid security or privacy incidents and errors. It is considered best practice. No user(s) should have `Cloud KMS Admin` and any of the `Cloud KMS CryptoKey Encrypter/Decrypter`, `Cloud KMS CryptoKey Encrypter`, `Cloud KMS CryptoKey Decrypter` roles assigned at the same time.",
+ "ImpactStatement": "Removed roles should be assigned to another user based on business needs.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `IAM & Admin/IAM` using `https://console.cloud.google.com/iam-admin/iam` 2. For any member having `Cloud KMS Admin` and any of the `Cloud KMS CryptoKey Encrypter/Decrypter`, `Cloud KMS CryptoKey Encrypter`, `Cloud KMS CryptoKey Decrypter` roles granted/assigned, click the `Delete Bin` icon to remove the role from the member. Note: Removing a role should be done based on the business requirement.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `IAM & Admin/IAM` by visiting: [https://console.cloud.google.com/iam-admin/iam](https://console.cloud.google.com/iam-admin/iam) 2. Ensure no member has the roles `Cloud KMS Admin` and any of the `Cloud KMS CryptoKey Encrypter/Decrypter`, `Cloud KMS CryptoKey Encrypter`, `Cloud KMS CryptoKey Decrypter` assigned. **From Google Cloud CLI** 1. List all users and role assignments: gcloud projects get-iam-policy PROJECT_ID 2. Ensure that there are no common users found in the member section for roles `cloudkms.admin` and any one of `Cloud KMS CryptoKey Encrypter/Decrypter`, `Cloud KMS CryptoKey Encrypter`, `Cloud KMS CryptoKey Decrypter`",
+ "AdditionalInformation": "Users granted with Owner (roles/owner) and Editor (roles/editor) have privileges equivalent to `Cloud KMS Admin` and `Cloud KMS CryptoKey Encrypter/Decrypter`. To avoid misuse, Owner and Editor roles should be granted to a very limited group of users. Use of these primitive privileges should be minimal.",
+ "References": "https://cloud.google.com/kms/docs/separation-of-duties",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.13",
+ "Description": "Ensure API Keys Only Exist for Active Services",
+ "Checks": [
+ "apikeys_key_exists"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "API Keys should only be used for services in cases where other authentication methods are unavailable. Unused keys with their permissions in tact may still exist within a project. Keys are insecure because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to use standard authentication flow instead.",
+ "RationaleStatement": "To avoid the security risk in using API keys, it is recommended to use standard authentication flow instead. Security risks involved in using API-Keys appear below: - API keys are simple encrypted strings - API keys do not identify the user or the application making the API request - API keys are typically accessible to clients, making it easy to discover and steal an API key",
+ "ImpactStatement": "Deleting an API key will break dependent applications (if any).",
+ "RemediationProcedure": "**From Console:** 1. Go to `APIs & ServicesCredentials` using https://console.cloud.google.com/apis/credentials. 1. In the section `API Keys`, to delete API Keys: Click the `Delete Bin Icon` in front of every `API Key Name`. **From Google Cloud Command Line** 1. Run the following from within the project you wish to audit gcloud services api-keys list --filter 1. Run the following command, providing the ID of the key or fully qualified identifier for the key for <key_id>: gcloud services api-keys delete <key_id> ",
+ "AuditProcedure": "**From Console:** 1. From within the Project you wish to audit Go to `APIs & ServicesCredentials`. 1. In the section `API Keys`, no API key should be listed. **From Google Cloud Command Line** 1. Run the following from within the project you wish to audit gcloud services api-keys list --filter 1. There should be no keys listed at the project level.",
+ "AdditionalInformation": "Google recommends using the standard authentication flow instead of using API keys. However, there are limited cases where API keys are more appropriate. For example, if there is a mobile application that needs to use the Google Cloud Translation API, but doesn't otherwise need a backend server, API keys are the simplest way to authenticate to that API. If a business requires API keys to be used, then the API keys should be secured properly.",
+ "References": "https://cloud.google.com/docs/authentication/api-keys:https://cloud.google.com/sdk/gcloud/reference/services/api-keys/list:https://cloud.google.com/docs/authentication:https://cloud.google.com/sdk/gcloud/reference/services/api-keys/delete",
+ "DefaultValue": "By default, API keys are not created for a project.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.14",
+ "Description": "Ensure API Keys Are Restricted To Use by Only Specified Hosts and Apps",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "API Keys should only be used for services in cases where other authentication methods are unavailable. In this case, unrestricted keys are insecure because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to restrict API key usage to trusted hosts, HTTP referrers and apps. It is recommended to use the more secure standard authentication flow instead.",
+ "RationaleStatement": "Security risks involved in using API-Keys appear below: - API keys are simple encrypted strings - API keys do not identify the user or the application making the API request - API keys are typically accessible to clients, making it easy to discover and steal an API key In light of these potential risks, Google recommends using the standard authentication flow instead of API keys. However, there are limited cases where API keys are more appropriate. For example, if there is a mobile application that needs to use the Google Cloud Translation API, but doesn't otherwise need a backend server, API keys are the simplest way to authenticate to that API. In order to reduce attack vectors, API-Keys can be restricted only to trusted hosts, HTTP referrers and applications.",
+ "ImpactStatement": "Setting `Application Restrictions` may break existing application functioning, if not done carefully.",
+ "RemediationProcedure": "**From Google Cloud Console** ***Leaving Keys in Place*** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, Click the `API Key Name`. The API Key properties display on a new page. 3. In the `Key restrictions` section, set the application restrictions to any of `HTTP referrers, IP addresses, Android apps, iOS apps`. 4. Click `Save`. 1. Repeat steps 2,3,4 for every unrestricted API key. **Note:** Do not set `HTTP referrers` to wild-cards (* or *.[TLD] or *.[TLD]/*) allowing access to any/wide HTTP referrer(s) Do not set `IP addresses` and referrer to `any host (0.0.0.0 or 0.0.0.0/0 or ::0)` ***Removing Keys*** Another option is to remove the keys entirely. 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, select the checkbox next to each key you wish to remove 3. Select `Delete` and confirm.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 1. In the section `API Keys`, Click the `API Key Name`. The API Key properties display on a new page. 1. For every API Key, ensure the section `Key restrictions` parameter `Application restrictions` is not set to `None`. Or, 1. Ensure `Application restrictions` is set to `HTTP referrers` and the referrer is not set to wild-cards `(* or *.[TLD] or *.[TLD]/*) allowing access to any/wide HTTP referrer(s)` Or, 1. Ensure `Application restrictions` is set to `IP addresses` and referrer is not set to `any host (0.0.0.0 or 0.0.0.0/0 or ::0)` **From Google Cloud Command Line** 1. Run the following from within the project you wish to audit gcloud services api-keys list --filter=-restrictions:* --format=table[box](displayName:label='Key With No Restrictions') ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/docs/authentication/api-keys:https://cloud.google.com/sdk/gcloud/reference/services/api-keys/list:https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update",
+ "DefaultValue": "By default, `Application Restrictions` are set to `None`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.15",
+ "Description": "Ensure API Keys Are Restricted to Only APIs That Application Needs Access",
+ "Checks": [
+ "apikeys_api_restrictions_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "API Keys should only be used for services in cases where other authentication methods are unavailable. API keys are always at risk because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to restrict API keys to use (call) only APIs required by an application.",
+ "RationaleStatement": "Security risks involved in using API-Keys are below: - API keys are simple encrypted strings - API keys do not identify the user or the application making the API request - API keys are typically accessible to clients, making it easy to discover and steal an API key In light of these potential risks, Google recommends using the standard authentication flow instead of API-Keys. However, there are limited cases where API keys are more appropriate. For example, if there is a mobile application that needs to use the Google Cloud Translation API, but doesn't otherwise need a backend server, API keys are the simplest way to authenticate to that API. In order to reduce attack surfaces by providing `least privileges`, API-Keys can be restricted to use (call) only APIs required by an application.",
+ "ImpactStatement": "Setting `API restrictions` may break existing application functioning, if not done carefully.",
+ "RemediationProcedure": "**From Console:** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, Click the `API Key Name`. The API Key properties display on a new page. 3. In the `Key restrictions` section go to `API restrictions`. 4. Click the `Select API` drop-down to choose an API. 5. Click `Save`. 6. Repeat steps 2,3,4,5 for every unrestricted API key **Note:** Do not set `API restrictions` to `Google Cloud APIs`, as this option allows access to all services offered by Google cloud. **From Google Cloud CLI** 1. List all API keys. gcloud services api-keys list 2. Note the `UID` of the key to add restrictions to. 3. Run the update command with the appropriate API target service or flags file with API target services and methods to add the required restrictions. Command with appropriate API target service: gcloud services api-keys update <UID> --api-target=service=<service> Command with flags file: gcloud services api-keys update <UID> --flags-file=<flags_file>.yaml Content of flags file: - --api-target: service: foo.service.com - --api-target: service: bar.service.com methods: - foomethod - barmethod Note: Flags can be found by running: gcloud services api-keys update --help Note: Services can be found by running: gcloud services list or in this documentation https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update",
+ "AuditProcedure": "**From Console:** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, Click the `API Key Name`. The API Key properties display on a new page. 3. For every API Key, ensure the section `Key restrictions` parameter `API restrictions` is not set to `None`. Or, Ensure `API restrictions` is not set to `Google Cloud APIs` **Note:** `Google Cloud APIs` represents the API collection of all cloud services/APIs offered by Google cloud. **From Google Cloud CLI** 1. List all API Keys. gcloud services api-keys list Each key should have a line that says `restrictions:` followed by varying parameters and NOT have a line saying `- service: cloudapis.googleapis.com` as shown here restrictions: apiTargets: - service: cloudapis.googleapis.com ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/docs/authentication/api-keys:https://cloud.google.com/apis/docs/overview",
+ "DefaultValue": "By default, `API restrictions` are set to `None`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.16",
+ "Description": "Ensure API Keys Are Rotated Every 90 Days",
+ "Checks": [
+ "apikeys_key_rotated_in_90_days"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "API Keys should only be used for services in cases where other authentication methods are unavailable. If they are in use it is recommended to rotate API keys every 90 days.",
+ "RationaleStatement": "Security risks involved in using API-Keys are listed below: - API keys are simple encrypted strings - API keys do not identify the user or the application making the API request - API keys are typically accessible to clients, making it easy to discover and steal an API key Because of these potential risks, Google recommends using the standard authentication flow instead of API Keys. However, there are limited cases where API keys are more appropriate. For example, if there is a mobile application that needs to use the Google Cloud Translation API, but doesn't otherwise need a backend server, API keys are the simplest way to authenticate to that API. Once a key is stolen, it has no expiration, meaning it may be used indefinitely unless the project owner revokes or regenerates the key. Rotating API keys will reduce the window of opportunity for an access key that is associated with a compromised or terminated account to be used. API keys should be rotated to ensure that data cannot be accessed with an old key that might have been lost, cracked, or stolen.",
+ "ImpactStatement": "`Regenerating Key` may break existing client connectivity as the client will try to connect with older API keys they have stored on devices.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, Click the `API Key Name`. The API Key properties display on a new page. 3. Click `REGENERATE KEY` to rotate API key. 4. Click `Save`. 5. Repeat steps 2,3,4 for every API key that has not been rotated in the last 90 days. **Note:** Do not set `HTTP referrers` to wild-cards (* or *.[TLD] or *.[TLD]/*) allowing access to any/wide HTTP referrer(s) Do not set `IP addresses` and referrer to `any host (0.0.0.0 or 0.0.0.0/0 or ::0)` **From Google Cloud CLI** There is not currently a way to regenerate and API key using gcloud commands. To 'regenerate' a key you will need to create a new one, duplicate the restrictions from the key being rotated, and delete the old key. 1. List existing keys. gcloud services api-keys list 2. Note the `UID` and restrictions of the key to regenerate. 3. Run this command to create a new API key. <key_name> is the display name of the new key. ` gcloud services api-keys create --display-name=<key_name> ` Note the `UID` of the newly created key 4. Run the update command to add required restrictions. Note - the restriction may vary for each key. Refer to this documentation for the appropriate flags. https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update gcloud services api-keys update <UID of new key> 5. Delete the old key. gcloud services api-keys delete <UID of old key> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `APIs & ServicesCredentials` using `https://console.cloud.google.com/apis/credentials` 2. In the section `API Keys`, for every key ensure the `creation date` is less than 90 days. **From Google Cloud CLI** To list keys, use the command gcloud services api-keys list Ensure the date in `createTime` is within 90 days.",
+ "AdditionalInformation": "There is no option to automatically regenerate (rotate) API keys periodically.",
+ "References": "https://developers.google.com/maps/api-security-best-practices#regenerate-apikey:https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.17",
+ "Description": "Ensure Essential Contacts is Configured for Organization",
+ "Checks": [
+ "iam_organization_essential_contacts_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that Essential Contacts is configured to designate email addresses for Google Cloud services to notify of important technical or security information.",
+ "RationaleStatement": "Many Google Cloud services, such as Cloud Billing, send out notifications to share important information with Google Cloud users. By default, these notifications are sent to members with certain Identity and Access Management (IAM) roles. With Essential Contacts, you can customize who receives notifications by providing your own list of contacts.",
+ "ImpactStatement": "There is no charge for Essential Contacts except for the 'Technical Incidents' category that is only available to premium support customers.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Essential Contacts` by visiting https://console.cloud.google.com/iam-admin/essential-contacts 2. Make sure the organization appears in the resource selector at the top of the page. The resource selector tells you what project, folder, or organization you are currently managing contacts for. 3. Click `+Add contact` 4. In the `Email` and `Confirm Email` fields, enter the email address of the contact. 5. From the `Notification categories` drop-down menu, select the notification categories that you want the contact to receive communications for. 6. Click `Save` **From Google Cloud CLI** 1. To add an organization Essential Contacts run a command: gcloud essential-contacts create --email=<EMAIL> --notification-categories=<NOTIFICATION_CATEGORIES> --organization=<ORGANIZATION_ID> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Essential Contacts` by visiting https://console.cloud.google.com/iam-admin/essential-contacts 2. Make sure the organization appears in the resource selector at the top of the page. The resource selector tells you what project, folder, or organization you are currently managing contacts for. 3. Ensure that appropriate email addresses are configured for each of the following notification categories: - `Legal` - `Security` - `Suspension` - `Technical` Alternatively, appropriate email addresses can be configured for the `All` notification category to receive all possible important notifications. **From Google Cloud CLI** 1. To list all configured organization Essential Contacts run a command: gcloud essential-contacts list --organization=<ORGANIZATION_ID> 2. Ensure at least one appropriate email address is configured for each of the following notification categories: - `LEGAL` - `SECURITY` - `SUSPENSION` - `TECHNICAL` Alternatively, appropriate email addresses can be configured for the `ALL` notification category to receive all possible important notifications.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/resource-manager/docs/managing-notification-contacts",
+ "DefaultValue": "By default, there are no Essential Contacts configured. In the absence of an Essential Contact, the following IAM roles are used to identify users to notify for the following categories: - **Legal**: `roles/billing.admin` - **Security**: `roles/resourcemanager.organizationAdmin` - **Suspension**: `roles/owner` - **Technical**: `roles/owner` - **Technical Incidents**: `roles/owner`",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "1.18",
+ "Description": "Ensure Secrets are Not Stored in Cloud Functions Environment Variables by Using Secret Manager",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Identity and Access Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Google Cloud Functions allow you to host serverless code that is executed when an event is triggered, without the requiring the management a host operating system. These functions can also store environment variables to be used by the code that may contain authentication or other information that needs to remain confidential.",
+ "RationaleStatement": "It is recommended to use the Secret Manager, because environment variables are stored unencrypted, and accessible for all users who have access to the code.",
+ "ImpactStatement": "There should be no impact on the Cloud Function. There are minor costs after 10,000 requests a month to the Secret Manager API as well for a high use of other functions. Modifying the Cloud Function to use the Secret Manager may prevent it running to completion.",
+ "RemediationProcedure": "Enable Secret Manager API for your Project **From Google Cloud Console** 1. Within the project you wish to enable, select the Navigation hamburger menu in the top left. Hover over 'APIs & Services' to under the heading 'Serverless', then select 'Enabled APIs & Services' in the menu that opens up. 2. Click the button '+ Enable APIS and Services' 3. In the Search bar, search for 'Secret Manager API' and select it. 4. Click the blue box that says 'Enable'. **From Google Cloud CLI** 1. Within the project you wish to enable the API in, run the following command. gcloud services enable Secret Manager API Reviewing Environment Variables That Should Be Migrated to Secret Manager **From Google Cloud Console** 1. Log in to the Google Cloud Web Portal (https://console.cloud.google.com/) 1. Go to Cloud Functions 1. Click on a function name from the list 1. Click on Edit and review the Runtime environment for variables that should be secrets. Leave this list open for the next step. **From Google Cloud CLI** 1. To view a list of your cloud functions run gcloud functions list 2. For each cloud function run the following command. gcloud functions describe <function_name> 3. Review the settings of the buildEnvironmentVariables and environmentVariables. Keep this information for the next step. Migrating Environment Variables to Secrets within the Secret Manager **From Google Cloud Console** 1. Go to the Secret Manager page in the Cloud Console. 1. On the Secret Manager page, click Create Secret. 1. On the Create secret page, under Name, enter the name of the Environment Variable you are replacing. This will then be the Secret Variable you will reference in your code. 1. You will also need to add a version. This is the actual value of the variable that will be referenced from the code. To add a secret version when creating the initial secret, in the Secret value field, enter the value from the Environment Variable you are replacing. 1. Leave the Regions section unchanged. 1. Click the Create secret button. 1. Repeat for all Environment Variables **From Google Cloud CLI** 1. Run the following command with the Environment Variable name you are replacing in the `<secret-id>`. It is most secure to point this command to a file with the Environment Variable value located in it, as if you entered it via command line it would show up in your shell’s command history. gcloud secrets create <secret-id> --data-file=/path/to/file.txt Granting your Runtime's Service Account Access to Secrets **From Google Cloud Console** 1. Within the project containing your runtime login with account that has the 'roles/secretmanager.secretAccessor' permission. 2. Select the Navigation hamburger menu in the top left. Hover over 'Security' to under the then select 'Secret Manager' in the menu that opens up. 3. Click the name of a secret listed in this screen. 4. If it is not already open, click Show Info Panel in this screen to open the panel. 5.In the info panel, click Add principal. 6.In the New principals field, enter the service account your function uses for its identity. (If you need help locating or updating your runtime's service account, please see the 'docs/securing/function-identity#runtime_service_account' reference.) 7. In the Select a role dropdown, choose Secret Manager and then Secret Manager Secret Accessor. **From Google Cloud CLI** As of the time of writing, using Google CLI to list Runtime variables is only in beta. Because this is likely to change we are not including it here. Modifying the Code to use the Secrets in Secret Manager **From Google Cloud Console** This depends heavily on which language your runtime is in. For the sake of the brevity of this recommendation, please see the '/docs/creating-and-accessing-secrets#access' reference for language specific instructions. **From Google Cloud CLI** This depends heavily on which language your runtime is in. For the sake of the brevity of this recommendation, please see the' /docs/creating-and-accessing-secrets#access' reference for language specific instructions. Deleting the Insecure Environment Variables **Be certain to do this step last.** Removing variables from code actively referencing them will prevent it from completing successfully. **From Google Cloud Console** 1. Select the Navigation hamburger menu in the top left. Hover over 'Security' then select 'Secret Manager' in the menu that opens up. 1. Click the name of a function. Click Edit. 1. Click Runtime, build and connections settings to expand the advanced configuration options. 1. Click 'Security’. Hover over the secret you want to remove, then click 'Delete'. 1. Click Next. Click Deploy. The latest version of the runtime will now reference the secrets in Secret Manager. **From Google Cloud CLI** gcloud functions deploy <Function name>--remove-env-vars <env vars> If you need to find the env vars to remove, they are from the step where ‘gcloud functions describe `<function_name>`’ was run.",
+ "AuditProcedure": "Determine if Confidential Information is Stored in your Functions in Cleartext **From Google Cloud Console** 1. Within the project you wish to audit, select the Navigation hamburger menu in the top left. Scroll down to under the heading 'Serverless', then select 'Cloud Functions' 1. Click on a function name from the list 1. Open the Variables tab and you will see both buildEnvironmentVariables and environmentVariables 1. Review the variables whether they are secrets 1. Repeat step 3-5 until all functions are reviewed **From Google Cloud CLI** 1. To view a list of your cloud functions run gcloud functions list 2. For each cloud function in the list run the following command. gcloud functions describe <function_name> 3. Review the settings of the buildEnvironmentVariables and environmentVariables. Determine if this is data that should not be publicly accessible. Determine if Secret Manager API is 'Enabled' for your Project **From Google Cloud Console** 1. Within the project you wish to audit, select the Navigation hamburger menu in the top left. Hover over 'APIs & Services' to under the heading 'Serverless', then select 'Enabled APIs & Services' in the menu that opens up. 1. Click the button '+ Enable APIS and Services' 1. In the Search bar, search for 'Secret Manager API' and select it. 1. If it is enabled, the blue box that normally says 'Enable' will instead say 'Manage'. **From Google Cloud CLI** 1. Within the project you wish to audit, run the following command. gcloud services list 2. If 'Secret Manager API' is in the list, it is enabled.",
+ "AdditionalInformation": "There are slight additional costs to using the Secret Manager API. Review the documentation to determine your organizations' needs.",
+ "References": "https://cloud.google.com/functions/docs/configuring/env-var#managing_secrets:https://cloud.google.com/secret-manager/docs/overview",
+ "DefaultValue": "By default Secret Manager is not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.1",
+ "Description": "Ensure That Cloud Audit Logging Is Configured Properly",
+ "Checks": [
+ "iam_audit_logs_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that Cloud Audit Logging is configured to track all admin activities and read, write access to user data.",
+ "RationaleStatement": "Cloud Audit Logging maintains two audit logs for each project, folder, and organization: Admin Activity and Data Access. 1. Admin Activity logs contain log entries for API calls or other administrative actions that modify the configuration or metadata of resources. Admin Activity audit logs are enabled for all services and cannot be configured. 2. Data Access audit logs record API calls that create, modify, or read user-provided data. These are disabled by default and should be enabled. There are three kinds of Data Access audit log information: - Admin read: Records operations that read metadata or configuration information. Admin Activity audit logs record writes of metadata and configuration information that cannot be disabled. - Data read: Records operations that read user-provided data. - Data write: Records operations that write user-provided data. It is recommended to have an effective default audit config configured in such a way that: 1. logtype is set to DATA_READ (to log user activity tracking) and DATA_WRITES (to log changes/tampering to user data). 2. audit config is enabled for all the services supported by the Data Access audit logs feature. 3. Logs should be captured for all users, i.e., there are no exempted users in any of the audit config sections. This will ensure overriding the audit config will not contradict the requirement.",
+ "ImpactStatement": "There is no charge for Admin Activity audit logs. Enabling the Data Access audit logs might result in your project being charged for the additional logs usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Audit Logs` by visiting [https://console.cloud.google.com/iam-admin/audit](https://console.cloud.google.com/iam-admin/audit). 2. Follow the steps at [https://cloud.google.com/logging/docs/audit/configure-data-access](https://cloud.google.com/logging/docs/audit/configure-data-access) to enable audit logs for all Google Cloud services. Ensure that no exemptions are allowed. **From Google Cloud CLI** 1. To read the project's IAM policy and store it in a file run a command: gcloud projects get-iam-policy PROJECT_ID > /tmp/project_policy.yaml Alternatively, the policy can be set at the organization or folder level. If setting the policy at the organization level, it is not necessary to also set it for each folder or project. gcloud organizations get-iam-policy ORGANIZATION_ID > /tmp/org_policy.yaml gcloud resource-manager folders get-iam-policy FOLDER_ID > /tmp/folder_policy.yaml 2. Edit policy in /tmp/policy.yaml, adding or changing only the audit logs configuration to: **Note: Admin Activity Logs are enabled by default, and cannot be disabled. So they are not listed in these configuration changes.** auditConfigs: - auditLogConfigs: - logType: DATA_WRITE - logType: DATA_READ service: allServices **Note:** `exemptedMembers:` is not set as audit logging should be enabled for all the users 3. To write new IAM policy run command: gcloud organizations set-iam-policy ORGANIZATION_ID /tmp/org_policy.yaml gcloud resource-manager folders set-iam-policy FOLDER_ID /tmp/folder_policy.yaml gcloud projects set-iam-policy PROJECT_ID /tmp/project_policy.yaml If the preceding command reports a conflict with another change, then repeat these steps, starting with the first step.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Audit Logs` by visiting [https://console.cloud.google.com/iam-admin/audit](https://console.cloud.google.com/iam-admin/audit). 2. Ensure that Admin Read, Data Write, and Data Read are enabled for all Google Cloud services and that no exemptions are allowed. **From Google Cloud CLI** 1. List the Identity and Access Management (IAM) policies for the project, folder, or organization: gcloud organizations get-iam-policy ORGANIZATION_ID gcloud resource-manager folders get-iam-policy FOLDER_ID gcloud projects get-iam-policy PROJECT_ID 2. Policy should have a default auditConfigs section which has the logtype set to DATA_WRITES and DATA_READ for all services. Note that projects inherit settings from folders, which in turn inherit settings from the organization. When called, projects get-iam-policy, the result shows only the policies set in the project, not the policies inherited from the parent folder or organization. Nevertheless, if the parent folder has Cloud Audit Logging enabled, the project does as well. Sample output for default audit configs may look like this: auditConfigs: - auditLogConfigs: - logType: ADMIN_READ - logType: DATA_WRITE - logType: DATA_READ service: allServices 3. Any of the auditConfigs sections should not have parameter exemptedMembers: set, which will ensure that Logging is enabled for all users and no user is exempted.",
+ "AdditionalInformation": "- Log type `DATA_READ` is equally important to that of `DATA_WRITE` to track detailed user activities. - BigQuery Data Access logs are handled differently from other data access logs. BigQuery logs are enabled by default and cannot be disabled. They do not count against logs allotment and cannot result in extra logs charges.",
+ "References": "https://cloud.google.com/logging/docs/audit/:https://cloud.google.com/logging/docs/audit/configure-data-access",
+ "DefaultValue": "Admin Activity logs are always enabled. They cannot be disabled. Data Access audit logs are disabled by default because they can be quite large.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.2",
+ "Description": "Ensure Google Workspace/Cloud Identity Data Sharing with Google Cloud is Enabled for Admin Audit Logging",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Google Workspace and Cloud Identity maintain audit logs for administrative actions, such as user creation, password changes, and modifications to security settings. By default, these logs are only available within the Google Admin Console. Enabling the \"Sharing of data with Google Cloud Services\" setting allows these logs to flow into the Google Cloud (GCP) Organization's Cloud Logging. This is critical for centralized security monitoring, long-term log retention, and the creation of automated alerts for high-risk identity events like privilege escalation.",
+ "RationaleStatement": "Without centralized logging of identity provider events, security teams cannot easily correlate Workspace/Identity administrative changes with GCP resource changes. If a Super Admin account is compromised, the audit trail must be preserved in a secure, centralized location to prevent an attacker from deleting evidence within the Workspace console.",
+ "ImpactStatement": "",
+ "AuditProcedure": "**From Google Admin Console**\n\n1. Log in to the Google Admin Console as a Super Admin.\n2. From the Home page, go to `Account` > `Account settings`.\n3. Click on the `Legal and compliance` section.\n4. Locate the setting titled `Sharing options - Google Cloud Platform Sharing Options` and verify that the status is set to `Enabled`.",
+ "RemediationProcedure": "**From Google Admin Console**\n\n1. Log in to the Google Admin Console as a Super Admin.\n2. From the Home page, go to `Account` > `Account settings`.\n3. Click on the `Legal and compliance` section.\n4. Locate the setting titled `Sharing options - Google Cloud Platform Sharing Options`, click on `Enabled` and click `Save`.\n5. (Optional but Recommended) Navigate to the GCP Console > `Logging` > `Logs Explorer` and verify that the logs are arriving from the admin portal.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, Google Workspace/Cloud Identity admin audit logs are only available within the Google Admin Console and are not shared with Google Cloud."
+ }
+ ]
+ },
+ {
+ "Id": "2.3",
+ "Description": "Ensure That Sinks Are Configured for All Log Entries",
+ "Checks": [
+ "cloudstorage_bucket_log_retention_policy_lock"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to create a sink that will export copies of all the log entries. This can help aggregate logs from multiple projects and export them to a Security Information and Event Management (SIEM).",
+ "RationaleStatement": "Log entries are held in Cloud Logging. To aggregate logs, export them to a SIEM. To keep them longer, it is recommended to set up a log sink. Exporting involves writing a filter that selects the log entries to export, and choosing a destination in Cloud Storage, BigQuery, or Cloud Pub/Sub. The filter and destination are held in an object called a sink. To ensure all log entries are exported to sinks, ensure that there is no filter configured for a sink. Sinks can be created in projects, organizations, folders, and billing accounts.",
+ "ImpactStatement": "There are no costs or limitations in Cloud Logging for exporting logs, but the export destinations charge for storing or transmitting the log data.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Logs Router` by visiting [https://console.cloud.google.com/logs/router](https://console.cloud.google.com/logs/router). 2. Click on the arrow symbol with `CREATE SINK` text. 3. Fill out the fields for `Sink details`. 4. Choose Cloud Logging bucket in the Select sink destination drop down menu. 5. Choose a log bucket in the next drop down menu. 6. If an inclusion filter is not provided for this sink, all ingested logs will be routed to the destination provided above. This may result in higher than expected resource usage. 7. Click `Create Sink`. For more information, see [https://cloud.google.com/logging/docs/export/configure_export_v2#dest-create](https://cloud.google.com/logging/docs/export/configure_export_v2#dest-create). **From Google Cloud CLI** To create a sink to export all log entries in a Google Cloud Storage bucket: gcloud logging sinks create <sink-name> storage.googleapis.com/DESTINATION_BUCKET_NAME Sinks can be created for a folder or organization, which will include all projects. gcloud logging sinks create <sink-name> storage.googleapis.com/DESTINATION_BUCKET_NAME --include-children --folder=FOLDER_ID | --organization=ORGANIZATION_ID **Note:** 1. A sink created by the command-line above will export logs in storage buckets. However, sinks can be configured to export logs into BigQuery, or Cloud Pub/Sub, or `Custom Destination`. 2. While creating a sink, the sink option `--log-filter` is not used to ensure the sink exports all log entries. 3. A sink can be created at a folder or organization level that collects the logs of all the projects underneath bypassing the option `--include-children` in the gcloud command.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Logs Router` by visiting [https://console.cloud.google.com/logs/router](https://console.cloud.google.com/logs/router). 2. For every sink, click the 3-dot button for Menu options and select `View sink details`. 3. Ensure there is at least one sink with an `empty` Inclusion filter. 4. Additionally, ensure that the resource configured as `Destination` exists. **From Google Cloud CLI** 1. Ensure that a sink with an `empty filter` exists. List the sinks for the project, folder or organization. If sinks are configured at a folder or organization level, they do not need to be configured for each project: gcloud logging sinks list --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID The output should list at least one sink with an `empty filter`. 2. Additionally, ensure that the resource configured as `Destination` exists. See [https://cloud.google.com/sdk/gcloud/reference/beta/logging/sinks/list](https://cloud.google.com/sdk/gcloud/reference/beta/logging/sinks/list) for more information.",
+ "AdditionalInformation": "For Command-Line Audit and Remediation, the sink destination of type `Cloud Storage Bucket` is considered. However, the destination could be configured to `Cloud Storage Bucket` or `BigQuery` or `Cloud PubSub` or `Custom Destination`. Command Line Interface commands would change accordingly.",
+ "References": "https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/logging/quotas:https://cloud.google.com/logging/docs/routing/overview:https://cloud.google.com/logging/docs/export/using_exported_logs:https://cloud.google.com/logging/docs/export/configure_export_v2:https://cloud.google.com/logging/docs/export/aggregated_exports:https://cloud.google.com/sdk/gcloud/reference/beta/logging/sinks/list",
+ "DefaultValue": "By default, there are no sinks configured.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.4",
+ "Description": "Ensure That Retention Policies on Cloud Storage Buckets Used for Exporting Logs Are Configured Using Bucket Lock",
+ "Checks": [
+ "cloudstorage_bucket_log_retention_policy_lock"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Enabling retention policies on log buckets will protect logs stored in cloud storage buckets from being overwritten or accidentally deleted. It is recommended to set up retention policies and configure Bucket Lock on all storage buckets that are used as log sinks.",
+ "RationaleStatement": "Logs can be exported by creating one or more sinks that include a log filter and a destination. As Cloud Logging receives new log entries, they are compared against each sink. If a log entry matches a sink's filter, then a copy of the log entry is written to the destination. Sinks can be configured to export logs in storage buckets. It is recommended to configure a data retention policy for these cloud storage buckets and to lock the data retention policy; thus permanently preventing the policy from being reduced or removed. This way, if the system is ever compromised by an attacker or a malicious insider who wants to cover their tracks, the activity logs are definitely preserved for forensics and security investigations.",
+ "ImpactStatement": "Locking a bucket is an irreversible action. Once you lock a bucket, you cannot remove the retention policy from the bucket or decrease the retention period for the policy. You will then have to wait for the retention period for all items within the bucket before you can delete them, and then the bucket.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. If sinks are **not** configured, first follow the instructions in the recommendation: `Ensure that sinks are configured for all Log entries`. 2. For each storage bucket configured as a sink, go to the Cloud Storage browser at `https://console.cloud.google.com/storage/browser/<BUCKET_NAME>`. 3. Select the Bucket Lock tab near the top of the page. 4. In the Retention policy entry, click the Add Duration link. The `Set a retention policy` dialog box appears. 5. Enter the desired length of time for the retention period and click `Save policy`. 6. Set the `Lock status` for this retention policy to `Locked`. **From Google Cloud CLI** 1. To list all sinks destined to storage buckets: gcloud logging sinks list --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID 2. For each storage bucket listed above, set a retention policy and lock it: gsutil retention set [TIME_DURATION] gs://[BUCKET_NAME] gsutil retention lock gs://[BUCKET_NAME] For more information, visit [https://cloud.google.com/storage/docs/using-bucket-lock#set-policy](https://cloud.google.com/storage/docs/using-bucket-lock#set-policy).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Open the Cloud Storage browser in the Google Cloud Console by visiting [https://console.cloud.google.com/storage/browser](https://console.cloud.google.com/storage/browser). 2. In the Column display options menu, make sure `Retention policy` is checked. 3. In the list of buckets, the retention period of each bucket is found in the `Retention policy` column. If the retention policy is locked, an image of a lock appears directly to the left of the retention period. **From Google Cloud CLI** 1. To list all sinks destined to storage buckets: gcloud logging sinks list --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID 2. For every storage bucket listed above, verify that retention policies and Bucket Lock are enabled: gsutil retention get gs://BUCKET_NAME For more information, see [https://cloud.google.com/storage/docs/using-bucket-lock#view-policy](https://cloud.google.com/storage/docs/using-bucket-lock#view-policy).",
+ "AdditionalInformation": "Caution: Locking a retention policy is an irreversible action. Once locked, you must delete the entire bucket in order to remove the bucket's retention policy. However, before you can delete the bucket, you must be able to delete all the objects in the bucket, which itself is only possible if all the objects have reached the retention period set by the retention policy.",
+ "References": "https://cloud.google.com/storage/docs/bucket-lock:https://cloud.google.com/storage/docs/using-bucket-lock:https://cloud.google.com/storage/docs/bucket-lock",
+ "DefaultValue": "By default, storage buckets used as log sinks do not have retention policies and Bucket Lock configured.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.5",
+ "Description": "Ensure Log Metric Filter and Alerts Exist for Project Ownership Assignments/Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In order to prevent unnecessary project ownership assignments to users/service-accounts and further misuses of projects and resources, all `roles/Owner` assignments should be monitored. Members (users/Service-Accounts) with a role assignment to primitive role `roles/Owner` are project owners. The project owner has all the privileges on the project the role belongs to. These are summarized below: - All viewer permissions on all GCP Services within the project - Permissions for actions that modify the state of all GCP services within the project - Manage roles and permissions for a project and all resources within the project - Set up billing for a project Granting the owner role to a member (user/Service-Account) will allow that member to modify the Identity and Access Management (IAM) policy. Therefore, grant the owner role only if the member has a legitimate purpose to manage the IAM policy. This is because the project IAM policy contains sensitive access control data. Having a minimal set of users allowed to manage IAM policy will simplify any auditing that may be necessary.",
+ "RationaleStatement": "Project ownership has the highest level of privileges on a project. To avoid misuse of project resources, the project ownership assignment/change actions mentioned above should be monitored and alerted to concerned recipients. - Sending project ownership invites - Acceptance/Rejection of project ownership invite by user - Adding `roleOwner` to a user/service-account - Removing a user/Service account from `roleOwner`",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: (protoPayload.serviceName=cloudresourcemanager.googleapis.com) AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=REMOVE AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=ADD AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) 4. Click `Submit Filter`. The logs display based on the filter text entered by the user. 5. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and the `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the advanced logs query. 6. Click `Create Metric`. **Create the display prescribed Alert Policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the desired metric and select `Create alert from Metric`. A new page opens. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value will ensure that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notifications channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create a prescribed Log Metric: - Use the command: gcloud beta logging metrics create - Reference for Command Usage: https://cloud.google.com/sdk/gcloud/reference/beta/logging/metrics/create Create prescribed Alert Policy - Use the command: gcloud alpha monitoring policies create - Reference for Command Usage: https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure that the prescribed log metric is present:** 1. Go to `Logging/Log-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure that at least one metric `<Log_Metric_Name>` is present with filter text: (protoPayload.serviceName=cloudresourcemanager.googleapis.com) AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=REMOVE AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=ADD AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) **Ensure that the prescribed Alerting Policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of zero(0) for greater than zero(0) seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for your organization. 5. Ensure that the appropriate notifications channels have been set up. **From Google Cloud CLI** **Ensure that the prescribed log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with filter set to: (protoPayload.serviceName=cloudresourcemanager.googleapis.com) AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=REMOVE AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action=ADD AND protoPayload.serviceData.policyDelta.bindingDeltas.role=roles/owner) 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains an least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "1. Project ownership assignments for a user cannot be done using the gcloud utility as assigning project ownership to a user requires sending, and the user accepting, an invitation. 2. Project Ownership assignment to a service account does not send any invites. SetIAMPolicy to `role/owner`is directly performed on service accounts.",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.6",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for Audit Configuration Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Google Cloud Platform (GCP) services write audit log entries to the Admin Activity and Data Access logs to help answer the questions of, who did what, where, and when? within GCP projects. Cloud audit logging records information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by GCP services. Cloud audit logging provides a history of GCP API calls for an account, including API calls made via the console, SDKs, command-line tools, and other GCP services.",
+ "RationaleStatement": "Admin activity and data access logs produced by cloud audit logging enable security analysis, resource change tracking, and compliance auditing. Configuring the metric filter and alerts for audit configuration changes ensures the recommended state of audit configuration is maintained so that all activities in the project are audit-able at any point in time.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: protoPayload.methodName=SetIamPolicy AND protoPayload.serviceData.policyDelta.auditConfigDeltas:* 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This will ensure that the log metric counts the number of log entries matching the user's advanced logs query. 6. Click `Create Metric`. **Create a prescribed Alert Policy:** 1. Identify the new metric the user just created, under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page opens. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the organization. For example, a threshold of zero(0) for the most recent value will ensure that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notifications channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create a prescribed Log Metric: - Use the command: gcloud beta logging metrics create - Reference for command usage: [https://cloud.google.com/sdk/gcloud/reference/beta/logging/metrics/create ](https://cloud.google.com/sdk/gcloud/reference/beta/logging/metrics/create) Create prescribed Alert Policy - Use the command: gcloud alpha monitoring policies create - Reference for command usage: [https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create](https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create)",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure the prescribed log metric is present:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure that at least one metric `<Log_Metric_Name>` is present with the filter text: protoPayload.methodName=SetIamPolicy AND protoPayload.serviceData.policyDelta.auditConfigDeltas:* **Ensure that the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of 0 for greater than zero(0) seconds`, means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that appropriate notifications channels have been set up. **From Google Cloud CLI** **Ensure that the prescribed log metric is present:** 1. List the log metrics: gcloud beta logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to: protoPayload.methodName=SetIamPolicy AND protoPayload.serviceData.policyDelta.auditConfigDeltas:* 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains at least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/logging/docs/audit/configure-data-access#getiampolicy-setiampolicy",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.7",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for Custom Role Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for changes to Identity and Access Management (IAM) role creation, deletion and updating activities.",
+ "RationaleStatement": "Google Cloud IAM provides predefined roles that give granular access to specific Google Cloud Platform resources and prevent unwanted access to other resources. However, to cater to organization-specific needs, Cloud IAM also provides the ability to create custom roles. Project owners and administrators with the Organization Role Administrator role or the IAM Role Administrator role can create custom roles. Monitoring role creation, deletion and updating activities will help in identifying any over-privileged role at early stages.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage.",
+ "RemediationProcedure": "**From Console:** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 1. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 1. Clear any text and add: resource.type=iam_role AND (protoPayload.methodName = google.iam.admin.v1.CreateRole OR protoPayload.methodName=google.iam.admin.v1.DeleteRole OR protoPayload.methodName=google.iam.admin.v1.UpdateRole OR protoPayload.methodName=google.iam.admin.v1.UndeleteRole) 1. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 1. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the advanced logs query. 1. Click `Create Metric`. **Create a prescribed Alert Policy:** 1. Identify the new metric that was just created under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the metric and select `Create alert from Metric`. A new page displays. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value ensures that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 1. Configure the desired notification channels in the section `Notifications`. 1. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed Log Metric: - Use the command: gcloud logging metrics create Create the prescribed Alert Policy: - Use the command: gcloud alpha monitoring policies create <policy name>",
+ "AuditProcedure": "**From Console:** **Ensure that the prescribed log metric is present:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure that at least one metric `<Log_Metric_Name>` is present with filter text: resource.type=iam_role AND (protoPayload.methodName=google.iam.admin.v1.CreateRole OR protoPayload.methodName=google.iam.admin.v1.DeleteRole OR protoPayload.methodName=google.iam.admin.v1.UpdateRole OR protoPayload.methodName=google.iam.admin.v1.UndeleteRole) **Ensure that the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of zero(0) for greater than zero(0) seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that the appropriate notifications channels have been set up. **From Google Cloud CLI** Ensure that the prescribed log metric is present: 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to: resource.type=iam_role AND (protoPayload.methodName = google.iam.admin.v1.CreateRole OR protoPayload.methodName=google.iam.admin.v1.DeleteRole OR protoPayload.methodName=google.iam.admin.v1.UpdateRole OR protoPayload.methodName=google.iam.admin.v1.UndeleteRole) 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains an least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/iam/docs/understanding-custom-roles",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.8",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for VPC Network Firewall Rule Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for Virtual Private Cloud (VPC) Network Firewall rule changes.",
+ "RationaleStatement": "Monitoring for Create or Update Firewall rule events gives insight to network access changes and may reduce the time it takes to detect suspicious activity.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: resource.type=gce_firewall_rule AND (protoPayload.methodName:compute.firewalls.patch OR protoPayload.methodName:compute.firewalls.insert OR protoPayload.methodName:compute.firewalls.delete) 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the advanced logs query. 6. Click `Create Metric`. **Create the prescribed Alert Policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page displays. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value ensures that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notifications channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed Log Metric - Use the command: gcloud logging metrics create Create the prescribed alert policy: - Use the command: gcloud alpha monitoring policies create",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure that the prescribed log metric is present:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure at least one metric `<Log_Metric_Name>` is present with this filter text: resource.type=gce_firewall_rule AND (protoPayload.methodName:compute.firewalls.patch OR protoPayload.methodName:compute.firewalls.insert OR protoPayload.methodName:compute.firewalls.delete) **Ensure that the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of zero(0) for greater than zero(0) seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that appropriate notification channels have been set up. **From Google Cloud CLI** **Ensure that the prescribed log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to: resource.type=gce_firewall_rule AND (protoPayload.methodName:compute.firewalls.patch OR protoPayload.methodName:compute.firewalls.insert OR protoPayload.methodName:compute.firewalls.delete) 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains an least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/vpc/docs/firewalls",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.9",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for VPC Network Route Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for Virtual Private Cloud (VPC) network route changes.",
+ "RationaleStatement": "Google Cloud Platform (GCP) routes define the paths network traffic takes from a VM instance to another destination. The other destination can be inside the organization VPC network (such as another VM) or outside of it. Every route consists of a destination and a next hop. Traffic whose destination IP is within the destination range is sent to the next hop for delivery. Monitoring changes to route tables will help ensure that all VPC traffic flows through an expected path.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed Log Metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter` 3. Clear any text and add: resource.type=gce_route AND (protoPayload.methodName:compute.routes.delete OR protoPayload.methodName:compute.routes.insert) 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the user's advanced logs query. 6. Click `Create Metric`. **Create the prescribed alert policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page displays. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value ensures that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notification channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed Log Metric: - Use the command: gcloud logging metrics create Create the prescribed the alert policy: - Use the command: gcloud alpha monitoring policies create",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure that the prescribed Log metric is present:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure that at least one metric `<Log_Metric_Name>` is present with the filter text: resource.type=gce_route AND (protoPayload.methodName:compute.routes.delete OR protoPayload.methodName:compute.routes.insert) **Ensure the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting: [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of 0 for greater than zero(0) seconds` means that the alert will trigger for any new owner change. Verify that the chosen alert thresholds make sense for the user's organization. 5. Ensure that the appropriate notification channels have been set up. **From Google Cloud CLI** **Ensure the prescribed log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to: resource.type=gce_route AND (protoPayload.methodName:compute.routes.delete OR protoPayload.methodName:compute.routes.insert) 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains an least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/storage/docs/access-control/iam:https://cloud.google.com/sdk/gcloud/reference/beta/logging/metrics/create:https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.10",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for VPC Network Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for Virtual Private Cloud (VPC) network changes.",
+ "RationaleStatement": "It is possible to have more than one VPC within a project. In addition, it is also possible to create a peer connection between two VPCs enabling network traffic to route between VPCs. Monitoring changes to a VPC will help ensure VPC traffic flow is not getting impacted.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: resource.type=gce_network AND (protoPayload.methodName:compute.networks.insert OR protoPayload.methodName:compute.networks.patch OR protoPayload.methodName:compute.networks.delete OR protoPayload.methodName:compute.networks.removePeering OR protoPayload.methodName:compute.networks.addPeering) 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on the right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the user's advanced logs query. 6. Click `Create Metric`. **Create the prescribed alert policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page appears. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of 0 for the most recent value will ensure that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notification channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed Log Metric: - Use the command: gcloud logging metrics create Create the prescribed alert policy: - Use the command: gcloud alpha monitoring policies create",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure the prescribed log metric is present:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure at least one metric `<Log_Metric_Name>` is present with filter text: resource.type=gce_network AND (protoPayload.methodName:compute.networks.insert OR protoPayload.methodName:compute.networks.patch OR protoPayload.methodName:compute.networks.delete OR protoPayload.methodName:compute.networks.removePeering OR protoPayload.methodName:compute.networks.addPeering) **Ensure the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of 0 for greater than 0 seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that appropriate notification channels have been set up. **From Google Cloud CLI** **Ensure the log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with filter set to: resource.type=gce_network AND protoPayload.methodName=beta.compute.networks.insert OR protoPayload.methodName=beta.compute.networks.patch OR protoPayload.methodName=v1.compute.networks.delete OR protoPayload.methodName=v1.compute.networks.removePeering OR protoPayload.methodName=v1.compute.networks.addPeering 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains at least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/vpc/docs/overview",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.11",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for Cloud Storage IAM Permission Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for Cloud Storage Bucket IAM changes.",
+ "RationaleStatement": "Monitoring changes to cloud storage bucket permissions may reduce the time needed to detect and correct permissions on sensitive cloud storage buckets and objects inside the bucket.",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed log metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: resource.type=gcs_bucket AND protoPayload.methodName=storage.setIamPermissions 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the user's advanced logs query. 6. Click `Create Metric`. **Create the prescribed Alert Policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page appears. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value will ensure that a notification is triggered for every owner change in the project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notifications channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed Log Metric: - Use the command: gcloud beta logging metrics create Create the prescribed alert policy: - Use the command: gcloud alpha monitoring policies create",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure the prescribed log metric is present:** 1. For each project that contains cloud storage buckets, go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure at least one metric `<Log_Metric_Name>` is present with the filter text: resource.type=gcs_bucket AND protoPayload.methodName=storage.setIamPermissions **Ensure that the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of 0 for greater than 0 seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that the appropriate notifications channels have been set up. **From Google Cloud CLI** **Ensure that the prescribed log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to: resource.type=gcs_bucket AND protoPayload.methodName=storage.setIamPermissions 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains an least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/storage/docs/overview:https://cloud.google.com/storage/docs/access-control/iam-roles",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.12",
+ "Description": "Ensure That the Log Metric Filter and Alerts Exist for SQL Instance Configuration Changes",
+ "Checks": [
+ "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that a metric filter and alarm be established for SQL instance configuration changes.",
+ "RationaleStatement": "Monitoring changes to SQL instance configuration changes may reduce the time needed to detect and correct misconfigurations done on the SQL server. Below are a few of the configurable options which may the impact security posture of an SQL instance: - Enable auto backups and high availability: Misconfiguration may adversely impact business continuity, disaster recovery, and high availability - Authorize networks: Misconfiguration may increase exposure to untrusted networks",
+ "ImpactStatement": "Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.",
+ "RemediationProcedure": "**From Google Cloud Console** **Create the prescribed Log Metric:** 1. Go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics) and click CREATE METRIC. 2. Click the down arrow symbol on the `Filter Bar` at the rightmost corner and select `Convert to Advanced Filter`. 3. Clear any text and add: protoPayload.methodName=cloudsql.instances.update 4. Click `Submit Filter`. Display logs appear based on the filter text entered by the user. 5. In the `Metric Editor` menu on right, fill out the name field. Set `Units` to `1` (default) and `Type` to `Counter`. This ensures that the log metric counts the number of log entries matching the user's advanced logs query. 6. Click `Create Metric`. **Create the prescribed alert policy:** 1. Identify the newly created metric under the section `User-defined Metrics` at [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. Click the 3-dot icon in the rightmost column for the new metric and select `Create alert from Metric`. A new page appears. 3. Fill out the alert policy configuration and click `Save`. Choose the alerting threshold and configuration that makes sense for the user's organization. For example, a threshold of zero(0) for the most recent value will ensure that a notification is triggered for every owner change in the user's project: Set `Aggregator` to `Count` Set `Configuration`: - Condition: above - Threshold: 0 - For: most recent value 4. Configure the desired notification channels in the section `Notifications`. 5. Name the policy and click `Save`. **From Google Cloud CLI** Create the prescribed log metric: - Use the command: gcloud logging metrics create Create the prescribed alert policy: - Use the command: gcloud alpha monitoring policies create - Reference for command usage: [https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create](https://cloud.google.com/sdk/gcloud/reference/alpha/monitoring/policies/create)",
+ "AuditProcedure": "**From Google Cloud Console** **Ensure the prescribed log metric is present:** 1. For each project that contains Cloud SQL instances, go to `Logging/Logs-based Metrics` by visiting [https://console.cloud.google.com/logs/metrics](https://console.cloud.google.com/logs/metrics). 2. In the `User-defined Metrics` section, ensure that at least one metric `<Log_Metric_Name>` is present with the filter text: protoPayload.methodName=cloudsql.instances.update **Ensure that the prescribed alerting policy is present:** 3. Go to `Alerting` by visiting [https://console.cloud.google.com/monitoring/alerting](https://console.cloud.google.com/monitoring/alerting). 4. Under the `Policies` section, ensure that at least one alert policy exists for the log metric above. Clicking on the policy should show that it is configured with a condition. For example, `Violates when: Any logging.googleapis.com/user/<Log Metric Name> stream` `is above a threshold of zero(0) for greater than zero(0) seconds` means that the alert will trigger for any new owner change. Verify that the chosen alerting thresholds make sense for the user's organization. 5. Ensure that the appropriate notifications channels have been set up. **From Google Cloud CLI** **Ensure that the prescribed log metric is present:** 1. List the log metrics: gcloud logging metrics list --format json 2. Ensure that the output contains at least one metric with the filter set to protoPayload.methodName=cloudsql.instances.update 3. Note the value of the property `metricDescriptor.type` for the identified metric, in the format `logging.googleapis.com/user/<Log Metric Name>`. **Ensure that the prescribed alerting policy is present:** 4. List the alerting policies: gcloud alpha monitoring policies list --format json 5. Ensure that the output contains at least one alert policy where: - `conditions.conditionThreshold.filter` is set to `metric.type=logging.googleapis.com/user/<Log Metric Name>` - AND `enabled` is set to `true`",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/logging/docs/logs-based-metrics/:https://cloud.google.com/monitoring/custom-metrics/:https://cloud.google.com/monitoring/alerts/:https://cloud.google.com/logging/docs/reference/tools/gcloud-logging:https://cloud.google.com/storage/docs/overview:https://cloud.google.com/sql/docs/:https://cloud.google.com/sql/docs/mysql/:https://cloud.google.com/sql/docs/postgres/",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.13",
+ "Description": "Ensure That Cloud DNS Logging Is Enabled for All VPC Networks",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Cloud DNS logging records the queries from the name servers within your VPC to Stackdriver. Logged queries can come from Compute Engine VMs, GKE containers, or other GCP resources provisioned within the VPC.",
+ "RationaleStatement": "Security monitoring and forensics cannot depend solely on IP addresses from VPC flow logs, especially when considering the dynamic IP usage of cloud resources, HTTP virtual host routing, and other technology that can obscure the DNS name used by a client from the IP address. Monitoring of Cloud DNS logs provides visibility to DNS names requested by the clients within the VPC. These logs can be monitored for anomalous domain names, evaluated against threat intelligence, and Note: For full capture of DNS, firewall must block egress UDP/53 (DNS) and TCP/443 (DNS over HTTPS) to prevent client from using external DNS name server for resolution.",
+ "ImpactStatement": "Enabling of Cloud DNS logging might result in your project being charged for the additional logs usage.",
+ "RemediationProcedure": "**From Google Cloud CLI** **Add New DNS Policy With Logging Enabled** For each VPC network that needs a DNS policy with logging enabled: gcloud dns policies create enable-dns-logging --enable-logging --description=Enable DNS Logging --networks=VPC_NETWORK_NAME The VPC_NETWORK_NAME can be one or more networks in comma-separated list **Enable Logging for Existing DNS Policy** For each VPC network that has an existing DNS policy that needs logging enabled: gcloud dns policies update POLICY_NAME --enable-logging --networks=VPC_NETWORK_NAME The VPC_NETWORK_NAME can be one or more networks in comma-separated list",
+ "AuditProcedure": "**From Google Cloud CLI** 1. List all VPCs networks in a project: gcloud compute networks list --format=table[box,title='All VPC Networks'](name:label='VPC Network Name') 2. List all DNS policies, logging enablement, and associated VPC networks: gcloud dns policies list --flatten=networks[] --format=table[box,title='All DNS Policies By VPC Network'](name:label='Policy Name',enableLogging:label='Logging Enabled':align=center,networks.networkUrl.basename():label='VPC Network Name') Each VPC Network should be associated with a DNS policy with logging enabled.",
+ "AdditionalInformation": "Additional Info - Only queries that reach a name server are logged. Cloud DNS resolvers cache responses, queries answered from caches, or direct queries to an external DNS resolver outside the VPC are not logged.",
+ "References": "https://cloud.google.com/dns/docs/monitoring",
+ "DefaultValue": "Cloud DNS logging is disabled by default on each network.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.14",
+ "Description": "Ensure Cloud Asset Inventory Is Enabled",
+ "Checks": [
+ "iam_cloud_asset_inventory_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "GCP Cloud Asset Inventory is services that provides a historical view of GCP resources and IAM policies through a time-series database. The information recorded includes metadata on Google Cloud resources, metadata on policies set on Google Cloud projects or resources, and runtime information gathered within a Google Cloud resource. Cloud Asset Inventory Service (CAIS) API enablement is not required for operation of the service, but rather enables the mechanism for searching/exporting CAIS asset data directly.",
+ "RationaleStatement": "The GCP resources and IAM policies captured by GCP Cloud Asset Inventory enables security analysis, resource change tracking, and compliance auditing. It is recommended GCP Cloud Asset Inventory be enabled for all GCP projects.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** Enable the Cloud Asset API: 1. Go to `API & Services/Library` by visiting [https://console.cloud.google.com/apis/library](https://console.cloud.google.com/apis/library) 2. Search for `Cloud Asset API` and select the result for _Cloud Asset API_ 3. Click the `ENABLE` button. **From Google Cloud CLI** Enable the Cloud Asset API: 1. Enable the Cloud Asset API through the services interface: gcloud services enable cloudasset.googleapis.com ",
+ "AuditProcedure": "**From Google Cloud Console** Ensure that the Cloud Asset API is enabled: 1. Go to `API & Services/Library` by visiting [https://console.cloud.google.com/apis/library](https://console.cloud.google.com/apis/library) 2. Search for `Cloud Asset API` and select the result for _Cloud Asset API_ 3. Ensure that `API Enabled` is displayed. **From Google Cloud CLI** Ensure that the Cloud Asset API is enabled: 1. Query enabled services: gcloud services list --enabled --filter=name:cloudasset.googleapis.com If the API is listed, then it is enabled. If the response is `Listed 0 items` the API is not enabled.",
+ "AdditionalInformation": "Additional info - Cloud Asset Inventory only keeps a five-week history of Google Cloud asset metadata. If a longer history is desired, automation to export the history to Cloud Storage or BigQuery should be evaluated. Users need not enable CAI API if they don't have any plans to export.",
+ "References": "https://cloud.google.com/asset-inventory/docs",
+ "DefaultValue": "The Cloud Asset Inventory API is disabled by default in each project.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.15",
+ "Description": "Ensure 'Access Transparency' is 'Enabled'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "GCP Access Transparency provides audit logs for all actions that Google personnel take in your Google Cloud resources.",
+ "RationaleStatement": "Controlling access to your information is one of the foundations of information security. Given that Google Employees do have access to your organizations' projects for support reasons, you should have logging in place to view who, when, and why your information is being accessed.",
+ "ImpactStatement": "To use Access Transparency your organization will need to have at one of the following support level: Premium, Enterprise, Platinum, or Gold. There will be subscription costs associated with support, as well as increased storage costs for storing the logs. You will also not be able to turn Access Transparency off yourself, and you will need to submit a service request to Google Cloud Support.",
+ "RemediationProcedure": "**From Google Cloud Console** **Add privileges to enable Access Transparency** 1. From the Google Cloud Home, within the project you wish to check, click on the Navigation hamburger menu in the top left. Hover over the 'IAM and Admin'. Select `IAM` in the top of the column that opens. 2. Click the blue button the says `+add` at the top of the screen. 3. In the `principals` field, select a user or group by typing in their associated email address. 4. Click on the `role` field to expand it. In the filter field enter `Access Transparency Admin` and select it. 5. Click `save`. **Verify that the Google Cloud project is associated with a billing account** 1. From the Google Cloud Home, click on the Navigation hamburger menu in the top left. Select `Billing`. 2. If you see `This project is not associated with a billing account` you will need to enter billing information or switch to a project with a billing account. **Enable Access Transparency** 1. From the Google Cloud Home, click on the Navigation hamburger menu in the top left. Hover over the IAM & Admin Menu. Select `settings` in the middle of the column that opens. 2. Click the blue button labeled Enable `Access Transparency for Organization`",
+ "AuditProcedure": "**From Google Cloud Console** **Determine if Access Transparency is Enabled** 1. From the Google Cloud Home, click on the Navigation hamburger menu in the top left. Hover over the IAM & Admin Menu. Select `settings` in the middle of the column that opens. 2. The status will be under the heading `Access Transparency`. Status should be `Enabled`",
+ "AdditionalInformation": "To enable Access Transparency for your Google Cloud organization, your Google Cloud organization must have one of the following customer support levels: Premium, Enterprise, Platinum, or Gold.",
+ "References": "https://cloud.google.com/cloud-provider-access-management/access-transparency/docs/overview:https://cloud.google.com/cloud-provider-access-management/access-transparency/docs/enable:https://cloud.google.com/cloud-provider-access-management/access-transparency/docs/reading-logs:https://cloud.google.com/cloud-provider-access-management/access-transparency/docs/reading-logs#justification_reason_codes:https://cloud.google.com/cloud-provider-access-management/access-transparency/docs/supported-services",
+ "DefaultValue": "By default Access Transparency is not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.16",
+ "Description": "Ensure 'Access Approval' is 'Enabled'",
+ "Checks": [
+ "iam_account_access_approval_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "GCP Access Approval enables you to require your organizations' explicit approval whenever Google support try to access your projects. You can then select users within your organization who can approve these requests through giving them a security role in IAM. All access requests display which Google Employee requested them in an email or Pub/Sub message that you can choose to Approve. This adds an additional control and logging of who in your organization approved/denied these requests.",
+ "RationaleStatement": "Controlling access to your information is one of the foundations of information security. Google Employees do have access to your organizations' projects for support reasons. With Access Approval, organizations can then be certain that their information is accessed by only approved Google Personnel.",
+ "ImpactStatement": "To use Access Approval your organization will need have enabled Access Transparency and have at one of the following support level: Enhanced or Premium. There will be subscription costs associated with these support levels, as well as increased storage costs for storing the logs. You will also not be able to turn the Access Transparency which Access Approval depends on, off yourself. To do so you will need to submit a service request to Google Cloud Support. There will also be additional overhead in managing user permissions. There may also be a potential delay in support times as Google Personnel will have to wait for their access to be approved.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. From the Google Cloud Home, within the project you wish to enable, click on the Navigation hamburger menu in the top left. Hover over the `Security` Menu. Select `Access Approval` in the middle of the column that opens. 2. The status will be displayed here. On this screen, there is an option to click `Enroll`. If it is greyed out and you see an error bar at the top of the screen that says `Access Transparency is not enabled` please view the corresponding reference within this section to enable it. 3. In the second screen click `Enroll`. **Grant an IAM Group or User the role with permissions to Add Users to be Access Approval message Recipients** 1. From the Google Cloud Home, within the project you wish to enable, click on the Navigation hamburger menu in the top left. Hover over the `IAM and Admin`. Select `IAM` in the middle of the column that opens. 2. Click the blue button the says `+ ADD` at the top of the screen. 3. In the `principals` field, select a user or group by typing in their associated email address. 4. Click on the role field to expand it. In the filter field enter `Access Approval Approver` and select it. 5. Click `save`. **Add a Group or User as an Approver for Access Approval Requests** 1. As a user with the `Access Approval Approver` permission, within the project where you wish to add an email address to which request will be sent, click on the Navigation hamburger menu in the top left. Hover over the `Security` Menu. Select `Access Approval` in the middle of the column that opens. 2. Click `Manage Settings` 3. Under `Set up approval notifications`, enter the email address associated with a Google Cloud User or Group you wish to send Access Approval requests to. All future access approvals will be sent as emails to this address. **From Google Cloud CLI** 1. To update all services in an entire project, run the following command from an account that has permissions as an 'Approver for Access Approval Requests' gcloud access-approval settings update --project=<project name> --enrolled_services=all --notification_emails='<email recipient for access approval requests>@<domain name>' ",
+ "AuditProcedure": "**From Google Cloud Console** **Determine if Access Transparency is Enabled as it is a Dependency** 1. From the Google Cloud Home inside the project you wish to audit, click on the Navigation hamburger menu in the top left. Hover over the `IAM & Admin` Menu. Select `settings` in the middle of the column that opens. 2. The status should be Enabled' under the heading `Access Transparency` **Determine if Access Approval is Enabled** 1. From the Google Cloud Home, within the project you wish to check, click on the Navigation hamburger menu in the top left. Hover over the `Security` Menu. Select `Access Approval` in the middle of the column that opens. 2. The status will be displayed here. If you see a screen saying you need to enroll in Access Approval, it is not enabled. **From Google Cloud CLI** **Determine if Access Approval is Enabled** 1. From within the project you wish to audit, run the following command. gcloud access-approval settings get 2. The status will be displayed in the output. IF Access Approval is not enabled you should get this output: API [accessapproval.googleapis.com] not enabled on project [-----]. Would you like to enable and retry (this will take a few minutes)? (y/N)? After entering `Y` if you get the following output, it means that `Access Transparency` is not enabled: ERROR: (gcloud.access-approval.settings.get) FAILED_PRECONDITION: Precondition check failed. ",
+ "AdditionalInformation": "The recipients of Access Requests will also need to be logged into a Google Cloud account associated with an email address in this list. To approve requests they can click approve within the email. Or they can view requests at the the Access Approval page within the Security submenu.",
+ "References": "https://cloud.google.com/cloud-provider-access-management/access-approval/docs:https://cloud.google.com/cloud-provider-access-management/access-approval/docs/overview:https://cloud.google.com/cloud-provider-access-management/access-approval/docs/quickstart-custom-key:https://cloud.google.com/cloud-provider-access-management/access-approval/docs/supported-services:https://cloud.google.com/cloud-provider-access-management/access-approval/docs/view-historical-requests",
+ "DefaultValue": "By default Access Approval and its dependency of Access Transparency are not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "2.17",
+ "Description": "Ensure Logging is enabled for HTTP(S) Load Balancer",
+ "Checks": [
+ "compute_loadbalancer_logging_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Logging and Monitoring",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Logging enabled on a HTTPS Load Balancer will show all network traffic and its destination.",
+ "RationaleStatement": "Logging will allow you to view HTTPS network traffic to your web applications.",
+ "ImpactStatement": "On high use systems with a high percentage sample rate, the logging file may grow to high capacity in a short amount of time. Ensure that the sample rate is set appropriately so that storage costs are not exorbitant.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. From Google Cloud home open the Navigation Menu in the top left. 1. Under the `Networking` heading select `Network services`. 1. Select the HTTPS load-balancer you wish to audit. 1. Select `Edit` then `Backend Configuration`. 1. Select `Edit` on the corresponding backend service. 1. Click `Enable Logging`. 1. Set `Sample Rate` to a desired value. This is a percentage as a decimal point. 1.0 is 100%. **From Google Cloud CLI** 1. Run the following command gcloud compute backend-services update <serviceName> --region=REGION --enable-logging --logging-sample-rate=<percentageAsADecimal> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. From Google Cloud home open the Navigation Menu in the top left. 1. Under the `Networking` heading select `Network services`. 1. Select the HTTPS load-balancer you wish to audit. 1. Select `Edit` then `Backend Configuration`. 1. Select `Edit` on the corresponding backend service. 1. Ensure that `Enable Logging` is selected. Also ensure that `Sample Rate` is set to an appropriate level for your needs. **From Google Cloud CLI** 1. Run the following command gcloud compute backend-services describe <serviceName> 1. Ensure that enable-logging is enabled and sample rate is set to your desired level.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/load-balancing/:https://cloud.google.com/load-balancing/docs/https/https-logging-monitoring#gcloud:-global-mode:https://cloud.google.com/sdk/gcloud/reference/compute/backend-services/",
+ "DefaultValue": "By default logging for https load balancing is disabled. When logging is enabled it sets the default sample rate as 1.0 or 100%. Ensure this value fits the need of your organization to avoid high storage costs.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.1",
+ "Description": "Ensure That the Default Network Does Not Exist in a Project",
+ "Checks": [
+ "compute_network_default_in_use"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "To prevent use of `default` network, a project should not have a `default` network.",
+ "RationaleStatement": "The `default` network has a preconfigured network configuration and automatically generates the following insecure firewall rules: - default-allow-internal: Allows ingress connections for all protocols and ports among instances in the network. - default-allow-ssh: Allows ingress connections on TCP port 22(SSH) from any source to any instance in the network. - default-allow-rdp: Allows ingress connections on TCP port 3389(RDP) from any source to any instance in the network. - default-allow-icmp: Allows ingress ICMP traffic from any source to any instance in the network. These automatically created firewall rules do not get audit logged by default. Furthermore, the default network is an auto mode network, which means that its subnets use the same predefined range of IP addresses, and as a result, it's not possible to use Cloud VPN or VPC Network Peering with the default network. Based on organization security and networking requirements, the organization should create a new network and delete the `default` network.",
+ "ImpactStatement": "When an organization deletes the default network, it will need to remove all asests from that network and migrate them to a new network.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the `VPC networks` page by visiting: [https://console.cloud.google.com/networking/networks/list](https://console.cloud.google.com/networking/networks/list). 2. Click the network named `default`. 2. On the network detail page, click `EDIT`. 3. Click `DELETE VPC NETWORK`. 4. If needed, create a new network to replace the default network. **From Google Cloud CLI** For each Google Cloud Platform project, 1. Delete the default network: gcloud compute networks delete default 2. If needed, create a new network to replace it: gcloud compute networks create NETWORK_NAME **Prevention:** The user can prevent the default network and its insecure default firewall rules from being created by setting up an Organization Policy to `Skip default network creation` at [https://console.cloud.google.com/iam-admin/orgpolicies/compute-skipDefaultNetworkCreation](https://console.cloud.google.com/iam-admin/orgpolicies/compute-skipDefaultNetworkCreation).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VPC networks` page by visiting: [https://console.cloud.google.com/networking/networks/list](https://console.cloud.google.com/networking/networks/list). 2. Ensure that a network with the name `default` is not present. **From Google Cloud CLI** 1. Set the project name in the Google Cloud Shell: gcloud config set project PROJECT_ID 2. List the networks configured in that project: gcloud compute networks list It should not list `default` as one of the available networks in that project.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/compute/docs/networking#firewall_rules:https://cloud.google.com/compute/docs/reference/latest/networks/insert:https://cloud.google.com/compute/docs/reference/latest/networks/delete:https://cloud.google.com/vpc/docs/firewall-rules-logging:https://cloud.google.com/vpc/docs/vpc#default-network:https://cloud.google.com/sdk/gcloud/reference/compute/networks/delete",
+ "DefaultValue": "By default, for each project, a `default` network is created.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.2",
+ "Description": "Ensure Legacy Networks Do Not Exist for Older Projects",
+ "Checks": [
+ "compute_network_not_legacy"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In order to prevent use of legacy networks, a project should not have a legacy network configured. As of now, Legacy Networks are gradually being phased out, and you can no longer create projects with them. This recommendation is to check older projects to ensure that they are not using Legacy Networks.",
+ "RationaleStatement": "Legacy networks have a single network IPv4 prefix range and a single gateway IP address for the whole network. The network is global in scope and spans all cloud regions. Subnetworks cannot be created in a legacy network and are unable to switch from legacy to auto or custom subnet networks. Legacy networks can have an impact for high network traffic projects and are subject to a single point of contention or failure.",
+ "ImpactStatement": "None.",
+ "RemediationProcedure": "**From Google Cloud CLI** For each Google Cloud Platform project, 1. Follow the documentation and create a non-legacy network suitable for the organization's requirements. 2. Follow the documentation and delete the networks in the `legacy` mode.",
+ "AuditProcedure": "**From Google Cloud CLI** For each Google Cloud Platform project, 1. Set the project name in the Google Cloud Shell: gcloud config set project <Project-ID> 2. List the networks configured in that project: gcloud compute networks list None of the listed networks should be in the `legacy` mode.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/vpc/docs/using-legacy#creating_a_legacy_network:https://cloud.google.com/vpc/docs/using-legacy#deleting_a_legacy_network",
+ "DefaultValue": "By default, networks are not created in the `legacy` mode.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.3",
+ "Description": "Ensure That DNSSEC Is Enabled for Cloud DNS",
+ "Checks": [
+ "dns_dnssec_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Cloud Domain Name System (DNS) is a fast, reliable and cost-effective domain name system that powers millions of domains on the internet. Domain Name System Security Extensions (DNSSEC) in Cloud DNS enables domain owners to take easy steps to protect their domains against DNS hijacking and man-in-the-middle and other attacks.",
+ "RationaleStatement": "Domain Name System Security Extensions (DNSSEC) adds security to the DNS protocol by enabling DNS responses to be validated. Having a trustworthy DNS that translates a domain name like www.example.com into its associated IP address is an increasingly important building block of today’s web-based applications. Attackers can hijack this process of domain/IP lookup and redirect users to a malicious site through DNS hijacking and man-in-the-middle attacks. DNSSEC helps mitigate the risk of such attacks by cryptographically signing DNS records. As a result, it prevents attackers from issuing fake DNS responses that may misdirect browsers to nefarious websites.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Cloud DNS` by visiting [https://console.cloud.google.com/net-services/dns/zones](https://console.cloud.google.com/net-services/dns/zones). 2. For each zone of `Type` `Public`, set `DNSSEC` to `On`. **From Google Cloud CLI** Use the below command to enable `DNSSEC` for Cloud DNS Zone Name. gcloud dns managed-zones update ZONE_NAME --dnssec-state on ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Cloud DNS` by visiting [https://console.cloud.google.com/net-services/dns/zones](https://console.cloud.google.com/net-services/dns/zones). 2. For each zone of `Type` `Public`, ensure that `DNSSEC` is set to `On`. **From Google Cloud CLI** 1. List all the Managed Zones in a project: gcloud dns managed-zones list 2. For each zone of `VISIBILITY` `public`, get its metadata: gcloud dns managed-zones describe ZONE_NAME 3. Ensure that `dnssecConfig.state` property is `on`.",
+ "AdditionalInformation": "",
+ "References": "https://cloudplatform.googleblog.com/2017/11/DNSSEC-now-available-in-Cloud-DNS.html:https://cloud.google.com/dns/dnssec-config#enabling:https://cloud.google.com/dns/dnssec",
+ "DefaultValue": "By default DNSSEC is not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.4",
+ "Description": "Ensure That RSASHA1 Is Not Used for the Key-Signing Key in Cloud DNS DNSSEC",
+ "Checks": [
+ "dns_rsasha1_in_use_to_key_sign_in_dnssec"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "NOTE: Currently, the SHA1 algorithm has been removed from general use by Google, and, if being used, needs to be whitelisted on a project basis by Google and will also, therefore, require a Google Cloud support contract. DNSSEC algorithm numbers in this registry may be used in CERT RRs. Zone signing (DNSSEC) and transaction security mechanisms (SIG(0) and TSIG) make use of particular subsets of these algorithms. The algorithm used for key signing should be a recommended one and it should be strong.",
+ "RationaleStatement": "Domain Name System Security Extensions (DNSSEC) algorithm numbers in this registry may be used in CERT RRs. Zonesigning (DNSSEC) and transaction security mechanisms (SIG(0) and TSIG) make use of particular subsets of these algorithms. The algorithm used for key signing should be a recommended one and it should be strong. When enabling DNSSEC for a managed zone, or creating a managed zone with DNSSEC, the user can select the DNSSEC signing algorithms and the denial-of-existence type. Changing the DNSSEC settings is only effective for a managed zone if DNSSEC is not already enabled. If there is a need to change the settings for a managed zone where it has been enabled, turn DNSSEC off and then re-enable it with different settings.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud CLI** 1. If it is necessary to change the settings for a managed zone where it has been enabled, DNSSEC must be turned off and re-enabled with different settings. To turn off DNSSEC, run the following command: gcloud dns managed-zones update ZONE_NAME --dnssec-state off 2. To update key-signing for a reported managed DNS Zone, run the following command: gcloud dns managed-zones update ZONE_NAME --dnssec-state on --ksk-algorithm KSK_ALGORITHM --ksk-key-length KSK_KEY_LENGTH --zsk-algorithm ZSK_ALGORITHM --zsk-key-length ZSK_KEY_LENGTH --denial-of-existence DENIAL_OF_EXISTENCE Supported algorithm options and key lengths are as follows. Algorithm KSK Length ZSK Length --------- ---------- ---------- RSASHA1 1024,2048 1024,2048 RSASHA256 1024,2048 1024,2048 RSASHA512 1024,2048 1024,2048 ECDSAP256SHA256 256 256 ECDSAP384SHA384 384 384",
+ "AuditProcedure": "**From Google Cloud CLI** Ensure the property algorithm for keyType keySigning is not using `RSASHA1`. gcloud dns managed-zones describe ZONENAME --format=json(dnsName,dnssecConfig.state,dnssecConfig.defaultKeySpecs)",
+ "AdditionalInformation": "1. RSASHA1 key-signing support may be required for compatibility reasons. 2. Remediation CLI works well with gcloud-cli version 221.0.0 and later.",
+ "References": "https://cloud.google.com/dns/dnssec-advanced#advanced_signing_options",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.5",
+ "Description": "Ensure That RSASHA1 Is Not Used for the Zone-Signing Key in Cloud DNS DNSSEC",
+ "Checks": [
+ "dns_rsasha1_in_use_to_zone_sign_in_dnssec"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "NOTE: Currently, the SHA1 algorithm has been removed from general use by Google, and, if being used, needs to be whitelisted on a project basis by Google and will also, therefore, require a Google Cloud support contract. DNSSEC algorithm numbers in this registry may be used in CERT RRs. Zone signing (DNSSEC) and transaction security mechanisms (SIG(0) and TSIG) make use of particular subsets of these algorithms. The algorithm used for key signing should be a recommended one and it should be strong.",
+ "RationaleStatement": "DNSSEC algorithm numbers in this registry may be used in CERT RRs. Zone signing (DNSSEC) and transaction security mechanisms (SIG(0) and TSIG) make use of particular subsets of these algorithms. The algorithm used for key signing should be a recommended one and it should be strong. When enabling DNSSEC for a managed zone, or creating a managed zone with DNSSEC, the DNSSEC signing algorithms and the denial-of-existence type can be selected. Changing the DNSSEC settings is only effective for a managed zone if DNSSEC is not already enabled. If the need exists to change the settings for a managed zone where it has been enabled, turn DNSSEC off and then re-enable it with different settings.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud CLI** 1. If the need exists to change the settings for a managed zone where it has been enabled, DNSSEC must be turned off and then re-enabled with different settings. To turn off DNSSEC, run following command: gcloud dns managed-zones update ZONE_NAME --dnssec-state off 2. To update zone-signing for a reported managed DNS Zone, run the following command: gcloud dns managed-zones update ZONE_NAME --dnssec-state on --ksk-algorithm KSK_ALGORITHM --ksk-key-length KSK_KEY_LENGTH --zsk-algorithm ZSK_ALGORITHM --zsk-key-length ZSK_KEY_LENGTH --denial-of-existence DENIAL_OF_EXISTENCE Supported algorithm options and key lengths are as follows. Algorithm KSK Length ZSK Length --------- ---------- ---------- RSASHA1 1024,2048 1024,2048 RSASHA256 1024,2048 1024,2048 RSASHA512 1024,2048 1024,2048 ECDSAP256SHA256 256 384 ECDSAP384SHA384 384 384",
+ "AuditProcedure": "**From Google Cloud CLI** Ensure the property algorithm for keyType zone signing is not using RSASHA1. gcloud dns managed-zones describe --format=json(dnsName,dnssecConfig.state,dnssecConfig.defaultKeySpecs) ",
+ "AdditionalInformation": "1. RSASHA1 zone-signing support may be required for compatibility reasons. 2. The remediation CLI works well with gcloud-cli version 221.0.0 and later.",
+ "References": "https://cloud.google.com/dns/dnssec-advanced#advanced_signing_options",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.6",
+ "Description": "Ensure That SSH Access Is Restricted From the Internet",
+ "Checks": [
+ "compute_firewall_ssh_access_from_the_internet_allowed"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "GCP `Firewall Rules` are specific to a `VPC Network`. Each rule either `allows` or `denies` traffic when its conditions are met. Its conditions allow the user to specify the type of traffic, such as ports and protocols, and the source or destination of the traffic, including IP addresses, subnets, and instances. Firewall rules are defined at the VPC network level and are specific to the network in which they are defined. The rules themselves cannot be shared among networks. Firewall rules only support IPv4 traffic. When specifying a source for an ingress rule or a destination for an egress rule by address, only an `IPv4` address or `IPv4 block in CIDR` notation can be used. Generic `(0.0.0.0/0)` incoming traffic from the internet to VPC or VM instance using `SSH` on `Port 22` can be avoided.",
+ "RationaleStatement": "GCP `Firewall Rules` within a `VPC Network` apply to outgoing (egress) traffic from instances and incoming (ingress) traffic to instances in the network. Egress and ingress traffic flows are controlled even if the traffic stays within the network (for example, instance-to-instance communication). For an instance to have outgoing Internet access, the network must have a valid Internet gateway route or custom route whose destination IP is specified. This route simply defines the path to the Internet, to avoid the most general `(0.0.0.0/0)` destination `IP Range` specified from the Internet through `SSH` with the default `Port 22`. Generic access from the Internet to a specific IP Range needs to be restricted.",
+ "ImpactStatement": "All Secure Shell (SSH) connections from outside of the network to the concerned VPC(s) will be blocked. There could be a business need where SSH access is required from outside of the network to access resources associated with the VPC. In that case, specific source IP(s) should be mentioned in firewall rules to white-list access to SSH port for the concerned VPC(s).",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `VPC Network`. 2. Go to the `Firewall Rules`. 3. Click the `Firewall Rule` you want to modify. 4. Click `Edit`. 5. Modify `Source IP ranges` to specific `IP`. 6. Click `Save`. **From Google Cloud CLI** 1.Update the Firewall rule with the new `SOURCE_RANGE` from the below command: gcloud compute firewall-rules update FirewallName --allow=[PROTOCOL[:PORT[-PORT]],...] --source-ranges=[CIDR_RANGE,...]",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `VPC network`. 2. Go to the `Firewall Rules`. 3. Ensure that `Port` is not equal to `22` and `Action` is not set to `Allow`. 4. Ensure `IP Ranges` is not equal to `0.0.0.0/0` under `Source filters`. **From Google Cloud CLI** gcloud compute firewall-rules list --format=table'(name,direction,sourceRanges,allowed)' Ensure that there is no rule matching the below criteria: - `SOURCE_RANGES` is `0.0.0.0/0` - AND `DIRECTION` is `INGRESS` - AND IPProtocol is `tcp` or `ALL` - AND `PORTS` is set to `22` or `range containing 22` or `Null (not set)` Note: - When ALL TCP ports are allowed in a rule, PORT does not have any value set (`NULL`) - When ALL Protocols are allowed in a rule, PORT does not have any value set (`NULL`)",
+ "AdditionalInformation": "Currently, GCP VPC only supports IPV4; however, Google is already working on adding IPV6 support for VPC. In that case along with source IP range `0.0.0.0`, the rule should be checked for IPv6 equivalent `::/0` as well.",
+ "References": "https://cloud.google.com/vpc/docs/firewalls#blockedtraffic:https://cloud.google.com/blog/products/identity-security/cloud-iap-enables-context-aware-access-to-vms-via-ssh-and-rdp-without-bastion-hosts",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.7",
+ "Description": "Ensure That RDP Access Is Restricted From the Internet",
+ "Checks": [
+ "compute_firewall_rdp_access_from_the_internet_allowed"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "GCP `Firewall Rules` are specific to a `VPC Network`. Each rule either `allows` or `denies` traffic when its conditions are met. Its conditions allow users to specify the type of traffic, such as ports and protocols, and the source or destination of the traffic, including IP addresses, subnets, and instances. Firewall rules are defined at the VPC network level and are specific to the network in which they are defined. The rules themselves cannot be shared among networks. Firewall rules only support IPv4 traffic. When specifying a source for an ingress rule or a destination for an egress rule by address, an `IPv4` address or `IPv4 block in CIDR` notation can be used. Generic `(0.0.0.0/0)` incoming traffic from the Internet to a VPC or VM instance using `RDP` on `Port 3389` can be avoided.",
+ "RationaleStatement": "GCP `Firewall Rules` within a `VPC Network`. These rules apply to outgoing (egress) traffic from instances and incoming (ingress) traffic to instances in the network. Egress and ingress traffic flows are controlled even if the traffic stays within the network (for example, instance-to-instance communication). For an instance to have outgoing Internet access, the network must have a valid Internet gateway route or custom route whose destination IP is specified. This route simply defines the path to the Internet, to avoid the most general `(0.0.0.0/0)` destination `IP Range` specified from the Internet through `RDP` with the default `Port 3389`. Generic access from the Internet to a specific IP Range should be restricted.",
+ "ImpactStatement": "All Remote Desktop Protocol (RDP) connections from outside of the network to the concerned VPC(s) will be blocked. There could be a business need where secure shell access is required from outside of the network to access resources associated with the VPC. In that case, specific source IP(s) should be mentioned in firewall rules to white-list access to RDP port for the concerned VPC(s).",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `VPC Network`. 2. Go to the `Firewall Rules`. 3. Click the `Firewall Rule` to be modified. 4. Click `Edit`. 5. Modify `Source IP ranges` to specific `IP`. 6. Click `Save`. **From Google Cloud CLI** 1.Update RDP Firewall rule with new `SOURCE_RANGE` from the below command: gcloud compute firewall-rules update FirewallName --allow=[PROTOCOL[:PORT[-PORT]],...] --source-ranges=[CIDR_RANGE,...]",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `VPC network`. 2. Go to the `Firewall Rules`. 3. Ensure `Port` is not equal to `3389` and `Action` is not `Allow`. 4. Ensure `IP Ranges` is not equal to `0.0.0.0/0` under `Source filters`. **From Google Cloud CLI** gcloud compute firewall-rules list --format=table'(name,direction,sourceRanges,allowed)' Ensure that there is no rule matching the below criteria: - `SOURCE_RANGES` is `0.0.0.0/0` - AND `DIRECTION` is `INGRESS` - AND IPProtocol is `TCP` or `ALL` - AND `PORTS` is set to `3389` or `range containing 3389` or `Null (not set)` Note: - When ALL TCP ports are allowed in a rule, PORT does not have any value set (`NULL`) - When ALL Protocols are allowed in a rule, PORT does not have any value set (`NULL`)",
+ "AdditionalInformation": "Currently, GCP VPC only supports IPV4; however, Google is already working on adding IPV6 support for VPC. In that case along with source IP range `0.0.0.0`, the rule should be checked for IPv6 equivalent `::/0` as well.",
+ "References": "https://cloud.google.com/vpc/docs/firewalls#blockedtraffic:https://cloud.google.com/blog/products/identity-security/cloud-iap-enables-context-aware-access-to-vms-via-ssh-and-rdp-without-bastion-hosts",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.8",
+ "Description": "Ensure VPC Service Controls Is Enabled for Supported Google Cloud Services",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that VPC Service Controls are configured to create security perimeters around sensitive Google Cloud resources, preventing unauthorized data exfiltration and limiting access to resources from approved networks and identities. VPC Service Controls provide an additional layer of defense-in-depth by allowing organizations to define trust boundaries around GCP services and control data movement across those boundaries.",
+ "RationaleStatement": "VPC Service Controls provide critical protection against data exfiltration attacks by creating security perimeters that restrict data access based on client identity, device state, and network origin. Without VPC Service Controls, an attacker who compromises credentials or exploits misconfigurations can freely move data between projects, organizations, or external systems. VPC Service Controls enforce defense-in-depth by adding network-level access controls that complement IAM policies. This control is essential for organizations handling regulated data or implementing zero-trust security architectures, and it also protects against supply chain attacks by restricting which services and APIs can interact with protected resources.",
+ "ImpactStatement": "Implementing VPC Service Controls requires careful planning as it restricts network access to protected resources. Services outside the perimeter will be denied access to resources inside the perimeter by default, which may impact application connectivity, cross-project data pipelines, third-party integrations, and administrative access from non-corporate networks. Organizations should use VPC Service Controls dry-run mode to test policies before enforcement. There is no direct performance impact on services within the perimeter.",
+ "AuditProcedure": "Note: The following audit instructions use Cloud Storage (GCS) as an example. Similar steps should be followed for other supported services (BigQuery, Cloud SQL, Bigtable, etc.).\n\n**From Google Cloud CLI**\n\n1. Check if the Access Context Manager API is enabled:\n`gcloud services list --enabled --filter=\"name:accesscontextmanager.googleapis.com\" --format=\"value(name)\"`\n2. List Access Context Manager policies and perimeters in the organization:\n`gcloud access-context-manager policies list --organization=<ORG_ID>`\n`gcloud access-context-manager perimeters list --policy=<POLICY_ID>`\n3. Check if a project's resources are protected by a perimeter and verify perimeter configuration with `gcloud access-context-manager perimeters describe <PERIMETER_NAME> --policy=<POLICY_ID>`.\n4. Check whether perimeters have access levels configured for conditional access.",
+ "RemediationProcedure": "Note: The following remediation instructions use Cloud Storage (GCS) as an example. Similar steps should be followed for other supported services.\n\n**From Google Cloud CLI**\n\n1. Create an Access Context Manager policy if none exists: `gcloud access-context-manager policies create --organization=<ORG_ID> --title=\"VPC Service Controls Policy\"`.\n2. Create a service perimeter to protect resources: `gcloud access-context-manager perimeters create <PERIMETER_NAME> --resources=projects/<PROJECT_NUMBER> --restricted-services=storage.googleapis.com --policy=<POLICY_ID> --perimeter-type=regular`.\n3. Add additional projects and restricted services to the perimeter as needed.\n4. Test with dry-run mode before enforcement and monitor dry-run logs for blocked requests, then enforce the perimeter with `gcloud access-context-manager perimeters dry-run enforce`.\n5. Optionally create access levels for conditional access and add them to the perimeter.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, VPC Service Controls are not configured and no service perimeters protect Google Cloud resources."
+ }
+ ]
+ },
+ {
+ "Id": "3.9",
+ "Description": "Ensure Private Service Connect is Used for Access to Google APIs",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that VPCs use Private Service Connect endpoints for access to Google APIs such as Cloud Storage, BigQuery, Pub/Sub, Artifact Registry, and other googleapis.com services, so that traffic from workloads to these APIs stays on the Google private network instead of traversing the public internet. Private Service Connect for Google APIs creates a dedicated endpoint in your VPC with firewall rule enforcement, providing more granular control than Private Google Access.",
+ "RationaleStatement": "Accessing Google APIs over the public internet exposes traffic to network-level threats, requires managing NAT gateways or external IPs, and makes it harder to enforce egress controls. Private Service Connect for Google APIs allows workloads to reach googleapis.com services over Google's private network using a dedicated endpoint in your VPC. Combined with VPC firewall rules, PSC ensures only authorized workloads can access Google APIs, preventing unauthorized API usage and enforcing least-privilege network access. This control eliminates reliance on internet connectivity for API access, enables granular network segmentation per API consumer, supports VPC Service Controls integration, and is essential for zero-trust architectures.",
+ "ImpactStatement": "Implementing Private Service Connect for Google APIs requires creating PSC endpoints in each VPC and configuring DNS to resolve googleapis.com domains to the private endpoint IP addresses. This introduces per-endpoint charges and operational overhead for DNS management. Migrating from public API access requires updating DNS configurations and may require changes to firewall rules. Workloads without proper firewall rules or DNS configuration will be unable to reach Google APIs after migration.",
+ "AuditProcedure": "**From Google Cloud CLI**\n\n1. Identify in-scope VPCs that host production or sensitive workloads accessing Google APIs: `gcloud compute networks list --format=\"table(name)\"`.\n2. For each in-scope VPC, check for a Private Service Connect endpoint for Google APIs: `gcloud compute addresses list --filter=\"purpose=PRIVATE_SERVICE_CONNECT\"`. At least one PSC endpoint should exist per VPC that needs Google API access.\n3. Verify the PSC endpoint targets Google's service attachment by listing global forwarding rules and looking for targets containing `all-apis` or `vpc-sc`.\n4. Check Cloud DNS for a private zone for googleapis.com with a wildcard A record pointing to the PSC endpoint IP.\n5. Verify firewall rules restrict access to the PSC endpoint using specific sourceRanges/sourceTags and do not allow 0.0.0.0/0.",
+ "RemediationProcedure": "**From Google Cloud CLI**\n\n1. Reserve an internal IP for the PSC endpoint: `gcloud compute addresses create psc-apis-endpoint --global --purpose=PRIVATE_SERVICE_CONNECT --addresses=<RFC1918_IP> --network=projects/<PROJECT_ID>/global/networks/<VPC_NAME>`.\n2. Create the PSC endpoint forwarding rule targeting Google's all-apis bundle: `gcloud compute forwarding-rules create pscapis --global --network=<VPC_NAME> --address=psc-apis-endpoint --target-google-apis-bundle=all-apis`.\n3. Configure DNS by creating a private zone for googleapis.com and a wildcard A record pointing to the PSC endpoint IP.\n4. Configure VPC firewall rules to restrict PSC endpoint access to specific subnets only.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, workloads access Google APIs over public Google API endpoints rather than through Private Service Connect endpoints."
+ }
+ ]
+ },
+ {
+ "Id": "3.10",
+ "Description": "Ensure that VPC Flow Logs is Enabled for Every Subnet in a VPC Network",
+ "Checks": [
+ "compute_subnet_flow_logs_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Flow Logs is a feature that enables users to capture information about the IP traffic going to and from network interfaces in the organization's VPC Subnets. Once a flow log is created, the user can view and retrieve its data in Stackdriver Logging. It is recommended that Flow Logs be enabled for every business-critical VPC subnet.",
+ "RationaleStatement": "VPC networks and subnetworks not reserved for internal HTTP(S) load balancing provide logically isolated and secure network partitions where GCP resources can be launched. When Flow Logs are enabled for a subnet, VMs within that subnet start reporting on all Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) flows. Each VM samples the TCP and UDP flows it sees, inbound and outbound, whether the flow is to or from another VM, a host in the on-premises datacenter, a Google service, or a host on the Internet. If two GCP VMs are communicating, and both are in subnets that have VPC Flow Logs enabled, both VMs report the flows. Flow Logs supports the following use cases: - Network monitoring - Understanding network usage and optimizing network traffic expenses - Network forensics - Real-time security analysis Flow Logs provide visibility into network traffic for each VM inside the subnet and can be used to detect anomalous traffic or provide insight during security workflows. The Flow Logs must be configured such that all network traffic is logged, the interval of logging is granular to provide detailed information on the connections, no logs are filtered, and metadata to facilitate investigations are included. **Note**: Subnets reserved for use by internal HTTP(S) load balancers do not support VPC flow logs.",
+ "ImpactStatement": "Standard pricing for Stackdriver Logging, BigQuery, or Cloud Pub/Sub applies. VPC Flow Logs generation will be charged starting in GA as described in reference: https://cloud.google.com/vpc/",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the VPC network GCP Console visiting `https://console.cloud.google.com/networking/networks/list` 2. Click the name of a subnet, The `Subnet details` page displays. 3. Click the `EDIT` button. 4. Set `Flow Logs` to `On`. 5. Expand the `Configure Logs` section. 6. Set `Aggregation Interval` to `5 SEC`. 7. Check the box beside `Include metadata`. 8. Set `Sample rate` to `100`. 9. Click Save. **Note**: It is not possible to configure a Log filter from the console. **From Google Cloud CLI** To enable VPC Flow Logs for a network subnet, run the following command: gcloud compute networks subnets update [SUBNET_NAME] --region [REGION] --enable-flow-logs --logging-aggregation-interval=interval-5-sec --logging-flow-sampling=1 --logging-metadata=include-all ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the VPC network GCP Console visiting `https://console.cloud.google.com/networking/networks/list` 2. From the list of network subnets, make sure for each subnet: - `Flow Logs` is set to `On` - `Aggregation Interval` is set to `5 sec` - `Include metadata` checkbox is checked - `Sample rate` is set to `100%` **Note**: It is not possible to determine if a Log filter has been defined from the console. **From Google Cloud CLI** gcloud compute networks subnets list --format json | jq -r '([Subnet,Purpose,Flow_Logs,Aggregation_Interval,Flow_Sampling,Metadata,Logs_Filtered] | (., map(length*-))), (.[] | [ .name, .purpose, (if has(enableFlowLogs) and .enableFlowLogs == true then Enabled else Disabled end), (if has(logConfig) then .logConfig.aggregationInterval else N/A end), (if has(logConfig) then .logConfig.flowSampling else N/A end), (if has(logConfig) then .logConfig.metadata else N/A end), (if has(logConfig) then (.logConfig | has(filterExpr)) else N/A end) ] ) | @tsv' | column -t The output of the above command will list: - each subnet - the subnet's purpose - a `Enabled` or `Disabled` value if `Flow Logs` are enabled - the value for `Aggregation Interval` or `N/A` if disabled, the value for `Flow Sampling` or `N/A` if disabled - the value for `Metadata` or `N/A` if disabled - 'true' or 'false' if a Logging Filter is configured or 'N/A' if disabled. If the subnet's purpose is `PRIVATE` then `Flow Logs` should be `Enabled`. If `Flow Logs` is enabled then: - `Aggregation_Interval` should be `INTERVAL_5_SEC` - `Flow_Sampling` should be 1 - `Metadata` should be `INCLUDE_ALL_METADATA` - `Logs_Filtered` should be `false`.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/vpc/docs/using-flow-logs#enabling_vpc_flow_logging:https://cloud.google.com/vpc/",
+ "DefaultValue": "By default, Flow Logs is set to Off when a new VPC network subnet is created.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.11",
+ "Description": "Ensure No HTTPS or SSL Proxy Load Balancers Permit SSL Policies With Weak Cipher Suites",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Secure Sockets Layer (SSL) policies determine what port Transport Layer Security (TLS) features clients are permitted to use when connecting to load balancers. To prevent usage of insecure features, SSL policies should use (a) at least TLS 1.2 with the MODERN profile; or (b) the RESTRICTED profile, because it effectively requires clients to use TLS 1.2 regardless of the chosen minimum TLS version; or (3) a CUSTOM profile that does not support any of the following features: TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA ",
+ "RationaleStatement": "Load balancers are used to efficiently distribute traffic across multiple servers. Both SSL proxy and HTTPS load balancers are external load balancers, meaning they distribute traffic from the Internet to a GCP network. GCP customers can configure load balancer SSL policies with a minimum TLS version (1.0, 1.1, or 1.2) that clients can use to establish a connection, along with a profile (Compatible, Modern, Restricted, or Custom) that specifies permissible cipher suites. To comply with users using outdated protocols, GCP load balancers can be configured to permit insecure cipher suites. In fact, the GCP default SSL policy uses a minimum TLS version of 1.0 and a Compatible profile, which allows the widest range of insecure cipher suites. As a result, it is easy for customers to configure a load balancer without even knowing that they are permitting outdated cipher suites.",
+ "ImpactStatement": "Creating more secure SSL policies can prevent clients using older TLS versions from establishing a connection.",
+ "RemediationProcedure": "**From Google Cloud Console** If the TargetSSLProxy or TargetHttpsProxy does not have an SSL policy configured, create a new SSL policy. Otherwise, modify the existing insecure policy. 1. Navigate to the `SSL Policies` page by visiting: [https://console.cloud.google.com/net-security/sslpolicies](https://console.cloud.google.com/net-security/sslpolicies) 2. Click on the name of the insecure policy to go to its `SSL policy details` page. 3. Click `EDIT`. 4. Set `Minimum TLS version` to `TLS 1.2`. 5. Set `Profile` to `Modern` or `Restricted`. 6. Alternatively, if teh user selects the profile `Custom`, make sure that the following features are disabled: TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA **From Google Cloud CLI** 1. For each insecure SSL policy, update it to use secure cyphers: gcloud compute ssl-policies update NAME [--profile COMPATIBLE|MODERN|RESTRICTED|CUSTOM] --min-tls-version 1.2 [--custom-features FEATURES] 2. If the target proxy has a GCP default SSL policy, use the following command corresponding to the proxy type to update it. gcloud compute target-ssl-proxies update TARGET_SSL_PROXY_NAME --ssl-policy SSL_POLICY_NAME gcloud compute target-https-proxies update TARGET_HTTPS_POLICY_NAME --ssl-policy SSL_POLICY_NAME ",
+ "AuditProcedure": "**From Google Cloud Console** 1. See all load balancers by visiting [https://console.cloud.google.com/net-services/loadbalancing/loadBalancers/list](https://console.cloud.google.com/net-services/loadbalancing/loadBalancers/list). 2. For each load balancer for `SSL (Proxy)` or `HTTPS`, click on its name to go the `Load balancer details` page. 3. Ensure that each target proxy entry in the `Frontend` table has an `SSL Policy` configured. 4. Click on each SSL policy to go to its `SSL policy details` page. 5. Ensure that the SSL policy satisfies one of the following conditions: - has a `Min TLS` set to `TLS 1.2` and `Profile` set to `Modern` profile, or - has `Profile` set to `Restricted`. Note that a Restricted profile effectively requires clients to use TLS 1.2 regardless of the chosen minimum TLS version, or - has `Profile` set to `Custom` and the following features are all disabled: TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA **From Google Cloud CLI** 1. List all TargetHttpsProxies and TargetSslProxies. gcloud compute target-https-proxies list gcloud compute target-ssl-proxies list 2. For each target proxy, list its properties: gcloud compute target-https-proxies describe TARGET_HTTPS_PROXY_NAME gcloud compute target-ssl-proxies describe TARGET_SSL_PROXY_NAME 3. Ensure that the `sslPolicy` field is present and identifies the name of the SSL policy: sslPolicy: https://www.googleapis.com/compute/v1/projects/PROJECT_ID/global/sslPolicies/SSL_POLICY_NAME If the `sslPolicy` field is missing from the configuration, it means that the GCP default policy is used, which is insecure. 4. Describe the SSL policy: gcloud compute ssl-policies describe SSL_POLICY_NAME 5. Ensure that the policy satisfies one of the following conditions: - has `Profile` set to `Modern` and `minTlsVersion` set to `TLS_1_2`, or - has `Profile` set to `Restricted`, or - has `Profile` set to `Custom` and `enabledFeatures` does not contain any of the following values: TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/load-balancing/docs/use-ssl-policies:https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r2.pdf",
+ "DefaultValue": "The GCP default SSL policy is the least secure setting: Min TLS 1.0 and Compatible profile",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "3.12",
+ "Description": "Use Identity Aware Proxy (IAP) to Ensure Only Traffic From Google IP Addresses are 'Allowed'",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Networking",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "IAP authenticates the user requests to your apps via a Google single sign in. You can then manage these users with permissions to control access. It is recommended to use both IAP permissions and firewalls to restrict this access to your apps with sensitive information.",
+ "RationaleStatement": "IAP ensure that access to VMs is controlled by authenticating incoming requests. Access to your apps and the VMs should be restricted by firewall rules that allow only the proxy IAP IP addresses contained in the 35.235.240.0/20 subnet. Otherwise, unauthenticated requests can be made to your apps. To ensure that load balancing works correctly health checks should also be allowed.",
+ "ImpactStatement": "If firewall rules are not configured correctly, legitimate business services could be negatively impacted. It is recommended to make these changes during a time of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud Console [VPC network > Firewall rules](https://console.cloud.google.com/networking/firewalls/list?_ga=2.72166934.480049361.1580860862-1336643914.1580248695). 2. Select the checkbox next to the following rules: - default-allow-http - default-allow-https - default-allow-internal 3. Click `Delete`. 4. Click `Create firewall rule` and set the following values: - Name: allow-iap-traffic - Targets: All instances in the network - Source IP ranges (press Enter after you paste each value in the box, copy each full CIDR IP address): - IAP Proxy Addresses `35.235.240.0/20` - Google Health Check `130.211.0.0/22` - Google Health Check `35.191.0.0/16` - Protocols and ports: - Specified protocols and ports required for access and management of your app. For example most health check connection protocols would be covered by; - tcp:80 (Default HTTP Health Check port) - tcp:443 (Default HTTPS Health Check port) **Note: if you have custom ports used by your load balancers, you will need to list them here** 5. When you're finished updating values, click `Create`.",
+ "AuditProcedure": "**From Google Cloud Console** 1. For each of your apps that have IAP enabled go to the Cloud Console VPC network > Firewall rules. 2. Verify that the only rules correspond to the following values: - Targets: All instances in the network - Source IP ranges: - IAP Proxy Addresses `35.235.240.0/20` - Google Health Check `130.211.0.0/22` - Google Health Check `35.191.0.0/16` - Protocols and ports: - Specified protocols and ports required for access and management of your app. For example most health check connection protocols would be covered by; - tcp:80 (Default HTTP Health Check port) - tcp:443 (Default HTTPS Health Check port) **Note: if you have custom ports used by your load balancers, you will need to list them here**",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/iap/docs/concepts-overview:https://cloud.google.com/iap/docs/load-balancer-howto:https://cloud.google.com/load-balancing/docs/health-checks:https://cloud.google.com/blog/products/identity-security/cloud-iap-enables-context-aware-access-to-vms-via-ssh-and-rdp-without-bastion-hosts",
+ "DefaultValue": "By default all traffic is allowed.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.1",
+ "Description": "Ensure That Instances Are Not Configured To Use the Default Service Account",
+ "Checks": [
+ "compute_instance_default_service_account_in_use"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to configure your instance to not use the default Compute Engine service account because it has the Editor role on the project.",
+ "RationaleStatement": "When a default Compute Engine service account is created, it is automatically granted the Editor role (roles/editor) on your project which allows read and write access to most Google Cloud Services. This role includes a very large number of permissions. To defend against privilege escalations if your VM is compromised and prevent an attacker from gaining access to all of your project, you should either revoke the Editor role from the default Compute Engine service account or create a new service account and assign only the permissions needed by your instance. To mitigate this at scale, we strongly recommend that you disable the automatic role grant by adding a constraint to your organization policy. The default Compute Engine service account is named `[PROJECT_NUMBER]-compute@developer.gserviceaccount.com`.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the instance name to go to its `VM instance details` page. 3. Click `STOP` and then click `EDIT`. 4. Under the section `API and identity management`, select a service account other than the default Compute Engine service account. You may first need to create a new service account. 5. Click `Save` and then click `START`. **From Google Cloud CLI** 1. Stop the instance: gcloud compute instances stop <INSTANCE_NAME> 2. Update the instance: gcloud compute instances set-service-account <INSTANCE_NAME> --service-account=<SERVICE_ACCOUNT> 3. Restart the instance: gcloud compute instances start <INSTANCE_NAME> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on each instance name to go to its `VM instance details` page. 3. Under the section `API and identity management`, ensure that the default Compute Engine service account is not used. This account is named `[PROJECT_NUMBER]-compute@developer.gserviceaccount.com`. **From Google Cloud CLI** 1. List the instances in your project and get details on each instance: gcloud compute instances list --format=json | jq -r '. | SA: (.[].serviceAccounts[].email) Name: (.[].name)' 2. Ensure that the service account section has an email that does not match the pattern `[PROJECT_NUMBER]-compute@developer.gserviceaccount.com`. **Exception:** VMs created by GKE should be excluded. These VMs have names that start with `gke-` and are labeled `goog-gke-node`.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/compute/docs/access/service-accounts:https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances:https://cloud.google.com/sdk/gcloud/reference/compute/instances/set-service-account",
+ "DefaultValue": "By default, Compute instances are configured to use the default Compute Engine service account.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.2",
+ "Description": "Ensure That Instances Are Not Configured To Use the Default Service Account With Full Access to All Cloud APIs",
+ "Checks": [
+ "compute_instance_default_service_account_in_use_with_full_api_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "To support principle of least privileges and prevent potential privilege escalation it is recommended that instances are not assigned to default service account `Compute Engine default service account` with Scope `Allow full access to all Cloud APIs`.",
+ "RationaleStatement": "Along with ability to optionally create, manage and use user managed custom service accounts, Google Compute Engine provides default service account `Compute Engine default service account` for an instances to access necessary cloud services. `Project Editor` role is assigned to `Compute Engine default service account` hence, This service account has almost all capabilities over all cloud services except billing. However, when `Compute Engine default service account` assigned to an instance it can operate in 3 scopes. 1. Allow default access: Allows only minimum access required to run an Instance (Least Privileges) 2. Allow full access to all Cloud APIs: Allow full access to all the cloud APIs/Services (Too much access) 3. Set access for each API: Allows Instance administrator to choose only those APIs that are needed to perform specific business functionality expected by instance When an instance is configured with `Compute Engine default service account` with Scope `Allow full access to all Cloud APIs`, based on IAM roles assigned to the user(s) accessing Instance, it may allow user to perform cloud operations/API calls that user is not supposed to perform leading to successful privilege escalation.",
+ "ImpactStatement": "In order to change service account or scope for an instance, it needs to be stopped.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the impacted VM instance. 3. If the instance is not stopped, click the `Stop` button. Wait for the instance to be stopped. 4. Next, click the `Edit` button. 5. Scroll down to the `Service Account` section. 6. Select a different service account or ensure that `Allow full access to all Cloud APIs` is not selected. 7. Click the `Save` button to save your changes and then click `START`. **From Google Cloud CLI** 1. Stop the instance: gcloud compute instances stop <INSTANCE_NAME> 2. Update the instance: gcloud compute instances set-service-account <INSTANCE_NAME> --service-account=<SERVICE_ACCOUNT> --scopes [SCOPE1, SCOPE2...] 3. Restart the instance: gcloud compute instances start <INSTANCE_NAME> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on each instance name to go to its `VM instance details` page. 3. Under the `API and identity management`, ensure that `Cloud API access scopes` is not set to `Allow full access to all Cloud APIs`. **From Google Cloud CLI** 1. List the instances in your project and get details on each instance: gcloud compute instances list --format=json | jq -r '. | SA Scopes: (.[].serviceAccounts[].scopes) Name: (.[].name) Email: (.[].serviceAccounts[].email)' 2. Ensure that the service account section has an email that does not match the pattern `[PROJECT_NUMBER]-compute@developer.gserviceaccount.com`. **Exception:** VMs created by GKE should be excluded. These VMs have names that start with `gke-` and are labeled `goog-gke-node",
+ "AdditionalInformation": "- User IAM roles will override service account scope but configuring minimal scope ensures defense in depth - Non-default service accounts do not offer selection of access scopes like default service account. IAM roles with non-default service accounts should be used to control VM access.",
+ "References": "https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances:https://cloud.google.com/compute/docs/access/service-accounts",
+ "DefaultValue": "While creating an VM instance, default service account is used with scope `Allow default access`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.3",
+ "Description": "Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances",
+ "Checks": [
+ "compute_instance_block_project_wide_ssh_keys_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to use Instance specific SSH key(s) instead of using common/shared project-wide SSH key(s) to access Instances.",
+ "RationaleStatement": "Project-wide SSH keys are stored in Compute/Project-meta-data. Project wide SSH keys can be used to login into all the instances within project. Using project-wide SSH keys eases the SSH key management but if compromised, poses the security risk which can impact all the instances within project. It is recommended to use Instance specific SSH keys which can limit the attack surface if the SSH keys are compromised.",
+ "ImpactStatement": "Users already having Project-wide ssh key pairs and using third party SSH clients will lose access to the impacted Instances. For Project users using gcloud or GCP Console based SSH option, no manual key creation and distribution is required and will be handled by GCE (Google Compute Engine) itself. To access Instance using third party SSH clients Instance specific SSH key pairs need to be created and distributed to the required users.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). It will list all the instances in your project. 2. Click on the name of the Impacted instance 3. Click `Edit` in the toolbar 4. Under SSH Keys, go to the `Block project-wide SSH keys` checkbox 5. To block users with project-wide SSH keys from connecting to this instance, select `Block project-wide SSH keys` 6. Click `Save` at the bottom of the page 7. Repeat steps for every impacted Instance **From Google Cloud CLI** To block project-wide public SSH keys, set the metadata value to `TRUE`: gcloud compute instances add-metadata <INSTANCE_NAME> --metadata block-project-ssh-keys=TRUE ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). It will list all the instances in your project. 2. For every instance, click on the name of the instance. 3. Under `SSH Keys`, ensure `Block project-wide SSH keys` is selected. **From Google Cloud CLI** 1. List the instances in your project and get details on each instance: gcloud compute instances list --format=json 2. Ensure `key: block-project-ssh-keys` is set to `value: 'true'`.",
+ "AdditionalInformation": "If OS Login is enabled, SSH keys in instance metadata are ignored, and therefore blocking project-wide SSH keys is not necessary.",
+ "References": "https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys:https://cloud.google.com/sdk/gcloud/reference/topic/formats",
+ "DefaultValue": "By Default `Block Project-wide SSH keys` is not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.4",
+ "Description": "Ensure Oslogin Is Enabled for a Project",
+ "Checks": [
+ "compute_project_os_login_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enabling OS login binds SSH certificates to IAM users and facilitates effective SSH certificate management.",
+ "RationaleStatement": "Enabling osLogin ensures that SSH keys used to connect to instances are mapped with IAM users. Revoking access to IAM user will revoke all the SSH keys associated with that particular user. It facilitates centralized and automated SSH key pair management which is useful in handling cases like response to compromised SSH key pairs and/or revocation of external/third-party/Vendor users.",
+ "ImpactStatement": "Enabling OS Login on project disables metadata-based SSH key configurations on all instances from a project. Disabling OS Login restores SSH keys that you have configured in project or instance meta-data.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the VM compute metadata page by visiting: [https://console.cloud.google.com/compute/metadata](https://console.cloud.google.com/compute/metadata). 2. Click `Edit`. 3. Add a metadata entry where the key is `enable-oslogin` and the value is `TRUE`. 4. Click `Save` to apply the changes. 5. For every instance that overrides the project setting, go to the `VM Instances` page at [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 6. Click the name of the instance on which you want to remove the metadata value. 7. At the top of the instance details page, click `Edit` to edit the instance settings. 8. Under `Custom metadata`, remove any entry with key `enable-oslogin` and the value is `FALSE` 9. At the bottom of the instance details page, click `Save` to apply your changes to the instance. **From Google Cloud CLI** 1. Configure oslogin on the project: gcloud compute project-info add-metadata --metadata enable-oslogin=TRUE 2. Remove instance metadata that overrides the project setting. gcloud compute instances remove-metadata <INSTANCE_NAME> --keys=enable-oslogin Optionally, you can enable two factor authentication for OS login. For more information, see: [https://cloud.google.com/compute/docs/oslogin/setup-two-factor-authentication](https://cloud.google.com/compute/docs/oslogin/setup-two-factor-authentication).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the VM compute metadata page by visiting [https://console.cloud.google.com/compute/metadata](https://console.cloud.google.com/compute/metadata). 2. Ensure that key `enable-oslogin` is present with value set to `TRUE`. 3. Because instances can override project settings, ensure that no instance has custom metadata with key `enable-oslogin` and value `FALSE`. **From Google Cloud CLI** 1. List the instances in your project and get details on each instance: gcloud compute instances list --format=json 2. Verify that the section `commonInstanceMetadata` has a key `enable-oslogin` set to value `TRUE`. **Exception:** VMs created by GKE should be excluded. These VMs have names that start with `gke-` and are labeled `goog-gke-node`",
+ "AdditionalInformation": "1. In order to use osLogin, instance using Custom Images must have the latest version of the Linux Guest Environment installed. The following image families do not yet support OS Login: Project cos-cloud (Container-Optimized OS) image family cos-stable. All project coreos-cloud (CoreOS) image families Project suse-cloud (SLES) image family sles-11 All Windows Server and SQL Server image families 2. Project enable-oslogin can be over-ridden by setting enable-oslogin parameter to an instance metadata individually.",
+ "References": "https://cloud.google.com/compute/docs/instances/managing-instance-access:https://cloud.google.com/compute/docs/instances/managing-instance-access#enable_oslogin:https://cloud.google.com/sdk/gcloud/reference/compute/instances/remove-metadata:https://cloud.google.com/compute/docs/oslogin/setup-two-factor-authentication",
+ "DefaultValue": "By default, parameter `enable-oslogin` is not set, which is equivalent to setting it to `FALSE`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.5",
+ "Description": "Ensure ‘Enable Connecting to Serial Ports’ Is Not Enabled for VM Instance",
+ "Checks": [
+ "compute_instance_serial_ports_in_use"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Interacting with a serial port is often referred to as the serial console, which is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address. Therefore interactive serial console support should be disabled.",
+ "RationaleStatement": "A virtual machine instance has four virtual serial ports. Interacting with a serial port is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support. The instance's operating system, BIOS, and other system-level entities often write output to the serial ports, and can accept input such as commands or answers to prompts. Typically, these system-level entities use the first serial port (port 1) and serial port 1 is often referred to as the serial console. The interactive serial console does not support IP-based access restrictions such as IP whitelists. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address. This allows anybody to connect to that instance if they know the correct SSH key, username, project ID, zone, and instance name. Therefore interactive serial console support should be disabled.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Login to Google Cloud console 2. Go to Computer Engine 3. Go to VM instances 4. Click on the Specific VM 5. Click `EDIT` 6. Unselect `Enable connecting to serial ports` below `Remote access` block. 7. Click `Save` **From Google Cloud CLI** Use the below command to disable gcloud compute instances add-metadata <INSTANCE_NAME> --zone=<ZONE> --metadata=serial-port-enable=false or gcloud compute instances add-metadata <INSTANCE_NAME> --zone=<ZONE> --metadata=serial-port-enable=0 **Prevention:** You can prevent VMs from having serial port access enable by `Disable VM serial port access` organization policy: [https://console.cloud.google.com/iam-admin/orgpolicies/compute-disableSerialPortAccess](https://console.cloud.google.com/iam-admin/orgpolicies/compute-disableSerialPortAccess).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Login to Google Cloud console 2. Go to Compute Engine 3. Go to VM instances 4. Click on the Specific VM 5. Ensure the statement `Connecting to serial serial ports is disabled` is displayed at the top of the details tab, just below the `Connect to serial console` drop-down.. **From Google Cloud CLI** Ensure the below command's output shows `null`: gcloud compute instances describe <vmName> --zone=<region> --format=json(metadata.items[].key,metadata.items[].value) or `key` and `value` properties from below command's json response are equal to `serial-port-enable` and `0` or `false` respectively. { metadata: { items: [ { key: serial-port-enable, value: 0 } ] } } ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/compute/docs/instances/interacting-with-serial-console",
+ "DefaultValue": "By default, connecting to serial ports is not enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.6",
+ "Description": "Ensure That IP Forwarding Is Not Enabled on Instances",
+ "Checks": [
+ "compute_instance_ip_forwarding_is_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Compute Engine instance cannot forward a packet unless the source IP address of the packet matches the IP address of the instance. Similarly, GCP won't deliver a packet whose destination IP address is different than the IP address of the instance receiving the packet. However, both capabilities are required if you want to use instances to help route packets. Forwarding of data packets should be disabled to prevent data loss or information disclosure.",
+ "RationaleStatement": "Compute Engine instance cannot forward a packet unless the source IP address of the packet matches the IP address of the instance. Similarly, GCP won't deliver a packet whose destination IP address is different than the IP address of the instance receiving the packet. However, both capabilities are required if you want to use instances to help route packets. To enable this source and destination IP check, disable the `canIpForward` field, which allows an instance to send and receive packets with non-matching destination or source IPs.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "You only edit the `canIpForward` setting at instance creation or using CLI. **From Google Cloud CLI** 1. Use the instances export command to export the existing instance properties: gcloud compute instances export <INSTANCE_NAME> --project <PROJECT_ID> --zone <ZONE> --destination=<FILE_PATH> **Note**Replace the following: INSTANCE_NAME the name for the instance that you want to export. PROJECT_ID: the project ID for this request. ZONE: the zone for this instance. FILE_PATH: the output path where you want to save the instance configuration file on your local workstation. 2. Use a text editor to modify this file Replace `canIpForward: true` with `canIpForward: false` 3. Run this command to import the file you just modified gcloud compute instances update-from-file INSTANCE_NAME --project PROJECT_ID --zone ZONE --source=FILE_PATH --most-disruptive-allowed-action=REFRESH If the update request is valid and the required resources are available, the instance update process begins. You can monitor the status of this operation by viewing the audit logs. This update requires only a REFRESH not a full restart.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM Instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. For every instance, click on its name to go to the `VM instance details` page. 3. Under the `Network interfaces` section, ensure that `IP forwarding` is set to `Off` for every network interface. **From Google Cloud CLI** 1. List all instances: gcloud compute instances list --format='table(name,canIpForward)' 2. Ensure that `CAN_IP_FORWARD` column in the output of above command does not contain `True` for any VM instance. **Exception:** Instances created by GKE should be excluded because they need to have IP forwarding enabled and cannot be changed. Instances created by GKE have names that start with gke-.",
+ "AdditionalInformation": "You can only set the `canIpForward` field at instance creation time or using CLI.",
+ "References": "https://cloud.google.com/vpc/docs/using-routes#canipforward:https://cloud.google.com/compute/docs/instances/update-instance-properties",
+ "DefaultValue": "By default, instances are not configured to allow IP forwarding.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.7",
+ "Description": "Ensure VM Disks for Critical VMs Are Encrypted With Customer-Supplied Encryption Keys (CSEK)",
+ "Checks": [
+ "compute_instance_encryption_with_csek_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Customer-Supplied Encryption Keys (CSEK) are a feature in Google Cloud Storage and Google Compute Engine. If you supply your own encryption keys, Google uses your key to protect the Google-generated keys used to encrypt and decrypt your data. By default, Google Compute Engine encrypts all data at rest. Compute Engine handles and manages this encryption for you without any additional actions on your part. However, if you wanted to control and manage this encryption yourself, you can provide your own encryption keys.",
+ "RationaleStatement": "By default, Google Compute Engine encrypts all data at rest. Compute Engine handles and manages this encryption for you without any additional actions on your part. However, if you wanted to control and manage this encryption yourself, you can provide your own encryption keys. If you provide your own encryption keys, Compute Engine uses your key to protect the Google-generated keys used to encrypt and decrypt your data. Only users who can provide the correct key can use resources protected by a customer-supplied encryption key. Google does not store your keys on its servers and cannot access your protected data unless you provide the key. This also means that if you forget or lose your key, there is no way for Google to recover the key or to recover any data encrypted with the lost key. At least business critical VMs should have VM disks encrypted with CSEK.",
+ "ImpactStatement": "If you lose your encryption key, you will not be able to recover the data.",
+ "RemediationProcedure": "Currently there is no way to update the encryption of an existing disk. Therefore you should create a new disk with `Encryption` set to `Customer supplied`. **From Google Cloud Console** 1. Go to Compute Engine `Disks` by visiting: [https://console.cloud.google.com/compute/disks](https://console.cloud.google.com/compute/disks). 2. Click `CREATE DISK`. 3. Set `Encryption type` to `Customer supplied`, 4. Provide the `Key` in the box. 5. Select `Wrapped key`. 6. Click `Create`. **From Google Cloud CLI** In the gcloud compute tool, encrypt a disk using the --csek-key-file flag during instance creation. If you are using an RSA-wrapped key, use the gcloud beta component: gcloud compute instances create <INSTANCE_NAME> --csek-key-file <example-file.json> To encrypt a standalone persistent disk: gcloud compute disks create <DISK_NAME> --csek-key-file <example-file.json> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to Compute Engine `Disks` by visiting: [https://console.cloud.google.com/compute/disks](https://console.cloud.google.com/compute/disks). 2. Click on the disk for your critical VMs to see its configuration details. 4. Ensure that `Encryption type` is set to `Customer supplied`. **From Google Cloud CLI** Ensure `diskEncryptionKey` property in the below command's response is not null, and contains key `sha256` with corresponding value gcloud compute disks describe <DISK_NAME> --zone <ZONE> --format=json(diskEncryptionKey,name) ",
+ "AdditionalInformation": "`Note 1:` When you delete a persistent disk, Google discards the cipher keys, rendering the data irretrievable. This process is irreversible. `Note 2:` It is up to you to generate and manage your key. You must provide a key that is a 256-bit string encoded in RFC 4648 standard base64 to Compute Engine. `Note 3:` An example key file looks like this. [ { uri: https://www.googleapis.com/compute/v1/projects/myproject/zones/us-central1-a/disks/example-disk, key: acXTX3rxrKAFTF0tYVLvydU1riRZTvUNC4g5I11NY-c=, key-type: raw }, { uri: https://www.googleapis.com/compute/v1/projects/myproject/global/snapshots/my-private-snapshot, key: ieCx/NcW06PcT7Ep1X6LUTc/hLvUDYyzSZPPVCVPTVEohpeHASqC8uw5TzyO9U+Fka9JFHz0mBibXUInrC/jEk014kCK/NPjYgEMOyssZ4ZINPKxlUh2zn1bV+MCaTICrdmuSBTWlUUiFoDD6PYznLwh8ZNdaheCeZ8ewEXgFQ8V+sDroLaN3Xs3MDTXQEMMoNUXMCZEIpg9Vtp9x2oeQ5lAbtt7bYAAHf5l+gJWw3sUfs0/Glw5fpdjT8Uggrr+RMZezGrltJEF293rvTIjWOEB3z5OHyHwQkvdrPDFcTqsLfh+8Hr8g+mf+7zVPEC8nEbqpdl3GPv3A7AwpFp7MA== key-type: rsa-encrypted } ]",
+ "References": "https://cloud.google.com/compute/docs/disks/customer-supplied-encryption#encrypt_a_new_persistent_disk_with_your_own_keys:https://cloud.google.com/compute/docs/reference/rest/v1/disks/get:https://cloud.google.com/compute/docs/disks/customer-supplied-encryption#key_file",
+ "DefaultValue": "By default, VM disks are encrypted with Google-managed keys. They are not encrypted with Customer-Supplied Encryption Keys.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.8",
+ "Description": "Ensure Compute Instances Are Launched With Shielded VM Enabled",
+ "Checks": [
+ "compute_instance_shielded_vm_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "To defend against advanced threats and ensure that the boot loader and firmware on your VMs are signed and untampered, it is recommended that Compute instances are launched with Shielded VM enabled.",
+ "RationaleStatement": "Shielded VMs are virtual machines (VMs) on Google Cloud Platform hardened by a set of security controls that help defend against rootkits and bootkits. Shielded VM offers verifiable integrity of your Compute Engine VM instances, so you can be confident your instances haven't been compromised by boot- or kernel-level malware or rootkits. Shielded VM's verifiable integrity is achieved through the use of Secure Boot, virtual trusted platform module (vTPM)-enabled Measured Boot, and integrity monitoring. Shielded VM instances run firmware which is signed and verified using Google's Certificate Authority, ensuring that the instance's firmware is unmodified and establishing the root of trust for Secure Boot. Integrity monitoring helps you understand and make decisions about the state of your VM instances and the Shielded VM vTPM enables Measured Boot by performing the measurements needed to create a known good boot baseline, called the integrity policy baseline. The integrity policy baseline is used for comparison with measurements from subsequent VM boots to determine if anything has changed. Secure Boot helps ensure that the system only runs authentic software by verifying the digital signature of all boot components, and halting the boot process if signature verification fails.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "To be able turn on `Shielded VM` on an instance, your instance must use an image with Shielded VM support. **From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the instance name to see its `VM instance details` page. 3. Click `STOP` to stop the instance. 4. When the instance has stopped, click `EDIT`. 5. In the Shielded VM section, select `Turn on vTPM` and `Turn on Integrity Monitoring`. 6. Optionally, if you do not use any custom or unsigned drivers on the instance, also select `Turn on Secure Boot`. 7. Click the `Save` button to modify the instance and then click `START` to restart it. **From Google Cloud CLI** You can only enable Shielded VM options on instances that have Shielded VM support. For a list of Shielded VM public images, run the gcloud compute images list command with the following flags: gcloud compute images list --project gce-uefi-images --no-standard-images 1. Stop the instance: gcloud compute instances stop <INSTANCE_NAME> 2. Update the instance: gcloud compute instances update <INSTANCE_NAME> --shielded-vtpm --shielded-vm-integrity-monitoring 3. Optionally, if you do not use any custom or unsigned drivers on the instance, also turn on secure boot. gcloud compute instances update <INSTANCE_NAME> --shielded-vm-secure-boot 4. Restart the instance: gcloud compute instances start <INSTANCE_NAME> **Prevention:** You can ensure that all new VMs will be created with Shielded VM enabled by setting up an Organization Policy to for `Shielded VM` at [https://console.cloud.google.com/iam-admin/orgpolicies/compute-requireShieldedVm](https://console.cloud.google.com/iam-admin/orgpolicies/compute-requireShieldedVm). Learn more at: [https://cloud.google.com/security/shielded-cloud/shielded-vm#organization-policy-constraint](https://cloud.google.com/security/shielded-cloud/shielded-vm#organization-policy-constraint).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the instance name to see its `VM instance details` page. 3. Under the section `Shielded VM`, ensure that `vTPM` and `Integrity Monitoring` are `on`. **From Google Cloud CLI** 1. For each instance in your project, get its metadata: gcloud compute instances list --format=json | jq -r '. | vTPM: (.[].shieldedInstanceConfig.enableVtpm) IntegrityMonitoring: (.[].shieldedInstanceConfig.enableIntegrityMonitoring) Name: (.[].name)' 2. Ensure that there is a `shieldedInstanceConfig` configuration and that configuration has the `enableIntegrityMonitoring` and `enableVtpm` set to `true`. If the VM is not a Shield VM image, you will not see a shieldedInstanceConfig` in the output.",
+ "AdditionalInformation": "If you do use custom or unsigned drivers on the instance, enabling Secure Boot will cause the machine to no longer boot. Turn on Secure Boot only on instances that have been verified to not have any custom drivers installed.",
+ "References": "https://cloud.google.com/compute/docs/instances/modifying-shielded-vm:https://cloud.google.com/shielded-vm:https://cloud.google.com/security/shielded-cloud/shielded-vm#organization-policy-constraint",
+ "DefaultValue": "By default, Compute Instances do not have Shielded VM enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.9",
+ "Description": "Ensure That Compute Instances Do Not Have Public IP Addresses",
+ "Checks": [
+ "compute_instance_public_ip"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Compute instances should not be configured to have external IP addresses.",
+ "RationaleStatement": "To reduce your attack surface, Compute instances should not have public IP addresses. Instead, instances should be configured behind load balancers, to minimize the instance's exposure to the internet.",
+ "ImpactStatement": "Removing the external IP address from your Compute instance may cause some applications to stop working.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the instance name to go the the `Instance detail page`. 3. Click `Edit`. 4. For each Network interface, ensure that `External IP` is set to `None`. 5. Click `Done` and then click `Save`. **From Google Cloud CLI** 1. Describe the instance properties: gcloud compute instances describe <INSTANCE_NAME> --zone=<ZONE> 2. Identify the access config name that contains the external IP address. This access config appears in the following format: networkInterfaces: - accessConfigs: - kind: compute#accessConfig name: External NAT natIP: 130.211.181.55 type: ONE_TO_ONE_NAT 3. Delete the access config. gcloud compute instances delete-access-config <INSTANCE_NAME> --zone=<ZONE> --access-config-name <ACCESS_CONFIG_NAME> In the above example, the `ACCESS_CONFIG_NAME` is `External NAT`. The name of your access config might be different. **Prevention:** You can configure the `Define allowed external IPs for VM instances` Organization Policy to prevent VMs from being configured with public IP addresses. Learn more at: [https://console.cloud.google.com/orgpolicies/compute-vmExternalIpAccess](https://console.cloud.google.com/orgpolicies/compute-vmExternalIpAccess)",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. For every VM, ensure that there is no `External IP` configured. **From Google Cloud CLI** gcloud compute instances list --format=json 1. The output should not contain an `accessConfigs` section under `networkInterfaces`. Note that the `natIP` value is present only for instances that are running or for instances that are stopped but have a static IP address. For instances that are stopped and are configured to have an ephemeral public IP address, the `natIP` field will not be present. Example output: networkInterfaces: - accessConfigs: - kind: compute#accessConfig name: External NAT networkTier: STANDARD type: ONE_TO_ONE_NAT **Exception:** Instances created by GKE should be excluded because some of them have external IP addresses and cannot be changed by editing the instance settings. Instances created by GKE should be excluded. These instances have names that start with gke- and are labeled goog-gke-node.",
+ "AdditionalInformation": "You can connect to Linux VMs that do not have public IP addresses by using Identity-Aware Proxy for TCP forwarding. Learn more at [https://cloud.google.com/compute/docs/instances/connecting-advanced#sshbetweeninstances](https://cloud.google.com/compute/docs/instances/connecting-advanced#sshbetweeninstances) For Windows VMs, see [https://cloud.google.com/compute/docs/instances/connecting-to-instance](https://cloud.google.com/compute/docs/instances/connecting-to-instance).",
+ "References": "https://cloud.google.com/load-balancing/docs/backend-service#backends_and_external_ip_addresses:https://cloud.google.com/compute/docs/instances/connecting-advanced#sshbetweeninstances:https://cloud.google.com/compute/docs/instances/connecting-to-instance:https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address#unassign_ip:https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints",
+ "DefaultValue": "By default, Compute instances have a public IP address.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.10",
+ "Description": "Ensure That App Engine Applications Enforce HTTPS Connections",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "In order to maintain the highest level of security all connections to an application should be secure by default.",
+ "RationaleStatement": "Insecure HTTP connections maybe subject to eavesdropping which can expose sensitive data.",
+ "ImpactStatement": "All connections to appengine will automatically be redirected to the HTTPS endpoint ensuring that all connections are secured by TLS.",
+ "RemediationProcedure": "Add a line to the app.yaml file controlling the application which enforces secure connections. For example handlers: - url: /.* **secure: always** redirect_http_response_code: 301 script: auto [https://cloud.google.com/appengine/docs/standard/python3/config/appref]",
+ "AuditProcedure": "Verify that the app.yaml file controlling the application contains a line which enforces secure connections. For example handlers: - url: /.* secure: always redirect_http_response_code: 301 script: auto [https://cloud.google.com/appengine/docs/standard/python3/config/appref](https://cloud.google.com/appengine/docs/standard/python3/config/appref)",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/appengine/docs/standard/python3/config/appref:https://cloud.google.com/appengine/docs/flexible/nodejs/configuring-your-app-with-app-yaml",
+ "DefaultValue": "By default both HTTP and HTTP are supported",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.11",
+ "Description": "Ensure That Compute Instances Have Confidential Computing Enabled",
+ "Checks": [
+ "compute_instance_confidential_computing_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Google Cloud encrypts data at-rest and in-transit, but customer data must be decrypted for processing. Confidential Computing is a breakthrough technology that encrypts data in-use while it is being processed. Confidential Computing environments keep data encrypted in memory and elsewhere outside the central processing unit (CPU). Confidential VMs leverage hardware-based memory encryption technologies, such as AMD Secure Encrypted Virtualization (SEV), AMD SEV-SNP, and Intel Trust Domain Extensions (TDX), depending on the chosen machine type and CPU platform. Customer data will stay encrypted while it is used, indexed, queried, or trained on. Encryption keys are generated by and reside solely in dedicated hardware and are not exportable, enhancing isolation and security. Built-in hardware optimizations ensure Confidential Computing workloads experience minimal to no significant performance penalties.",
+ "RationaleStatement": "Confidential Computing enables customers' sensitive code and other data encrypted in memory during processing. Google does not have access to the encryption keys. Confidential VM can help alleviate concerns about risk related to either dependency on Google infrastructure or Google insiders' access to customer data in the clear.",
+ "ImpactStatement": "- Confidential Computing for Compute instances does not support live migration. Unlike regular Compute instances, Confidential VMs experience disruptions during maintenance events like a software or hardware update. - Additional charges may be incurred when enabling this security feature. See [https://cloud.google.com/compute/confidential-vm/pricing](https://cloud.google.com/compute/confidential-vm/pricing) for more info.",
+ "RemediationProcedure": "Confidential Computing can only be enabled when an instance is created. You must delete the current instance and create a new one. **From Google Cloud Console** 1. Go to the VM instances page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click `CREATE INSTANCE`. 3. Fill out the desired configuration for your instance. 4. Under the `Confidential VM service` section, check the option `Enable the Confidential Computing service on this VM instance`. 5. Click `Create`. **From Google Cloud CLI** Create a new instance with Confidential Compute enabled. gcloud compute instances create <INSTANCE_NAME> --zone <ZONE> --confidential-compute --maintenance-policy=TERMINATE ",
+ "AuditProcedure": "Note: Confidential Computing is currently only supported on limited VM configurations. To learn more about VM configurations supported by Confidential Computing, visit [https://cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations](https://cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations) **From Google Cloud Console** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on the instance name to see its VM instance details page. 3. Ensure that `Confidential VM service` is `Enabled`. **From Google Cloud CLI** 1. List the instances in your project and get details on each instance: gcloud compute instances list --format=json 2. Ensure that `enableConfidentialCompute` is set to `true` for all instances with machine type starting with n2d-. confidentialInstanceConfig: enableConfidentialCompute: true ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/compute/confidential-vm/docs/creating-cvm-instance:https://cloud.google.com/compute/confidential-vm/docs/about-cvm:https://cloud.google.com/confidential-computing:https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-confidential-computing-with-confidential-vms",
+ "DefaultValue": "By default, Confidential Computing is disabled for Compute instances.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "4.12",
+ "Description": "Ensure the Latest Operating System Updates Are Installed On Your Virtual Machines in All Projects",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Virtual Machines",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Google Cloud Virtual Machines have the ability via an OS Config agent API to periodically (about every 10 minutes) report OS inventory data. A patch compliance API periodically reads this data, and cross references metadata to determine if the latest updates are installed. This is not the only Patch Management solution available to your organization and you should weigh your needs before committing to using this method.",
+ "RationaleStatement": "Keeping virtual machine operating systems up to date is a security best practice. Using this service will simplify this process.",
+ "ImpactStatement": "Most Operating Systems require a restart or changing critical resources to apply the updates. Using the Google Cloud VM manager for its OS Patch management will incur additional costs for each VM managed by it. Please view the VM manager pricing reference for further information.",
+ "RemediationProcedure": "**From Google Cloud Console** **Enabling OS Patch Management on a Project by Project Basis** **Install OS Config API for the Project** 1. Navigate into a project. In the expanded portal menu located at the top left of the screen hover over APIs & Services. Then in the menu right of that select API Libraries 2. Search for VM Manager (OS Config API) or scroll down in the left hand column and select the filter labeled Compute where it is the last listed. Open this API. 3. Click the blue 'Enable' button. **Add MetaData Tags for OSConfig Parsing** 1. From the main Google Cloud console, open the portal menu in the top left. Mouse over Computer Engine to expand the menu next to it. 2. Under the Settings heading, select Metadata. 3. In this view there will be a list of the project wide metadata tags for VMs. Click edit and 'add item' in the key column type 'enable-osconfig' and in the value column set it to 'true'. From Command Line 1. For project wide tagging, run the following command gcloud compute project-info add-metadata --project <PROJECT_ID> --metadata=enable-osconfig=TRUE Please see the reference /compute/docs/troubleshooting/vm-manager/verify-setup#metadata-enabled at the bottom for more options like instance specific tagging. Note: Adding a new tag via commandline may overwrite existing tags. You will need to do this at a time of low usage for the least impact. **Install and Start the Local OSConfig for Data Parsing** There is no way to centrally manage or start the Local OSConfig agent. Please view the reference of manage-os#agent-install to view specific operating system commands. **Setup a project wide Service Account** Please view Recommendation 4.1 to view how to setup a service account. Rerun the audit procedure to test if it has taken effect. **Enable NAT or Configure Private Google Access to allow Access to Public Update Hosting** For the sake of brevity, please see the attached resources to enable NAT or Private Google Access. Rerun the audit procedure to test if it has taken effect. From Command Line: **Install OS Config API for the Project** 1. In each project you wish to audit run gcloud services enable osconfig.googleapis.com **Install and Start the Local OSConfig for Data Parsing** Please view the reference of manage-os#agent-install to view specific operating system commands. **Setup a project wide Service Account** Please view Recommendation 4.1 to view how to setup a service account. Rerun the audit procedure to test if it has taken effect. **Enable NAT or Configure Private Google Access to allow Access to Public Update Hosting** For the sake of brevity, please see the attached resources to enable NAT or Private Google Access. Rerun the audit procedure to test if it has taken effect. Determine if Instances can connect to public update hosting Linux Debian Based Operating Systems sudo apt update The output should have a numbered list of lines with Hit: URL of updates. Redhat Based Operating Systems yum check-update The output should show a list of packages that have updates available. Windows ping http://windowsupdate.microsoft.com/ The ping should successfully be delivered and received.",
+ "AuditProcedure": "**From Google Cloud Console** **Determine if OS Config API is Enabled for the Project** 1. Navigate into a project. In the expanded navigation menu located at the top left of the screen hover over `APIs & Services`. Then in the menu right of that select `API Libraries` 2. Search for VM Manager (OS Config API) or scroll down in the left hand column and select the filter labeled Compute where it is the last listed. Open this API. 3. Verify the blue button at the top is enabled. **Determine if VM Instances have correct metadata tags for OSConfig parsing** 1. From the main Google Cloud console, open the hamburger menu in the top left. Mouse over Computer Engine to expand the menu next to it. 1. Under the Settings heading, select Metadata. 1. In this view there will be a list of the project wide metadata tags for VMs. Determine if the tag enable-osconfig is set to true. **Determine if the Operating System of VM Instances have the local OS-Config Agent running** There is no way to determine this from the Google Cloud console. The only way is to run operating specific commands locally inside the operating system via remote connection. For the sake of brevity of this recommendation please view the docs/troubleshooting/vm-manager/verify-setup reference at the bottom of the page. If you initialized your VM instance with a Google Supplied OS Image with a build date of later than v20200114 it will have the service installed. You should still determine its status for proper operation. **Verify the service account you have setup for the project in Recommendation 4.1 is running** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on each instance name to go to its `VM instance details` page. 3. Under the section `Service Account`, take note of the service account 4. Run the commands locally for your operating system that are located at the docs/troubleshooting/vm-manager/verify-setup#service-account-enabled reference located at the bottom of this page. They should return the name of your service account. **Determine if Instances can connect to public update hosting** Each type of operating system has its own update process. You will need to determine on each operating system that it can reach the update servers via its network connection. The VM Manager doesn't host the updates, it will only allow you to centrally issue a command to each VM to update. **Determine if OS Config API is Enabled for the Project** 1. In each project you wish to enable run the following command gcloud services list 2. If osconfig.googleapis.com is in the left hand column it is enabled for this project. **Determine if VM Manager is Enabled for the Project** 1. Within the project run the following command: gcloud compute instances os-inventory describe VM-NAME --zone=ZONE The output will look like INSTANCE_ID INSTANCE_NAME OS OSCONFIG_AGENT_VERSION UPDATE_TIME 29255009728795105 centos7 CentOS Linux 7 (Core) 20210217.00-g1.el7 2021-04-12T22:19:36.559Z 5138980234596718741 rhel-8 Red Hat Enterprise Linux 8.3 (Ootpa) 20210316.00-g1.el8 2021-09-16T17:19:24Z 7127836223366142250 windows Microsoft Windows Server 2019 Datacenter 20210316.00.0+win@1 2021-09-16T17:13:18Z **Determine if VM Instances have correct metadata tags for OSConfig parsing** 1. Select the project you want to view tagging in. **From Google Cloud Console** 1. From the main Google Cloud console, open the hamburger menu in the top left. Mouse over Computer Engine to expand the menu next to it. 2. Under the Settings heading, select Metadata. 3. In this view there will be a list of the project wide metadata tags for Vms. Verify a tag of ‘enable-osconfig’ is in this list and it is set to ‘true’. **From Command Line** Run the following command to view instance data gcloud compute instances list --format=table(name,status,tags.list()) On each instance it should have a tag of ‘enable-osconfig’ set to ‘true’ **Determine if the Operating System of VM Instances have the local OS-Config Agent running** There is no way to determine this from the Google Cloud CLI. The best way is to run the the commands inside the operating system located at 'Check OS-Config agent is installed and running' at the /docs/troubleshooting/vm-manager/verify-setup reference at the bottom of the page. If you initialized your VM instance with a Google Supplied OS Image with a build date of later than v20200114 it will have the service installed. You should still determine its status. **Verify the service account you have setup for the project in Recommendation 4.1 is running** 1. Go to the `VM instances` page by visiting: [https://console.cloud.google.com/compute/instances](https://console.cloud.google.com/compute/instances). 2. Click on each instance name to go to its `VM instance details` page. 3. Under the section `Service Account`, take note of the service account 4. View the compute/docs/troubleshooting/vm-manager/verify-setup#service-account-enabled resource at the bottom of the page for operating system specific commands to run locally. **Determine if Instances can connect to public update hosting** Linux Debian Based Operating Systems sudo apt update The output should have a numbered list of lines with Hit: URL of updates. Redhat Based Operating Systems yum check-update The output should show a list of packages that have updates available. Windows ping http://windowsupdate.microsoft.com/ The ping should successfully be delivered and received.",
+ "AdditionalInformation": "This is not your only solution to handle updates. This is a Google Cloud specific recommendation to leverage a resource to solve the need for comprehensive update procedures and policy. If you have a solution already in place you do not need to make the switch. There are also further resources that would be out of the scope of this recommendation. If you need to allow your VMs to access public hosted updates, please see the reference to setup NAT or Private Google Access.",
+ "References": "https://cloud.google.com/compute/docs/manage-os:https://cloud.google.com/compute/docs/os-patch-management:https://cloud.google.com/compute/docs/vm-manager:https://cloud.google.com/compute/docs/images/os-details#vm-manager:https://cloud.google.com/compute/docs/vm-manager#pricing:https://cloud.google.com/compute/docs/troubleshooting/vm-manager/verify-setup:https://cloud.google.com/compute/docs/instances/view-os-details#view-data-tools:https://cloud.google.com/compute/docs/os-patch-management/create-patch-job:https://cloud.google.com/nat/docs/set-up-network-address-translation:https://cloud.google.com/vpc/docs/configure-private-google-access:https://workbench.cisecurity.org/sections/811638/recommendations/1334335:https://cloud.google.com/compute/docs/manage-os#agent-install:https://cloud.google.com/compute/docs/troubleshooting/vm-manager/verify-setup#service-account-enabled:https://cloud.google.com/compute/docs/os-patch-management#use-dashboard:https://cloud.google.com/compute/docs/troubleshooting/vm-manager/verify-setup#metadata-enabled",
+ "DefaultValue": "By default most operating systems and programs do not update themselves. The Google Cloud VM Manager which is a dependency of the OS Patch management feature is installed on Google Built OS images with a build date of v20200114 or later. The VM manager is not enabled in a project by default and will need to be setup.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "5.1",
+ "Description": "Ensure That Cloud Storage Bucket Is Not Anonymously or Publicly Accessible",
+ "Checks": [
+ "cloudstorage_bucket_public_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Storage",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that IAM policy on Cloud Storage bucket does not allows anonymous or public access.",
+ "RationaleStatement": "Allowing anonymous or public access grants permissions to anyone to access bucket content. Such access might not be desired if you are storing any sensitive data. Hence, ensure that anonymous or public access to a bucket is not allowed.",
+ "ImpactStatement": "No storage buckets would be publicly accessible. You would have to explicitly administer bucket access.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `Storage browser` by visiting [https://console.cloud.google.com/storage/browser](https://console.cloud.google.com/storage/browser). 2. Click on the bucket name to go to its `Bucket details` page. 3. Click on the `Permissions` tab. 4. Click `Delete` button in front of `allUsers` and `allAuthenticatedUsers` to remove that particular role assignment. **From Google Cloud CLI** Remove `allUsers` and `allAuthenticatedUsers` access. gsutil iam ch -d allUsers gs://BUCKET_NAME gsutil iam ch -d allAuthenticatedUsers gs://BUCKET_NAME **Prevention:** You can prevent Storage buckets from becoming publicly accessible by setting up the `Domain restricted sharing` organization policy at:[ https://console.cloud.google.com/iam-admin/orgpolicies/iam-allowedPolicyMemberDomains ](https://console.cloud.google.com/iam-admin/orgpolicies/iam-allowedPolicyMemberDomains).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Storage browser` by visiting [https://console.cloud.google.com/storage/browser](https://console.cloud.google.com/storage/browser). 2. Click on each bucket name to go to its `Bucket details` page. 3. Click on the `Permissions` tab. 4. Ensure that `allUsers` and `allAuthenticatedUsers` are not in the `Members` list. **From Google Cloud CLI** 1. List all buckets in a project gsutil ls 2. Check the IAM Policy for each bucket: gsutil iam get gs://BUCKET_NAME No role should contain `allUsers` and/or `allAuthenticatedUsers` as a member. **Using Rest API** 1. List all buckets in a project Get https://www.googleapis.com/storage/v1/b?project=<ProjectName> 2. Check the IAM Policy for each bucket GET https://www.googleapis.com/storage/v1/b/<bucketName>/iam No role should contain `allUsers` and/or `allAuthenticatedUsers` as a member.",
+ "AdditionalInformation": "To implement Access restrictions on buckets, configuring Bucket IAM is preferred way than configuring Bucket ACL. On GCP console, Edit Permissions for bucket exposes IAM configurations only. Bucket ACLs are configured automatically as per need in order to implement/support User enforced Bucket IAM policy. In-case administrator changes bucket ACL using command-line(gsutils)/API bucket IAM also gets updated automatically.",
+ "References": "https://cloud.google.com/storage/docs/access-control/iam-reference:https://cloud.google.com/storage/docs/access-control/making-data-public:https://cloud.google.com/storage/docs/gsutil/commands/iam",
+ "DefaultValue": "By Default, Storage buckets are not publicly shared.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "5.2",
+ "Description": "Ensure That Cloud Storage Buckets Have Uniform Bucket-Level Access Enabled",
+ "Checks": [
+ "cloudstorage_bucket_uniform_bucket_level_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Storage",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that uniform bucket-level access is enabled on Cloud Storage buckets.",
+ "RationaleStatement": "It is recommended to use uniform bucket-level access to unify and simplify how you grant access to your Cloud Storage resources. Cloud Storage offers two systems for granting users permission to access your buckets and objects: Cloud Identity and Access Management (Cloud IAM) and Access Control Lists (ACLs). These systems act in parallel - in order for a user to access a Cloud Storage resource, only one of the systems needs to grant the user permission. Cloud IAM is used throughout Google Cloud and allows you to grant a variety of permissions at the bucket and project levels. ACLs are used only by Cloud Storage and have limited permission options, but they allow you to grant permissions on a per-object basis. In order to support a uniform permissioning system, Cloud Storage has uniform bucket-level access. Using this feature disables ACLs for all Cloud Storage resources: access to Cloud Storage resources then is granted exclusively through Cloud IAM. Enabling uniform bucket-level access guarantees that if a Storage bucket is not publicly accessible, no object in the bucket is publicly accessible either.",
+ "ImpactStatement": "If you enable uniform bucket-level access, you revoke access from users who gain their access solely through object ACLs. Certain Google Cloud services, such as Stackdriver, Cloud Audit Logs, and Datastore, cannot export to Cloud Storage buckets that have uniform bucket-level access enabled.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Open the Cloud Storage browser in the Google Cloud Console by visiting: [https://console.cloud.google.com/storage/browser](https://console.cloud.google.com/storage/browser) 2. In the list of buckets, click on the name of the desired bucket. 3. Select the `Permissions` tab near the top of the page. 4. In the text box that starts with `This bucket uses fine-grained access control...`, click `Edit`. 5. In the pop-up menu that appears, select `Uniform`. 6. Click `Save`. **From Google Cloud CLI** Use the on option in a uniformbucketlevelaccess set command: gsutil uniformbucketlevelaccess set on gs://BUCKET_NAME/ **Prevention** You can set up an Organization Policy to enforce that any new bucket has uniform bucket level access enabled. Learn more at: [https://cloud.google.com/storage/docs/setting-org-policies#uniform-bucket](https://cloud.google.com/storage/docs/setting-org-policies#uniform-bucket)",
+ "AuditProcedure": "**From Google Cloud Console** 1. Open the Cloud Storage browser in the Google Cloud Console by visiting: [https://console.cloud.google.com/storage/browser](https://console.cloud.google.com/storage/browser) 2. For each bucket, make sure that `Access control` column has the value `Uniform`. **From Google Cloud CLI** 1. List all buckets in a project gsutil ls 2. For each bucket, verify that uniform bucket-level access is enabled. gsutil uniformbucketlevelaccess get gs://BUCKET_NAME/ If uniform bucket-level access is enabled, the response looks like: Uniform bucket-level access setting for gs://BUCKET_NAME/: Enabled: True LockedTime: LOCK_DATE ",
+ "AdditionalInformation": "Uniform bucket-level access can no longer be disabled if it has been active on a bucket for 90 consecutive days.",
+ "References": "https://cloud.google.com/storage/docs/uniform-bucket-level-access:https://cloud.google.com/storage/docs/using-uniform-bucket-level-access:https://cloud.google.com/storage/docs/setting-org-policies#uniform-bucket",
+ "DefaultValue": "By default, Cloud Storage buckets do not have uniform bucket-level access enabled.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1",
+ "Description": "Ensure That a MySQL Instance Does Not Allow Anyone To Connect With Administrative Privileges",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.1 MySQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "It is recommended to set a password for the administrative user (`root` by default) to prevent unauthorized access to the SQL database instances. This recommendation is applicable only for MySQL Instances. PostgreSQL does not offer any setting for No Password from the cloud console.",
+ "RationaleStatement": "At the time of MySQL Instance creation, not providing an administrative password allows anyone to connect to the SQL database instance with administrative privileges. The root password should be set to ensure only authorized users have these privileges.",
+ "ImpactStatement": "Connection strings for administrative clients need to be reconfigured to use a password.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Platform Console using `https://console.cloud.google.com/sql/` 2. Select the instance to open its Overview page. 3. Select `Access Control > Users`. 4. Click the `More actions icon` for the user to be updated. 5. Select `Change password`, specify a `New password`, and click `OK`. **From Google Cloud CLI** 1. Set a password to a MySql instance: gcloud sql users set-password root --host=<host> --instance=<instance_name> --prompt-for-password 2. A prompt will appear, requiring the user to enter a password: Instance Password: 3. With a successful password configured, the following message should be seen: Updating Cloud SQL user...done. ",
+ "AuditProcedure": "**From Google Cloud CLI** 1. List All SQL database instances of type MySQL: gcloud sql instances list --filter='DATABASE_VERSION:MYSQL*' --project <project_id> --format=(NAME,PRIMARY_ADDRESS) 2. For every MySQL instance try to connect using the `PRIMARY_ADDRESS`, if available: mysql -u root -h <mysql_instance_ip_address> The command should return either an error message or a password prompt. Sample Error message: ERROR 1045 (28000): Access denied for user 'root'@'<Instance_IP>' (using password: NO) If a command produces the `mysql>` prompt, the MySQL instance allows anyone to connect with administrative privileges without needing a password. **Note:** The `No Password` setting is exposed only at the time of MySQL instance creation. Once the instance is created, the Google Cloud Platform Console does not expose the set to confirm whether a password for an administrative user is set to a MySQL instance.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/sql/docs/mysql/create-manage-users:https://cloud.google.com/sql/docs/mysql/create-instance",
+ "DefaultValue": "From the Google Cloud Platform Console, the `Create Instance` workflow enforces the rule to enter the root password unless the option `No Password` is selected explicitly."
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2",
+ "Description": "Ensure ‘Skip_show_database’ Database Flag for Cloud SQL MySQL Instance Is Set to ‘On’",
+ "Checks": [
+ "cloudsql_instance_mysql_skip_show_database_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.1 MySQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set `skip_show_database` database flag for Cloud SQL Mysql instance to `on`",
+ "RationaleStatement": "`skip_show_database` database flag prevents people from using the SHOW DATABASES statement if they do not have the SHOW DATABASES privilege. This can improve security if you have concerns about users being able to see databases belonging to other users. Its effect depends on the SHOW DATABASES privilege: If the variable value is ON, the SHOW DATABASES statement is permitted only to users who have the SHOW DATABASES privilege, and the statement displays all database names. If the value is OFF, SHOW DATABASES is permitted to all users, but displays the names of only those databases for which the user has the SHOW DATABASES or other privilege. This recommendation is applicable to Mysql database instances.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the Mysql instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `skip_show_database` from the drop-down menu, and set its value to `on`. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. List all Cloud SQL database Instances gcloud sql instances list 2. Configure the `skip_show_database` database flag for every Cloud SQL Mysql database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags skip_show_database=on **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `skip_show_database` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. List all Cloud SQL database Instances gcloud sql instances list 2. Ensure the below command returns `on` for every Cloud SQL Mysql database instance gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==skip_show_database)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/mysql/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag restarts the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/mysql/flags:https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_skip_show_database",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "6.1.3",
+ "Description": "Ensure That the ‘Local_infile’ Database Flag for a Cloud SQL MySQL Instance Is Set to ‘Off’",
+ "Checks": [
+ "cloudsql_instance_mysql_local_infile_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.1 MySQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set the `local_infile` database flag for a Cloud SQL MySQL instance to `off`.",
+ "RationaleStatement": "The `local_infile` flag controls the server-side LOCAL capability for LOAD DATA statements. Depending on the `local_infile` setting, the server refuses or permits local data loading by clients that have LOCAL enabled on the client side. To explicitly cause the server to refuse LOAD DATA LOCAL statements (regardless of how client programs and libraries are configured at build time or runtime), start mysqld with local_infile disabled. local_infile can also be set at runtime. Due to security issues associated with the `local_infile` flag, it is recommended to disable it. This recommendation is applicable to MySQL database instances.",
+ "ImpactStatement": "Disabling `local_infile` makes the server refuse local data loading by clients that have LOCAL enabled on the client side.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the MySQL instance where the database flag needs to be enabled. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `local_infile` from the drop-down menu, and set its value to `off`. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. List all Cloud SQL database instances using the following command: gcloud sql instances list 2. Configure the `local_infile` database flag for every Cloud SQL Mysql database instance using the below command: gcloud sql instances patch <INSTANCE_NAME> --database-flags local_infile=off **Note**: This command will overwrite all database flags that were previously set. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `local_infile` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. List all Cloud SQL database instances: gcloud sql instances list 2. Ensure the below command returns `off` for every Cloud SQL MySQL database instance. gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==local_infile)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require the instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/mysql/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines.",
+ "References": "https://cloud.google.com/sql/docs/mysql/flags:https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_local_infile:https://dev.mysql.com/doc/refman/5.7/en/load-data-local.html",
+ "DefaultValue": "By default `local_infile` is `on`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.1",
+ "Description": "Ensure ‘Log_error_verbosity’ Database Flag for Cloud SQL PostgreSQL Instance Is Set to ‘DEFAULT’ or Stricter",
+ "Checks": [
+ "cloudsql_instance_postgres_log_error_verbosity_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "The `log_error_verbosity` flag controls the verbosity/details of messages logged. Valid values are: - `TERSE` - `DEFAULT` - `VERBOSE` `TERSE` excludes the logging of `DETAIL`, `HINT`, `QUERY`, and `CONTEXT` error information. `VERBOSE` output includes the `SQLSTATE` error code, source code file name, function name, and line number that generated the error. Ensure an appropriate value is set to 'DEFAULT' or stricter.",
+ "RationaleStatement": "Auditing helps in troubleshooting operational problems and also permits forensic analysis. If `log_error_verbosity` is not set to the correct value, too many details or too few details may be logged. This flag should be configured with a value of 'DEFAULT' or stricter. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances. 2. Select the PostgreSQL instance for which you want to enable the database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `log_error_verbosity` from the drop-down menu and set appropriate value. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the log_error_verbosity database flag for every Cloud SQL PosgreSQL database instance using the below command. gcloud sql instances patch INSTANCE_NAME --database-flags log_error_verbosity=<TERSE|DEFAULT|VERBOSE> **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Go to `Configuration` card 4. Under `Database flags`, check the value of `log_error_verbosity` flag is set to 'DEFAULT' or stricter. **From Google Cloud CLI** 1. Use the below command for every Cloud SQL PostgreSQL database instance to verify the value of `log_error_verbosity` gcloud sql instances describe [INSTANCE_NAME] --format=json | jq '.settings.databaseFlags[] | select(.name==log_error_verbosity)|.value' In the output, database flags are listed under the settings as the collection databaseFlags.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY",
+ "DefaultValue": "By default `log_error_verbosity` is `DEFAULT`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.2",
+ "Description": "Ensure That the ‘Log_connections’ Database Flag for Cloud SQL PostgreSQL Instance Is Set to ‘On’",
+ "Checks": [
+ "cloudsql_instance_postgres_log_connections_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enabling the `log_connections` setting causes each attempted connection to the server to be logged, along with successful completion of client authentication. This parameter cannot be changed after the session starts.",
+ "RationaleStatement": "PostgreSQL does not log attempted connections by default. Enabling the `log_connections` setting will create log entries for each attempted connection as well as successful completion of client authentication which can be useful in troubleshooting issues and to determine any unusual connection attempts to the server. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances. 2. Select the PostgreSQL instance for which you want to enable the database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `log_connections` from the drop-down menu and set the value as `on`. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `log_connections` database flag for every Cloud SQL PosgreSQL database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags log_connections=on **Note**: This command will overwrite all previously set database flags. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page. 3. Go to the `Configuration` card. 4. Under `Database flags`, check the value of `log_connections` flag to determine if it is configured as expected. **From Google Cloud CLI** 1. Ensure the below command returns `on` for every Cloud SQL PostgreSQL database instance: gcloud sql instances describe [INSTANCE_NAME] --format=json | jq '.settings.databaseFlags[] | select(.name==log_connections)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see the Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-CONNECTIONS",
+ "DefaultValue": "By default `log_connections` is `off`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.3",
+ "Description": "Ensure That the ‘Log_disconnections’ Database Flag for Cloud SQL PostgreSQL Instance Is Set to ‘On’",
+ "Checks": [
+ "cloudsql_instance_postgres_log_disconnections_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enabling the `log_disconnections` setting logs the end of each session, including the session duration.",
+ "RationaleStatement": "PostgreSQL does not log session details such as duration and session end by default. Enabling the `log_disconnections` setting will create log entries at the end of each session which can be useful in troubleshooting issues and determine any unusual activity across a time period. The `log_disconnections` and `log_connections` work hand in hand and generally, the pair would be enabled/disabled together. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the PostgreSQL instance where the database flag needs to be enabled. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `log_disconnections` from the drop-down menu and set the value as `on`. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `log_disconnections` database flag for every Cloud SQL PosgreSQL database instance using the below command: gcloud sql instances patch <INSTANCE_NAME> --database-flags log_disconnections=on **Note**: This command will overwrite all previously set database flags. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Go to the `Configuration` card. 4. Under `Database flags`, check the value of `log_disconnections` flag is configured as expected. **From Google Cloud CLI** 1. Ensure the below command returns `on` for every Cloud SQL PostgreSQL database instance: gcloud sql instances list --format=json | jq '.[].settings.databaseFlags[] | select(.name==log_disconnections)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-DISCONNECTIONS",
+ "DefaultValue": "By default `log_disconnections` is off."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.4",
+ "Description": "Ensure ‘Log_statement’ Database Flag for Cloud SQL PostgreSQL Instance Is Set Appropriately",
+ "Checks": [
+ "cloudsql_instance_postgres_log_statement_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "The value of `log_statement` flag determined the SQL statements that are logged. Valid values are: - `none` - `ddl` - `mod` - `all` The value `ddl` logs all data definition statements. The value `mod` logs all ddl statements, plus data-modifying statements. The statements are logged after a basic parsing is done and statement type is determined, thus this does not logs statements with errors. When using extended query protocol, logging occurs after an Execute message is received and values of the Bind parameters are included. A value of 'ddl' is recommended unless otherwise directed by your organization's logging policy.",
+ "RationaleStatement": "Auditing helps in forensic analysis. If `log_statement` is not set to the correct value, too many statements may be logged leading to issues in finding the relevant information from the logs, or too few statements may be logged with relevant information missing from the logs. Setting log_statement to align with your organization's security and logging policies facilitates later auditing and review of database activities. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the PostgreSQL instance for which you want to enable the database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `log_statement` from the drop-down menu and set appropriate value. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `log_statement` database flag for every Cloud SQL PosgreSQL database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags log_statement=<ddl|mod|all|none> **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Go to `Configuration` card 4. Under `Database flags`, check the value of `log_statement` flag is set to appropriately. **From Google Cloud CLI** 1. Use the below command for every Cloud SQL PostgreSQL database instance to verify the value of `log_statement` gcloud sql instances list --format=json | jq '.[].settings.databaseFlags[] | select(.name==log_statement)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STATEMENT",
+ "DefaultValue": "`none`"
+ }
+ ]
+ },
+ {
+ "Id": "6.2.5",
+ "Description": "Ensure that the ‘Log_min_messages’ Flag for a Cloud SQL PostgreSQL Instance is set at minimum to 'Warning'",
+ "Checks": [
+ "cloudsql_instance_postgres_log_min_messages_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The `log_min_messages` flag defines the minimum message severity level that is considered as an error statement. Messages for error statements are logged with the SQL statement. Valid values include (from lowest to highest severity) `DEBUG5`, `DEBUG4`, `DEBUG3`, `DEBUG2`, `DEBUG1`, `INFO`, `NOTICE`, `WARNING`, `ERROR`, `LOG`, `FATAL`, and `PANIC`. Each severity level includes the subsequent levels mentioned above. ERROR is considered the best practice setting. Changes should only be made in accordance with the organization's logging policy.",
+ "RationaleStatement": "Auditing helps in troubleshooting operational problems and also permits forensic analysis. If `log_min_messages` is not set to the correct value, messages may not be classified as error messages appropriately. Setting the threshold to 'Warning' will log messages for the most needed error messages. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Setting the threshold too low will might result in increased log storage size and length, making it difficult to find actual errors. Higher severity levels may cause errors needed to troubleshoot to not be logged. An organization will need to decide their own threshold for logging `log_min_messages` flag. **Note**: To effectively turn off logging failing statements, set this parameter to PANIC.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances) 2. Select the PostgreSQL instance for which you want to enable the database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add a Database Flag`, choose the flag `log_min_messages` from the drop-down menu and set appropriate value. 6. Click `Save` to save the changes. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `log_min_messages` database flag for every Cloud SQL PosgreSQL database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags log_min_messages=<DEBUG5|DEBUG4|DEBUG3|DEBUG2|DEBUG1|INFO|NOTICE|WARNING|ERROR|LOG|FATAL|PANIC> **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page. 3. Go to the `Configuration` card. 4. Under `Database flags`, check the value of `log_min_messages` flag is set to `warning` or higher (WARNING|ERROR|LOG|FATAL|PANIC). **From Google Cloud CLI** 1. Use the below command for every Cloud SQL PostgreSQL database instance to verify that the value of `log_min_messages` is set to `warning` or higher . gcloud sql instances describe [INSTANCE_NAME] --format=json | jq '.settings.databaseFlags[] | select(.name==log_min_messages)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: Some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-MESSAGES",
+ "DefaultValue": "By default `log_min_messages` is `ERROR`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.6",
+ "Description": "Ensure ‘Log_min_error_statement’ Database Flag for Cloud SQL PostgreSQL Instance Is Set to ‘Error’ or Stricter",
+ "Checks": [
+ "cloudsql_instance_postgres_log_min_error_statement_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The `log_min_error_statement` flag defines the minimum message severity level that are considered as an error statement. Messages for error statements are logged with the SQL statement. Valid values include (from lowest to highest severity) `DEBUG5`, `DEBUG4`, `DEBUG3`, `DEBUG2`, `DEBUG1`, `INFO`, `NOTICE`, `WARNING`, `ERROR`, `LOG`, `FATAL`, and `PANIC`. Each severity level includes the subsequent levels mentioned above. Ensure a value of `ERROR` or stricter is set.",
+ "RationaleStatement": "Auditing helps in troubleshooting operational problems and also permits forensic analysis. If `log_min_error_statement` is not set to the correct value, messages may not be classified as error messages appropriately. Considering general log messages as error messages would make is difficult to find actual errors and considering only stricter severity levels as error messages may skip actual errors to log their SQL statements. The `log_min_error_statement` flag should be set to `ERROR` or stricter. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the PostgreSQL instance for which you want to enable the database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `log_min_error_statement` from the drop-down menu and set appropriate value. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `log_min_error_statement` database flag for every Cloud SQL PosgreSQL database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags log_min_error_statement=<DEBUG5|DEBUG4|DEBUG3|DEBUG2|DEBUG1|INFO|NOTICE|WARNING|ERROR> **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Go to `Configuration` card 4. Under `Database flags`, check the value of `log_min_error_statement` flag is configured as to `ERROR` or stricter. **From Google Cloud CLI** 1. Use the below command for every Cloud SQL PostgreSQL database instance to verify the value of `log_min_error_statement` is set to `ERROR` or stricter. gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.[].settings.databaseFlags[] | select(.name==log_min_error_statement)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-ERROR-STATEMENT",
+ "DefaultValue": "By default `log_min_error_statement` is `ERROR`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.7",
+ "Description": "Ensure That the ‘Log_min_duration_statement’ Database Flag for Cloud SQL PostgreSQL Instance Is Set to '-1' (Disabled)",
+ "Checks": [
+ "cloudsql_instance_postgres_log_min_duration_statement_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The `log_min_duration_statement` flag defines the minimum amount of execution time of a statement in milliseconds where the total duration of the statement is logged. Ensure that `log_min_duration_statement` is disabled, i.e., a value of `-1` is set.",
+ "RationaleStatement": "Logging SQL statements may include sensitive information that should not be recorded in logs. This recommendation is applicable to PostgreSQL database instances.",
+ "ImpactStatement": "Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the PostgreSQL instance where the database flag needs to be enabled. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `log_min_duration_statement` from the drop-down menu and set a value of `-1`. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. List all Cloud SQL database instances using the following command: gcloud sql instances list 2. Configure the `log_min_duration_statement` flag for every Cloud SQL PosgreSQL database instance using the below command: gcloud sql instances patch <INSTANCE_NAME> --database-flags log_min_duration_statement=-1 **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page. 3. Go to the `Configuration` card. 4. Under `Database flags`, check that the value of `log_min_duration_statement` flag is set to `-1`. **From Google Cloud CLI** 1. Use the below command for every Cloud SQL PostgreSQL database instance to verify the value of `log_min_duration_statement` is set to `-1`. gcloud sql instances describe <INSTANCE_NAME> --format=json| jq '.settings.databaseFlags[] | select(.name==log_min_duration_statement)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. **Note**: Some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not require restarting the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags:https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-DURATION-STATEMENT",
+ "DefaultValue": "By default `log_min_duration_statement` is `-1`."
+ }
+ ]
+ },
+ {
+ "Id": "6.2.8",
+ "Description": "Ensure That 'cloudsql.enable_pgaudit' Database Flag for each Cloud Sql Postgresql Instance Is Set to 'on' For Centralized Logging",
+ "Checks": [
+ "cloudsql_instance_postgres_enable_pgaudit_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.2 PostgreSQL Database",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure `cloudsql.enable_pgaudit` database flag for Cloud SQL PostgreSQL instance is set to `on` to allow for centralized logging.",
+ "RationaleStatement": "As numerous other recommendations in this section consist of turning on flags for logging purposes, your organization will need a way to manage these logs. You may have a solution already in place. If you do not, consider installing and enabling the open source pgaudit extension within PostgreSQL and enabling its corresponding flag of `cloudsql.enable_pgaudit`. This flag and installing the extension enables database auditing in PostgreSQL through the open-source pgAudit extension. This extension provides detailed session and object logging to comply with government, financial, & ISO standards and provides auditing capabilities to mitigate threats by monitoring security events on the instance. Enabling the flag and settings later in this recommendation will send these logs to Google Logs Explorer so that you can access them in a central location. to This recommendation is applicable only to PostgreSQL database instances.",
+ "ImpactStatement": "Enabling the pgAudit extension can lead to increased data storage requirements and to ensure durability of pgAudit log records in the event of unexpected storage issues, it is recommended to enable the `Enable automatic storage increases` setting on the instance. Enabling flags via the command line will also overwrite all existing flags, so you should apply all needed flags in the CLI command. Also flags may require a restart of the server to be implemented or will break existing functionality so update your servers at a time of low usage.",
+ "RemediationProcedure": "**Initialize the pgAudit flag** **From Google Cloud Console** 1. Go to [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Overview` page. 3. Click `Edit`. 4. Scroll down and expand `Flags`. 5. To set a flag that has not been set on the instance before, click `Add item`. 6. Enter `cloudsql.enable_pgaudit` for the flag name and set the flag to `on`. 7. Click `Done`. 8. Click `Save` to update the configuration. 9. Confirm your changes under `Flags` on the `Overview` page. **From Google Cloud CLI** Run the below command by providing `<INSTANCE_NAME>` to enable `cloudsql.enable_pgaudit` flag. gcloud sql instances patch <INSTANCE_NAME> --database-flags cloudsql.enable_pgaudit=on Note: `RESTART` is required to get this configuration in effect. **Creating the extension** 1. Connect to the the server running PostgreSQL or through a SQL client of your choice. 2. Run the following command as a superuser. CREATE EXTENSION pgaudit; **Updating the previously created pgaudit.log flag for your Logging Needs** **From Console:** Note: there are multiple options here. This command will enable logging for all databases on a server. Please see the customizing database audit logging reference for more flag options. 1. Go to [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Overview` page. 3. Click `Edit`. 4. Scroll down and expand `Flags`. 5. To set a flag that has not been set on the instance before, click `Add item`. 6. Enter `pgaudit.log=all` for the flag name and set the flag to `on`. 7. Click `Done`. 8. Click `Save` to update the configuration. 9. Confirm your changes under `Flags` on the `Overview` page. **From Command Line:** Run the command gcloud sql instances patch <INSTANCE_NAME> --database-flags cloudsql.enable_pgaudit=on,pgaudit.log=all **Determine if logs are being sent to Logs Explorer** 1. From the Google Console home page, open the hamburger menu in the top left. 2. In the menu that pops open, scroll down to Logs Explorer under Operations. 3. In the query box, paste the following and search resource.type=cloudsql_database logName=projects/<your-project-name>/logs/cloudaudit.googleapis.com%2Fdata_access protoPayload.request.@type=type.googleapis.com/google.cloud.sql.audit.v1.PgAuditEntry If it returns any log sources, they are correctly setup.",
+ "AuditProcedure": "**Determining if the pgAudit Flag is set to 'on'** **From Google Cloud Console** 1. Go to [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Overview` page. 3. Click `Edit`. 4. Scroll down and expand `Flags`. 5. Ensure that `cloudsql.enable_pgaudit` flag is set to `on`. **From Google Cloud CLI** Run the command by providing `<INSTANCE_NAME>`. Ensure the value of the flag is `on`. gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings|.|.databaseFlags[]|select(.name==cloudsql.enable_pgaudit)|.value' **Determine if the pgAudit extension is installed** 1. Connect to the the server running PostgreSQL or through a SQL client of your choice. 2. Run the following command SELECT * FROM pg_extension; 3. If pgAudit is in this list. If so, it is installed. **Determine if Data Access Audit logs are enabled for your project and have sufficient privileges** 1. From the homepage open the hamburger menu in the top left. 2. Scroll down to `IAM & Admin`and hover over it. 3. In the menu that opens up, select `Audit Logs` 4. In the middle of the page, in the search box next to `filter` search for `Cloud Composer API` 5. Select it, and ensure that both 'Admin Read' and 'Data Read' are checked. **Determine if logs are being sent to Logs Explorer** 1. From the Google Console home page, open the hamburger menu in the top left. 2. In the menu that pops open, scroll down to Logs Explorer under Operations. 3. In the query box, paste the following and search resource.type=cloudsql_database logName=projects/<your-project-name>/logs/cloudaudit.googleapis.com%2Fdata_access protoPayload.request.@type=type.googleapis.com/google.cloud.sql.audit.v1.PgAuditEntry 4. If it returns any log sources, they are correctly setup.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted. Note: Configuring the 'cloudsql.enable_pgaudit' database flag requires restarting the Cloud SQL PostgreSQL instance.",
+ "References": "https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres:https://cloud.google.com/sql/docs/postgres/pg-audit#enable-auditing-flag:https://cloud.google.com/sql/docs/postgres/pg-audit#customizing-database-audit-logging:https://cloud.google.com/logging/docs/audit/configure-data-access#config-console-enable",
+ "DefaultValue": "By default `cloudsql.enable_pgaudit` database flag is set to `off` and the extension is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "6.3.1",
+ "Description": "Ensure 'external scripts enabled' Database Flag for Cloud SQL SQL Server Instance Is Set to 'off'",
+ "Checks": [
+ "cloudsql_instance_sqlserver_external_scripts_enabled_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.3 SQL Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set `external scripts enabled` database flag for Cloud SQL SQL Server instance to `off`",
+ "RationaleStatement": "`external scripts enabled` enable the execution of scripts with certain remote language extensions. This property is OFF by default. When Advanced Analytics Services is installed, setup can optionally set this property to true. As the External Scripts Enabled feature allows scripts external to SQL such as files located in an R library to be executed, which could adversely affect the security of the system, hence this should be disabled. This recommendation is applicable to SQL Server database instances.",
+ "ImpactStatement": "Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `external scripts enabled` from the drop-down menu, and set its value to `off`. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `external scripts enabled` database flag for every Cloud SQL SQL Server database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags external scripts enabled=off **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `external scripts enabled` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. Ensure the below command returns `off` for every Cloud SQL SQL Server database instance gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==external scripts enabled)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag restarts the Cloud SQL instance.",
+ "References": "https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/external-scripts-enabled-server-configuration-option?view=sql-server-ver15:https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/advanced-analytics/concepts/security?view=sql-server-ver15:https://www.stigviewer.com/stig/ms_sql_server_2016_instance/2018-03-09/finding/V-79347",
+ "DefaultValue": "By default `external scripts enabled` is `off`"
+ }
+ ]
+ },
+ {
+ "Id": "6.3.2",
+ "Description": "Ensure 'cross db ownership chaining' Database Flag for Cloud SQL SQL Server Instance Is Set to 'off'",
+ "Checks": [
+ "cloudsql_instance_sqlserver_cross_db_ownership_chaining_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.3 SQL Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set `cross db ownership chaining` database flag for Cloud SQL SQL Server instance to `off`. This flag is deprecated for all SQL Server versions in CGP. Going forward, you can't set its value to on. However, if you have this flag enabled, we strongly recommend that you either remove the flag from your database or set it to off. For cross-database access, use the [Microsoft tutorial for signing stored procedures with a certificate](https://learn.microsoft.com/en-us/sql/relational-databases/tutorial-signing-stored-procedures-with-a-certificate?view=sql-server-ver16).",
+ "RationaleStatement": "Use the `cross db ownership` for chaining option to configure cross-database ownership chaining for an instance of Microsoft SQL Server. This server option allows you to control cross-database ownership chaining at the database level or to allow cross-database ownership chaining for all databases. Enabling `cross db ownership` is not recommended unless all of the databases hosted by the instance of SQL Server must participate in cross-database ownership chaining and you are aware of the security implications of this setting. This recommendation is applicable to SQL Server database instances.",
+ "ImpactStatement": "Updating flags may cause the database to restart. This may cause it to unavailable for a short amount of time, so this is best done at a time of low usage. You should also determine if the tables in your databases reference another table without using credentials for that database, as turning off cross database ownership will break this relationship.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `cross db ownership chaining` from the drop-down menu, and set its value to `off`. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `cross db ownership chaining` database flag for every Cloud SQL SQL Server database instance using the below command: gcloud sql instances patch <INSTANCE_NAME> --database-flags cross db ownership chaining=off **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**NOTE:** This flag is deprecated for all SQL Server versions. Going forward, you can't set its value to on. However, if you have this flag enabled it should be removed from your database or set to off. **From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console. 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `cross db ownership chaining` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. Ensure the below command returns `off` for every Cloud SQL SQL Server database instance: gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==cross db ownership chaining)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not restart the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/cross-db-ownership-chaining-server-configuration-option?view=sql-server-ver15",
+ "DefaultValue": "This flag is deprecated for all SQL Server versions. Going forward, you can't set its value to on."
+ }
+ ]
+ },
+ {
+ "Id": "6.3.3",
+ "Description": "Ensure 'user Connections' Database Flag for Cloud SQL SQL Server Instance Is Set to a Non-limiting Value",
+ "Checks": [
+ "cloudsql_instance_sqlserver_user_connections_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.3 SQL Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to check the `user connections` for a Cloud SQL SQL Server instance to ensure that it is not artificially limiting connections.",
+ "RationaleStatement": "The `user connections` option specifies the maximum number of simultaneous user connections that are allowed on an instance of SQL Server. The actual number of user connections allowed also depends on the version of SQL Server that you are using, and also the limits of your application or applications and hardware. SQL Server allows a maximum of 32,767 user connections. Because user connections is by default a self-configuring value, with SQL Server adjusting the maximum number of user connections automatically as needed, up to the maximum value allowable. For example, if only 10 users are logged in, 10 user connection objects are allocated. In most cases, you do not have to change the value for this option. The default is 0, which means that the maximum (32,767) user connections are allowed. However if there is a number defined here that limits connections, SQL Server will not allow anymore above this limit. If the connections are at the limit, any new requests will be dropped, potentially causing lost data or outages for those using the database.",
+ "ImpactStatement": "Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `user connections` from the drop-down menu, and set its value to your organization recommended value. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `user connections` database flag for every Cloud SQL SQL Server database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags user connections=[0-32,767] **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `user connections` listed under the `Database flags` section is 0. **From Google Cloud CLI** 1. Ensure the below command returns a value of 0, for every Cloud SQL SQL Server database instance. gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==user connections)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag restarts the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-user-connections-server-configuration-option?view=sql-server-ver15:https://www.stigviewer.com/stig/ms_sql_server_2016_instance/2018-03-09/finding/V-79119",
+ "DefaultValue": "By default `user connections` is set to '0' which does not limit the number of connections, giving the server free reign to facilitate a max of 32,767 connections."
+ }
+ ]
+ },
+ {
+ "Id": "6.3.4",
+ "Description": "Ensure 'user options' Database Flag for Cloud SQL SQL Server Instance Is Not Configured",
+ "Checks": [
+ "cloudsql_instance_sqlserver_user_options_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.3 SQL Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The `user options` option specifies global defaults for all users. A list of default query processing options is established for the duration of a user's work session. The user options option allows you to change the default values of the SET options (if the server's default settings are not appropriate). A user can override these defaults by using the SET statement. You can configure user options dynamically for new logins. After you change the setting of user options, new login sessions use the new setting; current login sessions are not affected. This recommendation is applicable to SQL Server database instances.",
+ "RationaleStatement": "It is recommended that, `user options` database flag for Cloud SQL SQL Server instance should not be configured. A user can override these defaults set with `user options` by using the SET statement. Some of these features/options could adversely affect the security of the system if enabled.",
+ "ImpactStatement": "Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. Click the X next `user options` flag shown 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. List all Cloud SQL database Instances gcloud sql instances list 2. Clear the `user options` database flag for every Cloud SQL SQL Server database instance using either of the below commands. Clearing all flags to their default value gcloud sql instances patch <INSTANCE_NAME> --clear-database-flags OR To clear only `user options` database flag, configure the database flag by overriding the `user options`. Exclude `user options` flag and its value, and keep all other flags you want to configure. gcloud sql instances patch <INSTANCE_NAME> --database-flags [FLAG1=VALUE1,FLAG2=VALUE2] **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `user options` that has been set is not listed under the `Database flags` section. **From Google Cloud CLI** 1. Ensure the below command returns empty result for every Cloud SQL SQL Server database instance gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==user options)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not restart the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-user-options-server-configuration-option?view=sql-server-ver15:https://www.stigviewer.com/stig/ms_sql_server_2016_instance/2018-03-09/finding/V-79335",
+ "DefaultValue": "By default 'user options' is not configured."
+ }
+ ]
+ },
+ {
+ "Id": "6.3.5",
+ "Description": "Ensure 'remote access' Database Flag for Cloud SQL SQL Server Instance Is Set to 'off'",
+ "Checks": [
+ "cloudsql_instance_sqlserver_remote_access_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "SubSection": "6.3 SQL Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set `remote access` database flag for Cloud SQL SQL Server instance to `off`.",
+ "RationaleStatement": "The `remote access` option controls the execution of stored procedures from local or remote servers on which instances of SQL Server are running. This default value for this option is 1. This grants permission to run local stored procedures from remote servers or remote stored procedures from the local server. To prevent local stored procedures from being run from a remote server or remote stored procedures from being run on the local server, this must be disabled. The Remote Access option controls the execution of local stored procedures on remote servers or remote stored procedures on local server. 'Remote access' functionality can be abused to launch a Denial-of-Service (DoS) attack on remote servers by off-loading query processing to a target, hence this should be disabled. This recommendation is applicable to SQL Server database instances.",
+ "ImpactStatement": "Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `remote access` from the drop-down menu, and set its value to `off`. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `remote access` database flag for every Cloud SQL SQL Server database instance using the below command gcloud sql instances patch <INSTANCE_NAME> --database-flags remote access=off **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `remote access` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. Ensure the below command returns `off` for every Cloud SQL SQL Server database instance gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==remote access)|.value' In the output, database flags are listed under the `settings` as the collection `databaseFlags`.",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag restarts the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-remote-access-server-configuration-option?view=sql-server-ver15:https://www.stigviewer.com/stig/ms_sql_server_2016_instance/2018-03-09/finding/V-79337",
+ "DefaultValue": "By default 'remote access' is 'on'."
+ }
+ ]
+ },
+ {
+ "Id": "6.3.6",
+ "Description": "Ensure '3625 (trace flag)' Database Flag for all Cloud SQL SQL Server Instances Is Set to 'on'",
+ "Checks": [
+ "cloudsql_instance_sqlserver_trace_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to set `3625 (trace flag)` database flag for Cloud SQL SQL Server instance to `on`.",
+ "RationaleStatement": "Microsoft SQL Trace Flags are frequently used to diagnose performance issues or to debug stored procedures or complex computer systems, but they may also be recommended by Microsoft Support to address behavior that is negatively impacting a specific workload. All documented trace flags and those recommended by Microsoft Support are fully supported in a production environment when used as directed. `3625(trace log)` Limits the amount of information returned to users who are not members of the sysadmin fixed server role, by masking the parameters of some error messages using '******'. Setting this in a Google Cloud flag for the instance allows for security through obscurity and prevents the disclosure of sensitive information, hence this is recommended to set this flag globally to on to prevent the flag having been left off, or changed by bad actors. This recommendation is applicable to SQL Server database instances.",
+ "ImpactStatement": "Changing flags on a database may cause it to be restarted. The best time to do this is at a time where there is low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. To set a flag that has not been set on the instance before, click `Add item`, choose the flag `3625` from the drop-down menu, and set its value to `on`. 6. Click `Save` to save your changes. 7. Confirm your changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. Configure the `3625` database flag for every Cloud SQL SQL Server database instance using the below command. gcloud sql instances patch <INSTANCE_NAME> --database-flags 3625=on **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Ensure the database flag `3625` that has been set is listed under the `Database flags` section. **From Google Cloud CLI** 1. Ensure the below command returns `on` for every Cloud SQL SQL Server database instance gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==3625)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag restarts the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql?view=sql-server-ver15#trace-flags:https://github.com/ktaranov/sqlserver-kit/blob/master/SQL%20Server%20Trace%20Flag.md",
+ "DefaultValue": "MS SQL Server implementations by default have trace flags, including the '3625' flag, turned off, as they are used for logging purposes.",
+ "SubSection": "6.3 SQL Server"
+ }
+ ]
+ },
+ {
+ "Id": "6.3.7",
+ "Description": "Ensure 'contained database authentication' Database Flag for Cloud SQL SQL Server Instance Is Set to 'off'",
+ "Checks": [
+ "cloudsql_instance_sqlserver_contained_database_authentication_flag"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "A contained database includes all database settings and metadata required to define the database and has no configuration dependencies on the instance of the Database Engine where the database is installed. Users can connect to the database without authenticating a login at the Database Engine level. Isolating the database from the Database Engine makes it possible to easily move the database to another instance of SQL Server. Contained databases have some unique threats that should be understood and mitigated by SQL Server Database Engine administrators. Most of the threats are related to the USER WITH PASSWORD authentication process, which moves the authentication boundary from the Database Engine level to the database level, hence this is recommended not to enable this flag. This recommendation is applicable to SQL Server database instances.",
+ "RationaleStatement": "When contained databases are enabled, database users with the ALTER ANY USER permission, such as members of the db_owner and db_accessadmin database roles, can grant access to databases and by doing so, grant access to the instance of SQL Server. This means that control over access to the server is no longer limited to members of the sysadmin and securityadmin fixed server role, and logins with the server level CONTROL SERVER and ALTER ANY LOGIN permission. It is recommended to set `contained database authentication` database flag for Cloud SQL on the SQL Server instance to `off`.",
+ "ImpactStatement": "When `contained database authentication` is off (0) for the instance, contained databases cannot be created, or attached to the Database Engine. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the SQL Server instance for which you want to enable to database flag. 3. Click `Edit`. 4. Scroll down to the `Flags` section. 5. If the flag `contained database authentication` is present and its value is set to 'on', then change it to 'off'. 6. Click `Save`. 7. Confirm the changes under `Flags` on the Overview page. **From Google Cloud CLI** 1. If any Cloud SQL for SQL Server instance has the database flag `contained database authentication` set to 'on', then change it to 'off' using the below command: gcloud sql instances patch <INSTANCE_NAME> --database-flags contained database authentication=off **Note**: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance to open its `Instance Overview` page 3. Under the 'Database flags' section, if the database flag `contained database authentication` is present, then ensure that it is set to 'off'. **From Google Cloud CLI** 1. Ensure the below command returns `off` for any Cloud SQL for SQL Server database instance. gcloud sql instances describe <INSTANCE_NAME> --format=json | jq '.settings.databaseFlags[] | select(.name==contained database authentication)|.value' ",
+ "AdditionalInformation": "WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/sqlserver/flags - to see if your instance will be restarted when this patch is submitted. **Note**: Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines. **Note**: Configuring the above flag does not restart the Cloud SQL instance.",
+ "References": "https://cloud.google.com/sql/docs/sqlserver/flags:https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/contained-database-authentication-server-configuration-option?view=sql-server-ver15:https://docs.microsoft.com/en-us/sql/relational-databases/databases/security-best-practices-with-contained-databases?view=sql-server-ver15",
+ "DefaultValue": "",
+ "SubSection": "6.3 SQL Server"
+ }
+ ]
+ },
+ {
+ "Id": "6.4",
+ "Description": "Ensure That the Cloud SQL Database Instance Requires All Incoming Connections To Use SSL",
+ "Checks": [
+ "cloudsql_instance_ssl_connections"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to enforce all incoming connections to SQL database instance to use SSL.",
+ "RationaleStatement": "SQL database connections if successfully trapped (MITM); can reveal sensitive data like credentials, database queries, query outputs etc. For security, it is recommended to always use SSL encryption when connecting to your instance. This recommendation is applicable for Postgresql, MySql generation 1, MySql generation 2 and SQL Server 2017 instances.",
+ "ImpactStatement": "After enforcing SSL requirement for connections, existing client will not be able to communicate with Cloud SQL database instance unless they use SSL encrypted connections to communicate to Cloud SQL database instance.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Click on an instance name to see its configuration overview. 3. In the left-side panel, select `Connections`. 3. In the `security` section, select SSL mode as `Allow only SSL connections`. 4. Under `Configure SSL server certificates` click `Create new certificate` and save the setting **From Google Cloud CLI** To enforce SSL encryption for an instance run the command: gcloud sql instances patch INSTANCE_NAME --ssl-mode= ENCRYPTED_ONLY Note: `RESTART` is required for type MySQL Generation 1 Instances (`backendType: FIRST_GEN`) to get this configuration in effect.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Click on an instance name to see its configuration overview. 3. In the left-side panel, select `Connections`. 3. In the `Security` section, ensure that `Allow only SSL connections` option is selected. **From Google Cloud CLI** 1. Get the detailed configuration for every SQL database instance using the following command: gcloud sql instances list --format=json Ensure that section `settings: ipConfiguration` has the parameter `sslMode` set to `ENCRYPTED_ONLY `.",
+ "AdditionalInformation": "By default `Settings: ipConfiguration` has no `authorizedNetworks` set/configured. In that case even if by default `sslMode` is not set, which is equivalent to `sslMode:ALLOW_UNENCRYPTED_AND_ENCRYPTED ` there is no risk as instance cannot be accessed outside of the network unless `authorizedNetworks` are configured. However, If default for `sslMode` is not updated to `ENCRYPTED_ONLY ` any `authorizedNetworks` created later on will not enforce SSL only connection.",
+ "References": "https://cloud.google.com/sql/docs/postgres/configure-ssl-instance/",
+ "DefaultValue": "By default parameter `settings: ipConfiguration: sslMode` is not set which is equivalent to `sslMode:ALLOW_UNENCRYPTED_AND_ENCRYPTED`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "6.5",
+ "Description": "Ensure That Cloud SQL Database Instances Do Not Implicitly Whitelist All Public IP Addresses",
+ "Checks": [
+ "cloudsql_instance_public_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Database Server should accept connections only from trusted Network(s)/IP(s) and restrict access from public IP addresses.",
+ "RationaleStatement": "To minimize attack surface on a Database server instance, only trusted/known and required IP(s) should be white-listed to connect to it. An authorized network should not have IPs/networks configured to `0.0.0.0/0` which will allow access to the instance from anywhere in the world. Note that authorized networks apply only to instances with public IPs.",
+ "ImpactStatement": "The Cloud SQL database instance would not be available to public IP addresses.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Click the instance name to open its `Instance details` page. 3. Under the `Configuration` section click `Edit configurations` 4. Under `Configuration options` expand the `Connectivity` section. 5. Click the `delete` icon for the authorized network `0.0.0.0/0`. 6. Click `Save` to update the instance. **From Google Cloud CLI** Update the authorized network list by dropping off any addresses. gcloud sql instances patch <INSTANCE_NAME> --authorized-networks=IP_ADDR1,IP_ADDR2... **Prevention:** To prevent new SQL instances from being configured to accept incoming connections from any IP addresses, set up a `Restrict Authorized Networks on Cloud SQL instances` Organization Policy at: [https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictAuthorizedNetworks](https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictAuthorizedNetworks).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Click the instance name to open its `Instance details` page. 3. Under the `Configuration` section click `Edit configurations` 4. Under `Configuration options` expand the `Connectivity` section. 5. Ensure that no authorized network is configured to allow `0.0.0.0/0`. **From Google Cloud CLI** 1. Get detailed configuration for every Cloud SQL database instance. gcloud sql instances list --format=json Ensure that the section `settings: ipConfiguration : authorizedNetworks` does not have any parameter `value` containing `0.0.0.0/0`.",
+ "AdditionalInformation": "There is no IPv6 configuration found for Google cloud SQL server services.",
+ "References": "https://cloud.google.com/sql/docs/mysql/configure-ip:https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictAuthorizedNetworks:https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints:https://cloud.google.com/sql/docs/mysql/connection-org-policy",
+ "DefaultValue": "By default, authorized networks are not configured. Remote connection to Cloud SQL database instance is not possible unless authorized networks are configured.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "6.6",
+ "Description": "Ensure Cloud SQL Database Instances Have IAM Database Authentication Enabled",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "It is recommended to enable IAM database authentication for Cloud SQL instances (PostgreSQL and MySQL) to eliminate static password-based authentication and instead use short-lived IAM tokens for database access. When enabled, database users can be created that authenticate via IAM, and connections use automatically-generated, short-lived tokens instead of static passwords. This recommendation is applicable to Cloud SQL for PostgreSQL and Cloud SQL for MySQL instances. Cloud SQL for SQL Server does not support IAM database authentication.",
+ "RationaleStatement": "IAM database authentication eliminates static database passwords by using short-lived IAM tokens for database access. This provides automatic credential rotation, centralized access control through Cloud IAM, and immediate revocation capabilities without password distribution across applications. Database access is correlated with GCP IAM principals in Cloud Logging, enabling better audit trails and attribution of database queries to specific service accounts or users. This recommendation is applicable to Cloud SQL for PostgreSQL and MySQL instances.",
+ "ImpactStatement": "Enabling IAM database authentication may require application changes, including updating connection methods and replacing password-based database users with IAM principals. Existing users and scripts that depend on static credentials may need to be reworked, and rollout should be coordinated carefully to avoid service disruption.",
+ "AuditProcedure": "**From Google Cloud CLI**\n\n1. List all Cloud SQL instances: `gcloud sql instances list`.\n2. For every PostgreSQL instance, verify the IAM authentication flag is enabled: `gcloud sql instances describe <INSTANCE_NAME> --format=\"json\" | jq '.settings.databaseFlags[] | select(.name==\"cloudsql.iam_authentication\")'`. It should return value `on`.\n3. For every MySQL instance, verify the flag `cloudsql_iam_authentication` is set to `on`. If the command returns no output, the flag is not set.",
+ "RemediationProcedure": "**From Google Cloud CLI**\n\n1. For PostgreSQL instances, enable IAM authentication: `gcloud sql instances patch <INSTANCE_NAME> --database-flags=cloudsql.iam_authentication=on`. For MySQL instances, use `cloudsql_iam_authentication=on`. Note: patching database flags overwrites previously set flags, so include all required flags.\n2. Create database users configured for IAM authentication using `gcloud sql users create ... --type=CLOUD_IAM_USER` (or `CLOUD_IAM_SERVICE_ACCOUNT`).\n3. Grant the necessary privileges to the database users via SQL GRANT commands.\n4. Ensure IAM principals have the roles `roles/cloudsql.client` and `roles/cloudsql.instanceUser`.\n5. Test the configuration by connecting using IAM authentication via the Cloud SQL Proxy.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, IAM database authentication is not enabled on Cloud SQL instances."
+ }
+ ]
+ },
+ {
+ "Id": "6.7",
+ "Description": "Ensure That Cloud SQL Database Instances Do Not Have Public IPs",
+ "Checks": [
+ "cloudsql_instance_public_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to configure Second Generation Sql instance to use private IPs instead of public IPs.",
+ "RationaleStatement": "To lower the organization's attack surface, Cloud SQL databases should not have public IPs. Private IPs provide improved network security and lower latency for your application.",
+ "ImpactStatement": "Removing the public IP address on SQL instances may break some applications that relied on it for database connectivity.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console: [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances) 2. Click the instance name to open its Instance details page. 3. Select the `Connections` tab. 4. Deselect the `Public IP` checkbox. 5. Click `Save` to update the instance. **From Google Cloud CLI** 1. For every instance remove its public IP and assign a private IP instead: gcloud sql instances patch <INSTANCE_NAME> --network=<VPC_NETWORK_NAME> --no-assign-ip 2. Confirm the changes using the following command:: gcloud sql instances describe <INSTANCE_NAME> **Prevention:** To prevent new SQL instances from getting configured with public IP addresses, set up a `Restrict Public IP access on Cloud SQL instances` Organization policy at: [https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictPublicIp](https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictPublicIp).",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console: [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances) 2. Ensure that every instance has a private IP address and no public IP address configured. **From Google Cloud CLI** 1. List all Cloud SQL database instances using the following command: gcloud sql instances list 2. For every instance of type `instanceType: CLOUD_SQL_INSTANCE` with `backendType: SECOND_GEN`, get detailed configuration. Ignore instances of type `READ_REPLICA_INSTANCE` because these instances inherit their settings from the primary instance. Also, note that first generation instances cannot be configured to have a private IP address. gcloud sql instances describe <INSTANCE_NAME> 3. Ensure that the setting `ipAddresses` has an IP address configured of `type: PRIVATE` and has no IP address of `type: PRIMARY`. `PRIMARY` IP addresses are public addresses. An instance can have both a private and public address at the same time. Note also that you cannot use private IP with First Generation instances.",
+ "AdditionalInformation": "Replicas inherit their private IP status from their primary instance. You cannot configure a private IP directly on a replica.",
+ "References": "https://cloud.google.com/sql/docs/mysql/configure-private-ip:https://cloud.google.com/sql/docs/mysql/private-ip:https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints:https://console.cloud.google.com/iam-admin/orgpolicies/sql-restrictPublicIp",
+ "DefaultValue": "By default, Cloud Sql instances have a public IP.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "6.8",
+ "Description": "Ensure That Cloud SQL Database Instances Are Configured With Automated Backups",
+ "Checks": [
+ "cloudsql_instance_automated_backups"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended to have all SQL database instances set to enable automated backups.",
+ "RationaleStatement": "Backups provide a way to restore a Cloud SQL instance to recover lost data or recover from a problem with that instance. Automated backups need to be set for any instance that contains data that should be protected from loss or damage. This recommendation is applicable for SQL Server, PostgreSql, MySql generation 1 and MySql generation 2 instances.",
+ "ImpactStatement": "Automated Backups will increase required size of storage and costs associated with it.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Select the instance where the backups need to be configured. 3. Click `Edit`. 4. In the `Backups` section, check `Enable automated backups', and choose a backup window. 5. Click `Save`. **From Google Cloud CLI** 1. List all Cloud SQL database instances using the following command: gcloud sql instances list --format=json | jq '. | map(select(.instanceType != READ_REPLICA_INSTANCE)) | .[].name' NOTE: gcloud command has been added with the filter to exclude read-replicas instances, as GCP do not provide Automated Backups for read-replica instances. 2. Enable `Automated backups` for every Cloud SQL database instance using the below command: gcloud sql instances patch <INSTANCE_NAME> --backup-start-time <[HH:MM]> The `backup-start-time` parameter is specified in 24-hour time, in the UTC±00 time zone, and specifies the start of a 4-hour backup window. Backups can start any time during the backup window.",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting [https://console.cloud.google.com/sql/instances](https://console.cloud.google.com/sql/instances). 2. Click the instance name to open its instance details page. 3. Go to the `Backups` menu. 4. Ensure that `Automated backups` is set to `Enabled` and `Backup time` is mentioned. **From Google Cloud CLI** 1. List all Cloud SQL database instances using the following command: gcloud sql instances list --format=json | jq '. | map(select(.instanceType != READ_REPLICA_INSTANCE)) | .[].name' NOTE: gcloud command has been added with the filter to exclude read-replicas instances, as GCP do not provide Automated Backups for read-replica instances. 2. Ensure that the below command returns `True` for every Cloud SQL database instance. gcloud sql instances describe <INSTANCE_NAME> --format=value('Enabled':settings.backupConfiguration.enabled) ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/sql/docs/mysql/backup-recovery/backups:https://cloud.google.com/sql/docs/postgres/backup-recovery/backups:https://cloud.google.com/sql/docs/sqlserver/backup-recovery/backups:https://cloud.google.com/sql/docs/mysql/backup-recovery/backing-up:https://cloud.google.com/sql/docs/postgres/backup-recovery/backing-up:https://cloud.google.com/sql/docs/sqlserver/backup-recovery/backing-up",
+ "DefaultValue": "By default, automated backups are not configured for Cloud SQL instances.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "6.9",
+ "Description": "Ensure Cloud SQL Database Instances Have Deletion Protection Enabled",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Cloud SQL Database Services",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that deletion protection is enabled on all Cloud SQL database instances to prevent accidental or unauthorized deletion. This setting safeguards critical databases by requiring explicit disabling of deletion protection before deletion, reducing the risk of data loss through human error or malicious activity.",
+ "RationaleStatement": "Cloud SQL instances without deletion protection can be permanently deleted with a single API call or console action, allowing compromised credentials, operational errors, or malicious insiders to cause catastrophic data loss. Deletion protection provides a critical safeguard against inadvertent or malicious deletion of production databases. By requiring deliberate action to disable deletion protection before an instance can be deleted, organizations mitigate risks associated with accidental data deletion and enhance the overall resilience of their data storage platform. This control is particularly important for production workloads where data loss could result in significant business disruption, regulatory compliance violations, and reputational damage.",
+ "ImpactStatement": "There is no performance impact to enabling deletion protection on Cloud SQL instances. The setting only affects delete operations. Administrators will need to explicitly disable deletion protection before deleting an instance, adding an additional step to the deletion workflow.",
+ "AuditProcedure": "**From Google Cloud CLI**\n\n1. List all Cloud SQL database instances to identify those without deletion protection: `gcloud sql instances list --format=\"table(name,settings.deletionProtectionEnabled)\"`.\n2. For each instance, verify deletion protection is enabled: `gcloud sql instances describe <INSTANCE_NAME> --format=\"value(settings.deletionProtectionEnabled)\"`. The command should return `True`. If it returns `False` or empty, deletion protection is not enabled.",
+ "RemediationProcedure": "**From Google Cloud CLI**\n\n1. To enable deletion protection on an existing Cloud SQL instance: `gcloud sql instances patch <INSTANCE_NAME> --deletion-protection`.\n2. To enable deletion protection when creating a new Cloud SQL instance, include the `--deletion-protection` flag in the `gcloud sql instances create` command.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, deletion protection is not enabled on Cloud SQL database instances."
+ }
+ ]
+ },
+ {
+ "Id": "7.1",
+ "Description": "Ensure That BigQuery Datasets Are Not Anonymously or Publicly Accessible",
+ "Checks": [
+ "bigquery_dataset_public_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 BigQuery",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "It is recommended that the IAM policy on BigQuery datasets does not allow anonymous and/or public access.",
+ "RationaleStatement": "Granting permissions to `allUsers` or `allAuthenticatedUsers` allows anyone to access the dataset. Such access might not be desirable if sensitive data is being stored in the dataset. Therefore, ensure that anonymous and/or public access to a dataset is not allowed.",
+ "ImpactStatement": "The dataset is not publicly accessible. Explicit modification of IAM privileges would be necessary to make them publicly accessible.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Go to `BigQuery` by visiting: [https://console.cloud.google.com/bigquery](https://console.cloud.google.com/bigquery). 2. Select the dataset from 'Resources'. 3. Click `SHARING` near the right side of the window and select `Permissions`. 4. Review each attached role. 5. Click the delete icon for each member `allUsers` or `allAuthenticatedUsers`. On the popup click `Remove`. **From Google Cloud CLI** List the name of all datasets. bq ls Retrieve the data set details: bq show --format=prettyjson PROJECT_ID:DATASET_NAME > PATH_TO_FILE In the access section of the JSON file, update the dataset information to remove all roles containing `allUsers` or `allAuthenticatedUsers`. Update the dataset: bq update --source PATH_TO_FILE PROJECT_ID:DATASET_NAME **Prevention:** You can prevent Bigquery dataset from becoming publicly accessible by setting up the `Domain restricted sharing` organization policy at: https://console.cloud.google.com/iam-admin/orgpolicies/iam-allowedPolicyMemberDomains .",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `BigQuery` by visiting: [https://console.cloud.google.com/bigquery](https://console.cloud.google.com/bigquery). 2. Select a dataset from `Resources`. 3. Click `SHARING` near the right side of the window and select `Permissions`. 4. Validate that none of the attached roles contain `allUsers` or `allAuthenticatedUsers`. **From Google Cloud CLI** List the name of all datasets. bq ls Retrieve each dataset details using the following command: bq show PROJECT_ID:DATASET_NAME Ensure that `allUsers` and `allAuthenticatedUsers` have not been granted access to the dataset.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/bigquery/docs/dataset-access-controls",
+ "DefaultValue": "By default, BigQuery datasets are not publicly accessible.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "7.2",
+ "Description": "Ensure That All BigQuery Tables Are Encrypted With Customer-Managed Encryption Key (CMEK)",
+ "Checks": [
+ "bigquery_table_cmk_encryption"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 BigQuery",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "BigQuery by default encrypts the data as rest by employing `Envelope Encryption` using Google managed cryptographic keys. The data is encrypted using the `data encryption keys` and data encryption keys themselves are further encrypted using `key encryption keys`. This is seamless and do not require any additional input from the user. However, if you want to have greater control, Customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery Data Sets. If CMEK is used, the CMEK is used to encrypt the data encryption keys instead of using google-managed encryption keys.",
+ "RationaleStatement": "BigQuery by default encrypts the data as rest by employing `Envelope Encryption` using Google managed cryptographic keys. This is seamless and does not require any additional input from the user. For greater control over the encryption, customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery tables. The CMEK is used to encrypt the data encryption keys instead of using google-managed encryption keys. BigQuery stores the table and CMEK association and the encryption/decryption is done automatically. Applying the Default Customer-managed keys on BigQuery data sets ensures that all the new tables created in the future will be encrypted using CMEK but existing tables need to be updated to use CMEK individually. Note: Google does not store your keys on its servers and cannot access your protected data unless you provide the key. This also means that if you forget or lose your key, there is no way for Google to recover the key or to recover any data encrypted with the lost key. ",
+ "ImpactStatement": "Using Customer-managed encryption keys (CMEK) will incur additional labor-hour investment to create, protect, and manage the keys.",
+ "RemediationProcedure": "**From Google Cloud CLI** Use the following command to copy the data. The source and the destination needs to be same in case copying to the original table. bq cp --destination_kms_key <customer_managed_key> source_dataset.source_table destination_dataset.destination_table ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Analytics` 2. Go to `BigQuery` 3. Under `SQL Workspace`, select the project 4. Select Data Set, select the table 5. Go to `Details` tab 6. Under `Table info`, verify `Customer-managed key` is present. 7. Repeat for each table in all data sets for all projects. **From Google Cloud CLI** List all dataset names bq ls Use the following command to view the table details. Verify the `kmsKeyName` is present. bq show <table_object> ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/bigquery/docs/customer-managed-encryption",
+ "DefaultValue": "Google Managed keys are used as `key encryption keys`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "7.3",
+ "Description": "Ensure That a Default Customer-Managed Encryption Key (CMEK) Is Specified for All BigQuery Data Sets",
+ "Checks": [
+ "bigquery_dataset_cmk_encryption"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 BigQuery",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "BigQuery by default encrypts the data as rest by employing `Envelope Encryption` using Google managed cryptographic keys. The data is encrypted using the `data encryption keys` and data encryption keys themselves are further encrypted using `key encryption keys`. This is seamless and do not require any additional input from the user. However, if you want to have greater control, Customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery Data Sets.",
+ "RationaleStatement": "BigQuery by default encrypts the data as rest by employing `Envelope Encryption` using Google managed cryptographic keys. This is seamless and does not require any additional input from the user. For greater control over the encryption, customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery Data Sets. Setting a Default Customer-managed encryption key (CMEK) for a data set ensure any tables created in future will use the specified CMEK if none other is provided. Note: Google does not store your keys on its servers and cannot access your protected data unless you provide the key. This also means that if you forget or lose your key, there is no way for Google to recover the key or to recover any data encrypted with the lost key. ",
+ "ImpactStatement": "Using Customer-managed encryption keys (CMEK) will incur additional labor-hour investment to create, protect, and manage the keys.",
+ "RemediationProcedure": "**From Google Cloud CLI** The default CMEK for existing data sets can be updated by specifying the default key in the `EncryptionConfiguration.kmsKeyName` field when calling the `datasets.insert` or `datasets.patch` methods",
+ "AuditProcedure": "**From Google Cloud Console** 1. Go to `Analytics` 2. Go to `BigQuery` 3. Under `Analysis` click on `SQL Workspaces`, select the project 4. Select Data Set 5. Ensure `Customer-managed key` is present under `Dataset info` section. 6. Repeat for each data set in all projects. **From Google Cloud CLI** List all dataset names bq ls Use the following command to view each dataset details. bq show <data_set_object> Verify the `kmsKeyName` is present.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/bigquery/docs/customer-managed-encryption",
+ "DefaultValue": "Google Managed keys are used as `key encryption keys`.",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "7.4",
+ "Description": "Ensure all data in BigQuery has been classified",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 BigQuery",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "BigQuery tables can contain sensitive data that for security purposes should be discovered, monitored, classified, and protected. Google Cloud's Sensitive Data Protection tools can automatically provide data classification of all BigQuery data across an organization.",
+ "RationaleStatement": "Using a cloud service or 3rd party software to continuously monitor and automate the process of data discovery and classification for BigQuery tables is an important part of protecting the data. Sensitive Data Protection is a fully managed data protection and data privacy platform that uses machine learning and pattern matching to discover and classify sensitive data in Google Cloud.",
+ "ImpactStatement": "There is a cost associated with using Sensitive Data Protection. There is also typically a cost associated with 3rd party tools that perform similar processes and protection.",
+ "RemediationProcedure": "**Enable profiling:** 1. Go to Cloud DLP by visiting https://console.cloud.google.com/dlp/landing/dataProfiles/configurations 1. Click Create Configuration 1. For projects follow https://cloud.google.com/dlp/docs/profile-project. For organizations or folders follow https://cloud.google.com/dlp/docs/profile-org-folder **Review findings:** - Columns or tables with high data risk have evidence of sensitive information without additional protections. To lower the data risk score, consider doing the following: - For columns containing sensitive data, apply a BigQuery policy tag to restrict access to accounts with specific access rights. - De-identify the raw sensitive data using de-identification techniques like masking and tokenization. **Incorporate findings into your security and governance operations:** - Enable sending findings into your security and posture services. You can publish data profiles to Security Command Center and Chronicle. - Automate remediation or enable alerting of new or changed data risk with Pub/Sub.",
+ "AuditProcedure": "1. Go to Cloud DLP by visiting https://console.cloud.google.com/dlp/landing/dataProfiles/configurations. 2. Verify there is a discovery scan configuration either for the organization or project.",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/dlp/docs/data-profiles:https://cloud.google.com/dlp/docs/analyze-data-profiles:https://cloud.google.com/dlp/docs/data-profiles-remediation:https://cloud.google.com/dlp/docs/send-profiles-to-scc:https://cloud.google.com/dlp/docs/profile-org-folder#chronicle:https://cloud.google.com/dlp/docs/profile-org-folder#publish-pubsub",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ },
+ {
+ "Id": "8.1",
+ "Description": "Ensure that Dataproc Cluster is encrypted using Customer-Managed Encryption Key",
+ "Checks": [
+ "dataproc_encrypted_with_cmks_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Dataproc",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "When you use Dataproc, cluster and job data is stored on Persistent Disks (PDs) associated with the Compute Engine VMs in your cluster and in a Cloud Storage staging bucket. This PD and bucket data is encrypted using a Google-generated data encryption key (DEK) and key encryption key (KEK). The CMEK feature allows you to create, use, and revoke the key encryption key (KEK). Google still controls the data encryption key (DEK).",
+ "RationaleStatement": "Cloud services offer the ability to protect data related to those services using encryption keys managed by the customer within Cloud KMS. These encryption keys are called customer-managed encryption keys (CMEK). When you protect data in Google Cloud services with CMEK, the CMEK key is within your control.",
+ "ImpactStatement": "Using Customer Managed Keys involves additional overhead in maintenance by administrators.",
+ "RemediationProcedure": "**From Google Cloud Console** 1. Login to the GCP Console and navigate to the Dataproc Cluster page by visiting https://console.cloud.google.com/dataproc/clusters. 1. Select the project from the projects dropdown list. 1. On the `Dataproc Cluster` page, click on the `Create Cluster` to create a new cluster with Customer managed encryption keys. 1. On `Create a cluster` page, perform below steps: - Inside `Set up cluster` section perform below steps: -In the `Name` textbox, provide a name for your cluster. - From `Location` select the location in which you want to deploy a cluster. - Configure other configurations as per your requirements. - Inside `Configure Nodes` and `Customize cluster` section configure the settings as per your requirements. - Inside `Manage security` section, perform below steps: - From `Encryption`, select `Customer-managed key`. - Select a customer-managed key from dropdown list. - Ensure that the selected KMS Key have Cloud KMS CryptoKey Encrypter/Decrypter role assign to Dataproc Cluster service account (serviceAccount:service-<project_number>@compute-system.iam.gserviceaccount.com). - Click on `Create` to create a cluster. - Once the cluster is created migrate all your workloads from the older cluster to the new cluster and delete the old cluster by performing the below steps: - On the `Clusters` page, select the old cluster and click on `Delete cluster`. - On the `Confirm deletion` window, click on `Confirm` to delete the cluster. - Repeat step above for other Dataproc clusters available in the selected project. - Change the project from the project dropdown list and repeat the remediation procedure for other Dataproc clusters available in other projects. **From Google Cloud CLI** Before creating cluster ensure that the selected KMS Key have Cloud KMS CryptoKey Encrypter/Decrypter role assign to Dataproc Cluster service account (serviceAccount:service-<project_number>@compute-system.iam.gserviceaccount.com). Run clusters create command to create new cluster with customer-managed key: gcloud dataproc clusters create <cluster_name> --region=us-central1 --gce-pd-kms-key=<key_resource_name> The above command will create a new cluster in the selected region. Once the cluster is created migrate all your workloads from the older cluster to the new cluster and Run clusters delete command to delete cluster: gcloud dataproc clusters delete <cluster_name> --region=us-central1 Repeat step no. 1 to create a new Dataproc cluster. Change the project by running the below command and repeat the remediation procedure for other projects: gcloud config set project <project_ID> ",
+ "AuditProcedure": "**From Google Cloud Console** 1. Login to the GCP Console and navigate to the Dataproc Cluster page by visiting https://console.cloud.google.com/dataproc/clusters. 1. Select the project from the project dropdown list. 1. On the `Dataproc Clusters` page, select the cluster and click on the Name attribute value that you want to examine. 1. On the `details` page, select the `Configurations` tab. 1. On the `Configurations` tab, check the `Encryption type` configuration attribute value. If the value is set to `Google-managed key`, then Dataproc Cluster is not encrypted with Customer managed encryption keys. Repeat step no. 3 - 5 for other Dataproc Clusters available in the selected project. 6. Change the project from the project dropdown list and repeat the audit procedure for other projects. **From Google Cloud CLI** 1. Run clusters list command to list all the Dataproc Clusters available in the region: gcloud dataproc clusters list --region='us-central1' 2. Run clusters describe command to get the key details of the selected cluster: gcloud dataproc clusters describe <cluster_name> --region=us-central1 --flatten=config.encryptionConfig.gcePdKmsKeyName 3. If the above command output return null, then the selected cluster is not encrypted with Customer managed encryption keys. 4. Repeat step no. 2 and 3 for other Dataproc Clusters available in the selected region. Change the region by updating --region and repeat step no. 2 for other clusters available in the project. Change the project by running the below command and repeat the audit procedure for other Dataproc clusters available in other projects: gcloud config set project <project_ID> ",
+ "AdditionalInformation": "",
+ "References": "https://cloud.google.com/docs/security/encryption/default-encryption",
+ "DefaultValue": "",
+ "SubSection": null
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/gcp/csa_ccm_4.0_gcp.json b/prowler/compliance/gcp/csa_ccm_4.0_gcp.json
deleted file mode 100644
index 6623fe5eca..0000000000
--- a/prowler/compliance/gcp/csa_ccm_4.0_gcp.json
+++ /dev/null
@@ -1,7386 +0,0 @@
-{
- "Framework": "CSA-CCM",
- "Name": "CSA Cloud Controls Matrix (CCM) v4.0.13",
- "Version": "4.0",
- "Provider": "GCP",
- "Description": "The Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing, composed of 197 control objectives structured in 17 domains covering all key aspects of cloud technology. The CCM can be used as a tool for the systematic assessment of a cloud implementation, and provides guidance on which security controls should be implemented by which actor within the cloud supply chain.",
- "Requirements": [
- {
- "Id": "A&A-02",
- "Description": "Conduct independent audit and assurance assessments according to relevant standards at least annually.",
- "Name": "Independent Assessments",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC4.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AAC-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.2",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.2.1",
- "27002: 18.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.35",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-2",
- "CA-2(1)",
- "CA-2(2)",
- "CA-7",
- "CA-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_audit_logs_enabled"
- ]
- },
- {
- "Id": "A&A-04",
- "Description": "Verify compliance with all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit.",
- "Name": "Requirements Compliance",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01",
- "GRM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.18.2.2",
- "27002: 18.2.2",
- "27001: A.18.2.3",
- "27002: 18.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-3",
- "DE.DP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_audit_logs_enabled",
- "iam_cloud_asset_inventory_enabled"
- ]
- },
- {
- "Id": "AIS-04",
- "Description": "Define and implement a SDLC process for application design, development, deployment, and operation in accordance with security requirements defined by the organization.",
- "Name": "Secure Application Design and Development",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27017: 14.1.1",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.14.2.1",
- "27002: 14.2.1",
- "27017: 14.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.8",
- "27001: A.8.25",
- "27001: A.8.26",
- "27001: A.8.28"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PL-8",
- "PL-8(1)",
- "SA-3",
- "SA-3(1)",
- "SA-4",
- "SA-4(2)",
- "SA-4(3)",
- "SA-4(8)",
- "SA-4(9)",
- "SA-5",
- "SA-8",
- "SA-8(1)-(7)",
- "SA-8(9)-(13)",
- "SA-8(15)-(20)",
- "SA-8(22)",
- "SA-8(24)-(28)",
- "SA-8(30)-(33)",
- "SA-17",
- "SA-17(1)-(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-6",
- "PR.DS-7",
- "PR.IP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1",
- "6.2.3",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "AIS-05",
- "Description": "Implement a testing strategy, including criteria for acceptance of new information systems, upgrades and new versions, which provides application security assurance and maintains compliance while enabling organizational speed of delivery goals. Automate when applicable and possible.",
- "Name": "Automated Application Security Testing",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.12",
- "16.13"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.3",
- "SD2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.8",
- "27001: A.14.2.9",
- "27001: A.12.1.2",
- "27002: 12.1.2",
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27001: A.14.2.2",
- "27002: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.25",
- "27001: A.8.29",
- "27001: A.8.32",
- "27002: 8.25 (e)",
- "27002: 8.32 (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SA-11",
- "SA-11(1)-(9)",
- "SI-6",
- "SI-6(2)",
- "SI-6(3)",
- "SI-10",
- "SI-10(1)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.IP-12",
- "DE.CM-8"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "PR.PS-01",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A.3.2.2",
- "A.3.2.2.1",
- "6.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.4",
- "6.4.1",
- "6.4.2",
- "6.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "gcr_container_scanning_enabled",
- "artifacts_container_analysis_enabled"
- ]
- },
- {
- "Id": "AIS-07",
- "Description": "Define and implement a process to remediate application security vulnerabilities, automating remediation when possible.",
- "Name": "Application Vulnerability Remediation",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1",
- "CC7.4",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.2",
- "16.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27001: A.12.6.1",
- "27002: 12.6.1",
- "27017: 12.6.1",
- "27018: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.26",
- "27001: A.8.8",
- "27002: 5.26 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-2",
- "SI-2(2)-(6)",
- "SA-11",
- "SA-11(2)",
- "SA-15",
- "SA-15(1)-(3)",
- "SA-15(5)-(8)",
- "SA-15(10)-(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.IP-12",
- "DE.CM-8",
- "RS.AN-5",
- "RS.MI-3",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.2",
- "6.5",
- "6.5.1-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "11.3.1",
- "11.3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "gcr_container_scanning_enabled",
- "artifacts_container_analysis_enabled"
- ]
- },
- {
- "Id": "BCR-08",
- "Description": "Periodically backup data stored in the cloud. Ensure the confidentiality, integrity and availability of the backup, and verify data restoration from backup for resiliency.",
- "Name": "Backup",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "A1.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "11.1",
- "11.2",
- "11.3",
- "11.4",
- "11.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27017: 12.3",
- "27018: 12.3.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.13",
- "27001: A.5.23",
- "27001: A.5.30",
- "27002: 8.13",
- "27002: 5.23 2nd (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-4",
- "CP-4(4)",
- "CP-6",
- "CP-6(1)-(3)",
- "CP-9",
- "CP-9(1)",
- "CP-9(2)",
- "CP-10",
- "CP-10(2)",
- "CP-10(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-4",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-11",
- "RC.RP-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.5.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "10.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudsql_instance_automated_backups",
- "cloudstorage_bucket_versioning_enabled",
- "cloudstorage_bucket_soft_delete_enabled"
- ]
- },
- {
- "Id": "BCR-09",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain a disaster response plan to recover from natural and man-made disasters. Update the plan at least annually or upon significant changes.",
- "Name": "Disaster Response Plan",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9",
- "1.6.1",
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.4",
- "BC2.1",
- "BC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.29",
- "27001: A.5.30",
- "27002: 5.29",
- "27002: 5.30"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2(1)",
- "CP-2(2)",
- "CP-2(3)",
- "CP-2(5)",
- "CP-2(6)",
- "CP-2(7)",
- "CP-2(8)",
- "PE-13",
- "PE-13(1)",
- "PE-13(2)",
- "PE-13(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-9",
- "PR.IP-10",
- "RC.IM-1",
- "RC.IM-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-04"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "BCR-11",
- "Description": "Supplement business-critical equipment with redundant equipment independently located at a reasonable minimum distance in accordance with applicable industry standards.",
- "Name": "Equipment Redundancy",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-06"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.20",
- "27001: A.7.11",
- "27001: A.8.14",
- "27002: 5.20 (t)",
- "27002: 8.14 (c)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "CP-4(3)",
- "CP-6",
- "CP-6(1)",
- "CP-7",
- "CP-8",
- "CP-8(1)-(3)",
- "CP-9",
- "CP-9(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.BE-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.OC-04",
- "GV.OC-05",
- "PR.IR-03"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_automatic_restart_enabled",
- "compute_instance_group_autohealing_enabled",
- "compute_instance_group_load_balancer_attached",
- "compute_instance_group_multiple_zones",
- "compute_instance_on_host_maintenance_migrate"
- ]
- },
- {
- "Id": "CCC-04",
- "Description": "Restrict the unauthorized addition, removal, update, and management of organization assets.",
- "Name": "Unauthorized Change Protection",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "CCC-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.1",
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4",
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.1.4",
- "27002: 12.1.4",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27001: A.14.2.2",
- "27017: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.3",
- "27001: A.8.4",
- "27001: A.8.15",
- "27001: A.8.31",
- "27001: A.8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(4)",
- "CM-3",
- "CM-3(1)",
- "CM-3(5)",
- "CM-3(7)",
- "CM-3(8)",
- "CM-5",
- "CM-5(1)",
- "CM-5(4)",
- "CM-5(5)",
- "CM-6",
- "CM-6(1)",
- "CM-6(2)",
- "CM-7",
- "CM-7(1)",
- "CM-7(4)",
- "CM-7(5)",
- "CM-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.MA-1",
- "PR.MA-2",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04",
- "ID.AM-08",
- "PR.PS-02",
- "PR.PS-03",
- "PR.PS-05",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.1",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_log_retention_policy_lock",
- "iam_audit_logs_enabled",
- "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
- "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled"
- ]
- },
- {
- "Id": "CCC-07",
- "Description": "Implement detection measures with proactive notification in case of changes deviating from the established baseline.",
- "Name": "Detection of Baseline Deviation",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.1",
- "1.5.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.2",
- "27001: A.14.2.4",
- "27001: A.12.4.1",
- "27002: 12.4.1 (g)",
- "27001: A.5.1.1",
- "27017: 5.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.9",
- "27001: A.8.15",
- "27002: 8.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(2)",
- "SI-2",
- "SI-2(2)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.MA-1",
- "PR.IP-1",
- "DE.DP-4",
- "PR.IP-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01",
- "DE.CM-09",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.3",
- "6.4.5.4",
- "11.5",
- "11.5.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "11.5.2",
- "11.6.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled",
- "logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
- "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
- "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled"
- ]
- },
- {
- "Id": "CEK-03",
- "Description": "Provide cryptographic protection to data at-rest and in-transit, using cryptographic libraries certified to approved standards.",
- "Name": "Data Encryption",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-03",
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6",
- "3.1",
- "3.11",
- "11.3",
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.1",
- "27001: A.18.1.2",
- "27001: A.18.1.3",
- "27001: A.18.1.4",
- "27001: A.18.1.5",
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.18",
- "27002: 18",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27001: A.14.1.3",
- "27002 14.1.3 c)",
- "27001 - A.10.1.1",
- "27017 - 10.1.1",
- "27001 - A.10.1.2",
- "27017 - 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.24",
- "27002: 8.24 Other Information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19",
- "AC-19(5)",
- "SC-8",
- "SC-8(1)",
- "SC-8(3)",
- "SC-8(4)",
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)-(3)",
- "SI-4",
- "SI-4(10)",
- "SI-7",
- "SI-7(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "Requirement 3",
- "2.2.3",
- "2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_encryption_with_csek_enabled",
- "compute_instance_confidential_computing_enabled",
- "bigquery_dataset_cmk_encryption",
- "bigquery_table_cmk_encryption",
- "cloudsql_instance_ssl_connections",
- "dataproc_encrypted_with_cmks_disabled"
- ]
- },
- {
- "Id": "CEK-04",
- "Description": "Use encryption algorithms that are appropriate for data protection, considering the classification of data, associated risks, and usability of the encryption technology.",
- "Name": "Encryption Algorithm",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.2",
- "27002: 8.2",
- "27001: A.8.3",
- "27001: A.10.1.1",
- "27002: 10.1.1 (b)",
- "27001: A.10.1.2",
- "27002: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.24",
- "27001: A.5.12",
- "27001: A.5.13",
- "27002: 8.24 General (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A2",
- "Requirement 3",
- "2.3",
- "2.2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "dns_rsasha1_in_use_to_key_sign_in_dnssec",
- "dns_rsasha1_in_use_to_zone_sign_in_dnssec"
- ]
- },
- {
- "Id": "CEK-08",
- "Description": "CSPs must provide the capability for CSCs to manage their own data encryption keys.",
- "Name": "CSC Key Management Capability",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27017: 10.1",
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.23",
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-9",
- "CP-9(8)",
- "SA-9",
- "SA-9(6)",
- "SC-12",
- "SC-12(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.AM-6",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-05"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "bigquery_dataset_cmk_encryption",
- "bigquery_table_cmk_encryption",
- "compute_instance_encryption_with_csek_enabled",
- "dataproc_encrypted_with_cmks_disabled",
- "kms_key_not_publicly_accessible",
- "kms_key_rotation_enabled"
- ]
- },
- {
- "Id": "CEK-10",
- "Description": "Generate Cryptographic keys using industry accepted cryptographic libraries specifying the algorithm strength and the random number generator used.",
- "Name": "Key Generation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "TS2.3",
- "SY1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27002: 10.1.1 (e)",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2",
- "27002: 10.1.2 (a)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24",
- "27002: 8.24 (d), Key management (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2.3",
- "3.6.1",
- "PCI Glossary - Cryptographic Key Generation"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.6.1.1",
- "3.7.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "bigquery_dataset_cmk_encryption",
- "bigquery_table_cmk_encryption",
- "dataproc_encrypted_with_cmks_disabled"
- ]
- },
- {
- "Id": "CEK-12",
- "Description": "Rotate cryptographic keys in accordance with the calculated cryptoperiod, which includes provisions for considering the risk of information disclosure and legal and regulatory requirements.",
- "Name": "Key Rotation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2 e)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (e,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_key_rotation_enabled",
- "iam_sa_user_managed_key_rotate_90_days",
- "apikeys_key_rotated_in_90_days"
- ]
- },
- {
- "Id": "CEK-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.",
- "Name": "Key Destruction",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27017: 10.1.2",
- "27001: A.10.1.2",
- "27002: 10.1.2 (j)",
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (j,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.IP-6",
- "ID.GV-3",
- "PR.DS-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "ID.AM-08",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.6.4",
- "3.6.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_kms_enforce_separation_of_duties"
- ]
- },
- {
- "Id": "DCS-06",
- "Description": "Catalogue and track all relevant physical and logical assets located at all of the CSP's sites within a secured system.",
- "Name": "Assets Cataloguing and Tracking",
- "Attributes": [
- {
- "Section": "Datacenter Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DCS - 01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "1.1",
- "2.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27017: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-8",
- "CM-8(1)",
- "CM-8(2)",
- "CM-8(4)",
- "CM-8(7)",
- "CM-8(8)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4",
- "9.7.1",
- "9.9.1",
- "9.9.1.a",
- "9.9.1.b",
- "9.9.1.c",
- "12.3.3",
- "12.3.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1.1",
- "6.3.2",
- "9.4.2",
- "9.4.3",
- "12.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_cloud_asset_inventory_enabled"
- ]
- },
- {
- "Id": "DSP-02",
- "Description": "Apply industry accepted methods for the secure disposal of data from storage media such that data is not recoverable by any forensic means.",
- "Name": "Secure Disposal",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3",
- "CC6.4",
- "CC6.5",
- "CC6.7",
- "P4.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-07"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.3",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.3.2",
- "27002: 8.3.2",
- "27001: A.11.2.7",
- "27002: 11.2.7"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.7.10",
- "27001: A.7.14",
- "27001: A.8.10",
- "27002: 7.10 (Secure reuse or disposal)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-22",
- "SI-12",
- "SI-12(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-10",
- "PR.PS-02",
- "PR.PS-03",
- "ID.AM-08"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1",
- "9.8",
- "9.8.1",
- "9.8.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "3.7.5",
- "9.4.7"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_lifecycle_management_enabled"
- ]
- },
- {
- "Id": "DSP-03",
- "Description": "Create and maintain a data inventory, at least for any sensitive data and personal data.",
- "Name": "Data Inventory",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2",
- "1.3.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-12",
- "CM-12(1)",
- "PM-5",
- "PM-5(1)",
- "SI-12",
- "SI-12(1)",
- "SI-19",
- "SI-19(1)",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "9.4.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_cloud_asset_inventory_enabled",
- "iam_audit_logs_enabled"
- ]
- },
- {
- "Id": "DSP-04",
- "Description": "Classify data according to its type and sensitivity level.",
- "Name": "Data Classification",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "C1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.2.1",
- "27002: 8.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-16",
- "AC-16(9)",
- "PM-22",
- "PM-23",
- "PT-2",
- "PT-2(1)",
- "SI-18",
- "SI-18(2)",
- "SI-19",
- "SI-19(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-05",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "9.4.2",
- "9.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-07",
- "Description": "Develop systems, products, and business practices based upon a principle of security by design and industry best practices.",
- "Name": "Data Protection by Design and Default",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "PI1.2",
- "PI1.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.1",
- "5.3.2",
- "5.3.3",
- "5.3.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.2",
- "IM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002:14.1.1",
- "27001: A.14.2.5",
- "27002:14.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.27",
- "27001: A.8.28",
- "27001: A.8.29",
- "27002: 5.8 (Information security requirements a-i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-17",
- "PM-24",
- "PM-25",
- "PT-2",
- "PT-2(2)",
- "SA-3",
- "SA-4",
- "SA-5",
- "SA-8",
- "SA-8(9)",
- "SA-8(13)",
- "SA-8(18)",
- "SA-8(20)",
- "SA-8(22)",
- "SA-8(23)",
- "SA-8(33)",
- "SA-15",
- "SA-15(12)",
- "SC-3",
- "SC-3(3)",
- "SC-7",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(4)",
- "SC-28",
- "SC-28(1)",
- "SI-12",
- "SI-12(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "bigquery_dataset_public_access",
- "cloudsql_instance_public_access",
- "cloudsql_instance_public_ip",
- "cloudstorage_bucket_public_access",
- "compute_image_not_publicly_shared",
- "compute_instance_public_ip",
- "kms_key_not_publicly_accessible"
- ]
- },
- {
- "Id": "DSP-10",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope as permitted by the respective laws and regulations.",
- "Name": "Sensitive Data Transfer",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.12",
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "9.5.1",
- "9.5.2",
- "9.5.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.8.3.3",
- "27002: 8.3.3",
- "27001: A.13.2.3",
- "27002: 13.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.7.10"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-4",
- "AC-4(23)-(25)",
- "CA-3",
- "CA-3(6)",
- "CA-6",
- "CA-6(1)",
- "CA-6(2)",
- "SC-4",
- "SC-4(2)",
- "SC-7",
- "SC-7(10)",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-16",
- "SC-16(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.DS-5",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.IR-01",
- "ID.AM-03",
- "GV.OC-03",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "4.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.1.1",
- "4.2.1",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudsql_instance_ssl_connections"
- ]
- },
- {
- "Id": "DSP-16",
- "Description": "Data retention, archiving and deletion is managed in accordance with business requirements, applicable laws and regulations.",
- "Name": "Data Retention and Deletion",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "C1.1",
- "C1.2",
- "CC3.1",
- "P4.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.4",
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.10",
- "27002: 5.33 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-12",
- "SI-12(1)-(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)",
- "SI-19",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-3",
- "PR.IP-6",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "GV.OC-03",
- "GV.SC-10",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_lifecycle_management_enabled",
- "cloudstorage_bucket_sufficient_retention_period"
- ]
- },
- {
- "Id": "DSP-17",
- "Description": "Define and implement, processes, procedures and technical measures to protect sensitive data throughout it's lifecycle.",
- "Name": "Sensitive Data Protection",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSC-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.1",
- "CC6.1",
- "CC6.3",
- "CC6.7",
- "CC8.1",
- "C1.1",
- "P2.0",
- "P3.0",
- "P4.0",
- "P5.0",
- "P6.0"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.1",
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.3",
- "9.1.1",
- "9.2.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001:A.18.1.4",
- "27002:18.1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.11",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PM-22",
- "PM-24",
- "PT-7",
- "PT-7(1)",
- "PT-7(2)",
- "PT-8",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.0 (including all subsections)",
- "4.0 (including all subsections)"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.1.1",
- "4.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_public_access",
- "bigquery_dataset_public_access",
- "cloudsql_instance_public_access",
- "cloudsql_instance_public_ip",
- "compute_instance_public_ip",
- "compute_image_not_publicly_shared",
- "kms_key_not_publicly_accessible"
- ]
- },
- {
- "Id": "GRC-05",
- "Description": "Develop and implement an Information Security Program, which includes programs for all the relevant domains of the CCM.",
- "Name": "Information Security Program",
- "Attributes": [
- {
- "Section": "Governance, Risk and Compliance",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "14.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SG2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-1",
- "PM-3",
- "PM-14",
- "PL-2",
- "PM-18",
- "PM-31"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.4.1",
- "A.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.4.1",
- "A3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_account_access_approval_enabled",
- "iam_audit_logs_enabled",
- "iam_organization_essential_contacts_configured"
- ]
- },
- {
- "Id": "IAM-02",
- "Description": "Establish, document, approve, communicate, implement, apply, evaluate and maintain strong password policies and procedures. Review and update the policies and procedures at least annually.",
- "Name": "Strong Password Policy and Procedures",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-12",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "4.1.2",
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1",
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.7.2.2",
- "27002: 7.2.2",
- "27001: A.9.2.6",
- "27002: 9.2.6",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.17",
- "27001: A.6.3",
- "27001: A.8.5",
- "27001: A.5.37"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-3",
- "AC-3(3)",
- "AC-12",
- "AC-12(1)",
- "IA-2",
- "IA-2(10)",
- "IA-5",
- "IA-5(1)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.AC-1",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.4",
- "12.1",
- "12.1.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.1.1",
- "8.3.8"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "IAM-03",
- "Description": "Manage, store, and review the information of system identities, and level of access.",
- "Name": "Identity Inventory",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-04",
- "IAM-08",
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27001: A.9.4.1",
- "27002: 9.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.5.15",
- "27001: A.5.16",
- "27001: A.5.18",
- "27001: A.7.4",
- "27001: A.8.15",
- "27001: A.8.2",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "AU-16",
- "AU-16(1)",
- "IA-4",
- "IA-4(8)",
- "IA-4(9)",
- "IA-5",
- "IA-5(5)",
- "IA-8",
- "IA-8(4)",
- "PM-5(1)",
- "SA-8",
- "SA-8(22)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-04",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4.a"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_sa_user_managed_key_unused",
- "iam_service_account_unused"
- ]
- },
- {
- "Id": "IAM-04",
- "Description": "Employ the separation of duties principle when implementing information system access.",
- "Name": "Separation of Duties",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC1.3",
- "CC5.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.2",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.6.1.2",
- "27002: 6.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18",
- "27001: A.5.3",
- "27001: A.8.2"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-6",
- "AC-6(1)-(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4",
- "6.4.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_sa_enforce_separation_of_duties",
- "iam_role_kms_enforce_separation_of_duties",
- "iam_no_service_roles_at_project_level"
- ]
- },
- {
- "Id": "IAM-05",
- "Description": "Employ the least privilege principle when implementing information system access.",
- "Name": "Least Privilege",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-06",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.1",
- "27002: 9.1.1",
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.8.2",
- "27002: 5.15 (Other information 2nd (a))"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "IA-12",
- "IA-12(2)",
- "IA-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1",
- "7.1.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2",
- "7.2.5",
- "7.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "apikeys_api_restrictions_configured",
- "compute_instance_default_service_account_in_use",
- "compute_instance_default_service_account_in_use_with_full_api_access",
- "gke_cluster_no_default_service_account",
- "iam_no_service_roles_at_project_level",
- "iam_sa_no_administrative_privileges"
- ]
- },
- {
- "Id": "IAM-07",
- "Description": "De-provision or respectively modify access of movers / leavers or system identity changes in a timely manner in order to effectively adopt and communicate identity and access management policies.",
- "Name": "User Access Changes and Revocation",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.3",
- "6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(1)",
- "AC-2(2)",
- "AC-2(6)",
- "AC-2(8)",
- "AC-3",
- "AC-3(8)",
- "AC-6",
- "AC-6(7)",
- "AU-10",
- "AU-10(4)",
- "AU-16",
- "AU-16(1)",
- "CM-7",
- "CM-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.IP-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-04",
- "GV.SC-10",
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.5",
- "8.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_sa_user_managed_key_unused",
- "iam_service_account_unused"
- ]
- },
- {
- "Id": "IAM-08",
- "Description": "Review and revalidate user access for least privilege and separation of duties with a frequency that is commensurate with organizational risk tolerance.",
- "Name": "User Access Review",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27001: A.9.2.6",
- "27001: A.9.4.1",
- "27017: 9.4.1",
- "27001: A.6.1.2",
- "27001: A 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.3",
- "27001: A.5.18",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "AC-6(8)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5.1",
- "7.2.5",
- "7.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_sa_user_managed_key_unused",
- "iam_service_account_unused",
- "iam_sa_user_managed_key_rotate_90_days"
- ]
- },
- {
- "Id": "IAM-09",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the segregation of privileged access roles such that administrative access to data, encryption and key management capabilities and logging capabilities are distinct and separated.",
- "Name": "Segregation of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.1",
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-3(7)",
- "AC-6(4)",
- "AC-6(8)",
- "IA-5",
- "IA-5(6)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.3",
- "3.5.2",
- "7.1.2",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.7.6",
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_role_kms_enforce_separation_of_duties",
- "iam_role_sa_enforce_separation_of_duties",
- "iam_sa_no_administrative_privileges"
- ]
- },
- {
- "Id": "IAM-10",
- "Description": "Define and implement an access process to ensure privileged access roles and rights are granted for a time limited period, and implement procedures to prevent the culmination of segregated privileged access.",
- "Name": "Management of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "6.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3",
- "27001: A.9.4.4",
- "27002: 9.4.4",
- "27017: 9.4.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(7)",
- "AC-3",
- "AC-3(4)",
- "AC-3(11)",
- "AC-3(13)",
- "AC-3(14)",
- "AC-6",
- "AC-6(4)",
- "AC-6(5)",
- "AC-6(8)",
- "AC-12",
- "AC-12(3)",
- "AC-17",
- "AC-17(4)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_no_service_roles_at_project_level",
- "iam_role_kms_enforce_separation_of_duties",
- "iam_role_sa_enforce_separation_of_duties",
- "iam_sa_no_administrative_privileges"
- ]
- },
- {
- "Id": "IAM-12",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the logging infrastructure is read-only for all with write access, including privileged access roles, and that the ability to disable it is controlled through a procedure that ensures the segregation of duties and break glass procedures.",
- "Name": "Safeguard Logs Integrity",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.3"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1",
- "27018: 12.4.1",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27017: 12.4.2",
- "27018: 12.4.2",
- "27001: A.12.4.3",
- "27002: 12.4.3",
- "27017: 12.4.3",
- "27018: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.18",
- "27002: 8.15 Protection of Logs"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(11)",
- "AC-2(12)",
- "IA-8",
- "IA-8(4)",
- "SA-8",
- "SA-8(22)",
- "SC-34",
- "SC-34(1)",
- "SC-34(2)",
- "SC-36",
- "SI-4",
- "SI-4(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_log_retention_policy_lock",
- "cloudstorage_bucket_logging_enabled",
- "logging_sink_created"
- ]
- },
- {
- "Id": "IAM-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure users are identifiable through unique IDs or which can associate individuals to the usage of user IDs.",
- "Name": "Uniquely Identifiable Users",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.1",
- "27002: 9.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(14)",
- "AC-24",
- "AC-24(2)",
- "AU-10",
- "AU-10(1)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-4",
- "IA-4(1)",
- "SA-8",
- "SA-8(22)",
- "SC-23",
- "SC-23(3)",
- "SC-40(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1",
- "8.2",
- "8.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.1",
- "8.2.2",
- "8.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_project_os_login_enabled"
- ]
- },
- {
- "Id": "IAM-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for authenticating access to systems, application and data assets, including multifactor authentication for at least privileged user and sensitive data access. Adopt digital certificates or alternatives which achieve an equivalent level of security for system identities.",
- "Name": "Strong Authentication",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.3",
- "6.5",
- "12.5",
- "12.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4",
- "SA1.8"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27017: 9.1.2",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.9.4.2",
- "27002: 9.4.2",
- "27017: 9.4.2",
- "27018: 9.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.17",
- "27001: A.8.5",
- "27001: A.8.24",
- "27002: 8.5",
- "27002: 8.24 other information (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(5)",
- "AC-7",
- "AC-7(4)",
- "AU-10",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(8)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5",
- "IA-5(2)",
- "IA-5(7)",
- "IA-5(9)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-5(14)-(16)",
- "IA-8",
- "IA-8(1)",
- "IA-8(6)",
- "SC-23",
- "SC-23(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3",
- "8.1.6",
- "8.2",
- "8.3",
- "8.3.2",
- "12.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "8.3.1",
- "8.3.2",
- "8.4.1",
- "8.4.2",
- "8.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_project_os_login_2fa_enabled",
- "compute_project_os_login_enabled"
- ]
- },
- {
- "Id": "IAM-15",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the secure management of passwords.",
- "Name": "Passwords Management",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27018: 9.2.4",
- "27001: A.9.3.1",
- "27002: 9.3.1",
- "27017: 9.3.1",
- "27018: 9.3.1",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.17"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IA-4",
- "IA-4(8)",
- "IA-5",
- "IA-5(1)",
- "IA-5(8)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.2",
- "8.2.1-6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.2",
- "2.3.1",
- "8.3.5",
- "8.3.6",
- "8.3.7",
- "8.3.8",
- "8.3.9",
- "8.3.10",
- "8.3.10.1",
- "8.6.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "IAM-16",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to verify access to data and system functions is authorized.",
- "Name": "Authorization Mechanisms",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27002: 9.2.5",
- "27017: 9.2.5",
- "27018: 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(5)",
- "AC-4",
- "AC-4(17)",
- "AC-4(21)",
- "AC-4(22)",
- "AC-6",
- "AC-6(8)",
- "AC-6(9)",
- "AC-12",
- "AC-12(1)",
- "AC-20",
- "AC-20(1)",
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5(1)",
- "IA-5(2)",
- "IA-5(5)",
- "IA-5(8)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-8",
- "IA-8(1)",
- "IA-8(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.AC-6",
- "PR.AC-7",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03",
- "PR.AA-04",
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.3",
- "7.1.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.4",
- "7.2.3",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "apikeys_api_restrictions_configured",
- "cloudstorage_bucket_uniform_bucket_level_access",
- "compute_instance_default_service_account_in_use_with_full_api_access",
- "iam_sa_no_administrative_privileges"
- ]
- },
- {
- "Id": "IPY-03",
- "Description": "Implement cryptographically secure and standardized network protocols for the management, import and export of data.",
- "Name": "Secure Interoperability and Portability Management",
- "Attributes": [
- {
- "Section": "Interoperability & Portability",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IPY-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.2",
- "NC1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1",
- "27001: A.15.1.1",
- "27002: 15.1.1",
- "27017: 15.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.19",
- "27001: A.5.23",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PT-2",
- "PT-2(2)",
- "SA-4",
- "SC-16",
- "SC-16(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.1",
- "1.2.5",
- "1.2.6",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudsql_instance_ssl_connections"
- ]
- },
- {
- "Id": "IVS-02",
- "Description": "Plan and monitor the availability, quality, and adequate capacity of resources in order to deliver the required system performance as determined by the business.",
- "Name": "Capacity and Resource Planning",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-04"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.3",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.12.1.3",
- "27002: 12.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.3 (b)",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.8.6",
- "27001: A.8.14"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "SC-5",
- "SC-5(2)",
- "SC-4",
- "SI-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-04",
- "GV.OC-04"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_group_autohealing_enabled",
- "compute_instance_group_load_balancer_attached",
- "compute_instance_group_multiple_zones"
- ]
- },
- {
- "Id": "IVS-03",
- "Description": "Monitor, encrypt and restrict communications between environments to only authenticated and authorized connections, as justified by the business. Review these configurations at least annually, and support them by a documented justification of all allowed services, protocols, ports, and compensating controls.",
- "Name": "Network Security",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-06"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.8",
- "3.1",
- "12.2",
- "13.6",
- "13.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: A.5.15 2nd c)",
- "27002: 8.20",
- "27002: 8.21",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-1",
- "SC-4",
- "SC-7",
- "SC-7(4)",
- "SC-7(5)",
- "SC-7(8)",
- "SC-7(9)",
- "SC-7(11)",
- "SC-8",
- "SC-8(1)",
- "SC-11",
- "SC-12",
- "SC-16",
- "SC-23",
- "SC-29",
- "SC-29(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-5",
- "PR.AC-7",
- "PR.PT-4",
- "DE.CM-1",
- "DE.CM-7",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-01",
- "PR.AA-03",
- "PR.AA-05",
- "DE.CM-01",
- "PR.DS-02",
- "ID.AM-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "1.1.6",
- "1.2",
- "1.2.3",
- "2.2",
- "4.1.1",
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.5",
- "1.2.6",
- "1.2.7",
- "1.4.2",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1",
- "10.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_firewall_rdp_access_from_the_internet_allowed",
- "compute_firewall_ssh_access_from_the_internet_allowed",
- "compute_instance_ip_forwarding_is_enabled",
- "compute_network_default_in_use",
- "compute_network_dns_logging_enabled",
- "compute_network_not_legacy",
- "compute_subnet_flow_logs_enabled"
- ]
- },
- {
- "Id": "IVS-04",
- "Description": "Harden host and guest OS, hypervisor or infrastructure control plane according to their respective best practices, and supported by technical controls, as part of a security baseline.",
- "Name": "OS Hardening and Base Controls",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.8",
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-07",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "4.1",
- "4.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.3",
- "SY1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.14.2.2",
- "27002: 14.2.2",
- "27001: A.14.2.3",
- "27001 A.14.2.4",
- "27018: 12.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: 8.20",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(1)",
- "SC-29",
- "SC-29(1)",
- "SC-2",
- "SC-7",
- "SC-7(12)",
- "SC-30",
- "SC-34",
- "SC-35",
- "SC-39",
- "SC-44"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-1",
- "PR.PT-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_shielded_vm_enabled",
- "compute_project_os_login_enabled",
- "compute_instance_serial_ports_in_use",
- "compute_instance_block_project_wide_ssh_keys_disabled"
- ]
- },
- {
- "Id": "IVS-06",
- "Description": "Design, develop, deploy and configure applications and infrastructures such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented and segregated, monitored and restricted from other tenants.",
- "Name": "Segmentation and Segregation",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-09"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.3.4",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.20",
- "27001: A.8.3",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.22",
- "27002: 5.15 (b)",
- "27002: 8.3 (b)",
- "27002: 8.16 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-3",
- "SC-7",
- "SC-7(20)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.AC-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.6",
- "8.3.1",
- "10.8",
- "11.3",
- "A3.2.1",
- "A3.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A1.1.1",
- "A1.1.2",
- "A1.1.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudsql_instance_private_ip_assignment",
- "cloudstorage_uses_vpc_service_controls",
- "compute_instance_public_ip",
- "compute_network_default_in_use",
- "compute_network_not_legacy"
- ]
- },
- {
- "Id": "IVS-07",
- "Description": "Use secure and encrypted communication channels when migrating servers, services, applications, or data to cloud environments. Such channels must include only up-to-date and approved protocols.",
- "Name": "Migration to Cloud Environments",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-10"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM1.4",
- "NC1.4",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27017: 13.1.1",
- "27018: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27017: 13.1.2",
- "27018: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3",
- "27018: 13.1.3",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27017: 13.2.1",
- "27018: 13.2.1",
- "27001: A.13.2.2",
- "27002: 13.2.2",
- "27017: 13.2.2",
- "27018: 13.2.2",
- "27001: A.13.2.3",
- "27002: 13.2.3",
- "27017: 13.2.3",
- "27018: 13.2.3",
- "27001: A.13.2.4",
- "27002: 13.2.4",
- "27017: 13.2.4",
- "27018: 13.2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.20",
- "27001: A.8.24",
- "27002: 8.20 (e)",
- "27002: 8.24 Guidance (b,f), other information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-17",
- "AC-20",
- "SC-7",
- "SC-7(28)",
- "SC-8",
- "SC-8(1)",
- "SC-12",
- "SC-23",
- "SC-29",
- "SI-7",
- "SI-7(1)-(3)",
- "SI-7(5)-(10)",
- "SI-7(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudsql_instance_ssl_connections"
- ]
- },
- {
- "Id": "IVS-09",
- "Description": "Define, implement and evaluate processes, procedures and defense-in-depth techniques for protection, detection, and timely response to network-based attacks.",
- "Name": "Network Defense",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.6",
- "CC6.8",
- "CC7.1",
- "CC7.2",
- "CC7.5"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-13"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "13.3",
- "13.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3",
- "5.2.4",
- "5.2.5",
- "5.2.7",
- "5.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.11.1.4",
- "27002: 11.1.4",
- "27017: 11.1.4",
- "27018: 16.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.5.24",
- "27001: A.5.26",
- "27001: A.8.8",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.26",
- "27002: 8.8 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-8",
- "PL-8(1)",
- "SC-5",
- "SC-5(1)",
- "SC-5(3)",
- "SC-7",
- "SC-7(13)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.DP-1",
- "DE.CM-1",
- "DE.CM-7",
- "PR.AC-5",
- "RS.MI-2",
- "PR.DS-2",
- "RS.RP-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "DE.CM-01",
- "PR.IR-01",
- "RS.MA-01",
- "RS.MI-01",
- "RS.MI-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.6",
- "1.1",
- "1.2",
- "1.3",
- "1.5",
- "12.10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.1.1",
- "1.3.1",
- "1.3.2",
- "1.3.3",
- "1.4.1",
- "1.4.2",
- "1.4.3",
- "1.4.4",
- "1.4.5",
- "1.5.1",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_firewall_rdp_access_from_the_internet_allowed",
- "compute_firewall_ssh_access_from_the_internet_allowed",
- "compute_loadbalancer_logging_enabled",
- "compute_public_address_shodan",
- "dns_dnssec_disabled"
- ]
- },
- {
- "Id": "LOG-02",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the security and retention of audit logs.",
- "Name": "Audit Logs Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1",
- "8.9",
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.3",
- "5.1.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-4",
- "AU-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-08",
- "PR.DS-11",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.7"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4",
- "10.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_log_retention_policy_lock",
- "cloudstorage_bucket_logging_enabled",
- "logging_sink_created"
- ]
- },
- {
- "Id": "LOG-03",
- "Description": "Identify and monitor security-related events within applications and the underlying infrastructure. Define and implement a system to generate alerts to responsible stakeholders based on such events and corresponding metrics.",
- "Name": "Security Monitoring and Alerting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03",
- "SEF-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "5.2.7",
- "1.6.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2",
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-3",
- "DE.AE-5",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-4",
- "DE.CM-5",
- "DE.CM-6",
- "DE.CM-7",
- "DE.DP-1",
- "DE.DP-4",
- "DE.AE-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2",
- "10.4.1.1",
- "10.4.2.1",
- "10.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled",
- "logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
- "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
- "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled"
- ]
- },
- {
- "Id": "LOG-04",
- "Description": "Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.",
- "Name": "Audit Logs Access and Accountability",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.1",
- "4.1.2",
- "4.1.3",
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27001: A.12.4.1",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(4)",
- "AU-9(6)",
- "AU-10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.1",
- "10.2.1",
- "10.2.3",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1.3",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_public_access",
- "cloudstorage_bucket_uniform_bucket_level_access",
- "iam_audit_logs_enabled",
- "kms_key_not_publicly_accessible"
- ]
- },
- {
- "Id": "LOG-05",
- "Description": "Monitor security audit logs to detect activity outside of typical or expected patterns. Establish and follow a defined process to review and take appropriate and timely actions on detected anomalies.",
- "Name": "Audit Logs Monitoring and Response",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.8",
- "8.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "1.6.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.3",
- "27002: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-6",
- "AU-6(1)",
- "AU-6(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-3",
- "PR.PT-1",
- "RS.AN-1",
- "RS.CO-1.",
- "DE.AE-1",
- "DE.AE-5",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6",
- "10.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.1.1",
- "10.4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled",
- "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled",
- "logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
- "logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled",
- "logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled"
- ]
- },
- {
- "Id": "LOG-07",
- "Description": "Establish, document and implement which information meta/data system events should be logged. Review and update the scope at least annually or whenever there is a change in the threat environment.",
- "Name": "Logging Scope",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-14",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.SC-4",
- "PR.PT-1",
- "ID.GV-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_audit_logs_enabled",
- "cloudstorage_bucket_logging_enabled",
- "compute_network_dns_logging_enabled",
- "compute_subnet_flow_logs_enabled",
- "iam_audit_logs_enabled"
- ]
- },
- {
- "Id": "LOG-08",
- "Description": "Generate audit records containing relevant security information.",
- "Name": "Log Records",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-3",
- "AU-3(1)",
- "AU-3(3)",
- "AU-6",
- "AU-6(8)",
- "AU-12",
- "AU-12(1)",
- "AU-12(2)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-6",
- "DE.CM-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_audit_logs_enabled",
- "compute_subnet_flow_logs_enabled",
- "compute_loadbalancer_logging_enabled",
- "compute_network_dns_logging_enabled",
- "cloudstorage_audit_logs_enabled",
- "cloudstorage_bucket_logging_enabled",
- "logging_sink_created",
- "cloudsql_instance_postgres_log_connections_flag",
- "cloudsql_instance_postgres_log_disconnections_flag",
- "cloudsql_instance_postgres_log_statement_flag",
- "cloudsql_instance_postgres_enable_pgaudit_flag"
- ]
- },
- {
- "Id": "LOG-09",
- "Description": "The information system protects audit records from unauthorized access, modification, and deletion.",
- "Name": "Log Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04",
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(2)",
- "AU-9(3)",
- "AU-9(4)",
- "AU-12(3)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_bucket_log_retention_policy_lock",
- "cloudstorage_bucket_uniform_bucket_level_access"
- ]
- },
- {
- "Id": "LOG-10",
- "Description": "Establish and maintain a monitoring and internal reporting capability over the operations of cryptographic, encryption and key management policies, processes, procedures, and controls.",
- "Name": "Encryption Monitoring and Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.1.1",
- "10.2.1",
- "10.4.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_key_rotation_enabled"
- ]
- },
- {
- "Id": "LOG-11",
- "Description": "Log and monitor key lifecycle management events to enable auditing and reporting on usage of cryptographic keys.",
- "Name": "Transaction/Activity Logging",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudstorage_audit_logs_enabled",
- "iam_audit_logs_enabled",
- "logging_sink_created"
- ]
- },
- {
- "Id": "LOG-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the reporting of anomalies and failures of the monitoring system and provide immediate notification to the accountable party.",
- "Name": "Failures and Anomalies Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.16.1.2",
- "27017: 16.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.24",
- "27001: A.6.8",
- "27002: 6.8 (g)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-6",
- "AU-6(3)",
- "AU-6(4)",
- "AU-6(5)",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-3",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.3",
- "10.7.1",
- "10.7.2",
- "10.7.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled",
- "logging_log_metric_filter_and_alert_for_custom_role_changes_enabled",
- "logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled"
- ]
- },
- {
- "Id": "SEF-03",
- "Description": "'Establish, document, approve, communicate, apply, evaluate and maintain a security incident response plan, which includes but is not limited to: relevant internal departments, impacted CSCs, and other business critical relationships (such as supply-chain) that may be impacted.'",
- "Name": "Incident Response Plans",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2",
- "CC7.3",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2",
- "17.4"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27017: CLD.12.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.5.26",
- "27002: 5.26 (e,f)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-1",
- "IR-2",
- "IR-2(1)-(3)",
- "IR-3",
- "IR-3(1)-(3)",
- "IR-4",
- "IR-4(1)-(15)",
- "IR-5",
- "IR-5(1)",
- "IR-6",
- "IR-6(1)-(3)",
- "IR-7",
- "IR-7(1)",
- "IR-7(2)",
- "IR-8",
- "IR-8(1)",
- "IR-9",
- "IR-9(1)-(4)",
- "PM-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.CO-1",
- "RS.CO-4",
- "ID.AM-6",
- "ID.GV-2",
- "ID.SC-5",
- "PR.IP-9",
- "PR.IP10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AT-01",
- "PR.AT-02",
- "RS.MA-01",
- "GV.SC-08",
- "ID.IM-02",
- "ID.IM-04",
- "RC.RP-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "12.10.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "SEF-06",
- "Description": "Define, implement and evaluate processes, procedures and technical measures supporting business processes to triage security-related events.",
- "Name": "Event Triage Processes",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.4",
- "27002: 16.1.4",
- "27017: 16.1.4",
- "27018: 16.1.4",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.25"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(3)",
- "CA-7(4)",
- "CA-7(5)",
- "CA-7(6)",
- "IR-4",
- "IR-4(1)",
- "IR-4(3)",
- "IR-4(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-4",
- "RS.RP-1",
- "RS.AN-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "RS.MA-02",
- "RS.MA-03",
- "RS.AN-03",
- "DE.AE-02",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "RS.MI-02",
- "RC.RP-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_audit_logs_enabled",
- "logging_sink_created"
- ]
- },
- {
- "Id": "SEF-08",
- "Description": "Maintain points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities.",
- "Name": "Points of Contact Maintenance",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.2",
- "27001: A.6.1.3",
- "27002: 6.1.3",
- "27017: 6.1.3",
- "27018: 6.1.3",
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.18.1.1",
- "27002: 18.1.1",
- "27017: 18.1.1",
- "27018: 18.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.5",
- "27001: A.5.24",
- "27002: 5.24 Incident management procedure (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-4",
- "IR-4(8)",
- "IR-6",
- "IR-6(3)",
- "IR-7",
- "IR-7(2)",
- "PM-21",
- "PM-23",
- "PM-26"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-2",
- "RS.CO-3",
- "RS.CO-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-02",
- "RS.CO-02",
- "RS.CO-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "iam_organization_essential_contacts_configured"
- ]
- },
- {
- "Id": "TVM-02",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually.",
- "Name": "Malware Protection Policy and Procedures",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.8"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-01",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "9.7",
- "10.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.2",
- "TS1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.12.2.1",
- "27001: A.6.2.1",
- "27002: 6.2.1 (h)",
- "27001: A.6.2.2",
- "27002: 6.2.2 (j)",
- "27001: A.7.2.2",
- "27002: 7.2.2 (d)",
- "27001: A.10.1.1",
- "27002: 10.1.1 (g)",
- "27001: A.13.2.1",
- "27002: 13.2.1 (b)",
- "27001: A.15.1.2",
- "27017: 15.1.2",
- "27001: A.12.2.1",
- "27002: 12.2.1 (a),(d)",
- "27017: CLD.9.5.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.7",
- "27001: A.5.37",
- "27001: A.8.7",
- "27002: 5.7 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-3",
- "RA-3(3)",
- "RA-5",
- "RA-5(3)",
- "RA-5(5)",
- "SI-3",
- "SI-3(4)",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "DE.CM-4",
- "DE.CM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "DE.CM-01",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.4",
- "12.1",
- "12.1.1",
- "12.3.1",
- "12.5.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.1.1",
- "12.1.2",
- "5.1.1",
- "5.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-03",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to enable both scheduled and emergency responses to vulnerability identifications, based on the identified risk.",
- "Name": "Vulnerability Remediation Schedule",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC7.1",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.2",
- "7.7",
- "17.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "TM2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.2.1",
- "27001: A.12.6.1",
- "27002: 12.6.1(c)(d)(j)",
- "27018: 12.6.1(k)(i)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.8.7",
- "27001: A.8.8",
- "27001: A.8.32",
- "27002: 8.7",
- "27002: 8.8",
- "27002: 8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-31",
- "RA-3",
- "RA-3(1)",
- "RA-5",
- "RA-5(2)-(4)",
- "RA-5(6)",
- "SI-3",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.AN-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.1.a",
- "6.1.b"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.1.1",
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-04",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to update detection tools, threat signatures, and indicators of compromise on a weekly, or more frequent basis.",
- "Name": "Detection Updates",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.3",
- "TS1.4",
- "TM1.3",
- "TM1.4",
- "IM1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1.1",
- "27002: 5.1.1 (h)",
- "27001: A.12.6.1",
- "27002: 12.6.1 (b),(c)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1",
- "27001: A.8.8",
- "27001: A.8.15",
- "27001: A.8.16",
- "27002: 5.1",
- "27002: 5.37",
- "27002: 8.8",
- "27002: 8.15 (d)",
- "27002: 8.16 (d,e)",
- "27002: 8.31 2nd (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-7",
- "CM-7(4)",
- "RA-3",
- "RA-3(3)",
- "RA-5(2)",
- "SA-10",
- "SA-10(5)",
- "SA-11",
- "SA-11(2)",
- "SI-2",
- "SI-2(4)",
- "SI-3",
- "SI-3(4)",
- "SI-4",
- "SI-4(9)",
- "SI-4(24)",
- "SI-8",
- "SI-8(2)",
- "SI-8(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-02",
- "ID.RA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.2",
- "5.2a",
- "5.2b",
- "5.2c"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "5.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "artifacts_container_analysis_enabled",
- "gcr_container_scanning_enabled"
- ]
- },
- {
- "Id": "TVM-05",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to identify updates for applications which use third party or open source libraries according to the organization's vulnerability management policy.",
- "Name": "External Library Vulnerabilities",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "SD2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.6.2",
- "27002: 12.6.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A 5.6",
- "27001: A.8.19",
- "27001: A.8.8",
- "27001: A.8.28",
- "27001: A.8.31",
- "27002: 5.6 (c)",
- "27001: 8.19",
- "27001: 8.8",
- "27001: 8.28",
- "27001: 8.31"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(3)",
- "SA-11",
- "SA-11(2)",
- "SA-11(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-03",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.2",
- "6.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "artifacts_container_analysis_enabled",
- "gcr_container_scanning_enabled"
- ]
- },
- {
- "Id": "TVM-07",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the detection of vulnerabilities on organizationally managed assets at least monthly.",
- "Name": "Vulnerability Identification",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.1",
- "7.5",
- "7.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.6",
- "27001: A.12.6.1",
- "27002: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.8",
- "27002: 8.8"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(4)",
- "RA-5(5)",
- "SA-11",
- "SA-11(5)",
- "SA-15(5)",
- "SC-7",
- "SC-7(10)",
- "SI-3(8)",
- "SI-3(10)",
- "SI-7",
- "SI-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.RA-1",
- "DE.CM-8",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "11.2",
- "11.2.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "11.3.2",
- "11.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "artifacts_container_analysis_enabled",
- "compute_public_address_shodan",
- "gcr_container_scanning_enabled"
- ]
- },
- {
- "Id": "UEM-08",
- "Description": "Protect information from unauthorized disclosure on managed endpoint devices with storage encryption.",
- "Name": "Storage Encryption",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "MOS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "3.1.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "PA1.2",
- "PA1.3",
- "PA1.5",
- "PA2.2",
- "PM1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.11.2.7",
- "27002: 11.2.7",
- "27001: A.18.1.1",
- "27017: 18.1.1",
- "27001: A.12.3.1",
- "27017: 12.3.1",
- "27018: A.11.4",
- "27018: A.11.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.1",
- "27002: 8.1 (h)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.4",
- "3.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.5.1",
- "3.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "bigquery_dataset_cmk_encryption",
- "bigquery_table_cmk_encryption",
- "compute_instance_confidential_computing_enabled",
- "compute_instance_encryption_with_csek_enabled",
- "dataproc_encrypted_with_cmks_disabled"
- ]
- },
- {
- "Id": "UEM-11",
- "Description": "Configure managed endpoints with Data Loss Prevention (DLP) technologies and rules in accordance with a risk assessment.",
- "Name": "Data Loss Prevention",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.5",
- "PA2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27002: 12.3",
- "27001: A.8.3.1",
- "27002: 8.3.1",
- "27001: A.12.2",
- "27002: 12.2",
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001: A.6.1.1",
- "27017: 6.1.1",
- "27018: 12.3.1",
- "27018: 10.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-7",
- "SC-7(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.DS-10",
- "PR.PS-01",
- "ID.AM-08",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A3.2.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A3.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": []
- }
- ]
-}
diff --git a/prowler/compliance/gcp/prowler_threatscore_gcp.json b/prowler/compliance/gcp/prowler_threatscore_gcp.json
index 46fc776fbe..923a1acfc2 100644
--- a/prowler/compliance/gcp/prowler_threatscore_gcp.json
+++ b/prowler/compliance/gcp/prowler_threatscore_gcp.json
@@ -117,7 +117,7 @@
"Id": "1.2.4",
"Description": "Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days",
"Checks": [
- "kms_key_rotation_enabled"
+ "kms_key_rotation_max_90_days"
],
"Attributes": [
{
diff --git a/prowler/compliance/github/cis_1.2.0_github.json b/prowler/compliance/github/cis_1.2.0_github.json
new file mode 100644
index 0000000000..840b5aa3d8
--- /dev/null
+++ b/prowler/compliance/github/cis_1.2.0_github.json
@@ -0,0 +1,2574 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS GitHub Benchmark v1.2.0",
+ "Version": "1.2.0",
+ "Provider": "GitHub",
+ "Description": "This document provides prescriptive guidance for establishing a secure configuration posture for securing GitHub.",
+ "Requirements": [
+ {
+ "Id": "1.1.1",
+ "Description": "Manage all code projects in a version control platform.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Manage all code projects in a version control platform.",
+ "RationaleStatement": "Version control platforms keep track of every modification to code. They represent the cornerstone of code security, as well as allowing for better code collaboration within engineering teams. With granular access management, change tracking, and key signing of code edits, version control platforms are the first step in securing the software supply chain.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Upload existing code projects to a dedicated Github organization and repositories and create an identity for each active team member who might contribute or need access to it.",
+ "AuditProcedure": "Ensure that all code activity is managed through Github repository for every micro-service or application developed by an organization.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.2",
+ "Description": "Use a task management system to trace any code back to its associated task.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use a task management system to trace any code back to its associated task.",
+ "RationaleStatement": "The ability to trace each piece of code back to its associated task simplifies the Agile and DevOps process by enabling transparency of any code changes. This allows faster remediation of bugs and security issues, while also making it harder to push unauthorized code changes to sensitive projects. Additionally, using a task management system simplifies achieving compliance, as it is easier to track each regulation.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Use a task management system to manage tasks as the starting point for each code change. Whether it is a new feature, bug fix, or security fix - all should originate from a dedicated task (ticket) in your organization's task management system. These tasks should also be linked to the code changes themselves in a way that is easy to follow: from code to task, and from task back to code.",
+ "AuditProcedure": "Ensure every code change can be traced back to its origin task in a task management system.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.3",
+ "Description": "Ensure that every code change is reviewed and approved by two authorized contributors who are both strongly authenticated - using Multi-Factor Authentication (MFA), from the team relevant to the code change.",
+ "Checks": [
+ "repository_default_branch_requires_multiple_approvals"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that every code change is reviewed and approved by two authorized contributors who are both strongly authenticated - using Multi-Factor Authentication (MFA), from the team relevant to the code change.",
+ "RationaleStatement": "To prevent malicious or unauthorized code changes, the first layer of protection is the process of code review. This process involves engineer teammates reviewing each other's code for errors, optimizations, and general knowledge-sharing. With proper peer reviews in place, an organization can detect unwanted code changes very early in the process of release. In order to help facilitate code review, companies should employ automation to verify that every code change has been reviewed and approved by at least two team members before it is pushed into the code base. These team members should be from the team that is related to the code change, so it will be a meaningful review.",
+ "ImpactStatement": "To enforce a code review requirement, verification for a minimum of two reviewers must be put into place. This will ensure new code will not be able to be pushed to the code base before it has received two independent approvals.",
+ "RemediationProcedure": "For every code repository in use, perform the next steps to require two approvals from the specific code repository team in order to push new code to the code base:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you added the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Check **Require a pull request before merging** and **Require approvals**, and set **Required number of approvals before merging** to 2.\n5. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, perform the next steps to verify that two approvals from the specific code repository team are required to push new code to the code base:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require a pull request before merging** and **Require approvals** are checked, and verify that **Required number of approvals before merging** is set to 2.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "0"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.4",
+ "Description": "Ensure that when a proposed code change is updated, previous approvals are declined, and new approvals are required.",
+ "Checks": [
+ "repository_default_branch_dismisses_stale_reviews"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that when a proposed code change is updated, previous approvals are declined, and new approvals are required.",
+ "RationaleStatement": "An approval process is necessary when code changes are suggested. Through this approval process, however, changes can still be made to the original proposal even after some approvals have already been given. This means malicious code can find its way into the code base even if the organization has enforced a review policy. To ensure this is not possible, outdated approvals must be declined when changes to the suggestion are introduced.",
+ "ImpactStatement": "If new code changes are pushed to a specific proposal, all previously accepted code change proposals must be declined.",
+ "RemediationProcedure": "For each code repository in use, perform the next steps to enforce dismissal of given approvals to code change suggestions if those suggestions were updated:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you added the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require pull request reviews before merging** and then **Dismiss stale pull request approvals when new commits are pushed**.\n5. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For each code repository in use, perform the next steps to verify that each updated code suggestion declines the previously received approvals:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require a pull request before merging** is checked, and verify that **Dismiss stale pull request approvals when new commits are pushed** is checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.5",
+ "Description": "Only trusted users should be allowed to dismiss code change reviews.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Only trusted users should be allowed to dismiss code change reviews.",
+ "RationaleStatement": "Dismissing a code change review permits users to merge new suggested code changes without going through the standard process of approvals. Controlling who can perform this action will prevent malicious actors from simply dismissing the required reviews to code changes and merging malicious or dysfunctional code into the code base.",
+ "ImpactStatement": "In cases where a code change proposal has been updated since it was last reviewed and the person who reviewed it isn't available for approval, a general collaborator would not be able to merge their code changes until a user with \"dismiss review\" abilities could dismiss the open review.\n\nUsers who are not allowed to dismiss code change reviews will not be permitted to do so, and thus are unable to waive the standard flow of approvals.",
+ "RemediationProcedure": "For each code repository in use, perform the next steps to restrict dismissal of code changes reviews unless it is necessary:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you added the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n4. Select **Require pull request reviews before merging** and **Restrict who can dismiss pull request reviews**.\n5. Do not add any user or team unless it is obligatory. If it is obligatory, carefully select the users or teams whom you trust with the ability to dismiss code change reviews.\n6. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For each code repository in use, perform the next steps to verify that only trusted users are allowed to dismiss code change reviews: \n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n4. Verify that **Require a pull request before merging** and **Restrict who can dismiss pull request reviews** is checked.\n5. Verify that no users and teams are specified except for organization and repository admins. If it is obligatory, verify that the users or teams specified were carefully selected to be trusted with the ability to dismiss code change reviews.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, all users who have write access to the code repository are able to dismiss code change reviews."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.6",
+ "Description": "Code owners are trusted users that are responsible for reviewing and managing an important piece of code or configuration. An organization is advised to set code owners for every extremely sensitive code or configuration.",
+ "Checks": [
+ "repository_has_codeowners_file"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Code owners are trusted users that are responsible for reviewing and managing an important piece of code or configuration. An organization is advised to set code owners for every extremely sensitive code or configuration.",
+ "RationaleStatement": "Configuring code owners protects data by verifying that trusted users will notice and review every edit, thus preventing unwanted or malicious changes from potentially compromising sensitive code or configurations.",
+ "ImpactStatement": "Code owner users will receive notifications for every change that occurs to the code and subsequently added as reviewers of pull requests automatically.",
+ "RemediationProcedure": "In every code repository create a CODEOWNERS file in the root, docs/, or .github/ directory of the repository.\nIn the file, specify codeowners for the .github/workflows/ directory atleast. Specify organization members you trust. For example:\n```\n.github/workflows/ @user1 @user2\n```",
+ "AuditProcedure": "In every code repository, verify that a file named CODEOWNERS exists in the root, docs/, or .github/ directory of the repository.\nIn the CODEOWNERS file, verify that the users specified are users you trust.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners",
+ "DefaultValue": "None"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.7",
+ "Description": "Ensure trusted code owners are required to review and approve any code change proposal made to their respective owned areas in the code base.",
+ "Checks": [
+ "repository_default_branch_requires_codeowners_review"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure trusted code owners are required to review and approve any code change proposal made to their respective owned areas in the code base.",
+ "RationaleStatement": "Configuring code owners ensures that no code, especially code which could prove malicious, will slip into the source code or configuration files of a repository. This allows an organization to mark areas in the code base that are especially sensitive or more prone to an attack. It can also enforce review by specific individuals who are designated as owners to those areas so that they may filter out unauthorized or unwanted changes beforehand.",
+ "ImpactStatement": "If an organization enforces code owner-based reviews, some code change proposals would not be able to be merged to the codebase before specific, trusted individuals approve them.",
+ "RemediationProcedure": "For every code repository in use, perform the following steps to require code owners' approvals for each change proposal related to code they own:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require pull request reviews before merging** and **Require review from Code Owners**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, perform the following steps to verify that code owners are required to review all code change proposals relevant to areas they own before code merge:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n4. Ensure that **Require a pull request before merging** and **Require review from Code Owners** are checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Code owners are not required to review changes by default."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.8",
+ "Description": "Keep track of code branches that are inactive for a lengthy period of time and periodically remove them.",
+ "Checks": [
+ "repository_inactive_not_archived",
+ "repository_branch_delete_on_merge_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Keep track of code branches that are inactive for a lengthy period of time and periodically remove them.",
+ "RationaleStatement": "Git branches that have been inactive (i.e., no new changes introduced) for a long period of time are enlarging the surface of attack for malicious code injection, sensitive data leaks, and CI pipeline exploitation. They potentially contain outdated dependencies which may leave them highly vulnerable. They are more likely to be improperly managed, and could possibly be accessed by a large number of members of the organization.",
+ "ImpactStatement": "Removing inactive Git branches means that any code changes they contain would be removed along with them, thus work done in the past might not be accessible after auditing for inactivity.",
+ "RemediationProcedure": "For each code repository in use, review existing Git branches and remove those which have not been active for a period of time by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Above the list of files, click **Branches**.\n3. Use the navigation at the top of the page to view the Stale branches. The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first.\n4. For each branch listed, either delete it by clicking the trash bin icon, or find the valid reason it still exists.\n\nYou can perform the next steps to prevent pull request branches from becoming stale branches:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click Settings.\n3. Under \"Pull Requests\", select **Automatically delete head branches**.",
+ "AuditProcedure": "For each code repository in use, verify that all existing Git branches are active or have yet to be checked for inactivity by performing the next steps:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Above the list of files, click **Branches**.\n3. Use the navigation at the top of the page to view the Stale branches. The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first.\n4. If the list is empty, you are compliant. If the list is not empty, but there is a valid reason the branches listed are not deleted, you are compliant.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, newly opened Git branches would never be removed, regardless of activity or inactivity."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.9",
+ "Description": "Before a code change request can be merged to the code base, all predefined checks must successfully pass.",
+ "Checks": [
+ "repository_default_branch_status_checks_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Before a code change request can be merged to the code base, all predefined checks must successfully pass.",
+ "RationaleStatement": "On top of manual reviews of code changes, a code protect should contain a set of prescriptive checks which validate each change. Organizations should enforce those status checks so that changes can only be introduced if all checks have successfully passed. This set of checks should serve as the absolute quality, stability, and security conditions which must be met in order to merge new code to a project.",
+ "ImpactStatement": "Code changes in which all checks do not pass successfully would not be able to be pushed into the code base of the specific code repository.",
+ "RemediationProcedure": "For each code repository in use, require all status checks to pass before permitting a merge of new code by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", check if there is a rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require status checks to pass before merging**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For each code repository in use, verify that status checks are required to pass before allowing any code change proposal merge by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require status checks to pass before merging** is checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, no checks are defined per project, and thus no enforcement of checks is made."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.10",
+ "Description": "Organizations should make sure each suggested code change is in full sync with the existing state of its origin code repository before allowing merging.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Organizations should make sure each suggested code change is in full sync with the existing state of its origin code repository before allowing merging.",
+ "RationaleStatement": "Git branches can easily become outdated since the origin code repository is constantly being edited. This means engineers working on separate code branches can accidentally include outdated code with potential security issues which might have already been fixed, overriding the potential solutions for those security issues when merging their own changes.",
+ "ImpactStatement": "If enforced, outdated branches would not be able to be merged into their origin repository without first being updated to contain any recent changes.",
+ "RemediationProcedure": "For each code repository in use, enforce a policy to only allow merging open branches if they are current with the latest change from their original repository by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require status checks to pass before merging** and **Require branches to be up to date before merging**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For each code repository in use, verify that open branches must be updated before merging is permitted by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require status checks to pass before merging** and **Require branches to be up to date before merging** are checked.",
+ "AdditionalInformation": "",
+ "References": "https://github.blog/changelog/2022-02-03-more-ways-to-keep-your-pull-request-branch-up-to-date/",
+ "DefaultValue": "By default, there is no requirement to update a branch before merging it."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.11",
+ "Description": "Organizations should enforce a \"no open comments\" policy before allowing code change merging.",
+ "Checks": [
+ "repository_default_branch_requires_conversation_resolution"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Organizations should enforce a \"no open comments\" policy before allowing code change merging.",
+ "RationaleStatement": "In an open code change proposal, reviewers can leave comments containing their questions and suggestions. These comments can also include potential bugs and security issues. Requiring all comments on a code change proposal to be resolved before it can be merged ensures that every concern is properly addressed or acknowledged before the new code changes are introduced to the code base.",
+ "ImpactStatement": "Code change proposals containing open comments would not be able to be merged into the code base.",
+ "RemediationProcedure": "For each code repository in use, require open comments to be resolved before the relevant code change can be merged by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require conversation resolution before merging**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, verify that each merged code change does not contain open, unattended comments by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require conversation resolution before merging** is checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, code changes with open comments on them are able to be merged into the code \nbase."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.12",
+ "Description": "Ensure every commit in a pull request is signed and verified before merging.",
+ "Checks": [
+ "repository_default_branch_requires_signed_commits"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure every commit in a pull request is signed and verified before merging.",
+ "RationaleStatement": "Signing commits, or requiring to sign commits, gives other users confidence about the origin of a specific code change. It ensures that the author of the change is not hidden and is verified by the version control system, thus the change comes from a trusted source.",
+ "ImpactStatement": "Pull requests with unsigned commits cannot be merged.",
+ "RemediationProcedure": "For each repository in use, enforce the branch protection rule of requiring signed commits, and make sure only signed commits are capable of merging by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require signed commits**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "Ensure only signed commits can be merged for every branch, especially the main branch, via branch protection rules by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require signed commits** is checked.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.13",
+ "Description": "Linear history is the name for Git history where all commits are listed in chronological order, one after another. Such history exists if a pull request is merged either by rebase merge (re-order the commits history) or squash merge (squashes all commits to one). Ensure that linear history is required by requiring the use of rebase or squash merge when merging a pull request.",
+ "Checks": [
+ "repository_default_branch_requires_linear_history"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Linear history is the name for Git history where all commits are listed in chronological order, one after another. Such history exists if a pull request is merged either by rebase merge (re-order the commits history) or squash merge (squashes all commits to one). Ensure that linear history is required by requiring the use of rebase or squash merge when merging a pull request.",
+ "RationaleStatement": "Enforcing linear history produces a clear record of activity, and as such it offers specific advantages: it is easier to follow, easier to revert a change, and bugs can be found more easily.",
+ "ImpactStatement": "Pull request cannot be merged except squash or rebase merge.",
+ "RemediationProcedure": "For every code repository in use, perform the following steps to require linear history and/or allow only rebase merge and squash merge:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Require linear history**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, perform the following steps to verify that linear history is required and/or that only squash merge and rebase merge are allowed:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Require linear history** is checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.14",
+ "Description": "Ensure administrators are subject to branch protection rules.",
+ "Checks": [
+ "repository_default_branch_protection_applies_to_admins"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure administrators are subject to branch protection rules.",
+ "RationaleStatement": "Administrators by default are excluded from any branch protection rules. This means these privileged users (both on the repository and organization levels) are not subject to protections meant to prevent untrusted code insertion, including malicious code. This is extremely important since administrator accounts are often targeted for account hijacking due to their privileged role.",
+ "ImpactStatement": "Administrator users won't be able to push code directly to the protected branch without being compliant with listed branch protection rules.",
+ "RemediationProcedure": "For every code repository in use, enforce branch protection rules on administrators as well, by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Do not allow bypassing the above settings**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, validate branch protection rules also apply to administrator accounts by performing the next steps:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Do not allow bypassing the above settings** is checked.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule",
+ "DefaultValue": "Administrator accounts are not subject to branch protection rules by default."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.15",
+ "Description": "Ensure that only trusted users can push or merge new code to protected branches.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that only trusted users can push or merge new code to protected branches.",
+ "RationaleStatement": "Requiring that only trusted users may push or merge new changes reduces the risk of unverified code, especially malicious code, to a protected branch by reducing the number of trusted users who are capable of doing such.",
+ "ImpactStatement": "Only administrators and trusted users can push or merge to the protected branch.",
+ "RemediationProcedure": "For every code repository in use, allow only trusted and responsible users to push or merge new code by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4.Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Select **Restrict who can push to matching branches** and choose trusted and responsible users and teams who will have the permission to do so. \n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, ensure only trusted and responsible users can push or merge new code by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Restrict who can push to matching branches** is checked and that only trusted and responsible users and teams are selected.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.16",
+ "Description": "The \"Force Push\" option allows users with \"Push\" permissions to force their changes directly to the branch without a pull request, and thus should be disabled.",
+ "Checks": [
+ "repository_default_branch_disallows_force_push"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The \"Force Push\" option allows users with \"Push\" permissions to force their changes directly to the branch without a pull request, and thus should be disabled.",
+ "RationaleStatement": "The \"Force Push\" option allows users to override the existing code with their own code. This can lead to both intentional and unintentional data loss, as well as data infection with malicious code. Disabling the \"Force Push\" option prohibits users from forcing their changes to the master branch, which ultimately prevents malicious code from entering source code.",
+ "ImpactStatement": "Users cannot force push to protected branches.",
+ "RemediationProcedure": "For each repository in use, block the option to \"Force Push\" code by performing the following:\n\nEnsure that Trunk / Long-standing branches are protected by Policies and submitted to PR while applying the 4-eyes approach.\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Uncheck **Allow force pushes**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For every code repository in use, validate that no one can force push code by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Allow force pushes** is not checked.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.17",
+ "Description": "Ensure that users with only push access are incapable of deleting a protected branch.",
+ "Checks": [
+ "repository_default_branch_deletion_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that users with only push access are incapable of deleting a protected branch.",
+ "RationaleStatement": "When enabling deletion of a protected branch, any user with at least push access to the repository can delete a branch. This can be potentially dangerous, as a simple human mistake or a hacked account can lead to data loss if a branch is deleted. It is therefore crucial to prevent such incidents by denying protected branch deletion.",
+ "ImpactStatement": "Protected branches cannot be deleted.",
+ "RemediationProcedure": "For each repository that is being used, block the option to delete protected branches by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, click **Add rule**.\n5. If you add the rule, under \"Branch name pattern\", type the branch name or pattern you want to protect.\n6. Uncheck **Allow deletions**.\n7. Click **Create** or **Save changes**.",
+ "AuditProcedure": "For each repository that is being used, verify that protected branches cannot be deleted by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", verify that there is at least one rule for your main branch. If there is, click **Edit** to its right. If there isn't, you are not compliant.\n5. Ensure that **Allow deletions** is not checked.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.18",
+ "Description": "Ensure that every pull request is required to be scanned for risks.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that every pull request is required to be scanned for risks.",
+ "RationaleStatement": "Scanning pull requests to detect risks allows for early detection of vulnerable code and/or dependencies and helps mitigate potentially malicious code.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every repository in use, enforce risk scanning on every pull request by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Actions**.\n3. If the repository already has at least one workflow set up and running, click **New workflow** and go to step 5. If there are currently no workflows configured for the repository, go to the next step.\n4. Scroll down to the \"Security\" category and click **Configure** under the workflow you want to configure or click **View all** to see all available security workflows.\n5. On the right pane of the workflow page, click **Documentation** and follow the on-screen instructions to tailor the workflow to your needs.",
+ "AuditProcedure": "For each repository in use, ensure that every pull request must be scanned for risks by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Actions**.\n3. Ensure that at least one workflow is configured to run like that: \n```\non:\n push:\n branches: [ \"main\" ]\n pull_request:\n branches: [ \"main\" ]\n```\nand that it has a step that runs code scanning on the code.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.19",
+ "Description": "Ensure that changes in the branch protection rules are audited.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that changes in the branch protection rules are audited.",
+ "RationaleStatement": "Branch protection rules should be configured on every repository. The only users who may change such rules are administrators. In a case of an attack on an administrator account or of human error on the part of an administrator, protection rules could be disabled, and thus decrease source code confidentiality as a result. It is important to track and audit such changes to prevent potential incidents as soon as possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Use the audit log to audit changes in branch protection rules by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Archives\" section of the sidebar, click **Logs**, then click **Audit log**.\n4. Use the action qualifier in your query and look for **protected_branch** category. Ensure every action is reasonable and secure and investigate if not.",
+ "AuditProcedure": "Ensure changes in branch protection rules are audited by performing the following regularly:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Archives\" section of the sidebar, click **Logs**, then click **Audit log**.\n4. Use the action qualifier in your query and look for **protected_branch** category. Ensure every action is reasonable and secure and is investigated if not.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.1.20",
+ "Description": "Enforce branch protection on the default and main branch.",
+ "Checks": [
+ "repository_default_branch_protection_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.1 Code Changes",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Enforce branch protection on the default and main branch.",
+ "RationaleStatement": "The default or main branch of repositories is considered very important, as it is eventually gets deployed to the production. Therefore it needs protection. By enforcing branch protection rules on this branch, it is secured from unwanted or unauthorized changes. It can also be protected from untested and unreviewed changes and more.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Perform the following to enforce branch protection on the main branch:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Next to \"Branch protection rules\", click **Add rule**.\n5. Under \"Branch name pattern\", type the branch name or pattern you want to protect. Ensure it applies to the main branch name.\n6. Configure policies you want.\n7. Click Create.",
+ "AuditProcedure": "Perform the following to ensure branch protection is enforced on the main branch:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Code and automation\" section of the sidebar, click **Branches**.\n4. Under **Branch protection rules**, verify that there is a rule applied to the \"main\" or default branch.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.2.1",
+ "Description": "A SECURITY.md file is a security policy file that offers instruction on reporting security vulnerabilities in a project. When someone creates an issue within a specific project, a link to the SECURITY.md file will subsequently be shown.",
+ "Checks": [
+ "repository_public_has_securitymd_file"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "A SECURITY.md file is a security policy file that offers instruction on reporting security vulnerabilities in a project. When someone creates an issue within a specific project, a link to the SECURITY.md file will subsequently be shown.",
+ "RationaleStatement": "A SECURITY.md file provides users with crucial security information. It can also serve an important role in project maintenance, encouraging users to think ahead about how to properly handle potential security issues, updates, and general security practices.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Enforce that each public repository has a SECURITY.md file by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under the repository name, click **Security**.\n3. In the left sidebar, click **Security policy**.\n4. Click **Start setup**.\n5. In the new SECURITY.md file, add information about supported versions of your project and how to report a vulnerability.\n6. At the bottom of the page, type a commit message.\n7. Below the commit message fields, choose to create a new branch for your commit and then create a pull request.\n8. Click **Propose file change**.",
+ "AuditProcedure": "Verify that each public repository has a SECURITY.md file by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under the repository name, click **Security**.\n3. Verify that **Security policy** is enabled.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.2.2",
+ "Description": "Limit the ability to create repositories to trusted users and teams.",
+ "Checks": [
+ "organization_repository_creation_limited"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Limit the ability to create repositories to trusted users and teams.",
+ "RationaleStatement": "Restricting repository creation to trusted users and teams is recommended in order to keep the organization properly structured, track fewer items, prevent impersonation, and to not overload the version-control system. It will allow administrators easier source code tracking and management capabilities, as they will have fewer repositories to track. The process of detecting potential attacks also becomes far more straightforward, as well, since the easier it is to track the source code, the easier it is to detect malicious acts within it. Additionally, the possibility of a member creating a public repository and sharing the organization's data externally is significantly decreased.",
+ "ImpactStatement": "Specific users will not be permitted to create repositories.",
+ "RemediationProcedure": "Restrict repository creation to trusted users and teams only by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Repository creation\", unselect both options - **Public** and **Private**.\n5. Click **Save**.",
+ "AuditProcedure": "Verify that only trusted users and teams can create repositories by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Repository creation\", ensure that **Public** and **Private** are not checked. This means only owners are able to create repositories.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.2.3",
+ "Description": "Ensure only a limited number of trusted users can delete repositories.",
+ "Checks": [
+ "organization_repository_deletion_limited"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure only a limited number of trusted users can delete repositories.",
+ "RationaleStatement": "Restricting the ability to delete repositories protects the organization from intentional and unintentional data loss. This ensures that users cannot delete repositories or cause other potential damage — whether by accident or due to their account being hacked — unless they have the correct privileges.",
+ "ImpactStatement": "Certain users will not be permitted to delete repositories.",
+ "RemediationProcedure": "Enforce repository deletion by a few trusted and responsible users only by performing either of the following steps:\n\nIf Your organizations > Settings > Access > Member privileges > Allow members to delete or transfer repositories for this organization is selected, allow only trusted members to have admin privileges:\n1. In every repository, on GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings** and then in the \"Access\" section of the sidebar, click **Collaborators & teams**.\n3. Under \"Manage access\" use the dropdown **Role** menu to filter and search for admin members. Change their role by clicking the **Role** dropdown next to the username until there are only two trusted and qualified users with admin privileges. \n\nIf it is not selected, allow only trusted users to become an organization owner:\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click the name of your organization and under your organization name, click **People**.\n3. You will see a list of the people in your organization. Click Role and select Owners. Check every member you want to change permissions to. Above the list of members, use the drop-down menu and click Change role and choose Member > change role. Do that until there are only a few trusted and qualified users with organization owner privileges. \n\nIn any case, only members with administrator or organization owner privileges can delete repositories, regardless of your setting.",
+ "AuditProcedure": "Verify that only a limited number of trusted users can delete repositories by performing either of the following steps:\n\nIf Your organizations > Settings > Access > Member privileges > Allow members to delete or transfer repositories for this organization is selected, verify that every admin member is trusted by you:\n1. In every repository, on GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings** and then in the \"Access\" section of the sidebar, click **Collaborators & teams**.\n3. Under \"Manage access\" use the dropdown **Role** menu to filter and search for admin members. Verify that there are only two of them and that they are trusted and qualified. \n\nIf it is not selected, verify that every organization owner is trusted by you:\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click the name of your organization and under your organization name, click **People**.\n3. You will see a list of the people in your organization. Click Role and select Owners. Verify that there are only a few of them and that they are trusted and qualified. \n\nIn any case, only members with administrator or organization owner privileges can delete repositories, regardless of your setting.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Only organization owners or members with admin privileges can delete repositories."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.4",
+ "Description": "Ensure only trusted and responsible users can delete issues.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure only trusted and responsible users can delete issues.",
+ "RationaleStatement": "Issues are a way to keep track of things happening in repositories, such as setting new milestones or requesting urgent fixes. Deleting an issue is not a benign activity, as it might harm the development workflow or attempt to hide malicious behavior. Because of this, it should be restricted and allowed only by trusted and responsible users.",
+ "ImpactStatement": "Certain users will not be permitted to delete issues.",
+ "RemediationProcedure": "Restrict issue deletion to a few trusted and responsible users only by performing either of the following steps:\n\nIf Your organizations > Settings > Access > Member privileges > Allow members to delete issues for this organization is selected, allow only trusted members to have admin privileges:\n1. In every repository, on GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings** and then in the \"Access\" section of the sidebar, click **Collaborators & teams**.\n3. Under \"Manage access\" use the dropdown **Role** menu to filter and search for admin members. Change their role by clicking the **Role** dropdown next to the username until there are only two trusted and qualified users with admin privileges.\n\nIf it is not selected, allow only trusted users to become an organization owner:\n1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations.\n2. Click the name of your organization and under your organization name, click **People**.\n3. You will see a list of the people in your organization. Click **Role** and select **Owners**. Check every member you want to change permissions to. Above the list of members, use the drop-down menu and click **Change role** and choose Member > change role. Do that until there are only a few trusted and qualified users with organization owner privileges.\n\nIn any case, only members with administrator or organization owner privileges can delete issues, regardless of your setting.",
+ "AuditProcedure": "Verify that only a limited number of trusted users can delete issues by performing either of the following steps:\n\nIf Your organizations > Settings > Access > Member privileges > Allow members to delete issues for this organization is selected, verify that every admin member is trusted by you:\n1. In every repository, on GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings** and then in the \"Access\" section of the sidebar, click **Collaborators & teams**.\n3. Under \"Manage access\" use the dropdown **Role** menu to filter and search for admin members. Verify that there are only two of them and that they are trusted and qualified.\n\nIf it is not selected, verify that every organization owner is trusted by you:\n1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations.\n2. Click the name of your organization and under your organization name, click **People**.\n3. You will see a list of the people in your organization. Click **Role** and select **Owners**. Verify that there are only a few of them and that they are trusted and qualified.\n\nIn any case, only members with administrator or organization owner privileges can delete issues, regardless of your setting.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Only organization owners or members with admin privileges can delete issues."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.5",
+ "Description": "Track every fork of code and ensure it is accounted for.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Track every fork of code and ensure it is accounted for.",
+ "RationaleStatement": "A fork is a copy of a repository. On top of being a plain copy, any updates to the original repository itself can be pulled and reflected by the fork under certain conditions. A large number of repository copies (forks) become difficult to manage and properly secure. New and sensitive changes can often be pushed into a critical repository without developer knowledge of an updated copy of the very same repository. If there is no limit on doing this, then it is recommended to track and delete copies of organization repositories as needed.",
+ "ImpactStatement": "Disabling forks completely may slow down the development process as more actions will be necessary to take in order to fork a repository.",
+ "RemediationProcedure": "Track forks and examine them by performing the following on a regular basis:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Insights**.\n3. In the left sidebar, click **Forks**.\n4. Examine the forks listed there.",
+ "AuditProcedure": "Verify that the following steps are done regularly to track and examine forks:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Insights**.\n3. In the left sidebar, click **Forks**.\n4. Examine the forks listed there.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.2.6",
+ "Description": "Ensure every change in visibility of projects is tracked.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure every change in visibility of projects is tracked.",
+ "RationaleStatement": "Visibility of projects determines who can access a project and/or fork it: anyone, designated users, or only members of the organization. If a private project becomes public, this may point to a potential attack, which can ultimately lead to data loss, the leaking of sensitive information, and finally to a supply chain attack. It is crucial to track these changes in order to prevent such incidents.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Track every change in project visibility and investigate if suspicious behavior occurs, by performing the following regularly:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Archives\" section of the sidebar, click **Logs**, then click **Audit log**.\n4. Use the **repo** qualifier in your query and look for **access** category. Ensure every change is reasonable and secure and investigate if it is not.",
+ "AuditProcedure": "Ensure that every change in project visibility is tracked and investigated, by performing the following regularly:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Archives\" section of the sidebar, click **Logs**, then click **Audit log**.\n4. Use the **repo** qualifier in your query and look for **access** category. Ensure every change is reasonable and secure and is investigated if it is not.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.2.7",
+ "Description": "Track inactive repositories and remove them periodically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.2 Repository Management",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Track inactive repositories and remove them periodically.",
+ "RationaleStatement": "Inactive repositories (i.e., no new changes introduced for a long period of time) can enlarge the surface of a potential attack or data leak. These repositories are more likely to be improperly managed, and thus could possibly be accessed by a large number of users in an organization.",
+ "ImpactStatement": "Bug fixes and deployment of necessary changes could prove complicated for archived repositories.",
+ "RemediationProcedure": "Perform the following to review all inactive repositories and archive them periodically:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click on your organization name and then on **repositories**.\n3. Ensure every repository listed has been active in the last 3 to 6 months. Every repository that isn't active you should either review or archive by performing the next steps:\n 1. On GitHub.com, navigate to the main page of the repository.\n 2. Under your repository name, click **Settings**.\n 3. Under \"Danger Zone\", click **Archive this repository**.\n 4. Read the warnings.\n 5. Type the name of the repository you want to archive.\n 6. Click **I understand the consequences, archive this repository**.",
+ "AuditProcedure": "Perform the following to ensure that all the repositories in the organization are active, and those that are not reviewed or archived:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click on your organization name and then on **repositories**.\n3. Ensure every repository listed has been active in the last 3 to 6 months. If it's not, then ensure it is archived or reviewed regularly.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.1",
+ "Description": "Track inactive user accounts and periodically remove them.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Track inactive user accounts and periodically remove them.",
+ "RationaleStatement": "User accounts that have been inactive for a long period of time are enlarging the surface of attack. Inactive users with high-level privileges are of particular concern, as these accounts are more likely to be targets for attackers. This could potentially allow access to large portions of an organization should such an attack prove successful. It is recommended to remove them as soon as possible in order to prevent this.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If you have GitHub Enterprise Cloud, perform the following:\n\n1. In the top-right corner of GitHub.com, click your profile photo, then click **Your enterprises**.\n2. In the list of enterprises, click the enterprise you want to view.\n3. In the enterprise account sidebar, click **Compliance**.\n4. To download your Dormant Users (beta) report as a CSV file, under \"Other\", click **Download**.\n5. Find the users listed in the file under **Your organizations** > your organization > **People** and select them.\n6. Click **Remove from organization** and **Remove members**.",
+ "AuditProcedure": "If you have GitHub Enterprise Cloud, perform the following:\n\n1. In the top-right corner of GitHub.com, click your profile photo, then click **Your enterprises**.\n2. In the list of enterprises, click the enterprise you want to view.\n3. In the enterprise account sidebar, click **Compliance**.\n4. To download your Dormant Users (beta) report as a CSV file, under \"Other\", click **Download**.\n5. Verify that there are no users listed.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.2",
+ "Description": "Limit ability to create teams to trusted and specific users.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Limit ability to create teams to trusted and specific users.",
+ "RationaleStatement": "The ability to create new teams should be restricted to specific members in order to keep the organization orderly and ensure users have access to only the lowest privilege level necessary. Teams typically inherit permissions from their parent team, thus if base permissions are less restricted and any user has the ability to create a team, a permission leverage could occur in which certain data is made available to users who should not have access to it. Such a situation could potentially lead to the creation of shadow teams by an attacker. Restricting team creation will also reduce additional clutter in the organizational structure, and as a result will make it easier to track changes and anomalies.",
+ "ImpactStatement": "Only specific users will be able to create new teams.",
+ "RemediationProcedure": "For every organization, limit team creation to specific, trusted users by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Team creation rules\", deselect **Allow members to create teams**.\n5. Click **Save**.",
+ "AuditProcedure": "For every organization, ensure that team creation is limited to specific, trusted users by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Team creation rules\", verify that **Allow members to create teams** is not selected.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.3",
+ "Description": "Ensure the organization has a minimum number of administrators.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure the organization has a minimum number of administrators.",
+ "RationaleStatement": "Organization administrators have the highest level of permissions, including the ability to add/remove collaborators, create or delete repositories, change branch protection policy, and convert to a publicly-accessible repository. Due to the permissive access granted to an organization administrator, it is highly recommended to keep the number of administrator accounts as minimal as possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set the minimum number of administrators in your organization by performing the following:\n\n1. In the top right corner of GitHub, click your profile photo, then click **Your profile**.\n2. On the left side of your profile page, under \"Organizations\", click the icon for your organization.\n3. Under your organization name, click **People**. \n4. In the Role drop-down, choose **Owners**.\n5. Select the person or people you'd like to remove from owner role.\n6. Above the list of members, use the drop-down menu and click Change role.\n7. Select **Member**, then click **Change role**.",
+ "AuditProcedure": "Verify the minimum number of administrators in your organization by performing the following:\n\n1. In the top right corner of GitHub, click your profile photo, then click **Your profile**.\n2. On the left side of your profile page, under \"Organizations\", click the icon for your organization.\n3. Under your organization name, click **People**. \n4. In the Role drop-down, choose **Owners**.\n5. If there are minimum number of members in the list, you are compliant.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.4",
+ "Description": "Require collaborators from outside the organization to use Multi-Factor Authentication (MFA) in addition to a standard user name and password when authenticating to the source code management platform.",
+ "Checks": [
+ "organization_members_mfa_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Require collaborators from outside the organization to use Multi-Factor Authentication (MFA) in addition to a standard user name and password when authenticating to the source code management platform.",
+ "RationaleStatement": "By default every user authenticates within the system by password only. If the password of a user is compromised, however, the user account and every repository to which they have access are in danger of data loss, malicious code commits, and data theft. It is therefore recommended that each user has Multi-Factor Authentication enabled. This adds an additional layer of protection to ensure the account remains secure even if the user's password is compromised.",
+ "ImpactStatement": "A member without enabled Multi-Factor Authentication cannot contribute to the project. They must enable Multi-Factor Authentication a before they can contribute any code.",
+ "RemediationProcedure": "For each repository in use, enforce Multi-Factor Authentication is the only way to authenticate for contributors, by doing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Under \"Authentication\", select **Require two-factor authentication for everyone in your organization**, then click **Save**.",
+ "AuditProcedure": "For each repository in use, verify that Multi-Factor Authentication is enforced for contributors and is the only way to authenticate, by doing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Under \"Authentication\", check if **Require two-factor authentication for everyone in your organization** is checked. If so, you are compliant.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.5",
+ "Description": "Require members of the organization to use Multi-Factor Authentication (MFA) in addition to a standard user name and password when authenticating to the source code management platform.",
+ "Checks": [
+ "organization_members_mfa_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Require members of the organization to use Multi-Factor Authentication (MFA) in addition to a standard user name and password when authenticating to the source code management platform.",
+ "RationaleStatement": "By default every user authenticates within the system by password only. If the password of a user is compromised, however, the user account and every repository to which they have access are in danger of data loss, malicious code commits, and data theft. It is therefore recommended that each user has Multi-Factor Authentication enabled. This adds an additional layer of protection to ensure the account remains secure even if the user's password is compromised.",
+ "ImpactStatement": "Members will be removed from the organization if they don't have Multi-Factor Authentication already enabled. If this is the case, it is recommended that an invitation be sent to reinstate the user's access and former privileges. They must enable Multi-Factor Authentication to accept the invitation.",
+ "RemediationProcedure": "For every organization that exists in your GitHub platform, enforce Multi-Factor Authentication and define it as the only way to authenticate, by doing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Under \"Authentication\", select **Require two-factor authentication for everyone in your organization**, then click **Save**.\n5. If prompted, read the information about members and outside collaborators who will be removed from the organization. Type your organization's name to confirm the change, then click **Remove members & require two-factor authentication**.",
+ "AuditProcedure": "For every organization that exists in your GitHub platform, verify that Multi-Factor Authentication is enforced and is the only way to authenticate, by doing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Under \"Authentication\", check if **Require two-factor authentication for everyone in your organization** is checked. If so, you are compliant.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.6",
+ "Description": "Existing members of an organization can invite new members to join, however new members must only be invited with their company-approved email.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Existing members of an organization can invite new members to join, however new members must only be invited with their company-approved email.",
+ "RationaleStatement": "Ensuring new members of an organization have company-approved email prevents existing members of the organization from inviting arbitrary new users to join. Without this verification, they can invite anyone who is using the organization's version control system or has an active email account, thus allowing outside users (and potential threat actors) to easily gain access to company private code and resources. This practice will subsequently reduce the chance of human error or typos when inviting a new member.",
+ "ImpactStatement": "Existing members would not be able to invite new users who do not have a company-approved email address.",
+ "RemediationProcedure": "For each organization, allow only users with company-approved email to be invited. If a user was invited without company-approved email, perform the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click the name of your organization and under your organization name, click **People**.\n3. On the People tab, click **Invitations**. Next to the username or email address of the person whose invitation you'd like to cancel, click **Edit invitation**.\n4. To cancel the user's invitation to join your organization, click **Cancel invitation**.",
+ "AuditProcedure": "For each organization in use, verify for every invitation that the invited email address is company-approved by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Click the name of your organization and under your organization name, click **People**.\n3. On the People tab, click **Invitations**. Verify that each invitation email is company approved by your company.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.7",
+ "Description": "Ensure every repository has two users with administrative permissions.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure every repository has two users with administrative permissions.",
+ "RationaleStatement": "Repository administrators have the highest permissions to said repository. These include the ability to add/remove collaborators, change branch protection policy, and convert to a publicly-accessible repository. Due to the liberal access granted to a repository administrator, it is highly recommended that only two contributors occupy this role.",
+ "ImpactStatement": "Removing administrative users from a repository would result in them losing high-level access to that repository.",
+ "RemediationProcedure": "For every repository in use, set two administrators by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Collaborators & teams**.\n4. Under **Manage access**, find the team or person whose you'd like to revoke admin permissions, then select the Role drop-down and click a new role.",
+ "AuditProcedure": "For every repository in use, verify there are two administrators by performing the following:\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Collaborators & teams**.\n4. Under **Manage access**, verify that there are only 2 members with Admin permission.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.8",
+ "Description": "Base permissions define the permission level automatically granted to all organization members. Define strict base access permissions for all of the repositories in the organization, including new ones.",
+ "Checks": [
+ "organization_default_repository_permission_strict"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Base permissions define the permission level automatically granted to all organization members. Define strict base access permissions for all of the repositories in the organization, including new ones.",
+ "RationaleStatement": "Defining strict base permissions is the best practice in every role-based access control (RBAC) system. If the base permission is high — for example, \"write\" permission — every member of the organization will have \"write\" permission to every repository in the organization. This will apply regardless of the specific permissions a user might need, which generally differ between organization repositories. The higher the permission, the higher the risk for incidents such as bad code commit or data breach. It is therefore recommended to set the base permissions to the strictest level possible.",
+ "ImpactStatement": "Users might not be able to access organization repositories or perform some acts as commits. These specific permissions should be granted individually for each user or team, as needed.",
+ "RemediationProcedure": "Set strict base permissions for the organization repositories with the next steps:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Base permissions\", use the drop-down to select new base permissions - \"Read\" or \"None\".\n5. Review the changes. To confirm, click **Change default permission to PERMISSION**.",
+ "AuditProcedure": "Verify that strict base permissions are set for the organization repositories by doing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Access\" section of the sidebar, click **Member privileges**.\n4. Under \"Base permissions\", verify that it is set to \"Read\" or \"None\". If it does, you are compliant.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Read permission"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.9",
+ "Description": "Confirm the domains an organization owns with a \"Verified\" badge.",
+ "Checks": [
+ "organization_verified_badge"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Confirm the domains an organization owns with a \"Verified\" badge.",
+ "RationaleStatement": "Verifying the organization's domain gives developers assurance that a given domain is truly the official home for a public organization. Attackers can pretend to be an organization and steal information via a faked/spoof domain, therefore the use of a \"Verified\" badge instills more confidence and trust between developers and the open-source community.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Only if you have an enterprise account, verify the organization's domains and secure a \"Verified\" badge next to its name by performing the following:\n\n1. In the top-right corner of GitHub.com, click your profile photo, then click **Your enterprises**.\n2. In the list of enterprises, click the enterprise you want to view. Then in the enterprise account sidebar, click **Settings**.\n3. Under \"Settings\", click **Verified & approved domains**.\n4. Click **Add a domain**.\n5. In the domain field, type the domain you'd like to verify, then click **Add domain**.\n6. Follow the instructions under **Add a DNS TXT record** to create a DNS TXT record with your domain hosting service. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing ENTERPRISE-ACCOUNT with the name of your enterprise account, and example.com with the domain you'd like to verify. You should see your new TXT record listed in the command output.\n```\ndig _github-challenge-ENTERPRISE-ACCOUNT.DOMAIN-NAME +nostats +nocomments +nocmd TXT\n```\n7. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your enterprise account's approved and verified domains.\n8. To the right of the domain that's pending verification, click the 3-dots, then click **Continue verifying**. Click **Verify**.\n9. Optionally, after the \"Verified\" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service.",
+ "AuditProcedure": "Only if you have an enterprise account, view the enterprise organization profile page and ensure it has a \"Verified\" badge in it.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.10",
+ "Description": "Restrict the Source Code Management (SCM) organization's email notifications to approved domains only.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Restrict the Source Code Management (SCM) organization's email notifications to approved domains only.",
+ "RationaleStatement": "Restricting Source Code Management email notifications to verified domains only prevents data leaks, as personal emails and custom domains are more prone to account takeover via DNS hijacking or password breach.",
+ "ImpactStatement": "Only members with approved email would be able to receive Source Code Management notifications.",
+ "RemediationProcedure": "Only if you have an enterprise account, restrict Source Code Management email notifications to approved domains only by performing the following:\n\n1. In the top-right corner of GitHub.com, click your profile photo, then click **Your enterprises**.\n2. In the list of enterprises, click the enterprise you want to view. Then in the enterprise account sidebar, click **Settings**.\n3. Under \"Settings\", click **Verified & approved domains**.\n4. Under \"Notification preferences\", select **Restrict email notifications to only approved or verified domains**.\n5. Click **Save**.",
+ "AuditProcedure": "Only if you have an enterprise account, ensure Source Code Management email notifications are restricted to approved domains only by performing the following:\n\n1. In the top-right corner of GitHub.com, click your profile photo, then click **Your enterprises**.\n2. In the list of enterprises, click the enterprise you want to view. Then in the enterprise account sidebar, click **Settings**.\n3. Under \"Settings\", click **Verified & approved domains**.\n4. Under \"Notification preferences\", verify that **Restrict email notifications to only approved or verified domains** is selected.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.11",
+ "Description": "As an organization, become an SSH Certificate Authority and provide SSH keys for accessing repositories.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "As an organization, become an SSH Certificate Authority and provide SSH keys for accessing repositories.",
+ "RationaleStatement": "There are two ways for remotely working with Source Code Management: via HTTPS, which requires authentication by user/password, or via SSH, which requires the use of SSH keys. SSH authentication is better in terms of security; key creation and distribution, however, must be done in a secure manner. This can be accomplished by implementing SSH certificates, which are used to validate the server's identity. A developer will not be able to connect to a Git server if its key cannot be verified by the SSH Certificate Authority (CA) server.\nAs an organization, one can verify the SSH certificate signature used to authenticate if a CA is defined and used. This ensures that only verified developers can access organization repositories, as their SSH key will be the only one signed by the CA certificate. This reduces the risk of misuse and malicious code commits.",
+ "ImpactStatement": "Members with unverified keys will not be able to clone organization repositories. Signing, certification, and verification might also slow down the development process.",
+ "RemediationProcedure": "Only if you have an enterprise account, deploy an SSH Certificate Authority server and configure it to provide an SSH certificate with which to sign keys by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. To the right of \"SSH Certificate Authorities\", click **New CA**.\n5. Under \"Key,\" paste your public SSH key.\n6. Click **Add CA**.\n7. Click **Save**.",
+ "AuditProcedure": "Only if you have an enterprise account, verify that the enterprise organization has an SSH Certificate Authority server and provides an SSH certificate with which to sign keys by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Verify that there's an SSH certificate authority listed there.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.12",
+ "Description": "Limit Git access based on IP addresses by having a allowlist of IP addresses from which connection is possible.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Limit Git access based on IP addresses by having a allowlist of IP addresses from which connection is possible.",
+ "RationaleStatement": "Allowing access to Git repositories (source code) only from specific IP addresses adds yet another layer of restriction and reduces the risk of unauthorized connection to the organization's assets. This will prevent attackers from accessing Source Code Management (SCM), as they would first need to know the allowed IP addresses to gain access to them.",
+ "ImpactStatement": "Only members with allowlisted IP addresses will be able to access the organization's Git repositories.",
+ "RemediationProcedure": "Only if you have an enterprise account, create an IP allowlist and forbid all other IPs from accessing the source code by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. At the bottom of the \"IP allow list\" section, enter an IP address, or a range of addresses in CIDR notation. Optionally, enter a description of the allowed IP address or range.\n5. Click **Add**.\n6. After that, under \"IP allow list\", select **Enable IP allow list**.\n7. Click **Save**.",
+ "AuditProcedure": "Only if you have an enterprise account, in every organization of yours, ensure access is allowed only by IP allowlist, and that access is forbidden for all other IPs by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Authentication security**.\n4. Verify that there's an IP address, or a range of addresses in CIDR notation listed. Also verify that **Enable IP allow list** is selected.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.3.13",
+ "Description": "Track code anomalies.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.3 Contribution Access",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Track code anomalies.",
+ "RationaleStatement": "Carefully analyze any code anomalies within the organization. For example, a code anomaly could be a push made outside of working hours. Such a code push has a higher likelihood of being the result of an attack, as most if not all members of the organization would likely be outside the office. Another example is an activity that exceeds the average activity of a particular user.\nTracking and auditing such behaviors creates additional layers of security and can aid in early detection of potential attacks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every repository in use, track and investigate anomalous code behavior and activity.",
+ "AuditProcedure": "For every repository in use, ensure code anomalies relevant to the organization are promptly investigated.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.4.1",
+ "Description": "Ensure an administrator approval is required when installing applications.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.4 Third-Party",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure an administrator approval is required when installing applications.",
+ "RationaleStatement": "Applications are typically automated integrations that improve the workflow of an organization. They are written by third-party developers, and therefore should be validated before using in case they're malicious or not trustable. Because administrators are expected to be the most qualified and trusted members of the organization, they should review the applications being installed and decide whether they are both trusted and necessary.",
+ "ImpactStatement": "Applications will not be installed without administrator approval.",
+ "RemediationProcedure": "Require an administrator approval for every installed application:\n\na. For GitHub Apps, you are compliant by default. That is because by default only organization owners and administrators can install them.\n\nb. For OAuth Apps, perform the following:\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Third-party Access\" section of the sidebar, click **OAuth application policy**.\n4. Under \"Third-party application access policy\", click **Setup application access restrictions**.\n5. After you review the information about third-party access restrictions, click **Restrict third-party application access**.",
+ "AuditProcedure": "Verify that applications are installed only after receiving administrator approval:\n\na. For GitHub Apps, you are compliant by default. That is because by default only organization owners and administrators can install them.\n\nb. For OAuth Apps, perform the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Third-party Access\" section of the sidebar, click **OAuth application policy**.\n4. Under \"Third-party application access policy\" verify that the policy status is **Access restricted**.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Maintainers are organization owners."
+ }
+ ]
+ },
+ {
+ "Id": "1.4.2",
+ "Description": "Ensure stale (inactive) applications are reviewed and removed if no longer in use.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.4 Third-Party",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure stale (inactive) applications are reviewed and removed if no longer in use.",
+ "RationaleStatement": "Applications that have been inactive for a long period of time are enlarging the surface of attack for data leaks. They are more likely to be improperly managed, and could possibly be accessed by third-party developers as a tool for collecting internal data of the organization or repository in which they are installed. It is important to remove these inactive applications as soon as possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Review all stale applications and periodically remove them.",
+ "AuditProcedure": "Verify that all the applications in the organization are actively used, and remove those that are no longer in use.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.4.3",
+ "Description": "Ensure installed application permissions are limited to the lowest privilege level required.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.4 Third-Party",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure installed application permissions are limited to the lowest privilege level required.",
+ "RationaleStatement": "Applications are typically automated integrations that can improve the workflow of an organization. They are written by third-party developers, and therefore should be reviewed carefully before use. It is recommended to use the \"least privilege\" principle, granting applications the lowest level of permissions required. This may prevent harm from a potentially malicious application with unnecessarily high-level permissions leaking data or modifying source code.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Grant permissions to applications by the \"least privilege\" principle, meaning the lowest possible permission necessary:\n\na. For GitHub Apps, perform the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Integrations\" section of the sidebar, click **GitHub Apps**.\n4. Next to every GitHub App, click **Configure**.\n5. Review the GitHub App's permissions and repository access. Edit the permissions granted to the least possible. For example, restrict the number of repositories the App can access.\n6. Click **Save**.",
+ "AuditProcedure": "Verify that each installed application has the least privilege needed:\n\na. For GitHub Apps, perform the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the \"Integrations\" section of the sidebar, click **GitHub Apps**.\n4. Next to every GitHub App, click **Configure**.\n5. Review the GitHub App's permissions and repository access. Verify that the App permissions are the least possible and that it can access only necessary repositories.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.4.4",
+ "Description": "Use only secured webhooks in the source code management platform.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.4 Third-Party",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use only secured webhooks in the source code management platform.",
+ "RationaleStatement": "A webhook is an event listener, attached to critical and sensitive parts of the software delivery process. It is triggered by a list of events (such as a new code being committed), and when triggered, the webhook sends out a notification with some payload to specific internet endpoints. Since the payload of the webhook contains sensitive organization data, it's important all webhooks are directed to an endpoint (URL) protected by SSL verification (HTTPS). This helps ensure that the data sent is delivered to securely without any man-in-the-middle, who could easily access and even alter the payload of the request.",
+ "ImpactStatement": "Perform the following to ensure all webhooks used are secured (HTTPS):\n\n1. Navigate to your organization or repository and select **Settings**.\n2. Select **Webhooks** on the side menu.\n3. Verify that each webhook URL starts with 'https'.",
+ "RemediationProcedure": "Perform the following to secure all webhooks used(over HTTPS):\n\n1. Navigate to your organization or repository and select **Settings**.\n2. Select **Webhooks** on the side menu.\n3. Find the webhooks that starts with 'http' and not 'https'.\n4. Ensure the endpoint (URL) of the webhook listens to secured port (443) and uses certificate.\n5. Click **Edit**.\n6. Change the payload URL to https and ensure **Enable SSL verification** is checked.\n7. Click **Update webhook**.",
+ "AuditProcedure": "Perform the following to secure all webhooks used(over HTTPS):\n\n1. Navigate to your organization or repository and select **Settings**.\n2. Select **Webhooks** on the side menu.\n3. Ensure all webhooks starts with 'https'.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.1",
+ "Description": "Detect and prevent sensitive data in code, such as confidential ID numbers, passwords, etc.",
+ "Checks": [
+ "repository_secret_scanning_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent sensitive data in code, such as confidential ID numbers, passwords, etc.",
+ "RationaleStatement": "Having sensitive data in the source code makes it easier for attackers to maliciously use such information. In order to avoid this, designate scanners to identify and prevent the existence of sensitive data in the code.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every repository in use, designate scanners to identify and prevent sensitive data in code by performing the following (enterprise only):\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Code security and analysis**.\n4. Scroll down to the bottom of the page and click **Enable** for secret scanning.",
+ "AuditProcedure": "For every repository in use, verify that scanners are set to identify and prevent the existence of sensitive data in code by performing the following (enterprise only):\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the \"Security\" section of the sidebar, click **Code security and analysis**.\n4. Scroll down to the bottom of the page. If you see a **Disable** button, it means that secret scanning is already enabled for the repository.",
+ "AdditionalInformation": "By January 2023, this feature is supposed to be open to all plans. Until then it is only for enterprise users.",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.2",
+ "Description": "Detect and prevent misconfigurations and insecure instructions in CI pipelines",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent misconfigurations and insecure instructions in CI pipelines",
+ "RationaleStatement": "Detecting and fixing misconfigurations or insecure instructions in CI pipelines decreases the risk for a successful attack through or on the CI pipeline. The more secure the pipeline, the less risk there is for potential exposure of sensitive data, a deployment being compromised, or external access mistakenly being granted to the CI infrastructure or the source code.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set a CI instructions scanning tool to identify and prevent misconfigurations and insecure instructions and scans all CI pipelines.",
+ "AuditProcedure": "Verify that a CI instructions scanning tool is set to identify and prevent misconfigurations and insecure instructions and that it scans all CI pipelines.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.3",
+ "Description": "Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files.",
+ "RationaleStatement": "Detecting and fixing misconfigurations and/or insecure instructions in IaC (Infrastructure as Code) files decreases the risk for data leak or data theft. It is important to secure IaC instructions in order to prevent further problems of deployment, exposed assets, or improper configurations, which can ultimately lead to easier ways to attack and steal organization data.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every repository that holds IaC instructions files, set a scanning tool to identify and prevent misconfigurations and insecure instructions.",
+ "AuditProcedure": "For every repository that holds IaC instructions files, verify that a scanning tool is set to identify and prevent misconfigurations and insecure instructions.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.4",
+ "Description": "Detect and prevent known open source vulnerabilities in the code.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent known open source vulnerabilities in the code.",
+ "RationaleStatement": "Open source code blocks are used a lot in developed software. This has its own advantages, but it also has risks. Because the code is open for everyone, it means that attackers can publish or add malicious code to these open-source code blocks, or use their knowledge to find vulnerabilities in an existing code. Detecting and fixing such code vulnerabilities, by SCA (Software Composition Analysis) prevents insecure flaws from reaching production. It gives another opportunity for developers to secure the source code before it is deployed in production, where it is far more exposed and vulnerable to attacks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every repository that is in use, set a scanning tool to identify and prevent code vulnerabilities by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under the repository name, click **Security**.\n3. To the right of \"Code scanning alerts\", click **Set up code scanning**.\n4. Under \"Get started with code scanning\", click Set up this workflow on a workflow of your choice.\n5. To customize how code scanning scans your code, edit the workflow.\n6. Use the **Start commit** drop-down and type a commit message.\n7. Choose whether you'd like to commit directly to the default branch or create a new branch and start a pull request.\n8. Click **Commit new file** or **Propose new file**.",
+ "AuditProcedure": "For every repository that is in use, verify that a scanning tool is set to identify and prevent code vulnerabilities by performing the following:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under the repository name, click **Security**.\n3. Verify that \"Code scanning alerts\" is **Enabled** or that there is a workflow that scans your code.",
+ "AdditionalInformation": "All public repositories in all plans can use code scanning in GitHub. In private repositories, only GitHub Enterprise can use code scanning.",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.5",
+ "Description": "Detect, prevent and monitor known open-source vulnerabilities in packages that are being used.",
+ "Checks": [
+ "repository_dependency_scanning_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect, prevent and monitor known open-source vulnerabilities in packages that are being used.",
+ "RationaleStatement": "Open-source vulnerabilities might exist before one starts to use a package, but they are also discovered over time. New attacks and vulnerabilities are announced every now and then. It is important to keep track of these and to monitor whether the dependencies used are affected by the recent vulnerability. Detecting and fixing those packages' vulnerabilities decreases the attack surface within deployed and running applications that use such packages. It prevents security flaws from reaching the production environment which could eventually lead to a security breach.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set scanners that will monitor, identify, and prevent open-source vulnerabilities in packages by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**. In the \"Security\" section of the sidebar, click **Code security and analysis**.\n3. Under \"Code security and analysis\", to the right of Dependabot alerts, click **Disable all** or **Enable all**.\n4. Check the **Enable by default for new repositories** option and then click **Enable Dependabot alerts**.\n\nIt is also recommended to use another additional solution for package scanning because GitHub doesn't always recognize the vulnerabilities.",
+ "AuditProcedure": "Verify that scanners are set to monitor, identify, and prevent open-source vulnerabilities in packages by performing the following:\n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**. In the \"Security\" section of the sidebar, click **Code security and analysis**.\n3. Verify that the Dependabot alerts is enabled and that **Enable by default for new repositories** is checked.\n\nIt is also recommended to verify that you're using another additional solution for package scanning because GitHub doesn't always recognize the vulnerabilities.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "1.5.6",
+ "Description": "Detect open-source license problems in used dependencies and fix them.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Source Code",
+ "Subsection": "1.5 Code Risks",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect open-source license problems in used dependencies and fix them.",
+ "RationaleStatement": "A software license is a legal document that establishes several key conditions between a software company or developer and a user in order to allow the use of software. Software licenses have the potential to create code dependencies. Not following the conditions in the software license can also lead to lawsuits. When using packages with a software license, especially commercial ones (which are the most permissive), it is important to verify what is allowed by that license in order to be protected against lawsuits.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Designate a license scanning tool to identify open-source license problems and fix them and scan every package you use.",
+ "AuditProcedure": "Ensure a license scanning tool is set up to identify open-source license problems and that every package you use is scanned by it.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.1",
+ "Description": "Ensure each pipeline has a single responsibility in the build process.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure each pipeline has a single responsibility in the build process.",
+ "RationaleStatement": "Build pipelines generally have access to multiple secrets depending on their purposes. There are, for example, secrets of the test environment for the test phase, repository and artifact credentials for the build phase, etc. Limiting access to these credentials/secrets is therefore recommended by dividing pipeline responsibilities, as well as having a dedicated pipeline for each phase with the lowest privilege instead of a single pipeline for all. This will ensure that any potential damage caused by attacks on a workflow will be limited.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Divide each multi-responsibility pipeline into multiple pipelines, each having a single responsibility with the least privilege. Additionally, create all new pipelines with a sole purpose going forward.",
+ "AuditProcedure": "For each pipeline, ensure it has only one responsibility in the build process.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.2",
+ "Description": "Ensure the pipeline orchestrator and its configuration are immutable.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure the pipeline orchestrator and its configuration are immutable.",
+ "RationaleStatement": "An immutable infrastructure is one that cannot be changed during execution of the pipeline. This can be done, for example, by using Infrastructure as Code for configuring the pipeline and the pipeline environment. Utilizing such infrastructure creates a more predictable environment because updates will require re-deployment to prevent any previous configuration from interfering. Because it is dependent on automation, it is easier to revert changes. Testing code is also simpler because it is based on virtualization. Most importantly, an immutable pipeline infrastructure ensures that a potential attacker seeking to compromise the build environment itself would not be able to do so if the orchestrator, its configuration, and any other component cannot be changed. Verifying that all aspects of the pipeline infrastructure and configuration are immutable therefore keeps them safe from malicious tampering attempts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Use an immutable pipeline orchestrator and ensure that its configuration and all other aspects of the built environment are immutable, as well.",
+ "AuditProcedure": "Verify that the pipeline orchestrator, its configuration, and all other aspects of the build environment are immutable.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.3",
+ "Description": "Keep build logs of the build environment detailing configuration and all activity within it. Also, consider to store them in a centralized organizational log store.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Keep build logs of the build environment detailing configuration and all activity within it. Also, consider to store them in a centralized organizational log store.",
+ "RationaleStatement": "Logging the environment is important for two primary reasons: one, for debugging and investigating the environment in case of a bug or security incident; and two, for reproducing the environment easily when needed. Storing these logs in a centralized organizational log store allows the organization to generate useful insights and identify anomalies in the build process faster.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Keep logs of the build environment. For example, use the .buildinfo file for Debian build workers. Also, store the logs in a centralized organizational log store.",
+ "AuditProcedure": "Verify that the build environment is logged and stored in a centralized organizational log store.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.4",
+ "Description": "Automate the creation of the build environment.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Automate the creation of the build environment.",
+ "RationaleStatement": "Automating the deployment of the build environment reduces the risk for human mistakes — such as a wrong configuration or exposure of sensitive data — because it requires less human interaction and intervention. It also eases re-deployment of the environment. It is best to automate with Infrastructure as Code because it offers more control over changes made to the environment creation configuration and stores to a version control platform.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Automate the deployment of the build environment.",
+ "AuditProcedure": "Verify that the deployment of the build environment is automated and can be easily redeployed.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.5",
+ "Description": "Restrict access to the build environment (orchestrator, pipeline executor, their environment, etc.) to trusted and qualified users only.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Restrict access to the build environment (orchestrator, pipeline executor, their environment, etc.) to trusted and qualified users only.",
+ "RationaleStatement": "A build environment contains sensitive data such as environment variables, secrets, and the source code itself. Any user that has access to this environment can make changes to the build process, including changes to the code within it. Restricting access to the build environment to trusted and qualified users only will reduce the risk for mistakes such as exposure of secrets or misconfiguration. Limiting access also reduces the number of accounts that are vulnerable to hijacking in order to potentially harm the build environment.",
+ "ImpactStatement": "Reducing the number of users who have access to the build process means those users would lose their ability to make direct changes to that process.",
+ "RemediationProcedure": "Restrict access to the build environment to trusted and qualified users.",
+ "AuditProcedure": "Verify each build environment is accessible only to known and authorized users.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.6",
+ "Description": "Require users to login in to access the build environment - where the orchestrator, the pipeline executer, where the build workers are running, etc.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Require users to login in to access the build environment - where the orchestrator, the pipeline executer, where the build workers are running, etc.",
+ "RationaleStatement": "Requiring users to authenticate and disabling anonymous access to the build environment allows organization to track every action on that environment, good or bad, to its actor. This will help recognizing attack and its attacker because the authentication is required.",
+ "ImpactStatement": "Anonymous users won't be able to access the build environment.",
+ "RemediationProcedure": "Require authentication to access the build environment and disable anonymous access.",
+ "AuditProcedure": "Ensure authentication is required to access the build environment.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.7",
+ "Description": "Build tools providers offer a secure way to store secrets that should be used during the build process.\nThese secrets will often be credentials used to access other tools, for example for pulling code or for uploading artifacts.\nAccess to these secrets can be defined on various scopes, for example in github it could be on an organization level or a repository level and there is also control on whether these secrets are passed to forked pull request.\nTo protect these critical assets it is important to choose the most restrictive scope necessary.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Build tools providers offer a secure way to store secrets that should be used during the build process.\nThese secrets will often be credentials used to access other tools, for example for pulling code or for uploading artifacts.\nAccess to these secrets can be defined on various scopes, for example in github it could be on an organization level or a repository level and there is also control on whether these secrets are passed to forked pull request.\nTo protect these critical assets it is important to choose the most restrictive scope necessary.",
+ "RationaleStatement": "Allowing over permissive access to these secrets may affect on their exposure.\nFor example if a secret is defined in an organization level, and users can create new repositories, there is a scenario where a user can create a new repo and run a controlled build just to exfiltrate these secrets.",
+ "ImpactStatement": "Increased risk of exposure of build related secrets.",
+ "RemediationProcedure": "For each build tool, review the secrets defined and their permissions scope and change over permissive scopes to more restrictive ones based on the required access.",
+ "AuditProcedure": "For each build tool in use, review the secrets defined and the permission scopes they are assigned.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.8",
+ "Description": "Scan the build infrastructure and its dependencies for vulnerabilities. It is recommended that this be done automatically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Scan the build infrastructure and its dependencies for vulnerabilities. It is recommended that this be done automatically.",
+ "RationaleStatement": "Automatic scanning for vulnerabilities detects known vulnerabilities in the tooling used by the build infrastructure and its dependencies. These vulnerabilities can lead\nto a potentially massive breach if not handled as fast as possible, as attackers might also be\naware of such vulnerabilities.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set an automated vulnerability scanning for your build infrastructure.",
+ "AuditProcedure": "Verify that your build infrastructure is automatically scanned for vulnerabilities.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.9",
+ "Description": "Do not use default passwords of build tools and components.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not use default passwords of build tools and components.",
+ "RationaleStatement": "Sometimes build tools and components are provided with default passwords for the first login. This password is intended to be used only on the first login and should be changed immediately after. Using the default password substantially increases the attack risk. It is especially important to ensure that default passwords are not used in build tools and components.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each build tool, change the default password.",
+ "AuditProcedure": "For each build tool, ensure the password used is not the default one.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.10",
+ "Description": "Use secured webhooks of the build environment.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use secured webhooks of the build environment.",
+ "RationaleStatement": "Webhooks are used for triggering an HTTP request based on an action made in the platform. Typically, build environment feature webhooks for a pipeline trigger based on source code event. Since webhooks are an HTTP POST request, they can be malformed if not secured over SSL. To prevent a potential hack and compromise of the webhook or to the environment or web server excepting the request, use only secured webhooks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each webhook in use, change it to secured (over HTTPS).",
+ "AuditProcedure": "For each webhook in use, ensure it is secured (HTTPS).",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.1.11",
+ "Description": "Ensure the build environment has a minimum number of administrators.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.1 Build Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure the build environment has a minimum number of administrators.",
+ "RationaleStatement": "Build environment administrators have the highest level of permissions, including the ability to add/remove users, create or delete pipelines, control build workers, change build trigger permissions and more. Due to the permissive access granted to a build environment administrator, it is highly recommended to keep the number of administrator accounts as minimal as possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set the minimum number of administrators in the build environment.",
+ "AuditProcedure": "Verify that the build environment has only the minimum number of administrators.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.1",
+ "Description": "Use a clean instance of build worker for every pipeline run.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use a clean instance of build worker for every pipeline run.",
+ "RationaleStatement": "Using a clean instance of build worker for every pipeline run eliminates the risks of data theft, data integrity breaches, and unavailability. It limits the pipeline's access to data stored on the file system from previous runs, and the cache is volatile. This prevents malicious changes from affecting other pipelines or the Continuous Integration/Continuous Delivery system itself.",
+ "ImpactStatement": "Data and cache will not be saved in different pipeline runs.",
+ "RemediationProcedure": "Create a clean build worker for every pipeline that is being run, or use build platform-hosted runners, as they typically offer a clean instance for every run.",
+ "AuditProcedure": "Ensure that every pipeline that is being run has its own clean, new runner.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.2",
+ "Description": "A worker’s environment can be passed (for example, a pod in a Kubernetes cluster in which an environment variable is passed to it). It also can be pulled, like a virtual machine that is installing a package. Ensure that the environment and commands are passed to the workers and not pulled from it.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "A worker’s environment can be passed (for example, a pod in a Kubernetes cluster in which an environment variable is passed to it). It also can be pulled, like a virtual machine that is installing a package. Ensure that the environment and commands are passed to the workers and not pulled from it.",
+ "RationaleStatement": "Passing an environment means additional configuration happens in the build time phase and not in run time. It will also pass locally and not remotely. Passing a worker environment, instead of pulling it from an outer source, reduces the possibility for an attacker to gain access and potentially pull malicious code into it. By passing locally and not pulling from remote, there is also less chance of an attack based on the remote connection, such as a man-in-the-middle or malicious scripts that can run from remote. This therefore prevents possible infection of the build worker.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each build worker, pass its environment and commands to it instead of pulling it.",
+ "AuditProcedure": "For each build worker, ensure its environment and commands are passed and not pulled.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.3",
+ "Description": "Separate responsibilities in the build workflow, such as testing, compiling, pushing artifacts, etc., to different build workers so that each worker will have a single duty.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Separate responsibilities in the build workflow, such as testing, compiling, pushing artifacts, etc., to different build workers so that each worker will have a single duty.",
+ "RationaleStatement": "Separating duties and allocating them to many workers makes it easier to verify each step in the build process and ensure there is no corruption. It also limits the effect of an attack on a build worker, as such an attack would be less critical if the worker has less access and duties that are subject to harm.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each build worker, limit its responsibility to one duty.",
+ "AuditProcedure": "For each build worker, ensure it has the least responsibility possible, preferably only one duty.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.4",
+ "Description": "Ensure that build workers have minimal network connectivity.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that build workers have minimal network connectivity.",
+ "RationaleStatement": "Restricting the network connectivity of build workers decreases the possibility that an attacker would be capable of entering the organization from the outside. If the build workers are connected to the public internet without any restriction, it is far simpler for attackers to compromise them. Limiting network connectivity between build workers also protects the organization in case an attacker was successful and subsequently attempts to spread the attack to other components of the environment.",
+ "ImpactStatement": "Developers will not have connectivity to every resource they might need from the outside. Workers will also only be able to exchange data through shareable storage.",
+ "RemediationProcedure": "Limit the network connectivity of build workers, environment, and any other components to the necessary minimum.",
+ "AuditProcedure": "Verify that build workers, environment, and any other components have only the required minimum of network connectivity.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.5",
+ "Description": "Add traces to build workers' operating systems and installed applications so that in run time, collected events can be analyzed to detect suspicious behavior patterns and malware.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Add traces to build workers' operating systems and installed applications so that in run time, collected events can be analyzed to detect suspicious behavior patterns and malware.",
+ "RationaleStatement": "Build workers are exposed to data exfiltration attacks, code injection attacks, and more while running. It is important to secure them from such attacks by enforcing run-time security on the build worker itself. This will identify attempted attacks in real time and prevent them.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Deploy and enforce a run-time security solution on build workers.",
+ "AuditProcedure": "Verify that a run-time security solution is enforced on every active build worker.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.6",
+ "Description": "Scan build workers for vulnerabilities. It is recommended that this be done automatically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Scan build workers for vulnerabilities. It is recommended that this be done automatically.",
+ "RationaleStatement": "Automatic scanning for vulnerabilities detects known weaknesses in environmental sources in use, such as docker images or kernel versions. Such vulnerabilities can lead to a massive breach if these environments are not replaced as fast as possible, since attackers also know about these vulnerabilities and often try to take advantage of them. Setting automatic scanning which scans environmental sources ensures that if any new vulnerability is revealed, it can be replaced quickly and easily. This protects the worker from being exposed to attacks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each build worker, automatically scan its environmental sources, such as docker image, for vulnerabilities.",
+ "AuditProcedure": "For each build worker, ensure the environmental sources it uses are scanned for vulnerabilities.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.7",
+ "Description": "Store the deployment configuration of build workers in a version control platform, such as Github.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Store the deployment configuration of build workers in a version control platform, such as Github.",
+ "RationaleStatement": "Build workers are a sensitive part of the build phase. They generally have access to the code repository, the Continuous Integration platform, the deployment platform, etc. This means that an attacker gaining access to a build worker may compromise other platforms in the organization and cause a major incident. One thing that can protect workers is to ensure that their deployment configuration is safe and well-configured. Storing the deployment configuration in version control enables more observability of these configurations because everything is catalogued in a single place. It adds another layer of security, as every change will be reviewed and noticed, and thus malicious changes will theoretically occur less. In the case of a mistake, bug, or security incident, it also offers an easier way to \"revert\" back to a safe version or add a \"hot fix\" quickly.",
+ "ImpactStatement": "Changes in deployment configuration may only be applied by declaration in the version control platform. This could potentially slow down the development process.",
+ "RemediationProcedure": "Document and store every deployment configuration of build workers in a version control platform.",
+ "AuditProcedure": "Verify that the deployment configuration of build workers is stored in a version control platform.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.2.8",
+ "Description": "Monitor the resource consumption of build workers and set alerts for high consumption that can lead to resource exhaustion.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.2 Build Worker",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Monitor the resource consumption of build workers and set alerts for high consumption that can lead to resource exhaustion.",
+ "RationaleStatement": "Resource exhaustion is when machine resources or services are highly consumed until exhausted. Resource exhaustion may lead to DOS (Denial of Service). When such a situation happens to build workers, it slows down and even stops the build process, which harms the production of artifacts and the organization's ability to deliver software on schedule. To prevent that, it is recommended to monitor resources consumption in the build workers and set alerts to notify when they are highly consumed. That way resource exhaustion can be acknowledged and prevented at an early stage.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set reources consumption monitoring for each build worker.",
+ "AuditProcedure": "Verify that there is monitoring of resources consumption for each build worker.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.1",
+ "Description": "Use pipeline as code for build pipelines and their defined steps.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use pipeline as code for build pipelines and their defined steps.",
+ "RationaleStatement": "Storing pipeline instructions as code in a version control system means automation of the build steps and less room for human error, which could potentially lead to a security breach. Additionally, It creates the ability to revert back to a previous pipeline configuration in order to pinpoint the affected change should a malicious incident occur.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Convert pipeline instructions into code-based syntax and upload them to the organization's version control platform.",
+ "AuditProcedure": "Verify that all build steps are defined as code and stored in a version control system.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.2",
+ "Description": "Define clear expected input and output for each build stage.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Define clear expected input and output for each build stage.",
+ "RationaleStatement": "In order to have more control over data flow in the build pipeline, clearly define the input and output of the pipeline steps. If anything malicious happens during the build stage, it will be recognized more easily and stand out as an anomaly.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each build stage, clearly define what is expected for input and output.",
+ "AuditProcedure": "For each build stage, verify that the expected input and output are clearly defined.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.3",
+ "Description": "Write pipeline output artifacts to a secured storage repository.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Write pipeline output artifacts to a secured storage repository.",
+ "RationaleStatement": "To maintain output artifacts securely and reduce the potential surface for attack, store such artifacts separately in secure storage. This separation enforces the Single Responsibility Principle by ensuring the orchestration platform will not be the same as the artifact storage, which reduces the potential harm of an attack. Using the same security considerations as the input (for example, the source code) will protect artifacts stored and will make it harder for a malicious actor to successfully execute an attack.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline that produces output artifacts, write them to a secured storage repository.",
+ "AuditProcedure": "For each pipeline that produces output artifacts, ensure that they're written to a secured storage repository.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.4",
+ "Description": "Track and review changes to pipeline files.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Track and review changes to pipeline files.",
+ "RationaleStatement": "Pipeline files are sensitive files. They have the ability to access sensitive data and control the build process, thus it is just as important to review changes to pipeline files as it is to verify source code. Malicious actors can potentially add harmful code to these files, which may lead to sensitive data exposure and hijacking of the build environment or artifacts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline file, track changes to it and review them.",
+ "AuditProcedure": "For each pipeline file, ensure changes to it are being tracked and reviewed.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.5",
+ "Description": "Restrict access to pipeline triggers.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Restrict access to pipeline triggers.",
+ "RationaleStatement": "Build pipelines are used for multiple reasons. Some are very sensitive, such as pipelines which deploy to production. In order to protect the environment from malicious acts or human mistakes, such as a developer deploying a bug to production, it is important to apply the Least Privilege principle to pipeline triggering. This principle requires restrictions placed on which users can run which pipeline. It allows for sensitive pipelines to only be run by administrators, who are generally the most trusted and skilled members of the organization.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every pipeline in use, grant only the necessary users permission to trigger it.",
+ "AuditProcedure": "For every pipeline in use, verify only the necessary users have permission to trigger it.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.6",
+ "Description": "Scan the pipeline for misconfigurations. It is recommended that this be performed automatically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Scan the pipeline for misconfigurations. It is recommended that this be performed automatically.",
+ "RationaleStatement": "Automatic scans for misconfigurations detect human mistakes and misconfigured tasks. This protects the environment from backdoors caused by such mistakes, which create easier access for attackers. For example, a task that mistakenly configures credentials to persist on the disk makes it easier for an attacker to steal them. This type of incident can be prevented by auto-scanning.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline, set automated misconfiguration scanning.",
+ "AuditProcedure": "For each pipeline, verify that it is automatically scanned for misconfigurations.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.7",
+ "Description": "Scan pipelines for vulnerabilities. It is recommended that this be implemented automatically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Scan pipelines for vulnerabilities. It is recommended that this be implemented automatically.",
+ "RationaleStatement": "Automatic scanning for vulnerabilities detects known vulnerabilities in pipeline instructions and components, allowing faster patching in case one is found. These vulnerabilities can lead to a potentially massive breach if not handled as fast as possible, as attackers might also be aware of such vulnerabilities.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline, set automated vulnerability scanning.",
+ "AuditProcedure": "For each pipeline, verify that it is automatically scanned for vulnerabilities.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.3.8",
+ "Description": "Detect and prevent sensitive data, such as confidential ID numbers, passwords, etc., in pipelines.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.3 Pipeline Instructions",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Detect and prevent sensitive data, such as confidential ID numbers, passwords, etc., in pipelines.",
+ "RationaleStatement": "Sensitive data in pipeline configuration, such as cloud provider credentials or repository credentials, create vulnerabilities with which malicious actors could steal such information if they gain access to a pipeline. In order to mitigate this, set scanners that will identify and prevent the existence of sensitive data in the pipeline.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every pipeline that is in use, set scanners that will identify and prevent sensitive data within it.",
+ "AuditProcedure": "For every pipeline that is in use, verify that scanners are set to identify and prevent the existence of sensitive data within it.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.1",
+ "Description": "Sign all artifacts in all releases with user or organization keys.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Sign all artifacts in all releases with user or organization keys.",
+ "RationaleStatement": "Signing artifacts is used to validate both their integrity and security. Organizations signal that artifacts may be trusted and they themselves produced them by ensuring that every artifact is properly signed. The presence of this signature also makes potentially malicious activity far more difficult.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every artifact in every release, verify that all are properly signed.",
+ "AuditProcedure": "Ensure every artifact in every release is signed.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.2",
+ "Description": "External dependencies may be public packages needed in the pipeline, or perhaps the public image being used for the build worker. Lock these external dependencies in every build pipeline.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "External dependencies may be public packages needed in the pipeline, or perhaps the public image being used for the build worker. Lock these external dependencies in every build pipeline.",
+ "RationaleStatement": "External dependencies are sources of code that aren't under organizational control. They might be intentionally or unintentionally infected with malicious code or have known vulnerabilities, which could result in sensitive data exposure, data harvesting, or the erosion of trust in an organization. Locking each external dependency to a specific, safe version gives more control and less chance for risk.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For all external dependencies being used in pipelines, verify they are locked.",
+ "AuditProcedure": "Ensure every external dependency being used in pipelines is locked.",
+ "AdditionalInformation": "",
+ "References": "https://argon.io/blog/pipeline-composition-analysis-how-your-ci-pipeline-presents-new-opportunities-for-attackers/",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.3",
+ "Description": "Validate every dependency of the pipeline before use.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Validate every dependency of the pipeline before use.",
+ "RationaleStatement": "To ensure that a dependency used in a pipeline is trusted and has not been infected by malicious actor (for example, the codecov incident), validate dependencies before using them. This can be accomplished by comparing the checksum of the dependency to its checksum in a trusted source. If a difference arises, this is a sign that an unknown actor has interfered and may have added malevolent code. If this dependency is used, it will infect the environment, which could end in a massive breach and leave the organization exposed to data leaks, etc.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every dependency used in every pipeline, validate each one.",
+ "AuditProcedure": "For every dependency used in every pipeline, ensure it has been validated.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.4",
+ "Description": "Verify that the build pipeline creates reproducible artifacts, meaning that an artifact of the build pipeline is the same in every run when given the same input.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Verify that the build pipeline creates reproducible artifacts, meaning that an artifact of the build pipeline is the same in every run when given the same input.",
+ "RationaleStatement": "A reproducible build is a build that produces the same artifact when given the same input data. Ensuring that the build pipeline produces the same artifact when given the same input helps verify that no change has been made to the artifact. This action allows an organization to trust that its artifacts are built only from safe code that has been reviewed and tested and has not been tainted or changed abruptly.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Create build pipelines that produce the same artifact given the same input (for example, artifacts that do not rely on timestamps).",
+ "AuditProcedure": "Ensure that build pipelines create reproducible artifacts.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.5",
+ "Description": "SBOM (Software Bill of Materials) is a file that specifies each component of software or a build process. Generate an SBOM after each run of a pipeline.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "SBOM (Software Bill of Materials) is a file that specifies each component of software or a build process. Generate an SBOM after each run of a pipeline.",
+ "RationaleStatement": "Generating a Software Bill of Materials after each run of a pipeline will validate the integrity and security of that pipeline. Recording every step or component role in the pipeline ensures that no malicious acts have been committed during the pipeline's run.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline, configure it to produce a Software Bill of Materials on every run.",
+ "AuditProcedure": "For each pipeline, ensure it produces a Software Bill of Materials on every run.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "2.4.6",
+ "Description": "SBOM (Software Bill of Materials) is a file that specifies each component of software or a build process. It should be generated after every pipeline run. After it is generated, it must then be signed.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Build Pipelines",
+ "Subsection": "2.4 Pipeline Integrity",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "SBOM (Software Bill of Materials) is a file that specifies each component of software or a build process. It should be generated after every pipeline run. After it is generated, it must then be signed.",
+ "RationaleStatement": "Software Bill of Materials (SBOM) is a file used to validate the integrity and security of a build pipeline. Signing it ensures that no one tampered with the file when it was delivered. Such interference can happen if someone tries to hide unusual activity. Validating the SBOM signature can detect this activity and prevent much greater incident.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each pipeline, configure it to sign its produced Software Bill of Materials on every run.",
+ "AuditProcedure": "For each pipeline, ensure it signs the Software Bill of Materials it produces on every run.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.1",
+ "Description": "Ensure third-party artifacts and open-source libraries in use are trusted and verified.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure third-party artifacts and open-source libraries in use are trusted and verified.",
+ "RationaleStatement": "Verify third-party artifacts used in code are trusted and have not been infected by a malicious actor before use. This can be accomplished, for example, by comparing the checksum of the dependency to its checksum in a trusted source. If a difference arises, this may be a sign that someone interfered and added malicious code. If this dependency is used, it will infect the environment and could end in a massive breach, leaving the organization exposed to data leaks and more.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Verify every GitHub action (building block of a GitHub workflow) in use by performing the following: \n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the left sidebar, click **Actions**, then click **General**.\n4. Under \"Policies\", check **Allow OWNER, and select non-OWNER, actions and reusable workflows**, and then **Allow actions created by GitHub**.\n5. Click **Save**.\n\nAlternatively, perform the following for each repository where GitHub actions are used:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the left sidebar, click **Actions**, then click **General**.\n4. Under \"Actions permissions\", check **Allow OWNER, and select non-OWNER, actions and reusable workflows**, and then **Allow actions created by GitHub**.\n5. Click **Save**.",
+ "AuditProcedure": "For every GitHub action (building block of a GitHub workflow), ensure verification before use by performing the following: \n\n1. In the top right corner of GitHub.com, click your profile photo, then click **Your organizations**.\n2. Next to the organization, click **Settings**.\n3. In the left sidebar, click **Actions**, then click **General**.\n4. Under \"Policies\", ensure **Allow OWNER, and select non-OWNER, actions and reusable workflows**, and **Allow actions created by GitHub** are checked.\n\nAlternatively, perform the following for each repository where GitHub actions are used:\n\n1. On GitHub.com, navigate to the main page of the repository.\n2. Under your repository name, click **Settings**.\n3. In the left sidebar, click **Actions**, then click **General**.\n4. Under \"Actions permissions\", ensure **Allow OWNER, and select non-OWNER, actions and reusable workflows** and **Allow actions created by GitHub** are checked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.2",
+ "Description": "A Software Bill Of Materials (SBOM) is a file that specifies each component of software or a build process. Require an SBOM from every third-party provider.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "A Software Bill Of Materials (SBOM) is a file that specifies each component of software or a build process. Require an SBOM from every third-party provider.",
+ "RationaleStatement": "A Software Bill of Materials (SBOM) for every third-party artifact helps to ensure an artifact is safe to use and fully compliant. This file lists all important metadata, especially all the dependencies of an artifact, and allows for verification of each dependency. If one of the dependencies/artifacts are attacked or has a new vulnerability (for example, the \"SolarWinds\" or even \"log4j\" attacks), it is easier to detect what has been affected by this incident because dependencies in use are listed in the SBOM file.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every third-party dependency in use, require a Software Bill of Materials from its supplier.",
+ "AuditProcedure": "For every third-party dependency in use, ensure it has a Software Bill of Materials.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.3",
+ "Description": "Require and verify signed metadata of the build process for all dependencies in use.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Require and verify signed metadata of the build process for all dependencies in use.",
+ "RationaleStatement": "The metadata of a build process lists every action that took place during an artifact build. It is used to ensure that an artifact has not been compromised during the build, that no malicious code was injected into it, and that no nefarious dependencies were added during the build phase. This creates trust between user and vendor that the software supplied is exactly the software that was promised. Signing this metadata adds a checksum to ensure there have been no revisions since its creation, as this checksum changes when the metadata is altered. Verification of proper metadata signature with Certificate Authority confirms that the signature was produced by a trusted entity.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each artifact in use, require and verify signed metadata of the build process.",
+ "AuditProcedure": "For each artifact used, ensure it was supplied with verified and signed metadata of its build process. The signature should be the organizational signature and should be verifiable by common Certificate Authority servers.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.4",
+ "Description": "Monitor, or ask software suppliers to monitor, dependencies between open-source components in use.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Monitor, or ask software suppliers to monitor, dependencies between open-source components in use.",
+ "RationaleStatement": "Monitoring dependencies between open-source components helps to detect if software has fallen victim to attack on a common open-source component. Swift detection can aid in quick application of a fix. It also helps find potential compliance problems with components usage. Some dependencies might not be compatible with the organization's policies, and other dependencies might have a license that is not compatible with how the organization uses this specific dependency. If dependencies are monitored, such situations can be detected and mitigated sooner, potentially deterring malicious attacks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each open-source component, monitor its dependencies.",
+ "AuditProcedure": "For each open-source component, ensure its dependencies are monitored.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.5",
+ "Description": "Prioritize trusted package registries over others when pulling a package.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Prioritize trusted package registries over others when pulling a package.",
+ "RationaleStatement": "When pulling a package by name, the package manager might look for it in several package registries, some of which may be untrusted or badly configured. If the package is pulled from such a registry, there is a higher likelihood that it could prove malicious. In order to avoid this, configure packages to be pulled from trusted package registries.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each package to be downloaded, configure it to be downloaded from a trusted source.",
+ "AuditProcedure": "For each package registry in use, ensure it is trusted.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.6",
+ "Description": "A Software Bill of Materials (SBOM) is a file that specifies each component of software or a build process. When using a dependency, demand its SBOM and ensure it is signed for validation purposes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "A Software Bill of Materials (SBOM) is a file that specifies each component of software or a build process. When using a dependency, demand its SBOM and ensure it is signed for validation purposes.",
+ "RationaleStatement": "A Software Bill of Materials (SBOM) creates trust between its provider and its users by ensuring that the software supplied is the software described, without any potential interference in between. Signing an SBOM creates a checksum for it, which will change if the SBOM's content was changed. With that checksum, a software user can be certain nothing had happened to it during the supply chain, engendering trust in the software. When there is no such trust in the software, the risk surface is increased because one cannot know if the software is potentially vulnerable. Demanding a signed SBOM and validating it decreases that risk.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every artifact supplied, require and verify a signed Software Bill of Materials from its supplier.",
+ "AuditProcedure": "For every artifact supplied, ensure it has a validated, signed Software Bill of Materials.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.7",
+ "Description": "Pin dependencies to a specific version. Avoid using the \"latest\" tag or broad version.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Pin dependencies to a specific version. Avoid using the \"latest\" tag or broad version.",
+ "RationaleStatement": "When using a wildcard version of a package, or the \"latest\" tag, the risk of encountering a new, potentially malicious package increases. The \"latest\" tag pulls the last package pushed to the registry. This means that if an attacker pushes a new, malicious package successfully to the registry, the next user who pulls the \"latest\" will pull it and risk attack. This same rule applies to a wildcard version - assuming one is using version v1.*, it will install the latest version of the major version 1, meaning that if an attacker can push a malicious package with that same version, those using it will be subject to possible attack. By using a secure, verified version, use is restricted to this version only and no other may be pulled, decreasing the risk for any malicious package.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every dependency in use, pin to a specific version.",
+ "AuditProcedure": "For every dependency in use, ensure it is pinned to a specific version.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.1.8",
+ "Description": "Use packages that are more than 60 days old.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.1 Third-Party Packages",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Use packages that are more than 60 days old.",
+ "RationaleStatement": "Third-party packages are a major risk since an organization cannot control their source code, and there is always the possibility these packages could be malicious. It is therefore good practice to remain cautious with any third-party or open-source package, especially new ones, until they can be verified that they are safe to use. Avoiding a new package allows the organization to fully examine it, its maintainer, and its behavior, and gives enough time to determine whether or not to use it.",
+ "ImpactStatement": "Developers may not use packages that are less than 60 days old.",
+ "RemediationProcedure": "If a package used is less than 60 days old, stop using it and find another solution.",
+ "AuditProcedure": "For every package used, ensure it is more than 60 days old.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.1",
+ "Description": "Enforce a policy for dependency usage across the organization. For example, disallow the use of packages less than 60 days old.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.2 Validate Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Enforce a policy for dependency usage across the organization. For example, disallow the use of packages less than 60 days old.",
+ "RationaleStatement": "Enforcing a policy for dependency usage in an organization helps to manage dependencies across the organization and ensure that all usage is compliant with security policy. If, for example, the policy limits the package managers that can be used, enforcing it will make sure that every dependency is installed only from these package managers, and limit the risk of installing from any untrusted source.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Enforce policies for dependency usage across the organization.",
+ "AuditProcedure": "Verify that a policy for dependency usage is enforced across the organization.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.2",
+ "Description": "Automatically scan every package for vulnerabilities.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.2 Validate Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Automatically scan every package for vulnerabilities.",
+ "RationaleStatement": "Automatic scanning for vulnerabilities detects known vulnerabilities in packages and dependencies in use, allowing faster patching when one is found. Such vulnerabilities can lead to a massive breach if not handled as fast as possible, as attackers will also know about those vulnerabilities and swiftly try to take advantage of them. Scanning packages regularly for vulnerabilities can also verify usage compliance with the organization's security policy.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set automatic scanning of packages for vulnerabilities.",
+ "AuditProcedure": "Ensure automatic scanning of packages for vulnerabilities is enabled.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.3",
+ "Description": "A software license is a document that provides legal conditions and guidelines for the use and distribution of software, usually defined by the author. It is recommended to scan for any legal implications automatically.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.2 Validate Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "A software license is a document that provides legal conditions and guidelines for the use and distribution of software, usually defined by the author. It is recommended to scan for any legal implications automatically.",
+ "RationaleStatement": "When using packages with software licenses, especially commercial ones which tend to be the strictest, it is important to verify that the use of the package meets the conditions of the license. If the use of the package violates the licensing agreement, it exposes the organization to possible lawsuits. Scanning used packages for such license implications leads to faster detection and quicker fixes of such violations, and also reduces the risk for a lawsuit.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set automatic package scanning for license implications.",
+ "AuditProcedure": "Ensure license implication rules are configured and are scanned automatically.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "3.2.4",
+ "Description": "Scan every package automatically for ownership change.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Dependencies",
+ "Subsection": "3.2 Validate Packages",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Scan every package automatically for ownership change.",
+ "RationaleStatement": "A change in package ownership is not a regular action. In some cases it can lead to a massive problem (for example, the \"event-stream\" incident). Open-source contributors are not always trusted, since by its very nature everyone can contribute. This means malicious actors can become contributors as well. Package maintainers might transfer their ownership to someone they do not know if maintaining the package is too much for them, in some cases without the other user's knowledge. This has led to known security breaches in the past. It is best to be aware of such activity as soon as it happens and to carefully examine the situation before continuing using the package in order to determine its safety.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Set automatic scanning of packages for ownership change.",
+ "AuditProcedure": "Ensure automatic scanning of packages for ownership change is set.",
+ "AdditionalInformation": "",
+ "References": "https://blog.npmjs.org/post/182828408610/the-security-risks-of-changing-package-owners.html:https://blog.npmjs.org/post/180565383195/details-about-the-event-stream-incident",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.1.1",
+ "Description": "Configure the build pipeline to sign every artifact it produces and verify that each artifact has the appropriate signature.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.1 Verification",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Configure the build pipeline to sign every artifact it produces and verify that each artifact has the appropriate signature.",
+ "RationaleStatement": "A cryptographic signature can be used to verify artifact authenticity. The signature created with a certain key is unique and not reversible, thus making it unique to the author. This means that an attacker tampering with a signed artifact will be noticed immediately using a simple verification step because the signature will change. Signing artifacts by the build pipeline that produces them ensures the integrity of those artifacts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Sign every artifact produced with the build pipeline that created it. Configure the build pipeline to sign each artifact.\n\nSteps from GitHub Documentation:\n\nYou can follow the steps below to sign artifacts in GitHub actions. The trick involves loading in your private key into GitHub Actions using the gpg command-line commands.\n\nExport your gpg private key from the system that you have created it.\nFind your key-id (using gpg --list-secret-keys --keyid-format=long)\nExport the gpg secret key to an ASCII file using gpg --export-secret-keys -a <key-id> > secret.txt\nEdit secret.txt using a plain text editor, and replace all newlines with a literal \"\\n\" until everything is on a single line\nSet up GitHub Actions secrets\nCreate a secret called OSSRH_GPG_SECRET_KEY using the text from your edited secret.txt file (the whole text should be in a single line)\nCreate a secret called OSSRH_GPG_SECRET_KEY_PASSWORD containing the password for your gpg secret key\nCreate a GitHub Actions step to install the gpg secret key\nAdd an action similar to:\n```\n- id: install-secret-key\n name: Install gpg secret key\n run: |\n cat <(echo -e \"${{ secrets.OSSRH_GPG_SECRET_KEY }}\") | gpg --batch --import\n gpg --list-secret-keys --keyid-format LONG\n```\nVerify that the secret key is shown in the GitHub Actions logs\nYou can remove the output from list secret keys if you are confident that this action will work, but it is better to leave it in there\nBring it all together, and create a GitHub Actions step to publish\nAdd an action similar to:\n```\n- id: publish-to-central\n name: Publish to Central Repository\n env:\n MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}\n MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}\n run: |\n mvn \\\n --no-transfer-progress \\\n --batch-mode \\\n -Dgpg.passphrase=${{ secrets.OSSRH_GPG_SECRET_KEY_PASSWORD }} \\\n clean deploy\n```\nAfter a couple of hours, verify that the artifact got published to The Central Repository",
+ "AuditProcedure": "Verify that the build pipeline signs every new artifact it produces and all artifacts are signed.\n\nThere are many different signing tools or options each have there own method or commands to verify that the code or package created is signed.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds:https://gist.github.com/sualeh/ae78dc16123899d7942bc38baba5203c",
+ "DefaultValue": "Artifacts are not signed by Default."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.2",
+ "Description": "Encrypt artifacts before they are distributed and ensure only trusted platforms have decryption capabilities.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.1 Verification",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Encrypt artifacts before they are distributed and ensure only trusted platforms have decryption capabilities.",
+ "RationaleStatement": "Build artifacts might contain sensitive data such as production configurations. In order to protect them and decrease the risk for breach, it is recommended to encrypt them before delivery. Encryption makes data unreadable, so even if attackers gain access to these artifacts, they won't be able to harvest sensitive data from them without the decryption key.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Encrypt every artifact before distribution.",
+ "AuditProcedure": "Ensure every artifact is encrypted before it is delivered.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Artifacts do not get encrypted by default."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.3",
+ "Description": "Grant decryption capabilities of artifacts only to trusted and authorized platforms.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.1 Verification",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Grant decryption capabilities of artifacts only to trusted and authorized platforms.",
+ "RationaleStatement": "Build artifacts might contain sensitive data such as production configuration. To protect them and decrease the risk of a breach, it is recommended to encrypt them before delivery. This will make them unreadable for every unauthorized user who doesn't have the decryption key. By implementing this, the decryption capabilities become overly sensitive in order to prevent a data leak or theft. Ensuring that only trusted and authorized platforms can decrypt the organization's packages decreases the possibility for an attacker to gain access to the critical data in artifacts.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Grant decryption capabilities of the organization's artifacts only for trusted and authorized platforms.",
+ "AuditProcedure": "Ensure only trusted and authorized platforms have decryption capabilities of the organization's artifacts.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.1",
+ "Description": "Software certification is used to verify the safety of certain software usage and to establish trust between the supplier and the consumer. Any artifact can be certified. Limit the authority to certify different artifacts.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Software certification is used to verify the safety of certain software usage and to establish trust between the supplier and the consumer. Any artifact can be certified. Limit the authority to certify different artifacts.",
+ "RationaleStatement": "Artifact certification is a powerful tool in establishing trust. Clients use a software certificate to verify that the artifact is safe to use according to their security policies. Because of this, certifying artifacts is considered sensitive. If an artifact is for debugging or internal use, or if it were compromised, the organization would not want certification. An attacker gaining access to both certificate authority and the artifact registry might also be able to certify its own artifact and cause a major breach. To prevent these issues, limit which artifacts can be certified by which platform so there will be minimal access to certification.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Limit which artifact can be certified by which authority.",
+ "AuditProcedure": "Ensure only certain artifacts can be certified by certain parties.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.2",
+ "Description": "Minimize ability to upload artifacts to the lowest number of trusted users possible.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Minimize ability to upload artifacts to the lowest number of trusted users possible.",
+ "RationaleStatement": "Artifacts might contain sensitive data. Even the simplest mistake can also lead to trust issues with customers and harm the integrity of the product. To decrease these risks, allow only trusted and qualified users to upload new artifacts. Those users are less likely to make mistakes. Having the lowest number of such users possible will also decrease the risk of hacked user accounts, which could lead to a massive breach or artifact compromising.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Allow only trusted and qualified users to upload new artifacts and limit them in number.",
+ "AuditProcedure": "Ensure only trusted and qualified users can upload new artifacts, and that their number is the lowest possible.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.3",
+ "Description": "Enforce Multi-Factor Authentication (MFA) for user access to the package registry.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Enforce Multi-Factor Authentication (MFA) for user access to the package registry.",
+ "RationaleStatement": "By default, every user authenticates to the system by password only. If a user's password is compromised, the user account and all its related packages are in danger of data theft and malicious builds. It is therefore recommended that each user enables Multi-Factor Authentication. This additional step guarantees that the account stays secure even if the user's password is compromised, as it adds another layer of authentication.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each package registry in use, enforce Multi-Factor Authentication as the only way to authenticate.",
+ "AuditProcedure": "For each package registry in use, verify that Multi-Factor Authentication is enforced and is the only way to authenticate.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.4",
+ "Description": "Manage users and their access to the package registry with an external authentication server and not with the package registry itself.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Manage users and their access to the package registry with an external authentication server and not with the package registry itself.",
+ "RationaleStatement": "Some package registries offer a tool for user management, aside from the main Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) server of the organization. That tool usually offers simple authentication and role-based permissions, which might not be granular enough. Having multiple user management tools in the organization could result in confusion and privilege escalation, as there will be more to manage. To avoid a situation where users escalate their privileges because someone missed them, manage user access to the package registry via the main authentication server and not locally on the package registry.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each package registry, use the main authentication server of the organization for user management and do not manage locally.",
+ "AuditProcedure": "For each package registry, verify that its user access is not managed locally, but instead with the main authentication server of the organization.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.5",
+ "Description": "For GitHub Private or Internal repositories anonymous access is not available. Verify that all repos that require access controls are Private or Internal.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "For GitHub Private or Internal repositories anonymous access is not available. Verify that all repos that require access controls are Private or Internal.",
+ "RationaleStatement": "Disable the option to view artifacts as an anonymous user in order to protect private artifacts from being exposed.",
+ "ImpactStatement": "Only logged and authorized users will be able to access artifacts.",
+ "RemediationProcedure": "Changing a repository's visibility\n\n1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.\n1. Under your repository name, click Settings\n1. Under \"Danger Zone\", to the right of to \"Change repository visibility\", click Change visibility.\n1. Select a visibility.\n\n1. Choose \n - Mark private\n - Make Internal\n\n6. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.",
+ "AuditProcedure": "To Audit the existing settings:\n\n1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.\n1. Under your repository name, click Settings\n3. Under \"Danger Zone\", to the right of to \"Change repository visibility\", click Change visibility.\n\nReview the current selection.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/enterprise-server@3.3/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.6",
+ "Description": "Ensure the package registry has a minimum number of administrators.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.2 Access to Artifacts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure the package registry has a minimum number of administrators.",
+ "RationaleStatement": "Package registry admins have the ability to add/remove users, repositories, packages. Due to the permissive access granted to an admin, it is highly recommended to keep the number of administrator accounts as minimal as possible.",
+ "ImpactStatement": "Administrator privileges are required to provide and maintain a secure and stable platform but allowing extraneous administrator accounts can create a vulnerability.",
+ "RemediationProcedure": "Set the minimum number of administrators in your package registry.\n\nTo accomplish this:\n\nFor each repository that you administer on GitHub, you can see an overview of every team or person with access to the repository. From the overview, choose Manage access and provide access to the appropriate people or teams.",
+ "AuditProcedure": "Verify that your package registry has only the minimum number of administrators.\n\nFor each repository that you administer on GitHub, you can see an overview of every team or person with access to the repository. From the overview, you can also invite new teams or people, change each team or person's role for the repository, or remove access to the repository.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.3.1",
+ "Description": "Validate artifact signatures before uploading to the package registry.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.3 Package Registries",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Validate artifact signatures before uploading to the package registry.",
+ "RationaleStatement": "Cryptographic signature is a tool to verify artifact authenticity. Every artifact is supposed to be signed by its creator in order to confirm that it was not compromised before reaching the client. Validating an artifact signature before delivering it is another level of protection which ensures the signature has not been changed, meaning no one tried or succeeded in tampering with the artifact. This creates trust between the supplier and the client.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Validate every artifact with its signature before uploading it to the package registry. It is recommended to do so automatically.",
+ "AuditProcedure": "Ensure every artifact in the package registry has been validated with its signature.\n\n1. On GitHub, navigate to a pull request\n2. On the pull request, click <> Commits and view the detailed information regarding the signature.",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification:https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits",
+ "DefaultValue": "Artifacts are not scanned by default."
+ }
+ ]
+ },
+ {
+ "Id": "4.3.2",
+ "Description": "Validate the signature of all versions of an existing artifact.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.3 Package Registries",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Validate the signature of all versions of an existing artifact.",
+ "RationaleStatement": "In order to be certain a version of an existing and trusted artifact is not malicious or delivered by someone looking to interfere with the supply chain, it is a good practice to validate the signatures of each version. Doing so decreases the risk of using a compromised artifact, which might lead to a breach.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each artifact, sign and validate each version before uploading or using the artifact.",
+ "AuditProcedure": "For each artifact, ensure that all of its versions are signed and validated before it is uploaded or used.\n\nEnsure every artifact in the package registry has been validated with its signature.\n\nOn GitHub, navigate to a pull request\nOn the pull request, click <> Commits and view the detailed information regarding the signature.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.3.3",
+ "Description": "Audit changes of the package registry configuration.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.3 Package Registries",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Audit changes of the package registry configuration.",
+ "RationaleStatement": "The package registry is a crucial component in the software supply chain. It stores artifacts with potentially sensitive data that will eventually be deployed and used in production. Every change made to the package registry configuration must be examined carefully to ensure no exposure of the registry's sensitive data. This examination also ensures no malicious actors have performed modifications to a stored artifact. Auditing the configuration and its changes helps in decreasing such risks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Audit the changes to the package registry configuration.",
+ "AuditProcedure": "Verify that all changes to the packages registry configuration are audited.\n\nSearch the audit log with\n\nrepo category actions",
+ "AdditionalInformation": "",
+ "References": "https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization",
+ "DefaultValue": "GitHub audits this by default."
+ }
+ ]
+ },
+ {
+ "Id": "4.3.4",
+ "Description": "Use secured webhooks to reduce the possibility of malicious payloads.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.3 Package Registries",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use secured webhooks to reduce the possibility of malicious payloads.",
+ "RationaleStatement": "Webhooks are used for triggering an HTTP request based on an action made in the platform. Typically, package registries feature webhooks when a package receives an update. Since webhooks are an HTTP POST request, they can be malformed if not secured over SSL. To prevent a potential hack and compromise of the webhook or to the registry or web server excepting the request, use only secured webhooks.",
+ "ImpactStatement": "Reduces the payloads that the web hook can listen for and receive.",
+ "RemediationProcedure": "For each webhook in use, change it to secured (over HTTPS).",
+ "AuditProcedure": "",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.4.1",
+ "Description": "When delivering artifacts, ensure they have information about their origin. This may be done by providing a Software Bill of Manufacture (SBOM) or some metadata files.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Artifacts",
+ "Subsection": "4.4 Origin Traceability",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "When delivering artifacts, ensure they have information about their origin. This may be done by providing a Software Bill of Manufacture (SBOM) or some metadata files.",
+ "RationaleStatement": "Information about artifact origin can be used for verification purposes. Having this kind of information allows the user to decide if the organization supplying the artifact is trusted. In a case of potential vulnerability or version update, this can be used to verify that the organization issuing it is the actual origin and not someone else. If users need to report problems with the artifact, they will have an address to contact as well.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each artifact supplied, supply information about its origin. For each artifact in use, ask for information about its origin.",
+ "AuditProcedure": "For each artifact, ensure it has information about its origin.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.1",
+ "Description": "Deployment configurations are often stored in a version control system. Separate deployment configuration files from source code repositories.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Deployment configurations are often stored in a version control system. Separate deployment configuration files from source code repositories.",
+ "RationaleStatement": "Deployment configuration manifests are often stored in version control systems. Storing them in dedicated repositories, separately from source code repositories, has several benefits. First, it adds order to both maintenance and version control history. This makes it easier to track code or manifest changes, as well as spot any malicious code or misconfigurations. Second, it helps achieve the Least Privilege principle. Because access can be configured differently for each repository, fewer users will have access to this configuration, which is typically sensitive.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Store each deployment configuration file in a dedicated repository separately from source code.",
+ "AuditProcedure": "Ensure each deployment configuration file is stored separately from source code.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2",
+ "Description": "Audit and track changes made in deployment configuration.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Audit and track changes made in deployment configuration.",
+ "RationaleStatement": "Deployment configuration is sensitive in nature. The tiniest mistake can lead to downtime or bugs in production, which consequently may have a direct effect on both product integrity and customer trust. Misconfigurations might also be used by malicious actors to attack the production platform. Because of this, every change in the configuration needs a review and possible \"revert\" in case of a mistake or malicious change. Auditing every change and tracking them helps detect and fix such incidents more quickly.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each deployment configuration, track and audit changes made to it.",
+ "AuditProcedure": "For each deployment configuration, ensure changes made to it are audited and tracked.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3",
+ "Description": "Detect and prevent sensitive data – such as confidential ID numbers, passwords, etc. – in deployment configurations.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent sensitive data – such as confidential ID numbers, passwords, etc. – in deployment configurations.",
+ "RationaleStatement": "Sensitive data in deployment configurations might create a major incident if an attacker gains access to it, as this can cause data loss and theft. It is important to keep sensitive data safe and to not expose it in the configuration. In order to prevent a possible exposure, set scanners that will identify and prevent such data in deployment configurations.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each deployment configuration file, set scanners to identify and prevent sensitive data within it.",
+ "AuditProcedure": "For each deployment configuration file, verify that scanners are set to identify and prevent the existence of sensitive data within it.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4",
+ "Description": "Restrict access to the deployment configuration to trusted and qualified users only.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Restrict access to the deployment configuration to trusted and qualified users only.",
+ "RationaleStatement": "Deployment configurations are sensitive in nature. The tiniest mistake can lead to downtime or bugs in production, which can have a direct effect on the product's integrity and customer trust. Misconfigurations might also be used by malicious actors to attack the production platform. To avoid such harm as much as possible, ensure only trusted and qualified users have access to such configurations. This will also reduce the number of accounts that might affect the environment in case of an attack.",
+ "ImpactStatement": "Reducing the number of users who have access to the deployment configuration means those users would lose their ability to make direct changes to that configuration.",
+ "RemediationProcedure": "Restrict access to the deployment configuration to trusted and qualified users.",
+ "AuditProcedure": "Verify each deployment configuration is accessible only to known and authorized users.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5",
+ "Description": "Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files.",
+ "RationaleStatement": "Infrastructure as Code (IaC) files are used for production environment and application deployment. These are sensitive parts of the software supply chain because they are always in touch with customers, and thus might affect their opinion of or trust in the product. Attackers often target these environments. Detecting and fixing misconfigurations and/or insecure instructions in IaC files decreases the risk for data leak or data theft. It is important to secure IaC instructions in order to prevent further problems of deployment, exposed assets, or improper configurations, which might ultimately lead to easier ways to attack and steal organization data.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For every Infrastructure as Code (IaC) instructions file, set scanners to identify and prevent misconfigurations and insecure instructions.",
+ "AuditProcedure": "For every Infrastructure as Code (IaC) instructions file, verify that scanners are set to identify and prevent misconfigurations and insecure instructions.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.6",
+ "Description": "Verify the deployment configuration manifests.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Verify the deployment configuration manifests.",
+ "RationaleStatement": "To ensure that the configuration manifests used are trusted and have not been infected by malicious actors before arriving at the platform, it is important to verify the manifests. This may be done by comparing the checksum of the manifest file to its checksum in a trusted source. If a difference arises, this is a sign that an unknown actor has interfered and may have added malicious instructions. If this manifest is used, it might harm the environment and application deployment, which could end in a massive breach and leave the organization exposed to data leaks, etc.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Verify each deployment configuration manifest in use.",
+ "AuditProcedure": "For each deployment configuration manifest in use, ensure it has been verified.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.7",
+ "Description": "Deployment configuration is often stored in a version control system and is pulled from there. Pin the configuration used to a specific, verified version or commit Secure Hash Algorithm (SHA). Avoid referring configuration without its version tag specified.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.1 Deployment Configuration",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Deployment configuration is often stored in a version control system and is pulled from there. Pin the configuration used to a specific, verified version or commit Secure Hash Algorithm (SHA). Avoid referring configuration without its version tag specified.",
+ "RationaleStatement": "Deployment configuration manifests are often stored in version control systems and pulled from there either by automation platforms, for example Ansible, or GitOps platforms, such as ArgoCD. When a manifest is pulled from a version control system without tag or commit Secure Hash Algorithm (SHA) specified, it is pulled from the HEAD revision, which is equal to the 'latest' tag, and pulls the last change made. This increases the risk of encountering a new, potentially malicious configuration. If an attacker pushes malicious configuration to the version control system, the next user who pulls the HEAD revision will pull it and risk attack. To avoid that risk, use a version tag of verified version or a commit SHA of a trusted commit, which will ensure this is the only version pulled.",
+ "ImpactStatement": "Changes in deployment configuration will not be pulled unless their version tag or commit Secure Hash Algorithm (SHA) is specified. This might slow down the deployment process.",
+ "RemediationProcedure": "For every deployment configuration manifest in use, pin to a specific version or commit Secure Hash Algorithm (SHA).",
+ "AuditProcedure": "For every deployment configuration manifest in use, ensure it is pinned to a specific version or commit Secure Hash Algorithm (SHA).",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2.1",
+ "Description": "Automate deployments of production environment and application.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.2 Deployment Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Automate deployments of production environment and application.",
+ "RationaleStatement": "Automating the deployments of both production environment and applications reduces the risk for human mistakes — such as a wrong configuration or exposure of sensitive data — because it requires less human interaction or intervention. It also eases redeployment of the environment. It is best to automate with Infrastructure as Code (IaC) because it offers more control over changes made to the environment creation configuration and stores to a version control platform.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Automate each deployment process of the production environment and application.",
+ "AuditProcedure": "For each deployment process, ensure it is automated.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2",
+ "Description": "Verify that the deployment environment – the orchestrator and the production environment where the application is deployed – is reproducible. This means that the environment stays the same in each deployment if the configuration has not changed.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.2 Deployment Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Verify that the deployment environment – the orchestrator and the production environment where the application is deployed – is reproducible. This means that the environment stays the same in each deployment if the configuration has not changed.",
+ "RationaleStatement": "A reproducible build is a build that produces the same artifact when given the same input data, and in this case the same environment. Ensuring that the same environment is produced when given the same input helps verify that no change has been made to it. This action allows an organization to trust that its deployment environment is built only from safe code and configuration that has been reviewed and tested and has not been tainted or changed abruptly.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Adjust the process that deploys the deployment/production environment to build the same environment each time when the configuration has not changed.",
+ "AuditProcedure": "Verify that the deployment/production environment is reproducible.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3",
+ "Description": "Restrict access to the production environment to a few trusted and qualified users only.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.2 Deployment Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Restrict access to the production environment to a few trusted and qualified users only.",
+ "RationaleStatement": "The production environment is an extremely sensitive one. It directly affects the customer experience and trust in a product, which has serious effects on the organization itself. Because of this sensitive nature, it is important to restrict access to the production environment to only a few trusted and qualified users. This will reduce the risk of mistakes such as exposure of secrets or misconfiguration. This restriction also reduces the number of accounts that are vulnerable to hijacking in order to potentially harm the production environment.",
+ "ImpactStatement": "Reducing the number of users who have access to the production environment means those users would lose their ability to make direct changes to that environment.",
+ "RemediationProcedure": "Restrict access to the production environment to trusted and qualified users.",
+ "AuditProcedure": "Verify that the production environment is accessible only to trusted and qualified users.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4",
+ "Description": "Do not use default passwords of deployment tools and components.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Deployment",
+ "Subsection": "5.2 Deployment Environment",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not use default passwords of deployment tools and components.",
+ "RationaleStatement": "Many deployment tools and components are provided with default passwords for the first login. This password is intended to be used only on the first login and should be changed immediately after. Using the default password substantially increases the attack risk. It is very important to ensure that default passwords are not used in deployment tools and components.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "For each deployment tool, change the password.",
+ "AuditProcedure": "For each deployment tool, ensure the password is not the default one.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/googleworkspace/cis_1.3_googleworkspace.json b/prowler/compliance/googleworkspace/cis_1.3_googleworkspace.json
index 7e79427747..167842af4b 100644
--- a/prowler/compliance/googleworkspace/cis_1.3_googleworkspace.json
+++ b/prowler/compliance/googleworkspace/cis_1.3_googleworkspace.json
@@ -1222,7 +1222,9 @@
{
"Id": "3.1.6.1",
"Description": "Ensure accessing groups from outside this organization is set to private",
- "Checks": [],
+ "Checks": [
+ "groups_external_access_restricted"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1243,7 +1245,9 @@
{
"Id": "3.1.6.2",
"Description": "Ensure creating groups is restricted",
- "Checks": [],
+ "Checks": [
+ "groups_creation_restricted"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1264,7 +1268,9 @@
{
"Id": "3.1.6.3",
"Description": "Ensure default for permission to view conversations is restricted",
- "Checks": [],
+ "Checks": [
+ "groups_view_conversations_restricted"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1285,7 +1291,9 @@
{
"Id": "3.1.7.1",
"Description": "Ensure service status for Google Sites is set to off",
- "Checks": [],
+ "Checks": [
+ "sites_service_disabled"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1306,7 +1314,9 @@
{
"Id": "3.1.8.1",
"Description": "Ensure access to external Google Groups is OFF for Everyone",
- "Checks": [],
+ "Checks": [
+ "additionalservices_external_groups_disabled"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1327,7 +1337,9 @@
{
"Id": "3.1.9.1.1",
"Description": "Ensure users access to Google Workspace Marketplace apps is restricted",
- "Checks": [],
+ "Checks": [
+ "marketplace_apps_access_restricted"
+ ],
"Attributes": [
{
"Section": "3 Apps",
@@ -1348,7 +1360,9 @@
{
"Id": "4.1.1.1",
"Description": "Ensure 2-Step Verification (Multi-Factor Authentication) is enforced for all users in administrative roles",
- "Checks": [],
+ "Checks": [
+ "security_2sv_enforced"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1369,7 +1383,9 @@
{
"Id": "4.1.1.2",
"Description": "Ensure hardware security keys are used for all users in administrative roles and other high-value accounts",
- "Checks": [],
+ "Checks": [
+ "security_2sv_hardware_keys_admins"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1390,7 +1406,9 @@
{
"Id": "4.1.1.3",
"Description": "Ensure 2-Step Verification (Multi-Factor Authentication) is enforced for all users",
- "Checks": [],
+ "Checks": [
+ "security_2sv_enforced"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1411,7 +1429,9 @@
{
"Id": "4.1.2.1",
"Description": "Ensure Super Admin account recovery is disabled",
- "Checks": [],
+ "Checks": [
+ "security_super_admin_recovery_disabled"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1432,7 +1452,9 @@
{
"Id": "4.1.2.2",
"Description": "Ensure User account recovery is enabled",
- "Checks": [],
+ "Checks": [
+ "security_user_recovery_enabled"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1453,7 +1475,9 @@
{
"Id": "4.1.3.1",
"Description": "Ensure Advanced Protection Program is configured",
- "Checks": [],
+ "Checks": [
+ "security_advanced_protection_configured"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1474,7 +1498,9 @@
{
"Id": "4.1.4.1",
"Description": "Ensure login challenges are enforced",
- "Checks": [],
+ "Checks": [
+ "security_login_challenges_configured"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1495,7 +1521,9 @@
{
"Id": "4.1.5.1",
"Description": "Ensure password policy is configured for enhanced security",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1516,7 +1544,9 @@
{
"Id": "4.2.1.1",
"Description": "Ensure application access to Google services is restricted",
- "Checks": [],
+ "Checks": [
+ "security_app_access_restricted"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1558,7 +1588,9 @@
{
"Id": "4.2.1.3",
"Description": "Ensure internal apps can access Google Workspace APIs",
- "Checks": [],
+ "Checks": [
+ "security_internal_apps_trusted"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1621,7 +1653,9 @@
{
"Id": "4.2.3.1",
"Description": "Ensure DLP policies for Google Drive are configured",
- "Checks": [],
+ "Checks": [
+ "security_dlp_drive_rules_configured"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1642,7 +1676,9 @@
{
"Id": "4.2.4.1",
"Description": "Ensure Google session control is configured",
- "Checks": [],
+ "Checks": [
+ "security_session_duration_limited"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1684,7 +1720,9 @@
{
"Id": "4.2.6.1",
"Description": "Ensure less secure app access is disabled",
- "Checks": [],
+ "Checks": [
+ "security_less_secure_apps_disabled"
+ ],
"Attributes": [
{
"Section": "4 Security",
@@ -1789,7 +1827,9 @@
{
"Id": "6.1",
"Description": "Ensure User's password changed is configured",
- "Checks": [],
+ "Checks": [
+ "rules_password_changed_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1810,7 +1850,9 @@
{
"Id": "6.2",
"Description": "Ensure Government-backed attacks is configured",
- "Checks": [],
+ "Checks": [
+ "rules_government_backed_attacks_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1831,7 +1873,9 @@
{
"Id": "6.3",
"Description": "Ensure User suspended due to suspicious activity is configured",
- "Checks": [],
+ "Checks": [
+ "rules_suspicious_activity_suspension_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1852,7 +1896,9 @@
{
"Id": "6.4",
"Description": "Ensure User granted Admin privilege is configured",
- "Checks": [],
+ "Checks": [
+ "rules_admin_privilege_granted_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1873,7 +1919,9 @@
{
"Id": "6.5",
"Description": "Ensure Suspicious programmatic login is configured",
- "Checks": [],
+ "Checks": [
+ "rules_suspicious_programmatic_login_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1894,7 +1942,9 @@
{
"Id": "6.6",
"Description": "Ensure Suspicious login is configured",
- "Checks": [],
+ "Checks": [
+ "rules_suspicious_login_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1915,7 +1965,9 @@
{
"Id": "6.7",
"Description": "Ensure Leaked password is configured",
- "Checks": [],
+ "Checks": [
+ "rules_leaked_password_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
@@ -1936,7 +1988,9 @@
{
"Id": "6.8",
"Description": "Ensure Gmail potential employee spoofing is configured",
- "Checks": [],
+ "Checks": [
+ "rules_gmail_employee_spoofing_alert_configured"
+ ],
"Attributes": [
{
"Section": "6 Rules",
diff --git a/prowler/compliance/googleworkspace/cisa_scuba_0.6_googleworkspace.json b/prowler/compliance/googleworkspace/cisa_scuba_0.6_googleworkspace.json
index 21c4b5d815..72ff97d97d 100644
--- a/prowler/compliance/googleworkspace/cisa_scuba_0.6_googleworkspace.json
+++ b/prowler/compliance/googleworkspace/cisa_scuba_0.6_googleworkspace.json
@@ -8,7 +8,10 @@
{
"Id": "GWS.COMMONCONTROLS.1.1",
"Description": "Phishing-resistant MFA SHALL be required for all users",
- "Checks": [],
+ "Checks": [
+ "security_2sv_enforced",
+ "security_2sv_hardware_keys_admins"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -21,7 +24,9 @@
{
"Id": "GWS.COMMONCONTROLS.1.2",
"Description": "If phishing-resistant MFA is not yet tenable, an MFA method from the list of acceptable MFA methods SHALL be used as an interim solution",
- "Checks": [],
+ "Checks": [
+ "security_2sv_enforced"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -112,7 +117,9 @@
{
"Id": "GWS.COMMONCONTROLS.4.1",
"Description": "Google Workspace sessions SHALL re-authenticate after 12 hours",
- "Checks": [],
+ "Checks": [
+ "security_session_duration_limited"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -125,7 +132,9 @@
{
"Id": "GWS.COMMONCONTROLS.5.1",
"Description": "Password strength SHALL be enforced",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -138,7 +147,9 @@
{
"Id": "GWS.COMMONCONTROLS.5.2",
"Description": "Minimum password length SHALL be at least 12 characters",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -151,7 +162,9 @@
{
"Id": "GWS.COMMONCONTROLS.5.3",
"Description": "Minimum password length SHOULD be at least 15 characters",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -164,7 +177,9 @@
{
"Id": "GWS.COMMONCONTROLS.5.4",
"Description": "Password policy SHALL be enforced at next sign-in",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -177,7 +192,9 @@
{
"Id": "GWS.COMMONCONTROLS.5.5",
"Description": "Password reuse SHALL be restricted",
- "Checks": [],
+ "Checks": [
+ "security_password_policy_strong"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -244,7 +261,9 @@
{
"Id": "GWS.COMMONCONTROLS.8.1",
"Description": "Account recovery for super admins SHALL be disabled",
- "Checks": [],
+ "Checks": [
+ "security_super_admin_recovery_disabled"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -283,7 +302,9 @@
{
"Id": "GWS.COMMONCONTROLS.9.1",
"Description": "Privileged accounts SHALL be enrolled in the Advanced Protection Program",
- "Checks": [],
+ "Checks": [
+ "security_advanced_protection_configured"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -296,7 +317,9 @@
{
"Id": "GWS.COMMONCONTROLS.9.2",
"Description": "Sensitive user accounts SHOULD be enrolled in the Advanced Protection Program",
- "Checks": [],
+ "Checks": [
+ "security_advanced_protection_configured"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -361,7 +384,9 @@
{
"Id": "GWS.COMMONCONTROLS.10.5",
"Description": "Internal apps SHALL be allowed to access restricted Google Workspace APIs",
- "Checks": [],
+ "Checks": [
+ "security_internal_apps_trusted"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -374,7 +399,9 @@
{
"Id": "GWS.COMMONCONTROLS.11.1",
"Description": "Only approved Marketplace apps SHALL be allowed for installation",
- "Checks": [],
+ "Checks": [
+ "marketplace_apps_access_restricted"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -400,7 +427,16 @@
{
"Id": "GWS.COMMONCONTROLS.13.1",
"Description": "All system-defined alerting rules SHALL be enabled with alerts sent to admin email addresses",
- "Checks": [],
+ "Checks": [
+ "rules_password_changed_alert_configured",
+ "rules_government_backed_attacks_alert_configured",
+ "rules_suspicious_activity_suspension_alert_configured",
+ "rules_admin_privilege_granted_alert_configured",
+ "rules_suspicious_programmatic_login_alert_configured",
+ "rules_suspicious_login_alert_configured",
+ "rules_leaked_password_alert_configured",
+ "rules_gmail_employee_spoofing_alert_configured"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -504,7 +540,9 @@
{
"Id": "GWS.COMMONCONTROLS.18.1",
"Description": "A DLP policy SHALL be configured for Drive",
- "Checks": [],
+ "Checks": [
+ "security_dlp_drive_rules_configured"
+ ],
"Attributes": [
{
"Section": "Common Controls",
@@ -1626,7 +1664,9 @@
{
"Id": "GWS.GROUPS.1.1",
"Description": "Group access from outside the organization SHALL be disabled unless explicitly granted by the group owner",
- "Checks": [],
+ "Checks": [
+ "groups_external_access_restricted"
+ ],
"Attributes": [
{
"Section": "Groups",
@@ -1639,7 +1679,9 @@
{
"Id": "GWS.GROUPS.1.2",
"Description": "Group owners' ability to add external members to groups SHOULD be disabled unless necessary for agency mission fulfillment",
- "Checks": [],
+ "Checks": [
+ "groups_creation_restricted"
+ ],
"Attributes": [
{
"Section": "Groups",
@@ -1652,7 +1694,9 @@
{
"Id": "GWS.GROUPS.1.3",
"Description": "Group owners' ability to allow posting to a group by an external, non-group member SHOULD be disabled unless necessary for agency mission fulfillment",
- "Checks": [],
+ "Checks": [
+ "groups_creation_restricted"
+ ],
"Attributes": [
{
"Section": "Groups",
@@ -1665,7 +1709,9 @@
{
"Id": "GWS.GROUPS.2.1",
"Description": "Group creation SHOULD be restricted to admins within the organization unless necessary for agency mission fulfillment",
- "Checks": [],
+ "Checks": [
+ "groups_creation_restricted"
+ ],
"Attributes": [
{
"Section": "Groups",
@@ -1678,7 +1724,9 @@
{
"Id": "GWS.GROUPS.3.1",
"Description": "The default permission to view conversations SHOULD be set to All Group Members",
- "Checks": [],
+ "Checks": [
+ "groups_view_conversations_restricted"
+ ],
"Attributes": [
{
"Section": "Groups",
@@ -1704,7 +1752,9 @@
{
"Id": "GWS.SITES.1.1",
"Description": "Sites Service SHOULD be disabled for all users",
- "Checks": [],
+ "Checks": [
+ "sites_service_disabled"
+ ],
"Attributes": [
{
"Section": "Sites",
diff --git a/prowler/compliance/kubernetes/cis_1.10_kubernetes.json b/prowler/compliance/kubernetes/cis_1.10_kubernetes.json
index a049efc040..ed0e90d88f 100644
--- a/prowler/compliance/kubernetes/cis_1.10_kubernetes.json
+++ b/prowler/compliance/kubernetes/cis_1.10_kubernetes.json
@@ -820,6 +820,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
"Attributes": [
{
"Section": "1 Control Plane Components",
@@ -858,6 +866,14 @@
"DefaultValue": "By default, auditing is not enabled.",
"References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/concepts/cluster-administration/audit/:https://github.com/kubernetes/features/issues/22"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
]
},
{
@@ -881,6 +897,14 @@
"DefaultValue": "By default, auditing is not enabled.",
"References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/concepts/cluster-administration/audit/:https://github.com/kubernetes/features/issues/22"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
]
},
{
@@ -1109,6 +1133,18 @@
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers",
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices#23-use-secure-cipher-suites"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_strong_ciphers_only",
+ "ConfigKey": "apiserver_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_AES_128_GCM_SHA256",
+ "TLS_AES_256_GCM_SHA384",
+ "TLS_CHACHA20_POLY1305_SHA256"
+ ]
+ }
]
},
{
@@ -2069,6 +2105,23 @@
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers",
"References": ""
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/kubernetes/cis_1.11_kubernetes.json b/prowler/compliance/kubernetes/cis_1.11_kubernetes.json
index 6a19ea4161..25d725683f 100644
--- a/prowler/compliance/kubernetes/cis_1.11_kubernetes.json
+++ b/prowler/compliance/kubernetes/cis_1.11_kubernetes.json
@@ -820,6 +820,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
"Attributes": [
{
"Section": "1 Control Plane Components",
@@ -858,6 +866,14 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
]
},
{
@@ -881,6 +897,14 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
]
},
{
@@ -1109,6 +1133,18 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices#23-use-secure-cipher-suites",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_strong_ciphers_only",
+ "ConfigKey": "apiserver_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_AES_128_GCM_SHA256",
+ "TLS_AES_256_GCM_SHA384",
+ "TLS_CHACHA20_POLY1305_SHA256"
+ ]
+ }
]
},
{
@@ -2112,6 +2148,23 @@
"References": "",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/kubernetes/cis_1.12_kubernetes.json b/prowler/compliance/kubernetes/cis_1.12_kubernetes.json
index 1ba1e55a88..ded2d6944a 100644
--- a/prowler/compliance/kubernetes/cis_1.12_kubernetes.json
+++ b/prowler/compliance/kubernetes/cis_1.12_kubernetes.json
@@ -820,6 +820,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
"Attributes": [
{
"Section": "1 Control Plane Components",
@@ -858,6 +866,14 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
]
},
{
@@ -881,6 +897,14 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
]
},
{
@@ -1109,6 +1133,18 @@
"References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices#23-use-secure-cipher-suites",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_strong_ciphers_only",
+ "ConfigKey": "apiserver_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_AES_128_GCM_SHA256",
+ "TLS_AES_256_GCM_SHA384",
+ "TLS_CHACHA20_POLY1305_SHA256"
+ ]
+ }
]
},
{
@@ -2090,6 +2126,23 @@
"References": "",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/kubernetes/cis_1.8_kubernetes.json b/prowler/compliance/kubernetes/cis_1.8_kubernetes.json
index 24a5733a05..a09d753f58 100644
--- a/prowler/compliance/kubernetes/cis_1.8_kubernetes.json
+++ b/prowler/compliance/kubernetes/cis_1.8_kubernetes.json
@@ -843,6 +843,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
"Attributes": [
{
"Section": "1 Control Plane Components",
@@ -881,6 +889,14 @@
"References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/concepts/cluster-administration/audit/:https://github.com/kubernetes/features/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
]
},
{
@@ -904,6 +920,14 @@
"References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/concepts/cluster-administration/audit/:https://github.com/kubernetes/features/issues/22",
"DefaultValue": "By default, auditing is not enabled."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
]
},
{
@@ -1132,6 +1156,18 @@
"References": "https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices#23-use-secure-cipher-suites",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_strong_ciphers_only",
+ "ConfigKey": "apiserver_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_AES_128_GCM_SHA256",
+ "TLS_AES_256_GCM_SHA384",
+ "TLS_CHACHA20_POLY1305_SHA256"
+ ]
+ }
]
},
{
@@ -2092,6 +2128,23 @@
"References": "",
"DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
]
},
{
diff --git a/prowler/compliance/kubernetes/cis_2.0.1_kubernetes.json b/prowler/compliance/kubernetes/cis_2.0.1_kubernetes.json
new file mode 100644
index 0000000000..2b9e695dd2
--- /dev/null
+++ b/prowler/compliance/kubernetes/cis_2.0.1_kubernetes.json
@@ -0,0 +1,2968 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS Kubernetes Benchmark v2.0.1",
+ "Version": "2.0.1",
+ "Provider": "Kubernetes",
+ "Description": "This CIS Kubernetes Benchmark provides prescriptive guidance for establishing a secure configuration posture for Kubernetes v1.34 - v1.35",
+ "Requirements": [
+ {
+ "Id": "1.1.1",
+ "Description": "Ensure that the API server pod specification file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the API server pod specification file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The API server pod specification file controls various parameters that set the behavior of the API server. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/manifests/kube-apiserver.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/manifests/kube-apiserver.yaml ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the `kube-apiserver.yaml` file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.2",
+ "Description": "Ensure that the API server pod specification file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the API server pod specification file ownership is set to `root:root`.",
+ "RationaleStatement": "The API server pod specification file controls various parameters that set the behavior of the API server. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/manifests/kube-apiserver.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/manifests/kube-apiserver.yaml ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the `kube-apiserver.yaml` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.3",
+ "Description": "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the controller manager pod specification file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The controller manager pod specification file controls various parameters that set the behavior of the Controller Manager on the master node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/manifests/kube-controller-manager.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/manifests/kube-controller-manager.yaml ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the `kube-controller-manager.yaml` file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.4",
+ "Description": "Ensure that the controller manager pod specification file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the controller manager pod specification file ownership is set to `root:root`.",
+ "RationaleStatement": "The controller manager pod specification file controls various parameters that set the behavior of various components of the master node. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/manifests/kube-controller-manager.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/manifests/kube-controller-manager.yaml ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager",
+ "DefaultValue": "By default, `kube-controller-manager.yaml` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.5",
+ "Description": "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the scheduler pod specification file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The scheduler pod specification file controls various parameters that set the behavior of the Scheduler service in the master node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/manifests/kube-scheduler.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/manifests/kube-scheduler.yaml ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-scheduler/",
+ "DefaultValue": "By default, `kube-scheduler.yaml` file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.6",
+ "Description": "Ensure that the scheduler pod specification file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the scheduler pod specification file ownership is set to `root:root`.",
+ "RationaleStatement": "The scheduler pod specification file controls various parameters that set the behavior of the `kube-scheduler` service in the master node. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/manifests/kube-scheduler.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/manifests/kube-scheduler.yaml ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-scheduler/",
+ "DefaultValue": "By default, `kube-scheduler.yaml` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.7",
+ "Description": "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `/etc/kubernetes/manifests/etcd.yaml` file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` controls various parameters that set the behavior of the `etcd` service in the master node. etcd is a highly-available key-value store which Kubernetes uses for persistent storage of all of its REST API object. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/manifests/etcd.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/manifests/etcd.yaml ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "By default, `/etc/kubernetes/manifests/etcd.yaml` file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.8",
+ "Description": "Ensure that the etcd pod specification file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `/etc/kubernetes/manifests/etcd.yaml` file ownership is set to `root:root`.",
+ "RationaleStatement": "The etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` controls various parameters that set the behavior of the `etcd` service in the master node. etcd is a highly-available key-value store which Kubernetes uses for persistent storage of all of its REST API object. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/manifests/etcd.yaml ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/manifests/etcd.yaml ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "By default, `/etc/kubernetes/manifests/etcd.yaml` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.9",
+ "Description": "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the Container Network Interface files have permissions of `600` or more restrictive.",
+ "RationaleStatement": "Container Network Interface provides various networking options for overlay networking. You should consult their documentation and restrict their respective file permissions to maintain the integrity of those files. Those files should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 <path/to/cni/files> ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a <path/to/cni/files> ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/cluster-administration/networking/",
+ "DefaultValue": "NA"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.10",
+ "Description": "Ensure that the Container Network Interface file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the Container Network Interface files have ownership set to `root:root`.",
+ "RationaleStatement": "Container Network Interface provides various networking options for overlay networking. You should consult their documentation and restrict their respective file permissions to maintain the integrity of those files. Those files should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root <path/to/cni/files> ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G <path/to/cni/files> ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/cluster-administration/networking/",
+ "DefaultValue": "NA"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.11",
+ "Description": "Ensure that the etcd data directory permissions are set to 700 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the etcd data directory has permissions of `700` or more restrictive.",
+ "RationaleStatement": "etcd is a highly-available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. This data directory should be protected from any unauthorized reads or writes. It should not be readable or writable by any group members or the world.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "On the etcd server node, get the etcd data directory, passed as an argument `--data-dir`, from the below command: ``` ps -ef | grep etcd ``` Run the below command (based on the etcd data directory found above). For example, ``` chmod 700 /var/lib/etcd ```",
+ "AuditProcedure": "On the etcd server node, get the etcd data directory, passed as an argument `--data-dir`, from the below command: ``` ps -ef | grep etcd ``` Run the below command (based on the etcd data directory found above). For example, ``` stat -c %a /var/lib/etcd ``` Verify that the permissions are `700` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/configuration.html#data-dir:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "By default, etcd data directory has permissions of `755`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.12",
+ "Description": "Ensure that the etcd data directory ownership is set to etcd:etcd",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the etcd data directory ownership is set to `etcd:etcd`.",
+ "RationaleStatement": "etcd is a highly-available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. This data directory should be protected from any unauthorized reads or writes. It should be owned by `etcd:etcd`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "On the etcd server node, get the etcd data directory, passed as an argument `--data-dir`, from the below command: ``` ps -ef | grep etcd ``` Run the below command (based on the etcd data directory found above). For example, ``` chown etcd:etcd /var/lib/etcd ```",
+ "AuditProcedure": "On the etcd server node, get the etcd data directory, passed as an argument `--data-dir`, from the below command: ``` ps -ef | grep etcd ``` Run the below command (based on the etcd data directory found above). For example, ``` stat -c %U:%G /var/lib/etcd ``` Verify that the ownership is set to `etcd:etcd`.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/configuration.html#data-dir:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "By default, etcd data directory ownership is set to `etcd:etcd`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.13",
+ "Description": "Ensure that the default administrative credential file permissions are set to 600",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `admin.conf` file (and `super-admin.conf` file, where it exists) have permissions of `600`.",
+ "RationaleStatement": "As part of initial cluster setup, default kubeconfig files are created to be used by the administrator of the cluster. These files contain private keys and certificates which allow for privileged access to the cluster. You should restrict their file permissions to maintain the integrity and confidentiality of the file(s). The file(s) should be readable and writable by only the administrators on the system.",
+ "ImpactStatement": "None.",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/admin.conf ``` On Kubernetes 1.29+ the `super-admin.conf` file should also be modified, if present. For example, ``` chmod 600 /etc/kubernetes/super-admin.conf ```",
+ "AuditProcedure": "Run the following command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/admin.conf ``` On Kubernetes version 1.29 and higher run the following command as well :- ``` stat -c %a /etc/kubernetes/super-admin.conf ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/:https://raesene.github.io/blog/2024/01/06/when-is-admin-not-admin/",
+ "DefaultValue": "By default, admin.conf and super-admin.conf have permissions of `600`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.14",
+ "Description": "Ensure that the default administrative credential file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `admin.conf` (and `super-admin.conf` file, where it exists) file ownership is set to `root:root`.",
+ "RationaleStatement": "As part of initial cluster setup, default kubeconfig files are created to be used by the administrator of the cluster. These files contain private keys and certificates which allow for privileged access to the cluster. You should set their file ownership to maintain the integrity and confidentiality of the file. The file(s) should be owned by `root:root`.",
+ "ImpactStatement": "None.",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/admin.conf ``` On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present. For example, ``` chown root:root /etc/kubernetes/super-admin.conf ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/admin.conf ``` On Kubernetes version 1.29 and higher run the following command as well :- ``` stat -c %U:%G /etc/kubernetes/super-admin.conf ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubeadm/:https://raesene.github.io/blog/2024/01/06/when-is-admin-not-admin/",
+ "DefaultValue": "By default, `admin.conf` and `super-admin.conf` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.15",
+ "Description": "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `scheduler.conf` file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The `scheduler.conf` file is the kubeconfig file for the Scheduler. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/scheduler.conf ```",
+ "AuditProcedure": "Run the following command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/scheduler.conf ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/",
+ "DefaultValue": "By default, `scheduler.conf` has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.16",
+ "Description": "Ensure that the scheduler.conf file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `scheduler.conf` file ownership is set to `root:root`.",
+ "RationaleStatement": "The `scheduler.conf` file is the kubeconfig file for the Scheduler. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/scheduler.conf ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/scheduler.conf ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubeadm/",
+ "DefaultValue": "By default, `scheduler.conf` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.17",
+ "Description": "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `controller-manager.conf` file has permissions of 600 or more restrictive.",
+ "RationaleStatement": "The `controller-manager.conf` file is the kubeconfig file for the Controller Manager. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod 600 /etc/kubernetes/controller-manager.conf ```",
+ "AuditProcedure": "Run the following command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %a /etc/kubernetes/controller-manager.conf ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/",
+ "DefaultValue": "By default, `controller-manager.conf` has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.18",
+ "Description": "Ensure that the controller-manager.conf file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `controller-manager.conf` file ownership is set to `root:root`.",
+ "RationaleStatement": "The `controller-manager.conf` file is the kubeconfig file for the Controller Manager. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown root:root /etc/kubernetes/controller-manager.conf ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c %U:%G /etc/kubernetes/controller-manager.conf ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/",
+ "DefaultValue": "By default, `controller-manager.conf` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.19",
+ "Description": "Ensure that the Kubernetes PKI directory and file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the Kubernetes PKI directory and file ownership is set to `root:root`.",
+ "RationaleStatement": "Kubernetes makes use of a number of certificates as part of its operation. You should set the ownership of the directory containing the PKI information and all files in that directory to maintain their integrity. The directory and files should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chown -R root:root /etc/kubernetes/pki/ ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` ls -laR /etc/kubernetes/pki/ ``` Verify that the ownership of all files and directories in this hierarchy is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the /etc/kubernetes/pki/ directory and all of the files and directories contained within it, are set to be owned by the root user."
+ }
+ ]
+ },
+ {
+ "Id": "1.1.20",
+ "Description": "Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Kubernetes PKI certificate files have permissions of `644` or more restrictive.",
+ "RationaleStatement": "Kubernetes makes use of a number of certificate files as part of the operation of its components. The permissions on these files should be set to `644` or more restrictive to protect their integrity and confidentiality.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod -R 644 /etc/kubernetes/pki/*.crt ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c '%a' /etc/kubernetes/pki/*.crt ``` Verify that the permissions are `644` or more restrictive. or ``` ls -l /etc/kubernetes/pki/*.crt ``` Verify -rw------",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the certificates used by Kubernetes are set to have permissions of `644`"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.21",
+ "Description": "Ensure that the Kubernetes PKI key file permissions are set to 600",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.1 Control Plane Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that Kubernetes PKI key files have permissions of `600`.",
+ "RationaleStatement": "Kubernetes makes use of a number of key files as part of the operation of its components. The permissions on these files should be set to `600` to protect their integrity and confidentiality.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` chmod -R 600 /etc/kubernetes/pki/*.key ```",
+ "AuditProcedure": "Run the below command (based on the file location on your system) on the Control Plane node. For example, ``` stat -c '%a' /etc/kubernetes/pki/*.key ``` Verify that the permissions are `600` or more restrictive. or ``` ls -l /etc/kubernetes/pki/*.key ``` Verify that the permissions are `-rw------`",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, the keys used by Kubernetes are set to have permissions of `600`"
+ }
+ ]
+ },
+ {
+ "Id": "1.2.1",
+ "Description": "Ensure that the --anonymous-auth argument is set to false",
+ "Checks": [
+ "apiserver_anonymous_requests"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Disable anonymous requests to the API server.",
+ "RationaleStatement": "When enabled, requests that are not rejected by other configured authentication methods are treated as anonymous requests. These requests are then served by the API server. You should rely on authentication to authorize access and disallow anonymous requests. If you are using RBAC authorization, it is generally considered reasonable to allow anonymous access to the API Server for health checks and discovery purposes, and hence this recommendation is not scored. However, you should consider whether anonymous discovery is an acceptable risk for your purposes.",
+ "ImpactStatement": "Anonymous requests will be rejected.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the below parameter. ``` --anonymous-auth=false ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--anonymous-auth` argument is set to `false`. Alternative Audit Method ``` kubectl get pod -nkube-system -lcomponent=kube-apiserver -o=jsonpath='{range .items[*]}{.spec.containers[*].command} {\\}{end}' | grep '--anonymous-auth' | grep -i false ``` If the exit code is '1', then the control isn't present / failed",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/admin/authentication/#anonymous-requests",
+ "DefaultValue": "By default, anonymous access is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.2",
+ "Description": "Ensure that the --token-auth-file parameter is not set",
+ "Checks": [
+ "apiserver_no_token_auth_file"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not use token based authentication.",
+ "RationaleStatement": "The token-based authentication utilizes static tokens to authenticate requests to the apiserver. The tokens are stored in clear-text in a file on the apiserver, and cannot be revoked or rotated without restarting the apiserver. Hence, do not use static token-based authentication.",
+ "ImpactStatement": "You will have to configure and use alternate authentication mechanisms such as certificates. Static token based authentication could not be used.",
+ "RemediationProcedure": "Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and remove the `--token-auth-file=<filename>` parameter.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--token-auth-file` argument does not exist. Alternative Audit Method ``` kubectl get pod -nkube-system -lcomponent=kube-apiserver -o=jsonpath='{range .items[*]}{.spec.containers[*].command} {\\}{end}' | grep '--token-auth-file' | grep -i false ``` If the exit code is '1', then the control isn't present / failed",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/authentication/#static-token-file:https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, `--token-auth-file` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.3",
+ "Description": "Ensure that the DenyServiceExternalIPs is set",
+ "Checks": [
+ "apiserver_deny_service_external_ips"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "This admission controller rejects all net-new usage of the Service field externalIPs.",
+ "RationaleStatement": "Most users do not need the ability to set the `externalIPs` field for a `Service` at all, and cluster admins should consider disabling this functionality by enabling the `DenyServiceExternalIPs` admission controller. Clusters that do need to allow this functionality should consider using some custom policy to manage its usage.",
+ "ImpactStatement": "When enabled, users of the cluster may not create new Services which use externalIPs and may not add new values to externalIPs on existing Service objects.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and append the Kubernetes API server flag --enable-admission-plugins with the DenyServiceExternalIPs plugin. Note, the Kubernetes API server flag --enable-admission-plugins takes a comma-delimited list of admission control plugins to be enabled, even if they are in the list of plugins enabled by default. ``` kube-apiserver --enable-admission-plugins=DenyServiceExternalIPs ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `DenyServiceExternalIPs' argument exist as a string value in --enable-admission-plugins.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/:https://kubernetes.io/docs/admin/kube-apiserver/",
+ "DefaultValue": "By default, --enable-admission-plugins=DenyServiceExternalIP argument is not set, and the use of externalIPs is authorized."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.4",
+ "Description": "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate",
+ "Checks": [
+ "apiserver_kubelet_tls_auth"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable certificate based kubelet authentication.",
+ "RationaleStatement": "The apiserver, by default, does not authenticate itself to the kubelet's HTTPS endpoints. The requests from the apiserver are treated anonymously. You should set up certificate-based kubelet authentication to ensure that the apiserver authenticates itself to kubelets when submitting requests.",
+ "ImpactStatement": "You require TLS to be configured on apiserver as well as kubelets.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set up the TLS connection between the apiserver and kubelets. Then, edit API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the kubelet client certificate and key parameters as below. ``` --kubelet-client-certificate=<path/to/client-certificate-file> --kubelet-client-key=<path/to/client-key-file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--kubelet-client-certificate` and `--kubelet-client-key` arguments exist and they are set as appropriate. Alternative Audit ``` kubectl get pod -nkube-system -lcomponent=kube-apiserver -o=jsonpath='{range .items[*]}{.spec.containers[*].command} {\\}{end}' | grep '--kubelet-client-certificate' | grep -i false ``` If the exit code is '1', then the control isn't present / failed",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/admin/kubelet-authentication-authorization/:https://kubernetes.io/docs/concepts/cluster-administration/master-node-communication/#apiserver---kubelet",
+ "DefaultValue": "By default, certificate-based kubelet authentication is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.5",
+ "Description": "Ensure that the --kubelet-certificate-authority argument is set as appropriate",
+ "Checks": [
+ "apiserver_kubelet_cert_auth"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Verify kubelet's certificate before establishing connection.",
+ "RationaleStatement": "The connections from the apiserver to the kubelet are used for fetching logs for pods, attaching (through kubectl) to running pods, and using the kubelet’s port-forwarding functionality. These connections terminate at the kubelet’s HTTPS endpoint. By default, the apiserver does not verify the kubelet’s serving certificate, which makes the connection subject to man-in-the-middle attacks, and unsafe to run over untrusted and/or public networks.",
+ "ImpactStatement": "You require TLS to be configured on apiserver as well as kubelets.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and setup the TLS connection between the apiserver and kubelets. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--kubelet-certificate-authority` parameter to the path to the cert file for the certificate authority. ``` --kubelet-certificate-authority=<ca-string> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--kubelet-certificate-authority` argument exists and is set as appropriate. Alternative Audit ``` kubectl get pod -nkube-system -lcomponent=kube-apiserver -o=jsonpath='{range .items[]}{.spec.containers[].command} {\\}{end}' | grep '--kubelet-certificate-authority' | grep -i false ``` If the exit code is '1', then the control isn't present / failed",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/admin/kubelet-authentication-authorization/:https://kubernetes.io/docs/concepts/cluster-administration/master-node-communication/#apiserver---kubelet",
+ "DefaultValue": "By default, `--kubelet-certificate-authority` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.6",
+ "Description": "Ensure that the --authorization-mode argument is not set to AlwaysAllow",
+ "Checks": [
+ "apiserver_auth_mode_not_always_allow"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not always authorize all requests.",
+ "RationaleStatement": "The API Server, can be configured to allow all requests. This mode should not be used on any production cluster.",
+ "ImpactStatement": "Only authorized requests will be served.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--authorization-mode` parameter to values other than `AlwaysAllow`. One such example could be as below. ``` --authorization-mode=RBAC ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--authorization-mode` argument exists and is not set to `AlwaysAllow`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/admin/authorization/",
+ "DefaultValue": "By default, `AlwaysAllow` is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.7",
+ "Description": "Ensure that the --authorization-mode argument includes Node",
+ "Checks": [
+ "apiserver_auth_mode_include_node"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Restrict kubelet nodes to reading only objects associated with them.",
+ "RationaleStatement": "The `Node` authorization mode only allows kubelets to read `Secret`, `ConfigMap`, `PersistentVolume`, and `PersistentVolumeClaim` objects associated with their nodes.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--authorization-mode` parameter to a value that includes `Node`. ``` --authorization-mode=Node,RBAC ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--authorization-mode` argument exists and is set to a value to include `Node`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-apiserver/:https://kubernetes.io/docs/admin/authorization/node/:https://github.com/kubernetes/kubernetes/pull/46076:https://acotten.com/post/kube17-security",
+ "DefaultValue": "By default, `Node` authorization is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.8",
+ "Description": "Ensure that the --authorization-mode argument includes RBAC",
+ "Checks": [
+ "apiserver_auth_mode_include_rbac"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Turn on Role Based Access Control.",
+ "RationaleStatement": "Role Based Access Control (RBAC) allows fine-grained control over the operations that different entities can perform on different objects in the cluster. It is recommended to use the RBAC authorization mode.",
+ "ImpactStatement": "When RBAC is enabled you will need to ensure that appropriate RBAC settings (including Roles, RoleBindings and ClusterRoleBindings) are configured to allow appropriate access.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--authorization-mode` parameter to a value that includes `RBAC`, for example: ``` --authorization-mode=Node,RBAC ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--authorization-mode` argument exists and is set to a value to include `RBAC`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/access-authn-authz/rbac/",
+ "DefaultValue": "By default, `RBAC` authorization is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.9",
+ "Description": "Ensure that the admission control plugin EventRateLimit is set",
+ "Checks": [
+ "apiserver_event_rate_limit"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Limit the rate at which the API server accepts requests.",
+ "RationaleStatement": "Using `EventRateLimit` admission control enforces a limit on the number of events that the API Server will accept in a given time slice. A misbehaving workload could overwhelm and DoS the API Server, making it unavailable. This particularly applies to a multi-tenant cluster, where there might be a small percentage of misbehaving tenants which could have a significant impact on the performance of the cluster overall. Hence, it is recommended to limit the rate of events that the API server will accept.",
+ "ImpactStatement": "You need to carefully tune in limits as per your environment.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set the desired limits in a configuration file. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` and set the below parameters. ``` --enable-admission-plugins=...,EventRateLimit,... --admission-control-config-file=<path/to/configuration/file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--enable-admission-plugins` argument is set to a value that includes `EventRateLimit`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#eventratelimit:https://github.com/staebler/community/blob/9873b632f4d99b5d99c38c9b15fe2f8b93d0a746/contributors/design-proposals/admission_control_event_rate_limit.md",
+ "DefaultValue": "By default, `EventRateLimit` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.10",
+ "Description": "Ensure that the admission control plugin AlwaysAdmit is not set",
+ "Checks": [
+ "apiserver_no_always_admit_plugin"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not allow all requests.",
+ "RationaleStatement": "Setting admission control plugin `AlwaysAdmit` allows all requests and do not filter any requests. The `AlwaysAdmit` admission controller was deprecated in Kubernetes v1.13. Its behavior was equivalent to turning off all admission controllers.",
+ "ImpactStatement": "Only requests explicitly allowed by the admissions control plugins would be served.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and either remove the `--enable-admission-plugins` parameter, or set it to a value that does not include `AlwaysAdmit`.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that if the `--enable-admission-plugins` argument is set, its value does not include `AlwaysAdmit`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#alwaysadmit",
+ "DefaultValue": "`AlwaysAdmit` is not in the list of default admission plugins."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.11",
+ "Description": "Ensure that the admission control plugin AlwaysPullImages is set",
+ "Checks": [
+ "apiserver_always_pull_images_plugin"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Always pull images.",
+ "RationaleStatement": "Setting admission control policy to `AlwaysPullImages` forces every new pod to pull the required images every time. In a multi-tenant cluster users can be assured that their private images can only be used by those who have the credentials to pull them. Without this admission control policy, once an image has been pulled to a node, any pod from any user can use it simply by knowing the image’s name, without any authorization check against the image ownership. When this plug-in is enabled, images are always pulled prior to starting containers, which means valid credentials are required.",
+ "ImpactStatement": "Credentials would be required to pull the private images every time. Also, in trusted environments, this might increases load on network, registry, and decreases speed. This setting could impact offline or isolated clusters, which have images preloaded and do not have access to a registry to pull in-use images. This setting is not appropriate for clusters which use this configuration.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--enable-admission-plugins` parameter to include `AlwaysPullImages`. ``` --enable-admission-plugins=...,AlwaysPullImages,... ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--enable-admission-plugins` argument is set to a value that includes `AlwaysPullImages`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages",
+ "DefaultValue": "By default, `AlwaysPullImages` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.12",
+ "Description": "Ensure that the admission control plugin ServiceAccount is set",
+ "Checks": [
+ "apiserver_service_account_plugin"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Automate service accounts management.",
+ "RationaleStatement": "When you create a pod, if you do not specify a service account, it is automatically assigned the `default` service account in the same namespace. You should create your own service account and let the API server manage its security tokens.",
+ "ImpactStatement": "None.",
+ "RemediationProcedure": "Follow the documentation and create `ServiceAccount` objects as per your environment. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and ensure that the `--disable-admission-plugins` parameter is set to a value that does not include `ServiceAccount`.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--disable-admission-plugins` argument is set to a value that does not includes `ServiceAccount`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#serviceaccount:https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/",
+ "DefaultValue": "By default, `ServiceAccount` is set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.13",
+ "Description": "Ensure that the admission control plugin NamespaceLifecycle is set",
+ "Checks": [
+ "apiserver_namespace_lifecycle_plugin"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Reject creating objects in a namespace that is undergoing termination.",
+ "RationaleStatement": "Setting admission control policy to `NamespaceLifecycle` ensures that objects cannot be created in non-existent namespaces, and that namespaces undergoing termination are not used for creating the new objects. This is recommended to enforce the integrity of the namespace termination process and also for the availability of the newer objects.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--disable-admission-plugins` parameter to ensure it does not include `NamespaceLifecycle`.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--disable-admission-plugins` argument is set to a value that does not include `NamespaceLifecycle`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#namespacelifecycle",
+ "DefaultValue": "By default, `NamespaceLifecycle` is set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.14",
+ "Description": "Ensure that the admission control plugin NodeRestriction is set",
+ "Checks": [
+ "apiserver_node_restriction_plugin"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Limit the `Node` and `Pod` objects that a kubelet could modify.",
+ "RationaleStatement": "Using the `NodeRestriction` plug-in ensures that the kubelet is restricted to the `Node` and `Pod` objects that it could modify as defined. Such kubelets will only be allowed to modify their own `Node` API object, and only modify `Pod` API objects that are bound to their node.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Follow the Kubernetes documentation and configure `NodeRestriction` plug-in on kubelets. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the `--enable-admission-plugins` parameter to a value that includes `NodeRestriction`. ``` --enable-admission-plugins=...,NodeRestriction,... ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--enable-admission-plugins` argument is set to a value that includes `NodeRestriction`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#noderestriction:https://kubernetes.io/docs/reference/access-authn-authz/node/",
+ "DefaultValue": "By default, `NodeRestriction` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.15",
+ "Description": "Ensure that the --profiling argument is set to false",
+ "Checks": [
+ "apiserver_disable_profiling"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Disable profiling, if not needed.",
+ "RationaleStatement": "Profiling allows for the identification of specific performance bottlenecks. It generates a significant amount of program data that could potentially be exploited to uncover system and program details. If you are not experiencing any bottlenecks and do not need the profiler for troubleshooting purposes, it is recommended to turn it off to reduce the potential attack surface.",
+ "ImpactStatement": "Profiling information would not be available.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the below parameter. ``` --profiling=false ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--profiling` argument is set to `false`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/",
+ "DefaultValue": "By default, profiling is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.16",
+ "Description": "Ensure that the --audit-log-path argument is set",
+ "Checks": [
+ "apiserver_audit_log_path_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable auditing on the Kubernetes API Server and set the desired audit log path.",
+ "RationaleStatement": "Auditing the Kubernetes API Server provides a security-relevant chronological set of records documenting the sequence of activities that have affected system by individual users, administrators or other components of the system. Even though currently, Kubernetes provides only basic audit capabilities, it should be enabled. You can enable it by setting an appropriate audit log path.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--audit-log-path` parameter to a suitable path and file where you would like audit logs to be written, for example: ``` --audit-log-path=/var/log/apiserver/audit.log ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--audit-log-path` argument is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
+ "DefaultValue": "By default, auditing is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.17",
+ "Description": "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate",
+ "Checks": [
+ "apiserver_audit_log_maxage_set"
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Retain the logs for at least 30 days or as appropriate.",
+ "RationaleStatement": "Retaining logs for at least 30 days ensures that you can go back in time and investigate or correlate any events. Set your audit log retention period to 30 days or as per your business requirements.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--audit-log-maxage` parameter to 30 or as an appropriate number of days: ``` --audit-log-maxage=30 ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--audit-log-maxage` argument is set to `30` or as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
+ "DefaultValue": "By default, auditing is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.18",
+ "Description": "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate",
+ "Checks": [
+ "apiserver_audit_log_maxbackup_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Retain 10 or an appropriate number of old log files.",
+ "RationaleStatement": "Kubernetes automatically rotates the log files. Retaining old log files ensures that you would have sufficient log data available for carrying out any investigation or correlation. For example, if you have set file size of 100 MB and the number of old log files to keep as 10, you would approximate have 1 GB of log data that you could potentially use for your analysis.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--audit-log-maxbackup` parameter to 10 or to an appropriate value. ``` --audit-log-maxbackup=10 ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--audit-log-maxbackup` argument is set to `10` or as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
+ "DefaultValue": "By default, auditing is not enabled."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
+ ]
+ },
+ {
+ "Id": "1.2.19",
+ "Description": "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate",
+ "Checks": [
+ "apiserver_audit_log_maxsize_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Rotate log files on reaching 100 MB or as appropriate.",
+ "RationaleStatement": "Kubernetes automatically rotates the log files. Retaining old log files ensures that you would have sufficient log data available for carrying out any investigation or correlation. If you have set file size of 100 MB and the number of old log files to keep as 10, you would approximate have 1 GB of log data that you could potentially use for your analysis.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--audit-log-maxsize` parameter to an appropriate size in MB. For example, to set it as 100 MB: ``` --audit-log-maxsize=100 ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--audit-log-maxsize` argument is set to `100` or as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/:https://github.com/kubernetes/enhancements/issues/22",
+ "DefaultValue": "By default, auditing is not enabled."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
+ ]
+ },
+ {
+ "Id": "1.2.20",
+ "Description": "Ensure that the --request-timeout argument is set as appropriate",
+ "Checks": [
+ "apiserver_request_timeout_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Set global request timeout for API server requests as appropriate.",
+ "RationaleStatement": "Setting global request timeout allows extending the API server request timeout limit to a duration appropriate to the user's connection speed. By default, it is set to 60 seconds which might be problematic on slower connections making cluster resources inaccessible once the data volume for requests exceeds what can be transmitted in 60 seconds. But, setting this timeout limit to be too large can exhaust the API server resources making it prone to Denial-of-Service attack. Hence, it is recommended to set this limit as appropriate and change the default limit of 60 seconds only if needed.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` and set the below parameter as appropriate and if needed. For example, ``` --request-timeout=300s ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--request-timeout` argument is either not set or set to an appropriate value.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kubernetes/kubernetes/pull/51415",
+ "DefaultValue": "By default, `--request-timeout` is set to 60 seconds."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.21",
+ "Description": "Ensure that the --service-account-lookup argument is set to true",
+ "Checks": [
+ "apiserver_service_account_lookup_true"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Validate service account before validating token.",
+ "RationaleStatement": "If `--service-account-lookup` is not enabled, the apiserver only verifies that the authentication token is valid, and does not validate that the service account token mentioned in the request is actually present in etcd. This allows using a service account token even after the corresponding service account is deleted. This is an example of time of check to time of use security issue.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the below parameter. ``` --service-account-lookup=true ``` Alternatively, you can delete the `--service-account-lookup` parameter from this file so that the default takes effect.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that if the `--service-account-lookup` argument exists it is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kubernetes/kubernetes/issues/24167:https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use",
+ "DefaultValue": "By default, `--service-account-lookup` argument is set to `true`."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.22",
+ "Description": "Ensure that the --service-account-key-file argument is set as appropriate",
+ "Checks": [
+ "apiserver_service_account_key_file_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Explicitly set a service account public key file for service accounts on the apiserver.",
+ "RationaleStatement": "By default, if no `--service-account-key-file` is specified to the apiserver, it uses the private key from the TLS serving certificate to verify service account tokens. To ensure that the keys for service account tokens could be rotated as needed, a separate public/private key pair should be used for signing service account tokens. Hence, the public key should be specified to the apiserver with `--service-account-key-file`.",
+ "ImpactStatement": "The corresponding private key must be provided to the controller manager. You would need to securely maintain the key file and rotate the keys based on your organization's key rotation policy.",
+ "RemediationProcedure": "Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the Control Plane node and set the `--service-account-key-file` parameter to the public key file for service accounts: ``` --service-account-key-file=<filename> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--service-account-key-file` argument exists and is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kubernetes/kubernetes/issues/24167",
+ "DefaultValue": "By default, `--service-account-key-file` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.23",
+ "Description": "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate",
+ "Checks": [
+ "apiserver_etcd_tls_config"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "etcd should be configured to make use of TLS encryption for client connections.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be protected by client authentication. This requires the API server to identify itself to the etcd server using a client certificate and key.",
+ "ImpactStatement": "TLS and client certificate authentication must be configured for etcd.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the etcd certificate and key file parameters. ``` --etcd-certfile=<path/to/client-certificate-file> --etcd-keyfile=<path/to/client-key-file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--etcd-certfile` and `--etcd-keyfile` arguments exist and they are set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/",
+ "DefaultValue": "By default, `--etcd-certfile` and `--etcd-keyfile` arguments are not set"
+ }
+ ]
+ },
+ {
+ "Id": "1.2.24",
+ "Description": "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate",
+ "Checks": [
+ "apiserver_tls_config"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Setup TLS connection on the API server.",
+ "RationaleStatement": "API server communication contains sensitive parameters that should remain encrypted in transit. Configure the API server to serve only HTTPS traffic.",
+ "ImpactStatement": "TLS and client certificate authentication must be configured for your Kubernetes cluster deployment.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set up the TLS connection on the apiserver. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the TLS certificate and private key file parameters. ``` --tls-cert-file=<path/to/tls-certificate-file> --tls-private-key-file=<path/to/tls-key-file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--tls-cert-file` and `--tls-private-key-file` arguments exist and they are set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kelseyhightower/docker-kubernetes-tls-guide",
+ "DefaultValue": "By default, `--tls-cert-file` and `--tls-private-key-file` are presented and created for use."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.25",
+ "Description": "Ensure that the --client-ca-file argument is set as appropriate",
+ "Checks": [
+ "apiserver_client_ca_file_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Setup TLS connection on the API server.",
+ "RationaleStatement": "API server communication contains sensitive parameters that should remain encrypted in transit. Configure the API server to serve only HTTPS traffic. If `--client-ca-file` argument is set, any request presenting a client certificate signed by one of the authorities in the `client-ca-file` is authenticated with an identity corresponding to the CommonName of the client certificate.",
+ "ImpactStatement": "TLS and client certificate authentication must be configured for your Kubernetes cluster deployment.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set up the TLS connection on the apiserver. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the client certificate authority file. ``` --client-ca-file=<path/to/client-ca-file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--client-ca-file` argument exists and it is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kelseyhightower/docker-kubernetes-tls-guide",
+ "DefaultValue": "By default, `--client-ca-file` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.26",
+ "Description": "Ensure that the --etcd-cafile argument is set as appropriate",
+ "Checks": [
+ "apiserver_etcd_cafile_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "etcd should be configured to make use of TLS encryption for client connections.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be protected by client authentication. This requires the API server to identify itself to the etcd server using a SSL Certificate Authority file.",
+ "ImpactStatement": "TLS and client certificate authentication must be configured for etcd.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the etcd certificate authority file parameter. ``` --etcd-cafile=<path/to/ca-file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--etcd-cafile` argument exists and it is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/",
+ "DefaultValue": "By default, `--etcd-cafile` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.27",
+ "Description": "Ensure that the --encryption-provider-config argument is set as appropriate",
+ "Checks": [
+ "apiserver_encryption_provider_config_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Encrypt etcd key-value store.",
+ "RationaleStatement": "etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be encrypted at rest to avoid any disclosures.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Follow the Kubernetes documentation and configure a `EncryptionConfig` file. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the `--encryption-provider-config` parameter to the path of that file: ``` --encryption-provider-config=</path/to/EncryptionConfig/File> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--encryption-provider-config` argument is set to a `EncryptionConfig` file. Additionally, ensure that the `EncryptionConfig` file has all the desired `resources` covered especially any secrets.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/:https://acotten.com/post/kube17-security:https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kubernetes/enhancements/issues/92",
+ "DefaultValue": "By default, `--encryption-provider-config` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.28",
+ "Description": "Ensure that encryption providers are appropriately configured",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Where `etcd` encryption is used, appropriate providers should be configured.",
+ "RationaleStatement": "Where `etcd` encryption is used, it is important to ensure that the appropriate set of encryption providers is used. Currently, the `aescbc`, `kms`, and `secretbox` are likely to be appropriate options.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Follow the Kubernetes documentation and configure a `EncryptionConfig` file. In this file, choose `aescbc`, `kms`, or `secretbox` as the encryption provider.",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Get the `EncryptionConfig` file set for `--encryption-provider-config` argument. Verify that `aescbc`, `kms`, or `secretbox` is set as the encryption provider for all the desired `resources`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/:https://acotten.com/post/kube17-security:https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/kubernetes/enhancements/issues/92:https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#providers",
+ "DefaultValue": "By default, no encryption provider is set."
+ }
+ ]
+ },
+ {
+ "Id": "1.2.29",
+ "Description": "Ensure that the API Server only makes use of Strong Cryptographic Ciphers",
+ "Checks": [
+ "apiserver_strong_ciphers_only"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the API server is configured to only use strong cryptographic ciphers.",
+ "RationaleStatement": "TLS ciphers have had a number of known vulnerabilities and weaknesses, which can reduce the protection provided by them. By default Kubernetes supports a number of TLS cipher suites including some that have security concerns, weakening the protection provided.",
+ "ImpactStatement": "API server clients that cannot support modern cryptographic ciphers will not be able to make connections to the API server.",
+ "RemediationProcedure": "Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the Control Plane node and set the below parameter. ``` --tls-cipher-suites=TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256. ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the `--tls-cipher-suites` argument returns a value that is in this list `TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`.",
+ "AdditionalInformation": "Insecure values: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_RC4_128_SHA.",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/:https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices#23-use-secure-cipher-suites",
+ "DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_strong_ciphers_only",
+ "ConfigKey": "apiserver_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_AES_128_GCM_SHA256",
+ "TLS_AES_256_GCM_SHA384",
+ "TLS_CHACHA20_POLY1305_SHA256"
+ ]
+ }
+ ]
+ },
+ {
+ "Id": "1.2.30",
+ "Description": "Ensure that the --service-account-extend-token-expiration parameter is set to false",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.2 API Server",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "By default Kubernetes extends service account token lifetimes to one year to aid in transition from the legacy token settings.",
+ "RationaleStatement": "This default setting is not ideal for security as it ignores other settings related to maximum token lifetime and means that a lost or stolen credential could be valid for an extended period of time.",
+ "ImpactStatement": "Disabling this setting means that the service account token expiry set in the cluster will be enforced, and service account tokens will expire at the end of that time frame.",
+ "RemediationProcedure": "Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the Control Plane node and set the --service-account-extend-token-expiration parameter to false. ``` --service-account-extend-token-expiration=false ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-apiserver ``` Verify that the --service-account-extend-token-expiration argument is set to false.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/",
+ "DefaultValue": "By default, this parameter is set to true"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.1",
+ "Description": "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate",
+ "Checks": [
+ "controllermanager_garbage_collection"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Activate garbage collector on pod termination, as appropriate.",
+ "RationaleStatement": "Garbage collection is important to ensure sufficient resource availability and avoiding degraded performance and availability. In the worst case, the system might crash or just be unusable for a long period of time. The current setting for garbage collection is 12,500 terminated pods which might be too high for your system to sustain. Based on your system resources and tests, choose an appropriate threshold value to activate garbage collection.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and set the `--terminated-pod-gc-threshold` to an appropriate threshold, for example: ``` --terminated-pod-gc-threshold=10 ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--terminated-pod-gc-threshold` argument is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/:https://github.com/kubernetes/kubernetes/issues/28484",
+ "DefaultValue": "By default, `--terminated-pod-gc-threshold` is set to `12500`."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.2",
+ "Description": "Ensure that the --profiling argument is set to false",
+ "Checks": [
+ "controllermanager_disable_profiling"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Disable profiling, if not needed.",
+ "RationaleStatement": "Profiling allows for the identification of specific performance bottlenecks. It generates a significant amount of program data that could potentially be exploited to uncover system and program details. If you are not experiencing any bottlenecks and do not need the profiler for troubleshooting purposes, it is recommended to turn it off to reduce the potential attack surface.",
+ "ImpactStatement": "Profiling information would not be available.",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and set the below parameter. ``` --profiling=false ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--profiling` argument is set to `false`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/:https://github.com/kubernetes/community/blob/master/contributors/devel/profiling.md",
+ "DefaultValue": "By default, profiling is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.3",
+ "Description": "Ensure that the --use-service-account-credentials argument is set to true",
+ "Checks": [
+ "controllermanager_service_account_credentials"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Use individual service account credentials for each controller.",
+ "RationaleStatement": "The controller manager creates a service account per controller in the `kube-system` namespace, generates a credential for it, and builds a dedicated API client with that service account credential for each controller loop to use. Setting the `--use-service-account-credentials` to `true` runs each control loop within the controller manager using a separate service account credential. When used in combination with RBAC, this ensures that the control loops run with the minimum permissions required to perform their intended tasks.",
+ "ImpactStatement": "Whatever authorizer is configured for the cluster, it must grant sufficient permissions to the service accounts to perform their intended tasks. When using the RBAC authorizer, those roles are created and bound to the appropriate service accounts in the `kube-system` namespace automatically with default roles and rolebindings that are auto-reconciled on startup. If using other authorization methods (ABAC, Webhook, etc), the cluster deployer is responsible for granting appropriate permissions to the service accounts (the required permissions can be seen by inspecting the `controller-roles.yaml` and `controller-role-bindings.yaml` files for the RBAC roles.",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node to set the below parameter. ``` --use-service-account-credentials=true ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--use-service-account-credentials` argument is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/:https://kubernetes.io/docs/admin/service-accounts-admin/:https://github.com/kubernetes/kubernetes/blob/release-1.6/plugin/pkg/auth/authorizer/rbac/bootstrappolicy/testdata/controller-roles.yaml:https://github.com/kubernetes/kubernetes/blob/release-1.6/plugin/pkg/auth/authorizer/rbac/bootstrappolicy/testdata/controller-role-bindings.yaml:https://kubernetes.io/docs/admin/authorization/rbac/#controller-roles",
+ "DefaultValue": "By default, `--use-service-account-credentials` is set to false."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.4",
+ "Description": "Ensure that the --service-account-private-key-file argument is set as appropriate",
+ "Checks": [
+ "controllermanager_service_account_private_key_file"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Explicitly set a service account private key file for service accounts on the controller manager.",
+ "RationaleStatement": "To ensure that keys for service account tokens can be rotated as needed, a separate public/private key pair should be used for signing service account tokens. The private key should be specified to the controller manager with `--service-account-private-key-file` as appropriate.",
+ "ImpactStatement": "You would need to securely maintain the key file and rotate the keys based on your organization's key rotation policy.",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and set the `--service-account-private-key-file` parameter to the private key file for service accounts. ``` --service-account-private-key-file=<filename> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--service-account-private-key-file` argument is set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/",
+ "DefaultValue": "By default, `--service-account-private-key-file` it not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.5",
+ "Description": "Ensure that the --root-ca-file argument is set as appropriate",
+ "Checks": [
+ "controllermanager_root_ca_file_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Allow pods to verify the API server's serving certificate before establishing connections.",
+ "RationaleStatement": "Processes running within pods that need to contact the API server must verify the API server's serving certificate. Failing to do so could be a subject to man-in-the-middle attacks. Providing the root certificate for the API server's serving certificate to the controller manager with the `--root-ca-file` argument allows the controller manager to inject the trusted bundle into pods so that they can verify TLS connections to the API server.",
+ "ImpactStatement": "You need to setup and maintain root certificate authority file.",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and set the `--root-ca-file` parameter to the certificate bundle file`. ``` --root-ca-file=<path/to/file> ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--root-ca-file` argument exists and is set to a certificate bundle file containing the root certificate for the API server's serving certificate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-controller-manager/:https://github.com/kubernetes/kubernetes/issues/11000",
+ "DefaultValue": "By default, `--root-ca-file` is not set."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.6",
+ "Description": "Ensure that the RotateKubeletServerCertificate argument is set to true",
+ "Checks": [
+ "controllermanager_rotate_kubelet_server_cert"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable kubelet server certificate rotation on controller-manager.",
+ "RationaleStatement": "`RotateKubeletServerCertificate` causes the kubelet to both request a serving certificate after bootstrapping its client credentials and rotate the certificate as its existing credentials expire. This automated periodic rotation ensures that the there are no downtimes due to expired certificates and thus addressing availability in the CIA security triad. Note: This recommendation only applies if you let kubelets get their certificates from the API server. In case your kubelet certificates come from an outside authority/tool (e.g. Vault) then you need to take care of rotation yourself.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and set the `--feature-gates` parameter to include `RotateKubeletServerCertificate=true`. ``` --feature-gates=RotateKubeletServerCertificate=true ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that `RotateKubeletServerCertificate` argument exists and is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet-tls-bootstrapping/#approval-controller:https://github.com/kubernetes/features/issues/267:https://github.com/kubernetes/kubernetes/pull/45059:https://kubernetes.io/docs/admin/kube-controller-manager/",
+ "DefaultValue": "By default, `RotateKubeletServerCertificate` is set to true this recommendation verifies that it has not been disabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.3.7",
+ "Description": "Ensure that the --bind-address argument is set to 127.0.0.1",
+ "Checks": [
+ "controllermanager_bind_address"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.3 Controller Manager",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not bind the Controller Manager service to non-loopback insecure addresses.",
+ "RationaleStatement": "The Controller Manager API service which runs on port 10252/TCP by default is used for health and metrics information and is available without authentication or encryption. As such it should only be bound to a localhost interface, to minimize the cluster's attack surface",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the Controller Manager pod specification file `/etc/kubernetes/manifests/kube-controller-manager.yaml` on the Control Plane node and ensure the correct value for the `--bind-address` parameter",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-controller-manager ``` Verify that the `--bind-address` argument is set to 127.0.0.1",
+ "AdditionalInformation": "Although the current Kubernetes documentation site says that `--address` is deprecated in favour of `--bind-address` Kubeadm 1.11 still makes use of `--address`",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/",
+ "DefaultValue": "By default, the `--bind-address` parameter is set to 0.0.0.0"
+ }
+ ]
+ },
+ {
+ "Id": "1.4.1",
+ "Description": "Ensure that the --profiling argument is set to false",
+ "Checks": [
+ "scheduler_profiling"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.4 Scheduler",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Disable profiling, if not needed.",
+ "RationaleStatement": "Profiling allows for the identification of specific performance bottlenecks. It generates a significant amount of program data that could potentially be exploited to uncover system and program details. If you are not experiencing any bottlenecks and do not need the profiler for troubleshooting purposes, it is recommended to turn it off to reduce the potential attack surface.",
+ "ImpactStatement": "Profiling information would not be available.",
+ "RemediationProcedure": "Edit the Scheduler pod specification file `/etc/kubernetes/manifests/kube-scheduler.yaml` file on the Control Plane node and set the below parameter. ``` --profiling=false ```",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-scheduler ``` Verify that the `--profiling` argument is set to `false`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-scheduler/:https://github.com/kubernetes/community/blob/master/contributors/devel/profiling.md",
+ "DefaultValue": "By default, profiling is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "1.4.2",
+ "Description": "Ensure that the --bind-address argument is set to 127.0.0.1",
+ "Checks": [
+ "scheduler_bind_address"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Control Plane Components",
+ "SubSection": "1.4 Scheduler",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not bind the scheduler service to non-loopback insecure addresses.",
+ "RationaleStatement": "The Scheduler API service which runs on port 10251/TCP by default is used for health and metrics information and is available without authentication or encryption. As such it should only be bound to a localhost interface, to minimize the cluster's attack surface",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the Scheduler pod specification file `/etc/kubernetes/manifests/kube-scheduler.yaml` on the Control Plane node and ensure the correct value for the `--bind-address` parameter",
+ "AuditProcedure": "Run the following command on the Control Plane node: ``` ps -ef | grep kube-scheduler ``` Verify that the `--bind-address` argument is set to 127.0.0.1",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/",
+ "DefaultValue": "By default, the `--bind-address` parameter is set to 0.0.0.0"
+ }
+ ]
+ },
+ {
+ "Id": "2.1",
+ "Description": "Ensure that the --cert-file and --key-file arguments are set as appropriate",
+ "Checks": [
+ "etcd_tls_encryption"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Configure TLS encryption for the etcd service.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be encrypted in transit.",
+ "ImpactStatement": "Client connections only over TLS would be served.",
+ "RemediationProcedure": "Follow the etcd service documentation and configure TLS encryption. Then, edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameters. ``` --cert-file=</path/to/ca-file> --key-file=</path/to/key-file> ```",
+ "AuditProcedure": "Run the following command on the etcd server node ``` ps -ef | grep etcd ``` Verify that the `--cert-file` and the `--key-file` arguments are set as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "By default, TLS encryption is not set."
+ }
+ ]
+ },
+ {
+ "Id": "2.2",
+ "Description": "Ensure that the --client-cert-auth argument is set to true",
+ "Checks": [
+ "etcd_client_cert_auth"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable client authentication on etcd service.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should not be available to unauthenticated clients. You should enable the client authentication via valid certificates to secure the access to the etcd service.",
+ "ImpactStatement": "All clients attempting to access the etcd server will require a valid client certificate.",
+ "RemediationProcedure": "Edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameter. ``` --client-cert-auth=true ```",
+ "AuditProcedure": "Run the following command on the etcd server node: ``` ps -ef | grep etcd ``` Verify that the `--client-cert-auth` argument is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/:https://coreos.com/etcd/docs/latest/op-guide/configuration.html#client-cert-auth",
+ "DefaultValue": "By default, the etcd service can be queried by unauthenticated clients."
+ }
+ ]
+ },
+ {
+ "Id": "2.3",
+ "Description": "Ensure that the --auto-tls argument is not set to true",
+ "Checks": [
+ "etcd_no_auto_tls"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not use self-signed certificates for TLS.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should not be available to unauthenticated clients. You should enable the client authentication via valid certificates to secure the access to the etcd service.",
+ "ImpactStatement": "Clients will not be able to use self-signed certificates for TLS.",
+ "RemediationProcedure": "Edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and either remove the `--auto-tls` parameter or set it to `false`. ``` --auto-tls=false ```",
+ "AuditProcedure": "Run the following command on the etcd server node: ``` ps -ef | grep etcd ``` Verify that if the `--auto-tls` argument exists, it is not set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/:https://coreos.com/etcd/docs/latest/op-guide/configuration.html#auto-tls",
+ "DefaultValue": "By default, `--auto-tls` is set to `false`."
+ }
+ ]
+ },
+ {
+ "Id": "2.4",
+ "Description": "Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate",
+ "Checks": [
+ "etcd_peer_tls_config"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "etcd should be configured to make use of TLS encryption for peer connections.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be encrypted in transit and also amongst peers in the etcd clusters.",
+ "ImpactStatement": "etcd cluster peers would need to set up TLS for their communication.",
+ "RemediationProcedure": "Follow the etcd service documentation and configure peer TLS encryption as appropriate for your etcd cluster. Then, edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameters. ``` --peer-client-file=</path/to/peer-cert-file> --peer-key-file=</path/to/peer-key-file> ```",
+ "AuditProcedure": "Run the following command on the etcd server node: ``` ps -ef | grep etcd ``` Verify that the `--peer-cert-file` and `--peer-key-file` arguments are set as appropriate. **Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/",
+ "DefaultValue": "**Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable. By default, peer communication over TLS is not configured."
+ }
+ ]
+ },
+ {
+ "Id": "2.5",
+ "Description": "Ensure that the --peer-client-cert-auth argument is set to true",
+ "Checks": [
+ "etcd_peer_client_cert_auth"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "etcd should be configured for peer authentication.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be accessible only by authenticated etcd peers in the etcd cluster.",
+ "ImpactStatement": "All peers attempting to communicate with the etcd server will require a valid client certificate for authentication.",
+ "RemediationProcedure": "Edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameter. ``` --peer-client-cert-auth=true ```",
+ "AuditProcedure": "Run the following command on the etcd server node: ``` ps -ef | grep etcd ``` Verify that the `--peer-client-cert-auth` argument is set to `true`. **Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/:https://coreos.com/etcd/docs/latest/op-guide/configuration.html#peer-client-cert-auth",
+ "DefaultValue": "**Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable. By default, `--peer-client-cert-auth` argument is set to `false`."
+ }
+ ]
+ },
+ {
+ "Id": "2.6",
+ "Description": "Ensure that the --peer-auto-tls argument is not set to true",
+ "Checks": [
+ "etcd_no_peer_auto_tls"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not use automatically generated self-signed certificates for TLS connections between peers.",
+ "RationaleStatement": "etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be accessible only by authenticated etcd peers in the etcd cluster. Hence, do not use self-signed certificates for authentication.",
+ "ImpactStatement": "All peers attempting to communicate with the etcd server will require a valid client certificate for authentication.",
+ "RemediationProcedure": "Edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and either remove the `--peer-auto-tls` parameter or set it to `false`. ``` --peer-auto-tls=false ```",
+ "AuditProcedure": "Run the following command on the etcd server node: ``` ps -ef | grep etcd ``` Verify that if the `--peer-auto-tls` argument exists, it is not set to `true`. **Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html:https://kubernetes.io/docs/admin/etcd/:https://coreos.com/etcd/docs/latest/op-guide/configuration.html#peer-auto-tls",
+ "DefaultValue": "**Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable. By default, `--peer-auto-tls` argument is set to `false`."
+ }
+ ]
+ },
+ {
+ "Id": "2.7",
+ "Description": "Ensure that a unique Certificate Authority is used for etcd",
+ "Checks": [
+ "etcd_unique_ca"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 etcd",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Use a different certificate authority for etcd from the one used for Kubernetes.",
+ "RationaleStatement": "etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. Its access should be restricted to specifically designated clients and peers only. Authentication to etcd is based on whether the certificate presented was issued by a trusted certificate authority. There is no checking of certificate attributes such as common name or subject alternative name. As such, if any attackers were able to gain access to any certificate issued by the trusted certificate authority, they would be able to gain full access to the etcd database.",
+ "ImpactStatement": "Additional management of the certificates and keys for the dedicated certificate authority will be required.",
+ "RemediationProcedure": "Follow the etcd documentation and create a dedicated certificate authority setup for the etcd service. Then, edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameter. ``` --trusted-ca-file=</path/to/ca-file> ```",
+ "AuditProcedure": "Review the CA used by the etcd environment and ensure that it does not match the CA certificate file used for the management of the overall Kubernetes cluster. Run the following command on the master node: ``` ps -ef | grep etcd ``` Note the file referenced by the `--trusted-ca-file` argument. Run the following command on the master node: ``` ps -ef | grep apiserver ``` Verify that the file referenced by the `--client-ca-file` for apiserver is different from the `--trusted-ca-file` used by etcd.",
+ "AdditionalInformation": "",
+ "References": "https://coreos.com/etcd/docs/latest/op-guide/security.html",
+ "DefaultValue": "By default, no etcd certificate is created and used."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.1",
+ "Description": "Client certificate authentication should not be used for users",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Control Plane Configuration",
+ "SubSection": "3.1 Authentication and Authorization",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes provides the option to use client certificates for user authentication. However as there is no way to revoke these certificates when a user leaves an organization or loses their credential, they are not suitable for this purpose. It is not possible to fully disable client certificate use within a cluster as it is used for component to component authentication.",
+ "RationaleStatement": "With any authentication mechanism the ability to revoke credentials if they are compromised or no longer required, is a key control. Kubernetes client certificate authentication does not allow for this due to a lack of support for certificate revocation.",
+ "ImpactStatement": "External mechanisms for authentication generally require additional software to be deployed.",
+ "RemediationProcedure": "Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented in place of client certificates.",
+ "AuditProcedure": "Review user access to the cluster and ensure that users are not making use of Kubernetes client certificate authentication.",
+ "AdditionalInformation": "The lack of certificate revocation was flagged up as a high risk issue in the recent Kubernetes security audit. Without this feature, client certificate authentication is not suitable for end users.",
+ "References": "",
+ "DefaultValue": "Client certificate authentication is enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.2",
+ "Description": "Service account token authentication should not be used for users",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Control Plane Configuration",
+ "SubSection": "3.1 Authentication and Authorization",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes provides service account tokens which are intended for use by workloads running in the Kubernetes cluster, for authentication to the API server. These tokens are not designed for use by end-users and do not provide for features such as revocation or expiry, making them insecure. A newer version of the feature (Bound service account token volumes) does introduce expiry but still does not allow for specific revocation.",
+ "RationaleStatement": "With any authentication mechanism the ability to revoke credentials if they are compromised or no longer required, is a key control. Service account token authentication does not allow for this due to the use of JWT tokens as an underlying technology.",
+ "ImpactStatement": "External mechanisms for authentication generally require additional software to be deployed.",
+ "RemediationProcedure": "Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented in place of service account tokens.",
+ "AuditProcedure": "Review user access to the cluster and ensure that users are not making use of service account token authentication.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Service account token authentication is enabled by default."
+ }
+ ]
+ },
+ {
+ "Id": "3.1.3",
+ "Description": "Bootstrap token authentication should not be used for users",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Control Plane Configuration",
+ "SubSection": "3.1 Authentication and Authorization",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes provides bootstrap tokens which are intended for use by new nodes joining the cluster These tokens are not designed for use by end-users they are specifically designed for the purpose of bootstrapping new nodes and not for general authentication",
+ "RationaleStatement": "Bootstrap tokens are not intended for use as a general authentication mechanism and impose constraints on user and group naming that do not facilitate good RBAC design. They also cannot be used with MFA resulting in a weak authentication mechanism being available.",
+ "ImpactStatement": "External mechanisms for authentication generally require additional software to be deployed.",
+ "RemediationProcedure": "Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented in place of bootstrap tokens.",
+ "AuditProcedure": "Review user access to the cluster and ensure that users are not making use of bootstrap token authentication.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Bootstrap token authentication is not enabled by default and requires an API server parameter to be set."
+ }
+ ]
+ },
+ {
+ "Id": "3.2.1",
+ "Description": "Ensure that a minimal audit policy is created",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Control Plane Configuration",
+ "SubSection": "3.2 Logging",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes can audit the details of requests made to the API server. The `--audit-policy-file` flag must be set for this logging to be enabled.",
+ "RationaleStatement": "Logging is an important detective control for all systems, to detect potential unauthorised access.",
+ "ImpactStatement": "Audit logs will be created on the master nodes, which will consume disk space. Care should be taken to avoid generating too large volumes of log information as this could impact the available of the cluster nodes.",
+ "RemediationProcedure": "Create an audit policy file for your cluster.",
+ "AuditProcedure": "Run the following command on one of the cluster master nodes: ``` ps -ef | grep kube-apiserver ``` Verify that the `--audit-policy-file` is set. Review the contents of the file specified and ensure that it contains a valid audit policy.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/debug-application-cluster/audit/",
+ "DefaultValue": "Unless the `--audit-policy-file` flag is specified, no auditing will be carried out."
+ }
+ ]
+ },
+ {
+ "Id": "3.2.2",
+ "Description": "Ensure that the audit policy covers key security concerns",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Control Plane Configuration",
+ "SubSection": "3.2 Logging",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the audit policy created for the cluster covers key security concerns.",
+ "RationaleStatement": "Security audit logs should cover access and modification of key resources in the cluster, to enable them to form an effective part of a security environment.",
+ "ImpactStatement": "Increasing audit logging will consume resources on the nodes or other log destination.",
+ "RemediationProcedure": "Consider modification of the audit policy in use on the cluster to include these items, at a minimum.",
+ "AuditProcedure": "Review the audit policy provided for the cluster and ensure that it covers at least the following areas :- - Access to Secrets managed by the cluster. Care should be taken to only log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in order to avoid the risk of logging sensitive data. - Modification of `pod` and `deployment` objects. - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`. - Use of the `CertificateSigningRequest` API which allows for creation of new credentials. - Use of the Token sub-resource of `ServiceAccount` objects which allows for creation of new credentials. For most requests, minimally logging at the Metadata level is recommended (the most basic level of logging). Exceptions should be created in the audit logging policy to ensure that system operations (e.g. the Kubelet creating new credentials) are not logged, to reduce operational load and the risk of false positives.",
+ "AdditionalInformation": "",
+ "References": "https://github.com/k8scop/k8s-security-dashboard/blob/master/configs/kubernetes/adv-audit.yaml:https://kubernetes.io/docs/tasks/debug-application-cluster/audit/#audit-policy:https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure-helper.sh#L735",
+ "DefaultValue": "By default Kubernetes clusters do not log audit information."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.1",
+ "Description": "Ensure that the kubelet service file permissions are set to 600 or more restrictive",
+ "Checks": [
+ "kubelet_service_file_permissions"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `kubelet` service file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The `kubelet` service file controls various parameters that set the behavior of the `kubelet` service in the worker node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chmod 600 /etc/systemd/system/kubelet.service.d/kubeadm.conf ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet service config file. Please set $kubelet_service_config=<PATH><filename> based on the file location on your system for example: ``` export kubelet_service_config=/etc/systemd/system/kubelet.service.d/kubeadm.conf ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %a /etc/systemd/system/kubelet.service.d/10-kubeadm.conf ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#44-joining-your-nodes:https://kubernetes.io/docs/admin/kubeadm/#kubelet-drop-in",
+ "DefaultValue": "By default, the `kubelet` service file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.2",
+ "Description": "Ensure that the kubelet service file ownership is set to root:root",
+ "Checks": [
+ "kubelet_service_file_ownership_root"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `kubelet` service file ownership is set to `root:root`.",
+ "RationaleStatement": "The `kubelet` service file controls various parameters that set the behavior of the `kubelet` service in the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chown root:root /etc/systemd/system/kubelet.service.d/kubeadm.conf ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet service config file. Please set $kubelet_service_config=<PATH><filename> based on the file location on your system for example: ``` export kubelet_service_config=/etc/systemd/system/kubelet.service.d/kubeadm.conf ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %U:%G /etc/systemd/system/kubelet.service.d/10-kubeadm.conf ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#44-joining-your-nodes:https://kubernetes.io/docs/admin/kubeadm/#kubelet-drop-in",
+ "DefaultValue": "By default, `kubelet` service file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.3",
+ "Description": "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "If `kube-proxy` is running, and if it is using a file-based kubeconfig file, ensure that the proxy kubeconfig file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The `kube-proxy` kubeconfig file controls various parameters of the `kube-proxy` service in the worker node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system. It is possible to run `kube-proxy` with the kubeconfig parameters configured as a Kubernetes ConfigMap instead of a file. In this case, there is no proxy kubeconfig file.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chmod 600 <proxy kubeconfig file> ```",
+ "AuditProcedure": "Find the kubeconfig file being used by `kube-proxy` by running the following command: ``` ps -ef | grep kube-proxy ``` If `kube-proxy` is running, get the kubeconfig file location from the `--kubeconfig` parameter. To perform the audit: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %a <path><filename> ``` Verify that a file is specified and it exists with permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-proxy/",
+ "DefaultValue": "By default, proxy file has permissions of `640`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.4",
+ "Description": "If proxy kubeconfig file exists ensure ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "If `kube-proxy` is running, ensure that the file ownership of its kubeconfig file is set to `root:root`.",
+ "RationaleStatement": "The kubeconfig file for `kube-proxy` controls various parameters for the `kube-proxy` service in the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chown root:root <proxy kubeconfig file> ```",
+ "AuditProcedure": "Find the kubeconfig file being used by `kube-proxy` by running the following command: ``` ps -ef | grep kube-proxy ``` If `kube-proxy` is running, get the kubeconfig file location from the `--kubeconfig` parameter. To perform the audit: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %U:%G <path><filename> ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kube-proxy/",
+ "DefaultValue": "By default, `proxy` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.5",
+ "Description": "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive",
+ "Checks": [
+ "kubelet_conf_file_permissions"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `kubelet.conf` file has permissions of `600` or more restrictive.",
+ "RationaleStatement": "The `kubelet.conf` file is the kubeconfig file for the node, and controls various parameters that set the behavior and identity of the worker node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chmod 600 /etc/kubernetes/kubelet.conf ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet config file. Please set $kubelet_config=<PATH><filename> based on the file location on your system for example: ``` export kubelet_config=/etc/kubernetes/kubelet.conf ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %a /etc/kubernetes/kubelet.conf ``` Verify that the ownership is set to `root:root`.Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/",
+ "DefaultValue": "By default, `kubelet.conf` file has permissions of `600`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.6",
+ "Description": "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root",
+ "Checks": [
+ "kubelet_conf_file_ownership"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that the `kubelet.conf` file ownership is set to `root:root`.",
+ "RationaleStatement": "The `kubelet.conf` file is the kubeconfig file for the node, and controls various parameters that set the behavior and identity of the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the below command (based on the file location on your system) on the each worker node. For example, ``` chown root:root /etc/kubernetes/kubelet.conf ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet config file. Please set $kubelet_config=<PATH><filename> based on the file location on your system for example: ``` export kubelet_config=/etc/kubernetes/kubelet.conf ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %U:%G /etc/kubernetes/kubelet.conf ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/",
+ "DefaultValue": "By default, `kubelet.conf` file ownership is set to `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.7",
+ "Description": "Ensure that the certificate authorities file permissions are set to 644 or more restrictive",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the certificate authorities file has permissions of `644` or more restrictive.",
+ "RationaleStatement": "The certificate authorities file controls the authorities used to validate API requests. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the following command to modify the file permissions of the `--client-ca-file` ``` chmod 644 <filename> ```",
+ "AuditProcedure": "Run the following command: ``` ps -ef | grep kubelet ``` Find the file specified by the `--client-ca-file` argument. Run the following command: ``` stat -c %a <filename> ``` Verify that the permissions are `644` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/authentication/#x509-client-certs",
+ "DefaultValue": "By default no `--client-ca-file` is specified."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.8",
+ "Description": "Ensure that the client certificate authorities file ownership is set to root:root",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the certificate authorities file ownership is set to `root:root`.",
+ "RationaleStatement": "The certificate authorities file controls the authorities used to validate API requests. You should set its file ownership to maintain the integrity of the file. The file should be owned by `root:root`.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the following command to modify the ownership of the `--client-ca-file`. ``` chown root:root <filename> ```",
+ "AuditProcedure": "Run the following command: ``` ps -ef | grep kubelet ``` Find the file specified by the `--client-ca-file` argument. Run the following command: ``` stat -c %U:%G <filename> ``` Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/authentication/#x509-client-certs",
+ "DefaultValue": "By default no `--client-ca-file` is specified."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.9",
+ "Description": "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive",
+ "Checks": [
+ "kubelet_config_yaml_permissions"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that if the kubelet refers to a configuration file with the `--config` argument, that file has permissions of 600 or more restrictive.",
+ "RationaleStatement": "The kubelet reads various parameters, including security settings, from a config file specified by the `--config` argument. If this file is specified you should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the following command (using the config file location identified in the Audit step) ``` chmod 600 /var/lib/kubelet/config.yaml ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet config yaml file. Please set $kubelet_config_yaml=<PATH><filename> based on the file location on your system for example: ``` export kubelet_config_yaml=/var/lib/kubelet/config.yaml ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %a /var/lib/kubelet/config.yaml ``` Verify that the permissions are `600` or more restrictive.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/",
+ "DefaultValue": "By default, the /var/lib/kubelet/config.yaml file as set up by `kubeadm` has permissions of 600."
+ }
+ ]
+ },
+ {
+ "Id": "4.1.10",
+ "Description": "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root",
+ "Checks": [
+ "kubelet_config_yaml_ownership"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.1 Worker Node Configuration Files",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Ensure that if the kubelet refers to a configuration file with the `--config` argument, that file is owned by root:root.",
+ "RationaleStatement": "The kubelet reads various parameters, including security settings, from a config file specified by the `--config` argument. If this file is specified you should restrict its file permissions to maintain the integrity of the file. The file should be owned by root:root.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Run the following command (using the config file location identied in the Audit step) ``` chown root:root /etc/kubernetes/kubelet.conf ```",
+ "AuditProcedure": "Automated AAC auditing has been modified to allow CIS-CAT to input a variable for the <PATH>/<FILENAME> of the kubelet config yaml file. Please set $kubelet_config_yaml=<PATH><filename> based on the file location on your system for example: ``` export kubelet_config_yaml=/var/lib/kubelet/config.yaml ``` To perform the audit manually: Run the below command (based on the file location on your system) on the each worker node. For example, ``` stat -c %U:%G /var/lib/kubelet/config.yaml ```Verify that the ownership is set to `root:root`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/",
+ "DefaultValue": "By default, `/var/lib/kubelet/config.yaml` file as set up by `kubeadm` is owned by `root:root`."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.1",
+ "Description": "Ensure that the --anonymous-auth argument is set to false",
+ "Checks": [
+ "kubelet_disable_anonymous_auth"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Disable anonymous requests to the Kubelet server.",
+ "RationaleStatement": "When enabled, requests that are not rejected by other configured authentication methods are treated as anonymous requests. These requests are then served by the Kubelet server. You should rely on authentication to authorize access and disallow anonymous requests.",
+ "ImpactStatement": "Anonymous requests will be rejected.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to `false`. If using executable arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_SYSTEM_PODS_ARGS` variable. ``` --anonymous-auth=false ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "If using a Kubelet configuration file, check that there is an entry for `authentication: anonymous: enabled` set to `false`. Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the `--anonymous-auth` argument is set to `false`. This executable argument may be omitted, provided there is a corresponding entry set to `false` in the Kubelet config file.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://kubernetes.io/docs/admin/kubelet-authentication-authorization/#kubelet-authentication",
+ "DefaultValue": "By default, anonymous access is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.2",
+ "Description": "Ensure that the --authorization-mode argument is not set to AlwaysAllow",
+ "Checks": [
+ "kubelet_authorization_mode"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Do not allow all requests. Enable explicit authorization.",
+ "RationaleStatement": "Kubelets, by default, allow all authenticated requests (even anonymous ones) without needing explicit authorization checks from the apiserver. You should restrict this behavior and only allow explicitly authorized requests.",
+ "ImpactStatement": "Unauthorized requests will be denied.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `authorization: mode` to `Webhook`. If using executable arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_AUTHZ_ARGS` variable. ``` --authorization-mode=Webhook ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` If the `--authorization-mode` argument is present check that it is not set to `AlwaysAllow`. If it is not present check that there is a Kubelet config file specified by `--config`, and that file sets `authorization: mode` to something other than `AlwaysAllow`. It is also possible to review the running configuration of a Kubelet via the `/configz` endpoint on the Kubelet API port (typically `10250/TCP`). Accessing these with appropriate credentials will provide details of the Kubelet's configuration.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://kubernetes.io/docs/admin/kubelet-authentication-authorization/#kubelet-authentication",
+ "DefaultValue": "By default, `--authorization-mode` argument is set to `AlwaysAllow`."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.3",
+ "Description": "Ensure that the --client-ca-file argument is set as appropriate",
+ "Checks": [
+ "kubelet_client_ca_file_set"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable Kubelet authentication using certificates.",
+ "RationaleStatement": "The connections from the apiserver to the kubelet are used for fetching logs for pods, attaching (through kubectl) to running pods, and using the kubelet’s port-forwarding functionality. These connections terminate at the kubelet’s HTTPS endpoint. By default, the apiserver does not verify the kubelet’s serving certificate, which makes the connection subject to man-in-the-middle attacks, and unsafe to run over untrusted and/or public networks. Enabling Kubelet certificate authentication ensures that the apiserver could authenticate the Kubelet before submitting any requests.",
+ "ImpactStatement": "You require TLS to be configured on apiserver as well as kubelets.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `authentication: x509: clientCAFile` to the location of the client CA file. If using command line arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_AUTHZ_ARGS` variable. ``` --client-ca-file=<path/to/client-ca-file> ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the `--client-ca-file` argument exists and is set to the location of the client certificate authority file. If the `--client-ca-file` argument is not present, check that there is a Kubelet config file specified by `--config`, and that the file sets `authentication: x509: clientCAFile` to the location of the client certificate authority file.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-authentication-authorization/",
+ "DefaultValue": "By default, `--client-ca-file` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.4",
+ "Description": "Verify that if defined, readOnlyPort is set to 0",
+ "Checks": [
+ "kubelet_disable_read_only_port"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Disable the read-only port.",
+ "RationaleStatement": "The Kubelet process provides a read-only API in addition to the main Kubelet API. Unauthenticated access is provided to this read-only API which could possibly retrieve potentially sensitive information about the cluster.",
+ "ImpactStatement": "Removal of the read-only port will require that any service which made use of it will need to be re-configured to use the main Kubelet API.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `readOnlyPort` to `0`. If using command line arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_SYSTEM_PODS_ARGS` variable. ``` --read-only-port=0 ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the `--read-only-port` argument exists and is set to `0`. If the `--read-only-port` argument is not present, check that there is a Kubelet config file specified by `--config`. Check that if there is a `readOnlyPort` entry in the file, it is set to `0`.",
+ "AdditionalInformation": "https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://github.com/kubernetes/kubernetes/blob/6cedc0853faa118df0ba3d41b48b993422ad3df6/staging/src/k8s.io/kubelet/config/v1beta1/types.go#L142",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.5",
+ "Description": "Ensure that the --streaming-connection-idle-timeout argument is not set to 0",
+ "Checks": [
+ "kubelet_streaming_connection_timeout"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not disable timeouts on streaming connections.",
+ "RationaleStatement": "Setting idle timeouts ensures that you are protected against Denial-of-Service attacks, inactive connections and running out of ephemeral ports. **Note:** By default, `--streaming-connection-idle-timeout` is set to 4 hours which might be too high for your environment. Setting this as appropriate would additionally ensure that such streaming connections are timed out after serving legitimate use cases.",
+ "ImpactStatement": "Long-lived connections could be interrupted.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a value other than 0. If using command line arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_SYSTEM_PODS_ARGS` variable. ``` --streaming-connection-idle-timeout=5m ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the `--streaming-connection-idle-timeout` argument is not set to `0`. If the argument is not present, and there is a Kubelet config file specified by `--config`, check that it does not set `streamingConnectionIdleTimeout` to 0.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://github.com/kubernetes/kubernetes/pull/18552",
+ "DefaultValue": "By default, `--streaming-connection-idle-timeout` is set to 4 hours."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.6",
+ "Description": "Ensure that the --make-iptables-util-chains argument is set to true",
+ "Checks": [
+ "kubelet_manage_iptables"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Allow Kubelet to manage iptables.",
+ "RationaleStatement": "Kubelets can automatically manage the required changes to iptables based on how you choose your networking options for the pods. It is recommended to let kubelets manage the changes to iptables. This ensures that the iptables configuration remains in sync with pods networking configuration. Manually configuring iptables with dynamic pod network configuration changes might hamper the communication between pods/containers and to the outside world. You might have iptables rules too restrictive or too open.",
+ "ImpactStatement": "Kubelet would manage the iptables on the system and keep it in sync. If you are using any other iptables management solution, then there might be some conflicts.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains: true`. If using command line arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and remove the `--make-iptables-util-chains` argument from the `KUBELET_SYSTEM_PODS_ARGS` variable. Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that if the `--make-iptables-util-chains` argument exists then it is set to `true`. If the `--make-iptables-util-chains` argument does not exist, and there is a Kubelet config file specified by `--config`, verify that the file does not set `makeIPTablesUtilChains` to `false`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/",
+ "DefaultValue": "By default, `--make-iptables-util-chains` argument is set to `true`."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.7",
+ "Description": "Ensure that the --hostname-override argument is not set",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not override node hostnames.",
+ "RationaleStatement": "Overriding hostnames could potentially break TLS setup between the kubelet and the apiserver. Additionally, with overridden hostnames, it becomes increasingly difficult to associate logs with a particular node and process them for security analytics. Hence, you should setup your kubelet nodes with resolvable FQDNs and avoid overriding the hostnames with IPs.",
+ "ImpactStatement": "Some cloud providers may require this flag to ensure that hostname matches names issued by the cloud provider. In these environments, this recommendation should not apply.",
+ "RemediationProcedure": "Edit the kubelet service file `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf` on each worker node and remove the `--hostname-override` argument from the `KUBELET_SYSTEM_PODS_ARGS` variable. Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that `--hostname-override` argument does not exist. **Note** This setting is not configurable via the Kubelet config file.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://github.com/kubernetes/kubernetes/issues/22063",
+ "DefaultValue": "By default, `--hostname-override` argument is not set."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.8",
+ "Description": "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture",
+ "Checks": [
+ "kubelet_event_record_qps"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Security relevant information should be captured. The eventRecordQPS on the Kubelet configuration can be used to limit the rate at which events are gathered and sets the maximum event creations per second. Setting this too low could result in relevant events not being logged, however the unlimited setting of `0` could result in a denial of service on the kubelet.",
+ "RationaleStatement": "It is important to capture all events and not restrict event creation. Events are an important source of security information and analytics that ensure that your environment is consistently monitored using the event data.",
+ "ImpactStatement": "Setting this parameter to `0` could result in a denial of service condition due to excessive events being created. The cluster's event processing and storage systems should be scaled to handle expected event loads.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `eventRecordQPS:` to an appropriate level. If using command line arguments, edit the kubelet service file `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf` on each worker node and set the below parameter in `KUBELET_ARGS` variable. Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` sudo grep eventRecordQPS /etc/systemd/system/kubelet.service.d/10-kubeadm.conf ``` or If using command line arguments, kubelet service file is located /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf ``` sudo grep eventRecordQPS /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf ``` Review the value set for the argument and determine whether this has been set to an appropriate level for the cluster. If the argument does not exist, check that there is a Kubelet config file specified by `--config` and review the value in this location. If using command line arguments",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/kubelet/:https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/kubeletconfig/v1beta1/types.go",
+ "DefaultValue": "By default, eventRecordQPS argument is set to `5`."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.9",
+ "Description": "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate",
+ "Checks": [
+ "kubelet_tls_cert_and_key"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Setup TLS connection on the Kubelets.",
+ "RationaleStatement": "The connections from the apiserver to the kubelet are used for fetching logs for pods, attaching (through kubectl) to running pods, and using the kubelet’s port-forwarding functionality. These connections terminate at the kubelet’s HTTPS endpoint. By default, the apiserver does not verify the kubelet’s serving certificate, which makes the connection subject to man-in-the-middle attacks, and unsafe to run over untrusted and/or public networks.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set tlsCertFile to the location of the certificate file to use to identify this Kubelet, and tlsPrivateKeyFile to the location of the corresponding private key file. If using command line arguments, edit the kubelet service file /etc/kubernetes/kubelet.conf on each worker node and set the below parameters in KUBELET_CERTIFICATE_ARGS variable. --tls-cert-file=<path/to/tls-certificate-file> --tls-private-key-file=<path/to/tls-key-file> Based on your system, restart the kubelet service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the --tls-cert-file and --tls-private-key-file arguments exist and they are set as appropriate. If these arguments are not present, check that there is a Kubelet config specified by --config and that it contains appropriate settings for tlsCertFile and tlsPrivateKeyFile.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "4.2.10",
+ "Description": "Ensure that the --rotate-certificates argument is not set to false",
+ "Checks": [
+ "kubelet_rotate_certificates"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable kubelet client certificate rotation.",
+ "RationaleStatement": "The `--rotate-certificates` setting causes the kubelet to rotate its client certificates by creating new CSRs as its existing credentials expire. This automated periodic rotation ensures that the there is no downtime due to expired certificates and thus addressing availability in the CIA security triad. **Note:** This recommendation only applies if you let kubelets get their certificates from the API server. In case your kubelet certificates come from an outside authority/tool (e.g. Vault) then you need to take care of rotation yourself. **Note:** This feature also require the `RotateKubeletClientCertificate` feature gate to be enabled (which is the default since Kubernetes v1.7)",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to add the line `rotateCertificates: true` or remove it altogether to use the default value. If using command line arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and remove `--rotate-certificates=false` argument from the `KUBELET_CERTIFICATE_ARGS` variable or set --rotate-certificates=true . Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that the `RotateKubeletServerCertificate` argument is not present, or is set to `true`. If the RotateKubeletServerCertificate argument is not present, verify that if there is a Kubelet config file specified by `--config`, that file does not contain `RotateKubeletServerCertificate: false`.",
+ "AdditionalInformation": "",
+ "References": "https://github.com/kubernetes/kubernetes/pull/41912:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/#kubelet-configuration:https://kubernetes.io/docs/imported/release/notes/:https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/",
+ "DefaultValue": "By default, kubelet client certificate rotation is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.11",
+ "Description": "Verify that the RotateKubeletServerCertificate argument is set to true",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Enable kubelet server certificate rotation.",
+ "RationaleStatement": "`RotateKubeletServerCertificate` causes the kubelet to both request a serving certificate after bootstrapping its client credentials and rotate the certificate as its existing credentials expire. This automated periodic rotation ensures that the there are no downtimes due to expired certificates and thus addressing availability in the CIA security triad. Note: This recommendation only applies if you let kubelets get their certificates from the API server. In case your kubelet certificates come from an outside authority/tool (e.g. Vault) then you need to take care of rotation yourself.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the below parameter in `KUBELET_CERTIFICATE_ARGS` variable. ``` --feature-gates=RotateKubeletServerCertificate=true ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "Ignore this check if serverTLSBootstrap is true in the kubelet config file or if the --rotate-server-certificates parameter is set on kubelet Run the following command on each node: ``` ps -ef | grep kubelet ``` Verify that `RotateKubeletServerCertificate` argument exists and is set to `true`.",
+ "AdditionalInformation": "",
+ "References": "https://github.com/kubernetes/kubernetes/pull/45059:https://kubernetes.io/docs/admin/kubelet-tls-bootstrapping/#kubelet-configuration",
+ "DefaultValue": "By default, kubelet server certificate rotation is enabled."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.12",
+ "Description": "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers",
+ "Checks": [
+ "kubelet_strong_ciphers_only"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the Kubelet is configured to only use strong cryptographic ciphers.",
+ "RationaleStatement": "TLS ciphers have had a number of known vulnerabilities and weaknesses, which can reduce the protection provided by them. By default Kubernetes supports a number of TLS ciphersuites including some that have security concerns, weakening the protection provided.",
+ "ImpactStatement": "Kubelet clients that cannot support modern cryptographic ciphers will not be able to make connections to the Kubelet API.",
+ "RemediationProcedure": "If using a Kubelet config file, edit the file to set `tlsCipherSuites:` to `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256` or to a subset of these values. If using executable arguments, edit the kubelet service file `/etc/kubernetes/kubelet.conf` on each worker node and set the `--tls-cipher-suites` parameter as follows, or to a subset of these values. ``` --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 ``` Based on your system, restart the `kubelet` service. For example: ``` systemctl daemon-reload systemctl restart kubelet.service ```",
+ "AuditProcedure": "The set of cryptographic ciphers currently considered secure is the following: - `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256` - `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256` - `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305` - `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384` - `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305` - `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384` - `TLS_RSA_WITH_AES_256_GCM_SHA384` - `TLS_RSA_WITH_AES_128_GCM_SHA256` Run the following command on each node: ``` ps -ef | grep kubelet ``` If the `--tls-cipher-suites` argument is present, ensure it only contains values included in this set. If it is not present check that there is a Kubelet config file specified by `--config`, and that file sets `tlsCipherSuites:` to only include values from this set.",
+ "AdditionalInformation": "The list chosen above should be fine for modern clients. It's essentially the list from the Mozilla Modern cipher option with the ciphersuites supporting CBC mode removed, as CBC has traditionally had a lot of issues",
+ "References": "",
+ "DefaultValue": "By default the Kubernetes API server supports a wide range of TLS ciphers"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
+ ]
+ },
+ {
+ "Id": "4.2.13",
+ "Description": "Ensure that a limit is set on pod PIDs",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the Kubelet sets limits on the number of PIDs that can be created by pods running on the node.",
+ "RationaleStatement": "By default pods running in a cluster can consume any number of PIDs, potentially exhausting the resources available on the node. Setting an appropriate limit reduces the risk of a denial of service attack on cluster nodes.",
+ "ImpactStatement": "Setting this value will restrict the number of processes per pod. If this limit is lower than the number of PIDs required by a pod it will not operate.",
+ "RemediationProcedure": "Decide on an appropriate level for this parameter and set it, either via the `--pod-max-pids` command line parameter or the `PodPidsLimit` configuration file setting.",
+ "AuditProcedure": "Review the Kubelet's start-up parameters for the value of `--pod-max-pids`, and check the Kubelet configuration file for the `PodPidsLimit` . If neither of these values is set, then there is no limit in place.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits",
+ "DefaultValue": "By default the number of PIDs is not limited."
+ }
+ ]
+ },
+ {
+ "Id": "4.2.14",
+ "Description": "Ensure that the --seccomp-default parameter is set to true",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.2 Kubelet",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensure that the Kubelet enforces the use of the RuntimeDefault seccomp profile",
+ "RationaleStatement": "By default, Kubernetes disables the seccomp profile which ships with most container runtimes. Setting this parameter will ensure workloads running on the node are protected by the runtime's seccomp profile.",
+ "ImpactStatement": "Setting this will remove some rights from pods running on the node.",
+ "RemediationProcedure": "Set the parameter, either via the `--seccomp-default` command line parameter or the `seccompDefault` configuration file setting.",
+ "AuditProcedure": "Review the Kubelet's start-up parameters for the value of `--seccomp-default`, and check the Kubelet configuration file for the `seccompDefault` . If neither of these values is set, then the seccomp profile is not in use.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tutorials/security/seccomp/#enable-the-use-of-runtimedefault-as-the-default-seccomp-profile-for-all-workloads",
+ "DefaultValue": "By default the seccomp profile is not enabled."
+ }
+ ]
+ },
+ {
+ "Id": "4.3.1",
+ "Description": "Ensure that the kube-proxy metrics service is bound to localhost",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Worker Nodes",
+ "SubSection": "4.3 kube-proxy",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not bind the kube-proxy metrics port to non-loopback addresses.",
+ "RationaleStatement": "kube-proxy has two APIs which provided access to information about the service and can be bound to network ports. The metrics API service includes endpoints (`/metrics` and `/configz`) which disclose information about the configuration and operation of kube-proxy. These endpoints should not be exposed to untrusted networks as they do not support encryption or authentication to restrict access to the data they provide.",
+ "ImpactStatement": "3rd party services which try to access metrics or configuration information related to kube-proxy will require access to the localhost interface of the node.",
+ "RemediationProcedure": "Modify or remove any values which bind the metrics service to a non-localhost address",
+ "AuditProcedure": "review the start-up flags provided to kube proxy Run the following command on each node: ``` ps -ef | grep -i kube-proxy ``` Ensure that the `--metrics-bind-address` parameter is not set to a value other than 127.0.0.1. From the output of this command gather the location specified in the `--config` parameter. Review any file stored at that location and ensure that it does not specify a value other than 127.0.0.1 for `metricsBindAddress`.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/",
+ "DefaultValue": "The default value is `127.0.0.1:10249`"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.1",
+ "Description": "Ensure that the cluster-admin role is only used where required",
+ "Checks": [
+ "rbac_cluster_admin_usage"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The RBAC role `cluster-admin` provides wide-ranging powers over the environment and should be used only where and when needed.",
+ "RationaleStatement": "Kubernetes provides a set of default roles where RBAC is used. Some of these roles such as `cluster-admin` provide wide-ranging privileges which should only be applied where absolutely necessary. Roles such as `cluster-admin` allow super-user access to perform any action on any resource. When used in a `ClusterRoleBinding`, it gives full control over every resource in the cluster and in all namespaces. When used in a `RoleBinding`, it gives full control over every resource in the rolebinding's namespace, including the namespace itself.",
+ "ImpactStatement": "Care should be taken before removing any `clusterrolebindings` from the environment to ensure they were not required for operation of the cluster. Specifically, modifications should not be made to `clusterrolebindings` with the `system:` prefix as they are required for the operation of system components.",
+ "RemediationProcedure": "Identify all clusterrolebindings to the cluster-admin role. Check if they are used and if they need this role or if they could use a role with fewer privileges. Where possible, first bind users to a lower privileged role and then remove the clusterrolebinding to the cluster-admin role : ``` kubectl delete clusterrolebinding [name] ```",
+ "AuditProcedure": "Obtain a list of the principals who have access to the `cluster-admin` role by reviewing the `clusterrolebinding` output for each role binding that has access to the `cluster-admin` role. ``` kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name ``` Review each principal listed and ensure that `cluster-admin` privilege is required for it.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/authorization/rbac/#user-facing-roles",
+ "DefaultValue": "By default a single `clusterrolebinding` called `cluster-admin` is provided with the `system:masters` group as its principal."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2",
+ "Description": "Minimize access to secrets",
+ "Checks": [
+ "rbac_minimize_secret_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The Kubernetes API stores secrets, which may be service account tokens for the Kubernetes API or credentials used by workloads in the cluster. Access to these secrets should be restricted to the smallest possible group of users to reduce the risk of privilege escalation.",
+ "RationaleStatement": "Inappropriate access to secrets stored within the Kubernetes cluster can allow for an attacker to gain additional access to the Kubernetes cluster or external resources whose credentials are stored as secrets.",
+ "ImpactStatement": "Care should be taken not to remove access to secrets to system components which require this for their operation",
+ "RemediationProcedure": "Where possible, restrict access to secret objects in the cluster by removing get, list, and watch permissions.",
+ "AuditProcedure": "Review the users who have `get`, `list`, or `watch` access to `secrets` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default in a kubeadm cluster the following list of principals have `get` privileges on `secret` objects ``` CLUSTERROLEBINDING SUBJECT TYPE SA-NAMESPACE cluster-admin system:masters Group system:controller:clusterrole-aggregation-controller clusterrole-aggregation-controller ServiceAccount kube-system system:controller:expand-controller expand-controller ServiceAccount kube-system system:controller:generic-garbage-collector generic-garbage-collector ServiceAccount kube-system system:controller:namespace-controller namespace-controller ServiceAccount kube-system system:controller:persistent-volume-binder persistent-volume-binder ServiceAccount kube-system system:kube-controller-manager system:kube-controller-manager User ```"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3",
+ "Description": "Minimize wildcard use in Roles and ClusterRoles",
+ "Checks": [
+ "rbac_minimize_wildcard_use_roles"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes Roles and ClusterRoles provide access to resources based on sets of objects and actions that can be taken on those objects. It is possible to set either of these to be the wildcard * which matches all items. Use of wildcards is not optimal from a security perspective as it may allow for inadvertent access to be granted when new resources are added to the Kubernetes API either as CRDs or in later versions of the product.",
+ "RationaleStatement": "The principle of least privilege recommends that users are provided only the access required for their role and nothing more. The use of wildcard rights grants is likely to provide excessive rights to the Kubernetes API.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible replace any use of wildcards in ClusterRoles and Roles with specific objects or actions.",
+ "AuditProcedure": "Retrieve the roles defined across each namespaces in the cluster and review for wildcards ``` kubectl get roles --all-namespaces -o yaml ``` Retrieve the cluster roles defined in the cluster and review for wildcards ``` kubectl get clusterroles -o yaml ```",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4",
+ "Description": "Minimize access to create pods",
+ "Checks": [
+ "rbac_minimize_pod_creation_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The ability to create pods in a namespace can provide a number of opportunities for privilege escalation, such as assigning privileged service accounts to these pods or mounting hostPaths with access to sensitive data (unless Pod Security Policies are implemented to restrict this access) As such, access to create new pods should be restricted to the smallest possible group of users.",
+ "RationaleStatement": "The ability to create pods in a cluster opens up possibilities for privilege escalation and should be restricted, where possible.",
+ "ImpactStatement": "Care should be taken not to remove access to pods to system components which require this for their operation",
+ "RemediationProcedure": "Where possible, remove `create` access to `pod` objects in the cluster.",
+ "AuditProcedure": "Review the users who have create access to pod objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default in a kubeadm cluster the following list of principals have `create` privileges on `pod` objects ``` CLUSTERROLEBINDING SUBJECT TYPE SA-NAMESPACE cluster-admin system:masters Group system:controller:clusterrole-aggregation-controller clusterrole-aggregation-controller ServiceAccount kube-system system:controller:daemon-set-controller daemon-set-controller ServiceAccount kube-system system:controller:job-controller job-controller ServiceAccount kube-system system:controller:persistent-volume-binder persistent-volume-binder ServiceAccount kube-system system:controller:replicaset-controller replicaset-controller ServiceAccount kube-system system:controller:replication-controller replication-controller ServiceAccount kube-system system:controller:statefulset-controller statefulset-controller ServiceAccount kube-system ```"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5",
+ "Description": "Ensure that default service accounts are not actively used.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The `default` service account should not be used to ensure that rights granted to applications can be more easily audited and reviewed.",
+ "RationaleStatement": "Kubernetes provides a default service account which is used by cluster workloads where no specific service account is assigned to the pod. Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account. The default service account should be configured to ensure that it does not automatically provide a service account token, and it must not have any non-default role bindings or custom role assignments",
+ "ImpactStatement": "All workloads which require access to the Kubernetes API will require an explicit service account to be created.",
+ "RemediationProcedure": "Create explicit service accounts wherever a Kubernetes workload requires specific access to the Kubernetes API server. Modify the configuration of each default service account to include this value ``` automountServiceAccountToken: false ```",
+ "AuditProcedure": "For each namespace in the cluster, review the rights assigned to the default service account and ensure that it has no roles or cluster roles bound to it apart from the defaults. Additionally ensure that the `automountServiceAccountToken: false` setting is in place for each default service account.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/",
+ "DefaultValue": "By default the `default` service account allows for its service account token to be mounted in pods in its namespace."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.6",
+ "Description": "Ensure that Service Account Tokens are only mounted where necessary",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Service accounts tokens should not be mounted in pods except where the workload running in the pod explicitly needs to communicate with the API server",
+ "RationaleStatement": "Mounting service account tokens inside pods can provide an avenue for privilege escalation attacks where an attacker is able to compromise a single pod in the cluster. Avoiding mounting these tokens removes this attack avenue.",
+ "ImpactStatement": "Pods mounted without service account tokens will not be able to communicate with the API server, except where the resource is available to unauthenticated principals.",
+ "RemediationProcedure": "Modify the definition of pods and service accounts which do not need to mount service account tokens to disable it.",
+ "AuditProcedure": "Review pod and service account objects in the cluster and ensure that the option below is set, unless the resource explicitly requires this access. ``` automountServiceAccountToken: false ```",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/",
+ "DefaultValue": "By default, all pods get a service account token mounted in them."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.7",
+ "Description": "Avoid use of system:masters group",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The special group `system:masters` should not be used to grant permissions to any user or service account, except where strictly necessary (e.g. bootstrapping access prior to RBAC being fully available)",
+ "RationaleStatement": "The `system:masters` group has unrestricted access to the Kubernetes API hard-coded into the API server source code. An authenticated user who is a member of this group cannot have their access reduced, even if all bindings and cluster role bindings which mention it, are removed. When combined with client certificate authentication, use of this group can allow for irrevocable cluster-admin level credentials to exist for a cluster.",
+ "ImpactStatement": "Once the RBAC system is operational in a cluster `system:masters` should not be specifically required, as ordinary bindings from principals to the `cluster-admin` cluster role can be made where unrestricted access is required.",
+ "RemediationProcedure": "Remove the `system:masters` group from all users in the cluster.",
+ "AuditProcedure": "Review a list of all credentials which have access to the cluster and ensure that the group `system:masters` is not used.",
+ "AdditionalInformation": "",
+ "References": "https://github.com/kubernetes/kubernetes/blob/master/pkg/registry/rbac/escalation_check.go#L38",
+ "DefaultValue": "By default some clusters will create a break glass client certificate which is a member of this group. Access to this client certificate should be carefully controlled and it should not be used for general cluster operations."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.8",
+ "Description": "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Cluster roles and roles with the impersonate, bind or escalate permissions should not be granted unless strictly required. Each of these permissions allow a particular subject to escalate their privileges beyond those explicitly granted by cluster administrators",
+ "RationaleStatement": "The impersonate privilege allows a subject to impersonate other users gaining their rights to the cluster. The bind privilege allows the subject to add a binding to a cluster role or role which escalates their effective permissions in the cluster. The escalate privilege allows a subject to modify cluster roles to which they are bound, increasing their rights to that level. Each of these permissions has the potential to allow for privilege escalation to cluster-admin level.",
+ "ImpactStatement": "There are some cases where these permissions are required for cluster service operation, and care should be taken before removing these permissions from system service accounts.",
+ "RemediationProcedure": "Where possible, remove the impersonate, bind, and escalate rights from subjects.",
+ "AuditProcedure": "Review the users who have access to cluster roles or roles which provide the impersonate, bind, or escalate privileges.",
+ "AdditionalInformation": "",
+ "References": "https://raesene.github.io/blog/2020/12/12/Escalating_Away/:https://raesene.github.io/blog/2021/01/16/Getting-Into-A-Bind-with-Kubernetes/",
+ "DefaultValue": "In a default kubeadm cluster, the system:masters group and clusterrole-aggregation-controller service account have access to the escalate privilege. The system:masters group also has access to bind and impersonate."
+ }
+ ]
+ },
+ {
+ "Id": "5.1.9",
+ "Description": "Minimize access to create persistent volumes",
+ "Checks": [
+ "rbac_minimize_pv_creation_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The ability to create persistent volumes in a cluster can provide an opportunity for privilege escalation, via the creation of `hostPath` volumes. As persistent volumes are not covered by Pod Security Admission, a user with access to create persistent volumes may be able to get access to sensitive files from the underlying host even where restrictive Pod Security Admission policies are in place.",
+ "RationaleStatement": "The ability to create persistent volumes in a cluster opens up possibilities for privilege escalation and should be restricted, where possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible, remove `create` access to `PersistentVolume` objects in the cluster.",
+ "AuditProcedure": "Review the users who have create access to `PersistentVolume` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/#persistent-volume-creation",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.10",
+ "Description": "Minimize access to the proxy sub-resource of nodes",
+ "Checks": [
+ "rbac_minimize_node_proxy_subresource_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Users with access to the `Proxy` sub-resource of `Node` objects automatically have permissions to use the kubelet API, which may allow for privilege escalation or bypass cluster security controls such as audit logs. The kubelet provides an API which includes rights to execute commands in any container running on the node. Access to this API is covered by permissions to the main Kubernetes API via the `node` object. The proxy sub-resource specifically allows wide ranging access to the kubelet API. Direct access to the kubelet API bypasses controls like audit logging (there is no audit log of kubelet API access) and admission control.",
+ "RationaleStatement": "The ability to use the `proxy` sub-resource of `node` objects opens up possibilities for privilege escalation and should be restricted, where possible.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible, remove access to the `proxy` sub-resource of `node` objects.",
+ "AuditProcedure": "Review the users who have access to the `proxy` sub-resource of `node` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/#access-to-proxy-subresource-of-nodes:https://kubernetes.io/docs/reference/access-authn-authz/kubelet-authn-authz/#kubelet-authorization",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.11",
+ "Description": "Minimize access to the approval sub-resource of certificatesigningrequests objects",
+ "Checks": [
+ "rbac_minimize_csr_approval_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Users with access to the update the `approval` sub-resource of `CertificateSigningRequests` objects can approve new client certificates for the Kubernetes API effectively allowing them to create new high-privileged user accounts. This can allow for privilege escalation to full cluster administrator, depending on users configured in the cluster",
+ "RationaleStatement": "The ability to update certificate signing requests should be limited.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible, remove access to the `approval` sub-resource of `CertificateSigningRequests` objects.",
+ "AuditProcedure": "Review the users who have access to update the `approval` sub-resource of `CertificateSigningRequests` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/#csrs-and-certificate-issuing",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.12",
+ "Description": "Minimize access to webhook configuration objects",
+ "Checks": [
+ "rbac_minimize_webhook_config_access"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Users with rights to create/modify/delete `validatingwebhookconfigurations` or `mutatingwebhookconfigurations` can control webhooks that can read any object admitted to the cluster, and in the case of mutating webhooks, also mutate admitted objects. This could allow for privilege escalation or disruption of the operation of the cluster.",
+ "RationaleStatement": "The ability to manage webhook configuration should be limited",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible, remove access to the `validatingwebhookconfigurations` or `mutatingwebhookconfigurations` objects",
+ "AuditProcedure": "Review the users who have access to `validatingwebhookconfigurations` or `mutatingwebhookconfigurations` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/#control-admission-webhooks",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.1.13",
+ "Description": "Minimize access to the service account token creation",
+ "Checks": [
+ "rbac_minimize_service_account_token_creation"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.1 RBAC and Service Accounts",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Users with rights to create new service account tokens at a cluster level, can create long-lived privileged credentials in the cluster. This could allow for privilege escalation and persistent access to the cluster, even if the users account has been revoked.",
+ "RationaleStatement": "The ability to create service account tokens should be limited.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "Where possible, remove access to the `token` sub-resource of `serviceaccount` objects.",
+ "AuditProcedure": "Review the users who have access to create the `token` sub-resource of `serviceaccount` objects in the Kubernetes API.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/#token-request",
+ "DefaultValue": ""
+ }
+ ]
+ },
+ {
+ "Id": "5.2.1",
+ "Description": "Ensure that the cluster has at least one active policy control mechanism in place",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Every Kubernetes cluster should have at least one policy control mechanism in place to enforce the other requirements in this section. This could be the in-built Pod Security Admission controller, or a third party policy control system.",
+ "RationaleStatement": "Without an active policy control mechanism, it is not possible to limit the use of containers with access to underlying cluster nodes, via mechanisms like privileged containers, or the use of hostPath volume mounts.",
+ "ImpactStatement": "Where policy control systems are in place, there is a risk that workloads required for the operation of the cluster may be stopped from running. Care is required when implementing admission control policies to ensure that this does not occur.",
+ "RemediationProcedure": "Ensure that either Pod Security Admission or an external policy control system is in place for every namespace which contains user workloads.",
+ "AuditProcedure": "Review the workloads deployed to the cluster to understand if Pod Security Admission or external admission control systems are in place.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-admission",
+ "DefaultValue": "By default, Pod Security Admission is enabled but no policies are in place."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2",
+ "Description": "Minimize the admission of privileged containers",
+ "Checks": [
+ "core_minimize_privileged_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run with the `securityContext.privileged` flag set to `true`.",
+ "RationaleStatement": "Privileged containers have access to all Linux Kernel capabilities and devices. A container running with full privileges can do almost everything that the host can do. This flag exists to allow special use-cases, like manipulating the network stack and accessing devices. There should be at least one admission control policy defined which does not permit privileged containers. If you need to run privileged containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `spec.containers[].securityContext.privileged: true`, `spec.initContainers[].securityContext.privileged: true` and `spec.ephemeralContainers[].securityContext.privileged: true` will not be permitted.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of privileged containers.",
+ "AuditProcedure": "Run the following command: `kubectl get pods -A -o=jsonpath='{range .items[*]}{@.metadata.name}: {@..securityContext}{end}'`It will produce an inventory of all the privileged use on the cluster, if any (please, refer to a sample below). Further grepping can be done to automate each specific violation detection. calico-kube-controllers-57b57c56f-jtmk4: {} << No Elevated Privileges calico-node-c4xv4: {} {privileged:true} {privileged:true} {privileged:true} {privileged:true} << Violates 5.2.2 dashboard-metrics-scraper-7bc864c59-2m2xw: {seccompProfile:{type:RuntimeDefault}} {allowPrivilegeEscalation:false,readOnlyRootFilesystem:true,runAsGroup:2001,runAsUser:1001}",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of privileged containers."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3",
+ "Description": "Minimize the admission of containers wishing to share the host process ID namespace",
+ "Checks": [
+ "core_minimize_hostPID_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run with the `hostPID` flag set to true.",
+ "RationaleStatement": "A container running in the host's PID namespace can inspect processes running outside the container. If the container also has access to ptrace capabilities this can be used to escalate privileges outside of the container. There should be at least one admission control policy defined which does not permit containers to share the host PID namespace. If you need to run containers which require hostPID, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `spec.hostPID: true` will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Configure the Admission Controller to restrict the admission of `hostPID` containers.",
+ "AuditProcedure": "Fetch hostPID from each pod with `get pods -A -o=jsonpath='{range .items[*]}{@.metadata.name}: {@.spec.hostPID}{end}'`",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of `hostPID` containers."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4",
+ "Description": "Minimize the admission of containers wishing to share the host IPC namespace",
+ "Checks": [
+ "core_minimize_hostIPC_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run with the `hostIPC` flag set to true.",
+ "RationaleStatement": "A container running in the host's IPC namespace can use IPC to interact with processes outside the container. There should be at least one admission control policy defined which does not permit containers to share the host IPC namespace. If you need to run containers which require hostIPC, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `spec.hostIPC: true` will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of `hostIPC` containers.",
+ "AuditProcedure": "Fetch hostIPC from each pod with `get pods -A -o=jsonpath='{range .items[*]}{@.metadata.name}: {@.spec.hostIPC}{end}'`",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of `hostIPC` containers."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.5",
+ "Description": "Minimize the admission of containers wishing to share the host network namespace",
+ "Checks": [
+ "core_minimize_hostNetwork_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run with the `hostNetwork` flag set to true.",
+ "RationaleStatement": "A container running in the host's network namespace could access the local loopback device, and could access network traffic to and from other pods. There should be at least one admission control policy defined which does not permit containers to share the host network namespace. If you need to run containers which require access to the host's network namespaces, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `spec.hostNetwork: true` will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of `hostNetwork` containers.",
+ "AuditProcedure": "Fetch hostNetwork from each pod with `get pods -A -o=jsonpath='{range .items[*]}{@.metadata.name}: {@.spec.hostNetwork}{end}'`",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of `hostNetwork` containers."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.6",
+ "Description": "Minimize the admission of containers with allowPrivilegeEscalation",
+ "Checks": [
+ "core_minimize_allowPrivilegeEscalation_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run with the `allowPrivilegeEscalation` flag set to true. Allowing this right can lead to a process running a container getting more rights than it started with. It's important to note that these rights are still constrained by the overall container sandbox, and this setting does not relate to the use of privileged containers.",
+ "RationaleStatement": "A container running with the `allowPrivilegeEscalation` flag set to `true` may have processes that can gain more privileges than their parent. There should be at least one admission control policy defined which does not permit containers to allow privilege escalation. The option exists (and is defaulted to true) to permit setuid binaries to run. If you have need to run containers which use setuid binaries or require privilege escalation, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `securityContext: allowPrivilegeEscalation: true` will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of containers with `securityContext: allowPrivilegeEscalation: true`",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that each policy disallows the admission of containers which allow privilege escalation. To fetch a list of pods which `allowPrivilegeEscalation` run this command: `get pods -A -o=jsonpath='{range .items[*]}{@.metadata.name}: {@..securityContext}{end}'`",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on contained process ability to escalate privileges, within the context of the container."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.7",
+ "Description": "Minimize the admission of root containers",
+ "Checks": [
+ "core_minimize_root_containers_admission"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers to be run as the root user.",
+ "RationaleStatement": "Containers may run as any Linux user. Containers which run as the root user, whilst constrained by Container Runtime security features still have a escalated likelihood of container breakout. Ideally, all containers should run as a defined non-UID 0 user. There should be at least one admission control policy defined which does not permit root containers. If you need to run root containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods with containers which run as the root user will not be permitted.",
+ "RemediationProcedure": "Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot` or `MustRunAs` with the range of UIDs not including 0, is set.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that each policy restricts the use of root containers by setting `MustRunAsNonRoot` or `MustRunAs` with the range of UIDs not including 0.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the use of root containers and if a User is not specified in the image, the container will run as root."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.8",
+ "Description": "Minimize the admission of containers with the NET_RAW capability",
+ "Checks": [
+ "core_minimize_net_raw_capability_admission"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers with the potentially dangerous NET_RAW capability.",
+ "RationaleStatement": "Containers run with a default set of capabilities as assigned by the Container Runtime. By default this can include potentially dangerous capabilities. With Docker as the container runtime the NET_RAW capability is enabled which may be misused by malicious containers. Ideally, all containers should drop this capability. There should be at least one admission control policy defined which does not permit containers with the NET_RAW capability. If you need to run containers with this capability, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods with containers which run with the NET_RAW capability will not be permitted.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of containers with the `NET_RAW` capability.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that at least one policy disallows the admission of containers with the `NET_RAW` capability.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/:https://www.nccgroup.trust/uk/our-research/abusing-privileged-and-unprivileged-linux-containers/",
+ "DefaultValue": "By default, there are no restrictions on the creation of containers with the `NET_RAW` capability."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.9",
+ "Description": "Minimize the admission of containers with capabilities assigned",
+ "Checks": [
+ "core_minimize_containers_capabilities_assigned"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers with capabilities",
+ "RationaleStatement": "Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities are parts of the rights generally granted on a Linux system to the root user. In many cases applications running in containers do not require any capabilities to operate, so from the perspective of the principal of least privilege use of capabilities should be minimized.",
+ "ImpactStatement": "Pods with containers require capabilities to operate will not be permitted.",
+ "RemediationProcedure": "Review the use of capabilities in applications running on your cluster. Where a namespace contains applications which do not require any Linux capabilities to operate consider adding a policy which forbids the admission of containers which do not drop all capabilities.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that at least one policy requires that capabilities are dropped by all containers.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/:https://www.nccgroup.trust/uk/our-research/abusing-privileged-and-unprivileged-linux-containers/",
+ "DefaultValue": "By default, there are no restrictions on the creation of containers with additional capabilities"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.10",
+ "Description": "Minimize the admission of Windows HostProcess Containers",
+ "Checks": [
+ "core_minimize_admission_windows_hostprocess_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit Windows containers to be run with the `hostProcess` flag set to true.",
+ "RationaleStatement": "A Windows container making use of the `hostProcess` flag can interact with the underlying Windows cluster node. As per the Kubernetes documentation, this provides privileged access to the Windows node. Where Windows containers are used inside a Kubernetes cluster, there should be at least one admission control policy which does not permit `hostProcess` Windows containers. If you need to run Windows containers which require `hostProcess`, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `securityContext.windowsOptions.hostProcess: true` will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of `hostProcess` containers.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that each policy disallows the admission of `hostProcess` containers",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/:https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of `hostProcess` containers."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.11",
+ "Description": "Minimize the admission of HostPath volumes",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally admit containers which make use of `hostPath` volumes.",
+ "RationaleStatement": "A container which mounts a `hostPath` volume as part of its specification will have access to the filesystem of the underlying cluster node. The use of `hostPath` volumes may allow containers access to privileged areas of the node filesystem. There should be at least one admission control policy defined which does not permit containers to mount `hostPath` volumes. If you need to run containers which require `hostPath` volumes, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined which make use of `hostPath` volumes will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of containers which use `hostPath` volumes.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that each policy disallows the admission of containers with `hostPath` volumes.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the creation of `hostPath` volumes."
+ }
+ ]
+ },
+ {
+ "Id": "5.2.12",
+ "Description": "Minimize the admission of containers which use HostPorts",
+ "Checks": [
+ "core_minimize_admission_hostport_containers"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.2 Pod Security Standards",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Do not generally permit containers which require the use of HostPorts.",
+ "RationaleStatement": "Host ports connect containers directly to the host's network. This can bypass controls such as network policy. There should be at least one admission control policy defined which does not permit containers which require the use of HostPorts. If you need to run containers which require HostPorts, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+ "ImpactStatement": "Pods defined with `hostPort` settings in either the container, initContainer or ephemeralContainer sections will not be permitted unless they are run under a specific policy.",
+ "RemediationProcedure": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of containers which use `hostPort` sections.",
+ "AuditProcedure": "List the policies in use for each namespace in the cluster, ensure that each policy disallows the admission of containers which have `hostPort` sections.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/security/pod-security-standards/",
+ "DefaultValue": "By default, there are no restrictions on the use of HostPorts."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.1",
+ "Description": "Ensure that the CNI in use supports Network Policies",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.3 Network Policies and CNI",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "There are a variety of CNI plugins available for Kubernetes. If the CNI in use does not support Network Policies it may not be possible to effectively restrict traffic in the cluster.",
+ "RationaleStatement": "Kubernetes network policies are enforced by the CNI plugin in use. As such it is important to ensure that the CNI plugin supports both Ingress and Egress network policies.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "If the CNI plugin in use does not support network policies, consideration should be given to making use of a different plugin, or finding an alternate mechanism for restricting traffic in the Kubernetes cluster.",
+ "AuditProcedure": "Review the documentation of CNI plugin in use by the cluster, and confirm that it supports Ingress and Egress network policies.",
+ "AdditionalInformation": "One example here is Flannel (https://github.com/coreos/flannel) which does not support Network policy unless Calico is also in use.",
+ "References": "https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/",
+ "DefaultValue": "This will depend on the CNI plugin in use."
+ }
+ ]
+ },
+ {
+ "Id": "5.3.2",
+ "Description": "Ensure that all Namespaces have Network Policies defined",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.3 Network Policies and CNI",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Use network policies to isolate traffic in your cluster network.",
+ "RationaleStatement": "Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints. Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace.",
+ "ImpactStatement": "Once network policies are in use within a given namespace, traffic not explicitly allowed by a network policy will be denied. As such it is important to ensure that, when introducing network policies, legitimate traffic is not blocked.",
+ "RemediationProcedure": "Follow the documentation and create `NetworkPolicy` objects as you need them.",
+ "AuditProcedure": "Run the below command and review the `NetworkPolicy` objects created in the cluster. ``` kubectl get networkpolicy --all-namespaces ``` Ensure that each namespace defined in the cluster has at least one Network Policy.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/services-networking/networkpolicies/:https://octetz.com/posts/k8s-network-policy-apis:https://kubernetes.io/docs/tasks/configure-pod-container/declare-network-policy/",
+ "DefaultValue": "By default, network policies are not created."
+ }
+ ]
+ },
+ {
+ "Id": "5.4.1",
+ "Description": "Prefer using secrets as files over secrets as environment variables",
+ "Checks": [
+ "core_no_secrets_envs"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.4 Secrets Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes supports mounting secrets as data volumes or as environment variables. Minimize the use of environment variable secrets.",
+ "RationaleStatement": "It is reasonably common for application code to log out its environment (particularly in the event of an error). This will include any secret values passed in as environment variables, so secrets can easily be exposed to any user or entity who has access to the logs.",
+ "ImpactStatement": "Application code which expects to read secrets in the form of environment variables would need modification",
+ "RemediationProcedure": "If possible, rewrite application code to read secrets from mounted secret files, rather than from environment variables.",
+ "AuditProcedure": "Run the following command to find references to objects which use environment variables defined from secrets. ``` kubectl get all -o jsonpath='{range .items[?(@..secretKeyRef)]}{.kind}{@.metadata.name}{end}' -A ```",
+ "AdditionalInformation": "Mounting secrets as volumes has the additional benefit that secret values can be updated without restarting the pod",
+ "References": "https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets",
+ "DefaultValue": "By default, secrets are not defined"
+ }
+ ]
+ },
+ {
+ "Id": "5.4.2",
+ "Description": "Consider external secret storage",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.4 Secrets Management",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Consider the use of an external secrets storage and management system, instead of using Kubernetes Secrets directly, if you have more complex secret management needs. Ensure the solution requires authentication to access secrets, has auditing of access to and use of secrets, and encrypts secrets. Some solutions also make it easier to rotate secrets.",
+ "RationaleStatement": "Kubernetes supports secrets as first-class objects, but care needs to be taken to ensure that access to secrets is carefully limited. Using an external secrets provider can ease the management of access to secrets, especially where secrests are used across both Kubernetes and non-Kubernetes environments.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Refer to the secrets management options offered by your cloud provider or a third-party secrets management solution.",
+ "AuditProcedure": "Review your secrets management implementation.",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "By default, no external secret management is configured."
+ }
+ ]
+ },
+ {
+ "Id": "5.5.1",
+ "Description": "Configure Image Provenance using ImagePolicyWebhook admission controller",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.5 Extensible Admission Control",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Configure Image Provenance for your deployment.",
+ "RationaleStatement": "Kubernetes supports plugging in provenance rules to accept or reject the images in your deployments. You could configure such rules to ensure that only approved images are deployed in the cluster.",
+ "ImpactStatement": "You need to regularly maintain your provenance configuration based on container image updates.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and setup image provenance.",
+ "AuditProcedure": "Review the pod definitions in your cluster and verify that image provenance is configured as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/admin/admission-controllers/#imagepolicywebhook:https://github.com/kubernetes/community/blob/master/contributors/design-proposals/image-provenance.md:https://hub.docker.com/r/dnurmi/anchore-toolbox/:https://github.com/kubernetes/kubernetes/issues/22888",
+ "DefaultValue": "By default, image provenance is not set."
+ }
+ ]
+ },
+ {
+ "Id": "5.6.1",
+ "Description": "Create administrative boundaries between resources using namespaces",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.6 General Policies",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Use namespaces to isolate your Kubernetes objects.",
+ "RationaleStatement": "Limiting the scope of user permissions can reduce the impact of mistakes or malicious activities. A Kubernetes namespace allows you to partition created resources into logically named groups. Resources created in one namespace can be hidden from other namespaces. By default, each resource created by a user in Kubernetes cluster runs in a default namespace, called `default`. You can create additional namespaces and attach resources and users to them. You can use Kubernetes Authorization plugins to create policies that segregate access to namespace resources between different users.",
+ "ImpactStatement": "You need to switch between namespaces for administration.",
+ "RemediationProcedure": "Follow the documentation and create namespaces for objects in your deployment as you need them.",
+ "AuditProcedure": "Run the below command and review the namespaces created in the cluster. ``` kubectl get namespaces ``` Ensure that these namespaces are the ones you need and are adequately administered as per your requirements.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#viewing-namespaces:http://blog.kubernetes.io/2016/08/security-best-practices-kubernetes-deployment.html:https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/589-efficient-node-heartbeats",
+ "DefaultValue": "By default, Kubernetes starts with 4 initial namespaces: 1. `default` - The default namespace for objects with no other namespace 1. `kube-system` - The namespace for objects created by the Kubernetes system 1. `kube-node-lease` - Namespace used for node heartbeats 1. `kube-public` - Namespace used for public information in a cluster"
+ }
+ ]
+ },
+ {
+ "Id": "5.6.2",
+ "Description": "Ensure that the seccomp profile is set to docker/default in your pod definitions",
+ "Checks": [
+ "core_seccomp_profile_docker_default"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.6 General Policies",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Enable `docker/default` seccomp profile in your pod definitions.",
+ "RationaleStatement": "Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in the cluster. Kubernetes disables seccomp profiles by default for historical reasons. You should enable it to ensure that the workloads have restricted actions available within the container.",
+ "ImpactStatement": "If the `docker/default` seccomp profile is too restrictive for you, you would have to create/manage your own seccomp profiles.",
+ "RemediationProcedure": "Use security context to enable the `docker/default` seccomp profile in your pod definitions. An example is as below: ``` securityContext: seccompProfile: type: RuntimeDefault ```",
+ "AuditProcedure": "Review the pod definitions in your cluster. It should create a line as below: ``` securityContext: seccompProfile: type: RuntimeDefault ```",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/tutorials/clusters/seccomp/:https://docs.docker.com/engine/security/seccomp/",
+ "DefaultValue": "By default, seccomp profile is set to `unconfined` which means that no seccomp profiles are enabled."
+ }
+ ]
+ },
+ {
+ "Id": "5.6.3",
+ "Description": "Apply Security Context to Your Pods and Containers",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.6 General Policies",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Apply Security Context to Your Pods and Containers",
+ "RationaleStatement": "A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. A security context is a property defined in the deployment yaml. It controls the security parameters that will be assigned to the pod/container/volume. There are two levels of security context: pod level security context, and container level security context.",
+ "ImpactStatement": "If you incorrectly apply security contexts, you may have trouble running the pods.",
+ "RemediationProcedure": "Follow the Kubernetes documentation and apply security contexts to your pods. For a suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker Containers.",
+ "AuditProcedure": "Review the pod definitions in your cluster and verify that you have security contexts defined as appropriate.",
+ "AdditionalInformation": "",
+ "References": "https://kubernetes.io/docs/concepts/policy/security-context/:https://learn.cisecurity.org/benchmarks",
+ "DefaultValue": "By default, no security contexts are automatically applied to pods."
+ }
+ ]
+ },
+ {
+ "Id": "5.6.4",
+ "Description": "The default namespace should not be used",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Policies",
+ "SubSection": "5.6 General Policies",
+ "Profile": "Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.",
+ "RationaleStatement": "Resources in a Kubernetes cluster should be segregated by namespace, to allow for security controls to be applied at that level and to make it easier to manage resources.",
+ "ImpactStatement": "None",
+ "RemediationProcedure": "Ensure that namespaces are created to allow for appropriate segregation of Kubernetes resources and that all new resources are created in a specific namespace.",
+ "AuditProcedure": "Run this command to list objects in default namespace ``` kubectl get $(kubectl api-resources --verbs=list --namespaced=true -o name | paste -sd, -) --ignore-not-found -n default ``` The only entries there should be system managed resources such as the `kubernetes` service",
+ "AdditionalInformation": "",
+ "References": "",
+ "DefaultValue": "Unless a namespace is specific on object creation, the `default` namespace will be used"
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/kubernetes/pci_4.0_kubernetes.json b/prowler/compliance/kubernetes/pci_4.0_kubernetes.json
index 0b301a0645..38d9557d5f 100644
--- a/prowler/compliance/kubernetes/pci_4.0_kubernetes.json
+++ b/prowler/compliance/kubernetes/pci_4.0_kubernetes.json
@@ -8268,6 +8268,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "10.5.1: Audit log history is retained and available for analysis.",
@@ -10054,6 +10062,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.1.3: Sensitive authentication data (SAD) is not stored after authorization.",
@@ -10250,6 +10266,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "3.3.3: Sensitive authentication data (SAD) is not stored after authorization.",
@@ -13004,6 +13028,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 365
+ }
+ ],
"Attributes": [
{
"Section": "5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored.",
diff --git a/prowler/compliance/kubernetes/prowler_threatscore_kubernetes.json b/prowler/compliance/kubernetes/prowler_threatscore_kubernetes.json
index 11ffe42485..58ef7c6ddb 100644
--- a/prowler/compliance/kubernetes/prowler_threatscore_kubernetes.json
+++ b/prowler/compliance/kubernetes/prowler_threatscore_kubernetes.json
@@ -1083,6 +1083,23 @@
"LevelOfRisk": 4,
"Weight": 100
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "kubelet_strong_ciphers_only",
+ "ConfigKey": "kubelet_strong_ciphers",
+ "Operator": "subset",
+ "Value": [
+ "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
+ "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
+ "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_256_GCM_SHA384",
+ "TLS_RSA_WITH_AES_128_GCM_SHA256"
+ ]
+ }
]
},
{
@@ -1199,6 +1216,14 @@
"Checks": [
"apiserver_audit_log_maxage_set"
],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxage_set",
+ "ConfigKey": "audit_log_maxage",
+ "Operator": "gte",
+ "Value": 30
+ }
+ ],
"Attributes": [
{
"Title": "API Server audit log retention configured",
@@ -1227,6 +1252,14 @@
"LevelOfRisk": 3,
"Weight": 10
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxbackup_set",
+ "ConfigKey": "audit_log_maxbackup",
+ "Operator": "gte",
+ "Value": 10
+ }
]
},
{
@@ -1245,6 +1278,14 @@
"LevelOfRisk": 2,
"Weight": 8
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "apiserver_audit_log_maxsize_set",
+ "ConfigKey": "audit_log_maxsize",
+ "Operator": "gte",
+ "Value": 100
+ }
]
},
{
diff --git a/tests/lib/outputs/compliance/asd_essential_eight/__init__.py b/prowler/compliance/linode/__init__.py
similarity index 100%
rename from tests/lib/outputs/compliance/asd_essential_eight/__init__.py
rename to prowler/compliance/linode/__init__.py
diff --git a/prowler/compliance/m365/cis_4.0_m365.json b/prowler/compliance/m365/cis_4.0_m365.json
index 23582fbaac..35d64d358e 100644
--- a/prowler/compliance/m365/cis_4.0_m365.json
+++ b/prowler/compliance/m365/cis_4.0_m365.json
@@ -565,6 +565,68 @@
"References": "https://learn.microsoft.com/en-us/powershell/module/exchange/get-malwarefilterpolicy?view=exchange-ps:https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-malware-policies-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/office/compatibility/office-file-format-reference",
"DefaultValue": "The following extensions are blocked by default:ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_malware_policy_comprehensive_attachments_filter_applied",
+ "ConfigKey": "recommended_blocked_file_types",
+ "Operator": "superset",
+ "Value": [
+ "ace",
+ "ani",
+ "apk",
+ "app",
+ "appx",
+ "arj",
+ "bat",
+ "cab",
+ "cmd",
+ "com",
+ "deb",
+ "dex",
+ "dll",
+ "docm",
+ "elf",
+ "exe",
+ "hta",
+ "img",
+ "iso",
+ "jar",
+ "jnlp",
+ "kext",
+ "lha",
+ "lib",
+ "library",
+ "lnk",
+ "lzh",
+ "macho",
+ "msc",
+ "msi",
+ "msix",
+ "msp",
+ "mst",
+ "pif",
+ "ppa",
+ "ppam",
+ "reg",
+ "rev",
+ "scf",
+ "scr",
+ "sct",
+ "sys",
+ "uif",
+ "vb",
+ "vbe",
+ "vbs",
+ "vxd",
+ "wsc",
+ "wsf",
+ "wsh",
+ "xll",
+ "xz",
+ "z"
+ ]
+ }
]
},
{
@@ -1209,6 +1271,14 @@
"References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/howto-conditional-access-session-lifetime",
"DefaultValue": "The default configuration for user sign-in frequency is a rolling window of 90 days."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "entra_admin_users_sign_in_frequency_enabled",
+ "ConfigKey": "sign_in_frequency",
+ "Operator": "lte",
+ "Value": 4
+ }
]
},
{
diff --git a/prowler/compliance/m365/cis_6.0_m365.json b/prowler/compliance/m365/cis_6.0_m365.json
index d0dcfb2e6d..5815c67ac9 100644
--- a/prowler/compliance/m365/cis_6.0_m365.json
+++ b/prowler/compliance/m365/cis_6.0_m365.json
@@ -582,6 +582,68 @@
"References": "https://learn.microsoft.com/en-us/powershell/module/exchange/get-malwarefilterpolicy?view=exchange-ps:https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-malware-policies-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/office/compatibility/office-file-format-reference",
"DefaultValue": "53 extensions are blocked by default."
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_malware_policy_comprehensive_attachments_filter_applied",
+ "ConfigKey": "recommended_blocked_file_types",
+ "Operator": "superset",
+ "Value": [
+ "ace",
+ "ani",
+ "apk",
+ "app",
+ "appx",
+ "arj",
+ "bat",
+ "cab",
+ "cmd",
+ "com",
+ "deb",
+ "dex",
+ "dll",
+ "docm",
+ "elf",
+ "exe",
+ "hta",
+ "img",
+ "iso",
+ "jar",
+ "jnlp",
+ "kext",
+ "lha",
+ "lib",
+ "library",
+ "lnk",
+ "lzh",
+ "macho",
+ "msc",
+ "msi",
+ "msix",
+ "msp",
+ "mst",
+ "pif",
+ "ppa",
+ "ppam",
+ "reg",
+ "rev",
+ "scf",
+ "scr",
+ "sct",
+ "sys",
+ "uif",
+ "vb",
+ "vbe",
+ "vbs",
+ "vxd",
+ "wsc",
+ "wsf",
+ "wsh",
+ "xll",
+ "xz",
+ "z"
+ ]
+ }
]
},
{
@@ -1949,6 +2011,14 @@
"References": "https://learn.microsoft.com/en-us/purview/audit-mailboxes?view=o365-worldwide",
"DefaultValue": "AuditEnabled: True for all mailboxes except Resource Mailboxes, Public Folder Mailboxes, and DiscoverySearch Mailbox"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "exchange_user_mailbox_auditing_enabled",
+ "ConfigKey": "audit_log_age",
+ "Operator": "gte",
+ "Value": 90
+ }
]
},
{
@@ -2110,6 +2180,14 @@
"References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/mailtips/mailtips",
"DefaultValue": "MailTipsAllTipsEnabled: True, MailTipsExternalRecipientsTipsEnabled: False, MailTipsGroupMetricsEnabled: True, MailTipsLargeAudienceThreshold: 25"
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "exchange_organization_mailtips_enabled",
+ "ConfigKey": "recommended_mailtips_large_audience_threshold",
+ "Operator": "lte",
+ "Value": 25
+ }
]
},
{
diff --git a/prowler/compliance/m365/cis_7.0_m365.json b/prowler/compliance/m365/cis_7.0_m365.json
new file mode 100644
index 0000000000..941a33b187
--- /dev/null
+++ b/prowler/compliance/m365/cis_7.0_m365.json
@@ -0,0 +1,3614 @@
+{
+ "Framework": "CIS",
+ "Name": "CIS Microsoft 365 Foundations Benchmark v7.0.0",
+ "Version": "7.0",
+ "Provider": "M365",
+ "Description": "The CIS Microsoft 365 Foundations Benchmark provides prescriptive guidance for establishing a secure configuration posture for Microsoft 365 Cloud offerings running on any OS. This guide includes recommendations for Exchange Online, SharePoint Online, OneDrive for Business, Teams, Power BI (Fabric) and Microsoft Entra ID.",
+ "Requirements": [
+ {
+ "Id": "1.1.1",
+ "Description": "Administrative accounts are special privileged accounts that could have varying levels of access to data, users, and settings. Regular user accounts should never be utilized for administrative tasks and care should be taken, in the case of a hybrid environment, to keep administrative accounts separate from on-prem accounts. Administrative accounts should not have applications assigned so that they have no access to potentially vulnerable services (EX. email, Teams, SharePoint, etc.) and only access to perform tasks as needed for administrative purposes. Ensure administrative accounts are not On-premises sync enabled.",
+ "Checks": [
+ "entra_admin_users_cloud_only"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.1 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Administrative accounts are special privileged accounts that could have varying levels of access to data, users, and settings. Regular user accounts should never be utilized for administrative tasks and care should be taken, in the case of a hybrid environment, to keep administrative accounts separate from on-prem accounts. Administrative accounts should not have applications assigned so that they have no access to potentially vulnerable services (EX. email, Teams, SharePoint, etc.) and only access to perform tasks as needed for administrative purposes. Ensure administrative accounts are not On-premises sync enabled.",
+ "RationaleStatement": "In a hybrid environment, having separate accounts will help ensure that in the event of a breach in the cloud, that the breach does not affect the on-prem environment and vice versa.",
+ "ImpactStatement": "Administrative users will need to utilize login/logout functionality to switch accounts when performing administrative tasks, which means they will not benefit from SSO. This will require a migration process from the 'daily driver' account to a dedicated admin account. Once the new admin account is created, permission sets should be migrated from the 'daily driver' account to the new admin account. This includes both M365 and Azure RBAC roles. Failure to migrate Azure RBAC roles could prevent an admin from seeing their subscriptions/resources while using their admin account.",
+ "RemediationProcedure": "Remediation will require first identifying the privileged accounts that are synced from on- premises and then creating a new cloud-only account for that user. Once a replacement account is established, the hybrid account should have its role reduced to that of a non- privileged user or removed depending on the need.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Identity > Users and select All users. 3. To the right of the search box click the Add filter button. 4. Add the On-premises sync enabled filter with the value set to Yes and click Apply. 5. Verify that no user accounts in administrative roles are present in the filtered list. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"RoleManagement.Read.Directory\",\"User.Read.All\" 2. Run the following PowerShell script: $DirectoryRoles = Get-MgDirectoryRole # Get privileged role IDs $PrivilegedRoles = $DirectoryRoles | Where-Object { $_.DisplayName -like \"*Administrator*\" -or $_.DisplayName -eq \"Global Reader\" } # Get the members of these various roles $RoleMembers = $PrivilegedRoles | ForEach-Object { Get-MgDirectoryRoleMember -DirectoryRoleId $_.Id } | Select-Object Id -Unique # Retrieve details about the members in these roles $PrivilegedUsers = $RoleMembers | ForEach-Object { Get-MgUser -UserId $_.Id -Property UserPrincipalName, DisplayName, Id, OnPremisesSyncEnabled } $PrivilegedUsers | Where-Object { $_.OnPremisesSyncEnabled -eq $true } | ft DisplayName,UserPrincipalName,OnPremisesSyncEnabled 3. The script will output any hybrid users that are also members of privileged roles. If nothing returns, then no users with that criteria exist.",
+ "AdditionalInformation": "",
+ "DefaultValue": "N/A",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/add-users?view=o365-worldwide:https://learn.microsoft.com/en-us/microsoft-365/enterprise/protect-your-global-administrator-accounts?view=o365-worldwide:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/best-practices#9-use-cloud-native-accounts-for-microsoft-entra-roles:https://learn.microsoft.com/en-us/entra/fundamentals/whatis:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.2",
+ "Description": "Emergency access or \"break glass\" accounts are limited for emergency scenarios where normal administrative accounts are unavailable. They are not assigned to a specific user and will have a combination of physical and technical controls to prevent them from being accessed outside a true emergency. These emergencies could be due to several things, including: - Technical failures of a cellular provider or Microsoft related service such as MFA. - The last remaining Global Administrator account is inaccessible. Ensure two Emergency Access accounts have been defined. Note: Microsoft provides several recommendations for these accounts and how to configure them. For more information on this, please refer to the references section. The CIS Benchmark outlines the more critical things to consider.",
+ "Checks": [
+ "entra_break_glass_account_fido2_security_key_registered",
+ "entra_emergency_access_exclusion"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.1 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Emergency access or \"break glass\" accounts are limited for emergency scenarios where normal administrative accounts are unavailable. They are not assigned to a specific user and will have a combination of physical and technical controls to prevent them from being accessed outside a true emergency. These emergencies could be due to several things, including: - Technical failures of a cellular provider or Microsoft related service such as MFA. - The last remaining Global Administrator account is inaccessible. Ensure two Emergency Access accounts have been defined. Note: Microsoft provides several recommendations for these accounts and how to configure them. For more information on this, please refer to the references section. The CIS Benchmark outlines the more critical things to consider.",
+ "RationaleStatement": "In various situations, an organization may require the use of a break glass account to gain emergency access. In the event of losing access to administrative functions, an organization may experience a significant loss in its ability to provide support, lose insight into its security posture, and potentially suffer financial losses.",
+ "ImpactStatement": "Failure to properly implement emergency access accounts can weaken the security posture. Microsoft recommends excluding at least one of the two emergency access accounts from all conditional access rules, necessitating passwords with sufficient entropy and length to protect against random guesses. For a secure passwordless solution, FIDO2 security keys may be used instead of passwords.",
+ "RemediationProcedure": "To remediate using the UI: Step 1 - Create two emergency access accounts: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Expand Users > Active Users 3. Click Add user and create a new user with this criteria: o Name the account in a way that does NOT identify it with a particular person. o Assign the account to the default .onmicrosoft.com domain and not the organization's. o The password must be at least 16 characters and generated randomly. o Do not assign a license. o Assign the user the Global Administrator role. 4. Repeat the above steps for the second account. Step 2 - Exclude at least one account from conditional access policies: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Protection > Conditional Access. 3. Inspect the conditional access policies. 4. For each rule add an exclusion for at least one of the emergency access accounts. 5. Users > Exclude > Users and groups and select one emergency access account. Step 3 - Ensure the necessary procedures and policies are in place: - In order for accounts to be effectively used in a break glass situation the proper policies and procedures must be authorized and distributed by senior management. - FIDO2 Security Keys should be locked in a secure separate fireproof location. - Passwords should be at least 16 characters, randomly generated and MAY be separated in multiple pieces to be joined in case of an emergency. Warning: As of 10/15/2024 MFA is required for all users including Break Glass Accounts. It is recommended to update these accounts to use passkey (FIDO2) or configure certificate-based authentication for MFA. Both methods satisfy the MFA requirement. Additional suggestions for emergency account management: - Create access reviews for these users. - Exclude users from conditional access rules. - Add the account to a restricted management administrative unit. Warning: If CA (conditional access) exclusion is managed by a group, this group should be added to PIM for groups (licensing required) or be created as a role-assignable group. If it is a regular security group, then users with the Group Administrators role are able to bypass CA entirely.",
+ "AuditProcedure": "To audit using the UI: Step 1 - Ensure a policy and procedure is in place at the organization: - In order for accounts to be effectively used in a break-glass situation the proper policies and procedures must be authorized and distributed by senior management. - FIDO2 Security Keys should be locked in a secure separate fireproof location. - Passwords should be at least 16 characters, randomly generated and MAY be separated in multiple pieces to be joined in case of an emergency. Step 2 - Ensure two emergency access accounts are defined: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Expand Users > Active Users 3. Inspect the designated emergency access accounts and ensure the following: o The accounts are named correctly, and do NOT identify with a particular person. o The accounts use the default .onmicrosoft.com domain and not the organization's. o The accounts are cloud-only. o The accounts are unlicensed. o The accounts are not disabled or Sign-in blocked. o The accounts are assigned the Global Administrator directory role. Step 3 - Ensure at least one account is excluded from all conditional access rules: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Protection > Conditional Access. 3. Inspect the conditional access rules. 4. Ensure one of the emergency access accounts is excluded from all rules. Warning: As of 10/15/2024 MFA is required for all users including Break Glass Accounts. It is recommended to update these accounts to use passkey (FIDO2) or configure certificate-based authentication for MFA. Both methods satisfy the MFA requirement.",
+ "AdditionalInformation": "Microsoft has additional instructions regarding using Azure Monitor to capture events in the Log Analytics workspace, and then generate alerts for Emergency Access accounts. This requires an Azure subscription but should be strongly considered as a method of monitoring activity on these accounts: https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security- emergency-access#monitor-sign-in-and-audit-logs",
+ "DefaultValue": "Not defined.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-planning#stage-1-critical-items-to-do-right-now:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/admin-units-restricted-management:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mandatory-multifactor-authentication#accounts"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.3",
+ "Description": "Between two and four global administrators should be designated in the tenant. Ideally, these accounts will not have licenses assigned to them which supports additional controls found in this benchmark.",
+ "Checks": [
+ "admincenter_users_between_two_and_four_global_admins"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.1 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Between two and four global administrators should be designated in the tenant. Ideally, these accounts will not have licenses assigned to them which supports additional controls found in this benchmark.",
+ "RationaleStatement": "The Global Administrator role grants unrestricted access across all services in Microsoft Entra ID and should never be used for routine daily activities. Limiting the number of Global Administrators reduces the attack surface of the tenant and aligns with the principle of least privilege. Fewer than two Global Administrators creates a single point of failure and removes the peer oversight needed to detect unauthorized actions. More than four increases the likelihood of account compromise by an external attacker. Maintaining between two and four Global Administrators balances operational redundancy against privileged access risk. For any accounts assigned the Global Administrator role, at least one strong authentication method such as a FIDO2 key or certificate is strongly advised.",
+ "ImpactStatement": "The potential impact associated with ensuring compliance with this requirement is dependent upon the current number of global administrators configured in the tenant. If there is only one global administrator in a tenant, an additional global administrator will need to be identified and configured. If there are more than four global administrators, a review of role requirements for current global administrators will be required to identify which of the users require global administrator access.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft 365 admin center https://admin.microsoft.com 2. Select Users > Active Users. 3. In the Search field enter the name of the user to be made a Global Administrator. 4. To create a new Global Admin: 1. Select the user's name. 2. A window will appear to the right. 3. Select Manage roles. 4. Select Admin center access. 5. Check Global Administrator. 6. Click Save changes. 5. To remove a Global Admin: 1. In the Search field, enter the name of the user to be removed. 2. Select the user's name. 3. A window will appear to the right. 4. Under Roles, select Manage roles. 5. Uncheck Global Administrator. 6. Click Save changes.",
+ "AuditProcedure": "Note: If an organization's tenant is using a third-party identity provider, the audit and remediation procedures presented here may not be relevant. The principle of the recommendation is still relevant, and compensating controls that are relevant to the third-party identity provider should be implemented. To audit using the UI: 1. Navigate to the Microsoft 365 admin center https://admin.microsoft.com 2. Select Roles > Role assignments. 3. Select the Global Administrator role from the list and click on Assigned. 4. Review the list of Global Administrators. o If there are groups present, then inspect each group and its members. o Take note of the total number of Global Administrators in and outside of groups. 5. Verify the number of Global Administrators is between two and four. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes Directory.Read.All 2. Run the following PowerShell script: # Determine Id of GA role using the immutable RoleTemplateId value. $GlobalAdminRole = Get-MgDirectoryRole -Filter \"RoleTemplateId eq '62e90394- 69f5-4237-9190-012177145e10'\" $RoleMembers = Get-MgDirectoryRoleMember -DirectoryRoleId $GlobalAdminRole.Id $GlobalAdmins = [System.Collections.Generic.List[Object]]::new() foreach ($object in $RoleMembers) { $Type = $object.AdditionalProperties.'@odata.type' # Check for and process role assigned groups if ($Type -eq '#microsoft.graph.group') { $GroupId = $object.Id $GroupMembers = (Get-MgGroupMember -GroupId $GroupId).AdditionalProperties foreach ($member in $GroupMembers) { if ($member.'@odata.type' -eq '#microsoft.graph.user') { $GlobalAdmins.Add([PSCustomObject][Ordered]@{ DisplayName = $member.displayName UserPrincipalName = $member.userPrincipalName }) } } } elseif ($Type -eq '#microsoft.graph.user') { $DisplayName = $object.AdditionalProperties.displayName $UPN = $object.AdditionalProperties.userPrincipalName $GlobalAdmins.Add([PSCustomObject][Ordered]@{ DisplayName = $DisplayName UserPrincipalName = $UPN }) } } $GlobalAdmins = $GlobalAdmins | select DisplayName,UserPrincipalName -Unique Write-Host \"*** There are\" $GlobalAdmins.Count \"Global Administrators in the organization.\" 3. Review the output and ensure there are between 2 and 4 Global Administrators. Note: When tallying the number of Global Administrators, the above does not account for Partner relationships. Those are located under Settings > Partner Relationships and should be reviewed on a recurring basis.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.identity.directorymanagement/get-mgdirectoryrole?view=graph-powershell-1.0:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#all-roles:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/best-practices#5-limit-the-number-of-global-administrators-to-less-than-5:https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide#security-guidelines-for-assigning-roles"
+ }
+ ]
+ },
+ {
+ "Id": "1.1.4",
+ "Description": "Administrative accounts are special privileged accounts that could have varying levels of access to data, users, and settings. A license can enable an account to gain access to a variety of different applications, depending on the license assigned. The recommended state is to not license a privileged account or use licenses without associated applications such as Microsoft Entra ID P1 or Microsoft Entra ID P2.",
+ "Checks": [
+ "admincenter_users_admins_reduced_license_footprint"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.1 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Administrative accounts are special privileged accounts that could have varying levels of access to data, users, and settings. A license can enable an account to gain access to a variety of different applications, depending on the license assigned. The recommended state is to not license a privileged account or use licenses without associated applications such as Microsoft Entra ID P1 or Microsoft Entra ID P2.",
+ "RationaleStatement": "Ensuring administrative accounts do not use licenses with applications assigned to them will reduce the attack surface of high privileged identities in the organization's environment. Granting access to a mailbox or other collaborative tools increases the likelihood that privileged users might interact with these applications, raising the risk of exposure to social engineering attacks or malicious content. These activities should be restricted to an unprivileged 'daily driver' account. Note: In order to participate in Microsoft 365 security services such as Identity Protection, PIM and Conditional Access an administrative account will need a license attached to it. Ensure that the license used does not include any applications with potentially vulnerable services by using either Microsoft Entra ID P1 or Microsoft Entra ID P2 for the cloud-only account with administrator roles.",
+ "ImpactStatement": "Administrative users will be required to switch accounts and use manual login/logout procedures when performing privileged tasks. This change also means they will not benefit from Single Sign-On (SSO), potentially impacting workflow efficiency and user experience. Note: Alerts will be sent to TenantAdmins, including Global Administrators, by default. To ensure proper receipt, configure alerts to be sent to security or operations staff with valid email addresses or a security operations center. Otherwise, after adoption of this recommendation, alerts sent to TenantAdmins may go unreceived due to the lack of an application-based license assigned to the Global Administrator accounts.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Users > Active users. 3. Click Add a user. 4. Fill out the appropriate fields for Name, user, etc. 5. When prompted to assign licenses select as needed Microsoft Entra ID P1 or Microsoft Entra ID P2, then click Next. 6. Under the Option settings screen you may choose from several types of privileged roles. Choose Admin center access followed by the appropriate role then click Next. 7. Select Finish adding. Note: Utilizing PIM to best practices will satisfy this control. CIS and Microsoft recommend an organization keep zero permanently active assignments for roles other than emergency access accounts.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Users > Active users. 3. Sort by the Licenses column. 4. For each user account in an administrative role verify the account is assigned a license that is not associated with applications i.e. (Microsoft Entra ID P1, Microsoft Entra ID P2). o If an organization uses PIM to elevate a daily driver account to privileged levels, this control and licensing requirement can be considered satisfied. Note: The final step assumes PIM is properly configured to best practices. Accounts eligible for the Global Administrator role should require approval to activate. Using the PIM blade to permanently assign accounts to privileged roles would not satisfy this audit procedure. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"RoleManagement.Read.Directory\",\"User.Read.All\" 2. Run the following PowerShell script: $DirectoryRoles = Get-MgDirectoryRole # Get privileged role IDs $PrivilegedRoles = $DirectoryRoles | Where-Object { $_.DisplayName -like \"*Administrator*\" -or $_.DisplayName -eq \"Global Reader\" } # Get the members of these various roles $RoleMembers = $PrivilegedRoles | ForEach-Object { Get-MgDirectoryRoleMember -DirectoryRoleId $_.Id } | Select-Object Id -Unique # Retrieve details about the members in these roles $PrivilegedUsers = $RoleMembers | ForEach-Object { Get-MgUser -UserId $_.Id -Property UserPrincipalName, DisplayName, Id } $Report = [System.Collections.Generic.List[Object]]::new() foreach ($Admin in $PrivilegedUsers) { $License = $null $License = (Get-MgUserLicenseDetail -UserId $Admin.id).SkuPartNumber - join \", \" $Object = [pscustomobject][ordered]@{ DisplayName = $Admin.DisplayName UserPrincipalName = $Admin.UserPrincipalName License = $License } $Report.Add($Object) } $Report 3. The output will display users assigned privileged roles alongside their assigned licenses. Additional manual assessment is required to determine if the licensing is appropriate for the user.",
+ "AdditionalInformation": "",
+ "DefaultValue": "N/A",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/enterprise/protect-your-global-administrator-accounts?view=o365-worldwide:https://learn.microsoft.com/en-us/entra/fundamentals/whatis#what-are-the-microsoft-entra-id-licenses:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference:https://learn.microsoft.com/en-us/microsoft-365/business-premium/m365bp-protect-admin-accounts?view=o365-worldwide:https://learn.microsoft.com/en-us/microsoft-365/enterprise/subscriptions-licenses-accounts-and-tenants-for-microsoft-cloud-offerings?view=o365-worldwide#licenses:https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-deployment-plan#principle-of-least-privilege"
+ }
+ ]
+ },
+ {
+ "Id": "1.2.1",
+ "Description": "Microsoft 365 Groups is the foundational membership service that drives all teamwork across Microsoft 365. With Microsoft 365 Groups, you can give a group of people access to a collection of shared resources. When a new group is created in the Administration panel, the default privacy value of the group is \"Public\". (In this case, 'public' means accessible to the identities within the organization without requiring group owner authorization to join.) The recommended state is Microsoft 365 Groups are set to Private in the Administration panel. Note: Although there are several different group types, this recommendation concerns Microsoft 365 Groups specifically.",
+ "Checks": [
+ "admincenter_groups_not_public_visibility"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.2 Teams & groups",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft 365 Groups is the foundational membership service that drives all teamwork across Microsoft 365. With Microsoft 365 Groups, you can give a group of people access to a collection of shared resources. When a new group is created in the Administration panel, the default privacy value of the group is \"Public\". (In this case, 'public' means accessible to the identities within the organization without requiring group owner authorization to join.) The recommended state is Microsoft 365 Groups are set to Private in the Administration panel. Note: Although there are several different group types, this recommendation concerns Microsoft 365 Groups specifically.",
+ "RationaleStatement": "If group privacy is not controlled, any user may access sensitive information, depending on the group they try to access. When the privacy value of a group is set to \"Public,\" users may access data related to this group (e.g. SharePoint) via three methods: 1. The Azure Portal: Users can add themselves to the public group via the Azure Portal; however, administrators are notified when users access the Portal. 2. Access Requests: Users can request to join the group via the Groups application in the Access Panel. This provides the user with immediate access to the group, even though they are required to send a message to the group owner when requesting to join. 3. SharePoint URL: Users can directly access a group via its SharePoint URL, which is usually guessable and can be found in the Groups application within the Access Panel.",
+ "ImpactStatement": "If the recommendation is applied, group owners could receive more access requests than usual, especially regarding groups originally meant to be public.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Teams & groups > Active teams & groups. 3. On the Active teams and groups page, select the group's name that is public. 4. On the popup groups name page, Select Settings. 5. Under Privacy, select Private.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Teams & groups > Active teams & groups. 3. On the Active teams and groups page, check that no groups have the status 'Public' in the privacy column. To audit using PowerShell: 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"Group.Read.All\". 2. Run the following Microsoft Graph PowerShell command: $Groups = Get-MgGroup -All -Filter \"groupTypes/any(c:c eq 'Unified')\" ` -Property Id,DisplayName,Visibility,GroupTypes # Displays the groups to the console for review $Groups | ft Id,DisplayName,Visibility 3. Verify that Visibility is Private for each group.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Public when created from the Administration portal; private otherwise.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/groups-self-service-management:https://learn.microsoft.com/en-us/microsoft-365/admin/create-groups/compare-groups?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "1.2.2",
+ "Description": "Shared mailboxes are used when multiple people need access to the same mailbox, such as a company information or support email address, reception desk, or other function that might be shared by multiple people. Users with permissions to the group mailbox can send as or send on behalf of the mailbox email address if the administrator has given that user permissions to do that. This is particularly useful for help and support mailboxes because users can send emails from \"Contoso Support\" or \"Building A Reception Desk.\" Shared mailboxes are created with a corresponding user account using a system generated password that is unknown at the time of creation. The recommended state is Sign in blocked for Shared mailboxes.",
+ "Checks": [
+ "exchange_shared_mailbox_sign_in_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.2 Teams & groups",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Shared mailboxes are used when multiple people need access to the same mailbox, such as a company information or support email address, reception desk, or other function that might be shared by multiple people. Users with permissions to the group mailbox can send as or send on behalf of the mailbox email address if the administrator has given that user permissions to do that. This is particularly useful for help and support mailboxes because users can send emails from \"Contoso Support\" or \"Building A Reception Desk.\" Shared mailboxes are created with a corresponding user account using a system generated password that is unknown at the time of creation. The recommended state is Sign in blocked for Shared mailboxes.",
+ "RationaleStatement": "The intent of the shared mailbox is to only allow delegated access from other mailboxes. An admin could reset the password, or an attacker could potentially gain access to the shared mailbox allowing the direct sign-in to the shared mailbox and subsequently the sending of email from a sender that does not have a unique identity. To prevent this, block sign-in for the account that is associated with the shared mailbox.",
+ "ImpactStatement": "Blocking sign-in to shared mailboxes prevents direct authentication to these accounts. Authorized users can still access shared mailbox content through their own accounts using Outlook delegation or by being granted Send As/Send on Behalf permissions. This change strengthens security by ensuring shared mailboxes cannot serve as entry points for unauthorized access.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com/ 2. Click to expand Teams & groups and select Shared mailboxes. 3. Take note of all shared mailboxes. 4. Click to expand Users and select Active users. 5. Select a shared mailbox account to open its properties pane and then select Block sign-in. 6. Check the box for Block this user from signing in. 7. Repeat for any additional shared mailboxes. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"User.ReadWrite.All\" 2. Connect to Exchange Online using Connect-ExchangeOnline. 3. To disable sign-in for a single account: $MBX = Get-EXOMailbox -Identity TestUser@example.com Update-MgUser -UserId $MBX.ExternalDirectoryObjectId -AccountEnabled:$false The following can be used block sign-in to all Shared Mailboxes: $MBX = Get-EXOMailbox -RecipientTypeDetails SharedMailbox $MBX | ForEach-Object { Update-MgUser -UserId $_.ExternalDirectoryObjectId - AccountEnabled:$false }",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com/ 2. Expand Teams & groups and select Shared mailboxes. 3. Take note of all shared mailboxes. 4. Expand Users and select Active users. 5. Select a shared mailbox account to open its properties pane, and review. 6. Verify that the text under the name reads Sign-in blocked. 7. Repeat for any additional shared mailboxes. Note: If sign-in is not blocked there will be an option to Block sign-in. This means the shared mailbox is out of compliance with this recommendation. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline 2. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"User.Read.All\" 3. Run the following PowerShell commands: $MBX = Get-EXOMailbox -RecipientTypeDetails SharedMailbox -ResultSize Unlimited $MBX | ForEach-Object { Get-MgUser -UserId $_.ExternalDirectoryObjectId ` -Property DisplayName, UserPrincipalName, AccountEnabled } | Format-Table DisplayName, UserPrincipalName, AccountEnabled 4. Ensure AccountEnabled is set to False for all Shared Mailboxes.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AccountEnabled: True",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes?view=o365-worldwide:https://learn.microsoft.com/en-us/microsoft-365/admin/email/create-a-shared-mailbox?view=o365-worldwide#block-sign-in-for-the-shared-mailbox-account:https://learn.microsoft.com/en-us/microsoft-365/enterprise/block-user-accounts-with-microsoft-365-powershell?view=o365-worldwide#block-individual-user-accounts"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.1",
+ "Description": "Microsoft cloud-only accounts have a pre-defined password policy that cannot be changed. The only items that can change are the number of days until a password expires and whether or not passwords expire at all.",
+ "Checks": [
+ "admincenter_settings_password_never_expire"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft cloud-only accounts have a pre-defined password policy that cannot be changed. The only items that can change are the number of days until a password expires and whether or not passwords expire at all.",
+ "RationaleStatement": "Organizations such as NIST and Microsoft recommend against arbitrarily requiring users to change their passwords after a set period, unless there is evidence of compromise or the user has forgotten the password. This guidance applies even to single-factor (password-only) scenarios, as forced, periodic changes often lead to weaker passwords and reduced security. Additionally, this Benchmark advises implementing multi-factor authentication (MFA) for all accounts, which further diminishes the value of password expiration policies. Long-lived passwords can be further strengthened by enabling additional password protection features in Entra ID.",
+ "ImpactStatement": "When setting passwords not to expire it is important to have other controls in place to supplement this setting. See below for related recommendations and user guidance. - Ban common passwords. - Educate users to not reuse organization passwords anywhere else. - Enforce Multi-Factor Authentication registration for all users.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org Settings. 3. Click on Security & privacy. 4. Check the Set passwords to never expire (recommended) box. 5. Click Save. To remediate using PowerShell: 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"Domain.ReadWrite.All\". 2. Run the following Microsoft Graph PowerShell command: Update-MgDomain -DomainId <Domain> -PasswordValidityPeriodInDays 2147483647",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org Settings. 3. Click on Security & privacy. 4. Select Password expiration policy and verify that Set passwords to never expire (recommended) has been checked. To audit using PowerShell: 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"Domain.Read.All\". 2. Run the following Microsoft Online PowerShell command: Get-MgDomain | ft id,PasswordValidityPeriodInDays 3. Verify the value returned for valid domains is 2147483647",
+ "AdditionalInformation": "",
+ "DefaultValue": "If the property is not set, a default value of 90 days will be used",
+ "References": "https://pages.nist.gov/800-63-3/sp800-63b.html:https://www.cisecurity.org/white-papers/cis-password-policy-guide/:https://learn.microsoft.com/en-us/microsoft-365/admin/misc/password-policy-recommendations?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.2",
+ "Description": "Idle session timeout allows the configuration of a setting which will timeout inactive users after a pre-determined amount of time. When a user reaches the set idle timeout session, they'll get a notification that they're about to be signed out. They must choose to stay signed in or they'll be automatically signed out of all Microsoft 365 web apps. Combined with a Conditional Access rule this will only impact unmanaged devices. A managed device is considered a device managed by Intune MDM or joined to a domain (Entra ID or Hybrid joined). The following Microsoft 365 web apps are supported. - Outlook Web App - OneDrive - SharePoint - Microsoft Fabric - Microsoft365.com and other start pages - Microsoft 365 web apps (Word, Excel, PowerPoint) - Microsoft 365 Admin Center - M365 Defender Portal - Microsoft Purview Compliance Portal The recommended setting is 3 hours (or less) for unmanaged devices. Note: Idle session timeout doesn't affect Microsoft 365 desktop and mobile apps.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Idle session timeout allows the configuration of a setting which will timeout inactive users after a pre-determined amount of time. When a user reaches the set idle timeout session, they'll get a notification that they're about to be signed out. They must choose to stay signed in or they'll be automatically signed out of all Microsoft 365 web apps. Combined with a Conditional Access rule this will only impact unmanaged devices. A managed device is considered a device managed by Intune MDM or joined to a domain (Entra ID or Hybrid joined). The following Microsoft 365 web apps are supported. - Outlook Web App - OneDrive - SharePoint - Microsoft Fabric - Microsoft365.com and other start pages - Microsoft 365 web apps (Word, Excel, PowerPoint) - Microsoft 365 Admin Center - M365 Defender Portal - Microsoft Purview Compliance Portal The recommended setting is 3 hours (or less) for unmanaged devices. Note: Idle session timeout doesn't affect Microsoft 365 desktop and mobile apps.",
+ "RationaleStatement": "Ending idle sessions through an automatic process can help protect sensitive company data and will add another layer of security for end users who work on unmanaged devices that can potentially be accessed by the public. Unauthorized individuals onsite or remotely can take advantage of systems left unattended over time. Automatic timing out of sessions makes this more difficult.",
+ "ImpactStatement": "If step 2 in the Audit/Remediation procedure is left out, then there is no issue with this from a security standpoint. However, it will require users on trusted devices to sign in more frequently which could result in credential prompt fatigue. Users don't get signed out in these cases: - If they get single sign-on (SSO) into the web app from the device joined account. - If they selected Stay signed in at the time of sign-in. For more info on hiding this option for your organization, see Add branding to your organization's sign-in page. - If they're on a managed device, that is compliant or joined to a domain and using a supported browser, like Microsoft Edge, or Google Chrome with the Microsoft Single Sign On extension. Note: Idle session timeout also affects the Azure Portal idle timeout if this is not explicitly set to a different timeout. The Azure Portal idle timeout applies to all kinds of devices, not just unmanaged. See: change the directory timeout setting admin",
+ "RemediationProcedure": "Step 1 - Configure Idle session timeout: To remediate using the UI: 1. Navigate to the Microsoft 365 admin center https://admin.microsoft.com/. 2. Expand Settings > Org settings. 3. Click Security & Privacy tab. 4. Select Idle session timeout. 5. Check the box Turn on to set the period of inactivity for users to be signed off of Microsoft 365 web apps 6. Set a maximum value of 3 hours. 7. Click save. Step 2 - Ensure the Conditional Access policy is in place: To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Protect > Conditional Access. 3. Click New policy and give the policy a name. o Select Users > All users. o Select Cloud apps or actions > Select apps and select Office 365 o Select Conditions > Client apps > Yes check only Browser unchecking all other boxes. o Select Sessions and check Use app enforced restrictions. 4. Set Enable policy to On and click Create. Note: To ensure that idle timeouts affect only unmanaged devices, both steps 1 and 2 must be completed. Otherwise managed devices will also be impacted by the timeout policy.",
+ "AuditProcedure": "Step 1 - Ensure Idle session timeout is configured: To audit using the UI: 1. Navigate to the Microsoft 365 admin center https://admin.microsoft.com/. 2. Expand Settings > Org settings. 3. Click Security & Privacy tab. 4. Select Idle session timeout. 5. Verify that Turn on to set the period of inactivity for users to be signed off of Microsoft 365 web apps is set to 3 hours (or less). To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\": 2. Run the following script: $TimeoutPolicy = Get-MgPolicyActivityBasedTimeoutPolicy $BenchmarkTimeSpan = [TimeSpan]::Parse('03:00:00') # 3 hours if ($TimeoutPolicy) { $PolicyDefinition = $TimeoutPolicy.Definition | ConvertFrom-Json $Timeout = $PolicyDefinition.ActivityBasedTimeoutPolicy.ApplicationPolicies[0].WebSessio nIdleTimeout $TimeSpan = [TimeSpan]::Parse($Timeout) $TimeoutReadable = \"{0} days, {1} hours, {2} minutes\" ` -f $TimeSpan.Days, $TimeSpan.Hours, $TimeSpan.Minutes if ($TimeSpan -le $BenchmarkTimeSpan) { Write-Host \"** PASS ** Timeout is set to $TimeoutReadable.\" } else { Write-Host \"** FAIL ** Timeout is too long. It is set to $TimeoutReadable.\" } } else { Write-Host \"** FAIL **: Idle session timeout is not configured.\" } 3. Verify the policy exists and is 3 hours or less. Step 2 - Ensure the Conditional Access policy is in place: To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Protect > Conditional Access. 3. Inspect existing conditional access rules for one that meets the below conditions: o Users or agents (Preview) is set to include All users. o Cloud apps or actions > Select apps is set to Office 365. o Conditions > Client apps is Browser and nothing else. o Session is set to Use app enforced restrictions. o Enable Policy is set to On To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\": 2. Run the following script: $Caps = Get-MgIdentityConditionalAccessPolicy -All | Where-Object { $_.SessionControls.ApplicationEnforcedRestrictions.IsEnabled } $CapReport = [System.Collections.Generic.List[Object]]::new() # Filter to policies with \"Use app enforced restrictions\" enabled # Loop through policies and generate a per policy report. foreach ($policy in $Caps) { $Name = $policy.DisplayName $Users = $policy.Conditions.Users.IncludeUsers $Targets = $policy.Conditions.Applications.IncludeApplications $ClientApps = $policy.Conditions.ClientAppTypes $Restrictions = $policy.SessionControls.ApplicationEnforcedRestrictions.IsEnabled $State = $policy.State $CountPass = $Targets.count -eq 1 -and $ClientApps.count -eq 1 $Pass = $Targets -eq 'Office365' -and $ClientApps -eq 'browser' -and $Restrictions -and $CountPass -and $State -eq 'enabled' $obj = [PSCustomObject]@{ DisplayName = $Name AuditState = if ($Pass) { \"PASS\" } else { \"FAIL\" } IncludeUsers = $Users IncludeApplications = $Targets ClientAppTypes = $ClientApps AppEnforcedRestrictions = $Restrictions State = $State } $CapReport.Add($obj) } if ($Caps) { $CapReport } else { Write-Host \"** FAIL **: There are no qualifying conditional access policies.\" } 3. The script will output qualifying Conditional Access Policies. If one policy passes, then the recommendation passes. A passing policy will have the following properties: DisplayName : (CIS) Idle timeout for unmanaged AuditState : PASS IncludeUsers : {All} # IncludeUsers not currently scored IncludeApplications : {Office365} ClientAppTypes : {browser} AppEnforcedRestrictions : True State : enabled Note: Both steps 1 and 2 must pass audit checks in order for the recommendation to pass as a whole.",
+ "AdditionalInformation": "According to Microsoft idle session timeout isn't supported when third party cookies are disabled in the browser. Users won't see any sign-out prompts.",
+ "DefaultValue": "Not configured. (Idle sessions will not timeout.)",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/manage/idle-session-timeout-web-apps?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.3",
+ "Description": "External calendar sharing allows an administrator to enable the ability for users to share calendars with anyone outside of the organization. Outside users will be sent a URL that can be used to view the calendar.",
+ "Checks": [
+ "admincenter_external_calendar_sharing_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "External calendar sharing allows an administrator to enable the ability for users to share calendars with anyone outside of the organization. Outside users will be sent a URL that can be used to view the calendar.",
+ "RationaleStatement": "Attackers often spend time learning about organizations before launching an attack. Publicly available calendars can help attackers understand organizational relationships and determine when specific users may be more vulnerable to an attack, such as when they are traveling.",
+ "ImpactStatement": "This functionality is not widely used. As a result, it is unlikely that implementation of this setting will cause an impact to most users. Users that do utilize this functionality are likely to experience a minor inconvenience when scheduling meetings or synchronizing calendars with people outside the tenant.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings select Org settings. 3. In the Services section click Calendar. 4. Uncheck Let your users share their calendars with people outside of your organization who have Office 365 or Exchange. 5. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following Exchange Online PowerShell command: Set-SharingPolicy -Identity \"Default Sharing Policy\" -Enabled $False",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. In the Services section click Calendar. 4. Verify that Let your users share their calendars with people outside of your organization who have Office 365 or Exchange is unchecked. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following Exchange Online PowerShell command: Get-SharingPolicy -Identity \"Default Sharing Policy\" | ft Name,Enabled 3. Verify that Enabled is set to False",
+ "AdditionalInformation": "The following script can be used to audit any mailboxes that might be sharing calendars prior to disabling the feature globally: $mailboxes = Get-Mailbox -ResultSize Unlimited foreach ($mailbox in $mailboxes) { # Get the name of the default calendar folder (depends on the mailbox's language) $calendarFolder = [string](Get-ExoMailboxFolderStatistics $mailbox.PrimarySmtpAddress -FolderScope Calendar| Where-Object { $_.FolderType -eq 'Calendar' }).Name # Get users calendar folder settings for their default Calendar folder # calendar has the format identity:\\<calendar folder name> $calendar = Get-MailboxCalendarFolder -Identity \"$($mailbox.PrimarySmtpAddress):\\$calendarFolder\" if ($calendar.PublishEnabled) { Write-Host -ForegroundColor Yellow \"Calendar publishing is enabled for $($mailbox.PrimarySmtpAddress) on $($calendar.PublishedCalendarUrl)\" } }",
+ "DefaultValue": "Enabled (True)",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/manage/share-calendars-with-external-users?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.4",
+ "Description": "By default, users can install add-ins in their Microsoft Word, Excel, and PowerPoint applications, allowing data access within the application. Do not allow users to install add-ins in Word, Excel, or PowerPoint.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "By default, users can install add-ins in their Microsoft Word, Excel, and PowerPoint applications, allowing data access within the application. Do not allow users to install add-ins in Word, Excel, or PowerPoint.",
+ "RationaleStatement": "Attackers commonly use vulnerable and custom-built add-ins to access data in user applications. While allowing users to install add-ins by themselves does allow them to easily acquire useful add-ins that integrate with Microsoft applications, it can represent a risk if not used and monitored carefully. Disabling future users' ability to install add-ins in Microsoft Word, Excel, or PowerPoint helps reduce your threat-surface and mitigate this risk.",
+ "ImpactStatement": "Implementation of this change will impact both end users and administrators. End users will not be able to install add-ins that they may want to install.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. In Services select User owned apps and services. 4. Uncheck Let users access the Office Store and Let users start trials on behalf of your organization. 5. Click Save. To remediate using PowerShell 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"OrgSettings-AppsAndServices.ReadWrite.All\". 2. Run the following Microsoft Graph PowerShell commands: $uri = \"https://graph.microsoft.com/beta/admin/appsAndServices\" $body = @{ \"Settings\" = @{ \"isAppAndServicesTrialEnabled\" = $false \"isOfficeStoreEnabled\" = $false } } | ConvertTo-Json Invoke-MgGraphRequest -Method PATCH -Uri $uri -Body $body",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. In Services select User owned apps and services. 4. Verify that Let users access the Office Store and Let users start trials on behalf of your organization are not checked. To Audit using PowerShell: 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"OrgSettings-AppsAndServices.Read.All\". 2. Run the following Microsoft Graph PowerShell command: $Uri = \"https://graph.microsoft.com/beta/admin/appsAndServices/settings\" Invoke-MgGraphRequest -Uri $Uri 3. Verify both isOfficeStoreEnabled and isAppAndServicesTrialEnabled are False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Let users access the Office Store is Checked Let users start trials on behalf of your organization is Checked",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-addins-in-the-admin-center?view=o365-worldwide#manage-add-in-downloads-by-turning-onoff-the-office-store-across-all-apps-except-outlook"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.5",
+ "Description": "Microsoft Forms can be used for phishing attacks by asking personal or sensitive information and collecting the results. Microsoft 365 has built-in protection that will proactively scan for phishing attempt in forms such personal information request.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Forms can be used for phishing attacks by asking personal or sensitive information and collecting the results. Microsoft 365 has built-in protection that will proactively scan for phishing attempt in forms such personal information request.",
+ "RationaleStatement": "Enabling internal phishing protection for Microsoft Forms will prevent attackers using forms for phishing attacks by asking personal or other sensitive information and URLs.",
+ "ImpactStatement": "If potential phishing was detected, the form will be temporarily blocked and cannot be distributed, and response collection will not happen until it is unblocked by the administrator or keywords were removed by the creator.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Under Services select Microsoft Forms. 4. Click the checkbox labeled Add internal phishing protection under Phishing protection. 5. Click Save. To remediate using PowerShell 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"OrgSettings-AppsAndServices.ReadWrite.All\". 2. Run the following Microsoft Graph PowerShell commands: $uri = 'https://graph.microsoft.com/beta/admin/forms/settings' $body = @{ \"isInOrgFormsPhishingScanEnabled\" = $true } | ConvertTo-Json Invoke-MgGraphRequest -Method PATCH -Uri $uri -Body $body",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Under Services select Microsoft Forms. 4. Verify the checkbox labeled Add internal phishing protection is checked under Phishing protection. To Audit using PowerShell: 1. Connect to the Microsoft Graph service using Connect-MgGraph -Scopes \"OrgSettings-Forms.Read.All\". 2. Run the following Microsoft Graph PowerShell commands: $uri = 'https://graph.microsoft.com/beta/admin/forms/settings' Invoke-MgGraphRequest -Uri $uri | select isInOrgFormsPhishingScanEnabled 3. Verify that isInOrgFormsPhishingScanEnabled is 'True'.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Internal Phishing Protection is enabled.",
+ "References": "https://learn.microsoft.com/en-US/microsoft-forms/administrator-settings-microsoft-forms:https://learn.microsoft.com/en-US/microsoft-forms/review-unblock-forms-users-detected-blocked-potential-phishing"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.6",
+ "Description": "Customer Lockbox is a security feature that provides an additional layer of control and transparency to customer data in Microsoft 365. It offers an approval process for Microsoft support personnel to access organization data and creates an audited trail to meet compliance requirements.",
+ "Checks": [
+ "admincenter_organization_customer_lockbox_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Customer Lockbox is a security feature that provides an additional layer of control and transparency to customer data in Microsoft 365. It offers an approval process for Microsoft support personnel to access organization data and creates an audited trail to meet compliance requirements.",
+ "RationaleStatement": "Enabling this feature protects organizational data against data spillage and exfiltration.",
+ "ImpactStatement": "Administrators will need to grant Microsoft access to the tenant environment prior to a Microsoft engineer accessing the environment for support or troubleshooting.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Select Security & privacy tab. 4. Click Customer lockbox. 5. Check the box Require approval for all data access requests. 6. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-OrganizationConfig -CustomerLockBoxEnabled $true",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Select Security & privacy tab. 4. Click Customer lockbox. 5. Verify the box labeled Require approval for all data access requests is checked. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-OrganizationConfig | Select-Object CustomerLockBoxEnabled 3. Verify the value is set to True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Require approval for all data access requests - Unchecked CustomerLockboxEnabled - False",
+ "References": "https://learn.microsoft.com/en-us/purview/customer-lockbox-requests#turn-customer-lockbox-requests-on-or-off"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.7",
+ "Description": "Third-party storage can be enabled for users in Microsoft 365, allowing them to store and share documents using services such as Dropbox, alongside OneDrive and team sites. Ensure Microsoft 365 on the web third-party storage services are restricted.",
+ "Checks": [
+ "exchange_mailbox_policy_additional_storage_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Third-party storage can be enabled for users in Microsoft 365, allowing them to store and share documents using services such as Dropbox, alongside OneDrive and team sites. Ensure Microsoft 365 on the web third-party storage services are restricted.",
+ "RationaleStatement": "By using external storage services an organization may increase the risk of data breaches and unauthorized access to confidential information. Additionally, third-party services may not adhere to the same security standards as the organization, making it difficult to maintain data privacy and security.",
+ "ImpactStatement": "Impact associated with this change is highly dependent upon current practices in the tenant. If users do not use other storage providers, then minimal impact is likely. However, if users do regularly utilize providers outside of the tenant this will affect their ability to continue to do so.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Go to Settings > Org Settings > Services > Microsoft 365 on the web 3. Uncheck Let users open files stored in third-party storage services in Microsoft 365 on the web To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Application.ReadWrite.All\" 2. Run the following script: $SP = Get-MgServicePrincipal -Filter \"appId eq 'c1f33bc0-bdb4-4248-ba9b- 096807ddb43e'\" # If the service principal doesn't exist then create it first. if (-not $SP) { $SP = New-MgServicePrincipal -AppId \"c1f33bc0-bdb4-4248-ba9b- 096807ddb43e\" } Update-MgServicePrincipal -ServicePrincipalId $SP.Id -AccountEnabled:$false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Go to Settings > Org Settings > Services > Microsoft 365 on the web 3. Verify that Let users open files stored in third-party storage services in Microsoft 365 on the web is not checked. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Application.Read.All\". 2. Run the following script: $SP = Get-MgServicePrincipal -Filter \"appId eq 'c1f33bc0-bdb4-4248-ba9b- 096807ddb43e'\" if ((-not $SP) -or $SP.AccountEnabled) { Write-Host \"Audit Result: ** FAIL **\" } else { Write-Host \"Audit Result: ** PASS **\" } 3. Verify that AccountEnabled is False. Note: The check will also fail if the Service Principal does not exist as users will still be able to open files stored in third-party storage services in Microsoft 365 on the web.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled - Users are able to open files stored in third-party storage services",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/setup/set-up-file-storage-and-sharing?view=o365-worldwide#enable-or-disable-third-party-storage-services"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.8",
+ "Description": "Sway is a Microsoft 365 app that lets organizations create interactive, web-based presentations using images, text, videos and other media. Its design engine simplifies the process, allowing for quick customization. Presentations can then be shared via a link. This setting controls user Sway sharing capability, both within and outside of the organization. By default, Sway is enabled for everyone in the organization.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Sway is a Microsoft 365 app that lets organizations create interactive, web-based presentations using images, text, videos and other media. Its design engine simplifies the process, allowing for quick customization. Presentations can then be shared via a link. This setting controls user Sway sharing capability, both within and outside of the organization. By default, Sway is enabled for everyone in the organization.",
+ "RationaleStatement": "Disable external sharing of Sway documents that can contain sensitive information to prevent accidental or arbitrary data leaks.",
+ "ImpactStatement": "Interactive reports, presentations, newsletters, and other items created in Sway will not be shared outside the organization by users.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Under Services select Sway o Uncheck: Let people in your organization share their sways with people outside your organization. 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings > Org settings. 3. Under Services select Sway. 4. Verify that under Sharing, the following is not checked: o Let people in your organization share their sways with people outside your organization.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Let people in your organization share their sways with people outside your organization - Enabled",
+ "References": "https://support.microsoft.com/en-us/office/administrator-settings-for-sway-d298e79b-b6ab-44c6-9239-aa312f5784d4:https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-sway-service-description"
+ }
+ ]
+ },
+ {
+ "Id": "1.3.9",
+ "Description": "Shared Bookings allows you to invite your team members and create booking pages and let your customers book time with you and your team. It contains various settings to define services, manage staff members, configure schedules and availability, business hours and customize how appointments are scheduled. These pages can be customized to fit the diverse needs of your organization. It is an extension of Person Bookings. The recommended state is to restrict the OwaMailboxPolicy-Default policy or disable at the organization level.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "1 Microsoft 365 admin center",
+ "SubSection": "1.3 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Shared Bookings allows you to invite your team members and create booking pages and let your customers book time with you and your team. It contains various settings to define services, manage staff members, configure schedules and availability, business hours and customize how appointments are scheduled. These pages can be customized to fit the diverse needs of your organization. It is an extension of Person Bookings. The recommended state is to restrict the OwaMailboxPolicy-Default policy or disable at the organization level.",
+ "RationaleStatement": "Shared Bookings pages can be exploited by threat actors to impersonate legitimate users using convincing internal email addresses. A compromised low-privilege account could be used to mimic high-profile identities (e.g., the CEO) and bypass impersonation filters to initiate fraudulent actions like fund transfers. Additionally, attackers may create authoritative-looking addresses (e.g., admin@, hostmaster@) to conduct social engineering attacks on external parties aimed at the transfer of infrastructure control. To reduce this risk, access to Shared Bookings should be limited to users with a clear business need and subject to monitoring and governance.",
+ "ImpactStatement": "Disabling Shared Bookings will limit users' ability to create self-service scheduling pages, which may reduce convenience for teams that rely on automated meeting coordination. Approved users will need to be added to a separate OWA Policy which will increase administrative overhead. Note: Before modifying the default owa policy, ensure that any users who rely on Shared Bookings are assigned a separate policy that explicitly allows its use. This will help prevent unintended service disruptions.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-OwaMailboxPolicy \"OwaMailboxPolicy-Default\" - BookingsMailboxCreationEnabled $false Optionally: For a more restrictive state Bookings can be disabled at the organization level 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following command: Set-OrganizationConfig -BookingsEnabled $false Note: Disabling Bookings at the tenant (organization) level will be more impactful to end users and is not required for compliance.",
+ "AuditProcedure": "Ensure Shared Bookings is turned off in the OWA Default policy. If booking is disabled at the tenant (OrganizationConfig) level this is also a compliant state. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following command: Get-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default | fl BookingsMailboxCreationEnabled 3. Verify that BookingsMailboxCreationEnabled is set to False. Optionally: If Bookings is disabled at the organization level, this is also considered a compliant state. 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following command: Get-OrganizationConfig | fl BookingsEnabled 3. If BookingsEnabled is set to False, the organization is using a more restrictive and compliant configuration. In this case changing the default OWA policy would not be required for compliance.",
+ "AdditionalInformation": "",
+ "DefaultValue": "BookingsMailboxCreationEnabled : True (OwaMailboxPolicy-Default) BookingsEnabled : True",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/bookings/turn-bookings-on-or-off?view=o365-worldwide:https://techcommunity.microsoft.com/blog/office365businessappsblog/enhancing-security-in-microsoft-bookings-best-practices-for-admins/4382447:https://learn.microsoft.com/en-us/microsoft-365/bookings/best-practices-shared-bookings?view=o365-worldwide&source=recommendations:https://www.cyberis.com/article/microsoft-bookings-facilitating-impersonation"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.1",
+ "Description": "Enabling Safe Links policy for Office applications allows URL's that exist inside of Office documents and email applications opened by Office, Office Online and Office mobile to be processed against Defender for Office time-of-click verification and rewritten if required. Note: E5 Licensing includes a number of Built-in Protection policies. When auditing policies note which policy you are viewing, and keep in mind CIS recommendations often extend the Default or Built-in Policies provided by MS. In order to Pass the highest priority policy must match all settings recommended.",
+ "Checks": [
+ "defender_safelinks_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Enabling Safe Links policy for Office applications allows URL's that exist inside of Office documents and email applications opened by Office, Office Online and Office mobile to be processed against Defender for Office time-of-click verification and rewritten if required. Note: E5 Licensing includes a number of Built-in Protection policies. When auditing policies note which policy you are viewing, and keep in mind CIS recommendations often extend the Default or Built-in Policies provided by MS. In order to Pass the highest priority policy must match all settings recommended.",
+ "RationaleStatement": "Safe Links for Office applications extends phishing protection to documents and emails that contain hyperlinks, even after they have been delivered to a user.",
+ "ImpactStatement": "User impact associated with this change is minor - users may experience a very short delay when clicking on URLs in Office documents before being directed to the requested site. Users should be informed of the change as, in the event a link is unsafe and blocked, they will receive a message that it has been blocked.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com 2. Under Email & collaboration select Policies & rules 3. Select Threat policies then Safe Links 4. Click on +Create 5. Name the policy then click Next 6. In Domains select all valid domains for the organization and Next 7. Ensure the following URL & click protection settings are defined: Email o Checked On: Safe Links checks a list of known, malicious links when users click links in email. URLs are rewritten by default o Checked Apply Safe Links to email messages sent within the organization o Checked Apply real-time URL scanning for suspicious links and links that point to files o Checked Wait for URL scanning to complete before delivering the message o Unchecked Do not rewrite URLs, do checks via Safe Links API only. Teams o Checked On: Safe Links checks a list of known, malicious links when users click links in Microsoft Teams. URLs are not rewritten Office 365 Apps o Checked On: Safe Links checks a list of known, malicious links when users click links in Microsoft Office apps. URLs are not rewritten Click protection settings o Checked Track user clicks o Unchecked Let users click through the original URL o There is no recommendation for organization branding. 8. Click Next twice and finally Submit To remediate using PowerShell: 1. Connect using Connect-ExchangeOnline. 2. Run the following PowerShell script to create a policy at highest priority that will apply to all valid domains on the tenant: # Create the Policy $params = @{ Name = \"CIS SafeLinks Policy\" EnableSafeLinksForEmail = $true EnableSafeLinksForTeams = $true EnableSafeLinksForOffice = $true TrackClicks = $true AllowClickThrough = $false ScanUrls = $true EnableForInternalSenders = $true DeliverMessageAfterScan = $true DisableUrlRewrite = $false } New-SafeLinksPolicy @params # Create the rule for all users in all valid domains and associate with Policy New-SafeLinksRule -Name \"CIS SafeLinks\" -SafeLinksPolicy \"CIS SafeLinks Policy\" -RecipientDomainIs (Get-AcceptedDomain).Name -Priority 0",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com 2. Under Email & collaboration select Policies & rules 3. Select Threat policies then Safe Links 4. Inspect each policy and attempt to identify one that matches the parameters outlined below. 5. Scroll down the pane and click on Edit Protection settings (Global Readers will look for on or off values) 6. Verify that the following protection settings are set as outlined: Email o Checked On: Safe Links checks a list of known, malicious links when users click links in email. URLs are rewritten by default o Checked Apply Safe Links to email messages sent within the organization o Checked Apply real-time URL scanning for suspicious links and links that point to files o Checked Wait for URL scanning to complete before delivering the message o Unchecked Do not rewrite URLs, do checks via Safe Links API only. Teams o Checked On: Safe Links checks a list of known, malicious links when users click links in Microsoft Teams. URLs are not rewritten Office 365 Apps o Checked On: Safe Links checks a list of known, malicious links when users click links in Microsoft Office apps. URLs are not rewritten Click protection settings oChecked Track user clicks oUnchecked Let users click through the original URL 7. There is no recommendation for organization branding. 8. Click close To audit using PowerShell: 1. Connect using Connect-ExchangeOnline. 2. Run the following to output properties from all Safe Links policies: $params = @( 'Identity', 'EnableSafeLinksForEmail', 'EnableSafeLinksForTeams', 'EnableSafeLinksForOffice', 'TrackClicks', 'AllowClickThrough', 'ScanUrls', 'EnableForInternalSenders', 'DeliverMessageAfterScan', 'DisableUrlRewrite' ) Get-SafeLinksPolicy | Select-Object -Property $Params 3. Verify there is at least one policy that matches the properties and values below: Identity : <Example CIS SafeLinks Policy> EnableSafeLinksForEmail : True EnableSafeLinksForTeams : True EnableSafeLinksForOffice : True TrackClicks : True AllowClickThrough : False ScanUrls : True EnableForInternalSenders : True DeliverMessageAfterScan : True DisableUrlRewrite : False",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/safe-links-policies-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/powershell/module/exchange/set-safelinkspolicy?view=exchange-ps:https://learn.microsoft.com/en-us/defender-office-365/preset-security-policies?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.2",
+ "Description": "The Common Attachment Types Filter is a setting within Exchange Online Protection's anti-malware policy that blocks inbound and outbound email messages containing attachments of specified file types. When enabled, messages with attachments matching the blocked extensions are quarantined before delivery. Microsoft maintains a default set of file types considered high risk; organizations may also add custom extensions to the list. The recommended state is Enable the common attachments filter set to On, on the default anti-malware policy, with the default list of blocked file types.",
+ "Checks": [
+ "defender_malware_policy_common_attachments_filter_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The Common Attachment Types Filter is a setting within Exchange Online Protection's anti-malware policy that blocks inbound and outbound email messages containing attachments of specified file types. When enabled, messages with attachments matching the blocked extensions are quarantined before delivery. Microsoft maintains a default set of file types considered high risk; organizations may also add custom extensions to the list. The recommended state is Enable the common attachments filter set to On, on the default anti-malware policy, with the default list of blocked file types.",
+ "RationaleStatement": "Email is a primary delivery vector for malware, including ransomware, trojans, and remote access tools distributed via executable, script, and installer file formats. The Common Attachment Types Filter blocks delivery of file types that have no legitimate business use in email but are routinely weaponized (such as .exe, .vbs, .bat, .msi), and similar formats. Enforcing this filter at the gateway reduces the attack surface before any client-side or endpoint control has the opportunity to respond.",
+ "ImpactStatement": "Emails containing attachments with blocked extensions, including those sent by trusted internal senders, will be quarantined and not delivered. Some file types in the default block list may be used legitimately in some IT workflows. Administrators who need to permit specific extensions for specific users or groups should create a scoped custom anti-malware policy with a higher priority than the Default policy rather than modifying the Default policy's file type list.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under polices select Anti-malware and click on the Default (Default) policy. 5. On the Policy page that appears on the right hand pane scroll to the bottom and click on Edit protection settings, check the Enable the common attachments filter. o If any of the default file types are missing click Select file types and add the missing file types in. o Reference the Default Value section of this document for the list of extensions that should be blocked. 6. Click Save to save the changes. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following to enable the common attachment filter: Set-MalwareFilterPolicy -Identity Default -EnableFileFilter $true 3. Use Set-MalwareFilterPolicy -Identity Default with the -FileTypes parameter to add any missing file types from the default list. o FileTypes accepts an array of strings. o To avoid using it destructively, first retrieve the existing list of file types using Get-MalwareFilterPolicy and append any missing file types to the list before using Set-MalwareFilterPolicy to update the policy.",
+ "AuditProcedure": "Note: The following procedures audit only the Default anti-malware policy. Auditing custom policies is not required for compliance and is discretionary based on the organization's needs. To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under Policies select Anti-malware and click on the Default (Default) policy. 5. On the policy page that appears on the righthand pane, under Protection settings, verify that the Enable the common attachments filter has the value of On. 6. Click on Edit protection settings to view the list of file types that are blocked by the common attachment filter. Verify that the list of file types contains at least the 53 file types found in the Default Value section of this document. Note: Verifying the complete file type list via the UI requires manual comparison against the default extensions listed in the Default Value section of this document. Auditors who require a programmatic comparison should use the PowerShell method. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following Exchange Online PowerShell command: Get-MalwareFilterPolicy -Identity Default 3. Verify that the EnableFileFilter property has the value of True. 4. Verify that the FileTypes property contains at least default list of 53 file types found in the Default Value section of this document.",
+ "AdditionalInformation": "",
+ "DefaultValue": "EnableFileFilter : True Default extensions: [ \"ani\", \"apk\", \"app\", \"appx\", \"arj\", \"bat\", \"cab\", \"cmd\", \"com\", \"deb\", \"dex\", \"dll\", \"docm\", \"elf\", \"exe\", \"hta\", \"img\", \"iso\", \"jar\", \"jnlp\", \"kext\", \"lha\", \"lib\", \"library\", \"lnk\", \"lzh\", \"macho\", \"msc\", \"msi\", \"msix\", \"msp\", \"mst\", \"pif\", \"ppa\", \"ppam\", \"reg\", \"rev\", \"scf\", \"scr\", \"sct\", \"sys\", \"uif\", \"vb\", \"vbe\", \"vbs\", \"vxd\", \"wsc\", \"wsf\", \"wsh\", \"xll\", \"xz\", \"z\", \"ace\" ]",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/exchange/get-malwarefilterpolicy?view=exchange-ps:https://learn.microsoft.com/en-us/defender-office-365/anti-malware-policies-configure?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.3",
+ "Description": "Exchange Online Protection (EOP) is Microsoft's cloud-based filtering service that protects organizations against spam, malware, and other email threats. EOP is included in all Microsoft 365 organizations with Exchange Online mailboxes. EOP uses flexible anti-malware policies for malware protection settings. These policies can be set to notify Admins of malicious activity.",
+ "Checks": [
+ "defender_malware_policy_notifications_internal_users_malware_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Exchange Online Protection (EOP) is Microsoft's cloud-based filtering service that protects organizations against spam, malware, and other email threats. EOP is included in all Microsoft 365 organizations with Exchange Online mailboxes. EOP uses flexible anti-malware policies for malware protection settings. These policies can be set to notify Admins of malicious activity.",
+ "RationaleStatement": "This setting alerts administrators that an internal user sent a message that contained malware. This may indicate an account or machine compromise that would need to be investigated.",
+ "ImpactStatement": "Notification of account with potential issues should not have an impact on the user.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand E-mail & Collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under Policies select Anti-malware. 5. Click on the Default (Default) policy. 6. Click on Edit protection settings and change the settings for Notify an admin about undelivered messages from internal senders to On and enter the email address of the administrator who should be notified under Administrator email address. 7. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following command: Set-MalwareFilterPolicy -Identity '{Identity Name}' - EnableInternalSenderAdminNotifications $True -InternalSenderAdminAddress {admin@domain1.com} Note: Audit and Remediation guidance may focus on the Default policy however, if a Custom Policy exists in the organization's tenant, then ensure the setting is set as outlined in the highest priority policy listed.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand E-mail & Collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under Policies select Anti-malware. 5. Click on the Default (Default) policy. 6. Verify that Notify an admin about undelivered messages from internal senders is set to On and that there is at least one email address under Administrator email address. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following command: Get-MalwareFilterPolicy | fl Identity, EnableInternalSenderAdminNotifications, InternalSenderAdminAddress 3. Verify that EnableInternalSenderAdminNotifications is set to True and a InternalSenderAdminAddress address is defined. Note: Audit and Remediation guidance may focus on the Default policy however, if a Custom Policy exists in the organization's tenant, then ensure the setting is set as outlined in the highest priority policy listed.",
+ "AdditionalInformation": "",
+ "DefaultValue": "EnableInternalSenderAdminNotifications : False InternalSenderAdminAddress : $null",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/anti-malware-protection-about:https://learn.microsoft.com/en-us/defender-office-365/anti-malware-policies-configure"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.4",
+ "Description": "The Safe Attachments policy helps protect users from malware in email attachments by scanning attachments for viruses, malware, and other malicious content. When an email attachment is received by a user, Safe Attachments will scan the attachment in a secure environment and provide a verdict on whether the attachment is safe or not.",
+ "Checks": [
+ "defender_safe_attachments_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "The Safe Attachments policy helps protect users from malware in email attachments by scanning attachments for viruses, malware, and other malicious content. When an email attachment is received by a user, Safe Attachments will scan the attachment in a secure environment and provide a verdict on whether the attachment is safe or not.",
+ "RationaleStatement": "Enabling Safe Attachments policy helps protect against malware threats in email attachments by analyzing suspicious attachments in a secure, cloud-based environment before they are delivered to the user's inbox. This provides an additional layer of security and can prevent new or unseen types of malware from infiltrating the organization's network.",
+ "ImpactStatement": "Delivery of email with attachments may be delayed while scanning is occurring.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand E-mail & Collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under Policies select Safe Attachments. 5. Click + Create. 6. Create a Policy Name and Description, and then click Next. 7. Select all valid domains and click Next. 8. Select Block. 9. Quarantine policy is AdminOnlyAccessPolicy. 10. Leave Enable redirect unchecked. 11. Click Next and finally Submit. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. To change an existing policy modify the example below and run the following PowerShell command: Set-SafeAttachmentPolicy -Identity 'Example policy' -Action 'Block' - QuarantineTag 'AdminOnlyAccessPolicy' -Enable $true 3. Or, edit and run the below example to create a new safe attachments policy. New-SafeAttachmentPolicy -Name \"CIS 2.1.4\" -Enable $true -Action 'Block' - QuarantineTag 'AdminOnlyAccessPolicy' New-SafeAttachmentRule -Name \"CIS 2.1.4 Rule\" -SafeAttachmentPolicy \"CIS 2.1.4\" -RecipientDomainIs 'exampledomain[.]com' Note: Policy targets such as users and domains should include domains, or groups that provide coverage for a majority of users in the organization. Different inclusion and exclusion use cases are not covered in the benchmark.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand E-mail & Collaboration > Policies & rules. 3. On the Policies & rules page select Threat policies. 4. Under Policies select Safe Attachments. 5. Inspect the highest priority policy. 6. Verify that Users and domains and Included recipient domains are in scope for the organization. 7. Verify that Safe Attachments detection response: is set to Block - Block current and future messages and attachments with detected malware. 8. Verify that Quarantine Policy is set to AdminOnlyAccessPolicy. 9. Verify that the policy is not disabled. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-SafeAttachmentPolicy | ft Identity,Enable,Action,QuarantineTag 3. Inspect the highest priority safe attachments policy and ensure the properties and values match the below: Enable : True Action : Block QuarantineTag : AdminOnlyAccessPolicy Note: To view the priority for a policy the Get-SafeAttachmentRule must be used. Built-in policies will always have a priority of lowest while presets like strict and standard can be viewed with Get-ATPProtectionPolicyRule. Strict and standard presets always operate at a higher priority than custom policies.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Identity : Built-In Protection Policy Enable : True Action : Block QuarantineTag : AdminOnlyAccessPolicy Priority : (lowest)",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-about:https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-policies-configure"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.5",
+ "Description": "Safe Attachments for SharePoint, OneDrive, and Microsoft Teams scans these services for malicious files.",
+ "Checks": [
+ "defender_atp_safe_attachments_and_docs_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Safe Attachments for SharePoint, OneDrive, and Microsoft Teams scans these services for malicious files.",
+ "RationaleStatement": "Safe Attachments for SharePoint, OneDrive, and Microsoft Teams protect organizations from inadvertently sharing malicious files. When a malicious file is detected that file is blocked so that no one can open, copy, move, or share it until further actions are taken by the organization's security team.",
+ "ImpactStatement": "Impact associated with Safe Attachments is minimal, and equivalent to impact associated with anti-virus scanners in an environment.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com 2. Under Email & collaboration select Policies & rules 3. Select Threat policies then Safe Attachments. 4. Click on Global settings 5. Click to Enable Turn on Defender for Office 365 for SharePoint, OneDrive, and Microsoft Teams 6. Click to Enable Turn on Safe Documents for Office clients 7. Click to Disable Allow people to click through Protected View even if Safe Documents identified the file as malicious. 8. Click Save To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-AtpPolicyForO365 -EnableATPForSPOTeamsODB $true -EnableSafeDocs $true - AllowSafeDocsOpen $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Under Email & collaboration select Policies & rules. 3. Select Threat policies then Safe Attachments. 4. Click on Global settings. 5. Verify that the Turn on Defender for Office 365 for SharePoint, OneDrive, and Microsoft Teams toggle is set to Enabled. 6. Verify that the Turn on Safe Documents for Office clients toggle is set to Enabled. 7. Verify that the Allow people to click through Protected View even if Safe Documents identified the file as malicious toggle is set to Disabled. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-AtpPolicyForO365 | fl Name,EnableATPForSPOTeamsODB,EnableSafeDocs,AllowSafeDocsOpen Verify the values for each parameter as below: EnableATPForSPOTeamsODB : True EnableSafeDocs : True AllowSafeDocsOpen : False",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-for-spo-odfb-teams-about"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.6",
+ "Description": "In Microsoft 365 organizations with mailboxes in Exchange Online or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, email messages are automatically protected against spam (junk email) by EOP. Configure Exchange Online Spam Policies to copy emails and notify someone when a sender in the organization has been blocked for sending spam emails.",
+ "Checks": [
+ "defender_antispam_outbound_policy_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft 365 organizations with mailboxes in Exchange Online or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, email messages are automatically protected against spam (junk email) by EOP. Configure Exchange Online Spam Policies to copy emails and notify someone when a sender in the organization has been blocked for sending spam emails.",
+ "RationaleStatement": "A blocked account is a good indication that the account in question has been breached, and an attacker is using it to send spam emails to other people.",
+ "ImpactStatement": "Notification of users that have been blocked should not cause an impact to the user.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules> Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Anti-spam outbound policy (default). 5. Select Edit protection settings then under Notifications: 6. Check Send a copy of suspicious outbound messages or message that exceed these limits to these users and groups then enter the desired email addresses. 7. Check Notify these users and groups if a sender is blocked due to sending outbound spam then enter the desired email addresses. 8. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: $BccEmailAddress = @(\"<INSERT-EMAIL>\") $NotifyEmailAddress = @(\"<INSERT-EMAIL>\") Set-HostedOutboundSpamFilterPolicy -Identity Default - BccSuspiciousOutboundAdditionalRecipients $BccEmailAddress - BccSuspiciousOutboundMail $true -NotifyOutboundSpam $true - NotifyOutboundSpamRecipients $NotifyEmailAddress Note: Audit and Remediation guidance may focus on the Default policy however, if a Custom Policy exists in the organization's tenant, then ensure the setting is set as outlined in the highest priority policy listed.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Anti-spam outbound policy (default). 5. Verify that Send a copy of suspicious outbound messages or message that exceed these limits to these users and groups is set to On, ensure the email address is correct. 6. Verify that Notify these users and groups if a sender is blocked due to sending outbound spam is set to On, ensure the email address is correct. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-HostedOutboundSpamFilterPolicy | Select-Object Bcc*, Notify* 3. Verify both BccSuspiciousOutboundMail and NotifyOutboundSpam are set to True and the email addresses to be notified are correct. Note: Audit and Remediation guidance may focus on the Default policy however, if a Custom Policy exists in the organization's tenant, then ensure the setting is set as outlined in the highest priority policy listed.",
+ "AdditionalInformation": "",
+ "DefaultValue": "BccSuspiciousOutboundAdditionalRecipients : {} BccSuspiciousOutboundMail : False NotifyOutboundSpamRecipients : {} NotifyOutboundSpam : False",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/outbound-spam-protection-about"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.7",
+ "Description": "By default, Office 365 includes built-in features that help protect users from phishing attacks. Set up anti-phishing polices to increase this protection, for example by refining settings to better detect and prevent impersonation and spoofing attacks. The default policy applies to all users within the organization and is a single view to fine-tune anti- phishing protection. Custom policies can be created and configured for specific users, groups or domains within the organization and will take precedence over the default policy for the scoped users.",
+ "Checks": [
+ "defender_antiphishing_policy_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "By default, Office 365 includes built-in features that help protect users from phishing attacks. Set up anti-phishing polices to increase this protection, for example by refining settings to better detect and prevent impersonation and spoofing attacks. The default policy applies to all users within the organization and is a single view to fine-tune anti- phishing protection. Custom policies can be created and configured for specific users, groups or domains within the organization and will take precedence over the default policy for the scoped users.",
+ "RationaleStatement": "Protects users from phishing attacks (like impersonation and spoofing) and uses safety tips to warn users about potentially harmful messages.",
+ "ImpactStatement": "Mailboxes that are used for support systems such as helpdesk and billing systems send mail to internal users and are often not suitable candidates for impersonation protection. Care should be taken to ensure that these systems are excluded from Impersonation Protection.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules 3. Select Threat policies. 4. Under Policies select Anti-phishing and click Create. 5. Name the policy, continuing and clicking Next as needed: o Add Groups and/or Domains that contain a majority of the organization. o Set Phishing email threshold to 3 - More Aggressive o Check Enable users to protect and add up to 350 users o Check Enable domains to protect and check Include domains I own o Check Enable mailbox intelligence (Recommended) o Check Enable Intelligence for impersonation protection (Recommended) o Check Enable spoof intelligence (Recommended) 6. Under Actions configure the following: o Set If a message is detected as user impersonation to Quarantine the message o Set If a message is detected as domain impersonation to Quarantine the message o Set If Mailbox Intelligence detects an impersonated user to Quarantine the message o Leave Honor DMARC record policy when the message is detected as spoof checked. o Check Show first contact safety tip (Recommended) o Check Show user impersonation safety tip o Check Show domain impersonation safety tip o Check Show user impersonation unusual characters safety tip 7. Finally, click Next and Submit the policy. Note: DefaultFullAccessWithNotificationPolicy is suggested but not required. Users will be notified that impersonation emails are in the Quarantine. To remediate using PowerShell: 1. Connect to Exchange Online service using Connect-ExchangeOnline. 2. Run the following Exchange Online PowerShell script to create an AntiPhish policy: # Create the Policy $params = @{ Name = \"CIS AntiPhish Policy\" PhishThresholdLevel = 3 EnableTargetedUserProtection = $true EnableOrganizationDomainsProtection = $true EnableMailboxIntelligence = $true EnableMailboxIntelligenceProtection = $true EnableSpoofIntelligence = $true TargetedUserProtectionAction = 'Quarantine' TargetedDomainProtectionAction = 'Quarantine' MailboxIntelligenceProtectionAction = 'Quarantine' TargetedUserQuarantineTag = 'DefaultFullAccessWithNotificationPolicy' MailboxIntelligenceQuarantineTag = 'DefaultFullAccessWithNotificationPolicy' TargetedDomainQuarantineTag = 'DefaultFullAccessWithNotificationPolicy' EnableFirstContactSafetyTips = $true EnableSimilarUsersSafetyTips = $true EnableSimilarDomainsSafetyTips = $true EnableUnusualCharactersSafetyTips = $true HonorDmarcPolicy = $true } New-AntiPhishPolicy @params # Create the rule for all users in all valid domains and associate with Policy New-AntiPhishRule -Name $params.Name -AntiPhishPolicy $params.Name - RecipientDomainIs (Get-AcceptedDomain).Name -Priority 0 3. The new policy can be edited in the UI or via PowerShell. Note: Remediation guidance is intended to help create a qualifying AntiPhish policy that meets the recommended criteria while protecting the majority of the organization. It's understood some individual user exceptions may exist or exceptions for the entire policy if another product acts as a similar control.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules 3. Select Threat policies. 4. Under Policies select Anti-phishing. 5. Verify an AntiPhish policy exists that is On and meets the following criteria: 6. Under Users, groups, and domains o Verify that the included domains and groups includes a majority of the organization. 7. Under Phishing threshold & protection verify the following: o Phishing email threshold is at least 3 - More Aggressive. o User impersonation protection is On and contains a subset of users. o Domain impersonation protection is On for owned domains. o Mailbox intelligence and Mailbox intelligence for impersonations and Spoof intelligence are On. 8. Under Actions verify the following: o If a message is detected as user impersonation is set to Quarantine the message. o If a message is detected as domain impersonation is set to Quarantine the message. o If Mailbox Intelligence detects an impersonated user is set to Quarantine the message. o First contact safety tip is On. o User impersonation safety tip is On. o Domain impersonation safety tip is On. o Unusual characters safety tip is On. o Honor DMARC record policy when the message is detected as spoof is On. Note: DefaultFullAccessWithNotificationPolicy is suggested but not required. Users will be notified that impersonation emails are in the Quarantine. To audit using PowerShell: 1. Connect to Exchange Online service using Connect-ExchangeOnline. 2. Run the following Exchange Online PowerShell commands: $params = @( \"name\",\"Enabled\",\"PhishThresholdLevel\",\"EnableTargetedUserProtection\" \"EnableOrganizationDomainsProtection\",\"EnableMailboxIntelligence\" \"EnableMailboxIntelligenceProtection\",\"EnableSpoofIntelligence\" \"TargetedUserProtectionAction\",\"TargetedDomainProtectionAction\" \"MailboxIntelligenceProtectionAction\",\"EnableFirstContactSafetyTips\" \"EnableSimilarUsersSafetyTips\",\"EnableSimilarDomainsSafetyTips\" \"EnableUnusualCharactersSafetyTips\",\"TargetedUsersToProtect\" \"HonorDmarcPolicy\" ) Get-AntiPhishPolicy | fl $params 3. Verify there is a policy created that has matching values for the following parameters: Enabled : True PhishThresholdLevel : 3 EnableTargetedUserProtection : True EnableOrganizationDomainsProtection : True EnableMailboxIntelligence : True EnableMailboxIntelligenceProtection : True EnableSpoofIntelligence : True TargetedUserProtectionAction : Quarantine TargetedDomainProtectionAction : Quarantine MailboxIntelligenceProtectionAction : Quarantine EnableFirstContactSafetyTips : True EnableSimilarUsersSafetyTips : True EnableSimilarDomainsSafetyTips : True EnableUnusualCharactersSafetyTips : True TargetedUsersToProtect : {<contains users>} HonorDmarcPolicy : True 4. Verify that TargetedUsersToProtect contains a subset of the organization, up to 350 users, for targeted Impersonation Protection. 5. Use PowerShell to verify the AntiPhishRule is configured and enabled. Get-AntiPhishRule | ft AntiPhishPolicy,Priority,State,SentToMemberOf,RecipientDomainIs 6. Identity correct rule from the matching AntiPhishPolicy name in step 3. Ensure the rule defines groups or domains that include the majority of the organization by inspecting SentToMemberOf or RecipientDomainIs. Note: Audit guidance is intended to help identify a qualifying AntiPhish policy+rule that meets the recommended criteria while protecting the majority of the organization. It's understood some individual user exceptions may exist or exceptions for the entire policy if another product stands in as an equivalent control.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/anti-phishing-protection-about:https://learn.microsoft.com/en-us/defender-office-365/anti-phishing-policies-eop-configure"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.8",
+ "Description": "For each domain that is configured in Exchange, a corresponding Sender Policy Framework (SPF) record should be created.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "For each domain that is configured in Exchange, a corresponding Sender Policy Framework (SPF) record should be created.",
+ "RationaleStatement": "SPF records enable Exchange Online Protection and other mail systems to verify which servers are authorized to send email for a domain. This helps those systems determine whether a message is legitimate or potentially spoofed. Enforcing a -all or ~all ensures that any undocumented or unauthorized networks attempting to send on behalf of the organization are immediately rejected, reducing the risk of impersonation. If an organization does not have full visibility into where its email originates, this represents a significant security gap. For example, if an email server is sending mail from an unexpected location across the country without your knowledge, that is a serious issue. Addressing this requires a deliberate discovery process to identify all legitimate sending sources, rather than allowing unknown systems to continue sending email unchecked.",
+ "ImpactStatement": "Setting up SPF records typically has minimal operational impact. However, organizations must ensure proper configuration, as misconfigured SPF records can cause legitimate email to be flagged as spam or fail authentication checks. Additionally, identifying all legitimate senders outside of the default Microsoft 365 IP ranges may require extra time and coordination during the discovery phase.",
+ "RemediationProcedure": "To remediate using a DNS provider: For each domain identified as non-compliant during the audit, make the necessary updates in your DNS provider or through your third-party SPF management service. Missing SPF Record: If a domain does not currently have an SPF record, create one similar to the example below, assuming all email is routed through Exchange Online (Microsoft 365 or Microsoft 365 GCC): # Hard fail v=spf1 include:spf.protection.outlook.com -all # Soft fail v=spf1 include:spf.protection.outlook.com ~all Additional Senders: If other authorized email services are used, add their SPF entries using the include: mechanism as needed. For example: v=spf1 include:spf.protection.outlook.com include:exampledomain.net -all",
+ "AuditProcedure": "STEP 1: Determine the list of domains to audit Using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Expand Settings > Domains. 3. Take note of all custom domains and subdomains defined. o Exclude the (MOERA) domain *.onmicrosoft.com o Exclude the coexistence domain *.mail.onmicrosoft.com (if shown). 4. Use this list of domains in the audit procedure. Using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following: Get-AcceptedDomain | Where-Object {$_.IsCoExistenceDomain -eq $false -and $_.InitialDomain -eq $false} 3. Use this list in the audit procedure. Note: Microsoft owns the tenant's organizational level *.onmicrosoft.com domains, so it is not necessary to create SPF records for the initial (MOERA) or the coexistence (hybrid) domain. STEP 2: Perform the Audit using PowerShell: 1. Open a PowerShell prompt. 2. Run the following for each custom domain identified in Step 1 that sends email from Exchange Online: Resolve-DnsName domain1.com -Type TXT | fl Ensure the following criteria are met: 1. A valid TXT record must begin with v=spf1, which indicates it is SPF v1 (the current standard). 2. The record must be either directly or indirectly managed: o An indirectly managed record uses a modifier like redirect=[domain], which allows centralized SPF management by a trusted vendor. 3. The record must end with a hard or soft fail policy: o The record must end with: -all or ~all, allowing for a hard fail or soft fail. o If the SPF record uses the redirect= modifier, the redirected SPF record must terminate with a compliant qualifier (not the parent). This will require repeating the DNS lookup against the redirected domain. o Other qualifiers not listed are not compliant as an end state. Parked domains: Ensure that any domain not used for sending email has an SPF record explicitly indicating that no mail is authorized from that domain, using v=spf1 - all. Below are examples of SPF records that are compliant. The audit does not evaluate specific include domains for compliant states. v=spf1 include:spf.protection.outlook.com -all v=spf1 include:spf.protection.outlook.com ~all # GCC High or DoD example v=spf1 include:exampledomain.net include:spf.protection.office365.us ~all # 21Vianet v=spf1 include:spf.protection.partner.outlook.cn ~all # Parked domains v=spf1 -all Note: Resolve-DnsName is not available on versions of Windows earlier than Windows 8 and Windows Server 2012. Use alternatives such as nslookup when needed.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/email-authentication-spf-configure?view=o365-worldwide:https://datatracker.ietf.org/doc/html/rfc7208:https://learn.microsoft.com/en-us/defender-office-365/email-authentication-spf-configure?view=o365-worldwide#scenario-parked-domains"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.9",
+ "Description": "DKIM is one of the trio of Authentication methods (SPF, DKIM and DMARC) that help prevent attackers from sending messages that look like they come from your domain. DKIM lets an organization add a digital signature to outbound email messages in the message header. When DKIM is configured, the organization authorizes it's domain to associate, or sign, it's name to an email message using cryptographic authentication. Email systems that get email from this domain can use a digital signature to help verify whether incoming email is legitimate. Use of DKIM in addition to SPF and DMARC to help prevent malicious actors using spoofing techniques from sending messages that look like they are coming from your domain.",
+ "Checks": [
+ "defender_domain_dkim_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "DKIM is one of the trio of Authentication methods (SPF, DKIM and DMARC) that help prevent attackers from sending messages that look like they come from your domain. DKIM lets an organization add a digital signature to outbound email messages in the message header. When DKIM is configured, the organization authorizes it's domain to associate, or sign, it's name to an email message using cryptographic authentication. Email systems that get email from this domain can use a digital signature to help verify whether incoming email is legitimate. Use of DKIM in addition to SPF and DMARC to help prevent malicious actors using spoofing techniques from sending messages that look like they are coming from your domain.",
+ "RationaleStatement": "By enabling DKIM with Office 365, messages that are sent from Exchange Online will be cryptographically signed. This will allow the receiving email system to validate that the messages were generated by a server that the organization authorized and not being spoofed.",
+ "ImpactStatement": "There should be no impact of setting up DKIM however, organizations should ensure appropriate setup to ensure continuous mail-flow.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Rules section click Email authentication settings. 4. Select DKIM 5. Select the domain to remediate. 6. Click Create DKIM keys. 7. Microsoft provides the properly formatted CNAME records, copy these for later use. 8. In another browser tab or window, go to the domain registrar for the domain, and then create the two CNAME records using the information from the previous step. 9. Return the domain properties flyout and toggle Sign messages for this domain with DKIM signatures to Enabled. If successful the status will show Signing DKIM signatures for this domain.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Rules section click Email authentication settings. 4. Select DKIM. 5. For each Accepted domain that is configured to send email: o Skip any *.onmicrosoft.com domain (MOERA or Coexistence), these outbound messages are automatically signed by Microsoft. o Click on the domain name. o Confirm Sign messages for this domain with DKIM signatures is Enabled. o Ensure Status reads Signing DKIM signatures for this domain. 6. A status of Not signing DKIM signatures for this domain or No DKIM keys saved for this domain is out of compliance. Note: For step 5 these can also be audited the overview showing all domains. In this case a passing audit procedure will display the Toggle set as Enabled and Status as Valid. To audit using PowerShell: 1. Connect to Exchange Online service using Connect-ExchangeOnline. 2. Run the following: # Get-DkimSigningConfig does not display unconfigured domains, # so we first get all accepted domains and then match them against # the DKIM signing configurations. $Domains = Get-AcceptedDomain | Where-Object {$_.IsCoExistenceDomain -eq $false -and $_.InitialDomain -eq $false} $DKIMCfg = Get-DkimSigningConfig # Generate the report $Report = foreach ($Domain in $Domains) { $DKIM = $DKIMCfg | Where-Object { $_.Name -eq $Domain.Name } [PSCustomObject]@{ DomainName = $Domain.Name Enabled = [bool]$DKIM.Enabled Status = if ($DKIM) { $DKIM.Status } else { \"Not Configured\" } IsCISCompliant = ($DKIM.Enabled -and $DKIM.Status -eq \"Valid\") } } # Output the report $Report | Format-Table -AutoSize # Optionally, export the report to a CSV file # $Report | Export-Csv -Path \"2_1_9.csv\" -NoTypeInformation 3. For each domain that is configured to send email verify: o Enabled is True o Status is Valid. o Note: The property IsCISCompliant will also validate whether the state is compliant. Note: If you own registered domains that aren't used for email or anything at all (also known as parked domains), don't publish DKIM records for those domains. The lack of a DKIM record (hence, the lack of a public key in DNS to validate the message signature) prevents DKIM validation of forged domains.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Custom domains: Not configured by default MOERA onmicrosoft.com domain: Outbound email is automatically signed",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/email-authentication-dkim-configure?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.10",
+ "Description": "DMARC, or Domain-based Message Authentication, Reporting, and Conformance, assists recipient mail systems in determining the appropriate action to take when messages from a domain fail to meet SPF or DKIM authentication criteria.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "DMARC, or Domain-based Message Authentication, Reporting, and Conformance, assists recipient mail systems in determining the appropriate action to take when messages from a domain fail to meet SPF or DKIM authentication criteria.",
+ "RationaleStatement": "DMARC strengthens the trustworthiness of messages sent from an organization's domain to destination email systems. When combined with SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail), DMARC significantly enhances defenses against email spoofing and phishing attempts. This includes the MOERA domain (e.g., contoso.onmicrosoft.com), which is provisioned with every Microsoft 365 tenant and is capable of originating email. Because it is often overlooked in favor of custom domains, it represents a common gap in email authentication coverage if left unprotected. Leaving a DMARC policy set to p=none can result in the mail system taking no action when a spear-phishing email fails DMARC but passes SPF and DKIM checks. Having DMARC fully configured is a critical part of preventing business email compromise.",
+ "ImpactStatement": "The remediation portion can take time to implement and involves a multi-staged approach over time. First, a baseline of the current state of email will be established with p=none and rua and ruf. Once the environment is better understood and reports have been analyzed, an organization will move to the final state with DMARC record values as outlined in the audit section.",
+ "RemediationProcedure": "To remediate using a DNS provider: 1. For any out of compliance domain sending email, add the following record to DNS: Record: _dmarc.domain1.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:<rua-report@example.com>; ruf=mailto:<ruf-report@example.com> 2. This will create a basic DMARC policy that will allow the organization to start monitoring message statistics. 3. One week is enough time for data generated by the reports to be useful in understanding email trends and traffic. The final step requires implementing a policy of p=reject OR p=quarantine and pct=100 with the necessary rua and ruf email addresses defined: Record: _dmarc.domain1.com Type: TXT Value: v=DMARC1; p=reject; pct=100; rua=mailto:<rua-report@example.com>; ruf=mailto:<ruf-report@example.com> Parked Domains: For any domain not used for sending email, add the following record to DNS: Record: _dmarc.domain1.com Type: TXT Value: v=DMARC1; p=reject; To remediate the MOERA domain using the UI: 1. Navigate to the Microsoft 365 admin center https://admin.microsoft.com/ 2. Expand Settings and select Domains. 3. Select your tenant domain (for example, contoso.onmicrosoft.com). 4. Select DNS records and click + Add record. 5. Add a new record with the TXT name of _dmarc with the appropriate values outlined above.",
+ "AuditProcedure": "STEP 1: Determine the list of domains to audit Using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com 2. Expand Settings > Domains. 3. Take note of all custom domains and subdomains defined. o Exclude the coexistence domain *.mail.onmicrosoft.com (if shown). 4. Include the MOERA domain: [tenant].onmicrosoft.com 5. Use this list of domains in the audit procedure. Using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following: Get-AcceptedDomain | Where-Object {$_.IsCoExistenceDomain -eq $false} 3. Use this list in the audit procedure. STEP 2: Perform the Audit using PowerShell: Note: Resolve-DnsName is not available on versions of Windows earlier than Windows 8 and Windows Server 2012. Use alternatives such as nslookup when needed. 1. Open a PowerShell prompt. 2. Run the following for each domain identified in Step 1: Resolve-DnsName _dmarc.domain1.com -Type TXT 3. Ensure the following criteria are met: 1. The record must be either directly or indirectly managed: - An indirectly managed record would use a CNAME to point to another record. - If the record is managed indirectly then that record must meet all criteria. This would require an additional DNS lookup. 2. The version v tag value must be v=DMARC1, which identifies it as a DMARC record. 3. The policy p tag value is p=quarantine OR p=reject. 4. The sampling rate pct tag value is pct=100 or does not exist. (A non- existent pct tag indicates sampling is 100 percent) 5. The aggregate data rua tag value is configured, i.e. rua=mailto:<reporting email address>. 6. The failure data ruf tag value is configured, i.e. ruf=mailto:<reporting email address>. 4. Subdomain considerations o When subdomains of the organizational domain are in scope, DMARC policy is determined using a two-step record discovery process (RFC 7489, Section 6.6.3): 1. If the subdomain has its own valid DMARC record (i.e., a record that includes the required p= tag), only that record is used. Nothing is inherited from the organizational domain. Any tags not explicitly defined in the subdomain's record fall back to their RFC- defined default values. 2. If the subdomain does not have a valid DMARC record - either because no record exists or because the record is malformed (e.g., missing the required p= tag) - the organizational domain's record is used. When determining policy disposition, the sp= (subdomain policy) tag is applied if present; otherwise, the p= tag is used. o This fallback is record discovery, not per-tag inheritance. The lookup always falls back to the organizational domain directly. Intermediate parent subdomains are never consulted. o The sp= tag is only meaningful when set on the organizational domain's record and is ignored on subdomain records. 5. Compliance is met when each domain and subdomain meets the requirements in steps 3 and 4. Parked Domains: Ensure that any domain not used for sending email has a DMARC record explicitly indicating that no mail is authorized from that domain. 1. The version v tag value must be v=DMARC1, which identifies it as a DMARC record. 2. The policy p tag value is p=reject. The following example records would pass as they contain a policy that would either quarantine or reject messages failing DMARC, and the policy affects 100% of mail pct=100 as well as containing valid reporting and aggregate addresses: v=DMARC1; p=reject; pct=100; rua=mailto:rua@example.com; ruf=mailto:ruf@example.com; fo=1 v=DMARC1; p=reject; rua=mailto:rua@example.com; ruf=mailto:ruf@example.com; fo=1 v=DMARC1; p=quarantine; pct=100; sp=none; fo=1; ri=3600; rua=mailto:rua@example.com; ruf=mailto:ruf@example.com; # Parked domains v=DMARC1; p=reject; Note: The third example includes sp=none, which sets the subdomain policy to monitor- only. While the organizational domain itself would be compliant, any subdomains would not meet the audit criteria if they exist. Auditors must evaluate subdomains separately to confirm compliance.",
+ "AdditionalInformation": "Microsoft has a list of best practices for implementing DMARC that cover these steps in detail.",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/email-authentication-dmarc-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/how-to-enable-dmarc-reporting-for-microsoft-online-email-routing-address-moera-and-parked-domains?view=o365-worldwide:https://media.defense.gov/2024/May/02/2003455483/-1/-1/0/CSA-NORTH-KOREAN-ACTORS-EXPLOIT-WEAK-DMARC.PDF:https://www.rfc-editor.org/rfc/rfc7489"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.11",
+ "Description": "The Common Attachment Types Filter lets a user block known and custom malicious file types from being attached to emails. The policy provided by Microsoft covers 53 extensions, and an additional custom list of extensions can be defined. The list of 186 extensions provided in this recommendation is comprehensive but not exhaustive.",
+ "Checks": [
+ "defender_malware_policy_comprehensive_attachments_filter_applied"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "The Common Attachment Types Filter lets a user block known and custom malicious file types from being attached to emails. The policy provided by Microsoft covers 53 extensions, and an additional custom list of extensions can be defined. The list of 186 extensions provided in this recommendation is comprehensive but not exhaustive.",
+ "RationaleStatement": "Blocking known malicious file types can help prevent malware-infested files from infecting a host or performing other malicious attacks such as phishing and data extraction. Defining a comprehensive list of attachments can help protect against additional unknown and known threats. Many legacy file formats, binary files and compressed files have been used as delivery mechanisms for malicious software. Organizations can protect themselves from Business E-mail Compromise (BEC) by allow-listing only the file types relevant to their line of business and blocking all others.",
+ "ImpactStatement": "For file types that are business necessary users will need to use other organizationally approved methods to transfer blocked extension types between business partners.",
+ "RemediationProcedure": "To Remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following script after editing InternalSenderAdminAddress: # Create an attachment policy and associated rule. The rule is # intentionally disabled allowing the org to enable it when ready $Policy = @{ Name = \"CIS L2 Attachment Policy\" EnableFileFilter = $true ZapEnabled = $true EnableInternalSenderAdminNotifications = $true InternalSenderAdminAddress = 'admin@contoso.com' # Change this. } $L2Extensions = @( \"7z\", \"a3x\", \"ace\", \"ade\", \"adp\", \"ani\", \"app\", \"appinstaller\", \"applescript\", \"application\", \"appref-ms\", \"appx\", \"appxbundle\", \"arj\", \"asd\", \"asx\", \"bas\", \"bat\", \"bgi\", \"bz2\", \"cab\", \"chm\", \"cmd\", \"com\", \"cpl\", \"crt\", \"cs\", \"csh\", \"daa\", \"dbf\", \"dcr\", \"deb\", \"desktopthemepackfile\", \"dex\", \"diagcab\", \"dif\", \"dir\", \"dll\", \"dmg\", \"doc\", \"docm\", \"dot\", \"dotm\", \"elf\", \"eml\", \"exe\", \"fxp\", \"gadget\", \"gz\", \"hlp\", \"hta\", \"htc\", \"htm\", \"html\", \"hwpx\", \"ics\", \"img\", \"inf\", \"ins\", \"iqy\", \"iso\", \"isp\", \"jar\", \"jnlp\", \"js\", \"jse\", \"kext\", \"ksh\", \"lha\", \"lib\", \"library-ms\", \"lnk\", \"lzh\", \"macho\", \"mam\", \"mda\", \"mdb\", \"mde\", \"mdt\", \"mdw\", \"mdz\", \"mht\", \"mhtml\", \"mof\", \"msc\", \"msi\", \"msix\", \"msp\", \"msrcincident\", \"mst\", \"ocx\", \"odt\", \"ops\", \"oxps\", \"pcd\", \"pif\", \"plg\", \"pot\", \"potm\", \"ppa\", \"ppam\", \"ppkg\", \"pps\", \"ppsm\", \"ppt\", \"pptm\", \"prf\", \"prg\", \"ps1\", \"ps11\", \"ps11xml\", \"ps1xml\", \"ps2\", \"ps2xml\", \"psc1\", \"psc2\", \"pub\", \"py\", \"pyc\", \"pyo\", \"pyw\", \"pyz\", \"pyzw\", \"rar\", \"reg\", \"rev\", \"rtf\", \"scf\", \"scpt\", \"scr\", \"sct\", \"searchConnector-ms\", \"service\", \"settingcontent-ms\", \"sh\", \"shb\", \"shs\", \"shtm\", \"shtml\", \"sldm\", \"slk\", \"so\", \"spl\", \"stm\", \"svg\", \"swf\", \"sys\", \"tar\", \"theme\", \"themepack\", \"timer\", \"uif\", \"url\", \"uue\", \"vb\", \"vbe\", \"vbs\", \"vhd\", \"vhdx\", \"vxd\", \"wbk\", \"website\", \"wim\", \"wiz\", \"ws\", \"wsc\", \"wsf\", \"wsh\", \"xla\", \"xlam\", \"xlc\", \"xll\", \"xlm\", \"xls\", \"xlsb\", \"xlsm\", \"xlt\", \"xltm\", \"xlw\", \"xnk\", \"xps\", \"xsl\", \"xz\", \"z\" ) # Create the policy New-MalwareFilterPolicy @Policy -FileTypes $L2Extensions # Create the rule for all accepted domains $Rule = @{ Name = $Policy.Name Enabled = $false MalwareFilterPolicy = $Policy.Name RecipientDomainIs = (Get-AcceptedDomain).Name Priority = 0 } New-MalwareFilterRule @Rule 3. When prepared enable the rule either through the UI or PowerShell. Note: Due to the number of extensions the UI method is not covered. The objects can however be edited in the UI or manually added using the list from the script. 1. Navigate to Microsoft Defender at https://security.microsoft.com/ 2. Browse to Policies & rules > Threat policies > Anti-malware.",
+ "AuditProcedure": "For this control, a Level 2 comprehensive attachment policy is defined as one that includes at least 120 extensions. The 184 extensions included are a known vector for malicious activity. To pass, organizations must demonstrate at least a 90% adoption rate of the extension list referenced in the script below, with allowances for justified exceptions. Since individual extensions are not assigned specific risk weights, exceptions should be based on documented business needs. Note: Utilizing the UI for auditing Anti-malware policies can be very time consuming so it is recommended to use a script like the one supplied below. To Audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following script: $AttachExts = @( '7z', 'a3x', 'ace', 'ade', 'adp', 'ani', 'apk', 'app', 'appinstaller', 'applescript', 'application', 'appref-ms', 'appx', 'appxbundle', 'arj', 'asd', 'asx', 'bas', 'bat', 'bgi', 'bz2', 'cab', 'chm', 'cmd', 'com', 'cpl', 'crt', 'cs', 'csh', 'daa', 'dbf', 'dcr', 'deb', 'desktopthemepackfile', 'dex', 'diagcab', 'dif', 'dir', 'dll', 'dmg', 'doc', 'docm', 'dot', 'dotm', 'elf', 'eml', 'exe', 'fxp', 'gadget', 'gz', 'hlp', 'hta', 'htc', 'htm', 'html', 'hwpx', 'ics', 'img', 'inf', 'ins', 'iqy', 'iso', 'isp', 'jar', 'jnlp', 'js', 'jse', 'kext', 'ksh', 'lha', 'lib', 'library', 'library-ms', 'lnk', 'lzh', 'macho', 'mam', 'mda', 'mdb', 'mde', 'mdt', 'mdw', 'mdz', 'mht', 'mhtml', 'mof', 'msc', 'msi', 'msix', 'msp', 'msrcincident', 'mst', 'ocx', 'odt', 'ops', 'oxps', 'pcd', 'pif', 'plg', 'pot', 'potm', 'ppa', 'ppam', 'ppkg', 'pps', 'ppsm', 'ppt', 'pptm', 'prf', 'prg', 'ps1', 'ps11', 'ps11xml', 'ps1xml', 'ps2', 'ps2xml', 'psc1', 'psc2', 'pub', 'py', 'pyc', 'pyo', 'pyw', 'pyz', 'pyzw', 'rar', 'reg', 'rev', 'rtf', 'scf', 'scpt', 'scr', 'sct', 'searchConnector-ms', 'service', 'settingcontent-ms', 'sh', 'shb', 'shs', 'shtm', 'shtml', 'sldm', 'slk', 'so', 'spl', 'stm', 'svg', 'swf', 'sys', 'tar', 'theme', 'themepack', 'timer', 'uif', 'url', 'uue', 'vb', 'vbe', 'vbs', 'vhd', 'vhdx', 'vxd', 'wbk', 'website', 'wim', 'wiz', 'ws', 'wsc', 'wsf', 'wsh', 'xla', 'xlam', 'xlc', 'xll', 'xlm', 'xls', 'xlsb', 'xlsm', 'xlt', 'xltm', 'xlw', 'xnk', 'xps', 'xsl', 'xz', 'z' ) $MalwareFilterPolicies = Get-MalwareFilterPolicy $MalwareFilterRules = Get-MalwareFilterRule # A policy must have at least 90% of the extensions in the reference list to pass. # This allows for some flexibility with exceptions. $PassingValue = .90 # 90% $FailThreshold = [int]($AttachExts.count * (1 - $PassingValue)) # Only evaluate policies that have more than 120 extensions defined # so we don't output failures on policies that aren't specific to # extension filtering. $CompPolicies = $MalwareFilterPolicies | Where-Object { $_.FileTypes.Count - gt 120 } if (-not $CompPolicies) { Write-Output \"## FAIL ## No comprehensive policies found to evaluate.\" return } $ExtensionReport = foreach ($policy in $CompPolicies) { $Missing = Compare-Object -ReferenceObject $AttachExts ` -DifferenceObject $policy.FileTypes ` -PassThru | Where-Object { $_.SideIndicator -eq '<=' } $FoundRule = $MalwareFilterRules | Where-Object { $_.MalwareFilterPolicy -eq $policy.Id } # Define passing conditions to determine if this policy passes all checks. $Pass = ($Missing.Count -lt $FailThreshold) -and ($FoundRule.State -eq 'Enabled') -and ($policy.EnableFileFilter -eq $true) [PSCustomObject]@{ PolicyName = $policy.Identity IsCISCompliant = $Pass EnableFileFilter = $policy.EnableFileFilter State = $FoundRule.State MissingCount = $Missing.count MissingExtensions = $Missing -join \", \" ExtensionCount = $policy.FileTypes.count } } # Output results in various formats $ExtensionReport | Format-Table -AutoSize <# Optional: Export methods $ExtensionReport | Out-GridView -Title \"Attachment Filter results\" $ExtensionReport | Export-Csv -Path \"2.1.11.csv\" -NoTypeInformation $ExtensionReport | ConvertTo-Json | Out-File -FilePath \"2.1.11.json\" #> 3. Review the results, only policies with over 120 extensions defined will be evaluated. At the end of the script examples of different output formats are given. 4. A pass is given for the following conditions: o A single active policy exists that covers all file extensions listed except those defined as an exception by the organization. o The policy has a state of Enabled. o The EnableFileFilter property is set to True. 5. The report includes a IsCISCompliant property, where True indicates in compliance, allowing for up to 10% of the listed extensions to be missing as documented exceptions. Note: Organizations should evaluate any extensions missing from the report to determine if they are valid exceptions. Note: The audit procedure intentionally does not include the action taken for matched extensions, e.g. Reject with NDR or Quarantine the message. These are considered organization specific and are not scored. When FileTypeAction is not specified the action will default to Reject the message with a non-delivery receipt (NDR). The Quarantine Policy is also considered organization specific.",
+ "AdditionalInformation": "",
+ "DefaultValue": "The following extensions are blocked by default: ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/exchange/get-malwarefilterpolicy?view=exchange-ps:https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-malware-policies-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/office/compatibility/office-file-format-reference"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_malware_policy_comprehensive_attachments_filter_applied",
+ "ConfigKey": "recommended_blocked_file_types",
+ "Operator": "superset",
+ "Value": [
+ "ace",
+ "ani",
+ "apk",
+ "app",
+ "appx",
+ "arj",
+ "bat",
+ "cab",
+ "cmd",
+ "com",
+ "deb",
+ "dex",
+ "dll",
+ "docm",
+ "elf",
+ "exe",
+ "hta",
+ "img",
+ "iso",
+ "jar",
+ "jnlp",
+ "kext",
+ "lha",
+ "lib",
+ "library",
+ "lnk",
+ "lzh",
+ "macho",
+ "msc",
+ "msi",
+ "msix",
+ "msp",
+ "mst",
+ "pif",
+ "ppa",
+ "ppam",
+ "reg",
+ "rev",
+ "scf",
+ "scr",
+ "sct",
+ "sys",
+ "uif",
+ "vb",
+ "vbe",
+ "vbs",
+ "vxd",
+ "wsc",
+ "wsf",
+ "wsh",
+ "xll",
+ "xz",
+ "z"
+ ]
+ }
+ ]
+ },
+ {
+ "Id": "2.1.12",
+ "Description": "In Microsoft 365 organizations with Exchange Online mailboxes or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, connection filtering and the default connection filter policy identify good or bad source email servers by IP addresses. The key components of the default connection filter policy are IP Allow List, IP Block List and Safe list. The recommended state is IP Allow List empty or undefined.",
+ "Checks": [
+ "defender_antispam_connection_filter_policy_empty_ip_allowlist"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft 365 organizations with Exchange Online mailboxes or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, connection filtering and the default connection filter policy identify good or bad source email servers by IP addresses. The key components of the default connection filter policy are IP Allow List, IP Block List and Safe list. The recommended state is IP Allow List empty or undefined.",
+ "RationaleStatement": "Without additional verification like mail flow rules, email from sources in the IP Allow List skips spam filtering and sender authentication (SPF, DKIM, DMARC) checks. This method creates a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered. Messages that are determined to be malware or high confidence phishing are filtered.",
+ "ImpactStatement": "This is the default behavior. IP Allow lists may reduce false positives, however, this benefit is outweighed by the importance of a policy which scans all messages regardless of the origin. This supports the principle of zero trust.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules> Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Connection filter policy (Default). 5. Click Edit connection filter policy. 6. Remove any IP entries from Always allow messages from the following IP addresses or address range:. 7. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-HostedConnectionFilterPolicy -Identity Default -IPAllowList @{}",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Connection filter policy (Default). 5. Verify that IP Allow list contains no entries. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-HostedConnectionFilterPolicy -Identity Default | fl IPAllowList 3. Verify that IPAllowList is empty or {}",
+ "AdditionalInformation": "",
+ "DefaultValue": "IPAllowList : {}",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/connection-filter-policies-configure:https://learn.microsoft.com/en-us/defender-office-365/create-safe-sender-lists-in-office-365#use-the-ip-allow-list:https://learn.microsoft.com/en-us/defender-office-365/how-policies-and-protections-are-combined#user-and-tenant-settings-conflict"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.13",
+ "Description": "In Microsoft 365 organizations with Exchange Online mailboxes or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, connection filtering and the default connection filter policy identify good or bad source email servers by IP addresses. The key components of the default connection filter policy are IP Allow List, IP Block List and Safe list. The safe list is a pre-configured allow list that is dynamically updated by Microsoft. The recommended safe list state is: Off or False",
+ "Checks": [
+ "defender_antispam_connection_filter_policy_safe_list_off"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft 365 organizations with Exchange Online mailboxes or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, connection filtering and the default connection filter policy identify good or bad source email servers by IP addresses. The key components of the default connection filter policy are IP Allow List, IP Block List and Safe list. The safe list is a pre-configured allow list that is dynamically updated by Microsoft. The recommended safe list state is: Off or False",
+ "RationaleStatement": "Without additional verification like mail flow rules, email from sources in the IP Allow List skips spam filtering and sender authentication (SPF, DKIM, DMARC) checks. This method creates a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered. Messages that are determined to be malware or high confidence phishing are filtered. The safe list is managed dynamically by Microsoft, and administrators do not have visibility into which senders are included. Incoming messages from email servers on the safe list bypass spam filtering.",
+ "ImpactStatement": "This is the default behavior. IP Allow lists may reduce false positives, however, this benefit is outweighed by the importance of a policy which scans all messages regardless of the origin. This supports the principle of zero trust.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules> Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Connection filter policy (Default). 5. Click Edit connection filter policy. 6. Uncheck Turn on safe list. 7. Click Save. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-HostedConnectionFilterPolicy -Identity Default -EnableSafeList $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Policies select Anti-spam. 4. Click on the Connection filter policy (Default). 5. Verify that Safe list is Off. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-HostedConnectionFilterPolicy -Identity Default | fl EnableSafeList 3. Verify that EnableSafeList is False",
+ "AdditionalInformation": "",
+ "DefaultValue": "EnableSafeList : False",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/connection-filter-policies-configure:https://learn.microsoft.com/en-us/defender-office-365/create-safe-sender-lists-in-office-365#use-the-ip-allow-list:https://learn.microsoft.com/en-us/defender-office-365/how-policies-and-protections-are-combined#user-and-tenant-settings-conflict"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.14",
+ "Description": "Anti-spam protection is a feature of Exchange Online that utilizes policies to help to reduce the amount of junk email, bulk and phishing emails a mailbox receives. These policies contain lists to allow or block specific senders or domains. - The allowed senders list - The allowed domains list - The blocked senders list - The blocked domains list The recommended state is: Do not define any Allowed domains",
+ "Checks": [
+ "defender_antispam_policy_inbound_no_allowed_domains"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Anti-spam protection is a feature of Exchange Online that utilizes policies to help to reduce the amount of junk email, bulk and phishing emails a mailbox receives. These policies contain lists to allow or block specific senders or domains. - The allowed senders list - The allowed domains list - The blocked senders list - The blocked domains list The recommended state is: Do not define any Allowed domains",
+ "RationaleStatement": "Messages from entries in the allowed senders list or the allowed domains list bypass most email protection (except malware and high confidence phishing) and email authentication checks (SPF, DKIM and DMARC). Entries in the allowed senders list or the allowed domains list create a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered. The risk is increased even more when allowing common domain names as these can be easily spoofed by attackers. Microsoft specifies in its documentation that allowed domains should be used for testing purposes only.",
+ "ImpactStatement": "This is the default behavior. Allowed domains may reduce false positives, however, this benefit is outweighed by the importance of having a policy which scans all messages regardless of the origin. As an alternative consider sender based lists. This supports the principle of zero trust.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules> Threat policies. 3. Under Policies select Anti-spam. 4. Open each out of compliance inbound anti-spam policy by clicking on it. 5. Click Edit allowed and blocked senders and domains. 6. Select Allow domains. 7. Delete each domain from the domains list. 8. Click Done > Save. 9. Repeat as needed. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-HostedContentFilterPolicy -Identity <Policy name> -AllowedSenderDomains @{} Or, run this to remove allowed domains from all inbound anti-spam policies: $AllowedDomains = Get-HostedContentFilterPolicy | Where-Object {$_.AllowedSenderDomains} $AllowedDomains | Set-HostedContentFilterPolicy -AllowedSenderDomains @{}",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Policies select Anti-spam. 4. Inspect each inbound anti-spam policy 5. Verify that Allowed domains does not contain any domain names. 6. Repeat as needed for any additional inbound anti-spam policy. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-HostedContentFilterPolicy | ft Identity,AllowedSenderDomains 3. Verify that AllowedSenderDomains is undefined for each inbound policy. Note: Each inbound policy must pass for this recommendation to be considered to be in a passing state.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AllowedSenderDomains : {}",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/anti-spam-protection-about#allow-and-block-lists-in-anti-spam-policies"
+ }
+ ]
+ },
+ {
+ "Id": "2.1.15",
+ "Description": "The default outbound anti-spam policy in Microsoft Defender automatically applies to all users and is designed to detect and limit suspicious email-sending behavior. The policy enforces limits based on both volume and spam detection. If a user sends too many emails too quickly or if a high percentage of their messages are flagged as spam, their ability to send email can be temporarily restricted. This helps prevent abuse from compromised accounts or inadvertent spam campaigns. When these limits are exceeded, Microsoft routes the messages through a high-risk delivery pool to protect its IP reputation and notifies administrators through built-in alert policies. The recommended state is: - External: Restrict sending to external recipients (per hour) - 500 - Internal: Restrict sending to internal recipients (per hour) - 1000 - Daily: Maximum recipient limit per day - 1000 - Action: Over limit action - Restrict the user from sending mail",
+ "Checks": [
+ "defender_antispam_outbound_policy_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.1 Email & collaboration",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The default outbound anti-spam policy in Microsoft Defender automatically applies to all users and is designed to detect and limit suspicious email-sending behavior. The policy enforces limits based on both volume and spam detection. If a user sends too many emails too quickly or if a high percentage of their messages are flagged as spam, their ability to send email can be temporarily restricted. This helps prevent abuse from compromised accounts or inadvertent spam campaigns. When these limits are exceeded, Microsoft routes the messages through a high-risk delivery pool to protect its IP reputation and notifies administrators through built-in alert policies. The recommended state is: - External: Restrict sending to external recipients (per hour) - 500 - Internal: Restrict sending to internal recipients (per hour) - 1000 - Daily: Maximum recipient limit per day - 1000 - Action: Over limit action - Restrict the user from sending mail",
+ "RationaleStatement": "Message limit settings help lessen the impact of a Business Email Compromise (BEC) by automatically restricting accounts that send unusually high volumes of email. This containment prevents compromised accounts from launching large-scale attacks and helps ensure the organization's email remains trusted and deliverable. Without these limits, excessive or suspicious outbound traffic could result in Microsoft blocking the organization's email, disrupting communication and damaging reputation.",
+ "ImpactStatement": "Enforcing message limits may result in legitimate users being temporarily blocked from sending email if their bulk messaging activity resembles spam or exceeds volume thresholds. This can disrupt business operations, delay communication, and require administrative effort to investigate and restore access. However, these adverse effects typically stem from a lack of planning around mass mailings. To avoid triggering these limits, Microsoft recommends sending bulk email through custom subdomains or third- party bulk email providers.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules> Threat policies. 3. Under Policies select Anti-spam and click to open Anti-spam outbound policy (Default). 4. Select Edit protection settings. 5. Set the following settings to the recommended values, or more restrictive values. Message limit values of 0 are not compliant, as it represents the service default o External: Set an external message limit - 500 o Internal: Set an internal message limit - 1000 o Daily: Set a daily message limit - 1000 o Action: Restriction placed on users who reach the message limit - Restrict the user from sending mail 6. Verify that Notify these users and groups if a sender is blocked due to sending outbound spam contains a monitored mailbox. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Change the example email addresses below and run the following PowerShell commands: $params = @{ RecipientLimitExternalPerHour = 500 RecipientLimitInternalPerHour = 1000 RecipientLimitPerDay = 1000 ActionWhenThresholdReached = 'BlockUser' NotifyOutboundSpamRecipients = @('admin@example.com','security@example.com') } Set-HostedOutboundSpamFilterPolicy -Identity 'Default' @params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com. 2. Expand Email & collaboration > Policies & rules > Threat policies. 3. Under Policies select Anti-spam and click to open Anti-spam outbound policy (Default). 4. Verify the following settings are configured to the recommended level or a more restrictive value. Message limit values of 0 are not compliant, as it represents the service default: o External: Restrict sending to external recipients (per hour) - 500 o Internal: Restrict sending to internal recipients (per hour) - 1000 o Daily: Maximum recipient limit per day - 1000 o Action: Over limit action - Restrict the user from sending mail 5. Verify that a monitored mailbox is configured as a recipient under Notify these users and groups if a sender is blocked due to sending outbound spam. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following: $params = @( 'RecipientLimitExternalPerHour' 'RecipientLimitInternalPerHour' 'RecipientLimitPerDay' 'ActionWhenThresholdReached' 'NotifyOutboundSpamRecipients' ) Get-HostedOutboundSpamFilterPolicy -Identity Default | fl $params 3. Verify that each of the following properties is configured as specified: o RecipientLimitExternalPerHour is 500 or less, but not 0 o RecipientLimitInternalPerHour is 1000 or less, but not 0 o RecipientLimitPerDay is 1000 or less, but not 0 o ActionWhenThresholdReached is BlockUser o NotifyOutboundSpamRecipients contains a monitored mailbox. Note: Microsoft's Recommended Strict values represent a more restrictive and also compliant configuration. These values 400, 800, and 800 align with the values above. For further details on Standard and Strict settings, refer to the references section.",
+ "AdditionalInformation": "",
+ "DefaultValue": "RecipientLimitExternalPerHour : 0 RecipientLimitInternalPerHour : 0 RecipientLimitPerDay : 0 ActionWhenThresholdReached : BlockUserForToday The value of 0 means the service defaults are being used. More information on sending limits is here: https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange- online-service-description/exchange-online-limits#sending-limits-1",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/outbound-spam-protection-about:https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365#outbound-spam-policy-settings:https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-1"
+ }
+ ]
+ },
+ {
+ "Id": "2.2.1",
+ "Description": "Organizations should monitor sign-in and audit log activity from the emergency accounts and trigger notifications to other administrators. When you monitor the activity for emergency access accounts, you can verify these accounts are only used for testing or actual emergencies. You can use Azure Monitor, Microsoft Sentinel, Defender for Cloud Apps or other tools to monitor the sign-in logs and trigger email and SMS alerts to your administrators whenever emergency access accounts sign in. This recommendation uses Defender for Cloud Apps Policies to alert on emergency access account activity. The recommended state is to monitor Activity type Log on on break-glass or emergency access accounts.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.2 Cloud apps",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Organizations should monitor sign-in and audit log activity from the emergency accounts and trigger notifications to other administrators. When you monitor the activity for emergency access accounts, you can verify these accounts are only used for testing or actual emergencies. You can use Azure Monitor, Microsoft Sentinel, Defender for Cloud Apps or other tools to monitor the sign-in logs and trigger email and SMS alerts to your administrators whenever emergency access accounts sign in. This recommendation uses Defender for Cloud Apps Policies to alert on emergency access account activity. The recommended state is to monitor Activity type Log on on break-glass or emergency access accounts.",
+ "RationaleStatement": "Emergency access accounts should be used in very few scenarios, for example, the last Global Administrator has left the organization and the account is inaccessible. All activity on an emergency access account should be reviewed at the time of the event to ensure the sign on is legitimate and authorized.",
+ "ImpactStatement": "There is no real world impact to monitoring these accounts beyond allocating staff. The frequency of emergency account sign on should be so low that any activity raises a red flag that is treated with the highest priority.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com 2. Under the Cloud Apps section select Policies -> Policy management. 3. Click on All policies and then Create policy -> Activity policy. 4. Give the policy a name and set the following: o Policy severity to High severity. o Category to Privileged accounts. o Act on Single activity. o Click Select a filter -> Activity type equals Log on. o Click Add a filter -> User Name equals <Emergency access account> as Any role. o Ensure all emergency access accounts are added to this policy or another. o Select an alert method such as Send alert as email. Note: Multiple accounts can be monitored by a single policy or by separate policies.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com 2. Under the Cloud Apps section select Policies -> Policy management. 3. Locate a privileged accounts policy that meets the following criteria o Policy severity is High severity. o Category is Privileged accounts. o Act on Single activity is selected. o Under Activities matching all of the following verify: o Filter1: Activity type equals Log on o Filter2: User Name equals <Emergency access account> as Any role o Verify all additional emergency access accounts are accounted for. o Under Alerts, verify alerting is configured. 4. Repeat this process for any additional emergency access or break-glass accounts in the organization. If matching policies do not exist, then the audit procedure is considered a fail. Note: Multiple accounts can be monitored by a single policy or by separate policies. Note: Emergency access account activity can be monitored in various ways. The audit procedure passes as long as all emergency access account activity is monitored.",
+ "AdditionalInformation": "",
+ "DefaultValue": "A policy to monitor emergency access accounts does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access#monitor-sign-in-and-audit-logs:https://learn.microsoft.com/en-us/defender-cloud-apps/control-cloud-apps-with-policies"
+ }
+ ]
+ },
+ {
+ "Id": "2.4.1",
+ "Description": "Identify priority accounts to utilize Microsoft 365's advanced custom security features. This is an essential tool to bolster protection for users who are frequently targeted due to their critical positions, such as executives, leaders, managers, or others who have access to sensitive, confidential, financial, or high-priority information. Once these accounts are identified, several services and features can be enabled, including threat policies, enhanced sign-in protection through conditional access policies, and alert policies, enabling faster response times for incident response teams.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.4 System",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Identify priority accounts to utilize Microsoft 365's advanced custom security features. This is an essential tool to bolster protection for users who are frequently targeted due to their critical positions, such as executives, leaders, managers, or others who have access to sensitive, confidential, financial, or high-priority information. Once these accounts are identified, several services and features can be enabled, including threat policies, enhanced sign-in protection through conditional access policies, and alert policies, enabling faster response times for incident response teams.",
+ "RationaleStatement": "Enabling priority account protection for users in Microsoft 365 is necessary to enhance security for accounts with access to sensitive data and high privileges, such as CEOs, CISOs, CFOs, and IT admins. These priority accounts are often targeted by spear phishing or whaling attacks and require stronger protection to prevent account compromise. To address this, Microsoft 365 and Microsoft Defender for Office 365 offer several key features that provide extra security, including the identification of incidents and alerts involving priority accounts and the use of built-in custom protections designed specifically for them.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "To remediate using the UI: Remediate with a 3-step process Step 1: Enable Priority account protection in Microsoft 365 Defender: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Select System > Settings near the bottom of the left most panel. 3. Select E-mail & Collaboration > Priority account protection 4. Ensure Priority account protection is set to On Step 2: Tag priority accounts: 5. Select User tags 6. Select the PRIORITY ACCOUNT tag and click Edit 7. Select Add members to add users, or groups. Groups are recommended. 8. Repeat the previous 2 steps for any additional tags needed, such as Finance or HR. 9. Next and Submit. Step 3: Configure E-mail alerts for Priority Accounts: 10. Expand E-mail & Collaboration on the left column. 11. Select Policies & rules > Alert policy 12. Select New Alert Policy 13. Enter a valid policy Name & Description. Set Severity to High and Category to Threat management. 14. Set Activity is to Detected malware in an e-mail message 15. Mail direction is Inbound 16. Select Add Condition and User: recipient tags are 17. In the Selection option field add chosen priority tags such as Priority account. 18. Select Every time an activity matches the rule. 19. Next and verify valid recipient(s) are selected. 20. Next and select Yes, turn it on right away. Click Submit to save the alert. 21. Repeat steps 12 - 18 to create a 2nd alert for the Activity field Activity is: Phishing email detected at time of delivery Note: Any additional activity types may be added as needed. Above are the minimum recommended.",
+ "AuditProcedure": "To audit using the UI: Audit with a 3-step process Step 1: Verify Priority account protection is enabled: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Select System > Settings near the bottom of the left most panel. 3. Select E-mail & collaboration > Priority account protection 4. Verify that Priority account protection is set to On Step 2: Verify that priority accounts are identified and tagged accordingly: 5. Select User tags 6. Select the PRIORITY ACCOUNT tag and click Edit 7. Verify the assigned members match the organization's defined priority accounts or groups. 8. Repeat the previous 2 steps for any additional tags identified, such as Finance or HR. Step 3: Ensure alerts are configured: 9. Expand E-mail & Collaboration on the left column. 10. Select Policies & rules > Alert policy 11. Verify that at least two alert policies are configured to monitor priority accounts for the activities Detected malware in an email message and Phishing email detected at time of delivery. These alerts should meet the following criteria: o Severity: High o Category: Threat management o Mail Direction: Inbound o Recipient Tags: Includes Priority account To audit using PowerShell: 1. Connect to Exchange using Connect-ExchangeOnline 2. Retrieve the Priority Account protection state: Get-EmailTenantSettings | select EnablePriorityAccountProtection - Ensure EnablePriorityAccountProtection is true. 3. Connect to Security & Compliance PowerShell using Connect-IPPSSession 4. Retrieve alert policies targeting priority accounts: Get-ProtectionAlert | Where-Object { $_.RecipientTags -Match 'Priority account' } 5. For each returned policy, verify all of the following criteria: o Severity is High o Filter matches the pattern Mail.Direction -eq 'Inbound' o RecipientTags matches the pattern Priority account o NotificationEnabled is true o NotifyUser contains a valid email recipient o Disabled is false 6. The control is compliant when the results include: o One passing phishing policy (ThreatType = Phish) o One passing malware policy (ThreatType = Malware). o EnablePriorityAccountProtection is true from step 2.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default, priority accounts are undefined.",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/setup/priority-accounts:https://learn.microsoft.com/en-us/defender-office-365/priority-accounts-security-recommendations"
+ }
+ ]
+ },
+ {
+ "Id": "2.4.2",
+ "Description": "Preset security policies have been established by Microsoft, utilizing observations and experiences within datacenters to strike a balance between the exclusion of malicious content from users and limiting unwarranted disruptions. These policies can apply to all, or select users and encompass recommendations for addressing spam, malware, and phishing threats. The policy parameters are pre-determined and non-adjustable. Strict protection has the most aggressive protection of the 3 presets. - EOP: Anti-spam, Anti-malware and Anti-phishing - Defender: Spoof protection, Impersonation protection and Advanced phishing - Defender: Safe Links and Safe Attachments NOTE: The preset security polices cannot target Priority account TAGS currently, groups should be used instead.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.4 System",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Preset security policies have been established by Microsoft, utilizing observations and experiences within datacenters to strike a balance between the exclusion of malicious content from users and limiting unwarranted disruptions. These policies can apply to all, or select users and encompass recommendations for addressing spam, malware, and phishing threats. The policy parameters are pre-determined and non-adjustable. Strict protection has the most aggressive protection of the 3 presets. - EOP: Anti-spam, Anti-malware and Anti-phishing - Defender: Spoof protection, Impersonation protection and Advanced phishing - Defender: Safe Links and Safe Attachments NOTE: The preset security polices cannot target Priority account TAGS currently, groups should be used instead.",
+ "RationaleStatement": "Enabling priority account protection for users in Microsoft 365 is necessary to enhance security for accounts with access to sensitive data and high privileges, such as CEOs, CISOs, CFOs, and IT admins. These priority accounts are often targeted by spear phishing or whaling attacks and require stronger protection to prevent account compromise. The implementation of stringent, pre-defined policies may result in instances of false positive, however, the benefit of requiring the end-user to preview junk email before accessing their inbox outweighs the potential risk of mistakenly perceiving a malicious email as safe due to its placement in the inbox.",
+ "ImpactStatement": "Strict policies are more likely to cause false positives in anti-spam, phishing, impersonation, spoofing and intelligence responses.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand E-mail & collaboration > Policies & rules > Threat policies. 3. Select Preset security policies. 4. Click to Manage protection settings for Strict protection preset. 5. For Apply Exchange Online Protection select at minimum Specific recipients and include the Accounts/Groups identified as Priority Accounts. 6. For Apply Defender for Office 365 Protection select at minimum Specific recipients and include the Accounts/Groups identified as Priority Accounts. 7. For Impersonation protection click Next and add valid e-mails or priority accounts both internal and external that may be subject to impersonation. 8. For Protected custom domains add the organization's domain name, along side other key partners. 9. Click Next and finally Confirm",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand E-mail & collaboration > Policies & rules > Threat policies. 3. From here visit each section in turn: Anti-phishing Anti-spam Anti-malware Safe Attachments Safe Links 4. Verify that each contains a policy named Strict Preset Security Policy that includes the organization's priority accounts and groups. To audit using PowerShell: 1. Connect to Exchange using Connect-ExchangeOnline 2. Retrieve the ATP strict presets rule for Defender: Get-ATPProtectionPolicyRule | Where-Object { $_.Identity -eq 'Strict Preset Security Policy' } 3. Retrieve the EOP strict preset rule for Defender: Get-EOPProtectionPolicyRule | Where-Object { $_.Identity -eq 'Strict Preset Security Policy' } 4. Verify the following criteria for both the EOP Rule and ATP Rule: o State is Enabled o At least one recipient target is populated with a VIP, i.e.: - SentTo, SentToMemberOf or RecipientDomainIs is not null 5. The control is compliant when both the ATP rule and the EOP rule exist and pass the criteria in step 4.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default, presets are not applied to any users or groups.",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/preset-security-policies?view=o365-worldwide:https://learn.microsoft.com/en-us/defender-office-365/priority-accounts-security-recommendations:https://learn.microsoft.com/en-us/defender-office-365/recommended-settings-for-eop-and-office365?view=o365-worldwide#impersonation-settings-in-anti-phishing-policies-in-microsoft-defender-for-office-365"
+ }
+ ]
+ },
+ {
+ "Id": "2.4.3",
+ "Description": "Microsoft Defender for Cloud Apps is a Cloud Access Security Broker (CASB). It provides visibility into suspicious activity in Microsoft 365, enabling investigation into potential security issues and facilitating the implementation of remediation measures if necessary. Some risk detection methods provided by Entra Identity Protection also require Microsoft Defender for Cloud Apps: - Suspicious manipulation of inbox rules - Suspicious inbox forwarding - New country detection - Impossible travel detection - Activity from anonymous IP addresses - Mass access to sensitive files",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.4 System",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Microsoft Defender for Cloud Apps is a Cloud Access Security Broker (CASB). It provides visibility into suspicious activity in Microsoft 365, enabling investigation into potential security issues and facilitating the implementation of remediation measures if necessary. Some risk detection methods provided by Entra Identity Protection also require Microsoft Defender for Cloud Apps: - Suspicious manipulation of inbox rules - Suspicious inbox forwarding - New country detection - Impossible travel detection - Activity from anonymous IP addresses - Mass access to sensitive files",
+ "RationaleStatement": "Security teams can receive notifications of triggered alerts for atypical or suspicious activities, see how the organization's data in Microsoft 365 is accessed and used, suspend user accounts exhibiting suspicious activity, and require users to log back in to Microsoft 365 apps after an alert has been triggered.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Cloud apps. 3. Scroll to Information Protection and select Files. 4. Check Enable file monitoring. 5. Scroll up to Cloud Discovery and select Microsoft Defender for Endpoint. 6. Check Enforce app access, configure a Notification URL and Save. Note: Defender for Endpoint requires a Defender for Endpoint license. Configure App Connectors: 1. Scroll to Connected apps and select App connectors. 2. Click on Connect an app and select Microsoft 365. 3. Check all Azure and Office 365 boxes then click Connect Office 365. 4. Repeat for the Microsoft Azure application.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Cloud apps. 3. Scroll to Connected apps and select App connectors. 4. Verify that Microsoft 365 and Microsoft Azure both show in the list as Connected. 5. Go to Cloud Discovery > Microsoft Defender for Endpoint and verify that the integration is enabled. 6. Go to Information Protection > Files and verify Enable file monitoring is checked.",
+ "AdditionalInformation": "Additional Microsoft 365 Defender features include: - The option to use Defender for cloud apps as a reverse proxy, allowing for the application of access or session controls through the definition of a conditional access policy. - The purchase and implementation of the \"App Governance\" add-on, which provides more precise control over OAuth app permissions and includes additional built-in policies. A list of Defender for Cloud Apps built-in policies for Office 365 can be found at https://learn.microsoft.com/en-us/defender-cloud-apps/protect-office-365.",
+ "DefaultValue": "Disabled",
+ "References": "https://learn.microsoft.com/en-us/defender-cloud-apps/protect-office-365#connect-microsoft-365-to-microsoft-defender-for-cloud-apps:https://learn.microsoft.com/en-us/defender-cloud-apps/protect-azure#connect-azure-to-microsoft-defender-for-cloud-apps:https://learn.microsoft.com/en-us/defender-cloud-apps/best-practices:https://learn.microsoft.com/en-us/defender-cloud-apps/get-started:https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks"
+ }
+ ]
+ },
+ {
+ "Id": "2.4.4",
+ "Description": "Zero-hour auto purge (ZAP) is a protection feature that retroactively detects and neutralizes malware and high confidence phishing. When ZAP for Teams protection blocks a message, the message is blocked for everyone in the chat. The initial block happens right after delivery, but ZAP occurs up to 48 hours after delivery.",
+ "Checks": [
+ "defender_zap_for_teams_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.4 System",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Zero-hour auto purge (ZAP) is a protection feature that retroactively detects and neutralizes malware and high confidence phishing. When ZAP for Teams protection blocks a message, the message is blocked for everyone in the chat. The initial block happens right after delivery, but ZAP occurs up to 48 hours after delivery.",
+ "RationaleStatement": "ZAP is intended to protect users that have received zero-day malware messages or content that is weaponized after being delivered to users. It does this by continually monitoring spam and malware signatures taking automated retroactive action on messages that have already been delivered.",
+ "ImpactStatement": "As with any anti-malware or anti-phishing product, false positives may occur.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Email & collaboration > Microsoft Teams protection. 3. Set Zero-hour auto purge (ZAP) to On (Default) To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following cmdlet: Set-TeamsProtectionPolicy -Identity \"Teams Protection Policy\" -ZapEnabled $true",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Email & collaboration > Microsoft Teams protection. 3. Verify that Zero-hour auto purge (ZAP) is set to On (Default) 4. Under Exclude these participants review the list of exclusions and verify they are justified and within tolerance for the organization. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following cmdlets: Get-TeamsProtectionPolicy | fl ZapEnabled Get-TeamsProtectionPolicyRule | fl ExceptIf* 3. Verify that ZapEnabled is True. 4. Review the list of exclusions and ensure they are justified and within tolerance for the organization. If nothing returns from the 2nd cmdlet then there are no exclusions defined.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On (Default)",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/zero-hour-auto-purge?view=o365-worldwide#zero-hour-auto-purge-zap-in-microsoft-teams:https://learn.microsoft.com/en-us/defender-office-365/mdo-support-teams-about?view=o365-worldwide#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2"
+ }
+ ]
+ },
+ {
+ "Id": "2.4.5",
+ "Description": "Automated Investigation and Response (AIR) investigates alerts and correlates related signals into investigations. When AIR identifies malicious email messages, it groups them into clusters based on shared characteristics like common malicious file, URL, or sending attributes and produces remediation actions for each cluster. This setting controls whether AIR-identified malicious message clusters are remediated automatically, without requiring SecOps approval. Administrators can enable automatic remediation for one or more cluster types: - Similar files: Clusters sharing a similar malicious file - Similar URLs: Clusters sharing a similar malicious URL - Multiple similar attributes: Clusters grouped by multiple shared attributes such as sender IP address, sender domain, or message subject When enabled, the configured remediation action is applied immediately upon cluster identification. The recommended state is to automatically remediate message clusters.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "2 Microsoft Defender",
+ "SubSection": "2.4 System",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Automated Investigation and Response (AIR) investigates alerts and correlates related signals into investigations. When AIR identifies malicious email messages, it groups them into clusters based on shared characteristics like common malicious file, URL, or sending attributes and produces remediation actions for each cluster. This setting controls whether AIR-identified malicious message clusters are remediated automatically, without requiring SecOps approval. Administrators can enable automatic remediation for one or more cluster types: - Similar files: Clusters sharing a similar malicious file - Similar URLs: Clusters sharing a similar malicious URL - Multiple similar attributes: Clusters grouped by multiple shared attributes such as sender IP address, sender domain, or message subject When enabled, the configured remediation action is applied immediately upon cluster identification. The recommended state is to automatically remediate message clusters.",
+ "RationaleStatement": "When automatic remediation is disabled, malicious message clusters identified by AIR remain in users' mailboxes as pending actions until a security analyst manually approves each remediation. During this approval window, users may interact with, open, or forward malicious messages, increasing the risk of a successful compromise. Enabling automatic remediation ensures identified threats are contained immediately upon detection, minimizing the exposure window and reducing the operational burden on security teams to manually review and approve routine threat clusters.",
+ "ImpactStatement": "Automatic remediation removes the manual SecOps approval step for qualifying message cluster actions. If AIR incorrectly classifies a legitimate message cluster as malicious, affected messages will be soft deleted without prior review. Soft deleted messages are moved to the Recoverable Items folder and can be restored through the Action center, Threat Explorer, or Advanced Hunting, subject to each mailbox's deleted item retention period (14 days by default). Organizations should verify retention policies and legal obligations before enabling this setting, as retention configuration affects whether soft deleted messages remain recoverable. Clusters exceeding 10,000 messages are always excluded from automatic remediation and will continue to require manual approval. License Requirement: This setting requires Defender for Office 365 Plan 2 which is included in Microsoft 365 E5.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Email & collaboration > MDO automation settings. 3. Under Message clusters check the following: o Similar files o Similar URLs o Multiple similar attributes 4. Click Save to apply the changes.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Defender https://security.microsoft.com/ 2. Expand System > Settings > Email & collaboration > MDO automation settings. 3. Verify that under Message clusters the following are checked: o Similar files o Similar URLs o Multiple similar attributes Note: At the time of publication, Soft delete is the only available remediation action and is selected by default. Because the action cannot be changed, verifying the selected remediation action is not part of the audit criteria for this recommendation.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default automatic remediation for message clusters is disabled.",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/air-auto-remediation:https://learn.microsoft.com/en-us/defender-office-365/air-about:https://learn.microsoft.com/en-us/exchange/security-and-compliance/recoverable-items-folder/recoverable-items-folder:https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/change-deleted-item-retention"
+ }
+ ]
+ },
+ {
+ "Id": "3.1.1",
+ "Description": "When audit log search is enabled in the Microsoft Purview compliance portal, user and admin activity within the organization is recorded in the audit log and retained for 180 days by default. However, some organizations may prefer to use a third-party security information and event management (SIEM) application to access their auditing data. In this scenario, a global admin can choose to turn off audit log search in Microsoft 365.",
+ "Checks": [
+ "purview_audit_log_search_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "3 Microsoft Purview",
+ "SubSection": "3.1 Audit",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "When audit log search is enabled in the Microsoft Purview compliance portal, user and admin activity within the organization is recorded in the audit log and retained for 180 days by default. However, some organizations may prefer to use a third-party security information and event management (SIEM) application to access their auditing data. In this scenario, a global admin can choose to turn off audit log search in Microsoft 365.",
+ "RationaleStatement": "Enabling audit log search in the Microsoft Purview compliance portal can help organizations improve their security posture, meet regulatory compliance requirements, respond to security incidents, and gain valuable operational insights.",
+ "ImpactStatement": "",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Purview https://purview.microsoft.com/ 2. Select Solutions and then Audit to open the audit search. 3. Click blue bar Start recording user and admin activity. 4. Click Yes on the dialog box to confirm. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Purview https://purview.microsoft.com/ 2. Select Solutions and then Audit to open the audit search. 3. Choose a date and time frame in the past 30 days. 4. Verify search capabilities (e.g. try searching for Activities as Accessed file and results should be displayed). To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-AdminAuditLogConfig | Select-Object UnifiedAuditLogIngestionEnabled 3. Ensure UnifiedAuditLogIngestionEnabled is set to True. Note: If the Get-AdminAuditLogConfig cmdlet is executed while connected to both Security & Compliance PowerShell as well as Exchange Online PowerShell then UnifiedAuditLogIngestionEnabled will always display False. This depends on the orders the module were imported. If Security & Compliance is needed in the same session be sure to connect to it first, and then Exchange PowerShell second.",
+ "AdditionalInformation": "",
+ "DefaultValue": "180 days",
+ "References": "https://learn.microsoft.com/en-us/purview/audit-log-enable-disable?view=o365-worldwide&tabs=microsoft-purview-portal:https://learn.microsoft.com/en-us/powershell/module/exchange/set-adminauditlogconfig?view=exchange-ps:https://learn.microsoft.com/en-us/purview/audit-log-enable-disable?view=o365-worldwide&tabs=microsoft-purview-portal#verify-the-auditing-status-for-your-organization"
+ }
+ ]
+ },
+ {
+ "Id": "3.2.1",
+ "Description": "Data Loss Prevention (DLP) policies allow Exchange Online and SharePoint Online content to be scanned for specific types of data like social security numbers, credit card numbers, or passwords.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Microsoft Purview",
+ "SubSection": "3.2 Data Loss Protection",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Data Loss Prevention (DLP) policies allow Exchange Online and SharePoint Online content to be scanned for specific types of data like social security numbers, credit card numbers, or passwords.",
+ "RationaleStatement": "Enabling DLP policies alerts users and administrators that specific types of data should not be exposed, helping to protect the data from accidental exposure.",
+ "ImpactStatement": "Enabling a Teams DLP policy will allow sensitive data in Exchange Online and SharePoint Online to be detected or blocked. Always ensure to follow appropriate procedures during testing and implementation of DLP policies based on organizational standards.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Purview https://purview.microsoft.com/ 2. Click Solutions > Data loss prevention then Policies. 3. Click Create policy. 4. Create a policy that is specific to the types of data the organization wishes to protect.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Purview https://purview.microsoft.com/ 2. Click Solutions > Data loss prevention and then Policies. 3. Inspect the list of policies and verify the following criteria: o A policy exists that meets the organizations DLP needs o Mode is On 4. Open the policy and verify there is at least one of the following locations defined: o Exchange email o SharePoint sites o OneDrive accounts o Teams chat and channel messages 5. Compliance is met when there is at least one policy the meets the above criteria. To audit using the PowerShell: 1. Connect to the Security & Compliance PowerShell using Connect-IPPSSession. 2. Execute the following cmdlet to get a list of DLP Policies: Get-DlpCompliancePolicy 3. For each policy returned verify the following criteria: o Mode is Enable o At least one of the following locations is defined: o ExchangeLocation o SharePointLocation o OneDriveLocation o TeamsLocation 4. Compliance is met when there is at least one policy the meets the above criteria. Note: The types of policies an organization should implement to protect information are specific to their industry. However, certain types of information, such as credit card numbers, social security numbers, and certain personally identifiable information (PII), are universally important to safeguard across all industries.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/purview/dlp-learn-about-dlp?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "3.2.2",
+ "Description": "The default Teams Data Loss Prevention (DLP) policy rule in Microsoft 365 is a preconfigured rule that is automatically applied to all Teams conversations and channels. The default rule helps prevent accidental sharing of sensitive information by detecting and blocking certain types of content that are deemed sensitive or inappropriate by the organization. By default, the rule includes a check for the sensitive info type Credit Card Number which is pre-defined by Microsoft.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Microsoft Purview",
+ "SubSection": "3.2 Data Loss Protection",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The default Teams Data Loss Prevention (DLP) policy rule in Microsoft 365 is a preconfigured rule that is automatically applied to all Teams conversations and channels. The default rule helps prevent accidental sharing of sensitive information by detecting and blocking certain types of content that are deemed sensitive or inappropriate by the organization. By default, the rule includes a check for the sensitive info type Credit Card Number which is pre-defined by Microsoft.",
+ "RationaleStatement": "Enabling the default Teams DLP policy rule in Microsoft 365 helps protect an organization's sensitive information by preventing accidental sharing or leakage of Credit Card information in Teams conversations and channels. DLP rules are not one size fits all, but at a minimum something should be defined. The organization should identify sensitive information important to them and seek to intercept it using DLP.",
+ "ImpactStatement": "End-users may be prevented from sharing certain types of content, which may require them to adjust their behavior or seek permission from administrators to share specific content. Administrators may receive requests from end-users for permission to share certain types of content or to modify the policy to better fit the needs of their teams.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Under Solutions select Data loss prevention then Policies. 3. Click Policies tab. 4. Check Default policy for Teams then click Edit policy. 5. The edit policy window will appear click Next 6. At the Choose locations to apply the policy page, turn the status toggle to On for Teams chat and channel messages location and then click Next. 7. On Customized advanced DLP rules page, ensure the Default Teams DLP policy rule Status is On and click Next. 8. On the Policy mode page, select the radial for Turn it on right away and click Next. 9. Review all the settings for the created policy on the Review your policy and create it page, and then click submit. 10. Once the policy has been successfully submitted click Done. Note: Some tenants may not have a default policy for teams as Microsoft started creating these by default at a particular point in time. In this case a new policy will have to be created that includes a rule to protect data important to the organization such as credit cards and PII.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Under Solutions select Data loss prevention then Policies. 3. Locate the Default policy for Teams. 4. Verify the Status is On. 5. Verify Locations include Teams chat and channel messages - All accounts. 6. Verify Policy settings includes the Default Teams DLP policy rule or one specific to the organization. Note: If there is not a default policy for teams inspect existing policies starting with step 4. DLP rules are specific to the organization and each organization should take steps to protect the data that matters to them. The default teams DLP rule will only alert on Credit Card matches. To audit using PowerShell: 1. Connect to the Security & Compliance PowerShell using Connect-IPPSSession. 2. Run the following to return policies that include Teams chat and channel messages: $DlpPolicy = Get-DlpCompliancePolicy $DlpPolicy | Where-Object {$_.Workload -match \"Teams\"} | ft Name,Mode,TeamsLocation* 3. If nothing returns, then there are no policies that include Teams and remediation is required. 4. For any returned policy verify Mode is set to Enable. 5. Verify TeamsLocation includes All. 6. Verify TeamsLocationException includes only permitted exceptions. Note: Some tenants may not have a default policy for teams as Microsoft started creating these by default at a particular point in time. In this case a new policy will have to be created that includes a rule to protect data important to the organization such as credit cards and PII.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled (On)",
+ "References": "https://learn.microsoft.com/en-us/powershell/exchange/connect-to-scc-powershell?view=exchange-ps:https://learn.microsoft.com/en-us/purview/dlp-teams-default-policy:https://learn.microsoft.com/en-us/powershell/module/exchange/connect-ippssession?view=exchange-ps"
+ }
+ ]
+ },
+ {
+ "Id": "3.2.3",
+ "Description": "Microsoft Purview Data Loss Prevention (DLP) policies can be scoped to Microsoft 365 Copilot and Copilot Chat interactions. When active, these policies can restrict Copilot from processing or surfacing content that matches configured sensitive information types. Organizations must define the sensitive data categories relevant to their environment and configure at least one DLP policy that covers Copilot interactions in enforcement mode. The recommended state is to configure at least one DLP policy that includes Microsoft 365 Copilot and Copilot Chat - All accounts as a location with rules specific to the organization's needs.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Microsoft Purview",
+ "SubSection": "3.2 Data Loss Protection",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Purview Data Loss Prevention (DLP) policies can be scoped to Microsoft 365 Copilot and Copilot Chat interactions. When active, these policies can restrict Copilot from processing or surfacing content that matches configured sensitive information types. Organizations must define the sensitive data categories relevant to their environment and configure at least one DLP policy that covers Copilot interactions in enforcement mode. The recommended state is to configure at least one DLP policy that includes Microsoft 365 Copilot and Copilot Chat - All accounts as a location with rules specific to the organization's needs.",
+ "RationaleStatement": "Microsoft 365 Copilot can retrieve, summarize, and generate content based on data the authenticated user has access to across M365 workloads, including SharePoint, OneDrive, Teams, and Exchange. Without a DLP policy scoped to Copilot interactions, no technical control exists to prevent sensitive information such as PII, financial data, or health records from being incorporated into Copilot-generated responses and potentially exposed to users who would not otherwise have direct access to the source content. Enforcing DLP policies for Copilot ensures that sensitive data categories defined by the organization are intercepted before they are processed or surfaced by AI-generated responses.",
+ "ImpactStatement": "Users may find that Copilot declines to process or respond to prompts that involve content matching the organization's configured sensitive information types. In these cases, Copilot will notify the user that the request was blocked by policy. Users who rely on Copilot to summarize, draft, or retrieve content containing sensitive data such as documents with PII, financial records, or health information may need to rephrase their prompts or work with the content directly outside of Copilot. Administrators should communicate the scope of active DLP policies to affected users prior to enforcement.",
+ "RemediationProcedure": "To remediate using the UI: Note: Microsoft provides a guided wizard to create the Default DLP policy - Protect sensitive M365 Copilot interactions policy, which can be used when no Copilot DLP policy exists in the tenant. The steps below describe how to create a custom policy from scratch with Copilot included as a location. 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Under Solutions select Data loss prevention then Policies. 3. Click Policies tab. 4. Click + Create Policy. 5. Click on Enterprise applications & devices. 6. Under Categories select Custom and then Custom policy for the regulation. 7. Name the policy, and if appropriate, select an Admin Unit. 8. In Locations select Microsoft 365 Copilot and Copilot Chat. 9. Click on Next to proceed to the Advanced DLP rules page. 10. Click on + Create Rule 1. Name the rule and give a brief description of the data that is being targeted. 2. Click on + Add condition and select Content Contains 3. Click on Add and select Sensitive info types 4. Select the sensitive information types the organization wants to protect from being processed in Copilot interactions and click Add. 5. Click on + Add an action and select Restrict Copilot from processing content 6. Check the box for a relevant restriction. 7. Click on Save. 11. Repeat step 10 to create as many rules as the organization requires 12. Click Next. 13. On the Policy mode page, select the radial for Turn it on right away and click Next. 14. Click Submit to create the policy once it has been reviewed. 15. Finally, click Done. Note: Compliance with this recommendation is not achieved until the policy is in enforcement mode.",
+ "AuditProcedure": "Note: Some tenants may have a default policy called Default DLP policy - Protect sensitive M365 Copilot interactions that was automatically created. If not present, it can also be created using a guided process in the Policies blade. If this policy exists, it may be used to satisfy the requirements of this control provided it meets the compliance criteria below. To audit using the UI: 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Under Solutions select Data loss prevention then Policies. 3. Inspect the list of policies and verify the following criteria: o Locations includes Microsoft 365 Copilot and Copilot Chat - All accounts. o Mode is On. o The policy includes Rules that restrict sensitive data from being shared in Copilot interactions based on the organization's needs. 4. Compliance is met when there is at least one policy that meets the above criteria. To audit using PowerShell: 1. Connect to the Security & Compliance PowerShell using Connect-IPPSSession. 2. Run the following to return policies that include Teams chat and channel messages: $DlpPolicy = Get-DlpCompliancePolicy $DlpPolicy | Where-Object {$_.EnforcementPlanes -match \"CopilotExperiences\"} | FT Name,Mode,LocationInclusions,LocationExclusions 3. If nothing returns, then there are no policies that include Copilot and remediation is required. 4. For any returned policy verify Mode is set to Enable. 5. Verify LocationInclusions includes All. 6. Verify LocationExclusions includes only permitted exceptions. Note: DLP rules are specific to the organization and each organization should take steps to protect the data that matters to them. At a minimum, organizations should consider protecting personally identifiable information (PII) specific to their locale.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No Copilot DLP policy exists by default for most tenants. Some tenants may have had a Default DLP policy - Protect sensitive M365 Copilot interactions policy automatically provisioned by Microsoft; if present, it may satisfy this recommendation if it meets the audit criteria.",
+ "References": "https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about:https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-default-policy:https://learn.microsoft.com/en-us/powershell/exchange/connect-to-scc-powershell?view=exchange-ps"
+ }
+ ]
+ },
+ {
+ "Id": "3.3.1",
+ "Description": "Sensitivity labels enable organizations to classify and label content across Microsoft 365 based on its sensitivity and business impact. These labels can be applied manually by users or automatically based on the content. When applied, labels can automatically encrypt content, provide \"Confidential\" watermarks, restrict access, and offer various data protection features. Labels can be scoped to data assets and containers: - Files & other data assets in Microsoft 365, Fabric, Azure, AWS and other platforms - Email messages sent from all versions of Outlook - Meeting calendar events and schedules in Outlook and Teams - Teams, Microsoft 365 Groups and SharePoint sites",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "3 Microsoft Purview",
+ "SubSection": "3.3 Information Protection",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Sensitivity labels enable organizations to classify and label content across Microsoft 365 based on its sensitivity and business impact. These labels can be applied manually by users or automatically based on the content. When applied, labels can automatically encrypt content, provide \"Confidential\" watermarks, restrict access, and offer various data protection features. Labels can be scoped to data assets and containers: - Files & other data assets in Microsoft 365, Fabric, Azure, AWS and other platforms - Email messages sent from all versions of Outlook - Meeting calendar events and schedules in Outlook and Teams - Teams, Microsoft 365 Groups and SharePoint sites",
+ "RationaleStatement": "Consistent usage of sensitivity labels can help reduce the risk of data loss or exposure and enable more effective incident response if a breach does occur. They can also help organizations comply with regulatory requirements and provide visibility and control over sensitive information.",
+ "ImpactStatement": "Encryption configurations (control access, DKE, BYOK) in the individual labels may impact users' ability to access site documents and information. Careful consideration of the individual sensitivity label configurations should be exercised prior to applying an auto labeling policy, publishing policy, sensitivity label configuration, or PowerShell based label settings to SharePoint sites. Additionally, when updating or deleting Sensitivity Labels, an assessment of the potential impacts should be conducted to avoid unintended consequences. If tenants are configured for sharing with guests or external domains and Sensitivity Labels have encryption applied, this can affect the ability to share documents via email stored in SharePoint. Some recipients may be unable to open the document depending on their email client, which could trigger Purview Advanced Encryptions and OME flows based on the recipient type and the cloud license from which the email is sent (e.g., government clouds vs. commercial clouds).",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Select Information protection > Sensitivity labels. 3. Click Create a label to create a label. 4. Click Publish labels and select any newly created labels to publish according to the organization's information protection needs.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Purview compliance portal https://purview.microsoft.com/ 2. Select Information protection > Policies > Label publishing policies. 3. Ensure that a Label policy exists and is published according to the organization's information protection needs. To audit using PowerShell: 1. Connect to the Security & Compliance PowerShell using Connect-IPPSSession. 2. Run the following script: $Policies = Get-LabelPolicy -WarningAction Ignore | Where-Object { $_.Type -eq \"PublishedSensitivityLabel\" } if ($Policies) { $Policies | Format-List -Property Name, *Location* Write-Host \"$($Policies.Count) Sensitivity Label policies found.\" } else { Write-Host \"No Sensitivity Label policies found\" } 3. Ensure there is at least one sensitivity label policy published. 4. Review the locations defined to ensure they're in scope with the organization's needs. Note: These policies are specific to the information protection needs of each organization. Whether an organization passes the audit is open to interpretation by the auditor and depends largely on how effectively it implements information protection features to safeguard data.",
+ "AdditionalInformation": "",
+ "DefaultValue": "The \"Global sensitivity label policy\" exists by default.",
+ "References": "https://learn.microsoft.com/en-us/purview/sensitivity-labels:https://learn.microsoft.com/en-us/purview/create-sensitivity-labels"
+ }
+ ]
+ },
+ {
+ "Id": "4.1",
+ "Description": "Compliance policies are sets of rules and conditions that are used to evaluate the configuration of managed devices. These policies can help secure organizational data and resources from devices that don't meet those configuration requirements. Managed devices must satisfy the conditions you set in your policies to be considered compliant by Intune. When combined with conditional access, this allows more control over how non-compliant devices are treated. The recommended state is Mark devices with no compliance policy assigned as as Not compliant",
+ "Checks": [
+ "intune_device_compliance_policy_unassigned_devices_not_compliant_by_default"
+ ],
+ "Attributes": [
+ {
+ "Section": "4 Microsoft Intune admin center",
+ "SubSection": "",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Compliance policies are sets of rules and conditions that are used to evaluate the configuration of managed devices. These policies can help secure organizational data and resources from devices that don't meet those configuration requirements. Managed devices must satisfy the conditions you set in your policies to be considered compliant by Intune. When combined with conditional access, this allows more control over how non-compliant devices are treated. The recommended state is Mark devices with no compliance policy assigned as as Not compliant",
+ "RationaleStatement": "Implementing this setting is a first step in adopting compliance policies for devices. When used together with Conditional Access policies the attack surface can be reduced by forcing an action to be taken for non-compliant devices. Note: This section does not focus on which compliance policies to use, only that an organization should adopt and enforce them to their needs.",
+ "ImpactStatement": "Any devices without a compliance policy will be marked not compliant. Care should be taken to first deploy any new compliance policies with a Conditional Access (CA) policy that is in the Report-only state. After the environment's device compliance is better understood it is then appropriate to finally align with Mark devices with no compliance policy assigned as and enable any CA policies that enforce actions based on device compliance. If a mature environment already has an existing device compliance CA policy and a large number of devices without an assigned compliance policy, this could cause disruption as those devices would then be suddenly considered not compliant.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Intune admin center https://intune.microsoft.com/ 2. Select Devices and then under Manage devices click Compliance 3. Click Compliance settings. 4. Set Mark devices with no compliance policy assigned as to Not compliant. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"DeviceManagementConfiguration.ReadWrite.All\" 2. Run the following commands: $Uri = 'https://graph.microsoft.com/v1.0/deviceManagement' $Body = @{ settings = @{ secureByDefault = $true } } | ConvertTo-Json Invoke-MgGraphRequest -Uri $Uri -Method PATCH -Body $Body",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Intune admin center https://intune.microsoft.com/ 2. Select Devices and then under Manage devices click Compliance 3. Click Compliance settings. 4. Verify that Mark devices with no compliance policy assigned as is set to Not compliant. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"DeviceManagementConfiguration.Read.All\" 2. Run the following commands: $Uri = 'https://graph.microsoft.com/v1.0/deviceManagement/settings' Invoke-MgGraphRequest -Uri $Uri -Method GET 3. Verify that secureByDefault is set to True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "UI: \"Compliant\" Graph: secureByDefault = $false",
+ "References": "https://learn.microsoft.com/en-us/mem/intune/protect/device-compliance-get-started"
+ }
+ ]
+ },
+ {
+ "Id": "4.2",
+ "Description": "Device enrollment restrictions let you restrict devices from enrolling in Intune based on certain device attributes such as device limit, device platform, OS Version, manufacturer or device ownership (Personally owned devices). The recommended state is to Block personally owned devices from enrollment.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "4 Microsoft Intune admin center",
+ "SubSection": "",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Device enrollment restrictions let you restrict devices from enrolling in Intune based on certain device attributes such as device limit, device platform, OS Version, manufacturer or device ownership (Personally owned devices). The recommended state is to Block personally owned devices from enrollment.",
+ "RationaleStatement": "Restricting the enrollment of personally owned devices prevents attackers who have bypassed other controls from registering a new device to gain an additional foothold, further hiding or obscuring their activities. An attack path could be: 1. Account Compromise via Phishing and AiTM 2. Conditional Access Bypass 3. Reconnaissance using e.g. ROADrecon, GraphRunner or AADInternals 4. Lateral Movement, Privilege Escalation or Persistence through a newly registered device enrolled in Intune",
+ "ImpactStatement": "Per platform personally owned device enrollment impacts are listed below. It is important to test the changes to the defaults prior to moving into production and implementing this control. Windows Devices The following enrollment methods are authorized for corporate enrollment for Windows devices, any other enrollment method will be considered \"Personal\" and blocked: - The device enrolls through Windows Autopilot. - The device enrolls through GPO, or automatic enrollment from Configuration Manager for co-management. - The device enrolls through a bulk provisioning package. - The enrolling user is using a device enrollment manager account. MacOS By default, Intune classifies macOS devices as personally owned. To be classified as corporate-owned, a Mac must fulfill one of the following conditions: - Registered with a serial number. - Enrolled via Apple Automated Device Enrollment (ADE). iOS/IPadOS devices By default, Intune classifies iOS/iPadOS devices as personally owned. To be classified as corporate-owned, an iOS/iPadOS device must fulfill one of the following conditions: - Registered with a serial number or IMEI. - Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program). Android devices By default, until you manually make changes in the admin center, your Android Enterprise work profile device settings and Android device administrator device settings are the same. If you block Android Enterprise work profile enrollment on personal devices, only corporate-owned devices can enroll with personally owned work profiles.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Intune admin center https://intune.microsoft.com/ 2. Select Devices and then under Device onboarding click Enrollment 3. Under Enrollment options select Device platform restriction. 4. Inspect the policies listed under Device type restrictions o For the Default priority policy, click All Users. o Select Properties. 5. Click Edit to change Platform settings. 6. In the Personally owned column set each platform to Block. Note: Blocking platforms that are not used in the organization is a more restrictive best practice and will also effectively block enrollment of personally owned devices for the selected platform, ensuring compliance for this recommendation.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Intune admin center https://intune.microsoft.com/ 2. Select Devices and then under Device onboarding click Enrollment 3. Under Enrollment options select Device platform restriction. 4. Inspect the policies listed under Device type restrictions o For the Default priority policy, click All Users. o Select Properties. 5. Verify that all platforms are set to Block in the Personally owned column. 6. If the Platform itself is set to Block for any of the platforms shown this is also a passing state for that platform. Note: Blocking platforms that are not used in the organization is a more restrictive best practice and will also effectively block enrollment of personally owned devices for the selected platform, ensuring compliance for this recommendation. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"DeviceManagementConfiguration.Read.All\" 2. Run the following script: $Uri = 'https://graph.microsoft.com/beta/deviceManagement/deviceEnrollmentConfigurat ions' $Config = (Invoke-MgGraphRequest -Uri $Uri -Method GET).value | Where-Object { $_.id -match 'DefaultPlatformRestrictions' -and $_.priority - eq 0 } $Result = [PSCustomObject]@{ WindowsPersonalDeviceEnrollmentBlocked = $Config.windowsRestriction.personalDeviceEnrollmentBlocked iOSPersonalDeviceEnrollmentBlocked = $Config.iosRestriction.personalDeviceEnrollmentBlocked AndroidForWorkPersonalDeviceEnrollmentBlocked = $Config.androidForWorkRestriction.personalDeviceEnrollmentBlocked MacOPersonalDeviceEnrollmentBlocked = $Config.macOSRestriction.personalDeviceEnrollmentBlocked AndroidPersonalDeviceEnrollmentBlocked = $Config.androidRestriction.personalDeviceEnrollmentBlocked } $Result 3. Inspect the output, ensure each platform displays True next to its property. A passing output will look like the below: WindowsPersonalDeviceEnrollmentBlocked : True iOSPersonalDeviceEnrollmentBlocked : True AndroidForWorkPersonalDeviceEnrollmentBlocked : True MacOPersonalDeviceEnrollmentBlocked : True AndroidPersonalDeviceEnrollmentBlocked : True Note: If platformBlocked is true then that platform is also in compliance as the platform is blocked from enrollment entirely. This is not currently reflected in the audit script but can be queried from the same API call.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Allow",
+ "References": "https://learn.microsoft.com/en-us/mem/intune/enrollment/enrollment-restrictions-set:https://www.glueckkanja.com/blog/security/2025/01/compliant-device-bypass-en/"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.1",
+ "Description": "Legacy per-user Multi-Factor Authentication (MFA) can be configured to require individual users to provide multiple authentication factors, such as passwords and additional verification codes, to access their accounts. It was introduced in earlier versions of Office 365, prior to the more comprehensive implementation of Conditional Access (CA).",
+ "Checks": [
+ "entra_users_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Legacy per-user Multi-Factor Authentication (MFA) can be configured to require individual users to provide multiple authentication factors, such as passwords and additional verification codes, to access their accounts. It was introduced in earlier versions of Office 365, prior to the more comprehensive implementation of Conditional Access (CA).",
+ "RationaleStatement": "Both security defaults and conditional access with security defaults turned off are not compatible with per-user multi-factor authentication (MFA), which can lead to undesirable user authentication states. The CIS Microsoft 365 Benchmark explicitly employs Conditional Access for MFA as an enhancement over security defaults and as a replacement for the outdated per-user MFA. To ensure a consistent authentication state disable per-user MFA on all accounts.",
+ "ImpactStatement": "Accounts using per-user MFA will need to be migrated to use CA. Prior to disabling per-user MFA the organization must be prepared to implement conditional access MFA to avoid security gaps and allow for a smooth transition. This will help ensure relevant accounts are covered by MFA during the change phase from disabling per-user MFA to enabling CA MFA. Section 5.2.2 in this document covers the creation of a CA rule for both administrators and all users in the tenant. Microsoft has documentation on migrating from per-user MFA Convert users from per- user MFA to Conditional Access based MFA",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select All users. 3. Click on Per-user MFA on the top row. 4. Click the empty box next to Display Name to select all accounts. 5. On the far right under quick steps click Disable.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select All users. 3. Click on Per-user MFA on the top row. 4. Verify that the Multi-factor Auth Status column shows Disabled for each account. To audit using Microsoft Graph 1. Determine the id or userPrincipalName of the user being audited. 2. Execute a GET request to the following relative URI: beta/users/{id | userPrincipalName}/authentication/requirements # Example https://graph.microsoft.com/beta/users/071cc716-8147-4397-a5ba- b2105951cc0b/authentication/requirements 3. Verify that the perUserMfaState property is set to disabled. 4. Repeat this process for all users within the tenant. Note: This API is in beta and does not support a list operation. To prevent server-side throttling, clients should implement batching and client-side rate limiting when auditing medium to large sized environments.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-userstates#convert-users-from-per-user-mfa-to-conditional-access:https://learn.microsoft.com/en-us/microsoft-365/admin/security-and-compliance/set-up-multi-factor-authentication?view=o365-worldwide#use-conditional-access-policies:https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-userstates#convert-per-user-mfa-enabled-and-enforced-users-to-disabled:https://learn.microsoft.com/en-us/graph/api/authentication-get?view=graph-rest-beta"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.2",
+ "Description": "This setting controls whether standard users can register applications in the Microsoft Entra ID directory. When enabled, any user can create app registrations, which function as identity objects for applications.",
+ "Checks": [
+ "entra_thirdparty_integrated_apps_not_allowed"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting controls whether standard users can register applications in the Microsoft Entra ID directory. When enabled, any user can create app registrations, which function as identity objects for applications.",
+ "RationaleStatement": "Allowing standard users to create app registrations expands the tenant's attack surface. A compromised account or malicious insider could create a rogue app registration to establish a persistent OAuth client, facilitate token theft, or impersonate a legitimate application. Restricting app registration to privileged roles ensures that new application identities in the directory are subject to administrative review and approval before they can be granted permissions to organizational resources.",
+ "ImpactStatement": "End users will no longer be able to register applications independently, including both third-party integrations and custom applications. Developers and IT staff who create app registrations as part of normal workflows will be affected and will need to submit registration requests to a privileged administrator (e.g., Application Administrator or Cloud Application Administrator). Organizations should establish a formal request and approval process before implementing this change to avoid workflow disruption.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select Users settings. 3. Set Users can register applications to No. 4. Click Save. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run the following commands: $param = @{ AllowedToCreateApps = $false } Update-MgPolicyAuthorizationPolicy -DefaultUserRolePermissions $param",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select Users settings. 3. Verify that Users can register applications is set to No. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: (Get-MgPolicyAuthorizationPolicy).DefaultUserRolePermissions | fl AllowedToCreateApps 3. Verify the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Yes (Users can register applications.)",
+ "References": "https://learn.microsoft.com/en-us/entra/identity-platform/how-applications-are-added:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/delegate-app-roles#restrict-who-can-create-applications"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.3",
+ "Description": "Non-privileged users can create tenants in the Microsoft Entra ID and Microsoft Entra administration portal under \"Manage tenant\". The creation of a tenant is recorded in the Audit log as category \"DirectoryManagement\" and activity \"Create Company\". By default, the user who creates a Microsoft Entra tenant is automatically assigned the Global Administrator role. The newly created tenant doesn't inherit any settings or configurations.",
+ "Checks": [
+ "entra_policy_ensure_default_user_cannot_create_tenants"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Non-privileged users can create tenants in the Microsoft Entra ID and Microsoft Entra administration portal under \"Manage tenant\". The creation of a tenant is recorded in the Audit log as category \"DirectoryManagement\" and activity \"Create Company\". By default, the user who creates a Microsoft Entra tenant is automatically assigned the Global Administrator role. The newly created tenant doesn't inherit any settings or configurations.",
+ "RationaleStatement": "Restricting tenant creation prevents unauthorized or uncontrolled deployment of resources and ensures that the organization retains control over its infrastructure. User generation of shadow IT could lead to multiple, disjointed environments that can make it difficult for IT to manage and secure the organization's data, especially if other users in the organization began using these tenants for business purposes under the misunderstanding that they were secured by the organization's security team.",
+ "ImpactStatement": "Non-admin users will need to contact I.T. if they have a valid reason to create a tenant.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Users and select User settings. 3. Set Restrict non-admin users from creating tenants to Yes then Save. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run the following commands: # Create hashtable and update the auth policy $params = @{ AllowedToCreateTenants = $false } Update-MgPolicyAuthorizationPolicy -DefaultUserRolePermissions $params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Users and select User settings. 3. Verify that Restrict non-admin users from creating tenants is set to Yes To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following commands: (Get-MgPolicyAuthorizationPolicy).DefaultUserRolePermissions | Select-Object AllowedToCreateTenants 3. Verify the returned value is False",
+ "AdditionalInformation": "",
+ "DefaultValue": "No - Non-administrators can create tenants. AllowedToCreateTenants is True",
+ "References": "https://learn.microsoft.com/en-us/entra/fundamentals/users-default-permissions#restrict-member-users-default-permissions:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#tenant-creator"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.4",
+ "Description": "This setting restricts non-administrators from loading a set of frequently visited pages in the Microsoft Entra admin center and Azure portal, including home, tenant overview, and the users list. What does it not do? - It does not block programmatic access to Microsoft Entra data via PowerShell, Microsoft Graph API, or other tools like Visual Studio. - It does not apply to users with an administrative role, including custom roles. - It does not prevent all access to the admin center. Many areas are still reachable through alternate paths.",
+ "Checks": [
+ "entra_admin_portals_access_restriction"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "This setting restricts non-administrators from loading a set of frequently visited pages in the Microsoft Entra admin center and Azure portal, including home, tenant overview, and the users list. What does it not do? - It does not block programmatic access to Microsoft Entra data via PowerShell, Microsoft Graph API, or other tools like Visual Studio. - It does not apply to users with an administrative role, including custom roles. - It does not prevent all access to the admin center. Many areas are still reachable through alternate paths.",
+ "RationaleStatement": "The Microsoft Entra admin center contains sensitive data and permission settings, which are still enforced based on the user's role. However, an end user may inadvertently change properties or account settings on their own account. This could result in increased administrative overhead. Additionally, a compromised end-user account could be used to enumerate tenant structure, users, and group memberships to support privilege escalation or lateral movement.",
+ "ImpactStatement": "Non-administrators who own groups will be unable to reach group management pages through the standard admin center navigation. Self-service access to other portal-facing features may also be affected depending on the navigation path used. Because the restriction targets specific frequently accessed pages rather than all portal content, users with direct (deep) links to other admin center sections may still be able to access them. Note: Users will still be able to sign into Microsoft Entra admin center but will be unable to see directory information.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Users and select User settings. 3. Set Restrict access to Microsoft Entra admin center to Yes then Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Users and select User settings. 3. Verify under the Administration center section that Restrict access to Microsoft Entra admin center is set to Yes.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No - Non-administrators can access the Microsoft Entra admin center.",
+ "References": "https://learn.microsoft.com/en-us/entra/fundamentals/users-default-permissions#restrict-member-users-default-permissions"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.5",
+ "Description": "The option for the user to Stay signed in, or the Keep me signed in option, will prompt a user after a successful login. When the user selects this option, a persistent refresh token is created. The refresh token lasts for 90 days by default and does not prompt for sign-in or multifactor.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "The option for the user to Stay signed in, or the Keep me signed in option, will prompt a user after a successful login. When the user selects this option, a persistent refresh token is created. The refresh token lasts for 90 days by default and does not prompt for sign-in or multifactor.",
+ "RationaleStatement": "Allowing users to select this option presents risk, especially if the user signs into their account on a publicly accessible computer/web browser. In this case it would be trivial for an unauthorized person to gain access to any associated cloud data from that account.",
+ "ImpactStatement": "Once this setting is hidden users will no longer be prompted upon sign-in with the message Stay signed in?. This may mean users will be forced to sign in more frequently. Important: some features of SharePoint Online and Office 2010 have a dependency on users remaining signed in. If you hide this option, users may get additional and unexpected sign in prompts.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select User settings. 3. Set Show keep user signed in to No. 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select User settings. 3. Verify that Show keep user signed in is highlighted No.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Users may select stay signed in",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concepts-azure-multi-factor-authentication-prompts-session-lifetime:https://learn.microsoft.com/en-us/entra/fundamentals/how-to-manage-stay-signed-in-prompt"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.2.6",
+ "Description": "LinkedIn account connections allow users to connect their Microsoft work or school account with LinkedIn. After a user connects their accounts, information and highlights from LinkedIn are available in some Microsoft apps and services.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.2 Users",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "LinkedIn account connections allow users to connect their Microsoft work or school account with LinkedIn. After a user connects their accounts, information and highlights from LinkedIn are available in some Microsoft apps and services.",
+ "RationaleStatement": "Disabling LinkedIn integration prevents potential phishing attacks and risk scenarios where an external party could accidentally disclose sensitive information.",
+ "ImpactStatement": "Users will not be able to sync contacts or use LinkedIn integration.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select User settings. 3. Under LinkedIn account connections select No. 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Users and select User settings. 3. Under LinkedIn account connections, verify that No is selected.",
+ "AdditionalInformation": "",
+ "DefaultValue": "LinkedIn integration is enabled by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/linkedin-integration:https://learn.microsoft.com/en-us/entra/identity/users/linkedin-user-consent"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3.1",
+ "Description": "This setting allows users in the organization to create new security groups and add members to these groups in the Azure portal, API, or PowerShell. These new groups also show up in the Access Panel for all other users. If the policy setting on the group allows it, other users can create requests to join these groups. The recommended state is Users can create security groups in Azure portals, API or PowerShell set to No.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.3 Groups",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting allows users in the organization to create new security groups and add members to these groups in the Azure portal, API, or PowerShell. These new groups also show up in the Access Panel for all other users. If the policy setting on the group allows it, other users can create requests to join these groups. The recommended state is Users can create security groups in Azure portals, API or PowerShell set to No.",
+ "RationaleStatement": "Allowing end users to create security groups without oversight can lead to uncontrolled group sprawl, increasing the risk of inappropriate access to sensitive data. The default assignment of group ownership to the creator introduces a potential for privilege escalation, especially if IT teams overlook how these groups are later used to manage access. A more malicious scenario arises when a compromised non-privileged user creates deceptively named security groups such as \"Accounting\" or \"Break-glass\", or uses homograph techniques to mimic legitimate group names. Third-party IT teams may be particularly susceptible, as they might not be familiar with the environment or lack consistent naming conventions. An unsuspecting administrator could then mistakenly assign elevated privileges, grant access to sensitive data, or exclude these groups from Conditional Access policies, inadvertently creating a serious security gap.",
+ "ImpactStatement": "Restrictions may introduce some operational friction, particularly in fast-paced or decentralized environments where teams rely on self-service capabilities for collaboration and access management. This can increase reliance on IT teams for routine tasks, potentially causing delays. However, these impacts can be minimized through automated approval workflows and clear governance processes.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Set Users can create security groups in Azure portals, API or PowerShell to No. 4. Click Save. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run the following commands: $params = @{ defaultUserRolePermissions = @{ AllowedToCreateSecurityGroups = $false } } Update-MgPolicyAuthorizationPolicy -BodyParameter $params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Verify that Users can create security groups in Azure portals, API or PowerShell is set to No. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: (Get-MgPolicyAuthorizationPolicy).DefaultUserRolePermissions | fl 3. Verify that AllowedToCreateSecurityGroups is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AllowedToCreateSecurityGroups : True",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/groups-self-service-management?WT.mc_id=Portal-Microsoft_AAD_IAM#group-settings:https://learn.microsoft.com/en-us/graph/api/authorizationpolicy-get?view=graph-rest-1.0&tabs=http:https://learn.microsoft.com/en-us/entra/identity/users/groups-self-service-management#making-a-group-available-for-end-user-self-service"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3.2",
+ "Description": "This setting restricts standard users from accessing the My Groups web interface in the My Account portal (https://myaccount.microsoft.com/groups). When set to Yes, this web interface access is removed for standard users. The recommended state is Yes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.3 Groups",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "This setting restricts standard users from accessing the My Groups web interface in the My Account portal (https://myaccount.microsoft.com/groups). When set to Yes, this web interface access is removed for standard users. The recommended state is Yes.",
+ "RationaleStatement": "By default, any authenticated user can access the My Groups portal and enumerate group memberships, SharePoint site URLs, group email addresses, Teams URLs, and Yammer URLs across the tenant. This information enables reconnaissance, where a user could identify high-value or privileged groups, map resource URLs, and use that data to plan further attacks or lateral movement. Restricting the web interface limits passive enumeration by users who do not require group browsing as part of their duties, reducing the available attack surface without impacting core productivity. Note: This setting applies only to the My Groups web interface. API-based enumeration remains possible for users with appropriate permissions or tooling, and this control should not be treated as a complete enumeration defense.",
+ "ImpactStatement": "Setting this to Yes creates administrative overhead for users who need to look up group memberships and must now request that information from an administrator.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Under Self Service Group Management, set Restrict user ability to access groups features in My Groups. Group and User Admin will have read-only access when the value of this setting is 'Yes' to Yes. 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Under Self Service Group Management, verify that Restrict user ability to access groups features in My Groups. Group and User Admin will have read-only access when the value of this setting is 'Yes' is set to Yes.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/groups-self-service-management"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3.3",
+ "Description": "Microsoft Entra ID provides self-service group management features that enable users to create and manage their own security groups or Microsoft 365 groups. The owner of the group can approve or deny membership requests and delegate control of group membership. Self-service group management features aren't available for mail-enabled security groups or distribution lists. The recommended state is No.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.3 Groups",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Microsoft Entra ID provides self-service group management features that enable users to create and manage their own security groups or Microsoft 365 groups. The owner of the group can approve or deny membership requests and delegate control of group membership. Self-service group management features aren't available for mail-enabled security groups or distribution lists. The recommended state is No.",
+ "RationaleStatement": "Group owners are standard users who may not have visibility into access governance requirements for a given group. Allowing owners to approve membership requests through My Groups means additions to security groups or Microsoft 365 groups can occur without administrator review, bypassing formal access provisioning controls. Unauthorized or excessive group membership can expand a user's effective permissions and increase the blast radius of a compromised account.",
+ "ImpactStatement": "Administrators will be responsible for managing group membership requests instead of group owners, which is the default behavior. Administrative overhead will only increase if this setting was previously changed to Yes.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups select General. 3. Set Owners can manage group membership requests in My Groups to No. 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Verify that Owners can manage group membership requests in My Groups is set to No",
+ "AdditionalInformation": "",
+ "DefaultValue": "No",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/groups-self-service-management#making-a-group-available-for-end-user-self-service"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.3.4",
+ "Description": "All users within a Microsoft Entra organization are permitted to create new Microsoft 365 groups and add members to those groups through the Azure portal, API, or PowerShell. Newly created groups also appear in the Access Panel for all other users. When the applicable group policy settings allow it, users can submit requests to join these groups. The recommended state is No.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.3 Groups",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "All users within a Microsoft Entra organization are permitted to create new Microsoft 365 groups and add members to those groups through the Azure portal, API, or PowerShell. Newly created groups also appear in the Access Panel for all other users. When the applicable group policy settings allow it, users can submit requests to join these groups. The recommended state is No.",
+ "RationaleStatement": "Restricting Microsoft 365 group creation to administrators only ensures that creation of Microsoft 365 groups is controlled by the administrator. Appropriate groups should be created and managed by the administrator and group creation rights should not be delegated to any other user.",
+ "ImpactStatement": "Enabling this setting could create a number of requests that would need to be managed by an administrator.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Set Users can create Microsoft 365 groups in Azure portals, API or PowerShell to No 4. Click Save. To remediate using the Microsoft Graph API: 1. Execute a PATCH request to the following relative URI: v1.0/groupSettings 2. Target the object with the templateId of 62375ab9-6b52-47ed-826b- 58e47e0e304b 3. Update EnableGroupCreation to false. Note: If a group with the above templateId doesn't exist this means the defaults are present and it would be advisable to use the UI to remediate, as this will automatically create the Group.Unified object with its defaults. Microsoft's documentation does cover using a POST request to build this using the API, however.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Groups and select General. 3. Verify that Users can create Microsoft 365 groups in Azure portals, API or PowerShell is set to No To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/groupSettings 2. Filter to groups with the templateId of 62375ab9-6b52-47ed-826b- 58e47e0e304b 3. Verify that EnableGroupCreation is false. 4. If the group with the above templateId does not exist, then it means the setting is in its default state and is not compliant.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Yes",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/solutions/manage-creation-of-groups:https://learn.microsoft.com/en-us/graph/api/group-list-settings?view=graph-rest-0&tabs=http:https://learn.microsoft.com/en-us/graph/api/groupsetting-update?view=graph-rest-1.0&tabs=http"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.1",
+ "Description": "This setting enables you to select the users who can register their devices as Microsoft Entra joined devices. The recommended state is Selected or None. Note: This setting is applicable only to Microsoft Entra join on Windows 10 or newer. This setting doesn't apply to Microsoft Entra hybrid joined devices, Microsoft Entra joined VMs in Azure, or Microsoft Entra joined devices that use Windows Autopilot self- deployment mode because these methods work in a userless context.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting enables you to select the users who can register their devices as Microsoft Entra joined devices. The recommended state is Selected or None. Note: This setting is applicable only to Microsoft Entra join on Windows 10 or newer. This setting doesn't apply to Microsoft Entra hybrid joined devices, Microsoft Entra joined VMs in Azure, or Microsoft Entra joined devices that use Windows Autopilot self- deployment mode because these methods work in a userless context.",
+ "RationaleStatement": "If a threat actor compromises a standard user account, they can enroll a rogue device under that user's identity. This device may inherit MDM policies and appear compliant, giving attackers persistent access to cloud resources without triggering MFA. In a 2023 blog, Microsoft IR reports that it has detected threat actors registering their own devices to the Microsoft Entra tenant, giving them a platform to escalate the cyberattack. While simply joining a device to a Microsoft Entra tenant may present limited immediate risk, it could allow a threat actor to establish a foothold in the environment.",
+ "ImpactStatement": "Restricting the setting requires IT teams to assign enrollment permissions to specific staff, such as helpdesk or provisioning personnel, which may impact user-driven Autopilot scenarios and increase administrative overhead for device onboarding and support.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Users may join devices to Microsoft Entra to Selected (and add members) or None.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Users may join devices to Microsoft Entra is set to Selected or None. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: beta/policies/deviceRegistrationPolicy 3. Verify that azureADJoin.allowedToJoin.@odata.type is one of the following: o #microsoft.graph.enumeratedDeviceRegistrationMembership (Selected) o #microsoft.graph.noDeviceRegistrationMembership (None). Note: When set to Selected, users and groups will also appear in the output of the Graph Request.",
+ "AdditionalInformation": "",
+ "DefaultValue": "All",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://www.microsoft.com/en-us/security/blog/2023/12/05/microsoft-incident-response-lessons-on-preventing-cloud-identity-compromise/#poor-device:https://learn.microsoft.com/en-us/graph/api/resources/deviceregistrationpolicy?view=graph-rest-beta"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.2",
+ "Description": "This setting defines the maximum number of Microsoft Entra joined or registered devices that a user can have in Microsoft Entra ID. Once this limit is reached, no additional devices can be added until existing ones are removed. Values above 100 are automatically capped at 100. The recommended state is 10 or less.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting defines the maximum number of Microsoft Entra joined or registered devices that a user can have in Microsoft Entra ID. Once this limit is reached, no additional devices can be added until existing ones are removed. Values above 100 are automatically capped at 100. The recommended state is 10 or less.",
+ "RationaleStatement": "Microsoft incident response teams have observed threat actors enrolling their own devices to establish persistence after a non-privileged user has been compromised. High device quotas can exacerbate this risk by enabling attackers to register multiple devices that appear legitimate, while also contributing to unmanaged or personal devices cluttering the environment, driving up licensing costs and complicating compliance efforts. Enforcing a reasonable device limit per user supports good governance, reduces the attack surface, and encourages administrators to reassess and clean up legacy or unused device enrollments.",
+ "ImpactStatement": "IT staff who need to enroll more than 10 devices on behalf of the organization must be assigned the role of Device Enrollment Manager in the Intune admin center. Device Enrollment Managers are non-administrator accounts that can enroll and manage up to 1,000 devices. It is recommended to use dedicated service accounts for this role rather than assigning it to users' primary or daily-use accounts. Warning: Do not delete accounts assigned as a Device enrollment manager if any devices were enrolled using the account. Doing so will lead to issues with these devices.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Maximum number of devices per user to 10 or less.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Maximum number of devices per user is set to 10 or less. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/policies/deviceRegistrationPolicy 2. Verify that userDeviceQuota is 10 or less.",
+ "AdditionalInformation": "",
+ "DefaultValue": "50",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://learn.microsoft.com/en-us/intune/intune-service/enrollment/device-enrollment-manager-enroll:https://learn.microsoft.com/en-us/graph/api/resources/deviceregistrationpolicy?view=graph-rest-beta"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.3",
+ "Description": "This setting controls whether the Global Administrator role is automatically added to the local administrators group on a device during the Microsoft Entra join process. The recommended state is No.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting controls whether the Global Administrator role is automatically added to the local administrators group on a device during the Microsoft Entra join process. The recommended state is No.",
+ "RationaleStatement": "System administrators may be inclined to use over-privileged accounts for convenience when managing devices. Enforcing this control helps discourage that behavior by requiring administrative actions to be performed using accounts specifically designated for local administration. This promotes adherence to the principle of least privilege and reduces the risk associated with using high-level roles for routine tasks. For example, using a Global Administrator account to authenticate to a compromised endpoint and continue performing tasks significantly increases the risk of broader organizational compromise.",
+ "ImpactStatement": "Restricting the default behavior and requiring manual assignment to least privilege roles introduces minor administrative overhead. During the Microsoft Entra join process, the Microsoft Entra Joined Device Local Administrator role is automatically added to the device's local administrators group and should be used instead.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Global administrator role is added as local administrator on the device during Microsoft Entra join (Preview) to No.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Global administrator role is added as local administrator on the device during Microsoft Entra join (Preview) is set to No. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: beta/policies/deviceRegistrationPolicy 2. Verify that azureADJoin.localAdmins.enableGlobalAdmins is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Yes",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://learn.microsoft.com/en-us/graph/api/resources/deviceregistrationpolicy?view=graph-rest-beta:https://learn.microsoft.com/en-us/entra/identity/devices/assign-local-admin"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.4",
+ "Description": "This setting determines if the Microsoft Entra user registering their device as Microsoft Entra join will be added to the local administrators group. This setting applies only once during the actual registration of the device as Microsoft Entra join. The recommended state is Selected or None.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting determines if the Microsoft Entra user registering their device as Microsoft Entra join will be added to the local administrators group. This setting applies only once during the actual registration of the device as Microsoft Entra join. The recommended state is Selected or None.",
+ "RationaleStatement": "To uphold the principle of least privilege, the assignment of local administrator rights during Microsoft Entra join should be centrally managed using appropriate built-in roles through Intune. This approach minimizes the number of disparate users with elevated privileges, reducing the attack surface and potential for misuse. Centralized management also streamlines the deprovisioning process, ensuring that administrative access can be revoked efficiently and consistently across all devices, rather than requiring manual intervention on each individual endpoint.",
+ "ImpactStatement": "Restricting the default behavior and requiring manual assignment to built-in roles introduces minor administrative overhead. During the Microsoft Entra join process, the Microsoft Entra Joined Device Local Administrator role is automatically added to the device's local administrators group and should be used instead.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Registering user is added as local administrator on the device during Microsoft Entra join (Preview) to Selected (and add members) or None.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Registering user is added as local administrator on the device during Microsoft Entra join (Preview) is set to Selected or None. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: beta/policies/deviceRegistrationPolicy 2. Verify that azureADJoin.localAdmins.registeringUsers.@odata.type is one of the following: o #microsoft.graph.enumeratedDeviceRegistrationMembership (Selected) o #microsoft.graph.noDeviceRegistrationMembership (None). Note: When set to Selected, users and groups will also appear in the output of the Graph Request.",
+ "AdditionalInformation": "",
+ "DefaultValue": "All",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://learn.microsoft.com/en-us/graph/api/resources/deviceregistrationpolicy?view=graph-rest-beta:https://learn.microsoft.com/en-us/entra/identity/devices/assign-local-admin"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.5",
+ "Description": "Local Administrator Password Solution (LAPS) is the management of local account passwords on Windows devices. LAPS provides a solution to securely manage and retrieve the built-in local admin password. With cloud version of LAPS, customers can enable storing and rotation of local admin passwords for both Microsoft Entra and Microsoft Entra hybrid join devices The recommended state is Yes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Local Administrator Password Solution (LAPS) is the management of local account passwords on Windows devices. LAPS provides a solution to securely manage and retrieve the built-in local admin password. With cloud version of LAPS, customers can enable storing and rotation of local admin passwords for both Microsoft Entra and Microsoft Entra hybrid join devices The recommended state is Yes.",
+ "RationaleStatement": "Managing local Administrator passwords across multiple systems can be challenging. As a result, many organizations opt to configure the same password on all workstations and/or member servers during deployment. However, this practice introduces a significant security risk: if an attacker compromises one system and obtains the local Administrator password, they can potentially gain administrative access to every other system using that same password. Additionally, enabling LAPS at the tenant level is a prerequisite for implementing LAPS- related recommendations outlined in the CIS Microsoft Intune for Windows Workstation Benchmarks. Note: Enabling LAPS at the tenant level does not automatically enforce password rotation for built-in Administrator accounts. To activate LAPS functionality, appropriate policies must be configured in Intune Settings Catalog or under the Endpoint security > Account protection blade. The CIS Microsoft 365 Foundations Benchmark focuses on hardening at the tenant level, while the CIS Intune Benchmarks focus on endpoint-specific configurations.",
+ "ImpactStatement": "Enabling LAPS requires some additional operational overhead. Although unlikely if a password is rotated and not retrieved or backed up before the device becomes unreachable (e.g., due to hardware failure, network isolation, or being decommissioned), administrators may be locked out.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Enable Microsoft Entra Local Administrator Password Solution (LAPS) to Yes.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Enable Microsoft Entra Local Administrator Password Solution (LAPS) is set to Yes. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/policies/deviceRegistrationPolicy 2. Verify that localAdminPassword.isEnabled is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://learn.microsoft.com/en-us/graph/api/resources/deviceregistrationpolicy?view=graph-rest-beta:https://learn.microsoft.com/en-us/entra/identity/devices/howto-manage-local-admin-passwords"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.4.6",
+ "Description": "This setting determines if users can self-service recover their BitLocker key(s). 'Yes' restricts non-admin users from being able to see the BitLocker key(s) for their owned devices if there are any. 'No' allows all users to recover their BitLocker key(s). The recommended state is Yes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.4 Devices",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting determines if users can self-service recover their BitLocker key(s). 'Yes' restricts non-admin users from being able to see the BitLocker key(s) for their owned devices if there are any. 'No' allows all users to recover their BitLocker key(s). The recommended state is Yes.",
+ "RationaleStatement": "Restricting user access to the self-service BitLocker recovery key portal helps mitigate the risk of recovery key exposure in the event of a compromised user account. If an attacker gains access to both the user's credentials and the physical device, they could potentially retrieve the recovery key and decrypt sensitive data. The recovery key itself is also considered sensitive information.",
+ "ImpactStatement": "Restricting this setting will increase administrative overhead and may introduce friction between end users and the helpdesk, as users will no longer be able to retrieve BitLocker recovery keys through the self-service portal. This portal was originally designed to streamline recovery and reduce support burden. During the CrowdStrike Falcon Sensor outage in July 2024, many endpoints entered recovery mode, and delays in accessing recovery keys contributed to prolonged downtime. Limiting self-service access could exacerbate such delays in future incidents, especially in large or distributed environments.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Set Restrict users from recovering the BitLocker key(s) for their owned devices to Yes. To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run the following: $params = @{ defaultUserRolePermissions = @{ AllowedToReadBitlockerKeysForOwnedDevice = $false } } Update-MgPolicyAuthorizationPolicy -BodyParameter $params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Devices and select Device settings. 3. Verify that Restrict users from recovering the BitLocker key(s) for their owned devices is set to Yes. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following: (Get-MgPolicyAuthorizationPolicy).DefaultUserRolePermissions | fl 3. Verify that AllowedToReadBitlockerKeysForOwnedDevice is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities#configure-device-settings:https://learn.microsoft.com/en-us/graph/api/authorizationpolicy-get?view=graph-rest-1.0:https://techcommunity.microsoft.com/blog/intunecustomersuccess/user-self-service-bitlocker-recovery-key-access-with-intune-company-portal-websi/4150458:https://learn.microsoft.com/en-us/windows/security/operating-system-security/data-protection/bitlocker/recovery-process#self-recovery"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.1",
+ "Description": "Control when end users and group owners are allowed to grant consent to applications, and when they will be required to request administrator review and approval. Allowing users to grant apps access to data helps them acquire useful applications and be productive but can represent a risk in some situations if it's not monitored and controlled carefully.",
+ "Checks": [
+ "entra_policy_restricts_user_consent_for_apps"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Control when end users and group owners are allowed to grant consent to applications, and when they will be required to request administrator review and approval. Allowing users to grant apps access to data helps them acquire useful applications and be productive but can represent a risk in some situations if it's not monitored and controlled carefully.",
+ "RationaleStatement": "Attackers commonly use custom applications to trick users into granting them access to company data. Restricting user consent mitigates this risk and helps to reduce the threat-surface.",
+ "ImpactStatement": "If user consent is disabled, previous consent grants will still be honored but all future consent operations must be performed by an administrator. Tenant-wide admin consent can be requested by users through an integrated administrator consent request workflow or through organizational support processes.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Consent and permissions > User consent settings. 4. Under User consent for applications select Do not allow user consent. 5. Click the Save option at the top of the window.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Consent and permissions > User consent settings. 4. Verify that User consent for applications is set to Do not allow user consent. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: (Get-MgPolicyAuthorizationPolicy).DefaultUserRolePermissions | Select-Object -ExpandProperty PermissionGrantPoliciesAssigned 3. Verify that the returned array does not contain either ManagePermissionGrantsForSelf.microsoft-user-default-low or ManagePermissionGrantsForSelf.microsoft-user-default-legacy. If either of these strings is present, the audit fails.",
+ "AdditionalInformation": "",
+ "DefaultValue": "UI - Allow user consent for apps",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-user-consent?pivots=portal:https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.identity.signins/get-mgpolicyauthorizationpolicy?view=graph-powershell-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.2",
+ "Description": "The admin consent workflow gives admins a secure way to grant access to applications that require admin approval. When a user tries to access an application but is unable to provide consent, they can send a request for admin approval. The request is sent via email to admins who have been designated as reviewers. A reviewer takes action on the request, and the user is notified of the action.",
+ "Checks": [
+ "entra_admin_consent_workflow_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The admin consent workflow gives admins a secure way to grant access to applications that require admin approval. When a user tries to access an application but is unable to provide consent, they can send a request for admin approval. The request is sent via email to admins who have been designated as reviewers. A reviewer takes action on the request, and the user is notified of the action.",
+ "RationaleStatement": "The admin consent workflow (Preview) gives admins a secure way to grant access to applications that require admin approval. When a user tries to access an application but is unable to provide consent, they can send a request for admin approval. The request is sent via email to admins who have been designated as reviewers. A reviewer acts on the request, and the user is notified of the action.",
+ "ImpactStatement": "To approve requests, a reviewer must be a global administrator, cloud application administrator, or application administrator. The reviewer must already have one of these admin roles assigned; simply designating them as a reviewer doesn't elevate their privileges.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Consent and permissions. 4. Under Manage select Admin consent settings. 5. Set Users can request admin consent to apps they are unable to consent to to Yes under Admin consent requests. 6. Under the Reviewers choose the Roles and Groups that will review user generated app consent requests. 7. Set Selected users will receive email notifications for requests to Yes 8. Select Save at the top of the window.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Consent and permissions. 4. Under Manage select Admin consent settings. 5. Verify that Users can request admin consent to apps they are unable to consent to is set to Yes. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: Get-MgPolicyAdminConsentRequestPolicy | fl IsEnabled,NotifyReviewers,RemindersEnabled 3. Verify that IsEnabled is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Users can request admin consent to apps they are unable to consent to: No - Selected users to review admin consent requests: None - Selected users will receive email notifications for requests: Yes - Selected users will receive request expiration reminders: Yes - Consent request expires after (days): 30",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.3",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using either certificate credentials or password credentials (also referred to as client secrets). This setting enforces a tenant-wide restriction that prevents new password credentials from being added to any application registration or service principal. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not revoke or invalidate existing password credentials; credentials created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Block password addition set to On.",
+ "Checks": [
+ "entra_default_app_management_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using either certificate credentials or password credentials (also referred to as client secrets). This setting enforces a tenant-wide restriction that prevents new password credentials from being added to any application registration or service principal. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not revoke or invalidate existing password credentials; credentials created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Block password addition set to On.",
+ "RationaleStatement": "Password credentials (client secrets) used for application authentication are static string values that offer weaker security guarantees than certificate or federated credentials. Unlike certificates, client secrets carry no built-in proof of possession and are frequently stored in plaintext in source code, configuration files, CI/CD pipelines, and shell history. A leaked client secret grants any holder the ability to authenticate as the application to Microsoft Entra ID, potentially accessing any resource or permission scope assigned to that application. Blocking the addition of new password credentials eliminates this attack surface for applications created going forward and forces adoption of stronger credential types such as certificates.",
+ "ImpactStatement": "This policy applies to new password credential additions only. Existing client secrets remain valid until they expire or are explicitly revoked; this recommendation does not retroactively invalidate credentials created before the policy was enabled. Any automated process, pipeline, or script that programmatically adds client secrets to application registrations or service principals will be blocked once the policy is enabled, unless an exception is configured. Applications that have not yet migrated to certificate- based authentication or workload identity federation will require changes before new credentials can be added.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Block password addition. 5. Set Status to On. 6. Set Applies to to one of the following: o All applications o All applications with exclusions (if using exclusions, ensure they are reviewed annually). 7. Set Only apply to apps created after to a desired date or leave it unconfigured. 8. Select Save and close to apply the changes. To remediate using the Microsoft Graph API: Important: The PATCH request replaces the passwordCredentials array in full. Retrieve the current policy first and include all existing entries in the request body to avoid overwriting other configured restrictions or exclusions. 1. Execute a GET request to retrieve the current policy: v1.0/policies/defaultAppManagementPolicy 2. Modify the returned JSON to reflect the following changes: - Set isEnabled to true. - Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is passwordAddition and set the following: o state to enabled o restrictForAppsCreatedAfterDateTime to 0001-01-01T00:00:00Z or a desired date. - Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is passwordAddition and set the following: o state to enabled o restrictForAppsCreatedAfterDateTime to 0001-01-01T00:00:00Z or a desired date. 3. Execute a PATCH request to the same URI with the modified JSON in the request body to apply the changes. Note: The References section includes a link to the API documentation with full remediation examples in multiple languages including HTTP, PowerShell, and Python.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Block password addition. 5. Verify that Status is set to On. 6. Verify that Applies to is set to one of the following: o All applications o All applications with exclusions (if using exclusions, verify they are reviewed annually). 7. Verify that Only apply to apps created after is one of the following states: o Not configured (Field will show Select a date with no date selected) o A date that is on or before the date of the assessment. 8. Compliance is met when all of the above conditions are satisfied. To audit using the Microsoft Graph API: Note: Both the application restrictions and service principal restrictions must be audited to ensure password addition is properly blocked, as they can be independently configured in Graph or PowerShell. The UI only surfaces the combined state of both settings. 1. Execute a GET request to the following relative URI to get the default app management policy: v1.0/policies/defaultAppManagementPolicy 2. Verify that isEnabled is true, this indicates that the default app management policy is enabled and being applied to the tenant. Part 1: Audit application restrictions 1. Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is passwordAddition. 2. Verify the following conditions are met for applicationRestrictions.passwordCredentials: o state is enabled o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Part 2: Audit service principal restrictions 1. Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is passwordAddition. 2. Verify the following conditions are met for servicePrincipalRestrictions.passwordCredentials: o state is enabled o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Note: Presently the API does not surface application exclusions, only excluded callers, so it is not necessary to audit them for compliance.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-app-management-policies?tabs=portal:https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/tutorial-enforce-secret-standards?pivots=ms-graph:https://learn.microsoft.com/en-us/graph/api/resources/tenantappmanagementpolicy?view=graph-rest-1.0:https://learn.microsoft.com/en-us/entra/fundamentals/zero-trust-protect-identities#enforce-standards-for-app-secrets-and-certificates"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.4",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using password credentials (also referred to as client secrets). This setting enforces a tenant- wide maximum lifetime for new password credentials added to any application registration or service principal. When enabled, any client secret created must have an expiration date that falls within the configured maximum, which for this recommendation is 180 days or less. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not retroactively shorten or invalidate existing password credentials; secrets created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Restrict max password lifetime set to On: 180 days or less.",
+ "Checks": [
+ "entra_default_app_management_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using password credentials (also referred to as client secrets). This setting enforces a tenant- wide maximum lifetime for new password credentials added to any application registration or service principal. When enabled, any client secret created must have an expiration date that falls within the configured maximum, which for this recommendation is 180 days or less. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not retroactively shorten or invalidate existing password credentials; secrets created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Restrict max password lifetime set to On: 180 days or less.",
+ "RationaleStatement": "Long-lived client secrets extend the window of exploitation if a credential is compromised. A secret valid for multiple years that is never rotated remains usable even if it was leaked in source code, a build log, or a security breach long after the initial exposure. Enforcing a maximum lifetime of 180 days ensures that client secrets expire on a regular basis, limiting the period during which a stolen credential remains valid and reducing the blast radius of a compromise. This control also encourages teams to establish automated rotation practices, which further reduces reliance on static, long- lived credentials.",
+ "ImpactStatement": "Any automated process, pipeline, or script that creates client secrets with a lifetime exceeding the configured maximum will fail once the policy is enabled, unless an exception is configured. Organizations will need to update secret creation workflows to specify expiration dates within the allowed range and establish rotation processes for secrets approaching expiry.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Restrict max password lifetime. 5. Set Status to On. 6. Set the maximum lifetime to 180 days or less. 7. Set Applies to to one of the following: o All applications o All applications with exclusions (if using exclusions, ensure they are reviewed annually). 8. Set Only apply to apps created after to a desired date or leave it unconfigured. 9. Select Save and close to apply the changes. To remediate using the Microsoft Graph API: Important: The PATCH request replaces the passwordCredentials array in full. Retrieve the current policy first and include all existing entries in the request body to avoid overwriting other configured restrictions or exclusions. 1. Execute a GET request to retrieve the current policy: v1.0/policies/defaultAppManagementPolicy 2. Modify the returned JSON to reflect the following changes: o Set isEnabled to true. o Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is passwordLifetime and set the following: - state to enabled - maxLifetime to P180D or a shorter duration. - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. o Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is passwordLifetime and set the following: - state to enabled - maxLifetime to P180D or a shorter duration. - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. 3. Execute a PATCH request to the same URI with the modified JSON in the request body to apply the changes. Note: The References section includes a link to the API documentation with full remediation examples in multiple languages including HTTP, PowerShell, and Python.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Restrict max password lifetime. 5. Verify that Status is set to On. 6. Verify that the configured maximum lifetime is 180 days or less. 7. Verify that Applies to is set to one of the following: o All applications o All applications with exclusions (if using exclusions, verify they are reviewed annually). 8. Verify that Only apply to apps created after is one of the following states: o Not configured (Field will show Select a date with no date selected) o A date that is on or before the date of the assessment. 9. Compliance is met when all of the above conditions are satisfied. To audit using the Microsoft Graph API: Note: Both the application restrictions and service principal restrictions must be audited to ensure the password lifetime is properly restricted, as they can be independently configured in Graph or PowerShell. The UI only surfaces the combined state of both settings. 1. Execute a GET request to the following relative URI to get the default app management policy: v1.0/policies/defaultAppManagementPolicy 2. Verify that isEnabled is true, this indicates that the default app management policy is enabled and being applied to the tenant. Part 1: Audit application restrictions 1. Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is passwordLifetime. 2. Verify the following conditions are met for applicationRestrictions.passwordCredentials: o state is enabled o maxLifetime is P180D or a shorter duration (e.g., P90D, P30D, etc.) o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Part 2: Audit service principal restrictions 1. Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is passwordLifetime. 2. Verify the following conditions are met for servicePrincipalRestrictions.passwordCredentials: o state is enabled o maxLifetime is P180D or a shorter duration (e.g., P90D, P30D, etc.) o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Note: Presently the API does not surface application exclusions, only excluded callers, so it is not necessary to audit them for compliance.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-app-management-policies?tabs=portal:https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/tutorial-enforce-secret-standards?pivots=ms-graph:https://learn.microsoft.com/en-us/graph/api/resources/tenantappmanagementpolicy?view=graph-rest-1.0:https://learn.microsoft.com/en-us/entra/fundamentals/zero-trust-protect-identities#enforce-standards-for-app-secrets-and-certificates"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.5",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using password credentials (also referred to as client secrets). By default, when adding a new password credential, the caller may supply a custom password value or allow the system to generate one. This setting enforces a tenant-wide restriction that blocks the use of custom password values, requiring all new password credentials to be system- generated. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not affect existing password credentials; credentials created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Block custom passwords set to On.",
+ "Checks": [
+ "entra_default_app_management_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using password credentials (also referred to as client secrets). By default, when adding a new password credential, the caller may supply a custom password value or allow the system to generate one. This setting enforces a tenant-wide restriction that blocks the use of custom password values, requiring all new password credentials to be system- generated. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not affect existing password credentials; credentials created before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Block custom passwords set to On.",
+ "RationaleStatement": "Custom password values are chosen by the caller and are susceptible to low entropy, predictable patterns, and reuse across multiple applications. A weak or reused client secret that is compromised through source code exposure, logging, or a supply-chain breach can be trivially exploited by an attacker to authenticate as the application. System-generated passwords use random values of sufficient length and complexity, making them resistant to brute-force and dictionary attacks. Blocking custom passwords removes the weakest credential creation path and ensures that all new client secrets meet a consistent entropy baseline.",
+ "ImpactStatement": "Any automated process, pipeline, or script that programmatically creates a client secret by supplying a custom password value will be blocked once the policy is enabled, unless an exception is configured. Most tooling, including the Microsoft Entra admin center, Azure CLI, and Azure PowerShell, already defaults to system-generated values, so the operational impact for typical workflows is minimal. Organizations that rely on custom password values in their automation will need to update those workflows to omit the custom value and accept the system-generated secret. Organizations that have policies or regulatory requirements that mandate specific password formats may need to maintain exclusions for certain applications. Exceptions should be scoped narrowly and reviewed regularly to minimize risk.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Block custom passwords. 5. Set Status to On. 6. Set Applies to to one of the following: o All applications o All applications with exclusions (if using exclusions, ensure they are reviewed annually). 7. Set Only apply to apps created after to a desired date or leave it unconfigured. 8. Select Save and close to apply the changes. To remediate using the Microsoft Graph API: Important: The PATCH request replaces the passwordCredentials array in full. Retrieve the current policy first and include all existing entries in the request body to avoid overwriting other configured restrictions or exclusions. 1. Execute a GET request to retrieve the current policy: v1.0/policies/defaultAppManagementPolicy 2. Modify the returned JSON to reflect the following changes: o Set isEnabled to true. o Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is customPasswordAddition and set the following: - state to enabled - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. o Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is customPasswordAddition and set the following: - state to enabled - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. 3. Execute a PATCH request to the same URI with the modified JSON in the request body to apply the changes. Note: The References section includes a link to the API documentation with full remediation examples in multiple languages including HTTP, PowerShell, and Python.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Block custom passwords. 5. Verify that Status is set to On. 6. Verify that Applies to is set to one of the following: o All applications o All applications with exclusions (if using exclusions, verify they are reviewed annually). 7. Verify that Only apply to apps created after is one of the following states: o Not configured (Field will show Select a date with no date selected) o A date that is on or before the date of the assessment. 8. Compliance is met when all of the above conditions are satisfied. To audit using the Microsoft Graph API: Note: Both the application restrictions and service principal restrictions must be audited to ensure custom password addition is properly blocked, as they can be independently configured in Graph or PowerShell. The UI only surfaces the combined state of both settings. 1. Execute a GET request to the following relative URI to get the default app management policy: v1.0/policies/defaultAppManagementPolicy 2. Verify that isEnabled is true, this indicates that the default app management policy is enabled and being applied to the tenant. Part 1: Audit application restrictions 1. Under applicationRestrictions.passwordCredentials, locate the entry where restrictionType is customPasswordAddition. 2. Verify the following conditions are met for applicationRestrictions.passwordCredentials: o state is enabled o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Part 2: Audit service principal restrictions 1. Under servicePrincipalRestrictions.passwordCredentials, locate the entry where restrictionType is customPasswordAddition. 2. Verify the following conditions are met for servicePrincipalRestrictions.passwordCredentials: o state is enabled o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Note: Presently the API does not surface application exclusions, only excluded callers, so it is not necessary to audit them for compliance.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-app-management-policies?tabs=portal:https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/tutorial-enforce-secret-standards?pivots=ms-graph:https://learn.microsoft.com/en-us/graph/api/resources/tenantappmanagementpolicy?view=graph-rest-1.0:https://learn.microsoft.com/en-us/entra/fundamentals/zero-trust-protect-identities#enforce-standards-for-app-secrets-and-certificates"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.5.6",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using certificate credentials. This setting enforces a tenant-wide maximum lifetime for new certificate credentials added to any application registration or service principal. When enabled, any certificate uploaded must have a validity period that falls within the configured maximum, which for this recommendation is 180 days or less. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not retroactively shorten or invalidate existing certificate credentials; certificates uploaded before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Restrict maximum certificate lifetime set to On: 180 days or less.",
+ "Checks": [
+ "entra_default_app_management_policy_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.5 Enterprise apps",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In Microsoft Entra ID, applications and service principals can authenticate using certificate credentials. This setting enforces a tenant-wide maximum lifetime for new certificate credentials added to any application registration or service principal. When enabled, any certificate uploaded must have a validity period that falls within the configured maximum, which for this recommendation is 180 days or less. The policy is implemented through the default app management policy and applies to all applications unless scoped exceptions are configured. The setting does not retroactively shorten or invalidate existing certificate credentials; certificates uploaded before the policy was enabled remain valid until they expire or are explicitly removed. The recommended state is Restrict maximum certificate lifetime set to On: 180 days or less.",
+ "RationaleStatement": "Long-lived certificates extend the window of exploitation if a credential is compromised. A certificate valid for multiple years that is never rotated remains usable even if the private key was exposed through a server breach, misconfigured storage, or supply- chain compromise long after the initial exposure. Enforcing a maximum lifetime of 180 days ensures that certificates expire on a regular basis, limiting the period during which a stolen credential remains valid and reducing the blast radius of a compromise. This control also encourages teams to establish automated certificate rotation practices, which further reduces reliance on static, long-lived credentials.",
+ "ImpactStatement": "Any automated process, pipeline, or script that uploads certificates with a validity period exceeding the configured maximum will be blocked once the policy is enabled, unless an exception is configured. Organizations will need to update certificate issuance workflows to generate certificates with expiration dates within the allowed range and establish rotation processes for certificates approaching expiry.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Restrict max certificate lifetime. 5. Set Status to On. 6. Set Applies to to one of the following: o All applications o All applications with exclusions (if using exclusions, ensure they are reviewed annually). 7. Set Only apply to apps created after to a desired date or leave it unconfigured. 8. Set Maximum lifetime (in days) to 180 days or less. 9. Select Save and close to apply the changes. To remediate using the Microsoft Graph API: 1. Execute a GET request to retrieve the current policy: v1.0/policies/defaultAppManagementPolicy 2. Modify the returned JSON to reflect the following changes: o Set isEnabled to true. o Under applicationRestrictions.keyCredentials, locate the entry where restrictionType is asymmetricKeyLifetime and set the following: - state to enabled - maxLifetime to P180D or a shorter duration. - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. o Under servicePrincipalRestrictions.keyCredentials, locate the entry where restrictionType is asymmetricKeyLifetime and set the following: - state to enabled - maxLifetime to P180D or a shorter duration. - restrictForAppsCreatedAfterDateTime to 0001-01- 01T00:00:00Z or a desired date. 3. Execute a PATCH request to the same URI with the modified JSON in the request body to apply the changes. Note: The References section includes a link to the API documentation with full remediation examples in multiple languages including HTTP, PowerShell, and Python.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID and select Enterprise apps. 3. Under Security select Application policies. 4. Select Restrict max certificate lifetime. 5. Verify that Status is set to On. 6. Verify that Applies to is set to one of the following: o All applications o All applications with exclusions (if using exclusions, verify they are reviewed annually). 7. Verify that Only apply to apps created after is one of the following states: o Not configured (Field will show Select a date with no date selected) o A date that is on or before the date of the assessment. 8. Verify that Maximum lifetime (in days) is 180 days or less. 9. Compliance is met when all of the above conditions are satisfied. To audit using the Microsoft Graph API: Note: Both the application restrictions and service principal restrictions must be audited to ensure the certificate lifetime is properly restricted, as they can be independently configured in Graph or PowerShell. The UI only surfaces the combined state of both settings. 1. Execute a GET request to the following relative URI to get the default app management policy: v1.0/policies/defaultAppManagementPolicy 2. Verify that isEnabled is true, this indicates that the default app management policy is enabled and being applied to the tenant. Part 1: Audit application restrictions 1. Under applicationRestrictions.keyCredentials, locate the entry where restrictionType is asymmetricKeyLifetime. 2. Verify the following conditions are met for applicationRestrictions.keyCredentials: o state is enabled o maxLifetime is P180D or a shorter duration (e.g., P90D, P30D, etc.) o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Part 2: Audit service principal restrictions 1. Under servicePrincipalRestrictions.keyCredentials, locate the entry where restrictionType is asymmetricKeyLifetime. 2. Verify the following conditions are met for servicePrincipalRestrictions.keyCredentials: o state is enabled o maxLifetime is P180D or a shorter duration (e.g., P90D, P30D, etc.) o restrictForAppsCreatedAfterDateTime is one of the following states: - 0001-01-01T00:00:00Z (not configured) - A date that is on or before the date of the assessment. 3. Compliance is met when all of the above conditions are satisfied. Note: Presently the API does not surface application exclusions, only excluded callers, so it is not necessary to audit them for compliance.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-app-management-policies?tabs=portal:https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/tutorial-enforce-secret-standards?pivots=ms-graph:https://learn.microsoft.com/en-us/graph/api/resources/tenantappmanagementpolicy?view=graph-rest-1.0:https://learn.microsoft.com/en-us/entra/fundamentals/zero-trust-protect-identities#enforce-standards-for-app-secrets-and-certificates"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.6.1",
+ "Description": "B2B collaboration is a feature within Microsoft Entra External ID that allows for guest invitations to an organization. Ensure users can only send invitations to specified domains. Note: This list works independently from OneDrive for Business and SharePoint Online allow/block lists. To restrict individual file sharing in SharePoint Online, set up an allow or blocklist for OneDrive for Business and SharePoint Online. For instance, in SharePoint or OneDrive users can still share with external users from prohibited domains by using Anyone links if they haven't been disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.6 External Identities",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "B2B collaboration is a feature within Microsoft Entra External ID that allows for guest invitations to an organization. Ensure users can only send invitations to specified domains. Note: This list works independently from OneDrive for Business and SharePoint Online allow/block lists. To restrict individual file sharing in SharePoint Online, set up an allow or blocklist for OneDrive for Business and SharePoint Online. For instance, in SharePoint or OneDrive users can still share with external users from prohibited domains by using Anyone links if they haven't been disabled.",
+ "RationaleStatement": "By specifying allowed domains for collaborations, external user's companies are explicitly identified. Also, this prevents internal users from inviting unknown external users such as personal accounts and granting them access to resources.",
+ "ImpactStatement": "This could make collaboration more difficult if the setting is not quickly updated when a new domain is identified as \"allowed\".",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Collaboration restrictions, select Allow invitations only to the specified domains (most restrictive) is selected. Then specify the allowed domains under Target domains.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Collaboration restrictions, verify that Allow invitations only to the specified domains (most restrictive) is selected. Then verify allowed domains are specified under Target domains. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following: $Uri = \"https://graph.microsoft.com/beta/legacy/policies\" $Response = (Invoke-MgGraphRequest -Uri $Uri).value | Where-Object { $_.type -eq 'B2BManagementPolicy' } if ($Response) { $Definition = $Response.definition | ConvertFrom-Json $DomainsPolicy = $Definition.B2BManagementPolicy.InvitationsAllowedAndBlockedDomainsPolicy } else { Write-Output \"No policy found.\" return } $DomainsPolicy 3. Verify that the output includes an AllowedDomains property that either contains no domains or lists only organizationally approved domains. If a BlockedDomains property is present, the configuration is considered non-compliant. Example of a compliant output with AllowedDomains defined: AllowedDomains -------------- {cisecurity.org, contoso.com, example.com} Allowed with no domains allowed (also compliant): AllowedDomains -------------- {}",
+ "AdditionalInformation": "",
+ "DefaultValue": "Allow invitations to be sent to any domain (most inclusive)",
+ "References": "https://learn.microsoft.com/en-us/entra/external-id/allow-deny-list:https://learn.microsoft.com/en-us/entra/external-id/what-is-b2b"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.6.2",
+ "Description": "Microsoft Entra ID, part of Microsoft Entra, allows you to restrict what external guest users can see in their organization in Microsoft Entra ID. Guest users are set to a limited permission level by default in Microsoft Entra ID, while the default for member users is the full set of user permissions. These directory level permissions are enforced across Microsoft Entra services including Microsoft Graph, PowerShell v2, the Azure portal, and My Apps portal. Microsoft 365 services leveraging Microsoft 365 groups for collaboration scenarios are also affected, specifically Outlook, Microsoft Teams, and SharePoint. They do not override the SharePoint or Microsoft Teams guest settings. The recommended state is at least Guest users have limited access to properties and memberships of directory objects or more restrictive.",
+ "Checks": [
+ "entra_policy_guest_users_access_restrictions"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.6 External Identities",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID, part of Microsoft Entra, allows you to restrict what external guest users can see in their organization in Microsoft Entra ID. Guest users are set to a limited permission level by default in Microsoft Entra ID, while the default for member users is the full set of user permissions. These directory level permissions are enforced across Microsoft Entra services including Microsoft Graph, PowerShell v2, the Azure portal, and My Apps portal. Microsoft 365 services leveraging Microsoft 365 groups for collaboration scenarios are also affected, specifically Outlook, Microsoft Teams, and SharePoint. They do not override the SharePoint or Microsoft Teams guest settings. The recommended state is at least Guest users have limited access to properties and memberships of directory objects or more restrictive.",
+ "RationaleStatement": "By limiting guest access to the most restrictive state this helps prevent malicious group and user object enumeration in the Microsoft 365 environment. This first step, known as reconnaissance in The Cyber Kill Chain, is often conducted by attackers prior to more advanced targeted attacks.",
+ "ImpactStatement": "The default is Guest users have limited access to properties and memberships of directory objects. When using the 'most restrictive' setting, guests will only be able to access their own profiles and will not be allowed to see other users' profiles, groups, or group memberships. There are some known issues with Yammer that will prevent guests that are signed in from leaving the group.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Guest user access set Guest user access restrictions to one of the following: o Guest users have limited access to properties and memberships of directory objects o Guest user access is restricted to properties and memberships of their own directory objects (most restrictive) To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run the following command to set the guest user access restrictions to default: # Guest users have limited access to properties and memberships of directory objects Update-MgPolicyAuthorizationPolicy -GuestUserRoleId '10dae51f-b6af-4016-8d66- 8c2a99b929b3' 3. Or, run the following command to set it to the \"most restrictive\": # Guest user access is restricted to properties and memberships of their own directory objects (most restrictive) Update-MgPolicyAuthorizationPolicy -GuestUserRoleId '2af84b1e-32c8-42b7-82bc- daa82404023b' Note: Either setting allows for a passing state.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Guest user access verify that Guest user access restrictions is set to one of the following: o Guest users have limited access to properties and memberships of directory objects o Guest user access is restricted to properties and memberships of their own directory objects (most restrictive) To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: Get-MgPolicyAuthorizationPolicy | fl GuestUserRoleId 3. Verify that the value returned is 10dae51f-b6af-4016-8d66-8c2a99b929b3 or 2af84b1e-32c8-42b7-82bc-daa82404023b (most restrictive) Note: Either setting allows for a passing state. Note 2: The value of a0b1b346-4d3e-4e8b-98f8-753987be4970 is equal to Guest users have the same access as members (most inclusive) and should not be used.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- UI: Guest users have limited access to properties and memberships of directory objects - PowerShell: 10dae51f-b6af-4016-8d66-8c2a99b929b3",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/users/users-restrict-guest-permissions:https://www.lockheedmartin.com/en-us/capabilities/cyber/cyber-kill-chain.html"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.6.3",
+ "Description": "By default, all users in the organization, including B2B collaboration guest users, can invite external users to B2B collaboration. The ability to send invitations can be limited by turning it on or off for everyone, or by restricting invitations to certain roles. The recommended state is Only users assigned to specific admin roles can invite guest users or No one in the organization can invite guest users including admins (most restrictive).",
+ "Checks": [
+ "entra_policy_guest_invite_only_for_admin_roles"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.6 External Identities",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "By default, all users in the organization, including B2B collaboration guest users, can invite external users to B2B collaboration. The ability to send invitations can be limited by turning it on or off for everyone, or by restricting invitations to certain roles. The recommended state is Only users assigned to specific admin roles can invite guest users or No one in the organization can invite guest users including admins (most restrictive).",
+ "RationaleStatement": "Restricting who can invite guests limits the exposure the organization might face from unauthorized accounts. The default behavior allows anyone within the organization to invite guests and non-admins to the tenant, posing a security risk.",
+ "ImpactStatement": "This introduces an obstacle to collaboration by restricting who can invite guest users to the organization. Designated Guest Inviters must be assigned, and an approval process established and clearly communicated to all users.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Guest invite settings set Guest invite restrictions to one of the desired compliant states: o Only users assigned to specific admin roles can invite guest users o No one in the organization can invite guest users including admins (most restrictive) To remediate using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.Authorization\" 2. Run one of the following PowerShell commands depending on the desired compliant state: To set to Only users assigned to specific admin roles can invite guest users: Update-MgPolicyAuthorizationPolicy -AllowInvitesFrom 'adminsAndGuestInviters' To set to No one in the organization can invite guest users including admins (most restrictive): Update-MgPolicyAuthorizationPolicy -AllowInvitesFrom \"none\"",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > External Identities and select External collaboration settings. 3. Under Guest invite settings verify that Guest invite restrictions is set to one of the following: o Only users assigned to specific admin roles can invite guest users o No one in the organization can invite guest users including admins (most restrictive) To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following command: Get-MgPolicyAuthorizationPolicy | fl AllowInvitesFrom 3. Verify the value returned is adminsAndGuestInviters or none.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- UI: Anyone in the organization can invite guest users including guests and non-admins (most inclusive) - PowerShell: everyone",
+ "References": "https://learn.microsoft.com/en-us/entra/external-id/external-collaboration-settings-configure:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#guest-inviter"
+ }
+ ]
+ },
+ {
+ "Id": "5.1.8.1",
+ "Description": "Password Hash Synchronization is one of the sign-in methods used to enable hybrid identity authentication. With this method, Microsoft Entra Connect synchronizes a cryptographically derived representation of a user's on-premises Active Directory password to Microsoft Entra ID. The original NT password hash (MD4) is never transmitted to Entra ID. Instead, Entra Connect computes a SHA-256 hash of the original MD4 hash and synchronizes that value. Because only this secondary hash is stored in the cloud, the credential material in Entra ID cannot be reused for on-premises pass-the-hash attacks, even if compromised. Note: The audit and remediation procedures described in this recommendation are applicable only to Microsoft 365 tenants operating in a hybrid identity configuration using Microsoft Entra Connect. They do not apply to federated or cloud-only deployments.",
+ "Checks": [
+ "entra_password_hash_sync_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.1.8 Hybrid management",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Password Hash Synchronization is one of the sign-in methods used to enable hybrid identity authentication. With this method, Microsoft Entra Connect synchronizes a cryptographically derived representation of a user's on-premises Active Directory password to Microsoft Entra ID. The original NT password hash (MD4) is never transmitted to Entra ID. Instead, Entra Connect computes a SHA-256 hash of the original MD4 hash and synchronizes that value. Because only this secondary hash is stored in the cloud, the credential material in Entra ID cannot be reused for on-premises pass-the-hash attacks, even if compromised. Note: The audit and remediation procedures described in this recommendation are applicable only to Microsoft 365 tenants operating in a hybrid identity configuration using Microsoft Entra Connect. They do not apply to federated or cloud-only deployments.",
+ "RationaleStatement": "Password hash synchronization helps by reducing the number of passwords your users need to maintain to just one and enables leaked credential detection for your hybrid accounts. Leaked credential protection is leveraged through Entra ID Protection and is a subset of that feature which can help identify if an organization's user account passwords have appeared on the dark web or public spaces. Using other options for your directory synchronization may be less resilient as Microsoft can still process sign-ins to 365 with Hash Sync even if a network connection to your on-premises environment is not available. This minimizes downtime and ensures business continuity.",
+ "ImpactStatement": "Compliance or regulatory restrictions may exist, depending on the organization's business sector, that preclude hashed versions of passwords from being securely transmitted to cloud data centers.",
+ "RemediationProcedure": "To remediate using the on-prem Microsoft Entra Connect tool: 1. Log in to the on premises server that hosts the Microsoft Entra Connect tool 2. Double-click the Azure AD Connect icon that was created on the desktop 3. Click Configure. 4. On the Additional tasks page, select Customize synchronization options and click Next. 5. Enter the username and password for your global administrator. 6. On the Connect your directories screen, click Next. 7. On the Domain and OU filtering screen, click Next. 8. On the Optional features screen, check Password hash synchronization and click Next. 9. On the Ready to configure screen click Configure. 10. Once the configuration completes, click Exit.",
+ "AuditProcedure": "To audit using the UI: Only Global Admin and Hybrid Identity Administrator roles have access to view the actual Password Hash Sync status message. Inadequate role access will result in a default message stating: \"Unable to retrieve your tenant's password hash sync information.\" 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Entra Connect. 3. Select Connect Sync. 4. Under Microsoft Entra Connect sync, verify the Password Hash Sync status message indicates that synchronization is occurring and no errors are present, with one of the following messages: o Password hash synchronization is enabled o Password hash synchronization cloud configuration is enabled o Password hash synchronization heartbeat detected To audit using the Microsoft Graph API: Permission required: OnPremDirectorySynchronization.Read.All 1. Execute a GET request to the following relative URI: v1.0/directory/onPremisesSynchronization 2. Verify that features.passwordSyncEnabled is true. To audit for the on-prem tool: 1. Log in to the server that hosts the Microsoft Entra Connect tool. 2. Run Azure AD Connect, and then click Configure and View or export current configuration. 3. Verify that PASSWORD HASH SYNCHRONIZATION is enabled on your tenant. To audit using PowerShell: 1. Open PowerShell on the on-premises server running Microsoft Entra Connect. 2. Run the following cmdlet: Get-ADSyncAADCompanyFeature 3. Verify that PasswordHashSync is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Microsoft Entra Connect sync disabled by default - Password Hash Sync is Microsoft's recommended setting for new deployments",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/whatis-phs:https://www.microsoft.com/en-us/download/details.aspx?id=47594:https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-staging-server:https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-password-hash-synchronization:https://learn.microsoft.com/en-us/graph/api/resources/onpremisesdirectorysynchronizationfeature?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.1",
+ "Description": "Multifactor authentication is a process that requires an additional form of identification during the sign-in process, such as a code from a mobile device or a fingerprint scan, to enhance security. Ensure users in administrator roles have MFA capabilities enabled.",
+ "Checks": [
+ "entra_admin_users_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Multifactor authentication is a process that requires an additional form of identification during the sign-in process, such as a code from a mobile device or a fingerprint scan, to enhance security. Ensure users in administrator roles have MFA capabilities enabled.",
+ "RationaleStatement": "Multifactor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Multifactor authentication provides additional assurance that the individual attempting to gain access is who they claim to be. With multifactor authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk. Note: To ensure that accounts cannot be easily used to enumerate resources (reconnaissance) through Microsoft Admin Portals or through Microsoft Azure Service Management API, both MFA conditional access policies must target All Resources: - \"Ensure multifactor authentication is enabled for all users\" and - \"Ensure multifactor authentication is enabled for all users in administrative roles\" (this recommendation)",
+ "ImpactStatement": "Implementation of multifactor authentication for all users in administrative roles will necessitate a change to user routine. All users in administrative roles will be required to enroll in multifactor authentication using phone, SMS, or an authentication application. After enrollment, use of multifactor authentication will be required for future access to the environment.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Click New policy. o Under Users or agents (Preview) include Select users and groups and check Directory roles. o At a minimum, include the directory roles listed below in this section of the document. o Under Target resources include All resources (formerly 'All cloud apps') and do not create any exclusions. - Under Exclude exclude any break-glass accounts. o Under Grant select Grant Access and check either Require multifactor authentication or Require authentication strength. o Click Select at the bottom of the pane. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On. At minimum these directory roles should be included for MFA: - Application administrator - Authentication administrator - Billing administrator - Cloud application administrator - Conditional Access administrator - Exchange administrator - Global administrator - Global reader - Helpdesk administrator - Password administrator - Privileged authentication administrator - Privileged role administrator - Security administrator - SharePoint administrator - User administrator",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify Directory roles specific to administrators are included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected with no exclusions. o Under Grant verify Grant Access is on and either Require multifactor authentication or Require authentication strength is checked. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. For each policy returned, verify the following criteria: o Conditions.Users.IncludeRoles contains the directory roles specific to administrators* o Conditions.Applications.IncludeApplications is All o GrantControls.BuiltInControls contains mfa OR GrantControls.AuthenticationStrength.id is defined o State is enabled 3. Compliance is met when at least one policy is found to meet all the criteria listed above. 4. Verify that any exclusions are documented and reviewed annually. Note: The Authentication Strength requirement is satisfied when any valid GUID is present in the authenticationStrength property of a matching policy. Because Authentication Strength configurations are inherently stronger than the built-in Require multifactor authentication control, the presence of a valid Authentication Strength also fulfills the MFA requirement for all users. Note: A list of Directory roles can be found in the Remediation section.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/howto-conditional-access-policy-admin-mfa:https://learn.microsoft.com/en-us/graph/api/conditionalaccessroot-list-policies?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.2",
+ "Description": "Enable multifactor authentication for all users in the Microsoft 365 tenant. Users will be prompted to authenticate with a second factor upon logging in to Microsoft 365 services. The second factor is most commonly a text message to a registered mobile phone number where they type in an authorization code, or with a mobile application like Microsoft Authenticator. Note: Since 2024, Microsoft has been rolling out mandatory multifactor authentication.",
+ "Checks": [
+ "entra_users_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Enable multifactor authentication for all users in the Microsoft 365 tenant. Users will be prompted to authenticate with a second factor upon logging in to Microsoft 365 services. The second factor is most commonly a text message to a registered mobile phone number where they type in an authorization code, or with a mobile application like Microsoft Authenticator. Note: Since 2024, Microsoft has been rolling out mandatory multifactor authentication.",
+ "RationaleStatement": "Multifactor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Multifactor authentication provides additional assurance that the individual attempting to gain access is who they claim to be. With multifactor authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk. Note: To ensure that accounts cannot be easily used to enumerate resources (reconnaissance) through Microsoft Admin Portals or through Microsoft Azure Service Management API, both MFA conditional access policies must target All Resources: - \"Ensure multifactor authentication is enabled for all users in administrative roles\" and - \"Ensure multifactor authentication is enabled for all users\" (this recommendation)",
+ "ImpactStatement": "Implementation of multifactor authentication for all users will necessitate a change to user routine. All users will be required to enroll in multifactor authentication using phone, SMS, or an authentication application. After enrollment, use of multifactor authentication will be required for future authentication to the environment. External identities that attempt to access documents that utilize Purview Information Protection (Sensitivity Labels) will find their access disrupted. In order to mitigate this create an exclusion for Microsoft Rights Management Services ID: 00000012- 0000-0000-c000-000000000000 Note: Organizations that struggle to enforce MFA globally due to budget constraints preventing the provision of company-owned mobile devices to every user, or due to regulations, unions, or policies that prevent forcing end users to use their personal devices, have another option. FIDO2 security keys can be used as an alternative. They are more secure, phishing-resistant, and affordable for organizations to issue to every end user.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Click New policy. o Under Users or agents (Preview) include All users. o Under Target resources include All resources (formerly 'All cloud apps') and do not create any exclusions. - Under Exclude exclude any break-glass accounts. o Under Grant select Grant Access and check either Require multifactor authentication or Require authentication strength. o Click Select at the bottom of the pane. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected with no exclusions. o Under Grant verify Grant Access and either Require multifactor authentication or Require authentication strength is checked. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o GrantControls.BuiltInControls contains mfa OR GrantControls.AuthenticationStrength.id is defined o State is enabled 3. Compliance is met when at least one policy is found to meet all the criteria listed above. 4. Verify that any exclusions are documented and reviewed annually. Note: The Authentication Strength requirement is satisfied when any valid GUID is present in the authenticationStrength property of a matching policy. Because Authentication Strength configurations are inherently stronger than the built-in Require multifactor authentication control, the presence of a valid Authentication Strength also fulfills the MFA requirement for all users.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. It may be present as a Microsoft-managed policy or created from a Conditional Access template.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/howto-conditional-access-policy-all-users-mfa:https://learn.microsoft.com/en-us/graph/api/conditionalaccessroot-list-policies?view=graph-rest-1.0:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mandatory-multifactor-authentication"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.3",
+ "Description": "Entra ID supports the most widely used authentication and authorization protocols including legacy authentication. This authentication pattern includes basic authentication, a widely used industry-standard method for collecting username and password information. The following messaging protocols support legacy authentication: - Authenticated SMTP - Used to send authenticated email messages. - Autodiscover - Used by Outlook and EAS clients to find and connect to mailboxes in Exchange Online. - Exchange ActiveSync (EAS) - Used to connect to mailboxes in Exchange Online. - Exchange Online PowerShell - Used to connect to Exchange Online with remote PowerShell. If you block Basic authentication for Exchange Online PowerShell, you need to use the Exchange Online PowerShell Module to connect. For instructions, see Connect to Exchange Online PowerShell using multifactor authentication. - Exchange Web Services (EWS) - A programming interface that's used by Outlook, Outlook for Mac, and third-party apps. - IMAP4 - Used by IMAP email clients. - MAPI over HTTP (MAPI/HTTP) - Primary mailbox access protocol used by Outlook 2010 SP2 and later. - Offline Address Book (OAB) - A copy of address list collections that are downloaded and used by Outlook. - Outlook Anywhere (RPC over HTTP) - Legacy mailbox access protocol supported by all current Outlook versions. - POP3 - Used by POP email clients. - Reporting Web Services - Used to retrieve report data in Exchange Online. - Universal Outlook - Used by the Mail and Calendar app for Windows 10. - Other clients - Other protocols identified as utilizing legacy authentication.",
+ "Checks": [
+ "entra_legacy_authentication_blocked"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Entra ID supports the most widely used authentication and authorization protocols including legacy authentication. This authentication pattern includes basic authentication, a widely used industry-standard method for collecting username and password information. The following messaging protocols support legacy authentication: - Authenticated SMTP - Used to send authenticated email messages. - Autodiscover - Used by Outlook and EAS clients to find and connect to mailboxes in Exchange Online. - Exchange ActiveSync (EAS) - Used to connect to mailboxes in Exchange Online. - Exchange Online PowerShell - Used to connect to Exchange Online with remote PowerShell. If you block Basic authentication for Exchange Online PowerShell, you need to use the Exchange Online PowerShell Module to connect. For instructions, see Connect to Exchange Online PowerShell using multifactor authentication. - Exchange Web Services (EWS) - A programming interface that's used by Outlook, Outlook for Mac, and third-party apps. - IMAP4 - Used by IMAP email clients. - MAPI over HTTP (MAPI/HTTP) - Primary mailbox access protocol used by Outlook 2010 SP2 and later. - Offline Address Book (OAB) - A copy of address list collections that are downloaded and used by Outlook. - Outlook Anywhere (RPC over HTTP) - Legacy mailbox access protocol supported by all current Outlook versions. - POP3 - Used by POP email clients. - Reporting Web Services - Used to retrieve report data in Exchange Online. - Universal Outlook - Used by the Mail and Calendar app for Windows 10. - Other clients - Other protocols identified as utilizing legacy authentication.",
+ "RationaleStatement": "Legacy authentication protocols do not support multi-factor authentication. These protocols are often used by attackers because of this deficiency. Blocking legacy authentication makes it harder for attackers to gain access. Note: Basic authentication is now disabled in all tenants. Before December 31 2022, you could re-enable the affected protocols if users and apps in your tenant couldn't connect. Now no one (you or Microsoft support) can re-enable Basic authentication in your tenant.",
+ "ImpactStatement": "Enabling this setting will block legacy authentication, preventing access from older versions of Microsoft Office, Exchange ActiveSync, and protocols such as IMAP, POP, and SMTP. As a result, some users may need to upgrade to newer Office versions or use email clients that support modern authentication. This change may also affect multifunction devices (MFPs), such as printers using legacy authentication for scan-to-email. Microsoft provides mail flow best practices (linked below) to configure MFPs without relying on legacy authentication. https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a- multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Conditions select Client apps and check the boxes for Exchange ActiveSync clients and Other clients. o Under Grant select Block Access. o Click Select. 4. Set the policy On and click Create.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected. o Verify that only documented resource exclusions exist and that they are reviewed annually. o Under Conditions select Client apps then verify Exchange ActiveSync clients and Other clients is checked. o Under Grant verify Block access is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.ClientAppTypes contains exchangeActiveSync OR other. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o Conditions.ClientAppTypes contains exchangeActiveSync o Conditions.ClientAppTypes contains other o GrantControls.BuiltInControls is block o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Basic authentication is disabled by default as of January 2023.",
+ "References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/disable-basic-authentication-in-exchange-online:https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365:https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.4",
+ "Description": "In complex deployments, organizations might have a need to restrict authentication sessions. Conditional Access policies allow for the targeting of specific user accounts. Some scenarios might include: - Resource access from an unmanaged or shared device - Access to sensitive information from an external network - High-privileged users - Business-critical applications Note: This CA policy can be added to the previous CA policy in this benchmark \"Ensure multifactor authentication is enabled for all users in administrative roles\"",
+ "Checks": [
+ "entra_admin_users_sign_in_frequency_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "In complex deployments, organizations might have a need to restrict authentication sessions. Conditional Access policies allow for the targeting of specific user accounts. Some scenarios might include: - Resource access from an unmanaged or shared device - Access to sensitive information from an external network - High-privileged users - Business-critical applications Note: This CA policy can be added to the previous CA policy in this benchmark \"Ensure multifactor authentication is enabled for all users in administrative roles\"",
+ "RationaleStatement": "Forcing a time out for MFA will help ensure that sessions are not kept alive for an indefinite period of time, ensuring that browser sessions are not persistent will help in prevention of drive-by attacks in web browsers, this also prevents creation and saving of session cookies leaving nothing for an attacker to take.",
+ "ImpactStatement": "Users with Administrative roles will be prompted at the frequency set for MFA.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Conditional Access and select Policies. 3. Click New policy. o Under Users or agents (Preview) include Select users and groups and check Directory roles. o At a minimum, include the directory roles listed below in this section of the document. o Under Target resources include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Grant select Grant Access and check Require multifactor authentication. o Under Session select Sign-in frequency select Periodic reauthentication and set it to 4 hours (or less). o Check Persistent browser session then select Never persistent in the drop-down menu. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On. At minimum these directory roles should be included in the policy: - Application administrator - Authentication administrator - Billing administrator - Cloud application administrator - Conditional Access administrator - Exchange administrator - Global administrator - Global reader - Helpdesk administrator - Password administrator - Privileged authentication administrator - Privileged role administrator - Security administrator - SharePoint administrator - User administrator",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify Directory roles specific to administrators are included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected. o Verify that only documented resource exclusions exist and that they are reviewed annually. o Under Session verify Sign-in frequency is checked and set to Periodic reauthentication. o Verify the timeframe is set to the time determined by the organization. o Verify that Periodic reauthentication does not exceed 4 hours (or less). o Verify that Persistent browser session is set to Never persistent. 4. Verify that Enable policy is set to On To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where SessionControls.PersistentBrowser.IsEnabled is true. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeRoles contains the directory roles specific to administrators* o Conditions.Applications.IncludeApplications is All o SessionControls.SignInFrequency.IsEnabled is true o SessionControls.SignInFrequency.FrequencyInterval is everyTime OR is timeBased AND does not exceed 4 hours. o SessionControls.PersistentBrowser.IsEnabled is true o SessionControls.PersistentBrowser.Mode is never o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually. Note: A list of directory roles applying to Administrators can be found in the remediation section.",
+ "AdditionalInformation": "",
+ "DefaultValue": "The default configuration for user sign-in frequency is a rolling window of 90 days.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/howto-conditional-access-session-lifetime"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.5",
+ "Description": "Authentication strength is a Conditional Access control that allows administrators to specify which combination of authentication methods can be used to access a resource. For example, they can make only phishing-resistant authentication methods available to access a sensitive resource. But to access a non-sensitive resource, they can allow less secure multifactor authentication (MFA) combinations, such as password + SMS. Microsoft has 3 built-in authentication strengths. MFA strength, Passwordless MFA strength, and Phishing-resistant MFA strength. Ensure administrator roles are using a CA policy with Phishing-resistant MFA strength. Administrators can then enroll using one of 3 methods: - FIDO2 Security Key - Windows Hello for Business - Certificate-based authentication (Multi-Factor) Note: Additional steps to configure methods such as FIDO2 keys are not covered here but can be found in related MS articles in the references section. The Conditional Access policy only ensures 1 of the 3 methods is used. Warning: Administrators should be pre-registered for a strong authentication mechanism before this Conditional Access Policy is enforced. Additionally, as stated elsewhere in the CIS Benchmark a break-glass administrator account should be excluded from this policy to ensure unfettered access in the case of an emergency.",
+ "Checks": [
+ "entra_admin_users_phishing_resistant_mfa_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Authentication strength is a Conditional Access control that allows administrators to specify which combination of authentication methods can be used to access a resource. For example, they can make only phishing-resistant authentication methods available to access a sensitive resource. But to access a non-sensitive resource, they can allow less secure multifactor authentication (MFA) combinations, such as password + SMS. Microsoft has 3 built-in authentication strengths. MFA strength, Passwordless MFA strength, and Phishing-resistant MFA strength. Ensure administrator roles are using a CA policy with Phishing-resistant MFA strength. Administrators can then enroll using one of 3 methods: - FIDO2 Security Key - Windows Hello for Business - Certificate-based authentication (Multi-Factor) Note: Additional steps to configure methods such as FIDO2 keys are not covered here but can be found in related MS articles in the references section. The Conditional Access policy only ensures 1 of the 3 methods is used. Warning: Administrators should be pre-registered for a strong authentication mechanism before this Conditional Access Policy is enforced. Additionally, as stated elsewhere in the CIS Benchmark a break-glass administrator account should be excluded from this policy to ensure unfettered access in the case of an emergency.",
+ "RationaleStatement": "Sophisticated attacks targeting MFA are more prevalent as the use of it becomes more widespread. These 3 methods are considered phishing-resistant as they remove passwords from the login workflow. It also ensures that public/private key exchange can only happen between the devices and a registered provider which prevents login to fake or phishing websites.",
+ "ImpactStatement": "If administrators aren't pre-registered for a strong authentication method prior to a conditional access policy being created, then a condition could occur where a user can't register for strong authentication because they don't meet the conditional access policy requirements and therefore are prevented from signing in. Additionally, Internet Explorer based credential prompts in PowerShell do not support prompting for a security key. Implementing phishing-resistant MFA with a security key may prevent admins from running their existing sets of PowerShell scripts. Device Authorization Grant Flow can be used as a workaround in some instances.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Click New policy. o Under Users or agents (Preview) include Select users and groups and check Directory roles. o At a minimum, include the directory roles listed below in this section of the document. o Under Target resources include All resources (formerly 'All cloud apps') and do not create any exclusions other than break-glass accounts. o Under Grant select Grant Access and check Require authentication strength and set Phishing-resistant MFA in the dropdown box. o Click Select. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On. Warning: Ensure administrators are pre-registered with strong authentication before enforcing the policy. After which the policy must be set to On. At minimum these directory roles should be included for the policy: - Application administrator - Authentication administrator - Billing administrator - Cloud application administrator - Conditional Access administrator - Exchange administrator - Global administrator - Global reader - Helpdesk administrator - Password administrator - Privileged authentication administrator - Privileged role administrator - Security administrator - SharePoint administrator - User administrator",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify Directory roles specific to administrators are included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Directory Roles should include at minimum the roles listed in the remediation section. o Under Target resources verify All resources (formerly 'All cloud apps') is selected with no exclusions. o Under Grant verify Grant Access is selected and Require authentication strength is checked with Phishing-resistant MFA set as the value. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where GrantControls.AuthenticationStrength.Id contains any valid id. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeRoles contains the directory roles specific to administrators* o Conditions.Applications.IncludeApplications is All o GrantControls.AuthenticationStrength.AllowedCombinations only contains windowsHelloForBusiness OR fido2 OR x509CertificateMultiFactor o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. It can be created from a Conditional Access template.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-passwordless#fido2-security-keys:https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-enable-passkey-fido2:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-strengths:https://learn.microsoft.com/en-us/entra/id-protection/howto-identity-protection-configure-mfa-policy"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.6",
+ "Description": "Microsoft Entra ID Protection user risk policies detect the probability that a user account has been compromised. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "Checks": [
+ "entra_identity_protection_user_risk_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID Protection user risk policies detect the probability that a user account has been compromised. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "RationaleStatement": "With the user risk policy turned on, Entra ID protection detects the probability that a user account has been compromised. Administrators can configure a user risk conditional access policy to automatically respond to a specific user risk level.",
+ "ImpactStatement": "Upon policy activation, account access will be either blocked or the user will be required to use multi-factor authentication (MFA) and change their password. Users without registered MFA will be denied access, necessitating an admin to recover the account. To avoid inconvenience, it is advised to configure the MFA registration policy for all users under the User Risk policy. Additionally, users identified in the Risky Users section will be affected by this policy. To gain a better understanding of the impact on the organization's environment, the list of Risky Users should be reviewed before enforcing the policy.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) choose All users o Under Target resources choose All resources (formerly 'All cloud apps') - Under Exclude exclude any break-glass accounts. o Under Conditions choose User risk then Yes and select the user risk level High. o Under Grant select Grant access then check Require multifactor authentication or Require authentication strength. Finally check Require password change. o Under Session set Sign-in frequency to Every time. o Click Select. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected. o Under Conditions verify User risk is set to High. o Under Grant verify Grant access is selected and either Require multifactor authentication or Require authentication strength are checked. Then verify Require password change is checked. o Under Session ensure Sign-in frequency is set to Every time. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.UserRiskLevels contains any string. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o Conditions.UserRiskLevels contains high o GrantControls.BuiltInControls contains passwordChange o GrantControls.BuiltInControls contains mfa OR GrantControls.AuthenticationStrength.id is any id o SessionControls.SignInFrequency.IsEnabled is true o SessionControls.SignInFrequency.FrequencyInterval is everyTime o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually. Note: If the UserRiskLevels array includes medium or low, this still qualifies as compliant, as these enforcement levels are considered more strict. However, it must always include high; omitting this level would exclude users who are classified as high risk.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. It may be created from a Conditional Access template.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-protection/howto-identity-protection-risk-feedback:https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.7",
+ "Description": "Microsoft Entra ID Protection sign-in risk detects risks in real-time and offline. A risky sign-in is an indicator for a sign-in attempt that might not have been performed by the legitimate owner of a user account. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "Checks": [
+ "entra_identity_protection_sign_in_risk_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID Protection sign-in risk detects risks in real-time and offline. A risky sign-in is an indicator for a sign-in attempt that might not have been performed by the legitimate owner of a user account. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "RationaleStatement": "Turning on the sign-in risk policy ensures that suspicious sign-ins are challenged for multi-factor authentication.",
+ "ImpactStatement": "When the policy triggers, the user will need MFA to access the account. In the case of a user who hasn't registered MFA on their account, they would be blocked from accessing their account. It is therefore recommended that the MFA registration policy be configured for all users who are a part of the Sign-in Risk policy.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) choose All users. o Under Target resources choose All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Conditions choose Sign-in risk then Yes and check the risk level boxes High and Medium. o Under Grant click Grant access then select Require multifactor authentication. o Under Session select Sign-in Frequency and set to Every time. o Click Select. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected. o Under Conditions verify Sign-in risk is set to Yes ensuring High and Medium are selected. o Under Grant verify grant Grant access is selected and Require multifactor authentication checked. o Under Session verify Sign-in Frequency is set to Every time. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.SignInRiskLevels contains any string. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o Conditions.SignInRiskLevels contains high o Conditions.SignInRiskLevels contains medium o GrantControls.BuiltInControls contains mfa OR GrantControls.AuthenticationStrength.id is any id o SessionControls.SignInFrequency.IsEnabled is true o SessionControls.SignInFrequency.FrequencyInterval is everyTime o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually. Note: If the SignInRiskLevels array includes low, this still qualifies as compliant, as these enforcement levels are considered more strict. However, it must always include high and medium; omitting these levels would exclude users who are classified as such. Note 2: If GrantControls.BuiltInControls is block then the Grant and Session controls are considered satisfied, as this is considered a more strict enforcement of sign-in risk control.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. It may be created from a Conditional Access template.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-protection/howto-identity-protection-risk-feedback:https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.8",
+ "Description": "Microsoft Entra ID Protection sign-in risk detects risks in real-time and offline. A risky sign-in is an indicator for a sign-in attempt that might not have been performed by the legitimate owner of a user account. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID Protection sign-in risk detects risks in real-time and offline. A risky sign-in is an indicator for a sign-in attempt that might not have been performed by the legitimate owner of a user account. Note: While Identity Protection also provides two risk policies with limited conditions, Microsoft highly recommends setting up risk-based policies in Conditional Access as opposed to the \"legacy method\" for the following benefits: - Enhanced diagnostic data - Report-only mode integration - Graph API support - Use more Conditional Access attributes like sign-in frequency in the policy",
+ "RationaleStatement": "Sign-in risk is determined at the time of sign-in and includes criteria across both real- time and offline detections for risk. Blocking sign-in to accounts that have risk can prevent undesired access from potentially compromised devices or unauthorized users.",
+ "ImpactStatement": "Sign-in risk is heavily dependent on detecting risk based on atypical behaviors. Due to this it is important to run this policy in a report-only mode to better understand how the organization's environment and user activity may influence sign-in risk before turning the policy on. Once it's understood what actions may trigger a medium or high sign-in risk event I.T. can then work to create an environment to reduce false positives. For example, employees might be required to notify security personnel when they intend to travel with intent to access work resources.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources include All resources (formerly 'All cloud apps') and do not set any exclusions. - Under Exclude exclude any break-glass accounts. o Under Conditions choose Sign-in risk values of High and Medium and click Done. o Under Grant choose Block access and click Select. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected with no exclusions. o Under Conditions verify Sign-in risk values of High and Medium are selected. o Under Grant verify Block access is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.SignInRiskLevels contains any string. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o Conditions.Applications.ExcludeApplications is null or empty o Conditions.SignInRiskLevels contains high o Conditions.SignInRiskLevels contains medium o GrantControls.BuiltInControls is block o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually. Note: If the SignInRiskLevels array includes low, this still qualifies as compliant, as these enforcement levels are considered more strict. However, it must always include high and medium; omitting these levels would exclude users who are classified as such.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-protection/concept-identity-protection-risks#risk-detections-mapped-to-riskeventtype"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.9",
+ "Description": "Conditional Access (CA) can be configured to enforce access based on the device's compliance status or whether it is Entra hybrid joined. Collectively this allows CA to classify devices as managed or unmanaged, providing more granular control over authentication policies. When using Require device to be marked as compliant, the device must pass checks configured in compliance policies defined within Microsoft Intune. Before these checks can be applied, the device must first be enrolled in Intune MDM. By selecting Require Microsoft Entra hybrid joined device this means the device must first be synchronized from an on-premises Active Directory to qualify for authentication. When configured to the recommended state below only one condition needs to be met for the user to authenticate from the device. This functions as an \"OR\" operator. The recommended state for authentication is: - Require device to be marked as compliant - Require Microsoft Entra hybrid joined device (optional for hybrid environments) - Require one of the selected controls",
+ "Checks": [
+ "entra_managed_device_required_for_authentication"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Conditional Access (CA) can be configured to enforce access based on the device's compliance status or whether it is Entra hybrid joined. Collectively this allows CA to classify devices as managed or unmanaged, providing more granular control over authentication policies. When using Require device to be marked as compliant, the device must pass checks configured in compliance policies defined within Microsoft Intune. Before these checks can be applied, the device must first be enrolled in Intune MDM. By selecting Require Microsoft Entra hybrid joined device this means the device must first be synchronized from an on-premises Active Directory to qualify for authentication. When configured to the recommended state below only one condition needs to be met for the user to authenticate from the device. This functions as an \"OR\" operator. The recommended state for authentication is: - Require device to be marked as compliant - Require Microsoft Entra hybrid joined device (optional for hybrid environments) - Require one of the selected controls",
+ "RationaleStatement": "\"Managed\" devices are considered more secure because they often have additional configuration hardening enforced through centralized management such as Intune or Group Policy. These devices are also typically equipped with MDR/EDR, managed patching and alerting systems. As a result, they provide a safer environment for users to authenticate and operate from. This policy also ensures that attackers must first gain access to a compliant or trusted device before authentication is permitted, reducing the risk posed by compromised account credentials. When combined with other distinct Conditional Access (CA) policies, such as requiring multi-factor authentication, this adds one additional factor before authentication is permitted. Note: Avoid combining these two settings with other Grant settings in the same policy. In a single policy you can only choose between Require all the selected controls or Require one of the selected controls, which limits the ability to integrate this recommendation with others in this benchmark. CA policies function as an \"AND\" operator across multiple policies. The goal here is to both (Require MFA for all users) AND (Require device to be marked as compliant OR Require Microsoft Entra hybrid joined device).",
+ "ImpactStatement": "Unmanaged devices will not be permitted as a valid authenticator. As a result this may require the organization to mature their device enrollment and management. The following devices can be considered managed: - Entra hybrid joined from Active Directory - Entra joined and enrolled in Intune, with compliance policies - Entra registered and enrolled in Intune, with compliance policies If Guest or external users are collaborating with the organization, they must either be excluded or onboarded with a compliant device to authenticate. Failure to adequately survey the environment and test the Conditional Access (CA) policy in the Report-only state could result in access disruptions for these guest users.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Grant select Grant access. o Select the checkbox Require device to be marked as compliant. o Optionally, also select Require Microsoft Entra hybrid joined device if the organization uses hybrid joined devices. o Choose Require one of the selected controls. o Click Select at the bottom. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On. Note: Guest user accounts, if collaborating with the organization, should be considered when testing this policy.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify All resources (formerly 'All cloud apps') is selected. o Verify that only documented resource exclusions exist and that they are reviewed annually. o Under Grant verify that Require device to be marked as compliant is checked. o Under Grant verify that no other controls are checked except, optionally, Require Microsoft Entra hybrid joined device. o Verify Require one of the selected controls is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where GrantControls.BuiltInControls contains compliantDevice or domainJoinedDevice. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o GrantControls.BuiltInControls contains compliantDevice o GrantControls.BuiltInControls does not contain any values other than compliantDevice and domainJoinedDevice o GrantControls.Operator is OR o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-grant#require-device-to-be-marked-as-compliant:https://learn.microsoft.com/en-us/entra/identity/devices/concept-hybrid-join:https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.10",
+ "Description": "Conditional Access (CA) can be configured to enforce access based on the device's compliance status or whether it is Entra hybrid joined. Collectively, this allows CA to classify devices as managed or unmanaged, providing more granular control over whether a user can register security information from a device. When using Require device to be marked as compliant, the device must pass checks configured in compliance policies defined within Microsoft Intune. Before these checks can be applied, the device must first be enrolled in Intune MDM. By selecting Require Microsoft Entra hybrid joined device this means the device must first be synchronized from an on-premises Active Directory to qualify. When configured to the recommended state below only one condition needs to be met for the user to authenticate from the device. This functions as an \"OR\" operator. The recommended state for registering security information is: - Require device to be marked as compliant - Require Microsoft Entra hybrid joined device (optional for hybrid environments) - Require one of the selected controls",
+ "Checks": [
+ "entra_managed_device_required_for_mfa_registration"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Conditional Access (CA) can be configured to enforce access based on the device's compliance status or whether it is Entra hybrid joined. Collectively, this allows CA to classify devices as managed or unmanaged, providing more granular control over whether a user can register security information from a device. When using Require device to be marked as compliant, the device must pass checks configured in compliance policies defined within Microsoft Intune. Before these checks can be applied, the device must first be enrolled in Intune MDM. By selecting Require Microsoft Entra hybrid joined device this means the device must first be synchronized from an on-premises Active Directory to qualify. When configured to the recommended state below only one condition needs to be met for the user to authenticate from the device. This functions as an \"OR\" operator. The recommended state for registering security information is: - Require device to be marked as compliant - Require Microsoft Entra hybrid joined device (optional for hybrid environments) - Require one of the selected controls",
+ "RationaleStatement": "Requiring registration on a managed device significantly reduces the risk of bad actors using stolen credentials to register security information. Accounts that are created but never registered with an MFA method are particularly vulnerable to this type of attack. Enforcing this requirement will both reduce the attack surface for fake registrations and ensure that legitimate users register using trusted devices which typically have additional security measures in place already.",
+ "ImpactStatement": "The organization will be required to have a mature device management process. New devices provided to users will need to be pre-enrolled in Intune, auto-enrolled, or be Entra hybrid joined. Otherwise, the user will be unable to complete registration, requiring additional resources from I.T. This could be more disruptive in remote worker environments where the MDM maturity is low. Users who do not yet have access to a managed device, such as new hires, users with lost or replaced devices, or users registering MFA methods on personal mobile devices - will be unable to satisfy the device compliance grant control. To address this, organizations should configure a Temporary Access Pass (TAP) policy and issue a one- time TAP to these users. A one-time TAP satisfies multifactor authentication requirements and allows the user to register security information from any device or location. B2B collaboration users (guest accounts) will also be blocked by this policy, as their devices are not managed in the resource tenant. Organizations should consider excluding All guest and external users from this policy. Alternatively, organizations that trust partner device compliance claims can configure this through cross-tenant access settings.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources select User actions and check Register security information. - Under Exclude exclude any break-glass accounts. o Under Grant select Grant access. o Select the checkbox Require device to be marked as compliant. o Optionally, also select Require Microsoft Entra hybrid joined device if the organization uses hybrid joined devices. o Choose Require one of the selected controls. o Click Select at the bottom. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify User actions is selected with Register security information checked. o Under Grant verify that Require device to be marked as compliant is checked. o Under Grant verify that no other controls are checked except, optionally, Require Microsoft Entra hybrid joined device. o Verify Require one of the selected controls is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.Applications.IncludeUserActions contains urn:user:registersecurityinfo. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeUserActions is urn:user:registersecurityinfo o GrantControls.BuiltInControls contains compliantDevice o GrantControls.BuiltInControls does not contain any values other than compliantDevice and domainJoinedDevice o GrantControls.Operator is OR o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-grant#require-device-to-be-marked-as-compliant:https://learn.microsoft.com/en-us/entra/identity/devices/concept-hybrid-join:https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment:https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-cloud-apps#user-actions:https://docs.azure.cn/en-us/entra/identity/authentication/concept-authentication-strength-how-it-works#how-multiple-authentication-strength-policies-are-evaluated-for-registering-security-info"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.11",
+ "Description": "Sign-in frequency defines the time period before a user is asked to sign in again when attempting to access a resource. The Microsoft Entra ID default configuration for user sign-in frequency is a rolling window of 90 days. The recommended state is a Sign-in frequency of Every time for Microsoft Intune Enrollment Note: Microsoft accounts for a five-minute clock skew when 'every time' is selected in a conditional access policy, ensuring that users are not prompted more frequently than once every five minutes.",
+ "Checks": [
+ "entra_intune_enrollment_sign_in_frequency_every_time"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Sign-in frequency defines the time period before a user is asked to sign in again when attempting to access a resource. The Microsoft Entra ID default configuration for user sign-in frequency is a rolling window of 90 days. The recommended state is a Sign-in frequency of Every time for Microsoft Intune Enrollment Note: Microsoft accounts for a five-minute clock skew when 'every time' is selected in a conditional access policy, ensuring that users are not prompted more frequently than once every five minutes.",
+ "RationaleStatement": "Intune Enrollment is considered a sensitive action and should be safeguarded. An attack path exists that allows for a bypass of device compliance Conditional Access rule. This could allow compromised credentials to be used through a newly registered device enrolled in Intune, enabling persistence and privilege escalation. Setting sign-in frequency to every time limits the timespan an attacker could use fresh credentials to enroll a new device to Intune.",
+ "ImpactStatement": "New users enrolling into Intune through an automated process may need to sign-in again if the enrollment process goes on for too long.",
+ "RemediationProcedure": "Note: If the Microsoft Intune Enrollment cloud app isn't available then it must be created. To add the app for new tenants, a Microsoft Entra administrator must create a service principal object, with app ID d4ebce55-015a-49b5-a083-c84d1797ae8c, in PowerShell or Microsoft Graph. To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources select Resources (formerly cloud apps), choose Select resources and add Microsoft Intune Enrollment to the list. - Under Exclude exclude any break-glass accounts. o Under Grant select Grant access. o Check either Require multifactor authentication or Require authentication strength. o Under Session check Sign-in frequency and select Every time. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify Resources (formerly cloud apps) includes Microsoft Intune Enrollment. o Under Grant verify Require multifactor authentication or Require authentication strength is checked. o Under Session verify Sign-in frequency is set to Every time. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: Note: The Authentication Strength requirement is satisfied when any valid GUID is present in the authenticationStrength property of a matching policy. Because Authentication Strength configurations are inherently stronger than the built-in Require multifactor authentication control, the presence of a valid Authentication Strength also fulfills the MFA requirement for all users. 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.Applications.IncludeApplications contains d4ebce55-015a-49b5-a083-c84d1797ae8c. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications contains d4ebce55- 015a-49b5-a083-c84d1797ae8c o GrantControls.BuiltInControls contains mfa OR GrantControls.AuthenticationStrength.id is defined o SessionControls.SignInFrequency.IsEnabled is true o SessionControls.SignInFrequency.FrequencyInterval is everyTime o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. Sign-in frequency defaults to 90 days.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-session-lifetime#require-reauthentication-every-time:https://www.blackhat.com/eu-24/briefings/schedule/#unveiling-the-power-of-intune-leveraging-intune-for-breaking-into-your-cloud-and-on-premise-42176:https://www.glueckkanja.com/blog/security/2025/01/compliant-device-bypass-en/"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.12",
+ "Description": "The Microsoft identity platform supports the device authorization grant, which allows users to sign in to input-constrained devices such as a smart TV, IoT device, or a printer. To enable this flow, the device has the user visit a webpage in a browser on another device to sign in. Once the user signs in, the device is able to get access tokens and refresh tokens as needed. The recommended state is to Block access for Device code flow in Conditional Access.",
+ "Checks": [
+ "entra_conditional_access_policy_device_code_flow_blocked"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The Microsoft identity platform supports the device authorization grant, which allows users to sign in to input-constrained devices such as a smart TV, IoT device, or a printer. To enable this flow, the device has the user visit a webpage in a browser on another device to sign in. Once the user signs in, the device is able to get access tokens and refresh tokens as needed. The recommended state is to Block access for Device code flow in Conditional Access.",
+ "RationaleStatement": "Since August 2024, Microsoft has observed threat actors, such as Storm-2372, employing \"device code phishing\" attacks. These attacks deceive users into logging into productivity applications, capturing authentication tokens to gain further access to compromised accounts. To mitigate this specific attack, block authentication code flows and permit only those from devices within trusted environments, identified by specific IP addresses.",
+ "ImpactStatement": "Some administrative overhead will be required for stricter management of these devices. Since exclusions do not violate compliance, this feature can still be utilized effectively within a controlled environment.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources > Resources (formerly cloud apps) include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Conditions > Authentication flows set Configure to Yes and check Device code flow. o Click Save. o Under Grant select Block access and click Select. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to `On",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify Resources (formerly cloud apps) includes All resources (formerly 'All cloud apps') o Under Conditions > Authentication flows verify Configure is set to Yes and Device code flow is checked. o Under Grant verify Block access is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where Conditions.AuthenticationFlows.TransferMethods contains deviceCodeFlow. 3. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o Conditions.AuthenticationFlows.TransferMethods contains deviceCodeFlow o GrantControls.BuiltInControls is block o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default. It may be present as a Microsoft-managed policy.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-device-code:https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-authentication-flows:https://www.microsoft.com/en-us/security/blog/2025/02/13/storm-2372-conducts-device-code-phishing-campaign/:https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-authentication-flows#device-code-flow-policies"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.13",
+ "Description": "Sign-in frequency defines the time period before a user is asked to sign in again when attempting to access a resource. The Microsoft Entra ID default configuration for user sign-in frequency is a rolling window of 90 days. The recommended state for all users is to enforce periodic reauthentication for 7 days or less.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Sign-in frequency defines the time period before a user is asked to sign in again when attempting to access a resource. The Microsoft Entra ID default configuration for user sign-in frequency is a rolling window of 90 days. The recommended state for all users is to enforce periodic reauthentication for 7 days or less.",
+ "RationaleStatement": "A 7-day interval balances security and user experience by reducing the maximum lifespan of compromised credentials or stolen tokens without introducing excessive reauthentication prompts that can increase phishing susceptibility and user fatigue.",
+ "ImpactStatement": "Most users will not find weekly reauthentication requirements disruptive. Organizations with legacy applications, custom authentication workflows, or users relying on long-running sessions (such as shared or kiosk devices) may need to evaluate compatibility and apply appropriate exclusions to prevent user disruption.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources verify Resources (formerly cloud apps) include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Session select Sign-in frequency and set Periodic reauthentication to 7 days or less. 4. Under Enable policy set it to Report-only. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria and is set to On: o Under Users or agents (Preview) verify All users is included. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify Resources (formerly cloud apps) includes All resources (formerly 'All cloud apps') o Under Session ensure Sign-in frequency is checked, and Periodic reauthentication is set to 7 days or less. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where SessionControls.SignInFrequency.IsEnabled is true 3. Filter out policies where Conditions.signInRiskLevels and Conditions.userRiskLevels have values defined, excluding these from the assessment. 4. For each policy returned, verify the following criteria: o Conditions.Users.IncludeUsers is All o Conditions.Applications.IncludeApplications is All o SessionControls.SignInFrequency.frequencyInterval is timeBased o SessionControls.SignInFrequency.type is days* o SessionControls.SignInFrequency.value is 7 (or less)* o State is enabled 5. Compliance is met when at least one policy is found to meet all the criteria listed above. 6. Verify that any exclusions are documented and reviewed annually. Note: Any SignInFrequency type and value combination is considered compliant as long as the reauthentication interval is less than or equal to 7 days. For example, a policy applied to all users that requires reauthentication every 20 hours would still meet the requirement.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/howto-conditional-access-session-lifetime"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.14",
+ "Description": "Microsoft Entra ID Conditional Access allows an organization to configure Named locations and configure whether those locations are trusted or untrusted. These settings provide organizations the means to specify Geographical locations for use in conditional access policies, or define actual IP addresses and IP ranges and whether or not those IP addresses and/or ranges are trusted by the organization. The recommended state is to define at least one trusted, IP range named location.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID Conditional Access allows an organization to configure Named locations and configure whether those locations are trusted or untrusted. These settings provide organizations the means to specify Geographical locations for use in conditional access policies, or define actual IP addresses and IP ranges and whether or not those IP addresses and/or ranges are trusted by the organization. The recommended state is to define at least one trusted, IP range named location.",
+ "RationaleStatement": "Defining trusted source IP addresses or ranges enables organizations to better tailor and enforce Conditional Access policies based on whether authentication attempts originate from trusted or untrusted network locations. Users signing in from trusted IP ranges can be granted reduced access requirements or fewer authentication prompts, while users coming from untrusted or unknown locations may face stricter controls. Additionally, marking named locations as trusted improves the accuracy of Microsoft Entra ID Protection's risk evaluations. When a user authenticates from a trusted location, their sign-in risk is appropriately lowered, helping reduce false positives and ensuring that risk-based policies trigger only when truly necessary.",
+ "ImpactStatement": "Configuring named locations by country cannot designate those locations as trusted, which means Conditional Access policies cannot use the \"All trusted locations\" option and must instead rely on explicitly selecting locations. This increases the administrative effort needed to configure and maintain these policies and requires more thorough testing to prevent unintended authentication blocks. Because Conditional Access policies can fully prevent users from signing in to Entra ID if misconfigured, organizations should maintain a dedicated break-glass Global Administrator account that is excluded from all Conditional Access policies and secured with a strong passphrase and hardware-based authentication. This account exists solely to recover access if all other administrators are locked out.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Under Manage, click Named locations. 4. Click on IP ranges location to add a new location. 5. Enter a name for this location setting in the Name field. 6. Click on the + icon. 7. Add only a trusted IP Address Range in CIDR notation inside the text box that appears. 8. Click on the Add button. 9. Repeat steps 6 through 8 for each additional IP range. 10. Select the Mark as trusted location checkbox. 11. Once finished, click on Create. Note: There is no single prescribed method for applying a named location to a Conditional Access policy, as the correct configuration depends on the specific access control requirements. Implementers should have a clear understanding of how named locations function before applying them to production policies.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Under Manage, click Named locations. 4. For each named location with a Location type of IP ranges, verify there is one with the following criteria: o Trusted is set to Yes. o At least one IP Range is defined 5. Compliance is met when at least one named location is found to meet all the criteria listed above. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/namedLocations?$filter=isof('microsoft.graph. ipNamedLocation') 2. For each named location returned, verify the following criteria: o isTrusted is true o ipRanges contains at least one ipv4 or ipv6 range 3. Compliance is met when at least one named location is found to meet all the criteria listed above.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Named locations are not configured by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-assignment-network:https://learn.microsoft.com/en-us/entra/id-protection/concept-risk-detection-types#locations:https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccesspolicy?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.15",
+ "Description": "Conditional Access Policies can be used to block access from geographic locations that are deemed out-of-scope for your organization or application. The scope and variables for this policy should be carefully examined and defined. The recommended state is to configure at least one policy to block access from untrusted locations.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Conditional Access Policies can be used to block access from geographic locations that are deemed out-of-scope for your organization or application. The scope and variables for this policy should be carefully examined and defined. The recommended state is to configure at least one policy to block access from untrusted locations.",
+ "RationaleStatement": "Using Conditional Access as a deny list at the tenant or subscription level enables an organization to block inbound and outbound traffic from geographic locations that fall outside its operational scope (e.g., customers, suppliers) or legal jurisdiction. Restricting access to only required regions significantly reduces unnecessary exposure to international threat actors, including advanced persistent threats (APTs), and helps maintain a more controlled and defensible security posture. Note: Because the selection of allowed or blocked locations is unique to each organization, this control does not prescribe specific countries or regions. Each organization should determine its geographic access requirements based on operational needs, regulatory obligations, and risk tolerance.",
+ "ImpactStatement": "Limiting access geographically will deny access to users that are traveling or working remotely in a different part of the world. A point-to-site or site to site tunnel such as a VPN is recommended to address exceptions to geographic access policies. CAUTION: If these policies are created without first auditing and testing the result, misconfiguration can potentially lock out administrators or create undesired access issues.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users o Under Target resources include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Network set Configure to Yes: - Select Include, then add entries for untrusted locations that should be blocked - Select Exclude, then add entries for trusted locations that should be allowed 4. Under Access Controls, select Grant select Block Access. 5. Under Enable policy set it to Report-only. 6. Click Create. 7. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria: o Under Users or agents (Preview) verify All users is included o Verify that only documented user exclusions exist and that they are reviewed annually o Under Target resources verify All resources (formerly 'All cloud apps') is selected o Under Network verify Include> Selected networks and locations contains at least one untrusted location o Under Network verify Exclude contains trusted locations through either All trusted networks and locations or Selected networks and locations o Under Grant verify Block access is selected 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. For each policy returned, verify the following criteria: o conditions.users.includeUsers is All o conditions.applications.includeApplications is All o conditions.locations.includeLocations contains at least one GUID of at least one untrusted location. o conditions.locations.excludeLocations is AllTrusted OR contains at least one GUID of at least one trusted location. o grantControls.builtInControls is block o state is enabled 3. Compliance is met when at least one policy is found to meet all the criteria listed above. 4. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "These policies should be tested by using the What If tool in the References. Setting these can and will create issues with logging in for users until they use an MFA device linked to their accounts. Further testing can also be done via the insights and reporting resource in References which monitors Azure sign ins.",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-by-location:https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-report-only"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.16",
+ "Description": "Token Protection is a Conditional Access session control that attempts to reduce token replay attacks by ensuring only device bound sign-in session tokens, like Primary Refresh Tokens (PRTs), are accepted by Microsoft Entra ID when applications request access to protected resources. When a user registers a supported device with Microsoft Entra, a PRT is issued and cryptographically bound to that device. This binding ensures that even if a threat actor steals the token, it can't be used from another device. With Token Protection enforced, Microsoft Entra validates that only these bound sign-in session tokens are used by supported applications. The recommended state is to enforce Token Protection for Office 365 Exchange Online, Office 365 SharePoint Online and Microsoft Teams Services.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Token Protection is a Conditional Access session control that attempts to reduce token replay attacks by ensuring only device bound sign-in session tokens, like Primary Refresh Tokens (PRTs), are accepted by Microsoft Entra ID when applications request access to protected resources. When a user registers a supported device with Microsoft Entra, a PRT is issued and cryptographically bound to that device. This binding ensures that even if a threat actor steals the token, it can't be used from another device. With Token Protection enforced, Microsoft Entra validates that only these bound sign-in session tokens are used by supported applications. The recommended state is to enforce Token Protection for Office 365 Exchange Online, Office 365 SharePoint Online and Microsoft Teams Services.",
+ "RationaleStatement": "When properly configured, Conditional Access can aid in preventing attacks involving token theft, via hijacking or replay, as part of the attack flow. Although currently considered a rare event, the impact from token impersonation can be severe.",
+ "ImpactStatement": "Token Protection currently supports native applications only. Browser-based applications are not supported. There are also many other known limitations documented in the link below: https://learn.microsoft.com/en-us/entra/identity/conditional-access/deployment-guide- token-protection-windows#known-limitations",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Select New policy. 4. Select Users or agents (Preview): 1. Under Include, select the users or groups to apply this policy. 2. Under Exclude exclude any break-glass accounts. 5. Select Target resources > Resources > Include > Select resources 1. Under Select specific resources, select the following applications: 1. Office 365 Exchange Online 2. Office 365 SharePoint Online 3. Microsoft Teams Services 2. Choose Select 6. Select Conditions: 1. Under Device platforms 1. Set Configure to Yes. 2. Include > Select device platforms > Windows. 3. Select Done. 2. Under Client apps: 1. Set Configure to Yes 2. Under Modern authentication clients, only select Mobile apps and desktop clients. 3. Select Done 7. Under Access controls > Session, select Require token protection for sign-in sessions (Generally available for Windows. Preview for MacOS, iOS) and click Select. 8. Under Enable policy set it to Report-only. 9. Click Create. 10. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access and select Policies. 3. Verify that a policy exists with the following criteria: o Under Users or agents (Preview) verify that None is not selected. o Verify that only documented exclusions exist and that they are reviewed annually o Under Target resources select Select resources and verify at minimum the following are checked: - Office 365 Exchange Online - Office 365 SharePoint Online - Microsoft Teams Services 4. Under Conditions > Device Platforms: verify that Configure is set to Yes and Include indicates Windows platforms. 5. Under Conditions > Client Apps: verify that Configure is set to Yes and only Mobile Apps and Desktop Clients is selected. 6. Under Access controls > Session, verify that Require token protection for sign-in sessions (Generally available for Windows. Preview for MacOS, iOS) is selected. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where sessionControls.secureSignInSession.isEnabled is true. 3. For each policy returned, verify the following criteria: o conditions.users.includeUsers is not None o conditions.applications.includeApplications contains at least the following GUIDs: - 00000002-0000-0ff1-ce00-000000000000 (Office 365 Exchange Online) - 00000003-0000-0ff1-ce00-000000000000 (Office 365 SharePoint Online) - cc15fd57-2c6c-4117-a88c-83b1d56b4bbe (Microsoft Teams Services) o conditions.platforms.includePlatforms contains windows o conditions.clientAppTypes is mobileAppsAndDesktopClients o sessionControls.secureSignInSession.isEnabled is true o State is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-token-protection:https://learn.microsoft.com/en-us/entra/identity/conditional-access/deployment-guide-token-protection-windows:https://learn.microsoft.com/en-us/entra/identity/devices/protecting-tokens-microsoft-entra-id"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.2.17",
+ "Description": "Authentication transfer is a flow that lets users seamlessly transfer authenticated state from one device to another. For example, users might see a QR code in the desktop version of Outlook that, when scanned on their mobile device, transfers their authenticated state to the mobile device. The recommended state is to block Authentication transfer.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.2 Conditional Access",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Authentication transfer is a flow that lets users seamlessly transfer authenticated state from one device to another. For example, users might see a QR code in the desktop version of Outlook that, when scanned on their mobile device, transfers their authenticated state to the mobile device. The recommended state is to block Authentication transfer.",
+ "RationaleStatement": "Blocking authentication transfer helps protect against token theft and replay attacks by preventing the use of device tokens to silently authenticate on other devices or browsers. When authentication transfer is enabled, a threat actor who gains access to one device can access resources to unapproved devices, bypassing standard authentication and device compliance checks. When administrators block this flow, organizations can ensure that each authentication request must originate from the original device, maintaining the integrity of the device compliance and user session context.",
+ "ImpactStatement": "Users will no longer be able to use authentication transfer to sign into mobile versions of Microsoft apps (e.g., scanning a QR code in Outlook desktop to sign into Outlook mobile). Each device will require independent, interactive sign-in subject to applicable Conditional Access policies.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access. 3. Create a new policy by selecting New policy. o Under Users or agents (Preview) include All users. o Under Target resources > Resources (formerly cloud apps) include All resources (formerly 'All cloud apps'). - Under Exclude exclude any break-glass accounts. o Under Conditions > Authentication flows set Configure to Yes and check Authentication transfer. - Click Save. o Under Grant select Block access and click Select. 4. Under Enable policy set it to Report-only until the organization is ready to enable it. 5. Click Create. 6. After allowing the policy to run in Report-only mode for at least one week, review the Sign-in logs for any unexpected impact, then return to the policy and set Enable policy to On.",
+ "AuditProcedure": "Note: Break-glass accounts should be excluded from all Conditional Access policies. To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Conditional Access. 3. Verify that a policy exists with the following criteria: o Under Users or agents (Preview) verify All users is selected. o Verify that only documented user exclusions exist and that they are reviewed annually. o Under Target resources verify Resources (formerly cloud apps) includes All resources (formerly 'All cloud apps') o Under Conditions > Authentication flows verify Configure is set to Yes and Authentication transfer is checked. o Under Grant verify Block access is selected. 4. Verify that Enable policy is set to On. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identity/conditionalAccess/policies 2. Filter to policies where conditions.authenticationFlows.transferMethods contains authenticationTransfer. 3. For each policy returned, verify the following criteria: o conditions.users.includeUsers is All o conditions.applications.includeApplications is All o conditions.authenticationFlows.transferMethods contains authenticationTransfer o grantControls.builtInControls is block o state is enabled 4. Compliance is met when at least one policy is found to meet all the criteria listed above. 5. Verify that any exclusions are documented and reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "This policy does not exist by default.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-authentication-flows#authentication-transfer-policies:https://learn.microsoft.com/en-us/entra/fundamentals/zero-trust-protect-identities#authentication-transfer-is-blocked:https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-authentication-flows:https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-authentication-transfer"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.1",
+ "Description": "Microsoft provides supporting settings to enhance the configuration of the Microsoft Authenticator application. These settings provide users with additional information and context when they receive MFA passwordless and push requests, including the geographic location of the request, the requesting application, and a requirement for number matching. The recommended state is Enabled for the following: - Show application name in push and passwordless notifications - Show geographic location in push and passwordless notifications Note: On February 27, 2023 Microsoft started enforcing number matching tenant-wide for all users using Microsoft Authenticator.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft provides supporting settings to enhance the configuration of the Microsoft Authenticator application. These settings provide users with additional information and context when they receive MFA passwordless and push requests, including the geographic location of the request, the requesting application, and a requirement for number matching. The recommended state is Enabled for the following: - Show application name in push and passwordless notifications - Show geographic location in push and passwordless notifications Note: On February 27, 2023 Microsoft started enforcing number matching tenant-wide for all users using Microsoft Authenticator.",
+ "RationaleStatement": "As the use of strong authentication has become more widespread, attackers have started to exploit the tendency of users to experience \"MFA fatigue.\" This occurs when users are repeatedly asked to provide additional forms of identification, leading them to eventually approve requests without fully verifying the source. To counteract this, number matching can be employed to ensure the security of the authentication process. With this method, users are prompted to confirm a number displayed on their original device and enter it into the device being used for MFA. Additionally, other information such as geolocation and application details are displayed to enhance the end user's awareness. Among these 3 options, number matching provides the strongest net security gain.",
+ "ImpactStatement": "Additional interaction will be required by end users using number matching as opposed to simply pressing \"Approve\" for login attempts.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Click to expand Entra ID > Authentication methods and select Policies. 3. Select Microsoft Authenticator 4. Under Enable and Target ensure the setting is set to Enable. 5. Select Configure 6. Set the following Microsoft Authenticator settings: o Show application name in push and passwordless notifications Status is set to Enabled, Target All users o Show geographic location in push and passwordless notifications Status is set to Enabled, Target All users Note: Valid groups such as break glass accounts can be excluded per organization policy.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Authentication methods and select Policies. 3. Under Method select Microsoft Authenticator. 4. Under Enable and Target verify the setting is set to Enable. 5. In the Include tab verify that All users is selected. 6. In the Exclude tab verify only valid groups are present (i.e. Break Glass accounts). 7. Select Configure 8. Verify the following Microsoft Authenticator settings: o Show application name in push and passwordless notifications Status is set to Enabled, Target All users o Show geographic location in push and passwordless notifications Status is set to Enabled, Target All users 9. In each setting select Exclude and verify only valid groups are present (i.e. Break Glass accounts). To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/policies/authenticationMethodsPolicy/authenticationMethodConfigurations/ microsoftAuthenticator 2. Verify that the state is enabled. 3. Verify that includeTargets.id is all_users. 4. Verify that the excludeTargets only includes valid groups (i.e. Break Glass accounts). 5. Under featureSettings verify the following settings: o displayAppInformationRequiredState.state is enabled o displayAppInformationRequiredState.includeTarget.id is all_users o displayLocationInformationRequiredState.state is enabled o displayLocationInformationRequiredState.includeTarget.id is all_users 6. In each setting excludeTarget only includes a valid group (i.e. Break Glass accounts) or a target id of 00000000-0000-0000-0000-000000000000 Note: Compliance cannot be easily validated for exclusions so adding these to a report for human manual review is recommended. These should be reviewed annually.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Microsoft-managed",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-default-enablement:https://techcommunity.microsoft.com/t5/microsoft-entra-blog/defend-your-users-from-mfa-fatigue-attacks/ba-p/2365677:https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-number-match:https://learn.microsoft.com/en-us/graph/api/authenticationmethodspolicy-get?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.2",
+ "Description": "With Entra Password Protection, default global banned password lists are automatically applied to all users in an Entra ID tenant. To support business and security needs, custom banned password lists can be defined. When users change or reset their passwords, these banned password lists are checked to enforce the use of strong passwords. A custom banned password list should include some of the following examples: - Brand names - Product names - Locations, such as company headquarters - Company-specific internal terms - Abbreviations that have specific company meaning",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "With Entra Password Protection, default global banned password lists are automatically applied to all users in an Entra ID tenant. To support business and security needs, custom banned password lists can be defined. When users change or reset their passwords, these banned password lists are checked to enforce the use of strong passwords. A custom banned password list should include some of the following examples: - Brand names - Product names - Locations, such as company headquarters - Company-specific internal terms - Abbreviations that have specific company meaning",
+ "RationaleStatement": "Creating a new password can be difficult regardless of one's technical background. It is common to look around one's environment for suggestions when building a password, however, this may include picking words specific to the organization as inspiration for a password. An adversary may employ what is called a 'mangler' to create permutations of these specific words in an attempt to crack passwords or hashes making it easier to reach their goal.",
+ "ImpactStatement": "If a custom banned password list includes too many common dictionary words, or short words that are part of compound words, then perfectly secure passwords may be blocked. The organization should consider a balance between security and usability when creating a list.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Authentication methods and select Password protection. 3. Set Enforce custom list to Yes 4. In Custom banned password list create a list using suggestions outlined in this document. 5. Click Save Note: Below is a list of examples that can be used as a starting place. The references section contains more suggestions. - Brand names - Product names - Locations, such as company headquarters - Company-specific internal terms - Abbreviations that have specific company meaning",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand Entra ID > Authentication methods and select Password protection. 3. Verify that Enforce custom list is set to Yes 4. Verify that Custom banned password list contains entries specific to the organization or matches a pre-determined list. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Directory.Read.All\" 2. Run the following commands: $PwRuleSettings = '5cf42378-d67d-4f36-ba46-e8b86229381d' Get-MgGroupSetting | Where-Object TemplateId -eq $PwRuleSettings | Select-Object -ExpandProperty Values 3. Verify that EnableBannedPasswordCheck is True and BannedPasswordList is populated.",
+ "AdditionalInformation": "Organization-specific terms can be added to the custom banned password list, such as the following examples: - Brand names - Product names - Locations, such as company headquarters - Company-specific terms - Abbreviations that have specific company meaning - Months and weekdays with your company's local languages The default global banned password list is already applied to your resources which applies the following basic requirements: Characters allowed: - Uppercase characters (A - Z) - Lowercase characters (a - z) - Numbers (0 - 9) - Symbols: - @#$%^&*-_!+=[]{}|\\:',.?/`~\"();<> - blank space Characters not allowed: - Unicode characters Password length: Passwords require: - A minimum of eight characters - A maximum of 256 characters Password complexity: Passwords require three out of four of the following categories: - Uppercase characters - Lowercase characters - Numbers - Symbols Note: Password complexity check isn't required for Education tenants. Password not recently used: - When a user changes or resets their password, the new password can't be the same as the current or recently used passwords. - Password isn't banned by Entra ID Password Protection. - The password can't be on the global list of banned passwords for Azure AD Password Protection, or on the customizable list of banned passwords specific to your organization. Evaluation New passwords are evaluated for strength and complexity by validating against the combined list of terms from the global and custom banned password lists. Even if a user's password contains a banned password, the password may be accepted if the overall password is otherwise strong enough.",
+ "DefaultValue": "By default the custom banned password list is not 'Enabled'.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-password-ban-bad#custom-banned-password-list:https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-configure-custom-password-protection:https://www.microsoft.com/en-us/research/publication/password-guidance/:https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-6-use-strong-authentication-controls"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.3",
+ "Description": "Microsoft Entra Password Protection provides a global and custom banned password list. A password change request fails if there's a match in these banned password list. To protect on-premises Active Directory Domain Services (AD DS) environment, install and configure Entra Password Protection. Note: This recommendation applies to Hybrid deployments only and will have no impact unless working with on-premises Active Directory.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra Password Protection provides a global and custom banned password list. A password change request fails if there's a match in these banned password list. To protect on-premises Active Directory Domain Services (AD DS) environment, install and configure Entra Password Protection. Note: This recommendation applies to Hybrid deployments only and will have no impact unless working with on-premises Active Directory.",
+ "RationaleStatement": "This feature protects an organization by prohibiting the use of weak or leaked passwords. In addition, organizations can create custom banned password lists to prevent their users from using easily guessed passwords that are specific to their industry. Deploying this feature to Active Directory will strengthen the passwords that are used in the environment.",
+ "ImpactStatement": "The potential impact associated with implementation of this setting is dependent upon the existing password policies in place in the environment. For environments that have strong password policies in place, the impact will be minimal. For organizations that do not have strong password policies in place, implementation of Microsoft Entra Password Protection may require users to change passwords and adhere to more stringent requirements than they have been accustomed to.",
+ "RemediationProcedure": "To remediate using the UI: - Download and install the Azure AD Password Proxies and DC Agents from the following location: https://www.microsoft.com/download/details.aspx?id=57071 After installed follow the steps below. 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Set Enable password protection on Windows Server Active Directory to Yes and Mode to Enforced.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Verify that Enable password protection on Windows Server Active Directory is set to Yes and that Mode is set to Enforced. To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Directory.Read.All\" 2. Run the following command: (Get-MgGroupSetting | ? { $_.TemplateId -eq '5cf42378-d67d-4f36-ba46- e8b86229381d' }).Values 3. Verify that EnableBannedPasswordCheckOnPremises is set to True and BannedPasswordCheckOnPremisesMode is set to Enforce.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enable - Yes Mode - Audit",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-password-ban-bad-on-premises-operations"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.4",
+ "Description": "Microsoft defines Multifactor authentication capable as being registered and enabled for a strong authentication method. The method must also be allowed by the authentication methods policy. Ensure all member users are MFA capable.",
+ "Checks": [
+ "entra_users_mfa_capable"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft defines Multifactor authentication capable as being registered and enabled for a strong authentication method. The method must also be allowed by the authentication methods policy. Ensure all member users are MFA capable.",
+ "RationaleStatement": "Multifactor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Users who are not MFA Capable have never registered a strong authentication method for multifactor authentication that is within policy and may not be using MFA. This could be a result of having never signed in, exclusion from a Conditional Access (CA) policy requiring MFA, or a CA policy does not exist. Reviewing this list of users will help identify possible lapses in policy or procedure.",
+ "ImpactStatement": "When using the UI audit method guest users will appear in the report and unless the organization is applying MFA rules to guests then they will need to be manually filtered. Accounts that provide on-premises directory synchronization also appear in these reports.",
+ "RemediationProcedure": "Remediation steps will depend on the status of the personnel in question or configuration of Conditional Access policies and will not be covered in detail. Administrators should review each user identified on a case-by-case basis using the conditions below. User has never signed on: - Employment status should be reviewed, and appropriate action taken on the user account's roles, licensing and enablement. Conditional Access policy applicability: - Ensure a CA policy is in place requiring all users to use MFA. - Ensure the user is not excluded from the CA MFA policy. - Ensure the policy's state is set to On. - Use What if to determine applicable CA policies. (Protection > Conditional Access > Policies) - Review the user account in Sign-in logs. Under the Activity Details pane click the Conditional Access tab to view applied policies. Note: Conditional Access is covered step by step in section 5.2.2",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select User registration details. 3. Set the filter option Multifactor authentication capable to Not Capable. 4. Review the non-guest users in this list. 5. Excluding any exceptions users found in this report may require remediation. To audit using PowerShell: 1. Connect to Graph using Connect-MgGraph -Scopes \"UserAuthenticationMethod.Read.All,AuditLog.Read.All\" 2. Run the following: Get-MgReportAuthenticationMethodUserRegistrationDetail ` -Filter \"IsMfaCapable eq false and UserType eq 'Member'\" | ft UserPrincipalName,IsMfaCapable,IsAdmin 3. Verify that IsMfaCapable is set to True. 4. Excluding any exceptions users found in this report may require remediation. Note: The CA rule must be in place for a successful deployment of Multifactor Authentication. This policy is outlined in the conditional access section 5.2.2 Note 2: Possible exceptions include on-premises synchronization accounts.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.reports/update-mgreportauthenticationmethoduserregistrationdetail?view=graph-powershell-0#-ismfacapable:https://learn.microsoft.com/en-us/entra/identity/monitoring-health/how-to-view-applied-conditional-access-policies:https://learn.microsoft.com/en-us/entra/identity/conditional-access/what-if-tool:https://learn.microsoft.com/en-us/entra/identity/authentication/howto-authentication-methods-activity"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.5",
+ "Description": "Authentication methods support a wide variety of scenarios for signing in to Microsoft 365 resources. Some of these methods are inherently more secure than others but require more investment in time to get users enrolled and operational. SMS and Voice Call rely on telephony carrier communication methods to deliver the authenticating factor. The recommended state is to Disable these methods: - SMS - Voice Call",
+ "Checks": [
+ "entra_authentication_method_sms_voice_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Authentication methods support a wide variety of scenarios for signing in to Microsoft 365 resources. Some of these methods are inherently more secure than others but require more investment in time to get users enrolled and operational. SMS and Voice Call rely on telephony carrier communication methods to deliver the authenticating factor. The recommended state is to Disable these methods: - SMS - Voice Call",
+ "RationaleStatement": "Traditional MFA methods such as SMS codes, email-based OTPs, and push notifications are becoming less effective against today's attackers. Sophisticated phishing campaigns have demonstrated that second factors can be intercepted or spoofed. Attackers now exploit social engineering, man-in-the-middle tactics, and user fatigue (e.g., MFA bombing) to bypass these mechanisms. These risks are amplified in distributed, cloud-first organizations with hybrid workforces and varied device ecosystems. The SMS and Voice call methods are vulnerable to SIM swapping which could allow an attacker to gain access to your Microsoft 365 account.",
+ "ImpactStatement": "There may be increased administrative overhead in adopting more secure authentication methods depending on the maturity of the organization.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Policies. 3. Inspect each method that is out of compliance and remediate: o Click on the method to open it. o Change the Enable toggle to the off position. o Click Save. Note: If the save button remains greyed out after toggling a method off, then first turn it back on and then change the position of the Target selection (all users or select groups). Turn the method off again and save. This was observed to be a bug in the UI at the time this document was published. To remediate using Powershell: 1. Connect to Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.AuthenticationMethod\" 2. Run the following to disable both authentication methods: $params = @( @{ Id = \"Sms\"; State = \"disabled\" }, @{ Id = \"Voice\"; State = \"disabled\" } ) Update-MgPolicyAuthenticationMethodPolicy -AuthenticationMethodConfigurations $params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Policies. 3. Verify that the following methods in the Enabled column are set to No. o Method: SMS o Method: Voice call To audit using Powershell: 1. Connect to Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following: (Get-MgPolicyAuthenticationMethodPolicy).AuthenticationMethodConfigurations 3. Verify that Sms and Voice are disabled.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- SMS : Disabled - Voice Call : Disabled",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods-manage:https://learn.microsoft.com/en-us/security/zero-trust/sfi/phishing-resistant-mfa#context-and-problem:https://www.microsoft.com/en-us/microsoft-365-life-hacks/privacy-and-safety/what-is-sim-swapping"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.6",
+ "Description": "System-preferred multifactor authentication (MFA) prompts users to sign in by using the most secure method they registered. The user is prompted to sign-in with the most secure method according to the below order. The order of authentication methods is dynamic. It's updated by Microsoft as the security landscape changes, and as better authentication methods emerge. 1. Temporary Access Pass 2. Passkey (FIDO2) 3. Microsoft Authenticator notifications 4. External authentication methods 5. Time-based one-time password (TOTP) 6. Telephony 7. Certificate-based authentication The recommended state is Enabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "System-preferred multifactor authentication (MFA) prompts users to sign in by using the most secure method they registered. The user is prompted to sign-in with the most secure method according to the below order. The order of authentication methods is dynamic. It's updated by Microsoft as the security landscape changes, and as better authentication methods emerge. 1. Temporary Access Pass 2. Passkey (FIDO2) 3. Microsoft Authenticator notifications 4. External authentication methods 5. Time-based one-time password (TOTP) 6. Telephony 7. Certificate-based authentication The recommended state is Enabled.",
+ "RationaleStatement": "Regardless of the authentication method enabled by an administrator or set as preferred by the user, the system will dynamically select the most secure option available at the time of authentication. This approach acts as an additional safeguard to prevent the use of weaker methods, such as voice calls, SMS, and email OTPs, which may have been inadvertently left enabled due to misconfiguration or lack of configuration hardening. Enforcing the default behavior also ensures the feature is not disabled.",
+ "ImpactStatement": "The Microsoft managed value of system-preferred MFA is Enabled and as such enforces the default behavior. No additional impact is expected. Note: Due to known issues with certificate-based authentication (CBA) and system- preferred MFA, Microsoft moved CBA to the bottom of the list. It is still considered a strong authentication method.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Settings. 3. Set the System-preferred multifactor authentication State to Enabled and include All users. 4. Any users exclusions should be documented and reviewed annually.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Settings. 3. Verify the System-preferred multifactor authentication State is set to Enabled and All users are included. 4. Verify that only documented exclusions exist and that they are reviewed annually To audit using PowerShell: 1. Connect to Microsoft Graph using Connect-MgGraph -Scopes \"Policy.Read.AuthenticationMethod\" 2. Run the following commands: $Uri = 'https://graph.microsoft.com/beta/policies/authenticationMethodsPolicy' (Invoke-MgGraphRequest -Method GET -Uri $Uri).systemCredentialPreferences 3. Verify that includeTargets is set to all_users and state is set to enabled.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Microsoft Managed (Enabled)",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-system-preferred-multifactor-authentication:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-system-preferred-multifactor-authentication#how-does-system-preferred-mfa-determine-the-most-secure-method"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.7",
+ "Description": "Authentication methods support a wide variety of scenarios for signing in to Microsoft 365 resources. Some of these methods are inherently more secure than others but require more investment in time to get users enrolled and operational. The email one-time passcode feature is a way to authenticate B2B collaboration users when they can't be authenticated through other means, such as Microsoft Entra ID, Microsoft account (MSA), or social identity providers. When a B2B guest user tries to redeem your invitation or sign in to your shared resources, they can request a temporary passcode, which is sent to their email address. Then they enter this passcode to continue signing in. The recommended state is to Disable email OTP.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Authentication methods support a wide variety of scenarios for signing in to Microsoft 365 resources. Some of these methods are inherently more secure than others but require more investment in time to get users enrolled and operational. The email one-time passcode feature is a way to authenticate B2B collaboration users when they can't be authenticated through other means, such as Microsoft Entra ID, Microsoft account (MSA), or social identity providers. When a B2B guest user tries to redeem your invitation or sign in to your shared resources, they can request a temporary passcode, which is sent to their email address. Then they enter this passcode to continue signing in. The recommended state is to Disable email OTP.",
+ "RationaleStatement": "Traditional MFA methods such as SMS codes, email-based OTPs, and push notifications are becoming less effective against today's attackers. Sophisticated phishing campaigns have demonstrated that second factors can be intercepted or spoofed. Attackers now exploit social engineering, man-in-the-middle tactics, and user fatigue (e.g., MFA bombing) to bypass these mechanisms. These risks are amplified in distributed, cloud-first organizations with hybrid workforces and varied device ecosystems.",
+ "ImpactStatement": "Disabling Email OTP will prevent one-time pass codes from being sent to unverified guest users accessing Microsoft 365 resources on the tenant such as \"@yahoo.com\". They will be required to use a personal Microsoft account, a managed Microsoft Entra account, be part of a federation or be configured as a guest in the host tenant's Microsoft Entra ID.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Policies. 3. Click on Email OTP. 4. Change the Enable toggle to the off position\\ 5. Click Save. Note: If the save button remains greyed out after toggling a method off, then first turn it back on and then change the position of the Target selection (all users or select groups). Turn the method off again and save. This was observed to be a bug in the UI at the time this document was published. To remediate using Powershell: 1. Connect to Graph using Connect-MgGraph -Scopes \"Policy.ReadWrite.AuthenticationMethod\" 2. Run the following: $params = @( @{ Id = \"Email\"; State = \"disabled\" } ) Update-MgPolicyAuthenticationMethodPolicy -AuthenticationMethodConfigurations $params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Policies. 3. Verify that Email OTP is set to No in the Enabled column. To audit using Powershell: 1. Connect to Graph using Connect-MgGraph -Scopes \"Policy.Read.All\" 2. Run the following: (Get-MgPolicyAuthenticationMethodPolicy).AuthenticationMethodConfigurations 3. Verify the id type Email is set to disabled.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Email OTP : Enabled",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods-manage:https://learn.microsoft.com/en-us/entra/external-id/one-time-passcode:https://learn.microsoft.com/en-us/security/zero-trust/sfi/phishing-resistant-mfa#context-and-problem"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.8",
+ "Description": "The account lockout threshold determines how many failed login attempts are permitted prior to placing the account in a locked-out state and initiating a variable lockout duration. The recommended Lockout threshold is 10 or less.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The account lockout threshold determines how many failed login attempts are permitted prior to placing the account in a locked-out state and initiating a variable lockout duration. The recommended Lockout threshold is 10 or less.",
+ "RationaleStatement": "Account lockout is a method of protecting against brute-force and password spray attacks. Once the lockout threshold has been exceeded, the account enters a locked- out state which prevents all login attempts for a variable duration. The lockout in combination with a reasonable duration reduces the total number of failed login attempts that a malicious actor can execute in a given period of time.",
+ "ImpactStatement": "If account lockout threshold is set too low (less than 3), users may experience frequent lockout events and the resulting security alerts may contribute to alert fatigue. If account lockout threshold is set too high (more than 10), malicious actors can programmatically execute more password attempts in a given period of time. In hybrid environments using pass-through authentication (PTA), the Microsoft Entra lockout threshold must be set lower than the AD DS account lockout threshold. If the AD DS threshold is equal to or lower than the Entra threshold, AD DS will lock the account before Entra smart lockout activates, bypassing the cloud-side protection and resulting in on-premises account lockouts that require manual administrator intervention to clear. Microsoft recommends configuring the AD DS lockout threshold to be at least two to three times greater than the Entra lockout threshold.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Set Lockout threshold to 10 or less. Note: In hybrid environments using pass-through authentication (PTA), Microsoft recommends to configure the AD DS account lockout threshold to be at least two to three times greater than the value set here to ensure Entra smart lockout activates before AD DS lockout.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Verify that Lockout threshold is set to 10 or less. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/groupSettings 2. Filter to Password Rule settings, where templateId is 5cf42378-d67d-4f36- ba46-e8b86229381d 3. Verify that LockoutThreshold is 10 or less.",
+ "AdditionalInformation": "NOTE: The variable number for failed login attempts allowed before lockout is prescribed by many security and compliance frameworks. The appropriate setting for this variable should be determined by the most restrictive security or compliance framework that your organization follows.",
+ "DefaultValue": "By default, Lockout threshold is set to 10.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-password-smart-lockout#manage-microsoft-entra-smart-lockout-values:https://learn.microsoft.com/en-us/graph/api/group-list-settings?view=graph-rest-0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.9",
+ "Description": "The account lockout duration value determines how long an account retains the status of lockout, and therefore how long before a user can continue to attempt to login after passing the lockout threshold. The recommended state is Lockout duration in seconds is at least 60.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The account lockout duration value determines how long an account retains the status of lockout, and therefore how long before a user can continue to attempt to login after passing the lockout threshold. The recommended state is Lockout duration in seconds is at least 60.",
+ "RationaleStatement": "Account lockout is a method of protecting against brute-force and password spray attacks. Once the lockout threshold has been exceeded, the account enters a locked- out state which prevents all login attempts for a variable duration. The lockout in combination with a reasonable duration reduces the total number of failed login attempts that a malicious actor can execute in a given period of time.",
+ "ImpactStatement": "If account lockout duration is set too low (less than 60 seconds), malicious actors can perform more password spray and brute-force attempts over a given period of time. If the account lockout duration is set too high (more than 300 seconds) users may experience inconvenient delays during lockout. In hybrid environments using pass-through authentication (PTA), the Microsoft Entra lockout duration must be set longer than the AD DS account lockout duration. Note that Entra lockout duration is configured in seconds while AD DS lockout duration is configured in minutes; verify the units when comparing the two values to ensure Entra smart lockout expires after AD DS lockout.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Set the Lockout duration in seconds to 60 or higher. 4. Click Save. Note: In hybrid environments using pass-through authentication (PTA), ensure the AD DS account lockout duration is shorter than the value set here. The Entra lockout duration is configured in seconds while AD DS lockout duration is configured in minutes; account for the unit difference when comparing the two values.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Authentication methods and select Password protection. 3. Verify that Lockout duration in seconds is set to 60 or higher. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/groupSettings 2. Filter to Password Rule settings, where templateId is 5cf42378-d67d-4f36- ba46-e8b86229381d 3. Verify that LockoutDurationInSeconds is greater than or equal to 60.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default, Lockout duration in seconds is set to 60.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-password-smart-lockout#manage-microsoft-entra-smart-lockout-values:https://learn.microsoft.com/en-us/graph/api/group-list-settings?view=graph-rest-0"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.3.10",
+ "Description": "Microsoft Entra ID includes a feature called Authenticator Lite, which embeds a subset of Microsoft Authenticator functionality into companion applications such as Outlook mobile. When enabled, users can satisfy MFA requirements using push notifications or time-based one-time passcodes (TOTP) directly from the companion application without installing the standalone Microsoft Authenticator app. The recommended state is Microsoft Authenticator on companion applications set to Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.3 Authentication Methods",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra ID includes a feature called Authenticator Lite, which embeds a subset of Microsoft Authenticator functionality into companion applications such as Outlook mobile. When enabled, users can satisfy MFA requirements using push notifications or time-based one-time passcodes (TOTP) directly from the companion application without installing the standalone Microsoft Authenticator app. The recommended state is Microsoft Authenticator on companion applications set to Disabled.",
+ "RationaleStatement": "Authenticator Lite does not support application name or geographic location context in push notifications, regardless of tenant-wide Authenticator feature settings. These are key defenses against MFA fatigue attacks that are only available in the full Microsoft Authenticator app. Authenticator Lite also does not satisfy Conditional Access authentication strength requirements, does not support passwordless authentication, and does not support SSPR via push notifications. Disabling this feature ensures users authenticate through the full Microsoft Authenticator app where all available security protections are active.",
+ "ImpactStatement": "Users who have registered Authenticator Lite as their only MFA method will be unable to complete MFA until they install and register the standalone Microsoft Authenticator app. Administrators should communicate this change in advance and verify that affected users have registered an alternative MFA method before disabling this feature to avoid authentication lockouts.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Authentication methods and select Policies. 3. Under Method select Microsoft Authenticator. 4. Select Configure. 5. Set Microsoft Authenticator on companion applications: Status to Disabled. 6. Select Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to the Microsoft Entra admin center https://entra.microsoft.com. 2. Expand Entra ID > Authentication methods and select Policies. 3. Under Method select Microsoft Authenticator. 4. Select Configure. 5. Verify that Microsoft Authenticator on companion applications: Status is set to Disabled. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: beta/policies/authenticationMethodsPolicy/authenticationMethodConfigurations/ microsoftAuthenticator 2. Verify that featureSettings.companionAppAllowedState.state is disabled.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Microsoft managed (enabled as of June 26, 2023)",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-authenticator-lite:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-default-enablement:https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-additional-context"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4.1",
+ "Description": "Enabling self-service password reset allows users to reset their own passwords in Entra ID. When users sign in to Microsoft 365, they will be prompted to enter additional contact information that will help them reset their password in the future. If combined registration is enabled additional information, outside of multi-factor, will not be needed. The recommended state is All. Note: Effective Oct. 1st, 2022, Microsoft will begin to enable combined registration for all users in Entra ID tenants created before August 15th, 2020. Tenants created after this date are enabled with combined registration by default.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.4 Password reset",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "Enabling self-service password reset allows users to reset their own passwords in Entra ID. When users sign in to Microsoft 365, they will be prompted to enter additional contact information that will help them reset their password in the future. If combined registration is enabled additional information, outside of multi-factor, will not be needed. The recommended state is All. Note: Effective Oct. 1st, 2022, Microsoft will begin to enable combined registration for all users in Entra ID tenants created before August 15th, 2020. Tenants created after this date are enabled with combined registration by default.",
+ "RationaleStatement": "Enabling Self-Service Password Reset (SSPR) significantly reduces helpdesk interactions, streamlining support operations and improving user experience. Traditional methods involving temporary passwords pose notable security risks-they are often weak, predictable, and susceptible to interception. This creates a window of opportunity for threat actors to compromise accounts before users can update their credentials. SSPR minimizes credential exposure and strengthens overall identity protection.",
+ "ImpactStatement": "Users will be required to provide additional contact information in order to enroll in SSPR. Some light user education may be necessary, particularly for individuals who are accustomed to contacting the help desk for password reset assistance. In hybrid environments, SSPR writeback must be enabled before users are able to reset their passwords through self-service.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Properties. 3. Set Self service password reset enabled to All",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Properties. 3. Verify that Self service password reset enabled is set to All",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/let-users-reset-passwords?view=o365-worldwide:https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr:https://learn.microsoft.com/en-us/entra/identity/authentication/howto-registration-mfa-sspr-combined:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-writeback"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4.2",
+ "Description": "Ensures that two alternate forms of identification are provided before allowing a password reset. The recommended state is Number of methods required to reset set to 2.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.4 Password reset",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Manual",
+ "Description": "Ensures that two alternate forms of identification are provided before allowing a password reset. The recommended state is Number of methods required to reset set to 2.",
+ "RationaleStatement": "Requiring Multi-factor Authentication (MFA) for Self-service Password Reset (SSPR) strengthens the password reset process by confirming the user's identity with two separate methods of authentication. With multiple methods required for password reset, an attacker would have to compromise multiple authentication methods before resetting a user's password.",
+ "ImpactStatement": "If multiple methods are required for password reset and a user has lost access to other authentication methods, the resetting user will need an administrator with permissions to remove the lost authentication method. Policy and training are recommended to teach administrators to verify the identity of the requesting user so that social engineering is not an effective vector of compromise. If multifactor authentication is not currently enabled for all users, users with only one registered form of authentication will not be able to reset their passwords through SSPR until another form of authentication is registered. If multifactor authentication is already enabled for all users, the impact of this recommendation should be minimal.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Authentication methods. 3. Set the Number of methods required to reset to 2 4. Click Save",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Authentication methods. 3. Verify that Number of methods required to reset is set to 2",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default, the Number of methods required to reset is 1.",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-registration-mfa-sspr-combined:https://support.microsoft.com/en-us/account-billing/reset-your-work-or-school-password-using-security-info-23dde81f-08bb-4776-ba72-e6b72b9dda9e:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4.3",
+ "Description": "The Require users to register when signing in? setting controls whether users are prompted to register their self-service password reset (SSPR) authentication methods at their next sign-in. When set to Yes, users who have not yet registered are prompted to do so upon signing in. The Number of days before users are asked to re-confirm their authentication information setting designates the period of time before registered users are prompted to re-confirm their existing authentication information is still valid, up to a maximum of 730 days. If set to 0 days, registered users will never be prompted to re-confirm their authentication information.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.4 Password reset",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "The Require users to register when signing in? setting controls whether users are prompted to register their self-service password reset (SSPR) authentication methods at their next sign-in. When set to Yes, users who have not yet registered are prompted to do so upon signing in. The Number of days before users are asked to re-confirm their authentication information setting designates the period of time before registered users are prompted to re-confirm their existing authentication information is still valid, up to a maximum of 730 days. If set to 0 days, registered users will never be prompted to re-confirm their authentication information.",
+ "RationaleStatement": "Without requiring users to register, users may never establish SSPR authentication methods, rendering the re-confirmation setting ineffective regardless of the value it is set to. When users do register authentication methods for self-service password reset (SSPR), those methods may become stale over time as phone numbers, email addresses, or other contact information changes. If re-confirmation is disabled, outdated recovery information persists indefinitely. An attacker who gains access to a former phone number or email address associated with a user's account can exploit that stale recovery information to reset the user's password and take over the account. Requiring registration and periodic re-confirmation ensures that the authentication methods on record remain accurate and under the user's control.",
+ "ImpactStatement": "Because both settings default to the compliant state, organizations that have not altered them will experience no impact. Re-enabling registration prompts unregistered users to register at their next sign-in; re-enabling re-confirmation prompts registered users to verify their information on the configured interval. Organizations with large user populations and short re-confirmation intervals should expect increased SSPR support volume.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Registration. 3. Set Require users to register when signing in? to Yes. 4. Set Number of days before users are asked to re-confirm their authentication information to any organization-approved value other than 0. 5. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Registration. 3. Verify that Require users to register when signing in? is set to Yes. 4. Verify that Number of days before users are asked to re-confirm their authentication information is not set to 0.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Require users to register when signing in?: Yes - Number of days before users are asked to re-confirm their authentication information: 180",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks#registration:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4.4",
+ "Description": "This setting determines whether or not users receive an email to their primary and alternate email addresses notifying them when their own password has been reset via the Self-Service Password Reset portal. The recommended state is Notify users on password resets? is set to Yes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.4 Password reset",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "This setting determines whether or not users receive an email to their primary and alternate email addresses notifying them when their own password has been reset via the Self-Service Password Reset portal. The recommended state is Notify users on password resets? is set to Yes.",
+ "RationaleStatement": "User notification on password reset is a proactive way of confirming password reset activity. It helps the user to recognize unauthorized password reset activities.",
+ "ImpactStatement": "Users will receive emails alerting them to password changes to both their primary and alternate emails.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Notifications. 3. Set Notify users on password resets? to Yes 4. Click Save.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Notifications. 3. Verify that Notify users on password resets? is set to Yes.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Yes",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr#set-up-notifications-and-customizations:https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks#notifications:https://support.microsoft.com/en-us/account-billing/reset-your-work-or-school-password-using-security-info-23dde81f-08bb-4776-ba72-e6b72b9dda9e"
+ }
+ ]
+ },
+ {
+ "Id": "5.2.4.5",
+ "Description": "This setting determines whether or not all global administrators receive an email to their primary email address when other administrators reset their own passwords via the Self-Service Password Reset Portal. The recommended state is Notify all admins when other admins reset their password? is set to Yes.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.2.4 Password reset",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "This setting determines whether or not all global administrators receive an email to their primary email address when other administrators reset their own passwords via the Self-Service Password Reset Portal. The recommended state is Notify all admins when other admins reset their password? is set to Yes.",
+ "RationaleStatement": "Administrator accounts are sensitive. Any password reset activity notification, when sent to all Administrators, ensures that all Global Administrators can passively confirm if such a reset is a common pattern within their group. For example, if all Administrators change their password every 30 days, any password reset activity before that may require administrator(s) to evaluate any unusual activity and confirm its origin.",
+ "ImpactStatement": "All Global Administrators will receive a notification from Azure every time a password is reset. This is useful for auditing procedures to confirm that there are no out of the ordinary password resets for Administrators. There is additional overhead, however, in the time required for Global Administrators to audit the notifications. This setting is only useful if all Global Administrators pay attention to the notifications and audit each one.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Notifications. 3. Set Notify all admins when other admins reset their password? to Yes 4. Click Save",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Password reset and select Notifications. 3. Verify that Notify all admins when other admins reset their password? is set to Yes",
+ "AdditionalInformation": "",
+ "DefaultValue": "No",
+ "References": "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks#notifications:https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr#set-up-notifications-and-customizations"
+ }
+ ]
+ },
+ {
+ "Id": "5.3.1",
+ "Description": "Microsoft Entra Privileged Identity Management (PIM) provides just-in-time (JIT) activation workflows for privileged Entra ID and Microsoft 365 roles, enabling time- bound access with approval and justification requirements. Rather than holding permanent role assignments, users are made eligible for a role and must explicitly activate it when needed. PIM supports requiring multi-factor authentication at activation, mandatory justification, approval workflows, and configurable activation durations.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.3 ID Governance",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra Privileged Identity Management (PIM) provides just-in-time (JIT) activation workflows for privileged Entra ID and Microsoft 365 roles, enabling time- bound access with approval and justification requirements. Rather than holding permanent role assignments, users are made eligible for a role and must explicitly activate it when needed. PIM supports requiring multi-factor authentication at activation, mandatory justification, approval workflows, and configurable activation durations.",
+ "RationaleStatement": "Permanent active role assignments expose privileged access continuously, regardless of whether a user is actively performing administrative tasks. If a permanently privileged account is compromised, an attacker immediately holds full role permissions with no time boundary. PIM eliminates standing privilege by requiring users to explicitly activate role assignments, scoping elevated access to a defined duration and requiring justification and, optionally, approval. This reduces the window of opportunity for both external attackers and insider threats to exploit privileged access.",
+ "ImpactStatement": "The implementation of Just in Time privileged access is likely to necessitate changes to administrator routine. Administrators will only be granted access to administrative roles when required. When administrators request role activation, they will need to document the reason for requiring role access, anticipated time required to have the access, and to reauthenticate to enable role access. Note: If all global admins become eligible then there will be no global admin to receive notifications, by default. Alerts are sent to TenantAdmins, including Global Administrators, by default. To ensure proper receipt, configure alerts to be sent to security or operations staff with valid email addresses or a security operations center. Otherwise, after adoption of this recommendation, alerts sent to TenantAdmins may go unreceived due to the lack of a licensed permanently active Global Administrator.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Roles & admins and select All roles. 3. For each user or group role assignment that is out of compliance: o Click on the role to open it in PIM. o Select the Active assignments tab. o Under action click Update or Remove. - If Update is selected, set the Assignment type to Eligible and click Save. - If Remove is selected, the assignment will be removed and the principal will no longer hold the role. 4. For each privileged role with a non-compliant service principal active assignment: 1. Open the Active assignments tab. 2. Click Update to modify the service principal assignment. 3. Uncheck Permanently assigned and set an appropriate end time to create a time-bound assignment based on business needs. 4. Click Save to apply the changes. 5. Repeat for any other privileged role assignments that are out of compliance. Note: CIS Safeguard 6.8, Define and Maintain Role-Based Access Control, recommends reviewing access on a recurring schedule, at least annually and more frequently as needed. This practice is strongly encouraged for service principals when defining time-bound assignments.",
+ "AuditProcedure": "Note: There is no programmatic way to reliably determine whether a principal is a designated break-glass account. Global Administrator assignments require manual review and judgment to confirm that any permanent assignments belong exclusively to the organization's two approved break-glass accounts. To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand Entra ID > Roles & admins and select All roles. 3. Select Add filters and apply the Privileged filter to scope the review to built- in and custom privileged roles. 4. For each PRIVILEGED role that has one or more assignments, perform the following review of active assignments: 1. Select the role to open it. 2. Open the Active assignments tab. 3. For each assignment where Type is User or Group, verify that State is Activated. - A State of Assigned is permitted only for approved break-glass accounts assigned to the Global Administrator role, and no more than 2 such accounts may hold this permanent assignment. 4. For each assignment where Type is Service principal, verify that State is Assigned and an End time is designated. 5. Compliance is met when all privileged role assignments meet the verification requirements in step 4. Usage of PIM for management of other administrator roles is recommended but not required for compliance. To audit using Microsoft Graph API: 1. Execute a GET request to the following relative URI to retrieve privileged roles (custom or built-in): beta/roleManagement/directory/roleDefinitions?$filter=isPrivileged eq true&$select=id,displayName,isPrivileged,isBuiltIn,isEnabled 2. Execute a GET request to the following relative URI to retrieve all instances of active role assignments: v1.0/roleManagement/directory/roleAssignmentScheduleInstances?$expand=princip al 3. Correlate by matching each assignment instance's roleDefinitionId to the privileged role list's id to produce a list of privileged role assignment instances. 4. For each privileged role assignment instance, verify the appropriate condition for the principal type: o For users and groups (principal@odata.type is #microsoft.graph.user or #microsoft.graph.group), verify that assignmentType is Activated. An assignmentType of Assigned is permitted only for approved break-glass accounts assigned to the Global Administrator role, and no more than 2 such accounts may hold this permanent assignment. o For service principals (principal@odata.type is #microsoft.graph.servicePrincipal), verify that assignmentType is Assigned and endDateTime is defined (time-bound assignment). 5. Compliance is met when all privileged role assignments meet the verification requirements in step 4. Usage of PIM for management of other administrator roles is recommended but not required for compliance.",
+ "AdditionalInformation": "In addition to enforcing just-in-time activation for active privileged role assignments, organizations are encouraged to periodically review eligible PIM role assignments to confirm ongoing business justification and remove stale entries. Annual review at minimum is recommended. This is a governance process that requires manual judgment and is outside the scope of the automated compliance check for this recommendation.",
+ "DefaultValue": "Without Privileged Identity Management configured, all privileged role assignments are permanent active assignments with no expiration or activation requirement.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure"
+ }
+ ]
+ },
+ {
+ "Id": "5.3.2",
+ "Description": "Access reviews enable administrators to establish an efficient automated process for reviewing group memberships, access to enterprise applications, and role assignments. These reviews can be scheduled to recur regularly, with flexible options for delegating the task of reviewing membership to different members of the organization. When configured for guest users, access reviews can automatically remove access if no reviewer responds within the review period, enforcing a fail-closed posture for external identities.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.3 ID Governance",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Access reviews enable administrators to establish an efficient automated process for reviewing group memberships, access to enterprise applications, and role assignments. These reviews can be scheduled to recur regularly, with flexible options for delegating the task of reviewing membership to different members of the organization. When configured for guest users, access reviews can automatically remove access if no reviewer responds within the review period, enforcing a fail-closed posture for external identities.",
+ "RationaleStatement": "Access to groups and applications for guests can change over time. If a guest user's access to a particular resource goes unnoticed, they may unintentionally gain access to sensitive data if a member adds new files or data to the resource. Access reviews can help reduce the risks associated with outdated assignments by requiring a member of the organization to conduct the reviews. Furthermore, these reviews can enable a fail- closed mechanism to remove access to the subject if the reviewer does not respond to the review.",
+ "ImpactStatement": "Legitimate guest users may lose access to resources if designated reviewers fail to respond within the review window, requiring re-invitation and re-provisioning of access. Organizations with a large number of Microsoft 365 groups may face significant reviewer workload from monthly review cycles, which can lead to approval fatigue. - Microsoft Entra ID Governance licensing (included in Microsoft 365 E5) is required to configure access reviews. - As of January 15, 2026, a linked Azure subscription is required to use Entra ID Governance features for guest users.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand ID Governance and select Access reviews 3. Click New access review. 4. In the Resource review box click Select. 5. In Review Type set the following: o Select what to review choose Teams + Groups. o Review Scope to All Microsoft 365 groups with guest users. o Scope to Guest users only then click Next: Reviews. 6. In Reviews set the following: o Select reviewers to Group members or Selected users and groups, ensuring that at least one reviewer is assigned and that the guest is not performing a self-review. o Duration (in days) to 14 days or less. o Review recurrence to Monthly or more frequent. o Start date for the review, ensuring the review becomes active before the next audit date. o End to Never, then click Next: Settings. 7. In Settings set the following: o Auto apply results to resource is checked. o If reviewers don't respond to Remove access o Justification required is checked. o E-mail notifications is checked. o Reminders is checked. o Click Next: Review + Create 8. Click Create. To remediate using the Microsoft Graph API: To create a new access review, execute a POST request to the following relative URI. To update an existing review, execute a PATCH request to the same URI appended with the review's id: v1.0/identityGovernance/accessReviews/definitions The request body must include properties that satisfy the audit criteria above. The Graph API documentation provides complete sample request bodies in multiple languages including HTTP, PowerShell, and Python. See Reference 3 for details.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand ID Governance and select Access reviews 3. Inspect the access reviews, and verify an access review is created with the following criteria: o Overview: Scope is set to Guest users only and Review status is Active o Reviewers: At least one reviewer is assigned, and the reviewer is not a guest user. o Settings > General: - Mail notifications is set to Enable - Reminders is set to Enable o Settings > Reviewers: - Require reason on approval is set to Enable o Settings > Scheduling: - Frequency is set to Monthly or more frequent - Duration (in days) does not exceed 14 days - End is set to Never o Settings > When completed: - Auto apply results to resource is set to Enable - If reviewers don't respond is set to Remove access 4. The control is compliant if there is at least one access review for guests that meets all criteria above. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identityGovernance/accessReviews/definitions 2. Apply the following filters to identify access reviews targeting guest users: o scope.resourceScopes.query matches the pattern userType eq 'Guest' OR o scope.query matches the pattern userType eq 'Guest' 3. For each review that passes the filters above, verify the following criteria: o Recurrence is configured as monthly or more frequent: - recurrence.pattern.type is absoluteMonthly OR - recurrence.pattern.type is weekly o reviewers is not empty o settings.mailNotificationsEnabled is true o settings.instanceDurationInDays is 14 days or less o settings.reminderNotificationsEnabled is true o settings.justificationRequiredOnApproval is true o settings.autoApplyDecisionsEnabled is true o settings.defaultDecision is Deny o settings.recurrence.range.type is noEnd 4. The control is compliant if there is at least one access review for guests that meets all criteria above.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default access reviews are not configured.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-governance/access-reviews-overview:https://learn.microsoft.com/en-us/entra/id-governance/create-access-review:https://learn.microsoft.com/en-us/graph/api/resources/accessreviewscheduledefinition?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.3.3",
+ "Description": "Access reviews in Microsoft Entra Privileged Identity Management (PIM) enable administrators to periodically validate whether users still require their privileged role assignments. These reviews can be scheduled to recur on a regular cadence and can be delegated to reviewers other than the role holders themselves, such as security auditors.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.3 ID Governance",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Access reviews in Microsoft Entra Privileged Identity Management (PIM) enable administrators to periodically validate whether users still require their privileged role assignments. These reviews can be scheduled to recur on a regular cadence and can be delegated to reviewers other than the role holders themselves, such as security auditors.",
+ "RationaleStatement": "Regular review of critical high privileged roles in Entra ID will help identify role drift, or potential malicious activity. This will enable the practice and application of \"separation of duties\" where even non-privileged users like security auditors can be assigned to review assigned roles in an organization. These reviews can optionally be configured to automatically remove access if a reviewer does not respond within the review window, though this recommendation conservatively sets non-response to result in no change to avoid inadvertent removal of privileged accounts including break-glass accounts.",
+ "ImpactStatement": "In order to avoid disruption reviewers who have the authority to revoke roles should be trusted individuals who understand the significance of access reviews. Additionally, the principle of separation of duties should be applied to ensure that no administrator is responsible for reviewing their own access levels. This will cause additional administrative overhead. If the reviews are configured to automatically revoke highly privileged roles like the Global Administrator role, then this could result in removing all Global Administrators from the organization. Care should be taken when configuring this setting especially in the case of break-glass accounts which would be included in the scope. - Microsoft Entra ID Governance licensing (included in Microsoft 365 E5) is required to configure access reviews.",
+ "RemediationProcedure": "Note: An access review is created for each role selected after completing the process. To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand ID Governance > Privileged Identity Management. 3. Select Microsoft Entra Roles under Manage. 4. Select Access reviews and click New. o Provide a name and description. o Set Frequency to Monthly or more frequently. o Set Duration (in days) to at most 14. o Set End to Never. o Set Users scope to All users and groups. o In Role select the directory roles outlined in the Additional Information section. o Set Assignment type to All active and eligible assignments. o Set Reviewers to member(s) responsible for this type of review, other than self. 5. In Upon completion settings set the following: o Auto apply results to resource to Enable. o If reviewers don't respond to No change. 6. In Advanced settings set the following: o Require reason on approval to Enable o Mail notifications to Enable o Reminders to Enable 7. Click Start to save and begin the review series. Warning: Care should be taken when configuring the If reviewers don't respond setting for Global Administrator reviews, if misconfigured break-glass accounts could automatically have roles revoked. Additionally, reviewers should be educated on the purpose of break-glass accounts to prevent accidental manual removal of roles. To remediate using the Microsoft Graph API: To create a new access review, execute a POST request to the following relative URI. To update an existing review, execute a PATCH request to the same URI appended with the review's id: v1.0/identityGovernance/accessReviews/definitions The request body must include properties that satisfy the audit criteria above. The Graph API documentation provides complete sample request bodies in multiple languages including HTTP, PowerShell, and Python. See Reference 3 for details",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/ 2. Expand ID Governance > Privileged Identity Management. 3. Select Microsoft Entra Roles under Manage. 4. Select Access reviews 5. For each privileged role listed in the Additional Information section, verify an access review exists that meets the following criteria: o Overview: - Role assignment type is set to Eligible and Active - Scope is set to Everyone - Review status is Active o Reviewers: At least one reviewer is assigned, and the reviewer is not self- reviewing. o Settings > General: - Mail notifications is set to Enable - Reminders is set to Enable o Settings > Reviewers: - Require reason on approval is set to Enable o Settings > Scheduling: - Frequency is set to Monthly or more frequently - Duration (in days) does not exceed 14 days - End is set to Never o Settings > When completed: - Auto apply results to resource is set to Enable - If reviewers don't respond is set to No change To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI: v1.0/identityGovernance/accessReviews/definitions 2. Apply the following filters to identify relevant access review definitions: o scope.resourceScopes.query matches the pattern /directory/roleDefinitions/ o scope.resourceScopes.query matches the GUID of one of the 6 privileged directory roles outlined in the Additional Information section. 3. For each review that passes the filters above, verify the following criteria: o Scoped to Eligible and Active role assignments: - scope.principalScopes.query contains /v1.0/users AND - scope.principalScopes.query contains /v1.0/groups o Recurrence is configured as monthly or more frequent: - recurrence.pattern.type is absoluteMonthly OR - recurrence.pattern.type is weekly - recurrence.range.startDate is in the past relative to the audit date o reviewers is not empty o settings.mailNotificationsEnabled is true o settings.reminderNotificationsEnabled is true o settings.justificationRequiredOnApproval is true o settings.instanceDurationInDays is less than or equal to 14 o settings.autoApplyDecisionsEnabled is true o settings.defaultDecision is None 4. The control is compliant when all 6 privileged directory roles have an associated access review definition that meets all the criteria listed above. Note: The 6 roles referenced and their associated GUIDs can be found in the Additional Information section.",
+ "AdditionalInformation": "The 6 privileged directory roles referenced in the audit and remediation procedures and their associated GUIDs are as follows: Role Name Role Definition GUID Global Administrator 62e90394-69f5-4237-9190-012177145e10 Privileged Role Administrator e8611ab8-c189-46e8-94e1-60213ab1f814 Exchange Administrator 29232cdf-9323-42fd-ade2-1d097af3e4de SharePoint Administrator f28a1f50-f6e7-4571-818b-6a12f2af6b6c Teams Administrator 69091246-20e8-4a56-aa4d-066075b2a7a8 Security Administrator 194ae4cb-b126-40b2-bd5b-6091b380977d",
+ "DefaultValue": "By default access reviews are not configured.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-create-roles-and-resource-roles-review:https://learn.microsoft.com/en-us/entra/id-governance/access-reviews-overview:https://learn.microsoft.com/en-us/graph/api/resources/accessreviewscheduledefinition?view=graph-rest-1.0"
+ }
+ ]
+ },
+ {
+ "Id": "5.3.4",
+ "Description": "Microsoft Entra Privileged Identity Management can be used to audit roles, allow just in time activation of roles and allow for periodic role attestation. Requiring approval before activation allows one of the selected approvers to first review and then approve the activation prior to PIM granted the role. The approver doesn't have to be a group member or owner. The recommended state is Require approval to activate for the Global Administrator role.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.3 ID Governance",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra Privileged Identity Management can be used to audit roles, allow just in time activation of roles and allow for periodic role attestation. Requiring approval before activation allows one of the selected approvers to first review and then approve the activation prior to PIM granted the role. The approver doesn't have to be a group member or owner. The recommended state is Require approval to activate for the Global Administrator role.",
+ "RationaleStatement": "Requiring approval for Global Administrator role activation enhances visibility and accountability every time this highly privileged role is used. This process reduces the risk of an attacker elevating a compromised account to the highest privilege level, as any activation must first be reviewed and approved by a trusted party. Note: This only acts as protection for eligible users that are activating a role. Directly assigning a role does not require an approval workflow so therefore it is important to implement and use PIM correctly.",
+ "ImpactStatement": "Approvers do not need to be assigned the same role or be members of the same group. It's important to have at least two approvers and an emergency access (break-glass) account to prevent a scenario where no Global Administrators are available. For example, if the last active Global Administrator leaves the organization, and only eligible but inactive Global Administrators remain, a trusted approver without the Global Administrator role or an emergency access account would be essential to avoid delays in critical administrative tasks.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand ID Governance > Privileged Identity Management. 3. Under Manage select Microsoft Entra Roles. 4. Under Manage select Roles. 5. Select Global Administrator in the list. 6. Select Role settings and click Edit. 7. Check the Require approval to activate box. 8. Add at least one approver. 9. Click Update.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand ID Governance > Privileged Identity Management. 3. Under Manage select Microsoft Entra Roles. 4. Under Manage select Roles. 5. Select Global Administrator in the list. 6. Select Role settings. 7. Verify that Require approval to activate is set to Yes. 8. Verify there is at least 1 approvers in the list. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI to retrieve the policyID for the Global Administrator-role: v1.0/policies/roleManagementPolicyAssignments?$filter=scopeId eq '/' and scopeType eq 'DirectoryRole' and roleDefinitionId eq '62e90394-69f5-4237- 9190-012177145e10'&$select=policyId 2. Execute a GET request to the following relative URI to retrieve the policy's Approval setting using the policyId from the previous call: v1.0/policies/roleManagementPolicies/{policyID}/rules/Approval_EndUser_Assign ment # Example https://graph.microsoft.com/v1.0/policies/roleManagementPolicies/DirectoryRol e_9c4d49a8-1f7a-4256-b1a2-b7cb0e7180f4_86522f3f-cfd0-4634-95a0- 38083127ca00/rules/Approval_EndUser_Assignment 3. Verify that isApprovalRequired is true. 4. Verify that approvalStages.primaryApprovers contains one or more valid users. Note: Approvers should be reviewed on a regular basis to ensure the members are active and valid.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Require approval to activate : No.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure:https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/groups-role-settings#require-approval-to-activate"
+ }
+ ]
+ },
+ {
+ "Id": "5.3.5",
+ "Description": "Microsoft Entra Privileged Identity Management can be used to audit roles, allow just in time activation of roles and allow for periodic role attestation. Requiring approval before activation allows one of the selected approvers to first review and then approve the activation prior to PIM granted the role. The approver doesn't have to be a group member or owner. The recommended state is Require approval to activate for the Privileged Role Administrator role.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "5 Microsoft Entra admin center",
+ "SubSection": "5.3 ID Governance",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Entra Privileged Identity Management can be used to audit roles, allow just in time activation of roles and allow for periodic role attestation. Requiring approval before activation allows one of the selected approvers to first review and then approve the activation prior to PIM granted the role. The approver doesn't have to be a group member or owner. The recommended state is Require approval to activate for the Privileged Role Administrator role.",
+ "RationaleStatement": "This role grants the ability to manage assignments for all Microsoft Entra roles including the Global Administrator role. This role does not include any other privileged abilities in Microsoft Entra ID like creating or updating users. However, users assigned to this role can grant themselves or others additional privilege by assigning additional roles. Requiring approval for activation enhances visibility and accountability every time this highly privileged role is used. This process reduces the risk of an attacker elevating a compromised account to the highest privilege level, as any activation must first be reviewed and approved by a trusted party. Note: This only acts as protection for eligible users that are activating a role. Directly assigning a role does not require an approval workflow so therefore it is important to implement and use PIM correctly.",
+ "ImpactStatement": "Requiring approvers for automatic role assignment can slightly increase administrative overhead and add delays to tasks.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand ID Governance > Privileged Identity Management. 3. Under Manage select Microsoft Entra Roles. 4. Under Manage select Roles. 5. Select Privileged Role Administrator in the list. 6. Select Role settings and click Edit. 7. Check the Require approval to activate box. 8. Add at least one approver. 9. Click Update.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Entra admin center https://entra.microsoft.com/. 2. Expand ID Governance > Privileged Identity Management. 3. Under Manage select Microsoft Entra Roles. 4. Under Manage select Roles. 5. Select Privileged Role Administrator in the list. 6. Select Role settings. 7. Verify Require approval to activate is set to Yes. 8. Verify there is at least one approvers in the list. To audit using the Microsoft Graph API: 1. Execute a GET request to the following relative URI to retrieve the policyID for the Privileged Role Administrator-role: v1.0/policies/roleManagementPolicyAssignments?$filter=scopeId eq '/' and scopeType eq 'DirectoryRole' and roleDefinitionId eq 'e8611ab8-c189-46e8- 94e1-60213ab1f814'&$select=policyId 2. Execute a GET request to the following relative URI to retrieve the policy's Approval setting using the policyId from the previous call: v1.0/policies/roleManagementPolicies/{policyID}/rules/Approval_EndUser_Assign ment # Example https://graph.microsoft.com/v1.0/policies/roleManagementPolicies/DirectoryRol e_d1fdbf46-5729-4c53-a951-7ab677be380f_3679e0d0-412a-444d-b517- ab23973d6067/rules/Approval_EndUser_Assignment 3. Verify that isApprovalRequired is true. 4. Verify that approvalStages.primaryApprovers contains one or more valid users. Note: Approvers should be reviewed on a regular basis to ensure the members are active and valid.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Require approval to activate : No.",
+ "References": "https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure:https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/groups-role-settings#require-approval-to-activate"
+ }
+ ]
+ },
+ {
+ "Id": "6.1.1",
+ "Description": "The value False indicates that mailbox auditing on by default is turned on for the organization. Mailbox auditing on by default in the organization overrides the mailbox auditing settings on individual mailboxes. For example, if mailbox auditing is turned off for a mailbox (the AuditEnabled property on the mailbox is False), the default mailbox actions are still audited for the mailbox, because mailbox auditing on by default is turned on for the organization. Turning off mailbox auditing on by default ($true) has the following results: - Mailbox auditing is turned off for your organization. - From the time you turn off mailbox auditing on by default, no mailbox actions are audited, even if mailbox auditing is enabled on a mailbox (the AuditEnabled property on the mailbox is True). - Mailbox auditing isn't turned on for new mailboxes and setting the AuditEnabled property on a new or existing mailbox to True is ignored. - Any mailbox audit bypass association settings (configured by using the Set- MailboxAuditBypassAssociation cmdlet) are ignored. - Existing mailbox audit records are retained until the audit log age limit for the record expires. The recommended state for this setting is False at the organization level. This will enable auditing and enforce the default.",
+ "Checks": [
+ "exchange_organization_mailbox_auditing_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.1 Audit",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The value False indicates that mailbox auditing on by default is turned on for the organization. Mailbox auditing on by default in the organization overrides the mailbox auditing settings on individual mailboxes. For example, if mailbox auditing is turned off for a mailbox (the AuditEnabled property on the mailbox is False), the default mailbox actions are still audited for the mailbox, because mailbox auditing on by default is turned on for the organization. Turning off mailbox auditing on by default ($true) has the following results: - Mailbox auditing is turned off for your organization. - From the time you turn off mailbox auditing on by default, no mailbox actions are audited, even if mailbox auditing is enabled on a mailbox (the AuditEnabled property on the mailbox is True). - Mailbox auditing isn't turned on for new mailboxes and setting the AuditEnabled property on a new or existing mailbox to True is ignored. - Any mailbox audit bypass association settings (configured by using the Set- MailboxAuditBypassAssociation cmdlet) are ignored. - Existing mailbox audit records are retained until the audit log age limit for the record expires. The recommended state for this setting is False at the organization level. This will enable auditing and enforce the default.",
+ "RationaleStatement": "Enforcing the default ensures auditing was not turned off intentionally or accidentally. Auditing mailbox actions will allow forensics and IR teams to trace various malicious activities that can generate TTPs caused by inbox access and tampering.",
+ "ImpactStatement": "None - this is the default behavior as of 2019.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-OrganizationConfig -AuditDisabled $false",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-OrganizationConfig | Format-List AuditDisabled 3. Verify that AuditDisabled is set to False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "False",
+ "References": "https://learn.microsoft.com/en-us/purview/audit-mailboxes?view=o365-worldwide:https://learn.microsoft.com/en-us/powershell/module/exchange/set-organizationconfig?view=exchange-ps#-auditdisabled"
+ }
+ ]
+ },
+ {
+ "Id": "6.1.2",
+ "Description": "Mailbox audit logging is turned on by default in all organizations. This effort started in January 2019, and means that certain actions performed by mailbox owners, delegates, and admins are automatically logged. The corresponding mailbox audit records are available for admins to search in the mailbox audit log. Mailboxes and shared mailboxes have actions assigned to them individually in order to audit the data the organization determines valuable at the mailbox level. The recommended state per mailbox is AuditEnabled to True including all default audit actions with additional actions outlined below in the audit and remediation sections. Note: Audit (Standard) licensing allows for up to 180 days log retention as of October 2023.",
+ "Checks": [
+ "exchange_user_mailbox_auditing_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.1 Audit",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Mailbox audit logging is turned on by default in all organizations. This effort started in January 2019, and means that certain actions performed by mailbox owners, delegates, and admins are automatically logged. The corresponding mailbox audit records are available for admins to search in the mailbox audit log. Mailboxes and shared mailboxes have actions assigned to them individually in order to audit the data the organization determines valuable at the mailbox level. The recommended state per mailbox is AuditEnabled to True including all default audit actions with additional actions outlined below in the audit and remediation sections. Note: Audit (Standard) licensing allows for up to 180 days log retention as of October 2023.",
+ "RationaleStatement": "Whether it is for regulatory compliance or for tracking unauthorized configuration changes in Microsoft 365, enabling mailbox auditing and ensuring the proper mailbox actions are accounted for allows for Microsoft 365 teams to run security operations, forensics or general investigations on mailbox activities. The following mailbox types ignore the organizational default and must have AuditEnabled set to True at the mailbox level in order to capture relevant audit data. - Resource Mailboxes - Public Folder Mailboxes - DiscoverySearch Mailbox",
+ "ImpactStatement": "Adding additional audit action types and increasing the AuditLogAgeLimit from 90 to 180 days will have a limited impact on mailbox storage. Mailbox audit log records are stored in a subfolder (named Audits) in the Recoverable Items folder in each user's mailbox. - Mailbox audit records count against the storage quota of the Recoverable Items folder. - Mailbox audit records also count against the folder limit for the Recoverable Items folder. A maximum of 3 million items (audit records) can be stored in the Audits subfolder. The following cmdlet in Exchange Online PowerShell can be run to display the size and number of items in the Audits subfolder in the Recoverable Items folder: Get-MailboxFolderStatistics -Identity <MailboxIdentity> -FolderScope RecoverableItems | Where-Object {$_.Name -eq 'Audits'} | Format-List FolderPath,FolderSize,ItemsInFolder Note: It's unlikely that mailbox auditing on by default impacts the storage quota or the folder limit for the Recoverable Items folder.",
+ "RemediationProcedure": "For each UserMailbox ensure AuditEnabled is True and the following audit actions are included in addition to default actions of each sign-in type. - Admin actions: Copy, FolderBind and Move. - Delegate actions: FolderBind and Move. - Owner actions: Create, MailboxLogin and Move. Note: The defaults can be found in the Default Value section and the combined total can be found in the scripts of the Audit/Remediation sections. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell script to remediate every 'UserMailbox' in the organization: $AuditAdmin = @( \"ApplyRecord\", \"Copy\", \"Create\", \"FolderBind\", \"HardDelete\", \"MailItemsAccessed\", \"Move\", \"MoveToDeletedItems\", \"SendAs\", \"SendOnBehalf\", \"Send\", \"SoftDelete\", \"Update\", \"UpdateCalendarDelegation\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) $AuditDelegate = @( \"ApplyRecord\", \"Create\", \"FolderBind\", \"HardDelete\", \"Move\", \"MailItemsAccessed\", \"MoveToDeletedItems\", \"SendAs\", \"SendOnBehalf\", \"SoftDelete\", \"Update\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) $AuditOwner = @( \"ApplyRecord\", \"Create\", \"HardDelete\", \"MailboxLogin\", \"Move\", \"MailItemsAccessed\", \"MoveToDeletedItems\", \"Send\", \"SoftDelete\", \"Update\", \"UpdateCalendarDelegation\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) $MBX = Get-EXOMailbox -ResultSize Unlimited | Where-Object { $_.RecipientTypeDetails -eq \"UserMailbox\" } $MBX | Set-Mailbox -AuditEnabled $true ` -AuditLogAgeLimit 180 -AuditAdmin $AuditAdmin -AuditDelegate $AuditDelegate ` -AuditOwner $AuditOwner 3. The script will apply the prescribed Audit Actions for each sign-in type (Owner, Delegate, Admin) and the AuditLogAgeLimit to each UserMailbox in the organization. Note: Mailboxes with Audit (Premium) licenses, which is included with E5, can retain audit logs beyond 180 days.",
+ "AuditProcedure": "Inspect each UserMailbox and ensure AuditEnabled is True and the following audit actions are included in addition to default actions of each sign-in type. - Admin actions: Copy, FolderBind and Move. - Delegate actions: FolderBind and Move. - Owner actions: Create, MailboxLogin and Move. Note: The defaults can be found in the Default Value section and the combined total can be found in the scripts of the Audit/Remediation sections. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell script: $AdminActions = @( \"ApplyRecord\", \"Copy\", \"Create\", \"FolderBind\", \"HardDelete\", \"MailItemsAccessed\", \"Move\", \"MoveToDeletedItems\", \"SendAs\", \"SendOnBehalf\", \"Send\", \"SoftDelete\", \"Update\", \"UpdateCalendarDelegation\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) $DelegateActions = @( \"ApplyRecord\", \"Create\", \"FolderBind\", \"HardDelete\", \"Move\", \"MailItemsAccessed\", \"MoveToDeletedItems\", \"SendAs\", \"SendOnBehalf\", \"SoftDelete\", \"Update\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) $OwnerActions = @( \"ApplyRecord\", \"Create\", \"HardDelete\", \"MailboxLogin\", \"Move\", \"MailItemsAccessed\", \"MoveToDeletedItems\", \"Send\", \"SoftDelete\", \"Update\", \"UpdateCalendarDelegation\", \"UpdateFolderPermissions\", \"UpdateInboxRules\" ) function VerifyActions { param ( [array]$ExpectedActions, [array]$ActualActions ) $Missing = $ExpectedActions | Where-Object { $_ -notin $ActualActions } return $Missing } $MBX = Get-EXOMailbox -PropertySets Audit, Minimum -ResultSize Unlimited | Where-Object { $_.RecipientTypeDetails -eq \"UserMailbox\" } $Results = foreach ($mailbox in $MBX) { $AdminMissing = VerifyActions -ExpectedActions $AdminActions ` -ActualActions $mailbox.AuditAdmin $DelegateMissing = VerifyActions -ExpectedActions $DelegateActions ` -ActualActions $mailbox.AuditDelegate $OwnerMissing = VerifyActions -ExpectedActions $OwnerActions ` -ActualActions $mailbox.AuditOwner $IsCompliant = $AdminMissing.Count -eq 0 -and $DelegateMissing.Count -eq 0 -and $OwnerMissing.Count -eq 0 -and $mailbox.AuditEnabled [PSCustomObject]@{ Mailbox = $mailbox.UserPrincipalName AuditEnabled = $mailbox.AuditEnabled AdminMissing = if ($AdminMissing.Count -gt 0) { $AdminMissing -join \", \" } else { \"None\" } DelegateMissing = if ($DelegateMissing.Count -gt 0) { $DelegateMissing -join \", \" } else { \"None\" } OwnerMissing = if ($OwnerMissing.Count -gt 0) { $OwnerMissing -join \", \" } else { \"None\" } ComplianceState = if ($IsCompliant) { \"Compliant\" } else { \"Non-Compliant\" } } } # Display results in table format $Results | Format-Table -AutoSize <# Optional: Export methods $Results | Out-GridView -Title \"Mailbox Audit Results\" $Results | Export-Csv -Path \"6.1.2.csv\" -NoTypeInformation $Results | ConvertTo-Json | Out-File -FilePath \"6.1.2.json\" #> 3. Inspect the results. Mailboxes will be labeled as either Compliant or Non- compliant, accompanied by supporting details that outline the missing actions for each type and the current state of AuditEnabled. Optional methods for exporting the data to CSV, JSON, or GridView are also shown at the end of the script. Note: Mailboxes with Audit (Premium) licenses, which is included with E5, can retain audit logs beyond 180 days.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AuditEnabled: True for all mailboxes except below: - Resource Mailboxes - Public Folder Mailboxes - DiscoverySearch Mailbox AuditAdmin: ApplyRecord, Create, HardDelete, MailItemsAccessed, MoveToDeletedItems, Send, SendAs, SendOnBehalf, SoftDelete, Update, UpdateCalendarDelegation, UpdateFolderPermissions, UpdateInboxRules AuditDelegate: ApplyRecord, Create, HardDelete, MailItemsAccessed, MoveToDeletedItems, SendAs, SendOnBehalf, SoftDelete, Update, UpdateFolderPermissions, UpdateInboxRules AuditOwner: ApplyRecord, HardDelete, MailItemsAccessed, MoveToDeletedItems, Send, SoftDelete, Update, UpdateCalendarDelegation, UpdateFolderPermissions, UpdateInboxRules",
+ "References": "https://learn.microsoft.com/en-us/purview/audit-mailboxes?view=o365-worldwide"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "exchange_user_mailbox_auditing_enabled",
+ "ConfigKey": "audit_log_age",
+ "Operator": "gte",
+ "Value": 90
+ }
+ ]
+ },
+ {
+ "Id": "6.1.3",
+ "Description": "When configuring a user or computer account to bypass mailbox audit logging, the system will not record any access, or actions performed by the said user or computer account on any mailbox. Administratively this was introduced to reduce the volume of entries in the mailbox audit logs on trusted user or computer accounts. Ensure AuditBypassEnabled is not enabled on accounts without a written exception.",
+ "Checks": [
+ "exchange_mailbox_audit_bypass_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.1 Audit",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "When configuring a user or computer account to bypass mailbox audit logging, the system will not record any access, or actions performed by the said user or computer account on any mailbox. Administratively this was introduced to reduce the volume of entries in the mailbox audit logs on trusted user or computer accounts. Ensure AuditBypassEnabled is not enabled on accounts without a written exception.",
+ "RationaleStatement": "If a mailbox audit bypass association is added for an account, the account can access any mailbox in the organization to which it has been assigned access permissions, without generating any mailbox audit logging entries for such access or recording any actions taken, such as message deletions. Enabling this parameter, whether intentionally or unintentionally, could allow insiders or malicious actors to conceal their activity on specific mailboxes. Ensuring proper logging of user actions and mailbox operations in the audit log will enable comprehensive incident response and forensics.",
+ "ImpactStatement": "None - this is the default behavior.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. The following example PowerShell script will disable AuditBypass for all mailboxes which currently have it enabled: # Get mailboxes with AuditBypassEnabled set to $true $MBXAudit = Get-MailboxAuditBypassAssociation -ResultSize unlimited | Where- Object { $_.AuditBypassEnabled -eq $true } foreach ($mailbox in $MBXAudit) { $mailboxName = $mailbox.Name Set-MailboxAuditBypassAssociation -Identity $mailboxName - AuditBypassEnabled $false Write-Host \"Audit Bypass disabled for mailbox Identity: $mailboxName\" - ForegroundColor Green }",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: $MBXData = Get-MailboxAuditBypassAssociation -ResultSize unlimited $Report = $MBXData | ? {$_.AuditBypassEnabled -eq $true} | select Name,AuditBypassEnabled $Report <# Optional: Export methods $Report | Out-GridView -Title \"Mailbox Audit Bypass Association\" $Report | Export-Csv -Path \"6.1.3.csv\" -NoTypeInformation #> 3. If nothing is returned, then there are no accounts with Audit Bypass enabled. Note: The cmdlet Get-MailboxAuditBypassAssociation may display a WARNING on system objects that begin with \"Asc-2X1\", this is not part of the Audit procedure and can be ignored.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AuditBypassEnabled False",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/exchange/get-mailboxauditbypassassociation?view=exchange-ps"
+ }
+ ]
+ },
+ {
+ "Id": "6.2.1",
+ "Description": "Exchange Online offers several methods of managing the flow of email messages. These are Remote domain, Transport Rules, and Anti-spam outbound policies. These methods work together to provide comprehensive coverage for potential automatic forwarding channels: - Outlook forwarding using inbox rules. - Outlook forwarding configured using OOF rule. - OWA forwarding setting (ForwardingSmtpAddress). - Forwarding set by the admin using EAC (ForwardingAddress). - Forwarding using Power Automate / Flow. Ensure a Transport rule and Anti-spam outbound policy are used to block mail forwarding. NOTE: Any exclusions should be implemented based on organizational policy.",
+ "Checks": [
+ "exchange_transport_rules_mail_forwarding_disabled",
+ "defender_antispam_outbound_policy_forwarding_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.2 Mail flow",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Exchange Online offers several methods of managing the flow of email messages. These are Remote domain, Transport Rules, and Anti-spam outbound policies. These methods work together to provide comprehensive coverage for potential automatic forwarding channels: - Outlook forwarding using inbox rules. - Outlook forwarding configured using OOF rule. - OWA forwarding setting (ForwardingSmtpAddress). - Forwarding set by the admin using EAC (ForwardingAddress). - Forwarding using Power Automate / Flow. Ensure a Transport rule and Anti-spam outbound policy are used to block mail forwarding. NOTE: Any exclusions should be implemented based on organizational policy.",
+ "RationaleStatement": "Attackers often create these rules to exfiltrate data from your tenancy, this could be accomplished via access to an end-user account or otherwise. An insider could also use one of these methods as a secondary channel to exfiltrate sensitive data.",
+ "ImpactStatement": "Care should be taken before implementation to ensure there is no business need for case-by-case auto-forwarding. Disabling auto-forwarding to remote domains will affect all users in an organization. Any exclusions should be implemented based on organizational policy.",
+ "RemediationProcedure": "Note: Remediation is a two step procedure as follows: STEP 1: Transport rules To remediate using the UI: 1. Select Exchange to open the Exchange admin center. 2. Select Mail Flow then Rules. 3. For each rule that redirects email to external domains, select the rule and click the 'Delete' icon. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Remove-TransportRule {RuleName} STEP 2: Anti-spam outbound policy To remediate using the UI: 1. Navigate to Microsoft 365 Defender https://security.microsoft.com/ 2. Expand E-mail & collaboration then select Policies & rules. 3. Select Threat policies > Anti-spam. 4. Select Anti-spam outbound policy (default) 5. Click Edit protection settings 6. Set Automatic forwarding rules dropdown to Off - Forwarding is disabled and click Save 7. Repeat steps 4-6 for any additional higher priority, custom policies. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-HostedOutboundSpamFilterPolicy -Identity {policyName} -AutoForwardingMode Off 3. To remove AutoForwarding from all outbound policies you can also run: Get-HostedOutboundSpamFilterPolicy | Set-HostedOutboundSpamFilterPolicy - AutoForwardingMode Off",
+ "AuditProcedure": "Note: Audit is a two step procedure as follows: STEP 1: Transport rules To audit using the UI: 1. Select Exchange to open the Exchange admin center. 2. Select Mail Flow then Rules. 3. Review the rules and verify that none of them are forwards or redirects e-mail to external domains. To audit using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. Run the following PowerShell command to review the Transport Rules that are redirecting email: Get-TransportRule | Where-Object {$_.RedirectMessageTo -ne $null} | ft Name,RedirectMessageTo 3. Verify that none of the addresses listed belong to external domains outside of the organization. If nothing returns then there are no transport rules set to redirect messages. STEP 2: Anti-spam outbound policy To audit using the UI: 1. Navigate to Microsoft 365 Defender https://security.microsoft.com/ 2. Expand E-mail & collaboration then select Policies & rules. 3. Select Threat policies > Anti-spam. 4. Inspect Anti-spam outbound policy (default) and ensure Automatic forwarding is set to Off - Forwarding is disabled 5. Inspect any additional custom outbound policies and ensure Automatic forwarding is set to Off - Forwarding is disabled, in accordance with the organization's exclusion policies. To audit using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. Run the following PowerShell cmdlet: Get-HostedOutboundSpamFilterPolicy | ft Name, AutoForwardingMode 3. In each outbound policy verify AutoForwardingMode is Off. Note: According to Microsoft if a recipient is defined in multiple policies of the same type (anti-spam, anti-phishing, etc.), only the policy with the highest priority is applied to the recipient. Any remaining policies of that type are not evaluated for the recipient (including the default policy). However, it is our recommendation to audit the default policy as well in the case a higher priority custom policy is removed. This will keep the organization's security posture strong.",
+ "AdditionalInformation": "",
+ "DefaultValue": "",
+ "References": "https://learn.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules:https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888#:~:text=%20%20%20Automatic%20forwarding%20option%20%20,%:https://learn.microsoft.com/en-us/defender-office-365/outbound-spam-policies-external-email-forwarding?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "6.2.2",
+ "Description": "Mail flow rules (transport rules) in Exchange Online can be configured to set the spam confidence level (SCL) of a message to -1, which bypasses spam and phishing filtering. When a rule applies this action to messages based on the sender's domain, all mail from that domain is treated as trusted and skips anti-malware and anti-phishing evaluation regardless of message content.",
+ "Checks": [
+ "exchange_transport_rules_whitelist_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.2 Mail flow",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Mail flow rules (transport rules) in Exchange Online can be configured to set the spam confidence level (SCL) of a message to -1, which bypasses spam and phishing filtering. When a rule applies this action to messages based on the sender's domain, all mail from that domain is treated as trusted and skips anti-malware and anti-phishing evaluation regardless of message content.",
+ "RationaleStatement": "Whitelisting domains in transport rules bypasses regular malware and phishing scanning, which can enable an attacker to launch attacks against your users from a safe haven domain. Note: If an organization identifies a business need for an exception, the domain should only be whitelisted if inbound emails from that domain originate from a specific IP address. These exceptions should be documented and regularly reviewed.",
+ "ImpactStatement": "Removing SCL bypass rules will subject previously whitelisted domains to standard spam and phishing filtering. Mail from those domains that does not pass filtering may be quarantined or rejected, which could disrupt established business communications. Prior to removal, identify any rules in scope and coordinate with affected business owners. If a legitimate need exists, consider replacing domain-based whitelisting with approved sender lists at the connection level.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com 2. Click to expand Mail Flow and then select Rules. 3. For each rule that sets the spam confidence level to -1 for a specific domain, select the rule and click Delete. To remediate using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. To remove a specific non-compliant rule: Remove-TransportRule -Identity \"RuleName\" Note: If the rule serves a legitimate purpose beyond domain whitelisting, consider modifying it to remove the SenderDomainIs condition or the SetSCL -1 action rather than deleting it entirely.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com 2. Click to expand Mail Flow and then select Rules. 3. Review each rule and ensure that a single rule does not contain both of these properties together: o Under Apply this rule if: Sender's address domain portion belongs to any of these domains: '<domain>' o Under Do the following: Set the spam confidence level (SCL) to '-1' Note: Setting the spam confidence level to -1 indicates the message is from a trusted sender, so the message bypasses spam filtering. The recommendation fails if any external domain has a SCL of -1. To audit using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-TransportRule | Where-Object { $_.setscl -eq -1 -and $_.SenderDomainIs - ne $null } | ft Name,SenderDomainIs,SetSCL 3. Transport rules that fail the audit will be shown. If no output is shown, the recommendation passes. To pass, all rules with SetSCL set to -1 must not include any domains in the SenderDomainIs property.",
+ "AdditionalInformation": "",
+ "DefaultValue": "No mail flow rules that set the SCL to -1 based on sender domain exist by default.",
+ "References": "https://learn.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/configuration-best-practices:https://learn.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules"
+ }
+ ]
+ },
+ {
+ "Id": "6.2.3",
+ "Description": "External callouts provide a native experience to identify emails from senders outside the organization. This is achieved by presenting a new tag on emails called \"External\" (the string is localized based on the client language setting) and exposing related user interface at the top of the message reading view to see and verify the real sender's email address. The recommended state is ExternalInOutlook set to Enabled True",
+ "Checks": [
+ "exchange_external_email_tagging_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.2 Mail flow",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "External callouts provide a native experience to identify emails from senders outside the organization. This is achieved by presenting a new tag on emails called \"External\" (the string is localized based on the client language setting) and exposing related user interface at the top of the message reading view to see and verify the real sender's email address. The recommended state is ExternalInOutlook set to Enabled True",
+ "RationaleStatement": "Tagging emails from external senders helps to inform end users about the origin of the email. This can allow them to proceed with more caution and make informed decisions when it comes to identifying spam or phishing emails. Mail flow rules are often used by Exchange administrators to accomplish the External email tagging by appending a tag to the front of a subject line. There are limitations to this outlined here. The preferred method in the CIS Benchmark is to use the native experience. Note: Existing emails in a user's inbox from external senders are not tagged retroactively.",
+ "ImpactStatement": "Mail flow rules using external tagging must be disabled, along with third-party mail filtering tools that offer similar features, to avoid duplicate [External] tags. External tags can consume additional screen space on systems with limited real estate, such as thin clients or mobile devices. After enabling this feature via PowerShell, it may take 24-48 hours for users to see the External sender tag in emails from outside your organization. Rolling back the feature takes the same amount of time. Note: Third-party tools that provide similar functionality will also meet compliance requirements, although Microsoft recommends using the native experience for better interoperability.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-ExternalInOutlook -Enabled $true",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-ExternalInOutlook 3. For each identity verify Enabled is set to True and the AllowList only contains email addresses the organization has permitted to bypass external tagging.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled (False)",
+ "References": "https://techcommunity.microsoft.com/t5/exchange-team-blog/native-external-sender-callouts-on-email-in-outlook/ba-p/2250098:https://learn.microsoft.com/en-us/powershell/module/exchange/set-externalinoutlook?view=exchange-ps"
+ }
+ ]
+ },
+ {
+ "Id": "6.3.1",
+ "Description": "Role assignment policies in Exchange Online control whether users can install and manage add-ins for Outlook. Three management roles govern this capability: My Custom Apps allows users to sideload custom add-ins, My Marketplace Apps allows users to install add-ins from the marketplace, and My ReadWriteMailbox Apps allows users to install add-ins that request read/write mailbox permissions. When these roles are assigned to a user's role assignment policy, users can self-install add-ins in both Outlook desktop and Outlook on the web, granting those add-ins access to mailbox data. This recommendation applies to the default role assignment policy, which is automatically assigned to new mailboxes unless a custom policy is specified.",
+ "Checks": [
+ "exchange_roles_assignment_policy_addins_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.3 Roles",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Role assignment policies in Exchange Online control whether users can install and manage add-ins for Outlook. Three management roles govern this capability: My Custom Apps allows users to sideload custom add-ins, My Marketplace Apps allows users to install add-ins from the marketplace, and My ReadWriteMailbox Apps allows users to install add-ins that request read/write mailbox permissions. When these roles are assigned to a user's role assignment policy, users can self-install add-ins in both Outlook desktop and Outlook on the web, granting those add-ins access to mailbox data. This recommendation applies to the default role assignment policy, which is automatically assigned to new mailboxes unless a custom policy is specified.",
+ "RationaleStatement": "Attackers exploit vulnerable or malicious add-ins to read, exfiltrate, or modify mailbox content including email, calendar items, and contacts. Restricting user-installed add-ins reduces this attack surface and centralizes add-in approval with administrators.",
+ "ImpactStatement": "End users will be unable to self-install third-party Outlook add-ins. Administrators may receive requests to evaluate and deploy add-ins on behalf of users. Organizations that rely on user-deployed add-ins for business workflows should inventory those add-ins and deploy them centrally via Centralized Deployment before implementing this recommendation.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com. 2. Click to expand Roles and select User roles. 3. Select Default Role Assignment Policy. 4. In the properties pane on the right click on Manage permissions. 5. Under Other roles uncheck any non-compliant roles: My Custom Apps, My Marketplace Apps, and My ReadWriteMailbox Apps. 6. Click Save changes. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following script: $TargetRoles = @( \"My Custom Apps\", \"My Marketplace Apps\", \"My ReadWriteMailbox Apps\" ) $DefaultPolicy = Get-RoleAssignmentPolicy | Where-Object { $_.IsDefault -eq $true } $Assignments = Get-ManagementRoleAssignment -RoleAssignee $DefaultPolicy.Identity | Where-Object { $_.Role -in $TargetRoles } foreach ($Assignment in $Assignments) { Remove-ManagementRoleAssignment -Identity $Assignment.Identity - Confirm:$false }",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com. 2. Expand Roles and select User roles. 3. Select Default Role Assignment Policy. 4. In the properties pane on the right click on Manage permissions. 5. Under Other roles verify that My Custom Apps, My Marketplace Apps, and My ReadWriteMailbox Apps are not checked. Note: As of this release of the Benchmark the manage permissions link no longer displays anything when a user assigned the Global Reader role clicks on it. As an alternative, users assigned the Global Reader directory role can inspect the Roles column or use the PowerShell method to perform the audit. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following script: $RoleList = @( \"My Custom Apps\", \"My Marketplace Apps\", \"My ReadWriteMailbox Apps\" ) $DefaultPolicy = Get-RoleAssignmentPolicy | Where-Object { $_.IsDefault -eq $true } $NonCompliantRoles = $DefaultPolicy.AssignedRoles | Where-Object { $_ -in $RoleList } Write-Host \"Checking Default Role Assignment Policy: $($DefaultPolicy.Name)\" if ($NonCompliantRoles) { \"Non-compliant - the following roles are assigned: \" + ($NonCompliantRoles -join \", \") } else { \"Compliant - no add-in roles are assigned to the default policy.\" } 3. Verify that the output indicates compliance. If My Custom Apps, My Marketplace Apps, or My ReadWriteMailbox Apps are listed, the default policy is non-compliant.",
+ "AdditionalInformation": "",
+ "DefaultValue": "UI - My Custom Apps, My Marketplace Apps, and My ReadWriteMailbox Apps are checked. PowerShell - My Custom Apps, My Marketplace Apps, and My ReadWriteMailbox Apps are assigned.",
+ "References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/add-ins-for-outlook/specify-who-can-install-and-manage-add-ins?source=recommendations:https://learn.microsoft.com/en-us/exchange/permissions-exo/role-assignment-policies"
+ }
+ ]
+ },
+ {
+ "Id": "6.3.2",
+ "Description": "Outlook on the web (OWA) mailbox policies include two settings that control personal account integration in Outlook. PersonalAccountsEnabled controls whether users can add personal email accounts (e.g., Outlook.com, Gmail, Yahoo) in the new Outlook for Windows. PersonalAccountCalendarsEnabled controls whether users can connect personal Outlook.com or Google calendars in Outlook on the web. Neither setting applies to classic Outlook for Windows, Outlook for Mac, or Outlook mobile apps. The recommended state for the default OWA Mailbox Policy is: - PersonalAccountsEnabled is set to False - PersonalAccountCalendarsEnabled is set to False",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.3 Roles",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Outlook on the web (OWA) mailbox policies include two settings that control personal account integration in Outlook. PersonalAccountsEnabled controls whether users can add personal email accounts (e.g., Outlook.com, Gmail, Yahoo) in the new Outlook for Windows. PersonalAccountCalendarsEnabled controls whether users can connect personal Outlook.com or Google calendars in Outlook on the web. Neither setting applies to classic Outlook for Windows, Outlook for Mac, or Outlook mobile apps. The recommended state for the default OWA Mailbox Policy is: - PersonalAccountsEnabled is set to False - PersonalAccountCalendarsEnabled is set to False",
+ "RationaleStatement": "Personal email accounts are not subject to corporate security controls such as anti- malware scanning, data loss prevention (DLP), Safe Links, or audit logging. Allowing personal accounts alongside the corporate mailbox enables side-channel data exfiltration (e.g., forwarding sensitive content to a personal inbox) and creates an ingress path for malware and phishing payloads that bypass tenant mail-flow protections.",
+ "ImpactStatement": "This control does not apply to classic Outlook for Windows, Outlook for Mac, or Outlook mobile apps. Organizations requiring broader coverage should evaluate additional controls like application management policies to restrict personal account usage on those clients. This also does not block users from accessing personal accounts via other email clients or web browsers. Changes to OWA mailbox policies may take up to 60 minutes to take effect. If users previously added personal accounts before this policy was applied, those accounts will be disabled once the policy is detected, and affected users will see a message advising them to remove the personal account from Outlook, which may generate helpdesk inquiries. The audit only applies to the default OWA mailbox policy. Users assigned to a non- default OWA mailbox policy are not covered; optionally, custom policies can be reviewed separately to ensure a level of enforcement beyond the compliance requirements of this control.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following: $DefaultPolicy = Get-OwaMailboxPolicy | Where-Object { $_.IsDefault } Set-OwaMailboxPolicy -Identity $DefaultPolicy.Identity - PersonalAccountsEnabled $false -PersonalAccountCalendarsEnabled $false",
+ "AuditProcedure": "Note: The default OWA Mailbox Policy is the only policy required for compliance with this control. Other mailbox policies are discretionary and left up to the organization to audit as needed. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following: Get-OwaMailboxPolicy | Where-Object { $_.IsDefault } | Format-List PersonalAccountsEnabled, PersonalAccountCalendarsEnabled 3. Verify the output matches the following: PersonalAccountsEnabled : False PersonalAccountCalendarsEnabled : False",
+ "AdditionalInformation": "",
+ "DefaultValue": "- PersonalAccountsEnabled is True. - PersonalAccountCalendarsEnabled is True.",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-owamailboxpolicy?view=exchange-ps#-personalaccountsenabled:https://learn.microsoft.com/en-us/microsoft-365-apps/outlook/get-started/supported-account-types#prevent-adding-personal-accounts:https://learn.microsoft.com/en-us/microsoft-365-apps/outlook/manage/policy-management"
+ }
+ ]
+ },
+ {
+ "Id": "6.5.1",
+ "Description": "Modern authentication in Microsoft 365 enables authentication features like multifactor authentication (MFA) using smart cards, certificate-based authentication (CBA), and third-party SAML identity providers. When you enable modern authentication in Exchange Online, Outlook 2016 and Outlook 2013 use modern authentication to log in to Microsoft 365 mailboxes. When you disable modern authentication in Exchange Online, Outlook 2016 and Outlook 2013 use basic authentication to log in to Microsoft 365 mailboxes. When users initially configure certain email clients, like Outlook 2013 and Outlook 2016, they may be required to authenticate using enhanced authentication mechanisms, such as multifactor authentication. Other Outlook clients that are available in Microsoft 365 (for example, Outlook Mobile and Outlook for Mac 2016) always use modern authentication to log in to Microsoft 365 mailboxes.",
+ "Checks": [
+ "exchange_organization_modern_authentication_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.5 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Modern authentication in Microsoft 365 enables authentication features like multifactor authentication (MFA) using smart cards, certificate-based authentication (CBA), and third-party SAML identity providers. When you enable modern authentication in Exchange Online, Outlook 2016 and Outlook 2013 use modern authentication to log in to Microsoft 365 mailboxes. When you disable modern authentication in Exchange Online, Outlook 2016 and Outlook 2013 use basic authentication to log in to Microsoft 365 mailboxes. When users initially configure certain email clients, like Outlook 2013 and Outlook 2016, they may be required to authenticate using enhanced authentication mechanisms, such as multifactor authentication. Other Outlook clients that are available in Microsoft 365 (for example, Outlook Mobile and Outlook for Mac 2016) always use modern authentication to log in to Microsoft 365 mailboxes.",
+ "RationaleStatement": "Strong authentication controls, such as the use of multifactor authentication, may be circumvented if basic authentication is used by Exchange Online email clients such as Outlook 2016 and Outlook 2013. Enabling modern authentication for Exchange Online ensures strong authentication mechanisms are used when establishing sessions between email clients and Exchange Online.",
+ "ImpactStatement": "Users of older email clients, such as Outlook 2013 and Outlook 2016, will no longer be able to authenticate to Exchange using Basic Authentication, which will necessitate migration to modern authentication practices.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings and select Org Settings. 3. Select Modern authentication. 4. Check Turn on modern authentication for Outlook 2013 for Windows and later (recommended) to enable modern authentication. To remediate using PowerShell: 1. Run the Microsoft Exchange Online PowerShell Module. 2. Connect to Exchange Online using Connect-ExchangeOnline. 3. Run the following PowerShell command: Set-OrganizationConfig -OAuth2ClientProfileEnabled $True",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft 365 admin center https://admin.microsoft.com. 2. Expand Settings and select Org Settings. 3. Select Modern authentication. 4. Verify that Turn on modern authentication for Outlook 2013 for Windows and later (recommended) is checked. To audit using PowerShell: 1. Run the Microsoft Exchange Online PowerShell Module. 2. Connect to Exchange Online using Connect-ExchangeOnline. 3. Run the following PowerShell command: Get-OrganizationConfig | Format-Table -Auto Name, OAuth* 4. Verify that OAuth2ClientProfileEnabled is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "True",
+ "References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online"
+ }
+ ]
+ },
+ {
+ "Id": "6.5.2",
+ "Description": "MailTips are informative messages displayed to users while they're composing a message. While a new message is open and being composed, Exchange analyzes the message (including recipients). If a potential problem is detected, the user is notified with a MailTip prior to sending the message. Using the information in the MailTip, the user can adjust the message to avoid undesirable situations or non-delivery reports (also known as NDRs or bounce messages).",
+ "Checks": [
+ "exchange_organization_mailtips_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.5 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "MailTips are informative messages displayed to users while they're composing a message. While a new message is open and being composed, Exchange analyzes the message (including recipients). If a potential problem is detected, the user is notified with a MailTip prior to sending the message. Using the information in the MailTip, the user can adjust the message to avoid undesirable situations or non-delivery reports (also known as NDRs or bounce messages).",
+ "RationaleStatement": "Setting up MailTips gives a visual aid to users when they send emails to large groups of recipients or send emails to recipients not within the tenant.",
+ "ImpactStatement": "Not applicable.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: $TipsParams = @{ MailTipsAllTipsEnabled = $true MailTipsExternalRecipientsTipsEnabled = $true MailTipsGroupMetricsEnabled = $true MailTipsLargeAudienceThreshold = '25' } Set-OrganizationConfig @TipsParams",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-OrganizationConfig | fl MailTips* 3. Verify the values for MailTipsAllTipsEnabled, MailTipsExternalRecipientsTipsEnabled, and MailTipsGroupMetricsEnabled are set to True and MailTipsLargeAudienceThreshold is set to an acceptable value; 25 is the default value.",
+ "AdditionalInformation": "",
+ "DefaultValue": "MailTipsAllTipsEnabled: True MailTipsExternalRecipientsTipsEnabled: False MailTipsGroupMetricsEnabled: True MailTipsLargeAudienceThreshold: 25",
+ "References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/mailtips/mailtips:https://learn.microsoft.com/en-us/powershell/module/exchange/set-organizationconfig?view=exchange-ps"
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "exchange_organization_mailtips_enabled",
+ "ConfigKey": "recommended_mailtips_large_audience_threshold",
+ "Operator": "lte",
+ "Value": 25
+ }
+ ]
+ },
+ {
+ "Id": "6.5.3",
+ "Description": "This setting allows users to open certain external files while working in Outlook on the web. If allowed, keep in mind that Microsoft doesn't control the use terms or privacy policies of those third-party services. Ensure AdditionalStorageProvidersAvailable is restricted on the default OWA policy.",
+ "Checks": [
+ "exchange_mailbox_policy_additional_storage_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.5 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting allows users to open certain external files while working in Outlook on the web. If allowed, keep in mind that Microsoft doesn't control the use terms or privacy policies of those third-party services. Ensure AdditionalStorageProvidersAvailable is restricted on the default OWA policy.",
+ "RationaleStatement": "By default, additional storage providers are allowed in Office on the Web (such as Box, Dropbox, Facebook, Google Drive, OneDrive Personal, etc.). This could lead to information leakage and additional risk of infection from organizational non-trusted storage providers. Restricting this will inherently reduce risk as it will narrow opportunities for infection and data leakage.",
+ "ImpactStatement": "The impact associated with this change is highly dependent upon current practices in the tenant. If users do not use other storage providers, then minimal impact is likely. However, if users do regularly utilize providers outside of the tenant this will affect their ability to continue to do so.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default - AdditionalStorageProvidersAvailable $false",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command to audit the default OWA policy: Get-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default | fl AdditionalStorageProvidersAvailable 3. Verify that AdditionalStorageProvidersAvailable is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AdditionalStorageProvidersAvailable : True",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/exchange/set-owamailboxpolicy?view=exchange-ps:https://support.microsoft.com/en-us/topic/3rd-party-cloud-storage-services-supported-by-office-apps-fce12782-eccc-4cf5-8f4b-d1ebec513f72"
+ }
+ ]
+ },
+ {
+ "Id": "6.5.4",
+ "Description": "This setting enables or disables authenticated client SMTP submission (SMTP AUTH) at an organization level in Exchange Online. The recommended state is Turn off SMTP AUTH protocol for your organization (checked).",
+ "Checks": [
+ "exchange_transport_config_smtp_auth_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.5 Settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting enables or disables authenticated client SMTP submission (SMTP AUTH) at an organization level in Exchange Online. The recommended state is Turn off SMTP AUTH protocol for your organization (checked).",
+ "RationaleStatement": "SMTP AUTH is a legacy protocol. Disabling it at the organization level supports the principle of least functionality and serves to further back additional controls that block legacy protocols, such as in Conditional Access. Virtually all modern email clients that connect to Exchange Online mailboxes in Microsoft 365 can do so without using SMTP AUTH.",
+ "ImpactStatement": "This enforces the default behavior, so no impact is expected unless the organization is using it globally. A per-mailbox setting exists that overrides the tenant-wide setting, allowing an individual mailbox SMTP AUTH capability for special cases.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com. 2. Expand Settings and select Mail flow. 3. Check Turn off SMTP AUTH protocol for your organization to disable the protocol. To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-TransportConfig -SmtpClientAuthenticationDisabled $true",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Exchange admin center https://admin.exchange.microsoft.com. 2. Expand Settings and select Mail flow. 3. Ensure Turn off SMTP AUTH protocol for your organization is checked. To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled 3. Verify that the value returned is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "SmtpClientAuthenticationDisabled : True",
+ "References": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission"
+ }
+ ]
+ },
+ {
+ "Id": "6.5.5",
+ "Description": "Direct Send is a method used to send emails directly to an Exchange Online customer's hosted mailboxes from on-premises devices, applications, or third-party cloud services using the customer's own accepted domain. This method does not require any form of authentication because, by its nature, it mimics incoming anonymous emails from the internet, apart from the sender domain. The recommended state is to configure RejectDirectSend to True.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "6 Exchange admin center",
+ "SubSection": "6.5 Settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Direct Send is a method used to send emails directly to an Exchange Online customer's hosted mailboxes from on-premises devices, applications, or third-party cloud services using the customer's own accepted domain. This method does not require any form of authentication because, by its nature, it mimics incoming anonymous emails from the internet, apart from the sender domain. The recommended state is to configure RejectDirectSend to True.",
+ "RationaleStatement": "Direct Send allows devices and applications to transmit unauthenticated email directly to Exchange Online. While this method may support legacy systems such as printers or scanners, it introduces significant security risks: - Unauthenticated Email Delivery: Direct Send does not require authentication, making it an attractive vector for threat actors to deliver spoofed or malicious emails that appear to originate from trusted internal sources. - Phishing and Spoofing Risks: Because these emails bypass standard authentication mechanisms, they can easily impersonate internal users or services, increasing the likelihood of successful phishing attacks. - Lack of Visibility and Control: Emails sent via Direct Send may not be subject to the same security policies, logging, or filtering as authenticated traffic, reducing the organization's ability to monitor and respond to threats effectively. Threat research from Varonis has shown that attackers are actively exploiting Direct Send to impersonate internal accounts and distribute malicious content without needing to compromise any credentials. These campaigns have successfully targeted organizations by leveraging predictable infrastructure and public user data to craft convincing phishing emails. Because these messages originate from outside the tenant but appear internal, they often evade detection and filtering mechanisms.",
+ "ImpactStatement": "Per Microsoft, there is a forwarding scenario that could be affected by this feature. It is possible that someone in your organization sends a message to a 3rd party and they in turn forward it to another mailbox in your organization. If the 3rd party's email provider does not support Sender Rewriting Scheme (SRS), the message will return with the original sender's address. Prior to this feature being enabled, those messages will already be punished by SPF failing but could still end up in inboxes. Enabling the Reject Direct Send feature without a partner mail flow connector being set up will lead to these messages being rejected outright.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Set-OrganizationConfig -RejectDirectSend $true",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to Exchange Online using Connect-ExchangeOnline. 2. Run the following PowerShell command: Get-OrganizationConfig | fl RejectDirectSend 3. Verify that the value returned for RejectDirectSend is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "RejectDirectSend : False",
+ "References": "https://techcommunity.microsoft.com/blog/exchange/introducing-more-control-over-direct-send-in-exchange-online/4408790?WT.mc_id=M365-MVP-9501:https://techcommunity.microsoft.com/blog/exchange/direct-send-vs-sending-directly-to-an-exchange-online-tenant/4439865:https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-organizationconfig?view=exchange-ps:https://www.varonis.com/blog/direct-send-exploit:https://techcommunity.microsoft.com/discussions/microsoft-365/disable-direct-send-in-exchange-online-to-mitigate-ongoing-phishing-threats/4434649"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.1",
+ "Description": "Modern authentication in Microsoft 365 enables authentication features like multifactor authentication (MFA) using smart cards, certificate-based authentication (CBA), and third-party SAML identity providers.",
+ "Checks": [
+ "sharepoint_modern_authentication_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Modern authentication in Microsoft 365 enables authentication features like multifactor authentication (MFA) using smart cards, certificate-based authentication (CBA), and third-party SAML identity providers.",
+ "RationaleStatement": "Strong authentication controls, such as the use of multifactor authentication, may be circumvented if basic authentication is used by SharePoint applications. Requiring modern authentication for SharePoint applications ensures strong authentication mechanisms are used when establishing sessions between these applications, SharePoint, and connecting users.",
+ "ImpactStatement": "Implementation of modern authentication for SharePoint will require users to authenticate to SharePoint using modern authentication. This may cause a minor impact to typical user behavior. This may also prevent third-party apps from accessing SharePoint Online resources. Also, this will also block apps using the SharePointOnlineCredentials class to access SharePoint Online resources.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint. 2. Expand Policies and select Access control. 3. Select Apps that don't use modern authentication. 4. Select the radio button for Block access. 5. Click Save. To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService -Url https://tenant-admin.sharepoint.com replacing tenant with your value. 2. Run the following SharePoint Online PowerShell command: Set-SPOTenant -LegacyAuthProtocolsEnabled $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint. 2. Expand Policies and select Access control. 3. Select Apps that don't use modern authentication and ensure that it is set to Block access. To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService -Url https://tenant-admin.sharepoint.com replacing tenant with your value. 2. Run the following SharePoint Online PowerShell command: Get-SPOTenant | ft LegacyAuthProtocolsEnabled 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "True (Apps that don't use modern authentication are allowed)",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.2",
+ "Description": "Entra ID B2B provides authentication and management of guests. Authentication happens via one-time passcode when they don't already have a work or school account or a Microsoft account. Integration with SharePoint and OneDrive allows for more granular control of how guest user accounts are managed in the organization's AAD, unifying a similar guest experience already deployed in other Microsoft 365 services such as Teams. Note: Global Reader role currently can't access SharePoint using PowerShell.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Entra ID B2B provides authentication and management of guests. Authentication happens via one-time passcode when they don't already have a work or school account or a Microsoft account. Integration with SharePoint and OneDrive allows for more granular control of how guest user accounts are managed in the organization's AAD, unifying a similar guest experience already deployed in other Microsoft 365 services such as Teams. Note: Global Reader role currently can't access SharePoint using PowerShell.",
+ "RationaleStatement": "External users assigned guest accounts will be subject to Entra ID access policies, such as multi-factor authentication. This provides a way to manage guest identities and control access to SharePoint and OneDrive resources. Without this integration, files can be shared without account registration, making it more challenging to audit and manage who has access to the organization's data.",
+ "ImpactStatement": "After enabling Microsoft Entra B2B integration, external users attempting to access previously shared links (One Time Passcode) will encounter access issues. They receive error 'This organization has updated its guest access settings'. To restore access, your users need to reshare files/folders/sites to external users.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService 2. Run the following command: Set-SPOTenant -EnableAzureADB2BIntegration $true",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService 2. Run the following command: Get-SPOTenant | ft EnableAzureADB2BIntegration 3. Verify that the returned value is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "False",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/sharepoint-azureb2b-integration#enabling-the-integration:https://learn.microsoft.com/en-us/entra/external-id/what-is-b2b:https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.3",
+ "Description": "The external sharing settings govern sharing for the organization overall. Each site has its own sharing setting that can be set independently, though it must be at the same or more restrictive setting as the organization. The new and existing guests option requires people who have received invitations to sign in with their work or school account (if their organization uses Microsoft 365) or a Microsoft account, or to provide a code to verify their identity. Users can share with guests already in your organization's directory, and they can send invitations to people who will be added to the directory if they sign in. The recommended state is New and existing guests or less permissive.",
+ "Checks": [
+ "sharepoint_external_sharing_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "The external sharing settings govern sharing for the organization overall. Each site has its own sharing setting that can be set independently, though it must be at the same or more restrictive setting as the organization. The new and existing guests option requires people who have received invitations to sign in with their work or school account (if their organization uses Microsoft 365) or a Microsoft account, or to provide a code to verify their identity. Users can share with guests already in your organization's directory, and they can send invitations to people who will be added to the directory if they sign in. The recommended state is New and existing guests or less permissive.",
+ "RationaleStatement": "Forcing guest authentication on the organization's tenant enables the implementation of controls and oversight over external file sharing. When a guest is registered with the organization, they now have an identity which can be accounted for. This identity can also have other restrictions applied to it through group membership and conditional access rules.",
+ "ImpactStatement": "When using B2B integration, Entra ID external collaboration settings, such as guest invite settings and collaboration restrictions apply.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. Under SharePoint, move the slider bar to New and existing guests or a less permissive level. o OneDrive will also be moved to the same level and can never be more permissive than SharePoint. To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet to establish the minimum recommended state: Set-SPOTenant -SharingCapability ExternalUserSharingOnly Note: Other acceptable values for this parameter that are more restrictive include: Disabled and ExistingExternalUserSharingOnly.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. Under SharePoint, verify that the slider bar is set to New and existing guests or a less permissive level. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Get-SPOTenant | fl SharingCapability 3. Verify that SharingCapability is set to one of the following values: o ExternalUserSharingOnly o ExistingExternalUserSharingOnly o Disabled",
+ "AdditionalInformation": "",
+ "DefaultValue": "Anyone (ExternalUserAndGuestSharing)",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off:https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.4",
+ "Description": "This setting governs the global permissiveness of OneDrive content sharing in the organization. OneDrive content sharing can be restricted independent of SharePoint but can never be more permissive than the level established with SharePoint. The recommended state is Only people in your organization.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting governs the global permissiveness of OneDrive content sharing in the organization. OneDrive content sharing can be restricted independent of SharePoint but can never be more permissive than the level established with SharePoint. The recommended state is Only people in your organization.",
+ "RationaleStatement": "OneDrive, designed for end-user cloud storage, inherently provides less oversight and control compared to SharePoint, which often involves additional content overseers or site administrators. This autonomy can lead to potential risks such as inadvertent sharing of privileged information by end users. Restricting external OneDrive sharing will require users to transfer content to SharePoint folders first which have those tighter controls.",
+ "ImpactStatement": "Users will be required to take additional steps to share OneDrive content or use other official channels.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. Under OneDrive, set the slider bar to Only people in your organization. To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Set-SPOTenant -OneDriveSharingCapability Disabled Alternative remediation method using PowerShell: 1. Connect to SharePoint Online. 2. Run one of the following: # Replace [tenant] with your tenant id Set-SPOSite -Identity https://[tenant]-my.sharepoint.com/ -SharingCapability Disabled # Or run this to filter to the specific site without supplying the tenant name. $OneDriveSite = Get-SPOSite -Filter { Url -like \"*-my.sharepoint.com/\" } Set-SPOSite -Identity $OneDriveSite -SharingCapability Disabled",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. Under OneDrive, verify that the slider bar is set to Only people in your organization. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Get-SPOTenant | fl OneDriveSharingCapability 3. Verify that the returned value is Disabled. Alternative audit method using PowerShell: 1. Connect to SharePoint Online. 2. Use one of the following methods: # Replace [tenant] with your tenant id Get-SPOSite -Identity https://[tenant]-my.sharepoint.com/ | fl Url,SharingCapability # Or run this to filter to the specific site without supplying the tenant name. $OneDriveSite = Get-SPOSite -Filter { Url -like \"*-my.sharepoint.com/\" } Get-SPOSite -Identity $OneDriveSite | fl Url,SharingCapability 2. Verify that the returned value for SharingCapability is Disabled Note: As of March 2024, using Get-SPOSite with Where-Object or filtering against the entire site and then returning the SharingCapability parameter can result in a different value as opposed to running the cmdlet specifically against the OneDrive specific site using the -Identity switch as shown in the example. Note 2: The parameter OneDriveSharingCapability may not be yet fully available in all tenants. It is demonstrated in official Microsoft documentation as linked in the references section but not in the Set-SPOTenant cmdlet itself. If the parameter is unavailable, then either use the UI method or alternative PowerShell audit method.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Anyone (ExternalUserAndGuestSharing)",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-onedrivesharingcapability"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.5",
+ "Description": "SharePoint gives users the ability to share files, folders, and site collections. Internal users can share with external collaborators, and with the right permissions could share to other external parties.",
+ "Checks": [
+ "sharepoint_guest_sharing_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "SharePoint gives users the ability to share files, folders, and site collections. Internal users can share with external collaborators, and with the right permissions could share to other external parties.",
+ "RationaleStatement": "Sharing and collaboration are key; however, file, folder, or site collection owners should have the authority over what external users get shared with to prevent unauthorized disclosures of information.",
+ "ImpactStatement": "The impact associated with this change is highly dependent upon current practices. If users do not regularly share with external parties, then minimal impact is likely. However, if users do regularly share with guests/externally, minimum impacts could occur as those external users will be unable to 're-share' content.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Expand More external sharing settings, uncheck Allow guests to share items they don't own. 4. Click Save. To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following SharePoint Online PowerShell command: Set-SPOTenant -PreventExternalUsersFromResharing $True",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Expand More external sharing settings, verify that Allow guests to share items they don't own is unchecked. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following SharePoint Online PowerShell command: Get-SPOTenant | ft PreventExternalUsersFromResharing 3. Verify that the returned value is True.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Checked (False)",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off:https://learn.microsoft.com/en-us/sharepoint/external-sharing-overview"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.6",
+ "Description": "The external sharing features of SharePoint and OneDrive let users in the organization share content with people outside the organization (such as partners, vendors, clients, or customers). It can also be used to share between licensed users on multiple Microsoft 365 subscriptions if your organization has more than one subscription. The recommended state is Limit external sharing by domain > Allow only specific domains",
+ "Checks": [
+ "sharepoint_external_sharing_managed"
+ ],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "The external sharing features of SharePoint and OneDrive let users in the organization share content with people outside the organization (such as partners, vendors, clients, or customers). It can also be used to share between licensed users on multiple Microsoft 365 subscriptions if your organization has more than one subscription. The recommended state is Limit external sharing by domain > Allow only specific domains",
+ "RationaleStatement": "Attackers will often attempt to expose sensitive information to external entities through sharing, and restricting the domains that users can share documents with will reduce that surface area.",
+ "ImpactStatement": "Users will be unable to initiate new shares with parties whose domains are not on the approved allowlist, which may require administrative action before collaboration with new partners or vendors can begin. Administrators must keep the allowlist current to reflect active business relationships; an outdated list can block legitimate sharing and generate support requests. Note that existing shares to domains not on the allowlist are not revoked when this setting is configured.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint. 2. Expand Policies > Sharing. 3. Expand More external sharing settings and check Limit external sharing by domain. 4. Select Add domains, choose Allow only specific domains, enter the list of approved domain names, and select Done. 5. Click Save at the bottom of the page. To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run the following PowerShell command: Set-SPOTenant -SharingDomainRestrictionMode AllowList - SharingAllowedDomainList \"domain1.com domain2.com\"",
+ "AuditProcedure": "Note: If the SharePoint external sharing slider is set to Only people in your organization, this recommendation is compliant regardless of the configured value for Limit external sharing by domain. To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. If the SharePoint slider is set to Only people in your organization, this recommendation is compliant. 5. Otherwise, expand More external sharing settings and confirm that Limit external sharing by domain is checked. 6. Verify that Allow only specific domains is selected and that domains listed are approved by the organization. To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run the following PowerShell command: Get-SPOTenant | fl SharingCapability,SharingDomainRestrictionMode,SharingAllowedDomainList 3. Verify that one of the following conditions is true: o SharingCapability is Disabled, OR o SharingDomainRestrictionMode is AllowList and SharingAllowedDomainList contains domains trusted by the organization for external sharing.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Limit external sharing by domain is unchecked SharingDomainRestrictionMode: None SharingAllowedDomainList: (empty)",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off?WT.mc_id=365AdminCSH_spo#more-external-sharing-settings"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.7",
+ "Description": "This setting sets the default link type that a user will see when sharing content in OneDrive or SharePoint. It does not restrict or exclude any other options. The recommended state is Specific people (only the people the user specifies) or Only people in your organization.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting sets the default link type that a user will see when sharing content in OneDrive or SharePoint. It does not restrict or exclude any other options. The recommended state is Specific people (only the people the user specifies) or Only people in your organization.",
+ "RationaleStatement": "By defaulting to specific people, the user will first need to consider whether or not the content being shared should be accessible by the entire organization versus select individuals. This aids in reinforcing the concept of least privilege.",
+ "ImpactStatement": "Changing the default sharing link type influences the user experience when sharing files and folders in SharePoint and OneDrive. The configured default option will appear pre- selected in the sharing dialog, guiding users toward the organization's preferred sharing method.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to File and folder links. 4. Set Choose the type of link that's selected by default when users share files and folders in SharePoint and OneDrive to Specific people (only the people the user specifies) or Only people in your organization. To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run one of the following PowerShell commands depending on the desired compliant state: To set the default sharing link to specific people: Set-SPOTenant -DefaultSharingLinkType Direct To set the default sharing link to people in the organization: Set-SPOTenant -DefaultSharingLinkType Internal",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to File and folder links. 4. Verify that the setting Choose the type of link that's selected by default when users share files and folders in SharePoint and OneDrive is set to Specific people (only the people the user specifies) or Only people in your organization. To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run the following PowerShell command: Get-SPOTenant | fl DefaultSharingLinkType 3. Verify that the returned value is Direct or Internal.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Only people in your organization (Internal)",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.8",
+ "Description": "External sharing of content can be restricted to specific security groups. This setting is global, applies to sharing in both SharePoint and OneDrive and cannot be set at the site level in SharePoint.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "External sharing of content can be restricted to specific security groups. This setting is global, applies to sharing in both SharePoint and OneDrive and cannot be set at the site level in SharePoint.",
+ "RationaleStatement": "Without restricting external sharing to designated security groups, any user in the organization can share SharePoint or OneDrive content with external recipients. A compromised or insider-threat account can exfiltrate sensitive data by sharing files externally without additional authorization controls. Limiting external sharing to members of specific Entra ID security groups ensures that only reviewed and authorized users have this capability, reducing the attack surface for data exfiltration through sharing.",
+ "ImpactStatement": "Users who are not members of the designated security groups will lose the ability to create new external shares or invite new external guests. Existing sharing links they previously established will remain active for current recipients. Organizations should ensure the security groups are populated with appropriate members before enabling this setting to avoid inadvertently blocking all external sharing. Helpdesk volume may increase as users in non-designated groups encounter sharing restrictions.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to and expand More external sharing settings. 4. Set the following: o Check Allow only users in specific security groups to share externally o Click Manage security groups, then add at least one security group authorized for external sharing. To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run the following command, replacing <GroupObjectId> with the GUID of the security group to be authorized for external sharing: Set-SPOTenant -WhoCanShareAuthenticatedGuestAllowList \"<GroupObjectId>\" Note: To authorize multiple security groups, provide a comma-delimited list of Object IDs: \"<GroupObjectId1>\",\"<GroupObjectId2>\". Note: Users in the designated security groups must also be permitted to invite guests in Microsoft Entra. Verify this at Identity > External Identities > External collaboration settings.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Locate the External sharing section. 4. If the SharePoint slider is set to Only people in your organization, this recommendation is compliant. 5. Otherwise, scroll to and expand More external sharing settings. 6. Verify the following: o Allow only users in specific security groups to share externally is checked o Manage security groups contains at least one security group. To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService. 2. Run the following PowerShell command: Get-SPOTenant | fl SharingCapability, WhoCanShareAuthenticatedGuestAllowList 3. Verify the output using the following logic: o If SharingCapability is Disabled, the recommendation is compliant regardless of the value of WhoCanShareAuthenticatedGuestAllowList. o Otherwise, verify that WhoCanShareAuthenticatedGuestAllowList contains at least one security group GUID. If the value is empty or $null, the recommendation is not compliant.",
+ "AdditionalInformation": "",
+ "DefaultValue": "By default, this restriction is not in place, allowing any user in the organization to share content externally, subject only to the top-level sharing slider.",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/manage-security-groups:https://learn.microsoft.com/en-us/powershell/module/microsoft.online.sharepoint.powershell/set-spotenant?view=sharepoint-ps"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.9",
+ "Description": "This policy setting configures the expiration time for each guest that is invited to the SharePoint site or with whom users share individual files and folders with. Expiration can be a number 30 to 730. The recommended state is 30.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting configures the expiration time for each guest that is invited to the SharePoint site or with whom users share individual files and folders with. Expiration can be a number 30 to 730. The recommended state is 30.",
+ "RationaleStatement": "This setting ensures that guests who no longer need access to the site or link no longer have access after a set period of time. Allowing guest access for an indefinite amount of time could lead to loss of data confidentiality and oversight. Note: Guest membership applies at the Microsoft 365 group level. Guests who have permission to view a SharePoint site or use a sharing link may also have access to a Microsoft Teams team or security group.",
+ "ImpactStatement": "Site collection administrators will have to renew access to guests who still need access after 30 days. They will receive an e-mail notification once per week about guest access that is about to expire. Note: The guest expiration policy only applies to guests who use sharing links or guests who have direct permissions to a SharePoint site after the guest policy is enabled. The guest policy does not apply to guest users that have pre-existing permissions or access through a sharing link before the guest expiration policy is applied.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to and expand More external sharing settings. 4. Set Guest access to a site or OneDrive will expire automatically after this many days to 30 To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Set-SPOTenant -ExternalUserExpireInDays 30 -ExternalUserExpirationRequired $True",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to and expand More external sharing settings. 4. Verify that Guest access to a site or OneDrive will expire automatically after this many days is checked and set to 30. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Get-SPOTenant | fl ExternalUserExpirationRequired,ExternalUserExpireInDays 3. Verify the following values are returned: o ExternalUserExpirationRequired is True. o ExternalUserExpireInDays is 30.",
+ "AdditionalInformation": "",
+ "DefaultValue": "ExternalUserExpirationRequired $false ExternalUserExpireInDays 60 days",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off#change-the-organization-level-external-sharing-setting:https://learn.microsoft.com/en-us/microsoft-365/community/sharepoint-security-a-team-effort"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.10",
+ "Description": "This setting configures if guests who use a verification code to access the site or links are required to reauthenticate after a set number of days. The recommended state is 15 or less.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting configures if guests who use a verification code to access the site or links are required to reauthenticate after a set number of days. The recommended state is 15 or less.",
+ "RationaleStatement": "By increasing the frequency of times guests need to reauthenticate this ensures guest user access to data is not prolonged beyond an acceptable amount of time.",
+ "ImpactStatement": "Guests who use Microsoft 365 in their organization can sign in using their work or school account to access the site or document. After the one-time passcode for verification has been entered for the first time, guests will authenticate with their work or school account and have a guest account created in the host's organization. Note: If OneDrive and SharePoint integration with Entra ID B2B is enabled as per the CIS Benchmark the one-time-passcode experience will be replaced. Please visit Secure external sharing in SharePoint - SharePoint in Microsoft 365 | Microsoft Learn for more information.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to and expand More external sharing settings. 4. Set People who use a verification code must reauthenticate after this many days to 15 or less. To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Set-SPOTenant -EmailAttestationRequired $true -EmailAttestationReAuthDays 15",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to and expand More external sharing settings. 4. Verify that People who use a verification code must reauthenticate after this many days is set to 15 or less. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Get-SPOTenant | fl EmailAttestationRequired,EmailAttestationReAuthDays 3. Verify that the following values are returned: o EmailAttestationRequired True o EmailAttestationReAuthDays 15 or less days.",
+ "AdditionalInformation": "",
+ "DefaultValue": "EmailAttestationRequired : False EmailAttestationReAuthDays : 30",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/what-s-new-in-sharing-in-targeted-release:https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off#change-the-organization-level-external-sharing-setting:https://learn.microsoft.com/en-us/entra/external-id/one-time-passcode"
+ }
+ ]
+ },
+ {
+ "Id": "7.2.11",
+ "Description": "This setting configures the permission that is selected by default for sharing link from a SharePoint site. The recommended state is View.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.2 Policies",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting configures the permission that is selected by default for sharing link from a SharePoint site. The recommended state is View.",
+ "RationaleStatement": "Setting the view permission as the default ensures that users must deliberately select the edit permission when sharing a link. This approach reduces the risk of unintentionally granting edit privileges to a resource that only requires read access, supporting the principle of least privilege.",
+ "ImpactStatement": "Not applicable.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to File and folder links. 4. Set Choose the permission that's selected by default for sharing links to View. To remediate using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Set-SPOTenant -DefaultLinkPermission View",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to SharePoint admin center https://admin.microsoft.com/sharepoint 2. Expand Policies > Sharing. 3. Scroll to File and folder links. 4. Verify that Choose the permission that's selected by default for sharing links is set to View. To audit using PowerShell: 1. Connect to SharePoint Online service using Connect-SPOService. 2. Run the following cmdlet: Get-SPOTenant | fl DefaultLinkPermission 3. Verify that the returned value is View.",
+ "AdditionalInformation": "",
+ "DefaultValue": "DefaultLinkPermission : Edit",
+ "References": "https://learn.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off#file-and-folder-links"
+ }
+ ]
+ },
+ {
+ "Id": "7.3.1",
+ "Description": "By default, SharePoint online allows files that Defender for Office 365 has detected as infected to be downloaded.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "7 SharePoint admin center",
+ "SubSection": "7.3 Settings",
+ "Profile": "E5 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "By default, SharePoint online allows files that Defender for Office 365 has detected as infected to be downloaded.",
+ "RationaleStatement": "Defender for Office 365 for SharePoint, OneDrive, and Microsoft Teams protects your organization from inadvertently sharing malicious files. When an infected file is detected that file is blocked so that no one can open, copy, move, or share it until further actions are taken by the organization's security team.",
+ "ImpactStatement": "The only potential impact associated with implementation of this setting is potential inconvenience associated with the small percentage of false positive detections that may occur.",
+ "RemediationProcedure": "To remediate using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService -Url https://tenant-admin.sharepoint.com, replacing \"tenant\" with the appropriate value. 2. Run the following PowerShell command to set the recommended value: Set-SPOTenant -DisallowInfectedFileDownload $true Note: The Global Reader role cannot access SharePoint using PowerShell according to Microsoft. See the reference section for more information.",
+ "AuditProcedure": "To audit using PowerShell: 1. Connect to SharePoint Online using Connect-SPOService -Url https://tenant-admin.sharepoint.com, replacing \"tenant\" with the appropriate value. 2. Run the following PowerShell command: Get-SPOTenant | Select-Object DisallowInfectedFileDownload 3. Ensure that the DisallowInfectedFileDownload is set to True. Note: According to Microsoft, SharePoint cannot be accessed through PowerShell by users with the Global Reader role. For further information, please refer to the reference section.",
+ "AdditionalInformation": "",
+ "DefaultValue": "False",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-for-spo-odfb-teams-configure?view=o365-worldwide:https://learn.microsoft.com/en-us/defender-office-365/anti-malware-protection-for-spo-odfb-teams-about?view=o365-worldwide:https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference#global-reader"
+ }
+ ]
+ },
+ {
+ "Id": "8.1.1",
+ "Description": "Microsoft Teams enables collaboration via file sharing. This file sharing is conducted within Teams, using SharePoint Online, by default; however, third-party cloud services are allowed as well. Note: Skype for business is deprecated as of July 31, 2021 although these settings may still be valid for a period of time. See the link in the references section for more information.",
+ "Checks": [
+ "teams_external_file_sharing_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.1 Teams",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Microsoft Teams enables collaboration via file sharing. This file sharing is conducted within Teams, using SharePoint Online, by default; however, third-party cloud services are allowed as well. Note: Skype for business is deprecated as of July 31, 2021 although these settings may still be valid for a period of time. See the link in the references section for more information.",
+ "RationaleStatement": "Ensuring that only authorized cloud storage providers are accessible from Teams will help to dissuade the use of non-approved storage providers.",
+ "ImpactStatement": "The impact associated with this change is highly dependent upon current practices in the tenant. If users do not use other storage providers, then minimal impact is likely. However, if users do regularly utilize providers outside of the tenant this will affect their ability to continue to do so.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Select Settings & policies > Global (Org-wide default) settings. 3. Click Teams to open the Teams settings section. 4. Under files set storages providers to Off unless they have first been authorized by the organization. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following PowerShell command to disable external providers that are not authorized. (the example disables Citrix Files, DropBox, Box, Google Drive and Egnyte) $Params = @{ Identity = 'Global' AllowGoogleDrive = $false AllowShareFile = $false AllowBox = $false AllowDropBox = $false AllowEgnyte = $false } Set-CsTeamsClientConfiguration @Params",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Select Settings & policies > Global (Org-wide default) settings. 3. Click Teams to open the Teams settings section. 4. Under files verify that only organizationally authorized cloud storage options are set to On and all others Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following to verify the recommended state: $Params = @( 'AllowDropbox' 'AllowBox' 'AllowGoogleDrive' 'AllowShareFile' 'AllowEgnyte' ) Get-CsTeamsClientConfiguration -Identity Global | fl $Params 3. Verify that only authorized providers are set to True and all others False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "AllowDropBox : True AllowBox : True AllowGoogleDrive : True AllowShareFile : True AllowEgnyte : True",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/teams-powershell-managing-teams"
+ }
+ ]
+ },
+ {
+ "Id": "8.1.2",
+ "Description": "This setting controls whether Teams channels are allowed to receive emails sent to their unique email addresses. When enabled, emails sent to a channel's address will be delivered and appear in the channel's conversation thread; when disabled, the channel will reject incoming emails, preventing them from being posted. The recommended state is Off.",
+ "Checks": [
+ "teams_email_sending_to_channel_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.1 Teams",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting controls whether Teams channels are allowed to receive emails sent to their unique email addresses. When enabled, emails sent to a channel's address will be delivered and appear in the channel's conversation thread; when disabled, the channel will reject incoming emails, preventing them from being posted. The recommended state is Off.",
+ "RationaleStatement": "Channel email addresses are not under the tenant's domain and organizations do not have control over the security settings for this email address. An attacker could email channels directly if they discover the channel email address.",
+ "ImpactStatement": "Depending on the organization's adoption, disabling this may disrupt workflows that rely on email-to-channel communication, particularly in environments where email is used to bridge external systems or vendors into Teams. This could include reduced visibility of important updates or alerts that were previously routed into Teams channels via email.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Select Settings & policies > Global (Org-wide default) settings. 3. Click Teams to open the Teams settings section. 4. Under email integration set Users can send emails to a channel email address to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsClientConfiguration -Identity Global -AllowEmailIntoChannel $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Select Settings & policies > Global (Org-wide default) settings. 3. Click Teams to open the Teams settings section. 4. Under email integration verify that Users can send emails to a channel email address is Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsClientConfiguration -Identity Global | fl AllowEmailIntoChannel 3. Ensure the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On (True)",
+ "References": "https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/step-by-step-guides/reducing-attack-surface-in-microsoft-teams?view=o365-worldwide#restricting-channel-email-messages-to-approved-domains:https://learn.microsoft.com/en-us/microsoftteams/settings-policies-reference#email-integration:https://support.microsoft.com/en-us/office/send-an-email-to-a-channel-in-microsoft-teams-d91db004-d9d7-4a47-82e6-fb1b16dfd51e"
+ }
+ ]
+ },
+ {
+ "Id": "8.2.1",
+ "Description": "This policy controls whether external domains are allowed, blocked or permitted based on an allowlist or denylist. When external domains are allowed, users in your organization can chat, add users to meetings, and use audio video conferencing with users in external organizations. The recommended state is Off on the Global (Org-wide default) policy.",
+ "Checks": [
+ "teams_external_domains_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.2 Users",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy controls whether external domains are allowed, blocked or permitted based on an allowlist or denylist. When external domains are allowed, users in your organization can chat, add users to meetings, and use audio video conferencing with users in external organizations. The recommended state is Off on the Global (Org-wide default) policy.",
+ "RationaleStatement": "Unrestricted external federation allows any Teams user from any organization to initiate contact with your users, making them susceptible to social engineering, phishing, and malware delivery via Teams chat. Restricting external domains to an allowlist or blocking them entirely eliminates this unsolicited contact vector. Real-world attacks and exploits delivered via Teams over external access channels include: - DarkGate malware - Social engineering / phishing attacks by \"Midnight Blizzard\" - GIFShell - Username enumeration",
+ "ImpactStatement": "Restricting external domains will limit users' ability to collaborate with individuals outside the organization unless their domain is explicitly allowlisted or they are invited as a guest in Microsoft Entra ID. Administrators choosing an allowlist approach will incur ongoing overhead to manage approved domains as external collaboration needs evolve. Note: Organizations may create custom external access policies with federation enabled and assign them to specific users or groups requiring external access, while keeping the Global (Org-wide default) policy restrictive.",
+ "RemediationProcedure": "Note: Configuring this setting at the organization level in Organization settings to either Off, Block all external domains or Allow only specific external domains is also a compliant remediation for this control. To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Set Manage external domains for this policy to Off. 6. Click Save. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command to configure the Global (Org-wide default) policy. Set-CsExternalAccessPolicy -Identity Global -EnableFederationAccess $false",
+ "AuditProcedure": "Note: The focus of this control at a minimum is the Global (Org-wide default) policy. If the organization-wide setting is configured to Allow only specific external domains or Block all external domains, then this is also considered a passing state due to its increased restrictiveness. To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Verify that Manage external domains for this policy is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Get-CsExternalAccessPolicy -Identity Global 3. Verify that EnableFederationAccess is False. Organization settings: Optional passing state 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Organization settings tab. 4. Verify that Manage external domains for this organization is set to one of the following: o Off o On with Allow or block external domains set to Allow only specific external domains o On with Allow or block external domains set to Block all external domains To audit using PowerShell: 1. Run the following command: Get-CsTenantFederationConfiguration | fl AllowFederatedUsers,AllowedDomains 2. Verify the output meets one of the following compliant conditions: o Off: AllowFederatedUsers is False o Block all external domains: AllowFederatedUsers is True and AllowedDomains is empty o Allow only specific external domains: AllowFederatedUsers is True and AllowedDomains contains only authorized domain names",
+ "AdditionalInformation": "",
+ "DefaultValue": "EnableFederationAccess - $True",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings:https://www.microsoft.com/en-us/security/blog/2023/08/02/midnight-blizzard-conducts-targeted-social-engineering-over-microsoft-teams/:https://www.bitdefender.com/blog/hotforsecurity/gifshell-attack-lets-hackers-create-reverse-shell-through-microsoft-teams-gifs/"
+ }
+ ]
+ },
+ {
+ "Id": "8.2.2",
+ "Description": "This policy setting controls chats and meetings initiated through the external access channel with unmanaged Teams users (those not managed by an organization, such as Microsoft Teams (free)). This does not govern anonymous meeting join via shared link, which is controlled separately. The recommended state is: People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts set to Off.",
+ "Checks": [
+ "teams_unmanaged_communication_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls chats and meetings initiated through the external access channel with unmanaged Teams users (those not managed by an organization, such as Microsoft Teams (free)). This does not govern anonymous meeting join via shared link, which is controlled separately. The recommended state is: People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts set to Off.",
+ "RationaleStatement": "Allowing users to communicate with unmanaged Teams users presents a potential security threat as little effort is required by threat actors to gain access to a trial or free Microsoft Teams account. Real-world attacks and exploits delivered via Teams over external access channels include: - DarkGate malware - Social engineering / Phishing attacks by \"Midnight Blizzard\" - GIFShell - Username enumeration",
+ "ImpactStatement": "Users will be unable to communicate with Teams users who are not managed by an organization. Organizations may choose to create additional policies for specific groups needing to communicate with unmanaged external users. Note: The settings that govern chats and meetings with external unmanaged Teams users aren't available in GCC, GCC High, or DOD deployments, or in private cloud environments.",
+ "RemediationProcedure": "Note: Configuring this setting at the organization level in Organization settings to Off is also a compliant remediation for this control. To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Set People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts to Off. 6. Click Save. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Set-CsExternalAccessPolicy -Identity Global -EnableTeamsConsumerAccess $false",
+ "AuditProcedure": "Note: The focus of this control at a minimum is the Global (Org-wide default) policy. If the organization-wide setting is configured to Off, then this is also considered a passing state due to its increased restrictiveness. To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Verify that People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Get-CsExternalAccessPolicy -Identity Global Verify that EnableTeamsConsumerAccess is set to False. Organization settings: Optional passing state 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Organization settings tab. 4. Verify that People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts is set to Off. To audit using PowerShell: 1. Run the following command: Get-CsTenantFederationConfiguration | fl AllowTeamsConsumer 2. Verify that AllowTeamsConsumer is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- EnableTeamsConsumerAccess (Global policy): True - AllowTeamsConsumer (Organization settings): True",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings:https://www.microsoft.com/en-us/security/blog/2023/08/02/midnight-blizzard-conducts-targeted-social-engineering-over-microsoft-teams/:https://www.bitdefender.com/blog/hotforsecurity/gifshell-attack-lets-hackers-create-reverse-shell-through-microsoft-teams-gifs/"
+ }
+ ]
+ },
+ {
+ "Id": "8.2.3",
+ "Description": "This setting prevents external users who are not managed by an organization from initiating contact with users in the protected organization. The recommended state is to uncheck People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts. Note: Disabling this setting is used as an additional stop gap for the parent setting which disables communication with unmanaged Teams users entirely. If an organization chooses to have an exception to Ensure communication with unmanaged Teams users is disabled they can do so while also disabling the ability for the same group of users to initiate contact. Disabling communication entirely will also disable the ability for unmanaged users to initiate contact.",
+ "Checks": [
+ "teams_external_users_cannot_start_conversations"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting prevents external users who are not managed by an organization from initiating contact with users in the protected organization. The recommended state is to uncheck People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts. Note: Disabling this setting is used as an additional stop gap for the parent setting which disables communication with unmanaged Teams users entirely. If an organization chooses to have an exception to Ensure communication with unmanaged Teams users is disabled they can do so while also disabling the ability for the same group of users to initiate contact. Disabling communication entirely will also disable the ability for unmanaged users to initiate contact.",
+ "RationaleStatement": "Allowing users to communicate with unmanaged Teams users presents a potential security threat as little effort is required by threat actors to gain access to a trial or free Microsoft Teams account. Real-world attacks and exploits delivered via Teams over external access channels include: - DarkGate malware - Social engineering / Phishing attacks by \"Midnight Blizzard\" - GIFShell - Username enumeration",
+ "ImpactStatement": "Unmanaged Teams users (those using personal Microsoft accounts or free Teams) will be unable to initiate new chats or meeting invitations with members of the organization. Organization members may still be able to join externally-initiated meetings depending on the configuration of the parent setting. Organizations that need to allow inbound contact from specific external users can assign a custom external access policy to those users that has EnableTeamsConsumerInbound enabled. Note: Chats and meetings with external unmanaged Teams users isn't available in GCC, GCC High, or DOD deployments, or in private cloud environments.",
+ "RemediationProcedure": "Note: Configuring this setting at the organization level in Organization settings to Off is also a compliant remediation for this control. To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Locate the parent setting People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts. 6. Uncheck People in my org can join external meetings and receive new chats from users who have unmanaged Microsoft accounts. 7. Click Save. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Set-CsExternalAccessPolicy -Identity Global -EnableTeamsConsumerInbound $false",
+ "AuditProcedure": "Note: The focus of this control at a minimum is the Global (Org-wide default) policy. If the equivalent organization-wide setting is disabled, then this is also considered a passing state due to its increased restrictiveness. To audit using the UI: Note: If the parent setting People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts is already set to Off then this setting will not be visible in the UI. 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Open the Policies tab. 4. Click on the Global (Org-wide default) settings policy. 5. Locate the parent setting People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts. 6. Verify that People in my org can join external meetings and receive new chats from users who have unmanaged Microsoft accounts is not checked. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Get-CsExternalAccessPolicy -Identity Global Verify that EnableTeamsConsumerInbound is False Organization settings: Optional passing state 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Select the Organization settings tab. 4. Locate the parent setting People in my org can chat and have meetings with external users who have unmanaged Microsoft accounts. 5. Verify that People in my org can join external meetings and receive new chats from users who have unmanaged Microsoft accounts is not checked. To audit using PowerShell: 1. Run the following command: Get-CsTenantFederationConfiguration | fl AllowTeamsConsumerInbound Verify that AllowTeamsConsumerInbound is False",
+ "AdditionalInformation": "",
+ "DefaultValue": "- EnableTeamsConsumerInbound (Global policy) : True - AllowTeamsConsumerInbound (Organization settings) : True",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings:https://www.microsoft.com/en-us/security/blog/2023/08/02/midnight-blizzard-conducts-targeted-social-engineering-over-microsoft-teams/:https://www.bitdefender.com/blog/hotforsecurity/gifshell-attack-lets-hackers-create-reverse-shell-through-microsoft-teams-gifs/"
+ }
+ ]
+ },
+ {
+ "Id": "8.2.4",
+ "Description": "This setting controls the organization's external access with Teams \"trial-only\" tenants. These are tenants that don't have any purchased seats. When set to Blocked, users from these trial-only tenants aren't able to search and contact your users via chats, Teams calls, and meetings (using the users' authenticated identities) and your users aren't able to reach users in these trial-only tenants. Users from the trial-only tenant are also removed from existing chats. The recommended state for People in my organization can communicate with accounts in trial Teams tenant is Off.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.2 Users",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting controls the organization's external access with Teams \"trial-only\" tenants. These are tenants that don't have any purchased seats. When set to Blocked, users from these trial-only tenants aren't able to search and contact your users via chats, Teams calls, and meetings (using the users' authenticated identities) and your users aren't able to reach users in these trial-only tenants. Users from the trial-only tenant are also removed from existing chats. The recommended state for People in my organization can communicate with accounts in trial Teams tenant is Off.",
+ "RationaleStatement": "Microsoft introduced this setting as Off by default on July 29, 2024 in order to block attack vectors being exploited by threat actors who have abused trial tenants. Enforcing the default ensures the setting is not reenabled for any reason. Allowing users to communicate with unmanaged Teams users presents a potential security threat as little effort is required by threat actors to gain access to a trial or free Microsoft Teams account. Real-world attacks and exploits delivered via Teams over external access channels include: - DarkGate malware - Social engineering / Phishing attacks by \"Midnight Blizzard\" - GIFShell - Username enumeration",
+ "ImpactStatement": "Users currently in chat conversations with accounts from trial tenants will be removed from those existing chats when this setting is disabled. Organizations that have established communication with external contacts who are using trial tenants will need to use alternative channels (such as email) until those contacts migrate to a licensed tenant.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Select the Organization settings tab. 4. Set People in my organization can communicate with accounts in trial Teams tenant to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants \"Blocked\"",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com/. 2. Expand External collaboration and select External access. 3. Select the Organization settings tab. 4. Verify that People in my organization can communicate with accounts in trial Teams tenant is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command: Get-CsTenantFederationConfiguration Verify that ExternalAccessWithTrialTenants is set to Blocked.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Off (UI) - Blocked (PowerShell)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#block-federation-with-teams-trial-only-tenants:https://www.microsoft.com/en-us/security/blog/2023/08/02/midnight-blizzard-conducts-targeted-social-engineering-over-microsoft-teams/:https://www.bitdefender.com/en-us/blog/hotforsecurity/gifshell-attack-lets-hackers-create-reverse-shell-through-microsoft-teams-gifs"
+ }
+ ]
+ },
+ {
+ "Id": "8.4.1",
+ "Description": "This policy setting controls which class of apps are available for users to install.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.4 Teams apps",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Manual",
+ "Description": "This policy setting controls which class of apps are available for users to install.",
+ "RationaleStatement": "Allowing users to install third-party or unverified apps poses a potential risk of introducing malicious software to the environment.",
+ "ImpactStatement": "Users will only be able to install approved classes of apps.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Expand Teams apps and select Manage apps. 3. In the upper right click Actions > Org-wide app settings. 4. For Third-party apps set Let users install and use available apps by default to Off. 5. For Custom apps set Let users install and use available apps by default to Off. 6. For Custom apps set Let users interact with custom apps in preview to Off.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Expand Teams apps and select Manage apps. 3. In the upper right click Actions > Org-wide app settings. 4. For Third-party apps verify Let users install and use available apps by default is Off. 5. For Custom apps verify Let users install and use available apps by default is Off. 6. For Custom apps verify Let users interact with custom apps in preview is Off.",
+ "AdditionalInformation": "",
+ "DefaultValue": "- Third-party apps: On - Custom apps: On",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/app-centric-management:https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/reducing-attack-surface-in-microsoft-teams?view=o365-worldwide#disabling-third-party--custom-apps"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.1",
+ "Description": "Anonymous users are users whose identity can't be verified. They may be logged in to an organization without a mutual trust relationship or they may not have an account (guest or user). Anonymous participants appear with \"(Unverified)\" appended to their name in meetings. These users could include: - Users who aren't logged in to Teams with a work or school account. - Users from non-trusted organizations (as configured in external access) and from organizations that you trust but which don't trust your organization. When defining trusted organizations for external meetings and chat, ensure both organizations allow each other's domains. Meeting organizers and participants should have user policies that allow external access. These settings prevent attendees from being considered anonymous due to external access settings. For details, see IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities The recommended state is Anonymous users can join a meeting unverified set to Off.",
+ "Checks": [
+ "teams_meeting_anonymous_user_join_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Anonymous users are users whose identity can't be verified. They may be logged in to an organization without a mutual trust relationship or they may not have an account (guest or user). Anonymous participants appear with \"(Unverified)\" appended to their name in meetings. These users could include: - Users who aren't logged in to Teams with a work or school account. - Users from non-trusted organizations (as configured in external access) and from organizations that you trust but which don't trust your organization. When defining trusted organizations for external meetings and chat, ensure both organizations allow each other's domains. Meeting organizers and participants should have user policies that allow external access. These settings prevent attendees from being considered anonymous due to external access settings. For details, see IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities The recommended state is Anonymous users can join a meeting unverified set to Off.",
+ "RationaleStatement": "For meetings that could contain sensitive information, it is best to allow the meeting organizer to vet anyone not directly sent an invite before admitting them to the meeting. This will also prevent the anonymous user from using the meeting link to have meetings at unscheduled times. Note: Those companies that don't normally operate at a Level 2 environment, but do deal with sensitive information, may want to consider this policy setting.",
+ "ImpactStatement": "Individuals who were not sent or forwarded a meeting invite will not be able to join the meeting automatically.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby set Anonymous users can join a meeting unverified to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -AllowAnonymousUsersToJoinMeeting $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby verify that Anonymous users can join a meeting unverified is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowAnonymousUsersToJoinMeeting 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On (True)",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/reducing-attack-surface-in-microsoft-teams?view=o365-worldwide#configure-meeting-settings:https://learn.microsoft.com/en-us/microsoftteams/settings-policies-reference?WT.mc_id=TeamsAdminCenterCSH#meeting-join--lobby:https://learn.microsoft.com/en-us/MicrosoftTeams/configure-meetings-sensitive-protection:https://learn.microsoft.com/en-us/microsoftteams/anonymous-users-in-meetings:https://learn.microsoft.com/en-us/microsoftteams/plan-meetings-external-participants"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.2",
+ "Description": "This policy setting controls if an anonymous participant can start a Microsoft Teams meeting without someone in attendance. Anonymous users and dial-in callers must wait in the lobby until the meeting is started by someone in the organization or an external user from a trusted organization. Anonymous participants are classified as: - Participants who are not logged in to Teams with a work or school account. - Participants from non-trusted organizations (as configured in external access). - Participants from organizations where there is not mutual trust. Note: This setting only applies when Who can bypass the lobby is set to Everyone. If the anonymous users can join a meeting organization-level setting or meeting policy is Off, this setting only applies to dial-in callers.",
+ "Checks": [
+ "teams_meeting_anonymous_user_start_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls if an anonymous participant can start a Microsoft Teams meeting without someone in attendance. Anonymous users and dial-in callers must wait in the lobby until the meeting is started by someone in the organization or an external user from a trusted organization. Anonymous participants are classified as: - Participants who are not logged in to Teams with a work or school account. - Participants from non-trusted organizations (as configured in external access). - Participants from organizations where there is not mutual trust. Note: This setting only applies when Who can bypass the lobby is set to Everyone. If the anonymous users can join a meeting organization-level setting or meeting policy is Off, this setting only applies to dial-in callers.",
+ "RationaleStatement": "Not allowing anonymous participants to automatically join a meeting reduces the risk of meeting spamming.",
+ "ImpactStatement": "Anonymous participants will not be able to start a Microsoft Teams meeting.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby set Anonymous users and dial-in callers can start a meeting to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -AllowAnonymousUsersToStartMeeting $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby verify that Anonymous users and dial-in callers can start a meeting is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowAnonymousUsersToStartMeeting 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off (False)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/anonymous-users-in-meetings:https://learn.microsoft.com/en-us/microsoftteams/who-can-bypass-meeting-lobby#overview-of-lobby-settings-and-policies"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.3",
+ "Description": "This policy setting controls who can join a meeting directly and who must wait in the lobby until they're admitted by an organizer, co-organizer, or presenter of the meeting. The recommended state is People who were invited, People in my org or Only organizers and co-organizers.",
+ "Checks": [
+ "teams_meeting_external_lobby_bypass_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls who can join a meeting directly and who must wait in the lobby until they're admitted by an organizer, co-organizer, or presenter of the meeting. The recommended state is People who were invited, People in my org or Only organizers and co-organizers.",
+ "RationaleStatement": "For meetings that could contain sensitive information, it is best to allow the meeting organizer to vet anyone not directly sent an invite before admitting them to the meeting. This will also prevent the anonymous user from using the meeting link to have meetings at unscheduled times.",
+ "ImpactStatement": "Individuals who are not part of the organization will have to wait in the lobby until they're admitted by an organizer, co-organizer, or presenter of the meeting. Any individual who dials into the meeting regardless of status will also have to wait in the lobby. This includes internal users who are considered unauthenticated when dialing in.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby set Who can bypass the lobby to one of the following: o People who were invited o People in my org o Only organizers and co-organizers To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run one of the following PowerShell commands depending on the desired compliant state: To set to People who were invited: Set-CsTeamsMeetingPolicy -Identity Global -AutoAdmittedUsers \"InvitedUsers\" To set to People in my org: Set-CsTeamsMeetingPolicy -Identity Global -AutoAdmittedUsers \"EveryoneInCompanyExcludingGuests\" To set to Only organizers and co-organizers: Set-CsTeamsMeetingPolicy -Identity Global -AutoAdmittedUsers \"OrganizerOnly\"",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby verify Who can bypass the lobby is set to one of the following: o People who were invited o People in my org o Only organizers and co-organizers To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AutoAdmittedUsers 3. Verify that the returned value is one of the following strings: o InvitedUsers o EveryoneInCompanyExcludingGuests o OrganizerOnly",
+ "AdditionalInformation": "",
+ "DefaultValue": "People in my org and guests (EveryoneInCompany)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/who-can-bypass-meeting-lobby#overview-of-lobby-settings-and-policies:https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.4",
+ "Description": "This policy setting controls if users who dial in by phone can join the meeting directly or must wait in the lobby. Admittance to the meeting from the lobby is authorized by the meeting organizer, co-organizer, or presenter of the meeting.",
+ "Checks": [
+ "teams_meeting_dial_in_lobby_bypass_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls if users who dial in by phone can join the meeting directly or must wait in the lobby. Admittance to the meeting from the lobby is authorized by the meeting organizer, co-organizer, or presenter of the meeting.",
+ "RationaleStatement": "For meetings that could contain sensitive information, it is best to allow the meeting organizer to vet anyone not directly from the organization.",
+ "ImpactStatement": "Individuals who are dialing in to the meeting must wait in the lobby until a meeting organizer, co-organizer, or presenter admits them.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby set People dialing in can bypass the lobby to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -AllowPSTNUsersToBypassLobby $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting join & lobby verify that People dialing in can bypass the lobby is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowPSTNUsersToBypassLobby 3. Verify that the value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off (False)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/who-can-bypass-meeting-lobby#overview-of-lobby-settings-and-policies:https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.5",
+ "Description": "This policy setting controls who has access to read and write chat messages during a meeting.",
+ "Checks": [
+ "teams_meeting_chat_anonymous_users_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls who has access to read and write chat messages during a meeting.",
+ "RationaleStatement": "Ensuring that only authorized individuals can read and write chat messages during a meeting reduces the risk that a malicious user can inadvertently show content that is not appropriate or view sensitive information.",
+ "ImpactStatement": "Only authorized individuals will be able to read and write chat messages during a meeting.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting engagement set Meeting chat to On for everyone but anonymous users. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the minimum recommended state: Set-CsTeamsMeetingPolicy -Identity Global -MeetingChatEnabledType \"EnabledExceptAnonymous\" Note: The audit section outlines additional compliant states which are more restrictive than the recommended state.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting engagement verify that Meeting chat is set to On for everyone but anonymous users or a more restrictive value: In-meeting only except anonymous or Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl MeetingChatEnabledType 3. Verify that the returned value is EnabledExceptAnonymous or a more restrictive value EnabledInMeetingOnlyForAllExceptAnonymous or Disabled.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On for everyone (Enabled)",
+ "References": "https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps#-meetingchatenabledtype"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.6",
+ "Description": "This policy setting controls who can present in a Teams meeting. Note: Organizers and co-organizers can change this setting when the meeting is set up.",
+ "Checks": [
+ "teams_meeting_presenters_restricted"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting controls who can present in a Teams meeting. Note: Organizers and co-organizers can change this setting when the meeting is set up.",
+ "RationaleStatement": "Ensuring that only authorized individuals are able to present reduces the risk that a malicious user can inadvertently show content that is not appropriate.",
+ "ImpactStatement": "Only organizers and co-organizers will be able to present without being granted permission.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under content sharing set Who can present to Only organizers and co- organizers. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -DesignatedPresenterRoleMode \"OrganizerOnlyUserOverride\"",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under content sharing verify Who can present is set to Only organizers and co-organizers. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl DesignatedPresenterRoleMode 3. Verify that the returned value is OrganizerOnlyUserOverride.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Everyone (EveryoneUserOverride)",
+ "References": "https://learn.microsoft.com/en-US/microsoftteams/meeting-who-present-request-control:https://learn.microsoft.com/en-us/microsoftteams/meeting-who-present-request-control#manage-who-can-present:https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/reducing-attack-surface-in-microsoft-teams?view=o365-worldwide#configure-meeting-settings-restrict-presenters:https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.7",
+ "Description": "This policy setting allows control of who can present in meetings and who can request control of the presentation while a meeting is underway.",
+ "Checks": [
+ "teams_meeting_external_control_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This policy setting allows control of who can present in meetings and who can request control of the presentation while a meeting is underway.",
+ "RationaleStatement": "Ensuring that only authorized individuals and not external participants are able to present and request control reduces the risk that a malicious user can inadvertently show content that is not appropriate. External participants are categorized as follows: external users, guests, and anonymous users.",
+ "ImpactStatement": "External participants will not be able to present or request control during the meeting. Warning: This setting also affects webinars. Note: At this time, to give and take control of shared content during a meeting, both parties must be using the Teams desktop client. Control isn't supported when either party is running Teams in a browser.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under content sharing set External participants can give or request control to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global - AllowExternalParticipantGiveRequestControl $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under content sharing verify that External participants can give or request control is Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowExternalParticipantGiveRequestControl 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Off (False)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/meeting-who-present-request-control:https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.8",
+ "Description": "This meeting policy setting controls whether users can read or write messages in external meeting chats with untrusted organizations. If an external organization is on the list of trusted organizations this setting will be ignored.",
+ "Checks": [
+ "teams_meeting_external_chat_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This meeting policy setting controls whether users can read or write messages in external meeting chats with untrusted organizations. If an external organization is on the list of trusted organizations this setting will be ignored.",
+ "RationaleStatement": "Restricting access to chat in meetings hosted by external organizations limits the opportunity for an exploit like GIFShell or DarkGate malware from being delivered to users.",
+ "ImpactStatement": "When joining external meetings users will be unable to read or write chat messages in Teams meetings with organizations that they don't have a trust relationship with. This will completely remove the chat functionality in meetings. From an I.T. perspective both the upkeep of adding new organizations to the trusted list and the decision-making process behind whether to trust or not trust an external partner will increase time expenditure.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab.. 3. Select Meetings to open the meeting settings section. 4. Under meeting engagement set External meeting chat to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -AllowExternalNonTrustedMeetingChat $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under meeting engagement verify that External meeting chat is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowExternalNonTrustedMeetingChat 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On(True)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/settings-policies-reference#meeting-engagement"
+ }
+ ]
+ },
+ {
+ "Id": "8.5.9",
+ "Description": "This setting controls the ability for a user to initiate a recording of a meeting in progress. The recommended state is Off for the Global (Org-wide default) meeting policy.",
+ "Checks": [
+ "teams_meeting_recording_disabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.5 Meetings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting controls the ability for a user to initiate a recording of a meeting in progress. The recommended state is Off for the Global (Org-wide default) meeting policy.",
+ "RationaleStatement": "Disabling meeting recordings in the Global meeting policy ensures that only authorized users, such as organizers, co-organizers, and leads, can initiate a recording. This measure helps safeguard sensitive information by preventing unauthorized individuals from capturing and potentially sharing meeting content. Restricting recording capabilities to specific roles allows organizations to exercise greater control over what is recorded, aligning it with the meeting's confidentiality requirements. Note: Creating a separate policy for users or groups who are allowed to record is expected and in compliance. This control is only for the default meeting policy.",
+ "ImpactStatement": "If there are no additional policies allowing anyone to record, then recording will effectively be disabled.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under Recording & transcription set Meeting recording to Off. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to set the recommended state: Set-CsTeamsMeetingPolicy -Identity Global -AllowCloudRecording $false",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Meetings to open the meeting settings section. 4. Under Recording & transcription verify that Meeting recording is set to Off. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following command to verify the recommended state: Get-CsTeamsMeetingPolicy -Identity Global | fl AllowCloudRecording 3. Verify that the returned value is False.",
+ "AdditionalInformation": "",
+ "DefaultValue": "On (True)",
+ "References": "https://learn.microsoft.com/en-us/microsoftteams/settings-policies-reference#recording--transcription"
+ }
+ ]
+ },
+ {
+ "Id": "8.6.1",
+ "Description": "User reporting settings allow a user to report a message as malicious for further analysis. This recommendation is composed of 3 different settings and all must be configured for compliance: - In the Teams admin center: On by default and controls whether users are able to report messages from Teams. When this setting is turned off, users can't report messages within Teams, so the corresponding setting in the Microsoft 365 Defender portal is irrelevant. - In the Microsoft 365 Defender portal: On by default for new tenants. Existing tenants need to enable it. If user reporting of messages is turned on in the Teams admin center, it also needs to be turned on the Defender portal for user reported messages to show up correctly on the User reported tab on the Submissions page. - Defender - Report message destinations: This applies to more than just Microsoft Teams and allows for an organization to keep their reports contained. Due to how the parameters are configured on the backend it is included in this assessment as a requirement.",
+ "Checks": [
+ "teams_security_reporting_enabled",
+ "defender_chat_report_policy_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "8 Microsoft Teams admin center",
+ "SubSection": "8.6 Messaging",
+ "Profile": "E5 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "User reporting settings allow a user to report a message as malicious for further analysis. This recommendation is composed of 3 different settings and all must be configured for compliance: - In the Teams admin center: On by default and controls whether users are able to report messages from Teams. When this setting is turned off, users can't report messages within Teams, so the corresponding setting in the Microsoft 365 Defender portal is irrelevant. - In the Microsoft 365 Defender portal: On by default for new tenants. Existing tenants need to enable it. If user reporting of messages is turned on in the Teams admin center, it also needs to be turned on the Defender portal for user reported messages to show up correctly on the User reported tab on the Submissions page. - Defender - Report message destinations: This applies to more than just Microsoft Teams and allows for an organization to keep their reports contained. Due to how the parameters are configured on the backend it is included in this assessment as a requirement.",
+ "RationaleStatement": "Users will be able to more quickly and systematically alert administrators of suspicious malicious messages within Teams. The content of these messages may be sensitive in nature and therefore should be kept within the organization and not shared with Microsoft without first consulting company policy. Note: - The reported message remains visible to the user in the Teams client. - Users can report the same message multiple times. - The message sender isn't notified that messages were reported.",
+ "ImpactStatement": "Enabling message reporting has an impact beyond just addressing security concerns. When users of the platform report a message, the content could include messages that are threatening or harassing in nature, possibly stemming from colleagues. Due to this the security staff responsible for reviewing and acting on these reports should be equipped with the skills to discern and appropriately direct such messages to the relevant departments, such as Human Resources (HR).",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Messaging to open the messaging settings section. 4. Set Report a security concern to On. 5. Next, navigate to Microsoft 365 Defender https://security.microsoft.com/ 6. Expand System > Settings and select Email & collaboration. 7. Click on User reported settings. 8. Under Microsoft Teams check the box for Monitor reported items in Microsoft Teams and click Save. 9. Set Send reported messages to: to My reporting mailbox only with reports configured to be sent to authorized staff. To remediate using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Connect to Exchange Online PowerShell using Connect-ExchangeOnline. 3. Run the following cmdlet: Set-CsTeamsMessagingPolicy -Identity Global -AllowSecurityEndUserReporting $true 4. To configure the Defender reporting policies, edit and run this script: $usersub = \"userreportedmessages@fabrikam.com\" # Change this. $params = @{ Identity = \"DefaultReportSubmissionPolicy\" EnableReportToMicrosoft = $false ReportChatMessageEnabled = $false ReportChatMessageToCustomizedAddressEnabled = $true ReportJunkToCustomizedAddress = $true ReportNotJunkToCustomizedAddress = $true ReportPhishToCustomizedAddress = $true ReportJunkAddresses = $usersub ReportNotJunkAddresses = $usersub ReportPhishAddresses = $usersub } Set-ReportSubmissionPolicy @params New-ReportSubmissionRule -Name DefaultReportSubmissionRule - ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Teams admin center https://admin.teams.microsoft.com. 2. Click Settings & policies and select the Global (Org-wide default) settings tab. 3. Select Messaging to open the messaging settings section. 4. Verify that Report a security concern is On. 5. Next, navigate to Microsoft 365 Defender https://security.microsoft.com/ 6. Expand System > Settings and select Email & collaboration. 7. Click on User reported settings. 8. Under Microsoft Teams verify that Monitor reported items in Microsoft Teams is checked. 9. Verify that Send reported messages to: is set to My reporting mailbox only with report email addresses defined for authorized staff. To audit using PowerShell: 1. Connect to Teams PowerShell using Connect-MicrosoftTeams. 2. Run the following cmdlet for to assess Teams: Get-CsTeamsMessagingPolicy -Identity Global | fl AllowSecurityEndUserReporting 3. Verify that the value returned is True. 4. Connect to Exchange Online PowerShell using Connect-ExchangeOnline. 5. Run this cmdlet to assess Defender: Get-ReportSubmissionPolicy | fl Report* 6. Verify that the output matches the following values with organization specific email addresses: ReportJunkToCustomizedAddress : True ReportNotJunkToCustomizedAddress : True ReportPhishToCustomizedAddress : True ReportJunkAddresses : {SOC@contoso.com} ReportNotJunkAddresses : {SOC@contoso.com} ReportPhishAddresses : {SOC@contoso.com} ReportChatMessageEnabled : False ReportChatMessageToCustomizedAddressEnabled : True",
+ "AdditionalInformation": "",
+ "DefaultValue": "On (True) Report message destination: Microsoft Only",
+ "References": "https://learn.microsoft.com/en-us/defender-office-365/submissions-teams?view=o365-worldwide"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.1",
+ "Description": "This setting allows business-to-business (B2B) guests access to Microsoft Fabric, and contents that they have permissions to. With the setting turned off, B2B guest users receive an error when trying to access Power BI. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting allows business-to-business (B2B) guests access to Microsoft Fabric, and contents that they have permissions to. With the setting turned off, B2B guest users receive an error when trying to access Power BI. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Establishing and enforcing a dedicated security group prevents unauthorized access to Microsoft Fabric for guests collaborating in Azure that are new or assigned guest status from other applications. This upholds the principle of least privilege and uses role-based access control (RBAC). These security groups can also be used for tasks like conditional access, enhancing risk management and user accountability across the organization.",
+ "ImpactStatement": "Security groups will need to be more closely tended to and monitored.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Guest users can access Microsoft Fabric to one of these states: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Guest users can access Microsoft Fabric is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName AllowGuestUserToAccessSharedContent in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is false. o enabled is true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.2",
+ "Description": "This setting helps organizations choose whether new external users can be invited to the organization through Power BI sharing, permissions, and subscription experiences. This setting only controls the ability to invite through Power BI. The recommended state is Enabled for a subset of the organization or Disabled. Note: To invite external users to the organization, the user must also have the Microsoft Entra Guest Inviter role.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting helps organizations choose whether new external users can be invited to the organization through Power BI sharing, permissions, and subscription experiences. This setting only controls the ability to invite through Power BI. The recommended state is Enabled for a subset of the organization or Disabled. Note: To invite external users to the organization, the user must also have the Microsoft Entra Guest Inviter role.",
+ "RationaleStatement": "Establishing and enforcing a dedicated security group prevents unauthorized access to Microsoft Fabric for guests collaborating in Azure that are new or assigned guest status from other applications. This upholds the principle of least privilege and uses role-based access control (RBAC). These security groups can also be used for tasks like conditional access, enhancing risk management and user accountability across the organization.",
+ "ImpactStatement": "Guest user invitations will be limited to only specific employees.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Users can invite guest users to collaborate through item sharing and permissions to one of these states: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Users can invite guest users to collaborate through item sharing and permissions is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName ExternalSharingV2 in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is false. o enabled is true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing:https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-azure-ad-b2b#invite-guest-users"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.3",
+ "Description": "This setting allows Microsoft Entra B2B guest users to have full access to the browsing experience using the left-hand navigation pane in the organization. Guest users who have been assigned workspace roles or specific item permissions will continue to have those roles and/or permissions, even if this setting is disabled. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting allows Microsoft Entra B2B guest users to have full access to the browsing experience using the left-hand navigation pane in the organization. Guest users who have been assigned workspace roles or specific item permissions will continue to have those roles and/or permissions, even if this setting is disabled. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Establishing and enforcing a dedicated security group prevents unauthorized access to Microsoft Fabric for guests collaborating in Entra that are new or assigned guest status from other applications. This upholds the principle of least privilege and uses role-based access control (RBAC). These security groups can also be used for tasks like conditional access, enhancing risk management and user accountability across the organization.",
+ "ImpactStatement": "Security groups will need to be more closely tended to and monitored.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Guest users can browse and access Fabric content to one of these states: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Guest users can browse and access Fabric content is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName ElevatedGuestsTenant in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is false. o enabled is true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.4",
+ "Description": "Power BI enables users to share reports and materials directly on the internet from both the application's desktop version and its web user interface. This functionality generates a publicly reachable web link that doesn't necessitate authentication or the need to be an Entra ID user in order to access and view it. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Power BI enables users to share reports and materials directly on the internet from both the application's desktop version and its web user interface. This functionality generates a publicly reachable web link that doesn't necessitate authentication or the need to be an Entra ID user in order to access and view it. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "When using Publish to Web anyone on the Internet can view a published report or visual. Viewing requires no authentication. It includes viewing detail-level data that your reports aggregate. By disabling the feature, restricting access to certain users and allowing existing embed codes organizations can mitigate the exposure of confidential or proprietary information.",
+ "ImpactStatement": "Depending on the organization's utilization administrators may experience more overhead managing embed codes, and requests.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Publish to web to one of these states: o Disabled o Enabled with Choose how embed codes work set to Only allow existing codes AND Specific security groups selected and defined Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Publish to web is set to one of the following: o Disabled o Enabled with Choose how embed codes work set to Only allow existing codes AND Specific security groups selected and defined Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName PublishToWeb in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is false. o enabled is true AND createP2w is false AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: The createP2w property can be found nested under properties.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization Only allow existing codes",
+ "References": "https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-publish-to-web:https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing#publish-to-web"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.5",
+ "Description": "Power BI allows the integration of R and Python scripts directly into visuals. This feature allows data visualizations by incorporating custom calculations, statistical analyses, machine learning models, and more using R or Python scripts. Custom visuals can be created by embedding them directly into Power BI reports. Users can then interact with these visuals and see the results of the custom code within the Power BI interface.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 2",
+ "AssessmentStatus": "Automated",
+ "Description": "Power BI allows the integration of R and Python scripts directly into visuals. This feature allows data visualizations by incorporating custom calculations, statistical analyses, machine learning models, and more using R or Python scripts. Custom visuals can be created by embedding them directly into Power BI reports. Users can then interact with these visuals and see the results of the custom code within the Power BI interface.",
+ "RationaleStatement": "Disabling this feature can reduce the attack surface by preventing potential malicious code execution leading to data breaches, or unauthorized access. The potential for sensitive or confidential data being leaked to unintended users is also increased with the use of scripts.",
+ "ImpactStatement": "Use of R and Python scripting will require exceptions for developers, along with more stringent code review.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to R and Python visuals settings. 4. Set Interact with and share R and Python visuals to Disabled",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to R and Python visuals settings. 4. Verify that Interact with and share R and Python visuals is set to Disabled To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName RScriptVisual in the output. 3. Verify that enabled is false.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-r-python-visuals:https://learn.microsoft.com/en-us/power-bi/visuals/service-r-visuals:https://www.r-project.org/"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.6",
+ "Description": "Information protection tenant settings help to protect sensitive information in the Power BI tenant. Allowing and applying sensitivity labels to content ensures that information is only seen and accessed by the appropriate users. The recommended state is Enabled or Enabled for a subset of the organization. Note: Sensitivity labels and protection are only applied to files exported to Excel, PowerPoint, or PDF files, that are controlled by \"Export to Excel\" and \"Export reports as PowerPoint presentation or PDF documents\" settings. All other export and sharing options do not support the application of sensitivity labels and protection. Note 2: There are some prerequisite steps that need to be completed in order to fully utilize labeling. See here.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Information protection tenant settings help to protect sensitive information in the Power BI tenant. Allowing and applying sensitivity labels to content ensures that information is only seen and accessed by the appropriate users. The recommended state is Enabled or Enabled for a subset of the organization. Note: Sensitivity labels and protection are only applied to files exported to Excel, PowerPoint, or PDF files, that are controlled by \"Export to Excel\" and \"Export reports as PowerPoint presentation or PDF documents\" settings. All other export and sharing options do not support the application of sensitivity labels and protection. Note 2: There are some prerequisite steps that need to be completed in order to fully utilize labeling. See here.",
+ "RationaleStatement": "Establishing data classifications and affixing labels to data at creation enables organizations to discern the data's criticality, sensitivity, and value. This initial identification enables the implementation of appropriate protective measures, utilizing technologies like Data Loss Prevention (DLP) to avert inadvertent exposure and enforcing access controls to safeguard against unauthorized access. This practice can also promote user awareness and responsibility in regard to the nature of the data they interact with. Which in turn can foster awareness in other areas of data management across the organization.",
+ "ImpactStatement": "Additional license requirements like Power BI Pro are required, as outlined in the Licensed and requirements page linked in the description and references sections.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Information protection. 4. Set Allow users to apply sensitivity labels for content to one of these states: o Enabled o Enabled with Specific security groups selected and defined.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Information protection. 4. Verify that Allow users to apply sensitivity labels for content is set to one of the following: o Enabled o Enabled with Specific security groups selected and defined. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName EimInformationProtectionEdit in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is true. o enabled is true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled",
+ "References": "https://learn.microsoft.com/en-us/power-bi/enterprise/service-security-enable-data-sensitivity-labels:https://learn.microsoft.com/en-us/fabric/governance/data-loss-prevention-overview:https://learn.microsoft.com/en-us/power-bi/enterprise/service-security-enable-data-sensitivity-labels#licensing-and-requirements"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.7",
+ "Description": "Creating a shareable link allows a user to create a link to a report or dashboard, then add that link to an email or another messaging application. There are 3 options that can be selected when creating a shareable link: - People in your organization - People with existing access - Specific people This setting solely deals with restrictions to People in the organization. External users by default are not included in any of these categories, and therefore cannot use any of these links regardless of the state of this setting. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Creating a shareable link allows a user to create a link to a report or dashboard, then add that link to an email or another messaging application. There are 3 options that can be selected when creating a shareable link: - People in your organization - People with existing access - Specific people This setting solely deals with restrictions to People in the organization. External users by default are not included in any of these categories, and therefore cannot use any of these links regardless of the state of this setting. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "While external users are unable to utilize shareable links, disabling or restricting this feature ensures that a user cannot generate a link accessible by individuals within the same organization who lack the necessary clearance to the shared data. For example, a member of Human Resources intends to share sensitive information with a particular employee or another colleague within their department. The owner would be prompted to specify either People with existing access or Specific people when generating the link requiring the person clicking the link to pass a first layer access control list. This measure along with proper file and folder permissions can help prevent unintended access and potential information leakage.",
+ "ImpactStatement": "If the setting is Enabled then only specific people in the organization would be allowed to create general links viewable by the entire organization.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Allow shareable links to grant access to everyone in your organization to one of these states: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Allow shareable links to grant access to everyone in your organization is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName ShareLinkToEntireOrg in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is set to false. o enabled is set to true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-share-dashboards?wt.mc_id=powerbi_inproduct_sharedialog#link-settings:https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.8",
+ "Description": "Power BI admins can specify which users or user groups can share datasets externally with guests from a different tenant through the in-place mechanism. Disabling this setting prevents any user from sharing datasets externally by restricting the ability of users to turn on external sharing for datasets they own or manage. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Power BI admins can specify which users or user groups can share datasets externally with guests from a different tenant through the in-place mechanism. Disabling this setting prevents any user from sharing datasets externally by restricting the ability of users to turn on external sharing for datasets they own or manage. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Establishing and enforcing a dedicated security group prevents unauthorized access to Microsoft Fabric for guests collaborating in Azure that are new or from other applications. This upholds the principle of least privilege and uses role-based access control (RBAC). These security groups can also be used for tasks like conditional access, enhancing risk management and user accountability across the organization.",
+ "ImpactStatement": "Security groups will need to be more closely tended to and monitored.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Set Allow specific users to turn on external data sharing to one of these states: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Export and Sharing settings. 4. Verify that Allow specific users to turn on external data sharing is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName EnableDatasetInPlaceSharing in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is set to false. o enabled is set to true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-export-sharing"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.9",
+ "Description": "This setting blocks the use of resource key based authentication. The Block ResourceKey Authentication setting applies to streaming and PUSH datasets. If blocked users will not be allowed to send data to streaming and PUSH datasets using the API with a resource key. The recommended state is Enabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "This setting blocks the use of resource key based authentication. The Block ResourceKey Authentication setting applies to streaming and PUSH datasets. If blocked users will not be allowed to send data to streaming and PUSH datasets using the API with a resource key. The recommended state is Enabled.",
+ "RationaleStatement": "Resource keys are a form of authentication that allows users to access Power BI resources (such as reports, dashboards, and datasets) without requiring individual user accounts. While convenient, this method bypasses the organization's centralized identity and access management controls. Enabling ensures that access to Power BI resources is tied to the organization's authentication mechanisms, providing a more secure and controlled environment.",
+ "ImpactStatement": "Developers will need to request a special exception in order to use this feature.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Set Block ResourceKey Authentication to Enabled",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Verify that Block ResourceKey Authentication is set to Enabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName BlockResourceKeyAuthentication in the output. 3. Verify that enabled is set to true. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer:https://learn.microsoft.com/en-us/power-bi/connect-data/service-real-time-streaming"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.10",
+ "Description": "Use a service principal to access Fabric public APIs that include create, read, update, and delete (CRUD) operations, and are protected by a Fabric permission model. To allow an app to use service principal authentication, its service principal must be included in an allowed security group. You can control who can access service principals by creating dedicated security groups and using these groups in other tenant settings. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Use a service principal to access Fabric public APIs that include create, read, update, and delete (CRUD) operations, and are protected by a Fabric permission model. To allow an app to use service principal authentication, its service principal must be included in an allowed security group. You can control who can access service principals by creating dedicated security groups and using these groups in other tenant settings. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Leaving API access unrestricted increases the attack surface in the event an adversary gains access to a Service Principal. APIs are a feature-rich method for programmatic access to many areas of Power Bi and should be guarded closely.",
+ "ImpactStatement": "Service principals will need to be members of specific security groups in order to perform public API calls.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Set Service principals can call Fabric public APIs to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Verify that Service principals can call Fabric public APIs is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName ServicePrincipalAccessPermissionAPIs in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is set to false. o enabled is set to true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Enabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.11",
+ "Description": "Service principal profiles provide a flexible solution for apps used in a multitenancy deployment. The profiles enable customer data isolation and tighter security boundaries between customers that are utilizing the app. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Service principal profiles provide a flexible solution for apps used in a multitenancy deployment. The profiles enable customer data isolation and tighter security boundaries between customers that are utilizing the app. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Service Principals should be restricted to a security group to limit which Service Principals can interact with profiles. This supports the principle of least privilege.",
+ "ImpactStatement": "Disabled is the default behavior.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Set Allow service principals to create and use profiles to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Verify that Allow service principals to create and use profiles is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName AllowServicePrincipalsCreateAndUseProfiles in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is set to false. o enabled is set to true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer:https://learn.microsoft.com/en-us/power-bi/developer/embedded/embed-multi-tenancy"
+ }
+ ]
+ },
+ {
+ "Id": "9.1.12",
+ "Description": "Use a service principal to access these Fabric APIs that aren't protected by a Fabric permission model. - Create Workspace - Create Connection - Create Deployment Pipeline To allow an app to use service principal authentication, its service principal must be included in an allowed security group. You can control who can access service principals by creating dedicated security groups and using these groups in other tenant settings. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "Checks": [],
+ "Attributes": [
+ {
+ "Section": "9 Microsoft Fabric",
+ "SubSection": "9.1 Tenant settings",
+ "Profile": "E3 Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "Use a service principal to access these Fabric APIs that aren't protected by a Fabric permission model. - Create Workspace - Create Connection - Create Deployment Pipeline To allow an app to use service principal authentication, its service principal must be included in an allowed security group. You can control who can access service principals by creating dedicated security groups and using these groups in other tenant settings. The recommended state is Enabled for a subset of the organization or Disabled.",
+ "RationaleStatement": "Leaving API access unrestricted increases the attack surface in the event an adversary gains access to a Service Principal. APIs are a feature-rich method for programmatic access to many areas of Power Bi and should be guarded closely.",
+ "ImpactStatement": "Service principals will need to be members of specific security groups in order to perform public API calls.",
+ "RemediationProcedure": "To remediate using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Set Service principals can create workspaces, connections, and deployment pipelines to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled.",
+ "AuditProcedure": "To audit using the UI: 1. Navigate to Microsoft Fabric https://app.powerbi.com/admin-portal 2. Select Tenant settings. 3. Scroll to Developer settings. 4. Verify that Service principals can create workspaces, connections, and deployment pipelines is set to one of the following: o Disabled o Enabled with Specific security groups selected and defined. Important: If the organization doesn't actively use this feature it is recommended to keep it Disabled. To audit using PowerShell: 1. Inspect the results of the Get-CISFabricTenantSettings function from the section overview. 2. Locate the settingName ServicePrincipalAccessGlobalAPIs in the output. 3. Verify that the properties adhere to one of the following compliant configurations: o enabled is set to false. o enabled is set to true AND enabledSecurityGroups contains at least one security group. 4. If neither condition is met, the setting is non-compliant. Note: If the Specific security groups setting is not enabled then the enabledSecurityGroups property does not appear in the output.",
+ "AdditionalInformation": "",
+ "DefaultValue": "Disabled for the entire organization",
+ "References": "https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer"
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/m365/prowler_threatscore_m365.json b/prowler/compliance/m365/prowler_threatscore_m365.json
index 286a4fff39..f5a6cd1cd8 100644
--- a/prowler/compliance/m365/prowler_threatscore_m365.json
+++ b/prowler/compliance/m365/prowler_threatscore_m365.json
@@ -819,6 +819,14 @@
"LevelOfRisk": 4,
"Weight": 100
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "entra_admin_users_sign_in_frequency_enabled",
+ "ConfigKey": "sign_in_frequency",
+ "Operator": "lte",
+ "Value": 4
+ }
]
},
{
@@ -964,6 +972,68 @@
"LevelOfRisk": 2,
"Weight": 8
}
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "defender_malware_policy_comprehensive_attachments_filter_applied",
+ "ConfigKey": "recommended_blocked_file_types",
+ "Operator": "superset",
+ "Value": [
+ "ace",
+ "ani",
+ "apk",
+ "app",
+ "appx",
+ "arj",
+ "bat",
+ "cab",
+ "cmd",
+ "com",
+ "deb",
+ "dex",
+ "dll",
+ "docm",
+ "elf",
+ "exe",
+ "hta",
+ "img",
+ "iso",
+ "jar",
+ "jnlp",
+ "kext",
+ "lha",
+ "lib",
+ "library",
+ "lnk",
+ "lzh",
+ "macho",
+ "msc",
+ "msi",
+ "msix",
+ "msp",
+ "mst",
+ "pif",
+ "ppa",
+ "ppam",
+ "reg",
+ "rev",
+ "scf",
+ "scr",
+ "sct",
+ "sys",
+ "uif",
+ "vb",
+ "vbe",
+ "vbs",
+ "vxd",
+ "wsc",
+ "wsf",
+ "wsh",
+ "xll",
+ "xz",
+ "z"
+ ]
+ }
]
},
{
diff --git a/tests/lib/outputs/compliance/ccc/__init__.py b/prowler/compliance/okta/__init__.py
similarity index 100%
rename from tests/lib/outputs/compliance/ccc/__init__.py
rename to prowler/compliance/okta/__init__.py
diff --git a/prowler/compliance/okta/okta_idaas_stig_v1r2_okta.json b/prowler/compliance/okta/okta_idaas_stig_v1r2_okta.json
new file mode 100644
index 0000000000..66747cdba7
--- /dev/null
+++ b/prowler/compliance/okta/okta_idaas_stig_v1r2_okta.json
@@ -0,0 +1,670 @@
+{
+ "Framework": "Okta-IDaaS-STIG",
+ "Name": "DISA Okta Identity as a Service (IDaaS) STIG V1R2",
+ "Version": "1R2",
+ "Provider": "Okta",
+ "Description": "Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) for Okta Identity as a Service (IDaaS), Version 1 Release 2 (Benchmark Date: 05 Jan 2026).",
+ "Requirements": [
+ {
+ "Id": "OKTA-APP-000020",
+ "Name": "Okta must log out a session after a 15-minute period of inactivity.",
+ "Description": "A session timeout lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application session prior to vacating the vicinity, applications must be able to identify when a user's application session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. This is typically at the operating system level and results in a system lock. However, it may be at the application level where the application interface window is secured instead. Satisfies: SRG-APP-000003, SRG-APP-000190",
+ "Checks": [
+ "signon_global_session_idle_timeout_15min"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273186r1098825_rule",
+ "StigID": "OKTA-APP-000020",
+ "CCI": [
+ "CCI-000057",
+ "CCI-001133"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Global Session Policy. 2. In the Default Policy, verify a rule is configured at Priority 1 that is not named \"Default Rule\". 3. Click the edit icon next to the Priority 1 rule. 4. Verify the \"Maximum Okta global session idle time\" is set to 15 minutes. If \"Maximum Okta global session idle time\" is not set to 15 minutes, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Global Session Policy. 2. Select the Default Policy. 3. In the Rules table, make these updates: - Click \"Add rule\". - Set \"Maximum Okta global session idle time\" to 15 minutes."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "signon_global_session_idle_timeout_15min",
+ "ConfigKey": "okta_max_session_idle_minutes",
+ "Operator": "lte",
+ "Value": 15
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000025",
+ "Name": "The Okta Admin Console must log out a session after a 15-minute period of inactivity.",
+ "Description": "A session timeout lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application session prior to vacating the vicinity, applications must be able to identify when a user's application session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. This is typically at the operating system level and results in a system lock. However, it may be at the application level where the application interface window is secured instead.",
+ "Checks": [
+ "application_admin_console_session_idle_timeout_15min"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273187r1098828_rule",
+ "StigID": "OKTA-APP-000025",
+ "CCI": [
+ "CCI-000057"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Applications >> Applications >> Okta Admin Console. 2. In the Sign On tab, under \"Okta Admin Console session\", verify the \"Maximum app session idle time\" is set to 15 minutes. If the \"Maximum app session idle time\" is not set to 15 minutes, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Applications >> Applications >> Okta Admin Console. 2. In the Sign On tab, under \"Okta Admin Console session\", set the \"Maximum app session idle time\" to 15 minutes."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "application_admin_console_session_idle_timeout_15min",
+ "ConfigKey": "okta_admin_console_idle_timeout_max_minutes",
+ "Operator": "lte",
+ "Value": 15
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000090",
+ "Name": "Okta must automatically disable accounts after a 35-day period of account inactivity.",
+ "Description": "Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications must track periods of user inactivity and disable accounts after 35 days of inactivity. Such a process greatly reduces the risk that accounts will be hijacked, leading to a data compromise. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality. This policy does not apply to emergency accounts or infrequently used accounts. Infrequently used accounts are local login administrator accounts used by system administrators when network or normal login/access is not available. Emergency accounts are administrator accounts created in response to crisis situations. Satisfies: SRG-APP-000025, SRG-APP-000163, SRG-APP-000700",
+ "Checks": [
+ "user_inactivity_automation_35d_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273188r1098831_rule",
+ "StigID": "OKTA-APP-000090",
+ "CCI": [
+ "CCI-000017",
+ "CCI-000795",
+ "CCI-003627"
+ ],
+ "CheckText": "If Okta Services rely on external directory services for user sourcing, this is not applicable, and the connected directory services must perform this function. Go to Workflows >> Automations and verify that an Automation has been created to disable accounts after 35 days of inactivity. If the Okta configuration does not automatically disable accounts after a 35-day period of account inactivity, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Workflow >> Automations and select \"Add Automation\". 2. Create a name for the Automation (e.g., \"User Inactivity\"). 3. Click \"Add Condition\" and select \"User Inactivity in Okta\". 4. In the duration field, enter 35 days and click \"Save\". 5 Click the edit button next to \"Select Schedule\". 6. Configure the \"Schedule\" field for \"Run Daily\" and set the \"Time\" field to an organizationally defined time to run this automation. Click \"Save\". 7. Click the edit button next to \"Select group membership\". 8. In the \"Applies to\" field, select the group \"Everyone\" by typing it into the field. Click \"Save\". 9. Click \"Add Action\" and select \"Change User lifecycle state in Okta\". 10. In the \"Change user state to\" field, select \"Suspended\" and click \"Save\". 11. Click the \"Inactive\" button near the top of the section screen and select \"Activate\"."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "user_inactivity_automation_35d_enabled",
+ "ConfigKey": "okta_user_inactivity_max_days",
+ "Operator": "lte",
+ "Value": 35
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000170",
+ "Name": "Okta must enforce the limit of three consecutive invalid login attempts by a user during a 15-minute time period.",
+ "Description": "By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. Satisfies: SRG-APP-000065, SRG-APP-000345",
+ "Checks": [
+ "authenticator_password_lockout_threshold_3"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273189r1098834_rule",
+ "StigID": "OKTA-APP-000170",
+ "CCI": [
+ "CCI-000044",
+ "CCI-002238"
+ ],
+ "CheckText": "If Okta Services rely on external directory services for user sourcing, this check is not applicable, and the connected directory services must perform this function. From the Admin Console: 1. Go to Security >> Authenticators. 2. Click the \"Actions\" button next to \"Password\" and select \"Edit\". 3. For each Password Policy, verify the \"Lock Out\" section has the following values: - \"Lock out after 3 unsuccessful attempts\" is checked. - The value is set to \"3\". If Okta Services are not configured to automatically lock user accounts after three consecutive invalid login attempts, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authenticators. 2. Click the \"Actions\" button next to \"Password\" and select \"Edit\". 3. For each Password Policy, ensure the \"Lock Out\" section has the following values: - \"Lock out after 3 unsuccessful attempts\" is checked. - The value is set to \"3\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000180",
+ "Name": "The Okta Dashboard application must be configured to allow authentication only via non-phishable authenticators.",
+ "Description": "Requiring the use of non-phishable authenticators protects against brute force/password dictionary attacks. This provides a better level of security while removing the need to lock out accounts after three attempts in 15 minutes.",
+ "Checks": [
+ "application_dashboard_phishing_resistant_authentication"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273190r1099763_rule",
+ "StigID": "OKTA-APP-000180",
+ "CCI": [
+ "CCI-000044"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Dashboard\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"Possession factor constraints are\" section, verify the \"Phishing resistant\" box is checked. This will ensure that only phishing-resistant factors are used to access the Okta Dashboard. If in the \"Possession factor constraints are\" section the \"Phishing resistant\" box is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Dashboard\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"Possession factor constraints are\" section, ensure the \"Phishing resistant\" box is checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000190",
+ "Name": "The Okta Admin Console application must be configured to allow authentication only via non-phishable authenticators.",
+ "Description": "Requiring the use of non-phishable authenticators protects against brute force/password dictionary attacks. This provides a better level of security while removing the need to lock out accounts after three attempts in 15 minutes.",
+ "Checks": [
+ "application_admin_console_phishing_resistant_authentication"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273191r1099764_rule",
+ "StigID": "OKTA-APP-000190",
+ "CCI": [
+ "CCI-000044"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Admin Console\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"Possession factor constraints are\" section, verify the \"Phishing resistant\" box is checked. This will ensure that only phishing-resistant factors are used to access the Okta Dashboard. If in the \"Possession factor constraints are\" section the \"Phishing resistant\" box is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Admin Console\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"Possession factor constraints are\" section, ensure the \"Phishing resistant\" box is checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000200",
+ "Name": "Okta must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the application.",
+ "Description": "Display of the DOD-approved use notification before granting access to the application ensures that privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for applications that can accommodate banners of 1300 characters: \"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \"I've read & consent to terms in IS user agreem't.\" Satisfies: SRG-APP-000068, SRG-APP-000069, SRG-APP-000070",
+ "Checks": [
+ "signon_dod_warning_banner_configured"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273192r1098843_rule",
+ "StigID": "OKTA-APP-000200",
+ "CCI": [
+ "CCI-000048",
+ "CCI-000050",
+ "CCI-001384",
+ "CCI-001385",
+ "CCI-001386",
+ "CCI-001387",
+ "CCI-001388"
+ ],
+ "CheckText": "Attempt to log in to the Okta tenant and verify the DOD-approved warning banner is in place. If the required warning banner is not present and complete, this is a finding.",
+ "FixText": "Follow the supplemental instructions in the \"Okta DOD Warning Banner Configuration Guide\" provided with this STIG package."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000560",
+ "Name": "The Okta Admin Console application must be configured to use multifactor authentication.",
+ "Description": "Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) something a user is (e.g., biometric). A privileged account is defined as an information system account with authorizations of a privileged user. Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). Satisfies: SRG-APP-000149, SRG-APP-000154",
+ "Checks": [
+ "application_admin_console_mfa_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT I (High)",
+ "Severity": "high",
+ "RuleID": "SV-273193r1098846_rule",
+ "StigID": "OKTA-APP-000560",
+ "CCI": [
+ "CCI-000765",
+ "CCI-004046"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Admin Console\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"User must authenticate with\" field, verify that either \"Password/IdP + Another factor\" or \"Any 2 factor types\" is selected. If either of these settings is incorrect, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Admin Console\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"User must authenticate with\" field, select either \"Password/IdP + Another factor\" or \"Any 2 factor types\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000570",
+ "Name": "The Okta Dashboard application must be configured to use multifactor authentication.",
+ "Description": "To ensure accountability and prevent unauthenticated access, nonprivileged users must use multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses two or more factors to achieve authentication. Factors include: (i) Something you know (e.g., password/PIN); (ii) Something you have (e.g., cryptographic identification device, token); or (iii) Something you are (e.g., biometric). A nonprivileged account is any information system account with authorizations of a nonprivileged user. Network access is any access to an application by a user (or process acting on behalf of a user) where the access is obtained through a network connection. Applications integrating with the DOD Active Directory and using the DOD CAC are examples of compliant multifactor authentication solutions. Satisfies: SRG-APP-000150, SRG-APP-000155",
+ "Checks": [
+ "application_dashboard_mfa_required"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT I (High)",
+ "Severity": "high",
+ "RuleID": "SV-273194r1098849_rule",
+ "StigID": "OKTA-APP-000570",
+ "CCI": [
+ "CCI-000766",
+ "CCI-004046"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Dashboard\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"User must authenticate with\" field, verify that either \"Password/IdP + Another factor\" or \"Any 2 factor types\" is selected. If either of these settings is incorrect, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authentication Policies. 2. Click the \"Okta Dashboard\" policy. 3. Click the \"Actions\" button next to the top rule and select \"Edit\". 4. In the \"User must authenticate with\" field, select either \"Password/IdP + Another factor\" or \"Any 2 factor types\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000650",
+ "Name": "Okta must enforce a minimum 15-character password length.",
+ "Description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.",
+ "Checks": [
+ "authenticator_password_minimum_length_15"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273195r1098852_rule",
+ "StigID": "OKTA-APP-000650",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify the \"Minimum Length\" field is set to at least \"15\" characters. If any policy is not set to at least \"15\", this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set the \"Minimum Length\" field to at least \"15\" characters."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000670",
+ "Name": "Okta must enforce password complexity by requiring that at least one uppercase character be used.",
+ "Description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised.",
+ "Checks": [
+ "authenticator_password_complexity_uppercase"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273196r1098855_rule",
+ "StigID": "OKTA-APP-000670",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Upper case letter\" is checked. For each policy, if \"Upper case letter\" is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Upper case letter\" to checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000680",
+ "Name": "Okta must enforce password complexity by requiring that at least one lowercase character be used.",
+ "Description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.",
+ "Checks": [
+ "authenticator_password_complexity_lowercase"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273197r1098858_rule",
+ "StigID": "OKTA-APP-000680",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Lower case letter\" is checked. For each policy, if \"Lower case letter\" is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Lower case letter\" to checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000690",
+ "Name": "Okta must enforce password complexity by requiring that at least one numeric character be used.",
+ "Description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.",
+ "Checks": [
+ "authenticator_password_complexity_number"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273198r1098861_rule",
+ "StigID": "OKTA-APP-000690",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Number (0-9)\" is checked. For each policy, if \"Number (0-9)\" is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Number (0-9)\" to checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000700",
+ "Name": "Okta must enforce password complexity by requiring that at least one special character be used.",
+ "Description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Special characters are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.",
+ "Checks": [
+ "authenticator_password_complexity_symbol"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273199r1098864_rule",
+ "StigID": "OKTA-APP-000700",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Symbol (e.g., !@#$%^&*)\" is checked. For each policy, if \"Symbol (e.g., !@#$%^&*)\" is not checked, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Symbol (e.g., !@#$%^&*)\" to checked."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000740",
+ "Name": "Okta must enforce 24 hours/one day as the minimum password lifetime.",
+ "Description": "Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. Restricting this setting limits the user's ability to change their password. Passwords must be changed at specific policy-based intervals; however, if the application allows the user to immediately and continually change their password, it could be changed repeatedly in a short period of time to defeat the organization's policy regarding password reuse. Satisfies: SRG-APP-000173, SRG-APP-000870",
+ "Checks": [
+ "authenticator_password_minimum_age_24h"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273200r1098867_rule",
+ "StigID": "OKTA-APP-000740",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Minimum password age is XX hours\" is set to at least \"24\". For each policy, if \"Minimum password age is XX hours\" is not set to at least \"24\", this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Minimum password age is XX hours\" to at least \"24\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-000745",
+ "Name": "Okta must enforce a 60-day maximum password lifetime restriction.",
+ "Description": "Any password, no matter how complex, can eventually be cracked. Therefore, passwords must be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the system and/or application passwords could be compromised. This requirement does not include emergency administration accounts, which are meant for access to the application in case of failure. These accounts are not required to have maximum password lifetime restrictions.",
+ "Checks": [
+ "authenticator_password_maximum_age_60d"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273201r1098870_rule",
+ "StigID": "OKTA-APP-000745",
+ "CCI": [
+ "CCI-004066"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy, verify \"Password expires after XX days\" is set to \"60\". For each policy, if \"Password expires after XX days\" is not set to \"60\", this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Password expires after XX days\" to \"60\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001430",
+ "Name": "Okta must off-load audit records onto a central log server.",
+ "Description": "Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Satisfies: SRG-APP-000358, SRG-APP-000080, SRG-APP-000125",
+ "Checks": [
+ "systemlog_streaming_enabled"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT I (High)",
+ "Severity": "high",
+ "RuleID": "SV-273202r1099766_rule",
+ "StigID": "OKTA-APP-001430",
+ "CCI": [
+ "CCI-001851",
+ "CCI-000166",
+ "CCI-001348"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Reports >> Log Streaming. 2. Verify that a Log Stream connection is configured and active. Alternately, interview the information system security manager (ISSM) and verify that an external Security Information and Event Management (SIEM) system is pulling Okta logs via an Application Programming Interface (API). If either of these is not configured, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Reports >> Log Streaming. 2. Select either \"AWS EventBridge\" or \"Splunk Cloud\" and click \"Next\". 3. Complete the necessary fields and click \"Save\". If Log Streaming is not an option because the SIEM required is not an option, customers can use the Okta Log API to export system logs in real time."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001665",
+ "Name": "Okta must be configured to limit the global session lifetime to 18 hours.",
+ "Description": "Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user reauthenticate. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances. (i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) When the execution of privileged functions occurs; (v) After a fixed period of time; or (vi) Periodically. Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation and role changes.",
+ "Checks": [
+ "signon_global_session_lifetime_18h"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273203r1099958_rule",
+ "StigID": "OKTA-APP-001665",
+ "CCI": [
+ "CCI-002038"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Global Session Policy. 2. In the Default Policy, verify a rule is configured at Priority 1 that is not named \"Default Rule\". 3. Click the \"Edit\" icon next to the Priority 1 rule. 4. Verify \"Maximum Okta global session lifetime\" is set to 18 hours. If the above is not set, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Global Session Policy. 2. Select the Default Policy. 3. In the Rules table, make these updates: - Click \"Add rule\". - Set \"Maximum Okta global session lifetime\" to 18 hours."
+ }
+ ],
+ "ConfigRequirements": [
+ {
+ "Check": "signon_global_session_lifetime_18h",
+ "ConfigKey": "okta_max_session_lifetime_minutes",
+ "Operator": "lte",
+ "Value": 1080
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001670",
+ "Name": "Okta must be configured to accept Personal Identity Verification (PIV) credentials.",
+ "Description": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary component of layered protection for national security systems. Satisfies: SRG-APP-000391, SRG-APP-000402, SRG-APP-000403",
+ "Checks": [
+ "authenticator_smart_card_active"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273204r1098879_rule",
+ "StigID": "OKTA-APP-001670",
+ "CCI": [
+ "CCI-001953",
+ "CCI-002009",
+ "CCI-002010"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authenticators. 2. Verify that \"Smart Card Authenticator\" is listed and has \"Status\" listed as \"Active\". If \"Smart Card Authenticator\" is not listed or is not listed as \"Active\", this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authenticators. 2. In the \"Setup\" tab, click \"Add authenticator\". 3. Select the configured Smart Card Identity Provider and finish configuration."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001700",
+ "Name": "The Okta Verify application must be configured to connect only to FIPS-compliant devices.",
+ "Description": "Without device-to-device authentication, communications with malicious devices may be established. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. Currently, DOD requires the use of AES for bidirectional authentication because it is the only FIPS-validated AES cipher block algorithm. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of authentication claims may be made by services separate from the services acting on those decisions. In such situations, it is necessary to provide authentication decisions (as opposed to the actual authenticators) to the services that need to act on those decisions. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network; the internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to apply the requirement only to those limited number (and type) of devices that truly need to support this capability.",
+ "Checks": [
+ "authenticator_okta_verify_fips_compliant"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273205r1098882_rule",
+ "StigID": "OKTA-APP-001700",
+ "CCI": [
+ "CCI-001967"
+ ],
+ "CheckText": "From the Admin Console: 1. Go to Security >> Authenticators. 2. From the \"Setup\" tab, select \"Edit Okta Verify\". 3. Review the \"FIPS Compliance\" field. If FIPS-compliant authentication is not enabled, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Authenticators. 2. From the \"Setup\" tab, select \"Edit Okta Verify\". 3. In the \"FIPS Compliance\" field, choose whether users enrolling in Okta Verify can use FIPS-compliant devices only or any device. 4. Click \"Save\" after making any changes."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001710",
+ "Name": "Okta must be configured to disable persistent global session cookies.",
+ "Description": "If cached authentication information is out of date, the validity of the authentication information may be questionable. Satisfies: SRG-APP-000400, SRG-APP-000157",
+ "Checks": [
+ "signon_global_session_cookies_not_persistent"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273206r1098885_rule",
+ "StigID": "OKTA-APP-001710",
+ "CCI": [
+ "CCI-002007",
+ "CCI-001942"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Global Session Policy. 2. In the Default Policy, verify a rule is configured at Priority 1 that is not named \"Default Rule\". 3. Click the \"Edit\" icon next to the Priority 1 rule. 4. Verify \"Okta global session cookies persist across browser sessions\" is set to \"Disabled\". If the above it not set, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Global Session Policy. 2. Select the Default Policy. 3. In the \"Rules\" table, make these updates: - Click \"Add rule\". - Set \"Okta global session cookies persist across browser sessions\" to Disable."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-001920",
+ "Name": "Okta must be configured to use only DOD-approved certificate authorities.",
+ "Description": "Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not DOD approved, trust of this CA has not been established. The DOD will accept only PKI certificates obtained from a DOD-approved internal or external CA. Reliance on CAs for the establishment of secure sessions includes, for example, the use of Transport Layer Security (TLS) certificates. This requirement focuses on communications protection for the application session rather than for the network packet. This requirement applies to applications that use communications sessions. This includes, but is not limited to, web-based applications and Service-Oriented Architectures (SOA). Satisfies: SRG-APP-000427, SRG-APP-000910",
+ "Checks": [
+ "idp_smart_card_dod_approved_ca"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273207r1098888_rule",
+ "StigID": "OKTA-APP-001920",
+ "CCI": [
+ "CCI-002470",
+ "CCI-004909"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Identity Providers (IdPs). 2. Review the list of IdPs with \"Type\" as \"Smart Card\". If the IdP is not listed as \"Active\", this is a finding. 3. Select Actions >> Configure. 4. Under \"Certificate chain\", verify the certificate is from a DOD-approved CA. If the certificate is not from a DOD-approved CA, this is a finding.",
+ "FixText": "From the Admin Console: 1. Go to Security >> Identity Providers. 2. Click \"Add identity provider.\" 3. Click \"Smart Card IdP\". Click \"Next\". 4. Enter the name of the identity provider. 5. Build a certificate chain: - Click \"Browse\" to open a file explorer. Select the certificate file to add and click \"Open\". - To add another certificate, click \"Add Another\" and repeat step 1. - Click \"Build certificate chain\". On success, the chain and its certificates are shown. If the build failed, correct any issues and try again. - Click \"Reset certificate chain\" if replacing the current chain with a new one. 6. In \"IdP username\", select the \"idpuser.subjectAltNameUpn\" attribute. This is the attribute that stores the Electronic Data Interchange Personnel Identifier (EDIPI) on the CAC. 7. In the \"Match Against\" field, select the Okta Profile Attribute in which the EDIPI is to be stored."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-002980",
+ "Name": "Okta must validate passwords against a list of commonly used, expected, or compromised passwords.",
+ "Description": "Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.",
+ "Checks": [
+ "authenticator_password_common_password_check"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273208r1099769_rule",
+ "StigID": "OKTA-APP-002980",
+ "CCI": [
+ "CCI-004058"
+ ],
+ "CheckText": "From the Admin Console: 1. Navigate to Security >> Authenticators. 2. Click the \"Actions\" button next to the Password authenticator and select \"Edit\". 3. Under the \"Password Settings\" section, verify the \"Common Password Check\" box is checked. If \"Common Password Check\" is not selected, this is a finding.",
+ "FixText": "From the Admin Console: 1. Navigate to Security >> Authenticators. 2. Click the \"Actions\" button next to the Password authenticator and select \"Edit\". 3. Under the \"Password Settings\" section, check the \"Common Password Check\" box."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003010",
+ "Name": "Okta must prohibit password reuse for a minimum of five generations.",
+ "Description": "Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.",
+ "Checks": [
+ "authenticator_password_history_5"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-273209r1098894_rule",
+ "StigID": "OKTA-APP-003010",
+ "CCI": [
+ "CCI-004061"
+ ],
+ "CheckText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password row\" and select \"Edit\". 3. For each listed policy, verify \"Enforce password history for last XX passwords\" is set to \"5\". If any policy is not set to at least \"5\", this is a finding.",
+ "FixText": "From the Admin Console: 1. Select Security >> Authenticators. 2. Click the \"Actions\" button next to the \"Password\" row and select \"Edit\". 3. For each listed policy: - Click \"Edit\". - Set \"Enforce password history for last XX passwords\" to \"5\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003240",
+ "Name": "Okta API tokens must be configured with Network Zones to restrict authorization from known networks.",
+ "Description": "An access token is a piece of data that represents the authorization granted to a user or NPE to access specific systems or information resources. Access tokens enable controlled access to services and resources. Properly managing the lifecycle of access tokens, including their issuance, validation, and revocation, is crucial to maintaining confidentiality of data and systems. Restricting token validity to a specific audience, e.g., an application or security domain, and restricting token validity lifetimes are important practices. Access tokens are revoked or invalidated if they are compromised, lost, or are no longer needed to mitigate the risks associated with stolen or misused tokens. API tokens have the potential to be replicated or stolen (just like a password). Because of this, it is important to only allow API tokens to authenticate from known IP ranges as this limits an adversary's ability to use a token to gain access.",
+ "Checks": [
+ "apitoken_restricted_to_network_zone"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-279689r1155066_rule",
+ "StigID": "OKTA-APP-003240",
+ "CCI": [
+ "CCI-005165",
+ "CCI-000366"
+ ],
+ "CheckText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"API\" item. 2. Click the \"Tokens\" tab. 3. For each token listed, click the token name link. 4. In the \"Security\" section, verify the \"Token can be used from\" setting is mapped to a known network zone for the application calling the API. If a network zone for each API access token is not defined, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"API\" item. 2. Click the \"Tokens\" tab. 3. For each token listed, click the token name link. 4. In the \"Security\" section, click \"Edit\". 5. Set the \"Token can be used from\" setting to the known network zone for the application calling the API. 6. Click \"Save\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003241",
+ "Name": "Okta API tokens must be created under new dedicated user accounts.",
+ "Description": "An access token is a piece of data that represents the authorization granted to a user or NPE to access specific systems or information resources. Access tokens enable controlled access to services and resources. Properly managing the lifecycle of access tokens, including their issuance, validation, and revocation, is crucial to maintaining confidentiality of data and systems. Restricting token validity to a specific audience, e.g., an application or security domain, and restricting token validity lifetimes are important practices. Access tokens are revoked or invalidated if they are compromised, lost, or are no longer needed to mitigate the risks associated with stolen or misused tokens. When API tokens are created, they inherit the permissions of the user that created them. Therefore, API tokens should only be created from dedicated accounts and permissions must be constrained to least privilege for that dedicated user account and token. No API tokens should be created using a Super Admin account.",
+ "Checks": [
+ "apitoken_not_super_admin"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-279690r1155069_rule",
+ "StigID": "OKTA-APP-003241",
+ "CCI": [
+ "CCI-005165",
+ "CCI-000366"
+ ],
+ "CheckText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"API\" item. 2. Click the \"Tokens\" tab. 3. For each token listed, verify that the Role listed is not \"Super Admin\", and that the account has been specifically created for that token. 4. Click the account name to be token to the user profile for that user. 5. Verify the user only has an administrator role (standard or customer) applied that is correctly scoped as required and documented in the Okta Access Control policy. If the token is using a Super Administrator account, or one that is not properly scoped per the Access Control policy, this is a finding. Note: If a Super Admin token is required for system operation, then this permanent finding.",
+ "FixText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"API\" item. 2. Click the \"Tokens\" tab. 3. For each token listed that has \"Super Admin\" or an improperly scoped Admin account, delete the token and create a new one with the appropriately scoped permissions. 4. Verify the application performing the API calls with the new token has been updated."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003242",
+ "Name": "The Okta Global Session policy must be configured to allow or deny IP based access in accordance with the Access Control policy for Okta.",
+ "Description": "To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access Control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. The Okta Global Session Policy is applied at the organization level and before any application-specific authentication policies are processed. The Okta authorization package should contain an access control policy that defines IP ranges from which to either allow or deny access. This list (either as an explicit allow or explicit deny) can be implemented in the Global Session Policy.",
+ "Checks": [
+ "signon_global_session_policy_network_zone_enforced"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-279691r1155072_rule",
+ "StigID": "OKTA-APP-003242",
+ "CCI": [
+ "CCI-000213"
+ ],
+ "CheckText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"Global Session Policy\" item. 2. In the \"Policy Settings\" section, verify the \"IF User's IP is\" setting is correctly set to either allow or deny based on the organization defined policy. If the Okta Global Session Policy is not configured to restrict access to specific IP ranges, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"Global Session Policy\" item. 2. In the Policy Settings section, configure the \"IF User's IP is\" setting to correctly set the appropriate network to either allow or deny based on the Access Control Policy."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003243",
+ "Name": "Okta must be configured with Network Zones defined to block anonymized proxies according to organizationally defined policy.",
+ "Description": "A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow control regulates where information is allowed to travel within a system and between interconnected systems. The flow of all application information must be monitored and controlled so it does not introduce any unacceptable risk to the systems or data. Application-specific examples of enforcement occurs in systems that employ rule sets or establish configuration settings that restrict information system services, or provide a message filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy. Working with the organizational CSSP, the ISSM should obtain a list of known anonymizer proxies that exist on the commercial internet. If this is not available from the CSSP, then the Okta-provided \"Enhanced dynamic zone blocklist\" should be activated.",
+ "Checks": [
+ "network_zone_block_anonymized_proxies"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-279692r1155075_rule",
+ "StigID": "OKTA-APP-003243",
+ "CCI": [
+ "CCI-001414"
+ ],
+ "CheckText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"Networks' item. 2. If the CSSP has provided a list of anonymizers to block, verify the \"IP Block list\" is configured with them. a. Click the pencil icon next to IP Block list. b. Verify the \"Gateway IPs\" section contains all of the IP ranges in the provided list. 3. If the CSSP is not able to provide a list, then implement the Okta managed list. a. Verify the \"Enhanced dynamic zone blocklist\" is set to \"Active\". If Network Zones are not configured to block anonymous proxies, this is a finding.",
+ "FixText": "From the Admin Console: 1. Select the \"Security\" menu, and then click the \"Networks\" item. 2. If the CSSP has provided a list of anonymizers to block, add the IP ranges to the \"IP Block list\". a. Click the pencil icon next to IP Block list. b. Add the IP ranges to the \"Gateway IPs\" section and click \"Save\". 3. If the CSSP is not able to provide a list, then implement the Okta managed list. a. Set the \"Enhanced dynamic zone blocklist\" to \"Active\"."
+ }
+ ]
+ },
+ {
+ "Id": "OKTA-APP-003244",
+ "Name": "For each application integrated with Okta, network zones must be defined in its authentication policy.",
+ "Description": "A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow control regulates where information is allowed to travel within a system and between interconnected systems. The flow of all application information must be monitored and controlled so it does not introduce any unacceptable risk to the systems or data. Application-specific examples of enforcement occurs in systems that employ rule sets or establish configuration settings that restrict information system services, or provide a message filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy. Each application in Okta should have a well defined access control policy that takes into account the end user network. This should be documented in the Access Control policy for each application. As an example, access to an application may be restricted to a specific location by policy. In this case, a network defining that specific location should be created.",
+ "Checks": [
+ "application_authentication_policy_network_zone_enforced"
+ ],
+ "Attributes": [
+ {
+ "Section": "CAT II (Medium)",
+ "Severity": "medium",
+ "RuleID": "SV-279693r1155078_rule",
+ "StigID": "OKTA-APP-003244",
+ "CCI": [
+ "CCI-001414"
+ ],
+ "CheckText": "For each application integrated into Okta: 1. From the Admin console, open the \"Security\" menu, and then select \"Networks\". 2. Verify the list of networks includes all necessary allow or block lists. If any application is not configured with network zones, this is a finding.",
+ "FixText": "For each application, starting at the admin console: 1. Open the \"Applications\" group from the Menu, and then click the \"Applications\" menu item. 2. Click the application name. 3. Click the \"Sign On\" tab. 4. Scroll to the \"User Authentication\" section, and then click \"Edit\". 5. Select the appropriate Authentication policy from the pull down, and then click \"Save\". 6. Click \"View Policy Details\". 7. For each nondefault rule: a. Select \"Edit\" from the Actions menu. b. In the \"IF\" section, verify the \"User is\" setting has the appropriate allow or deny range has been selected based on the Access Control policy for the application. c. Scroll down to the bottom and click \"Save\". 8. For the Catch-All rule: a. Select \"Edit\" from the Actions menu. b. Scroll down to the \"Then\" section. c. For the \"Access is\" setting, select \"Denied\", and then click \"Save\"."
+ }
+ ]
+ }
+ ]
+}
diff --git a/prowler/compliance/oraclecloud/cis_3.1_oraclecloud.json b/prowler/compliance/oraclecloud/cis_3.1_oraclecloud.json
index ceca68d124..8140dca6cc 100644
--- a/prowler/compliance/oraclecloud/cis_3.1_oraclecloud.json
+++ b/prowler/compliance/oraclecloud/cis_3.1_oraclecloud.json
@@ -302,7 +302,9 @@
{
"Id": "1.15",
"Description": "Ensure storage service-level admins cannot delete resources they manage",
- "Checks": [],
+ "Checks": [
+ "identity_storage_service_level_admins_scoped"
+ ],
"Attributes": [
{
"Section": "1. Identity and Access Management",
diff --git a/prowler/compliance/oraclecloud/csa_ccm_4.0_oraclecloud.json b/prowler/compliance/oraclecloud/csa_ccm_4.0_oraclecloud.json
deleted file mode 100644
index 300e32788d..0000000000
--- a/prowler/compliance/oraclecloud/csa_ccm_4.0_oraclecloud.json
+++ /dev/null
@@ -1,7307 +0,0 @@
-{
- "Framework": "CSA-CCM",
- "Name": "CSA Cloud Controls Matrix (CCM) v4.0.13",
- "Version": "4.0",
- "Provider": "OracleCloud",
- "Description": "The Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing, composed of 197 control objectives structured in 17 domains covering all key aspects of cloud technology. The CCM can be used as a tool for the systematic assessment of a cloud implementation, and provides guidance on which security controls should be implemented by which actor within the cloud supply chain.",
- "Requirements": [
- {
- "Id": "A&A-02",
- "Description": "Conduct independent audit and assurance assessments according to relevant standards at least annually.",
- "Name": "Independent Assessments",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC4.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AAC-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.2",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.2.1",
- "27002: 18.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.35",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-2",
- "CA-2(1)",
- "CA-2(2)",
- "CA-7",
- "CA-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "A&A-04",
- "Description": "Verify compliance with all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit.",
- "Name": "Requirements Compliance",
- "Attributes": [
- {
- "Section": "Audit & Assurance",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01",
- "GRM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "AS1.1",
- "AS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.18.2.2",
- "27002: 18.2.2",
- "27001: A.18.2.3",
- "27002: 18.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.3.2",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34",
- "27001: A.5.36"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-3",
- "DE.DP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-01"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "AIS-04",
- "Description": "Define and implement a SDLC process for application design, development, deployment, and operation in accordance with security requirements defined by the organization.",
- "Name": "Secure Application Design and Development",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27017: 14.1.1",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.14.2.1",
- "27002: 14.2.1",
- "27017: 14.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.8",
- "27001: A.8.25",
- "27001: A.8.26",
- "27001: A.8.28"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PL-8",
- "PL-8(1)",
- "SA-3",
- "SA-3(1)",
- "SA-4",
- "SA-4(2)",
- "SA-4(3)",
- "SA-4(8)",
- "SA-4(9)",
- "SA-5",
- "SA-8",
- "SA-8(1)-(7)",
- "SA-8(9)-(13)",
- "SA-8(15)-(20)",
- "SA-8(22)",
- "SA-8(24)-(28)",
- "SA-8(30)-(33)",
- "SA-17",
- "SA-17(1)-(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-6",
- "PR.DS-7",
- "PR.IP-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1",
- "6.2.3",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "AIS-05",
- "Description": "Implement a testing strategy, including criteria for acceptance of new information systems, upgrades and new versions, which provides application security assurance and maintains compliance while enabling organizational speed of delivery goals. Automate when applicable and possible.",
- "Name": "Automated Application Security Testing",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "AIS-01",
- "AIS-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.12",
- "16.13"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.3",
- "SD2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.8",
- "27001: A.14.2.9",
- "27001: A.12.1.2",
- "27002: 12.1.2",
- "27001: A.14.1.1",
- "27002: 14.1.1",
- "27001: A.14.2.2",
- "27002: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.25",
- "27001: A.8.29",
- "27001: A.8.32",
- "27002: 8.25 (e)",
- "27002: 8.32 (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SA-11",
- "SA-11(1)-(9)",
- "SI-6",
- "SI-6(2)",
- "SI-6(3)",
- "SI-10",
- "SI-10(1)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.IP-12",
- "DE.CM-8"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "PR.PS-01",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A.3.2.2",
- "A.3.2.2.1",
- "6.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.4",
- "6.4.1",
- "6.4.2",
- "6.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "AIS-07",
- "Description": "Define and implement a process to remediate application security vulnerabilities, automating remediation when possible.",
- "Name": "Application Vulnerability Remediation",
- "Attributes": [
- {
- "Section": "Application & Interface Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1",
- "CC7.4",
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.2",
- "16.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27001: A.12.6.1",
- "27002: 12.6.1",
- "27017: 12.6.1",
- "27018: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.26",
- "27001: A.8.8",
- "27002: 5.26 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-2",
- "SI-2(2)-(6)",
- "SA-11",
- "SA-11(2)",
- "SA-15",
- "SA-15(1)-(3)",
- "SA-15(5)-(8)",
- "SA-15(10)-(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.IP-12",
- "DE.CM-8",
- "RS.AN-5",
- "RS.MI-3",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.2",
- "6.5",
- "6.5.1-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "11.3.1",
- "11.3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "BCR-08",
- "Description": "Periodically backup data stored in the cloud. Ensure the confidentiality, integrity and availability of the backup, and verify data restoration from backup for resiliency.",
- "Name": "Backup",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "A1.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "11.1",
- "11.2",
- "11.3",
- "11.4",
- "11.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27017: 12.3",
- "27018: 12.3.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.13",
- "27001: A.5.23",
- "27001: A.5.30",
- "27002: 8.13",
- "27002: 5.23 2nd (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-4",
- "CP-4(4)",
- "CP-6",
- "CP-6(1)-(3)",
- "CP-9",
- "CP-9(1)",
- "CP-9(2)",
- "CP-10",
- "CP-10(2)",
- "CP-10(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-4",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-11",
- "RC.RP-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.5.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "10.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "objectstorage_bucket_versioning_enabled"
- ]
- },
- {
- "Id": "BCR-09",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain a disaster response plan to recover from natural and man-made disasters. Update the plan at least annually or upon significant changes.",
- "Name": "Disaster Response Plan",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8",
- "5.2.9",
- "1.6.1",
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.4",
- "BC2.1",
- "BC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.29",
- "27001: A.5.30",
- "27002: 5.29",
- "27002: 5.30"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2(1)",
- "CP-2(2)",
- "CP-2(3)",
- "CP-2(5)",
- "CP-2(6)",
- "CP-2(7)",
- "CP-2(8)",
- "PE-13",
- "PE-13(1)",
- "PE-13(2)",
- "PE-13(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-9",
- "PR.IP-10",
- "RC.IM-1",
- "RC.IM-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.IM-04"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "BCR-11",
- "Description": "Supplement business-critical equipment with redundant equipment independently located at a reasonable minimum distance in accordance with applicable industry standards.",
- "Name": "Equipment Redundancy",
- "Attributes": [
- {
- "Section": "Business Continuity Management and Operational Resilience",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.2",
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-06"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.8"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "BC1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.20",
- "27001: A.7.11",
- "27001: A.8.14",
- "27002: 5.20 (t)",
- "27002: 8.14 (c)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "CP-4(3)",
- "CP-6",
- "CP-6(1)",
- "CP-7",
- "CP-8",
- "CP-8(1)-(3)",
- "CP-9",
- "CP-9(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.BE-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.OC-04",
- "GV.OC-05",
- "PR.IR-03"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "CCC-04",
- "Description": "Restrict the unauthorized addition, removal, update, and management of organization assets.",
- "Name": "Unauthorized Change Protection",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "CCC-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.1",
- "1.3.4",
- "5.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4",
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.1.4",
- "27002: 12.1.4",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27001: A.14.2.2",
- "27017: 14.2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.3",
- "27001: A.8.4",
- "27001: A.8.15",
- "27001: A.8.31",
- "27001: A.8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(4)",
- "CM-3",
- "CM-3(1)",
- "CM-3(5)",
- "CM-3(7)",
- "CM-3(8)",
- "CM-5",
- "CM-5(1)",
- "CM-5(4)",
- "CM-5(5)",
- "CM-6",
- "CM-6(1)",
- "CM-6(2)",
- "CM-7",
- "CM-7(1)",
- "CM-7(4)",
- "CM-7(5)",
- "CM-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.MA-1",
- "PR.MA-2",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04",
- "ID.AM-08",
- "PR.PS-02",
- "PR.PS-03",
- "PR.PS-05",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.1",
- "6.5.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "events_rule_iam_group_changes",
- "events_rule_iam_policy_changes",
- "events_rule_user_changes",
- "events_rule_vcn_changes"
- ]
- },
- {
- "Id": "CCC-07",
- "Description": "Implement detection measures with proactive notification in case of changes deviating from the established baseline.",
- "Name": "Detection of Baseline Deviation",
- "Attributes": [
- {
- "Section": "Change Control and Configuration Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC8.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.5.1",
- "1.5.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.2.2",
- "27001: A.14.2.4",
- "27001: A.12.4.1",
- "27002: 12.4.1 (g)",
- "27001: A.5.1.1",
- "27017: 5.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.9",
- "27001: A.8.15",
- "27002: 8.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(2)",
- "SI-2",
- "SI-2(2)-(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.MA-1",
- "PR.IP-1",
- "DE.DP-4",
- "PR.IP-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01",
- "DE.CM-09",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4.5.3",
- "6.4.5.4",
- "11.5",
- "11.5.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "11.5.2",
- "11.6.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled",
- "events_rule_cloudguard_problems",
- "events_rule_network_gateway_changes",
- "events_rule_network_security_group_changes",
- "events_rule_route_table_changes",
- "events_rule_security_list_changes",
- "events_rule_vcn_changes"
- ]
- },
- {
- "Id": "CEK-03",
- "Description": "Provide cryptographic protection to data at-rest and in-transit, using cryptographic libraries certified to approved standards.",
- "Name": "Data Encryption",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-03",
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6",
- "3.1",
- "3.11",
- "11.3",
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.1",
- "27001: A.18.1.2",
- "27001: A.18.1.3",
- "27001: A.18.1.4",
- "27001: A.18.1.5",
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.18",
- "27002: 18",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27001: A.14.1.3",
- "27002 14.1.3 c)",
- "27001 - A.10.1.1",
- "27017 - 10.1.1",
- "27001 - A.10.1.2",
- "27017 - 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.24",
- "27002: 8.24 Other Information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19",
- "AC-19(5)",
- "SC-8",
- "SC-8(1)",
- "SC-8(3)",
- "SC-8(4)",
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)-(3)",
- "SI-4",
- "SI-4(10)",
- "SI-7",
- "SI-7(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "Requirement 3",
- "2.2.3",
- "2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "blockstorage_block_volume_encrypted_with_cmk",
- "blockstorage_boot_volume_encrypted_with_cmk",
- "compute_instance_in_transit_encryption_enabled",
- "filestorage_file_system_encrypted_with_cmk",
- "objectstorage_bucket_encrypted_with_cmk"
- ]
- },
- {
- "Id": "CEK-04",
- "Description": "Use encryption algorithms that are appropriate for data protection, considering the classification of data, associated risks, and usability of the encryption technology.",
- "Name": "Encryption Algorithm",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.2",
- "27002: 8.2",
- "27001: A.8.3",
- "27001: A.10.1.1",
- "27002: 10.1.1 (b)",
- "27001: A.10.1.2",
- "27002: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.2",
- "27001: 6.1.3",
- "27001: A.8.24",
- "27001: A.5.12",
- "27001: A.5.13",
- "27002: 8.24 General (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A2",
- "Requirement 3",
- "2.3",
- "2.2.3",
- "3.4",
- "3.5.3",
- "4.1",
- "8.2.1",
- "PCI Glossary - Strong Cryptography"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.7",
- "3.5.1",
- "4.2.1",
- "4.2.1.2",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "CEK-08",
- "Description": "CSPs must provide the capability for CSCs to manage their own data encryption keys.",
- "Name": "CSC Key Management Capability",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27017: 10.1",
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.23",
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-9",
- "CP-9(8)",
- "SA-9",
- "SA-9(6)",
- "SC-12",
- "SC-12(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.AM-6",
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-05"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "blockstorage_block_volume_encrypted_with_cmk",
- "blockstorage_boot_volume_encrypted_with_cmk",
- "filestorage_file_system_encrypted_with_cmk",
- "objectstorage_bucket_encrypted_with_cmk"
- ]
- },
- {
- "Id": "CEK-10",
- "Description": "Generate Cryptographic keys using industry accepted cryptographic libraries specifying the algorithm strength and the random number generator used.",
- "Name": "Key Generation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2",
- "TS2.3",
- "SY1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27002: 10.1.1 (e)",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2",
- "27002: 10.1.2 (a)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24",
- "27002: 8.24 (d), Key management (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2.3",
- "3.6.1",
- "PCI Glossary - Cryptographic Key Generation"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.6.1.1",
- "3.7.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "CEK-12",
- "Description": "Rotate cryptographic keys in accordance with the calculated cryptoperiod, which includes provisions for considering the risk of information disclosure and legal and regulatory requirements.",
- "Name": "Key Rotation",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27001: A.10.1.2",
- "27002: 10.1.2 e)",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (e,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)",
- "SC-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_key_rotation_enabled",
- "identity_user_api_keys_rotated_90_days",
- "identity_user_auth_tokens_rotated_90_days",
- "identity_user_customer_secret_keys_rotated_90_days",
- "identity_user_db_passwords_rotated_90_days"
- ]
- },
- {
- "Id": "CEK-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.",
- "Name": "Key Destruction",
- "Attributes": [
- {
- "Section": "Cryptography, Encryption & Key Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.1",
- "27017: 10.1.1",
- "27017: 10.1.2",
- "27001: A.10.1.2",
- "27002: 10.1.2 (j)",
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.31",
- "27001: A.8.24",
- "27002: 5.31 Cryptography",
- "27002: 8.24 Key management (j,m)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-12",
- "SC-12(2)",
- "SC-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.IP-6",
- "ID.GV-3",
- "PR.DS-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05",
- "ID.AM-08",
- "GV.OC-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.6.4",
- "3.6.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.7.4",
- "3.7.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DCS-06",
- "Description": "Catalogue and track all relevant physical and logical assets located at all of the CSP's sites within a secured system.",
- "Name": "Assets Cataloguing and Tracking",
- "Attributes": [
- {
- "Section": "Datacenter Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DCS - 01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "1.1",
- "2.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.6"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27017: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-8",
- "CM-8(1)",
- "CM-8(2)",
- "CM-8(4)",
- "CM-8(7)",
- "CM-8(8)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-1",
- "ID.AM-2",
- "ID.AM-4",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-01",
- "ID.AM-02",
- "ID.AM-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4",
- "9.7.1",
- "9.9.1",
- "9.9.1.a",
- "9.9.1.b",
- "9.9.1.c",
- "12.3.3",
- "12.3.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1.1",
- "6.3.2",
- "9.4.2",
- "9.4.3",
- "12.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-02",
- "Description": "Apply industry accepted methods for the secure disposal of data from storage media such that data is not recoverable by any forensic means.",
- "Name": "Secure Disposal",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3",
- "CC6.4",
- "CC6.5",
- "CC6.7",
- "P4.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-07"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.3",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.3.2",
- "27002: 8.3.2",
- "27001: A.11.2.7",
- "27002: 11.2.7"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.7.10",
- "27001: A.7.14",
- "27001: A.8.10",
- "27002: 7.10 (Secure reuse or disposal)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-22",
- "SI-12",
- "SI-12(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.SC-10",
- "PR.PS-02",
- "PR.PS-03",
- "ID.AM-08"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1",
- "9.8",
- "9.8.1",
- "9.8.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "3.7.5",
- "9.4.7"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-03",
- "Description": "Create and maintain a data inventory, at least for any sensitive data and personal data.",
- "Name": "Data Inventory",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2",
- "1.3.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.1.1",
- "27002: 8.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.9",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-12",
- "CM-12(1)",
- "PM-5",
- "PM-5(1)",
- "SI-12",
- "SI-12(1)",
- "SI-19",
- "SI-19(1)",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1",
- "9.4.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-04",
- "Description": "Classify data according to its type and sensitivity level.",
- "Name": "Data Classification",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "C1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "DSI-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.3.1",
- "1.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.8.2.1",
- "27002: 8.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-16",
- "AC-16(9)",
- "PM-22",
- "PM-23",
- "PT-2",
- "PT-2(1)",
- "SI-18",
- "SI-18(2)",
- "SI-19",
- "SI-19(6)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.AM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-05",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "9.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "9.4.2",
- "9.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "DSP-07",
- "Description": "Develop systems, products, and business practices based upon a principle of security by design and industry best practices.",
- "Name": "Data Protection by Design and Default",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "PI1.2",
- "PI1.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "16.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.1",
- "5.3.2",
- "5.3.3",
- "5.3.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SD2.2",
- "IM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.14.1.1",
- "27002:14.1.1",
- "27001: A.14.2.5",
- "27002:14.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.27",
- "27001: A.8.28",
- "27001: A.8.29",
- "27002: 5.8 (Information security requirements a-i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-17",
- "PM-24",
- "PM-25",
- "PT-2",
- "PT-2(2)",
- "SA-3",
- "SA-4",
- "SA-5",
- "SA-8",
- "SA-8(9)",
- "SA-8(13)",
- "SA-8(18)",
- "SA-8(20)",
- "SA-8(22)",
- "SA-8(23)",
- "SA-8(33)",
- "SA-15",
- "SA-15(12)",
- "SC-3",
- "SC-3(3)",
- "SC-7",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(4)",
- "SC-28",
- "SC-28(1)",
- "SI-12",
- "SI-12(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-2",
- "PR.PT-3",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "PR.PS-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "objectstorage_bucket_not_publicly_accessible",
- "database_autonomous_database_access_restricted",
- "analytics_instance_access_restricted",
- "integration_instance_access_restricted"
- ]
- },
- {
- "Id": "DSP-10",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope as permitted by the respective laws and regulations.",
- "Name": "Sensitive Data Transfer",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.12",
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "9.5.1",
- "9.5.2",
- "9.5.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27001: A.8.3.3",
- "27002: 8.3.3",
- "27001: A.13.2.3",
- "27002: 13.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.7.10"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-4",
- "AC-4(23)-(25)",
- "CA-3",
- "CA-3(6)",
- "CA-6",
- "CA-6(1)",
- "CA-6(2)",
- "SC-4",
- "SC-4(2)",
- "SC-7",
- "SC-7(10)",
- "SC-7(24)",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-16",
- "SC-16(1)-(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.DS-5",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.IR-01",
- "ID.AM-03",
- "GV.OC-03",
- "ID.AM-07"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "4.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.1.1",
- "4.2.1",
- "4.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_in_transit_encryption_enabled"
- ]
- },
- {
- "Id": "DSP-16",
- "Description": "Data retention, archiving and deletion is managed in accordance with business requirements, applicable laws and regulations.",
- "Name": "Data Retention and Deletion",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "C1.1",
- "C1.2",
- "CC3.1",
- "P4.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-02",
- "BCR-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.4",
- "3.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.3.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.10",
- "27002: 5.33 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SI-12",
- "SI-12(1)-(3)",
- "SI-18",
- "SI-18(1)",
- "SI-18(4)",
- "SI-18(5)",
- "SI-19",
- "SI-19(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-3",
- "PR.IP-6",
- "ID.GV-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-08",
- "GV.OC-03",
- "GV.SC-10",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days"
- ]
- },
- {
- "Id": "DSP-17",
- "Description": "Define and implement, processes, procedures and technical measures to protect sensitive data throughout it's lifecycle.",
- "Name": "Sensitive Data Protection",
- "Attributes": [
- {
- "Section": "Data Security and Privacy Lifecycle Management",
- "CCMLite": "Yes",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSC-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.1",
- "CC6.1",
- "CC6.3",
- "CC6.7",
- "CC8.1",
- "C1.1",
- "P2.0",
- "P3.0",
- "P4.0",
- "P5.0",
- "P6.0"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.1",
- "3.1",
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.3.3",
- "9.1.1",
- "9.2.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.1",
- "IM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001:A.18.1.4",
- "27002:18.1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.11",
- "27001: A.8.12"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-2",
- "PM-22",
- "PM-24",
- "PT-7",
- "PT-7(1)",
- "PT-7(2)",
- "PT-8",
- "SC-8",
- "SC-8(1)-(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1",
- "PR.DS-2",
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-10"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.0 (including all subsections)",
- "4.0 (including all subsections)"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.1.1",
- "4.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "objectstorage_bucket_not_publicly_accessible",
- "objectstorage_bucket_encrypted_with_cmk",
- "database_autonomous_database_access_restricted",
- "blockstorage_block_volume_encrypted_with_cmk",
- "blockstorage_boot_volume_encrypted_with_cmk"
- ]
- },
- {
- "Id": "GRC-05",
- "Description": "Develop and implement an Information Security Program, which includes programs for all the relevant domains of the CCM.",
- "Name": "Information Security Program",
- "Attributes": [
- {
- "Section": "Governance, Risk and Compliance",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "14.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SG2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 4.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-1",
- "PM-3",
- "PM-14",
- "PL-2",
- "PM-18",
- "PM-31"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.4.1",
- "A.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.4.1",
- "A3.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "IAM-02",
- "Description": "Establish, document, approve, communicate, implement, apply, evaluate and maintain strong password policies and procedures. Review and update the policies and procedures at least annually.",
- "Name": "Strong Password Policy and Procedures",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-12",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "4.1.2",
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1",
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.7.2.2",
- "27002: 7.2.2",
- "27001: A.9.2.6",
- "27002: 9.2.6",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.17",
- "27001: A.6.3",
- "27001: A.8.5",
- "27001: A.5.37"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-3",
- "AC-3(3)",
- "AC-12",
- "AC-12(1)",
- "IA-2",
- "IA-2(10)",
- "IA-5",
- "IA-5(1)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.AC-1",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.4",
- "12.1",
- "12.1.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.1.1",
- "8.3.8"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_password_policy_minimum_length_14",
- "identity_password_policy_expires_within_365_days",
- "identity_password_policy_prevents_reuse"
- ]
- },
- {
- "Id": "IAM-03",
- "Description": "Manage, store, and review the information of system identities, and level of access.",
- "Name": "Identity Inventory",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-04",
- "IAM-08",
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "5.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.8.1.1",
- "27002: 8.1.1",
- "27001: A.9.4.1",
- "27002: 9.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.2 (c)",
- "27001: A.5.15",
- "27001: A.5.16",
- "27001: A.5.18",
- "27001: A.7.4",
- "27001: A.8.15",
- "27001: A.8.2",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "AU-16",
- "AU-16(1)",
- "IA-4",
- "IA-4(8)",
- "IA-4(9)",
- "IA-5",
- "IA-5(5)",
- "IA-8",
- "IA-8(4)",
- "PM-5(1)",
- "SA-8",
- "SA-8(22)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-04",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.4.a"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_user_api_keys_rotated_90_days",
- "identity_user_auth_tokens_rotated_90_days",
- "identity_user_customer_secret_keys_rotated_90_days",
- "identity_user_valid_email_address"
- ]
- },
- {
- "Id": "IAM-04",
- "Description": "Employ the separation of duties principle when implementing information system access.",
- "Name": "Separation of Duties",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC1.3",
- "CC5.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.2.2",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.6.1.2",
- "27002: 6.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18",
- "27001: A.5.3",
- "27001: A.8.2"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(3)",
- "AC-2(11)",
- "AC-6",
- "AC-6(1)-(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.4",
- "6.4.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_service_level_admins_exist",
- "identity_iam_admins_cannot_update_tenancy_admins",
- "identity_tenancy_admin_permissions_limited"
- ]
- },
- {
- "Id": "IAM-05",
- "Description": "Employ the least privilege principle when implementing information system access.",
- "Name": "Least Privilege",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-06",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.1",
- "27002: 9.1.1",
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27001: A.9.2.3",
- "27002: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.8.2",
- "27002: 5.15 (Other information 2nd (a))"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "IA-12",
- "IA-12(2)",
- "IA-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1",
- "7.1.1",
- "7.1.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2",
- "7.2.5",
- "7.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_tenancy_admin_permissions_limited",
- "identity_service_level_admins_exist",
- "identity_no_resources_in_root_compartment",
- "identity_non_root_compartment_exists"
- ]
- },
- {
- "Id": "IAM-07",
- "Description": "De-provision or respectively modify access of movers / leavers or system identity changes in a timely manner in order to effectively adopt and communicate identity and access management policies.",
- "Name": "User Access Changes and Revocation",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.3",
- "6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(1)",
- "AC-2(2)",
- "AC-2(6)",
- "AC-2(8)",
- "AC-3",
- "AC-3(8)",
- "AC-6",
- "AC-6(7)",
- "AU-10",
- "AU-10(4)",
- "AU-16",
- "AU-16(1)",
- "CM-7",
- "CM-7(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.IP-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-04",
- "GV.SC-10",
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.5",
- "8.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_user_api_keys_rotated_90_days",
- "identity_user_auth_tokens_rotated_90_days",
- "identity_user_customer_secret_keys_rotated_90_days"
- ]
- },
- {
- "Id": "IAM-08",
- "Description": "Review and revalidate user access for least privilege and separation of duties with a frequency that is commensurate with organizational risk tolerance.",
- "Name": "User Access Review",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-10"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27001: A.9.2.6",
- "27001: A.9.4.1",
- "27017: 9.4.1",
- "27001: A.6.1.2",
- "27001: A 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.3",
- "27001: A.5.18",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(4)",
- "AC-6(8)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.5.1",
- "7.2.5",
- "7.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_user_api_keys_rotated_90_days",
- "identity_user_auth_tokens_rotated_90_days",
- "identity_user_customer_secret_keys_rotated_90_days",
- "identity_user_db_passwords_rotated_90_days"
- ]
- },
- {
- "Id": "IAM-09",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the segregation of privileged access roles such that administrative access to data, encryption and key management capabilities and logging capabilities are distinct and separated.",
- "Name": "Segregation of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.1",
- "CC6.1",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (j)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-3(7)",
- "AC-6(4)",
- "AC-6(8)",
- "IA-5",
- "IA-5(6)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.3",
- "3.5.2",
- "7.1.2",
- "7.1.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.6.1",
- "3.7.6",
- "6.5.3",
- "6.5.4",
- "7.2.1",
- "7.2.2",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_tenancy_admin_permissions_limited",
- "identity_iam_admins_cannot_update_tenancy_admins",
- "identity_tenancy_admin_users_no_api_keys"
- ]
- },
- {
- "Id": "IAM-10",
- "Description": "Define and implement an access process to ensure privileged access roles and rights are granted for a time limited period, and implement procedures to prevent the culmination of segregated privileged access.",
- "Name": "Management of Privileged Access Roles",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1",
- "6.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.3",
- "27002: 9.2.3",
- "27017: 9.2.3",
- "27018: 9.2.3",
- "27001: A.9.4.4",
- "27002: 9.4.4",
- "27017: 9.4.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.2",
- "27001: A.8.18",
- "27002: 8.2 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(7)",
- "AC-3",
- "AC-3(4)",
- "AC-3(11)",
- "AC-3(13)",
- "AC-3(14)",
- "AC-6",
- "AC-6(4)",
- "AC-6(5)",
- "AC-6(8)",
- "AC-12",
- "AC-12(3)",
- "AC-17",
- "AC-17(4)",
- "IA-8",
- "IA-8(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "7.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "7.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_tenancy_admin_permissions_limited",
- "identity_tenancy_admin_users_no_api_keys",
- "identity_iam_admins_cannot_update_tenancy_admins"
- ]
- },
- {
- "Id": "IAM-12",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the logging infrastructure is read-only for all with write access, including privileged access roles, and that the ability to disable it is controlled through a procedure that ensures the segregation of duties and break glass procedures.",
- "Name": "Safeguard Logs Integrity",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.3"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1",
- "27018: 12.4.1",
- "27001: A.12.4.2",
- "27002: 12.4.2",
- "27017: 12.4.2",
- "27018: 12.4.2",
- "27001: A.12.4.3",
- "27002: 12.4.3",
- "27017: 12.4.3",
- "27018: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.18",
- "27002: 8.15 Protection of Logs"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-2",
- "AC-2(11)",
- "AC-2(12)",
- "IA-8",
- "IA-8(4)",
- "SA-8",
- "SA-8(22)",
- "SC-34",
- "SC-34(1)",
- "SC-34(2)",
- "SC-36",
- "SI-4",
- "SI-4(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days"
- ]
- },
- {
- "Id": "IAM-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures that ensure users are identifiable through unique IDs or which can associate individuals to the usage of user IDs.",
- "Name": "Uniquely Identifiable Users",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.1",
- "27002: 9.2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(14)",
- "AC-24",
- "AC-24(2)",
- "AU-10",
- "AU-10(1)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-4",
- "IA-4(1)",
- "SA-8",
- "SA-8(22)",
- "SC-23",
- "SC-23(3)",
- "SC-40(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1",
- "8.2",
- "8.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "8.2.1",
- "8.2.2",
- "8.2.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_user_mfa_enabled_console_access",
- "identity_user_valid_email_address"
- ]
- },
- {
- "Id": "IAM-14",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for authenticating access to systems, application and data assets, including multifactor authentication for at least privileged user and sensitive data access. Adopt digital certificates or alternatives which achieve an equivalent level of security for system identities.",
- "Name": "Strong Authentication",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02",
- "IAM-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "6.3",
- "6.5",
- "12.5",
- "12.7"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4",
- "SA1.8"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.1.2",
- "27002: 9.1.2",
- "27017: 9.1.2",
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27001: A.9.4.2",
- "27002: 9.4.2",
- "27017: 9.4.2",
- "27018: 9.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.15",
- "27001: A.5.17",
- "27001: A.8.5",
- "27001: A.8.24",
- "27002: 8.5",
- "27002: 8.24 other information (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-6",
- "AC-6(5)",
- "AC-7",
- "AC-7(4)",
- "AU-10",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(8)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5",
- "IA-5(2)",
- "IA-5(7)",
- "IA-5(9)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-5(14)-(16)",
- "IA-8",
- "IA-8(1)",
- "IA-8(6)",
- "SC-23",
- "SC-23(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-6",
- "PR.AC-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.1.2",
- "8.1.3",
- "8.1.6",
- "8.2",
- "8.3",
- "8.3.2",
- "12.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.1",
- "8.3.1",
- "8.3.2",
- "8.4.1",
- "8.4.2",
- "8.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_user_mfa_enabled_console_access"
- ]
- },
- {
- "Id": "IAM-15",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the secure management of passwords.",
- "Name": "Passwords Management",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.4",
- "27002: 9.2.4",
- "27017: 9.2.4",
- "27018: 9.2.4",
- "27001: A.9.3.1",
- "27002: 9.3.1",
- "27017: 9.3.1",
- "27018: 9.3.1",
- "27001: A.9.4.3",
- "27002: 9.4.3",
- "27017: 9.4.3",
- "27018: 9.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.17"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IA-4",
- "IA-4(8)",
- "IA-5",
- "IA-5(1)",
- "IA-5(8)",
- "IA-5(18)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "8.2",
- "8.2.1-6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.2",
- "2.3.1",
- "8.3.5",
- "8.3.6",
- "8.3.7",
- "8.3.8",
- "8.3.9",
- "8.3.10",
- "8.3.10.1",
- "8.6.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_password_policy_minimum_length_14",
- "identity_password_policy_expires_within_365_days",
- "identity_password_policy_prevents_reuse"
- ]
- },
- {
- "Id": "IAM-16",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to verify access to data and system functions is authorized.",
- "Name": "Authorization Mechanisms",
- "Attributes": [
- {
- "Section": "Identity & Access Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.2",
- "CC6.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IAM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "5.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SA1.3",
- "SA1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.9.2.5",
- "27002: 9.2.5",
- "27017: 9.2.5",
- "27018: 9.2.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.18"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-3",
- "AC-3(5)",
- "AC-4",
- "AC-4(17)",
- "AC-4(21)",
- "AC-4(22)",
- "AC-6",
- "AC-6(8)",
- "AC-6(9)",
- "AC-12",
- "AC-12(1)",
- "AC-20",
- "AC-20(1)",
- "AU-10",
- "AU-10(1)",
- "AU-10(2)",
- "IA-2",
- "IA-2(1)",
- "IA-2(2)",
- "IA-2(12)",
- "IA-3",
- "IA-3(1)",
- "IA-5(1)",
- "IA-5(2)",
- "IA-5(5)",
- "IA-5(8)",
- "IA-5(10)",
- "IA-5(12)",
- "IA-8",
- "IA-8(1)",
- "IA-8(2)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4",
- "PR.AC-6",
- "PR.AC-7",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-01",
- "PR.AA-02",
- "PR.AA-03",
- "PR.AA-04",
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.3",
- "7.1.4"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "7.2.4",
- "7.2.3",
- "7.2.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "identity_tenancy_admin_permissions_limited",
- "identity_service_level_admins_exist",
- "database_autonomous_database_access_restricted",
- "analytics_instance_access_restricted",
- "integration_instance_access_restricted"
- ]
- },
- {
- "Id": "IPY-03",
- "Description": "Implement cryptographically secure and standardized network protocols for the management, import and export of data.",
- "Name": "Secure Interoperability and Portability Management",
- "Attributes": [
- {
- "Section": "Interoperability & Portability",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IPY-04"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.2",
- "NC1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1",
- "27001: A.15.1.1",
- "27002: 15.1.1",
- "27017: 15.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.19",
- "27001: A.5.23",
- "27001: A.5.31",
- "27001: A.5.32",
- "27001: A.5.33",
- "27001: A.5.34"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PT-2",
- "PT-2(2)",
- "SA-4",
- "SC-16",
- "SC-16(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.1",
- "1.2.5",
- "1.2.6",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_in_transit_encryption_enabled"
- ]
- },
- {
- "Id": "IVS-02",
- "Description": "Plan and monitor the availability, quality, and adequate capacity of resources in order to deliver the required system performance as determined by the business.",
- "Name": "Capacity and Resource Planning",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "No",
- "IaaS": "CSP-Owned",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "A1.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-04"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.3",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.12.1.3",
- "27002: 12.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.3 (b)",
- "27001: 6.1",
- "27001: 9.1",
- "27001: A.8.6",
- "27001: A.8.14"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CP-2",
- "CP-2(2)",
- "SC-5",
- "SC-5(2)",
- "SC-4",
- "SI-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-4",
- "ID.BE-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-04",
- "GV.OC-04"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "IVS-03",
- "Description": "Monitor, encrypt and restrict communications between environments to only authenticated and authorized connections, as justified by the business. Review these configurations at least annually, and support them by a documented justification of all allowed services, protocols, ports, and compensating controls.",
- "Name": "Network Security",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-06"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.8",
- "3.1",
- "12.2",
- "13.6",
- "13.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: A.5.15 2nd c)",
- "27002: 8.20",
- "27002: 8.21",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-1",
- "SC-4",
- "SC-7",
- "SC-7(4)",
- "SC-7(5)",
- "SC-7(8)",
- "SC-7(9)",
- "SC-7(11)",
- "SC-8",
- "SC-8(1)",
- "SC-11",
- "SC-12",
- "SC-16",
- "SC-23",
- "SC-29",
- "SC-29(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-5",
- "PR.AC-7",
- "PR.PT-4",
- "DE.CM-1",
- "DE.CM-7",
- "PR.DS-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.IR-01",
- "PR.AA-03",
- "PR.AA-05",
- "DE.CM-01",
- "PR.DS-02",
- "ID.AM-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "1.1.6",
- "1.2",
- "1.2.3",
- "2.2",
- "4.1.1",
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.2.5",
- "1.2.6",
- "1.2.7",
- "1.4.2",
- "2.2.4",
- "2.2.5",
- "2.2.7",
- "4.2.1",
- "10.1.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "network_vcn_subnet_flow_logs_enabled",
- "network_default_security_list_restricts_traffic",
- "network_security_group_ingress_from_internet_to_ssh_port",
- "network_security_group_ingress_from_internet_to_rdp_port",
- "network_security_list_ingress_from_internet_to_ssh_port",
- "network_security_list_ingress_from_internet_to_rdp_port"
- ]
- },
- {
- "Id": "IVS-04",
- "Description": "Harden host and guest OS, hypervisor or infrastructure control plane according to their respective best practices, and supported by technical controls, as part of a security baseline.",
- "Name": "OS Hardening and Base Controls",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "CSP-Owned",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.8",
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-07",
- "IVS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "4.1",
- "4.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.1.3",
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SY1.1",
- "SY1.3",
- "SY1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.14.2.2",
- "27002: 14.2.2",
- "27001: A.14.2.3",
- "27001 A.14.2.4",
- "27018: 12.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5",
- "27001: 9.1",
- "27001: A.5.37",
- "27001: A.8.5",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.22",
- "27001: A.8.24",
- "27002: 8.20",
- "27002: 8.22",
- "27002: 8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-6",
- "CM-6(1)",
- "SC-29",
- "SC-29(1)",
- "SC-2",
- "SC-7",
- "SC-7(12)",
- "SC-30",
- "SC-34",
- "SC-35",
- "SC-39",
- "SC-44"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.IP-1",
- "PR.PT-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "2.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_legacy_metadata_endpoint_disabled",
- "compute_instance_secure_boot_enabled"
- ]
- },
- {
- "Id": "IVS-06",
- "Description": "Design, develop, deploy and configure applications and infrastructures such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented and segregated, monitored and restricted from other tenants.",
- "Name": "Segmentation and Segregation",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-09"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.3.4",
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SC2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 9.1",
- "27001: A.5.15",
- "27001: A.5.20",
- "27001: A.8.3",
- "27001: A.8.9",
- "27001: A.8.16",
- "27001: A.8.22",
- "27002: 5.15 (b)",
- "27002: 8.3 (b)",
- "27002: 8.16 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-3",
- "SC-7",
- "SC-7(20)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.AC-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.IR-01",
- "PR.PS-01",
- "PR.PS-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "2.6",
- "8.3.1",
- "10.8",
- "11.3",
- "A3.2.1",
- "A3.3.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A1.1.1",
- "A1.1.2",
- "A1.1.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "network_default_security_list_restricts_traffic",
- "identity_non_root_compartment_exists",
- "identity_no_resources_in_root_compartment"
- ]
- },
- {
- "Id": "IVS-07",
- "Description": "Use secure and encrypted communication channels when migrating servers, services, applications, or data to cloud environments. Such channels must include only up-to-date and approved protocols.",
- "Name": "Migration to Cloud Environments",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-10"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.4",
- "IM1.4",
- "NC1.4",
- "SC2.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.13.1.1",
- "27002: 13.1.1",
- "27017: 13.1.1",
- "27018: 13.1.1",
- "27001: A.13.1.2",
- "27002: 13.1.2",
- "27017: 13.1.2",
- "27018: 13.1.2",
- "27001: A.13.1.3",
- "27002: 13.1.3",
- "27017: 13.1.3",
- "27018: 13.1.3",
- "27001: A.13.2.1",
- "27002: 13.2.1",
- "27017: 13.2.1",
- "27018: 13.2.1",
- "27001: A.13.2.2",
- "27002: 13.2.2",
- "27017: 13.2.2",
- "27018: 13.2.2",
- "27001: A.13.2.3",
- "27002: 13.2.3",
- "27017: 13.2.3",
- "27018: 13.2.3",
- "27001: A.13.2.4",
- "27002: 13.2.4",
- "27017: 13.2.4",
- "27018: 13.2.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.14",
- "27001: A.8.20",
- "27001: A.8.24",
- "27002: 8.20 (e)",
- "27002: 8.24 Guidance (b,f), other information (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-17",
- "AC-20",
- "SC-7",
- "SC-7(28)",
- "SC-8",
- "SC-8(1)",
- "SC-12",
- "SC-23",
- "SC-29",
- "SI-7",
- "SI-7(1)-(3)",
- "SI-7(5)-(10)",
- "SI-7(12)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-2",
- "PR.PT-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "compute_instance_in_transit_encryption_enabled"
- ]
- },
- {
- "Id": "IVS-09",
- "Description": "Define, implement and evaluate processes, procedures and defense-in-depth techniques for protection, detection, and timely response to network-based attacks.",
- "Name": "Network Defense",
- "Attributes": [
- {
- "Section": "Infrastructure & Virtualization Security",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.6",
- "CC6.8",
- "CC7.1",
- "CC7.2",
- "CC7.5"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-13"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "13.3",
- "13.8"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3",
- "5.2.4",
- "5.2.5",
- "5.2.7",
- "5.3.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "NC1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.14.1.2",
- "27002: 14.1.2",
- "27017: 14.1.2",
- "27001: A.11.1.4",
- "27002: 11.1.4",
- "27017: 11.1.4",
- "27018: 16.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1",
- "27001: 6.2",
- "27001: A.5.24",
- "27001: A.5.26",
- "27001: A.8.8",
- "27001: A.8.16",
- "27001: A.8.20",
- "27001: A.8.21",
- "27001: A.8.22",
- "27001: A.8.26",
- "27002: 8.8 (i)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PL-8",
- "PL-8(1)",
- "SC-5",
- "SC-5(1)",
- "SC-5(3)",
- "SC-7",
- "SC-7(13)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.DP-1",
- "DE.CM-1",
- "DE.CM-7",
- "PR.AC-5",
- "RS.MI-2",
- "PR.DS-2",
- "RS.RP-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "DE.CM-01",
- "PR.IR-01",
- "RS.MA-01",
- "RS.MI-01",
- "RS.MI-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.6",
- "1.1",
- "1.2",
- "1.3",
- "1.5",
- "12.10.5"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "1.1.1",
- "1.3.1",
- "1.3.2",
- "1.3.3",
- "1.4.1",
- "1.4.2",
- "1.4.3",
- "1.4.4",
- "1.4.5",
- "1.5.1",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled",
- "events_rule_cloudguard_problems"
- ]
- },
- {
- "Id": "LOG-02",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to ensure the security and retention of audit logs.",
- "Name": "Audit Logs Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1",
- "8.9",
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.3",
- "5.1.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.18.1.3",
- "27002: 18.1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-4",
- "AU-11"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "ID.AM-08",
- "PR.DS-11",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.7"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4",
- "10.5.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days"
- ]
- },
- {
- "Id": "LOG-03",
- "Description": "Identify and monitor security-related events within applications and the underlying infrastructure. Define and implement a system to generate alerts to responsible stakeholders based on such events and corresponding metrics.",
- "Name": "Security Monitoring and Alerting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.8",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03",
- "SEF-05"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.5"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "5.2.7",
- "1.6.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2",
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.28",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-13"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-3",
- "DE.AE-5",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-4",
- "DE.CM-5",
- "DE.CM-6",
- "DE.CM-7",
- "DE.DP-1",
- "DE.DP-4",
- "DE.AE-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2",
- "10.4.1.1",
- "10.4.2.1",
- "10.4.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled",
- "events_rule_cloudguard_problems",
- "events_notification_topic_and_subscription_exists",
- "events_rule_local_user_authentication"
- ]
- },
- {
- "Id": "LOG-04",
- "Description": "Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.",
- "Name": "Audit Logs Access and Accountability",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.14"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "3.1.1",
- "4.1.2",
- "4.1.3",
- "4.2.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27001: A.12.4.1",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.33",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(4)",
- "AU-9(6)",
- "AU-10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-1",
- "PR.AC-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.1",
- "10.2.1",
- "10.2.3",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1.3",
- "10.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "LOG-05",
- "Description": "Monitor security audit logs to detect activity outside of typical or expected patterns. Establish and follow a defined process to review and take appropriate and timely actions on detected anomalies.",
- "Name": "Audit Logs Monitoring and Response",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.8",
- "8.11"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "1.6.2",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.3",
- "27002: 12.4.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15",
- "27001: A.8.16"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-6",
- "AU-6(1)",
- "AU-6(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-3",
- "PR.PT-1",
- "RS.AN-1",
- "RS.CO-1.",
- "DE.AE-1",
- "DE.AE-5",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.AM-03",
- "PR.PS-04",
- "DE.AE-02",
- "DE.AE-03",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6",
- "10.6.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.1.1",
- "10.4.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "events_rule_iam_group_changes",
- "events_rule_iam_policy_changes",
- "events_rule_identity_provider_changes",
- "events_rule_idp_group_mapping_changes",
- "events_rule_local_user_authentication",
- "events_rule_network_gateway_changes",
- "events_rule_network_security_group_changes",
- "events_rule_route_table_changes",
- "events_rule_security_list_changes",
- "events_rule_user_changes",
- "events_rule_vcn_changes",
- "events_rule_cloudguard_problems"
- ]
- },
- {
- "Id": "LOG-07",
- "Description": "Establish, document and implement which information meta/data system events should be logged. Review and update the scope at least annually or whenever there is a change in the threat environment.",
- "Name": "Logging Scope",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 7.5.3",
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-14",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.SC-3",
- "ID.SC-4",
- "PR.PT-1",
- "ID.GV-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.1",
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days",
- "network_vcn_subnet_flow_logs_enabled",
- "objectstorage_bucket_logging_enabled"
- ]
- },
- {
- "Id": "LOG-08",
- "Description": "Generate audit records containing relevant security information.",
- "Name": "Log Records",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "8.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.1",
- "27002: 12.4.1",
- "27017: 12.4.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-3",
- "AU-3(1)",
- "AU-3(3)",
- "AU-6",
- "AU-6(8)",
- "AU-12",
- "AU-12(1)",
- "AU-12(2)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3",
- "DE.CM-1",
- "DE.CM-2",
- "DE.CM-3",
- "DE.CM-6",
- "DE.CM-7"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-01",
- "DE.CM-02",
- "DE.CM-03",
- "DE.CM-06",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.3"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.2.2"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days",
- "network_vcn_subnet_flow_logs_enabled",
- "objectstorage_bucket_logging_enabled"
- ]
- },
- {
- "Id": "LOG-09",
- "Description": "The information system protects audit records from unauthorized access, modification, and deletion.",
- "Name": "Log Protection",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "GRM-04",
- "IVS-01"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.4",
- "4.2.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.4.2",
- "27002: 12.4.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.15"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(2)",
- "AU-9(3)",
- "AU-9(4)",
- "AU-12(3)",
- "AU-12(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.AC-4",
- "PR.IP-4",
- "PR.IP-6",
- "PR.PT-1",
- "PR.DS-1",
- "PR.DS-6"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AA-05",
- "PR.DS-01",
- "PR.DS-02",
- "PR.DS-11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.5",
- "10.5.1",
- "10.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.3.1",
- "10.3.2",
- "10.3.3",
- "10.3.4"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days"
- ]
- },
- {
- "Id": "LOG-10",
- "Description": "Establish and maintain a monitoring and internal reporting capability over the operations of cryptographic, encryption and key management policies, processes, procedures, and controls.",
- "Name": "Encryption Monitoring and Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02",
- "EKM-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "4.2.1",
- "5.1.1",
- "5.1.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1",
- "27002: 10.1",
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-1",
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "PR.PT-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.1.1",
- "10.2.1",
- "10.4.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "kms_key_rotation_enabled"
- ]
- },
- {
- "Id": "LOG-11",
- "Description": "Log and monitor key lifecycle management events to enable auditing and reporting on usage of cryptographic keys.",
- "Name": "Transaction/Activity Logging",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "EKM-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.1"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.10.1.2",
- "27017: 10.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.24"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-9",
- "AU-9(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.PT-1",
- "DE.AE-3"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.CM-09"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "audit_log_retention_period_365_days"
- ]
- },
- {
- "Id": "LOG-13",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the reporting of anomalies and failures of the monitoring system and provide immediate notification to the accountable party.",
- "Name": "Failures and Anomalies Reporting",
- "Attributes": [
- {
- "Section": "Logging and Monitoring",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3",
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-03"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.1",
- "5.2.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.16.1.2",
- "27017: 16.1.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.24",
- "27001: A.6.8",
- "27002: 6.8 (g)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AU-5",
- "AU-5(2)",
- "AU-6",
- "AU-6(3)",
- "AU-6(4)",
- "AU-6(5)",
- "AU-16"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-3",
- "DE.DP-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-04",
- "DE.AE-06"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "10.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "10.4.3",
- "10.7.1",
- "10.7.2",
- "10.7.3"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled",
- "events_rule_cloudguard_problems",
- "events_notification_topic_and_subscription_exists"
- ]
- },
- {
- "Id": "SEF-03",
- "Description": "'Establish, document, approve, communicate, apply, evaluate and maintain a security incident response plan, which includes but is not limited to: relevant internal departments, impacted CSCs, and other business critical relationships (such as supply-chain) that may be impacted.'",
- "Name": "Incident Response Plans",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2",
- "CC7.3",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "BCR-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2",
- "17.4"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27017: CLD.12.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: A.5.26",
- "27002: 5.26 (e,f)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-1",
- "IR-2",
- "IR-2(1)-(3)",
- "IR-3",
- "IR-3(1)-(3)",
- "IR-4",
- "IR-4(1)-(15)",
- "IR-5",
- "IR-5(1)",
- "IR-6",
- "IR-6(1)-(3)",
- "IR-7",
- "IR-7(1)",
- "IR-7(2)",
- "IR-8",
- "IR-8(1)",
- "IR-9",
- "IR-9(1)-(4)",
- "PM-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.CO-1",
- "RS.CO-4",
- "ID.AM-6",
- "ID.GV-2",
- "ID.SC-5",
- "PR.IP-9",
- "PR.IP10"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.AT-01",
- "PR.AT-02",
- "RS.MA-01",
- "GV.SC-08",
- "ID.IM-02",
- "ID.IM-04",
- "RC.RP-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.1",
- "12.10.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1",
- "12.10.5"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "SEF-06",
- "Description": "Define, implement and evaluate processes, procedures and technical measures supporting business processes to triage security-related events.",
- "Name": "Event Triage Processes",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-02"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.16.1.4",
- "27002: 16.1.4",
- "27017: 16.1.4",
- "27018: 16.1.4",
- "27001: A.16.1.5",
- "27002: 16.1.5",
- "27017: 16.1.5",
- "27018: 16.1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.25"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CA-7",
- "CA-7(3)",
- "CA-7(4)",
- "CA-7(5)",
- "CA-7(6)",
- "IR-4",
- "IR-4(1)",
- "IR-4(3)",
- "IR-4(4)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.AE-1",
- "DE.AE-2",
- "DE.AE-4",
- "RS.RP-1",
- "RS.AN-2"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "RS.MA-02",
- "RS.MA-03",
- "RS.AN-03",
- "DE.AE-02",
- "DE.AE-04",
- "DE.AE-06",
- "DE.AE-07",
- "DE.AE-08",
- "RS.MI-02",
- "RC.RP-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "12.5.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "SEF-08",
- "Description": "Maintain points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities.",
- "Name": "Points of Contact Maintenance",
- "Attributes": [
- {
- "Section": "Security Incident Management, E-Discovery, & Cloud Forensics",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC2.3"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "SEF-01"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "17.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.6.2",
- "1.6.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "SM2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 4.2",
- "27001: A.6.1.3",
- "27002: 6.1.3",
- "27017: 6.1.3",
- "27018: 6.1.3",
- "27001: A.16.1.1",
- "27002: 16.1.1",
- "27001: A.18.1.1",
- "27002: 18.1.1",
- "27017: 18.1.1",
- "27018: 18.1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.5",
- "27001: A.5.24",
- "27002: 5.24 Incident management procedure (d)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "IR-4",
- "IR-4(8)",
- "IR-6",
- "IR-6(3)",
- "IR-7",
- "IR-7(2)",
- "PM-21",
- "PM-23",
- "PM-26"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-2",
- "RS.CO-3",
- "RS.CO-4"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.RR-02",
- "RS.CO-02",
- "RS.CO-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-02",
- "Description": "Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures to protect against malware on managed assets. Review and update the policies and procedures at least annually.",
- "Name": "Malware Protection Policy and Procedures",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC6.8"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-01",
- "GRM-06",
- "GRM-09"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "9.7",
- "10.1"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "1.1.1",
- "1.5.1",
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.2",
- "TS1.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5",
- "27002: 5",
- "27001: A.12.2.1",
- "27001: A.6.2.1",
- "27002: 6.2.1 (h)",
- "27001: A.6.2.2",
- "27002: 6.2.2 (j)",
- "27001: A.7.2.2",
- "27002: 7.2.2 (d)",
- "27001: A.10.1.1",
- "27002: 10.1.1 (g)",
- "27001: A.13.2.1",
- "27002: 13.2.1 (b)",
- "27001: A.15.1.2",
- "27017: 15.1.2",
- "27001: A.12.2.1",
- "27002: 12.2.1 (a),(d)",
- "27017: CLD.9.5.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 5.1",
- "27001: 5.2",
- "27001: 7.3",
- "27001: 7.4",
- "27001: 7.5",
- "27001: 9.1",
- "27001: 9.3",
- "27001: A.5.1",
- "27001: A.5.4",
- "27001: A.5.7",
- "27001: A.5.37",
- "27001: A.8.7",
- "27002: 5.7 (b)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-3",
- "RA-3(3)",
- "RA-5",
- "RA-5(3)",
- "RA-5(5)",
- "SI-3",
- "SI-3(4)",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.GV-1",
- "DE.CM-4",
- "DE.CM-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "GV.PO-01",
- "GV.PO-02",
- "ID.IM-03",
- "DE.CM-01",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.4",
- "12.1",
- "12.1.1",
- "12.3.1",
- "12.5.1",
- "12.11"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "12.1.1",
- "12.1.2",
- "5.1.1",
- "5.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-03",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to enable both scheduled and emergency responses to vulnerability identifications, based on the identified risk.",
- "Name": "Vulnerability Remediation Schedule",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC5.3",
- "CC7.1",
- "CC7.4"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.2",
- "7.7",
- "17.9"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "TM2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.2.1",
- "27001: A.12.6.1",
- "27002: 12.6.1(c)(d)(j)",
- "27018: 12.6.1(k)(i)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.8.7",
- "27001: A.8.8",
- "27001: A.8.32",
- "27002: 8.7",
- "27002: 8.8",
- "27002: 8.32"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "PM-31",
- "RA-3",
- "RA-3(1)",
- "RA-5",
- "RA-5(2)-(4)",
- "RA-5(6)",
- "SI-3",
- "SI-3(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "RS.AN-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-06",
- "ID.RA-08",
- "PR.PS-02",
- "PR.PS-03"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.1.a",
- "6.1.b"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.1.1",
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "12.10.1"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-04",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to update detection tools, threat signatures, and indicators of compromise on a weekly, or more frequent basis.",
- "Name": "Detection Updates",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "10.2"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.3"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TS1.3",
- "TS1.4",
- "TM1.3",
- "TM1.4",
- "IM1.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1.1",
- "27002: 5.1.1 (h)",
- "27001: A.12.6.1",
- "27002: 12.6.1 (b),(c)"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.5.1",
- "27001: A.8.8",
- "27001: A.8.15",
- "27001: A.8.16",
- "27002: 5.1",
- "27002: 5.37",
- "27002: 8.8",
- "27002: 8.15 (d)",
- "27002: 8.16 (d,e)",
- "27002: 8.31 2nd (a)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "CM-7",
- "CM-7(4)",
- "RA-3",
- "RA-3(3)",
- "RA-5(2)",
- "SA-10",
- "SA-10(5)",
- "SA-11",
- "SA-11(2)",
- "SI-2",
- "SI-2(4)",
- "SI-3",
- "SI-3(4)",
- "SI-4",
- "SI-4(9)",
- "SI-4(24)",
- "SI-8",
- "SI-8(2)",
- "SI-8(3)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.PS-02",
- "ID.RA-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "5.2",
- "5.2a",
- "5.2b",
- "5.2c"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "5.3.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "TVM-05",
- "Description": "Define, implement and evaluate processes, procedures and technical measures to identify updates for applications which use third party or open source libraries according to the organization's vulnerability management policy.",
- "Name": "External Library Vulnerabilities",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "CSP-Owned",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC3.2"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "No mapping"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1",
- "SD2.3"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A.12.6.2",
- "27002: 12.6.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: 6.1.3",
- "27001: A 5.6",
- "27001: A.8.19",
- "27001: A.8.8",
- "27001: A.8.28",
- "27001: A.8.31",
- "27002: 5.6 (c)",
- "27001: 8.19",
- "27001: 8.8",
- "27001: 8.28",
- "27001: 8.31"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(3)",
- "SA-11",
- "SA-11(2)",
- "SA-11(5)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "DE.DP-5",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01",
- "ID.RA-03",
- "PR.PS-02"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "6.2",
- "6.3.2"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3"
- ]
- }
- ]
- }
- ],
- "Checks": []
- },
- {
- "Id": "TVM-07",
- "Description": "Define, implement and evaluate processes, procedures and technical measures for the detection of vulnerabilities on organizationally managed assets at least monthly.",
- "Name": "Vulnerability Identification",
- "Attributes": [
- {
- "Section": "Threat & Vulnerability Management",
- "CCMLite": "Yes",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC7.1"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "TVM-02"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "7.1",
- "7.5",
- "7.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.5",
- "5.2.6"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "TM1.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.6",
- "27001: A.12.6.1",
- "27002: 12.6.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.8",
- "27002: 8.8"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "RA-5",
- "RA-5(4)",
- "RA-5(5)",
- "SA-11",
- "SA-11(5)",
- "SA-15(5)",
- "SC-7",
- "SC-7(10)",
- "SI-3(8)",
- "SI-3(10)",
- "SI-7",
- "SI-7(9)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "ID.RA-1",
- "DE.CM-8",
- "PR.IP-12"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "ID.RA-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "6.1",
- "11.2",
- "11.2.1"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "6.3.1",
- "6.3.2",
- "6.3.3",
- "11.3.2",
- "11.3.2.1"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "cloudguard_enabled"
- ]
- },
- {
- "Id": "UEM-08",
- "Description": "Protect information from unauthorized disclosure on managed endpoint devices with storage encryption.",
- "Name": "Storage Encryption",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.1",
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CCM v3.0.1",
- "Identifiers": [
- "MOS-11"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.6"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.1.2",
- "3.1.4"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "PA1.2",
- "PA1.3",
- "PA1.5",
- "PA2.2",
- "PM1.4"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.11.2.7",
- "27002: 11.2.7",
- "27001: A.18.1.1",
- "27017: 18.1.1",
- "27001: A.12.3.1",
- "27017: 12.3.1",
- "27018: A.11.4",
- "27018: A.11.5"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.8.1",
- "27002: 8.1 (h)"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "AC-19(5)",
- "SC-28",
- "SC-28(1)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-1"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-01"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "3.4",
- "3.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "3.5.1",
- "3.6"
- ]
- }
- ]
- }
- ],
- "Checks": [
- "blockstorage_block_volume_encrypted_with_cmk",
- "blockstorage_boot_volume_encrypted_with_cmk",
- "filestorage_file_system_encrypted_with_cmk"
- ]
- },
- {
- "Id": "UEM-11",
- "Description": "Configure managed endpoints with Data Loss Prevention (DLP) technologies and rules in accordance with a risk assessment.",
- "Name": "Data Loss Prevention",
- "Attributes": [
- {
- "Section": "Universal Endpoint Management",
- "CCMLite": "No",
- "IaaS": "Shared",
- "PaaS": "Shared",
- "SaaS": "Shared",
- "ScopeApplicability": [
- {
- "ReferenceId": "AICPA TSC 2017",
- "Identifiers": [
- "CC6.7"
- ]
- },
- {
- "ReferenceId": "CIS v8.0",
- "Identifiers": [
- "3.13"
- ]
- },
- {
- "ReferenceId": "ENX ISA v6.0",
- "Identifiers": [
- "5.2.7"
- ]
- },
- {
- "ReferenceId": "ISF SOGP 2022",
- "Identifiers": [
- "IM1.5",
- "PA2.2"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2013,27002:2013,27017:2015,27018:2019",
- "Identifiers": [
- "27001: A.12.3",
- "27002: 12.3",
- "27001: A.8.3.1",
- "27002: 8.3.1",
- "27001: A.12.2",
- "27002: 12.2",
- "27001: A.18.1.3",
- "27002: 18.1.3",
- "27001: A.6.1.1",
- "27017: 6.1.1",
- "27018: 12.3.1",
- "27018: 10.1"
- ]
- },
- {
- "ReferenceId": "ISO/IEC 27001:2022, 27002:2022",
- "Identifiers": [
- "27001: A.5.12",
- "27001: A.8.3"
- ]
- },
- {
- "ReferenceId": "NIST 800-53 rev 5",
- "Identifiers": [
- "SC-7",
- "SC-7(10)"
- ]
- },
- {
- "ReferenceId": "NIST CSF v1.1",
- "Identifiers": [
- "PR.DS-5"
- ]
- },
- {
- "ReferenceId": "NIST CSF v2.0",
- "Identifiers": [
- "PR.DS-02",
- "PR.DS-10",
- "PR.PS-01",
- "ID.AM-08",
- "DE.CM-09"
- ]
- },
- {
- "ReferenceId": "PCI DSS v3.2.1",
- "Identifiers": [
- "A3.2.6"
- ]
- },
- {
- "ReferenceId": "PCI DSS v4.0",
- "Identifiers": [
- "A3.2.6"
- ]
- }
- ]
- }
- ],
- "Checks": []
- }
- ]
-}
diff --git a/tests/lib/outputs/compliance/universal/__init__.py b/prowler/compliance/stackit/__init__.py
similarity index 100%
rename from tests/lib/outputs/compliance/universal/__init__.py
rename to prowler/compliance/stackit/__init__.py
diff --git a/prowler/config/config.py b/prowler/config/config.py
index 8b0ba9e503..bee2984db3 100644
--- a/prowler/config/config.py
+++ b/prowler/config/config.py
@@ -1,3 +1,4 @@
+import importlib.metadata
import os
import pathlib
from datetime import datetime, timezone
@@ -48,7 +49,7 @@ class _MutableTimestamp:
timestamp = _MutableTimestamp(datetime.today())
timestamp_utc = _MutableTimestamp(datetime.now(timezone.utc))
-prowler_version = "5.28.0"
+prowler_version = "5.36.0"
html_logo_url = "https://github.com/prowler-cloud/prowler/"
square_logo_img = "https://raw.githubusercontent.com/prowler-cloud/prowler/dc7d2d5aeb92fdf12e8604f42ef6472cd3e8e889/docs/img/prowler-logo-black.png"
aws_logo = "https://user-images.githubusercontent.com/38561120/235953920-3e3fba08-0795-41dc-b480-9bea57db9f2e.png"
@@ -78,19 +79,54 @@ class Provider(str, Enum):
SCALEWAY = "scaleway"
VERCEL = "vercel"
OKTA = "okta"
+ STACKIT = "stackit"
+ LINODE = "linode"
+ E2ENETWORKS = "e2enetworks"
# Compliance
actual_directory = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
+def _get_ep_compliance_dirs() -> dict:
+ """Discover compliance directories from entry points. Returns {provider: [paths]}.
+
+ A provider may be contributed by several packages, so accumulate every
+ directory instead of overwriting.
+ """
+ dirs = {}
+ for ep in importlib.metadata.entry_points(group="prowler.compliance"):
+ try:
+ module = ep.load()
+ if hasattr(module, "__path__"):
+ path = module.__path__[0]
+ elif hasattr(module, "__file__"):
+ path = os.path.dirname(module.__file__)
+ else:
+ continue
+ dirs.setdefault(ep.name, []).append(path)
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return dirs
+
+
def get_available_compliance_frameworks(provider=None):
available_compliance_frameworks = []
- providers = [p.value for p in Provider]
+ # Built-in compliance
+ compliance_base = f"{actual_directory}/../compliance"
if provider:
providers = [provider]
- for current_provider in providers:
- compliance_dir = f"{actual_directory}/../compliance/{current_provider}"
+ else:
+ # Scan compliance directory for all provider subdirectories
+ providers = []
+ if os.path.isdir(compliance_base):
+ for entry in os.scandir(compliance_base):
+ if entry.is_dir():
+ providers.append(entry.name)
+ for prov in providers:
+ compliance_dir = f"{compliance_base}/{prov}"
if not os.path.isdir(compliance_dir):
continue
with os.scandir(compliance_dir) as files:
@@ -99,7 +135,8 @@ def get_available_compliance_frameworks(provider=None):
available_compliance_frameworks.append(
file.name.removesuffix(".json")
)
- # Also scan top-level compliance/ for multi-provider (universal) JSONs.
+ # Built-in multi-provider frameworks at top-level compliance/ directory.
+ # Placed before external entry points so built-ins win on name collisions.
# When a specific provider was requested, only include the framework if it
# declares support for that provider; otherwise include all universal frameworks.
compliance_root = f"{actual_directory}/../compliance"
@@ -116,6 +153,46 @@ def get_available_compliance_frameworks(provider=None):
continue
if name not in available_compliance_frameworks:
available_compliance_frameworks.append(name)
+ # External compliance via entry points; a provider may be served by
+ # several packages, so iterate every directory it contributes.
+ ep_dirs = _get_ep_compliance_dirs()
+ for prov, paths in ep_dirs.items():
+ if provider and prov != provider:
+ continue
+ for path in paths:
+ if not os.path.isdir(path):
+ continue
+ for file in os.scandir(path):
+ if file.is_file() and file.name.endswith(".json"):
+ name = file.name.removesuffix(".json")
+ if name not in available_compliance_frameworks:
+ available_compliance_frameworks.append(name)
+ # External multi-provider frameworks via the dedicated universal group;
+ # filtered by supports_provider when a provider is given.
+ for ep in importlib.metadata.entry_points(group="prowler.compliance.universal"):
+ try:
+ module = ep.load()
+ path = (
+ module.__path__[0]
+ if hasattr(module, "__path__")
+ else os.path.dirname(module.__file__)
+ )
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ continue
+ if not os.path.isdir(path):
+ continue
+ for file in os.scandir(path):
+ if file.is_file() and file.name.endswith(".json"):
+ name = file.name.removesuffix(".json")
+ if provider:
+ framework = load_compliance_framework_universal(file.path)
+ if framework is None or not framework.supports_provider(provider):
+ continue
+ if name not in available_compliance_frameworks:
+ available_compliance_frameworks.append(name)
return available_compliance_frameworks
@@ -223,24 +300,41 @@ def load_and_validate_config_file(provider: str, config_file_path: str) -> dict:
Returns:
dict: The configuration dictionary for the specified provider.
"""
+ # Imported lazily to avoid an import cycle: schemas may eventually want to
+ # import from prowler.config.config (e.g. for shared constants).
+ from prowler.config.schema.registry import SCHEMAS
+ from prowler.config.schema.validator import validate_provider_config
+
try:
with open(config_file_path, "r", encoding=encoding_format_utf_8) as f:
config_file = yaml.safe_load(f)
- # Not to introduce a breaking change, allow the old format config file without any provider keys
- # and a new format with a key for each provider to include their configuration values within.
- if any(
- key in config_file
- for key in ["aws", "gcp", "azure", "kubernetes", "m365"]
+ # Namespaced format: each provider has its own top-level key.
+ # Works for every built-in and every external plugin without a hardcoded list.
+ # Flat legacy format is AWS-only (historical, pre-multicloud). We identify it
+ # by the absence of nested-dict top-level values (namespaced files always
+ # have dict values; the legacy AWS format only has primitives/lists).
+ if (
+ isinstance(config_file, dict)
+ and provider in config_file
+ and isinstance(config_file[provider], dict)
):
- config = config_file.get(provider, {})
+ config = config_file.get(provider, {}) or {}
+ elif (
+ isinstance(config_file, dict)
+ and config_file
+ and provider == "aws"
+ and not any(isinstance(v, dict) for v in config_file.values())
+ ):
+ config = config_file
else:
- config = config_file if config_file else {}
- # Not to break Azure, K8s and GCP does not support or use the old config format
- if provider in ["azure", "gcp", "kubernetes", "m365"]:
- config = {}
+ config = {}
- return config
+ return validate_provider_config(
+ provider=provider,
+ raw=config,
+ schema_cls=SCHEMAS.get(provider),
+ )
except FileNotFoundError as error:
logger.error(
diff --git a/prowler/config/config.yaml b/prowler/config/config.yaml
index a98512d720..aba7fd6481 100644
--- a/prowler/config/config.yaml
+++ b/prowler/config/config.yaml
@@ -3,6 +3,32 @@ aws:
# AWS Global Configuration
# aws.mute_non_default_regions --> Set to True to muted failed findings in non-default regions for AccessAnalyzer, GuardDuty, SecurityHub, DRS and Config
mute_non_default_regions: False
+
+ # AWS Resource Scan Limit Configuration
+ # Limits the number of resources scanned per service for services that can
+ # accumulate huge numbers of resources (EBS snapshots, backup recovery
+ # points, CloudWatch log groups, Lambda functions, ECS task definitions,
+ # CodeArtifact packages). Limits apply to resources analyzed, not findings:
+ # a selected resource can produce zero, one, or many findings. Where the AWS
+ # API supports server-side ordering the latest resources are scanned first;
+ # otherwise it is best-effort API order.
+ # Disabled by default: scan every resource unless a positive limit is configured.
+ # Set to 0 (or a negative value) to disable the limit (scan every resource).
+ # aws.max_scanned_resources_per_service --> global default for all services below
+ max_scanned_resources_per_service: 0
+ # Per-service overrides. Leave as null to fall back to the global default.
+ # aws.max_ebs_snapshots --> ec2_ebs_* checks (EBS snapshots)
+ max_ebs_snapshots: null
+ # aws.max_backup_recovery_points --> backup_recovery_point_* checks
+ max_backup_recovery_points: null
+ # aws.max_cloudwatch_log_groups --> cloudwatch_log_group_* checks
+ max_cloudwatch_log_groups: null
+ # aws.max_lambda_functions --> awslambda_function_* checks
+ max_lambda_functions: null
+ # aws.max_ecs_task_definitions --> ecs_task_definitions_* checks
+ max_ecs_task_definitions: null
+ # aws.max_codeartifact_packages --> codeartifact_packages_* checks
+ max_codeartifact_packages: null
# aws.disallowed_regions --> List of AWS regions to exclude from the scan.
# Also settable via the PROWLER_AWS_DISALLOWED_REGIONS environment variable or
# the --excluded-region CLI flag. Precedence: CLI > env var > config file.
@@ -380,6 +406,54 @@ aws:
# Minimum number of Availability Zones that an ELBv2 must be in
elbv2_min_azs: 2
+ # AWS Post-Quantum TLS Configuration
+ # aws.acmpca_certificate_authority_pqc_key_algorithm
+ # Allowed post-quantum key algorithms for AWS Private CA certificate authorities
+ acmpca_pqc_key_algorithms:
+ - "ML_DSA_44"
+ - "ML_DSA_65"
+ - "ML_DSA_87"
+ # aws.cloudfront_distributions_pqc_tls_enabled
+ # Allowed CloudFront MinimumProtocolVersion values that enable post-quantum hybrid key exchange
+ cloudfront_pqc_min_protocol_versions:
+ - "TLSv1.3_2025"
+ # aws.apigateway_domain_name_pqc_tls_enabled
+ # Allowed post-quantum TLS security policies for API Gateway custom domain names
+ apigateway_pqc_tls_allowed_policies:
+ - "SecurityPolicy_TLS13_1_2_FIPS_PFS_PQ_2025_09"
+ - "SecurityPolicy_TLS13_1_2_PFS_PQ_2025_09"
+ - "SecurityPolicy_TLS13_1_2_PQ_2025_09"
+
+ # aws.elbv2_listener_pqc_tls_enabled
+ # Allowed post-quantum TLS security policies for ELBv2 HTTPS/TLS listeners
+ elbv2_listener_pqc_tls_allowed_policies:
+ - "ELBSecurityPolicy-TLS13-1-2-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext1-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext2-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-3-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext0-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext1-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext2-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Res-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-3-FIPS-PQ-2025-09"
+
+ # aws.rolesanywhere_trust_anchor_pqc_pki
+ # Allowed post-quantum key algorithms for AWS Private CAs backing IAM Roles Anywhere trust anchors
+ rolesanywhere_pqc_pca_key_algorithms:
+ - "ML_DSA_44"
+ - "ML_DSA_65"
+ - "ML_DSA_87"
+
+ # AWS Post-Quantum SSH Key Exchange Configuration
+ # aws.transfer_server_pqc_ssh_kex_enabled
+ # Allowed AWS Transfer Family security policies with post-quantum SSH key exchange
+ transfer_pqc_ssh_allowed_policies:
+ - "TransferSecurityPolicy-2025-03"
+ - "TransferSecurityPolicy-FIPS-2025-03"
+ - "TransferSecurityPolicy-AS2Restricted-2025-07"
+
# AWS Elasticache Configuration
# aws.elasticache_redis_cluster_backup_enabled
# Minimum number of days that a Redis cluster must have backups retention period
@@ -390,6 +464,27 @@ aws:
# Patterns to ignore in the secrets checks
secrets_ignore_patterns: []
+ # aws.awslambda_function_no_secrets_in_code
+ # Glob patterns of file names inside the Lambda deployment package to skip
+ # when scanning for secrets. Useful to suppress known false positives such
+ # as .NET dependency manifests.
+ # Example:
+ # secrets_ignore_files:
+ # - "*.deps.json"
+ # WARNING: use at your own risk. Any file whose name matches one of these
+ # patterns is fully excluded from secret scanning, so a real secret placed
+ # in such a file will NOT be detected. Keep patterns as narrow and specific
+ # as possible; this is not recommended unless you have confirmed the matched
+ # files only ever contain false positives.
+ secrets_ignore_files: []
+
+ # Validate discovered secrets by checking whether they are live against the
+ # provider APIs. WARNING: this makes outbound network calls that authenticate
+ # with the discovered secret itself; the credential is exercised against the
+ # provider and the call will appear in the audited account's logs (and may
+ # trigger its monitoring). Disabled by default (scans stay fully offline).
+ secrets_validate: False
+
# AWS Secrets Manager Configuration
# aws.secretsmanager_secret_unused
# Maximum number of days a secret can be unused
@@ -403,36 +498,17 @@ aws:
# Minimum retention period in hours for Kinesis streams
min_kinesis_stream_retention_hours: 168 # 7 days
- # Detect Secrets plugin configuration
- detect_secrets_plugins: [
- {"name": "ArtifactoryDetector"},
- {"name": "AWSKeyDetector"},
- {"name": "AzureStorageKeyDetector"},
- {"name": "BasicAuthDetector"},
- {"name": "CloudantDetector"},
- {"name": "DiscordBotTokenDetector"},
- {"name": "GitHubTokenDetector"},
- {"name": "GitLabTokenDetector"},
- {"name": "Base64HighEntropyString", "limit": 6.0},
- {"name": "HexHighEntropyString", "limit": 3.0},
- {"name": "IbmCloudIamDetector"},
- {"name": "IbmCosHmacDetector"},
- # {"name": "IPPublicDetector"}, https://github.com/Yelp/detect-secrets/pull/885
- {"name": "JwtTokenDetector"},
- {"name": "KeywordDetector"},
- {"name": "MailchimpDetector"},
- {"name": "NpmDetector"},
- {"name": "OpenAIDetector"},
- {"name": "PrivateKeyDetector"},
- {"name": "PypiTokenDetector"},
- {"name": "SendGridDetector"},
- {"name": "SlackDetector"},
- {"name": "SoftlayerDetector"},
- {"name": "SquareOAuthDetector"},
- {"name": "StripeDetector"},
- # {"name": "TelegramBotTokenDetector"}, https://github.com/Yelp/detect-secrets/pull/878
- {"name": "TwilioKeyDetector"},
- ]
+ # AWS S3 Configuration
+ # aws.s3_bucket_object_public
+ # This check performs a spot-check by sampling object ACLs within a bucket, so
+ # it is disabled by default. For complete coverage, rely on s3_bucket_acl_prohibited
+ # which enforces BucketOwnerEnforced Object Ownership (AWS's recommended approach).
+ # Set s3_bucket_object_public_enabled to True to opt in.
+ s3_bucket_object_public_enabled: False
+ # Maximum number of objects to list per bucket (upper bound for the sampling pool)
+ s3_bucket_object_public_max_objects: 100
+ # Number of objects to randomly sample from the listed pool and inspect ACLs for
+ s3_bucket_object_public_sample_size: 3
# AWS CodeBuild Configuration
# aws.codebuild_project_uses_allowed_github_organizations
@@ -467,6 +543,18 @@ azure:
"1.3",
]
+ # Azure Storage
+ # azure.storage_smb_channel_encryption_with_secure_algorithm
+ # List of SMB channel encryption algorithms allowed on file shares. A storage
+ # account passes only if every enabled algorithm is in this list. Defaults to
+ # the value required by CIS (AES-256-GCM only, excluding weaker AES-128 ciphers).
+ recommended_smb_channel_encryption_algorithms:
+ [
+ "AES-256-GCM",
+ # "AES-128-CCM",
+ # "AES-128-GCM",
+ ]
+
# Azure Virtual Machines
# azure.vm_desired_sku_size
# List of desired VM SKU sizes that are allowed in the organization
@@ -537,6 +625,9 @@ gcp:
# GCP Storage Sufficient Retention Period
# gcp.cloudstorage_bucket_sufficient_retention_period
storage_min_retention_days: 90
+ # GCP Secret Manager Rotation Period
+ # gcp.secretmanager_secret_rotation_enabled
+ secretmanager_max_rotation_days: 90
# Kubernetes Configuration
kubernetes:
@@ -657,3 +748,76 @@ okta:
# 15 per DISA STIG V-273186 (OKTA-APP-000020); raise it only with an
# explicit risk acceptance.
okta_max_session_idle_minutes: 15
+ # okta.signon_global_session_lifetime_18h
+ # Maximum acceptable Global Session lifetime, in minutes. Defaults to
+ # 18h (1080); raise it only with an explicit risk acceptance.
+ okta_max_session_lifetime_minutes: 1080
+ # Okta Applications
+ # okta.application_admin_console_session_idle_timeout_15min
+ # Maximum acceptable Okta Admin Console app idle timeout, in minutes.
+ # Defaults to 15 per DISA STIG V-273187 (OKTA-APP-000025); raise it only
+ # with an explicit risk acceptance.
+ okta_admin_console_idle_timeout_max_minutes: 15
+ # Okta API rate limiting
+ # Max retries on HTTP 429. The Okta SDK sleeps until the X-Rate-Limit-Reset
+ # window before each retry, so raising this lets scans ride out more rate-limit
+ # windows on busy orgs instead of failing with partial data. SDK default is 2.
+ okta_max_retries: 5
+ # Per-request timeout in seconds. In the Okta SDK this value plays a DUAL role:
+ # it is both the per-HTTP-call socket timeout AND the total wall-clock budget
+ # across the whole retry+backoff loop. It defaults to 300 (not 0) because it is
+ # the only effective hang guard, and 300s is the smallest value that still lets
+ # all okta_max_retries rate-limit waits (~60s Okta reset windows) complete
+ # without being cut short. Keep it roughly >= okta_max_retries * 60 if you
+ # raise okta_max_retries.
+ okta_request_timeout: 300
+ # Maximum aggregate Okta API requests per second. Prowler paces all requests
+ # through a shared limiter so scans stay under Okta's rate limits proactively,
+ # rather than relying on the 429 retry above as a safety net. Okta enforces
+ # limits per endpoint, so this is a deliberately simple global cap; lower it if
+ # scans still hit limits, raise it to scan faster. Set to 0 to disable. Valid
+ # range: 0 or 0.1..100 — non-zero rates below 0.1 are rejected because they
+ # would make a scan impractically slow.
+ okta_requests_per_second: 4
+ # Okta Users
+ # okta.user_inactivity_automation_35d_enabled
+ # Maximum number of days a user can stay inactive before the
+ # inactivity-automation check flags the org. Defaults to 35.
+ okta_user_inactivity_max_days: 35
+ # Okta Identity Providers
+ # okta.idp_smart_card_dod_approved_ca
+ # Extra regex patterns matched against a Smart Card IdP certificate issuer
+ # DN to recognise a DOD-approved CA, on top of the built-in `OU=DoD` /
+ # `OU=ECA` patterns.
+ okta_dod_approved_ca_issuer_patterns: []
+
+alibabacloud:
+ # alibabacloud.cs_kubernetes_cluster_check_recent / cs_kubernetes_cluster_check_weekly
+ # Maximum number of days an ACK cluster can go without a security check
+ # before being flagged. Defaults to 7.
+ max_cluster_check_days: 7
+ # alibabacloud.ram_user_console_access_unused
+ # Days a RAM user's console access can stay unused before being flagged.
+ # Defaults to 90.
+ max_console_access_days: 90
+ # alibabacloud.sls_logstore_retention_period
+ # Minimum required SLS log store retention, in days. Defaults to 365.
+ min_log_retention_days: 365
+ # alibabacloud.rds_instance_sql_audit_retention
+ # Minimum required RDS SQL audit log retention, in days. Defaults to 180.
+ min_rds_audit_retention_days: 180
+
+openstack:
+ # openstack.image_not_shared_with_multiple_projects
+ # Maximum number of accepted project members a shared image may have before
+ # being flagged. Defaults to 5.
+ image_sharing_threshold: 5
+ # openstack.<compute|blockstorage|objectstorage>_*_metadata_sensitive_data
+ # Regex patterns whose matches are excluded from secret scanning of
+ # resource metadata.
+ secrets_ignore_patterns: []
+
+# E2E Networks Configuration
+e2enetworks:
+ # load_balancer_bitninja_enabled
+ require_bitninja_on_load_balancers: false
diff --git a/prowler/config/e2enetworks_mutelist_example.yaml b/prowler/config/e2enetworks_mutelist_example.yaml
new file mode 100644
index 0000000000..40443287a6
--- /dev/null
+++ b/prowler/config/e2enetworks_mutelist_example.yaml
@@ -0,0 +1,23 @@
+### Account, Check and/or Region can be * to apply for all the cases.
+### Account == * (E2E Networks findings are matched by resource, so use * to apply to all)
+### Region == <E2E Networks location, e.g. Delhi> or * for all locations
+### Resources and tags are lists that can have either Regex or Keywords.
+### Tags is an optional list that matches on tuples of 'key=value' and are "ANDed" together.
+### Use an alternation Regex to match one of multiple tags with "ORed" logic.
+### For each check you can except Accounts, Regions, Resources and/or Tags.
+########################### MUTELIST EXAMPLE ###########################
+Mutelist:
+ Accounts:
+ "*":
+ Checks:
+ "node_public_ip_not_assigned":
+ Regions:
+ - "Delhi"
+ Resources:
+ - "example-node-id"
+ - "bastion-.*"
+ "storage_bucket_public_access_disabled":
+ Regions:
+ - "*"
+ Resources:
+ - "public-assets-bucket"
diff --git a/prowler/config/linode_mutelist_example.yaml b/prowler/config/linode_mutelist_example.yaml
new file mode 100644
index 0000000000..1b08ab6fda
--- /dev/null
+++ b/prowler/config/linode_mutelist_example.yaml
@@ -0,0 +1,18 @@
+### Account, Check and/or Region can be * to apply for all the cases.
+### Account == <Linode Account UUID>
+### Region == * (Linode is non-regional)
+### Resources and tags are lists that can have either Regex or Keywords.
+### Tags is an optional list that matches on tuples of 'key=value' and are "ANDed" together.
+### Use an alternation Regex to match one of multiple tags with "ORed" logic.
+### For each check you can except Accounts, Regions, Resources and/or Tags.
+########################### MUTELIST EXAMPLE ###########################
+Mutelist:
+ Accounts:
+ "example-account-uuid":
+ Checks:
+ "administration_user_2fa_enabled":
+ Regions:
+ - "*"
+ Resources:
+ - "example-user@example.com"
+ - "another-user@example.com"
diff --git a/prowler/config/scan_config_schema.py b/prowler/config/scan_config_schema.py
new file mode 100644
index 0000000000..431c4cec60
--- /dev/null
+++ b/prowler/config/scan_config_schema.py
@@ -0,0 +1,241 @@
+"""Bridge between the Pydantic-based provider schemas in
+`prowler.config.schema` and the Prowler App backend (Django) + UI.
+
+The SDK runtime is intentionally LENIENT: invalid keys are dropped with a
+warning and downstream checks fall back to their defaults
+(`prowler.config.schema.validator.validate_provider_config`).
+
+The Prowler App, however, needs to surface those errors to the user when
+they save a Scan Config from the UI, and to expose the schema as JSON so
+the UI can validate live with `ajv`. This module provides:
+
+- `validate_and_normalize_scan_config(payload)` — STRICT: returns
+ ``(normalized, errors)``. When ``errors`` is non-empty the normalized
+ dictionary is empty so callers never persist a partially validated
+ configuration. On success the normalized payload is JSON-serializable
+ (`model_dump(mode="json", exclude_unset=True)`), so the API can store
+ it directly in a Django ``JSONField`` and consume it at scan time
+ without re-running schema validation.
+
+- `validate_scan_config(payload)` — thin backward-compatible wrapper that
+ returns only the validation errors, preserved for callers that don't
+ need the normalized payload.
+
+- `SCAN_CONFIG_SCHEMA` — aggregated JSON Schema derived from the Pydantic
+ models via `model_json_schema()`. Served by the `/scan-configs/schema`
+ endpoint and consumed by the UI editor for in-editor live validation.
+"""
+
+import json
+from functools import lru_cache
+from typing import Any
+
+from pydantic import ValidationError
+
+from prowler.config.schema.registry import SCHEMAS
+from prowler.lib.check.check import list_services
+from prowler.lib.check.models import CheckMetadata
+
+# Pydantic v2 prefixes messages emitted from a ``field_validator`` that
+# raises ``ValueError`` with this string. Strip it so the message that
+# reaches the UI is the one the validator actually wrote.
+_PYDANTIC_VALUE_ERROR_PREFIX = "Value error, "
+
+
+@lru_cache(maxsize=None)
+def _get_provider_check_ids(provider: str) -> frozenset[str]:
+ """Return cached check identifiers for a provider."""
+ return frozenset(CheckMetadata.get_bulk(provider))
+
+
+@lru_cache(maxsize=None)
+def _get_provider_services(provider: str) -> frozenset[str]:
+ """Return cached service identifiers for a provider."""
+ return frozenset(list_services(provider))
+
+
+def _format_loc(loc: tuple) -> str:
+ """Render a Pydantic error location as a dot-separated path.
+
+ Integer elements (array indices) are formatted as `[idx]` appended to the
+ previous component. String elements are joined with dots. An empty location
+ is rendered as `<root>`.
+
+ Examples:
+ ("aws", "regions", 0) -> "aws.regions[0]"
+ ("aws", "threshold") -> "aws.threshold"
+ () -> "<root>"
+ """
+ parts: list[str] = []
+ for piece in loc:
+ if isinstance(piece, int):
+ if parts:
+ parts[-1] = f"{parts[-1]}[{piece}]"
+ else:
+ parts.append(f"[{piece}]")
+ else:
+ parts.append(str(piece))
+ return ".".join(parts) if parts else "<root>"
+
+
+def validate_and_normalize_scan_config(
+ payload: Any,
+) -> tuple[dict, list[dict[str, str]]]:
+ """Strict validation and normalization of a scan configuration payload.
+
+ Returns ``(normalized, errors)``:
+
+ - ``normalized`` is a JSON-serializable dict that mirrors the layout of
+ ``prowler/config/config.yaml`` (keyed by provider type). Registered
+ provider sections are dumped from their Pydantic models with
+ ``mode="json"`` (so the API can persist the result in a Django
+ ``JSONField``) and ``exclude_unset=True`` (so omitted defaults are
+ not injected into pre-existing configurations). Unknown provider
+ sections and unknown keys inside registered sections are preserved
+ untouched for forward compatibility with plugin-provided keys.
+ - ``errors`` is a list of ``{"path": <dotted-path>, "message": <str>}``
+ entries, one per schema or exclusion-catalog violation. When any error
+ is present the normalized dictionary is returned empty so the caller
+ never persists a partially validated configuration.
+
+ The input payload is never mutated.
+ """
+ if not isinstance(payload, dict):
+ return {}, [
+ {
+ "path": "<root>",
+ "message": "Scan config must be a mapping with provider sections.",
+ }
+ ]
+
+ errors: list[dict[str, str]] = []
+ normalized: dict[str, Any] = {}
+
+ for provider, section in payload.items():
+ # Reject non-string provider keys so distinct entries like ``123``
+ # and ``"123"`` don't collide after ``str()`` in the normalized dict.
+ # YAML always produces string keys at this level; anything else
+ # comes from a hand-built payload and is a caller bug.
+ if not isinstance(provider, str):
+ errors.append(
+ {
+ "path": repr(provider),
+ "message": "provider keys must be strings.",
+ }
+ )
+ continue
+
+ provider_key = provider
+ schema_cls = SCHEMAS.get(provider_key)
+ if schema_cls is None:
+ # Unknown provider type: tolerated, but only when its contents
+ # are already JSON-serializable. The API persists the returned
+ # payload in a Django ``JSONField`` and would blow up at write
+ # time if we let a ``set()`` or similar through here.
+ try:
+ json.dumps(section)
+ except (TypeError, ValueError) as exc:
+ errors.append(
+ {
+ "path": provider_key,
+ "message": (
+ "unknown provider section is not JSON-serializable: "
+ f"{exc}"
+ ),
+ }
+ )
+ continue
+ normalized[provider_key] = section
+ continue
+ if not isinstance(section, dict):
+ errors.append(
+ {
+ "path": provider_key,
+ "message": "section must be a mapping.",
+ }
+ )
+ continue
+ try:
+ model = schema_cls.model_validate(section)
+ except ValidationError as exc:
+ for err in exc.errors():
+ loc = err.get("loc") or ()
+ path = _format_loc((provider_key, *loc))
+ message = err.get("msg", "validation error")
+ # Only strip on the specific error type that pydantic
+ # prefixes — a legitimate future message that happens to
+ # start with "Value error, " keeps its text intact.
+ if err.get("type") == "value_error" and message.startswith(
+ _PYDANTIC_VALUE_ERROR_PREFIX
+ ):
+ message = message[len(_PYDANTIC_VALUE_ERROR_PREFIX) :]
+ errors.append({"path": path, "message": message})
+ continue
+
+ if model.excluded_checks:
+ available_checks = _get_provider_check_ids(provider_key)
+ for index, check in enumerate(model.excluded_checks):
+ if check not in available_checks:
+ errors.append(
+ {
+ "path": f"{provider_key}.excluded_checks[{index}]",
+ "message": (
+ f"Unknown check '{check}' for provider "
+ f"'{provider_key}'."
+ ),
+ }
+ )
+
+ if model.excluded_services:
+ available_services = _get_provider_services(provider_key)
+ for index, service in enumerate(model.excluded_services):
+ if service not in available_services:
+ errors.append(
+ {
+ "path": f"{provider_key}.excluded_services[{index}]",
+ "message": (
+ f"Unknown service '{service}' for provider "
+ f"'{provider_key}'."
+ ),
+ }
+ )
+
+ normalized[provider_key] = model.model_dump(mode="json", exclude_unset=True)
+
+ if errors:
+ return {}, errors
+ return normalized, []
+
+
+def validate_scan_config(payload: Any) -> list[dict]:
+ """Backward-compatible wrapper returning only validation errors.
+
+ Preserved for callers that only need the strict-validation error list
+ (e.g. the DRF serializer that turns each entry into a
+ ``ValidationError``). New callers should prefer
+ :func:`validate_and_normalize_scan_config` to also receive the
+ normalized payload.
+ """
+ _, errors = validate_and_normalize_scan_config(payload)
+ return errors
+
+
+def _build_aggregated_schema() -> dict:
+ """Compose one JSON Schema per provider into a single top-level schema.
+
+ The output mirrors the layout of `prowler/config/config.yaml` (a mapping
+ keyed by provider type) and is what the UI consumes via `ajv`.
+ """
+ properties: dict[str, dict] = {}
+ for provider, schema_cls in SCHEMAS.items():
+ properties[provider] = schema_cls.model_json_schema()
+ return {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "title": "Prowler Scan Config",
+ "type": "object",
+ "additionalProperties": True,
+ "properties": properties,
+ }
+
+
+SCAN_CONFIG_SCHEMA: dict = _build_aggregated_schema()
diff --git a/tests/lib/outputs/jira/__init__.py b/prowler/config/schema/__init__.py
similarity index 100%
rename from tests/lib/outputs/jira/__init__.py
rename to prowler/config/schema/__init__.py
diff --git a/prowler/config/schema/alibabacloud.py b/prowler/config/schema/alibabacloud.py
new file mode 100644
index 0000000000..104f8a3556
--- /dev/null
+++ b/prowler/config/schema/alibabacloud.py
@@ -0,0 +1,54 @@
+"""Alibaba Cloud provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class AlibabaCloudProviderConfig(ProviderConfigBase):
+ """Alibaba Cloud provider configuration schema.
+
+ Bounds the retention and staleness thresholds consumed by the Alibaba
+ Cloud checks. Every field is optional: when omitted (or dropped for being
+ out of range) the check falls back to its own default via
+ ``audit_config.get(key, default)``.
+ """
+
+ max_cluster_check_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=365,
+ description=(
+ "Maximum number of days an ACK cluster can go without a security "
+ "check before being flagged. Range: 1..365 (defaults to 7)."
+ ),
+ )
+ max_console_access_days: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=180,
+ description=(
+ "Days a RAM user's console access can stay unused before being "
+ "flagged. Range: 30..180 (defaults to 90)."
+ ),
+ )
+ min_log_retention_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=3650,
+ description=(
+ "Minimum required SLS log store retention, in days. Range: "
+ "1..3650 (defaults to 365)."
+ ),
+ )
+ min_rds_audit_retention_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=3650,
+ description=(
+ "Minimum required RDS SQL audit log retention, in days. Range: "
+ "1..3650 (defaults to 180)."
+ ),
+ )
diff --git a/prowler/config/schema/aws.py b/prowler/config/schema/aws.py
new file mode 100644
index 0000000000..7ac12d60de
--- /dev/null
+++ b/prowler/config/schema/aws.py
@@ -0,0 +1,492 @@
+"""AWS provider config schema.
+
+Bounds on every field are intentionally conservative: they are not the
+absolute service maxima but the values that produce a useful security
+check. A user is free to keep the built-in default by omitting the key —
+out-of-range values are dropped with a warning at SDK runtime, and
+rejected at the Prowler App backend.
+
+Whenever an upper bound is uncertain, the cap is set to a value that
+still keeps the check meaningful (e.g. a 10-year window for date-based
+thresholds) and avoids ints that obviously break downstream maths
+(`min_kinesis_stream_retention_hours = 99999`).
+"""
+
+from typing import Annotated, Literal, Optional
+
+from pydantic import AfterValidator, BeforeValidator, Field
+
+from prowler.config.schema.base import ProviderConfigBase
+from prowler.config.schema.validators import (
+ make_dotted_version_validator,
+ validate_ip_networks,
+ validate_port_range,
+)
+
+# ---- Reusable constants -----------------------------------------------------
+
+# CloudWatch Logs only accepts these retention values (in days). Anything else
+# is silently coerced to the next valid value by the API — we reject upfront.
+_CLOUDWATCH_RETENTION_DAYS = (
+ 1,
+ 3,
+ 5,
+ 7,
+ 14,
+ 30,
+ 60,
+ 90,
+ 120,
+ 150,
+ 180,
+ 365,
+ 400,
+ 545,
+ 731,
+ 1096,
+ 1827,
+ 2192,
+ 2557,
+ 2922,
+ 3288,
+ 3653,
+)
+
+_VALID_CW_RETENTION_LITERAL = Literal[
+ 1,
+ 3,
+ 5,
+ 7,
+ 14,
+ 30,
+ 60,
+ 90,
+ 120,
+ 150,
+ 180,
+ 365,
+ 400,
+ 545,
+ 731,
+ 1096,
+ 1827,
+ 2192,
+ 2557,
+ 2922,
+ 3288,
+ 3653,
+]
+
+
+# ---- Custom validators ------------------------------------------------------
+
+
+# Reusable validators shared across providers (see schema/validators.py).
+_validate_port_range = validate_port_range
+_validate_trusted_ips = validate_ip_networks
+# "1.4.0" style strings (used by Fargate platform versions).
+_validate_semver = make_dotted_version_validator(3, 3)
+# "1.28" style strings (EKS minor versions).
+_validate_eks_minor = make_dotted_version_validator(2, 2)
+
+
+def _validate_account_ids(v: Optional[list[str]]) -> Optional[list[str]]:
+ if v is None:
+ return v
+ for account_id in v:
+ if not (account_id.isdigit() and len(account_id) == 12):
+ raise ValueError(
+ f"trusted_account_ids entry {account_id!r} is not a 12-digit AWS account id"
+ )
+ return v
+
+
+def _reject_bool_resource_limit(v):
+ if isinstance(v, bool):
+ raise ValueError("resource scan limits must be integers, not booleans")
+ return v
+
+
+ResourceScanLimit = Annotated[
+ Optional[int], BeforeValidator(_reject_bool_resource_limit)
+]
+
+
+# ---- Main schema ------------------------------------------------------------
+
+
+class AWSProviderConfig(ProviderConfigBase):
+ # --- Resource scan limits ---------------------------------------------
+ max_scanned_resources_per_service: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Global resource scan limit for high-volume AWS services. Use 0 or -1 to disable.",
+ )
+ max_ebs_snapshots: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for EBS snapshots. Use 0 or -1 to disable.",
+ )
+ max_backup_recovery_points: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for AWS Backup recovery points. Use 0 or -1 to disable.",
+ )
+ max_cloudwatch_log_groups: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for CloudWatch log groups. Use 0 or -1 to disable.",
+ )
+ max_lambda_functions: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for Lambda functions. Use 0 or -1 to disable.",
+ )
+ max_ecs_task_definitions: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for ECS task definitions. Use 0 or -1 to disable.",
+ )
+ max_codeartifact_packages: ResourceScanLimit = Field(
+ default=None,
+ ge=-1,
+ le=1_000_000,
+ description="Resource scan limit for CodeArtifact packages. Use 0 or -1 to disable.",
+ )
+
+ # --- IAM ---------------------------------------------------------------
+ mute_non_default_regions: Optional[bool] = None
+ disallowed_regions: Optional[list[str]] = None
+ max_unused_access_keys_days: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=180,
+ description=(
+ "Days an IAM user access key can stay unused before being flagged. "
+ "Range: 30..180 days (CIS AWS 1.13 recommends 45; NIST IA-5 ≤90)."
+ ),
+ )
+ max_console_access_days: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=180,
+ description=(
+ "Days an IAM console password can stay unused before being flagged. "
+ "Range: 30..180 days (CIS AWS 1.12 recommends 45)."
+ ),
+ )
+ max_unused_sagemaker_access_days: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=180,
+ description=(
+ "Days a SageMaker user access key can stay unused. Range: 7..180 "
+ "(SageMaker tokens are usually high-privilege over S3/KMS)."
+ ),
+ )
+
+ # --- EC2 ---------------------------------------------------------------
+ shodan_api_key: Optional[str] = Field(
+ default=None,
+ max_length=512,
+ description="API key for Shodan lookups on EC2 public IPs.",
+ )
+ max_security_group_rules: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1000,
+ description="Max ingress+egress rules per security group. AWS hard limit is 1000.",
+ )
+ max_ec2_instance_age_in_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1095,
+ description=(
+ "Days an EC2 instance can run before being flagged as old. "
+ "Range: 1..1095 (3 years; instances should be refreshed for patching "
+ "per NIST CM-3 — anything older is a security smell)."
+ ),
+ )
+ ec2_allowed_interface_types: Optional[list[str]] = None
+ ec2_allowed_instance_owners: Optional[list[str]] = None
+ ec2_high_risk_ports: Annotated[
+ Optional[list[int]], AfterValidator(_validate_port_range)
+ ] = Field(
+ default=None,
+ description="TCP/UDP ports considered high-risk when reachable from the Internet (1..65535; port 0 is reserved).",
+ )
+
+ # --- ECS ---------------------------------------------------------------
+ fargate_linux_latest_version: Annotated[
+ Optional[str], AfterValidator(_validate_semver)
+ ] = Field(default=None, description="Fargate Linux platform version (X.Y.Z).")
+ fargate_windows_latest_version: Annotated[
+ Optional[str], AfterValidator(_validate_semver)
+ ] = Field(default=None, description="Fargate Windows platform version (X.Y.Z).")
+
+ # --- Cross-account trust ----------------------------------------------
+ trusted_account_ids: Annotated[
+ Optional[list[str]], AfterValidator(_validate_account_ids)
+ ] = Field(
+ default=None,
+ description="Additional 12-digit AWS account IDs trusted by cross-account checks.",
+ )
+ trusted_ips: Annotated[
+ Optional[list[str]], AfterValidator(_validate_trusted_ips)
+ ] = Field(
+ default=None,
+ description="IPv4/IPv6 addresses or CIDR ranges that are NOT considered public.",
+ )
+
+ # --- CloudWatch / CloudFormation --------------------------------------
+ log_group_retention_days: Optional[_VALID_CW_RETENTION_LITERAL] = Field(
+ default=None,
+ description=(
+ "Required CloudWatch Logs retention in days. Must match one of the "
+ f"values accepted by the AWS API: {list(_CLOUDWATCH_RETENTION_DAYS)}."
+ ),
+ )
+ recommended_cdk_bootstrap_version: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=100,
+ description="Min CDK bootstrap version expected on the account.",
+ )
+
+ # --- AppStream --------------------------------------------------------
+ max_idle_disconnect_timeout_in_seconds: Optional[int] = Field(
+ default=None,
+ ge=60,
+ le=1800,
+ description=(
+ "AppStream idle disconnect timeout (seconds). Range: 60..1800 "
+ "(NIST AC-12: sensitive sessions ≤15 min — cap at 30 min)."
+ ),
+ )
+ max_disconnect_timeout_in_seconds: Optional[int] = Field(
+ default=None,
+ ge=60,
+ le=3600,
+ description="AppStream disconnect timeout (seconds). Range: 60..3600.",
+ )
+ max_session_duration_seconds: Optional[int] = Field(
+ default=None,
+ ge=600,
+ le=86400,
+ description=(
+ "AppStream max session duration (seconds). Range: 600..86400 "
+ "(10 min .. 24 h — AWS AppStream hard limit per session)."
+ ),
+ )
+
+ # --- Lambda -----------------------------------------------------------
+ obsolete_lambda_runtimes: Optional[list[str]] = None
+ lambda_min_azs: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=6,
+ description="Min number of AZs a VPC-bound Lambda must span. Range: 1..6.",
+ )
+
+ # --- Organizations ----------------------------------------------------
+ organizations_enabled_regions: Optional[list[str]] = None
+ organizations_trusted_delegated_administrators: Annotated[
+ Optional[list[str]], AfterValidator(_validate_account_ids)
+ ] = None
+ organizations_trusted_ids: Optional[list[str]] = None
+
+ # --- ECR --------------------------------------------------------------
+ ecr_repository_vulnerability_minimum_severity: Optional[
+ Literal["CRITICAL", "HIGH", "MEDIUM", "LOW", "INFORMATIONAL"]
+ ] = Field(
+ default=None,
+ description="Highest severity tolerated for ECR images.",
+ )
+
+ # --- Trusted Advisor --------------------------------------------------
+ verify_premium_support_plans: Optional[bool] = None
+
+ # --- CloudTrail threat detection: privilege escalation ----------------
+ threat_detection_privilege_escalation_threshold: Optional[float] = Field(
+ default=None,
+ ge=0.0,
+ le=1.0,
+ description="Fraction of suspicious actions that triggers the priv-esc detection.",
+ )
+ threat_detection_privilege_escalation_minutes: Optional[int] = Field(
+ default=None,
+ ge=5,
+ le=43200,
+ description=(
+ "Lookback window (minutes) for priv-esc detection. Range: 5..43200 "
+ "(under 5 min the signal is dominated by false positives)."
+ ),
+ )
+ threat_detection_privilege_escalation_actions: Optional[list[str]] = None
+
+ # --- CloudTrail threat detection: enumeration -------------------------
+ threat_detection_enumeration_threshold: Optional[float] = Field(
+ default=None,
+ ge=0.0,
+ le=1.0,
+ description="Fraction of suspicious actions that triggers the enumeration detection.",
+ )
+ threat_detection_enumeration_minutes: Optional[int] = Field(
+ default=None,
+ ge=5,
+ le=43200,
+ description="Lookback window (minutes) for enumeration detection. Range: 5..43200.",
+ )
+ threat_detection_enumeration_actions: Optional[list[str]] = None
+
+ # --- CloudTrail threat detection: LLM jacking -------------------------
+ threat_detection_llm_jacking_threshold: Optional[float] = Field(
+ default=None,
+ ge=0.0,
+ le=1.0,
+ description="Fraction of suspicious actions that triggers the LLM-jacking detection.",
+ )
+ threat_detection_llm_jacking_minutes: Optional[int] = Field(
+ default=None,
+ ge=5,
+ le=43200,
+ description="Lookback window (minutes) for LLM-jacking detection. Range: 5..43200.",
+ )
+ threat_detection_llm_jacking_actions: Optional[list[str]] = None
+
+ # --- RDS --------------------------------------------------------------
+ check_rds_instance_replicas: Optional[bool] = None
+
+ # --- ACM --------------------------------------------------------------
+ days_to_expire_threshold: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=365,
+ description=(
+ "Days before certificate expiration to flag. Range: 7..365 "
+ "(PCI-DSS 4.2.1.1: alert ≥30 days before expiry; <7 days is too "
+ "tight to actually act on)."
+ ),
+ )
+ insecure_key_algorithms: Optional[list[str]] = None
+
+ # --- EKS --------------------------------------------------------------
+ eks_required_log_types: Optional[
+ list[
+ Literal[
+ "api",
+ "audit",
+ "authenticator",
+ "controllerManager",
+ "scheduler",
+ ]
+ ]
+ ] = Field(
+ default=None,
+ description="EKS control plane log types that must be enabled.",
+ )
+ eks_cluster_oldest_version_supported: Annotated[
+ Optional[str], AfterValidator(_validate_eks_minor)
+ ] = Field(
+ default=None,
+ description='Minimum supported EKS minor version, expected as "X.Y".',
+ )
+
+ # --- CodeBuild --------------------------------------------------------
+ excluded_sensitive_environment_variables: Optional[list[str]] = None
+ codebuild_github_allowed_organizations: Optional[list[str]] = None
+
+ # --- ELB / ELBv2 ------------------------------------------------------
+ elb_min_azs: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=6,
+ description="Min AZs a Classic ELB must span. Range: 1..6.",
+ )
+ elbv2_min_azs: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=6,
+ description="Min AZs an Application/Network LB must span. Range: 1..6.",
+ )
+ elbv2_listener_pqc_tls_allowed_policies: Optional[list[str]] = Field(
+ default=None,
+ description="ELBv2 SSL policies that satisfy the PQ TLS listener check.",
+ )
+
+ # --- ElastiCache -----------------------------------------------------
+ minimum_snapshot_retention_period: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=35,
+ description="Days an ElastiCache backup must be retained. Range: 1..35 (service hard limit).",
+ )
+
+ # --- Secrets ---------------------------------------------------------
+ secrets_ignore_patterns: Optional[list[str]] = None
+ secrets_ignore_files: Optional[list[str]] = None
+ secrets_validate: Optional[bool] = Field(
+ default=None,
+ description=(
+ "Validate discovered secrets against the provider APIs (live check). "
+ "Makes outbound network calls that authenticate with the discovered "
+ "secret. Disabled by default."
+ ),
+ )
+ max_days_secret_unused: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=365,
+ description="Days a Secrets Manager secret can stay unused. Range: 7..365.",
+ )
+ max_days_secret_unrotated: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=180,
+ description=(
+ "Days a Secrets Manager secret can go without rotation. Range: 1..180 "
+ "(NIST IA-5: rotate quarterly; CIS recommends ≤90)."
+ ),
+ )
+
+ # --- Kinesis ---------------------------------------------------------
+ min_kinesis_stream_retention_hours: Optional[int] = Field(
+ default=None,
+ ge=24,
+ le=8760,
+ description="Hours of Kinesis stream retention. Range: 24..8760 (1 day .. 1 year).",
+ )
+
+ # --- S3 --------------------------------------------------------------
+ s3_bucket_object_public_enabled: Optional[bool] = Field(
+ default=None,
+ description=(
+ "Enable the s3_bucket_object_public spot-check, which samples object "
+ "ACLs per bucket. Disabled by default because it lists and reads object "
+ "ACLs, which is expensive on large buckets."
+ ),
+ )
+ s3_bucket_object_public_max_objects: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1000,
+ description=(
+ "Max objects to list per bucket as the sampling pool. Range: 1..1000 "
+ "(ListObjectsV2 returns at most 1000 keys per page)."
+ ),
+ )
+ s3_bucket_object_public_sample_size: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1000,
+ description=(
+ "Number of objects sampled from the listed pool for ACL inspection. "
+ "Range: 1..1000. Must be positive to avoid a no-op or invalid sample."
+ ),
+ )
diff --git a/prowler/config/schema/azure.py b/prowler/config/schema/azure.py
new file mode 100644
index 0000000000..75954c602b
--- /dev/null
+++ b/prowler/config/schema/azure.py
@@ -0,0 +1,83 @@
+"""Azure provider config schema with safety bounds.
+
+Bounds aim for values that produce a meaningful security check; out-of-range
+values are dropped (SDK runtime) or rejected (Prowler App backend).
+"""
+
+from typing import Annotated, Literal, Optional
+
+from pydantic import AfterValidator, Field
+
+from prowler.config.schema.base import ProviderConfigBase
+from prowler.config.schema.validators import make_dotted_version_validator
+
+# Accept "8.2", "3.12", "17" style version strings. Used by App Service
+# language version fields where the upstream APIs accept either MAJOR or
+# MAJOR.MINOR notation.
+_validate_dotted_version = make_dotted_version_validator(1, 2)
+
+
+class AzureProviderConfig(ProviderConfigBase):
+ # --- Network ---------------------------------------------------------
+ shodan_api_key: Optional[str] = Field(
+ default=None,
+ max_length=512,
+ description="API key for Shodan lookups on Azure public IPs.",
+ )
+
+ # --- Defender --------------------------------------------------------
+ defender_attack_path_minimal_risk_level: Optional[
+ Literal["Low", "Medium", "High", "Critical"]
+ ] = Field(
+ default=None,
+ description="Minimum attack-path risk level worth a notification.",
+ )
+
+ # --- App Service ----------------------------------------------------
+ php_latest_version: Annotated[
+ Optional[str], AfterValidator(_validate_dotted_version)
+ ] = Field(default=None, description='PHP minimum acceptable version, e.g. "8.2".')
+ python_latest_version: Annotated[
+ Optional[str], AfterValidator(_validate_dotted_version)
+ ] = Field(
+ default=None, description='Python minimum acceptable version, e.g. "3.12".'
+ )
+ java_latest_version: Annotated[
+ Optional[str], AfterValidator(_validate_dotted_version)
+ ] = Field(default=None, description='Java minimum acceptable version, e.g. "17".')
+
+ # --- SQL ------------------------------------------------------------
+ recommended_minimal_tls_versions: Optional[list[Literal["1.2", "1.3"]]] = Field(
+ default=None,
+ description="TLS versions accepted on Azure SQL Server.",
+ )
+
+ # --- Virtual Machines -----------------------------------------------
+ desired_vm_sku_sizes: Optional[list[str]] = None
+ vm_backup_min_daily_retention_days: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=9999,
+ description=(
+ "Min daily backup retention days. Range: 7..9999 "
+ "(Azure Backup hard limit; <7 days defeats DR/ransomware recovery)."
+ ),
+ )
+
+ # --- API Management threat detection (LLM jacking) -----------------
+ apim_threat_detection_llm_jacking_threshold: Optional[float] = Field(
+ default=None,
+ ge=0.0,
+ le=1.0,
+ description="Fraction of suspicious actions that triggers the detection.",
+ )
+ apim_threat_detection_llm_jacking_minutes: Optional[int] = Field(
+ default=None,
+ ge=5,
+ le=43200,
+ description=(
+ "Lookback window (minutes) for LLM-jacking detection. Range: 5..43200 "
+ "(under 5 min the signal is dominated by false positives)."
+ ),
+ )
+ apim_threat_detection_llm_jacking_actions: Optional[list[str]] = None
diff --git a/prowler/config/schema/base.py b/prowler/config/schema/base.py
new file mode 100644
index 0000000000..fc5a76af43
--- /dev/null
+++ b/prowler/config/schema/base.py
@@ -0,0 +1,50 @@
+from typing import Annotated
+
+from pydantic import BaseModel, ConfigDict, Field, StringConstraints, field_validator
+
+# Item type for excluded_checks / excluded_services list entries. Item
+# whitespace is stripped via ``str_strip_whitespace`` on the base
+# ``model_config`` (no second stripping implementation added here), so
+# ``min_length=1`` catches "", " ", and any all-whitespace input uniformly.
+NonEmptyScopeIdentifier = Annotated[str, StringConstraints(min_length=1)]
+
+
+class ProviderConfigBase(BaseModel):
+ """Base for every provider config schema.
+
+ ``extra="allow"`` is REQUIRED for backwards compatibility: third-party
+ check plugins frequently introduce config keys we do not know about,
+ and pre-existing user configs may carry deprecated keys. Validation
+ must never reject these.
+ """
+
+ model_config = ConfigDict(
+ extra="allow",
+ str_strip_whitespace=True,
+ validate_assignment=False,
+ )
+
+ excluded_checks: list[NonEmptyScopeIdentifier] = Field(
+ default_factory=list,
+ description="Check identifiers to exclude from the scan scope.",
+ json_schema_extra={"default": [], "uniqueItems": True},
+ )
+ excluded_services: list[NonEmptyScopeIdentifier] = Field(
+ default_factory=list,
+ description="Service identifiers to exclude from the scan scope.",
+ json_schema_extra={"default": [], "uniqueItems": True},
+ )
+
+ @field_validator("excluded_checks", "excluded_services")
+ @classmethod
+ def _reject_duplicates(cls, value: list[str]) -> list[str]:
+ seen: set[str] = set()
+ duplicates: set[str] = set()
+ for item in value:
+ if item in seen:
+ duplicates.add(item)
+ else:
+ seen.add(item)
+ if duplicates:
+ raise ValueError(f"duplicate values are not allowed: {sorted(duplicates)}")
+ return value
diff --git a/prowler/config/schema/cloudflare.py b/prowler/config/schema/cloudflare.py
new file mode 100644
index 0000000000..417092d6df
--- /dev/null
+++ b/prowler/config/schema/cloudflare.py
@@ -0,0 +1,24 @@
+"""Cloudflare provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class CloudflareProviderConfig(ProviderConfigBase):
+ """Cloudflare provider configuration schema.
+
+ Defines optional configuration parameters for Cloudflare security checks,
+ including API retry behavior.
+ """
+
+ max_retries: Optional[int] = Field(
+ default=None,
+ ge=0,
+ le=10,
+ description=(
+ "Max retries for Cloudflare API requests. Range: 0..10 (0 disables retries)."
+ ),
+ )
diff --git a/prowler/config/schema/e2enetworks.py b/prowler/config/schema/e2enetworks.py
new file mode 100644
index 0000000000..57e29e32d6
--- /dev/null
+++ b/prowler/config/schema/e2enetworks.py
@@ -0,0 +1,22 @@
+"""E2E Networks provider config schema."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class E2eNetworksProviderConfig(ProviderConfigBase):
+ """E2E Networks provider configuration schema.
+
+ Defines optional configuration parameters for E2E Networks security checks.
+ """
+
+ require_bitninja_on_load_balancers: Optional[bool] = Field(
+ default=None,
+ description=(
+ "Whether BitNinja protection is required on load balancers for the "
+ "loadbalancer_bitninja_enabled check."
+ ),
+ )
diff --git a/prowler/config/schema/gcp.py b/prowler/config/schema/gcp.py
new file mode 100644
index 0000000000..59e1a162fa
--- /dev/null
+++ b/prowler/config/schema/gcp.py
@@ -0,0 +1,45 @@
+"""GCP provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class GCPProviderConfig(ProviderConfigBase):
+ shodan_api_key: Optional[str] = Field(
+ default=None,
+ max_length=512,
+ description="API key for Shodan lookups on GCP public IPs.",
+ )
+ mig_min_zones: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=5,
+ description="Min zones a Managed Instance Group must span. Range: 1..5.",
+ )
+ max_snapshot_age_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1095,
+ description=(
+ "Days a disk snapshot can age before being flagged. Range: 1..1095 "
+ "(3 years; older snapshots typically miss data-class compliance)."
+ ),
+ )
+ max_unused_account_days: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=365,
+ description=(
+ "Days a service account or user-managed key can stay unused. "
+ "Range: 30..365."
+ ),
+ )
+ storage_min_retention_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=3650,
+ description="Min retention period on Cloud Storage buckets. Range: 1..3650.",
+ )
diff --git a/prowler/config/schema/github.py b/prowler/config/schema/github.py
new file mode 100644
index 0000000000..30b5a13b85
--- /dev/null
+++ b/prowler/config/schema/github.py
@@ -0,0 +1,20 @@
+"""GitHub provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class GitHubProviderConfig(ProviderConfigBase):
+ inactive_not_archived_days_threshold: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=3650,
+ description=(
+ "Days a repository can stay inactive without being archived before "
+ "being flagged. Range: 30..3650 (CIS GitHub recommends 180; "
+ "<30 days produces false positives on seasonal projects)."
+ ),
+ )
diff --git a/prowler/config/schema/kubernetes.py b/prowler/config/schema/kubernetes.py
new file mode 100644
index 0000000000..3235971500
--- /dev/null
+++ b/prowler/config/schema/kubernetes.py
@@ -0,0 +1,45 @@
+"""Kubernetes provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class KubernetesProviderConfig(ProviderConfigBase):
+ audit_log_maxbackup: Optional[int] = Field(
+ default=None,
+ ge=2,
+ le=1000,
+ description=(
+ "API server audit log file rotations to keep. Range: 2..1000 "
+ "(CIS Kubernetes 1.2.18 recommends ≥10)."
+ ),
+ )
+ audit_log_maxsize: Optional[int] = Field(
+ default=None,
+ ge=10,
+ le=10000,
+ description=(
+ "Max MB per audit log file before rotation. Range: 10..10000 MB "
+ "(CIS Kubernetes 1.2.19 recommends ≥100 MB)."
+ ),
+ )
+ audit_log_maxage: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=3650,
+ description=(
+ "Days an audit log file is retained. Range: 7..3650 "
+ "(CIS Kubernetes 1.2.17 recommends ≥30 days)."
+ ),
+ )
+ apiserver_strong_ciphers: Optional[list[str]] = Field(
+ default=None,
+ description="Whitelist of strong TLS cipher suites required on the API server.",
+ )
+ kubelet_strong_ciphers: Optional[list[str]] = Field(
+ default=None,
+ description="Whitelist of strong TLS cipher suites required on kubelet.",
+ )
diff --git a/prowler/config/schema/m365.py b/prowler/config/schema/m365.py
new file mode 100644
index 0000000000..ff1ff98285
--- /dev/null
+++ b/prowler/config/schema/m365.py
@@ -0,0 +1,54 @@
+"""M365 provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class M365ProviderConfig(ProviderConfigBase):
+ # --- Entra (sign-in policy) ----------------------------------------
+ sign_in_frequency: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=168,
+ description=(
+ "Hours between forced sign-ins for admin users. Range: 1..168 (1 h .. 7 days). "
+ "Microsoft Conditional Access baseline for admin roles is ≤24 h."
+ ),
+ )
+
+ # --- Teams ---------------------------------------------------------
+ allowed_cloud_storage_services: Optional[list[str]] = Field(
+ default=None,
+ description="External cloud storage services allowed in Teams.",
+ )
+
+ # --- Exchange ------------------------------------------------------
+ recommended_mailtips_large_audience_threshold: Optional[int] = Field(
+ default=None,
+ ge=5,
+ le=10000,
+ description=(
+ "Recipient count that should trigger a 'large audience' MailTip. "
+ "Range: 5..10000 (Microsoft default 25)."
+ ),
+ )
+
+ # --- Defender malware policy --------------------------------------
+ default_recommended_extensions: Optional[list[str]] = Field(
+ default=None,
+ description="File extensions blocked by the malware policy.",
+ )
+
+ # --- Mailbox auditing ---------------------------------------------
+ audit_log_age: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=3650,
+ description=(
+ "Days mailbox audit logs must be retained. Range: 30..3650 "
+ "(M365 E3 default is 90 days; SEC/FINRA require ≥7 years)."
+ ),
+ )
diff --git a/prowler/config/schema/mongodbatlas.py b/prowler/config/schema/mongodbatlas.py
new file mode 100644
index 0000000000..552e0a7bbd
--- /dev/null
+++ b/prowler/config/schema/mongodbatlas.py
@@ -0,0 +1,25 @@
+"""MongoDB Atlas provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class MongoDBAtlasProviderConfig(ProviderConfigBase):
+ """MongoDB Atlas provider configuration schema.
+
+ Defines optional configuration parameters for MongoDB Atlas security checks,
+ including service account secret validity constraints.
+ """
+
+ max_service_account_secret_validity_hours: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=720,
+ description=(
+ "Max hours a service account secret can stay valid. "
+ "Range: 1..720 (1 h .. 30 days)."
+ ),
+ )
diff --git a/prowler/config/schema/okta.py b/prowler/config/schema/okta.py
new file mode 100644
index 0000000000..933948f3b6
--- /dev/null
+++ b/prowler/config/schema/okta.py
@@ -0,0 +1,124 @@
+"""Okta provider config schema with safety bounds."""
+
+from typing import Annotated, Optional
+
+from pydantic import AfterValidator, Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+# Lowest non-zero request rate we accept. Below this a scan is paced so slowly
+# it becomes impractical (e.g. 0.001 req/s is ~1000s per request, turning a
+# routine scan into days or years). 0 stays valid as the "disable throttling"
+# sentinel; anything between 0 and this floor is rejected so a typo can never
+# stall a scan.
+MIN_REQUESTS_PER_SECOND = 0.1
+
+
+def _validate_requests_per_second(value: Optional[float]) -> Optional[float]:
+ """Reject impractically slow non-zero request rates.
+
+ ``0`` (and ``None``) pass through unchanged — ``0`` is the documented
+ "disable throttling" sentinel. Any positive value below
+ ``MIN_REQUESTS_PER_SECOND`` is rejected; the ``ge``/``le`` bounds on the
+ field already handle negatives and the upper cap.
+ """
+ if value is None or value == 0:
+ return value
+ if value < MIN_REQUESTS_PER_SECOND:
+ raise ValueError(
+ f"must be 0 (disable throttling) or >= {MIN_REQUESTS_PER_SECOND}; "
+ "smaller rates make scans impractically slow"
+ )
+ return value
+
+
+class OktaProviderConfig(ProviderConfigBase):
+ """Okta provider configuration schema.
+
+ Bounds the session, idle-timeout and inactivity thresholds consumed by
+ the Okta checks, plus the provider's API rate-limit handling (proactive
+ request throttling and the SDK retry safety net). Every field is optional:
+ when omitted (or dropped for being out of range) the check falls back to
+ its own DISA STIG-derived default via ``audit_config.get(key, default)``.
+ """
+
+ okta_max_session_idle_minutes: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1440,
+ description=(
+ "Maximum acceptable Global Session idle timeout, in minutes. "
+ "Range: 1..1440 (DISA STIG V-273186 recommends 15; raising it "
+ "weakens the idle-timeout control)."
+ ),
+ )
+ okta_max_session_lifetime_minutes: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=43200,
+ description=(
+ "Maximum acceptable Global Session lifetime, in minutes. "
+ "Range: 1..43200 i.e. up to 30 days (DISA STIG recommends 18h = "
+ "1080; raising it weakens the session-lifetime control)."
+ ),
+ )
+ okta_admin_console_idle_timeout_max_minutes: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1440,
+ description=(
+ "Maximum acceptable Okta Admin Console app idle timeout, in "
+ "minutes. Range: 1..1440 (DISA STIG V-273187 recommends 15)."
+ ),
+ )
+ okta_user_inactivity_max_days: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=3650,
+ description=(
+ "Maximum number of days a user can stay inactive before the "
+ "inactivity-automation check flags the org. Range: 1..3650 "
+ "(defaults to 35)."
+ ),
+ )
+ okta_dod_approved_ca_issuer_patterns: Optional[list[str]] = Field(
+ default=None,
+ description=(
+ "Additional regex patterns matched against a Smart Card IdP "
+ "certificate issuer DN to recognise a DOD-approved CA. Extends "
+ "the built-in `OU=DoD` / `OU=ECA` patterns."
+ ),
+ )
+
+ # API rate limiting
+ okta_requests_per_second: Annotated[
+ Optional[float], AfterValidator(_validate_requests_per_second)
+ ] = Field(
+ default=None,
+ ge=0,
+ le=100,
+ description=(
+ "Maximum aggregate Okta API requests per second. Range: 0 or "
+ f"{MIN_REQUESTS_PER_SECOND}..100 (0 disables throttling). Non-zero "
+ f"values below {MIN_REQUESTS_PER_SECOND} are rejected to avoid "
+ "impractically slow scans."
+ ),
+ )
+ okta_max_retries: Optional[int] = Field(
+ default=None,
+ ge=0,
+ le=10,
+ description=(
+ "Max retries on Okta API rate limiting (HTTP 429). Range: 0..10 "
+ "(0 disables retries)."
+ ),
+ )
+ okta_request_timeout: Optional[int] = Field(
+ default=None,
+ ge=0,
+ le=3600,
+ description=(
+ "Per-request timeout in seconds; also the total budget for the SDK "
+ "retry loop. Range: 0..3600 (0 disables the timeout)."
+ ),
+ )
diff --git a/prowler/config/schema/openstack.py b/prowler/config/schema/openstack.py
new file mode 100644
index 0000000000..02b94136ef
--- /dev/null
+++ b/prowler/config/schema/openstack.py
@@ -0,0 +1,34 @@
+"""OpenStack provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class OpenStackProviderConfig(ProviderConfigBase):
+ """OpenStack provider configuration schema.
+
+ Bounds the image-sharing threshold and reuses the ``secrets_ignore_patterns``
+ config consumed by the metadata sensitive-data checks. Every field is
+ optional: when omitted (or dropped for being out of range) the check falls
+ back to its own default via ``audit_config.get(key, default)``.
+ """
+
+ image_sharing_threshold: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1000,
+ description=(
+ "Maximum number of accepted project members a shared image may "
+ "have before being flagged. Range: 1..1000 (defaults to 5)."
+ ),
+ )
+ secrets_ignore_patterns: Optional[list[str]] = Field(
+ default=None,
+ description=(
+ "Regex patterns whose matches are excluded from secret "
+ "scanning of resource metadata."
+ ),
+ )
diff --git a/prowler/config/schema/registry.py b/prowler/config/schema/registry.py
new file mode 100644
index 0000000000..074ccc264d
--- /dev/null
+++ b/prowler/config/schema/registry.py
@@ -0,0 +1,36 @@
+"""Mapping of provider name to its Pydantic schema class.
+
+Kept in its own module so the validator stays free of provider-schema imports
+and callers pay the import cost only when they actually need the registry.
+"""
+
+from prowler.config.schema.alibabacloud import AlibabaCloudProviderConfig
+from prowler.config.schema.aws import AWSProviderConfig
+from prowler.config.schema.azure import AzureProviderConfig
+from prowler.config.schema.base import ProviderConfigBase
+from prowler.config.schema.cloudflare import CloudflareProviderConfig
+from prowler.config.schema.e2enetworks import E2eNetworksProviderConfig
+from prowler.config.schema.gcp import GCPProviderConfig
+from prowler.config.schema.github import GitHubProviderConfig
+from prowler.config.schema.kubernetes import KubernetesProviderConfig
+from prowler.config.schema.m365 import M365ProviderConfig
+from prowler.config.schema.mongodbatlas import MongoDBAtlasProviderConfig
+from prowler.config.schema.okta import OktaProviderConfig
+from prowler.config.schema.openstack import OpenStackProviderConfig
+from prowler.config.schema.vercel import VercelProviderConfig
+
+SCHEMAS: dict[str, type[ProviderConfigBase]] = {
+ "aws": AWSProviderConfig,
+ "azure": AzureProviderConfig,
+ "gcp": GCPProviderConfig,
+ "kubernetes": KubernetesProviderConfig,
+ "m365": M365ProviderConfig,
+ "github": GitHubProviderConfig,
+ "mongodbatlas": MongoDBAtlasProviderConfig,
+ "cloudflare": CloudflareProviderConfig,
+ "e2enetworks": E2eNetworksProviderConfig,
+ "vercel": VercelProviderConfig,
+ "okta": OktaProviderConfig,
+ "alibabacloud": AlibabaCloudProviderConfig,
+ "openstack": OpenStackProviderConfig,
+}
diff --git a/prowler/config/schema/validator.py b/prowler/config/schema/validator.py
new file mode 100644
index 0000000000..8113302855
--- /dev/null
+++ b/prowler/config/schema/validator.py
@@ -0,0 +1,66 @@
+from typing import Any
+
+from pydantic import ValidationError
+
+from prowler.config.schema.base import ProviderConfigBase
+from prowler.lib.logger import logger
+
+
+def validate_provider_config(
+ provider: str,
+ raw: Any,
+ schema_cls: type[ProviderConfigBase] | None,
+) -> dict:
+ """Validate a provider's config dict against its Pydantic schema.
+
+ Behavior is intentionally lenient to preserve backwards compatibility:
+
+ - If ``raw`` is not a dict, return an empty dict (mirrors prior loader).
+ - If no schema is registered for ``provider``, return ``raw`` untouched.
+ - On validation errors, log one WARNING per offending field, DROP those
+ keys from the result, and continue. Consumers fall back to their own
+ hard-coded defaults via ``audit_config.get(key, default)``.
+ - Coerced values (e.g. ``"180"`` -> ``180``) replace the user's input
+ so that downstream checks never receive a wrongly-typed value.
+ """
+ if not isinstance(raw, dict):
+ return {}
+
+ if schema_cls is None:
+ return raw
+
+ try:
+ model = schema_cls.model_validate(raw)
+ return model.model_dump(exclude_unset=True)
+ except ValidationError as exc:
+ bad_keys: set[str] = set()
+ for err in exc.errors():
+ loc = err.get("loc") or ()
+ if not loc:
+ continue
+ key = loc[0]
+ if not isinstance(key, str):
+ continue
+ bad_keys.add(key)
+ logger.warning(
+ f"prowler.config[{provider}.{key}] = {raw.get(key)!r} is invalid "
+ f"({err.get('msg', 'validation error')}); the value will be ignored "
+ f"and the built-in default will be used."
+ )
+
+ cleaned = {k: v for k, v in raw.items() if k not in bad_keys}
+ # Retry validation with the cleaned dict. Dropping invalid keys handles
+ # common field-level mismatches, but revalidation can still fail due to
+ # higher-level structural constraints (e.g. nested validation errors not
+ # captured in the top-level bad_keys). In that case, log and return the
+ # cleaned dict so consumers fall back to their own defaults.
+ try:
+ model = schema_cls.model_validate(cleaned)
+ return model.model_dump(exclude_unset=True)
+ except ValidationError as exc2:
+ logger.error(
+ f"prowler.config[{provider}] could not be revalidated after dropping "
+ f"invalid keys ({bad_keys}); passing through the cleaned dict as-is. "
+ f"Underlying errors: {exc2.errors()}"
+ )
+ return cleaned
diff --git a/prowler/config/schema/validators.py b/prowler/config/schema/validators.py
new file mode 100644
index 0000000000..3c87f532c7
--- /dev/null
+++ b/prowler/config/schema/validators.py
@@ -0,0 +1,71 @@
+"""Reusable field validators shared across provider config schemas.
+
+These are factored out so multiple providers can reuse the same validation
+logic (version strings, port ranges, IP/CIDR entries) instead of duplicating
+it per schema. Each validator accepts ``None`` so optional fields stay valid
+when the key is absent.
+"""
+
+from ipaddress import ip_network
+from typing import Callable, Optional
+
+_VERSION_PART_LABELS = ("X", "Y", "Z", "W")
+
+
+def make_dotted_version_validator(
+ min_parts: int, max_parts: int
+) -> Callable[[Optional[str]], Optional[str]]:
+ """Build a validator for dotted numeric version strings.
+
+ The returned validator accepts ``None`` and strings made of between
+ ``min_parts`` and ``max_parts`` dot-separated numeric components. Anything
+ else raises ``ValueError``.
+
+ Examples:
+ ``make_dotted_version_validator(3, 3)`` accepts ``"1.4.0"`` (semver).
+ ``make_dotted_version_validator(2, 2)`` accepts ``"1.28"`` (EKS minor).
+ ``make_dotted_version_validator(1, 2)`` accepts ``"17"`` or ``"8.2"``.
+ """
+ if min_parts == max_parts:
+ expected = ".".join(_VERSION_PART_LABELS[:min_parts])
+ else:
+ expected = " or ".join(
+ f"'{'.'.join(_VERSION_PART_LABELS[:n])}'"
+ for n in range(min_parts, max_parts + 1)
+ )
+
+ def _validate(v: Optional[str]) -> Optional[str]:
+ if v is None:
+ return v
+ parts = v.split(".")
+ if not (min_parts <= len(parts) <= max_parts) or not all(
+ p.isdigit() for p in parts
+ ):
+ raise ValueError(f"{v!r} is not a valid version (expected {expected})")
+ return v
+
+ return _validate
+
+
+def validate_port_range(v: Optional[list[int]]) -> Optional[list[int]]:
+ """Reject ports outside the valid ``1..65535`` range."""
+ if v is None:
+ return v
+ for port in v:
+ if not 1 <= port <= 65535:
+ raise ValueError(f"port {port} is outside the valid range 1..65535")
+ return v
+
+
+def validate_ip_networks(v: Optional[list[str]]) -> Optional[list[str]]:
+ """Reject entries that are not a valid IP address or CIDR network."""
+ if v is None:
+ return v
+ for entry in v:
+ try:
+ ip_network(entry, strict=False)
+ except ValueError as exc:
+ raise ValueError(
+ f"entry {entry!r} is not a valid IP or CIDR ({exc})"
+ ) from exc
+ return v
diff --git a/prowler/config/schema/vercel.py b/prowler/config/schema/vercel.py
new file mode 100644
index 0000000000..2e466e2049
--- /dev/null
+++ b/prowler/config/schema/vercel.py
@@ -0,0 +1,68 @@
+"""Vercel provider config schema with safety bounds."""
+
+from typing import Optional
+
+from pydantic import Field
+
+from prowler.config.schema.base import ProviderConfigBase
+
+
+class VercelProviderConfig(ProviderConfigBase):
+ """Vercel provider configuration schema.
+
+ Defines optional configuration parameters for Vercel security checks,
+ including deployment branch policies, credential staleness thresholds,
+ RBAC ownership limits, and secret detection patterns.
+ """
+
+ stable_branches: Optional[list[str]] = Field(
+ default=None,
+ description="Branches considered stable for production deployments.",
+ )
+ days_to_expire_threshold: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=365,
+ description=(
+ "Days before token/certificate expiration to flag. Range: 7..365 "
+ "(PCI-DSS 4.2.1.1: alert ≥30 days before expiry)."
+ ),
+ )
+ stale_token_threshold_days: Optional[int] = Field(
+ default=None,
+ ge=30,
+ le=3650,
+ description=(
+ "Days of inactivity before a token is considered stale. Range: 30..3650 "
+ "(NIST AC-2(3) typical window 30..90 days)."
+ ),
+ )
+ stale_invitation_threshold_days: Optional[int] = Field(
+ default=None,
+ ge=7,
+ le=365,
+ description=(
+ "Days a pending invitation can stay open. Range: 7..365 "
+ "(OWASP ASVS 2.7.1 recommends short-lived invitations)."
+ ),
+ )
+ max_owner_percentage: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=50,
+ description=(
+ "Max percentage of team members that can have the OWNER role. "
+ "Range: 1..50 (PoLP — having >50% of a team as OWNER defeats RBAC; "
+ "industry guidance recommends ≤25%)."
+ ),
+ )
+ max_owners: Optional[int] = Field(
+ default=None,
+ ge=1,
+ le=1000,
+ description="Absolute max owners (overrides percentage for large teams). Range: 1..1000.",
+ )
+ secret_suffixes: Optional[list[str]] = Field(
+ default=None,
+ description="Suffixes that mark a project env var as secret-like.",
+ )
diff --git a/prowler/config/stackit_mutelist_example.yaml b/prowler/config/stackit_mutelist_example.yaml
new file mode 100644
index 0000000000..40b04a2731
--- /dev/null
+++ b/prowler/config/stackit_mutelist_example.yaml
@@ -0,0 +1,26 @@
+### Project, Check and/or Region can be * to apply for all the cases.
+### Project == <StackIT Project ID>
+### Resources and tags are lists that can have either Regex or Keywords.
+### Tags is an optional list that matches on tuples of 'key=value' and are "ANDed" together.
+### Use an alternation Regex to match one of multiple tags with "ORed" logic.
+### For each check you can except Projects, Regions, Resources and/or Tags.
+########################### MUTELIST EXAMPLE ###########################
+Mutelist:
+ Accounts:
+ "project_id_1":
+ Checks:
+ "iaas_security_group_ssh_unrestricted":
+ Regions:
+ - "*"
+ Resources:
+ - "sg-production-ssh"
+ - "sg-development-rdp"
+ Tags:
+ - "environment=dev"
+ "project_id_2":
+ Checks:
+ "*":
+ Regions:
+ - "eu01"
+ Resources:
+ - ".*-test$"
diff --git a/prowler/lib/banner.py b/prowler/lib/banner.py
index 72031805e2..e1c7fa5a35 100644
--- a/prowler/lib/banner.py
+++ b/prowler/lib/banner.py
@@ -2,13 +2,29 @@ from colorama import Fore, Style
from prowler.config.config import banner_color, orange_color, prowler_version, timestamp
+# Prowler Cloud landing URL used by the CLI banner. The visible text stays
+# "cloud.prowler.com" while the clickable target carries the UTM source so
+# terminals that support OSC 8 hyperlinks attribute the visit to the CLI.
+CLOUD_DISPLAY_TEXT = "cloud.prowler.com"
+CLOUD_BANNER_URL = "https://cloud.prowler.com/sign-up?utm_source=prowler-cli"
-def print_banner(legend: bool = False):
+
+def _hyperlink(url: str, text: str) -> str:
+ """Wrap ``text`` in an OSC 8 terminal hyperlink pointing to ``url``.
+
+ Terminals that support OSC 8 render ``text`` as a clickable link to ``url``;
+ those that do not simply display ``text`` unchanged.
+ """
+ return f"\033]8;;{url}\033\\{text}\033]8;;\033\\"
+
+
+def print_banner(legend: bool = False, provider: str = None):
"""
Prints the banner with optional legend for color codes.
Parameters:
- legend (bool): Flag to indicate whether to print the color legend or not. Default is False.
+ - provider (str): The provider being scanned, used to tailor the Prowler Cloud banner.
Returns:
- None
@@ -17,23 +33,56 @@ def print_banner(legend: bool = False):
_ __ _ __ _____ _| | ___ _ __
| '_ \| '__/ _ \ \ /\ / / |/ _ \ '__|
| |_) | | | (_) \ V V /| | __/ |
-| .__/|_| \___/ \_/\_/ |_|\___|_|v{prowler_version}
-|_|{Fore.BLUE} Get the most at https://cloud.prowler.com {Style.RESET_ALL}
-
-{Fore.GREEN}New! Send findings from Prowler CLI to Prowler Cloud{Style.RESET_ALL}
-{Fore.GREEN}More details here: goto.prowler.com/import-findings{Style.RESET_ALL}
+| .__/|_| \___/ \_/\_/ |_|\___|_| CLI - v{prowler_version}
+|_|
{Fore.YELLOW}Date: {timestamp.strftime("%Y-%m-%d %H:%M:%S")}{Style.RESET_ALL}
"""
print(banner)
+ print_prowler_cloud_banner(provider)
+
if legend:
- print(
- f"""
+ print(f"""
{Style.BRIGHT}Color code for results:{Style.RESET_ALL}
- {Fore.YELLOW}MANUAL (Manual check){Style.RESET_ALL}
- {Fore.GREEN}PASS (Recommended value){Style.RESET_ALL}
- {orange_color}MUTED (Muted by muted list){Style.RESET_ALL}
- {Fore.RED}FAIL (Fix required){Style.RESET_ALL}
- """
- )
+ """)
+
+
+def print_prowler_cloud_banner(provider: str = None):
+ """
+ Prints a promotional banner highlighting what Prowler Cloud adds on top of
+ the open-source CLI.
+
+ Shown at the start and end of a scan to let users know about the managed
+ platform capabilities they are missing (CLI findings upload, attack paths,
+ AI, triage, organizations, continuous scanning with custom scheduling and
+ scan configuration, integrations and live compliance dashboards).
+
+ Parameters:
+ - provider (str): The provider that was scanned, used to tailor the message.
+
+ Returns:
+ - None
+ """
+ check = f"{Fore.GREEN}✓{Style.RESET_ALL}"
+ bar = f"{banner_color}│{Style.RESET_ALL}"
+ print(f"""
+{bar} {Style.BRIGHT}You're getting a snapshot 📸. Prowler Cloud gives you the full picture:{Style.RESET_ALL}
+{bar}
+{bar} {check} {Style.BRIGHT}Send your findings{Style.RESET_ALL} - directly from the Prowler CLI to Prowler Cloud.
+{bar} {check} {Style.BRIGHT}Continuous Security Monitoring{Style.RESET_ALL} - custom scheduling and scan configuration with history, trends and alerts.
+{bar} {check} {Style.BRIGHT}Triage{Style.RESET_ALL} - review findings, flag false positives and track accepted risk with your team.
+{bar} {check} {Style.BRIGHT}Lighthouse AI + MCP{Style.RESET_ALL} - autonomous triage, custom dashboards, prioritization with prevention and remediation.
+{bar} {check} {Style.BRIGHT}Alerts{Style.RESET_ALL} - get notified when anything you want is happening.
+{bar} {check} {Style.BRIGHT}Live Compliance{Style.RESET_ALL} - dashboards for 50+ frameworks, always up to date.
+{bar} {check} {Style.BRIGHT}Remediation{Style.RESET_ALL} - complete guided remediation including Autonomous remediation with Lighthouse AI.
+{bar} {check} {Style.BRIGHT}Attack Path Visualization{Style.RESET_ALL} - see how attackers chain risks to reach your crown jewels.
+{bar} {check} {Style.BRIGHT}Bulk Provisioning{Style.RESET_ALL} - add your entire AWS Organization in seconds.
+{bar} {check} {Style.BRIGHT}Integrations{Style.RESET_ALL} - Anything with our MCP + Jira, Slack, AWS Security Hub, Amazon S3, SSO and RBAC.
+{bar}
+{bar} {banner_color}Start free at 👉 {_hyperlink(CLOUD_BANNER_URL, CLOUD_DISPLAY_TEXT)}{Style.RESET_ALL}
+""")
diff --git a/prowler/lib/check/check.py b/prowler/lib/check/check.py
index 53b832290f..c0c6a02e5d 100644
--- a/prowler/lib/check/check.py
+++ b/prowler/lib/check/check.py
@@ -1,4 +1,6 @@
import importlib
+import importlib.metadata
+import importlib.util
import json
import os
import re
@@ -19,6 +21,7 @@ from prowler.lib.check.utils import recover_checks_from_provider
from prowler.lib.logger import logger
from prowler.lib.outputs.outputs import report
from prowler.lib.utils.utils import open_file, parse_json_file, print_boxes
+from prowler.providers.common.builtin import is_builtin_provider
from prowler.providers.common.models import Audit_Metadata
@@ -385,6 +388,45 @@ def import_check(check_path: str) -> ModuleType:
return lib
+def _resolve_check_module(
+ provider_type: str, service: str, check_name: str
+) -> ModuleType:
+ """Resolve and import a check module.
+
+ Built-in wins on CheckID collision. Plug-ins are first-class extenders
+ (they can add new checks under new CheckIDs) but cannot override
+ existing built-ins — a security tool prefers fail-loud predictability
+ over silent overrides. CheckMetadata.get_bulk() applies the same
+ precedence on the metadata side (first-write-wins) and emits a warning
+ when a plug-in tries to override, so the user knows their plug-in
+ duplicate is being ignored and can rename it.
+
+ Gates the built-in branch on `is_builtin_provider(provider_type)` —
+ calling `find_spec` on `prowler.providers.{provider_type}.services...`
+ directly would propagate `ModuleNotFoundError` for external providers
+ (their parent package `prowler.providers.{provider_type}` does not
+ exist) instead of returning None. The leaf helper encapsulates the
+ safe lookup, so external providers go straight to entry points. For
+ built-ins we still use `find_spec` to distinguish "check doesn't
+ exist" from "check exists but failed to import" (broken transitive
+ dep, etc.).
+ """
+ # Built-in first — built-in wins on CheckID collision
+ if is_builtin_provider(provider_type):
+ builtin_path = f"prowler.providers.{provider_type}.services.{service}.{check_name}.{check_name}"
+ if importlib.util.find_spec(builtin_path) is not None:
+ return import_check(builtin_path)
+
+ # Entry point lookup — only consulted when the built-in truly doesn't exist
+ for ep in importlib.metadata.entry_points(group=f"prowler.checks.{provider_type}"):
+ if ep.name == check_name:
+ return importlib.import_module(ep.value)
+
+ raise ModuleNotFoundError(
+ f"Check '{check_name}' not found for provider '{provider_type}'"
+ )
+
+
def run_fixer(check_findings: list) -> int:
"""
Run the fixer for the check if it exists and there are any FAIL findings
@@ -525,9 +567,10 @@ def execute_checks(
service = check_name.split("_")[0]
try:
try:
- # Import check module
- check_module_path = f"prowler.providers.{global_provider.type}.services.{service}.{check_name}.{check_name}"
- lib = import_check(check_module_path)
+ # Import check module (built-in or entry point)
+ lib = _resolve_check_module(
+ global_provider.type, service, check_name
+ )
# Recover functions from check
check_to_execute = getattr(lib, check_name)
check = check_to_execute()
@@ -605,9 +648,10 @@ def execute_checks(
)
try:
try:
- # Import check module
- check_module_path = f"prowler.providers.{global_provider.type}.services.{service}.{check_name}.{check_name}"
- lib = import_check(check_module_path)
+ # Import check module (built-in or entry point)
+ lib = _resolve_check_module(
+ global_provider.type, service, check_name
+ )
# Recover functions from check
check_to_execute = getattr(lib, check_name)
check = check_to_execute()
@@ -753,6 +797,14 @@ def execute(
is_finding_muted_args["org_domain"] = (
global_provider.identity.org_domain
)
+ elif global_provider.type == "linode":
+ is_finding_muted_args["account_id"] = (
+ global_provider.identity.account_id
+ )
+ elif not is_builtin_provider(global_provider.type):
+ # External/custom provider — delegate identity args
+ is_finding_muted_args = global_provider.get_mutelist_finding_args()
+
for finding in check_findings:
if global_provider.type == "cloudflare":
is_finding_muted_args["account_id"] = finding.account_id
diff --git a/prowler/lib/check/checks_loader.py b/prowler/lib/check/checks_loader.py
index 9ef672df6b..77840084ff 100644
--- a/prowler/lib/check/checks_loader.py
+++ b/prowler/lib/check/checks_loader.py
@@ -2,10 +2,10 @@ import sys
from colorama import Fore, Style
-from prowler.config.config import EXTERNAL_TOOL_PROVIDERS
from prowler.lib.check.check import parse_checks_from_file
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.check.models import CheckMetadata, Severity
+from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
from prowler.lib.logger import logger
@@ -26,8 +26,13 @@ def load_checks_to_execute(
) -> set:
"""Generate the list of checks to execute based on the cloud provider and the input arguments given"""
try:
- # Bypass check loading for providers that use external tools directly
- if provider in EXTERNAL_TOOL_PROVIDERS:
+ # Bypass check loading for tool-wrapper providers — they delegate
+ # scanning to an external tool and have no checks to recover.
+ # Single source of truth across __main__, the CheckMetadata validators,
+ # check discovery and this loader, covering both built-in tool wrappers
+ # (iac/llm/image) and external plug-ins that declare
+ # `is_external_tool_provider = True` via the contract.
+ if is_tool_wrapper_provider(provider):
return set()
# Local subsets
diff --git a/prowler/lib/check/compliance_config_eval.py b/prowler/lib/check/compliance_config_eval.py
new file mode 100644
index 0000000000..0024d41e3f
--- /dev/null
+++ b/prowler/lib/check/compliance_config_eval.py
@@ -0,0 +1,410 @@
+"""Shared evaluation of a requirement's configuration constraints.
+
+Some compliance requirements only hold if the configurable checks they map to
+ran with a configuration strict enough for the requirement. For example CIS AWS
+6.0 requirement 2.11 ("credentials unused for 45 days or more are disabled")
+maps `iam_user_accesskey_unused` (config `max_unused_access_keys_days`); if the
+user loosens that to 120 days the check can PASS while the requirement is, in
+fact, not satisfied.
+
+A requirement declares its expectations via ``ConfigRequirements`` (a list of
+``{Check, ConfigKey, Operator, Value}``). The configuration a scan applied is a
+single, scan-global mapping (the provider's ``audit_config``), so the rules are
+evaluated against that mapping directly. This module is consumed by the SDK
+compliance outputs (CSV + CLI table) and by the Prowler App backend so the rule
+lives in one place.
+"""
+
+from typing import Any, Optional
+
+# Leading sentence of the message prepended to a finding's ``status_extended``
+# when its requirement's config constraints are not satisfied and the status is
+# forced to FAIL. It opens every config-not-valid message, so it doubles as a
+# stable marker for detecting the case programmatically.
+CONFIG_NOT_VALID_PREFIX = "Configuration not valid for this requirement."
+
+
+def _format_value(value: Any) -> str:
+ """Render a constraint value for a user-facing message (lists comma-joined)."""
+ if isinstance(value, (list, tuple, set)):
+ return ", ".join(str(item) for item in value)
+ return str(value)
+
+
+def _describe_violation(
+ check: Any, config_key: Any, applied: Any, operator: str, expected: Any
+) -> str:
+ """Return a product-friendly explanation of why a config violates a constraint.
+
+ The message names the check and config key, the value the scan applied, what
+ the requirement needs, and how to fix it, in plain language rather than the
+ operator/value pair.
+
+ Args:
+ check: the check the requirement maps to (e.g. ``iam_user_accesskey_unused``).
+ config_key: the config option that was too loose (e.g. ``max_unused_access_keys_days``).
+ applied: the value the scan actually applied.
+ operator: the constraint operator (``lte``/``gte``/``eq``/``in``/``subset``/``superset``).
+ expected: the value the requirement expects.
+
+ Returns:
+ A full, human-readable message ending with an actionable fix.
+ """
+ applied_str = _format_value(applied)
+ expected_str = _format_value(expected)
+ needs, fix = {
+ "lte": (
+ f"a value of {expected_str} or lower",
+ f"Update it to {expected_str} or lower.",
+ ),
+ "gte": (
+ f"a value of {expected_str} or higher",
+ f"Update it to {expected_str} or higher.",
+ ),
+ "eq": (
+ f"it set to {expected_str}",
+ f"Update it to {expected_str}.",
+ ),
+ "in": (
+ f"it set to one of {expected_str}",
+ f"Update it to one of {expected_str}.",
+ ),
+ "subset": (
+ f"it limited to {expected_str}",
+ f"Remove any value that is not in {expected_str}.",
+ ),
+ "superset": (
+ f"it to include {expected_str}",
+ f"Make sure it includes {expected_str}.",
+ ),
+ }.get(operator, (f"a different value (expected {operator} {expected_str})", ""))
+ message = (
+ f"{CONFIG_NOT_VALID_PREFIX} The check {check} has {config_key} set to "
+ f"{applied_str}, but the requirement needs {needs}."
+ )
+ return f"{message} {fix}".strip()
+
+
+def _check_operator(applied: Any, operator: str, expected: Any) -> bool:
+ """Return whether ``applied`` satisfies ``operator`` against ``expected``."""
+ try:
+ if operator == "lte":
+ return applied <= expected
+ if operator == "gte":
+ return applied >= expected
+ if operator == "eq":
+ return applied == expected
+ if operator == "in":
+ return applied in expected
+ if operator in ("subset", "superset"):
+ # Set comparisons for list-valued configs (allowlists / denylists).
+ # Both sides must be collections; anything else is not satisfiable.
+ if not isinstance(applied, (list, tuple, set)) or not isinstance(
+ expected, (list, tuple, set)
+ ):
+ return False
+ applied_set, expected_set = set(applied), set(expected)
+ if operator == "subset":
+ return applied_set <= expected_set
+ return applied_set >= expected_set
+ except TypeError:
+ # Mismatched/unhashable types → treat as not satisfied.
+ return False
+ # Unknown operator: do not block the requirement on a malformed constraint.
+ return True
+
+
+def evaluate_config_constraints(
+ config_requirements: Optional[list[Any]],
+ audit_config: Optional[dict[str, Any]],
+ provider_type: Optional[str] = None,
+) -> tuple[bool, str]:
+ """Evaluate a requirement's config constraints against the scan's config.
+
+ Args:
+ config_requirements: list of constraints, each a mapping (or object with
+ the same attributes) holding ``Check``, ``ConfigKey``, ``Operator``,
+ ``Value`` and an optional ``Provider``. ``None``/empty means the
+ requirement has no config expectations.
+ audit_config: the scan-global configuration mapping (the provider's
+ ``audit_config``, i.e. ``{config_key: value}``). The applied config
+ is identical across every resource and region of a scan.
+ provider_type: the provider being scanned (e.g. ``aws``). A constraint
+ tagged with a ``Provider`` is only evaluated when it matches this
+ value; this scopes universal (multi-provider) framework constraints
+ to the right provider. ``None`` disables provider scoping (every
+ constraint is evaluated), which is the correct behaviour for
+ single-provider frameworks.
+
+ Returns:
+ ``(is_compliant, reason)``. ``is_compliant`` is ``True`` when there are
+ no constraints or every explicitly-set value satisfies its constraint.
+ When a configured value violates a constraint, returns ``(False, reason)``
+ describing the first violation. A constraint whose ``ConfigKey`` was not
+ explicitly set is skipped (the check's default is assumed to match what
+ the requirement expects).
+ """
+ if not config_requirements:
+ return True, ""
+
+ audit_config = audit_config or {}
+
+ for constraint in config_requirements:
+ # Accept both dicts (API template) and objects (Pydantic model).
+ if isinstance(constraint, dict):
+ check = constraint.get("Check")
+ config_key = constraint.get("ConfigKey")
+ operator = constraint.get("Operator")
+ expected = constraint.get("Value")
+ provider = constraint.get("Provider")
+ else:
+ check = getattr(constraint, "Check", None)
+ config_key = getattr(constraint, "ConfigKey", None)
+ operator = getattr(constraint, "Operator", None)
+ expected = getattr(constraint, "Value", None)
+ provider = getattr(constraint, "Provider", None)
+
+ # Constraint scoped to another provider → not applicable to this scan.
+ # Compared case-insensitively (and trimmed) so a constraint authored as
+ # e.g. "AWS" still scopes to the "aws" scan instead of being silently
+ # bypassed by a casing/format mismatch.
+ if (
+ provider
+ and provider_type
+ and str(provider).strip().lower() != str(provider_type).strip().lower()
+ ):
+ continue
+
+ if config_key not in audit_config:
+ # Config not explicitly set → default is assumed adequate.
+ continue
+
+ applied = audit_config[config_key]
+ if not _check_operator(applied, operator, expected):
+ reason = _describe_violation(check, config_key, applied, operator, expected)
+ return False, reason
+
+ return True, ""
+
+
+def get_scan_audit_config() -> dict[str, Any]:
+ """Return the scan-global applied configuration (the provider's audit_config).
+
+ The applied config is identical across every resource and region of a scan,
+ so every compliance output evaluates constraints against this single mapping.
+ Imported lazily to avoid a circular import with the provider package and to
+ keep this module usable from contexts without a global provider.
+
+ Returns:
+ The provider's ``audit_config`` mapping, or ``{}`` when no global
+ provider is set (``AttributeError``) or the provider package cannot be
+ imported (``ImportError``).
+ """
+ try:
+ from prowler.providers.common.provider import Provider
+
+ return Provider.get_global_provider().audit_config or {}
+ except (AttributeError, ImportError):
+ # No global provider set, or provider package unavailable.
+ return {}
+
+
+def get_scan_provider_type() -> str:
+ """Return the provider being scanned (e.g. ``aws``) for constraint scoping.
+
+ Imported lazily to avoid a circular import with the provider package and to
+ keep this module usable from contexts without a global provider.
+
+ Returns:
+ The provider's ``type`` (e.g. ``aws``), or ``""`` when no global provider
+ is set (``AttributeError``) or the provider package cannot be imported
+ (``ImportError``); an empty string disables provider scoping.
+ """
+ try:
+ from prowler.providers.common.provider import Provider
+
+ return Provider.get_global_provider().type or ""
+ except (AttributeError, ImportError):
+ # No global provider set, or provider package unavailable.
+ return ""
+
+
+def _requirement_id(requirement: Any) -> Optional[str]:
+ """Return a requirement's id across the legacy (``Id``) and universal (``id``) models."""
+ return getattr(requirement, "Id", None) or getattr(requirement, "id", None)
+
+
+def _requirement_constraints(requirement: Any) -> Optional[list]:
+ """Return a requirement's config constraints across both model flavours.
+
+ Legacy ``Compliance_Requirement`` exposes ``ConfigRequirements`` (a list of
+ Pydantic models); ``UniversalComplianceRequirement`` exposes
+ ``config_requirements`` (a list of dicts). ``evaluate_config_constraints``
+ handles both element types.
+ """
+ return getattr(requirement, "ConfigRequirements", None) or getattr(
+ requirement, "config_requirements", None
+ )
+
+
+def build_requirement_config_status(
+ requirements: list[Any],
+ audit_config: Optional[dict[str, Any]] = None,
+ provider_type: Optional[str] = None,
+) -> dict[str, tuple[bool, str]]:
+ """Map every requirement id to its ``(is_compliant, reason)`` config verdict.
+
+ Only requirements that actually declare constraints are included; callers use
+ ``dict.get(req_id)`` (returning ``None`` → no constraints → no override).
+
+ Args:
+ requirements: the framework's requirements (legacy or universal models).
+ audit_config: the applied config; resolved via ``get_scan_audit_config``
+ when omitted.
+ provider_type: the provider being scanned, for constraint scoping;
+ resolved via ``get_scan_provider_type`` when omitted.
+
+ Returns:
+ A mapping ``{requirement_id: (is_compliant, reason)}`` containing only the
+ requirements that declare config constraints.
+ """
+ if audit_config is None:
+ audit_config = get_scan_audit_config()
+ if provider_type is None:
+ provider_type = get_scan_provider_type()
+ status = {}
+ for requirement in requirements:
+ constraints = _requirement_constraints(requirement)
+ if constraints:
+ status[_requirement_id(requirement)] = evaluate_config_constraints(
+ constraints, audit_config, provider_type
+ )
+ return status
+
+
+def resolve_requirement_config_status(
+ requirement: Any,
+ audit_config: dict[str, Any],
+ cache: dict,
+ provider_type: Optional[str] = None,
+) -> tuple[bool, str]:
+ """Return a requirement's ``(is_compliant, reason)`` verdict, memoised in ``cache``.
+
+ For table generators that iterate findings × compliances and only encounter
+ each requirement lazily.
+
+ Args:
+ requirement: the requirement (legacy or universal model).
+ audit_config: the scan-global applied config.
+ cache: a dict keyed by requirement id, reused across the whole table
+ build to memoise verdicts.
+ provider_type: the provider being scanned, for constraint scoping;
+ resolved via ``get_scan_provider_type`` when omitted.
+
+ Returns:
+ The ``(is_compliant, reason)`` verdict; ``(True, "")`` when the
+ requirement declares no constraints.
+ """
+ req_id = _requirement_id(requirement)
+ if req_id not in cache:
+ constraints = _requirement_constraints(requirement)
+ if constraints:
+ if provider_type is None:
+ provider_type = get_scan_provider_type()
+ cache[req_id] = evaluate_config_constraints(
+ constraints, audit_config, provider_type
+ )
+ else:
+ cache[req_id] = (True, "")
+ return cache[req_id]
+
+
+def apply_config_status(
+ status: str,
+ status_extended: str,
+ config_status: Optional[tuple[bool, str]],
+) -> tuple[str, str]:
+ """Override a finding's ``(status, status_extended)`` when its config is invalid.
+
+ A requirement whose configurable checks ran with a config too loose to trust
+ is forced to ``FAIL`` regardless of the finding's own status, with the reason
+ prepended to ``status_extended``.
+
+ Args:
+ status: the finding's original status (e.g. ``PASS`` / ``FAIL``).
+ status_extended: the finding's extended status message.
+ config_status: the ``(is_compliant, reason)`` tuple from
+ ``build_requirement_config_status``/``resolve_requirement_config_status``,
+ or ``None`` when the requirement declares no constraints.
+
+ Returns:
+ The ``(status, status_extended)`` to report: unchanged when the config is
+ valid (or ``config_status`` is ``None``); otherwise ``FAIL`` with the
+ reason prepended to ``status_extended``.
+ """
+ if not config_status or config_status[0]:
+ return status, status_extended
+ return (
+ "FAIL",
+ f"{config_status[1]} {status_extended}".strip(),
+ )
+
+
+def get_effective_status(
+ status: str,
+ config_status: Optional[tuple[bool, str]],
+) -> str:
+ """Return the effective status for table aggregation.
+
+ Args:
+ status: the finding's original status.
+ config_status: the ``(is_compliant, reason)`` tuple, or ``None`` when the
+ requirement declares no constraints.
+
+ Returns:
+ ``FAIL`` when ``config_status`` marks the config invalid; otherwise the
+ finding's original ``status``.
+ """
+ if not config_status or config_status[0]:
+ return status
+ return "FAIL"
+
+
+def accumulate_overview_status(
+ index: int,
+ status: str,
+ pass_indices: set,
+ fail_indices: set,
+ muted_indices: set,
+) -> None:
+ """Record a finding in the overview totals once, with FAIL precedence over PASS (sets mutated in place)."""
+ if status == "Muted":
+ muted_indices.add(index)
+ elif status == "FAIL":
+ fail_indices.add(index)
+ pass_indices.discard(index)
+ elif status == "PASS" and index not in fail_indices:
+ pass_indices.add(index)
+
+
+def accumulate_group_status(
+ index: int,
+ status: str,
+ counts: dict,
+ seen: dict,
+) -> None:
+ """Count a finding once per group, upgrading a counted PASS to FAIL on conflict (mutates ``counts``/``seen``)."""
+ previous = seen.get(index)
+ if status == "MANUAL":
+ # MANUAL findings come from manual, checks-less requirements and are
+ # informational only: they have no PASS/FAIL/Muted column in the section
+ # tally, so counting them would raise KeyError on counts[status] += 1.
+ # Skip them (an unexpected status still raises loudly below).
+ return
+ if previous is None:
+ seen[index] = status
+ counts[status] += 1
+ elif previous == "PASS" and status == "FAIL":
+ seen[index] = "FAIL"
+ counts["PASS"] -= 1
+ counts["FAIL"] += 1
diff --git a/prowler/lib/check/compliance_models.py b/prowler/lib/check/compliance_models.py
index 82ac54e4d9..80322a6929 100644
--- a/prowler/lib/check/compliance_models.py
+++ b/prowler/lib/check/compliance_models.py
@@ -1,8 +1,9 @@
+import importlib.metadata
import json
import os
import sys
from enum import Enum
-from typing import Optional, Union
+from typing import Any, Literal, Optional, Union
from pydantic.v1 import BaseModel, Field, ValidationError, root_validator
@@ -169,6 +170,79 @@ class ISO27001_2013_Requirement_Attribute(BaseModel):
Check_Summary: str
+# Base Compliance Model
+class Compliance_Requirement_ConfigConstraint(BaseModel):
+ """A constraint a requirement places on a configurable check's config.
+
+ Declares that the configurable check ``Check`` must have run with
+ ``ConfigKey`` satisfying ``Operator`` ``Value`` for the requirement's
+ result to be trusted. Example: ``max_unused_access_keys_days <= 45``.
+
+ ``Provider`` scopes the constraint to a single provider. It is required for
+ universal (multi-provider) frameworks, where the same requirement maps
+ checks across providers and a constraint must only apply when that provider
+ is the one being scanned. Single-provider frameworks may omit it (the
+ framework's provider is already the one being scanned).
+
+ Operators:
+ - ``lte``/``gte``/``eq``: scalar comparisons (e.g. a max-age or min-retention
+ threshold, or a boolean toggle).
+ - ``in``: the applied scalar must be one of ``Value`` (a list).
+ - ``subset``: the applied list must be a subset of ``Value`` — for allowlist
+ configs (e.g. ``recommended_minimal_tls_versions``); widening the allowlist
+ with a weaker value (e.g. TLS ``1.0``) breaks the constraint.
+ - ``superset``: the applied list must be a superset of ``Value`` — for
+ denylist configs (e.g. ``insecure_key_algorithms``); removing a forbidden
+ value from the denylist breaks the constraint.
+ """
+
+ Check: str
+ ConfigKey: str
+ Operator: Literal["lte", "gte", "eq", "in", "subset", "superset"]
+ # ``bool`` must precede ``int`` so pydantic v1 keeps booleans (e.g. a
+ # ``mute_non_default_regions == false`` constraint) instead of coercing
+ # them to 0/1.
+ Value: Union[bool, int, float, str, list[Any]]
+ # Provider this constraint applies to (e.g. ``aws``), matched
+ # case-insensitively. ``None`` applies whenever the requirement runs
+ # (single-provider frameworks).
+ Provider: Optional[str] = None
+
+ @root_validator
+ @classmethod
+ def validate_value_matches_operator(cls, values): # noqa: F841
+ """Ensure ``Value``'s type is consistent with ``Operator``.
+
+ Without this, a mistyped value (e.g. ``gte`` with a list, or ``subset``
+ with a scalar) is not rejected at load time and ``_check_operator``
+ silently treats it as *not satisfied*, forcing the requirement to a
+ spurious config-not-valid FAIL. Validating here turns that into a
+ clear error when the framework is loaded.
+ """
+ operator = values.get("Operator")
+ value = values.get("Value")
+ # If Operator/Value failed their own validation they are absent here.
+ if operator is None or value is None:
+ return values
+ if operator in ("in", "subset", "superset"):
+ if not isinstance(value, list):
+ raise ValueError(
+ f"operator '{operator}' requires a list Value, got {type(value).__name__}"
+ )
+ elif operator in ("lte", "gte"):
+ # bool is an int subclass but is never a valid numeric threshold.
+ if isinstance(value, bool) or not isinstance(value, (int, float)):
+ raise ValueError(
+ f"operator '{operator}' requires a numeric Value, got {value!r}"
+ )
+ elif operator == "eq":
+ if not isinstance(value, (bool, int, float, str)):
+ raise ValueError(
+ f"operator 'eq' requires a scalar Value, got {type(value).__name__}"
+ )
+ return values
+
+
# MITRE Requirement Attribute for AWS
class Mitre_Requirement_Attribute_AWS(BaseModel):
"""MITRE Requirement Attribute"""
@@ -216,6 +290,9 @@ class Mitre_Requirement(BaseModel):
list[Mitre_Requirement_Attribute_GCP],
]
Checks: list[str]
+ # MITRE checks may also declare config constraints; without this field
+ # Pydantic silently drops them during parsing.
+ ConfigRequirements: Optional[list[Compliance_Requirement_ConfigConstraint]] = None
# KISA-ISMS-P Requirement Attribute
@@ -282,7 +359,26 @@ class CSA_CCM_Requirement_Attribute(BaseModel):
ScopeApplicability: list[dict]
-# Base Compliance Model
+class STIG_Requirement_Attribute_Severity(str, Enum):
+ """DISA STIG Requirement Attribute Severity (maps to CAT I/II/III)"""
+
+ high = "high"
+ medium = "medium"
+ low = "low"
+
+
+class STIG_Requirement_Attribute(BaseModel):
+ """DISA STIG Requirement Attribute"""
+
+ Section: str
+ Severity: STIG_Requirement_Attribute_Severity
+ RuleID: str
+ StigID: str
+ CCI: Optional[list[str]] = None
+ CheckText: Optional[str] = None
+ FixText: Optional[str] = None
+
+
# TODO: move this to compliance folder
class Compliance_Requirement(BaseModel):
"""Compliance_Requirement holds the base model for every requirement within a compliance framework"""
@@ -302,11 +398,13 @@ class Compliance_Requirement(BaseModel):
CCC_Requirement_Attribute,
C5Germany_Requirement_Attribute,
CSA_CCM_Requirement_Attribute,
+ STIG_Requirement_Attribute,
# Generic_Compliance_Requirement_Attribute must be the last one since it is the fallback for generic compliance framework
Generic_Compliance_Requirement_Attribute,
]
]
Checks: list[str]
+ ConfigRequirements: Optional[list[Compliance_Requirement_ConfigConstraint]] = None
class Compliance(BaseModel):
@@ -434,26 +532,63 @@ class Compliance(BaseModel):
"""Bulk load all compliance frameworks specification into a dict"""
try:
bulk_compliance_frameworks = {}
+ # Built-in compliance from prowler/compliance/{provider}/
available_compliance_framework_modules = list_compliance_modules()
for compliance_framework in available_compliance_framework_modules:
- if provider in compliance_framework.name:
+ # Match the provider segment exactly, not as a substring, so
+ # e.g. `cloud` does not capture `cloudflare`.
+ if compliance_framework.name.split(".")[-1] == provider:
compliance_specification_dir_path = (
f"{compliance_framework.module_finder.path}/{provider}"
)
- # for compliance_framework in available_compliance_framework_modules:
for filename in os.listdir(compliance_specification_dir_path):
file_path = os.path.join(
compliance_specification_dir_path, filename
)
- # Check if it is a file and ti size is greater than 0
if os.path.isfile(file_path) and os.stat(file_path).st_size > 0:
- # Open Compliance file in JSON
- # cis_v1.4_aws.json --> cis_v1.4_aws
compliance_framework_name = filename.split(".json")[0]
- # Store the compliance info
bulk_compliance_frameworks[compliance_framework_name] = (
load_compliance_framework(file_path)
)
+
+ # External compliance via entry points
+ for ep in importlib.metadata.entry_points(group="prowler.compliance"):
+ if ep.name == provider:
+ try:
+ module = ep.load()
+ compliance_dir = (
+ module.__path__[0]
+ if hasattr(module, "__path__")
+ else os.path.dirname(module.__file__)
+ )
+ for filename in os.listdir(compliance_dir):
+ if filename.endswith(".json"):
+ file_path = os.path.join(compliance_dir, filename)
+ if (
+ os.path.isfile(file_path)
+ and os.stat(file_path).st_size > 0
+ ):
+ compliance_framework_name = filename.split(".json")[
+ 0
+ ]
+ if (
+ compliance_framework_name
+ not in bulk_compliance_frameworks
+ ):
+ # External JSON: tolerate non-legacy
+ # schemas (skip + warn) instead of aborting.
+ framework = load_compliance_framework(
+ file_path, fatal=False
+ )
+ if framework is not None:
+ bulk_compliance_frameworks[
+ compliance_framework_name
+ ] = framework
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
except Exception as e:
logger.error(f"{e.__class__.__name__}[{e.__traceback__.tb_lineno}] -- {e}")
@@ -462,18 +597,26 @@ class Compliance(BaseModel):
# Testing Pending
def load_compliance_framework(
- compliance_specification_file: str,
-) -> Compliance:
- """load_compliance_framework loads and parse a Compliance Framework Specification"""
+ compliance_specification_file: str, fatal: bool = True
+) -> Optional[Compliance]:
+ """load_compliance_framework loads and parse a Compliance Framework Specification.
+
+ With ``fatal=True`` (built-in JSONs) an invalid file aborts the run; with
+ ``fatal=False`` (external JSONs) it is skipped with a warning and ``None``
+ is returned.
+ """
try:
- compliance_framework = Compliance.parse_file(compliance_specification_file)
+ return Compliance.parse_file(compliance_specification_file)
except ValidationError as error:
- logger.critical(
- f"Compliance Framework Specification from {compliance_specification_file} is not valid: {error}"
+ if fatal:
+ logger.critical(
+ f"Compliance Framework Specification from {compliance_specification_file} is not valid: {error}"
+ )
+ sys.exit(1)
+ logger.warning(
+ f"Skipping invalid compliance framework {compliance_specification_file}: {error}"
)
- sys.exit(1)
- else:
- return compliance_framework
+ return None
# ─── Universal Compliance Schema Models (Phase 1-3) ─────────────────────────
@@ -634,6 +777,10 @@ class UniversalComplianceRequirement(BaseModel):
name: Optional[str] = None
attributes: dict = Field(default_factory=dict)
checks: dict[str, list[str]] = Field(default_factory=dict)
+ # Typed with the same constraint model as legacy so the operator/value
+ # validation also covers universal frameworks. evaluate_config_constraints
+ # accepts both dicts and model objects, so downstream consumers are unaffected.
+ config_requirements: Optional[list[Compliance_Requirement_ConfigConstraint]] = None
tactics: Optional[list] = None
sub_techniques: Optional[list] = None
platforms: Optional[list] = None
@@ -827,6 +974,11 @@ def adapt_legacy_to_universal(legacy: Compliance) -> ComplianceFramework:
# For MITRE, promote special fields and store raw attributes
raw_attrs = [attr.dict() for attr in req.Attributes]
attrs = {"_raw_attributes": raw_attrs}
+ config_requirements = (
+ [c.dict() for c in req.ConfigRequirements]
+ if getattr(req, "ConfigRequirements", None)
+ else None
+ )
universal_requirements.append(
UniversalComplianceRequirement(
id=req.Id,
@@ -834,6 +986,7 @@ def adapt_legacy_to_universal(legacy: Compliance) -> ComplianceFramework:
name=req.Name,
attributes=attrs,
checks=req_checks,
+ config_requirements=config_requirements,
tactics=req.Tactics,
sub_techniques=req.SubTechniques,
platforms=req.Platforms,
@@ -846,6 +999,11 @@ def adapt_legacy_to_universal(legacy: Compliance) -> ComplianceFramework:
attrs = req.Attributes[0].dict()
else:
attrs = {}
+ config_requirements = (
+ [c.dict() for c in req.ConfigRequirements]
+ if getattr(req, "ConfigRequirements", None)
+ else None
+ )
universal_requirements.append(
UniversalComplianceRequirement(
id=req.Id,
@@ -853,6 +1011,7 @@ def adapt_legacy_to_universal(legacy: Compliance) -> ComplianceFramework:
name=req.Name,
attributes=attrs,
checks=req_checks,
+ config_requirements=config_requirements,
)
)
@@ -950,6 +1109,25 @@ def get_bulk_compliance_frameworks_universal(provider: str) -> dict:
if compliance_root and os.path.isdir(compliance_root):
_load_jsons_from_dir(compliance_root, provider, bulk)
+ # External multi-provider frameworks via the dedicated universal entry
+ # point group, kept separate from the per-provider `prowler.compliance`
+ # group so the legacy loader never parses a universal JSON. Built-ins
+ # (already in bulk) win on a name collision.
+ for ep in importlib.metadata.entry_points(group="prowler.compliance.universal"):
+ try:
+ module = ep.load()
+ ep_dir = (
+ module.__path__[0]
+ if hasattr(module, "__path__")
+ else os.path.dirname(module.__file__)
+ )
+ if os.path.isdir(ep_dir):
+ _load_jsons_from_dir(ep_dir, provider, bulk)
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
except Exception as e:
logger.error(f"{e.__class__.__name__}[{e.__traceback__.tb_lineno}] -- {e}")
return bulk
diff --git a/prowler/lib/check/models.py b/prowler/lib/check/models.py
index d034c5e550..5f92ecf481 100644
--- a/prowler/lib/check/models.py
+++ b/prowler/lib/check/models.py
@@ -11,10 +11,10 @@ from typing import Any, Dict, Optional, Set
from pydantic.v1 import BaseModel, Field, ValidationError, validator
from pydantic.v1.error_wrappers import ErrorWrapper
-from prowler.config.config import EXTERNAL_TOOL_PROVIDERS, Provider
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.check.utils import recover_checks_from_provider
from prowler.lib.logger import logger
+from prowler.providers.common.provider import Provider as ProviderABC
# Valid ResourceGroup values as defined in the RFC
VALID_RESOURCE_GROUPS = frozenset(
@@ -259,7 +259,7 @@ class CheckMetadata(BaseModel):
)
if (
value_lower not in VALID_CATEGORIES
- and values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS
+ and not ProviderABC.is_tool_wrapper_provider(values.get("Provider"))
):
raise ValueError(
f"Invalid category: '{value_lower}'. Must be one of: {', '.join(sorted(VALID_CATEGORIES))}."
@@ -288,7 +288,9 @@ class CheckMetadata(BaseModel):
raise ValueError("ServiceName must be a non-empty string")
check_id = values.get("CheckID")
- if check_id and values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if check_id and not ProviderABC.is_tool_wrapper_provider(
+ values.get("Provider")
+ ):
service_from_check_id = check_id.split("_")[0]
if service_name != service_from_check_id:
raise ValueError(
@@ -304,7 +306,9 @@ class CheckMetadata(BaseModel):
if not check_id:
raise ValueError("CheckID must be a non-empty string")
- if check_id and values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if check_id and not ProviderABC.is_tool_wrapper_provider(
+ values.get("Provider")
+ ):
if "-" in check_id:
raise ValueError(
f"CheckID {check_id} contains a hyphen, which is not allowed"
@@ -313,8 +317,9 @@ class CheckMetadata(BaseModel):
return check_id
@validator("CheckTitle", pre=True, always=True)
+ @classmethod
def validate_check_title(cls, check_title, values): # noqa: F841
- if values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if not ProviderABC.is_tool_wrapper_provider(values.get("Provider")):
if len(check_title) > 150:
raise ValueError(
f"CheckTitle must not exceed 150 characters, got {len(check_title)} characters"
@@ -326,14 +331,18 @@ class CheckMetadata(BaseModel):
return check_title
@validator("RelatedUrl", pre=True, always=True)
+ @classmethod
def validate_related_url(cls, related_url, values): # noqa: F841
- if related_url and values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if related_url and not ProviderABC.is_tool_wrapper_provider(
+ values.get("Provider")
+ ):
raise ValueError("RelatedUrl must be empty. This field is deprecated.")
return related_url
@validator("Remediation")
+ @classmethod
def validate_recommendation_url(cls, remediation, values): # noqa: F841
- if values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if not ProviderABC.is_tool_wrapper_provider(values.get("Provider")):
url = remediation.Recommendation.Url
if url and not url.startswith("https://hub.prowler.com/"):
raise ValueError(
@@ -346,7 +355,7 @@ class CheckMetadata(BaseModel):
provider = values.get("Provider", "").lower()
# Non-AWS providers must have an empty CheckType list
- if provider != "aws" and provider not in EXTERNAL_TOOL_PROVIDERS:
+ if provider != "aws" and not ProviderABC.is_tool_wrapper_provider(provider):
if check_type:
raise ValueError(
f"CheckType must be empty for non-AWS providers. Got {check_type} for provider '{provider}'."
@@ -371,8 +380,9 @@ class CheckMetadata(BaseModel):
return check_type
@validator("Description", pre=True, always=True)
+ @classmethod
def validate_description(cls, description, values): # noqa: F841
- if values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if not ProviderABC.is_tool_wrapper_provider(values.get("Provider")):
if len(description) > 400:
raise ValueError(
f"Description must not exceed 400 characters, got {len(description)} characters"
@@ -380,8 +390,9 @@ class CheckMetadata(BaseModel):
return description
@validator("Risk", pre=True, always=True)
+ @classmethod
def validate_risk(cls, risk, values): # noqa: F841
- if values.get("Provider") not in EXTERNAL_TOOL_PROVIDERS:
+ if not ProviderABC.is_tool_wrapper_provider(values.get("Provider")):
if len(risk) > 400:
raise ValueError(
f"Risk must not exceed 400 characters, got {len(risk)} characters"
@@ -433,6 +444,20 @@ class CheckMetadata(BaseModel):
metadata_file = f"{check_path}/{check_name}.metadata.json"
# Load metadata
check_metadata = load_check_metadata(metadata_file)
+ # Built-in wins on CheckID collision. Plug-in entry points are
+ # appended after built-ins by `recover_checks_from_provider`, so
+ # a duplicate CheckID here means an entry-point check is trying
+ # to override a built-in. Ignore the override (the built-in
+ # metadata stays) and surface it via a warning — matching the
+ # precedence enforced by `_resolve_check_module`.
+ if check_metadata.CheckID in bulk_check_metadata:
+ logger.warning(
+ f"Plug-in check metadata '{check_metadata.CheckID}' "
+ f"(loaded from '{metadata_file}') is being IGNORED — "
+ f"a built-in with the same CheckID exists. To use your "
+ f"plug-in, register it under a different CheckID."
+ )
+ continue
bulk_check_metadata[check_metadata.CheckID] = check_metadata
return bulk_check_metadata
@@ -470,7 +495,7 @@ class CheckMetadata(BaseModel):
# If the bulk checks metadata is not provided, get it
if not bulk_checks_metadata:
bulk_checks_metadata = {}
- available_providers = [p.value for p in Provider]
+ available_providers = ProviderABC.get_available_providers()
for provider_name in available_providers:
bulk_checks_metadata.update(CheckMetadata.get_bulk(provider_name))
if provider:
@@ -495,7 +520,7 @@ class CheckMetadata(BaseModel):
# Loaded here, as it is not always needed
if not bulk_compliance_frameworks:
bulk_compliance_frameworks = {}
- available_providers = [p.value for p in Provider]
+ available_providers = ProviderABC.get_available_providers()
for provider in available_providers:
bulk_compliance_frameworks = Compliance.get_bulk(provider=provider)
checks_from_compliance_framework = (
@@ -1081,6 +1106,37 @@ class CheckReportCloudflare(Check_Report):
return "global"
+@dataclass
+class CheckReportLinode(Check_Report):
+ """Contains the Linode Check's finding information."""
+
+ resource_name: str
+ resource_id: str
+ region: str
+
+ def __init__(
+ self,
+ metadata: Dict,
+ resource: Any,
+ resource_name: str,
+ resource_id: str,
+ region: str = "global",
+ ) -> None:
+ """Initialize the Linode Check's finding information.
+
+ Args:
+ metadata: The metadata of the check.
+ resource: Basic information about the resource.
+ resource_name: The name of the resource related with the finding.
+ resource_id: The id of the resource related with the finding.
+ region: The region of the resource related with the finding.
+ """
+ super().__init__(metadata, resource)
+ self.resource_name = resource_name
+ self.resource_id = resource_id
+ self.region = region
+
+
@dataclass
class CheckReportM365(Check_Report):
"""Contains the M365 Check's finding information."""
@@ -1230,6 +1286,54 @@ class CheckReportNHN(Check_Report):
self.location = getattr(resource, "location", "kr1")
+@dataclass
+class CheckReportE2eNetworks(Check_Report):
+ """Contains the E2E Networks Check's finding information."""
+
+ resource_name: str
+ resource_id: str
+ location: str
+
+ def __init__(self, metadata: Dict, resource: Any) -> None:
+ """Initialize the E2E Networks Check's finding information.
+
+ Args:
+ metadata: The metadata of the check.
+ resource: Basic information about the E2E Networks resource.
+ """
+ super().__init__(metadata, resource)
+ self.resource_name = getattr(
+ resource, "name", getattr(resource, "resource_name", "")
+ )
+ self.resource_id = getattr(resource, "id", getattr(resource, "resource_id", ""))
+ self.location = getattr(resource, "location", "global")
+
+
+@dataclass
+class CheckReportStackIT(Check_Report):
+ """Contains the StackIT Check's finding information."""
+
+ resource_name: str
+ resource_id: str
+ project_id: str
+ location: str
+
+ def __init__(self, metadata: Dict, resource: Any) -> None:
+ """Initialize the StackIT Check's finding information.
+
+ Args:
+ metadata: The metadata of the check.
+ resource: Basic information about the resource. Defaults to None.
+ """
+ super().__init__(metadata, resource)
+ self.resource_name = getattr(
+ resource, "name", getattr(resource, "resource_name", "")
+ )
+ self.resource_id = getattr(resource, "id", getattr(resource, "resource_id", ""))
+ self.project_id = getattr(resource, "project_id", "")
+ self.location = getattr(resource, "region", getattr(resource, "location", ""))
+
+
@dataclass
class CheckReportOpenStack(Check_Report):
"""Contains the OpenStack Check's finding information."""
diff --git a/prowler/lib/check/tool_wrapper.py b/prowler/lib/check/tool_wrapper.py
new file mode 100644
index 0000000000..a1d606594e
--- /dev/null
+++ b/prowler/lib/check/tool_wrapper.py
@@ -0,0 +1,62 @@
+"""Standalone helper for tool-wrapper provider detection.
+
+A provider is a "tool wrapper" if it delegates scanning to an external tool
+(Trivy, promptfoo, etc.) instead of running checks/services through the
+standard Prowler engine. This module is the single source of truth for that
+classification across the codebase.
+
+Kept as a leaf module with no Prowler imports beyond the leaf
+`external_tool_providers` so it can be referenced from `prowler.lib.check.*`
+and `prowler.providers.common.provider` without forming an import cycle.
+"""
+
+import importlib.metadata
+
+from prowler.lib.check.external_tool_providers import EXTERNAL_TOOL_PROVIDERS
+from prowler.providers.common.builtin import is_builtin_provider
+
+# Module-level cache for entry-point classes consulted by this helper.
+# Independent of `Provider._ep_providers` to keep this module leaf — the cost
+# of a duplicate cache entry is negligible (one class object per external
+# provider, loaded lazily on first lookup).
+_ep_class_cache: dict = {}
+
+
+def _load_ep_class(provider: str):
+ """Return the entry-point provider class for `provider`, or None.
+
+ Caches the result in `_ep_class_cache`. Errors during entry-point loading
+ are swallowed (returning None) so a broken plug-in never crashes the
+ is-tool-wrapper check; it just falls through to "not a tool wrapper".
+ """
+ if provider in _ep_class_cache:
+ return _ep_class_cache[provider]
+ for ep in importlib.metadata.entry_points(group="prowler.providers"):
+ if ep.name == provider:
+ try:
+ cls = ep.load()
+ except Exception:
+ cls = None
+ _ep_class_cache[provider] = cls
+ return cls
+ _ep_class_cache[provider] = None
+ return None
+
+
+def is_tool_wrapper_provider(provider: str) -> bool:
+ """Return True if the provider delegates scanning to an external tool.
+
+ Combines the built-in `EXTERNAL_TOOL_PROVIDERS` frozenset (fast path for
+ iac/llm/image) with the `is_external_tool_provider` class attribute of
+ external plug-ins registered via entry points. This is the single source
+ of truth consulted by `__main__`, the `CheckMetadata` validators, the
+ check-loading utilities, and the checks loader.
+ """
+ if provider in EXTERNAL_TOOL_PROVIDERS:
+ return True
+ # Built-in wins: short-circuit before ep.load() so a same-name plug-in
+ # cannot flip a built-in onto the tool-wrapper path or run its code.
+ if is_builtin_provider(provider):
+ return False
+ cls = _load_ep_class(provider)
+ return bool(cls and getattr(cls, "is_external_tool_provider", False))
diff --git a/prowler/lib/check/utils.py b/prowler/lib/check/utils.py
index 0e4807078f..9c9a9c0523 100644
--- a/prowler/lib/check/utils.py
+++ b/prowler/lib/check/utils.py
@@ -1,9 +1,43 @@
import importlib
+import importlib.metadata
+import importlib.util
+import os
import sys
from pkgutil import walk_packages
-from prowler.lib.check.external_tool_providers import EXTERNAL_TOOL_PROVIDERS
+from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
from prowler.lib.logger import logger
+from prowler.providers.common.builtin import is_builtin_provider
+
+
+def _recover_ep_checks(provider: str, service: str = None) -> list[tuple]:
+ """Discover external checks registered via entry points for a provider.
+
+ External plugins follow the same layout as built-ins:
+ `{plugin_root}.services.{service}.{check}.{check}`
+
+ When `service` is provided, only entry points whose dotted path contains
+ `.services.{service}.` are included — mirroring how built-in discovery
+ filters by the `prowler.providers.{provider}.services.{service}` package.
+
+ Uses find_spec to locate the check module without importing it,
+ avoiding service client initialization at discovery time.
+ """
+ checks = []
+ for ep in importlib.metadata.entry_points(group=f"prowler.checks.{provider}"):
+ try:
+ if service and f".services.{service}." not in ep.value:
+ continue
+
+ spec = importlib.util.find_spec(ep.value)
+ if spec and spec.origin:
+ check_path = os.path.dirname(spec.origin)
+ checks.append((ep.name, check_path))
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return checks
def recover_checks_from_provider(
@@ -15,29 +49,55 @@ def recover_checks_from_provider(
Returns a list of tuples with the following format (check_name, check_path)
"""
try:
- # Bypass check loading for providers that use external tools directly
- if provider in EXTERNAL_TOOL_PROVIDERS:
+ # Bypass check loading for tool-wrapper providers — they delegate
+ # scanning to an external tool and have no checks to recover.
+ # Single source of truth: combines the EXTERNAL_TOOL_PROVIDERS
+ # frozenset (built-ins) with the per-provider `is_external_tool_provider`
+ # class attribute (so external plug-ins opt in via the contract).
+ if is_tool_wrapper_provider(provider):
return []
checks = []
- modules = list_modules(provider, service)
- for module_name in modules:
- # Format: "prowler.providers.{provider}.services.{service}.{check_name}.{check_name}"
- check_module_name = module_name.name
- # We need to exclude common shared libraries in services
- if (
- check_module_name.count(".") == 6
- and ".lib." not in check_module_name
- and (not check_module_name.endswith("_fixer") or include_fixers)
- ):
- check_path = module_name.module_finder.path
- # Check name is the last part of the check_module_name
- check_name = check_module_name.split(".")[-1]
- check_info = (check_name, check_path)
- checks.append(check_info)
- except ModuleNotFoundError:
- logger.critical(f"Service {service} was not found for the {provider} provider.")
- sys.exit(1)
+ # Built-in checks from prowler.providers.{provider}.services. Gate
+ # the built-in branch on `is_builtin_provider(provider)` — calling
+ # `find_spec` directly on `prowler.providers.{provider}.services`
+ # would propagate `ModuleNotFoundError` when the parent package
+ # `prowler.providers.{provider}` does not exist (i.e. the provider
+ # is external), instead of returning None. The leaf helper
+ # encapsulates the safe lookup, so we only run the built-in
+ # discovery when the provider actually ships with the SDK; for
+ # external providers we go straight to entry points.
+ if is_builtin_provider(provider):
+ modules = list_modules(provider, service)
+ for module_name in modules:
+ # Format: "prowler.providers.{provider}.services.{service}.{check_name}.{check_name}"
+ check_module_name = module_name.name
+ # We need to exclude common shared libraries in services
+ if (
+ check_module_name.count(".") == 6
+ and ".lib." not in check_module_name
+ and (not check_module_name.endswith("_fixer") or include_fixers)
+ ):
+ check_path = module_name.module_finder.path
+ check_name = check_module_name.split(".")[-1]
+ check_info = (check_name, check_path)
+ checks.append(check_info)
+
+ # External checks registered via entry points — always consulted, with
+ # optional service filter. Previously gated by `if not service:`, which
+ # prevented external providers from being usable with --service.
+ checks.extend(_recover_ep_checks(provider, service))
+
+ # A service was requested but nothing matched in either built-ins or
+ # entry points — surface this as a clear error instead of silently
+ # returning an empty list.
+ if service and not checks:
+ logger.critical(
+ f"Service '{service}' was not found for the '{provider}' provider "
+ f"(neither as a built-in nor via external entry points)."
+ )
+ sys.exit(1)
+
except Exception as e:
logger.critical(f"{e.__class__.__name__}[{e.__traceback__.tb_lineno}]: {e}")
sys.exit(1)
@@ -64,8 +124,9 @@ def recover_checks_from_service(service_list: list, provider: str) -> set:
Returns a set of checks from the given services
"""
try:
- # Bypass check loading for providers that use external tools directly
- if provider in EXTERNAL_TOOL_PROVIDERS:
+ # Bypass check loading for tool-wrapper providers — symmetric with
+ # `recover_checks_from_provider` above, using the same source of truth.
+ if is_tool_wrapper_provider(provider):
return set()
checks = set()
diff --git a/prowler/lib/cli/parser.py b/prowler/lib/cli/parser.py
index 6045302a43..38661e6445 100644
--- a/prowler/lib/cli/parser.py
+++ b/prowler/lib/cli/parser.py
@@ -15,24 +15,70 @@ from prowler.lib.check.models import Severity
from prowler.lib.cli.redact import warn_sensitive_argument_values
from prowler.lib.outputs.common import Status
from prowler.providers.common.arguments import (
+ PROVIDER_ALIASES,
+ enforce_invoked_provider_loaded,
init_providers_parser,
validate_asff_usage,
validate_provider_arguments,
validate_sarif_usage,
)
+from prowler.providers.common.provider import Provider
class ProwlerArgumentParser:
# Set the default parser
def __init__(self):
+ # Discover any providers not in the hardcoded list below
+ # TODO - First step to support current providers and the new external provider implementation
+ known_providers = {
+ "aws",
+ "azure",
+ "gcp",
+ "kubernetes",
+ "m365",
+ "github",
+ "googleworkspace",
+ "cloudflare",
+ "oraclecloud",
+ "openstack",
+ "alibabacloud",
+ "iac",
+ "llm",
+ "image",
+ "nhn",
+ "mongodbatlas",
+ "vercel",
+ "e2enetworks",
+ "okta",
+ "scaleway",
+ "stackit",
+ "linode",
+ }
+ all_providers = set(Provider.get_available_providers())
+ new_providers = sorted(all_providers - known_providers)
+
+ # Build extra strings for dynamically discovered providers
+ extra_providers_csv = ""
+ extra_providers_text = ""
+ if new_providers:
+ providers_help = Provider.get_providers_help_text()
+ extra_providers_csv = "," + ",".join(new_providers)
+ extra_lines = []
+ for name in new_providers:
+ help_text = providers_help.get(name, "")
+ if help_text:
+ extra_lines.append(f" {name:<20}{help_text}")
+ if extra_lines:
+ extra_providers_text = "\n" + "\n".join(extra_lines)
+
# CLI Arguments
self.parser = argparse.ArgumentParser(
prog="prowler",
formatter_class=RawTextHelpFormatter,
- usage="prowler [-h] [--version] {aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,vercel,dashboard,iac,image,llm} ...",
- epilog="""
+ usage=f"prowler [-h] [--version] {{aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,stackit,vercel,linode,e2enetworks,dashboard,iac,image,llm{extra_providers_csv}}} ...",
+ epilog=f"""
Available Cloud Providers:
- {aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,iac,llm,image,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,vercel}
+ {{aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,iac,llm,image,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,stackit,vercel,linode,e2enetworks{extra_providers_csv}}}
aws AWS Provider
azure Azure Provider
gcp GCP Provider
@@ -44,6 +90,7 @@ Available Cloud Providers:
cloudflare Cloudflare Provider
oraclecloud Oracle Cloud Infrastructure Provider
openstack OpenStack Provider
+ stackit StackIT Provider
alibabacloud Alibaba Cloud Provider
iac IaC Provider
llm LLM Provider (Beta)
@@ -52,12 +99,15 @@ Available Cloud Providers:
mongodbatlas MongoDB Atlas Provider
scaleway Scaleway Provider
vercel Vercel Provider
+ linode Linode Provider
+ e2enetworks E2E Networks Provider{extra_providers_text}
+
Available components:
dashboard Local dashboard
To see the different available options on a specific component, run:
- prowler {provider|dashboard} -h|--help
+ prowler {{provider|dashboard}} -h|--help
Detailed documentation at https://docs.prowler.com
""",
@@ -116,17 +166,19 @@ Detailed documentation at https://docs.prowler.com
and (sys.argv[1] not in ("-v", "--version"))
):
# Since the provider is always the second argument, we are checking if
- # a flag, starting by "-", is supplied
- if "-" in sys.argv[1]:
+ # a flag is supplied. Use startswith("-") instead of "in" to avoid
+ # matching external provider names that contain hyphens
+ # (e.g. "local-acme-snowflake").
+ if sys.argv[1].startswith("-"):
sys.argv = self.__set_default_provider__(sys.argv)
- # Provider aliases mapping
- # Microsoft 365
- elif sys.argv[1] == "microsoft365":
- sys.argv[1] = "m365"
- # Oracle Cloud Infrastructure
- elif sys.argv[1] == "oci":
- sys.argv[1] = "oraclecloud"
+ # Provider aliases mapping (single source: arguments.PROVIDER_ALIASES)
+ elif sys.argv[1] in PROVIDER_ALIASES:
+ sys.argv[1] = PROVIDER_ALIASES[sys.argv[1]]
+
+ # Selective fail-loud here (post argv-normalisation, pre parse_args)
+ # so the invoked-provider check stays correct under parse(args=...).
+ enforce_invoked_provider_loaded(self)
# Warn about sensitive flags passed with explicit values
# Snapshot argv before parse_args() which may exit on errors
@@ -423,6 +475,18 @@ Detailed documentation at https://docs.prowler.com
default=default_fixer_config_file_path,
help="Set configuration fixer file path",
)
+ config_parser.add_argument(
+ "--scan-secrets-validate",
+ action="store_true",
+ default=False,
+ help=(
+ "Validate secrets discovered by the secrets checks by checking "
+ "whether they are live against the provider APIs. WARNING: this "
+ "makes outbound network calls using the discovered secret itself; "
+ "the credential is exercised against the provider and the call "
+ "appears in the audited account's logs. Disabled by default."
+ ),
+ )
def __init_custom_checks_metadata_parser__(self):
# CustomChecksMetadata
diff --git a/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight.py b/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight.py
index 75481fb6aa..074e684f33 100644
--- a/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight.py
+++ b/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_asd_essential_eight_table(
@@ -19,15 +26,26 @@ def get_asd_essential_eight_table(
"Status": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ section_seen = {}
+ provider = ""
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
if compliance.Framework == "ASD-Essential-Eight":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
if section not in sections:
@@ -36,21 +54,19 @@ def get_asd_essential_eight_table(
"PASS": 0,
"Muted": 0,
}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- sections[section]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- sections[section]["PASS"] += 1
+ section_seen[section] = {}
+
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, sections[section], section_seen[section]
+ )
sections = dict(sorted(sections.items()))
for section in sections:
- asd_essential_eight_compliance_table["Provider"].append(compliance.Provider)
+ asd_essential_eight_compliance_table["Provider"].append(provider)
asd_essential_eight_compliance_table["Section"].append(section)
if sections[section]["FAIL"] > 0:
asd_essential_eight_compliance_table["Status"].append(
diff --git a/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_aws.py b/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_aws.py
index 78ef53c5e6..4bdf9cd851 100644
--- a/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_aws.py
+++ b/prowler/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.asd_essential_eight.models import (
ASDEssentialEightAWSModel,
@@ -36,10 +40,19 @@ class ASDEssentialEightAWS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ASDEssentialEightAWSModel(
Provider=finding.provider,
@@ -63,8 +76,8 @@ class ASDEssentialEightAWS(ComplianceOutput):
Requirements_Attributes_AuditProcedure=attribute.AuditProcedure,
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/aws_well_architected/aws_well_architected.py b/prowler/lib/outputs/compliance/aws_well_architected/aws_well_architected.py
index 38352484c2..69a37949f8 100644
--- a/prowler/lib/outputs/compliance/aws_well_architected/aws_well_architected.py
+++ b/prowler/lib/outputs/compliance/aws_well_architected/aws_well_architected.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.aws_well_architected.models import (
AWSWellArchitectedModel,
@@ -36,11 +40,18 @@ class AWSWellArchitected(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSWellArchitectedModel(
Provider=finding.provider,
@@ -59,8 +70,8 @@ class AWSWellArchitected(ComplianceOutput):
Requirements_Attributes_AssessmentMethod=attribute.AssessmentMethod,
Requirements_Attributes_Description=attribute.Description,
Requirements_Attributes_ImplementationGuidanceUrl=attribute.ImplementationGuidanceUrl,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/c5/c5.py b/prowler/lib/outputs/compliance/c5/c5.py
index 32eb7e0f5a..003b2664cf 100644
--- a/prowler/lib/outputs/compliance/c5/c5.py
+++ b/prowler/lib/outputs/compliance/c5/c5.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_c5_table(
@@ -18,37 +25,45 @@ def get_c5_table(
"Status": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
sections = {}
+ section_seen = {}
+ provider = ""
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
if compliance.Framework == "C5":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
if section not in sections:
sections[section] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ section_seen[section] = {}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- sections[section]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- sections[section]["PASS"] += 1
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, sections[section], section_seen[section]
+ )
sections = dict(sorted(sections.items()))
for section in sections:
- section_table["Provider"].append(compliance.Provider)
+ section_table["Provider"].append(provider)
section_table["Section"].append(section)
if sections[section]["FAIL"] > 0:
section_table["Status"].append(
diff --git a/prowler/lib/outputs/compliance/c5/c5_aws.py b/prowler/lib/outputs/compliance/c5/c5_aws.py
index 24d5239602..b8a4115482 100644
--- a/prowler/lib/outputs/compliance/c5/c5_aws.py
+++ b/prowler/lib/outputs/compliance/c5/c5_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.c5.models import AWSC5Model
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class AWSC5(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSC5Model(
Provider=finding.provider,
@@ -53,8 +65,8 @@ class AWSC5(ComplianceOutput):
Requirements_Attributes_Type=attribute.Type,
Requirements_Attributes_AboutCriteria=attribute.AboutCriteria,
Requirements_Attributes_ComplementaryCriteria=attribute.ComplementaryCriteria,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/c5/c5_azure.py b/prowler/lib/outputs/compliance/c5/c5_azure.py
index 3c050a6581..0899ff6b15 100644
--- a/prowler/lib/outputs/compliance/c5/c5_azure.py
+++ b/prowler/lib/outputs/compliance/c5/c5_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.c5.models import AzureC5Model
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class AzureC5(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AzureC5Model(
Provider=finding.provider,
@@ -53,8 +65,8 @@ class AzureC5(ComplianceOutput):
Requirements_Attributes_Type=attribute.Type,
Requirements_Attributes_AboutCriteria=attribute.AboutCriteria,
Requirements_Attributes_ComplementaryCriteria=attribute.ComplementaryCriteria,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/c5/c5_gcp.py b/prowler/lib/outputs/compliance/c5/c5_gcp.py
index 85ee9c25e9..c8b874f622 100644
--- a/prowler/lib/outputs/compliance/c5/c5_gcp.py
+++ b/prowler/lib/outputs/compliance/c5/c5_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.c5.models import GCPC5Model
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class GCPC5(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GCPC5Model(
Provider=finding.provider,
@@ -53,8 +65,8 @@ class GCPC5(ComplianceOutput):
Requirements_Attributes_Type=attribute.Type,
Requirements_Attributes_AboutCriteria=attribute.AboutCriteria,
Requirements_Attributes_ComplementaryCriteria=attribute.ComplementaryCriteria,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/ccc/ccc.py b/prowler/lib/outputs/compliance/ccc/ccc.py
index 99a6c91cd9..48b2086e78 100644
--- a/prowler/lib/outputs/compliance/ccc/ccc.py
+++ b/prowler/lib/outputs/compliance/ccc/ccc.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_ccc_table(
@@ -18,37 +25,45 @@ def get_ccc_table(
"Status": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
sections = {}
+ section_seen = {}
+ provider = ""
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
if compliance.Framework == "CCC":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
if section not in sections:
sections[section] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ section_seen[section] = {}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- sections[section]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- sections[section]["PASS"] += 1
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, sections[section], section_seen[section]
+ )
sections = dict(sorted(sections.items()))
for section in sections:
- section_table["Provider"].append(compliance.Provider)
+ section_table["Provider"].append(provider)
section_table["Section"].append(section)
if sections[section]["FAIL"] > 0:
section_table["Status"].append(
diff --git a/prowler/lib/outputs/compliance/ccc/ccc_aws.py b/prowler/lib/outputs/compliance/ccc/ccc_aws.py
index a9de0aeca7..20d42b1508 100644
--- a/prowler/lib/outputs/compliance/ccc/ccc_aws.py
+++ b/prowler/lib/outputs/compliance/ccc/ccc_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.ccc.models import CCC_AWSModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class CCC_AWS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = CCC_AWSModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class CCC_AWS(ComplianceOutput):
Requirements_Attributes_Recommendation=attribute.Recommendation,
Requirements_Attributes_SectionThreatMappings=attribute.SectionThreatMappings,
Requirements_Attributes_SectionGuidelineMappings=attribute.SectionGuidelineMappings,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/ccc/ccc_azure.py b/prowler/lib/outputs/compliance/ccc/ccc_azure.py
index 2801b91f97..4dcc8c5ca8 100644
--- a/prowler/lib/outputs/compliance/ccc/ccc_azure.py
+++ b/prowler/lib/outputs/compliance/ccc/ccc_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.ccc.models import CCC_AzureModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class CCC_Azure(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = CCC_AzureModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class CCC_Azure(ComplianceOutput):
Requirements_Attributes_Recommendation=attribute.Recommendation,
Requirements_Attributes_SectionThreatMappings=attribute.SectionThreatMappings,
Requirements_Attributes_SectionGuidelineMappings=attribute.SectionGuidelineMappings,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/ccc/ccc_gcp.py b/prowler/lib/outputs/compliance/ccc/ccc_gcp.py
index 9793834776..ed7c709c24 100644
--- a/prowler/lib/outputs/compliance/ccc/ccc_gcp.py
+++ b/prowler/lib/outputs/compliance/ccc/ccc_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.ccc.models import CCC_GCPModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class CCC_GCP(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = CCC_GCPModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class CCC_GCP(ComplianceOutput):
Requirements_Attributes_Recommendation=attribute.Recommendation,
Requirements_Attributes_SectionThreatMappings=attribute.SectionThreatMappings,
Requirements_Attributes_SectionGuidelineMappings=attribute.SectionGuidelineMappings,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis.py b/prowler/lib/outputs/compliance/cis/cis.py
index 7f161f34c2..de3120f689 100644
--- a/prowler/lib/outputs/compliance/cis/cis.py
+++ b/prowler/lib/outputs/compliance/cis/cis.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_cis_table(
@@ -13,6 +20,9 @@ def get_cis_table(
compliance_overview: bool,
):
sections = {}
+ section_muted_seen = {}
+ section_split_seen = {}
+ provider = ""
cis_compliance_table = {
"Provider": [],
"Section": [],
@@ -20,16 +30,25 @@ def get_cis_table(
"Level 2": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
version_in_name = compliance_framework.split("_")[1]
if compliance.Framework == "CIS" and version_in_name in compliance.Version:
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
# Check if Section exists
@@ -40,32 +59,44 @@ def get_cis_table(
"Level 2": {"FAIL": 0, "PASS": 0},
"Muted": 0,
}
+ section_muted_seen[section] = set()
+ section_split_seen[section] = {
+ "Level 1": {},
+ "Level 2": {},
+ }
+
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
+ # Per-section Muted: count each finding once per section
+ # it belongs to (a finding can map to several sections).
+ if index not in section_muted_seen[section]:
+ section_muted_seen[section].add(index)
sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
+
if "Level 1" in attribute.Profile:
if not finding.muted:
- if finding.status == "FAIL":
- sections[section]["Level 1"]["FAIL"] += 1
- else:
- sections[section]["Level 1"]["PASS"] += 1
+ accumulate_group_status(
+ index,
+ effective_status,
+ sections[section]["Level 1"],
+ section_split_seen[section]["Level 1"],
+ )
elif "Level 2" in attribute.Profile:
if not finding.muted:
- if finding.status == "FAIL":
- sections[section]["Level 2"]["FAIL"] += 1
- else:
- sections[section]["Level 2"]["PASS"] += 1
+ accumulate_group_status(
+ index,
+ effective_status,
+ sections[section]["Level 2"],
+ section_split_seen[section]["Level 2"],
+ )
# Add results to table
sections = dict(sorted(sections.items()))
for section in sections:
- cis_compliance_table["Provider"].append(compliance.Provider)
+ cis_compliance_table["Provider"].append(provider)
cis_compliance_table["Section"].append(section)
if sections[section]["Level 1"]["FAIL"] > 0:
cis_compliance_table["Level 1"].append(
diff --git a/prowler/lib/outputs/compliance/cis/cis_alibabacloud.py b/prowler/lib/outputs/compliance/cis/cis_alibabacloud.py
index adf8ef2af1..77bf02ee98 100644
--- a/prowler/lib/outputs/compliance/cis/cis_alibabacloud.py
+++ b/prowler/lib/outputs/compliance/cis/cis_alibabacloud.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import AlibabaCloudCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class AlibabaCloudCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AlibabaCloudCISModel(
Provider=finding.provider,
@@ -60,8 +71,8 @@ class AlibabaCloudCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_aws.py b/prowler/lib/outputs/compliance/cis/cis_aws.py
index 749a3b7463..58bf7fbc27 100644
--- a/prowler/lib/outputs/compliance/cis/cis_aws.py
+++ b/prowler/lib/outputs/compliance/cis/cis_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import AWSCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,19 @@ class AWSCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSCISModel(
Provider=finding.provider,
@@ -60,8 +72,8 @@ class AWSCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_azure.py b/prowler/lib/outputs/compliance/cis/cis_azure.py
index 5c5e4cd486..53b1cbdd32 100644
--- a/prowler/lib/outputs/compliance/cis/cis_azure.py
+++ b/prowler/lib/outputs/compliance/cis/cis_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import AzureCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class AzureCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AzureCISModel(
Provider=finding.provider,
@@ -60,8 +71,8 @@ class AzureCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_gcp.py b/prowler/lib/outputs/compliance/cis/cis_gcp.py
index 328726aa9b..c2a11dae77 100644
--- a/prowler/lib/outputs/compliance/cis/cis_gcp.py
+++ b/prowler/lib/outputs/compliance/cis/cis_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import GCPCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class GCPCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GCPCISModel(
Provider=finding.provider,
@@ -59,8 +70,8 @@ class GCPCIS(ComplianceOutput):
Requirements_Attributes_AuditProcedure=attribute.AuditProcedure,
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_github.py b/prowler/lib/outputs/compliance/cis/cis_github.py
index 0082b891e5..039bd1b993 100644
--- a/prowler/lib/outputs/compliance/cis/cis_github.py
+++ b/prowler/lib/outputs/compliance/cis/cis_github.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import GithubCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class GithubCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GithubCISModel(
Provider=finding.provider,
@@ -59,8 +70,8 @@ class GithubCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_References=attribute.References,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_googleworkspace.py b/prowler/lib/outputs/compliance/cis/cis_googleworkspace.py
index a4b58bb3b4..cf2d3755c7 100644
--- a/prowler/lib/outputs/compliance/cis/cis_googleworkspace.py
+++ b/prowler/lib/outputs/compliance/cis/cis_googleworkspace.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import GoogleWorkspaceCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class GoogleWorkspaceCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GoogleWorkspaceCISModel(
Provider=finding.provider,
@@ -59,8 +70,8 @@ class GoogleWorkspaceCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_kubernetes.py b/prowler/lib/outputs/compliance/cis/cis_kubernetes.py
index e8fee839fc..23c482310e 100644
--- a/prowler/lib/outputs/compliance/cis/cis_kubernetes.py
+++ b/prowler/lib/outputs/compliance/cis/cis_kubernetes.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import KubernetesCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class KubernetesCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = KubernetesCISModel(
Provider=finding.provider,
@@ -60,8 +71,8 @@ class KubernetesCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_References=attribute.References,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_m365.py b/prowler/lib/outputs/compliance/cis/cis_m365.py
index 3c7de43542..8dc06155e7 100644
--- a/prowler/lib/outputs/compliance/cis/cis_m365.py
+++ b/prowler/lib/outputs/compliance/cis/cis_m365.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import M365CISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class M365CIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = M365CISModel(
Provider=finding.provider,
@@ -60,8 +71,8 @@ class M365CIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cis/cis_oraclecloud.py b/prowler/lib/outputs/compliance/cis/cis_oraclecloud.py
index 19e6e1d8c8..d8110d72db 100644
--- a/prowler/lib/outputs/compliance/cis/cis_oraclecloud.py
+++ b/prowler/lib/outputs/compliance/cis/cis_oraclecloud.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cis.models import OracleCloudCISModel
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
@@ -34,11 +38,18 @@ class OracleCloudCIS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = OracleCloudCISModel(
Provider=finding.provider,
@@ -60,8 +71,8 @@ class OracleCloudCIS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_DefaultValue=attribute.DefaultValue,
Requirements_Attributes_References=attribute.References,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/cisa_scuba/cisa_scuba_googleworkspace.py b/prowler/lib/outputs/compliance/cisa_scuba/cisa_scuba_googleworkspace.py
index 8250d1bcce..d2f6faa212 100644
--- a/prowler/lib/outputs/compliance/cisa_scuba/cisa_scuba_googleworkspace.py
+++ b/prowler/lib/outputs/compliance/cisa_scuba/cisa_scuba_googleworkspace.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.cisa_scuba.models import (
GoogleWorkspaceCISASCuBAModel,
@@ -36,11 +40,18 @@ class GoogleWorkspaceCISASCuBA(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GoogleWorkspaceCISASCuBAModel(
Provider=finding.provider,
@@ -53,8 +64,8 @@ class GoogleWorkspaceCISASCuBA(ComplianceOutput):
Requirements_Attributes_SubSection=attribute.SubSection,
Requirements_Attributes_Service=attribute.Service,
Requirements_Attributes_Type=attribute.Type,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/compliance.py b/prowler/lib/outputs/compliance/compliance.py
index b6b2f1f81f..4e4bd78232 100644
--- a/prowler/lib/outputs/compliance/compliance.py
+++ b/prowler/lib/outputs/compliance/compliance.py
@@ -10,7 +10,6 @@ from prowler.lib.outputs.compliance.cis.cis import get_cis_table
from prowler.lib.outputs.compliance.compliance_check import ( # noqa: F401 - re-export for backward compatibility
get_check_compliance,
)
-from prowler.lib.outputs.compliance.csa.csa import get_csa_table
from prowler.lib.outputs.compliance.ens.ens import get_ens_table
from prowler.lib.outputs.compliance.generic.generic_table import (
get_generic_compliance_table,
@@ -19,6 +18,9 @@ from prowler.lib.outputs.compliance.kisa_ismsp.kisa_ismsp import get_kisa_ismsp_
from prowler.lib.outputs.compliance.mitre_attack.mitre_attack import (
get_mitre_attack_table,
)
+from prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig import (
+ get_okta_idaas_stig_table,
+)
from prowler.lib.outputs.compliance.prowler_threatscore.prowler_threatscore import (
get_prowler_threatscore_table,
)
@@ -33,24 +35,28 @@ def process_universal_compliance_frameworks(
output_filename: str,
provider: str,
generated_outputs: dict,
+ from_cli: bool = True,
+ is_last: bool = True,
) -> set:
"""Process universal compliance frameworks, generating CSV and OCSF outputs.
For each framework in *input_compliance_frameworks* that exists in
- *universal_frameworks* and has an outputs.table_config, this function
- creates both a CSV (UniversalComplianceOutput) and an OCSF JSON
- (OCSFComplianceOutput) file. OCSF is always generated regardless of
+ *universal_frameworks* and has an ``outputs.table_config``, this function
+ writes both a CSV (``UniversalComplianceOutput``) and an OCSF JSON
+ (``OCSFComplianceOutput``) file. OCSF is always generated regardless of
the user's ``--output-formats`` flag.
- The function is idempotent: it tracks already-created writers via
- ``generated_outputs["compliance"]`` keyed by ``file_path``. If invoked
- again for the same framework (e.g. once per streaming batch), it
- reuses the existing writer instead of recreating it. This guarantees
- one output writer per framework for the whole execution and keeps
- the OCSF JSON array valid across multiple calls.
+ Streaming-aware: writers are tracked via ``generated_outputs["compliance"]``
+ keyed by ``file_path``. On the first call per framework a new writer is
+ created and emits both findings and manual requirements; subsequent calls
+ reuse the writer, transform only the new ``finding_outputs`` (manual
+ requirements are not re-emitted), and append to the open file. Set
+ ``from_cli=False`` and ``is_last=False`` for intermediate batches; pass
+ ``is_last=True`` on the final batch to close the file (OCSF is also
+ finalized as a valid JSON array).
- Returns the set of framework names that were processed so the caller
- can remove them before entering the legacy per-provider output loop.
+ Returns the set of framework names processed so the caller can subtract
+ them from the legacy per-provider output loop.
"""
from prowler.lib.outputs.compliance.universal.ocsf_compliance import (
OCSFComplianceOutput,
@@ -65,6 +71,13 @@ def process_universal_compliance_frameworks(
if isinstance(out, (UniversalComplianceOutput, OCSFComplianceOutput))
}
+ def _flush(writer, framework, label, is_new):
+ if not is_new:
+ writer._transform(finding_outputs, framework, label, include_manual=False)
+ writer.close_file = is_last
+ writer.batch_write_data_to_file()
+ writer._data.clear()
+
processed = set()
for compliance_name in input_compliance_frameworks:
if not (
@@ -75,37 +88,46 @@ def process_universal_compliance_frameworks(
continue
fw = universal_frameworks[compliance_name]
+ compliance_label = (
+ fw.framework + "-" + fw.version if fw.version else fw.framework
+ )
# CSV output
csv_path = (
f"{output_directory}/compliance/" f"{output_filename}_{compliance_name}.csv"
)
- if csv_path not in existing_writers:
- output = UniversalComplianceOutput(
+ csv_writer = existing_writers.get(csv_path)
+ csv_is_new = csv_writer is None
+ if csv_is_new:
+ csv_writer = UniversalComplianceOutput(
findings=finding_outputs,
framework=fw,
file_path=csv_path,
+ from_cli=from_cli,
provider=provider,
)
- generated_outputs["compliance"].append(output)
- existing_writers[csv_path] = output
- output.batch_write_data_to_file()
+ generated_outputs["compliance"].append(csv_writer)
+ existing_writers[csv_path] = csv_writer
+ _flush(csv_writer, fw, compliance_label, csv_is_new)
# OCSF output (always generated for universal frameworks)
ocsf_path = (
f"{output_directory}/compliance/"
f"{output_filename}_{compliance_name}.ocsf.json"
)
- if ocsf_path not in existing_writers:
- ocsf_output = OCSFComplianceOutput(
+ ocsf_writer = existing_writers.get(ocsf_path)
+ ocsf_is_new = ocsf_writer is None
+ if ocsf_is_new:
+ ocsf_writer = OCSFComplianceOutput(
findings=finding_outputs,
framework=fw,
file_path=ocsf_path,
+ from_cli=from_cli,
provider=provider,
)
- generated_outputs["compliance"].append(ocsf_output)
- existing_writers[ocsf_path] = ocsf_output
- ocsf_output.batch_write_data_to_file()
+ generated_outputs["compliance"].append(ocsf_writer)
+ existing_writers[ocsf_path] = ocsf_writer
+ _flush(ocsf_writer, fw, compliance_label, ocsf_is_new)
processed.add(compliance_name)
@@ -206,15 +228,6 @@ def display_compliance_table(
output_directory,
compliance_overview,
)
- elif compliance_framework.startswith("csa_ccm_"):
- get_csa_table(
- findings,
- bulk_checks_metadata,
- compliance_framework,
- output_filename,
- output_directory,
- compliance_overview,
- )
elif compliance_framework.startswith("c5_"):
get_c5_table(
findings,
@@ -242,8 +255,8 @@ def display_compliance_table(
output_directory,
compliance_overview,
)
- else:
- get_generic_compliance_table(
+ elif compliance_framework.startswith("okta_idaas_stig"):
+ get_okta_idaas_stig_table(
findings,
bulk_checks_metadata,
compliance_framework,
@@ -251,6 +264,33 @@ def display_compliance_table(
output_directory,
compliance_overview,
)
+ else:
+ # Try provider-specific table first, fall back to generic
+ from prowler.providers.common.provider import Provider
+
+ provider = Provider.get_global_provider()
+ handled = False
+ if provider is not None:
+ try:
+ handled = provider.display_compliance_table(
+ findings,
+ bulk_checks_metadata,
+ compliance_framework,
+ output_filename,
+ output_directory,
+ compliance_overview,
+ )
+ except NotImplementedError:
+ handled = False
+ if not handled:
+ get_generic_compliance_table(
+ findings,
+ bulk_checks_metadata,
+ compliance_framework,
+ output_filename,
+ output_directory,
+ compliance_overview,
+ )
except Exception as error:
logger.critical(
f"{error.__class__.__name__}:{error.__traceback__.tb_lineno} -- {error}"
diff --git a/prowler/lib/outputs/compliance/csa/csa_alibabacloud.py b/prowler/lib/outputs/compliance/csa/csa_alibabacloud.py
deleted file mode 100644
index 084edbaa4b..0000000000
--- a/prowler/lib/outputs/compliance/csa/csa_alibabacloud.py
+++ /dev/null
@@ -1,96 +0,0 @@
-from prowler.config.config import timestamp
-from prowler.lib.check.compliance_models import Compliance
-from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
-from prowler.lib.outputs.compliance.csa.models import AlibabaCloudCSAModel
-from prowler.lib.outputs.finding import Finding
-
-
-class AlibabaCloudCSA(ComplianceOutput):
- """
- This class represents the Alibaba Cloud CSA compliance output.
-
- Attributes:
- - _data (list): A list to store transformed data from findings.
- - _file_descriptor (TextIOWrapper): A file descriptor to write data to a file.
-
- Methods:
- - transform: Transforms findings into Alibaba Cloud CSA compliance format.
- """
-
- def transform(
- self,
- findings: list[Finding],
- compliance: Compliance,
- compliance_name: str,
- ) -> None:
- """
- Transforms a list of findings into Alibaba Cloud CSA compliance format.
-
- Parameters:
- - findings (list): A list of findings.
- - compliance (Compliance): A compliance model.
- - compliance_name (str): The name of the compliance model.
-
- Returns:
- - None
- """
- for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
- for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
- for attribute in requirement.Attributes:
- compliance_row = AlibabaCloudCSAModel(
- Provider=finding.provider,
- Description=compliance.Description,
- AccountId=finding.account_uid,
- Region=finding.region,
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status=finding.status,
- StatusExtended=finding.status_extended,
- ResourceId=finding.resource_uid,
- ResourceName=finding.resource_name,
- CheckId=finding.check_id,
- Muted=finding.muted,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
- # Add manual requirements to the compliance output
- for requirement in compliance.Requirements:
- if not requirement.Checks:
- for attribute in requirement.Attributes:
- compliance_row = AlibabaCloudCSAModel(
- Provider=compliance.Provider.lower(),
- Description=compliance.Description,
- AccountId="",
- Region="",
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status="MANUAL",
- StatusExtended="Manual check",
- ResourceId="manual_check",
- ResourceName="Manual check",
- CheckId="manual",
- Muted=False,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
diff --git a/prowler/lib/outputs/compliance/csa/csa_aws.py b/prowler/lib/outputs/compliance/csa/csa_aws.py
deleted file mode 100644
index 0f371bfb3a..0000000000
--- a/prowler/lib/outputs/compliance/csa/csa_aws.py
+++ /dev/null
@@ -1,96 +0,0 @@
-from prowler.config.config import timestamp
-from prowler.lib.check.compliance_models import Compliance
-from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
-from prowler.lib.outputs.compliance.csa.models import AWSCSAModel
-from prowler.lib.outputs.finding import Finding
-
-
-class AWSCSA(ComplianceOutput):
- """
- This class represents the AWS CSA compliance output.
-
- Attributes:
- - _data (list): A list to store transformed data from findings.
- - _file_descriptor (TextIOWrapper): A file descriptor to write data to a file.
-
- Methods:
- - transform: Transforms findings into AWS CSA compliance format.
- """
-
- def transform(
- self,
- findings: list[Finding],
- compliance: Compliance,
- compliance_name: str,
- ) -> None:
- """
- Transforms a list of findings into AWS CSA compliance format.
-
- Parameters:
- - findings (list): A list of findings.
- - compliance (Compliance): A compliance model.
- - compliance_name (str): The name of the compliance model.
-
- Returns:
- - None
- """
- for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
- for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
- for attribute in requirement.Attributes:
- compliance_row = AWSCSAModel(
- Provider=finding.provider,
- Description=compliance.Description,
- AccountId=finding.account_uid,
- Region=finding.region,
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status=finding.status,
- StatusExtended=finding.status_extended,
- ResourceId=finding.resource_uid,
- ResourceName=finding.resource_name,
- CheckId=finding.check_id,
- Muted=finding.muted,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
- # Add manual requirements to the compliance output
- for requirement in compliance.Requirements:
- if not requirement.Checks:
- for attribute in requirement.Attributes:
- compliance_row = AWSCSAModel(
- Provider=compliance.Provider.lower(),
- Description=compliance.Description,
- AccountId="",
- Region="",
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status="MANUAL",
- StatusExtended="Manual check",
- ResourceId="manual_check",
- ResourceName="Manual check",
- CheckId="manual",
- Muted=False,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
diff --git a/prowler/lib/outputs/compliance/csa/csa_azure.py b/prowler/lib/outputs/compliance/csa/csa_azure.py
deleted file mode 100644
index 9bb16e6f11..0000000000
--- a/prowler/lib/outputs/compliance/csa/csa_azure.py
+++ /dev/null
@@ -1,96 +0,0 @@
-from prowler.config.config import timestamp
-from prowler.lib.check.compliance_models import Compliance
-from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
-from prowler.lib.outputs.compliance.csa.models import AzureCSAModel
-from prowler.lib.outputs.finding import Finding
-
-
-class AzureCSA(ComplianceOutput):
- """
- This class represents the Azure CSA compliance output.
-
- Attributes:
- - _data (list): A list to store transformed data from findings.
- - _file_descriptor (TextIOWrapper): A file descriptor to write data to a file.
-
- Methods:
- - transform: Transforms findings into Azure CSA compliance format.
- """
-
- def transform(
- self,
- findings: list[Finding],
- compliance: Compliance,
- compliance_name: str,
- ) -> None:
- """
- Transforms a list of findings into Azure CSA compliance format.
-
- Parameters:
- - findings (list): A list of findings.
- - compliance (Compliance): A compliance model.
- - compliance_name (str): The name of the compliance model.
-
- Returns:
- - None
- """
- for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
- for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
- for attribute in requirement.Attributes:
- compliance_row = AzureCSAModel(
- Provider=finding.provider,
- Description=compliance.Description,
- SubscriptionId=finding.account_uid,
- Location=finding.region,
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status=finding.status,
- StatusExtended=finding.status_extended,
- ResourceId=finding.resource_uid,
- ResourceName=finding.resource_name,
- CheckId=finding.check_id,
- Muted=finding.muted,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
- # Add manual requirements to the compliance output
- for requirement in compliance.Requirements:
- if not requirement.Checks:
- for attribute in requirement.Attributes:
- compliance_row = AzureCSAModel(
- Provider=compliance.Provider.lower(),
- Description=compliance.Description,
- SubscriptionId="",
- Location="",
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status="MANUAL",
- StatusExtended="Manual check",
- ResourceId="manual_check",
- ResourceName="Manual check",
- CheckId="manual",
- Muted=False,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
diff --git a/prowler/lib/outputs/compliance/csa/csa_gcp.py b/prowler/lib/outputs/compliance/csa/csa_gcp.py
deleted file mode 100644
index 5c1b400525..0000000000
--- a/prowler/lib/outputs/compliance/csa/csa_gcp.py
+++ /dev/null
@@ -1,96 +0,0 @@
-from prowler.config.config import timestamp
-from prowler.lib.check.compliance_models import Compliance
-from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
-from prowler.lib.outputs.compliance.csa.models import GCPCSAModel
-from prowler.lib.outputs.finding import Finding
-
-
-class GCPCSA(ComplianceOutput):
- """
- This class represents the GCP CSA compliance output.
-
- Attributes:
- - _data (list): A list to store transformed data from findings.
- - _file_descriptor (TextIOWrapper): A file descriptor to write data to a file.
-
- Methods:
- - transform: Transforms findings into GCP CSA compliance format.
- """
-
- def transform(
- self,
- findings: list[Finding],
- compliance: Compliance,
- compliance_name: str,
- ) -> None:
- """
- Transforms a list of findings into GCP CSA compliance format.
-
- Parameters:
- - findings (list): A list of findings.
- - compliance (Compliance): A compliance model.
- - compliance_name (str): The name of the compliance model.
-
- Returns:
- - None
- """
- for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
- for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
- for attribute in requirement.Attributes:
- compliance_row = GCPCSAModel(
- Provider=finding.provider,
- Description=compliance.Description,
- ProjectId=finding.account_uid,
- Location=finding.region,
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status=finding.status,
- StatusExtended=finding.status_extended,
- ResourceId=finding.resource_uid,
- ResourceName=finding.resource_name,
- CheckId=finding.check_id,
- Muted=finding.muted,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
- # Add manual requirements to the compliance output
- for requirement in compliance.Requirements:
- if not requirement.Checks:
- for attribute in requirement.Attributes:
- compliance_row = GCPCSAModel(
- Provider=compliance.Provider.lower(),
- Description=compliance.Description,
- ProjectId="",
- Location="",
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Name=requirement.Name,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status="MANUAL",
- StatusExtended="Manual check",
- ResourceId="manual_check",
- ResourceName="Manual check",
- CheckId="manual",
- Muted=False,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
diff --git a/prowler/lib/outputs/compliance/csa/models.py b/prowler/lib/outputs/compliance/csa/models.py
deleted file mode 100644
index 78c7384fc6..0000000000
--- a/prowler/lib/outputs/compliance/csa/models.py
+++ /dev/null
@@ -1,146 +0,0 @@
-from pydantic.v1 import BaseModel
-
-
-class AWSCSAModel(BaseModel):
- """
- AWSCSAModel generates a finding's output in CSV CSA format for AWS.
- """
-
- Provider: str
- Description: str
- AccountId: str
- Region: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- Requirements_Name: str
- Requirements_Attributes_Section: str
- Requirements_Attributes_CCMLite: str
- Requirements_Attributes_IaaS: str
- Requirements_Attributes_PaaS: str
- Requirements_Attributes_SaaS: str
- Requirements_Attributes_ScopeApplicability: list[dict]
- Status: str
- StatusExtended: str
- ResourceId: str
- CheckId: str
- Muted: bool
- ResourceName: str
- Framework: str
- Name: str
-
-
-class GCPCSAModel(BaseModel):
- """
- GCPCSAModel generates a finding's output in CSV CSA format for GCP.
- """
-
- Provider: str
- Description: str
- ProjectId: str
- Location: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- Requirements_Name: str
- Requirements_Attributes_Section: str
- Requirements_Attributes_CCMLite: str
- Requirements_Attributes_IaaS: str
- Requirements_Attributes_PaaS: str
- Requirements_Attributes_SaaS: str
- Requirements_Attributes_ScopeApplicability: list[dict]
- Status: str
- StatusExtended: str
- ResourceId: str
- CheckId: str
- Muted: bool
- ResourceName: str
- Framework: str
- Name: str
-
-
-class OracleCloudCSAModel(BaseModel):
- """
- OracleCloudCSAModel generates a finding's output in CSV CSA format for OracleCloud.
- """
-
- Provider: str
- Description: str
- TenancyId: str
- Region: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- Requirements_Name: str
- Requirements_Attributes_Section: str
- Requirements_Attributes_CCMLite: str
- Requirements_Attributes_IaaS: str
- Requirements_Attributes_PaaS: str
- Requirements_Attributes_SaaS: str
- Requirements_Attributes_ScopeApplicability: list[dict]
- Status: str
- StatusExtended: str
- ResourceId: str
- CheckId: str
- Muted: bool
- ResourceName: str
- Framework: str
- Name: str
-
-
-class AlibabaCloudCSAModel(BaseModel):
- """
- AlibabaCloudCSAModel generates a finding's output in CSV CSA format for Alibaba Cloud.
- """
-
- Provider: str
- Description: str
- AccountId: str
- Region: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- Requirements_Name: str
- Requirements_Attributes_Section: str
- Requirements_Attributes_CCMLite: str
- Requirements_Attributes_IaaS: str
- Requirements_Attributes_PaaS: str
- Requirements_Attributes_SaaS: str
- Requirements_Attributes_ScopeApplicability: list[dict]
- Status: str
- StatusExtended: str
- ResourceId: str
- CheckId: str
- Muted: bool
- ResourceName: str
- Framework: str
- Name: str
-
-
-class AzureCSAModel(BaseModel):
- """
- AzureCSAModel generates a finding's output in CSV CSA format for Azure.
- """
-
- Provider: str
- Description: str
- SubscriptionId: str
- Location: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- Requirements_Name: str
- Requirements_Attributes_Section: str
- Requirements_Attributes_CCMLite: str
- Requirements_Attributes_IaaS: str
- Requirements_Attributes_PaaS: str
- Requirements_Attributes_SaaS: str
- Requirements_Attributes_ScopeApplicability: list[dict]
- Status: str
- StatusExtended: str
- ResourceId: str
- CheckId: str
- Muted: bool
- ResourceName: str
- Framework: str
- Name: str
diff --git a/prowler/lib/outputs/compliance/ens/ens.py b/prowler/lib/outputs/compliance/ens/ens.py
index a414a0206d..4fcca922c7 100644
--- a/prowler/lib/outputs/compliance/ens/ens.py
+++ b/prowler/lib/outputs/compliance/ens/ens.py
@@ -2,6 +2,11 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_ens_table(
@@ -13,6 +18,8 @@ def get_ens_table(
compliance_overview: bool,
):
marcos = {}
+ marco_muted_seen = {}
+ provider = ""
ens_compliance_table = {
"Proveedor": [],
"Marco/Categoria": [],
@@ -23,15 +30,24 @@ def get_ens_table(
"Opcional": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
if compliance.Framework == "ENS":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
marco_categoria = f"{attribute.Marco}/{attribute.Categoria}"
# Check if Marco/Categoria exists
@@ -44,22 +60,27 @@ def get_ens_table(
"Bajo": 0,
"Muted": 0,
}
+ marco_muted_seen[marco_categoria] = set()
if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
+ # Overview total: count each finding once per framework
+ muted_count.add(index)
+ # Per-marco Muted: count each finding once per marco
+ # it belongs to (a finding can map to several marcos).
+ if index not in marco_muted_seen[marco_categoria]:
+ marco_muted_seen[marco_categoria].add(index)
marcos[marco_categoria]["Muted"] += 1
else:
- if finding.status == "FAIL":
- if (
- attribute.Tipo != "recomendacion"
- and index not in fail_count
- ):
- fail_count.append(index)
+ if effective_status == "FAIL":
+ if attribute.Tipo != "recomendacion":
+ fail_count.add(index)
+ pass_count.discard(index)
+ # Mark every marco the finding belongs to as
+ # NO CUMPLE, not just the first one seen.
marcos[marco_categoria][
"Estado"
] = f"{Fore.RED}NO CUMPLE{Style.RESET_ALL}"
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
+ elif effective_status == "PASS" and index not in fail_count:
+ pass_count.add(index)
if attribute.Nivel == "opcional":
marcos[marco_categoria]["Opcional"] += 1
elif attribute.Nivel == "alto":
@@ -71,7 +92,7 @@ def get_ens_table(
# Add results to table
for marco in sorted(marcos):
- ens_compliance_table["Proveedor"].append(compliance.Provider)
+ ens_compliance_table["Proveedor"].append(provider)
ens_compliance_table["Marco/Categoria"].append(marco)
ens_compliance_table["Estado"].append(marcos[marco]["Estado"])
ens_compliance_table["Opcional"].append(
diff --git a/prowler/lib/outputs/compliance/ens/ens_aws.py b/prowler/lib/outputs/compliance/ens/ens_aws.py
index 01a212d9af..543799f7b9 100644
--- a/prowler/lib/outputs/compliance/ens/ens_aws.py
+++ b/prowler/lib/outputs/compliance/ens/ens_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.ens.models import AWSENSModel
@@ -34,11 +38,19 @@ class AWSENS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSENSModel(
Provider=finding.provider,
@@ -61,8 +73,8 @@ class AWSENS(ComplianceOutput):
Requirements_Attributes_Dependencias=",".join(
attribute.Dependencias
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/ens/ens_azure.py b/prowler/lib/outputs/compliance/ens/ens_azure.py
index 35385ab673..23055da2a2 100644
--- a/prowler/lib/outputs/compliance/ens/ens_azure.py
+++ b/prowler/lib/outputs/compliance/ens/ens_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.ens.models import AzureENSModel
@@ -34,11 +38,19 @@ class AzureENS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AzureENSModel(
Provider=finding.provider,
@@ -61,8 +73,8 @@ class AzureENS(ComplianceOutput):
Requirements_Attributes_Dependencias=",".join(
attribute.Dependencias
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/ens/ens_gcp.py b/prowler/lib/outputs/compliance/ens/ens_gcp.py
index 81d6d33b14..f616e48f83 100644
--- a/prowler/lib/outputs/compliance/ens/ens_gcp.py
+++ b/prowler/lib/outputs/compliance/ens/ens_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.ens.models import GCPENSModel
@@ -34,11 +38,19 @@ class GCPENS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GCPENSModel(
Provider=finding.provider,
@@ -61,8 +73,8 @@ class GCPENS(ComplianceOutput):
Requirements_Attributes_Dependencias=",".join(
attribute.Dependencias
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/generic/generic.py b/prowler/lib/outputs/compliance/generic/generic.py
index d9dbe8abe9..b3f1ad7ec9 100644
--- a/prowler/lib/outputs/compliance/generic/generic.py
+++ b/prowler/lib/outputs/compliance/generic/generic.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.generic.models import GenericComplianceModel
@@ -34,61 +38,61 @@ class GenericCompliance(ComplianceOutput):
Returns:
- None
"""
+
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
+ def compliance_row(requirement, attribute, finding=None):
+ # Read attribute fields defensively: GenericCompliance is the
+ # last-resort renderer for any framework, and provider-specific
+ # schemas (e.g. CIS, ENS, ISO27001) do not declare the universal
+ # Section/SubSection/SubGroup/Service/Type/Comment fields.
+ status, status_extended = (
+ apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
+ if finding
+ else ("MANUAL", "Manual check")
+ )
+ return GenericComplianceModel(
+ Provider=(finding.provider if finding else compliance.Provider.lower()),
+ Description=compliance.Description,
+ AccountId=finding.account_uid if finding else "",
+ Region=finding.region if finding else "",
+ AssessmentDate=str(timestamp),
+ Requirements_Id=requirement.Id,
+ Requirements_Description=requirement.Description,
+ Requirements_Attributes_Section=getattr(attribute, "Section", None),
+ Requirements_Attributes_SubSection=getattr(
+ attribute, "SubSection", None
+ ),
+ Requirements_Attributes_SubGroup=getattr(attribute, "SubGroup", None),
+ Requirements_Attributes_Service=getattr(attribute, "Service", None),
+ Requirements_Attributes_Type=getattr(attribute, "Type", None),
+ Requirements_Attributes_Comment=getattr(attribute, "Comment", None),
+ Status=status,
+ StatusExtended=status_extended,
+ ResourceId=finding.resource_uid if finding else "manual_check",
+ ResourceName=finding.resource_name if finding else "Manual check",
+ CheckId=finding.check_id if finding else "manual",
+ Muted=finding.muted if finding else False,
+ Framework=compliance.Framework,
+ Name=compliance.Name,
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
for attribute in requirement.Attributes:
- compliance_row = GenericComplianceModel(
- Provider=finding.provider,
- Description=compliance.Description,
- AccountId=finding.account_uid,
- Region=finding.region,
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_SubSection=attribute.SubSection,
- Requirements_Attributes_SubGroup=attribute.SubGroup,
- Requirements_Attributes_Service=attribute.Service,
- Requirements_Attributes_Type=attribute.Type,
- Requirements_Attributes_Comment=attribute.Comment,
- Status=finding.status,
- StatusExtended=finding.status_extended,
- ResourceId=finding.resource_uid,
- ResourceName=finding.resource_name,
- CheckId=finding.check_id,
- Muted=finding.muted,
- Framework=compliance.Framework,
- Name=compliance.Name,
+ self._data.append(
+ compliance_row(requirement, attribute, finding)
)
- self._data.append(compliance_row)
# Add manual requirements to the compliance output
for requirement in compliance.Requirements:
if not requirement.Checks:
for attribute in requirement.Attributes:
- compliance_row = GenericComplianceModel(
- Provider=compliance.Provider.lower(),
- Description=compliance.Description,
- AccountId="",
- Region="",
- AssessmentDate=str(timestamp),
- Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
- Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_SubSection=attribute.SubSection,
- Requirements_Attributes_SubGroup=attribute.SubGroup,
- Requirements_Attributes_Service=attribute.Service,
- Requirements_Attributes_Type=attribute.Type,
- Requirements_Attributes_Comment=attribute.Comment,
- Status="MANUAL",
- StatusExtended="Manual check",
- ResourceId="manual_check",
- ResourceName="Manual check",
- CheckId="manual",
- Muted=False,
- Framework=compliance.Framework,
- Name=compliance.Name,
- )
- self._data.append(compliance_row)
+ self._data.append(compliance_row(requirement, attribute))
diff --git a/prowler/lib/outputs/compliance/generic/generic_table.py b/prowler/lib/outputs/compliance/generic/generic_table.py
index 9136cf19e2..060acda10a 100644
--- a/prowler/lib/outputs/compliance/generic/generic_table.py
+++ b/prowler/lib/outputs/compliance/generic/generic_table.py
@@ -2,6 +2,11 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_generic_compliance_table(
@@ -15,6 +20,8 @@ def get_generic_compliance_table(
pass_count = []
fail_count = []
muted_count = []
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
@@ -25,13 +32,21 @@ def get_generic_compliance_table(
and compliance.Version in compliance_framework.upper()
and compliance.Provider.upper() in compliance_framework.upper()
):
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- else:
- if finding.status == "FAIL" and index not in fail_count:
+ for requirement in compliance.Requirements:
+ # A configurable check that passed with a too-loose config is
+ # forced to FAIL (source of truth: framework ConfigRequirements).
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
+ if finding.muted:
+ if index not in muted_count:
+ muted_count.append(index)
+ elif effective_status == "FAIL" and index not in fail_count:
fail_count.append(index)
- elif finding.status == "PASS" and index not in pass_count:
+ elif effective_status == "PASS" and index not in pass_count:
pass_count.append(index)
if (
len(fail_count) + len(pass_count) + len(muted_count) > 1
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_aws.py b/prowler/lib/outputs/compliance/iso27001/iso27001_aws.py
index b6da583af2..3376b8c5ad 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_aws.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import AWSISO27001Model
@@ -34,11 +38,18 @@ class AWSISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSISO27001Model(
Provider=finding.provider,
@@ -53,8 +64,8 @@ class AWSISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_azure.py b/prowler/lib/outputs/compliance/iso27001/iso27001_azure.py
index 1e36005440..f1f964c726 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_azure.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import AzureISO27001Model
@@ -34,11 +38,18 @@ class AzureISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AzureISO27001Model(
Provider=finding.provider,
@@ -53,8 +64,8 @@ class AzureISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_gcp.py b/prowler/lib/outputs/compliance/iso27001/iso27001_gcp.py
index 9f08e3d920..9a5de17bfa 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_gcp.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import GCPISO27001Model
@@ -34,11 +38,18 @@ class GCPISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = GCPISO27001Model(
Provider=finding.provider,
@@ -53,8 +64,8 @@ class GCPISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_kubernetes.py b/prowler/lib/outputs/compliance/iso27001/iso27001_kubernetes.py
index b0e8904ebe..5ca81e82d5 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_kubernetes.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_kubernetes.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import KubernetesISO27001Model
@@ -34,11 +38,18 @@ class KubernetesISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = KubernetesISO27001Model(
Provider=finding.provider,
@@ -53,8 +64,8 @@ class KubernetesISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_m365.py b/prowler/lib/outputs/compliance/iso27001/iso27001_m365.py
index cf12bbd841..84c5072002 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_m365.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_m365.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import M365ISO27001Model
@@ -34,10 +38,18 @@ class M365ISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = M365ISO27001Model(
Provider=finding.provider,
@@ -52,8 +64,8 @@ class M365ISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/iso27001/iso27001_nhn.py b/prowler/lib/outputs/compliance/iso27001/iso27001_nhn.py
index 6c89b7333f..ad8ea6dcab 100644
--- a/prowler/lib/outputs/compliance/iso27001/iso27001_nhn.py
+++ b/prowler/lib/outputs/compliance/iso27001/iso27001_nhn.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.iso27001.models import NHNISO27001Model
@@ -34,10 +38,18 @@ class NHNISO27001(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = NHNISO27001Model(
Provider=finding.provider,
@@ -52,8 +64,8 @@ class NHNISO27001(ComplianceOutput):
Requirements_Attributes_Objetive_ID=attribute.Objetive_ID,
Requirements_Attributes_Objetive_Name=attribute.Objetive_Name,
Requirements_Attributes_Check_Summary=attribute.Check_Summary,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
CheckId=finding.check_id,
Muted=finding.muted,
diff --git a/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp.py b/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp.py
index 93b925a5ff..dda83342b6 100644
--- a/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp.py
+++ b/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp.py
@@ -2,6 +2,12 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_kisa_ismsp_table(
@@ -13,16 +19,20 @@ def get_kisa_ismsp_table(
compliance_overview: bool,
):
sections = {}
+ section_seen = {}
sections_status = {}
+ provider = ""
kisa_ismsp_compliance_table = {
"Provider": [],
"Section": [],
"Status": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
@@ -31,7 +41,14 @@ def get_kisa_ismsp_table(
compliance.Framework.startswith("KISA")
and compliance.Version in compliance_framework
):
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
# Check if Section exists
@@ -43,17 +60,27 @@ def get_kisa_ismsp_table(
},
"Muted": 0,
}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
+ section_seen[section] = {}
+
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+
+ # FAIL/PASS live under ["Status"], Muted at top level.
+ previous = section_seen[section].get(index)
+ if previous is None:
+ section_seen[section][index] = status
+ if status == "Muted":
sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
+ elif status == "FAIL":
sections[section]["Status"]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
+ elif status == "PASS":
sections[section]["Status"]["PASS"] += 1
+ elif previous == "PASS" and status == "FAIL":
+ section_seen[section][index] = "FAIL"
+ sections[section]["Status"]["PASS"] -= 1
+ sections[section]["Status"]["FAIL"] += 1
# Add results to table
sections = dict(sorted(sections.items()))
@@ -70,7 +97,7 @@ def get_kisa_ismsp_table(
else:
sections_status[section] = f"{Fore.GREEN}PASS{Style.RESET_ALL}"
for section in sections:
- kisa_ismsp_compliance_table["Provider"].append(compliance.Provider)
+ kisa_ismsp_compliance_table["Provider"].append(provider)
kisa_ismsp_compliance_table["Section"].append(section)
kisa_ismsp_compliance_table["Status"].append(sections_status[section])
kisa_ismsp_compliance_table["Muted"].append(
diff --git a/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_aws.py b/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_aws.py
index f65430b1a3..3d05632d26 100644
--- a/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_aws.py
+++ b/prowler/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.kisa_ismsp.models import AWSKISAISMSPModel
@@ -34,11 +38,19 @@ class AWSKISAISMSP(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = AWSKISAISMSPModel(
Provider=finding.provider,
@@ -56,8 +68,8 @@ class AWSKISAISMSP(ComplianceOutput):
Requirements_Attributes_RelatedRegulations=attribute.RelatedRegulations,
Requirements_Attributes_AuditEvidence=attribute.AuditEvidence,
Requirements_Attributes_NonComplianceCases=attribute.NonComplianceCases,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack.py b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack.py
index bab3e4e31a..a352acfa6e 100644
--- a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack.py
+++ b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
def get_mitre_attack_table(
@@ -13,15 +20,19 @@ def get_mitre_attack_table(
compliance_overview: bool,
):
tactics = {}
+ tactic_seen = {}
+ provider = ""
mitre_compliance_table = {
"Provider": [],
"Tactic": [],
"Status": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
@@ -30,27 +41,29 @@ def get_mitre_attack_table(
"MITRE-ATTACK" in compliance.Framework
and compliance.Version in compliance_framework
):
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
+ status = "Muted" if finding.muted else effective_status
for tactic in requirement.Tactics:
if tactic not in tactics:
tactics[tactic] = {"FAIL": 0, "PASS": 0, "Muted": 0}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- tactics[tactic]["Muted"] += 1
- else:
- if finding.status == "FAIL":
- if index not in fail_count:
- fail_count.append(index)
- tactics[tactic]["FAIL"] += 1
- elif finding.status == "PASS":
- if index not in pass_count:
- pass_count.append(index)
- tactics[tactic]["PASS"] += 1
+ tactic_seen[tactic] = {}
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, tactics[tactic], tactic_seen[tactic]
+ )
# Add results to table
tactics = dict(sorted(tactics.items()))
for tactic in tactics:
- mitre_compliance_table["Provider"].append(compliance.Provider)
+ mitre_compliance_table["Provider"].append(provider)
mitre_compliance_table["Tactic"].append(tactic)
if tactics[tactic]["FAIL"] > 0:
mitre_compliance_table["Status"].append(
diff --git a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_aws.py b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_aws.py
index 9a4c4fc2c3..92f4ac0e5b 100644
--- a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_aws.py
+++ b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.mitre_attack.models import AWSMitreAttackModel
@@ -35,11 +39,19 @@ class AWSMitreAttack(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
compliance_row = AWSMitreAttackModel(
Provider=finding.provider,
Description=compliance.Description,
@@ -67,8 +79,8 @@ class AWSMitreAttack(ComplianceOutput):
Requirements_Attributes_Comments=", ".join(
attribute.Comment for attribute in requirement.Attributes
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_azure.py b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_azure.py
index 5787bbfba6..a43e27e775 100644
--- a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_azure.py
+++ b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.mitre_attack.models import AzureMitreAttackModel
@@ -35,11 +39,19 @@ class AzureMitreAttack(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
compliance_row = AzureMitreAttackModel(
Provider=finding.provider,
Description=compliance.Description,
@@ -68,8 +80,8 @@ class AzureMitreAttack(ComplianceOutput):
Requirements_Attributes_Comments=", ".join(
attribute.Comment for attribute in requirement.Attributes
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_gcp.py b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_gcp.py
index bae7920e43..b8efdc5250 100644
--- a/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_gcp.py
+++ b/prowler/lib/outputs/compliance/mitre_attack/mitre_attack_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.mitre_attack.models import GCPMitreAttackModel
@@ -35,11 +39,19 @@ class GCPMitreAttack(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
compliance_row = GCPMitreAttackModel(
Provider=finding.provider,
Description=compliance.Description,
@@ -67,8 +79,8 @@ class GCPMitreAttack(ComplianceOutput):
Requirements_Attributes_Comments=", ".join(
attribute.Comment for attribute in requirement.Attributes
),
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/tests/lib/timeline/__init__.py b/prowler/lib/outputs/compliance/okta_idaas_stig/__init__.py
similarity index 100%
rename from tests/lib/timeline/__init__.py
rename to prowler/lib/outputs/compliance/okta_idaas_stig/__init__.py
diff --git a/prowler/lib/outputs/compliance/okta_idaas_stig/models.py b/prowler/lib/outputs/compliance/okta_idaas_stig/models.py
new file mode 100644
index 0000000000..674d9656b7
--- /dev/null
+++ b/prowler/lib/outputs/compliance/okta_idaas_stig/models.py
@@ -0,0 +1,32 @@
+from typing import Optional
+
+from pydantic.v1 import BaseModel
+
+
+class OktaIDaaSSTIGModel(BaseModel):
+ """
+ OktaIDaaSSTIGModel generates a finding's output in DISA Okta IDaaS STIG Compliance format.
+ """
+
+ Provider: str
+ Description: str
+ OrganizationDomain: str
+ AssessmentDate: str
+ Requirements_Id: str
+ Requirements_Name: str
+ Requirements_Description: str
+ Requirements_Attributes_Section: str
+ Requirements_Attributes_Severity: str
+ Requirements_Attributes_RuleID: str
+ Requirements_Attributes_StigID: str
+ Requirements_Attributes_CCI: Optional[list[str]] = None
+ Requirements_Attributes_CheckText: Optional[str] = None
+ Requirements_Attributes_FixText: Optional[str] = None
+ Status: str
+ StatusExtended: str
+ ResourceId: str
+ ResourceName: str
+ CheckId: str
+ Muted: bool
+ Framework: str
+ Name: str
diff --git a/prowler/lib/outputs/compliance/csa/csa.py b/prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig.py
similarity index 68%
rename from prowler/lib/outputs/compliance/csa/csa.py
rename to prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig.py
index ab8a021a70..ef6bb2742a 100644
--- a/prowler/lib/outputs/compliance/csa/csa.py
+++ b/prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig.py
@@ -2,9 +2,14 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
-def get_csa_table(
+def get_okta_idaas_stig_table(
findings: list,
bulk_checks_metadata: dict,
compliance_framework: str,
@@ -22,36 +27,57 @@ def get_csa_table(
fail_count = []
muted_count = []
sections = {}
+ section_seen = {}
+ provider = ""
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
- if (
- compliance.Framework == "CSA-CCM"
- and compliance.Version in compliance_framework
- ):
+ if compliance.Framework == "Okta-IDaaS-STIG":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ # A configurable check that passed with a too-loose config is
+ # forced to FAIL (source of truth: framework ConfigRequirements).
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
section = attribute.Section
if section not in sections:
sections[section] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ section_seen[section] = set()
+ # Overview totals: count each finding once per framework
if finding.muted:
if index not in muted_count:
muted_count.append(index)
- sections[section]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
+ elif effective_status == "FAIL":
+ if index not in fail_count:
fail_count.append(index)
- sections[section]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
+ elif effective_status == "PASS":
+ if index not in pass_count:
pass_count.append(index)
+
+ # Per-section counts: count each finding once per section
+ # it belongs to (a finding can map to several sections).
+ if index not in section_seen[section]:
+ section_seen[section].add(index)
+ if finding.muted:
+ sections[section]["Muted"] += 1
+ elif effective_status == "FAIL":
+ sections[section]["FAIL"] += 1
+ elif effective_status == "PASS":
sections[section]["PASS"] += 1
sections = dict(sorted(sections.items()))
for section in sections:
- section_table["Provider"].append(compliance.Provider)
+ section_table["Provider"].append(provider)
section_table["Section"].append(section)
if sections[section]["FAIL"] > 0:
section_table["Status"].append(
diff --git a/prowler/lib/outputs/compliance/csa/csa_oraclecloud.py b/prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta.py
similarity index 55%
rename from prowler/lib/outputs/compliance/csa/csa_oraclecloud.py
rename to prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta.py
index 9b3d36c168..b8a72f9f95 100644
--- a/prowler/lib/outputs/compliance/csa/csa_oraclecloud.py
+++ b/prowler/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta.py
@@ -1,62 +1,73 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
-from prowler.lib.outputs.compliance.csa.models import OracleCloudCSAModel
+from prowler.lib.outputs.compliance.okta_idaas_stig.models import OktaIDaaSSTIGModel
from prowler.lib.outputs.finding import Finding
-class OracleCloudCSA(ComplianceOutput):
+class OktaIDaaSSTIG(ComplianceOutput):
"""
- This class represents the OracleCloud CSA compliance output.
+ This class represents the Okta IDaaS STIG compliance output.
Attributes:
- _data (list): A list to store transformed data from findings.
- _file_descriptor (TextIOWrapper): A file descriptor to write data to a file.
Methods:
- - transform: Transforms findings into OracleCloud CSA compliance format.
+ - transform: Transforms findings into Okta IDaaS STIG compliance format.
"""
def transform(
self,
findings: list[Finding],
compliance: Compliance,
- compliance_name: str,
+ _compliance_name: str,
) -> None:
"""
- Transforms a list of findings into OracleCloud CSA compliance format.
+ Transforms a list of findings into Okta IDaaS STIG compliance format.
Parameters:
- findings (list): A list of findings.
- compliance (Compliance): A compliance model.
- - compliance_name (str): The name of the compliance model.
+ - _compliance_name (str): The name of the compliance model (unused).
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
- compliance_row = OracleCloudCSAModel(
+ compliance_row = OktaIDaaSSTIGModel(
Provider=finding.provider,
Description=compliance.Description,
- TenancyId=finding.account_uid,
- Region=finding.region,
+ OrganizationDomain=finding.account_name,
AssessmentDate=str(timestamp),
Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
Requirements_Name=requirement.Name,
+ Requirements_Description=requirement.Description,
Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Requirements_Attributes_Severity=attribute.Severity.value,
+ Requirements_Attributes_RuleID=attribute.RuleID,
+ Requirements_Attributes_StigID=attribute.StigID,
+ Requirements_Attributes_CCI=attribute.CCI,
+ Requirements_Attributes_CheckText=attribute.CheckText,
+ Requirements_Attributes_FixText=attribute.FixText,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
@@ -69,21 +80,21 @@ class OracleCloudCSA(ComplianceOutput):
for requirement in compliance.Requirements:
if not requirement.Checks:
for attribute in requirement.Attributes:
- compliance_row = OracleCloudCSAModel(
+ compliance_row = OktaIDaaSSTIGModel(
Provider=compliance.Provider.lower(),
Description=compliance.Description,
- TenancyId="",
- Region="",
+ OrganizationDomain="",
AssessmentDate=str(timestamp),
Requirements_Id=requirement.Id,
- Requirements_Description=requirement.Description,
Requirements_Name=requirement.Name,
+ Requirements_Description=requirement.Description,
Requirements_Attributes_Section=attribute.Section,
- Requirements_Attributes_CCMLite=attribute.CCMLite,
- Requirements_Attributes_IaaS=attribute.IaaS,
- Requirements_Attributes_PaaS=attribute.PaaS,
- Requirements_Attributes_SaaS=attribute.SaaS,
- Requirements_Attributes_ScopeApplicability=attribute.ScopeApplicability,
+ Requirements_Attributes_Severity=attribute.Severity.value,
+ Requirements_Attributes_RuleID=attribute.RuleID,
+ Requirements_Attributes_StigID=attribute.StigID,
+ Requirements_Attributes_CCI=attribute.CCI,
+ Requirements_Attributes_CheckText=attribute.CheckText,
+ Requirements_Attributes_FixText=attribute.FixText,
Status="MANUAL",
StatusExtended="Manual check",
ResourceId="manual_check",
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore.py
index cfcd4a006e..cb23d67ffb 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
@@ -20,22 +27,33 @@ def get_prowler_threatscore_table(
"Score": [],
"Muted": [],
}
- pass_count = []
- fail_count = []
- muted_count = []
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
pillars = {}
+ pillar_seen = {}
+ provider = ""
generic_score = 0
max_generic_score = 0
- counted_findings_generic = []
+ counted_findings_generic = {}
score_per_pillar = {}
max_score_per_pillar = {}
counted_findings_per_pillar = {}
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check = bulk_checks_metadata[finding.check_metadata.CheckID]
check_compliances = check.Compliance
for compliance in check_compliances:
if compliance.Framework == "ProwlerThreatScore":
+ provider = compliance.Provider
for requirement in compliance.Requirements:
+ config_status = resolve_requirement_config_status(
+ requirement, audit_config, config_status_cache
+ )
+ effective_status = get_effective_status(
+ finding.status, config_status
+ )
for attribute in requirement.Attributes:
pillar = attribute.Section
@@ -48,60 +66,68 @@ def get_prowler_threatscore_table(
):
score_per_pillar[pillar] = 0
max_score_per_pillar[pillar] = 0
- counted_findings_per_pillar[pillar] = []
+ counted_findings_per_pillar[pillar] = {}
- if (
- index not in counted_findings_per_pillar[pillar]
- and not finding.muted
- ):
- if finding.status == "PASS":
- score_per_pillar[pillar] += (
- attribute.LevelOfRisk * attribute.Weight
- )
- max_score_per_pillar[pillar] += (
- attribute.LevelOfRisk * attribute.Weight
- )
- counted_findings_per_pillar[pillar].append(index)
+ # Revoke an earlier PASS score if a later requirement FAILs.
+ if not finding.muted:
+ contribution = attribute.LevelOfRisk * attribute.Weight
+ counted = counted_findings_per_pillar[pillar]
+ if index not in counted:
+ max_score_per_pillar[pillar] += contribution
+ if effective_status == "PASS":
+ score_per_pillar[pillar] += contribution
+ counted[index] = contribution
+ else:
+ counted[index] = 0
+ elif effective_status == "FAIL" and counted[index]:
+ score_per_pillar[pillar] -= counted[index]
+ counted[index] = 0
if pillar not in pillars:
pillars[pillar] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ pillar_seen[pillar] = {}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- pillars[pillar]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- pillars[pillar]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- pillars[pillar]["PASS"] += 1
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, pillars[pillar], pillar_seen[pillar]
+ )
- # Generic score
- if index not in counted_findings_generic and not finding.muted:
- if finding.status == "PASS":
- generic_score += (
- attribute.LevelOfRisk * attribute.Weight
- )
- max_generic_score += (
- attribute.LevelOfRisk * attribute.Weight
- )
- counted_findings_generic.append(index)
+ # Generic score, with the same PASS-revocation on FAIL.
+ if not finding.muted:
+ contribution = attribute.LevelOfRisk * attribute.Weight
+ if index not in counted_findings_generic:
+ max_generic_score += contribution
+ if effective_status == "PASS":
+ generic_score += contribution
+ counted_findings_generic[index] = contribution
+ else:
+ counted_findings_generic[index] = 0
+ elif (
+ effective_status == "FAIL"
+ and counted_findings_generic[index]
+ ):
+ generic_score -= counted_findings_generic[index]
+ counted_findings_generic[index] = 0
no_findings_pillars = []
- bulk_compliance = Compliance.get_bulk(provider=compliance.Provider.lower()).get(
- compliance_framework
+ bulk_compliance = (
+ Compliance.get_bulk(provider=provider.lower()).get(compliance_framework)
+ if provider
+ else None
)
- for requirement in bulk_compliance.Requirements:
- for attribute in requirement.Attributes:
- pillar = attribute.Section
- if pillar not in pillars.keys() and pillar not in no_findings_pillars:
- no_findings_pillars.append(pillar)
+ if bulk_compliance:
+ for requirement in bulk_compliance.Requirements:
+ for attribute in requirement.Attributes:
+ pillar = attribute.Section
+ if pillar not in pillars.keys() and pillar not in no_findings_pillars:
+ no_findings_pillars.append(pillar)
pillars = dict(sorted(pillars.items()))
for pillar in pillars:
- pillar_table["Provider"].append(compliance.Provider)
+ pillar_table["Provider"].append(provider)
pillar_table["Pillar"].append(pillar)
if max_score_per_pillar[pillar] == 0:
pillar_score = 100.0
@@ -127,7 +153,7 @@ def get_prowler_threatscore_table(
)
for pillar in no_findings_pillars:
- pillar_table["Provider"].append(compliance.Provider)
+ pillar_table["Provider"].append(provider)
pillar_table["Pillar"].append(pillar)
pillar_table["Score"].append(f"{Style.BRIGHT}{Fore.GREEN}100%{Style.RESET_ALL}")
pillar_table["Status"].append(f"{Fore.GREEN}PASS{Style.RESET_ALL}")
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_alibaba.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_alibaba.py
index 66fabe51b3..7d682a3e62 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_alibaba.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_alibaba.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreAlibaba(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreAlibabaModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreAlibaba(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_aws.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_aws.py
index b896e55528..f1280808e3 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_aws.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_aws.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreAWS(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreAWSModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreAWS(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_azure.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_azure.py
index bbc3749843..5118511369 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_azure.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_azure.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreAzure(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreAzureModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreAzure(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_gcp.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_gcp.py
index 4b03e269a3..39f9c23850 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_gcp.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_gcp.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreGCP(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreGCPModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreGCP(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_kubernetes.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_kubernetes.py
index 7b35dab312..88bf41582a 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_kubernetes.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_kubernetes.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreKubernetes(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreKubernetesModel(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreKubernetes(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_m365.py b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_m365.py
index 6b0cc88a15..b7b533c72a 100644
--- a/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_m365.py
+++ b/prowler/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_m365.py
@@ -1,4 +1,8 @@
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import Compliance
from prowler.lib.outputs.compliance.compliance_output import ComplianceOutput
from prowler.lib.outputs.compliance.prowler_threatscore.models import (
@@ -36,11 +40,19 @@ class ProwlerThreatScoreM365(ComplianceOutput):
Returns:
- None
"""
+ requirement_config_status = build_requirement_config_status(
+ compliance.Requirements
+ )
+
for finding in findings:
- # Get the compliance requirements for the finding
- finding_requirements = finding.compliance.get(compliance_name, [])
for requirement in compliance.Requirements:
- if requirement.Id in finding_requirements:
+ # Source of truth: framework JSON, not finding.compliance snapshot (avoids CSV/UI count drift).
+ if finding.check_id in requirement.Checks:
+ row_status, row_status_extended = apply_config_status(
+ finding.status,
+ finding.status_extended,
+ requirement_config_status.get(requirement.Id),
+ )
for attribute in requirement.Attributes:
compliance_row = ProwlerThreatScoreM365Model(
Provider=finding.provider,
@@ -57,8 +69,8 @@ class ProwlerThreatScoreM365(ComplianceOutput):
Requirements_Attributes_AdditionalInformation=attribute.AdditionalInformation,
Requirements_Attributes_LevelOfRisk=attribute.LevelOfRisk,
Requirements_Attributes_Weight=attribute.Weight,
- Status=finding.status,
- StatusExtended=finding.status_extended,
+ Status=row_status,
+ StatusExtended=row_status_extended,
ResourceId=finding.resource_uid,
ResourceName=finding.resource_name,
CheckId=finding.check_id,
diff --git a/prowler/lib/outputs/compliance/universal/ocsf_compliance.py b/prowler/lib/outputs/compliance/universal/ocsf_compliance.py
index 2ce69412e1..07c1f67b10 100644
--- a/prowler/lib/outputs/compliance/universal/ocsf_compliance.py
+++ b/prowler/lib/outputs/compliance/universal/ocsf_compliance.py
@@ -19,6 +19,10 @@ from py_ocsf_models.objects.product import Product
from py_ocsf_models.objects.resource_details import ResourceDetails
from prowler.config.config import prowler_version
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import ComplianceFramework
from prowler.lib.logger import logger
from prowler.lib.outputs.utils import unroll_dict_to_list
@@ -79,30 +83,43 @@ def _to_snake_case(name: str) -> str:
return s.lower()
-def _build_requirement_attrs(requirement, framework) -> dict:
- """Build a dict with requirement attributes for the unmapped section.
+def _build_requirement_attrs(requirement, framework):
+ """Build the requirement attributes payload for the unmapped section.
- Keys are normalized to snake_case for OCSF consistency.
- Only includes attributes whose AttributeMetadata has output_formats.ocsf=True.
- When no metadata is declared, all attributes are included.
+ Keys are snake_cased and filtered by ``AttributeMetadata.output_formats.ocsf``
+ when declared. MITRE-style attrs (``{"_raw_attributes": [...]}``) are
+ unwrapped into a list of per-entry dicts.
"""
- attrs = requirement.attributes
- if not attrs:
+ requirement_attributes = requirement.attributes
+ if not requirement_attributes:
return {}
- # Build set of keys allowed for OCSF output
metadata = framework.attributes_metadata
- if metadata:
- ocsf_keys = {m.key for m in metadata if m.output_formats.ocsf}
- else:
- ocsf_keys = None # No metadata → include all
+ allowed_keys = (
+ {entry.key for entry in metadata if entry.output_formats.ocsf}
+ if metadata
+ else None
+ )
- result = {}
- for key, value in attrs.items():
- if ocsf_keys is not None and key not in ocsf_keys:
- continue
- result[_to_snake_case(key)] = value
- return result
+ def _to_snake_case_dict(entry: dict) -> dict:
+ return {
+ _to_snake_case(key): value
+ for key, value in entry.items()
+ if allowed_keys is None or key in allowed_keys
+ }
+
+ if (
+ isinstance(requirement_attributes, dict)
+ and "_raw_attributes" in requirement_attributes
+ ):
+ raw_entries = requirement_attributes.get("_raw_attributes") or []
+ return [
+ _to_snake_case_dict(entry)
+ for entry in raw_entries
+ if isinstance(entry, dict)
+ ]
+
+ return _to_snake_case_dict(requirement_attributes)
class OCSFComplianceOutput:
@@ -147,7 +164,14 @@ class OCSFComplianceOutput:
findings: List["Finding"],
framework: ComplianceFramework,
compliance_name: str,
+ include_manual: bool = True,
) -> None:
+ """Transform findings into OCSF ComplianceFinding events.
+
+ Manual requirements are emitted only when ``include_manual=True``. The
+ caller must pass ``False`` for subsequent streaming batches so manual
+ events are not duplicated.
+ """
# Build check -> requirements map
check_req_map = {}
for req in framework.requirements:
@@ -161,15 +185,28 @@ class OCSFComplianceOutput:
for check_id in all_checks:
check_req_map.setdefault(check_id, []).append(req)
+ # Scope constraints to this output's provider (e.g. an Azure constraint
+ # must not affect an AWS output).
+ requirement_config_status = build_requirement_config_status(
+ framework.requirements, provider_type=self._provider
+ )
+
for finding in findings:
if finding.check_id in check_req_map:
for req in check_req_map[finding.check_id]:
cf = self._build_compliance_finding(
- finding, framework, req, compliance_name
+ finding,
+ framework,
+ req,
+ compliance_name,
+ requirement_config_status.get(req.id, (True, "")),
)
if cf:
self._data.append(cf)
+ if not include_manual:
+ return
+
# Manual requirements (no checks or empty for current provider)
for req in framework.requirements:
checks = req.checks
@@ -217,10 +254,14 @@ class OCSFComplianceOutput:
framework: ComplianceFramework,
requirement,
compliance_name: str,
+ config_status: tuple = (True, ""),
) -> ComplianceFinding:
try:
+ effective_status, message = apply_config_status(
+ finding.status, finding.status_extended, config_status
+ )
compliance_status = PROWLER_TO_COMPLIANCE_STATUS.get(
- finding.status, ComplianceStatusID.Unknown
+ effective_status, ComplianceStatusID.Unknown
)
check_status = PROWLER_TO_COMPLIANCE_STATUS.get(
finding.status, ComplianceStatusID.Unknown
@@ -249,6 +290,7 @@ class OCSFComplianceOutput:
requirements=[requirement.id],
control=requirement.description,
status_id=compliance_status,
+ # Nested Check preserves the raw check result.
checks=[
Check(
uid=finding.check_id,
@@ -270,7 +312,7 @@ class OCSFComplianceOutput:
else None
),
),
- message=finding.status_extended,
+ message=message,
metadata=Metadata(
event_code=finding.check_id,
product=Product(
@@ -316,8 +358,10 @@ class OCSFComplianceOutput:
severity=finding_severity.name,
status_id=event_status.value,
status=event_status.name,
- status_code=finding.status,
- status_detail=finding.status_extended,
+ # Effective status, so the top-level never contradicts the
+ # nested compliance status.
+ status_code=effective_status,
+ status_detail=message,
time=time_value,
time_dt=(
finding.timestamp
diff --git a/prowler/lib/outputs/compliance/universal/universal_output.py b/prowler/lib/outputs/compliance/universal/universal_output.py
index 5f99f05755..b1b0d9409b 100644
--- a/prowler/lib/outputs/compliance/universal/universal_output.py
+++ b/prowler/lib/outputs/compliance/universal/universal_output.py
@@ -5,6 +5,10 @@ from typing import TYPE_CHECKING, Optional
from pydantic.v1 import create_model
from prowler.config.config import timestamp
+from prowler.lib.check.compliance_config_eval import (
+ apply_config_status,
+ build_requirement_config_status,
+)
from prowler.lib.check.compliance_models import ComplianceFramework
from prowler.lib.logger import logger
from prowler.lib.utils.utils import open_file
@@ -22,6 +26,7 @@ PROVIDER_HEADER_MAP = {
"oraclecloud": ("TenancyId", "account_uid", "Region", "region"),
"alibabacloud": ("AccountId", "account_uid", "Region", "region"),
"nhn": ("AccountId", "account_uid", "Region", "region"),
+ "e2enetworks": ("ProjectId", "account_uid", "Location", "region"),
}
_DEFAULT_HEADERS = ("AccountId", "account_uid", "Region", "region")
@@ -134,7 +139,9 @@ class UniversalComplianceOutput:
return " | ".join(str(v) for v in value)
return value
- def _build_row(self, finding, framework, requirement, is_manual=False):
+ def _build_row(
+ self, finding, framework, requirement, is_manual=False, config_status=None
+ ):
"""Build a single row dict for a finding + requirement combination."""
row = {
"Provider": (
@@ -180,10 +187,14 @@ class UniversalComplianceOutput:
)
row["Requirements_TechniqueURL"] = requirement.technique_url
- row["Status"] = finding.status if not is_manual else "MANUAL"
- row["StatusExtended"] = (
- finding.status_extended if not is_manual else "Manual check"
- )
+ if is_manual:
+ row["Status"] = "MANUAL"
+ row["StatusExtended"] = "Manual check"
+ else:
+ # Config-invalid PASS reports as FAIL, matching OCSF/table outputs.
+ row["Status"], row["StatusExtended"] = apply_config_status(
+ finding.status, finding.status_extended, config_status
+ )
row["ResourceId"] = finding.resource_uid if not is_manual else "manual_check"
row["ResourceName"] = finding.resource_name if not is_manual else "Manual check"
row["CheckId"] = finding.check_id if not is_manual else "manual"
@@ -198,8 +209,15 @@ class UniversalComplianceOutput:
findings: list["Finding"],
framework: ComplianceFramework,
compliance_name: str,
+ include_manual: bool = True,
) -> None:
- """Transform findings into universal compliance CSV rows."""
+ """Transform findings into universal compliance CSV rows.
+
+ Manual requirements (no checks or empty for current provider) are
+ emitted only when ``include_manual=True``. When the writer is reused
+ across streaming batches, the caller should pass ``False`` after the
+ first batch so manual rows are not duplicated.
+ """
# Build check -> requirements map (filtered by provider for dict checks)
check_req_map = {}
for req in framework.requirements:
@@ -215,6 +233,12 @@ class UniversalComplianceOutput:
check_req_map[check_id] = []
check_req_map[check_id].append(req)
+ # Scope constraints to this output's provider (e.g. an Azure constraint
+ # must not affect an AWS output).
+ requirement_config_status = build_requirement_config_status(
+ framework.requirements, provider_type=self._provider
+ )
+
# Process findings using the provider-filtered check_req_map.
# This ensures that for multi-provider dict checks, only the checks
# belonging to the current provider produce output rows.
@@ -222,12 +246,20 @@ class UniversalComplianceOutput:
check_id = finding.check_id
if check_id in check_req_map:
for req in check_req_map[check_id]:
- row = self._build_row(finding, framework, req)
+ row = self._build_row(
+ finding,
+ framework,
+ req,
+ config_status=requirement_config_status.get(req.id),
+ )
try:
self._data.append(self._row_model(**row))
except Exception as e:
logger.debug(f"Skipping row for {req.id}: {e}")
+ if not include_manual:
+ return
+
# Manual requirements (no checks or empty dict)
for req in framework.requirements:
checks = req.checks
diff --git a/prowler/lib/outputs/compliance/universal/universal_table.py b/prowler/lib/outputs/compliance/universal/universal_table.py
index e838c5e9cf..5f4a6cf88b 100644
--- a/prowler/lib/outputs/compliance/universal/universal_table.py
+++ b/prowler/lib/outputs/compliance/universal/universal_table.py
@@ -2,6 +2,13 @@ from colorama import Fore, Style
from tabulate import tabulate
from prowler.config.config import orange_color
+from prowler.lib.check.compliance_config_eval import (
+ accumulate_group_status,
+ accumulate_overview_status,
+ get_effective_status,
+ get_scan_audit_config,
+ resolve_requirement_config_status,
+)
from prowler.lib.check.compliance_models import ComplianceFramework
@@ -163,9 +170,12 @@ def _render_grouped(
"""Grouped mode: one row per group with pass/fail counts."""
check_map = _build_requirement_check_map(framework, provider)
groups = {}
- pass_count = []
- fail_count = []
- muted_count = []
+ group_seen = {}
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check_id = finding.check_metadata.CheckID
@@ -173,21 +183,24 @@ def _render_grouped(
continue
for req in check_map[check_id]:
+ effective_status = get_effective_status(
+ finding.status,
+ resolve_requirement_config_status(
+ req, audit_config, config_status_cache, provider_type=provider
+ ),
+ )
for group_key in _get_group_key(req, group_by):
if group_key not in groups:
groups[group_key] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ group_seen[group_key] = {}
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- groups[group_key]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- groups[group_key]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- groups[group_key]["PASS"] += 1
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, groups[group_key], group_seen[group_key]
+ )
if not _print_overview(
pass_count, fail_count, muted_count, compliance_framework_name, labels
@@ -258,9 +271,13 @@ def _render_split(
split_field = split_by.field
split_values = split_by.values
groups = {}
- pass_count = []
- fail_count = []
- muted_count = []
+ group_muted_seen = {}
+ group_split_seen = {}
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check_id = finding.check_metadata.CheckID
@@ -268,32 +285,46 @@ def _render_split(
continue
for req in check_map[check_id]:
+ effective_status = get_effective_status(
+ finding.status,
+ resolve_requirement_config_status(
+ req, audit_config, config_status_cache, provider_type=provider
+ ),
+ )
for group_key in _get_group_key(req, group_by):
if group_key not in groups:
groups[group_key] = {
sv: {"FAIL": 0, "PASS": 0} for sv in split_values
}
groups[group_key]["Muted"] = 0
+ group_muted_seen[group_key] = set()
+ group_split_seen[group_key] = {sv: {} for sv in split_values}
split_val = req.attributes.get(split_field, "")
if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
+ # Overview total: count each finding once per framework
+ muted_count.add(index)
+ # Per-group Muted: count each finding once per group it
+ # belongs to (a finding can map to several groups).
+ if index not in group_muted_seen[group_key]:
+ group_muted_seen[group_key].add(index)
groups[group_key]["Muted"] += 1
else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
+ if effective_status == "FAIL":
+ fail_count.add(index)
+ pass_count.discard(index)
+ elif effective_status == "PASS" and index not in fail_count:
+ pass_count.add(index)
for sv in split_values:
if sv in str(split_val):
- if not finding.muted:
- if finding.status == "FAIL":
- groups[group_key][sv]["FAIL"] += 1
- else:
- groups[group_key][sv]["PASS"] += 1
+ accumulate_group_status(
+ index,
+ effective_status,
+ groups[group_key][sv],
+ group_split_seen[group_key][sv],
+ )
if not _print_overview(
pass_count, fail_count, muted_count, compliance_framework_name, labels
@@ -364,16 +395,19 @@ def _render_scored(
risk_field = scoring.risk_field
weight_field = scoring.weight_field
groups = {}
- pass_count = []
- fail_count = []
- muted_count = []
+ group_seen = {}
+ pass_count = set()
+ fail_count = set()
+ muted_count = set()
score_per_group = {}
max_score_per_group = {}
counted_per_group = {}
generic_score = 0
max_generic_score = 0
- counted_generic = []
+ counted_generic = {}
+ audit_config = get_scan_audit_config()
+ config_status_cache = {}
for index, finding in enumerate(findings):
check_id = finding.check_metadata.CheckID
@@ -381,6 +415,12 @@ def _render_scored(
continue
for req in check_map[check_id]:
+ effective_status = get_effective_status(
+ finding.status,
+ resolve_requirement_config_status(
+ req, audit_config, config_status_cache, provider_type=provider
+ ),
+ )
for group_key in _get_group_key(req, group_by):
attrs = req.attributes
risk = attrs.get(risk_field, 0)
@@ -388,33 +428,47 @@ def _render_scored(
if group_key not in groups:
groups[group_key] = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ group_seen[group_key] = {}
score_per_group[group_key] = 0
max_score_per_group[group_key] = 0
- counted_per_group[group_key] = []
+ counted_per_group[group_key] = {}
- if index not in counted_per_group[group_key] and not finding.muted:
- if finding.status == "PASS":
- score_per_group[group_key] += risk * weight
- max_score_per_group[group_key] += risk * weight
- counted_per_group[group_key].append(index)
+ # Revoke an earlier PASS score if a later requirement FAILs.
+ if not finding.muted:
+ contribution = risk * weight
+ counted = counted_per_group[group_key]
+ if index not in counted:
+ max_score_per_group[group_key] += contribution
+ if effective_status == "PASS":
+ score_per_group[group_key] += contribution
+ counted[index] = contribution
+ else:
+ counted[index] = 0
+ elif effective_status == "FAIL" and counted[index]:
+ score_per_group[group_key] -= counted[index]
+ counted[index] = 0
- if finding.muted:
- if index not in muted_count:
- muted_count.append(index)
- groups[group_key]["Muted"] += 1
- else:
- if finding.status == "FAIL" and index not in fail_count:
- fail_count.append(index)
- groups[group_key]["FAIL"] += 1
- elif finding.status == "PASS" and index not in pass_count:
- pass_count.append(index)
- groups[group_key]["PASS"] += 1
+ status = "Muted" if finding.muted else effective_status
+ accumulate_overview_status(
+ index, status, pass_count, fail_count, muted_count
+ )
+ accumulate_group_status(
+ index, status, groups[group_key], group_seen[group_key]
+ )
- if index not in counted_generic and not finding.muted:
- if finding.status == "PASS":
- generic_score += risk * weight
- max_generic_score += risk * weight
- counted_generic.append(index)
+ # Generic score, with the same PASS-revocation on FAIL.
+ if not finding.muted:
+ contribution = risk * weight
+ if index not in counted_generic:
+ max_generic_score += contribution
+ if effective_status == "PASS":
+ generic_score += contribution
+ counted_generic[index] = contribution
+ else:
+ counted_generic[index] = 0
+ elif effective_status == "FAIL" and counted_generic[index]:
+ generic_score -= counted_generic[index]
+ counted_generic[index] = 0
if not _print_overview(
pass_count, fail_count, muted_count, compliance_framework_name, labels
diff --git a/prowler/lib/outputs/finding.py b/prowler/lib/outputs/finding.py
index 8ca01bc9c5..7231572571 100644
--- a/prowler/lib/outputs/finding.py
+++ b/prowler/lib/outputs/finding.py
@@ -342,6 +342,32 @@ class Finding(BaseModel):
output_data["resource_uid"] = check_output.resource_id
output_data["region"] = check_output.location
+ elif provider.type == "e2enetworks":
+ output_data["auth_method"] = "api_key_and_bearer_token"
+ output_data["account_uid"] = str(
+ get_nested_attribute(provider, "identity.project_id")
+ )
+ output_data["account_name"] = str(
+ get_nested_attribute(provider, "identity.project_id")
+ )
+ output_data["resource_name"] = check_output.resource_name
+ output_data["resource_uid"] = check_output.resource_id
+ output_data["region"] = check_output.location
+
+ elif provider.type == "stackit":
+ output_data["auth_method"] = getattr(
+ provider, "auth_method", "api_token"
+ )
+ output_data["account_uid"] = get_nested_attribute(
+ provider, "identity.project_id"
+ )
+ output_data["account_name"] = get_nested_attribute(
+ provider, "identity.project_name"
+ )
+ output_data["resource_name"] = check_output.resource_name
+ output_data["resource_uid"] = check_output.resource_id
+ output_data["region"] = check_output.location
+
elif provider.type == "iac":
output_data["auth_method"] = provider.auth_method
provider_uid = getattr(provider, "provider_uid", None)
@@ -454,6 +480,24 @@ class Finding(BaseModel):
output_data["resource_uid"] = check_output.resource_id
output_data["region"] = check_output.region
+ elif provider.type == "linode":
+ output_data["auth_method"] = "api_token"
+ # account_uid is a required string, but the account ID may be
+ # unavailable when the token lacks account:read_only scope. Fall
+ # back to the username/email so findings are never dropped.
+ output_data["account_uid"] = (
+ get_nested_attribute(provider, "identity.account_id")
+ or get_nested_attribute(provider, "identity.username")
+ or get_nested_attribute(provider, "identity.email")
+ or "linode"
+ )
+ output_data["account_name"] = get_nested_attribute(
+ provider, "identity.username"
+ ) or get_nested_attribute(provider, "identity.email")
+ output_data["resource_name"] = check_output.resource_name
+ output_data["resource_uid"] = check_output.resource_id
+ output_data["region"] = check_output.region
+
elif provider.type == "alibabacloud":
output_data["auth_method"] = get_nested_attribute(
provider, "identity.identity_arn"
@@ -503,6 +547,11 @@ class Finding(BaseModel):
check_output, "fixed_version", ""
)
+ else:
+ # Dynamic fallback: any external/custom provider
+ provider_data = provider.get_finding_output_data(check_output)
+ output_data.update(provider_data)
+
# check_output Unique ID
# TODO: move this to a function
# TODO: in Azure, GCP and K8s there are findings without resource_name
@@ -576,6 +625,8 @@ class Finding(BaseModel):
finding.subscription = list(provider.identity.subscriptions.keys())[0]
elif provider.type == "gcp":
finding.project_id = list(provider.projects.keys())[0]
+ elif provider.type == "stackit":
+ finding.project_id = provider.identity.project_id
elif provider.type == "iac":
# For IaC, we don't have resource_line_range in the Finding model
# It would need to be extracted from the resource metadata if needed
diff --git a/prowler/lib/outputs/html/html.py b/prowler/lib/outputs/html/html.py
index 8685d711ce..3463014232 100644
--- a/prowler/lib/outputs/html/html.py
+++ b/prowler/lib/outputs/html/html.py
@@ -2,6 +2,7 @@ import sys
from io import TextIOWrapper
import markdown
+from markupsafe import escape
from prowler.config.config import (
html_logo_url,
@@ -73,8 +74,7 @@ class HTML(Output):
elif finding.status == "FAIL":
row_class = "table-danger"
- self._data.append(
- f"""
+ self._data.append(f"""
<tr class="{row_class}">
<td>{finding_status}</td>
<td>{finding.metadata.Severity.value}</td>
@@ -89,8 +89,7 @@ class HTML(Output):
<td><p class="show-read-more">{HTML.process_markdown(finding.metadata.Remediation.Recommendation.Text)}</p> <a class="read-more" href="{finding.metadata.Remediation.Recommendation.Url}"><i class="fas fa-external-link-alt"></i></a></td>
<td><p class="show-read-more">{parse_html_string(unroll_dict(finding.compliance, separator=": "))}</p></td>
</tr>
- """
- )
+ """)
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
@@ -143,8 +142,7 @@ class HTML(Output):
from_cli (bool): whether the request is from the CLI or not
"""
try:
- file_descriptor.write(
- f"""<!DOCTYPE html>
+ file_descriptor.write(f"""<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -253,8 +251,7 @@ class HTML(Output):
<th scope="col">Compliance</th>
</tr>
</thead>
- <tbody>"""
- )
+ <tbody>""")
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
@@ -269,8 +266,7 @@ class HTML(Output):
file_descriptor (file): the file descriptor to write the footer
"""
try:
- file_descriptor.write(
- """
+ file_descriptor.write("""
</tbody>
</table>
</div>
@@ -409,8 +405,7 @@ class HTML(Output):
</body>
</html>
-"""
- )
+""")
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
@@ -1076,6 +1071,73 @@ class HTML(Output):
)
return ""
+ @staticmethod
+ def get_stackit_assessment_summary(provider: Provider) -> str:
+ """
+ get_stackit_assessment_summary gets the HTML assessment summary for the StackIT provider
+
+ Args:
+ provider (Provider): the StackIT provider object
+
+ Returns:
+ str: HTML assessment summary for the StackIT provider
+ """
+ try:
+ project_id = getattr(provider.identity, "project_id", "unknown")
+ project_name = getattr(provider.identity, "project_name", "")
+ audited_regions = getattr(provider.identity, "audited_regions", set())
+
+ project_name_item = (
+ f"""
+ <li class="list-group-item">
+ <b>Project Name:</b> {project_name}
+ </li>"""
+ if project_name
+ else ""
+ )
+
+ regions_item = (
+ f"""
+ <li class="list-group-item">
+ <b>Regions:</b> {", ".join(sorted(audited_regions))}
+ </li>"""
+ if audited_regions
+ else ""
+ )
+
+ return f"""
+ <div class="col-md-2">
+ <div class="card">
+ <div class="card-header">
+ StackIT Assessment Summary
+ </div>
+ <ul class="list-group list-group-flush">
+ <li class="list-group-item">
+ <b>Project ID:</b> {project_id}
+ </li>
+ {project_name_item}
+ {regions_item}
+ </ul>
+ </div>
+ </div>
+ <div class="col-md-4">
+ <div class="card">
+ <div class="card-header">
+ StackIT Credentials
+ </div>
+ <ul class="list-group list-group-flush">
+ <li class="list-group-item">
+ <b>Authentication Type:</b> Service Account Key
+ </li>
+ </ul>
+ </div>
+ </div>"""
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ return ""
+
@staticmethod
def get_cloudflare_assessment_summary(provider: Provider) -> str:
"""
@@ -1335,6 +1397,46 @@ class HTML(Output):
)
return ""
+ @staticmethod
+ def get_e2enetworks_assessment_summary(provider: Provider) -> str:
+ """Get the HTML assessment summary for the E2E Networks provider."""
+ try:
+ locations = escape(", ".join(provider.identity.locations))
+ project_id = escape(str(provider.identity.project_id))
+ return f"""
+ <div class="col-md-2">
+ <div class="card">
+ <div class="card-header">
+ E2E Networks Assessment Summary
+ </div>
+ <ul class="list-group list-group-flush">
+ <li class="list-group-item">
+ <b>Project ID:</b> {project_id}
+ </li>
+ <li class="list-group-item">
+ <b>Locations:</b> {locations}
+ </li>
+ </ul>
+ </div>
+ </div>
+ <div class="col-md-4">
+ <div class="card">
+ <div class="card-header">
+ E2E Networks Credentials
+ </div>
+ <ul class="list-group list-group-flush">
+ <li class="list-group-item">
+ <b>Authentication:</b> API Key + Bearer Token
+ </li>
+ </ul>
+ </div>
+ </div>"""
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ return ""
+
@staticmethod
def get_vercel_assessment_summary(provider: Provider) -> str:
"""
@@ -1521,6 +1623,63 @@ class HTML(Output):
)
return ""
+ @staticmethod
+ def get_linode_assessment_summary(provider: Provider) -> str:
+ """
+ get_linode_assessment_summary gets the HTML assessment summary for the Linode provider
+
+ Args:
+ provider (Provider): the Linode provider object
+
+ Returns:
+ str: HTML assessment summary for the Linode provider
+ """
+ try:
+ username = getattr(provider.identity, "username", None) or "-"
+ email = getattr(provider.identity, "email", None) or "-"
+ account_id = getattr(provider.identity, "account_id", None) or "-"
+
+ assessment_items = f"""
+ <li class="list-group-item">
+ <b>Account ID:</b> {account_id}
+ </li>
+ <li class="list-group-item">
+ <b>Username:</b> {username}
+ </li>
+ <li class="list-group-item">
+ <b>Email:</b> {email}
+ </li>"""
+
+ credentials_items = """
+ <li class="list-group-item">
+ <b>Authentication:</b> API Token
+ </li>"""
+
+ return f"""
+ <div class="col-md-2">
+ <div class="card">
+ <div class="card-header">
+ Linode Assessment Summary
+ </div>
+ <ul class="list-group list-group-flush">{assessment_items}
+ </ul>
+ </div>
+ </div>
+ <div class="col-md-4">
+ <div class="card">
+ <div class="card-header">
+ Linode Credentials
+ </div>
+ <ul class="list-group list-group-flush">{credentials_items}
+ </ul>
+ </div>
+ </div>"""
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ return ""
+
@staticmethod
def get_assessment_summary(provider: Provider) -> str:
"""
@@ -1541,11 +1700,13 @@ class HTML(Output):
# Azure_provider --> azure
# Kubernetes_provider --> kubernetes
- # Dynamically get the Provider quick inventory handler
- provider_html_assessment_summary_function = (
- f"get_{provider.type}_assessment_summary"
- )
- return getattr(HTML, provider_html_assessment_summary_function)(provider)
+ # Try static method first, fall back to provider method
+ method_name = f"get_{provider.type}_assessment_summary"
+ if hasattr(HTML, method_name):
+ return getattr(HTML, method_name)(provider)
+ else:
+ # Dynamic fallback: any external/custom provider
+ return provider.get_html_assessment_summary()
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
diff --git a/prowler/lib/outputs/jira/jira.py b/prowler/lib/outputs/jira/jira.py
index ed8f7faab0..601120cdfc 100644
--- a/prowler/lib/outputs/jira/jira.py
+++ b/prowler/lib/outputs/jira/jira.py
@@ -1,5 +1,6 @@
import base64
import os
+import re
from dataclasses import dataclass
from datetime import datetime, timedelta
from typing import Dict, List, Optional
@@ -37,6 +38,10 @@ from prowler.lib.outputs.jira.exceptions.exceptions import (
)
from prowler.providers.common.models import Connection
+ATLASSIAN_SITE_NAME_REGEX = re.compile(
+ r"\A[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?\Z"
+)
+
@dataclass
class JiraConnection(Connection):
@@ -51,6 +56,39 @@ class JiraConnection(Connection):
issue_types: dict = None
+def _format_jira_issue_creation_error(response_json: object, status_code: int) -> str:
+ """Build a safe Jira issue creation error message from structured fields.
+
+ Args:
+ response_json: Parsed Jira response body.
+ status_code: HTTP status code returned by Jira.
+
+ Returns:
+ Safe issue creation error message for user-facing propagation.
+ """
+ message_parts = []
+
+ if not isinstance(response_json, dict):
+ return f"Failed to create Jira issue: Jira returned status code {status_code}."
+
+ errors = response_json.get("errors")
+ if isinstance(errors, dict):
+ message_parts.extend(
+ f"'{field}': '{message}'" for field, message in errors.items() if message
+ )
+
+ error_messages = response_json.get("errorMessages")
+ if isinstance(error_messages, list):
+ message_parts.extend(str(message) for message in error_messages if message)
+ elif isinstance(error_messages, str) and error_messages:
+ message_parts.append(error_messages)
+
+ if message_parts:
+ return f"Failed to create Jira issue: {'; '.join(message_parts)}"
+
+ return f"Failed to create Jira issue: Jira returned status code {status_code}."
+
+
class MarkdownToADFConverter:
"""Helper to convert Markdown strings into Atlassian Document Format blocks."""
@@ -229,7 +267,9 @@ class MarkdownToADFConverter:
return node
def _paragraph_with_text(self, text: str) -> Dict:
- return {"type": "paragraph", "content": [self._create_text_node(text, None)]}
+ # ADF forbids empty text nodes; emit an empty paragraph instead.
+ content = [self._create_text_node(text, None)] if text else []
+ return {"type": "paragraph", "content": content}
@staticmethod
def _pop_mark(marks_stack: List[Dict], mark_type: str) -> None:
@@ -339,6 +379,7 @@ class Jira:
}
TOKEN_URL = "https://auth.atlassian.com/oauth/token"
API_TOKEN_URL = "https://api.atlassian.com/oauth/token/accessible-resources"
+ REQUEST_TIMEOUT = 90
HEADER_TEMPLATE = {
"Content-Type": "application/json",
"X-Force-Accept-Language": "true",
@@ -376,6 +417,19 @@ class Jira:
message=init_error, file=os.path.basename(__file__)
)
+ @staticmethod
+ def _sanitize_summary(summary: str) -> str:
+ """Normalize and truncate a Jira issue summary.
+
+ Args:
+ summary: Raw summary text.
+
+ Returns:
+ The summary collapsed to one line and limited to Jira's 255-character
+ summary maximum.
+ """
+ return " ".join(summary.split())[:255]
+
@staticmethod
def _build_code_block_content(code_value: str) -> Optional[Dict]:
if not code_value:
@@ -576,7 +630,12 @@ class Jira:
}
headers = self.get_headers(content_type_json=True)
- response = requests.post(self.TOKEN_URL, json=body, headers=headers)
+ response = requests.post(
+ self.TOKEN_URL,
+ json=body,
+ headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
+ )
if response.status_code == 200:
tokens = response.json()
@@ -624,16 +683,24 @@ class Jira:
"""
try:
if self._using_basic_auth:
+ if not domain or not ATLASSIAN_SITE_NAME_REGEX.fullmatch(domain):
+ raise ValueError("Invalid Jira site name.")
headers = self.get_headers(access_token)
response = requests.get(
f"https://{domain}.atlassian.net/_edge/tenant_info",
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
+ allow_redirects=False,
)
response = response.json()
return response.get("cloudId")
else:
headers = self.get_headers(access_token)
- response = requests.get(self.API_TOKEN_URL, headers=headers)
+ response = requests.get(
+ self.API_TOKEN_URL,
+ headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
+ )
if response.status_code == 200:
resources = response.json()
@@ -715,7 +782,12 @@ class Jira:
}
headers = self.get_headers(content_type_json=True)
- response = requests.post(url, json=body, headers=headers)
+ response = requests.post(
+ url,
+ json=body,
+ headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
+ )
if response.status_code == 200:
tokens = response.json()
@@ -872,6 +944,7 @@ class Jira:
response = requests.get(
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/project",
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if response.status_code == 200:
@@ -939,6 +1012,7 @@ class Jira:
response = requests.get(
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/issue/createmeta?projectKeys={project_key}&expand=projects.issuetypes.fields",
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if response.status_code == 200:
@@ -984,6 +1058,7 @@ class Jira:
response = requests.get(
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/project",
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if response.status_code == 200:
projects_data = {}
@@ -999,6 +1074,7 @@ class Jira:
project_response = requests.get(
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/issue/createmeta?projectKeys={project['key']}&expand=projects.issuetypes.fields",
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if project_response.status_code == 200:
project_metadata = project_response.json()
@@ -1092,6 +1168,101 @@ class Jira:
return "#0000FF"
return "#000000" # Default black color for unknown severities
+ @staticmethod
+ def _adf_colored_strong_marks(color_mark_type: str, color: str) -> list[dict]:
+ """Build ADF marks for bold text with a Jira color mark.
+
+ Args:
+ color_mark_type: Jira ADF color mark type, such as textColor or
+ backgroundColor.
+ color: Hex color value for the mark.
+
+ Returns:
+ ADF marks for strong colored text.
+ """
+ return [
+ {"type": "strong"},
+ {"type": color_mark_type, "attrs": {"color": color}},
+ ]
+
+ def _adf_severity_marks(
+ self, severity: str = "", severity_color: str | None = None
+ ) -> list[dict]:
+ """Build ADF marks for severity text.
+
+ Args:
+ severity: Finding severity used to derive a color when severity_color
+ is not provided.
+ severity_color: Optional explicit severity color.
+
+ Returns:
+ ADF marks for highlighted severity text.
+ """
+ color = severity_color or self.get_severity_color(str(severity).lower())
+ return self._adf_colored_strong_marks("backgroundColor", color)
+
+ def _adf_status_marks(
+ self, status: str = "", status_color: str | None = None
+ ) -> list[dict]:
+ """Build ADF marks for status text.
+
+ Args:
+ status: Finding status used to derive a color when status_color is
+ not provided.
+ status_color: Optional explicit status color.
+
+ Returns:
+ ADF marks for colored status text.
+ """
+ color = status_color or self.get_color_from_status(str(status).upper())
+ return self._adf_colored_strong_marks("textColor", color)
+
+ @staticmethod
+ def _adf_text_node(text: str, marks: list[dict] | None = None) -> dict:
+ """Build an ADF text node.
+
+ Args:
+ text: Text content for the node.
+ marks: Optional ADF marks to apply to the text.
+
+ Returns:
+ ADF text node with optional marks.
+ """
+ node = {"type": "text", "text": text}
+ if marks:
+ node["marks"] = marks
+ return node
+
+ def _adf_severity_text_node(
+ self, severity: str = "", severity_color: str | None = None
+ ) -> dict:
+ """Build an ADF text node for severity.
+
+ Args:
+ severity: Severity text to render.
+ severity_color: Optional explicit severity color.
+
+ Returns:
+ ADF text node with severity marks.
+ """
+ return self._adf_text_node(
+ severity, self._adf_severity_marks(severity, severity_color)
+ )
+
+ def _adf_status_text_node(
+ self, status: str = "", status_color: str | None = None
+ ) -> dict:
+ """Build an ADF text node for status.
+
+ Args:
+ status: Status text to render.
+ status_color: Optional explicit status color.
+
+ Returns:
+ ADF text node with status marks.
+ """
+ return self._adf_text_node(status, self._adf_status_marks(status, status_color))
+
def get_adf_description(
self,
check_id: str = "",
@@ -1118,6 +1289,18 @@ class Jira:
tenant_info: str = "",
) -> dict:
+ # ADF forbids empty text nodes, so Jira rejects them with 400 INVALID_INPUT.
+ def _safe(value: str) -> str:
+ return value if (value and value.strip()) else "-"
+
+ check_id = _safe(check_id)
+ check_title = _safe(check_title)
+ status_extended = _safe(status_extended)
+ provider = _safe(provider)
+ region = _safe(region)
+ resource_uid = _safe(resource_uid)
+ resource_name = _safe(resource_name)
+
table_rows = [
{
"type": "tableRow",
@@ -1218,19 +1401,9 @@ class Jira:
{
"type": "paragraph",
"content": [
- {
- "type": "text",
- "text": severity,
- "marks": [
- {"type": "strong"},
- {
- "type": "backgroundColor",
- "attrs": {
- "color": severity_color,
- },
- },
- ],
- }
+ self._adf_severity_text_node(
+ severity, severity_color
+ )
],
}
],
@@ -1263,17 +1436,7 @@ class Jira:
{
"type": "paragraph",
"content": [
- {
- "type": "text",
- "text": status,
- "marks": [
- {"type": "strong"},
- {
- "type": "textColor",
- "attrs": {"color": status_color},
- },
- ],
- }
+ self._adf_status_text_node(status, status_color)
],
}
],
@@ -1797,6 +1960,239 @@ class Jira:
],
}
+ def get_grouped_adf_description(
+ self,
+ check_id: str = "",
+ check_title: str = "",
+ check_description: str = "",
+ severity: str = "",
+ status: str = "",
+ provider: str = "",
+ service: str = "",
+ affected_failing_resources: int = 0,
+ last_seen: str = "",
+ failing_for: str = "",
+ grouped_resources: list[dict] | None = None,
+ resources_total: int = 0,
+ resources_shown: int = 0,
+ finding_group_url: str = "",
+ finding_group_link_text: str = "",
+ risk: str = "",
+ recommendation_text: str = "",
+ recommendation_url: str = "",
+ ) -> dict:
+ """Build a Jira ADF description for a grouped finding issue.
+
+ Args:
+ check_id: Finding check ID.
+ check_title: Finding check title.
+ check_description: Finding check description.
+ severity: Finding group severity.
+ status: Finding group status.
+ provider: Cloud provider name.
+ service: Provider service name.
+ affected_failing_resources: Number of failing resources in the group.
+ last_seen: Last time the finding group was seen.
+ failing_for: Duration the finding group has been failing.
+ grouped_resources: Resource rows to include in the grouped issue.
+ resources_total: Total number of resources in the group.
+ resources_shown: Number of resources rendered in this Jira issue.
+ finding_group_url: Optional URL for the full finding group.
+ finding_group_link_text: Optional link text for finding_group_url.
+ risk: Risk description for the check.
+ recommendation_text: Remediation recommendation text.
+ recommendation_url: Optional remediation recommendation URL.
+
+ Returns:
+ Jira ADF document describing the finding group.
+ """
+
+ def _safe(value) -> str:
+ return str(value) if value not in (None, "") else "-"
+
+ def _text(value, marks: list[dict] | None = None) -> dict:
+ node = {"type": "text", "text": _safe(value)}
+ if marks:
+ node["marks"] = marks
+ return node
+
+ def _paragraph(value, marks: list[dict] | None = None) -> dict:
+ return {"type": "paragraph", "content": [_text(value, marks)]}
+
+ def _cell(value, marks: list[dict] | None = None) -> dict:
+ return {"type": "tableCell", "content": [_paragraph(value, marks)]}
+
+ def _content_cell(content: list[dict]) -> dict:
+ return {"type": "tableCell", "content": content}
+
+ def _append_link(content: list[dict], url: str) -> list[dict]:
+ if not url:
+ return content
+
+ link_node = {
+ "type": "text",
+ "text": url,
+ "marks": [{"type": "link", "attrs": {"href": url}}],
+ }
+ if content and content[-1].get("type") == "paragraph":
+ paragraph_content = content[-1].setdefault("content", [])
+ if paragraph_content:
+ last_inline = paragraph_content[-1]
+ if last_inline.get("type") != "text" or not last_inline.get(
+ "text", ""
+ ).endswith(" "):
+ paragraph_content.append({"type": "text", "text": " "})
+ paragraph_content.append(link_node)
+ else:
+ content.append({"type": "paragraph", "content": [link_node]})
+ return content
+
+ def _row(cells: list[dict]) -> dict:
+ return {"type": "tableRow", "content": cells}
+
+ strong = [{"type": "strong"}]
+ code = [{"type": "code"}]
+ severity_marks = self._adf_severity_marks(severity)
+ status_marks = self._adf_status_marks(status)
+ recommendation_content = _append_link(
+ self._markdown_converter.convert(_safe(recommendation_text)),
+ recommendation_url,
+ )
+ main_rows = [
+ _row([_cell("Check Id", strong), _cell(check_id, code)]),
+ _row([_cell("Check Title", strong), _cell(check_title)]),
+ _row([_cell("Severity", strong), _cell(severity, severity_marks)]),
+ _row([_cell("Status", strong), _cell(status, status_marks)]),
+ _row([_cell("Provider", strong), _cell(provider, code)]),
+ _row([_cell("Service", strong), _cell(service, code)]),
+ _row(
+ [
+ _cell("Affected Failing Resources", strong),
+ _cell(affected_failing_resources, strong),
+ ]
+ ),
+ _row([_cell("Last Seen", strong), _cell(last_seen)]),
+ _row([_cell("Failing For", strong), _cell(failing_for)]),
+ _row(
+ [
+ _cell("Risk", strong),
+ _content_cell(self._markdown_converter.convert(_safe(risk))),
+ ]
+ ),
+ _row(
+ [
+ _cell("Recommendation", strong),
+ _content_cell(recommendation_content),
+ ]
+ ),
+ ]
+
+ resource_rows = [
+ _row(
+ [
+ _cell("Resource", strong),
+ _cell("Resource UID", strong),
+ _cell("Provider", strong),
+ _cell("Service", strong),
+ _cell("Account / Tenant", strong),
+ _cell("Status", strong),
+ _cell("Severity", strong),
+ _cell("Region", strong),
+ _cell("Last Seen", strong),
+ _cell("Failing For", strong),
+ _cell("Triage", strong),
+ ]
+ )
+ ]
+ for resource in grouped_resources or []:
+ resource_status = resource.get("status")
+ resource_severity = str(resource.get("severity", "")).upper()
+ resource_status_marks = self._adf_status_marks(resource_status)
+ resource_severity_marks = self._adf_severity_marks(resource_severity)
+ resource_rows.append(
+ _row(
+ [
+ _cell(resource.get("resource_name"), code),
+ _cell(resource.get("resource_uid"), code),
+ _cell(resource.get("provider"), code),
+ _cell(resource.get("service"), code),
+ _cell(resource.get("provider_account"), code),
+ _cell(resource_status, resource_status_marks),
+ _cell(resource_severity, resource_severity_marks),
+ _cell(resource.get("region"), code),
+ _cell(resource.get("last_seen")),
+ _cell(resource.get("failing_for")),
+ _cell(resource.get("triage")),
+ ]
+ )
+ )
+
+ content = [
+ _paragraph("Prowler has discovered the following Finding Group:"),
+ {"type": "table", "attrs": {"layout": "full-width"}, "content": main_rows},
+ ]
+
+ content.extend(
+ [
+ {
+ "type": "heading",
+ "attrs": {"level": 2},
+ "content": [_text("Affected failing resources")],
+ },
+ {
+ "type": "table",
+ "attrs": {"layout": "full-width"},
+ "content": resource_rows,
+ },
+ ]
+ )
+
+ if resources_total > resources_shown:
+ remaining_content = [
+ _text(f"Showing {resources_shown} of {resources_total} Findings.")
+ ]
+ if finding_group_url and finding_group_link_text:
+ remaining_content = [
+ _text(
+ f"Showing {resources_shown} of {resources_total} Findings "
+ "in this Jira issue. "
+ ),
+ _text(
+ finding_group_link_text,
+ [
+ {
+ "type": "link",
+ "attrs": {"href": finding_group_url},
+ }
+ ],
+ ),
+ ]
+ content.append(
+ {
+ "type": "paragraph",
+ "content": remaining_content,
+ }
+ )
+ elif finding_group_url and finding_group_link_text:
+ content.append(
+ {
+ "type": "paragraph",
+ "content": [
+ _text(
+ finding_group_link_text,
+ [
+ {
+ "type": "link",
+ "attrs": {"href": finding_group_url},
+ }
+ ],
+ ),
+ ],
+ }
+ )
+
+ return {"type": "doc", "version": 1, "content": content}
+
def send_findings(
self,
findings: list[Finding] = None,
@@ -1890,7 +2286,7 @@ class Jira:
summary_parts.append(finding.resource_uid)
summary = " - ".join(summary_parts[1:])
- summary = f"{summary_parts[0]} {summary}"[:255]
+ summary = self._sanitize_summary(f"{summary_parts[0]} {summary}")
payload = {
"fields": {
@@ -1909,6 +2305,7 @@ class Jira:
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/issue",
json=payload,
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if response.status_code != 201:
@@ -1972,11 +2369,13 @@ class Jira:
self,
check_id: str = "",
check_title: str = "",
+ check_description: str = "",
severity: str = "",
status: str = "",
status_extended: str = "",
provider: str = "",
region: str = "",
+ service: str = "",
resource_uid: str = "",
resource_name: str = "",
risk: str = "",
@@ -1993,6 +2392,14 @@ class Jira:
issue_labels: list[str] = "",
finding_url: str = "",
tenant_info: str = "",
+ affected_failing_resources: int = 0,
+ grouped_resources: list[dict] | None = None,
+ resources_total: int = 0,
+ resources_shown: int = 0,
+ last_seen: str = "",
+ failing_for: str = "",
+ finding_group_url: str = "",
+ finding_group_link_text: str = "",
) -> bool:
"""
Send the finding to Jira
@@ -2000,11 +2407,13 @@ class Jira:
Args:
- check_id: The check ID
- check_title: The check title
+ - check_description: The check description
- severity: The severity
- status: The status
- status_extended: The status extended
- provider: The provider
- region: The region
+ - service: The service
- resource_uid: The resource UID
- resource_name: The resource name
- risk: The risk
@@ -2021,10 +2430,20 @@ class Jira:
- issue_labels: The issue labels
- finding_url: The finding URL
- tenant_info: The tenant info
+ - affected_failing_resources: The number of affected failing resources
+ - grouped_resources: The grouped resources to render, or None for a
+ single finding issue
+ - resources_total: The total resources in the finding group
+ - resources_shown: The resources shown in the Jira issue
+ - last_seen: The last time the finding group was seen
+ - failing_for: The duration the finding group has been failing
+ - finding_group_url: The finding group URL
+ - finding_group_link_text: The link text for the finding group URL
Raises:
- JiraRefreshTokenError: Failed to refresh the access token
- JiraRefreshTokenResponseError: Failed to refresh the access token, response code did not match 200
+ - JiraNoTokenError: Failed to get an access token
- JiraCreateIssueError: Failed to create an issue in Jira
- JiraSendFindingsResponseError: Failed to send the finding to Jira
- JiraRequiredCustomFieldsError: Jira project requires custom fields that are not supported
@@ -2063,40 +2482,66 @@ class Jira:
status_color = self.get_color_from_status(status)
severity_color = self.get_severity_color(severity.lower())
- adf_description = self.get_adf_description(
- check_id=check_id,
- check_title=check_title,
- severity=severity.upper(),
- severity_color=severity_color,
- status=status,
- status_color=status_color,
- status_extended=status_extended,
- provider=provider,
- region=region,
- resource_uid=resource_uid,
- resource_name=resource_name,
- risk=risk,
- recommendation_text=recommendation_text,
- recommendation_url=recommendation_url,
- remediation_code_native_iac=remediation_code_native_iac,
- remediation_code_terraform=remediation_code_terraform,
- remediation_code_cli=remediation_code_cli,
- remediation_code_other=remediation_code_other,
- resource_tags=resource_tags,
- compliance=compliance,
- finding_url=finding_url,
- tenant_info=tenant_info,
- )
+ if grouped_resources is not None:
+ adf_description = self.get_grouped_adf_description(
+ check_id=check_id,
+ check_title=check_title,
+ check_description=check_description,
+ severity=severity.upper(),
+ status=status,
+ provider=provider,
+ service=service,
+ affected_failing_resources=affected_failing_resources,
+ last_seen=last_seen,
+ failing_for=failing_for,
+ grouped_resources=grouped_resources,
+ resources_total=resources_total,
+ resources_shown=resources_shown,
+ finding_group_url=finding_group_url,
+ finding_group_link_text=finding_group_link_text,
+ risk=risk,
+ recommendation_text=recommendation_text,
+ recommendation_url=recommendation_url,
+ )
+ else:
+ adf_description = self.get_adf_description(
+ check_id=check_id,
+ check_title=check_title,
+ severity=severity.upper(),
+ severity_color=severity_color,
+ status=status,
+ status_color=status_color,
+ status_extended=status_extended,
+ provider=provider,
+ region=region,
+ resource_uid=resource_uid,
+ resource_name=resource_name,
+ risk=risk,
+ recommendation_text=recommendation_text,
+ recommendation_url=recommendation_url,
+ remediation_code_native_iac=remediation_code_native_iac,
+ remediation_code_terraform=remediation_code_terraform,
+ remediation_code_cli=remediation_code_cli,
+ remediation_code_other=remediation_code_other,
+ resource_tags=resource_tags,
+ compliance=compliance,
+ finding_url=finding_url,
+ tenant_info=tenant_info,
+ )
summary_parts = ["[Prowler]"]
if severity:
summary_parts.append(severity.upper())
if check_id:
summary_parts.append(check_id)
- if resource_uid:
+ if grouped_resources is not None:
+ summary_parts.append(
+ f"{affected_failing_resources} affected failing resources"
+ )
+ elif resource_uid:
summary_parts.append(resource_uid)
summary = " - ".join(summary_parts[1:])
- summary = f"{summary_parts[0]} {summary}"[:255]
+ summary = self._sanitize_summary(f"{summary_parts[0]} {summary}")
payload = {
"fields": {
@@ -2113,37 +2558,52 @@ class Jira:
f"https://api.atlassian.com/ex/jira/{self.cloud_id}/rest/api/3/issue",
json=payload,
headers=headers,
+ timeout=self.REQUEST_TIMEOUT,
)
if response.status_code != 201:
try:
response_json = response.json()
except (ValueError, requests.exceptions.JSONDecodeError):
- response_error = f"Failed to send finding: {response.status_code} - {response.text}"
+ response_error = _format_jira_issue_creation_error(
+ {}, response.status_code
+ )
logger.error(response_error)
- return False
+ raise JiraSendFindingsResponseError(
+ message=response_error, file=os.path.basename(__file__)
+ )
# Check if the error is due to required custom fields
- if response.status_code == 400 and "errors" in response_json:
+ if (
+ response.status_code == 400
+ and isinstance(response_json, dict)
+ and "errors" in response_json
+ ):
errors = response_json.get("errors", {})
# Look for custom field errors (fields starting with "customfield_")
- custom_field_errors = {
- k: v for k, v in errors.items() if k.startswith("customfield_")
- }
+ custom_field_errors = {}
+ if isinstance(errors, dict):
+ custom_field_errors = {
+ k: v
+ for k, v in errors.items()
+ if k.startswith("customfield_")
+ }
if custom_field_errors:
custom_fields_formatted = ", ".join(
[f"'{k}': '{v}'" for k, v in custom_field_errors.items()]
)
- logger.error(
- f"Jira project requires custom fields that are not supported: {custom_fields_formatted}"
+ raise JiraRequiredCustomFieldsError(
+ message=f"Jira project requires custom fields that are not supported: {custom_fields_formatted}",
+ file=os.path.basename(__file__),
)
- return False
- response_error = (
- f"Failed to send finding: {response.status_code} - {response_json}"
+ response_error = _format_jira_issue_creation_error(
+ response_json, response.status_code
)
logger.error(response_error)
- return False
+ raise JiraSendFindingsResponseError(
+ message=response_error, file=os.path.basename(__file__)
+ )
else:
try:
response_json = response.json()
@@ -2155,13 +2615,17 @@ class Jira:
return True
except JiraRequiredCustomFieldsError as custom_fields_error:
logger.error(f"Custom fields error: {custom_fields_error}")
- return False
+ raise custom_fields_error
+ except JiraSendFindingsResponseError as response_error:
+ logger.error(f"Jira response error: {response_error}")
+ raise response_error
except JiraRefreshTokenError as refresh_error:
logger.error(f"Token refresh error: {refresh_error}")
- return False
+ raise refresh_error
except JiraRefreshTokenResponseError as response_error:
- logger.error(f"Token response error: {response_error}")
- return False
+ raise response_error
+ except JiraNoTokenError as no_token_error:
+ raise no_token_error
except Exception as e:
logger.error(f"Failed to send finding: {e}")
return False
diff --git a/prowler/lib/outputs/ocsf/ocsf.py b/prowler/lib/outputs/ocsf/ocsf.py
index 731d029284..53f27d0e1b 100644
--- a/prowler/lib/outputs/ocsf/ocsf.py
+++ b/prowler/lib/outputs/ocsf/ocsf.py
@@ -227,6 +227,10 @@ class OCSF(Output):
json_output = finding.json(exclude_none=True, indent=4)
self._file_descriptor.write(json_output)
self._file_descriptor.write(",")
+ except OSError:
+ # I/O errors (e.g. ENOSPC) are not recoverable per finding:
+ # fail fast instead of logging once per finding.
+ raise
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
@@ -239,6 +243,10 @@ class OCSF(Output):
self._file_descriptor.truncate()
self._file_descriptor.write("]")
self._file_descriptor.close()
+ except OSError:
+ # Propagate unrecoverable I/O errors (e.g. ENOSPC) so the caller can
+ # fail fast instead of producing a corrupt output file.
+ raise
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
diff --git a/prowler/lib/outputs/outputs.py b/prowler/lib/outputs/outputs.py
index d0ec605d4b..05421ac584 100644
--- a/prowler/lib/outputs/outputs.py
+++ b/prowler/lib/outputs/outputs.py
@@ -7,43 +7,56 @@ from prowler.lib.outputs.common import Status
from prowler.lib.outputs.finding import Finding
-def stdout_report(finding, color, verbose, status, fix):
+def stdout_report(finding, color, verbose, status, fix, provider=None):
if finding.check_metadata.Provider == "aws":
details = finding.region
- if finding.check_metadata.Provider == "azure":
+ elif finding.check_metadata.Provider == "azure":
details = finding.location
- if finding.check_metadata.Provider == "gcp":
+ elif finding.check_metadata.Provider == "gcp":
details = finding.location.lower()
- if finding.check_metadata.Provider == "kubernetes":
+ elif finding.check_metadata.Provider == "kubernetes":
details = finding.namespace.lower()
- if finding.check_metadata.Provider == "github":
+ elif finding.check_metadata.Provider == "github":
details = finding.owner
- if finding.check_metadata.Provider == "m365":
+ elif finding.check_metadata.Provider == "m365":
details = finding.location
- if finding.check_metadata.Provider == "mongodbatlas":
+ elif finding.check_metadata.Provider == "mongodbatlas":
details = finding.location
- if finding.check_metadata.Provider == "nhn":
+ elif finding.check_metadata.Provider == "nhn":
details = finding.location
- if finding.check_metadata.Provider == "llm":
+ elif finding.check_metadata.Provider == "e2enetworks":
+ details = finding.location
+ elif finding.check_metadata.Provider == "stackit":
+ details = finding.location
+ elif finding.check_metadata.Provider == "llm":
details = finding.check_metadata.CheckID
- if finding.check_metadata.Provider == "iac":
+ elif finding.check_metadata.Provider == "iac":
details = finding.check_metadata.CheckID
- if finding.check_metadata.Provider == "oraclecloud":
+ elif finding.check_metadata.Provider == "oraclecloud":
details = finding.region
- if finding.check_metadata.Provider == "alibabacloud":
+ elif finding.check_metadata.Provider == "alibabacloud":
details = finding.region
- if finding.check_metadata.Provider == "openstack":
+ elif finding.check_metadata.Provider == "openstack":
details = finding.region
- if finding.check_metadata.Provider == "cloudflare":
+ elif finding.check_metadata.Provider == "cloudflare":
details = finding.zone_name
- if finding.check_metadata.Provider == "googleworkspace":
+ elif finding.check_metadata.Provider == "googleworkspace":
details = finding.location
- if finding.check_metadata.Provider == "vercel":
+ elif finding.check_metadata.Provider == "vercel":
details = finding.region
- if finding.check_metadata.Provider == "okta":
+ elif finding.check_metadata.Provider == "okta":
details = finding.region
- if finding.check_metadata.Provider == "scaleway":
+ elif finding.check_metadata.Provider == "scaleway":
details = finding.region
+ elif finding.check_metadata.Provider == "linode":
+ details = finding.region
+ else:
+ # Dynamic fallback: any external/custom provider
+ if provider is None:
+ from prowler.providers.common.provider import Provider
+
+ provider = Provider.get_global_provider()
+ details = provider.get_stdout_detail(finding)
if (verbose or fix) and (not status or finding.status in status):
if finding.muted:
@@ -63,12 +76,15 @@ def report(check_findings, provider, output_options):
if hasattr(output_options, "verbose"):
verbose = output_options.verbose
if check_findings:
- # TO-DO Generic Function
if provider.type == "aws":
check_findings.sort(key=lambda x: x.region)
-
- if provider.type == "azure":
+ elif provider.type == "azure":
check_findings.sort(key=lambda x: x.subscription)
+ else:
+ # Dynamic fallback: any external/custom provider
+ sort_key = provider.get_finding_sort_key()
+ if sort_key and isinstance(sort_key, str):
+ check_findings.sort(key=lambda x: getattr(x, sort_key, ""))
for finding in check_findings:
# Print findings by stdout
@@ -79,12 +95,16 @@ def report(check_findings, provider, output_options):
if hasattr(output_options, "fixer"):
fixer = output_options.fixer
color = set_report_color(finding.status, finding.muted)
+ # Pass the local `provider` through so the dynamic else inside
+ # `stdout_report` does not have to consult the global singleton
+ # — defeating the whole purpose of the new parameter.
stdout_report(
finding,
color,
verbose,
status,
fixer,
+ provider=provider,
)
else: # No service resources in the whole account
diff --git a/prowler/lib/outputs/summary_table.py b/prowler/lib/outputs/summary_table.py
index 263c21b1e5..2d8da80597 100644
--- a/prowler/lib/outputs/summary_table.py
+++ b/prowler/lib/outputs/summary_table.py
@@ -70,6 +70,16 @@ def display_summary_table(
elif provider.type == "nhn":
entity_type = "Tenant Domain"
audited_entities = provider.identity.tenant_domain
+ elif provider.type == "e2enetworks":
+ entity_type = "Project"
+ audited_entities = str(provider.identity.project_id)
+ elif provider.type == "stackit":
+ if provider.identity.project_name:
+ entity_type = "Project"
+ audited_entities = provider.identity.project_name
+ else:
+ entity_type = "Project ID"
+ audited_entities = provider.identity.project_id
elif provider.type == "iac":
if provider.scan_repository_url:
entity_type = "Repository"
@@ -114,6 +124,14 @@ def display_summary_table(
elif provider.type == "scaleway":
entity_type = "Organization"
audited_entities = provider.identity.organization_id
+ elif provider.type == "linode":
+ entity_type = "Account"
+ audited_entities = (
+ provider.identity.username or provider.identity.email or "linode"
+ )
+ else:
+ # Dynamic fallback: any external/custom provider
+ entity_type, audited_entities = provider.get_summary_entity()
# Check if there are findings and that they are not all MANUAL
if findings and not all(finding.status == "MANUAL" for finding in findings):
diff --git a/prowler/lib/resource_limit.py b/prowler/lib/resource_limit.py
new file mode 100644
index 0000000000..da144e9dd0
--- /dev/null
+++ b/prowler/lib/resource_limit.py
@@ -0,0 +1,88 @@
+"""Scoped resource scan limits for high-volume resources.
+
+Some services accumulate huge numbers of resources (EBS snapshots, backup
+recovery points, log groups, Lambda functions, ECS task definitions,
+CodeArtifact packages). Scanning all of them causes API throttling, slow
+scans, cost and noisy findings.
+
+``get_resource_scan_limit`` resolves the configured number of resources to
+analyze for a supported resource path. A limited resource can produce zero,
+one, or many findings; findings are not capped or re-ordered here.
+
+Tradeoff: for newest-based resources, services may need to list lightweight or
+base metadata broadly to select the truly newest resources, then apply limits
+only to expensive hydration or analysis. The helper must not send
+user-configured limits as unsafe paginator ``PageSize`` values because AWS
+services validate page sizes differently.
+"""
+
+from collections.abc import Callable, Iterable, Iterator, Mapping
+from itertools import islice
+from typing import Any, Optional, Protocol, TypeVar
+
+GLOBAL_LIMIT_KEY = "max_scanned_resources_per_service"
+T = TypeVar("T")
+
+
+class PaginatorProtocol(Protocol):
+ """Minimal boto3-compatible paginator interface used by this module."""
+
+ def paginate(self, **operation_parameters: Any) -> Iterable[Mapping[str, Any]]:
+ """Return paginator pages for the provided operation parameters."""
+
+
+def get_resource_scan_limit(audit_config: dict, service_key: str) -> Optional[int]:
+ """Resolve the resource scan limit for a service.
+
+ Precedence: per-service key (``service_key``) > global
+ ``max_scanned_resources_per_service`` > unlimited.
+
+ A non-positive resolved value means **unlimited** (``None``), preserving
+ the legacy behavior as an explicit opt-out.
+
+ Args:
+ audit_config: The provider ``audit_config`` dictionary.
+ service_key: The per-service config key, e.g. ``max_lambda_functions``.
+
+ Returns:
+ The limit as a positive ``int``, or ``None`` for unlimited.
+ """
+ value = audit_config.get(service_key)
+ if value is None:
+ value = audit_config.get(GLOBAL_LIMIT_KEY)
+ if value is None or value <= 0:
+ return None
+ return int(value)
+
+
+def limit_resources(resources: Iterable[T], limit: Optional[int]) -> Iterator[T]:
+ """Yield up to ``limit`` resources without changing resource order."""
+ if not limit or limit <= 0:
+ yield from resources
+ return
+ yield from islice(resources, limit)
+
+
+def iter_limited_paginator_items(
+ paginator: PaginatorProtocol,
+ result_key: str,
+ limit: Optional[int],
+ item_filter: Optional[Callable[[T], bool]] = None,
+ **operation_parameters: Any,
+) -> Iterator[T]:
+ """Yield paginator result items, stopping after ``limit`` selected items.
+
+ The configured resource-analysis limit is intentionally not sent as
+ ``PageSize`` because AWS services validate page sizes differently. The
+ paginator receives only the operation parameters needed by the AWS API,
+ while this iterator applies the analysis limit defensively client-side.
+ """
+ selected = 0
+ for page in paginator.paginate(**operation_parameters):
+ for item in page.get(result_key, []):
+ if item_filter and not item_filter(item):
+ continue
+ yield item
+ selected += 1
+ if limit and selected >= limit:
+ return
diff --git a/prowler/lib/scan/scan.py b/prowler/lib/scan/scan.py
index 2ce7263e2b..b87cfcdf1d 100644
--- a/prowler/lib/scan/scan.py
+++ b/prowler/lib/scan/scan.py
@@ -4,8 +4,8 @@ from types import SimpleNamespace
from typing import Generator
from prowler.lib.check.check import (
+ _resolve_check_module,
execute,
- import_check,
list_services,
update_audit_metadata,
)
@@ -178,25 +178,58 @@ class Scan:
)
)
- # Exclude checks
+ # Validate excluded checks against the FULL provider catalog — not
+ # just the selected scope — so a global config can exclude a valid
+ # check even when that check is not part of a particular scoped run.
+ excluded_check_set: set[str] = set()
if excluded_checks:
- for check in excluded_checks:
- if check in self._checks_to_execute:
- self._checks_to_execute.remove(check)
- else:
- raise ScanInvalidCheckError(
- f"Invalid check provided: {check}. Check does not exist in the provider."
- )
+ excluded_check_set = set(excluded_checks)
+ if len(excluded_check_set) != len(excluded_checks):
+ raise ScanInvalidCheckError(
+ "Duplicate excluded checks are not allowed."
+ )
+ unknown_checks = excluded_check_set.difference(self._bulk_checks_metadata)
+ if unknown_checks:
+ raise ScanInvalidCheckError(
+ f"Invalid excluded check(s) provided: {sorted(unknown_checks)}."
+ )
- # Exclude services
+ # Validate excluded services against the provider service catalog.
+ # Only resolve the catalog when there is something to check to avoid
+ # walking the provider package tree unnecessarily.
+ excluded_service_set: set[str] = set()
if excluded_services:
- for check in self._checks_to_execute:
- if get_service_name_from_check_name(check) in excluded_services:
- self._checks_to_execute.remove(check)
- else:
- raise ScanInvalidServiceError(
- f"Invalid service provided: {check}. Service does not exist in the provider."
- )
+ excluded_service_set = set(excluded_services)
+ if len(excluded_service_set) != len(excluded_services):
+ raise ScanInvalidServiceError(
+ "Duplicate excluded services are not allowed."
+ )
+ unknown_services = excluded_service_set.difference(
+ list_services(provider.type)
+ )
+ if unknown_services:
+ raise ScanInvalidServiceError(
+ f"Invalid excluded service(s) provided: {sorted(unknown_services)}."
+ )
+
+ if excluded_check_set or excluded_service_set:
+ previous_scope = self._checks_to_execute
+ selected_checks = {
+ check
+ for check in previous_scope
+ if check not in excluded_check_set
+ and get_service_name_from_check_name(check) not in excluded_service_set
+ }
+ # Only complain when exclusions actually emptied a non-empty
+ # scope. If the scope was already empty (e.g. a severity or
+ # category filter matched nothing) the exclusions did not
+ # cause the emptiness and the misleading error would obscure
+ # the real reason.
+ if previous_scope and not selected_checks:
+ raise ScanInvalidCheckError(
+ "The scan configuration excludes every selected check."
+ )
+ self._checks_to_execute = sorted(selected_checks)
self._number_of_checks_to_execute = len(self._checks_to_execute)
@@ -426,9 +459,14 @@ class Scan:
# Recover service from check name
service = get_service_name_from_check_name(check_name)
try:
- # Import check module
- check_module_path = f"prowler.providers.{self._provider.type}.services.{service}.{check_name}.{check_name}"
- lib = import_check(check_module_path)
+ # Import check module (built-in or entry point) —
+ # delegates to `_resolve_check_module` so external
+ # providers registered via entry points are resolved
+ # correctly (their checks do not live under
+ # `prowler.providers.{type}.services...`).
+ lib = _resolve_check_module(
+ self._provider.type, service, check_name
+ )
# Recover functions from check
check_to_execute = getattr(lib, check_name)
check = check_to_execute()
diff --git a/prowler/lib/utils/utils.py b/prowler/lib/utils/utils.py
index c4b29f6cc1..62e01d66ef 100644
--- a/prowler/lib/utils/utils.py
+++ b/prowler/lib/utils/utils.py
@@ -9,52 +9,116 @@ except ImportError:
pass
import re
+import shutil
+import subprocess
import sys
import tempfile
from datetime import datetime
-from hashlib import sha512
+from functools import lru_cache
+from hashlib import sha1, sha512
from io import TextIOWrapper
from ipaddress import ip_address
from os.path import exists
from time import mktime
-from typing import Any, Optional
+from typing import Any, Iterable, Mapping, Optional, Union
from colorama import Style
-from detect_secrets import SecretsCollection
-from detect_secrets.settings import transient_settings
from prowler.config.config import encoding_format_utf_8
from prowler.lib.logger import logger
-default_detect_secrets_plugins = [
- {"name": "ArtifactoryDetector"},
- {"name": "AWSKeyDetector"},
- {"name": "AzureStorageKeyDetector"},
- {"name": "BasicAuthDetector"},
- {"name": "CloudantDetector"},
- {"name": "DiscordBotTokenDetector"},
- {"name": "GitHubTokenDetector"},
- {"name": "GitLabTokenDetector"},
- {"name": "Base64HighEntropyString", "limit": 6.0},
- {"name": "HexHighEntropyString", "limit": 3.0},
- {"name": "IbmCloudIamDetector"},
- {"name": "IbmCosHmacDetector"},
- # {"name": "IPPublicDetector"}, https://github.com/Yelp/detect-secrets/pull/885
- {"name": "JwtTokenDetector"},
- {"name": "KeywordDetector"},
- {"name": "MailchimpDetector"},
- {"name": "NpmDetector"},
- {"name": "OpenAIDetector"},
- {"name": "PrivateKeyDetector"},
- {"name": "PypiTokenDetector"},
- {"name": "SendGridDetector"},
- {"name": "SlackDetector"},
- {"name": "SoftlayerDetector"},
- {"name": "SquareOAuthDetector"},
- {"name": "StripeDetector"},
- # {"name": "TelegramBotTokenDetector"}, https://github.com/Yelp/detect-secrets/pull/878
- {"name": "TwilioKeyDetector"},
-]
+# Default minimum confidence level for reporting findings. "low" is required to
+# enable Kingfisher's built-in generic rules (Generic Password / Secret / API
+# Key), which preserve the keyword-based coverage Prowler had with
+# detect-secrets' KeywordDetector; at "medium" those generic rules do not fire.
+# Possible values: "low", "medium", "high".
+default_secrets_confidence = "low"
+
+# Kingfisher exit codes considered successful: 0 (no findings), 200 (findings),
+# 205 (validated findings).
+_kingfisher_success_exit_codes = (0, 200, 205)
+
+# Number of payloads scanned per Kingfisher invocation in batch mode. Bounds
+# peak temp-disk and memory while still amortizing the per-process spawn cost
+# across many fragments (see detect_secrets_scan_batch).
+default_secrets_batch_chunk_size = 500
+
+# Wall-clock cap (seconds) for a single Kingfisher subprocess, so a hung binary
+# cannot block the audit indefinitely.
+default_secrets_scan_timeout = 300
+
+
+class SecretsScanError(Exception):
+ """The secret scanner could not produce a trustworthy result.
+
+ Raised when Kingfisher exits with a non-success code, times out, cannot be
+ located/executed, or returns output that cannot be parsed. This is distinct
+ from "no secrets found": a security check must never treat a scanner failure
+ as a clean result, so callers are expected to surface it as ``MANUAL``
+ (manual review required) instead of ``PASS``.
+ """
+
+
+@lru_cache(maxsize=1)
+def get_kingfisher_binary() -> str:
+ """Return the path to the bundled Kingfisher binary (cached)."""
+ from kingfisher import get_binary_path
+
+ return get_binary_path()
+
+
+def _build_kingfisher_command(
+ scan_paths: list,
+ output_path: str,
+ confidence: str,
+ validate: bool,
+ no_dedup: bool = False,
+) -> list:
+ """Build the Kingfisher ``scan`` command shared by single and batch scans."""
+ command = [
+ get_kingfisher_binary(),
+ "scan",
+ *scan_paths,
+ "--format",
+ "json",
+ "--output",
+ output_path,
+ "--no-update-check",
+ "--confidence",
+ confidence,
+ ]
+ if validate:
+ # Live-validate discovered secrets against provider APIs. Use
+ # conservative defaults (short timeout, no retries) to limit the blast
+ # radius of the outbound calls.
+ command += ["--validation-timeout", "5", "--validation-retries", "0"]
+ else:
+ command.append("--no-validate")
+ if no_dedup:
+ # Report every occurrence (one per file) so batched results match
+ # scanning each payload individually.
+ command.append("--no-dedup")
+ return command
+
+
+def _finding_to_dict(entry: dict, fallback_filename: str) -> dict:
+ """Convert a Kingfisher finding entry into Prowler's finding dict shape."""
+ rule = entry.get("rule", {})
+ finding = entry.get("finding", {})
+ snippet = finding.get("snippet", "") or ""
+ return {
+ "filename": finding.get("path", fallback_filename),
+ "line_number": finding.get("line"),
+ "type": rule.get("name"),
+ # Non-security identifier for the matched secret (matches the
+ # detect-secrets output shape); not used for security.
+ "hashed_secret": (
+ sha1(snippet.encode(), usedforsecurity=False).hexdigest()
+ if snippet
+ else None
+ ),
+ "is_verified": finding.get("validation", {}).get("status") == "Active",
+ }
def open_file(input_file: str, mode: str = "r") -> TextIOWrapper:
@@ -111,77 +175,188 @@ def hash_sha512(string: str) -> str:
return sha512(string.encode(encoding_format_utf_8)).hexdigest()[0:9]
-def detect_secrets_scan(
- data: str = None,
- file=None,
- excluded_secrets: list[str] = None,
- detect_secrets_plugins: dict = None,
-) -> list[dict[str, str]]:
- """detect_secrets_scan scans the data or file for secrets using the detect-secrets library.
- Args:
- data (str): The data to scan for secrets.
- file (str): The file to scan for secrets.
- excluded_secrets (list): A list of regex patterns to exclude from the scan.
- detect_secrets_plugins (dict): The settings to use for the scan.
- Returns:
- dict: The secrets found in the
- Raises:
- Exception: If an error occurs during the scan.
- Examples:
- >>> detect_secrets_scan(data="password=password")
- [{'filename': 'data', 'hashed_secret': 'f7c3bc1d808e04732adf679965ccc34ca7ae3441', 'is_verified': False, 'line_number': 1, 'type': 'Secret Keyword'}]
- >>> detect_secrets_scan(file="file.txt")
- {'file.txt': [{'filename': 'file.txt', 'hashed_secret': 'f7c3bc1d808e04732adf679965ccc34ca7ae3441', 'is_verified': False, 'line_number': 1, 'type': 'Secret Keyword'}]}
+def _scan_batch_chunk(
+ chunk: list,
+ excluded_secrets: list,
+ confidence: str,
+ validate: bool,
+ results: dict,
+) -> None:
+ """Scan one chunk of ``(key, data)`` payloads in a single Kingfisher call.
+
+ Writes each payload to its own file in a temp directory, scans the whole
+ directory once (``--no-dedup`` so per-file results match individual scans),
+ maps findings back to their key by file path, and appends them to
+ ``results``. The temp directory is always removed.
"""
+ if not chunk:
+ return
+ tmp_dir = tempfile.mkdtemp()
+ temp_output_file = None
try:
- if not file:
- temp_data_file = tempfile.NamedTemporaryFile(delete=False)
- temp_data_file.write(bytes(data, encoding="raw_unicode_escape"))
- temp_data_file.close()
+ index_to_key = {}
+ for index, (key, data) in enumerate(chunk):
+ content = data if data.endswith("\n") else data + "\n"
+ name = str(index)
+ with open(os.path.join(tmp_dir, name), "wb") as fh:
+ fh.write(bytes(content, encoding="raw_unicode_escape"))
+ index_to_key[name] = key
- secrets = SecretsCollection()
-
- if not detect_secrets_plugins:
- detect_secrets_plugins = default_detect_secrets_plugins
-
- settings = {
- "plugins_used": detect_secrets_plugins,
- "filters_used": [
- {"path": "detect_secrets.filters.common.is_invalid_file"},
- {"path": "detect_secrets.filters.common.is_known_false_positive"},
- {"path": "detect_secrets.filters.heuristic.is_likely_id_string"},
- {"path": "detect_secrets.filters.heuristic.is_potential_secret"},
- ],
- }
-
- if excluded_secrets and len(excluded_secrets) > 0:
- settings["filters_used"].append(
- {
- "path": "detect_secrets.filters.regex.should_exclude_line",
- "pattern": excluded_secrets,
- }
+ temp_output_file = tempfile.NamedTemporaryFile(delete=False, suffix=".json")
+ temp_output_file.close()
+ command = _build_kingfisher_command(
+ [tmp_dir], temp_output_file.name, confidence, validate, no_dedup=True
+ )
+ process = subprocess.run(
+ command,
+ capture_output=True,
+ text=True,
+ timeout=default_secrets_scan_timeout,
+ )
+ if process.returncode not in _kingfisher_success_exit_codes:
+ raise SecretsScanError(
+ f"Kingfisher exited with code {process.returncode}: "
+ f"{process.stderr.strip()[:500]}"
)
- with transient_settings(settings):
- if file:
- secrets.scan_file(file)
- else:
- secrets.scan_file(temp_data_file.name)
- if not file:
- os.remove(temp_data_file.name)
+ with open(temp_output_file.name, encoding=encoding_format_utf_8) as f:
+ output = f.read()
+ kingfisher_output = json.loads(output) if output.strip() else {}
- detect_secrets_output = secrets.json()
+ source_lines_cache = {}
- if detect_secrets_output:
- if file:
- return detect_secrets_output[file]
- else:
- return detect_secrets_output[temp_data_file.name]
- else:
- return None
- except Exception as e:
- logger.error(f"Error scanning for secrets: {e}")
- return None
+ def source_lines(file_name: str) -> list:
+ if file_name not in source_lines_cache:
+ with open(
+ os.path.join(tmp_dir, file_name),
+ encoding=encoding_format_utf_8,
+ errors="replace",
+ ) as f:
+ source_lines_cache[file_name] = f.read().splitlines()
+ return source_lines_cache[file_name]
+
+ for entry in kingfisher_output.get("findings", []):
+ finding = entry.get("finding", {})
+ name = os.path.basename(finding.get("path", ""))
+ key = index_to_key.get(name)
+ if key is None:
+ continue
+ # Validate the line index before any consumer trusts it. Checks use
+ # ``line_number`` as a 1-based index into their own parallel data
+ # (e.g. CloudWatch does ``events[line_number - 1]``), so a missing,
+ # non-integer, or out-of-range line would crash the check or map the
+ # secret to the wrong resource. Fail closed: surface a malformed
+ # finding as a scan failure so callers report MANUAL instead of a
+ # wrong PASS/FAIL. ``bool`` is rejected explicitly because it is a
+ # subclass of ``int``.
+ line_number = finding.get("line")
+ lines = source_lines(name)
+ if (
+ isinstance(line_number, bool)
+ or not isinstance(line_number, int)
+ or not 1 <= line_number <= len(lines)
+ ):
+ raise SecretsScanError(
+ f"Kingfisher returned an invalid line number "
+ f"{line_number!r} for a finding in {name}"
+ )
+ if excluded_secrets and any(
+ re.search(pattern, lines[line_number - 1])
+ for pattern in excluded_secrets
+ ):
+ continue
+ results.setdefault(key, []).append(_finding_to_dict(entry, name))
+ except SecretsScanError:
+ # Already a typed scan failure; propagate so callers report MANUAL.
+ raise
+ except subprocess.TimeoutExpired as error:
+ raise SecretsScanError(
+ f"Kingfisher timed out after {default_secrets_scan_timeout}s "
+ "while scanning for secrets"
+ ) from error
+ except Exception as error:
+ # Fail closed: a missing/unexecutable binary, unparseable JSON output or
+ # any other runtime failure must NOT be silently treated as "no secrets
+ # found". Surface it so callers can report MANUAL instead of PASS.
+ raise SecretsScanError(f"Secret scan failed: {error}") from error
+ finally:
+ if temp_output_file and os.path.exists(temp_output_file.name):
+ os.remove(temp_output_file.name)
+ shutil.rmtree(tmp_dir, ignore_errors=True)
+
+
+def detect_secrets_scan_batch(
+ payloads: Union[Mapping[Any, str], Iterable[tuple[Any, str]]],
+ excluded_secrets: Optional[list[str]] = None,
+ confidence: str = default_secrets_confidence,
+ validate: bool = False,
+ chunk_size: int = default_secrets_batch_chunk_size,
+) -> dict:
+ """Scan many payloads with Kingfisher in chunked subprocess invocations.
+
+ This is the scan entry point used by every secret check. Each payload is
+ written to its own file and scanned with ``--no-dedup`` so per-payload
+ results match scanning each payload on its own. Payloads are processed in
+ chunks (writing each to disk and releasing it as it is consumed) to bound
+ peak temp-disk and memory use while amortizing the per-process spawn cost
+ across many fragments.
+
+ By default the scan runs fully offline (``--no-validate``,
+ ``--no-update-check``): no network calls are made, so the scanned data is
+ never sent anywhere. When ``validate`` is True, Kingfisher additionally
+ checks whether each discovered secret is live by authenticating with it
+ against the provider's API (the secret itself is the credential; no extra
+ permissions are required). That makes outbound network calls, so it must be
+ explicitly opted in.
+
+ Args:
+ payloads: a mapping ``{key: data}`` or any iterable of ``(key, data)``
+ pairs. ``key`` is any hashable the caller uses to map findings back
+ to its source (e.g. a variable name or a ``(resource, stream)``).
+ excluded_secrets (list): regex patterns; a finding whose source line
+ matches one is excluded.
+ confidence (str): minimum Kingfisher confidence ("low"/"medium"/"high").
+ validate (bool): live-validate discovered secrets (outbound calls).
+ chunk_size (int): payloads scanned per Kingfisher invocation.
+ Returns:
+ dict mapping each key that produced findings to its list of finding
+ dicts, each with ``filename``, ``line_number``, ``type``,
+ ``hashed_secret`` and ``is_verified`` keys. Keys with no findings are
+ omitted.
+ Raises:
+ SecretsScanError: if the scanner fails for any chunk (non-success exit
+ code, timeout, missing/unexecutable binary or unparseable output).
+ An empty result is therefore always "no secrets found", never a
+ silent scan failure; callers must report MANUAL on this error.
+ """
+ items = payloads.items() if hasattr(payloads, "items") else payloads
+ results = {}
+ chunk = []
+ for key, data in items:
+ chunk.append((key, data))
+ if len(chunk) >= chunk_size:
+ _scan_batch_chunk(chunk, excluded_secrets, confidence, validate, results)
+ chunk = []
+ _scan_batch_chunk(chunk, excluded_secrets, confidence, validate, results)
+ return results
+
+
+def annotate_verified_secrets(report, secrets: list) -> None:
+ """Escalate and annotate a finding when any of its secrets is confirmed live.
+
+ When secret validation (``--scan-secrets-validate`` / ``secrets_validate``)
+ confirms that a discovered secret is live, the finding is more severe than a
+ potential secret: its severity is raised to critical and a note is appended
+ to ``status_extended``. No-op when no secret was validated as live, so the
+ default offline behavior (and existing finding messages) is unchanged.
+ """
+ if secrets and any(secret.get("is_verified") for secret in secrets):
+ from prowler.lib.check.models import Severity
+
+ report.check_metadata.Severity = Severity.critical
+ report.status_extended += (
+ " One or more of these secrets were confirmed to be live."
+ )
def validate_ip_address(ip_string):
diff --git a/prowler/providers/alibabacloud/alibabacloud_provider.py b/prowler/providers/alibabacloud/alibabacloud_provider.py
index 82e48e2f14..d7020186a0 100644
--- a/prowler/providers/alibabacloud/alibabacloud_provider.py
+++ b/prowler/providers/alibabacloud/alibabacloud_provider.py
@@ -53,6 +53,7 @@ class AlibabacloudProvider(Provider):
"""
_type: str = "alibabacloud"
+ sdk_only: bool = False
_identity: AlibabaCloudIdentityInfo
_session: AlibabaCloudSession
_audit_resources: list = []
diff --git a/tests/providers/alibabacloud/__init__.py b/prowler/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_weekly/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/__init__.py
rename to prowler/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_weekly/__init__.py
diff --git a/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/ecs_securitygroup_restrict_rdp_internet.py b/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/ecs_securitygroup_restrict_rdp_internet.py
index 72e579bbc6..45cfa81bda 100644
--- a/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/ecs_securitygroup_restrict_rdp_internet.py
+++ b/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/ecs_securitygroup_restrict_rdp_internet.py
@@ -26,7 +26,7 @@ class ecs_securitygroup_restrict_rdp_internet(Check):
for ingress_rule in security_group.ingress_rules:
# Check if rule allows traffic (policy == "accept")
- if ingress_rule.get("policy", "accept") != "accept":
+ if str(ingress_rule.get("policy", "accept")).lower() != "accept":
continue
# Check protocol (tcp for RDP)
diff --git a/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/ecs_securitygroup_restrict_ssh_internet.py b/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/ecs_securitygroup_restrict_ssh_internet.py
index 9dfdd182e1..0315a69207 100644
--- a/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/ecs_securitygroup_restrict_ssh_internet.py
+++ b/prowler/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/ecs_securitygroup_restrict_ssh_internet.py
@@ -26,7 +26,7 @@ class ecs_securitygroup_restrict_ssh_internet(Check):
for ingress_rule in security_group.ingress_rules:
# Check if rule allows traffic (policy == "accept")
- if ingress_rule.get("policy", "accept") != "accept":
+ if str(ingress_rule.get("policy", "accept")).lower() != "accept":
continue
# Check protocol (tcp for SSH)
diff --git a/prowler/providers/alibabacloud/services/ram/ram_password_policy_number/ram_password_policy_number.py b/prowler/providers/alibabacloud/services/ram/ram_password_policy_number/ram_password_policy_number.py
new file mode 100644
index 0000000000..305570289c
--- /dev/null
+++ b/prowler/providers/alibabacloud/services/ram/ram_password_policy_number/ram_password_policy_number.py
@@ -0,0 +1,34 @@
+from prowler.lib.check.models import Check, CheckReportAlibabaCloud
+from prowler.providers.alibabacloud.services.ram.ram_client import ram_client
+
+
+class ram_password_policy_number(Check):
+ """Check if RAM password policy requires at least one number."""
+
+ def execute(self) -> list[CheckReportAlibabaCloud]:
+ findings = []
+
+ if ram_client.password_policy:
+ report = CheckReportAlibabaCloud(
+ metadata=self.metadata(), resource=ram_client.password_policy
+ )
+ report.region = ram_client.region
+ report.resource_id = f"{ram_client.audited_account}-password-policy"
+ report.resource_arn = (
+ f"acs:ram::{ram_client.audited_account}:password-policy"
+ )
+
+ if ram_client.password_policy.require_numbers:
+ report.status = "PASS"
+ report.status_extended = (
+ "RAM password policy requires at least one number."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ "RAM password policy does not require at least one number."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/aws_provider.py b/prowler/providers/aws/aws_provider.py
index cf6cbdd73a..b4c9ed3771 100644
--- a/prowler/providers/aws/aws_provider.py
+++ b/prowler/providers/aws/aws_provider.py
@@ -90,6 +90,7 @@ class AwsProvider(Provider):
"""
_type: str = "aws"
+ sdk_only: bool = False
_identity: AWSIdentityInfo
_session: AWSSession
_organizations_metadata: AWSOrganizationsInfo
diff --git a/prowler/providers/aws/aws_regions_by_service.json b/prowler/providers/aws/aws_regions_by_service.json
index f525ce2155..6ee2b8d627 100644
--- a/prowler/providers/aws/aws_regions_by_service.json
+++ b/prowler/providers/aws/aws_regions_by_service.json
@@ -482,6 +482,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"ca-west-1",
"eu-central-1",
@@ -506,7 +507,9 @@
"cn-north-1",
"cn-northwest-1"
],
- "aws-eusc": [],
+ "aws-eusc": [
+ "eusc-de-east-1"
+ ],
"aws-us-gov": [
"us-gov-east-1",
"us-gov-west-1"
@@ -896,6 +899,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -1231,6 +1235,24 @@
"aws-us-gov": []
}
},
+ "aws-devops-agent": {
+ "regions": {
+ "aws": [
+ "ap-northeast-1",
+ "ap-southeast-1",
+ "ap-southeast-2",
+ "eu-central-1",
+ "eu-west-1",
+ "eu-west-2",
+ "sa-east-1",
+ "us-east-1",
+ "us-west-2"
+ ],
+ "aws-cn": [],
+ "aws-eusc": [],
+ "aws-us-gov": []
+ }
+ },
"awshealthdashboard": {
"regions": {
"aws": [
@@ -1292,6 +1314,7 @@
"ca-central-1",
"eu-central-1",
"eu-west-2",
+ "sa-east-1",
"us-east-1"
],
"aws-cn": [],
@@ -1566,9 +1589,13 @@
"ap-south-1",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"eu-central-1",
"eu-north-1",
+ "eu-south-1",
+ "eu-south-2",
"eu-west-1",
"eu-west-2",
"eu-west-3",
@@ -1590,6 +1617,7 @@
"ap-southeast-2",
"ca-central-1",
"eu-central-1",
+ "eu-south-2",
"eu-west-1",
"eu-west-2",
"us-east-1",
@@ -2193,6 +2221,7 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -2255,6 +2284,8 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"ca-west-1",
"eu-central-1",
@@ -2444,6 +2475,9 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-5",
+ "ap-southeast-6",
+ "ap-southeast-7",
"ca-central-1",
"eu-central-1",
"eu-central-2",
@@ -2557,6 +2591,7 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
@@ -2566,6 +2601,9 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-5",
+ "ap-southeast-6",
+ "ap-southeast-7",
"ca-central-1",
"ca-west-1",
"eu-central-1",
@@ -2579,6 +2617,7 @@
"il-central-1",
"me-central-1",
"me-south-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -2589,7 +2628,9 @@
"cn-north-1",
"cn-northwest-1"
],
- "aws-eusc": [],
+ "aws-eusc": [
+ "eusc-de-east-1"
+ ],
"aws-us-gov": [
"us-gov-east-1",
"us-gov-west-1"
@@ -2649,6 +2690,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ca-central-1",
"eu-central-1",
"eu-central-2",
@@ -2796,6 +2838,7 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
@@ -2806,6 +2849,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -3151,6 +3195,7 @@
"connecthealth": {
"regions": {
"aws": [
+ "eu-west-2",
"us-east-1",
"us-west-2"
],
@@ -3767,6 +3812,7 @@
"ap-southeast-5",
"ap-southeast-7",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
@@ -3810,7 +3856,9 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-6",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
@@ -3829,7 +3877,9 @@
"us-west-2"
],
"aws-cn": [],
- "aws-eusc": [],
+ "aws-eusc": [
+ "eusc-de-east-1"
+ ],
"aws-us-gov": [
"us-gov-east-1",
"us-gov-west-1"
@@ -3890,17 +3940,22 @@
"dsql": {
"regions": {
"aws": [
+ "ap-east-1",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
+ "ap-south-1",
+ "ap-southeast-1",
"ap-southeast-2",
"ap-southeast-4",
"ca-central-1",
"ca-west-1",
"eu-central-1",
+ "eu-north-1",
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "sa-east-1",
"us-east-1",
"us-east-2",
"us-west-2"
@@ -4577,7 +4632,12 @@
},
"elementalinference": {
"regions": {
- "aws": [],
+ "aws": [
+ "ap-south-1",
+ "eu-west-1",
+ "us-east-1",
+ "us-west-2"
+ ],
"aws-cn": [],
"aws-eusc": [],
"aws-us-gov": []
@@ -4681,15 +4741,19 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
"ap-south-1",
+ "ap-south-2",
"ap-southeast-1",
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
+ "ap-southeast-7",
"ca-central-1",
"ca-west-1",
"eu-central-1",
@@ -4703,6 +4767,7 @@
"il-central-1",
"me-central-1",
"me-south-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -5260,6 +5325,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -5310,6 +5376,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -5360,6 +5427,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -5410,6 +5478,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -5460,6 +5529,7 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
"ca-west-1",
@@ -6034,6 +6104,7 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
@@ -6081,6 +6152,7 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
@@ -6845,6 +6917,7 @@
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "il-central-1",
"me-south-1",
"sa-east-1",
"us-east-1",
@@ -7295,6 +7368,7 @@
"lightsail": {
"regions": {
"aws": [
+ "ap-east-1",
"ap-northeast-1",
"ap-northeast-2",
"ap-south-1",
@@ -7305,9 +7379,11 @@
"ca-central-1",
"eu-central-1",
"eu-north-1",
+ "eu-south-2",
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "sa-east-1",
"us-east-1",
"us-east-2",
"us-west-2"
@@ -7681,6 +7757,8 @@
"ap-south-1",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"eu-central-1",
"eu-north-1",
@@ -8065,6 +8143,7 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
@@ -8075,8 +8154,10 @@
"ap-southeast-3",
"ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
@@ -8088,6 +8169,7 @@
"il-central-1",
"me-central-1",
"me-south-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -8214,7 +8296,9 @@
"cn-north-1",
"cn-northwest-1"
],
- "aws-eusc": [],
+ "aws-eusc": [
+ "eusc-de-east-1"
+ ],
"aws-us-gov": [
"us-gov-east-1",
"us-gov-west-1"
@@ -8279,22 +8363,31 @@
"aws": [
"af-south-1",
"ap-east-1",
+ "ap-east-2",
"ap-northeast-1",
"ap-northeast-2",
"ap-northeast-3",
"ap-south-1",
+ "ap-south-2",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-3",
+ "ap-southeast-4",
"ap-southeast-5",
+ "ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
+ "eu-south-1",
"eu-south-2",
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "il-central-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -8315,6 +8408,7 @@
"ap-northeast-2",
"ap-northeast-3",
"ap-south-1",
+ "ap-south-2",
"ap-southeast-1",
"ap-southeast-2",
"ap-southeast-3",
@@ -8574,6 +8668,7 @@
"il-central-1",
"me-central-1",
"me-south-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -8706,13 +8801,19 @@
"aws": [
"ap-northeast-1",
"ap-northeast-2",
+ "ap-northeast-3",
"ap-south-1",
"ap-south-2",
"ap-southeast-2",
+ "ap-southeast-4",
"ca-central-1",
"eu-central-1",
+ "eu-central-2",
+ "eu-south-1",
+ "eu-south-2",
"eu-west-1",
"eu-west-2",
+ "sa-east-1",
"us-east-1",
"us-east-2",
"us-west-2"
@@ -9034,6 +9135,7 @@
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "sa-east-1",
"us-east-1",
"us-east-2",
"us-west-2"
@@ -9135,15 +9237,21 @@
"pcs": {
"regions": {
"aws": [
+ "af-south-1",
"ap-northeast-1",
+ "ap-northeast-3",
"ap-south-1",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-3",
"eu-central-1",
"eu-north-1",
+ "eu-south-1",
+ "eu-south-2",
"eu-west-1",
"eu-west-2",
"eu-west-3",
+ "sa-east-1",
"us-east-1",
"us-east-2",
"us-west-2"
@@ -9171,9 +9279,7 @@
"us-east-2",
"us-west-2"
],
- "aws-cn": [
- "cn-north-1"
- ],
+ "aws-cn": [],
"aws-eusc": [],
"aws-us-gov": []
}
@@ -9377,6 +9483,7 @@
"ap-southeast-1",
"ap-southeast-2",
"ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"eu-central-1",
"eu-central-2",
@@ -9395,7 +9502,9 @@
"aws-cn": [
"cn-northwest-1"
],
- "aws-eusc": [],
+ "aws-eusc": [
+ "eusc-de-east-1"
+ ],
"aws-us-gov": [
"us-gov-west-1"
]
@@ -9865,10 +9974,12 @@
"ap-southeast-1",
"ap-southeast-2",
"ap-southeast-3",
+ "ap-southeast-4",
"ap-southeast-5",
"ap-southeast-6",
"ap-southeast-7",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
@@ -9905,6 +10016,8 @@
"ap-south-1",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-5",
+ "ap-southeast-7",
"ca-central-1",
"eu-central-1",
"eu-south-2",
@@ -10012,7 +10125,10 @@
],
"aws-cn": [],
"aws-eusc": [],
- "aws-us-gov": []
+ "aws-us-gov": [
+ "us-gov-east-1",
+ "us-gov-west-1"
+ ]
}
},
"resource-groups": {
@@ -10182,6 +10298,7 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-6",
"ca-central-1",
"eu-central-1",
"eu-central-2",
@@ -10693,9 +10810,15 @@
"us-west-1",
"us-west-2"
],
- "aws-cn": [],
+ "aws-cn": [
+ "cn-north-1",
+ "cn-northwest-1"
+ ],
"aws-eusc": [],
- "aws-us-gov": []
+ "aws-us-gov": [
+ "us-gov-east-1",
+ "us-gov-west-1"
+ ]
}
},
"sagemaker": {
@@ -11315,7 +11438,9 @@
"ap-southeast-2",
"ap-southeast-3",
"ap-southeast-4",
+ "ap-southeast-6",
"ca-central-1",
+ "ca-west-1",
"eu-central-1",
"eu-central-2",
"eu-north-1",
@@ -11647,26 +11772,6 @@
]
}
},
- "simspaceweaver": {
- "regions": {
- "aws": [
- "ap-southeast-1",
- "ap-southeast-2",
- "eu-central-1",
- "eu-north-1",
- "eu-west-1",
- "us-east-1",
- "us-east-2",
- "us-west-2"
- ],
- "aws-cn": [],
- "aws-eusc": [],
- "aws-us-gov": [
- "us-gov-east-1",
- "us-gov-west-1"
- ]
- }
- },
"sms": {
"regions": {
"aws": [
@@ -13063,6 +13168,7 @@
"eu-west-3",
"me-central-1",
"me-south-1",
+ "mx-central-1",
"sa-east-1",
"us-east-1",
"us-east-2",
@@ -13351,6 +13457,7 @@
"wisdom": {
"regions": {
"aws": [
+ "af-south-1",
"ap-northeast-1",
"ap-northeast-2",
"ap-southeast-1",
@@ -13414,6 +13521,7 @@
"ap-south-1",
"ap-southeast-1",
"ap-southeast-2",
+ "ap-southeast-5",
"ca-central-1",
"eu-central-1",
"eu-west-1",
@@ -13422,6 +13530,7 @@
"il-central-1",
"sa-east-1",
"us-east-1",
+ "us-east-2",
"us-west-2"
],
"aws-cn": [
@@ -13520,4 +13629,4 @@
}
}
}
-}
\ No newline at end of file
+}
diff --git a/prowler/providers/aws/lib/arguments/arguments.py b/prowler/providers/aws/lib/arguments/arguments.py
index 50f4665b2d..2d1632422b 100644
--- a/prowler/providers/aws/lib/arguments/arguments.py
+++ b/prowler/providers/aws/lib/arguments/arguments.py
@@ -235,7 +235,7 @@ def validate_arguments(arguments: Namespace) -> tuple[bool, str]:
def validate_bucket(bucket_name: str) -> str:
"""validate_bucket validates that the input bucket_name is valid"""
if search(
- "^(?!^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$)(?!.*\.{2})(?!.*\.-)(?!.*-\.)(?!^xn--)(?!^sthree-)(?!^amzn-s3-demo-)(?!.*--table-s3$)[a-z0-9][a-z0-9.-]{1,61}[a-z0-9]$",
+ r"^(?!^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$)(?!.*\.{2})(?!.*\.-)(?!.*-\.)(?!^xn--)(?!^sthree-)(?!^amzn-s3-demo-)(?!.*--table-s3$)[a-z0-9][a-z0-9.-]{1,61}[a-z0-9]$",
bucket_name,
):
return bucket_name
diff --git a/tests/providers/alibabacloud/lib/__init__.py b/prowler/providers/aws/lib/ip_ranges/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/lib/__init__.py
rename to prowler/providers/aws/lib/ip_ranges/__init__.py
diff --git a/prowler/providers/aws/lib/ip_ranges/ip_ranges.py b/prowler/providers/aws/lib/ip_ranges/ip_ranges.py
new file mode 100644
index 0000000000..3dbb9d1b17
--- /dev/null
+++ b/prowler/providers/aws/lib/ip_ranges/ip_ranges.py
@@ -0,0 +1,51 @@
+import json
+import urllib.error
+import urllib.request
+from ipaddress import ip_network
+
+from prowler.lib.logger import logger
+
+AWS_IP_RANGES_URL = "https://ip-ranges.amazonaws.com/ip-ranges.json"
+AWS_IP_RANGES_TIMEOUT = 10
+
+
+def get_public_ip_networks() -> list:
+ """Fetch the AWS public IP prefixes as a list of ip_network objects.
+
+ The request verifies the server certificate against the system trust store,
+ matching urllib's default behaviour. This replaces the unmaintained
+ awsipranges package, whose latest release (0.3.3) calls
+ urllib.request.urlopen() with the cafile/capath arguments that Python 3.13
+ removed.
+
+ Returns an empty list when the feed cannot be fetched or parsed, and skips
+ individual malformed prefixes, so a transient or corrupt feed never aborts
+ the calling check.
+ """
+ try:
+ with urllib.request.urlopen(
+ AWS_IP_RANGES_URL, timeout=AWS_IP_RANGES_TIMEOUT
+ ) as response:
+ ranges = json.loads(response.read())
+ except (urllib.error.URLError, TimeoutError, json.JSONDecodeError) as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return []
+
+ networks = []
+ for key, prefixes in (
+ ("ip_prefix", ranges.get("prefixes", [])),
+ ("ipv6_prefix", ranges.get("ipv6_prefixes", [])),
+ ):
+ for prefix in prefixes:
+ cidr = prefix.get(key)
+ if not cidr:
+ continue
+ try:
+ networks.append(ip_network(cidr))
+ except ValueError as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return networks
diff --git a/tests/providers/alibabacloud/lib/mutelist/__init__.py b/prowler/providers/aws/services/acmpca/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/lib/mutelist/__init__.py
rename to prowler/providers/aws/services/acmpca/__init__.py
diff --git a/tests/providers/alibabacloud/services/__init__.py b/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/__init__.py
rename to prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/__init__.py
diff --git a/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.metadata.json b/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.metadata.json
new file mode 100644
index 0000000000..6915540539
--- /dev/null
+++ b/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.metadata.json
@@ -0,0 +1,41 @@
+{
+ "Provider": "aws",
+ "CheckID": "acmpca_certificate_authority_pqc_key_algorithm",
+ "CheckTitle": "AWS Private CA certificate authorities use a post-quantum (ML-DSA) key algorithm",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "acmpca",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsAcmPcaCertificateAuthority",
+ "ResourceGroup": "security",
+ "Description": "**AWS Private Certificate Authorities (Private CAs)** are assessed for use of a **post-quantum digital signature key algorithm** (`ML_DSA_44`, `ML_DSA_65`, `ML_DSA_87`). CAs that still issue certificates with RSA or ECC algorithms produce signatures vulnerable to forgery once a cryptographically relevant quantum computer is available.",
+ "Risk": "RSA and ECC signatures can be broken by Shor's algorithm on a sufficiently large quantum computer. A compromised CA private key would let an attacker issue arbitrary certificates trusted across the PKI, undermining identity and code-signing controls. Migrating CAs to **ML-DSA** (NIST FIPS 204) provides quantum-resistant signatures so issued certificates retain integrity in the post-quantum era.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/privateca/latest/userguide/PcaTerms.html",
+ "https://aws.amazon.com/about-aws/whats-new/2025/11/aws-private-ca-post-quantum-digital-certificates/",
+ "https://aws.amazon.com/blogs/security/post-quantum-ml-dsa-code-signing-with-aws-private-ca-and-aws-kms/",
+ "https://csrc.nist.gov/pubs/fips/204/final"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws acm-pca create-certificate-authority --certificate-authority-configuration '{\"KeyAlgorithm\":\"ML_DSA_65\",\"SigningAlgorithm\":\"ML_DSA_65\",\"Subject\":{...}}' --certificate-authority-type SUBORDINATE",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::ACMPCA::CertificateAuthority\n Properties:\n Type: SUBORDINATE\n KeyAlgorithm: ML_DSA_65 # FIX: post-quantum signature algorithm\n SigningAlgorithm: ML_DSA_65\n Subject:\n CommonName: example-pqc-ca\n```",
+ "Other": "Existing CAs cannot have their key algorithm changed; create a new CA with KeyAlgorithm = ML_DSA_44 / ML_DSA_65 / ML_DSA_87, re-issue certificates from it, and decommission the legacy CA once dependent workloads have rotated.",
+ "Terraform": "```hcl\nresource \"aws_acmpca_certificate_authority\" \"<example_resource_name>\" {\n type = \"SUBORDINATE\"\n certificate_authority_configuration {\n key_algorithm = \"ML_DSA_65\" # FIX: post-quantum signature algorithm\n signing_algorithm = \"ML_DSA_65\"\n subject {\n common_name = \"example-pqc-ca\"\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Create new Private CAs with a **post-quantum key algorithm** (`ML_DSA_44`, `ML_DSA_65`, or `ML_DSA_87`) and migrate workloads off legacy RSA/ECC CAs. Plan crypto-agility for your PKI so that quantum-resistant trust anchors can be rolled out before threat actors gain access to a cryptographically relevant quantum computer.",
+ "Url": "https://hub.prowler.com/check/acmpca_certificate_authority_pqc_key_algorithm"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.py b/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.py
new file mode 100644
index 0000000000..738875baee
--- /dev/null
+++ b/prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.py
@@ -0,0 +1,49 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.acmpca.acmpca_client import acmpca_client
+
+PQC_PCA_KEY_ALGORITHMS_DEFAULT = [
+ "ML_DSA_44",
+ "ML_DSA_65",
+ "ML_DSA_87",
+]
+
+
+class acmpca_certificate_authority_pqc_key_algorithm(Check):
+ """Verify that every AWS Private CA uses a post-quantum key algorithm.
+
+ A Private CA PASSES when its ``KeyAlgorithm`` belongs to the configured
+ allowlist of post-quantum signature algorithms (ML-DSA family).
+ Deleted CAs are skipped.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the check against AWS Private CAs.
+
+ Returns:
+ A list of reports with each non-deleted CA PQC key algorithm status.
+ """
+
+ findings = []
+ pqc_algorithms = acmpca_client.audit_config.get(
+ "acmpca_pqc_key_algorithms", PQC_PCA_KEY_ALGORITHMS_DEFAULT
+ )
+ for ca in acmpca_client.certificate_authorities.values():
+ if ca.status == "DELETED":
+ continue
+ report = Check_Report_AWS(metadata=self.metadata(), resource=ca)
+ algorithm = ca.key_algorithm or "<none>"
+ if ca.key_algorithm in pqc_algorithms:
+ report.status = "PASS"
+ report.status_extended = (
+ f"AWS Private CA {ca.id} uses post-quantum key algorithm "
+ f"{algorithm}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"AWS Private CA {ca.id} uses key algorithm {algorithm}, "
+ "which is not post-quantum (ML-DSA)."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/acmpca/acmpca_client.py b/prowler/providers/aws/services/acmpca/acmpca_client.py
new file mode 100644
index 0000000000..c8e22730bc
--- /dev/null
+++ b/prowler/providers/aws/services/acmpca/acmpca_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.aws.services.acmpca.acmpca_service import ACMPCA
+from prowler.providers.common.provider import Provider
+
+acmpca_client = ACMPCA(Provider.get_global_provider())
diff --git a/prowler/providers/aws/services/acmpca/acmpca_service.py b/prowler/providers/aws/services/acmpca/acmpca_service.py
new file mode 100644
index 0000000000..9c6fb77096
--- /dev/null
+++ b/prowler/providers/aws/services/acmpca/acmpca_service.py
@@ -0,0 +1,97 @@
+from __future__ import annotations
+
+from typing import Any, Dict, List
+
+from pydantic.v1 import BaseModel, Field
+
+from prowler.lib.logger import logger
+from prowler.lib.scan_filters.scan_filters import is_resource_filtered
+from prowler.providers.aws.aws_provider import AwsProvider
+from prowler.providers.aws.lib.service.service import AWSService
+
+
+class ACMPCA(AWSService):
+ """AWS Private CA service class to list certificate authorities."""
+
+ def __init__(self, provider: AwsProvider) -> None:
+ """Initialize the AWS Private CA service.
+
+ Args:
+ provider: AWS provider instance with session and audit context.
+ """
+
+ # The boto3 client identifier for AWS Private CA is "acm-pca"
+ super().__init__("acm-pca", provider)
+ self.certificate_authorities: dict[str, CertificateAuthority] = {}
+ self.__threading_call__(self._list_certificate_authorities)
+
+ def _list_certificate_authorities(self, regional_client: Any) -> None:
+ """List AWS Private CAs and their tags in a region.
+
+ Args:
+ regional_client: Regional AWS Private CA client.
+ """
+
+ logger.info("ACM PCA - Listing Certificate Authorities...")
+ try:
+ paginator = regional_client.get_paginator("list_certificate_authorities")
+ for page in paginator.paginate():
+ for ca in page.get("CertificateAuthorities", []):
+ arn = ca.get("Arn", "")
+ if not arn:
+ continue
+ if self.audit_resources and not is_resource_filtered(
+ arn, self.audit_resources
+ ):
+ continue
+ config = ca.get("CertificateAuthorityConfiguration", {})
+ tags = []
+ try:
+ tags = regional_client.list_tags(
+ CertificateAuthorityArn=arn
+ ).get("Tags", [])
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ self.certificate_authorities[arn] = CertificateAuthority(
+ arn=arn,
+ id=arn.split("/")[-1],
+ region=regional_client.region,
+ status=ca.get("Status", ""),
+ type=ca.get("Type", ""),
+ usage_mode=ca.get("UsageMode", ""),
+ key_algorithm=config.get("KeyAlgorithm", ""),
+ signing_algorithm=config.get("SigningAlgorithm", ""),
+ tags=tags,
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class CertificateAuthority(BaseModel):
+ """AWS Private Certificate Authority metadata.
+
+ Attributes:
+ arn: Certificate authority ARN.
+ id: Certificate authority identifier.
+ region: AWS region where the certificate authority exists.
+ status: Certificate authority lifecycle status.
+ type: Certificate authority type.
+ usage_mode: Certificate authority usage mode.
+ key_algorithm: Key algorithm configured for the certificate authority.
+ signing_algorithm: Signing algorithm configured for the certificate authority.
+ tags: Tags attached to the certificate authority.
+ """
+
+ arn: str
+ id: str
+ region: str
+ status: str = ""
+ type: str = ""
+ usage_mode: str = ""
+ key_algorithm: str = ""
+ signing_algorithm: str = ""
+ tags: List[Dict[str, str]] = Field(default_factory=list)
diff --git a/tests/providers/alibabacloud/services/actiontrail/__init__.py b/prowler/providers/aws/services/amplify/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/actiontrail/__init__.py
rename to prowler/providers/aws/services/amplify/__init__.py
diff --git a/tests/providers/alibabacloud/services/actiontrail/actiontrail_multi_region_enabled/__init__.py b/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/actiontrail/actiontrail_multi_region_enabled/__init__.py
rename to prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/__init__.py
diff --git a/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.metadata.json b/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.metadata.json
new file mode 100644
index 0000000000..1a5c209fcb
--- /dev/null
+++ b/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.metadata.json
@@ -0,0 +1,42 @@
+{
+ "Provider": "aws",
+ "CheckID": "amplify_app_no_secrets_in_environment",
+ "CheckTitle": "Amplify app has no sensitive credentials in environment variables or build settings",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "TTPs/Credential Access",
+ "Effects/Data Exposure",
+ "Sensitive Data Identifications/Security"
+ ],
+ "ServiceName": "amplify",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "arn:partition:amplify:region:account-id:apps/app-id",
+ "Severity": "high",
+ "ResourceType": "AwsAmplifyApp",
+ "ResourceGroup": "security",
+ "Description": "AWS Amplify apps and their branches are inspected for hardcoded secrets, such as API keys, tokens, or passwords embedded in environment variables or build settings (buildSpec).",
+ "Risk": "Plaintext secrets in Amplify app environment variables or build configurations can be viewed by anyone with read access to the Amplify console, or may leak during the build process, exposing downstream resources and integrations.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html",
+ "https://docs.prowler.com/developer-guide/secret-scanning-checks"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws amplify update-app --app-id <app-id> --environment-variables <key1=value1,key2=value2>",
+ "NativeIaC": "",
+ "Other": "1. Access the AWS Amplify console.\n2. Navigate to your app settings, choose Environment variables, and check if any secrets are stored in plaintext.\n3. For actual secrets, migrate them to environment secrets or AWS Secrets Manager / Parameter Store and reference them securely during the build phase.\n4. Clean the variables or buildSpec configuration.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Avoid storing secrets in plaintext environment variables or build specifications for AWS Amplify apps. Store sensitive settings securely in AWS Systems Manager Parameter Store or AWS Secrets Manager.",
+ "Url": "https://hub.prowler.com/check/amplify_app_no_secrets_in_environment"
+ }
+ },
+ "Categories": [
+ "secrets"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.py b/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.py
new file mode 100644
index 0000000000..33175c724f
--- /dev/null
+++ b/prowler/providers/aws/services/amplify/amplify_app_no_secrets_in_environment/amplify_app_no_secrets_in_environment.py
@@ -0,0 +1,105 @@
+import json
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.amplify.amplify_client import amplify_client
+
+
+class amplify_app_no_secrets_in_environment(Check):
+ """Check that AWS Amplify apps contain no hardcoded secrets in their environment variables or build settings."""
+
+ def execute(self) -> list[Check_Report_AWS]:
+ findings = []
+ secrets_ignore_patterns = amplify_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = amplify_client.audit_config.get("secrets_validate", False)
+ apps = list(amplify_client.apps.values())
+ line_context_by_app = {}
+
+ payloads_list = []
+ for app_index, app in enumerate(apps):
+ payload, line_context = _build_app_payload(app)
+ line_context_by_app[app_index] = line_context
+ if payload:
+ payloads_list.append((app_index, payload))
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads_list,
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for app_index, app in enumerate(apps):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=app)
+ report.resource_tags = app.tags
+ report.status = "PASS"
+ report.status_extended = f"No secrets found in Amplify app {app.name} environment variables or build settings."
+
+ line_context = line_context_by_app.get(app_index, {})
+ if line_context:
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Amplify app {app.name} environment variables "
+ f"for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ detect_secrets_output = batch_results.get(app_index)
+ if detect_secrets_output:
+ secrets_string = ", ".join(
+ [
+ f"{secret['type']} in {line_context.get(secret['line_number'], 'environment variables/build settings')}"
+ for secret in detect_secrets_output
+ ]
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Potential {'secrets' if len(detect_secrets_output) > 1 else 'secret'} "
+ f"found in Amplify app {app.name} environment variables or build settings -> {secrets_string}."
+ )
+ annotate_verified_secrets(report, detect_secrets_output)
+
+ findings.append(report)
+ return findings
+
+
+def _build_app_payload(app) -> tuple[str, dict[int, str]]:
+ """Build a line-oriented scan payload and map each line to a field context."""
+ lines = []
+ line_context = {}
+
+ def add_line(context: str, value: str) -> None:
+ if value is None:
+ return
+ lines.append(json.dumps({context: value}))
+ line_context[len(lines)] = context
+
+ # App environment variables
+ for var_name, var_value in app.environment_variables.items():
+ add_line(f"app environment variable '{var_name}'", var_value)
+
+ # App buildSpec
+ if app.build_spec:
+ for idx, line in enumerate(app.build_spec.splitlines(), start=1):
+ add_line(f"app buildSpec line {idx}", line)
+
+ # Branch environment variables
+ for branch in app.branches:
+ for var_name, var_value in branch.environment_variables.items():
+ add_line(
+ f"branch '{branch.name}' environment variable '{var_name}'", var_value
+ )
+
+ return "\n".join(lines), line_context
diff --git a/prowler/providers/aws/services/amplify/amplify_client.py b/prowler/providers/aws/services/amplify/amplify_client.py
new file mode 100644
index 0000000000..9d69c68424
--- /dev/null
+++ b/prowler/providers/aws/services/amplify/amplify_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.aws.services.amplify.amplify_service import Amplify
+from prowler.providers.common.provider import Provider
+
+amplify_client = Amplify(Provider.get_global_provider())
diff --git a/prowler/providers/aws/services/amplify/amplify_service.py b/prowler/providers/aws/services/amplify/amplify_service.py
new file mode 100644
index 0000000000..1a80f9ebd3
--- /dev/null
+++ b/prowler/providers/aws/services/amplify/amplify_service.py
@@ -0,0 +1,97 @@
+from botocore.exceptions import ClientError
+from pydantic.v1 import BaseModel, Field
+
+from prowler.lib.logger import logger
+from prowler.lib.scan_filters.scan_filters import is_resource_filtered
+from prowler.providers.aws.lib.service.service import AWSService
+
+
+class Branch(BaseModel):
+ """Represents an AWS Amplify App Branch."""
+
+ name: str
+ arn: str
+ environment_variables: dict = Field(default_factory=dict)
+
+
+class App(BaseModel):
+ """Represents an AWS Amplify App."""
+
+ id: str
+ name: str
+ arn: str
+ region: str
+ environment_variables: dict = Field(default_factory=dict)
+ build_spec: str = ""
+ branches: list[Branch] = Field(default_factory=list)
+ tags: list[dict] = Field(default_factory=list)
+
+
+class Amplify(AWSService):
+ """AWS Amplify service class."""
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ self.apps = {}
+ self.__threading_call__(self._list_apps)
+ if self.apps:
+ self.__threading_call__(self._list_branches, self.apps.values())
+
+ def _list_apps(self, regional_client) -> None:
+ logger.info("Amplify - Listing apps...")
+ try:
+ list_apps_paginator = regional_client.get_paginator("list_apps")
+ for page in list_apps_paginator.paginate():
+ for app in page.get("apps", []):
+ app_id = app.get("appId")
+ app_name = app.get("name")
+ app_arn = app.get("appArn")
+ if not self.audit_resources or is_resource_filtered(
+ app_arn, self.audit_resources
+ ):
+ tags = app.get("tags", {})
+ tags_list = [tags] if tags else []
+ self.apps[app_arn] = App(
+ id=app_id,
+ name=app_name,
+ arn=app_arn,
+ region=regional_client.region,
+ environment_variables=app.get("environmentVariables", {}),
+ build_spec=app.get("buildSpec", ""),
+ tags=tags_list,
+ )
+ except ClientError as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _list_branches(self, app: App) -> None:
+ logger.info(f"Amplify - Listing branches for app {app.name}...")
+ try:
+ regional_client = self.regional_clients[app.region]
+ list_branches_paginator = regional_client.get_paginator("list_branches")
+ for page in list_branches_paginator.paginate(appId=app.id):
+ for branch in page.get("branches", []):
+ branch_name = branch.get("branchName")
+ branch_arn = branch.get("branchArn")
+ app.branches.append(
+ Branch(
+ name=branch_name,
+ arn=branch_arn,
+ environment_variables=branch.get(
+ "environmentVariables", {}
+ ),
+ )
+ )
+ except ClientError as error:
+ logger.error(
+ f"{app.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{app.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
diff --git a/tests/providers/alibabacloud/services/actiontrail/actiontrail_oss_bucket_not_publicly_accessible/__init__.py b/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/actiontrail/actiontrail_oss_bucket_not_publicly_accessible/__init__.py
rename to prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/__init__.py
diff --git a/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.metadata.json b/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.metadata.json
new file mode 100644
index 0000000000..276f6e1741
--- /dev/null
+++ b/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.metadata.json
@@ -0,0 +1,41 @@
+{
+ "Provider": "aws",
+ "CheckID": "apigateway_domain_name_pqc_tls_enabled",
+ "CheckTitle": "API Gateway custom domain names use a post-quantum TLS security policy",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "apigateway",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsApiGatewayDomainName",
+ "ResourceGroup": "network",
+ "Description": "**API Gateway custom domain names** for REST APIs are assessed for use of a **post-quantum (PQ) TLS security policy** such as `SecurityPolicy_TLS13_1_2_PQ_2025_09`. Custom domains with legacy policies such as `TLS_1_0` or `TLS_1_2` lack hybrid ML-KEM key exchange, leaving captured traffic vulnerable to future quantum decryption.",
+ "Risk": "Without a PQ-ready TLS policy, traffic to API Gateway custom domains captured today can be decrypted once a **cryptographically relevant quantum computer** exists (**harvest-now, decrypt-later** attack). This threatens long-term **confidentiality** of API payloads, credentials, and bearer tokens.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-custom-domain-tls-version.html",
+ "https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-security-policies-list.html",
+ "https://aws.amazon.com/security/post-quantum-cryptography/",
+ "https://csrc.nist.gov/projects/post-quantum-cryptography"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws apigateway update-domain-name --domain-name <domain_name> --patch-operations op=replace,path=/securityPolicy,value=SecurityPolicy_TLS13_1_2_PQ_2025_09",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::ApiGateway::DomainName\n Properties:\n DomainName: api.example.com\n RegionalCertificateArn: <example_certificate_arn>\n SecurityPolicy: SecurityPolicy_TLS13_1_2_PQ_2025_09 # FIX: enhanced post-quantum security policy\n EndpointConfiguration:\n Types:\n - REGIONAL\n```",
+ "Other": "1. In the AWS Console, go to API Gateway > Custom domain names\n2. Select the custom domain and choose Edit on Domain name configurations\n3. Set Security policy to SecurityPolicy_TLS13_1_2_PQ_2025_09 (post-quantum) and Endpoint access mode to Strict\n4. Save the changes",
+ "Terraform": "```hcl\nresource \"aws_api_gateway_domain_name\" \"<example_resource_name>\" {\n domain_name = \"api.example.com\"\n regional_certificate_arn = \"<example_certificate_arn>\"\n security_policy = \"SecurityPolicy_TLS13_1_2_PQ_2025_09\" # FIX: enhanced post-quantum security policy\n endpoint_configuration {\n types = [\"REGIONAL\"]\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Migrate every API Gateway custom domain name to an **enhanced post-quantum TLS policy** such as `SecurityPolicy_TLS13_1_2_PQ_2025_09` that enables hybrid ML-KEM key exchange. Note that you must also enable Strict endpoint access mode and that mutual TLS is not supported on enhanced policies. Review allowed policies regularly as AWS publishes new PQ-ready options.",
+ "Url": "https://hub.prowler.com/check/apigateway_domain_name_pqc_tls_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "API Gateway HTTP and WebSocket APIs only support the legacy TLS_1_2 security policy and therefore cannot use post-quantum TLS today; this check evaluates REST API custom domain names only."
+}
diff --git a/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.py b/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.py
new file mode 100644
index 0000000000..d9c2d071f9
--- /dev/null
+++ b/prowler/providers/aws/services/apigateway/apigateway_domain_name_pqc_tls_enabled/apigateway_domain_name_pqc_tls_enabled.py
@@ -0,0 +1,55 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.apigateway.apigateway_client import (
+ apigateway_client,
+)
+
+PQC_APIGATEWAY_POLICIES_DEFAULT = [
+ "SecurityPolicy_TLS13_1_2_FIPS_PFS_PQ_2025_09",
+ "SecurityPolicy_TLS13_1_2_PFS_PQ_2025_09",
+ "SecurityPolicy_TLS13_1_2_PQ_2025_09",
+]
+
+
+def _get_allowed_policies(configured_policies: object) -> list[str]:
+ if not isinstance(configured_policies, list):
+ return PQC_APIGATEWAY_POLICIES_DEFAULT
+
+ return configured_policies
+
+
+class apigateway_domain_name_pqc_tls_enabled(Check):
+ """Verify that every API Gateway custom domain name uses a post-quantum TLS policy.
+
+ A custom domain name PASSES when its ``securityPolicy`` belongs to the
+ configured allowlist of enhanced post-quantum policies.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the API Gateway custom domain post-quantum TLS check.
+
+ Returns:
+ A list of reports for API Gateway custom domain names and their
+ post-quantum TLS policy compliance status.
+ """
+ findings = []
+ pqc_policies = _get_allowed_policies(
+ apigateway_client.audit_config.get("apigateway_pqc_tls_allowed_policies")
+ )
+ for domain in apigateway_client.domain_names:
+ report = Check_Report_AWS(metadata=self.metadata(), resource=domain)
+ policy = domain.security_policy or "<none>"
+ if domain.security_policy in pqc_policies:
+ report.status = "PASS"
+ report.status_extended = (
+ f"API Gateway custom domain {domain.name} uses post-quantum "
+ f"TLS policy {policy}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"API Gateway custom domain {domain.name} uses TLS policy "
+ f"{policy}, which is not in the post-quantum allowlist."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/cs/__init__.py b/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/__init__.py
rename to prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/__init__.py
diff --git a/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.metadata.json b/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.metadata.json
new file mode 100644
index 0000000000..d0866175b9
--- /dev/null
+++ b/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "aws",
+ "CheckID": "apigateway_restapi_no_secrets_in_stage_variables",
+ "CheckTitle": "API Gateway REST API stage variables should not contain secrets",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices"
+ ],
+ "ServiceName": "apigateway",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "arn:aws:apigateway:region::/restapis/api-id/stages/stage-name",
+ "Severity": "high",
+ "ResourceType": "AwsApiGatewayStage",
+ "ResourceGroup": "security",
+ "Description": "Checks API Gateway REST API stage variables for hardcoded secrets such as passwords, API keys, and tokens. Stage variables should reference AWS Secrets Manager or Parameter Store rather than containing plaintext credentials.",
+ "Risk": "Hardcoded secrets in stage variables are stored in plaintext in the AWS control plane and are visible to anyone with read access to the API Gateway configuration. This can lead to unauthorized access, credential theft, and lateral movement across systems.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/secretsmanager/latest/userguide/integrating_how-services-use-secrets_api-gateway.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws apigateway update-stage --rest-api-id <api-id> --stage-name <stage-name> --patch-operations op=remove,path=/variables/<variable-name>",
+ "NativeIaC": "",
+ "Other": "1. Open AWS Console > API Gateway\n2. Select the REST API and stage\n3. Go to Stage Variables tab\n4. Remove any variables containing plaintext secrets\n5. Reference secrets using AWS Secrets Manager integration instead",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove hardcoded secrets from API Gateway stage variables. Use AWS Secrets Manager or Parameter Store to manage credentials and retrieve them at runtime using Lambda authorizers or integration request mapping templates.",
+ "Url": "https://hub.prowler.com/check/apigateway_restapi_no_secrets_in_stage_variables"
+ }
+ },
+ "Categories": [
+ "secrets"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Infrastructure Protection"
+}
diff --git a/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.py b/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.py
new file mode 100644
index 0000000000..490057a5ed
--- /dev/null
+++ b/prowler/providers/aws/services/apigateway/apigateway_restapi_no_secrets_in_stage_variables/apigateway_restapi_no_secrets_in_stage_variables.py
@@ -0,0 +1,89 @@
+import json
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.apigateway.apigateway_client import (
+ apigateway_client,
+)
+
+
+class apigateway_restapi_no_secrets_in_stage_variables(Check):
+ """Check that API Gateway REST API stage variables contain no hardcoded secrets."""
+
+ def execute(self) -> list[Check_Report_AWS]:
+ findings = []
+ secrets_ignore_patterns = apigateway_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = apigateway_client.audit_config.get("secrets_validate", False)
+
+ # Collect one payload per stage (its variables) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per stage.
+ # Findings are keyed by (rest_api index, stage index).
+ def payloads():
+ for api_index, rest_api in enumerate(apigateway_client.rest_apis):
+ for stage_index, stage in enumerate(rest_api.stages):
+ if stage.variables:
+ yield (api_index, stage_index), json.dumps(
+ stage.variables, indent=2
+ )
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for api_index, rest_api in enumerate(apigateway_client.rest_apis):
+ for stage_index, stage in enumerate(rest_api.stages):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=rest_api)
+ report.resource_arn = stage.arn
+ report.resource_id = f"{rest_api.name}/{stage.name}"
+ report.status = "PASS"
+ report.status_extended = (
+ f"No secrets found in stage variables of API Gateway "
+ f"REST API {rest_api.name} stage {stage.name}."
+ )
+
+ if stage.variables:
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan stage variables of API Gateway REST API "
+ f"{rest_api.name} stage {stage.name} for secrets: "
+ f"{scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ detect_secrets_output = batch_results.get((api_index, stage_index))
+ if detect_secrets_output:
+ variable_names = list(stage.variables.keys())
+ secrets_string = ", ".join(
+ [
+ f"{secret['type']} in variable "
+ f"{variable_names[secret['line_number'] - 2]}"
+ for secret in detect_secrets_output
+ ]
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Potential "
+ f"{'secrets' if len(detect_secrets_output) > 1 else 'secret'} "
+ f"found in stage variables of API Gateway REST API "
+ f"{rest_api.name} stage {stage.name} -> {secrets_string}."
+ )
+ annotate_verified_secrets(report, detect_secrets_output)
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/apigateway/apigateway_service.py b/prowler/providers/aws/services/apigateway/apigateway_service.py
index 4f887a2da8..94f7d86b8d 100644
--- a/prowler/providers/aws/services/apigateway/apigateway_service.py
+++ b/prowler/providers/aws/services/apigateway/apigateway_service.py
@@ -1,4 +1,4 @@
-from typing import Optional
+from typing import Any, Optional
from botocore.exceptions import ClientError
from pydantic.v1 import BaseModel
@@ -13,12 +13,45 @@ class APIGateway(AWSService):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
self.rest_apis = []
+ self.domain_names = []
self.__threading_call__(self._get_rest_apis)
+ self.__threading_call__(self._get_domain_names)
self._get_authorizers()
self._get_rest_api()
self._get_stages()
self._get_resources()
+ def _get_domain_names(self, regional_client: Any) -> None:
+ """Get API Gateway custom domain names for a regional client.
+
+ Args:
+ regional_client: Regional API Gateway boto3 client used to list
+ custom domain names.
+ """
+ logger.info("APIGateway - Getting custom domain names...")
+ try:
+ paginator = regional_client.get_paginator("get_domain_names")
+ for page in paginator.paginate():
+ for item in page.get("items", []):
+ domain_name = item.get("domainName", "")
+ arn = f"arn:{self.audited_partition}:apigateway:{regional_client.region}::/domainnames/{domain_name}"
+ if not self.audit_resources or (
+ is_resource_filtered(arn, self.audit_resources)
+ ):
+ self.domain_names.append(
+ DomainName(
+ name=domain_name,
+ arn=arn,
+ region=regional_client.region,
+ security_policy=item.get("securityPolicy", ""),
+ tags=[item.get("tags", {})],
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _get_rest_apis(self, regional_client):
logger.info("APIGateway - Getting Rest APIs...")
try:
@@ -146,6 +179,7 @@ class APIGateway(AWSService):
tracing_enabled=tracing_enabled,
cache_enabled=cache_enabled,
cache_data_encrypted=cache_data_encrypted,
+ variables=stage.get("variables", {}),
)
)
except ClientError as error:
@@ -232,6 +266,7 @@ class Stage(BaseModel):
tracing_enabled: Optional[bool] = None
cache_enabled: Optional[bool] = None
cache_data_encrypted: Optional[bool] = None
+ variables: Optional[dict] = {}
class PathResourceMethods(BaseModel):
@@ -249,3 +284,21 @@ class RestAPI(BaseModel):
stages: list[Stage] = []
tags: Optional[list] = []
resources: list[PathResourceMethods] = []
+
+
+class DomainName(BaseModel):
+ """API Gateway custom domain name metadata.
+
+ Attributes:
+ name: Custom domain name.
+ arn: Custom domain name ARN.
+ region: AWS region where the custom domain name exists.
+ security_policy: TLS security policy configured for the custom domain.
+ tags: Custom domain tags.
+ """
+
+ name: str
+ arn: str
+ region: str
+ security_policy: str = ""
+ tags: Optional[list] = []
diff --git a/prowler/providers/aws/services/autoscaling/autoscaling_find_secrets_ec2_launch_configuration/autoscaling_find_secrets_ec2_launch_configuration.py b/prowler/providers/aws/services/autoscaling/autoscaling_find_secrets_ec2_launch_configuration/autoscaling_find_secrets_ec2_launch_configuration.py
index 6595b71085..dbe6fc534c 100644
--- a/prowler/providers/aws/services/autoscaling/autoscaling_find_secrets_ec2_launch_configuration/autoscaling_find_secrets_ec2_launch_configuration.py
+++ b/prowler/providers/aws/services/autoscaling/autoscaling_find_secrets_ec2_launch_configuration/autoscaling_find_secrets_ec2_launch_configuration.py
@@ -4,7 +4,11 @@ from base64 import b64decode
from prowler.config.config import encoding_format_utf_8
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.lib.logger import logger
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.autoscaling.autoscaling_client import (
autoscaling_client,
)
@@ -16,13 +20,19 @@ class autoscaling_find_secrets_ec2_launch_configuration(Check):
secrets_ignore_patterns = autoscaling_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for (
- configuration_arn,
- configuration,
- ) in autoscaling_client.launch_configurations.items():
- report = Check_Report_AWS(metadata=self.metadata(), resource=configuration)
+ validate = autoscaling_client.audit_config.get("secrets_validate", False)
+ configurations = list(autoscaling_client.launch_configurations.values())
- if configuration.user_data:
+ # Collect the decoded User Data of each launch configuration and scan it
+ # all in batched Kingfisher invocations instead of one subprocess each.
+ # Configurations whose User Data cannot be decoded are undecodable (no report),
+ # matching the original per-resource behavior.
+ undecodable = set()
+
+ def payloads():
+ for index, configuration in enumerate(configurations):
+ if not configuration.user_data:
+ continue
user_data = b64decode(configuration.user_data)
try:
if user_data[0:2] == b"\x1f\x8b": # GZIP magic number
@@ -35,24 +45,46 @@ class autoscaling_find_secrets_ec2_launch_configuration(Check):
logger.warning(
f"{configuration.region} -- Unable to decode user data in autoscaling launch configuration {configuration.name}: {error}"
)
+ undecodable.add(index)
continue
except Exception as error:
logger.error(
f"{configuration.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ undecodable.add(index)
continue
+ yield index, user_data
- has_secrets = detect_secrets_scan(
- data=user_data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=autoscaling_client.audit_config.get(
- "detect_secrets_plugins"
- ),
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, configuration in enumerate(configurations):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=configuration)
+
+ if scan_error and configuration.user_data:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan autoscaling {configuration.name} User Data for "
+ f"secrets: {scan_error}; manual review is required."
)
+ findings.append(report)
+ continue
+ if index in undecodable:
+ report.status = "MANUAL"
+ report.status_extended = f"Could not decode User Data for autoscaling {configuration.name}; manual review is required to scan for secrets."
+ elif configuration.user_data:
+ has_secrets = batch_results.get(index)
if has_secrets:
report.status = "FAIL"
report.status_extended = f"Potential secret found in autoscaling {configuration.name} User Data."
+ annotate_verified_secrets(report, has_secrets)
else:
report.status = "PASS"
report.status_extended = f"No secrets found in autoscaling {configuration.name} User Data."
diff --git a/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_code/awslambda_function_no_secrets_in_code.py b/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_code/awslambda_function_no_secrets_in_code.py
index 51c56a2011..d4f3010903 100644
--- a/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_code/awslambda_function_no_secrets_in_code.py
+++ b/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_code/awslambda_function_no_secrets_in_code.py
@@ -1,65 +1,120 @@
+import fnmatch
import os
import tempfile
+from collections import defaultdict
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.awslambda.awslambda_client import awslambda_client
class awslambda_function_no_secrets_in_code(Check):
def execute(self):
findings = []
- if awslambda_client.functions:
- secrets_ignore_patterns = awslambda_client.audit_config.get(
- "secrets_ignore_patterns", []
- )
+ if not awslambda_client.functions:
+ return findings
+
+ secrets_ignore_patterns = awslambda_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ # Glob patterns of file names inside the deployment package to skip
+ # when scanning for secrets (e.g. "*.deps.json" for .NET Lambdas).
+ secrets_ignore_files = (
+ awslambda_client.audit_config.get("secrets_ignore_files", []) or []
+ )
+ validate = awslambda_client.audit_config.get("secrets_validate", False)
+
+ # Scan files of every function's package in batched
+ # Kingfisher invocations instead of one subprocess per file per function.
+ # Each package is extracted one at a time and its files are
+ # read (byte-faithfully via latin-1) before the extraction is released,
+ # so only a single package is on disk at a time. Findings are keyed by
+ # (function index, package-relative file name) so they can be grouped
+ # back per function.
+ functions_with_code = []
+
+ def code_payloads():
for function, function_code in awslambda_client._get_function_code():
- if function_code:
- report = Check_Report_AWS(
- metadata=self.metadata(), resource=function
- )
-
- report.status = "PASS"
- report.status_extended = (
- f"No secrets found in Lambda function {function.name} code."
- )
- with tempfile.TemporaryDirectory() as tmp_dir_name:
- function_code.code_zip.extractall(tmp_dir_name)
- # List all files
- files_in_zip = next(os.walk(tmp_dir_name))[2]
- secrets_findings = []
- for file in files_in_zip:
- detect_secrets_output = detect_secrets_scan(
- file=f"{tmp_dir_name}/{file}",
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=awslambda_client.audit_config.get(
- "detect_secrets_plugins",
- ),
+ if not function_code:
+ continue
+ index = len(functions_with_code)
+ functions_with_code.append(function)
+ with tempfile.TemporaryDirectory() as tmp_dir_name:
+ function_code.code_zip.extractall(tmp_dir_name)
+ for root, _, files in os.walk(tmp_dir_name):
+ for file_name in files:
+ file_path = os.path.join(root, file_name)
+ relative_file_path = os.path.relpath(
+ file_path, tmp_dir_name
)
- if detect_secrets_output:
- for (
- secret
- ) in (
- detect_secrets_output
- ): # Appears that only 1 file is being scanned at a time, so could rework this
- output_file_name = secret["filename"].replace(
- f"{tmp_dir_name}/", ""
- )
- secrets_string = ", ".join(
- [
- f"{secret['type']} on line {secret['line_number']}"
- for secret in detect_secrets_output
- ]
- )
- secrets_findings.append(
- f"{output_file_name}: {secrets_string}"
- )
+ if any(
+ fnmatch.fnmatch(relative_file_path, pattern)
+ for pattern in secrets_ignore_files
+ ):
+ continue
+ try:
+ with open(file_path, "rb") as code_file:
+ content = code_file.read().decode("latin-1")
+ except Exception:
+ continue
+ yield (index, relative_file_path), content
- if secrets_findings:
- final_output_string = "; ".join(secrets_findings)
- report.status = "FAIL"
- report.status_extended = f"Potential {'secrets' if len(secrets_findings) > 1 else 'secret'} found in Lambda function {function.name} code -> {final_output_string}."
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ code_payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
- findings.append(report)
+ if scan_error:
+ # The scan failed before any function's code could be cleared. Report
+ # MANUAL for every function rather than risk a false PASS.
+ for function in awslambda_client.functions.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=function)
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Lambda function {function.name} code for "
+ f"secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ return findings
+
+ findings_by_function = defaultdict(dict)
+ for (index, file_name), file_findings in batch_results.items():
+ findings_by_function[index][file_name] = file_findings
+
+ for index, function in enumerate(functions_with_code):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=function)
+ report.status = "PASS"
+ report.status_extended = (
+ f"No secrets found in Lambda function {function.name} code."
+ )
+
+ files_with_secrets = findings_by_function.get(index)
+ if files_with_secrets:
+ all_secrets = []
+ secrets_findings = []
+ for file_name, file_findings in files_with_secrets.items():
+ all_secrets.extend(file_findings)
+ secrets_string = ", ".join(
+ f"{secret['type']} on line {secret['line_number']}"
+ for secret in file_findings
+ )
+ secrets_findings.append(f"{file_name}: {secrets_string}")
+
+ final_output_string = "; ".join(secrets_findings)
+ report.status = "FAIL"
+ report.status_extended = f"Potential {'secrets' if len(secrets_findings) > 1 else 'secret'} found in Lambda function {function.name} code -> {final_output_string}."
+ annotate_verified_secrets(report, all_secrets)
+
+ findings.append(report)
return findings
diff --git a/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_variables/awslambda_function_no_secrets_in_variables.py b/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_variables/awslambda_function_no_secrets_in_variables.py
index 9448b0239f..065cc7a9b9 100644
--- a/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_variables/awslambda_function_no_secrets_in_variables.py
+++ b/prowler/providers/aws/services/awslambda/awslambda_function_no_secrets_in_variables/awslambda_function_no_secrets_in_variables.py
@@ -1,7 +1,11 @@
import json
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.awslambda.awslambda_client import awslambda_client
@@ -11,7 +15,30 @@ class awslambda_function_no_secrets_in_variables(Check):
secrets_ignore_patterns = awslambda_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for function in awslambda_client.functions.values():
+ validate = awslambda_client.audit_config.get("secrets_validate", False)
+ functions = list(awslambda_client.functions.values())
+
+ # Scan every function's environment variables in batched Kingfisher
+ # invocations instead of one subprocess per function. Payloads are
+ # yielded lazily so only a chunk is held/written at a time, which matters
+ # for accounts with very large numbers of Lambda functions.
+ def environment_payloads():
+ for index, function in enumerate(functions):
+ if function.environment:
+ yield index, json.dumps(function.environment, indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ environment_payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, function in enumerate(functions):
report = Check_Report_AWS(metadata=self.metadata(), resource=function)
report.status = "PASS"
@@ -20,17 +47,17 @@ class awslambda_function_no_secrets_in_variables(Check):
)
if function.environment:
- detect_secrets_output = detect_secrets_scan(
- data=json.dumps(function.environment, indent=2),
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=awslambda_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
- original_env_vars = []
- for name, value in function.environment.items():
- original_env_vars.append(name)
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Lambda function {function.name} variables "
+ f"for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
+ original_env_vars = list(function.environment.keys())
secrets_string = ", ".join(
[
f"{secret['type']} in variable {original_env_vars[secret['line_number'] - 2]}"
@@ -39,6 +66,7 @@ class awslambda_function_no_secrets_in_variables(Check):
)
report.status = "FAIL"
report.status_extended = f"Potential secret found in Lambda function {function.name} variables -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
findings.append(report)
diff --git a/prowler/providers/aws/services/awslambda/awslambda_service.py b/prowler/providers/aws/services/awslambda/awslambda_service.py
index 433a5ab588..ac90e9fb11 100644
--- a/prowler/providers/aws/services/awslambda/awslambda_service.py
+++ b/prowler/providers/aws/services/awslambda/awslambda_service.py
@@ -10,6 +10,10 @@ from botocore.client import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ limit_resources,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
@@ -18,8 +22,16 @@ class Lambda(AWSService):
def __init__(self, provider):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
+ # Functions are listed first, then trimmed to the subset selected for
+ # analysis before expensive per-function detail is hydrated.
self.functions = {}
+ self.security_groups_in_use = set()
+ self.regions_with_functions = set()
+ self.function_limit = get_resource_scan_limit(
+ self.audit_config, "max_lambda_functions"
+ )
self.__threading_call__(self._list_functions)
+ self._select_functions_for_analysis()
self._list_tags_for_resource()
self.__threading_call__(self._get_policy)
self.__threading_call__(self._get_function_url_config)
@@ -30,24 +42,29 @@ class Lambda(AWSService):
try:
list_functions_paginator = regional_client.get_paginator("list_functions")
for page in list_functions_paginator.paginate():
- for function in page["Functions"]:
- if not self.audit_resources or (
- is_resource_filtered(
- function["FunctionArn"], self.audit_resources
- )
+ for function in page.get("Functions", []):
+ if not self.audit_resources or is_resource_filtered(
+ function["FunctionArn"], self.audit_resources
):
lambda_name = function["FunctionName"]
lambda_arn = function["FunctionArn"]
vpc_config = function.get("VpcConfig", {})
+ security_groups = vpc_config.get("SecurityGroupIds", [])
+ self.security_groups_in_use.update(security_groups)
+ self.regions_with_functions.add(regional_client.region)
# We must use the Lambda ARN as the dict key since we could have Lambdas in different regions with the same name
self.functions[lambda_arn] = Function(
name=lambda_name,
arn=lambda_arn,
- security_groups=vpc_config.get("SecurityGroupIds", []),
+ security_groups=security_groups,
vpc_id=vpc_config.get("VpcId"),
subnet_ids=set(vpc_config.get("SubnetIds", [])),
region=regional_client.region,
)
+ if "LastModified" in function:
+ self.functions[lambda_arn].last_modified = function[
+ "LastModified"
+ ]
if "Runtime" in function:
self.functions[lambda_arn].runtime = function["Runtime"]
if "Environment" in function:
@@ -76,26 +93,61 @@ class Lambda(AWSService):
f" {error}"
)
+ def _select_functions_for_analysis(self):
+ self.functions = {
+ function.arn: function
+ for function in limit_resources(
+ sorted(
+ self.functions.values(),
+ key=lambda f: f.last_modified or "",
+ reverse=True,
+ ),
+ self.function_limit,
+ )
+ }
+
def _list_event_source_mappings(self, regional_client):
logger.info("Lambda - Listing Event Source Mappings...")
try:
paginator = regional_client.get_paginator("list_event_source_mappings")
- for page in paginator.paginate():
- for mapping in page.get("EventSourceMappings", []):
- function_arn = mapping.get("FunctionArn", "")
- # Normalise to unqualified ARN (strip :qualifier suffix if present)
- base_arn = ":".join(function_arn.split(":")[:7])
- if base_arn not in self.functions:
- continue
- self.functions[base_arn].event_source_mappings.append(
- EventSourceMapping(
- uuid=mapping["UUID"],
- event_source_arn=mapping.get("EventSourceArn", ""),
- state=mapping.get("State", ""),
- batch_size=mapping.get("BatchSize"),
- starting_position=mapping.get("StartingPosition"),
+ if not self.function_limit:
+ for page in paginator.paginate():
+ self._add_event_source_mappings(page.get("EventSourceMappings", []))
+ return
+
+ for function in self.functions.values():
+ if function.region != regional_client.region:
+ continue
+ try:
+ for page in paginator.paginate(FunctionName=function.name):
+ self._add_event_source_mappings(
+ page.get("EventSourceMappings", [])
)
- )
+ except ClientError as error:
+ if (
+ error.response.get("Error", {}).get("Code")
+ == "InvalidParameterValueException"
+ ):
+ logger.warning(
+ f"{function.region} --"
+ f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
+ f" {error}"
+ )
+ else:
+ logger.error(
+ f"{function.region} --"
+ f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
+ f" {error}"
+ )
+ raise
+ except ClientError as error:
+ if self.function_limit:
+ raise
+ logger.error(
+ f"{regional_client.region} --"
+ f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
+ f" {error}"
+ )
except Exception as error:
logger.error(
f"{regional_client.region} --"
@@ -103,6 +155,23 @@ class Lambda(AWSService):
f" {error}"
)
+ def _add_event_source_mappings(self, event_source_mappings):
+ for mapping in event_source_mappings:
+ function_arn = mapping.get("FunctionArn", "")
+ # Normalise to unqualified ARN (strip :qualifier suffix if present)
+ base_arn = ":".join(function_arn.split(":")[:7])
+ if base_arn not in self.functions:
+ continue
+ self.functions[base_arn].event_source_mappings.append(
+ EventSourceMapping(
+ uuid=mapping["UUID"],
+ event_source_arn=mapping.get("EventSourceArn", ""),
+ state=mapping.get("State", ""),
+ batch_size=mapping.get("BatchSize"),
+ starting_position=mapping.get("StartingPosition"),
+ )
+ )
+
def _get_function_code(self):
logger.info("Lambda - Getting Function Code...")
# Use a thread pool handle the queueing and execution of the _fetch_function_code tasks, up to max_workers tasks concurrently.
@@ -158,7 +227,6 @@ class Lambda(AWSService):
except ClientError as e:
if e.response["Error"]["Code"] == "ResourceNotFoundException":
self.functions[function.arn].policy = {}
-
except Exception as error:
logger.error(
f"{regional_client.region} --"
@@ -187,7 +255,6 @@ class Lambda(AWSService):
except ClientError as e:
if e.response["Error"]["Code"] == "ResourceNotFoundException":
self.functions[function.arn].url_config = None
-
except Exception as error:
logger.error(
f"{regional_client.region} --"
@@ -206,10 +273,9 @@ class Lambda(AWSService):
except ClientError as e:
if e.response["Error"]["Code"] == "ResourceNotFoundException":
function.tags = []
-
except Exception as error:
logger.error(
- f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"{function.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
@@ -259,6 +325,7 @@ class Function(BaseModel):
name: str
arn: str
security_groups: list
+ last_modified: Optional[str] = None
runtime: Optional[str] = None
environment: Optional[dict] = None
region: str
diff --git a/prowler/providers/aws/services/backup/backup_service.py b/prowler/providers/aws/services/backup/backup_service.py
index 4320d42c0b..ddacc9e6d2 100644
--- a/prowler/providers/aws/services/backup/backup_service.py
+++ b/prowler/providers/aws/services/backup/backup_service.py
@@ -5,6 +5,10 @@ from botocore.client import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ limit_resources,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
@@ -27,8 +31,14 @@ class Backup(AWSService):
self.__threading_call__(self._list_backup_report_plans)
self.protected_resources = []
self.__threading_call__(self._list_backup_selections)
+ # Recovery points are listed first, then only the selected subset is
+ # tagged and exposed for checks.
self.recovery_points = []
- self.__threading_call__(self._list_recovery_points)
+ self.recovery_point_limit = get_resource_scan_limit(
+ self.audit_config, "max_backup_recovery_points"
+ )
+ self.__threading_call__(self._list_recovery_points, self.backup_vaults or [])
+ self._select_recovery_points_for_analysis()
self.__threading_call__(self._list_tags, self.recovery_points)
def _list_backup_vaults(self, regional_client):
@@ -183,40 +193,63 @@ class Backup(AWSService):
f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- def _list_recovery_points(self, regional_client):
+ def _list_recovery_points(self, backup_vault=None):
logger.info("Backup - Listing Recovery Points...")
+ if backup_vault is None:
+ for vault in self.backup_vaults or []:
+ self._list_recovery_points(vault)
+ return
+
try:
- if self.backup_vaults:
- for backup_vault in self.backup_vaults:
- paginator = regional_client.get_paginator(
- "list_recovery_points_by_backup_vault"
- )
- for page in paginator.paginate(BackupVaultName=backup_vault.name):
- for recovery_point in page.get("RecoveryPoints", []):
- arn = recovery_point.get("RecoveryPointArn")
- if arn:
- self.recovery_points.append(
- RecoveryPoint(
- arn=arn,
- id=arn.split(":")[-1],
- backup_vault_name=backup_vault.name,
- encrypted=recovery_point.get(
- "IsEncrypted", False
- ),
- backup_vault_region=backup_vault.region,
- region=regional_client.region,
- tags=[],
- )
- )
+ regional_client = self.regional_clients[backup_vault.region]
+ paginator = regional_client.get_paginator(
+ "list_recovery_points_by_backup_vault"
+ )
+ for page in paginator.paginate(BackupVaultName=backup_vault.name):
+ for recovery_point in page.get("RecoveryPoints", []):
+ arn = recovery_point.get("RecoveryPointArn")
+ if arn:
+ rp = RecoveryPoint(
+ arn=arn,
+ id=arn.split(":")[-1],
+ backup_vault_name=backup_vault.name,
+ encrypted=recovery_point.get("IsEncrypted", False),
+ creation_date=recovery_point.get("CreationDate"),
+ backup_vault_region=backup_vault.region,
+ region=backup_vault.region,
+ tags=[],
+ )
+ self.recovery_points.append(rp)
except ClientError as error:
logger.error(
- f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"{backup_vault.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
except Exception as error:
logger.error(
- f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"{backup_vault.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _select_recovery_points_for_analysis(self):
+ self.recovery_points = list(
+ limit_resources(
+ sorted(
+ self.recovery_points,
+ key=lambda rp: (
+ (
+ -rp.creation_date.timestamp()
+ if isinstance(rp.creation_date, datetime)
+ else 0.0
+ ),
+ rp.region or "",
+ rp.backup_vault_name or "",
+ rp.arn or "",
+ rp.id or "",
+ ),
+ ),
+ self.recovery_point_limit,
+ )
+ )
+
class BackupVault(BaseModel):
arn: str
@@ -256,4 +289,5 @@ class RecoveryPoint(BaseModel):
backup_vault_name: str
encrypted: bool
backup_vault_region: str
+ creation_date: Optional[datetime] = None
tags: Optional[list] = None
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_cloudmonitor_enabled/__init__.py b/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_cloudmonitor_enabled/__init__.py
rename to prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/__init__.py
diff --git a/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.metadata.json b/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.metadata.json
new file mode 100644
index 0000000000..7625b6a626
--- /dev/null
+++ b/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.metadata.json
@@ -0,0 +1,41 @@
+{
+ "Provider": "aws",
+ "CheckID": "bedrock_agent_role_least_privilege",
+ "CheckTitle": "Amazon Bedrock agent execution role follows least privilege",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices/Runtime Behavior Analysis",
+ "TTPs/Privilege Escalation"
+ ],
+ "ServiceName": "bedrock",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "Other",
+ "ResourceGroup": "ai_ml",
+ "Description": "**Bedrock Agent** execution roles (`agentResourceRoleArn`) should grant only the minimum permissions the agent needs. The evaluation FAILs when the role has an AWS-managed `*FullAccess` policy attached, has an inline statement allowing broad actions on `Resource: \"*\"`, or has no permissions boundary configured.",
+ "Risk": "An overly permissive **Bedrock Agent** execution role turns a successful **prompt injection** into AWS privilege escalation. A model coerced into calling tools can invoke any API the role allows — reading secrets, modifying IAM, exfiltrating data from S3, or pivoting laterally. **Least privilege** plus a **permissions boundary** keeps the blast radius bounded even when guardrails fail.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html",
+ "https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html",
+ "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws iam put-role-permissions-boundary --role-name <execution_role_name> --permissions-boundary <boundary_policy_arn>",
+ "NativeIaC": "",
+ "Other": "1. Identify the Bedrock Agent's execution role (agentResourceRoleArn) in the IAM console\n2. Detach any AWS-managed *FullAccess policies (e.g. AmazonBedrockFullAccess, AdministratorAccess)\n3. Replace inline policies that use Resource: \"*\" with statements scoped to specific resource ARNs and minimal action sets\n4. Attach a permissions boundary that caps what the role can ever do, even if a future policy is added\n5. Re-run Prowler to confirm the check passes",
+ "Terraform": "```hcl\nresource \"aws_iam_role\" \"bedrock_agent\" {\n name = \"<execution_role_name>\"\n assume_role_policy = data.aws_iam_policy_document.trust.json\n permissions_boundary = aws_iam_policy.bedrock_agent_boundary.arn # CRITICAL: caps maximum privileges\n}\n\nresource \"aws_iam_role_policy\" \"bedrock_agent_inline\" {\n role = aws_iam_role.bedrock_agent.name\n policy = jsonencode({\n Version = \"2012-10-17\",\n Statement = [{\n Effect = \"Allow\",\n Action = [\"s3:GetObject\"], # CRITICAL: narrow action\n Resource = [\"arn:aws:s3:::my-rag-bucket/*\"] # CRITICAL: narrow resource\n }]\n })\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Apply **least privilege** to every Bedrock Agent execution role: scope `Action` and `Resource` to exactly what the agent needs, avoid AWS-managed `*FullAccess` policies, and always attach a **permissions boundary** so that future policy edits cannot exceed an approved ceiling. Treat agent roles as high-risk because prompt injection can weaponize any granted permission.",
+ "Url": "https://hub.prowler.com/check/bedrock_agent_role_least_privilege"
+ }
+ },
+ "Categories": [
+ "gen-ai"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.py b/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.py
new file mode 100644
index 0000000000..e53183d90f
--- /dev/null
+++ b/prowler/providers/aws/services/bedrock/bedrock_agent_role_least_privilege/bedrock_agent_role_least_privilege.py
@@ -0,0 +1,101 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.bedrock.bedrock_agent_client import (
+ bedrock_agent_client,
+)
+from prowler.providers.aws.services.iam.iam_client import iam_client
+from prowler.providers.aws.services.iam.lib.policy import check_admin_access
+from prowler.providers.aws.services.iam.lib.privilege_escalation import (
+ check_privilege_escalation,
+)
+
+
+class bedrock_agent_role_least_privilege(Check):
+ """Ensure Bedrock Agent execution roles follow least privilege.
+
+ A Bedrock Agent's execution role is evaluated against three criteria:
+ - No AWS-managed ``*FullAccess`` policy attached.
+ - No attached or inline policy granting administrative access or known
+ privilege escalation combinations.
+ - A permissions boundary is configured on the role.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Run the least-privilege evaluation across all Bedrock Agents.
+
+ Returns:
+ A list of ``Check_Report_AWS`` with one entry per agent. The
+ status is ``FAIL`` when any of the criteria above is violated,
+ or when the execution role cannot be resolved in IAM.
+ """
+ findings = []
+ roles_by_arn = {role.arn: role for role in (iam_client.roles or [])}
+
+ for agent in bedrock_agent_client.agents.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=agent)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Bedrock Agent {agent.name} execution role follows least privilege."
+ )
+
+ role = roles_by_arn.get(agent.role_arn) if agent.role_arn else None
+ if role is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Bedrock Agent {agent.name} execution role could not be "
+ f"resolved in IAM and cannot be evaluated for least privilege."
+ )
+ findings.append(report)
+ continue
+
+ violations = []
+
+ for policy in role.attached_policies:
+ policy_arn = policy.get("PolicyArn", "")
+ policy_name = policy.get("PolicyName") or policy_arn
+ if policy_arn.startswith(
+ "arn:aws:iam::aws:policy/"
+ ) and policy_arn.endswith("FullAccess"):
+ violations.append(
+ f"managed policy {policy_name} grants full access"
+ )
+ continue
+ policy_obj = iam_client.policies.get(policy_arn)
+ if policy_obj is None or not policy_obj.document:
+ continue
+ document = policy_obj.document
+ if check_admin_access(document):
+ violations.append(
+ f"managed policy {policy_name} grants administrative access"
+ )
+ elif check_privilege_escalation(document):
+ violations.append(
+ f"managed policy {policy_name} allows privilege escalation"
+ )
+
+ for inline_name in role.inline_policies:
+ policy_obj = iam_client.policies.get(f"{role.arn}:policy/{inline_name}")
+ if policy_obj is None or not policy_obj.document:
+ continue
+ document = policy_obj.document
+ if check_admin_access(document):
+ violations.append(
+ f"inline policy {inline_name} grants administrative access"
+ )
+ elif check_privilege_escalation(document):
+ violations.append(
+ f"inline policy {inline_name} allows privilege escalation"
+ )
+
+ if not role.permissions_boundary:
+ violations.append("no permissions boundary configured")
+
+ if violations:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Bedrock Agent {agent.name} execution role violates least "
+ f"privilege: {'; '.join(violations)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.metadata.json b/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.metadata.json
index f9b8ee0df9..c85279e4a4 100644
--- a/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.metadata.json
+++ b/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.metadata.json
@@ -1,7 +1,7 @@
{
"Provider": "aws",
"CheckID": "bedrock_api_key_no_long_term_credentials",
- "CheckTitle": "Amazon Bedrock API key is expired",
+ "CheckTitle": "Amazon Bedrock long-term API key has expired",
"CheckType": [
"Software and Configuration Checks/AWS Security Best Practices",
"Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices",
@@ -14,23 +14,24 @@
"Severity": "high",
"ResourceType": "AwsIamUser",
"ResourceGroup": "IAM",
- "Description": "**Bedrock API keys** are evaluated for **lifetime** and **expiration**.\n\nThe finding identifies keys that are long-lived, set to expire far in the future, or configured to `never expire`, and distinguishes them from keys that have already expired.",
- "Risk": "Long-lived or non-expiring keys enable persistent access if compromised.\n- Confidentiality: unauthorized inference and exposure of prompts/outputs\n- Availability/Cost: uncontrolled usage and spend spikes\n- Integrity: actions can continue without timely revocation or rotation",
+ "Description": "AWS recommends Amazon Bedrock **long-term API keys** only for **exploration**; production workloads should use **short-term API keys** (session-scoped, valid up to **12 hours**). This check fails for any active long-term Bedrock API key, escalating to `critical` severity when configured to **never expire**. Already-expired keys pass — they can no longer authenticate.",
+ "Risk": "Long-term Bedrock API keys persist beyond a session until their stored expiration, and keys set to **never expire** grant indefinite access until manually revoked, enabling unauthorized inference, uncontrolled usage and spend, and activity that continues past timely revocation.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://docs.aws.amazon.com/ja_jp/bedrock/latest/userguide/getting-started-api-keys.html",
- "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#rotate-credentials",
- "https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html"
+ "https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html",
+ "https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys-generate.html",
+ "https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds-programmatic-access.html#security-creds-alternatives-to-long-term-access-keys",
+ "https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#rotate-credentials"
],
"Remediation": {
"Code": {
"CLI": "aws iam delete-service-specific-credential --user-name <username> --service-specific-credential-id <credential-id>",
"NativeIaC": "",
- "Other": "1. Sign in to the AWS Management Console and open IAM\n2. Go to Users > select <example_resource_name> > Security credentials\n3. In \"API keys for Amazon Bedrock\", find the non-expired key and click Delete\n4. Confirm deletion to remove the key (removes the long-term credential so the check passes)",
+ "Other": "1. Sign in to the AWS Management Console and open IAM\n2. Go to Users > select the IAM user backing the Bedrock API key > Security credentials\n3. In \"API keys for Amazon Bedrock\", select the active long-term key and click Delete\n4. For workloads that still need Bedrock access, generate a short-term API key from the Bedrock console (Short-term API keys tab), or call the Bedrock API with short-term credentials issued by AWS STS",
"Terraform": ""
},
"Recommendation": {
- "Text": "Prefer **short-term credentials** and **IAM roles**; avoid `never expire`.\n\nEnforce **least privilege**, strict **rotation**, and automatic **expiration** for any long-term key. Store secrets securely, monitor with audit logs, and revoke unused or stale keys quickly.",
+ "Text": "Use short-term Amazon Bedrock API keys for any non-exploratory workload — they are bound to the IAM principal's session, valid for at most 12 hours, scoped to a single Region, and can be auto-refreshed by the SDK. For existing long-term keys, delete the underlying IAM service-specific credential. If a long-term key must be retained for an exploration scenario, set an explicit short expiration and never select `never expire`.",
"Url": "https://hub.prowler.com/check/bedrock_api_key_no_long_term_credentials"
}
},
@@ -40,5 +41,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": "This check verifies that Amazon Bedrock API keys have expiration dates set. API keys without expiration dates are considered long-term credentials and pose a security risk. The check follows security best practices for credential management and the principle of least privilege."
+ "Notes": "AWS recommends against using long-term Amazon Bedrock API keys outside of exploration; production workloads should use short-term API keys (session-scoped, valid up to 12 hours). The IAM `ListServiceSpecificCredentials` API only enumerates long-term keys — short-term keys are session-scoped credentials that never appear here. The check therefore passes only when an existing long-term key has already expired and can no longer authenticate; any active long-term key fails, with critical severity when it is configured to never expire."
}
diff --git a/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.py b/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.py
index 2edffd7ccb..9697ecbff0 100644
--- a/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.py
+++ b/prowler/providers/aws/services/bedrock/bedrock_api_key_no_long_term_credentials/bedrock_api_key_no_long_term_credentials.py
@@ -1,49 +1,62 @@
from datetime import datetime, timezone
-from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.check.models import Check, Check_Report_AWS, Severity
from prowler.providers.aws.services.iam.iam_client import iam_client
+# Days threshold above which a Bedrock long-term API key is considered effectively non-expiring.
+NEVER_EXPIRES_THRESHOLD_DAYS = 10000
+
class bedrock_api_key_no_long_term_credentials(Check):
- """
- Bedrock API keys should be short-lived to reduce the risk of unauthorized access.
- This check verifies if there are any long-term Bedrock API keys.
- If there are, it checks if they are expired or will be expired.
- If they are expired, it will be marked as PASS.
- If they are not expired, it will be marked as FAIL and the severity will be critical if the key will never expire.
+ """Amazon Bedrock long-term API keys should not be used outside of exploration.
+
+ AWS recommends short-term Bedrock API keys (session-scoped, valid up to 12 hours)
+ for any non-exploratory workload. ``ListServiceSpecificCredentials`` only enumerates
+ long-term keys, so every key inspected here is by definition a long-term credential.
+
+ PASS when the long-term key has already expired (it can no longer authenticate).
+ FAIL (critical) when the key is configured to never expire.
+ FAIL (high) for any other active long-term key.
"""
def execute(self):
- """
- Execute the Bedrock API key no long-term credentials check.
-
- Iterate over all the Bedrock API keys and check if they are expired or will be expired.
-
- Returns:
- List[Check_Report_AWS]: A list of report objects with the results of the check.
- """
-
findings = []
for api_key in iam_client.service_specific_credentials:
if api_key.service_name != "bedrock.amazonaws.com":
continue
- if api_key.expiration_date:
- report = Check_Report_AWS(metadata=self.metadata(), resource=api_key)
- # Check if the expiration date is in the future
- if api_key.expiration_date > datetime.now(timezone.utc):
- report.status = "FAIL"
- # Get the days until the expiration date
- days_until_expiration = (
- api_key.expiration_date - datetime.now(timezone.utc)
- ).days
- if days_until_expiration > 10000:
- self.Severity = "critical"
- report.status_extended = f"Long-term Bedrock API key {api_key.id} in user {api_key.user.name} exists and never expires."
- else:
- report.status_extended = f"Long-term Bedrock API key {api_key.id} in user {api_key.user.name} exists and will expire in {days_until_expiration} days."
- else:
- report.status = "PASS"
- report.status_extended = f"Long-term Bedrock API key {api_key.id} in user {api_key.user.name} exists but has expired."
- findings.append(report)
+ if not api_key.expiration_date:
+ continue
+
+ report = Check_Report_AWS(metadata=self.metadata(), resource=api_key)
+ now = datetime.now(timezone.utc)
+
+ if api_key.expiration_date <= now:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Bedrock long-term API key {api_key.id} in user "
+ f"{api_key.user.name} has already expired and can no longer "
+ f"authenticate."
+ )
+ elif (api_key.expiration_date - now).days > NEVER_EXPIRES_THRESHOLD_DAYS:
+ report.status = "FAIL"
+ report.check_metadata.Severity = Severity.critical
+ report.status_extended = (
+ f"Bedrock long-term API key {api_key.id} in user "
+ f"{api_key.user.name} is configured to never expire. Use "
+ f"short-term Bedrock API keys (session-scoped, valid up to "
+ f"12 hours) for non-exploratory workloads instead."
+ )
+ else:
+ days_until_expiration = (api_key.expiration_date - now).days
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Bedrock long-term API key {api_key.id} in user "
+ f"{api_key.user.name} is active and will expire in "
+ f"{days_until_expiration} days. Use short-term Bedrock API "
+ f"keys (session-scoped, valid up to 12 hours) for "
+ f"non-exploratory workloads instead."
+ )
+
+ findings.append(report)
return findings
diff --git a/prowler/providers/aws/services/bedrock/bedrock_model_invocation_logs_encryption_enabled/bedrock_model_invocation_logs_encryption_enabled.py b/prowler/providers/aws/services/bedrock/bedrock_model_invocation_logs_encryption_enabled/bedrock_model_invocation_logs_encryption_enabled.py
index c4adddc344..230cfd2295 100644
--- a/prowler/providers/aws/services/bedrock/bedrock_model_invocation_logs_encryption_enabled/bedrock_model_invocation_logs_encryption_enabled.py
+++ b/prowler/providers/aws/services/bedrock/bedrock_model_invocation_logs_encryption_enabled/bedrock_model_invocation_logs_encryption_enabled.py
@@ -30,12 +30,13 @@ class bedrock_model_invocation_logs_encryption_enabled(Check):
s3_encryption = False
if logging.cloudwatch_log_group:
log_group_arn = f"arn:{logs_client.audited_partition}:logs:{region}:{logs_client.audited_account}:log-group:{logging.cloudwatch_log_group}"
+ all_log_groups = getattr(logs_client, "all_log_groups", None) or {}
if (
- log_group_arn in logs_client.log_groups
- and not logs_client.log_groups[log_group_arn].kms_id
+ log_group_arn in all_log_groups
+ and not all_log_groups[log_group_arn].kms_id
) or (
- log_group_arn + ":*" in logs_client.log_groups
- and not logs_client.log_groups[log_group_arn + ":*"].kms_id
+ log_group_arn + ":*" in all_log_groups
+ and not all_log_groups[log_group_arn + ":*"].kms_id
):
cloudwatch_encryption = False
if not s3_encryption and not cloudwatch_encryption:
diff --git a/prowler/providers/aws/services/bedrock/bedrock_service.py b/prowler/providers/aws/services/bedrock/bedrock_service.py
index 7222456341..aead63a67f 100644
--- a/prowler/providers/aws/services/bedrock/bedrock_service.py
+++ b/prowler/providers/aws/services/bedrock/bedrock_service.py
@@ -146,6 +146,7 @@ class BedrockAgent(AWSService):
self.prompts = {}
self.prompt_scanned_regions: set = set()
self.__threading_call__(self._list_agents)
+ self.__threading_call__(self._get_agent, self.agents.values())
self.__threading_call__(self._list_prompts)
self.__threading_call__(self._get_prompt, self.prompts.values())
self.__threading_call__(self._list_tags_for_resource, self.agents.values())
@@ -174,6 +175,22 @@ class BedrockAgent(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_agent(self, agent):
+ """Fetch full agent details to capture the execution role ARN.
+
+ list_agents only returns summaries (no agentResourceRoleArn), so we
+ need a per-agent GetAgent call. Stored on the Agent model for use by
+ checks like bedrock_agent_role_least_privilege.
+ """
+ logger.info("Bedrock Agent - Getting Agent...")
+ try:
+ agent_info = self.regional_clients[agent.region].get_agent(agentId=agent.id)
+ agent.role_arn = agent_info.get("agent", {}).get("agentResourceRoleArn")
+ except Exception as error:
+ logger.error(
+ f"{agent.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _list_prompts(self, regional_client):
"""List all prompts in a region."""
logger.info("Bedrock Agent - Listing Prompts...")
@@ -236,6 +253,7 @@ class Agent(BaseModel):
name: str
arn: str
guardrail_id: Optional[str] = None
+ role_arn: Optional[str] = None
region: str
tags: Optional[list] = []
diff --git a/prowler/providers/aws/services/cloudformation/cloudformation_stack_outputs_find_secrets/cloudformation_stack_outputs_find_secrets.py b/prowler/providers/aws/services/cloudformation/cloudformation_stack_outputs_find_secrets/cloudformation_stack_outputs_find_secrets.py
index f9b47932bb..b86f851765 100644
--- a/prowler/providers/aws/services/cloudformation/cloudformation_stack_outputs_find_secrets/cloudformation_stack_outputs_find_secrets.py
+++ b/prowler/providers/aws/services/cloudformation/cloudformation_stack_outputs_find_secrets/cloudformation_stack_outputs_find_secrets.py
@@ -1,5 +1,9 @@
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.cloudformation.cloudformation_client import (
cloudformation_client,
)
@@ -14,26 +18,41 @@ class cloudformation_stack_outputs_find_secrets(Check):
secrets_ignore_patterns = cloudformation_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for stack in cloudformation_client.stacks:
+ validate = cloudformation_client.audit_config.get("secrets_validate", False)
+ stacks = list(cloudformation_client.stacks)
+
+ # Collect one payload per stack (its Outputs) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per stack.
+ def payloads():
+ for index, stack in enumerate(stacks):
+ if stack.outputs:
+ yield index, "".join(f"{output}\n" for output in stack.outputs)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, stack in enumerate(stacks):
report = Check_Report_AWS(metadata=self.metadata(), resource=stack)
report.status = "PASS"
report.status_extended = (
f"No secrets found in CloudFormation Stack {stack.name} Outputs."
)
if stack.outputs:
- data = ""
- # Store the CloudFormation Stack Outputs into a file
- for output in stack.outputs:
- data += f"{output}\n"
-
- detect_secrets_output = detect_secrets_scan(
- data=data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=cloudformation_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
- # If secrets are found, update the report status
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan CloudFormation Stack {stack.name} Outputs "
+ f"for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
secrets_string = ", ".join(
[
@@ -43,7 +62,7 @@ class cloudformation_stack_outputs_find_secrets(Check):
)
report.status = "FAIL"
report.status_extended = f"Potential secret found in CloudFormation Stack {stack.name} Outputs -> {secrets_string}."
-
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status = "PASS"
report.status_extended = (
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_recent/__init__.py b/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_recent/__init__.py
rename to prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/__init__.py
diff --git a/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.metadata.json b/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.metadata.json
new file mode 100644
index 0000000000..465f4335c2
--- /dev/null
+++ b/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "aws",
+ "CheckID": "cloudfront_distributions_pqc_tls_enabled",
+ "CheckTitle": "CloudFront distributions enforce a post-quantum TLS 1.3 security policy",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "cloudfront",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsCloudFrontDistribution",
+ "ResourceGroup": "network",
+ "Description": "**CloudFront distributions** are assessed for use of a **TLS 1.3-only security policy** (`TLSv1.3_2025`). CloudFront's quantum-safe key exchanges (`X25519MLKEM768`, `SecP256r1MLKEM768`) only work with TLS 1.3. Distributions that allow TLS 1.2 (or older) fallback to classical key exchanges and are exposed to `harvest-now, decrypt-later` attacks.",
+ "Risk": "Without a TLS 1.3-only policy, viewer traffic captured today can be decrypted once a **cryptographically relevant quantum computer** is available. Distributions using the default CloudFront certificate (`*.cloudfront.net`) cannot enable a post-quantum policy because they are pinned to the legacy `TLSv1` policy.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/secure-connections-supported-viewer-protocols-ciphers.html",
+ "https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DownloadDistValuesGeneral.html#DownloadDistValues-security-policy",
+ "https://aws.amazon.com/security/post-quantum-cryptography/",
+ "https://csrc.nist.gov/projects/post-quantum-cryptography"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws cloudfront update-distribution --id <distribution_id> --distribution-config '{...\"ViewerCertificate\":{\"MinimumProtocolVersion\":\"TLSv1.3_2025\",...}}'",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::CloudFront::Distribution\n Properties:\n DistributionConfig:\n ViewerCertificate:\n AcmCertificateArn: <example_certificate_arn>\n SslSupportMethod: sni-only\n MinimumProtocolVersion: TLSv1.3_2025 # FIX: enforces TLS 1.3 + post-quantum KEX\n```",
+ "Other": "1. In the AWS Console, go to CloudFront > Distributions\n2. Select the distribution and open the General tab\n3. Choose Edit on Settings\n4. Set Custom SSL certificate (do not use the default *.cloudfront.net certificate)\n5. Set Security policy to TLSv1.3_2025\n6. Save changes",
+ "Terraform": "```hcl\nresource \"aws_cloudfront_distribution\" \"<example_resource_name>\" {\n # ...\n viewer_certificate {\n acm_certificate_arn = \"<example_certificate_arn>\"\n ssl_support_method = \"sni-only\"\n minimum_protocol_version = \"TLSv1.3_2025\" # FIX: enforces TLS 1.3 + post-quantum KEX\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Use a **custom SSL certificate** with **SNI** support and set `MinimumProtocolVersion` to `TLSv1.3_2025` so CloudFront refuses TLS 1.2 handshakes and uses the hybrid ML-KEM key exchange. Distributions still using the default CloudFront certificate must be migrated to a custom certificate to enable post-quantum TLS.",
+ "Url": "https://hub.prowler.com/check/cloudfront_distributions_pqc_tls_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "cloudfront_distributions_using_deprecated_ssl_protocols"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.py b/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.py
new file mode 100644
index 0000000000..6c472d43c7
--- /dev/null
+++ b/prowler/providers/aws/services/cloudfront/cloudfront_distributions_pqc_tls_enabled/cloudfront_distributions_pqc_tls_enabled.py
@@ -0,0 +1,56 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.cloudfront.cloudfront_client import (
+ cloudfront_client,
+)
+
+PQC_CLOUDFRONT_POLICIES_DEFAULT = [
+ "TLSv1.3_2025",
+]
+
+
+class cloudfront_distributions_pqc_tls_enabled(Check):
+ """Verify that every CloudFront distribution enforces TLS 1.3 with post-quantum key exchange.
+
+ Quantum-safe key exchanges (``X25519MLKEM768``, ``SecP256r1MLKEM768``) are
+ only available on TLS 1.3 viewer connections. A distribution PASSES when
+ its ``MinimumProtocolVersion`` belongs to the configured allowlist of
+ TLS 1.3-only policies. Distributions that rely on the default CloudFront
+ certificate are pinned to the legacy ``TLSv1`` policy and therefore FAIL.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the CloudFront post-quantum TLS policy check.
+
+ Returns:
+ A list of reports containing each CloudFront distribution's
+ post-quantum TLS compliance status.
+ """
+ findings = []
+ pqc_policies = cloudfront_client.audit_config.get(
+ "cloudfront_pqc_min_protocol_versions", PQC_CLOUDFRONT_POLICIES_DEFAULT
+ )
+ for distribution in cloudfront_client.distributions.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=distribution)
+ policy = distribution.minimum_protocol_version or "<none>"
+ if distribution.default_certificate:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"CloudFront Distribution {distribution.id} uses the default "
+ "CloudFront certificate, which pins the security policy to "
+ "TLSv1 and cannot enable post-quantum TLS."
+ )
+ elif distribution.minimum_protocol_version in pqc_policies:
+ report.status = "PASS"
+ report.status_extended = (
+ f"CloudFront Distribution {distribution.id} uses post-quantum "
+ f"TLS policy {policy}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"CloudFront Distribution {distribution.id} uses TLS policy "
+ f"{policy}, which is not in the post-quantum allowlist."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/cloudfront/cloudfront_service.py b/prowler/providers/aws/services/cloudfront/cloudfront_service.py
index 0826c9adfd..660b483c4c 100644
--- a/prowler/providers/aws/services/cloudfront/cloudfront_service.py
+++ b/prowler/providers/aws/services/cloudfront/cloudfront_service.py
@@ -48,6 +48,9 @@ class CloudFront(AWSService):
"SSLSupportMethod", "static-ip"
)
)
+ minimum_protocol_version = item["ViewerCertificate"].get(
+ "MinimumProtocolVersion", ""
+ )
origins = []
for origin in item.get("Origins", {}).get("Items", []):
origins.append(
@@ -79,6 +82,7 @@ class CloudFront(AWSService):
ssl_support_method=ssl_support_method,
default_certificate=default_certificate,
certificate=certificate,
+ minimum_protocol_version=minimum_protocol_version,
)
self.distributions[distribution_id] = distribution
@@ -268,3 +272,4 @@ class Distribution(BaseModel):
origin_failover: Optional[bool] = None
ssl_support_method: Optional[SSLSupportMethod] = None
certificate: Optional[str] = None
+ minimum_protocol_version: str = ""
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.metadata.json b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.metadata.json
index 20ed5f0adb..9070c7b0c7 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.metadata.json
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.metadata.json
@@ -17,9 +17,8 @@
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html",
- "https://www.clouddefense.ai/compliance-rules/cis-v130/monitoring/cis-v130-4-11",
"https://support.icompaas.com/support/solutions/articles/62000084031-ensure-a-log-metric-filter-and-alarm-exist-for-changes-to-network-access-control-lists-nacl-",
- "https://trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/CloudWatchLogs/network-acl-changes-alarm.html",
+ "https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/CloudWatchLogs/network-acl-changes-alarm.html",
"https://support.icompaas.com/support/solutions/articles/62000233134-4-11-ensure-network-access-control-list-nacl-changes-are-monitored-manual-"
],
"Remediation": {
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.py
index 20d68a0121..68f45a8d27 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_acls_alarm_configured/cloudwatch_changes_to_network_acls_alarm_configured.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,16 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_changes_to_network_acls_alarm_configured(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?CreateNetworkAcl.+\$\.eventName\s*=\s*.?CreateNetworkAclEntry.+\$\.eventName\s*=\s*.?DeleteNetworkAcl.+\$\.eventName\s*=\s*.?DeleteNetworkAclEntry.+\$\.eventName\s*=\s*.?ReplaceNetworkAclEntry.+\$\.eventName\s*=\s*.?ReplaceNetworkAclAssociation.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "CreateNetworkAcl",
+ "CreateNetworkAclEntry",
+ "DeleteNetworkAcl",
+ "DeleteNetworkAclEntry",
+ "ReplaceNetworkAclEntry",
+ "ReplaceNetworkAclAssociation",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_gateways_alarm_configured/cloudwatch_changes_to_network_gateways_alarm_configured.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_gateways_alarm_configured/cloudwatch_changes_to_network_gateways_alarm_configured.py
index 5f6eda3973..f7bf8e1d22 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_gateways_alarm_configured/cloudwatch_changes_to_network_gateways_alarm_configured.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_gateways_alarm_configured/cloudwatch_changes_to_network_gateways_alarm_configured.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,16 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_changes_to_network_gateways_alarm_configured(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?CreateCustomerGateway.+\$\.eventName\s*=\s*.?DeleteCustomerGateway.+\$\.eventName\s*=\s*.?AttachInternetGateway.+\$\.eventName\s*=\s*.?CreateInternetGateway.+\$\.eventName\s*=\s*.?DeleteInternetGateway.+\$\.eventName\s*=\s*.?DetachInternetGateway.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "CreateCustomerGateway",
+ "DeleteCustomerGateway",
+ "AttachInternetGateway",
+ "CreateInternetGateway",
+ "DeleteInternetGateway",
+ "DetachInternetGateway",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.metadata.json b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.metadata.json
index 82490a63da..89949cfbd6 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.metadata.json
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.metadata.json
@@ -37,5 +37,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": ""
+ "Notes": "Logging and Monitoring"
}
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.py
index f8fcc8eacb..460765cb2f 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_network_route_tables_alarm_configured/cloudwatch_changes_to_network_route_tables_alarm_configured.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,18 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_changes_to_network_route_tables_alarm_configured(Check):
def execute(self):
- pattern = r"\$\.eventSource\s*=\s*.?ec2.amazonaws.com.+\$\.eventName\s*=\s*.?CreateRoute.+\$\.eventName\s*=\s*.?CreateRouteTable.+\$\.eventName\s*=\s*.?ReplaceRoute.+\$\.eventName\s*=\s*.?ReplaceRouteTableAssociation.+\$\.eventName\s*=\s*.?DeleteRouteTable.+\$\.eventName\s*=\s*.?DeleteRoute.+\$\.eventName\s*=\s*.?DisassociateRouteTable.?"
+ pattern = build_metric_filter_pattern(
+ event_source="ec2.amazonaws.com",
+ event_names=[
+ "CreateRoute",
+ "CreateRouteTable",
+ "ReplaceRoute",
+ "ReplaceRouteTableAssociation",
+ "DeleteRouteTable",
+ "DeleteRoute",
+ "DisassociateRouteTable",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_vpcs_alarm_configured/cloudwatch_changes_to_vpcs_alarm_configured.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_vpcs_alarm_configured/cloudwatch_changes_to_vpcs_alarm_configured.py
index d7606647c4..be4fb0859d 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_vpcs_alarm_configured/cloudwatch_changes_to_vpcs_alarm_configured.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_changes_to_vpcs_alarm_configured/cloudwatch_changes_to_vpcs_alarm_configured.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,21 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_changes_to_vpcs_alarm_configured(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?CreateVpc.+\$\.eventName\s*=\s*.?DeleteVpc.+\$\.eventName\s*=\s*.?ModifyVpcAttribute.+\$\.eventName\s*=\s*.?AcceptVpcPeeringConnection.+\$\.eventName\s*=\s*.?CreateVpcPeeringConnection.+\$\.eventName\s*=\s*.?DeleteVpcPeeringConnection.+\$\.eventName\s*=\s*.?RejectVpcPeeringConnection.+\$\.eventName\s*=\s*.?AttachClassicLinkVpc.+\$\.eventName\s*=\s*.?DetachClassicLinkVpc.+\$\.eventName\s*=\s*.?DisableVpcClassicLink.+\$\.eventName\s*=\s*.?EnableVpcClassicLink.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "CreateVpc",
+ "DeleteVpc",
+ "ModifyVpcAttribute",
+ "AcceptVpcPeeringConnection",
+ "CreateVpcPeeringConnection",
+ "DeleteVpcPeeringConnection",
+ "RejectVpcPeeringConnection",
+ "AttachClassicLinkVpc",
+ "DetachClassicLinkVpc",
+ "DisableVpcClassicLink",
+ "EnableVpcClassicLink",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_group_no_secrets_in_logs/cloudwatch_log_group_no_secrets_in_logs.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_group_no_secrets_in_logs/cloudwatch_log_group_no_secrets_in_logs.py
index 5154a5acb7..9cfd17ab0a 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_group_no_secrets_in_logs/cloudwatch_log_group_no_secrets_in_logs.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_group_no_secrets_in_logs/cloudwatch_log_group_no_secrets_in_logs.py
@@ -1,7 +1,11 @@
from json import dumps, loads
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.cloudwatch.cloudwatch_service import (
convert_to_cloudwatch_timestamp_format,
)
@@ -11,95 +15,197 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_group_no_secrets_in_logs(Check):
def execute(self):
findings = []
- if logs_client.log_groups:
- secrets_ignore_patterns = logs_client.audit_config.get(
- "secrets_ignore_patterns", []
- )
+ if not logs_client.log_groups:
+ return findings
+
+ secrets_ignore_patterns = logs_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = logs_client.audit_config.get("secrets_validate", False)
+
+ # Phase 1: batch-scan every (log group, log stream). Payloads are yielded
+ # lazily so only a chunk is written/held at a time, which matters for
+ # accounts with very large numbers of log groups/streams. The log group
+ # ARN (not its name) keys every map below, since group and stream names
+ # are not unique across regions and would otherwise collide.
+ def stream_payloads():
for log_group in logs_client.log_groups.values():
- report = Check_Report_AWS(metadata=self.metadata(), resource=log_group)
- report.status = "PASS"
- report.status_extended = (
- f"No secrets found in {log_group.name} log group."
+ if not log_group.log_streams:
+ continue
+ for log_stream_name, events in log_group.log_streams.items():
+ yield (
+ (log_group.arn, log_stream_name),
+ "\n".join(dumps(event["message"]) for event in events),
+ )
+
+ # A scanner failure here must never look like "no secrets": log groups
+ # whose streams could not be scanned are reported MANUAL in Phase 4.
+ stream_scan_error = None
+ try:
+ stream_results = detect_secrets_scan_batch(
+ stream_payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ stream_results = {}
+ stream_scan_error = error
+
+ # Phase 2: plan the per-event secrets for each flagged stream and collect
+ # the multiline events to rescan. Each multiline event is rescanned once
+ # to resolve per-line detail; the rescans are batched in Phase 3 instead
+ # of one subprocess per event. The event index (``line_number - 1``,
+ # since Phase 1 joins one event per line) is the per-event discriminator:
+ # a CloudWatch stream can hold several events sharing one millisecond
+ # timestamp, so keying only by timestamp would let a later multiline
+ # event overwrite an earlier one's payload and lose secret evidence.
+ # Output still groups/displays by timestamp; only the rescan identity is
+ # per event.
+ # stream_plans: (group arn, stream) ->
+ # {timestamp: {event index: {"multiline", "types"}}}
+ # rescan_payloads: (group arn, stream, timestamp, event index) ->
+ # multiline event data
+ stream_plans = {}
+ rescan_payloads = {}
+ groups_with_rescan = set() # group arns that depend on the Phase 3 rescan
+ for log_group in logs_client.log_groups.values():
+ for log_stream_name in log_group.log_streams or {}:
+ stream_secrets = stream_results.get((log_group.arn, log_stream_name))
+ if not stream_secrets:
+ continue
+ events = log_group.log_streams[log_stream_name]
+ plan = {}
+ for secret in stream_secrets:
+ event_index = secret["line_number"] - 1
+ flagged_event = events[event_index]
+ cloudwatch_timestamp = convert_to_cloudwatch_timestamp_format(
+ flagged_event["timestamp"]
+ )
+ try:
+ log_event_data = dumps(
+ loads(flagged_event["message"]), indent=2
+ )
+ except Exception:
+ log_event_data = dumps(flagged_event["message"], indent=2)
+ multiline = len(log_event_data.split("\n")) > 1
+ events_at_timestamp = plan.setdefault(cloudwatch_timestamp, {})
+ if event_index not in events_at_timestamp:
+ events_at_timestamp[event_index] = {
+ "multiline": multiline,
+ "types": [],
+ }
+ if multiline:
+ # More informative output is possible with more than one
+ # line: the event is rescanned to get the type and line
+ # number of each secret.
+ rescan_payloads[
+ (
+ log_group.arn,
+ log_stream_name,
+ cloudwatch_timestamp,
+ event_index,
+ )
+ ] = log_event_data
+ groups_with_rescan.add(log_group.arn)
+ else:
+ events_at_timestamp[event_index]["types"].append(secret["type"])
+ stream_plans[(log_group.arn, log_stream_name)] = plan
+
+ # Phase 3: one batched rescan for all multiline flagged events. Validation
+ # is never enabled here: this rescan only resolves line numbers for
+ # display and must not re-authenticate the secret.
+ # If the rescan fails we know secrets were already found in Phase 1, so
+ # the affected groups must not silently pass; they are reported MANUAL.
+ rescan_scan_error = None
+ rescan_results = {}
+ if rescan_payloads:
+ try:
+ rescan_results = detect_secrets_scan_batch(
+ rescan_payloads, excluded_secrets=secrets_ignore_patterns
)
- log_group_secrets = []
- if log_group.log_streams:
- for log_stream_name in log_group.log_streams:
- log_stream_secrets = {}
- log_stream_data = "\n".join(
- [
- dumps(event["message"])
- for event in log_group.log_streams[log_stream_name]
- ]
- )
- log_stream_secrets_output = detect_secrets_scan(
- data=log_stream_data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=logs_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
+ except SecretsScanError as error:
+ rescan_scan_error = error
- if log_stream_secrets_output:
- for secret in log_stream_secrets_output:
- flagged_event = log_group.log_streams[log_stream_name][
- secret["line_number"] - 1
- ]
- cloudwatch_timestamp = (
- convert_to_cloudwatch_timestamp_format(
- flagged_event["timestamp"]
- )
- )
- if (
- cloudwatch_timestamp
- not in log_stream_secrets.keys()
- ):
- log_stream_secrets[cloudwatch_timestamp] = (
- SecretsDict()
- )
+ # Phase 4: assemble one report per log group.
+ for log_group in logs_client.log_groups.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=log_group)
+ report.status = "PASS"
+ report.status_extended = f"No secrets found in {log_group.name} log group."
- try:
- log_event_data = dumps(
- loads(flagged_event["message"]), indent=2
- )
- except Exception:
- log_event_data = dumps(
- flagged_event["message"], indent=2
- )
- if len(log_event_data.split("\n")) > 1:
- # Can get more informative output if there is more than 1 line.
- # Will rescan just this event to get the type of secret and the line number
- event_detect_secrets_output = detect_secrets_scan(
- data=log_event_data,
- detect_secrets_plugins=logs_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
- if event_detect_secrets_output:
- for secret in event_detect_secrets_output:
- log_stream_secrets[
- cloudwatch_timestamp
- ].add_secret(
- secret["line_number"], secret["type"]
- )
- else:
- log_stream_secrets[cloudwatch_timestamp].add_secret(
- 1, secret["type"]
- )
- if log_stream_secrets:
- secrets_string = "; ".join(
- [
- f"at {timestamp} - {log_stream_secrets[timestamp].to_string()}"
- for timestamp in log_stream_secrets
- ]
- )
- log_group_secrets.append(
- f"in log stream {log_stream_name} {secrets_string}"
- )
- if log_group_secrets:
- secrets_string = "; ".join(log_group_secrets)
- report.status = "FAIL"
- report.status_extended = f"Potential secrets found in log group {log_group.name} {secrets_string}."
+ # The stream scan failed: we cannot conclude this group is clean.
+ if stream_scan_error and log_group.log_streams:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan log group {log_group.name} for secrets: "
+ f"{stream_scan_error}; manual review is required."
+ )
findings.append(report)
+ continue
+
+ log_group_secrets = []
+ all_secrets = []
+ for log_stream_name in log_group.log_streams or {}:
+ stream_secrets = stream_results.get((log_group.arn, log_stream_name))
+ if not stream_secrets:
+ continue
+ all_secrets.extend(stream_secrets)
+ log_stream_secrets = {}
+ for cloudwatch_timestamp, events_at_timestamp in stream_plans[
+ (log_group.arn, log_stream_name)
+ ].items():
+ secrets_dict = SecretsDict()
+ # Multiple events can share one timestamp; aggregate each
+ # event's secrets into the timestamp's display entry.
+ for event_index, entry in events_at_timestamp.items():
+ if entry["multiline"]:
+ for event_secret in rescan_results.get(
+ (
+ log_group.arn,
+ log_stream_name,
+ cloudwatch_timestamp,
+ event_index,
+ ),
+ [],
+ ):
+ secrets_dict.add_secret(
+ event_secret["line_number"], event_secret["type"]
+ )
+ else:
+ for secret_type in entry["types"]:
+ secrets_dict.add_secret(1, secret_type)
+ # Only record the event when at least one non-ignored secret
+ # remains after the rescan. A multiline event whose secrets
+ # were all dropped by ``secrets_ignore_patterns`` leaves an
+ # empty SecretsDict, which must not produce a FAIL with no
+ # actual secret evidence.
+ if secrets_dict:
+ log_stream_secrets[cloudwatch_timestamp] = secrets_dict
+ if log_stream_secrets:
+ secrets_string = "; ".join(
+ [
+ f"at {timestamp} - {log_stream_secrets[timestamp].to_string()}"
+ for timestamp in log_stream_secrets
+ ]
+ )
+ log_group_secrets.append(
+ f"in log stream {log_stream_name} {secrets_string}"
+ )
+ # The multiline rescan failed for a group that had flagged secrets:
+ # detail is unavailable, so report MANUAL rather than risk a false
+ # PASS when every flagged event was multiline.
+ if rescan_scan_error and log_group.arn in groups_with_rescan:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Secrets were detected in log group {log_group.name} but the "
+ f"detailed rescan failed: {rescan_scan_error}; manual review "
+ "is required."
+ )
+ elif log_group_secrets:
+ secrets_string = "; ".join(log_group_secrets)
+ report.status = "FAIL"
+ report.status_extended = f"Potential secrets found in log group {log_group.name} {secrets_string}."
+ annotate_verified_secrets(report, all_secrets)
+ findings.append(report)
return findings
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled.py
index 11bf08d99d..49bf9a03a3 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_changes_enabled.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -15,7 +16,15 @@ class cloudwatch_log_metric_filter_and_alarm_for_aws_config_configuration_change
Check
):
def execute(self):
- pattern = r"\$\.eventSource\s*=\s*.?config.amazonaws.com.+\$\.eventName\s*=\s*.?StopConfigurationRecorder.+\$\.eventName\s*=\s*.?DeleteDeliveryChannel.+\$\.eventName\s*=\s*.?PutDeliveryChannel.+\$\.eventName\s*=\s*.?PutConfigurationRecorder.?"
+ pattern = build_metric_filter_pattern(
+ event_source="config.amazonaws.com",
+ event_names=[
+ "StopConfigurationRecorder",
+ "DeleteDeliveryChannel",
+ "PutDeliveryChannel",
+ "PutConfigurationRecorder",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled.py
index eb272ecfb1..e9567315f4 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled/cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_changes_enabled.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -15,7 +16,15 @@ class cloudwatch_log_metric_filter_and_alarm_for_cloudtrail_configuration_change
Check
):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?CreateTrail.+\$\.eventName\s*=\s*.?UpdateTrail.+\$\.eventName\s*=\s*.?DeleteTrail.+\$\.eventName\s*=\s*.?StartLogging.+\$\.eventName\s*=\s*.?StopLogging.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "CreateTrail",
+ "UpdateTrail",
+ "DeleteTrail",
+ "StartLogging",
+ "StopLogging",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_authentication_failures/cloudwatch_log_metric_filter_authentication_failures.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_authentication_failures/cloudwatch_log_metric_filter_authentication_failures.py
index c217cbbaf6..1b2e5173bb 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_authentication_failures/cloudwatch_log_metric_filter_authentication_failures.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_authentication_failures/cloudwatch_log_metric_filter_authentication_failures.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,10 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_authentication_failures(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?ConsoleLogin.+\$\.errorMessage\s*=\s*.?Failed authentication.?"
+ pattern = build_metric_filter_pattern(
+ event_names=["ConsoleLogin"],
+ extra_clauses=[("errorMessage", "=", "Failed authentication")],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_aws_organizations_changes/cloudwatch_log_metric_filter_aws_organizations_changes.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_aws_organizations_changes/cloudwatch_log_metric_filter_aws_organizations_changes.py
index af7ec82119..9976a885bb 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_aws_organizations_changes/cloudwatch_log_metric_filter_aws_organizations_changes.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_aws_organizations_changes/cloudwatch_log_metric_filter_aws_organizations_changes.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,32 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_aws_organizations_changes(Check):
def execute(self):
- pattern = r"\$\.eventSource\s*=\s*.?organizations\.amazonaws\.com.+\$\.eventName\s*=\s*.?AcceptHandshake.+\$\.eventName\s*=\s*.?AttachPolicy.+\$\.eventName\s*=\s*.?CancelHandshake.+\$\.eventName\s*=\s*.?CreateAccount.+\$\.eventName\s*=\s*.?CreateOrganization.+\$\.eventName\s*=\s*.?CreateOrganizationalUnit.+\$\.eventName\s*=\s*.?CreatePolicy.+\$\.eventName\s*=\s*.?DeclineHandshake.+\$\.eventName\s*=\s*.?DeleteOrganization.+\$\.eventName\s*=\s*.?DeleteOrganizationalUnit.+\$\.eventName\s*=\s*.?DeletePolicy.+\$\.eventName\s*=\s*.?EnableAllFeatures.+\$\.eventName\s*=\s*.?EnablePolicyType.+\$\.eventName\s*=\s*.?InviteAccountToOrganization.+\$\.eventName\s*=\s*.?LeaveOrganization.+\$\.eventName\s*=\s*.?DetachPolicy.+\$\.eventName\s*=\s*.?DisablePolicyType.+\$\.eventName\s*=\s*.?MoveAccount.+\$\.eventName\s*=\s*.?RemoveAccountFromOrganization.+\$\.eventName\s*=\s*.?UpdateOrganizationalUnit.+\$\.eventName\s*=\s*.?UpdatePolicy.?"
+ pattern = build_metric_filter_pattern(
+ event_source="organizations.amazonaws.com",
+ event_names=[
+ "AcceptHandshake",
+ "AttachPolicy",
+ "CancelHandshake",
+ "CreateAccount",
+ "CreateOrganization",
+ "CreateOrganizationalUnit",
+ "CreatePolicy",
+ "DeclineHandshake",
+ "DeleteOrganization",
+ "DeleteOrganizationalUnit",
+ "DeletePolicy",
+ "EnableAllFeatures",
+ "EnablePolicyType",
+ "InviteAccountToOrganization",
+ "LeaveOrganization",
+ "DetachPolicy",
+ "DisablePolicyType",
+ "MoveAccount",
+ "RemoveAccountFromOrganization",
+ "UpdateOrganizationalUnit",
+ "UpdatePolicy",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk.py
index 4cfed985f7..20d1d62a5a 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk/cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,10 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_disable_or_scheduled_deletion_of_kms_cmk(Check):
def execute(self):
- pattern = r"\$\.eventSource\s*=\s*.?kms.amazonaws.com.+\$\.eventName\s*=\s*.?DisableKey.+\$\.eventName\s*=\s*.?ScheduleKeyDeletion.?"
+ pattern = build_metric_filter_pattern(
+ event_source="kms.amazonaws.com",
+ event_names=["DisableKey", "ScheduleKeyDeletion"],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.metadata.json b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.metadata.json
index 2d77c42704..6292de6071 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.metadata.json
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.metadata.json
@@ -17,8 +17,7 @@
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html",
- "https://support.icompaas.com/support/solutions/articles/62000086674-ensure-a-log-metric-filter-and-alarm-exist-for-s3-bucket-policy-changes",
- "https://www.tenable.com/audits/items/CIS_Amazon_Web_Services_Foundations_v5.0.0_L1.audit:8101350d6907e07863ac6748689b3e12"
+ "https://support.icompaas.com/support/solutions/articles/62000086674-ensure-a-log-metric-filter-and-alarm-exist-for-s3-bucket-policy-changes"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.py
index 45d09b3528..d5fe1ef994 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes/cloudwatch_log_metric_filter_for_s3_bucket_policy_changes.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,20 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_for_s3_bucket_policy_changes(Check):
def execute(self):
- pattern = r"\$\.eventSource\s*=\s*.?s3.amazonaws.com.+\$\.eventName\s*=\s*.?PutBucketAcl.+\$\.eventName\s*=\s*.?PutBucketPolicy.+\$\.eventName\s*=\s*.?PutBucketCors.+\$\.eventName\s*=\s*.?PutBucketLifecycle.+\$\.eventName\s*=\s*.?PutBucketReplication.+\$\.eventName\s*=\s*.?DeleteBucketPolicy.+\$\.eventName\s*=\s*.?DeleteBucketCors.+\$\.eventName\s*=\s*.?DeleteBucketLifecycle.+\$\.eventName\s*=\s*.?DeleteBucketReplication.?"
+ pattern = build_metric_filter_pattern(
+ event_source="s3.amazonaws.com",
+ event_names=[
+ "PutBucketAcl",
+ "PutBucketPolicy",
+ "PutBucketCors",
+ "PutBucketLifecycle",
+ "PutBucketReplication",
+ "DeleteBucketPolicy",
+ "DeleteBucketCors",
+ "DeleteBucketLifecycle",
+ "DeleteBucketReplication",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.metadata.json b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.metadata.json
index 75cba1ee62..b1c36be2d8 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.metadata.json
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.metadata.json
@@ -17,7 +17,6 @@
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html",
- "https://www.clouddefense.ai/compliance-rules/cis-v140/monitoring/cis-v140-4-4",
"https://www.intelligentdiscovery.io/controls/cloudwatch/cloudwatch-alarm-iam-policy-change"
],
"Remediation": {
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.py
index f5efd04dde..4347a9b3aa 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_policy_changes/cloudwatch_log_metric_filter_policy_changes.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,26 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_policy_changes(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?DeleteGroupPolicy.+\$\.eventName\s*=\s*.?DeleteRolePolicy.+\$\.eventName\s*=\s*.?DeleteUserPolicy.+\$\.eventName\s*=\s*.?PutGroupPolicy.+\$\.eventName\s*=\s*.?PutRolePolicy.+\$\.eventName\s*=\s*.?PutUserPolicy.+\$\.eventName\s*=\s*.?CreatePolicy.+\$\.eventName\s*=\s*.?DeletePolicy.+\$\.eventName\s*=\s*.?CreatePolicyVersion.+\$\.eventName\s*=\s*.?DeletePolicyVersion.+\$\.eventName\s*=\s*.?AttachRolePolicy.+\$\.eventName\s*=\s*.?DetachRolePolicy.+\$\.eventName\s*=\s*.?AttachUserPolicy.+\$\.eventName\s*=\s*.?DetachUserPolicy.+\$\.eventName\s*=\s*.?AttachGroupPolicy.+\$\.eventName\s*=\s*.?DetachGroupPolicy.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "DeleteGroupPolicy",
+ "DeleteRolePolicy",
+ "DeleteUserPolicy",
+ "PutGroupPolicy",
+ "PutRolePolicy",
+ "PutUserPolicy",
+ "CreatePolicy",
+ "DeletePolicy",
+ "CreatePolicyVersion",
+ "DeletePolicyVersion",
+ "AttachRolePolicy",
+ "DetachRolePolicy",
+ "AttachUserPolicy",
+ "DetachUserPolicy",
+ "AttachGroupPolicy",
+ "DetachGroupPolicy",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_security_group_changes/cloudwatch_log_metric_filter_security_group_changes.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_security_group_changes/cloudwatch_log_metric_filter_security_group_changes.py
index a7972e420c..3557632904 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_security_group_changes/cloudwatch_log_metric_filter_security_group_changes.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_security_group_changes/cloudwatch_log_metric_filter_security_group_changes.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,16 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_security_group_changes(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?AuthorizeSecurityGroupIngress.+\$\.eventName\s*=\s*.?AuthorizeSecurityGroupEgress.+\$\.eventName\s*=\s*.?RevokeSecurityGroupIngress.+\$\.eventName\s*=\s*.?RevokeSecurityGroupEgress.+\$\.eventName\s*=\s*.?CreateSecurityGroup.+\$\.eventName\s*=\s*.?DeleteSecurityGroup.?"
+ pattern = build_metric_filter_pattern(
+ event_names=[
+ "AuthorizeSecurityGroupIngress",
+ "AuthorizeSecurityGroupEgress",
+ "RevokeSecurityGroupIngress",
+ "RevokeSecurityGroupEgress",
+ "CreateSecurityGroup",
+ "DeleteSecurityGroup",
+ ],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.metadata.json b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.metadata.json
index 20058c1ed8..76ffd832ff 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.metadata.json
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.metadata.json
@@ -21,7 +21,6 @@
"https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html",
"https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/CloudWatchLogs/console-sign-in-without-mfa.html",
"https://www.tenable.com/audits/items/CIS_Amazon_Web_Services_Foundations_v3.0.0_L1.audit:1957056ee174cc38502d5f5f1864333b",
- "https://www.clouddefense.ai/compliance-rules/gdpr/data-protection/log-metric-filter-console-login-mfa",
"https://www.intelligentdiscovery.io/controls/cloudwatch/cloudwatch-alarm-no-mfa",
"https://support.icompaas.com/support/solutions/articles/62000083605-ensure-a-log-metric-filter-and-alarm-exist-for-management-console-sign-in-without-mfa"
],
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.py
index 8437600646..07475a6185 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_log_metric_filter_sign_in_without_mfa/cloudwatch_log_metric_filter_sign_in_without_mfa.py
@@ -6,6 +6,7 @@ from prowler.providers.aws.services.cloudwatch.cloudwatch_client import (
cloudwatch_client,
)
from prowler.providers.aws.services.cloudwatch.lib.metric_filters import (
+ build_metric_filter_pattern,
check_cloudwatch_log_metric_filter,
)
from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
@@ -13,7 +14,10 @@ from prowler.providers.aws.services.cloudwatch.logs_client import logs_client
class cloudwatch_log_metric_filter_sign_in_without_mfa(Check):
def execute(self):
- pattern = r"\$\.eventName\s*=\s*.?ConsoleLogin.+\$\.additionalEventData\.MFAUsed\s*!=\s*.?Yes.?"
+ pattern = build_metric_filter_pattern(
+ event_names=["ConsoleLogin"],
+ extra_clauses=[("additionalEventData.MFAUsed", "!=", "Yes")],
+ )
findings = []
report = check_cloudwatch_log_metric_filter(
diff --git a/prowler/providers/aws/services/cloudwatch/cloudwatch_service.py b/prowler/providers/aws/services/cloudwatch/cloudwatch_service.py
index 29ac103867..56b7ebe25c 100644
--- a/prowler/providers/aws/services/cloudwatch/cloudwatch_service.py
+++ b/prowler/providers/aws/services/cloudwatch/cloudwatch_service.py
@@ -6,6 +6,10 @@ from botocore.exceptions import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ limit_resources,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
@@ -83,8 +87,19 @@ class Logs(AWSService):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
self.log_group_arn_template = f"arn:{self.audited_partition}:logs:{self.region}:{self.audited_account}:log-group"
+ # Log groups are listed first, then only the selected subset is enriched
+ # and exposed for primary log group checks. Keep a complete lightweight
+ # index for cross-service evidence lookups.
+ self.all_log_groups = {}
self.log_groups = {}
+ self._log_groups_hydrated = set()
+ self.log_group_limit = get_resource_scan_limit(
+ self.audit_config, "max_cloudwatch_log_groups"
+ )
+ # The threshold for number of events to return per log group.
+ self.events_per_log_group_threshold = 1000
self.__threading_call__(self._describe_log_groups)
+ self._select_log_groups_for_analysis()
self.resource_policies = {}
self.__threading_call__(self._describe_resource_policies)
self.metric_filters = []
@@ -94,14 +109,27 @@ class Logs(AWSService):
"cloudwatch_log_group_no_secrets_in_logs"
in provider.audit_metadata.expected_checks
):
- self.events_per_log_group_threshold = (
- 1000 # The threshold for number of events to return per log group.
- )
- self.__threading_call__(self._get_log_events)
+ self.__threading_call__(self._get_log_events, self.log_groups.values())
self.__threading_call__(
self._list_tags_for_resource, self.log_groups.values()
)
+ def _select_log_groups_for_analysis(self):
+ """Select the newest log groups for bounded analysis."""
+ if not self.log_groups:
+ return
+ self.log_groups = {
+ log_group.arn: log_group
+ for log_group in limit_resources(
+ sorted(
+ self.log_groups.values(),
+ key=lambda lg: lg.creation_time or 0,
+ reverse=True,
+ ),
+ self.log_group_limit,
+ )
+ }
+
def _describe_metric_filters(self, regional_client):
logger.info("CloudWatch Logs - Describing metric filters...")
try:
@@ -118,11 +146,21 @@ class Logs(AWSService):
self.metric_filters = []
log_group = None
- for lg in self.log_groups.values():
- if lg.name == filter["logGroupName"]:
+ for lg in (self.all_log_groups or {}).values():
+ if (
+ lg.name == filter["logGroupName"]
+ and lg.region == regional_client.region
+ ):
log_group = lg
break
+ if (
+ log_group
+ and log_group.arn in (self.log_groups or {})
+ and log_group.arn not in self._log_groups_hydrated
+ ):
+ self._list_tags_for_resource(log_group)
+
self.metric_filters.append(
MetricFilter(
arn=arn,
@@ -156,9 +194,9 @@ class Logs(AWSService):
"describe_log_groups"
)
for page in describe_log_groups_paginator.paginate():
- for log_group in page["logGroups"]:
- if not self.audit_resources or (
- is_resource_filtered(log_group["arn"], self.audit_resources)
+ for log_group in page.get("logGroups", []):
+ if not self.audit_resources or is_resource_filtered(
+ log_group["arn"], self.audit_resources
):
never_expire = False
kms = log_group.get("kmsKeyId")
@@ -168,20 +206,26 @@ class Logs(AWSService):
retention_days = 9999
if self.log_groups is None:
self.log_groups = {}
- self.log_groups[log_group["arn"]] = LogGroup(
+ if self.all_log_groups is None:
+ self.all_log_groups = {}
+ log_group_object = LogGroup(
arn=log_group["arn"],
name=log_group["logGroupName"],
retention_days=retention_days,
never_expire=never_expire,
kms_id=kms,
+ creation_time=log_group.get("creationTime"),
region=regional_client.region,
)
+ self.all_log_groups[log_group_object.arn] = log_group_object
+ self.log_groups[log_group_object.arn] = log_group_object
except ClientError as error:
if error.response["Error"]["Code"] == "AccessDeniedException":
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
if not self.log_groups:
+ self.all_log_groups = None
self.log_groups = None
else:
logger.error(
@@ -192,37 +236,29 @@ class Logs(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- def _get_log_events(self, regional_client):
- regional_log_groups = [
- log_group
- for log_group in self.log_groups.values()
- if log_group.region == regional_client.region
- ]
- total_log_groups = len(regional_log_groups)
+ def _get_log_events(self, log_group):
+ """Retrieve recent log events for a selected log group.
+
+ Args:
+ log_group: Log group selected for bounded analysis.
+ """
logger.info(
- f"CloudWatch Logs - Retrieving log events for {total_log_groups} log groups in {regional_client.region}..."
+ f"CloudWatch Logs - Retrieving log events for log group {log_group.name}..."
)
try:
- for count, log_group in enumerate(regional_log_groups, start=1):
- events = regional_client.filter_log_events(
- logGroupName=log_group.name,
- limit=self.events_per_log_group_threshold,
- )["events"]
- for event in events:
- if event["logStreamName"] not in log_group.log_streams:
- log_group.log_streams[event["logStreamName"]] = []
- log_group.log_streams[event["logStreamName"]].append(event)
- if count % 10 == 0:
- logger.info(
- f"CloudWatch Logs - Retrieved log events for {count}/{total_log_groups} log groups in {regional_client.region}..."
- )
+ regional_client = self.regional_clients[log_group.region]
+ events = regional_client.filter_log_events(
+ logGroupName=log_group.name,
+ limit=self.events_per_log_group_threshold,
+ )["events"]
+ for event in events:
+ if event["logStreamName"] not in log_group.log_streams:
+ log_group.log_streams[event["logStreamName"]] = []
+ log_group.log_streams[event["logStreamName"]].append(event)
except Exception as error:
logger.error(
- f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"{log_group.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- logger.info(
- f"CloudWatch Logs - Finished retrieving log events in {regional_client.region}..."
- )
def _describe_resource_policies(self, regional_client):
logger.info("CloudWatch Logs - Describing resource policies...")
@@ -257,6 +293,13 @@ class Logs(AWSService):
)
def _list_tags_for_resource(self, log_group):
+ """Hydrate tags for a selected log group once.
+
+ Args:
+ log_group: Log group selected for tag hydration.
+ """
+ if log_group.arn in self._log_groups_hydrated:
+ return
logger.info(f"CloudWatch Logs - List Tags for Log Group {log_group.name}...")
try:
regional_client = self.regional_clients[log_group.region]
@@ -264,6 +307,7 @@ class Logs(AWSService):
resourceArn=log_group.arn
)["tags"]
log_group.tags = [response]
+ self._log_groups_hydrated.add(log_group.arn)
except ClientError as error:
if error.response["Error"]["Code"] == "ResourceNotFoundException":
logger.warning(
@@ -292,6 +336,7 @@ class LogGroup(BaseModel):
retention_days: int
never_expire: bool
kms_id: Optional[str]
+ creation_time: Optional[int] = None
region: str
log_streams: dict[str, list[str]] = (
{}
diff --git a/prowler/providers/aws/services/cloudwatch/lib/metric_filters.py b/prowler/providers/aws/services/cloudwatch/lib/metric_filters.py
index 84d70b4083..e5d104b840 100644
--- a/prowler/providers/aws/services/cloudwatch/lib/metric_filters.py
+++ b/prowler/providers/aws/services/cloudwatch/lib/metric_filters.py
@@ -3,6 +3,45 @@ import re
from prowler.lib.check.models import Check_Report_AWS
+def build_metric_filter_pattern(
+ *,
+ event_names: list[str] | None = None,
+ event_source: str | None = None,
+ extra_clauses: list[tuple[str, str, str]] | None = None,
+) -> str:
+ """Build a regex pattern to match a CloudWatch Logs filterPattern string.
+
+ All clauses must be present for the pattern to match, regardless of the
+ order in which AWS stores them. Event names are matched exactly, so a
+ short name like ``CreateRoute`` will not be satisfied by a longer one
+ like ``CreateRouteTable``.
+
+ Pass the result directly to ``check_cloudwatch_log_metric_filter``.
+
+ Args:
+ event_names: AWS API action names to require (``$.eventName``).
+ event_source: optional service principal to require (``$.eventSource``),
+ e.g. ``"ec2.amazonaws.com"``.
+ extra_clauses: additional conditions as ``(field, operator, value)``
+ tuples, where ``operator`` is ``"="`` or ``"!="``. Example:
+ ``("additionalEventData.MFAUsed", "!=", "Yes")``.
+
+ Returns:
+ A regex string for use with ``re.search(..., flags=re.DOTALL)``.
+ """
+ parts: list[str] = []
+ if event_source is not None:
+ parts.append(rf"(?=.*\$\.eventSource\s*=\s*.?{re.escape(event_source)})")
+ for name in event_names or []:
+ parts.append(rf"(?=.*\$\.eventName\s*=\s*.?{re.escape(name)}\b)")
+ for field, operator, value in extra_clauses or []:
+ if operator not in ("=", "!="):
+ raise ValueError(f"unsupported operator {operator!r}; expected '=' or '!='")
+ op = r"\s*!=\s*" if operator == "!=" else r"\s*=\s*"
+ parts.append(rf"(?=.*\$\.{re.escape(field)}{op}.?{re.escape(value)})")
+ return "".join(parts)
+
+
def check_cloudwatch_log_metric_filter(
metric_filter_pattern: str,
trails: list,
diff --git a/prowler/providers/aws/services/codeartifact/codeartifact_service.py b/prowler/providers/aws/services/codeartifact/codeartifact_service.py
index 1465092063..9a13e8fcf7 100644
--- a/prowler/providers/aws/services/codeartifact/codeartifact_service.py
+++ b/prowler/providers/aws/services/codeartifact/codeartifact_service.py
@@ -1,10 +1,14 @@
from enum import Enum
-from typing import Optional
+from typing import Iterator, Optional, Tuple
from botocore.exceptions import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ iter_limited_paginator_items,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
@@ -15,9 +19,18 @@ class CodeArtifact(AWSService):
super().__init__(__class__.__name__, provider)
# repositories is a dictionary containing all the codeartifact service information
self.repositories = {}
+ # repository ARNs whose selected packages have been listed and memoized
+ # into repository.packages.
+ self._packages_listed = set()
+ self.package_limit = get_resource_scan_limit(
+ self.audit_config, "max_codeartifact_packages"
+ )
self.__threading_call__(self._list_repositories)
- self.__threading_call__(self._list_packages)
- self._list_tags_for_resource()
+ for _ in self._load_packages_for_analysis():
+ pass
+ self.__threading_call__(
+ self._list_tags_for_resource, self.repositories.values()
+ )
def _list_repositories(self, regional_client):
logger.info("CodeArtifact - Listing Repositories...")
@@ -51,134 +64,146 @@ class CodeArtifact(AWSService):
f" {error}"
)
- def _list_packages(self, regional_client):
- logger.info("CodeArtifact - Listing Packages and retrieving information...")
- for repository in self.repositories:
- try:
- if self.repositories[repository].region == regional_client.region:
- list_packages_paginator = regional_client.get_paginator(
- "list_packages"
+ def _iter_repository_packages(
+ self, repository, limit: Optional[int] = None
+ ) -> Iterator["Package"]:
+ """Yield packages for a single repository, hydrating each one lazily.
+
+ Each package requires an extra ``list_package_versions`` call to
+ resolve its latest version, so producing them lazily lets the resource
+ limit stop before extra package version calls.
+ """
+ regional_client = self.regional_clients[repository.region]
+ try:
+ list_packages_paginator = regional_client.get_paginator("list_packages")
+ list_packages_parameters = {
+ "domain": repository.domain_name,
+ "domainOwner": repository.domain_owner,
+ "repository": repository.name,
+ }
+ for package in iter_limited_paginator_items(
+ list_packages_paginator,
+ "packages",
+ limit,
+ **list_packages_parameters,
+ ):
+ # Package information
+ package_format = package["format"]
+ package_namespace = package.get("namespace")
+ package_name = package["package"]
+ package_origin_configuration_restrictions_publish = package[
+ "originConfiguration"
+ ]["restrictions"]["publish"]
+ package_origin_configuration_restrictions_upstream = package[
+ "originConfiguration"
+ ]["restrictions"]["upstream"]
+ # Get Latest Package Version
+ list_package_versions_parameters = {
+ "domain": repository.domain_name,
+ "domainOwner": repository.domain_owner,
+ "repository": repository.name,
+ "format": package_format,
+ "package": package_name,
+ "sortBy": "PUBLISHED_TIME",
+ "maxResults": 1,
+ }
+ if package_namespace:
+ list_package_versions_parameters["namespace"] = package_namespace
+ latest_version_information = regional_client.list_package_versions(
+ **list_package_versions_parameters
+ )
+ latest_version = ""
+ latest_origin_type = "UNKNOWN"
+ latest_status = "Published"
+ if latest_version_information.get("versions"):
+ latest_version = latest_version_information["versions"][0].get(
+ "version"
)
- list_packages_parameters = {
- "domain": self.repositories[repository].domain_name,
- "domainOwner": self.repositories[repository].domain_owner,
- "repository": self.repositories[repository].name,
- }
- packages = []
- for page in list_packages_paginator.paginate(
- **list_packages_parameters
- ):
- for package in page["packages"]:
- # Package information
- package_format = package["format"]
- package_namespace = package.get("namespace")
- package_name = package["package"]
- package_origin_configuration_restrictions_publish = package[
- "originConfiguration"
- ]["restrictions"]["publish"]
- package_origin_configuration_restrictions_upstream = (
- package["originConfiguration"]["restrictions"][
- "upstream"
- ]
- )
- # Get Latest Package Version
- if package_namespace:
- latest_version_information = (
- regional_client.list_package_versions(
- domain=self.repositories[
- repository
- ].domain_name,
- domainOwner=self.repositories[
- repository
- ].domain_owner,
- repository=self.repositories[repository].name,
- format=package_format,
- namespace=package_namespace,
- package=package_name,
- sortBy="PUBLISHED_TIME",
- maxResults=1,
- )
- )
- else:
- latest_version_information = (
- regional_client.list_package_versions(
- domain=self.repositories[
- repository
- ].domain_name,
- domainOwner=self.repositories[
- repository
- ].domain_owner,
- repository=self.repositories[repository].name,
- format=package_format,
- package=package_name,
- sortBy="PUBLISHED_TIME",
- maxResults=1,
- )
- )
- latest_version = ""
- latest_origin_type = "UNKNOWN"
- latest_status = "Published"
- if latest_version_information.get("versions"):
- latest_version = latest_version_information["versions"][
- 0
- ].get("version")
- latest_origin_type = (
- latest_version_information["versions"][0]
- .get("origin", {})
- .get("originType", "UNKNOWN")
- )
- latest_status = latest_version_information["versions"][
- 0
- ].get("status", "Published")
-
- packages.append(
- Package(
- name=package_name,
- namespace=package_namespace,
- format=package_format,
- origin_configuration=OriginConfiguration(
- restrictions=Restrictions(
- publish=package_origin_configuration_restrictions_publish,
- upstream=package_origin_configuration_restrictions_upstream,
- )
- ),
- latest_version=LatestPackageVersion(
- version=latest_version,
- status=latest_status,
- origin=OriginInformation(
- origin_type=latest_origin_type
- ),
- ),
- )
- )
- # Save all the packages information
- self.repositories[repository].packages = packages
-
- except ClientError as error:
- if error.response["Error"]["Code"] == "ResourceNotFoundException":
- logger.warning(
- f"{regional_client.region} --"
- f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
- f" {error}"
+ latest_origin_type = (
+ latest_version_information["versions"][0]
+ .get("origin", {})
+ .get("originType", "UNKNOWN")
+ )
+ latest_status = latest_version_information["versions"][0].get(
+ "status", "Published"
)
- continue
- except Exception as error:
- logger.error(
- f"{regional_client.region} --"
+ yield Package(
+ name=package_name,
+ namespace=package_namespace,
+ format=package_format,
+ origin_configuration=OriginConfiguration(
+ restrictions=Restrictions(
+ publish=package_origin_configuration_restrictions_publish,
+ upstream=package_origin_configuration_restrictions_upstream,
+ )
+ ),
+ latest_version=LatestPackageVersion(
+ version=latest_version,
+ status=latest_status,
+ origin=OriginInformation(origin_type=latest_origin_type),
+ ),
+ )
+
+ except ClientError as error:
+ if error.response["Error"]["Code"] == "ResourceNotFoundException":
+ logger.warning(
+ f"{repository.region} --"
f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
f" {error}"
)
+ else:
+ logger.error(
+ f"{repository.region} --"
+ f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
+ f" {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{repository.region} --"
+ f" {error.__class__.__name__}[{error.__traceback__.tb_lineno}]:"
+ f" {error}"
+ )
- def _list_tags_for_resource(self):
+ def _load_packages_for_analysis(self) -> Iterator[Tuple["Repository", "Package"]]:
+ """Yield the ``(repository, package)`` pairs selected for analysis.
+
+ Package listing stays in the service layer so checks receive only the
+ selected packages and remain unaware of resource-analysis limits.
+ """
+ yielded = 0
+ for repository in list(self.repositories.values()):
+ if repository.arn in self._packages_listed:
+ for package in repository.packages:
+ yield repository, package
+ yielded += 1
+ if self.package_limit and yielded >= self.package_limit:
+ return
+ continue
+ collected = []
+ remaining_limit = None
+ if self.package_limit:
+ remaining_limit = self.package_limit - yielded
+ if remaining_limit <= 0:
+ return
+ for package in self._iter_repository_packages(repository, remaining_limit):
+ collected.append(package)
+ repository.packages = collected
+ yield repository, package
+ yielded += 1
+ if self.package_limit and yielded >= self.package_limit:
+ self._packages_listed.add(repository.arn)
+ return
+ self._packages_listed.add(repository.arn)
+
+ def _list_tags_for_resource(self, repository):
logger.info("CodeArtifact - List Tags...")
try:
- for repository in self.repositories.values():
- regional_client = self.regional_clients[repository.region]
- response = regional_client.list_tags_for_resource(
- resourceArn=repository.arn
- )["tags"]
- repository.tags = response
+ regional_client = self.regional_clients[repository.region]
+ response = regional_client.list_tags_for_resource(
+ resourceArn=repository.arn
+ )["tags"]
+ repository.tags = response
except Exception as error:
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
diff --git a/prowler/providers/aws/services/codebuild/codebuild_project_no_secrets_in_variables/codebuild_project_no_secrets_in_variables.py b/prowler/providers/aws/services/codebuild/codebuild_project_no_secrets_in_variables/codebuild_project_no_secrets_in_variables.py
index 8d031cc25a..2e0c5863eb 100644
--- a/prowler/providers/aws/services/codebuild/codebuild_project_no_secrets_in_variables/codebuild_project_no_secrets_in_variables.py
+++ b/prowler/providers/aws/services/codebuild/codebuild_project_no_secrets_in_variables/codebuild_project_no_secrets_in_variables.py
@@ -1,7 +1,11 @@
import json
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.codebuild.codebuild_client import codebuild_client
@@ -14,35 +18,71 @@ class codebuild_project_no_secrets_in_variables(Check):
secrets_ignore_patterns = codebuild_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for project in codebuild_client.projects.values():
+ validate = codebuild_client.audit_config.get("secrets_validate", False)
+ projects = list(codebuild_client.projects.values())
+
+ # Collect every scannable plaintext variable across all projects and scan
+ # them in batched Kingfisher invocations instead of one subprocess per
+ # variable. Findings are keyed by (project index, variable index).
+ def payloads():
+ for project_index, project in enumerate(projects):
+ if project.environment_variables:
+ for var_index, env_var in enumerate(project.environment_variables):
+ if (
+ env_var.type == "PLAINTEXT"
+ and env_var.name not in sensitive_vars_excluded
+ ):
+ yield (project_index, var_index), json.dumps(
+ {env_var.name: env_var.value}
+ )
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for project_index, project in enumerate(projects):
report = Check_Report_AWS(metadata=self.metadata(), resource=project)
report.status = "PASS"
report.status_extended = f"CodeBuild project {project.name} does not have sensitive environment plaintext credentials."
secrets_found = []
+ all_secrets = []
+
+ if scan_error and any(
+ env_var.type == "PLAINTEXT"
+ and env_var.name not in sensitive_vars_excluded
+ for env_var in project.environment_variables or []
+ ):
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan CodeBuild project {project.name} environment "
+ f"variables for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
if project.environment_variables:
- for env_var in project.environment_variables:
- if (
- env_var.type == "PLAINTEXT"
- and env_var.name not in sensitive_vars_excluded
- ):
- detect_secrets_output = detect_secrets_scan(
- data=json.dumps({env_var.name: env_var.value}),
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=codebuild_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
- if detect_secrets_output:
- secrets_info = [
+ for var_index, env_var in enumerate(project.environment_variables):
+ detect_secrets_output = batch_results.get(
+ (project_index, var_index)
+ )
+ if detect_secrets_output:
+ all_secrets.extend(detect_secrets_output)
+ secrets_found.extend(
+ [
f"{secret['type']} in variable {env_var.name}"
for secret in detect_secrets_output
]
- secrets_found.extend(secrets_info)
+ )
if secrets_found:
report.status = "FAIL"
report.status_extended = f"CodeBuild project {project.name} has sensitive environment plaintext credentials in variables: {', '.join(secrets_found)}."
+ annotate_verified_secrets(report, all_secrets)
findings.append(report)
diff --git a/prowler/providers/aws/services/codepipeline/codepipeline_project_repo_private/codepipeline_project_repo_private.py b/prowler/providers/aws/services/codepipeline/codepipeline_project_repo_private/codepipeline_project_repo_private.py
index 0c745fc658..bc9f569f1b 100644
--- a/prowler/providers/aws/services/codepipeline/codepipeline_project_repo_private/codepipeline_project_repo_private.py
+++ b/prowler/providers/aws/services/codepipeline/codepipeline_project_repo_private/codepipeline_project_repo_private.py
@@ -7,6 +7,8 @@ from prowler.providers.aws.services.codepipeline.codepipeline_client import (
codepipeline_client,
)
+HTTP_TIMEOUT = 30
+
class codepipeline_project_repo_private(Check):
"""Checks if AWS CodePipeline source repositories are configured as private.
@@ -87,9 +89,8 @@ class codepipeline_project_repo_private(Check):
repo_url = repo_url[:-4]
try:
- context = ssl._create_unverified_context()
req = urllib.request.Request(repo_url, method="HEAD")
- response = urllib.request.urlopen(req, context=context)
+ response = urllib.request.urlopen(req, timeout=HTTP_TIMEOUT)
return not response.geturl().endswith("sign_in")
- except (urllib.error.HTTPError, urllib.error.URLError):
+ except (urllib.error.URLError, TimeoutError, ssl.SSLError):
return False
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_weekly/__init__.py b/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_cluster_check_weekly/__init__.py
rename to prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/__init__.py
diff --git a/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.metadata.json b/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.metadata.json
new file mode 100644
index 0000000000..cbbd7a66dd
--- /dev/null
+++ b/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.metadata.json
@@ -0,0 +1,44 @@
+{
+ "Provider": "aws",
+ "CheckID": "config_delegated_admin_and_org_aggregator_all_regions",
+ "CheckTitle": "AWS Config has a delegated administrator and an organization aggregator covering all AWS regions",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices"
+ ],
+ "ServiceName": "config",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "AwsConfigConfigurationAggregator",
+ "ResourceGroup": "governance",
+ "Description": "**AWS Config** has a delegated administrator registered via AWS Organizations and at least one Configuration Aggregator with an OrganizationAggregationSource that covers all AWS regions, ensuring centralized org-wide configuration visibility.",
+ "Risk": "Without an org-wide **AWS Config** aggregator and a delegated administrator, configuration data is fragmented across accounts and regions, **compliance reporting** is incomplete, and **drift detection** is delayed. Adversaries or misconfigurations can persist in unmonitored accounts, eroding **audit readiness** and **regulatory posture**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html",
+ "https://docs.aws.amazon.com/config/latest/developerguide/set-up-aggregator-cli.html",
+ "https://docs.aws.amazon.com/organizations/latest/userguide/services-that-can-integrate-config.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws organizations register-delegated-administrator --account-id <ADMIN_ACCOUNT_ID> --service-principal config.amazonaws.com && aws configservice put-configuration-aggregator --configuration-aggregator-name org-aggregator --organization-aggregation-source RoleArn=<ROLE_ARN>,AllAwsRegions=true",
+ "NativeIaC": "",
+ "Other": "1. From the AWS Organizations management account, register the delegated administrator for config.amazonaws.com\n2. In the delegated admin account, open AWS Config\n3. Create a Configuration Aggregator and select Add my organization as the source\n4. Enable Include all AWS Regions\n5. Confirm an IAM role with AWSConfigRoleForOrganizations is attached\n6. Verify the aggregator status reaches SUCCEEDED for all member accounts",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Register a **delegated administrator** for AWS Config via AWS Organizations and create at least one **Configuration Aggregator** with an OrganizationAggregationSource that covers **all AWS regions**. This centralizes configuration data across the organization for unified compliance and audit reporting.",
+ "Url": "https://hub.prowler.com/check/config_delegated_admin_and_org_aggregator_all_regions"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "config_recorder_all_regions_enabled",
+ "guardduty_delegated_admin_enabled_all_regions"
+ ],
+ "Notes": "This check requires execution from the organization management account or delegated administrator account to access organization-level APIs."
+}
diff --git a/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.py b/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.py
new file mode 100644
index 0000000000..f56ea191f8
--- /dev/null
+++ b/prowler/providers/aws/services/config/config_delegated_admin_and_org_aggregator_all_regions/config_delegated_admin_and_org_aggregator_all_regions.py
@@ -0,0 +1,115 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.config.config_client import config_client
+from prowler.providers.aws.services.config.config_service import Aggregator
+
+
+class config_delegated_admin_and_org_aggregator_all_regions(Check):
+ """Ensure AWS Config has a delegated admin and an org aggregator covering all regions.
+
+ This check verifies that:
+ 1. A delegated administrator is registered for the config.amazonaws.com
+ service principal via AWS Organizations.
+ 2. At least one AWS Config Configuration Aggregator exists with an
+ OrganizationAggregationSource that covers all AWS regions
+ (AllAwsRegions=true).
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports containing the result of the check. One finding per
+ aggregator-region, or a single synthetic FAIL when no aggregators
+ exist in any region.
+ """
+ findings = []
+
+ has_delegated_admin = (
+ bool(config_client.delegated_administrators)
+ and not config_client.delegated_administrators_lookup_failed
+ )
+ delegated_admin_unknown = config_client.delegated_administrators_lookup_failed
+
+ # No aggregators in any region: emit one synthetic FAIL anchored to the
+ # audited account in the default region.
+ if not config_client.aggregators:
+ synthetic = Aggregator(
+ name="unknown",
+ arn=config_client.get_unknown_arn(
+ region=config_client.region,
+ resource_type="config-aggregator",
+ ),
+ region=config_client.region,
+ all_aws_regions=False,
+ aws_regions=None,
+ organization_aggregation_source_present=False,
+ )
+ report = Check_Report_AWS(metadata=self.metadata(), resource=synthetic)
+ if delegated_admin_unknown:
+ delegated_state = (
+ "delegated administrator status could not be determined"
+ )
+ elif has_delegated_admin:
+ delegated_state = "delegated administrator configured"
+ else:
+ delegated_state = (
+ "no delegated administrator registered for config.amazonaws.com"
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"AWS Config has no Organization Aggregator configured in any "
+ f"region ({delegated_state})."
+ )
+ findings.append(report)
+ return findings
+
+ for region, aggregators_in_region in config_client.aggregators.items():
+ for aggregator in aggregators_in_region:
+ report = Check_Report_AWS(metadata=self.metadata(), resource=aggregator)
+
+ org_aware = aggregator.organization_aggregation_source_present
+ covers_all = aggregator.all_aws_regions
+
+ issues = []
+ if delegated_admin_unknown:
+ issues.append(
+ "delegated administrator status for config.amazonaws.com "
+ "could not be determined"
+ )
+ elif not has_delegated_admin:
+ issues.append(
+ "no delegated administrator registered for config.amazonaws.com"
+ )
+ if not org_aware:
+ issues.append(
+ f"aggregator {aggregator.name} is not an organization aggregator"
+ )
+ elif not covers_all:
+ issues.append(
+ f"aggregator {aggregator.name} does not cover all AWS regions"
+ )
+
+ if issues:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"AWS Config aggregator {aggregator.name} in region "
+ f"{region} has issues: {', '.join(issues)}."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"AWS Config aggregator {aggregator.name} in region "
+ f"{region} is an organization aggregator covering all "
+ f"AWS regions with delegated admin configured."
+ )
+
+ # Support muting non-default regions if configured
+ if report.status == "FAIL" and (
+ config_client.audit_config.get("mute_non_default_regions", False)
+ and region != config_client.region
+ ):
+ report.muted = True
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/config/config_service.py b/prowler/providers/aws/services/config/config_service.py
index 443cee2233..85ab22fd8e 100644
--- a/prowler/providers/aws/services/config/config_service.py
+++ b/prowler/providers/aws/services/config/config_service.py
@@ -1,5 +1,6 @@
from typing import Optional
+from botocore.client import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
@@ -12,10 +13,16 @@ class Config(AWSService):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
self.recorders = {}
+ self.aggregators: dict[str, list] = {}
+ self.delegated_administrators: list = []
+ self.delegated_administrators_lookup_failed: bool = False
self.__threading_call__(self.describe_configuration_recorders)
self.__threading_call__(
self._describe_configuration_recorder_status, self.recorders.values()
)
+ self.__threading_call__(self._describe_configuration_aggregators)
+ # Organizations API is not regional; single call.
+ self._list_config_delegated_administrators()
def _get_recorder_arn_template(self, region):
return f"arn:{self.audited_partition}:config:{region}:{self.audited_account}:recorder"
@@ -73,6 +80,108 @@ class Config(AWSService):
f"{recorder.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _describe_configuration_aggregators(self, regional_client):
+ """Describe AWS Config configuration aggregators per region.
+
+ An aggregator counts as organization-aware when its
+ OrganizationAggregationSource key is present in the response.
+ """
+ logger.info("Config - Describing Configuration Aggregators...")
+ try:
+ paginator = regional_client.get_paginator(
+ "describe_configuration_aggregators"
+ )
+ region_aggregators: list = []
+ for page in paginator.paginate():
+ for aggregator in page.get("ConfigurationAggregators", []):
+ name = aggregator.get("ConfigurationAggregatorName", "")
+ arn = aggregator.get("ConfigurationAggregatorArn", "")
+ org_source = aggregator.get("OrganizationAggregationSource")
+ org_aware = org_source is not None
+ all_aws_regions = False
+ aws_regions: Optional[list] = None
+ if org_aware:
+ all_aws_regions = org_source.get("AllAwsRegions", False)
+ aws_regions = org_source.get("AwsRegions")
+ if not self.audit_resources or (
+ is_resource_filtered(arn, self.audit_resources)
+ ):
+ region_aggregators.append(
+ Aggregator(
+ name=name,
+ arn=arn,
+ region=regional_client.region,
+ all_aws_regions=all_aws_regions,
+ aws_regions=aws_regions,
+ organization_aggregation_source_present=org_aware,
+ )
+ )
+ if region_aggregators:
+ self.aggregators[regional_client.region] = region_aggregators
+ except ClientError as error:
+ if error.response["Error"]["Code"] in (
+ "AccessDeniedException",
+ "AccessDenied",
+ ):
+ logger.warning(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ else:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _list_config_delegated_administrators(self):
+ """List delegated administrators for the AWS Config service principal.
+
+ Uses the Organizations API directly (not regional). Sets
+ delegated_administrators_lookup_failed to True on AccessDenied so callers
+ can surface the unknown delegated-admin state in findings.
+ """
+ logger.info(
+ "Config - Listing delegated administrators for config.amazonaws.com..."
+ )
+ try:
+ org_client = self.session.client("organizations")
+ paginator = org_client.get_paginator("list_delegated_administrators")
+ for page in paginator.paginate(ServicePrincipal="config.amazonaws.com"):
+ for admin in page.get("DelegatedAdministrators", []):
+ self.delegated_administrators.append(
+ ConfigDelegatedAdministrator(
+ id=admin.get("Id", ""),
+ arn=admin.get("Arn", ""),
+ name=admin.get("Name", ""),
+ email=admin.get("Email", ""),
+ status=admin.get("Status", ""),
+ joined_method=admin.get("JoinedMethod", ""),
+ )
+ )
+ except ClientError as error:
+ error_code = error.response["Error"]["Code"]
+ if error_code in (
+ "AccessDeniedException",
+ "AccessDenied",
+ "AWSOrganizationsNotInUseException",
+ ):
+ self.delegated_administrators_lookup_failed = True
+ logger.warning(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ else:
+ self.delegated_administrators_lookup_failed = True
+ logger.error(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ self.delegated_administrators_lookup_failed = True
+ logger.error(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
class Recorder(BaseModel):
name: str
@@ -80,3 +189,25 @@ class Recorder(BaseModel):
recording: Optional[bool]
last_status: Optional[str]
region: str
+
+
+class Aggregator(BaseModel):
+ """Represents an AWS Config Configuration Aggregator."""
+
+ name: str
+ arn: str
+ region: str
+ all_aws_regions: bool = False
+ aws_regions: Optional[list] = None
+ organization_aggregation_source_present: bool = False
+
+
+class ConfigDelegatedAdministrator(BaseModel):
+ """Represents a delegated administrator registered for config.amazonaws.com."""
+
+ id: str
+ arn: str
+ name: str
+ email: str
+ status: str
+ joined_method: str
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_dashboard_disabled/__init__.py b/prowler/providers/aws/services/datapipeline/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_dashboard_disabled/__init__.py
rename to prowler/providers/aws/services/datapipeline/__init__.py
diff --git a/prowler/providers/aws/services/datapipeline/datapipeline_client.py b/prowler/providers/aws/services/datapipeline/datapipeline_client.py
new file mode 100644
index 0000000000..4732a559a5
--- /dev/null
+++ b/prowler/providers/aws/services/datapipeline/datapipeline_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.aws.services.datapipeline.datapipeline_service import (
+ DataPipeline,
+)
+from prowler.providers.common.provider import Provider
+
+datapipeline_client = DataPipeline(Provider.get_global_provider())
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_eni_multiple_ip_enabled/__init__.py b/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_eni_multiple_ip_enabled/__init__.py
rename to prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/__init__.py
diff --git a/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.metadata.json b/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.metadata.json
new file mode 100644
index 0000000000..cadafedfa9
--- /dev/null
+++ b/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "aws",
+ "CheckID": "datapipeline_pipeline_no_secrets_in_definition",
+ "CheckTitle": "Data Pipeline definition has no sensitive credentials",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "TTPs/Credential Access",
+ "Effects/Data Exposure",
+ "Sensitive Data Identifications/Security"
+ ],
+ "ServiceName": "datapipeline",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "arn:partition:datapipeline:region:account-id:pipeline/pipeline-id",
+ "Severity": "high",
+ "ResourceType": "AwsDataPipelinePipeline",
+ "ResourceGroup": "analytics",
+ "Description": "AWS Data Pipeline definitions are inspected for hardcoded secrets, such as keys, tokens, passwords, or database credentials embedded directly in pipeline objects, parameters, or parameter values.",
+ "Risk": "Plaintext secrets in Data Pipeline definitions can be viewed by users with pipeline read permissions and may leak through scripts, SQL commands, logs, or exported definitions. Exposed credentials can enable unauthorized access to databases, storage, and downstream systems.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/datapipeline/latest/APIReference/API_GetPipelineDefinition.html",
+ "https://docs.aws.amazon.com/datapipeline/latest/DeveloperGuide/dp-object-pipeline.html",
+ "https://docs.prowler.com/developer-guide/secret-scanning-checks"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Review the Data Pipeline definition.\n2. Remove hardcoded credentials from pipeline objects, parameter objects, and parameter values.\n3. Store secrets in AWS Secrets Manager or AWS Systems Manager Parameter Store.\n4. Grant the pipeline role least-privilege access to retrieve secrets securely at runtime.\n5. Rotate any exposed credentials.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Avoid embedding secrets in AWS Data Pipeline definitions. Store sensitive values in AWS Secrets Manager or AWS Systems Manager Parameter Store and reference them securely at runtime with least-privilege IAM permissions.",
+ "Url": "https://hub.prowler.com/check/datapipeline_pipeline_no_secrets_in_definition"
+ }
+ },
+ "Categories": [
+ "secrets"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "AWS Data Pipeline has been closed to new customers since July 25, 2024. Accounts without pre-existing pipelines will not return findings for this check, as the service cannot be used by new customers."
+}
diff --git a/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.py b/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.py
new file mode 100644
index 0000000000..1e6a60facd
--- /dev/null
+++ b/prowler/providers/aws/services/datapipeline/datapipeline_pipeline_no_secrets_in_definition/datapipeline_pipeline_no_secrets_in_definition.py
@@ -0,0 +1,112 @@
+import json
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.datapipeline.datapipeline_client import (
+ datapipeline_client,
+)
+
+
+class datapipeline_pipeline_no_secrets_in_definition(Check):
+ """Check that AWS Data Pipeline definitions contain no hardcoded secrets."""
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the Data Pipeline definition secret scan."""
+ findings = []
+ secrets_ignore_patterns = datapipeline_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = datapipeline_client.audit_config.get("secrets_validate", False)
+ pipelines = list(datapipeline_client.pipelines.values())
+ line_context_by_pipeline = {}
+ payloads = []
+ for pipeline_index, pipeline in enumerate(pipelines):
+ payload, line_context = _build_definition_payload(pipeline.definition)
+ line_context_by_pipeline[pipeline_index] = line_context
+ if payload:
+ payloads.append((pipeline_index, payload))
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads, excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for pipeline_index, pipeline in enumerate(pipelines):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=pipeline)
+ report.resource_tags = pipeline.tags
+ report.status = "PASS"
+ report.status_extended = (
+ f"No secrets found in Data Pipeline {pipeline.name} definition."
+ )
+
+ line_context = line_context_by_pipeline.get(pipeline_index, {})
+ if line_context:
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Data Pipeline {pipeline.name} definition "
+ f"for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ detect_secrets_output = batch_results.get(pipeline_index)
+ if detect_secrets_output:
+ secrets_string = ", ".join(
+ [
+ f"{secret['type']} in {line_context.get(secret['line_number'], 'definition')}"
+ for secret in detect_secrets_output
+ ]
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Potential {'secrets' if len(detect_secrets_output) > 1 else 'secret'} "
+ f"found in Data Pipeline {pipeline.name} definition -> {secrets_string}."
+ )
+ annotate_verified_secrets(report, detect_secrets_output)
+
+ findings.append(report)
+ return findings
+
+
+def _build_definition_payload(definition: dict) -> tuple[str, dict[int, str]]:
+ """Build a line-oriented scan payload and map each line to a definition field."""
+ lines = []
+ line_context = {}
+
+ def add_line(context: str, value) -> None:
+ if value is None:
+ return
+ lines.append(json.dumps({context: value}))
+ line_context[len(lines)] = context
+
+ for pipeline_object in definition.get("pipelineObjects", []):
+ object_name = pipeline_object.get("name") or pipeline_object.get("id")
+ for field in pipeline_object.get("fields", []):
+ field_name = field.get("key")
+ field_value = field.get("stringValue") or field.get("refValue")
+ add_line(f"object {object_name} field {field_name}", field_value)
+
+ for parameter_object in definition.get("parameterObjects", []):
+ parameter_name = parameter_object.get("id")
+ for attribute in parameter_object.get("attributes", []):
+ attribute_name = attribute.get("key")
+ attribute_value = attribute.get("stringValue")
+ add_line(
+ f"parameter object {parameter_name} attribute {attribute_name}",
+ attribute_value,
+ )
+
+ for parameter_value in definition.get("parameterValues", []):
+ parameter_id = parameter_value.get("id")
+ add_line(f"parameter value {parameter_id}", parameter_value.get("stringValue"))
+
+ return "\n".join(lines), line_context
diff --git a/prowler/providers/aws/services/datapipeline/datapipeline_service.py b/prowler/providers/aws/services/datapipeline/datapipeline_service.py
new file mode 100644
index 0000000000..c893dd0557
--- /dev/null
+++ b/prowler/providers/aws/services/datapipeline/datapipeline_service.py
@@ -0,0 +1,96 @@
+from botocore.exceptions import ClientError
+from pydantic.v1 import BaseModel, Field
+
+from prowler.lib.logger import logger
+from prowler.lib.scan_filters.scan_filters import is_resource_filtered
+from prowler.providers.aws.lib.service.service import AWSService
+
+
+class Pipeline(BaseModel):
+ """Represents an AWS Data Pipeline pipeline."""
+
+ id: str
+ name: str
+ arn: str
+ region: str
+ definition: dict = Field(default_factory=dict)
+ tags: list[dict] = Field(default_factory=list)
+
+
+class DataPipeline(AWSService):
+ """AWS Data Pipeline service class to list pipelines and definitions."""
+
+ def __init__(self, provider):
+ """Initialize the AWS Data Pipeline service."""
+ super().__init__(__class__.__name__, provider)
+ self.pipelines = {}
+ self.__threading_call__(self._list_pipelines)
+ if self.pipelines:
+ self.__threading_call__(
+ self._get_pipeline_definition, self.pipelines.values()
+ )
+
+ def _list_pipelines(self, regional_client) -> None:
+ """List AWS Data Pipeline pipelines in a region."""
+ logger.info("DataPipeline - Listing pipelines...")
+ try:
+ list_pipelines_paginator = regional_client.get_paginator("list_pipelines")
+ for page in list_pipelines_paginator.paginate():
+ for pipeline in page.get("pipelineIdList", []):
+ pipeline_id = pipeline.get("id")
+ pipeline_name = pipeline.get("name", pipeline_id)
+ pipeline_arn = (
+ f"arn:{self.audited_partition}:datapipeline:"
+ f"{regional_client.region}:{self.audited_account}:pipeline/{pipeline_id}"
+ )
+ if not self.audit_resources or is_resource_filtered(
+ pipeline_arn, self.audit_resources
+ ):
+ self.pipelines[pipeline_arn] = Pipeline(
+ id=pipeline_id,
+ name=pipeline_name,
+ arn=pipeline_arn,
+ region=regional_client.region,
+ )
+ except ClientError as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _get_pipeline_definition(self, pipeline: Pipeline) -> None:
+ """Get the full definition for an AWS Data Pipeline pipeline."""
+ logger.info(f"DataPipeline - Getting definition for pipeline {pipeline.id}...")
+ try:
+ regional_client = self.regional_clients[pipeline.region]
+ try:
+ pipeline_descriptions = regional_client.describe_pipelines(
+ pipelineIds=[pipeline.id]
+ ).get("pipelineDescriptionList", [])
+ if pipeline_descriptions:
+ pipeline.tags = pipeline_descriptions[0].get("tags", [])
+ except ClientError as error:
+ logger.error(
+ f"{pipeline.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{pipeline.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ definition = regional_client.get_pipeline_definition(pipelineId=pipeline.id)
+ pipeline.definition = {
+ "pipelineObjects": definition.get("pipelineObjects", []),
+ "parameterObjects": definition.get("parameterObjects", []),
+ "parameterValues": definition.get("parameterValues", []),
+ }
+ except ClientError as error:
+ logger.error(
+ f"{pipeline.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{pipeline.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
diff --git a/prowler/providers/aws/services/dlm/dlm_ebs_snapshot_lifecycle_policy_exists/dlm_ebs_snapshot_lifecycle_policy_exists.py b/prowler/providers/aws/services/dlm/dlm_ebs_snapshot_lifecycle_policy_exists/dlm_ebs_snapshot_lifecycle_policy_exists.py
index 3ee815fb23..c7eedc7f8f 100644
--- a/prowler/providers/aws/services/dlm/dlm_ebs_snapshot_lifecycle_policy_exists/dlm_ebs_snapshot_lifecycle_policy_exists.py
+++ b/prowler/providers/aws/services/dlm/dlm_ebs_snapshot_lifecycle_policy_exists/dlm_ebs_snapshot_lifecycle_policy_exists.py
@@ -1,6 +1,5 @@
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.providers.aws.services.dlm.dlm_client import dlm_client
-from prowler.providers.aws.services.ec2.ec2_client import ec2_client
class dlm_ebs_snapshot_lifecycle_policy_exists(Check):
@@ -8,8 +7,8 @@ class dlm_ebs_snapshot_lifecycle_policy_exists(Check):
findings = []
for region in dlm_client.lifecycle_policies:
if (
- region in ec2_client.regions_with_snapshots
- and ec2_client.regions_with_snapshots[region]
+ region in dlm_client.regions_with_snapshots
+ and dlm_client.regions_with_snapshots[region]
):
report = Check_Report_AWS(
metadata=self.metadata(),
diff --git a/prowler/providers/aws/services/dlm/dlm_service.py b/prowler/providers/aws/services/dlm/dlm_service.py
index 1d6fff9b5a..f0f67e631c 100644
--- a/prowler/providers/aws/services/dlm/dlm_service.py
+++ b/prowler/providers/aws/services/dlm/dlm_service.py
@@ -9,7 +9,13 @@ class DLM(AWSService):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
self.lifecycle_policies = {}
+ self.regions_with_snapshots = {}
self.__threading_call__(self._get_lifecycle_policies)
+ ec2_regional_clients = provider.generate_regional_clients("ec2") or {}
+ self.__threading_call__(
+ self._get_regions_with_snapshots,
+ iterator=ec2_regional_clients.values(),
+ )
def _get_lifecycle_policy_arn_template(self, region):
return (
@@ -35,6 +41,34 @@ class DLM(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_regions_with_snapshots(self, regional_client):
+ logger.info("DLM - Checking regions with self-owned EBS snapshots...")
+ try:
+ self.regions_with_snapshots[regional_client.region] = False
+ next_token = None
+ while True:
+ describe_snapshots_args = {
+ "OwnerIds": ["self"],
+ "MaxResults": 5,
+ }
+ if next_token:
+ describe_snapshots_args["NextToken"] = next_token
+
+ snapshots = regional_client.describe_snapshots(
+ **describe_snapshots_args
+ )
+ if snapshots.get("Snapshots"):
+ self.regions_with_snapshots[regional_client.region] = True
+ break
+
+ next_token = snapshots.get("NextToken")
+ if not next_token:
+ break
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
class LifecyclePolicy(BaseModel):
id: str
diff --git a/prowler/providers/aws/services/dms/dms_instance_no_public_access/dms_instance_no_public_access.py b/prowler/providers/aws/services/dms/dms_instance_no_public_access/dms_instance_no_public_access.py
index 2b491529c9..5f1a57897b 100644
--- a/prowler/providers/aws/services/dms/dms_instance_no_public_access/dms_instance_no_public_access.py
+++ b/prowler/providers/aws/services/dms/dms_instance_no_public_access/dms_instance_no_public_access.py
@@ -1,9 +1,14 @@
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.providers.aws.services.dms.dms_client import dms_client
-from prowler.providers.aws.services.ec2.ec2_client import ec2_client
from prowler.providers.aws.services.ec2.lib.security_groups import check_security_group
+def _get_ec2_client():
+ from prowler.providers.aws.services.ec2.ec2_client import ec2_client
+
+ return ec2_client
+
+
class dms_instance_no_public_access(Check):
def execute(self):
findings = []
@@ -19,7 +24,7 @@ class dms_instance_no_public_access(Check):
if instance.security_groups:
report.status = "PASS"
report.status_extended = f"DMS Replication Instance {instance.id} is set as publicly accessible but filtered with security groups."
- for security_group in ec2_client.security_groups.values():
+ for security_group in _get_ec2_client().security_groups.values():
if security_group.id in instance.security_groups:
for ingress_rule in security_group.ingress_rules:
if check_security_group(
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_log_service_enabled/__init__.py b/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_log_service_enabled/__init__.py
rename to prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/__init__.py
diff --git a/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.metadata.json b/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.metadata.json
new file mode 100644
index 0000000000..c8638927a3
--- /dev/null
+++ b/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "aws",
+ "CheckID": "ec2_ami_account_block_public_access",
+ "CheckTitle": "AMI block public access is enabled at the account level",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Effects/Data Exposure"
+ ],
+ "ServiceName": "ec2",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Other",
+ "ResourceGroup": "compute",
+ "Description": "AMI block public access configuration is assessed to see whether public sharing of AMIs is blocked in the account and Region. When enabled (`block-new-sharing`), no AMI in the Region can be made public regardless of individual image permissions.",
+ "Risk": "Without blocking public access, AMIs could be accidentally or maliciously shared publicly, exposing baked-in secrets, source code, and infrastructure details to unauthorized actors.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-intro.html",
+ "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/image-block-public-access.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws ec2 enable-image-block-public-access --image-block-public-access-state block-new-sharing",
+ "NativeIaC": "",
+ "Other": "1. In the AWS console, select the target Region in the top-right.\n2. Go to EC2 > AMIs.\n3. In the AMIs page, choose Block public access for AMIs (or EC2 Dashboard > Account attributes > Data protection and security).\n4. Choose Manage and enable Block public access.\n5. Save changes.",
+ "Terraform": "```hcl\nresource \"aws_ec2_image_block_public_access\" \"<example_resource_name>\" {\n state = \"block-new-sharing\" # Blocks new public sharing of AMIs in the configured Region\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable AMI block public access (`block-new-sharing`) in every active Region. Apply guardrails (SCPs) to prevent it from being disabled, and review any AMIs that are currently shared publicly.",
+ "Url": "https://hub.prowler.com/check/ec2_ami_account_block_public_access"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.py b/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.py
new file mode 100644
index 0000000000..08a892a674
--- /dev/null
+++ b/prowler/providers/aws/services/ec2/ec2_ami_account_block_public_access/ec2_ami_account_block_public_access.py
@@ -0,0 +1,29 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.ec2.ec2_client import ec2_client
+
+
+class ec2_ami_account_block_public_access(Check):
+ def execute(self):
+ findings = []
+ for state in ec2_client.ami_block_public_access_states:
+ report = Check_Report_AWS(
+ metadata=self.metadata(),
+ resource=state,
+ )
+ report.resource_id = ec2_client.audited_account
+ report.resource_arn = ec2_client.account_arn_template
+
+ if state.status == "block-new-sharing":
+ report.status = "PASS"
+ report.status_extended = (
+ f"AMI Block Public Access is enabled in {state.region}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"AMI Block Public Access is disabled in {state.region}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/ec2/ec2_ami_public/ec2_ami_public.py b/prowler/providers/aws/services/ec2/ec2_ami_public/ec2_ami_public.py
index 3df5fffb58..a708467a94 100644
--- a/prowler/providers/aws/services/ec2/ec2_ami_public/ec2_ami_public.py
+++ b/prowler/providers/aws/services/ec2/ec2_ami_public/ec2_ami_public.py
@@ -18,4 +18,4 @@ class ec2_ami_public(Check):
findings.append(report)
- return findings
+ return findings
diff --git a/prowler/providers/aws/services/ec2/ec2_instance_account_imdsv2_enabled/ec2_instance_account_imdsv2_enabled.py b/prowler/providers/aws/services/ec2/ec2_instance_account_imdsv2_enabled/ec2_instance_account_imdsv2_enabled.py
index 9abd6239cc..f6b0fce95f 100644
--- a/prowler/providers/aws/services/ec2/ec2_instance_account_imdsv2_enabled/ec2_instance_account_imdsv2_enabled.py
+++ b/prowler/providers/aws/services/ec2/ec2_instance_account_imdsv2_enabled/ec2_instance_account_imdsv2_enabled.py
@@ -14,7 +14,11 @@ class ec2_instance_account_imdsv2_enabled(Check):
metadata=self.metadata(),
resource=instance_metadata_default,
)
- report.resource_arn = ec2_client.account_arn_template
+ report.resource_arn = (
+ f"arn:{ec2_client.audited_partition}:ec2:"
+ f"{instance_metadata_default.region}:"
+ f"{ec2_client.audited_account}:account"
+ )
report.resource_id = ec2_client.audited_account
if instance_metadata_default.http_tokens == "required":
report.status = "PASS"
diff --git a/prowler/providers/aws/services/ec2/ec2_instance_secrets_user_data/ec2_instance_secrets_user_data.py b/prowler/providers/aws/services/ec2/ec2_instance_secrets_user_data/ec2_instance_secrets_user_data.py
index 3c3864c479..31b3f8fb05 100644
--- a/prowler/providers/aws/services/ec2/ec2_instance_secrets_user_data/ec2_instance_secrets_user_data.py
+++ b/prowler/providers/aws/services/ec2/ec2_instance_secrets_user_data/ec2_instance_secrets_user_data.py
@@ -4,7 +4,11 @@ from base64 import b64decode
from prowler.config.config import encoding_format_utf_8
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.lib.logger import logger
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.ec2.ec2_client import ec2_client
@@ -14,54 +18,86 @@ class ec2_instance_secrets_user_data(Check):
secrets_ignore_patterns = ec2_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for instance in ec2_client.instances:
- if instance.state != "terminated":
- report = Check_Report_AWS(metadata=self.metadata(), resource=instance)
- if instance.user_data:
- user_data = b64decode(instance.user_data)
- try:
- if user_data[0:2] == b"\x1f\x8b": # GZIP magic number
- user_data = zlib.decompress(
- user_data, zlib.MAX_WBITS | 32
- ).decode(encoding_format_utf_8)
- else:
- user_data = user_data.decode(encoding_format_utf_8)
- except UnicodeDecodeError as error:
- logger.warning(
- f"{instance.region} -- Unable to decode user data in EC2 instance {instance.id}: {error}"
- )
- continue
- except Exception as error:
- logger.error(
- f"{instance.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
- )
- continue
- detect_secrets_output = detect_secrets_scan(
- data=user_data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=ec2_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
- if detect_secrets_output:
- secrets_string = ", ".join(
- [
- f"{secret['type']} on line {secret['line_number']}"
- for secret in detect_secrets_output
- ]
- )
- report.status = "FAIL"
- report.status_extended = f"Potential secret found in EC2 instance {instance.id} User Data -> {secrets_string}."
+ validate = ec2_client.audit_config.get("secrets_validate", False)
+ instances = list(ec2_client.instances)
+ # Collect the decoded User Data of each non-terminated instance and scan
+ # it all in batched Kingfisher invocations instead of one subprocess each.
+ # Instances whose User Data cannot be decoded are undecodable (no report),
+ # matching the original per-resource behavior.
+ undecodable = set()
+
+ def payloads():
+ for index, instance in enumerate(instances):
+ if instance.state == "terminated" or not instance.user_data:
+ continue
+ user_data = b64decode(instance.user_data)
+ try:
+ if user_data[0:2] == b"\x1f\x8b": # GZIP magic number
+ user_data = zlib.decompress(
+ user_data, zlib.MAX_WBITS | 32
+ ).decode(encoding_format_utf_8)
else:
- report.status = "PASS"
- report.status_extended = (
- f"No secrets found in EC2 instance {instance.id} User Data."
- )
+ user_data = user_data.decode(encoding_format_utf_8)
+ except UnicodeDecodeError as error:
+ logger.warning(
+ f"{instance.region} -- Unable to decode user data in EC2 instance {instance.id}: {error}"
+ )
+ undecodable.add(index)
+ continue
+ except Exception as error:
+ logger.error(
+ f"{instance.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ undecodable.add(index)
+ continue
+ yield index, user_data
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, instance in enumerate(instances):
+ if instance.state == "terminated":
+ continue
+ report = Check_Report_AWS(metadata=self.metadata(), resource=instance)
+ if scan_error and instance.user_data:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan EC2 instance {instance.id} User Data for "
+ f"secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ if index in undecodable:
+ report.status = "MANUAL"
+ report.status_extended = f"Could not decode User Data for EC2 instance {instance.id}; manual review is required to scan for secrets."
+ elif instance.user_data:
+ detect_secrets_output = batch_results.get(index)
+ if detect_secrets_output:
+ secrets_string = ", ".join(
+ [
+ f"{secret['type']} on line {secret['line_number']}"
+ for secret in detect_secrets_output
+ ]
+ )
+ report.status = "FAIL"
+ report.status_extended = f"Potential secret found in EC2 instance {instance.id} User Data -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status = "PASS"
- report.status_extended = f"No secrets found in EC2 instance {instance.id} since User Data is empty."
+ report.status_extended = (
+ f"No secrets found in EC2 instance {instance.id} User Data."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = f"No secrets found in EC2 instance {instance.id} since User Data is empty."
- findings.append(report)
+ findings.append(report)
return findings
diff --git a/prowler/providers/aws/services/ec2/ec2_instance_with_outdated_ami/ec2_instance_with_outdated_ami.py b/prowler/providers/aws/services/ec2/ec2_instance_with_outdated_ami/ec2_instance_with_outdated_ami.py
index b0dc677e34..3e4d17f4fd 100644
--- a/prowler/providers/aws/services/ec2/ec2_instance_with_outdated_ami/ec2_instance_with_outdated_ami.py
+++ b/prowler/providers/aws/services/ec2/ec2_instance_with_outdated_ami/ec2_instance_with_outdated_ami.py
@@ -26,11 +26,12 @@ class ec2_instance_with_outdated_ami(Check):
List[Check_Report_AWS]: A list containing the results of the check for each instance.
"""
findings = []
+ images_by_id = getattr(ec2_client, "images_by_id", None)
+ if images_by_id is None:
+ images_by_id = {image.id: image for image in ec2_client.images}
+
for instance in ec2_client.instances:
- ami = next(
- (image for image in ec2_client.images if image.id == instance.image_id),
- None,
- )
+ ami = images_by_id.get(instance.image_id)
if ami and ami.owner == "amazon":
report = Check_Report_AWS(metadata=self.metadata(), resource=instance)
report.status = "PASS"
diff --git a/prowler/providers/aws/services/ec2/ec2_launch_template_no_secrets/ec2_launch_template_no_secrets.py b/prowler/providers/aws/services/ec2/ec2_launch_template_no_secrets/ec2_launch_template_no_secrets.py
index 823553bcdf..e84da724a2 100644
--- a/prowler/providers/aws/services/ec2/ec2_launch_template_no_secrets/ec2_launch_template_no_secrets.py
+++ b/prowler/providers/aws/services/ec2/ec2_launch_template_no_secrets/ec2_launch_template_no_secrets.py
@@ -4,7 +4,11 @@ from base64 import b64decode
from prowler.config.config import encoding_format_utf_8
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.lib.logger import logger
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.ec2.ec2_client import ec2_client
@@ -14,43 +18,77 @@ class ec2_launch_template_no_secrets(Check):
secrets_ignore_patterns = ec2_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for template in ec2_client.launch_templates:
+ validate = ec2_client.audit_config.get("secrets_validate", False)
+ templates = list(ec2_client.launch_templates)
+
+ # Track versions whose User Data cannot be decoded so the template is
+ # surfaced (MANUAL) instead of silently claiming no secrets were found.
+ undecodable_versions = {}
+
+ # Collect the decoded User Data of every (template, version) and scan it
+ # all in batched Kingfisher invocations instead of one subprocess per
+ # version. Versions whose User Data cannot be decoded are recorded above.
+ def payloads():
+ for template_index, template in enumerate(templates):
+ for version_index, version in enumerate(template.versions):
+ if not version.template_data.user_data:
+ continue
+ user_data = b64decode(version.template_data.user_data)
+ try:
+ if user_data[0:2] == b"\x1f\x8b": # GZIP magic number
+ user_data = zlib.decompress(
+ user_data, zlib.MAX_WBITS | 32
+ ).decode(encoding_format_utf_8)
+ else:
+ user_data = user_data.decode(encoding_format_utf_8)
+ except UnicodeDecodeError as error:
+ logger.warning(
+ f"{template.region} -- Unable to decode User Data in EC2 Launch Template {template.name} version {version.version_number}: {error}"
+ )
+ undecodable_versions.setdefault(template_index, []).append(
+ version.version_number
+ )
+ continue
+ except Exception as error:
+ logger.error(
+ f"{template.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ undecodable_versions.setdefault(template_index, []).append(
+ version.version_number
+ )
+ continue
+ yield (template_index, version_index), user_data
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for template_index, template in enumerate(templates):
report = Check_Report_AWS(metadata=self.metadata(), resource=template)
- versions_with_secrets = []
-
- for version in template.versions:
- if not version.template_data.user_data:
- continue
- user_data = b64decode(version.template_data.user_data)
-
- try:
- if user_data[0:2] == b"\x1f\x8b": # GZIP magic number
- user_data = zlib.decompress(
- user_data, zlib.MAX_WBITS | 32
- ).decode(encoding_format_utf_8)
- else:
- user_data = user_data.decode(encoding_format_utf_8)
- except UnicodeDecodeError as error:
- logger.warning(
- f"{template.region} -- Unable to decode User Data in EC2 Launch Template {template.name} version {version.version_number}: {error}"
- )
- continue
- except Exception as error:
- logger.error(
- f"{template.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
- )
- continue
-
- version_secrets = detect_secrets_scan(
- data=user_data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=ec2_client.audit_config.get(
- "detect_secrets_plugins"
- ),
+ if scan_error and any(
+ version.template_data.user_data for version in template.versions
+ ):
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan EC2 Launch Template {template.name} User Data "
+ f"for secrets: {scan_error}; manual review is required."
)
+ findings.append(report)
+ continue
+ versions_with_secrets = []
+ all_secrets = []
+
+ for version_index, version in enumerate(template.versions):
+ version_secrets = batch_results.get((template_index, version_index))
if version_secrets:
+ all_secrets.extend(version_secrets)
secrets_string = ", ".join(
[
f"{secret['type']} on line {secret['line_number']}"
@@ -61,9 +99,14 @@ class ec2_launch_template_no_secrets(Check):
f"Version {version.version_number}: {secrets_string}"
)
+ undecodable = undecodable_versions.get(template_index, [])
if len(versions_with_secrets) > 0:
report.status = "FAIL"
report.status_extended = f"Potential secret found in User Data for EC2 Launch Template {template.name} in template versions: {', '.join(versions_with_secrets)}."
+ annotate_verified_secrets(report, all_secrets)
+ elif undecodable:
+ report.status = "MANUAL"
+ report.status_extended = f"Could not decode User Data for EC2 Launch Template {template.name} versions: {', '.join(str(version_number) for version_number in undecodable)}; manual review is required to scan for secrets."
else:
report.status = "PASS"
report.status_extended = f"No secrets found in User Data of any version for EC2 Launch Template {template.name}."
diff --git a/prowler/providers/aws/services/ec2/ec2_securitygroup_not_used/ec2_securitygroup_not_used.py b/prowler/providers/aws/services/ec2/ec2_securitygroup_not_used/ec2_securitygroup_not_used.py
index aa621abdfb..c45693c498 100644
--- a/prowler/providers/aws/services/ec2/ec2_securitygroup_not_used/ec2_securitygroup_not_used.py
+++ b/prowler/providers/aws/services/ec2/ec2_securitygroup_not_used/ec2_securitygroup_not_used.py
@@ -15,11 +15,10 @@ class ec2_securitygroup_not_used(Check):
report.resource_details = security_group.name
report.status = "PASS"
report.status_extended = f"Security group {security_group.name} ({security_group.id}) it is being used."
- sg_in_lambda = False
+ sg_in_lambda = (
+ security_group.id in awslambda_client.security_groups_in_use
+ )
sg_associated = False
- for function in awslambda_client.functions.values():
- if security_group.id in function.security_groups:
- sg_in_lambda = True
for sg in ec2_client.security_groups.values():
if security_group.id in sg.associated_sgs:
sg_associated = True
diff --git a/prowler/providers/aws/services/ec2/ec2_service.py b/prowler/providers/aws/services/ec2/ec2_service.py
index ccdb9e58fe..1c1055ba78 100644
--- a/prowler/providers/aws/services/ec2/ec2_service.py
+++ b/prowler/providers/aws/services/ec2/ec2_service.py
@@ -6,9 +6,15 @@ from botocore.client import ClientError
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ limit_resources,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
+DESCRIBE_IMAGES_IMAGE_IDS_BATCH_SIZE = 200
+
class EC2(AWSService):
def __init__(self, provider):
@@ -26,22 +32,31 @@ class EC2(AWSService):
self.snapshots = []
self.volumes_with_snapshots = {}
self.regions_with_snapshots = {}
+ # Snapshots are listed first, then limited after per-region snapshot
+ # presence is derived and before public status is hydrated.
+ self.snapshot_limit = get_resource_scan_limit(
+ self.audit_config, "max_ebs_snapshots"
+ )
self.__threading_call__(self._describe_snapshots)
- self.__threading_call__(self._determine_public_snapshots, self.snapshots)
self.network_interfaces = {}
self.__threading_call__(self._describe_network_interfaces)
self.images = []
+ self.images_by_id = {}
self.__threading_call__(self._describe_images)
self.volumes = []
self.__threading_call__(self._describe_volumes)
self.attributes_for_regions = {}
self.__threading_call__(self._get_resources_for_regions)
+ self._select_snapshots_for_analysis()
+ self.__threading_call__(self._determine_public_snapshots, self.snapshots)
self.ebs_encryption_by_default = []
self.__threading_call__(self._get_ebs_encryption_settings)
self.elastic_ips = []
self.__threading_call__(self._describe_ec2_addresses)
self.ebs_block_public_access_snapshots_states = []
self.__threading_call__(self._get_snapshot_block_public_access_state)
+ self.ami_block_public_access_states = []
+ self.__threading_call__(self._get_ami_block_public_access_state)
self.instance_metadata_defaults = []
self.__threading_call__(self._get_instance_metadata_defaults)
self.launch_templates = []
@@ -207,6 +222,7 @@ class EC2(AWSService):
arn=arn,
region=regional_client.region,
encrypted=snapshot.get("Encrypted", False),
+ start_time=snapshot.get("StartTime"),
tags=snapshot.get("Tags"),
volume=snapshot["VolumeId"],
)
@@ -243,6 +259,18 @@ class EC2(AWSService):
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _select_snapshots_for_analysis(self):
+ self.snapshots = list(
+ limit_resources(
+ sorted(
+ self.snapshots,
+ key=lambda s: (s.start_time.timestamp() if s.start_time else 0.0),
+ reverse=True,
+ ),
+ self.snapshot_limit,
+ )
+ )
+
def _describe_network_interfaces(self, regional_client):
try:
# Get Network Interfaces with Public IPs
@@ -349,36 +377,90 @@ class EC2(AWSService):
def _describe_images(self, regional_client):
try:
- for owner in ["self", "amazon"]:
- try:
- for image in regional_client.describe_images(
- Owners=[owner], IncludeDeprecated=True
- )["Images"]:
- arn = f"arn:{self.audited_partition}:ec2:{regional_client.region}:{self.audited_account}:image/{image['ImageId']}"
- if not self.audit_resources or (
- is_resource_filtered(arn, self.audit_resources)
- ):
- self.images.append(
- Image(
- id=image["ImageId"],
- arn=arn,
- name=image.get("Name", ""),
- public=image.get("Public", False),
- region=regional_client.region,
- tags=image.get("Tags"),
- deprecation_time=image.get("DeprecationTime"),
- owner=owner,
- )
- )
- except Exception as error:
- logger.error(
- f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
- )
+ try:
+ for image in regional_client.describe_images(
+ Owners=["self"], IncludeDeprecated=True
+ )["Images"]:
+ self._add_image(image, regional_client.region, "self")
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ amazon_image_ids = sorted(
+ {
+ instance.image_id
+ for instance in self.instances
+ if instance.region == regional_client.region
+ and instance.image_id
+ and instance.image_id not in self.images_by_id
+ }
+ )
+
+ for image_batch in self._get_image_id_batches(amazon_image_ids):
+ for image in self._describe_images_by_id(regional_client, image_batch):
+ if self._is_amazon_image(image):
+ self._add_image(image, regional_client.region, "amazon")
except Exception as error:
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _add_image(self, image, region, owner):
+ arn = f"arn:{self.audited_partition}:ec2:{region}:{self.audited_account}:image/{image['ImageId']}"
+ if not self.audit_resources or (
+ is_resource_filtered(arn, self.audit_resources)
+ ):
+ ec2_image = Image(
+ id=image["ImageId"],
+ arn=arn,
+ name=image.get("Name", ""),
+ public=image.get("Public", False),
+ region=region,
+ tags=image.get("Tags"),
+ deprecation_time=image.get("DeprecationTime"),
+ owner=owner,
+ )
+ self.images.append(ec2_image)
+ self.images_by_id[ec2_image.id] = ec2_image
+
+ def _describe_images_by_id(self, regional_client, image_ids):
+ try:
+ return regional_client.describe_images(
+ ImageIds=image_ids, IncludeDeprecated=True
+ )["Images"]
+ except ClientError as error:
+ if error.response["Error"]["Code"] == "InvalidAMIID.NotFound":
+ if len(image_ids) == 1:
+ logger.warning(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return []
+
+ midpoint = len(image_ids) // 2
+ return self._describe_images_by_id(
+ regional_client, image_ids[:midpoint]
+ ) + self._describe_images_by_id(regional_client, image_ids[midpoint:])
+
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return []
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return []
+
+ @staticmethod
+ def _get_image_id_batches(image_ids):
+ for index in range(0, len(image_ids), DESCRIBE_IMAGES_IMAGE_IDS_BATCH_SIZE):
+ yield image_ids[index : index + DESCRIBE_IMAGES_IMAGE_IDS_BATCH_SIZE]
+
+ @staticmethod
+ def _is_amazon_image(image):
+ return image.get("ImageOwnerAlias") == "amazon"
+
def _describe_volumes(self, regional_client):
try:
describe_volumes_paginator = regional_client.get_paginator(
@@ -475,6 +557,21 @@ class EC2(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_ami_block_public_access_state(self, regional_client):
+ try:
+ self.ami_block_public_access_states.append(
+ AmiBlockPublicAccess(
+ status=regional_client.get_image_block_public_access_state()[
+ "ImageBlockPublicAccessState"
+ ],
+ region=regional_client.region,
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _get_instance_metadata_defaults(self, regional_client):
try:
instances_in_region = self.attributes_for_regions.get(
@@ -686,6 +783,7 @@ class Snapshot(BaseModel):
region: str
encrypted: bool
public: bool = False
+ start_time: Optional[datetime] = None
tags: Optional[list] = []
volume: Optional[str]
@@ -774,6 +872,11 @@ class EbsSnapshotBlockPublicAccess(BaseModel):
region: str
+class AmiBlockPublicAccess(BaseModel):
+ status: str
+ region: str
+
+
class InstanceMetadataDefaults(BaseModel):
http_tokens: Optional[str]
instances: bool
diff --git a/prowler/providers/aws/services/ecs/ecs_service.py b/prowler/providers/aws/services/ecs/ecs_service.py
index 560125bf58..65c3aabf56 100644
--- a/prowler/providers/aws/services/ecs/ecs_service.py
+++ b/prowler/providers/aws/services/ecs/ecs_service.py
@@ -1,9 +1,16 @@
+from datetime import datetime
+from itertools import zip_longest
from re import sub
from typing import Optional
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
+from prowler.lib.resource_limit import (
+ get_resource_scan_limit,
+ iter_limited_paginator_items,
+ limit_resources,
+)
from prowler.lib.scan_filters.scan_filters import is_resource_filtered
from prowler.providers.aws.lib.service.service import AWSService
@@ -12,40 +19,126 @@ class ECS(AWSService):
def __init__(self, provider):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
+ # Task definition ARNs are listed first, then only the selected subset
+ # is described and exposed for checks.
self.task_definitions = {}
+ self._task_definition_arns = None
+ self._task_definition_arns_by_region = {}
+ self.task_definition_limit = get_resource_scan_limit(
+ self.audit_config, "max_ecs_task_definitions"
+ )
self.services = {}
self.clusters = {}
self.task_sets = {}
- self.__threading_call__(self._list_task_definitions)
- self.__threading_call__(
- self._describe_task_definition, self.task_definitions.values()
- )
+ for _ in self._load_task_definitions_for_analysis():
+ pass
self.__threading_call__(self._list_clusters)
self.__threading_call__(self._describe_clusters, self.clusters.values())
self.__threading_call__(self._describe_services, self.clusters.values())
- def _list_task_definitions(self, regional_client):
+ def _list_task_definition_arns(self) -> list:
+ """List task definition ARNs newest-first, memoized.
+
+ AWS returns ``list_task_definitions(sort=DESC)`` results per region.
+ Prowler limits the task definitions it describes and exposes to checks.
+ """
+ if self._task_definition_arns is not None:
+ return self._task_definition_arns
logger.info("ECS - Listing Task Definitions...")
+ self.__threading_call__(self._list_task_definition_arns_by_region)
+ arns_by_region = []
+ for region in self.regional_clients:
+ arns_by_region.append(self._task_definition_arns_by_region.get(region, []))
+ arns = []
+ for task_definition_batch in zip_longest(*arns_by_region):
+ for task_definition in task_definition_batch:
+ if task_definition:
+ arns.append(task_definition)
+ self._task_definition_arns = arns
+ return arns
+
+ def _list_task_definition_arns_by_region(self, regional_client):
try:
list_ecs_paginator = regional_client.get_paginator("list_task_definitions")
- for page in list_ecs_paginator.paginate():
- for task_definition in page["taskDefinitionArns"]:
- if not self.audit_resources or (
- is_resource_filtered(task_definition, self.audit_resources)
- ):
- self.task_definitions[task_definition] = TaskDefinition(
- # we want the family name without the revision
- name=sub(":.*", "", task_definition.split("/")[-1]),
- arn=task_definition,
- revision=task_definition.split(":")[-1],
- region=regional_client.region,
- environment_variables=[],
- )
+ regional_arns = []
+ for task_definition in iter_limited_paginator_items(
+ list_ecs_paginator,
+ "taskDefinitionArns",
+ None,
+ item_filter=lambda task_definition: not self.audit_resources
+ or is_resource_filtered(task_definition, self.audit_resources),
+ sort="DESC",
+ ):
+ regional_arns.append((task_definition, regional_client.region))
+ self._task_definition_arns_by_region[regional_client.region] = regional_arns
except Exception as error:
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _load_task_definitions_for_analysis(self):
+ """Yield task definitions lazily, describing each one on demand.
+
+ Resources already fetched are memoized in ``self.task_definitions`` and
+ reused across checks (checks run sequentially, so no locking is needed).
+ Task definitions are described before applying the configured resource
+ limit because AWS exposes ``registeredAt`` only through
+ ``describe_task_definition``. The limit bounds the task definitions
+ exposed to checks for analysis.
+ """
+ task_definitions = []
+ for arn, region in self._list_task_definition_arns():
+ task_definition = self.task_definitions.get(arn)
+ if task_definition is None:
+ task_definition = TaskDefinition(
+ # we want the family name without the revision
+ name=sub(":.*", "", arn.split("/")[-1]),
+ arn=arn,
+ revision=arn.split(":")[-1],
+ region=region,
+ environment_variables=[],
+ )
+ self.task_definitions[arn] = task_definition
+ task_definitions.append(task_definition)
+
+ self.__threading_call__(self._describe_task_definition, task_definitions)
+
+ selected_task_definitions = list(
+ limit_resources(
+ self._sort_task_definitions_by_registration_date(
+ self.task_definitions.values()
+ ),
+ self.task_definition_limit,
+ )
+ )
+ self.task_definitions = {
+ task_definition.arn: task_definition
+ for task_definition in selected_task_definitions
+ }
+ for task_definition in selected_task_definitions:
+ yield task_definition
+
+ @staticmethod
+ def _sort_task_definitions_by_registration_date(task_definitions):
+ task_definitions = list(task_definitions)
+ if not any(
+ task_definition.registered_at for task_definition in task_definitions
+ ):
+ return task_definitions
+
+ return sorted(
+ task_definitions,
+ key=lambda task_definition: (
+ task_definition.registered_at is None,
+ (
+ -task_definition.registered_at.timestamp()
+ if task_definition.registered_at
+ else 0
+ ),
+ task_definition.arn,
+ ),
+ )
+
def _describe_task_definition(self, task_definition):
logger.info("ECS - Describing Task Definition...")
try:
@@ -84,6 +177,9 @@ class ECS(AWSService):
)
)
task_definition.pid_mode = response["taskDefinition"].get("pidMode", "")
+ task_definition.registered_at = response["taskDefinition"].get(
+ "registeredAt"
+ )
task_definition.tags = response.get("tags")
task_definition.network_mode = response["taskDefinition"].get(
"networkMode", "bridge"
@@ -208,6 +304,7 @@ class TaskDefinition(BaseModel):
region: str
container_definitions: list[ContainerDefinition] = []
pid_mode: Optional[str]
+ registered_at: Optional[datetime] = None
tags: Optional[list] = []
network_mode: Optional[str]
diff --git a/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.py b/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.py
index cd835d0149..b0bc7198ee 100644
--- a/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.py
+++ b/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.py
@@ -1,7 +1,11 @@
from json import dumps
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.ecs.ecs_client import ecs_client
@@ -11,33 +15,67 @@ class ecs_task_definitions_no_environment_secrets(Check):
secrets_ignore_patterns = ecs_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for task_definition in ecs_client.task_definitions.values():
+ validate = ecs_client.audit_config.get("secrets_validate", False)
+ task_definitions = list(ecs_client.task_definitions.values())
+
+ # Scan every (task definition, container) environment in batched
+ # Kingfisher invocations instead of one subprocess per container.
+ # Payloads are yielded lazily so only a chunk is held/written at a time.
+ def environment_payloads():
+ for td_index, task_definition in enumerate(task_definitions):
+ for c_index, container in enumerate(
+ task_definition.container_definitions
+ ):
+ if container.environment:
+ dump_env_vars = {
+ env_var.name: env_var.value
+ for env_var in container.environment
+ }
+ yield (td_index, c_index), dumps(dump_env_vars, indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ environment_payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for td_index, task_definition in enumerate(task_definitions):
report = Check_Report_AWS(
metadata=self.metadata(), resource=task_definition
)
report.resource_id = f"{task_definition.name}:{task_definition.revision}"
report.status = "PASS"
extended_status_parts = []
+ all_secrets = []
- for container in task_definition.container_definitions:
+ if scan_error and any(
+ container.environment
+ for container in task_definition.container_definitions
+ ):
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan ECS task definition {task_definition.name} with "
+ f"revision {task_definition.revision} for secrets: {scan_error}; "
+ "manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ for c_index, container in enumerate(task_definition.container_definitions):
container_secrets_found = []
if container.environment:
- dump_env_vars = {}
- original_env_vars = []
- for env_var in container.environment:
- dump_env_vars.update({env_var.name: env_var.value})
- original_env_vars.append(env_var.name)
-
- env_data = dumps(dump_env_vars, indent=2)
- detect_secrets_output = detect_secrets_scan(
- data=env_data,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=ecs_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
+ original_env_vars = [
+ env_var.name for env_var in container.environment
+ ]
+ detect_secrets_output = batch_results.get((td_index, c_index))
if detect_secrets_output:
+ all_secrets.extend(detect_secrets_output)
secrets_string = ", ".join(
[
f"{secret['type']} on the environment variable {original_env_vars[secret['line_number'] - 2]}"
@@ -56,6 +94,7 @@ class ecs_task_definitions_no_environment_secrets(Check):
+ "; ".join(extended_status_parts)
+ "."
)
+ annotate_verified_secrets(report, all_secrets)
else:
report.status_extended = f"No secrets found in variables of ECS task definition {task_definition.name} with revision {task_definition.revision}."
findings.append(report)
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_network_policy_enabled/__init__.py b/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_network_policy_enabled/__init__.py
rename to prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/__init__.py
diff --git a/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.metadata.json b/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.metadata.json
new file mode 100644
index 0000000000..0293501578
--- /dev/null
+++ b/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "aws",
+ "CheckID": "elbv2_alb_drop_invalid_header_fields_enabled",
+ "CheckTitle": "Application Load Balancer should be configured to drop invalid HTTP header fields",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices/Network Reachability",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices",
+ "TTPs/Initial Access",
+ "Effects/Data Exposure"
+ ],
+ "ServiceName": "elbv2",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "AwsElbv2LoadBalancer",
+ "ResourceGroup": "network",
+ "Description": "Ensure that Application Load Balancers (ALB) are configured to drop invalid HTTP header fields. The check fails when `routing.http.drop_invalid_header_fields.enabled` is not set to `true`. By default, ALBs do not remove HTTP headers that do not conform to RFC 7230.",
+ "Risk": "Forwarding non-RFC-compliant HTTP headers to backend targets enables HTTP desync (request smuggling):\n- **Confidentiality**: session/token theft, data exfiltration\n- **Integrity**: cache poisoning, request routing bypass, unauthorized actions\n- **Availability**: backend exhaustion.\nDropping invalid header fields removes a primary smuggling vector.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html#drop-invalid-header-fields",
+ "https://docs.aws.amazon.com/securityhub/latest/userguide/elb-controls.html#elb-4"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws elbv2 modify-load-balancer-attributes --load-balancer-arn <ALB_ARN> --attributes Key=routing.http.drop_invalid_header_fields.enabled,Value=true",
+ "NativeIaC": "```yaml\n# CloudFormation: enable drop invalid header fields on an ALB\nResources:\n <example_resource_name>:\n Type: AWS::ElasticLoadBalancingV2::LoadBalancer\n Properties:\n Type: application\n Subnets:\n - <example_subnet_id1>\n - <example_subnet_id2>\n LoadBalancerAttributes:\n - Key: routing.http.drop_invalid_header_fields.enabled # Critical: drop non-RFC-compliant headers\n Value: true\n```",
+ "Other": "1. Open the Amazon EC2 console and choose Load Balancers.\n2. Select the Application Load Balancer.\n3. On the Attributes tab, choose Edit.\n4. Set 'Drop invalid header fields' to Enabled.\n5. Save changes.",
+ "Terraform": "```hcl\n# Terraform: enable drop invalid header fields on an ALB\nresource \"aws_lb\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n load_balancer_type = \"application\"\n subnets = [\"<example_subnet_id1>\", \"<example_subnet_id2>\"]\n drop_invalid_header_fields = true # Critical: drop non-RFC-compliant headers\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable 'drop invalid header fields' on Application Load Balancers so non-RFC-compliant HTTP headers are removed before requests reach backend targets, reducing exposure to HTTP desync and request smuggling. Apply defense in depth and validate requests at the application layer as well.",
+ "Url": "https://hub.prowler.com/check/elbv2_alb_drop_invalid_header_fields_enabled"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.py b/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.py
new file mode 100644
index 0000000000..86740a253a
--- /dev/null
+++ b/prowler/providers/aws/services/elbv2/elbv2_alb_drop_invalid_header_fields_enabled/elbv2_alb_drop_invalid_header_fields_enabled.py
@@ -0,0 +1,27 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.elbv2.elbv2_client import elbv2_client
+
+
+class elbv2_alb_drop_invalid_header_fields_enabled(Check):
+ def execute(self):
+ findings = []
+ for lb in elbv2_client.loadbalancersv2.values():
+ if lb.type == "application":
+ report = Check_Report_AWS(
+ metadata=self.metadata(),
+ resource=lb,
+ )
+ report.status = "PASS"
+ report.status_extended = (
+ f"ELBv2 ALB {lb.name} is configured to drop invalid "
+ "header fields."
+ )
+ if lb.drop_invalid_header_fields != "true":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"ELBv2 ALB {lb.name} is not configured to drop "
+ "invalid header fields."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_private_cluster_enabled/__init__.py b/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_private_cluster_enabled/__init__.py
rename to prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/__init__.py
diff --git a/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.metadata.json b/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.metadata.json
new file mode 100644
index 0000000000..d86778d5ae
--- /dev/null
+++ b/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.metadata.json
@@ -0,0 +1,42 @@
+{
+ "Provider": "aws",
+ "CheckID": "elbv2_listener_pqc_tls_enabled",
+ "CheckTitle": "ELBv2 HTTPS/TLS listeners use a post-quantum TLS security policy",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "elbv2",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsElbv2LoadBalancer",
+ "ResourceGroup": "network",
+ "Description": "**ELBv2 HTTPS and TLS listeners** are assessed for use of **post-quantum (PQ) TLS security policies**. Listeners whose `SslPolicy` is not in the approved PQ set lack hybrid key exchange (ML-KEM 768 + ECDHE), which can increase harvest-now-decrypt-later exposure for recorded traffic.",
+ "Risk": "Without PQ-ready TLS policies, encrypted traffic captured today may be stored for future cryptanalysis if a **cryptographically relevant quantum computer** becomes available (**harvest-now, decrypt-later** attack). PQ-ready TLS policies reduce this long-term confidentiality risk for sensitive data, credentials, and session tokens transmitted through the load balancer.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/elasticloadbalancing/latest/application/describe-ssl-policies.html",
+ "https://aws.amazon.com/security/post-quantum-cryptography/",
+ "https://csrc.nist.gov/projects/post-quantum-cryptography"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws elbv2 modify-listener --listener-arn <listener_arn> --ssl-policy ELBSecurityPolicy-TLS13-1-2-PQ-2025-09",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::ElasticLoadBalancingV2::Listener\n Properties:\n LoadBalancerArn: <example_resource_arn>\n Protocol: HTTPS\n Port: 443\n DefaultActions:\n - Type: forward\n TargetGroupArn: <example_resource_arn>\n Certificates:\n - CertificateArn: <example_certificate_arn>\n SslPolicy: ELBSecurityPolicy-TLS13-1-2-PQ-2025-09 # FIX: uses a post-quantum TLS policy\n```",
+ "Other": "1. In the AWS Console, go to EC2 > Load Balancers\n2. Select the load balancer and open the Listeners tab\n3. Select the HTTPS/TLS listener and choose Edit\n4. Set Security policy to ELBSecurityPolicy-TLS13-1-2-PQ-2025-09 (or any approved PQ policy)\n5. Save changes",
+ "Terraform": "```hcl\nresource \"aws_lb_listener\" \"<example_resource_name>\" {\n load_balancer_arn = \"<example_resource_arn>\"\n port = 443\n protocol = \"HTTPS\"\n ssl_policy = \"ELBSecurityPolicy-TLS13-1-2-PQ-2025-09\" # FIX: post-quantum TLS policy\n certificate_arn = \"<example_certificate_arn>\"\n\n default_action {\n type = \"forward\"\n target_group_arn = \"<example_resource_arn>\"\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Migrate all ELBv2 HTTPS and TLS listeners to a **post-quantum TLS policy** (`ELBSecurityPolicy-TLS13-*-PQ-2025-09` family) to enable hybrid key exchange (ML-KEM + ECDHE). Periodically review and update policies as AWS publishes new PQ-ready options.",
+ "Url": "https://hub.prowler.com/check/elbv2_listener_pqc_tls_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "elbv2_insecure_ssl_ciphers"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.py b/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.py
new file mode 100644
index 0000000000..270a2cc31b
--- /dev/null
+++ b/prowler/providers/aws/services/elbv2/elbv2_listener_pqc_tls_enabled/elbv2_listener_pqc_tls_enabled.py
@@ -0,0 +1,73 @@
+"""Check that ELBv2 HTTPS/TLS listeners use post-quantum TLS policies."""
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.elbv2.elbv2_client import elbv2_client
+
+PQ_TLS_POLICIES_DEFAULT = [
+ "ELBSecurityPolicy-TLS13-1-2-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext1-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext2-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-3-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext0-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext1-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext2-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Res-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-3-FIPS-PQ-2025-09",
+]
+
+
+class elbv2_listener_pqc_tls_enabled(Check):
+ """Verify that every ELBv2 HTTPS or TLS listener uses a post-quantum TLS policy.
+
+ This check evaluates whether each HTTPS (ALB) or TLS (NLB) listener on an
+ ELBv2 load balancer terminates TLS with a security policy that offers
+ post-quantum (PQ) hybrid key exchange (ML-KEM 768 combined with ECDHE).
+ - PASS: All HTTPS/TLS listeners on the load balancer use a PQ TLS policy.
+ - FAIL: At least one HTTPS/TLS listener uses a non-PQ TLS policy.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the PQ TLS policy check for every ELBv2 load balancer.
+
+ Returns:
+ A list of reports for load balancers with discovered listeners.
+ """
+ findings = []
+ pq_tls_policies = elbv2_client.audit_config.get(
+ "elbv2_listener_pqc_tls_allowed_policies", PQ_TLS_POLICIES_DEFAULT
+ )
+ for lb in elbv2_client.loadbalancersv2.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=lb)
+
+ if lb.listener_discovery_failed:
+ continue
+
+ has_tls_listeners = False
+ non_pq_listeners = []
+ for listener_arn, listener in lb.listeners.items():
+ if listener.protocol in ("HTTPS", "TLS"):
+ has_tls_listeners = True
+ if listener.ssl_policy not in pq_tls_policies:
+ ssl_policy = listener.ssl_policy or "<none>"
+ non_pq_listeners.append(
+ f"{listener.protocol}:{listener.port} ({listener_arn}) uses {ssl_policy}"
+ )
+
+ if not has_tls_listeners:
+ report.status = "PASS"
+ report.status_extended = f"ELBv2 {lb.name} has no HTTPS/TLS listeners."
+ findings.append(report)
+ continue
+
+ if non_pq_listeners:
+ report.status = "FAIL"
+ report.status_extended = f"ELBv2 {lb.name} has HTTPS/TLS listeners without post-quantum TLS policy: {', '.join(non_pq_listeners)}."
+ else:
+ report.status = "PASS"
+ report.status_extended = f"ELBv2 {lb.name} has all HTTPS/TLS listeners using a post-quantum TLS policy."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/elbv2/elbv2_service.py b/prowler/providers/aws/services/elbv2/elbv2_service.py
index c52110869f..e2d9bd3682 100644
--- a/prowler/providers/aws/services/elbv2/elbv2_service.py
+++ b/prowler/providers/aws/services/elbv2/elbv2_service.py
@@ -86,10 +86,14 @@ class ELBv2(AWSService):
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
else:
+ load_balancer[1].listener_discovery_failed = True
+ load_balancer[1].listener_discovery_error = str(error)
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
except Exception as error:
+ load_balancer[1].listener_discovery_failed = True
+ load_balancer[1].listener_discovery_error = str(error)
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
@@ -209,6 +213,8 @@ class LoadBalancerv2(BaseModel):
drop_invalid_header_fields: Optional[str]
cross_zone_load_balancing: Optional[str]
listeners: Dict[str, Listenerv2] = {}
+ listener_discovery_failed: bool = False
+ listener_discovery_error: Optional[str] = None
scheme: Optional[str]
security_groups: list[str] = []
# Key: ZoneName, Value: SubnetId
diff --git a/prowler/providers/aws/services/glue/glue_etl_jobs_no_secrets_in_arguments/glue_etl_jobs_no_secrets_in_arguments.py b/prowler/providers/aws/services/glue/glue_etl_jobs_no_secrets_in_arguments/glue_etl_jobs_no_secrets_in_arguments.py
index 50c92f8619..fec480efb1 100644
--- a/prowler/providers/aws/services/glue/glue_etl_jobs_no_secrets_in_arguments/glue_etl_jobs_no_secrets_in_arguments.py
+++ b/prowler/providers/aws/services/glue/glue_etl_jobs_no_secrets_in_arguments/glue_etl_jobs_no_secrets_in_arguments.py
@@ -1,52 +1,83 @@
-import json
-
-from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
-from prowler.providers.aws.services.glue.glue_client import glue_client
-
-
-class glue_etl_jobs_no_secrets_in_arguments(Check):
- """Check if Glue ETL jobs have secrets in their default arguments.
-
- Scans the DefaultArguments of each Glue job for hardcoded credentials,
- tokens, passwords, and other sensitive values that should be stored in
- Secrets Manager or Parameter Store instead.
- """
-
- def execute(self):
- findings = []
- secrets_ignore_patterns = glue_client.audit_config.get(
- "secrets_ignore_patterns", []
- )
- for job in glue_client.jobs:
- report = Check_Report_AWS(metadata=self.metadata(), resource=job)
- report.status = "PASS"
- report.status_extended = (
- f"No secrets found in Glue job {job.name} default arguments."
- )
-
- if job.arguments:
- secrets_found = []
- for arg_name, arg_value in job.arguments.items():
- detect_secrets_output = detect_secrets_scan(
- data=json.dumps({arg_name: arg_value}),
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=glue_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
- if detect_secrets_output:
- secrets_found.extend(
- [
- f"{secret['type']} in argument {arg_name}"
- for secret in detect_secrets_output
- ]
- )
-
- if secrets_found:
- report.status = "FAIL"
- report.status_extended = f"Potential secrets found in Glue job {job.name} default arguments: {', '.join(secrets_found)}."
-
- findings.append(report)
-
- return findings
+import json
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.glue.glue_client import glue_client
+
+
+class glue_etl_jobs_no_secrets_in_arguments(Check):
+ """Check if Glue ETL jobs have secrets in their default arguments.
+
+ Scans the DefaultArguments of each Glue job for hardcoded credentials,
+ tokens, passwords, and other sensitive values that should be stored in
+ Secrets Manager or Parameter Store instead.
+ """
+
+ def execute(self):
+ findings = []
+ secrets_ignore_patterns = glue_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = glue_client.audit_config.get("secrets_validate", False)
+ jobs = list(glue_client.jobs)
+
+ # Collect every default argument across all jobs and scan them in batched
+ # Kingfisher invocations instead of one subprocess per argument. Findings
+ # are keyed by (job index, argument name).
+ def payloads():
+ for job_index, job in enumerate(jobs):
+ if job.arguments:
+ for arg_name, arg_value in job.arguments.items():
+ yield (job_index, arg_name), json.dumps({arg_name: arg_value})
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for job_index, job in enumerate(jobs):
+ report = Check_Report_AWS(metadata=self.metadata(), resource=job)
+ report.status = "PASS"
+ report.status_extended = (
+ f"No secrets found in Glue job {job.name} default arguments."
+ )
+
+ if job.arguments and scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Glue job {job.name} default arguments for "
+ f"secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ if job.arguments:
+ secrets_found = []
+ all_secrets = []
+ for arg_name in job.arguments:
+ detect_secrets_output = batch_results.get((job_index, arg_name))
+ if detect_secrets_output:
+ all_secrets.extend(detect_secrets_output)
+ secrets_found.extend(
+ [
+ f"{secret['type']} in argument {arg_name}"
+ for secret in detect_secrets_output
+ ]
+ )
+
+ if secrets_found:
+ report.status = "FAIL"
+ report.status_extended = f"Potential secrets found in Glue job {job.name} default arguments: {', '.join(secrets_found)}."
+ annotate_verified_secrets(report, all_secrets)
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/iam/iam_policy_allows_privilege_escalation/iam_policy_allows_privilege_escalation.metadata.json b/prowler/providers/aws/services/iam/iam_policy_allows_privilege_escalation/iam_policy_allows_privilege_escalation.metadata.json
index 79b02882d7..4c7962242e 100644
--- a/prowler/providers/aws/services/iam/iam_policy_allows_privilege_escalation/iam_policy_allows_privilege_escalation.metadata.json
+++ b/prowler/providers/aws/services/iam/iam_policy_allows_privilege_escalation/iam_policy_allows_privilege_escalation.metadata.json
@@ -37,7 +37,8 @@
}
},
"Categories": [
- "identity-access"
+ "identity-access",
+ "privilege-escalation"
],
"DependsOn": [],
"RelatedTo": [],
diff --git a/prowler/providers/aws/services/iam/iam_service.py b/prowler/providers/aws/services/iam/iam_service.py
index d6cb150178..fa01550b11 100644
--- a/prowler/providers/aws/services/iam/iam_service.py
+++ b/prowler/providers/aws/services/iam/iam_service.py
@@ -103,6 +103,9 @@ class IAM(AWSService):
self._get_user_temporary_credentials_usage()
self.organization_features = []
self._list_organizations_features()
+ # ListRoles does not echo PermissionsBoundary; backfill via GetRole.
+ if self.roles:
+ self.__threading_call__(self._get_role_permissions_boundary, self.roles)
# List missing tags
self.__threading_call__(self._list_tags, self.users)
self.__threading_call__(self._list_tags, self.roles)
@@ -133,6 +136,7 @@ class IAM(AWSService):
arn=role["Arn"],
assume_role_policy=role["AssumeRolePolicyDocument"],
is_service_role=is_service_role(role),
+ permissions_boundary=role.get("PermissionsBoundary"),
)
)
except ClientError as error:
@@ -460,6 +464,34 @@ class IAM(AWSService):
f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_role_permissions_boundary(self, role):
+ """Backfill ``role.permissions_boundary`` via ``GetRole``.
+
+ ``ListRoles`` does not return ``PermissionsBoundary`` in practice, so
+ the value is fetched per role and stored on the ``Role`` model.
+
+ Args:
+ role: The ``Role`` instance to enrich.
+ """
+ try:
+ response = self.client.get_role(RoleName=role.name)
+ role.permissions_boundary = response.get("Role", {}).get(
+ "PermissionsBoundary"
+ )
+ except ClientError as error:
+ if error.response["Error"]["Code"] == "NoSuchEntity":
+ logger.warning(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ else:
+ logger.error(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{self.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _list_attached_role_policies(self):
logger.info("IAM - List Attached Role Policies...")
try:
@@ -1139,6 +1171,7 @@ class Role(BaseModel):
is_service_role: bool
attached_policies: list[dict] = []
inline_policies: list[str] = []
+ permissions_boundary: Optional[dict] = None
tags: Optional[list]
diff --git a/prowler/providers/aws/services/iam/lib/privilege_escalation.py b/prowler/providers/aws/services/iam/lib/privilege_escalation.py
index 9fded2d5c9..d7f16895d5 100644
--- a/prowler/providers/aws/services/iam/lib/privilege_escalation.py
+++ b/prowler/providers/aws/services/iam/lib/privilege_escalation.py
@@ -19,6 +19,7 @@ from prowler.providers.aws.services.iam.lib.policy import get_effective_actions
# - https://github.com/RhinoSecurityLabs/Security-Research/blob/master/tools/aws-pentest-tools/aws_escalate.py
# - https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/
# - https://github.com/DataDog/pathfinding.cloud (AWS IAM Privilege Escalation Path Library)
+# - https://www.beyondtrust.com/blog/entry/aws-agentcore-privilege-escalation (AWS Bedrock AgentCore)
privilege_escalation_policies_combination = {
# IAM self-escalation and policy manipulation
@@ -299,6 +300,7 @@ privilege_escalation_policies_combination = {
"PassRole+AgentCoreCreateInterpreter+InvokeInterpreter": {
"iam:PassRole",
"bedrock-agentcore:CreateCodeInterpreter",
+ "bedrock-agentcore:StartCodeInterpreterSession",
"bedrock-agentcore:InvokeCodeInterpreter",
},
# Prerequisite: Existing Bedrock code interpreter with admin role
@@ -306,6 +308,40 @@ privilege_escalation_policies_combination = {
"bedrock-agentcore:StartCodeInterpreterSession",
"bedrock-agentcore:InvokeCodeInterpreter",
},
+ # Prerequisite: Existing AgentCore Runtime or Harness with admin execution role.
+ # InvokeAgentRuntimeCommand runs shell commands as root inside the microVM and
+ # reads the execution role credentials from MMDS, bypassing the agent and guardrails.
+ "AgentCoreInvokeRuntimeCommand": {
+ "bedrock-agentcore:InvokeAgentRuntimeCommand",
+ },
+ "PassRole+AgentCoreCreateRuntime+InvokeRuntimeCommand": {
+ "iam:PassRole",
+ "bedrock-agentcore:CreateAgentRuntime",
+ "bedrock-agentcore:CreateAgentRuntimeEndpoint",
+ "bedrock-agentcore:CreateWorkloadIdentity",
+ "bedrock-agentcore:InvokeAgentRuntimeCommand",
+ },
+ "PassRole+AgentCoreCreateHarness+InvokeRuntimeCommand": {
+ "iam:PassRole",
+ "bedrock-agentcore:CreateHarness",
+ "bedrock-agentcore:CreateAgentRuntime",
+ "bedrock-agentcore:CreateAgentRuntimeEndpoint",
+ "bedrock-agentcore:CreateWorkloadIdentity",
+ "bedrock-agentcore:GetAgentRuntime",
+ "bedrock-agentcore:InvokeAgentRuntimeCommand",
+ },
+ # Prerequisite: Existing AgentCore Custom Browser with admin execution role.
+ # A remote CDP driver on the browser session reads the role credentials from MMDS.
+ "AgentCoreBrowserSessionConnect": {
+ "bedrock-agentcore:StartBrowserSession",
+ "bedrock-agentcore:ConnectBrowserAutomationStream",
+ },
+ "PassRole+AgentCoreCreateBrowser+ConnectBrowser": {
+ "iam:PassRole",
+ "bedrock-agentcore:CreateBrowser",
+ "bedrock-agentcore:StartBrowserSession",
+ "bedrock-agentcore:ConnectBrowserAutomationStream",
+ },
# TO-DO: We have to handle AssumeRole just if the resource is * and without conditions
# "sts:AssumeRole": {"sts:AssumeRole"},
}
diff --git a/prowler/providers/aws/services/inspector2/inspector2_is_enabled/inspector2_is_enabled.py b/prowler/providers/aws/services/inspector2/inspector2_is_enabled/inspector2_is_enabled.py
index a9f5efbedd..fd414badfa 100644
--- a/prowler/providers/aws/services/inspector2/inspector2_is_enabled/inspector2_is_enabled.py
+++ b/prowler/providers/aws/services/inspector2/inspector2_is_enabled/inspector2_is_enabled.py
@@ -15,11 +15,10 @@ class inspector2_is_enabled(Check):
if inspector.status == "ENABLED":
report.status = "PASS"
report.status_extended = "Inspector2 is enabled for EC2 instances, ECR container images, Lambda functions and code."
- funtions_in_region = False
+ functions_in_region = (
+ inspector.region in awslambda_client.regions_with_functions
+ )
ec2_in_region = False
- for function in awslambda_client.functions.values():
- if function.region == inspector.region:
- funtions_in_region = True
for instance in ec2_client.instances:
if instance == inspector.region:
ec2_in_region = True
@@ -36,12 +35,12 @@ class inspector2_is_enabled(Check):
failed_services.append("ECR")
if inspector.lambda_status != "ENABLED" and (
inspector2_client.provider.scan_unused_services
- or funtions_in_region
+ or functions_in_region
):
failed_services.append("Lambda")
if inspector.lambda_code_status != "ENABLED" and (
inspector2_client.provider.scan_unused_services
- or funtions_in_region
+ or functions_in_region
):
failed_services.append("Lambda Code")
diff --git a/prowler/providers/aws/services/organizations/organizations_scp_check_deny_regions/organizations_scp_check_deny_regions.py b/prowler/providers/aws/services/organizations/organizations_scp_check_deny_regions/organizations_scp_check_deny_regions.py
index cced82a762..1b676ff0b5 100644
--- a/prowler/providers/aws/services/organizations/organizations_scp_check_deny_regions/organizations_scp_check_deny_regions.py
+++ b/prowler/providers/aws/services/organizations/organizations_scp_check_deny_regions/organizations_scp_check_deny_regions.py
@@ -67,7 +67,7 @@ class organizations_scp_check_deny_regions(Check):
# Allow if Condition = {"StringEquals": {"aws:RequestedRegion": [region1, region2]}}
if (
- policy.content.get("Statement") == "Allow"
+ statement.get("Effect") == "Allow"
and "Condition" in statement
and "StringEquals" in statement["Condition"]
and "aws:RequestedRegion"
diff --git a/tests/providers/alibabacloud/services/cs/cs_kubernetes_rbac_enabled/__init__.py b/prowler/providers/aws/services/rolesanywhere/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/cs/cs_kubernetes_rbac_enabled/__init__.py
rename to prowler/providers/aws/services/rolesanywhere/__init__.py
diff --git a/prowler/providers/aws/services/rolesanywhere/rolesanywhere_client.py b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_client.py
new file mode 100644
index 0000000000..254f0a5dbf
--- /dev/null
+++ b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.aws.services.rolesanywhere.rolesanywhere_service import (
+ RolesAnywhere,
+)
+from prowler.providers.common.provider import Provider
+
+rolesanywhere_client = RolesAnywhere(Provider.get_global_provider())
diff --git a/prowler/providers/aws/services/rolesanywhere/rolesanywhere_service.py b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_service.py
new file mode 100644
index 0000000000..46dca281d6
--- /dev/null
+++ b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_service.py
@@ -0,0 +1,64 @@
+from typing import Dict, List
+
+from pydantic.v1 import BaseModel, Field
+
+from prowler.lib.logger import logger
+from prowler.lib.scan_filters.scan_filters import is_resource_filtered
+from prowler.providers.aws.lib.service.service import AWSService
+
+
+class RolesAnywhere(AWSService):
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ self.trust_anchors = {}
+ self.__threading_call__(self._list_trust_anchors)
+
+ def _list_trust_anchors(self, regional_client):
+ logger.info("RolesAnywhere - Listing Trust Anchors...")
+ try:
+ paginator = regional_client.get_paginator("list_trust_anchors")
+ for page in paginator.paginate():
+ for ta in page.get("trustAnchors", []):
+ arn = ta.get("trustAnchorArn", "")
+ if not arn:
+ continue
+ if self.audit_resources and not is_resource_filtered(
+ arn, self.audit_resources
+ ):
+ continue
+ source = ta.get("source", {}) or {}
+ source_data = source.get("sourceData", {}) or {}
+ tags = []
+ try:
+ tags = regional_client.list_tags_for_resource(
+ resourceArn=arn
+ ).get("tags", [])
+ except Exception as error:
+ logger.warning(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ self.trust_anchors[arn] = TrustAnchor(
+ arn=arn,
+ id=ta.get("trustAnchorId", ""),
+ name=ta.get("name", ""),
+ region=regional_client.region,
+ enabled=ta.get("enabled", False),
+ source_type=source.get("sourceType", ""),
+ acm_pca_arn=source_data.get("acmPcaArn", ""),
+ tags=tags,
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class TrustAnchor(BaseModel):
+ arn: str
+ id: str
+ name: str
+ region: str
+ enabled: bool = False
+ source_type: str = ""
+ acm_pca_arn: str = ""
+ tags: List[Dict[str, str]] = Field(default_factory=list)
diff --git a/tests/providers/alibabacloud/services/ecs/__init__.py b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/__init__.py
rename to prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/__init__.py
diff --git a/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.metadata.json b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.metadata.json
new file mode 100644
index 0000000000..7d919f83a7
--- /dev/null
+++ b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "aws",
+ "CheckID": "rolesanywhere_trust_anchor_pqc_pki",
+ "CheckTitle": "IAM Roles Anywhere trust anchors are backed by a post-quantum (ML-DSA) PKI",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "rolesanywhere",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsRolesAnywhereTrustAnchor",
+ "ResourceGroup": "security",
+ "Description": "**IAM Roles Anywhere trust anchors** are assessed for use of a **post-quantum digital signature algorithm** (ML-DSA). A trust anchor backed by an AWS Private CA whose `KeyAlgorithm` is RSA or ECC produces signatures vulnerable to forgery by a future quantum attacker, allowing an unintended actor to issue certificates and obtain unauthorized AWS access.",
+ "Risk": "Trust anchors are the root of trust for workloads authenticating to AWS via X.509 certificates. If the signing CA uses RSA or ECC, an attacker with quantum capability could forge end-entity certificates and impersonate workloads. Migrating trust anchors to **ML-DSA-backed PKI** (NIST FIPS 204) protects this control plane in the post-quantum era.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/rolesanywhere/latest/userguide/introduction.html",
+ "https://aws.amazon.com/about-aws/whats-new/2026/03/iam-roles-anywhere-post-quantum-digital-certificates/",
+ "https://aws.amazon.com/security/post-quantum-cryptography/",
+ "https://csrc.nist.gov/pubs/fips/204/final"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws rolesanywhere create-trust-anchor --name pqc-trust --source 'sourceType=AWS_ACM_PCA,sourceData={acmPcaArn=<ml_dsa_ca_arn>}' --enabled",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::RolesAnywhere::TrustAnchor\n Properties:\n Name: pqc-trust\n Enabled: true\n Source:\n SourceType: AWS_ACM_PCA\n SourceData:\n AcmPcaArn: <ml_dsa_ca_arn> # FIX: PCA must use ML_DSA key algorithm\n```",
+ "Other": "1. Create a new AWS Private CA with a post-quantum KeyAlgorithm (ML_DSA_44/65/87)\n2. Create a new Roles Anywhere trust anchor with sourceType=AWS_ACM_PCA pointing to the new CA\n3. Rotate end-entity certificates issued from the new CA\n4. Delete the legacy trust anchor once workloads have rotated",
+ "Terraform": "```hcl\nresource \"aws_rolesanywhere_trust_anchor\" \"<example_resource_name>\" {\n name = \"pqc-trust\"\n enabled = true\n source {\n source_type = \"AWS_ACM_PCA\"\n source_data {\n acm_pca_arn = \"<ml_dsa_ca_arn>\" # FIX: PCA must use ML_DSA key algorithm\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Back IAM Roles Anywhere trust anchors with an **AWS Private CA that uses an ML-DSA key algorithm**. For trust anchors backed by an external certificate bundle, ensure the certificates were issued by an ML-DSA CA and re-verify periodically as the cryptographic landscape evolves.",
+ "Url": "https://hub.prowler.com/check/rolesanywhere_trust_anchor_pqc_pki"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [
+ "acmpca_certificate_authority_pqc_key_algorithm"
+ ],
+ "RelatedTo": [],
+ "Notes": "Trust anchors backed by an external CERTIFICATE_BUNDLE cannot be evaluated automatically by this check and are reported as FAIL with guidance to migrate to an AWS Private CA using an ML-DSA key algorithm."
+}
diff --git a/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.py b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.py
new file mode 100644
index 0000000000..495ed4e9c7
--- /dev/null
+++ b/prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/rolesanywhere_trust_anchor_pqc_pki.py
@@ -0,0 +1,79 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.acmpca.acmpca_client import acmpca_client
+from prowler.providers.aws.services.rolesanywhere.rolesanywhere_client import (
+ rolesanywhere_client,
+)
+
+PQC_PCA_KEY_ALGORITHMS_DEFAULT = [
+ "ML_DSA_44",
+ "ML_DSA_65",
+ "ML_DSA_87",
+]
+
+
+class rolesanywhere_trust_anchor_pqc_pki(Check):
+ """Verify that IAM Roles Anywhere trust anchors are backed by a post-quantum PKI.
+
+ For trust anchors whose source is ``AWS_ACM_PCA``, the linked Private CA's
+ ``KeyAlgorithm`` is checked against the configured ML-DSA allowlist.
+ Trust anchors backed by an external ``CERTIFICATE_BUNDLE`` are reported as
+ FAIL because their certificate signature algorithm cannot be inspected
+ from the IAM Roles Anywhere API alone.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ findings = []
+ pqc_algorithms = rolesanywhere_client.audit_config.get(
+ "rolesanywhere_pqc_pca_key_algorithms", PQC_PCA_KEY_ALGORITHMS_DEFAULT
+ )
+ for trust_anchor in rolesanywhere_client.trust_anchors.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=trust_anchor)
+ if trust_anchor.source_type == "AWS_ACM_PCA":
+ linked_ca = acmpca_client.certificate_authorities.get(
+ trust_anchor.acm_pca_arn
+ )
+ if linked_ca and linked_ca.status != "ACTIVE":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"IAM Roles Anywhere trust anchor {trust_anchor.name} is "
+ f"backed by Private CA {linked_ca.id}, which is in "
+ f"{linked_ca.status or '<unknown>'} status and cannot be "
+ "used as an active post-quantum PKI trust root."
+ )
+ elif linked_ca and linked_ca.key_algorithm in pqc_algorithms:
+ report.status = "PASS"
+ report.status_extended = (
+ f"IAM Roles Anywhere trust anchor {trust_anchor.name} is "
+ f"backed by Private CA {linked_ca.id} using post-quantum "
+ f"key algorithm {linked_ca.key_algorithm}."
+ )
+ elif linked_ca:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"IAM Roles Anywhere trust anchor {trust_anchor.name} is "
+ f"backed by Private CA {linked_ca.id} using key algorithm "
+ f"{linked_ca.key_algorithm or '<unknown>'}, which is not "
+ "post-quantum (ML-DSA)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"IAM Roles Anywhere trust anchor {trust_anchor.name} is "
+ f"backed by Private CA {trust_anchor.acm_pca_arn}, which "
+ "could not be inspected (cross-account or missing "
+ "acm-pca permissions). Verify the CA uses an ML-DSA key "
+ "algorithm."
+ )
+ else:
+ source = trust_anchor.source_type or "<none>"
+ report.status = "FAIL"
+ report.status_extended = (
+ f"IAM Roles Anywhere trust anchor {trust_anchor.name} uses "
+ f"source type {source}; the certificate signature algorithm "
+ "cannot be inspected automatically. Migrate to an AWS Private "
+ "CA using an ML-DSA key algorithm to enable post-quantum "
+ "evaluation."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/route53/route53_dangling_ip_subdomain_takeover/route53_dangling_ip_subdomain_takeover.py b/prowler/providers/aws/services/route53/route53_dangling_ip_subdomain_takeover/route53_dangling_ip_subdomain_takeover.py
index caf3629816..25703b979f 100644
--- a/prowler/providers/aws/services/route53/route53_dangling_ip_subdomain_takeover/route53_dangling_ip_subdomain_takeover.py
+++ b/prowler/providers/aws/services/route53/route53_dangling_ip_subdomain_takeover/route53_dangling_ip_subdomain_takeover.py
@@ -1,10 +1,9 @@
import re
from ipaddress import ip_address
-import awsipranges
-
from prowler.lib.check.models import Check, Check_Report_AWS
from prowler.lib.utils.utils import validate_ip_address
+from prowler.providers.aws.lib.ip_ranges.ip_ranges import get_public_ip_networks
from prowler.providers.aws.services.ec2.ec2_client import ec2_client
from prowler.providers.aws.services.route53.route53_client import route53_client
from prowler.providers.aws.services.s3.s3_client import s3_client
@@ -21,6 +20,10 @@ class route53_dangling_ip_subdomain_takeover(Check):
def execute(self) -> Check_Report_AWS:
findings = []
+ # AWS public IP prefixes are fetched lazily, at most once per run, only
+ # when a dangling-candidate public IP is found.
+ aws_ip_networks = None
+
# When --region is used, Route53 service gathers EIPs from all regions
# to avoid false positives. Otherwise, use ec2_client data directly.
if route53_client.all_account_elastic_ips:
@@ -42,6 +45,7 @@ class route53_dangling_ip_subdomain_takeover(Check):
if record_set.type == "A" and not record_set.is_alias:
for record in record_set.records:
if validate_ip_address(record):
+ record_ip = ip_address(record)
report = Check_Report_AWS(
metadata=self.metadata(), resource=record_set
)
@@ -53,14 +57,12 @@ class route53_dangling_ip_subdomain_takeover(Check):
report.status = "PASS"
report.status_extended = f"Route53 record {record} (name: {record_set.name}) in Hosted Zone {hosted_zone.name} is not a dangling IP."
# If Public IP check if it is in the AWS Account
- if (
- not ip_address(record).is_private
- and record not in public_ips
- ):
+ if not record_ip.is_private and record not in public_ips:
report.status_extended = f"Route53 record {record} (name: {record_set.name}) in Hosted Zone {hosted_zone.name} does not belong to AWS and it is not a dangling IP."
# Check if potential dangling IP is within AWS Ranges
- aws_ip_ranges = awsipranges.get_ranges()
- if aws_ip_ranges.get(record):
+ if aws_ip_networks is None:
+ aws_ip_networks = get_public_ip_networks()
+ if any(record_ip in network for network in aws_ip_networks):
report.status = "FAIL"
report.status_extended = f"Route53 record {record} (name: {record_set.name}) in Hosted Zone {hosted_zone.name} is a dangling IP which can lead to a subdomain takeover attack."
findings.append(report)
diff --git a/prowler/providers/aws/services/s3/s3_bucket_default_encryption/s3_bucket_default_encryption.metadata.json b/prowler/providers/aws/services/s3/s3_bucket_default_encryption/s3_bucket_default_encryption.metadata.json
index eb0c07e8af..bda2595347 100644
--- a/prowler/providers/aws/services/s3/s3_bucket_default_encryption/s3_bucket_default_encryption.metadata.json
+++ b/prowler/providers/aws/services/s3/s3_bucket_default_encryption/s3_bucket_default_encryption.metadata.json
@@ -1,7 +1,7 @@
{
"Provider": "aws",
"CheckID": "s3_bucket_default_encryption",
- "CheckTitle": "S3 bucket has default server-side encryption (SSE) enabled",
+ "CheckTitle": "[DEPRECATED] S3 bucket has default server-side encryption (SSE) enabled",
"CheckType": [
"Software and Configuration Checks/AWS Security Best Practices",
"Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices",
@@ -14,13 +14,11 @@
"Severity": "medium",
"ResourceType": "AwsS3Bucket",
"ResourceGroup": "storage",
- "Description": "**Amazon S3 buckets** have a default **server-side encryption** setting that automatically encrypts new objects using `SSE-S3` or `SSE-KMS`. This evaluates whether a bucket has a default encryption configuration defined.",
+ "Description": "[DEPRECATED] **Amazon S3 buckets** have a default **server-side encryption** setting that automatically encrypts new objects using `SSE-S3` or `SSE-KMS`. This evaluates whether a bucket has a default encryption configuration defined.",
"Risk": "Without default encryption, older objects may remain unencrypted and new uploads won't be forced to use `SSE-KMS`. This reduces confidentiality and governance by limiting key audit logs, rotation, and cross-account controls, and increases exposure if data is copied, replicated, or accessed outside intended paths.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://docs.amazonaws.cn/en_us/AmazonS3/latest/userguide/bucket-encryption.html",
- "https://aws.amazon.com/blogs/security/how-to-prevent-uploads-of-unencrypted-objects-to-amazon-s3/",
- "https://docs.aws.amazon.com/us_en/AmazonS3/latest/userguide/default-encryption-faq.html"
+ "https://docs.aws.amazon.com/AmazonS3/latest/userguide/default-encryption-faq.html"
],
"Remediation": {
"Code": {
@@ -39,5 +37,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": ""
+ "Notes": "This check is being deprecated since AWS automatically applies SSE-S3 to every S3 bucket (both new buckets and previously-unencrypted existing buckets) as of January 5, 2023, and encryption can no longer be disabled. For SSE-KMS validation, use `s3_bucket_kms_encryption` instead."
}
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_attached_disk_encrypted/__init__.py b/prowler/providers/aws/services/s3/s3_bucket_object_public/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_attached_disk_encrypted/__init__.py
rename to prowler/providers/aws/services/s3/s3_bucket_object_public/__init__.py
diff --git a/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.metadata.json b/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.metadata.json
new file mode 100644
index 0000000000..197a5aa205
--- /dev/null
+++ b/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "aws",
+ "CheckID": "s3_bucket_object_public",
+ "CheckTitle": "Spot-check S3 bucket objects for public ACLs",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Effects/Data Exposure"
+ ],
+ "ServiceName": "s3",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "arn:partition:s3:::resource",
+ "Severity": "low",
+ "ResourceType": "AwsS3Bucket",
+ "Description": "Spot-checks a configurable sample of objects in each S3 bucket and flags any whose ACL grants access to the AllUsers or AuthenticatedUsers groups. This is a sampling-based check, not a comprehensive audit, so public objects outside the sample can be missed. It is disabled by default and must be enabled via the s3_bucket_object_public_enabled configuration flag.",
+ "Risk": "Public objects can be accessed by anyone on the internet, potentially leaking sensitive data. A bucket can appear private at the bucket-policy level while still containing individual objects with public ACL grants.",
+ "RelatedUrl": "",
+ "Remediation": {
+ "Code": {
+ "CLI": "aws s3api put-object-acl --bucket <bucket_name> --key <object_key> --acl private",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "For complete coverage, enable the s3_bucket_acl_prohibited check, which enforces the BucketOwnerEnforced Object Ownership setting (AWS's recommended approach since April 2023) and prevents public object ACLs entirely. Use this spot-check as a supplementary tool for manual assessments.",
+ "Url": "https://hub.prowler.com/check/s3_bucket_object_public"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "s3_bucket_acl_prohibited"
+ ],
+ "Notes": "Disabled by default. Configure s3_bucket_object_public_enabled, s3_bucket_object_public_max_objects, and s3_bucket_object_public_sample_size in the Prowler configuration. Because only a sample of objects is inspected, a PASS does not guarantee the bucket is free of public objects; use s3_bucket_acl_prohibited for full assurance."
+}
diff --git a/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.py b/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.py
new file mode 100644
index 0000000000..9912da561b
--- /dev/null
+++ b/prowler/providers/aws/services/s3/s3_bucket_object_public/s3_bucket_object_public.py
@@ -0,0 +1,82 @@
+from typing import List
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.s3.s3_client import s3_client
+
+# ACL grantee groups that make an object effectively public. AllUsers is anyone on
+# the internet; AuthenticatedUsers is any authenticated AWS principal (any account).
+PUBLIC_ACL_URIS = {
+ "http://acs.amazonaws.com/groups/global/AllUsers",
+ "http://acs.amazonaws.com/groups/global/AuthenticatedUsers",
+}
+
+
+class s3_bucket_object_public(Check):
+ """Spot-check a sample of S3 bucket objects for public ACL grants."""
+
+ def execute(self) -> List[Check_Report_AWS]:
+ """Evaluate sampled object ACLs for AllUsers/AuthenticatedUsers grants.
+
+ Returns:
+ List[Check_Report_AWS]: One report per sampled bucket (empty when the
+ check is disabled via configuration).
+ """
+ findings = []
+
+ if not s3_client.audit_config.get("s3_bucket_object_public_enabled", False):
+ return findings
+
+ for bucket in s3_client.buckets.values():
+ sampling = bucket.object_sampling
+ # Sampling is populated by the service layer only when the check is
+ # enabled; skip any bucket that was not sampled.
+ if sampling is None or not sampling.performed:
+ continue
+
+ report = Check_Report_AWS(metadata=self.metadata(), resource=bucket)
+
+ if sampling.error_code is not None:
+ report.status = "MANUAL"
+ if sampling.error_code == "AccessDenied":
+ report.status_extended = (
+ f"Access Denied when spot-checking objects in bucket "
+ f"{bucket.name}."
+ )
+ else:
+ report.status_extended = (
+ f"Could not spot-check objects in bucket {bucket.name}: "
+ f"{sampling.error_message}."
+ )
+ elif sampling.is_empty:
+ report.status = "PASS"
+ report.status_extended = f"S3 Bucket {bucket.name} is empty."
+ else:
+ public_objects = [
+ obj.key
+ for obj in sampling.objects
+ if any(
+ grantee.type == "Group" and grantee.URI in PUBLIC_ACL_URIS
+ for grantee in obj.grantees
+ )
+ ]
+ sampled = len(sampling.objects)
+
+ if public_objects:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"S3 Bucket {bucket.name} has public objects detected in "
+ f"spot-check sample of {sampled} objects: "
+ f"{', '.join(public_objects)}."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"No public objects detected in spot-check sample of "
+ f"{sampled} objects in bucket {bucket.name}. For complete "
+ f"assurance, ensure ACLs are disabled via Object Ownership "
+ f"settings."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/s3/s3_service.py b/prowler/providers/aws/services/s3/s3_service.py
index 00605fbe6e..94768138df 100644
--- a/prowler/providers/aws/services/s3/s3_service.py
+++ b/prowler/providers/aws/services/s3/s3_service.py
@@ -36,6 +36,10 @@ class S3(AWSService):
self.__threading_call__(
self._get_bucket_notification_configuration, self.buckets.values()
)
+ # Object-level ACL sampling is expensive and opt-in, so only run it when
+ # the s3_bucket_object_public check is explicitly enabled in the config.
+ if self.audit_config.get("s3_bucket_object_public_enabled", False):
+ self.__threading_call__(self._get_public_objects, self.buckets.values())
def _list_buckets(self, provider):
logger.info("S3 - Listing buckets...")
@@ -487,6 +491,69 @@ class S3(AWSService):
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_public_objects(self, bucket):
+ logger.info("S3 - Spot-checking bucket objects for public ACLs...")
+ max_objects = self.audit_config.get("s3_bucket_object_public_max_objects", 100)
+ sample_size = self.audit_config.get("s3_bucket_object_public_sample_size", 3)
+ # Guard against misconfigured non-positive values: a zero sample size would
+ # raise ZeroDivisionError and a negative one would silently sample nothing.
+ if not isinstance(max_objects, int) or max_objects <= 0:
+ max_objects = 100
+ if not isinstance(sample_size, int) or sample_size <= 0:
+ sample_size = 3
+ sampling = BucketObjectSampling(performed=True)
+ regional_client = None
+ try:
+ regional_client = self.regional_clients[bucket.region]
+ contents = regional_client.list_objects_v2(
+ Bucket=bucket.name, MaxKeys=max_objects
+ ).get("Contents", [])
+
+ if not contents:
+ sampling.is_empty = True
+ bucket.object_sampling = sampling
+ return
+
+ all_keys = [obj["Key"] for obj in contents]
+ # Deterministic, evenly-spaced sampling so findings are reproducible
+ # across scans instead of flipping between PASS/FAIL with a random sample.
+ if len(all_keys) <= sample_size:
+ sample_keys = all_keys
+ else:
+ step = len(all_keys) // sample_size
+ sample_keys = [all_keys[i * step] for i in range(sample_size)]
+
+ for key in sample_keys:
+ acl = regional_client.get_object_acl(Bucket=bucket.name, Key=key)
+ grantees = []
+ for grant in acl.get("Grants", []):
+ grant_grantee = grant.get("Grantee", {})
+ grantee = ACL_Grantee(type=grant_grantee.get("Type", ""))
+ grantee.display_name = grant_grantee.get("DisplayName")
+ grantee.ID = grant_grantee.get("ID")
+ grantee.URI = grant_grantee.get("URI")
+ grantee.permission = grant.get("Permission")
+ grantees.append(grantee)
+ sampling.objects.append(ObjectACL(key=key, grantees=grantees))
+
+ bucket.object_sampling = sampling
+ except ClientError as error:
+ sampling.error_code = error.response["Error"]["Code"]
+ sampling.error_message = str(error)
+ bucket.object_sampling = sampling
+ region = regional_client.region if regional_client else bucket.region
+ logger.warning(
+ f"{region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ sampling.error_code = error.__class__.__name__
+ sampling.error_message = str(error)
+ bucket.object_sampling = sampling
+ region = regional_client.region if regional_client else bucket.region
+ logger.error(
+ f"{region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _head_bucket(self, bucket_name):
logger.info("S3 - Checking if bucket exists...")
try:
@@ -654,6 +721,19 @@ class PublicAccessBlock(BaseModel):
restrict_public_buckets: bool
+class ObjectACL(BaseModel):
+ key: str
+ grantees: List[ACL_Grantee] = Field(default_factory=list)
+
+
+class BucketObjectSampling(BaseModel):
+ performed: bool = False
+ is_empty: bool = False
+ objects: List[ObjectACL] = Field(default_factory=list)
+ error_code: Optional[str] = None
+ error_message: Optional[str] = None
+
+
class AccessPoint(BaseModel):
arn: str
account_id: str
@@ -703,3 +783,4 @@ class Bucket(BaseModel):
lifecycle: List[LifeCycleRule] = Field(default_factory=list)
replication_rules: List[ReplicationRule] = Field(default_factory=list)
notification_config: Dict = Field(default_factory=dict)
+ object_sampling: Optional[BucketObjectSampling] = None
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_instance_endpoint_protection_installed/__init__.py b/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_instance_endpoint_protection_installed/__init__.py
rename to prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/__init__.py
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.metadata.json b/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.metadata.json
new file mode 100644
index 0000000000..0e127a7759
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "aws",
+ "CheckID": "sagemaker_clarify_exists",
+ "CheckTitle": "Amazon SageMaker Clarify processing jobs exist in the region",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "sagemaker",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "Other",
+ "ResourceGroup": "ai_ml",
+ "Description": "**SageMaker Clarify** provides bias detection and model explainability for ML workloads.\n\nThis check verifies that at least one SageMaker processing job using the AWS-managed Clarify container image exists in each successfully scanned region. The absence of Clarify jobs indicates that responsible-AI controls such as bias detection and explainability are not in place.",
+ "Risk": "Without **SageMaker Clarify** processing jobs, ML models may be deployed without bias analysis or explainability reports. This can lead to:\n- **Regulatory non-compliance** with AI governance frameworks\n- **Undetected bias** in model predictions affecting protected groups\n- **Lack of accountability** for ML model decisions in production",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/clarify-configure-processing-jobs.html",
+ "https://docs.aws.amazon.com/sagemaker/latest/dg-ecr-paths/sagemaker-algo-docker-registry-paths.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws sagemaker create-processing-job --processing-job-name clarify-bias-check --app-specification ImageUri=<clarify-image-uri> --role-arn <role-arn> --processing-resources 'ClusterConfig={InstanceCount=1,InstanceType=ml.m5.xlarge,VolumeSizeInGB=20}'",
+ "NativeIaC": "",
+ "Other": "1. Open the AWS Console and go to Amazon SageMaker\n2. Navigate to Processing > Processing jobs\n3. Click Create processing job\n4. Select the SageMaker Clarify container image for your region\n5. Configure input/output paths and the analysis configuration\n6. Click Create processing job",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Create SageMaker Clarify processing jobs to evaluate models for bias and explainability before deployment. Integrate Clarify into your ML pipeline to ensure responsible AI practices.",
+ "Url": "https://hub.prowler.com/check/sagemaker_clarify_exists"
+ }
+ },
+ "Categories": [
+ "gen-ai"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Results are generated per scanned region. Regions where `ListProcessingJobs` cannot be queried are omitted from the findings."
+}
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.py b/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.py
new file mode 100644
index 0000000000..9c559613d3
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_clarify_exists/sagemaker_clarify_exists.py
@@ -0,0 +1,54 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.sagemaker.sagemaker_client import sagemaker_client
+
+
+class sagemaker_clarify_exists(Check):
+ """Check whether at least one SageMaker Clarify processing job exists per region.
+
+ A region is reported only when ListProcessingJobs succeeded for it; regions
+ where the API call failed (e.g. AccessDenied, unsupported region) are
+ skipped at the service layer and produce no finding.
+
+ - PASS: At least one processing job uses the AWS-managed Clarify container
+ image in the region (one finding per job).
+ - FAIL: No processing job uses the Clarify container image in the region
+ (one finding per region).
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the SageMaker Clarify exists check.
+
+ Returns:
+ A list of reports containing the result of the check.
+ """
+ findings = []
+ for region in sorted(sagemaker_client.processing_jobs_scanned_regions):
+ clarify_jobs = sorted(
+ (
+ job
+ for job in sagemaker_client.sagemaker_processing_jobs
+ if job.region == region
+ and job.image_uri
+ and "sagemaker-clarify-processing" in job.image_uri
+ ),
+ key=lambda job: job.name,
+ )
+
+ if clarify_jobs:
+ for job in clarify_jobs:
+ report = Check_Report_AWS(metadata=self.metadata(), resource=job)
+ report.status = "PASS"
+ report.status_extended = f"SageMaker Clarify processing job {job.name} exists in region {region}."
+ findings.append(report)
+ else:
+ report = Check_Report_AWS(metadata=self.metadata(), resource={})
+ report.region = region
+ report.resource_id = "sagemaker-clarify"
+ report.resource_arn = f"arn:{sagemaker_client.audited_partition}:sagemaker:{region}:{sagemaker_client.audited_account}:processing-job"
+ report.status = "FAIL"
+ report.status_extended = (
+ f"No SageMaker Clarify processing jobs found in region {region}."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_instance_latest_os_patches_applied/__init__.py b/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_instance_latest_os_patches_applied/__init__.py
rename to prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/__init__.py
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.metadata.json b/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.metadata.json
new file mode 100644
index 0000000000..d1d025fe7e
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "aws",
+ "CheckID": "sagemaker_models_monitor_enabled",
+ "CheckTitle": "Amazon SageMaker has a monitoring schedule scheduled",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices"
+ ],
+ "ServiceName": "sagemaker",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "Other",
+ "ResourceGroup": "ai_ml",
+ "Description": "**SageMaker Models Monitor** detects data drift, model quality issues, and bias drift in production.",
+ "Risk": "Without an **active monitoring schedule**, data drift, model quality issues, and bias drift go undetected, so **model quality degrades silently** while downstream decisions such as fraud detection, access control, and pricing keep relying on a degrading model.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor.html",
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor-scheduling.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **Amazon SageMaker Model Monitor** and keep at least one **monitoring schedule** in the `Scheduled` state so data quality, model quality, and bias drift are continuously evaluated against a baseline.",
+ "Url": "https://hub.prowler.com/check/sagemaker_models_monitor_enabled"
+ }
+ },
+ "Categories": [
+ "gen-ai"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.py b/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.py
new file mode 100644
index 0000000000..f9f893a895
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_models_monitor_enabled/sagemaker_models_monitor_enabled.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.sagemaker.sagemaker_client import sagemaker_client
+
+
+class sagemaker_models_monitor_enabled(Check):
+ def execute(self):
+ findings = []
+ for monitoring_schedule in sagemaker_client.sagemaker_monitoring_schedules:
+ report = Check_Report_AWS(
+ metadata=self.metadata(), resource=monitoring_schedule
+ )
+ if monitoring_schedule.is_scheduled:
+ report.status = "PASS"
+ report.status_extended = f"SageMaker monitoring schedule {monitoring_schedule.name} is enabled in region {monitoring_schedule.region}."
+ elif not monitoring_schedule.has_schedules:
+ report.status = "FAIL"
+ report.status_extended = f"No SageMaker monitoring schedules found in region {monitoring_schedule.region}."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"No active SageMaker monitoring schedule in region {monitoring_schedule.region}; existing schedules are not in Scheduled status."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_instance_no_legacy_network/__init__.py b/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_instance_no_legacy_network/__init__.py
rename to prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/__init__.py
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.metadata.json b/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.metadata.json
new file mode 100644
index 0000000000..fe9bd5db95
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.metadata.json
@@ -0,0 +1,42 @@
+{
+ "Provider": "aws",
+ "CheckID": "sagemaker_models_registry_in_use",
+ "CheckTitle": "Amazon SageMaker Model Registry should have at least one approved model package",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "sagemaker",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "Other",
+ "ResourceGroup": "ai_ml",
+ "Description": "**SageMaker Model Registry** is evaluated to verify that at least one Model Package Group exists and contains at least one model package with **ModelApprovalStatus = Approved**. This confirms that the ML governance workflow (register → review → approve → deploy) is actively in use.",
+ "Risk": "An empty Model Registry, or one with no approved packages, indicates that models are being deployed outside any review process. This breaks provenance and accountability for production ML workloads, making it impossible to enforce governance controls such as auditing, versioning, and approval workflows.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry.html",
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry-approve.html",
+ "https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_ListModelPackageGroups.html",
+ "https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_ListModelPackages.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws sagemaker list-model-package-groups\naws sagemaker list-model-packages --model-package-group-name <group-name>\naws sagemaker update-model-package --model-package-arn <arn> --model-approval-status Approved",
+ "NativeIaC": "",
+ "Other": "1. In the AWS console, navigate to SageMaker > Models > Model Registry.\n2. Create a Model Package Group if none exists.\n3. Register a model version in the group.\n4. Review and approve at least one model package by setting its approval status to Approved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Register all production models in the **SageMaker Model Registry** and enforce an approval workflow before deployment. Ensure at least one model package per group reaches **Approved** status. Use **IAM policies** to restrict who can approve model packages and integrate with **CI/CD pipelines** to automate registration.",
+ "Url": "https://hub.prowler.com/check/sagemaker_models_registry_in_use"
+ }
+ },
+ "Categories": [
+ "gen-ai",
+ "software-supply-chain"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.py b/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.py
new file mode 100644
index 0000000000..5c7ff31fa5
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_models_registry_in_use/sagemaker_models_registry_in_use.py
@@ -0,0 +1,28 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.sagemaker.sagemaker_client import sagemaker_client
+
+
+class sagemaker_models_registry_in_use(Check):
+ """Ensure that SageMaker Model Registry has at least one approved model package."""
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports indicating whether the SageMaker Model Registry
+ in each region contains at least one approved model package.
+ """
+ findings = []
+ for registry in sagemaker_client.sagemaker_model_registries:
+ report = Check_Report_AWS(metadata=self.metadata(), resource=registry)
+ if not registry.has_groups:
+ report.status = "FAIL"
+ report.status_extended = f"SageMaker Model Registry in region {registry.region} has no Model Package Groups."
+ elif registry.has_approved_packages:
+ report.status = "PASS"
+ report.status_extended = f"SageMaker Model Registry in region {registry.region} has at least one approved model package."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"SageMaker Model Registry in region {registry.region} has Model Package Groups but no approved model packages."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/__init__.py b/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_rdp_internet/__init__.py
rename to prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/__init__.py
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.metadata.json b/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.metadata.json
new file mode 100644
index 0000000000..161abe5d30
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.metadata.json
@@ -0,0 +1,41 @@
+{
+ "Provider": "aws",
+ "CheckID": "sagemaker_notebook_instance_no_secrets",
+ "CheckTitle": "SageMaker notebook instance lifecycle configuration contains no hardcoded secrets",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Sensitive Data Identifications/Passwords",
+ "Effects/Data Exposure"
+ ],
+ "ServiceName": "sagemaker",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "AwsSageMakerNotebookInstance",
+ "ResourceGroup": "ai_ml",
+ "Description": "**SageMaker notebook instance lifecycle configuration scripts** (`OnCreate` and `OnStart`) are analyzed for **embedded secrets**, detecting patterns like API keys, passwords, tokens, and connection strings. Findings reference the lifecycle hook and line numbers where potential secrets appear.",
+ "Risk": "**Hardcoded secrets** in lifecycle configuration scripts can be read by anyone with SageMaker access to the notebook instance, letting attackers reuse the credentials to access databases, APIs, or cloud resources, enabling data exfiltration and unauthorized changes.\n\nRotation is harder, increasing dwell time and blast radius of compromises.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/sagemaker/latest/dg/notebook-lifecycle-config.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws sagemaker update-notebook-instance-lifecycle-config --notebook-instance-lifecycle-config-name <lifecycle-config-name> --on-start Content=<base64-script-without-secrets>",
+ "NativeIaC": "",
+ "Other": "1. Create a secret in AWS Secrets Manager for the hardcoded value.\n2. Update the notebook instance IAM role to allow secretsmanager:GetSecretValue on that secret.\n3. Edit the lifecycle script to fetch the secret at runtime instead of hardcoding it.\n4. Update the notebook instance lifecycle configuration.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Use AWS Secrets Manager or Parameter Store to store secrets and retrieve them at runtime in lifecycle scripts; never hardcode them.",
+ "Url": "https://hub.prowler.com/check/sagemaker_notebook_instance_no_secrets"
+ }
+ },
+ "Categories": [
+ "secrets",
+ "gen-ai"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.py b/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.py
new file mode 100644
index 0000000000..9b975596e4
--- /dev/null
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_notebook_instance_no_secrets/sagemaker_notebook_instance_no_secrets.py
@@ -0,0 +1,131 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
+from prowler.providers.aws.services.sagemaker.sagemaker_client import (
+ sagemaker_client,
+)
+
+
+class sagemaker_notebook_instance_no_secrets(Check):
+ """Check for hardcoded secrets in SageMaker notebook instance lifecycle scripts.
+
+ Scans the OnCreate and OnStart lifecycle configuration scripts of each
+ SageMaker notebook instance for hardcoded secrets such as API keys,
+ passwords, tokens, and connection strings. The scripts are fetched and
+ decoded by the SageMaker service; this check only consumes that data.
+ """
+
+ def execute(self):
+ """Execute the sagemaker_notebook_instance_no_secrets check.
+
+ Returns:
+ list[Check_Report_AWS]: One report per SageMaker notebook
+ instance, with status PASS, FAIL, or MANUAL.
+ """
+ findings = []
+ notebook_instances = sagemaker_client.sagemaker_notebook_instances
+ if not notebook_instances:
+ return findings
+
+ secrets_ignore_patterns = sagemaker_client.audit_config.get(
+ "secrets_ignore_patterns", []
+ )
+ validate = sagemaker_client.audit_config.get("secrets_validate", False)
+
+ # Instances that actually contribute a script to the batch. Only these
+ # (plus instances whose describe/decode failed) may be marked MANUAL on
+ # a batch scan failure; instances with nothing to scan must PASS.
+ scanned_resources = {
+ notebook_instance.arn
+ for notebook_instance in notebook_instances
+ if notebook_instance.lifecycle_scripts
+ }
+
+ def payloads():
+ for notebook_instance in notebook_instances:
+ for fragment, script in notebook_instance.lifecycle_scripts.items():
+ yield (notebook_instance.arn, fragment), script
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(),
+ excluded_secrets=secrets_ignore_patterns,
+ validate=validate,
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ findings_by_instance = {}
+ for (
+ resource_id,
+ fragment,
+ ), fragment_findings in batch_results.items():
+ findings_by_instance.setdefault(resource_id, {})[
+ fragment
+ ] = fragment_findings
+
+ for notebook_instance in notebook_instances:
+ report = Check_Report_AWS(
+ metadata=self.metadata(), resource=notebook_instance
+ )
+
+ # MANUAL when the instance could not be fully scanned: either the
+ # lifecycle config describe/decode failed, or the batch scan failed
+ # for an instance that actually had scripts queued for scanning.
+ batch_failed = (
+ scan_error is not None and notebook_instance.arn in scanned_resources
+ )
+ if notebook_instance.lifecycle_scan_failed or batch_failed:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not fully scan SageMaker notebook instance "
+ f"{notebook_instance.name} lifecycle configuration for "
+ f"secrets; manual review is required."
+ )
+ findings.append(report)
+ continue
+
+ report.status = "PASS"
+ if not notebook_instance.lifecycle_config_name:
+ report.status_extended = (
+ f"SageMaker notebook instance {notebook_instance.name} "
+ f"does not have a lifecycle configuration."
+ )
+ else:
+ report.status_extended = (
+ f"No secrets found in SageMaker notebook instance "
+ f"{notebook_instance.name} lifecycle configuration."
+ )
+
+ fragments_with_secrets = findings_by_instance.get(notebook_instance.arn)
+
+ if fragments_with_secrets:
+ all_secrets = []
+ secrets_findings = []
+
+ for fragment, fragment_findings in fragments_with_secrets.items():
+ all_secrets.extend(fragment_findings)
+ secrets_string = ", ".join(
+ f"{secret['type']} on line {secret['line_number']}"
+ for secret in fragment_findings
+ )
+ secrets_findings.append(f"{fragment}: {secrets_string}")
+
+ final_output_string = "; ".join(secrets_findings)
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Potential {'secrets' if len(secrets_findings) > 1 else 'secret'} "
+ f"found in SageMaker notebook instance "
+ f"{notebook_instance.name} lifecycle configuration -> "
+ f"{final_output_string}."
+ )
+ annotate_verified_secrets(report, all_secrets)
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/sagemaker/sagemaker_service.py b/prowler/providers/aws/services/sagemaker/sagemaker_service.py
index 8577dfe08e..6303ebbbf2 100644
--- a/prowler/providers/aws/services/sagemaker/sagemaker_service.py
+++ b/prowler/providers/aws/services/sagemaker/sagemaker_service.py
@@ -1,3 +1,4 @@
+import base64
from typing import Optional
from botocore.client import ClientError
@@ -15,24 +16,39 @@ class SageMaker(AWSService):
self.sagemaker_notebook_instances = []
self.sagemaker_models = []
self.sagemaker_training_jobs = []
+ self.sagemaker_processing_jobs = []
+ self.processing_jobs_scanned_regions = set()
self.sagemaker_domains = []
self.endpoint_configs = {}
+ self.sagemaker_model_registries = []
+ self.sagemaker_monitoring_schedules = []
# Retrieve resources concurrently
self.__threading_call__(self._list_notebook_instances)
self.__threading_call__(self._list_models)
self.__threading_call__(self._list_training_jobs)
+ self.__threading_call__(self._list_processing_jobs)
self.__threading_call__(self._list_endpoint_configs)
self.__threading_call__(self._list_domains)
+ self.__threading_call__(self._list_model_package_groups)
+ self.__threading_call__(self._list_monitoring_schedules)
# Describe resources concurrently
self.__threading_call__(self._describe_model, self.sagemaker_models)
self.__threading_call__(
self._describe_notebook_instance, self.sagemaker_notebook_instances
)
+ # Runs after _describe_notebook_instance so lifecycle_config_name is set.
+ self.__threading_call__(
+ self._describe_notebook_instance_lifecycle_config,
+ self.sagemaker_notebook_instances,
+ )
self.__threading_call__(
self._describe_training_job, self.sagemaker_training_jobs
)
+ self.__threading_call__(
+ self._describe_processing_job, self.sagemaker_processing_jobs
+ )
self.__threading_call__(
self._describe_endpoint_config, list(self.endpoint_configs.values())
)
@@ -47,6 +63,9 @@ class SageMaker(AWSService):
self.__threading_call__(
self._list_tags_for_resource, self.sagemaker_training_jobs
)
+ self.__threading_call__(
+ self._list_tags_for_resource, self.sagemaker_processing_jobs
+ )
self.__threading_call__(
self._list_tags_for_resource, list(self.endpoint_configs.values())
)
@@ -124,6 +143,66 @@ class SageMaker(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _list_processing_jobs(self, regional_client):
+ """List SageMaker processing jobs in a region.
+
+ Populates ``self.sagemaker_processing_jobs`` with `ProcessingJob`
+ entries and adds ``regional_client.region`` to
+ ``self.processing_jobs_scanned_regions`` once pagination succeeds, so
+ regions where ``ListProcessingJobs`` fails are skipped by checks that
+ consume that set.
+
+ Args:
+ regional_client: Regional SageMaker boto3 client.
+ """
+ logger.info("SageMaker - listing processing jobs...")
+ try:
+ list_processing_jobs_paginator = regional_client.get_paginator(
+ "list_processing_jobs"
+ )
+ for page in list_processing_jobs_paginator.paginate():
+ for processing_job in page["ProcessingJobSummaries"]:
+ if not self.audit_resources or (
+ is_resource_filtered(
+ processing_job["ProcessingJobArn"], self.audit_resources
+ )
+ ):
+ self.sagemaker_processing_jobs.append(
+ ProcessingJob(
+ name=processing_job["ProcessingJobName"],
+ region=regional_client.region,
+ arn=processing_job["ProcessingJobArn"],
+ )
+ )
+ self.processing_jobs_scanned_regions.add(regional_client.region)
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _describe_processing_job(self, processing_job):
+ """Describe a SageMaker processing job and enrich its image metadata.
+
+ Reads ``AppSpecification.ImageUri`` from ``DescribeProcessingJob`` and
+ stores it on ``processing_job.image_uri``. Errors are logged and
+ swallowed so a failure in one job does not abort the scan.
+
+ Args:
+ processing_job: ProcessingJob model to enrich in-place.
+ """
+ logger.info("SageMaker - describing processing job...")
+ try:
+ regional_client = self.regional_clients[processing_job.region]
+ describe_processing_job = regional_client.describe_processing_job(
+ ProcessingJobName=processing_job.name
+ )
+ app_spec = describe_processing_job.get("AppSpecification", {})
+ processing_job.image_uri = app_spec.get("ImageUri")
+ except Exception as error:
+ logger.error(
+ f"{processing_job.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _describe_notebook_instance(self, notebook_instance):
logger.info("SageMaker - describing notebook instances...")
try:
@@ -151,11 +230,61 @@ class SageMaker(AWSService):
notebook_instance.direct_internet_access = True
if "KmsKeyId" in describe_notebook_instance:
notebook_instance.kms_key_id = describe_notebook_instance["KmsKeyId"]
+ if "NotebookInstanceLifecycleConfigName" in describe_notebook_instance:
+ notebook_instance.lifecycle_config_name = describe_notebook_instance[
+ "NotebookInstanceLifecycleConfigName"
+ ]
except Exception as error:
logger.error(
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _describe_notebook_instance_lifecycle_config(self, notebook_instance):
+ """Fetch and decode a notebook instance's lifecycle scripts.
+
+ Reads the ``OnCreate`` and ``OnStart`` scripts from
+ ``DescribeNotebookInstanceLifecycleConfig`` and stores the base64-decoded
+ content on ``notebook_instance.lifecycle_scripts`` keyed by
+ ``"<hook>[<index>]"``. Instances without a lifecycle configuration are
+ skipped. Any describe or decode failure sets
+ ``notebook_instance.lifecycle_scan_failed`` to True so the consuming
+ check can report ``MANUAL`` instead of a false ``PASS``.
+
+ Args:
+ notebook_instance: NotebookInstance model to enrich in-place.
+ """
+ if not notebook_instance.lifecycle_config_name:
+ return
+ logger.info("SageMaker - describing notebook instance lifecycle config...")
+ try:
+ regional_client = self.regional_clients[notebook_instance.region]
+ lifecycle_config = regional_client.describe_notebook_instance_lifecycle_config(
+ NotebookInstanceLifecycleConfigName=notebook_instance.lifecycle_config_name
+ )
+ except Exception as error:
+ notebook_instance.lifecycle_scan_failed = True
+ logger.error(
+ f"{notebook_instance.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return
+
+ scripts = {}
+ for hook_name in ("OnCreate", "OnStart"):
+ for script_index, script in enumerate(lifecycle_config.get(hook_name, [])):
+ content_b64 = script.get("Content")
+ if not content_b64:
+ continue
+ try:
+ scripts[f"{hook_name}[{script_index}]"] = base64.b64decode(
+ content_b64
+ ).decode("utf-8", errors="ignore")
+ except Exception as error:
+ notebook_instance.lifecycle_scan_failed = True
+ logger.error(
+ f"{notebook_instance.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ notebook_instance.lifecycle_scripts = scripts
+
def _describe_model(self, model):
logger.info("SageMaker - describing models...")
try:
@@ -207,6 +336,71 @@ class SageMaker(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _list_model_package_groups(self, regional_client):
+ logger.info("SageMaker - listing model package groups...")
+ registry_arn = self.get_unknown_arn(
+ region=regional_client.region,
+ resource_type="model-registry",
+ )
+ has_groups = False
+ has_approved = False
+ try:
+ paginator = regional_client.get_paginator("list_model_package_groups")
+ for page in paginator.paginate():
+ for group in page["ModelPackageGroupSummaryList"]:
+ has_groups = True
+ if not has_approved:
+ group_name = group["ModelPackageGroupName"]
+ try:
+ pkg_paginator = regional_client.get_paginator(
+ "list_model_packages"
+ )
+ for pkg_page in pkg_paginator.paginate(
+ ModelPackageGroupName=group_name,
+ ModelApprovalStatus="Approved",
+ ):
+ if pkg_page["ModelPackageSummaryList"]:
+ has_approved = True
+ break
+ except ClientError as pkg_error:
+ if pkg_error.response["Error"]["Code"] in (
+ "AccessDeniedException",
+ "UnrecognizedClientException",
+ ):
+ raise
+ logger.error(
+ f"{regional_client.region} -- {pkg_error.__class__.__name__}[{pkg_error.__traceback__.tb_lineno}]: {pkg_error}"
+ )
+ except Exception as pkg_error:
+ logger.error(
+ f"{regional_client.region} -- {pkg_error.__class__.__name__}[{pkg_error.__traceback__.tb_lineno}]: {pkg_error}"
+ )
+ except ClientError as error:
+ if error.response["Error"]["Code"] in (
+ "AccessDeniedException",
+ "UnrecognizedClientException",
+ ):
+ logger.warning(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ self.sagemaker_model_registries.append(
+ ModelRegistry(
+ name="SageMaker Model Registry",
+ arn=registry_arn,
+ region=regional_client.region,
+ has_groups=has_groups,
+ has_approved_packages=has_approved,
+ )
+ )
+
def _list_tags_for_resource(self, resource):
"""
Lists tags for a specific SageMaker resource.
@@ -310,6 +504,46 @@ class SageMaker(AWSService):
f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _list_monitoring_schedules(self, regional_client):
+ logger.info("SageMaker - listing monitoring schedules...")
+ name = "SageMaker Monitoring Schedules"
+ arn = self.get_unknown_arn(
+ region=regional_client.region,
+ resource_type="monitoring-schedule",
+ )
+ has_schedules = False
+ is_scheduled = False
+ try:
+ paginator = regional_client.get_paginator("list_monitoring_schedules")
+ for page in paginator.paginate():
+ for schedule in page["MonitoringScheduleSummaries"]:
+ if not self.audit_resources or (
+ is_resource_filtered(
+ schedule["MonitoringScheduleArn"], self.audit_resources
+ )
+ ):
+ has_schedules = True
+ if schedule["MonitoringScheduleStatus"] == "Scheduled":
+ is_scheduled = True
+ name = schedule["MonitoringScheduleName"]
+ arn = schedule["MonitoringScheduleArn"]
+ break
+ if is_scheduled:
+ break
+ except Exception as error:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ self.sagemaker_monitoring_schedules.append(
+ MonitoringSchedule(
+ name=name,
+ region=regional_client.region,
+ arn=arn,
+ has_schedules=has_schedules,
+ is_scheduled=is_scheduled,
+ )
+ )
+
class NotebookInstance(BaseModel):
name: str
@@ -319,6 +553,13 @@ class NotebookInstance(BaseModel):
subnet_id: str = None
direct_internet_access: bool = None
kms_key_id: str = None
+ lifecycle_config_name: str = None
+ # Decoded lifecycle scripts keyed by "<hook>[<index>]" (e.g. "OnStart[0]"),
+ # populated by _describe_notebook_instance_lifecycle_config.
+ lifecycle_scripts: dict = {}
+ # True if the lifecycle configuration could not be fully described/decoded,
+ # so the secrets check reports MANUAL instead of a false PASS.
+ lifecycle_scan_failed: bool = False
tags: Optional[list] = []
@@ -342,6 +583,25 @@ class TrainingJob(BaseModel):
tags: Optional[list] = []
+class ProcessingJob(BaseModel):
+ """Represents a SageMaker processing job.
+
+ Attributes:
+ name: Processing job name.
+ region: AWS region where the job lives.
+ arn: Processing job ARN.
+ image_uri: Container image URI from `AppSpecification.ImageUri`,
+ populated by `_describe_processing_job`.
+ tags: Resource tags, populated by `_list_tags_for_resource`.
+ """
+
+ name: str
+ region: str
+ arn: str
+ image_uri: Optional[str] = None
+ tags: Optional[list] = []
+
+
class ProductionVariant(BaseModel):
name: str
initial_instance_count: int
@@ -364,3 +624,21 @@ class EndpointConfig(BaseModel):
arn: str
production_variants: list[ProductionVariant] = []
tags: Optional[list] = []
+
+
+class ModelRegistry(BaseModel):
+ """Represents the SageMaker Model Registry state for a specific region."""
+
+ name: str
+ arn: str
+ region: str
+ has_groups: bool = False
+ has_approved_packages: bool = False
+
+
+class MonitoringSchedule(BaseModel):
+ name: str
+ region: str
+ arn: str
+ has_schedules: bool = False
+ is_scheduled: bool = False
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/__init__.py b/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_securitygroup_restrict_ssh_internet/__init__.py
rename to prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/__init__.py
diff --git a/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.metadata.json b/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.metadata.json
new file mode 100644
index 0000000000..99748671ae
--- /dev/null
+++ b/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.metadata.json
@@ -0,0 +1,44 @@
+{
+ "Provider": "aws",
+ "CheckID": "securityhub_delegated_admin_enabled_all_regions",
+ "CheckTitle": "Security Hub has delegated admin configured and is enabled in all regions with organization auto-enable",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices"
+ ],
+ "ServiceName": "securityhub",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "AwsSecurityHubHub",
+ "ResourceGroup": "security",
+ "Description": "**AWS Security Hub** has a delegated administrator configured at the organization level, hubs are active in all opted-in regions, and organization auto-enable is active so that new member accounts are automatically enrolled.",
+ "Risk": "Without org-wide **AWS Security Hub** configuration, findings can be aggregated inconsistently, delegated admin may be missing in some regions, and new accounts will not be auto-enrolled. This fragments **security posture visibility**, delays **incident response**, and lets misconfigurations and compliance drift go undetected across the organization.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/securityhub/latest/userguide/designate-orgs-admin-account.html",
+ "https://docs.aws.amazon.com/securityhub/latest/userguide/accounts-orgs-auto-enable.html",
+ "https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-regions.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws securityhub enable-organization-admin-account --admin-account-id <ADMIN_ACCOUNT_ID> && aws securityhub update-organization-configuration --auto-enable --auto-enable-standards DEFAULT",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the AWS Organizations management account\n2. Open the AWS Organizations console\n3. Navigate to Services > AWS Security Hub\n4. Click Register delegated administrator and enter the security account ID\n5. Switch to the delegated admin account\n6. In Security Hub console, go to Settings > Accounts\n7. Enable auto-enable for new organization accounts\n8. Repeat hub enablement for all opted-in regions",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure a **delegated administrator** for AWS Security Hub via AWS Organizations. Enable Security Hub in **all opted-in regions** and turn on **auto-enable** so new member accounts are automatically enrolled. This ensures uniform security posture monitoring across the entire organization.",
+ "Url": "https://hub.prowler.com/check/securityhub_delegated_admin_enabled_all_regions"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "securityhub_enabled",
+ "guardduty_delegated_admin_enabled_all_regions"
+ ],
+ "Notes": "This check requires execution from the organization management account or delegated administrator account to access organization-level APIs."
+}
diff --git a/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.py b/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.py
new file mode 100644
index 0000000000..4828752183
--- /dev/null
+++ b/prowler/providers/aws/services/securityhub/securityhub_delegated_admin_enabled_all_regions/securityhub_delegated_admin_enabled_all_regions.py
@@ -0,0 +1,84 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.securityhub.securityhub_client import (
+ securityhub_client,
+)
+
+
+class securityhub_delegated_admin_enabled_all_regions(Check):
+ """Ensure Security Hub has a delegated admin and is enabled in all regions.
+
+ This check verifies that:
+ 1. A delegated administrator account is configured for Security Hub
+ 2. Security Hub is active (ACTIVE status) in each region
+ 3. Organization auto-enable is configured for new member accounts
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports containing the result of the check for each region.
+ """
+ findings = []
+
+ # Build a set of regions that have an organization admin account configured
+ regions_with_admin = {
+ admin.region
+ for admin in securityhub_client.organization_admin_accounts
+ if admin.admin_status == "ENABLED"
+ }
+ admin_lookup_failed = securityhub_client.organization_admin_lookup_failed
+
+ for securityhub in securityhub_client.securityhubs:
+ report = Check_Report_AWS(metadata=self.metadata(), resource=securityhub)
+
+ # Check if this region has a delegated admin
+ has_delegated_admin = securityhub.region in regions_with_admin
+
+ # Check if hub is active
+ hub_active = securityhub.status == "ACTIVE"
+
+ # Check if auto-enable is configured for organization members
+ auto_enable_on = securityhub.organization_auto_enable
+
+ # Determine overall status
+ issues = []
+ if admin_lookup_failed:
+ issues.append("delegated administrator status could not be determined")
+ elif not has_delegated_admin:
+ issues.append("no delegated administrator configured")
+ if not hub_active:
+ issues.append("Security Hub not enabled")
+ if (
+ hub_active
+ and securityhub.organization_config_available
+ and not auto_enable_on
+ ):
+ # Only report auto-enable issue if hub is active and org config data
+ # is available (i.e., we could actually read AutoEnable from the API).
+ issues.append("organization auto-enable not configured")
+
+ if issues:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Security Hub in region {securityhub.region} has issues: "
+ f"{', '.join(issues)}."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Security Hub in region {securityhub.region} has delegated "
+ f"admin configured with hub active and organization auto-enable "
+ f"enabled."
+ )
+
+ # Support muting non-default regions if configured
+ if report.status == "FAIL" and (
+ securityhub_client.audit_config.get("mute_non_default_regions", False)
+ and securityhub.region != securityhub_client.region
+ ):
+ report.muted = True
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/securityhub/securityhub_service.py b/prowler/providers/aws/services/securityhub/securityhub_service.py
index 0799c6e048..5e2d445742 100644
--- a/prowler/providers/aws/services/securityhub/securityhub_service.py
+++ b/prowler/providers/aws/services/securityhub/securityhub_service.py
@@ -13,8 +13,14 @@ class SecurityHub(AWSService):
# Call AWSService's __init__
super().__init__(__class__.__name__, provider)
self.securityhubs = []
+ self.organization_admin_accounts = []
+ self.organization_admin_lookup_failed: bool = False
self.__threading_call__(self._describe_hub)
self.__threading_call__(self._list_tags, self.securityhubs)
+ self.__threading_call__(self._list_organization_admin_accounts)
+ self.__threading_call__(
+ self._describe_organization_configuration, self.securityhubs
+ )
def _describe_hub(self, regional_client):
logger.info("SecurityHub - Describing Hub...")
@@ -104,6 +110,95 @@ class SecurityHub(AWSService):
f"{resource.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _list_organization_admin_accounts(self, regional_client):
+ """List Security Hub delegated administrator accounts for the organization.
+
+ This API is only available to the organization management account or
+ a delegated administrator account.
+ """
+ logger.info("SecurityHub - listing organization admin accounts...")
+ try:
+ paginator = regional_client.get_paginator(
+ "list_organization_admin_accounts"
+ )
+ for page in paginator.paginate():
+ for admin in page.get("AdminAccounts", []):
+ admin_account = OrganizationAdminAccount(
+ admin_account_id=admin.get("AdminAccountId"),
+ admin_status=admin.get("AdminStatus"),
+ region=regional_client.region,
+ )
+ # Avoid duplicates across regions for the same admin account
+ if not any(
+ existing.admin_account_id == admin_account.admin_account_id
+ and existing.region == admin_account.region
+ for existing in self.organization_admin_accounts
+ ):
+ self.organization_admin_accounts.append(admin_account)
+ except ClientError as error:
+ self.organization_admin_lookup_failed = True
+ if error.response["Error"]["Code"] in (
+ "AccessDeniedException",
+ "InvalidAccessException",
+ "BadRequestException",
+ ):
+ logger.warning(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ else:
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ self.organization_admin_lookup_failed = True
+ logger.error(
+ f"{regional_client.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _describe_organization_configuration(self, securityhub):
+ """Describe the organization configuration for a Security Hub instance.
+
+ This provides information about auto-enable settings for the organization.
+ Only invoked for hubs in ACTIVE status.
+ """
+ logger.info("SecurityHub - describing organization configuration...")
+ try:
+ if securityhub.status != "ACTIVE":
+ return
+ regional_client = self.regional_clients[securityhub.region]
+ org_config = regional_client.describe_organization_configuration()
+ securityhub.organization_auto_enable = org_config.get("AutoEnable", False)
+ securityhub.auto_enable_standards = org_config.get(
+ "AutoEnableStandards", "NONE"
+ )
+ securityhub.organization_config_available = True
+ except ClientError as error:
+ if error.response["Error"]["Code"] in (
+ "AccessDeniedException",
+ "InvalidAccessException",
+ "BadRequestException",
+ ):
+ # Expected when not running from management or delegated admin account
+ logger.warning(
+ f"{securityhub.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ else:
+ logger.error(
+ f"{securityhub.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{securityhub.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class OrganizationAdminAccount(BaseModel):
+ """Represents a Security Hub delegated administrator account."""
+
+ admin_account_id: str
+ admin_status: str # ENABLED or DISABLE_IN_PROGRESS
+ region: str
+
class SecurityHubHub(BaseModel):
arn: str
@@ -112,4 +207,8 @@ class SecurityHubHub(BaseModel):
standards: str
integrations: str
region: str
- tags: Optional[list]
+ tags: Optional[list] = []
+ # Organization configuration fields
+ organization_auto_enable: bool = False
+ auto_enable_standards: str = "NONE"
+ organization_config_available: bool = False
diff --git a/tests/providers/alibabacloud/services/ecs/ecs_unattached_disk_encrypted/__init__.py b/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ecs/ecs_unattached_disk_encrypted/__init__.py
rename to prowler/providers/aws/services/ses/ses_identity_dkim_enabled/__init__.py
diff --git a/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.metadata.json b/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.metadata.json
new file mode 100644
index 0000000000..83353b0caa
--- /dev/null
+++ b/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "aws",
+ "CheckID": "ses_identity_dkim_enabled",
+ "CheckTitle": "SES identity has DKIM signing enabled",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "ses",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Other",
+ "ResourceGroup": "messaging",
+ "Description": "**Amazon SES identities** are evaluated for **DKIM (DomainKeys Identified Mail)** signing enabled and verified. DKIM adds a cryptographic signature to outgoing emails, allowing recipients to verify that the email was sent by the domain owner and was not altered in transit.",
+ "Risk": "Without DKIM signing, emails sent from SES identities are vulnerable to **spoofing and tampering**. Attackers can forge emails that appear to come from your domain, leading to phishing attacks, brand impersonation, and loss of email deliverability. Email providers are more likely to reject or mark unsigned emails as spam, impacting business communication and reputation.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim.html",
+ "https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws sesv2 put-email-identity-dkim-signing-attributes --email-identity <IDENTITY-NAME> --signing-attributes-origin AWS_SES",
+ "NativeIaC": "",
+ "Other": "1. In the AWS Console, go to Simple Email Service (SES)\n2. Open Verified identities and select the affected identity\n3. Click the Authentication tab\n4. Under DKIM, click Edit\n5. Enable DKIM signatures and select 'Provide DKIM authentication token (Easy DKIM)'\n6. Save changes and add the provided CNAME records to your DNS provider",
+ "Terraform": "```hcl\nresource \"aws_ses_domain_dkim\" \"<example_resource_name>\" {\n domain = \"<example_domain_name>\"\n}\n\n# Add the CNAME records to Route53 (or your DNS provider)\nresource \"aws_route53_record\" \"<example_resource_name>_dkim\" {\n count = 3\n zone_id = \"<route53_zone_id>\"\n name = \"${aws_ses_domain_dkim.<example_resource_name>.dkim_tokens[count.index]}._domainkey.<example_domain_name>\"\n type = \"CNAME\"\n ttl = 600\n records = [\"${aws_ses_domain_dkim.<example_resource_name>.dkim_tokens[count.index]}.dkim.amazonses.com\"]\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **DKIM signing** for all SES identities and ensure the DKIM status is **SUCCESS**. Add the required CNAME records to your DNS provider to complete verification. Combine DKIM with **SPF** and **DMARC** for comprehensive email authentication following **defense in depth** principles. Monitor DKIM status regularly and rotate DKIM keys as recommended by AWS.",
+ "Url": "https://hub.prowler.com/check/ses_identity_dkim_enabled"
+ }
+ },
+ "Categories": [
+ "identity-access",
+ "email-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.py b/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.py
new file mode 100644
index 0000000000..2654010e28
--- /dev/null
+++ b/prowler/providers/aws/services/ses/ses_identity_dkim_enabled/ses_identity_dkim_enabled.py
@@ -0,0 +1,33 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.ses.ses_client import ses_client
+
+
+class ses_identity_dkim_enabled(Check):
+ def execute(self):
+ findings = []
+ for identity in ses_client.email_identities.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=identity)
+ if identity.dkim_status == "SUCCESS" and identity.dkim_signing_enabled:
+ report.status = "PASS"
+ report.status_extended = f"SES identity {identity.name} has DKIM signing enabled and verified."
+ elif identity.dkim_status in (
+ "PENDING",
+ "NOT_STARTED",
+ "TEMPORARY_FAILURE",
+ ):
+ report.status = "FAIL"
+ report.status_extended = f"SES identity {identity.name} has DKIM signing not verified (status: {identity.dkim_status})."
+ elif identity.dkim_status == "FAILED":
+ report.status = "FAIL"
+ report.status_extended = f"SES identity {identity.name} has DKIM signing failed verification."
+ elif (
+ identity.dkim_status == "SUCCESS" and not identity.dkim_signing_enabled
+ ):
+ report.status = "FAIL"
+ report.status_extended = f"SES identity {identity.name} has DKIM verified but signing is disabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"SES identity {identity.name} does not have DKIM signing configured."
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/ses/ses_service.py b/prowler/providers/aws/services/ses/ses_service.py
index ff19f829e6..7d0feb8f54 100644
--- a/prowler/providers/aws/services/ses/ses_service.py
+++ b/prowler/providers/aws/services/ses/ses_service.py
@@ -46,9 +46,15 @@ class SES(AWSService):
identity_attributes = regional_client.get_email_identity(
EmailIdentity=identity.name
)
- for _, content in identity_attributes["Policies"].items():
+ for _, content in identity_attributes.get("Policies", {}).items():
identity.policy = loads(content)
- identity.tags = identity_attributes["Tags"]
+ identity.tags = identity_attributes.get("Tags", [])
+ dkim_attrs = identity_attributes.get("DkimAttributes", {}) or {}
+ identity.dkim_status = dkim_attrs.get("Status")
+ identity.dkim_signing_enabled = dkim_attrs.get("SigningEnabled", False)
+ identity.dkim_signing_attributes_origin = dkim_attrs.get(
+ "SigningAttributesOrigin"
+ )
except Exception as error:
logger.error(
@@ -67,3 +73,6 @@ class Identity(BaseModel):
type: Optional[str]
policy: Optional[dict] = None
tags: Optional[list] = []
+ dkim_status: Optional[str] = None
+ dkim_signing_attributes_origin: Optional[str] = None
+ dkim_signing_enabled: Optional[bool] = False
diff --git a/prowler/providers/aws/services/ssm/ssm_document_secrets/ssm_document_secrets.py b/prowler/providers/aws/services/ssm/ssm_document_secrets/ssm_document_secrets.py
index 0ec8502bab..1755c6f736 100644
--- a/prowler/providers/aws/services/ssm/ssm_document_secrets/ssm_document_secrets.py
+++ b/prowler/providers/aws/services/ssm/ssm_document_secrets/ssm_document_secrets.py
@@ -1,7 +1,11 @@
import json
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.ssm.ssm_client import ssm_client
@@ -11,7 +15,26 @@ class ssm_document_secrets(Check):
secrets_ignore_patterns = ssm_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for document in ssm_client.documents.values():
+ validate = ssm_client.audit_config.get("secrets_validate", False)
+ documents = list(ssm_client.documents.values())
+
+ # Collect one payload per document (its content) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per document.
+ def payloads():
+ for index, document in enumerate(documents):
+ if document.content:
+ yield index, json.dumps(document.content, indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, document in enumerate(documents):
report = Check_Report_AWS(metadata=self.metadata(), resource=document)
report.status = "PASS"
report.status_extended = (
@@ -19,13 +42,15 @@ class ssm_document_secrets(Check):
)
if document.content:
- detect_secrets_output = detect_secrets_scan(
- data=json.dumps(document.content, indent=2),
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=ssm_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan SSM Document {document.name} for secrets: "
+ f"{scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
secrets_string = ", ".join(
[
@@ -35,6 +60,7 @@ class ssm_document_secrets(Check):
)
report.status = "FAIL"
report.status_extended = f"Potential secret found in SSM Document {document.name} -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
findings.append(report)
diff --git a/tests/providers/alibabacloud/services/oss/__init__.py b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/oss/__init__.py
rename to prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/__init__.py
diff --git a/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.metadata.json b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.metadata.json
new file mode 100644
index 0000000000..14b65b886b
--- /dev/null
+++ b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "aws",
+ "CheckID": "stepfunctions_statemachine_encrypted_with_cmk",
+ "CheckTitle": "Step Functions state machine is encrypted at rest with a customer-managed KMS key",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/NIST 800-53 Controls (USA)"
+ ],
+ "ServiceName": "stepfunctions",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "AwsStepFunctionStateMachine",
+ "ResourceGroup": "serverless",
+ "Description": "**AWS Step Functions state machines** store execution history and input/output data passed between workflow states. This check verifies that each state machine uses a **customer-managed KMS key** (`CUSTOMER_MANAGED_KMS_KEY`) for encryption at rest rather than the default AWS-owned key.",
+ "Risk": "Without a customer-managed KMS key, execution history containing **sensitive input/output data** is protected only by an AWS-owned key you cannot control, rotate, or revoke. This limits **auditability** via CloudTrail, prevents independent access revocation, and weakens **confidentiality** for regulated workloads.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/step-functions/latest/dg/encryption-at-rest.html",
+ "https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws stepfunctions update-state-machine --state-machine-arn <state-machine-arn> --encryption-configuration '{\"kmsKeyId\": \"<kms-key-id>\", \"type\": \"CUSTOMER_MANAGED_KMS_KEY\", \"kmsDataKeyReusePeriodSeconds\": 300}'",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::StepFunctions::StateMachine\n Properties:\n RoleArn: arn:aws:iam::<account-id>:role/<example_role_name>\n DefinitionString: |\n {\"StartAt\":\"Pass\",\"States\":{\"Pass\":{\"Type\":\"Pass\",\"End\":true}}}\n EncryptionConfiguration:\n KmsKeyId: arn:aws:kms:<region>:<account-id>:key/<key-id> # Critical: customer-managed KMS key\n Type: CUSTOMER_MANAGED_KMS_KEY # Critical: must be CUSTOMER_MANAGED_KMS_KEY\n KmsDataKeyReusePeriodSeconds: 300\n```",
+ "Other": "1. Open AWS Console > Step Functions > State machines\n2. Select the state machine and click Edit\n3. Under Encryption, select Customer managed key\n4. Choose an existing KMS key or create a new one\n5. Save changes",
+ "Terraform": "```hcl\nresource \"aws_sfn_state_machine\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n role_arn = \"arn:aws:iam::<account-id>:role/<example_role_name>\"\n definition = jsonencode({ StartAt = \"Pass\", States = { Pass = { Type = \"Pass\", End = true } } })\n\n encryption_configuration {\n kms_key_id = \"arn:aws:kms:<region>:<account-id>:key/<key-id>\" # Critical: customer-managed KMS key\n type = \"CUSTOMER_MANAGED_KMS_KEY\" # Critical: must be CUSTOMER_MANAGED_KMS_KEY\n kms_data_key_reuse_period_seconds = 300\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure each Step Functions state machine to use a **customer-managed KMS key** for encryption at rest. Assign a least-privilege key policy, enable **automatic key rotation**, and grant the execution role `kms:GenerateDataKey` and `kms:Decrypt`. Monitor key usage via CloudTrail.",
+ "Url": "https://hub.prowler.com/check/stepfunctions_statemachine_encrypted_with_cmk"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "stepfunctions_statemachine_logging_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.py b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.py
new file mode 100644
index 0000000000..b14de0b482
--- /dev/null
+++ b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_encrypted_with_cmk/stepfunctions_statemachine_encrypted_with_cmk.py
@@ -0,0 +1,50 @@
+from typing import List
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.stepfunctions.stepfunctions_client import (
+ stepfunctions_client,
+)
+from prowler.providers.aws.services.stepfunctions.stepfunctions_service import (
+ EncryptionType,
+)
+
+
+class stepfunctions_statemachine_encrypted_with_cmk(Check):
+ """Ensure Step Functions state machines are encrypted at rest with a customer-managed KMS key.
+
+ This check evaluates whether each AWS Step Functions state machine uses a
+ customer-managed KMS key (CUSTOMER_MANAGED_KMS_KEY) for encryption at rest rather
+ than the default AWS-owned key (AWS_OWNED_KEY).
+
+ - PASS: The state machine encryption_configuration type is CUSTOMER_MANAGED_KMS_KEY.
+ - FAIL: The state machine has no encryption_configuration or its type is AWS_OWNED_KEY.
+ """
+
+ def execute(self) -> List[Check_Report_AWS]:
+ """Execute the Step Functions state machine encryption at rest check.
+
+ Iterates over all Step Functions state machines and generates a report
+ indicating whether each state machine uses a customer-managed KMS key
+ for encryption at rest.
+
+ Returns:
+ List[Check_Report_AWS]: A list of report objects with the results of the check.
+ """
+ findings = []
+ for state_machine in stepfunctions_client.state_machines.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=state_machine)
+
+ if (
+ state_machine.encryption_configuration
+ and state_machine.encryption_configuration.type
+ == EncryptionType.CUSTOMER_MANAGED_KMS_KEY
+ ):
+ report.status = "PASS"
+ report.status_extended = f"Step Functions state machine {state_machine.name} is encrypted at rest with a customer-managed KMS key."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Step Functions state machine {state_machine.name} is not encrypted at rest with a customer-managed KMS key."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/stepfunctions_statemachine_no_secrets_in_definition.py b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/stepfunctions_statemachine_no_secrets_in_definition.py
index db04710029..12934528e9 100644
--- a/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/stepfunctions_statemachine_no_secrets_in_definition.py
+++ b/prowler/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/stepfunctions_statemachine_no_secrets_in_definition.py
@@ -1,5 +1,9 @@
from prowler.lib.check.models import Check, Check_Report_AWS
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.aws.services.stepfunctions.stepfunctions_client import (
stepfunctions_client,
)
@@ -13,20 +17,41 @@ class stepfunctions_statemachine_no_secrets_in_definition(Check):
secrets_ignore_patterns = stepfunctions_client.audit_config.get(
"secrets_ignore_patterns", []
)
- for state_machine in stepfunctions_client.state_machines.values():
+ validate = stepfunctions_client.audit_config.get("secrets_validate", False)
+ state_machines = list(stepfunctions_client.state_machines.values())
+
+ # Collect one payload per state machine (its definition) and scan them
+ # all in batched Kingfisher invocations instead of one subprocess each.
+ def payloads():
+ for index, state_machine in enumerate(state_machines):
+ if state_machine.definition:
+ yield index, state_machine.definition
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, state_machine in enumerate(state_machines):
report = Check_Report_AWS(metadata=self.metadata(), resource=state_machine)
report.status = "PASS"
report.status_extended = f"No secrets found in Step Functions state machine {state_machine.name} definition."
if state_machine.definition:
- detect_secrets_output = detect_secrets_scan(
- data=state_machine.definition,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=stepfunctions_client.audit_config.get(
- "detect_secrets_plugins",
- ),
- )
-
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan Step Functions state machine "
+ f"{state_machine.name} definition for secrets: {scan_error}; "
+ "manual review is required."
+ )
+ findings.append(report)
+ continue
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
secrets_string = ", ".join(
[
@@ -40,6 +65,7 @@ class stepfunctions_statemachine_no_secrets_in_definition(Check):
f"found in Step Functions state machine {state_machine.name} definition "
f"-> {secrets_string}."
)
+ annotate_verified_secrets(report, detect_secrets_output)
findings.append(report)
return findings
diff --git a/tests/providers/alibabacloud/services/oss/oss_bucket_logging_enabled/__init__.py b/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/oss/oss_bucket_logging_enabled/__init__.py
rename to prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/__init__.py
diff --git a/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.metadata.json b/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.metadata.json
new file mode 100644
index 0000000000..773c85b7ab
--- /dev/null
+++ b/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "aws",
+ "CheckID": "transfer_server_pqc_ssh_kex_enabled",
+ "CheckTitle": "AWS Transfer Family server uses a post-quantum hybrid SSH key exchange security policy",
+ "CheckType": [
+ "Software and Configuration Checks/AWS Security Best Practices"
+ ],
+ "ServiceName": "transfer",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "AwsTransferServer",
+ "ResourceGroup": "network",
+ "Description": "**AWS Transfer Family servers** (SFTP, FTPS, AS2) are assessed for use of an approved **post-quantum (PQ) hybrid SSH key exchange security policy**. Servers whose `SecurityPolicyName` is not in the configured allowlist of PQ-ready Transfer Family security policies leave file-transfer sessions exposed to **harvest-now, decrypt-later** attacks.",
+ "Risk": "Without a PQ-ready security policy, SSH/SFTP traffic captured today can be stored and decrypted in the future once a **cryptographically relevant quantum computer** is available. This threatens long-term **confidentiality** of transferred files, credentials, and metadata.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/transfer/latest/userguide/post-quantum-security-policies.html",
+ "https://docs.aws.amazon.com/transfer/latest/userguide/security-policies.html",
+ "https://aws.amazon.com/security/post-quantum-cryptography/",
+ "https://csrc.nist.gov/projects/post-quantum-cryptography"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws transfer update-server --server-id <server_id> --security-policy-name TransferSecurityPolicy-2025-03",
+ "NativeIaC": "```yaml\nResources:\n <example_resource_name>:\n Type: AWS::Transfer::Server\n Properties:\n Protocols:\n - SFTP\n SecurityPolicyName: TransferSecurityPolicy-2025-03 # FIX: post-quantum hybrid SSH KEX policy\n```",
+ "Other": "1. In the AWS Console, go to AWS Transfer Family > Servers\n2. Select the server and choose Edit on the Additional details panel\n3. Set Cryptographic algorithm options (Security policy) to TransferSecurityPolicy-2025-03 (or another approved PQ policy)\n4. Save the changes",
+ "Terraform": "```hcl\nresource \"aws_transfer_server\" \"<example_resource_name>\" {\n protocols = [\"SFTP\"]\n security_policy_name = \"TransferSecurityPolicy-2025-03\" # FIX: post-quantum hybrid SSH KEX policy\n endpoint_type = \"PUBLIC\"\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Migrate AWS Transfer Family servers to a **post-quantum security policy** (e.g., `TransferSecurityPolicy-2025-03`, `TransferSecurityPolicy-FIPS-2025-03`, `TransferSecurityPolicy-AS2Restricted-2025-07`) that adds ML-KEM hybrid SSH key exchange. Avoid deprecated `*-PQ-SSH-Experimental-2023-04` policies. Review allowed policies regularly as AWS publishes new PQ-ready options.",
+ "Url": "https://hub.prowler.com/check/transfer_server_pqc_ssh_kex_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "transfer_server_in_transit_encryption_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.py b/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.py
new file mode 100644
index 0000000000..a7d70df2df
--- /dev/null
+++ b/prowler/providers/aws/services/transfer/transfer_server_pqc_ssh_kex_enabled/transfer_server_pqc_ssh_kex_enabled.py
@@ -0,0 +1,50 @@
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.transfer.transfer_client import transfer_client
+
+PQC_TRANSFER_POLICIES_DEFAULT = [
+ "TransferSecurityPolicy-2025-03",
+ "TransferSecurityPolicy-FIPS-2025-03",
+ "TransferSecurityPolicy-AS2Restricted-2025-07",
+]
+
+
+class transfer_server_pqc_ssh_kex_enabled(Check):
+ """Verify that every AWS Transfer Family server uses a post-quantum security policy.
+
+ A Transfer Family server PASSES when its ``SecurityPolicyName`` is in the
+ configured allowlist of policies that enable hybrid ML-KEM SSH key exchange.
+ """
+
+ def execute(self) -> list[Check_Report_AWS]:
+ """Check whether Transfer Family servers use approved PQ SSH KEX policies.
+
+ Iterates through discovered AWS Transfer Family servers and compares each
+ server's ``SecurityPolicyName`` with the configured allowlist of
+ post-quantum hybrid SSH key exchange security policies.
+
+ Returns:
+ list[Check_Report_AWS]: A list of reports for each Transfer Family
+ server, including the evaluated security policy context.
+ """
+ findings = []
+ pqc_policies = transfer_client.audit_config.get(
+ "transfer_pqc_ssh_allowed_policies", PQC_TRANSFER_POLICIES_DEFAULT
+ )
+ for server in transfer_client.servers.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=server)
+ policy = server.security_policy_name or "<none>"
+ if server.security_policy_name in pqc_policies:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Transfer Server {server.id} uses post-quantum security policy "
+ f"{policy}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Transfer Server {server.id} uses security policy {policy}, "
+ "which does not enable post-quantum hybrid SSH key exchange."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/transfer/transfer_service.py b/prowler/providers/aws/services/transfer/transfer_service.py
index f86e195a31..968b0c9e60 100644
--- a/prowler/providers/aws/services/transfer/transfer_service.py
+++ b/prowler/providers/aws/services/transfer/transfer_service.py
@@ -46,6 +46,9 @@ class Transfer(AWSService):
)
for protocol in server_description.get("Protocols", []):
server.protocols.append(Protocol(protocol))
+ server.security_policy_name = server_description.get(
+ "SecurityPolicyName", ""
+ )
server.tags = server_description.get("Tags", [])
except Exception as error:
logger.error(
@@ -65,4 +68,5 @@ class Server(BaseModel):
id: str
region: str
protocols: List[Protocol] = Field(default_factory=list)
+ security_policy_name: str = ""
tags: List[Dict[str, str]] = Field(default_factory=list)
diff --git a/tests/providers/alibabacloud/services/oss/oss_bucket_not_publicly_accessible/__init__.py b/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/oss/oss_bucket_not_publicly_accessible/__init__.py
rename to prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/__init__.py
diff --git a/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.metadata.json b/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.metadata.json
new file mode 100644
index 0000000000..b213398059
--- /dev/null
+++ b/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.metadata.json
@@ -0,0 +1,44 @@
+{
+ "Provider": "aws",
+ "CheckID": "waf_regional_webacl_logging_enabled",
+ "CheckTitle": "AWS WAF Classic Regional Web ACL has logging enabled",
+ "CheckType": [
+ "Software and Configuration Checks/Industry and Regulatory Standards/AWS Foundational Security Best Practices",
+ "Software and Configuration Checks/Industry and Regulatory Standards/NIST 800-53 Controls (USA)",
+ "Software and Configuration Checks/Industry and Regulatory Standards/PCI-DSS"
+ ],
+ "ServiceName": "waf",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "AwsWafRegionalWebAcl",
+ "ResourceGroup": "security",
+ "Description": "**AWS WAF Classic Regional Web ACLs** are evaluated for **logging** enabled to capture evaluated web requests and rule actions. Regional Web ACLs protect Application Load Balancers and API Gateway stages.",
+ "Risk": "Without **WAF logging**, you lose **visibility** into attacks (SQLi/XSS probes, bots, brute-force) and into allow/block decisions for ALB and API Gateway traffic. This limits detection, forensics, and incident response, weakening **confidentiality**, **integrity**, and **availability**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.aws.amazon.com/waf/latest/developerguide/classic-logging.html",
+ "https://docs.aws.amazon.com/securityhub/latest/userguide/waf-controls.html",
+ "https://docs.aws.amazon.com/cli/latest/reference/waf-regional/put-logging-configuration.html"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "aws waf-regional put-logging-configuration --logging-configuration ResourceArn=<web_acl_arn>,LogDestinationConfigs=<kinesis_firehose_delivery_stream_arn> --region <region>",
+ "NativeIaC": "",
+ "Other": "1. Create an Amazon Kinesis Data Firehose delivery stream with a name starting with \"aws-waf-logs-\" in the same region as your Web ACL\n2. Open the AWS WAF console and switch to AWS WAF Classic\n3. Select Filter: Regional (your region) and go to Web ACLs\n4. Open the target Web ACL and go to the Logging tab\n5. Click Enable logging and select the Firehose delivery stream created in step 1\n6. Click Enable/Save",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **logging** on all Regional Web ACLs and send records to a centralized logging platform. Apply **least privilege** to log destinations, redact sensitive fields, and monitor for anomalies. Integrate logs with incident response for **defense in depth** and faster containment.",
+ "Url": "https://hub.prowler.com/check/waf_regional_webacl_logging_enabled"
+ }
+ },
+ "Categories": [
+ "logging"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "waf_global_webacl_logging_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.py b/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.py
new file mode 100644
index 0000000000..8d832d6c1e
--- /dev/null
+++ b/prowler/providers/aws/services/waf/waf_regional_webacl_logging_enabled/waf_regional_webacl_logging_enabled.py
@@ -0,0 +1,43 @@
+from typing import List
+
+from prowler.lib.check.models import Check, Check_Report_AWS
+from prowler.providers.aws.services.waf.wafregional_client import wafregional_client
+
+
+class waf_regional_webacl_logging_enabled(Check):
+ """Ensure AWS WAF Classic Regional Web ACLs have logging enabled.
+
+ This check evaluates whether each AWS WAF Classic Regional Web ACL has logging
+ enabled by verifying the presence of at least one log destination configured
+ in its logging configuration.
+
+ - PASS: The Web ACL has at least one log destination configured.
+ - FAIL: The Web ACL has no log destinations configured (logging is disabled).
+ """
+
+ def execute(self) -> List[Check_Report_AWS]:
+ """Execute the WAF Regional Web ACL logging enabled check.
+
+ Iterates over all WAF Classic Regional Web ACLs and generates a report
+ indicating whether each Web ACL has logging enabled.
+
+ Returns:
+ List[Check_Report_AWS]: A list of report objects with the results of the check.
+ """
+ findings = []
+ for acl in wafregional_client.web_acls.values():
+ report = Check_Report_AWS(metadata=self.metadata(), resource=acl)
+ report.status = "FAIL"
+ report.status_extended = (
+ f"AWS WAF Regional Web ACL {acl.name} does not have logging enabled."
+ )
+
+ if acl.logging_enabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"AWS WAF Regional Web ACL {acl.name} does have logging enabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/aws/services/waf/waf_service.py b/prowler/providers/aws/services/waf/waf_service.py
index 25476e6858..602b7116f6 100644
--- a/prowler/providers/aws/services/waf/waf_service.py
+++ b/prowler/providers/aws/services/waf/waf_service.py
@@ -168,6 +168,7 @@ class WAFRegional(AWSService):
)
self.__threading_call__(self._list_web_acls)
self.__threading_call__(self._get_web_acl, self.web_acls.values())
+ self.__threading_call__(self._get_logging_configuration, self.web_acls.values())
self.__threading_call__(self._list_resources_for_web_acl)
def _list_rules(self, regional_client):
@@ -277,6 +278,34 @@ class WAFRegional(AWSService):
f"{acl.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_logging_configuration(self, acl):
+ """Fetch and store the logging configuration for a Regional Web ACL.
+
+ Calls the WAF Regional GetLoggingConfiguration API for the given ACL and
+ sets acl.logging_enabled to True if at least one log destination is configured,
+ False otherwise.
+
+ Args:
+ acl (WebAcl): The Regional Web ACL instance to update.
+ """
+ logger.info(
+ f"WAFRegional - Getting Regional Web ACL {acl.name} logging configuration..."
+ )
+ try:
+ get_logging_configuration = self.regional_clients[
+ acl.region
+ ].get_logging_configuration(ResourceArn=acl.arn)
+ acl.logging_enabled = bool(
+ get_logging_configuration.get("LoggingConfiguration", {}).get(
+ "LogDestinationConfigs", []
+ )
+ )
+
+ except Exception as error:
+ logger.error(
+ f"{acl.region} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _list_resources_for_web_acl(self, regional_client):
logger.info("WAFRegional - Describing resources...")
try:
diff --git a/prowler/providers/azure/azure_provider.py b/prowler/providers/azure/azure_provider.py
index ce28d60bda..bffc72396b 100644
--- a/prowler/providers/azure/azure_provider.py
+++ b/prowler/providers/azure/azure_provider.py
@@ -16,6 +16,7 @@ from azure.identity import (
DefaultAzureCredential,
InteractiveBrowserCredential,
)
+from azure.mgmt.resource import ResourceManagementClient
from azure.mgmt.subscription import SubscriptionClient
from colorama import Fore, Style
from msgraph import GraphServiceClient
@@ -97,12 +98,14 @@ class AzureProvider(Provider):
"""
_type: str = "azure"
+ sdk_only: bool = False
_session: DefaultAzureCredential
_identity: AzureIdentityInfo
_audit_config: dict
_region_config: AzureRegionConfig
_locations: dict
_mutelist: AzureMutelist
+ _resource_groups: dict[str, list[str]]
# TODO: this is not optional, enforce for all providers
audit_metadata: Audit_Metadata
@@ -122,6 +125,7 @@ class AzureProvider(Provider):
mutelist_content: dict = None,
client_id: str = None,
client_secret: str = None,
+ resource_groups: list = [],
):
"""
Initializes the Azure provider.
@@ -141,6 +145,7 @@ class AzureProvider(Provider):
mutelist_content (dict): The mutelist content.
client_id (str): The Azure client ID.
client_secret (str): The Azure client secret.
+ resource_groups (list): List of resource group names.
Returns:
None
@@ -205,7 +210,7 @@ class AzureProvider(Provider):
... managed_identity_auth=False,
... region="AzureUSGovernment",
... )
- - Subscriptions: rowler is multisubscription, which means that is going to scan all the subscriptions is able to list. If you only assign permissions to one subscription, it is going to scan a single one.
+ - Subscriptions: Prowler is multisubscription, which means that is going to scan all the subscriptions is able to list. If you only assign permissions to one subscription, it is going to scan a single one.
Prowler also allows you to specify the subscriptions you want to scan by passing a list of subscription IDs.
>>> AzureProvider(
... az_cli_auth=False,
@@ -214,6 +219,11 @@ class AzureProvider(Provider):
... managed_identity_auth=False,
... subscription_ids=["XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"],
... )
+ - Resource Groups: Prowler allows you to narrow the scan to specific resource groups.
+ >>> AzureProvider(
+ ... az_cli_auth=True,
+ ... resource_groups=["rg-production", "rg-staging"],
+ ... )
"""
logger.info("Setting Azure provider ...")
@@ -241,7 +251,10 @@ class AzureProvider(Provider):
azure_credentials = None
if tenant_id and client_id and client_secret:
azure_credentials = self.validate_static_credentials(
- tenant_id=tenant_id, client_id=client_id, client_secret=client_secret
+ tenant_id=tenant_id,
+ client_id=client_id,
+ client_secret=client_secret,
+ region_config=self._region_config,
)
# Set up the Azure session
@@ -268,6 +281,8 @@ class AzureProvider(Provider):
# TODO: should we keep this here or within the identity?
self._locations = self.get_locations()
+ self._resource_groups = self.validate_resource_groups(resource_groups)
+
# Audit Config
if config_content:
self._audit_config = config_content
@@ -333,6 +348,11 @@ class AzureProvider(Provider):
"""Mutelist object associated with this Azure provider."""
return self._mutelist
+ @property
+ def resource_groups(self) -> dict[str, list[str]]:
+ """Mapping of subscription ID to the list of resource groups to scan within it."""
+ return self._resource_groups
+
# TODO: this should be moved to the argparse, if not we need to enforce it from the Provider
# previously was using the AzureException
@staticmethod
@@ -410,6 +430,9 @@ class AzureProvider(Provider):
authority=config["authority"],
base_url=config["base_url"],
credential_scopes=config["credential_scopes"],
+ graph_host=config["graph_host"],
+ graph_scope=config["graph_scope"],
+ logs_endpoint=config["logs_endpoint"],
)
except ArgumentTypeError as validation_error:
logger.error(
@@ -432,7 +455,7 @@ class AzureProvider(Provider):
"""Azure credentials information.
This method prints the Azure Tenant Domain, Azure Tenant ID, Azure Region,
- Azure Subscriptions, Azure Identity Type, and Azure Identity ID.
+ Azure Subscriptions, Azure Resource Groups, Azure Identity Type, and Azure Identity ID.
Args:
None
@@ -448,6 +471,7 @@ class AzureProvider(Provider):
f"Azure Tenant Domain: {Fore.YELLOW}{self._identity.tenant_domain}{Style.RESET_ALL} Azure Tenant ID: {Fore.YELLOW}{self._identity.tenant_ids[0]}{Style.RESET_ALL}",
f"Azure Region: {Fore.YELLOW}{self.region_config.name}{Style.RESET_ALL}",
f"Azure Subscriptions: {Fore.YELLOW}{printed_subscriptions}{Style.RESET_ALL}",
+ f"Azure Resource Groups: {Fore.YELLOW}{sorted({rg for rgs in self._resource_groups.values() for rg in rgs}) if any(self._resource_groups.values()) else ('NONE (no matching resource groups found)' if self._resource_groups else 'ALL')}{Style.RESET_ALL}",
f"Azure Identity Type: {Fore.YELLOW}{self._identity.identity_type}{Style.RESET_ALL} Azure Identity ID: {Fore.YELLOW}{self._identity.identity_id}{Style.RESET_ALL}",
]
report_title = (
@@ -507,6 +531,7 @@ class AzureProvider(Provider):
tenant_id=azure_credentials["tenant_id"],
client_id=azure_credentials["client_id"],
client_secret=azure_credentials["client_secret"],
+ authority=region_config.authority,
)
return credentials
except ClientAuthenticationError as error:
@@ -579,7 +604,10 @@ class AzureProvider(Provider):
)
else:
try:
- credentials = InteractiveBrowserCredential(tenant_id=tenant_id)
+ credentials = InteractiveBrowserCredential(
+ tenant_id=tenant_id,
+ authority=region_config.authority,
+ )
except Exception as error:
logger.critical(
"Failed to retrieve azure credentials using browser authentication"
@@ -662,6 +690,7 @@ class AzureProvider(Provider):
tenant_id=tenant_id,
client_id=client_id,
client_secret=client_secret,
+ region_config=region_config,
)
# Set up the Azure session
@@ -675,7 +704,11 @@ class AzureProvider(Provider):
region_config,
)
# Create a SubscriptionClient
- subscription_client = SubscriptionClient(credentials)
+ subscription_client = SubscriptionClient(
+ credentials,
+ base_url=region_config.base_url,
+ credential_scopes=region_config.credential_scopes,
+ )
# Get info from the subscriptions
available_subscriptions = []
@@ -949,7 +982,7 @@ class AzureProvider(Provider):
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
)
- asyncio.get_event_loop().run_until_complete(get_azure_identity())
+ asyncio.run(get_azure_identity())
# Managed identities only can be assigned resource, resource group and subscription scope permissions
elif managed_identity_auth:
@@ -1039,7 +1072,11 @@ class AzureProvider(Provider):
}
"""
credentials = self.session
- subscription_client = SubscriptionClient(credentials)
+ subscription_client = SubscriptionClient(
+ credentials,
+ base_url=self.region_config.base_url,
+ credential_scopes=self.region_config.credential_scopes,
+ )
locations = {}
for subscription_id, display_name in self._identity.subscriptions.items():
@@ -1082,9 +1119,74 @@ class AzureProvider(Provider):
return set(chain.from_iterable(locations.values()))
+ def validate_resource_groups(self, resource_groups: list) -> dict[str, list[str]]:
+ """Validate requested resource groups across Azure subscriptions.
+
+ Args:
+ resource_groups: Resource group names requested for scanning.
+
+ Returns:
+ A mapping of subscription IDs to the matching resource group names.
+
+ The matching is case-insensitive and resolved independently for each
+ subscription. If a subscription's resource groups cannot be queried, a
+ warning is logged and that subscription keeps an empty resource group
+ list so the remaining subscriptions can still be validated.
+ """
+ resource_groups = [r.strip() for r in resource_groups if r and r.strip()]
+ if not resource_groups:
+ return {}
+
+ rg_map = {
+ subscription_id: [] for subscription_id in self._identity.subscriptions
+ }
+ credentials = self.session
+
+ for subscription_id, display_name in self._identity.subscriptions.items():
+ try:
+ rg_client = ResourceManagementClient(
+ credentials,
+ subscription_id,
+ base_url=self._region_config.base_url,
+ credential_scopes=self._region_config.credential_scopes,
+ )
+ existing_rgs = {
+ rg.name.lower(): rg.name for rg in rg_client.resource_groups.list()
+ }
+ except Exception as error:
+ logger.warning(
+ f"Could not list resource groups for subscription '{display_name}' "
+ f"({subscription_id}): {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}. "
+ "Skipping resource group filtering for this subscription."
+ )
+ continue
+
+ for rg in resource_groups:
+ real_name = existing_rgs.get(rg.lower())
+ if real_name:
+ rg_map[subscription_id].append(real_name)
+
+ for rg in resource_groups:
+ if not any(rg.lower() == r.lower() for rgs in rg_map.values() for r in rgs):
+ logger.warning(
+ f"Resource group '{rg}' was not found in any subscription. "
+ "Please check the resource group name and try again."
+ )
+
+ if not any(rgs for rgs in rg_map.values()):
+ logger.warning(
+ f"None of the provided resource groups {resource_groups} were found "
+ "in any subscription. Please check the resource group names and try again."
+ )
+
+ return rg_map
+
@staticmethod
def validate_static_credentials(
- tenant_id: str = None, client_id: str = None, client_secret: str = None
+ tenant_id: str = None,
+ client_id: str = None,
+ client_secret: str = None,
+ region_config: AzureRegionConfig = None,
) -> dict:
"""
Validates the static credentials for the Azure provider.
@@ -1093,6 +1195,9 @@ class AzureProvider(Provider):
tenant_id (str): The Azure Active Directory tenant ID.
client_id (str): The Azure client ID.
client_secret (str): The Azure client secret.
+ region_config (AzureRegionConfig): The region configuration used to
+ build the per-cloud login endpoint and Graph scope. Defaults to
+ the public-cloud configuration when not provided.
Raises:
AzureNotValidTenantIdError: If the provided Azure Tenant ID is not valid.
@@ -1129,8 +1234,13 @@ class AzureProvider(Provider):
message="The provided Azure Client Secret is not valid.",
)
+ if region_config is None:
+ region_config = AzureProvider.setup_region_config("AzureCloud")
+
try:
- AzureProvider.verify_client(tenant_id, client_id, client_secret)
+ AzureProvider.verify_client(
+ tenant_id, client_id, client_secret, region_config
+ )
return {
"tenant_id": tenant_id,
"client_id": client_id,
@@ -1162,7 +1272,9 @@ class AzureProvider(Provider):
)
@staticmethod
- def verify_client(tenant_id, client_id, client_secret) -> None:
+ def verify_client(
+ tenant_id, client_id, client_secret, region_config: AzureRegionConfig = None
+ ) -> None:
"""
Verifies the Azure client credentials using the specified tenant ID, client ID, and client secret.
@@ -1170,6 +1282,9 @@ class AzureProvider(Provider):
tenant_id (str): The Azure Active Directory tenant ID.
client_id (str): The Azure client ID.
client_secret (str): The Azure client secret.
+ region_config (AzureRegionConfig): The region configuration used to
+ build the per-cloud login endpoint and Graph scope. Defaults to
+ the public-cloud configuration when not provided.
Raises:
AzureNotValidTenantIdError: If the provided Azure Tenant ID is not valid.
@@ -1179,7 +1294,13 @@ class AzureProvider(Provider):
Returns:
None
"""
- url = f"https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token"
+ if region_config is None:
+ region_config = AzureProvider.setup_region_config("AzureCloud")
+ # `authority` is None for the public cloud and a bare host (e.g.
+ # `login.chinacloudapi.cn`) for sovereign clouds, mirroring the
+ # `AzureAuthorityHosts` constants used by azure-identity.
+ login_endpoint = region_config.authority or "login.microsoftonline.com"
+ url = f"https://{login_endpoint}/{tenant_id}/oauth2/v2.0/token"
headers = {
"Content-Type": "application/x-www-form-urlencoded",
"Accept": "application/json",
@@ -1188,7 +1309,7 @@ class AzureProvider(Provider):
"grant_type": "client_credentials",
"client_id": client_id,
"client_secret": client_secret,
- "scope": "https://graph.microsoft.com/.default",
+ "scope": region_config.graph_scope,
}
response = requests.post(url, headers=headers, data=data).json()
if "access_token" not in response.keys() and "error_codes" in response.keys():
diff --git a/prowler/providers/azure/lib/arguments/arguments.py b/prowler/providers/azure/lib/arguments/arguments.py
index 2b624a3f23..87bea948aa 100644
--- a/prowler/providers/azure/lib/arguments/arguments.py
+++ b/prowler/providers/azure/lib/arguments/arguments.py
@@ -53,6 +53,16 @@ def init_parser(self):
type=validate_azure_region,
help="Azure region from `az cloud list --output table`, by default AzureCloud",
)
+ # Resource Groups
+ azure_rg_subparser = azure_parser.add_argument_group("Resource Groups")
+ azure_rg_subparser.add_argument(
+ "--azure-resource-group",
+ "--azure-resource-groups",
+ nargs="+",
+ default=[],
+ dest="resource_groups",
+ help="Azure Resource Group names to scope the scan to specific groups.",
+ )
def validate_azure_region(region):
diff --git a/prowler/providers/azure/lib/regions/regions.py b/prowler/providers/azure/lib/regions/regions.py
index 6b88ab5561..b72a7c3af4 100644
--- a/prowler/providers/azure/lib/regions/regions.py
+++ b/prowler/providers/azure/lib/regions/regions.py
@@ -4,6 +4,18 @@ AZURE_CHINA_CLOUD = "https://management.chinacloudapi.cn"
AZURE_US_GOV_CLOUD = "https://management.usgovcloudapi.net"
AZURE_GENERIC_CLOUD = "https://management.azure.com"
+AZURE_GENERIC_GRAPH_HOST = "https://graph.microsoft.com"
+AZURE_CHINA_GRAPH_HOST = "https://microsoftgraph.chinacloudapi.cn"
+AZURE_US_GOV_GRAPH_HOST = "https://graph.microsoft.us"
+
+AZURE_GENERIC_GRAPH_SCOPE = f"{AZURE_GENERIC_GRAPH_HOST}/.default"
+AZURE_CHINA_GRAPH_SCOPE = f"{AZURE_CHINA_GRAPH_HOST}/.default"
+AZURE_US_GOV_GRAPH_SCOPE = f"{AZURE_US_GOV_GRAPH_HOST}/.default"
+
+AZURE_GENERIC_LOGS_ENDPOINT = "https://api.loganalytics.io"
+AZURE_CHINA_LOGS_ENDPOINT = "https://api.loganalytics.azure.cn"
+AZURE_US_GOV_LOGS_ENDPOINT = "https://api.loganalytics.us"
+
def get_regions_config(region):
allowed_regions = {
@@ -11,16 +23,25 @@ def get_regions_config(region):
"authority": None,
"base_url": AZURE_GENERIC_CLOUD,
"credential_scopes": [AZURE_GENERIC_CLOUD + "/.default"],
+ "graph_host": AZURE_GENERIC_GRAPH_HOST,
+ "graph_scope": AZURE_GENERIC_GRAPH_SCOPE,
+ "logs_endpoint": AZURE_GENERIC_LOGS_ENDPOINT,
},
"AzureChinaCloud": {
"authority": AzureAuthorityHosts.AZURE_CHINA,
"base_url": AZURE_CHINA_CLOUD,
"credential_scopes": [AZURE_CHINA_CLOUD + "/.default"],
+ "graph_host": AZURE_CHINA_GRAPH_HOST,
+ "graph_scope": AZURE_CHINA_GRAPH_SCOPE,
+ "logs_endpoint": AZURE_CHINA_LOGS_ENDPOINT,
},
"AzureUSGovernment": {
"authority": AzureAuthorityHosts.AZURE_GOVERNMENT,
"base_url": AZURE_US_GOV_CLOUD,
"credential_scopes": [AZURE_US_GOV_CLOUD + "/.default"],
+ "graph_host": AZURE_US_GOV_GRAPH_HOST,
+ "graph_scope": AZURE_US_GOV_GRAPH_SCOPE,
+ "logs_endpoint": AZURE_US_GOV_LOGS_ENDPOINT,
},
}
return allowed_regions[region]
diff --git a/prowler/providers/azure/lib/service/service.py b/prowler/providers/azure/lib/service/service.py
index f8cfd417c9..9d63639e94 100644
--- a/prowler/providers/azure/lib/service/service.py
+++ b/prowler/providers/azure/lib/service/service.py
@@ -1,5 +1,12 @@
+from collections.abc import Callable, Iterable
from concurrent.futures import ThreadPoolExecutor, as_completed
+from kiota_authentication_azure.azure_identity_authentication_provider import (
+ AzureIdentityAuthenticationProvider,
+)
+from msgraph.graph_request_adapter import GraphRequestAdapter
+from msgraph_core import GraphClientFactory
+
from prowler.lib.logger import logger
from prowler.providers.azure.azure_provider import AzureProvider
@@ -20,6 +27,7 @@ class AzureService:
)
self.subscriptions = provider.identity.subscriptions
+ self.resource_groups = provider.resource_groups
self.locations = provider.locations
self.audit_config = provider.audit_config
self.fixer_config = provider.fixer_config
@@ -43,14 +51,74 @@ class AzureService:
return results
+ def list_with_rg_scope(
+ self,
+ subscription_id: str,
+ list_all_fn: Callable[[], Iterable[object]],
+ list_by_rg_fn: Callable[..., Iterable[object]],
+ ) -> list[object]:
+ """List Azure resources using the provider resource group scope.
+
+ Args:
+ subscription_id: Subscription ID whose resource group scope should be used.
+ list_all_fn: Callable that lists all resources in the subscription when
+ no resource group filter is configured.
+ list_by_rg_fn: Callable that lists resources for a single resource
+ group. It must accept ``resource_group_name`` as a keyword argument.
+
+ Returns:
+ A list containing the resources returned by the selected Azure SDK
+ list operation.
+ """
+ if not self.resource_groups:
+ return list(list_all_fn())
+ resource_groups = self.resource_groups.get(subscription_id, [])
+ if not resource_groups:
+ logger.info(
+ f"No valid resource groups for subscription {subscription_id}, skipping."
+ )
+ return []
+ output = []
+ for resource_group in resource_groups:
+ try:
+ output += list(list_by_rg_fn(resource_group_name=resource_group))
+ except Exception as error:
+ logger.warning(
+ f"Subscription ID: {subscription_id} -- Resource Group: {resource_group} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return output
+
def __set_clients__(self, identity, session, service, region_config):
clients = {}
try:
if "GraphServiceClient" in str(service):
- clients.update({identity.tenant_domain: service(credentials=session)})
+ # GraphServiceClient(credentials, scopes=...) only customises the
+ # OAuth scope; the underlying httpx client's base URL stays at
+ # graph.microsoft.com. For sovereign clouds we must also point
+ # the HTTP transport at the per-cloud host, which is done by
+ # building a custom GraphRequestAdapter with a NationalClouds
+ # base URL.
+ auth_provider = AzureIdentityAuthenticationProvider(
+ session, scopes=[region_config.graph_scope]
+ )
+ http_client = GraphClientFactory.create_with_default_middleware(
+ host=region_config.graph_host
+ )
+ request_adapter = GraphRequestAdapter(auth_provider, client=http_client)
+ clients.update(
+ {identity.tenant_domain: service(request_adapter=request_adapter)}
+ )
elif "LogsQueryClient" in str(service):
for subscription_id, display_name in identity.subscriptions.items():
- clients.update({subscription_id: service(credential=session)})
+ clients.update(
+ {
+ subscription_id: service(
+ credential=session,
+ endpoint=region_config.logs_endpoint,
+ )
+ }
+ )
else:
for subscription_id, display_name in identity.subscriptions.items():
clients.update(
diff --git a/prowler/providers/azure/models.py b/prowler/providers/azure/models.py
index 752d1372c6..62d03db365 100644
--- a/prowler/providers/azure/models.py
+++ b/prowler/providers/azure/models.py
@@ -20,6 +20,9 @@ class AzureRegionConfig(BaseModel):
authority: Optional[str] = None
base_url: str = ""
credential_scopes: list = []
+ graph_host: str = "https://graph.microsoft.com"
+ graph_scope: str = "https://graph.microsoft.com/.default"
+ logs_endpoint: str = "https://api.loganalytics.io"
class AzureSubscription(BaseModel):
diff --git a/prowler/providers/azure/services/aisearch/aisearch_service.py b/prowler/providers/azure/services/aisearch/aisearch_service.py
index 3f482a41a5..01c6a458f7 100644
--- a/prowler/providers/azure/services/aisearch/aisearch_service.py
+++ b/prowler/providers/azure/services/aisearch/aisearch_service.py
@@ -17,7 +17,11 @@ class AISearch(AzureService):
for subscription, client in self.clients.items():
try:
aisearch_services.update({subscription: {}})
- aisearch_services_list = client.services.list_by_subscription()
+ aisearch_services_list = self.list_with_rg_scope(
+ subscription,
+ client.services.list_by_subscription,
+ client.services.list_by_resource_group,
+ )
for aisearch_service in aisearch_services_list:
aisearch_services[subscription].update(
{
diff --git a/tests/providers/alibabacloud/services/oss/oss_bucket_secure_transport_enabled/__init__.py b/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/oss/oss_bucket_secure_transport_enabled/__init__.py
rename to prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/__init__.py
diff --git a/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.metadata.json b/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.metadata.json
new file mode 100644
index 0000000000..77096d6a20
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "aks_cluster_auto_upgrade_enabled",
+ "CheckTitle": "AKS cluster has automatic upgrade enabled",
+ "CheckType": [],
+ "ServiceName": "aks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.containerservice/managedclusters",
+ "ResourceGroup": "container",
+ "Description": "**AKS clusters** are evaluated for an **automatic upgrade channel** other than `none`. Automatic upgrades keep the Kubernetes control plane and node pools on supported patch/minor versions and reduce version drift across clusters.",
+ "Risk": "Without automatic upgrades, AKS clusters can remain on unsupported or vulnerable Kubernetes versions. Delayed patching increases exposure to **known CVEs**, control plane/node defects, and exploit chains that can affect workload **confidentiality**, **integrity**, and **availability**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/aks/auto-upgrade-cluster",
+ "https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az aks update --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME> --auto-upgrade-channel patch",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure an AKS automatic upgrade channel so clusters receive Kubernetes version updates and security patches without relying only on manual upgrade processes. Use `patch` or `stable` for conservative production upgrades, reserve faster channels such as `rapid` for environments that can absorb quicker version changes, and avoid `none` unless a documented exception and manual patching process exists.",
+ "Url": "https://hub.prowler.com/check/aks_cluster_auto_upgrade_enabled"
+ }
+ },
+ "Categories": [
+ "vulnerabilities",
+ "cluster-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Automatic upgrade channels can change cluster versions during Azure-managed upgrade windows. Select a channel that matches the workload change tolerance and use planned maintenance windows, staging validation, and documented rollback procedures for production clusters."
+}
diff --git a/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.py b/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.py
new file mode 100644
index 0000000000..9d1f8b48a1
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_auto_upgrade_enabled/aks_cluster_auto_upgrade_enabled.py
@@ -0,0 +1,28 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.aks.aks_client import aks_client
+
+
+class aks_cluster_auto_upgrade_enabled(Check):
+ def execute(self) -> list[Check_Report_Azure]:
+ findings = []
+
+ for subscription_name, clusters in aks_client.clusters.items():
+ for cluster in clusters.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=cluster)
+ report.subscription = subscription_name
+
+ auto_upgrade_channel = (
+ (cluster.auto_upgrade_channel or "").strip().lower()
+ )
+ if auto_upgrade_channel and auto_upgrade_channel != "none":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Cluster '{cluster.name}' has auto-upgrade channel."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Cluster '{cluster.name}' does not have auto-upgrade configured."
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/__init__.py b/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/__init__.py
rename to prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/__init__.py
diff --git a/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.metadata.json b/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.metadata.json
new file mode 100644
index 0000000000..362b8e4d73
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "aks_cluster_azure_monitor_enabled",
+ "CheckTitle": "AKS cluster has Azure Monitor metrics enabled",
+ "CheckType": [],
+ "ServiceName": "aks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.containerservice/managedclusters",
+ "ResourceGroup": "container",
+ "Description": "**Azure Kubernetes Service** clusters are evaluated for **Azure Monitor managed service for Prometheus** (the cluster's `azureMonitorProfile.metrics` configuration). When enabled, cluster and workload metrics are collected into an Azure Monitor workspace for dashboards and alerting. This is distinct from Container Insights (the `omsagent` logs addon).",
+ "Risk": "Without **Azure Monitor metrics**, cluster degradation, resource exhaustion, and anomalous behavior go undetected. Lack of metric-based observability delays incident detection and hampers investigation after a security or availability event.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/azure-monitor/containers/kubernetes-monitoring-enable",
+ "https://learn.microsoft.com/en-us/azure/azure-monitor/containers/prometheus-metrics-enable",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az aks update --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME> --enable-azure-monitor-metrics",
+ "NativeIaC": "```bicep\n// Bicep: AKS cluster with Azure Monitor managed Prometheus metrics enabled\nresource aks 'Microsoft.ContainerService/managedClusters@2024-02-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n properties: {\n azureMonitorProfile: {\n metrics: {\n enabled: true // CRITICAL: enables Azure Monitor managed service for Prometheus (metrics)\n }\n }\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your AKS cluster\n2. In the left menu, select Monitoring > Insights\n3. Click Configure monitoring\n4. Ensure 'Enable Prometheus metrics' is selected and choose (or create) an Azure Monitor workspace\n5. Click Configure to enable Azure Monitor managed Prometheus metrics",
+ "Terraform": "```hcl\n# Terraform: AKS cluster with Azure Monitor managed Prometheus metrics enabled\nresource \"azurerm_kubernetes_cluster\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n location = \"<region>\"\n resource_group_name = \"<example_resource_name>\"\n dns_prefix = \"<example_resource_name>\"\n\n monitor_metrics {} # CRITICAL: enables Azure Monitor managed service for Prometheus (metrics)\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **Azure Monitor managed service for Prometheus** on AKS clusters so cluster and workload metrics are collected into an Azure Monitor workspace. Pair it with alerting on cluster health and resource saturation, and consider also enabling Container Insights (logs) for full observability.",
+ "Url": "https://hub.prowler.com/check/aks_cluster_azure_monitor_enabled"
+ }
+ },
+ "Categories": [
+ "logging"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.py b/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.py
new file mode 100644
index 0000000000..0c47f6373c
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_azure_monitor_enabled/aks_cluster_azure_monitor_enabled.py
@@ -0,0 +1,32 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.aks.aks_client import aks_client
+
+
+class aks_cluster_azure_monitor_enabled(Check):
+ """
+ Ensure Azure Monitor is enabled for AKS clusters.
+
+ This check evaluates whether each Azure Kubernetes Service cluster has Azure Monitor integration enabled for metrics collection, log aggregation, and alerting.
+
+ - PASS: The cluster has Azure Monitor enabled.
+ - FAIL: The cluster does not have Azure Monitor enabled.
+ """
+
+ def execute(self) -> list[Check_Report_Azure]:
+ findings = []
+
+ for subscription_name, clusters in aks_client.clusters.items():
+ for cluster in clusters.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=cluster)
+ report.subscription = subscription_name
+
+ if cluster.azure_monitor_enabled:
+ report.status = "PASS"
+ report.status_extended = f"Cluster '{cluster.name}' has Azure Monitor managed Prometheus metrics enabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Cluster '{cluster.name}' does not have Azure Monitor managed Prometheus metrics enabled."
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_no_root_access_key/__init__.py b/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_no_root_access_key/__init__.py
rename to prowler/providers/azure/services/aks/aks_cluster_defender_enabled/__init__.py
diff --git a/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.metadata.json b/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.metadata.json
new file mode 100644
index 0000000000..90bbd45f3b
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "azure",
+ "CheckID": "aks_cluster_defender_enabled",
+ "CheckTitle": "AKS cluster has Microsoft Defender security profile enabled",
+ "CheckType": [],
+ "ServiceName": "aks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.containerservice/managedclusters",
+ "ResourceGroup": "container",
+ "Description": "**AKS clusters** are evaluated for the **Microsoft Defender security profile** (`securityProfile.defender.securityMonitoring.enabled=true`). Defender for Containers extends security monitoring, threat detection, vulnerability assessment, and security posture insights to Azure Kubernetes Service workloads.",
+ "Risk": "Without the Microsoft Defender security profile, AKS runtime threats such as **cryptomining**, suspicious Kubernetes API activity, vulnerable container images, and malicious workload behavior may go undetected. Compromised containers can pivot to cluster resources and cloud APIs, impacting **confidentiality**, **integrity**, and **availability**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-containers-deployment-overview",
+ "https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-update",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az aks update --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME> --enable-defender",
+ "NativeIaC": "```bicep\n// AKS cluster with Microsoft Defender security monitoring enabled\nresource aks 'Microsoft.ContainerService/managedClusters@2024-05-01' = {\n name: '<CLUSTER_NAME>'\n location: '<LOCATION>'\n identity: {\n type: 'SystemAssigned'\n }\n properties: {\n dnsPrefix: '<DNS_PREFIX>'\n securityProfile: {\n defender: {\n logAnalyticsWorkspaceResourceId: '<LOG_ANALYTICS_WORKSPACE_RESOURCE_ID>'\n securityMonitoring: {\n enabled: true // Critical: enables Defender security monitoring for AKS\n }\n }\n }\n agentPoolProfiles: [\n {\n name: 'system'\n count: 1\n vmSize: 'Standard_DS2_v2'\n mode: 'System'\n }\n ]\n }\n}\n```",
+ "Other": "1. In Microsoft Defender for Cloud, enable the Containers plan for the subscription that contains the AKS cluster\n2. In the AKS cluster configuration, enable the Microsoft Defender security profile\n3. Verify that Defender security monitoring is enabled for the managed cluster",
+ "Terraform": "```hcl\nresource \"azurerm_log_analytics_workspace\" \"example\" {\n name = \"<workspace-name>\"\n location = \"<location>\"\n resource_group_name = \"<resource-group>\"\n sku = \"PerGB2018\"\n}\n\nresource \"azurerm_kubernetes_cluster\" \"example\" {\n name = \"<cluster-name>\"\n location = \"<location>\"\n resource_group_name = \"<resource-group>\"\n dns_prefix = \"<dns-prefix>\"\n\n default_node_pool {\n name = \"system\"\n node_count = 1\n vm_size = \"Standard_DS2_v2\"\n }\n\n identity {\n type = \"SystemAssigned\"\n }\n\n microsoft_defender {\n log_analytics_workspace_id = azurerm_log_analytics_workspace.example.id\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable the Microsoft Defender security profile for AKS clusters and ensure the subscription has Defender for Containers enabled. Route security monitoring data to the appropriate workspace and review Defender alerts and recommendations as part of the cluster operations process.",
+ "Url": "https://hub.prowler.com/check/aks_cluster_defender_enabled"
+ }
+ },
+ "Categories": [
+ "threat-detection",
+ "cluster-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check evaluates the AKS managed cluster Defender security monitoring flag. Defender for Containers plan availability, billing, workspace routing, and alert response processes should be validated separately at the subscription and security operations levels."
+}
diff --git a/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.py b/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.py
new file mode 100644
index 0000000000..08074754a6
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_defender_enabled/aks_cluster_defender_enabled.py
@@ -0,0 +1,29 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.aks.aks_client import aks_client
+
+
+class aks_cluster_defender_enabled(Check):
+ def execute(self) -> list[Check_Report_Azure]:
+ findings = []
+
+ for subscription_name, clusters in aks_client.clusters.items():
+ for cluster in clusters.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=cluster)
+ report.subscription = subscription_name
+
+ if cluster.defender_enabled is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Cluster '{cluster.name}' has Defender for Containers "
+ "enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Cluster '{cluster.name}' does not have Defender for "
+ "Containers enabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_lowercase/__init__.py b/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_lowercase/__init__.py
rename to prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/__init__.py
diff --git a/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.metadata.json b/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.metadata.json
new file mode 100644
index 0000000000..5577d4799c
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "aks_cluster_local_accounts_disabled",
+ "CheckTitle": "AKS cluster has local accounts disabled",
+ "CheckType": [],
+ "ServiceName": "aks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.containerservice/managedclusters",
+ "ResourceGroup": "container",
+ "Description": "**Azure Kubernetes Service** clusters are evaluated for **local account** status. Disabling local accounts forces all cluster authentication through Microsoft Entra ID, ensuring centralized identity management, MFA, and conditional access.",
+ "Risk": "Local accounts bypass **Entra ID** authentication, MFA, and conditional access policies. Compromised local credentials (such as the static cluster-admin certificate) provide persistent cluster access without an identity-based audit trail or governance.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/aks/manage-local-accounts-managed-azure-ad",
+ "https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-update",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az aks update --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME> --disable-local-accounts",
+ "NativeIaC": "```bicep\n// Bicep: AKS cluster with local accounts disabled\nresource aks 'Microsoft.ContainerService/managedClusters@2024-02-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n properties: {\n disableLocalAccounts: true // CRITICAL: forces authentication through Entra ID\n aadProfile: {\n managed: true\n enableAzureRbac: true\n }\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your AKS cluster\n2. Ensure Microsoft Entra ID (AAD) authentication is configured for the cluster\n3. Under Settings, select Cluster configuration (or Authentication and Authorization)\n4. Set Local accounts to Disabled\n5. Save the configuration",
+ "Terraform": "```hcl\n# Terraform: AKS cluster with local accounts disabled\nresource \"azurerm_kubernetes_cluster\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n location = \"<region>\"\n resource_group_name = \"<example_resource_name>\"\n dns_prefix = \"<example_resource_name>\"\n local_account_disabled = true # CRITICAL: forces authentication through Entra ID\n\n azure_active_directory_role_based_access_control {\n azure_rbac_enabled = true\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Disable local accounts on AKS clusters and require **Microsoft Entra ID** authentication with Azure RBAC. Before disabling, confirm Entra ID integration and break-glass access are in place so administrators retain authenticated access, then enforce MFA and conditional access on cluster identities.",
+ "Url": "https://hub.prowler.com/check/aks_cluster_local_accounts_disabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.py b/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.py
new file mode 100644
index 0000000000..85670e0d15
--- /dev/null
+++ b/prowler/providers/azure/services/aks/aks_cluster_local_accounts_disabled/aks_cluster_local_accounts_disabled.py
@@ -0,0 +1,36 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.aks.aks_client import aks_client
+
+
+class aks_cluster_local_accounts_disabled(Check):
+ """
+ Ensure local accounts are disabled on AKS clusters.
+
+ This check evaluates whether each Azure Kubernetes Service cluster has local accounts disabled, forcing all authentication through Microsoft Entra ID.
+
+ - PASS: The cluster has local accounts disabled.
+ - FAIL: The cluster has local accounts enabled.
+ """
+
+ def execute(self) -> list[Check_Report_Azure]:
+ findings = []
+
+ for subscription_name, clusters in aks_client.clusters.items():
+ for cluster in clusters.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=cluster)
+ report.subscription = subscription_name
+
+ if cluster.local_accounts_disabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Cluster '{cluster.name}' has local accounts disabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Cluster '{cluster.name}' has local accounts enabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/aks/aks_service.py b/prowler/providers/azure/services/aks/aks_service.py
index 3d158a2f70..0bd7c4d63c 100644
--- a/prowler/providers/azure/services/aks/aks_service.py
+++ b/prowler/providers/azure/services/aks/aks_service.py
@@ -1,5 +1,5 @@
from dataclasses import dataclass
-from typing import List
+from typing import List, Optional
from azure.mgmt.containerservice import ContainerServiceClient
@@ -19,8 +19,12 @@ class AKS(AzureService):
for subscription_id, client in self.clients.items():
try:
- clusters_list = client.managed_clusters.list()
clusters.update({subscription_id: {}})
+ clusters_list = self.list_with_rg_scope(
+ subscription_id,
+ client.managed_clusters.list,
+ client.managed_clusters.list_by_resource_group,
+ )
for cluster in clusters_list:
if getattr(cluster, "kubernetes_version", None):
@@ -55,6 +59,56 @@ class AKS(AzureService):
)
],
rbac_enabled=getattr(cluster, "enable_rbac", False),
+ auto_upgrade_channel=getattr(
+ getattr(cluster, "auto_upgrade_profile", None),
+ "upgrade_channel",
+ None,
+ ),
+ defender_enabled=bool(
+ getattr(
+ getattr(
+ getattr(
+ getattr(
+ cluster,
+ "security_profile",
+ None,
+ ),
+ "defender",
+ None,
+ ),
+ "security_monitoring",
+ None,
+ ),
+ "enabled",
+ False,
+ )
+ ),
+ azure_monitor_enabled=(
+ bool(
+ getattr(
+ getattr(
+ getattr(
+ cluster,
+ "azure_monitor_profile",
+ None,
+ ),
+ "metrics",
+ None,
+ ),
+ "enabled",
+ False,
+ )
+ )
+ if getattr(
+ cluster, "azure_monitor_profile", None
+ )
+ else False
+ ),
+ local_accounts_disabled=bool(
+ getattr(
+ cluster, "disable_local_accounts", False
+ )
+ ),
)
}
)
@@ -82,3 +136,7 @@ class Cluster:
agent_pool_profiles: List[ManagedClusterAgentPoolProfile]
rbac_enabled: bool
location: str
+ auto_upgrade_channel: Optional[str] = None
+ defender_enabled: bool = False
+ azure_monitor_enabled: bool = False
+ local_accounts_disabled: bool = False
diff --git a/prowler/providers/azure/services/apim/apim_service.py b/prowler/providers/azure/services/apim/apim_service.py
index 98fb00f276..3186716ddb 100644
--- a/prowler/providers/azure/services/apim/apim_service.py
+++ b/prowler/providers/azure/services/apim/apim_service.py
@@ -131,7 +131,11 @@ class APIM(AzureService):
for subscription, client in self.clients.items():
try:
instances.update({subscription: []})
- apim_instances = client.api_management_service.list()
+ apim_instances = self.list_with_rg_scope(
+ subscription,
+ client.api_management_service.list,
+ client.api_management_service.list_by_resource_group,
+ )
for instance in apim_instances:
workspace_id = self._get_log_analytics_workspace_id(
diff --git a/prowler/providers/azure/services/app/app_function_application_insights_enabled/app_function_application_insights_enabled.py b/prowler/providers/azure/services/app/app_function_application_insights_enabled/app_function_application_insights_enabled.py
index 6fec5e7042..a903097beb 100644
--- a/prowler/providers/azure/services/app/app_function_application_insights_enabled/app_function_application_insights_enabled.py
+++ b/prowler/providers/azure/services/app/app_function_application_insights_enabled/app_function_application_insights_enabled.py
@@ -14,7 +14,7 @@ class app_function_application_insights_enabled(Check):
subscription_id, subscription_id
)
for function in functions.values():
- if function.enviroment_variables is not None:
+ if function.environment_variables is not None:
report = Check_Report_Azure(
metadata=self.metadata(), resource=function
)
@@ -22,9 +22,9 @@ class app_function_application_insights_enabled(Check):
report.status = "FAIL"
report.status_extended = f"Function {function.name} from subscription {subscription_name} ({subscription_id}) is not using Application Insights."
- if function.enviroment_variables.get(
+ if function.environment_variables.get(
"APPINSIGHTS_INSTRUMENTATIONKEY", None
- ) or function.enviroment_variables.get(
+ ) or function.environment_variables.get(
"APPLICATIONINSIGHTS_CONNECTION_STRING", None
):
report.status = "PASS"
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_max_login_attempts/__init__.py b/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_max_login_attempts/__init__.py
rename to prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/__init__.py
diff --git a/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.metadata.json b/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.metadata.json
new file mode 100644
index 0000000000..7696bec34f
--- /dev/null
+++ b/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "app_function_ensure_http_is_redirected_to_https",
+ "CheckTitle": "Function app redirects HTTP to HTTPS",
+ "CheckType": [],
+ "ServiceName": "app",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.web/sites",
+ "ResourceGroup": "serverless",
+ "Description": "**Azure Function apps** redirect `HTTP` traffic to `HTTPS` when the `HTTPS Only` setting is enabled. This evaluation identifies Function apps that do not force secure transport by checking whether plaintext requests are automatically redirected to encrypted endpoints.",
+ "Risk": "Leaving **HTTP accessible** on a Function app enables **man-in-the-middle** interception, credential and token theft, and response tampering. This undermines **confidentiality** and **integrity**, and can lead to session hijacking or downgrade attacks that bypass TLS.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-bindings#enforce-https",
+ "https://learn.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-data-protection#dp-3-encrypt-sensitive-data-in-transit"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az functionapp update --resource-group <RESOURCE_GROUP_NAME> --name <FUNCTION_APP_NAME> --https-only true",
+ "NativeIaC": "```bicep\n// Enable HTTPS-only redirect on an existing Function App\nresource functionApp 'Microsoft.Web/sites@2022-09-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n properties: {\n httpsOnly: true // Critical: forces redirect from HTTP to HTTPS\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and go to Function Apps\n2. Select your Function app\n3. Go to TLS/SSL settings and set HTTPS Only to On\n4. Click Save",
+ "Terraform": "```hcl\n# Enforce HTTPS-only on a Function App\nresource \"azurerm_linux_function_app\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<example_location>\"\n service_plan_id = \"<example_resource_id>\"\n storage_account_name = \"<example_resource_name>\"\n storage_account_access_key = \"<example_secret_value>\"\n\n https_only = true # Critical: redirects HTTP to HTTPS\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enforce **HTTPS-only** for all Function apps.\n- Use trusted certificates and require `TLS 1.2` or later\n- Enable **HSTS** to prevent downgrade/mixed-content\n- Redirect legacy `http` links to `https`\n- Minimize HTTP exposure via WAF/CDN or private access\nApply **defense in depth** to protect data in transit.",
+ "Url": "https://hub.prowler.com/check/app_function_ensure_http_is_redirected_to_https"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check mirrors app_ensure_http_is_redirected_to_https but evaluates Function apps (Microsoft.Web/sites with kind starting with 'functionapp') via app_client.functions. When HTTPS Only is enabled, every incoming HTTP request is redirected to the HTTPS port."
+}
diff --git a/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.py b/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.py
new file mode 100644
index 0000000000..17090ac2cf
--- /dev/null
+++ b/prowler/providers/azure/services/app/app_function_ensure_http_is_redirected_to_https/app_function_ensure_http_is_redirected_to_https.py
@@ -0,0 +1,35 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.app.app_client import app_client
+
+
+class app_function_ensure_http_is_redirected_to_https(Check):
+ """Ensure Function Apps redirect HTTP traffic to HTTPS."""
+
+ def execute(self) -> list[Check_Report_Azure]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports for Function Apps HTTPS-only enforcement.
+ """
+ findings = []
+
+ for (
+ subscription_id,
+ functions,
+ ) in app_client.functions.items():
+ subscription_name = app_client.subscriptions.get(
+ subscription_id, subscription_id
+ )
+ for function in functions.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=function)
+ report.subscription = subscription_id
+ report.status = "PASS"
+ report.status_extended = f"HTTP is redirected to HTTPS for Function app '{function.name}' in subscription '{subscription_name} ({subscription_id})'."
+
+ if not function.https_only:
+ report.status = "FAIL"
+ report.status_extended = f"HTTP is not redirected to HTTPS for Function app '{function.name}' in subscription '{subscription_name} ({subscription_id})'."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/app/app_function_latest_runtime_version/app_function_latest_runtime_version.py b/prowler/providers/azure/services/app/app_function_latest_runtime_version/app_function_latest_runtime_version.py
index 828362a8fe..694c5bbdc6 100644
--- a/prowler/providers/azure/services/app/app_function_latest_runtime_version/app_function_latest_runtime_version.py
+++ b/prowler/providers/azure/services/app/app_function_latest_runtime_version/app_function_latest_runtime_version.py
@@ -14,7 +14,7 @@ class app_function_latest_runtime_version(Check):
subscription_id, subscription_id
)
for function in functions.values():
- if function.enviroment_variables is not None:
+ if function.environment_variables is not None:
report = Check_Report_Azure(
metadata=self.metadata(), resource=function
)
@@ -23,13 +23,13 @@ class app_function_latest_runtime_version(Check):
report.status_extended = f"Function {function.name} from subscription {subscription_name} ({subscription_id}) is using the latest runtime."
if (
- function.enviroment_variables.get(
+ function.environment_variables.get(
"FUNCTIONS_EXTENSION_VERSION", ""
)
!= "~4"
):
report.status = "FAIL"
- report.status_extended = f"Function {function.name} from subscription {subscription_name} ({subscription_id}) is not using the latest runtime. The current runtime is '{function.enviroment_variables.get('FUNCTIONS_EXTENSION_VERSION', '')}' and should be '~4'."
+ report.status_extended = f"Function {function.name} from subscription {subscription_name} ({subscription_id}) is not using the latest runtime. The current runtime is '{function.environment_variables.get('FUNCTIONS_EXTENSION_VERSION', '')}' and should be '~4'."
findings.append(report)
diff --git a/prowler/providers/azure/services/app/app_service.py b/prowler/providers/azure/services/app/app_service.py
index 201cd6a344..68c683caa1 100644
--- a/prowler/providers/azure/services/app/app_service.py
+++ b/prowler/providers/azure/services/app/app_service.py
@@ -22,8 +22,12 @@ class App(AzureService):
for subscription_id, client in self.clients.items():
try:
- apps_list = client.web_apps.list()
apps.update({subscription_id: {}})
+ apps_list = self.list_with_rg_scope(
+ subscription_id,
+ client.web_apps.list,
+ client.web_apps.list_by_resource_group,
+ )
for app in apps_list:
# Filter function apps
@@ -117,8 +121,12 @@ class App(AzureService):
for subscription_id, client in self.clients.items():
try:
- functions_list = client.web_apps.list()
functions.update({subscription_id: {}})
+ functions_list = self.list_with_rg_scope(
+ subscription_id,
+ client.web_apps.list,
+ client.web_apps.list_by_resource_group,
+ )
for function in functions_list:
# Filter function apps
@@ -150,7 +158,7 @@ class App(AzureService):
location=function.location,
kind=function.kind,
function_keys=function_keys,
- enviroment_variables=getattr(
+ environment_variables=getattr(
application_settings, "properties", None
),
identity=getattr(function, "identity", None),
@@ -170,6 +178,7 @@ class App(AzureService):
ftps_state=getattr(
function_config, "ftps_state", None
),
+ https_only=getattr(function, "https_only", False),
)
}
)
@@ -217,7 +226,7 @@ class App(AzureService):
name=name,
)
except Exception as error:
- logger.error(
+ logger.warning(
f"Error getting host keys for {name} in {resource_group}: {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
return None
@@ -241,7 +250,7 @@ class App(AzureService):
name=name,
)
except Exception as error:
- logger.error(
+ logger.warning(
f"Error getting application settings for {name} in {resource_group}: {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
return None
@@ -288,8 +297,9 @@ class FunctionApp:
location: str
kind: str
function_keys: Optional[Dict[str, str]]
- enviroment_variables: Optional[Dict[str, str]]
+ environment_variables: Optional[Dict[str, str]]
identity: ManagedServiceIdentity
public_access: bool
vnet_subnet_id: str
ftps_state: Optional[str]
+ https_only: bool = False
diff --git a/prowler/providers/azure/services/appinsights/appinsights_service.py b/prowler/providers/azure/services/appinsights/appinsights_service.py
index 918a0f1b0f..6e92a7b275 100644
--- a/prowler/providers/azure/services/appinsights/appinsights_service.py
+++ b/prowler/providers/azure/services/appinsights/appinsights_service.py
@@ -17,8 +17,12 @@ class AppInsights(AzureService):
for subscription_id, client in self.clients.items():
try:
- components_list = client.components.list()
components.update({subscription_id: {}})
+ components_list = self.list_with_rg_scope(
+ subscription_id,
+ client.components.list,
+ client.components.list_by_resource_group,
+ )
for component in components_list:
components[subscription_id].update(
diff --git a/prowler/providers/azure/services/containerregistry/containerregistry_service.py b/prowler/providers/azure/services/containerregistry/containerregistry_service.py
index ee6cce39f2..c44a0c7ef1 100644
--- a/prowler/providers/azure/services/containerregistry/containerregistry_service.py
+++ b/prowler/providers/azure/services/containerregistry/containerregistry_service.py
@@ -19,8 +19,12 @@ class ContainerRegistry(AzureService):
registries = {}
for subscription, client in self.clients.items():
try:
- registries_list = client.registries.list()
registries.update({subscription: {}})
+ registries_list = self.list_with_rg_scope(
+ subscription,
+ client.registries.list,
+ client.registries.list_by_resource_group,
+ )
for registry in registries_list:
resource_group = self._get_resource_group(registry.id)
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_max_password_age/__init__.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_max_password_age/__init__.py
rename to prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/__init__.py
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.metadata.json b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.metadata.json
new file mode 100644
index 0000000000..41246ff7a6
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "cosmosdb_account_automatic_failover_enabled",
+ "CheckTitle": "Cosmos DB account has automatic failover enabled",
+ "CheckType": [],
+ "ServiceName": "cosmosdb",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.documentdb/databaseaccounts",
+ "ResourceGroup": "database",
+ "Description": "**Azure Cosmos DB accounts** are evaluated for **automatic failover** configuration. When enabled, Cosmos DB automatically promotes a secondary region to primary during a regional outage, ensuring continuous availability without manual intervention.",
+ "Risk": "Without **automatic failover**, a regional outage requires **manual failover** which delays recovery and risks data unavailability. Applications dependent on the primary region experience downtime until an operator intervenes.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-manage-database-account#automatic-failover",
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/high-availability",
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/distribute-data-globally"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az cosmosdb update --name <COSMOS_ACCOUNT_NAME> --resource-group <RESOURCE_GROUP> --enable-automatic-failover true",
+ "NativeIaC": "```bicep\n// Bicep: Enable automatic failover on a Cosmos DB account\nresource account 'Microsoft.DocumentDB/databaseAccounts@2025-10-15' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n kind: 'GlobalDocumentDB'\n properties: {\n databaseAccountOfferType: 'Standard'\n locations: [\n { locationName: '<primary_region>', failoverPriority: 0 }\n { locationName: '<secondary_region>', failoverPriority: 1 }\n ]\n enableAutomaticFailover: true // Critical: Promotes a secondary region during a primary region outage\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your Cosmos DB account\n2. In the left menu, select Replicate data globally\n3. Click Automatic Failover\n4. Toggle Enable Automatic Failover to On\n5. Set failover priorities for each region\n6. Click Save",
+ "Terraform": "```hcl\n# Terraform: Enable automatic failover on a Cosmos DB account\nresource \"azurerm_cosmosdb_account\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<primary_region>\"\n offer_type = \"Standard\"\n kind = \"GlobalDocumentDB\"\n\n geo_location {\n location = \"<primary_region>\"\n failover_priority = 0\n }\n\n geo_location {\n location = \"<secondary_region>\"\n failover_priority = 1\n }\n\n enable_automatic_failover = true # Critical: Promotes a secondary region during a primary region outage\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **automatic failover** on Cosmos DB accounts with **multi-region** deployments so a secondary region is promoted automatically when the primary region becomes unavailable. Configure **failover priorities** to reflect your recovery strategy, validate **RTO/RPO** expectations with periodic failover drills, and combine with **multi-region writes** where active-active is required.",
+ "Url": "https://hub.prowler.com/check/cosmosdb_account_automatic_failover_enabled"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.py
new file mode 100644
index 0000000000..7d7d2e5023
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_automatic_failover_enabled/cosmosdb_account_automatic_failover_enabled.py
@@ -0,0 +1,29 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.cosmosdb.cosmosdb_client import cosmosdb_client
+
+
+class cosmosdb_account_automatic_failover_enabled(Check):
+ """Ensure that Cosmos DB accounts have automatic failover enabled."""
+
+ def execute(self) -> Check_Report_Azure:
+ """Execute the Cosmos DB automatic failover check.
+
+ Iterates over every Cosmos DB account fetched by the service and reports
+ PASS when `enableAutomaticFailover` is True, FAIL otherwise.
+
+ Returns:
+ A list of Check_Report_Azure with one report per Cosmos DB account.
+ """
+ findings = []
+ for subscription, accounts in cosmosdb_client.accounts.items():
+ for account in accounts:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=account)
+ report.subscription = subscription
+ report.status = "FAIL"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} does not have automatic failover enabled."
+ if account.enable_automatic_failover:
+ report.status = "PASS"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} has automatic failover enabled."
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_minimum_length/__init__.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_minimum_length/__init__.py
rename to prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/__init__.py
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.metadata.json b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.metadata.json
new file mode 100644
index 0000000000..1631aa5b3a
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "cosmosdb_account_backup_policy_continuous",
+ "CheckTitle": "Cosmos DB account uses continuous backup policy",
+ "CheckType": [],
+ "ServiceName": "cosmosdb",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.documentdb/databaseaccounts",
+ "ResourceGroup": "database",
+ "Description": "**Azure Cosmos DB accounts** are evaluated for **continuous backup** policy. Continuous backup provides **point-in-time restore (PITR)** enabling recovery to any point within the retention window, unlike periodic backup which only supports full restores at fixed intervals.",
+ "Risk": "**Periodic backup** limits recovery to the last backup snapshot. Data changes between snapshots are lost during restore. **Continuous backup** enables **granular recovery** from accidental deletes, corruption, or ransomware.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/continuous-backup-restore-introduction",
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/migrate-continuous-backup",
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/restore-account-continuous-backup"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az cosmosdb update --name <COSMOS_ACCOUNT_NAME> --resource-group <RESOURCE_GROUP> --backup-policy-type Continuous --continuous-tier Continuous30Days",
+ "NativeIaC": "```bicep\n// Bicep: Switch a Cosmos DB account to Continuous backup (irreversible)\nresource account 'Microsoft.DocumentDB/databaseAccounts@2025-10-15' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n kind: 'GlobalDocumentDB'\n properties: {\n databaseAccountOfferType: 'Standard'\n locations: [{ locationName: resourceGroup().location }]\n backupPolicy: {\n type: 'Continuous' // Critical: Enables point-in-time restore. Migration from Periodic is one-way.\n continuousModeProperties: {\n tier: 'Continuous30Days' // or 'Continuous7Days' for the lower-cost tier\n }\n }\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your Cosmos DB account\n2. In the left menu, select Backup & Restore\n3. Click Switch to Continuous backup\n4. Select the retention tier (Continuous30Days or Continuous7Days)\n5. Acknowledge that the migration from Periodic to Continuous is irreversible\n6. Click Save",
+ "Terraform": "```hcl\n# Terraform: Configure Cosmos DB account with Continuous backup (irreversible)\nresource \"azurerm_cosmosdb_account\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<example_resource_name>\"\n offer_type = \"Standard\"\n kind = \"GlobalDocumentDB\"\n\n geo_location {\n location = \"<example_resource_name>\"\n failover_priority = 0\n }\n\n backup {\n type = \"Continuous\" # Critical: Enables point-in-time restore. One-way migration from Periodic.\n tier = \"Continuous30Days\" # or \"Continuous7Days\" for the lower-cost tier\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Use **Continuous backup** for Cosmos DB accounts that require **point-in-time restore (PITR)**. Pick the retention tier (`Continuous7Days` or `Continuous30Days`) based on recovery objectives, and validate restore procedures with periodic drills. Note that switching from **Periodic** to **Continuous** is a **one-way** migration; plan the change and review pricing before applying.",
+ "Url": "https://hub.prowler.com/check/cosmosdb_account_backup_policy_continuous"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.py
new file mode 100644
index 0000000000..f1a00fc2e8
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_backup_policy_continuous/cosmosdb_account_backup_policy_continuous.py
@@ -0,0 +1,30 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.cosmosdb.cosmosdb_client import cosmosdb_client
+
+
+class cosmosdb_account_backup_policy_continuous(Check):
+ """Ensure that Cosmos DB accounts use the continuous backup policy."""
+
+ def execute(self) -> Check_Report_Azure:
+ """Execute the Cosmos DB continuous-backup check.
+
+ Iterates over every Cosmos DB account fetched by the service and reports
+ PASS when `backupPolicy.type` is `Continuous`, FAIL otherwise (including
+ when the property is missing).
+
+ Returns:
+ A list of Check_Report_Azure with one report per Cosmos DB account.
+ """
+ findings = []
+ for subscription, accounts in cosmosdb_client.accounts.items():
+ for account in accounts:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=account)
+ report.subscription = subscription
+ report.status = "FAIL"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} does not use continuous backup policy."
+ if account.backup_policy_type == "Continuous":
+ report.status = "PASS"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} uses continuous backup policy."
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_password_reuse_prevention/__init__.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_password_reuse_prevention/__init__.py
rename to prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/__init__.py
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.metadata.json b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.metadata.json
new file mode 100644
index 0000000000..f9ddb2baa0
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "cosmosdb_account_minimum_tls_version",
+ "CheckTitle": "Cosmos DB account enforces TLS 1.2 or higher",
+ "CheckType": [],
+ "ServiceName": "cosmosdb",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.documentdb/databaseaccounts",
+ "ResourceGroup": "database",
+ "Description": "**Azure Cosmos DB accounts** are evaluated for **minimum TLS version**. TLS 1.0 and 1.1 are deprecated and contain known weaknesses. Enforcing **TLS 1.2** ensures all client connections negotiate modern, secure encryption protocols.",
+ "Risk": "Allowing **TLS 1.0/1.1** exposes client connections to **POODLE**, **BEAST**, and other protocol downgrade attacks that can compromise the **confidentiality** and **integrity** of data in transit, and may enable credential interception via weakened cipher suites.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/security",
+ "https://learn.microsoft.com/en-us/cli/azure/cosmosdb",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/databaseaccounts"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az cosmosdb update --name <COSMOS_ACCOUNT_NAME> --resource-group <RESOURCE_GROUP> --minimal-tls-version Tls12",
+ "NativeIaC": "```bicep\n// Bicep: Enforce minimum TLS 1.2 on a Cosmos DB account\nresource account 'Microsoft.DocumentDB/databaseAccounts@2025-10-15' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n kind: 'GlobalDocumentDB'\n properties: {\n databaseAccountOfferType: 'Standard'\n locations: [{ locationName: resourceGroup().location }]\n minimalTlsVersion: 'Tls12' // Critical: Rejects client connections negotiating TLS 1.0 or 1.1\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your Cosmos DB account\n2. In the left menu, select Networking\n3. Locate the Minimum TLS version setting\n4. Select TLS 1.2\n5. Click Save\n6. Validate that all client applications support TLS 1.2 before enforcing the change",
+ "Terraform": "```hcl\n# Terraform: Enforce minimum TLS 1.2 on a Cosmos DB account\nresource \"azurerm_cosmosdb_account\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<example_location>\"\n offer_type = \"Standard\"\n kind = \"GlobalDocumentDB\"\n\n geo_location {\n location = \"<example_location>\"\n failover_priority = 0\n }\n\n minimal_tls_version = \"Tls12\" # Critical: Rejects client connections negotiating TLS 1.0 or 1.1\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Set the Cosmos DB account **minimum TLS version** to at least **1.2** to block legacy protocols (`TLS 1.0`/`1.1`) vulnerable to known downgrade and cipher attacks. Inventory and update **client SDKs** and **drivers** to support TLS 1.2 prior to enforcement, and pair this control with **private endpoints**, **AAD/RBAC authentication**, and **handshake failure monitoring** to identify outdated clients.",
+ "Url": "https://hub.prowler.com/check/cosmosdb_account_minimum_tls_version"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.py
new file mode 100644
index 0000000000..5d85072367
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_minimum_tls_version/cosmosdb_account_minimum_tls_version.py
@@ -0,0 +1,30 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.cosmosdb.cosmosdb_client import cosmosdb_client
+
+
+class cosmosdb_account_minimum_tls_version(Check):
+ """Ensure that Cosmos DB accounts enforce TLS 1.2 or higher."""
+
+ def execute(self) -> Check_Report_Azure:
+ """Execute the Cosmos DB minimum TLS version check.
+
+ Iterates over every Cosmos DB account fetched by the service and reports
+ PASS when `minimalTlsVersion` is `Tls12` or higher, FAIL otherwise
+ (including when the property is missing or set to a legacy value).
+
+ Returns:
+ A list of Check_Report_Azure with one report per Cosmos DB account.
+ """
+ findings = []
+ for subscription, accounts in cosmosdb_client.accounts.items():
+ for account in accounts:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=account)
+ report.subscription = subscription
+ report.status = "FAIL"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} does not enforce TLS 1.2 or higher."
+ if account.minimal_tls_version in {"Tls12", "Tls13"}:
+ report.status = "PASS"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} enforces TLS 1.2 or higher."
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_symbol/__init__.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_symbol/__init__.py
rename to prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/__init__.py
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.metadata.json b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.metadata.json
new file mode 100644
index 0000000000..2d8a61a54e
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "cosmosdb_account_public_network_access_disabled",
+ "CheckTitle": "Cosmos DB account has public network access disabled",
+ "CheckType": [],
+ "ServiceName": "cosmosdb",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.documentdb/databaseaccounts",
+ "ResourceGroup": "database",
+ "Description": "**Azure Cosmos DB accounts** are evaluated for **public network access**. Disabling public network access ensures the account is only reachable through **private endpoints** or **VNet service endpoints**, reducing the attack surface and preventing direct exposure of the data plane to the internet.",
+ "Risk": "Allowing **public network access** exposes the Cosmos DB data plane to the internet. Combined with leaked **connection strings**, weak **firewall rules**, or compromised **AAD tokens**, this enables **unauthorized data access**, **enumeration**, **brute force**, and **data exfiltration** from any source on the internet.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-private-endpoints",
+ "https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-firewall",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/databaseaccounts"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az cosmosdb update --name <COSMOS_ACCOUNT_NAME> --resource-group <RESOURCE_GROUP> --public-network-access Disabled",
+ "NativeIaC": "```bicep\n// Bicep: Disable public network access on a Cosmos DB account\nresource account 'Microsoft.DocumentDB/databaseAccounts@2025-10-15' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n kind: 'GlobalDocumentDB'\n properties: {\n databaseAccountOfferType: 'Standard'\n locations: [{ locationName: resourceGroup().location }]\n publicNetworkAccess: 'Disabled' // Critical: Blocks all public-internet traffic to the data plane\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your Cosmos DB account\n2. In the left menu, select Networking\n3. Under Public network access, select Disabled\n4. Configure private endpoints or VNet service endpoints before saving so clients retain connectivity\n5. Click Save",
+ "Terraform": "```hcl\n# Terraform: Disable public network access on a Cosmos DB account\nresource \"azurerm_cosmosdb_account\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<example_location>\"\n offer_type = \"Standard\"\n kind = \"GlobalDocumentDB\"\n\n geo_location {\n location = \"<example_location>\"\n failover_priority = 0\n }\n\n public_network_access_enabled = false # Critical: Blocks all public-internet traffic to the data plane\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Disable **public network access** on Cosmos DB accounts and require connectivity via **private endpoints** or **VNet service endpoints**. Before enforcement, validate that all application workloads have private-network connectivity, and pair this control with **AAD/RBAC authentication**, **TLS 1.2+**, and **firewall rules** restricted to the minimum trusted ranges to uphold **defense in depth**.",
+ "Url": "https://hub.prowler.com/check/cosmosdb_account_public_network_access_disabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.py
new file mode 100644
index 0000000000..ec2d29728d
--- /dev/null
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_account_public_network_access_disabled/cosmosdb_account_public_network_access_disabled.py
@@ -0,0 +1,31 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.cosmosdb.cosmosdb_client import cosmosdb_client
+
+
+class cosmosdb_account_public_network_access_disabled(Check):
+ """Ensure that Cosmos DB accounts have public network access disabled."""
+
+ def execute(self) -> Check_Report_Azure:
+ """Execute the Cosmos DB public network access check.
+
+ Iterates over every Cosmos DB account fetched by the service and reports
+ PASS when `publicNetworkAccess` is `Disabled` or `SecuredByPerimeter`
+ (Microsoft Network Security Perimeter), FAIL otherwise (including when
+ the property is missing or set to `Enabled`).
+
+ Returns:
+ A list of Check_Report_Azure with one report per Cosmos DB account.
+ """
+ findings = []
+ for subscription, accounts in cosmosdb_client.accounts.items():
+ for account in accounts:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=account)
+ report.subscription = subscription
+ report.status = "FAIL"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} does not have public network access disabled (current value: {account.public_network_access!r})."
+ if account.public_network_access in {"Disabled", "SecuredByPerimeter"}:
+ report.status = "PASS"
+ report.status_extended = f"CosmosDB account {account.name} from subscription {subscription} has public network access disabled."
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/cosmosdb/cosmosdb_service.py b/prowler/providers/azure/services/cosmosdb/cosmosdb_service.py
index c36af1d2e9..37b06da1c5 100644
--- a/prowler/providers/azure/services/cosmosdb/cosmosdb_service.py
+++ b/prowler/providers/azure/services/cosmosdb/cosmosdb_service.py
@@ -1,5 +1,5 @@
from dataclasses import dataclass
-from typing import List
+from typing import List, Optional
from azure.mgmt.cosmosdb import CosmosDBManagementClient
@@ -18,8 +18,13 @@ class CosmosDB(AzureService):
accounts = {}
for subscription, client in self.clients.items():
try:
- accounts_list = client.database_accounts.list()
accounts.update({subscription: []})
+ accounts_list = self.list_with_rg_scope(
+ subscription,
+ client.database_accounts.list,
+ client.database_accounts.list_by_resource_group,
+ )
+
for account in accounts_list:
accounts[subscription].append(
Account(
@@ -36,14 +41,29 @@ class CosmosDB(AzureService):
name=private_endpoint_connection.name,
type=private_endpoint_connection.type,
)
- for private_endpoint_connection in getattr(
- account, "private_endpoint_connections", []
+ for private_endpoint_connection in (
+ getattr(account, "private_endpoint_connections", [])
+ or []
)
if private_endpoint_connection
],
disable_local_auth=getattr(
account, "disable_local_auth", False
),
+ enable_automatic_failover=getattr(
+ account, "enable_automatic_failover", False
+ ),
+ backup_policy_type=getattr(
+ getattr(account, "backup_policy", None),
+ "type",
+ None,
+ ),
+ public_network_access=getattr(
+ account, "public_network_access", None
+ ),
+ minimal_tls_version=getattr(
+ account, "minimal_tls_version", None
+ ),
)
)
except Exception as error:
@@ -71,3 +91,7 @@ class Account:
location: str
private_endpoint_connections: List[PrivateEndpointConnection]
disable_local_auth: bool = False
+ enable_automatic_failover: bool = False
+ backup_policy_type: Optional[str] = None
+ public_network_access: Optional[str] = None
+ minimal_tls_version: Optional[str] = None
diff --git a/prowler/providers/azure/services/databricks/databricks_service.py b/prowler/providers/azure/services/databricks/databricks_service.py
index 7920500d88..128495a2c7 100644
--- a/prowler/providers/azure/services/databricks/databricks_service.py
+++ b/prowler/providers/azure/services/databricks/databricks_service.py
@@ -38,8 +38,13 @@ class Databricks(AzureService):
for subscription, client in self.clients.items():
try:
workspaces[subscription] = {}
+ workspaces_list = self.list_with_rg_scope(
+ subscription,
+ client.workspaces.list_by_subscription,
+ client.workspaces.list_by_resource_group,
+ )
- for workspace in client.workspaces.list_by_subscription():
+ for workspace in workspaces_list:
workspace_parameters = getattr(workspace, "parameters", None)
workspace_managed_disk_encryption = getattr(
getattr(
@@ -62,10 +67,21 @@ class Databricks(AzureService):
else:
managed_disk_encryption = None
+ enable_no_public_ip = getattr(
+ workspace_parameters, "enable_no_public_ip", None
+ )
workspaces[subscription][workspace.id] = DatabricksWorkspace(
id=workspace.id,
name=workspace.name,
location=workspace.location,
+ public_network_access=getattr(
+ workspace, "public_network_access", None
+ ),
+ no_public_ip_enabled=(
+ getattr(enable_no_public_ip, "value", None)
+ if enable_no_public_ip
+ else None
+ ),
custom_managed_vnet_id=(
getattr(
workspace_parameters, "custom_virtual_network_id", None
@@ -107,6 +123,8 @@ class DatabricksWorkspace(BaseModel):
id: The unique identifier of the workspace.
name: The name of the workspace.
location: The Azure region where the workspace is deployed.
+ public_network_access: Whether public network access is "Enabled" or "Disabled", if configured.
+ no_public_ip_enabled: Whether secure cluster connectivity (no public IP) is enabled. None when the workspace does not expose this classic-compute setting (e.g. serverless workspaces).
custom_managed_vnet_id: The ID of the custom managed virtual network, if configured.
managed_disk_encryption: The encryption settings for the workspace's managed disks.
"""
@@ -114,5 +132,7 @@ class DatabricksWorkspace(BaseModel):
id: str
name: str
location: str
+ public_network_access: Optional[str] = None
+ no_public_ip_enabled: Optional[bool] = None
custom_managed_vnet_id: Optional[str] = None
managed_disk_encryption: Optional[ManagedDiskEncryption] = None
diff --git a/tests/providers/alibabacloud/services/ram/ram_password_policy_uppercase/__init__.py b/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_password_policy_uppercase/__init__.py
rename to prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/__init__.py
diff --git a/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.metadata.json b/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.metadata.json
new file mode 100644
index 0000000000..4062199474
--- /dev/null
+++ b/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "databricks_workspace_no_public_ip_enabled",
+ "CheckTitle": "Databricks workspace has secure cluster connectivity (no public IP)",
+ "CheckType": [],
+ "ServiceName": "databricks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.databricks/workspaces",
+ "ResourceGroup": "ai_ml",
+ "Description": "**Azure Databricks workspaces** are evaluated for **secure cluster connectivity** (No Public IP / NPIP). When enabled, compute (cluster) nodes are deployed without public IP addresses and communicate with the control plane through a secure relay, reducing the workspace's exposure to the internet.",
+ "Risk": "Without **secure cluster connectivity**, Databricks compute nodes are assigned **public IP addresses** and are directly reachable from the internet. This enables **port scanning**, **lateral movement** from a compromised node, and **data exfiltration** that bypasses private-network controls.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/secure-cluster-connectivity",
+ "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/vnet-inject",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.databricks/workspaces"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az databricks workspace create --name <workspace_name> --resource-group <resource_group_name> --location <region> --sku premium --enable-no-public-ip",
+ "NativeIaC": "```bicep\n// Bicep: Deploy a Databricks workspace with secure cluster connectivity (No Public IP)\nresource workspace 'Microsoft.Databricks/workspaces@2023-02-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n sku: {\n name: 'premium'\n }\n properties: {\n managedResourceGroupId: '/subscriptions/<example_resource_id>/resourceGroups/<example_resource_name>'\n parameters: {\n enableNoPublicIp: {\n value: true // CRITICAL: Deploys cluster nodes without public IP addresses\n }\n }\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and start creating a new Azure Databricks workspace (No Public IP must be set at creation; it cannot be enabled on an existing workspace)\n2. On the Networking tab, set Deploy Azure Databricks workspace with Secure Cluster Connectivity (No Public IP) to Yes\n3. Complete the VNet injection configuration if required\n4. Review + create the workspace\n5. Migrate workloads to the new workspace and decommission the old one",
+ "Terraform": "```hcl\n# Terraform: Databricks workspace with secure cluster connectivity (No Public IP)\nresource \"azurerm_databricks_workspace\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n sku = \"premium\"\n\n custom_parameters {\n no_public_ip = true # CRITICAL: Deploys cluster nodes without public IP addresses\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Deploy Databricks workspaces with **secure cluster connectivity (No Public IP)** so compute nodes have no public IP addresses. Because this is set at creation, plan a migration for existing workspaces, and pair it with **VNet injection**, **private endpoints / disabled public network access**, and least-privilege NSG rules to uphold **defense in depth**.",
+ "Url": "https://hub.prowler.com/check/databricks_workspace_no_public_ip_enabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Secure cluster connectivity (No Public IP) applies to classic compute and is set at workspace creation. Serverless workspaces do not expose this setting (they have no customer-managed cluster nodes with public IPs) and are reported as MANUAL for verification."
+}
diff --git a/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.py b/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.py
new file mode 100644
index 0000000000..13b7742ffa
--- /dev/null
+++ b/prowler/providers/azure/services/databricks/databricks_workspace_no_public_ip_enabled/databricks_workspace_no_public_ip_enabled.py
@@ -0,0 +1,41 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.databricks.databricks_client import (
+ databricks_client,
+)
+
+
+class databricks_workspace_no_public_ip_enabled(Check):
+ """
+ Ensure Azure Databricks workspaces have secure cluster connectivity (no public IP) enabled.
+
+ This check evaluates whether each Azure Databricks workspace in the subscription is deployed with secure cluster connectivity (No Public IP / NPIP), so cluster nodes are not assigned public IP addresses.
+
+ Secure cluster connectivity is a classic-compute setting. Serverless workspaces do not expose it (they have no customer-managed cluster nodes with public IPs), so the workspace is reported as MANUAL for verification rather than failed.
+
+ - PASS: The workspace has secure cluster connectivity enabled (no_public_ip_enabled is True).
+ - FAIL: The workspace has secure cluster connectivity disabled (no_public_ip_enabled is False).
+ - MANUAL: The workspace does not expose the setting (no_public_ip_enabled is None, e.g. serverless workspaces).
+ """
+
+ def execute(self):
+ findings = []
+ for subscription, workspaces in databricks_client.workspaces.items():
+ subscription_name = databricks_client.subscriptions.get(
+ subscription, subscription
+ )
+ for workspace in workspaces.values():
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=workspace
+ )
+ report.subscription = subscription
+ if workspace.no_public_ip_enabled is None:
+ report.status = "MANUAL"
+ report.status_extended = f"Databricks workspace {workspace.name} in subscription {subscription_name} ({subscription}) does not expose secure cluster connectivity (no public IP) settings (for example, serverless workspaces have no public-IP cluster nodes); verify the network configuration manually."
+ elif workspace.no_public_ip_enabled:
+ report.status = "PASS"
+ report.status_extended = f"Databricks workspace {workspace.name} in subscription {subscription_name} ({subscription}) has secure cluster connectivity (no public IP) enabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Databricks workspace {workspace.name} in subscription {subscription_name} ({subscription}) does not have secure cluster connectivity (no public IP) enabled."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/ram/ram_rotate_access_key_90_days/__init__.py b/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/ram/ram_rotate_access_key_90_days/__init__.py
rename to prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/__init__.py
diff --git a/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.metadata.json b/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.metadata.json
new file mode 100644
index 0000000000..cb92d6df0f
--- /dev/null
+++ b/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "azure",
+ "CheckID": "databricks_workspace_public_network_access_disabled",
+ "CheckTitle": "Databricks workspace has public network access disabled",
+ "CheckType": [],
+ "ServiceName": "databricks",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.databricks/workspaces",
+ "ResourceGroup": "ai_ml",
+ "Description": "**Azure Databricks workspaces** are evaluated for **public network access**. Disabling public network access ensures the workspace is only reachable through **private endpoints**, reducing the attack surface and preventing direct exposure of the control plane and data plane to the internet.",
+ "Risk": "Allowing **public network access** exposes the Databricks workspace control plane and data plane to the internet. Combined with leaked **credentials**, **personal access tokens**, or unpatched vulnerabilities, this enables **unauthorized access**, **brute force**, and **data exfiltration** from any source on the internet.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/private-link",
+ "https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/private-link#step-4-disable-public-network-access",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.databricks/workspaces"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az databricks workspace update --name <workspace_name> --resource-group <resource_group_name> --public-network-access Disabled",
+ "NativeIaC": "```bicep\n// Bicep: Disable public network access on a Databricks workspace\nresource workspace 'Microsoft.Databricks/workspaces@2023-02-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n sku: {\n name: 'premium'\n }\n properties: {\n managedResourceGroupId: '/subscriptions/<example_resource_id>/resourceGroups/<example_resource_name>'\n publicNetworkAccess: 'Disabled' // CRITICAL: Blocks all public-internet traffic to the workspace\n }\n}\n```",
+ "Other": "1. Sign in to the Azure portal and open your Databricks workspace\n2. In the left menu, select Networking\n3. Under Public network access, select Disabled\n4. Configure Azure Private Link private endpoints before saving so clients retain connectivity\n5. Click Save",
+ "Terraform": "```hcl\n# Terraform: Disable public network access on a Databricks workspace\nresource \"azurerm_databricks_workspace\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n sku = \"premium\"\n\n public_network_access_enabled = false # CRITICAL: Blocks all public-internet traffic to the workspace\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Disable **public network access** on Databricks workspaces and require connectivity via **Azure Private Link** private endpoints. Before enforcement, validate that all application workloads have private-network connectivity, and pair this control with **VNet injection**, **secure cluster connectivity (no public IP)**, and least-privilege access to uphold **defense in depth**.",
+ "Url": "https://hub.prowler.com/check/databricks_workspace_public_network_access_disabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.py b/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.py
new file mode 100644
index 0000000000..e8193cedb6
--- /dev/null
+++ b/prowler/providers/azure/services/databricks/databricks_workspace_public_network_access_disabled/databricks_workspace_public_network_access_disabled.py
@@ -0,0 +1,35 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.databricks.databricks_client import (
+ databricks_client,
+)
+
+
+class databricks_workspace_public_network_access_disabled(Check):
+ """
+ Ensure Azure Databricks workspaces have public network access disabled.
+
+ This check evaluates whether each Azure Databricks workspace in the subscription restricts connectivity to private endpoints by disabling public network access.
+
+ - PASS: The workspace has public network access disabled (public_network_access is "Disabled").
+ - FAIL: The workspace has public network access enabled (or the value is not set).
+ """
+
+ def execute(self):
+ findings = []
+ for subscription, workspaces in databricks_client.workspaces.items():
+ subscription_name = databricks_client.subscriptions.get(
+ subscription, subscription
+ )
+ for workspace in workspaces.values():
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=workspace
+ )
+ report.subscription = subscription
+ if workspace.public_network_access == "Disabled":
+ report.status = "PASS"
+ report.status_extended = f"Databricks workspace {workspace.name} in subscription {subscription_name} ({subscription}) has public network access disabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Databricks workspace {workspace.name} in subscription {subscription_name} ({subscription}) has public network access enabled."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/rds/__init__.py b/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/__init__.py
rename to prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/__init__.py
diff --git a/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.metadata.json b/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.metadata.json
new file mode 100644
index 0000000000..cae92490af
--- /dev/null
+++ b/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "defender_ensure_defender_cspm_is_on",
+ "CheckTitle": "Microsoft Defender CSPM is set to On",
+ "CheckType": [],
+ "ServiceName": "defender",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.security/pricings",
+ "ResourceGroup": "security",
+ "Description": "**Microsoft Defender for Cloud** Cloud Security Posture Management (CSPM) plan is evaluated for **standard tier** activation. Defender CSPM provides advanced posture management capabilities including attack path analysis, cloud security explorer, agentless scanning, and governance rules.",
+ "Risk": "Without Defender CSPM, the subscription relies on **foundational CSPM** (free tier) which lacks attack path analysis, agentless vulnerability scanning, and security governance. Advanced threats exploiting misconfiguration chains go undetected.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/defender-for-cloud/concept-cloud-security-posture-management",
+ "https://learn.microsoft.com/en-us/azure/defender-for-cloud/enable-enhanced-security"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az security pricing create -n CloudPosture --tier Standard",
+ "NativeIaC": "```bicep\ntargetScope = 'subscription'\n\nresource defenderCSPM 'Microsoft.Security/pricings@2024-01-01' = {\n name: 'CloudPosture'\n properties: {\n pricingTier: 'Standard' // Critical: enables Defender CSPM\n }\n}\n```",
+ "Other": "1. Sign in to Azure portal\n2. Go to Microsoft Defender for Cloud\n3. Select Environment Settings\n4. Click on the subscription\n5. Set Cloud Security Posture Management (CSPM) to On\n6. Click Save",
+ "Terraform": "```hcl\nresource \"azurerm_security_center_subscription_pricing\" \"<example_resource_name>\" {\n tier = \"Standard\" # Critical: enables Defender CSPM\n resource_type = \"CloudPosture\"\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **Defender CSPM** standard tier for advanced cloud security posture management. Evaluate the cost against the security benefits \u2014 CSPM provides attack path analysis and agentless scanning.",
+ "Url": "https://hub.prowler.com/check/defender_ensure_defender_cspm_is_on"
+ }
+ },
+ "Categories": [
+ "threat-detection"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.py b/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.py
new file mode 100644
index 0000000000..cf7957400c
--- /dev/null
+++ b/prowler/providers/azure/services/defender/defender_ensure_defender_cspm_is_on/defender_ensure_defender_cspm_is_on.py
@@ -0,0 +1,35 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.defender.defender_client import defender_client
+
+
+class defender_ensure_defender_cspm_is_on(Check):
+ """
+ Ensure Microsoft Defender Cloud Security Posture Management (CSPM) is set to On.
+
+ This check evaluates whether the Defender CSPM plan (CloudPosture pricing) is enabled with the Standard tier for each subscription.
+
+ - PASS: The CloudPosture pricing tier is "Standard" (Defender CSPM is on).
+ - FAIL: The CloudPosture pricing tier is not "Standard" (Defender CSPM is off).
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+ for subscription, pricings in defender_client.pricings.items():
+ subscription_name = defender_client.subscriptions.get(
+ subscription, subscription
+ )
+ if "CloudPosture" in pricings:
+ report = Check_Report_Azure(
+ metadata=self.metadata(),
+ resource=pricings["CloudPosture"],
+ )
+ report.subscription = subscription
+ report.resource_name = "Defender plan CSPM"
+ report.status = "PASS"
+ report.status_extended = f"Defender plan CSPM from subscription {subscription_name} ({subscription}) is set to ON (pricing tier standard)."
+ if pricings["CloudPosture"].pricing_tier != "Standard":
+ report.status = "FAIL"
+ report.status_extended = f"Defender plan CSPM from subscription {subscription_name} ({subscription}) is set to OFF (pricing tier not standard)."
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/azure/services/defender/defender_service.py b/prowler/providers/azure/services/defender/defender_service.py
index 7da96cd8ec..d68d88dc22 100644
--- a/prowler/providers/azure/services/defender/defender_service.py
+++ b/prowler/providers/azure/services/defender/defender_service.py
@@ -230,10 +230,12 @@ class Defender(AzureService):
iot_security_solutions = {}
for subscription_id, client in self.clients.items():
try:
- iot_security_solutions_list = (
- client.iot_security_solution.list_by_subscription()
- )
iot_security_solutions.update({subscription_id: {}})
+ iot_security_solutions_list = self.list_with_rg_scope(
+ subscription_id,
+ client.iot_security_solution.list_by_subscription,
+ client.iot_security_solution.list_by_resource_group,
+ )
for iot_security_solution in iot_security_solutions_list:
iot_security_solutions[subscription_id].update(
{
@@ -267,8 +269,13 @@ class Defender(AzureService):
for subscription_id, client in self.clients.items():
try:
jit_policies[subscription_id] = {}
- policies = client.jit_network_access_policies.list()
- for policy in policies:
+ policies_list = self.list_with_rg_scope(
+ subscription_id,
+ client.jit_network_access_policies.list,
+ client.jit_network_access_policies.list_by_resource_group,
+ )
+
+ for policy in policies_list:
vm_ids = set()
for vm in getattr(policy, "virtual_machines", []):
vm_ids.add(vm.id)
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_postgresql_log_connections_enabled/__init__.py b/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_postgresql_log_connections_enabled/__init__.py
rename to prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/__init__.py
diff --git a/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.metadata.json b/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.metadata.json
new file mode 100644
index 0000000000..c786fd49af
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "entra_app_registration_credential_not_expired",
+ "CheckTitle": "App registration credentials are not expired or expiring soon",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Microsoft Entra ID** app registrations are evaluated for **credential validity**. Each app's password secrets and certificate credentials are checked for expiration. Credentials that are already expired, expiring within 30 days, or have no expiration date are flagged.",
+ "Risk": "Expired credentials cause **service outages** when apps can no longer authenticate. Credentials without expiration violate **least privilege** by persisting indefinitely. Long-lived or leaked secrets enable **unauthorized API access**, **data exfiltration**, and **lateral movement** via the app's permissions.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal",
+ "https://learn.microsoft.com/en-us/graph/api/resources/application"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az ad app credential reset --id <app_id> --years 1",
+ "NativeIaC": "",
+ "Other": "1. Sign in to Microsoft Entra admin center\n2. Go to Identity > Applications > App registrations\n3. Select the application with the expiring credential\n4. Go to Certificates & secrets\n5. Delete the expired credential\n6. Add a new credential with an appropriate expiration (recommended: 6-12 months)\n7. Update the consuming application with the new credential\n8. Consider migrating to managed identities or federated credentials where possible",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Rotate app registration credentials before expiration. Set expiration to 6-12 months maximum. Prefer **managed identities** or **federated credentials** over secrets. Monitor credential expiry with Azure Monitor alerts or Microsoft Entra workbooks.",
+ "Url": "https://hub.prowler.com/check/entra_app_registration_credential_not_expired"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check evaluates both password secrets and certificate credentials. Each credential is reported individually. Apps with no credentials are skipped."
+}
diff --git a/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.py b/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.py
new file mode 100644
index 0000000000..5cbdf009a0
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_app_registration_credential_not_expired/entra_app_registration_credential_not_expired.py
@@ -0,0 +1,72 @@
+from datetime import datetime, timezone
+
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.entra.entra_client import entra_client
+
+EXPIRY_WARNING_DAYS = 30
+
+
+class entra_app_registration_credential_not_expired(Check):
+ """
+ Ensure Microsoft Entra ID app registration credentials are not expired or expiring soon.
+
+ This check evaluates each app registration's password secrets and certificate credentials. A credential is reported individually and flagged when it is already expired, expiring within 30 days, or has no expiration date. Apps with no credentials are skipped.
+
+ - PASS: The credential is valid for more than 30 days.
+ - FAIL: The credential is expired, expiring within 30 days, or has no expiration date.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+
+ for tenant_domain, apps in entra_client.app_registrations.items():
+ for app_id, app in apps.items():
+ if not app.credentials:
+ continue
+
+ for credential in app.credentials:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=app)
+ report.subscription = f"Tenant: {tenant_domain}"
+ report.resource_name = (
+ f"{app.name} ({credential.credential_type}: "
+ f"{credential.display_name or 'unnamed'})"
+ )
+
+ if credential.end_date_time is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"App '{app.name}' has a {credential.credential_type} "
+ f"credential with no expiration date."
+ )
+ else:
+ now = datetime.now(timezone.utc)
+ end = credential.end_date_time
+ if end.tzinfo is None:
+ end = end.replace(tzinfo=timezone.utc)
+ if end <= now:
+ days_ago = (now - end).days
+ report.status = "FAIL"
+ report.status_extended = (
+ f"App '{app.name}' has a {credential.credential_type} "
+ f"credential that expired {days_ago} days ago."
+ )
+ elif (end - now).days <= EXPIRY_WARNING_DAYS:
+ days_left = (end - now).days
+ report.status = "FAIL"
+ report.status_extended = (
+ f"App '{app.name}' has a {credential.credential_type} "
+ f"credential expiring in {days_left} days (within the "
+ f"{EXPIRY_WARNING_DAYS}-day rotation threshold); rotate it soon."
+ )
+ else:
+ days_left = (end - now).days
+ report.status = "PASS"
+ report.status_extended = (
+ f"App '{app.name}' has a {credential.credential_type} "
+ f"credential valid for {days_left} more days (beyond the "
+ f"{EXPIRY_WARNING_DAYS}-day rotation threshold)."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_sql_audit_enabled/__init__.py b/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_sql_audit_enabled/__init__.py
rename to prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/__init__.py
diff --git a/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.metadata.json b/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.metadata.json
new file mode 100644
index 0000000000..11dfa6e85b
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "entra_authentication_methods_policy_strong_auth_enforced",
+ "CheckTitle": "Strong authentication methods are enabled with registration enforcement",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Microsoft Entra ID** authentication methods policy is evaluated for **strong authentication enforcement**. The check verifies that at least one strong method (Microsoft Authenticator, FIDO2, or X.509 Certificate) is enabled and that the MFA registration campaign is active to prompt users to enroll.",
+ "Risk": "Without strong authentication methods, the tenant relies on **passwords alone** or weak factors like SMS/voice. Password-only authentication enables **credential stuffing**, **phishing**, and **brute force** attacks. Without registration enforcement, users may never enroll in MFA even when it is available.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods-manage",
+ "https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-nudge-authenticator-app"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to Microsoft Entra admin center\n2. Go to Protection > Authentication methods > Policies\n3. Enable Microsoft Authenticator and/or FIDO2 security keys\n4. Go to Protection > Authentication methods > Registration campaign\n5. Set State to Enabled\n6. Configure included users/groups\n7. Consider disabling weak methods (SMS, Voice) after users migrate",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **Microsoft Authenticator** and **FIDO2 security keys** as authentication methods. Activate the **MFA registration campaign** to prompt users to register. Disable weak methods (SMS, voice) after migration. Use **Conditional Access** to require strong authentication for all users.",
+ "Url": "https://hub.prowler.com/check/entra_authentication_methods_policy_strong_auth_enforced"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check reports a single finding per tenant and passes only when both the MFA registration campaign is enabled and at least one strong method is enabled. Microsoft recommends phishing-resistant methods (FIDO2, certificate-based) over app-based push notifications."
+}
diff --git a/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.py b/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.py
new file mode 100644
index 0000000000..efdbcfa6a0
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_authentication_methods_policy_strong_auth_enforced/entra_authentication_methods_policy_strong_auth_enforced.py
@@ -0,0 +1,63 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.entra.entra_client import entra_client
+
+# Methods considered strong (phishing-resistant or app-based MFA)
+STRONG_METHODS = {"microsoftAuthenticator", "fido2", "x509Certificate"}
+
+
+class entra_authentication_methods_policy_strong_auth_enforced(Check):
+ """
+ Ensure the Entra ID authentication methods policy enforces strong authentication.
+
+ This check evaluates the tenant authentication methods policy and reports a single finding per tenant. Strong authentication is considered enforced only when BOTH conditions hold:
+ 1. The MFA registration campaign is enabled (users are prompted to register methods).
+ 2. At least one strong, phishing-resistant or app-based method (Microsoft Authenticator, FIDO2, or X.509 certificate) is enabled.
+
+ - PASS: Both conditions hold.
+ - FAIL: One or both conditions are missing; the status extended names exactly what is missing.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+
+ for tenant_domain, policy in entra_client.authentication_methods_policy.items():
+ if policy is None:
+ continue
+
+ report = Check_Report_Azure(metadata=self.metadata(), resource=policy)
+ report.subscription = f"Tenant: {tenant_domain}"
+ report.resource_name = "Authentication Methods Policy"
+ report.resource_id = policy.id
+
+ registration_enabled = policy.registration_enforcement_state == "enabled"
+ enabled_strong = [
+ config.method_name
+ for config in policy.method_configurations
+ if config.state == "enabled" and config.method_name in STRONG_METHODS
+ ]
+
+ if registration_enabled and enabled_strong:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Strong authentication is enforced for tenant {tenant_domain}: "
+ f"the MFA registration campaign is enabled and strong methods are "
+ f"enabled ({', '.join(enabled_strong)})."
+ )
+ else:
+ issues = []
+ if not registration_enabled:
+ issues.append("the MFA registration campaign is not enabled")
+ if not enabled_strong:
+ issues.append(
+ "no strong authentication methods (Microsoft Authenticator, "
+ "FIDO2, or X.509 Certificate) are enabled"
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Strong authentication is not enforced for tenant "
+ f"{tenant_domain}: {'; '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/entra/entra_service.py b/prowler/providers/azure/services/entra/entra_service.py
index eb1d62ac11..e23f3cd34a 100644
--- a/prowler/providers/azure/services/entra/entra_service.py
+++ b/prowler/providers/azure/services/entra/entra_service.py
@@ -1,5 +1,6 @@
import asyncio
from asyncio import gather
+from datetime import datetime
from typing import List, Optional
from uuid import UUID
@@ -49,6 +50,8 @@ class Entra(AzureService):
self._get_named_locations(),
self._get_directory_roles(),
self._get_conditional_access_policy(),
+ self._get_app_registrations(),
+ self._get_authentication_methods_policy(),
)
)
@@ -58,6 +61,8 @@ class Entra(AzureService):
self.named_locations = attributes[3]
self.directory_roles = attributes[4]
self.conditional_access_policy = attributes[5]
+ self.app_registrations = attributes[6]
+ self.authentication_methods_policy = attributes[7]
if created_loop:
asyncio.set_event_loop(None)
@@ -69,7 +74,12 @@ class Entra(AzureService):
try:
request_configuration = RequestConfiguration(
query_parameters=UsersRequestBuilder.UsersRequestBuilderGetQueryParameters(
- select=["id", "displayName", "accountEnabled"]
+ select=[
+ "id",
+ "displayName",
+ "accountEnabled",
+ "signInActivity",
+ ]
)
)
for tenant, client in self.clients.items():
@@ -82,6 +92,16 @@ class Entra(AzureService):
try:
while users_response:
for user in getattr(users_response, "value", []) or []:
+ sign_in_activity = getattr(user, "sign_in_activity", None)
+ last_sign_in = (
+ getattr(
+ sign_in_activity,
+ "last_sign_in_date_time",
+ None,
+ )
+ if sign_in_activity
+ else None
+ )
users[tenant].update(
{
user.id: User(
@@ -93,6 +113,7 @@ class Entra(AzureService):
account_enabled=getattr(
user, "account_enabled", True
),
+ last_sign_in=last_sign_in,
)
}
)
@@ -416,12 +437,142 @@ class Entra(AzureService):
return conditional_access_policy
+ async def _get_app_registrations(self):
+ logger.info("Entra - Getting app registrations...")
+ app_registrations = {}
+ try:
+ for tenant, client in self.clients.items():
+ app_registrations[tenant] = {}
+ apps_response = await client.applications.get()
+
+ try:
+ while apps_response:
+ for app in getattr(apps_response, "value", []) or []:
+ credentials = []
+ for cred in getattr(app, "password_credentials", []) or []:
+ credentials.append(
+ AppCredential(
+ display_name=getattr(cred, "display_name", "")
+ or "",
+ credential_type="password",
+ end_date_time=getattr(
+ cred, "end_date_time", None
+ ),
+ )
+ )
+ for cred in getattr(app, "key_credentials", []) or []:
+ credentials.append(
+ AppCredential(
+ display_name=getattr(cred, "display_name", "")
+ or "",
+ credential_type="certificate",
+ end_date_time=getattr(
+ cred, "end_date_time", None
+ ),
+ )
+ )
+ app_registrations[tenant][app.id] = AppRegistration(
+ id=app.id,
+ name=getattr(app, "display_name", "") or "",
+ credentials=credentials,
+ )
+
+ next_link = getattr(apps_response, "odata_next_link", None)
+ if not next_link:
+ break
+ apps_response = await client.applications.with_url(
+ next_link
+ ).get()
+
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ return app_registrations
+
+ async def _get_authentication_methods_policy(self):
+ logger.info("Entra - Getting authentication methods policy...")
+ auth_methods_policy = {}
+ try:
+ for tenant, client in self.clients.items():
+ policy_response = (
+ await client.policies.authentication_methods_policy.get()
+ )
+
+ if not policy_response:
+ auth_methods_policy[tenant] = None
+ continue
+
+ # Parse registration enforcement
+ reg_enforcement = getattr(
+ policy_response, "registration_enforcement", None
+ )
+ reg_campaign = (
+ getattr(
+ reg_enforcement,
+ "authentication_methods_registration_campaign",
+ None,
+ )
+ if reg_enforcement
+ else None
+ )
+ registration_enforcement_state = (
+ getattr(reg_campaign, "state", None) if reg_campaign else None
+ )
+
+ # Parse authentication method configurations
+ method_configs = []
+ for config in (
+ getattr(
+ policy_response,
+ "authentication_method_configurations",
+ [],
+ )
+ or []
+ ):
+ odata_type = getattr(config, "odata_type", "") or ""
+ # Extract method name from odata_type
+ # e.g. "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration"
+ method_name = (
+ odata_type.split(".")[-1].replace(
+ "AuthenticationMethodConfiguration", ""
+ )
+ if odata_type
+ else getattr(config, "id", "unknown")
+ )
+ method_configs.append(
+ AuthMethodConfig(
+ id=getattr(config, "id", "") or "",
+ method_name=method_name,
+ state=getattr(config, "state", "disabled") or "disabled",
+ )
+ )
+
+ auth_methods_policy[tenant] = AuthMethodsPolicy(
+ id=getattr(policy_response, "id", "") or "",
+ registration_enforcement_state=registration_enforcement_state,
+ method_configurations=method_configs,
+ )
+
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ return auth_methods_policy
+
class User(BaseModel):
id: str
name: str
is_mfa_capable: bool = False
account_enabled: bool = True
+ last_sign_in: Optional[datetime] = None
class DefaultUserRolePermissions(BaseModel):
@@ -481,3 +632,27 @@ class ConditionalAccessPolicy(BaseModel):
users: dict[str, List[str]]
target_resources: dict[str, List[str]]
access_controls: dict[str, List[str]]
+
+
+class AppCredential(BaseModel):
+ display_name: str = ""
+ credential_type: str # "password" or "certificate"
+ end_date_time: Optional[datetime] = None
+
+
+class AppRegistration(BaseModel):
+ id: str
+ name: str
+ credentials: List[AppCredential] = []
+
+
+class AuthMethodConfig(BaseModel):
+ id: str = ""
+ method_name: str
+ state: str = "disabled" # "enabled" or "disabled"
+
+
+class AuthMethodsPolicy(BaseModel):
+ id: str = ""
+ registration_enforcement_state: Optional[str] = None # "enabled" or "disabled"
+ method_configurations: List[AuthMethodConfig] = []
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_sql_audit_retention/__init__.py b/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_sql_audit_retention/__init__.py
rename to prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/__init__.py
diff --git a/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.metadata.json b/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.metadata.json
new file mode 100644
index 0000000000..64ccb383a1
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "entra_user_with_recent_sign_in",
+ "CheckTitle": "Enabled user has signed in within the last 90 days",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Microsoft Entra ID** enabled user accounts are evaluated for **recent sign-in activity**. Accounts that have not signed in for more than 90 days are flagged as stale. Stale accounts indicate orphaned identities that may have been abandoned after personnel changes, project completions, or role transitions without proper deprovisioning.",
+ "Risk": "Stale accounts retain **role assignments** and **group memberships**. Attackers target dormant accounts via **credential stuffing** and **password spraying** because owners are unlikely to notice anomalous activity. Compromise enables **lateral movement**, **data exfiltration**, and **persistence** while evading detection tuned to active users.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/resources/signinactivity",
+ "https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-sign-ins"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az rest --method patch --url https://graph.microsoft.com/v1.0/users/<user_id> --body '{\"accountEnabled\":false}'",
+ "NativeIaC": "",
+ "Other": "1. Sign in to Microsoft Entra admin center\n2. Go to Identity > Users > All users\n3. Add filter: Sign-in activity > Last interactive sign-in date is before <90 days ago>\n4. Review each stale account with the account owner or manager\n5. Disable accounts confirmed as no longer needed\n6. After a grace period, delete disabled accounts\n7. Establish a recurring access review to automate this process",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Implement **automated access reviews** in Entra ID to periodically review and remove stale accounts. Configure reviews to run quarterly, targeting all users or specific groups. Set auto-apply to disable accounts that are not confirmed by reviewers. For immediate remediation, filter users by last sign-in date and disable accounts inactive for more than 90 days after confirming with managers.",
+ "Url": "https://hub.prowler.com/check/entra_user_with_recent_sign_in"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "The signInActivity resource requires Microsoft Entra ID P1 or P2 license. Tenants without this license will not have sign-in activity data available, and all users will be reported as never having signed in."
+}
diff --git a/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.py b/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.py
new file mode 100644
index 0000000000..fa6d1af05d
--- /dev/null
+++ b/prowler/providers/azure/services/entra/entra_user_with_recent_sign_in/entra_user_with_recent_sign_in.py
@@ -0,0 +1,77 @@
+from datetime import datetime, timezone
+
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.entra.entra_client import entra_client
+
+STALE_THRESHOLD_DAYS = 90
+
+
+class entra_user_with_recent_sign_in(Check):
+ """
+ Ensure enabled Entra ID users have signed in within the last 90 days.
+
+ This check evaluates each enabled user's last interactive sign-in to detect stale or dormant accounts that should be reviewed or deprovisioned. Sign-in activity requires Entra ID P1/P2 licensing.
+
+ - PASS: The enabled user signed in within the last 90 days.
+ - FAIL: The enabled user has not signed in for more than 90 days, or has never signed in.
+ - FAIL (tenant-level): No sign-in activity data is available for any enabled user, indicating missing P1/P2 licensing or Graph permissions (reported once instead of flagging every user).
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+
+ for tenant_domain, users in entra_client.users.items():
+ enabled_users = {k: v for k, v in users.items() if v.account_enabled}
+
+ if not enabled_users:
+ continue
+
+ # If all enabled users are missing sign-in data, avoid claiming
+ # they never signed in. This usually indicates missing telemetry,
+ # often due to licensing or Graph permission limitations.
+ all_null = all(u.last_sign_in is None for u in enabled_users.values())
+ if all_null:
+ first_user = next(iter(enabled_users.values()))
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=first_user
+ )
+ report.subscription = f"Tenant: {tenant_domain}"
+ report.resource_name = "Sign-in Activity Data"
+ count = len(enabled_users)
+ noun = "user" if count == 1 else "users"
+ report.status = "FAIL"
+ report.status_extended = (
+ f"No sign-in activity data available for any of the "
+ f"{count} enabled {noun}. This likely means the tenant "
+ f"is missing Entra ID P1/P2 licensing or the required "
+ f"Graph permissions to read sign-in activity."
+ )
+ findings.append(report)
+ continue
+
+ for user_domain_name, user in enabled_users.items():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=user)
+ report.subscription = f"Tenant: {tenant_domain}"
+
+ if user.last_sign_in is None:
+ report.status = "FAIL"
+ report.status_extended = f"User {user.name} has never signed in."
+ else:
+ last = user.last_sign_in
+ if last.tzinfo is None:
+ last = last.replace(tzinfo=timezone.utc)
+ days_since = (datetime.now(timezone.utc) - last).days
+ if days_since > STALE_THRESHOLD_DAYS:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"User {user.name} has not signed in for {days_since} days."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"User {user.name} signed in {days_since} days ago."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.metadata.json b/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.metadata.json
index 164a43b5da..241c95ec7f 100644
--- a/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.metadata.json
+++ b/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.metadata.json
@@ -9,7 +9,7 @@
"Severity": "high",
"ResourceType": "microsoft.keyvault/vaults",
"ResourceGroup": "security",
- "Description": "**Azure Key Vault** diagnostic settings capture **audit logs** (`AuditEvent`) when category groups `audit` and `allLogs` are enabled and routed to a supported destination. Logged events include management and data-plane operations on vaults, keys, secrets, and certificates.",
+ "Description": "**Azure Key Vault** diagnostic settings capture **audit logs** (`AuditEvent`) when the `AuditEvent` category is enabled, or when category groups `audit` and `allLogs` are enabled, and routed to a supported destination. Logged events include management and data-plane operations on vaults, keys, secrets, and certificates.",
"Risk": "Without **Key Vault audit logging**, access and changes to keys, secrets, and certificates are untracked.\n\nAttackers can misuse keys to decrypt data, alter or delete crypto material, and evade detection-eroding **confidentiality** and **integrity** and delaying **incident response**.",
"RelatedUrl": "",
"AdditionalURLs": [
@@ -20,13 +20,13 @@
],
"Remediation": {
"Code": {
- "CLI": "az monitor diagnostic-settings create --name <example_resource_name> --resource <example_resource_id> --workspace <example_resource_id> --logs '[{\"categoryGroup\":\"audit\",\"enabled\":true},{\"categoryGroup\":\"allLogs\",\"enabled\":true}]'",
- "NativeIaC": "```bicep\n// Enable Key Vault diagnostic settings with audit + allLogs\nparam keyVaultName string\nparam workspaceId string\n\nresource kv 'Microsoft.KeyVault/vaults@2023-07-01' existing = {\n name: keyVaultName\n}\n\nresource diag 'Microsoft.Insights/diagnosticSettings@2021-05-01-preview' = {\n name: '<example_resource_name>'\n scope: kv\n properties: {\n workspaceId: workspaceId\n logs: [\n {\n categoryGroup: 'audit' // critical: enables audit logs\n enabled: true // required to pass the check\n }\n {\n categoryGroup: 'allLogs' // critical: enables allLogs group\n enabled: true // required to pass the check\n }\n ]\n }\n}\n```",
- "Other": "1. In Azure Portal, go to your Key Vault > Monitoring > Diagnostic settings\n2. Click Add diagnostic setting\n3. Under Category groups, select audit and allLogs\n4. Choose a destination (e.g., Send to Log Analytics workspace) and select the workspace\n5. Click Save",
- "Terraform": "```hcl\n# Enable diagnostic settings on Key Vault with audit + allLogs\nresource \"azurerm_monitor_diagnostic_setting\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n target_resource_id = \"<example_resource_id>\" # Key Vault resource ID\n log_analytics_workspace_id = \"<example_resource_id>\" # Destination workspace ID\n\n enabled_log { # critical: audit category group\n category_group = \"audit\" # enables audit logs\n }\n enabled_log { # critical: allLogs category group\n category_group = \"allLogs\" # enables all logs\n }\n}\n```"
+ "CLI": "az monitor diagnostic-settings create --name <example_resource_name> --resource <example_resource_id> --workspace <example_resource_id> --logs '[{\"category\":\"AuditEvent\",\"enabled\":true}]'",
+ "NativeIaC": "```bicep\n// Enable Key Vault AuditEvent diagnostic logs\nparam keyVaultName string\nparam workspaceId string\n\nresource kv 'Microsoft.KeyVault/vaults@2023-07-01' existing = {\n name: keyVaultName\n}\n\nresource diag 'Microsoft.Insights/diagnosticSettings@2021-05-01-preview' = {\n name: '<example_resource_name>'\n scope: kv\n properties: {\n workspaceId: workspaceId\n logs: [\n {\n category: 'AuditEvent'\n enabled: true\n }\n ]\n }\n}\n```",
+ "Other": "1. In Azure Portal, go to your Key Vault > Monitoring > Diagnostic settings\n2. Click Add diagnostic setting\n3. Enable AuditEvent audit logs, or select the audit and allLogs category groups\n4. Choose a destination (e.g., Send to Log Analytics workspace) and select the workspace\n5. Click Save",
+ "Terraform": "```hcl\n# Enable AuditEvent diagnostic logs on Key Vault\nresource \"azurerm_monitor_diagnostic_setting\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n target_resource_id = \"<example_resource_id>\"\n log_analytics_workspace_id = \"<example_resource_id>\"\n\n enabled_log {\n category = \"AuditEvent\"\n }\n}\n```"
},
"Recommendation": {
- "Text": "Enable **diagnostic settings** to collect `AuditEvent` logs-covering category groups `audit` and `allLogs`-and send them to a central sink. Apply **least privilege** to log access, enforce secure **retention/immutability**, monitor with alerts for anomalous operations, and use **separation of duties** to prevent logging bypass.",
+ "Text": "Enable **diagnostic settings** to collect `AuditEvent` logs and send them to a central sink. Apply **least privilege** to log access, enforce secure **retention/immutability**, monitor with alerts for anomalous operations, and use **separation of duties** to prevent logging bypass.",
"Url": "https://hub.prowler.com/check/keyvault_logging_enabled"
}
},
diff --git a/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.py b/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.py
index 68ef149cd7..ea80b920c5 100644
--- a/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.py
+++ b/prowler/providers/azure/services/keyvault/keyvault_logging_enabled/keyvault_logging_enabled.py
@@ -16,14 +16,17 @@ class keyvault_logging_enabled(Check):
report.status = "FAIL"
report.status_extended = f"Key Vault {keyvault.name} in subscription {subscription_name} ({subscription_id}) does not have a diagnostic setting with audit logging."
for diagnostic_setting in keyvault.monitor_diagnostic_settings or []:
- has_audit = False
+ has_audit_category = False
+ has_audit_group = False
has_all_logs = False
for log in diagnostic_setting.logs:
+ if log.category == "AuditEvent" and log.enabled:
+ has_audit_category = True
if log.category_group == "audit" and log.enabled:
- has_audit = True
+ has_audit_group = True
if log.category_group == "allLogs" and log.enabled:
has_all_logs = True
- if has_audit and has_all_logs:
+ if has_audit_category or (has_audit_group and has_all_logs):
report.status = "PASS"
report.status_extended = f"Key Vault {keyvault.name} in subscription {subscription_name} ({subscription_id}) has a diagnostic setting with audit logging."
break
diff --git a/prowler/providers/azure/services/keyvault/keyvault_service.py b/prowler/providers/azure/services/keyvault/keyvault_service.py
index 9fb3fd98af..e5b2e76427 100644
--- a/prowler/providers/azure/services/keyvault/keyvault_service.py
+++ b/prowler/providers/azure/services/keyvault/keyvault_service.py
@@ -35,7 +35,11 @@ class KeyVault(AzureService):
for subscription, client in self.clients.items():
try:
key_vaults[subscription] = []
- vaults_list = list(client.vaults.list_by_subscription())
+ vaults_list = self.list_with_rg_scope(
+ subscription,
+ client.vaults.list_by_subscription,
+ client.vaults.list_by_resource_group,
+ )
if not vaults_list:
continue
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_ssl_enabled/__init__.py b/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_ssl_enabled/__init__.py
rename to prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/__init__.py
diff --git a/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.metadata.json b/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.metadata.json
new file mode 100644
index 0000000000..1dac541283
--- /dev/null
+++ b/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "mysql_flexible_server_geo_redundant_backup_enabled",
+ "CheckTitle": "MySQL flexible server has geo-redundant backup enabled",
+ "CheckType": [],
+ "ServiceName": "mysql",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.dbformysql/flexibleservers",
+ "ResourceGroup": "database",
+ "Description": "**Azure MySQL Flexible Server** is evaluated for **geo-redundant backup**. Geo-redundant backup stores backup copies in a paired Azure region, enabling restore and recovery from a full regional outage.",
+ "Risk": "Without **geo-redundant backup**, a regional disaster can cause **permanent data loss**. Locally redundant backups only protect against storage hardware failures within the same region and cannot be restored if the primary region becomes unavailable.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-backup-restore",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.dbformysql/flexibleservers"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az mysql flexible-server create --name <server_name> --resource-group <resource_group_name> --location <region> --geo-redundant-backup Enabled",
+ "NativeIaC": "```bicep\n// Bicep: MySQL Flexible Server with geo-redundant backup (set at creation)\nresource mysql 'Microsoft.DBforMySQL/flexibleServers@2023-12-30' = {\n name: '<example_resource_name>'\n location: '<region>'\n properties: {\n backup: {\n geoRedundantBackup: 'Enabled' // CRITICAL: stores backups in the paired region\n }\n }\n}\n```",
+ "Other": "1. Geo-redundant backup must be configured when the server is created; it cannot be enabled on an existing server\n2. In the Azure portal, start creating a new Azure Database for MySQL flexible server\n3. On the Basics tab, under Compute + storage, open Configure server\n4. Set Geographically redundant backup to Enabled and save\n5. Finish creating the server and migrate workloads to it",
+ "Terraform": "```hcl\n# Terraform: MySQL Flexible Server with geo-redundant backup (set at creation)\nresource \"azurerm_mysql_flexible_server\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n geo_redundant_backup_enabled = true # CRITICAL: stores backups in the paired region\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **geo-redundant backup** on MySQL Flexible Servers so backups are replicated to the paired Azure region and can be restored during a regional outage. Because this is set at server creation, plan a migration for existing servers, and pair it with an appropriate backup retention period and periodic restore testing.",
+ "Url": "https://hub.prowler.com/check/mysql_flexible_server_geo_redundant_backup_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Geo-redundant backup for Azure MySQL Flexible Server can only be configured at server creation time and cannot be changed afterwards."
+}
diff --git a/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.py b/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.py
new file mode 100644
index 0000000000..5b1685354c
--- /dev/null
+++ b/prowler/providers/azure/services/mysql/mysql_flexible_server_geo_redundant_backup_enabled/mysql_flexible_server_geo_redundant_backup_enabled.py
@@ -0,0 +1,31 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.mysql.mysql_client import mysql_client
+
+
+class mysql_flexible_server_geo_redundant_backup_enabled(Check):
+ """
+ Ensure Azure MySQL Flexible Servers have geo-redundant backup enabled.
+
+ This check evaluates whether each Azure MySQL Flexible Server stores backups in a paired Azure region, enabling recovery from a full regional outage.
+
+ - PASS: The server has geo-redundant backup enabled (geo_redundant_backup is "Enabled").
+ - FAIL: The server does not have geo-redundant backup enabled.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+ for subscription_id, servers in mysql_client.flexible_servers.items():
+ subscription_name = mysql_client.subscriptions.get(
+ subscription_id, subscription_id
+ )
+ for server in servers.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=server)
+ report.subscription = subscription_id
+ if server.geo_redundant_backup == "Enabled":
+ report.status = "PASS"
+ report.status_extended = f"Geo-redundant backup is enabled for server {server.name} in subscription {subscription_name} ({subscription_id})."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Geo-redundant backup is disabled for server {server.name} in subscription {subscription_name} ({subscription_id})."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_tde_enabled/__init__.py b/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_tde_enabled/__init__.py
rename to prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/__init__.py
diff --git a/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.metadata.json b/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.metadata.json
new file mode 100644
index 0000000000..22a9b93401
--- /dev/null
+++ b/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "mysql_flexible_server_high_availability_enabled",
+ "CheckTitle": "MySQL flexible server has high availability enabled",
+ "CheckType": [],
+ "ServiceName": "mysql",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.dbformysql/flexibleservers",
+ "ResourceGroup": "database",
+ "Description": "**Azure MySQL Flexible Server** is evaluated for **high availability** mode. Zone-redundant or same-zone HA provisions a standby replica and provides automatic failover during planned and unplanned outages.",
+ "Risk": "Without **high availability**, a server or zone failure causes **downtime** until manual recovery or redeployment. Applications experience extended unavailability and potential data loss for in-flight transactions during unplanned outages.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-high-availability",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.dbformysql/flexibleservers"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az mysql flexible-server update --name <server_name> --resource-group <resource_group_name> --high-availability ZoneRedundant",
+ "NativeIaC": "```bicep\n// Bicep: MySQL Flexible Server with zone-redundant high availability\nresource mysql 'Microsoft.DBforMySQL/flexibleServers@2023-12-30' = {\n name: '<example_resource_name>'\n location: '<region>'\n sku: {\n name: 'Standard_D2ds_v4'\n tier: 'GeneralPurpose'\n }\n properties: {\n highAvailability: {\n mode: 'ZoneRedundant' // CRITICAL: provisions a standby replica with automatic failover\n }\n }\n}\n```",
+ "Other": "1. In the Azure portal, open your Azure Database for MySQL flexible server\n2. Under Settings, select High availability\n3. Enable High availability and choose Zone redundant (or Same zone)\n4. Save (high availability requires the General Purpose or Business Critical tier)",
+ "Terraform": "```hcl\n# Terraform: MySQL Flexible Server with zone-redundant high availability\nresource \"azurerm_mysql_flexible_server\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n sku_name = \"GP_Standard_D2ds_v4\"\n\n high_availability {\n mode = \"ZoneRedundant\" # CRITICAL: provisions a standby replica with automatic failover\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **high availability** (zone-redundant where supported, otherwise same-zone) on production MySQL Flexible Servers so a standby replica provides automatic failover. High availability requires the General Purpose or Business Critical tier; pair it with geo-redundant backup and periodic failover testing for full resilience.",
+ "Url": "https://hub.prowler.com/check/mysql_flexible_server_high_availability_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "High availability for Azure MySQL Flexible Server requires the General Purpose or Business Critical compute tier and is not available on the Burstable tier."
+}
diff --git a/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.py b/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.py
new file mode 100644
index 0000000000..e1f3054baf
--- /dev/null
+++ b/prowler/providers/azure/services/mysql/mysql_flexible_server_high_availability_enabled/mysql_flexible_server_high_availability_enabled.py
@@ -0,0 +1,34 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.mysql.mysql_client import mysql_client
+
+
+class mysql_flexible_server_high_availability_enabled(Check):
+ """
+ Ensure Azure MySQL Flexible Servers have high availability enabled.
+
+ This check evaluates whether each Azure MySQL Flexible Server is configured with high availability (zone-redundant or same-zone), providing automatic failover to a standby replica during outages.
+
+ - PASS: The server has high availability enabled (high_availability_mode is set and not "Disabled").
+ - FAIL: The server does not have high availability enabled.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+ for subscription_id, servers in mysql_client.flexible_servers.items():
+ subscription_name = mysql_client.subscriptions.get(
+ subscription_id, subscription_id
+ )
+ for server in servers.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=server)
+ report.subscription = subscription_id
+ if (
+ server.high_availability_mode is not None
+ and server.high_availability_mode != "Disabled"
+ ):
+ report.status = "PASS"
+ report.status_extended = f"High availability is enabled for server {server.name} in subscription {subscription_name} ({subscription_id})."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"High availability is disabled for server {server.name} in subscription {subscription_name} ({subscription_id})."
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/azure/services/mysql/mysql_service.py b/prowler/providers/azure/services/mysql/mysql_service.py
index 565e14da01..2898d8445c 100644
--- a/prowler/providers/azure/services/mysql/mysql_service.py
+++ b/prowler/providers/azure/services/mysql/mysql_service.py
@@ -1,4 +1,5 @@
from dataclasses import dataclass
+from typing import Optional
from azure.mgmt.rdbms.mysql_flexibleservers import MySQLManagementClient
@@ -18,9 +19,15 @@ class MySQL(AzureService):
servers = {}
for subscription_id, client in self.clients.items():
try:
- servers_list = client.servers.list()
servers.update({subscription_id: {}})
+ servers_list = self.list_with_rg_scope(
+ subscription_id,
+ client.servers.list,
+ client.servers.list_by_resource_group,
+ )
for server in servers_list:
+ backup = getattr(server, "backup", None)
+ ha = getattr(server, "high_availability", None)
servers[subscription_id].update(
{
server.id: FlexibleServer(
@@ -31,6 +38,10 @@ class MySQL(AzureService):
configurations=self._get_configurations(
client, server.id.split("/")[4], server.name
),
+ geo_redundant_backup=getattr(
+ backup, "geo_redundant_backup", None
+ ),
+ high_availability_mode=getattr(ha, "mode", None),
)
}
)
@@ -78,3 +89,5 @@ class FlexibleServer:
location: str
version: str
configurations: dict[Configuration]
+ geo_redundant_backup: Optional[str] = None
+ high_availability_mode: Optional[str] = None
diff --git a/prowler/providers/azure/services/network/network_service.py b/prowler/providers/azure/services/network/network_service.py
index 0eb6144534..54cb02989b 100644
--- a/prowler/providers/azure/services/network/network_service.py
+++ b/prowler/providers/azure/services/network/network_service.py
@@ -17,14 +17,20 @@ class Network(AzureService):
self.bastion_hosts = self._get_bastion_hosts()
self.network_watchers = self._get_network_watchers()
self.public_ip_addresses = self._get_public_ip_addresses()
+ self.virtual_networks = self._get_virtual_networks()
def _get_security_groups(self):
logger.info("Network - Getting Network Security Groups...")
security_groups = {}
for subscription, client in self.clients.items():
try:
+ security_groups_list = self.list_with_rg_scope(
+ subscription,
+ client.network_security_groups.list_all,
+ client.network_security_groups.list,
+ )
+
security_groups.update({subscription: []})
- security_groups_list = client.network_security_groups.list_all()
for security_group in security_groups_list:
security_groups[subscription].append(
SecurityGroup(
@@ -63,8 +69,8 @@ class Network(AzureService):
network_watchers = {}
for subscription, client in self.clients.items():
try:
- network_watchers.update({subscription: []})
network_watchers_list = client.network_watchers.list_all()
+ network_watchers.update({subscription: []})
for network_watcher in network_watchers_list:
flow_logs = self._get_flow_logs(
subscription, network_watcher.name, network_watcher.id
@@ -163,8 +169,13 @@ class Network(AzureService):
bastion_hosts = {}
for subscription, client in self.clients.items():
try:
+ bastion_hosts_list = self.list_with_rg_scope(
+ subscription,
+ client.bastion_hosts.list,
+ client.bastion_hosts.list_by_resource_group,
+ )
+
bastion_hosts.update({subscription: []})
- bastion_hosts_list = client.bastion_hosts.list()
for bastion_host in bastion_hosts_list:
bastion_hosts[subscription].append(
BastionHost(
@@ -185,8 +196,13 @@ class Network(AzureService):
public_ip_addresses = {}
for subscription, client in self.clients.items():
try:
+ public_ip_addresses_list = self.list_with_rg_scope(
+ subscription,
+ client.public_ip_addresses.list_all,
+ client.public_ip_addresses.list,
+ )
+
public_ip_addresses.update({subscription: []})
- public_ip_addresses_list = client.public_ip_addresses.list_all()
for public_ip_address in public_ip_addresses_list:
public_ip_addresses[subscription].append(
PublicIp(
@@ -203,6 +219,45 @@ class Network(AzureService):
)
return public_ip_addresses
+ def _get_virtual_networks(self):
+ logger.info("Network - Getting Virtual Networks...")
+ virtual_networks = {}
+ for subscription_id, client in self.clients.items():
+ try:
+ virtual_networks[subscription_id] = []
+ virtual_networks_list = self.list_with_rg_scope(
+ subscription_id,
+ client.virtual_networks.list_all,
+ client.virtual_networks.list,
+ )
+ for virtual_network in virtual_networks_list:
+ subnets = []
+ for subnet in getattr(virtual_network, "subnets", []) or []:
+ nsg = getattr(subnet, "network_security_group", None)
+ subnets.append(
+ VNetSubnet(
+ id=subnet.id,
+ name=subnet.name,
+ nsg_id=getattr(nsg, "id", None) if nsg else None,
+ )
+ )
+ virtual_networks[subscription_id].append(
+ VirtualNetwork(
+ id=virtual_network.id,
+ name=virtual_network.name,
+ location=virtual_network.location,
+ enable_ddos_protection=getattr(
+ virtual_network, "enable_ddos_protection", False
+ ),
+ subnets=subnets,
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"Subscription ID: {subscription_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return virtual_networks
+
@dataclass
class BastionHost:
@@ -261,3 +316,23 @@ class PublicIp:
name: str
location: str
ip_address: str
+
+
+@dataclass
+class VNetSubnet:
+ id: str
+ name: str
+ nsg_id: Optional[str] = None
+
+
+@dataclass
+class VirtualNetwork:
+ id: str
+ name: str
+ location: str
+ enable_ddos_protection: bool = False
+ subnets: List[VNetSubnet] = None
+
+ def __post_init__(self):
+ if self.subnets is None:
+ self.subnets = []
diff --git a/tests/providers/alibabacloud/services/rds/rds_instance_tde_key_custom/__init__.py b/prowler/providers/azure/services/network/network_subnet_nsg_associated/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/rds/rds_instance_tde_key_custom/__init__.py
rename to prowler/providers/azure/services/network/network_subnet_nsg_associated/__init__.py
diff --git a/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.metadata.json b/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.metadata.json
new file mode 100644
index 0000000000..73cb41f886
--- /dev/null
+++ b/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "network_subnet_nsg_associated",
+ "CheckTitle": "Subnet has a network security group associated",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.network/virtualnetworks/subnets",
+ "ResourceGroup": "network",
+ "Description": "**Azure Virtual Network** subnets are evaluated for **Network Security Group (NSG)** association. Each subnet should have an NSG to enforce inbound and outbound traffic filtering rules. Subnets without NSGs allow all traffic by default.",
+ "Risk": "Subnets without NSGs have **no network-level access control**. All inbound and outbound traffic is allowed by default, enabling **lateral movement**, **unauthorized access** to resources, and **data exfiltration** across the virtual network.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview",
+ "https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az network vnet subnet update --resource-group <rg> --vnet-name <vnet> --name <subnet> --network-security-group <nsg_name>",
+ "NativeIaC": "```bicep\nresource vnet 'Microsoft.Network/virtualNetworks@2023-09-01' existing = {\n name: '<example_resource_name>'\n}\n\nresource subnet 'Microsoft.Network/virtualNetworks/subnets@2023-09-01' = {\n name: '<example_resource_name>'\n parent: vnet\n properties: {\n addressPrefix: '10.0.1.0/24'\n networkSecurityGroup: {\n id: '<example_resource_id>' // Critical: associates NSG with subnet\n }\n }\n}\n```",
+ "Other": "1. Sign in to Azure portal\n2. Go to Virtual networks and select the VNet\n3. Click on Subnets\n4. Select the subnet without an NSG\n5. Under Network security group, select an existing NSG or create a new one\n6. Click Save",
+ "Terraform": "```hcl\nresource \"azurerm_subnet_network_security_group_association\" \"<example_resource_name>\" {\n subnet_id = \"<example_resource_id>\" # Critical: associates NSG with subnet\n network_security_group_id = \"<example_resource_id>\"\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Associate a **Network Security Group** with every subnet. Create NSG rules following **least privilege** \u2014 deny all by default and allow only required traffic. Exclude Azure-managed subnets (GatewaySubnet, AzureFirewallSubnet, AzureBastionSubnet) which have their own security controls.",
+ "Url": "https://hub.prowler.com/check/network_subnet_nsg_associated"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check excludes Azure-managed subnets (GatewaySubnet, AzureFirewallSubnet, AzureFirewallManagementSubnet, AzureBastionSubnet, RouteServerSubnet) which should not have custom NSGs."
+}
diff --git a/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.py b/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.py
new file mode 100644
index 0000000000..054f663351
--- /dev/null
+++ b/prowler/providers/azure/services/network/network_subnet_nsg_associated/network_subnet_nsg_associated.py
@@ -0,0 +1,54 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.network.network_client import network_client
+
+# Subnets that are managed by Azure and should not have custom NSGs
+EXCLUDED_SUBNET_NAMES = {
+ "GatewaySubnet",
+ "AzureFirewallSubnet",
+ "AzureFirewallManagementSubnet",
+ "AzureBastionSubnet",
+ "RouteServerSubnet",
+}
+
+
+class network_subnet_nsg_associated(Check):
+ """
+ Ensure every subnet has a Network Security Group (NSG) associated.
+
+ This check evaluates whether each subnet in every virtual network has an NSG associated to enforce inbound and outbound traffic filtering. Azure-managed subnets (e.g. GatewaySubnet, AzureFirewallSubnet, AzureBastionSubnet) are excluded because they must not have custom NSGs.
+
+ - PASS: The subnet has an NSG associated.
+ - FAIL: The subnet does not have an NSG associated.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+
+ for subscription_name, vnets in network_client.virtual_networks.items():
+ for vnet in vnets:
+ for subnet in vnet.subnets:
+ if subnet.name in EXCLUDED_SUBNET_NAMES:
+ continue
+
+ report = Check_Report_Azure(metadata=self.metadata(), resource=vnet)
+ report.subscription = subscription_name
+ report.resource_name = f"{vnet.name}/{subnet.name}"
+ report.resource_id = subnet.id
+ report.location = vnet.location
+
+ if subnet.nsg_id:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Subnet '{subnet.name}' in VNet '{vnet.name}' "
+ f"has an NSG associated."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Subnet '{subnet.name}' in VNet '{vnet.name}' "
+ f"does not have an NSG associated."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/securitycenter/__init__.py b/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/securitycenter/__init__.py
rename to prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/__init__.py
diff --git a/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.metadata.json b/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.metadata.json
new file mode 100644
index 0000000000..dfeef103c1
--- /dev/null
+++ b/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "azure",
+ "CheckID": "network_vnet_ddos_protection_enabled",
+ "CheckTitle": "Virtual network has Azure DDoS Network Protection enabled",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.network/virtualnetworks",
+ "ResourceGroup": "network",
+ "Description": "**Azure Virtual Networks** are evaluated for **DDoS Network Protection**. When enabled, Azure DDoS Protection provides enhanced mitigation against volumetric, protocol, and application-layer DDoS attacks targeting resources deployed in the virtual network.",
+ "Risk": "Without DDoS protection, Azure resources are only covered by **DDoS Infrastructure Protection** (basic), which may not mitigate sophisticated or large-scale attacks. Successful DDoS attacks cause **service unavailability** and potential **data exposure** during failover.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/ddos-protection/ddos-protection-overview"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az network ddos-protection create --resource-group <rg> --name <plan> && az network vnet update --resource-group <rg> --name <vnet> --ddos-protection-plan <plan_id>",
+ "NativeIaC": "```bicep\nresource vnet 'Microsoft.Network/virtualNetworks@2023-09-01' = {\n name: '<example_resource_name>'\n location: '<example_location>'\n properties: {\n addressSpace: { addressPrefixes: ['10.0.0.0/16'] }\n enableDdosProtection: true // Critical: enables DDoS Protection\n ddosProtectionPlan: { id: '<example_resource_id>' }\n }\n}\n```",
+ "Other": "1. Sign in to Azure portal\n2. Search for 'DDoS protection plans'\n3. Create a new DDoS protection plan\n4. Go to Virtual networks and select the target VNet\n5. Under DDoS protection, select 'Enable' and select the plan\n6. Click Save",
+ "Terraform": "```hcl\nresource \"azurerm_virtual_network\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n location = \"<example_location>\"\n resource_group_name = \"<example_resource_name>\"\n address_space = [\"10.0.0.0/16\"]\n\n ddos_protection_plan {\n id = \"<example_resource_id>\" # Critical: associates DDoS Protection Plan\n enable = true\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **Azure DDoS Network Protection** on virtual networks hosting internet-facing workloads. Consider cost implications — DDoS Network Protection has a monthly charge per plan. Use **DDoS IP Protection** as a lower-cost alternative for individual public IPs.",
+ "Url": "https://hub.prowler.com/check/network_vnet_ddos_protection_enabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Azure DDoS Network Protection has a monthly cost (~$2,944/month per plan). Consider whether the workload justifies this cost. Internal-only VNets without internet-facing resources may not need DDoS protection."
+}
diff --git a/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.py b/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.py
new file mode 100644
index 0000000000..6a9a081fb7
--- /dev/null
+++ b/prowler/providers/azure/services/network/network_vnet_ddos_protection_enabled/network_vnet_ddos_protection_enabled.py
@@ -0,0 +1,41 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.network.network_client import network_client
+
+
+class network_vnet_ddos_protection_enabled(Check):
+ """
+ Ensure Azure DDoS Network Protection is enabled on virtual networks.
+
+ This check evaluates whether each virtual network has a DDoS protection plan associated, providing always-on traffic monitoring and adaptive mitigation against volumetric and protocol attacks.
+
+ - PASS: The virtual network has DDoS protection enabled.
+ - FAIL: The virtual network does not have DDoS protection enabled.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+
+ for subscription_name, vnets in network_client.virtual_networks.items():
+ for vnet in vnets:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=vnet)
+ report.subscription = subscription_name
+ report.resource_name = vnet.name
+ report.resource_id = vnet.id
+ report.location = vnet.location
+
+ if vnet.enable_ddos_protection:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Virtual network '{vnet.name}' has DDoS "
+ f"protection enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Virtual network '{vnet.name}' does not have "
+ f"DDoS protection enabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/policy/policy_service.py b/prowler/providers/azure/services/policy/policy_service.py
index 1d1381202f..663e9b76a3 100644
--- a/prowler/providers/azure/services/policy/policy_service.py
+++ b/prowler/providers/azure/services/policy/policy_service.py
@@ -18,8 +18,8 @@ class Policy(AzureService):
for subscription_id, client in self.clients.items():
try:
- policy_assigments_list = client.policy_assignments.list()
policy_assigments.update({subscription_id: {}})
+ policy_assigments_list = client.policy_assignments.list()
for policy_assigment in policy_assigments_list:
policy_assigments[subscription_id].update(
diff --git a/tests/providers/alibabacloud/services/securitycenter/securitycenter_all_assets_agent_installed/__init__.py b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/securitycenter/securitycenter_all_assets_agent_installed/__init__.py
rename to prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/__init__.py
diff --git a/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.metadata.json b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.metadata.json
new file mode 100644
index 0000000000..7be125ecf2
--- /dev/null
+++ b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "postgresql_flexible_server_geo_redundant_backup_enabled",
+ "CheckTitle": "PostgreSQL flexible server has geo-redundant backup enabled",
+ "CheckType": [],
+ "ServiceName": "postgresql",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.dbforpostgresql/flexibleservers",
+ "ResourceGroup": "database",
+ "Description": "**Azure PostgreSQL Flexible Server** is evaluated for **geo-redundant backup**. Geo-redundant backup stores backup copies in a paired Azure region, enabling restore and cross-region disaster recovery.",
+ "Risk": "Without **geo-redundant backup**, a regional disaster can cause **permanent data loss**. Locally redundant backups only protect against storage hardware failures within the same region and cannot be restored if the primary region becomes unavailable.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-backup-restore",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.dbforpostgresql/flexibleservers"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az postgres flexible-server create --name <server_name> --resource-group <resource_group_name> --location <region> --geo-redundant-backup Enabled",
+ "NativeIaC": "```bicep\n// Bicep: PostgreSQL Flexible Server with geo-redundant backup (set at creation)\nresource postgresql 'Microsoft.DBforPostgreSQL/flexibleServers@2023-06-01-preview' = {\n name: '<example_resource_name>'\n location: '<region>'\n properties: {\n backup: {\n geoRedundantBackup: 'Enabled' // CRITICAL: stores backups in the paired region\n }\n }\n}\n```",
+ "Other": "1. Geo-redundant backup must be configured when the server is created; it cannot be enabled on an existing server\n2. In the Azure portal, start creating a new Azure Database for PostgreSQL flexible server\n3. On the Basics tab, under Compute + storage, open Configure server\n4. Set Geographically redundant backup to Enabled and save\n5. Finish creating the server and migrate workloads to it",
+ "Terraform": "```hcl\n# Terraform: PostgreSQL Flexible Server with geo-redundant backup (set at creation)\nresource \"azurerm_postgresql_flexible_server\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n geo_redundant_backup_enabled = true # CRITICAL: stores backups in the paired region\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **geo-redundant backup** on PostgreSQL Flexible Servers so backups are replicated to the paired Azure region and can be restored during a regional outage. Because this is set at server creation, plan a migration for existing servers, and pair it with an appropriate backup retention period and periodic restore testing.",
+ "Url": "https://hub.prowler.com/check/postgresql_flexible_server_geo_redundant_backup_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Geo-redundant backup for Azure PostgreSQL Flexible Server can only be configured at server creation time and cannot be changed afterwards."
+}
diff --git a/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.py b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.py
new file mode 100644
index 0000000000..94fdaa7a1c
--- /dev/null
+++ b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_geo_redundant_backup_enabled/postgresql_flexible_server_geo_redundant_backup_enabled.py
@@ -0,0 +1,36 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.postgresql.postgresql_client import (
+ postgresql_client,
+)
+
+
+class postgresql_flexible_server_geo_redundant_backup_enabled(Check):
+ """
+ Ensure Azure PostgreSQL Flexible Servers have geo-redundant backup enabled.
+
+ This check evaluates whether each Azure PostgreSQL Flexible Server stores backups in a paired Azure region, enabling cross-region disaster recovery.
+
+ - PASS: The server has geo-redundant backup enabled (geo_redundant_backup is "Enabled").
+ - FAIL: The server does not have geo-redundant backup enabled.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+ for (
+ subscription,
+ flexible_servers,
+ ) in postgresql_client.flexible_servers.items():
+ subscription_name = postgresql_client.subscriptions.get(
+ subscription, subscription
+ )
+ for server in flexible_servers:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=server)
+ report.subscription = subscription
+ if server.geo_redundant_backup == "Enabled":
+ report.status = "PASS"
+ report.status_extended = f"Flexible Postgresql server {server.name} from subscription {subscription_name} ({subscription}) has geo-redundant backup enabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Flexible Postgresql server {server.name} from subscription {subscription_name} ({subscription}) does not have geo-redundant backup enabled."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/alibabacloud/services/securitycenter/securitycenter_vulnerability_scan_enabled/__init__.py b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/securitycenter/securitycenter_vulnerability_scan_enabled/__init__.py
rename to prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/__init__.py
diff --git a/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.metadata.json b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.metadata.json
new file mode 100644
index 0000000000..58b6588886
--- /dev/null
+++ b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "postgresql_flexible_server_high_availability_enabled",
+ "CheckTitle": "PostgreSQL flexible server has high availability enabled",
+ "CheckType": [],
+ "ServiceName": "postgresql",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.dbforpostgresql/flexibleservers",
+ "ResourceGroup": "database",
+ "Description": "**Azure PostgreSQL Flexible Server** is evaluated for **high availability** mode. Zone-redundant or same-zone HA provisions a standby replica and provides automatic failover during planned and unplanned outages.",
+ "Risk": "Without **high availability**, a server or zone failure causes **downtime** until manual recovery or redeployment. Critical databases experience extended unavailability and potential data loss for in-flight transactions during unplanned outages.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-high-availability",
+ "https://learn.microsoft.com/en-us/azure/templates/microsoft.dbforpostgresql/flexibleservers"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az postgres flexible-server update --name <server_name> --resource-group <resource_group_name> --high-availability ZoneRedundant",
+ "NativeIaC": "```bicep\n// Bicep: PostgreSQL Flexible Server with zone-redundant high availability\nresource postgresql 'Microsoft.DBforPostgreSQL/flexibleServers@2023-06-01-preview' = {\n name: '<example_resource_name>'\n location: '<region>'\n sku: {\n name: 'Standard_D2ds_v4'\n tier: 'GeneralPurpose'\n }\n properties: {\n highAvailability: {\n mode: 'ZoneRedundant' // CRITICAL: provisions a standby replica with automatic failover\n }\n }\n}\n```",
+ "Other": "1. In the Azure portal, open your Azure Database for PostgreSQL flexible server\n2. Under Settings, select High availability\n3. Enable High availability and choose Zone redundant (or Same zone)\n4. Save (high availability requires the General Purpose or Memory Optimized tier)",
+ "Terraform": "```hcl\n# Terraform: PostgreSQL Flexible Server with zone-redundant high availability\nresource \"azurerm_postgresql_flexible_server\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<region>\"\n sku_name = \"GP_Standard_D2ds_v4\"\n\n high_availability {\n mode = \"ZoneRedundant\" # CRITICAL: provisions a standby replica with automatic failover\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **high availability** (zone-redundant where supported, otherwise same-zone) on production PostgreSQL Flexible Servers so a standby replica provides automatic failover. High availability requires the General Purpose or Memory Optimized tier; pair it with geo-redundant backup and periodic failover testing for full resilience.",
+ "Url": "https://hub.prowler.com/check/postgresql_flexible_server_high_availability_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "High availability for Azure PostgreSQL Flexible Server requires the General Purpose or Memory Optimized compute tier and is not available on the Burstable tier."
+}
diff --git a/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.py b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.py
new file mode 100644
index 0000000000..14c69f591e
--- /dev/null
+++ b/prowler/providers/azure/services/postgresql/postgresql_flexible_server_high_availability_enabled/postgresql_flexible_server_high_availability_enabled.py
@@ -0,0 +1,39 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.postgresql.postgresql_client import (
+ postgresql_client,
+)
+
+
+class postgresql_flexible_server_high_availability_enabled(Check):
+ """
+ Ensure Azure PostgreSQL Flexible Servers have high availability enabled.
+
+ This check evaluates whether each Azure PostgreSQL Flexible Server is configured with high availability (zone-redundant or same-zone), providing automatic failover to a standby replica during outages.
+
+ - PASS: The server has high availability enabled (high_availability_mode is set and not "Disabled").
+ - FAIL: The server does not have high availability enabled.
+ """
+
+ def execute(self) -> Check_Report_Azure:
+ findings = []
+ for (
+ subscription,
+ flexible_servers,
+ ) in postgresql_client.flexible_servers.items():
+ subscription_name = postgresql_client.subscriptions.get(
+ subscription, subscription
+ )
+ for server in flexible_servers:
+ report = Check_Report_Azure(metadata=self.metadata(), resource=server)
+ report.subscription = subscription
+ if (
+ server.high_availability_mode is not None
+ and server.high_availability_mode != "Disabled"
+ ):
+ report.status = "PASS"
+ report.status_extended = f"Flexible Postgresql server {server.name} from subscription {subscription_name} ({subscription}) has high availability enabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Flexible Postgresql server {server.name} from subscription {subscription_name} ({subscription}) does not have high availability enabled."
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/azure/services/postgresql/postgresql_service.py b/prowler/providers/azure/services/postgresql/postgresql_service.py
index 13081ad270..9bcb6426b8 100644
--- a/prowler/providers/azure/services/postgresql/postgresql_service.py
+++ b/prowler/providers/azure/services/postgresql/postgresql_service.py
@@ -1,5 +1,7 @@
from dataclasses import dataclass
+from typing import Optional
+from azure.core.exceptions import ResourceNotFoundError
from azure.mgmt.postgresqlflexibleservers import PostgreSQLManagementClient
from prowler.lib.logger import logger
@@ -18,58 +20,77 @@ class PostgreSQL(AzureService):
for subscription, client in self.clients.items():
try:
flexible_servers.update({subscription: []})
- flexible_servers_list = client.servers.list()
+ flexible_servers_list = self.list_with_rg_scope(
+ subscription,
+ client.servers.list,
+ client.servers.list_by_resource_group,
+ )
+
for postgresql_server in flexible_servers_list:
- resource_group = self._get_resource_group(postgresql_server.id)
- # Fetch full server object once to extract multiple properties
- server_details = client.servers.get(
- resource_group, postgresql_server.name
- )
- require_secure_transport = self._get_require_secure_transport(
- subscription, resource_group, postgresql_server.name
- )
- active_directory_auth = self._extract_active_directory_auth(
- server_details
- )
- entra_id_admins = self._get_entra_id_admins(
- subscription, resource_group, postgresql_server.name
- )
- log_checkpoints = self._get_log_checkpoints(
- subscription, resource_group, postgresql_server.name
- )
- log_disconnections = self._get_log_disconnections(
- subscription, resource_group, postgresql_server.name
- )
- log_connections = self._get_log_connections(
- subscription, resource_group, postgresql_server.name
- )
- connection_throttling = self._get_connection_throttling(
- subscription, resource_group, postgresql_server.name
- )
- log_retention_days = self._get_log_retention_days(
- subscription, resource_group, postgresql_server.name
- )
- firewall = self._get_firewall(
- subscription, resource_group, postgresql_server.name
- )
- location = server_details.location
- flexible_servers[subscription].append(
- Server(
- id=postgresql_server.id,
- name=postgresql_server.name,
- resource_group=resource_group,
- location=location,
- require_secure_transport=require_secure_transport,
- active_directory_auth=active_directory_auth,
- entra_id_admins=entra_id_admins,
- log_checkpoints=log_checkpoints,
- log_connections=log_connections,
- log_disconnections=log_disconnections,
- connection_throttling=connection_throttling,
- log_retention_days=log_retention_days,
- firewall=firewall,
+ # Isolate each server: a failure collecting one server must
+ # not abort collection of the remaining servers in the
+ # subscription.
+ try:
+ resource_group = self._get_resource_group(postgresql_server.id)
+ # Fetch full server object once to extract multiple properties
+ server_details = client.servers.get(
+ resource_group, postgresql_server.name
+ )
+ require_secure_transport = self._get_require_secure_transport(
+ subscription, resource_group, postgresql_server.name
+ )
+ active_directory_auth = self._extract_active_directory_auth(
+ server_details
+ )
+ entra_id_admins = self._get_entra_id_admins(
+ subscription, resource_group, postgresql_server.name
+ )
+ log_checkpoints = self._get_log_checkpoints(
+ subscription, resource_group, postgresql_server.name
+ )
+ log_disconnections = self._get_log_disconnections(
+ subscription, resource_group, postgresql_server.name
+ )
+ log_connections = self._get_log_connections(
+ subscription, resource_group, postgresql_server.name
+ )
+ connection_throttling = self._get_connection_throttling(
+ subscription, resource_group, postgresql_server.name
+ )
+ log_retention_days = self._get_log_retention_days(
+ subscription, resource_group, postgresql_server.name
+ )
+ firewall = self._get_firewall(
+ subscription, resource_group, postgresql_server.name
+ )
+ location = server_details.location
+ backup = getattr(server_details, "backup", None)
+ ha = getattr(server_details, "high_availability", None)
+ flexible_servers[subscription].append(
+ Server(
+ id=postgresql_server.id,
+ name=postgresql_server.name,
+ resource_group=resource_group,
+ location=location,
+ require_secure_transport=require_secure_transport,
+ active_directory_auth=active_directory_auth,
+ entra_id_admins=entra_id_admins,
+ log_checkpoints=log_checkpoints,
+ log_connections=log_connections,
+ log_disconnections=log_disconnections,
+ connection_throttling=connection_throttling,
+ log_retention_days=log_retention_days,
+ firewall=firewall,
+ geo_redundant_backup=getattr(
+ backup, "geo_redundant_backup", None
+ ),
+ high_availability_mode=getattr(ha, "mode", None),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"Subscription ID: {subscription} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- )
except Exception as error:
logger.error(
f"Subscription ID: {subscription} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
@@ -149,21 +170,60 @@ class PostgreSQL(AzureService):
)
return admin_list
except Exception as e:
- logger.error(f"Error getting Entra ID admins for {server_name}: {e}")
+ if "authentication is not enabled" in str(e):
+ # Expected when the server uses PostgreSQL authentication only
+ # (Entra/Azure AD auth disabled); not an error.
+ logger.warning(
+ f"Entra ID authentication is not enabled for {server_name}; skipping Entra ID admins."
+ )
+ else:
+ logger.error(f"Error getting Entra ID admins for {server_name}: {e}")
return []
- def _get_connection_throttling(self, subscription, resouce_group_name, server_name):
+ def _get_connection_throttling(
+ self, subscription: str, resouce_group_name: str, server_name: str
+ ) -> Optional[str]:
+ """Get the ``connection_throttle.enable`` setting for a flexible server.
+
+ The ``connection_throttle.enable`` server parameter was removed in
+ PostgreSQL 16+, so it no longer exists on newer flexible servers. When
+ the parameter is genuinely absent the Azure SDK raises
+ ``ResourceNotFoundError`` (error code ``ConfigurationNotExists``); that
+ case is treated as "not enabled" and ``None`` is returned so collection
+ of the server can continue.
+
+ Any other error (permissions, throttling, transient SDK failures) is
+ intentionally left to propagate: returning ``None`` for those would make
+ the downstream check report the server as having connection throttling
+ disabled, silently turning a collection failure into a security finding.
+
+ Args:
+ subscription: Azure subscription identifier.
+ resouce_group_name: Resource group containing the server.
+ server_name: PostgreSQL flexible server name.
+
+ Returns:
+ The uppercased throttling value, or ``None`` when the parameter does
+ not exist on the server.
+
+ Raises:
+ ResourceNotFoundError is handled; any other exception propagates to
+ the caller so it can be surfaced as a collection failure.
+ """
client = self.clients[subscription]
- connection_throttling = client.configurations.get(
- resouce_group_name, server_name, "connection_throttle.enable"
- )
- return connection_throttling.value.upper()
+ try:
+ connection_throttling = client.configurations.get(
+ resouce_group_name, server_name, "connection_throttle.enable"
+ )
+ return connection_throttling.value.upper()
+ except ResourceNotFoundError:
+ return None
def _get_log_retention_days(self, subscription, resouce_group_name, server_name):
client = self.clients[subscription]
try:
log_retention_days = client.configurations.get(
- resouce_group_name, server_name, "log_retention_days"
+ resouce_group_name, server_name, "logfiles.retention_days"
)
log_retention_days = log_retention_days.value
except Exception:
@@ -214,6 +274,8 @@ class Server:
log_checkpoints: str
log_connections: str
log_disconnections: str
- connection_throttling: str
- log_retention_days: str
+ connection_throttling: Optional[str]
+ log_retention_days: Optional[str]
firewall: list[Firewall]
+ geo_redundant_backup: Optional[str] = None
+ high_availability_mode: Optional[str] = None
diff --git a/tests/providers/alibabacloud/services/sls/__init__.py b/prowler/providers/azure/services/recovery/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/__init__.py
rename to prowler/providers/azure/services/recovery/__init__.py
diff --git a/prowler/providers/azure/services/recovery/recovery_service.py b/prowler/providers/azure/services/recovery/recovery_service.py
index 16b5bc3248..6c414ee446 100644
--- a/prowler/providers/azure/services/recovery/recovery_service.py
+++ b/prowler/providers/azure/services/recovery/recovery_service.py
@@ -52,12 +52,18 @@ class Recovery(AzureService):
"""
logger.info("Recovery - Getting Recovery Services vaults...")
vaults_dict: dict[str, dict[str, BackupVault]] = {}
+ subscription_id = "unknown"
try:
vaults_dict: dict[str, dict[str, BackupVault]] = {}
for subscription_id, client in self.clients.items():
- vaults = client.vaults.list_by_subscription_id()
+ vaults_list = self.list_with_rg_scope(
+ subscription_id,
+ client.vaults.list_by_subscription_id,
+ client.vaults.list_by_resource_group,
+ )
+
vaults_dict[subscription_id] = {}
- for vault in vaults:
+ for vault in vaults_list:
vault_obj = BackupVault(
id=vault.id,
name=vault.name,
@@ -66,21 +72,33 @@ class Recovery(AzureService):
vaults_dict[subscription_id][vault_obj.id] = vault_obj
except Exception as error:
logger.error(
- f"Subscription ID: {subscription_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"Subscription ID: {subscription_id} -- "
+ f"{error.__class__.__name__}"
+ f"[{error.__traceback__.tb_lineno}]: {error}"
)
return vaults_dict
class RecoveryBackup(AzureService):
+ """
+ Service wrapper for Azure Recovery Services backup data.
+
+ Collects the backup protected items and backup policies for each Recovery
+ Services vault discovered by the Recovery service.
+ """
+
def __init__(
- self, provider: AzureProvider, vaults: dict[str, dict[str, BackupVault]]
+ self,
+ provider: AzureProvider,
+ vaults: dict[str, dict[str, BackupVault]],
):
super().__init__(RecoveryServicesBackupClient, provider)
for subscription_id, vaults in vaults.items():
for vault in vaults.values():
- vault.backup_protected_items = self._get_backup_protected_items(
+ protected_items = self._get_backup_protected_items(
subscription_id=subscription_id, vault=vault
)
+ vault.backup_protected_items = protected_items
vault.backup_policies = self._get_backup_policies(
subscription_id=subscription_id, vault=vault
)
@@ -102,19 +120,22 @@ class RecoveryBackup(AzureService):
)
for item in backup_protected_items:
item_properties = getattr(item, "properties", None)
+ workload_type = None
+ backup_policy_id = None
+ if item_properties:
+ workload_type = item_properties.workload_type
+ backup_policy_id = item_properties.policy_id
backup_protected_items_dict[item.id] = BackupItem(
id=item.id,
name=item.name,
- workload_type=(
- item_properties.workload_type if item_properties else None
- ),
- backup_policy_id=(
- item_properties.policy_id if item_properties else None
- ),
+ workload_type=workload_type,
+ backup_policy_id=backup_policy_id,
)
except Exception as error:
logger.error(
- f"Subscription ID: {subscription_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"Subscription ID: {subscription_id} -- "
+ f"{error.__class__.__name__}"
+ f"[{error.__traceback__.tb_lineno}]: {error}"
)
return backup_protected_items_dict
@@ -126,40 +147,44 @@ class RecoveryBackup(AzureService):
"""
logger.info("Recovery - Getting backup policies...")
backup_policies_dict: dict[str, BackupPolicy] = {}
- unique_backup_policies: set[str] = set()
try:
- for item in vault.backup_protected_items.values():
- if item.backup_policy_id:
- unique_backup_policies.add(item.backup_policy_id)
- for policy_id in unique_backup_policies:
- policy = self.clients[subscription_id].protection_policies.get(
- vault_name=vault.name,
- resource_group_name=vault.id.split("/")[4],
- policy_name=policy_id.split("/")[-1],
- )
- backup_policies_dict[policy_id] = BackupPolicy(
+ client = self.clients[subscription_id]
+ backup_policies = client.backup_policies.list(
+ vault_name=vault.name,
+ resource_group_name=vault.id.split("/")[4],
+ )
+ for policy in backup_policies:
+ retention_days = self._get_backup_policy_retention_days(policy)
+ backup_policies_dict[policy.id] = BackupPolicy(
id=policy.id,
name=policy.name,
- retention_days=getattr(
- getattr(
- getattr(
- getattr(
- getattr(policy, "properties", None),
- "retention_policy",
- None,
- ),
- "daily_schedule",
- None,
- ),
- "retention_duration",
- None,
- ),
- "count",
- None,
- ),
+ retention_days=retention_days,
)
except Exception as error:
logger.error(
- f"Subscription ID: {subscription_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ f"Subscription ID: {subscription_id} -- "
+ f"{error.__class__.__name__}"
+ f"[{error.__traceback__.tb_lineno}]: {error}"
)
return backup_policies_dict
+
+ @staticmethod
+ def _get_backup_policy_retention_days(policy) -> Optional[int]:
+ """Return the daily retention duration count for a backup policy."""
+ return getattr(
+ getattr(
+ getattr(
+ getattr(
+ getattr(policy, "properties", None),
+ "retention_policy",
+ None,
+ ),
+ "daily_schedule",
+ None,
+ ),
+ "retention_duration",
+ None,
+ ),
+ "count",
+ None,
+ )
diff --git a/tests/providers/alibabacloud/services/sls/sls_logstore_retention_period/__init__.py b/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/sls_logstore_retention_period/__init__.py
rename to prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/__init__.py
diff --git a/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.metadata.json b/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.metadata.json
new file mode 100644
index 0000000000..33f8516d1b
--- /dev/null
+++ b/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "recovery_vault_backup_policy_retention_adequate",
+ "CheckTitle": "Recovery Services backup policy has at least 30 days retention",
+ "CheckType": [],
+ "ServiceName": "recovery",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "**Azure Recovery Services** backup policies are evaluated for adequate **daily retention**. Policies with fewer than 30 days of retention may not provide sufficient recovery points for incident investigation, compliance requirements, or ransomware recovery scenarios.",
+ "Risk": "Short retention periods limit the ability to recover from **delayed-discovery incidents** such as ransomware that encrypts backups over time, data corruption that propagates across backup cycles, or compliance investigations requiring historical data. Insufficient retention may violate regulatory requirements.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/backup/backup-azure-vm-backup-faq",
+ "https://learn.microsoft.com/en-us/azure/backup/backup-azure-backup-faq"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az backup policy set --resource-group <resource-group> --vault-name <vault-name> --name <policy-name> --policy @policy.json",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Azure portal\n2. Go to Recovery Services vaults and select the vault\n3. Go to Backup policies\n4. Select the policy to modify\n5. Under Retention range, set Daily backup point retention to at least 30 days\n6. Click Save",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set daily backup retention to at least **30 days**. For production workloads, consider 90+ days. Configure **weekly, monthly, and yearly** retention points for long-term compliance. Use **immutable vaults** to prevent backup deletion by compromised admin accounts.",
+ "Url": "https://hub.prowler.com/check/recovery_vault_backup_policy_retention_adequate"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check evaluates daily retention from the backup policy's retention_policy.daily_schedule.retention_duration.count. Policies without a daily schedule are flagged. The 30-day minimum aligns with common compliance requirements and incident response timelines."
+}
diff --git a/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.py b/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.py
new file mode 100644
index 0000000000..b770f87a62
--- /dev/null
+++ b/prowler/providers/azure/services/recovery/recovery_vault_backup_policy_retention_adequate/recovery_vault_backup_policy_retention_adequate.py
@@ -0,0 +1,65 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.recovery.recovery_client import recovery_client
+
+MINIMUM_RETENTION_DAYS = 30
+
+
+class recovery_vault_backup_policy_retention_adequate(Check):
+ """Check if vault backup policies retain backups for at least 30 days."""
+
+ def execute(self) -> list[Check_Report_Azure]:
+ """Execute the check across Recovery Services vault backup policies."""
+
+ findings = []
+
+ for subscription_name, vaults in recovery_client.vaults.items():
+ for vault in vaults.values():
+ if not vault.backup_policies:
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=vault
+ )
+ report.subscription = subscription_name
+ report.resource_name = vault.name
+ report.resource_id = vault.id
+ report.location = vault.location
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Recovery vault '{vault.name}' has no backup "
+ f"policies configured."
+ )
+ findings.append(report)
+ continue
+
+ for policy in vault.backup_policies.values():
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=vault
+ )
+ report.subscription = subscription_name
+ report.resource_name = f"{vault.name}/{policy.name}"
+ report.resource_id = policy.id
+ report.location = vault.location
+
+ if policy.retention_days is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Backup policy '{policy.name}' in vault "
+ f"'{vault.name}' has no daily retention configured."
+ )
+ elif policy.retention_days < MINIMUM_RETENTION_DAYS:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Backup policy '{policy.name}' in vault "
+ f"'{vault.name}' has {policy.retention_days}-day "
+ f"retention (minimum: {MINIMUM_RETENTION_DAYS})."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Backup policy '{policy.name}' in vault "
+ f"'{vault.name}' has {policy.retention_days}-day "
+ f"retention."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/alibabacloud/services/sls/sls_management_console_authentication_failures_alert_enabled/__init__.py b/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/sls_management_console_authentication_failures_alert_enabled/__init__.py
rename to prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/__init__.py
diff --git a/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.metadata.json b/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.metadata.json
new file mode 100644
index 0000000000..04e4405851
--- /dev/null
+++ b/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "recovery_vault_has_protected_items",
+ "CheckTitle": "Recovery Services vault has backup protected items configured",
+ "CheckType": [],
+ "ServiceName": "recovery",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "microsoft.recoveryservices/vaults",
+ "ResourceGroup": "storage",
+ "Description": "**Azure Recovery Services** vaults are evaluated for **backup protected items**. A vault with no protected items indicates that no resources (VMs, databases, file shares) are configured for backup through this vault, potentially leaving critical workloads unprotected.",
+ "Risk": "Empty vaults represent a gap in **disaster recovery** coverage. Resources without backup protection face permanent data loss from accidental deletion, ransomware, corruption, or regional outages. The vault may have been provisioned but backup was never configured.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/backup/backup-azure-vms-first-look-arm",
+ "https://learn.microsoft.com/en-us/azure/backup/backup-overview"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az backup protection enable-for-vm --resource-group <rg> --vault-name <vault> --vm <vm_id> --policy-name DefaultPolicy",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Azure portal\n2. Go to Recovery Services vaults and select the vault\n3. Click + Backup\n4. Select the workload type (Azure VM, SQL, File Share, etc.)\n5. Select the backup policy\n6. Choose the resources to protect\n7. Click Enable Backup",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure **backup protection** for critical resources including VMs, databases, and file shares. Use **Azure Backup policies** with appropriate retention and frequency. If the vault is unused, consider deleting it to reduce resource sprawl.",
+ "Url": "https://hub.prowler.com/check/recovery_vault_has_protected_items"
+ }
+ },
+ "Categories": [
+ "forensics-ready"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check reports on each Recovery Services vault individually. An empty vault is not necessarily a security risk if backups are managed through a different vault or Azure Backup center."
+}
diff --git a/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.py b/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.py
new file mode 100644
index 0000000000..6ebd9e5328
--- /dev/null
+++ b/prowler/providers/azure/services/recovery/recovery_vault_has_protected_items/recovery_vault_has_protected_items.py
@@ -0,0 +1,36 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.recovery.recovery_client import recovery_client
+
+
+class recovery_vault_has_protected_items(Check):
+ """Check if Recovery Services vaults have protected backup items."""
+
+ def execute(self) -> list[Check_Report_Azure]:
+ """Execute the check across Recovery Services vaults."""
+
+ findings = []
+
+ for subscription_name, vaults in recovery_client.vaults.items():
+ for vault in vaults.values():
+ report = Check_Report_Azure(metadata=self.metadata(), resource=vault)
+ report.subscription = subscription_name
+ report.resource_name = vault.name
+ report.resource_id = vault.id
+ report.location = vault.location
+
+ if vault.backup_protected_items:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Recovery Services vault '{vault.name}' has "
+ f"{len(vault.backup_protected_items)} protected items."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Recovery Services vault '{vault.name}' has no "
+ f"protected items configured."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/sqlserver/sqlserver_service.py b/prowler/providers/azure/services/sqlserver/sqlserver_service.py
index af02dace0d..274025fd7b 100644
--- a/prowler/providers/azure/services/sqlserver/sqlserver_service.py
+++ b/prowler/providers/azure/services/sqlserver/sqlserver_service.py
@@ -18,8 +18,13 @@ class SQLServer(AzureService):
sql_servers = {}
for subscription, client in self.clients.items():
try:
+ sql_servers_list = self.list_with_rg_scope(
+ subscription,
+ client.servers.list,
+ client.servers.list_by_resource_group,
+ )
+
sql_servers.update({subscription: []})
- sql_servers_list = client.servers.list()
for sql_server in sql_servers_list:
resource_group = self._get_resource_group(sql_server.id)
auditing_policies = self._get_server_blob_auditing_policies(
diff --git a/tests/providers/alibabacloud/services/sls/sls_management_console_signin_without_mfa_alert_enabled/__init__.py b/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/sls_management_console_signin_without_mfa_alert_enabled/__init__.py
rename to prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/__init__.py
diff --git a/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.metadata.json b/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.metadata.json
new file mode 100644
index 0000000000..142b1082cf
--- /dev/null
+++ b/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "azure",
+ "CheckID": "storage_account_public_network_access_disabled",
+ "CheckTitle": "Storage account has 'Public Network Access' disabled",
+ "CheckType": [],
+ "ServiceName": "storage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "microsoft.storage/storageaccounts",
+ "ResourceGroup": "storage",
+ "Description": "**Azure Storage accounts** with **public network access** disabled cannot be reached from public networks. Setting `publicNetworkAccess` to `Disabled` overrides the public access settings of individual containers and forces access through private endpoints or trusted services. This is independent from the 'Allow Blob Anonymous Access' setting.",
+ "Risk": "Leaving **public network access** enabled exposes the storage account endpoints to the **public Internet**, widening the attack surface and undermining **defense in depth**.\n\nThis increases the risk of **unauthorized access**, **data exfiltration**, and reconnaissance against the account, especially when combined with weak network rules or overly permissive access policies.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal#change-the-default-network-access-rule",
+ "https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security-set-default-access"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "az storage account update --name <storage-account> --resource-group <resource-group> --public-network-access Disabled",
+ "NativeIaC": "```bicep\n// Storage account with public network access disabled\nresource sa 'Microsoft.Storage/storageAccounts@2023-01-01' = {\n name: '<example_resource_name>'\n location: resourceGroup().location\n kind: 'StorageV2'\n sku: { name: 'Standard_LRS' }\n properties: {\n publicNetworkAccess: 'Disabled' // Critical: disables public network access to the account\n }\n}\n```",
+ "Other": "1. In the Azure portal, go to Storage accounts and select the target account\n2. Under Security + networking, click Networking\n3. Set Public network access to Disabled\n4. Click Save",
+ "Terraform": "```hcl\nresource \"azurerm_storage_account\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n resource_group_name = \"<example_resource_name>\"\n location = \"<example_location>\"\n account_tier = \"Standard\"\n account_replication_type = \"LRS\"\n public_network_access_enabled = false # Critical: disables public network access\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Disable **public network access** on the storage account and reach it through **private endpoints** or trusted Azure services only. Combine this with **least privilege** RBAC, short-lived `SAS` tokens, and network restrictions. Validate client connectivity before disabling public access in production.",
+ "Url": "https://hub.prowler.com/check/storage_account_public_network_access_disabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check evaluates the storage account publicNetworkAccess property. It is independent from the 'Allow Blob Anonymous Access' setting evaluated by storage_blob_public_access_level_is_disabled."
+}
diff --git a/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.py b/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.py
new file mode 100644
index 0000000000..3db62c5256
--- /dev/null
+++ b/prowler/providers/azure/services/storage/storage_account_public_network_access_disabled/storage_account_public_network_access_disabled.py
@@ -0,0 +1,38 @@
+from prowler.lib.check.models import Check, Check_Report_Azure
+from prowler.providers.azure.services.storage.storage_client import storage_client
+
+
+class storage_account_public_network_access_disabled(Check):
+ """
+ Ensure that 'Public Network Access' is 'Disabled' for storage accounts.
+
+ This check evaluates the storage account's publicNetworkAccess property, which controls
+ whether the account is reachable from public networks. It is independent from the
+ 'Allow Blob Anonymous Access' setting (covered by
+ storage_blob_public_access_level_is_disabled).
+ - PASS: The storage account has public network access disabled.
+ - FAIL: The storage account has public network access enabled (or unset, which Azure treats as enabled).
+ """
+
+ def execute(self) -> list[Check_Report_Azure]:
+ findings = []
+ for subscription, storage_accounts in storage_client.storage_accounts.items():
+ subscription_name = storage_client.subscriptions.get(
+ subscription, subscription
+ )
+ for storage_account in storage_accounts:
+ report = Check_Report_Azure(
+ metadata=self.metadata(), resource=storage_account
+ )
+ report.subscription = subscription
+
+ if storage_account.public_network_access == "Disabled":
+ report.status = "PASS"
+ report.status_extended = f"Storage account {storage_account.name} from subscription {subscription_name} ({subscription}) has public network access disabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Storage account {storage_account.name} from subscription {subscription_name} ({subscription}) has public network access enabled."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/azure/services/storage/storage_blob_public_access_level_is_disabled/storage_blob_public_access_level_is_disabled.metadata.json b/prowler/providers/azure/services/storage/storage_blob_public_access_level_is_disabled/storage_blob_public_access_level_is_disabled.metadata.json
index 079376899b..1cf3e35569 100644
--- a/prowler/providers/azure/services/storage/storage_blob_public_access_level_is_disabled/storage_blob_public_access_level_is_disabled.metadata.json
+++ b/prowler/providers/azure/services/storage/storage_blob_public_access_level_is_disabled/storage_blob_public_access_level_is_disabled.metadata.json
@@ -1,7 +1,7 @@
{
"Provider": "azure",
"CheckID": "storage_blob_public_access_level_is_disabled",
- "CheckTitle": "Storage account has 'Allow blob public access' disabled",
+ "CheckTitle": "Storage account has 'Allow Blob Anonymous Access' disabled",
"CheckType": [],
"ServiceName": "storage",
"SubServiceName": "",
@@ -9,7 +9,7 @@
"Severity": "high",
"ResourceType": "microsoft.storage/storageaccounts",
"ResourceGroup": "storage",
- "Description": "**Azure Storage accounts** with **blob public access** disabled prevent containers or blobs from being set to a public access level. Setting `allow blob public access` to `false` enforces no anonymous reads across the account.",
+ "Description": "**Azure Storage accounts** with **blob anonymous (public) access** disabled prevent containers or blobs from being set to a public access level. Setting `allowBlobPublicAccess` to `false` enforces no anonymous reads across the account. This is independent from the account's 'Public Network Access' setting, which is evaluated by storage_account_public_network_access_disabled.",
"Risk": "Allowing public access permits unauthenticated users to read blob data or enumerate container contents when any container is made public, compromising confidentiality.\n\nExposed objects can be scraped at scale, enabling data exfiltration and intelligence gathering without audit attribution.",
"RelatedUrl": "",
"AdditionalURLs": [
@@ -33,5 +33,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": ""
+ "Notes": "This check evaluates the 'Allow Blob Anonymous Access' (allowBlobPublicAccess) setting. The account's 'Public Network Access' (publicNetworkAccess) setting is evaluated by storage_account_public_network_access_disabled."
}
diff --git a/prowler/providers/azure/services/storage/storage_service.py b/prowler/providers/azure/services/storage/storage_service.py
index 6ec88248bf..863b33256e 100644
--- a/prowler/providers/azure/services/storage/storage_service.py
+++ b/prowler/providers/azure/services/storage/storage_service.py
@@ -20,8 +20,13 @@ class Storage(AzureService):
storage_accounts = {}
for subscription, client in self.clients.items():
try:
+ storage_accounts_list = self.list_with_rg_scope(
+ subscription,
+ client.storage_accounts.list,
+ client.storage_accounts.list_by_resource_group,
+ )
+
storage_accounts.update({subscription: []})
- storage_accounts_list = client.storage_accounts.list()
for storage_account in storage_accounts_list:
parts = storage_account.id.split("/")
if "resourceGroups" in parts:
@@ -42,6 +47,9 @@ class Storage(AzureService):
enable_https_traffic_only=storage_account.enable_https_traffic_only,
infrastructure_encryption=storage_account.encryption.require_infrastructure_encryption,
allow_blob_public_access=storage_account.allow_blob_public_access,
+ public_network_access=getattr(
+ storage_account, "public_network_access", None
+ ),
network_rule_set=NetworkRuleSet(
bypass=getattr(
storage_account.network_rule_set,
@@ -301,6 +309,7 @@ class Account(BaseModel):
enable_https_traffic_only: bool
infrastructure_encryption: Optional[bool] = None
allow_blob_public_access: bool
+ public_network_access: Optional[str] = None
network_rule_set: NetworkRuleSet
encryption_type: str
minimum_tls_version: str
diff --git a/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.metadata.json b/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.metadata.json
index 0649b30110..3bffd83e67 100644
--- a/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.metadata.json
+++ b/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.metadata.json
@@ -34,5 +34,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": "This check passes if SMB channel encryption is set to a secure algorithm."
+ "Notes": "This check passes only if every SMB channel encryption algorithm allowed on the file shares is in the recommended list, which is configurable via azure.recommended_smb_channel_encryption_algorithms and defaults to AES-256-GCM only, as required by CIS."
}
diff --git a/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.py b/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.py
index e46b951583..61d4abc185 100644
--- a/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.py
+++ b/prowler/providers/azure/services/storage/storage_smb_channel_encryption_with_secure_algorithm/storage_smb_channel_encryption_with_secure_algorithm.py
@@ -1,32 +1,38 @@
from prowler.lib.check.models import Check, Check_Report_Azure
from prowler.providers.azure.services.storage.storage_client import storage_client
-SECURE_ENCRYPTION_ALGORITHMS = ["AES-256-GCM"]
+DEFAULT_SECURE_ENCRYPTION_ALGORITHMS = ["AES-256-GCM"]
class storage_smb_channel_encryption_with_secure_algorithm(Check):
"""
- Ensure SMB channel encryption for file shares is set to the recommended algorithm (AES-256-GCM or higher).
+ Ensure SMB channel encryption for file shares only allows secure algorithms (AES-256-GCM or higher by default).
+
+ The list of allowed algorithms is configurable via
+ azure.recommended_smb_channel_encryption_algorithms in the Prowler configuration file.
This check evaluates whether SMB file shares are configured to use only the recommended SMB channel encryption algorithms.
- - PASS: Storage account has the recommended SMB channel encryption (AES-256-GCM or higher) enabled for file shares.
- - FAIL: Storage account does not have the recommended SMB channel encryption enabled for file shares or uses an unsupported algorithm.
+ - PASS: Storage account only allows secure SMB channel encryption algorithms for file shares.
+ - FAIL: Storage account does not have SMB channel encryption enabled, or it allows at least one algorithm that is not in the recommended list.
"""
def execute(self) -> list[Check_Report_Azure]:
findings = []
+ secure_encryption_algorithms = storage_client.audit_config.get(
+ "recommended_smb_channel_encryption_algorithms",
+ DEFAULT_SECURE_ENCRYPTION_ALGORITHMS,
+ )
for subscription, storage_accounts in storage_client.storage_accounts.items():
subscription_name = storage_client.subscriptions.get(
subscription, subscription
)
for account in storage_accounts:
if account.file_service_properties:
+ channel_encryption = (
+ account.file_service_properties.smb_protocol_settings.channel_encryption
+ )
pretty_current_algorithms = (
- ", ".join(
- account.file_service_properties.smb_protocol_settings.channel_encryption
- )
- if account.file_service_properties.smb_protocol_settings.channel_encryption
- else "none"
+ ", ".join(channel_encryption) if channel_encryption else "none"
)
report = Check_Report_Azure(
metadata=self.metadata(),
@@ -35,20 +41,18 @@ class storage_smb_channel_encryption_with_secure_algorithm(Check):
report.subscription = subscription
report.resource_name = account.name
- if (
- not account.file_service_properties.smb_protocol_settings.channel_encryption
- ):
+ if not channel_encryption:
report.status = "FAIL"
report.status_extended = f"Storage account {account.name} from subscription {subscription_name} ({subscription}) does not have SMB channel encryption enabled for file shares."
- elif any(
- algorithm in SECURE_ENCRYPTION_ALGORITHMS
- for algorithm in account.file_service_properties.smb_protocol_settings.channel_encryption
+ elif all(
+ algorithm in secure_encryption_algorithms
+ for algorithm in channel_encryption
):
report.status = "PASS"
- report.status_extended = f"Storage account {account.name} from subscription {subscription_name} ({subscription}) has a secure algorithm for SMB channel encryption ({', '.join(SECURE_ENCRYPTION_ALGORITHMS)}) enabled for file shares since it supports {pretty_current_algorithms}."
+ report.status_extended = f"Storage account {account.name} from subscription {subscription_name} ({subscription}) only allows secure algorithms for SMB channel encryption on file shares since it supports {pretty_current_algorithms}."
else:
report.status = "FAIL"
- report.status_extended = f"Storage account {account.name} from subscription {subscription_name} ({subscription}) does not have SMB channel encryption with a secure algorithm for file shares since it supports {pretty_current_algorithms}."
+ report.status_extended = f"Storage account {account.name} from subscription {subscription_name} ({subscription}) allows insecure algorithms for SMB channel encryption on file shares since it supports {pretty_current_algorithms} and only {', '.join(secure_encryption_algorithms)} is recommended."
findings.append(report)
return findings
diff --git a/prowler/providers/azure/services/vm/vm_service.py b/prowler/providers/azure/services/vm/vm_service.py
index b20f4b5678..8ef27c57f4 100644
--- a/prowler/providers/azure/services/vm/vm_service.py
+++ b/prowler/providers/azure/services/vm/vm_service.py
@@ -22,8 +22,12 @@ class VirtualMachines(AzureService):
for subscription_id, client in self.clients.items():
try:
- virtual_machines_list = client.virtual_machines.list_all()
virtual_machines.update({subscription_id: {}})
+ virtual_machines_list = self.list_with_rg_scope(
+ subscription_id,
+ client.virtual_machines.list_all,
+ client.virtual_machines.list,
+ )
for vm in virtual_machines_list:
storage_profile = getattr(vm, "storage_profile", None)
@@ -155,8 +159,12 @@ class VirtualMachines(AzureService):
for subscription_id, client in self.clients.items():
try:
- disks_list = client.disks.list()
disks.update({subscription_id: {}})
+ disks_list = self.list_with_rg_scope(
+ subscription_id,
+ client.disks.list,
+ client.disks.list_by_resource_group,
+ )
for disk in disks_list:
vms_attached = []
@@ -202,9 +210,13 @@ class VirtualMachines(AzureService):
vm_scale_sets = {}
for subscription_id, client in self.clients.items():
try:
- scale_sets = client.virtual_machine_scale_sets.list_all()
vm_scale_sets[subscription_id] = {}
- for scale_set in scale_sets:
+ scale_sets_list = self.list_with_rg_scope(
+ subscription_id,
+ client.virtual_machine_scale_sets.list_all,
+ client.virtual_machine_scale_sets.list,
+ )
+ for scale_set in scale_sets_list:
backend_pools = []
nic_configs = []
virtual_machine_profile = getattr(
diff --git a/prowler/providers/cloudflare/cloudflare_provider.py b/prowler/providers/cloudflare/cloudflare_provider.py
index 48763df395..9c39839f5d 100644
--- a/prowler/providers/cloudflare/cloudflare_provider.py
+++ b/prowler/providers/cloudflare/cloudflare_provider.py
@@ -46,6 +46,7 @@ class CloudflareProvider(Provider):
"""Cloudflare provider."""
_type: str = "cloudflare"
+ sdk_only: bool = False
_session: CloudflareSession
_identity: CloudflareIdentityInfo
_audit_config: dict
diff --git a/prowler/providers/common/arguments.py b/prowler/providers/common/arguments.py
index 9745bab2ca..2e4d9c8896 100644
--- a/prowler/providers/common/arguments.py
+++ b/prowler/providers/common/arguments.py
@@ -10,24 +10,107 @@ provider_arguments_lib_path = "lib.arguments.arguments"
validate_provider_arguments_function = "validate_arguments"
init_provider_arguments_function = "init_parser"
+# Kept in sync with parser.py's argv normalisation; both consumers import this.
+PROVIDER_ALIASES = {
+ "microsoft365": "m365",
+ "oci": "oraclecloud",
+}
+
+
+def _invoked_provider_from_argv(available_providers: Sequence[str]) -> Optional[str]:
+ """Return the provider name the user invoked, or None.
+
+ Mirrors `ProwlerArgumentParser.parse()` resolution: only inspects
+ `sys.argv[1]`. Scanning the whole argv would misclassify
+ `prowler --output-directory stackit` as `stackit`.
+ """
+ available = set(available_providers)
+ if len(sys.argv) < 2:
+ return "aws" if "aws" in available else None
+ first = sys.argv[1]
+ if first in ("-h", "--help", "-v", "--version"):
+ return None
+ if first.startswith("-"):
+ return "aws" if "aws" in available else None
+ normalized = PROVIDER_ALIASES.get(first, first)
+ return normalized if normalized in available else None
+
def init_providers_parser(self):
- """init_providers_parser calls the provider init_parser function to load all the arguments and flags. Receives a ProwlerArgumentParser object"""
- # We need to call the arguments parser for each provider
+ """Build the subparser of each available provider.
+
+ Built-in load failures are captured silently on
+ `self._builtin_load_failures`; the warn/exit decision is deferred to
+ `enforce_invoked_provider_loaded()` because `parse(args=...)` can
+ override `sys.argv` after this function ran.
+ """
+ self._builtin_load_failures = {}
providers = Provider.get_available_providers()
for provider in providers:
- try:
- getattr(
- import_module(
- f"{providers_path}.{provider}.{provider_arguments_lib_path}"
- ),
- init_provider_arguments_function,
- )(self)
- except Exception as error:
- logger.critical(
+ if Provider.is_builtin(provider):
+ try:
+ getattr(
+ import_module(
+ f"{providers_path}.{provider}.{provider_arguments_lib_path}"
+ ),
+ init_provider_arguments_function,
+ )(self)
+ except Exception as error:
+ self._builtin_load_failures[provider] = error
+ else:
+ cls = Provider._load_ep_provider(provider)
+ if cls and hasattr(cls, "init_parser"):
+ try:
+ cls.init_parser(self)
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+def enforce_invoked_provider_loaded(self):
+ """Apply selective fail-loud over the failures captured at init time.
+
+ Called by `ProwlerArgumentParser.parse()` AFTER argv normalisation so
+ the invoked provider matches what argparse will dispatch to — including
+ the case where `parse(args=...)` overrode the ambient `sys.argv`.
+
+ Invoked + failed → critical + `sys.exit(1)`. Others → warning.
+ """
+ failures = getattr(self, "_builtin_load_failures", {})
+ if not failures:
+ return
+ invoked = _invoked_provider_from_argv(Provider.get_available_providers())
+ for provider, error in failures.items():
+ if provider == invoked:
+ continue
+ if isinstance(error, ImportError):
+ logger.warning(
+ f"Skipping built-in provider '{provider}' due to missing "
+ f"dependency: {error}. It will be unavailable in this "
+ f"invocation, but the CLI continues because you invoked a "
+ f"different provider."
+ )
+ else:
+ logger.warning(
+ f"Skipping built-in provider '{provider}': "
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- sys.exit(1)
+ if invoked is None or invoked not in failures:
+ return
+ error = failures[invoked]
+ if isinstance(error, ImportError):
+ logger.critical(
+ f"Failed to load arguments for built-in provider '{invoked}'. "
+ f"Missing dependency: {error}. "
+ f"Ensure all required dependencies are installed."
+ )
+ logger.debug("Full traceback:", exc_info=True)
+ else:
+ logger.critical(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ sys.exit(1)
def validate_provider_arguments(arguments: Namespace) -> tuple[bool, str]:
diff --git a/prowler/providers/common/builtin.py b/prowler/providers/common/builtin.py
new file mode 100644
index 0000000000..d60b5483d9
--- /dev/null
+++ b/prowler/providers/common/builtin.py
@@ -0,0 +1,29 @@
+"""Leaf helper for built-in provider detection.
+
+Lives in its own module — with no imports back into `prowler.lib.check` — so
+that callers in `prowler.lib.check.*` can ask "is this provider built-in?"
+without creating an import cycle through `prowler.providers.common.provider`
+(which transitively imports `prowler.config.config` and from there
+`prowler.lib.check.compliance_models` / `prowler.lib.check.external_tool_providers`).
+
+Same rationale as `prowler.lib.check.tool_wrapper`: extracting the predicate
+to a leaf module is the canonical way to break the cycle in this codebase.
+"""
+
+import importlib.util
+
+
+def is_builtin_provider(provider: str) -> bool:
+ """Return True if the provider's own package ships with the SDK.
+
+ Wraps `importlib.util.find_spec` in `try/except (ImportError, ValueError)`
+ because `find_spec` propagates `ModuleNotFoundError` when a parent package
+ in the dotted path does not exist (instead of returning `None`). The
+ try/except is what makes the call safe for external providers, whose
+ package does not live under `prowler.providers.{provider}`.
+ """
+ try:
+ spec = importlib.util.find_spec(f"prowler.providers.{provider}")
+ return spec is not None
+ except (ImportError, ValueError):
+ return False
diff --git a/prowler/providers/common/models.py b/prowler/providers/common/models.py
index ea70252f0a..84e71c4809 100644
--- a/prowler/providers/common/models.py
+++ b/prowler/providers/common/models.py
@@ -4,6 +4,7 @@ from os.path import isdir
from pydantic.v1 import BaseModel
+from prowler.config.config import output_file_timestamp
from prowler.providers.common.provider import Provider
@@ -48,6 +49,16 @@ class ProviderOutputOptions:
if updated_audit_config:
provider._audit_config = updated_audit_config
+ # Secrets validation: --scan-secrets-validate opts into live validation
+ # of discovered secrets. Set the audit_config key directly so it applies
+ # even for providers whose default config does not declare it.
+ self.scan_secrets_validate = getattr(arguments, "scan_secrets_validate", False)
+ if self.scan_secrets_validate:
+ provider = Provider.get_global_provider()
+ audit_config = provider.audit_config or {}
+ audit_config["secrets_validate"] = True
+ provider._audit_config = audit_config
+
# Check output directory, if it is not created -> create it
if self.output_directory and not self.fixer:
if not isdir(self.output_directory):
@@ -69,3 +80,15 @@ class Connection:
is_connected: bool = False
error: Exception = None
+
+
+def default_output_options(provider, arguments, bulk_checks_metadata):
+ """Generic OutputOptions fallback for external providers that do not
+ implement get_output_options, so the run still produces output instead of
+ aborting. Honors arguments.output_filename and otherwise derives a name
+ from the provider type."""
+ output_options = ProviderOutputOptions(arguments, bulk_checks_metadata)
+ output_options.output_filename = getattr(arguments, "output_filename", None) or (
+ f"prowler-output-{provider.type}-{output_file_timestamp}"
+ )
+ return output_options
diff --git a/prowler/providers/common/provider.py b/prowler/providers/common/provider.py
index d76c1b6f2a..d4793adbe7 100644
--- a/prowler/providers/common/provider.py
+++ b/prowler/providers/common/provider.py
@@ -1,4 +1,6 @@
import importlib
+import importlib.metadata
+import importlib.util
import os
import pkgutil
import sys
@@ -136,6 +138,169 @@ class Provider(ABC):
"""
return set()
+ # --- Dynamic provider contract methods (not @abstractmethod for incremental migration) ---
+
+ _cli_help_text: str = ""
+
+ # CLI/SDK-only provider, hidden from the app (API/UI). Defaults True; a
+ # provider opts into the app with ``sdk_only = False``. See get_app_providers().
+ sdk_only: bool = True
+
+ @classmethod
+ def from_cli_args(cls, arguments: Namespace, fixer_config: dict) -> "Provider":
+ """Instantiate the provider from CLI arguments and return the instance.
+
+ The caller wires the returned instance into the global provider slot
+ via Provider.set_global_provider(). Implementations that already call
+ set_global_provider(self) from __init__ are also supported — the call
+ site tolerates a None return in that case.
+ """
+ raise NotImplementedError(f"{cls.__name__} has not implemented from_cli_args()")
+
+ def get_output_options(self, arguments, _bulk_checks_metadata):
+ """Create the provider-specific OutputOptions."""
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented get_output_options()"
+ )
+
+ def get_stdout_detail(self, _finding) -> str:
+ """Return the detail string for stdout reporting (region, location, etc.)."""
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented get_stdout_detail()"
+ )
+
+ def get_finding_sort_key(self) -> Optional[str]:
+ """Return the attribute name to sort findings by, or None for no sorting."""
+ return None
+
+ def get_summary_entity(self) -> tuple:
+ """Return (entity_type, audited_entities) for the summary table."""
+ return (self.type, getattr(self.identity, "account_id", ""))
+
+ def get_finding_output_data(self, _check_output) -> dict:
+ """Return provider-specific fields for Finding.generate_output()."""
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented get_finding_output_data()"
+ )
+
+ def get_html_assessment_summary(self) -> str:
+ """Return the HTML assessment summary card for this provider."""
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented get_html_assessment_summary()"
+ )
+
+ def generate_compliance_output(
+ self,
+ _findings,
+ _bulk_compliance_frameworks,
+ _input_compliance_frameworks,
+ _output_options,
+ _generated_outputs,
+ ) -> None:
+ """Generate compliance CSV output for this provider's frameworks."""
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented generate_compliance_output()"
+ )
+
+ def get_mutelist_finding_args(self) -> dict:
+ """Return extra kwargs for mutelist.is_finding_muted() besides 'finding'.
+
+ External providers must return a dict with the identity key their
+ Mutelist subclass expects, e.g. ``{"account_id": self.identity.account_id}``.
+ The ``finding`` kwarg is added automatically by the caller.
+ """
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented get_mutelist_finding_args()"
+ )
+
+ @classmethod
+ def get_scan_arguments(
+ cls,
+ provider_uid: str,
+ secret: dict,
+ mutelist_content: Optional[dict] = None,
+ ) -> dict:
+ """Build the provider constructor kwargs from a stored uid and secret.
+
+ This is the programmatic construction interface intended for callers
+ that will persist a provider as a single ``uid`` plus a ``secret`` dict
+ (e.g. the API), as opposed to the CLI which passes explicit per-provider
+ flags.
+
+ The base implementation is a default: it passes the secret through, adds
+ the mutelist, and intentionally drops ``provider_uid``. The API consumes
+ this contract for external providers, so an external provider whose uid
+ is part of the scan scope (e.g. a subscription or project id) or that
+ renames/filters secret keys overrides this to inject the uid into the
+ right kwarg; until it does, the base default is not the final shape for
+ that provider. Built-in providers whose scope derives from the uid are
+ mapped on the API side and do not go through this method.
+ """
+ kwargs = {**secret}
+ if mutelist_content is not None:
+ kwargs["mutelist_content"] = mutelist_content
+ return kwargs
+
+ @classmethod
+ def get_connection_arguments(cls, provider_uid: str, secret: dict) -> dict:
+ """Build the ``test_connection`` kwargs from a stored uid and secret.
+
+ Companion to :meth:`get_scan_arguments` for the connection check, which
+ often needs a different shape than the constructor. The base passes the
+ secret through and intentionally drops ``provider_uid``. An external
+ provider whose uid is part of the scope overrides this to add its
+ identity kwarg (and ``provider_id`` where its ``test_connection``
+ expects it); built-in providers are mapped on the API side and do not go
+ through this method.
+ """
+ return {**secret}
+
+ @classmethod
+ def get_credentials_schema(cls) -> dict:
+ """Return the provider's credential schemas keyed by secret type.
+
+ Maps each secret type the provider accepts (``"static"``, ``"role"`` or
+ ``"service_account"``) to the pydantic model that validates a secret of
+ that type. The provider declares which type each schema belongs to, so
+ the API validates a secret against the model for the secret type it is
+ created with and the chosen type stays bound to the shape it claims.
+
+ Each model documents each field via ``Field(description=...)`` and
+ whether it is required (no default) or optional. An empty dict means no
+ schema is declared: the secret is accepted as an object and validated by
+ :meth:`test_connection`.
+ """
+ return {}
+
+ def display_compliance_table(
+ self,
+ _findings: list,
+ _bulk_checks_metadata: dict,
+ _compliance_framework: str,
+ _output_filename: str,
+ _output_directory: str,
+ _compliance_overview: bool,
+ ) -> bool:
+ """Render a custom compliance table in the terminal.
+
+ External providers can override this to display a detailed
+ compliance table (e.g., per-section breakdown). Return True
+ if the table was rendered, False to fall back to the generic table.
+ """
+ raise NotImplementedError(
+ f"{self.__class__.__name__} has not implemented display_compliance_table()"
+ )
+
+ # Class-level flag: True for providers that delegate scanning to an external
+ # tool (e.g. Trivy, promptfoo) and bypass standard check/service loading and
+ # metadata validation. Subclasses override as `is_external_tool_provider = True`.
+ # Kept as a class attribute (not a property) so it can be read from the class
+ # without instantiation — the metadata validators in lib.check.models need to
+ # decide whether to relax validation before any provider instance exists.
+ is_external_tool_provider: bool = False
+
+ # --- End dynamic provider contract methods ---
+
@staticmethod
def get_excluded_regions_from_env() -> set:
"""Parse the PROWLER_AWS_DISALLOWED_REGIONS environment variable.
@@ -159,20 +324,57 @@ class Provider(ABC):
@staticmethod
def init_global_provider(arguments: Namespace) -> None:
try:
- provider_class_path = (
- f"{providers_path}.{arguments.provider}.{arguments.provider}_provider"
- )
- provider_class_name = f"{arguments.provider.capitalize()}Provider"
- provider_class = getattr(
- import_module(provider_class_path), provider_class_name
- )
+ # Delegate class resolution to the public, side-effect-free
+ # resolver. init_global_provider owns the CLI-specific error
+ # handling: a missing transitive dep in a built-in becomes a
+ # logger.critical + sys.exit(1); a completely unknown provider
+ # re-raises so the outer try/except can sys.exit too.
+ try:
+ provider_class = Provider.get_class(arguments.provider)
+ except ImportError as e:
+ if Provider.is_builtin(arguments.provider):
+ # Built-in's transitive dependency is missing — loud CLI error.
+ logger.critical(
+ f"Failed to load built-in provider '{arguments.provider}'. "
+ f"Missing dependency: {e}. "
+ f"Ensure all required dependencies are installed."
+ )
+ logger.debug("Full traceback:", exc_info=True)
+ sys.exit(1)
+ # Unknown or missing external provider — propagate so the
+ # outer try/except can handle it (sys.exit(1) via generic
+ # exception handler).
+ raise
+
+ # Built-in wins on name collision — warn that a same-named
+ # plug-in is ignored. This lives here (not in get_class) so
+ # that `prowler --help` and API callers that resolve a class
+ # without initialising a global provider do not see spurious
+ # warnings. Match by name only — never ep.load() a shadowing
+ # plug-in, or its module code would run during a built-in run.
+ if Provider.is_builtin(arguments.provider) and any(
+ ep.name == arguments.provider
+ for ep in importlib.metadata.entry_points(group="prowler.providers")
+ ):
+ logger.warning(
+ f"Plug-in provider '{arguments.provider}' registered "
+ f"via entry points is being IGNORED — a built-in with "
+ f"the same name exists. To use your plug-in, register "
+ f"it under a different name."
+ )
fixer_config = load_and_validate_config_file(
arguments.provider, arguments.fixer_config
)
+ # Dispatch by exact provider name (equality, not substring) so
+ # external plug-ins whose names contain a built-in substring
+ # (e.g. `awsx`, `azure_gov`, `iac_v2`) cannot be silently routed
+ # to the wrong built-in branch. Anything that doesn't match a
+ # built-in falls through to the dynamic else and uses the
+ # contract's `from_cli_args`.
if not isinstance(Provider._global, provider_class):
- if "aws" in provider_class_name.lower():
+ if arguments.provider == "aws":
excluded_regions = (
set(arguments.excluded_region)
if getattr(arguments, "excluded_region", None)
@@ -196,7 +398,7 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "azure" in provider_class_name.lower():
+ elif arguments.provider == "azure":
provider_class(
az_cli_auth=arguments.az_cli_auth,
sp_env_auth=arguments.sp_env_auth,
@@ -205,11 +407,12 @@ class Provider(ABC):
tenant_id=arguments.tenant_id,
region=arguments.azure_region,
subscription_ids=arguments.subscription_id,
+ resource_groups=arguments.resource_groups,
config_path=arguments.config_file,
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "gcp" in provider_class_name.lower():
+ elif arguments.provider == "gcp":
provider_class(
retries_max_attempts=arguments.gcp_retries_max_attempts,
organization_id=arguments.organization_id,
@@ -223,7 +426,7 @@ class Provider(ABC):
fixer_config=fixer_config,
skip_api_check=arguments.skip_api_check,
)
- elif "kubernetes" in provider_class_name.lower():
+ elif arguments.provider == "kubernetes":
provider_class(
kubeconfig_file=arguments.kubeconfig_file,
context=arguments.context,
@@ -233,7 +436,7 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "m365" in provider_class_name.lower():
+ elif arguments.provider == "m365":
provider_class(
region=arguments.region,
config_path=arguments.config_file,
@@ -247,7 +450,7 @@ class Provider(ABC):
init_modules=arguments.init_modules,
fixer_config=fixer_config,
)
- elif "nhn" in provider_class_name.lower():
+ elif arguments.provider == "nhn":
provider_class(
username=arguments.nhn_username,
password=arguments.nhn_password,
@@ -256,7 +459,26 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "github" in provider_class_name.lower():
+ elif arguments.provider == "stackit":
+ provider_class(
+ project_id=arguments.stackit_project_id,
+ service_account_key_path=getattr(
+ arguments, "stackit_service_account_key_path", None
+ ),
+ service_account_key=getattr(
+ arguments, "stackit_service_account_key", None
+ ),
+ regions=(
+ set(arguments.stackit_region)
+ if arguments.stackit_region
+ else None
+ ),
+ scan_unused_services=arguments.scan_unused_services,
+ config_path=arguments.config_file,
+ mutelist_path=arguments.mutelist_file,
+ fixer_config=fixer_config,
+ )
+ elif arguments.provider == "github":
orgs = []
repos = []
@@ -288,13 +510,13 @@ class Provider(ABC):
exclude_workflows=getattr(arguments, "exclude_workflows", []),
fixer_config=fixer_config,
)
- elif "googleworkspace" in provider_class_name.lower():
+ elif arguments.provider == "googleworkspace":
provider_class(
config_path=arguments.config_file,
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "cloudflare" in provider_class_name.lower():
+ elif arguments.provider == "cloudflare":
provider_class(
filter_zones=arguments.region,
filter_accounts=arguments.account_id,
@@ -302,7 +524,7 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "iac" in provider_class_name.lower():
+ elif arguments.provider == "iac":
provider_class(
scan_path=arguments.scan_path,
scan_repository_url=arguments.scan_repository_url,
@@ -315,13 +537,13 @@ class Provider(ABC):
oauth_app_token=arguments.oauth_app_token,
provider_uid=arguments.provider_uid,
)
- elif "llm" in provider_class_name.lower():
+ elif arguments.provider == "llm":
provider_class(
max_concurrency=arguments.max_concurrency,
config_path=arguments.config_file,
fixer_config=fixer_config,
)
- elif "image" in provider_class_name.lower():
+ elif arguments.provider == "image":
provider_class(
images=arguments.images,
image_list_file=arguments.image_list_file,
@@ -339,7 +561,7 @@ class Provider(ABC):
registry_insecure=arguments.registry_insecure,
registry_list_images=arguments.registry_list_images,
)
- elif "mongodbatlas" in provider_class_name.lower():
+ elif arguments.provider == "mongodbatlas":
provider_class(
atlas_public_key=arguments.atlas_public_key,
atlas_private_key=arguments.atlas_private_key,
@@ -348,7 +570,7 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "oraclecloud" in provider_class_name.lower():
+ elif arguments.provider == "oraclecloud":
provider_class(
oci_config_file=arguments.oci_config_file,
profile=arguments.profile,
@@ -359,7 +581,7 @@ class Provider(ABC):
fixer_config=fixer_config,
use_instance_principal=arguments.use_instance_principal,
)
- elif "openstack" in provider_class_name.lower():
+ elif arguments.provider == "openstack":
provider_class(
clouds_yaml_file=getattr(arguments, "clouds_yaml_file", None),
clouds_yaml_content=getattr(
@@ -384,7 +606,7 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "alibabacloud" in provider_class_name.lower():
+ elif arguments.provider == "alibabacloud":
provider_class(
role_arn=arguments.role_arn,
role_session_name=arguments.role_session_name,
@@ -396,14 +618,24 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "vercel" in provider_class_name.lower():
+ elif arguments.provider == "vercel":
provider_class(
projects=getattr(arguments, "project", None),
config_path=arguments.config_file,
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "okta" in provider_class_name.lower():
+ elif arguments.provider == "e2enetworks":
+ provider_class(
+ api_key=getattr(arguments, "e2e_networks_api_key", None),
+ auth_token=getattr(arguments, "e2e_networks_auth_token", None),
+ project_id=getattr(arguments, "e2e_networks_project_id", None),
+ locations=getattr(arguments, "region", None),
+ config_path=arguments.config_file,
+ mutelist_path=arguments.mutelist_file,
+ fixer_config=fixer_config,
+ )
+ elif arguments.provider == "okta":
provider_class(
okta_org_domain=getattr(arguments, "okta_org_domain", ""),
okta_client_id=getattr(arguments, "okta_client_id", ""),
@@ -412,11 +644,17 @@ class Provider(ABC):
arguments, "okta_private_key_file", ""
),
okta_scopes=getattr(arguments, "okta_scopes", None),
+ okta_retries_max_attempts=getattr(
+ arguments, "okta_retries_max_attempts", None
+ ),
+ okta_requests_per_second=getattr(
+ arguments, "okta_requests_per_second", None
+ ),
config_path=arguments.config_file,
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
- elif "scaleway" in provider_class_name.lower():
+ elif arguments.provider == "scaleway":
# Credentials are read from the SCW_ACCESS_KEY /
# SCW_SECRET_KEY env vars by the provider itself; there
# are no credential CLI flags to avoid leaking secrets.
@@ -428,6 +666,28 @@ class Provider(ABC):
mutelist_path=arguments.mutelist_file,
fixer_config=fixer_config,
)
+ elif arguments.provider == "linode":
+ # Credentials are read from the LINODE_TOKEN env var by the
+ # provider itself; there are no credential CLI flags to
+ # avoid leaking secrets.
+ provider_class(
+ config_path=arguments.config_file,
+ mutelist_path=arguments.mutelist_file,
+ fixer_config=fixer_config,
+ regions=getattr(arguments, "region", None),
+ )
+ else:
+ # Dynamic fallback: any external/custom provider.
+ # Honor the from_cli_args type hint (-> Provider): if the
+ # implementation returns an instance, wire it as the global
+ # provider here. Implementations that call
+ # set_global_provider(self) from __init__ return None and
+ # remain supported (the condition below is a no-op for them).
+ provider_instance = provider_class.from_cli_args(
+ arguments, fixer_config
+ )
+ if provider_instance is not None:
+ Provider.set_global_provider(provider_instance)
except TypeError as error:
logger.critical(
@@ -440,17 +700,163 @@ class Provider(ABC):
)
sys.exit(1)
+ # Cache for entry-point provider classes {name: class}
+ _ep_providers: dict = {}
+
@staticmethod
def get_available_providers() -> list[str]:
"""get_available_providers returns a list of the available providers"""
- providers = []
- # Dynamically import the package based on its string path
+ providers = set()
+ # Built-in providers from local package
prowler_providers = importlib.import_module(providers_path)
- # Iterate over all modules found in the prowler_providers package
for _, provider, ispkg in pkgutil.iter_modules(prowler_providers.__path__):
if provider != "common" and ispkg:
- providers.append(provider)
- return providers
+ providers.add(provider)
+ # External providers registered via entry points
+ for ep in importlib.metadata.entry_points(group="prowler.providers"):
+ providers.add(ep.name)
+ return sorted(providers)
+
+ @staticmethod
+ def get_app_providers() -> list[str]:
+ """Return the providers the app (API/UI) may expose: those with
+ ``sdk_only = False``.
+
+ Counterpart of :meth:`get_available_providers`, which lists every
+ provider for the CLI. A provider whose class cannot be imported is
+ treated as ``sdk_only`` (excluded) so a broken plug-in never leaks in.
+ """
+ app_providers = []
+ for name in Provider.get_available_providers():
+ try:
+ provider_class = Provider.get_class(name)
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ continue
+ if not getattr(provider_class, "sdk_only", True):
+ app_providers.append(name)
+ return app_providers
+
+ @staticmethod
+ def is_tool_wrapper_provider(provider: str) -> bool:
+ """Return True if the provider delegates scanning to an external tool.
+
+ Delegates to `prowler.lib.check.tool_wrapper.is_tool_wrapper_provider`,
+ the leaf module that holds the actual logic. Kept on `Provider` as a
+ convenience entry point for callers that already import `Provider`.
+ """
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider as _impl
+
+ return _impl(provider)
+
+ @staticmethod
+ def is_builtin(provider: str) -> bool:
+ """Return True if the provider's own package is importable as a built-in.
+
+ Delegates to `prowler.providers.common.builtin.is_builtin_provider`,
+ the leaf module that holds the actual check. Kept on `Provider` as a
+ convenience entry point for callers that already import `Provider`.
+ Call sites in `prowler.lib.check.*` should import from the leaf
+ directly to avoid the import cycle through this module.
+ """
+ from prowler.providers.common.builtin import is_builtin_provider as _impl
+
+ return _impl(provider)
+
+ @staticmethod
+ def _load_ep_provider(name: str):
+ """Load an external provider class from entry points, with cache.
+
+ Caches both hits and misses so repeated lookups for unknown names do
+ not re-iterate entry_points(). Symmetric with
+ tool_wrapper._ep_class_cache.
+ """
+ if name in Provider._ep_providers:
+ return Provider._ep_providers[name]
+ for ep in importlib.metadata.entry_points(group="prowler.providers"):
+ if ep.name == name:
+ try:
+ cls = ep.load()
+ Provider._ep_providers[name] = cls
+ return cls
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ Provider._ep_providers[name] = None
+ return None
+
+ @staticmethod
+ def get_class(provider: str) -> type:
+ """Resolve the provider class for a name (built-in or entry-point).
+
+ Does not call ``sys.exit`` and does not initialize the global
+ provider (it may populate the ``_ep_providers`` memoization cache).
+ Collision warnings are emitted by ``init_global_provider``, not here.
+ The caller handles errors (CLI exits; the API can return HTTP 400).
+
+ Args:
+ provider: Provider name, e.g. ``"aws"`` or an external plug-in.
+
+ Returns:
+ The provider class (a subclass of :class:`Provider`).
+
+ Raises:
+ ImportError: If not found as built-in or entry point, a built-in's
+ transitive dependency is missing, or an entry point resolves to
+ an object that is not a subclass of :class:`Provider`.
+ """
+ if Provider.is_builtin(provider):
+ provider_class_path = f"{providers_path}.{provider}.{provider}_provider"
+ provider_class_name = f"{provider.capitalize()}Provider"
+ # Let ImportError propagate — the caller decides whether to
+ # sys.exit (CLI) or return HTTP 400 (API).
+ module = import_module(provider_class_path)
+ try:
+ return getattr(module, provider_class_name)
+ except AttributeError as error:
+ # is_builtin already confirmed this is a built-in, so the
+ # module MUST define the expected class. A missing class is a
+ # broken built-in contract — raise rather than fall back to a
+ # same-named external plug-in, which would contradict
+ # is_builtin and silently return a foreign class.
+ raise ImportError(
+ f"Built-in provider '{provider}' module "
+ f"'{provider_class_path}' does not define expected class "
+ f"'{provider_class_name}'"
+ ) from error
+
+ cls = Provider._load_ep_provider(provider)
+ if cls is None:
+ raise ImportError(
+ f"Provider '{provider}' not found as built-in or entry point"
+ )
+ # ep.load() can return any object; enforce the public contract that
+ # get_class returns a Provider subclass. isinstance(cls, type) guards
+ # issubclass against a TypeError when cls is not a class at all.
+ if not (isinstance(cls, type) and issubclass(cls, Provider)):
+ raise ImportError(
+ f"Entry-point provider '{provider}' resolved to {cls!r}, "
+ f"which is not a subclass of Provider"
+ )
+ return cls
+
+ @staticmethod
+ def get_providers_help_text() -> dict:
+ """Returns a dict of {provider_name: cli_help_text} for all available providers."""
+ help_text = {}
+ for name in Provider.get_available_providers():
+ try:
+ cls = Provider.get_class(name)
+ help_text[name] = getattr(cls, "_cli_help_text", "")
+ except Exception as error:
+ logger.warning(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ help_text[name] = ""
+ return help_text
@staticmethod
def update_provider_config(audit_config: dict, variable: str, value: str):
diff --git a/tests/providers/alibabacloud/services/sls/sls_root_account_usage_alert_enabled/__init__.py b/prowler/providers/e2enetworks/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/sls_root_account_usage_alert_enabled/__init__.py
rename to prowler/providers/e2enetworks/__init__.py
diff --git a/prowler/providers/e2enetworks/e2enetworks_provider.py b/prowler/providers/e2enetworks/e2enetworks_provider.py
new file mode 100644
index 0000000000..480f5ee4a8
--- /dev/null
+++ b/prowler/providers/e2enetworks/e2enetworks_provider.py
@@ -0,0 +1,258 @@
+import os
+
+import requests
+from colorama import Fore, Style
+
+from prowler.config.config import (
+ default_config_file_path,
+ get_default_mute_file_path,
+ load_and_validate_config_file,
+)
+from prowler.lib.logger import logger
+from prowler.lib.utils.utils import print_boxes
+from prowler.providers.common.models import Audit_Metadata, Connection
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.exceptions.exceptions import (
+ E2eNetworksCredentialsError,
+ E2eNetworksSessionError,
+)
+from prowler.providers.e2enetworks.lib.mutelist.mutelist import E2eNetworksMutelist
+from prowler.providers.e2enetworks.models import (
+ E2E_DEFAULT_LOCATIONS,
+ E2eNetworksIdentityInfo,
+ E2eNetworksSession,
+)
+
+
+class E2enetworksProvider(Provider):
+ """Provider class for E2E Networks."""
+
+ _type: str = "e2enetworks"
+ _session: E2eNetworksSession
+ _identity: E2eNetworksIdentityInfo
+ _audit_config: dict
+ _fixer_config: dict
+ _mutelist: E2eNetworksMutelist
+ audit_metadata: Audit_Metadata
+
+ def __init__(
+ self,
+ api_key: str = None,
+ auth_token: str = None,
+ project_id: str | int = None,
+ locations: list[str] | None = None,
+ config_path: str = None,
+ fixer_config: dict = None,
+ mutelist_path: str = None,
+ mutelist_content: dict = None,
+ ):
+ logger.info("Initializing E2E Networks Provider...")
+
+ self._api_key = api_key or os.getenv("E2E_NETWORKS_API_KEY")
+ self._auth_token = auth_token or os.getenv("E2E_NETWORKS_AUTH_TOKEN")
+ project_value = project_id or os.getenv("E2E_NETWORKS_PROJECT_ID")
+ self._project_id = int(project_value) if project_value else None
+ self._locations = self._resolve_locations(locations)
+
+ if not self._api_key or not self._auth_token or self._project_id is None:
+ raise E2eNetworksCredentialsError(
+ message="E2enetworksProvider requires api_key, auth_token, and project_id."
+ )
+
+ self._fixer_config = fixer_config if fixer_config else {}
+ if not config_path:
+ config_path = default_config_file_path
+ self._audit_config = load_and_validate_config_file(self._type, config_path)
+
+ if mutelist_content is not None:
+ self._mutelist = E2eNetworksMutelist(mutelist_content=mutelist_content)
+ else:
+ if not mutelist_path:
+ mutelist_path = get_default_mute_file_path(self._type)
+ self._mutelist = E2eNetworksMutelist(mutelist_path=mutelist_path)
+
+ self._session = E2enetworksProvider.setup_session(
+ api_key=self._api_key,
+ auth_token=self._auth_token,
+ project_id=self._project_id,
+ locations=self._locations,
+ )
+ self._identity = E2eNetworksIdentityInfo(
+ project_id=self._project_id,
+ locations=self._locations,
+ )
+
+ Provider.set_global_provider(self)
+
+ @staticmethod
+ def _resolve_locations(locations: list[str] | None) -> list[str]:
+ """Resolve scan locations from CLI args, env vars, or defaults.
+
+ Args:
+ locations: Optional list of location names from CLI arguments.
+
+ Returns:
+ The resolved list of E2E Networks locations to scan.
+ """
+ if locations:
+ return locations
+
+ env_region = os.getenv("E2E_NETWORKS_REGION")
+ if env_region:
+ return [env_region]
+
+ return list(E2E_DEFAULT_LOCATIONS)
+
+ @property
+ def type(self) -> str:
+ return self._type
+
+ @property
+ def session(self) -> E2eNetworksSession:
+ return self._session
+
+ @property
+ def identity(self) -> E2eNetworksIdentityInfo:
+ return self._identity
+
+ @property
+ def audit_config(self) -> dict:
+ return self._audit_config
+
+ @property
+ def fixer_config(self) -> dict:
+ return self._fixer_config
+
+ @property
+ def mutelist(self) -> E2eNetworksMutelist:
+ return self._mutelist
+
+ @staticmethod
+ def setup_session(
+ api_key: str,
+ auth_token: str,
+ project_id: int,
+ locations: list[str],
+ ) -> E2eNetworksSession:
+ """Create an authenticated E2E Networks API session.
+
+ Args:
+ api_key: E2E Networks API key.
+ auth_token: Bearer auth token for the MyAccount API.
+ project_id: E2E Networks project identifier.
+ locations: Locations included in the session scope.
+
+ Returns:
+ A configured E2eNetworksSession with an HTTP client.
+
+ Raises:
+ E2eNetworksSessionError: If session initialization fails.
+ """
+ try:
+ http_session = requests.Session()
+ http_session.headers.update(
+ {
+ "Authorization": f"Bearer {auth_token}",
+ "Content-Type": "application/json",
+ }
+ )
+ return E2eNetworksSession(
+ api_key=api_key,
+ auth_token=auth_token,
+ project_id=project_id,
+ locations=locations,
+ http_session=http_session,
+ )
+ except Exception as error:
+ raise E2eNetworksSessionError(
+ message="Failed to initialize E2E Networks session.",
+ original_exception=error,
+ ) from error
+
+ def print_credentials(self) -> None:
+ """Print the E2E Networks scan scope to stdout.
+
+ The API key and auth token are never printed, matching the behavior of
+ the other Prowler providers, which only report identity and scope.
+ """
+ report_lines = [
+ f" Authentication: {Fore.YELLOW}API Key{Style.RESET_ALL}",
+ f" Project ID: {self._project_id}",
+ f" Locations: {', '.join(self._locations)}",
+ ]
+ report_title = (
+ f"{Style.BRIGHT}Using the E2E Networks credentials below:{Style.RESET_ALL}"
+ )
+ print_boxes(report_lines, report_title)
+
+ @staticmethod
+ def test_connection(
+ api_key: str = None,
+ auth_token: str = None,
+ project_id: str | int = None,
+ locations: list[str] | None = None,
+ raise_on_exception: bool = True,
+ ) -> Connection:
+ """Test connectivity to the E2E Networks MyAccount API.
+
+ Args:
+ api_key: E2E Networks API key. Falls back to E2E_NETWORKS_API_KEY.
+ auth_token: Bearer auth token. Falls back to E2E_NETWORKS_AUTH_TOKEN.
+ project_id: Project identifier. Falls back to E2E_NETWORKS_PROJECT_ID.
+ locations: Optional locations to use for the probe request.
+ raise_on_exception: Whether to re-raise caught exceptions.
+
+ Returns:
+ Connection indicating success or containing the error.
+
+ Raises:
+ E2eNetworksCredentialsError: If required credentials are missing.
+ E2eNetworksSessionError: If the API returns a non-200 response.
+ Exception: Any unexpected error when raise_on_exception is True.
+ """
+ try:
+ api_key = api_key or os.getenv("E2E_NETWORKS_API_KEY")
+ auth_token = auth_token or os.getenv("E2E_NETWORKS_AUTH_TOKEN")
+ project_value = project_id or os.getenv("E2E_NETWORKS_PROJECT_ID")
+ project_id_int = int(project_value) if project_value else None
+ resolved_locations = locations or (
+ [os.getenv("E2E_NETWORKS_REGION")]
+ if os.getenv("E2E_NETWORKS_REGION")
+ else list(E2E_DEFAULT_LOCATIONS)
+ )
+
+ if not api_key or not auth_token or project_id_int is None:
+ raise E2eNetworksCredentialsError(
+ message="E2E Networks test_connection requires api_key, auth_token, and project_id."
+ )
+
+ session = E2enetworksProvider.setup_session(
+ api_key=api_key,
+ auth_token=auth_token,
+ project_id=project_id_int,
+ locations=resolved_locations,
+ )
+ response = session.http_session.get(
+ f"{session.base_url}/nodes/",
+ params={
+ "apikey": session.api_key,
+ "project_id": session.project_id,
+ "location": resolved_locations[0],
+ },
+ timeout=30,
+ )
+ if response.status_code != 200:
+ error_msg = (
+ f"E2E Networks connection failed with status {response.status_code}: "
+ f"{response.text}"
+ )
+ raise E2eNetworksSessionError(message=error_msg)
+
+ return Connection(is_connected=True)
+ except Exception as error:
+ logger.critical(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ if raise_on_exception:
+ raise error
+ return Connection(error=error)
diff --git a/tests/providers/alibabacloud/services/sls/sls_unauthorized_api_calls_alert_enabled/__init__.py b/prowler/providers/e2enetworks/exceptions/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/sls/sls_unauthorized_api_calls_alert_enabled/__init__.py
rename to prowler/providers/e2enetworks/exceptions/__init__.py
diff --git a/prowler/providers/e2enetworks/exceptions/exceptions.py b/prowler/providers/e2enetworks/exceptions/exceptions.py
new file mode 100644
index 0000000000..e01179bbc4
--- /dev/null
+++ b/prowler/providers/e2enetworks/exceptions/exceptions.py
@@ -0,0 +1,93 @@
+from prowler.exceptions.exceptions import ProwlerException
+
+
+# Exceptions codes from 19000 to 19999 are reserved for E2E Networks exceptions
+class E2eNetworksBaseException(ProwlerException):
+ """Base class for E2E Networks errors."""
+
+ E2E_NETWORKS_ERROR_CODES = {
+ (19000, "E2eNetworksCredentialsError"): {
+ "message": "E2E Networks credentials not found or invalid",
+ "remediation": "Provide a valid API key, auth token and project id via the E2E_NETWORKS_API_KEY, E2E_NETWORKS_AUTH_TOKEN and E2E_NETWORKS_PROJECT_ID environment variables.",
+ },
+ (19001, "E2eNetworksAuthenticationError"): {
+ "message": "E2E Networks authentication failed",
+ "remediation": "Verify the E2E Networks API key and auth token and ensure the project id is correct and accessible.",
+ },
+ (19002, "E2eNetworksSessionError"): {
+ "message": "E2E Networks session setup failed",
+ "remediation": "Review the E2E Networks credentials and network connectivity to the MyAccount API.",
+ },
+ (19003, "E2eNetworksAPIError"): {
+ "message": "E2E Networks API request failed",
+ "remediation": "Check the E2E Networks MyAccount API status and that the credentials grant access to the requested resource.",
+ },
+ (19004, "E2eNetworksIdentityError"): {
+ "message": "Unable to retrieve E2E Networks identity or project information",
+ "remediation": "Ensure the credentials allow access to the E2E Networks project and account APIs.",
+ },
+ }
+
+ def __init__(self, code, file=None, original_exception=None, message=None):
+ provider = "E2E"
+ error_info = self.E2E_NETWORKS_ERROR_CODES.get((code, self.__class__.__name__))
+ if error_info is None:
+ error_info = {
+ "message": message or "Unknown E2E Networks error",
+ "remediation": "Check the E2E Networks MyAccount API documentation for more details.",
+ }
+ elif message:
+ error_info = error_info.copy()
+ error_info["message"] = message
+ super().__init__(
+ code=code,
+ source=provider,
+ file=file,
+ original_exception=original_exception,
+ error_info=error_info,
+ )
+
+
+class E2eNetworksCredentialsError(E2eNetworksBaseException):
+ """Exception for E2E Networks credential errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 19000, file=file, original_exception=original_exception, message=message
+ )
+
+
+class E2eNetworksAuthenticationError(E2eNetworksBaseException):
+ """Exception for E2E Networks authentication errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 19001, file=file, original_exception=original_exception, message=message
+ )
+
+
+class E2eNetworksSessionError(E2eNetworksBaseException):
+ """Exception for E2E Networks session setup errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 19002, file=file, original_exception=original_exception, message=message
+ )
+
+
+class E2eNetworksAPIError(E2eNetworksBaseException):
+ """Exception for E2E Networks API request errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 19003, file=file, original_exception=original_exception, message=message
+ )
+
+
+class E2eNetworksIdentityError(E2eNetworksBaseException):
+ """Exception for E2E Networks identity errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 19004, file=file, original_exception=original_exception, message=message
+ )
diff --git a/tests/providers/alibabacloud/services/vpc/__init__.py b/prowler/providers/e2enetworks/lib/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/vpc/__init__.py
rename to prowler/providers/e2enetworks/lib/__init__.py
diff --git a/tests/providers/alibabacloud/services/vpc/vpc_flow_logs_enabled/__init__.py b/prowler/providers/e2enetworks/lib/api/__init__.py
similarity index 100%
rename from tests/providers/alibabacloud/services/vpc/vpc_flow_logs_enabled/__init__.py
rename to prowler/providers/e2enetworks/lib/api/__init__.py
diff --git a/prowler/providers/e2enetworks/lib/api/client.py b/prowler/providers/e2enetworks/lib/api/client.py
new file mode 100644
index 0000000000..1025bd815e
--- /dev/null
+++ b/prowler/providers/e2enetworks/lib/api/client.py
@@ -0,0 +1,109 @@
+from __future__ import annotations
+
+import re
+from typing import Any
+
+import requests
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.exceptions.exceptions import E2eNetworksAPIError
+from prowler.providers.e2enetworks.models import E2eNetworksSession
+
+
+def _redact_sensitive_values(message: str) -> str:
+ """Redact E2E Networks secrets from request error messages."""
+ redacted = re.sub(r"(?i)(apikey=)[^&\s]+", r"\1REDACTED", message)
+ return re.sub(
+ r"(?i)(Authorization:\s*Bearer\s+|Bearer\s+)[^\s,;]+",
+ r"\1REDACTED",
+ redacted,
+ )
+
+
+class E2eNetworksAPIClient:
+ """Shared HTTP client for E2E Networks MyAccount API requests."""
+
+ def __init__(self, session: E2eNetworksSession):
+ self.session = session
+
+ def _auth_params(self, location: str, extra: dict | None = None) -> dict[str, Any]:
+ params = {
+ "apikey": self.session.api_key,
+ "project_id": self.session.project_id,
+ "location": location,
+ }
+ if extra:
+ params.update(extra)
+ return params
+
+ def get(
+ self,
+ path: str,
+ location: str,
+ params: dict | None = None,
+ timeout: int = 30,
+ ) -> dict:
+ """Perform a GET request against the E2E Networks API."""
+ url = f"{self.session.base_url}{path}"
+ query_params = self._auth_params(location, params)
+ try:
+ response = self.session.http_session.get(
+ url,
+ params=query_params,
+ timeout=timeout,
+ )
+ response.raise_for_status()
+ payload = response.json()
+ if not isinstance(payload, dict):
+ return {"data": payload}
+ return payload
+ except requests.exceptions.RequestException as error:
+ redacted_error = _redact_sensitive_values(str(error))
+ logger.error(
+ f"E2E API GET {path} failed: {error.__class__.__name__}: {redacted_error}"
+ )
+ raise E2eNetworksAPIError(
+ message=f"GET {path} failed for location {location}",
+ original_exception=Exception(redacted_error),
+ ) from error
+
+ def get_data(
+ self,
+ path: str,
+ location: str,
+ params: dict | None = None,
+ ) -> list | dict:
+ """Return the `data` field from a standard E2E API envelope."""
+ payload = self.get(path, location=location, params=params)
+ return payload.get("data", [])
+
+ def paginate(
+ self,
+ path: str,
+ location: str,
+ params: dict | None = None,
+ per_page: int = 100,
+ ) -> list:
+ """Iterate page_no/per_page style paginated list endpoints."""
+ all_items: list = []
+ page_no = 1
+ total_pages = 1
+
+ while page_no <= total_pages:
+ page_params = {"page_no": page_no, "per_page": per_page}
+ if params:
+ page_params.update(params)
+
+ payload = self.get(path, location=location, params=page_params)
+ data = payload.get("data", [])
+ if isinstance(data, list):
+ all_items.extend(data)
+ elif isinstance(data, dict):
+ all_items.extend(data.values())
+
+ total_pages = int(payload.get("total_page_number", page_no))
+ if not data:
+ break
+ page_no += 1
+
+ return all_items
diff --git a/tests/providers/aws/lib/cloudtrail_timeline/__init__.py b/prowler/providers/e2enetworks/lib/arguments/__init__.py
similarity index 100%
rename from tests/providers/aws/lib/cloudtrail_timeline/__init__.py
rename to prowler/providers/e2enetworks/lib/arguments/__init__.py
diff --git a/prowler/providers/e2enetworks/lib/arguments/arguments.py b/prowler/providers/e2enetworks/lib/arguments/arguments.py
new file mode 100644
index 0000000000..fde5ff6355
--- /dev/null
+++ b/prowler/providers/e2enetworks/lib/arguments/arguments.py
@@ -0,0 +1,68 @@
+import os
+
+SENSITIVE_ARGUMENTS = frozenset({"--e2e-networks-api-key", "--e2e-networks-auth-token"})
+
+
+def init_parser(self):
+ """Init the E2E Networks Provider CLI parser."""
+ e2enetworks_parser = self.subparsers.add_parser(
+ "e2enetworks",
+ parents=[self.common_providers_parser],
+ help="E2E Networks Provider",
+ )
+
+ auth_group = e2enetworks_parser.add_argument_group("Authentication")
+ auth_group.add_argument(
+ "--e2e-networks-api-key",
+ nargs="?",
+ default=None,
+ metavar="E2E_NETWORKS_API_KEY",
+ help="E2E Networks API key. Use E2E_NETWORKS_API_KEY env var instead of passing directly.",
+ )
+ auth_group.add_argument(
+ "--e2e-networks-auth-token",
+ nargs="?",
+ default=None,
+ metavar="E2E_NETWORKS_AUTH_TOKEN",
+ help="E2E Networks auth token. Use E2E_NETWORKS_AUTH_TOKEN env var instead of passing directly.",
+ )
+ auth_group.add_argument(
+ "--e2e-networks-project-id",
+ nargs="?",
+ default=None,
+ metavar="E2E_NETWORKS_PROJECT_ID",
+ help="E2E Networks project ID. Use E2E_NETWORKS_PROJECT_ID env var instead of passing directly.",
+ )
+
+ regions_subparser = e2enetworks_parser.add_argument_group("Regions")
+ regions_subparser.add_argument(
+ "--region",
+ "--filter-region",
+ "-f",
+ nargs="+",
+ default=None,
+ metavar="REGION",
+ help="E2E Networks region(s) to scan (e.g. Delhi Chennai). If omitted, "
+ "uses E2E_NETWORKS_REGION or scans all regions (Delhi, Chennai).",
+ )
+
+
+def validate_arguments(arguments) -> tuple[bool, str]:
+ """Validate E2E Networks provider CLI arguments.
+
+ Only argument consistency is checked here so that listing operations such as
+ ``--list-checks`` and ``--list-services`` run without credentials. Credential
+ presence (API key, auth token and project ID) is enforced later at provider
+ initialization, when an actual scan is performed.
+ """
+ project_id = arguments.e2e_networks_project_id or os.getenv(
+ "E2E_NETWORKS_PROJECT_ID"
+ )
+
+ if project_id is not None:
+ try:
+ int(project_id)
+ except (TypeError, ValueError):
+ return False, "E2E Networks project ID must be an integer."
+
+ return True, ""
diff --git a/tests/providers/aws/services/codebuild/codebuild_project_not_publicly_accessible/__init__.py b/prowler/providers/e2enetworks/lib/mutelist/__init__.py
similarity index 100%
rename from tests/providers/aws/services/codebuild/codebuild_project_not_publicly_accessible/__init__.py
rename to prowler/providers/e2enetworks/lib/mutelist/__init__.py
diff --git a/prowler/providers/e2enetworks/lib/mutelist/mutelist.py b/prowler/providers/e2enetworks/lib/mutelist/mutelist.py
new file mode 100644
index 0000000000..6468169e17
--- /dev/null
+++ b/prowler/providers/e2enetworks/lib/mutelist/mutelist.py
@@ -0,0 +1,27 @@
+"""E2E Networks mutelist support for suppressing findings."""
+
+from prowler.lib.check.models import CheckReportE2eNetworks
+from prowler.lib.mutelist.mutelist import Mutelist
+from prowler.lib.outputs.utils import unroll_dict, unroll_tags
+
+
+class E2eNetworksMutelist(Mutelist):
+ """Mutelist implementation for E2E Networks check findings."""
+
+ def is_finding_muted(self, **kwargs) -> bool:
+ """Determine whether an E2E Networks finding is muted.
+
+ Args:
+ **kwargs: Keyword arguments; must include ``finding``.
+
+ Returns:
+ True if the finding matches a mutelist entry, otherwise False.
+ """
+ finding: CheckReportE2eNetworks = kwargs["finding"]
+ return self.is_muted(
+ finding.resource_id,
+ finding.check_metadata.CheckID,
+ finding.location,
+ finding.resource_name,
+ unroll_dict(unroll_tags(finding.resource_tags)),
+ )
diff --git a/tests/providers/aws/services/ec2/ec2_securitygroup_allow_ingress_from_internet_to_any_port_from_ip/__init__.py b/prowler/providers/e2enetworks/lib/service/__init__.py
similarity index 100%
rename from tests/providers/aws/services/ec2/ec2_securitygroup_allow_ingress_from_internet_to_any_port_from_ip/__init__.py
rename to prowler/providers/e2enetworks/lib/service/__init__.py
diff --git a/prowler/providers/e2enetworks/lib/service/service.py b/prowler/providers/e2enetworks/lib/service/service.py
new file mode 100644
index 0000000000..7d5b51f463
--- /dev/null
+++ b/prowler/providers/e2enetworks/lib/service/service.py
@@ -0,0 +1,19 @@
+from prowler.providers.e2enetworks.e2enetworks_provider import E2enetworksProvider
+from prowler.providers.e2enetworks.lib.api.client import E2eNetworksAPIClient
+
+
+class E2eNetworksService:
+ """Base class for E2E Networks services."""
+
+ def __init__(self, service: str, provider: E2enetworksProvider):
+ """Initialize an E2E Networks service client.
+
+ Args:
+ service: Service name used for logging and configuration lookup.
+ provider: The active E2E Networks provider instance.
+ """
+ self.provider = provider
+ self.audit_config = provider.audit_config
+ self.fixer_config = provider.fixer_config
+ self.service = service.lower() if not service.islower() else service
+ self.client = E2eNetworksAPIClient(provider.session)
diff --git a/prowler/providers/e2enetworks/models.py b/prowler/providers/e2enetworks/models.py
new file mode 100644
index 0000000000..84d6bf4e57
--- /dev/null
+++ b/prowler/providers/e2enetworks/models.py
@@ -0,0 +1,53 @@
+from typing import Any
+
+from pydantic import BaseModel, Field
+
+from prowler.config.config import output_file_timestamp
+from prowler.providers.common.models import ProviderOutputOptions
+
+E2E_DEFAULT_LOCATIONS = ("Delhi", "Chennai")
+E2E_BASE_URL = "https://api.e2enetworks.com/myaccount/api/v1"
+
+
+class E2eNetworksSession(BaseModel):
+ """E2E Networks API session information."""
+
+ api_key: str = Field(exclude=True, repr=False)
+ auth_token: str = Field(exclude=True, repr=False)
+ project_id: int
+ locations: list[str]
+ base_url: str = E2E_BASE_URL
+ http_session: Any = Field(default=None, exclude=True)
+
+
+class E2eNetworksIdentityInfo(BaseModel):
+ """E2E Networks identity and scoping information."""
+
+ project_id: int
+ locations: list[str]
+
+
+class E2eNetworksOutputOptions(ProviderOutputOptions):
+ """Customize output filenames for E2E Networks scans."""
+
+ def __init__(
+ self,
+ arguments: object,
+ bulk_checks_metadata: dict,
+ identity: E2eNetworksIdentityInfo,
+ ) -> None:
+ """Initialize E2E Networks output options.
+
+ Args:
+ arguments: Parsed CLI arguments for the scan.
+ bulk_checks_metadata: Loaded metadata for all checks in the scan.
+ identity: E2E Networks identity information used in output filenames.
+ """
+ super().__init__(arguments, bulk_checks_metadata)
+ if (
+ not hasattr(arguments, "output_filename")
+ or arguments.output_filename is None
+ ):
+ self.output_filename = f"prowler-output-e2enetworks-{identity.project_id}-{output_file_timestamp}"
+ else:
+ self.output_filename = arguments.output_filename
diff --git a/tests/providers/aws/services/iam/iam_role_access_not_stale_to_bedrock/__init__.py b/prowler/providers/e2enetworks/services/__init__.py
similarity index 100%
rename from tests/providers/aws/services/iam/iam_role_access_not_stale_to_bedrock/__init__.py
rename to prowler/providers/e2enetworks/services/__init__.py
diff --git a/tests/providers/aws/services/iam/iam_user_access_not_stale_to_bedrock/__init__.py b/prowler/providers/e2enetworks/services/database/__init__.py
similarity index 100%
rename from tests/providers/aws/services/iam/iam_user_access_not_stale_to_bedrock/__init__.py
rename to prowler/providers/e2enetworks/services/database/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_client.py b/prowler/providers/e2enetworks/services/database/database_client.py
new file mode 100644
index 0000000000..5eaf4d6bda
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.database.database_service import Database
+
+database_client = Database(Provider.get_global_provider())
diff --git a/tests/providers/aws/services/kms/kms_cmk_not_multi_region/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/__init__.py
similarity index 100%
rename from tests/providers/aws/services/kms/kms_cmk_not_multi_region/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.metadata.json
new file mode 100644
index 0000000000..1604d0e5f7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_backup_enabled",
+ "CheckTitle": "E2E Networks database clusters have automated backups enabled",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database clusters** should have automated backups enabled so data can be restored after failures, corruption, or accidental deletion. Automated backups capture point-in-time copies of the cluster on a recurring schedule.",
+ "Risk": "Database clusters without backups are vulnerable to permanent **data loss** from hardware failures, corruption, or accidental deletion, with no way to recover to a prior state.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **automated backups** on every database cluster that does not currently have them configured, and validate that backups can be restored.",
+ "Url": "https://hub.prowler.com/check/database_cluster_backup_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.py b/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.py
new file mode 100644
index 0000000000..553c05f8ff
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_backup_enabled/database_cluster_backup_enabled.py
@@ -0,0 +1,24 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_backup_enabled(Check):
+ """Check if E2E Networks database clusters have backups enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Database cluster {cluster.name} has backups enabled."
+ )
+ if not cluster.backup_enabled:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Database cluster {cluster.name} does not have backups enabled."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/__init__.py
similarity index 100%
rename from tests/providers/aws/services/stepfunctions/stepfunctions_statemachine_no_secrets_in_definition/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.metadata.json
new file mode 100644
index 0000000000..83d2d160c9
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_default_admin_username",
+ "CheckTitle": "E2E Networks database clusters do not use the default admin username",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database clusters** should be configured with a custom administrative username instead of the well-known default, reducing the predictability of privileged credentials.",
+ "Risk": "Default admin usernames are publicly known, so they increase exposure to **credential guessing** and **brute-force attacks** against the privileged database account.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Replace the default administrative username on database clusters with a unique, non-default account name and rotate the associated credentials.",
+ "Url": "https://hub.prowler.com/check/database_cluster_default_admin_username"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.py b/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.py
new file mode 100644
index 0000000000..8a5de20d0e
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_default_admin_username/database_cluster_default_admin_username.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_default_admin_username(Check):
+ """Check if E2E Networks database clusters do not use the default admin username."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = f"Database cluster {cluster.name} does not use the default admin username."
+ if cluster.master_username.lower() == "admin":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Database cluster {cluster.name} uses the default admin username."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/aws/services/storagegateway/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/__init__.py
similarity index 100%
rename from tests/providers/aws/services/storagegateway/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.metadata.json
new file mode 100644
index 0000000000..eebe425046
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_ip_whitelist_configured",
+ "CheckTitle": "E2E Networks database clusters with public IPs have IP whitelisting configured",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database clusters** that expose a public IP should restrict connectivity through an **IP whitelist** instead of accepting connections from any address (`0.0.0.0/0`).",
+ "Risk": "Publicly exposed database clusters without IP whitelisting accept connections from **any source on the internet**, greatly increasing the risk of unauthorized access and data exfiltration.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure an **IP whitelist** on publicly exposed database clusters to allow only trusted source ranges, or move the cluster onto private networking.",
+ "Url": "https://hub.prowler.com/check/database_cluster_ip_whitelist_configured"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.py b/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.py
new file mode 100644
index 0000000000..0537f6f9e9
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_ip_whitelist_configured/database_cluster_ip_whitelist_configured.py
@@ -0,0 +1,24 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_ip_whitelist_configured(Check):
+ """Check if E2E Networks database clusters with public IPs have IP whitelisting configured."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ if not cluster.master_has_public_ip:
+ continue
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Database cluster {cluster.name} has IP whitelisting configured."
+ )
+ if not cluster.whitelisted_ips:
+ report.status = "FAIL"
+ report.status_extended = f"Database cluster {cluster.name} has a public IP but no whitelisted IPs."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/azure/services/apim/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/__init__.py
similarity index 100%
rename from tests/providers/azure/services/apim/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.metadata.json
new file mode 100644
index 0000000000..a965ef84f7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_public_ip_not_assigned",
+ "CheckTitle": "E2E Networks database cluster master nodes do not expose a public IP",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "The **master node** of each **E2E Networks database cluster** should be reachable only over private networking and must not have a public IP address assigned.",
+ "Risk": "A **public database endpoint** is directly reachable from the internet, expanding the attack surface and increasing the risk of unauthorized access, brute-force attempts, and data exposure.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove the **public IP** from the master node of database clusters and access them through private networking such as a VPC.",
+ "Url": "https://hub.prowler.com/check/database_cluster_public_ip_not_assigned"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.py b/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.py
new file mode 100644
index 0000000000..f6116d9e68
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_public_ip_not_assigned/database_cluster_public_ip_not_assigned.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_public_ip_not_assigned(Check):
+ """Check if E2E Networks database clusters do not expose a public IP on the master node."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = f"Database cluster {cluster.name} master node does not have a public IP."
+ if cluster.master_has_public_ip:
+ report.status = "FAIL"
+ report.status_extended = f"Database cluster {cluster.name} master node has a public IP assigned."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/azure/services/apim/apim_threat_detection_llm_jacking/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_running/__init__.py
similarity index 100%
rename from tests/providers/azure/services/apim/apim_threat_detection_llm_jacking/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_running/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.metadata.json
new file mode 100644
index 0000000000..8de420a54b
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_running",
+ "CheckTitle": "E2E Networks database clusters are in RUNNING status",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database clusters** should be in the `RUNNING` state, confirming they are operational rather than stopped, failed, or stuck in a transitional status.",
+ "Risk": "Database clusters that are not `RUNNING` may indicate outages, failed provisioning, or misconfiguration that impacts **availability** and the ability to recover data.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Start database clusters that are not in the `RUNNING` state and investigate the root cause of any stopped or failed clusters.",
+ "Url": "https://hub.prowler.com/check/database_cluster_running"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.py b/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.py
new file mode 100644
index 0000000000..3322f85863
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_running/database_cluster_running.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_running(Check):
+ """Check if E2E Networks database clusters are in RUNNING status."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = f"Database cluster {cluster.name} is running."
+ if cluster.status != "RUNNING":
+ report.status = "FAIL"
+ report.status_extended = f"Database cluster {cluster.name} is not running (status: {cluster.status})."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/gcp/services/cloudstorage/cloudstorage_audit_logs_enabled/__init__.py b/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/__init__.py
similarity index 100%
rename from tests/providers/gcp/services/cloudstorage/cloudstorage_audit_logs_enabled/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.metadata.json b/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.metadata.json
new file mode 100644
index 0000000000..f459ffd40b
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_cluster_ssl_enabled",
+ "CheckTitle": "E2E Networks database clusters have SSL enabled on the master node",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database clusters** should require `SSL/TLS` on the master node so that client connections and credentials are encrypted **in transit**.",
+ "Risk": "Without `SSL/TLS`, database credentials and query data travel in **plaintext** and can be intercepted through man-in-the-middle or network eavesdropping attacks.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable `SSL/TLS` on the master node of database clusters to encrypt all client connections in transit.",
+ "Url": "https://hub.prowler.com/check/database_cluster_ssl_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.py b/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.py
new file mode 100644
index 0000000000..7def7a8c26
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_cluster_ssl_enabled/database_cluster_ssl_enabled.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_cluster_ssl_enabled(Check):
+ """Check if E2E Networks database clusters have SSL enabled on the master node."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for cluster in database_client.clusters:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=cluster)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Database cluster {cluster.name} has SSL enabled on the master node."
+ )
+ if not cluster.master_ssl_enabled:
+ report.status = "FAIL"
+ report.status_extended = f"Database cluster {cluster.name} does not have SSL enabled on the master node."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/gcp/services/cloudstorage/cloudstorage_uses_vpc_service_controls/__init__.py b/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/__init__.py
similarity index 100%
rename from tests/providers/gcp/services/cloudstorage/cloudstorage_uses_vpc_service_controls/__init__.py
rename to prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/__init__.py
diff --git a/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.metadata.json b/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.metadata.json
new file mode 100644
index 0000000000..268ae1c6ad
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "database_replica_public_ip_not_assigned",
+ "CheckTitle": "E2E Networks database read replicas do not have a public IP assigned",
+ "CheckType": [],
+ "ServiceName": "database",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "database",
+ "Description": "**E2E Networks database read replicas** should be reachable only over private networking and must not have a public IP address assigned.",
+ "Risk": "Read replicas with **public IPs** are directly reachable from the internet, expanding database exposure and increasing the risk of unauthorized access to replicated data.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/database/rds/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove the **public IP** from database read replicas and route access through private networking.",
+ "Url": "https://hub.prowler.com/check/database_replica_public_ip_not_assigned"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.py b/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.py
new file mode 100644
index 0000000000..0dadc211a6
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_replica_public_ip_not_assigned/database_replica_public_ip_not_assigned.py
@@ -0,0 +1,26 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.database.database_client import (
+ database_client,
+)
+
+
+class database_replica_public_ip_not_assigned(Check):
+ """Check if E2E Networks database read replicas do not have a public IP assigned."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for instance in database_client.instances:
+ if instance.role != "replica":
+ continue
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=instance)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Database replica {instance.name} does not have a public IP assigned."
+ )
+ if instance.has_public_ip:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Database replica {instance.name} has a public IP assigned."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/database/database_service.py b/prowler/providers/e2enetworks/services/database/database_service.py
new file mode 100644
index 0000000000..703c2871d7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/database/database_service.py
@@ -0,0 +1,164 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+def _has_public_ip(public_ip_address: str | None) -> bool:
+ if not public_ip_address:
+ return False
+ value = str(public_ip_address).strip()
+ if not value or value.lower() in ("[]", "null", "none"):
+ return False
+ return True
+
+
+class Database(E2eNetworksService):
+ """Service class for E2E Networks DBaaS (RDS) resources."""
+
+ def __init__(self, provider):
+ super().__init__("database", provider)
+ self.clusters: list[DatabaseCluster] = []
+ self.instances: list[DatabaseInstance] = []
+ self._fetch_clusters()
+
+ def _fetch_clusters(self):
+ for location in self.provider.session.locations:
+ try:
+ cluster_list = self.client.get_data("/rds/cluster/", location=location)
+ if not isinstance(cluster_list, list):
+ continue
+
+ for item in cluster_list:
+ cluster_id = str(item.get("id", ""))
+ detail = self._get_cluster_detail(cluster_id, location)
+ merged = {**item, **detail}
+
+ master_node = merged.get("master_node", {}) or {}
+ database_info = master_node.get("database", {}) or {}
+ software = (
+ merged.get("software", {})
+ or master_node.get("plan", {}).get("software", {})
+ or {}
+ )
+
+ cluster = DatabaseCluster(
+ id=cluster_id,
+ name=merged.get("name", ""),
+ location=location,
+ status=merged.get("status", ""),
+ software_name=software.get("name", ""),
+ software_version=software.get("version", ""),
+ backup_enabled=bool(merged.get("backup_enabled", False)),
+ whitelisted_ips=merged.get("whitelisted_ips", []) or [],
+ master_ssl_enabled=bool(master_node.get("ssl", False)),
+ master_public_ip=master_node.get("public_ip_address"),
+ master_username=database_info.get("username", ""),
+ master_has_public_ip=_has_public_ip(
+ master_node.get("public_ip_address")
+ ),
+ )
+ self.clusters.append(cluster)
+
+ self.instances.append(
+ DatabaseInstance(
+ id=str(master_node.get("instance_id", cluster_id)),
+ name=master_node.get("node_name", merged.get("name", "")),
+ cluster_id=cluster_id,
+ cluster_name=cluster.name,
+ location=location,
+ role="master",
+ public_ip_address=master_node.get("public_ip_address"),
+ has_public_ip=_has_public_ip(
+ master_node.get("public_ip_address")
+ ),
+ ssl_enabled=bool(master_node.get("ssl", False)),
+ username=database_info.get("username", ""),
+ )
+ )
+
+ for slave in merged.get("slave_nodes", []) or []:
+ if not isinstance(slave, dict):
+ continue
+ slave_db = slave.get("database", {}) or {}
+ self.instances.append(
+ DatabaseInstance(
+ id=str(slave.get("instance_id", "")),
+ name=slave.get("node_name", ""),
+ cluster_id=cluster_id,
+ cluster_name=cluster.name,
+ location=location,
+ role="replica",
+ public_ip_address=slave.get("public_ip_address"),
+ has_public_ip=_has_public_ip(
+ slave.get("public_ip_address")
+ ),
+ ssl_enabled=bool(slave.get("ssl", False)),
+ username=slave_db.get("username", ""),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"database - Error fetching clusters in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _get_cluster_detail(self, cluster_id: str, location: str) -> dict:
+ if not cluster_id:
+ return {}
+ try:
+ data = self.client.get_data(
+ f"/rds/cluster/{cluster_id}/",
+ location=location,
+ )
+ return data if isinstance(data, dict) else {}
+ except Exception as error:
+ logger.error(
+ f"database - Error fetching cluster detail {cluster_id} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+
+class DatabaseCluster(BaseModel):
+ id: str
+ name: str
+ location: str
+ status: str = ""
+ software_name: str = ""
+ software_version: str = ""
+ backup_enabled: bool = False
+ whitelisted_ips: list = []
+ master_ssl_enabled: bool = False
+ master_public_ip: str | None = None
+ master_username: str = ""
+ master_has_public_ip: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+
+class DatabaseInstance(BaseModel):
+ id: str
+ name: str
+ cluster_id: str
+ cluster_name: str
+ location: str
+ role: str
+ public_ip_address: str | None = None
+ has_public_ip: bool = False
+ ssl_enabled: bool = False
+ username: str = ""
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
diff --git a/tests/providers/gcp/services/compute/compute_automatic_restart_enabled/__init__.py b/prowler/providers/e2enetworks/services/loadbalancer/__init__.py
similarity index 100%
rename from tests/providers/gcp/services/compute/compute_automatic_restart_enabled/__init__.py
rename to prowler/providers/e2enetworks/services/loadbalancer/__init__.py
diff --git a/tests/providers/gcp/services/compute/compute_instance_group_multiple_zones/__init__.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/__init__.py
similarity index 100%
rename from tests/providers/gcp/services/compute/compute_instance_group_multiple_zones/__init__.py
rename to prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/__init__.py
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.metadata.json b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.metadata.json
new file mode 100644
index 0000000000..641554a2cc
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "loadbalancer_alb_https_uses_ssl_certificate",
+ "CheckTitle": "E2E Networks ALB HTTPS load balancers use an SSL certificate",
+ "CheckType": [],
+ "ServiceName": "loadbalancer",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks application load balancers** serving `HTTPS` traffic should have a valid **SSL certificate** configured so client connections are encrypted and authenticated.",
+ "Risk": "`HTTPS` load balancers without a valid **SSL certificate** expose traffic to interception and downgrade attacks, weakening **confidentiality** and **integrity** for client connections.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/load-balancer/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach a valid **SSL certificate** to every load balancer that serves `HTTPS` traffic.",
+ "Url": "https://hub.prowler.com/check/loadbalancer_alb_https_uses_ssl_certificate"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.py
new file mode 100644
index 0000000000..2ed10c1c14
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_alb_https_uses_ssl_certificate/loadbalancer_alb_https_uses_ssl_certificate.py
@@ -0,0 +1,25 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.loadbalancer.loadbalancer_client import (
+ loadbalancer_client,
+)
+
+
+class loadbalancer_alb_https_uses_ssl_certificate(Check):
+ """Check that HTTPS load balancers have an SSL certificate configured."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for lb in loadbalancer_client.load_balancers:
+ if not lb.is_alb_https:
+ continue
+
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=lb)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Load balancer {lb.name} uses an SSL certificate for HTTPS traffic."
+ )
+ if not lb.ssl_certificate_id:
+ report.status = "FAIL"
+ report.status_extended = f"Load balancer {lb.name} does not have an SSL certificate configured for HTTPS traffic."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/image/lib/__init__.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/__init__.py
similarity index 100%
rename from tests/providers/image/lib/__init__.py
rename to prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.metadata.json b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.metadata.json
new file mode 100644
index 0000000000..b4c6a710c7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "loadbalancer_backend_health_check_enabled",
+ "CheckTitle": "E2E Networks ALB load balancers have backend health checks enabled",
+ "CheckType": [],
+ "ServiceName": "loadbalancer",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks application load balancers** should have `HTTP` **health checks** configured for their backends so traffic is only routed to healthy nodes.",
+ "Risk": "Load balancers without backend **health checks** may route traffic to failed or unhealthy nodes, causing outages and masking active compromise on degraded backends.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/load-balancer/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure `HTTP` **health checks** for ALB backends so unhealthy nodes are automatically removed from rotation.",
+ "Url": "https://hub.prowler.com/check/loadbalancer_backend_health_check_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.py
new file mode 100644
index 0000000000..8602797e5f
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_backend_health_check_enabled/loadbalancer_backend_health_check_enabled.py
@@ -0,0 +1,25 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.loadbalancer.loadbalancer_client import (
+ loadbalancer_client,
+)
+
+
+class loadbalancer_backend_health_check_enabled(Check):
+ """Check that ALB load balancers have backend health checks configured."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for lb in loadbalancer_client.load_balancers:
+ if not lb.is_alb:
+ continue
+
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=lb)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Load balancer {lb.name} has backend health checks configured."
+ )
+ if not lb.has_backend_health_check:
+ report.status = "FAIL"
+ report.status_extended = f"Load balancer {lb.name} does not have backend health checks configured."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/image/lib/registry/__init__.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/__init__.py
similarity index 100%
rename from tests/providers/image/lib/registry/__init__.py
rename to prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.metadata.json b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.metadata.json
new file mode 100644
index 0000000000..8ecae9db08
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "loadbalancer_bitninja_enabled",
+ "CheckTitle": "E2E Networks load balancers have BitNinja protection enabled",
+ "CheckType": [],
+ "ServiceName": "loadbalancer",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks load balancers** should have **BitNinja** protection enabled to provide web application firewall coverage on public endpoints.",
+ "Risk": "Load balancers without **BitNinja** protection have reduced **WAF** coverage, increasing exposure to automated attacks and malicious traffic against public endpoints.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/load-balancer/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **BitNinja** protection on load balancer appliances to strengthen web application firewall coverage.",
+ "Url": "https://hub.prowler.com/check/loadbalancer_bitninja_enabled"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.py
new file mode 100644
index 0000000000..c08ebef982
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_bitninja_enabled/loadbalancer_bitninja_enabled.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.loadbalancer.loadbalancer_client import (
+ loadbalancer_client,
+)
+
+
+class loadbalancer_bitninja_enabled(Check):
+ """Check that load balancers have BitNinja protection enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for lb in loadbalancer_client.load_balancers:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=lb)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Load balancer {lb.name} has BitNinja protection enabled."
+ )
+ if not lb.enable_bitninja:
+ report.status = "FAIL"
+ report.status_extended = f"Load balancer {lb.name} does not have BitNinja protection enabled."
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_client.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_client.py
new file mode 100644
index 0000000000..88330ec3a8
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.loadbalancer.loadbalancer_service import (
+ LoadBalancers,
+)
+
+loadbalancer_client = LoadBalancers(Provider.get_global_provider())
diff --git a/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_service.py b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_service.py
new file mode 100644
index 0000000000..e572a2f614
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/loadbalancer/loadbalancer_service.py
@@ -0,0 +1,96 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+class LoadBalancers(E2eNetworksService):
+ """Service class for E2E Networks load balancers."""
+
+ def __init__(self, provider):
+ super().__init__("loadbalancer", provider)
+ self.load_balancers: list[LoadBalancer] = []
+ self._fetch_loadbalancers()
+
+ def _fetch_loadbalancers(self):
+ for location in self.provider.session.locations:
+ try:
+ appliances = self.client.paginate(
+ "/appliances/",
+ location=location,
+ )
+ for item in appliances:
+ context = self._extract_context(item)
+ node_detail = item.get("node_detail", {}) or {}
+ self.load_balancers.append(
+ LoadBalancer(
+ id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ location=location,
+ status=item.get("status", ""),
+ lb_mode=context.get("lb_mode", ""),
+ lb_port=str(context.get("lb_port", "")),
+ enable_bitninja=bool(context.get("enable_bitninja", False)),
+ ssl_certificate_id=self._get_ssl_certificate_id(context),
+ backends=context.get("backends", []) or [],
+ public_ip=node_detail.get("public_ip", ""),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"loadbalancer - Error fetching appliances in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ @staticmethod
+ def _extract_context(item: dict) -> dict:
+ instances = item.get("appliance_instance", []) or []
+ if not instances:
+ return {}
+ return instances[0].get("context", {}) or {}
+
+ @staticmethod
+ def _get_ssl_certificate_id(context: dict) -> str | None:
+ ssl_context = context.get("ssl_context", {}) or {}
+ certificate_id = ssl_context.get("ssl_certificate_id")
+ if certificate_id in (None, "", 0):
+ return None
+ return str(certificate_id)
+
+
+class LoadBalancer(BaseModel):
+ id: str
+ name: str
+ location: str
+ status: str = ""
+ lb_mode: str = ""
+ lb_port: str = ""
+ enable_bitninja: bool = False
+ ssl_certificate_id: str | None = None
+ backends: list = []
+ public_ip: str = ""
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+ @property
+ def is_alb(self) -> bool:
+ mode = self.lb_mode.upper()
+ return mode in ("HTTP", "HTTPS", "BOTH")
+
+ @property
+ def is_alb_https(self) -> bool:
+ mode = self.lb_mode.upper()
+ return mode in ("HTTPS", "BOTH")
+
+ @property
+ def has_backend_health_check(self) -> bool:
+ for backend in self.backends:
+ if isinstance(backend, dict) and backend.get("http_check"):
+ return True
+ return False
diff --git a/tests/providers/m365/services/defenderidentity/__init__.py b/prowler/providers/e2enetworks/services/network/__init__.py
similarity index 100%
rename from tests/providers/m365/services/defenderidentity/__init__.py
rename to prowler/providers/e2enetworks/services/network/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_client.py b/prowler/providers/e2enetworks/services/network/network_client.py
new file mode 100644
index 0000000000..d7d16095d3
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.network.network_service import Network
+
+network_client = Network(Provider.get_global_provider())
diff --git a/tests/providers/m365/services/defenderidentity/defenderidentity_health_issues_no_open/__init__.py b/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/__init__.py
similarity index 100%
rename from tests/providers/m365/services/defenderidentity/defenderidentity_health_issues_no_open/__init__.py
rename to prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.metadata.json b/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.metadata.json
new file mode 100644
index 0000000000..a9fecbfb0a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "network_reserveip_floating_ip_unattached",
+ "CheckTitle": "E2E Networks floating IPs are attached to nodes",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks floating (reserved) IP addresses** should be attached to a node instead of being left unassigned, since idle floating IPs can be reassigned unexpectedly.",
+ "Risk": "**Unattached floating IPs** may be reassigned unexpectedly to other resources, disrupting secure routing assumptions and potentially exposing services.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/reserve-ip/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach unassigned **floating IPs** to the intended node, or release them if they are no longer needed.",
+ "Url": "https://hub.prowler.com/check/network_reserveip_floating_ip_unattached"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.py b/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.py
new file mode 100644
index 0000000000..c24a270804
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_reserveip_floating_ip_unattached/network_reserveip_floating_ip_unattached.py
@@ -0,0 +1,24 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.network.network_client import network_client
+
+
+class network_reserveip_floating_ip_unattached(Check):
+ """Check if E2E Networks floating IPs are attached to nodes."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for ip in network_client.reserved_ips:
+ if ip.reserved_type != "FloatingIP":
+ continue
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=ip)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Floating IP {ip.ip_address} is attached to node(s)."
+ )
+ if ip.status != "Attached" or ip.floating_ip_attached_nodes_count == 0:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Floating IP {ip.ip_address} is not attached to any node."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/m365/services/defenderxdr/__init__.py b/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/__init__.py
similarity index 100%
rename from tests/providers/m365/services/defenderxdr/__init__.py
rename to prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.metadata.json b/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.metadata.json
new file mode 100644
index 0000000000..b8c21b4b6b
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "network_reserveip_orphaned_public_ip",
+ "CheckTitle": "E2E Networks public or addon IPs are attached to a resource",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks public and addon reserved IP addresses** should be attached to a resource, identifying orphaned addresses that remain internet-reachable without an owner.",
+ "Risk": "**Orphaned public IPs** remain internet-reachable resources that can be misused or reassigned without ownership controls, expanding the attack surface.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/reserve-ip/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach orphaned **public or addon IPs** to a resource, or delete them to remove unused internet-reachable addresses.",
+ "Url": "https://hub.prowler.com/check/network_reserveip_orphaned_public_ip"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.py b/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.py
new file mode 100644
index 0000000000..bb4a67066d
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_reserveip_orphaned_public_ip/network_reserveip_orphaned_public_ip.py
@@ -0,0 +1,24 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.network.network_client import network_client
+
+
+class network_reserveip_orphaned_public_ip(Check):
+ """Check if E2E Networks public or addon IPs are attached."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for ip in network_client.reserved_ips:
+ if ip.reserved_type not in ("PublicIP", "AddonIP"):
+ continue
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=ip)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Reserved IP {ip.ip_address} is attached to a resource."
+ )
+ if ip.status != "Attached" or ip.vm_id is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Reserved IP {ip.ip_address} is orphaned (status: {ip.status})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/network/network_service.py b/prowler/providers/e2enetworks/services/network/network_service.py
new file mode 100644
index 0000000000..327749d22c
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_service.py
@@ -0,0 +1,158 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+class Network(E2eNetworksService):
+ """Service class for E2E Networks network resources."""
+
+ def __init__(self, provider):
+ super().__init__("network", provider)
+ self.vpcs: list[Vpc] = []
+ self.reserved_ips: list[ReservedIp] = []
+ self.vpc_tunnels: list[VpcTunnel] = []
+ self._fetch_vpcs()
+ self._fetch_reserved_ips()
+ self._fetch_vpc_tunnels()
+
+ def _fetch_vpcs(self):
+ for location in self.provider.session.locations:
+ try:
+ vpcs = self.client.paginate("/vpc/list/", location=location)
+ if not isinstance(vpcs, list):
+ continue
+ for item in vpcs:
+ gateway_node = item.get("gateway_node", {}) or {}
+ self.vpcs.append(
+ Vpc(
+ network_id=str(item.get("network_id", "")),
+ name=item.get("name", ""),
+ location=location,
+ is_active=bool(item.get("is_active", False)),
+ state=item.get("state", ""),
+ ipv4_cidr=item.get("ipv4_cidr", ""),
+ vm_count=int(item.get("vm_count", 0)),
+ gateway_node_id=str(gateway_node.get("node_id", "")),
+ gateway_public_ip=gateway_node.get("ip_address_public", ""),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"network - Error fetching VPCs in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _fetch_reserved_ips(self):
+ for location in self.provider.session.locations:
+ try:
+ ips = self.client.get_data("/reserve_ips/", location=location)
+ if not isinstance(ips, list):
+ continue
+
+ for item in ips:
+ attached_nodes = item.get("floating_ip_attached_nodes", []) or []
+ self.reserved_ips.append(
+ ReservedIp(
+ reserve_id=str(item.get("reserve_id", "")),
+ ip_address=item.get("ip_address", ""),
+ location=location,
+ status=item.get("status", ""),
+ reserved_type=item.get("reserved_type", ""),
+ vm_id=item.get("vm_id"),
+ floating_ip_attached_nodes_count=len(attached_nodes),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"network - Error fetching reserved IPs in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _fetch_vpc_tunnels(self):
+ for vpc in self.vpcs:
+ if not vpc.network_id:
+ continue
+ try:
+ tunnels = self.client.get_data(
+ f"/vpc/tunnels/{vpc.network_id}/",
+ location=vpc.location,
+ )
+ if not isinstance(tunnels, list):
+ continue
+
+ for item in tunnels:
+ self.vpc_tunnels.append(
+ VpcTunnel(
+ id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ location=vpc.location,
+ local_vpc_network_id=vpc.network_id,
+ local_vpc_name=vpc.name,
+ status=item.get("status", ""),
+ is_peer_vpc_external=bool(
+ item.get("is_peer_vpc_external", False)
+ ),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"network - Error fetching tunnels for VPC {vpc.network_id} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class Vpc(BaseModel):
+ network_id: str
+ name: str
+ location: str
+ is_active: bool = False
+ state: str = ""
+ ipv4_cidr: str = ""
+ vm_count: int = 0
+ gateway_node_id: str = ""
+ gateway_public_ip: str = ""
+
+ @property
+ def resource_id(self) -> str:
+ return self.network_id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+
+class ReservedIp(BaseModel):
+ reserve_id: str
+ ip_address: str
+ location: str
+ status: str = ""
+ reserved_type: str = ""
+ vm_id: int | None = None
+ floating_ip_attached_nodes_count: int = 0
+
+ @property
+ def resource_id(self) -> str:
+ return self.reserve_id
+
+ @property
+ def resource_name(self) -> str:
+ return self.ip_address
+
+
+class VpcTunnel(BaseModel):
+ id: str
+ name: str
+ location: str
+ local_vpc_network_id: str
+ local_vpc_name: str
+ status: str = ""
+ is_peer_vpc_external: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
diff --git a/tests/providers/m365/services/defenderxdr/defenderxdr_endpoint_privileged_user_exposed_credentials/__init__.py b/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/__init__.py
similarity index 100%
rename from tests/providers/m365/services/defenderxdr/defenderxdr_endpoint_privileged_user_exposed_credentials/__init__.py
rename to prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.metadata.json b/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.metadata.json
new file mode 100644
index 0000000000..59b94ba76a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "network_vpc_has_attached_nodes",
+ "CheckTitle": "E2E Networks VPCs have attached nodes",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks VPCs** should have at least one node attached, identifying unused network segments that may indicate misconfiguration or forgotten resources.",
+ "Risk": "**VPCs without attached nodes** may indicate unused network segments or misconfiguration that weakens **network segmentation** and increases management overhead.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/vpc/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach nodes to VPCs that are in use, or remove empty VPCs that are no longer required.",
+ "Url": "https://hub.prowler.com/check/network_vpc_has_attached_nodes"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.py b/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.py
new file mode 100644
index 0000000000..3b453e188a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_has_attached_nodes/network_vpc_has_attached_nodes.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.network.network_client import network_client
+
+
+class network_vpc_has_attached_nodes(Check):
+ """Check if E2E Networks VPCs have attached nodes."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for vpc in network_client.vpcs:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=vpc)
+ report.status = "PASS"
+ report.status_extended = (
+ f"VPC {vpc.name} has {vpc.vm_count} attached node(s)."
+ )
+ if vpc.vm_count <= 0:
+ report.status = "FAIL"
+ report.status_extended = f"VPC {vpc.name} has no attached nodes."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/m365/services/entra/entra_conditional_access_policy_mdm_compliant_device_required/__init__.py b/prowler/providers/e2enetworks/services/network/network_vpc_is_active/__init__.py
similarity index 100%
rename from tests/providers/m365/services/entra/entra_conditional_access_policy_mdm_compliant_device_required/__init__.py
rename to prowler/providers/e2enetworks/services/network/network_vpc_is_active/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.metadata.json b/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.metadata.json
new file mode 100644
index 0000000000..8843bdf1e7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "network_vpc_is_active",
+ "CheckTitle": "E2E Networks VPCs are active",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks VPCs** should be in the `active` state so that attached workloads retain expected connectivity and network isolation.",
+ "Risk": "**Inactive VPCs** can cause connectivity failures and may leave workloads without the expected **network isolation** boundaries.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/vpc/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Activate VPCs that are `inactive` so dependent workloads keep their expected connectivity and isolation.",
+ "Url": "https://hub.prowler.com/check/network_vpc_is_active"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.py b/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.py
new file mode 100644
index 0000000000..d95027d9ae
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_is_active/network_vpc_is_active.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.network.network_client import network_client
+
+
+class network_vpc_is_active(Check):
+ """Check if E2E Networks VPCs are active."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for vpc in network_client.vpcs:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=vpc)
+ report.status = "PASS"
+ report.status_extended = f"VPC {vpc.name} is active."
+ if not vpc.is_active or vpc.state != "Active":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"VPC {vpc.name} is not active (state: {vpc.state})."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/m365/services/intune/__init__.py b/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/__init__.py
similarity index 100%
rename from tests/providers/m365/services/intune/__init__.py
rename to prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.metadata.json b/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.metadata.json
new file mode 100644
index 0000000000..9adbfab90e
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "network_vpc_peering_external_peer_disabled",
+ "CheckTitle": "E2E Networks VPC peering does not use external peers",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks VPC peering connections** should be established only with internal networks and must not extend trust to external peers outside the account.",
+ "Risk": "**VPC peering with external peers** expands trust boundaries and can expose private networks to third parties, enabling lateral movement across accounts.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/vpc/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove **VPC peering** tunnels that connect to external peers to keep private networks within trusted boundaries.",
+ "Url": "https://hub.prowler.com/check/network_vpc_peering_external_peer_disabled"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.py b/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.py
new file mode 100644
index 0000000000..d47fa0a6df
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/network/network_vpc_peering_external_peer_disabled/network_vpc_peering_external_peer_disabled.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.network.network_client import network_client
+
+
+class network_vpc_peering_external_peer_disabled(Check):
+ """Check if E2E Networks VPC peering does not use external peers."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for tunnel in network_client.vpc_tunnels:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=tunnel)
+ report.status = "PASS"
+ report.status_extended = (
+ f"VPC peering {tunnel.name} does not use an external peer VPC."
+ )
+ if tunnel.is_peer_vpc_external:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"VPC peering {tunnel.name} uses an external peer VPC."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/openstack/lib/__init__.py b/prowler/providers/e2enetworks/services/node/__init__.py
similarity index 100%
rename from tests/providers/openstack/lib/__init__.py
rename to prowler/providers/e2enetworks/services/node/__init__.py
diff --git a/tests/providers/openstack/lib/arguments/__init__.py b/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/__init__.py
similarity index 100%
rename from tests/providers/openstack/lib/arguments/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.metadata.json b/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.metadata.json
new file mode 100644
index 0000000000..6229383147
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_accidental_protection_enabled",
+ "CheckTitle": "E2E Networks nodes have accidental protection enabled",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should have **accidental protection** enabled to guard against unintended deletion or modification of compute instances.",
+ "Risk": "Nodes without **accidental protection** are easier to delete or modify unintentionally, increasing the risk of **service disruption** and unplanned exposure of compute resources.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **accidental protection** on nodes to prevent unintended deletion or modification.",
+ "Url": "https://hub.prowler.com/check/node_accidental_protection_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.py b/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.py
new file mode 100644
index 0000000000..49a6ff411d
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_accidental_protection_enabled/node_accidental_protection_enabled.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_accidental_protection_enabled(Check):
+ """Check if E2E Networks nodes have accidental protection enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Node {node.name} has accidental protection enabled."
+ )
+ if not node.is_accidental_protection:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Node {node.name} does not have accidental protection enabled."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/node/node_client.py b/prowler/providers/e2enetworks/services/node/node_client.py
new file mode 100644
index 0000000000..a1c9981373
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.node.node_service import Nodes
+
+node_client = Nodes(Provider.get_global_provider())
diff --git a/tests/providers/openstack/lib/mutelist/__init__.py b/prowler/providers/e2enetworks/services/node/node_compliance_enabled/__init__.py
similarity index 100%
rename from tests/providers/openstack/lib/mutelist/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_compliance_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.metadata.json b/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.metadata.json
new file mode 100644
index 0000000000..bb3b5f30ef
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_compliance_enabled",
+ "CheckTitle": "E2E Networks nodes have compliance mode enabled",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should run with **compliance mode** enabled so required security controls are enforced and workload activity remains auditable.",
+ "Risk": "Nodes without **compliance mode** may not enforce required security controls, increasing misconfiguration risk and weakening the **auditability** of compute workloads.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **compliance mode** on nodes to enforce required security controls and maintain auditability.",
+ "Url": "https://hub.prowler.com/check/node_compliance_enabled"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.py b/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.py
new file mode 100644
index 0000000000..bae2b16184
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_compliance_enabled/node_compliance_enabled.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_compliance_enabled(Check):
+ """Check if E2E Networks nodes have compliance mode enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = f"Node {node.name} has compliance mode enabled."
+ if not node.is_node_compliance:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Node {node.name} does not have compliance mode enabled."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/openstack/lib/mutelist/fixtures/__init__.py b/prowler/providers/e2enetworks/services/node/node_encryption_enabled/__init__.py
similarity index 100%
rename from tests/providers/openstack/lib/mutelist/fixtures/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_encryption_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.metadata.json b/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.metadata.json
new file mode 100644
index 0000000000..6af8ca2479
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_encryption_enabled",
+ "CheckTitle": "E2E Networks nodes have disk encryption enabled",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should have **disk encryption** enabled so data stored on node volumes and snapshots is protected **at rest**.",
+ "Risk": "**Unencrypted nodes** increase the risk of **data exposure** if disks or snapshots are accessed outside normal operating controls.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **disk encryption** on nodes to protect data at rest on volumes and snapshots.",
+ "Url": "https://hub.prowler.com/check/node_encryption_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.py b/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.py
new file mode 100644
index 0000000000..65f65feb83
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_encryption_enabled/node_encryption_enabled.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_encryption_enabled(Check):
+ """Check if E2E Networks nodes have encryption enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = f"Node {node.name} has encryption enabled."
+ if not node.is_encryption_enabled:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Node {node.name} does not have encryption enabled."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/lib/__init__.py b/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/lib/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.metadata.json b/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.metadata.json
new file mode 100644
index 0000000000..addcf3feb0
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_public_ip_not_assigned",
+ "CheckTitle": "E2E Networks nodes do not have a public IP assigned",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should not be assigned a public IP address, keeping compute instances off the public internet unless inbound access is explicitly required.",
+ "Risk": "Nodes with **public IP addresses** are directly reachable from the internet, expanding the attack surface and increasing exposure to unauthorized access attempts.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove **public IP addresses** from nodes that do not require inbound internet access and reach them over private networking.",
+ "Url": "https://hub.prowler.com/check/node_public_ip_not_assigned"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.py b/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.py
new file mode 100644
index 0000000000..a95bd4552d
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_public_ip_not_assigned/node_public_ip_not_assigned.py
@@ -0,0 +1,18 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_public_ip_not_assigned(Check):
+ """Check if E2E Networks nodes do not have a public IP assigned."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = f"Node {node.name} does not have a public IP."
+ if node.has_public_ip:
+ report.status = "FAIL"
+ report.status_extended = f"Node {node.name} has a public IP assigned."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/lib/mutelist/__init__.py b/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/lib/mutelist/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.metadata.json b/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.metadata.json
new file mode 100644
index 0000000000..8336bc12cb
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_rescue_mode_disabled",
+ "CheckTitle": "E2E Networks nodes do not have rescue mode enabled",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should not be running in **rescue mode**, which grants elevated filesystem access and can bypass normal operating controls.",
+ "Risk": "**Rescue mode** provides elevated access to node filesystems and can bypass normal operating controls, increasing the risk of unauthorized data access or persistence.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable **rescue mode** on nodes once recovery tasks are complete to restore normal operating controls.",
+ "Url": "https://hub.prowler.com/check/node_rescue_mode_disabled"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.py b/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.py
new file mode 100644
index 0000000000..bde2da993d
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_rescue_mode_disabled/node_rescue_mode_disabled.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_rescue_mode_disabled(Check):
+ """Check if E2E Networks nodes do not have rescue mode enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Node {node.name} does not have rescue mode enabled."
+ )
+ if node.rescue_mode_status != "Disabled":
+ report.status = "FAIL"
+ report.status_extended = f"Node {node.name} has rescue mode enabled."
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/node/node_service.py b/prowler/providers/e2enetworks/services/node/node_service.py
new file mode 100644
index 0000000000..03e39be1b9
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_service.py
@@ -0,0 +1,109 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+def _has_public_ip(public_ip_address: str | None) -> bool:
+ if not public_ip_address:
+ return False
+ value = str(public_ip_address).strip()
+ if not value or value in ("[]", "null", "None"):
+ return False
+ return True
+
+
+class Nodes(E2eNetworksService):
+ """Service class for E2E Networks compute nodes."""
+
+ def __init__(self, provider):
+ super().__init__("node", provider)
+ self.nodes: list[Node] = []
+ self._fetch_nodes()
+
+ def _fetch_nodes(self):
+ for location in self.provider.session.locations:
+ try:
+ node_list = self.client.get_data("/nodes/", location=location)
+ if not isinstance(node_list, list):
+ continue
+
+ for item in node_list:
+ node_id = str(item.get("id", ""))
+ detail = self._get_node_detail(node_id, location)
+ merged = {**item, **detail}
+
+ self.nodes.append(
+ Node(
+ id=node_id,
+ name=merged.get("name", ""),
+ status=merged.get("status", ""),
+ location=location,
+ vm_id=str(merged.get("vm_id", merged.get("id", ""))),
+ public_ip_address=merged.get("public_ip_address"),
+ private_ip_address=merged.get("private_ip_address", ""),
+ is_accidental_protection=bool(
+ merged.get("is_accidental_protection", False)
+ ),
+ is_encryption_enabled=bool(
+ merged.get("isEncryptionEnabled", False)
+ ),
+ is_locked=bool(merged.get("is_locked", False)),
+ rescue_mode_status=merged.get(
+ "rescue_mode_status", "Disabled"
+ ),
+ is_node_compliance=bool(
+ merged.get("is_node_compliance", False)
+ ),
+ is_vpc_attached=bool(merged.get("is_vpc_attached", False)),
+ has_public_ip=_has_public_ip(
+ merged.get("public_ip_address")
+ ),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"node - Error fetching nodes in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _get_node_detail(self, node_id: str, location: str) -> dict:
+ if not node_id:
+ return {}
+ try:
+ data = self.client.get_data(
+ f"/nodes/{node_id}/",
+ location=location,
+ )
+ return data if isinstance(data, dict) else {}
+ except Exception as error:
+ logger.error(
+ f"node - Error fetching node detail {node_id} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+
+class Node(BaseModel):
+ id: str
+ name: str
+ status: str
+ location: str
+ vm_id: str
+ public_ip_address: str | None = None
+ private_ip_address: str = ""
+ is_accidental_protection: bool = False
+ is_encryption_enabled: bool = False
+ is_locked: bool = False
+ rescue_mode_status: str = "Disabled"
+ is_node_compliance: bool = False
+ is_vpc_attached: bool = False
+ has_public_ip: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
diff --git a/tests/providers/oraclecloud/services/__init__.py b/prowler/providers/e2enetworks/services/node/node_vpc_attached/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/__init__.py
rename to prowler/providers/e2enetworks/services/node/node_vpc_attached/__init__.py
diff --git a/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.metadata.json b/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.metadata.json
new file mode 100644
index 0000000000..59822e48e7
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "node_vpc_attached",
+ "CheckTitle": "E2E Networks nodes are attached to a VPC",
+ "CheckType": [],
+ "ServiceName": "node",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**E2E Networks nodes** should be attached to a **VPC** so their traffic benefits from network isolation and segmentation controls.",
+ "Risk": "Nodes not attached to a **VPC** may lack network isolation controls, making traffic routing and **segmentation** harder to enforce.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/compute/nodes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach nodes to a **VPC** to enforce network isolation and segmentation for their traffic.",
+ "Url": "https://hub.prowler.com/check/node_vpc_attached"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.py b/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.py
new file mode 100644
index 0000000000..5318461d3c
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/node/node_vpc_attached/node_vpc_attached.py
@@ -0,0 +1,18 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+
+class node_vpc_attached(Check):
+ """Check if E2E Networks nodes are attached to a VPC."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for node in node_client.nodes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=node)
+ report.status = "PASS"
+ report.status_extended = f"Node {node.name} is attached to a VPC."
+ if not node.is_vpc_attached:
+ report.status = "FAIL"
+ report.status_extended = f"Node {node.name} is not attached to a VPC."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/analytics/__init__.py b/prowler/providers/e2enetworks/services/securitygroup/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/analytics/__init__.py
rename to prowler/providers/e2enetworks/services/securitygroup/__init__.py
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_client.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_client.py
new file mode 100644
index 0000000000..4c938fbb2a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.securitygroup.securitygroup_service import (
+ SecurityGroups,
+)
+
+securitygroup_client = SecurityGroups(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/analytics/analytics_instance_access_restricted/__init__.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/analytics/analytics_instance_access_restricted/__init__.py
rename to prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/__init__.py
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.metadata.json b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.metadata.json
new file mode 100644
index 0000000000..23d765050a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "securitygroup_no_all_traffic_rule",
+ "CheckTitle": "E2E Networks security groups do not allow all traffic",
+ "CheckType": [],
+ "ServiceName": "securitygroup",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks security groups** should not have an **all-traffic rule**, which permits unrestricted inbound and outbound network access.",
+ "Risk": "Security groups that allow **all traffic** permit unrestricted network access, increasing exposure to **lateral movement** and **data exfiltration**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/security-group/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict security group rules to the required ports and sources only, removing any all-traffic rule.",
+ "Url": "https://hub.prowler.com/check/securitygroup_no_all_traffic_rule"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.py
new file mode 100644
index 0000000000..5230211d6f
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_all_traffic_rule/securitygroup_no_all_traffic_rule.py
@@ -0,0 +1,24 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.securitygroup.securitygroup_client import (
+ securitygroup_client,
+)
+
+
+class securitygroup_no_all_traffic_rule(Check):
+ """Check that security groups do not allow all traffic."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for group in securitygroup_client.security_groups:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=group)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Security group {group.name} does not allow all traffic."
+ )
+ if group.is_all_traffic_rule:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Security group {group.name} allows all traffic."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/audit/__init__.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/audit/__init__.py
rename to prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/__init__.py
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.metadata.json b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.metadata.json
new file mode 100644
index 0000000000..ebd43c61cc
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "securitygroup_no_inbound_any_all_ports",
+ "CheckTitle": "E2E Networks security groups do not allow inbound all-protocol traffic from any source",
+ "CheckType": [],
+ "ServiceName": "securitygroup",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks security groups** should not allow inbound **all-protocol** traffic from any source (`0.0.0.0/0`), which opens every port to the internet.",
+ "Risk": "Inbound **all-protocol** rules from any source expose services to the entire internet and greatly increase the likelihood of unauthorized access.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/security-group/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Replace overly permissive inbound rules with **least-privilege** rules scoped to specific ports and trusted sources.",
+ "Url": "https://hub.prowler.com/check/securitygroup_no_inbound_any_all_ports"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.py
new file mode 100644
index 0000000000..ee3c38015f
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_no_inbound_any_all_ports/securitygroup_no_inbound_any_all_ports.py
@@ -0,0 +1,35 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.securitygroup.securitygroup_client import (
+ securitygroup_client,
+)
+
+
+def _is_open_network(value: str | None) -> bool:
+ if value is None:
+ return False
+ normalized = str(value).lower().strip()
+ return normalized in ("any", "0.0.0.0/0", "::/0")
+
+
+def _is_permissive_inbound(rule) -> bool:
+ if (rule.rule_type or "").lower() != "inbound":
+ return False
+ if (rule.protocol_name or "").lower() != "all":
+ return False
+ return _is_open_network(rule.network) or _is_open_network(rule.network_cidr)
+
+
+class securitygroup_no_inbound_any_all_ports(Check):
+ """Check if E2E Networks security groups do not allow inbound all-protocol traffic from any source."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for group in securitygroup_client.security_groups:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=group)
+ report.status = "PASS"
+ report.status_extended = f"Security group {group.name} does not allow inbound all-protocol traffic from any source."
+ if any(_is_permissive_inbound(rule) for rule in group.rules):
+ report.status = "FAIL"
+ report.status_extended = f"Security group {group.name} allows inbound all-protocol traffic from any source."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/audit/audit_log_retention_period_365_days/__init__.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/audit/audit_log_retention_period_365_days/__init__.py
rename to prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/__init__.py
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.metadata.json b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.metadata.json
new file mode 100644
index 0000000000..15202d4a86
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "securitygroup_restrictive_default",
+ "CheckTitle": "E2E Networks nodes do not rely on permissive default security groups",
+ "CheckType": [],
+ "ServiceName": "securitygroup",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**E2E Networks nodes** should not rely solely on **default security groups** that have overly permissive inbound rules.",
+ "Risk": "Nodes that rely only on **permissive default security groups** inherit broad inbound access, weakening **network segmentation** and trust boundaries.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/network/security-group/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach custom security groups with **least-privilege** rules to nodes instead of relying on permissive defaults.",
+ "Url": "https://hub.prowler.com/check/securitygroup_restrictive_default"
+ }
+ },
+ "Categories": [
+ "trust-boundaries",
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.py
new file mode 100644
index 0000000000..39d750db6b
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_restrictive_default/securitygroup_restrictive_default.py
@@ -0,0 +1,49 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.securitygroup.securitygroup_client import (
+ securitygroup_client,
+)
+
+
+def _is_open_network(value: str | None) -> bool:
+ if value is None:
+ return False
+ normalized = str(value).lower().strip()
+ return normalized in ("any", "0.0.0.0/0", "::/0")
+
+
+def _has_permissive_inbound(rules) -> bool:
+ for rule in rules:
+ if (
+ (rule.rule_type or "").lower() == "inbound"
+ and (rule.protocol_name or "").lower() == "all"
+ and (_is_open_network(rule.network) or _is_open_network(rule.network_cidr))
+ ):
+ return True
+ return False
+
+
+class securitygroup_restrictive_default(Check):
+ """Check if E2E Networks nodes do not rely on permissive default security groups."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ node_groups: dict[str, list] = {}
+ for group in securitygroup_client.node_security_groups:
+ node_groups.setdefault(group.node_id, []).append(group)
+
+ for node_id, groups in node_groups.items():
+ resource = groups[0]
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=resource)
+ report.status = "PASS"
+ report.status_extended = f"Node {resource.node_name} does not rely on a permissive default security group."
+
+ default_groups = [group for group in groups if group.is_default]
+ if default_groups and len(groups) == len(default_groups):
+ if any(
+ _has_permissive_inbound(group.rules) for group in default_groups
+ ):
+ report.status = "FAIL"
+ report.status_extended = f"Node {resource.node_name} uses only default security groups with overly permissive inbound rules."
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/securitygroup/securitygroup_service.py b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_service.py
new file mode 100644
index 0000000000..7a874d85ae
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/securitygroup/securitygroup_service.py
@@ -0,0 +1,147 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+class SecurityGroups(E2eNetworksService):
+ """Service class for E2E Networks security groups."""
+
+ def __init__(self, provider):
+ super().__init__("securitygroup", provider)
+ self.security_groups: list[SecurityGroupResource] = []
+ self.node_security_groups: list[NodeSecurityGroup] = []
+ self._fetch_security_groups()
+ self._fetch_node_security_groups()
+
+ def _fetch_security_groups(self):
+ for location in self.provider.session.locations:
+ try:
+ groups = self.client.get_data("/security_group/", location=location)
+ if not isinstance(groups, list):
+ continue
+
+ for item in groups:
+ rules = [
+ SecurityGroupRule(
+ id=str(rule.get("id", "")),
+ rule_type=rule.get("rule_type", ""),
+ protocol_name=rule.get("protocol_name", ""),
+ port_range=rule.get("port_range", ""),
+ network=rule.get("network", ""),
+ network_cidr=rule.get("network_cidr", ""),
+ )
+ for rule in item.get("rules", [])
+ ]
+ self.security_groups.append(
+ SecurityGroupResource(
+ id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ location=location,
+ description=item.get("description", ""),
+ is_default=bool(item.get("is_default", False)),
+ is_all_traffic_rule=bool(
+ item.get("is_all_traffic_rule", False)
+ ),
+ rules=rules,
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"securitygroup - Error fetching groups in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _fetch_node_security_groups(self):
+ from prowler.providers.e2enetworks.services.node.node_client import node_client
+
+ for node in node_client.nodes:
+ if not node.vm_id:
+ continue
+ try:
+ attached = self.client.get_data(
+ f"/security_group/{node.vm_id}/attach/",
+ location=node.location,
+ )
+ if not isinstance(attached, list):
+ continue
+
+ for item in attached:
+ rules = [
+ SecurityGroupRule(
+ id=str(rule.get("id", "")),
+ rule_type=rule.get("rule_type", ""),
+ protocol_name=rule.get("protocol_name", ""),
+ port_range=rule.get("port_range", ""),
+ network=rule.get("network", ""),
+ network_cidr=rule.get("network_cidr", ""),
+ )
+ for rule in item.get("rules", [])
+ ]
+ self.node_security_groups.append(
+ NodeSecurityGroup(
+ node_id=node.id,
+ node_name=node.name,
+ vm_id=node.vm_id,
+ location=node.location,
+ security_group_id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ is_default=bool(item.get("is_default", False)),
+ is_all_traffic_rule=bool(
+ item.get("is_all_traffic_rule", False)
+ ),
+ rules=rules,
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"securitygroup - Error fetching attached groups for node {node.id} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class SecurityGroupRule(BaseModel):
+ id: str
+ rule_type: str
+ protocol_name: str
+ port_range: str
+ network: str
+ network_cidr: str
+
+
+class SecurityGroupResource(BaseModel):
+ id: str
+ name: str
+ location: str
+ description: str = ""
+ is_default: bool = False
+ is_all_traffic_rule: bool = False
+ rules: list[SecurityGroupRule] = []
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+
+class NodeSecurityGroup(BaseModel):
+ node_id: str
+ node_name: str
+ vm_id: str
+ location: str
+ security_group_id: str
+ name: str
+ is_default: bool = False
+ is_all_traffic_rule: bool = False
+ rules: list[SecurityGroupRule] = []
+
+ @property
+ def resource_id(self) -> str:
+ return f"{self.node_id}:{self.security_group_id}"
+
+ @property
+ def resource_name(self) -> str:
+ return f"{self.node_name}/{self.name}"
diff --git a/tests/providers/oraclecloud/services/blockstorage/__init__.py b/prowler/providers/e2enetworks/services/storage/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/blockstorage/__init__.py
rename to prowler/providers/e2enetworks/services/storage/__init__.py
diff --git a/tests/providers/oraclecloud/services/blockstorage/blockstorage_block_volume_encrypted_with_cmk/__init__.py b/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/blockstorage/blockstorage_block_volume_encrypted_with_cmk/__init__.py
rename to prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/__init__.py
diff --git a/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.metadata.json b/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.metadata.json
new file mode 100644
index 0000000000..9c3b0b3391
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "storage_block_volume_not_orphaned",
+ "CheckTitle": "E2E Networks block volumes are not orphaned",
+ "CheckType": [],
+ "ServiceName": "storage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "**E2E Networks block volumes** in the `Available` state should be attached to a node rather than left provisioned without an owner.",
+ "Risk": "**Orphaned block volumes** remain provisioned without an attached workload, increasing storage cost and the risk of retaining **sensitive data** without active ownership.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/storage/block-storage/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach `Available` block volumes to nodes, or delete unused volumes after confirming the data is no longer needed.",
+ "Url": "https://hub.prowler.com/check/storage_block_volume_not_orphaned"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.py b/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.py
new file mode 100644
index 0000000000..0bbf7d488a
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_block_volume_not_orphaned/storage_block_volume_not_orphaned.py
@@ -0,0 +1,18 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.storage.storage_client import storage_client
+
+
+class storage_block_volume_not_orphaned(Check):
+ """Check that available block volumes are attached to a node."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for volume in storage_client.block_volumes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=volume)
+ report.status = "PASS"
+ report.status_extended = f"Block volume {volume.name} is attached or not in an available orphaned state."
+ if volume.status == "Available" and not volume.is_attached:
+ report.status = "FAIL"
+ report.status_extended = f"Block volume {volume.name} is available and not attached to any node."
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/storage/storage_client.py b/prowler/providers/e2enetworks/services/storage/storage_client.py
new file mode 100644
index 0000000000..b71905e363
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.e2enetworks.services.storage.storage_service import Storage
+
+storage_client = Storage(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/blockstorage/blockstorage_boot_volume_encrypted_with_cmk/__init__.py b/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/blockstorage/blockstorage_boot_volume_encrypted_with_cmk/__init__.py
rename to prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/__init__.py
diff --git a/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.metadata.json b/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.metadata.json
new file mode 100644
index 0000000000..7be4fdafe0
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "storage_efs_backup_enabled",
+ "CheckTitle": "E2E Networks EFS volumes have backup enabled",
+ "CheckType": [],
+ "ServiceName": "storage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "**E2E Networks EFS shared file systems** should have **backups** enabled so data can be recovered after failures or accidental changes.",
+ "Risk": "Shared file systems without **backups** increase the risk of permanent **data loss** during failures or accidental changes.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/storage/parallel-file-storage/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **backups** on EFS shared file systems to allow recovery after failures or accidental changes.",
+ "Url": "https://hub.prowler.com/check/storage_efs_backup_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.py b/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.py
new file mode 100644
index 0000000000..0e8272b338
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_efs_backup_enabled/storage_efs_backup_enabled.py
@@ -0,0 +1,20 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.storage.storage_client import storage_client
+
+
+class storage_efs_backup_enabled(Check):
+ """Check if E2E Networks EFS volumes have backup enabled."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for volume in storage_client.efs_volumes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=volume)
+ report.status = "PASS"
+ report.status_extended = f"EFS volume {volume.name} has backup enabled."
+ if not volume.is_backup_enabled:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"EFS volume {volume.name} does not have backup enabled."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/cloudguard/__init__.py b/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/cloudguard/__init__.py
rename to prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/__init__.py
diff --git a/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.metadata.json b/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.metadata.json
new file mode 100644
index 0000000000..1fd4d54e63
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.metadata.json
@@ -0,0 +1,34 @@
+{
+ "Provider": "e2enetworks",
+ "CheckID": "storage_efs_vpc_access_restricted",
+ "CheckTitle": "E2E Networks EFS volumes restrict VPC access",
+ "CheckType": [],
+ "ServiceName": "storage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "**E2E Networks EFS volumes** should restrict access to specific VPC resources instead of allowing every resource in the **VPC** to connect.",
+ "Risk": "EFS volumes that allow **all VPC resources** broaden access beyond **least privilege** within the network, increasing the blast radius of a compromised resource.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.e2enetworks.com/api/myaccount/storage/parallel-file-storage/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict EFS volume access to specific VPC resources instead of allowing all resources in the VPC.",
+ "Url": "https://hub.prowler.com/check/storage_efs_vpc_access_restricted"
+ }
+ },
+ "Categories": [],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.py b/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.py
new file mode 100644
index 0000000000..c3bd715fa6
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_efs_vpc_access_restricted/storage_efs_vpc_access_restricted.py
@@ -0,0 +1,22 @@
+from prowler.lib.check.models import Check, CheckReportE2eNetworks
+from prowler.providers.e2enetworks.services.storage.storage_client import storage_client
+
+
+class storage_efs_vpc_access_restricted(Check):
+ """Check if E2E Networks EFS volumes restrict VPC access."""
+
+ def execute(self) -> list[CheckReportE2eNetworks]:
+ findings = []
+ for volume in storage_client.efs_volumes:
+ report = CheckReportE2eNetworks(metadata=self.metadata(), resource=volume)
+ report.status = "PASS"
+ report.status_extended = (
+ f"EFS volume {volume.name} does not allow all VPC resources."
+ )
+ if volume.is_all_vpc_resources_allowed:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"EFS volume {volume.name} allows access from all VPC resources."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/e2enetworks/services/storage/storage_service.py b/prowler/providers/e2enetworks/services/storage/storage_service.py
new file mode 100644
index 0000000000..9038d727f1
--- /dev/null
+++ b/prowler/providers/e2enetworks/services/storage/storage_service.py
@@ -0,0 +1,158 @@
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.e2enetworks.lib.service.service import E2eNetworksService
+
+
+class Storage(E2eNetworksService):
+ """Service class for E2E Networks storage resources."""
+
+ def __init__(self, provider):
+ super().__init__("storage", provider)
+ self.block_volumes: list[BlockVolume] = []
+ self.efs_volumes: list[EfsVolume] = []
+ self.epfs_volumes: list[EpfsVolume] = []
+ self._fetch_block_volumes()
+ self._fetch_efs_volumes()
+ self._fetch_epfs_volumes()
+
+ def _fetch_block_volumes(self):
+ for location in self.provider.session.locations:
+ try:
+ volumes = self.client.paginate(
+ "/block_storage/",
+ location=location,
+ )
+ for item in volumes:
+ vm_detail = item.get("vm_detail", {}) or {}
+ self.block_volumes.append(
+ BlockVolume(
+ id=str(item.get("block_id", "")),
+ name=item.get("name", ""),
+ location=location,
+ status=item.get("status", ""),
+ size_string=item.get("size_string", ""),
+ is_attached=bool(vm_detail),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"storage - Error fetching block volumes in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _fetch_efs_volumes(self):
+ for location in self.provider.session.locations:
+ try:
+ volumes = self.client.paginate("/efs/", location=location)
+ for item in volumes:
+ self.efs_volumes.append(
+ EfsVolume(
+ id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ location=location,
+ status=item.get("status", ""),
+ vpc_id=str(item.get("vpc_id", "")),
+ is_backup_enabled=bool(
+ item.get("is_backup_enabled", False)
+ ),
+ is_all_vpc_resources_allowed=bool(
+ item.get("is_all_vpc_resources_allowed", False)
+ ),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"storage - Error fetching EFS volumes in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _fetch_epfs_volumes(self):
+ for location in self.provider.session.locations:
+ try:
+ all_items: list = []
+ page = 1
+ total_pages = 1
+ while page <= total_pages:
+ payload = self.client.get(
+ "/epfs/",
+ location=location,
+ params={"page": page, "page_size": 100},
+ )
+ data = payload.get("data", [])
+ if isinstance(data, list):
+ all_items.extend(data)
+ total_pages = int(payload.get("total_page_number", page))
+ if not data:
+ break
+ page += 1
+
+ for item in all_items:
+ vpc = item.get("vpc", {}) or {}
+ self.epfs_volumes.append(
+ EpfsVolume(
+ id=str(item.get("id", "")),
+ name=item.get("name", ""),
+ location=location,
+ vpc_network_id=str(vpc.get("network_id", "")),
+ vpc_name=vpc.get("name", ""),
+ deleted=bool(item.get("deleted", False)),
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"storage - Error fetching EPFS volumes in {location} -- "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class BlockVolume(BaseModel):
+ id: str
+ name: str
+ location: str
+ status: str = ""
+ size_string: str = ""
+ is_attached: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+
+class EfsVolume(BaseModel):
+ id: str
+ name: str
+ location: str
+ status: str = ""
+ vpc_id: str = ""
+ is_backup_enabled: bool = False
+ is_all_vpc_resources_allowed: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
+
+
+class EpfsVolume(BaseModel):
+ id: str
+ name: str
+ location: str
+ vpc_network_id: str = ""
+ vpc_name: str = ""
+ deleted: bool = False
+
+ @property
+ def resource_id(self) -> str:
+ return self.id
+
+ @property
+ def resource_name(self) -> str:
+ return self.name
diff --git a/prowler/providers/gcp/exceptions/exceptions.py b/prowler/providers/gcp/exceptions/exceptions.py
index 5c5845951c..09cb642cba 100644
--- a/prowler/providers/gcp/exceptions/exceptions.py
+++ b/prowler/providers/gcp/exceptions/exceptions.py
@@ -34,11 +34,17 @@ class GCPBaseException(ProwlerException):
"message": "Error loading Service Account Private Key credentials from dictionary",
"remediation": "Check the dictionary and ensure it contains a Service Account Private Key.",
},
+ (3011, "GCPGetOrganizationProjectsError"): {
+ "message": "Error retrieving projects under the organization via the Cloud Asset API",
+ "remediation": "Ensure the Cloud Asset API is enabled in the credentials' project and that the principal has 'roles/cloudasset.viewer' bound at the organization level. See https://cloud.google.com/asset-inventory/docs/access-control.",
+ },
}
def __init__(self, code, file=None, original_exception=None, message=None):
provider = "GCP"
- error_info = self.GCP_ERROR_CODES.get((code, self.__class__.__name__))
+ # Copy the catalog entry so a custom message does not mutate the
+ # class-level GCP_ERROR_CODES shared across exception instances.
+ error_info = dict(self.GCP_ERROR_CODES.get((code, self.__class__.__name__)))
if message:
error_info["message"] = message
super().__init__(
@@ -104,3 +110,10 @@ class GCPLoadServiceAccountKeyFromDictError(GCPCredentialsError):
super().__init__(
3010, file=file, original_exception=original_exception, message=message
)
+
+
+class GCPGetOrganizationProjectsError(GCPBaseException):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 3011, file=file, original_exception=original_exception, message=message
+ )
diff --git a/prowler/providers/gcp/gcp_provider.py b/prowler/providers/gcp/gcp_provider.py
index 5017b84c42..69ab9404ef 100644
--- a/prowler/providers/gcp/gcp_provider.py
+++ b/prowler/providers/gcp/gcp_provider.py
@@ -21,6 +21,8 @@ from prowler.providers.common.models import Audit_Metadata, Connection
from prowler.providers.common.provider import Provider
from prowler.providers.gcp.config import DEFAULT_RETRY_ATTEMPTS
from prowler.providers.gcp.exceptions.exceptions import (
+ GCPBaseException,
+ GCPGetOrganizationProjectsError,
GCPInvalidProviderIdError,
GCPLoadADCFromDictError,
GCPLoadServiceAccountKeyFromDictError,
@@ -59,6 +61,7 @@ class GcpProvider(Provider):
"""
_type: str = "gcp"
+ sdk_only: bool = False
_session: Credentials
_project_ids: list
_excluded_project_ids: list
@@ -621,10 +624,7 @@ class GcpProvider(Provider):
credentials_file: str
Returns:
- dict[str, GCPProject]
-
- Usage:
- >>> GcpProvider.get_projects(credentials=credentials, organization_id=organization_id)
+ dict of project_id and GCPProject object
"""
projects = {}
try:
@@ -632,7 +632,10 @@ class GcpProvider(Provider):
try:
# Initialize Cloud Asset Inventory API for recursive project retrieval
asset_service = discovery.build(
- "cloudasset", "v1", credentials=credentials
+ "cloudasset",
+ "v1",
+ credentials=credentials,
+ num_retries=DEFAULT_RETRY_ATTEMPTS,
)
# Set the scope to the specified organization and filter for projects
scope = f"organizations/{organization_id}"
@@ -643,7 +646,7 @@ class GcpProvider(Provider):
)
while request is not None:
- response = request.execute()
+ response = request.execute(num_retries=DEFAULT_RETRY_ATTEMPTS)
for asset in response.get("assets", []):
# Extract labels and other project details
@@ -688,13 +691,25 @@ class GcpProvider(Provider):
)
except HttpError as http_error:
if "Cloud Asset API has not been used" in str(http_error):
- logger.error(
- f"Projects cannot be retrieved from the Organization since Cloud Asset API has not been used before or it is disabled [{http_error.__traceback__.tb_lineno}]. Enable it by visiting https://console.developers.google.com/apis/api/cloudasset.googleapis.com/ then retry."
+ message = (
+ "Projects cannot be retrieved from the Organization since the Cloud Asset API "
+ "has not been used before or it is disabled. Enable it by visiting "
+ "https://console.developers.google.com/apis/api/cloudasset.googleapis.com/ then retry."
)
else:
- logger.error(
- f"{http_error.__class__.__name__}[{http_error.__traceback__.tb_lineno}]: {http_error}"
+ message = (
+ f"Cloud Asset API call failed while listing projects under organization "
+ f"'{organization_id}': {http_error}. Ensure the credentials' principal has "
+ "'roles/cloudasset.viewer' bound at the organization level."
)
+ logger.critical(
+ f"{http_error.__class__.__name__}[{http_error.__traceback__.tb_lineno}]: {message}"
+ )
+ raise GCPGetOrganizationProjectsError(
+ file=__file__,
+ original_exception=http_error,
+ message=message,
+ )
else:
try:
# Initialize Cloud Resource Manager API for simple project listing
@@ -781,8 +796,10 @@ class GcpProvider(Provider):
labels={},
lifecycle_state="ACTIVE",
)
- # If no projects were able to be accessed via API, add them manually from the credentials file
- elif credentials_file:
+ # If no projects were able to be accessed via API, add them manually from the credentials file.
+ # Skip this fallback when an organization scan was explicitly requested: silently
+ # downgrading scope to the service account's home project hides permission errors.
+ elif credentials_file and not organization_id:
with open(credentials_file, "r", encoding="utf-8") as file:
project_id = json.load(file)["project_id"]
# Handle empty or null project names
@@ -798,6 +815,8 @@ class GcpProvider(Provider):
labels={},
lifecycle_state="ACTIVE",
)
+ except GCPBaseException as gcp_error:
+ raise gcp_error
except Exception as error:
logger.critical(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
diff --git a/tests/providers/oraclecloud/services/cloudguard/cloudguard_enabled/__init__.py b/prowler/providers/gcp/services/cloudfunction/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/cloudguard/cloudguard_enabled/__init__.py
rename to prowler/providers/gcp/services/cloudfunction/__init__.py
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_client.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_client.py
new file mode 100644
index 0000000000..a252da1be7
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.gcp.services.cloudfunction.cloudfunction_service import (
+ CloudFunction,
+)
+
+cloudfunction_client = CloudFunction(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/compute/__init__.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/compute/__init__.py
rename to prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/__init__.py
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.metadata.json b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.metadata.json
new file mode 100644
index 0000000000..72c908bf80
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "gcp",
+ "CheckID": "cloudfunction_function_inside_vpc",
+ "CheckTitle": "Cloud Function is connected to a VPC network",
+ "CheckType": [],
+ "ServiceName": "cloudfunction",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "cloudfunctions.googleapis.com/Function",
+ "Description": "Cloud Functions are attached to a **Serverless VPC Access connector** so egress traffic is routed through a private VPC network instead of the public internet.\n\nThe evaluation reviews each function's network configuration to confirm that a connector is configured.",
+ "Risk": "Without a VPC connector, Cloud Functions cannot privately reach internal resources such as `Cloud SQL`, `Memorystore`, or `GKE`, forcing those services to be exposed over public IPs. This expands the **attack surface**, weakens **confidentiality** of internal traffic, and breaks network segmentation controls required by most security frameworks.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://cloud.google.com/functions/docs/networking/connecting-vpc",
+ "https://cloud.google.com/vpc/docs/serverless-vpc-access"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud functions deploy <FUNCTION_NAME> --region=<REGION> --vpc-connector=projects/<PROJECT_ID>/locations/<REGION>/connectors/<CONNECTOR_NAME> --egress-settings=all-traffic",
+ "NativeIaC": "",
+ "Other": "1. In Google Cloud Console, go to Cloud Functions\n2. Select the function and click Edit\n3. Under Connections, select the VPC connector for your network\n4. Set Egress settings to route all traffic through the VPC connector\n5. Save and redeploy the function",
+ "Terraform": "```hcl\nresource \"google_cloudfunctions2_function\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n location = \"us-central1\"\n\n service_config {\n vpc_connector = \"<example_resource_id>\" # Critical: routes egress through the VPC\n vpc_connector_egress_settings = \"ALL_TRAFFIC\"\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Apply **defense in depth** by routing Cloud Function egress through a **Serverless VPC Access connector** when the function must reach internal resources.\n\nScope each connector to **least privilege** subnets so functions cannot reach unintended endpoints.",
+ "Url": "https://hub.prowler.com/check/cloudfunction_function_inside_vpc"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "cloudfunction_function_not_publicly_accessible",
+ "cloudsql_instance_public_ip",
+ "compute_instance_public_ip"
+ ],
+ "Notes": "A VPC connector must be created in the same region as the Cloud Function. This check only verifies that a connector is attached; it does not validate egress settings or connector configuration."
+}
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.py
new file mode 100644
index 0000000000..3b28db7d8e
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_inside_vpc/cloudfunction_function_inside_vpc.py
@@ -0,0 +1,43 @@
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.cloudfunction.cloudfunction_client import (
+ cloudfunction_client,
+)
+
+
+class cloudfunction_function_inside_vpc(Check):
+ """Check that Cloud Functions are attached to a Serverless VPC Access connector.
+
+ Verifies that each active Cloud Function has a `vpcConnector` configured so
+ egress traffic flows through a private VPC network instead of the public
+ internet. Functions in non-`ACTIVE` states are skipped because their network
+ configuration is transient.
+ """
+
+ def execute(self) -> list[Check_Report_GCP]:
+ """Execute the VPC-connector check across all Cloud Functions.
+
+ Returns:
+ A list of `Check_Report_GCP` findings, one per active Cloud
+ Function. Status is `PASS` when a `vpc_connector` is set and `FAIL`
+ otherwise.
+ """
+ findings = []
+ for function in cloudfunction_client.functions:
+ if function.state != "ACTIVE":
+ continue
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=function,
+ resource_id=function.name,
+ )
+ if function.vpc_connector:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Cloud Function {function.name} is connected to a VPC via "
+ f"connector: {function.vpc_connector}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Cloud Function {function.name} is not connected to any VPC network."
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/compute/compute_instance_in_transit_encryption_enabled/__init__.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/compute/compute_instance_in_transit_encryption_enabled/__init__.py
rename to prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/__init__.py
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.metadata.json b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.metadata.json
new file mode 100644
index 0000000000..8c9247b2bd
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "gcp",
+ "CheckID": "cloudfunction_function_not_publicly_accessible",
+ "CheckTitle": "Cloud Function is not publicly invocable",
+ "CheckType": [],
+ "ServiceName": "cloudfunction",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "cloudfunctions.googleapis.com/Function",
+ "Description": "Cloud Functions deny invocation to `allUsers` and `allAuthenticatedUsers`, so only **explicitly authorized identities or services** can trigger them.\n\nThe evaluation reviews each function's IAM policy bindings to confirm no public principals are granted invoker access.",
+ "Risk": "Publicly invocable Cloud Functions expose **business logic** to the internet and let any caller trigger execution. This enables **unauthorized data access** when the function returns sensitive output, **code execution** in shared environments, and **denial-of-wallet** attacks driven by uncontrolled invocation costs.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://cloud.google.com/functions/docs/securing/authenticating",
+ "https://cloud.google.com/iam/docs/overview"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud functions remove-iam-policy-binding <FUNCTION_NAME> --region=<REGION> --member=<allUsers|allAuthenticatedUsers> --role=roles/cloudfunctions.invoker",
+ "NativeIaC": "",
+ "Other": "1. In Google Cloud Console, go to Cloud Functions\n2. Select the function and open the Permissions tab\n3. Remove any binding with allUsers or allAuthenticatedUsers\n4. Grant invocation rights only to specific service accounts or user groups",
+ "Terraform": "```hcl\nresource \"google_cloudfunctions2_function_iam_binding\" \"<example_resource_name>\" {\n project = \"<example_resource_id>\"\n location = \"<example_resource_id>\"\n cloud_function = \"<example_resource_name>\"\n role = \"roles/cloudfunctions.invoker\"\n members = [\"serviceAccount:<example_resource_id>\"] # Critical: never include allUsers or allAuthenticatedUsers\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Apply **least privilege** to Cloud Function invocation: grant `roles/cloudfunctions.invoker` only to specific service accounts or groups.\n\nFor externally exposed functions, front them with **API Gateway** or **Cloud Endpoints** that enforce authentication and rate limiting.",
+ "Url": "https://hub.prowler.com/check/cloudfunction_function_not_publicly_accessible"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "cloudfunction_function_inside_vpc",
+ "secretmanager_secret_not_publicly_accessible",
+ "cloudstorage_bucket_public_access"
+ ],
+ "Notes": "This check evaluates function-level IAM policies. Organization policy constraints/iam.allowedPolicyMemberDomains can prevent public bindings at the org level."
+}
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.py
new file mode 100644
index 0000000000..14ee874f22
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_function_not_publicly_accessible/cloudfunction_function_not_publicly_accessible.py
@@ -0,0 +1,44 @@
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.cloudfunction.cloudfunction_client import (
+ cloudfunction_client,
+)
+
+
+class cloudfunction_function_not_publicly_accessible(Check):
+ """Check that Cloud Functions do not grant invocation rights to all users.
+
+ Verifies that no active Cloud Function has an IAM binding granting access
+ to `allUsers` or `allAuthenticatedUsers`. Non-`ACTIVE` functions are
+ skipped because their IAM bindings are transient.
+ """
+
+ def execute(self) -> list[Check_Report_GCP]:
+ """Execute the public-access check across all Cloud Functions.
+
+ Returns:
+ A list of `Check_Report_GCP` findings, one per active Cloud
+ Function. Status is `FAIL` when the function is invokable by
+ `allUsers` or `allAuthenticatedUsers` and `PASS` otherwise.
+ """
+ findings = []
+ for function in cloudfunction_client.functions:
+ if function.state != "ACTIVE":
+ continue
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=function,
+ resource_id=function.name,
+ )
+ if function.publicly_accessible:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Cloud Function {function.name} is publicly invocable "
+ f"(allUsers or allAuthenticatedUsers IAM binding detected)."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Cloud Function {function.name} is not publicly accessible."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/gcp/services/cloudfunction/cloudfunction_service.py b/prowler/providers/gcp/services/cloudfunction/cloudfunction_service.py
new file mode 100644
index 0000000000..9905c98748
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudfunction/cloudfunction_service.py
@@ -0,0 +1,146 @@
+from typing import Optional
+
+from googleapiclient import discovery
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.gcp.config import DEFAULT_RETRY_ATTEMPTS
+from prowler.providers.gcp.gcp_provider import GcpProvider
+from prowler.providers.gcp.lib.service.service import GCPService
+
+
+class CloudFunction(GCPService):
+ """Cloud Functions v2 service client.
+
+ Enumerates Cloud Functions across every accessible project and region
+ using the `cloudfunctions.googleapis.com` v2 API and exposes them through
+ the `functions` attribute.
+ """
+
+ def __init__(self, provider: GcpProvider) -> None:
+ """Initialize the service and preload Cloud Functions."""
+ super().__init__("cloudfunctions", provider, api_version="v2")
+ self.functions = []
+ self._run_client = None
+ self._get_functions()
+ self._get_functions_iam_policy()
+
+ def _get_functions(self) -> None:
+ """Fetch Cloud Functions for every project and location."""
+ for project_id in self.project_ids:
+ try:
+ locations = self.client.projects().locations()
+ locations_request = locations.list(name=f"projects/{project_id}")
+ while locations_request is not None:
+ locations_response = locations_request.execute(
+ num_retries=DEFAULT_RETRY_ATTEMPTS
+ )
+ for location in locations_response.get("locations", []):
+ location_id = location["locationId"]
+ try:
+ functions = locations.functions()
+ request = functions.list(
+ parent=f"projects/{project_id}/locations/{location_id}"
+ )
+ while request is not None:
+ response = request.execute(
+ num_retries=DEFAULT_RETRY_ATTEMPTS
+ )
+ for fn in response.get("functions", []):
+ service_config = fn.get("serviceConfig", {})
+ self.functions.append(
+ Function(
+ id=fn["name"],
+ name=fn["name"].split("/")[-1],
+ project_id=project_id,
+ location=location_id,
+ state=fn.get("state", "UNKNOWN"),
+ environment=fn.get("environment", "GEN_1"),
+ service=service_config.get("service"),
+ vpc_connector=service_config.get(
+ "vpcConnector"
+ ),
+ )
+ )
+ request = functions.list_next(
+ previous_request=request,
+ previous_response=response,
+ )
+ except Exception as error:
+ logger.error(
+ f"{location_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ locations_request = locations.list_next(
+ previous_request=locations_request,
+ previous_response=locations_response,
+ )
+ except Exception as error:
+ logger.error(
+ f"{project_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _get_functions_iam_policy(self) -> None:
+ """Fetch IAM policy for every Cloud Function in parallel.
+
+ For gen2 functions, IAM is delegated to the underlying Cloud Run
+ service, so a `run.googleapis.com` v2 client is required.
+ """
+ if any(f.environment == "GEN_2" for f in self.functions):
+ self._run_client = discovery.build(
+ "run",
+ "v2",
+ credentials=self.credentials,
+ num_retries=DEFAULT_RETRY_ATTEMPTS,
+ )
+ self.__threading_call__(self._get_function_iam_policy, self.functions)
+
+ def _get_function_iam_policy(self, function: "Function") -> None:
+ """Mark a Cloud Function as publicly accessible when bound to `allUsers` or `allAuthenticatedUsers`.
+
+ Cloud Functions gen2 delegates invocation IAM to its backing Cloud Run
+ service, so the binding is queried via the Run API. Gen1 functions are
+ queried through the Cloud Functions API directly.
+ """
+ try:
+ if function.environment == "GEN_2" and function.service:
+ response = (
+ self._run_client.projects()
+ .locations()
+ .services()
+ .getIamPolicy(resource=function.service)
+ .execute(num_retries=DEFAULT_RETRY_ATTEMPTS)
+ )
+ else:
+ response = (
+ self.client.projects()
+ .locations()
+ .functions()
+ .getIamPolicy(resource=function.id)
+ .execute(
+ http=self.__get_AuthorizedHttp_client__(),
+ num_retries=DEFAULT_RETRY_ATTEMPTS,
+ )
+ )
+ for binding in response.get("bindings", []):
+ members = binding.get("members", [])
+ if "allUsers" in members or "allAuthenticatedUsers" in members:
+ function.publicly_accessible = True
+ break
+ except Exception as error:
+ logger.error(
+ f"{function.location} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class Function(BaseModel):
+ """Cloud Function resource consumed by GCP checks."""
+
+ id: str
+ name: str
+ project_id: str
+ location: str
+ state: str
+ environment: str = "GEN_1"
+ service: Optional[str] = None
+ vpc_connector: Optional[str] = None
+ publicly_accessible: bool = False
diff --git a/tests/providers/oraclecloud/services/compute/compute_instance_legacy_metadata_endpoint_disabled/__init__.py b/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/compute/compute_instance_legacy_metadata_endpoint_disabled/__init__.py
rename to prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/__init__.py
diff --git a/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.metadata.json b/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.metadata.json
new file mode 100644
index 0000000000..3e66f9cdd3
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "gcp",
+ "CheckID": "cloudsql_instance_high_availability_enabled",
+ "CheckTitle": "Cloud SQL instance has high availability (REGIONAL) configured",
+ "CheckType": [],
+ "ServiceName": "cloudsql",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "sqladmin.googleapis.com/Instance",
+ "Description": "Ensures that Cloud SQL instances have high availability configured by setting availabilityType to REGIONAL. A REGIONAL instance maintains a standby replica in a different zone within the same region and automatically fails over on zone-level outages.",
+ "Risk": "Instances with ZONAL availability have no standby replica. A zone-level outage will cause database downtime until manual recovery, violating availability requirements and potentially breaching SLAs and ISMS-P 2.12.1 disaster preparedness controls.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://cloud.google.com/sql/docs/postgres/high-availability",
+ "https://cloud.google.com/sql/docs/sqlserver/high-availability"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud sql instances patch <INSTANCE_NAME> --availability-type=REGIONAL",
+ "NativeIaC": "",
+ "Other": "1. Go to Google Cloud Console > SQL > Instances.\n2. Click the instance name, then Edit.\n3. Under Availability, select Multiple zones (Highly available).\n4. Click Save.",
+ "Terraform": "```hcl\nresource \"google_sql_database_instance\" \"example\" {\n name = \"<instance_name>\"\n database_version = \"POSTGRES_15\"\n region = \"<region>\"\n\n settings {\n tier = \"db-custom-2-7680\"\n\n availability_type = \"REGIONAL\" # Critical: enables HA standby replica\n\n backup_configuration {\n enabled = true\n start_time = \"02:00\"\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Set availabilityType to REGIONAL for all production Cloud SQL instances. This creates a standby replica in a different zone and enables automatic failover, reducing RTO in the event of a zone outage.",
+ "Url": "https://hub.prowler.com/check/cloudsql_instance_high_availability_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "cloudsql_instance_automated_backups"
+ ],
+ "Notes": "Enabling HA increases instance cost approximately 2x due to the standby replica. ZONAL instances are acceptable for non-production workloads where downtime is tolerable."
+}
diff --git a/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.py b/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.py
new file mode 100644
index 0000000000..37bf576345
--- /dev/null
+++ b/prowler/providers/gcp/services/cloudsql/cloudsql_instance_high_availability_enabled/cloudsql_instance_high_availability_enabled.py
@@ -0,0 +1,41 @@
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.cloudsql.cloudsql_client import cloudsql_client
+
+
+class cloudsql_instance_high_availability_enabled(Check):
+ """Check that Cloud SQL primary instances are configured for high availability.
+
+ Verifies that each Cloud SQL primary instance has `availabilityType` set to
+ `REGIONAL`, which provisions a standby replica in a different zone within
+ the same region and enables automatic failover on zone-level outages. Read
+ replicas are skipped because they inherit availability from their primary.
+ """
+
+ def execute(self) -> list[Check_Report_GCP]:
+ """Execute the high availability check across all Cloud SQL instances.
+
+ Returns:
+ A list of `Check_Report_GCP` findings, one per Cloud SQL primary
+ instance. Status is `PASS` when `availability_type == "REGIONAL"`
+ and `FAIL` otherwise.
+ """
+ findings = []
+ for instance in cloudsql_client.instances:
+ if instance.instance_type != "CLOUD_SQL_INSTANCE":
+ continue
+ report = Check_Report_GCP(metadata=self.metadata(), resource=instance)
+ if instance.availability_type == "REGIONAL":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Database instance {instance.name} has high availability "
+ f"(REGIONAL) configured."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Database instance {instance.name} does not have high "
+ f"availability configured (current: "
+ f"{instance.availability_type})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/gcp/services/cloudsql/cloudsql_service.py b/prowler/providers/gcp/services/cloudsql/cloudsql_service.py
index 137169999a..1fe706bb02 100644
--- a/prowler/providers/gcp/services/cloudsql/cloudsql_service.py
+++ b/prowler/providers/gcp/services/cloudsql/cloudsql_service.py
@@ -46,6 +46,9 @@ class CloudSQL(GCPService):
"authorizedNetworks", []
),
flags=settings.get("databaseFlags", []),
+ availability_type=settings.get(
+ "availabilityType", "ZONAL"
+ ),
instance_type=instance.get(
"instanceType", "CLOUD_SQL_INSTANCE"
),
@@ -76,6 +79,7 @@ class Instance(BaseModel):
ssl_mode: str
automated_backups: bool
flags: list
+ availability_type: str = "ZONAL"
instance_type: str = "CLOUD_SQL_INSTANCE"
cmek_key_name: Optional[str] = None
project_id: str
diff --git a/prowler/providers/gcp/services/compute/compute_service.py b/prowler/providers/gcp/services/compute/compute_service.py
index 0965142766..41cce29a7b 100644
--- a/prowler/providers/gcp/services/compute/compute_service.py
+++ b/prowler/providers/gcp/services/compute/compute_service.py
@@ -87,9 +87,15 @@ class Compute(GCPService):
.execute(num_retries=DEFAULT_RETRY_ATTEMPTS)
)
for item in response["commonInstanceMetadata"].get("items", []):
- if item["key"] == "enable-oslogin" and item["value"] == "TRUE":
+ if (
+ item["key"] == "enable-oslogin"
+ and item["value"].lower() == "true"
+ ):
enable_oslogin = True
- if item["key"] == "enable-oslogin-2fa" and item["value"] == "TRUE":
+ if (
+ item["key"] == "enable-oslogin-2fa"
+ and item["value"].lower() == "true"
+ ):
enable_oslogin_2fa = True
self.compute_projects.append(
Project(
diff --git a/prowler/providers/gcp/services/iam/iam_service.py b/prowler/providers/gcp/services/iam/iam_service.py
index 13e96276e7..987a86068c 100644
--- a/prowler/providers/gcp/services/iam/iam_service.py
+++ b/prowler/providers/gcp/services/iam/iam_service.py
@@ -37,6 +37,7 @@ class IAM(GCPService):
display_name=account.get("displayName", ""),
project_id=project_id,
uniqueId=account.get("uniqueId", ""),
+ disabled=account.get("disabled", False),
)
)
@@ -102,6 +103,7 @@ class ServiceAccount(BaseModel):
keys: list[Key] = []
project_id: str
uniqueId: str
+ disabled: bool = False
class AccessApproval(GCPService):
diff --git a/prowler/providers/gcp/services/iam/iam_service_account_unused/iam_service_account_unused.py b/prowler/providers/gcp/services/iam/iam_service_account_unused/iam_service_account_unused.py
index 12440aff25..912237b9e5 100644
--- a/prowler/providers/gcp/services/iam/iam_service_account_unused/iam_service_account_unused.py
+++ b/prowler/providers/gcp/services/iam/iam_service_account_unused/iam_service_account_unused.py
@@ -19,7 +19,12 @@ class iam_service_account_unused(Check):
resource_id=account.email,
location=iam_client.region,
)
- if account.uniqueId in sa_ids_used:
+ if account.disabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Service Account {account.email} is disabled and cannot be used."
+ )
+ elif account.uniqueId in sa_ids_used:
report.status = "PASS"
report.status_extended = f"Service Account {account.email} was used over the last {max_unused_days} days."
else:
diff --git a/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.metadata.json b/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.metadata.json
index 5efe894b04..7312ffefeb 100644
--- a/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.metadata.json
+++ b/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.metadata.json
@@ -1,14 +1,14 @@
{
"Provider": "gcp",
"CheckID": "kms_key_rotation_enabled",
- "CheckTitle": "KMS key is rotated at least annually",
+ "CheckTitle": "KMS key has automatic rotation enabled",
"CheckType": [],
"ServiceName": "kms",
"SubServiceName": "",
"ResourceIdTemplate": "",
"Severity": "low",
"ResourceType": "cloudkms.googleapis.com/CryptoKey",
- "Description": "Google Cloud KMS customer-managed keys have **automatic rotation** enabled or a rotation interval `365` days.\n\nThe evaluation reviews each key's rotation settings to confirm periodic creation of new key versions.",
+ "Description": "Google Cloud KMS customer-managed keys have **automatic rotation** enabled, regardless of the rotation interval.\n\nThe evaluation reviews each key's rotation settings to confirm that a rotation period is configured so new key versions are created periodically.",
"Risk": "Without timely rotation, a stolen key can decrypt an expanding volume of data, eroding **confidentiality**. Prolonged key lifetimes widen windows for misuse, impact **integrity** of protected workloads, and make emergency rollover harder, risking **availability** disruptions.",
"RelatedUrl": "",
"AdditionalURLs": [
@@ -17,13 +17,13 @@
],
"Remediation": {
"Code": {
- "CLI": "gcloud kms keys update <KEY_NAME> --keyring=<KEY_RING> --location=<LOCATION> --rotation-period=365d --next-rotation-time=<RFC3339_TIME>",
+ "CLI": "gcloud kms keys update <KEY_NAME> --keyring=<KEY_RING> --location=<LOCATION> --rotation-period=<PERIOD> --next-rotation-time=<RFC3339_TIME>",
"NativeIaC": "",
- "Other": "1. In Google Cloud Console, go to Security > Key Management > Key rings\n2. Open the key ring and select the key\n3. Click Edit rotation schedule (or Set rotation schedule)\n4. Set Rotation period to 365 days or less\n5. Set Next rotation date/time\n6. Click Save",
- "Terraform": "```hcl\nresource \"google_kms_crypto_key\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n key_ring = \"<example_resource_id>\"\n purpose = \"ENCRYPT_DECRYPT\"\n\n rotation_period = \"31536000s\" # Critical: sets automatic rotation to 365 days (<= 365 ensures PASS)\n}\n```"
+ "Other": "1. In Google Cloud Console, go to Security > Key Management > Key rings\n2. Open the key ring and select the key\n3. Click Edit rotation schedule (or Set rotation schedule)\n4. Set a Rotation period\n5. Set Next rotation date/time\n6. Click Save",
+ "Terraform": "```hcl\nresource \"google_kms_crypto_key\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n key_ring = \"<example_resource_id>\"\n purpose = \"ENCRYPT_DECRYPT\"\n\n rotation_period = \"7776000s\" # Critical: enables automatic rotation (any period ensures PASS)\n}\n```"
},
"Recommendation": {
- "Text": "Enable **auto-rotation** for customer-managed keys with an interval `365` days.\n\nAdopt a **key lifecycle** policy: enforce **least privilege** on key usage, apply **separation of duties** between key admins and users, monitor key access, and rehearse emergency rotation to minimize blast radius.",
+ "Text": "Enable **auto-rotation** for customer-managed keys by configuring a rotation period.\n\nAdopt a **key lifecycle** policy: enforce **least privilege** on key usage, apply **separation of duties** between key admins and users, monitor key access, and rehearse emergency rotation to minimize blast radius.",
"Url": "https://hub.prowler.com/check/kms_key_rotation_enabled"
}
},
@@ -31,6 +31,8 @@
"encryption"
],
"DependsOn": [],
- "RelatedTo": [],
+ "RelatedTo": [
+ "kms_key_rotation_max_90_days"
+ ],
"Notes": ""
}
diff --git a/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.py b/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.py
index 577a7c9f99..ae924ca380 100644
--- a/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.py
+++ b/prowler/providers/gcp/services/kms/kms_key_rotation_enabled/kms_key_rotation_enabled.py
@@ -1,5 +1,3 @@
-import datetime
-
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.kms.kms_client import kms_client
@@ -9,36 +7,16 @@ class kms_key_rotation_enabled(Check):
findings = []
for key in kms_client.crypto_keys:
report = Check_Report_GCP(metadata=self.metadata(), resource=key)
- now = datetime.datetime.now()
- condition_next_rotation_time = False
- if key.next_rotation_time:
- try:
- next_rotation_time = datetime.datetime.strptime(
- key.next_rotation_time, "%Y-%m-%dT%H:%M:%S.%fZ"
- )
- except ValueError:
- next_rotation_time = datetime.datetime.strptime(
- key.next_rotation_time, "%Y-%m-%dT%H:%M:%SZ"
- )
- condition_next_rotation_time = (
- abs((next_rotation_time - now).days) <= 90
- )
- condition_rotation_period = False
if key.rotation_period:
- condition_rotation_period = (
- int(key.rotation_period[:-1]) // (24 * 3600) <= 90
- )
- if condition_rotation_period and condition_next_rotation_time:
report.status = "PASS"
- report.status_extended = f"Key {key.name} is rotated every 90 days or less and the next rotation time is in less than 90 days."
+ report.status_extended = (
+ f"Key {key.name} has automatic rotation enabled."
+ )
else:
report.status = "FAIL"
- if condition_rotation_period:
- report.status_extended = f"Key {key.name} is rotated every 90 days or less but the next rotation time is in more than 90 days."
- elif condition_next_rotation_time:
- report.status_extended = f"Key {key.name} is not rotated every 90 days or less but the next rotation time is in less than 90 days."
- else:
- report.status_extended = f"Key {key.name} is not rotated every 90 days or less and the next rotation time is in more than 90 days."
+ report.status_extended = (
+ f"Key {key.name} does not have automatic rotation enabled."
+ )
findings.append(report)
return findings
diff --git a/tests/providers/oraclecloud/services/compute/compute_instance_secure_boot_enabled/__init__.py b/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/compute/compute_instance_secure_boot_enabled/__init__.py
rename to prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/__init__.py
diff --git a/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.metadata.json b/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.metadata.json
new file mode 100644
index 0000000000..f1597fee53
--- /dev/null
+++ b/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "gcp",
+ "CheckID": "kms_key_rotation_max_90_days",
+ "CheckTitle": "KMS key is rotated every 90 days or less",
+ "CheckType": [],
+ "ServiceName": "kms",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "cloudkms.googleapis.com/CryptoKey",
+ "Description": "Google Cloud KMS customer-managed keys are rotated with an interval of `90` days or less, in line with the CIS Benchmark.\n\nThe evaluation reviews each key's rotation settings to confirm that both the rotation period and the next rotation time stay within 90 days.",
+ "Risk": "Without timely rotation, a stolen key can decrypt an expanding volume of data, eroding **confidentiality**. Prolonged key lifetimes widen windows for misuse, impact **integrity** of protected workloads, and make emergency rollover harder, risking **availability** disruptions.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/CloudKMS/rotate-kms-encryption-keys.html",
+ "https://cloud.google.com/iam/docs/manage-access-service-accounts"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud kms keys update <KEY_NAME> --keyring=<KEY_RING> --location=<LOCATION> --rotation-period=90d --next-rotation-time=<RFC3339_TIME>",
+ "NativeIaC": "",
+ "Other": "1. In Google Cloud Console, go to Security > Key Management > Key rings\n2. Open the key ring and select the key\n3. Click Edit rotation schedule (or Set rotation schedule)\n4. Set Rotation period to 90 days or less\n5. Set Next rotation date/time\n6. Click Save",
+ "Terraform": "```hcl\nresource \"google_kms_crypto_key\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n key_ring = \"<example_resource_id>\"\n purpose = \"ENCRYPT_DECRYPT\"\n\n rotation_period = \"7776000s\" # Critical: sets automatic rotation to 90 days (<= 90 ensures PASS)\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **auto-rotation** for customer-managed keys with an interval of `90` days or less.\n\nAdopt a **key lifecycle** policy: enforce **least privilege** on key usage, apply **separation of duties** between key admins and users, monitor key access, and rehearse emergency rotation to minimize blast radius.",
+ "Url": "https://hub.prowler.com/check/kms_key_rotation_max_90_days"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "kms_key_rotation_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.py b/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.py
new file mode 100644
index 0000000000..cbca4f0e91
--- /dev/null
+++ b/prowler/providers/gcp/services/kms/kms_key_rotation_max_90_days/kms_key_rotation_max_90_days.py
@@ -0,0 +1,44 @@
+import datetime
+
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.kms.kms_client import kms_client
+
+
+class kms_key_rotation_max_90_days(Check):
+ def execute(self) -> Check_Report_GCP:
+ findings = []
+ for key in kms_client.crypto_keys:
+ report = Check_Report_GCP(metadata=self.metadata(), resource=key)
+ now = datetime.datetime.now()
+ condition_next_rotation_time = False
+ if key.next_rotation_time:
+ try:
+ next_rotation_time = datetime.datetime.strptime(
+ key.next_rotation_time, "%Y-%m-%dT%H:%M:%S.%fZ"
+ )
+ except ValueError:
+ next_rotation_time = datetime.datetime.strptime(
+ key.next_rotation_time, "%Y-%m-%dT%H:%M:%SZ"
+ )
+ condition_next_rotation_time = (
+ abs((next_rotation_time - now).days) <= 90
+ )
+ condition_rotation_period = False
+ if key.rotation_period:
+ condition_rotation_period = (
+ int(key.rotation_period[:-1]) // (24 * 3600) <= 90
+ )
+ if condition_rotation_period and condition_next_rotation_time:
+ report.status = "PASS"
+ report.status_extended = f"Key {key.name} is rotated every 90 days or less and the next rotation time is in less than 90 days."
+ else:
+ report.status = "FAIL"
+ if condition_rotation_period:
+ report.status_extended = f"Key {key.name} is rotated every 90 days or less but the next rotation time is in more than 90 days."
+ elif condition_next_rotation_time:
+ report.status_extended = f"Key {key.name} is not rotated every 90 days or less but the next rotation time is in less than 90 days."
+ else:
+ report.status_extended = f"Key {key.name} is not rotated every 90 days or less and the next rotation time is in more than 90 days."
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled.py
index 4654be4d29..84bf078dac 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -10,12 +13,10 @@ class logging_log_metric_filter_and_alert_for_audit_configuration_changes_enable
):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'protoPayload.methodName="SetIamPolicy" AND protoPayload.serviceData.policyDelta.auditConfigDeltas:*'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'protoPayload.methodName="SetIamPolicy" AND protoPayload.serviceData.policyDelta.auditConfigDeltas:*'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -33,6 +34,11 @@ class logging_log_metric_filter_and_alert_for_audit_configuration_changes_enable
break
findings.append(report)
+ # Credit projects whose logs are centrally monitored via an org-level
+ # aggregated sink to a bucket-scoped metric + alert (instead of failing them).
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -46,8 +52,12 @@ class logging_log_metric_filter_and_alert_for_audit_configuration_changes_enable
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled.py
index 166f7b7ee8..e7d74f3f8e 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled/logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'resource.type="gcs_bucket" AND protoPayload.methodName="storage.setIamPermissions"'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'resource.type="gcs_bucket" AND protoPayload.methodName="storage.setIamPermissions"'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
metric_name = getattr(metric, "name", None) or "unknown"
report = Check_Report_GCP(
metadata=self.metadata(),
@@ -36,6 +37,9 @@ class logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled(
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
project_obj = logging_client.projects.get(project)
@@ -46,8 +50,12 @@ class logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled(
location=logging_client.region,
resource_name=(getattr(project_obj, "name", None) or "GCP Project"),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled.py
index 7902f9ed72..cf7cdb1679 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -10,9 +13,10 @@ class logging_log_metric_filter_and_alert_for_compute_configuration_changes_enab
):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'protoPayload.serviceName="compute.googleapis.com"'
projects_with_metric = set()
for metric in logging_client.metrics:
- if 'protoPayload.serviceName="compute.googleapis.com"' in metric.filter:
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -30,6 +34,9 @@ class logging_log_metric_filter_and_alert_for_compute_configuration_changes_enab
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -43,8 +50,12 @@ class logging_log_metric_filter_and_alert_for_compute_configuration_changes_enab
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated for Compute Engine configuration changes in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated for Compute Engine configuration changes in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled.py
index 1e6584e5fb..f836dc25b2 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled/logging_log_metric_filter_and_alert_for_custom_role_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_custom_role_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'resource.type="iam_role" AND (protoPayload.methodName="google.iam.admin.v1.CreateRole" OR protoPayload.methodName="google.iam.admin.v1.DeleteRole" OR protoPayload.methodName="google.iam.admin.v1.UpdateRole")'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'resource.type="iam_role" AND (protoPayload.methodName="google.iam.admin.v1.CreateRole" OR protoPayload.methodName="google.iam.admin.v1.DeleteRole" OR protoPayload.methodName="google.iam.admin.v1.UpdateRole")'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -31,6 +32,9 @@ class logging_log_metric_filter_and_alert_for_custom_role_changes_enabled(Check)
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -44,8 +48,12 @@ class logging_log_metric_filter_and_alert_for_custom_role_changes_enabled(Check)
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled.py
index 8c8927ec32..b7bc619ea4 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled/logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = '(protoPayload.serviceName="cloudresourcemanager.googleapis.com") AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="REMOVE" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner") OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="ADD" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner")'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- '(protoPayload.serviceName="cloudresourcemanager.googleapis.com") AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="REMOVE" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner") OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="ADD" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner")'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
metric_name = getattr(metric, "name", None) or "unknown"
report = Check_Report_GCP(
metadata=self.metadata(),
@@ -36,6 +37,9 @@ class logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled(
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
project_obj = logging_client.projects.get(project)
@@ -47,8 +51,12 @@ class logging_log_metric_filter_and_alert_for_project_ownership_changes_enabled(
location=logging_client.region,
resource_name=(getattr(project_obj, "name", None) or "GCP Project"),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled.py
index 3e499db10a..3c03ab0fde 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled/logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -10,9 +13,10 @@ class logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes
):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'protoPayload.methodName="cloudsql.instances.update"'
projects_with_metric = set()
for metric in logging_client.metrics:
- if 'protoPayload.methodName="cloudsql.instances.update"' in metric.filter:
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -30,6 +34,9 @@ class logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -43,8 +50,12 @@ class logging_log_metric_filter_and_alert_for_sql_instance_configuration_changes
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled.py
index e2b7cdcc13..0e05838f05 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'resource.type="gce_firewall_rule" AND (protoPayload.methodName:"compute.firewalls.patch" OR protoPayload.methodName:"compute.firewalls.insert" OR protoPayload.methodName:"compute.firewalls.delete")'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'resource.type="gce_firewall_rule" AND (protoPayload.methodName:"compute.firewalls.patch" OR protoPayload.methodName:"compute.firewalls.insert" OR protoPayload.methodName:"compute.firewalls.delete")'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -31,6 +32,9 @@ class logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled(
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -44,8 +48,12 @@ class logging_log_metric_filter_and_alert_for_vpc_firewall_rule_changes_enabled(
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled.py
index c8b15ce1ee..1330ad7a9a 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'resource.type="gce_network" AND (protoPayload.methodName:"compute.networks.insert" OR protoPayload.methodName:"compute.networks.patch" OR protoPayload.methodName:"compute.networks.delete" OR protoPayload.methodName:"compute.networks.removePeering" OR protoPayload.methodName:"compute.networks.addPeering")'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'resource.type="gce_network" AND (protoPayload.methodName:"compute.networks.insert" OR protoPayload.methodName:"compute.networks.patch" OR protoPayload.methodName:"compute.networks.delete" OR protoPayload.methodName:"compute.networks.removePeering" OR protoPayload.methodName:"compute.networks.addPeering")'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -31,6 +32,9 @@ class logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled(Check)
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -44,8 +48,12 @@ class logging_log_metric_filter_and_alert_for_vpc_network_changes_enabled(Check)
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled.py b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled.py
index f840d75852..27f25879e8 100644
--- a/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled.py
+++ b/prowler/providers/gcp/services/logging/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled/logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled.py
@@ -1,5 +1,8 @@
from prowler.lib.check.models import Check, Check_Report_GCP
from prowler.providers.gcp.services.logging.logging_client import logging_client
+from prowler.providers.gcp.services.logging.logging_service import (
+ get_projects_covered_by_aggregated_metric,
+)
from prowler.providers.gcp.services.monitoring.monitoring_client import (
monitoring_client,
)
@@ -8,12 +11,10 @@ from prowler.providers.gcp.services.monitoring.monitoring_client import (
class logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+ metric_filter = 'resource.type="gce_route" AND (protoPayload.methodName:"compute.routes.delete" OR protoPayload.methodName:"compute.routes.insert")'
projects_with_metric = set()
for metric in logging_client.metrics:
- if (
- 'resource.type="gce_route" AND (protoPayload.methodName:"compute.routes.delete" OR protoPayload.methodName:"compute.routes.insert")'
- in metric.filter
- ):
+ if metric_filter in metric.filter:
report = Check_Report_GCP(
metadata=self.metadata(),
resource=metric,
@@ -31,6 +32,9 @@ class logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled(
break
findings.append(report)
+ centrally_covered = get_projects_covered_by_aggregated_metric(
+ logging_client, monitoring_client, metric_filter
+ )
for project in logging_client.project_ids:
if project not in projects_with_metric:
report = Check_Report_GCP(
@@ -44,8 +48,12 @@ class logging_log_metric_filter_and_alert_for_vpc_network_route_changes_enabled(
else "GCP Project"
),
)
- report.status = "FAIL"
- report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
+ if project in centrally_covered:
+ report.status = "PASS"
+ report.status_extended = f"Log metric filter {centrally_covered[project]} found with an alert, covering project {project} via an organization-level aggregated sink."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"There are no log metric filters or alerts associated in project {project}."
findings.append(report)
return findings
diff --git a/prowler/providers/gcp/services/logging/logging_service.py b/prowler/providers/gcp/services/logging/logging_service.py
index 637c8782b2..7d8843584e 100644
--- a/prowler/providers/gcp/services/logging/logging_service.py
+++ b/prowler/providers/gcp/services/logging/logging_service.py
@@ -1,9 +1,12 @@
+import re
+
from pydantic.v1 import BaseModel
from prowler.lib.logger import logger
from prowler.providers.gcp.config import DEFAULT_RETRY_ATTEMPTS
from prowler.providers.gcp.gcp_provider import GcpProvider
from prowler.providers.gcp.lib.service.service import GCPService
+from prowler.providers.gcp.services.monitoring.monitoring_service import Monitoring
class Logging(GCPService):
@@ -12,6 +15,7 @@ class Logging(GCPService):
self.sinks = []
self.metrics = []
self._get_sinks()
+ self._get_org_sinks()
self._get_metrics()
def _get_sinks(self):
@@ -39,6 +43,38 @@ class Logging(GCPService):
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ def _get_org_sinks(self):
+ """Fetch org-level sinks with includeChildren so child projects are not falsely failed."""
+ org_ids = set()
+ for project in self.projects.values():
+ if project.organization:
+ org_ids.add(project.organization.id)
+
+ for org_id in org_ids:
+ try:
+ request = self.client.sinks().list(parent=f"organizations/{org_id}")
+ while request is not None:
+ response = request.execute(num_retries=DEFAULT_RETRY_ATTEMPTS)
+
+ for sink in response.get("sinks", []):
+ self.sinks.append(
+ Sink(
+ name=sink["name"],
+ destination=sink["destination"],
+ filter=sink.get("filter", "all"),
+ project_id=f"organizations/{org_id}",
+ include_children=sink.get("includeChildren", False),
+ )
+ )
+
+ request = self.client.sinks().list_next(
+ previous_request=request, previous_response=response
+ )
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
def _get_metrics(self):
for project_id in self.project_ids:
try:
@@ -57,6 +93,7 @@ class Logging(GCPService):
type=metric["metricDescriptor"]["type"],
filter=metric["filter"],
project_id=project_id,
+ bucket_name=metric.get("bucketName", ""),
)
)
@@ -76,6 +113,7 @@ class Sink(BaseModel):
destination: str
filter: str
project_id: str
+ include_children: bool = False
class Metric(BaseModel):
@@ -83,3 +121,140 @@ class Metric(BaseModel):
type: str
filter: str
project_id: str
+ bucket_name: str = ""
+
+
+# A positive selector of the Admin Activity stream: a ``logName`` predicate
+# (``:`` has-substring or ``=`` equals) or a ``log_id()`` call. Written verbose
+# so each fragment stays legible; ``(?![a-z_])`` keeps a longer stream name
+# (``.../activity_v2``) from impersonating Admin Activity.
+_ACTIVITY_SELECTOR = re.compile(
+ r"""
+ (?: logName \s* [:=] \s* | log_id \s* \( \s* ) # logName: / logName= / log_id(
+ ["']? [^"'\s)]* # optional quote, then path prefix
+ cloudaudit\.googleapis\.com/activity (?![a-z_]) # the Admin Activity stream itself
+ """,
+ re.IGNORECASE | re.VERBOSE,
+)
+
+# The same selector for *any* Cloud Audit stream (activity, data_access,
+# system_event, policy, access_transparency, …). Used to strip the OR-combined
+# audit clauses so we can prove nothing restrictive is left over.
+_CLOUDAUDIT_SELECTOR = re.compile(
+ r"""
+ (?: logName \s* [:=] \s* | log_id \s* \( \s* ) # logName: / logName= / log_id(
+ ["']? [^"'\s)]* # optional quote, then path prefix
+ cloudaudit\.googleapis\.com/[a-z_]+ # any cloudaudit stream
+ ["']? \s* \)? # optional closing quote / paren
+ """,
+ re.IGNORECASE | re.VERBOSE,
+)
+
+# Operators that exclude or narrow coverage. Any of these means we cannot prove
+# the sink delivers the *whole* Admin Activity stream, so it is not credited.
+_NEGATION_OR_RESTRICTION = re.compile(
+ r"""
+ \bNOT\b # NOT exclusion
+ | \bAND\b # AND conjunction (restriction)
+ | != | !: # "!=" / "!:" inequality
+ | (?:^|[\s(]) -\s* [A-Za-z_] # leading "-" exclusion operator
+ """,
+ re.IGNORECASE | re.VERBOSE,
+)
+
+
+def _sink_delivers_activity_logs(sink_filter: str) -> bool:
+ """True only when a sink's filter *provably* exports the full Admin Activity
+ audit stream (or everything).
+
+ Crediting flips a child project to PASS on a CIS security control, so the
+ match is deliberately conservative: a false FAIL is safe, a false PASS is
+ not. A non-``"all"`` filter is credited only when
+
+ 1. it positively selects the Admin Activity stream
+ (``logName:.../activity``, ``logName="...activity"`` or
+ ``log_id("...activity")``);
+ 2. it carries no operator that excludes or narrows the stream — ``NOT`` /
+ ``-`` / ``!=`` (negation) or ``AND`` (restriction); and
+ 3. nothing but ``OR``-combined Cloud Audit selectors remains once those are
+ stripped — an ``OR`` only widens coverage, but any leftover predicate
+ (``severity>=ERROR``, ``resource.type=...``) could narrow it.
+
+ Sink filters encode the stream URL-encoded (``...%2Factivity``) or as a path
+ — normalize before matching.
+ """
+ if not sink_filter or sink_filter.strip().lower() == "all":
+ return True
+ normalized = sink_filter.replace("%2F", "/").replace("%2f", "/")
+ # 1. The Admin Activity stream must be positively selected.
+ if not _ACTIVITY_SELECTOR.search(normalized):
+ return False
+ # 2. No operator may exclude or narrow that coverage.
+ if _NEGATION_OR_RESTRICTION.search(normalized):
+ return False
+ # 3. Only OR-combined audit selectors may remain — strip them and the OR
+ # glue; anything left is a predicate we cannot prove is full-coverage.
+ remainder = _CLOUDAUDIT_SELECTOR.sub(" ", normalized)
+ remainder = re.sub(r"\bOR\b|[()\s]", " ", remainder, flags=re.IGNORECASE)
+ return remainder.strip() == ""
+
+
+def get_projects_covered_by_aggregated_metric(
+ logging_client: Logging,
+ monitoring_client: Monitoring,
+ metric_filter: str,
+) -> dict[str, str]:
+ """Return {project_id: metric_name} for scanned projects whose logs are routed,
+ via an organization-level sink with includeChildren=True, to a bucket that holds
+ a bucket-scoped log metric matching ``metric_filter`` that has an alert policy.
+
+ The CIS GCP logging-metric checks are written per-project, but a common (and
+ recommended) topology centralizes monitoring: an org-level aggregated sink ships
+ every child project's logs into one bucket, where a single bucket-scoped metric
+ + alert covers them all. Without crediting that, those child projects are falsely
+ failed. Mirrors the org-sink handling already in ``logging_sink_created`` (#11355).
+
+ A sink is credited when it exports everything (``filter == "all"``) or when its
+ filter carries the Admin Activity audit stream — the only stream the CIS metric
+ filters can match (see ``_sink_delivers_activity_logs``).
+ """
+ # Buckets that hold a matching, alerted, bucket-scoped metric -> metric name.
+ bucket_to_metric = {}
+ for metric in logging_client.metrics:
+ if not getattr(metric, "bucket_name", ""):
+ continue
+ if metric_filter not in metric.filter:
+ continue
+ if any(
+ metric.name in policy_filter
+ for alert_policy in monitoring_client.alert_policies
+ for policy_filter in alert_policy.filters
+ ):
+ bucket_to_metric[metric.bucket_name] = metric.name
+ if not bucket_to_metric:
+ return {}
+
+ # Org resources whose includeChildren sink targets one of those buckets.
+ org_to_metric = {}
+ for sink in logging_client.sinks:
+ if not getattr(sink, "include_children", False):
+ continue
+ if not _sink_delivers_activity_logs(getattr(sink, "filter", "all")):
+ continue
+ for bucket, metric_name in bucket_to_metric.items():
+ # sink.destination e.g. "logging.googleapis.com/projects/.../buckets/X";
+ # metric.bucket_name e.g. "projects/.../buckets/X".
+ if sink.destination.endswith(bucket):
+ org_to_metric[sink.project_id] = metric_name
+ break
+ if not org_to_metric:
+ return {}
+
+ # Scanned projects sitting under a covering organization.
+ covered = {}
+ for project_id in logging_client.project_ids:
+ project = logging_client.projects.get(project_id)
+ organization = getattr(project, "organization", None) if project else None
+ if organization and f"organizations/{organization.id}" in org_to_metric:
+ covered[project_id] = org_to_metric[f"organizations/{organization.id}"]
+ return covered
diff --git a/prowler/providers/gcp/services/logging/logging_sink_created/logging_sink_created.py b/prowler/providers/gcp/services/logging/logging_sink_created/logging_sink_created.py
index 30104a050d..a7846e3dd8 100644
--- a/prowler/providers/gcp/services/logging/logging_sink_created/logging_sink_created.py
+++ b/prowler/providers/gcp/services/logging/logging_sink_created/logging_sink_created.py
@@ -5,26 +5,30 @@ from prowler.providers.gcp.services.logging.logging_client import logging_client
class logging_sink_created(Check):
def execute(self) -> Check_Report_GCP:
findings = []
+
+ # Map project_id -> sink for direct project-level sinks
projects_with_logging_sink = {}
for sink in logging_client.sinks:
- if sink.filter == "all":
+ if sink.filter == "all" and not sink.include_children:
projects_with_logging_sink[sink.project_id] = sink
+ # Collect org resource names that have a covering sink (includeChildren=True)
+ covering_org_sinks = {}
+ for sink in logging_client.sinks:
+ if sink.filter == "all" and sink.include_children:
+ covering_org_sinks[sink.project_id] = sink
+
for project in logging_client.project_ids:
- if project not in projects_with_logging_sink.keys():
- project_obj = logging_client.projects.get(project)
- report = Check_Report_GCP(
- metadata=self.metadata(),
- resource=project_obj,
- resource_id=project,
- project_id=project,
- location=logging_client.region,
- resource_name=(getattr(project_obj, "name", None) or "GCP Project"),
- )
- report.status = "FAIL"
- report.status_extended = f"There are no logging sinks to export copies of all the log entries in project {project}."
- findings.append(report)
- else:
+ project_obj = logging_client.projects.get(project)
+
+ # Determine whether this project is covered by an org-level sink
+ org = getattr(project_obj, "organization", None) if project_obj else None
+ org_resource = f"organizations/{org.id}" if org else None
+ covering_sink = (
+ covering_org_sinks.get(org_resource) if org_resource else None
+ )
+
+ if project in projects_with_logging_sink:
sink = projects_with_logging_sink[project]
sink_name = getattr(sink, "name", None) or "unknown"
report = Check_Report_GCP(
@@ -40,4 +44,31 @@ class logging_sink_created(Check):
report.status = "PASS"
report.status_extended = f"Sink {sink_name} is enabled exporting copies of all the log entries in project {project}."
findings.append(report)
+ elif covering_sink:
+ sink_name = getattr(covering_sink, "name", None) or "unknown"
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=covering_sink,
+ resource_id=sink_name,
+ project_id=project,
+ location=logging_client.region,
+ resource_name=(
+ sink_name if sink_name != "unknown" else "Logging Sink"
+ ),
+ )
+ report.status = "PASS"
+ report.status_extended = f"Sink {sink_name} at organization level is exporting copies of all the log entries in project {project}."
+ findings.append(report)
+ else:
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=project_obj,
+ resource_id=project,
+ project_id=project,
+ location=logging_client.region,
+ resource_name=(getattr(project_obj, "name", None) or "GCP Project"),
+ )
+ report.status = "FAIL"
+ report.status_extended = f"There are no logging sinks to export copies of all the log entries in project {project}."
+ findings.append(report)
return findings
diff --git a/tests/providers/oraclecloud/services/database/__init__.py b/prowler/providers/gcp/services/secretmanager/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/database/__init__.py
rename to prowler/providers/gcp/services/secretmanager/__init__.py
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_client.py b/prowler/providers/gcp/services/secretmanager/secretmanager_client.py
new file mode 100644
index 0000000000..dc18866cb3
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.gcp.services.secretmanager.secretmanager_service import (
+ SecretManager,
+)
+
+secretmanager_client = SecretManager(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/database/database_autonomous_database_access_restricted/__init__.py b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/database/database_autonomous_database_access_restricted/__init__.py
rename to prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/__init__.py
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.metadata.json b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.metadata.json
new file mode 100644
index 0000000000..9f1f4d3381
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "gcp",
+ "CheckID": "secretmanager_secret_not_publicly_accessible",
+ "CheckTitle": "Secret Manager secret is not publicly accessible",
+ "CheckType": [],
+ "ServiceName": "secretmanager",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "critical",
+ "ResourceType": "secretmanager.googleapis.com/Secret",
+ "Description": "Secret Manager secrets deny access to `allUsers` and `allAuthenticatedUsers`, so only **explicitly authorized identities** can read or use them.\n\nThe evaluation reviews each secret's IAM policy bindings to confirm no public principals are granted access.",
+ "Risk": "Granting public IAM access to a secret exposes credentials, API keys, certificates, or other sensitive values to any caller on the internet or any authenticated Google account. This compromises **confidentiality**, enables **lateral movement** with leaked credentials, and can trigger regulatory breaches under PCI-DSS, ISO 27001, and GDPR.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://cloud.google.com/secret-manager/docs/access-control",
+ "https://cloud.google.com/iam/docs/overview"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud secrets remove-iam-policy-binding <SECRET_NAME> --member=<allUsers|allAuthenticatedUsers> --role=roles/secretmanager.secretAccessor",
+ "NativeIaC": "",
+ "Other": "1. In Google Cloud Console, go to Security > Secret Manager\n2. Select the secret and open the Permissions tab\n3. Remove any binding with allUsers or allAuthenticatedUsers\n4. Grant access only to required service accounts or groups",
+ "Terraform": "```hcl\nresource \"google_secret_manager_secret_iam_binding\" \"<example_resource_name>\" {\n secret_id = \"<example_resource_id>\"\n role = \"roles/secretmanager.secretAccessor\"\n members = [\"serviceAccount:<example_resource_id>\"] # Critical: never include allUsers or allAuthenticatedUsers\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Apply **least privilege** to Secret Manager: grant `roles/secretmanager.secretAccessor` only to the specific service accounts or groups that need to read each secret.\n\nUse **workload identity** for GKE workloads and rotate credentials regularly to limit blast radius when a binding is misconfigured.",
+ "Url": "https://hub.prowler.com/check/secretmanager_secret_not_publicly_accessible"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "secretmanager_secret_rotation_enabled",
+ "kms_key_not_publicly_accessible",
+ "cloudstorage_bucket_public_access"
+ ],
+ "Notes": "This check evaluates the secret-level IAM policy. Project-level IAM policies that may indirectly grant public access are not evaluated by this check."
+}
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.py b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.py
new file mode 100644
index 0000000000..fb52a119fa
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_not_publicly_accessible/secretmanager_secret_not_publicly_accessible.py
@@ -0,0 +1,41 @@
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.secretmanager.secretmanager_client import (
+ secretmanager_client,
+)
+
+
+class secretmanager_secret_not_publicly_accessible(Check):
+ """Check that Secret Manager secrets do not grant access to all users.
+
+ Verifies that no Secret Manager secret has an IAM binding granting access
+ to `allUsers` or `allAuthenticatedUsers`.
+ """
+
+ def execute(self) -> list[Check_Report_GCP]:
+ """Execute the public-access check across all Secret Manager secrets.
+
+ Returns:
+ A list of `Check_Report_GCP` findings, one per secret. Status is
+ `FAIL` when the secret is accessible to `allUsers` or
+ `allAuthenticatedUsers` and `PASS` otherwise.
+ """
+ findings = []
+ for secret in secretmanager_client.secrets:
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=secret,
+ resource_id=secret.name,
+ )
+ if secret.publicly_accessible:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Secret {secret.name} is publicly accessible "
+ f"(allUsers or allAuthenticatedUsers IAM binding detected)."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Secret {secret.name} is not publicly accessible."
+ )
+ findings.append(report)
+ return findings
diff --git a/tests/providers/oraclecloud/services/events/__init__.py b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/__init__.py
rename to prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/__init__.py
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.metadata.json b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.metadata.json
new file mode 100644
index 0000000000..09dd158b49
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "gcp",
+ "CheckID": "secretmanager_secret_rotation_enabled",
+ "CheckTitle": "Secret Manager secret is rotated every 90 days or less",
+ "CheckType": [],
+ "ServiceName": "secretmanager",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "secretmanager.googleapis.com/Secret",
+ "Description": "Secret Manager secrets have **automatic rotation** configured with a rotation period of `90` days or less and the next scheduled rotation has not been missed.\n\nThe evaluation reviews each secret's `rotation` settings to confirm both the period and the upcoming rotation time are within bounds.",
+ "Risk": "Without timely rotation, a leaked or compromised secret remains valid indefinitely, eroding **confidentiality** and widening the **blast radius** of any credential exposure. Stale secrets also bypass periodic re-authorization controls expected by frameworks such as PCI-DSS and ISO 27001.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://cloud.google.com/secret-manager/docs/rotation-recommendations",
+ "https://cloud.google.com/secret-manager/docs/reference/rest/v1/projects.secrets"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "gcloud secrets update <SECRET_NAME> --rotation-period=7776000s --next-rotation-time=<RFC3339_TIMESTAMP>",
+ "NativeIaC": "",
+ "Other": "1. In Google Cloud Console, go to Security > Secret Manager\n2. Select the secret and click Edit secret\n3. Under Rotation, enable Automatic rotation with a period of 90 days or less\n4. Configure a Pub/Sub topic to receive rotation notifications\n5. Click Save",
+ "Terraform": "```hcl\nresource \"google_secret_manager_secret\" \"<example_resource_name>\" {\n secret_id = \"<example_resource_id>\"\n\n replication {\n auto {}\n }\n\n rotation {\n rotation_period = \"7776000s\" # Critical: enables rotation within 90 days\n next_rotation_time = \"<RFC3339_TIMESTAMP>\"\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Enable **automatic rotation** for every Secret Manager secret with a period of `90` days or less.\n\nWire **Pub/Sub notifications** to trigger rotation logic and apply **defense in depth** by versioning each secret update so consumers can roll back without losing availability.",
+ "Url": "https://hub.prowler.com/check/secretmanager_secret_rotation_enabled"
+ }
+ },
+ "Categories": [
+ "secrets"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "secretmanager_secret_not_publicly_accessible",
+ "kms_key_rotation_enabled",
+ "iam_sa_user_managed_key_rotate_90_days"
+ ],
+ "Notes": "A secret without a rotationPeriod field has no automatic rotation configured and will be marked as FAIL. Rotation periods exceeding 90 days are also marked as FAIL."
+}
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.py b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.py
new file mode 100644
index 0000000000..84d53e7f3a
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_secret_rotation_enabled/secretmanager_secret_rotation_enabled.py
@@ -0,0 +1,83 @@
+import datetime
+
+from prowler.lib.check.models import Check, Check_Report_GCP
+from prowler.providers.gcp.services.secretmanager.secretmanager_client import (
+ secretmanager_client,
+)
+
+
+class secretmanager_secret_rotation_enabled(Check):
+ """
+ Ensure Secret Manager secrets have automatic rotation configured within the max rotation period.
+
+ - PASS: Secret has a rotation period within the maximum (default 90 days) and the next rotation is not overdue.
+ - FAIL: Secret has no rotation, the period exceeds the maximum, or the next rotation has been missed.
+ """
+
+ def execute(self) -> list[Check_Report_GCP]:
+ """Evaluate every Secret Manager secret's rotation configuration against the maximum rotation period."""
+ findings = []
+
+ max_rotation_days = int(
+ getattr(secretmanager_client, "audit_config", {}).get(
+ "secretmanager_max_rotation_days", 90
+ )
+ )
+
+ for secret in secretmanager_client.secrets:
+ report = Check_Report_GCP(
+ metadata=self.metadata(),
+ resource=secret,
+ resource_id=secret.name,
+ )
+
+ rotation_seconds = None
+ if secret.rotation_period:
+ try:
+ rotation_seconds = float(secret.rotation_period[:-1])
+ except (ValueError, IndexError):
+ rotation_seconds = None
+
+ rotation_overdue = False
+ if rotation_seconds is not None and secret.next_rotation_time:
+ try:
+ parsed = secret.next_rotation_time.replace("Z", "+00:00")
+ next_rotation_time = datetime.datetime.fromisoformat(parsed)
+ rotation_overdue = next_rotation_time < datetime.datetime.now(
+ datetime.timezone.utc
+ )
+ except (ValueError, AttributeError):
+ rotation_overdue = True
+
+ max_rotation_seconds = max_rotation_days * 86400
+ rotation_days = (
+ int(rotation_seconds // 86400) if rotation_seconds is not None else None
+ )
+
+ if rotation_seconds is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Secret {secret.name} does not have automatic rotation enabled."
+ )
+ elif rotation_seconds > max_rotation_seconds:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Secret {secret.name} has rotation enabled but the period "
+ f"({rotation_days} days) exceeds the {max_rotation_days}-day maximum."
+ )
+ elif rotation_overdue:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Secret {secret.name} has rotation configured "
+ f"({rotation_days} days) but the scheduled rotation is overdue."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Secret {secret.name} has automatic rotation enabled "
+ f"with a period of {rotation_days} days."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/gcp/services/secretmanager/secretmanager_service.py b/prowler/providers/gcp/services/secretmanager/secretmanager_service.py
new file mode 100644
index 0000000000..ca01663083
--- /dev/null
+++ b/prowler/providers/gcp/services/secretmanager/secretmanager_service.py
@@ -0,0 +1,94 @@
+from typing import Optional
+
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.gcp.config import DEFAULT_RETRY_ATTEMPTS
+from prowler.providers.gcp.gcp_provider import GcpProvider
+from prowler.providers.gcp.lib.service.service import GCPService
+
+
+class SecretManager(GCPService):
+ """Secret Manager service client.
+
+ Enumerates Secret Manager secrets across every accessible project using
+ the `secretmanager.googleapis.com` v1 API and exposes them through the
+ `secrets` attribute.
+ """
+
+ def __init__(self, provider: GcpProvider) -> None:
+ """Initialize the service and preload secrets with their IAM policies."""
+ super().__init__("secretmanager", provider)
+ self.secrets = []
+ self._get_secrets()
+ self._get_secrets_iam_policy()
+
+ def _get_secrets(self) -> None:
+ """Fetch Secret Manager secrets for every project."""
+ for project_id in self.project_ids:
+ try:
+ request = (
+ self.client.projects()
+ .secrets()
+ .list(parent=f"projects/{project_id}")
+ )
+ while request is not None:
+ response = request.execute(num_retries=DEFAULT_RETRY_ATTEMPTS)
+ for secret in response.get("secrets", []):
+ rotation = secret.get("rotation") or {}
+ self.secrets.append(
+ Secret(
+ id=secret["name"],
+ name=secret["name"].split("/")[-1],
+ project_id=project_id,
+ rotation_period=rotation.get("rotationPeriod"),
+ next_rotation_time=rotation.get("nextRotationTime"),
+ )
+ )
+ request = (
+ self.client.projects()
+ .secrets()
+ .list_next(previous_request=request, previous_response=response)
+ )
+ except Exception as error:
+ logger.error(
+ f"{project_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def _get_secrets_iam_policy(self) -> None:
+ """Fetch IAM policy for every Secret Manager secret in parallel."""
+ self.__threading_call__(self._get_secret_iam_policy, self.secrets)
+
+ def _get_secret_iam_policy(self, secret: "Secret") -> None:
+ """Mark a secret as publicly accessible when bound to `allUsers` or `allAuthenticatedUsers`."""
+ try:
+ response = (
+ self.client.projects()
+ .secrets()
+ .getIamPolicy(resource=secret.id)
+ .execute(
+ http=self.__get_AuthorizedHttp_client__(),
+ num_retries=DEFAULT_RETRY_ATTEMPTS,
+ )
+ )
+ for binding in response.get("bindings", []):
+ members = binding.get("members", [])
+ if "allUsers" in members or "allAuthenticatedUsers" in members:
+ secret.publicly_accessible = True
+ break
+ except Exception as error:
+ logger.error(
+ f"{secret.project_id} -- {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+
+class Secret(BaseModel):
+ """Secret Manager secret resource consumed by GCP checks."""
+
+ id: str
+ name: str
+ project_id: str
+ location: str = "global"
+ rotation_period: Optional[str] = None
+ next_rotation_time: Optional[str] = None
+ publicly_accessible: bool = False
diff --git a/prowler/providers/github/github_provider.py b/prowler/providers/github/github_provider.py
index 0f6e7f59ea..d832a93f98 100644
--- a/prowler/providers/github/github_provider.py
+++ b/prowler/providers/github/github_provider.py
@@ -91,6 +91,7 @@ class GithubProvider(Provider):
"""
_type: str = "github"
+ sdk_only: bool = False
_auth_method: str = None
MAX_REPO_LIST_LINES: int = 10_000
MAX_REPO_NAME_LENGTH: int = 500
diff --git a/prowler/providers/github/services/repository/repository_default_branch_deletion_disabled/repository_default_branch_deletion_disabled.py b/prowler/providers/github/services/repository/repository_default_branch_deletion_disabled/repository_default_branch_deletion_disabled.py
index bf615a21b6..1f05035723 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_deletion_disabled/repository_default_branch_deletion_disabled.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_deletion_disabled/repository_default_branch_deletion_disabled.py
@@ -28,6 +28,8 @@ class repository_default_branch_deletion_disabled(Check):
report.status_extended = (
f"Repository {repo.name} does allow default branch deletion."
)
+ if repo.default_branch.branch_deletion_source == "ruleset_not_active":
+ report.status_extended = f"Repository {repo.name} has default branch deletion disabled in a ruleset, but the ruleset is not active."
if not repo.default_branch.branch_deletion:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.metadata.json
index f774f204d0..2ef741d253 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.metadata.json
@@ -9,12 +9,13 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** blocks **force pushes** through branch protection.\n\nEvaluates whether the default branch permits force pushes.",
+ "Description": "**GitHub repository default branch** blocks **force pushes** through branch protection.\n\nEvaluates whether the default branch permits force pushes. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Allowing **force pushes on the default branch** erodes **integrity** and **auditability** by enabling history rewrites and deletion of commits. Attackers or insiders can inject unreviewed code, bypass reviews and status checks, and corrupt PRs, risking supply-chain compromise and reduced **availability**.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#allow-force-pushes"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#allow-force-pushes",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.py b/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.py
index 16eb7fa794..de61256080 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_disallows_force_push/repository_default_branch_disallows_force_push.py
@@ -26,6 +26,11 @@ class repository_default_branch_disallows_force_push(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does allow force pushes on default branch ({repo.default_branch.name})."
+ if (
+ repo.default_branch.allow_force_pushes_source
+ == "ruleset_not_active"
+ ):
+ report.status_extended = f"Repository {repo.name} has force pushes disallowed in a ruleset on default branch ({repo.default_branch.name}), but the ruleset is not active."
if not repo.default_branch.allow_force_pushes:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.metadata.json
index 70668adbc1..75c84dc752 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.metadata.json
@@ -9,12 +9,13 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** applies **branch protection rules** to **administrators** via `enforce_admins`, holding admin pushes to the same requirements as other contributors (reviews, status checks, and push restrictions).",
+ "Description": "**GitHub repository default branch** applies **branch protection rules** to **administrators** via `enforce_admins`, holding admin pushes to the same requirements as other contributors (reviews, status checks, and push restrictions). This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without admin enforcement, privileged users can bypass reviews and checks, enabling **unauthorized code changes**. A compromised admin token can inject backdoors, alter dependencies, or disable safeguards, undermining **integrity**, exposing secrets (**confidentiality**), and causing outages (**availability**).",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#do-not-allow-bypassing-the-above-settings"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#do-not-allow-bypassing-the-above-settings",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.py b/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.py
index 0a70cf0aea..142f0a5b7b 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_protection_applies_to_admins/repository_default_branch_protection_applies_to_admins.py
@@ -26,6 +26,8 @@ class repository_default_branch_protection_applies_to_admins(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not enforce administrators to be subject to the same branch protection rules as other users."
+ if repo.default_branch.enforce_admins_source == "ruleset_not_active":
+ report.status_extended = f"Repository {repo.name} has a ruleset that would apply to administrators, but the ruleset is not active."
if repo.default_branch.enforce_admins:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.metadata.json
index 8f173e868f..dbefae6179 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.metadata.json
@@ -9,12 +9,13 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** has **branch protection rules** enabled to restrict direct changes and require reviewed, validated merges. The evaluation determines whether the default branch enforces such rules.",
+ "Description": "**GitHub repository default branch** has **branch protection rules** enabled to restrict direct changes and require reviewed, validated merges. The evaluation determines whether the default branch enforces such rules. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without default-branch protection, changes can bypass reviews and checks, enabling:\n- Unauthorized direct pushes/force pushes\n- Malicious code injection and workflow tampering\n- Accidental deletions or unstable releases\nThis undermines code **integrity** and service **availability**.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.py b/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.py
index 1348018ee1..b305f5019a 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_protection_enabled/repository_default_branch_protection_enabled.py
@@ -26,6 +26,8 @@ class repository_default_branch_protection_enabled(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not enforce branch protection on default branch ({repo.default_branch.name})."
+ if repo.default_branch.protected_source == "ruleset_not_active":
+ report.status_extended = f"Repository {repo.name} has a ruleset configured on default branch ({repo.default_branch.name}), but the ruleset is not active."
if repo.default_branch.protected:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.metadata.json
index 465e61aad9..53f849271a 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.metadata.json
@@ -9,12 +9,13 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** requires **Code Owners** approval for pull requests that modify paths declared in `CODEOWNERS`",
+ "Description": "**GitHub repository default branch** requires **Code Owners** approval for pull requests that modify paths declared in `CODEOWNERS`. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without required **Code Owners** review, non-owners can merge changes to sensitive code, undermining **integrity**.\nThis increases the chance of **malicious code injection**, hidden backdoors, or fragile changes that enable **data exfiltration** or cause outages, impacting confidentiality and availability.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-review-from-code-owners",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.py b/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.py
index 4c5b75010a..3b8a749961 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_codeowners_review/repository_default_branch_requires_codeowners_review.py
@@ -30,6 +30,11 @@ class repository_default_branch_requires_codeowners_review(Check):
else:
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not require code owner approval for changes to owned code."
+ if (
+ repo.default_branch.require_code_owner_reviews_source
+ == "ruleset_not_active"
+ ):
+ report.status_extended = f"Repository {repo.name} has code owner approval configured in a ruleset, but the ruleset is not active."
findings.append(report)
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.metadata.json
index beaff24afb..c304ef26c1 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.metadata.json
@@ -9,12 +9,13 @@
"Severity": "medium",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** uses **branch protection** to require **conversation resolution** on pull requests (`Require conversation resolution before merging`).",
+ "Description": "**GitHub repository default branch** uses **branch protection** to require **conversation resolution** on pull requests (`Require conversation resolution before merging`). This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Unresolved threads let code with known concerns reach default, weakening **integrity** and **confidentiality**. Insecure changes or secrets may ship, enabling injection, auth bypass, or data exposure. **Availability** can suffer from regressions; review accountability is reduced.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.py b/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.py
index da33754cf5..9c25f8a14f 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_conversation_resolution/repository_default_branch_requires_conversation_resolution.py
@@ -26,6 +26,11 @@ class repository_default_branch_requires_conversation_resolution(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not require conversation resolution on default branch ({repo.default_branch.name})."
+ if (
+ repo.default_branch.conversation_resolution_source
+ == "ruleset_not_active"
+ ):
+ report.status_extended = f"Repository {repo.name} has conversation resolution configured in a ruleset on default branch ({repo.default_branch.name}), but the ruleset is not active."
if repo.default_branch.conversation_resolution:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.metadata.json
index 215ab496aa..5ecb27ffc6 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.metadata.json
@@ -9,12 +9,13 @@
"Severity": "low",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** enforces `Require linear history`, blocking merge commits and allowing only `squash` or `rebase` merges",
+ "Description": "**GitHub repository default branch** enforces `Require linear history`, blocking merge commits and allowing only `squash` or `rebase` merges. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without a **linear history**, commit provenance is harder to verify, weakening **integrity** and **accountability**.\n\nMerge commits can obscure diffs entering the default branch, hindering audits and rollbacks, enabling unnoticed **malicious or unreviewed code**, and delaying incident response.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-linear-history",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.py b/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.py
index 29a0e51b51..86f944738c 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_linear_history/repository_default_branch_requires_linear_history.py
@@ -26,6 +26,11 @@ class repository_default_branch_requires_linear_history(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not require linear history on default branch ({repo.default_branch.name})."
+ if (
+ repo.default_branch.required_linear_history_source
+ == "ruleset_not_active"
+ ):
+ report.status_extended = f"Repository {repo.name} has linear history configured in a ruleset on default branch ({repo.default_branch.name}), but the ruleset is not active."
if repo.default_branch.required_linear_history:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.metadata.json
index dda4f25ea0..c7f07b1101 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.metadata.json
@@ -9,12 +9,13 @@
"Severity": "medium",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** enforces **required reviews** with a minimum of `2` approving reviews before a pull request can be merged.\n\nAssesses whether an approval threshold of at least `2` is configured for code changes targeting the default branch.",
+ "Description": "**GitHub repository default branch** enforces **required reviews** with a minimum of `2` approving reviews before a pull request can be merged.\n\nAssesses whether an approval threshold of at least `2` is configured for code changes targeting the default branch. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without multi-review approval on the default branch, a single actor can merge changes, degrading **integrity** and **accountability**. This enables:\n- supply-chain tampering or backdoors\n- introduction of exploitable bugs\n- bypass of change control via compromised accounts",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews",
- "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging"
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.py b/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.py
index 6312b98d02..5ddf37e853 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_multiple_approvals/repository_default_branch_requires_multiple_approvals.py
@@ -26,6 +26,8 @@ class repository_default_branch_requires_multiple_approvals(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not enforce at least 2 approvals for code changes."
+ if repo.default_branch.approval_count_source == "ruleset_not_active":
+ report.status_extended = f"Repository {repo.name} has at least 2 approvals configured in a ruleset, but the ruleset is not active."
if repo.default_branch.approval_count >= 2:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.metadata.json
index d3d9c91806..9b045fc4e9 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.metadata.json
@@ -9,12 +9,13 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** enforces **signed and verified commits** (`Require signed commits`), allowing only commits with valid cryptographic signatures to be pushed or merged.",
+ "Description": "**GitHub repository default branch** enforces **signed and verified commits** (`Require signed commits`), allowing only commits with valid cryptographic signatures to be pushed or merged. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without required signing, commit authorship can be spoofed and unverified changes added, impacting integrity.\n- Backdoor injection\n- History tampering and forged identities\n- Release pipeline abuse and supply-chain compromise",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-signed-commits",
- "https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification"
+ "https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.py b/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.py
index 4b6aa3ae4c..110a7d4a1e 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_requires_signed_commits/repository_default_branch_requires_signed_commits.py
@@ -26,6 +26,11 @@ class repository_default_branch_requires_signed_commits(Check):
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
report.status = "FAIL"
report.status_extended = f"Repository {repo.name} does not require signed commits on default branch ({repo.default_branch.name})."
+ if (
+ repo.default_branch.require_signed_commits_source
+ == "ruleset_not_active"
+ ):
+ report.status_extended = f"Repository {repo.name} has signed commits configured in a ruleset on default branch ({repo.default_branch.name}), but the ruleset is not active."
if repo.default_branch.require_signed_commits:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.metadata.json b/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.metadata.json
index 6d450fde33..d0799962ce 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.metadata.json
+++ b/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.metadata.json
@@ -9,13 +9,14 @@
"Severity": "high",
"ResourceType": "NotDefined",
"ResourceGroup": "devops",
- "Description": "**GitHub repository default branch** uses **required status checks**, indicating whether merges are gated by successful check results on pull requests",
+ "Description": "**GitHub repository default branch** uses **required status checks**, indicating whether merges are gated by successful check results on pull requests. This protection can be enforced through classic **branch protection** or repository **rulesets**.",
"Risk": "Without required checks, unvetted commits can be merged, degrading code **integrity** and **availability**. Skipped or failing validations may introduce vulnerable dependencies, break builds, or allow malicious code, enabling supply-chain compromise and rapid propagation to production.",
"RelatedUrl": "",
"AdditionalURLs": [
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule",
"https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging",
- "https://docs.gearset.com/en/articles/2437757-managing-status-check-rules-in-github"
+ "https://docs.gearset.com/en/articles/2437757-managing-status-check-rules-in-github",
+ "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.py b/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.py
index e67b9def2c..f96d5b058d 100644
--- a/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.py
+++ b/prowler/providers/github/services/repository/repository_default_branch_status_checks_required/repository_default_branch_status_checks_required.py
@@ -28,6 +28,8 @@ class repository_default_branch_status_checks_required(Check):
report.status_extended = (
f"Repository {repo.name} does not enforce status checks."
)
+ if repo.default_branch.status_checks_source == "ruleset_not_active":
+ report.status_extended = f"Repository {repo.name} has status checks configured in a ruleset, but the ruleset is not active."
if repo.default_branch.status_checks:
report.status = "PASS"
diff --git a/prowler/providers/github/services/repository/repository_has_codeowners_file/repository_has_codeowners_file.py b/prowler/providers/github/services/repository/repository_has_codeowners_file/repository_has_codeowners_file.py
index 7120e0411a..2ece6abf42 100644
--- a/prowler/providers/github/services/repository/repository_has_codeowners_file/repository_has_codeowners_file.py
+++ b/prowler/providers/github/services/repository/repository_has_codeowners_file/repository_has_codeowners_file.py
@@ -22,6 +22,9 @@ class repository_has_codeowners_file(Check):
"""
findings = []
for repo in repository_client.repositories.values():
+ if repo.archived:
+ continue
+
if repo.codeowners_exists is not None:
report = CheckReportGithub(metadata=self.metadata(), resource=repo)
if repo.codeowners_exists:
diff --git a/prowler/providers/github/services/repository/repository_service.py b/prowler/providers/github/services/repository/repository_service.py
index 0201d199e4..fd8aa28662 100644
--- a/prowler/providers/github/services/repository/repository_service.py
+++ b/prowler/providers/github/services/repository/repository_service.py
@@ -202,15 +202,40 @@ class Repository(GithubService):
return None
- def _get_dismiss_stale_reviews_from_rulesets(
+ def _evaluate_default_branch_rulesets(
self, repo, default_branch: str
- ) -> tuple[Optional[bool], Optional[str]]:
- """Evaluate dismiss-stale-review coverage from repository and parent rulesets."""
- rulesets = self._get_repository_rulesets(repo)
- if rulesets is None:
- return None, None
+ ) -> dict[str, tuple[Optional[int], str]]:
+ """Evaluate default-branch protection coverage provided by rulesets.
- has_inactive_ruleset = False
+ Fetches the repository (and parent) rulesets once and walks every rule that
+ targets the default branch, mapping each ruleset rule to its equivalent classic
+ branch-protection attribute.
+
+ Returns:
+ dict mapping a ``Branch`` attribute name to a ``(value, source)`` tuple where
+ ``source`` is ``"ruleset"`` (enforced by an active ruleset), ``"ruleset_not_active"``
+ (configured by a ruleset that is not active) or absent when no ruleset addresses
+ the attribute. ``value`` is only meaningful for ``approval_count`` (the enforced
+ review count); for boolean attributes it is ``None`` and the caller derives the
+ value from ``source`` and the attribute polarity.
+ """
+ result: dict[str, tuple[Optional[int], str]] = {}
+ rulesets = self._get_repository_rulesets(repo)
+ if not rulesets:
+ return result
+
+ active: set[str] = set()
+ inactive: set[str] = set()
+ active_approval_count: Optional[int] = None
+ inactive_approval_count: Optional[int] = None
+ any_active_ruleset = False
+ any_inactive_ruleset = False
+ # A ruleset with no bypass actors applies to everyone, including administrators
+ # (the rulesets equivalent of "enforce admins"). A ruleset that has bypass actors
+ # would not apply to admins even if activated, so it must not drive the
+ # enforce-admins finding in either the active or the inactive case.
+ admins_enforced_active = False
+ admins_configured_inactive = False
for ruleset in rulesets:
if ruleset.get("target") != "branch":
@@ -219,26 +244,119 @@ class Repository(GithubService):
if not self._ruleset_targets_default_branch(ruleset, default_branch):
continue
+ enforcement = ruleset.get("enforcement")
+ is_active = enforcement in {"active", "enabled"}
+ is_inactive = enforcement in {"disabled", "evaluate"}
+ if not (is_active or is_inactive):
+ continue
+
+ has_no_bypass_actors = not (ruleset.get("bypass_actors") or [])
+ if is_active:
+ any_active_ruleset = True
+ if has_no_bypass_actors:
+ admins_enforced_active = True
+ else:
+ any_inactive_ruleset = True
+ if has_no_bypass_actors:
+ admins_configured_inactive = True
+
+ bucket = active if is_active else inactive
+
for rule in ruleset.get("rules") or []:
- if rule.get("type") != "pull_request":
- continue
+ rule_type = rule.get("type")
+ params = rule.get("parameters") or {}
- dismiss_stale_reviews = (rule.get("parameters") or {}).get(
- "dismiss_stale_reviews_on_push"
- )
- if dismiss_stale_reviews is not True:
- continue
+ if rule_type == "required_linear_history":
+ bucket.add("required_linear_history")
+ elif rule_type == "required_signatures":
+ bucket.add("require_signed_commits")
+ elif rule_type == "required_status_checks":
+ # Only enforced when at least one status check is configured;
+ # an empty list (or just strict policy) requires nothing.
+ if params.get("required_status_checks"):
+ bucket.add("status_checks")
+ elif rule_type == "non_fast_forward":
+ # Presence of the rule disallows force pushes.
+ bucket.add("allow_force_pushes")
+ elif rule_type == "deletion":
+ # Presence of the rule disallows branch deletion.
+ bucket.add("branch_deletion")
+ elif rule_type == "pull_request":
+ bucket.add("require_pull_request")
+ if params.get("require_code_owner_review") is True:
+ bucket.add("require_code_owner_reviews")
+ if params.get("required_review_thread_resolution") is True:
+ bucket.add("conversation_resolution")
+ if params.get("dismiss_stale_reviews_on_push") is True:
+ bucket.add("dismiss_stale_reviews")
+ count = params.get("required_approving_review_count")
+ if isinstance(count, int):
+ if is_active:
+ active_approval_count = max(
+ active_approval_count or 0, count
+ )
+ else:
+ inactive_approval_count = max(
+ inactive_approval_count or 0, count
+ )
- enforcement = ruleset.get("enforcement")
- if enforcement in {"active", "enabled"}:
- return True, "ruleset"
- if enforcement in {"disabled", "evaluate"}:
- has_inactive_ruleset = True
+ for concept in (
+ "required_linear_history",
+ "require_signed_commits",
+ "status_checks",
+ "allow_force_pushes",
+ "branch_deletion",
+ "require_pull_request",
+ "require_code_owner_reviews",
+ "conversation_resolution",
+ "dismiss_stale_reviews",
+ ):
+ if concept in active:
+ result[concept] = (None, "ruleset")
+ elif concept in inactive:
+ result[concept] = (None, "ruleset_not_active")
- if has_inactive_ruleset:
- return False, "ruleset_not_active"
+ if active_approval_count is not None:
+ result["approval_count"] = (active_approval_count, "ruleset")
+ elif inactive_approval_count is not None:
+ result["approval_count"] = (inactive_approval_count, "ruleset_not_active")
- return None, None
+ if any_active_ruleset:
+ result["protected"] = (None, "ruleset")
+ elif any_inactive_ruleset:
+ result["protected"] = (None, "ruleset_not_active")
+
+ if admins_enforced_active:
+ result["enforce_admins"] = (None, "ruleset")
+ elif admins_configured_inactive:
+ result["enforce_admins"] = (None, "ruleset_not_active")
+
+ return result
+
+ @staticmethod
+ def _merge_ruleset_bool(
+ classic_value: Optional[bool], ruleset_source: Optional[str], good: bool = True
+ ) -> tuple[Optional[bool], Optional[str]]:
+ """Merge a boolean branch-protection attribute with its ruleset evaluation.
+
+ Args:
+ classic_value: The value resolved from classic branch protection.
+ ruleset_source: ``"ruleset"``, ``"ruleset_not_active"`` or ``None``.
+ good: The compliant value for the attribute (``True`` for positive attributes,
+ ``False`` for inverted ones such as ``allow_force_pushes``).
+
+ Returns:
+ A ``(value, source)`` tuple. Classic protection wins when it already satisfies
+ the control; otherwise an active ruleset enforces the compliant value, and an
+ inactive ruleset surfaces the non-compliant value with a ``"ruleset_not_active"``
+ source so checks can explain the gap.
+ """
+ classic_pass = classic_value == good
+ if ruleset_source == "ruleset":
+ return good, "ruleset"
+ if ruleset_source == "ruleset_not_active" and not classic_pass:
+ return (not good), "ruleset_not_active"
+ return classic_value, ("classic" if classic_pass else None)
def _list_repositories(self):
"""
@@ -398,6 +516,17 @@ class Repository(GithubService):
conversation_resolution = False
dismiss_stale_reviews = False
dismiss_stale_reviews_source = None
+ protected_source = None
+ require_pull_request_source = None
+ approval_count_source = None
+ required_linear_history_source = None
+ allow_force_pushes_source = None
+ branch_deletion_source = None
+ require_code_owner_reviews_source = None
+ require_signed_commits_source = None
+ status_checks_source = None
+ enforce_admins_source = None
+ conversation_resolution_source = None
try:
branch = repo.get_branch(default_branch)
if branch.protected:
@@ -458,20 +587,98 @@ class Repository(GithubService):
f"{repo.full_name}: {error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
- if dismiss_stale_reviews is not None:
+ # Branch protection enforced through rulesets is equivalent to classic branch
+ # protection, so merge any ruleset coverage before reporting findings to avoid
+ # false positives for repositories that have migrated to rulesets.
+ if branch_protection is not None:
+ ruleset_eval = self._evaluate_default_branch_rulesets(
+ repo, default_branch
+ )
+
+ branch_protection, protected_source = self._merge_ruleset_bool(
+ branch_protection, ruleset_eval.get("protected", (None, None))[1]
+ )
+ require_pr, require_pull_request_source = self._merge_ruleset_bool(
+ require_pr,
+ ruleset_eval.get("require_pull_request", (None, None))[1],
+ )
(
- ruleset_dismiss_stale_reviews,
- ruleset_source,
- ) = self._get_dismiss_stale_reviews_from_rulesets(repo, default_branch)
- if ruleset_dismiss_stale_reviews:
+ required_linear_history,
+ required_linear_history_source,
+ ) = self._merge_ruleset_bool(
+ required_linear_history,
+ ruleset_eval.get("required_linear_history", (None, None))[1],
+ )
+ (
+ require_signed_commits,
+ require_signed_commits_source,
+ ) = self._merge_ruleset_bool(
+ require_signed_commits,
+ ruleset_eval.get("require_signed_commits", (None, None))[1],
+ )
+ status_checks, status_checks_source = self._merge_ruleset_bool(
+ status_checks, ruleset_eval.get("status_checks", (None, None))[1]
+ )
+ (
+ require_code_owner_reviews,
+ require_code_owner_reviews_source,
+ ) = self._merge_ruleset_bool(
+ require_code_owner_reviews,
+ ruleset_eval.get("require_code_owner_reviews", (None, None))[1],
+ )
+ (
+ conversation_resolution,
+ conversation_resolution_source,
+ ) = self._merge_ruleset_bool(
+ conversation_resolution,
+ ruleset_eval.get("conversation_resolution", (None, None))[1],
+ )
+ enforce_admins, enforce_admins_source = self._merge_ruleset_bool(
+ enforce_admins,
+ ruleset_eval.get("enforce_admins", (None, None))[1],
+ )
+ allow_force_pushes, allow_force_pushes_source = (
+ self._merge_ruleset_bool(
+ allow_force_pushes,
+ ruleset_eval.get("allow_force_pushes", (None, None))[1],
+ good=False,
+ )
+ )
+ branch_deletion, branch_deletion_source = self._merge_ruleset_bool(
+ branch_deletion,
+ ruleset_eval.get("branch_deletion", (None, None))[1],
+ good=False,
+ )
+
+ # Dismiss stale reviews keeps its dedicated handling so the classic source
+ # set above (when enabled) is preserved.
+ _, dismiss_source = ruleset_eval.get(
+ "dismiss_stale_reviews", (None, None)
+ )
+ if dismiss_source == "ruleset":
dismiss_stale_reviews = True
dismiss_stale_reviews_source = "ruleset"
elif (
- ruleset_source == "ruleset_not_active" and not dismiss_stale_reviews
+ dismiss_source == "ruleset_not_active" and not dismiss_stale_reviews
):
dismiss_stale_reviews = False
dismiss_stale_reviews_source = "ruleset_not_active"
+ # Approval count takes the strongest requirement between classic and rulesets.
+ approval_value, approval_source = ruleset_eval.get(
+ "approval_count", (None, None)
+ )
+ if approval_source == "ruleset" and approval_value is not None:
+ if approval_value > approval_cnt:
+ approval_cnt = approval_value
+ approval_count_source = "ruleset"
+ elif (
+ approval_source == "ruleset_not_active"
+ and (approval_value or 0) >= 2
+ and approval_cnt < 2
+ ):
+ approval_count_source = "ruleset_not_active"
+
secret_scanning_enabled = False
dependabot_alerts_enabled = False
try:
@@ -517,17 +724,28 @@ class Repository(GithubService):
default_branch=Branch(
name=default_branch,
protected=branch_protection,
+ protected_source=protected_source,
default_branch=True,
require_pull_request=require_pr,
+ require_pull_request_source=require_pull_request_source,
approval_count=approval_cnt,
+ approval_count_source=approval_count_source,
required_linear_history=required_linear_history,
+ required_linear_history_source=required_linear_history_source,
allow_force_pushes=allow_force_pushes,
+ allow_force_pushes_source=allow_force_pushes_source,
branch_deletion=branch_deletion,
+ branch_deletion_source=branch_deletion_source,
status_checks=status_checks,
+ status_checks_source=status_checks_source,
enforce_admins=enforce_admins,
+ enforce_admins_source=enforce_admins_source,
conversation_resolution=conversation_resolution,
+ conversation_resolution_source=conversation_resolution_source,
require_code_owner_reviews=require_code_owner_reviews,
+ require_code_owner_reviews_source=require_code_owner_reviews_source,
require_signed_commits=require_signed_commits,
+ require_signed_commits_source=require_signed_commits_source,
dismiss_stale_reviews=dismiss_stale_reviews,
dismiss_stale_reviews_source=dismiss_stale_reviews_source,
),
@@ -599,17 +817,28 @@ class Branch(BaseModel):
name: str
protected: Optional[bool]
+ protected_source: Optional[str] = None
default_branch: bool
require_pull_request: Optional[bool]
+ require_pull_request_source: Optional[str] = None
approval_count: Optional[int]
+ approval_count_source: Optional[str] = None
required_linear_history: Optional[bool]
+ required_linear_history_source: Optional[str] = None
allow_force_pushes: Optional[bool]
+ allow_force_pushes_source: Optional[str] = None
branch_deletion: Optional[bool]
+ branch_deletion_source: Optional[str] = None
status_checks: Optional[bool]
+ status_checks_source: Optional[str] = None
enforce_admins: Optional[bool]
+ enforce_admins_source: Optional[str] = None
require_code_owner_reviews: Optional[bool]
+ require_code_owner_reviews_source: Optional[str] = None
require_signed_commits: Optional[bool]
+ require_signed_commits_source: Optional[str] = None
conversation_resolution: Optional[bool]
+ conversation_resolution_source: Optional[str] = None
dismiss_stale_reviews: Optional[bool]
dismiss_stale_reviews_source: Optional[str] = None
diff --git a/prowler/providers/googleworkspace/googleworkspace_provider.py b/prowler/providers/googleworkspace/googleworkspace_provider.py
index 4c431aa736..2a40a59ddf 100644
--- a/prowler/providers/googleworkspace/googleworkspace_provider.py
+++ b/prowler/providers/googleworkspace/googleworkspace_provider.py
@@ -54,6 +54,7 @@ class GoogleworkspaceProvider(Provider):
"""
_type: str = "googleworkspace"
+ sdk_only: bool = False
_session: GoogleWorkspaceSession
_identity: GoogleWorkspaceIdentityInfo
_domain_resource: GoogleWorkspaceResource
diff --git a/tests/providers/oraclecloud/services/events/events_notification_topic_and_subscription_exists/__init__.py b/prowler/providers/googleworkspace/services/additionalservices/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_notification_topic_and_subscription_exists/__init__.py
rename to prowler/providers/googleworkspace/services/additionalservices/__init__.py
diff --git a/prowler/providers/googleworkspace/services/additionalservices/additionalservices_client.py b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_client.py
new file mode 100644
index 0000000000..0d256528fa
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.additionalservices.additionalservices_service import (
+ AdditionalServices,
+)
+
+additionalservices_client = AdditionalServices(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/events/events_rule_cloudguard_problems/__init__.py b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_cloudguard_problems/__init__.py
rename to prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/__init__.py
diff --git a/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.metadata.json b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.metadata.json
new file mode 100644
index 0000000000..8dcf6c1f3f
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "additionalservices_external_groups_disabled",
+ "CheckTitle": "Access to external Google Groups is off for everyone",
+ "CheckType": [],
+ "ServiceName": "additionalservices",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "The Additional Google services configuration **disables access to external Google Groups** for all users. This setting controls whether users can access groups created outside the organization from their Google Workspace account.",
+ "Risk": "When external Google Groups access is enabled, users can access and participate in groups created **outside the organization**, potentially exposing them to **phishing, social engineering, or data leakage** through unmanaged external group communications.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/users/advanced/turn-on-or-off-additional-google-services",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace** > **Additional Google services**\n3. Scroll down to **Google Groups**\n4. Set it to **OFF for everyone**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable access to **external Google Groups** for all users. If specific users require access to external groups, enable it by exception for those users or groups only.",
+ "Url": "https://hub.prowler.com/check/additionalservices_external_groups_disabled"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check covers the 'Additional Google services > Google Groups' toggle, which is distinct from the 'Groups for Business' sharing settings covered by the groups service checks."
+}
diff --git a/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.py b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.py
new file mode 100644
index 0000000000..cf61220054
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_external_groups_disabled/additionalservices_external_groups_disabled.py
@@ -0,0 +1,55 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.additionalservices.additionalservices_client import (
+ additionalservices_client,
+)
+
+
+class additionalservices_external_groups_disabled(Check):
+ """Check that access to external Google Groups is disabled for all users.
+
+ This check verifies that the domain-level Additional Google services policy
+ disables external Google Groups access, preventing users from accessing
+ groups created outside the organization.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if additionalservices_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=additionalservices_client.policies,
+ resource_id="additionalServicesPolicies",
+ resource_name="Additional Services Policies",
+ customer_id=additionalservices_client.provider.identity.customer_id,
+ )
+
+ groups_state = additionalservices_client.policies.groups_service_state
+
+ if groups_state == "DISABLED":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Access to external Google Groups is disabled "
+ f"in domain {additionalservices_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if groups_state is None:
+ report.status_extended = (
+ f"Access to external Google Groups is not explicitly configured "
+ f"in domain {additionalservices_client.provider.identity.domain}. "
+ f"The default is ON for everyone. "
+ f"External Google Groups access should be disabled."
+ )
+ else:
+ report.status_extended = (
+ f"Access to external Google Groups is enabled "
+ f"in domain {additionalservices_client.provider.identity.domain}. "
+ f"External Google Groups access should be disabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/additionalservices/additionalservices_service.py b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_service.py
new file mode 100644
index 0000000000..5a41060bc8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/additionalservices/additionalservices_service.py
@@ -0,0 +1,92 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+
+class AdditionalServices(GoogleWorkspaceService):
+ """Google Workspace Additional Services for auditing domain-level service toggles.
+
+ Uses the Cloud Identity Policy API v1 to read the service status of
+ additional Google services configured in the Admin Console, such as
+ the external Google Groups access toggle.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.policies = AdditionalServicesPolicies()
+ self.policies_fetched = False
+ self._fetch_additional_services_policies()
+
+ def _fetch_additional_services_policies(self):
+ """Fetch Additional Services policies from the Cloud Identity Policy API v1."""
+ logger.info("Additional Services - Fetching policies...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ request = service.policies().list(
+ pageSize=100,
+ filter='setting.type.matches("groups.service_status")',
+ )
+ fetch_succeeded = True
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ setting_type = setting.get("type", "").removeprefix("settings/")
+ value = setting.get("value", {})
+
+ if setting_type == "groups.service_status":
+ self.policies.groups_service_state = value.get(
+ "serviceState"
+ )
+ logger.debug(
+ "Additional Services - Groups service state: "
+ f"{self.policies.groups_service_state}"
+ )
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Additional Services policies",
+ self.provider.identity.customer_id,
+ )
+ fetch_succeeded = False
+ break
+
+ self.policies_fetched = fetch_succeeded
+
+ logger.info(
+ f"Additional Services policies fetched - "
+ f"Groups service state: {self.policies.groups_service_state}"
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Additional Services policies",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+
+class AdditionalServicesPolicies(BaseModel):
+ """Model for domain-level Additional Google Services policy settings."""
+
+ # groups.service_status
+ groups_service_state: Optional[str] = None
diff --git a/prowler/providers/googleworkspace/services/calendar/calendar_external_invitations_warning/calendar_external_invitations_warning.metadata.json b/prowler/providers/googleworkspace/services/calendar/calendar_external_invitations_warning/calendar_external_invitations_warning.metadata.json
index 4c7e71c102..3cca0005dd 100644
--- a/prowler/providers/googleworkspace/services/calendar/calendar_external_invitations_warning/calendar_external_invitations_warning.metadata.json
+++ b/prowler/providers/googleworkspace/services/calendar/calendar_external_invitations_warning/calendar_external_invitations_warning.metadata.json
@@ -13,9 +13,8 @@
"Risk": "Without external invitation warnings, users may unintentionally include **external guests** in internal meetings, exposing **confidential meeting details**, agendas, and internal attendee lists to unauthorized parties. This is a common vector for inadvertent data leakage through everyday calendar actions.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/6329284",
- "https://knowledge.workspace.google.com/admin/calendar/set-google-calendar-sharing-options",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/calendar/allow-external-invitations-in-google-calendar-events",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_primary_calendar/calendar_external_sharing_primary_calendar.metadata.json b/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_primary_calendar/calendar_external_sharing_primary_calendar.metadata.json
index 87a82946e5..d923754a9e 100644
--- a/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_primary_calendar/calendar_external_sharing_primary_calendar.metadata.json
+++ b/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_primary_calendar/calendar_external_sharing_primary_calendar.metadata.json
@@ -13,9 +13,8 @@
"Risk": "Overly permissive external sharing of primary calendars exposes **sensitive meeting metadata** — titles, attendees, locations, and descriptions — to users outside the organization. This increases the risk of **information disclosure**, **social engineering**, and **targeted phishing** based on insights into organizational activities.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60765",
"https://knowledge.workspace.google.com/admin/calendar/set-google-calendar-sharing-options",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_secondary_calendar/calendar_external_sharing_secondary_calendar.metadata.json b/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_secondary_calendar/calendar_external_sharing_secondary_calendar.metadata.json
index bd2bbf5be7..d1ac914a0f 100644
--- a/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_secondary_calendar/calendar_external_sharing_secondary_calendar.metadata.json
+++ b/prowler/providers/googleworkspace/services/calendar/calendar_external_sharing_secondary_calendar/calendar_external_sharing_secondary_calendar.metadata.json
@@ -13,9 +13,8 @@
"Risk": "Overly permissive external sharing of secondary calendars exposes **project-specific or team-specific event details** to users outside the organization. Because secondary calendars often hold more targeted activities (e.g., product launches, internal reviews), unrestricted external sharing increases the risk of **information disclosure** and **competitive intelligence leakage**.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60765",
"https://knowledge.workspace.google.com/admin/calendar/set-google-calendar-sharing-options",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_apps_installation_disabled/chat_apps_installation_disabled.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_apps_installation_disabled/chat_apps_installation_disabled.metadata.json
index 54f4d6d852..070de032e1 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_apps_installation_disabled/chat_apps_installation_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_apps_installation_disabled/chat_apps_installation_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Unrestricted Chat app installation allows **unvetted third-party applications** to access user data including conversation content and organizational information. An attacker could distribute a malicious Chat app to **exfiltrate confidential data** or establish **persistent access** to internal communications.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/6089179",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/apps/manage-the-marketplace-app-allowlist-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_external_file_sharing_disabled/chat_external_file_sharing_disabled.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_external_file_sharing_disabled/chat_external_file_sharing_disabled.metadata.json
index c2d8323994..adc1b1fc5f 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_external_file_sharing_disabled/chat_external_file_sharing_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_external_file_sharing_disabled/chat_external_file_sharing_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Enabled external file sharing allows users to send files containing **confidential information** to external parties through Chat. This creates a **data leakage** channel that bypasses DLP controls, particularly dangerous for organizations handling **regulated data** such as PII, PHI, or financial records.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9540647",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/chat/set-up-chat-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_external_messaging_restricted/chat_external_messaging_restricted.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_external_messaging_restricted/chat_external_messaging_restricted.metadata.json
index 0c366d7689..34b0016065 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_external_messaging_restricted/chat_external_messaging_restricted.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_external_messaging_restricted/chat_external_messaging_restricted.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Unrestricted external messaging allows users to communicate freely with **any external party**, increasing the risk of **data exfiltration** through conversation content and **social engineering attacks** from untrusted domains targeting internal users.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9540647",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/chat/set-up-chat-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_external_spaces_restricted/chat_external_spaces_restricted.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_external_spaces_restricted/chat_external_spaces_restricted.metadata.json
index 9f40730d9f..1385f34ef8 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_external_spaces_restricted/chat_external_spaces_restricted.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_external_spaces_restricted/chat_external_spaces_restricted.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Unrestricted external spaces allow users to add **anyone from any domain** to persistent group conversations. This increases the risk of **confidential information exposure** in shared spaces and enables **unauthorized external access** to ongoing organizational discussions.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9540647",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/chat/set-up-chat-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_incoming_webhooks_disabled/chat_incoming_webhooks_disabled.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_incoming_webhooks_disabled/chat_incoming_webhooks_disabled.metadata.json
index 7dec1c83e4..8e8f4b6301 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_incoming_webhooks_disabled/chat_incoming_webhooks_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_incoming_webhooks_disabled/chat_incoming_webhooks_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Exposed webhook URLs allow **unauthorized content injection** into Chat spaces. Attackers can send **fraudulent or misleading messages** that appear to come from trusted services, creating a vector for **social engineering** and **phishing** within internal communications.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/6089179",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/apps/manage-the-marketplace-app-allowlist-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/chat/chat_internal_file_sharing_disabled/chat_internal_file_sharing_disabled.metadata.json b/prowler/providers/googleworkspace/services/chat/chat_internal_file_sharing_disabled/chat_internal_file_sharing_disabled.metadata.json
index af2130d741..b41f662cc3 100644
--- a/prowler/providers/googleworkspace/services/chat/chat_internal_file_sharing_disabled/chat_internal_file_sharing_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/chat/chat_internal_file_sharing_disabled/chat_internal_file_sharing_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Unrestricted internal file sharing in Chat allows files with **sensitive information** to be distributed freely without passing through approved channels. This undermines **data governance** and **audit trail** requirements, making it harder to track data movement within the organization.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9540647",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/chat/set-up-chat-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/directory/directory_super_admin_count/directory_super_admin_count.metadata.json b/prowler/providers/googleworkspace/services/directory/directory_super_admin_count/directory_super_admin_count.metadata.json
index 24165aaade..fcd769cd12 100644
--- a/prowler/providers/googleworkspace/services/directory/directory_super_admin_count/directory_super_admin_count.metadata.json
+++ b/prowler/providers/googleworkspace/services/directory/directory_super_admin_count/directory_super_admin_count.metadata.json
@@ -14,7 +14,7 @@
"RelatedUrl": "",
"AdditionalURLs": [
"https://knowledge.workspace.google.com/admin/users/prebuilt-administrator-roles",
- "https://support.google.com/a/answer/9011373"
+ "https://knowledge.workspace.google.com/admin/users/security-best-practices-for-administrator-accounts"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/directory/directory_super_admin_only_admin_roles/directory_super_admin_only_admin_roles.metadata.json b/prowler/providers/googleworkspace/services/directory/directory_super_admin_only_admin_roles/directory_super_admin_only_admin_roles.metadata.json
index 0264078982..ec531f10c8 100644
--- a/prowler/providers/googleworkspace/services/directory/directory_super_admin_only_admin_roles/directory_super_admin_only_admin_roles.metadata.json
+++ b/prowler/providers/googleworkspace/services/directory/directory_super_admin_only_admin_roles/directory_super_admin_only_admin_roles.metadata.json
@@ -14,7 +14,7 @@
"RelatedUrl": "",
"AdditionalURLs": [
"https://knowledge.workspace.google.com/admin/users/prebuilt-administrator-roles",
- "https://support.google.com/a/answer/9011373"
+ "https://knowledge.workspace.google.com/admin/users/security-best-practices-for-administrator-accounts"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_access_checker_recipients_only/drive_access_checker_recipients_only.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_access_checker_recipients_only/drive_access_checker_recipients_only.metadata.json
index a79283f9c3..8f1c14510a 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_access_checker_recipients_only/drive_access_checker_recipients_only.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_access_checker_recipients_only/drive_access_checker_recipients_only.metadata.json
@@ -13,8 +13,8 @@
"Risk": "If Access Checker suggests broader audiences or public visibility, users may **inadvertently widen access** to a file beyond the people they intended to share with. This is a common cause of unintentional internal or external over-sharing.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_desktop_access_disabled/drive_desktop_access_disabled.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_desktop_access_disabled/drive_desktop_access_disabled.metadata.json
index 43a08b0cab..576f78b19f 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_desktop_access_disabled/drive_desktop_access_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_desktop_access_disabled/drive_desktop_access_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "When Drive for desktop is enabled, organizational files are **synchronized to local devices** and remain accessible if the device is lost, stolen, or compromised. Because Drive for desktop bypasses the central offline-access controls, this channel is a frequently overlooked path for sensitive data to leave organization-managed environments.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7491144",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/set-up-drive-for-desktop-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_external_sharing_warn_users/drive_external_sharing_warn_users.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_external_sharing_warn_users/drive_external_sharing_warn_users.metadata.json
index 8cfd0b4de8..474cadfe20 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_external_sharing_warn_users/drive_external_sharing_warn_users.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_external_sharing_warn_users/drive_external_sharing_warn_users.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without external sharing warnings, users may unintentionally share **sensitive documents** with external recipients who are not entitled to the data. This is a common vector for inadvertent leakage of intellectual property, personally identifiable information, and confidential business data through routine Drive sharing.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_internal_users_distribute_content/drive_internal_users_distribute_content.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_internal_users_distribute_content/drive_internal_users_distribute_content.metadata.json
index 9194d6d19e..df537051ba 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_internal_users_distribute_content/drive_internal_users_distribute_content.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_internal_users_distribute_content/drive_internal_users_distribute_content.metadata.json
@@ -13,8 +13,8 @@
"Risk": "If external users can move files from internal shared drives into shared drives owned by another organization, the organization **loses authoritative control** over its own data. This is a frequently overlooked path for unintentional or malicious data exfiltration through shared drive collaboration.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_publishing_files_disabled/drive_publishing_files_disabled.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_publishing_files_disabled/drive_publishing_files_disabled.metadata.json
index 9968665841..323d7f07a1 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_publishing_files_disabled/drive_publishing_files_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_publishing_files_disabled/drive_publishing_files_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Allowing users to publish Drive files to the web creates a path for **unbounded data exposure**. Sensitive documents, intellectual property, customer data, or internal communications can be made publicly accessible — and indexed by search engines — with a single click, often unintentionally.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_creation_allowed/drive_shared_drive_creation_allowed.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_creation_allowed/drive_shared_drive_creation_allowed.metadata.json
index aba88e28b3..c27742b7ed 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_creation_allowed/drive_shared_drive_creation_allowed.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_creation_allowed/drive_shared_drive_creation_allowed.metadata.json
@@ -13,8 +13,8 @@
"Risk": "When users cannot create shared drives, they store collaborative content in their personal **My Drive** instead. When that user account is deleted, the data is also deleted, leading to **unintentional data loss** of organizationally significant information. Allowing shared drive creation makes data survivable across account lifecycle events.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7212025",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://support.google.com/a/users/answer/7212025",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_disable_download_print_copy/drive_shared_drive_disable_download_print_copy.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_disable_download_print_copy/drive_shared_drive_disable_download_print_copy.metadata.json
index d4bf3300b7..b2a7738925 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_disable_download_print_copy/drive_shared_drive_disable_download_print_copy.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_disable_download_print_copy/drive_shared_drive_disable_download_print_copy.metadata.json
@@ -13,8 +13,8 @@
"Risk": "When viewers and commenters can download, print, or copy shared drive files, they can **bulk-extract sensitive content** — including intellectual property, personally identifiable information, and confidential business documents — using nothing more than read access. This is one of the most direct paths to data exfiltration through Drive.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7662202",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-shared-drives-as-an-admin",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_managers_cannot_override/drive_shared_drive_managers_cannot_override.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_managers_cannot_override/drive_shared_drive_managers_cannot_override.metadata.json
index adc3555dc4..62e46c2ae2 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_managers_cannot_override/drive_shared_drive_managers_cannot_override.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_managers_cannot_override/drive_shared_drive_managers_cannot_override.metadata.json
@@ -13,8 +13,8 @@
"Risk": "If shared drive managers can override organizational defaults, **unauthorized data exposure** can occur when a manager intentionally or accidentally weakens a shared drive's security posture (for example, allowing external members or enabling download for viewers).",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7662202",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-shared-drives-as-an-admin",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_members_only_access/drive_shared_drive_members_only_access.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_members_only_access/drive_shared_drive_members_only_access.metadata.json
index 0949a55040..d9495ea249 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_shared_drive_members_only_access/drive_shared_drive_members_only_access.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_shared_drive_members_only_access/drive_shared_drive_members_only_access.metadata.json
@@ -13,8 +13,8 @@
"Risk": "If non-members can be added to files inside a shared drive, the **drive's membership becomes meaningless** as a security control. Sensitive content scoped to a specific team can be silently extended to users who were never granted access to the drive itself, leading to unintended information disclosure.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7662202",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-shared-drives-as-an-admin",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_sharing_allowlisted_domains/drive_sharing_allowlisted_domains.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_sharing_allowlisted_domains/drive_sharing_allowlisted_domains.metadata.json
index 46caa58bf7..ddba469b0b 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_sharing_allowlisted_domains/drive_sharing_allowlisted_domains.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_sharing_allowlisted_domains/drive_sharing_allowlisted_domains.metadata.json
@@ -13,8 +13,8 @@
"Risk": "When external sharing is unrestricted, users can share organizational content with **any external Google account**, including untrusted or unknown parties. Restricting sharing to allowlisted domains drastically reduces the surface area for accidental and malicious data exfiltration through Drive.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/drive/drive_warn_sharing_with_allowlisted_domains/drive_warn_sharing_with_allowlisted_domains.metadata.json b/prowler/providers/googleworkspace/services/drive/drive_warn_sharing_with_allowlisted_domains/drive_warn_sharing_with_allowlisted_domains.metadata.json
index e41d074a23..c788df1a27 100644
--- a/prowler/providers/googleworkspace/services/drive/drive_warn_sharing_with_allowlisted_domains/drive_warn_sharing_with_allowlisted_domains.metadata.json
+++ b/prowler/providers/googleworkspace/services/drive/drive_warn_sharing_with_allowlisted_domains/drive_warn_sharing_with_allowlisted_domains.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Allowlisted domains are still external. Users may not realize that even an allowlisted recipient is outside the organization, leading to **unintentional disclosure of sensitive content** to legitimate but external collaborators. A warning prompt at share time mitigates that without preventing the sharing itself.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/60781",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_anomalous_attachment_protection_enabled/gmail_anomalous_attachment_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_anomalous_attachment_protection_enabled/gmail_anomalous_attachment_protection_enabled.metadata.json
index 77a1c68b38..2295591dba 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_anomalous_attachment_protection_enabled/gmail_anomalous_attachment_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_anomalous_attachment_protection_enabled/gmail_anomalous_attachment_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against anomalous attachment types, users may receive **emails with unusual file formats** that are designed to bypass standard security filters. Attackers may use **uncommon file extensions or MIME types** to deliver malware that evades signature-based detection.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/set-up-rules-to-detect-harmful-attachments",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_auto_forwarding_disabled/gmail_auto_forwarding_disabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_auto_forwarding_disabled/gmail_auto_forwarding_disabled.metadata.json
index 87d3111130..14484c251c 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_auto_forwarding_disabled/gmail_auto_forwarding_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_auto_forwarding_disabled/gmail_auto_forwarding_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "With auto-forwarding enabled, an attacker who gains control of a user account can create **forwarding rules to exfiltrate** all incoming email to an external address. This can persist undetected and provide the attacker with continuous access to sensitive communications even after the account is recovered.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/2491924",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/let-users-automatically-forward-their-own-gmail-emails",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_comprehensive_mail_storage_enabled/gmail_comprehensive_mail_storage_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_comprehensive_mail_storage_enabled/gmail_comprehensive_mail_storage_enabled.metadata.json
index 157a3da673..530d7af908 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_comprehensive_mail_storage_enabled/gmail_comprehensive_mail_storage_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_comprehensive_mail_storage_enabled/gmail_comprehensive_mail_storage_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without comprehensive mail storage, messages sent through other Google services (Calendar, Drive, etc.) may not be stored in Gmail and therefore **not subject to Vault retention policies**. This creates gaps in **compliance coverage**, **eDiscovery**, and **audit trails** that could violate regulatory requirements.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/3547347",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/set-up-comprehensive-mail-storage",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_domain_spoofing_protection_enabled/gmail_domain_spoofing_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_domain_spoofing_protection_enabled/gmail_domain_spoofing_protection_enabled.metadata.json
index 4ae8bfb3c0..7e6be13d58 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_domain_spoofing_protection_enabled/gmail_domain_spoofing_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_domain_spoofing_protection_enabled/gmail_domain_spoofing_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against domain spoofing based on similar domain names, users may receive **phishing emails from lookalike domains** (e.g., examp1e.com instead of example.com) that appear legitimate. This enables **credential theft, malware delivery, and business email compromise** attacks.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9157861",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_employee_name_spoofing_protection_enabled/gmail_employee_name_spoofing_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_employee_name_spoofing_protection_enabled/gmail_employee_name_spoofing_protection_enabled.metadata.json
index b72137019a..d6d107f360 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_employee_name_spoofing_protection_enabled/gmail_employee_name_spoofing_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_employee_name_spoofing_protection_enabled/gmail_employee_name_spoofing_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against employee name spoofing, users may receive **emails that appear to come from colleagues or executives** but are actually from external attackers. This enables **business email compromise (BEC)**, **wire fraud**, and **social engineering attacks** that exploit trust relationships.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9157861",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_encrypted_attachment_protection_enabled/gmail_encrypted_attachment_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_encrypted_attachment_protection_enabled/gmail_encrypted_attachment_protection_enabled.metadata.json
index 459ce1f539..3367e11777 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_encrypted_attachment_protection_enabled/gmail_encrypted_attachment_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_encrypted_attachment_protection_enabled/gmail_encrypted_attachment_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against encrypted attachments from untrusted senders, users may receive **password-protected archives containing malware** that bypass standard content scanning. Attackers commonly use encrypted attachments to evade detection and deliver **ransomware, trojans, or other malicious payloads**.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/set-up-rules-to-detect-harmful-attachments",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_enhanced_pre_delivery_scanning_enabled/gmail_enhanced_pre_delivery_scanning_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_enhanced_pre_delivery_scanning_enabled/gmail_enhanced_pre_delivery_scanning_enabled.metadata.json
index 69b1be1e4b..0f14ecd73b 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_enhanced_pre_delivery_scanning_enabled/gmail_enhanced_pre_delivery_scanning_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_enhanced_pre_delivery_scanning_enabled/gmail_enhanced_pre_delivery_scanning_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without enhanced pre-delivery scanning, some **sophisticated phishing and malware** messages may pass through standard filters and be delivered to users. The additional scanning layer catches threats that the first-pass filters miss, reducing the organization's exposure to **zero-day phishing campaigns** and **targeted attacks**.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7380368",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/security/help-prevent-phishing-with-pre-delivery-message-scanning",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_external_image_scanning_enabled/gmail_external_image_scanning_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_external_image_scanning_enabled/gmail_external_image_scanning_enabled.metadata.json
index d6a087183c..4df5f8bd84 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_external_image_scanning_enabled/gmail_external_image_scanning_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_external_image_scanning_enabled/gmail_external_image_scanning_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without external image scanning, attackers can use **linked images to track email opens**, deliver **exploit payloads via image rendering vulnerabilities**, or use images as part of sophisticated **phishing schemes** that mimic legitimate communications.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_groups_spoofing_protection_enabled/gmail_groups_spoofing_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_groups_spoofing_protection_enabled/gmail_groups_spoofing_protection_enabled.metadata.json
index 0c3dd64761..c5f5ee61a9 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_groups_spoofing_protection_enabled/gmail_groups_spoofing_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_groups_spoofing_protection_enabled/gmail_groups_spoofing_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection of groups from domain-spoofing emails, attackers can send **spoofed messages to group mailboxes** that appear to originate from the organization. Since groups distribute to many recipients, a single spoofed email can enable **mass phishing, social engineering, or misinformation** campaigns across the organization.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9157861",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_inbound_domain_spoofing_protection_enabled/gmail_inbound_domain_spoofing_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_inbound_domain_spoofing_protection_enabled/gmail_inbound_domain_spoofing_protection_enabled.metadata.json
index 9e285621c8..a049a7ede5 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_inbound_domain_spoofing_protection_enabled/gmail_inbound_domain_spoofing_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_inbound_domain_spoofing_protection_enabled/gmail_inbound_domain_spoofing_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against inbound domain spoofing, users may receive **emails that appear to come from their own organization** but are sent by external attackers. This enables **internal impersonation**, **phishing**, and **business email compromise** attacks that exploit trust in internal communications.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9157861",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_mail_delegation_disabled/gmail_mail_delegation_disabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_mail_delegation_disabled/gmail_mail_delegation_disabled.metadata.json
index a23cf60741..a4f9fd0460 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_mail_delegation_disabled/gmail_mail_delegation_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_mail_delegation_disabled/gmail_mail_delegation_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "If users can delegate access to their mailbox, an attacker who compromises one account could silently delegate access to maintain persistent email surveillance. This also increases the risk of **insider threats** and **data exfiltration** through shared mailbox access.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7223765",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/let-users-delegate-access-to-a-gmail-account",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_per_user_outbound_gateway_disabled/gmail_per_user_outbound_gateway_disabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_per_user_outbound_gateway_disabled/gmail_per_user_outbound_gateway_disabled.metadata.json
index 2f68b3adbc..95cd7567c3 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_per_user_outbound_gateway_disabled/gmail_per_user_outbound_gateway_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_per_user_outbound_gateway_disabled/gmail_per_user_outbound_gateway_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "With per-user outbound gateways enabled, users can route outbound email through **external SMTP servers**, bypassing organizational **email security controls**, **DLP policies**, and **audit logging**. This creates an unmonitored channel for data exfiltration and policy circumvention.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/176652",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/allow-per-user-outbound-gateways",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_pop_imap_access_disabled/gmail_pop_imap_access_disabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_pop_imap_access_disabled/gmail_pop_imap_access_disabled.metadata.json
index 76affe3e47..48f077d8ea 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_pop_imap_access_disabled/gmail_pop_imap_access_disabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_pop_imap_access_disabled/gmail_pop_imap_access_disabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "With POP and IMAP enabled, users can access email through **legacy clients** that rely on simple password authentication, bypassing **multifactor authentication** and other modern security controls. This significantly increases the risk of **credential-based account compromise**.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/105694",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/sync/turn-pop-and-imap-on-or-off-for-users",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_script_attachment_protection_enabled/gmail_script_attachment_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_script_attachment_protection_enabled/gmail_script_attachment_protection_enabled.metadata.json
index fc2a3af1b0..cae7d474ac 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_script_attachment_protection_enabled/gmail_script_attachment_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_script_attachment_protection_enabled/gmail_script_attachment_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against script-bearing attachments from untrusted senders, users may receive **files containing malicious scripts** that can execute harmful code when opened. Attackers commonly use script attachments to deliver **malware, backdoors, or credential stealers**.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/set-up-rules-to-detect-harmful-attachments",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_shortener_scanning_enabled/gmail_shortener_scanning_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_shortener_scanning_enabled/gmail_shortener_scanning_enabled.metadata.json
index 4ea88e92d3..518b90b962 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_shortener_scanning_enabled/gmail_shortener_scanning_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_shortener_scanning_enabled/gmail_shortener_scanning_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without shortened URL scanning, attackers can use **URL shortening services** to hide malicious destinations in phishing emails. Users cannot visually verify where the link leads, increasing the success rate of **phishing and credential harvesting** attacks.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_unauthenticated_email_protection_enabled/gmail_unauthenticated_email_protection_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_unauthenticated_email_protection_enabled/gmail_unauthenticated_email_protection_enabled.metadata.json
index 6199080224..ec730d0a8b 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_unauthenticated_email_protection_enabled/gmail_unauthenticated_email_protection_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_unauthenticated_email_protection_enabled/gmail_unauthenticated_email_protection_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without protection against unauthenticated emails, users may receive **spoofed or forged messages** that fail SPF and DKIM checks but are still delivered normally. This enables **phishing**, **spam**, and **impersonation attacks** that exploit the lack of sender verification.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/9157861",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/prowler/providers/googleworkspace/services/gmail/gmail_untrusted_link_warnings_enabled/gmail_untrusted_link_warnings_enabled.metadata.json b/prowler/providers/googleworkspace/services/gmail/gmail_untrusted_link_warnings_enabled/gmail_untrusted_link_warnings_enabled.metadata.json
index eb350e3b0f..78678ff9f5 100644
--- a/prowler/providers/googleworkspace/services/gmail/gmail_untrusted_link_warnings_enabled/gmail_untrusted_link_warnings_enabled.metadata.json
+++ b/prowler/providers/googleworkspace/services/gmail/gmail_untrusted_link_warnings_enabled/gmail_untrusted_link_warnings_enabled.metadata.json
@@ -13,8 +13,8 @@
"Risk": "Without untrusted link warnings, users may click on **phishing links** or links to **malware distribution sites** without any warning. This significantly increases the success rate of **social engineering attacks** targeting the organization.",
"RelatedUrl": "",
"AdditionalURLs": [
- "https://support.google.com/a/answer/7676854",
- "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ "https://knowledge.workspace.google.com/admin/gmail/advanced/advanced-phishing-and-malware-protection",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
],
"Remediation": {
"Code": {
diff --git a/tests/providers/oraclecloud/services/events/events_rule_iam_group_changes/__init__.py b/prowler/providers/googleworkspace/services/groups/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_iam_group_changes/__init__.py
rename to prowler/providers/googleworkspace/services/groups/__init__.py
diff --git a/prowler/providers/googleworkspace/services/groups/groups_client.py b/prowler/providers/googleworkspace/services/groups/groups_client.py
new file mode 100644
index 0000000000..0f4881b52c
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.groups.groups_service import (
+ Groups,
+)
+
+groups_client = Groups(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/events/events_rule_iam_policy_changes/__init__.py b/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_iam_policy_changes/__init__.py
rename to prowler/providers/googleworkspace/services/groups/groups_creation_restricted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.metadata.json b/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.metadata.json
new file mode 100644
index 0000000000..6a5bb80c3e
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "groups_creation_restricted",
+ "CheckTitle": "Group creation is restricted to admins with no external members or incoming email",
+ "CheckType": [],
+ "ServiceName": "groups",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "Google Groups for Business **creation settings** control who can create groups and whether group owners can add external members or allow incoming email from outside the organization. Restricting creation to admins and disabling external member and incoming email options limits the attack surface.",
+ "Risk": "Allowing any user to create groups with external members or incoming email from outside increases the risk of **unauthorized data sharing**, **spam delivery**, and **shadow IT** groups that bypass organizational controls.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/groups/what-you-get-with-groups-for-business",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace** > **Groups for Business**\n3. Click **Creating groups**\n4. Select **Only organization admins can create groups**\n5. Uncheck **Group owners can allow external members**\n6. Uncheck **Group owners can allow incoming email from outside the organization**\n7. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict **group creation** to **organization admins** and disable **external member** and **incoming email** options to maintain control over group membership and communication boundaries.",
+ "Url": "https://hub.prowler.com/check/groups_creation_restricted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "groups_external_access_restricted",
+ "groups_view_conversations_restricted"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.py b/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.py
new file mode 100644
index 0000000000..ad9ce534ed
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_creation_restricted/groups_creation_restricted.py
@@ -0,0 +1,76 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.groups.groups_client import (
+ groups_client,
+)
+
+
+class groups_creation_restricted(Check):
+ """Check that group creation is restricted to admins only with no external members or incoming email.
+
+ This check verifies three sub-settings:
+ - Only organization admins can create groups (not all users)
+ - Group owners cannot allow external members
+ - Group owners cannot allow incoming email from outside the organization
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if groups_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=groups_client.policies,
+ resource_id="groupsPolicies",
+ resource_name="Groups Policies",
+ customer_id=groups_client.provider.identity.customer_id,
+ )
+
+ policies = groups_client.policies
+ domain = groups_client.provider.identity.domain
+
+ access_level = policies.create_groups_access_level
+ external_members = policies.owners_can_allow_external_members
+ incoming_mail = policies.owners_can_allow_incoming_mail_from_public
+
+ issues = []
+
+ # Check creation access level
+ # Default is USERS_IN_DOMAIN (insecure) — only ADMIN_ONLY is compliant
+ if access_level is None or access_level != "ADMIN_ONLY":
+ effective = access_level or "USERS_IN_DOMAIN (default)"
+ issues.append(
+ f"group creation is set to {effective} instead of ADMIN_ONLY"
+ )
+
+ # Check external members
+ # Default is false (secure) — only false is compliant
+ if external_members is True:
+ issues.append("group owners can allow external members")
+
+ # Check incoming mail from outside
+ # Default is false (secure) — only true is non-compliant
+ if incoming_mail is True:
+ issues.append(
+ "group owners can allow incoming email from outside the organization"
+ )
+
+ if not issues:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Group creation is properly restricted in domain {domain}: "
+ f"admin-only creation, no external members, "
+ f"no incoming email from outside."
+ )
+ else:
+ report.status = "FAIL"
+ issues_text = "; ".join(issues)
+ report.status_extended = (
+ f"Group creation is not fully restricted "
+ f"in domain {domain}: {issues_text}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/events/events_rule_identity_provider_changes/__init__.py b/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_identity_provider_changes/__init__.py
rename to prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.metadata.json b/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.metadata.json
new file mode 100644
index 0000000000..9d32063c90
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "groups_external_access_restricted",
+ "CheckTitle": "Accessing groups from outside the organization is set to private",
+ "CheckType": [],
+ "ServiceName": "groups",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "Google Groups for Business **external access** controls whether people outside the organization can view and search for groups. When set to private, only users within the domain can discover and access groups, while external users can still email a group if the group's own settings allow it.",
+ "Risk": "Allowing external access to groups exposes **group names, descriptions, and membership** to anyone outside the organization, increasing the risk of **information disclosure** and enabling external parties to identify targets for **social engineering attacks**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/groups/what-you-get-with-groups-for-business",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace** > **Groups for Business**\n3. Click **Sharing options**\n4. Set **Accessing groups from outside this organization** to **Private**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set **external group access** to **private** to prevent external parties from viewing or searching for organizational groups.",
+ "Url": "https://hub.prowler.com/check/groups_external_access_restricted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "groups_creation_restricted",
+ "groups_view_conversations_restricted"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.py b/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.py
new file mode 100644
index 0000000000..4ac057b905
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_external_access_restricted/groups_external_access_restricted.py
@@ -0,0 +1,54 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.groups.groups_client import (
+ groups_client,
+)
+
+
+class groups_external_access_restricted(Check):
+ """Check that accessing groups from outside the organization is set to private.
+
+ This check verifies that the domain-level Groups for Business policy
+ restricts external access so that only domain users can view groups,
+ preventing information exposure to external parties.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if groups_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=groups_client.policies,
+ resource_id="groupsPolicies",
+ resource_name="Groups Policies",
+ customer_id=groups_client.provider.identity.customer_id,
+ )
+
+ collaboration = groups_client.policies.collaboration_capability
+ domain = groups_client.provider.identity.domain
+
+ if collaboration == "DOMAIN_USERS_ONLY":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Groups external access is set to private (domain users only) "
+ f"in domain {domain}."
+ )
+ elif collaboration is None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Groups external access uses Google's secure default "
+ f"configuration (private) in domain {domain}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Groups external access is set to {collaboration} "
+ f"in domain {domain}. "
+ f"External access should be set to private (domain users only)."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/groups/groups_service.py b/prowler/providers/googleworkspace/services/groups/groups_service.py
new file mode 100644
index 0000000000..1ebc0508e3
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_service.py
@@ -0,0 +1,118 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+
+class Groups(GoogleWorkspaceService):
+ """Google Workspace Groups for Business service for auditing domain-level group policies.
+
+ Uses the Cloud Identity Policy API v1 to read group sharing, creation,
+ and conversation viewing settings configured in the Admin Console.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.policies = GroupsPolicies()
+ self.policies_fetched = False
+ self._fetch_groups_for_business_policies()
+
+ def _fetch_groups_for_business_policies(self):
+ """Fetch Groups for Business policies from the Cloud Identity Policy API v1."""
+ logger.info("Groups for Business - Fetching policies...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ request = service.policies().list(
+ pageSize=100,
+ filter='setting.type.matches("groups_for_business.*")',
+ )
+ fetch_succeeded = True
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ setting_type = setting.get("type", "").removeprefix("settings/")
+ logger.debug(f"Processing setting type: {setting_type}")
+
+ value = setting.get("value", {})
+
+ if setting_type == "groups_for_business.groups_sharing":
+ self.policies.collaboration_capability = value.get(
+ "collaborationCapability"
+ )
+ self.policies.create_groups_access_level = value.get(
+ "createGroupsAccessLevel"
+ )
+ self.policies.owners_can_allow_external_members = value.get(
+ "ownersCanAllowExternalMembers"
+ )
+ self.policies.owners_can_allow_incoming_mail_from_public = (
+ value.get("ownersCanAllowIncomingMailFromPublic")
+ )
+ self.policies.view_topics_default_access_level = value.get(
+ "viewTopicsDefaultAccessLevel"
+ )
+ self.policies.owners_can_hide_groups = value.get(
+ "ownersCanHideGroups"
+ )
+ self.policies.new_groups_are_hidden = value.get(
+ "newGroupsAreHidden"
+ )
+ logger.debug(
+ "Groups for Business sharing settings fetched."
+ )
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Groups for Business policies",
+ self.provider.identity.customer_id,
+ )
+ fetch_succeeded = False
+ break
+
+ self.policies_fetched = fetch_succeeded
+
+ logger.info(
+ f"Groups for Business policies fetched - "
+ f"Collaboration: {self.policies.collaboration_capability}, "
+ f"Creation: {self.policies.create_groups_access_level}, "
+ f"View topics: {self.policies.view_topics_default_access_level}"
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Groups for Business policies",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+
+class GroupsPolicies(BaseModel):
+ """Model for domain-level Groups for Business policy settings."""
+
+ # groups_for_business.groups_sharing
+ collaboration_capability: Optional[str] = None
+ create_groups_access_level: Optional[str] = None
+ owners_can_allow_external_members: Optional[bool] = None
+ owners_can_allow_incoming_mail_from_public: Optional[bool] = None
+ view_topics_default_access_level: Optional[str] = None
+ owners_can_hide_groups: Optional[bool] = None
+ new_groups_are_hidden: Optional[bool] = None
diff --git a/tests/providers/oraclecloud/services/events/events_rule_idp_group_mapping_changes/__init__.py b/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_idp_group_mapping_changes/__init__.py
rename to prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.metadata.json b/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.metadata.json
new file mode 100644
index 0000000000..88f0927155
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "groups_view_conversations_restricted",
+ "CheckTitle": "Default permission to view conversations is set to all group members",
+ "CheckType": [],
+ "ServiceName": "groups",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "Google Groups for Business **conversation viewing** controls who can see group conversations by default. Restricting this to group members only ensures that conversations are visible only to participants, not all users in the organization or external parties.",
+ "Risk": "Allowing all organization users or anyone to view group conversations can lead to **information disclosure** of sensitive discussions, internal decisions, and confidential data shared within groups.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/groups/what-you-get-with-groups-for-business",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace** > **Groups for Business**\n3. Click **Sharing options**\n4. Set **Default for permission to view conversations** to **All group members**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set the default **permission to view conversations** to **all group members** to ensure group discussions are only visible to their participants.",
+ "Url": "https://hub.prowler.com/check/groups_view_conversations_restricted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "groups_external_access_restricted",
+ "groups_creation_restricted"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.py b/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.py
new file mode 100644
index 0000000000..66fb15a43b
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/groups/groups_view_conversations_restricted/groups_view_conversations_restricted.py
@@ -0,0 +1,55 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.groups.groups_client import (
+ groups_client,
+)
+
+
+class groups_view_conversations_restricted(Check):
+ """Check that the default permission to view conversations is set to All Group Members.
+
+ This check verifies that the domain-level Groups for Business policy
+ restricts conversation viewing to group members only, preventing
+ broader access by all organization users or anyone.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if groups_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=groups_client.policies,
+ resource_id="groupsPolicies",
+ resource_name="Groups Policies",
+ customer_id=groups_client.provider.identity.customer_id,
+ )
+
+ view_access = groups_client.policies.view_topics_default_access_level
+ domain = groups_client.provider.identity.domain
+
+ if view_access == "GROUP_MEMBERS":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Default permission to view conversations is set to "
+ f"all group members in domain {domain}."
+ )
+ elif view_access is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Default permission to view conversations uses Google's default "
+ f"configuration (all organization users) in domain {domain}. "
+ f"It should be restricted to all group members only."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Default permission to view conversations is set to "
+ f"{view_access} in domain {domain}. "
+ f"It should be restricted to all group members only."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/events/events_rule_local_user_authentication/__init__.py b/prowler/providers/googleworkspace/services/marketplace/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_local_user_authentication/__init__.py
rename to prowler/providers/googleworkspace/services/marketplace/__init__.py
diff --git a/tests/providers/oraclecloud/services/events/events_rule_network_gateway_changes/__init__.py b/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_network_gateway_changes/__init__.py
rename to prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.metadata.json b/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.metadata.json
new file mode 100644
index 0000000000..78fe1850ad
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "marketplace_apps_access_restricted",
+ "CheckTitle": "Users access to Google Workspace Marketplace apps is restricted",
+ "CheckType": [],
+ "ServiceName": "marketplace",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "The domain-wide Google Workspace Marketplace configuration **restricts which apps users can install**. Only admin-approved apps from the Marketplace allowlist are permitted, preventing users from installing unvetted third-party applications.",
+ "Risk": "Allowing unrestricted Marketplace app installation exposes the organization to **unvetted third-party applications** that may request broad OAuth scopes, potentially gaining access to **sensitive organizational data** including emails, documents, and calendar events without proper security review.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/apps/manage-the-marketplace-app-allowlist-for-your-organization",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace Marketplace apps**\n3. Click **Settings**\n4. Under **Manage Google Workspace Marketplace allowlist access**, select **Allow users to install and run only selected apps from the Marketplace**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict **Marketplace app installation** to only **admin-approved apps** to prevent users from installing unvetted third-party applications that could access sensitive organizational data.",
+ "Url": "https://hub.prowler.com/check/marketplace_apps_access_restricted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.py b/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.py
new file mode 100644
index 0000000000..cee1adaa71
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/marketplace/marketplace_apps_access_restricted/marketplace_apps_access_restricted.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.marketplace.marketplace_client import (
+ marketplace_client,
+)
+
+
+class marketplace_apps_access_restricted(Check):
+ """Check that Google Workspace Marketplace app installation is restricted.
+
+ This check verifies that the domain-level Marketplace policy restricts
+ which apps users can install, preventing unvetted third-party applications
+ from accessing organizational data.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if marketplace_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=marketplace_client.policies,
+ resource_id="marketplacePolicies",
+ resource_name="Marketplace Policies",
+ customer_id=marketplace_client.provider.identity.customer_id,
+ )
+
+ access_level = marketplace_client.policies.access_level
+
+ if access_level == "ALLOW_LISTED_APPS":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Marketplace app installation is restricted to admin-approved apps "
+ f"in domain {marketplace_client.provider.identity.domain}."
+ )
+ elif access_level == "ALLOW_NONE":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Marketplace app installation is fully blocked "
+ f"in domain {marketplace_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if access_level is None:
+ report.status_extended = (
+ f"Marketplace app access is not explicitly configured "
+ f"in domain {marketplace_client.provider.identity.domain}. "
+ f"The default allows all apps. "
+ f"App installation should be restricted to approved apps only."
+ )
+ else:
+ report.status_extended = (
+ f"Marketplace allows users to install any app "
+ f"in domain {marketplace_client.provider.identity.domain}. "
+ f"App installation should be restricted to approved apps only."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/marketplace/marketplace_client.py b/prowler/providers/googleworkspace/services/marketplace/marketplace_client.py
new file mode 100644
index 0000000000..ccc6cdf208
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/marketplace/marketplace_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.marketplace.marketplace_service import (
+ Marketplace,
+)
+
+marketplace_client = Marketplace(Provider.get_global_provider())
diff --git a/prowler/providers/googleworkspace/services/marketplace/marketplace_service.py b/prowler/providers/googleworkspace/services/marketplace/marketplace_service.py
new file mode 100644
index 0000000000..4c117a4468
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/marketplace/marketplace_service.py
@@ -0,0 +1,89 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+
+class Marketplace(GoogleWorkspaceService):
+ """Google Workspace Marketplace service for auditing domain-level Marketplace policies.
+
+ Uses the Cloud Identity Policy API v1 to read the Marketplace app access
+ settings configured in the Admin Console.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.policies = MarketplacePolicies()
+ self.policies_fetched = False
+ self._fetch_marketplace_policies()
+
+ def _fetch_marketplace_policies(self):
+ """Fetch Marketplace policies from the Cloud Identity Policy API v1."""
+ logger.info("Marketplace - Fetching marketplace policies...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ request = service.policies().list(
+ pageSize=100,
+ filter='setting.type.matches("workspace_marketplace.*")',
+ )
+ fetch_succeeded = True
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ setting_type = setting.get("type", "").removeprefix("settings/")
+ value = setting.get("value", {})
+
+ if setting_type == "workspace_marketplace.apps_access_options":
+ self.policies.access_level = value.get("accessLevel")
+ logger.debug(
+ "Marketplace access level: "
+ f"{self.policies.access_level}"
+ )
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Marketplace policies",
+ self.provider.identity.customer_id,
+ )
+ fetch_succeeded = False
+ break
+
+ self.policies_fetched = fetch_succeeded
+
+ logger.info(
+ f"Marketplace policies fetched - "
+ f"Access level: {self.policies.access_level}"
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Marketplace policies",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+
+class MarketplacePolicies(BaseModel):
+ """Model for domain-level Marketplace policy settings."""
+
+ # workspace_marketplace.apps_access_options
+ access_level: Optional[str] = None
diff --git a/tests/providers/oraclecloud/services/events/events_rule_network_security_group_changes/__init__.py b/prowler/providers/googleworkspace/services/rules/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_network_security_group_changes/__init__.py
rename to prowler/providers/googleworkspace/services/rules/__init__.py
diff --git a/tests/providers/oraclecloud/services/events/events_rule_route_table_changes/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_route_table_changes/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.metadata.json
new file mode 100644
index 0000000000..a93b4fb737
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_admin_privilege_granted_alert_configured",
+ "CheckTitle": "User granted Admin privilege alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **User granted Admin privilege** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when a user is given elevated admin privileges.",
+ "Risk": "Without this alert enabled, administrators will not be notified when users receive **elevated admin privileges**. Unauthorized privilege escalation could indicate account compromise or insider threats and requires immediate verification.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **User granted Admin privilege** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Medium**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **User granted Admin privilege** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_admin_privilege_granted_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.py
new file mode 100644
index 0000000000..55b9a685bf
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_admin_privilege_granted_alert_configured/rules_admin_privilege_granted_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "User granted Admin privilege"
+
+
+class rules_admin_privilege_granted_alert_configured(Check):
+ """Check that the User granted Admin privilege system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/rules/rules_client.py b/prowler/providers/googleworkspace/services/rules/rules_client.py
new file mode 100644
index 0000000000..8d1c8821a1
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.rules.rules_service import (
+ Rules,
+)
+
+rules_client = Rules(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/events/events_rule_security_list_changes/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_security_list_changes/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.metadata.json
new file mode 100644
index 0000000000..34885cb605
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_gmail_employee_spoofing_alert_configured",
+ "CheckTitle": "Gmail potential employee spoofing alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **Gmail potential employee spoofing** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when incoming messages have a sender name matching the directory but from an external domain.",
+ "Risk": "Without this alert enabled, administrators will not be notified of potential **employee spoofing via email**. Attackers may impersonate internal employees using external email addresses to conduct phishing attacks against the organization.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **Gmail potential employee spoofing** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Medium**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **Gmail potential employee spoofing** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_gmail_employee_spoofing_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "email-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.py
new file mode 100644
index 0000000000..0993f72d3d
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_gmail_employee_spoofing_alert_configured/rules_gmail_employee_spoofing_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "Gmail potential employee spoofing"
+
+
+class rules_gmail_employee_spoofing_alert_configured(Check):
+ """Check that the Gmail potential employee spoofing system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/events/events_rule_user_changes/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_user_changes/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.metadata.json
new file mode 100644
index 0000000000..35fa25f248
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_government_backed_attacks_alert_configured",
+ "CheckTitle": "Government-backed attacks alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **Government-backed attacks** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when Google believes users are being targeted by a government-backed attacker.",
+ "Risk": "Without this alert enabled, administrators will not be notified of potential **government-backed attacks** targeting their users. These attacks are sophisticated and require immediate response to protect affected accounts and investigate the threat.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **Government-backed attacks** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **High**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **Government-backed attacks** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_government_backed_attacks_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.py
new file mode 100644
index 0000000000..b566d99e0c
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_government_backed_attacks_alert_configured/rules_government_backed_attacks_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "Government-backed attacks"
+
+
+class rules_government_backed_attacks_alert_configured(Check):
+ """Check that the Government-backed attacks system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/events/events_rule_vcn_changes/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/events/events_rule_vcn_changes/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.metadata.json
new file mode 100644
index 0000000000..870144a873
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_leaked_password_alert_configured",
+ "CheckTitle": "Leaked password alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **Leaked password** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when Google detects compromised credentials requiring a password reset.",
+ "Risk": "Without this alert enabled, administrators will not be notified when Google detects that a user's **credentials have been compromised** in a publicized breach. The user likely reused their password at another site that was breached, and their account requires an immediate password change.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **Leaked password** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Medium**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **Leaked password** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_leaked_password_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.py
new file mode 100644
index 0000000000..797bed4f71
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_leaked_password_alert_configured/rules_leaked_password_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "Leaked password"
+
+
+class rules_leaked_password_alert_configured(Check):
+ """Check that the Leaked password system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/filestorage/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/filestorage/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.metadata.json
new file mode 100644
index 0000000000..f1f4fbc622
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_password_changed_alert_configured",
+ "CheckTitle": "User's password changed alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **User's password changed** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are promptly notified when user passwords are changed.",
+ "Risk": "Without this alert enabled, administrators will not be notified when user passwords are changed. This could allow **credential compromise and account takeover** to go undetected, giving attackers time to establish persistence.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **User's password changed** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Medium**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **User's password changed** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_password_changed_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.py
new file mode 100644
index 0000000000..fb6382caf8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_password_changed_alert_configured/rules_password_changed_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "User's password changed"
+
+
+class rules_password_changed_alert_configured(Check):
+ """Check that the User's password changed system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/rules/rules_service.py b/prowler/providers/googleworkspace/services/rules/rules_service.py
new file mode 100644
index 0000000000..76b0b0df7a
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_service.py
@@ -0,0 +1,143 @@
+from typing import Dict, List, Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+SYSTEM_RULE_DEFAULTS: Dict[str, str] = {
+ "User's password changed": "INACTIVE",
+ "Government-backed attacks": "ACTIVE",
+ "User suspended due to suspicious activity": "ACTIVE",
+ "User granted Admin privilege": "INACTIVE",
+ "Suspicious programmatic login": "ACTIVE",
+ "Suspicious login": "ACTIVE",
+ "Leaked password": "ACTIVE",
+ "Gmail potential employee spoofing": "ACTIVE",
+}
+
+
+class Rules(GoogleWorkspaceService):
+ """Google Workspace Rules service for auditing system-defined alert rules.
+
+ Uses the Cloud Identity Policy API v1 to read system-defined alert rule
+ configurations from the Admin Console "Rules" section.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.system_defined_alerts: List[SystemDefinedAlert] = []
+ self.policies_fetched = False
+ self._fetch_system_defined_alerts()
+
+ def _fetch_system_defined_alerts(self):
+ """Fetch system-defined alert rules from the Cloud Identity Policy API v1."""
+ logger.info("Rules - Fetching system-defined alert rules...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ request = service.policies().list(
+ pageSize=100,
+ filter='setting.type.matches("rule.system_defined_alerts")',
+ )
+ fetch_succeeded = True
+ found_rules: Dict[str, SystemDefinedAlert] = {}
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ value = setting.get("value", {})
+ display_name = value.get("displayName", "")
+
+ if display_name not in SYSTEM_RULE_DEFAULTS:
+ continue
+
+ alert = self._parse_alert(value)
+ found_rules[display_name] = alert
+ logger.debug(
+ f"System-defined alert rule: {display_name} "
+ f"state={alert.state} "
+ f"has_recipients={alert.email_notifications_enabled}"
+ )
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching system-defined alert rules",
+ self.provider.identity.customer_id,
+ )
+ fetch_succeeded = False
+ break
+
+ for rule_name, default_state in SYSTEM_RULE_DEFAULTS.items():
+ if rule_name not in found_rules:
+ is_active_default = default_state == "ACTIVE"
+ found_rules[rule_name] = SystemDefinedAlert(
+ display_name=rule_name,
+ state=default_state,
+ email_notifications_enabled=is_active_default,
+ all_super_admins=is_active_default,
+ )
+ logger.debug(
+ f"System-defined alert rule (default): {rule_name} "
+ f"state={default_state}"
+ )
+
+ self.system_defined_alerts = list(found_rules.values())
+ self.policies_fetched = fetch_succeeded
+
+ logger.info(
+ f"Rules policies fetched - "
+ f"{len(self.system_defined_alerts)} system-defined alert rules"
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching system-defined alert rules",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+ @staticmethod
+ def _parse_alert(value: dict) -> "SystemDefinedAlert":
+ """Parse a single system-defined alert rule from the API response."""
+ display_name = value.get("displayName", "")
+ state = value.get("state", "INACTIVE")
+
+ alert_center_action = value.get("action", {}).get("alertCenterAction", {})
+ severity = alert_center_action.get("alertCenterConfig", {}).get("severity")
+ recipients = alert_center_action.get("recipients", [])
+
+ all_super_admins = any(r.get("allSuperAdmins") is True for r in recipients)
+
+ return SystemDefinedAlert(
+ display_name=display_name,
+ state=state,
+ severity=severity,
+ email_notifications_enabled=len(recipients) > 0,
+ all_super_admins=all_super_admins,
+ )
+
+
+class SystemDefinedAlert(BaseModel):
+ """Model for a system-defined alert rule."""
+
+ display_name: str
+ state: str = "INACTIVE"
+ severity: Optional[str] = None
+ email_notifications_enabled: bool = False
+ all_super_admins: bool = False
diff --git a/tests/providers/oraclecloud/services/filestorage/filestorage_file_system_encrypted_with_cmk/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/filestorage/filestorage_file_system_encrypted_with_cmk/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.metadata.json
new file mode 100644
index 0000000000..b79120abde
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_suspicious_activity_suspension_alert_configured",
+ "CheckTitle": "User suspended due to suspicious activity alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **User suspended due to suspicious activity** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when Google suspends an account due to a potential compromise.",
+ "Risk": "Without this alert enabled, administrators will not be promptly notified when Google **suspends a user account** due to detected compromise. The suspended user cannot work, and the underlying security incident requires immediate investigation.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **User suspended due to suspicious activity** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **High**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **User suspended due to suspicious activity** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_suspicious_activity_suspension_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.py
new file mode 100644
index 0000000000..cd243be8e3
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_activity_suspension_alert_configured/rules_suspicious_activity_suspension_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "User suspended due to suspicious activity"
+
+
+class rules_suspicious_activity_suspension_alert_configured(Check):
+ """Check that the User suspended due to suspicious activity system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.metadata.json
new file mode 100644
index 0000000000..93af99b565
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_suspicious_login_alert_configured",
+ "CheckTitle": "Suspicious login alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **Suspicious login** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when Google detects a sign-in attempt that does not match a user's normal behavior.",
+ "Risk": "Without this alert enabled, administrators will not be notified of **suspicious login attempts** such as sign-ins from unusual locations. This could indicate an active attack using previously obtained credentials.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **Suspicious login** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Low**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **Suspicious login** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_suspicious_login_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.py
new file mode 100644
index 0000000000..eee7844c43
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_login_alert_configured/rules_suspicious_login_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "Suspicious login"
+
+
+class rules_suspicious_login_alert_configured(Check):
+ """Check that the Suspicious login system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_iam_admins_cannot_update_tenancy_admins/__init__.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_iam_admins_cannot_update_tenancy_admins/__init__.py
rename to prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.metadata.json b/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.metadata.json
new file mode 100644
index 0000000000..202df2adad
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "rules_suspicious_programmatic_login_alert_configured",
+ "CheckTitle": "Suspicious programmatic login alert rule is configured",
+ "CheckType": [],
+ "ServiceName": "rules",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "The **Suspicious programmatic login** system-defined alert rule should be enabled with alerts sent to the alert center, email notifications turned on, and recipients set to all super administrators. This ensures administrators are notified when Google detects suspicious login attempts from applications or programs.",
+ "Risk": "Without this alert enabled, administrators will not be notified of **suspicious programmatic login attempts**. This could indicate automated credential stuffing or unauthorized API access using compromised credentials.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://support.google.com/a/answer/3230421",
+ "https://cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Select **Rules**\n3. Under **Google protects you by default** select **View list**\n4. Scroll to **Suspicious programmatic login** and select it\n5. Within the Actions pane, click the edit pencil\n6. Select **Send to alert center** to set the alert to ON\n7. Set the alert severity to **Low**\n8. Select **Send email notifications**\n9. Ensure **All super administrators** is selected as recipients\n10. Click **Review** to confirm the values\n11. Click **Update Rule**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure the **Suspicious programmatic login** alert rule with alert center ON, email notifications ON, and recipients set to **all super administrators**.",
+ "Url": "https://hub.prowler.com/check/rules_suspicious_programmatic_login_alert_configured"
+ }
+ },
+ "Categories": [
+ "logging",
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.py b/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.py
new file mode 100644
index 0000000000..0d609a99e1
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/rules/rules_suspicious_programmatic_login_alert_configured/rules_suspicious_programmatic_login_alert_configured.py
@@ -0,0 +1,61 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.rules.rules_client import (
+ rules_client,
+)
+
+RULE_NAME = "Suspicious programmatic login"
+
+
+class rules_suspicious_programmatic_login_alert_configured(Check):
+ """Check that the Suspicious programmatic login system-defined alert rule is fully configured."""
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if rules_client.policies_fetched:
+ for alert in rules_client.system_defined_alerts:
+ if alert.display_name != RULE_NAME:
+ continue
+
+ domain = rules_client.provider.identity.domain
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=alert,
+ resource_id=f"systemDefinedAlert/{RULE_NAME}",
+ resource_name=RULE_NAME,
+ customer_id=rules_client.provider.identity.customer_id,
+ )
+
+ is_active = alert.state == "ACTIVE"
+ has_recipients = alert.email_notifications_enabled
+ all_super_admins = alert.all_super_admins
+
+ if is_active and has_recipients and all_super_admins:
+ report.status = "PASS"
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is properly "
+ f"configured in domain {domain}: alert is ON, email "
+ f"notifications are enabled, and recipients include "
+ f"all super administrators."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not is_active:
+ issues.append("alert is OFF")
+ if not has_recipients:
+ issues.append("email notifications are disabled")
+ elif not all_super_admins:
+ issues.append(
+ "email recipients do not include all super administrators"
+ )
+ report.status_extended = (
+ f"System-defined alert rule '{RULE_NAME}' is not properly "
+ f"configured in domain {domain}: {', '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_instance_principal_used/__init__.py b/prowler/providers/googleworkspace/services/security/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_instance_principal_used/__init__.py
rename to prowler/providers/googleworkspace/services/security/__init__.py
diff --git a/tests/providers/oraclecloud/services/identity/identity_no_resources_in_root_compartment/__init__.py b/prowler/providers/googleworkspace/services/security/security_2sv_enforced/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_no_resources_in_root_compartment/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_2sv_enforced/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.metadata.json b/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.metadata.json
new file mode 100644
index 0000000000..3a2c0b4566
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_2sv_enforced",
+ "CheckTitle": "2-Step Verification is enforced for all users",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level policy **enforces 2-Step Verification (Multi-Factor Authentication)** for all users. 2-Step Verification requires users to present a second form of authentication beyond their password, significantly reducing the risk of account compromise.",
+ "Risk": "Without 2-Step Verification enforcement, users can access their accounts with **only a password**. If credentials are compromised through phishing, credential stuffing, or data breaches, attackers gain **immediate access** to the user's account and organizational data without any additional verification.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/protect-your-business-with-2-step-verification",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **2-Step Verification**\n3. Check **Allow users to turn on 2-Step Verification**\n4. Set **Enforcement** to **On**\n5. Set **New user enrollment period** to **2 weeks**\n6. Under **Frequency**, uncheck **Allow user to trust device**\n7. Under **Methods**, select **Any except verification codes via text, phone call**\n8. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enforce **2-Step Verification** for all users to require a second authentication factor beyond passwords, protecting accounts from credential-based attacks.",
+ "Url": "https://hub.prowler.com/check/security_2sv_enforced"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_2sv_hardware_keys_admins"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.py b/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.py
new file mode 100644
index 0000000000..7cf17b348e
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_2sv_enforced/security_2sv_enforced.py
@@ -0,0 +1,59 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_2sv_enforced(Check):
+ """Check that 2-Step Verification is enforced for all users.
+
+ This check verifies that the domain-level policy enforces 2-Step
+ Verification (Multi-Factor Authentication) for all users, reducing
+ the risk of account compromise through stolen credentials.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ enforced_from = security_client.policies.two_sv_enforced_from
+ # The API returns "1970-01-01T00:00:00Z" (protobuf zero-value
+ # Timestamp) when enforcement is OFF, not null or empty.
+ enforcement_off_epoch = "1970-01-01T00:00:00Z"
+
+ if enforced_from and enforced_from != enforcement_off_epoch:
+ report.status = "PASS"
+ report.status_extended = (
+ f"2-Step Verification enforcement is active "
+ f"(enforced from {enforced_from}) "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if enforced_from is None:
+ report.status_extended = (
+ f"2-Step Verification enforcement is not configured "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"The default is OFF. 2-Step Verification should be "
+ f"enforced for all users."
+ )
+ else:
+ report.status_extended = (
+ f"2-Step Verification enforcement is set to OFF "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"2-Step Verification should be enforced for all users."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_non_root_compartment_exists/__init__.py b/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_non_root_compartment_exists/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.metadata.json b/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.metadata.json
new file mode 100644
index 0000000000..4aae5840a5
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_2sv_hardware_keys_admins",
+ "CheckTitle": "Hardware security keys are required for 2-Step Verification",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level 2-Step Verification policy requires **hardware security keys only** as the allowed sign-in factor, providing the strongest phishing-resistant authentication. **Note**: the Policy API returns domain-wide policies only and cannot verify admin role-specific enforcement.",
+ "Risk": "When 2SV methods include **SMS, phone calls, or software-based authenticators**, users are vulnerable to **SIM swapping, SS7 attacks, and real-time phishing proxies** that can intercept one-time codes. Hardware security keys are resistant to all known remote phishing techniques.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/protect-your-business-with-2-step-verification",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Authentication** > **2-Step Verification**\n3. Select the appropriate group with **ALL ADMIN ROLES** (create this group if needed)\n4. Under **Methods**, select **Only security key**\n5. Under **2-Step Verification policy suspension grace period**, select **1 day**\n6. Under **Security codes**, select **Don't allow users to generate security codes**\n7. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require **hardware security keys only** for 2-Step Verification to provide the strongest phishing-resistant authentication for all users, particularly those in administrative roles.",
+ "Url": "https://hub.prowler.com/check/security_2sv_hardware_keys_admins"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_2sv_enforced"
+ ],
+ "Notes": "The Cloud Identity Policy API returns domain-wide policies only. It cannot verify that hardware keys are enforced specifically for admin roles versus all users. This check evaluates the customer-level enforcement factor, which applies to all users including administrators."
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.py b/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.py
new file mode 100644
index 0000000000..5913f448e1
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_2sv_hardware_keys_admins/security_2sv_hardware_keys_admins.py
@@ -0,0 +1,64 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_2sv_hardware_keys_admins(Check):
+ """Check that 2SV enforcement requires hardware security keys.
+
+ This check verifies that the domain-level 2-Step Verification enforcement
+ factor is set to security keys only, providing the strongest protection
+ against phishing attacks. Note: the Cloud Identity Policy API returns
+ domain-wide policies — it cannot verify enforcement for admin roles
+ specifically. This check evaluates the customer-level policy which
+ applies to all users including administrators.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ factor_set = security_client.policies.two_sv_allowed_factor_set
+
+ if factor_set == "PASSKEY_ONLY":
+ report.status = "PASS"
+ report.status_extended = (
+ f"2-Step Verification enforcement requires security keys only "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if factor_set is None:
+ report.status_extended = (
+ f"2-Step Verification enforcement factor is not configured "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"The default allows all methods including SMS and phone call. "
+ f"Security keys should be required for administrative accounts. "
+ f"Note: this check evaluates the domain-wide policy, the Policy "
+ f"API does not expose role-specific 2SV enforcement."
+ )
+ else:
+ report.status_extended = (
+ f"2-Step Verification enforcement factor is set to "
+ f"{factor_set} "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Only security keys (PASSKEY_ONLY) should be allowed for "
+ f"administrative accounts. "
+ f"Note: this check evaluates the domain-wide policy, the Policy "
+ f"API does not expose role-specific 2SV enforcement."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_password_policy_expires_within_365_days/__init__.py b/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_password_policy_expires_within_365_days/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.metadata.json b/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.metadata.json
new file mode 100644
index 0000000000..10c5d9e788
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_advanced_protection_configured",
+ "CheckTitle": "Advanced Protection Program is configured",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level policy enables the **Advanced Protection Program** with user self-enrollment and **blocks the use of security codes**. The Advanced Protection Program is Google's strongest account security offering, requiring hardware security keys and applying a curated set of high-security policies.",
+ "Risk": "Without the Advanced Protection Program, user accounts rely on standard security controls that are vulnerable to **sophisticated phishing attacks, targeted credential theft, and third-party app data access**. Allowing security codes alongside Advanced Protection weakens its protections by providing an alternative authentication path that can be intercepted.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/protect-users-with-the-advanced-protection-program",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Advanced Protection Program**\n3. Under **Enrollment**, select **Enable user enrollment**\n4. Under **Security Codes**, select **Do not allow users to generate security codes**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable the **Advanced Protection Program** with user self-enrollment and block **security codes** to enforce the strongest available account protection.",
+ "Url": "https://hub.prowler.com/check/security_advanced_protection_configured"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_2sv_enforced",
+ "security_2sv_hardware_keys_admins"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.py b/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.py
new file mode 100644
index 0000000000..ab32837515
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_advanced_protection_configured/security_advanced_protection_configured.py
@@ -0,0 +1,66 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_advanced_protection_configured(Check):
+ """Check that the Advanced Protection Program is configured.
+
+ This check verifies that the domain-level policy enables Advanced
+ Protection Program self-enrollment and blocks the use of security codes,
+ as recommended by CIS 4.1.3.1.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ enrollment = security_client.policies.advanced_protection_enrollment
+ code_option = (
+ security_client.policies.advanced_protection_security_code_option
+ )
+ domain = security_client.provider.identity.domain
+
+ enrollment_ok = enrollment is True
+ codes_ok = code_option == "CODES_NOT_ALLOWED"
+
+ if enrollment_ok and codes_ok:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Advanced Protection Program is configured with enrollment "
+ f"enabled and security codes blocked in domain {domain}."
+ )
+ else:
+ report.status = "FAIL"
+ issues = []
+ if not enrollment_ok:
+ issues.append(
+ "enrollment is not configured"
+ if enrollment is None
+ else "enrollment is disabled"
+ )
+ if not codes_ok:
+ issues.append(
+ f"security codes are "
+ f"{code_option or 'using default (allowed without remote access)'} "
+ f"(should be CODES_NOT_ALLOWED)"
+ )
+ report.status_extended = (
+ f"Advanced Protection Program is not properly configured "
+ f"in domain {domain}: {'; '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_password_policy_minimum_length_14/__init__.py b/prowler/providers/googleworkspace/services/security/security_app_access_restricted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_password_policy_minimum_length_14/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_app_access_restricted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.metadata.json b/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.metadata.json
new file mode 100644
index 0000000000..0945fccdec
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_app_access_restricted",
+ "CheckTitle": "Application access to Google services is restricted",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level API controls configuration **restricts third-party app access** to at least one Google service. This check verifies that the administrator has configured API access controls rather than leaving all services at the unrestricted default. The CIS benchmark recommends restricting access to all applicable services, particularly high-risk scopes like Drive and Gmail.",
+ "Risk": "When application access to Google services is unrestricted, **any third-party app** that users consent to can access sensitive organizational data through Google APIs. This includes apps that may request **broad OAuth scopes** for Drive, Gmail, and other services, potentially leading to **data exfiltration** through unvetted applications.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/apps/control-which-apps-access-google-workspace-data",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Access and Data Control** > **API Controls**\n3. Click **App access control** > **MANAGE GOOGLE SERVICES**\n4. Select **ALL applicable Google Services**\n5. Click **Change access**\n6. Select **Restricted: Only trusted apps can access a service**\n7. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict **application access to Google services** to trusted apps only, particularly for high-risk scopes like **Drive and Gmail**, to prevent unvetted third-party apps from accessing sensitive organizational data.",
+ "Url": "https://hub.prowler.com/check/security_app_access_restricted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_internal_apps_trusted"
+ ],
+ "Notes": "This check verifies that at least one Google service has API access restricted, serving as a signal that the administrator has configured API access controls. The CIS benchmark recommends restricting access to all applicable services."
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.py b/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.py
new file mode 100644
index 0000000000..4db6a95b83
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_app_access_restricted/security_app_access_restricted.py
@@ -0,0 +1,62 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_app_access_restricted(Check):
+ """Check that application access to Google services is restricted.
+
+ This check verifies that at least one Google service has API access
+ restricted for third-party apps, indicating that the administrator
+ has reviewed and configured API access controls. The CIS benchmark
+ recommends restricting access to all applicable services, particularly
+ high-risk scopes like Drive and Gmail. This check serves as a signal
+ that API access controls have been configured rather than left at the
+ unrestricted default.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ restricted = security_client.policies.google_services_restricted
+ domain = security_client.provider.identity.domain
+
+ if restricted is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Application access to Google services is restricted "
+ f"in domain {domain}. At least one Google service has "
+ f"API access limited to trusted apps."
+ )
+ else:
+ report.status = "FAIL"
+ if restricted is None:
+ report.status_extended = (
+ f"Application access to Google services is not configured "
+ f"in domain {domain}. The default is unrestricted. "
+ f"API access should be restricted for all applicable "
+ f"Google services, particularly high-risk scopes."
+ )
+ else:
+ report.status_extended = (
+ f"Application access to Google services is unrestricted "
+ f"in domain {domain}. "
+ f"API access should be restricted for all applicable "
+ f"Google services, particularly high-risk scopes."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/security/security_client.py b/prowler/providers/googleworkspace/services/security/security_client.py
new file mode 100644
index 0000000000..5c8930edf1
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.security.security_service import (
+ Security,
+)
+
+security_client = Security(Provider.get_global_provider())
diff --git a/tests/providers/oraclecloud/services/identity/identity_password_policy_prevents_reuse/__init__.py b/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_password_policy_prevents_reuse/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.metadata.json b/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.metadata.json
new file mode 100644
index 0000000000..e19c3292b8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_dlp_drive_rules_configured",
+ "CheckTitle": "DLP policies for Google Drive are configured",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "At least one active **Data Loss Prevention (DLP) rule** targeting Google Drive file sharing is configured. DLP policies detect and prevent users from sharing sensitive information such as credit card numbers, identity numbers, and other regulated data through Drive.",
+ "Risk": "Without DLP policies, users can **freely share files containing sensitive information** through Google Drive without any detection or prevention controls. This increases the risk of **accidental data exposure, regulatory non-compliance**, and data breaches through oversharing.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/about-dlp",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Access and Data Control** > **Data protection**\n3. Click **Manage Rules**\n4. Click **ADD RULE** and select **New rule** or **New rule from template**\n5. Set the rule name and scope\n6. Set triggers by checking **File modified** under **Google Drive**\n7. Add conditions (Field, Comparison Operator, Content to match)\n8. Under **Actions**, select the desired action for each incident\n9. Under **Alerting**, set severity and select **Send to alert center**\n10. Click **Create**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure **DLP policies for Google Drive** to detect and prevent sharing of sensitive information such as credit card numbers, identity numbers, and other regulated data.",
+ "Url": "https://hub.prowler.com/check/security_dlp_drive_rules_configured"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.py b/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.py
new file mode 100644
index 0000000000..37304d0636
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_dlp_drive_rules_configured/security_dlp_drive_rules_configured.py
@@ -0,0 +1,50 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_dlp_drive_rules_configured(Check):
+ """Check that DLP policies for Google Drive are configured.
+
+ This check verifies that at least one active Data Loss Prevention (DLP)
+ rule targeting Google Drive file sharing exists, helping to prevent
+ unintended exposure of sensitive information.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ dlp_exists = security_client.policies.dlp_drive_rules_exist
+ domain = security_client.provider.identity.domain
+
+ if dlp_exists is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"DLP policies for Google Drive are configured "
+ f"in domain {domain}. At least one active DLP rule "
+ f"targeting Drive file sharing exists."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"No active DLP policies for Google Drive are configured "
+ f"in domain {domain}. DLP rules should be configured "
+ f"to detect and prevent sharing of sensitive information "
+ f"through Drive."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_service_level_admins_exist/__init__.py b/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_service_level_admins_exist/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.metadata.json b/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.metadata.json
new file mode 100644
index 0000000000..e4b055f6e1
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_internal_apps_trusted",
+ "CheckTitle": "Internal apps can access Google Workspace APIs",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level API controls configuration **trusts internal domain-owned apps** to access restricted Google Workspace APIs. This avoids the need to individually trust each internal app.",
+ "Risk": "When internal apps are not trusted, legitimate **organization-built applications** cannot access restricted Google Workspace API scopes, potentially **breaking internal workflows** and forcing administrators to trust each app individually, which increases administrative overhead.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/apps/control-which-apps-access-google-workspace-data",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Access and Data Control** > **API Controls**\n3. Click **App access control** > **Settings**\n4. Check **Trust internal, domain-owned apps**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **trust for internal domain-owned apps** so organization-built applications can access restricted Google Workspace APIs without individual trust configuration.",
+ "Url": "https://hub.prowler.com/check/security_internal_apps_trusted"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_app_access_restricted"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.py b/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.py
new file mode 100644
index 0000000000..8a62124125
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_internal_apps_trusted/security_internal_apps_trusted.py
@@ -0,0 +1,56 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_internal_apps_trusted(Check):
+ """Check that internal apps can access Google Workspace APIs.
+
+ This check verifies that the domain-level policy trusts internal
+ domain-owned apps, allowing them to access restricted Google Workspace
+ APIs without requiring individual trust configuration.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ trust_internal = security_client.policies.trust_internal_apps
+
+ if trust_internal is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Internal domain-owned apps are trusted to access "
+ f"Google Workspace APIs "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ elif trust_internal is None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Internal domain-owned apps use Google's secure default "
+ f"configuration (trusted) "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Internal domain-owned apps are not trusted to access "
+ f"Google Workspace APIs "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Internal apps should be trusted to access restricted APIs."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_tenancy_admin_permissions_limited/__init__.py b/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_tenancy_admin_permissions_limited/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.metadata.json b/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.metadata.json
new file mode 100644
index 0000000000..c6c2ff57e9
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_less_secure_apps_disabled",
+ "CheckTitle": "Less secure app access is disabled",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level policy **disables access to less secure apps** that do not use modern security standards such as OAuth. Blocking these apps helps keep user accounts and organizational data safe.",
+ "Risk": "When less secure app access is enabled, users can allow apps that use **basic authentication** (username and password only) to access their Google account. These apps are more vulnerable to **credential theft** and do not support 2-Step Verification, increasing the risk of account compromise.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/apps/control-access-to-less-secure-apps",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Access and Data Control** > **Less secure apps**\n3. Select **Disable access to less secure apps (Recommended)**\n4. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable **less secure app access** to prevent users from allowing apps that do not use modern authentication standards to access their accounts.",
+ "Url": "https://hub.prowler.com/check/security_less_secure_apps_disabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.py b/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.py
new file mode 100644
index 0000000000..a430f9d1e9
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_less_secure_apps_disabled/security_less_secure_apps_disabled.py
@@ -0,0 +1,56 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_less_secure_apps_disabled(Check):
+ """Check that less secure app access is disabled.
+
+ This check verifies that the domain-level policy prevents users from
+ allowing access to apps that use less secure sign-in technology,
+ reducing the risk of credential compromise.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ less_secure_allowed = security_client.policies.less_secure_apps_allowed
+
+ if less_secure_allowed is False:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Less secure app access is disabled "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ elif less_secure_allowed is None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Less secure app access uses Google's secure default "
+ f"configuration (disabled) "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Less secure app access is enabled "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Less secure app access should be disabled to prevent "
+ f"credential compromise through apps that do not use modern "
+ f"security standards."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_tenancy_admin_users_no_api_keys/__init__.py b/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_tenancy_admin_users_no_api_keys/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_login_challenges_configured/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.metadata.json b/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.metadata.json
new file mode 100644
index 0000000000..ec945474fc
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_login_challenges_configured",
+ "CheckTitle": "Login challenges are configured correctly",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level login challenges configuration has the **employee ID challenge disabled**. CIS 4.1.4.1 also requires Post-SSO verification to be enabled, but that setting is **not exposed by the Cloud Identity Policy API**. This check only covers the employee ID challenge portion of the control.",
+ "Risk": "When the employee ID login challenge is enabled without proper configuration, it may create a **false sense of security** or interfere with the login flow. The employee ID challenge is a supplementary verification method that should only be used when specifically required by the organization.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/protect-google-workspace-accounts-with-security-challenges",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Login Challenges**\n3. Under **Login challenges**, uncheck **Use employee ID to keep my users more secure**\n4. Click **Save**\n5. Under **Post-SSO verification**, check **Logins using SSO are subject to additional verifications (if appropriate) and 2-Step Verification (if configured)** (this setting cannot be verified via the Policy API)\n6. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable the **employee ID login challenge** and manually verify that **Post-SSO verification** is enabled in the Admin Console, as the Post-SSO setting is not exposed by the Policy API.",
+ "Url": "https://hub.prowler.com/check/security_login_challenges_configured"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_2sv_enforced"
+ ],
+ "Notes": "This check is partial — it only verifies the employee ID challenge setting. CIS 4.1.4.1 also requires Post-SSO verification to be enabled, which is not exposed by the Cloud Identity Policy API and must be verified manually."
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.py b/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.py
new file mode 100644
index 0000000000..e3732053b8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_login_challenges_configured/security_login_challenges_configured.py
@@ -0,0 +1,62 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_login_challenges_configured(Check):
+ """Check that login challenges are configured correctly.
+
+ This check verifies that the employee ID login challenge is disabled,
+ as recommended by CIS. Note: CIS 4.1.4.1 also requires Post-SSO
+ verification to be enabled, but that setting is not exposed by the
+ Cloud Identity Policy API. This check only covers the employee ID
+ challenge portion of the control.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ employee_id_enabled = security_client.policies.login_challenge_employee_id
+
+ if employee_id_enabled is False:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Employee ID login challenge is disabled "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Note: Post-SSO verification status cannot be verified "
+ f"via the Policy API."
+ )
+ elif employee_id_enabled is None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Employee ID login challenge uses Google's secure default "
+ f"configuration (disabled) "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Note: Post-SSO verification status cannot be verified "
+ f"via the Policy API."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Employee ID login challenge is enabled "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"The employee ID challenge should be disabled per CIS "
+ f"recommendations. Note: Post-SSO verification status "
+ f"cannot be verified via the Policy API."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_api_keys_rotated_90_days/__init__.py b/prowler/providers/googleworkspace/services/security/security_password_policy_strong/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_api_keys_rotated_90_days/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_password_policy_strong/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.metadata.json b/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.metadata.json
new file mode 100644
index 0000000000..776c9745e8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_password_policy_strong",
+ "CheckTitle": "Password policy is configured for enhanced security",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level password policy is configured with **enhanced security settings**: minimum length of 14 characters, strong passwords enforced, password reuse disallowed, enforcement at next sign-in enabled, and password expiration set to 365 days.",
+ "Risk": "Weak password policies allow users to set **short, simple, or previously compromised passwords** that are vulnerable to brute-force attacks, credential stuffing, and password spraying. Without enforcement at sign-in, users may continue using weak passwords indefinitely.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/users/enforce-and-monitor-password-requirements-for-users",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Password management**\n3. Under **Strength**, check **Enforce strong passwords**\n4. Under **Length**, set **Minimum Length** to **14** or greater\n5. Under **Strength and Length enforcement**, check **Enforce password policy at next sign-in**\n6. Under **Reuse**, uncheck **Allow password reuse**\n7. Under **Expiration**, set **Password reset frequency** to **365 Days**\n8. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure a **strong password policy** with minimum 14-character length, strong password enforcement, reuse prevention, enforcement at next sign-in, and annual password expiration.",
+ "Url": "https://hub.prowler.com/check/security_password_policy_strong"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.py b/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.py
new file mode 100644
index 0000000000..33448aa536
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_password_policy_strong/security_password_policy_strong.py
@@ -0,0 +1,76 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_password_policy_strong(Check):
+ """Check that password policy is configured for enhanced security.
+
+ This check verifies that the domain-level password policy meets CIS
+ requirements: minimum length of 14 characters, strong passwords enforced,
+ password reuse disallowed, enforcement at next sign-in, and password
+ expiration configured.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ policies = security_client.policies
+ domain = security_client.provider.identity.domain
+ issues = []
+
+ min_length = policies.password_minimum_length
+ if min_length is None or min_length < 14:
+ issues.append(
+ "minimum length is not configured (requires 14+)"
+ if min_length is None
+ else f"minimum length is {min_length} (requires 14+)"
+ )
+
+ if policies.password_allowed_strength != "STRONG":
+ issues.append(
+ "password strength is not configured (requires STRONG)"
+ if policies.password_allowed_strength is None
+ else f"password strength is {policies.password_allowed_strength} (requires STRONG)"
+ )
+
+ if policies.password_allow_reuse is True:
+ issues.append("password reuse is allowed")
+
+ if policies.password_enforce_at_login is not True:
+ issues.append("password policy is not enforced at next sign-in")
+
+ expiration = policies.password_expiration_duration
+ if expiration is None or expiration == "0s":
+ issues.append("password expiration is not configured")
+
+ if not issues:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Password policy meets CIS requirements "
+ f"in domain {domain}: minimum length {min_length}, "
+ f"strong passwords enforced, reuse disallowed, "
+ f"enforced at next sign-in, expiration configured."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Password policy does not meet CIS requirements "
+ f"in domain {domain}: {'; '.join(issues)}."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/googleworkspace/services/security/security_service.py b/prowler/providers/googleworkspace/services/security/security_service.py
new file mode 100644
index 0000000000..96f24061f8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_service.py
@@ -0,0 +1,281 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+
+class Security(GoogleWorkspaceService):
+ """Google Workspace Security service for auditing domain-level security policies.
+
+ Uses the Cloud Identity Policy API v1 to read authentication, password,
+ session, recovery, API control, and DLP settings configured in the
+ Admin Console.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.policies = SecurityPolicies()
+ self.policies_fetched = False
+ self._fetch_security_policies()
+
+ def _fetch_security_policies(self):
+ """Fetch security policies from the Cloud Identity Policy API v1."""
+ logger.info("Security - Fetching security policies...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ fetch_succeeded = True
+
+ # Fetch 1: security.* settings
+ fetch_succeeded = self._fetch_namespace(
+ service, 'setting.type.matches("security.*")', fetch_succeeded
+ )
+
+ # Fetch 2: api_controls.* settings
+ fetch_succeeded = self._fetch_namespace(
+ service, 'setting.type.matches("api_controls.*")', fetch_succeeded
+ )
+
+ # Fetch 3: rule.dlp for DLP existence check
+ fetch_succeeded = self._fetch_namespace(
+ service, 'setting.type.matches("rule.dlp")', fetch_succeeded
+ )
+
+ self.policies_fetched = fetch_succeeded
+
+ if fetch_succeeded:
+ logger.info("Security policies fetched successfully.")
+ else:
+ logger.warning(
+ "Security policies fetched with partial failures; "
+ "some checks may be skipped."
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching security policies",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+ def _fetch_namespace(self, service, filter_str: str, fetch_succeeded: bool) -> bool:
+ """Fetch policies for a single namespace filter."""
+ try:
+ request = service.policies().list(
+ pageSize=100,
+ filter=filter_str,
+ )
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ setting_type = setting.get("type", "").removeprefix("settings/")
+ value = setting.get("value", {})
+
+ self._process_setting(setting_type, value)
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ f"fetching policies with filter {filter_str}",
+ self.provider.identity.customer_id,
+ )
+ return False
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ f"listing policies with filter {filter_str}",
+ self.provider.identity.customer_id,
+ )
+ return False
+
+ return fetch_succeeded
+
+ def _process_setting(self, setting_type: str, value: dict):
+ """Process a single policy setting and populate the model."""
+
+ # 2-Step Verification settings
+ if setting_type == "security.two_step_verification_enrollment":
+ self.policies.two_sv_allow_enrollment = value.get("allowEnrollment")
+ logger.debug(f"2SV enrollment: {self.policies.two_sv_allow_enrollment}")
+
+ elif setting_type == "security.two_step_verification_enforcement":
+ self.policies.two_sv_enforced_from = value.get("enforcedFrom")
+ logger.debug(f"2SV enforcement: {self.policies.two_sv_enforced_from}")
+
+ elif setting_type == "security.two_step_verification_enforcement_factor":
+ self.policies.two_sv_allowed_factor_set = value.get(
+ "allowedSignInFactorSet"
+ )
+ logger.debug(f"2SV factor set: {self.policies.two_sv_allowed_factor_set}")
+
+ elif setting_type == "security.two_step_verification_device_trust":
+ self.policies.two_sv_allow_trusting_device = value.get(
+ "allowTrustingDevice"
+ )
+ logger.debug(
+ f"2SV device trust: {self.policies.two_sv_allow_trusting_device}"
+ )
+
+ elif setting_type == "security.two_step_verification_grace_period":
+ self.policies.two_sv_enrollment_grace_period = value.get(
+ "enrollmentGracePeriod"
+ )
+ logger.debug(
+ f"2SV grace period: {self.policies.two_sv_enrollment_grace_period}"
+ )
+
+ elif setting_type == "security.two_step_verification_sign_in_code":
+ self.policies.two_sv_backup_code_exception_period = value.get(
+ "backupCodeExceptionPeriod"
+ )
+ logger.debug(
+ f"2SV backup code period: {self.policies.two_sv_backup_code_exception_period}"
+ )
+
+ # Account recovery
+ elif setting_type == "security.super_admin_account_recovery":
+ self.policies.super_admin_recovery_enabled = value.get(
+ "enableAccountRecovery"
+ )
+ logger.debug(
+ f"Super admin recovery: {self.policies.super_admin_recovery_enabled}"
+ )
+
+ elif setting_type == "security.user_account_recovery":
+ self.policies.user_recovery_enabled = value.get("enableAccountRecovery")
+ logger.debug(f"User recovery: {self.policies.user_recovery_enabled}")
+
+ # Advanced Protection Program
+ elif setting_type == "security.advanced_protection_program":
+ self.policies.advanced_protection_enrollment = value.get(
+ "enableAdvancedProtectionSelfEnrollment"
+ )
+ self.policies.advanced_protection_security_code_option = value.get(
+ "securityCodeOption"
+ )
+ logger.debug("Advanced Protection Program settings fetched.")
+
+ # Login challenges
+ elif setting_type == "security.login_challenges":
+ self.policies.login_challenge_employee_id = value.get(
+ "enableEmployeeIdChallenge"
+ )
+ logger.debug("Login challenges settings fetched.")
+
+ # Password policy
+ elif setting_type == "security.password":
+ self.policies.password_minimum_length = value.get("minimumLength")
+ self.policies.password_maximum_length = value.get("maximumLength")
+ self.policies.password_allowed_strength = value.get("allowedStrength")
+ self.policies.password_allow_reuse = value.get("allowReuse")
+ self.policies.password_enforce_at_login = value.get(
+ "enforceRequirementsAtLogin"
+ )
+ self.policies.password_expiration_duration = value.get("expirationDuration")
+ logger.debug("Password policy settings fetched.")
+
+ # Less secure apps
+ elif setting_type == "security.less_secure_apps":
+ self.policies.less_secure_apps_allowed = value.get("allowLessSecureApps")
+ logger.debug(f"Less secure apps: {self.policies.less_secure_apps_allowed}")
+
+ # Session controls
+ elif setting_type == "security.session_controls":
+ self.policies.web_session_duration = value.get("webSessionDuration")
+ logger.debug(f"Web session duration: {self.policies.web_session_duration}")
+
+ # Passkeys restriction
+ elif setting_type == "security.passkeys_restriction":
+ self.policies.passkeys_type = value.get("allowedPasskeysType")
+ logger.debug(f"Passkeys type: {self.policies.passkeys_type}")
+
+ # API controls - internal apps
+ elif setting_type == "api_controls.internal_apps":
+ self.policies.trust_internal_apps = value.get("trustInternalApps")
+ logger.debug(f"Trust internal apps: {self.policies.trust_internal_apps}")
+
+ # API controls - google services
+ elif setting_type == "api_controls.google_services":
+ services = value.get("services", [])
+ for svc in services:
+ if svc.get("isEnabled") is False:
+ self.policies.google_services_restricted = True
+ break
+ if self.policies.google_services_restricted is None:
+ self.policies.google_services_restricted = False
+ logger.debug(
+ f"Google services restricted: {self.policies.google_services_restricted}"
+ )
+
+ # DLP rules
+ elif setting_type == "rule.dlp":
+ state = value.get("state")
+ triggers = value.get("triggers", [])
+ if state == "ACTIVE" and any(
+ trigger.startswith("google.workspace.drive.") for trigger in triggers
+ ):
+ self.policies.dlp_drive_rules_exist = True
+ logger.debug(f"DLP rule: state={state}, triggers={triggers}")
+
+
+class SecurityPolicies(BaseModel):
+ """Model for domain-level Security policy settings."""
+
+ # security.two_step_verification_enrollment
+ two_sv_allow_enrollment: Optional[bool] = None
+ # security.two_step_verification_enforcement
+ two_sv_enforced_from: Optional[str] = None
+ # security.two_step_verification_enforcement_factor
+ two_sv_allowed_factor_set: Optional[str] = None
+ # security.two_step_verification_device_trust
+ two_sv_allow_trusting_device: Optional[bool] = None
+ # security.two_step_verification_grace_period
+ two_sv_enrollment_grace_period: Optional[str] = None
+ # security.two_step_verification_sign_in_code
+ two_sv_backup_code_exception_period: Optional[str] = None
+ # security.super_admin_account_recovery
+ super_admin_recovery_enabled: Optional[bool] = None
+ # security.user_account_recovery
+ user_recovery_enabled: Optional[bool] = None
+ # security.advanced_protection_program
+ advanced_protection_enrollment: Optional[bool] = None
+ advanced_protection_security_code_option: Optional[str] = None
+ # security.login_challenges
+ login_challenge_employee_id: Optional[bool] = None
+ # security.password
+ password_minimum_length: Optional[int] = None
+ password_maximum_length: Optional[int] = None
+ password_allowed_strength: Optional[str] = None
+ password_allow_reuse: Optional[bool] = None
+ password_enforce_at_login: Optional[bool] = None
+ password_expiration_duration: Optional[str] = None
+ # security.less_secure_apps
+ less_secure_apps_allowed: Optional[bool] = None
+ # security.session_controls
+ web_session_duration: Optional[str] = None
+ # security.passkeys_restriction
+ passkeys_type: Optional[str] = None
+ # api_controls.internal_apps
+ trust_internal_apps: Optional[bool] = None
+ # api_controls.google_services
+ google_services_restricted: Optional[bool] = None
+ # rule.dlp
+ dlp_drive_rules_exist: Optional[bool] = None
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_auth_tokens_rotated_90_days/__init__.py b/prowler/providers/googleworkspace/services/security/security_session_duration_limited/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_auth_tokens_rotated_90_days/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_session_duration_limited/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.metadata.json b/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.metadata.json
new file mode 100644
index 0000000000..83e89527d8
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_session_duration_limited",
+ "CheckTitle": "Google session control is configured to 12 hours or less",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level Google session control limits web session duration to **12 hours or less**. When a session expires, users must re-authenticate, reducing the window of opportunity for session hijacking.",
+ "Risk": "The default 14-day session duration means that a compromised session token provides an attacker with **two weeks of uninterrupted access** without re-authentication. Shorter session durations limit the impact of **stolen cookies, session hijacking, and unauthorized access** from shared or untrusted devices.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/security/set-session-length-for-google-services",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Access and Data Control** > **Google session control**\n3. Set **Web session duration** to **12 hours** or less\n4. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set **Google session control** web session duration to **12 hours or less** to limit the window of access from compromised sessions.",
+ "Url": "https://hub.prowler.com/check/security_session_duration_limited"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.py b/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.py
new file mode 100644
index 0000000000..1b72310ee6
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_session_duration_limited/security_session_duration_limited.py
@@ -0,0 +1,75 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+MAX_SESSION_DURATION_SECONDS = 43200 # 12 hours
+
+
+class security_session_duration_limited(Check):
+ """Check that Google session control is configured to 12 hours or less.
+
+ This check verifies that the domain-level web session duration is set
+ to 12 hours or less, requiring users to re-authenticate more frequently
+ than the default 14-day session length.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ duration_str = security_client.policies.web_session_duration
+ domain = security_client.provider.identity.domain
+
+ if duration_str is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Google session control is not explicitly configured "
+ f"in domain {domain}. The default is 14 days. "
+ f"Web session duration should be 12 hours or less."
+ )
+ findings.append(report)
+ return findings
+
+ try:
+ duration_seconds = int(duration_str.removesuffix("s"))
+ except ValueError:
+ logger.error(f"Unparseable web session duration: {duration_str!r}")
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Web session duration value {duration_str!r} is not parseable "
+ f"in domain {domain}."
+ )
+ findings.append(report)
+ return findings
+
+ duration_hours = duration_seconds / 3600
+
+ if duration_seconds <= MAX_SESSION_DURATION_SECONDS:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Google session control is set to {duration_hours:.0f} hours "
+ f"in domain {domain}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Google session control is set to {duration_hours:.0f} hours "
+ f"in domain {domain}. "
+ f"Web session duration should be 12 hours or less."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_customer_secret_keys_rotated_90_days/__init__.py b/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_customer_secret_keys_rotated_90_days/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.metadata.json b/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.metadata.json
new file mode 100644
index 0000000000..540faddac9
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_super_admin_recovery_disabled",
+ "CheckTitle": "Super Admin account recovery is disabled",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level policy **disables self-service account recovery for Super Admin accounts**. When disabled, Super Admins cannot use recovery options (phone, email) to regain access, reducing the risk of account takeover through compromised recovery channels.",
+ "Risk": "If Super Admin account recovery is enabled, an attacker who compromises a Super Admin's **recovery phone or email** could use the self-service recovery flow to take over the account, gaining **full administrative control** over the entire Google Workspace organization.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/users/allow-super-administrators-to-recover-their-password",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Authentication** > **Account recovery**\n3. Select **Super admin account recovery**\n4. Uncheck **Allow super admins to recover their account**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable **Super Admin account recovery** to prevent attackers from exploiting the self-service recovery flow to take over privileged accounts.",
+ "Url": "https://hub.prowler.com/check/security_super_admin_recovery_disabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_user_recovery_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.py b/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.py
new file mode 100644
index 0000000000..5c201e7b5d
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_super_admin_recovery_disabled/security_super_admin_recovery_disabled.py
@@ -0,0 +1,55 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_super_admin_recovery_disabled(Check):
+ """Check that Super Admin account recovery is disabled.
+
+ This check verifies that the domain-level policy prevents Super Admin
+ users from recovering their account through self-service, reducing the
+ risk of account takeover through the recovery flow.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ recovery_enabled = security_client.policies.super_admin_recovery_enabled
+
+ if recovery_enabled is False:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Super Admin account recovery is disabled "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ elif recovery_enabled is None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Super Admin account recovery uses Google's secure default "
+ f"configuration (disabled) "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Super Admin account recovery is enabled "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"Super Admin account recovery should be disabled to prevent "
+ f"account takeover through the recovery flow."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_db_passwords_rotated_90_days/__init__.py b/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_db_passwords_rotated_90_days/__init__.py
rename to prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/__init__.py
diff --git a/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.metadata.json b/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.metadata.json
new file mode 100644
index 0000000000..0a2de745db
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "security_user_recovery_enabled",
+ "CheckTitle": "User account recovery is enabled",
+ "CheckType": [],
+ "ServiceName": "security",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The domain-level policy **enables self-service account recovery for non-Super Admin users**. When enabled, users can recover access to their accounts if their password is forgotten, reducing helpdesk burden and downtime.",
+ "Risk": "When user account recovery is disabled, users who lose access to their accounts must **contact an administrator** to regain access. This increases helpdesk burden, extends downtime, and may lead to users adopting **insecure workarounds** like sharing credentials.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/users/set-up-password-recovery-for-users",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Security** > **Authentication** > **Account recovery**\n3. Select **User account recovery**\n4. Check **Allow users and non-super admins to recover their account**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable **user account recovery** to allow non-admin users to regain access to their accounts through self-service, reducing helpdesk burden and user downtime.",
+ "Url": "https://hub.prowler.com/check/security_user_recovery_enabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "security_super_admin_recovery_disabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.py b/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.py
new file mode 100644
index 0000000000..99aabcb842
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/security/security_user_recovery_enabled/security_user_recovery_enabled.py
@@ -0,0 +1,56 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.security.security_client import (
+ security_client,
+)
+
+
+class security_user_recovery_enabled(Check):
+ """Check that user account recovery is enabled.
+
+ This check verifies that the domain-level policy allows non-Super Admin
+ users to recover their accounts through self-service, reducing helpdesk
+ burden while maintaining access to their accounts.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if security_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=security_client.policies,
+ resource_id="securityPolicies",
+ resource_name="Security Policies",
+ customer_id=security_client.provider.identity.customer_id,
+ )
+
+ recovery_enabled = security_client.policies.user_recovery_enabled
+
+ if recovery_enabled is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"User account recovery is enabled "
+ f"in domain {security_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if recovery_enabled is None:
+ report.status_extended = (
+ f"User account recovery is not explicitly configured "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"The default is disabled. User account recovery should be "
+ f"enabled to reduce helpdesk burden."
+ )
+ else:
+ report.status_extended = (
+ f"User account recovery is disabled "
+ f"in domain {security_client.provider.identity.domain}. "
+ f"User account recovery should be enabled to reduce "
+ f"helpdesk burden."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_mfa_enabled_console_access/__init__.py b/prowler/providers/googleworkspace/services/sites/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_mfa_enabled_console_access/__init__.py
rename to prowler/providers/googleworkspace/services/sites/__init__.py
diff --git a/prowler/providers/googleworkspace/services/sites/sites_client.py b/prowler/providers/googleworkspace/services/sites/sites_client.py
new file mode 100644
index 0000000000..d57e537c5d
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/sites/sites_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.googleworkspace.services.sites.sites_service import (
+ Sites,
+)
+
+sites_client = Sites(Provider.get_global_provider())
diff --git a/prowler/providers/googleworkspace/services/sites/sites_service.py b/prowler/providers/googleworkspace/services/sites/sites_service.py
new file mode 100644
index 0000000000..456c2aca65
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/sites/sites_service.py
@@ -0,0 +1,88 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.googleworkspace.lib.service.service import GoogleWorkspaceService
+
+
+class Sites(GoogleWorkspaceService):
+ """Google Workspace Sites service for auditing domain-level Sites policies.
+
+ Uses the Cloud Identity Policy API v1 to read the Sites service status
+ configured in the Admin Console.
+ """
+
+ def __init__(self, provider):
+ super().__init__(provider)
+ self.policies = SitesPolicies()
+ self.policies_fetched = False
+ self._fetch_sites_policies()
+
+ def _fetch_sites_policies(self):
+ """Fetch Sites policies from the Cloud Identity Policy API v1."""
+ logger.info("Sites - Fetching sites policies...")
+
+ try:
+ service = self._build_service("cloudidentity", "v1")
+
+ if not service:
+ logger.error("Failed to build Cloud Identity service")
+ return
+
+ request = service.policies().list(
+ pageSize=100,
+ filter='setting.type.matches("sites.*")',
+ )
+ fetch_succeeded = True
+
+ while request is not None:
+ try:
+ response = request.execute()
+
+ for policy in response.get("policies", []):
+ if not self._is_customer_level_policy(policy):
+ continue
+
+ setting = policy.get("setting", {})
+ setting_type = setting.get("type", "").removeprefix("settings/")
+ value = setting.get("value", {})
+
+ if setting_type == "sites.service_status":
+ self.policies.service_state = value.get("serviceState")
+ logger.debug(
+ "Sites service state: " f"{self.policies.service_state}"
+ )
+
+ request = service.policies().list_next(request, response)
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Sites policies",
+ self.provider.identity.customer_id,
+ )
+ fetch_succeeded = False
+ break
+
+ self.policies_fetched = fetch_succeeded
+
+ logger.info(
+ f"Sites policies fetched - "
+ f"Service state: {self.policies.service_state}"
+ )
+
+ except Exception as error:
+ self._handle_api_error(
+ error,
+ "fetching Sites policies",
+ self.provider.identity.customer_id,
+ )
+ self.policies_fetched = False
+
+
+class SitesPolicies(BaseModel):
+ """Model for domain-level Sites policy settings."""
+
+ # sites.service_status
+ service_state: Optional[str] = None
diff --git a/tests/providers/oraclecloud/services/identity/identity_user_valid_email_address/__init__.py b/prowler/providers/googleworkspace/services/sites/sites_service_disabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/identity/identity_user_valid_email_address/__init__.py
rename to prowler/providers/googleworkspace/services/sites/sites_service_disabled/__init__.py
diff --git a/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.metadata.json b/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.metadata.json
new file mode 100644
index 0000000000..3871b358a2
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "googleworkspace",
+ "CheckID": "sites_service_disabled",
+ "CheckTitle": "Service status for Google Sites is set to off",
+ "CheckType": [],
+ "ServiceName": "sites",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "The domain-wide Google Sites configuration has the service **disabled for all users**. Google Sites allows users to create internal and external websites, which may expose sensitive information or create unmanaged content outside the organization's control.",
+ "Risk": "When Google Sites is enabled, users can create websites that may **inadvertently expose internal information** to external parties. These sites can be difficult to track and manage, creating potential **data leakage vectors** outside the organization's standard content management controls.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://knowledge.workspace.google.com/admin/users/advanced/turn-a-service-on-or-off-for-google-workspace-users",
+ "https://docs.cloud.google.com/identity/docs/concepts/supported-policy-api-settings"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Google **Admin console** at https://admin.google.com\n2. Navigate to **Apps** > **Google Workspace** > **Sites**\n3. Click **Service status**\n4. Select **OFF for everyone**\n5. Click **Save**",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Disable **Google Sites** for all users to reduce the organization's attack surface. If specific users require access, enable it by exception for those users or groups only.",
+ "Url": "https://hub.prowler.com/check/sites_service_disabled"
+ }
+ },
+ "Categories": [
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.py b/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.py
new file mode 100644
index 0000000000..2acd84fb7c
--- /dev/null
+++ b/prowler/providers/googleworkspace/services/sites/sites_service_disabled/sites_service_disabled.py
@@ -0,0 +1,52 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportGoogleWorkspace
+from prowler.providers.googleworkspace.services.sites.sites_client import sites_client
+
+
+class sites_service_disabled(Check):
+ """Check that the Google Sites service is disabled for all users.
+
+ This check verifies that the domain-level policy disables the Google Sites
+ service, reducing the organization's attack surface by preventing users
+ from creating internal or external websites.
+ """
+
+ def execute(self) -> List[CheckReportGoogleWorkspace]:
+ findings = []
+
+ if sites_client.policies_fetched:
+ report = CheckReportGoogleWorkspace(
+ metadata=self.metadata(),
+ resource=sites_client.policies,
+ resource_id="sitesPolicies",
+ resource_name="Sites Policies",
+ customer_id=sites_client.provider.identity.customer_id,
+ )
+
+ service_state = sites_client.policies.service_state
+
+ if service_state == "DISABLED":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Google Sites service is disabled "
+ f"in domain {sites_client.provider.identity.domain}."
+ )
+ else:
+ report.status = "FAIL"
+ if service_state is None:
+ report.status_extended = (
+ f"Google Sites service is not explicitly configured "
+ f"in domain {sites_client.provider.identity.domain}. "
+ f"The default is ON for everyone. Google Sites should be disabled."
+ )
+ else:
+ report.status_extended = (
+ f"Google Sites service is enabled "
+ f"in domain {sites_client.provider.identity.domain}. "
+ f"Google Sites should be disabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/iac/iac_provider.py b/prowler/providers/iac/iac_provider.py
index b91fdf070e..df9114e033 100644
--- a/prowler/providers/iac/iac_provider.py
+++ b/prowler/providers/iac/iac_provider.py
@@ -28,6 +28,7 @@ from prowler.providers.common.provider import Provider
class IacProvider(Provider):
_type: str = "iac"
+ sdk_only: bool = False
audit_metadata: Audit_Metadata
def __init__(
diff --git a/prowler/providers/image/image_provider.py b/prowler/providers/image/image_provider.py
index b142240867..7a245e4125 100644
--- a/prowler/providers/image/image_provider.py
+++ b/prowler/providers/image/image_provider.py
@@ -59,6 +59,7 @@ class ImageProvider(Provider):
"""
_type: str = "image"
+ sdk_only: bool = False
FINDING_BATCH_SIZE: int = 100
MAX_IMAGE_LIST_LINES: int = 10_000
MAX_IMAGE_NAME_LENGTH: int = 500
diff --git a/prowler/providers/kubernetes/kubernetes_provider.py b/prowler/providers/kubernetes/kubernetes_provider.py
index 2572b5be88..b350a18ebc 100644
--- a/prowler/providers/kubernetes/kubernetes_provider.py
+++ b/prowler/providers/kubernetes/kubernetes_provider.py
@@ -58,6 +58,7 @@ class KubernetesProvider(Provider):
"""
_type: str = "kubernetes"
+ sdk_only: bool = False
_session: KubernetesSession
_namespaces: list
_audit_config: dict
diff --git a/tests/providers/oraclecloud/services/integration/__init__.py b/prowler/providers/kubernetes/services/core/core_cpu_limits_set/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/integration/__init__.py
rename to prowler/providers/kubernetes/services/core/core_cpu_limits_set/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.metadata.json b/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.metadata.json
new file mode 100644
index 0000000000..5831cb2abd
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.metadata.json
@@ -0,0 +1,35 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_cpu_limits_set",
+ "CheckTitle": "Pod containers have CPU limits set",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "KubernetesPod",
+ "Description": "Ensure CPU limits are set for containers to prevent noisy neighbors and resource exhaustion.",
+ "Risk": "Missing CPU limits can allow containers to consume unbounded CPU leading to performance issues.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl set resources deployment/<name> -n <namespace> --containers=<container> --limits=cpu=500m",
+ "NativeIaC": "# Example: set cpu limits in container resources\nresources:\n limits:\n cpu: \"500m\"",
+ "Other": "1. Edit the Pod/Deployment manifest and set `resources.limits.cpu` for each container.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Define CPU limits to bound a container's CPU usage and protect node stability.",
+ "Url": "https://hub.prowler.com/check/core_cpu_limits_set"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Limits should be tuned per workload and monitored."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.py b/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.py
new file mode 100644
index 0000000000..8f22fa6b28
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_cpu_limits_set/core_cpu_limits_set.py
@@ -0,0 +1,35 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_cpu_limits_set(Check):
+ """Check whether regular pod containers have CPU limits configured."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the Kubernetes pod CPU limits check.
+
+ Returns:
+ List of check reports for Kubernetes pods.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Pod {pod.name} regular containers have CPU limits configured."
+ )
+
+ for container in (pod.containers or {}).values():
+ resources = container.resources or {}
+ limits = (
+ resources.get("limits") if isinstance(resources, dict) else None
+ )
+ cpu = limits.get("cpu") if limits and isinstance(limits, dict) else None
+ if not cpu:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} container {container.name} does not have a CPU limit configured."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/integration/integration_instance_access_restricted/__init__.py b/prowler/providers/kubernetes/services/core/core_cpu_requests_set/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/integration/integration_instance_access_restricted/__init__.py
rename to prowler/providers/kubernetes/services/core/core_cpu_requests_set/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.metadata.json b/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.metadata.json
new file mode 100644
index 0000000000..9f3972e271
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.metadata.json
@@ -0,0 +1,35 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_cpu_requests_set",
+ "CheckTitle": "Pod containers have CPU requests set",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "KubernetesPod",
+ "Description": "Ensure CPU requests are set for containers to enable proper scheduling and resource guarantees.",
+ "Risk": "Missing CPU requests can lead to scheduling and resource contention issues.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl set resources deployment/<name> -n <namespace> --containers=<container> --requests=cpu=100m",
+ "NativeIaC": "# Example: set cpu requests in container resources\nresources:\n requests:\n cpu: \"100m\"",
+ "Other": "1. Edit the Pod/Deployment manifest and set `resources.requests.cpu` for each container.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Define sensible CPU requests to enable efficient scheduling and fair resource allocation.",
+ "Url": "https://hub.prowler.com/check/core_cpu_requests_set"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Requests should be tuned per workload and cluster capacity."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.py b/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.py
new file mode 100644
index 0000000000..6e7f9f8020
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_cpu_requests_set/core_cpu_requests_set.py
@@ -0,0 +1,39 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_cpu_requests_set(Check):
+ """Check whether regular pod containers have CPU requests configured."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the Kubernetes pod CPU requests check.
+
+ Returns:
+ List of check reports for Kubernetes pods.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Pod {pod.name} regular containers have CPU requests configured."
+ )
+
+ for container in (pod.containers or {}).values():
+ resources = container.resources or {}
+ requests = (
+ resources.get("requests") if isinstance(resources, dict) else None
+ )
+ cpu = (
+ requests.get("cpu")
+ if requests and isinstance(requests, dict)
+ else None
+ )
+ if not cpu:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} container {container.name} does not have a CPU request configured."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/kms/__init__.py b/prowler/providers/kubernetes/services/core/core_image_tag_fixed/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/kms/__init__.py
rename to prowler/providers/kubernetes/services/core/core_image_tag_fixed/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.metadata.json b/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.metadata.json
new file mode 100644
index 0000000000..3a395caad1
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_image_tag_fixed",
+ "CheckTitle": "Container images use fixed tags",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Pod",
+ "ResourceGroup": "container",
+ "Description": "**Kubernetes Pods** are evaluated for containers using images without a **fixed version tag**, such as `latest` or no tag at all, which results in unpredictable image versions being pulled.",
+ "Risk": "Using **`latest` or untagged images** breaks reproducibility and introduces risk:\n- Deployments may pull different image versions across nodes (integrity)\n- Rollbacks become unreliable when the exact image is unknown\n- Supply-chain attacks can inject malicious code via mutable tags\nCompromised or unexpected images can lead to **data breaches**, **lateral movement**, and **service disruption**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/containers/images/",
+ "https://kubernetes.io/docs/concepts/configuration/overview/#container-images"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl set image deployment/<workload-name> <container-name>=<image>:<fixed-version> -n <namespace>\n# Example: kubectl set image deployment/nginx nginx=nginx:1.25.3 -n default\n# For maximum immutability, use an image digest instead: <image>@sha256:<digest>",
+ "NativeIaC": "",
+ "Other": "1. Open your Kubernetes UI (e.g., cloud provider console or Dashboard)\n2. Navigate to the failing workload (Deployment/StatefulSet/DaemonSet) or Pod and choose Edit YAML/Manifest\n3. Update the image field for each affected container to include a specific version tag or digest:\n - Example: change `nginx` or `nginx:latest` to `nginx:1.25.3` or `nginx@sha256:<digest>`\n4. Save changes (controllers will roll out new Pods). If it is a standalone Pod, delete and recreate it to apply the change",
+ "Terraform": "```hcl\nresource \"kubernetes_pod\" \"<example_resource_name>\" {\n metadata { name = \"<example_resource_name>\" }\n spec {\n container {\n name = \"<example_resource_name>\"\n image = \"nginx:1.25.3\" # Critical: use a fixed version tag, never 'latest' or untagged\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Pin all container images to a **specific version tag** or **digest** (`@sha256:...`) to ensure reproducible, auditable deployments.\n\n- Avoid `latest` and untagged images in production\n- Use **image digests** for maximum immutability\n- Enforce tag policies with **admission controllers** (e.g., OPA Gatekeeper, Kyverno)\n- Integrate image scanning into CI/CD pipelines for **defense in depth**",
+ "Url": "https://hub.prowler.com/check/core_image_tag_fixed"
+ }
+ },
+ "Categories": [
+ "container-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Using fixed image tags ensures reproducible deployments and reduces supply-chain attack surface."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.py b/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.py
new file mode 100644
index 0000000000..5167d09f2c
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_image_tag_fixed/core_image_tag_fixed.py
@@ -0,0 +1,50 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+def _has_fixed_image_tag(image: str) -> bool:
+ if "@" in image:
+ return True
+
+ image_name = image.rsplit("/", 1)[-1]
+ if ":" not in image_name:
+ return False
+
+ tag = image_name.rsplit(":", 1)[-1]
+ return bool(tag) and tag.lower() != "latest"
+
+
+class core_image_tag_fixed(Check):
+ """Ensure that image tag is not set to latest or blank."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports containing the result of the check.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Pod {pod.name} has fixed image tags on all containers."
+ )
+
+ for containers in (
+ pod.containers,
+ pod.init_containers,
+ pod.ephemeral_containers,
+ ):
+ for container in (containers or {}).values():
+ image = container.image
+ if not _has_fixed_image_tag(image):
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} has container {container.name} with image '{image}' that does not use a fixed tag."
+ break
+ if report.status == "FAIL":
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/kms/kms_key_rotation_enabled/__init__.py b/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/kms/kms_key_rotation_enabled/__init__.py
rename to prowler/providers/kubernetes/services/core/core_liveness_probe_configured/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.metadata.json b/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.metadata.json
new file mode 100644
index 0000000000..668551bca4
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_liveness_probe_configured",
+ "CheckTitle": "Pod containers have liveness probes configured",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "KubernetesPod",
+ "Description": "Ensure each regular pod container has a liveness probe configured to detect and restart unhealthy containers.",
+ "Risk": "Without liveness probes, failed containers may remain running causing degraded service or resource waste.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/",
+ "https://sre.google/workbook/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl patch deployment/<name> -n <namespace> --type='json' -p='[{\"op\":\"add\",\"path\":\"/spec/template/spec/containers/0/livenessProbe\",\"value\":{\"httpGet\":{\"path\":\"/healthz\",\"port\":8080},\"initialDelaySeconds\":10,\"periodSeconds\":10}}]'",
+ "NativeIaC": "# Example: add a livenessProbe to your container spec\nlivenessProbe:\n httpGet:\n path: /healthz\n port: 8080\n initialDelaySeconds: 10\n periodSeconds: 10",
+ "Other": "1. Edit the Pod/Deployment manifest and add a `livenessProbe` to each container.\n2. Tune `initialDelaySeconds`, `periodSeconds` and failure thresholds to your app.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Add and tune liveness probes for containers to allow Kubernetes to detect and restart unhealthy containers.",
+ "Url": "https://hub.prowler.com/check/core_liveness_probe_configured"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Presence of a probe is checked; adjust thresholds for app behavior to avoid false positives."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.py b/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.py
new file mode 100644
index 0000000000..0bfbc618d2
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_liveness_probe_configured/core_liveness_probe_configured.py
@@ -0,0 +1,28 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_liveness_probe_configured(Check):
+ """Check whether regular pod containers have liveness probes configured."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the Kubernetes pod liveness probe check.
+
+ Returns:
+ List of check reports for Kubernetes pods.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = f"Pod {pod.name} has liveness probes configured for all regular containers."
+
+ for container in (pod.containers or {}).values():
+ if not container.liveness_probe:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} container {container.name} does not have a liveness probe configured."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/logging/__init__.py b/prowler/providers/kubernetes/services/core/core_memory_limits_set/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/logging/__init__.py
rename to prowler/providers/kubernetes/services/core/core_memory_limits_set/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.metadata.json b/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.metadata.json
new file mode 100644
index 0000000000..8b9a121bf2
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_memory_limits_set",
+ "CheckTitle": "Container memory limits are configured",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Pod",
+ "ResourceGroup": "container",
+ "Description": "**Kubernetes Pods** are evaluated for containers without **memory limits** configured in `resources.limits.memory`, indicating unbounded memory consumption is permitted.",
+ "Risk": "Without **memory limits**, a single container can consume all available node memory, causing:\n- **OOM kills** of other workloads (availability)\n- Node instability and cascading failures\n- Noisy-neighbor problems in multi-tenant clusters\nAttackers exploiting a vulnerability can amplify impact by exhausting node resources, enabling **denial of service** across co-located workloads.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
+ "https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl set resources deployment/<workload-name> -c <container-name> --limits=memory=<memory-limit> -n <namespace>\n# Example: kubectl set resources deployment/nginx -c nginx --limits=memory=128Mi -n default",
+ "NativeIaC": "",
+ "Other": "1. Open your Kubernetes UI (e.g., cloud provider console or Dashboard)\n2. Navigate to the failing workload (Deployment/StatefulSet/DaemonSet) or Pod and choose Edit YAML/Manifest\n3. Set resources.limits.memory for each affected container:\n - For controllers: spec.template.spec.containers[].resources.limits.memory\n - For standalone Pods: spec.containers[].resources.limits.memory\n4. Save changes (controllers will roll out new Pods). If it is a standalone Pod, delete and recreate it to apply the change",
+ "Terraform": "```hcl\nresource \"kubernetes_pod\" \"<example_resource_name>\" {\n metadata { name = \"<example_resource_name>\" }\n spec {\n container {\n name = \"<example_resource_name>\"\n image = \"<IMAGE>\"\n resources {\n limits = {\n memory = \"128Mi\" # Critical: sets a memory ceiling to prevent unbounded consumption\n }\n }\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Set **memory limits** on every container to prevent unbounded consumption and protect node stability.\n\n- Start with observed usage plus headroom; tune with **VPA** recommendations\n- Combine with **LimitRanges** and **ResourceQuotas** at the namespace level for **defense in depth**\n- Monitor memory usage and OOMKill events to right-size limits over time",
+ "Url": "https://hub.prowler.com/check/core_memory_limits_set"
+ }
+ },
+ "Categories": [
+ "container-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Memory limits prevent containers from consuming unbounded memory and protect node stability."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.py b/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.py
new file mode 100644
index 0000000000..2fd623c8d5
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_memory_limits_set/core_memory_limits_set.py
@@ -0,0 +1,39 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_memory_limits_set(Check):
+ """Ensure that memory limits are set on all containers."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports containing the result of the check.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Pod {pod.name} has memory limits set on all containers."
+ )
+
+ for container in (pod.containers or {}).values():
+ resources = container.resources or {}
+ limits = (
+ resources.get("limits") if isinstance(resources, dict) else None
+ )
+ memory = (
+ limits.get("memory")
+ if limits and isinstance(limits, dict)
+ else None
+ )
+ if not memory:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} does not have memory limits set on container {container.name}."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/network/__init__.py b/prowler/providers/kubernetes/services/core/core_memory_requests_set/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/__init__.py
rename to prowler/providers/kubernetes/services/core/core_memory_requests_set/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.metadata.json b/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.metadata.json
new file mode 100644
index 0000000000..1871884621
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_memory_requests_set",
+ "CheckTitle": "Container memory requests are configured",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Pod",
+ "ResourceGroup": "container",
+ "Description": "**Kubernetes Pods** are evaluated for containers without **memory requests** configured in `resources.requests.memory`, indicating the scheduler cannot guarantee memory allocation.",
+ "Risk": "Without **memory requests**, the scheduler cannot make informed placement decisions, leading to:\n- Overcommitted nodes that trigger **OOM kills** (availability)\n- Unpredictable performance under load\n- Inability to enforce **ResourceQuotas** effectively\nMissing requests weaken cluster stability and make capacity planning unreliable, increasing blast radius during incidents.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
+ "https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl set resources deployment/<workload-name> -c <container-name> --requests=memory=<memory-request> -n <namespace>\n# Example: kubectl set resources deployment/nginx -c nginx --requests=memory=64Mi -n default",
+ "NativeIaC": "",
+ "Other": "1. Open your Kubernetes UI (e.g., cloud provider console or Dashboard)\n2. Navigate to the failing workload (Deployment/StatefulSet/DaemonSet) or Pod and choose Edit YAML/Manifest\n3. Set resources.requests.memory for each affected container:\n - For controllers: spec.template.spec.containers[].resources.requests.memory\n - For standalone Pods: spec.containers[].resources.requests.memory\n4. Save changes (controllers will roll out new Pods). If it is a standalone Pod, delete and recreate it to apply the change",
+ "Terraform": "```hcl\nresource \"kubernetes_pod\" \"<example_resource_name>\" {\n metadata { name = \"<example_resource_name>\" }\n spec {\n container {\n name = \"<example_resource_name>\"\n image = \"<IMAGE>\"\n resources {\n requests = {\n memory = \"64Mi\" # Critical: guarantees memory for the scheduler to make informed placement\n }\n }\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Set **memory requests** on every container so the scheduler can guarantee memory allocation and place pods effectively.\n\n- Base requests on observed steady-state usage; use **VPA** for data-driven sizing\n- Enforce minimum requests via **LimitRanges** at the namespace level\n- Combine with **ResourceQuotas** for **defense in depth** against overcommitment",
+ "Url": "https://hub.prowler.com/check/core_memory_requests_set"
+ }
+ },
+ "Categories": [
+ "container-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Memory requests enable the scheduler to guarantee memory allocation and prevent overcommitment."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.py b/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.py
new file mode 100644
index 0000000000..a560365e32
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_memory_requests_set/core_memory_requests_set.py
@@ -0,0 +1,39 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_memory_requests_set(Check):
+ """Ensure that memory requests are set on all containers."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports containing the result of the check.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = (
+ f"Pod {pod.name} has memory requests set on all containers."
+ )
+
+ for container in (pod.containers or {}).values():
+ resources = container.resources or {}
+ requests = (
+ resources.get("requests") if isinstance(resources, dict) else None
+ )
+ memory = (
+ requests.get("memory")
+ if requests and isinstance(requests, dict)
+ else None
+ )
+ if not memory:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} does not have memory requests set on container {container.name}."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/network/network_default_security_list_restricts_traffic/__init__.py b/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_default_security_list_restricts_traffic/__init__.py
rename to prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.metadata.json b/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.metadata.json
new file mode 100644
index 0000000000..f25b22231f
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_minimize_hostpath_volume_mounts",
+ "CheckTitle": "Pod does not use hostPath volumes",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "Pod",
+ "ResourceGroup": "container",
+ "Description": "**Kubernetes Pods** are evaluated for volumes of type `hostPath`, which mount paths from the node filesystem into a pod.",
+ "Risk": "`hostPath` volumes weaken the container boundary by exposing node files to workloads. A compromised container can read sensitive host data, tamper with node files, or use writable mounts to escalate privileges and affect node availability.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/concepts/storage/volumes/#hostpath",
+ "https://kubernetes.io/docs/concepts/security/pod-security-standards/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl get pod <pod_name> -n <namespace> -o jsonpath='{range .metadata.ownerReferences[*]}{.kind}/{.name}{\"\\n\"}{end}{range .spec.volumes[?(@.hostPath)]}{.name}{\"\\t\"}{.hostPath.path}{\"\\n\"}{end}'\n# If the Pod is managed by a controller, edit the owning workload and remove hostPath volumes from its Pod template:\nkubectl edit <workload_kind>/<workload_name> -n <namespace>\n# For a standalone Pod, export the manifest, remove hostPath volumes, then recreate it:\nkubectl get pod <pod_name> -n <namespace> -o yaml > pod.yaml\nkubectl delete pod <pod_name> -n <namespace>\nkubectl apply -f pod.yaml",
+ "NativeIaC": "",
+ "Other": "1. Identify the workload that owns the failing Pod (Deployment/DaemonSet/StatefulSet/Job) or confirm it is a standalone Pod\n2. Edit the Pod template and remove volumes that define `hostPath`\n3. Replace hostPath with a safer volume type such as ConfigMap, Secret, emptyDir, persistentVolumeClaim, or a CSI volume when appropriate\n4. Apply the updated manifest and allow the workload to recreate Pods without hostPath volumes",
+ "Terraform": "```hcl\nresource \"kubernetes_pod\" \"<example_resource_name>\" {\n metadata {\n name = \"<example_resource_name>\"\n }\n spec {\n container {\n name = \"app\"\n image = \"nginx\"\n }\n # Do not define host_path blocks under volume.\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Disallow `hostPath` volumes by default with Pod Security Admission or policy-as-code controls. Permit narrow, read-only exceptions only for trusted system workloads, and prefer Kubernetes-native volume types that do not expose the node filesystem.",
+ "Url": "https://hub.prowler.com/check/core_minimize_hostpath_volume_mounts"
+ }
+ },
+ "Categories": [
+ "container-security",
+ "trust-boundaries"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Exceptions for hostPath volumes should be narrowly scoped, read-only where possible, and monitored."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.py b/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.py
new file mode 100644
index 0000000000..a693f52f0e
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_minimize_hostpath_volume_mounts/core_minimize_hostpath_volume_mounts.py
@@ -0,0 +1,23 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_minimize_hostpath_volume_mounts(Check):
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = f"Pod {pod.name} does not use hostPath volumes."
+
+ for volume in pod.volumes or []:
+ if volume.get("host_path"):
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Pod {pod.name} uses hostPath volume {volume['name']}."
+ )
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/network/network_security_group_ingress_from_internet_to_rdp_port/__init__.py b/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_security_group_ingress_from_internet_to_rdp_port/__init__.py
rename to prowler/providers/kubernetes/services/core/core_readiness_probe_configured/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.metadata.json b/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.metadata.json
new file mode 100644
index 0000000000..5c61381064
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.metadata.json
@@ -0,0 +1,35 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_readiness_probe_configured",
+ "CheckTitle": "Regular pod containers have readiness probes configured",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "KubernetesPod",
+ "Description": "Ensure each regular pod container has a readiness probe configured to signal when it is ready to serve traffic.",
+ "Risk": "Without readiness probes, services may receive traffic before containers are ready, causing errors.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl patch deployment/<name> -n <namespace> --type='json' -p='[{\"op\":\"add\",\"path\":\"/spec/template/spec/containers/0/readinessProbe\",\"value\":{\"httpGet\":{\"path\":\"/ready\",\"port\":8080},\"initialDelaySeconds\":5,\"periodSeconds\":5}}]'",
+ "NativeIaC": "# Example readiness probe\nreadinessProbe:\n httpGet:\n path: /ready\n port: 8080\n initialDelaySeconds: 5\n periodSeconds: 5",
+ "Other": "1. Add a `readinessProbe` to the container spec in Deployments/Pods.\n2. Ensure the probe accurately reflects service readiness.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Add readiness probes to prevent routing traffic to unready containers.",
+ "Url": "https://hub.prowler.com/check/core_readiness_probe_configured"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Readiness and liveness probes serve different purposes; implement both where appropriate."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.py b/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.py
new file mode 100644
index 0000000000..847f9b4b97
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_readiness_probe_configured/core_readiness_probe_configured.py
@@ -0,0 +1,28 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_readiness_probe_configured(Check):
+ """Check whether regular pod containers have readiness probes configured."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the Kubernetes pod readiness probe check.
+
+ Returns:
+ List of check reports for Kubernetes pods.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = f"Pod {pod.name} has readiness probes configured for all regular containers."
+
+ for container in (pod.containers or {}).values():
+ if not container.readiness_probe:
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} container {container.name} does not have a readiness probe configured."
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/tests/providers/oraclecloud/services/network/network_security_group_ingress_from_internet_to_ssh_port/__init__.py b/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_security_group_ingress_from_internet_to_ssh_port/__init__.py
rename to prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/__init__.py
diff --git a/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.metadata.json b/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.metadata.json
new file mode 100644
index 0000000000..d28b7ab94f
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "kubernetes",
+ "CheckID": "core_readonly_root_filesystem_enabled",
+ "CheckTitle": "Containers should run with a read-only root filesystem",
+ "CheckType": [],
+ "ServiceName": "core",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Pod",
+ "ResourceGroup": "container",
+ "Description": "**Kubernetes Pods** are evaluated to ensure every container sets `readOnlyRootFilesystem: true` in its `securityContext`. A writable root filesystem lets an attacker who gains code execution modify binaries, drop tools, or persist malicious files inside the container.",
+ "Risk": "Without a read-only root filesystem an attacker with code execution inside a container can tamper with binaries or libraries (**integrity**), write credential files or exfiltration tools (**confidentiality**), and persist across process restarts (**availability**).",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://kubernetes.io/docs/tasks/configure-pod-container/security-context/",
+ "https://kubernetes.io/docs/concepts/security/pod-security-standards/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "kubectl patch deployment/<workload-name> -n <namespace> -p '{\"spec\":{\"template\":{\"spec\":{\"containers\":[{\"name\":\"<container-name>\",\"securityContext\":{\"readOnlyRootFilesystem\":true}}]}}}}'\n# Deployment template example for regular containers. For init containers, use initContainers instead of containers. Ephemeral containers are added through the ephemeralcontainers subresource; remove or recreate debug containers with a compliant securityContext.",
+ "NativeIaC": "",
+ "Other": "1. Open your Kubernetes Dashboard (or your cloud provider's Kubernetes console) and locate the workload managing the failing Pod (Deployment/StatefulSet/DaemonSet)\n2. Click Edit to modify the manifest (YAML)\n3. For each container missing `securityContext.readOnlyRootFilesystem: true`, add or set it to `true`\n4. If the container needs write access, mount a writable `emptyDir` or `persistentVolumeClaim` at the specific paths that require writes instead of making the entire root filesystem writable\n5. Save/Apply the changes to trigger a rollout\n6. Verify new Pods have `securityContext.readOnlyRootFilesystem` set to `true`",
+ "Terraform": "```hcl\nresource \"kubernetes_pod\" \"main\" {\n metadata {\n name = \"<example_resource_name>\"\n }\n spec {\n container {\n name = \"app\"\n image = \"nginx\"\n security_context {\n read_only_root_filesystem = true # Critical: enforce a read-only root filesystem\n }\n }\n }\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Set `readOnlyRootFilesystem: true` for every regular, init, and ephemeral container that is part of a Pod spec. Mount writable `emptyDir` volumes only at the specific paths that genuinely need write access (e.g., `/tmp`, `/var/cache`). Enforce this at admission time with custom admission policies such as ValidatingAdmissionPolicy or OPA/Gatekeeper.",
+ "Url": "https://hub.prowler.com/check/core_readonly_root_filesystem_enabled"
+ }
+ },
+ "Categories": [
+ "container-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Regular, init, and ephemeral containers are evaluated. Workloads that genuinely require root filesystem writes should mount writable volumes at specific paths and may be exempted via Prowler's mutelist."
+}
diff --git a/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.py b/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.py
new file mode 100644
index 0000000000..cb7eebcdf7
--- /dev/null
+++ b/prowler/providers/kubernetes/services/core/core_readonly_root_filesystem_enabled/core_readonly_root_filesystem_enabled.py
@@ -0,0 +1,38 @@
+from prowler.lib.check.models import Check, Check_Report_Kubernetes
+from prowler.providers.kubernetes.services.core.core_client import core_client
+
+
+class core_readonly_root_filesystem_enabled(Check):
+ """Check whether every container in each Pod has readOnlyRootFilesystem set to true."""
+
+ def execute(self) -> list[Check_Report_Kubernetes]:
+ """Execute the Kubernetes read-only root filesystem check.
+
+ Returns:
+ List of check reports for Kubernetes pods.
+ """
+ findings = []
+ for pod in core_client.pods.values():
+ report = Check_Report_Kubernetes(metadata=self.metadata(), resource=pod)
+ report.status = "PASS"
+ report.status_extended = f"Pod {pod.name} has read-only root filesystem enabled for all containers."
+
+ for containers in (
+ pod.containers,
+ pod.init_containers,
+ pod.ephemeral_containers,
+ ):
+ for container in (containers or {}).values():
+ if (
+ container.security_context.get("read_only_root_filesystem")
+ is not True
+ ):
+ report.status = "FAIL"
+ report.status_extended = f"Pod {pod.name} container {container.name} does not have readOnlyRootFilesystem set to true."
+ break
+ if report.status == "FAIL":
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/kubernetes/services/core/core_service.py b/prowler/providers/kubernetes/services/core/core_service.py
index e685140a87..dc44d8f51f 100644
--- a/prowler/providers/kubernetes/services/core/core_service.py
+++ b/prowler/providers/kubernetes/services/core/core_service.py
@@ -27,45 +27,12 @@ class Core(KubernetesService):
for namespace in self.namespaces:
pods = self.client.list_namespaced_pod(namespace)
for pod in pods.items:
- pod_containers = {}
- containers = pod.spec.containers if pod.spec.containers else []
- init_containers = (
- pod.spec.init_containers if pod.spec.init_containers else []
- )
- ephemeral_containers = (
+ containers = self._build_containers(pod.spec.containers)
+ init_containers = self._build_containers(pod.spec.init_containers)
+ ephemeral_containers = self._build_containers(
pod.spec.ephemeral_containers
- if pod.spec.ephemeral_containers
- else []
)
- for container in (
- containers + init_containers + ephemeral_containers
- ):
- pod_containers[container.name] = Container(
- name=container.name,
- image=container.image,
- command=container.command if container.command else None,
- ports=(
- [
- {"containerPort": port.container_port}
- for port in container.ports
- ]
- if container.ports
- else None
- ),
- env=(
- [
- {"name": env.name, "value": env.value}
- for env in container.env
- ]
- if container.env
- else None
- ),
- security_context=(
- container.security_context.to_dict()
- if container.security_context
- else {}
- ),
- )
+ volumes = self._build_volumes(pod.spec.volumes)
self.pods[pod.metadata.uid] = Pod(
name=pod.metadata.name,
uid=pod.metadata.uid,
@@ -85,13 +52,71 @@ class Core(KubernetesService):
if pod.spec.security_context
else {}
),
- containers=pod_containers,
+ containers=containers,
+ init_containers=init_containers,
+ ephemeral_containers=ephemeral_containers,
+ volumes=volumes,
)
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
+ @staticmethod
+ def _build_containers(containers) -> dict:
+ pod_containers = {}
+ for container in containers or []:
+ pod_containers[container.name] = Container(
+ name=container.name,
+ image=container.image,
+ command=container.command if container.command else None,
+ ports=(
+ [{"containerPort": port.container_port} for port in container.ports]
+ if container.ports
+ else None
+ ),
+ env=(
+ [{"name": env.name, "value": env.value} for env in container.env]
+ if container.env
+ else None
+ ),
+ security_context=(
+ container.security_context.to_dict()
+ if container.security_context
+ else {}
+ ),
+ resources=(
+ container.resources.to_dict()
+ if getattr(container, "resources", None)
+ else None
+ ),
+ liveness_probe=(
+ container.liveness_probe.to_dict()
+ if getattr(container, "liveness_probe", None)
+ else None
+ ),
+ readiness_probe=(
+ container.readiness_probe.to_dict()
+ if getattr(container, "readiness_probe", None)
+ else None
+ ),
+ )
+ return pod_containers
+
+ @staticmethod
+ def _build_volumes(volumes) -> List[dict]:
+ pod_volumes = []
+ for volume in volumes or []:
+ pod_volumes.append(
+ {
+ "name": volume.name,
+ "host_path": (
+ volume.host_path.to_dict() if volume.host_path else None
+ ),
+ }
+ )
+ return pod_volumes
+
def _list_config_maps(self):
try:
response = self.client.list_config_map_for_all_namespaces()
@@ -156,6 +181,9 @@ class Container(BaseModel):
ports: Optional[List[dict]]
env: Optional[List[dict]]
security_context: dict
+ resources: Optional[dict] = None
+ liveness_probe: Optional[dict] = None
+ readiness_probe: Optional[dict] = None
class Pod(BaseModel):
@@ -174,6 +202,9 @@ class Pod(BaseModel):
host_network: Optional[bool]
security_context: Optional[dict]
containers: Optional[dict]
+ init_containers: Optional[dict] = None
+ ephemeral_containers: Optional[dict] = None
+ volumes: Optional[List[dict]] = None
class ConfigMap(BaseModel):
diff --git a/tests/providers/oraclecloud/services/network/network_security_list_ingress_from_internet_to_rdp_port/__init__.py b/prowler/providers/linode/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_security_list_ingress_from_internet_to_rdp_port/__init__.py
rename to prowler/providers/linode/__init__.py
diff --git a/tests/providers/oraclecloud/services/network/network_security_list_ingress_from_internet_to_ssh_port/__init__.py b/prowler/providers/linode/exceptions/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_security_list_ingress_from_internet_to_ssh_port/__init__.py
rename to prowler/providers/linode/exceptions/__init__.py
diff --git a/prowler/providers/linode/exceptions/exceptions.py b/prowler/providers/linode/exceptions/exceptions.py
new file mode 100644
index 0000000000..6c39f477db
--- /dev/null
+++ b/prowler/providers/linode/exceptions/exceptions.py
@@ -0,0 +1,106 @@
+from prowler.exceptions.exceptions import ProwlerException
+
+
+# Exceptions codes from 18000 to 18099 are reserved for Linode exceptions
+class LinodeBaseException(ProwlerException):
+ """Base class for Linode errors."""
+
+ LINODE_ERROR_CODES = {
+ (18000, "LinodeCredentialsError"): {
+ "message": "Linode credentials not found or invalid",
+ "remediation": "Provide a valid Personal Access Token for Linode via the LINODE_TOKEN environment variable.",
+ },
+ (18001, "LinodeAuthenticationError"): {
+ "message": "Linode authentication failed",
+ "remediation": "Verify the Linode Personal Access Token and ensure it has the required scopes (linodes:read_only, firewalls:read_only, account:read_only).",
+ },
+ (18002, "LinodeSessionError"): {
+ "message": "Linode session setup failed",
+ "remediation": "Review the Linode SDK initialization parameters and credentials.",
+ },
+ (18003, "LinodeIdentityError"): {
+ "message": "Unable to retrieve Linode identity or account information",
+ "remediation": "Ensure the Personal Access Token allows access to the Linode account and profile APIs.",
+ },
+ (18004, "LinodeMissingPermissionError"): {
+ "message": "Linode token is missing a required permission scope",
+ "remediation": "Grant the Personal Access Token the read-only scope required for the affected service (account:read_only, linodes:read_only, firewall:read_only).",
+ },
+ (18005, "LinodeInvalidRegionError"): {
+ "message": "One or more requested Linode regions are invalid",
+ "remediation": "Pass a valid Linode region id to --region. See https://www.linode.com/global-infrastructure/ or the API /v4/regions endpoint for the current list.",
+ },
+ }
+
+ def __init__(self, code, file=None, original_exception=None, message=None):
+ provider = "Linode"
+ error_info = self.LINODE_ERROR_CODES.get((code, self.__class__.__name__))
+ if error_info is None:
+ error_info = {
+ "message": message or "Unknown Linode error",
+ "remediation": "Check the Linode API documentation for more details.",
+ }
+ elif message:
+ error_info = error_info.copy()
+ error_info["message"] = message
+ super().__init__(
+ code=code,
+ source=provider,
+ file=file,
+ original_exception=original_exception,
+ error_info=error_info,
+ )
+
+
+class LinodeCredentialsError(LinodeBaseException):
+ """Exception for Linode credential errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18000, file=file, original_exception=original_exception, message=message
+ )
+
+
+class LinodeAuthenticationError(LinodeBaseException):
+ """Exception for Linode authentication errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18001, file=file, original_exception=original_exception, message=message
+ )
+
+
+class LinodeSessionError(LinodeBaseException):
+ """Exception for Linode session setup errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18002, file=file, original_exception=original_exception, message=message
+ )
+
+
+class LinodeIdentityError(LinodeBaseException):
+ """Exception for Linode identity errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18003, file=file, original_exception=original_exception, message=message
+ )
+
+
+class LinodeMissingPermissionError(LinodeBaseException):
+ """Exception for Linode missing permission scope errors."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18004, file=file, original_exception=original_exception, message=message
+ )
+
+
+class LinodeInvalidRegionError(LinodeBaseException):
+ """Exception for invalid Linode region filters."""
+
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 18005, file=file, original_exception=original_exception, message=message
+ )
diff --git a/tests/providers/oraclecloud/services/network/network_vcn_subnet_flow_logs_enabled/__init__.py b/prowler/providers/linode/lib/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/network/network_vcn_subnet_flow_logs_enabled/__init__.py
rename to prowler/providers/linode/lib/__init__.py
diff --git a/tests/providers/oraclecloud/services/objectstorage/__init__.py b/prowler/providers/linode/lib/arguments/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/objectstorage/__init__.py
rename to prowler/providers/linode/lib/arguments/__init__.py
diff --git a/prowler/providers/linode/lib/arguments/arguments.py b/prowler/providers/linode/lib/arguments/arguments.py
new file mode 100644
index 0000000000..b8af36dba9
--- /dev/null
+++ b/prowler/providers/linode/lib/arguments/arguments.py
@@ -0,0 +1,24 @@
+def init_parser(self):
+ """Init the Linode provider CLI parser."""
+ linode_parser = self.subparsers.add_parser(
+ "linode", parents=[self.common_providers_parser], help="Linode Provider"
+ )
+
+ # Authentication
+ # Credentials are read exclusively from the standard Linode environment
+ # variable (LINODE_TOKEN) to avoid leaking secrets into shell history and
+ # process listings. There are no credential CLI flags.
+
+ # Regions
+ regions_subparser = linode_parser.add_argument_group("Regions")
+ regions_subparser.add_argument(
+ "--region",
+ "--filter-region",
+ "-f",
+ nargs="+",
+ default=None,
+ metavar="REGION",
+ help="Linode region(s) to scan (e.g. eu-central us-east). Region-less "
+ "resources (account, networking) are always scanned. If omitted, all "
+ "regions are scanned.",
+ )
diff --git a/tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_encrypted_with_cmk/__init__.py b/prowler/providers/linode/lib/mutelist/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_encrypted_with_cmk/__init__.py
rename to prowler/providers/linode/lib/mutelist/__init__.py
diff --git a/prowler/providers/linode/lib/mutelist/mutelist.py b/prowler/providers/linode/lib/mutelist/mutelist.py
new file mode 100644
index 0000000000..c7da04a58a
--- /dev/null
+++ b/prowler/providers/linode/lib/mutelist/mutelist.py
@@ -0,0 +1,30 @@
+from prowler.lib.check.models import CheckReportLinode
+from prowler.lib.mutelist.mutelist import Mutelist
+from prowler.lib.outputs.utils import unroll_dict, unroll_tags
+
+
+class LinodeMutelist(Mutelist):
+ """Linode-specific mutelist helper."""
+
+ def is_finding_muted(
+ self,
+ finding: CheckReportLinode,
+ account_id: str,
+ ) -> bool:
+ """
+ Check if a Linode finding is muted.
+
+ Args:
+ finding: CheckReportLinode instance containing check metadata, region, resource info, and tags.
+ account_id: Linode account identifier.
+
+ Returns:
+ True if the finding is muted, False otherwise.
+ """
+ return self.is_muted(
+ account_id,
+ finding.check_metadata.CheckID,
+ finding.region or "global",
+ finding.resource_id or finding.resource_name,
+ unroll_dict(unroll_tags(finding.resource_tags)),
+ )
diff --git a/tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_logging_enabled/__init__.py b/prowler/providers/linode/lib/service/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_logging_enabled/__init__.py
rename to prowler/providers/linode/lib/service/__init__.py
diff --git a/prowler/providers/linode/lib/service/service.py b/prowler/providers/linode/lib/service/service.py
new file mode 100644
index 0000000000..d1a9de65db
--- /dev/null
+++ b/prowler/providers/linode/lib/service/service.py
@@ -0,0 +1,86 @@
+import os
+from concurrent.futures import ThreadPoolExecutor, as_completed
+
+from prowler.lib.logger import logger
+from prowler.providers.linode.exceptions.exceptions import LinodeMissingPermissionError
+from prowler.providers.linode.linode_provider import LinodeProvider
+
+MAX_WORKERS = 10
+
+
+class LinodeService:
+ """Base class for Linode services to share provider context."""
+
+ def __init__(self, service: str, provider: LinodeProvider):
+ """
+ Initialize the Linode service with provider context.
+
+ Args:
+ service: The Linode service name (e.g., administration, compute, networking).
+ provider: LinodeProvider instance containing session, audit config, and fixer config.
+ """
+ self.provider = provider
+ self.client = provider.session.client
+ self.audit_config = provider.audit_config
+ self.fixer_config = provider.fixer_config
+ self.service = service.lower() if not service.islower() else service
+
+ self.thread_pool = ThreadPoolExecutor(max_workers=MAX_WORKERS)
+
+ def _log_fetch_error(
+ self, resource_label: str, required_scope: str, error: Exception
+ ) -> None:
+ """Log a resource-fetch failure, distinguishing an insufficient-scope
+ (HTTP 401/403) error from a generic API error.
+
+ This never raises: a single service's missing permission must not abort
+ the rest of the scan. When the token lacks the required scope, the log
+ names the exact scope to grant via ``LinodeMissingPermissionError``.
+
+ Args:
+ resource_label: Human-readable resource name (e.g. "firewalls").
+ required_scope: The Linode OAuth scope needed (e.g. "firewall:read_only").
+ error: The exception raised by the SDK call.
+ """
+ service_name = getattr(self, "service", "linode")
+ status = getattr(error, "status", None)
+ if status in (401, 403) or "not authorized to use this endpoint" in str(error):
+ logger.error(
+ str(
+ LinodeMissingPermissionError(
+ file=os.path.basename(__file__),
+ message=(
+ f"{service_name} - unable to list {resource_label}: the Linode "
+ f"token lacks the '{required_scope}' scope; skipping these checks."
+ ),
+ original_exception=error,
+ )
+ )
+ )
+ else:
+ logger.error(
+ f"{service_name} - Error fetching {resource_label}: "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ def __threading_call__(self, call, iterator):
+ """Execute a function across multiple items using threading."""
+ items = list(iterator) if not isinstance(iterator, list) else iterator
+
+ futures = {self.thread_pool.submit(call, item): item for item in items}
+ results = []
+
+ for future in as_completed(futures):
+ try:
+ result = future.result()
+ if result is not None:
+ results.append(result)
+ except Exception as error:
+ item = futures[future]
+ item_id = getattr(item, "id", str(item))
+ logger.error(
+ f"{self.service} - Threading error processing {item_id}: "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ return results
diff --git a/prowler/providers/linode/linode_provider.py b/prowler/providers/linode/linode_provider.py
new file mode 100644
index 0000000000..ab069fab3d
--- /dev/null
+++ b/prowler/providers/linode/linode_provider.py
@@ -0,0 +1,343 @@
+import logging
+import os
+
+from colorama import Fore, Style
+from linode_api4 import LinodeClient
+
+from prowler.config.config import (
+ default_config_file_path,
+ get_default_mute_file_path,
+ load_and_validate_config_file,
+)
+from prowler.lib.logger import logger
+from prowler.lib.utils.utils import print_boxes
+from prowler.providers.common.models import Audit_Metadata, Connection
+from prowler.providers.common.provider import Provider
+from prowler.providers.linode.exceptions.exceptions import (
+ LinodeAuthenticationError,
+ LinodeCredentialsError,
+ LinodeIdentityError,
+ LinodeInvalidRegionError,
+ LinodeSessionError,
+)
+from prowler.providers.linode.lib.mutelist.mutelist import LinodeMutelist
+from prowler.providers.linode.models import (
+ LinodeIdentityInfo,
+ LinodeSession,
+)
+
+
+class LinodeProvider(Provider):
+ """Linode provider."""
+
+ _type: str = "linode"
+ _session: LinodeSession
+ _identity: LinodeIdentityInfo
+ _audit_config: dict
+ _fixer_config: dict
+ _mutelist: LinodeMutelist
+ _regions: set
+ audit_metadata: Audit_Metadata
+
+ def __init__(
+ self,
+ config_path: str = None,
+ config_content: dict | None = None,
+ fixer_config: dict | None = None,
+ mutelist_path: str = None,
+ mutelist_content: dict = None,
+ token: str = None,
+ regions: list = None,
+ ):
+ """
+ Initializes the LinodeProvider instance.
+
+ Args:
+ config_path (str): Path to the configuration file.
+ config_content (dict): Audit configuration content.
+ fixer_config (dict): Fixer configuration.
+ mutelist_path (str): Path to the mutelist file.
+ mutelist_content (dict): Mutelist content.
+ token (str): Linode Personal Access Token (falls back to LINODE_TOKEN env var).
+ regions (list): Region(s) to scan regional resources in. Region-less
+ resources are always scanned. ``None`` scans all regions.
+
+ Raises:
+ LinodeCredentialsError: If no token is provided.
+ LinodeSessionError: If the Linode session cannot be established.
+ LinodeIdentityError: If user or account identity cannot be retrieved.
+ """
+ logger.info("Instantiating Linode provider...")
+
+ # Mute noisy HTTP client logs
+ logging.getLogger("urllib3").setLevel(logging.WARNING)
+
+ if config_content:
+ self._audit_config = config_content
+ else:
+ if not config_path:
+ config_path = default_config_file_path
+ self._audit_config = load_and_validate_config_file(self._type, config_path)
+
+ self._session = LinodeProvider.setup_session(token=token)
+
+ # Region filter for regional resources, validated against the live
+ # Linode regions list. None means scan all regions.
+ self._regions = LinodeProvider.validate_regions(self._session, regions)
+
+ self._identity = LinodeProvider.setup_identity(self._session)
+
+ self._fixer_config = fixer_config if fixer_config is not None else {}
+
+ if mutelist_content:
+ self._mutelist = LinodeMutelist(mutelist_content=mutelist_content)
+ else:
+ if not mutelist_path:
+ mutelist_path = get_default_mute_file_path(self.type)
+ self._mutelist = LinodeMutelist(mutelist_path=mutelist_path)
+
+ Provider.set_global_provider(self)
+
+ @property
+ def type(self):
+ return self._type
+
+ @property
+ def session(self):
+ return self._session
+
+ @property
+ def identity(self):
+ return self._identity
+
+ @property
+ def audit_config(self):
+ return self._audit_config
+
+ @property
+ def fixer_config(self):
+ return self._fixer_config
+
+ @property
+ def mutelist(self) -> LinodeMutelist:
+ return self._mutelist
+
+ @property
+ def regions(self):
+ """Set of regions to scan for regional resources, or None for all."""
+ return self._regions
+
+ def validate_arguments(self) -> None:
+ """Linode provider has no provider-specific arguments to validate."""
+ return None
+
+ @staticmethod
+ def setup_session(token: str = None) -> LinodeSession:
+ """Initialize Linode SDK client.
+
+ Credentials can be provided as argument or read from environment variable:
+ - LINODE_TOKEN (Personal Access Token)
+
+ Args:
+ token: Linode Personal Access Token (optional, falls back to env var).
+
+ Returns:
+ LinodeSession: The initialized Linode session.
+
+ Raises:
+ LinodeCredentialsError: If no credentials are provided.
+ LinodeSessionError: If session setup fails.
+ """
+ token = token or os.environ.get("LINODE_TOKEN", "")
+
+ if not token:
+ raise LinodeCredentialsError(
+ file=os.path.basename(__file__),
+ message="Linode credentials not found. Set the LINODE_TOKEN environment variable.",
+ )
+
+ try:
+ client = LinodeClient(token)
+ return LinodeSession(client=client, token=token)
+ except Exception as error:
+ logger.critical(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ raise LinodeSessionError(
+ file=os.path.basename(__file__),
+ original_exception=error,
+ )
+
+ @staticmethod
+ def validate_regions(session: LinodeSession, regions: list = None):
+ """Validate the requested regions against the live Linode regions list.
+
+ The ``/v4/regions`` endpoint is public, so this works regardless of the
+ token's scope. Validating against the live list (instead of a static
+ file) avoids rejecting newly added Linode regions.
+
+ Args:
+ session: The Linode session.
+ regions: The region ids requested via --region (or None).
+
+ Returns:
+ The validated set of region ids, or None when no filter is given.
+
+ Raises:
+ LinodeInvalidRegionError: If any requested region id is unknown.
+ """
+ if not regions:
+ return None
+
+ requested = set(regions)
+ try:
+ available = {region.id for region in session.client.regions()}
+ except Exception as error:
+ # Do not block a scan if the regions list cannot be fetched.
+ logger.warning(
+ f"Unable to validate Linode regions: {error}. "
+ "Proceeding with the requested regions without validation."
+ )
+ return requested
+
+ invalid = requested - available
+ if invalid:
+ raise LinodeInvalidRegionError(
+ file=os.path.basename(__file__),
+ message=(
+ f"Invalid Linode region(s): {', '.join(sorted(invalid))}. "
+ f"Valid regions are: {', '.join(sorted(available))}."
+ ),
+ )
+ return requested
+
+ @staticmethod
+ def setup_identity(session: LinodeSession) -> LinodeIdentityInfo:
+ """Fetch user and account metadata for Linode.
+
+ The authenticated user's profile is retrieved first to validate the
+ token. Any valid token can read its own profile, so a failure here
+ (for example a ``401 Invalid Token``) means the credentials are invalid
+ and the scan is aborted instead of silently returning empty results.
+
+ Args:
+ session: The Linode session.
+
+ Returns:
+ LinodeIdentityInfo: The identity information.
+
+ Raises:
+ LinodeAuthenticationError: If the token is invalid.
+ LinodeIdentityError: If identity setup fails unexpectedly.
+ """
+ try:
+ client = session.client
+ username = None
+ email = None
+ account_id = None
+
+ # Validate the token by reading the authenticated user's profile.
+ # A failure here means the credentials are invalid, so abort.
+ try:
+ profile = client.profile()
+ username = profile.username
+ email = profile.email
+ except Exception as error:
+ logger.critical(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ raise LinodeAuthenticationError(
+ file=os.path.basename(__file__),
+ original_exception=error,
+ )
+
+ # The account endpoint requires the account:read_only scope. A
+ # token without that scope is still valid, so continue without the
+ # account ID instead of failing the scan.
+ try:
+ account = client.account()
+ account_id = getattr(account, "euuid", None)
+ except Exception as error:
+ logger.warning(
+ f"Unable to retrieve Linode account info: {error}. Continuing without account ID."
+ )
+
+ return LinodeIdentityInfo(
+ username=username,
+ email=email,
+ account_id=account_id,
+ )
+ except LinodeAuthenticationError:
+ raise
+ except Exception as error:
+ logger.critical(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}] -- {error}"
+ )
+ raise LinodeIdentityError(
+ file=os.path.basename(__file__),
+ original_exception=error,
+ )
+
+ def print_credentials(self) -> None:
+ report_title = (
+ f"{Style.BRIGHT}Using the Linode credentials below:{Style.RESET_ALL}"
+ )
+ report_lines = []
+
+ report_lines.append(
+ f"Authentication: {Fore.YELLOW}Personal Access Token{Style.RESET_ALL}"
+ )
+
+ if self.identity.username:
+ report_lines.append(
+ f"Username: {Fore.YELLOW}{self.identity.username}{Style.RESET_ALL}"
+ )
+
+ if self.identity.email:
+ report_lines.append(
+ f"Email: {Fore.YELLOW}{self.identity.email}{Style.RESET_ALL}"
+ )
+
+ if self.identity.account_id:
+ report_lines.append(
+ f"Account ID: {Fore.YELLOW}{self.identity.account_id}{Style.RESET_ALL}"
+ )
+
+ print_boxes(report_lines, report_title)
+
+ @staticmethod
+ def test_connection(
+ token: str = None,
+ raise_on_exception: bool = True,
+ ) -> Connection:
+ """Test connection to Linode.
+
+ Args:
+ token: Linode Personal Access Token.
+ raise_on_exception: Flag indicating whether to raise an exception if the connection fails.
+
+ Returns:
+ Connection: Connection object with is_connected status.
+ """
+ try:
+ session = LinodeProvider.setup_session(token=token)
+ # Validate by fetching profile
+ session.client.profile()
+ return Connection(is_connected=True)
+ except LinodeCredentialsError as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ if raise_on_exception:
+ raise
+ return Connection(is_connected=False, error=error)
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ if raise_on_exception:
+ raise LinodeAuthenticationError(
+ file=os.path.basename(__file__),
+ original_exception=error,
+ )
+ return Connection(is_connected=False, error=error)
diff --git a/prowler/providers/linode/models.py b/prowler/providers/linode/models.py
new file mode 100644
index 0000000000..8e41e881a7
--- /dev/null
+++ b/prowler/providers/linode/models.py
@@ -0,0 +1,38 @@
+from typing import Any, Optional
+
+from pydantic import BaseModel
+
+from prowler.config.config import output_file_timestamp
+from prowler.providers.common.models import ProviderOutputOptions
+
+
+class LinodeSession(BaseModel):
+ """Linode session information."""
+
+ client: Any
+ token: Optional[str] = None
+
+
+class LinodeIdentityInfo(BaseModel):
+ """Linode identity and scoping information."""
+
+ username: Optional[str] = None
+ email: Optional[str] = None
+ account_id: Optional[str] = None
+
+
+class LinodeOutputOptions(ProviderOutputOptions):
+ """Customize output filenames for Linode scans."""
+
+ def __init__(self, arguments, bulk_checks_metadata, identity: LinodeIdentityInfo):
+ super().__init__(arguments, bulk_checks_metadata)
+ if (
+ not hasattr(arguments, "output_filename")
+ or arguments.output_filename is None
+ ):
+ account_fragment = identity.account_id or identity.username or "linode"
+ self.output_filename = (
+ f"prowler-output-{account_fragment}-{output_file_timestamp}"
+ )
+ else:
+ self.output_filename = arguments.output_filename
diff --git a/tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_not_publicly_accessible/__init__.py b/prowler/providers/linode/services/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_not_publicly_accessible/__init__.py
rename to prowler/providers/linode/services/__init__.py
diff --git a/tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_versioning_enabled/__init__.py b/prowler/providers/linode/services/administration/__init__.py
similarity index 100%
rename from tests/providers/oraclecloud/services/objectstorage/objectstorage_bucket_versioning_enabled/__init__.py
rename to prowler/providers/linode/services/administration/__init__.py
diff --git a/prowler/providers/linode/services/administration/administration_client.py b/prowler/providers/linode/services/administration/administration_client.py
new file mode 100644
index 0000000000..99a242e9ee
--- /dev/null
+++ b/prowler/providers/linode/services/administration/administration_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.linode.services.administration.administration_service import (
+ AdministrationService,
+)
+
+administration_client = AdministrationService(Provider.get_global_provider())
diff --git a/prowler/providers/linode/services/administration/administration_service.py b/prowler/providers/linode/services/administration/administration_service.py
new file mode 100644
index 0000000000..7704cf11b2
--- /dev/null
+++ b/prowler/providers/linode/services/administration/administration_service.py
@@ -0,0 +1,46 @@
+from typing import List
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.linode.lib.service.service import LinodeService
+
+
+class User(BaseModel):
+ """Model for a Linode account user."""
+
+ username: str
+ email: str = ""
+ tfa_enabled: bool = False
+ restricted: bool = False
+
+
+class AdministrationService(LinodeService):
+ """Service to interact with Linode Account Users."""
+
+ def __init__(self, provider):
+ super().__init__("administration", provider)
+ self.users: List[User] = []
+ self._describe_users()
+
+ def _describe_users(self):
+ """Fetch all Linode account users."""
+ try:
+ raw_users = self.client.account.users()
+ for user in raw_users:
+ try:
+ self.users.append(
+ User(
+ username=getattr(user, "username", "") or "",
+ email=getattr(user, "email", "") or "",
+ tfa_enabled=getattr(user, "tfa_enabled", False) or False,
+ restricted=getattr(user, "restricted", False) or False,
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"account - Error processing user {getattr(user, 'username', 'unknown')}: "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ self._log_fetch_error("account users", "account:read_only", error)
diff --git a/prowler/providers/linode/services/administration/administration_user_2fa_enabled/__init__.py b/prowler/providers/linode/services/administration/administration_user_2fa_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.metadata.json b/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.metadata.json
new file mode 100644
index 0000000000..c16e26f56d
--- /dev/null
+++ b/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "linode",
+ "CheckID": "administration_user_2fa_enabled",
+ "CheckTitle": "Linode account user has two-factor authentication enabled",
+ "CheckType": [],
+ "ServiceName": "administration",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Linode account users** are assessed for **two-factor authentication (2FA)** enablement. 2FA adds a second verification factor (a TOTP code or security key) on top of the password, so a stolen or guessed password alone is not enough to sign in to the **Linode Cloud Manager**.",
+ "Risk": "Without **2FA**, a single compromised password — through phishing, credential stuffing, or brute force — grants an attacker full access to the user's Linode account. This can lead to **data exfiltration**, destruction of instances and backups, and resource abuse for **cryptomining**, impacting **confidentiality**, **integrity**, and **availability**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/manage-2fa"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to My Profile > Login & Authentication\n3. Under Security Settings, configure all 3 security questions\n4. Enable Two-Factor Authentication",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable `2FA` for all Linode account users. Use an authenticator app (`TOTP`) for the second factor and store backup codes securely.",
+ "Url": "https://hub.prowler.com/check/administration_user_2fa_enabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.py b/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.py
new file mode 100644
index 0000000000..2bb2c92729
--- /dev/null
+++ b/prowler/providers/linode/services/administration/administration_user_2fa_enabled/administration_user_2fa_enabled.py
@@ -0,0 +1,41 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.administration.administration_client import (
+ administration_client,
+)
+
+
+class administration_user_2fa_enabled(Check):
+ """Check if Linode account users have two-factor authentication enabled."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the administration_user_2fa_enabled check.
+
+ Iterates over all account users and checks whether two-factor
+ authentication is enabled.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each user.
+ """
+ findings = []
+
+ for user in administration_client.users:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=user,
+ resource_name=user.username,
+ resource_id=user.username,
+ region="global",
+ )
+
+ if user.tfa_enabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"User '{user.username}' has two-factor authentication enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"User '{user.username}' does not have two-factor authentication enabled."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/compute/__init__.py b/prowler/providers/linode/services/compute/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/compute/compute_client.py b/prowler/providers/linode/services/compute/compute_client.py
new file mode 100644
index 0000000000..8dc03fa36d
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.linode.services.compute.compute_service import ComputeService
+
+compute_client = ComputeService(Provider.get_global_provider())
diff --git a/prowler/providers/linode/services/compute/compute_instance_backups_enabled/__init__.py b/prowler/providers/linode/services/compute/compute_instance_backups_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.metadata.json b/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.metadata.json
new file mode 100644
index 0000000000..b425e5c5b0
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "linode",
+ "CheckID": "compute_instance_backups_enabled",
+ "CheckTitle": "Linode Instance has the Backup service enabled",
+ "CheckType": [],
+ "ServiceName": "compute",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**Linode instances** are assessed for enrollment in the **Linode Backup service**, which performs automatic daily and weekly snapshots of an instance's disks. Without it enabled, there is no managed recovery point to restore from after a data-loss event.",
+ "Risk": "With the **Backup service** disabled, there is no automated recovery point for the instance. Accidental deletion, **ransomware**, disk corruption, or operator error can result in **permanent data loss** and extended **downtime**, directly impacting **availability** and data **integrity**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/enable-backups",
+ "https://techdocs.akamai.com/cloud-computing/docs/create-a-compute-instance#configure-additional-options"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "linode-cli linodes backups-enable <linode_id>",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Select the Linode instance\n3. Navigate to the Backups tab\n4. Click 'Enable Backups'",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable the `Linode Backup service` on this instance to ensure automated recovery points are available. Consider supplementing it with manual snapshots before critical changes.",
+ "Url": "https://hub.prowler.com/check/compute_instance_backups_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.py b/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.py
new file mode 100644
index 0000000000..c7ae903fbf
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_backups_enabled/compute_instance_backups_enabled.py
@@ -0,0 +1,40 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.compute.compute_client import compute_client
+
+
+class compute_instance_backups_enabled(Check):
+ """Check if Linode instances have the Backup service enabled."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the compute_instance_backups_enabled check.
+
+ Iterates over all Linode instances and checks whether the Backup
+ service is enabled.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each instance.
+ """
+ findings = []
+
+ for instance in compute_client.instances:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=instance,
+ resource_name=instance.label,
+ resource_id=str(instance.id),
+ region=instance.region,
+ )
+ report.resource_tags = instance.tags
+
+ if instance.backups_enabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Instance {instance.label} has the Backup service enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Instance {instance.label} does not have the Backup service enabled."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/__init__.py b/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.metadata.json b/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.metadata.json
new file mode 100644
index 0000000000..878030dc25
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "linode",
+ "CheckID": "compute_instance_disk_encryption_enabled",
+ "CheckTitle": "Linode Instance has disk encryption enabled",
+ "CheckType": [],
+ "ServiceName": "compute",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**Linode instances** are assessed for **disk encryption** status. Disk encryption protects **data at rest** on the instance's underlying disks, keeping stored data unreadable without the encryption keys even if the physical media is accessed.",
+ "Risk": "Without **disk encryption**, data at rest on the instance's disks is stored unprotected. This increases the risk of **data exposure** through physical access to decommissioned or stolen storage media, or via certain **hypervisor-level** vulnerabilities, compromising the **confidentiality** of sensitive data.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/local-disk-encryption",
+ "https://techdocs.akamai.com/cloud-computing/docs/create-a-compute-instance#enable-or-disable-disk-encryption"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Disk encryption must be enabled at instance creation time or by rebuilding the instance\n2. Create a new instance with disk_encryption set to 'enabled'\n3. Migrate data from the unencrypted instance to the new encrypted instance",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable `disk encryption` for this instance. Because it cannot be toggled on existing instances, rebuild or migrate to a new instance with encryption enabled.",
+ "Url": "https://hub.prowler.com/check/compute_instance_disk_encryption_enabled"
+ }
+ },
+ "Categories": [
+ "encryption"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.py b/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.py
new file mode 100644
index 0000000000..abe364d0b4
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_disk_encryption_enabled/compute_instance_disk_encryption_enabled.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.compute.compute_client import compute_client
+
+
+class compute_instance_disk_encryption_enabled(Check):
+ """Check if Linode instances have disk encryption enabled."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the compute_instance_disk_encryption_enabled check.
+
+ Iterates over all Linode instances and checks whether disk encryption
+ is enabled.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each instance.
+ """
+ findings = []
+
+ for instance in compute_client.instances:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=instance,
+ resource_name=instance.label,
+ resource_id=str(instance.id),
+ region=instance.region,
+ )
+ report.resource_tags = instance.tags
+
+ if instance.disk_encryption == "enabled":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Instance {instance.label} has disk encryption enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Instance {instance.label} does not have disk encryption enabled."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/__init__.py b/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.metadata.json b/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.metadata.json
new file mode 100644
index 0000000000..42e3c8f46f
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "linode",
+ "CheckID": "compute_instance_watchdog_enabled",
+ "CheckTitle": "Linode Instance has Watchdog (Lassie) enabled",
+ "CheckType": [],
+ "ServiceName": "compute",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "compute",
+ "Description": "**Linode instances** are assessed for **Watchdog (Lassie)** status. Watchdog is Linode's automatic recovery feature that monitors an instance and reboots it if it powers off unexpectedly, helping maintain availability without manual intervention.",
+ "Risk": "With **Watchdog (Lassie)** disabled, an instance that crashes or shuts down unexpectedly stays offline until it is manually restarted. This prolongs **downtime**, delays detection of availability incidents, and weakens the **availability** of services running on the instance.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/recover-from-unexpected-shutdowns-with-lassie"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "linode-cli linodes update <linode_id> --watchdog_enabled true",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Select the Linode instance\n3. Navigate to the Settings tab\n4. Enable the Shutdown Watchdog (Lassie) toggle",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable `Watchdog (Lassie)` on this instance to automatically recover from unexpected shutdowns and improve availability protection.",
+ "Url": "https://hub.prowler.com/check/compute_instance_watchdog_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.py b/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.py
new file mode 100644
index 0000000000..498deb970c
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_instance_watchdog_enabled/compute_instance_watchdog_enabled.py
@@ -0,0 +1,40 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.compute.compute_client import compute_client
+
+
+class compute_instance_watchdog_enabled(Check):
+ """Check if Linode instances have Watchdog (Lassie) enabled."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the compute_instance_watchdog_enabled check.
+
+ Iterates over all Linode instances and checks whether Watchdog
+ (Lassie) is enabled.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each instance.
+ """
+ findings = []
+
+ for instance in compute_client.instances:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=instance,
+ resource_name=instance.label,
+ resource_id=str(instance.id),
+ region=instance.region,
+ )
+ report.resource_tags = instance.tags
+
+ if instance.watchdog_enabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Instance {instance.label} has Watchdog (Lassie) enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Instance {instance.label} does not have Watchdog (Lassie) enabled."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/compute/compute_service.py b/prowler/providers/linode/services/compute/compute_service.py
new file mode 100644
index 0000000000..51d38aa834
--- /dev/null
+++ b/prowler/providers/linode/services/compute/compute_service.py
@@ -0,0 +1,99 @@
+from typing import List
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.linode.lib.service.service import LinodeService
+
+
+class Instance(BaseModel):
+ """Model for a Linode Instance."""
+
+ id: int
+ label: str
+ region: str
+ status: str
+ backups_enabled: bool = False
+ disk_encryption: str = "disabled" # "enabled" or "disabled"
+ watchdog_enabled: bool = False
+ tags: List[str] = []
+
+
+class ComputeService(LinodeService):
+ """Service to interact with Linode Instances."""
+
+ def __init__(self, provider):
+ super().__init__("compute", provider)
+ self.instances: List[Instance] = []
+ self._describe_instances()
+
+ def _describe_instances(self):
+ """Fetch all Linode instances with firewall and IP details."""
+ # Optional --region filter. None scans all regions. Region-less services
+ # do not call this, so they are always scanned.
+ regions_filter = getattr(getattr(self, "provider", None), "regions", None)
+ try:
+ raw_instances = self.client.linode.instances()
+ for inst in raw_instances:
+ try:
+ region = (
+ inst.region.id
+ if hasattr(inst.region, "id")
+ else str(inst.region)
+ )
+ if regions_filter and region not in regions_filter:
+ continue
+
+ # Get backup status
+ backups_enabled = False
+ try:
+ backups = getattr(inst, "backups", None)
+ if backups:
+ backups_enabled = getattr(backups, "enabled", False)
+ except Exception as error:
+ logger.warning(
+ f"instance - Unable to fetch backup status for instance "
+ f"{inst.id}: {error}"
+ )
+
+ # Get disk encryption status
+ disk_encryption = "disabled"
+ try:
+ de = getattr(inst, "disk_encryption", None)
+ if de:
+ disk_encryption = str(de)
+ except Exception as error:
+ logger.warning(
+ f"instance - Unable to fetch disk encryption status for "
+ f"instance {inst.id}: {error}"
+ )
+
+ # Get watchdog status
+ watchdog_enabled = False
+ try:
+ watchdog_enabled = getattr(inst, "watchdog_enabled", False)
+ except Exception as error:
+ logger.warning(
+ f"instance - Unable to fetch watchdog status for instance "
+ f"{inst.id}: {error}"
+ )
+
+ self.instances.append(
+ Instance(
+ id=inst.id,
+ label=inst.label or f"linode-{inst.id}",
+ region=region,
+ status=inst.status or "unknown",
+ backups_enabled=backups_enabled,
+ disk_encryption=disk_encryption,
+ watchdog_enabled=watchdog_enabled,
+ tags=inst.tags or [],
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"instance - Error processing instance {inst.id}: "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ self._log_fetch_error("instances", "linodes:read_only", error)
diff --git a/prowler/providers/linode/services/networking/__init__.py b/prowler/providers/linode/services/networking/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_client.py b/prowler/providers/linode/services/networking/networking_client.py
new file mode 100644
index 0000000000..0f0406048b
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.linode.services.networking.networking_service import (
+ NetworkingService,
+)
+
+networking_client = NetworkingService(Provider.get_global_provider())
diff --git a/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.metadata.json
new file mode 100644
index 0000000000..475601e5b3
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_assigned_to_devices",
+ "CheckTitle": "Linode Cloud Firewall is assigned to devices",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** are checked to verify each one is attached to at least one device, such as a **Linode instance** or **NodeBalancer**. A firewall only filters traffic for the resources it is assigned to, so an unassigned firewall enforces no protection at all.",
+ "Risk": "An **unassigned firewall** provides no protection to running workloads, leaving their network exposure governed only by default behavior. This commonly signals a **misconfigured control** where operators assume traffic is filtered when it is not, raising the risk of **unauthorized network access** to unprotected instances.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/apply-firewall-rules-to-a-service"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Select the associated firewall\n4. Click on either the Linodes or Nodebalancers tab and add those devices to the firewall",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Attach each firewall to applicable Linode devices, such as `Linodes` or `NodeBalancers`, to enforce intended network controls.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_assigned_to_devices"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_status_enabled"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.py b/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.py
new file mode 100644
index 0000000000..f245dd168e
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_assigned_to_devices/networking_firewall_assigned_to_devices.py
@@ -0,0 +1,52 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.lib.logger import logger
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_assigned_to_devices(Check):
+ """Check if Linode Cloud Firewalls are assigned to at least one device."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_assigned_to_devices check.
+
+ Iterates over all Cloud Firewalls and checks whether each one is
+ assigned to at least one device.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ # When the device count could not be determined (the devices fetch
+ # failed) skip the firewall instead of reporting a false FAIL.
+ if fw.attached_devices_count is None:
+ logger.warning(
+ f"firewall - Skipping firewall '{fw.label}' ({fw.id}): "
+ "device assignment could not be determined."
+ )
+ continue
+
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if fw.attached_devices_count > 0:
+ report.status = "PASS"
+ report.status_extended = f"Firewall '{fw.label}' is assigned to {fw.attached_devices_count} device(s)."
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Firewall '{fw.label}' is not assigned to any device."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.metadata.json
new file mode 100644
index 0000000000..16f0666f7d
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_default_inbound_policy_drop",
+ "CheckTitle": "Linode Cloud Firewall default inbound policy is DROP",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** apply a **default inbound policy** to ingress traffic that does not match any explicit rule. This check verifies the default is set to `DROP`, enforcing a **default-deny** posture so that only traffic intentionally permitted by a rule is allowed in.",
+ "Risk": "When the default inbound policy is `ACCEPT` instead of `DROP`, any traffic not explicitly denied by a rule is permitted. This **default-allow** posture can silently expose services, management ports, and unintended endpoints to the internet, enlarging the attack surface and increasing the risk of **unauthorized access**.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/manage-firewall-rules"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Select the associated firewall\n4. In the Rules tab, set the default inbound policy to DROP",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set the default inbound policy to `DROP` and allow only explicitly required inbound traffic.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_default_inbound_policy_drop"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_inbound_rules_configured"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.py b/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.py
new file mode 100644
index 0000000000..2f5c8cb6c3
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_default_inbound_policy_drop/networking_firewall_default_inbound_policy_drop.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_default_inbound_policy_drop(Check):
+ """Check if Linode Cloud Firewall default inbound policy is DROP."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_default_inbound_policy_drop check.
+
+ Iterates over all Cloud Firewalls and checks whether the default
+ inbound policy is DROP.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if fw.inbound_policy == "DROP":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Firewall '{fw.label}' has default inbound policy set to DROP."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Firewall '{fw.label}' has default inbound policy set to {fw.inbound_policy}."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.metadata.json
new file mode 100644
index 0000000000..5de3985464
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_default_outbound_policy_drop",
+ "CheckTitle": "Linode Cloud Firewall default outbound policy is DROP",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** apply a **default outbound policy** to egress traffic that matches no explicit rule. This check verifies the default is set to `DROP`, enforcing **default-deny egress** so that only approved outbound connections are allowed to leave the instance.",
+ "Risk": "An outbound default of `ACCEPT` permits unrestricted egress from the instance. If a host is compromised, this eases **data exfiltration** and **command-and-control (C2)** communication and lets malware reach arbitrary external endpoints, harming **confidentiality** and enabling lateral movement.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/manage-firewall-rules"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Select the associated firewall\n4. In the Rules tab, set the default outbound policy to DROP",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set the default outbound policy to `DROP` and allow only explicit outbound destinations and services.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_default_outbound_policy_drop"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_outbound_rules_configured"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.py b/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.py
new file mode 100644
index 0000000000..011693aee9
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_default_outbound_policy_drop/networking_firewall_default_outbound_policy_drop.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_default_outbound_policy_drop(Check):
+ """Check if Linode Cloud Firewall default outbound policy is DROP."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_default_outbound_policy_drop check.
+
+ Iterates over all Cloud Firewalls and checks whether the default
+ outbound policy is DROP.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if fw.outbound_policy == "DROP":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Firewall '{fw.label}' has default outbound policy set to DROP."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Firewall '{fw.label}' has default outbound policy set to {fw.outbound_policy}."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.metadata.json
new file mode 100644
index 0000000000..5e54dc6241
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_inbound_rules_configured",
+ "CheckTitle": "Linode Cloud Firewall inbound rules are configured",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** are checked to determine whether explicit **inbound rules** are configured. Defined ingress rules express the intended allow-list of sources, ports, and protocols instead of relying solely on the firewall's default policy.",
+ "Risk": "Without explicit **inbound rules**, ingress filtering depends entirely on the default policy and no intentional allow-list is documented. This makes the firewall's behavior ambiguous and harder to audit, raising the chance of **overly permissive access** or gaps in the protection operators expect.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/manage-firewall-rules"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Select the associated firewall\n4. Click Add an Inbound Rule in the Rules tab",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure explicit `inbound rules` to define allowed ingress sources, ports, and protocols and enforce expected security boundaries.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_inbound_rules_configured"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_default_inbound_policy_drop"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.py b/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.py
new file mode 100644
index 0000000000..9eba9ddeb6
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_inbound_rules_configured/networking_firewall_inbound_rules_configured.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_inbound_rules_configured(Check):
+ """Check if Linode Cloud Firewall has inbound rules configured."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_inbound_rules_configured check.
+
+ Iterates over all Cloud Firewalls and checks whether at least one
+ explicit inbound rule is configured.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if len(fw.inbound_rules) == 0:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Firewall '{fw.label}' has no inbound rules configured."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = f"Firewall '{fw.label}' has {len(fw.inbound_rules)} inbound rule(s) configured."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.metadata.json
new file mode 100644
index 0000000000..9bedf854cc
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_outbound_rules_configured",
+ "CheckTitle": "Linode Cloud Firewall outbound rules are configured",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** are checked to determine whether explicit **outbound rules** are configured. Defined egress rules express which destinations, ports, and protocols an instance is permitted to reach, rather than depending only on the firewall's default policy.",
+ "Risk": "Without explicit **outbound rules**, egress behavior depends solely on the default policy and no intended destination allow-list exists. Unconstrained or undocumented egress complicates auditing and can enable **data exfiltration** or connections to malicious endpoints if a host is compromised.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/manage-firewall-rules"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Select the associated firewall\n4. Click Add an Outbound Rule in the Rules tab",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure explicit `outbound rules` to control allowed egress destinations, ports, and protocols.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_outbound_rules_configured"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_default_outbound_policy_drop"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.py b/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.py
new file mode 100644
index 0000000000..1d97dca075
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_outbound_rules_configured/networking_firewall_outbound_rules_configured.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_outbound_rules_configured(Check):
+ """Check if Linode Cloud Firewall has outbound rules configured."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_outbound_rules_configured check.
+
+ Iterates over all Cloud Firewalls and checks whether at least one
+ explicit outbound rule is configured.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if len(fw.outbound_rules) == 0:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Firewall '{fw.label}' has no outbound rules configured."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = f"Firewall '{fw.label}' has {len(fw.outbound_rules)} outbound rule(s) configured."
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_firewall_status_enabled/__init__.py b/prowler/providers/linode/services/networking/networking_firewall_status_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.metadata.json b/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.metadata.json
new file mode 100644
index 0000000000..dd1e760d4c
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "linode",
+ "CheckID": "networking_firewall_status_enabled",
+ "CheckTitle": "Linode Cloud Firewall status is enabled",
+ "CheckType": [],
+ "ServiceName": "networking",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Linode Cloud Firewalls** can be in an `enabled` or `disabled` state. This check verifies the firewall status is `enabled`, because a firewall must be active for its inbound and outbound policies and rules to actually filter network traffic.",
+ "Risk": "A `disabled` firewall enforces **none** of its configured rules or default policies, leaving attached instances with no network filtering. This can unexpectedly expose management ports and services to the internet, significantly increasing the risk of **unauthorized access** and exploitation.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://techdocs.akamai.com/cloud-computing/docs/update-cloud-firewall-status"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Log in to the Linode Cloud Manager\n2. Navigate to Firewalls\n3. Click on the Enable button from the options corresponding to the firewall whose status you would like to update",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable `Linode Cloud Firewalls` so configured network filtering controls are actively enforced.",
+ "Url": "https://hub.prowler.com/check/networking_firewall_status_enabled"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "networking_firewall_assigned_to_devices"
+ ],
+ "Notes": ""
+}
diff --git a/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.py b/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.py
new file mode 100644
index 0000000000..603a088bd0
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_firewall_status_enabled/networking_firewall_status_enabled.py
@@ -0,0 +1,42 @@
+from prowler.lib.check.models import Check, CheckReportLinode
+from prowler.providers.linode.services.networking.networking_client import (
+ networking_client,
+)
+
+
+class networking_firewall_status_enabled(Check):
+ """Check if Linode Cloud Firewalls are enabled."""
+
+ def execute(self) -> list[CheckReportLinode]:
+ """Execute the networking_firewall_status_enabled check.
+
+ Iterates over all Cloud Firewalls and checks whether each one has
+ an enabled status.
+
+ Returns:
+ list[CheckReportLinode]: A list of findings for each firewall.
+ """
+ findings = []
+
+ for fw in networking_client.firewalls:
+ report = CheckReportLinode(
+ metadata=self.metadata(),
+ resource=fw,
+ resource_name=fw.label,
+ resource_id=str(fw.id),
+ region="global",
+ )
+ report.resource_tags = fw.tags
+
+ if fw.status == "enabled":
+ report.status = "PASS"
+ report.status_extended = f"Firewall '{fw.label}' is enabled."
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Firewall '{fw.label}' is not enabled (status: {fw.status})."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/linode/services/networking/networking_service.py b/prowler/providers/linode/services/networking/networking_service.py
new file mode 100644
index 0000000000..97f811a98a
--- /dev/null
+++ b/prowler/providers/linode/services/networking/networking_service.py
@@ -0,0 +1,127 @@
+from typing import List, Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.linode.lib.service.service import LinodeService
+
+
+class FirewallRule(BaseModel):
+ """Model for a single firewall rule."""
+
+ protocol: str = "TCP"
+ ports: str = "" # e.g. "22", "1-65535", ""
+ addresses_ipv4: List[str] = []
+ addresses_ipv6: List[str] = []
+ action: str = "ACCEPT" # ACCEPT or DROP
+ label: str = ""
+
+
+class Firewall(BaseModel):
+ """Model for a Linode Cloud Firewall."""
+
+ id: int
+ label: str
+ status: str
+ inbound_rules: List[FirewallRule] = []
+ outbound_rules: List[FirewallRule] = []
+ inbound_policy: str
+ outbound_policy: str
+ # None means the device count could not be determined (fetch failed), as
+ # opposed to 0 which means the firewall genuinely has no devices attached.
+ attached_devices_count: Optional[int] = None
+ tags: List[str] = []
+
+
+class NetworkingService(LinodeService):
+ """Service to interact with Linode Cloud Firewalls."""
+
+ def __init__(self, provider):
+ super().__init__("networking", provider)
+ self.firewalls: List[Firewall] = []
+ self._describe_firewalls()
+
+ def _describe_firewalls(self):
+ """Fetch all Linode Cloud Firewalls with their rules."""
+ try:
+ raw_firewalls = self.client.networking.firewalls()
+ for fw in raw_firewalls:
+ try:
+ inbound_rules = []
+ outbound_rules = []
+ inbound_policy = ""
+ outbound_policy = ""
+ attached_devices_count = None
+
+ try:
+ attached_devices_count = len(fw.devices)
+ except Exception as error:
+ logger.warning(
+ f"firewall - Unable to fetch devices for firewall {fw.id}: {error}"
+ )
+
+ try:
+ # linode_api4 Firewall objects expose rules as a mapped object.
+ rules = fw.rules
+ inbound_policy = getattr(rules, "inbound_policy", "")
+ outbound_policy = getattr(rules, "outbound_policy", "")
+ inbound = getattr(rules, "inbound", [])
+ outbound = getattr(rules, "outbound", [])
+
+ for rule in inbound:
+ addresses = getattr(rule, "addresses", None)
+ inbound_rules.append(
+ FirewallRule(
+ protocol=(
+ getattr(rule, "protocol", None) or "TCP"
+ ).upper(),
+ ports=getattr(rule, "ports", "") or "",
+ addresses_ipv4=getattr(addresses, "ipv4", []) or [],
+ addresses_ipv6=getattr(addresses, "ipv6", []) or [],
+ action=(
+ getattr(rule, "action", None) or "ACCEPT"
+ ).upper(),
+ label=getattr(rule, "label", "") or "",
+ )
+ )
+ for rule in outbound:
+ addresses = getattr(rule, "addresses", None)
+ outbound_rules.append(
+ FirewallRule(
+ protocol=(
+ getattr(rule, "protocol", None) or "TCP"
+ ).upper(),
+ ports=getattr(rule, "ports", "") or "",
+ addresses_ipv4=getattr(addresses, "ipv4", []) or [],
+ addresses_ipv6=getattr(addresses, "ipv6", []) or [],
+ action=(
+ getattr(rule, "action", None) or "ACCEPT"
+ ).upper(),
+ label=getattr(rule, "label", "") or "",
+ )
+ )
+ except Exception as error:
+ logger.warning(
+ f"firewall - Unable to fetch rules for firewall {fw.id}: {error}"
+ )
+
+ self.firewalls.append(
+ Firewall(
+ id=fw.id,
+ label=fw.label or f"firewall-{fw.id}",
+ status=fw.status or "unknown",
+ inbound_rules=inbound_rules,
+ outbound_rules=outbound_rules,
+ inbound_policy=inbound_policy,
+ outbound_policy=outbound_policy,
+ attached_devices_count=attached_devices_count,
+ tags=fw.tags or [],
+ )
+ )
+ except Exception as error:
+ logger.error(
+ f"firewall - Error processing firewall {fw.id}: "
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ except Exception as error:
+ self._log_fetch_error("firewalls", "firewall:read_only", error)
diff --git a/prowler/providers/m365/lib/powershell/m365_powershell.py b/prowler/providers/m365/lib/powershell/m365_powershell.py
index 9cc7207f20..d9cbdcee90 100644
--- a/prowler/providers/m365/lib/powershell/m365_powershell.py
+++ b/prowler/providers/m365/lib/powershell/m365_powershell.py
@@ -104,8 +104,11 @@ class M365PowerShell(PowerShellSession):
authentication information.
Note:
- The credentials are sanitized to prevent command injection and
- stored securely in the PowerShell session.
+ ``client_id`` and ``tenant_id`` are sanitized via ``sanitize()`` since
+ they are UUIDs. ``client_secret`` is assigned with a single-quoted
+ string (escaping any embedded single quote as ``''``) following
+ PowerShell best practices for literal values, so its content is taken
+ verbatim with no variable expansion or subexpression evaluation.
"""
# Certificate Auth
if credentials.certificate_content and credentials.client_id:
@@ -135,9 +138,16 @@ class M365PowerShell(PowerShellSession):
else:
# Application Auth
- self.execute(f'$clientID = "{credentials.client_id}"')
- self.execute(f'$clientSecret = "{credentials.client_secret}"')
- self.execute(f'$tenantID = "{credentials.tenant_id}"')
+ sanitized_client_id = self.sanitize(credentials.client_id)
+ sanitized_tenant_id = self.sanitize(credentials.tenant_id)
+ self.execute(f"$clientID = '{sanitized_client_id}'")
+ # Single-quoted strings are the PowerShell convention for literals:
+ # the content is taken verbatim with no variable expansion. Escape any
+ # embedded single quote as '' and do not sanitize() so the value is
+ # preserved exactly.
+ sanitized_secret = (credentials.client_secret or "").replace("'", "''")
+ self.execute(f"$clientSecret = '{sanitized_secret}'")
+ self.execute(f"$tenantID = '{sanitized_tenant_id}'")
self.execute(
'$graphtokenBody = @{ Grant_Type = "client_credentials"; Scope = "https://graph.microsoft.com/.default"; Client_Id = $clientID; Client_Secret = $clientSecret }'
)
@@ -196,7 +206,7 @@ class M365PowerShell(PowerShellSession):
"""Test Exchange Online API connection and raise exception if it fails."""
try:
self.execute(
- '$SecureSecret = ConvertTo-SecureString "$clientSecret" -AsPlainText -Force'
+ "$SecureSecret = ConvertTo-SecureString $clientSecret -AsPlainText -Force"
)
self.execute(
'$exchangeToken = Get-MsalToken -clientID "$clientID" -tenantID "$tenantID" -clientSecret $SecureSecret -Scopes "https://outlook.office365.com/.default"'
@@ -940,6 +950,32 @@ class M365PowerShell(PowerShellSession):
"Get-TeamsProtectionPolicy | ConvertTo-Json -Depth 10", json_parse=True
)
+ def get_mailboxes(self) -> dict:
+ """
+ Get Exchange Online Recipient-Facing Mailboxes.
+
+ Retrieves all recipient-facing mailboxes from Exchange Online with the
+ properties needed to evaluate primary SMTP domain policy.
+
+ Returns:
+ dict: Mailbox information in JSON format.
+
+ Example:
+ >>> get_mailboxes()
+ [
+ {
+ "Identity": "user1@contoso.com",
+ "DisplayName": "User One",
+ "PrimarySmtpAddress": "user1@contoso.com",
+ "RecipientTypeDetails": "UserMailbox"
+ }
+ ]
+ """
+ return self.execute(
+ "Get-EXOMailbox -ResultSize Unlimited | Select-Object Identity, DisplayName, PrimarySmtpAddress, RecipientTypeDetails | ConvertTo-Json -Depth 10",
+ json_parse=True,
+ )
+
def get_shared_mailboxes(self) -> dict:
"""
Get Exchange Online Shared Mailboxes.
@@ -966,6 +1002,31 @@ class M365PowerShell(PowerShellSession):
json_parse=True,
)
+ def get_application_access_policies(self) -> dict:
+ """
+ Get Exchange Online Application Access Policies.
+
+ Retrieves all Exchange Online Application Access Policies.
+
+ Returns:
+ dict: Application access policies in JSON format.
+
+ Example:
+ >>> get_application_access_policies()
+ [
+ {
+ "Identity": "Policy1",
+ "AppId": "12345678-1234-1234-1234-123456789012",
+ "AccessRight": "RestrictAccess",
+ "Description": "Restrict mailbox access"
+ }
+ ]
+ """
+ return self.execute(
+ "Get-ApplicationAccessPolicy | ConvertTo-Json -Depth 10",
+ json_parse=True,
+ )
+
def get_user_account_status(self) -> dict:
"""
Get User Account Status.
diff --git a/prowler/providers/m365/m365_provider.py b/prowler/providers/m365/m365_provider.py
index 0e3a6c2b26..040e390658 100644
--- a/prowler/providers/m365/m365_provider.py
+++ b/prowler/providers/m365/m365_provider.py
@@ -99,6 +99,7 @@ class M365Provider(Provider):
"""
_type: str = "m365"
+ sdk_only: bool = False
_session: DefaultAzureCredential # Must be used besides being named for Azure
_identity: M365IdentityInfo
_audit_config: dict
@@ -1073,7 +1074,7 @@ class M365Provider(Provider):
organization_info = await client.organization.get()
identity.tenant_id = organization_info.value[0].id
- asyncio.get_event_loop().run_until_complete(get_m365_identity(identity))
+ asyncio.run(get_m365_identity(identity))
return identity
@staticmethod
@@ -1261,9 +1262,7 @@ class M365Provider(Provider):
result = await client.domains.get()
return result.value
- result = asyncio.get_event_loop().run_until_complete(
- verify_certificate()
- )
+ result = asyncio.run(verify_certificate())
if not result:
raise M365NotValidCertificateContentError(
file=os.path.basename(__file__),
@@ -1284,9 +1283,7 @@ class M365Provider(Provider):
result = await client.domains.get()
return result.value
- result = asyncio.get_event_loop().run_until_complete(
- verify_certificate()
- )
+ result = asyncio.run(verify_certificate())
if not result:
raise M365NotValidCertificatePathError(
file=os.path.basename(__file__),
diff --git a/prowler/providers/m365/services/admincenter/admincenter_service.py b/prowler/providers/m365/services/admincenter/admincenter_service.py
index 45be16d11a..3899dced67 100644
--- a/prowler/providers/m365/services/admincenter/admincenter_service.py
+++ b/prowler/providers/m365/services/admincenter/admincenter_service.py
@@ -175,17 +175,23 @@ class AdminCenter(M365Service):
try:
groups_list = await self.client.groups.get()
groups.update({})
- for group in groups_list.value:
- groups.update(
- {
- group.id: Group(
- id=group.id,
- name=getattr(group, "display_name", ""),
- visibility=getattr(group, "visibility", ""),
- group_types=getattr(group, "group_types", []) or [],
- )
- }
- )
+ while groups_list:
+ for group in getattr(groups_list, "value", []) or []:
+ groups.update(
+ {
+ group.id: Group(
+ id=group.id,
+ name=getattr(group, "display_name", ""),
+ visibility=getattr(group, "visibility", ""),
+ group_types=getattr(group, "group_types", []) or [],
+ )
+ }
+ )
+
+ next_link = getattr(groups_list, "odata_next_link", None)
+ if not next_link:
+ break
+ groups_list = await self.client.groups.with_url(next_link).get()
except Exception as error:
logger.error(
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/__init__.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.metadata.json b/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.metadata.json
new file mode 100644
index 0000000000..c352854003
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.metadata.json
@@ -0,0 +1,43 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_conditional_access_policy_explicitly_targets_azure_devops",
+ "CheckTitle": "Conditional Access Policy explicitly targets Azure DevOps",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Microsoft Entra **Conditional Access** is verified to have at least one **enabled** policy that explicitly includes the **Azure DevOps** cloud application. Policies targeting **All** cloud apps do not satisfy this check because the goal is to verify that Azure DevOps has been deliberately considered.",
+ "Risk": "Without an explicit Conditional Access policy for Azure DevOps, organizations may rely on broad policies that do not account for Azure DevOps-specific access patterns such as CLI, IDE plug-ins, PAT-based workflows, source code access, build pipelines, secrets, and service connections.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccesspolicy?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccessapplications?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/manage-conditional-access",
+ "https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/governance/verify-first-party-apps-sign-in"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Navigate to the Microsoft Entra admin center (https://entra.microsoft.com).\n2. Expand **Protection** > **Conditional Access** and select **Policies**.\n3. Create or edit a policy for Azure DevOps.\n4. Under **Target resources**, select **Include** > **Select apps** and choose **Azure DevOps**.\n5. Configure the required grant or session controls for your organization.\n6. Set the policy to **Report-only** until validated, then enable it.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Create and enable a Conditional Access policy that explicitly includes the Azure DevOps cloud application, then configure the appropriate access controls for your organization.",
+ "Url": "https://hub.prowler.com/check/entra_conditional_access_policy_explicitly_targets_azure_devops"
+ }
+ },
+ "Categories": [
+ "identity-access",
+ "trust-boundaries",
+ "e3"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "entra_conditional_access_policy_all_apps_all_users"
+ ],
+ "Notes": "Azure DevOps Services uses appId 499b84ac-1321-427f-aa17-267ca6975798."
+}
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.py
new file mode 100644
index 0000000000..f1e874fc91
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_explicitly_targets_azure_devops/entra_conditional_access_policy_explicitly_targets_azure_devops.py
@@ -0,0 +1,57 @@
+"""Check if a Conditional Access policy explicitly targets Azure DevOps."""
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+from prowler.providers.m365.services.entra.entra_service import (
+ ConditionalAccessPolicyState,
+)
+
+AZURE_DEVOPS_APP_ID = "499b84ac-1321-427f-aa17-267ca6975798"
+
+
+class entra_conditional_access_policy_explicitly_targets_azure_devops(Check):
+ """Check that an enabled Conditional Access policy explicitly targets Azure DevOps."""
+
+ def execute(self) -> list[CheckReportM365]:
+ """Execute the check for explicit Azure DevOps targeting.
+
+ Returns:
+ A list of reports containing the result of the check.
+ """
+ findings = []
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource={},
+ resource_name="Conditional Access Policies",
+ resource_id="conditionalAccessPolicies",
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ "No enabled Conditional Access Policy explicitly targets Azure DevOps."
+ )
+
+ for policy in entra_client.conditional_access_policies.values():
+ if policy.state != ConditionalAccessPolicyState.ENABLED:
+ continue
+
+ if not policy.conditions.application_conditions:
+ continue
+
+ if (
+ AZURE_DEVOPS_APP_ID
+ not in policy.conditions.application_conditions.included_applications
+ ):
+ continue
+
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=policy,
+ resource_name=policy.display_name,
+ resource_id=policy.id,
+ )
+ report.status = "PASS"
+ report.status_extended = f"Conditional Access Policy {policy.display_name} explicitly targets Azure DevOps."
+ break
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/__init__.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.metadata.json b/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.metadata.json
new file mode 100644
index 0000000000..ccfa9eb086
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_conditional_access_policy_groups_management_restricted",
+ "CheckTitle": "Conditional Access policy groups are management-restricted or role-assignable",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Microsoft Entra **Conditional Access** policies are evaluated for security groups referenced in `includeGroups` and `excludeGroups`. Referenced groups must be protected by **Restricted Management Administrative Unit** membership or configured as **role-assignable groups**.",
+ "Risk": "Groups referenced by **Conditional Access** policies become privileged identity control points. If their membership can be changed by broad group administrators or applications, an attacker may bypass access controls by adding themselves to an excluded group or removing themselves from an included group, weakening **confidentiality** and **integrity** without modifying the policy.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccesspolicy?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/resources/group?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/admin-units-restricted-management",
+ "https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/groups-concept"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Microsoft Entra admin center at https://entra.microsoft.com.\n2. Review every group used by enabled or report-only Conditional Access policies under Users > Include and Users > Exclude.\n3. For each group, either place it in a Restricted Management Administrative Unit or recreate/use a role-assignable group where appropriate.\n4. Restrict group ownership and membership management to privileged administrators.\n5. Remove stale or deleted group references from Conditional Access policies.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Protect every security group that scopes **Conditional Access** decisions with **Restricted Management Administrative Units** or **role-assignable group** controls. Regularly audit group membership, owners, and stale Conditional Access references.",
+ "Url": "https://hub.prowler.com/check/entra_conditional_access_policy_groups_management_restricted"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Conditional Access policies require Microsoft Entra ID P1 or P2 licenses. The check relies on Microsoft Graph group properties `isManagementRestricted` and `isAssignableToRole`, which must be requested with `$select`."
+}
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.py
new file mode 100644
index 0000000000..884f065257
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_groups_management_restricted/entra_conditional_access_policy_groups_management_restricted.py
@@ -0,0 +1,130 @@
+from collections import defaultdict
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+from prowler.providers.m365.services.entra.entra_service import (
+ ConditionalAccessPolicyState,
+)
+
+
+class entra_conditional_access_policy_groups_management_restricted(Check):
+ """Ensure Conditional Access group scopes are protected against broad management.
+
+ Security groups referenced by enabled or report-only Conditional Access
+ policies (in ``includeGroups`` or ``excludeGroups``) are privileged control
+ points: anyone able to change their membership can silently bypass or weaken
+ a policy. This check reports one finding per referenced group.
+
+ - PASS: The group is management-restricted or role-assignable, or no enabled
+ or report-only policy references any group.
+ - FAIL: The group is neither management-restricted nor role-assignable.
+ - MANUAL: The group reference no longer resolves in Microsoft Entra ID and
+ must be verified or removed.
+ """
+
+ def execute(self) -> list[CheckReportM365]:
+ """Execute the check logic.
+
+ Returns:
+ A list of reports, one per group referenced by an enabled or
+ report-only Conditional Access policy.
+ """
+ findings = []
+
+ group_usage = defaultdict(lambda: {"include": [], "exclude": []})
+
+ for policy in entra_client.conditional_access_policies.values():
+ if policy.state == ConditionalAccessPolicyState.DISABLED:
+ continue
+
+ user_conditions = policy.conditions.user_conditions
+ if not user_conditions:
+ continue
+
+ for group_id in user_conditions.included_groups:
+ group_usage[group_id]["include"].append(policy)
+ for group_id in user_conditions.excluded_groups:
+ group_usage[group_id]["exclude"].append(policy)
+
+ if not group_usage:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource={},
+ resource_name="Conditional Access Policies",
+ resource_id="conditionalAccessPolicies",
+ )
+ report.status = "PASS"
+ report.status_extended = (
+ "No enabled or report-only Conditional Access Policy references "
+ "groups."
+ )
+ findings.append(report)
+ return findings
+
+ groups_by_id = {group.id: group for group in entra_client.groups}
+
+ for group_id in sorted(group_usage):
+ usage = self._policy_usage(group_usage[group_id])
+ group = groups_by_id.get(group_id)
+
+ if not group:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource={},
+ resource_name=group_id,
+ resource_id=group_id,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Group {group_id} referenced by Conditional Access Policies "
+ f"could not be resolved in Microsoft Entra ID; verify the group "
+ f"exists or remove the stale reference ({usage})."
+ )
+ findings.append(report)
+ continue
+
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=group,
+ resource_name=group.name,
+ resource_id=group.id,
+ )
+
+ if group.is_management_restricted or group.is_assignable_to_role:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Group {group.name} ({group.id}) referenced by Conditional "
+ f"Access Policies is management-restricted or role-assignable."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Group {group.name} ({group.id}) referenced by Conditional "
+ f"Access Policies is neither management-restricted nor "
+ f"role-assignable ({usage})."
+ )
+
+ findings.append(report)
+
+ return findings
+
+ @staticmethod
+ def _policy_usage(usage) -> str:
+ """Render the include/exclude policy usage of a group as a string.
+
+ Args:
+ usage: Mapping with ``include`` and ``exclude`` lists of policies.
+
+ Returns:
+ A string such as ``"include policies: A; exclude policies: B"``.
+ """
+
+ def policy_names(policies):
+ if not policies:
+ return "none"
+ return ", ".join(sorted({policy.display_name for policy in policies}))
+
+ return (
+ f"include policies: {policy_names(usage['include'])}; "
+ f"exclude policies: {policy_names(usage['exclude'])}"
+ )
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/__init__.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.metadata.json b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.metadata.json
new file mode 100644
index 0000000000..42b3acaeb6
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.metadata.json
@@ -0,0 +1,44 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_conditional_access_policy_no_deleted_object_references",
+ "CheckTitle": "Conditional Access policies must not reference deleted users, groups, or roles",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every object identifier referenced by any Conditional Access policy under conditions.users (includeUsers, excludeUsers, includeGroups, excludeGroups, includeRoles, excludeRoles) must resolve to an existing Microsoft Entra object. This check audits all Conditional Access policies regardless of state and reports any whose user, group, or role references no longer resolve in the directory.",
+ "Risk": "When a user, group, or directory role referenced by a Conditional Access policy stops resolving (account or group deleted, role template removed), the reference becomes orphaned. include* references silently shrink the policy's enforcement scope; exclude* references can cause the policy to evaluate unexpectedly. This is a common root cause of MFA-not-applied incidents.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccesspolicy?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccessusers?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/group-get?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/unifiedroledefinition-get?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-users-groups"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Microsoft Entra admin center (https://entra.microsoft.com)\n2. Navigate to Protection > Conditional Access > Policies\n3. Open each policy reported by this check\n4. Under Assignments > Users, remove every user, group, or role identifier reported as deleted\n5. Save the policy and re-run the audit\n6. For ongoing hygiene, audit Conditional Access policies after any bulk user/group/role cleanup",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Audit each Conditional Access policy quarterly and remove references to deleted users, groups, or directory roles. Stale references in include collections silently shrink enforcement scope; stale references in exclude collections can cause policies to behave unexpectedly. Treat both as misconfigurations regardless of policy state.",
+ "Url": "https://hub.prowler.com/check/entra_conditional_access_policy_no_deleted_object_references"
+ }
+ },
+ "Categories": [
+ "identity-access",
+ "e3"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "entra_conditional_access_policy_directory_sync_account_excluded"
+ ],
+ "Notes": "The check runs against all Conditional Access policies regardless of state (enabled, disabled, enabledForReportingButNotEnforced) — stale references in disabled policies are a misconfiguration that becomes live the moment the policy is re-enabled. Only HTTP 404 responses flag an identifier as deleted (FAIL). Transient Graph errors (5xx, throttling, insufficient permissions) are not treated as deletions; a policy whose references could not be resolved for those reasons is reported as MANUAL so it is not silently considered clean."
+}
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.py
new file mode 100644
index 0000000000..e5c5eff389
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_deleted_object_references/entra_conditional_access_policy_no_deleted_object_references.py
@@ -0,0 +1,157 @@
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+from prowler.providers.m365.services.entra.entra_service import (
+ CONDITIONAL_ACCESS_SENTINEL_IDS,
+ ConditionalAccessPolicyState,
+)
+
+
+class entra_conditional_access_policy_no_deleted_object_references(Check):
+ """
+ Ensure Conditional Access policies do not reference deleted directory objects.
+
+ Stale references to deleted users, groups, or directory roles silently change
+ the runtime behavior of a Conditional Access policy: include* references
+ shrink enforcement scope, exclude* references can change exemption logic.
+ Either way, the policy stops behaving the way the operator believes it does.
+
+ The directory-object existence check runs once at service init time and is
+ cached on the entra client. This check reads from that cache and reports any
+ policy whose users/groups/roles inclusion or exclusion collections name an
+ identifier that no longer resolves in Microsoft Entra ID.
+
+ Identifiers whose Graph lookup failed with a non-404 error (5xx, throttling,
+ insufficient permissions) are cached separately: they could not be verified
+ as present or deleted, so the policy is reported as MANUAL rather than being
+ silently treated as clean.
+
+ - PASS: The policy references no deleted users, groups, or roles.
+ - FAIL: The policy references at least one deleted user, group, or role.
+ - MANUAL: At least one referenced identifier could not be resolved due to a
+ transient Graph error, so the policy could not be fully evaluated.
+ """
+
+ def execute(self) -> list[CheckReportM365]:
+ findings = []
+ unresolved = entra_client.unresolved_directory_object_references
+ errored = entra_client.errored_directory_object_references
+
+ for policy_id, policy in entra_client.conditional_access_policies.items():
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=policy,
+ resource_name=policy.display_name,
+ resource_id=policy_id,
+ )
+
+ orphans = self._collect_references_in(policy, unresolved)
+ unverified = self._collect_references_in(policy, errored)
+
+ if orphans:
+ # A confirmed deletion takes precedence over unverified ones.
+ report.status = "FAIL"
+ report.status_extended = self._format_failure(
+ policy.display_name, orphans, unverified, policy.state
+ )
+ elif unverified:
+ # Nothing confirmed deleted, but we could not verify every
+ # reference — do not claim the policy is clean.
+ report.status = "MANUAL"
+ report.status_extended = self._format_manual(
+ policy.display_name, unverified
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Conditional Access policy {policy.display_name} references no "
+ f"deleted directory objects."
+ )
+
+ findings.append(report)
+
+ return findings
+
+ @staticmethod
+ def _collect_references_in(policy, id_set):
+ """Walk the six identifier collections and return references in ``id_set``.
+
+ Args:
+ policy: The Conditional Access policy to inspect.
+ id_set: Set of ``(type, id)`` pairs to match references against.
+
+ Returns:
+ list[tuple[str, str, str]]: ``(type, id, side)`` tuples where
+ ``type`` is one of ``user|group|role``, ``id`` is the Graph
+ identifier, and ``side`` is one of ``include|exclude``.
+ """
+ if not policy.conditions or not policy.conditions.user_conditions:
+ return []
+
+ uc = policy.conditions.user_conditions
+ collections = (
+ ("user", "include", uc.included_users),
+ ("user", "exclude", uc.excluded_users),
+ ("group", "include", uc.included_groups),
+ ("group", "exclude", uc.excluded_groups),
+ ("role", "include", uc.included_roles),
+ ("role", "exclude", uc.excluded_roles),
+ )
+
+ matches = []
+ for type_, side, identifiers in collections:
+ for identifier in identifiers:
+ if identifier in CONDITIONAL_ACCESS_SENTINEL_IDS:
+ continue
+ if (type_, identifier) in id_set:
+ matches.append((type_, identifier, side))
+ return matches
+
+ @staticmethod
+ def _group_by_type(references):
+ """Group ``(type, id, side)`` references into a deterministic message part."""
+ by_type = {"user": [], "group": [], "role": []}
+ for type_, identifier, side in references:
+ by_type[type_].append(f"{identifier} ({side})")
+
+ parts = []
+ for type_ in ("user", "group", "role"):
+ if by_type[type_]:
+ joined = ", ".join(sorted(by_type[type_]))
+ parts.append(f"{type_}s: {joined}")
+ return "; ".join(parts)
+
+ @classmethod
+ def _format_failure(cls, display_name, orphans, unverified, state=None):
+ # Surface report-only mode explicitly: the stale references are not yet
+ # enforced, but become live the moment the policy is turned on.
+ report_only = (
+ " The policy is in report-only mode, so these references are not "
+ "enforced yet but will take effect once it is enabled."
+ if state == ConditionalAccessPolicyState.ENABLED_FOR_REPORTING
+ else ""
+ )
+
+ # If some references also could not be resolved, say so rather than
+ # implying the rest of the policy is fully clean.
+ unverified_note = (
+ f" Additionally, {len(unverified)} reference(s) could not be verified "
+ f"due to transient Microsoft Graph errors."
+ if unverified
+ else ""
+ )
+
+ return (
+ f"Conditional Access policy {display_name} references "
+ f"{len(orphans)} deleted directory object(s) — "
+ f"{cls._group_by_type(orphans)}.{report_only}{unverified_note}"
+ )
+
+ @classmethod
+ def _format_manual(cls, display_name, unverified):
+ return (
+ f"Conditional Access policy {display_name} could not be fully evaluated: "
+ f"{len(unverified)} reference(s) could not be resolved due to transient "
+ f"Microsoft Graph errors (5xx, throttling, or insufficient permissions) — "
+ f"{cls._group_by_type(unverified)}. Re-run the scan or review the policy "
+ f"manually."
+ )
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/__init__.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.metadata.json b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.metadata.json
new file mode 100644
index 0000000000..35c80b8054
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.metadata.json
@@ -0,0 +1,42 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_conditional_access_policy_no_exclusion_gaps",
+ "CheckTitle": "Conditional Access exclusions are covered by another policy (no exclusion gaps)",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Verifies that every object excluded from an enabled Microsoft Entra **Conditional Access** policy (users, groups, roles, or applications) is still included by at least one enabled policy, so the exclusion keeps a compensating control. The Directory Synchronization Accounts role and confirmed emergency access (break glass) accounts are treated as intentional and not reported.",
+ "Risk": "An object excluded from a Conditional Access policy but never included by any other enabled policy sits completely outside Conditional Access enforcement. This creates a silent **MFA bypass** and **lateral movement** path: a principal exempted as a one-off remains permanently uncontrolled if no compensating policy covers it.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/entra/identity/conditional-access/plan-conditional-access",
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccesspolicy?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/resources/conditionalaccessusers?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Navigate to Protection > Conditional Access > Policies in the Microsoft Entra admin center.\n2. For each object reported as an exclusion gap, decide whether the exclusion is still required.\n3. If the exclusion must stay, add the object to the Include scope of another enabled Conditional Access policy that enforces compensating controls (for example MFA).\n4. If the exclusion is no longer required, remove it so the object falls back under the original policy.\n5. Re-run the check to confirm no exclusion gaps remain.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Ensure every object excluded from a Conditional Access policy is included by at least one other enabled policy that applies compensating controls. Reserve exclusions for break-glass accounts and the Directory Synchronization Accounts role, and review exclusion lists regularly so that exempted principals never drift outside Conditional Access enforcement.",
+ "Url": "https://hub.prowler.com/check/entra_conditional_access_policy_no_exclusion_gaps"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "entra_conditional_access_policy_directory_sync_account_excluded",
+ "entra_emergency_access_exclusion"
+ ],
+ "Notes": "Covers user, group, role, and application exclusions. Platform and location exclusions are out of scope because they are scoping conditions rather than principals removed from enforcement. Service-principal exclusions require additional fields on the ConditionalAccessPolicy service model."
+}
diff --git a/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.py b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.py
new file mode 100644
index 0000000000..0974581759
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_conditional_access_policy_no_exclusion_gaps/entra_conditional_access_policy_no_exclusion_gaps.py
@@ -0,0 +1,262 @@
+"""Check that Conditional Access exclusions do not create coverage gaps."""
+
+from collections import Counter, defaultdict
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+from prowler.providers.m365.services.entra.entra_service import (
+ ConditionalAccessGrantControl,
+ ConditionalAccessPolicyState,
+)
+
+# Directory Synchronization Accounts built-in role template ID. Prowler enforces
+# excluding this role (see entra_conditional_access_policy_directory_sync_account_excluded);
+# it is intended to have no fallback, so it never counts as a gap here.
+DIRECTORY_SYNC_ROLE_TEMPLATE_ID = "d29b2b05-8046-44ba-8758-1e26182fcf32"
+
+
+class entra_conditional_access_policy_no_exclusion_gaps(Check):
+ """Check that objects excluded from Conditional Access policies remain covered.
+
+ Excluding a principal from a Conditional Access (CA) policy is only safe when
+ that principal is still covered by *some* enabled CA policy that enforces
+ compensating controls. An object excluded everywhere and included nowhere
+ sits completely outside CA enforcement, which is how MFA bypass and lateral
+ movement against admin accounts happen in real incidents.
+
+ For every enabled CA policy this check walks each exclusion collection and
+ verifies the excluded object is still in scope of another enabled policy: one
+ that includes it (explicitly, or via the "All" wildcard) and does not itself
+ exclude it. A wildcard belonging to the policy that excludes the object does
+ not count, so a one-off exclusion with no compensating policy is reported as
+ a gap.
+
+ Only principals and target apps are evaluated (users, groups, roles,
+ applications). Platform and location exclusions are scoping conditions rather
+ than principals removed from enforcement, so they are out of scope.
+
+ - PASS: Every excluded object stays in scope of another enabled policy, or no
+ enabled policy uses any exclusion.
+ - FAIL: At least one excluded object is in scope of no other enabled policy.
+ """
+
+ # (label, conditions attribute, included attr, excluded attr, wildcard token).
+ # The wildcard token, when present in an include collection, scopes a policy
+ # to every object of that type. Groups and roles have no wildcard: they are
+ # always explicit identifiers and transitive group/role expansion is out of
+ # scope for v1, so an excluded group/role is only "covered" when the same
+ # identifier is explicitly included by another enabled policy.
+ _COLLECTIONS = [
+ ("users", "user_conditions", "included_users", "excluded_users", "All"),
+ ("groups", "user_conditions", "included_groups", "excluded_groups", None),
+ ("roles", "user_conditions", "included_roles", "excluded_roles", None),
+ (
+ "applications",
+ "application_conditions",
+ "included_applications",
+ "excluded_applications",
+ "All",
+ ),
+ ]
+
+ def execute(self) -> list[CheckReportM365]:
+ """Execute the Conditional Access exclusion-gap check.
+
+ Returns:
+ list[CheckReportM365]: A single-element list with the aggregate result.
+ """
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource={},
+ resource_name="Conditional Access Policies",
+ resource_id="conditionalAccessPolicies",
+ )
+
+ enabled_policies = [
+ policy
+ for policy in entra_client.conditional_access_policies.values()
+ if policy.state == ConditionalAccessPolicyState.ENABLED
+ ]
+
+ if not enabled_policies:
+ report.status = "PASS"
+ report.status_extended = (
+ "No enabled Conditional Access policies found; "
+ "no exclusion coverage gaps are possible."
+ )
+ return [report]
+
+ emergency_users, emergency_groups = self._emergency_access_objects()
+
+ # gaps: type label -> set of excluded object IDs with no compensating policy
+ gaps = defaultdict(set)
+ any_exclusion = False
+
+ for policy in enabled_policies:
+ for (
+ label,
+ conditions_attr,
+ included_attr,
+ excluded_attr,
+ wildcard,
+ ) in self._COLLECTIONS:
+ conditions = getattr(policy.conditions, conditions_attr)
+ if not conditions:
+ continue
+ for object_id in getattr(conditions, excluded_attr):
+ any_exclusion = True
+ if self._is_expected_exclusion(
+ label, object_id, emergency_users, emergency_groups
+ ):
+ continue
+ if not self._is_covered(
+ object_id,
+ conditions_attr,
+ included_attr,
+ excluded_attr,
+ wildcard,
+ enabled_policies,
+ ):
+ gaps[label].add(object_id)
+
+ if not any_exclusion:
+ report.status = "PASS"
+ report.status_extended = (
+ "No enabled Conditional Access policy uses exclusions; "
+ "no coverage gaps are possible."
+ )
+ return [report]
+
+ if not gaps:
+ report.status = "PASS"
+ report.status_extended = (
+ "Every object excluded from an enabled Conditional Access policy is "
+ "still in scope of another enabled policy, so a compensating control "
+ "remains in effect."
+ )
+ return [report]
+
+ report.status = "FAIL"
+ report.status_extended = (
+ "Conditional Access exclusion gaps found "
+ f"({self._format_gaps(gaps, self._build_name_index())}). These objects "
+ "are excluded but in scope of no other enabled policy, leaving them "
+ "outside CA enforcement."
+ )
+ return [report]
+
+ def _build_name_index(self) -> dict:
+ """Map excluded object IDs to display names per type, for readable findings.
+
+ Users, groups, and applications resolve to their display name; roles have
+ no loaded name catalog, so role template IDs are shown as-is. Unresolved
+ IDs (for example deleted principals still referenced by a policy) fall
+ back to the raw identifier.
+ """
+ users = {
+ uid: user.name
+ for uid, user in (getattr(entra_client, "users", {}) or {}).items()
+ if getattr(user, "name", None)
+ }
+ groups = {
+ group.id: group.name
+ for group in (getattr(entra_client, "groups", []) or [])
+ if getattr(group, "name", None)
+ }
+ applications = {
+ sp.app_id: sp.name
+ for sp in (getattr(entra_client, "service_principals", {}) or {}).values()
+ if getattr(sp, "app_id", None) and getattr(sp, "name", None)
+ }
+ return {"users": users, "groups": groups, "applications": applications}
+
+ def _is_covered(
+ self,
+ object_id,
+ conditions_attr,
+ included_attr,
+ excluded_attr,
+ wildcard,
+ enabled_policies,
+ ) -> bool:
+ """Return True if any enabled policy keeps ``object_id`` in scope.
+
+ A policy keeps the object in scope when it includes it —explicitly or via
+ the type's wildcard token— and does not also exclude it. The wildcard of a
+ policy that itself excludes the object does not count, which is what makes
+ a one-off exclusion with no compensating policy a real gap.
+ """
+ for policy in enabled_policies:
+ conditions = getattr(policy.conditions, conditions_attr)
+ if not conditions:
+ continue
+ if object_id in getattr(conditions, excluded_attr):
+ continue
+ included = getattr(conditions, included_attr)
+ if object_id in included or (wildcard is not None and wildcard in included):
+ return True
+ return False
+
+ def _emergency_access_objects(self) -> tuple[set, set]:
+ """Return user and group IDs that act as emergency access (break-glass).
+
+ Objects excluded from *every* enabled (enforced) Conditional Access policy
+ with a Block grant control are intended, compensating gaps and must not be
+ reported here. Only ENABLED policies count: report-only policies are not
+ enforced, so including them would dilute the "excluded everywhere" check
+ and could hide a genuine break-glass account (consistent with execute()).
+ """
+ blocking_policies = [
+ policy
+ for policy in entra_client.conditional_access_policies.values()
+ if policy.state == ConditionalAccessPolicyState.ENABLED
+ and ConditionalAccessGrantControl.BLOCK
+ in policy.grant_controls.built_in_controls
+ ]
+ if not blocking_policies:
+ return set(), set()
+
+ total = len(blocking_policies)
+ excluded_users = Counter()
+ excluded_groups = Counter()
+ for policy in blocking_policies:
+ user_conditions = policy.conditions.user_conditions
+ if not user_conditions:
+ continue
+ for user_id in user_conditions.excluded_users:
+ excluded_users[user_id] += 1
+ for group_id in user_conditions.excluded_groups:
+ excluded_groups[group_id] += 1
+
+ emergency_users = {uid for uid, n in excluded_users.items() if n == total}
+ emergency_groups = {gid for gid, n in excluded_groups.items() if n == total}
+ return emergency_users, emergency_groups
+
+ def _is_expected_exclusion(
+ self, label, object_id, emergency_users, emergency_groups
+ ) -> bool:
+ """Exclusions that are intentional by design and must not count as gaps."""
+ if label == "roles" and object_id == DIRECTORY_SYNC_ROLE_TEMPLATE_ID:
+ return True
+ if label == "users" and object_id in emergency_users:
+ return True
+ if label == "groups" and object_id in emergency_groups:
+ return True
+ return False
+
+ def _format_gaps(self, gaps, name_index) -> str:
+ """Render the orphaned objects grouped by type, by display name when known.
+
+ Each ID is shown as its display name when resolvable; unresolved IDs (and
+ all roles, which have no name catalog) fall back to the raw identifier.
+ """
+ parts = []
+ for label in ("users", "groups", "roles", "applications"):
+ if label not in gaps:
+ continue
+ names = name_index.get(label, {})
+ rendered = sorted(
+ names.get(object_id, object_id) for object_id in gaps[label]
+ )
+ parts.append(f"{label}: {', '.join(rendered)}")
+ return " | ".join(parts)
diff --git a/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/__init__.py b/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.metadata.json b/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.metadata.json
new file mode 100644
index 0000000000..0cc14e2965
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.metadata.json
@@ -0,0 +1,42 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_directory_sync_object_takeover_blocked",
+ "CheckTitle": "Microsoft Entra directory sync must block object takeover (soft- and hard-matching)",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "When on-premises directory synchronization is enabled, both blockSoftMatchEnabled and blockCloudObjectTakeoverThroughHardMatchEnabled must be true. Without these blocks, an attacker who can write to on-premises AD can craft an object that matches a privileged cloud account and take it over.",
+ "Risk": "An attacker with write access to on-premises Active Directory can create an object whose UPN, SMTP address, or ImmutableID matches an existing cloud-only account (e.g. Global Administrator). When the sync engine processes this object, it merges the on-premises identity into the cloud account, effectively granting the attacker full control of that privileged account.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/resources/onpremisesdirectorysynchronization?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/resources/onpremisesdirectorysynchronizationfeature?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-syncservice-features"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Open Microsoft Entra admin center\n2. Navigate to Identity > Hybrid management > Microsoft Entra Connect > Connect Sync\n3. Enable 'Block soft match' and 'Block cloud object takeover through hard match'\n4. Alternatively, use Microsoft Graph API to set both features to true on the onPremisesDirectorySynchronization resource",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Enable both blockSoftMatchEnabled and blockCloudObjectTakeoverThroughHardMatchEnabled on the on-premises directory synchronization configuration. These should remain enabled permanently except during time-boxed migration windows.",
+ "Url": "https://hub.prowler.com/check/entra_directory_sync_object_takeover_blocked"
+ }
+ },
+ "Categories": [
+ "identity-access",
+ "e3"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "entra_password_hash_sync_enabled",
+ "entra_seamless_sso_disabled"
+ ],
+ "Notes": "This check only applies to hybrid tenants with on-premises directory synchronization enabled. Cloud-only tenants receive a PASS since the attack path does not exist."
+}
diff --git a/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.py b/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.py
new file mode 100644
index 0000000000..d1f00a70ff
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_directory_sync_object_takeover_blocked/entra_directory_sync_object_takeover_blocked.py
@@ -0,0 +1,118 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+
+
+class entra_directory_sync_object_takeover_blocked(Check):
+ """Check that directory sync blocks object takeover via soft-match and hard-match.
+
+ When on-premises directory synchronization is enabled, an attacker who can
+ write to on-premises AD can craft an object that matches a privileged cloud
+ account and take it over. Both blockSoftMatchEnabled and
+ blockCloudObjectTakeoverThroughHardMatchEnabled must be true to prevent this.
+
+ The attack path only exists on hybrid tenants, so the tenant's
+ organization.onPremisesSyncEnabled is evaluated first. Microsoft Graph
+ returns an onPremisesSynchronization object (with all features disabled) even
+ for cloud-only tenants, so the directory sync features must not be evaluated
+ unless on-premises synchronization is actually enabled.
+
+ - PASS: The tenant is cloud-only, or both block flags are enabled.
+ - FAIL: On-premises sync is enabled and either block flag is disabled.
+ - MANUAL: On-premises sync is enabled but the settings cannot be read
+ (insufficient permissions) or were not returned by Microsoft Graph.
+ """
+
+ def execute(self) -> List[CheckReportM365]:
+ findings = []
+
+ organizations = entra_client.organizations or []
+ on_premises_sync_enabled = any(
+ organization.on_premises_sync_enabled for organization in organizations
+ )
+
+ # Cloud-only tenant: the object takeover attack path does not exist, so
+ # the directory sync features are not evaluated even if Microsoft Graph
+ # returns an (all-disabled) onPremisesSynchronization object.
+ if organizations and not on_premises_sync_enabled:
+ for organization in organizations:
+ report = CheckReportM365(
+ self.metadata(),
+ resource=organization,
+ resource_id=organization.id,
+ resource_name=organization.name,
+ )
+ report.status = "PASS"
+ report.status_extended = (
+ f"Entra organization {organization.name} is cloud-only "
+ "(no on-premises sync), object takeover protection is not "
+ "applicable."
+ )
+ findings.append(report)
+ return findings
+
+ # Hybrid tenant but the directory sync settings could not be read.
+ if entra_client.directory_sync_error:
+ for organization in organizations:
+ report = CheckReportM365(
+ self.metadata(),
+ resource=organization,
+ resource_id=organization.id,
+ resource_name=organization.name,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Cannot verify object takeover protection for "
+ f"{organization.name}: {entra_client.directory_sync_error}."
+ )
+ findings.append(report)
+ return findings
+
+ for sync_settings in entra_client.directory_sync_settings:
+ report = CheckReportM365(
+ self.metadata(),
+ resource=sync_settings,
+ resource_id=sync_settings.id,
+ resource_name=f"Directory Sync {sync_settings.id}",
+ )
+
+ disabled_flags = []
+ if not sync_settings.block_soft_match_enabled:
+ disabled_flags.append("blockSoftMatchEnabled")
+ if not sync_settings.block_cloud_object_takeover_through_hard_match_enabled:
+ disabled_flags.append("blockCloudObjectTakeoverThroughHardMatchEnabled")
+
+ if not disabled_flags:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Entra directory sync {sync_settings.id} blocks both soft-match "
+ "and hard-match object takeover."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Entra directory sync {sync_settings.id} does not block object "
+ f"takeover: {', '.join(disabled_flags)} disabled."
+ )
+
+ findings.append(report)
+
+ # Hybrid tenant that reported on-premises sync but returned no settings.
+ if not entra_client.directory_sync_settings:
+ for organization in organizations:
+ report = CheckReportM365(
+ self.metadata(),
+ resource=organization,
+ resource_id=organization.id,
+ resource_name=organization.name,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Entra organization {organization.name} has on-premises sync "
+ "enabled, but no directory sync settings were returned. Review "
+ "the tenant configuration manually."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/m365/services/entra/entra_service.py b/prowler/providers/m365/services/entra/entra_service.py
index a09ee32da0..a083eb1c3c 100644
--- a/prowler/providers/m365/services/entra/entra_service.py
+++ b/prowler/providers/m365/services/entra/entra_service.py
@@ -1,16 +1,15 @@
import asyncio
+import importlib
import json
from asyncio import gather
from datetime import datetime, timezone
from enum import Enum
-from typing import Any, Dict, List, Optional, Tuple
+from typing import Any, Dict, List, Optional, Set, Tuple
from uuid import UUID
from kiota_abstractions.base_request_configuration import RequestConfiguration
+from msgraph.generated.groups.groups_request_builder import GroupsRequestBuilder
from msgraph.generated.models.o_data_errors.o_data_error import ODataError
-from msgraph.generated.security.microsoft_graph_security_run_hunting_query.run_hunting_query_post_request_body import (
- RunHuntingQueryPostRequestBody,
-)
from msgraph.generated.users.users_request_builder import UsersRequestBuilder
from pydantic.v1 import BaseModel, validator
@@ -18,6 +17,16 @@ from prowler.lib.logger import logger
from prowler.providers.m365.lib.service.service import M365Service
from prowler.providers.m365.m365_provider import M365Provider
+run_hunting_query_body = importlib.import_module(
+ "msgraph.generated.security.microsoft_graph_security_run_hunting_query."
+ "run_hunting_query_post_request_body"
+)
+# Sentinel identifiers used in Conditional Access ``conditions.users``
+# collections that do not correspond to real directory objects and must not be
+# resolved against Graph. Shared by the resolver below and the check that reads
+# its result.
+CONDITIONAL_ACCESS_SENTINEL_IDS = {"All", "None", "GuestsOrExternalUsers"}
+
class Entra(M365Service):
"""
@@ -77,6 +86,7 @@ class Entra(M365Service):
self.tenant_domain = provider.identity.tenant_domain
self.tenant_id = getattr(provider.identity, "tenant_id", None)
self.user_registration_details_error: Optional[str] = None
+ self.exchange_mailbox_permission_service_principals_error: Optional[str] = None
attributes = loop.run_until_complete(
gather(
self._get_authorization_policy(),
@@ -91,6 +101,7 @@ class Entra(M365Service):
self._get_authentication_method_configurations(),
self._get_service_principals(),
self._get_app_registrations(),
+ self._get_exchange_mailbox_permission_service_principals(),
)
)
@@ -108,8 +119,28 @@ class Entra(M365Service):
] = attributes[9]
self.service_principals: Dict[str, "ServicePrincipal"] = attributes[10]
self.app_registrations: Dict[str, "AppRegistration"] = attributes[11]
+ self.exchange_mailbox_permission_service_principals: Dict[
+ str, "ServicePrincipal"
+ ] = attributes[12]
self.user_accounts_status = {}
+ # Resolve directory-object identifiers referenced by Conditional Access
+ # policies. This runs as a separate phase because it depends on the
+ # main gather having populated ``conditional_access_policies`` first.
+ # The result is cached on the instance so sync checks can read it
+ # without issuing Graph calls of their own. ``unresolved`` holds ids
+ # confirmed deleted (HTTP 404); ``errored`` holds ids whose lookup
+ # failed for any other reason (5xx, throttling, permission) and could
+ # therefore be neither confirmed present nor confirmed deleted.
+ self.unresolved_directory_object_references: Set[Tuple[str, str]]
+ self.errored_directory_object_references: Set[Tuple[str, str]]
+ (
+ self.unresolved_directory_object_references,
+ self.errored_directory_object_references,
+ ) = loop.run_until_complete(
+ self._resolve_directory_object_references(self.conditional_access_policies)
+ )
+
if created_loop:
asyncio.set_event_loop(None)
loop.close()
@@ -720,16 +751,48 @@ class Entra(M365Service):
logger.info("Entra - Getting groups...")
groups = []
try:
- groups_data = await self.client.groups.get()
- for group in groups_data.value:
- groups.append(
- Group(
- id=group.id,
- name=group.display_name,
- groupTypes=group.group_types,
- membershipRule=group.membership_rule,
- )
+ query_parameters = (
+ GroupsRequestBuilder.GroupsRequestBuilderGetQueryParameters(
+ select=[
+ "id",
+ "displayName",
+ "groupTypes",
+ "membershipRule",
+ "isAssignableToRole",
+ "isManagementRestricted",
+ ],
)
+ )
+ request_configuration = RequestConfiguration(
+ query_parameters=query_parameters,
+ )
+ groups_data = await self.client.groups.get(
+ request_configuration=request_configuration,
+ )
+
+ while groups_data:
+ for group in groups_data.value:
+ groups.append(
+ Group(
+ id=group.id,
+ name=group.display_name,
+ groupTypes=group.group_types or [],
+ membershipRule=group.membership_rule,
+ is_assignable_to_role=getattr(
+ group, "is_assignable_to_role", False
+ )
+ or False,
+ is_management_restricted=getattr(
+ group, "is_management_restricted", False
+ )
+ or False,
+ )
+ )
+
+ next_link = getattr(groups_data, "odata_next_link", None)
+ if not next_link:
+ break
+ groups_data = await self.client.groups.with_url(next_link).get()
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
@@ -791,6 +854,16 @@ class Entra(M365Service):
features, "seamless_sso_enabled", False
)
or False,
+ block_soft_match_enabled=getattr(
+ features, "block_soft_match_enabled", False
+ )
+ or False,
+ block_cloud_object_takeover_through_hard_match_enabled=getattr(
+ features,
+ "block_cloud_object_takeover_through_hard_match_enabled",
+ False,
+ )
+ or False,
)
)
except ODataError as error:
@@ -830,6 +903,7 @@ class Entra(M365Service):
"userType",
"accountEnabled",
"onPremisesSyncEnabled",
+ "employeeHireDate",
],
)
)
@@ -890,6 +964,7 @@ class Entra(M365Service):
"authentication_methods", []
),
user_type=getattr(user, "user_type", None),
+ employee_hire_date=getattr(user, "employee_hire_date", None),
)
next_link = getattr(users_response, "odata_next_link", None)
@@ -986,7 +1061,9 @@ OAuthAppInfo
| project OAuthAppId, AppName, AppStatus, PrivilegeLevel, Permissions,
ServicePrincipalId, IsAdminConsented, LastUsedTime, AppOrigin
"""
- request_body = RunHuntingQueryPostRequestBody(query=query)
+ request_body = run_hunting_query_body.RunHuntingQueryPostRequestBody(
+ query=query
+ )
result = await self.client.security.microsoft_graph_security_run_hunting_query.post(
request_body
@@ -1197,6 +1274,10 @@ OAuthAppInfo
service_principals_by_app_id = {
sp.app_id: sp for sp in service_principals.values() if sp.app_id
}
+ # Remember each SP's parent application object ID so the owner
+ # lookup below can address it directly without re-walking
+ # /applications.
+ application_object_id_by_sp_id: Dict[str, str] = {}
app_response = await self.client.applications.get()
while app_response:
for app in getattr(app_response, "value", []) or []:
@@ -1207,6 +1288,10 @@ OAuthAppInfo
if target_sp is None:
continue
+ app_object_id = getattr(app, "id", None)
+ if app_object_id:
+ application_object_id_by_sp_id[target_sp.id] = app_object_id
+
for cred in getattr(app, "password_credentials", []) or []:
target_sp.password_credentials.append(
PasswordCredential(
@@ -1257,12 +1342,161 @@ OAuthAppInfo
next_link
).get()
+ # Resolve owners only for service principals that hold a permanent
+ # Tier 0 directory role. Owner ownership of the SP object or its
+ # parent app registration is a credential-rotation escalation path
+ # outside PIM and Conditional Access; fetching owners for every
+ # consented SP would multiply Graph traffic for no benefit.
+ for sp in service_principals.values():
+ if not sp.directory_role_template_ids:
+ continue
+ try:
+ sp_owners_response = (
+ await self.client.service_principals.by_service_principal_id(
+ sp.id
+ ).owners.get()
+ )
+ sp.sp_owner_ids = [
+ getattr(owner, "id", None)
+ for owner in (getattr(sp_owners_response, "value", []) or [])
+ if getattr(owner, "id", None)
+ ]
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ app_object_id = application_object_id_by_sp_id.get(sp.id)
+ if not app_object_id:
+ continue
+ try:
+ app_owners_response = (
+ await self.client.applications.by_application_id(
+ app_object_id
+ ).owners.get()
+ )
+ sp.app_owner_ids = [
+ getattr(owner, "id", None)
+ for owner in (getattr(app_owners_response, "value", []) or [])
+ if getattr(owner, "id", None)
+ ]
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
except Exception as error:
logger.error(
f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
)
return service_principals
+ async def _get_exchange_mailbox_permission_service_principals(self):
+ """Retrieve service principals with Exchange mailbox Graph app roles."""
+ logger.info(
+ "Entra - Getting service principals with Exchange mailbox permissions..."
+ )
+ self.exchange_mailbox_permission_service_principals_error = None
+ service_principals = {}
+ graph_service_principal = None
+ candidate_service_principals = []
+
+ try:
+ sp_response = await self.client.service_principals.get()
+ while sp_response:
+ for sp in getattr(sp_response, "value", []) or []:
+ app_id = getattr(sp, "app_id", None)
+ if app_id == MICROSOFT_GRAPH_APP_ID:
+ graph_service_principal = sp
+ continue
+
+ if not getattr(sp, "account_enabled", True):
+ continue
+
+ raw_owner = getattr(sp, "app_owner_organization_id", None)
+ app_owner_org_id = str(raw_owner).lower() if raw_owner else None
+ if app_owner_org_id in MICROSOFT_FIRST_PARTY_TENANT_IDS:
+ continue
+
+ candidate_service_principals.append(sp)
+
+ next_link = getattr(sp_response, "odata_next_link", None)
+ if not next_link:
+ break
+ sp_response = await self.client.service_principals.with_url(
+ next_link
+ ).get()
+
+ if graph_service_principal is None:
+ return service_principals
+
+ graph_service_principal_id = getattr(graph_service_principal, "id", None)
+ exchange_app_roles = {}
+ for role in getattr(graph_service_principal, "app_roles", []) or []:
+ role_value = getattr(role, "value", "") or ""
+ allowed_member_types = getattr(role, "allowed_member_types", []) or []
+ if (
+ role_value in EXCHANGE_MAILBOX_GRAPH_PERMISSIONS
+ and "Application" in allowed_member_types
+ ):
+ exchange_app_roles[str(getattr(role, "id", ""))] = role_value
+
+ if not graph_service_principal_id or not exchange_app_roles:
+ return service_principals
+
+ for sp in candidate_service_principals:
+ assignments_response = (
+ await self.client.service_principals.by_service_principal_id(
+ sp.id
+ ).app_role_assignments.get()
+ )
+ exchange_permissions = set()
+
+ while assignments_response:
+ for assignment in getattr(assignments_response, "value", []) or []:
+ resource_id = str(getattr(assignment, "resource_id", ""))
+ app_role_id = str(getattr(assignment, "app_role_id", ""))
+ if resource_id == graph_service_principal_id:
+ permission = exchange_app_roles.get(app_role_id)
+ if permission:
+ exchange_permissions.add(permission)
+
+ next_link = getattr(assignments_response, "odata_next_link", None)
+ if not next_link:
+ break
+ assignments_response = (
+ await self.client.service_principals.by_service_principal_id(
+ sp.id
+ )
+ .app_role_assignments.with_url(next_link)
+ .get()
+ )
+
+ if exchange_permissions:
+ raw_owner = getattr(sp, "app_owner_organization_id", None)
+ service_principals[sp.id] = ServicePrincipal(
+ id=sp.id,
+ name=getattr(sp, "display_name", "") or "",
+ app_id=getattr(sp, "app_id", "") or "",
+ app_owner_organization_id=(
+ str(raw_owner).lower() if raw_owner else None
+ ),
+ account_enabled=getattr(sp, "account_enabled", True),
+ service_principal_type=getattr(
+ sp, "service_principal_type", "Application"
+ ),
+ exchange_mailbox_permissions=sorted(exchange_permissions),
+ )
+ except Exception as error:
+ self.exchange_mailbox_permission_service_principals_error = (
+ f"{error.__class__.__name__}: {error}"
+ )
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+
+ return service_principals
+
async def _get_app_registrations(self) -> Dict[str, "AppRegistration"]:
"""Retrieve application registrations from Microsoft Entra.
@@ -1316,6 +1550,130 @@ OAuthAppInfo
)
return app_registrations
+ async def _resolve_directory_object_references(
+ self,
+ policies: Dict[str, "ConditionalAccessPolicy"],
+ ) -> Tuple[Set[Tuple[str, str]], Set[Tuple[str, str]]]:
+ """Resolve every user/group/role identifier referenced by CA policies.
+
+ Walks the inclusion/exclusion collections of every loaded Conditional
+ Access policy, deduplicates the resulting identifiers per type, and
+ queries Microsoft Graph for each one. Identifiers that return HTTP 404
+ are reported as deleted. Non-404 errors (5xx, throttling, permission,
+ transient network failures) are reported as unresolvable: they must not
+ be flagged as deletions, but they must also not be silently treated as
+ clean resolutions, so the downstream check surfaces them as MANUAL.
+
+ The sentinel values ``All``, ``None``, and ``GuestsOrExternalUsers``
+ are not directory identifiers and are excluded before any Graph call.
+
+ Args:
+ policies: Conditional Access policies keyed by policy ID.
+
+ Returns:
+ Tuple[Set[Tuple[str, str]], Set[Tuple[str, str]]]: A pair of
+ ``(type, identifier)`` sets. The first holds identifiers that
+ failed to resolve via Graph with HTTP 404 (deleted); the second
+ holds identifiers whose lookup failed for any other reason and
+ could be neither confirmed present nor confirmed deleted.
+ """
+ logger.info(
+ "Entra - Resolving directory-object references in Conditional "
+ "Access policies..."
+ )
+
+ ids_by_type: Dict[str, Set[str]] = {
+ "user": set(),
+ "group": set(),
+ "role": set(),
+ }
+
+ for policy in policies.values():
+ if not getattr(policy, "conditions", None):
+ continue
+ user_conditions = getattr(policy.conditions, "user_conditions", None)
+ if user_conditions is None:
+ continue
+ for ident in (user_conditions.included_users or []) + (
+ user_conditions.excluded_users or []
+ ):
+ if ident and ident not in CONDITIONAL_ACCESS_SENTINEL_IDS:
+ ids_by_type["user"].add(ident)
+ for ident in (user_conditions.included_groups or []) + (
+ user_conditions.excluded_groups or []
+ ):
+ if ident and ident not in CONDITIONAL_ACCESS_SENTINEL_IDS:
+ ids_by_type["group"].add(ident)
+ for ident in (user_conditions.included_roles or []) + (
+ user_conditions.excluded_roles or []
+ ):
+ if ident and ident not in CONDITIONAL_ACCESS_SENTINEL_IDS:
+ ids_by_type["role"].add(ident)
+
+ unresolved: Set[Tuple[str, str]] = set()
+ errored: Set[Tuple[str, str]] = set()
+
+ # Resolve types in parallel; within a type, walk identifiers serially
+ # to keep concurrent Graph calls bounded and avoid throttling.
+ await gather(
+ self._resolve_identifiers_for_type(
+ "user", ids_by_type["user"], unresolved, errored
+ ),
+ self._resolve_identifiers_for_type(
+ "group", ids_by_type["group"], unresolved, errored
+ ),
+ self._resolve_identifiers_for_type(
+ "role", ids_by_type["role"], unresolved, errored
+ ),
+ )
+ return unresolved, errored
+
+ async def _resolve_identifiers_for_type(
+ self,
+ type_: str,
+ identifiers: Set[str],
+ unresolved: Set[Tuple[str, str]],
+ errored: Set[Tuple[str, str]],
+ ) -> None:
+ """Resolve a set of identifiers of a given type, mutating the result sets.
+
+ Only HTTP 404 (or ``Request_ResourceNotFound``) responses add to
+ ``unresolved``. Every other error (5xx, throttling, permission, or an
+ unexpected exception) is logged and added to ``errored`` so the check
+ can report it as unverified instead of silently treating it as clean.
+ """
+ for identifier in identifiers:
+ try:
+ if type_ == "user":
+ await self.client.users.by_user_id(identifier).get()
+ elif type_ == "group":
+ await self.client.groups.by_group_id(identifier).get()
+ elif type_ == "role":
+ await self.client.role_management.directory.role_definitions.by_unified_role_definition_id(
+ identifier
+ ).get()
+ else:
+ continue
+ except ODataError as error:
+ status_code = getattr(error, "response_status_code", None)
+ error_code = getattr(error.error, "code", None) if error.error else None
+ if status_code == 404 or error_code == "Request_ResourceNotFound":
+ unresolved.add((type_, identifier))
+ else:
+ errored.add((type_, identifier))
+ logger.warning(
+ f"Entra - Could not resolve {type_} '{identifier}' for "
+ f"Conditional Access reference check: "
+ f"{error.__class__.__name__}: {error}"
+ )
+ except Exception as error:
+ errored.add((type_, identifier))
+ logger.warning(
+ f"Entra - Unexpected error resolving {type_} '{identifier}' "
+ f"for Conditional Access reference check: "
+ f"{error.__class__.__name__}: {error}"
+ )
+
class ConditionalAccessPolicyState(Enum):
ENABLED = "enabled"
@@ -1436,7 +1794,7 @@ class PlatformConditions(BaseModel):
@validator("include_platforms", "exclude_platforms", pre=True)
@classmethod
- def normalize_platforms(cls, values):
+ def normalize_platforms(cls, values): # noqa: vulture
if not values:
return []
@@ -1584,6 +1942,8 @@ class DirectorySyncSettings(BaseModel):
id: str
password_sync_enabled: bool = False
seamless_sso_enabled: bool = False
+ block_soft_match_enabled: bool = False
+ block_cloud_object_takeover_through_hard_match_enabled: bool = False
class AuthenticationMethodConfiguration(BaseModel):
@@ -1606,6 +1966,8 @@ class Group(BaseModel):
name: str
groupTypes: List[str]
membershipRule: Optional[str]
+ is_assignable_to_role: bool = False
+ is_management_restricted: bool = False
class AdminConsentPolicy(BaseModel):
@@ -1674,6 +2036,7 @@ class User(BaseModel):
user_type: The user account type as reported by Microsoft Graph
(typically 'Member' or 'Guest'). ``None`` when Microsoft Graph does not
return the property; checks must not assume a default in that case.
+ employee_hire_date: The user's hire date as reported by Microsoft Graph.
"""
id: str
@@ -1684,6 +2047,7 @@ class User(BaseModel):
account_enabled: bool = True
authentication_methods: List[str] = []
user_type: Optional[str] = None
+ employee_hire_date: Optional[datetime] = None
class InvitationsFrom(Enum):
@@ -1815,6 +2179,27 @@ TIER_0_ROLE_TEMPLATE_IDS = {
"e00e864a-17c5-4a4b-9c06-f5b95a8d5bd8", # Partner Tier2 Support
}
+MICROSOFT_GRAPH_APP_ID = "00000003-0000-0000-c000-000000000000"
+
+MICROSOFT_FIRST_PARTY_TENANT_IDS = {
+ "72f988bf-86f1-41af-91ab-2d7cd011db47",
+ "f8cdef31-a31e-4b4a-93e4-5f571e91255a",
+}
+
+EXCHANGE_MAILBOX_GRAPH_PERMISSIONS = {
+ "Calendars.Read",
+ "Calendars.ReadWrite",
+ "Contacts.Read",
+ "Contacts.ReadWrite",
+ "Mail.Read",
+ "Mail.ReadBasic",
+ "Mail.ReadBasic.All",
+ "Mail.ReadWrite",
+ "Mail.Send",
+ "MailboxSettings.Read",
+ "MailboxSettings.ReadWrite",
+}
+
class ServicePrincipal(BaseModel):
"""Model representing a Microsoft Entra ID service principal.
@@ -1832,6 +2217,12 @@ class ServicePrincipal(BaseModel):
key_credentials: List of key credentials (certificates).
directory_role_template_ids: List of directory role template IDs permanently
assigned to this service principal.
+ sp_owner_ids: Principal IDs that own the service principal object.
+ Populated only for service principals that hold a permanent Tier 0
+ directory role assignment, to keep Graph traffic bounded.
+ app_owner_ids: Principal IDs that own the parent app registration.
+ Populated only for service principals that hold a permanent Tier 0
+ directory role assignment.
"""
id: str
@@ -1841,6 +2232,11 @@ class ServicePrincipal(BaseModel):
password_credentials: List[PasswordCredential] = []
key_credentials: List[KeyCredential] = []
directory_role_template_ids: List[str] = []
+ account_enabled: bool = True
+ service_principal_type: str = "Application"
+ exchange_mailbox_permissions: List[str] = []
+ sp_owner_ids: List[str] = []
+ app_owner_ids: List[str] = []
class AppRegistration(BaseModel):
diff --git a/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/__init__.py b/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.metadata.json b/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.metadata.json
new file mode 100644
index 0000000000..4822d8956d
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.metadata.json
@@ -0,0 +1,40 @@
+{
+ "Provider": "m365",
+ "CheckID": "entra_service_principal_privileged_role_no_owners",
+ "CheckTitle": "Service principals with privileged Entra directory roles must have no owners",
+ "CheckType": [],
+ "ServiceName": "entra",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "critical",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Microsoft Entra **service principals** holding permanent **Control Plane (Tier 0)** directory roles (such as **Global Administrator** or **Privileged Role Administrator**) are evaluated for the presence of **owners** on either the service principal itself or its parent **app registration**.",
+ "Risk": "An **owner** of a service principal or its parent app registration can **rotate credentials** and sign in as the service principal, inheriting its **Tier 0** role outside **PIM** and **Conditional Access** controls. This is a documented privilege escalation path impacting **confidentiality**, **integrity**, and **availability** of the tenant's control plane.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/api/serviceprincipal-list-owners?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/application-list-owners?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/rbacapplication-list-roleassignments?view=graph-rest-1.0"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the Microsoft Entra admin center (https://entra.microsoft.com)\n2. Go to Identity > Applications > Enterprise applications > select the service principal\n3. Under Owners, remove all owners\n4. Repeat for the parent App Registration under Identity > Applications > App registrations\n5. Use PIM eligible assignments instead of permanent role assignments where possible",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Remove all owners from service principals that hold privileged Entra directory roles. Manage privileged service principals exclusively via PIM-eligible role assignments and break-glass controls. Ensure no human account can silently inherit control-plane privileges through ownership.",
+ "Url": "https://hub.prowler.com/check/entra_service_principal_privileged_role_no_owners"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "entra_service_principal_no_secrets_for_permanent_tier0_roles"
+ ],
+ "Notes": "Only service principals with permanent Tier 0 directory role assignments are evaluated. Microsoft first-party service principals and multi-tenant ISV apps consented from other publishers are excluded by the service layer."
+}
diff --git a/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.py b/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.py
new file mode 100644
index 0000000000..f3af26e23f
--- /dev/null
+++ b/prowler/providers/m365/services/entra/entra_service_principal_privileged_role_no_owners/entra_service_principal_privileged_role_no_owners.py
@@ -0,0 +1,71 @@
+"""Check for service principals with privileged roles that have owners."""
+
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+
+
+class entra_service_principal_privileged_role_no_owners(Check):
+ """Service principal with a permanent Tier 0 directory role has no owners.
+
+ Owners of a service principal or its parent app registration can rotate
+ credentials and sign in as the service principal, inheriting its privileged
+ directory role outside PIM approval flows and Conditional Access policies
+ targeting user accounts.
+
+ - PASS: The service principal does not hold a permanent Tier 0 directory
+ role, or it does but has zero owners on both the service principal and
+ its parent app registration.
+ - FAIL: The service principal holds a permanent Tier 0 directory role and
+ has at least one owner on either the service principal or its parent
+ app registration.
+ """
+
+ def execute(self) -> List[CheckReportM365]:
+ """Execute the privileged service principal owner check.
+
+ Returns:
+ A list of reports, one per service principal owned by the audited
+ tenant.
+ """
+ findings = []
+ for sp in entra_client.service_principals.values():
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=sp,
+ resource_name=sp.name,
+ resource_id=sp.id,
+ )
+
+ if not sp.directory_role_template_ids:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Service principal '{sp.name}' has no permanent Tier 0 "
+ f"directory role assignments."
+ )
+ findings.append(report)
+ continue
+
+ unique_owners = set(sp.sp_owner_ids) | set(sp.app_owner_ids)
+ tier0_role_count = len(sp.directory_role_template_ids)
+
+ if unique_owners:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Service principal '{sp.name}' holds {tier0_role_count} "
+ f"permanent Tier 0 directory role(s) and has "
+ f"{len(unique_owners)} owner(s) "
+ f"({len(sp.sp_owner_ids)} on the service principal, "
+ f"{len(sp.app_owner_ids)} on the parent app registration)."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Service principal '{sp.name}' holds {tier0_role_count} "
+ f"permanent Tier 0 directory role(s) and has no owners on "
+ f"either the service principal or its parent app registration."
+ )
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/m365/services/entra/entra_users_mfa_capable/entra_users_mfa_capable.py b/prowler/providers/m365/services/entra/entra_users_mfa_capable/entra_users_mfa_capable.py
index 9485676d30..d3e75cef7f 100644
--- a/prowler/providers/m365/services/entra/entra_users_mfa_capable/entra_users_mfa_capable.py
+++ b/prowler/providers/m365/services/entra/entra_users_mfa_capable/entra_users_mfa_capable.py
@@ -1,3 +1,4 @@
+from datetime import datetime, timezone
from typing import List
from prowler.lib.check.models import Check, CheckReportM365
@@ -12,7 +13,8 @@ class entra_users_mfa_capable(Check):
Microsoft 365 Foundations Benchmark recommendation 5.2.3.4
("Ensure all member users are 'MFA capable'").
- Guest users and disabled accounts are excluded from the evaluation.
+ Guest users, disabled accounts, and future hires are excluded from the
+ evaluation.
- PASS: The member user is MFA capable.
- FAIL: The member user is not MFA capable, or MFA capability cannot be
@@ -38,6 +40,15 @@ class entra_users_mfa_capable(Check):
for user in entra_client.users.values():
if user.user_type == "Guest" or not user.account_enabled:
continue
+ if user.employee_hire_date:
+ employee_hire_date = user.employee_hire_date
+ if (
+ employee_hire_date.tzinfo is None
+ or employee_hire_date.utcoffset() is None
+ ):
+ employee_hire_date = employee_hire_date.replace(tzinfo=timezone.utc)
+ if employee_hire_date > datetime.now(timezone.utc):
+ continue
report = CheckReportM365(
metadata=self.metadata(),
diff --git a/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/__init__.py b/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.metadata.json b/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.metadata.json
new file mode 100644
index 0000000000..0e4da9420d
--- /dev/null
+++ b/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.metadata.json
@@ -0,0 +1,41 @@
+{
+ "Provider": "m365",
+ "CheckID": "exchange_application_access_policy_restricts_mailbox_apps",
+ "CheckTitle": "Apps with Exchange mailbox permissions must be scoped via Application Access Policy",
+ "CheckType": [],
+ "ServiceName": "exchange",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "**Microsoft 365 Exchange Online** applications with mailbox access permissions should be restricted using **Application Access Policies**.\n\nThis check evaluates whether applications granted Exchange-related Microsoft Graph application permissions are scoped using Exchange Online `ApplicationAccessPolicy` objects.",
+ "Risk": "Applications with unrestricted Exchange mailbox permissions may gain tenant-wide mailbox access. Without **Application Access Policies**, compromised or over-privileged applications can read or manipulate mail across all mailboxes, leading to unauthorized access, data exfiltration, phishing, and loss of confidentiality and integrity.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/graph/auth-limit-mailbox-access",
+ "https://learn.microsoft.com/en-us/powershell/module/exchange/new-applicationaccesspolicy",
+ "https://learn.microsoft.com/en-us/powershell/module/exchange/get-applicationaccesspolicy",
+ "https://learn.microsoft.com/en-us/graph/api/resources/serviceprincipal?view=graph-rest-1.0",
+ "https://learn.microsoft.com/en-us/graph/api/serviceprincipal-list-approleassignments?view=graph-rest-1.0"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "New-ApplicationAccessPolicy -AppId <AppId> -PolicyScopeGroupId <Group> -AccessRight RestrictAccess -Description \"Restrict mailbox access\"",
+ "NativeIaC": "",
+ "Other": "1. Connect to Exchange Online PowerShell\n2. Run Get-ApplicationAccessPolicy to review existing policies\n3. Identify applications with Exchange-related Graph application permissions\n4. Create an Application Access Policy for each required application\n5. Scope mailbox access using a dedicated mail-enabled security group",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Restrict applications with Exchange mailbox permissions using **Application Access Policies**. Apply least privilege by limiting mailbox scope to only required users or groups. Regularly review app permissions and remove unused or excessive mailbox access.",
+ "Url": "https://hub.prowler.com/check/exchange_application_access_policy_restricts_mailbox_apps"
+ }
+ },
+ "Categories": [
+ "identity-access",
+ "email-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.py b/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.py
new file mode 100644
index 0000000000..d4c786b338
--- /dev/null
+++ b/prowler/providers/m365/services/exchange/exchange_application_access_policy_restricts_mailbox_apps/exchange_application_access_policy_restricts_mailbox_apps.py
@@ -0,0 +1,99 @@
+import importlib
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.entra.entra_client import entra_client
+
+exchange_client = importlib.import_module(
+ "prowler.providers.m365.services.exchange.exchange_client"
+).exchange_client
+
+
+class exchange_application_access_policy_restricts_mailbox_apps(Check):
+ """
+ Check if applications with Exchange mailbox permissions
+ are restricted using Exchange Application Access Policies.
+ """
+
+ def execute(self) -> List[CheckReportM365]:
+ findings = []
+
+ application_access_policies = exchange_client.application_access_policies
+ if application_access_policies is None:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=exchange_client.organization_config,
+ resource_name="Exchange Online",
+ resource_id="ExchangeOnlineTenant",
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Exchange Online PowerShell is unavailable. "
+ "Enable Exchange Online PowerShell credentials to evaluate "
+ "Application Access Policies."
+ )
+ findings.append(report)
+ return findings
+
+ mailbox_permission_collection_error = getattr(
+ entra_client,
+ "exchange_mailbox_permission_service_principals_error",
+ None,
+ )
+ if isinstance(mailbox_permission_collection_error, str):
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=exchange_client.organization_config,
+ resource_name="Exchange Online",
+ resource_id="ExchangeOnlineTenant",
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Microsoft Graph mailbox permission collection failed. "
+ "Manually verify whether applications with Exchange mailbox "
+ "permissions are restricted using Application Access Policies."
+ )
+ findings.append(report)
+ return findings
+
+ policy_app_ids = {
+ policy.app_id.lower()
+ for policy in application_access_policies
+ if getattr(policy, "app_id", None)
+ and getattr(policy, "access_right", None) == "RestrictAccess"
+ }
+
+ service_principals = (
+ entra_client.exchange_mailbox_permission_service_principals.values()
+ )
+ for service_principal in service_principals:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=service_principal,
+ resource_name=service_principal.name,
+ resource_id=service_principal.id,
+ )
+ permissions = ", ".join(service_principal.exchange_mailbox_permissions)
+
+ if service_principal.app_id.lower() in policy_app_ids:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Service principal '{service_principal.name}' "
+ f"({service_principal.app_id}) "
+ "has Exchange mailbox permissions "
+ f"({permissions}) and is restricted using an Application "
+ "Access Policy."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Service principal '{service_principal.name}' "
+ f"({service_principal.app_id}) "
+ "has Exchange mailbox permissions "
+ f"({permissions}) but is not restricted using an Application "
+ "Access Policy."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/__init__.py b/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.metadata.json b/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.metadata.json
new file mode 100644
index 0000000000..66ce055152
--- /dev/null
+++ b/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "m365",
+ "CheckID": "exchange_mailbox_primary_smtp_uses_custom_domain",
+ "CheckTitle": "Mailbox primary SMTP address must use a custom domain",
+ "CheckType": [],
+ "ServiceName": "exchange",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "collaboration",
+ "Description": "**Exchange Online mailboxes** should use a custom domain as their primary SMTP address, not the default **\\*.onmicrosoft.com** routing domain assigned by Microsoft on tenant creation. This check verifies that the **PrimarySmtpAddress** of every user-facing mailbox does not end with `.onmicrosoft.com`.",
+ "Risk": "Mailboxes still using **.onmicrosoft.com** as their primary SMTP address leak the internal **tenant identifier** in every From: header, helping attackers fingerprint the tenant for spear-phishing. They also bypass **DMARC/DKIM** hardening that organisations deploy on their custom domains and are frequently treated as low-trust by recipient anti-phishing engines.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://learn.microsoft.com/en-us/microsoft-365/admin/setup/add-domain",
+ "https://learn.microsoft.com/en-us/microsoft-365/admin/setup/domains-faq",
+ "https://learn.microsoft.com/en-us/powershell/module/exchange/get-mailbox",
+ "https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/manage-user-mailboxes"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "Get-Mailbox -ResultSize Unlimited | Where-Object { $_.PrimarySmtpAddress -like '*.onmicrosoft.com' } | ForEach-Object { Set-Mailbox -Identity $_.Identity -PrimarySmtpAddress '<user>@<customdomain.com>' }",
+ "NativeIaC": "",
+ "Other": "1. Navigate to the Microsoft 365 admin center (https://admin.microsoft.com/)\n2. Go to Users > Active users and select the affected user\n3. Under the Aliases section, add the custom domain email address\n4. Set the custom domain address as the primary SMTP address\n5. Save changes and repeat for all affected mailboxes",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Update the primary SMTP address of all affected mailboxes to use a custom domain. Ensure your custom domain is verified in the Microsoft 365 admin center before making this change.",
+ "Url": "https://hub.prowler.com/check/exchange_mailbox_primary_smtp_uses_custom_domain"
+ }
+ },
+ "Categories": [
+ "email-security"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.py b/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.py
new file mode 100644
index 0000000000..d34d091145
--- /dev/null
+++ b/prowler/providers/m365/services/exchange/exchange_mailbox_primary_smtp_uses_custom_domain/exchange_mailbox_primary_smtp_uses_custom_domain.py
@@ -0,0 +1,79 @@
+from typing import List
+
+from prowler.lib.check.models import Check, CheckReportM365
+from prowler.providers.m365.services.exchange.exchange_client import exchange_client
+
+
+class exchange_mailbox_primary_smtp_uses_custom_domain(Check):
+ """
+ Verify that every Exchange Online mailbox uses a custom domain as its
+ primary SMTP address, not the default .onmicrosoft.com routing domain.
+
+ The .onmicrosoft.com domain is assigned by Microsoft on tenant creation
+ and is not intended for ongoing mail. Mailboxes still using it leak the
+ internal tenant identifier in every From: header (aiding spear-phishing),
+ bypass DMARC/DKIM hardening on custom domains and are often treated as
+ low-trust by recipient anti-phishing engines.
+
+ - PASS: Primary SMTP address does not use the .onmicrosoft.com domain.
+ - FAIL: Primary SMTP address uses the .onmicrosoft.com domain.
+ - MANUAL: Exchange Online PowerShell unavailable; check cannot run.
+ """
+
+ def execute(self) -> List[CheckReportM365]:
+ """
+ Execute the check against all recipient-facing Exchange Online mailboxes.
+
+ Returns:
+ List[CheckReportM365]: A report for each mailbox with its SMTP
+ domain status, or a single MANUAL report if PowerShell was
+ unavailable.
+ """
+ findings = []
+
+ # mailboxes is None when Exchange Online PowerShell could not be
+ # reached or the cmdlet raised. An empty list means PowerShell ran
+ # but the tenant has no recipient-facing mailboxes (no findings).
+ if exchange_client.mailboxes is None:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource={},
+ resource_name="Exchange Online Mailboxes",
+ resource_id="exchange_mailboxes",
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Exchange Online PowerShell is unavailable. "
+ "Enable EXO PowerShell access to run this check."
+ )
+ findings.append(report)
+ return findings
+
+ for mailbox in exchange_client.mailboxes:
+ report = CheckReportM365(
+ metadata=self.metadata(),
+ resource=mailbox,
+ resource_name=mailbox.name or mailbox.identity,
+ resource_id=mailbox.identity,
+ )
+
+ if mailbox.primary_smtp_address.endswith(".onmicrosoft.com"):
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Mailbox {mailbox.identity} "
+ f"({mailbox.recipient_type_details}) has primary SMTP "
+ f"address {mailbox.primary_smtp_address} using the "
+ f".onmicrosoft.com domain instead of a custom domain."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Mailbox {mailbox.identity} "
+ f"({mailbox.recipient_type_details}) has primary SMTP "
+ f"address {mailbox.primary_smtp_address} using a "
+ f"custom domain."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/m365/services/exchange/exchange_service.py b/prowler/providers/m365/services/exchange/exchange_service.py
index 9b3ee47da9..c4e4b309a4 100644
--- a/prowler/providers/m365/services/exchange/exchange_service.py
+++ b/prowler/providers/m365/services/exchange/exchange_service.py
@@ -8,6 +8,15 @@ from prowler.lib.logger import logger
from prowler.providers.m365.lib.service.service import M365Service
from prowler.providers.m365.m365_provider import M365Provider
+SYSTEM_MAILBOX_TYPES = {
+ "DiscoveryMailbox",
+ "ArbitrationMailbox",
+ "AuditLogMailbox",
+ "MonitoringMailbox",
+ "AuxAuditLogMailbox",
+ "SystemMailbox",
+}
+
class Exchange(M365Service):
"""
@@ -34,6 +43,8 @@ class Exchange(M365Service):
self.role_assignment_policies = []
self.mailbox_audit_properties = []
self.shared_mailboxes = []
+ self.application_access_policies = None
+ self.mailboxes = None
if self.powershell:
if self.powershell.connect_exchange_online():
@@ -46,6 +57,10 @@ class Exchange(M365Service):
self.role_assignment_policies = self._get_role_assignment_policies()
self.mailbox_audit_properties = self._get_mailbox_audit_properties()
self.shared_mailboxes = self._get_shared_mailboxes()
+ self.application_access_policies = (
+ self._get_application_access_policies()
+ )
+ self.mailboxes = self._get_mailboxes()
self.powershell.close()
# Fetch license count via Graph API
@@ -355,6 +370,97 @@ class Exchange(M365Service):
)
return shared_mailboxes
+ def _get_application_access_policies(self):
+ """
+ Get Exchange Online Application Access Policies.
+
+ Returns:
+ Optional[list[ApplicationAccessPolicy]]: List of application access
+ policies, or None if the PowerShell command failed.
+ """
+ logger.info("Microsoft365 - Getting application access policies...")
+
+ application_access_policies = []
+
+ try:
+ policies_data = self.powershell.get_application_access_policies()
+
+ if not policies_data:
+ return application_access_policies
+
+ if isinstance(policies_data, dict):
+ policies_data = [policies_data]
+
+ for policy in policies_data:
+ if policy:
+ application_access_policies.append(
+ ApplicationAccessPolicy(
+ identity=policy.get("Identity", ""),
+ app_id=policy.get("AppId", ""),
+ access_right=policy.get(
+ "AccessRight",
+ "",
+ ),
+ description=policy.get(
+ "Description",
+ "",
+ ),
+ )
+ )
+
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}"
+ f"[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return None
+
+ return application_access_policies
+
+ def _get_mailboxes(self) -> Optional[list["Mailbox"]]:
+ """
+ Get all recipient-facing mailboxes from Exchange Online.
+
+ Retrieves mailboxes of types UserMailbox, SharedMailbox, RoomMailbox
+ and EquipmentMailbox. System-managed mailbox types are excluded as
+ they are controlled by Microsoft and are not subject to domain policy.
+
+ Returns:
+ list[Mailbox]: List of mailboxes with their primary SMTP address
+ and recipient type details. Returns ``None`` when the
+ underlying PowerShell cmdlet raises, so callers can
+ distinguish "PowerShell unavailable" from "empty tenant".
+ """
+ logger.info("Microsoft365 - Getting mailboxes...")
+ mailboxes = []
+ try:
+ mailboxes_data = self.powershell.get_mailboxes()
+ if not mailboxes_data:
+ return mailboxes
+ # PowerShell can return a single dict instead of a list when only
+ # one result is returned; normalize to a list for uniform handling.
+ if isinstance(mailboxes_data, dict):
+ mailboxes_data = [mailboxes_data]
+ for mailbox in mailboxes_data:
+ if mailbox:
+ recipient_type = mailbox.get("RecipientTypeDetails", "")
+ if recipient_type in SYSTEM_MAILBOX_TYPES:
+ continue
+ mailboxes.append(
+ Mailbox(
+ identity=mailbox.get("Identity", ""),
+ name=mailbox.get("DisplayName", ""),
+ primary_smtp_address=mailbox.get("PrimarySmtpAddress", ""),
+ recipient_type_details=recipient_type,
+ )
+ )
+ return mailboxes
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return None
+
class Organization(BaseModel):
"""
@@ -497,3 +603,33 @@ class SharedMailbox(BaseModel):
user_principal_name: str
external_directory_object_id: str
identity: str
+
+
+class ApplicationAccessPolicy(BaseModel):
+ """
+ Model for Exchange Online Application Access Policy.
+ """
+
+ identity: str
+ app_id: str
+ access_right: str
+ description: str
+
+
+class Mailbox(BaseModel):
+ """
+ Model for an Exchange Online recipient-facing mailbox.
+
+ Attributes:
+ identity: The unique identity of the mailbox in Exchange.
+ name: Display name of the mailbox.
+ primary_smtp_address: The primary SMTP address used for outbound mail
+ and the From: header. This is the address the check evaluates.
+ recipient_type_details: The mailbox type (e.g., UserMailbox,
+ SharedMailbox, RoomMailbox, EquipmentMailbox).
+ """
+
+ identity: str
+ name: str
+ primary_smtp_address: str
+ recipient_type_details: str
diff --git a/prowler/providers/mongodbatlas/mongodbatlas_provider.py b/prowler/providers/mongodbatlas/mongodbatlas_provider.py
index c40f1ced6e..07ff6f86cc 100644
--- a/prowler/providers/mongodbatlas/mongodbatlas_provider.py
+++ b/prowler/providers/mongodbatlas/mongodbatlas_provider.py
@@ -36,6 +36,7 @@ class MongodbatlasProvider(Provider):
"""
_type: str = "mongodbatlas"
+ sdk_only: bool = False
_session: MongoDBAtlasSession
_identity: MongoDBAtlasIdentityInfo
_audit_config: dict
diff --git a/prowler/providers/okta/exceptions/exceptions.py b/prowler/providers/okta/exceptions/exceptions.py
index 20a20c1b93..04dd71bef0 100644
--- a/prowler/providers/okta/exceptions/exceptions.py
+++ b/prowler/providers/okta/exceptions/exceptions.py
@@ -34,6 +34,10 @@ class OktaBaseException(ProwlerException):
"message": "Okta service app is missing required scopes",
"remediation": "Have a Super Admin grant the required *.read scopes to the service app and assign the Read-Only Administrator role.",
},
+ (14007, "OktaInvalidProviderIdError"): {
+ "message": "The provided provider_id does not match the credentials org domain",
+ "remediation": "Check the provider_id (Okta org domain) and ensure it matches the org the service app credentials were issued for.",
+ },
}
def __init__(self, code, file=None, original_exception=None, message=None):
@@ -110,3 +114,10 @@ class OktaInsufficientPermissionsError(OktaCredentialsError):
super().__init__(
14006, file=file, original_exception=original_exception, message=message
)
+
+
+class OktaInvalidProviderIdError(OktaCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 14007, file=file, original_exception=original_exception, message=message
+ )
diff --git a/prowler/providers/okta/lib/arguments/arguments.py b/prowler/providers/okta/lib/arguments/arguments.py
index 3ad27de1c7..3865e30a4b 100644
--- a/prowler/providers/okta/lib/arguments/arguments.py
+++ b/prowler/providers/okta/lib/arguments/arguments.py
@@ -35,9 +35,32 @@ def init_parser(self):
nargs="+",
help=(
"OAuth scopes to request, space-separated "
- "(e.g. okta.policies.read okta.users.read). Defaults to the "
- "read scopes required by the bundled checks."
+ "(e.g. okta.policies.read okta.brands.read okta.apps.read "
+ "okta.logStreams.read okta.idps.read). "
+ "Defaults to the read scopes required by the bundled checks."
),
default=None,
metavar="OKTA_SCOPES",
)
+ okta_rate_limit_subparser = okta_parser.add_argument_group("Rate limiting")
+ okta_rate_limit_subparser.add_argument(
+ "--okta-retries-max-attempts",
+ type=int,
+ default=None,
+ help=(
+ "Maximum number of retries on Okta API rate limiting (HTTP 429). "
+ "Overrides the config.yaml value (okta_max_retries). Default: 5."
+ ),
+ metavar="OKTA_RETRIES_MAX_ATTEMPTS",
+ )
+ okta_rate_limit_subparser.add_argument(
+ "--okta-requests-per-second",
+ type=float,
+ default=None,
+ help=(
+ "Maximum aggregate Okta API requests per second. Throttles requests "
+ "to stay under Okta's rate limits. Overrides the config.yaml value "
+ "(okta_requests_per_second); set to 0 to disable. Default: 4."
+ ),
+ metavar="OKTA_REQUESTS_PER_SECOND",
+ )
diff --git a/prowler/providers/okta/lib/service/pagination.py b/prowler/providers/okta/lib/service/pagination.py
new file mode 100644
index 0000000000..a30bbf9477
--- /dev/null
+++ b/prowler/providers/okta/lib/service/pagination.py
@@ -0,0 +1,69 @@
+"""Shared pagination helpers for Okta SDK list calls.
+
+The Okta SDK exposes paginated list endpoints (`list_applications`,
+`list_policies`, `list_log_streams`, `list_identity_providers`, …) that
+return a tuple `(items, response, error)`. The next page is signalled
+through an RFC 5988 `Link: <…>; rel="next"` header carrying an opaque
+`after` cursor.
+
+These helpers are used by every Okta service that needs to drain a
+paginated endpoint. They live here so we don't keep copy-pasting them
+into each service module.
+"""
+
+from typing import Optional
+from urllib.parse import parse_qs, urlparse
+
+
+def next_after_cursor(resp) -> Optional[str]:
+ """Extract the `after` cursor from a `Link: ...; rel="next"` header.
+
+ Returns None when there is no next page. Header format follows RFC
+ 5988 and Okta's pagination guide.
+ """
+ if resp is None:
+ return None
+ headers = getattr(resp, "headers", None) or {}
+ link = headers.get("link") or headers.get("Link") or ""
+ if not link:
+ return None
+ for part in link.split(","):
+ if 'rel="next"' not in part:
+ continue
+ url_segment = part.split(";", 1)[0].strip().lstrip("<").rstrip(">")
+ cursor = parse_qs(urlparse(url_segment).query).get("after", [None])[0]
+ if cursor:
+ return cursor
+ return None
+
+
+async def paginate(fetch):
+ """Drain all pages of an SDK list call.
+
+ `fetch` is a callable that accepts the `after` cursor (or None for
+ the first page) and returns the SDK's standard `(items, resp, err)`
+ tuple — or the 2-tuple early-error shape `(items, err)`. Follows the
+ `Link: rel="next"` header until exhausted. The returned tuple is
+ `(all_items, error)` — error is non-None only when a page fails
+ to fetch.
+ """
+ all_items = []
+ result = await fetch(None)
+ err = result[-1]
+ if err is not None:
+ return [], err
+ items = result[0]
+ resp = result[1] if len(result) >= 3 else None
+ all_items.extend(items or [])
+ while True:
+ cursor = next_after_cursor(resp)
+ if not cursor:
+ break
+ result = await fetch(cursor)
+ err = result[-1]
+ if err is not None:
+ return all_items, err
+ items = result[0]
+ resp = result[1] if len(result) >= 3 else None
+ all_items.extend(items or [])
+ return all_items, None
diff --git a/prowler/providers/okta/lib/service/rate_limiter.py b/prowler/providers/okta/lib/service/rate_limiter.py
new file mode 100644
index 0000000000..9a8c72fe63
--- /dev/null
+++ b/prowler/providers/okta/lib/service/rate_limiter.py
@@ -0,0 +1,105 @@
+"""Client-side request throttling for the Okta provider.
+
+The Okta SDK already retries on HTTP 429 (see `service.py`), but retrying is
+reactive: it only helps *after* a rate limit has been hit, and each backoff
+waits out a full reset window. To avoid hitting Okta's limits in the first
+place, this module paces outbound requests with a shared token bucket.
+
+A single `OktaRateLimiter` instance lives on the provider and is shared by every
+service's SDK client, so the cap applies to the *aggregate* request rate rather
+than per client. The limiter is injected by wrapping the SDK's `HTTPClient`
+(via the `httpClient` config key) and awaiting `acquire()` before each call.
+
+Note: Okta enforces rate limits per endpoint, so a single requests-per-second
+cap is a deliberately simple, blunt control. It keeps bursty pagination from
+overrunning the limits without trying to model every per-endpoint budget.
+"""
+
+import asyncio
+import threading
+import time
+
+from okta.http_client import HTTPClient
+
+# Default aggregate request rate. Okta-managed orgs commonly throttle the
+# busiest endpoints around a handful of requests per second, so we pace below
+# that by default. Set `okta_requests_per_second` to 0 (or a negative value) to
+# disable throttling entirely.
+DEFAULT_REQUESTS_PER_SECOND = 4
+
+
+class OktaRateLimiter:
+ """Token-bucket limiter shared across a provider's Okta SDK clients.
+
+ The bucket refills at `requests_per_second` tokens per second up to a small
+ burst capacity. `acquire()` consumes one token, sleeping just long enough
+ when the bucket is empty. Token accounting is wall-clock based
+ (`time.monotonic`) so it stays correct across the separate event loops the
+ services spin up with `asyncio.run`.
+ """
+
+ def __init__(
+ self,
+ requests_per_second: float,
+ *,
+ clock=time.monotonic,
+ sleep=asyncio.sleep,
+ ):
+ if requests_per_second <= 0:
+ raise ValueError("requests_per_second must be greater than 0")
+ self._rate = float(requests_per_second)
+ # Allow up to one second of requests to burst, then settle to the rate.
+ self._capacity = max(1.0, self._rate)
+ self._tokens = self._capacity
+ self._clock = clock
+ self._sleep = sleep
+ self._last = clock()
+ # Guards the token math only; never held across an await.
+ self._lock = threading.Lock()
+
+ async def acquire(self) -> None:
+ """Block until a request token is available, then consume it."""
+ while True:
+ with self._lock:
+ now = self._clock()
+ self._tokens = min(
+ self._capacity, self._tokens + (now - self._last) * self._rate
+ )
+ self._last = now
+ if self._tokens >= 1:
+ self._tokens -= 1
+ return
+ wait = (1 - self._tokens) / self._rate
+ await self._sleep(wait)
+
+
+def build_throttled_http_client(limiter: OktaRateLimiter) -> type[HTTPClient]:
+ """Return an `HTTPClient` subclass that paces requests through `limiter`.
+
+ The Okta SDK instantiates `config["httpClient"]` with its HTTP config, so we
+ return a class (not an instance) that closes over the shared limiter.
+
+ Args:
+ limiter: Shared token-bucket limiter that paces the aggregate request
+ rate across every service client of the provider.
+
+ Returns:
+ An `HTTPClient` subclass that awaits the limiter before each request.
+ """
+
+ class ThrottledHTTPClient(HTTPClient):
+ """`HTTPClient` that acquires a limiter token before each request."""
+
+ async def send_request(self, request):
+ """Acquire a rate-limit token, then delegate to the SDK client.
+
+ Args:
+ request: The request payload built by the Okta SDK.
+
+ Returns:
+ The result of the underlying `HTTPClient.send_request` call.
+ """
+ await limiter.acquire()
+ return await super().send_request(request)
+
+ return ThrottledHTTPClient
diff --git a/prowler/providers/okta/lib/service/raw_fetch.py b/prowler/providers/okta/lib/service/raw_fetch.py
new file mode 100644
index 0000000000..42e8eede11
--- /dev/null
+++ b/prowler/providers/okta/lib/service/raw_fetch.py
@@ -0,0 +1,141 @@
+"""Raw-JSON HTTP fetch via the Okta SDK's request executor.
+
+Some Okta Management API endpoints are not yet exposed as typed methods
+on the SDK client (e.g. `/api/v1/automations`), or the typed path's
+pydantic deserialization rejects values the API actually returns (e.g.
+the `KnowledgeConstraint.types` lowercase issue we hit on
+`list_policy_rules`). In both cases we go around the typed layer:
+construct the request via `client._request_executor.create_request`,
+execute without a response type, and parse the body ourselves.
+
+`get_json` returns the parsed JSON payload (typically a list or dict)
+or raises with a descriptive log line on any of the failure modes —
+request build, transport, decode, parse. `get_json_paginated` drains
+list endpoints by following the `Link: rel="next"` cursor — without it,
+the raw fallback would silently truncate at the per-request `limit`.
+Callers are expected to project the JSON onto their own pydantic snapshot.
+"""
+
+import json
+from typing import Any, Optional
+from urllib.parse import parse_qsl, urlencode, urlparse, urlunparse
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import next_after_cursor
+
+
+async def get_json(
+ client,
+ path: str,
+ *,
+ accept: str = "application/json",
+ context: Optional[str] = None,
+) -> Optional[Any]:
+ """GET `path` via the SDK's request executor and return parsed JSON.
+
+ Returns the decoded JSON payload on success, or None when the
+ request, transport, or decode steps fail. Each failure path emits a
+ `logger.error` line tagged with `context` so the caller can grep
+ for it.
+ """
+ label = context or path
+ request, error = await client._request_executor.create_request(
+ method="GET",
+ url=path,
+ body=None,
+ headers={"Accept": accept},
+ )
+ if error is not None:
+ logger.error(f"Raw fetch (create_request) failed for {label}: {error}")
+ return None
+
+ _response, response_body, error = await client._request_executor.execute(request)
+ if error is not None:
+ logger.error(f"Raw fetch (execute) failed for {label}: {error}")
+ return None
+
+ if isinstance(response_body, (bytes, bytearray)):
+ try:
+ response_body = response_body.decode("utf-8")
+ except UnicodeDecodeError as decode_err:
+ logger.error(f"Could not decode response for {label}: {decode_err}")
+ return None
+ try:
+ return json.loads(response_body) if response_body else None
+ except json.JSONDecodeError as decode_err:
+ logger.error(f"Could not parse JSON for {label}: {decode_err}")
+ return None
+
+
+async def get_json_paginated(
+ client,
+ path: str,
+ *,
+ page_size: int = 200,
+ accept: str = "application/json",
+ context: Optional[str] = None,
+) -> Optional[list]:
+ """Drain all pages of a raw-JSON list endpoint.
+
+ Mirrors the typed `pagination.paginate` shape but operates on the
+ SDK's request executor directly. Follows the `Link: rel="next"`
+ header until exhausted, accumulating items across pages. Returns
+ the concatenated list, or None if any page fails to fetch or the
+ response is not a JSON array.
+
+ `page_size` is appended as `limit=N` to the first request; subsequent
+ requests use the URL Okta returns via the cursor.
+ """
+ label = context or path
+ all_items: list = []
+ current_path = _set_query(path, {"limit": str(page_size)})
+ while True:
+ request, error = await client._request_executor.create_request(
+ method="GET",
+ url=current_path,
+ body=None,
+ headers={"Accept": accept},
+ )
+ if error is not None:
+ logger.error(f"Raw fetch (create_request) failed for {label}: {error}")
+ return None
+
+ response, response_body, error = await client._request_executor.execute(request)
+ if error is not None:
+ logger.error(f"Raw fetch (execute) failed for {label}: {error}")
+ return None
+
+ if isinstance(response_body, (bytes, bytearray)):
+ try:
+ response_body = response_body.decode("utf-8")
+ except UnicodeDecodeError as decode_err:
+ logger.error(f"Could not decode response for {label}: {decode_err}")
+ return None
+ if not response_body:
+ break
+ try:
+ page = json.loads(response_body)
+ except json.JSONDecodeError as decode_err:
+ logger.error(f"Could not parse JSON for {label}: {decode_err}")
+ return None
+ if not isinstance(page, list):
+ logger.error(
+ f"Unexpected raw payload shape for {label}: "
+ f"{type(page).__name__}; expected list"
+ )
+ return None
+ all_items.extend(page)
+
+ cursor = next_after_cursor(response)
+ if not cursor:
+ break
+ current_path = _set_query(path, {"limit": str(page_size), "after": cursor})
+ return all_items
+
+
+def _set_query(path: str, params: dict) -> str:
+ """Return `path` with the given query params merged in (overriding existing)."""
+ parsed = urlparse(path)
+ qs = dict(parse_qsl(parsed.query))
+ qs.update({k: v for k, v in params.items() if v is not None})
+ return urlunparse(parsed._replace(query=urlencode(qs)))
diff --git a/prowler/providers/okta/lib/service/service.py b/prowler/providers/okta/lib/service/service.py
index baaabcb219..0c6c24c186 100644
--- a/prowler/providers/okta/lib/service/service.py
+++ b/prowler/providers/okta/lib/service/service.py
@@ -3,11 +3,21 @@ from typing import TYPE_CHECKING
from okta.client import Client as OktaSDKClient
+from prowler.providers.okta.lib.service.rate_limiter import build_throttled_http_client
from prowler.providers.okta.models import OktaSession
if TYPE_CHECKING:
from prowler.providers.okta.okta_provider import OktaProvider
+# Okta API rate-limit handling. The okta-sdk-python `Client` already backs off
+# on HTTP 429 by sleeping until the `X-Rate-Limit-Reset` window before retrying,
+# but it only does so `maxRetries` times (SDK default 2). On busy orgs that is
+# too few and requests fail with partial data, so we raise it. See config.yaml
+# (`okta_max_retries` / `okta_request_timeout`) for the user-facing knobs and the
+# rationale behind the 300s timeout default.
+DEFAULT_MAX_RETRIES = 5
+DEFAULT_REQUEST_TIMEOUT = 300
+
class OktaService:
"""Base class for Okta service implementations.
@@ -20,13 +30,34 @@ class OktaService:
def __init__(self, service: str, provider: "OktaProvider"):
self.provider = provider
self.service = service
- self.client = self.__set_client__(provider.session)
self.audit_config = provider.audit_config
self.fixer_config = provider.fixer_config
+ self.client = self.__set_client__(
+ provider.session, self.audit_config, provider.rate_limiter
+ )
@staticmethod
- def __set_client__(session: OktaSession) -> OktaSDKClient:
- return OktaSDKClient(session.to_sdk_config())
+ def __set_client__(
+ session: OktaSession, audit_config: dict, rate_limiter=None
+ ) -> OktaSDKClient:
+ # Start from the shared SDK config and layer the rate-limit settings on
+ # top. `Client(config)` deep-merges these flat keys onto its defaults, so
+ # `rateLimit`/`requestTimeout` override the SDK's built-in values.
+ config = session.to_sdk_config()
+ audit_config = audit_config or {}
+ config["rateLimit"] = {
+ "maxRetries": audit_config.get("okta_max_retries", DEFAULT_MAX_RETRIES)
+ }
+ config["requestTimeout"] = audit_config.get(
+ "okta_request_timeout", DEFAULT_REQUEST_TIMEOUT
+ )
+ # Proactively pace outbound requests so scans stay under Okta's limits
+ # instead of relying on the 429 retry as a safety net. The limiter is
+ # shared across every service client of the provider, so the cap applies
+ # to the aggregate request rate.
+ if rate_limiter is not None:
+ config["httpClient"] = build_throttled_http_client(rate_limiter)
+ return OktaSDKClient(config)
@staticmethod
def _run(coro):
diff --git a/prowler/providers/okta/models.py b/prowler/providers/okta/models.py
index 0f9c14a87b..b3f5c1f1cc 100644
--- a/prowler/providers/okta/models.py
+++ b/prowler/providers/okta/models.py
@@ -32,6 +32,12 @@ class OktaSession(BaseModel):
class OktaIdentityInfo(BaseModel):
org_domain: str
client_id: str
+ # Scopes actually granted in the access token (`scp` claim). Used by
+ # services to distinguish "no data" from "no permission" so checks can
+ # surface the missing scope rather than a misleading FAIL. Empty when
+ # decoding the token was not possible — callers must treat empty as
+ # "unknown" and fall back to attempting the API call.
+ granted_scopes: list[str] = []
class OktaOutputOptions(ProviderOutputOptions):
diff --git a/prowler/providers/okta/okta_provider.py b/prowler/providers/okta/okta_provider.py
index d26cfaee5c..757e81d51d 100644
--- a/prowler/providers/okta/okta_provider.py
+++ b/prowler/providers/okta/okta_provider.py
@@ -1,4 +1,6 @@
import asyncio
+import base64
+import json
import os
import re
from os import environ
@@ -22,14 +24,30 @@ from prowler.providers.okta.exceptions.exceptions import (
OktaInsufficientPermissionsError,
OktaInvalidCredentialsError,
OktaInvalidOrgDomainError,
+ OktaInvalidProviderIdError,
OktaPrivateKeyFileError,
OktaSetUpIdentityError,
OktaSetUpSessionError,
)
from prowler.providers.okta.lib.mutelist.mutelist import OktaMutelist
+from prowler.providers.okta.lib.service.rate_limiter import (
+ DEFAULT_REQUESTS_PER_SECOND,
+ OktaRateLimiter,
+)
from prowler.providers.okta.models import OktaIdentityInfo, OktaSession
-DEFAULT_SCOPES = ["okta.policies.read"]
+DEFAULT_SCOPES = [
+ "okta.policies.read",
+ "okta.brands.read",
+ "okta.apps.read",
+ "okta.authenticators.read",
+ "okta.networkZones.read",
+ "okta.apiTokens.read",
+ "okta.roles.read",
+ "okta.groups.read",
+ "okta.logStreams.read",
+ "okta.idps.read",
+]
# Accept only Okta-managed domains. Custom (vanity) domains are rejected on
# purpose — they're a recurring source of typos and silent misconfig and
# Prowler's audience overwhelmingly uses Okta-managed hosts. The TLDs below
@@ -64,12 +82,14 @@ class OktaProvider(Provider):
"""
_type: str = "okta"
+ sdk_only: bool = False
_auth_method: str = None
_session: OktaSession
_identity: OktaIdentityInfo
_audit_config: dict
_fixer_config: dict
_mutelist: Mutelist
+ _rate_limiter: Optional[OktaRateLimiter]
audit_metadata: Audit_Metadata
def __init__(
@@ -79,6 +99,8 @@ class OktaProvider(Provider):
okta_private_key: str = "",
okta_private_key_file: str = "",
okta_scopes: Optional[Union[str, list[str]]] = None,
+ okta_retries_max_attempts: int = None,
+ okta_requests_per_second: float = None,
config_path: str = None,
config_content: dict = None,
fixer_config: dict = {},
@@ -110,6 +132,30 @@ class OktaProvider(Provider):
if not config_path:
config_path = default_config_file_path
self._audit_config = load_and_validate_config_file(self._type, config_path)
+
+ # CLI flags take precedence over config.yaml for the Okta API rate-limit
+ # settings. Services read these from audit_config when building the SDK
+ # client, so override the loaded values here.
+ if okta_retries_max_attempts is not None:
+ self._audit_config["okta_max_retries"] = okta_retries_max_attempts
+ logger.info(f"Okta max retries set to {okta_retries_max_attempts}")
+ if okta_requests_per_second is not None:
+ self._audit_config["okta_requests_per_second"] = okta_requests_per_second
+
+ # Build the shared request limiter once, here, so every service client
+ # paces against the same token bucket. A value of 0 (or below) disables
+ # throttling.
+ requests_per_second = self._audit_config.get(
+ "okta_requests_per_second", DEFAULT_REQUESTS_PER_SECOND
+ )
+ if requests_per_second and requests_per_second > 0:
+ self._rate_limiter = OktaRateLimiter(requests_per_second)
+ logger.info(
+ f"Okta request throttling enabled at {requests_per_second} req/s"
+ )
+ else:
+ self._rate_limiter = None
+
self._fixer_config = fixer_config
if mutelist_content:
@@ -149,6 +195,10 @@ class OktaProvider(Provider):
def mutelist(self) -> OktaMutelist:
return self._mutelist
+ @property
+ def rate_limiter(self) -> Optional[OktaRateLimiter]:
+ return self._rate_limiter
+
@staticmethod
def validate_arguments(
okta_org_domain: str = "",
@@ -284,14 +334,32 @@ class OktaProvider(Provider):
org URL plus the service-app client ID. We still hit the cheapest
scope-covered endpoint (`list_policies` with limit=1) to fail loud
when credentials, scopes, or the granted admin role are wrong.
+
+ After the probe succeeds, the access token's `scp` claim is
+ decoded and exposed on the identity. Services compare it against
+ their required scope so checks can emit "missing scope X" rather
+ than a misleading "no resources returned" finding.
"""
async def _probe():
client = OktaSDKClient(session.to_sdk_config())
- return await client.list_policies(type="OKTA_SIGN_ON", limit="1")
+ result = await client.list_policies(type="OKTA_SIGN_ON", limit="1")
+ access_token = None
+ # The OAuth helper caches the token on `_access_token` after
+ # the first authenticated call. Reach through `_request_executor`
+ # — a documented internal but a moving target across SDK
+ # versions, so any failure here degrades silently to empty
+ # granted_scopes (services then fall back to attempting calls).
+ try:
+ oauth = getattr(client._request_executor, "_oauth", None)
+ if oauth is not None:
+ access_token = getattr(oauth, "_access_token", None)
+ except Exception:
+ access_token = None
+ return result, access_token
try:
- result = asyncio.run(_probe())
+ result, access_token = asyncio.run(_probe())
# SDK returns (items, resp, err) on the normal path and (items, err)
# only on early request-creation errors. The error is always last.
err = result[-1]
@@ -304,6 +372,11 @@ class OktaProvider(Provider):
"forbidden",
"not authorized",
"permission",
+ # Okta emits HTTP 400 `consent_required` when none of the
+ # requested scopes are consented on the service app —
+ # semantically a permission gap, not a credential one.
+ "consent_required",
+ "not allowed",
)
if any(signal in err_text for signal in permission_signals):
raise OktaInsufficientPermissionsError(
@@ -320,6 +393,7 @@ class OktaProvider(Provider):
return OktaIdentityInfo(
org_domain=session.org_domain,
client_id=session.client_id,
+ granted_scopes=OktaProvider._decode_token_scopes(access_token),
)
except (OktaInvalidCredentialsError, OktaInsufficientPermissionsError):
raise
@@ -329,6 +403,40 @@ class OktaProvider(Provider):
)
raise OktaSetUpIdentityError(original_exception=error)
+ @staticmethod
+ def _decode_token_scopes(access_token: Optional[str]) -> list[str]:
+ """Return the `scp` claim from a JWT access token, or `[]` on failure.
+
+ No signature verification: the token came from Okta over TLS via
+ the SDK's OAuth handshake, so the only thing we extract is the
+ scope claim. Any decode error returns an empty list — callers
+ must treat empty as "unknown" rather than "no scopes granted".
+ """
+ if not access_token:
+ return []
+ try:
+ parts = access_token.split(".")
+ if len(parts) < 2:
+ return []
+ payload_b64 = parts[1]
+ # Base64url pad to a multiple of 4 — JWT segments are
+ # unpadded per RFC 7515.
+ padding = "=" * (-len(payload_b64) % 4)
+ payload_bytes = base64.urlsafe_b64decode(payload_b64 + padding)
+ payload = json.loads(payload_bytes)
+ scp = payload.get("scp")
+ if isinstance(scp, list):
+ return [str(s) for s in scp if s]
+ if isinstance(scp, str):
+ return [s for s in scp.split(" ") if s]
+ return []
+ except Exception as error:
+ logger.warning(
+ f"Could not decode Okta access token scopes: "
+ f"{error.__class__.__name__}: {error}"
+ )
+ return []
+
def print_credentials(self):
report_lines = [
f"Okta Domain: {Fore.YELLOW}{self.identity.org_domain}{Style.RESET_ALL}",
@@ -348,8 +456,17 @@ class OktaProvider(Provider):
okta_private_key_file: str = "",
okta_scopes: Optional[Union[str, list[str]]] = None,
raise_on_exception: bool = True,
+ provider_id: str = None,
) -> Connection:
- """Test the connection to Okta with the provided OAuth credentials."""
+ """Test the connection to Okta with the provided OAuth credentials.
+
+ Args:
+ provider_id: The provider ID (Okta org domain). When supplied, the
+ authenticated org domain must match it — guards against the
+ stored provider UID drifting from the org the credentials were
+ actually issued for. Compared case-insensitively, matching the
+ normalization applied during session setup.
+ """
try:
OktaProvider.validate_arguments(
okta_org_domain=okta_org_domain,
@@ -364,7 +481,17 @@ class OktaProvider(Provider):
private_key_file=okta_private_key_file,
scopes=okta_scopes,
)
- OktaProvider.setup_identity(session)
+ identity = OktaProvider.setup_identity(session)
+
+ if provider_id and provider_id.strip().lower() != identity.org_domain:
+ raise OktaInvalidProviderIdError(
+ file=os.path.basename(__file__),
+ message=(
+ f"The provider ID '{provider_id}' does not match the "
+ f"authenticated Okta org domain '{identity.org_domain}'."
+ ),
+ )
+
return Connection(is_connected=True)
except Exception as error:
logger.critical(
diff --git a/prowler/providers/okta/services/apitoken/__init__.py b/prowler/providers/okta/services/apitoken/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/apitoken/api_token_client.py b/prowler/providers/okta/services/apitoken/api_token_client.py
new file mode 100644
index 0000000000..fbe10d7c7f
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/api_token_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.apitoken.api_token_service import ApiToken
+
+api_token_client = ApiToken(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/apitoken/api_token_service.py b/prowler/providers/okta/services/apitoken/api_token_service.py
new file mode 100644
index 0000000000..5fafd71c35
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/api_token_service.py
@@ -0,0 +1,327 @@
+from typing import Optional
+
+from pydantic import BaseModel, Field, ValidationError
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate as _paginate_shared
+from prowler.providers.okta.lib.service.raw_fetch import (
+ get_json_paginated as _raw_get_json_paginated,
+)
+from prowler.providers.okta.lib.service.service import OktaService
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "api_tokens": "okta.apiTokens.read",
+ "network_zones": "okta.networkZones.read",
+ "user_roles": "okta.roles.read",
+ # Needed to resolve admin roles inherited via group membership.
+ # `/api/v1/users/{id}/roles` returns only direct role assignments;
+ # group-inherited Super Admin is invisible without `okta.groups.read`
+ # to enumerate the user's groups.
+ "user_groups": "okta.groups.read",
+}
+
+
+def _value(value) -> str:
+ """Return plain string values from Okta SDK enums and raw strings."""
+ if value is None:
+ return ""
+ enum_value = getattr(value, "value", None)
+ if enum_value is not None:
+ return str(enum_value)
+ return str(value)
+
+
+def _role_to_string(role) -> str:
+ """Pick the most specific role identifier from an SDK Role object.
+
+ `list_assigned_roles_for_user` and `list_group_assigned_roles` return
+ `ListGroupAssignedRoles200ResponseInner` — a oneOf wrapper that holds
+ the real `StandardRole`/`CustomRole` on `.actual_instance`. Reading
+ `.type`/`.label` from the wrapper returns None and the role silently
+ disappears, so unwrap first.
+ """
+ inner = getattr(role, "actual_instance", None) or role
+ return _value(getattr(inner, "type", None)) or _value(getattr(inner, "label", None))
+
+
+def _raw_value(item, key: str) -> str:
+ """Return a string value from an SDK model or raw dictionary."""
+ if isinstance(item, dict):
+ return _value(item.get(key))
+ return _value(getattr(item, key, None))
+
+
+class ApiToken(OktaService):
+ """Fetches Okta API token metadata, token owners' roles, and zones."""
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+ # Per-resource caches keyed on the Okta resource id. API tokens
+ # commonly share owners (e.g. a service user holding multiple
+ # tokens) and admin groups frequently overlap across users, so we
+ # memoize the resolutions within a single service instance.
+ self._user_roles_cache: dict[str, list[str]] = {}
+ self._group_roles_cache: dict[str, list[str]] = {}
+ self.known_network_zone_ids: set[str] = (
+ set()
+ if self.missing_scope["api_tokens"] or self.missing_scope["network_zones"]
+ else self._list_known_network_zone_ids()
+ )
+ self.api_tokens: dict[str, OktaApiToken] = (
+ {} if self.missing_scope["api_tokens"] else self._list_api_tokens()
+ )
+
+ def _list_api_tokens(self) -> dict[str, "OktaApiToken"]:
+ """List active API token metadata and owner roles."""
+ logger.info("ApiToken - Listing Okta API tokens...")
+ try:
+ return self._run(self._fetch_api_tokens())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_api_tokens(self) -> dict[str, "OktaApiToken"]:
+ # `list_api_tokens` is non-paginated in the SDK (no `after`
+ # parameter); we inline the tuple unwrap rather than going
+ # through `paginate`. Same pattern application_service uses for
+ # `get_first_party_app_settings`.
+ result: dict[str, OktaApiToken] = {}
+ sdk_result = await self.client.list_api_tokens()
+ err = sdk_result[-1]
+ if err is not None:
+ logger.error(f"Error listing API tokens: {err}")
+ return result
+ items = sdk_result[0] or []
+
+ for token in items:
+ token_id = _value(getattr(token, "id", None))
+ user_id = _value(getattr(token, "user_id", None))
+ roles = (
+ await self._fetch_effective_user_role_types(user_id) if user_id else []
+ )
+ network = getattr(token, "network", None)
+ token_obj = OktaApiToken(
+ id=token_id,
+ name=_value(getattr(token, "name", None)) or token_id,
+ client_name=_value(getattr(token, "client_name", None)),
+ user_id=user_id,
+ network_connection=_value(getattr(network, "connection", None)),
+ network_includes=list(getattr(network, "include", None) or []),
+ network_excludes=list(getattr(network, "exclude", None) or []),
+ owner_roles=roles,
+ )
+ result[token_obj.id] = token_obj
+ return result
+
+ async def _fetch_effective_user_role_types(self, user_id: str) -> list[str]:
+ """Return direct + group-inherited admin role types for `user_id`.
+
+ Okta's `/api/v1/users/{userId}/roles` (the SDK's
+ `list_assigned_roles_for_user`) only returns roles assigned
+ *directly* to the user. Roles inherited via group membership are
+ invisible to that endpoint — but they are how Okta normally
+ grants Super Admin (e.g. the org creator joins the default
+ "Okta Super Admins" group). Without resolving group-inherited
+ roles, the Super Admin check would falsely PASS for any token
+ whose owner gets admin via a group.
+
+ Results are memoized per `user_id` so multiple tokens with the
+ same owner cost a single resolution.
+ """
+ if user_id in self._user_roles_cache:
+ return self._user_roles_cache[user_id]
+ direct = await self._fetch_direct_user_role_types(user_id)
+ inherited = await self._fetch_group_inherited_role_types(user_id)
+ # Dedupe while preserving first-seen order (direct first, then
+ # inherited) so the status_extended reads from most-specific.
+ seen: set[str] = set()
+ combined: list[str] = []
+ for role in (*direct, *inherited):
+ if role and role not in seen:
+ combined.append(role)
+ seen.add(role)
+ self._user_roles_cache[user_id] = combined
+ return combined
+
+ async def _fetch_direct_user_role_types(self, user_id: str) -> list[str]:
+ """Return roles assigned directly to the user (no group inheritance)."""
+ if self.missing_scope["user_roles"]:
+ return []
+ # `list_assigned_roles_for_user` is non-paginated in the SDK
+ # (no `after` parameter); inline the tuple unwrap.
+ sdk_result = await self.client.list_assigned_roles_for_user(user_id)
+ err = sdk_result[-1]
+ if err is not None:
+ logger.error(f"Error listing roles for token owner {user_id}: {err}")
+ return []
+ items = sdk_result[0] or []
+ roles = [_role_to_string(role) for role in items if _role_to_string(role)]
+ if roles or not items:
+ return roles
+
+ # Belt-and-suspenders: when the SDK's typed parse returns items
+ # but every projection ends up empty (a discriminator surface we
+ # don't yet handle, a future schema change, …), fall back to the
+ # raw JSON. The `_role_to_string` unwrap above already covers the
+ # known `ListGroupAssignedRoles200ResponseInner` oneOf wrapper
+ # bug — this fallback exists for whatever the next SDK quirk is.
+ return await self._fetch_user_role_types_raw(user_id)
+
+ async def _fetch_user_role_types_raw(self, user_id: str) -> list[str]:
+ """Return user role types from the raw response when typed models are empty.
+
+ Uses the shared `get_json_paginated` helper so any `Link: next`
+ header the API returns is followed (role lists are typically
+ small, but the SDK doesn't paginate this endpoint at all so the
+ only correct way to drain it lives here).
+ """
+ raw_items = await _raw_get_json_paginated(
+ self.client,
+ f"/api/v1/users/{user_id}/roles",
+ context=f"user roles for {user_id}",
+ )
+ if raw_items is None:
+ return []
+ roles = [
+ _value(role.get("type")) or _value(role.get("label"))
+ for role in raw_items
+ if isinstance(role, dict)
+ ]
+ return [role for role in roles if role]
+
+ async def _fetch_group_inherited_role_types(self, user_id: str) -> list[str]:
+ """Return roles inherited via the user's group memberships.
+
+ Each group's role list is itself memoized — admin groups are
+ commonly shared across many users.
+ """
+ if self.missing_scope["user_roles"] or self.missing_scope["user_groups"]:
+ return []
+ # Defensive try/except: tenants we've seen in the wild return 403
+ # on `/api/v1/users/{id}/groups` even when `okta.groups.read` is
+ # granted (admin-role on the service app gates the response
+ # separately). Treat any failure as "no inherited roles" so the
+ # caller still surfaces direct roles cleanly.
+ try:
+ sdk_result = await self.client.list_user_groups(user_id)
+ except Exception as error:
+ logger.error(
+ f"Error listing groups for token owner {user_id}: "
+ f"{error.__class__.__name__}: {error}"
+ )
+ return []
+ err = sdk_result[-1]
+ if err is not None:
+ logger.error(f"Error listing groups for token owner {user_id}: {err}")
+ return []
+ groups = sdk_result[0] or []
+ roles: list[str] = []
+ for group in groups:
+ group_id = _value(getattr(group, "id", None))
+ if not group_id:
+ continue
+ if group_id in self._group_roles_cache:
+ roles.extend(self._group_roles_cache[group_id])
+ continue
+ # Per-group try/except: one group's parse or auth failure
+ # must not erase admin-role coverage for other groups.
+ try:
+ group_roles = await self._fetch_group_role_types(group_id)
+ except Exception as error:
+ logger.error(
+ f"Error listing roles for group {group_id} "
+ f"(owner={user_id}): {error.__class__.__name__}: {error}"
+ )
+ group_roles = []
+ self._group_roles_cache[group_id] = group_roles
+ roles.extend(group_roles)
+ return roles
+
+ async def _fetch_group_role_types(self, group_id: str) -> list[str]:
+ """Return role types assigned to `group_id`."""
+ sdk_result = await self.client.list_group_assigned_roles(group_id)
+ err = sdk_result[-1]
+ if err is not None:
+ logger.error(f"Error listing roles for group {group_id}: {err}")
+ return []
+ items = sdk_result[0] or []
+ return [_role_to_string(role) for role in items if _role_to_string(role)]
+
+ def _list_known_network_zone_ids(self) -> set[str]:
+ """List known Network Zone ids and names for token condition validation."""
+ logger.info("ApiToken - Listing Network Zones for token restrictions...")
+ try:
+ return self._run(self._fetch_known_network_zone_ids())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return set()
+
+ async def _fetch_known_network_zone_ids(self) -> set[str]:
+ identifiers: set[str] = set()
+ items, err = await self._fetch_all_network_zones()
+ if err is not None:
+ logger.error(f"Error listing Network Zones for API token checks: {err}")
+ return identifiers
+ for zone in items:
+ zone_id = _raw_value(zone, "id")
+ zone_name = _raw_value(zone, "name")
+ if zone_id:
+ identifiers.add(zone_id)
+ if zone_name:
+ identifiers.add(zone_name)
+ return identifiers
+
+ async def _fetch_all_network_zones(self) -> tuple[list, object]:
+ """Drain all Network Zone pages for API token reference validation.
+
+ Catches the upstream Okta SDK ↔ Management API schema drift on
+ Enhanced Dynamic Zones (object-shaped pydantic model where the
+ API returns a JSON array) the same way `network_zone_service`
+ does. `(ValueError, ValidationError)` covers both discriminator
+ misses and model mismatches — matching the `user_service`
+ precedent.
+ """
+ try:
+ return await _paginate_shared(
+ lambda after: self.client.list_network_zones(after=after, limit=200)
+ )
+ except (ValueError, ValidationError) as ex:
+ logger.warning(
+ f"Okta SDK raised {type(ex).__name__} parsing Network Zones "
+ "for API token validation — falling back to raw-JSON parse."
+ )
+ return await self._fetch_all_network_zones_raw()
+
+ async def _fetch_all_network_zones_raw(self) -> tuple[list, object]:
+ """Drain Network Zone pages via the shared raw-JSON helper."""
+ items = await _raw_get_json_paginated(
+ self.client,
+ "/api/v1/zones",
+ page_size=200,
+ context="Network Zones for API token validation",
+ )
+ if items is None:
+ return [], Exception("raw Network Zones fetch failed; see logs")
+ return items, None
+
+
+class OktaApiToken(BaseModel):
+ """Normalized Okta API token metadata used by checks."""
+
+ id: str
+ name: str
+ client_name: str = ""
+ user_id: str = ""
+ network_connection: str = ""
+ network_includes: list[str] = Field(default_factory=list)
+ network_excludes: list[str] = Field(default_factory=list)
+ owner_roles: list[str] = Field(default_factory=list)
diff --git a/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/__init__.py b/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.metadata.json b/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.metadata.json
new file mode 100644
index 0000000000..d15c5b4680
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "apitoken_not_super_admin",
+ "CheckTitle": "Okta API tokens are not owned by Super Admin users",
+ "CheckType": [],
+ "ServiceName": "apitoken",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Okta API token ownership** should avoid Super Admin users because API tokens inherit the admin permissions of the user that created them.",
+ "Risk": "**Super Admin-owned API tokens** become high-impact secrets: if one is exposed, an attacker can perform broad organization administration with the token owner privileges.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/guides/roles",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/apitoken"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "Create a dedicated service account, assign only required admin roles, rotate the API token, and revoke Super Admin-owned tokens.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Use dedicated Okta service accounts** for API tokens and assign only the least-privilege admin roles required; rotate and revoke tokens created by Super Admin users.",
+ "Url": "https://hub.prowler.com/check/apitoken_not_super_admin"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.py b/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.py
new file mode 100644
index 0000000000..0971af4aab
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/apitoken_not_super_admin/apitoken_not_super_admin.py
@@ -0,0 +1,70 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.apitoken.api_token_client import api_token_client
+from prowler.providers.okta.services.apitoken.lib.api_token_helpers import (
+ missing_api_token_scope_finding,
+ missing_user_roles_scope_for_token_finding,
+ owner_has_super_admin,
+)
+
+
+class apitoken_not_super_admin(Check):
+ """Ensure Okta API tokens are not owned by Super Admin users."""
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate every active API token owner's assigned admin roles."""
+ org_domain = api_token_client.provider.identity.org_domain
+ missing_api_token_scope = api_token_client.missing_scope.get("api_tokens")
+ if missing_api_token_scope:
+ return [
+ missing_api_token_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_api_token_scope,
+ additional_required=["okta.roles.read", "okta.groups.read"],
+ )
+ ]
+
+ missing_user_roles_scope = api_token_client.missing_scope.get("user_roles")
+ # `okta.groups.read` is needed to resolve admin roles inherited via
+ # group membership. Without it we fall back to direct-only role
+ # assignments, which Okta returns for `/api/v1/users/{id}/roles` —
+ # commonly empty for trial accounts where Super Admin is granted
+ # through the default admin group. The finding stays evaluable but
+ # is flagged as best-effort so operators know to grant the scope.
+ missing_user_groups_scope = api_token_client.missing_scope.get("user_groups")
+ findings: list[CheckReportOkta] = []
+ for token in api_token_client.api_tokens.values():
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=token, org_domain=org_domain
+ )
+ if missing_user_roles_scope:
+ report = missing_user_roles_scope_for_token_finding(
+ self.metadata(), org_domain, token, missing_user_roles_scope
+ )
+ elif owner_has_super_admin(token):
+ report.status = "FAIL"
+ report.status_extended = (
+ f"API token {token.name} is owned by user {token.user_id} "
+ "with the Super Admin role. Use a dedicated service account "
+ "with least-privilege admin roles instead."
+ )
+ else:
+ roles = (
+ ", ".join(token.owner_roles)
+ if token.owner_roles
+ else "no admin roles returned"
+ )
+ caveat = (
+ " Group-inherited roles were not checked because the "
+ f"`{missing_user_groups_scope}` scope is missing — grant "
+ "it to detect Super Admin assigned via group membership."
+ if missing_user_groups_scope
+ else ""
+ )
+ report.status = "PASS"
+ report.status_extended = (
+ f"API token {token.name} owner {token.user_id} is not "
+ f"assigned Super Admin ({roles}).{caveat}"
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/__init__.py b/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.metadata.json b/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.metadata.json
new file mode 100644
index 0000000000..4a088a0c1c
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "apitoken_restricted_to_network_zone",
+ "CheckTitle": "Okta API tokens are restricted to known Network Zones",
+ "CheckType": [],
+ "ServiceName": "apitoken",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**Okta API token network restrictions** should prevent token use from Any IP by tying each token to known Okta Network Zones.",
+ "Risk": "**API tokens allowed from Any IP** can be replayed from attacker-controlled infrastructure if the secret is exposed, removing an important network boundary.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/apitoken",
+ "https://help.okta.com/oie/en-us/content/topics/security/api.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "Security > API > Tokens: edit each token Security section and select specific Network Zones instead of Any IP.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Restrict every Okta API token to trusted IP-based Network Zones** and review token network conditions whenever service locations change.",
+ "Url": "https://hub.prowler.com/check/apitoken_restricted_to_network_zone"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.py b/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.py
new file mode 100644
index 0000000000..04cfcf2df7
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/apitoken_restricted_to_network_zone/apitoken_restricted_to_network_zone.py
@@ -0,0 +1,55 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.apitoken.api_token_client import api_token_client
+from prowler.providers.okta.services.apitoken.lib.api_token_helpers import (
+ definite_network_zone_restriction_failure,
+ missing_api_token_scope_finding,
+ missing_network_zone_scope_for_token_finding,
+ network_zone_restriction_status,
+)
+
+
+class apitoken_restricted_to_network_zone(Check):
+ """Ensure Okta API tokens are restricted to known Network Zones."""
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate every active API token's network condition."""
+ org_domain = api_token_client.provider.identity.org_domain
+ missing_api_token_scope = api_token_client.missing_scope.get("api_tokens")
+ if missing_api_token_scope:
+ return [
+ missing_api_token_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_api_token_scope,
+ additional_required=["okta.networkZones.read"],
+ )
+ ]
+
+ missing_network_zone_scope = api_token_client.missing_scope.get("network_zones")
+ findings: list[CheckReportOkta] = []
+ for token in api_token_client.api_tokens.values():
+ if missing_network_zone_scope:
+ definite_failure = definite_network_zone_restriction_failure(token)
+ if definite_failure:
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=token,
+ org_domain=org_domain,
+ )
+ report.status, report.status_extended = definite_failure
+ else:
+ report = missing_network_zone_scope_for_token_finding(
+ self.metadata(), org_domain, token, missing_network_zone_scope
+ )
+ else:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=token, org_domain=org_domain
+ )
+ (
+ report.status,
+ report.status_extended,
+ ) = network_zone_restriction_status(
+ token, api_token_client.known_network_zone_ids
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/apitoken/lib/__init__.py b/prowler/providers/okta/services/apitoken/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/apitoken/lib/api_token_helpers.py b/prowler/providers/okta/services/apitoken/lib/api_token_helpers.py
new file mode 100644
index 0000000000..3a871714ae
--- /dev/null
+++ b/prowler/providers/okta/services/apitoken/lib/api_token_helpers.py
@@ -0,0 +1,140 @@
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.apitoken.api_token_service import OktaApiToken
+
+ANYWHERE_CONNECTIONS = {"", "ANYWHERE", "ANY_IP"}
+_SCOPE_ADVICE = (
+ "Grant it on the Okta API Scopes tab of the service app in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def network_zone_restriction_status(
+ token: OktaApiToken, known_network_zone_ids: set[str]
+) -> tuple[str, str]:
+ """Evaluate whether an API token is restricted to known Network Zones."""
+ connection = token.network_connection.upper()
+ if connection in ANYWHERE_CONNECTIONS:
+ return (
+ "FAIL",
+ f"API token {token.name} can be used from any IP address. "
+ "Restrict the token to one or more known Okta Network Zones.",
+ )
+
+ if not token.network_includes:
+ return (
+ "FAIL",
+ f"API token {token.name} does not allowlist a specific Okta "
+ "Network Zone. Excluded zones do not restrict the token to trusted "
+ "source networks.",
+ )
+
+ unknown_zones = [
+ zone for zone in token.network_includes if zone not in known_network_zone_ids
+ ]
+ if unknown_zones:
+ return (
+ "FAIL",
+ f"API token {token.name} references unknown Network Zone(s): "
+ f"{', '.join(unknown_zones)}.",
+ )
+
+ return (
+ "PASS",
+ f"API token {token.name} is restricted to known Okta Network Zone(s): "
+ f"{', '.join(token.network_includes)}.",
+ )
+
+
+def definite_network_zone_restriction_failure(
+ token: OktaApiToken,
+) -> tuple[str, str] | None:
+ """Return a definite network restriction failure that does not need zone lookup."""
+ connection = token.network_connection.upper()
+ if connection in ANYWHERE_CONNECTIONS or not token.network_includes:
+ return network_zone_restriction_status(token, set())
+ return None
+
+
+def owner_has_super_admin(token: OktaApiToken) -> bool:
+ """Return True when any token owner role is Super Admin."""
+ for role in token.owner_roles:
+ normalized = role.strip().replace(" ", "_").upper()
+ if normalized in {"SUPER_ADMIN", "SUPER_ADMINISTRATOR"}:
+ return True
+ return False
+
+
+def missing_api_token_scope_finding(
+ metadata,
+ org_domain: str,
+ scope: str,
+ additional_required: list[str] | None = None,
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when API tokens cannot be listed.
+
+ `additional_required` lets the calling check name the secondary
+ scopes it also needs (e.g. `okta.roles.read` for the Super Admin
+ check, `okta.networkZones.read` for the zone-restriction check) so
+ the operator can grant everything in one go instead of re-running
+ once per missing scope.
+ """
+ resource = OktaApiToken(
+ id="api-tokens-scope-missing",
+ name="(scope not granted)",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=resource, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ if additional_required:
+ extras = f" This check also requires {_format_scope_list(additional_required)}."
+ advice = (
+ "Grant them on the service app's Okta API Scopes tab in the Okta "
+ "Admin Console, then re-run the check."
+ )
+ else:
+ extras = ""
+ advice = _SCOPE_ADVICE
+ report.status_extended = (
+ f"Could not retrieve Okta API token metadata: the Okta service app "
+ f"is missing the required `{scope}` API scope.{extras} {advice}"
+ )
+ return report
+
+
+def _format_scope_list(scopes: list[str]) -> str:
+ """Format a list of scope names as backticked, comma-joined text."""
+ formatted = [f"`{scope}`" for scope in scopes]
+ if len(formatted) == 1:
+ return formatted[0]
+ if len(formatted) == 2:
+ return " and ".join(formatted)
+ return ", ".join(formatted[:-1]) + f", and {formatted[-1]}"
+
+
+def missing_network_zone_scope_for_token_finding(
+ metadata, org_domain: str, token: OktaApiToken, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when token zones cannot be validated."""
+ report = CheckReportOkta(metadata=metadata, resource=token, org_domain=org_domain)
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not validate Network Zone restrictions for API token "
+ f"{token.name}: the Okta service app is missing the required "
+ f"`{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
+
+
+def missing_user_roles_scope_for_token_finding(
+ metadata, org_domain: str, token: OktaApiToken, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when token owner roles cannot be listed."""
+ report = CheckReportOkta(metadata=metadata, resource=token, org_domain=org_domain)
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve admin roles for API token {token.name} owner "
+ f"{token.user_id}: the Okta service app is missing the required "
+ f"`{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
diff --git a/prowler/providers/okta/services/application/__init__.py b/prowler/providers/okta/services/application/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_admin_console_mfa_required/__init__.py b/prowler/providers/okta/services/application/application_admin_console_mfa_required/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.metadata.json b/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.metadata.json
new file mode 100644
index 0000000000..dbe02f23f8
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_admin_console_mfa_required",
+ "CheckTitle": "Okta Admin Console authentication policy enforces multifactor authentication",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "The **Authentication Policy** bound to the **Okta Admin Console** app must require MFA. On its top active rule, *User must authenticate with* must be set to `Password / IdP + Another factor` or `Any 2 factor types` (`factorMode=2FA` in the API).",
+ "Risk": "Single-factor access to the Okta control plane is the highest-impact identity risk in the tenant.\n\n- **Credential compromise** is enough to take over every administrator account\n- **Lateral movement** into every downstream SaaS that trusts Okta SSO\n- **Privileged configuration changes** with no second-factor barrier",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-app-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication Policies**.\n3. Open the **Okta Admin Console** policy.\n4. Edit the top active rule.\n5. Set *User must authenticate with* to `Password / IdP + Another factor` or `Any 2 factor types`.\n6. Save the rule.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require MFA on the top active rule of the Okta Admin Console authentication policy. Set *User must authenticate with* to `Password / IdP + Another factor` or `Any 2 factor types`.",
+ "Url": "https://hub.prowler.com/check/application_admin_console_mfa_required"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273193 / OKTA-APP-000560."
+}
diff --git a/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.py b/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.py
new file mode 100644
index 0000000000..bf21a1a766
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_mfa_required/application_admin_console_mfa_required.py
@@ -0,0 +1,89 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ ADMIN_CONSOLE_APP_NAME,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ app_label,
+ app_not_found_finding,
+ missing_app_scope_finding,
+ policy_missing_finding,
+ rule_label,
+ top_active_rule,
+)
+
+ADMIN_CONSOLE_LABEL_HINT = "Okta Admin Console"
+
+
+class application_admin_console_mfa_required(Check):
+ """STIG V-273193 / OKTA-APP-000560.
+
+ The Authentication Policy bound to the Okta Admin Console app must
+ require multifactor authentication on its top rule: `User must
+ authenticate with` set to `Password / IdP + Another factor` or
+ `Any 2 factor types`.
+
+ The underlying SDK exposes this as `AssuranceMethod.factor_mode`
+ with values `1FA` / `2FA`.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = application_client.provider.identity.org_domain
+
+ for scope_key in ("built_in_apps", "access_policies"):
+ missing_scope = application_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_app_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_scope,
+ ADMIN_CONSOLE_LABEL_HINT,
+ )
+ )
+ return findings
+
+ app = application_client.built_in_apps.get(ADMIN_CONSOLE_APP_NAME)
+ if app is None:
+ findings.append(
+ app_not_found_finding(
+ self.metadata(), org_domain, ADMIN_CONSOLE_LABEL_HINT
+ )
+ )
+ return findings
+
+ if app.access_policy_id is None or app.access_policy is None:
+ findings.append(policy_missing_finding(self.metadata(), org_domain, app))
+ return findings
+
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=app, org_domain=org_domain
+ )
+ rule = top_active_rule(app)
+ if rule is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{app_label(app)} has no active rules on its Authentication "
+ "Policy. The top rule must set `User must authenticate with` to "
+ "`Password / IdP + Another factor` or `Any 2 factor types`."
+ )
+ elif rule.factor_mode == "2FA":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} enforces "
+ "multifactor authentication (`factorMode=2FA`)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} does not "
+ f"enforce multifactor authentication "
+ f"(`factorMode={rule.factor_mode or 'unset'}`). "
+ "Set `User must authenticate with` to `Password / IdP + Another "
+ "factor` or `Any 2 factor types`."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/__init__.py b/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.metadata.json b/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.metadata.json
new file mode 100644
index 0000000000..0c86fdd974
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_admin_console_phishing_resistant_authentication",
+ "CheckTitle": "Okta Admin Console authentication policy enforces phishing-resistant factors",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "The **Authentication Policy** bound to the **Okta Admin Console** app must restrict possession factors to phishing-resistant authenticators (FIDO2/WebAuthn, PIV/CAC, Okta FastPass with biometrics). On the top active rule, *Possession factor constraints are: Phishing resistant* must be checked (`possession.phishingResistant=REQUIRED`).",
+ "Risk": "Phishable possession factors (SMS, voice, standard push, OTP delivered via reverse-proxy AiTM) leave the most privileged surface of the IdP exposed.\n\n- **Credential phishing** against administrators succeeds despite MFA\n- **Adversary-in-the-Middle attacks** capture session tokens through fake login pages\n- **Account takeover** of the tenant control plane",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/authenticators/phishing-resistant-auth.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication Policies**.\n3. Open the **Okta Admin Console** policy.\n4. Edit the top active rule.\n5. Under *Possession factor constraints are*, check **Phishing resistant**.\n6. Save the rule.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require phishing-resistant possession factors on the top active rule of the Okta Admin Console authentication policy.",
+ "Url": "https://hub.prowler.com/check/application_admin_console_phishing_resistant_authentication"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273191 / OKTA-APP-000190."
+}
diff --git a/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.py b/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.py
new file mode 100644
index 0000000000..237ffe27bb
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_phishing_resistant_authentication/application_admin_console_phishing_resistant_authentication.py
@@ -0,0 +1,88 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ ADMIN_CONSOLE_APP_NAME,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ app_label,
+ app_not_found_finding,
+ missing_app_scope_finding,
+ policy_missing_finding,
+ rule_label,
+ top_active_rule,
+)
+
+ADMIN_CONSOLE_LABEL_HINT = "Okta Admin Console"
+
+
+class application_admin_console_phishing_resistant_authentication(Check):
+ """STIG V-273191 / OKTA-APP-000190.
+
+ The Authentication Policy bound to the Okta Admin Console app must
+ restrict possession factors to phishing-resistant authenticators.
+ The underlying SDK exposes `phishingResistant` on each
+ `PossessionConstraint`; at least one constraint object on the top
+ rule must set `phishingResistant=REQUIRED` (constraints are OR-ed
+ by Okta semantics).
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = application_client.provider.identity.org_domain
+
+ for scope_key in ("built_in_apps", "access_policies"):
+ missing_scope = application_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_app_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_scope,
+ ADMIN_CONSOLE_LABEL_HINT,
+ )
+ )
+ return findings
+
+ app = application_client.built_in_apps.get(ADMIN_CONSOLE_APP_NAME)
+ if app is None:
+ findings.append(
+ app_not_found_finding(
+ self.metadata(), org_domain, ADMIN_CONSOLE_LABEL_HINT
+ )
+ )
+ return findings
+
+ if app.access_policy_id is None or app.access_policy is None:
+ findings.append(policy_missing_finding(self.metadata(), org_domain, app))
+ return findings
+
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=app, org_domain=org_domain
+ )
+ rule = top_active_rule(app)
+ if rule is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{app_label(app)} has no active rules on its Authentication "
+ "Policy. The top rule must mark "
+ "`Possession factor constraints are: Phishing resistant`."
+ )
+ elif rule.possession_phishing_resistant_required:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} enforces "
+ "phishing-resistant possession factors "
+ "(`possession.phishingResistant=REQUIRED`)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} does not "
+ "enforce phishing-resistant possession factors. Enable "
+ "`Possession factor constraints are: Phishing resistant` "
+ "on the rule."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/__init__.py b/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.metadata.json b/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.metadata.json
new file mode 100644
index 0000000000..fda8cd7816
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_admin_console_session_idle_timeout_15min",
+ "CheckTitle": "Okta Admin Console app session idle timeout is 15 minutes or less",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "The integrated **Okta Admin Console** app must close idle privileged sessions. *Maximum app session idle time* on the **Sign On** tab must be `15` minutes or less.\n\nThreshold override: `okta_admin_console_idle_timeout_max_minutes`.",
+ "Risk": "An unattended administrator workstation leaves the Okta control plane open for session hijacking.\n\n- **Privileged session takeover** by anyone with physical or remote access to the workstation\n- **Tenant-wide configuration changes** under the absent administrator's identity\n- **Bypassed reauthentication** for the most sensitive surface of the IdP",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/guides/configure-signon-policy/main/",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OktaApplicationSettings/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Applications** > **Applications** > **Okta Admin Console**.\n3. Open the **Sign On** tab.\n4. Under **Okta Admin Console session**, set *Maximum app session idle time* to `15` minutes or less.\n5. Save the changes.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Set the *Maximum app session idle time* of the Okta Admin Console first-party app to `15` minutes or less so privileged administrator sessions terminate on inactivity.",
+ "Url": "https://hub.prowler.com/check/application_admin_console_session_idle_timeout_15min"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273187 / OKTA-APP-000025."
+}
diff --git a/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.py b/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.py
new file mode 100644
index 0000000000..6103360f07
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_admin_console_session_idle_timeout_15min/application_admin_console_session_idle_timeout_15min.py
@@ -0,0 +1,89 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ AdminConsoleAppSettings,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ missing_admin_console_settings_scope_finding,
+)
+
+DEFAULT_THRESHOLD_MINUTES = 15
+
+
+class application_admin_console_session_idle_timeout_15min(Check):
+ """STIG V-273187 / OKTA-APP-000025.
+
+ The Okta Admin Console first-party app must set its
+ `Maximum app session idle time` to 15 minutes (or less) so privileged
+ administrator sessions terminate on inactivity. Threshold override:
+ `okta_admin_console_idle_timeout_max_minutes` in the audit config.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ audit_config = application_client.audit_config or {}
+ threshold = audit_config.get(
+ "okta_admin_console_idle_timeout_max_minutes",
+ DEFAULT_THRESHOLD_MINUTES,
+ )
+ org_domain = application_client.provider.identity.org_domain
+
+ missing_scope = application_client.missing_scope.get(
+ "admin_console_app_settings"
+ )
+ if missing_scope:
+ findings.append(
+ missing_admin_console_settings_scope_finding(
+ self.metadata(), org_domain, missing_scope
+ )
+ )
+ return findings
+
+ settings = application_client.admin_console_app_settings
+ if settings is None:
+ placeholder = AdminConsoleAppSettings()
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Could not retrieve the Okta Admin Console first-party app "
+ "settings. Okta restricts `GET /api/v1/first-party-app-settings/"
+ "admin-console` to the Super Administrator role; every other "
+ "role — including Read-Only Administrator — receives "
+ "`403 E0000006`. Assign Super Administrator to the service "
+ f"app to evaluate this check. The `Maximum app session idle "
+ f"time` must be set to {threshold} minutes or less."
+ )
+ findings.append(report)
+ return findings
+
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=settings, org_domain=org_domain
+ )
+ idle = settings.session_idle_timeout_minutes
+ if idle is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ "The Okta Admin Console first-party app does not define a "
+ "`Maximum app session idle time`. This value must be "
+ f"{threshold} minutes or less."
+ )
+ elif idle <= threshold:
+ report.status = "PASS"
+ report.status_extended = (
+ "The Okta Admin Console first-party app sets the maximum "
+ f"app session idle time to {idle} minutes, meeting the "
+ f"configured threshold of {threshold} minutes."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ "The Okta Admin Console first-party app sets the maximum "
+ f"app session idle time to {idle} minutes, exceeding the "
+ f"configured threshold of {threshold} minutes."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/__init__.py b/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.metadata.json b/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.metadata.json
new file mode 100644
index 0000000000..fd9234e0a6
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_authentication_policy_network_zone_enforced",
+ "CheckTitle": "Okta application authentication policies enforce Network Zones",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "Every active Okta application must be bound to an **Authentication Policy** that uses **Network Zones**. Each active non-default rule must map *User's IP* to `In zone` or `Not in zone`, and the active built-in *Catch-all Rule* must set *Access is* to `Denied`.",
+ "Risk": "Applications without network-aware authentication rules can be reached from unauthorized locations and bypass location-based access controls.\n\n- **Unauthorized access paths** from unmanaged or blocked networks\n- **Inconsistent information-flow enforcement** across SSO applications\n- **Residual access** when the fallback rule still allows traffic after policy misses",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-app-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Networks** and define the allow-list and deny-list zones required by policy.\n3. For each active application, open **Applications** > **Applications** > *Application* > **Sign On**.\n4. In **User Authentication**, bind the appropriate **Authentication Policy** and open **View Policy Details**.\n5. For each active non-default rule, set *User's IP* to `In zone` or `Not in zone` and select the correct **Network Zone**.\n6. Edit the built-in **Catch-all Rule** and set *Access is* to `Denied`.\n7. Save the policy.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require every active application Authentication Policy to use Network Zones on each active non-default rule and to deny access on the Catch-all Rule.",
+ "Url": "https://hub.prowler.com/check/application_authentication_policy_network_zone_enforced"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-279693 / OKTA-APP-003244."
+}
diff --git a/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.py b/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.py
new file mode 100644
index 0000000000..5e6e2c9c76
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_authentication_policy_network_zone_enforced/application_authentication_policy_network_zone_enforced.py
@@ -0,0 +1,151 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ AuthenticationPolicyRule,
+ OktaBuiltInApp,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ active_apps,
+ app_label,
+ missing_integrated_apps_scope_finding,
+ no_active_apps_finding,
+ rule_has_network_zone,
+ rule_label,
+)
+
+
+class application_authentication_policy_network_zone_enforced(Check):
+ """STIG V-279693 / OKTA-APP-003244.
+
+ Every active Okta application must be bound to an Authentication
+ Policy that uses Network Zones. Each active non-default rule must map
+ `User's IP` to an allow/deny zone, and the active Catch-all Rule
+ must deny access.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = application_client.provider.identity.org_domain
+
+ for scope_key in ("integrated_apps", "access_policies"):
+ missing_scope = application_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_integrated_apps_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_scope,
+ )
+ )
+ return findings
+
+ apps = active_apps(application_client.integrated_apps)
+ if not apps:
+ findings.append(no_active_apps_finding(self.metadata(), org_domain))
+ return findings
+
+ for app in apps:
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=app,
+ org_domain=org_domain,
+ resource_name=app.label or app.name,
+ resource_id=app.id,
+ )
+ status, status_extended = _evaluate_app(app)
+ report.status = status
+ report.status_extended = status_extended
+ findings.append(report)
+ return findings
+
+
+def _active_rules(app: OktaBuiltInApp) -> list[AuthenticationPolicyRule]:
+ if app.access_policy is None:
+ return []
+ return sorted(
+ [
+ rule
+ for rule in app.access_policy.rules
+ if not rule.status or rule.status.upper() == "ACTIVE"
+ ],
+ key=lambda rule: (
+ rule.priority if rule.priority is not None else float("inf"),
+ rule.name,
+ ),
+ )
+
+
+def _evaluate_app(app: OktaBuiltInApp) -> tuple[str, str]:
+ label = app_label(app)
+ if app.access_policy_id is None or app.access_policy is None:
+ return (
+ "FAIL",
+ f"{label} has no Authentication Policy bound to it. "
+ "Bind an Access Policy in Security > Authentication Policies.",
+ )
+
+ active_rules = _active_rules(app)
+ if not active_rules:
+ return (
+ "FAIL",
+ f"{label} has no active rules on its Authentication Policy. "
+ "Every active non-default rule must enforce a Network Zone "
+ "condition, and the Catch-all Rule must set `Access is: Denied`.",
+ )
+
+ nondefault_rules = [
+ rule
+ for rule in active_rules
+ if not rule.is_default and rule.name != "Catch-all Rule"
+ ]
+ if not nondefault_rules:
+ return (
+ "FAIL",
+ f"{label} has no active non-default rules on its Authentication "
+ "Policy. Define at least one non-default rule that maps `User's "
+ "IP` to a Network Zone, and use the Catch-all Rule only as the "
+ "final deny path.",
+ )
+
+ missing_zone_rules = [
+ rule.name for rule in nondefault_rules if not rule_has_network_zone(rule)
+ ]
+ if missing_zone_rules:
+ quoted_rules = ", ".join(f"'{rule_name}'" for rule_name in missing_zone_rules)
+ return (
+ "FAIL",
+ f"{label} has active non-default rule(s) without Network Zones: "
+ f"{quoted_rules}. Configure `User's IP` to `In zone` or `Not in zone` "
+ "for every active non-default rule.",
+ )
+
+ catch_all_rule = next(
+ (
+ rule
+ for rule in active_rules
+ if rule.is_default or rule.name == "Catch-all Rule"
+ ),
+ None,
+ )
+ if catch_all_rule is None:
+ return (
+ "FAIL",
+ f"{label} has no active Catch-all Rule. The Catch-all Rule must "
+ "deny access after the zoned non-default rules.",
+ )
+
+ if catch_all_rule.access != "DENY":
+ return (
+ "FAIL",
+ f"Active {rule_label(catch_all_rule)} on {label} does not set "
+ f"`Access is` to `DENY` (`access={catch_all_rule.access or 'unset'}`). "
+ "Set the Catch-all Rule to deny access.",
+ )
+
+ return (
+ "PASS",
+ f"{label} applies Network Zones on every active non-default rule and "
+ f"its active {rule_label(catch_all_rule)} denies access.",
+ )
diff --git a/prowler/providers/okta/services/application/application_client.py b/prowler/providers/okta/services/application/application_client.py
new file mode 100644
index 0000000000..63658ea3c6
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.application.application_service import Application
+
+application_client = Application(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/application/application_dashboard_mfa_required/__init__.py b/prowler/providers/okta/services/application/application_dashboard_mfa_required/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.metadata.json b/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.metadata.json
new file mode 100644
index 0000000000..1211eaec62
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_dashboard_mfa_required",
+ "CheckTitle": "Okta Dashboard authentication policy enforces multifactor authentication",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "The **Authentication Policy** bound to the **Okta Dashboard** app must require MFA for end users. On its top active rule, *User must authenticate with* must be set to `Password / IdP + Another factor` or `Any 2 factor types` (`factorMode=2FA` in the API).",
+ "Risk": "Single-factor access to the Okta Dashboard lets an attacker pivot from one compromised password into every downstream SSO app.\n\n- **Credential stuffing** and password reuse attacks succeed in one step\n- **Lateral movement** into every SaaS the user has access to via Okta SSO\n- **Weakened identity assurance** for every user signing in to the end-user portal",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-app-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication Policies**.\n3. Open the **Okta Dashboard** policy.\n4. Edit the top active rule.\n5. Set *User must authenticate with* to `Password / IdP + Another factor` or `Any 2 factor types`.\n6. Save the rule.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require MFA on the top active rule of the Okta Dashboard authentication policy. Set *User must authenticate with* to `Password / IdP + Another factor` or `Any 2 factor types`.",
+ "Url": "https://hub.prowler.com/check/application_dashboard_mfa_required"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273194 / OKTA-APP-000570."
+}
diff --git a/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.py b/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.py
new file mode 100644
index 0000000000..48c04083fb
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_dashboard_mfa_required/application_dashboard_mfa_required.py
@@ -0,0 +1,85 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ DASHBOARD_APP_NAME,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ app_label,
+ app_not_found_finding,
+ missing_app_scope_finding,
+ policy_missing_finding,
+ rule_label,
+ top_active_rule,
+)
+
+DASHBOARD_LABEL_HINT = "Okta Dashboard"
+
+
+class application_dashboard_mfa_required(Check):
+ """STIG V-273194 / OKTA-APP-000570.
+
+ The Authentication Policy bound to the Okta Dashboard app must
+ require multifactor authentication on its top rule for
+ non-privileged users: `User must authenticate with` set to
+ `Password / IdP + Another factor` or `Any 2 factor types`
+ (`AssuranceMethod.factor_mode == "2FA"`).
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = application_client.provider.identity.org_domain
+
+ for scope_key in ("built_in_apps", "access_policies"):
+ missing_scope = application_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_app_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_scope,
+ DASHBOARD_LABEL_HINT,
+ )
+ )
+ return findings
+
+ app = application_client.built_in_apps.get(DASHBOARD_APP_NAME)
+ if app is None:
+ findings.append(
+ app_not_found_finding(self.metadata(), org_domain, DASHBOARD_LABEL_HINT)
+ )
+ return findings
+
+ if app.access_policy_id is None or app.access_policy is None:
+ findings.append(policy_missing_finding(self.metadata(), org_domain, app))
+ return findings
+
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=app, org_domain=org_domain
+ )
+ rule = top_active_rule(app)
+ if rule is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{app_label(app)} has no active rules on its Authentication "
+ "Policy. The top rule must set `User must authenticate with` to "
+ "`Password / IdP + Another factor` or `Any 2 factor types`."
+ )
+ elif rule.factor_mode == "2FA":
+ report.status = "PASS"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} enforces "
+ "multifactor authentication (`factorMode=2FA`)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} does not "
+ f"enforce multifactor authentication "
+ f"(`factorMode={rule.factor_mode or 'unset'}`). "
+ "Set `User must authenticate with` to `Password / IdP + Another "
+ "factor` or `Any 2 factor types`."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/__init__.py b/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.metadata.json b/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.metadata.json
new file mode 100644
index 0000000000..1c8996280b
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "application_dashboard_phishing_resistant_authentication",
+ "CheckTitle": "Okta Dashboard authentication policy enforces phishing-resistant factors",
+ "CheckType": [],
+ "ServiceName": "application",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "The **Authentication Policy** bound to the **Okta Dashboard** app must restrict possession factors to phishing-resistant authenticators. On the top active rule, *Possession factor constraints are: Phishing resistant* must be checked (`possession.phishingResistant=REQUIRED`).",
+ "Risk": "Phishable possession factors leave end-user SSO sessions exposed to credential phishing and AiTM proxies.\n\n- **Credential phishing** against end users succeeds despite MFA\n- **Session token theft** through reverse-proxy AiTM attacks (Evilginx-class tooling)\n- **Compromise of every downstream SSO app** the user has access to",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/authenticators/phishing-resistant-auth.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication Policies**.\n3. Open the **Okta Dashboard** policy.\n4. Edit the top active rule.\n5. Under *Possession factor constraints are*, check **Phishing resistant**.\n6. Save the rule.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Require phishing-resistant possession factors on the top active rule of the Okta Dashboard authentication policy.",
+ "Url": "https://hub.prowler.com/check/application_dashboard_phishing_resistant_authentication"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273190 / OKTA-APP-000180."
+}
diff --git a/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.py b/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.py
new file mode 100644
index 0000000000..11fa310da2
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_dashboard_phishing_resistant_authentication/application_dashboard_phishing_resistant_authentication.py
@@ -0,0 +1,84 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.application.application_client import (
+ application_client,
+)
+from prowler.providers.okta.services.application.application_service import (
+ DASHBOARD_APP_NAME,
+)
+from prowler.providers.okta.services.application.lib.application_helpers import (
+ app_label,
+ app_not_found_finding,
+ missing_app_scope_finding,
+ policy_missing_finding,
+ rule_label,
+ top_active_rule,
+)
+
+DASHBOARD_LABEL_HINT = "Okta Dashboard"
+
+
+class application_dashboard_phishing_resistant_authentication(Check):
+ """STIG V-273190 / OKTA-APP-000180.
+
+ The Authentication Policy bound to the Okta Dashboard app must
+ restrict possession factors to phishing-resistant authenticators on
+ its top active rule
+ (`possession.phishingResistant=REQUIRED`).
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = application_client.provider.identity.org_domain
+
+ for scope_key in ("built_in_apps", "access_policies"):
+ missing_scope = application_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_app_scope_finding(
+ self.metadata(),
+ org_domain,
+ missing_scope,
+ DASHBOARD_LABEL_HINT,
+ )
+ )
+ return findings
+
+ app = application_client.built_in_apps.get(DASHBOARD_APP_NAME)
+ if app is None:
+ findings.append(
+ app_not_found_finding(self.metadata(), org_domain, DASHBOARD_LABEL_HINT)
+ )
+ return findings
+
+ if app.access_policy_id is None or app.access_policy is None:
+ findings.append(policy_missing_finding(self.metadata(), org_domain, app))
+ return findings
+
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=app, org_domain=org_domain
+ )
+ rule = top_active_rule(app)
+ if rule is None:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{app_label(app)} has no active rules on its Authentication "
+ "Policy. The top rule must mark "
+ "`Possession factor constraints are: Phishing resistant`."
+ )
+ elif rule.possession_phishing_resistant_required:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} enforces "
+ "phishing-resistant possession factors "
+ "(`possession.phishingResistant=REQUIRED`)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Top active {rule_label(rule)} on {app_label(app)} does not "
+ "enforce phishing-resistant possession factors. Enable "
+ "`Possession factor constraints are: Phishing resistant` "
+ "on the rule."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/application/application_service.py b/prowler/providers/okta/services/application/application_service.py
new file mode 100644
index 0000000000..fa6f483021
--- /dev/null
+++ b/prowler/providers/okta/services/application/application_service.py
@@ -0,0 +1,501 @@
+from typing import Optional
+from urllib.parse import urlparse
+
+from pydantic import BaseModel, ValidationError
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate as _paginate_shared
+from prowler.providers.okta.lib.service.raw_fetch import (
+ get_json_paginated as _raw_get_json_paginated,
+)
+from prowler.providers.okta.lib.service.service import OktaService
+
+# These three keys are Okta-platform constants, not tenant-configurable:
+#
+# - `saasure` / `okta_enduser` are the `name` fields of the OIN catalog
+# templates for the Okta Admin Console and Okta Dashboard built-in apps.
+# The Okta SDK's `OINApplication.name` is documented as "the key name for
+# the OIN app definition" — tied to the platform-level template, not
+# editable by customers. The user-facing field is `label`, which we read
+# only for display purposes in finding text.
+# - `admin-console` is the Okta-defined URL key for
+# `/api/v1/first-party-app-settings/{appName}`; per the SDK's own
+# `get_first_party_app_settings` docstring it is the only value Okta
+# currently supports on that endpoint.
+#
+# If Okta introduces a new first-party app or renames one of these at the
+# platform level, both the constants and the check coverage need updating
+# together.
+ADMIN_CONSOLE_APP_NAME = "saasure"
+DASHBOARD_APP_NAME = "okta_enduser"
+ADMIN_CONSOLE_FIRST_PARTY_APP_KEY = "admin-console"
+
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "admin_console_app_settings": "okta.apps.read",
+ "built_in_apps": "okta.apps.read",
+ "integrated_apps": "okta.apps.read",
+ "access_policies": "okta.policies.read",
+}
+
+
+class Application(OktaService):
+ """Fetches Okta first-party apps and their bound Authentication Policies.
+
+ Populates:
+ - `self.admin_console_app_settings` — first-party Admin Console session
+ knobs (`sessionIdleTimeoutMinutes`, `sessionMaxLifetimeMinutes`).
+ - `self.built_in_apps` — keyed by canonical `name` (`saasure`,
+ `okta_enduser`). Each entry carries the resolved Authentication
+ Policy (Access Policy) and its rules.
+ - `self.integrated_apps` — lazily populated and keyed by application id.
+ Used by the per-application network-zone STIG to evaluate every
+ active app returned by `/api/v1/apps`.
+
+ Required OAuth scopes (`REQUIRED_SCOPES`) are compared against the
+ access token's granted scopes (`provider.identity.granted_scopes`).
+ When a scope is known to be missing, the corresponding fetch is
+ skipped and recorded in `self.missing_scope` so each check can emit
+ an explicit MANUAL finding instead of a misleading
+ "no resources returned". Empty granted_scopes means "unknown" — the
+ service attempts the fetch and lets the SDK fail loudly.
+ """
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+
+ self.admin_console_app_settings: Optional[AdminConsoleAppSettings] = (
+ None
+ if self.missing_scope["admin_console_app_settings"]
+ else self._get_admin_console_app_settings()
+ )
+
+ # Apps and policies share the same SDK round-trips, so fetch them
+ # together. When either scope is missing we still attempt the
+ # other, but `built_in_apps` is only populated when both are
+ # available — checks then look at `missing_scope` to report which
+ # one is at fault.
+ if self.missing_scope["built_in_apps"] or self.missing_scope["access_policies"]:
+ self.built_in_apps: dict[str, OktaBuiltInApp] = {}
+ else:
+ self.built_in_apps = self._list_built_in_apps_with_policies()
+ self._integrated_apps: Optional[dict[str, OktaBuiltInApp]] = None
+
+ @property
+ def integrated_apps(self) -> dict[str, "OktaBuiltInApp"]:
+ """List every Okta-integrated app with its Authentication Policy.
+
+ This is fetched lazily because only the V-279693 check needs the
+ full app inventory; the bundled Admin Console / Dashboard checks
+ only need the two built-in apps.
+ """
+ if self._integrated_apps is None:
+ if (
+ self.missing_scope["integrated_apps"]
+ or self.missing_scope["access_policies"]
+ ):
+ self._integrated_apps = {}
+ else:
+ self._integrated_apps = self._list_integrated_apps_with_policies()
+ return self._integrated_apps
+
+ def _get_admin_console_app_settings(self) -> Optional["AdminConsoleAppSettings"]:
+ logger.info("Application - Fetching first-party Admin Console settings...")
+ try:
+ return self._run(self._fetch_admin_console_app_settings())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return None
+
+ async def _fetch_admin_console_app_settings(
+ self,
+ ) -> Optional["AdminConsoleAppSettings"]:
+ result = await self.client.get_first_party_app_settings(
+ ADMIN_CONSOLE_FIRST_PARTY_APP_KEY
+ )
+ err = result[-1]
+ if err is not None:
+ # 404 means the org is on Classic engine or the endpoint isn't
+ # available — fall through to None and checks emit MANUAL.
+ logger.error(f"Error fetching first-party Admin Console settings: {err}")
+ return None
+ data = result[0]
+ if data is None:
+ return None
+ return AdminConsoleAppSettings(
+ session_idle_timeout_minutes=getattr(
+ data, "session_idle_timeout_minutes", None
+ ),
+ session_max_lifetime_minutes=getattr(
+ data, "session_max_lifetime_minutes", None
+ ),
+ )
+
+ def _list_built_in_apps_with_policies(self) -> dict:
+ logger.info("Application - Listing Okta built-in apps and policies...")
+ try:
+ return self._run(self._fetch_built_in_apps_and_policies())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ def _list_integrated_apps_with_policies(self) -> dict:
+ logger.info("Application - Listing integrated Okta apps and policies...")
+ try:
+ return self._run(self._fetch_integrated_apps_and_policies())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_built_in_apps_and_policies(self) -> dict:
+ # Per-app try/except: one app's SDK failure (e.g. ValidationError
+ # while deserializing its policy rules) must not erase findings
+ # for the other.
+ result: dict[str, OktaBuiltInApp] = {}
+ for app_name in (ADMIN_CONSOLE_APP_NAME, DASHBOARD_APP_NAME):
+ try:
+ built_in_app = await self._fetch_built_in_app(app_name)
+ except Exception as error:
+ logger.error(
+ f"Error fetching built-in app {app_name}: "
+ f"{error.__class__.__name__}: {error}"
+ )
+ continue
+ if built_in_app is None:
+ continue
+ if built_in_app.access_policy_id:
+ try:
+ built_in_app.access_policy = await self._fetch_access_policy(
+ built_in_app.access_policy_id
+ )
+ except Exception as error:
+ logger.error(
+ f"Error fetching access policy "
+ f"{built_in_app.access_policy_id} for {app_name}: "
+ f"{error.__class__.__name__}: {error}"
+ )
+ built_in_app.access_policy = None
+ result[app_name] = built_in_app
+ return result
+
+ async def _fetch_integrated_apps_and_policies(self) -> dict:
+ all_apps, err = await self._paginate(
+ lambda after: self.client.list_applications(after=after)
+ )
+ if err is not None:
+ logger.error(f"Error listing integrated apps: {err}")
+ return {}
+
+ # Per-app try/except: a single app's policy fetch failure must
+ # not drop the whole inventory.
+ result: dict[str, OktaBuiltInApp] = {}
+ for app in all_apps:
+ try:
+ app_model = _to_application_model(app)
+ except Exception as error:
+ logger.error(
+ f"Error projecting Okta app onto pydantic model "
+ f"(id={getattr(app, 'id', '?')}): "
+ f"{error.__class__.__name__}: {error}"
+ )
+ continue
+ if app_model.access_policy_id:
+ try:
+ app_model.access_policy = await self._fetch_access_policy(
+ app_model.access_policy_id
+ )
+ except Exception as error:
+ logger.error(
+ f"Error fetching access policy "
+ f"{app_model.access_policy_id} for app "
+ f"{app_model.name} ({app_model.id}): "
+ f"{error.__class__.__name__}: {error}"
+ )
+ app_model.access_policy = None
+ result[app_model.id] = app_model
+ return result
+
+ async def _fetch_built_in_app(self, app_name: str) -> Optional["OktaBuiltInApp"]:
+ # Filter by `name eq` so we don't paginate every app in the org
+ # for a single match. The two OIN-built-in apps are uniquely
+ # identified by their internal `name`.
+ apps, err = await self._paginate(
+ lambda after: self.client.list_applications(
+ filter=f'name eq "{app_name}"', after=after
+ )
+ )
+ if err is not None:
+ logger.error(f"Error listing app with name={app_name}: {err}")
+ return None
+ if not apps:
+ return None
+ return _to_application_model(apps[0])
+
+ async def _fetch_access_policy(
+ self, policy_id: str
+ ) -> Optional["AuthenticationPolicy"]:
+ # Okta's `list_policy_rules` does not accept an `after` cursor in
+ # the SDK signature, so we call once with a generous limit. Auth
+ # policies almost always have <10 rules; a warning is logged if
+ # the limit is hit.
+ rule_fetch_limit = 100
+ try:
+ result = await self.client.list_policy_rules(
+ policy_id, limit=str(rule_fetch_limit)
+ )
+ except ValidationError as ve:
+ # Upstream Okta SDK ↔ Management API enum drift: the SDK's
+ # strict pydantic validators (e.g. KnowledgeConstraint.types
+ # uppercase-only) reject values the API returns lowercase
+ # (e.g. ["password"]). Fall back to a raw-JSON fetch so the
+ # STIG evaluation isn't blocked by an upstream SDK bug.
+ logger.warning(
+ f"Okta SDK raised ValidationError parsing rules for policy "
+ f"{policy_id} ({ve.error_count()} error(s)) — falling back "
+ "to raw-JSON parse. This is an okta-sdk-python deserialization "
+ "bug; the workaround should be removed once upstream fixes it."
+ )
+ return await self._fetch_access_policy_raw(policy_id, rule_fetch_limit)
+
+ err = result[-1]
+ if err is not None:
+ logger.error(f"Error listing rules for access policy {policy_id}: {err}")
+ return AuthenticationPolicy(
+ id=policy_id,
+ name="",
+ status="",
+ is_default=False,
+ rules=[],
+ )
+ all_rules = list(result[0] or [])
+ if len(all_rules) >= rule_fetch_limit:
+ logger.warning(
+ f"Access policy {policy_id} returned {len(all_rules)} rules — "
+ f"the per-policy fetch limit ({rule_fetch_limit}) was hit; any "
+ "rules beyond this limit are not evaluated by Prowler. Review "
+ "the policy in the Okta Admin Console."
+ )
+ rules_out = [_rule_to_model(rule) for rule in all_rules]
+ return AuthenticationPolicy(
+ id=policy_id,
+ name="",
+ status="",
+ is_default=False,
+ rules=rules_out,
+ )
+
+ async def _fetch_access_policy_raw(
+ self, policy_id: str, rule_fetch_limit: int
+ ) -> Optional["AuthenticationPolicy"]:
+ """Raw-JSON fallback for `list_policy_rules`.
+
+ Bypasses the Okta SDK's typed deserialization by calling the
+ request executor directly via the shared `get_json_paginated`
+ helper, which follows `Link: rel=next` so policies with more
+ rules than `rule_fetch_limit` are not silently truncated.
+ Projects the response onto our own pydantic snapshot which only
+ validates the fields the STIG checks actually read. This keeps
+ the checks evaluable on tenants where the Management API returns
+ values the SDK validators reject.
+ """
+ rules_data = await _raw_get_json_paginated(
+ self.client,
+ f"/api/v1/policies/{policy_id}/rules",
+ page_size=rule_fetch_limit,
+ context=f"access policy {policy_id} rules",
+ )
+ if rules_data is None:
+ return AuthenticationPolicy(
+ id=policy_id, name="", status="", is_default=False, rules=[]
+ )
+ rules_out = [_raw_rule_to_model(rule) for rule in rules_data]
+ return AuthenticationPolicy(
+ id=policy_id, name="", status="", is_default=False, rules=rules_out
+ )
+
+ @staticmethod
+ async def _paginate(fetch):
+ return await _paginate_shared(fetch)
+
+
+def _policy_id_from_href(href: Optional[str]) -> Optional[str]:
+ """Extract the trailing policy id from `.../policies/{id}` URLs."""
+ if not href:
+ return None
+ path = urlparse(href).path or href
+ segment = path.rstrip("/").rsplit("/", 1)[-1]
+ return segment or None
+
+
+def _rule_to_model(rule) -> "AuthenticationPolicyRule":
+ """Project an SDK `AccessPolicyRule` onto our pydantic snapshot.
+
+ Pulls out the two STIG-relevant fields from the deeply nested
+ `actions.appSignOn.verificationMethod` tree: the assurance `factor_mode`
+ and whether any possession constraint requires phishing resistance.
+ """
+ actions = getattr(rule, "actions", None)
+ app_sign_on = getattr(actions, "app_sign_on", None) if actions else None
+ verification_method = (
+ getattr(app_sign_on, "verification_method", None) if app_sign_on else None
+ )
+ factor_mode = _stringify_enum(getattr(verification_method, "factor_mode", None))
+ verification_type = _stringify_enum(getattr(verification_method, "type", None))
+ constraints = list(getattr(verification_method, "constraints", None) or [])
+ phishing_resistant_required = False
+ for constraint in constraints:
+ possession = getattr(constraint, "possession", None)
+ if possession is None:
+ continue
+ if (
+ _stringify_enum(getattr(possession, "phishing_resistant", None))
+ == "REQUIRED"
+ ):
+ phishing_resistant_required = True
+ break
+
+ access_action = getattr(app_sign_on, "access", None) if app_sign_on else None
+ conditions = getattr(rule, "conditions", None)
+ network = getattr(conditions, "network", None) if conditions else None
+ return AuthenticationPolicyRule(
+ id=getattr(rule, "id", "") or "",
+ name=getattr(rule, "name", "") or "",
+ priority=getattr(rule, "priority", None),
+ status=getattr(rule, "status", "") or "",
+ is_default=bool(getattr(rule, "system", False)),
+ factor_mode=factor_mode,
+ possession_phishing_resistant_required=phishing_resistant_required,
+ constraints_count=len(constraints),
+ verification_method_type=verification_type,
+ access=_stringify_enum(access_action),
+ network_connection=_stringify_enum(getattr(network, "connection", None)),
+ network_zones_include=list(getattr(network, "include", None) or []),
+ network_zones_exclude=list(getattr(network, "exclude", None) or []),
+ )
+
+
+def _stringify_enum(value) -> Optional[str]:
+ """Return the string form of an enum-or-string value, or None."""
+ if value is None:
+ return None
+ return getattr(value, "value", None) or str(value)
+
+
+def _raw_rule_to_model(rule_dict: dict) -> "AuthenticationPolicyRule":
+ """Project a raw `/api/v1/policies/{id}/rules` JSON rule onto our model.
+
+ Mirrors `_rule_to_model` but reads camelCase JSON keys (`appSignOn`,
+ `verificationMethod`, `phishingResistant`) instead of the SDK's
+ snake_case attribute names. Used by the raw-JSON fallback that
+ activates when the Okta SDK's strict enum validators reject values
+ the Management API returns.
+ """
+ actions = rule_dict.get("actions") or {}
+ app_sign_on = actions.get("appSignOn") or {}
+ verification_method = app_sign_on.get("verificationMethod") or {}
+ factor_mode = verification_method.get("factorMode")
+ verification_type = verification_method.get("type")
+ constraints = verification_method.get("constraints") or []
+ phishing_resistant_required = False
+ for constraint in constraints:
+ possession = (constraint or {}).get("possession") or {}
+ if possession.get("phishingResistant") == "REQUIRED":
+ phishing_resistant_required = True
+ break
+
+ access_action = app_sign_on.get("access")
+ conditions = rule_dict.get("conditions") or {}
+ network = conditions.get("network") or {}
+ return AuthenticationPolicyRule(
+ id=rule_dict.get("id") or "",
+ name=rule_dict.get("name") or "",
+ priority=rule_dict.get("priority"),
+ status=rule_dict.get("status") or "",
+ is_default=bool(rule_dict.get("system", False)),
+ factor_mode=factor_mode,
+ possession_phishing_resistant_required=phishing_resistant_required,
+ constraints_count=len(constraints),
+ verification_method_type=verification_type,
+ access=access_action,
+ network_connection=network.get("connection"),
+ network_zones_include=list(network.get("include") or []),
+ network_zones_exclude=list(network.get("exclude") or []),
+ )
+
+
+class AdminConsoleAppSettings(BaseModel):
+ """First-party Okta Admin Console session settings.
+
+ `id` and `name` are set to fixed sentinels so this can be passed as
+ the `resource` to `CheckReportOkta`, which reads those attributes.
+ """
+
+ id: str = "okta-admin-console-app-settings"
+ name: str = "Okta Admin Console (first-party app settings)"
+ session_idle_timeout_minutes: Optional[int] = None
+ session_max_lifetime_minutes: Optional[int] = None
+
+
+class AuthenticationPolicyRule(BaseModel):
+ id: str
+ name: str
+ priority: Optional[int] = None
+ status: str = ""
+ is_default: bool = False
+ factor_mode: Optional[str] = None
+ possession_phishing_resistant_required: bool = False
+ constraints_count: int = 0
+ verification_method_type: Optional[str] = None
+ access: Optional[str] = None
+ network_connection: Optional[str] = None
+ network_zones_include: list[str] = []
+ network_zones_exclude: list[str] = []
+
+
+class AuthenticationPolicy(BaseModel):
+ id: str
+ name: str = ""
+ status: str = ""
+ is_default: bool = False
+ rules: list[AuthenticationPolicyRule] = []
+
+
+class OktaBuiltInApp(BaseModel):
+ # `id` matches the Okta-generated `0oa…` app identifier; `name` is the
+ # canonical internal name (`saasure`, `okta_enduser`). Both are read
+ # directly by `CheckReportOkta(resource=…)`.
+ id: str
+ name: str
+ label: str = ""
+ status: str = ""
+ access_policy_id: Optional[str] = None
+ access_policy: Optional[AuthenticationPolicy] = None
+
+
+def _application_access_policy_id(app) -> Optional[str]:
+ links = getattr(app, "links", None)
+ access_policy_link = getattr(links, "access_policy", None) if links else None
+ return _policy_id_from_href(
+ getattr(access_policy_link, "href", None) if access_policy_link else None
+ )
+
+
+def _to_application_model(app) -> OktaBuiltInApp:
+ return OktaBuiltInApp(
+ id=getattr(app, "id", "") or "",
+ name=getattr(app, "name", "") or "",
+ label=getattr(app, "label", "") or "",
+ status=getattr(app, "status", "") or "",
+ access_policy_id=_application_access_policy_id(app),
+ )
diff --git a/prowler/providers/okta/services/application/lib/__init__.py b/prowler/providers/okta/services/application/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/application/lib/application_helpers.py b/prowler/providers/okta/services/application/lib/application_helpers.py
new file mode 100644
index 0000000000..90cccc98ec
--- /dev/null
+++ b/prowler/providers/okta/services/application/lib/application_helpers.py
@@ -0,0 +1,212 @@
+"""Shared helpers for the OKTA application STIG checks."""
+
+from typing import Optional
+
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.application.application_service import (
+ AdminConsoleAppSettings,
+ AuthenticationPolicyRule,
+ OktaBuiltInApp,
+)
+
+
+def active_apps(apps: dict[str, OktaBuiltInApp]) -> list[OktaBuiltInApp]:
+ """Return active apps sorted by label/name, id as tiebreaker."""
+ return sorted(
+ [
+ app
+ for app in apps.values()
+ if not app.status or app.status.upper() == "ACTIVE"
+ ],
+ key=lambda app: (app.label or app.name, app.id),
+ )
+
+
+def top_active_rule(
+ app: OktaBuiltInApp,
+) -> Optional[AuthenticationPolicyRule]:
+ """Return the topmost active rule on the app's Authentication Policy.
+
+ Mirrors the STIG fix text — *"Click the 'Actions' button next to the
+ top rule and select 'Edit'"* — by returning the active rule with the
+ lowest `priority` value (= highest precedence). Downstream checks
+ separately reject the rule when it is the built-in Catch-all Rule.
+
+ The priority value itself is intentionally not pinned to a specific
+ integer. Okta indexes Access Policy rule priorities inconsistently
+ across tenants and policy types (some responses report `0` for the
+ top rule, others `1`); the STIG only requires that the topmost rule
+ satisfy the predicate, not that it carry any specific priority literal.
+ """
+ if app.access_policy is None:
+ return None
+ active_rules = sorted(
+ [
+ rule
+ for rule in app.access_policy.rules
+ if not rule.status or rule.status.upper() == "ACTIVE"
+ ],
+ key=lambda rule: (
+ rule.priority if rule.priority is not None else float("inf"),
+ rule.name,
+ ),
+ )
+ if not active_rules:
+ return None
+ return active_rules[0]
+
+
+def app_label(app: OktaBuiltInApp) -> str:
+ """Format a human-readable label for an Okta application."""
+ label = app.label or app.name
+ return f"Okta app '{label}' (app={app.name}, id={app.id})"
+
+
+def rule_label(rule: AuthenticationPolicyRule) -> str:
+ """Format whether a rule is the built-in catch-all or a custom rule."""
+ if rule.is_default or rule.name == "Catch-all Rule":
+ return f"built-in Catch-all Rule '{rule.name}'"
+ return f"non-default rule '{rule.name}'"
+
+
+def rule_has_network_zone(rule: AuthenticationPolicyRule) -> bool:
+ """Return True when the rule maps User's IP to at least one Network Zone."""
+ return bool(rule.network_zones_include or rule.network_zones_exclude)
+
+
+_SCOPE_ADVICE = (
+ "Grant it on the service app's Okta API Scopes tab in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def missing_app_scope_finding(
+ metadata, org_domain: str, scope: str, app_label_hint: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding when an app/policy scope is not granted."""
+ placeholder = OktaBuiltInApp(
+ id="okta-built-in-app-scope-missing",
+ name="(scope not granted)",
+ label=app_label_hint,
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not evaluate the authentication policy for {app_label_hint}: "
+ f"the Okta service app is missing the required `{scope}` API scope. "
+ f"{_SCOPE_ADVICE}"
+ )
+ return report
+
+
+def missing_integrated_apps_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding when the integrated-app inventory scope is not granted."""
+ placeholder = OktaBuiltInApp(
+ id="okta-integrated-apps-scope-missing",
+ name="(scope not granted)",
+ label="Okta integrated applications",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata,
+ resource=placeholder,
+ org_domain=org_domain,
+ resource_name=placeholder.label,
+ resource_id=placeholder.id,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Could not retrieve Okta integrated applications and their "
+ f"authentication policies: the Okta service app is missing the "
+ f"required `{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
+
+
+def missing_admin_console_settings_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding for the Admin Console idle timeout check when scope is missing."""
+ placeholder = AdminConsoleAppSettings()
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Could not retrieve the Okta Admin Console first-party app settings: "
+ f"the Okta service app is missing the required `{scope}` API scope. "
+ f"{_SCOPE_ADVICE}"
+ )
+ return report
+
+
+def app_not_found_finding(
+ metadata, org_domain: str, app_label_hint: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when a built-in OIN app isn't returned.
+
+ Okta filters the first-party apps (`saasure`, `okta_enduser`) out of
+ `/api/v1/apps` for every admin role below Super Administrator, so the
+ check has no way to resolve the app's bound Authentication Policy.
+ """
+ placeholder = OktaBuiltInApp(
+ id="okta-built-in-app-missing",
+ name="(app not found)",
+ label=app_label_hint,
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"The {app_label_hint} first-party app was not returned by the Okta "
+ "API. Okta restricts the visibility of first-party apps "
+ "(`saasure`, `okta_enduser`) to the Super Administrator role; "
+ "every other role — including Read-Only Administrator — receives "
+ "an empty result. Assign Super Administrator to the service app "
+ "to evaluate this check."
+ )
+ return report
+
+
+def no_active_apps_finding(metadata, org_domain: str) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when no active apps are returned."""
+ placeholder = OktaBuiltInApp(
+ id="okta-apps-missing",
+ name="(no active apps)",
+ label="Okta applications",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata,
+ resource=placeholder,
+ org_domain=org_domain,
+ resource_name=placeholder.label,
+ resource_id=placeholder.id,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "No active Okta applications were returned by the API. Verify the "
+ "tenant exposes applications to the Read-Only Administrator role and "
+ "review the application inventory manually."
+ )
+ return report
+
+
+def policy_missing_finding(
+ metadata, org_domain: str, app: OktaBuiltInApp
+) -> CheckReportOkta:
+ """Build the FAIL finding when the built-in app has no bound Access Policy."""
+ report = CheckReportOkta(metadata=metadata, resource=app, org_domain=org_domain)
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{app_label(app)} has no Authentication Policy bound to it. "
+ "Bind an Access Policy in Security > Authentication Policies."
+ )
+ return report
diff --git a/prowler/providers/okta/services/authenticator/__init__.py b/prowler/providers/okta/services/authenticator/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_client.py b/prowler/providers/okta/services/authenticator/authenticator_client.py
new file mode 100644
index 0000000000..3657a2821e
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.authenticator.authenticator_service import (
+ Authenticator,
+)
+
+authenticator_client = Authenticator(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.metadata.json
new file mode 100644
index 0000000000..363b95f84a
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_okta_verify_fips_compliant",
+ "CheckTitle": "Okta Verify authenticator is active and restricts enrollment to FIPS-compliant devices",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The **Okta Verify authenticator** (`okta_verify`) must be present, in the `ACTIVE` status, and configured to require FIPS-compliant devices for enrollment (`settings.compliance.fips == REQUIRED`).\n\nMissing, inactive, and active-but-non-FIPS authenticators surface as distinct FAIL findings so the operator can act on the specific gap.",
+ "Risk": "Without FIPS-required enrollment, users can authenticate with devices whose cryptographic modules are not FIPS-validated.\n\n- **Regulatory exposure** under frameworks that mandate FIPS-validated cryptography\n- **Inconsistent assurance** across the user population\n- **Weak baseline** if the authenticator is active but the FIPS flag is `OPTIONAL` or unset",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/authenticator",
+ "https://help.okta.com/en-us/content/topics/mobile/ov-admin-config.htm",
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/authenticators/configure-okta-verify-options.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authenticators**.\n3. Activate the **Okta Verify** authenticator if it is not already `ACTIVE`.\n4. Open the authenticator's settings and set *FIPS Compliance* to **Users enrolling in Okta Verify can use FIPS compliant devices only**.\n5. Save the authenticator.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Ensure the **Okta Verify** authenticator is:\n- Present in the org (`key = okta_verify`)\n- In the `ACTIVE` status\n- Configured so *FIPS Compliance* is **Required** (`settings.compliance.fips == REQUIRED`)\n\nIf the organization does not require FIPS-validated authenticators, mute the check rather than disabling the FIPS toggle on a partial population.",
+ "Url": "https://hub.prowler.com/check/authenticator_okta_verify_fips_compliant"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273205 / OKTA-APP-001700."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.py b/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.py
new file mode 100644
index 0000000000..bf3c64b4b8
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_okta_verify_fips_compliant/authenticator_okta_verify_fips_compliant.py
@@ -0,0 +1,65 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.authenticator_helpers import (
+ find_authenticator_by_key,
+ missing_authenticator_resource,
+ missing_authenticators_scope_finding,
+)
+
+
+class authenticator_okta_verify_fips_compliant(Check):
+ """STIG V-273205 / OKTA-APP-001700.
+
+ The check requires Okta to restrict Okta Verify enrollment to FIPS-compliant devices.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate Okta Verify FIPS compliance settings."""
+ org_domain = authenticator_client.provider.identity.org_domain
+ missing_scope = authenticator_client.missing_scope.get("authenticators")
+ if missing_scope:
+ return [
+ missing_authenticators_scope_finding(
+ self.metadata(),
+ org_domain,
+ "okta_verify",
+ "Okta Verify authenticator",
+ missing_scope,
+ )
+ ]
+
+ authenticator = find_authenticator_by_key(
+ authenticator_client.authenticators, "okta_verify"
+ )
+ resource = authenticator or missing_authenticator_resource(
+ "okta_verify", "Okta Verify authenticator"
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=resource, org_domain=org_domain
+ )
+ if not authenticator:
+ report.status = "FAIL"
+ report.status_extended = "Okta Verify authenticator is missing."
+ elif authenticator.status.upper() != "ACTIVE":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Okta Verify authenticator is not active; current status is "
+ f"{authenticator.status}."
+ )
+ elif authenticator.fips.upper() == "REQUIRED":
+ report.status = "PASS"
+ report.status_extended = (
+ "Okta Verify authenticator requires FIPS-compliant devices "
+ "for enrollment."
+ )
+ else:
+ current_fips = authenticator.fips or "unset"
+ report.status = "FAIL"
+ report.status_extended = (
+ "Okta Verify authenticator is active but does not require "
+ "FIPS-compliant devices for enrollment (current value: "
+ f"{current_fips})."
+ )
+ return [report]
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.metadata.json
new file mode 100644
index 0000000000..f61ccef8a1
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_common_password_check",
+ "CheckTitle": "Every active Okta Password Policy rejects common passwords",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must reject passwords found in Okta's common-password dictionary (the *Restrict use of common passwords* setting).\n\nOkta evaluates Password Policies by group assignment; a custom policy with the check disabled can govern users. The check emits one finding per active policy.",
+ "Risk": "Without dictionary checking, users can pick passwords known to attackers from public breaches.\n\n- **Credential stuffing** succeeds with the same passwords compromised elsewhere\n- **Trivial guessing** stays viable for top-N lists (`123456`, `password`, …)\n- **Inconsistent baselines** leave users on legacy policies that allow common passwords",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and enable **Restrict use of common passwords**.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_dictionary_lookup = true # Critical: enables the common-password dictionary check\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Restrict use of common passwords* is **enabled**\n- Group assignments do not route users to legacy policies that leave the check disabled\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_common_password_check"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273208 / OKTA-APP-002980."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.py b/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.py
new file mode 100644
index 0000000000..d90d88afeb
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_common_password_check/authenticator_password_common_password_check.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_common_password_check(Check):
+ """STIG V-273208 / OKTA-APP-002980.
+
+ Every active Okta Password Policy must reject passwords found in the common-password dictionary.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "common-password dictionary checks"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.common_password_check is True:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(common password check enabled: {policy.common_password_check})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(common password check enabled: {policy.common_password_check})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.metadata.json
new file mode 100644
index 0000000000..42a74b6e71
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_complexity_lowercase",
+ "CheckTitle": "Every active Okta Password Policy requires at least one lowercase character",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require at least one **lowercase** character in the user's password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy that drops lowercase complexity can govern users even when the default policy is compliant. The check emits one finding per active policy so weaker custom policies do not hide behind a compliant default.",
+ "Risk": "Without lowercase complexity, the effective alphabet shrinks and passwords become easier to enumerate.\n\n- **Brute force** succeeds against a smaller character space\n- **Wordlist attacks** match more candidates without case mixing\n- **Inconsistent baselines** leave users on legacy policies with weaker complexity than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and enable **Lower case letter** under *Complexity*.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_lowercase = 1 # Critical: STIG-aligned complexity\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum number of lowercase characters* is `1` or more\n- Group assignments do not route users to legacy policies that disable lowercase complexity\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_complexity_lowercase"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273197 / OKTA-APP-000680."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.py
new file mode 100644
index 0000000000..e058e27b7b
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_lowercase/authenticator_password_complexity_lowercase.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_complexity_lowercase(Check):
+ """STIG V-273197 / OKTA-APP-000680.
+
+ Every active Okta Password Policy must require at least one lowercase character.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "at least one lowercase character"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_lower_case is not None and policy.min_lower_case >= 1:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum lowercase characters: {policy.min_lower_case})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum lowercase characters: {policy.min_lower_case})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.metadata.json
new file mode 100644
index 0000000000..fb3d4a920b
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_complexity_number",
+ "CheckTitle": "Every active Okta Password Policy requires at least one numeric character",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require at least one **numeric** character in the user's password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy that drops numeric complexity can govern users even when the default policy is compliant. The check emits one finding per active policy so weaker custom policies do not hide behind a compliant default.",
+ "Risk": "Without numeric complexity, the effective alphabet shrinks and dictionary words remain viable as passwords.\n\n- **Brute force** succeeds against a smaller character space\n- **Wordlist attacks** match plain dictionary words without numeric padding\n- **Inconsistent baselines** leave users on legacy policies with weaker complexity than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and enable **Number** under *Complexity*.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_number = 1 # Critical: STIG-aligned complexity\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum number of numeric characters* is `1` or more\n- Group assignments do not route users to legacy policies that disable numeric complexity\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_complexity_number"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273198 / OKTA-APP-000690."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.py
new file mode 100644
index 0000000000..78ffe6878e
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_number/authenticator_password_complexity_number.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_complexity_number(Check):
+ """STIG V-273198 / OKTA-APP-000690.
+
+ Every active Okta Password Policy must require at least one numeric character.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "at least one numeric character"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_number is not None and policy.min_number >= 1:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum numeric characters: {policy.min_number})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum numeric characters: {policy.min_number})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.metadata.json
new file mode 100644
index 0000000000..1268780551
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_complexity_symbol",
+ "CheckTitle": "Every active Okta Password Policy requires at least one symbol character",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require at least one **symbol** character in the user's password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy that drops symbol complexity can govern users even when the default policy is compliant. The check emits one finding per active policy so weaker custom policies do not hide behind a compliant default.",
+ "Risk": "Without symbol complexity, the effective alphabet shrinks and passwords stay closer to natural-language phrases.\n\n- **Brute force** succeeds against a smaller character space\n- **Wordlist attacks** match dictionary words without symbol padding\n- **Inconsistent baselines** leave users on legacy policies with weaker complexity than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and enable **Symbol** under *Complexity*.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_symbol = 1 # Critical: STIG-aligned complexity\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum number of symbol characters* is `1` or more\n- Group assignments do not route users to legacy policies that disable symbol complexity\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_complexity_symbol"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273199 / OKTA-APP-000700."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.py
new file mode 100644
index 0000000000..208a0f51d3
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_symbol/authenticator_password_complexity_symbol.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_complexity_symbol(Check):
+ """STIG V-273199 / OKTA-APP-000700.
+
+ Every active Okta Password Policy must require at least one symbol character.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "at least one symbol character"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_symbol is not None and policy.min_symbol >= 1:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum symbol characters: {policy.min_symbol})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum symbol characters: {policy.min_symbol})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.metadata.json
new file mode 100644
index 0000000000..7e885364ae
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_complexity_uppercase",
+ "CheckTitle": "Every active Okta Password Policy requires at least one uppercase character",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require at least one **uppercase** character in the user's password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy that drops uppercase complexity can govern users even when the default policy is compliant. The check emits one finding per active policy so weaker custom policies do not hide behind a compliant default.",
+ "Risk": "Without uppercase complexity, the effective alphabet shrinks and passwords become easier to enumerate.\n\n- **Brute force** succeeds against a smaller character space\n- **Wordlist attacks** match more candidates without case mixing\n- **Inconsistent baselines** leave users on legacy policies with weaker complexity than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and enable **Upper case letter** under *Complexity*.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_uppercase = 1 # Critical: STIG-aligned complexity\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum number of uppercase characters* is `1` or more\n- Group assignments do not route users to legacy policies that disable uppercase complexity\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_complexity_uppercase"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273196 / OKTA-APP-000670."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.py b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.py
new file mode 100644
index 0000000000..1419027980
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_complexity_uppercase/authenticator_password_complexity_uppercase.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_complexity_uppercase(Check):
+ """STIG V-273196 / OKTA-APP-000670.
+
+ Every active Okta Password Policy must require at least one uppercase character.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "at least one uppercase character"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_upper_case is not None and policy.min_upper_case >= 1:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum uppercase characters: {policy.min_upper_case})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum uppercase characters: {policy.min_upper_case})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_history_5/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_history_5/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.metadata.json
new file mode 100644
index 0000000000..a7191b0364
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_history_5",
+ "CheckTitle": "Every active Okta Password Policy remembers at least 5 previous passwords",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must keep at least the last `5` passwords in history so users cannot immediately recycle a recently-used password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy that lowers the history depth can govern users even when the default policy is compliant. The check emits one finding per active policy.",
+ "Risk": "A short password history lets users cycle back to compromised or trivially-guessable values shortly after a forced rotation.\n\n- **Reuse of breached passwords** within the same account\n- **Defeats forced rotation** by letting users return to a previous password\n- **Inconsistent baselines** leave users on legacy policies with shorter history than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and set *Enforce password history for last* to `5` passwords or more.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_history_count = 5 # Critical: STIG-aligned history depth\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Enforce password history for last* is `5` passwords or more\n- Group assignments do not route users to legacy policies with shorter history\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_history_5"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273209 / OKTA-APP-003010."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.py b/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.py
new file mode 100644
index 0000000000..b2eb6d16ba
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_history_5/authenticator_password_history_5.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_history_5(Check):
+ """STIG V-273209 / OKTA-APP-003010.
+
+ Every active Okta Password Policy must remember at least the last 5 previous passwords.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "password history of at least 5 previous passwords"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.history_count is not None and policy.history_count >= 5:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(password history count: {policy.history_count})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(password history count: {policy.history_count})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.metadata.json
new file mode 100644
index 0000000000..e287ed38f3
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_lockout_threshold_3",
+ "CheckTitle": "Every active Okta Password Policy locks accounts after 3 or fewer failed attempts",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must lock the account after at most `3` consecutive failed sign-in attempts.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy with a higher threshold (or no lockout) can govern users even when the default is compliant. The check emits one finding per active policy.",
+ "Risk": "A high lockout threshold (or no threshold) leaves accounts exposed to online password guessing.\n\n- **Online brute force** retains enough attempts to enumerate common passwords\n- **Credential stuffing** can iterate through breached credentials at scale\n- **Inconsistent baselines** leave users on legacy policies with weaker thresholds than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and set *Lock out user after X unsuccessful attempts* to `3` or fewer.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_max_lockout_attempts = 3 # Critical: STIG-aligned lockout threshold\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Lock out user after X unsuccessful attempts* is `3` or fewer\n- Group assignments do not route users to legacy policies with higher thresholds or no lockout\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_lockout_threshold_3"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273189 / OKTA-APP-000170. Not applicable when Okta delegates password sourcing to an external directory (AD/LDAP) — mute the check in that case; the directory enforces lockout instead."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.py b/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.py
new file mode 100644
index 0000000000..8026725c8a
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_lockout_threshold_3/authenticator_password_lockout_threshold_3.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_lockout_threshold_3(Check):
+ """STIG V-273189 / OKTA-APP-000170.
+
+ Every active Okta Password Policy must lock accounts after no more than 3 consecutive failed login attempts.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "password lockout after 3 or fewer failed attempts"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.max_attempts is not None and policy.max_attempts <= 3:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(maximum failed attempts: {policy.max_attempts})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(maximum failed attempts: {policy.max_attempts})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.metadata.json
new file mode 100644
index 0000000000..449904303e
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_maximum_age_60d",
+ "CheckTitle": "Every active Okta Password Policy enforces a maximum password age of 60 days or less",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require users to change their password at least every `60` days. The check rejects both unlimited expiration (`0`, which Okta treats as *never expires*) and any value greater than `60`.\n\nOkta evaluates Password Policies by group assignment; a permissive custom policy with a longer window can govern users. The check emits one finding per active policy.",
+ "Risk": "Long-lived passwords give a compromised credential indefinite usefulness.\n\n- **Stolen passwords** stay valid until the user happens to change them\n- **Breach detection lag** means a leaked password can be in use for months unnoticed\n- **No expiration** is the same risk as an infinite expiration window",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and set *Enforce password expiration* to `60` days or less. Do **not** leave it disabled or set to `0` — that disables expiration entirely.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_max_age_days = 60 # Critical: STIG-aligned maximum age; do not use 0 (disables expiration)\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Enforce password expiration* is `60` days or less\n- Never set the value to `0`, which disables expiration\n- Group assignments do not route users to legacy policies with longer windows or disabled expiration\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_maximum_age_60d"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273201 / OKTA-APP-000745."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.py b/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.py
new file mode 100644
index 0000000000..2dbc5d9c07
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_maximum_age_60d/authenticator_password_maximum_age_60d.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_maximum_age_60d(Check):
+ """STIG V-273201 / OKTA-APP-000745.
+
+ Every active Okta Password Policy must enforce a 60-day maximum password age.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "maximum password age of 60 days or less"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.max_age_days is not None and 0 < policy.max_age_days <= 60:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(maximum age days: {policy.max_age_days})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(maximum age days: {policy.max_age_days})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.metadata.json
new file mode 100644
index 0000000000..8adbf3b5a0
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_minimum_age_24h",
+ "CheckTitle": "Every active Okta Password Policy enforces a minimum password age of 24 hours",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "low",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must prevent users from changing their password again for at least `24` hours (`1440` minutes) after the previous change.\n\nA minimum age stops users from cycling through their entire history in one session to land back on a previously-known password. The check emits one finding per active policy.",
+ "Risk": "Without a minimum password age, users can sidestep history and rotation requirements in minutes.\n\n- **Defeats password history** by walking through new passwords back to a previous one\n- **Defeats forced rotation** by returning to the prior password after the mandatory change\n- **Inconsistent baselines** leave users on legacy policies with shorter minimums than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and set *Minimum password age* to `24` hours (`1440` minutes) or more.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_age_minutes = 1440 # Critical: STIG-aligned 24h minimum age\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum password age* is `1440` minutes (`24` hours) or more\n- Group assignments do not route users to legacy policies with shorter minimums or no minimum age\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_minimum_age_24h"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273200 / OKTA-APP-000740."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.py b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.py
new file mode 100644
index 0000000000..93ce511458
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_age_24h/authenticator_password_minimum_age_24h.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_minimum_age_24h(Check):
+ """STIG V-273200 / OKTA-APP-000740.
+
+ Every active Okta Password Policy must enforce a 24-hour minimum password age.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "minimum password age of at least 24 hours"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_age_minutes is not None and policy.min_age_minutes >= 1440:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum age minutes: {policy.min_age_minutes})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum age minutes: {policy.min_age_minutes})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.metadata.json
new file mode 100644
index 0000000000..d7409c6bb1
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_password_minimum_length_15",
+ "CheckTitle": "Every active Okta Password Policy enforces a minimum length of 15 characters",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every **active Okta Password Policy** must require at least `15` characters in the user's password.\n\nOkta evaluates Password Policies by group assignment, so a permissive custom policy with a shorter minimum length can govern users even when the default policy is compliant. The check emits one finding per active policy so weaker custom policies do not hide behind a compliant default.",
+ "Risk": "Short password minimums weaken brute-force and credential-stuffing resistance for every user assigned to the affected policy.\n\n- **Brute force** completes in feasible time against short passwords\n- **Credential stuffing** succeeds with reused passwords from public breaches\n- **Inconsistent baselines** leave users on legacy policies with weaker assurance than the default",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/policy",
+ "https://help.okta.com/en-us/content/topics/security/policies/configure-password-policies.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authentication** > **Password**.\n3. For every active policy, click **Edit** and set *Minimum password length* to `15` or more.\n4. Save the policy.\n5. Repeat for every active Password Policy returned by the check.",
+ "Terraform": "```hcl\nresource \"okta_policy_password\" \"<example_resource_name>\" {\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n password_min_length = 15 # Critical: STIG-aligned minimum\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure every active **Okta Password Policy** so:\n- *Minimum password length* is `15` characters or more\n- Group assignments do not route users to legacy policies with shorter minimums\n\nReview each active Password Policy individually — the check evaluates them one at a time.",
+ "Url": "https://hub.prowler.com/check/authenticator_password_minimum_length_15"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273195 / OKTA-APP-000650."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.py b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.py
new file mode 100644
index 0000000000..35e0a02b8b
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_password_minimum_length_15/authenticator_password_minimum_length_15.py
@@ -0,0 +1,60 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.password_policy_helpers import (
+ active_password_policies,
+ missing_password_policies_scope_finding,
+ no_active_password_policies_finding,
+ password_policy_label,
+)
+
+
+class authenticator_password_minimum_length_15(Check):
+ """STIG V-273195 / OKTA-APP-000650.
+
+ Every active Okta Password Policy must enforce a minimum password length of 15 characters.
+ The check emits one finding per active policy so a weaker
+ custom policy cannot hide behind a compliant default.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate all active Okta Password Policies."""
+ findings = []
+ org_domain = authenticator_client.provider.identity.org_domain
+ requirement = "minimum password length of at least 15 characters"
+ missing_scope = authenticator_client.missing_scope.get("password_policies")
+
+ if missing_scope:
+ return [
+ missing_password_policies_scope_finding(
+ self.metadata(), org_domain, missing_scope, requirement
+ )
+ ]
+
+ policies = active_password_policies(authenticator_client.password_policies)
+ if not policies:
+ return [
+ no_active_password_policies_finding(
+ self.metadata(), org_domain, requirement
+ )
+ ]
+
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ if policy.min_length is not None and policy.min_length >= 15:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{password_policy_label(policy)} enforces {requirement} "
+ f"(minimum length: {policy.min_length})."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{password_policy_label(policy)} does not enforce {requirement} "
+ f"(minimum length: {policy.min_length})."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/authenticator/authenticator_service.py b/prowler/providers/okta/services/authenticator/authenticator_service.py
new file mode 100644
index 0000000000..86b4084dfb
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_service.py
@@ -0,0 +1,236 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate as _paginate_shared
+from prowler.providers.okta.lib.service.service import OktaService
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "password_policies": "okta.policies.read",
+ "authenticators": "okta.authenticators.read",
+}
+
+
+def _value(value) -> str:
+ """Return plain string values from Okta SDK enums and raw strings."""
+ if value is None:
+ return ""
+ enum_value = getattr(value, "value", None)
+ if enum_value is not None:
+ return str(enum_value)
+ return str(value)
+
+
+def _int_or_none(value) -> Optional[int]:
+ if value is None:
+ return None
+ try:
+ return int(value)
+ except (TypeError, ValueError):
+ return None
+
+
+def _bool_or_none(value) -> Optional[bool]:
+ """Coerce common Okta boolean shapes into a real `Optional[bool]`.
+
+ The Okta SDK typed `bool` fields are already real booleans, but the
+ raw-JSON fallback paths in sibling services have surfaced both
+ JSON-style booleans (`true`/`false` as Python `bool` after `json.loads`)
+ and string-flavored ones (`"true"`/`"false"`). `bool("false")` is
+ `True` — so naive coercion silently flips the meaning. Reject that
+ explicitly.
+ """
+ if value is None:
+ return None
+ if isinstance(value, bool):
+ return value
+ if isinstance(value, str):
+ normalized = value.strip().lower()
+ if normalized in {"true", "1", "yes"}:
+ return True
+ if normalized in {"false", "0", "no", ""}:
+ return False
+ return None
+ return bool(value)
+
+
+class Authenticator(OktaService):
+ """Fetches Okta Password Policies and Authenticators for STIG checks.
+
+ Populates:
+ - `self.password_policies` — keyed by policy id. Each `PasswordPolicy`
+ carries the projected fields the 10 password-policy checks read
+ (length, complexity, age, history, lockout, common-password
+ dictionary). The complete typed SDK response is collapsed into a
+ flat dataclass so the checks never reach back into the SDK shape.
+ - `self.authenticators` — keyed by authenticator id. Used by the
+ two non-password checks (Smart Card IdP, Okta Verify FIPS).
+
+ Before each fetch the service compares its required OAuth scope
+ (see `REQUIRED_SCOPES`) against the access token's granted scopes
+ (`provider.identity.granted_scopes`). When a scope is known to be
+ missing, the fetch is skipped and recorded in `self.missing_scope`
+ so each check can emit an explicit MANUAL finding instead of a
+ misleading "no resources returned". Empty granted_scopes means
+ "unknown" — the service attempts the fetch and lets the SDK fail
+ loudly.
+ """
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+ self.password_policies: dict[str, PasswordPolicy] = (
+ {}
+ if self.missing_scope["password_policies"]
+ else self._list_password_policies()
+ )
+ self.authenticators: dict[str, OktaAuthenticator] = (
+ {} if self.missing_scope["authenticators"] else self._list_authenticators()
+ )
+
+ def _list_password_policies(self) -> dict[str, "PasswordPolicy"]:
+ """List PASSWORD policies with normalized password settings."""
+ logger.info("Authenticator - Listing Okta PASSWORD policies...")
+ try:
+ return self._run(self._fetch_password_policies())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_password_policies(self) -> dict[str, "PasswordPolicy"]:
+ result: dict[str, PasswordPolicy] = {}
+ items, err = await _paginate_shared(
+ lambda after: self.client.list_policies(
+ type="PASSWORD", after=after, limit="200"
+ )
+ )
+ if err is not None:
+ logger.error(f"Error listing PASSWORD policies: {err}")
+ return result
+
+ for policy in items:
+ policy_obj = self._build_password_policy(policy)
+ result[policy_obj.id] = policy_obj
+ return result
+
+ def _list_authenticators(self) -> dict[str, "OktaAuthenticator"]:
+ """List org authenticators with normalized settings."""
+ logger.info("Authenticator - Listing Okta authenticators...")
+ try:
+ return self._run(self._fetch_authenticators())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_authenticators(self) -> dict[str, "OktaAuthenticator"]:
+ # `list_authenticators` is non-paginated in the SDK (no `after`
+ # parameter); inline the tuple unwrap rather than going through
+ # `paginate`. Same shape `application_service` uses for
+ # `get_first_party_app_settings`.
+ result: dict[str, OktaAuthenticator] = {}
+ sdk_result = await self.client.list_authenticators()
+ err = sdk_result[-1]
+ if err is not None:
+ logger.error(f"Error listing authenticators: {err}")
+ return result
+ items = sdk_result[0] or []
+
+ for authenticator in items:
+ auth_obj = self._build_authenticator(authenticator)
+ result[auth_obj.id] = auth_obj
+ return result
+
+ @staticmethod
+ def _build_password_policy(policy) -> "PasswordPolicy":
+ settings = getattr(policy, "settings", None)
+ password_settings = getattr(settings, "password", None) if settings else None
+ lockout = (
+ getattr(password_settings, "lockout", None) if password_settings else None
+ )
+ complexity = (
+ getattr(password_settings, "complexity", None)
+ if password_settings
+ else None
+ )
+ dictionary = getattr(complexity, "dictionary", None) if complexity else None
+ common = getattr(dictionary, "common", None) if dictionary else None
+ age = getattr(password_settings, "age", None) if password_settings else None
+ policy_id = _value(getattr(policy, "id", None))
+ return PasswordPolicy(
+ id=policy_id,
+ name=_value(getattr(policy, "name", None)) or policy_id,
+ status=_value(getattr(policy, "status", None)),
+ priority=_int_or_none(getattr(policy, "priority", None)),
+ is_default=bool(getattr(policy, "system", False)),
+ max_attempts=_int_or_none(getattr(lockout, "max_attempts", None)),
+ min_length=_int_or_none(getattr(complexity, "min_length", None)),
+ min_upper_case=_int_or_none(getattr(complexity, "min_upper_case", None)),
+ min_lower_case=_int_or_none(getattr(complexity, "min_lower_case", None)),
+ min_number=_int_or_none(getattr(complexity, "min_number", None)),
+ min_symbol=_int_or_none(getattr(complexity, "min_symbol", None)),
+ min_age_minutes=_int_or_none(getattr(age, "min_age_minutes", None)),
+ max_age_days=_int_or_none(getattr(age, "max_age_days", None)),
+ history_count=_int_or_none(getattr(age, "history_count", None)),
+ common_password_check=_bool_or_none(getattr(common, "exclude", None)),
+ )
+
+ @staticmethod
+ def _build_authenticator(authenticator) -> "OktaAuthenticator":
+ settings = getattr(authenticator, "settings", None)
+ compliance = getattr(settings, "compliance", None) if settings else None
+ auth_id = _value(getattr(authenticator, "id", None))
+ return OktaAuthenticator(
+ id=auth_id,
+ key=_value(getattr(authenticator, "key", None)),
+ name=_value(getattr(authenticator, "name", None)) or auth_id,
+ status=_value(getattr(authenticator, "status", None)),
+ type=_value(getattr(authenticator, "type", None)),
+ fips=_value(getattr(compliance, "fips", None)),
+ )
+
+
+class PasswordPolicy(BaseModel):
+ """Normalized Okta Password Policy settings used by checks."""
+
+ id: str
+ name: str
+ status: str = ""
+ priority: Optional[int] = None
+ is_default: bool = False
+ max_attempts: Optional[int] = None
+ min_length: Optional[int] = None
+ min_upper_case: Optional[int] = None
+ min_lower_case: Optional[int] = None
+ min_number: Optional[int] = None
+ min_symbol: Optional[int] = None
+ min_age_minutes: Optional[int] = None
+ max_age_days: Optional[int] = None
+ history_count: Optional[int] = None
+ common_password_check: Optional[bool] = None
+
+
+class OktaAuthenticator(BaseModel):
+ """Normalized Okta Authenticator settings used by checks."""
+
+ id: str
+ key: str
+ name: str
+ status: str = ""
+ type: str = ""
+ fips: str = ""
+
+
+class AuthenticatorSummary(BaseModel):
+ """Synthetic resource for org-level authenticator findings."""
+
+ id: str
+ name: str
diff --git a/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/__init__.py b/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.metadata.json b/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.metadata.json
new file mode 100644
index 0000000000..b8e93ae548
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "authenticator_smart_card_active",
+ "CheckTitle": "Okta Smart Card IdP authenticator is configured and active",
+ "CheckType": [],
+ "ServiceName": "authenticator",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "The **Smart Card IdP authenticator** (`smart_card_idp`) must exist in the org and be in the `ACTIVE` status so certificate-based authentication is available to users and apps that require it.\n\nThe check resolves the authenticator by its built-in `key`. Missing and inactive authenticators surface as distinct FAIL findings.",
+ "Risk": "Without an active Smart Card authenticator, users cannot satisfy mandated certificate-based authentication and may be forced onto weaker fallback paths.\n\n- **Mandated CAC/PIV use** cannot be enforced\n- **Compliance gaps** for environments that require X.509 certificate authentication\n- **Fallback to password-only** sign-in for affected groups",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/authenticator",
+ "https://help.okta.com/oie/en-us/Content/Topics/identity-engine/authenticators/smart-card-authenticator.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Authenticators**.\n3. If the **Smart Card IdP** authenticator is not listed, click **Add Authenticator** and add it.\n4. Open the authenticator and switch its status to **ACTIVE**.\n5. Bind it to the Authentication Policies that require certificate-based auth.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Ensure the **Smart Card IdP** authenticator is:\n- Present in the org (`key = smart_card_idp`)\n- In the `ACTIVE` status\n- Referenced by every Authentication Policy that requires certificate-based authentication\n\nIf certificate-based authentication is not in scope for the organization, mute the check rather than disabling the authenticator.",
+ "Url": "https://hub.prowler.com/check/authenticator_smart_card_active"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273204 / OKTA-APP-001670."
+}
diff --git a/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.py b/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.py
new file mode 100644
index 0000000000..4341db8612
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/authenticator_smart_card_active/authenticator_smart_card_active.py
@@ -0,0 +1,56 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_client import (
+ authenticator_client,
+)
+from prowler.providers.okta.services.authenticator.lib.authenticator_helpers import (
+ find_authenticator_by_key,
+ missing_authenticator_resource,
+ missing_authenticators_scope_finding,
+)
+
+
+class authenticator_smart_card_active(Check):
+ """STIG V-273204 / OKTA-APP-001670.
+
+ The check requires Okta to configure and activate the Smart Card (PIV) authenticator.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate the Smart Card IdP authenticator status."""
+ org_domain = authenticator_client.provider.identity.org_domain
+ missing_scope = authenticator_client.missing_scope.get("authenticators")
+ if missing_scope:
+ return [
+ missing_authenticators_scope_finding(
+ self.metadata(),
+ org_domain,
+ "smart_card_idp",
+ "Smart Card IdP authenticator",
+ missing_scope,
+ )
+ ]
+
+ authenticator = find_authenticator_by_key(
+ authenticator_client.authenticators, "smart_card_idp"
+ )
+ resource = authenticator or missing_authenticator_resource(
+ "smart_card_idp", "Smart Card IdP authenticator"
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=resource, org_domain=org_domain
+ )
+ if authenticator and authenticator.status.upper() == "ACTIVE":
+ report.status = "PASS"
+ report.status_extended = "Smart Card IdP authenticator is ACTIVE."
+ elif authenticator:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Smart Card IdP authenticator is not active; current status is "
+ f"{authenticator.status}."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ "Smart Card IdP authenticator is not active or missing."
+ )
+ return [report]
diff --git a/prowler/providers/okta/services/authenticator/lib/__init__.py b/prowler/providers/okta/services/authenticator/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/authenticator/lib/authenticator_helpers.py b/prowler/providers/okta/services/authenticator/lib/authenticator_helpers.py
new file mode 100644
index 0000000000..851daec5a8
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/lib/authenticator_helpers.py
@@ -0,0 +1,49 @@
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_service import (
+ AuthenticatorSummary,
+ OktaAuthenticator,
+)
+
+_SCOPE_ADVICE = (
+ "Grant it on the Okta API Scopes tab of the service app in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def find_authenticator_by_key(
+ authenticators: dict[str, OktaAuthenticator], key: str
+) -> OktaAuthenticator | None:
+ """Return the first authenticator with the requested key.
+
+ Okta enforces unique authenticator `key` values per org for built-in
+ types (`okta_verify`, `smart_card_idp`, etc.), so the "first match"
+ is the only match in practice. If a future Okta release relaxes
+ that and returns duplicates, only the first is evaluated — STIG
+ semantics need refining at that point.
+ """
+ for authenticator in authenticators.values():
+ if authenticator.key == key:
+ return authenticator
+ return None
+
+
+def missing_authenticator_resource(key: str, name: str) -> AuthenticatorSummary:
+ """Build a synthetic resource for a missing authenticator."""
+ return AuthenticatorSummary(id=f"{key}-missing", name=name)
+
+
+def missing_authenticators_scope_finding(
+ metadata, org_domain: str, key: str, name: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when authenticators cannot be listed."""
+ resource = AuthenticatorSummary(id=f"{key}-scope-missing", name=name)
+ report = CheckReportOkta(
+ metadata=metadata, resource=resource, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Okta authenticators to evaluate {name}: the Okta "
+ f"service app is missing the required `{scope}` API scope. "
+ f"{_SCOPE_ADVICE}"
+ )
+ return report
diff --git a/prowler/providers/okta/services/authenticator/lib/password_policy_helpers.py b/prowler/providers/okta/services/authenticator/lib/password_policy_helpers.py
new file mode 100644
index 0000000000..08aa64a3a6
--- /dev/null
+++ b/prowler/providers/okta/services/authenticator/lib/password_policy_helpers.py
@@ -0,0 +1,80 @@
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.authenticator.authenticator_service import (
+ PasswordPolicy,
+)
+
+_SCOPE_ADVICE = (
+ "Grant it on the Okta API Scopes tab of the service app in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def active_password_policies(
+ password_policies: dict[str, PasswordPolicy],
+) -> list[PasswordPolicy]:
+ """Return active password policies sorted by priority.
+
+ Treats `policy.status == ""` as ACTIVE: the typed Okta SDK
+ occasionally returns policies without a `status` field populated
+ (the SDK enum doesn't cover every server-side value Okta has
+ shipped). Dropping those would silently hide real policies — we
+ 'd rather evaluate them and let the per-field comparator decide.
+ """
+ return sorted(
+ [
+ policy
+ for policy in password_policies.values()
+ if not policy.status or policy.status.upper() == "ACTIVE"
+ ],
+ key=lambda policy: (
+ policy.priority if policy.priority is not None else float("inf"),
+ policy.name,
+ ),
+ )
+
+
+def password_policy_label(policy: PasswordPolicy) -> str:
+ kind = "default" if policy.is_default else "custom"
+ priority = policy.priority if policy.priority is not None else "unset"
+ return f"Password Policy {policy.name} (priority {priority}, {kind})"
+
+
+def no_active_password_policies_finding(
+ metadata, org_domain: str, requirement: str
+) -> CheckReportOkta:
+ """Build the FAIL finding emitted when no active password policies exist."""
+ placeholder = PasswordPolicy(
+ id="password-policies-missing",
+ name="(no active password policies)",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ "No active Okta Password Policies were returned by the API. "
+ f"The organization must enforce: {requirement}."
+ )
+ return report
+
+
+def missing_password_policies_scope_finding(
+ metadata, org_domain: str, scope: str, requirement: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when Password Policies cannot be listed."""
+ placeholder = PasswordPolicy(
+ id="password-policies-scope-missing",
+ name="(scope not granted)",
+ status="UNKNOWN",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Okta Password Policies to evaluate {requirement}: "
+ f"the Okta service app is missing the required `{scope}` API scope. "
+ f"{_SCOPE_ADVICE}"
+ )
+ return report
diff --git a/prowler/providers/okta/services/idp/__init__.py b/prowler/providers/okta/services/idp/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/idp/idp_client.py b/prowler/providers/okta/services/idp/idp_client.py
new file mode 100644
index 0000000000..5bbf98c17a
--- /dev/null
+++ b/prowler/providers/okta/services/idp/idp_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.idp.idp_service import Idp
+
+idp_client = Idp(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/idp/idp_service.py b/prowler/providers/okta/services/idp/idp_service.py
new file mode 100644
index 0000000000..2ff106cb47
--- /dev/null
+++ b/prowler/providers/okta/services/idp/idp_service.py
@@ -0,0 +1,118 @@
+from typing import Optional
+
+from pydantic import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate
+from prowler.providers.okta.lib.service.service import OktaService
+
+# Okta's API value for the "Smart Card" IdP shown in the Admin Console.
+# The UI label is "Smart Card IdP" but the `type` field on the API response
+# is `X509` (Mutual TLS) — that is the value we filter on.
+SMART_CARD_IDP_TYPE = "X509"
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "identity_providers": "okta.idps.read",
+}
+
+
+class Idp(OktaService):
+ """Fetches Okta Identity Providers.
+
+ Populates `self.identity_providers` keyed by IdP id. Each entry
+ captures the minimum fields the bundled checks read: identity
+ (`id`, `name`), `type`, `status`, and — for `X509` Smart Card IdPs
+ — the certificate-chain `issuer` and `kid` exposed by Okta's
+ `protocol.credentials.trust` structure. Reading the issuer DN lets
+ the check surface it for out-of-band verification against the
+ DOD-approved CA list.
+
+ Required OAuth scopes (`REQUIRED_SCOPES`) are compared against the
+ access token's granted scopes (`provider.identity.granted_scopes`).
+ Missing scopes are recorded in `self.missing_scope` so the check
+ can emit an explicit MANUAL finding.
+ """
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+
+ self.identity_providers: dict[str, OktaIdentityProvider] = (
+ {}
+ if self.missing_scope["identity_providers"]
+ else self._list_identity_providers()
+ )
+
+ def _list_identity_providers(self) -> dict:
+ logger.info("Idp - Listing Okta Identity Providers...")
+ try:
+ return self._run(self._fetch_identity_providers())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_identity_providers(self) -> dict:
+ result: dict[str, OktaIdentityProvider] = {}
+ all_idps, err = await paginate(
+ lambda after: self.client.list_identity_providers(after=after)
+ )
+ if err is not None:
+ logger.error(f"Error listing identity providers: {err}")
+ return result
+
+ for idp in all_idps:
+ idp_id = getattr(idp, "id", "") or ""
+ if not idp_id:
+ continue
+ issuer, kid = _trust_fields(idp)
+ result[idp_id] = OktaIdentityProvider(
+ id=idp_id,
+ name=getattr(idp, "name", "") or "",
+ type=_stringify_enum(getattr(idp, "type", None)) or "",
+ status=_stringify_enum(getattr(idp, "status", None)) or "",
+ trust_issuer=issuer,
+ trust_kid=kid,
+ )
+ return result
+
+
+def _trust_fields(idp) -> tuple[Optional[str], Optional[str]]:
+ """Extract `issuer` and `kid` from an `X509` IdP's protocol.credentials.trust.
+
+ The SDK exposes `IdentityProvider.protocol` as `IdentityProviderProtocol`,
+ a Pydantic v2 oneOf wrapper that holds the concrete protocol (ProtocolMtls
+ for X509 IdPs) on `actual_instance`. `credentials` is not proxied on the
+ wrapper, so reading it directly returns None — we have to unwrap first.
+ """
+ protocol = getattr(idp, "protocol", None)
+ if protocol is None:
+ return None, None
+ actual_protocol = getattr(protocol, "actual_instance", None) or protocol
+ credentials = getattr(actual_protocol, "credentials", None)
+ if credentials is None:
+ return None, None
+ trust = getattr(credentials, "trust", None)
+ if trust is None:
+ return None, None
+ return getattr(trust, "issuer", None), getattr(trust, "kid", None)
+
+
+def _stringify_enum(value) -> Optional[str]:
+ if value is None:
+ return None
+ return getattr(value, "value", None) or str(value)
+
+
+class OktaIdentityProvider(BaseModel):
+ id: str
+ name: str = ""
+ type: str = ""
+ status: str = ""
+ trust_issuer: Optional[str] = None
+ trust_kid: Optional[str] = None
diff --git a/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/__init__.py b/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.metadata.json b/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.metadata.json
new file mode 100644
index 0000000000..e7e85294be
--- /dev/null
+++ b/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "idp_smart_card_dod_approved_ca",
+ "CheckTitle": "Okta Smart Card (X509) Identity Provider uses a DOD-approved certificate authority",
+ "CheckType": [],
+ "ServiceName": "idp",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "Every Okta Smart Card (X509) Identity Provider must be `ACTIVE` and its certificate chain must be issued by a DOD-approved CA. The check ships default issuer-DN patterns covering DOD PKI and ECA, and matches them against the chain's `issuer`. Override or extend via `okta_dod_approved_ca_issuer_patterns` in the audit config to recognise tenant-specific DOD CAs.",
+ "Risk": "An Okta Smart Card IdP whose certificate chain is not issued by a DOD-approved CA can be used to authenticate non-vetted identities.\n\n- **Trust on an unverified CA** allows impersonation of CAC/PIV holders\n- **Bypass of the federal PKI** required for DOD-grade identity assurance\n- **Acceptance of certificates** from a private or unaccredited issuer",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/en-us/content/topics/security/idp-enable-smart-card.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Identity Providers**.\n3. For each IdP whose **Type** is **Smart Card**, click **Actions** > **Configure**.\n4. Under **Certificate chain**, verify the certificate is from a DOD-approved Certificate Authority (DOD PKI, ECA, JITC, or equivalent).\n5. If the IdP is not **Active**, activate it once the chain is validated.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Verify each Okta Smart Card (X509) Identity Provider is ACTIVE and its certificate chain is issued by a DOD-approved Certificate Authority. Document the issuer for audit evidence.",
+ "Url": "https://hub.prowler.com/check/idp_smart_card_dod_approved_ca"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273207 / OKTA-APP-001920."
+}
diff --git a/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.py b/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.py
new file mode 100644
index 0000000000..5d19cca0dd
--- /dev/null
+++ b/prowler/providers/okta/services/idp/idp_smart_card_dod_approved_ca/idp_smart_card_dod_approved_ca.py
@@ -0,0 +1,148 @@
+import re
+
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.idp.idp_client import idp_client
+from prowler.providers.okta.services.idp.idp_service import (
+ SMART_CARD_IDP_TYPE,
+ OktaIdentityProvider,
+)
+from prowler.providers.okta.services.idp.lib.idp_helpers import (
+ missing_idps_scope_finding,
+)
+
+# Default issuer-DN substring patterns recognised as DOD-approved Certificate
+# Authorities. The DOD PKI publishes canonical DN forms that include
+# `O=U.S. Government, OU=DoD` (for DoD Root, DoD ID, DoD EMAIL, DoD SW, DoD
+# JITC CAs) and `O=U.S. Government, OU=ECA` for the External Certificate
+# Authorities. Customers running an internal CA outside these patterns can
+# extend the list via the `okta_dod_approved_ca_issuer_patterns` audit-config
+# entry — see the per-check Notes in metadata.json.
+DEFAULT_DOD_CA_ISSUER_PATTERNS = (
+ # `OU=DoD` is the distinctive DISA DN component for every CA in the DoD
+ # PKI (Root, ID, EMAIL, SW, JITC). `OU=ECA` is the equivalent for the
+ # External Certificate Authorities. The trailing `\b` prevents accidental
+ # matches against superstrings like `OU=DoDExtra`.
+ r"\bOU=DoD\b",
+ r"\bOU=ECA\b",
+)
+
+
+class idp_smart_card_dod_approved_ca(Check):
+ """Verifies that Okta Smart Card (X509) IdPs are configured and use a DOD-approved CA.
+
+ PASS when the IdP is `ACTIVE` and its certificate chain's `issuer`
+ DN matches one of the configured DOD-approved CA patterns. MANUAL
+ when active but the issuer doesn't match (operator can verify
+ out-of-band or extend the pattern list). FAIL when no Smart Card
+ IdP is configured or when the configured IdP is inactive.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = idp_client.provider.identity.org_domain
+ audit_config = idp_client.audit_config or {}
+ configured_patterns = audit_config.get("okta_dod_approved_ca_issuer_patterns")
+ patterns = (
+ tuple(configured_patterns)
+ if configured_patterns
+ else DEFAULT_DOD_CA_ISSUER_PATTERNS
+ )
+
+ missing_scope = idp_client.missing_scope.get("identity_providers")
+ if missing_scope:
+ findings.append(
+ missing_idps_scope_finding(self.metadata(), org_domain, missing_scope)
+ )
+ return findings
+
+ smart_card_idps = [
+ idp
+ for idp in idp_client.identity_providers.values()
+ if (idp.type or "").upper() == SMART_CARD_IDP_TYPE
+ ]
+
+ if not smart_card_idps:
+ placeholder = OktaIdentityProvider(
+ id="okta-smart-card-idp-missing",
+ name="(no Smart Card IdP configured)",
+ type=SMART_CARD_IDP_TYPE,
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=placeholder, org_domain=org_domain
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ "No Smart Card (X509) Identity Providers are configured. "
+ "Configure a Smart Card IdP in the Admin Console "
+ "(Security > Identity Providers) with a certificate chain "
+ "issued by a DOD-approved CA. If CAC/PIV authentication is "
+ "not required for this tenant, mutelist this check with "
+ "that documented exception."
+ )
+ findings.append(report)
+ return findings
+
+ for idp in smart_card_idps:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=idp, org_domain=org_domain
+ )
+ label = f"Okta Smart Card IdP '{idp.name}' (id={idp.id}, type={idp.type})"
+ chain_detail = _format_chain_detail(idp)
+
+ if (idp.status or "").upper() != "ACTIVE":
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{label} is not ACTIVE (status={idp.status or 'unset'}). "
+ "Activate the IdP from Security > Identity Providers, then "
+ f"verify the certificate chain. {chain_detail}"
+ )
+ findings.append(report)
+ continue
+
+ matched_pattern = _matched_issuer_pattern(idp.trust_issuer, patterns)
+ if matched_pattern is not None:
+ report.status = "PASS"
+ report.status_extended = (
+ f"{label} is ACTIVE and its chain issuer matches a "
+ f"DOD-approved CA pattern (`{matched_pattern}`). "
+ f"{chain_detail}"
+ )
+ else:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"{label} is ACTIVE but its chain issuer does not match any "
+ "configured DOD-approved CA pattern. Verify out-of-band "
+ "that the certificate chain belongs to a DOD-approved "
+ "Certificate Authority, or extend "
+ "`okta_dod_approved_ca_issuer_patterns` in the audit "
+ f"config. {chain_detail}"
+ )
+ findings.append(report)
+ return findings
+
+
+def _matched_issuer_pattern(issuer, patterns):
+ if not issuer:
+ return None
+ for pattern in patterns:
+ try:
+ if re.search(pattern, issuer):
+ return pattern
+ except re.error:
+ # Skip malformed operator-supplied patterns rather than crashing
+ # the whole check.
+ continue
+ return None
+
+
+def _format_chain_detail(idp: OktaIdentityProvider) -> str:
+ if idp.trust_issuer or idp.trust_kid:
+ return (
+ f"Chain issuer: {idp.trust_issuer or 'unset'}; "
+ f"kid: {idp.trust_kid or 'unset'}."
+ )
+ return (
+ "Chain issuer and kid were not exposed by the API; inspect the IdP in "
+ "the Admin Console under Security > Identity Providers > Configure."
+ )
diff --git a/prowler/providers/okta/services/idp/lib/__init__.py b/prowler/providers/okta/services/idp/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/idp/lib/idp_helpers.py b/prowler/providers/okta/services/idp/lib/idp_helpers.py
new file mode 100644
index 0000000000..f1689f34a1
--- /dev/null
+++ b/prowler/providers/okta/services/idp/lib/idp_helpers.py
@@ -0,0 +1,26 @@
+"""Shared helpers for the OKTA idp STIG checks."""
+
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.idp.idp_service import OktaIdentityProvider
+
+
+def missing_idps_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding when the IdPs scope is not granted."""
+ placeholder = OktaIdentityProvider(
+ id="okta-idps-scope-missing",
+ name="(scope not granted)",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Could not retrieve Okta Identity Providers: the Okta service app is "
+ f"missing the required `{scope}` API scope. Grant it on the service "
+ "app's Okta API Scopes tab in the Okta Admin Console, then re-run the "
+ "check."
+ )
+ return report
diff --git a/prowler/providers/okta/services/network/__init__.py b/prowler/providers/okta/services/network/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/network/lib/__init__.py b/prowler/providers/okta/services/network/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/network/lib/network_zone_helpers.py b/prowler/providers/okta/services/network/lib/network_zone_helpers.py
new file mode 100644
index 0000000000..bcd906b01a
--- /dev/null
+++ b/prowler/providers/okta/services/network/lib/network_zone_helpers.py
@@ -0,0 +1,88 @@
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.network.network_zone_service import (
+ NetworkZoneSummary,
+ OktaNetworkZone,
+)
+
+ANONYMIZER_CATEGORY_MARKERS = (
+ "ANONYM",
+ "PROXY",
+ "TOR",
+ "VPN",
+)
+
+
+def active_blocklist_zones(
+ network_zones: dict[str, OktaNetworkZone],
+) -> list[OktaNetworkZone]:
+ """Return active Network Zones configured for blocklist usage."""
+ return sorted(
+ [
+ zone
+ for zone in network_zones.values()
+ if zone.status.upper() == "ACTIVE" and zone.usage.upper() == "BLOCKLIST"
+ ],
+ key=lambda zone: (zone.name, zone.id),
+ )
+
+
+def is_ip_blocklist_with_entries(zone: OktaNetworkZone) -> bool:
+ """Return True when an IP blocklist zone contains gateway/proxy entries."""
+ return zone.type.upper() == "IP" and bool(zone.gateways or zone.proxies)
+
+
+def is_enhanced_dynamic_anonymizer_blocklist(zone: OktaNetworkZone) -> bool:
+ """Return True for active Enhanced Dynamic blocklists covering anonymizers."""
+ if zone.type.upper() != "DYNAMIC_V2":
+ return False
+ categories = [category.upper() for category in zone.ip_service_categories]
+ return any(
+ marker in category
+ for category in categories
+ for marker in ANONYMIZER_CATEGORY_MARKERS
+ )
+
+
+def compliant_anonymized_proxy_blocklist(
+ network_zones: dict[str, OktaNetworkZone],
+) -> tuple[OktaNetworkZone | None, str]:
+ """Find the Network Zone that satisfies anonymized-proxy blocklisting."""
+ for zone in active_blocklist_zones(network_zones):
+ if is_enhanced_dynamic_anonymizer_blocklist(zone):
+ return zone, "active Enhanced Dynamic Zone blocklist for anonymizers"
+ return None, ""
+
+
+def static_ip_blocklist_evidence(
+ network_zones: dict[str, OktaNetworkZone],
+) -> OktaNetworkZone | None:
+ """Return static IP blocklist evidence that requires human validation."""
+ for zone in active_blocklist_zones(network_zones):
+ if is_ip_blocklist_with_entries(zone):
+ return zone
+ return None
+
+
+_SCOPE_ADVICE = (
+ "Grant it on the Okta API Scopes tab of the service app in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def missing_network_zone_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding emitted when Network Zones cannot be listed."""
+ resource = NetworkZoneSummary(
+ id="network-zones-scope-missing",
+ name="(scope not granted)",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=resource, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Okta Network Zones: the Okta service app "
+ f"is missing the required `{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
diff --git a/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/__init__.py b/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.metadata.json b/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.metadata.json
new file mode 100644
index 0000000000..d2a4791c17
--- /dev/null
+++ b/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "network_zone_block_anonymized_proxies",
+ "CheckTitle": "Okta uses active Network Zone blocklists for anonymized proxy sources",
+ "CheckType": [],
+ "ServiceName": "network",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "**Okta Network Zone blocklists** should block anonymized proxy access before authentication. Enhanced Dynamic Zone anonymizer categories provide direct coverage; static IP blocklists show gateway/proxy blocking but cannot prove full anonymizer-provider coverage.",
+ "Risk": "**Anonymized proxy access** lets attackers hide source networks while attempting credential attacks, session establishment, or policy bypass from untrusted infrastructure.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tags/networkzone",
+ "https://help.okta.com/en-us/content/topics/security/network/about-enhanced-dynamic-zones.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "Security > Networks: configure BlockedIpZone gateway/proxy IP entries or activate DefaultEnhancedDynamicZone / Enhanced Dynamic Zone blocklisting for anonymizers.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Prefer an active Enhanced Dynamic Zone blocklist** for anonymizers. If you use a static IP Network Zone blocklist, keep gateway/proxy entries actively maintained because Prowler cannot prove full anonymizer-provider coverage from static entries alone.",
+ "Url": "https://hub.prowler.com/check/network_zone_block_anonymized_proxies"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.py b/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.py
new file mode 100644
index 0000000000..3da973b415
--- /dev/null
+++ b/prowler/providers/okta/services/network/network_zone_block_anonymized_proxies/network_zone_block_anonymized_proxies.py
@@ -0,0 +1,77 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.network.lib.network_zone_helpers import (
+ compliant_anonymized_proxy_blocklist,
+ missing_network_zone_scope_finding,
+ static_ip_blocklist_evidence,
+)
+from prowler.providers.okta.services.network.network_zone_client import (
+ network_zone_client,
+)
+from prowler.providers.okta.services.network.network_zone_service import (
+ NetworkZoneSummary,
+)
+
+
+class network_zone_block_anonymized_proxies(Check):
+ """Ensure Okta actively blocks anonymized proxy sources before auth."""
+
+ def execute(self) -> list[CheckReportOkta]:
+ """Evaluate whether an active blocklist covers anonymized proxies."""
+ org_domain = network_zone_client.provider.identity.org_domain
+ missing_scope = network_zone_client.missing_scope.get("network_zones")
+ if missing_scope:
+ return [
+ missing_network_zone_scope_finding(
+ self.metadata(), org_domain, missing_scope
+ )
+ ]
+
+ retrieval_error = getattr(network_zone_client, "retrieval_error", None)
+ if retrieval_error:
+ resource = NetworkZoneSummary(
+ id="network-zones-retrieval-error",
+ name="(retrieval failed)",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=resource, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Okta Network Zones could not be retrieved or validated. "
+ f"Reason: {retrieval_error}"
+ )
+ return [report]
+
+ matching_zone, reason = compliant_anonymized_proxy_blocklist(
+ network_zone_client.network_zones
+ )
+ manual_zone = (
+ None
+ if matching_zone
+ else static_ip_blocklist_evidence(network_zone_client.network_zones)
+ )
+
+ resource = matching_zone or manual_zone or NetworkZoneSummary()
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=resource, org_domain=org_domain
+ )
+ if matching_zone:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Okta Network Zone {matching_zone.name} is an {reason}."
+ )
+ elif manual_zone:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Okta Network Zone {manual_zone.name} is an active manual IP "
+ "blocklist with gateway or proxy IP entries; Prowler cannot "
+ "verify full anonymizer coverage for static entries."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ "No active Okta Network Zone blocklist was found that blocks "
+ "anonymized proxies. Existing zones do not actively block gateway "
+ "or proxy IPs, nor an Enhanced Dynamic Zone anonymizer category."
+ )
+ return [report]
diff --git a/prowler/providers/okta/services/network/network_zone_client.py b/prowler/providers/okta/services/network/network_zone_client.py
new file mode 100644
index 0000000000..6d4f603f80
--- /dev/null
+++ b/prowler/providers/okta/services/network/network_zone_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.network.network_zone_service import NetworkZone
+
+network_zone_client = NetworkZone(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/network/network_zone_service.py b/prowler/providers/okta/services/network/network_zone_service.py
new file mode 100644
index 0000000000..550c9b0d49
--- /dev/null
+++ b/prowler/providers/okta/services/network/network_zone_service.py
@@ -0,0 +1,234 @@
+from typing import Optional
+
+from pydantic import BaseModel, Field, ValidationError
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate as _paginate_shared
+from prowler.providers.okta.lib.service.raw_fetch import (
+ get_json_paginated as _raw_get_json_paginated,
+)
+from prowler.providers.okta.lib.service.service import OktaService
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "network_zones": "okta.networkZones.read",
+}
+
+
+def _value(value) -> str:
+ """Return plain string values from Okta SDK enums and raw strings."""
+ if value is None:
+ return ""
+ enum_value = getattr(value, "value", None)
+ if enum_value is not None:
+ return str(enum_value)
+ return str(value)
+
+
+class NetworkZone(OktaService):
+ """Fetches Okta Network Zones for STIG network-zone checks."""
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+ self.retrieval_error: str | None = None
+ self.network_zones: dict[str, OktaNetworkZone] = (
+ {} if self.missing_scope["network_zones"] else self._list_network_zones()
+ )
+
+ def _set_retrieval_error(self, message: str) -> None:
+ self.retrieval_error = message
+ logger.error(message)
+
+ def _list_network_zones(self) -> dict[str, "OktaNetworkZone"]:
+ """List all Network Zones visible to the configured Okta service app."""
+ logger.info("NetworkZone - Listing Okta Network Zones...")
+ try:
+ return self._run(self._fetch_all())
+ except Exception as error:
+ line_number = getattr(error.__traceback__, "tb_lineno", "unknown")
+ self._set_retrieval_error(
+ f"{error.__class__.__name__}[{line_number}]: {error}"
+ )
+ return {}
+
+ async def _fetch_all(self) -> dict[str, "OktaNetworkZone"]:
+ result: dict[str, OktaNetworkZone] = {}
+ try:
+ all_zones, err = await _paginate_shared(
+ lambda after: self.client.list_network_zones(after=after, limit=200)
+ )
+ except (ValueError, ValidationError) as ex:
+ # Upstream Okta SDK ↔ Management API schema drift: the SDK
+ # generates `EnhancedDynamicNetworkZoneAllOfAsnsInclude` as an
+ # object-shaped pydantic model, but the API returns
+ # `asns.include` as a JSON array (typically `[]`), so pydantic
+ # rejects the whole zone with `model_type` errors. Fall back
+ # to a raw-JSON fetch so STIG evaluation isn't blocked by an
+ # upstream SDK bug. Same workaround shape as
+ # `application_service._fetch_access_policy_raw`. The wider
+ # `(ValueError, ValidationError)` catch matches the
+ # `user_service` precedent — the SDK raises either depending
+ # on whether the failure is a discriminator miss or a model
+ # mismatch.
+ logger.warning(
+ f"Okta SDK raised {type(ex).__name__} parsing Network Zones — "
+ "falling back to raw-JSON parse. This is an okta-sdk-python "
+ "deserialization bug; the workaround should be removed once "
+ "upstream fixes it."
+ )
+ return await self._fetch_all_raw()
+ if err is not None:
+ self._set_retrieval_error(f"Error listing Network Zones: {err}")
+ return result
+
+ for zone in all_zones:
+ zone_obj = self._build_zone(zone)
+ result[zone_obj.id] = zone_obj
+ return result
+
+ async def _fetch_all_raw(self) -> dict[str, "OktaNetworkZone"]:
+ """Raw-JSON fallback for `list_network_zones`.
+
+ Bypasses the SDK's typed deserialization via the shared
+ `get_json_paginated` helper, then projects each zone onto our
+ own pydantic snapshot — which only validates the fields the
+ STIG checks actually read.
+ """
+ result: dict[str, OktaNetworkZone] = {}
+ zones_data = await _raw_get_json_paginated(
+ self.client,
+ "/api/v1/zones",
+ page_size=200,
+ context="Network Zones",
+ )
+ if zones_data is None:
+ self._set_retrieval_error(
+ "Raw Network Zones fetch failed; see logs for details."
+ )
+ return result
+ for zone_dict in zones_data:
+ if not isinstance(zone_dict, dict):
+ continue
+ zone_obj = _raw_zone_to_model(zone_dict)
+ result[zone_obj.id] = zone_obj
+ return result
+
+ @staticmethod
+ def _build_zone(zone) -> "OktaNetworkZone":
+ zone_id = _value(getattr(zone, "id", None))
+ return OktaNetworkZone(
+ id=zone_id,
+ name=_value(getattr(zone, "name", None)) or zone_id,
+ status=_value(getattr(zone, "status", None)),
+ type=_value(getattr(zone, "type", None)),
+ usage=_value(getattr(zone, "usage", None)),
+ system=bool(getattr(zone, "system", False)),
+ gateways=_address_values(getattr(zone, "gateways", None)),
+ proxies=_address_values(getattr(zone, "proxies", None)),
+ asns=_condition_values(getattr(zone, "asns", None)),
+ locations=_condition_values(getattr(zone, "locations", None)),
+ ip_service_categories=_condition_values(
+ getattr(zone, "ip_service_categories", None)
+ ),
+ )
+
+
+def _raw_zone_to_model(zone_dict: dict) -> "OktaNetworkZone":
+ """Project a raw `/api/v1/zones` JSON zone onto our model.
+
+ Mirrors `NetworkZone._build_zone` but reads camelCase JSON keys
+ (`ipServiceCategories`) instead of the SDK's snake_case attributes.
+ Used by the raw-JSON fallback that activates when the Okta SDK's
+ strict pydantic validators reject zone payloads the Management API
+ returns (e.g. Enhanced Dynamic Zones with `asns.include: []`).
+ """
+ zone_id = str(zone_dict.get("id") or "")
+ categories = _condition_values(zone_dict.get("ipServiceCategories"))
+ # IP-typed zones return `gateways`/`proxies` as `[{type, value}]`
+ # arrays; Enhanced Dynamic Zones return `asns`/`locations` and
+ # `ipServiceCategories` as `{include, exclude}` objects. Keep the
+ # `list[str]` shape by extracting address values and included
+ # condition values from both SDK models and raw JSON.
+ return OktaNetworkZone(
+ id=zone_id,
+ name=str(zone_dict.get("name") or zone_id),
+ status=str(zone_dict.get("status") or ""),
+ type=str(zone_dict.get("type") or ""),
+ usage=str(zone_dict.get("usage") or ""),
+ system=bool(zone_dict.get("system", False)),
+ gateways=_address_values(zone_dict.get("gateways")),
+ proxies=_address_values(zone_dict.get("proxies")),
+ asns=_condition_values(zone_dict.get("asns")),
+ locations=_condition_values(zone_dict.get("locations")),
+ ip_service_categories=categories,
+ )
+
+
+def _address_values(raw) -> list[str]:
+ """Return string values from an Okta address-style JSON array.
+
+ Each entry in `gateways`/`proxies` is `{"type": ..., "value": ...}`;
+ `asns`/`locations` may be a `{include, exclude}` object on Enhanced
+ Dynamic Zones. Non-list inputs collapse to `[]` so the resulting
+ list satisfies the pydantic `list[str]` field.
+ """
+ if not isinstance(raw, list):
+ return []
+ out: list[str] = []
+ for entry in raw:
+ if isinstance(entry, dict):
+ value = entry.get("value")
+ elif entry is not None:
+ value = getattr(entry, "value", entry)
+ else:
+ value = None
+ if value is not None:
+ out.append(_value(value))
+ return out
+
+
+def _condition_values(raw) -> list[str]:
+ """Return string values from Okta include/exclude-style conditions."""
+ if raw is None:
+ return []
+ values = (
+ raw.get("include") if isinstance(raw, dict) else getattr(raw, "include", raw)
+ )
+ if values is None:
+ return []
+ if not isinstance(values, list):
+ values = [values]
+ normalized = []
+ for value in values:
+ if isinstance(value, dict):
+ value = value.get("value")
+ if value is not None:
+ normalized.append(_value(value))
+ return normalized
+
+
+class OktaNetworkZone(BaseModel):
+ """Normalized Okta Network Zone attributes used by checks."""
+
+ id: str
+ name: str
+ status: str = ""
+ type: str = ""
+ usage: str = ""
+ system: bool = False
+ gateways: list[str] = Field(default_factory=list)
+ proxies: list[str] = Field(default_factory=list)
+ asns: list[str] = Field(default_factory=list)
+ locations: list[str] = Field(default_factory=list)
+ ip_service_categories: list[str] = Field(default_factory=list)
+
+
+class NetworkZoneSummary(BaseModel):
+ """Synthetic resource for org-level Network Zone findings."""
+
+ id: str = "okta-network-zones"
+ name: str = "Okta Network Zones"
diff --git a/prowler/providers/okta/services/signon/lib/__init__.py b/prowler/providers/okta/services/signon/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/signon/lib/signon_helpers.py b/prowler/providers/okta/services/signon/lib/signon_helpers.py
new file mode 100644
index 0000000000..7c84fe5733
--- /dev/null
+++ b/prowler/providers/okta/services/signon/lib/signon_helpers.py
@@ -0,0 +1,146 @@
+"""Shared helpers for the OKTA sign-on STIG checks.
+
+The four `signon_global_session_*` checks share the same plumbing:
+they iterate active Global Session Policies in priority order, locate
+each policy's Priority 1 active rule, and emit one finding per policy.
+This module centralises that plumbing so each check can stay focused
+on its STIG-specific predicate.
+"""
+
+from typing import Optional
+
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.signon.signon_service import (
+ GlobalSessionPolicy,
+ GlobalSessionPolicyRule,
+ SignInPage,
+)
+
+
+def active_policies(
+ global_session_policies: dict[str, GlobalSessionPolicy],
+) -> list[GlobalSessionPolicy]:
+ """Return active policies sorted by priority (ascending, name as tiebreaker).
+
+ A policy with no `status` is treated as ACTIVE because the Okta SDK
+ sometimes omits the field on default policies.
+ """
+ return sorted(
+ [
+ policy
+ for policy in global_session_policies.values()
+ if not policy.status or policy.status.upper() == "ACTIVE"
+ ],
+ key=lambda policy: (
+ policy.priority if policy.priority is not None else float("inf"),
+ policy.name,
+ ),
+ )
+
+
+def priority_one_active_rule(
+ policy: GlobalSessionPolicy,
+) -> Optional[GlobalSessionPolicyRule]:
+ """Return the policy's Priority 1 active rule, or None.
+
+ Okta's evaluator skips inactive rules, so we first filter to active
+ rules and pick the highest-priority one. If that rule is not at
+ priority 1 we return None — the policy effectively has no
+ priority-1 rule for evaluation purposes.
+ """
+ active_rules = sorted(
+ [
+ rule
+ for rule in policy.rules
+ if not rule.status or rule.status.upper() == "ACTIVE"
+ ],
+ key=lambda rule: (
+ rule.priority if rule.priority is not None else float("inf"),
+ rule.name,
+ ),
+ )
+ if not active_rules:
+ return None
+ candidate = active_rules[0]
+ if candidate.priority != 1:
+ return None
+ return candidate
+
+
+def policy_label(policy: GlobalSessionPolicy) -> str:
+ kind = "default" if policy.is_default else "custom"
+ priority = policy.priority if policy.priority is not None else "unset"
+ return f"Global Session Policy '{policy.name}' (priority {priority}, {kind})"
+
+
+def no_active_policies_finding(
+ metadata, org_domain: str, status_extended: str
+) -> CheckReportOkta:
+ """Build the FAIL finding emitted when no active sign-on policies exist."""
+ placeholder = GlobalSessionPolicy(
+ id="signon-policies-missing",
+ name="(no active sign-on policies)",
+ priority=1,
+ status="MISSING",
+ is_default=False,
+ rules=[],
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "FAIL"
+ report.status_extended = status_extended
+ return report
+
+
+_SCOPE_ADVICE = (
+ "Grant it on the service app's Okta API Scopes tab in the Okta Admin "
+ "Console, then re-run the check."
+)
+
+
+def missing_policy_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding for a sign-on policy check when the API scope is not granted."""
+ placeholder = GlobalSessionPolicy(
+ id="signon-policies-scope-missing",
+ name="(scope not granted)",
+ priority=1,
+ status="MISSING",
+ is_default=False,
+ rules=[],
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Global Session Policies: the Okta service app "
+ f"is missing the required `{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
+
+
+def missing_brand_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding for a brand/sign-in-page check when the API scope is not granted."""
+ placeholder = SignInPage(
+ brand_id="signon-brands-scope-missing",
+ brand_name="(scope not granted)",
+ is_customized=False,
+ )
+ report = CheckReportOkta(
+ metadata=metadata,
+ resource=placeholder,
+ org_domain=org_domain,
+ resource_name=placeholder.brand_name,
+ resource_id=placeholder.brand_id,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Okta brand sign-in pages: the Okta service app "
+ f"is missing the required `{scope}` API scope. {_SCOPE_ADVICE}"
+ )
+ return report
diff --git a/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/__init__.py b/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.metadata.json b/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.metadata.json
new file mode 100644
index 0000000000..523795c8ac
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "okta",
+ "CheckID": "signon_dod_warning_banner_configured",
+ "CheckTitle": "Okta sign-in page displays the Standard Mandatory DOD Notice and Consent Banner",
+ "CheckType": [],
+ "ServiceName": "signon",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "informational",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "Each Okta brand's sign-in page must present the **Standard Mandatory DOD Notice and Consent Banner** (`DTM-08-060`) before granting access.\n\nThe check inspects the sign-in page HTML returned by the Okta Management API, using the *customized* page when present and otherwise falling back to the *default* sign-in page.\n\nAligns with **DISA STIG V-273192 / OKTA-APP-000200**.",
+ "Risk": "Without the **DOD Notice and Consent Banner**, users are not informed that the system is a U.S. Government information system subject to monitoring.\n\n- **Legal basis** for incident response and prosecution is weakened\n- **Alignment** with federal laws, Executive Orders, directives, and standards is broken\n- **Implied consent** to monitoring cannot be asserted on connection",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/settings/settings-customization.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/CustomPages/",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Brands/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Follow the supplemental *Okta DOD Warning Banner Configuration Guide* shipped with the **DISA Okta IDaaS STIG** package.\n2. Sign in to the **Okta Admin Console** as a *Super Admin*.\n3. Navigate to **Customizations** > **Brands** and select the brand.\n4. Edit the **Sign-in page** customization.\n5. Insert the full `DTM-08-060` Standard Mandatory DOD Notice and Consent Banner text into the page content.\n6. Publish the customization and verify the banner is presented before sign-in.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Customize the Okta sign-in page for **each brand** to display the **Standard Mandatory DOD Notice and Consent Banner** (`DTM-08-060`) before users authenticate.\n\nApplies only to Okta tenants under **U.S. Department of Defense** scope; non-DOD organizations can mute this check.",
+ "Url": "https://hub.prowler.com/check/signon_dod_warning_banner_configured"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Applicable only to Okta tenants under U.S. Department of Defense scope (DISA Okta IDaaS STIG, control V-273192 / OKTA-APP-000200). For non-DOD organizations this check is not applicable and can be muted."
+}
diff --git a/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.py b/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.py
new file mode 100644
index 0000000000..347f04f245
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_dod_warning_banner_configured/signon_dod_warning_banner_configured.py
@@ -0,0 +1,129 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.signon.lib.signon_helpers import (
+ missing_brand_scope_finding,
+)
+from prowler.providers.okta.services.signon.signon_client import signon_client
+from prowler.providers.okta.services.signon.signon_service import SignInPage
+
+# Distinctive marker groups drawn from the DTM-08-060 Standard Mandatory
+# DOD Notice and Consent Banner. The HTML can vary across brands, so the
+# check looks for the banner's core ideas rather than requiring an exact
+# string match.
+BANNER_MARKER_GROUPS = (
+ ("u.s. government", "us government"),
+ ("information system", "information systems"),
+ ("authorized use only", "authorized use"),
+ (
+ "subject to monitoring",
+ "may be intercepted",
+ "searched, monitored, and recorded",
+ "consent to monitoring",
+ ),
+)
+
+
+def _matched_banner_groups(content_lower: str) -> list[str]:
+ matched_markers: list[str] = []
+ for marker_group in BANNER_MARKER_GROUPS:
+ for marker in marker_group:
+ if marker in content_lower:
+ matched_markers.append(marker)
+ break
+ return matched_markers
+
+
+class signon_dod_warning_banner_configured(Check):
+ """STIG V-273192 / OKTA-APP-000200.
+
+ Okta must display the Standard Mandatory DOD Notice and Consent
+ Banner (DTM-08-060) before granting access to the application. The
+ check inspects each brand's sign-in page HTML returned by the Okta
+ Management API, using the customized page when present and otherwise
+ falling back to the default sign-in page.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ org_domain = signon_client.provider.identity.org_domain
+ findings: list[CheckReportOkta] = []
+
+ missing_scope = signon_client.missing_scope.get("sign_in_pages")
+ if missing_scope:
+ return [
+ missing_brand_scope_finding(self.metadata(), org_domain, missing_scope)
+ ]
+
+ if not signon_client.sign_in_pages:
+ placeholder = SignInPage(
+ brand_id="no-brands-detected",
+ brand_name="(no brands detected)",
+ is_customized=False,
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=placeholder,
+ org_domain=org_domain,
+ resource_name=placeholder.brand_name,
+ resource_id=placeholder.brand_id,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "No Okta brands were retrieved from the Brands API. Verify "
+ "the sign-in page for the organization displays the DOD "
+ "Notice and Consent Banner (DTM-08-060) in the Admin Console."
+ )
+ findings.append(report)
+ return findings
+
+ for page in signon_client.sign_in_pages.values():
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=page,
+ org_domain=org_domain,
+ resource_name=page.brand_name or page.brand_id,
+ resource_id=page.brand_id,
+ )
+
+ if page.fetch_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve the sign-in page for "
+ f"brand '{page.brand_name or page.brand_id}' ({page.fetch_error}). "
+ "Inspect the brand manually to confirm the "
+ "DOD Notice and Consent Banner (DTM-08-060) is displayed."
+ )
+ findings.append(report)
+ continue
+
+ if not page.page_content:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Sign-in page content for brand "
+ f"'{page.brand_name or page.brand_id}' could not be "
+ "retrieved from the Okta API. Verify the DOD Notice and "
+ "Consent Banner (DTM-08-060) manually in the Admin Console."
+ )
+ findings.append(report)
+ continue
+
+ page_type = "customized" if page.is_customized else "default"
+ content_lower = page.page_content.lower()
+ matches = _matched_banner_groups(content_lower)
+
+ if len(matches) == len(BANNER_MARKER_GROUPS):
+ report.status = "PASS"
+ report.status_extended = (
+ f"DOD Notice and Consent Banner detected on the {page_type} "
+ f"sign-in page for brand '{page.brand_name or page.brand_id}' "
+ f"({len(matches)} of {len(BANNER_MARKER_GROUPS)} required "
+ "marker groups matched)."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{page_type.title()} sign-in page for brand "
+ f"'{page.brand_name or page.brand_id}' does not contain "
+ "the DOD Notice and Consent Banner (DTM-08-060)."
+ )
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/__init__.py b/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.metadata.json b/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.metadata.json
new file mode 100644
index 0000000000..c4738fd5bf
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "signon_global_session_cookies_not_persistent",
+ "CheckTitle": "Default Global Session Policy has a Priority 1 non-default rule disabling persistent global session cookies",
+ "CheckType": [],
+ "ServiceName": "signon",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "Every active Okta **Global Session Policy** needs a **Priority 1** rule that is **not** the built-in `Default Rule`, setting *Okta global session cookies persist across browser sessions* to `Disabled`.\n\nOkta evaluates policies by group assignment, so a permissive custom policy can govern users. Aligns with **DISA STIG V-273206 / OKTA-APP-001710**.",
+ "Risk": "Persistent global session cookies keep an authenticated Okta session alive across browser restarts.\n\n- **Surviving sessions** outlive the browsing context the user expected\n- **Cached authorization decisions** remain in effect after the browser closes\n- **Forgotten or shared devices** continue to hold authenticated access until cookies expire on their own",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-okta-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Global Session Policy**.\n3. Open the **Default Policy** (and repeat for every other active policy).\n4. Add or edit a non-default rule.\n5. Move that rule to **Priority 1** so it is evaluated before the built-in `Default Rule`.\n6. Set *Okta global session cookies persist across browser sessions* to `Disabled`.\n7. Save the rule.",
+ "Terraform": "```hcl\nresource \"okta_policy_rule_signon\" \"<example_resource_name>\" {\n policy_id = okta_policy_signon.default.id\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n priority = 1 # Critical: rule must sit at Priority 1 before the Default Rule\n session_persistent = false # Critical: disable persistent global session cookies\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure each active **Global Session Policy** so a non-default rule at **Priority 1**:\n- Sets *Okta global session cookies persist across browser sessions* to `Disabled`\n- Is enabled (`ACTIVE`) and evaluated before the built-in `Default Rule`\n\nReview group assignments to confirm the rule actually governs the intended users.",
+ "Url": "https://hub.prowler.com/check/signon_global_session_cookies_not_persistent"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.py b/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.py
new file mode 100644
index 0000000000..c5ffd849b5
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_cookies_not_persistent/signon_global_session_cookies_not_persistent.py
@@ -0,0 +1,100 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.signon.lib.signon_helpers import (
+ active_policies,
+ missing_policy_scope_finding,
+ no_active_policies_finding,
+ policy_label,
+ priority_one_active_rule,
+)
+from prowler.providers.okta.services.signon.signon_client import signon_client
+from prowler.providers.okta.services.signon.signon_service import GlobalSessionPolicy
+
+
+class signon_global_session_cookies_not_persistent(Check):
+ """STIG V-273206 / OKTA-APP-001710.
+
+ Every active Global Session Policy must have an active Priority 1
+ rule that is not the built-in Default Rule, and that rule must
+ disable persistent global session cookies so the session does not
+ survive across browser restarts.
+
+ Okta evaluates sign-on policies in priority order based on group
+ assignments, so a permissive custom policy can govern a user's
+ session even when the Default Policy is strict. The check emits one
+ finding per active policy to surface that risk.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ org_domain = signon_client.provider.identity.org_domain
+
+ missing_scope = signon_client.missing_scope.get("global_session_policies")
+ if missing_scope:
+ return [
+ missing_policy_scope_finding(self.metadata(), org_domain, missing_scope)
+ ]
+
+ policies = active_policies(signon_client.global_session_policies)
+ if not policies:
+ return [
+ no_active_policies_finding(
+ self.metadata(),
+ org_domain,
+ "No active Okta Global Session Policies were returned by the API. "
+ "STIG V-273206 requires the policy that governs each user to enforce "
+ "a Priority 1 non-default rule that disables persistent global "
+ "session cookies.",
+ )
+ ]
+
+ findings: list[CheckReportOkta] = []
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ status, status_extended = _evaluate_policy(policy)
+ report.status = status
+ report.status_extended = status_extended
+ findings.append(report)
+ return findings
+
+
+def _evaluate_policy(policy: GlobalSessionPolicy) -> tuple[str, str]:
+ label = policy_label(policy)
+ rule = priority_one_active_rule(policy)
+
+ if rule is None:
+ return (
+ "FAIL",
+ f"{label} has no Priority 1 active rule. STIG V-273206 requires "
+ "a non-default Priority 1 rule that disables persistent global "
+ "session cookies.",
+ )
+
+ if rule.is_default or rule.name == "Default Rule":
+ return (
+ "FAIL",
+ f"{label} uses '{rule.name}' as its active Priority 1 rule. "
+ "The STIG requires a non-default Priority 1 rule.",
+ )
+
+ use_persistent_cookie = rule.use_persistent_cookie
+ if use_persistent_cookie is None:
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "does not assert the 'Okta global session cookies persist across "
+ "browser sessions' setting.",
+ )
+
+ if use_persistent_cookie is False:
+ return (
+ "PASS",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "disables persistent global session cookies.",
+ )
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "allows persistent global session cookies, leaving the session active "
+ "across browser restarts.",
+ )
diff --git a/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.metadata.json b/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.metadata.json
index 6a191b4a8a..f31a835864 100644
--- a/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.metadata.json
+++ b/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.metadata.json
@@ -9,8 +9,8 @@
"Severity": "medium",
"ResourceType": "NotDefined",
"ResourceGroup": "governance",
- "Description": "The **Default Global Session Policy** must have a **Priority 1** rule that is **not** the built-in `Default Rule`, and that rule must set **Maximum Okta global session idle time** to 15 minutes or less. The threshold defaults to 15 minutes and is overridable via the `okta_max_session_idle_minutes` key in the audit config.",
- "Risk": "Without a 15-minute idle timeout, an unattended workstation leaves an authenticated Okta session open indefinitely, allowing an attacker physical or remote access to take over the user's identity and pivot into every downstream application that trusts Okta SSO.",
+ "Description": "Every active Okta **Global Session Policy** needs a **Priority 1** rule that is **not** the built-in `Default Rule`, setting *Maximum Okta global session idle time* to `15` minutes or less.\n\nOkta evaluates policies by group assignment, so a permissive custom policy can govern users. Threshold override: `okta_max_session_idle_minutes`. Aligns with **DISA STIG V-273186**.",
+ "Risk": "Without a `15`-minute idle timeout, an unattended workstation leaves an authenticated Okta session open indefinitely.\n\n- **Session takeover** of the user's identity by anyone with physical or remote access\n- **Lateral movement** into every downstream application that trusts Okta SSO\n- **Bypassed reauthentication** even after the user has stepped away",
"RelatedUrl": "",
"AdditionalURLs": [
"https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-okta-sign-on-policies.htm",
@@ -20,11 +20,11 @@
"Code": {
"CLI": "",
"NativeIaC": "",
- "Other": "1. Sign in to the Okta Admin Console as a Super Admin\n2. Go to Security > Global Session Policy\n3. Open the Default Policy\n4. Add or edit a non-default rule\n5. Move that rule to Priority 1 so it is evaluated before the built-in Default Rule\n6. Set 'Maximum Okta global session idle time' to 15 minutes or less\n7. Save the rule",
- "Terraform": "resource \"okta_policy_rule_signon\" \"prowler_idle_timeout_15min\" {\n policy_id = okta_policy_signon.default.id\n name = \"Prowler-enforced idle timeout\"\n status = \"ACTIVE\"\n session_idle = 15\n session_persistent = false\n}\n"
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Global Session Policy**.\n3. Open the **Default Policy** (and repeat for every other active policy).\n4. Add or edit a non-default rule.\n5. Move that rule to **Priority 1** so it is evaluated before the built-in `Default Rule`.\n6. Set *Maximum Okta global session idle time* to `15` minutes or less.\n7. Save the rule.",
+ "Terraform": "```hcl\nresource \"okta_policy_rule_signon\" \"<example_resource_name>\" {\n policy_id = okta_policy_signon.default.id\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n priority = 1 # Critical: rule must sit at Priority 1 before the Default Rule\n session_idle = 15 # Critical: enforce idle timeout at 15 minutes or less\n session_persistent = false # Critical: avoid persistent global session cookies\n}\n```"
},
"Recommendation": {
- "Text": "Configure the Default Global Session Policy so its Priority 1 non-default rule sets the Maximum Okta global session idle time to 15 minutes or less.",
+ "Text": "Configure each active **Global Session Policy** so a non-default rule at **Priority 1**:\n- Sets *Maximum Okta global session idle time* to `15` minutes or less\n- Is enabled (`ACTIVE`) and evaluated before the built-in `Default Rule`\n\nReview group assignments to confirm the rule actually governs the intended users.",
"Url": "https://hub.prowler.com/check/signon_global_session_idle_timeout_15min"
}
},
diff --git a/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.py b/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.py
index e34c375fd2..3f20a22adb 100644
--- a/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.py
+++ b/prowler/providers/okta/services/signon/signon_global_session_idle_timeout_15min/signon_global_session_idle_timeout_15min.py
@@ -1,4 +1,11 @@
from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.signon.lib.signon_helpers import (
+ active_policies,
+ missing_policy_scope_finding,
+ no_active_policies_finding,
+ policy_label,
+ priority_one_active_rule,
+)
from prowler.providers.okta.services.signon.signon_client import signon_client
from prowler.providers.okta.services.signon.signon_service import GlobalSessionPolicy
@@ -8,11 +15,16 @@ DEFAULT_THRESHOLD_MINUTES = 15
class signon_global_session_idle_timeout_15min(Check):
"""STIG V-273186 / OKTA-APP-000020.
- The DISA STIG requires the Okta Default Policy to have an active
- Priority 1 rule that is not the built-in Default Rule, and that
- rule must set the maximum Okta global session idle time to the
- configured threshold or lower (defaults to 15 minutes per STIG;
- override via `okta_max_session_idle_minutes` in the audit config).
+ Every active Global Session Policy must have an active Priority 1
+ rule that is not the built-in Default Rule, and that rule must set
+ the maximum Okta global session idle time to the configured
+ threshold or lower (defaults to 15 minutes per STIG; override via
+ `okta_max_session_idle_minutes` in the audit config).
+
+ Okta evaluates sign-on policies in priority order based on group
+ assignments, so a permissive custom policy can govern a user's
+ session even when the Default Policy is strict. The check emits one
+ finding per active policy to surface that risk.
"""
def execute(self) -> list[CheckReportOkta]:
@@ -21,106 +33,74 @@ class signon_global_session_idle_timeout_15min(Check):
"okta_max_session_idle_minutes", DEFAULT_THRESHOLD_MINUTES
)
org_domain = signon_client.provider.identity.org_domain
- policy = self._get_default_policy()
- report = CheckReportOkta(
- metadata=self.metadata(), resource=policy, org_domain=org_domain
+
+ missing_scope = signon_client.missing_scope.get("global_session_policies")
+ if missing_scope:
+ return [
+ missing_policy_scope_finding(self.metadata(), org_domain, missing_scope)
+ ]
+
+ policies = active_policies(signon_client.global_session_policies)
+ if not policies:
+ return [
+ no_active_policies_finding(
+ self.metadata(),
+ org_domain,
+ "No active Okta Global Session Policies were returned by the API. "
+ "STIG V-273186 requires the policy that governs each user to enforce "
+ "a Priority 1 non-default rule with a 15-minute idle timeout.",
+ )
+ ]
+
+ findings: list[CheckReportOkta] = []
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ status, status_extended = _evaluate_policy(policy, threshold)
+ report.status = status
+ report.status_extended = status_extended
+ findings.append(report)
+ return findings
+
+
+def _evaluate_policy(policy: GlobalSessionPolicy, threshold: int) -> tuple[str, str]:
+ label = policy_label(policy)
+ rule = priority_one_active_rule(policy)
+
+ if rule is None:
+ return (
+ "FAIL",
+ f"{label} has no Priority 1 active rule. STIG V-273186 requires "
+ f"a non-default Priority 1 rule with idle timeout <= {threshold} "
+ "minutes.",
)
- if policy.id == "default-policy-missing":
- report.status = "FAIL"
- report.status_extended = (
- "Default Global Session Policy was not found. STIG V-273186 "
- "requires the Default Policy to contain an active Priority 1 "
- f"non-default rule with idle timeout <= {threshold} minutes."
- )
- return [report]
-
- if policy.status and policy.status.upper() != "ACTIVE":
- report.status = "FAIL"
- report.status_extended = (
- f"Default Global Session Policy '{policy.name}' is in "
- f"status '{policy.status}'. STIG V-273186 requires an active "
- "Default Policy with an active Priority 1 non-default rule."
- )
- return [report]
-
- active_rules = sorted(
- [
- rule
- for rule in policy.rules
- if not rule.status or rule.status.upper() == "ACTIVE"
- ],
- key=lambda rule: (
- rule.priority if rule.priority is not None else float("inf"),
- rule.name,
- ),
+ if rule.is_default or rule.name == "Default Rule":
+ return (
+ "FAIL",
+ f"{label} uses '{rule.name}' as its active Priority 1 rule. "
+ "The STIG requires a non-default Priority 1 rule.",
)
- if not active_rules:
- report.status = "FAIL"
- report.status_extended = (
- f"Default Global Session Policy '{policy.name}' has no active "
- "rules. STIG V-273186 requires an active Priority 1 non-default "
- f"rule with idle timeout <= {threshold} minutes."
- )
- return [report]
- priority_one_rule = active_rules[0]
- if priority_one_rule.priority != 1:
- report.status = "FAIL"
- report.status_extended = (
- f"Default Global Session Policy '{policy.name}' has no active "
- f"Priority 1 rule. The first active rule is '{priority_one_rule.name}' "
- f"at priority {priority_one_rule.priority}."
- )
- return [report]
-
- if priority_one_rule.is_default or priority_one_rule.name == "Default Rule":
- report.status = "FAIL"
- report.status_extended = (
- f"Default Global Session Policy '{policy.name}' uses "
- f"'{priority_one_rule.name}' as its active Priority 1 rule. "
- "The STIG requires a non-default Priority 1 rule."
- )
- return [report]
-
- idle_timeout = priority_one_rule.max_session_idle_minutes
- if idle_timeout is None:
- report.status = "FAIL"
- report.status_extended = (
- f"Priority 1 non-default rule '{priority_one_rule.name}' in "
- f"Default Global Session Policy '{policy.name}' does not define "
- "a maximum Okta global session idle time."
- )
- return [report]
-
- if idle_timeout <= threshold:
- report.status = "PASS"
- report.status_extended = (
- f"Priority 1 non-default rule '{priority_one_rule.name}' in "
- f"Default Global Session Policy '{policy.name}' sets the "
- f"maximum Okta global session idle time to {idle_timeout} "
- f"minutes, meeting the configured threshold of {threshold} minutes."
- )
- else:
- report.status = "FAIL"
- report.status_extended = (
- f"Priority 1 non-default rule '{priority_one_rule.name}' in "
- f"Default Global Session Policy '{policy.name}' sets the "
- f"maximum Okta global session idle time to {idle_timeout} "
- f"minutes, exceeding the configured threshold of {threshold} minutes."
- )
- return [report]
-
- @staticmethod
- def _get_default_policy() -> GlobalSessionPolicy:
- for policy in signon_client.global_session_policies.values():
- if policy.is_default or policy.name == "Default Policy":
- return policy
- return GlobalSessionPolicy(
- id="default-policy-missing",
- name="Default Policy",
- priority=1,
- status="MISSING",
- is_default=True,
- rules=[],
+ idle_timeout = rule.max_session_idle_minutes
+ if idle_timeout is None:
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "does not define a maximum Okta global session idle time.",
)
+
+ if idle_timeout <= threshold:
+ return (
+ "PASS",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ f"sets the maximum Okta global session idle time to {idle_timeout} "
+ f"minutes, meeting the configured threshold of {threshold} minutes.",
+ )
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ f"sets the maximum Okta global session idle time to {idle_timeout} "
+ f"minutes, exceeding the configured threshold of {threshold} minutes.",
+ )
diff --git a/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/__init__.py b/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.metadata.json b/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.metadata.json
new file mode 100644
index 0000000000..84d88b3c76
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "signon_global_session_lifetime_18h",
+ "CheckTitle": "Default Global Session Policy has a Priority 1 non-default rule limiting session lifetime to 18 hours",
+ "CheckType": [],
+ "ServiceName": "signon",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "Every active Okta **Global Session Policy** needs a **Priority 1** rule that is **not** the built-in `Default Rule`, setting *Maximum Okta global session lifetime* to `18` hours or less.\n\nOkta evaluates policies by group assignment, so a permissive custom policy can govern users. Threshold override: `okta_max_session_lifetime_minutes` (minutes). Aligns with **DISA STIG V-273203**.",
+ "Risk": "Without an enforced session lifetime, an authenticated Okta session can be reused indefinitely without reauthentication.\n\n- **Stolen session material** continues to grant access long after sign-in\n- **Authorization changes** (role revocation, group removal) take effect only on the next reauth\n- **Token replay** against downstream apps stays viable for the session window",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-okta-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Global Session Policy**.\n3. Open the **Default Policy** (and repeat for every other active policy).\n4. Add or edit a non-default rule.\n5. Move that rule to **Priority 1** so it is evaluated before the built-in `Default Rule`.\n6. Set *Maximum Okta global session lifetime* to `18` hours or less. Do **not** set it to `0`, which disables the limit.\n7. Save the rule.",
+ "Terraform": "```hcl\nresource \"okta_policy_rule_signon\" \"<example_resource_name>\" {\n policy_id = okta_policy_signon.default.id\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n priority = 1 # Critical: rule must sit at Priority 1 before the Default Rule\n session_lifetime = 1080 # Critical: 18 hours in minutes; do not use 0 (disables the limit)\n session_persistent = false # Critical: avoid persistent global session cookies\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure each active **Global Session Policy** so a non-default rule at **Priority 1**:\n- Sets *Maximum Okta global session lifetime* to `18` hours or less (`1080` minutes)\n- Never sets the lifetime to `0`, which disables the limit\n- Is enabled (`ACTIVE`) and evaluated before the built-in `Default Rule`\n\nReview group assignments to confirm the rule actually governs the intended users.",
+ "Url": "https://hub.prowler.com/check/signon_global_session_lifetime_18h"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.py b/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.py
new file mode 100644
index 0000000000..25003eef90
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_lifetime_18h/signon_global_session_lifetime_18h.py
@@ -0,0 +1,114 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.signon.lib.signon_helpers import (
+ active_policies,
+ missing_policy_scope_finding,
+ no_active_policies_finding,
+ policy_label,
+ priority_one_active_rule,
+)
+from prowler.providers.okta.services.signon.signon_client import signon_client
+from prowler.providers.okta.services.signon.signon_service import GlobalSessionPolicy
+
+DEFAULT_THRESHOLD_MINUTES = 18 * 60
+
+
+class signon_global_session_lifetime_18h(Check):
+ """STIG V-273203 / OKTA-APP-001665.
+
+ Every active Global Session Policy must have an active Priority 1
+ rule that is not the built-in Default Rule, and that rule must set
+ the maximum Okta global session lifetime to the configured threshold
+ or lower (defaults to 18 hours per STIG; override via
+ `okta_max_session_lifetime_minutes` in the audit config).
+
+ Okta evaluates sign-on policies in priority order based on group
+ assignments, so a permissive custom policy can govern a user's
+ session even when the Default Policy is strict. The check emits one
+ finding per active policy to surface that risk.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ audit_config = signon_client.audit_config or {}
+ threshold = audit_config.get(
+ "okta_max_session_lifetime_minutes", DEFAULT_THRESHOLD_MINUTES
+ )
+ org_domain = signon_client.provider.identity.org_domain
+
+ missing_scope = signon_client.missing_scope.get("global_session_policies")
+ if missing_scope:
+ return [
+ missing_policy_scope_finding(self.metadata(), org_domain, missing_scope)
+ ]
+
+ policies = active_policies(signon_client.global_session_policies)
+ if not policies:
+ return [
+ no_active_policies_finding(
+ self.metadata(),
+ org_domain,
+ "No active Okta Global Session Policies were returned by the API. "
+ "STIG V-273203 requires the policy that governs each user to enforce "
+ "a Priority 1 non-default rule with an 18-hour session lifetime.",
+ )
+ ]
+
+ findings: list[CheckReportOkta] = []
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ status, status_extended = _evaluate_policy(policy, threshold)
+ report.status = status
+ report.status_extended = status_extended
+ findings.append(report)
+ return findings
+
+
+def _evaluate_policy(policy: GlobalSessionPolicy, threshold: int) -> tuple[str, str]:
+ label = policy_label(policy)
+ rule = priority_one_active_rule(policy)
+
+ if rule is None:
+ return (
+ "FAIL",
+ f"{label} has no Priority 1 active rule. STIG V-273203 requires "
+ f"a non-default Priority 1 rule with session lifetime <= {threshold} "
+ "minutes.",
+ )
+
+ if rule.is_default or rule.name == "Default Rule":
+ return (
+ "FAIL",
+ f"{label} uses '{rule.name}' as its active Priority 1 rule. "
+ "The STIG requires a non-default Priority 1 rule.",
+ )
+
+ lifetime = rule.max_session_lifetime_minutes
+ if lifetime is None:
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "does not define a maximum Okta global session lifetime.",
+ )
+
+ if lifetime == 0:
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ "disables the maximum Okta global session lifetime by setting it "
+ "to 0 minutes.",
+ )
+
+ if lifetime <= threshold:
+ return (
+ "PASS",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ f"sets the maximum Okta global session lifetime to {lifetime} "
+ f"minutes, meeting the configured threshold of {threshold} minutes.",
+ )
+ return (
+ "FAIL",
+ f"Priority 1 non-default rule '{rule.name}' in {label} "
+ f"sets the maximum Okta global session lifetime to {lifetime} minutes, "
+ f"exceeding the configured threshold of {threshold} minutes.",
+ )
diff --git a/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/__init__.py b/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.metadata.json b/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.metadata.json
new file mode 100644
index 0000000000..b1009ba970
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.metadata.json
@@ -0,0 +1,38 @@
+{
+ "Provider": "okta",
+ "CheckID": "signon_global_session_policy_network_zone_enforced",
+ "CheckTitle": "Default Global Session Policy applies a Network Zone condition aligned with the Access Control Policy",
+ "CheckType": [],
+ "ServiceName": "signon",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "governance",
+ "Description": "Every active Okta **Global Session Policy** must apply the *IF User's IP is* condition, mapped to a **Network Zone**, on its **Priority 1** active rule.\n\nUnlike the idle / lifetime / cookie STIGs, this control does **not** exclude the built-in `Default Rule`. Okta evaluates policies by group assignment. Aligns with **DISA STIG V-279691**.",
+ "Risk": "When the Global Session Policy does not restrict access by **Network Zone**, every authenticated entity establishes a session regardless of source IP.\n\n- **Stolen credentials** reach the Okta dashboard from any internet-routable address\n- **Out-of-band sessions** bypass the organization's Access Control Policy\n- **Network anomalies** cannot become deny decisions at sign-on",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/oie/en-us/content/topics/security/network/network-zones.htm",
+ "https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/about-okta-sign-on-policies.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Security** > **Networks** and define the **Network Zones** (allow / deny) that match the organization's Access Control Policy.\n3. Navigate to **Security** > **Global Session Policy**.\n4. Open the **Default Policy** (and repeat for every other active policy).\n5. Edit the rule that sits at **Priority 1**, or add a new one and move it to **Priority 1**.\n6. Under *Conditions*, set *IF User's IP is* to `In zone` (allow) or `Not in zone` (deny) and select the **Network Zone**.\n7. Save the rule.",
+ "Terraform": "```hcl\nresource \"okta_policy_rule_signon\" \"<example_resource_name>\" {\n policy_id = okta_policy_signon.default.id\n name = \"<example_resource_name>\"\n status = \"ACTIVE\"\n priority = 1 # Critical: rule must sit at Priority 1\n network_connection = \"ZONE\" # Critical: bind the rule to a Network Zone\n network_includes = [okta_network_zone.allowed.id] # Critical: zones that reflect the Access Control Policy\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Configure the **Priority 1** active rule in each Global Session Policy so it:\n- Maps the *IF User's IP is* condition to a **Network Zone** aligned with the organization's Access Control Policy\n- Uses `In zone` for allow-list zones and `Not in zone` for deny-list zones\n- Is enabled (`ACTIVE`) and evaluated before the built-in `Default Rule`, or *is* the `Default Rule` itself\n\nReview group assignments to confirm the rule actually governs the intended users.",
+ "Url": "https://hub.prowler.com/check/signon_global_session_policy_network_zone_enforced"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.py b/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.py
new file mode 100644
index 0000000000..7a7e51706c
--- /dev/null
+++ b/prowler/providers/okta/services/signon/signon_global_session_policy_network_zone_enforced/signon_global_session_policy_network_zone_enforced.py
@@ -0,0 +1,95 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.signon.lib.signon_helpers import (
+ active_policies,
+ missing_policy_scope_finding,
+ no_active_policies_finding,
+ policy_label,
+ priority_one_active_rule,
+)
+from prowler.providers.okta.services.signon.signon_client import signon_client
+from prowler.providers.okta.services.signon.signon_service import GlobalSessionPolicy
+
+
+class signon_global_session_policy_network_zone_enforced(Check):
+ """STIG V-279691 / OKTA-APP-003242.
+
+ Every active Global Session Policy must apply an "IF User's IP is"
+ condition mapped to a Network Zone on its Priority 1 active rule so
+ access can be allowed or denied per the organization's Access
+ Control Policy.
+
+ Unlike the idle / lifetime / persistent-cookie STIGs, V-279691 does
+ not exclude the built-in Default Rule, so a zone condition on the
+ Default Rule is still effective when no non-default rule sits at
+ Priority 1.
+
+ The check emits one finding per active policy because Okta evaluates
+ sign-on policies in priority order based on group assignments, and a
+ permissive custom policy can govern a user's session even when the
+ Default Policy is strict.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ org_domain = signon_client.provider.identity.org_domain
+
+ missing_scope = signon_client.missing_scope.get("global_session_policies")
+ if missing_scope:
+ return [
+ missing_policy_scope_finding(self.metadata(), org_domain, missing_scope)
+ ]
+
+ policies = active_policies(signon_client.global_session_policies)
+ if not policies:
+ return [
+ no_active_policies_finding(
+ self.metadata(),
+ org_domain,
+ "No active Okta Global Session Policies were returned by the API. "
+ "STIG V-279691 requires the policy that governs each user to map "
+ "User's IP to a Network Zone on its Priority 1 active rule.",
+ )
+ ]
+
+ findings: list[CheckReportOkta] = []
+ for policy in policies:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=policy, org_domain=org_domain
+ )
+ status, status_extended = _evaluate_policy(policy)
+ report.status = status
+ report.status_extended = status_extended
+ findings.append(report)
+ return findings
+
+
+def _evaluate_policy(policy: GlobalSessionPolicy) -> tuple[str, str]:
+ label = policy_label(policy)
+ rule = priority_one_active_rule(policy)
+
+ if rule is None:
+ return (
+ "FAIL",
+ f"{label} has no Priority 1 active rule. STIG V-279691 requires "
+ "the policy to apply an IP-based Network Zone condition on its "
+ "Priority 1 active rule.",
+ )
+
+ rule_kind = (
+ "built-in Default Rule"
+ if rule.is_default or rule.name == "Default Rule"
+ else "non-default rule"
+ )
+ has_zones = bool(rule.network_zones_include or rule.network_zones_exclude)
+
+ if has_zones:
+ return (
+ "PASS",
+ f"Priority 1 active {rule_kind} '{rule.name}' in {label} maps "
+ "User's IP to a Network Zone.",
+ )
+ return (
+ "FAIL",
+ f"Priority 1 active {rule_kind} '{rule.name}' in {label} does not "
+ "map User's IP to a Network Zone. The policy cannot allow or deny "
+ "access based on the organization's Access Control Policy.",
+ )
diff --git a/prowler/providers/okta/services/signon/signon_service.py b/prowler/providers/okta/services/signon/signon_service.py
index 12c1349a2c..663e9cf187 100644
--- a/prowler/providers/okta/services/signon/signon_service.py
+++ b/prowler/providers/okta/services/signon/signon_service.py
@@ -1,46 +1,56 @@
from typing import Optional
-from urllib.parse import parse_qs, urlparse
from pydantic import BaseModel
from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate as _paginate_shared
from prowler.providers.okta.lib.service.service import OktaService
-
-def _next_after_cursor(resp) -> Optional[str]:
- """Extract the `after` cursor from a `Link: ...; rel="next"` header.
-
- Returns None when there is no next page. Header format follows RFC 5988
- and Okta's pagination guide.
- """
- if resp is None:
- return None
- headers = getattr(resp, "headers", None) or {}
- link = headers.get("link") or headers.get("Link") or ""
- if not link:
- return None
- for part in link.split(","):
- if 'rel="next"' not in part:
- continue
- url_segment = part.split(";", 1)[0].strip().lstrip("<").rstrip(">")
- cursor = parse_qs(urlparse(url_segment).query).get("after", [None])[0]
- if cursor:
- return cursor
- return None
+REQUIRED_SCOPES: dict[str, str] = {
+ "global_session_policies": "okta.policies.read",
+ "sign_in_pages": "okta.brands.read",
+}
class Signon(OktaService):
- """Fetches OKTA_SIGN_ON policies and their rules.
+ """Fetches OKTA_SIGN_ON policies, rules, and brand sign-in pages.
Populates `self.global_session_policies` keyed by policy id. Each
policy carries its rules; downstream checks read directly from this
structure.
+
+ Also populates `self.sign_in_pages` keyed by brand id with sign-in page
+ HTML used by the DOD warning-banner check. When a brand has no
+ customized page, the service falls back to the default sign-in page
+ exposed by the Okta Management API and tracks it with
+ `is_customized=False`.
+
+ Before each fetch the service compares its required OAuth scope
+ (see `REQUIRED_SCOPES`) against the access token's granted scopes
+ (`provider.identity.granted_scopes`). When a scope is known to be
+ missing, the fetch is skipped and the resource is recorded in
+ `self.missing_scope` so checks can report the missing scope explicitly
+ instead of emitting a misleading "no resources returned" finding.
+ When granted_scopes is empty (token decode unavailable), the service
+ treats permissions as unknown and attempts the fetch — preserving
+ the prior behavior.
"""
def __init__(self, provider):
super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+
self.global_session_policies: dict[str, GlobalSessionPolicy] = (
- self._list_global_session_policies()
+ {}
+ if self.missing_scope["global_session_policies"]
+ else self._list_global_session_policies()
+ )
+ self.sign_in_pages: dict[str, SignInPage] = (
+ {} if self.missing_scope["sign_in_pages"] else self._list_sign_in_pages()
)
def _list_global_session_policies(self) -> dict:
@@ -125,35 +135,77 @@ class Signon(OktaService):
)
return rules_out
+ def _list_sign_in_pages(self) -> dict:
+ logger.info("Signon - Listing brand sign-in pages...")
+ try:
+ return self._run(self._fetch_brands_and_pages())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_brands_and_pages(self) -> dict:
+ result: dict[str, SignInPage] = {}
+ all_brands, err = await self._paginate(
+ lambda after: self.client.list_brands(after=after)
+ )
+ if err is not None:
+ logger.error(f"Error listing brands: {err}")
+ return result
+
+ for brand in all_brands:
+ brand_id = getattr(brand, "id", "") or ""
+ brand_name = getattr(brand, "name", "") or ""
+ result[brand_id] = await self._fetch_sign_in_page(brand_id, brand_name)
+ return result
+
+ async def _fetch_sign_in_page(self, brand_id: str, brand_name: str) -> "SignInPage":
+ page_result = await self.client.get_customized_sign_in_page(brand_id)
+ page_err = page_result[-1]
+ page_data = page_result[0]
+ if page_err is None:
+ return SignInPage(
+ brand_id=brand_id,
+ brand_name=brand_name,
+ is_customized=True,
+ page_content=getattr(page_data, "page_content", None),
+ )
+
+ if not self._is_missing_customized_page_error(page_err):
+ return SignInPage(
+ brand_id=brand_id,
+ brand_name=brand_name,
+ is_customized=False,
+ fetch_error=str(page_err),
+ )
+
+ default_page_result = await self.client.get_default_sign_in_page(brand_id)
+ default_page_err = default_page_result[-1]
+ default_page_data = default_page_result[0]
+ if default_page_err is not None:
+ return SignInPage(
+ brand_id=brand_id,
+ brand_name=brand_name,
+ is_customized=False,
+ fetch_error=str(default_page_err),
+ )
+
+ return SignInPage(
+ brand_id=brand_id,
+ brand_name=brand_name,
+ is_customized=False,
+ page_content=getattr(default_page_data, "page_content", None),
+ )
+
+ @staticmethod
+ def _is_missing_customized_page_error(error) -> bool:
+ err_text = str(error).lower()
+ return "404" in err_text or "not found" in err_text or "e0000007" in err_text
+
@staticmethod
async def _paginate(fetch):
- """Drain all pages of an SDK list call.
-
- `fetch` is a callable that takes the `after` cursor (or None for
- the first page) and returns the SDK's standard `(items, resp, err)`
- tuple. We follow `Link: rel="next"` headers until exhausted.
- """
- all_items = []
- result = await fetch(None)
- # Defensive against the SDK's 2-tuple early-error path: error is last.
- err = result[-1]
- if err is not None:
- return [], err
- items = result[0]
- resp = result[1] if len(result) >= 3 else None
- all_items.extend(items or [])
- while True:
- cursor = _next_after_cursor(resp)
- if not cursor:
- break
- result = await fetch(cursor)
- err = result[-1]
- if err is not None:
- return all_items, err
- items = result[0]
- resp = result[1] if len(result) >= 3 else None
- all_items.extend(items or [])
- return all_items, None
+ return await _paginate_shared(fetch)
class GlobalSessionPolicyRule(BaseModel):
@@ -176,3 +228,11 @@ class GlobalSessionPolicy(BaseModel):
status: str = ""
is_default: bool = False
rules: list[GlobalSessionPolicyRule] = []
+
+
+class SignInPage(BaseModel):
+ brand_id: str
+ brand_name: str = ""
+ is_customized: bool = False
+ page_content: Optional[str] = None
+ fetch_error: Optional[str] = None
diff --git a/prowler/providers/okta/services/systemlog/__init__.py b/prowler/providers/okta/services/systemlog/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/systemlog/lib/__init__.py b/prowler/providers/okta/services/systemlog/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/systemlog/lib/systemlog_helpers.py b/prowler/providers/okta/services/systemlog/lib/systemlog_helpers.py
new file mode 100644
index 0000000000..e82cedff5f
--- /dev/null
+++ b/prowler/providers/okta/services/systemlog/lib/systemlog_helpers.py
@@ -0,0 +1,26 @@
+"""Shared helpers for the OKTA systemlog STIG checks."""
+
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.systemlog.systemlog_service import LogStream
+
+
+def missing_log_streams_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding when the log-streams scope is not granted."""
+ placeholder = LogStream(
+ id="okta-log-streams-scope-missing",
+ name="(scope not granted)",
+ status="MISSING",
+ type="",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "Could not retrieve Okta Log Streams: the Okta service app is missing "
+ f"the required `{scope}` API scope. Grant it on the service app's "
+ "Okta API Scopes tab in the Okta Admin Console, then re-run the check."
+ )
+ return report
diff --git a/prowler/providers/okta/services/systemlog/systemlog_client.py b/prowler/providers/okta/services/systemlog/systemlog_client.py
new file mode 100644
index 0000000000..3dc0a1a0af
--- /dev/null
+++ b/prowler/providers/okta/services/systemlog/systemlog_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.systemlog.systemlog_service import SystemLog
+
+systemlog_client = SystemLog(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/systemlog/systemlog_service.py b/prowler/providers/okta/services/systemlog/systemlog_service.py
new file mode 100644
index 0000000000..96c8b6d7ae
--- /dev/null
+++ b/prowler/providers/okta/services/systemlog/systemlog_service.py
@@ -0,0 +1,136 @@
+from typing import Optional
+
+from pydantic import BaseModel, ValidationError
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate
+from prowler.providers.okta.lib.service.raw_fetch import (
+ get_json_paginated as raw_get_json_paginated,
+)
+from prowler.providers.okta.lib.service.service import OktaService
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "log_streams": "okta.logStreams.read",
+}
+
+
+class SystemLog(OktaService):
+ """Fetches Okta Log Stream configurations.
+
+ Populates `self.log_streams` keyed by Log Stream id. Each entry
+ carries `name`, `status`, `type` — enough for the streaming-enabled
+ check to evaluate whether the tenant has off-loaded audit records
+ to an external SIEM/event bus.
+
+ Required OAuth scopes (`REQUIRED_SCOPES`) are compared against the
+ access token's granted scopes (`provider.identity.granted_scopes`).
+ Missing scopes are recorded in `self.missing_scope` so the check
+ can emit an explicit MANUAL finding instead of a misleading
+ "no resources returned".
+ """
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+
+ self.log_streams: dict[str, LogStream] = (
+ {} if self.missing_scope["log_streams"] else self._list_log_streams()
+ )
+
+ def _list_log_streams(self) -> dict:
+ logger.info("SystemLog - Listing Okta Log Streams...")
+ try:
+ return self._run(self._fetch_log_streams())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_log_streams(self) -> dict:
+ result: dict[str, LogStream] = {}
+ try:
+ all_streams, err = await paginate(
+ lambda after: self.client.list_log_streams(after=after)
+ )
+ except ValidationError as ve:
+ # Upstream okta-sdk-python bug: e.g. `LogStreamSettingsAws`'s
+ # `eventSourceName` validator regex is `^[a-zA-Z0-9.\-_]$` —
+ # missing the `+` quantifier, so it rejects every
+ # multi-character name. Fall back to raw JSON so the check
+ # can still evaluate the tenant's actual log-stream state.
+ # Remove this workaround once okta-sdk-python fixes the
+ # validator (issue to be filed upstream).
+ logger.warning(
+ f"Okta SDK raised ValidationError parsing log streams "
+ f"({ve.error_count()} error(s)) — falling back to raw-JSON "
+ "parse. This is an okta-sdk-python deserialization bug."
+ )
+ return await self._fetch_log_streams_raw()
+
+ if err is not None:
+ logger.error(f"Error listing log streams: {err}")
+ return result
+
+ for stream in all_streams:
+ stream_id = getattr(stream, "id", "") or ""
+ if not stream_id:
+ continue
+ result[stream_id] = LogStream(
+ id=stream_id,
+ name=getattr(stream, "name", "") or "",
+ status=getattr(stream, "status", "") or "",
+ type=_stringify_enum(getattr(stream, "type", None)) or "",
+ )
+ return result
+
+ async def _fetch_log_streams_raw(self) -> dict:
+ """Raw-JSON fallback for `list_log_streams`.
+
+ Bypasses the SDK's typed deserialization via the shared
+ `get_json_paginated` helper (which follows the `Link: rel=next`
+ cursor so tenants with >200 streams are not silently truncated),
+ and projects the response onto our own pydantic snapshot which
+ only validates the four fields the check reads. Keeps the check
+ evaluable on tenants whose Log Stream settings happen to trip
+ an SDK enum/regex validator.
+ """
+ result: dict[str, LogStream] = {}
+ data = await raw_get_json_paginated(
+ self.client,
+ "/api/v1/logStreams",
+ page_size=200,
+ context="log streams",
+ )
+ if data is None:
+ return result
+ for item in data:
+ if not isinstance(item, dict):
+ continue
+ stream_id = item.get("id")
+ if not stream_id:
+ continue
+ result[stream_id] = LogStream(
+ id=stream_id,
+ name=item.get("name") or "",
+ status=(item.get("status") or "").upper(),
+ type=item.get("type") or "",
+ )
+ return result
+
+
+def _stringify_enum(value) -> Optional[str]:
+ if value is None:
+ return None
+ return getattr(value, "value", None) or str(value)
+
+
+class LogStream(BaseModel):
+ id: str
+ name: str = ""
+ status: str = ""
+ type: str = ""
diff --git a/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/__init__.py b/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.metadata.json b/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.metadata.json
new file mode 100644
index 0000000000..27541ee2fe
--- /dev/null
+++ b/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "okta",
+ "CheckID": "systemlog_streaming_enabled",
+ "CheckTitle": "Okta off-loads audit records to a central log server via Log Streaming",
+ "CheckType": [],
+ "ServiceName": "systemlog",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "monitoring",
+ "Description": "Okta must off-load audit records to a central log server. At least one **Log Stream** (AWS EventBridge, Splunk Cloud, etc.) must be configured and `ACTIVE` in the tenant. Alternatively, an external SIEM pulling the System Log API can satisfy the requirement, but that pull-based path is verified manually.",
+ "Risk": "Audit records stored only inside the Okta tenant are exposed to accidental or incidental deletion or alteration.\n\n- **No central retention** of authentication events for incident investigations\n- **Single point of failure** for the audit trail\n- **No correlation** with other identity, network, and endpoint telemetry in the SIEM",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/en-us/content/topics/reports/log-streaming/about-log-streams.htm",
+ "https://developer.okta.com/docs/api/openapi/okta-management/management/tag/LogStream/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Reports** > **Log Streaming**.\n3. Click **Add Log Stream** and select **AWS EventBridge**, **Splunk Cloud**, or another supported destination.\n4. Complete the connection fields and save.\n5. Activate the stream and verify the destination receives events.\n6. If the destination SIEM is not natively supported, document the pull-based ingestion that uses the System Log API.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure at least one ACTIVE Okta Log Stream that off-loads audit records to a central SIEM (AWS EventBridge, Splunk Cloud, or another supported destination). Document any alternative pull-based ingestion via the System Log API.",
+ "Url": "https://hub.prowler.com/check/systemlog_streaming_enabled"
+ }
+ },
+ "Categories": [
+ "logging"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273202 / OKTA-APP-001430."
+}
diff --git a/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.py b/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.py
new file mode 100644
index 0000000000..61448aeaf5
--- /dev/null
+++ b/prowler/providers/okta/services/systemlog/systemlog_streaming_enabled/systemlog_streaming_enabled.py
@@ -0,0 +1,88 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.systemlog.lib.systemlog_helpers import (
+ missing_log_streams_scope_finding,
+)
+from prowler.providers.okta.services.systemlog.systemlog_client import systemlog_client
+from prowler.providers.okta.services.systemlog.systemlog_service import LogStream
+
+
+class systemlog_streaming_enabled(Check):
+ """Verifies that at least one Okta Log Stream is configured and active.
+
+ Off-loading audit records to a central SIEM (AWS EventBridge, Splunk
+ Cloud, etc.) is the standard mechanism for centralised retention.
+ An alternative path — pulling the System Log API into an external
+ SIEM — is allowed by the requirement, but cannot be verified
+ automatically; this check emits a MANUAL note in that case.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ org_domain = systemlog_client.provider.identity.org_domain
+
+ missing_scope = systemlog_client.missing_scope.get("log_streams")
+ if missing_scope:
+ findings.append(
+ missing_log_streams_scope_finding(
+ self.metadata(), org_domain, missing_scope
+ )
+ )
+ return findings
+
+ active_streams = [
+ stream
+ for stream in systemlog_client.log_streams.values()
+ if not stream.status or stream.status.upper() == "ACTIVE"
+ ]
+
+ if not systemlog_client.log_streams:
+ placeholder = LogStream(
+ id="okta-log-streams-missing",
+ name="(no Log Streams configured)",
+ status="MISSING",
+ type="",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=placeholder, org_domain=org_domain
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ "No Okta Log Streams are configured. Configure a Log Stream "
+ "(Reports > Log Streaming) to off-load audit records to a "
+ "central SIEM. If an external SIEM is already pulling logs "
+ "via the System Log API, mutelist this check with that "
+ "evidence."
+ )
+ findings.append(report)
+ return findings
+
+ if not active_streams:
+ placeholder = LogStream(
+ id="okta-log-streams-inactive",
+ name="(no active Log Streams)",
+ status="INACTIVE",
+ type="",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=placeholder, org_domain=org_domain
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ f"{len(systemlog_client.log_streams)} Okta Log Stream(s) are "
+ "configured but none are ACTIVE. Activate a Log Stream to "
+ "off-load audit records to a central SIEM."
+ )
+ findings.append(report)
+ return findings
+
+ for stream in active_streams:
+ report = CheckReportOkta(
+ metadata=self.metadata(), resource=stream, org_domain=org_domain
+ )
+ report.status = "PASS"
+ report.status_extended = (
+ f"Okta Log Stream '{stream.name}' (type={stream.type or 'unset'}) "
+ "is ACTIVE and off-loads audit records to a central SIEM."
+ )
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/okta/services/user/__init__.py b/prowler/providers/okta/services/user/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/user/lib/__init__.py b/prowler/providers/okta/services/user/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/user/lib/user_helpers.py b/prowler/providers/okta/services/user/lib/user_helpers.py
new file mode 100644
index 0000000000..423801f2d8
--- /dev/null
+++ b/prowler/providers/okta/services/user/lib/user_helpers.py
@@ -0,0 +1,26 @@
+"""Shared helpers for the OKTA user STIG checks."""
+
+from prowler.lib.check.models import CheckReportOkta
+from prowler.providers.okta.services.user.user_service import UserAutomation
+
+
+def missing_user_scope_finding(
+ metadata, org_domain: str, scope: str
+) -> CheckReportOkta:
+ """Build the MANUAL finding when an OAuth scope is not granted."""
+ placeholder = UserAutomation(
+ id="okta-user-scope-missing",
+ name="(scope not granted)",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=metadata, resource=placeholder, org_domain=org_domain
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not retrieve Okta user lifecycle automations: the Okta service "
+ f"app is missing the required `{scope}` API scope. Grant it on the "
+ "service app's Okta API Scopes tab in the Okta Admin Console, then "
+ "re-run the check."
+ )
+ return report
diff --git a/prowler/providers/okta/services/user/user_client.py b/prowler/providers/okta/services/user/user_client.py
new file mode 100644
index 0000000000..9a49fbdbac
--- /dev/null
+++ b/prowler/providers/okta/services/user/user_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.okta.services.user.user_service import User
+
+user_client = User(Provider.get_global_provider())
diff --git a/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/__init__.py b/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.metadata.json b/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.metadata.json
new file mode 100644
index 0000000000..64f24d95ae
--- /dev/null
+++ b/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.metadata.json
@@ -0,0 +1,36 @@
+{
+ "Provider": "okta",
+ "CheckID": "user_inactivity_automation_35d_enabled",
+ "CheckTitle": "Okta automation suspends or deactivates users after 35 days of inactivity",
+ "CheckType": [],
+ "ServiceName": "user",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "An Okta **Workflows Automation** must disable inactive user accounts. The automation must be `ACTIVE`, on an `ACTIVE` schedule, evaluate `User Inactivity = 35 days` (or less), apply to a group covering every user, and trigger `Suspended` / `Deactivated` / `Deprovisioned`. Threshold override: `okta_user_inactivity_max_days`. N/A when user sourcing is delegated to Active Directory or LDAP.",
+ "Risk": "Inactive Okta accounts retained indefinitely give an attacker who exploits one undetected access to downstream applications.\n\n- **Account takeover via dormant identities** that no one is monitoring\n- **Lateral movement** through SSO sessions of forgotten users\n- **Stale entitlements** that survive role and policy reorganisations",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://help.okta.com/en-us/content/topics/automation-hooks/automations-main.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. Sign in to the **Okta Admin Console** as a *Super Admin*.\n2. Navigate to **Workflow** > **Automations** and click **Add Automation**.\n3. Name the automation (e.g., `User Inactivity`).\n4. Add a condition: select **User Inactivity in Okta** and enter `35` days.\n5. Configure the schedule to run daily and activate it.\n6. Apply the automation to a group that covers every user — typically `Everyone`.\n7. Add an action: **Change User lifecycle state in Okta** and choose `Suspended` (or `Deactivated`/`Deprovisioned`).\n8. Activate the automation.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Create an active Okta Workflows automation that runs daily, evaluates `User Inactivity in Okta = 35 days`, applies to a group covering every user, and changes the user lifecycle state to Suspended/Deactivated. If user sourcing is delegated to Active Directory or LDAP, document that the connected directory enforces this requirement instead.",
+ "Url": "https://hub.prowler.com/check/user_inactivity_automation_35d_enabled"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Aligns with DISA STIG V-273188 / OKTA-APP-000090."
+}
diff --git a/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.py b/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.py
new file mode 100644
index 0000000000..79e77c3f73
--- /dev/null
+++ b/prowler/providers/okta/services/user/user_inactivity_automation_35d_enabled/user_inactivity_automation_35d_enabled.py
@@ -0,0 +1,204 @@
+from prowler.lib.check.models import Check, CheckReportOkta
+from prowler.providers.okta.services.user.lib.user_helpers import (
+ missing_user_scope_finding,
+)
+from prowler.providers.okta.services.user.user_client import user_client
+from prowler.providers.okta.services.user.user_service import UserAutomation
+
+DEFAULT_INACTIVITY_DAYS = 35
+SUSPENSION_LIFECYCLE_ACTIONS = {"SUSPENDED", "DEACTIVATED", "DEPROVISIONED"}
+
+
+class user_inactivity_automation_35d_enabled(Check):
+ """Verifies that Okta suspends/deactivates users after 35 days of inactivity.
+
+ A Workflows Automation must exist with:
+ - status ACTIVE,
+ - schedule active,
+ - condition `User Inactivity in Okta = 35 days`,
+ - action that changes the user state to Suspended / Deactivated,
+ - applied to a group covering every user (typically `Everyone`).
+
+ When user sourcing is delegated to an external directory (Active
+ Directory or LDAP), the requirement is N/A on the Okta side — the
+ connected directory is expected to enforce inactivity-based
+ deactivation instead. Threshold override:
+ `okta_user_inactivity_max_days` in the audit config.
+ """
+
+ def execute(self) -> list[CheckReportOkta]:
+ findings: list[CheckReportOkta] = []
+ audit_config = user_client.audit_config or {}
+ threshold_days = audit_config.get(
+ "okta_user_inactivity_max_days", DEFAULT_INACTIVITY_DAYS
+ )
+ org_domain = user_client.provider.identity.org_domain
+
+ for scope_key in ("automations", "identity_providers"):
+ missing_scope = user_client.missing_scope.get(scope_key)
+ if missing_scope:
+ findings.append(
+ missing_user_scope_finding(
+ self.metadata(), org_domain, missing_scope
+ )
+ )
+ return findings
+
+ # External-directory N/A path.
+ if user_client.external_directory_idps:
+ idp_names = ", ".join(
+ f"'{idp.name}' (type={idp.type})"
+ for idp in user_client.external_directory_idps.values()
+ )
+ placeholder = UserAutomation(
+ id="okta-user-inactivity-na-external-directory",
+ name="(external directory enforces inactivity)",
+ status="N/A",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=placeholder,
+ org_domain=org_domain,
+ )
+ report.status = "MANUAL"
+ report.status_extended = (
+ "User sourcing is delegated to an external directory "
+ f"({idp_names}). The 35-day inactivity disable requirement is "
+ "expected to be enforced by the connected directory rather "
+ "than by an Okta automation. Confirm out-of-band that the "
+ "external directory disables accounts after "
+ f"{threshold_days} days of inactivity."
+ )
+ findings.append(report)
+ return findings
+
+ compliant_automations = [
+ automation
+ for automation in user_client.automations.values()
+ if _is_compliant(automation, threshold_days)
+ ]
+
+ if not user_client.automations:
+ placeholder = UserAutomation(
+ id="okta-user-inactivity-no-automations",
+ name="(no automations configured)",
+ status="MISSING",
+ )
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=placeholder,
+ org_domain=org_domain,
+ )
+ report.status = "FAIL"
+ report.status_extended = (
+ "No Okta Workflows automations are configured. Create an "
+ "automation that suspends or deactivates users after "
+ f"{threshold_days} days of inactivity, scoped to a group "
+ "covering every user (typically 'Everyone'), with an active "
+ "schedule."
+ )
+ findings.append(report)
+ return findings
+
+ if compliant_automations:
+ for automation in compliant_automations:
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=automation,
+ org_domain=org_domain,
+ )
+ report.status = "PASS"
+ groups_label = ", ".join(automation.applies_to_groups)
+ report.status_extended = (
+ f"Okta automation '{automation.name}' is ACTIVE with an "
+ f"active schedule, triggers after "
+ f"{automation.inactivity_days} days of inactivity, and "
+ f"changes the user state to "
+ f"{automation.lifecycle_action or 'unset'}. "
+ f"Applied to group(s): {groups_label}. Verify that these "
+ "group(s) cover every user. Okta has no built-in "
+ "'Everyone' group ID, so tenant-wide coverage cannot be "
+ "asserted automatically."
+ )
+ findings.append(report)
+ return findings
+
+ # Automations exist but none satisfy the predicate — surface the
+ # closest candidate for the auditor.
+ candidate = _closest_candidate(user_client.automations.values())
+ report = CheckReportOkta(
+ metadata=self.metadata(),
+ resource=candidate
+ or UserAutomation(
+ id="okta-user-inactivity-noncompliant",
+ name="(no compliant automation)",
+ status="MISSING",
+ ),
+ org_domain=org_domain,
+ )
+ report.status = "FAIL"
+ report.status_extended = _failure_message(candidate, threshold_days)
+ findings.append(report)
+ return findings
+
+
+def _is_compliant(automation: UserAutomation, threshold_days: int) -> bool:
+ # `applies_to_groups` must be non-empty — Okta USER_LIFECYCLE policies
+ # do not implicitly cover every user; the scope is whatever group IDs
+ # the operator put in `people.groups.include`. An empty scope means
+ # the automation runs against nobody. Operator must still verify those
+ # group(s) cover the intended user population (surfaced in the PASS
+ # status_extended).
+ return bool(
+ automation.status.upper() == "ACTIVE"
+ and automation.schedule_status.upper() == "ACTIVE"
+ and automation.inactivity_days is not None
+ and automation.inactivity_days <= threshold_days
+ and (automation.lifecycle_action or "").upper() in SUSPENSION_LIFECYCLE_ACTIONS
+ and bool(automation.applies_to_groups)
+ )
+
+
+def _closest_candidate(automations):
+ automations = list(automations)
+ if not automations:
+ return None
+ automations.sort(
+ key=lambda a: (
+ 0 if a.status.upper() == "ACTIVE" else 1,
+ 0 if a.schedule_status.upper() == "ACTIVE" else 1,
+ (
+ abs(a.inactivity_days - DEFAULT_INACTIVITY_DAYS)
+ if a.inactivity_days is not None
+ else 10_000
+ ),
+ a.name,
+ )
+ )
+ return automations[0]
+
+
+def _failure_message(automation, threshold_days):
+ if automation is None:
+ return f"No Okta automation enforces {threshold_days}-day inactivity disable."
+ issues = []
+ if automation.status.upper() != "ACTIVE":
+ issues.append(f"status {automation.status or 'unset'}")
+ if automation.schedule_status.upper() != "ACTIVE":
+ issues.append(f"schedule {automation.schedule_status or 'unset'}")
+ if automation.inactivity_days is None:
+ issues.append("no inactivity condition")
+ elif automation.inactivity_days > threshold_days:
+ issues.append(
+ f"inactivity {automation.inactivity_days}d (max {threshold_days}d)"
+ )
+ action = (automation.lifecycle_action or "").upper()
+ if action not in SUSPENSION_LIFECYCLE_ACTIONS:
+ issues.append(f"action {automation.lifecycle_action or 'unset'}")
+ if not automation.applies_to_groups:
+ issues.append("no group scope")
+ detail = ", ".join(issues) if issues else "incomplete"
+ return (
+ f"Okta automation '{automation.name}' fails {threshold_days}d "
+ f"inactivity: {detail}."
+ )
diff --git a/prowler/providers/okta/services/user/user_service.py b/prowler/providers/okta/services/user/user_service.py
new file mode 100644
index 0000000000..c816bd38ee
--- /dev/null
+++ b/prowler/providers/okta/services/user/user_service.py
@@ -0,0 +1,455 @@
+from typing import Optional
+
+from pydantic import BaseModel, ValidationError
+
+from prowler.lib.logger import logger
+from prowler.providers.okta.lib.service.pagination import paginate
+from prowler.providers.okta.lib.service.raw_fetch import (
+ get_json_paginated as raw_get_json_paginated,
+)
+from prowler.providers.okta.lib.service.service import OktaService
+
+# External-directory IdP `type` values that delegate user sourcing to a
+# separate identity store. When any of these is present and ACTIVE, the
+# STIG's 35-day inactivity disable requirement is N/A on the Okta side —
+# the connected directory is expected to enforce it instead.
+EXTERNAL_DIRECTORY_IDP_TYPES = {"ACTIVE_DIRECTORY", "LDAP"}
+
+# Okta exposes "Workflow > Automations" as USER_LIFECYCLE policies with
+# inactivity rule conditions, not as a standalone `/api/v1/automations`
+# resource. The SDK's `UserPolicyRuleCondition.inactivity` and
+# `ScheduledUserLifecycleAction` models confirm this; the API rejects
+# every other `type` candidate.
+USER_LIFECYCLE_POLICY_TYPE = "USER_LIFECYCLE"
+
+REQUIRED_SCOPES: dict[str, str] = {
+ "automations": "okta.policies.read",
+ "identity_providers": "okta.idps.read",
+}
+
+
+class User(OktaService):
+ """Fetches Okta User Lifecycle Automations and external-directory IdPs.
+
+ Populates:
+ - `self.automations` — keyed by USER_LIFECYCLE policy rule id. Each
+ entry projects the fields the 35-day inactivity check evaluates:
+ identity (`id`, `name` — taken from the rule), `status`,
+ `schedule_status` (inherited from the parent policy), the
+ `inactivity_days` condition and `applies_to_groups` scope from the
+ parent policy, and the `lifecycle_action` from the rule.
+ - `self.external_directory_idps` — keyed by IdP id. Used to short
+ circuit the STIG to N/A when user sourcing is delegated to an
+ external directory (Active Directory, LDAP).
+
+ The Okta Admin Console's "Workflow > Automations" page is rendered
+ on top of `USER_LIFECYCLE` policies in the Management API
+ (`list_policies(type='USER_LIFECYCLE')` + `list_policy_rules(...)`).
+ There is no standalone `/api/v1/automations` GET endpoint; the SDK's
+ `InactivityPolicyRuleCondition`, `UserPolicyRuleCondition`, and
+ `ScheduledUserLifecycleAction` models all hang off the policy API.
+
+ Required OAuth scopes (`REQUIRED_SCOPES`) are compared against the
+ access token's granted scopes (`provider.identity.granted_scopes`).
+ Missing scopes are recorded in `self.missing_scope` so the check
+ can emit an explicit MANUAL finding.
+ """
+
+ def __init__(self, provider):
+ super().__init__(__class__.__name__, provider)
+ granted = set(getattr(provider.identity, "granted_scopes", None) or [])
+ self.missing_scope: dict[str, Optional[str]] = {
+ resource: (scope if granted and scope not in granted else None)
+ for resource, scope in REQUIRED_SCOPES.items()
+ }
+
+ self.automations: dict[str, UserAutomation] = (
+ {} if self.missing_scope["automations"] else self._list_automations()
+ )
+ self.external_directory_idps: dict[str, ExternalDirectoryIdp] = (
+ {}
+ if self.missing_scope["identity_providers"]
+ else self._list_external_directory_idps()
+ )
+
+ def _list_automations(self) -> dict:
+ logger.info("User - Listing USER_LIFECYCLE policies and rules...")
+ try:
+ return self._run(self._fetch_automations())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_automations(self) -> dict:
+ result: dict[str, UserAutomation] = {}
+ try:
+ all_policies, err = await paginate(
+ lambda after: self.client.list_policies(
+ type=USER_LIFECYCLE_POLICY_TYPE, after=after
+ )
+ )
+ except (ValueError, ValidationError) as ex:
+ # Upstream okta-sdk-python bug: `Policy.from_dict` uses a
+ # discriminator dispatch that maps `type` → concrete Policy
+ # subclass, and `USER_LIFECYCLE` is not in the map. The SDK
+ # raises ValueError ("failed to lookup discriminator value")
+ # even though the API returns a valid policy. Fall back to
+ # raw JSON. Remove once okta-sdk-python adds
+ # USER_LIFECYCLE → UserLifecyclePolicy to the mapping.
+ logger.warning(
+ f"Okta SDK raised {type(ex).__name__} parsing USER_LIFECYCLE "
+ "policies — falling back to raw-JSON parse. This is an "
+ "okta-sdk-python deserialization bug "
+ "(missing discriminator mapping)."
+ )
+ return await self._fetch_automations_raw()
+
+ if err is not None:
+ logger.error(f"Error listing USER_LIFECYCLE policies: {err}")
+ return result
+
+ for policy in all_policies:
+ policy_id = getattr(policy, "id", "") or ""
+ if not policy_id:
+ continue
+ policy_status = _stringify_enum(getattr(policy, "status", None)) or ""
+ policy_name = getattr(policy, "name", "") or ""
+ rules = await self._fetch_rules(policy_id)
+ if rules is None:
+ # Rule typed parsing tripped an SDK validator. Re-run the
+ # whole automation discovery via raw JSON so we don't lose
+ # the rule data for this — or any other — policy. Cheaper
+ # than mixing typed and raw projections.
+ logger.warning(
+ f"Rule typed parsing failed for USER_LIFECYCLE policy "
+ f"{policy_id} — re-running all automations via raw-JSON."
+ )
+ return await self._fetch_automations_raw()
+ if not rules:
+ # A policy with no rules exists in the Admin Console UI as
+ # an "Automation" the operator hasn't finished configuring
+ # (no conditions, no actions). Emit a placeholder so the
+ # check FAILs with a specific message naming every missing
+ # piece, instead of pretending the policy doesn't exist.
+ result[policy_id] = _shell_automation(
+ policy_id, policy_name, policy_status
+ )
+ continue
+ for rule in rules:
+ automation = _rule_to_automation(rule, policy)
+ if automation is None:
+ continue
+ result[automation.id] = automation
+ return result
+
+ async def _fetch_rules(self, policy_id: str) -> Optional[list]:
+ """Return the policy's typed rules, or None to signal raw fallback.
+
+ The Okta SDK's `list_policy_rules` shares the same brittle typed
+ deserialization as `list_policies` (strict pydantic validators
+ rejecting values the API actually returns). When that happens the
+ caller can't reuse any of the typed projection for this policy —
+ we return None as a sentinel and the caller re-runs the whole
+ discovery via `_fetch_automations_raw`. Returning `[]` would
+ otherwise misclassify the policy as an "unfinished automation"
+ and FAIL it.
+ """
+ rule_fetch_limit = 100
+ try:
+ result = await self.client.list_policy_rules(
+ policy_id, limit=str(rule_fetch_limit)
+ )
+ except (ValueError, ValidationError) as ex:
+ logger.warning(
+ f"Okta SDK raised {type(ex).__name__} parsing rules for "
+ f"USER_LIFECYCLE policy {policy_id} — signaling raw fallback."
+ )
+ return None
+ err = result[-1]
+ if err is not None:
+ logger.error(
+ f"Error listing rules for USER_LIFECYCLE policy {policy_id}: {err}"
+ )
+ return []
+ rules = list(result[0] or [])
+ if len(rules) >= rule_fetch_limit:
+ logger.warning(
+ f"USER_LIFECYCLE policy {policy_id} returned {len(rules)} rules — "
+ f"the per-policy fetch limit ({rule_fetch_limit}) was hit; any "
+ "rules beyond this limit are not evaluated."
+ )
+ return rules
+
+ async def _fetch_automations_raw(self) -> dict:
+ """Raw-JSON fallback for `list_policies(type='USER_LIFECYCLE')`.
+
+ Bypasses the SDK's typed deserialization via the shared
+ `get_json_paginated` helper, then drains each policy's rules
+ via the same path. Projects everything onto our `UserAutomation`
+ snapshot which only validates the fields the check reads.
+ """
+ result: dict[str, UserAutomation] = {}
+ policies_data = await raw_get_json_paginated(
+ self.client,
+ f"/api/v1/policies?type={USER_LIFECYCLE_POLICY_TYPE}",
+ page_size=200,
+ context="USER_LIFECYCLE policies",
+ )
+ if policies_data is None:
+ return result
+
+ for policy_dict in policies_data:
+ if not isinstance(policy_dict, dict):
+ continue
+ policy_id = policy_dict.get("id")
+ if not policy_id:
+ continue
+ policy_status = (policy_dict.get("status") or "").upper()
+ policy_name = policy_dict.get("name") or ""
+
+ rules_data = await raw_get_json_paginated(
+ self.client,
+ f"/api/v1/policies/{policy_id}/rules",
+ page_size=100,
+ context=f"USER_LIFECYCLE policy {policy_id} rules",
+ )
+ if not rules_data:
+ # No rules under the policy → emit placeholder. Same
+ # rationale as the typed path: surface the unfinished
+ # automation so the check can name what's missing.
+ result[policy_id] = _shell_automation(
+ policy_id, policy_name, policy_status
+ )
+ continue
+ for rule_dict in rules_data:
+ automation = _raw_rule_to_automation(
+ rule_dict, policy_dict, policy_id, policy_name, policy_status
+ )
+ if automation is None:
+ continue
+ result[automation.id] = automation
+ return result
+
+ def _list_external_directory_idps(self) -> dict:
+ logger.info("User - Listing Okta IdPs for external-directory detection...")
+ try:
+ return self._run(self._fetch_external_directory_idps())
+ except Exception as error:
+ logger.error(
+ f"{error.__class__.__name__}[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ return {}
+
+ async def _fetch_external_directory_idps(self) -> dict:
+ result: dict[str, ExternalDirectoryIdp] = {}
+ all_idps, err = await paginate(
+ lambda after: self.client.list_identity_providers(after=after)
+ )
+ if err is not None:
+ logger.error(f"Error listing identity providers: {err}")
+ return result
+
+ for idp in all_idps:
+ idp_type = _stringify_enum(getattr(idp, "type", None)) or ""
+ if idp_type.upper() not in EXTERNAL_DIRECTORY_IDP_TYPES:
+ continue
+ idp_status = _stringify_enum(getattr(idp, "status", None)) or ""
+ if idp_status.upper() != "ACTIVE":
+ continue
+ idp_id = getattr(idp, "id", "") or ""
+ if not idp_id:
+ continue
+ result[idp_id] = ExternalDirectoryIdp(
+ id=idp_id,
+ name=getattr(idp, "name", "") or "",
+ type=idp_type,
+ status=idp_status,
+ )
+ return result
+
+
+def _rule_to_automation(rule, policy) -> Optional["UserAutomation"]:
+ """Project a typed USER_LIFECYCLE policy + rule pair onto our snapshot.
+
+ Important: in the actual API response, an Okta "Automation" is split
+ across two resources — the **inactivity condition + group scope**
+ live on the *policy* (`policy.conditions.people.users.inactivity`,
+ `policy.conditions.people.groups.include`), and the **lifecycle
+ action** lives on the *rule* (`rule.actions.user_lifecycle.action`
+ on the typed model; `updateUserLifecycle.targetStatus` on raw JSON).
+ The rule's own `conditions` is typically empty. Projecting requires
+ both — kept aligned with `_raw_rule_to_automation` so the two paths
+ yield identical snapshots.
+ """
+ rule_id = getattr(rule, "id", "") or ""
+ if not rule_id:
+ return None
+
+ policy_id = getattr(policy, "id", "") or ""
+ policy_name = getattr(policy, "name", "") or ""
+ policy_status = (_stringify_enum(getattr(policy, "status", None)) or "").upper()
+
+ # Inactivity + groups live on the POLICY in the API response.
+ inactivity_days: Optional[int] = None
+ applies_to_groups: list[str] = []
+ conditions = getattr(policy, "conditions", None)
+ people = getattr(conditions, "people", None) if conditions else None
+ users = getattr(people, "users", None) if people else None
+ inactivity = getattr(users, "inactivity", None) if users else None
+ if inactivity is not None:
+ number = getattr(inactivity, "number", None)
+ unit = (_stringify_enum(getattr(inactivity, "unit", None)) or "").upper()
+ if isinstance(number, int) and unit in {"DAYS", "DAY"}:
+ inactivity_days = number
+ groups = getattr(people, "groups", None) if people else None
+ include_groups = getattr(groups, "include", None) if groups else None
+ if include_groups:
+ applies_to_groups = [str(g) for g in include_groups if g]
+
+ # Lifecycle action lives on the RULE.
+ actions = getattr(rule, "actions", None)
+ user_lifecycle = (
+ getattr(actions, "user_lifecycle", None) if actions else None
+ ) or (getattr(actions, "userLifecycle", None) if actions else None)
+ lifecycle_action: Optional[str] = None
+ if user_lifecycle is not None:
+ for attr in ("action", "status"):
+ value = _stringify_enum(getattr(user_lifecycle, attr, None))
+ if value:
+ lifecycle_action = value.upper()
+ break
+
+ rule_name = getattr(rule, "name", "") or policy_name or "(unnamed)"
+ rule_status = _stringify_enum(getattr(rule, "status", None)) or ""
+
+ return UserAutomation(
+ id=rule_id,
+ name=rule_name,
+ status=rule_status.upper(),
+ schedule_status=policy_status,
+ inactivity_days=inactivity_days,
+ lifecycle_action=lifecycle_action,
+ applies_to_groups=applies_to_groups,
+ policy_id=policy_id,
+ policy_name=policy_name,
+ )
+
+
+def _raw_rule_to_automation(
+ rule_dict,
+ policy_dict,
+ policy_id: str,
+ policy_name: str,
+ policy_status: str,
+) -> Optional["UserAutomation"]:
+ """Project a raw USER_LIFECYCLE policy+rule pair onto our snapshot.
+
+ Important: in the actual API response, an Okta "Automation" is split
+ across two resources — the **inactivity condition + group scope**
+ live on the *policy* (`policy.conditions.people.users.inactivity`,
+ `policy.conditions.people.groups.include`), and the **lifecycle
+ action** lives on the *rule*
+ (`rule.actions.updateUserLifecycle.targetStatus`). The rule's own
+ `conditions` is typically empty `{}`. Projecting requires both.
+
+ Schedule isn't exposed by the API on either resource. Okta runs an
+ automation on its UI-configured schedule iff the policy is ACTIVE,
+ so we treat `policy.status` as the schedule proxy.
+ """
+ if not isinstance(rule_dict, dict):
+ return None
+ rule_id = rule_dict.get("id")
+ if not rule_id:
+ return None
+
+ # Inactivity + groups live on the POLICY in the API response.
+ inactivity_days: Optional[int] = None
+ applies_to_groups: list[str] = []
+ if isinstance(policy_dict, dict):
+ policy_conditions = policy_dict.get("conditions") or {}
+ people = policy_conditions.get("people") or {}
+ users = people.get("users") or {}
+ inactivity = users.get("inactivity")
+ if isinstance(inactivity, dict):
+ number = inactivity.get("number")
+ unit = (inactivity.get("unit") or "").upper()
+ if isinstance(number, int) and unit in {"DAYS", "DAY"}:
+ inactivity_days = number
+ groups = people.get("groups") or {}
+ include_groups = groups.get("include")
+ if isinstance(include_groups, list):
+ applies_to_groups = [str(g) for g in include_groups if g]
+
+ # Lifecycle action lives on the RULE under
+ # `actions.updateUserLifecycle.targetStatus` (the API uses
+ # "updateUserLifecycle" rather than the SDK's `user_lifecycle`).
+ rule_actions = rule_dict.get("actions") or {}
+ update_user_lifecycle = rule_actions.get("updateUserLifecycle") or {}
+ lifecycle_action: Optional[str] = None
+ if isinstance(update_user_lifecycle, dict):
+ target = update_user_lifecycle.get("targetStatus")
+ if isinstance(target, str) and target:
+ lifecycle_action = target.upper()
+
+ return UserAutomation(
+ id=rule_id,
+ name=(rule_dict.get("name") or policy_name or "(unnamed)"),
+ status=(rule_dict.get("status") or "").upper(),
+ schedule_status=policy_status,
+ inactivity_days=inactivity_days,
+ lifecycle_action=lifecycle_action,
+ applies_to_groups=applies_to_groups,
+ policy_id=policy_id,
+ policy_name=policy_name,
+ )
+
+
+def _shell_automation(
+ policy_id: str, policy_name: str, policy_status: str
+) -> "UserAutomation":
+ """Placeholder UserAutomation for a USER_LIFECYCLE policy with no rules.
+
+ Surfaces the unfinished automation in `self.automations` so the check
+ can list every missing piece in its FAIL message (no inactivity
+ condition, no lifecycle action, status inactive, etc.) instead of
+ silently dropping the policy.
+ """
+ upper_status = (policy_status or "").upper()
+ return UserAutomation(
+ id=policy_id,
+ name=policy_name or "(unnamed automation)",
+ status=upper_status,
+ schedule_status=upper_status,
+ inactivity_days=None,
+ lifecycle_action=None,
+ applies_to_groups=[],
+ policy_id=policy_id,
+ policy_name=policy_name,
+ )
+
+
+def _stringify_enum(value) -> Optional[str]:
+ if value is None:
+ return None
+ return getattr(value, "value", None) or str(value)
+
+
+class UserAutomation(BaseModel):
+ id: str
+ name: str = ""
+ status: str = ""
+ schedule_status: str = ""
+ inactivity_days: Optional[int] = None
+ lifecycle_action: Optional[str] = None
+ applies_to_groups: list[str] = []
+ policy_id: str = ""
+ policy_name: str = ""
+
+
+class ExternalDirectoryIdp(BaseModel):
+ id: str
+ name: str = ""
+ type: str = ""
+ status: str = ""
diff --git a/prowler/providers/openstack/exceptions/exceptions.py b/prowler/providers/openstack/exceptions/exceptions.py
index c78e35c475..f5b7dc9a7d 100644
--- a/prowler/providers/openstack/exceptions/exceptions.py
+++ b/prowler/providers/openstack/exceptions/exceptions.py
@@ -1,56 +1,56 @@
from prowler.exceptions.exceptions import ProwlerException
-# Exceptions codes from 10000 to 10999 are reserved for OpenStack exceptions
+# Exceptions codes from 17000 to 17999 are reserved for OpenStack exceptions
class OpenStackBaseException(ProwlerException):
"""Base class for OpenStack Errors."""
OPENSTACK_ERROR_CODES = {
- (10000, "OpenStackCredentialsError"): {
+ (17000, "OpenStackCredentialsError"): {
"message": "OpenStack credentials not found or invalid",
"remediation": "Check the OpenStack API credentials and ensure they are properly set.",
},
- (10001, "OpenStackAuthenticationError"): {
+ (17001, "OpenStackAuthenticationError"): {
"message": "OpenStack authentication failed",
"remediation": "Check the OpenStack API credentials and ensure they are valid.",
},
- (10002, "OpenStackSessionError"): {
+ (17002, "OpenStackSessionError"): {
"message": "OpenStack session setup failed",
"remediation": "Check the session setup and ensure it is properly configured.",
},
- (10003, "OpenStackIdentityError"): {
+ (17003, "OpenStackIdentityError"): {
"message": "OpenStack identity setup failed",
"remediation": "Check credentials and ensure they are properly set up for OpenStack.",
},
- (10004, "OpenStackAPIError"): {
+ (17004, "OpenStackAPIError"): {
"message": "OpenStack API call failed",
"remediation": "Check the API request and ensure it is properly formatted.",
},
- (10005, "OpenStackRateLimitError"): {
+ (17005, "OpenStackRateLimitError"): {
"message": "OpenStack API rate limit exceeded",
"remediation": "Reduce the number of API requests or wait before making more requests.",
},
- (10006, "OpenStackConfigFileNotFoundError"): {
+ (17006, "OpenStackConfigFileNotFoundError"): {
"message": "OpenStack clouds.yaml configuration file not found",
"remediation": "Check that the clouds.yaml file exists at the specified path or in standard locations (~/.config/openstack/clouds.yaml, /etc/openstack/clouds.yaml, ./clouds.yaml).",
},
- (10007, "OpenStackCloudNotFoundError"): {
+ (17007, "OpenStackCloudNotFoundError"): {
"message": "Specified cloud not found in clouds.yaml configuration",
"remediation": "Check that the cloud name exists in your clouds.yaml file and is properly configured.",
},
- (10008, "OpenStackInvalidConfigError"): {
+ (17008, "OpenStackInvalidConfigError"): {
"message": "Invalid or malformed clouds.yaml configuration file",
"remediation": "Check that the clouds.yaml file is valid YAML and follows the OpenStack configuration format.",
},
- (10009, "OpenStackInvalidProviderIdError"): {
+ (17009, "OpenStackInvalidProviderIdError"): {
"message": "Provider ID does not match the project_id in clouds.yaml",
"remediation": "Ensure the provider_id matches the project_id configured in your clouds.yaml file.",
},
- (10010, "OpenStackNoRegionError"): {
+ (17010, "OpenStackNoRegionError"): {
"message": "No region configuration found in clouds.yaml",
"remediation": "Add either 'region_name' (single region) or 'regions' (list of regions) to your cloud configuration in clouds.yaml.",
},
- (10011, "OpenStackAmbiguousRegionError"): {
+ (17011, "OpenStackAmbiguousRegionError"): {
"message": "Ambiguous region configuration in clouds.yaml",
"remediation": "Use either 'region_name' or 'regions' in your cloud configuration, not both.",
},
@@ -75,7 +75,7 @@ class OpenStackCredentialsError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10000,
+ code=17000,
file=file,
original_exception=original_exception,
message=message,
@@ -87,7 +87,7 @@ class OpenStackAuthenticationError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10001,
+ code=17001,
file=file,
original_exception=original_exception,
message=message,
@@ -99,7 +99,7 @@ class OpenStackSessionError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10002,
+ code=17002,
file=file,
original_exception=original_exception,
message=message,
@@ -111,7 +111,7 @@ class OpenStackIdentityError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10003,
+ code=17003,
file=file,
original_exception=original_exception,
message=message,
@@ -123,7 +123,7 @@ class OpenStackAPIError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10004,
+ code=17004,
file=file,
original_exception=original_exception,
message=message,
@@ -135,7 +135,7 @@ class OpenStackRateLimitError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10005,
+ code=17005,
file=file,
original_exception=original_exception,
message=message,
@@ -147,7 +147,7 @@ class OpenStackConfigFileNotFoundError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10006,
+ code=17006,
file=file,
original_exception=original_exception,
message=message,
@@ -159,7 +159,7 @@ class OpenStackCloudNotFoundError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10007,
+ code=17007,
file=file,
original_exception=original_exception,
message=message,
@@ -171,7 +171,7 @@ class OpenStackInvalidConfigError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10008,
+ code=17008,
file=file,
original_exception=original_exception,
message=message,
@@ -183,7 +183,7 @@ class OpenStackInvalidProviderIdError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10009,
+ code=17009,
file=file,
original_exception=original_exception,
message=message,
@@ -195,7 +195,7 @@ class OpenStackNoRegionError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10010,
+ code=17010,
file=file,
original_exception=original_exception,
message=message,
@@ -207,7 +207,7 @@ class OpenStackAmbiguousRegionError(OpenStackBaseException):
def __init__(self, file=None, original_exception=None, message=None):
super().__init__(
- code=10011,
+ code=17011,
file=file,
original_exception=original_exception,
message=message,
diff --git a/prowler/providers/openstack/openstack_provider.py b/prowler/providers/openstack/openstack_provider.py
index e81a399478..e11c4f7909 100644
--- a/prowler/providers/openstack/openstack_provider.py
+++ b/prowler/providers/openstack/openstack_provider.py
@@ -36,6 +36,7 @@ class OpenstackProvider(Provider):
"""OpenStack provider responsible for bootstrapping the SDK session."""
_type: str = "openstack"
+ sdk_only: bool = False
_session: OpenStackSession
_identity: OpenStackIdentityInfo
_audit_config: dict
diff --git a/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.metadata.json b/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.metadata.json
index 597d3ab4d4..bd83049d82 100644
--- a/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.metadata.json
+++ b/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.metadata.json
@@ -36,5 +36,5 @@
"RelatedTo": [
"blockstorage_volume_metadata_sensitive_data"
],
- "Notes": "This check uses the detect-secrets library to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns and detect_secrets_plugins to customize detection."
+ "Notes": "This check uses Kingfisher to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns."
}
diff --git a/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.py b/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.py
index 95de628871..51e25bc5eb 100644
--- a/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.py
+++ b/prowler/providers/openstack/services/blockstorage/blockstorage_snapshot_metadata_sensitive_data/blockstorage_snapshot_metadata_sensitive_data.py
@@ -2,7 +2,11 @@ import json
from typing import List
from prowler.lib.check.models import Check, CheckReportOpenStack
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.openstack.services.blockstorage.blockstorage_client import (
blockstorage_client,
)
@@ -16,30 +20,42 @@ class blockstorage_snapshot_metadata_sensitive_data(Check):
secrets_ignore_patterns = blockstorage_client.audit_config.get(
"secrets_ignore_patterns", []
)
+ validate = blockstorage_client.audit_config.get("secrets_validate", False)
+ snapshots = list(blockstorage_client.snapshots)
- for snapshot in blockstorage_client.snapshots:
+ # Collect one payload per snapshot (its metadata) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per snapshot.
+ def payloads():
+ for index, snapshot in enumerate(snapshots):
+ if snapshot.metadata:
+ yield index, json.dumps(dict(snapshot.metadata), indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, snapshot in enumerate(snapshots):
report = CheckReportOpenStack(metadata=self.metadata(), resource=snapshot)
report.status = "PASS"
report.status_extended = f"Snapshot {snapshot.name} ({snapshot.id}) metadata does not contain sensitive data."
if snapshot.metadata:
- # Build metadata dict and parallel list of keys
- dump_metadata = {}
- original_metadata_keys = []
- for key, value in snapshot.metadata.items():
- dump_metadata[key] = value
- original_metadata_keys.append(key)
-
- # Convert metadata dict to JSON string for detect-secrets scanning
- metadata_json = json.dumps(dump_metadata, indent=2)
- detect_secrets_output = detect_secrets_scan(
- data=metadata_json,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=blockstorage_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
-
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan snapshot {snapshot.name} ({snapshot.id}) "
+ f"metadata for secrets: {scan_error}; manual review is "
+ "required."
+ )
+ findings.append(report)
+ continue
+ original_metadata_keys = list(snapshot.metadata.keys())
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
# Map line numbers back to metadata keys using the parallel list
# Line numbering: line 1 = "{", line 2 = first key-value, etc.
@@ -54,6 +70,7 @@ class blockstorage_snapshot_metadata_sensitive_data(Check):
)
report.status = "FAIL"
report.status_extended = f"Snapshot {snapshot.name} ({snapshot.id}) metadata contains potential secrets -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status_extended = f"Snapshot {snapshot.name} ({snapshot.id}) has no metadata (no sensitive data exposure risk)."
diff --git a/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.metadata.json b/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.metadata.json
index ec17ee02d1..79874db214 100644
--- a/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.metadata.json
+++ b/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.metadata.json
@@ -34,5 +34,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": "This check uses the detect-secrets library to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns and detect_secrets_plugins to customize detection."
+ "Notes": "This check uses Kingfisher to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns."
}
diff --git a/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.py b/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.py
index 1bfa84c3df..48e064642a 100644
--- a/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.py
+++ b/prowler/providers/openstack/services/blockstorage/blockstorage_volume_metadata_sensitive_data/blockstorage_volume_metadata_sensitive_data.py
@@ -2,7 +2,11 @@ import json
from typing import List
from prowler.lib.check.models import Check, CheckReportOpenStack
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.openstack.services.blockstorage.blockstorage_client import (
blockstorage_client,
)
@@ -16,30 +20,41 @@ class blockstorage_volume_metadata_sensitive_data(Check):
secrets_ignore_patterns = blockstorage_client.audit_config.get(
"secrets_ignore_patterns", []
)
+ validate = blockstorage_client.audit_config.get("secrets_validate", False)
+ volumes = list(blockstorage_client.volumes)
- for volume in blockstorage_client.volumes:
+ # Collect one payload per volume (its metadata) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per volume.
+ def payloads():
+ for index, volume in enumerate(volumes):
+ if volume.metadata:
+ yield index, json.dumps(dict(volume.metadata), indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, volume in enumerate(volumes):
report = CheckReportOpenStack(metadata=self.metadata(), resource=volume)
report.status = "PASS"
report.status_extended = f"Volume {volume.name} ({volume.id}) metadata does not contain sensitive data."
if volume.metadata:
- # Build metadata dict and parallel list of keys
- dump_metadata = {}
- original_metadata_keys = []
- for key, value in volume.metadata.items():
- dump_metadata[key] = value
- original_metadata_keys.append(key)
-
- # Convert metadata dict to JSON string for detect-secrets scanning
- metadata_json = json.dumps(dump_metadata, indent=2)
- detect_secrets_output = detect_secrets_scan(
- data=metadata_json,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=blockstorage_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
-
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan volume {volume.name} ({volume.id}) metadata "
+ f"for secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ original_metadata_keys = list(volume.metadata.keys())
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
# Map line numbers back to metadata keys using the parallel list
# Line numbering: line 1 = "{", line 2 = first key-value, etc.
@@ -54,6 +69,7 @@ class blockstorage_volume_metadata_sensitive_data(Check):
)
report.status = "FAIL"
report.status_extended = f"Volume {volume.name} ({volume.id}) metadata contains potential secrets -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status_extended = f"Volume {volume.name} ({volume.id}) has no metadata (no sensitive data exposure risk)."
diff --git a/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.metadata.json b/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.metadata.json
index 015a00986d..c7f3e41f8e 100644
--- a/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.metadata.json
+++ b/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.metadata.json
@@ -34,5 +34,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": "This check uses the detect-secrets library to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns and detect_secrets_plugins to customize detection. Metadata is world-readable within instance via 169.254.169.254."
+ "Notes": "This check uses Kingfisher to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns. Metadata is world-readable within instance via 169.254.169.254."
}
diff --git a/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.py b/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.py
index 5df151c939..0627862da9 100644
--- a/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.py
+++ b/prowler/providers/openstack/services/compute/compute_instance_metadata_sensitive_data/compute_instance_metadata_sensitive_data.py
@@ -2,7 +2,11 @@ import json
from typing import List
from prowler.lib.check.models import Check, CheckReportOpenStack
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.openstack.services.compute.compute_client import compute_client
@@ -14,30 +18,42 @@ class compute_instance_metadata_sensitive_data(Check):
secrets_ignore_patterns = compute_client.audit_config.get(
"secrets_ignore_patterns", []
)
+ validate = compute_client.audit_config.get("secrets_validate", False)
+ instances = list(compute_client.instances)
- for instance in compute_client.instances:
+ # Collect one payload per instance (its metadata) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per instance.
+ def payloads():
+ for index, instance in enumerate(instances):
+ if instance.metadata:
+ yield index, json.dumps(dict(instance.metadata), indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, instance in enumerate(instances):
report = CheckReportOpenStack(metadata=self.metadata(), resource=instance)
report.status = "PASS"
report.status_extended = f"Instance {instance.name} ({instance.id}) metadata does not contain sensitive data."
if instance.metadata:
- # Build metadata dict and parallel list of keys (similar to AWS ECS pattern)
- dump_metadata = {}
- original_metadata_keys = []
- for key, value in instance.metadata.items():
- dump_metadata[key] = value
- original_metadata_keys.append(key)
-
- # Convert metadata dict to JSON string for detect-secrets scanning
- metadata_json = json.dumps(dump_metadata, indent=2)
- detect_secrets_output = detect_secrets_scan(
- data=metadata_json,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=compute_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
-
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan instance {instance.name} ({instance.id}) "
+ f"metadata for secrets: {scan_error}; manual review is "
+ "required."
+ )
+ findings.append(report)
+ continue
+ original_metadata_keys = list(instance.metadata.keys())
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
# Map line numbers back to metadata keys using the parallel list
# Line numbering: line 1 = "{", line 2 = first key-value, etc.
@@ -45,11 +61,14 @@ class compute_instance_metadata_sensitive_data(Check):
[
f"{secret['type']} in metadata key '{original_metadata_keys[secret['line_number'] - 2]}'"
for secret in detect_secrets_output
- if secret["line_number"] - 2 < len(original_metadata_keys)
+ if 0
+ <= secret["line_number"] - 2
+ < len(original_metadata_keys)
]
)
report.status = "FAIL"
report.status_extended = f"Instance {instance.name} ({instance.id}) metadata contains potential secrets -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status_extended = f"Instance {instance.name} ({instance.id}) has no metadata (no sensitive data exposure risk)."
diff --git a/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.metadata.json b/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.metadata.json
index b3a39bd3f8..37e7563c27 100644
--- a/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.metadata.json
+++ b/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.metadata.json
@@ -35,5 +35,5 @@
],
"DependsOn": [],
"RelatedTo": [],
- "Notes": "This check uses the detect-secrets library to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns and detect_secrets_plugins to customize detection."
+ "Notes": "This check uses Kingfisher to scan for credentials. May produce false positives on metadata keys containing secret-like keywords. Findings should be reviewed manually. The audit_config allows configuring secrets_ignore_patterns to exclude specific patterns."
}
diff --git a/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.py b/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.py
index 94d281bf32..549be81046 100644
--- a/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.py
+++ b/prowler/providers/openstack/services/objectstorage/objectstorage_container_metadata_sensitive_data/objectstorage_container_metadata_sensitive_data.py
@@ -2,7 +2,11 @@ import json
from typing import List
from prowler.lib.check.models import Check, CheckReportOpenStack
-from prowler.lib.utils.utils import detect_secrets_scan
+from prowler.lib.utils.utils import (
+ SecretsScanError,
+ annotate_verified_secrets,
+ detect_secrets_scan_batch,
+)
from prowler.providers.openstack.services.objectstorage.objectstorage_client import (
objectstorage_client,
)
@@ -16,8 +20,26 @@ class objectstorage_container_metadata_sensitive_data(Check):
secrets_ignore_patterns = objectstorage_client.audit_config.get(
"secrets_ignore_patterns", []
)
+ validate = objectstorage_client.audit_config.get("secrets_validate", False)
+ containers = list(objectstorage_client.containers)
- for container in objectstorage_client.containers:
+ # Collect one payload per container (its metadata) and scan them all in
+ # batched Kingfisher invocations instead of one subprocess per container.
+ def payloads():
+ for index, container in enumerate(containers):
+ if container.metadata:
+ yield index, json.dumps(dict(container.metadata), indent=2)
+
+ scan_error = None
+ try:
+ batch_results = detect_secrets_scan_batch(
+ payloads(), excluded_secrets=secrets_ignore_patterns, validate=validate
+ )
+ except SecretsScanError as error:
+ batch_results = {}
+ scan_error = error
+
+ for index, container in enumerate(containers):
report = CheckReportOpenStack(metadata=self.metadata(), resource=container)
report.status = "PASS"
report.status_extended = (
@@ -25,23 +47,16 @@ class objectstorage_container_metadata_sensitive_data(Check):
)
if container.metadata:
- # Build metadata dict and parallel list of keys
- dump_metadata = {}
- original_metadata_keys = []
- for key, value in container.metadata.items():
- dump_metadata[key] = value
- original_metadata_keys.append(key)
-
- # Convert metadata dict to JSON string for detect-secrets scanning
- metadata_json = json.dumps(dump_metadata, indent=2)
- detect_secrets_output = detect_secrets_scan(
- data=metadata_json,
- excluded_secrets=secrets_ignore_patterns,
- detect_secrets_plugins=objectstorage_client.audit_config.get(
- "detect_secrets_plugins"
- ),
- )
-
+ if scan_error:
+ report.status = "MANUAL"
+ report.status_extended = (
+ f"Could not scan container {container.name} metadata for "
+ f"secrets: {scan_error}; manual review is required."
+ )
+ findings.append(report)
+ continue
+ original_metadata_keys = list(container.metadata.keys())
+ detect_secrets_output = batch_results.get(index)
if detect_secrets_output:
# Map line numbers back to metadata keys using the parallel list
# Line numbering: line 1 = "{", line 2 = first key-value, etc.
@@ -56,6 +71,7 @@ class objectstorage_container_metadata_sensitive_data(Check):
)
report.status = "FAIL"
report.status_extended = f"Container {container.name} metadata contains potential secrets -> {secrets_string}."
+ annotate_verified_secrets(report, detect_secrets_output)
else:
report.status_extended = f"Container {container.name} has no metadata (no sensitive data exposure risk)."
diff --git a/prowler/providers/oraclecloud/oraclecloud_provider.py b/prowler/providers/oraclecloud/oraclecloud_provider.py
index 22fa10b276..a4794f6269 100644
--- a/prowler/providers/oraclecloud/oraclecloud_provider.py
+++ b/prowler/providers/oraclecloud/oraclecloud_provider.py
@@ -1,3 +1,4 @@
+from collections.abc import Iterable
import os
import pathlib
import re
@@ -59,6 +60,7 @@ class OraclecloudProvider(Provider):
"""
_type: str = "oraclecloud"
+ sdk_only: bool = False
_identity: OCIIdentityInfo
_session: OCISession
_audit_config: dict
@@ -67,12 +69,13 @@ class OraclecloudProvider(Provider):
_mutelist: OCIMutelist
audit_metadata: Audit_Metadata
_home_region: str = "us-ashburn-1"
+ _bootstrap_region: str = "us-ashburn-1"
def __init__(
self,
oci_config_file: str = None,
profile: str = None,
- region: set = set(),
+ region: str | Iterable[str] = None,
compartment_ids: list = None,
config_path: str = None,
config_content: dict = None,
@@ -128,10 +131,17 @@ class OraclecloudProvider(Provider):
logger.info("Initializing OCI provider ...")
- # Check if the configuration is scanning a single region
- single_region = None
- if region:
- single_region = list(region)[0] if len(region) == 1 else None
+ # Check if the configuration is scanning exactly one explicit region.
+ explicit_regions = self._normalize_region_input(region)
+ single_region = (
+ next(iter(explicit_regions))
+ if explicit_regions and len(explicit_regions) == 1
+ else None
+ )
+ has_direct_credentials = user and fingerprint and tenancy
+ bootstrap_region = single_region or (
+ self._bootstrap_region if has_direct_credentials else None
+ )
# Setup OCI Session
logger.info("Setting up OCI session ...")
@@ -144,7 +154,7 @@ class OraclecloudProvider(Provider):
key_file=key_file,
key_content=key_content,
tenancy=tenancy,
- region=single_region,
+ region=bootstrap_region,
pass_phrase=pass_phrase,
)
@@ -161,12 +171,20 @@ class OraclecloudProvider(Provider):
# Get regions
self._regions = self.get_regions_to_audit(region)
- self._home_region = None
- if self._regions:
- self._home_region = next(
- (region.key for region in self._regions if region.is_home_region),
- self._regions[0].key,
- )
+ # Determine the tenancy home region from the full subscription list, independent of
+ # the --region filter, so tenancy-level APIs (e.g. the Audit configuration) always
+ # target the home region instead of a filtered, non-home region.
+ try:
+ all_subscribed_regions = self.get_regions_to_audit()
+ except OCISetUpSessionError:
+ if single_region and len(self._regions) == 1:
+ all_subscribed_regions = self._regions
+ else:
+ raise
+ self._home_region = next(
+ (region.key for region in all_subscribed_regions if region.is_home_region),
+ self._regions[0].key if self._regions else "us-ashburn-1",
+ )
logger.info(f"Home region is: {self._home_region}")
# Get compartments
@@ -240,6 +258,22 @@ class OraclecloudProvider(Provider):
"""
return self._mutelist
+ @staticmethod
+ def _normalize_region_input(region: str | Iterable[str] = None) -> set[str] | None:
+ """Normalize OCI region input while treating strings as one region.
+
+ Args:
+ region: Region input as a string, iterable of strings, or None.
+
+ Returns:
+ A set of region names, or None when no region is provided.
+ """
+ if isinstance(region, str):
+ return {region} if region else None
+ if region:
+ return set(region)
+ return None
+
@staticmethod
def setup_session(
oci_config_file: str = None,
@@ -281,7 +315,7 @@ class OraclecloudProvider(Provider):
signer = None
# If API key credentials are provided directly, create config from them
- if user and fingerprint and tenancy and region:
+ if user and fingerprint and tenancy:
import base64
logger.info("Using API key credentials from direct parameters")
@@ -291,7 +325,7 @@ class OraclecloudProvider(Provider):
"user": user,
"fingerprint": fingerprint,
"tenancy": tenancy,
- "region": region,
+ "region": region or OraclecloudProvider._bootstrap_region,
}
# Handle private key
@@ -550,7 +584,7 @@ class OraclecloudProvider(Provider):
return True
- def get_regions_to_audit(self, region_set: set = None) -> list:
+ def get_regions_to_audit(self, region_set: str | Iterable[str] = None) -> list:
"""
get_regions_to_audit returns the list of regions to audit.
@@ -562,6 +596,8 @@ class OraclecloudProvider(Provider):
"""
regions = []
+ explicit_regions = self._normalize_region_input(region_set)
+
# Audit all subscribed regions
try:
# Create identity client with proper authentication handling
@@ -578,11 +614,9 @@ class OraclecloudProvider(Provider):
).data
# Check if auditing specific region or all
- regions_check = (
- region_set
- if region_set
- else [sub.region_name for sub in region_subscriptions]
- )
+ regions_check = explicit_regions or [
+ sub.region_name for sub in region_subscriptions
+ ]
for region_sub in region_subscriptions:
if region_sub.region_name in regions_check:
@@ -597,11 +631,25 @@ class OraclecloudProvider(Provider):
)
logger.info(f"Found {len(regions)} subscribed regions")
except Exception as error:
+ if not explicit_regions or len(explicit_regions) != 1:
+ logger.critical(
+ f"OCISetUpSessionError[{error.__traceback__.tb_lineno}]: {error}"
+ )
+ raise OCISetUpSessionError(
+ original_exception=error,
+ file=pathlib.Path(__file__).name,
+ message=(
+ "Could not retrieve OCI subscribed regions. "
+ "Configure an explicit region to preserve legacy single-region scans, "
+ "or fix the credentials/permissions required to list region subscriptions."
+ ),
+ ) from error
+
+ config_region = next(iter(explicit_regions))
logger.warning(
- f"Could not retrieve region subscriptions: {error}. Using configured region."
+ f"Could not retrieve region subscriptions: {error}. "
+ f"Using explicitly configured region {config_region}."
)
- # Fallback to configured region
- config_region = self._session.config.get("region", "us-ashburn-1")
regions.append(
OCIRegion(
key=config_region,
@@ -852,17 +900,21 @@ class OraclecloudProvider(Provider):
session = None
# If API key credentials are provided directly, create config from them
- if user and fingerprint and tenancy and region:
+ has_direct_credentials = user and fingerprint and tenancy
+ identity_region = region
+ if has_direct_credentials:
import base64
logger.info("Using API key credentials from direct parameters")
+ identity_region = region or OraclecloudProvider._bootstrap_region
+
# Create config dict from provided credentials
config = {
"user": user,
"fingerprint": fingerprint,
"tenancy": tenancy,
- "region": region,
+ "region": identity_region,
}
# Handle private key
@@ -911,7 +963,7 @@ class OraclecloudProvider(Provider):
identity = OraclecloudProvider.set_identity(
session=session,
- region=region,
+ region=identity_region,
)
# Validate provider_id if provided
diff --git a/prowler/providers/oraclecloud/services/audit/audit_service.py b/prowler/providers/oraclecloud/services/audit/audit_service.py
index fe7751a10e..38022d1d87 100644
--- a/prowler/providers/oraclecloud/services/audit/audit_service.py
+++ b/prowler/providers/oraclecloud/services/audit/audit_service.py
@@ -19,9 +19,15 @@ class Audit(OCIService):
def __get_configuration__(self):
"""Get Audit configuration."""
try:
- audit_client = self._create_oci_client(oci.audit.AuditClient)
+ home_region = self.provider.home_region
+ audit_client = self._create_oci_client(
+ oci.audit.AuditClient,
+ config_overrides={"region": home_region},
+ )
- logger.info("Audit - Getting Configuration...")
+ logger.info(
+ f"Audit - Getting Configuration from home region ({home_region})..."
+ )
try:
config = audit_client.get_configuration(
diff --git a/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/__init__.py b/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.metadata.json b/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.metadata.json
new file mode 100644
index 0000000000..4e8f905658
--- /dev/null
+++ b/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "oraclecloud",
+ "CheckID": "identity_storage_service_level_admins_scoped",
+ "CheckTitle": "OCI IAM storage service-level admin policies exclude delete permissions",
+ "CheckType": [],
+ "ServiceName": "identity",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "Policy",
+ "ResourceGroup": "IAM",
+ "Description": "**OCI IAM policies** are reviewed to ensure storage service-level administrator statements that grant `manage` permissions exclude the relevant storage delete permissions with `request.permission`. This supports CIS OCI 3.1 control 1.15 separation of duties for Block Volume, File Storage, and Object Storage administrators.",
+ "Risk": "Storage service-level administrators with unrestricted `manage` permissions can delete the resources they administer, including volumes, backups, file systems, mount targets, export sets, objects, or buckets. This weakens separation of duties and can lead to data loss, service disruption, or destructive insider activity.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.oracle.com/en-us/iaas/Content/Identity/policyreference/policyreference.htm",
+ "https://docs.oracle.com/en-us/iaas/Content/Block/home.htm",
+ "https://docs.oracle.com/en-us/iaas/Content/File/home.htm",
+ "https://docs.oracle.com/en-us/iaas/Content/Object/home.htm"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "oci iam policy update --policy-id <policy-ocid> --statements \"[\\\"Allow group VolumeUsers to manage volumes in tenancy where request.permission!='VOLUME_DELETE'\\\"]\"",
+ "NativeIaC": "",
+ "Other": "1. In OCI Console, go to Identity & Security > Policies\n2. Open each active policy that grants storage service-level administrators `manage` permissions\n3. Edit storage manage statements to exclude the relevant delete permission with `request.permission`\n4. Example: Allow group BucketUsers to manage buckets in tenancy where request.permission!='BUCKET_DELETE'\n5. Save changes",
+ "Terraform": "```hcl\nresource \"oci_identity_policy\" \"storage_admins\" {\n compartment_id = var.compartment_id\n name = \"storage-admins\"\n description = \"Storage administrators without delete permissions\"\n\n statements = [\n \"Allow group VolumeUsers to manage volumes in tenancy where request.permission!='VOLUME_DELETE'\",\n \"Allow group VolumeUsers to manage volume-backups in tenancy where request.permission!='VOLUME_BACKUP_DELETE'\",\n \"Allow group FileUsers to manage file-systems in tenancy where request.permission!='FILE_SYSTEM_DELETE'\",\n \"Allow group FileUsers to manage mount-targets in tenancy where request.permission!='MOUNT_TARGET_DELETE'\",\n \"Allow group FileUsers to manage export-sets in tenancy where request.permission!='EXPORT_SET_DELETE'\",\n \"Allow group BucketUsers to manage objects in tenancy where request.permission!='OBJECT_DELETE'\",\n \"Allow group BucketUsers to manage buckets in tenancy where request.permission!='BUCKET_DELETE'\"\n ]\n}\n```"
+ },
+ "Recommendation": {
+ "Text": "Exclude delete permissions from storage service-level administrator policies. Use `request.permission!='VOLUME_DELETE'`, `request.permission!='VOLUME_BACKUP_DELETE'`, `request.permission!='FILE_SYSTEM_DELETE'`, `request.permission!='MOUNT_TARGET_DELETE'`, `request.permission!='EXPORT_SET_DELETE'`, `request.permission!='OBJECT_DELETE'`, and `request.permission!='BUCKET_DELETE'` as appropriate for each storage manage statement.",
+ "Url": "https://hub.prowler.com/check/identity_storage_service_level_admins_scoped"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": ""
+}
diff --git a/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.py b/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.py
new file mode 100644
index 0000000000..49ef16748a
--- /dev/null
+++ b/prowler/providers/oraclecloud/services/identity/identity_storage_service_level_admins_scoped/identity_storage_service_level_admins_scoped.py
@@ -0,0 +1,176 @@
+"""Check storage service-level administrators cannot delete managed resources."""
+
+import re
+
+from prowler.lib.check.models import Check, Check_Report_OCI
+from prowler.providers.oraclecloud.services.identity.identity_client import (
+ identity_client,
+)
+
+STORAGE_DELETE_PERMISSIONS_BY_RESOURCE = {
+ "volumes": {"VOLUME_DELETE"},
+ "volume-backups": {"VOLUME_BACKUP_DELETE"},
+ "file-systems": {"FILE_SYSTEM_DELETE"},
+ "mount-targets": {"MOUNT_TARGET_DELETE"},
+ "export-sets": {"EXPORT_SET_DELETE"},
+ "objects": {"OBJECT_DELETE"},
+ "buckets": {"BUCKET_DELETE"},
+ "volume-family": {"VOLUME_DELETE", "VOLUME_BACKUP_DELETE"},
+ "file-family": {"FILE_SYSTEM_DELETE", "MOUNT_TARGET_DELETE", "EXPORT_SET_DELETE"},
+ "object-family": {"OBJECT_DELETE", "BUCKET_DELETE"},
+}
+ALL_STORAGE_DELETE_PERMISSIONS = set().union(
+ *STORAGE_DELETE_PERMISSIONS_BY_RESOURCE.values()
+)
+STORAGE_DELETE_PERMISSIONS_BY_RESOURCE["all-resources"] = ALL_STORAGE_DELETE_PERMISSIONS
+
+MANAGE_STATEMENT_PATTERN = re.compile(
+ r"\ballow\s+group\b.+?\bto\s+manage\s+(?P<resource>[a-z-]+)\b",
+ re.IGNORECASE,
+)
+QUOTED_LITERAL_PATTERN = re.compile(r"'(?:\\.|[^'\\])*'|\"(?:\\.|[^\"\\])*\"")
+
+
+def _normalize_statement(statement: str) -> str:
+ """Collapse whitespace in an OCI policy statement."""
+ return " ".join(statement.strip().split())
+
+
+def _has_disjunctive_condition(statement: str) -> bool:
+ """Return True when the WHERE condition can allow alternate branches."""
+ condition = re.split(r"\bwhere\b", statement, flags=re.IGNORECASE, maxsplit=1)
+ if len(condition) != 2:
+ return False
+
+ condition_without_literals = QUOTED_LITERAL_PATTERN.sub("", condition[1])
+ return bool(
+ re.search(r"\b(any|or)\b|\|\|", condition_without_literals, re.IGNORECASE)
+ )
+
+
+def _storage_manage_resource(statement: str) -> str | None:
+ """Return the managed storage resource in a policy statement, if any."""
+ normalized_statement = _normalize_statement(statement)
+ match = MANAGE_STATEMENT_PATTERN.search(normalized_statement)
+ if not match:
+ return None
+
+ resource = match.group("resource").lower()
+ if resource not in STORAGE_DELETE_PERMISSIONS_BY_RESOURCE:
+ return None
+
+ return resource
+
+
+def _excluded_permissions(statement: str) -> set[str]:
+ """Return delete permissions explicitly excluded with request.permission != value."""
+ if _has_disjunctive_condition(statement):
+ return set()
+
+ exclusions = set()
+ for permission in ALL_STORAGE_DELETE_PERMISSIONS:
+ pattern = re.compile(
+ rf"\brequest\.permission\s*!=\s*['\"]?{re.escape(permission)}['\"]?\b",
+ re.IGNORECASE,
+ )
+ if pattern.search(statement):
+ exclusions.add(permission)
+ return exclusions
+
+
+def _missing_delete_exclusions(statement: str) -> tuple[str, set[str]] | None:
+ """Return the storage resource and missing delete exclusions for a statement."""
+ normalized_statement = _normalize_statement(statement)
+ resource = _storage_manage_resource(normalized_statement)
+ if not resource:
+ return None
+
+ required_permissions = STORAGE_DELETE_PERMISSIONS_BY_RESOURCE[resource]
+
+ excluded_permissions = _excluded_permissions(normalized_statement)
+ missing_permissions = required_permissions - excluded_permissions
+ if not missing_permissions:
+ return None
+
+ return resource, missing_permissions
+
+
+class identity_storage_service_level_admins_scoped(Check):
+ """Ensure storage service-level admins cannot delete resources they manage."""
+
+ def execute(self) -> list[Check_Report_OCI]:
+ """Execute the storage service-level administrators scoped check.
+
+ Returns:
+ A list of OCI check reports for active non-tenant-admin policies.
+ """
+ findings = []
+
+ for policy in identity_client.policies:
+ if policy.lifecycle_state != "ACTIVE":
+ continue
+
+ if policy.name.upper() == "TENANT ADMIN POLICY":
+ continue
+
+ region = policy.region if hasattr(policy, "region") else "global"
+ violations = []
+ has_storage_manage_statement = False
+
+ for statement in policy.statements:
+ if _storage_manage_resource(statement):
+ has_storage_manage_statement = True
+
+ missing_result = _missing_delete_exclusions(statement)
+ if not missing_result:
+ continue
+
+ resource, missing_permissions = missing_result
+ violations.append(
+ f"statement `{_normalize_statement(statement)}` manages {resource} without excluding: {', '.join(sorted(missing_permissions))}"
+ )
+
+ if not has_storage_manage_statement:
+ continue
+
+ report = Check_Report_OCI(
+ metadata=self.metadata(),
+ resource=policy,
+ region=region,
+ resource_id=policy.id,
+ resource_name=policy.name,
+ compartment_id=policy.compartment_id,
+ )
+
+ if violations:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Policy '{policy.name}' allows storage service-level administrators to manage storage resources without explicitly excluding required delete permissions: "
+ + "; ".join(violations)
+ + "."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = f"Policy '{policy.name}' excludes required storage delete permissions from storage manage statements."
+
+ findings.append(report)
+
+ if not findings:
+ region = (
+ identity_client.audited_regions[0].key
+ if identity_client.audited_regions
+ else "global"
+ )
+ report = Check_Report_OCI(
+ metadata=self.metadata(),
+ resource={},
+ region=region,
+ resource_id=identity_client.audited_tenancy,
+ resource_name="Tenancy",
+ compartment_id=identity_client.audited_tenancy,
+ )
+ report.status = "PASS"
+ report.status_extended = "No active storage service-level administrator policies grant manage permissions without excluding delete permissions."
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/__init__.py b/prowler/providers/stackit/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/exceptions/__init__.py b/prowler/providers/stackit/exceptions/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/exceptions/exceptions.py b/prowler/providers/stackit/exceptions/exceptions.py
new file mode 100644
index 0000000000..246abb337c
--- /dev/null
+++ b/prowler/providers/stackit/exceptions/exceptions.py
@@ -0,0 +1,99 @@
+from prowler.exceptions.exceptions import ProwlerException
+
+
+# Exceptions codes from 16000 to 16999 are reserved for StackIT exceptions
+class StackITBaseException(ProwlerException):
+ """Base class for StackIT Errors."""
+
+ STACKIT_ERROR_CODES = {
+ (16001, "StackITNonExistentTokenError"): {
+ "message": "A StackIT service account key file is required to authenticate against StackIT",
+ "remediation": "Set --stackit-service-account-key-path or the STACKIT_SERVICE_ACCOUNT_KEY_PATH environment variable to a valid service account key JSON file.",
+ },
+ (16002, "StackITInvalidTokenError"): {
+ "message": "StackIT service account key was rejected or lacks permissions",
+ "remediation": "Verify the service account key file is current, has not been revoked, and that the service account has the required roles on the project.",
+ },
+ (16003, "StackITSetUpSessionError"): {
+ "message": "Error setting up StackIT session",
+ "remediation": "Check the session setup and ensure the StackIT SDK is properly configured.",
+ },
+ (16004, "StackITSetUpIdentityError"): {
+ "message": "StackIT identity setup error due to bad credentials",
+ "remediation": "Check credentials and ensure they are properly set up for StackIT.",
+ },
+ (16005, "StackITInvalidProjectIdError"): {
+ "message": "The provided project ID is not valid or not accessible",
+ "remediation": "Check the project ID and ensure you have access to it with the provided credentials.",
+ },
+ (16006, "StackITAPIError"): {
+ "message": "Error calling StackIT API",
+ "remediation": "Check the API endpoint and ensure the service is accessible. Verify network connectivity.",
+ },
+ }
+
+ def __init__(self, code, file=None, original_exception=None, message=None):
+ provider = "StackIT"
+ # Clone the catalog entry so per-instance message overrides do not
+ # mutate the class-level dict and bleed into later exceptions raised
+ # in the same process.
+ base_info = self.STACKIT_ERROR_CODES.get((code, self.__class__.__name__))
+ error_info = dict(base_info) if base_info else None
+ if message and error_info is not None:
+ error_info["message"] = message
+ super().__init__(
+ code=code,
+ source=provider,
+ file=file,
+ original_exception=original_exception,
+ error_info=error_info,
+ )
+
+
+class StackITCredentialsError(StackITBaseException):
+ """Base class for StackIT credentials errors."""
+
+ def __init__(self, code, file=None, original_exception=None, message=None):
+ super().__init__(code, file, original_exception, message)
+
+
+class StackITNonExistentTokenError(StackITCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16001, file=file, original_exception=original_exception, message=message
+ )
+
+
+class StackITInvalidTokenError(StackITCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16002, file=file, original_exception=original_exception, message=message
+ )
+
+
+class StackITSetUpSessionError(StackITCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16003, file=file, original_exception=original_exception, message=message
+ )
+
+
+class StackITSetUpIdentityError(StackITCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16004, file=file, original_exception=original_exception, message=message
+ )
+
+
+class StackITInvalidProjectIdError(StackITCredentialsError):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16005, file=file, original_exception=original_exception, message=message
+ )
+
+
+class StackITAPIError(StackITBaseException):
+ def __init__(self, file=None, original_exception=None, message=None):
+ super().__init__(
+ 16006, file=file, original_exception=original_exception, message=message
+ )
diff --git a/prowler/providers/stackit/lib/__init__.py b/prowler/providers/stackit/lib/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/lib/arguments/__init__.py b/prowler/providers/stackit/lib/arguments/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/lib/arguments/arguments.py b/prowler/providers/stackit/lib/arguments/arguments.py
new file mode 100644
index 0000000000..afabc41fe8
--- /dev/null
+++ b/prowler/providers/stackit/lib/arguments/arguments.py
@@ -0,0 +1,60 @@
+from prowler.providers.stackit.stackit_provider import StackitProvider
+
+SENSITIVE_ARGUMENTS = frozenset({"--stackit-service-account-key"})
+
+
+def init_parser(self):
+ """Init the StackIT Provider CLI parser"""
+ stackit_parser = self.subparsers.add_parser(
+ "stackit", parents=[self.common_providers_parser], help="StackIT Provider"
+ )
+
+ # Authentication
+ stackit_auth_subparser = stackit_parser.add_argument_group("Authentication")
+ stackit_auth_subparser.add_argument(
+ "--stackit-project-id",
+ nargs="?",
+ default=None,
+ help="StackIT Project ID to audit (alternatively set via STACKIT_PROJECT_ID environment variable)",
+ )
+ stackit_auth_subparser.add_argument(
+ "--stackit-service-account-key-path",
+ nargs="?",
+ default=None,
+ help=(
+ "Path to a StackIT service account key JSON file. The SDK signs the RSA "
+ "challenge in the key and mints/refreshes access tokens internally for "
+ "the life of the scan. Alternatively set via the "
+ "STACKIT_SERVICE_ACCOUNT_KEY_PATH environment variable."
+ ),
+ )
+ stackit_auth_subparser.add_argument(
+ "--stackit-service-account-key",
+ nargs="?",
+ default=None,
+ help=(
+ "Inline content of a StackIT service account key (JSON). Useful in "
+ "CI/CD where the secret comes from a secret manager and you do not "
+ "want to write it to disk. Prefer the STACKIT_SERVICE_ACCOUNT_KEY "
+ "environment variable over this flag to avoid leaking the key "
+ "through process listings or shell history."
+ ),
+ )
+
+ stackit_parser.add_argument(
+ "--stackit-region",
+ "-r",
+ nargs="+",
+ help="STACKIT region(s) to scan (default: all available regions)",
+ choices=StackitProvider.get_regions(),
+ default=None,
+ )
+
+ scan_unused_services_subparser = stackit_parser.add_argument_group(
+ "Scan Unused Services"
+ )
+ scan_unused_services_subparser.add_argument(
+ "--scan-unused-services",
+ action="store_true",
+ help="Scan unused services",
+ )
diff --git a/prowler/providers/stackit/lib/mutelist/__init__.py b/prowler/providers/stackit/lib/mutelist/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/lib/mutelist/mutelist.py b/prowler/providers/stackit/lib/mutelist/mutelist.py
new file mode 100644
index 0000000000..5711392849
--- /dev/null
+++ b/prowler/providers/stackit/lib/mutelist/mutelist.py
@@ -0,0 +1,23 @@
+from prowler.lib.check.models import CheckReportStackIT
+from prowler.lib.mutelist.mutelist import Mutelist
+from prowler.lib.outputs.utils import unroll_dict, unroll_tags
+
+
+class StackITMutelist(Mutelist):
+ def is_finding_muted(self, finding: CheckReportStackIT) -> bool:
+ """
+ Determines if a StackIT finding is muted based on mutelist rules.
+
+ Args:
+ finding: A CheckReportStackIT finding object
+
+ Returns:
+ bool: True if the finding is muted, False otherwise
+ """
+ return self.is_muted(
+ finding.project_id,
+ finding.check_metadata.CheckID,
+ finding.location,
+ finding.resource_name,
+ unroll_dict(unroll_tags(finding.resource_tags)),
+ )
diff --git a/prowler/providers/stackit/lib/service/__init__.py b/prowler/providers/stackit/lib/service/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/models.py b/prowler/providers/stackit/models.py
new file mode 100644
index 0000000000..d069011083
--- /dev/null
+++ b/prowler/providers/stackit/models.py
@@ -0,0 +1,48 @@
+from pydantic.v1 import BaseModel
+
+from prowler.config.config import output_file_timestamp
+from prowler.providers.common.models import ProviderOutputOptions
+
+
+class StackITIdentityInfo(BaseModel):
+ """
+ StackITIdentityInfo holds basic identity fields for the StackIT provider.
+
+ Attributes:
+ - project_id (str): The StackIT project ID being audited.
+ - project_name (str): The name of the StackIT project (fetched from Resource Manager API).
+ """
+
+ project_id: str
+ project_name: str = ""
+ audited_regions: set = set()
+
+
+class StackITOutputOptions(ProviderOutputOptions):
+ """
+ StackITOutputOptions overrides ProviderOutputOptions for StackIT-specific output logic.
+ Generates a filename that includes the StackIT project_id.
+
+ Attributes inherited from ProviderOutputOptions:
+ - output_filename (str): The base filename used for generated reports.
+ - output_directory (str): The directory to store the output files.
+ - ... see ProviderOutputOptions for more details.
+
+ Methods:
+ - __init__: Customizes the output filename logic for StackIT.
+ """
+
+ def __init__(self, arguments, bulk_checks_metadata, identity: StackITIdentityInfo):
+ super().__init__(arguments, bulk_checks_metadata)
+
+ # If --output-filename is not specified, build a default name.
+ if not getattr(arguments, "output_filename", None):
+ # If project_id exists, include it in the filename (e.g., prowler-output-stackit-<project_id>-20230101)
+ if identity.project_id:
+ self.output_filename = f"prowler-output-stackit-{identity.project_id}-{output_file_timestamp}"
+ # Otherwise just 'prowler-output-stackit-<timestamp>'
+ else:
+ self.output_filename = f"prowler-output-stackit-{output_file_timestamp}"
+ # If --output-filename was explicitly given, respect that
+ else:
+ self.output_filename = arguments.output_filename
diff --git a/prowler/providers/stackit/services/__init__.py b/prowler/providers/stackit/services/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/__init__.py b/prowler/providers/stackit/services/iaas/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_client.py b/prowler/providers/stackit/services/iaas/iaas_client.py
new file mode 100644
index 0000000000..eca20c46b4
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_client.py
@@ -0,0 +1,4 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.stackit.services.iaas.iaas_service import IaaSService
+
+iaas_client = IaaSService(Provider.get_global_provider())
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/__init__.py b/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.metadata.json b/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.metadata.json
new file mode 100644
index 0000000000..a6bcd648bd
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "iaas_security_group_all_traffic_unrestricted",
+ "CheckTitle": "IaaS security groups do not allow unrestricted access to all ports",
+ "CheckType": [],
+ "ServiceName": "iaas",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "critical",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "Security groups should not allow unrestricted access to all ports from the public internet (`0.0.0.0/0` or `::/0`). This includes rules with no port range specified or rules covering the full port range (`0-65535` or `1-65535`). Allowing all ports **exposes every service** running on the instances to potential attacks.",
+ "Risk": "Allowing unrestricted access to all ports from the internet exposes **all services and applications** to potential attacks, **unauthorized access**, and security breaches. This effectively **bypasses the security group's purpose** as a firewall.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/",
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/how-tos/create-and-manage-security-groups-and-rules/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the StackIT Portal open Networking > Security Groups and select the affected security group. 2. Locate the ingress rule that allows all ports and protocols from 0.0.0.0/0 or ::/0. 3. Delete the broad rule and replace it with granular rules that open only the specific ports each service needs. 4. Restrict the source of every rule to trusted IP ranges following least privilege. 5. Re-run Prowler to confirm the finding is resolved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Follow the **principle of least privilege** by only allowing the specific ports that are required. Create **granular rules** for each service and restrict access to trusted IP addresses or ranges.",
+ "Url": "https://hub.prowler.com/check/iaas_security_group_all_traffic_unrestricted"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check identifies security groups that allow all ports from the public internet. It flags rules with no port range specified or rules covering the full port range (0-65535 or 1-65535), regardless of the specific protocol. Security groups should implement specific rules for each required service rather than allowing all ports."
+}
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.py b/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.py
new file mode 100644
index 0000000000..1b2a7d02f3
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_all_traffic_unrestricted/iaas_security_group_all_traffic_unrestricted.py
@@ -0,0 +1,67 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+
+class iaas_security_group_all_traffic_unrestricted(Check):
+ """
+ Check if IaaS security groups allow unrestricted access to all ports.
+
+ This check verifies that security groups do not allow all ports
+ from the public internet (0.0.0.0/0 or ::/0). This includes rules
+ with no port range specified or rules covering the full port range
+ (0-65535 or 1-65535), regardless of the specific protocol.
+ """
+
+ def execute(self):
+ """
+ Execute the check for all security groups in the StackIT project.
+
+ Returns:
+ list: A list of CheckReportStackIT findings
+ """
+ findings = []
+
+ for security_group in iaas_client.security_groups:
+ if not (iaas_client.scan_unused_services or security_group.in_use):
+ continue
+ unrestricted_rules = []
+
+ # Check each ingress rule
+ for rule in security_group.rules:
+ # Only check ingress rules that are unrestricted
+ if rule.is_ingress() and rule.is_unrestricted():
+ # Check if rule allows all traffic (no port restrictions or all protocols)
+ if rule.port_range_min is None or rule.port_range_max is None:
+ # No port range specified - allows all ports
+ unrestricted_rules.append(
+ f"Rule {rule.get_rule_display_name()} allows all ports ({rule.protocol or 'all protocols'}) from {rule.get_ip_range_display()}"
+ )
+ elif (
+ rule.port_range_min == 0 or rule.port_range_min == 1
+ ) and rule.port_range_max >= 65535:
+ # Port range covers all or nearly all ports
+ unrestricted_rules.append(
+ f"Rule {rule.get_rule_display_name()} allows all ports (1-65535) ({rule.protocol or 'all protocols'}) from {rule.get_ip_range_display()}"
+ )
+
+ # Create a finding report for this security group
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group,
+ )
+
+ if unrestricted_rules:
+ report.status = "FAIL"
+ rules_list = "; ".join(unrestricted_rules)
+ report.status_extended = f"Security group {security_group.name} allows unrestricted access to all traffic: {rules_list}."
+ else:
+ report.status = "PASS"
+ report.status_extended = f"Security group {security_group.name} does not allow unrestricted access to all traffic."
+
+ report.resource_id = security_group.id
+ report.resource_name = security_group.name
+ report.location = security_group.region
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/__init__.py b/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.metadata.json b/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.metadata.json
new file mode 100644
index 0000000000..2337e2e01c
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "iaas_security_group_database_unrestricted",
+ "CheckTitle": "IaaS security groups do not allow unrestricted database access",
+ "CheckType": [],
+ "ServiceName": "iaas",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "Security groups should not allow unrestricted access to database ports from the public internet (`0.0.0.0/0` or `::/0`). This includes MySQL (`3306`), PostgreSQL (`5432`), MongoDB (`27017`), Redis (`6379`), SQL Server (`1433`), and CouchDB (`5984`). Unrestricted database access can lead to **data breaches** and **unauthorized access**.",
+ "Risk": "Allowing unrestricted database access from the internet exposes sensitive data to potential **breaches**, **unauthorized access**, **data exfiltration**, and malicious attacks. Databases often contain critical business data and should **never** be directly accessible from the public internet.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/",
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/how-tos/create-and-manage-security-groups-and-rules/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the StackIT Portal open Networking > Security Groups and select the affected security group. 2. Locate the ingress rules that allow database ports (3306, 5432, 27017, 6379, 1433, 5984) from 0.0.0.0/0 or ::/0. 3. Delete those rules or restrict their source to the specific application servers or trusted IP ranges. 4. Prefer private networking for database connectivity and do not expose database ports to the internet. 5. Re-run Prowler to confirm the finding is resolved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Restrict database access** to specific application servers or trusted IP ranges. Use **private networks** for database connectivity and implement additional security layers such as VPNs, private endpoints, or application-level authentication.",
+ "Url": "https://hub.prowler.com/check/iaas_security_group_database_unrestricted"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check covers common database ports: MySQL (3306), PostgreSQL (5432), MongoDB (27017), Redis (6379), SQL Server (1433), and CouchDB (5984). Databases should always be placed in private networks and accessed through secure channels."
+}
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.py b/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.py
new file mode 100644
index 0000000000..e777cbb17f
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_database_unrestricted/iaas_security_group_database_unrestricted.py
@@ -0,0 +1,74 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+# Database ports to check
+DATABASE_PORTS = {
+ 3306: "MySQL",
+ 5432: "PostgreSQL",
+ 27017: "MongoDB",
+ 6379: "Redis",
+ 1433: "SQL Server",
+ 5984: "CouchDB",
+}
+
+
+class iaas_security_group_database_unrestricted(Check):
+ """
+ Check if IaaS security groups allow unrestricted database access.
+
+ This check verifies that security groups do not allow database ports
+ (MySQL, PostgreSQL, MongoDB, Redis, SQL Server, CouchDB) access
+ from the public internet (0.0.0.0/0 or ::/0).
+ """
+
+ def execute(self):
+ """
+ Execute the check for all security groups in the StackIT project.
+
+ Returns:
+ list: A list of CheckReportStackIT findings
+ """
+ findings = []
+
+ for security_group in iaas_client.security_groups:
+ if not (iaas_client.scan_unused_services or security_group.in_use):
+ continue
+ exposed_databases = set()
+ exposing_rule = None
+
+ # Check each ingress rule
+ for rule in security_group.rules:
+ # Only check ingress TCP rules that are unrestricted
+ if rule.is_ingress() and rule.is_tcp() and rule.is_unrestricted():
+ # Check if rule allows any database ports
+ for port, db_name in DATABASE_PORTS.items():
+ if rule.includes_port(port):
+ exposed_databases.add(f"{db_name} (port {port})")
+ # Track the first exposing rule for the message
+ if exposed_databases and not exposing_rule:
+ exposing_rule = rule
+
+ # Create a finding report for this security group
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group,
+ )
+
+ if exposed_databases:
+ report.status = "FAIL"
+ databases_list = ", ".join(sorted(exposed_databases))
+ report.status_extended = (
+ f"Security group {security_group.name} allows unrestricted database access "
+ f"to: {databases_list} from {exposing_rule.get_ip_range_display()} via rule {exposing_rule.get_rule_display_name()}."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = f"Security group {security_group.name} does not allow unrestricted database access."
+
+ report.resource_id = security_group.id
+ report.resource_name = security_group.name
+ report.location = security_group.region
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/__init__.py b/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.metadata.json b/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.metadata.json
new file mode 100644
index 0000000000..e2b7cc527c
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "iaas_security_group_rdp_unrestricted",
+ "CheckTitle": "IaaS security groups do not allow unrestricted RDP access",
+ "CheckType": [],
+ "ServiceName": "iaas",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "Security groups should not allow unrestricted RDP access (port `3389`) from the public internet (`0.0.0.0/0` or `::/0`). Unrestricted RDP access increases the attack surface and can lead to **unauthorized access**, **brute force attacks**, and potential system compromise.",
+ "Risk": "Allowing unrestricted RDP access from the internet exposes Windows servers to potential **unauthorized access attempts**, **brute force attacks**, **ransomware**, and security breaches. Attackers can exploit weak credentials or vulnerabilities.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/",
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/how-tos/create-and-manage-security-groups-and-rules/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the StackIT Portal open Networking > Security Groups and select the affected security group. 2. Locate the ingress rule that allows TCP port 3389 from 0.0.0.0/0 or ::/0. 3. Delete that rule or edit its source to the specific IP ranges that require RDP access. 4. If administration from anywhere is required, expose RDP only through a bastion host or VPN instead of the public internet. 5. Re-run Prowler to confirm the finding is resolved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Restrict RDP access** to specific IP addresses or ranges that require administrative access. Use **bastion hosts** or **VPN connections** for secure remote access instead of exposing RDP directly to the internet.",
+ "Url": "https://hub.prowler.com/check/iaas_security_group_rdp_unrestricted"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check focuses on ingress rules that allow RDP (port 3389) from 0.0.0.0/0 or ::/0. Consider implementing network-level authentication and regular security audits."
+}
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.py b/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.py
new file mode 100644
index 0000000000..839fdfabe3
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_rdp_unrestricted/iaas_security_group_rdp_unrestricted.py
@@ -0,0 +1,51 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+
+class iaas_security_group_rdp_unrestricted(Check):
+ """
+ Check if IaaS security groups allow unrestricted RDP access.
+
+ This check verifies that security groups do not allow RDP (port 3389)
+ access from the public internet (0.0.0.0/0 or ::/0).
+ """
+
+ def execute(self):
+ """
+ Execute the check for all security groups in the StackIT project.
+
+ Returns:
+ list: A list of CheckReportStackIT findings
+ """
+ findings = []
+
+ for security_group in iaas_client.security_groups:
+ if not (iaas_client.scan_unused_services or security_group.in_use):
+ continue
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group,
+ )
+ report.status = "PASS"
+ report.status_extended = f"Security group {security_group.name} does not allow unrestricted RDP access."
+ report.resource_id = security_group.id
+ report.resource_name = security_group.name
+ report.location = security_group.region
+
+ for rule in security_group.rules:
+ if (
+ rule.is_ingress()
+ and rule.is_tcp()
+ and rule.is_unrestricted()
+ and rule.includes_port(3389)
+ ):
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Security group {security_group.name} allows unrestricted RDP access (port 3389) "
+ f"from {rule.get_ip_range_display()} via rule {rule.get_rule_display_name()}."
+ )
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/__init__.py b/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.metadata.json b/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.metadata.json
new file mode 100644
index 0000000000..df18970ddf
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "iaas_security_group_ssh_unrestricted",
+ "CheckTitle": "IaaS security groups do not allow unrestricted SSH access",
+ "CheckType": [],
+ "ServiceName": "iaas",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "Security groups should not allow unrestricted SSH access (port `22`) from the public internet (`0.0.0.0/0` or `::/0`). Unrestricted SSH access increases the attack surface and can lead to **unauthorized access**, **brute force attacks**, and potential system compromise.",
+ "Risk": "Allowing unrestricted SSH access from the internet exposes servers to potential **unauthorized access attempts**, **brute force attacks**, and security breaches. Attackers can scan for and exploit weak credentials or vulnerabilities.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/",
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/how-tos/create-and-manage-security-groups-and-rules/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the StackIT Portal open Networking > Security Groups and select the affected security group. 2. Locate the ingress rule that allows TCP port 22 from 0.0.0.0/0 or ::/0. 3. Delete that rule or edit its source to the specific IP ranges that require SSH access. 4. If administration from anywhere is required, expose SSH only through a bastion host or VPN instead of the public internet. 5. Re-run Prowler to confirm the finding is resolved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Restrict SSH access** to specific IP addresses or ranges that require administrative access. Use **bastion hosts** or **VPN connections** for secure remote access instead of exposing SSH directly to the internet.",
+ "Url": "https://hub.prowler.com/check/iaas_security_group_ssh_unrestricted"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check focuses on ingress rules that allow SSH (port 22) from 0.0.0.0/0 or ::/0. Consider implementing additional controls such as multi-factor authentication and regular security audits."
+}
diff --git a/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.py b/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.py
new file mode 100644
index 0000000000..27b9265c15
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_security_group_ssh_unrestricted/iaas_security_group_ssh_unrestricted.py
@@ -0,0 +1,51 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+
+class iaas_security_group_ssh_unrestricted(Check):
+ """
+ Check if IaaS security groups allow unrestricted SSH access.
+
+ This check verifies that security groups do not allow SSH (port 22)
+ access from the public internet (0.0.0.0/0 or ::/0).
+ """
+
+ def execute(self):
+ """
+ Execute the check for all security groups in the StackIT project.
+
+ Returns:
+ list: A list of CheckReportStackIT findings
+ """
+ findings = []
+
+ for security_group in iaas_client.security_groups:
+ if not (iaas_client.scan_unused_services or security_group.in_use):
+ continue
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=security_group,
+ )
+ report.status = "PASS"
+ report.status_extended = f"Security group {security_group.name} does not allow unrestricted SSH access."
+ report.resource_id = security_group.id
+ report.resource_name = security_group.name
+ report.location = security_group.region
+
+ for rule in security_group.rules:
+ if (
+ rule.is_ingress()
+ and rule.is_tcp()
+ and rule.is_unrestricted()
+ and rule.includes_port(22)
+ ):
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Security group {security_group.name} allows unrestricted SSH access (port 22) "
+ f"from {rule.get_ip_range_display()} via rule {rule.get_rule_display_name()}."
+ )
+ break
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/__init__.py b/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.metadata.json b/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.metadata.json
new file mode 100644
index 0000000000..a52c0c01fe
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "iaas_server_public_ip_attached",
+ "CheckTitle": "IaaS servers do not have public IP addresses directly attached",
+ "CheckType": [],
+ "ServiceName": "iaas",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "network",
+ "Description": "Servers should not have public IP addresses directly attached to their network interfaces unless strictly required. A public IP exposes the server to inbound traffic from the internet on all ports not blocked by a security group, increasing the attack surface.",
+ "Risk": "**Direct internet exposure.** A server with a directly attached public IP can be reached from the internet. If its security groups allow broad inbound traffic, this exposure can enable unauthorized access, data exfiltration, or server compromise.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/network/core-networking/public-ip-address/",
+ "https://docs.stackit.cloud/products/network/core-networking/security-groups/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the StackIT Portal open Networking > Public IPs and identify the IP attached to the affected server's network interface. 2. Detach the public IP from the server. 3. Use a load balancer for internet-facing workloads or a bastion host / VPN for administrative access. 4. Re-run Prowler to confirm the finding is resolved.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "**Remove direct public exposure.** Detach the public IP from the server network interface unless it is strictly required. Route internet-facing workloads through a load balancer, and use a bastion host or VPN for administrative access.",
+ "Url": "https://hub.prowler.com/check/iaas_server_public_ip_attached"
+ }
+ },
+ "Categories": [
+ "internet-exposed"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "This check flags servers that have a public IP attached directly to a NIC. Evaluate whether internet exposure is intentional and whether appropriate security groups are in place."
+}
diff --git a/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.py b/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.py
new file mode 100644
index 0000000000..966f385239
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_server_public_ip_attached/iaas_server_public_ip_attached.py
@@ -0,0 +1,43 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.iaas.iaas_client import iaas_client
+
+
+class iaas_server_public_ip_attached(Check):
+ """
+ Check if IaaS servers have public IP addresses directly attached.
+
+ This check verifies that servers do not have a public IP address
+ directly attached to their network interfaces, which would expose
+ them to inbound traffic from the internet.
+ """
+
+ def execute(self):
+ """
+ Execute the check for all servers in the StackIT project.
+
+ Returns:
+ list: A list of CheckReportStackIT findings
+ """
+ findings = []
+
+ for server in iaas_client.servers:
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=server,
+ )
+
+ if server.has_public_ip:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Server {server.name} has a public IP address directly attached, "
+ f"exposing it to the internet."
+ )
+ else:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Server {server.name} does not have a public IP address attached."
+ )
+
+ findings.append(report)
+
+ return findings
diff --git a/prowler/providers/stackit/services/iaas/iaas_service.py b/prowler/providers/stackit/services/iaas/iaas_service.py
new file mode 100644
index 0000000000..71e8ec0ae1
--- /dev/null
+++ b/prowler/providers/stackit/services/iaas/iaas_service.py
@@ -0,0 +1,608 @@
+from typing import Optional
+
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.stackit.stackit_provider import StackitProvider, suppress_stderr
+
+
+class IaaSService:
+ """
+ StackIT IaaS Service class to handle security group operations.
+
+ This service uses the StackIT Python SDK to access IaaS resources.
+ Authentication is delegated to the SDK, which signs the RSA challenge
+ in the configured service account key and refreshes access tokens
+ internally for the life of the scan.
+ """
+
+ def __init__(self, provider: StackitProvider):
+ """
+ Initialize the IaaS service.
+
+ Args:
+ provider: The StackIT provider instance
+ """
+ self.provider = provider
+ self.project_id = provider.identity.project_id
+ self.service_account_key_path = provider.session.get("service_account_key_path")
+ self.scan_unused_services = provider.scan_unused_services
+
+ # Generate regional clients (AWS pattern)
+ self.regional_clients = provider.generate_regional_clients("iaas")
+ self.audited_regions = provider.identity.audited_regions
+
+ # Initialize security groups list
+ self.security_groups: list[SecurityGroup] = []
+
+ # Initialize server NICs list and used security group IDs
+ self.server_nics: list = []
+ self.in_use_sg_ids: set[str] = set()
+
+ # Initialize server list and supporting indices
+ self.servers: list[Server] = []
+ self._nic_device_index: dict[str, str] = {} # nic_id → server_id
+ self._public_ip_server_ids: set[str] = set()
+
+ # Fetch resources from all regions
+ self._fetch_all_regions()
+ self._log_skipped_security_groups()
+
+ def _log_skipped_security_groups(self):
+ """Explain an empty report when every security group is skipped.
+
+ Following the same convention as the rest of Prowler, security group
+ checks only evaluate groups that are in use (attached to a network
+ interface) unless ``--scan-unused-services`` is set. When a project
+ has security groups but none are attached, every check returns no
+ finding, which looks like "nothing was scanned". Emit an explicit
+ hint so the empty report is not mistaken for a failure.
+ """
+ if (
+ not self.scan_unused_services
+ and self.security_groups
+ and not any(sg.in_use for sg in self.security_groups)
+ ):
+ logger.info(
+ f"{len(self.security_groups)} StackIT security group(s) were "
+ f"found but none are attached to a network interface, so all "
+ f"of them are skipped and no finding is produced. Re-run with "
+ f"--scan-unused-services to audit security groups that are "
+ f"not currently in use."
+ )
+
+ def _fetch_all_regions(self):
+ """Fetch resources from all audited regions.
+
+ A project is not necessarily provisioned in every StackIT region. A
+ region where the project does not exist answers the IaaS endpoints
+ with HTTP 404 (``resource not found: project``). That is expected, so
+ the region is skipped and the scan continues with the remaining
+ regions instead of aborting (which previously left every check
+ failing to load and produced an empty, misleading report).
+
+ Credential and permission failures (401/403) still propagate via
+ ``handle_api_error`` so a misconfigured account fails loudly.
+ """
+ for region, client in self.regional_clients.items():
+ try:
+ self._list_server_nics(client, region)
+ self._list_security_groups(client, region)
+ self._list_public_ips(client, region)
+ self._list_servers(client, region)
+ except Exception as error:
+ if getattr(error, "status", None) == 404:
+ logger.info(
+ f"StackIT project {self.project_id} has no IaaS "
+ f"presence in region {region} (404 resource not "
+ f"found); skipping this region."
+ )
+ continue
+ raise
+
+ @staticmethod
+ def _extract_items(response, endpoint_name: str) -> list:
+ """Extract the items list from a StackIT SDK response.
+
+ Handles three response shapes safely:
+ - SDK model exposing an ``items`` attribute (not the ``dict.items`` method)
+ - Raw ``dict`` with an ``"items"`` key
+ - Plain ``list``
+
+ ``isinstance(response, dict)`` is checked first because ``dict`` has an
+ ``items`` *method*; ``hasattr(response, "items")`` is otherwise True for
+ plain dicts and silently returns the bound method.
+ """
+ if isinstance(response, dict):
+ return response.get("items", [])
+ if isinstance(response, list):
+ return response
+ items_attr = getattr(response, "items", None)
+ if items_attr is not None and not callable(items_attr):
+ return items_attr
+ logger.warning(
+ f"Unexpected response type from {endpoint_name}: {type(response)}"
+ )
+ return []
+
+ @staticmethod
+ def _get_item_field(item, *keys, default=None):
+ """Read a field from an SDK model (attribute) or a raw ``dict`` (key).
+
+ ``_extract_items`` already yields either SDK models or raw dicts, so the
+ correlation logic must read fields from both shapes. Multiple key aliases
+ are accepted so snake_case SDK attributes and camelCase API/dict keys are
+ both supported (e.g. ``network_interface`` / ``networkInterface``).
+ Returns the first non-None match, otherwise ``default``.
+ """
+ if isinstance(item, dict):
+ for key in keys:
+ value = item.get(key)
+ if value is not None:
+ return value
+ return default
+ for key in keys:
+ value = getattr(item, key, None)
+ if value is not None:
+ return value
+ return default
+
+ def _handle_api_call(self, api_function, *args, **kwargs):
+ """
+ Centralized API call handler with authentication error detection.
+
+ Args:
+ api_function: The API function to call
+ *args: Positional arguments to pass to the API function
+ **kwargs: Keyword arguments to pass to the API function
+
+ Returns:
+ The API response
+
+ Raises:
+ StackITInvalidTokenError: If authentication fails (401)
+ """
+ try:
+ # Suppress StackIT SDK stderr messages during API calls
+ with suppress_stderr():
+ return api_function(*args, **kwargs)
+ except Exception as e:
+ # Use centralized error handler from provider
+ self.provider.handle_api_error(e)
+ raise
+
+ def _list_security_groups(self, client, region: str):
+ """
+ List all security groups in the StackIT project and fetch their rules.
+
+ This method populates the self.security_groups list with SecurityGroup
+ objects containing information about each security group and its rules.
+ """
+ if not client:
+ logger.warning(
+ f"Cannot list security groups in {region}: StackIT IaaS client not available"
+ )
+ return
+
+ # Call the list security groups API with centralized error handling
+ response = self._handle_api_call(
+ client.list_security_groups, project_id=self.project_id, region=region
+ )
+
+ # Extract security groups from response
+ security_groups_list = self._extract_items(response, "list_security_groups")
+
+ # Process each security group
+ for sg_data in security_groups_list:
+ try:
+ # Extract security group information
+ if hasattr(sg_data, "id"):
+ sg_id = sg_data.id
+ sg_name = getattr(sg_data, "name", sg_id)
+ elif isinstance(sg_data, dict):
+ sg_id = sg_data.get("id", "")
+ sg_name = sg_data.get("name", sg_id)
+ else:
+ logger.warning(
+ f"Unexpected security group data type: {type(sg_data)}"
+ )
+ continue
+
+ except Exception as e:
+ logger.error(f"Error processing security group: {e}")
+ continue
+
+ # Get security group rules after local parsing succeeds so API errors
+ # from the rules endpoint propagate instead of being downgraded.
+ rules = self._list_security_group_rules(client, region, sg_id)
+
+ security_group = SecurityGroup(
+ id=sg_id,
+ name=sg_name,
+ project_id=self.project_id,
+ region=region,
+ rules=rules,
+ # in_use_sg_ids is normalized to str; the SDK returns the NIC
+ # security group references as uuid.UUID while the security
+ # group id is a str, so compare on the string form.
+ in_use=str(sg_id) in self.in_use_sg_ids,
+ )
+ self.security_groups.append(security_group)
+
+ logger.info(
+ f"Successfully listed {len(security_groups_list)} security groups in {region}"
+ )
+
+ def _list_security_group_rules(
+ self, client, region: str, security_group_id: str
+ ) -> list["SecurityGroupRule"]:
+ """
+ List all rules for a specific security group.
+
+ Args:
+ client: The StackIT IaaS client
+ region: The region of the security group
+ security_group_id: The ID of the security group
+
+ Returns:
+ list: List of SecurityGroupRule objects
+ """
+ rules = []
+ # Get security group rules via SDK
+ response = self._handle_api_call(
+ client.list_security_group_rules,
+ project_id=self.project_id,
+ region=region,
+ security_group_id=security_group_id,
+ )
+
+ # Extract rules from response
+ rules_list = self._extract_items(response, "list_security_group_rules")
+
+ # Process each rule
+ for rule_data in rules_list:
+ try:
+ if hasattr(rule_data, "id"):
+ # Extract protocol name from Protocol object
+ protocol_obj = getattr(rule_data, "protocol", None)
+ protocol_name = None
+ if protocol_obj and hasattr(protocol_obj, "name"):
+ protocol_name = protocol_obj.name
+
+ # Extract port range from PortRange object
+ port_range_obj = getattr(rule_data, "port_range", None)
+ port_min = None
+ port_max = None
+ if port_range_obj:
+ if hasattr(port_range_obj, "min"):
+ port_min = port_range_obj.min
+ if hasattr(port_range_obj, "max"):
+ port_max = port_range_obj.max
+
+ rule = SecurityGroupRule(
+ id=getattr(rule_data, "id", ""),
+ direction=getattr(rule_data, "direction", ""),
+ protocol=protocol_name,
+ ip_range=getattr(rule_data, "ip_range", None),
+ port_range_min=port_min,
+ port_range_max=port_max,
+ description=getattr(rule_data, "description", None),
+ remote_security_group_id=getattr(
+ rule_data, "remote_security_group_id", None
+ ),
+ )
+ elif isinstance(rule_data, dict):
+ # Handle dict response (if API returns dict instead of objects)
+ protocol_data = rule_data.get("protocol")
+ protocol_name = None
+ if isinstance(protocol_data, dict):
+ protocol_name = protocol_data.get("name")
+ elif isinstance(protocol_data, str):
+ protocol_name = protocol_data
+
+ port_range_data = rule_data.get("port_range")
+ port_min = None
+ port_max = None
+ if isinstance(port_range_data, dict):
+ port_min = port_range_data.get("min")
+ port_max = port_range_data.get("max")
+
+ rule = SecurityGroupRule(
+ id=rule_data.get("id", ""),
+ direction=rule_data.get("direction", ""),
+ protocol=protocol_name,
+ ip_range=rule_data.get("ip_range"),
+ port_range_min=port_min,
+ port_range_max=port_max,
+ description=rule_data.get("description"),
+ remote_security_group_id=rule_data.get(
+ "remote_security_group_id"
+ ),
+ )
+ else:
+ continue
+
+ rules.append(rule)
+ logger.debug(
+ f"Parsed rule: id={rule.id}, direction={rule.direction}, "
+ f"protocol={rule.protocol}, ip_range={rule.ip_range}, "
+ f"ports={rule.port_range_min}-{rule.port_range_max}, "
+ f"remote_sg={rule.remote_security_group_id}"
+ )
+
+ except Exception as e:
+ logger.debug(f"Error processing rule: {e}")
+ continue
+
+ return rules
+
+ def _list_server_nics(self, client, region: str):
+ """
+ List all server network interfaces (NICs) in the StackIT project.
+
+ This method fetches all NICs and determines which security groups are
+ actively in use by checking which security groups are attached to any NIC.
+ """
+ if not client:
+ logger.warning(
+ f"Cannot list server NICs in {region}: StackIT IaaS client not available"
+ )
+ return
+
+ # Call the list project NICs API with centralized error handling
+ response = self._handle_api_call(
+ client.list_project_nics, project_id=self.project_id, region=region
+ )
+
+ # Extract NICs from response
+ nics_list = self._extract_items(response, "list_project_nics")
+
+ self.server_nics.extend(nics_list)
+
+ # A security group is "in use" when attached to any NIC
+ used_sg_ids = self._get_used_security_group_ids(nics_list)
+ self.in_use_sg_ids.update(used_sg_ids)
+
+ # Build nic_id → server_id index for public IP cross-reference
+ for nic in nics_list:
+ try:
+ nic_id = str(self._get_item_field(nic, "id") or "")
+ device = self._get_item_field(nic, "device")
+ if nic_id and device:
+ self._nic_device_index[nic_id] = str(device)
+ except Exception as e:
+ logger.debug(f"Error indexing NIC device: {e}")
+ continue
+
+ logger.info(
+ f"Successfully listed {len(nics_list)} NICs in {region}. "
+ f"Found {len(used_sg_ids)} security groups attached to NICs."
+ )
+
+ def _list_public_ips(self, client, region: str):
+ """
+ List all public IPs in the project and record which servers have one attached.
+
+ A public IP is considered attached to a server when its ``network_interface``
+ field (a NIC UUID) matches a NIC whose ``device`` field points to a server.
+ The result is stored in ``self._public_ip_server_ids`` so that
+ ``_list_servers`` can set ``has_public_ip`` when creating Server objects.
+ """
+ if not client:
+ logger.warning(
+ f"Cannot list public IPs in {region}: StackIT IaaS client not available"
+ )
+ return
+
+ response = self._handle_api_call(
+ client.list_public_ips, project_id=self.project_id, region=region
+ )
+ ips_list = self._extract_items(response, "list_public_ips")
+
+ for ip_data in ips_list:
+ try:
+ network_interface = self._get_item_field(
+ ip_data, "network_interface", "networkInterface"
+ )
+ if network_interface is None:
+ continue
+ server_id = self._nic_device_index.get(str(network_interface))
+ if server_id:
+ self._public_ip_server_ids.add(server_id)
+ except Exception as e:
+ logger.debug(f"Error processing public IP: {e}")
+ continue
+
+ logger.info(f"Successfully listed {len(ips_list)} public IPs in {region}")
+
+ def _list_servers(self, client, region: str):
+ """
+ List all servers in the project and populate ``self.servers``.
+
+ ``has_public_ip`` is set to True for any server whose ID appears in
+ ``self._public_ip_server_ids`` (populated by ``_list_public_ips``).
+ """
+ if not client:
+ logger.warning(
+ f"Cannot list servers in {region}: StackIT IaaS client not available"
+ )
+ return
+
+ response = self._handle_api_call(
+ client.list_servers, project_id=self.project_id, region=region
+ )
+ servers_list = self._extract_items(response, "list_servers")
+
+ for server_data in servers_list:
+ try:
+ server_id = str(self._get_item_field(server_data, "id") or "")
+ server_name = self._get_item_field(server_data, "name") or server_id
+ server = Server(
+ id=server_id,
+ name=server_name,
+ project_id=self.project_id,
+ region=region,
+ has_public_ip=server_id in self._public_ip_server_ids,
+ )
+ self.servers.append(server)
+ except Exception as e:
+ logger.error(f"Error processing server: {e}")
+ continue
+
+ logger.info(f"Successfully listed {len(servers_list)} servers in {region}")
+
+ def _get_used_security_group_ids(self, nics_list) -> set[str]:
+ """
+ Get the set of security group IDs that are actively attached to any NIC.
+
+ Returns:
+ set[str]: Set of security group IDs that are attached to at least one NIC
+ """
+ used_sg_ids = set()
+
+ for nic in nics_list:
+ try:
+ # Extract security groups from NIC. The SDK model exposes them
+ # as ``security_groups``; a raw dict uses the camelCase
+ # ``securityGroups`` key (falling back to snake_case).
+ if hasattr(nic, "security_groups"):
+ sg_list = nic.security_groups
+ elif isinstance(nic, dict):
+ sg_list = nic.get("securityGroups", nic.get("security_groups", []))
+ else:
+ continue
+
+ if sg_list:
+ for sg_id in sg_list:
+ if sg_id:
+ # The SDK returns these references as uuid.UUID
+ # while the security group id is a str; normalize
+ # to str so the membership test in
+ # _list_security_groups matches.
+ used_sg_ids.add(str(sg_id))
+
+ except Exception as e:
+ logger.debug(f"Error extracting security groups from NIC: {e}")
+ continue
+
+ return used_sg_ids
+
+
+class SecurityGroupRule(BaseModel):
+ """
+ Represents a Security Group Rule.
+
+ Attributes:
+ id: The unique identifier of the rule
+ direction: The direction of the rule (ingress/egress)
+ protocol: The protocol (tcp/udp/icmp/all) - can be None for some rules
+ ip_range: The IP range (CIDR notation) - can be None for some rules
+ port_range_min: The minimum port number
+ port_range_max: The maximum port number
+ description: The user-defined description/name of the rule (optional)
+ remote_security_group_id: The ID of a security group to allow traffic from (optional)
+ """
+
+ id: str
+ direction: str
+ protocol: Optional[str] = None
+ ip_range: Optional[str] = None
+ port_range_min: Optional[int] = None
+ port_range_max: Optional[int] = None
+ description: Optional[str] = None
+ remote_security_group_id: Optional[str] = None
+
+ def is_unrestricted(self) -> bool:
+ """Check if the rule allows access from anywhere (0.0.0.0/0, ::/0, or None for unrestricted)."""
+ # If remote_security_group_id is set, the rule only allows traffic from that security group
+ # This is NOT unrestricted access - it's restricted to instances in the same security group
+ if self.remote_security_group_id is not None:
+ return False
+
+ # None means no IP restriction (allows all sources) - this is unrestricted!
+ if self.ip_range is None:
+ return True
+ # Explicit unrestricted ranges
+ return self.ip_range in ["0.0.0.0/0", "::/0"]
+
+ def is_ingress(self) -> bool:
+ """Check if the rule is an ingress rule."""
+ if not self.direction:
+ return False
+ return self.direction.lower() == "ingress"
+
+ def is_tcp(self) -> bool:
+ """Check if the rule is TCP protocol."""
+ # None means all protocols (including TCP) - treat as TCP-applicable
+ if self.protocol is None:
+ return True
+ return self.protocol.lower() in ["tcp", "all"]
+
+ def includes_port(self, port: int) -> bool:
+ """Check if the rule includes a specific port."""
+ if self.port_range_min is None or self.port_range_max is None:
+ # If no port range specified, rule applies to all ports
+ return True
+ return self.port_range_min <= port <= self.port_range_max
+
+ def get_ip_range_display(self) -> str:
+ """
+ Get a user-friendly display string for the IP range.
+
+ Returns:
+ str: Human-readable IP range description
+ """
+ if self.ip_range is None:
+ return "anywhere (0.0.0.0/0, ::/0)"
+ return self.ip_range
+
+ def get_rule_display_name(self) -> str:
+ """
+ Get a user-friendly display name for the rule.
+
+ Returns:
+ str: Rule description if available, otherwise rule ID
+ """
+ if self.description:
+ return f"{self.description} ({self.id})"
+ return f"{self.id}"
+
+
+class SecurityGroup(BaseModel):
+ """
+ Represents a StackIT IaaS Security Group.
+
+ Attributes:
+ id: The unique identifier of the security group
+ name: The name of the security group
+ project_id: The StackIT project ID containing the security group
+ region: The region where the security group is located
+ rules: List of security group rules
+ in_use: Whether the security group is actively attached to any resources
+ """
+
+ id: str
+ name: str
+ project_id: str
+ region: str
+ rules: list[SecurityGroupRule] = []
+ in_use: bool = False
+
+
+class Server(BaseModel):
+ """
+ Represents a StackIT IaaS Server.
+
+ Attributes:
+ id: The unique identifier of the server
+ name: The name of the server
+ project_id: The StackIT project ID containing the server
+ region: The region where the server is located
+ has_public_ip: Whether a public IP is directly attached to any of the server's NICs
+ """
+
+ id: str
+ name: str
+ project_id: str
+ region: str
+ has_public_ip: bool = False
diff --git a/prowler/providers/stackit/services/objectstorage/__init__.py b/prowler/providers/stackit/services/objectstorage/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/__init__.py b/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.metadata.json b/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.metadata.json
new file mode 100644
index 0000000000..38da16c5fa
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "objectstorage_access_key_expiration",
+ "CheckTitle": "ObjectStorage access keys should have an expiration date",
+ "CheckType": [],
+ "ServiceName": "objectstorage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "IAM",
+ "Description": "**ObjectStorage access keys** should have an explicit expiration date. Long-lived credentials increase the blast radius of a credential compromise because they cannot expire on their own. Setting an expiration date enforces periodic rotation and limits the exposure window if a key is leaked.",
+ "Risk": "If an **ObjectStorage access key** is leaked, stolen, or forgotten without an expiration date, it remains usable indefinitely. An attacker can retain persistent access to object storage resources until the key is manually revoked.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/storage/object-storage/",
+ "https://docs.stackit.cloud/products/storage/object-storage/how-tos/create-and-delete-object-storage-credentials/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "1. In the STACKIT Portal navigate to Object Storage > Access Keys. 2. Delete the non-expiring access key. 3. Create a new access key with an expiration date appropriate for your rotation policy (e.g. 90 days). 4. Update all applications and services that use the old key with the new credentials.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Create **ObjectStorage access keys** with an explicit expiration date and establish a rotation process. Delete non-expiring keys and replace them with time-limited credentials. A rotation period of **90 days or less** is recommended.",
+ "Url": "https://hub.prowler.com/check/objectstorage_access_key_expiration"
+ }
+ },
+ "Categories": [
+ "identity-access"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Access keys are scoped to credentials groups. This check evaluates all access keys across all credentials groups in the project."
+}
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.py b/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.py
new file mode 100644
index 0000000000..2fb49ac725
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_access_key_expiration/objectstorage_access_key_expiration.py
@@ -0,0 +1,27 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.objectstorage.objectstorage_client import (
+ objectstorage_client,
+)
+
+
+class objectstorage_access_key_expiration(Check):
+ def execute(self):
+ findings = []
+ for key in objectstorage_client.access_keys:
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=key,
+ )
+ report.resource_id = key.key_id
+ report.resource_name = key.display_name
+ report.location = key.region
+
+ if key.has_expiration():
+ report.status = "PASS"
+ report.status_extended = f"Access key {key.display_name} has an expiration date set ({key.expires})."
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Access key {key.display_name} has no expiration date and never rotates."
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/__init__.py b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.metadata.json b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.metadata.json
new file mode 100644
index 0000000000..cd587c72da
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.metadata.json
@@ -0,0 +1,37 @@
+{
+ "Provider": "stackit",
+ "CheckID": "objectstorage_bucket_object_lock_enabled",
+ "CheckTitle": "ObjectStorage buckets should have S3 Object Lock enabled",
+ "CheckType": [],
+ "ServiceName": "objectstorage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "high",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "**S3 Object Lock** prevents objects from being deleted or overwritten for a fixed period or indefinitely. Enabling it protects against accidental deletion and ransomware by enforcing a **write-once-read-many (WORM)** model. Object Lock can only be enabled when the bucket is created.",
+ "Risk": "Without **Object Lock**, objects can be deleted or overwritten at any time, increasing the risk of data loss from accidental deletion, malicious actors, or ransomware. Backups and compliance data are particularly vulnerable.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/storage/object-storage/",
+ "https://docs.stackit.cloud/products/storage/object-storage/how-tos/object-lock-bucket/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "Object Lock must be enabled at bucket creation time and cannot be enabled on an existing bucket. Create a new bucket with Object Lock enabled and migrate your data to it.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Create **ObjectStorage buckets** with S3 Object Lock enabled for workloads that require data immutability, compliance archiving, or ransomware protection. Object Lock cannot be retroactively enabled on existing buckets.",
+ "Url": "https://hub.prowler.com/check/objectstorage_bucket_object_lock_enabled"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [],
+ "Notes": "Object Lock can only be activated at bucket creation. Buckets without Object Lock are not necessarily misconfigured — evaluate based on the sensitivity and compliance requirements of the stored data."
+}
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.py b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.py
new file mode 100644
index 0000000000..89a3c1d3fb
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_object_lock_enabled/objectstorage_bucket_object_lock_enabled.py
@@ -0,0 +1,31 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.objectstorage.objectstorage_client import (
+ objectstorage_client,
+)
+
+
+class objectstorage_bucket_object_lock_enabled(Check):
+ def execute(self):
+ findings = []
+ for bucket in objectstorage_client.buckets:
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=bucket,
+ )
+ report.resource_id = bucket.name
+ report.resource_name = bucket.name
+ report.location = bucket.region
+
+ if bucket.object_lock_enabled:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Bucket {bucket.name} has S3 Object Lock enabled."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = (
+ f"Bucket {bucket.name} does not have S3 Object Lock enabled."
+ )
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/__init__.py b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.metadata.json b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.metadata.json
new file mode 100644
index 0000000000..44088e5889
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.metadata.json
@@ -0,0 +1,39 @@
+{
+ "Provider": "stackit",
+ "CheckID": "objectstorage_bucket_retention_policy",
+ "CheckTitle": "ObjectStorage buckets should have a default retention policy configured",
+ "CheckType": [],
+ "ServiceName": "objectstorage",
+ "SubServiceName": "",
+ "ResourceIdTemplate": "",
+ "Severity": "medium",
+ "ResourceType": "NotDefined",
+ "ResourceGroup": "storage",
+ "Description": "An **ObjectStorage default retention policy** automatically applies a minimum retention period to every object uploaded to the bucket, preventing deletion or overwriting before the period expires. Without it, objects can be removed immediately after upload, undermining compliance and data durability requirements.",
+ "Risk": "Buckets without a **default retention policy** offer no automatic protection against premature object deletion. Compliance data, audit logs, and backups may be deleted before their required retention period elapses.",
+ "RelatedUrl": "",
+ "AdditionalURLs": [
+ "https://docs.stackit.cloud/products/storage/object-storage/",
+ "https://docs.stackit.cloud/products/storage/object-storage/how-tos/object-lock-default-retention/"
+ ],
+ "Remediation": {
+ "Code": {
+ "CLI": "",
+ "NativeIaC": "",
+ "Other": "Use the STACKIT Object Storage API or Portal to set a default retention policy on the bucket. Choose COMPLIANCE mode for strict immutability or GOVERNANCE mode to allow privileged users to override the policy.",
+ "Terraform": ""
+ },
+ "Recommendation": {
+ "Text": "Configure a **default retention policy** on every bucket that stores compliance-relevant or sensitive data. Choose `COMPLIANCE` mode for regulatory requirements and `GOVERNANCE` mode when administrative overrides are acceptable.",
+ "Url": "https://hub.prowler.com/check/objectstorage_bucket_retention_policy"
+ }
+ },
+ "Categories": [
+ "resilience"
+ ],
+ "DependsOn": [],
+ "RelatedTo": [
+ "objectstorage_bucket_object_lock_enabled"
+ ],
+ "Notes": "A default retention policy requires Object Lock to be enabled on the bucket. Buckets without Object Lock cannot have a retention policy."
+}
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.py b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.py
new file mode 100644
index 0000000000..a9dbc7ed2b
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_bucket_retention_policy/objectstorage_bucket_retention_policy.py
@@ -0,0 +1,30 @@
+from prowler.lib.check.models import Check, CheckReportStackIT
+from prowler.providers.stackit.services.objectstorage.objectstorage_client import (
+ objectstorage_client,
+)
+
+
+class objectstorage_bucket_retention_policy(Check):
+ def execute(self):
+ findings = []
+ for bucket in objectstorage_client.buckets:
+ report = CheckReportStackIT(
+ metadata=self.metadata(),
+ resource=bucket,
+ )
+ report.resource_id = bucket.name
+ report.resource_name = bucket.name
+ report.location = bucket.region
+
+ if bucket.retention_days and bucket.retention_days > 0:
+ report.status = "PASS"
+ report.status_extended = (
+ f"Bucket {bucket.name} has a default retention policy of "
+ f"{bucket.retention_days} day(s) in {bucket.retention_mode} mode."
+ )
+ else:
+ report.status = "FAIL"
+ report.status_extended = f"Bucket {bucket.name} does not have a default retention policy configured."
+
+ findings.append(report)
+ return findings
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_client.py b/prowler/providers/stackit/services/objectstorage/objectstorage_client.py
new file mode 100644
index 0000000000..56cdbfd0bf
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_client.py
@@ -0,0 +1,6 @@
+from prowler.providers.common.provider import Provider
+from prowler.providers.stackit.services.objectstorage.objectstorage_service import (
+ ObjectStorageService,
+)
+
+objectstorage_client = ObjectStorageService(Provider.get_global_provider())
diff --git a/prowler/providers/stackit/services/objectstorage/objectstorage_service.py b/prowler/providers/stackit/services/objectstorage/objectstorage_service.py
new file mode 100644
index 0000000000..e37545ec24
--- /dev/null
+++ b/prowler/providers/stackit/services/objectstorage/objectstorage_service.py
@@ -0,0 +1,306 @@
+import json
+from datetime import datetime, timezone
+from typing import Optional
+
+from pydantic.v1 import BaseModel
+
+from prowler.lib.logger import logger
+from prowler.providers.stackit.stackit_provider import StackitProvider, suppress_stderr
+
+
+class ObjectStorageService:
+ def __init__(self, provider: StackitProvider):
+ self.provider = provider
+ self.project_id = provider.identity.project_id
+ self.regional_clients = provider.generate_regional_clients("objectstorage")
+
+ self.buckets: list[Bucket] = []
+ self.access_keys: list[AccessKey] = []
+
+ self._fetch_all_regions()
+
+ def _fetch_all_regions(self):
+ for region, client in self.regional_clients.items():
+ try:
+ self._list_buckets(client, region)
+ self._list_access_keys(client, region)
+ except Exception as error:
+ if getattr(error, "status", None) == 404:
+ logger.info(
+ f"StackIT project {self.project_id} has no ObjectStorage "
+ f"presence in region {region}; skipping."
+ )
+ continue
+ raise
+
+ def _handle_api_call(self, api_function, *args, **kwargs):
+ try:
+ with suppress_stderr():
+ return api_function(*args, **kwargs)
+ except Exception as e:
+ self.provider.handle_api_error(e)
+ raise
+
+ def _list_buckets(self, client, region: str):
+ response = self._handle_api_call(
+ client.list_buckets, project_id=self.project_id, region=region
+ )
+
+ buckets_list = getattr(response, "buckets", None) or []
+ if isinstance(response, dict):
+ buckets_list = response.get("buckets", [])
+
+ for bucket_data in buckets_list:
+ try:
+ if hasattr(bucket_data, "name"):
+ name = bucket_data.name
+ object_lock_enabled = getattr(
+ bucket_data, "object_lock_enabled", False
+ )
+ elif isinstance(bucket_data, dict):
+ name = bucket_data.get("name", "")
+ object_lock_enabled = bucket_data.get("objectLockEnabled", False)
+ else:
+ continue
+ except Exception as e:
+ logger.error(f"Error processing bucket: {e}")
+ continue
+
+ retention_days, retention_mode = self._get_default_retention(
+ client, region, name
+ )
+
+ self.buckets.append(
+ Bucket(
+ name=name,
+ region=region,
+ project_id=self.project_id,
+ object_lock_enabled=object_lock_enabled,
+ retention_days=retention_days,
+ retention_mode=retention_mode,
+ )
+ )
+
+ logger.info(f"Listed {len(buckets_list)} buckets in {region}")
+
+ def _get_default_retention(
+ self, client, region: str, bucket_name: str
+ ) -> tuple[Optional[int], Optional[str]]:
+ try:
+ response = self._handle_api_call(
+ client.get_default_retention,
+ project_id=self.project_id,
+ region=region,
+ bucket_name=bucket_name,
+ )
+ days = getattr(response, "days", None)
+ mode = getattr(response, "mode", None)
+ if isinstance(response, dict):
+ days = response.get("days")
+ mode = response.get("mode")
+ return days, str(mode) if mode else None
+ except Exception as e:
+ if getattr(e, "status", None) == 404:
+ return None, None
+ raise
+
+ def _list_access_keys(self, client, region: str):
+ credentials_groups_response = self._handle_api_call(
+ client.list_credentials_groups, project_id=self.project_id, region=region
+ )
+
+ credentials_groups = (
+ getattr(credentials_groups_response, "credentials_groups", None) or []
+ )
+ if isinstance(credentials_groups_response, dict):
+ credentials_groups = credentials_groups_response.get(
+ "credentialsGroups",
+ credentials_groups_response.get("credentials_groups", []),
+ )
+
+ total_keys = 0
+
+ for credentials_group_data in credentials_groups:
+ try:
+ if isinstance(credentials_group_data, dict):
+ credentials_group_id = credentials_group_data.get(
+ "id",
+ credentials_group_data.get(
+ "groupId",
+ credentials_group_data.get("credentialsGroupId", ""),
+ ),
+ )
+ credentials_group_name = credentials_group_data.get(
+ "displayName",
+ credentials_group_data.get("name", credentials_group_id),
+ )
+ else:
+ credentials_group_id = (
+ getattr(credentials_group_data, "id", None)
+ or getattr(credentials_group_data, "group_id", None)
+ or getattr(credentials_group_data, "credentials_group_id", "")
+ )
+ credentials_group_name = getattr(
+ credentials_group_data,
+ "display_name",
+ getattr(credentials_group_data, "name", credentials_group_id),
+ )
+ except Exception as e:
+ logger.error(f"Error processing credentials group: {e}")
+ continue
+
+ if not credentials_group_id:
+ continue
+
+ response = self._list_access_keys_response(
+ client, region, credentials_group_id
+ )
+ keys_list = self._extract_access_keys(response)
+
+ for key_data in keys_list:
+ try:
+ if hasattr(key_data, "key_id"):
+ key_id = key_data.key_id
+ display_name = getattr(key_data, "display_name", key_id)
+ expires = getattr(key_data, "expires", None)
+ elif isinstance(key_data, dict):
+ key_id = key_data.get("keyId", key_data.get("key_id", ""))
+ display_name = key_data.get(
+ "displayName", key_data.get("display_name", key_id)
+ )
+ expires = key_data.get("expires")
+ else:
+ continue
+
+ if not key_id:
+ continue
+
+ self.access_keys.append(
+ AccessKey(
+ key_id=key_id,
+ display_name=display_name,
+ expires=expires,
+ region=region,
+ project_id=self.project_id,
+ credentials_group_id=credentials_group_id,
+ credentials_group_name=credentials_group_name,
+ )
+ )
+ except Exception as e:
+ logger.error(f"Error processing access key: {e}")
+ continue
+
+ total_keys += len(keys_list)
+
+ logger.info(f"Listed {total_keys} access keys in {region}")
+
+ def _list_access_keys_response(
+ self, client, region: str, credentials_group_id: str
+ ):
+ raw_method = None
+ if callable(
+ getattr(type(client), "list_access_keys_without_preload_content", None)
+ ):
+ raw_method = client.list_access_keys_without_preload_content
+ elif callable(vars(client).get("list_access_keys_without_preload_content")):
+ raw_method = vars(client)["list_access_keys_without_preload_content"]
+
+ if raw_method:
+ response = self._handle_api_call(
+ raw_method,
+ project_id=self.project_id,
+ region=region,
+ credentials_group=credentials_group_id,
+ )
+ self._raise_for_raw_response_status(response)
+ return response
+
+ return self._handle_api_call(
+ client.list_access_keys,
+ project_id=self.project_id,
+ region=region,
+ credentials_group=credentials_group_id,
+ )
+
+ def _raise_for_raw_response_status(self, response):
+ status = getattr(response, "status", None)
+ if status is None:
+ status = getattr(response, "status_code", None)
+ if isinstance(status, int) and status >= 400:
+ error = Exception(
+ f"StackIT ObjectStorage list_access_keys failed with status {status}"
+ )
+ error.status = status
+ self.provider.handle_api_error(error)
+ raise error
+
+ @staticmethod
+ def _extract_access_keys(response) -> list:
+ payload = response
+ if not isinstance(payload, (dict, list)):
+ json_method = getattr(response, "json", None)
+ if callable(json_method):
+ payload = json_method()
+ elif hasattr(response, "data"):
+ payload = ObjectStorageService._parse_raw_json(response.data)
+ elif hasattr(response, "text"):
+ payload = ObjectStorageService._parse_raw_json(response.text)
+
+ if isinstance(payload, dict):
+ return payload.get("accessKeys", payload.get("access_keys", []))
+ if isinstance(payload, list):
+ return payload
+ return getattr(response, "access_keys", None) or []
+
+ @staticmethod
+ def _parse_raw_json(raw):
+ if raw in (None, b"", ""):
+ return {}
+ if isinstance(raw, (bytes, bytearray)):
+ raw = raw.decode("utf-8")
+ if isinstance(raw, str):
+ return json.loads(raw)
+ return raw
+
+
+class Bucket(BaseModel):
+ name: str
+ region: str
+ project_id: str
+ object_lock_enabled: bool = False
+ retention_days: Optional[int] = None
+ retention_mode: Optional[str] = None
+
+
+class AccessKey(BaseModel):
+ key_id: str
+ display_name: str
+ # None or a sentinel year-0001 date string means the key never expires.
+ expires: Optional[str] = None
+ region: str
+ project_id: str
+ credentials_group_id: Optional[str] = None
+ credentials_group_name: Optional[str] = None
+
+ def has_expiration(self) -> bool:
+ """Return True if the key has a real (non-sentinel) expiration date."""
+ if not self.expires:
+ return False
+ try:
+ expires_str = self.expires.replace("Z", "+00:00")
+ dt = datetime.fromisoformat(expires_str)
+ # Year 0001 (or earlier) is the SDK sentinel for "never expires"
+ return dt.year > 1
+ except (ValueError, AttributeError):
+ return False
+
+ def expires_within_days(self, days: int) -> bool:
+ """Return True if the key expires within the given number of days from now."""
+ if not self.has_expiration():
+ return False
+ expires_str = self.expires.replace("Z", "+00:00")
+ dt = datetime.fromisoformat(expires_str)
+ if dt.tzinfo is None:
+ dt = dt.replace(tzinfo=timezone.utc)
+ delta = dt - datetime.now(tz=timezone.utc)
+ return delta.days <= days
diff --git a/prowler/providers/stackit/stackit_provider.py b/prowler/providers/stackit/stackit_provider.py
new file mode 100644
index 0000000000..4c34afd31b
--- /dev/null
+++ b/prowler/providers/stackit/stackit_provider.py
@@ -0,0 +1,624 @@
+import contextlib
+import io
+import os
+import pathlib
+from typing import Optional
+from uuid import UUID
+
+from colorama import Style
+
+# The StackIT SDK is a hard dependency of the provider (declared in
+# pyproject.toml). Import it at module level, like every other Prowler
+# provider, so a missing SDK fails immediately when the provider module is
+# imported and is reported by Provider.init_global_provider as a critical
+# error and a non-zero exit, instead of being swallowed later by the check
+# loader and surfacing as a misleading empty report.
+from stackit.core.configuration import Configuration
+from stackit.iaas import DefaultApi as IaasDefaultApi
+from stackit.objectstorage import DefaultApi as ObjectStorageDefaultApi
+from stackit.resourcemanager import DefaultApi as ResourceManagerDefaultApi
+
+from prowler.config.config import (
+ default_config_file_path,
+ get_default_mute_file_path,
+ load_and_validate_config_file,
+)
+from prowler.lib.logger import logger
+from prowler.lib.utils.utils import open_file, parse_json_file, print_boxes
+from prowler.providers.common.models import Audit_Metadata, Connection
+from prowler.providers.common.provider import Provider
+from prowler.providers.stackit.exceptions.exceptions import (
+ StackITAPIError,
+ StackITInvalidProjectIdError,
+ StackITInvalidTokenError,
+ StackITNonExistentTokenError,
+ StackITSetUpIdentityError,
+ StackITSetUpSessionError,
+)
+from prowler.providers.stackit.lib.mutelist.mutelist import StackITMutelist
+from prowler.providers.stackit.models import StackITIdentityInfo
+
+STACKIT_REGIONS_JSON_FILE = "stackit_regions_by_service.json"
+
+
+@contextlib.contextmanager
+def suppress_stderr():
+ with contextlib.redirect_stderr(io.StringIO()):
+ yield
+
+
+class StackitProvider(Provider):
+ """
+ StackIT Provider class to handle the StackIT provider
+
+ Attributes:
+ - _type: str -> The type of the provider, which is set to "stackit".
+ - _project_id: str -> The StackIT project ID to audit.
+ - _service_account_key_path: str -> Path to a StackIT service account key
+ JSON file. The SDK mints and refreshes access tokens internally.
+ - _service_account_key: str -> Inline JSON content of a StackIT service
+ account key, for secret-manager driven deployments that do not write
+ the key to disk. Takes precedence over the key path when both are set.
+ - _identity: StackITIdentityInfo -> The identity information for the StackIT provider.
+ - _audit_config: dict -> The audit configuration for the StackIT provider.
+ - _mutelist: StackITMutelist -> The mutelist object associated with the StackIT provider.
+ - audit_metadata: Audit_Metadata -> The audit metadata for the StackIT provider.
+
+ Methods:
+ - __init__: Initializes the StackIT provider.
+ - type: Returns the type of the StackIT provider.
+ - identity: Returns the identity of the StackIT provider (ex: project_id).
+ - session: Returns the session/configuration for API calls.
+ - audit_config: Returns the audit configuration for the StackIT provider.
+ - fixer_config: Returns the fixer configuration.
+ - mutelist: Returns the mutelist object associated with the StackIT provider.
+ - validate_arguments: Validates the StackIT provider arguments (key path, project_id).
+ - print_credentials: Prints the StackIT credentials information (ex: project_id).
+ - setup_session: Set up the StackIT session with the specified authentication method.
+ - test_connection: Tests the provider connection.
+ """
+
+ _type: str = "stackit"
+ _project_id: Optional[str]
+ _service_account_key_path: Optional[str]
+ _service_account_key: Optional[str]
+ _session: Optional[dict]
+ _identity: StackITIdentityInfo
+ _audit_config: dict
+ _mutelist: StackITMutelist
+ _scan_unused_services: bool = False
+ audit_metadata: Audit_Metadata
+
+ def __init__(
+ self,
+ project_id: str = None,
+ service_account_key_path: str = None,
+ service_account_key: str = None,
+ regions: set = None,
+ scan_unused_services: bool = False,
+ config_path: str = None,
+ fixer_config: dict = None,
+ mutelist_path: str = None,
+ mutelist_content: dict = None,
+ ):
+ """
+ Initializes the StackIT provider.
+
+ Args:
+ - project_id: The StackIT project ID to audit.
+ - service_account_key_path: Path to a StackIT service account key
+ JSON file. The SDK mints and refreshes access tokens internally
+ from this key. Read from ``STACKIT_SERVICE_ACCOUNT_KEY_PATH``
+ when not provided.
+ - service_account_key: Inline JSON content of a StackIT service
+ account key, intended for CI/CD where the secret is fetched
+ from a secret manager and not persisted to disk. Read from
+ ``STACKIT_SERVICE_ACCOUNT_KEY`` when not provided. Takes
+ precedence over ``service_account_key_path`` when both are set.
+ - regions: The list of regions to audit.
+ - config_path: The path to the configuration file.
+ - fixer_config: The fixer configuration.
+ - mutelist_path: The path to the mutelist file.
+ - mutelist_content: The mutelist content.
+ """
+ logger.info("Initializing StackIT Provider...")
+
+ # 1) Store argument values
+ self._project_id = project_id or os.getenv("STACKIT_PROJECT_ID")
+ self._service_account_key_path = service_account_key_path or os.getenv(
+ "STACKIT_SERVICE_ACCOUNT_KEY_PATH"
+ )
+ self._service_account_key = service_account_key or os.getenv(
+ "STACKIT_SERVICE_ACCOUNT_KEY"
+ )
+ self._audited_regions = regions if regions else self.get_regions()
+ self._scan_unused_services = scan_unused_services
+
+ # 2) Validate credentials format (following Azure's validation pattern)
+ try:
+ self.validate_arguments(
+ self._project_id,
+ self._service_account_key_path,
+ self._service_account_key,
+ )
+ except StackITNonExistentTokenError:
+ logger.critical(
+ "StackIT service account credentials are required. Provide the "
+ "key file path via --stackit-service-account-key-path / "
+ "STACKIT_SERVICE_ACCOUNT_KEY_PATH, or the key content via "
+ "--stackit-service-account-key / STACKIT_SERVICE_ACCOUNT_KEY."
+ )
+ raise
+ except StackITInvalidProjectIdError:
+ logger.critical(
+ "StackIT project ID must be a valid UUID. Provide it via --stackit-project-id or STACKIT_PROJECT_ID environment variable."
+ )
+ raise
+
+ # 3) Load audit_config, fixer_config, mutelist
+ self._fixer_config = fixer_config if fixer_config else {}
+ if not config_path:
+ config_path = default_config_file_path
+ self._audit_config = load_and_validate_config_file(self._type, config_path)
+
+ if mutelist_content:
+ self._mutelist = StackITMutelist(mutelist_content=mutelist_content)
+ else:
+ if not mutelist_path:
+ mutelist_path = get_default_mute_file_path(self._type)
+ self._mutelist = StackITMutelist(mutelist_path=mutelist_path)
+
+ # 4) Initialize session configuration
+ self._session = None
+ try:
+ self.setup_session()
+ except Exception as e:
+ logger.critical(f"Error setting up StackIT session: {e}")
+ raise StackITSetUpSessionError(
+ original_exception=e,
+ message=f"Failed to set up StackIT session: {str(e)}",
+ )
+
+ # 5) Create StackITIdentityInfo object and fetch project name
+ try:
+ project_name = self._get_project_name()
+ self._identity = StackITIdentityInfo(
+ project_id=self._project_id,
+ project_name=project_name,
+ audited_regions=self._audited_regions,
+ )
+ except StackITInvalidTokenError:
+ # Re-raise authentication errors without wrapping to avoid verbose output
+ raise
+ except Exception as e:
+ logger.critical(f"Error setting up StackIT identity: {e}")
+ raise StackITSetUpIdentityError(
+ original_exception=e,
+ message=f"Failed to set up StackIT identity: {str(e)}",
+ )
+
+ # 6) Register as global provider
+ Provider.set_global_provider(self)
+
+ @staticmethod
+ def read_stackit_regions_file() -> dict:
+ """Read the STACKIT regions JSON file."""
+ actual_directory = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
+ with open_file(f"{actual_directory}/{STACKIT_REGIONS_JSON_FILE}") as f:
+ return parse_json_file(f)
+
+ @staticmethod
+ def get_regions() -> set:
+ """Get all available STACKIT regions from the JSON file."""
+ regions = set()
+ data = StackitProvider.read_stackit_regions_file()
+ for service in data["services"].values():
+ regions.update(service["regions"])
+ return regions
+
+ @staticmethod
+ def get_available_service_regions(service: str, audited_regions: set = None) -> set:
+ """Get available regions for a specific service, filtered by audited_regions."""
+ data = StackitProvider.read_stackit_regions_file()
+ json_regions = set(data["services"].get(service, {}).get("regions", []))
+ if audited_regions:
+ return json_regions.intersection(audited_regions)
+ return json_regions
+
+ _SERVICE_API_CLASS = {
+ "iaas": IaasDefaultApi,
+ "objectstorage": ObjectStorageDefaultApi,
+ }
+
+ def generate_regional_clients(self, service: str = "iaas") -> dict:
+ """Generate regional API clients for the given service.
+
+ Returns dict: {"eu01": DefaultApi_client, "eu02": DefaultApi_client}
+ """
+ api_class = self._SERVICE_API_CLASS.get(service, IaasDefaultApi)
+ regional_clients = {}
+ service_regions = self.get_available_service_regions(
+ service, self._audited_regions
+ )
+
+ for region in service_regions:
+ with suppress_stderr():
+ config = self._build_sdk_configuration(
+ self._service_account_key_path,
+ self._service_account_key,
+ )
+ client = api_class(config)
+ client.region = region # Attach region attribute
+ regional_clients[region] = client
+
+ return regional_clients
+
+ @staticmethod
+ def _build_sdk_configuration(
+ service_account_key_path: str, service_account_key: str = None
+ ):
+ """Build a ``stackit.core.configuration.Configuration`` from the
+ configured service account credentials.
+
+ Prefer the inlined key content over the path so secret-manager
+ deployments (where the path may also be set as a default) work
+ without writing the secret to disk. In both cases the SDK signs
+ the RSA challenge and refreshes access tokens internally for the
+ life of the scan.
+
+ Kept as a static helper so ``test_connection`` (which has no provider
+ instance) can reuse it.
+ """
+ if service_account_key:
+ return Configuration(service_account_key=service_account_key)
+ return Configuration(service_account_key_path=service_account_key_path)
+
+ @property
+ def type(self) -> str:
+ """
+ Returns the type of the provider ("stackit").
+ """
+ return self._type
+
+ @property
+ def identity(self) -> StackITIdentityInfo:
+ """
+ Returns the StackITIdentityInfo object, which contains project_id, etc.
+ """
+ return self._identity
+
+ @property
+ def session(self) -> dict:
+ """
+ Returns the session configuration for StackIT API calls.
+ This includes the API token and project ID needed for SDK initialization.
+ """
+ return self._session
+
+ @property
+ def audit_config(self) -> dict:
+ """
+ Returns the audit configuration loaded from file or default settings.
+ """
+ return self._audit_config
+
+ @property
+ def fixer_config(self) -> dict:
+ """
+ Returns any fixer configuration provided to the StackIT provider.
+ """
+ return self._fixer_config
+
+ @property
+ def scan_unused_services(self) -> bool:
+ return self._scan_unused_services
+
+ @property
+ def mutelist(self) -> StackITMutelist:
+ """
+ Returns the StackITMutelist object for handling any muted checks.
+ """
+ return self._mutelist
+
+ @staticmethod
+ def validate_arguments(
+ project_id: str,
+ service_account_key_path: str,
+ service_account_key: str = None,
+ ) -> None:
+ """
+ Validates StackIT static arguments format before use.
+
+ Either the service account key file path or the inline key content
+ must be supplied, and the project ID is always required and must be
+ a valid UUID. This mirrors Azure's pattern of failing fast on input
+ format issues before making any API calls.
+
+ Args:
+ project_id: The StackIT project ID (must be valid UUID format)
+ service_account_key_path: Path to a service account key JSON file
+ (optional when ``service_account_key`` is provided)
+ service_account_key: Inline JSON content of a service account key
+ (optional when ``service_account_key_path`` is provided)
+
+ Raises:
+ StackITNonExistentTokenError: If both ``service_account_key_path``
+ and ``service_account_key`` are missing or empty
+ StackITInvalidProjectIdError: If ``project_id`` is missing or not a
+ valid UUID
+ """
+ has_path = bool(service_account_key_path and service_account_key_path.strip())
+ has_key = bool(service_account_key and service_account_key.strip())
+ if not has_path and not has_key:
+ raise StackITNonExistentTokenError(
+ message=(
+ "StackIT service account credentials are required: provide "
+ "the key file path (--stackit-service-account-key-path or "
+ "STACKIT_SERVICE_ACCOUNT_KEY_PATH) or the inline key content "
+ "(--stackit-service-account-key or STACKIT_SERVICE_ACCOUNT_KEY)"
+ )
+ )
+
+ # Validate project_id is not empty
+ if not project_id or not project_id.strip():
+ raise StackITInvalidProjectIdError(
+ message="StackIT project ID is required for auditing"
+ )
+
+ # Validate project_id is a valid UUID format
+ # StackIT uses UUIDs for project IDs, similar to Azure subscription IDs
+ try:
+ UUID(project_id)
+ except ValueError as e:
+ raise StackITInvalidProjectIdError(
+ original_exception=e,
+ message=f"StackIT project ID must be a valid UUID format, got: {project_id}",
+ )
+
+ @property
+ def auth_method(self) -> str:
+ """Auth method label used for findings and credentials box.
+
+ StackIT authenticates with a service account key; the SDK signs
+ the RSA challenge and refreshes access tokens internally.
+ """
+ return "service_account_key"
+
+ def print_credentials(self) -> None:
+ """
+ Prints the StackIT credentials in a simple box format.
+ """
+ # Build credential lines
+ lines = []
+ if self._identity.project_name:
+ lines.append(f" Project Name: {self._identity.project_name}")
+ lines.append(f" Project ID: {self._project_id}")
+ if self._service_account_key:
+ lines.append(" Service Account Key: ***REDACTED*** (inline)")
+ else:
+ lines.append(f" Service Account Key: {self._service_account_key_path}")
+ lines.append(" Auth Method: service account key (auto-refresh)")
+
+ report_lines = ["\n".join(lines)]
+
+ report_title = (
+ f"{Style.BRIGHT}Using the StackIT credentials below:{Style.RESET_ALL}"
+ )
+ print_boxes(report_lines, report_title)
+
+ def setup_session(self) -> None:
+ """
+ Set up the StackIT session configuration.
+
+ This creates a session dictionary containing the credentials
+ used by service clients to build SDK ``Configuration`` objects.
+ """
+ try:
+ self._session = {
+ "project_id": self._project_id,
+ "service_account_key_path": self._service_account_key_path,
+ "service_account_key": self._service_account_key,
+ }
+ logger.info("StackIT session configuration set up successfully.")
+ except Exception as e:
+ logger.critical(f"Error in setup_session: {e}")
+ raise e
+
+ def _get_project_name(self) -> str:
+ """
+ Fetch the project name from the StackIT Resource Manager API.
+
+ The project name is cosmetic (shown in the credentials box and in
+ the ``account_name`` field of findings); a missing or unauthorized
+ Resource Manager endpoint must not abort an otherwise valid IaaS
+ scan. A service account can legitimately hold IaaS roles on a
+ project without holding Resource Manager roles on it.
+
+ Failure semantics:
+ - HTTP 401 -> hard failure via :class:`StackITInvalidTokenError`
+ (the credentials cannot mint a usable token).
+ - HTTP 403 (or any other non-401 error) -> warning, returns
+ an empty project name; the scan continues and per-service
+ ``handle_api_error`` will abort later if the IaaS endpoints
+ are also forbidden.
+
+ Returns:
+ str: The project name, or empty string if unavailable.
+
+ Raises:
+ StackITInvalidTokenError: If the credentials are rejected with a
+ 401 response when contacting Resource Manager.
+ """
+ try:
+ with suppress_stderr():
+ config = self._build_sdk_configuration(
+ self._service_account_key_path,
+ self._service_account_key,
+ )
+ client = ResourceManagerDefaultApi(config)
+
+ # Fetch project details - validates that the credentials
+ # can mint a token; permission to read this specific
+ # project is checked but optional.
+ response = client.get_project(id=self._project_id)
+
+ # Extract project name from response
+ if hasattr(response, "name"):
+ project_name = response.name
+ elif isinstance(response, dict):
+ project_name = response.get("name", "")
+ else:
+ project_name = ""
+
+ logger.info(f"Successfully retrieved project name: {project_name}")
+ return project_name
+
+ except Exception as e:
+ status = getattr(e, "status", None)
+ if status == 401:
+ # Bad credentials are a hard failure even at the cosmetic
+ # Resource Manager lookup; keep the same behaviour as
+ # ``handle_api_error`` so the user sees the same message.
+ logger.critical(
+ "StackIT service account key was rejected by Resource "
+ "Manager (401). Verify the key file is current and has "
+ "not been revoked in the StackIT portal."
+ )
+ raise StackITInvalidTokenError(
+ file="stackit_provider.py",
+ original_exception=None,
+ message="StackIT service account key was rejected (401)",
+ )
+ if status == 403:
+ logger.warning(
+ f"StackIT service account lacks the Resource Manager "
+ f"role on project {self._project_id} (403). The project "
+ f"name will not be displayed in reports, but IaaS "
+ f"checks will still run if the service account has the "
+ f"relevant IaaS role."
+ )
+ return ""
+ logger.warning(
+ f"Unable to fetch project name from StackIT API: {e}. "
+ f"Project name will not be displayed in reports."
+ )
+ return ""
+
+ @staticmethod
+ def handle_api_error(exception: Exception) -> None:
+ """
+ Centralized handler for StackIT API errors across all services.
+
+ Detects credential and permission errors (HTTP 401 and 403) and raises
+ ``StackITInvalidTokenError`` so the scan aborts instead of continuing
+ with partial data. All other exceptions are re-raised unchanged so
+ callers can decide how to handle them (e.g. per-resource ``continue``).
+
+ Args:
+ exception: The exception caught from a StackIT API call
+
+ Raises:
+ StackITInvalidTokenError: If the error is a 401 Unauthorized or
+ a 403 Forbidden response
+ Exception: Re-raises the original exception otherwise
+ """
+ status = getattr(exception, "status", None)
+ if status == 401:
+ logger.critical(
+ "StackIT service account key was rejected. Verify the key "
+ "file referenced by STACKIT_SERVICE_ACCOUNT_KEY_PATH is the "
+ "current one and has not been revoked in the StackIT portal."
+ )
+ raise StackITInvalidTokenError(
+ file="stackit_provider.py",
+ original_exception=None, # Don't include verbose HTTP details
+ message="StackIT service account key was rejected (401)",
+ )
+ if status == 403:
+ logger.critical(
+ "StackIT service account lacks the required permissions on this project. "
+ "Ensure the service account has the necessary IAM roles."
+ )
+ raise StackITInvalidTokenError(
+ file="stackit_provider.py",
+ original_exception=None, # Don't include verbose HTTP details
+ message="Service account lacks required permissions on this project",
+ )
+ # Re-raise other exceptions unchanged
+ raise exception
+
+ @staticmethod
+ def test_connection(
+ project_id: str = None,
+ service_account_key_path: str = None,
+ service_account_key: str = None,
+ raise_on_exception: bool = True,
+ ) -> Connection:
+ """
+ Test connection to StackIT by validating credentials.
+
+ This method validates the service account credentials and project ID
+ by making a Resource Manager ``get_project`` call. Pass either the
+ key file path or the inline key content; the SDK signs the RSA
+ challenge and mints a short-lived access token internally.
+
+ Args:
+ project_id (str): StackIT project ID
+ service_account_key_path (str): Path to a StackIT service account
+ key JSON file (optional when ``service_account_key`` is given)
+ service_account_key (str): Inline JSON content of a StackIT
+ service account key (optional when
+ ``service_account_key_path`` is given)
+ raise_on_exception (bool): If True, raise the caught exception;
+ if False, return Connection(error=exception).
+
+ Returns:
+ Connection:
+ Connection(is_connected=True) if success,
+ otherwise Connection(error=Exception or custom error).
+ """
+ try:
+ StackitProvider.validate_arguments(
+ project_id, service_account_key_path, service_account_key
+ )
+
+ with suppress_stderr():
+ config = StackitProvider._build_sdk_configuration(
+ service_account_key_path,
+ service_account_key,
+ )
+ client = ResourceManagerDefaultApi(config)
+ client.get_project(id=project_id)
+
+ logger.info(
+ "StackIT test_connection: Successfully connected using StackIT Resource Manager."
+ )
+ return Connection(is_connected=True)
+ except (StackITNonExistentTokenError, StackITInvalidProjectIdError) as error:
+ logger.error(f"StackIT test_connection error: {error}")
+ if raise_on_exception:
+ raise error
+ return Connection(error=error)
+ except Exception as test_error:
+ try:
+ StackitProvider.handle_api_error(test_error)
+ except StackITInvalidTokenError as auth_error:
+ if raise_on_exception:
+ raise auth_error
+ return Connection(error=auth_error)
+ except Exception as api_error:
+ error_msg = (
+ "Failed to connect to StackIT using Resource Manager: "
+ f"{str(api_error)}"
+ )
+ logger.error(error_msg)
+ connection_error = StackITAPIError(
+ original_exception=api_error, message=error_msg
+ )
+ if raise_on_exception:
+ raise connection_error
+ return Connection(error=connection_error)
+
+ if raise_on_exception:
+ raise test_error
+ return Connection(error=test_error)
diff --git a/prowler/providers/stackit/stackit_regions_by_service.json b/prowler/providers/stackit/stackit_regions_by_service.json
new file mode 100644
index 0000000000..5841d4e32d
--- /dev/null
+++ b/prowler/providers/stackit/stackit_regions_by_service.json
@@ -0,0 +1,16 @@
+{
+ "services": {
+ "iaas": {
+ "regions": [
+ "eu01",
+ "eu02"
+ ]
+ },
+ "objectstorage": {
+ "regions": [
+ "eu01",
+ "eu02"
+ ]
+ }
+ }
+}
diff --git a/prowler/providers/vercel/vercel_provider.py b/prowler/providers/vercel/vercel_provider.py
index 54ab4627a9..3de89becbe 100644
--- a/prowler/providers/vercel/vercel_provider.py
+++ b/prowler/providers/vercel/vercel_provider.py
@@ -33,6 +33,7 @@ class VercelProvider(Provider):
"""Vercel provider."""
_type: str = "vercel"
+ sdk_only: bool = False
_session: VercelSession
_identity: VercelIdentityInfo
_audit_config: dict
diff --git a/prowler/towncrier.toml b/prowler/towncrier.toml
new file mode 100644
index 0000000000..528e6129ec
--- /dev/null
+++ b/prowler/towncrier.toml
@@ -0,0 +1,39 @@
+[tool.towncrier]
+directory = "changelog.d"
+filename = "CHANGELOG.md"
+start_string = "<!-- changelog: release notes start -->\n"
+title_format = "## [{version}] ({name})"
+issue_format = "[(#{issue})](https://github.com/prowler-cloud/prowler/pull/{issue})"
+template = "../.github/towncrier/template.md.jinja"
+underlines = ["", "", ""]
+ignore = [".gitkeep", "README.md"]
+
+[[tool.towncrier.type]]
+directory = "added"
+name = "🚀 Added"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "changed"
+name = "🔄 Changed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "deprecated"
+name = "⚠️ Deprecated"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "removed"
+name = "❌ Removed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "fixed"
+name = "🐞 Fixed"
+showcontent = true
+
+[[tool.towncrier.type]]
+directory = "security"
+name = "🔐 Security"
+showcontent = true
diff --git a/pyproject.toml b/pyproject.toml
index 710b5d4604..64affc8556 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -5,7 +5,7 @@ requires = ["hatchling"]
[dependency-groups]
dev = [
"bandit==1.8.3",
- "black==25.1.0",
+ "black==26.3.1",
"coverage==7.6.12",
"docker==7.1.0",
"filelock==3.20.3",
@@ -17,7 +17,7 @@ dev = [
"openapi-spec-validator==0.7.1",
"prek==0.3.9",
"pylint==3.3.4",
- "pytest==8.3.5",
+ "pytest==9.0.3",
"pytest-cov==6.0.0",
"pytest-env==1.1.5",
"pytest-randomly==3.16.0",
@@ -32,10 +32,10 @@ classifiers = [
"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
- "Programming Language :: Python :: 3.12"
+ "Programming Language :: Python :: 3.12",
+ "Programming Language :: Python :: 3.13"
]
dependencies = [
- "awsipranges==0.3.3",
"alive-progress==3.3.0",
"azure-identity==1.21.0",
"azure-keyvault-keys==4.10.0",
@@ -72,16 +72,17 @@ dependencies = [
"dash==3.1.1",
"dash-bootstrap-components==2.0.3",
"defusedxml==0.7.1",
- "detect-secrets==1.5.0",
- "dulwich==0.23.0",
+ "dulwich==1.2.5",
"google-api-python-client==2.163.0",
"google-auth-httplib2==0.2.0",
"jsonschema==4.23.0",
+ "kingfisher-bin==1.104.0",
"kubernetes==32.0.1",
+ "linode-api4==5.45.0",
"markdown==3.10.2",
- "microsoft-kiota-abstractions==1.9.2",
+ "microsoft-kiota-abstractions==1.9.9",
+ "numpy==2.2.6",
"msgraph-sdk==1.55.0",
- "numpy==2.0.2",
"okta==3.4.2",
"openstacksdk==4.2.0",
"pandas==2.2.3",
@@ -93,10 +94,14 @@ dependencies = [
"schema==0.7.5",
"shodan==1.31.0",
"slack-sdk==3.39.0",
+ "stackit-core==0.2.0",
+ "stackit-iaas==1.4.0",
+ "stackit-objectstorage==1.4.0",
+ "stackit-resourcemanager==0.8.0",
"tabulate==0.9.0",
"tzlocal==5.3.1",
"uuid6==2024.7.10",
- "py-iam-expand==0.1.0",
+ "py-iam-expand==0.3.0",
"h2==4.3.0",
"oci==2.169.0",
"alibabacloud_credentials==1.0.3",
@@ -119,8 +124,8 @@ license = "Apache-2.0"
maintainers = [{name = "Prowler Engineering", email = "engineering@prowler.com"}]
name = "prowler"
readme = "README.md"
-requires-python = ">=3.10,<3.13"
-version = "5.28.0"
+requires-python = ">=3.10,<3.14"
+version = "5.36.0"
[project.scripts]
prowler = "prowler.__main__:prowler"
@@ -158,7 +163,7 @@ constraint-dependencies = [
"aenum==3.1.17",
"aiofiles==24.1.0",
"aiohappyeyeballs==2.6.1",
- "aiohttp==3.13.5",
+ "aiohttp==3.14.0",
"aiosignal==1.4.0",
"alibabacloud-actiontrail20200706==2.4.1",
"alibabacloud-credentials==1.0.3",
@@ -201,7 +206,7 @@ constraint-dependencies = [
"azure-core==1.41.0",
"azure-mgmt-core==1.6.0",
"bandit==1.8.3",
- "black==25.1.0",
+ "black==26.3.1",
"blinker==1.9.0",
"certifi==2026.4.22",
"cffi==2.0.0",
@@ -214,6 +219,7 @@ constraint-dependencies = [
"coverage==7.6.12",
"darabonba-core==1.0.5",
"decorator==5.2.1",
+ "deprecated==1.3.1",
"dill==0.4.1",
"distro==1.9.0",
"dnspython==2.8.0",
@@ -263,12 +269,12 @@ constraint-dependencies = [
"markupsafe==3.0.3",
"mccabe==0.7.0",
"mdurl==0.1.2",
- "microsoft-kiota-authentication-azure==1.9.2",
- "microsoft-kiota-http==1.9.2",
- "microsoft-kiota-serialization-form==1.9.2",
- "microsoft-kiota-serialization-json==1.9.2",
- "microsoft-kiota-serialization-multipart==1.9.2",
- "microsoft-kiota-serialization-text==1.9.2",
+ "microsoft-kiota-authentication-azure==1.9.9",
+ "microsoft-kiota-http==1.9.9",
+ "microsoft-kiota-serialization-form==1.9.9",
+ "microsoft-kiota-serialization-json==1.9.9",
+ "microsoft-kiota-serialization-multipart==1.9.9",
+ "microsoft-kiota-serialization-text==1.9.9",
"mock==5.2.0",
"moto==5.1.11",
"mpmath==1.3.0",
@@ -296,6 +302,7 @@ constraint-dependencies = [
"platformdirs==4.9.6",
"plotly==6.7.0",
"pluggy==1.6.0",
+ "polling==0.3.2",
"prek==0.3.9",
"propcache==0.5.2",
"proto-plus==1.28.0",
@@ -311,16 +318,17 @@ constraint-dependencies = [
"pydash==8.0.6",
"pyflakes==3.2.0",
"pygments==2.20.0",
- "pyjwt==2.12.1",
+ "pyjwt==2.13.0",
"pylint==3.3.4",
"pynacl==1.6.2",
"pyopenssl==26.2.0",
"pyparsing==3.3.2",
- "pytest==8.3.5",
+ "pytest==9.0.3",
"pytest-cov==6.0.0",
"pytest-env==1.1.5",
"pytest-randomly==3.16.0",
"pytest-xdist==3.6.1",
+ "pytokens==0.4.1",
"pywin32==311",
"pyyaml==6.0.3",
"referencing==0.36.2",
@@ -360,3 +368,13 @@ constraint-dependencies = [
"zstd==1.5.7.3"
]
override-dependencies = ["okta==3.4.2"]
+
+[tool.vulture]
+# Suppress known false positives. The CI command only passes --exclude and
+# --min-confidence on the CLI, so ignore_names from here still applies (vulture
+# only overrides the keys set on the CLI).
+# - mock_* : pytest fixtures injected as test params but unused in the body
+# (e.g. mock_sensitive_args in tests/lib/cli/redact_test.py)
+# - view : DRF BasePermission.has_object_permission(self, request, view, obj)
+# framework-required signature param in skills/django-drf template assets
+ignore_names = ["mock_*", "view"]
diff --git a/scripts/check_test_init_files.py b/scripts/check_test_init_files.py
new file mode 100644
index 0000000000..ddb94548e6
--- /dev/null
+++ b/scripts/check_test_init_files.py
@@ -0,0 +1,90 @@
+#!/usr/bin/env python3
+"""Fail when __init__.py files are present inside test directories."""
+
+from __future__ import annotations
+
+import sys
+from argparse import ArgumentParser
+from os import walk
+from pathlib import Path
+
+EXCLUDED_TEST_INIT_ROOTS = {
+ Path("tests/lib/check/fixtures/checks_folder"),
+}
+
+IGNORED_DIRECTORY_NAMES = {
+ ".git",
+ ".mypy_cache",
+ ".nox",
+ ".pytest_cache",
+ ".tox",
+ ".venv",
+ "__pycache__",
+ "node_modules",
+ "venv",
+}
+
+
+def is_test_init_file(path: Path) -> bool:
+ """Return True when the file is a root tests __init__.py."""
+ return path.name == "__init__.py" and path.parts[0] == "tests"
+
+
+def is_excluded_test_init_file(path: Path, root: Path) -> bool:
+ """Return True when the file belongs to an allowed fixture directory."""
+ relative_path = path.relative_to(root)
+ return any(
+ relative_path.is_relative_to(excluded) for excluded in EXCLUDED_TEST_INIT_ROOTS
+ )
+
+
+def find_test_init_files(root: Path) -> list[Path]:
+ """Return sorted __init__.py files found under test directories."""
+ matches = []
+
+ for current_root, directories, filenames in walk(root):
+ directories[:] = [
+ directory
+ for directory in directories
+ if directory not in IGNORED_DIRECTORY_NAMES
+ ]
+ if "__init__.py" in filenames:
+ path = Path(current_root) / "__init__.py"
+ else:
+ continue
+
+ relative_path = path.relative_to(root)
+ if is_test_init_file(relative_path) and not is_excluded_test_init_file(
+ path, root
+ ):
+ matches.append(path)
+
+ return sorted(matches)
+
+
+def main(argv: list[str] | None = None) -> int:
+ parser = ArgumentParser(description=__doc__)
+ parser.add_argument(
+ "root",
+ nargs="?",
+ default=".",
+ help="Repository root to scan. Defaults to the current directory.",
+ )
+ args = parser.parse_args(argv)
+
+ root = Path(args.root).resolve()
+ matches = find_test_init_files(root)
+
+ if not matches:
+ print("No __init__.py files found in test directories.")
+ return 0
+
+ print("Remove __init__.py files from test directories:")
+ for path in matches:
+ print(path.relative_to(root))
+
+ return 1
+
+
+if __name__ == "__main__":
+ sys.exit(main())
diff --git a/scripts/development/dev-local.sh b/scripts/development/dev-local.sh
new file mode 100755
index 0000000000..d193b81532
--- /dev/null
+++ b/scripts/development/dev-local.sh
@@ -0,0 +1,558 @@
+#!/usr/bin/env bash
+#
+# Local dev for Prowler API + worker.
+# Postgres / Valkey / Neo4j run in Docker via docker-compose-dev.yml;
+# Django and Celery run natively.
+#
+# Quick start:
+# make dev-setup first-time bootstrap (deps, migrations, fixtures)
+# make dev launch api + worker + postgres logs in tmux
+# make dev-attach attach to the tmux session in the current terminal pane
+# make dev-launch use fixed ports and attach interactive local dev
+# make dev-stop stop everything: tmux + stop + remove containers
+# make dev-clean remove stopped containers only (data preserved)
+# make dev-wipe full nuke: kill + clean + delete ./_data/
+#
+# Agent / non-interactive usage: 'make dev' is idempotent, runs
+# everything detached, blocks until the API answers HTTP, and ends with
+# parseable key=value lines (api_url=, api_log=, worker_log=,
+# postgres_log=, attach_cmd=, stop_cmd=).
+# Every pane is teed ANSI-stripped to _data/logs/{api,worker,postgres}.log
+# (truncated per run), so logs are readable with tail -f, no tmux needed.
+#
+# 'attach' attaches to tmux inside the current terminal pane.
+#
+# Inside the tmux session "prowler-dev-<compose-project>" the prefix key is Ctrl+b. After it:
+# d detach (everything keeps running; reattach: make dev-attach)
+# <arrows> move between panes
+# z zoom current pane (toggle)
+# [ scrollback mode (q to exit)
+# x kill current pane (asks for confirmation)
+# & kill current window
+# :kill-session end the whole session
+#
+# How to stop everything from inside tmux:
+# 1) Ctrl+b then d detach back to your shell
+# 2) make dev-stop tears down tmux + containers
+# Alternative without detaching: open a new tmux window with Ctrl+b then c
+# and run make dev-stop there; the session will close itself.
+#
+# Stop just the python procs (keep containers up to skip a slow neo4j boot next time):
+# ./scripts/development/dev-local.sh down
+#
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
+cd "$REPO_ROOT"
+
+path_hash() {
+ if command -v shasum >/dev/null 2>&1; then
+ printf '%s' "$REPO_ROOT" | shasum | awk '{print substr($1, 1, 8)}'
+ else
+ printf '%s' "$REPO_ROOT" | cksum | awk '{print $1}'
+ fi
+}
+
+compose_project_default() {
+ local base hash
+ base="$(basename "$REPO_ROOT" | tr '[:upper:]' '[:lower:]' | sed -E 's/[^a-z0-9_-]+/-/g; s/^-+//; s/-+$//')"
+ hash="$(path_hash)"
+ printf '%s-%s' "${base:-prowler}" "$hash"
+}
+
+export COMPOSE_PROJECT_NAME="${COMPOSE_PROJECT_NAME:-$(compose_project_default)}"
+
+if [ -f .env ]; then
+ set -a
+ # shellcheck disable=SC1091
+ . ./.env
+ set +a
+fi
+
+export POSTGRES_HOST=localhost
+export POSTGRES_PORT="${POSTGRES_PORT:-5432}"
+export VALKEY_HOST=localhost
+export VALKEY_PORT="${VALKEY_PORT:-6379}"
+export VALKEY_SCHEME="${VALKEY_SCHEME:-redis}"
+export NEO4J_HOST=localhost
+export NEO4J_PORT="${NEO4J_PORT:-7687}"
+export NEO4J_HTTP_PORT="${NEO4J_HTTP_PORT:-7474}"
+export DJANGO_SETTINGS_MODULE=config.django.devel
+export DJANGO_DEBUG="${DJANGO_DEBUG:-True}"
+export DJANGO_PORT="${DJANGO_PORT:-8080}"
+export DJANGO_LOGGING_FORMATTER="${DJANGO_LOGGING_FORMATTER:-human_readable}"
+export DJANGO_LOGGING_LEVEL="${DJANGO_LOGGING_LEVEL:-info}"
+export DJANGO_MANAGE_DB_PARTITIONS="${DJANGO_MANAGE_DB_PARTITIONS:-False}"
+
+if docker compose version >/dev/null 2>&1; then
+ COMPOSE=(docker compose)
+else
+ COMPOSE=(docker-compose)
+fi
+COMPOSE_FILE="docker-compose-dev.yml"
+
+log() { printf '\033[1;34m→\033[0m %s\n' "$*"; }
+ok() { printf '\033[1;32m✓\033[0m %s\n' "$*"; }
+warn() { printf '\033[1;33m!\033[0m %s\n' "$*"; }
+
+require_uv() {
+ if ! command -v uv >/dev/null 2>&1; then
+ warn "uv not found in PATH. Install: https://docs.astral.sh/uv/getting-started/installation/"
+ exit 1
+ fi
+}
+
+services_up() {
+ log "Starting postgres + valkey + neo4j via Docker (waits for healthchecks)..."
+ "${COMPOSE[@]}" -f "$COMPOSE_FILE" up -d --wait postgres valkey neo4j
+ ok "Services ready: pg:${POSTGRES_PORT} / valkey:${VALKEY_PORT} / neo4j:${NEO4J_PORT} / neo4j-http:${NEO4J_HTTP_PORT}"
+}
+
+kill_tmux_session() {
+ command -v tmux >/dev/null 2>&1 || return 0
+ if tmux has-session -t "$TMUX_SESSION" 2>/dev/null; then
+ log "Killing tmux session '$TMUX_SESSION'"
+ tmux kill-session -t "$TMUX_SESSION"
+ fi
+}
+
+tmux_pane_count() {
+ tmux list-panes -t "$TMUX_SESSION:" 2>/dev/null | wc -l | tr -d ' '
+}
+
+# Tee a tmux pane's output to _data/logs/<name>.log so non-interactive
+# consumers (scripts, agents) can follow the stack without attaching.
+# ANSI codes are stripped; the file is truncated on session creation so
+# its content always matches the current run.
+pipe_pane_log() {
+ local pane="$1" name="$2"
+ local logfile="$REPO_ROOT/_data/logs/$name.log"
+ : > "$logfile"
+ tmux pipe-pane -t "$pane" -o "perl -pe 'BEGIN{\$|=1} s/\\e\\[[0-9;?]*[A-Za-z]//g' >> '$logfile'"
+}
+
+# Stop native dev processes (api/worker/beat) launched outside tmux. Scoped by
+# cwd under REPO_ROOT so other prowler clones running their own stacks are not
+# touched.
+kill_native_procs() {
+ command -v pgrep >/dev/null 2>&1 || return 0
+ command -v lsof >/dev/null 2>&1 || return 0
+
+ local pids="" pid pcwd pat
+ for pat in "manage.py runserver" "celery -A config.celery worker" "celery -A config.celery beat"; do
+ while IFS= read -r pid; do
+ [ -n "$pid" ] || continue
+ pcwd="$(lsof -a -d cwd -p "$pid" 2>/dev/null | awk 'NR>1 {print $NF; exit}')"
+ case "$pcwd" in
+ "$REPO_ROOT"|"$REPO_ROOT"/*) pids="$pids $pid" ;;
+ esac
+ done < <(pgrep -f "$pat" 2>/dev/null)
+ done
+
+ pids="$(printf '%s\n' "$pids" | tr ' ' '\n' | sed '/^$/d' | sort -u | xargs)"
+ [ -z "$pids" ] && return 0
+
+ log "Stopping native dev procs ($pids) under $REPO_ROOT"
+ # shellcheck disable=SC2086
+ kill -TERM $pids 2>/dev/null || true
+ sleep 0.5
+ # shellcheck disable=SC2086
+ kill -KILL $pids 2>/dev/null || true
+}
+
+services_down() {
+ kill_tmux_session
+ kill_native_procs
+ log "Stopping postgres + valkey + neo4j..."
+ "${COMPOSE[@]}" -f "$COMPOSE_FILE" stop postgres valkey neo4j
+}
+
+services_status() {
+ "${COMPOSE[@]}" -f "$COMPOSE_FILE" ps postgres valkey neo4j
+}
+
+deps() {
+ require_uv
+ log "uv sync (api/)..."
+ (cd api && uv sync)
+}
+
+migrate() {
+ require_uv
+ log "Applying migrations (admin DB)..."
+ (
+ cd api/src/backend
+ uv run python manage.py check_and_fix_socialaccount_sites_migration --database admin
+ uv run python manage.py migrate --database admin
+ )
+ ok "Migrations applied"
+}
+
+fixtures() {
+ require_uv
+ log "Loading dev fixtures..."
+ (
+ cd api/src/backend
+ for fixture in api/fixtures/dev/*.json; do
+ [ -f "$fixture" ] || continue
+ echo " loading $(basename "$fixture")"
+ uv run python manage.py loaddata "$fixture" --database admin
+ done
+ )
+ ok "Fixtures loaded"
+}
+
+api_run() {
+ require_uv
+ log "Starting Django API on [::]:${DJANGO_PORT} (IPv4 + IPv6 dual-stack)"
+ cd api/src/backend
+ exec uv run python manage.py runserver "[::]:${DJANGO_PORT}"
+}
+
+worker_run() {
+ require_uv
+ log "Starting Celery worker"
+ cd api/src/backend
+ exec uv run python -m celery -A config.celery worker \
+ -l "${DJANGO_LOGGING_LEVEL}" \
+ -Q celery,scans,scan-reports,deletion,backfill,overview,integrations,compliance,attack-paths-scans \
+ -E
+}
+
+beat_run() {
+ require_uv
+ log "Starting Celery beat (DatabaseScheduler)"
+ cd api/src/backend
+ exec uv run python -m celery -A config.celery beat \
+ -l "${DJANGO_LOGGING_LEVEL}" \
+ --scheduler django_celery_beat.schedulers:DatabaseScheduler
+}
+
+TMUX_SESSION="prowler-dev-${COMPOSE_PROJECT_NAME}"
+SCRIPT_PATH="$REPO_ROOT/scripts/development/dev-local.sh"
+
+require_tmux() {
+ if ! command -v tmux >/dev/null 2>&1; then
+ warn "tmux not installed. Run: brew install tmux"
+ exit 1
+ fi
+}
+
+remove_repo_compose_containers() {
+ command -v docker >/dev/null 2>&1 || return 0
+ local ids
+ ids="$(
+ docker ps -aq 2>/dev/null \
+ | while IFS= read -r id; do
+ docker inspect --format '{{.ID}} {{index .Config.Labels "com.docker.compose.project.working_dir"}}' "$id" 2>/dev/null || true
+ done \
+ | awk -v repo="$REPO_ROOT" '$2 == repo {print $1}'
+ )"
+ [ -n "$ids" ] || return 0
+ warn "Removing existing Docker containers for this repo before launch"
+ # shellcheck disable=SC2086
+ docker rm -f $ids >/dev/null
+}
+
+remove_docker_containers_on_ports() {
+ command -v docker >/dev/null 2>&1 || return 0
+ local all_ids ids_to_remove="" id port published_ports
+ all_ids="$(docker ps -aq 2>/dev/null || true)"
+ [ -n "$all_ids" ] || return 0
+
+ for id in $all_ids; do
+ published_ports="$(docker inspect --format '{{range $containerPort, $bindings := .HostConfig.PortBindings}}{{range $bindings}}{{.HostPort}}{{"\n"}}{{end}}{{end}}' "$id" 2>/dev/null || true)"
+ [ -n "$published_ports" ] || continue
+ for port in "$@"; do
+ if printf '%s\n' "$published_ports" | grep -qx "$port"; then
+ ids_to_remove="$ids_to_remove $id"
+ break
+ fi
+ done
+ done
+
+ ids_to_remove="$(printf '%s\n' "$ids_to_remove" | tr ' ' '\n' | sed '/^$/d' | sort -u | xargs)"
+ [ -n "$ids_to_remove" ] || return 0
+ warn "Removing Docker containers publishing fixed dev ports: $ids_to_remove"
+ # shellcheck disable=SC2086
+ docker rm -f $ids_to_remove >/dev/null
+}
+
+kill_listeners_on_ports() {
+ command -v lsof >/dev/null 2>&1 || return 0
+ local pids="" port port_pids
+ for port in "$@"; do
+ port_pids="$(lsof -nP -tiTCP:"$port" -sTCP:LISTEN 2>/dev/null || true)"
+ [ -n "$port_pids" ] && pids="$pids $port_pids"
+ done
+
+ pids="$(printf '%s\n' "$pids" | tr ' ' '\n' | sed '/^$/d' | sort -u | xargs)"
+ [ -n "$pids" ] || return 0
+ warn "Killing local processes listening on fixed dev ports: $pids"
+ # shellcheck disable=SC2086
+ kill -TERM $pids 2>/dev/null || true
+ sleep 0.5
+ # shellcheck disable=SC2086
+ kill -KILL $pids 2>/dev/null || true
+}
+
+clear_dev_port_conflicts() {
+ local ports=("$DJANGO_PORT" "$POSTGRES_PORT" "$VALKEY_PORT" "$NEO4J_PORT" "$NEO4J_HTTP_PORT")
+ log "Ensuring fixed dev ports are free: api:${DJANGO_PORT} pg:${POSTGRES_PORT} valkey:${VALKEY_PORT} neo4j:${NEO4J_PORT} neo4j-http:${NEO4J_HTTP_PORT}"
+ remove_docker_containers_on_ports "${ports[@]}"
+ kill_listeners_on_ports "${ports[@]}"
+}
+
+# Block until the API answers HTTP on DJANGO_PORT (any status code counts).
+wait_for_api() {
+ local timeout="${1:-90}" waited=0
+ log "Waiting for API on :${DJANGO_PORT} (timeout ${timeout}s)..."
+ until curl -s -o /dev/null --max-time 2 "http://localhost:${DJANGO_PORT}/"; do
+ waited=$((waited + 1))
+ if [ "$waited" -ge "$timeout" ]; then
+ warn "API not responding after ${timeout}s. Check _data/logs/api.log"
+ return 1
+ fi
+ sleep 1
+ done
+ ok "API responding on :${DJANGO_PORT}"
+}
+
+needs_db_bootstrap() {
+ ! "${COMPOSE[@]}" -f "$COMPOSE_FILE" exec -T postgres \
+ psql -U prowler -d prowler_db -c 'select 1' >/dev/null 2>&1
+}
+
+bootstrap_db_if_needed() {
+ if needs_db_bootstrap; then
+ warn "App DB user not ready. Bootstrapping (deps + migrate + fixtures)..."
+ deps
+ migrate
+ fixtures
+ ok "DB bootstrap complete"
+ fi
+}
+
+all_run() {
+ require_tmux
+ require_uv
+ services_up
+ bootstrap_db_if_needed
+
+ # Wrap a command so it auto-runs as the pane's foreground process and, on
+ # exit (e.g. Ctrl+C), drops into the user's login shell instead of closing.
+ # Avoids the `send-keys` race where keys arrive before zsh+starship are ready.
+ local user_shell="${SHELL:-/bin/zsh}"
+ pane_cmd() {
+ printf 'bash -c %q' "$1; exec ${user_shell}"
+ }
+ local api_cmd worker_cmd pg_cmd
+ api_cmd="$(pane_cmd "$SCRIPT_PATH api")"
+ worker_cmd="$(pane_cmd "$SCRIPT_PATH worker")"
+ pg_cmd="$(pane_cmd "${COMPOSE[*]} -f $COMPOSE_FILE logs -f postgres")"
+
+ # If a tmux server is already running (e.g. another project's session), new
+ # sessions inherit THAT server's env, not the launcher shell's env. Pass our
+ # overrides explicitly so each pane sees the right project name, ports, etc.
+ local -a env_args=()
+ local var
+ for var in COMPOSE_PROJECT_NAME \
+ POSTGRES_HOST POSTGRES_PORT \
+ VALKEY_HOST VALKEY_PORT VALKEY_SCHEME \
+ NEO4J_HOST NEO4J_PORT NEO4J_HTTP_PORT \
+ DJANGO_SETTINGS_MODULE DJANGO_DEBUG DJANGO_PORT \
+ DJANGO_LOGGING_FORMATTER DJANGO_LOGGING_LEVEL \
+ DJANGO_MANAGE_DB_PARTITIONS; do
+ env_args+=(-e "${var}=${!var-}")
+ done
+
+ local expected_panes=3
+
+ if tmux has-session -t "$TMUX_SESSION" 2>/dev/null; then
+ local current_panes
+ current_panes="$(tmux_pane_count)"
+ if [ "$current_panes" -lt "$expected_panes" ]; then
+ warn "Session '$TMUX_SESSION' has $current_panes pane(s), expected $expected_panes. Rebuilding it."
+ tmux kill-session -t "$TMUX_SESSION"
+ else
+ log "Session '$TMUX_SESSION' already exists"
+ fi
+ fi
+
+ if ! tmux has-session -t "$TMUX_SESSION" 2>/dev/null; then
+ log "Creating tmux session '$TMUX_SESSION' (api / worker / db logs)"
+ tmux new-session -d -s "$TMUX_SESSION" -n services -c "$REPO_ROOT" "${env_args[@]}" "$api_cmd"
+ tmux split-window -t "$TMUX_SESSION:0.0" -v -p 50 -c "$REPO_ROOT" "${env_args[@]}" "$worker_cmd"
+ tmux split-window -t "$TMUX_SESSION:0.1" -h -p 50 -c "$REPO_ROOT" "${env_args[@]}" "$pg_cmd"
+ tmux select-pane -t "$TMUX_SESSION:0.0"
+ tmux set-option -t "$TMUX_SESSION" -g mouse on >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g bell-action none >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g visual-bell off >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g monitor-bell off >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g monitor-activity off >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g visual-activity off >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g activity-action none >/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g silence-action none >/dev/null
+ tmux bind-key -T copy-mode MouseDragEnd1Pane send-keys -X copy-pipe-and-cancel "pbcopy" 2>/dev/null
+ tmux bind-key -T copy-mode-vi MouseDragEnd1Pane send-keys -X copy-pipe-and-cancel "pbcopy" 2>/dev/null
+ tmux set-option -t "$TMUX_SESSION" -g status-right " API:${DJANGO_PORT} | DB:${POSTGRES_PORT} | Broker:${VALKEY_PORT} " >/dev/null
+
+ mkdir -p "$REPO_ROOT/_data/logs"
+ pipe_pane_log "$TMUX_SESSION:0.0" api
+ pipe_pane_log "$TMUX_SESSION:0.1" worker
+ pipe_pane_log "$TMUX_SESSION:0.2" postgres
+ fi
+
+ wait_for_api 90
+
+ ok "Dev stack ready (detached)"
+ cat <<EOF
+api_url=http://localhost:${DJANGO_PORT}/api/v1
+api_log=_data/logs/api.log
+worker_log=_data/logs/worker.log
+postgres_log=_data/logs/postgres.log
+EOF
+ cat <<EOF
+attach_cmd=make dev-attach
+stop_cmd=make dev-stop
+EOF
+}
+
+attach_run() {
+ require_tmux
+ if ! tmux has-session -t "$TMUX_SESSION" 2>/dev/null; then
+ warn "No session '$TMUX_SESSION'. Starting it with: $0 all"
+ all_run
+ else
+ local current_panes
+ current_panes="$(tmux_pane_count)"
+ if [ "$current_panes" -lt 3 ]; then
+ warn "Session '$TMUX_SESSION' only has $current_panes pane(s). Rebuilding with db logs."
+ tmux kill-session -t "$TMUX_SESSION"
+ all_run
+ fi
+ fi
+ if [ -n "${TMUX:-}" ]; then
+ tmux switch-client -t "$TMUX_SESSION"
+ else
+ tmux attach-session -t "$TMUX_SESSION"
+ fi
+}
+
+clean_run() {
+ log "Removing stopped containers from the compose project..."
+ "${COMPOSE[@]}" -f "$COMPOSE_FILE" rm -f
+ ok "Stopped containers removed (data volumes under ./_data/ untouched)"
+}
+
+wipe_run() {
+ warn "DESTRUCTIVE: this will tear down everything AND delete ./_data/"
+ warn " postgres database, valkey state, neo4j graph, api jwt keys - all gone."
+ warn " Next start will require 'make dev-setup' from scratch."
+ kill_run
+ if [ -d ./_data ]; then
+ log "Removing ./_data/ ..."
+ rm -rf ./_data
+ fi
+ ok "Wipe complete. Run 'make dev-setup' for a fresh environment."
+}
+
+kill_run() {
+ kill_tmux_session
+ services_down
+ clean_run
+ ok "Dev stack stopped (tmux killed, containers stopped + removed)"
+}
+
+launch_run() {
+ require_uv
+ kill_tmux_session
+ remove_repo_compose_containers
+ clear_dev_port_conflicts
+
+ log "Launching dev stack in tmux inside the current terminal"
+ log " api:${DJANGO_PORT} pg:${POSTGRES_PORT} valkey:${VALKEY_PORT} neo4j:${NEO4J_PORT} neo4j-http:${NEO4J_HTTP_PORT}"
+ all_run
+ attach_run
+}
+
+setup() {
+ services_up
+ deps
+ migrate
+ fixtures
+ ok "Setup complete."
+ cat <<EOF
+
+Next run everything in one window:
+ make dev # api + worker in tmux
+
+API will be available at http://localhost:${DJANGO_PORT}/api/v1/
+EOF
+}
+
+usage() {
+ cat <<EOF
+Usage: $0 <command>
+
+One-window dev (tmux inside the terminal):
+ all api + worker + postgres logs in 3 panes (detached,
+ blocks until API responds,
+ ends with parseable api_url= / *_log= / attach_cmd= / stop_cmd= lines)
+ attach Reattach to the existing dev session
+ Attaches tmux inside the current terminal pane.
+ Pane output is also written to _data/logs/{api,worker,postgres}.log
+ (ANSI-stripped, truncated per run) - usable without attaching
+ kill Stop tmux + stop containers + remove them (full teardown)
+ launch Use fixed ports, clear conflicts, then run 'all' and attach tmux
+
+Platform support:
+ macOS Supported
+ Linux Should work when Docker, tmux, and uv are available
+ Windows Requires script changes before it can be supported
+
+State (containers postgres + valkey + neo4j):
+ up Start postgres + valkey + neo4j (waits for healthchecks)
+ down Stop tmux + postgres + valkey + neo4j (keeps containers around)
+ status Show container status
+ clean Remove all stopped containers in the project (data volumes preserved)
+ wipe Full nuke: kill + clean + delete ./_data/
+
+Python (native, foreground - usually launched via 'all'):
+ api Run Django API (runserver)
+ worker Run Celery worker
+ beat Run Celery beat scheduler
+
+One-shots:
+ setup up + deps + migrate + fixtures (first-time / fresh DB)
+ deps uv sync inside api/
+ migrate Apply migrations to admin DB
+ fixtures Load dev fixtures
+
+Typical flow:
+ make dev-setup # first time only
+ make dev # daily dev
+ make dev-stop # when done
+EOF
+}
+
+case "${1:-help}" in
+ all) shift; if [ "$#" -gt 0 ]; then warn "'all $*' is not supported. Use: $0 all"; exit 1; fi; all_run ;;
+ attach) attach_run ;;
+ kill) kill_run ;;
+ launch) launch_run ;;
+ clean) clean_run ;;
+ wipe) wipe_run ;;
+ up) services_up ;;
+ down) services_down ;;
+ status) services_status ;;
+ api) api_run ;;
+ worker) worker_run ;;
+ beat) beat_run ;;
+ setup) setup ;;
+ deps) deps ;;
+ migrate) migrate ;;
+ fixtures) fixtures ;;
+ help|-h|--help|*) usage ;;
+esac
diff --git a/skills/README.md b/skills/README.md
index 999760d079..cfc65527a9 100644
--- a/skills/README.md
+++ b/skills/README.md
@@ -23,12 +23,12 @@ Run the setup script to configure skills for all supported AI coding assistants:
This creates symlinks so each tool finds skills in its expected location:
-| Tool | Symlink Created |
-|------|-----------------|
-| Claude Code / OpenCode | `.claude/skills/` |
-| Codex (OpenAI) | `.codex/skills/` |
-| GitHub Copilot | `.github/skills/` |
-| Gemini CLI | `.gemini/skills/` |
+| Tool | Created by setup |
+|------|------------------|
+| Claude Code | `.claude/skills/` symlink and `CLAUDE.md` |
+| Gemini CLI | `.gemini/skills/` symlink and `GEMINI.md` |
+| Codex (OpenAI) | `.codex/skills/` symlink (uses `AGENTS.md` natively) |
+| GitHub Copilot | `.github/copilot-instructions.md` symlink to `AGENTS.md` |
After running setup, restart your AI coding assistant to load the skills.
@@ -36,7 +36,7 @@ After running setup, restart your AI coding assistant to load the skills.
Skills are automatically discovered by the AI agent. To manually load a skill during a session:
-```
+```text
Read skills/{skill-name}/SKILL.md
```
@@ -90,7 +90,7 @@ Patterns tailored for Prowler development:
## Directory Structure
-```
+```text
skills/
├── {skill-name}/
│ ├── SKILL.md # Required - main instrunsction and metadata
@@ -118,7 +118,7 @@ This reads `metadata.scope` and `metadata.auto_invoke` from each `SKILL.md` and
Use the `skill-creator` skill for guidance:
-```
+```text
Read skills/skill-creator/SKILL.md
```
diff --git a/skills/django-drf/SKILL.md b/skills/django-drf/SKILL.md
index 46c1c1bc93..7d73ed1543 100644
--- a/skills/django-drf/SKILL.md
+++ b/skills/django-drf/SKILL.md
@@ -54,7 +54,7 @@ When implementing a new endpoint, review these patterns in order:
## Decision Trees
### Which Serializer?
-```
+```text
GET list/retrieve → <Model>Serializer
POST create → <Model>CreateSerializer
PATCH update → <Model>UpdateSerializer
@@ -62,7 +62,7 @@ PATCH update → <Model>UpdateSerializer
```
### Which Base Serializer?
-```
+```text
Read-only serializer → BaseModelSerializerV1
Create with tenant_id → RLSSerializer + BaseWriteSerializer (auto-injects tenant_id on create)
Update with validation → BaseWriteSerializer (tenant_id already exists on object)
@@ -70,14 +70,14 @@ Non-model data → BaseSerializerV1
```
### Which Filter Base?
-```
+```text
Direct FK to Provider → BaseProviderFilter
FK via Scan → BaseScanProviderFilter
No provider relation → FilterSet
```
### Which Base ViewSet?
-```
+```text
RLS-protected model → BaseRLSViewSet (most common)
Tenant operations → BaseTenantViewset
User operations → BaseUserViewset
@@ -85,7 +85,7 @@ No RLS required → BaseViewSet (rare)
```
### Resource Name Format?
-```
+```text
Single word model → plural lowercase (Provider → providers)
Multi-word model → plural lowercase kebab (ProviderGroup → provider-groups)
Through/join model → parent-child pattern (UserRoleRelationship → user-roles)
@@ -490,7 +490,7 @@ When implementing or debugging, query these libraries via `mcp_context7_query-do
| **drf-spectacular** | `/tfranzel/drf-spectacular` | OpenAPI schema, `@extend_schema` |
**Example queries:**
-```
+```text
mcp_context7_query-docs(libraryId="/websites/django-rest-framework", query="ViewSet get_queryset best practices")
mcp_context7_query-docs(libraryId="/tfranzel/drf-spectacular", query="extend_schema examples for custom actions")
mcp_context7_query-docs(libraryId="/websites/djangoproject_en_5_2", query="model constraints and indexes")
diff --git a/skills/django-drf/references/file-locations.md b/skills/django-drf/references/file-locations.md
index 30dab71550..d0f63ad042 100644
--- a/skills/django-drf/references/file-locations.md
+++ b/skills/django-drf/references/file-locations.md
@@ -16,7 +16,7 @@
## ViewSet Hierarchy
-```
+```text
BaseViewSet (minimal - no RLS/auth)
│
├── BaseRLSViewSet (+ tenant filtering, RLS-protected models)
@@ -31,7 +31,7 @@ BaseViewSet (minimal - no RLS/auth)
## Serializer Hierarchy
-```
+```text
BaseModelSerializerV1 (JSON:API defaults, read_only_fields)
│
├── RLSSerializer (auto-injects tenant_id from request)
@@ -47,7 +47,7 @@ BaseModelSerializerV1 (JSON:API defaults, read_only_fields)
## Filter Hierarchy
-```
+```text
FilterSet (django-filter)
│
├── CommonFindingFilters (mixin for date ranges, delta, status)
diff --git a/skills/django-drf/references/json-api-conventions.md b/skills/django-drf/references/json-api-conventions.md
index c51326b0b2..9a546671fa 100644
--- a/skills/django-drf/references/json-api-conventions.md
+++ b/skills/django-drf/references/json-api-conventions.md
@@ -2,7 +2,7 @@
## Content Type
-```
+```http
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json
```
diff --git a/skills/django-migration-psql/SKILL.md b/skills/django-migration-psql/SKILL.md
index d292036dd0..bca8949fda 100644
--- a/skills/django-migration-psql/SKILL.md
+++ b/skills/django-migration-psql/SKILL.md
@@ -364,7 +364,7 @@ Batch utilities: `api/db_utils.py` (`batch_delete`, `create_objects_in_batches`,
## Decision tree
-```
+```text
Auto-generated migration?
├── Yes → Split it following the rules below
└── No → Review it against the rules below
@@ -420,7 +420,7 @@ When implementing or debugging migration patterns, query these libraries via `mc
| django-postgres-extra | `/SectorLabs/django-postgres-extra` | Partitioned models, `PostgresPartitionedModel`, partition management |
**Example queries:**
-```
+```text
mcp_context7_query-docs(libraryId="/websites/djangoproject_en_5_1", query="migration operations AddIndex RunPython atomic")
mcp_context7_query-docs(libraryId="/websites/djangoproject_en_5_1", query="database indexes Meta class concurrently")
mcp_context7_query-docs(libraryId="/websites/postgresql_org_docs_current", query="CREATE INDEX CONCURRENTLY partitioned table")
diff --git a/skills/gh-aw/SKILL.md b/skills/gh-aw/SKILL.md
index b45d4d151e..d4c3a0c829 100644
--- a/skills/gh-aw/SKILL.md
+++ b/skills/gh-aw/SKILL.md
@@ -30,7 +30,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch
## File Layout
-```
+```text
.github/
├── workflows/
│ ├── {name}.md # Frontmatter + thin context dispatcher
@@ -308,7 +308,7 @@ After modifying any `.github/workflows/*.md`:
Add to repo root so lock files auto-resolve on merge:
-```
+```text
.github/workflows/*.lock.yml linguist-generated=true merge=ours
```
diff --git a/skills/jsonapi/SKILL.md b/skills/jsonapi/SKILL.md
index a8959a2199..db11146929 100644
--- a/skills/jsonapi/SKILL.md
+++ b/skills/jsonapi/SKILL.md
@@ -35,7 +35,7 @@ This skill focuses on **spec compliance**. For **implementation patterns** (View
If Context7 MCP is available, query the JSON:API spec directly:
-```
+```text
mcp_context7_resolve-library-id(query="jsonapi specification")
mcp_context7_query-docs(libraryId="<resolved-id>", query="[specific topic: relationships, errors, etc.]")
```
@@ -44,7 +44,7 @@ mcp_context7_query-docs(libraryId="<resolved-id>", query="[specific topic: relat
If Context7 is not available, fetch from the official spec:
-```
+```text
WebFetch(url="https://jsonapi.org/format/", prompt="Extract rules for [specific topic]")
```
diff --git a/skills/nextjs-16/SKILL.md b/skills/nextjs-16/SKILL.md
index 272339c2da..cea38e255d 100644
--- a/skills/nextjs-16/SKILL.md
+++ b/skills/nextjs-16/SKILL.md
@@ -14,7 +14,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## App Router File Conventions
-```
+```text
app/
├── layout.tsx # Root layout (required)
├── page.tsx # Home page (/)
diff --git a/skills/playwright/SKILL.md b/skills/playwright/SKILL.md
index d9009d6f4a..60c1db9fd5 100644
--- a/skills/playwright/SKILL.md
+++ b/skills/playwright/SKILL.md
@@ -36,7 +36,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## File Structure
-```
+```text
tests/
├── base-page.ts # Parent class for ALL pages
├── helpers.ts # Shared utilities
@@ -182,14 +182,14 @@ export class SignUpPage extends BasePage {
## Refactoring Guidelines
-### Move to `BasePage` when:
+### Move to `BasePage` when
- ✅ Navigation helpers used by multiple pages (`waitForPageLoad()`, `getCurrentUrl()`)
- ✅ Common UI interactions (notifications, modals, theme toggles)
- ✅ Verification patterns repeated across pages (`isVisible()`, `waitForVisible()`)
- ✅ Error handling that applies to all pages
- ✅ Screenshot utilities for debugging
-### Move to `helpers.ts` when:
+### Move to `helpers.ts` when
- ✅ Test data generation (`generateUniqueEmail()`, `generateTestUser()`)
- ✅ Setup/teardown utilities (`createTestUser()`, `cleanupTestData()`)
- ✅ Custom assertions (`expectNotificationToContain()`)
diff --git a/skills/postgresql-indexing/SKILL.md b/skills/postgresql-indexing/SKILL.md
index 7fac9f4ecd..615000ad9e 100644
--- a/skills/postgresql-indexing/SKILL.md
+++ b/skills/postgresql-indexing/SKILL.md
@@ -225,7 +225,7 @@ Rebuild invalid indexes without locking writes:
REINDEX INDEX CONCURRENTLY index_name;
```
-### Understanding _ccnew and _ccold artifacts
+### Understanding _ccnew and_ccold artifacts
When `CREATE INDEX CONCURRENTLY` or `REINDEX INDEX CONCURRENTLY` is interrupted, temporary indexes may remain:
@@ -377,7 +377,8 @@ VACUUM (ANALYZE) table_name;
| PostgreSQL | `/websites/postgresql_org_docs_current` | Index types, EXPLAIN, partitioned table indexing, REINDEX |
**Example queries:**
-```
+
+```text
mcp_context7_query-docs(libraryId="/websites/postgresql_org_docs_current", query="CREATE INDEX CONCURRENTLY partitioned table")
mcp_context7_query-docs(libraryId="/websites/postgresql_org_docs_current", query="EXPLAIN ANALYZE BUFFERS query plan")
mcp_context7_query-docs(libraryId="/websites/postgresql_org_docs_current", query="partial index WHERE clause")
diff --git a/skills/prowler-api/SKILL.md b/skills/prowler-api/SKILL.md
index 604d7fe4d2..0c7dc86222 100644
--- a/skills/prowler-api/SKILL.md
+++ b/skills/prowler-api/SKILL.md
@@ -61,7 +61,7 @@ Provider.objects.filter(connected=True) # Requires rls_transaction context
### RLS Transaction Flow
-```
+```text
Request → Authentication → BaseRLSViewSet.initial()
│
├─ Extract tenant_id from JWT
@@ -92,7 +92,7 @@ When implementing Prowler-specific API features:
## Decision Trees
### Which Base Model?
-```
+```text
Tenant-scoped data → RowLevelSecurityProtectedModel
Global/shared data → models.Model + BaseSecurityConstraint (rare)
Partitioned time-series → PostgresPartitionedModel + RowLevelSecurityProtectedModel
@@ -100,14 +100,14 @@ Soft-deletable → Add is_deleted + ActiveProviderManager
```
### Which Manager?
-```
+```text
Normal queries → Model.objects (excludes deleted)
Include deleted records → Model.all_objects
Celery task context → Must use rls_transaction() first
```
### Which Database?
-```
+```text
Standard API queries → default (automatic via ViewSet)
Read-only operations → replica (automatic for GET in BaseRLSViewSet)
Auth/admin operations → MainRouter.admin_db
@@ -115,7 +115,7 @@ Cross-tenant lookups → MainRouter.admin_db (use sparingly!)
```
### Celery Task Decorator Order?
-```
+```python
@shared_task(base=RLSTask, name="...", queue="...")
@set_tenant # First: sets tenant context
@handle_provider_deletion # Second: handles deleted providers
@@ -496,7 +496,7 @@ When implementing or debugging Prowler-specific patterns, query these libraries
| **Django** | `/websites/djangoproject_en_5_2` | Models, ORM, constraints, indexes |
**Example queries:**
-```
+```text
mcp_context7_query-docs(libraryId="/websites/celeryq_dev_en_stable", query="shared_task decorator retry patterns")
mcp_context7_query-docs(libraryId="/celery/django-celery-beat", query="periodic task database scheduler")
mcp_context7_query-docs(libraryId="/websites/djangoproject_en_5_2", query="model constraints CheckConstraint UniqueConstraint")
diff --git a/skills/prowler-api/references/configuration.md b/skills/prowler-api/references/configuration.md
index 677f999cc4..0a68d58951 100644
--- a/skills/prowler-api/references/configuration.md
+++ b/skills/prowler-api/references/configuration.md
@@ -2,7 +2,7 @@
## Settings File Structure
-```
+```text
api/src/backend/config/
├── django/
│ ├── base.py # Base settings (all environments)
diff --git a/skills/prowler-api/references/modeling-decisions.md b/skills/prowler-api/references/modeling-decisions.md
index 68923c4ef4..c11ed585ec 100644
--- a/skills/prowler-api/references/modeling-decisions.md
+++ b/skills/prowler-api/references/modeling-decisions.md
@@ -247,7 +247,7 @@ class JSONAPIMeta:
## Decision Tree: New Model
-```
+```text
Is it tenant-scoped data?
├── Yes → Inherit RowLevelSecurityProtectedModel
│ Add RowLevelSecurityConstraint
diff --git a/skills/prowler-attack-paths-query/SKILL.md b/skills/prowler-attack-paths-query/SKILL.md
index fb25d4fa43..a70734aa6f 100644
--- a/skills/prowler-attack-paths-query/SKILL.md
+++ b/skills/prowler-attack-paths-query/SKILL.md
@@ -2,13 +2,14 @@
name: prowler-attack-paths-query
description: >
Creates Prowler Attack Paths openCypher queries using the Cartography schema as the source of truth
- for node labels, properties, and relationships. Also covers Prowler-specific additions (Internet node,
- ProwlerFinding, internal isolation labels) and $provider_uid scoping for predefined queries.
+ for node labels, properties, and relationships. Covers Prowler-specific additions (Internet node,
+ ProwlerFinding, internal isolation labels), $provider_uid scoping, and list-property item nodes
+ with typed `HAS_*` edges that run efficiently on both Neo4j and Amazon Neptune sinks.
Trigger: When creating or updating Attack Paths queries.
license: Apache-2.0
metadata:
author: prowler-cloud
- version: "2.0"
+ version: "3.0"
scope: [root, api]
auto_invoke:
- "Creating Attack Paths queries"
@@ -19,36 +20,30 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, Task
## Overview
-Attack Paths queries are openCypher queries that analyze cloud infrastructure graphs (ingested via Cartography) to detect security risks like privilege escalation paths, network exposure, and misconfigurations.
-
-Queries are written in **openCypher Version 9** for compatibility with both Neo4j and Amazon Neptune.
+Attack Paths queries are read-only openCypher queries over a Cartography-ingested cloud graph that detect privilege escalation chains, network exposure, and other graph-shaped security risks. Queries are written in openCypher Version 9 so they run on both Neo4j and Amazon Neptune sinks.
---
## Two query audiences
-This skill covers two types of queries with different isolation mechanisms:
+| | Predefined queries | Custom queries |
+| ------------------ | ----------------------------------------------------------- | --------------------------------------------------------------------- |
+| Where they live | `api/src/backend/api/attack_paths/queries/{provider}.py` | User-supplied via the custom query API endpoint |
+| Provider isolation | `AWSAccount {id: $provider_uid}` anchor + path connectivity | Automatic `_Provider_{uuid}` label injection by `cypher_sanitizer.py` |
+| What to write | Chain every MATCH from the `aws` variable | Plain Cypher, no isolation boilerplate |
+| Internal labels | Never use | Never use (system-injected) |
-| | Predefined queries | Custom queries |
-|---|---|---|
-| **Where they live** | `api/src/backend/api/attack_paths/queries/{provider}.py` | User/LLM-supplied via the custom query API endpoint |
-| **Provider isolation** | `AWSAccount {id: $provider_uid}` anchor + path connectivity | Automatic `_Provider_{uuid}` label injection via `cypher_sanitizer.py` |
-| **What to write** | Chain every MATCH from the `aws` variable | Plain Cypher, no isolation boilerplate needed |
-| **Internal labels** | Never use (`_ProviderResource`, `_Tenant_*`, `_Provider_*`) | Never use (injected automatically by the system) |
+**Predefined queries**: every node must be reachable from the `AWSAccount` root via graph traversal. That is the isolation boundary.
-**For predefined queries**: every node must be reachable from the `AWSAccount` root via graph traversal. This is the isolation boundary.
-
-**For custom queries**: write natural Cypher without isolation concerns. The query runner injects a `_Provider_{uuid}` label into every node pattern before execution, and a post-query filter catches edge cases.
+**Custom queries**: write natural Cypher. The runner injects a `_Provider_{uuid}` label into every node pattern, and a post-query filter handles edge cases.
---
-## Input Sources
+## Input sources
-Queries can be created from:
+Two sources for new queries:
-1. **pathfinding.cloud ID** (e.g., `ECS-001`, `GLUE-001`)
- - Reference: https://github.com/DataDog/pathfinding.cloud
- - The aggregated `paths.json` is too large for WebFetch. Use Bash:
+1. **pathfinding.cloud ID** (e.g. `ECS-001`, `GLUE-001`), the Datadog research catalogue. The aggregated `paths.json` is too large for WebFetch:
```bash
# Fetch a single path by ID
@@ -64,28 +59,24 @@ Queries can be created from:
| jq -r '.[] | select(.id | startswith("ecs")) | "\(.id): \(.name)"'
```
- If `jq` is not available, use `python3 -c "import json,sys; ..."` as a fallback.
+ If `jq` is unavailable, use `python3 -c "import json,sys; ..."`.
-2. **Natural language description** from the user
+2. **Natural language description** from the requester.
---
-## Query Structure
+## Query structure
### Provider scoping parameter
-One parameter is injected automatically by the query runner:
+| Parameter | Property | Used on | Purpose |
+| --------------- | -------- | ------------ | -------------------------------------- |
+| `$provider_uid` | `id` | `AWSAccount` | Scopes the query to a specific account |
-| Parameter | Property it matches | Used on | Purpose |
-| --------------- | ------------------- | ------------ | -------------------------------- |
-| `$provider_uid` | `id` | `AWSAccount` | Scopes to a specific AWS account |
-
-All other nodes are isolated by path connectivity from the `AWSAccount` anchor.
+The runner binds `$provider_uid` automatically. Every other node is isolated by path connectivity from the `AWSAccount` anchor.
### Imports
-All query files start with these imports:
-
```python
from api.attack_paths.queries.types import (
AttackPathsQueryAttribution,
@@ -95,29 +86,33 @@ from api.attack_paths.queries.types import (
from tasks.jobs.attack_paths.config import PROWLER_FINDING_LABEL
```
-The `PROWLER_FINDING_LABEL` constant (value: `"ProwlerFinding"`) is used via f-string interpolation in all queries. Never hardcode the label string.
+Always use `PROWLER_FINDING_LABEL` via f-string interpolation, never hardcode `"ProwlerFinding"`.
-### Privilege escalation sub-patterns
+### Definition fields
-There are four distinct privilege escalation patterns. Choose based on the attack type:
+- **id**: kebab-case `{provider}-{description}`, e.g. `aws-ec2-privesc-passrole-iam`.
+- **name**: short, human-friendly label. Sourced queries append the reference ID: `"EC2 Instance Launch with Privileged Role (EC2-001)"`.
+- **short_description**: one sentence, no technical permissions.
+- **description**: full technical explanation, plain text.
+- **provider**: `aws`, `azure`, `gcp`, `kubernetes`, or `github`.
+- **cypher**: f-string Cypher body. Literal `{` / `}` are escaped as `{{` / `}}`.
+- **parameters**: `parameters=[]` if none.
+- **attribution**: optional `AttackPathsQueryAttribution(text, link)` for sourced queries. `link` uses the lowercase ID.
-| Sub-pattern | Target | `path_target` shape | Example |
-|---|---|---|---|
-| Self-escalation | Principal's own policies | `(aws)--(target_policy:AWSPolicy)--(principal)` | IAM-001 |
-| Lateral to user | Other IAM users | `(aws)--(target_user:AWSUser)` | IAM-002 |
-| Assume-role lateral | Assumable roles | `(aws)--(target_role:AWSRole)<-[:STS_ASSUMEROLE_ALLOW]-(principal)` | IAM-014 |
-| PassRole + service | Service-trusting roles | `(aws)--(target_role:AWSRole)-[:TRUSTS_AWS_PRINCIPAL]->(...)` | EC2-001 |
+Append the constant to the `{PROVIDER}_QUERIES` list at the bottom of the provider file.
-#### Self-escalation (e.g., IAM-001)
+---
-The principal modifies resources attached to itself. `path_target` loops back to `principal`:
+## Predefined query template
+
+The canonical shape combines a principal walk, an optional target walk, deduplicated nodes, and a typed finding overlay:
```python
AWS_{QUERY_NAME} = AttackPathsQueryDefinition(
id="aws-{kebab-case-name}",
- name="{Human-friendly label} ({REFERENCE_ID})",
- short_description="{Brief explanation, no technical permissions.}",
- description="{Detailed description of the attack vector and impact.}",
+ name="{Label} ({REFERENCE_ID})",
+ short_description="{One sentence.}",
+ description="{Full technical explanation.}",
attribution=AttackPathsQueryAttribution(
text="pathfinding.cloud - {REFERENCE_ID} - {permission}",
link="https://pathfinding.cloud/paths/{reference_id_lowercase}",
@@ -125,29 +120,27 @@ AWS_{QUERY_NAME} = AttackPathsQueryDefinition(
provider="aws",
cypher=f"""
// Find principals with {permission}
- MATCH path_principal = (aws:AWSAccount {{id: $provider_uid}})--(principal:AWSPrincipal)--(policy:AWSPolicy)--(stmt:AWSPolicyStatement)
- WHERE stmt.effect = 'Allow'
- AND any(action IN stmt.action WHERE
- toLower(action) = '{permission_lowercase}'
- OR toLower(action) = '{service}:*'
- OR action = '*'
- )
+ MATCH path_principal = (aws:AWSAccount {{id: $provider_uid}})--(principal:AWSPrincipal)-[:POLICY]->(policy:AWSPolicy)-[:STATEMENT]->(stmt:AWSPolicyStatement {{effect: 'Allow'}})
+ MATCH (stmt)-[:HAS_ACTION]->(act:AWSPolicyStatementActionItem)
+ WHERE toLower(act.value) IN ['{permission_lowercase}', '{service}:*']
+ OR act.value = '*'
+ WITH DISTINCT aws, principal, stmt, path_principal
- // Find target resources attached to the same principal
+ // Target resources attached to the same principal (sub-patterns below)
MATCH path_target = (aws)--(target_policy:AWSPolicy)--(principal)
WHERE target_policy.arn CONTAINS $provider_uid
- AND any(resource IN stmt.resource WHERE
- resource = '*'
- OR target_policy.arn CONTAINS resource
- )
+ MATCH (stmt)-[:HAS_RESOURCE]->(res:AWSPolicyStatementResourceItem)
+ WHERE res.value = '*'
+ OR target_policy.arn CONTAINS res.value
+ WITH DISTINCT path_principal, path_target
WITH collect(path_principal) + collect(path_target) AS paths
UNWIND paths AS p
UNWIND nodes(p) AS n
WITH paths, collect(DISTINCT n) AS unique_nodes
UNWIND unique_nodes AS n
- OPTIONAL MATCH (n)-[pfr]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
+ OPTIONAL MATCH (n)-[pfr:HAS_FINDING]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr
""",
@@ -155,158 +148,146 @@ AWS_{QUERY_NAME} = AttackPathsQueryDefinition(
)
```
-#### Other sub-pattern `path_target` shapes
+Key points:
-The other 3 sub-patterns share the same `path_principal`, deduplication tail, and RETURN as self-escalation. Only the `path_target` MATCH differs:
+- The principal walk types the `POLICY` and `STATEMENT` hops. Both are low-fan-out (each principal has a handful of policies; each policy a handful of statements), so the typed edge lets the planner cost a cheap inline filter.
+- The `(aws)--` hub hops stay anonymous. `AWSAccount` is a high-degree node that fans out to every principal, role, policy, and resource in the account; typing those edges forces the planner to enumerate from the hub and collapses performance on multi-tenant Neptune.
+- Other relationship types appear only where the file's existing queries already use one (`TRUSTS_AWS_PRINCIPAL`, `STS_ASSUMEROLE_ALLOW`, `MEMBER_AWS_GROUP`, `HAS_EXECUTION_ROLE`).
+- The finding probe is typed `:HAS_FINDING` and left undirected. The type lets Neptune apply an inline edge filter; the lack of direction matches the convention of the rest of the file.
+- Collapse duplicate rows after each permission gate with `WITH DISTINCT`, carrying only the variables needed by later clauses.
+- Each `HAS_*` traversal is its own `MATCH` clause with a `WHERE` on the child item node. `WITH DISTINCT path_principal, path_target` precedes `collect(path...)` to dedupe the row multiplication produced by the joins.
+- The `RETURN` shape `paths, dpf, dpfr` is the contract the serializer and visualiser depend on. Do not change it.
+
+---
+
+## Privilege escalation sub-patterns
+
+Four `path_target` shapes cover the common attack types. Each shares the canonical template's `path_principal`, deduplication tail, and `RETURN`; only the `path_target` MATCH and its resource predicate differ.
+
+| Sub-pattern | Target | `path_target` shape | Example |
+| ------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------- | ------- |
+| Self-escalation | Principal's own policies | `(aws)--(target_policy:AWSPolicy)--(principal)` | IAM-001 |
+| Lateral to user | Other IAM users | `(aws)--(target_user:AWSUser)` | IAM-002 |
+| Assume-role lateral | Assumable roles | `(aws)--(target_role:AWSRole)-[:STS_ASSUMEROLE_ALLOW]-(principal)` | IAM-014 |
+| PassRole + service | Service-trusting roles | `(aws)--(target_role:AWSRole)-[:TRUSTS_AWS_PRINCIPAL]-(:AWSPrincipal {arn: '{service}.amazonaws.com'})` | EC2-001 |
+
+**Multi-permission queries** (e.g. PassRole plus a service-create action) add permission gates before `path_target`. Reuse the per-query counter for new variables (`act2`, `policy2`, `stmt2`) and collapse rows after each gate:
```cypher
-// Lateral to user (e.g., IAM-002) - targets other IAM users
-MATCH path_target = (aws)--(target_user:AWSUser)
-WHERE any(resource IN stmt.resource WHERE resource = '*' OR target_user.arn CONTAINS resource OR resource CONTAINS target_user.name)
-
-// Assume-role lateral (e.g., IAM-014) - targets roles the principal can assume
-MATCH path_target = (aws)--(target_role:AWSRole)<-[:STS_ASSUMEROLE_ALLOW]-(principal)
-WHERE any(resource IN stmt.resource WHERE resource = '*' OR target_role.arn CONTAINS resource OR resource CONTAINS target_role.name)
-
-// PassRole + service (e.g., EC2-001) - targets roles trusting a service
-MATCH path_target = (aws)--(target_role:AWSRole)-[:TRUSTS_AWS_PRINCIPAL]->(:AWSPrincipal {arn: '{service}.amazonaws.com'})
-WHERE any(resource IN stmt.resource WHERE resource = '*' OR target_role.arn CONTAINS resource OR resource CONTAINS target_role.name)
+MATCH (principal)-[:POLICY]->(policy2:AWSPolicy)-[:STATEMENT]->(stmt2:AWSPolicyStatement {effect: 'Allow'})
+MATCH (stmt2)-[:HAS_ACTION]->(act2:AWSPolicyStatementActionItem)
+WHERE toLower(act2.value) IN ['service:*', 'service:createsomething']
+ OR act2.value = '*'
+WITH DISTINCT aws, principal, stmt, stmt2, path_principal
```
-**Multi-permission**: PassRole queries require a second permission. Add `MATCH (principal)--(policy2:AWSPolicy)--(stmt2:AWSPolicyStatement)` with its own WHERE before `path_target`, then check BOTH `stmt.resource` AND `stmt2.resource` against the target. See IAM-015 or EC2-001 in `aws.py` for examples.
+If a permission is an existence-only gate whose statement resource is not checked later, keep the policy and statement anonymous and carry only the variables still needed:
-### Network exposure pattern
+```cypher
+MATCH (principal)-[:POLICY]->(:AWSPolicy)-[:STATEMENT]->(:AWSPolicyStatement {effect: 'Allow'})-[:HAS_ACTION]->(act3:AWSPolicyStatementActionItem)
+WHERE toLower(act3.value) IN ['service:*', 'service:othersomething']
+ OR act3.value = '*'
+WITH DISTINCT aws, principal, stmt, path_principal
+```
-The Internet node is reached via `CAN_ACCESS` through the already-scoped resource, not via a standalone lookup:
+When all matching principals can target the same independent resource set, collect principal paths before expanding targets instead of creating one row per principal-target pair:
+
+```cypher
+WITH aws, collect(DISTINCT path_principal) AS principal_paths
+MATCH path_target = (aws)--(target)
+WITH principal_paths, collect(DISTINCT path_target) AS target_paths
+WITH principal_paths + target_paths AS paths
+```
+
+Statements that constrain a target are still checked via `HAS_RESOURCE` traversals (`res`, `res2`). See IAM-015 or EC2-001 in `aws.py`.
+
+---
+
+## Network exposure pattern
+
+The Internet node is reached via `CAN_ACCESS` through an already-scoped resource, never as a standalone lookup:
```python
-AWS_{QUERY_NAME} = AttackPathsQueryDefinition(
- id="aws-{kebab-case-name}",
- name="{Human-friendly label}",
- short_description="{Brief explanation.}",
- description="{Detailed description.}",
- provider="aws",
- cypher=f"""
- // Match exposed resources (MUST chain from `aws`)
- MATCH path = (aws:AWSAccount {{id: $provider_uid}})--(resource:EC2Instance)
- WHERE resource.exposed_internet = true
+cypher=f"""
+ // Resource scoped through the account anchor
+ MATCH path = (aws:AWSAccount {{id: $provider_uid}})--(resource:EC2Instance)
+ WHERE resource.exposed_internet = true
- // Internet node reached via path connectivity through the resource
- OPTIONAL MATCH (internet:Internet)-[can_access:CAN_ACCESS]->(resource)
+ // Internet node reached via path connectivity through the resource
+ OPTIONAL MATCH (internet:Internet)-[can_access:CAN_ACCESS]->(resource)
- WITH collect(path) AS paths, head(collect(internet)) AS internet, collect(can_access) AS can_access
- UNWIND paths AS p
- UNWIND nodes(p) AS n
+ WITH collect(path) AS paths, head(collect(internet)) AS internet, collect(can_access) AS can_access
+ UNWIND paths AS p
+ UNWIND nodes(p) AS n
- WITH paths, internet, can_access, collect(DISTINCT n) AS unique_nodes
- UNWIND unique_nodes AS n
- OPTIONAL MATCH (n)-[pfr]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
+ WITH paths, internet, can_access, collect(DISTINCT n) AS unique_nodes
+ UNWIND unique_nodes AS n
+ OPTIONAL MATCH (n)-[pfr:HAS_FINDING]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
- RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr,
- internet, can_access
- """,
- parameters=[],
-)
+ RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr,
+ internet, can_access
+"""
```
-### Register in query list
-
-Add to the `{PROVIDER}_QUERIES` list at the bottom of the file:
-
-```python
-AWS_QUERIES: list[AttackPathsQueryDefinition] = [
- # ... existing queries ...
- AWS_{NEW_QUERY_NAME}, # Add here
-]
-```
+The `CAN_ACCESS` edge stays typed and directed (`-[:CAN_ACCESS]->`); that is its canonical sync-time orientation.
---
-## Step-by-step creation process
+## List-typed properties as child nodes
-### 1. Read the queries module
+Some Cartography node properties carry a list of values: `AWSPolicyStatement.action`, `AWSPolicyStatement.resource`, `KMSKey.encryption_algorithms`, `CloudFrontDistribution.aliases`, and many others. The graph models each such property as a set of child item nodes connected to the parent by a typed edge. Queries reach the values by traversing the edge; the parent does not carry the list as a single field.
-**FIRST**, read all files in the queries module to understand the structure, type definitions, registration, and existing style:
+### Naming convention
-```
-api/src/backend/api/attack_paths/queries/
-├── __init__.py # Module exports
-├── types.py # AttackPathsQueryDefinition, AttackPathsQueryParameterDefinition
-├── registry.py # Query registry logic
-└── {provider}.py # Provider-specific queries (e.g., aws.py)
+For a list-typed parent property the sink stores:
+
+- **Child label**: `<ParentLabel><PropertyPascal>Item`. Example: `AWSPolicyStatement.resource` → `AWSPolicyStatementResourceItem`.
+- **Edge type**: `HAS_<PROPERTY_UPPER>`. Example: `resource` → `HAS_RESOURCE`.
+- **Child property**: `value` (a single scalar string) for scalar-list properties. For list-of-dict properties (rare; for example `SecretsManagerSecretVersion.tags`) the child carries the dict keys as named fields per the catalog's `field_map`.
+
+### Variable naming for child-item matches
+
+`aws.py` uses a per-query counter for each `HAS_*` traversal so chained matches stay unambiguous:
+
+| Edge | First | Second | Third |
+| ----------------- | ------ | ------- | ------- |
+| `HAS_ACTION` | `act` | `act2` | `act3` |
+| `HAS_RESOURCE` | `res` | `res2` | `res3` |
+| `HAS_NOTACTION` | `nact` | `nact2` | `nact3` |
+| `HAS_NOTRESOURCE` | `nres` | `nres2` | `nres3` |
+
+The counter resets at the top of every query.
+
+### Example - action match
+
+Find statements that grant `iam:PassRole`, `iam:*`, or `*`. Traverse the `HAS_ACTION` edge in its own `MATCH` clause and apply the predicate in the attached `WHERE`:
+
+```cypher
+MATCH (stmt:AWSPolicyStatement {effect: 'Allow'})
+MATCH (stmt)-[:HAS_ACTION]->(act:AWSPolicyStatementActionItem)
+WHERE toLower(act.value) IN ['iam:passrole', 'iam:*']
+ OR act.value = '*'
```
-**DO NOT** use generic templates. Match the exact style of existing queries in the file.
+The literal-action list is case-folded with `toLower(act.value)` because IAM authors mix case (`iam:PassRole`, `iam:passrole`); the `*` wildcard never lower-cases.
-### 2. Fetch and consult the Cartography schema
+### Example - resource ARN match
-**This is the most important step.** Every node label, property, and relationship in the query must exist in the Cartography schema for the pinned version. Do not guess or rely on memory.
+Find statements whose resource can target a specific role:
-Check `api/pyproject.toml` for the Cartography dependency, then fetch the schema:
-
-```bash
-grep cartography api/pyproject.toml
+```cypher
+MATCH path_target = (aws)--(target_role:AWSRole)
+MATCH (stmt)-[:HAS_RESOURCE]->(res:AWSPolicyStatementResourceItem)
+WHERE res.value = '*'
+ OR res.value CONTAINS target_role.name
+ OR target_role.arn CONTAINS res.value
```
-Build the schema URL (ALWAYS use the specific tag, not master/main):
+Three predicates cover the cases: full wildcard (`*`), pattern containing the role name (`arn:aws:iam::*:role/admin*`), and pattern that is a prefix or component of the actual ARN.
-```
-# Git dependency (prowler-cloud/cartography@0.126.1):
-https://raw.githubusercontent.com/prowler-cloud/cartography/refs/tags/0.126.1/docs/root/modules/{provider}/schema.md
+### Catalog of list properties
-# PyPI dependency (cartography = "^0.126.0"):
-https://raw.githubusercontent.com/cartography-cncf/cartography/refs/tags/0.126.0/docs/root/modules/{provider}/schema.md
-```
-
-Read the schema to discover available node labels, properties, and relationships for the target resources. Internal labels (`_ProviderResource`, `_AWSResource`, `_Tenant_*`, `_Provider_*`) exist for isolation but should never appear in queries.
-
-### 4. Create query definition
-
-Use the appropriate pattern (privilege escalation or network exposure) with:
-
-- **id**: `{provider}-{kebab-case-description}`
-- **name**: Short, human-friendly label. For sourced queries, append the reference ID: `"EC2 Instance Launch with Privileged Role (EC2-001)"`.
-- **short_description**: Brief explanation, no technical permissions.
-- **description**: Full technical explanation. Plain text only.
-- **provider**: Provider identifier (aws, azure, gcp, kubernetes, github)
-- **cypher**: The openCypher query with proper escaping
-- **parameters**: Optional list of user-provided parameters (`parameters=[]` if none)
-- **attribution**: Optional `AttackPathsQueryAttribution(text, link)` for sourced queries. The `text` includes source, reference ID, and permissions. The `link` uses a lowercase ID. Omit for non-sourced queries.
-
-### 5. Add query to provider list
-
-Add the constant to the `{PROVIDER}_QUERIES` list.
-
----
-
-## Query naming conventions
-
-### Query ID
-
-```
-{provider}-{category}-{description}
-```
-
-Examples: `aws-ec2-privesc-passrole-iam`, `aws-ec2-instances-internet-exposed`
-
-### Query constant name
-
-```
-{PROVIDER}_{CATEGORY}_{DESCRIPTION}
-```
-
-Examples: `AWS_EC2_PRIVESC_PASSROLE_IAM`, `AWS_EC2_INSTANCES_INTERNET_EXPOSED`
-
----
-
-## Query categories
-
-| Category | Description | Example |
-| -------------------- | ------------------------------ | ------------------------- |
-| Basic Resource | List resources with properties | RDS instances, S3 buckets |
-| Network Exposure | Internet-exposed resources | EC2 with public IPs |
-| Privilege Escalation | IAM privilege escalation paths | PassRole + RunInstances |
-| Data Access | Access to sensitive data | EC2 with S3 access |
+The provider catalog lives in `api/src/backend/tasks/jobs/attack_paths/provider_config.py` (`AWS_NORMALIZED_LISTS`). Beyond policy statements it includes KMS algorithms, ECS container-definition lists (`entry_point`, `command`, `links`, `dns_servers`, ...), CloudFront aliases, Inspector finding URL and vulnerability lists, RDS event-subscription categories, and others. To query a list property that is not in the catalog, add an entry there first so the sync layer materialises it.
---
@@ -315,53 +296,42 @@ Examples: `AWS_EC2_PRIVESC_PASSROLE_IAM`, `AWS_EC2_INSTANCES_INTERNET_EXPOSED`
### Match account and principal
```cypher
-MATCH path_principal = (aws:AWSAccount {id: $provider_uid})--(principal:AWSPrincipal)--(policy:AWSPolicy)--(stmt:AWSPolicyStatement)
+MATCH path_principal = (aws:AWSAccount {id: $provider_uid})--(principal:AWSPrincipal)-[:POLICY]->(policy:AWSPolicy)-[:STATEMENT]->(stmt:AWSPolicyStatement {effect: 'Allow'})
```
-### Check IAM action permissions
+The `(aws)--(principal)` hop stays anonymous; the `POLICY` and `STATEMENT` hops are typed.
+
+### Roles trusting a service
```cypher
-WHERE stmt.effect = 'Allow'
- AND any(action IN stmt.action WHERE
- toLower(action) = 'iam:passrole'
- OR toLower(action) = 'iam:*'
- OR action = '*'
- )
+MATCH path_target = (aws)--(target_role:AWSRole)-[:TRUSTS_AWS_PRINCIPAL]-(:AWSPrincipal {arn: 'ec2.amazonaws.com'})
```
-### Find roles trusting a service
+### Roles a principal can assume
```cypher
-MATCH path_target = (aws)--(target_role:AWSRole)-[:TRUSTS_AWS_PRINCIPAL]->(:AWSPrincipal {arn: 'ec2.amazonaws.com'})
+MATCH path_target = (aws)--(target_role:AWSRole)-[:STS_ASSUMEROLE_ALLOW]-(principal)
```
-### Find roles the principal can assume
+### JSON-encoded properties
-Note the arrow direction - `STS_ASSUMEROLE_ALLOW` points from the role to the principal:
+Object-typed Cartography properties (most notably `condition` on `AWSPolicyStatement` and `S3PolicyStatement`) are stored as JSON-encoded strings, e.g. `'{"StringEquals":{"aws:SourceAccount":"123456789012"}}'`. There is no JSON parser at query time, so use `CONTAINS` for substring checks:
```cypher
-MATCH path_target = (aws)--(target_role:AWSRole)<-[:STS_ASSUMEROLE_ALLOW]-(principal)
+WHERE stmt.condition CONTAINS '"aws:SourceAccount"'
```
-### Check resource scope
-
-```cypher
-WHERE any(resource IN stmt.resource WHERE
- resource = '*'
- OR target_role.arn CONTAINS resource
- OR resource CONTAINS target_role.name
-)
-```
+For structured inspection, fetch the rows and parse in Python. Cypher cannot navigate JSON object keys.
### Internet node via path connectivity
-The Internet node is reached through `CAN_ACCESS` relationships to already-scoped resources. No standalone lookup needed:
-
```cypher
OPTIONAL MATCH (internet:Internet)-[can_access:CAN_ACCESS]->(resource)
```
-### Multi-label OR (match multiple resource types)
+`resource` must already be bound by the account-anchored pattern above.
+
+### Multi-label OR (multiple resource types)
```cypher
MATCH path = (aws:AWSAccount {id: $provider_uid})-[r]-(x)-[q]-(y)
@@ -373,7 +343,7 @@ WHERE (x:EC2PrivateIp AND x.public_ip = $ip)
### Include Prowler findings
-Deduplicate nodes before the ProwlerFinding lookup to avoid redundant OPTIONAL MATCH calls on nodes that appear in multiple paths:
+Deduplicate nodes before the typed finding probe to avoid one `OPTIONAL MATCH` per path-occurrence of the same node:
```cypher
WITH collect(path_principal) + collect(path_target) AS paths
@@ -382,12 +352,12 @@ UNWIND nodes(p) AS n
WITH paths, collect(DISTINCT n) AS unique_nodes
UNWIND unique_nodes AS n
-OPTIONAL MATCH (n)-[pfr]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
+OPTIONAL MATCH (n)-[pfr:HAS_FINDING]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr
```
-For network exposure queries, aggregate the internet node and relationship alongside paths:
+For network-exposure queries, aggregate the Internet node and its edge alongside paths:
```cypher
WITH collect(path) AS paths, head(collect(internet)) AS internet, collect(can_access) AS can_access
@@ -396,7 +366,7 @@ UNWIND nodes(p) AS n
WITH paths, internet, can_access, collect(DISTINCT n) AS unique_nodes
UNWIND unique_nodes AS n
-OPTIONAL MATCH (n)-[pfr]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
+OPTIONAL MATCH (n)-[pfr:HAS_FINDING]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})
RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr,
internet, can_access
@@ -406,22 +376,22 @@ RETURN paths, collect(DISTINCT pf) as dpf, collect(DISTINCT pfr) as dpfr,
## Prowler-specific labels and relationships
-These are added by the sync task, not part of the Cartography schema. For all other node labels, properties, and relationships, **always consult the Cartography schema** (see step 2 below).
+Added by the sync task, not part of the Cartography schema. For everything else, consult the pinned Cartography schema (see "Creation steps").
-| Label/Relationship | Description |
-| ---------------------- | -------------------------------------------------- |
-| `ProwlerFinding` | Finding node (`status`, `severity`, `check_id`) |
-| `Internet` | Internet sentinel node |
-| `CAN_ACCESS` | Internet-to-resource exposure (relationship) |
-| `HAS_FINDING` | Resource-to-finding link (relationship) |
-| `TRUSTS_AWS_PRINCIPAL` | Role trust relationship |
-| `STS_ASSUMEROLE_ALLOW` | Can assume role (direction: role -> principal) |
+| Label / Relationship | Description |
+| ---------------------- | ----------------------------------------------------------- |
+| `ProwlerFinding` | Finding node (`status`, `severity`, `check_id`) |
+| `Internet` | Internet sentinel node |
+| `CAN_ACCESS` | `(Internet)-[:CAN_ACCESS]->(resource)` exposure edge |
+| `HAS_FINDING` | `(resource)-[:HAS_FINDING]->(:ProwlerFinding)` finding link |
+| `TRUSTS_AWS_PRINCIPAL` | Role trust relationship |
+| `STS_ASSUMEROLE_ALLOW` | Can assume role |
---
## Parameters
-For queries requiring user input:
+For queries that take user input:
```python
parameters=[
@@ -438,50 +408,84 @@ parameters=[
---
-## Best practices
+## openCypher compatibility
-1. **Chain all MATCHes from the root account node**: Every `MATCH` clause must connect to the `aws` variable (or another variable already bound to the account's subgraph). An unanchored `MATCH` would return nodes from all providers.
+Queries must run on both Neo4j and Amazon Neptune. Avoid these constructs:
- ```cypher
- // WRONG: matches ALL AWSRoles across all providers
- MATCH (role:AWSRole) WHERE role.name = 'admin'
+| Feature | Use instead |
+| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| APOC procedures (`apoc.*`) | Real nodes and relationships in the graph |
+| Neptune extensions | Standard openCypher |
+| `reduce()` | `UNWIND` + `collect()` |
+| `FOREACH` | `WITH` + `UNWIND` + `SET` |
+| Regex `=~` | `toLower()` + exact match, or `STARTS WITH` / `CONTAINS` |
+| `CALL () { UNION }` | Multi-label `OR` in `WHERE` (see pattern above) |
+| Carried value plus aggregate expression | Project the aggregate first: `WITH principal_paths, collect(...) AS target_paths`, then combine lists in the next `WITH` |
+| `any(x IN list ...)` | `size([x IN list WHERE pred]) > 0` |
+| `all(x IN list ...)` | `size([x IN list WHERE pred]) = size(list)` |
+| `none(x IN list ...)` | `size([x IN list WHERE pred]) = 0` |
+| `EXISTS { MATCH (pattern) WHERE pred }` | Standalone `MATCH (pattern)` + `WHERE pred`; precede the downstream `collect(path...)` with `WITH DISTINCT <path-vars>` to dedupe the joins |
- // CORRECT: scoped to the specific account's subgraph
- MATCH (aws)--(role:AWSRole) WHERE role.name = 'admin'
- ```
-
- **Exception**: A second-permission MATCH like `MATCH (principal)--(policy2:AWSPolicy)--(stmt2:AWSPolicyStatement)` is safe because `principal` is already bound to the account's subgraph by the first MATCH. It does not need to chain from `aws` again.
-
-2. **Include Prowler findings**: Always add `OPTIONAL MATCH (n)-[pfr]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})` with `collect(DISTINCT pf)`.
-
-3. **Comment the query purpose**: Add inline comments explaining each MATCH clause.
-
-4. **Never use internal labels in queries**: `_ProviderResource`, `_AWSResource`, `_Tenant_*`, `_Provider_*` are for system isolation. They should never appear in predefined or custom query text.
-
-6. **Internet node uses path connectivity**: Reach it via `OPTIONAL MATCH (internet:Internet)-[can_access:CAN_ACCESS]->(resource)` where `resource` is already scoped by the account anchor. No standalone lookup.
+For list-typed properties in the catalog (action, resource, and so on), traverse the `HAS_*` edges to the child item nodes via the multi-`MATCH` shape shown in "List-typed properties as child nodes". The parent node does not carry the list as a single field, so `split(...)` and comma-string predicates do not apply.
---
-## openCypher compatibility
+## Best practices
-Queries must be written in **openCypher Version 9** for compatibility with both Neo4j and Amazon Neptune.
+1. **Chain every MATCH from the account anchor.** An unanchored `MATCH (role:AWSRole)` returns roles from every provider in the graph; `MATCH (aws)--(role:AWSRole)` is scoped. A second-permission MATCH like `MATCH (principal)--(policy2:AWSPolicy)--(stmt2:AWSPolicyStatement)` is safe because `principal` is already bound to the account's subgraph.
+2. **Type the finding probe.** Always `OPTIONAL MATCH (n)-[pfr:HAS_FINDING]-(pf:{PROWLER_FINDING_LABEL} {{status: 'FAIL'}})`. The type lets Neptune apply an inline edge filter; an untyped probe scans every incident edge of high-degree nodes.
+3. **Comment each MATCH.** One inline `// ...` line per clause explaining its role.
+4. **Never use internal labels.** `_ProviderResource`, `_AWSResource`, `_Tenant_*`, `_Provider_*` are system isolation labels and must not appear in query text (predefined or custom).
+5. **Reach the Internet node through path connectivity** via `(internet:Internet)-[:CAN_ACCESS]->(resource)`, never as a standalone match.
+6. **Preserve the `RETURN` contract.** `paths, dpf, dpfr` for the standard shape; add `internet, can_access` for network-exposure queries. The serializer and visualiser depend on these names.
-### Avoid these (not in openCypher spec)
+---
-| Feature | Use instead |
-| -------------------------- | ------------------------------------------------------ |
-| APOC procedures (`apoc.*`) | Real nodes and relationships in the graph |
-| Neptune extensions | Standard openCypher |
-| `reduce()` function | `UNWIND` + `collect()` |
-| `FOREACH` clause | `WITH` + `UNWIND` + `SET` |
-| Regex operator (`=~`) | `toLower()` + exact match, or `CONTAINS`/`STARTS WITH`. One legacy query uses `=~` - do not add new usages |
-| `CALL () { UNION }` | Multi-label OR in WHERE (see patterns section) |
+## Naming conventions
+
+- **ID**: kebab-case `{provider}-{category}-{description}`, e.g. `aws-ec2-privesc-passrole-iam`.
+- **Constant**: SHOUTING*SNAKE_CASE `{PROVIDER}*{CATEGORY}\_{DESCRIPTION}`, e.g. `AWS_EC2_PRIVESC_PASSROLE_IAM`.
+
+---
+
+## Creation steps
+
+1. **Read the queries module first** to match the existing style:
+
+ ```text
+ api/src/backend/api/attack_paths/queries/
+ ├── __init__.py
+ ├── types.py # dataclass definitions
+ ├── registry.py
+ └── {provider}.py
+ ```
+
+2. **Fetch the Cartography schema for the pinned version.** Do not guess labels, properties, or relationships. Read the dependency pin:
+
+ ```bash
+ grep cartography api/pyproject.toml
+ ```
+
+ Then fetch the schema for that exact tag:
+
+ ```text
+ # Git pin (prowler-cloud/cartography@<TAG>):
+ https://raw.githubusercontent.com/prowler-cloud/cartography/refs/tags/<TAG>/docs/root/modules/{provider}/schema.md
+
+ # PyPI pin (cartography==<TAG>):
+ https://raw.githubusercontent.com/cartography-cncf/cartography/refs/tags/<TAG>/docs/root/modules/{provider}/schema.md
+ ```
+
+3. **Build the query** using the canonical predefined template plus the appropriate sub-pattern (privilege escalation or network exposure). For list-typed properties (action/resource/etc.), traverse the exploded child nodes via `[:HAS_ACTION]->(:AWSPolicyStatementActionItem)` etc. (see "List-typed properties as child nodes" and the `AWS_NORMALIZED_LISTS` catalog).
+
+4. **Register** the constant in the `{PROVIDER}_QUERIES` list at the bottom of the provider file.
---
## Reference
-- **pathfinding.cloud**: https://github.com/DataDog/pathfinding.cloud (use `curl | jq`, not WebFetch)
-- **Cartography schema**: `https://raw.githubusercontent.com/{org}/cartography/refs/tags/{version}/docs/root/modules/{provider}/schema.md`
-- **Neptune openCypher compliance**: https://docs.aws.amazon.com/neptune/latest/userguide/feature-opencypher-compliance.html
-- **openCypher spec**: https://github.com/opencypher/openCypher
+- **pathfinding.cloud**: https://github.com/DataDog/pathfinding.cloud (use `curl | jq`; the aggregated `paths.json` is too large for WebFetch).
+- **Cartography schema** (per pinned tag): `https://raw.githubusercontent.com/{org}/cartography/refs/tags/{tag}/docs/root/modules/{provider}/schema.md`.
+- **Neptune openCypher compliance**: https://docs.aws.amazon.com/neptune/latest/userguide/feature-opencypher-compliance.html.
+- **openCypher spec**: https://github.com/opencypher/openCypher.
+- **Sync converter** (`tasks/jobs/attack_paths/sync.py`): list-typed node properties listed in `tasks/jobs/attack_paths/provider_config.py::AWS_NORMALIZED_LISTS` are materialised as child item nodes + `HAS_*` edges. Properties that are not in the catalog are serialised to a comma-delimited string and emit a one-time warning. Dict-typed properties become JSON strings. Same shape on both sinks.
diff --git a/skills/prowler-changelog/SKILL.md b/skills/prowler-changelog/SKILL.md
index 67e853b0fd..fef70fa9bc 100644
--- a/skills/prowler-changelog/SKILL.md
+++ b/skills/prowler-changelog/SKILL.md
@@ -6,7 +6,7 @@ description: >
license: Apache-2.0
metadata:
author: prowler-cloud
- version: "1.0"
+ version: "2.0"
scope: [root, ui, api, sdk, mcp_server]
auto_invoke:
- "Add changelog entry for a PR or feature"
@@ -16,70 +16,80 @@ metadata:
allowed-tools: Read, Edit, Write, Glob, Grep, Bash
---
-## Changelog Locations
+## How changelog entries work: fragments
-| Component | File | Version Prefix | Current Version |
-|-----------|------|----------------|-----------------|
-| UI | `ui/CHANGELOG.md` | None | 1.x.x |
-| API | `api/CHANGELOG.md` | None | 1.x.x |
-| MCP Server | `mcp_server/CHANGELOG.md` | None | 0.x.x |
-| SDK | `prowler/CHANGELOG.md` | None | 5.x.x |
+A PR never edits unreleased `CHANGELOG.md` content directly; use fragments instead. Released-block typo/correction fixes are the only direct-edit exception and are described below. For regular entries, add one small **fragment file** per entry under the component's `changelog.d/` directory. Fragments are compiled into the component's `CHANGELOG.md` at release time (deleting the consumed fragments), so concurrent PRs never conflict on the changelog.
-## Format Rules (keepachangelog.com)
+| Component | Fragments directory | Compiled file |
+|-----------|---------------------|---------------|
+| UI | `ui/changelog.d/` | `ui/CHANGELOG.md` |
+| API | `api/changelog.d/` | `api/CHANGELOG.md` |
+| MCP Server | `mcp_server/changelog.d/` | `mcp_server/CHANGELOG.md` |
+| SDK | `prowler/changelog.d/` | `prowler/CHANGELOG.md` |
-### Section Order (ALWAYS this order)
+"What's unreleased" = "what's in `changelog.d/`". The compiled `CHANGELOG.md` files contain only released versions.
-```markdown
-## [X.Y.Z] (Prowler vA.B.C) OR (Prowler UNRELEASED)
+## Fragment filename
-### Added
-### Changed
-### Deprecated
-### Removed
-### Fixed
-### Security
+```text
+<slug>.<type>.md
```
-### Emoji Prefixes (REQUIRED for ALL components)
+- `<slug>` is free-form (`[A-Za-z0-9][A-Za-z0-9._-]*`), chosen by the author, ideally descriptive of the change (e.g. `securityhub-delegated-admin`). The PR number is also a valid slug (e.g. `11259`) when it is already known; it is never required.
+- `<type>` maps 1:1 to the keepachangelog sections:
-| Section | Emoji | Usage |
-|---------|-------|-------|
-| Added | `### 🚀 Added` | New features, checks, endpoints |
-| Changed | `### 🔄 Changed` | Modifications to existing functionality |
-| Deprecated | `### ⚠️ Deprecated` | Features marked for removal |
-| Removed | `### ❌ Removed` | Deleted features |
-| Fixed | `### 🐞 Fixed` | Bug fixes |
-| Security | `### 🔐 Security` | Security patches, CVE fixes |
+| `<type>` | Section | Usage |
+|----------|---------|-------|
+| `added` | `### 🚀 Added` | New features, checks, endpoints |
+| `changed` | `### 🔄 Changed` | Modifications to existing functionality |
+| `deprecated` | `### ⚠️ Deprecated` | Features marked for removal |
+| `removed` | `### ❌ Removed` | Deleted features |
+| `fixed` | `### 🐞 Fixed` | Bug fixes |
+| `security` | `### 🔐 Security` | Security patches, CVE fixes |
-### Entry Format
+- A PR adds as many fragment files as entries it needs, freely mixing types: one file per entry. E.g. a PR touching Added, Changed and Fixed ships `kms-rotation-check.added.md` + `kms-metadata-cache.changed.md` + `kms-disabled-keys.fixed.md`, and all compile with the same PR link into their own sections.
+- Several entries of the SAME type: a different slug per entry (`kms-rotation-check.added.md`, `kms-rotation-docs.added.md`).
+- At least one fragment per touched component, same as the old one-entry-per-changelog rule.
-```markdown
-### Added
+## Fragment content
-- Existing entry one [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- Existing entry two [(#YYYY)](https://github.com/prowler-cloud/prowler/pull/YYYY)
-- NEW ENTRY GOES HERE at the BOTTOM [(#ZZZZ)](https://github.com/prowler-cloud/prowler/pull/ZZZZ)
+The file contains ONLY the entry text, exactly as it should appear in the changelog, on a single line ending with a trailing newline:
-### Changed
-
-- Existing change [(#AAAA)](https://github.com/prowler-cloud/prowler/pull/AAAA)
-- NEW CHANGE ENTRY at BOTTOM [(#BBBB)](https://github.com/prowler-cloud/prowler/pull/BBBB)
+```bash
+echo '`securityhub_delegated_admin_enabled_all_regions` check for AWS provider, verifying that Security Hub has a delegated administrator, is active in all opted-in regions, and has organization auto-enable on' > prowler/changelog.d/securityhub-delegated-admin.added.md
```
-**Rules:**
-- **ADD NEW ENTRIES AT THE BOTTOM of each section** (before next section header or `---`)
-- **Blank line after section header** before first entry
-- **Blank line between sections**
+**Rules (same prose conventions as always):**
+
+- **NEVER write the PR link in the text.** It is attached automatically at compile time (the compile workflow resolves the PR that added the fragment from git history). Writing `[(#NNNN)](...)` in a fragment produces a duplicated link.
+- No period at the end
+- Do NOT start with redundant verbs (the section header already provides the action)
- Be specific: what changed, not why (that's in the PR)
- Keep entries readable: use spaces around inline code and product names, and wrap endpoints, commands, errors, task names, and file paths in backticks
- Avoid long run-on sentences; split complex changes into one concise result plus one concise context clause
-- One entry per PR (can link multiple PRs for related changes)
-- No period at the end
-- Do NOT start with redundant verbs (section header already provides the action)
-- **CRITICAL: Preserve section order** — when adding a new section to the UNRELEASED block, insert it in the correct position relative to existing sections (Added → Changed → Deprecated → Removed → Fixed → Security). Never append a new section at the top or bottom without checking order
-- **CRITICAL: ALWAYS link to the PR, NEVER to the issue.** Every entry MUST use `https://github.com/prowler-cloud/prowler/pull/N`. Linking to `/issues/N` is FORBIDDEN, even when the PR fixes an issue. The issue↔PR relationship belongs in the PR body (`Fixes #N`), not in the changelog. If a fix has no PR yet, do not add the entry until the PR exists.
-### Semantic Versioning Rules
+### Good fragments
+
+```text
+# ui/changelog.d/provider-search-bar.added.md
+Search bar when adding a provider
+
+# api/changelog.d/scan-dispatch-race.fixed.md
+`POST /api/v1/scans` no longer intermittently fails with `Scan matching query does not exist`; scan dispatch now publishes the `scan-perform` Celery task after the transaction commits
+
+# ui/changelog.d/node-24-bump.security.md
+Node.js from 20.x to 24.13.0 LTS, patching 8 CVEs
+```
+
+### Bad fragments
+
+```text
+Fixed bug. # Too vague, has period, redundant verb
+Add search bar # Redundant verb (the section already says "Added")
+Search bar [(#9634)](https://github.com/prowler-cloud/prowler/pull/9634) # NEVER include the PR link; it is added at compile time
+```
+
+## Semantic Versioning Rules
Prowler follows [semver.org](https://semver.org/):
@@ -89,69 +99,26 @@ Prowler follows [semver.org](https://semver.org/):
| New features (backwards compatible) | MINOR (x.**Y**.0) | 1.16.2 → 1.17.0 |
| Breaking changes, removals | MAJOR (**X**.0.0) | 1.17.0 → 2.0.0 |
-**CRITICAL:** `### ❌ Removed` entries MUST only appear in MAJOR version releases. Removing features is a breaking change.
-
-### Released Versions Are Immutable
-
-**NEVER modify already released versions.** Once a version is released (has a Prowler version tag like `v5.16.0`), its changelog section is frozen.
-
-**Common issue:** A PR is created during release cycle X, includes a changelog entry, but merges after release. The entry is now in the wrong section.
-
-```markdown
-## [1.16.0] (Prowler v5.16.0) ← RELEASED, DO NOT MODIFY
-
-### Added
-- Feature from merged PR [(#9999)] ← WRONG! PR merged after release
-
-## [1.17.0] (Prowler UNRELEASED) ← Move entry HERE
-```
-
-**Fix:** Move the entry from the released version to the UNRELEASED section.
-
-### Version Header Format
-
-```markdown
-## [1.17.0] (Prowler UNRELEASED) # For unreleased changes
-## [1.16.0] (Prowler v5.16.0) # For released versions
-
---- # Horizontal rule between versions
-```
-
-## Mandatory Changelog Preflight
-
-Before editing any `CHANGELOG.md`, always inspect the active release boundary:
-
-1. Read the UNRELEASED block plus the latest three released version blocks:
- ```bash
- awk '/^## \[/{n++} n<=4 {print}' ui/CHANGELOG.md
- ```
-2. Identify the **only writable block**: the block whose header contains `(Prowler UNRELEASED)`.
-3. Treat every block whose header contains `(Prowler vX.Y.Z)` as immutable. Do not add, move, reword, reorder, or deduplicate entries there.
-4. If your PR's entry appears in any of the latest three released blocks, remove it from the released block and add it to the correct section in the UNRELEASED block.
-5. If there is no UNRELEASED block at the top, stop and ask before editing.
-
-**Do not trust the current topmost matching section name.** A released block can contain the same section heading (`### 🚀 Added`, `### 🔄 Changed`, etc.). Always anchor edits to the `Prowler UNRELEASED` version block first.
+**CRITICAL:** `removed` fragments MUST only ship in MAJOR version releases. Removing features is a breaking change.
## Mandatory Human Confirmation Gate
-Before creating or editing any changelog file (`CHANGELOG.md`), the agent MUST stop and get explicit user confirmation. This applies even when the changelog gate is failing, the required edit seems obvious, or the user asked to "fix the changelog".
+Before creating or editing any changelog fragment or `CHANGELOG.md` file, the agent MUST stop and get explicit user confirmation. This applies even when the changelog gate is failing, the required file seems obvious, or the user asked to "fix the changelog".
-Present the proposed changelog action before writing:
+Present the proposed action before writing:
-1. Target file path.
-2. Target version block and section.
-3. Exact entry to add, move, remove, or rewrite.
-4. Reason the changelog is needed.
+1. Target fragment path (component, slug, type) or CHANGELOG.md edit.
+2. Exact entry text.
+3. Reason the changelog entry is needed.
-Only proceed after an explicit approval such as "confirm", "approved", "sí", or equivalent. If the user rejects or does not answer, do not edit or create the changelog. Offer alternatives such as adding `no-changelog` when appropriate.
+Only proceed after an explicit approval such as "confirm", "approved", "sí", or equivalent. If the user rejects or does not answer, do not create or edit anything. Offer alternatives such as adding `no-changelog` when appropriate.
## Adding a Changelog Entry
### Step 1: Determine Affected Component(s)
```bash
-# Check which files changed
-git diff main...HEAD --name-only
+git diff master...HEAD --name-only | grep -E '^(ui|api|mcp_server|prowler)/' | cut -d/ -f1 | sort -u
```
| Path Pattern | Component |
@@ -160,114 +127,63 @@ git diff main...HEAD --name-only
| `api/**` | API |
| `mcp_server/**` | MCP Server |
| `prowler/**` | SDK |
-| Multiple | Update ALL affected changelogs |
+| Root `uv.lock` / `pyproject.toml` | SDK (the gate requires a `prowler/changelog.d/` fragment) |
+| Multiple | One fragment per affected component |
-### Step 2: Determine Change Type
+### Step 2: Create the fragment(s)
-| Change | Section |
-|--------|---------|
-| New feature, check, endpoint | 🚀 Added |
-| Behavior change, refactor | 🔄 Changed |
-| Bug fix | 🐞 Fixed |
-| CVE patch, security improvement | 🔐 Security |
-| Feature removal | ❌ Removed |
-| Deprecation notice | ⚠️ Deprecated |
-
-### Step 3: Add Entry at BOTTOM of Appropriate Section
-
-**CRITICAL:** Add new entries at the BOTTOM of each section, NOT at the top.
-
-**CRITICAL:** The link MUST point to the PR (`/pull/N`). Linking to `/issues/N` is FORBIDDEN. If the PR closes an issue, that mapping goes in the PR body via `Fixes #N` — never in the changelog entry.
-
-```markdown
-## [1.17.0] (Prowler UNRELEASED)
-
-### 🐞 Fixed
-
-- Existing fix one [(#9997)](https://github.com/prowler-cloud/prowler/pull/9997)
-- Existing fix two [(#9998)](https://github.com/prowler-cloud/prowler/pull/9998)
-- Button alignment in dashboard header [(#9999)](https://github.com/prowler-cloud/prowler/pull/9999) ← NEW ENTRY AT BOTTOM
-
-### 🔐 Security
+```bash
+echo 'Entry text describing the change' > <component>/changelog.d/<slug>.<type>.md
```
-This maintains chronological order within each section (oldest at top, newest at bottom).
+### Step 3: Check pending fragments
-## Examples
-
-### Good Entries
-
-```markdown
-### 🚀 Added
-- Search bar when adding a provider [(#9634)](https://github.com/prowler-cloud/prowler/pull/9634)
-
-### 🐞 Fixed
-- OCI update credentials form failing silently due to missing provider UID [(#9746)](https://github.com/prowler-cloud/prowler/pull/9746)
-
-### 🔐 Security
-- Node.js from 20.x to 24.13.0 LTS, patching 8 CVEs [(#9797)](https://github.com/prowler-cloud/prowler/pull/9797)
-```
-
-### Readable Technical Entries
-
-```markdown
-# GOOD - Technical but readable
-### 🐞 Fixed
-- `POST /api/v1/scans` no longer intermittently fails with `Scan matching query does not exist`; scan dispatch now publishes the `scan-perform` Celery task after the transaction commits [(#11122)](https://github.com/prowler-cloud/prowler/pull/11122)
-- `entra_users_mfa_capable` no longer flags disabled guest users; Microsoft Graph is now the source of truth for `account_enabled` because EXO `Get-User` omits guest users [(#11002)](https://github.com/prowler-cloud/prowler/pull/11002)
-```
-
-### Bad Entries
-
-```markdown
-# BAD - Wrong section order (Fixed before Added)
-### 🐞 Fixed
-- Some bug fix [(#123)](...)
-
-### 🚀 Added
-- Some new feature [(#456)](...)
-
-- Fixed bug. # Too vague, has period
-- Added new feature for users # Missing PR link, redundant verb
-- Add search bar [(#123)] # Redundant verb (section already says "Added")
-- This PR adds a cool new thing (#123) # Wrong link format, conversational
-- Some bug fix [(#123)](https://github.com/prowler-cloud/prowler/issues/123) # FORBIDDEN: must link to /pull/N, never /issues/N
-- POST /api/v1/scanswas intermittently failing withScan matching query does not existin thescan-performworker (#11122) # Missing spaces/backticks, unreadable
-- entra_users_mfa_capable no longer flags disabled guest users by requesting accountEnabled and userType from Microsoft Graph via $select and using Graph as the source of truth for account_enabled (EXO Get-User does not return guest users) (#11002) # Run-on sentence, identifiers not formatted
+```bash
+ls prowler/changelog.d/ api/changelog.d/ ui/changelog.d/ mcp_server/changelog.d/
```
## PR Changelog Gate
-The `pr-check-changelog.yml` workflow enforces changelog entries:
+The `pr-check-changelog.yml` workflow enforces fragments:
-1. **REQUIRED**: PRs touching `ui/`, `api/`, `mcp_server/`, or `prowler/` MUST update the corresponding changelog
-2. **SKIP**: Add `no-changelog` label to bypass (use sparingly for docs-only, CI-only changes)
+1. **REQUIRED**: PRs touching `ui/`, `api/`, `mcp_server/`, or `prowler/` MUST add (or fix) a fragment under the corresponding `changelog.d/`
+2. **VALIDATED**: added fragment filenames must match `<slug>.<type>.md` with a valid type
+3. **LINTED**: fragment content must NOT contain a hand-written PR link (`[(#N)](...)`); the gate fails if one is found because the link is attached automatically at compile time
+4. **SKIP**: Add `no-changelog` label to bypass (use sparingly for docs-only, CI-only changes)
-## Commands
+## Release flow (compile)
-```bash
-# Check which changelogs need updates based on changed files
-git diff main...HEAD --name-only | grep -E '^(ui|api|mcp_server|prowler)/' | cut -d/ -f1 | sort -u
+- At release time, the `compile-changelogs` workflow (manual dispatch: `prowler_version` + `target_branch`; per-component versions are auto-derived by mirroring the Prowler version — SDK mirrors it directly, UI is `1.<minor>.<patch>`, API is `1.<minor + 1>.<patch>`, and only the MCP Server derives from its pending fragment types — with optional explicit overrides or `skip`) resolves each fragment's PR from git history, runs the compiler per component, and opens a `chore(changelog): vX.Y.Z` PR (labeled `no-changelog` and `skip-sync`) that inserts the stamped `## [X.Y.Z] (Prowler vX.Y.Z)` block into each `CHANGELOG.md` and deletes the consumed fragments. A human reviews and squash-merges it. `prepare-release.yml` then extracts the stamped sections exactly as before.
+- **Minor release (X.Y.0):** compile on `master` and merge the compile PR BEFORE cutting the `v5.X` branch.
+- **Patch release (X.Y.Z):** fixes are backported to `v5.X` with their fragment files (conflict-free); compile on `v5.X` and merge its PR there. The same workflow run automatically opens a second forward-sync PR against master (labeled `no-changelog` and `skip-sync`) that inserts the same stamped block under master's marker and deletes the consumed fragments, so the next minor cannot re-release them; merge it right after. Fragments that only existed on `v5.X` are skipped with a notice. No manual git is involved.
+- Entries within a section are ordered by PR number ascending (approximately chronological). Do not fight this ordering.
-# View current UNRELEASED section
-head -50 ui/CHANGELOG.md
-head -50 api/CHANGELOG.md
-head -50 mcp_server/CHANGELOG.md
-head -50 prowler/CHANGELOG.md
-```
+## Fixing an already-released entry
-## Migration Note
+Released version blocks in `CHANGELOG.md` are otherwise immutable, but typo/correction fixes to already-released entries are the one case where a PR edits `CHANGELOG.md` directly: make the edit and add the `no-changelog` label.
-**API, MCP Server, and SDK changelogs currently lack emojis.** When editing these files, add emoji prefixes to section headers as you update them:
+If a PR's entry shipped in the wrong released block (e.g. the PR merged after its release was cut), move the entry back to a fragment: delete it from the released block and recreate it as `<component>/changelog.d/<PR>.<type>.md` (label the PR `no-changelog` since it edits `CHANGELOG.md`).
+
+## Compiled CHANGELOG.md format (for reference)
+
+The compiler renders, per release, into each `CHANGELOG.md` right under the `<!-- changelog: release notes start -->` marker (never remove that marker):
```markdown
-# Before (legacy)
-### Added
+## [X.Y.Z] (Prowler vA.B.C)
-# After (standardized)
### 🚀 Added
+
+- Entry text [(#NNNN)](https://github.com/prowler-cloud/prowler/pull/NNNN)
+
+### 🐞 Fixed
+
+- Fix entry [(#NNNN)](https://github.com/prowler-cloud/prowler/pull/NNNN)
+
+---
```
+Section order is always: Added → Changed → Deprecated → Removed → Fixed → Security. `X.Y.Z` is the COMPONENT version; `A.B.C` is the Prowler release version. Every entry ends with its PR link; linking to `/issues/N` is forbidden (the issue↔PR mapping belongs in the PR body via `Fixes #N`).
+
## Resources
- **Templates**: See [assets/](assets/) for entry templates
diff --git a/skills/prowler-changelog/assets/entry-templates.md b/skills/prowler-changelog/assets/entry-templates.md
index cc74efbb63..b2367b0219 100644
--- a/skills/prowler-changelog/assets/entry-templates.md
+++ b/skills/prowler-changelog/assets/entry-templates.md
@@ -1,101 +1,73 @@
-# Changelog Entry Templates
+# Changelog Fragment Templates
-## Entry Placement Rule
+## Fragment basics
-**CRITICAL:** Always add new entries at the **BOTTOM** of each section (before the next section header or `---`).
+One fragment file per entry, under the component's `changelog.d/`:
-This maintains chronological order: oldest entries at top, newest at bottom.
-
-## Section Headers
-
-```markdown
-### 🚀 Added
-### 🔄 Changed
-### ⚠️ Deprecated
-### ❌ Removed
-### 🐞 Fixed
-### 🔐 Security
+```text
+<component>/changelog.d/<slug>.<type>.md
```
-## Entry Patterns
+- `<slug>`: free-form, descriptive (`[A-Za-z0-9][A-Za-z0-9._-]*`)
+- `<type>`: `added`, `changed`, `deprecated`, `removed`, `fixed`, `security`
+- Content: a single line with the entry text. **No PR link** (attached automatically at compile time) and no trailing period.
-> **Note:** Section headers already provide the verb. Entries describe WHAT, not the action.
->
-> **Link target rule:** Every entry MUST link to the PR (`https://github.com/prowler-cloud/prowler/pull/N`). Linking to `/issues/N` is FORBIDDEN — even when the PR fixes an issue. The issue↔PR mapping belongs in the PR body (`Fixes #N`), not here.
+> **Note:** The section header already provides the verb. Entries describe WHAT, not the action.
-### Feature Addition (🚀 Added)
-```markdown
-- Search bar when adding a provider [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- `{check_id}` check for {provider} provider [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- `/api/v1/{endpoint}` endpoint to {description} [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
+## Content Patterns by Type
+
+### Feature Addition (`.added.md`)
+
+```text
+Search bar when adding a provider
+`{check_id}` check for {provider} provider
+`/api/v1/{endpoint}` endpoint to {description}
```
-### Behavior Change (🔄 Changed)
-```markdown
-- Lighthouse AI MCP tool filtering from blacklist to whitelist approach [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- {package} from {old} to {new} [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
+### Behavior Change (`.changed.md`)
+
+```text
+Lighthouse AI MCP tool filtering from blacklist to whitelist approach
+{package} from {old} to {new}
```
-### Bug Fix (🐞 Fixed)
-```markdown
-- OCI update credentials form failing silently due to missing provider UID [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- {What was broken} in {component} [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
+### Bug Fix (`.fixed.md`)
+
+```text
+OCI update credentials form failing silently due to missing provider UID
+{What was broken} in {component}
```
-> When a PR fixes a reported issue, the link still goes to the PR (`/pull/N`), never the issue (`/issues/N`). Reference the issue from the PR body with `Fixes #N`.
+### Security Patch (`.security.md`)
-### Security Patch (🔐 Security)
-```markdown
-- Node.js from 20.x to 24.13.0 LTS, patching 8 CVEs [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-- {package} to version {version} (CVE-XXXX-XXXXX) [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
+```text
+Node.js from 20.x to 24.13.0 LTS, patching 8 CVEs
+{package} to version {version} (CVE-XXXX-XXXXX)
```
-### Removal (❌ Removed)
-```markdown
-- Deprecated {feature} from {location} [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
+### Removal (`.removed.md`)
+
+```text
+Deprecated {feature} from {location}
```
-## Version Header Templates
+## Full Examples
-### Unreleased
-```markdown
-## [X.Y.Z] (Prowler UNRELEASED)
+```bash
+echo 'Search bar when adding a provider' > ui/changelog.d/provider-search-bar.added.md
+
+echo '`kms_key_rotation_max_90_days` check for GCP provider, verifying KMS customer-managed keys are rotated every 90 days or less' > prowler/changelog.d/kms-rotation-90d.added.md
+
+echo 'OCI update credentials form failing silently due to missing provider UID' > ui/changelog.d/oci-credentials-form.fixed.md
```
-### Released
-```markdown
-## [X.Y.Z] (Prowler vA.B.C)
+Several entries in one PR → one file per entry, freely mixing types (different slugs when the type repeats):
----
+```text
+prowler/changelog.d/kms-rotation-check.added.md
+prowler/changelog.d/kms-rotation-docs.added.md
+prowler/changelog.d/kms-metadata-cache.changed.md
+prowler/changelog.d/kms-disabled-keys.fixed.md
```
-## Full Entry Example
-
-```markdown
-## [1.17.0] (Prowler UNRELEASED)
-
-### 🚀 Added
-
-- Search bar when adding a provider [(#9634)](https://github.com/prowler-cloud/prowler/pull/9634)
-- New findings table UI with new design system components [(#9699)](https://github.com/prowler-cloud/prowler/pull/9699)
-- YOUR NEW ENTRY GOES HERE AT BOTTOM [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-
-### 🔄 Changed
-
-- Lighthouse AI MCP tool filtering from blacklist to whitelist approach [(#9802)](https://github.com/prowler-cloud/prowler/pull/9802)
-- YOUR NEW CHANGE GOES HERE AT BOTTOM [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-
-### 🐞 Fixed
-
-- OCI update credentials form failing silently due to missing provider UID [(#9746)](https://github.com/prowler-cloud/prowler/pull/9746)
-- YOUR NEW FIX GOES HERE AT BOTTOM [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-
-### 🔐 Security
-
-- Node.js from 20.x to 24.13.0 LTS, patching 8 CVEs [(#9797)](https://github.com/prowler-cloud/prowler/pull/9797)
-- YOUR NEW SECURITY FIX GOES HERE AT BOTTOM [(#XXXX)](https://github.com/prowler-cloud/prowler/pull/XXXX)
-
----
-```
-
-> **Remember:** Each new entry is added at the BOTTOM of its section to maintain chronological order.
+> **Remember:** never include the PR link in the fragment text; the compile step resolves and appends it automatically.
diff --git a/skills/prowler-ci/SKILL.md b/skills/prowler-ci/SKILL.md
index b673178c8c..e956cd4ee0 100644
--- a/skills/prowler-ci/SKILL.md
+++ b/skills/prowler-ci/SKILL.md
@@ -31,7 +31,8 @@ Use this skill whenever you are:
- PR template: `.github/pull_request_template.md`
- PR title validation: `.github/workflows/conventional-commit.yml`
-- Changelog gate: `.github/workflows/pr-check-changelog.yml`
+- Changelog gate: `.github/workflows/pr-check-changelog.yml` (requires a fragment under `<component>/changelog.d/`)
+- Changelog compile (release time): `.github/workflows/compile-changelogs.yml`
- Conflict markers check: `.github/workflows/pr-conflict-checker.yml`
- Secret scanning: `.github/workflows/find-secrets.yml`
- Auto labels: `.github/workflows/labeler.yml` and `.github/labeler.yml`
@@ -42,7 +43,7 @@ Use this skill whenever you are:
1. Identify which workflow/job is failing (name + file under `.github/workflows/`).
2. Check path filters: is the workflow supposed to run for your changed files?
3. If it's a title check: verify PR title matches Conventional Commits.
-4. If it's changelog: verify the right `CHANGELOG.md` is updated OR apply `no-changelog` label.
+4. If it's changelog: verify a valid fragment exists under the right `<component>/changelog.d/` OR apply `no-changelog` label.
5. If it's conflict checker: remove `<<<<<<<`, `=======`, `>>>>>>>` markers.
6. If it's secrets (TruffleHog): see section below.
diff --git a/skills/prowler-commit/SKILL.md b/skills/prowler-commit/SKILL.md
index 0f67cbe882..30dbbc49cd 100644
--- a/skills/prowler-commit/SKILL.md
+++ b/skills/prowler-commit/SKILL.md
@@ -28,7 +28,7 @@ metadata:
## Commit Format
-```
+```text
type(scope): concise description
- Key change 1
@@ -68,7 +68,7 @@ type(scope): concise description
### Title Line
-```
+```text
# GOOD - Concise and clear
feat(api): add provider connection retry logic
fix(ui): resolve dashboard loading state
@@ -83,7 +83,7 @@ fix(ui): fix the bug in dashboard component on line 45
### Body (Bullet Points)
-```
+```text
# GOOD - High-level changes
- Add retry mechanism for failed connections
- Document task composition patterns
@@ -132,7 +132,7 @@ fix(ui): fix the bug in dashboard component on line 45
## Decision Tree
-```
+```text
Single file changed?
├─ Yes → May omit body, title only
└─ No → Include body with key changes
diff --git a/skills/prowler-compliance-review/SKILL.md b/skills/prowler-compliance-review/SKILL.md
index 6ac720dce8..6136467538 100644
--- a/skills/prowler-compliance-review/SKILL.md
+++ b/skills/prowler-compliance-review/SKILL.md
@@ -27,7 +27,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
| JSON Valid | `python3 -m json.tool file.json` | No syntax errors |
| All Checks Exist | Run validation script | 0 missing checks |
| No Duplicate IDs | Run validation script | 0 duplicate requirement IDs |
-| CHANGELOG Entry | Manual review | Present under correct version |
+| Changelog fragment | Manual review | Fragment present under `prowler/changelog.d/` |
| Dashboard File | Compare with existing | Follows established pattern |
| Framework Metadata | Manual review | All required fields populated |
@@ -53,7 +53,7 @@ diff dashboard/compliance/{new_framework}.py \
## Decision Tree
-```
+```text
JSON Valid?
├── No → FAIL: Fix JSON syntax errors
└── Yes ↓
@@ -63,8 +63,8 @@ JSON Valid?
Duplicate Requirement IDs?
├── Yes → FAIL: Fix duplicate IDs
└── No ↓
- CHANGELOG Entry Present?
- ├── No → REQUEST CHANGES: Add CHANGELOG entry
+ Changelog Fragment Present?
+ ├── No → REQUEST CHANGES: Add changelog fragment
└── Yes ↓
Dashboard File Follows Pattern?
├── No → REQUEST CHANGES: Fix dashboard pattern
@@ -124,7 +124,7 @@ Compliance frameworks are JSON files in: `prowler/compliance/{provider}/{framewo
| Empty Checks for Automated | AssessmentStatus is Automated but Checks is empty | Add checks or change to Manual |
| Wrong file location | Framework not in `prowler/compliance/{provider}/` | Move to correct directory |
| Missing dashboard file | No corresponding `dashboard/compliance/{framework}.py` | Create dashboard file following pattern |
-| CHANGELOG missing | Not under correct version section | Add entry to prowler/CHANGELOG.md |
+| Changelog fragment missing | No fragment file in the PR diff | Add a fragment under prowler/changelog.d/ |
---
diff --git a/skills/prowler-compliance-review/references/review-checklist.md b/skills/prowler-compliance-review/references/review-checklist.md
index d8673d8c03..34e5e26c67 100644
--- a/skills/prowler-compliance-review/references/review-checklist.md
+++ b/skills/prowler-compliance-review/references/review-checklist.md
@@ -16,7 +16,7 @@
|-----------|----------|
| Compliance JSON | `prowler/compliance/{provider}/{framework}.json` |
| Dashboard | `dashboard/compliance/{framework}_{provider}.py` |
-| CHANGELOG | `prowler/CHANGELOG.md` |
+| Changelog fragment | `prowler/changelog.d/` |
| Checks | `prowler/providers/{provider}/services/{service}/{check}/` |
## Validation Script
@@ -40,7 +40,7 @@ When completing a compliance framework review, use this summary format:
| JSON Valid | PASS/FAIL |
| All Checks Exist | PASS/FAIL (N missing) |
| No Duplicate IDs | PASS/FAIL |
-| CHANGELOG Entry | PASS/FAIL |
+| Changelog fragment | PASS/FAIL |
| Dashboard File | PASS/FAIL |
### Statistics
diff --git a/skills/prowler-compliance/SKILL.md b/skills/prowler-compliance/SKILL.md
index 51c68eb05f..747cb6ab64 100644
--- a/skills/prowler-compliance/SKILL.md
+++ b/skills/prowler-compliance/SKILL.md
@@ -2,23 +2,29 @@
name: prowler-compliance
description: >
Creates, syncs, audits and manages Prowler compliance frameworks end-to-end.
- Covers the four-layer architecture (SDK models → JSON catalogs → output
- formatters → API/UI), upstream sync workflows, cloud-auditor check-mapping
- reviews, output formatter creation, and framework-specific attribute models.
- Trigger: When working with compliance frameworks (CIS, NIST, PCI-DSS, SOC2,
- GDPR, ISO27001, ENS, MITRE ATT&CK, CCC, C5, CSA CCM, KISA ISMS-P,
- Prowler ThreatScore, FedRAMP, HIPAA), syncing with upstream catalogs,
- auditing check-to-requirement mappings, adding output formatters, or fixing
- compliance JSON bugs (duplicate IDs, empty Version, wrong Section, stale
- check refs).
+ Covers the two supported JSON schemas (universal multi-provider and legacy
+ per-provider), the SDK model tree (legacy attribute classes, universal
+ ComplianceFramework, ConfigRequirements guardrails), output formatters
+ (legacy per-framework + universal data-driven), API/UI consumption, upstream
+ sync workflows, and cloud-auditor check-mapping reviews.
+ Trigger: When working with compliance frameworks (CIS, CIS Controls, NIST,
+ PCI-DSS, SOC2, GDPR, ISO27001, ENS, MITRE ATT&CK, CCC, C5, CSA CCM, DORA,
+ KISA ISMS-P, ASD Essential Eight, DISA STIG, CISA SCuBA, SecNumCloud,
+ FedRAMP, HIPAA, NIS2, Prowler ThreatScore), creating a universal
+ multi-provider framework, adding ConfigRequirements guardrails, syncing with
+ upstream catalogs, auditing check-to-requirement mappings, adding output
+ formatters, or fixing compliance JSON bugs (duplicate IDs, empty Version,
+ wrong Section, stale check refs).
license: Apache-2.0
metadata:
author: prowler-cloud
- version: "1.2"
+ version: "2.0"
scope: [root, sdk]
auto_invoke:
- "Creating/updating compliance frameworks"
+ - "Creating a universal (multi-provider) compliance framework"
- "Mapping checks to compliance controls"
+ - "Adding ConfigRequirements guardrails to compliance requirements"
- "Syncing compliance framework with upstream catalog"
- "Auditing check-to-requirement mappings as a cloud auditor"
- "Adding a compliance output formatter (per-provider class + table dispatcher)"
@@ -29,523 +35,673 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## When to Use
Use this skill when:
-- Creating a new compliance framework for any provider
+
+- Creating a new compliance framework for any provider — **decide universal vs legacy first** (see below)
- **Syncing an existing framework with an upstream source of truth** (CIS, FINOS CCC, CSA CCM, NIST, ENS, etc.)
-- Adding requirements to existing frameworks
+- Adding requirements to existing frameworks, or extending a universal framework to a new provider
- Mapping checks to compliance controls
-- **Auditing existing check mappings as a cloud auditor** (user asks "are these mappings correct?", "which checks apply to this requirement?", "review the mappings")
-- **Adding a new output formatter** (new framework needs a table dispatcher + per-provider classes + CSV models)
+- **Adding `ConfigRequirements` guardrails** so configurable checks can't silently satisfy a requirement with a loosened config
+- **Auditing existing check mappings as a cloud auditor** ("are these mappings correct?", "which checks apply?", "review the mappings")
+- **Adding a new legacy output formatter** (table dispatcher + per-provider classes + CSV models)
- **Fixing JSON bugs**: duplicate IDs, empty Version, wrong Section, stale check refs, inconsistent FamilyName, padded tangential check mappings
-- **Registering a framework in the CLI table dispatcher or API export map**
- Investigating why a finding/check isn't showing under the expected compliance framework in the UI
- Understanding compliance framework structures and attributes
-## Four-Layer Architecture (Mental Model)
+The authoritative contributor doc is `docs/developer-guide/security-compliance-framework.mdx` —
+keep this skill and that doc consistent when either changes. For **reviewing**
+a compliance PR, use the sister skill
+[prowler-compliance-review](../prowler-compliance-review/SKILL.md) instead.
-Prowler compliance is a **four-layer system** hanging off one Pydantic model tree. Bugs usually happen where one layer doesn't match another, so know all four before touching anything.
+## Universal vs Legacy: The First Decision
+
+Prowler supports **two JSON schemas**. Choosing wrong means unnecessary Python
+code, so decide this before anything else. At load time both converge: legacy
+files are adapted into the universal `ComplianceFramework` model
+(`adapt_legacy_to_universal()`), so the difference is about **authoring cost
+and capabilities**, not about what the rest of Prowler sees.
+
+### Side-by-side comparison
+
+| | Universal (recommended for new frameworks) | Legacy provider-specific |
+|---|---|---|
+| File location | `prowler/compliance/<framework>.json` (top level) | `prowler/compliance/<provider>/<framework>_<version>_<provider>.json` |
+| Providers | Any number, one file (`checks` dict keyed by provider) | Exactly one provider per file (one file per provider to multi-cover) |
+| Key style | lowercase (`framework`, `requirements`, `checks`) | Capitalized (`Framework`, `Requirements`, `Checks`) |
+| Attribute schema | Declared **in the JSON itself** via `attributes_metadata`, validated at load | Pydantic class per framework family in `compliance_models.py` (code change for new shapes) |
+| Attributes per requirement | One flat dict (`attributes: {...}`) | List of objects (`Attributes: [{...}]`) — only `Attributes[0]` is used downstream |
+| Table/CSV/OCSF output | Data-driven from `outputs.table_config` — **zero Python changes** | Formatter package + registrations in `compliance.py`, `__main__.py`, `export.py` |
+| Guardrails field | `config_requirements` (+ mandatory `Provider` per constraint) | `ConfigRequirements` (`Provider` omitted) |
+| Loader behavior on error | Lenient: logs + skips file (`load_compliance_framework_universal`) | Fail-fast: `sys.exit(1)` (`load_compliance_framework`) |
+| Loaded by | Only `get_bulk_compliance_frameworks_universal()` | Both loaders (`Compliance.get_bulk()` + universal, via adapter) |
+| Shipped examples | `cis_controls_8.1.json`, `csa_ccm_4.0.json`, `dora_2022_2554.json` | Everything else (~105 files across 11 providers) |
+
+### When to use which
+
+**Use universal when** (any of these):
+
+- The framework is **new to Prowler** — no existing attribute class, no
+ existing formatter. This is the default: zero Python changes needed.
+- The framework spans (or will span) **more than one provider** — DORA, CSA
+ CCM, CIS Controls. One file covers all providers; extending to a new
+ provider is a one-line `checks` edit.
+- The attribute shape is **unique to this framework** — declare it in
+ `attributes_metadata` instead of adding a Pydantic class to the Union.
+
+**Use legacy only when extending an existing legacy family**:
+
+- A new **version** of a shipped legacy framework (CIS 8.0 for AWS → new
+ `cis_8.0_aws.json`, same `CIS_Requirement_Attribute`, same `cis/` formatter).
+- An existing legacy framework for a **new provider** (ENS for m365 → new
+ `ens_rd2022_m365.json` + `ens_m365.py` transformer).
+- Consistency with the family matters more than the universal benefits — a
+ lone `cis_8.0_aws` in universal format while 20+ CIS files stay legacy
+ would fragment the family.
+
+**Never**: start a brand-new single-provider framework as legacy "because it's
+only AWS today". Universal handles single-provider fine (the `checks` dict
+just has one key) and you skip 3 output files + 3 registrations.
+
+### The same requirement in both schemas
+
+Universal (`prowler/compliance/my_framework_1.0.json`):
+
+```json
+{
+ "framework": "My-Framework",
+ "name": "My Framework 1.0",
+ "version": "1.0",
+ "description": "...",
+ "attributes_metadata": [
+ {"key": "Section", "type": "str", "required": true},
+ {"key": "Service", "type": "str"}
+ ],
+ "outputs": {"table_config": {"group_by": "Section"}},
+ "requirements": [
+ {
+ "id": "MF-1.1",
+ "name": "Root MFA",
+ "description": "Root account must have MFA enabled.",
+ "attributes": {"Section": "IAM", "Service": "iam"},
+ "checks": {
+ "aws": ["iam_root_mfa_enabled"],
+ "azure": []
+ }
+ }
+ ]
+}
+```
+
+Legacy (`prowler/compliance/aws/my_framework_1.0_aws.json` — plus a second
+file per extra provider, plus formatter + registrations):
+
+```json
+{
+ "Framework": "My-Framework",
+ "Name": "My Framework 1.0 for AWS",
+ "Version": "1.0",
+ "Provider": "AWS",
+ "Description": "...",
+ "Requirements": [
+ {
+ "Id": "MF-1.1",
+ "Name": "Root MFA",
+ "Description": "Root account must have MFA enabled.",
+ "Attributes": [
+ {"ItemId": "MF-1.1", "Section": "IAM", "Service": "iam"}
+ ],
+ "Checks": ["iam_root_mfa_enabled"]
+ }
+ ]
+}
+```
+
+Same control, but the universal file already covers Azure, validates its own
+attribute schema, and renders table/CSV/OCSF with no code. Field-by-field
+references for each schema follow below.
+
+## Architecture (Mental Model)
+
+Prowler compliance is a four-layer system. Bugs usually happen where one layer
+doesn't match another, so know all four before touching anything.
### Layer 1: SDK / Core Models — `prowler/lib/check/`
-- **`compliance_models.py`** — Pydantic **v1** model tree (`from pydantic.v1 import`). One `*_Requirement_Attribute` class per framework type + `Generic_Compliance_Requirement_Attribute` as fallback.
-- `Compliance_Requirement.Attributes: list[Union[...]]` — **`Generic_Compliance_Requirement_Attribute` MUST be LAST** in the Union or every framework-specific attribute falls through to Generic (Pydantic v1 tries union members in order).
-- **`compliance.py`** — runtime linker. `get_check_compliance()` builds the key as `f"{Framework}-{Version}"` **only if `Version` is non-empty**. An empty Version makes the key just `"{Framework}"` — this breaks downstream filters and tests that expect the versioned key.
-- `Compliance.get_bulk(provider)` walks `prowler/compliance/{provider}/` and parses every `.json` file. No central index — just directory scan.
+All in **Pydantic v1** (`from pydantic.v1 import ...`). Three model groups live
+in `compliance_models.py`:
-### Layer 2: JSON Frameworks — `prowler/compliance/{provider}/`
+**Legacy tree** — `Compliance` → `Compliance_Requirement` / `Mitre_Requirement`:
-See "Compliance Framework Location" and "Framework-Specific Attribute Structures" sections below.
+- One `*_Requirement_Attribute` class per framework family. Registered today (Union order matters):
+ `ASDEssentialEight`, `CIS`, `ENS`, `ISO27001_2013`, `AWS_Well_Architected`,
+ `KISA_ISMSP`, `Prowler_ThreatScore`, `CCC`, `C5Germany`, `CSA_CCM`, `STIG`
+ (Okta IDaaS), and `Generic_Compliance_Requirement_Attribute` as fallback.
+- **Generic MUST stay LAST** in `Compliance_Requirement.Attributes: list[Union[...]]` —
+ Pydantic v1 tries union members in order; Generic first would swallow every
+ framework-specific attribute. NIST 800-53/CSF, PCI DSS, GDPR, HIPAA, SOC2,
+ FedRAMP, SecNumCloud etc. intentionally use Generic.
+- A `root_validator` rejects empty `Framework`, `Provider` or `Name`.
+- MITRE uses the separate `Mitre_Requirement` model (`Tactics`, `SubTechniques`,
+ `Platforms`, `TechniqueURL` at requirement top level, per-provider
+ `Mitre_Requirement_Attribute_{AWS,Azure,GCP}`).
-### Layer 3: Output Formatters — `prowler/lib/outputs/compliance/{framework}/`
+**Universal tree** — `ComplianceFramework` → `UniversalComplianceRequirement`:
-**Every framework directory follows this exact convention** — do not deviate:
+- Flat `attributes: dict` per requirement, schema declared in
+ `attributes_metadata` (key, label, type, enum, required, `enum_display`,
+ `enum_order`, `output_formats`). A `root_validator` rejects missing required
+ keys, unknown keys (drift guard), enum violations, and int/float/bool type
+ mismatches. If `attributes_metadata` is omitted, **no validation runs**.
+- `checks: dict[provider, list[check_id]]` — the provider list of the framework
+ is **derived** from these keys (`get_providers()` / `supports_provider()`);
+ the top-level `provider` field is only a fallback.
+- `outputs.table_config` (group_by, split_by, scoring, labels) drives the CLI
+ table; `outputs.pdf_config` exists in the model but **is not consumed by the
+ API PDF pipeline yet** (see Layer 4).
-```
+**Guardrails** — `Compliance_Requirement_ConfigConstraint`:
+
+- Fields `Check`, `ConfigKey`, `Operator` (`lte|gte|eq|in|subset|superset`),
+ `Value`, optional `Provider` (required in universal multi-provider files).
+- A `root_validator` rejects Value/Operator type mismatches at load time.
+- Evaluation is centralized in `prowler/lib/check/compliance_config_eval.py`
+ (`evaluate_config_constraints`, `apply_config_status`, `get_effective_status`,
+ `CONFIG_NOT_VALID_PREFIX = "Configuration not valid for this requirement."`),
+ shared by CSV/OCSF/table outputs **and** the API backend. A violated
+ constraint forces the requirement to FAIL and prepends the reason to
+ `status_extended`. Constraints whose `ConfigKey` is absent from
+ `audit_config` are skipped (defaults assumed compliant).
+
+**Loaders**:
+
+- `Compliance.get_bulk(provider)` — legacy: scans only
+ `prowler/compliance/{provider}/` (+ external JSONs via the
+ `prowler.compliance` entry-point group). Does NOT see top-level universal files.
+- `get_bulk_compliance_frameworks_universal(provider)` — scans **both** the
+ top-level `prowler/compliance/` and every provider subdirectory, adapting
+ legacy files via `adapt_legacy_to_universal()` (flattens `Attributes[0]` to a
+ dict, wraps `Checks` as `{provider: [...]}`, infers `attributes_metadata`).
+ Also loads external universal frameworks via the
+ `prowler.compliance.universal` entry-point group (built-ins win collisions).
+- `get_check_compliance(finding, provider_type, bulk_checks_metadata)` lives in
+ **`prowler/lib/outputs/compliance/compliance_check.py`** (not in
+ `lib/check/compliance.py`). It builds the per-finding dict keyed
+ `f"{Framework}-{Version}"` **only when Version is non-empty** — an empty
+ Version silently produces the key `"{Framework}"` and breaks downstream
+ filters and tests.
+- `prowler/lib/check/compliance.py` now contains only
+ `update_checks_metadata_with_compliance()`.
+
+### Layer 2: JSON Catalogs — `prowler/compliance/`
+
+See "Compliance Catalog Coverage" below.
+
+### Layer 3: Output Formatters — `prowler/lib/outputs/compliance/`
+
+**Universal path** (no Python needed per framework):
+
+- `universal/universal_table.py` — `get_universal_table()`, renders the CLI
+ table from `outputs.table_config` + `attributes_metadata`.
+- `universal/universal_output.py` — `UniversalComplianceOutput`, builds the CSV
+ Pydantic model **dynamically** from `attributes_metadata`.
+- `universal/ocsf_compliance.py` — `OCSFComplianceOutput`; OCSF output is
+ **always generated** for universal frameworks regardless of `--output-formats`.
+- Orchestrated by `process_universal_compliance_frameworks()` in
+ `compliance.py`, which runs **before** any legacy dispatch and removes the
+ processed frameworks from the set.
+
+**Legacy path** — per-framework directory, usually:
+
+```text
{framework}/
├── __init__.py
-├── {framework}.py # ONLY get_{framework}_table() — NO function docstring
-├── {framework}_{provider}.py # One class per provider (e.g., CCC_AWS, CCC_Azure, CCC_GCP)
-└── models.py # One Pydantic v2 BaseModel per provider (CSV columns)
+├── {framework}.py # get_{framework}_table() summary-table function
+├── {framework}_{provider}.py # One ComplianceOutput subclass per provider
+└── models.py # One Pydantic CSV row model per provider
```
-- **`{framework}.py`** holds the **table dispatcher function** `get_{framework}_table()`. It prints the pass/fail/muted summary table. **Must NOT import `Finding` or `ComplianceOutput`** — doing so creates a circular import with `prowler/lib/outputs/compliance/compliance.py`. Only imports: `colorama`, `tabulate`, `prowler.config.config.orange_color`.
-- **`{framework}_{provider}.py`** holds a per-provider class like `CCC_AWS(ComplianceOutput)` with a `transform()` method that walks findings and emits rows. This file IS allowed to import `Finding` because it's not on the dispatcher import chain.
-- **`models.py`** holds one Pydantic v2 `BaseModel` per provider. Field names become CSV column headers (**public API** — renaming breaks downstream consumers).
-- **Never collapse per-provider files into a unified parameterized class**, even when DRY-tempting. Every framework in Prowler follows the per-provider file pattern and reviewers will reject the refactor. CSV columns differ per provider (`AccountId`/`Region` vs `SubscriptionId`/`Location` vs `ProjectId`/`Location`) — three classes is the convention.
-- **No function docstring on `get_{framework}_table()`** — no other framework has one; stay consistent.
-- Register in `prowler/lib/outputs/compliance/compliance.py` → `display_compliance_table()` with an `elif compliance_framework.startswith("{framework}_"):` branch. Import the table function at the top of the file.
+Directories today: `asd_essential_eight`, `aws_well_architected`, `c5`, `ccc`,
+`cis`, `cisa_scuba`, `ens`, `generic`, `iso27001`, `kisa_ismsp`,
+`mitre_attack`, `okta_idaas_stig`, `prowler_threatscore`, `universal`.
+Known deviations (don't "fix" them without a reason): `iso27001/` has no table
+file (falls to the generic table), `aws_well_architected/` has no per-provider
+files, `cisa_scuba/` only ships googleworkspace.
+
+- CSV writers emit `;`-delimited files with UPPERCASE headers
+ (`ComplianceOutput.batch_write_data_to_file`). Field names in `models.py`
+ are **public API** — renaming breaks downstream consumers.
+- **Circular import rule**: the table file (`{framework}.py`) must not import
+ `Finding` directly or transitively (`compliance.compliance` → table module →
+ `ComplianceOutput` → `Finding` → `get_check_compliance` → cycle). Keep table
+ files bare (`colorama`, `tabulate`, `prowler.config.config`); when a module
+ genuinely needs both, use `if TYPE_CHECKING:` or function-local imports (see
+ `universal_output.py` / `process_universal_compliance_frameworks`).
+- Legacy table functions have no docstrings; the universal ones do. Match the
+ style of the file family you're touching.
+- Dispatcher `display_compliance_table()` in `compliance.py` order:
+ universal (`table_config`) first → `cis_` → `ens_` → `mitre_attack` →
+ `kisa` → `prowler_threatscore_` → `c5_` → `ccc_` → `asd_essential_eight`
+ (substring) → `okta_idaas_stig` → else provider hook
+ (`provider.display_compliance_table()`, may raise `NotImplementedError`) →
+ `get_generic_compliance_table()`. iso27001, aws_well_architected and
+ cisa_scuba ride the fallback on purpose.
### Layer 4: API / UI
-- **API table dispatcher**: `api/src/backend/tasks/jobs/export.py` → `COMPLIANCE_CLASS_MAP` keyed by provider. Uses `startswith` predicates: `(lambda name: name.startswith("ccc_"), CCC_AWS)`. **Never use exact match** (`name == "ccc_aws"`) — it's inconsistent and breaks versioning.
-- **API lazy loader**: `api/src/backend/api/compliance.py` — `LazyComplianceTemplate` and `LazyChecksMapping` load compliance per provider on first access.
-- **UI mapper routing**: `ui/lib/compliance/compliance-mapper.ts` routes framework names → per-framework mapper.
-- **UI per-framework mapper**: `ui/lib/compliance/{framework}.tsx` flattens `Requirements` into a 3-level tree (Framework → Category → Control → Requirement) for the accordion view. Groups by `Attributes[0].FamilyName` and `Attributes[0].Section`.
-- **UI detail panel**: `ui/components/compliance/compliance-custom-details/{framework}-details.tsx`.
-- **UI types**: `ui/types/compliance.ts` — TypeScript mirrors of the attribute metadata.
+- **API lazy loaders**: `api/src/backend/api/compliance.py` —
+ `LazyComplianceTemplate` / `LazyChecksMapping` (per-provider lazy caches over
+ `get_bulk_compliance_frameworks_universal`, with Gunicorn background warm-up).
+- **API CSV export dispatch**: `COMPLIANCE_CLASS_MAP` in
+ `api/src/backend/tasks/jobs/export.py`, consumed from `tasks/tasks.py`. It is
+ a dict `provider → [(predicate, exporter_class)]` with `GenericCompliance` as
+ fallback. Predicates mix **`startswith` for multi-version families**
+ (`cis_`, `ens_`, `iso27001_`, `ccc_`, `cisa_scuba_`, ...) and **exact
+ `name == ...` for true singletons** (`mitre_attack_aws`,
+ `prowler_threatscore_*`, `asd_essential_eight_aws` — and inconsistently
+ `c5_azure`/`c5_gcp`, while aws uses `startswith("c5_")`). Rule of thumb: if
+ the framework can ever grow versions or variants, use `startswith`.
+- **API overview ingestion**: `create_compliance_requirements()` in
+ `api/src/backend/tasks/jobs/scan.py` builds per-region rows from the lazy
+ template and persists `ComplianceRequirementOverview` (COPY with bulk-create
+ fallback) plus `ComplianceOverviewSummary`.
+- **API PDF reports**: `api/src/backend/tasks/jobs/reports/` — hardcoded
+ `FRAMEWORK_REGISTRY` (own `FrameworkConfig` dataclass, NOT the SDK
+ `PDFConfig`) with one generator class per framework. Only
+ `prowler_threatscore`, `ens`, `nis2`, `csa_ccm` and `cis` have PDFs today;
+ adding one means a generator class + registry entry + wiring in `report.py`.
+- **UI mapper routing**: `ui/lib/compliance/compliance-mapper.ts` —
+ `getComplianceMappers()` keyed by the JSON's `framework` value
+ (e.g. `"CIS"`, `"CIS-Controls"`, `"DORA"`, `"Okta-IDaaS-STIG"`). Unregistered
+ frameworks **fall back to the generic mapper + `GenericCustomDetails`
+ automatically** — a dedicated mapper/detail panel is a first-class upgrade,
+ not a requirement to render.
+- **UI grouping varies per mapper**: generic/cis group by
+ `Section`/`SubSection`, iso by `Category`, ccc by `FamilyName`. All read
+ `attributes[0]` — inconsistent values within one JSON become separate tree
+ branches, so normalize before shipping.
+- **UI types**: `ui/types/compliance.ts` — one `*AttributesMetadata` interface
+ per framework, added to the `AttributesItemData` metadata union.
+- **UI icons**: `ui/components/icons/compliance/` + `IconCompliance.tsx`.
+ Registration is an ordered substring match (`COMPLIANCE_LOGOS`): put
+ framework-specific keywords **before** generic ones (`nist` before `nis2`,
+ `cisa` before `cis`; `aws` deliberately last).
### The CLI Pipeline (end-to-end)
-```
-prowler aws --compliance ccc_aws
+```text
+prowler aws --compliance cis_7.0_aws # framework key = JSON basename
↓
-Compliance.get_bulk("aws") → parses prowler/compliance/aws/*.json
+Compliance.get_bulk("aws") # legacy frameworks
+get_bulk_compliance_frameworks_universal("aws") # legacy (adapted) + universal
↓
-update_checks_metadata_with_compliance() → attaches compliance info to CheckMetadata
+update_checks_metadata_with_compliance() # attaches compliance to CheckMetadata
↓
-execute_checks() → runs checks, produces Finding objects
+execute_checks() → Finding objects
↓
-get_check_compliance(finding, "aws", bulk_checks_metadata)
- → dict "{Framework}-{Version}" → [requirement_ids]
+get_check_compliance(finding, "aws", bulk) # dict "{Framework}-{Version}" → [req_ids]
↓
-CCC_AWS(findings, compliance).transform() → per-provider class builds CSV rows
+process_universal_compliance_frameworks() # universal: CSV + OCSF, then removed from set
+per-provider elif branches in __main__.py # legacy: AWSCIS(...).batch_write_data_to_file()
↓
-batch_write_data_to_file() → writes {output_filename}_ccc_aws.csv
- ↓
-display_compliance_table() → get_ccc_table() → prints stdout summary
+display_compliance_table() # universal table first, then legacy elifs,
+ # then generic fallback
```
---
-## Compliance Framework Location
+## Compliance Catalog Coverage
-Frameworks are JSON files located in: `prowler/compliance/{provider}/{framework_name}_{provider}.json`
+Counts as of 2026-07 (109 JSON files). Regenerate before trusting them:
-**Supported Providers:**
-- `aws` - Amazon Web Services
-- `azure` - Microsoft Azure
-- `gcp` - Google Cloud Platform
-- `kubernetes` - Kubernetes
-- `github` - GitHub
-- `m365` - Microsoft 365
-- `alibabacloud` - Alibaba Cloud
-- `cloudflare` - Cloudflare
-- `oraclecloud` - Oracle Cloud
-- `oci` - Oracle Cloud Infrastructure
-- `nhn` - NHN Cloud
-- `mongodbatlas` - MongoDB Atlas
-- `iac` - Infrastructure as Code
-- `llm` - Large Language Models
+```bash
+for d in prowler/compliance/*/; do printf "%s: %s\n" "$(basename $d)" "$(ls $d*.json 2>/dev/null | wc -l)"; done
+ls prowler/compliance/*.json # universal, top-level
+```
-## Base Framework Structure
+**Universal (top-level, multi-provider)**: `cis_controls_8.1.json` (18
+providers), `csa_ccm_4.0.json` (aws/azure/gcp/alibabacloud/oraclecloud),
+`dora_2022_2554.json` (aws/azure/gcp/alibabacloud/cloudflare).
-All compliance frameworks share this base structure:
+**Legacy per-provider** (families, not exhaustive versions):
+
+| Provider | # | Framework families |
+|---|---|---|
+| aws | 45 | CIS 1.4–7.0, NIST 800-53 r4/r5, NIST 800-171 r2, NIST CSF 1.1/2.0, PCI 3.2.1/4.0, ISO 27001 2013/2022, HIPAA, GDPR, SOC2, FedRAMP low/moderate r4 + 20x KSI low, ENS RD2022, MITRE ATT&CK, C5, CCC, CISA, FFIEC, RBI, Well-Architected (security/reliability), FTR, FSBP, AWS AI Security Framework, AWS Account Security Onboarding, Audit Manager Control Tower, GxP 21 CFR 11 / EU Annex 11, KISA ISMS-P 2023 (en+ko), NIS2, ASD Essential Eight, SecNumCloud 3.2, Prowler ThreatScore |
+| azure | 19 | CIS 2.0–6.0, ISO 27001 2022, ENS RD2022, MITRE ATT&CK, PCI 4.0, HIPAA, SOC2, NIS2, RBI, C5, CCC, FedRAMP 20x KSI low, SecNumCloud 3.2, Prowler ThreatScore |
+| gcp | 17 | CIS 2.0–5.0, ISO 27001 2022, ENS RD2022, MITRE ATT&CK, PCI 4.0, HIPAA, SOC2, NIS2, RBI, C5, CCC, FedRAMP 20x KSI low, SecNumCloud 3.2, Prowler ThreatScore |
+| kubernetes | 8 | CIS 1.8–2.0.1, ISO 27001 2022, PCI 4.0, Prowler ThreatScore |
+| m365 | 5 | CIS 4.0/6.0/7.0, ISO 27001 2022, Prowler ThreatScore |
+| alibabacloud | 3 | CIS 2.0, SecNumCloud 3.2, Prowler ThreatScore |
+| oraclecloud | 3 | CIS 3.0/3.1, SecNumCloud 3.2 |
+| github | 2 | CIS 1.0/1.2.0 |
+| googleworkspace | 2 | CIS 1.3, CISA SCuBA 0.6 |
+| okta | 1 | Okta IDaaS STIG V1R2 |
+| nhn | 1 | ISO 27001 2022 |
+
+Providers with a compliance directory but no frameworks yet: cloudflare, iac,
+linode, llm, mongodbatlas, openstack, stackit. Provider keys inside universal
+`checks` dicts must match directory names under `prowler/providers/` (lowercase).
+
+---
+
+## Universal Schema Reference
+
+Full spec in `docs/developer-guide/security-compliance-framework.mdx`. Skeleton:
+
+```json
+{
+ "framework": "DORA",
+ "name": "Digital Operational Resilience Act (DORA) 2022/2554",
+ "version": "2022/2554",
+ "description": "Shown in --list-compliance and PDF reports.",
+ "icon": "dora",
+ "attributes_metadata": [
+ {"key": "Pillar", "label": "Pillar", "type": "str", "required": true,
+ "enum": ["ICT Risk Management", "..."],
+ "output_formats": {"csv": true, "ocsf": true}},
+ {"key": "Article", "type": "str", "required": true}
+ ],
+ "outputs": {
+ "table_config": {"group_by": "Pillar"},
+ "pdf_config": {"group_by_field": "Pillar", "charts": ["..."]}
+ },
+ "requirements": [
+ {
+ "id": "DORA-Art5",
+ "name": "Governance and organisation",
+ "description": "Requirement text verbatim from the source.",
+ "attributes": {"Pillar": "ICT Risk Management", "Article": "Article 5"},
+ "checks": {
+ "aws": ["iam_no_root_access_key"],
+ "azure": [],
+ "gcp": []
+ },
+ "config_requirements": [
+ {"Check": "iam_user_accesskey_unused", "Provider": "aws",
+ "ConfigKey": "max_unused_access_keys_days", "Operator": "lte", "Value": 45}
+ ]
+ }
+ ]
+}
+```
+
+### Universal fields, top level (`ComplianceFramework`)
+
+| Field | Type | Required | Notes |
+|---|---|---|---|
+| `framework` | string | Yes | Short identifier (`DORA`, `CSA-CCM`, `CIS-Controls`). This is the key the UI mapper routes on. |
+| `name` | string | Yes | Human-readable full name. |
+| `version` | string | No (never leave empty) | Framework version/edition (`8.1`, `2022/2554`). |
+| `description` | string | Yes | Shown in `--list-compliance` and PDF reports. |
+| `provider` | string | No | Fallback only — the effective provider list is derived from `checks` keys across requirements (`get_providers()`). |
+| `icon` | string | No | Short icon slug. |
+| `attributes_metadata` | array | No (strongly recommended) | Declares the schema of every `attributes` key. **If omitted, no attribute validation runs at all.** |
+| `outputs` | object | No | `table_config` (CLI table) + `pdf_config` (modeled, not yet consumed by the API). |
+| `requirements` | array | Yes | List of requirement objects (below). |
+
+### Universal fields, per requirement (`UniversalComplianceRequirement`)
+
+| Field | Type | Required | Notes |
+|---|---|---|---|
+| `id` | string | Yes | Unique within the framework. |
+| `description` | string | Yes | Requirement text verbatim from the source. |
+| `name` | string | No | Short title. |
+| `attributes` | dict | No (default `{}`) | Flat dict; every key must be declared in `attributes_metadata` (unknown keys are rejected at load when metadata exists). |
+| `checks` | dict | No (default `{}`) | `{provider: [check_ids]}`, lowercase keys matching `prowler/providers/` dirs. Empty list = manual requirement for that provider. |
+| `config_requirements` | array | No | Guardrails; each constraint **must** carry `Provider`. |
+| `tactics`, `sub_techniques`, `platforms`, `technique_url` | — | No | MITRE-style extras (auto-populated when adapting legacy MITRE files). |
+
+### `attributes_metadata` entry fields (`AttributeMetadata`)
+
+| Field | Type | Notes |
+|---|---|---|
+| `key` | string (required) | Attribute name as used in `requirement.attributes`. |
+| `label` | string | Human-readable label for CSV headers / PDF. |
+| `type` | string | `str` (default), `int`, `float`, `bool`, `list_str`, `list_dict`. Only int/float/bool are enforced at load; the rest are documentation. |
+| `enum` | list | Allowed values — enforced at load. Use it whenever the value set is closed. |
+| `required` | bool | Enforced at load: every requirement must carry the key non-null. |
+| `enum_display` / `enum_order` | dict / list | Per-enum-value visual metadata (label, abbreviation, color, icon) and ordering for PDF rendering. |
+| `chart_label` | string | Axis label when the attribute is used in charts. |
+| `output_formats` | object | `{"csv": bool, "ocsf": bool}`, both default `true` — toggles inclusion per output. |
+
+Key rules:
+
+- `--compliance` key = JSON basename without `.json` (`dora_2022_2554`).
+- Auto-discovered: no `__init__.py`, no formatter, no dispatcher registration.
+- `table_config.group_by`, `pdf_config.group_by_field` and every
+ `charts[].group_by` must reference a key declared in `attributes_metadata`.
+- Runtime type validation only covers `int`/`float`/`bool`; `str`/`list_str`/
+ `list_dict` are documentation-only.
+- Extending to a new provider = adding a key to `requirement.checks`. Nothing else.
+- **No automatic check-existence validation at load time** — a typo'd check id
+ silently produces a requirement with no findings. Always run the
+ check-existence cross-check (see Validation).
+- In universal files, always set `Provider` on every config constraint so a
+ guardrail authored for an AWS check never affects Azure/GCP scans of the
+ same requirement.
+
+## Legacy Schema Reference
+
+Base legacy file structure:
```json
{
"Framework": "FRAMEWORK_NAME",
"Name": "Full Framework Name with Version",
"Version": "X.X",
- "Provider": "PROVIDER",
+ "Provider": "AWS",
"Description": "Framework description...",
"Requirements": [
{
"Id": "requirement_id",
- "Description": "Requirement description",
"Name": "Optional requirement name",
- "Attributes": [...],
- "Checks": ["check_name_1", "check_name_2"]
+ "Description": "Requirement description",
+ "Attributes": [ ... ],
+ "Checks": ["check_name_1"],
+ "ConfigRequirements": [ ... ]
}
]
}
```
-## Framework-Specific Attribute Structures
+### Legacy fields, top level (`Compliance`)
-Each framework type has its own attribute model. Below are the exact structures used by Prowler:
+| Field | Type | Required | Notes |
+|---|---|---|---|
+| `Framework` | string | Yes (non-empty, validated) | Canonical identifier (`CIS`, `ENS`, `NIST-800-53-Revision-5`). |
+| `Name` | string | Yes (non-empty, validated) | Human-readable name with version. |
+| `Version` | string | Optional in the model — **never leave it empty in practice** | Empty Version silently degrades the `get_check_compliance()` key to `"{Framework}"` (gotcha #4). Must match the version substring in the filename. |
+| `Provider` | string | Yes (non-empty, validated) | Upper-cased single provider (`AWS`, `AZURE`, `GCP`, `M365`, ...). One file = one provider. |
+| `Description` | string | Yes | Framework scope and purpose. |
+| `Requirements` | array | Yes | Requirement objects (below), or `Mitre_Requirement` objects for MITRE files. |
-### CIS (Center for Internet Security)
+### Legacy fields, per requirement (`Compliance_Requirement`)
-**Framework ID format:** `cis_{version}_{provider}` (e.g., `cis_5.0_aws`)
+| Field | Type | Required | Notes |
+|---|---|---|---|
+| `Id` | string | Yes | Unique within the framework; follow the source numbering exactly (`1.1`, `A.5.1`, `CCC.Core.CN01.AR01`). |
+| `Description` | string | Yes | Verbatim from the source catalog. |
+| `Name` | string | No | Optional short title (NIST-style catalogs use it). |
+| `Attributes` | array of objects | Yes | Parsed against the Union of attribute classes below; only `Attributes[0]` survives the universal adaptation and drives UI grouping. |
+| `Checks` | array of strings | Yes | Check ids automating the requirement; `[]` = manual. |
+| `ConfigRequirements` | array | No | Guardrails; `Provider` is omitted (the file is single-provider). |
+
+MITRE files use `Mitre_Requirement` instead, which adds `Tactics`,
+`SubTechniques`, `Platforms`, `TechniqueURL` at the requirement top level.
+
+### Attribute shapes per framework family
+
+Unlike universal (schema in-file), a legacy requirement's `Attributes` must
+match one of the Pydantic classes registered in
+`Compliance_Requirement.Attributes` — a shape matching no class **silently
+falls through to Generic**, dropping its specific fields. The most common
+shapes (full field sets in `compliance_models.py`):
+
+### CIS — `cis_{version}_{provider}`
```json
{
- "Id": "1.1",
- "Description": "Maintain current contact details",
- "Checks": ["account_maintain_current_contact_details"],
- "Attributes": [
- {
- "Section": "1 Identity and Access Management",
- "SubSection": "Optional subsection",
- "Profile": "Level 1",
- "AssessmentStatus": "Automated",
- "Description": "Detailed attribute description",
- "RationaleStatement": "Why this control matters",
- "ImpactStatement": "Impact of implementing this control",
- "RemediationProcedure": "Steps to fix the issue",
- "AuditProcedure": "Steps to verify compliance",
- "AdditionalInformation": "Extra notes",
- "DefaultValue": "Default configuration value",
- "References": "https://docs.example.com/reference"
- }
- ]
+ "Section": "1 Identity and Access Management",
+ "SubSection": "Optional subsection",
+ "Profile": "Level 1",
+ "AssessmentStatus": "Automated",
+ "Description": "...", "RationaleStatement": "...", "ImpactStatement": "...",
+ "RemediationProcedure": "...", "AuditProcedure": "...",
+ "AdditionalInformation": "...", "DefaultValue": "...", "References": "https://..."
}
```
-**Profile values:** `Level 1`, `Level 2`, `E3 Level 1`, `E3 Level 2`, `E5 Level 1`, `E5 Level 2`
-**AssessmentStatus values:** `Automated`, `Manual`
+`Profile`: `Level 1|Level 2|E3 Level 1|E3 Level 2|E5 Level 1|E5 Level 2`.
+`AssessmentStatus`: `Automated|Manual`.
----
-
-### ISO 27001
-
-**Framework ID format:** `iso27001_{year}_{provider}` (e.g., `iso27001_2022_aws`)
+### ENS — `ens_rd2022_{provider}`
```json
{
- "Id": "A.5.1",
- "Description": "Policies for information security should be defined...",
- "Name": "Policies for information security",
- "Checks": ["securityhub_enabled"],
- "Attributes": [
- {
- "Category": "A.5 Organizational controls",
- "Objetive_ID": "A.5.1",
- "Objetive_Name": "Policies for information security",
- "Check_Summary": "Summary of what is being checked"
- }
- ]
+ "IdGrupoControl": "op.acc.1", "Marco": "operacional",
+ "Categoria": "control de acceso", "DescripcionControl": "...",
+ "Nivel": "alto", "Tipo": "requisito",
+ "Dimensiones": ["trazabilidad", "autenticidad"],
+ "ModoEjecucion": "automatico", "Dependencias": []
}
```
-**Note:** `Objetive_ID` and `Objetive_Name` use this exact spelling (not "Objective").
+`Nivel`: `opcional|bajo|medio|alto`. `Tipo`: `refuerzo|requisito|recomendacion|medida`.
+`Dimensiones`: `confidencialidad|integridad|trazabilidad|autenticidad|disponibilidad`.
----
-
-### ENS (Esquema Nacional de Seguridad - Spain)
-
-**Framework ID format:** `ens_rd2022_{provider}` (e.g., `ens_rd2022_aws`)
+### ISO 27001 — `iso27001_{year}_{provider}`
```json
{
- "Id": "op.acc.1.aws.iam.2",
- "Description": "Proveedor de identidad centralizado",
- "Checks": ["iam_check_saml_providers_sts"],
- "Attributes": [
- {
- "IdGrupoControl": "op.acc.1",
- "Marco": "operacional",
- "Categoria": "control de acceso",
- "DescripcionControl": "Detailed control description in Spanish",
- "Nivel": "alto",
- "Tipo": "requisito",
- "Dimensiones": ["trazabilidad", "autenticidad"],
- "ModoEjecucion": "automatico",
- "Dependencias": []
- }
- ]
+ "Category": "A.5 Organizational controls",
+ "Objetive_ID": "A.5.1", "Objetive_Name": "Policies for information security",
+ "Check_Summary": "Summary of what is being checked"
}
```
-**Nivel values:** `opcional`, `bajo`, `medio`, `alto`
-**Tipo values:** `refuerzo`, `requisito`, `recomendacion`, `medida`
-**Dimensiones values:** `confidencialidad`, `integridad`, `trazabilidad`, `autenticidad`, `disponibilidad`
+Note: `Objetive_ID` / `Objetive_Name` use this exact (mis)spelling.
----
-
-### MITRE ATT&CK
-
-**Framework ID format:** `mitre_attack_{provider}` (e.g., `mitre_attack_aws`)
-
-MITRE uses a different requirement structure:
+### MITRE ATT&CK — `mitre_attack_{provider}` (separate requirement model)
```json
{
- "Name": "Exploit Public-Facing Application",
- "Id": "T1190",
- "Tactics": ["Initial Access"],
- "SubTechniques": [],
- "Platforms": ["Containers", "IaaS", "Linux", "Network", "Windows", "macOS"],
- "Description": "Adversaries may attempt to exploit a weakness...",
+ "Name": "Exploit Public-Facing Application", "Id": "T1190",
+ "Tactics": ["Initial Access"], "SubTechniques": [],
+ "Platforms": ["IaaS"], "Description": "...",
"TechniqueURL": "https://attack.mitre.org/techniques/T1190/",
- "Checks": ["guardduty_is_enabled", "inspector2_is_enabled"],
+ "Checks": ["guardduty_is_enabled"],
"Attributes": [
- {
- "AWSService": "Amazon GuardDuty",
- "Category": "Detect",
- "Value": "Minimal",
- "Comment": "Explanation of how this service helps..."
- }
+ {"AWSService": "Amazon GuardDuty", "Category": "Detect",
+ "Value": "Minimal", "Comment": "..."}
]
}
```
-**For Azure:** Use `AzureService` instead of `AWSService`
-**For GCP:** Use `GCPService` instead of `AWSService`
-**Category values:** `Detect`, `Protect`, `Respond`
-**Value values:** `Minimal`, `Partial`, `Significant`
+`AzureService`/`GCPService` for the other providers. `Category`:
+`Detect|Protect|Respond`. `Value`: `Minimal|Partial|Significant`.
----
-
-### NIST 800-53
-
-**Framework ID format:** `nist_800_53_revision_{version}_{provider}` (e.g., `nist_800_53_revision_5_aws`)
+### CCC — `ccc_{provider}`
```json
{
- "Id": "ac_2_1",
- "Name": "AC-2(1) Automated System Account Management",
- "Description": "Support the management of system accounts...",
- "Checks": ["iam_password_policy_minimum_length_14"],
- "Attributes": [
- {
- "ItemId": "ac_2_1",
- "Section": "Access Control (AC)",
- "SubSection": "Account Management (AC-2)",
- "SubGroup": "AC-2(3) Disable Accounts",
- "Service": "iam"
- }
- ]
+ "FamilyName": "Data", "FamilyDescription": "...",
+ "Section": "CCC.Core.CN01 Encrypt Data for Transmission", "SubSection": "",
+ "SubSectionObjective": "...",
+ "Applicability": ["tlp-green", "tlp-amber", "tlp-red"],
+ "Recommendation": "...",
+ "SectionThreatMappings": [{"ReferenceId": "CCC", "Identifiers": ["CCC.Core.TH02"]}],
+ "SectionGuidelineMappings": [{"ReferenceId": "NIST-CSF", "Identifiers": ["PR.DS-02"]}]
}
```
----
+`Applicability` holds TLP tags (`tlp-clear|tlp-green|tlp-amber|tlp-red`).
-### Generic Compliance (Fallback)
-
-For frameworks without specific attribute models:
+### ASD Essential Eight — `asd_essential_eight_aws`
```json
{
- "Id": "requirement_id",
- "Description": "Requirement description",
- "Name": "Optional name",
- "Checks": ["check_name"],
- "Attributes": [
- {
- "ItemId": "item_id",
- "Section": "Section name",
- "SubSection": "Subsection name",
- "SubGroup": "Subgroup name",
- "Service": "service_name",
- "Type": "type"
- }
- ]
+ "Section": "Patch applications", "MaturityLevel": "ML1",
+ "AssessmentStatus": "Automated", "CloudApplicability": "partial",
+ "MitigatedThreats": ["..."], "Description": "...",
+ "RationaleStatement": "...", "ImpactStatement": "...",
+ "RemediationProcedure": "...", "AuditProcedure": "...",
+ "AdditionalInformation": "...", "References": "..."
}
```
----
+`MaturityLevel`: `ML1|ML2|ML3`. `CloudApplicability`: `full|partial|limited|non-applicable`.
-### AWS Well-Architected Framework
-
-**Framework ID format:** `aws_well_architected_framework_{pillar}_pillar_aws`
+### DISA STIG — `okta_idaas_stig_v1r2_okta`
```json
{
- "Id": "SEC01-BP01",
- "Description": "Establish common guardrails...",
- "Name": "Establish common guardrails",
- "Checks": ["account_part_of_organizations"],
- "Attributes": [
- {
- "Name": "Establish common guardrails",
- "WellArchitectedQuestionId": "securely-operate",
- "WellArchitectedPracticeId": "sec_securely_operate_multi_accounts",
- "Section": "Security",
- "SubSection": "Security foundations",
- "LevelOfRisk": "High",
- "AssessmentMethod": "Automated",
- "Description": "Detailed description",
- "ImplementationGuidanceUrl": "https://docs.aws.amazon.com/..."
- }
- ]
+ "Section": "...", "Severity": "high", "RuleID": "...", "StigID": "...",
+ "CCI": ["CCI-000015"], "CheckText": "...", "FixText": "..."
}
```
----
+`Severity`: `high|medium|low` (maps to CAT I/II/III).
-### KISA ISMS-P (Korea)
+### Other registered shapes
-**Framework ID format:** `kisa_isms_p_{year}_{provider}` (e.g., `kisa_isms_p_2023_aws`)
+- **AWS Well-Architected** (`aws_well_architected_framework_{pillar}_pillar_aws`):
+ `Name`, `WellArchitectedQuestionId`, `WellArchitectedPracticeId`, `Section`,
+ `SubSection`, `LevelOfRisk`, `AssessmentMethod`, `Description`,
+ `ImplementationGuidanceUrl`.
+- **KISA ISMS-P** (`kisa_isms_p_2023_{provider}`): `Domain`, `Subdomain`,
+ `Section`, `AuditChecklist`, `RelatedRegulations`, `AuditEvidence`,
+ `NonComplianceCases`.
+- **C5** (`c5_{provider}`): `Section`, `SubSection`, `Type`, `AboutCriteria`,
+ `ComplementaryCriteria`.
+- **CSA CCM** (legacy shape; the shipped CSA CCM 4.0 is universal): `Section`,
+ `CCMLite`, `IaaS`, `PaaS`, `SaaS`, `ScopeApplicability`.
+- **Prowler ThreatScore** (`prowler_threatscore_{provider}`): `Title`,
+ `Section`, `SubSection`, `AttributeDescription`, `AdditionalInformation`,
+ `LevelOfRisk` (1–5), `Weight` (1/8/10/100/1000). Pillars: 1 IAM, 2 Attack
+ Surface, 3 Logging and Monitoring, 4 Encryption. Available for aws,
+ azure, gcp, kubernetes, m365, alibabacloud.
+- **Generic (fallback)**: `ItemId`, `Section`, `SubSection`, `SubGroup`,
+ `Service`, `Type`, `Comment` — all optional. Used by NIST, PCI, GDPR,
+ HIPAA, SOC2, FedRAMP, CISA, FFIEC, RBI, NIS2, GxP, SecNumCloud, etc.
+
+## Config Guardrails (`ConfigRequirements`)
+
+Requirements backed by [configurable checks](https://docs.prowler.com/developer-guide/configurable-checks)
+can be silently "satisfied" by a loosened `audit_config` (e.g. CIS demands
+45-day unused credentials but the scan ran with `max_unused_access_keys_days: 120`).
+Guardrails force such requirements to FAIL:
```json
-{
- "Id": "1.1.1",
- "Description": "Requirement description",
- "Name": "Requirement name",
- "Checks": ["check_name"],
- "Attributes": [
- {
- "Domain": "1. Management System",
- "Subdomain": "1.1 Management System Establishment",
- "Section": "1.1.1 Section Name",
- "AuditChecklist": ["Checklist item 1", "Checklist item 2"],
- "RelatedRegulations": ["Regulation 1"],
- "AuditEvidence": ["Evidence type 1"],
- "NonComplianceCases": ["Non-compliance example"]
- }
- ]
-}
+"ConfigRequirements": [
+ {"Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days", "Operator": "lte", "Value": 45}
+]
```
----
-
-### C5 (Germany Cloud Computing Compliance Criteria Catalogue)
-
-**Framework ID format:** `c5_{provider}` (e.g., `c5_aws`)
-
-```json
-{
- "Id": "BCM-01",
- "Description": "Requirement description",
- "Name": "Requirement name",
- "Checks": ["check_name"],
- "Attributes": [
- {
- "Section": "BCM Business Continuity Management",
- "SubSection": "BCM-01",
- "Type": "Basic Criteria",
- "AboutCriteria": "Description of criteria",
- "ComplementaryCriteria": "Additional criteria"
- }
- ]
-}
-```
+- Operators: `lte`/`gte` (numeric thresholds), `eq` (toggles/exact — use JSON
+ booleans, not 0/1), `in` (scalar in allowed set), `subset` (allowlists —
+ widening breaks it), `superset` (denylists — removing an entry breaks it).
+- `Value` must be the **strictest** setting the control text tolerates.
+- `ConfigKey` must be spelled exactly as the check reads it; unknown keys are
+ silently skipped (defaults assumed OK).
+- Guardrails only tighten (PASS→FAIL), never relax.
+- Universal files: lowercase `config_requirements` + mandatory `Provider` per
+ constraint.
+- Tests: `tests/lib/check/compliance_config_eval_test.py`,
+ `compliance_config_constraint_model_test.py`,
+ `compliance_config_requirements_data_test.py`, plus per-output tests under
+ `tests/lib/outputs/compliance/`.
---
-### CCC (Cloud Computing Compliance)
-
-**Framework ID format:** `ccc_{provider}` (e.g., `ccc_aws`)
-
-```json
-{
- "Id": "CCC.C01",
- "Description": "Requirement description",
- "Name": "Requirement name",
- "Checks": ["check_name"],
- "Attributes": [
- {
- "FamilyName": "Cryptography & Key Management",
- "FamilyDescription": "Family description",
- "Section": "CCC.C01",
- "SubSection": "Key Management",
- "SubSectionObjective": "Objective description",
- "Applicability": ["IaaS", "PaaS", "SaaS"],
- "Recommendation": "Recommended action",
- "SectionThreatMappings": [{"threat": "T1190"}],
- "SectionGuidelineMappings": [{"guideline": "NIST"}]
- }
- ]
-}
-```
-
----
-
-### Prowler ThreatScore
-
-**Framework ID format:** `prowler_threatscore_{provider}` (e.g., `prowler_threatscore_aws`)
-
-Prowler ThreatScore is a custom security scoring framework developed by Prowler that evaluates AWS account security based on **four main pillars**:
-
-| Pillar | Description |
-|--------|-------------|
-| **1. IAM** | Identity and Access Management controls (authentication, authorization, credentials) |
-| **2. Attack Surface** | Network exposure, public resources, security group rules |
-| **3. Logging and Monitoring** | Audit logging, threat detection, forensic readiness |
-| **4. Encryption** | Data at rest and in transit encryption |
-
-**Scoring System:**
-- **LevelOfRisk** (1-5): Severity of the security issue
- - `5` = Critical (e.g., root MFA, public S3 buckets)
- - `4` = High (e.g., user MFA, public EC2)
- - `3` = Medium (e.g., password policies, encryption)
- - `2` = Low
- - `1` = Informational
-- **Weight**: Impact multiplier for score calculation
- - `1000` = Critical controls (root security, public exposure)
- - `100` = High-impact controls (user authentication, monitoring)
- - `10` = Standard controls (password policies, encryption)
- - `1` = Low-impact controls (best practices)
-
-```json
-{
- "Id": "1.1.1",
- "Description": "Ensure MFA is enabled for the 'root' user account",
- "Checks": ["iam_root_mfa_enabled"],
- "Attributes": [
- {
- "Title": "MFA enabled for 'root'",
- "Section": "1. IAM",
- "SubSection": "1.1 Authentication",
- "AttributeDescription": "The root user account holds the highest level of privileges within an AWS account. Enabling MFA enhances security by adding an additional layer of protection.",
- "AdditionalInformation": "Enabling MFA enhances console security by requiring the authenticating user to both possess a time-sensitive key-generating device and have knowledge of their credentials.",
- "LevelOfRisk": 5,
- "Weight": 1000
- }
- ]
-}
-```
-
-**Available for providers:** AWS, Kubernetes, M365
-
----
-
-## Available Compliance Frameworks
-
-### AWS (41 frameworks)
-| Framework | File Name |
-|-----------|-----------|
-| CIS 1.4, 1.5, 2.0, 3.0, 4.0, 5.0 | `cis_{version}_aws.json` |
-| ISO 27001:2013, 2022 | `iso27001_{year}_aws.json` |
-| NIST 800-53 Rev 4, 5 | `nist_800_53_revision_{version}_aws.json` |
-| NIST 800-171 Rev 2 | `nist_800_171_revision_2_aws.json` |
-| NIST CSF 1.1, 2.0 | `nist_csf_{version}_aws.json` |
-| PCI DSS 3.2.1, 4.0 | `pci_{version}_aws.json` |
-| HIPAA | `hipaa_aws.json` |
-| GDPR | `gdpr_aws.json` |
-| SOC 2 | `soc2_aws.json` |
-| FedRAMP Low/Moderate | `fedramp_{level}_revision_4_aws.json` |
-| ENS RD2022 | `ens_rd2022_aws.json` |
-| MITRE ATT&CK | `mitre_attack_aws.json` |
-| C5 Germany | `c5_aws.json` |
-| CISA | `cisa_aws.json` |
-| FFIEC | `ffiec_aws.json` |
-| RBI Cyber Security | `rbi_cyber_security_framework_aws.json` |
-| AWS Well-Architected | `aws_well_architected_framework_{pillar}_pillar_aws.json` |
-| AWS FTR | `aws_foundational_technical_review_aws.json` |
-| GxP 21 CFR Part 11, EU Annex 11 | `gxp_{standard}_aws.json` |
-| KISA ISMS-P 2023 | `kisa_isms_p_2023_aws.json` |
-| NIS2 | `nis2_aws.json` |
-
-### Azure (15+ frameworks)
-| Framework | File Name |
-|-----------|-----------|
-| CIS 2.0, 2.1, 3.0, 4.0 | `cis_{version}_azure.json` |
-| ISO 27001:2022 | `iso27001_2022_azure.json` |
-| ENS RD2022 | `ens_rd2022_azure.json` |
-| MITRE ATT&CK | `mitre_attack_azure.json` |
-| PCI DSS 4.0 | `pci_4.0_azure.json` |
-| NIST CSF 2.0 | `nist_csf_2.0_azure.json` |
-
-### GCP (15+ frameworks)
-| Framework | File Name |
-|-----------|-----------|
-| CIS 2.0, 3.0, 4.0 | `cis_{version}_gcp.json` |
-| ISO 27001:2022 | `iso27001_2022_gcp.json` |
-| HIPAA | `hipaa_gcp.json` |
-| MITRE ATT&CK | `mitre_attack_gcp.json` |
-| PCI DSS 4.0 | `pci_4.0_gcp.json` |
-| NIST CSF 2.0 | `nist_csf_2.0_gcp.json` |
-
-### Kubernetes (6 frameworks)
-| Framework | File Name |
-|-----------|-----------|
-| CIS 1.8, 1.10, 1.11 | `cis_{version}_kubernetes.json` |
-| ISO 27001:2022 | `iso27001_2022_kubernetes.json` |
-| PCI DSS 4.0 | `pci_4.0_kubernetes.json` |
-
-### Other Providers
-- **GitHub:** `cis_1.0_github.json`
-- **M365:** `cis_4.0_m365.json`, `iso27001_2022_m365.json`
-- **NHN:** `iso27001_2022_nhn.json`
-
## Workflow A: Sync a Framework With an Upstream Catalog
-Use when the framework is maintained upstream (CIS Benchmarks, FINOS CCC, CSA CCM, NIST, ENS, etc.) and Prowler needs to catch up.
+Use when the framework is maintained upstream (CIS Benchmarks, FINOS CCC, CSA
+CCM, NIST, ENS, etc.) and Prowler needs to catch up.
### Step 1 — Cache the upstream source
-Download every upstream file to a local cache so subsequent iterations don't hit the network. For FINOS CCC:
+Download every upstream file to a local cache so iterations don't hit the
+network. For FINOS CCC:
```bash
mkdir -p /tmp/ccc_upstream
@@ -559,492 +715,480 @@ done
### Step 2 — Run the generic sync runner against a framework config
-The sync tooling is split into three layers so adding a new framework only takes a YAML config (and optionally a new parser module for an unfamiliar upstream format):
+The sync tooling is three layers, so adding a framework only takes a YAML
+config (plus a parser module for an unfamiliar upstream format):
-```
+```text
skills/prowler-compliance/assets/
├── sync_framework.py # generic runner — works for any framework
-├── configs/
-│ └── ccc.yaml # per-framework config (canonical example)
-└── parsers/
- ├── __init__.py
- └── finos_ccc.py # parser module for FINOS CCC YAML
+├── configs/ccc.yaml # per-framework config (canonical example)
+└── parsers/finos_ccc.py # parser module for FINOS CCC YAML
```
-**For frameworks that already have a config + parser** (today: FINOS CCC), run:
-
```bash
python skills/prowler-compliance/assets/sync_framework.py \
skills/prowler-compliance/assets/configs/ccc.yaml
```
-The runner loads the config, validates it, dynamically imports the parser declared in `parser.module`, calls `parser.parse_upstream(config) -> list[dict]`, then applies generic post-processing (id uniqueness safety net, `FamilyName` normalization, legacy check-mapping preservation) and writes the provider JSONs.
+The runner loads the config, dynamically imports `parser.module`, calls
+`parse_upstream(config) -> list[dict]`, then applies generic post-processing
+(id-uniqueness safety net, `FamilyName` normalization, legacy check-mapping
+preservation with config-driven fallback keys) and writes the provider JSONs
+with Pydantic post-validation.
**To add a new framework sync**:
-1. **Write a config file** at `skills/prowler-compliance/assets/configs/{framework}.yaml`. See `configs/ccc.yaml` as the canonical example. Required top-level sections:
- - `framework` — `name`, `display_name`, `version` (**never empty** — empty Version silently breaks `get_check_compliance()` key construction, so the runner refuses to start), `description_template` (accepts `{provider_display}`, `{provider_key}`, `{framework_name}`, `{framework_display}`, `{version}` placeholders).
- - `providers` — list of `{key, display}` pairs, one per Prowler provider the framework targets.
- - `output.path_template` — supports `{provider}`, `{framework}`, `{version}` placeholders. Examples: `"prowler/compliance/{provider}/ccc_{provider}.json"` for unversioned file names, `"prowler/compliance/{provider}/cis_{version}_{provider}.json"` for versioned ones.
- - `upstream.dir` — local cache directory (populate via Step 1).
- - `parser.module` — name of the module under `parsers/` to load (without `.py`). Everything else under `parser.` is opaque to the runner and passed to the parser as config.
- - `post_processing.check_preservation.primary_key` — top-level field name for the primary legacy-mapping lookup (almost always `Id`).
- - `post_processing.check_preservation.fallback_keys` — **config-driven fallback keys** for preserving check mappings when ids change. Each entry is a list of `Attributes[0]` field names composed into a tuple. Examples:
- - CCC: `- [Section, Applicability]` (because `Applicability` is a CCC-only attribute, verified in `compliance_models.py:213`).
- - CIS would use `- [Section, Profile]`.
- - NIST would use `- [ItemId]`.
- - List-valued fields (like `Applicability`) are automatically frozen to `frozenset` so the tuple is hashable.
- - `post_processing.family_name_normalization` (optional) — map of raw → canonical `FamilyName` values. The UI groups by `Attributes[0].FamilyName` exactly, so inconsistent upstream variants otherwise become separate tree branches.
+1. Write `assets/configs/{framework}.yaml` (see `ccc.yaml`). Required sections:
+ - `framework` — `name`, `display_name`, `version` (**never empty** — the
+ runner refuses to start, because empty Version breaks the
+ `get_check_compliance()` key), `description_template`.
+ - `providers` — list of `{key, display}` pairs.
+ - `output.path_template` — e.g.
+ `"prowler/compliance/{provider}/cis_{version}_{provider}.json"`.
+ - `upstream.dir` — local cache (Step 1).
+ - `parser.module` — module under `parsers/`; the rest of `parser.` is
+ passed through opaque.
+ - `post_processing.check_preservation.primary_key` (almost always `Id`) and
+ `fallback_keys` — lists of `Attributes[0]` field names composed into
+ tuples for recovering mappings when ids change. CCC:
+ `- [Section, Applicability]`; CIS: `- [Section, Profile]`; NIST:
+ `- [ItemId]`. List-valued fields are frozen to `frozenset` automatically.
+ - `post_processing.family_name_normalization` (optional) — raw → canonical
+ map; the UI groups by the exact attribute value, so upstream variants
+ otherwise become separate tree branches.
+2. Reuse an existing parser or write `parsers/{name}.py` implementing
+ `parse_upstream(config) -> list[dict]` returning Prowler-format
+ requirements with **guaranteed-unique ids**. The runner raises on
+ duplicates — it never silently renumbers, because mutating a canonical
+ upstream id (CIS `1.1.1`, NIST `AC-2(1)`) would be catastrophic. The parser
+ owns all upstream quirks: foreign-prefix rewriting, genuine collision
+ renumbering, multi-shape handling.
-2. **Reuse an existing parser** if the upstream format matches one (currently only `finos_ccc` exists). Otherwise, **write a new parser** at `parsers/{name}.py` implementing:
+**Gotchas the runner already handles** (from the FINOS CCC v2025.10 sync):
- ```python
- def parse_upstream(config: dict) -> list[dict]:
- """Return Prowler-format requirements {Id, Description, Attributes: [...], Checks: []}.
-
- Ids MUST be unique in the returned list. The runner raises ValueError
- on duplicates — it does NOT silently renumber, because mutating a
- canonical upstream id (e.g. CIS '1.1.1' or NIST 'AC-2(1)') would be
- catastrophic. The parser owns all upstream-format quirks: foreign-prefix
- rewriting, genuine collision renumbering, shape handling.
- """
- ```
-
- The parser reads its own settings from `config['upstream']` and `config['parser']`. It does NOT load existing Prowler JSONs (the runner does that for check preservation) and does NOT write output (the runner does that too).
-
-**Gotchas the runner already handles for you** (learned from the FINOS CCC v2025.10 sync — they're documented here so you don't re-discover them):
-
-- **Multiple upstream YAML shapes**. Most FINOS CCC catalogs use `control-families: [...]`, but `storage/object` uses a top-level `controls: [...]` with a `family: "CCC.X.Y"` reference id and no human-readable family name. A parser that only handles shape 1 silently drops the shape-2 catalog — this exact bug dropped ObjStor from Prowler for a full iteration. `parsers/finos_ccc.py` handles both shapes; if you write a new parser for a similar format, test with at least one file of each shape.
-- **Whitespace collapse**. Upstream YAML multi-line block scalars (`|`) preserve newlines. Prowler stores descriptions single-line. Collapse with `" ".join(value.split())` before emitting (see `parsers/finos_ccc.py::clean()`).
-- **Foreign-prefix AR id rewriting**. Upstream sometimes aliases requirements across catalogs by keeping the original prefix (e.g., `CCC.AuditLog.CN08.AR01` appears nested under `CCC.Logging.CN03`). Rewrite the foreign id to fit its parent control: `CCC.Logging.CN03.AR01`. This logic is parser-specific because the id structure varies per framework (CCC uses 3-dot depth; CIS uses numeric dots; NIST uses `AC-2(1)`).
-- **Genuine upstream collision renumbering**. Sometimes upstream has a real typo where two different requirements share the same id (e.g., `CCC.Core.CN14.AR02` defined twice for 30-day and 14-day backup variants). Renumber the second copy to the next free AR number (`.AR03`). The parser handles this; the runner asserts the final list has unique ids as a safety net.
-- **Existing check mapping preservation**. The runner uses the `primary_key` + `fallback_keys` declared in config to look up the old `Checks` list for each requirement. For CCC this means primary index by `Id` plus fallback index by `(Section, frozenset(Applicability))` — the fallback recovers mappings for requirements whose ids were rewritten or renumbered by the parser.
-- **FamilyName normalization**. Configured via `post_processing.family_name_normalization` — no code changes needed to collapse upstream variants like `"Logging & Monitoring"` → `"Logging and Monitoring"`.
-- **Populate `Version`**. The runner refuses to start on empty `framework.version` — fail-fast replaces the silent bug where `get_check_compliance()` would build the key as just `"{Framework}"`.
+- **Multiple upstream YAML shapes.** Most FINOS CCC catalogs use
+ `control-families: [...]` but `storage/object` uses top-level
+ `controls: [...]`. A single-shape parser silently drops entire catalogs —
+ this exact bug dropped ObjStor for a full iteration. Test with one file of
+ each shape.
+- **Whitespace collapse.** Upstream `|` block scalars keep newlines; Prowler
+ stores single-line. Collapse with `" ".join(value.split())`.
+- **Foreign-prefix id rewriting.** Upstream aliases requirements across
+ catalogs keeping the original prefix (`CCC.AuditLog.CN08.AR01` nested under
+ `CCC.Logging.CN03`) — rewrite to fit the parent (`CCC.Logging.CN03.AR01`).
+- **Genuine upstream collisions.** Two different requirements sharing one id
+ (upstream typo): renumber the second to the next free number; check-mapping
+ preservation recovers by the fallback keys.
+- **Populate `Version`** — fail-fast beats the silent broken-key bug.
### Step 3 — Validate before committing
-```python
-from prowler.lib.check.compliance_models import Compliance
-for prov in ['aws', 'azure', 'gcp']:
- c = Compliance.parse_file(f"prowler/compliance/{prov}/ccc_{prov}.json")
- print(f"{prov}: {len(c.Requirements)} reqs, version={c.Version}")
-```
+Run the full Validation section below (universal loader + check existence +
+CLI smoke + pytest).
-Any `ValidationError` means the Attribute fields don't match the `*_Requirement_Attribute` model. Either fix the JSON or extend the model in `compliance_models.py` (remember: Generic stays last).
+### Step 4 — Add an attribute model if needed
-### Step 4 — Verify every check id exists
-
-```python
-import json
-from pathlib import Path
-for prov in ['aws', 'azure', 'gcp']:
- existing = {p.stem.replace('.metadata','')
- for p in Path(f'prowler/providers/{prov}/services').rglob('*.metadata.json')}
- with open(f'prowler/compliance/{prov}/ccc_{prov}.json') as f:
- data = json.load(f)
- refs = {c for r in data['Requirements'] for c in r['Checks']}
- missing = refs - existing
- assert not missing, f"{prov} missing: {missing}"
-```
-
-A stale check id silently becomes dead weight — no finding will ever map to it. This pre-validation **must run on every write**; bake it into the generator script.
-
-### Step 5 — Add an attribute model if needed
-
-Only if the framework has fields beyond `Generic_Compliance_Requirement_Attribute`. Add the class to `prowler/lib/check/compliance_models.py` and register it in `Compliance_Requirement.Attributes: list[Union[...]]`. **Generic stays last.**
+Only if the framework has fields beyond
+`Generic_Compliance_Requirement_Attribute` and must stay legacy. Add the class
+to `compliance_models.py` and register it in the
+`Compliance_Requirement.Attributes` Union **before Generic** (Generic stays
+last). For new frameworks, prefer universal `attributes_metadata` instead.
---
## Workflow B: Audit Check Mappings as a Cloud Auditor
-Use when the user asks to review existing mappings ("are these correct?", "verify that the checks apply", "audit the CCC mappings"). This is the highest-value compliance task — it surfaces padded mappings with zero actual coverage and missing mappings for legitimate coverage.
+Use when the user asks to review existing mappings. This is the
+highest-value compliance task — it surfaces padded mappings with zero actual
+coverage and missing mappings for legitimate coverage.
### The golden rule
-> A Prowler check's title/risk MUST **literally describe what the requirement text says**. "Related" is not enough. If no check actually addresses the requirement, leave `Checks: []` (MANUAL) — **honest MANUAL is worth more than padded coverage**.
+> A Prowler check's title/risk MUST **literally describe what the requirement
+> text says**. "Related" is not enough. If no check actually addresses the
+> requirement, leave the checks list empty (MANUAL) — **honest MANUAL is worth
+> more than padded coverage**.
### Audit process
-**Step 1 — Build a per-provider check inventory** (cache in `/tmp/`):
+1. **Build a per-provider check inventory** — `assets/build_inventory.py`
+ (writes `/tmp/checks_{provider}.json` for every provider discovered under
+ `prowler/providers/`).
+2. **Query it** — `assets/query_checks.py` (run from the repository root):
-```python
-import json
-from pathlib import Path
-for provider in ['aws', 'azure', 'gcp']:
- inv = {}
- for meta in Path(f'prowler/providers/{provider}/services').rglob('*.metadata.json'):
- with open(meta) as f:
- d = json.load(f)
- cid = d.get('CheckID') or meta.stem.replace('.metadata','')
- inv[cid] = {
- 'service': d.get('ServiceName', ''),
- 'title': d.get('CheckTitle', ''),
- 'risk': d.get('Risk', ''),
- 'description': d.get('Description', ''),
- }
- with open(f'/tmp/checks_{provider}.json', 'w') as f:
- json.dump(inv, f, indent=2)
-```
+ ```bash
+ python skills/prowler-compliance/assets/query_checks.py aws encryption transit # keyword AND-search
+ python skills/prowler-compliance/assets/query_checks.py aws --service iam # all iam checks
+ python skills/prowler-compliance/assets/query_checks.py aws --id kms_cmk_rotation_enabled
+ ```
-**Step 2 — Keyword/service query helper** — see [assets/query_checks.py](assets/query_checks.py):
+3. **Dump a framework section with current mappings** — `assets/dump_section.py`:
-```bash
-python assets/query_checks.py aws encryption transit # keyword AND-search
-python assets/query_checks.py aws --service iam # all iam checks
-python assets/query_checks.py aws --id kms_cmk_rotation_enabled # full metadata
-```
+ ```bash
+ python skills/prowler-compliance/assets/dump_section.py ccc "CCC.Core."
+ python skills/prowler-compliance/assets/dump_section.py cis_5.0_aws "1."
+ ```
-**Step 3 — Dump a framework section with current mappings** — see [assets/dump_section.py](assets/dump_section.py):
+4. **Encode explicit REPLACE decisions** — `assets/audit_framework_template.py`:
-```bash
-python assets/dump_section.py ccc "CCC.Core." # all Core ARs across 3 providers
-python assets/dump_section.py ccc "CCC.AuditLog." # all AuditLog ARs
-```
+ ```python
+ DECISIONS = {}
+ DECISIONS["CCC.Core.CN01.AR01"] = {
+ "aws": ["cloudfront_distributions_https_enabled", ...],
+ "azure": ["storage_secure_transfer_required_is_enabled", ...],
+ "gcp": ["cloudsql_instance_ssl_connections"],
+ # Missing provider key = leave the legacy mapping untouched
+ }
+ # Empty list = EXPLICITLY MANUAL (overwrites legacy)
+ DECISIONS["CCC.Core.CN01.AR07"] = {"aws": [], "azure": [], "gcp": []}
+ ```
-**Step 4 — Encode explicit REPLACE decisions** — see [assets/audit_framework_template.py](assets/audit_framework_template.py). Structure:
+ **REPLACE, not PATCH.** Full lists make the audit reproducible and surface
+ hidden assumptions in the legacy data.
+5. **Pre-validate** every check id against the inventory; the script MUST
+ abort with stderr listing typos (real audits caught
+ `storage_secure_transfer_required_enabled` →
+ `storage_secure_transfer_required_is_enabled`,
+ `sqlserver_minimum_tls_version_12` →
+ `sqlserver_recommended_minimal_tls_version`, and several checks that
+ simply don't exist).
+6. **Apply + validate + test**:
-```python
-DECISIONS = {}
+ ```bash
+ python /path/to/audit_script.py
+ uv run pytest -n auto tests/lib/outputs/compliance/ tests/lib/check/ -q
+ ```
-DECISIONS["CCC.Core.CN01.AR01"] = {
- "aws": [
- "cloudfront_distributions_https_enabled",
- "cloudfront_distributions_origin_traffic_encrypted",
- # ...
- ],
- "azure": [
- "storage_secure_transfer_required_is_enabled",
- "app_minimum_tls_version_12",
- # ...
- ],
- "gcp": [
- "cloudsql_instance_ssl_connections",
- ],
- # Missing provider key = leave the legacy mapping untouched
-}
-
-# Empty list = EXPLICITLY MANUAL (overwrites legacy)
-DECISIONS["CCC.Core.CN01.AR07"] = {
- "aws": [], # Prowler has no IANA port/protocol check
- "azure": [],
- "gcp": [],
-}
-```
-
-**REPLACE, not PATCH.** Encoding every mapping as a full list (not add/remove delta) makes the audit reproducible and surfaces hidden assumptions from the legacy data.
-
-**Step 5 — Pre-validation**. The audit script MUST validate every check id against the inventory and **abort with stderr listing typos**. Common typos caught during a real audit:
-
-- `fsx_file_system_encryption_at_rest_using_kms` (doesn't exist)
-- `cosmosdb_account_encryption_at_rest_with_cmk` (doesn't exist)
-- `sqlserver_geo_replication` (doesn't exist)
-- `redshift_cluster_audit_logging` (should be `redshift_cluster_encrypted_at_rest`)
-- `postgresql_flexible_server_require_secure_transport` (should be `postgresql_flexible_server_enforce_ssl_enabled`)
-- `storage_secure_transfer_required_enabled` (should be `storage_secure_transfer_required_is_enabled`)
-- `sqlserver_minimum_tls_version_12` (should be `sqlserver_recommended_minimal_tls_version`)
-
-**Step 6 — Apply + validate + test**:
-
-```bash
-python /path/to/audit_script.py # applies decisions, pre-validates
-python -m pytest tests/lib/outputs/compliance/ tests/lib/check/ -q
-```
-
-### Audit Reference Table: Requirement Text → Prowler Checks
-
-Use this table to map CCC-style / NIST-style / ISO-style requirements to the checks that actually verify them. Built from a real audit of 172 CCC ARs × 3 providers.
-
-| Requirement text | AWS checks | Azure checks | GCP checks |
-|---|---|---|---|
-| **TLS in transit enforced** | `cloudfront_distributions_https_enabled`, `s3_bucket_secure_transport_policy`, `elbv2_ssl_listeners`, `elbv2_insecure_ssl_ciphers`, `elb_ssl_listeners`, `elb_insecure_ssl_ciphers`, `opensearch_service_domains_https_communications_enforced`, `rds_instance_transport_encrypted`, `redshift_cluster_in_transit_encryption_enabled`, `elasticache_redis_cluster_in_transit_encryption_enabled`, `dynamodb_accelerator_cluster_in_transit_encryption_enabled`, `dms_endpoint_ssl_enabled`, `kafka_cluster_in_transit_encryption_enabled`, `transfer_server_in_transit_encryption_enabled`, `glue_database_connections_ssl_enabled`, `sns_subscription_not_using_http_endpoints` | `storage_secure_transfer_required_is_enabled`, `storage_ensure_minimum_tls_version_12`, `postgresql_flexible_server_enforce_ssl_enabled`, `mysql_flexible_server_ssl_connection_enabled`, `mysql_flexible_server_minimum_tls_version_12`, `sqlserver_recommended_minimal_tls_version`, `app_minimum_tls_version_12`, `app_ensure_http_is_redirected_to_https`, `app_ftp_deployment_disabled` | `cloudsql_instance_ssl_connections` (almost only option) |
-| **TLS 1.3 specifically** | Partial: `cloudfront_distributions_using_deprecated_ssl_protocols`, `elb*_insecure_ssl_ciphers`, `*_minimum_tls_version_12` | Partial: `*_minimum_tls_version_12` checks | None — accept as MANUAL |
-| **SSH / port 22 hardening** | `ec2_instance_port_ssh_exposed_to_internet`, `ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22`, `ec2_networkacl_allow_ingress_tcp_port_22` | `network_ssh_internet_access_restricted`, `vm_linux_enforce_ssh_authentication` | `compute_firewall_ssh_access_from_the_internet_allowed`, `compute_instance_block_project_wide_ssh_keys_disabled`, `compute_project_os_login_enabled`, `compute_project_os_login_2fa_enabled` |
-| **mTLS (mutual TLS)** | `kafka_cluster_mutual_tls_authentication_enabled`, `apigateway_restapi_client_certificate_enabled` | `app_client_certificates_on` | None — MANUAL |
-| **Data at rest encrypted** | `s3_bucket_default_encryption`, `s3_bucket_kms_encryption`, `ec2_ebs_default_encryption`, `ec2_ebs_volume_encryption`, `rds_instance_storage_encrypted`, `rds_cluster_storage_encrypted`, `rds_snapshots_encrypted`, `dynamodb_tables_kms_cmk_encryption_enabled`, `redshift_cluster_encrypted_at_rest`, `neptune_cluster_storage_encrypted`, `documentdb_cluster_storage_encrypted`, `opensearch_service_domains_encryption_at_rest_enabled`, `kinesis_stream_encrypted_at_rest`, `firehose_stream_encrypted_at_rest`, `sns_topics_kms_encryption_at_rest_enabled`, `sqs_queues_server_side_encryption_enabled`, `efs_encryption_at_rest_enabled`, `athena_workgroup_encryption`, `glue_data_catalogs_metadata_encryption_enabled`, `backup_vaults_encrypted`, `backup_recovery_point_encrypted`, `cloudtrail_kms_encryption_enabled`, `cloudwatch_log_group_kms_encryption_enabled`, `eks_cluster_kms_cmk_encryption_in_secrets_enabled`, `sagemaker_notebook_instance_encryption_enabled`, `apigateway_restapi_cache_encrypted`, `kafka_cluster_encryption_at_rest_uses_cmk`, `dynamodb_accelerator_cluster_encryption_enabled`, `storagegateway_fileshare_encryption_enabled` | `storage_infrastructure_encryption_is_enabled`, `storage_ensure_encryption_with_customer_managed_keys`, `vm_ensure_attached_disks_encrypted_with_cmk`, `vm_ensure_unattached_disks_encrypted_with_cmk`, `sqlserver_tde_encryption_enabled`, `sqlserver_tde_encrypted_with_cmk`, `databricks_workspace_cmk_encryption_enabled`, `monitor_storage_account_with_activity_logs_cmk_encrypted` | `compute_instance_encryption_with_csek_enabled`, `dataproc_encrypted_with_cmks_disabled`, `bigquery_dataset_cmk_encryption`, `bigquery_table_cmk_encryption` |
-| **CMEK required (customer-managed keys)** | `kms_cmk_are_used` | `storage_ensure_encryption_with_customer_managed_keys`, `vm_ensure_attached_disks_encrypted_with_cmk`, `vm_ensure_unattached_disks_encrypted_with_cmk`, `sqlserver_tde_encrypted_with_cmk`, `databricks_workspace_cmk_encryption_enabled` | `bigquery_dataset_cmk_encryption`, `bigquery_table_cmk_encryption`, `dataproc_encrypted_with_cmks_disabled`, `compute_instance_encryption_with_csek_enabled` |
-| **Key rotation enabled** | `kms_cmk_rotation_enabled` | `keyvault_key_rotation_enabled`, `storage_key_rotation_90_days` | `kms_key_rotation_enabled` |
-| **MFA for UI access** | `iam_root_mfa_enabled`, `iam_root_hardware_mfa_enabled`, `iam_user_mfa_enabled_console_access`, `iam_user_hardware_mfa_enabled`, `iam_administrator_access_with_mfa`, `cognito_user_pool_mfa_enabled` | `entra_privileged_user_has_mfa`, `entra_non_privileged_user_has_mfa`, `entra_user_with_vm_access_has_mfa`, `entra_security_defaults_enabled` | `compute_project_os_login_2fa_enabled` |
-| **API access / credentials** | `iam_no_root_access_key`, `iam_user_no_setup_initial_access_key`, `apigateway_restapi_authorizers_enabled`, `apigateway_restapi_public_with_authorizer`, `apigatewayv2_api_authorizers_enabled` | `entra_conditional_access_policy_require_mfa_for_management_api`, `app_function_access_keys_configured`, `app_function_identity_is_configured` | `apikeys_api_restrictions_configured`, `apikeys_key_exists`, `apikeys_key_rotated_in_90_days` |
-| **Log all admin/config changes** | `cloudtrail_multi_region_enabled`, `cloudtrail_multi_region_enabled_logging_management_events`, `cloudtrail_cloudwatch_logging_enabled`, `cloudtrail_log_file_validation_enabled`, `cloudwatch_log_metric_filter_*`, `cloudwatch_changes_to_*_alarm_configured`, `config_recorder_all_regions_enabled` | `monitor_diagnostic_settings_exists`, `monitor_diagnostic_setting_with_appropriate_categories`, `monitor_alert_*` | `iam_audit_logs_enabled`, `logging_log_metric_filter_and_alert_for_*`, `logging_sink_created` |
-| **Log integrity (digital signatures)** | `cloudtrail_log_file_validation_enabled` (exact) | None | None |
-| **Public access denied** | `s3_bucket_public_access`, `s3_bucket_public_list_acl`, `s3_bucket_public_write_acl`, `s3_account_level_public_access_blocks`, `apigateway_restapi_public`, `awslambda_function_url_public`, `awslambda_function_not_publicly_accessible`, `rds_instance_no_public_access`, `rds_snapshots_public_access`, `ec2_securitygroup_allow_ingress_from_internet_to_all_ports`, `sns_topics_not_publicly_accessible`, `sqs_queues_not_publicly_accessible` | `storage_blob_public_access_level_is_disabled`, `storage_ensure_private_endpoints_in_storage_accounts`, `containerregistry_not_publicly_accessible`, `keyvault_private_endpoints`, `app_function_not_publicly_accessible`, `aks_clusters_public_access_disabled`, `network_http_internet_access_restricted` | `cloudstorage_bucket_public_access`, `compute_instance_public_ip`, `cloudsql_instance_public_ip`, `compute_firewall_*_access_from_the_internet_allowed` |
-| **IAM least privilege** | `iam_*_no_administrative_privileges`, `iam_policy_allows_privilege_escalation`, `iam_inline_policy_allows_privilege_escalation`, `iam_role_administratoraccess_policy`, `iam_group_administrator_access_policy`, `iam_user_administrator_access_policy`, `iam_policy_attached_only_to_group_or_roles`, `iam_role_cross_service_confused_deputy_prevention` | `iam_role_user_access_admin_restricted`, `iam_subscription_roles_owner_custom_not_created`, `iam_custom_role_has_permissions_to_administer_resource_locks` | `iam_sa_no_administrative_privileges`, `iam_no_service_roles_at_project_level`, `iam_role_kms_enforce_separation_of_duties`, `iam_role_sa_enforce_separation_of_duties` |
-| **Password policy** | `iam_password_policy_minimum_length_14`, `iam_password_policy_uppercase`, `iam_password_policy_lowercase`, `iam_password_policy_symbol`, `iam_password_policy_number`, `iam_password_policy_expires_passwords_within_90_days_or_less`, `iam_password_policy_reuse_24` | None | None |
-| **Credential rotation / unused** | `iam_rotate_access_key_90_days`, `iam_user_accesskey_unused`, `iam_user_console_access_unused` | None | `iam_sa_user_managed_key_rotate_90_days`, `iam_sa_user_managed_key_unused`, `iam_service_account_unused` |
-| **VPC / flow logs** | `vpc_flow_logs_enabled` | `network_flow_log_captured_sent`, `network_watcher_enabled`, `network_flow_log_more_than_90_days` | `compute_subnet_flow_logs_enabled` |
-| **Backup / DR / Multi-AZ** | `backup_vaults_exist`, `backup_plans_exist`, `backup_reportplans_exist`, `rds_instance_backup_enabled`, `rds_*_protected_by_backup_plan`, `rds_cluster_multi_az`, `neptune_cluster_backup_enabled`, `documentdb_cluster_backup_enabled`, `efs_have_backup_enabled`, `s3_bucket_cross_region_replication`, `dynamodb_table_protected_by_backup_plan` | `vm_backup_enabled`, `vm_sufficient_daily_backup_retention_period`, `storage_geo_redundant_enabled` | `cloudsql_instance_automated_backups`, `cloudstorage_bucket_log_retention_policy_lock`, `cloudstorage_bucket_sufficient_retention_period` |
-| **Access analysis / discovery** | `accessanalyzer_enabled`, `accessanalyzer_enabled_without_findings` | None specific | `iam_account_access_approval_enabled`, `iam_cloud_asset_inventory_enabled` |
-| **Object lock / retention** | `s3_bucket_object_lock`, `s3_bucket_object_versioning`, `s3_bucket_lifecycle_enabled`, `cloudtrail_bucket_requires_mfa_delete`, `s3_bucket_no_mfa_delete` | `storage_ensure_soft_delete_is_enabled`, `storage_blob_versioning_is_enabled`, `storage_ensure_file_shares_soft_delete_is_enabled` | `cloudstorage_bucket_log_retention_policy_lock`, `cloudstorage_bucket_soft_delete_enabled`, `cloudstorage_bucket_versioning_enabled`, `cloudstorage_bucket_sufficient_retention_period` |
-| **Uniform bucket-level access** | `s3_bucket_acl_prohibited` | `storage_account_key_access_disabled`, `storage_default_to_entra_authorization_enabled` | `cloudstorage_bucket_uniform_bucket_level_access` |
-| **Container vulnerability scanning** | `ecr_registry_scan_images_on_push_enabled`, `ecr_repositories_scan_vulnerabilities_in_latest_image` | `defender_container_images_scan_enabled`, `defender_container_images_resolved_vulnerabilities` | `artifacts_container_analysis_enabled`, `gcr_container_scanning_enabled` |
-| **WAF / rate limiting** | `wafv2_webacl_with_rules`, `waf_*_webacl_with_rules`, `wafv2_webacl_logging_enabled`, `waf_global_webacl_logging_enabled` | None | None |
-| **Deployment region restriction** | `organizations_scp_check_deny_regions` | None | None |
-| **Secrets automatic rotation** | `secretsmanager_automatic_rotation_enabled`, `secretsmanager_secret_rotated_periodically` | `keyvault_rbac_secret_expiration_set`, `keyvault_non_rbac_secret_expiration_set` | None |
-| **Certificate management** | `acm_certificates_expiration_check`, `acm_certificates_with_secure_key_algorithms`, `acm_certificates_transparency_logs_enabled` | `keyvault_key_expiration_set_in_non_rbac`, `keyvault_rbac_key_expiration_set`, `keyvault_non_rbac_secret_expiration_set` | None |
-| **GenAI guardrails / input/output filtering** | `bedrock_guardrail_prompt_attack_filter_enabled`, `bedrock_guardrail_sensitive_information_filter_enabled`, `bedrock_agent_guardrail_enabled`, `bedrock_model_invocation_logging_enabled`, `bedrock_api_key_no_administrative_privileges`, `bedrock_api_key_no_long_term_credentials` | None | None |
-| **ML dev environment security** | `sagemaker_notebook_instance_root_access_disabled`, `sagemaker_notebook_instance_without_direct_internet_access_configured`, `sagemaker_notebook_instance_vpc_settings_configured`, `sagemaker_models_vpc_settings_configured`, `sagemaker_training_jobs_vpc_settings_configured`, `sagemaker_training_jobs_network_isolation_enabled`, `sagemaker_training_jobs_volume_and_output_encryption_enabled` | None | None |
-| **Threat detection / anomalous behavior** | `cloudtrail_threat_detection_enumeration`, `cloudtrail_threat_detection_privilege_escalation`, `cloudtrail_threat_detection_llm_jacking`, `guardduty_is_enabled`, `guardduty_no_high_severity_findings` | None | None |
-| **Serverless private access** | `awslambda_function_inside_vpc`, `awslambda_function_not_publicly_accessible`, `awslambda_function_url_public` | `app_function_not_publicly_accessible` | None |
-
-### What Prowler Does NOT Cover (accept MANUAL honestly)
-
-Don't pad mappings for these — mark `Checks: []` and move on:
-
-- **TLS 1.3 version specifically** — Prowler verifies TLS is enforced, not always the exact version
-- **IANA port-protocol consistency** — no check for "protocol running on its assigned port"
-- **mTLS on most Azure/GCP services** — limited to App Service client certs on Azure, nothing on GCP
-- **Rate limiting** on monitoring endpoints, load balancers, serverless invocations, vector ingestion
-- **Session cookie expiry** (LB stickiness)
-- **HTTP header scrubbing** (Server, X-Powered-By)
-- **Certificate transparency verification for imports**
-- **Model version pinning, red teaming, AI quality review**
-- **Vector embedding validation, dimensional constraints, ANN vs exact search**
-- **Secret region replication** (cross-region residency)
-- **Lifecycle cleanup policies on container registries**
-- **Row-level / column-level security in data warehouses**
-- **Deployment region restriction on Azure/GCP** (AWS has `organizations_scp_check_deny_regions`, others don't)
-- **Cross-tenant alert silencing permissions**
-- **Field-level masking in logs**
-- **Managed view enforcement for database access**
-- **Automatic MFA delete on all S3 buckets** (only CloudTrail bucket variant exists for some frameworks — AWS has the generic `s3_bucket_no_mfa_delete` though)
+For the curated mapping table (requirement text → AWS/Azure/GCP checks) and
+the list of controls Prowler genuinely cannot verify, see
+[references/check-mapping-reference.md](references/check-mapping-reference.md).
---
-## Workflow C: Add a New Output Formatter
+## Workflow C: Add a New Universal Framework
-Use when a new framework needs its own CSV columns or terminal table. Follow the c5/csa/ens layout exactly:
+1. Author `prowler/compliance/{framework}_{version}.json` following the
+ Universal Schema Reference above (use `dora_2022_2554.json` or
+ `csa_ccm_4.0.json` as template).
+2. Declare every attribute in `attributes_metadata` (with `required`/`enum`
+ where possible — that's your load-time validation) and a
+ `outputs.table_config.group_by`.
+3. Map checks per provider; add `config_requirements` (with `Provider`) for
+ configurable checks; leave empty lists for manual requirements — **include
+ every requirement of the source catalog** (coverage percentages depend on
+ the full denominator).
+4. Validate (section below). No Python registration of any kind is needed for
+ CLI table/CSV/OCSF.
+5. Optional first-class UI: mapper in `ui/lib/compliance/{framework}.tsx`,
+ registration in `getComplianceMappers()` under the JSON's `framework` value,
+ detail panel, `*AttributesMetadata` type, and icon (ordered keyword!). Until
+ then the generic mapper renders it.
+6. Optional API extras: CSV exporter entry in `COMPLIANCE_CLASS_MAP`; PDF
+ generator + `FRAMEWORK_REGISTRY` entry if a PDF is required.
+7. Tests: extend `tests/lib/check/universal_compliance_models_test.py` with a
+ case loading the new JSON. The parametrized `test_loads_as_universal`
+ already picks the file up automatically.
+8. Changelog fragment `prowler/changelog.d/<slug>.added.md` + user-guide
+ tutorial under `docs/user-guide/compliance/tutorials/` for high-profile
+ frameworks.
-```bash
-mkdir -p prowler/lib/outputs/compliance/{framework}
-touch prowler/lib/outputs/compliance/{framework}/__init__.py
-```
+## Workflow D: Add a New Legacy Output Formatter
-### Step 1 — Create `{framework}.py` (table dispatcher ONLY)
+Only for new members of an existing legacy family. Follow the `c5/` or `ccc/`
+layout exactly:
-Copy from `prowler/lib/outputs/compliance/c5/c5.py` and change the function name + framework string. The `diff` between your file and `c5.py` should be just those two lines. **No function docstring** — other frameworks don't have one, stay consistent.
+1. `mkdir prowler/lib/outputs/compliance/{framework}` with `__init__.py`.
+2. `{framework}.py` — copy `c5/c5.py`, change function name + framework
+ string; the diff should be just those lines. No docstring (legacy style).
+3. `models.py` — one Pydantic CSV row model per provider. Column sets differ
+ per provider (`AccountId`/`Region` vs `SubscriptionId`/`Location` vs
+ `ProjectId`/`Location`); per-provider files are the convention — don't
+ collapse them into a parameterized class, reviewers will reject it.
+4. `{framework}_{provider}.py` — `{Framework}_{Provider}(ComplianceOutput)`
+ with `transform()`; this file may import `Finding`.
+5. Register:
+ - `compliance.py` → `display_compliance_table()` `elif` branch (+ top import).
+ - `prowler/__main__.py` → per-provider `elif compliance_name.startswith(...)`
+ branches instantiating the writer classes.
+ - `api/src/backend/tasks/jobs/export.py` → `COMPLIANCE_CLASS_MAP` entries
+ (`startswith` for families, exact match only for true singletons).
+6. Tests under `tests/lib/outputs/compliance/{framework}/` + fixtures in
+ `tests/lib/outputs/compliance/fixtures.py` (1 evaluated + 1 manual
+ requirement to exercise both `transform()` paths).
-### Step 2 — Create `models.py`
+**Circular import warning**: the table file must not import `Finding` directly
+or transitively (cycle: `compliance.compliance` → table → `ComplianceOutput` →
+`Finding` → `get_check_compliance` → `compliance.compliance`). Keep it bare;
+use `TYPE_CHECKING`/function-local imports where both are genuinely needed.
-One Pydantic v2 `BaseModel` per provider. Field names become CSV column headers (public API — don't rename later without a migration).
+---
-```python
-from typing import Optional
-from pydantic import BaseModel
+## Validation (run before every commit)
-class {Framework}_AWSModel(BaseModel):
- Provider: str
- Description: str
- AccountId: str
- Region: str
- AssessmentDate: str
- Requirements_Id: str
- Requirements_Description: str
- # ... provider-specific columns
- Status: str
- StatusExtended: str
- ResourceId: str
- ResourceName: str
- CheckId: str
- Muted: bool
-```
+1. **Schema load (both formats)**:
-### Step 3 — Create `{framework}_{provider}.py` for each provider
+ ```python
+ from prowler.lib.check.compliance_models import (
+ load_compliance_framework_universal,
+ get_bulk_compliance_frameworks_universal,
+ )
+ fw = load_compliance_framework_universal("prowler/compliance/<file>.json")
+ assert fw is not None, "check logs for the ValidationError"
+ print(fw.framework, len(fw.requirements), fw.get_providers())
+ assert "<file_basename>" in get_bulk_compliance_frameworks_universal("aws")
+ ```
-Copy from `prowler/lib/outputs/compliance/c5/c5_aws.py` etc. Contains the `{Framework}_AWS(ComplianceOutput)` class with `transform()` that walks findings and emits model rows. This file IS allowed to import `Finding`.
+ Remember: the universal loader is lenient (skips broken files with a log
+ line) — an `assert fw is not None` is mandatory, a green scan is not proof.
-### Step 4 — Register everywhere
+2. **Check existence** — no loader validates this; a stale id is silent dead
+ weight:
-**`prowler/lib/outputs/compliance/compliance.py`** (CLI table dispatcher):
-```python
-from prowler.lib.outputs.compliance.{framework}.{framework} import get_{framework}_table
+ ```python
+ import json
+ from pathlib import Path
+ for prov in ["aws", "azure", "gcp"]:
+ real = {p.stem.replace(".metadata", "")
+ for p in Path(f"prowler/providers/{prov}/services").rglob("*.metadata.json")}
+ data = json.load(open(f"prowler/compliance/{prov}/<file>.json"))
+ refs = {c for r in data["Requirements"] for c in r["Checks"]}
+ missing = refs - real
+ assert not missing, f"{prov} missing: {missing}"
+ ```
-def display_compliance_table(...):
- ...
- elif compliance_framework.startswith("{framework}_"):
- get_{framework}_table(findings, bulk_checks_metadata,
- compliance_framework, output_filename,
- output_directory, compliance_overview)
-```
+ (For universal files use `r.get("checks", {}).get(prov, [])` instead —
+ requirements may legitimately omit a provider key.)
-**`prowler/__main__.py`** (CLI output writer per provider):
-Add imports at the top:
-```python
-from prowler.lib.outputs.compliance.{framework}.{framework}_aws import {Framework}_AWS
-from prowler.lib.outputs.compliance.{framework}.{framework}_azure import {Framework}_Azure
-from prowler.lib.outputs.compliance.{framework}.{framework}_gcp import {Framework}_GCP
-```
-Add provider-specific `elif compliance_name.startswith("{framework}_"):` branches that instantiate the class and call `batch_write_data_to_file()`.
+3. **CLI smoke test**:
-**`api/src/backend/tasks/jobs/export.py`** (API export dispatcher):
-```python
-from prowler.lib.outputs.compliance.{framework}.{framework}_aws import {Framework}_AWS
-# ... azure, gcp
+ ```bash
+ uv run python prowler-cli.py <provider> --list-compliance # appears?
+ uv run python prowler-cli.py <provider> --compliance <key> --log-level ERROR
+ ```
-COMPLIANCE_CLASS_MAP = {
- "aws": [
- # ...
- (lambda name: name.startswith("{framework}_"), {Framework}_AWS),
- ],
- # ... azure, gcp
-}
-```
+ Verify the CSV under `output/compliance/`, the summary table sections, and
+ the findings roll-up.
-**Always use `startswith`**, never `name == "framework_aws"`. Exact match is a regression.
+4. **Tests**:
-### Step 5 — Add tests
+ ```bash
+ uv run pytest -n auto tests/lib/check/universal_compliance_models_test.py \
+ tests/lib/outputs/compliance/
+ ```
-Create `tests/lib/outputs/compliance/{framework}/` with `{framework}_aws_test.py`, `{framework}_azure_test.py`, `{framework}_gcp_test.py`. See the test template in [references/test_template.md](references/test_template.md).
+ `test_loads_as_universal` is parametrized over **every** JSON in
+ `prowler/compliance/` (top-level + subdirectories) — a malformed file fails
+ CI here even if you never wrote a dedicated test.
-Add fixtures to `tests/lib/outputs/compliance/fixtures.py`: one `Compliance` object per provider with 1 evaluated + 1 manual requirement to exercise both code paths in `transform()`.
+5. **What CI/pre-commit do and don't cover**: pre-commit only guarantees
+ well-formed/pretty JSON (`check-json`, `pretty-format-json`) — no semantic
+ validation. The workflow `.github/workflows/pr-check-compliance-mapping.yml`
+ flags PRs adding new checks without mapping them to any framework (label
+ `needs-compliance-review`; skip with label `no-compliance-check`). Semantic
+ validation happens in the pytest suite above and manually via
+ `skills/prowler-compliance-review/assets/validate_compliance.py` (note:
+ that validator assumes the **legacy** schema).
-### Circular import warning
-
-**The table dispatcher file (`{framework}.py`) MUST NOT import `Finding`** (directly or transitively). The cycle is:
-
-```
-compliance.compliance imports get_{framework}_table
- → {framework}.py imports ComplianceOutput
- → compliance_output imports Finding
- → finding imports get_check_compliance from compliance.compliance
- → CIRCULAR
-```
-
-Keep `{framework}.py` bare — only `colorama`, `tabulate`, `prowler.config.config`. Put anything that imports `Finding` in the per-provider `{framework}_{provider}.py` files.
+6. **Prowler Local Server**: `docker compose up` and confirm the compliance
+ page renders requirements, sections and widgets.
---
## Conventions and Hard-Won Gotchas
-These are lessons from the FINOS CCC v2025.10 sync + 172-AR audit pass (April 2026). Learn them once; save days of debugging.
-
-1. **Per-provider files are non-negotiable.** Never collapse `{framework}_aws.py`, `{framework}_azure.py`, `{framework}_gcp.py` into a single parameterized class, no matter how DRY-tempting. Every other framework in the codebase follows the per-provider pattern and reviewers will reject the refactor. The CSV column names differ per provider — three classes is the convention.
-2. **`{framework}.py` has NO function docstring.** Other frameworks don't have them. Don't add one to be "helpful".
-3. **Circular import protection**: the table dispatcher file MUST NOT import `Finding` (directly or transitively). Split the code so `{framework}.py` only has `get_{framework}_table()` with bare imports, and `{framework}_{provider}.py` holds the class that needs `Finding`.
-4. **`Generic_Compliance_Requirement_Attribute` is the fallback** — in the `Compliance_Requirement.Attributes` Union in `compliance_models.py`, Generic MUST be LAST because Pydantic v1 tries union members in order. Putting Generic first means every framework-specific attribute falls through to Generic and the specific model is never used.
-5. **Pydantic v1 imports.** `from pydantic.v1 import BaseModel` in `compliance_models.py` — not v2. Mixing causes validation errors. Pydantic v2 is used in the CSV models (`models.py`) — that's fine because they're separate trees.
-6. **`get_check_compliance()` key format** is `f"{Framework}-{Version}"` ONLY if Version is set. Empty Version → key is `"{Framework}"` (no version suffix). Tests that mock compliance dicts must match this exact format — when a framework ships with `Version: ""`, downstream code and tests break silently.
-7. **CSV column names from `models.py` are public API.** Don't rename a field without migrating downstream consumers — CSV headers change.
-8. **Upstream YAML multi-line scalars** (`|` block scalars) preserve newlines. Collapse to single-line with `" ".join(value.split())` before writing to JSON.
-9. **Upstream catalogs can use multiple shapes.** FINOS CCC uses `control-families: [...]` in most catalogs but `controls: [...]` at the top level in `storage/object`. Any sync script must handle both or silently drop entire catalogs.
-10. **Foreign-prefix AR ids.** Upstream sometimes "imports" requirements from one catalog into another by keeping the original id prefix (e.g., `CCC.AuditLog.CN08.AR01` appearing under `CCC.Logging.CN03`). Prowler's compliance model requires unique ids within a catalog — rewrite the foreign id to fit the parent control: `CCC.AuditLog.CN08.AR01` (inside `CCC.Logging.CN03`) → `CCC.Logging.CN03.AR01`.
-11. **Genuine upstream id collisions.** Sometimes upstream has a real typo where two different requirements share the same id (e.g., `CCC.Core.CN14.AR02` defined twice for 30-day and 14-day backup variants). Renumber the second copy to the next free AR number. Preserve check mappings by matching on `(Section, frozenset(Applicability))` since the renumbered id won't match by id.
-12. **`COMPLIANCE_CLASS_MAP` in `export.py` uses `startswith` predicates** for all modern frameworks. Exact match (`name == "ccc_aws"`) is an anti-pattern — it was present for CCC until April 2026 and was the reason CCC couldn't have versioned variants.
-13. **Pre-validate every check id** against the per-provider inventory before writing the JSON. A typo silently creates an unreferenced check that will fail when findings try to map to it. The audit script MUST abort with stderr listing typos, not swallow them.
-14. **REPLACE is better than PATCH** for audit decisions. Encoding every mapping explicitly makes the audit reproducible and surfaces hidden assumptions from the legacy data. A PATCH system that adds/removes is too easy to forget.
-15. **When no check applies, MANUAL is correct.** Do not pad mappings with tangential checks "just in case". Prowler's compliance reports are meant to be actionable — padding them with noise breaks that. Honest manual reqs can be mapped later when new checks land.
-16. **UI groups by `Attributes[0].FamilyName` and `Attributes[0].Section`.** If FamilyName has inconsistent variants within the same JSON (e.g., "Logging & Monitoring" vs "Logging and Monitoring"), the UI renders them as separate categories. Section empty → the requirement falls into an orphan control with label "". Normalize before shipping.
-17. **Provider coverage is asymmetric.** AWS has dense coverage (~586 checks across 80+ services): in-transit encryption, IAM, database encryption, backup. Azure (~167 checks) and GCP (~102 checks) are thinner especially for in-transit encryption, mTLS, and ML/AI. Accept the asymmetry in mappings — don't force GCP parity where Prowler genuinely can't verify.
+1. **Universal first.** A new framework that starts as legacy needs 3 output
+ files + 3 registrations; the same framework as universal needs zero. Only
+ extend legacy families.
+2. **`Generic_Compliance_Requirement_Attribute` stays LAST** in the legacy
+ Attributes Union — Pydantic v1 tries members in order; Generic first
+ silently swallows every specific shape.
+3. **Pydantic v1 everywhere in `compliance_models.py`**
+ (`from pydantic.v1 import ...`). Don't mix in v2.
+4. **`get_check_compliance()` lives in
+ `prowler/lib/outputs/compliance/compliance_check.py`** and keys the dict
+ `f"{Framework}-{Version}"` only when Version is non-empty. Never ship
+ `Version: ""` — the key silently degrades to `"{Framework}"` and breaks
+ filters, tests and `--compliance`. For legacy files the filename version
+ substring must match `Version` (the CLI reads
+ `compliance_framework.split("_")[1]`).
+5. **`Compliance.get_bulk()` does not see top-level universal files** — only
+ `get_bulk_compliance_frameworks_universal()` does. Wire new code paths
+ against the universal loader.
+6. **Loader leniency differs**: legacy loader exits the process on a broken
+ JSON; universal loader logs and skips. A missing framework after your edit
+ usually means the universal loader dropped it — check the logs.
+7. **Circular import protection**: legacy table dispatcher files must not
+ import `Finding` (directly or transitively). Use `TYPE_CHECKING` or
+ function-local imports when a module needs both sides (that's how the
+ universal formatter does it).
+8. **Per-provider formatter files are the legacy convention** — but know the
+ exceptions before flagging them (iso27001 has no table file,
+ aws_well_architected has no per-provider files, cisa_scuba is
+ googleworkspace-only). CSV model field names are public API.
+9. **CSV output**: `;` delimiter, UPPERCASE headers. OCSF compliance output is
+ always generated for universal frameworks regardless of `--output-formats`.
+10. **`COMPLIANCE_CLASS_MAP` mixes predicate styles**: `startswith` for
+ multi-version families, exact `==` for singletons. When in doubt use
+ `startswith` — exact match blocked versioned CCC variants until 2026.
+11. **UI grouping is per-mapper, always on `attributes[0]`**: generic/cis →
+ `Section`/`SubSection`, iso → `Category`, ccc → `FamilyName`. Inconsistent
+ values (or empty Section) create orphan/duplicate tree branches — normalize
+ before shipping.
+12. **UI has a generic fallback** — an unregistered framework still renders.
+ A dedicated mapper/panel/icon is an upgrade, not a prerequisite.
+13. **Icon registration is ordered substring matching** in
+ `IconCompliance.tsx` — specific keywords before generic (`nist` before
+ `nis2`, `cisa` before `cis`, `aws` last).
+14. **API PDF pipeline is not `PDFConfig`-driven yet** — it has its own
+ `FRAMEWORK_REGISTRY` (5 frameworks). Don't assume adding `pdf_config` to a
+ JSON produces a PDF in Prowler App.
+15. **Pre-validate every check id** against the per-provider inventory before
+ writing JSON. No loader will catch a typo; the requirement just never
+ matches a finding.
+16. **REPLACE beats PATCH** for audit decisions — full explicit lists are
+ reproducible and surface legacy assumptions.
+17. **When no check applies, MANUAL is correct.** Don't pad mappings with
+ tangential checks; compliance reports must stay actionable.
+18. **Include every requirement of the source catalog**, automated or not —
+ compliance percentages use the full requirement count as denominator.
+19. **Provider coverage is asymmetric** (AWS dense; Azure/GCP thinner; new
+ providers minimal). Accept it — don't force parity Prowler can't verify.
+20. **Guardrail authoring**: strictest tolerated `Value`, exact `ConfigKey`
+ spelling, `Provider` mandatory in universal files, booleans as JSON
+ booleans. Malformed constraints are treated as satisfied — validate with
+ the config tests, don't trust silence.
---
## Useful One-Liners
```bash
-# Count requirements per service prefix (CCC, CIS sections, etc.)
-jq -r '.Requirements[].Id | split(".")[1]' prowler/compliance/aws/ccc_aws.json | sort | uniq -c
-
-# Find duplicate requirement IDs
+# Find duplicate requirement IDs (legacy | universal)
jq -r '.Requirements[].Id' file.json | sort | uniq -d
+jq -r '.requirements[].id' file.json | sort | uniq -d
-# Count manual requirements (no checks)
+# Count manual requirements (legacy | universal, per provider)
jq '[.Requirements[] | select((.Checks | length) == 0)] | length' file.json
+jq '[.requirements[] | select((.checks.aws // [] | length) == 0)] | length' file.json
-# List all unique check references in a framework
+# List unique check references (legacy | universal)
jq -r '.Requirements[].Checks[]' file.json | sort -u
+jq -r '.requirements[].checks[]? | .[]' file.json | sort -u
-# List all unique Sections (to spot inconsistency)
+# Providers covered by a universal framework
+jq '[.requirements[].checks | keys[]] | unique' file.json
+
+# Spot inconsistent grouping values (UI tree branches)
jq '[.Requirements[].Attributes[0].Section] | unique' file.json
-
-# List all unique FamilyNames (to spot inconsistency)
jq '[.Requirements[].Attributes[0].FamilyName] | unique' file.json
-# Diff requirement ids between two versions of the same framework
+# Requirements with config guardrails (empty arrays are truthy in jq — check length)
+jq '[.Requirements[] | select((.ConfigRequirements // []) | length > 0)] | length' file.json
+
+# Diff requirement ids between two versions
diff <(jq -r '.Requirements[].Id' a.json | sort) <(jq -r '.Requirements[].Id' b.json | sort)
-# Find where a check id is used across all frameworks
+# Where is a check mapped across all frameworks?
grep -rl "my_check_name" prowler/compliance/
-# Check if a Prowler check exists
+# Does a check exist?
find prowler/providers/aws/services -name "{check_id}.metadata.json"
-# Validate a JSON with Pydantic
-python -c "from prowler.lib.check.compliance_models import Compliance; print(Compliance.parse_file('prowler/compliance/aws/ccc_aws.json').Framework)"
+# Validate one file with the universal loader
+python -c "from prowler.lib.check.compliance_models import load_compliance_framework_universal as l; fw=l('prowler/compliance/aws/cis_7.0_aws.json'); print(fw.framework, len(fw.requirements))"
```
----
-
-## Best Practices
-
-1. **Requirement IDs**: Follow the original framework numbering exactly (e.g., "1.1", "A.5.1", "T1190", "ac_2_1")
-2. **Check Mapping**: Map to existing checks when possible. Use `Checks: []` for manual-only requirements — honest MANUAL beats padded coverage
-3. **Completeness**: Include all framework requirements, even those without automated checks
-4. **Version Control**: Include framework version in `Name` and `Version` fields. **Never leave `Version: ""`** — it breaks `get_check_compliance()` key format
-5. **File Naming**: Use format `{framework}_{version}_{provider}.json`
-6. **Validation**: Prowler validates JSON against Pydantic models at startup — invalid JSON will cause errors
-7. **Pre-validate check ids** against the provider's `*.metadata.json` inventory before every commit
-8. **Normalize FamilyName and Section** to avoid inconsistent UI tree branches
-9. **Register everywhere**: SDK model (if needed) → `compliance.py` dispatcher → `__main__.py` CLI writer → `export.py` API map → UI mapper. Skipping any layer results in silent failures
-10. **Audit, don't pad**: when reviewing mappings, apply the golden rule — the check's title/risk MUST literally describe what the requirement text says. Tangential relation doesn't count
-
## Commands
```bash
-# List available frameworks for a provider
prowler {provider} --list-compliance
-
-# Run scan with specific compliance framework
-prowler aws --compliance cis_5.0_aws
-
-# Run scan with multiple frameworks
-prowler aws --compliance cis_5.0_aws pci_4.0_aws
-
-# Output compliance report in multiple formats
-prowler aws --compliance cis_5.0_aws -M csv json html
+prowler {provider} --compliance cis_7.0_aws
+prowler aws --compliance cis_7.0_aws pci_4.0_aws
+prowler aws --compliance dora_2022_2554 # universal key = file basename
+prowler aws --list-compliance-requirements cis_7.0_aws
+prowler aws --compliance cis_7.0_aws -M csv json html
```
## Code References
### Layer 1 — SDK / Core
-- **Compliance Models:** `prowler/lib/check/compliance_models.py` (Pydantic v1 model tree)
-- **Compliance Processing / Linker:** `prowler/lib/check/compliance.py` (`get_check_compliance`, `update_checks_metadata_with_compliance`)
-- **Check Utils:** `prowler/lib/check/utils.py` (`list_compliance_modules`)
+
+- `prowler/lib/check/compliance_models.py` — legacy + universal model trees,
+ `Compliance_Requirement_ConfigConstraint`, all loaders and the
+ legacy→universal adapter
+- `prowler/lib/check/compliance.py` — `update_checks_metadata_with_compliance`
+- `prowler/lib/check/compliance_config_eval.py` — guardrail evaluation
+ (shared with the API)
+- `prowler/lib/outputs/compliance/compliance_check.py` — `get_check_compliance`
+- `prowler/lib/check/utils.py` — `list_compliance_modules`
### Layer 2 — JSON Catalogs
-- **Framework JSONs:** `prowler/compliance/{provider}/` (auto-discovered via directory walk)
+
+- `prowler/compliance/*.json` — universal, multi-provider (auto-discovered)
+- `prowler/compliance/{provider}/` — legacy, per-provider (auto-discovered)
### Layer 3 — Output Formatters
-- **Per-framework folders:** `prowler/lib/outputs/compliance/{framework}/`
-- **Shared base class:** `prowler/lib/outputs/compliance/compliance_output.py` (`ComplianceOutput` + `batch_write_data_to_file`)
-- **CLI table dispatcher:** `prowler/lib/outputs/compliance/compliance.py` (`display_compliance_table`)
-- **Finding model:** `prowler/lib/outputs/finding.py` (**do not import transitively from table dispatcher files — circular import**)
-- **CLI writer:** `prowler/__main__.py` (per-provider `elif compliance_name.startswith(...)` branches that instantiate per-provider classes)
+
+- `prowler/lib/outputs/compliance/universal/` — `universal_table.py`,
+ `universal_output.py`, `ocsf_compliance.py`
+- `prowler/lib/outputs/compliance/{framework}/` — legacy per-framework packages
+- `prowler/lib/outputs/compliance/compliance.py` —
+ `process_universal_compliance_frameworks`, `display_compliance_table`
+- `prowler/lib/outputs/compliance/compliance_output.py` — `ComplianceOutput`
+ base + CSV writer
+- `prowler/__main__.py` — universal processing + per-provider legacy writer
+ branches
### Layer 4 — API / UI
-- **API lazy loader:** `api/src/backend/api/compliance.py` (`LazyComplianceTemplate`, `LazyChecksMapping`)
-- **API export dispatcher:** `api/src/backend/tasks/jobs/export.py` (`COMPLIANCE_CLASS_MAP` with `startswith` predicates)
-- **UI framework router:** `ui/lib/compliance/compliance-mapper.ts`
-- **UI per-framework mapper:** `ui/lib/compliance/{framework}.tsx`
-- **UI detail panel:** `ui/components/compliance/compliance-custom-details/{framework}-details.tsx`
-- **UI types:** `ui/types/compliance.ts`
-- **UI icon:** `ui/components/icons/compliance/{framework}.svg` + registration in `IconCompliance.tsx`
+
+- `api/src/backend/api/compliance.py` — `LazyComplianceTemplate`,
+ `LazyChecksMapping`, cache warm-up
+- `api/src/backend/tasks/jobs/export.py` — `COMPLIANCE_CLASS_MAP`
+- `api/src/backend/tasks/jobs/scan.py` — `create_compliance_requirements`
+ (overview ingestion)
+- `api/src/backend/tasks/jobs/reports/` — PDF generators + `FRAMEWORK_REGISTRY`
+- `ui/lib/compliance/compliance-mapper.ts` — mapper routing + generic fallback
+- `ui/lib/compliance/{framework}.tsx` — per-framework mappers
+- `ui/components/compliance/compliance-custom-details/` — detail panels
+- `ui/types/compliance.ts` — attribute metadata types
+- `ui/components/icons/compliance/` + `IconCompliance.tsx` — icons (ordered)
### Tests
-- **Output formatter tests:** `tests/lib/outputs/compliance/{framework}/{framework}_{provider}_test.py`
-- **Shared fixtures:** `tests/lib/outputs/compliance/fixtures.py`
+
+- `tests/lib/check/universal_compliance_models_test.py` — includes the
+ parametrized `test_loads_as_universal` over every shipped JSON
+- `tests/lib/check/compliance_check_test.py`,
+ `compliance_config_eval_test.py`, `compliance_config_constraint_model_test.py`,
+ `compliance_config_requirements_data_test.py`, `mitre_config_requirements_test.py`
+- `tests/lib/outputs/compliance/` — per-framework + universal + dispatcher +
+ config-status coverage tests; shared `fixtures.py`
## Resources
-- **JSON Templates:** See [assets/](assets/) for framework JSON templates (cis, ens, iso27001, mitre_attack, prowler_threatscore, generic)
-- **Config-driven compliance sync** (any upstream-backed framework):
- - [assets/sync_framework.py](assets/sync_framework.py) — generic runner. Loads a YAML config, dynamically imports the declared parser, applies generic post-processing (id uniqueness safety net, `FamilyName` normalization, legacy check-mapping preservation with config-driven fallback keys), and writes the provider JSONs with Pydantic post-validation. Framework-agnostic — works for any compliance framework.
- - [assets/configs/ccc.yaml](assets/configs/ccc.yaml) — canonical config example (FINOS CCC v2025.10). Copy and adapt for new frameworks.
- - [assets/parsers/finos_ccc.py](assets/parsers/finos_ccc.py) — FINOS CCC YAML parser. Handles both upstream shapes (`control-families` and top-level `controls`), foreign-prefix AR rewriting, and genuine collision renumbering. Exposes `parse_upstream(config) -> list[dict]`.
- - [assets/parsers/](assets/parsers/) — add new parser modules here for unfamiliar upstream formats (NIST OSCAL JSON, MITRE STIX, CIS Benchmarks, etc.). Each parser is a `{name}.py` file implementing `parse_upstream(config) -> list[dict]` with guaranteed-unique ids.
-- **Reusable audit tooling** (added April 2026 after the FINOS CCC v2025.10 sync):
- - [assets/audit_framework_template.py](assets/audit_framework_template.py) — explicit REPLACE decision ledger with pre-validation against the per-provider inventory. Drop-in template for auditing any framework.
- - [assets/query_checks.py](assets/query_checks.py) — keyword/service/id query helper over `/tmp/checks_{provider}.json`.
- - [assets/dump_section.py](assets/dump_section.py) — dumps every AR for a given id prefix across all 3 providers with current check mappings.
- - [assets/build_inventory.py](assets/build_inventory.py) — generates `/tmp/checks_{provider}.json` from `*.metadata.json` files.
-- **Documentation:** See [references/compliance-docs.md](references/compliance-docs.md) for additional resources
-- **Related skill:** [prowler-compliance-review](../prowler-compliance-review/SKILL.md) — PR review checklist and validator script for compliance framework PRs
+- **Docs (source of truth for contributors)**:
+ `docs/developer-guide/security-compliance-framework.mdx` (both schemas,
+ guardrails, validation, PR process),
+ `docs/user-guide/compliance/tutorials/compliance.mdx`,
+ `docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx`
+- **Repo tooling** (`util/compliance/`): CSV→JSON generators
+ (`generate_json_from_csv/`), `ccc/from_yaml_to_json.py`,
+ `compliance_mapper/`, `threatscore/`
+- **Skill assets** ([assets/](assets/)):
+ - `sync_framework.py` + `configs/ccc.yaml` + `parsers/finos_ccc.py` —
+ config-driven upstream sync (Workflow A)
+ - `build_inventory.py`, `query_checks.py`, `dump_section.py`,
+ `audit_framework_template.py` — audit tooling (Workflow B)
+ - Legacy JSON templates: `cis_framework.json`, `ens_framework.json`,
+ `iso27001_framework.json`, `mitre_attack_framework.json`,
+ `prowler_threatscore_framework.json`, `generic_framework.json`
+- **References**:
+ [references/compliance-docs.md](references/compliance-docs.md) — model/loader
+ quick reference;
+ [references/check-mapping-reference.md](references/check-mapping-reference.md)
+ — curated requirement-text → checks mapping table + honest-MANUAL list
+- **Sister skill**:
+ [prowler-compliance-review](../prowler-compliance-review/SKILL.md) — PR
+ review checklist + `validate_compliance.py` (legacy-schema validator)
+- After editing this skill's frontmatter, run
+ `./skills/skill-sync/assets/sync.sh` to regenerate the AGENTS.md auto-invoke
+ tables.
diff --git a/skills/prowler-compliance/references/check-mapping-reference.md b/skills/prowler-compliance/references/check-mapping-reference.md
new file mode 100644
index 0000000000..cae9701ae7
--- /dev/null
+++ b/skills/prowler-compliance/references/check-mapping-reference.md
@@ -0,0 +1,78 @@
+# Audit Reference: Requirement Text → Prowler Checks
+
+Built from a real audit of 172 CCC ARs × 3 providers (April 2026). Use it to map
+CCC-style / NIST-style / ISO-style requirement text to the checks that actually
+verify them. Always re-validate every check id against the current inventory
+(`assets/build_inventory.py` + `assets/query_checks.py`) before using a row —
+checks get renamed and added over time.
+
+**Entries containing `*` are glob patterns, NOT literal check ids** (e.g.
+`iam_*_no_administrative_privileges`, `cloudwatch_log_metric_filter_*`,
+`*_minimum_tls_version_12`). Copied verbatim into a compliance JSON they map
+nothing — expand each pattern to the concrete check ids via
+`python skills/prowler-compliance/assets/query_checks.py <provider> <keywords>`
+before writing any mapping.
+
+| Requirement text | AWS checks | Azure checks | GCP checks |
+|---|---|---|---|
+| **TLS in transit enforced** | `cloudfront_distributions_https_enabled`, `s3_bucket_secure_transport_policy`, `elbv2_ssl_listeners`, `elbv2_insecure_ssl_ciphers`, `elb_ssl_listeners`, `elb_insecure_ssl_ciphers`, `opensearch_service_domains_https_communications_enforced`, `rds_instance_transport_encrypted`, `redshift_cluster_in_transit_encryption_enabled`, `elasticache_redis_cluster_in_transit_encryption_enabled`, `dynamodb_accelerator_cluster_in_transit_encryption_enabled`, `dms_endpoint_ssl_enabled`, `kafka_cluster_in_transit_encryption_enabled`, `transfer_server_in_transit_encryption_enabled`, `glue_database_connections_ssl_enabled`, `sns_subscription_not_using_http_endpoints` | `storage_secure_transfer_required_is_enabled`, `storage_ensure_minimum_tls_version_12`, `postgresql_flexible_server_enforce_ssl_enabled`, `mysql_flexible_server_ssl_connection_enabled`, `mysql_flexible_server_minimum_tls_version_12`, `sqlserver_recommended_minimal_tls_version`, `app_minimum_tls_version_12`, `app_ensure_http_is_redirected_to_https`, `app_ftp_deployment_disabled` | `cloudsql_instance_ssl_connections` (almost only option) |
+| **TLS 1.3 specifically** | Partial: `cloudfront_distributions_using_deprecated_ssl_protocols`, `elb*_insecure_ssl_ciphers`, `*_minimum_tls_version_12` | Partial: `*_minimum_tls_version_12` checks | None — accept as MANUAL |
+| **SSH / port 22 hardening** | `ec2_instance_port_ssh_exposed_to_internet`, `ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_22`, `ec2_networkacl_allow_ingress_tcp_port_22` | `network_ssh_internet_access_restricted`, `vm_linux_enforce_ssh_authentication` | `compute_firewall_ssh_access_from_the_internet_allowed`, `compute_instance_block_project_wide_ssh_keys_disabled`, `compute_project_os_login_enabled`, `compute_project_os_login_2fa_enabled` |
+| **mTLS (mutual TLS)** | `kafka_cluster_mutual_tls_authentication_enabled`, `apigateway_restapi_client_certificate_enabled` | `app_client_certificates_on` | None — MANUAL |
+| **Data at rest encrypted** | `s3_bucket_default_encryption`, `s3_bucket_kms_encryption`, `ec2_ebs_default_encryption`, `ec2_ebs_volume_encryption`, `rds_instance_storage_encrypted`, `rds_cluster_storage_encrypted`, `rds_snapshots_encrypted`, `dynamodb_tables_kms_cmk_encryption_enabled`, `redshift_cluster_encrypted_at_rest`, `neptune_cluster_storage_encrypted`, `documentdb_cluster_storage_encrypted`, `opensearch_service_domains_encryption_at_rest_enabled`, `kinesis_stream_encrypted_at_rest`, `firehose_stream_encrypted_at_rest`, `sns_topics_kms_encryption_at_rest_enabled`, `sqs_queues_server_side_encryption_enabled`, `efs_encryption_at_rest_enabled`, `athena_workgroup_encryption`, `glue_data_catalogs_metadata_encryption_enabled`, `backup_vaults_encrypted`, `backup_recovery_point_encrypted`, `cloudtrail_kms_encryption_enabled`, `cloudwatch_log_group_kms_encryption_enabled`, `eks_cluster_kms_cmk_encryption_in_secrets_enabled`, `sagemaker_notebook_instance_encryption_enabled`, `apigateway_restapi_cache_encrypted`, `kafka_cluster_encryption_at_rest_uses_cmk`, `dynamodb_accelerator_cluster_encryption_enabled`, `storagegateway_fileshare_encryption_enabled` | `storage_infrastructure_encryption_is_enabled`, `storage_ensure_encryption_with_customer_managed_keys`, `vm_ensure_attached_disks_encrypted_with_cmk`, `vm_ensure_unattached_disks_encrypted_with_cmk`, `sqlserver_tde_encryption_enabled`, `sqlserver_tde_encrypted_with_cmk`, `databricks_workspace_cmk_encryption_enabled`, `monitor_storage_account_with_activity_logs_cmk_encrypted` | `compute_instance_encryption_with_csek_enabled`, `dataproc_encrypted_with_cmks_disabled`, `bigquery_dataset_cmk_encryption`, `bigquery_table_cmk_encryption` |
+| **CMEK required (customer-managed keys)** | `kms_cmk_are_used` | `storage_ensure_encryption_with_customer_managed_keys`, `vm_ensure_attached_disks_encrypted_with_cmk`, `vm_ensure_unattached_disks_encrypted_with_cmk`, `sqlserver_tde_encrypted_with_cmk`, `databricks_workspace_cmk_encryption_enabled` | `bigquery_dataset_cmk_encryption`, `bigquery_table_cmk_encryption`, `dataproc_encrypted_with_cmks_disabled`, `compute_instance_encryption_with_csek_enabled` |
+| **Key rotation enabled** | `kms_cmk_rotation_enabled` | `keyvault_key_rotation_enabled`, `storage_key_rotation_90_days` | `kms_key_rotation_enabled` |
+| **MFA for UI access** | `iam_root_mfa_enabled`, `iam_root_hardware_mfa_enabled`, `iam_user_mfa_enabled_console_access`, `iam_user_hardware_mfa_enabled`, `iam_administrator_access_with_mfa`, `cognito_user_pool_mfa_enabled` | `entra_privileged_user_has_mfa`, `entra_non_privileged_user_has_mfa`, `entra_user_with_vm_access_has_mfa`, `entra_security_defaults_enabled` | `compute_project_os_login_2fa_enabled` |
+| **API access / credentials** | `iam_no_root_access_key`, `iam_user_no_setup_initial_access_key`, `apigateway_restapi_authorizers_enabled`, `apigateway_restapi_public_with_authorizer`, `apigatewayv2_api_authorizers_enabled` | `entra_conditional_access_policy_require_mfa_for_management_api`, `app_function_access_keys_configured`, `app_function_identity_is_configured` | `apikeys_api_restrictions_configured`, `apikeys_key_exists`, `apikeys_key_rotated_in_90_days` |
+| **Log all admin/config changes** | `cloudtrail_multi_region_enabled`, `cloudtrail_multi_region_enabled_logging_management_events`, `cloudtrail_cloudwatch_logging_enabled`, `cloudtrail_log_file_validation_enabled`, `cloudwatch_log_metric_filter_*`, `cloudwatch_changes_to_*_alarm_configured`, `config_recorder_all_regions_enabled` | `monitor_diagnostic_settings_exists`, `monitor_diagnostic_setting_with_appropriate_categories`, `monitor_alert_*` | `iam_audit_logs_enabled`, `logging_log_metric_filter_and_alert_for_*`, `logging_sink_created` |
+| **Log integrity (digital signatures)** | `cloudtrail_log_file_validation_enabled` (exact) | None | None |
+| **Public access denied** | `s3_bucket_public_access`, `s3_bucket_public_list_acl`, `s3_bucket_public_write_acl`, `s3_account_level_public_access_blocks`, `apigateway_restapi_public`, `awslambda_function_url_public`, `awslambda_function_not_publicly_accessible`, `rds_instance_no_public_access`, `rds_snapshots_public_access`, `ec2_securitygroup_allow_ingress_from_internet_to_all_ports`, `sns_topics_not_publicly_accessible`, `sqs_queues_not_publicly_accessible` | `storage_blob_public_access_level_is_disabled`, `storage_ensure_private_endpoints_in_storage_accounts`, `containerregistry_not_publicly_accessible`, `keyvault_private_endpoints`, `app_function_not_publicly_accessible`, `aks_clusters_public_access_disabled`, `network_http_internet_access_restricted` | `cloudstorage_bucket_public_access`, `compute_instance_public_ip`, `cloudsql_instance_public_ip`, `compute_firewall_*_access_from_the_internet_allowed` |
+| **IAM least privilege** | `iam_*_no_administrative_privileges`, `iam_policy_allows_privilege_escalation`, `iam_inline_policy_allows_privilege_escalation`, `iam_role_administratoraccess_policy`, `iam_group_administrator_access_policy`, `iam_user_administrator_access_policy`, `iam_policy_attached_only_to_group_or_roles`, `iam_role_cross_service_confused_deputy_prevention` | `iam_role_user_access_admin_restricted`, `iam_subscription_roles_owner_custom_not_created`, `iam_custom_role_has_permissions_to_administer_resource_locks` | `iam_sa_no_administrative_privileges`, `iam_no_service_roles_at_project_level`, `iam_role_kms_enforce_separation_of_duties`, `iam_role_sa_enforce_separation_of_duties` |
+| **Password policy** | `iam_password_policy_minimum_length_14`, `iam_password_policy_uppercase`, `iam_password_policy_lowercase`, `iam_password_policy_symbol`, `iam_password_policy_number`, `iam_password_policy_expires_passwords_within_90_days_or_less`, `iam_password_policy_reuse_24` | None | None |
+| **Credential rotation / unused** | `iam_rotate_access_key_90_days`, `iam_user_accesskey_unused`, `iam_user_console_access_unused` | None | `iam_sa_user_managed_key_rotate_90_days`, `iam_sa_user_managed_key_unused`, `iam_service_account_unused` |
+| **VPC / flow logs** | `vpc_flow_logs_enabled` | `network_flow_log_captured_sent`, `network_watcher_enabled`, `network_flow_log_more_than_90_days` | `compute_subnet_flow_logs_enabled` |
+| **Backup / DR / Multi-AZ** | `backup_vaults_exist`, `backup_plans_exist`, `backup_reportplans_exist`, `rds_instance_backup_enabled`, `rds_*_protected_by_backup_plan`, `rds_cluster_multi_az`, `neptune_cluster_backup_enabled`, `documentdb_cluster_backup_enabled`, `efs_have_backup_enabled`, `s3_bucket_cross_region_replication`, `dynamodb_table_protected_by_backup_plan` | `vm_backup_enabled`, `vm_sufficient_daily_backup_retention_period`, `storage_geo_redundant_enabled` | `cloudsql_instance_automated_backups`, `cloudstorage_bucket_log_retention_policy_lock`, `cloudstorage_bucket_sufficient_retention_period` |
+| **Access analysis / discovery** | `accessanalyzer_enabled`, `accessanalyzer_enabled_without_findings` | None specific | `iam_account_access_approval_enabled`, `iam_cloud_asset_inventory_enabled` |
+| **Object lock / retention** | `s3_bucket_object_lock`, `s3_bucket_object_versioning`, `s3_bucket_lifecycle_enabled`, `cloudtrail_bucket_requires_mfa_delete`, `s3_bucket_no_mfa_delete` | `storage_ensure_soft_delete_is_enabled`, `storage_blob_versioning_is_enabled`, `storage_ensure_file_shares_soft_delete_is_enabled` | `cloudstorage_bucket_log_retention_policy_lock`, `cloudstorage_bucket_soft_delete_enabled`, `cloudstorage_bucket_versioning_enabled`, `cloudstorage_bucket_sufficient_retention_period` |
+| **Uniform bucket-level access** | `s3_bucket_acl_prohibited` | `storage_account_key_access_disabled`, `storage_default_to_entra_authorization_enabled` | `cloudstorage_bucket_uniform_bucket_level_access` |
+| **Container vulnerability scanning** | `ecr_registry_scan_images_on_push_enabled`, `ecr_repositories_scan_vulnerabilities_in_latest_image` | `defender_container_images_scan_enabled`, `defender_container_images_resolved_vulnerabilities` | `artifacts_container_analysis_enabled`, `gcr_container_scanning_enabled` |
+| **WAF / rate limiting** | `wafv2_webacl_with_rules`, `waf_*_webacl_with_rules`, `wafv2_webacl_logging_enabled`, `waf_global_webacl_logging_enabled` | None | None |
+| **Deployment region restriction** | `organizations_scp_check_deny_regions` | None | None |
+| **Secrets automatic rotation** | `secretsmanager_automatic_rotation_enabled`, `secretsmanager_secret_rotated_periodically` | `keyvault_rbac_secret_expiration_set`, `keyvault_non_rbac_secret_expiration_set` | None |
+| **Certificate management** | `acm_certificates_expiration_check`, `acm_certificates_with_secure_key_algorithms`, `acm_certificates_transparency_logs_enabled` | `keyvault_key_expiration_set_in_non_rbac`, `keyvault_rbac_key_expiration_set`, `keyvault_non_rbac_secret_expiration_set` | None |
+| **GenAI guardrails / input/output filtering** | `bedrock_guardrail_prompt_attack_filter_enabled`, `bedrock_guardrail_sensitive_information_filter_enabled`, `bedrock_agent_guardrail_enabled`, `bedrock_model_invocation_logging_enabled`, `bedrock_api_key_no_administrative_privileges`, `bedrock_api_key_no_long_term_credentials` | None | None |
+| **ML dev environment security** | `sagemaker_notebook_instance_root_access_disabled`, `sagemaker_notebook_instance_without_direct_internet_access_configured`, `sagemaker_notebook_instance_vpc_settings_configured`, `sagemaker_models_vpc_settings_configured`, `sagemaker_training_jobs_vpc_settings_configured`, `sagemaker_training_jobs_network_isolation_enabled`, `sagemaker_training_jobs_volume_and_output_encryption_enabled` | None | None |
+| **Threat detection / anomalous behavior** | `cloudtrail_threat_detection_enumeration`, `cloudtrail_threat_detection_privilege_escalation`, `cloudtrail_threat_detection_llm_jacking`, `guardduty_is_enabled`, `guardduty_no_high_severity_findings` | None | None |
+| **Serverless private access** | `awslambda_function_inside_vpc`, `awslambda_function_not_publicly_accessible`, `awslambda_function_url_public` | `app_function_not_publicly_accessible` | None |
+
+## What Prowler Does NOT Cover (accept MANUAL honestly)
+
+Don't pad mappings for these — mark the requirement's checks empty and move on:
+
+- **TLS 1.3 version specifically** — Prowler verifies TLS is enforced, not always the exact version
+- **IANA port-protocol consistency** — no check for "protocol running on its assigned port"
+- **mTLS on most Azure/GCP services** — limited to App Service client certs on Azure, nothing on GCP
+- **Rate limiting** on monitoring endpoints, load balancers, serverless invocations, vector ingestion
+- **Session cookie expiry** (LB stickiness)
+- **HTTP header scrubbing** (Server, X-Powered-By)
+- **Certificate transparency verification for imports**
+- **Model version pinning, red teaming, AI quality review**
+- **Vector embedding validation, dimensional constraints, ANN vs exact search**
+- **Secret region replication** (cross-region residency)
+- **Lifecycle cleanup policies on container registries**
+- **Row-level / column-level security in data warehouses**
+- **Deployment region restriction on Azure/GCP** (AWS has `organizations_scp_check_deny_regions`, others don't)
+- **Cross-tenant alert silencing permissions**
+- **Field-level masking in logs**
+- **Managed view enforcement for database access**
+- **Automatic MFA delete on all S3 buckets** (only CloudTrail bucket variant exists for some frameworks — AWS has the generic `s3_bucket_no_mfa_delete` though)
+
+## Provider coverage asymmetry
+
+AWS has dense coverage (in-transit encryption, IAM, database encryption, backup,
+GenAI). Azure and GCP are thinner, especially for in-transit encryption, mTLS,
+and ML/AI. Accept the asymmetry in mappings — don't force GCP parity where
+Prowler genuinely can't verify. Newer providers (alibabacloud, oraclecloud,
+googleworkspace, okta, cloudflare, linode...) have far smaller inventories:
+always rebuild the inventory with `assets/build_inventory.py` before assuming
+a mapping exists.
diff --git a/skills/prowler-compliance/references/compliance-docs.md b/skills/prowler-compliance/references/compliance-docs.md
index 62d619953f..272aa10ef1 100644
--- a/skills/prowler-compliance/references/compliance-docs.md
+++ b/skills/prowler-compliance/references/compliance-docs.md
@@ -1,137 +1,154 @@
-# Compliance Framework Documentation
+# Compliance Framework Quick Reference
## Code References
-Key files for understanding and modifying compliance frameworks:
-
| File | Purpose |
|------|---------|
-| `prowler/lib/check/compliance_models.py` | Pydantic models defining attribute structures for each framework type |
-| `prowler/lib/check/compliance.py` | Core compliance processing logic |
-| `prowler/lib/check/utils.py` | Utility functions including `list_compliance_modules()` |
-| `prowler/lib/outputs/compliance/` | Framework-specific output generators |
-| `prowler/compliance/{provider}/` | JSON compliance framework definitions |
+| `prowler/lib/check/compliance_models.py` | Legacy + universal Pydantic (v1) model trees, config-constraint model, loaders, legacy→universal adapter |
+| `prowler/lib/check/compliance.py` | `update_checks_metadata_with_compliance()` (only) |
+| `prowler/lib/check/compliance_config_eval.py` | Shared `ConfigRequirements` guardrail evaluation (SDK outputs + API) |
+| `prowler/lib/outputs/compliance/compliance_check.py` | `get_check_compliance()` — per-finding `{Framework}-{Version}` → requirement ids |
+| `prowler/lib/check/utils.py` | `list_compliance_modules()` |
+| `prowler/lib/outputs/compliance/` | Output formatters (legacy per-framework + `universal/`) |
+| `prowler/compliance/*.json` | Universal multi-provider framework definitions |
+| `prowler/compliance/{provider}/` | Legacy per-provider framework definitions |
-## Attribute Model Classes
+## Attribute Model Classes (legacy schema)
-Each framework type has a specific Pydantic model in `compliance_models.py`:
+Registered in the `Compliance_Requirement.Attributes` Union, in this order
+(order is load-bearing; Generic must stay last):
-| Framework | Model Class |
+| Framework family | Model Class |
|-----------|-------------|
+| ASD Essential Eight | `ASDEssentialEight_Requirement_Attribute` |
| CIS | `CIS_Requirement_Attribute` |
-| ISO 27001 | `ISO27001_2013_Requirement_Attribute` |
| ENS | `ENS_Requirement_Attribute` |
-| MITRE ATT&CK | `Mitre_Requirement` (uses different structure) |
+| ISO 27001 | `ISO27001_2013_Requirement_Attribute` |
| AWS Well-Architected | `AWS_Well_Architected_Requirement_Attribute` |
| KISA ISMS-P | `KISA_ISMSP_Requirement_Attribute` |
| Prowler ThreatScore | `Prowler_ThreatScore_Requirement_Attribute` |
| CCC | `CCC_Requirement_Attribute` |
| C5 Germany | `C5Germany_Requirement_Attribute` |
-| Generic/Fallback | `Generic_Compliance_Requirement_Attribute` |
+| CSA CCM (legacy shape) | `CSA_CCM_Requirement_Attribute` |
+| DISA STIG (Okta IDaaS) | `STIG_Requirement_Attribute` |
+| Generic/Fallback (NIST, PCI, GDPR, HIPAA, SOC2, FedRAMP, ...) | `Generic_Compliance_Requirement_Attribute` |
-## How Compliance Frameworks are Loaded
+MITRE ATT&CK uses the separate `Mitre_Requirement` model with per-provider
+`Mitre_Requirement_Attribute_{AWS,Azure,GCP}` attribute classes.
-1. `Compliance.get_bulk(provider)` is called at startup
-2. Scans `prowler/compliance/{provider}/` for `.json` files
-3. Each file is parsed using `load_compliance_framework()`
-4. Pydantic validates against `Compliance` model
-5. Framework is stored in dictionary with filename (without `.json`) as key
+`Compliance_Requirement_ConfigConstraint` models each `ConfigRequirements` /
+`config_requirements` entry (`Check`, `ConfigKey`, `Operator`, `Value`,
+optional `Provider`) with load-time operator/value type validation.
+
+## Universal Schema Models
+
+| Model | Purpose |
+|-------|---------|
+| `ComplianceFramework` | Top-level container (`framework`, `name`, `version`, `requirements`, `attributes_metadata`, `outputs`); validates attributes against metadata at load |
+| `UniversalComplianceRequirement` | Flat `attributes: dict`, `checks: dict[provider, list]`, `config_requirements`, MITRE extras |
+| `AttributeMetadata` | Per-attribute schema descriptor (key/label/type/enum/required/`enum_display`/`enum_order`/`output_formats`) |
+| `OutputsConfig` → `TableConfig` | CLI table rendering (`group_by`, `split_by`, `scoring`, `labels`) — consumed by `universal_table.py` |
+| `OutputsConfig` → `PDFConfig` (+ `ChartConfig`, `ScoringFormula`, `I18nLabels`, ...) | Declarative PDF config — modeled but **not yet consumed** by the API PDF pipeline (it uses its own `FRAMEWORK_REGISTRY`) |
+
+## How Frameworks Are Loaded
+
+Two entry points — they see different files:
+
+1. **Legacy**: `Compliance.get_bulk(provider)` scans only
+ `prowler/compliance/{provider}/` (exact provider-segment match) plus
+ external JSONs from the `prowler.compliance` entry-point group. Invalid
+ built-in file → `logger.critical` + `sys.exit(1)`
+ (`load_compliance_framework`, `fatal=True`).
+2. **Universal**: `get_bulk_compliance_frameworks_universal(provider)` scans
+ the top-level `prowler/compliance/` **and** every provider subdirectory,
+ plus the `prowler.compliance.universal` entry-point group (built-ins win
+ collisions). Legacy files are adapted via `adapt_legacy_to_universal()`
+ (flattens `Attributes[0]` into a dict, wraps `Checks` as
+ `{provider: [...]}`, infers `attributes_metadata` from the matched Pydantic
+ class). Invalid file → logged and **skipped**
+ (`load_compliance_framework_universal` returns `None`).
+
+The framework key in both bulk dicts is the JSON basename without `.json` —
+that's also the `--compliance` CLI key.
## How Checks Map to Compliance
-1. After loading, `update_checks_metadata_with_compliance()` is called
-2. For each check, it finds all compliance requirements that reference it
-3. Compliance info is attached to `CheckMetadata.Compliance` list
-4. During output, `get_check_compliance()` retrieves mappings per finding
+1. `update_checks_metadata_with_compliance()` attaches, per check, every
+ framework requirement that references it (`CheckMetadata.Compliance`).
+2. During output, `get_check_compliance()`
+ (`prowler/lib/outputs/compliance/compliance_check.py`) returns the
+ per-finding dict `{"{Framework}-{Version}": [requirement_ids]}` — the
+ `-{Version}` suffix only exists when `Version` is non-empty.
+3. `ConfigRequirements` guardrails are evaluated by
+ `evaluate_config_constraints()` (`compliance_config_eval.py`); a violated
+ constraint forces FAIL and prepends
+ `Configuration not valid for this requirement.` to `status_extended` in
+ every output format.
-## File Naming Convention
+## File Naming Conventions
-```
-{framework}_{version}_{provider}.json
+```text
+prowler/compliance/{framework}_{version}.json # universal
+prowler/compliance/{provider}/{framework}_{version}_{provider}.json # legacy
```
-Examples:
-- `cis_5.0_aws.json`
-- `iso27001_2022_azure.json`
-- `mitre_attack_gcp.json`
-- `ens_rd2022_aws.json`
-- `nist_800_53_revision_5_aws.json`
+Examples: `dora_2022_2554.json`, `cis_controls_8.1.json`, `cis_7.0_aws.json`,
+`iso27001_2022_azure.json`, `okta_idaas_stig_v1r2_okta.json`,
+`cisa_scuba_0.6_googleworkspace.json`, `ccc_aws.json` (unversioned only when
+the framework has no versioning). For legacy files the version substring in
+the filename must equal `Version`.
-## Validation
+## Validation Summary
-Prowler validates compliance JSON at startup. Invalid files cause:
-- `ValidationError` logged with details
-- Application exit with error code
+- **Load time (universal)**: `attributes_metadata` root validator — required
+ keys, unknown-key drift guard, enums, int/float/bool types. Omit the
+ metadata and nothing is validated.
+- **Load time (legacy)**: Pydantic attribute-class matching; a shape matching
+ no specific class silently falls through to Generic.
+- **Never validated at load**: check-id existence. Cross-check manually
+ (see SKILL.md → Validation).
+- **Test suite**: `tests/lib/check/universal_compliance_models_test.py::test_loads_as_universal`
+ is parametrized over every shipped JSON (top-level + per-provider).
+- **CI**: `.github/workflows/pr-check-compliance-mapping.yml` flags new checks
+ not mapped in any framework (`needs-compliance-review` label; opt out with
+ `no-compliance-check`).
+- **Pre-commit**: `check-json` + `pretty-format-json` only (syntax/format, no
+ semantics).
+- **Manual**: `skills/prowler-compliance-review/assets/validate_compliance.py`
+ (legacy schema only).
-Common validation errors:
-- Missing required fields (`Id`, `Description`, `Checks`, `Attributes`)
-- Invalid enum values (e.g., `Profile` must be "Level 1" or "Level 2" for CIS)
-- Type mismatches (e.g., `Checks` must be array of strings)
+## Repo Tooling (`util/compliance/`)
-## Adding a New Framework
-
-1. Create JSON file in `prowler/compliance/{provider}/`
-2. Use appropriate attribute model (see table above)
-3. Map existing checks to requirements via `Checks` array
-4. Use empty `Checks: []` for manual-only requirements
-5. Test with `prowler {provider} --list-compliance` to verify loading
-6. Run `prowler {provider} --compliance {framework_name}` to test execution
-
-## Templates
-
-See `assets/` directory for example templates:
-- `cis_framework.json` - CIS Benchmark template
-- `iso27001_framework.json` - ISO 27001 template
-- `ens_framework.json` - ENS (Spain) template
-- `mitre_attack_framework.json` - MITRE ATT&CK template
-- `prowler_threatscore_framework.json` - Prowler ThreatScore template
-- `generic_framework.json` - Generic/custom framework template
+| Tool | Purpose |
+|------|---------|
+| `util/compliance/generate_json_from_csv/*.py` | CSV→JSON generators (CIS 1.5, CIS 2.0 GCP, CIS 1.0 GitHub, CIS 4.0 M365, ENS, ThreatScore) |
+| `util/compliance/ccc/from_yaml_to_json.py` | FINOS CCC YAML→JSON converter |
+| `util/compliance/compliance_mapper/` | Compliance mapper (see its README) |
+| `util/compliance/threatscore/get_prowler_threatscore_from_generic_output.py` | Derive ThreatScore from generic output |
## Prowler ThreatScore Details
-Prowler ThreatScore is a custom security scoring framework that calculates an overall security posture score based on:
+Custom Prowler scoring framework. Pillars / ID prefixes: `1.x.x` IAM, `2.x.x`
+Attack Surface, `3.x.x` Logging and Monitoring, `4.x.x` Encryption.
-### Four Pillars
-1. **IAM (Identity and Access Management)**
- - SubSections: Authentication, Authorization, Credentials Management
-
-2. **Attack Surface**
- - SubSections: Network Exposure, Storage Exposure, Service Exposure
-
-3. **Logging and Monitoring**
- - SubSections: Audit Logging, Threat Detection, Alerting
-
-4. **Encryption**
- - SubSections: Data at Rest, Data in Transit
-
-### Scoring Algorithm
-The ThreatScore uses `LevelOfRisk` and `Weight` to calculate severity:
-
-| LevelOfRisk | Weight | Example Controls |
-|-------------|--------|------------------|
-| 5 (Critical) | 1000 | Root MFA, No root access keys, Public S3 buckets |
-| 4 (High) | 100 | User MFA, Public EC2, GuardDuty enabled |
-| 3 (Medium) | 10 | Password policies, EBS encryption, CloudTrail |
-| 2 (Low) | 1-10 | Best practice recommendations |
-| 1 (Info) | 1 | Informational controls |
-
-### ID Numbering Convention
-- `1.x.x` - IAM controls
-- `2.x.x` - Attack Surface controls
-- `3.x.x` - Logging and Monitoring controls
-- `4.x.x` - Encryption controls
+Scoring: `LevelOfRisk` 1–5 (5=critical) × `Weight` (values in the shipped
+catalogs: 1000 critical / 100 high / 8–10 standard / 1 low). Available for
+aws, azure, gcp, kubernetes, m365, alibabacloud.
## External Resources
-### Official Framework Documentation
- [CIS Benchmarks](https://www.cisecurity.org/cis-benchmarks)
-- [ISO 27001:2022](https://www.iso.org/standard/27001)
+- [CIS Critical Security Controls](https://www.cisecurity.org/controls)
+- [ISO 27001](https://www.iso.org/standard/27001)
- [NIST 800-53](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final)
- [NIST CSF](https://www.nist.gov/cyberframework)
- [PCI DSS](https://www.pcisecuritystandards.org/)
- [MITRE ATT&CK](https://attack.mitre.org/)
- [ENS (Spain)](https://www.ccn-cert.cni.es/es/ens.html)
-
-### Prowler Documentation
-- [Prowler Docs - Compliance](https://docs.prowler.com/projects/prowler-open-source/en/latest/)
-- [Prowler GitHub](https://github.com/prowler-cloud/prowler)
+- [FINOS CCC](https://github.com/finos/common-cloud-controls)
+- [CSA CCM](https://cloudsecurityalliance.org/research/cloud-controls-matrix)
+- [DORA (EU 2022/2554)](https://eur-lex.europa.eu/eli/reg/2022/2554/oj)
+- [ASD Essential Eight](https://www.cyber.gov.au/resources-business-and-government/essential-cybersecurity/essential-eight)
+- [CISA SCuBA](https://www.cisa.gov/resources-tools/services/secure-cloud-business-applications-scuba-project)
+- [DISA STIGs](https://public.cyber.mil/stigs/)
+- [Prowler Docs — Compliance developer guide](https://docs.prowler.com/developer-guide/security-compliance-framework)
diff --git a/skills/prowler-docs/SKILL.md b/skills/prowler-docs/SKILL.md
index 41a97f5ff9..4c4c64967f 100644
--- a/skills/prowler-docs/SKILL.md
+++ b/skills/prowler-docs/SKILL.md
@@ -104,7 +104,7 @@ Reference without articles:
## Documentation Structure
-```
+```text
docs/
├── getting-started/
├── tutorials/
diff --git a/skills/prowler-mcp/SKILL.md b/skills/prowler-mcp/SKILL.md
index af3c597771..704acf8553 100644
--- a/skills/prowler-mcp/SKILL.md
+++ b/skills/prowler-mcp/SKILL.md
@@ -19,7 +19,7 @@ The Prowler MCP Server uses three sub-servers with prefixed namespacing:
| Sub-Server | Prefix | Auth | Purpose |
|------------|--------|------|---------|
-| Prowler App | `prowler_app_*` | Required | Cloud management tools |
+| Prowler | `prowler_*` | Required | Prowler Cloud, Private Cloud & Local Server management tools |
| Prowler Hub | `prowler_hub_*` | No | Security checks catalog |
| Prowler Docs | `prowler_docs_*` | No | Documentation search |
@@ -27,7 +27,7 @@ For complete architecture, patterns, and examples, see [docs/developer-guide/mcp
---
-## Critical Rules (Prowler App Only)
+## Critical Rules (Prowler Tools Only)
### Tool Implementation
@@ -56,7 +56,7 @@ Use `@mcp.tool()` decorator directly—no BaseTool or models required.
---
-## Quick Reference: New Prowler App Tool
+## Quick Reference: New Prowler Tool
1. Create tool class in `prowler_app/tools/` extending `BaseTool`
2. Create models in `prowler_app/models/` using `MinimalSerializerMixin`
@@ -64,7 +64,7 @@ Use `@mcp.tool()` decorator directly—no BaseTool or models required.
---
-## QA Checklist (Prowler App)
+## QA Checklist (Prowler Tools)
- [ ] Tool docstrings describe LLM-relevant behavior
- [ ] Models use `MinimalSerializerMixin`
diff --git a/skills/prowler-pr/SKILL.md b/skills/prowler-pr/SKILL.md
index e147d37fbe..ee18f7205f 100644
--- a/skills/prowler-pr/SKILL.md
+++ b/skills/prowler-pr/SKILL.md
@@ -56,7 +56,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
- [ ] Review if code is being documented following https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
- [ ] Review if backport is needed.
- [ ] Review if is needed to change the Readme.md
-- [ ] Ensure new entries are added to CHANGELOG.md, if applicable.
+- [ ] Ensure a changelog fragment is added under <component>/changelog.d/, if applicable.
#### SDK/CLI
- Are there new checks included in this PR? Yes / No
@@ -67,7 +67,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
- [ ] Screenshots/Video - Mobile (X < 640px)
- [ ] Screenshots/Video - Tablet (640px > X < 1024px)
- [ ] Screenshots/Video - Desktop (X > 1024px)
-- [ ] Ensure new entries are added to ui/CHANGELOG.md
+- [ ] Ensure a changelog fragment is added under ui/changelog.d/
#### API (if applicable)
- [ ] All issue/task requirements work as expected on the API
@@ -77,7 +77,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
- [ ] Any other relevant evidence of the implementation (if applicable)
- [ ] Verify if API specs need to be regenerated.
- [ ] Check if version updates are required.
-- [ ] Ensure new entries are added to api/CHANGELOG.md
+- [ ] Ensure a changelog fragment is added under api/changelog.d/
### License
@@ -86,12 +86,12 @@ By submitting this pull request, I confirm that my contribution is made under th
## Component-Specific Rules
-| Component | CHANGELOG | Extra Checks |
-|-----------|-----------|--------------|
-| SDK | `prowler/CHANGELOG.md` | New checks → permissions update? |
-| API | `api/CHANGELOG.md` | API specs, version bump, endpoint output, EXPLAIN ANALYZE, performance |
-| UI | `ui/CHANGELOG.md` | Screenshots for Mobile/Tablet/Desktop |
-| MCP | `mcp_server/CHANGELOG.md` | N/A |
+| Component | Changelog fragment | Extra Checks |
+|-----------|--------------------|--------------|
+| SDK | `prowler/changelog.d/` | New checks → permissions update? |
+| API | `api/changelog.d/` | API specs, version bump, endpoint output, EXPLAIN ANALYZE, performance |
+| UI | `ui/changelog.d/` | Screenshots for Mobile/Tablet/Desktop |
+| MCP | `mcp_server/changelog.d/` | N/A |
## Commands
@@ -128,7 +128,7 @@ Follow conventional commits:
1. ✅ All tests pass locally
2. ✅ Linting passes (`make lint` or component-specific)
-3. ✅ CHANGELOG updated (if applicable)
+3. ✅ Changelog fragment added (if applicable)
4. ✅ Branch is up to date with main
5. ✅ Commits are clean and descriptive
diff --git a/skills/prowler-provider/SKILL.md b/skills/prowler-provider/SKILL.md
index 5b93ddd479..8042cd9f5a 100644
--- a/skills/prowler-provider/SKILL.md
+++ b/skills/prowler-provider/SKILL.md
@@ -25,7 +25,7 @@ Use this skill when:
Every provider MUST follow this structure:
-```
+```text
prowler/providers/{provider}/
├── __init__.py
├── {provider}_provider.py # Main provider class
diff --git a/skills/prowler-readme-table/SKILL.md b/skills/prowler-readme-table/SKILL.md
index d6f9c6e780..6cea125ca0 100644
--- a/skills/prowler-readme-table/SKILL.md
+++ b/skills/prowler-readme-table/SKILL.md
@@ -34,7 +34,7 @@ python3 prowler-cli.py <provider> --list-<metric>
The CLI output ends with a summary line like:
-```
+```text
There are 572 available checks.
There is 1 available Compliance Framework.
```
diff --git a/skills/prowler-sdk-check/SKILL.md b/skills/prowler-sdk-check/SKILL.md
index 13ae895da4..1901e996d4 100644
--- a/skills/prowler-sdk-check/SKILL.md
+++ b/skills/prowler-sdk-check/SKILL.md
@@ -16,7 +16,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## Check Structure
-```
+```text
prowler/providers/{provider}/services/{service}/{check_name}/
├── __init__.py
├── {check_name}.py
@@ -90,7 +90,7 @@ See `prowler-test-sdk` skill for test patterns (PASS, FAIL, no resources, error
## Check Naming Convention
-```
+```text
{service}_{resource}_{security_control}
```
diff --git a/skills/prowler-test-api/SKILL.md b/skills/prowler-test-api/SKILL.md
index 6395b562dd..2b5231104a 100644
--- a/skills/prowler-test-api/SKILL.md
+++ b/skills/prowler-test-api/SKILL.md
@@ -28,10 +28,10 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## 1. Fixture Dependency Chain
-```
+```text
create_test_user (session) ─► tenants_fixture (function) ─► authenticated_client
│
- └─► providers_fixture ─► scans_fixture ─► findings_fixture
+ └─► aws_provider ─► scans_fixture ─► findings_fixture
```
### Key Fixtures
@@ -40,8 +40,12 @@ create_test_user (session) ─► tenants_fixture (function) ─► authenticate
|---------|-------------|
| `create_test_user` | Session user (`dev@prowler.com`) |
| `tenants_fixture` | 3 tenants: [0],[1] have membership, [2] isolated |
-| `authenticated_client` | JWT client for tenant[0] |
-| `providers_fixture` | 9 providers in tenant[0] |
+| `authenticated_client` | Django test client with JWT for tenant[0] |
+| `authenticated_client_for_tenant_factory` | Creates a Django test client with JWT for a specific user and tenant |
+| `provider_factory` | Creates one validated provider with provider-specific defaults |
+| `aws_provider` | 1 AWS provider in tenant[0] |
+| `aws_provider_pair` | 2 AWS providers in tenant[0] |
+| `all_provider_types_fixture` | 1 provider for every supported provider type |
| `tasks_fixture` | 2 Celery tasks with TaskResult |
### RBAC Fixtures
@@ -52,6 +56,14 @@ create_test_user (session) ─► tenants_fixture (function) ─► authenticate
| `authenticated_client_rbac_noroles` | Membership but NO roles |
| `authenticated_client_no_permissions_rbac` | All permissions = False |
+Use `authenticated_client` for normal view behavior tests. It uses a cheap JWT
+and still runs the real request authentication path. Use serializer-generated
+JWTs or API-key clients only when the test is specifically about token
+obtain/refresh, invalid tokens, expired tokens, tenant switching by token, API
+keys, or unauthenticated 401 behavior. Use
+`authenticated_client_for_tenant_factory` when a test needs a cheap JWT client
+for a different user or tenant.
+
---
## 2. JSON:API Requests
diff --git a/skills/prowler-test-api/assets/api_test.py b/skills/prowler-test-api/assets/api_test.py
index 0b70cd599d..e0ca148662 100644
--- a/skills/prowler-test-api/assets/api_test.py
+++ b/skills/prowler-test-api/assets/api_test.py
@@ -22,12 +22,12 @@ from api.rls import Tenant
class TestProviderViewSet:
"""Example API tests for Provider endpoints."""
- def test_list_providers(self, authenticated_client, providers_fixture):
+ def test_list_providers(self, authenticated_client, aws_provider):
"""GET list returns all providers for authenticated tenant."""
response = authenticated_client.get(reverse("provider-list"))
assert response.status_code == status.HTTP_200_OK
- assert len(response.json()["data"]) == len(providers_fixture)
+ assert len(response.json()["data"]) == 1
def test_create_provider(self, authenticated_client):
"""POST with JSON:API format creates provider."""
@@ -49,9 +49,9 @@ class TestProviderViewSet:
assert response.status_code == status.HTTP_201_CREATED
assert response.json()["data"]["attributes"]["uid"] == "123456789012"
- def test_update_provider(self, authenticated_client, providers_fixture):
+ def test_update_provider(self, authenticated_client, aws_provider):
"""PATCH with JSON:API format updates provider."""
- provider = providers_fixture[0]
+ provider = aws_provider
payload = {
"data": {
@@ -95,7 +95,7 @@ class TestRLSIsolation:
assert response.status_code == status.HTTP_404_NOT_FOUND
def test_list_excludes_other_tenants(
- self, authenticated_client, providers_fixture, tenants_fixture
+ self, authenticated_client, aws_provider, tenants_fixture
):
"""List endpoints only return resources from user's tenants."""
# Create provider in isolated tenant
@@ -109,8 +109,8 @@ class TestRLSIsolation:
response = authenticated_client.get(reverse("provider-list"))
assert response.status_code == status.HTTP_200_OK
- # Should only see providers_fixture (9 providers in tenant[0])
- assert len(response.json()["data"]) == len(providers_fixture)
+ # Should only see the AWS provider in tenant[0]
+ assert len(response.json()["data"]) == 1
@pytest.mark.django_db
@@ -136,7 +136,7 @@ class TestRBACPermissions:
response = authenticated_client_rbac_noroles.get(reverse("user-list"))
assert response.status_code == status.HTTP_403_FORBIDDEN
- def test_admin_sees_all(self, authenticated_client_rbac, providers_fixture):
+ def test_admin_sees_all(self, authenticated_client_rbac, aws_provider):
"""Admin with unlimited_visibility=True sees all providers."""
response = authenticated_client_rbac.get(reverse("provider-list"))
assert response.status_code == status.HTTP_200_OK
@@ -153,11 +153,11 @@ class TestAsyncOperations:
mock_delete_task,
mock_task_get,
authenticated_client,
- providers_fixture,
+ aws_provider,
tasks_fixture,
):
"""DELETE returns 202 Accepted with Content-Location header."""
- provider = providers_fixture[0]
+ provider = aws_provider
prowler_task = tasks_fixture[0]
# Mock the Celery task
@@ -184,11 +184,11 @@ class TestAsyncOperations:
mock_scan_task,
mock_task_get,
authenticated_client,
- providers_fixture,
+ aws_provider,
tasks_fixture,
):
"""POST to scan trigger returns 202 with task location."""
- provider = providers_fixture[0]
+ provider = aws_provider
prowler_task = tasks_fixture[0]
task_mock = Mock()
@@ -208,9 +208,9 @@ class TestAsyncOperations:
class TestJSONAPIResponses:
"""Example JSON:API response handling."""
- def test_read_single_resource(self, authenticated_client, providers_fixture):
+ def test_read_single_resource(self, authenticated_client, aws_provider):
"""Read data from single resource response."""
- provider = providers_fixture[0]
+ provider = aws_provider
response = authenticated_client.get(
reverse("provider-detail", kwargs={"pk": provider.id})
)
@@ -222,12 +222,12 @@ class TestJSONAPIResponses:
assert resource_id == str(provider.id)
assert attrs["provider"] == provider.provider
- def test_read_list_response(self, authenticated_client, providers_fixture):
+ def test_read_list_response(self, authenticated_client, aws_provider):
"""Read data from list response."""
response = authenticated_client.get(reverse("provider-list"))
items = response.json()["data"]
- assert len(items) == len(providers_fixture)
+ assert len(items) == 1
def test_read_relationships(self, authenticated_client, scans_fixture):
"""Read relationship data."""
@@ -262,9 +262,9 @@ class TestJSONAPIResponses:
class TestSoftDelete:
"""Example soft-delete manager tests."""
- def test_objects_excludes_soft_deleted(self, providers_fixture):
+ def test_objects_excludes_soft_deleted(self, aws_provider):
"""Default manager excludes soft-deleted records."""
- provider = providers_fixture[0]
+ provider = aws_provider
provider.is_deleted = True
provider.save()
@@ -284,12 +284,12 @@ class TestSoftDelete:
class TestCeleryTaskLogic:
"""Example: Testing Celery task logic directly with apply()."""
- def test_task_logic_directly(self, tenants_fixture, providers_fixture):
+ def test_task_logic_directly(self, tenants_fixture, aws_provider):
"""Use apply() for synchronous execution without Celery worker."""
from tasks.tasks import check_provider_connection_task
tenant = tenants_fixture[0]
- provider = providers_fixture[0]
+ provider = aws_provider
# Execute task synchronously (no broker needed)
result = check_provider_connection_task.apply(
@@ -328,12 +328,12 @@ class TestSetTenantDecorator:
"""Example: Testing @set_tenant decorator behavior."""
@patch("api.decorators.connection")
- def test_sets_rls_context(self, mock_conn, tenants_fixture, providers_fixture):
+ def test_sets_rls_context(self, mock_conn, tenants_fixture, aws_provider):
"""Verify @set_tenant sets RLS context via SET_CONFIG_QUERY."""
from tasks.tasks import check_provider_connection_task
tenant = tenants_fixture[0]
- provider = providers_fixture[0]
+ provider = aws_provider
# Call task with tenant_id - decorator sets RLS and pops it
check_provider_connection_task.apply(
@@ -349,13 +349,13 @@ class TestBeatScheduling:
"""Example: Testing Beat scheduled task creation."""
@patch("tasks.beat.perform_scheduled_scan_task.apply_async")
- def test_schedule_provider_scan(self, mock_apply, providers_fixture):
+ def test_schedule_provider_scan(self, mock_apply, aws_provider):
"""Verify periodic task is created with correct settings."""
from django_celery_beat.models import PeriodicTask
from tasks.beat import schedule_provider_scan
- provider = providers_fixture[0]
+ provider = aws_provider
mock_apply.return_value = Mock(id="task-123")
schedule_provider_scan(provider)
diff --git a/skills/prowler-test-api/references/test-api-docs.md b/skills/prowler-test-api/references/test-api-docs.md
index 11f866bd85..02d450e788 100644
--- a/skills/prowler-test-api/references/test-api-docs.md
+++ b/skills/prowler-test-api/references/test-api-docs.md
@@ -14,7 +14,7 @@
## Fixture Dependency Graph
-```
+```text
create_test_user (session)
│
└─► tenants_fixture (function)
@@ -24,7 +24,7 @@ create_test_user (session)
│ └─► authenticated_client
│ └─► (most API tests use this)
│
- ├─► providers_fixture
+ ├─► aws_provider
│ └─► scans_fixture
│ └─► findings_fixture
│
@@ -102,12 +102,20 @@ Authentication tests:
```python
@pytest.mark.django_db
class TestProviderViewSet:
- def test_list(self, authenticated_client, providers_fixture):
- # authenticated_client has JWT for tenant[0]
- # providers_fixture has 9 providers in tenant[0]
+ def test_list(self, authenticated_client, aws_provider):
+ # authenticated_client is a Django test client with JWT for tenant[0]
+ # aws_provider creates one validated AWS provider in tenant[0]
...
```
+Use serializer-generated JWTs or API-key clients for authentication behavior
+tests only: token obtain/refresh, invalid or expired tokens, token-scoped tenant
+switching, API keys, and unauthenticated 401 responses. Regular view tests
+should use `authenticated_client` so they still exercise `request.user`,
+`request.auth["tenant_id"]`, RLS, and RBAC without paying token serializer cost.
+Use `authenticated_client_for_tenant_factory` when a test needs the same cheap
+JWT path for a different user or tenant.
+
### RBAC Tests
```python
diff --git a/skills/prowler-test-sdk/SKILL.md b/skills/prowler-test-sdk/SKILL.md
index a9e5b3c9fe..ccf9ecdf03 100644
--- a/skills/prowler-test-sdk/SKILL.md
+++ b/skills/prowler-test-sdk/SKILL.md
@@ -265,7 +265,7 @@ from tests.providers.kubernetes.kubernetes_fixtures import set_mocked_kubernetes
## Test File Structure
-```
+```text
tests/providers/{provider}/services/{service}/
├── {service}_service_test.py # Service tests
└── {check_name}/
diff --git a/skills/prowler-test-ui/SKILL.md b/skills/prowler-test-ui/SKILL.md
index 558525932d..2cd583eb32 100644
--- a/skills/prowler-test-ui/SKILL.md
+++ b/skills/prowler-test-ui/SKILL.md
@@ -19,7 +19,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## Prowler UI Test Structure
-```
+```text
ui/tests/
├── base-page.ts # Prowler-specific base page
├── helpers.ts # Prowler test utilities
@@ -35,13 +35,13 @@ ui/tests/
**⚠️ ALWAYS verify BEFORE completing any E2E task:**
-### When CREATING new tests:
+### When CREATING new tests
- [ ] `{page-name}-page.ts` - Page Object created/updated
- [ ] `{page-name}.spec.ts` - Tests added with correct tags (@TEST-ID)
- [ ] `{page-name}.md` - Documentation created with ALL test cases
- [ ] Test IDs in `.md` match tags in `.spec.ts`
-### When MODIFYING existing tests:
+### When MODIFYING existing tests
- [ ] `{page-name}.md` MUST be updated if:
- Test cases were added/removed
- Test flow changed (steps)
@@ -49,7 +49,7 @@ ui/tests/
- Tags or priorities changed
- [ ] Test IDs synchronized between `.md` and `.spec.ts`
-### Quick validation:
+### Quick validation
```bash
# Verify .md exists for each test folder
ls ui/tests/{feature}/{feature}.md
@@ -59,7 +59,8 @@ grep -o "@[A-Z]*-E2E-[0-9]*" ui/tests/{feature}/{feature}.spec.ts | sort -u
grep -o "\`[A-Z]*-E2E-[0-9]*\`" ui/tests/{feature}/{feature}.md | sort -u
```
-**❌ An E2E change is NOT considered complete without updating the corresponding .md file**
+> [!IMPORTANT]
+> ❌ An E2E change is NOT considered complete without updating the corresponding `.md` file.
---
diff --git a/skills/prowler-tour/SKILL.md b/skills/prowler-tour/SKILL.md
new file mode 100644
index 0000000000..8511581a47
--- /dev/null
+++ b/skills/prowler-tour/SKILL.md
@@ -0,0 +1,99 @@
+---
+name: prowler-tour
+description: >
+ Keeps product-tour definitions aligned with the UI features they describe.
+ Trigger: When modifying UI components that have associated tours, editing tour
+ definition files, or renaming data-tour-id attributes.
+license: Apache-2.0
+metadata:
+ author: prowler-cloud
+ version: "1.0"
+ scope: [root, ui]
+ auto_invoke:
+ - "Editing a UI file containing data-tour-id attributes"
+ - "Adding, updating, or removing a tour definition (*.tour.ts)"
+ - "Renaming or removing a data-tour-id attribute value"
+ - "Changing button labels or section headings on a tour-covered page"
+ - "Restructuring routes or layouts covered by a tour"
+allowed-tools: Read, Glob, Grep
+---
+
+# prowler-tour
+
+**Report-only.** This skill never edits tour files or UI files; it inspects
+the change, reports drift it finds between tours and the covered UI, and
+recommends actions for the developer to apply.
+
+## Early-exit rule
+
+Run this check first. Most UI edits are not tour-related — exit cheaply.
+
+1. Glob `ui/lib/tours/*.tour.ts`.
+2. For each tour, check whether any `coversFiles` glob pattern matches any
+ file in the current change.
+3. If no tour matches, respond **exactly**:
+
+ > No tour affected — skipping alignment check
+
+ and exit. Do not proceed to the checklist.
+4. If at least one tour matches, continue to "Drift checklist" for that tour.
+
+## Drift checklist
+
+For each affected tour, evaluate every item. Skip items that obviously do
+not apply, but list explicitly which items were checked.
+
+1. **Orphan selectors** — every step's `target` (which composes to
+ `data-tour-id="<tour-id>-<step.target>"`) must resolve to a real element
+ in the codebase. Grep `ui/` for the expected attribute value; report
+ any step whose target is missing.
+2. **Renamed selectors** — a `data-tour-id` attribute was edited in this
+ change. Match it back to any tour step referencing the old value.
+3. **Outdated copy** — a popover `title`/`description` references a button
+ label, heading, or term that no longer exists on the covered page.
+4. **Obsolete steps** — a step describes a section, panel, or workflow
+ that was removed.
+5. **Missing steps** — a new feature was added on the covered surface
+ without a corresponding step (e.g. a new panel, a new primary action,
+ a new wizard stage).
+6. **Reordered flow** — the user's path through the feature changed (e.g.
+ query builder moved before scan selection) and the step order no
+ longer reflects it.
+
+## Version-bump decision tree
+
+Apply per tour after listing drift:
+
+- **NO bump** when the change is cosmetic. Examples: fix a typo, soften
+ copy, rename a `data-tour-id` selector while keeping the same step,
+ swap one screenshot for another, tighten wording.
+- **BUMP `version`** when the user-visible flow changes materially.
+ Examples: a new step was added or removed; the order changed; an
+ anchored target was retargeted to a different panel; the tour now
+ covers a new feature on the surface.
+
+When in doubt, ask: "Would a user who already saw the previous version
+miss something useful by not seeing this one?" If yes, bump.
+
+## Output format
+
+When emitting a report, follow the exact structure in
+`references/output-format.md`. The structure is mandatory because the
+report is consumed downstream and tolerates no field reordering.
+
+## What this skill MUST NOT do
+
+- Do not edit `*.tour.ts` files. This skill is report-only.
+- Do not edit UI files to add or rename `data-tour-id` attributes.
+- Do not invent new tours. Authoring a new tour is a separate, deliberate
+ decision — the developer makes it, not the skill.
+- Do not flag drift in tours whose `coversFiles` do not match any file
+ in the current change. Stick to the early-exit rule.
+
+## See also
+
+- `references/output-format.md` — exact report template (read when
+ emitting a report).
+- `references/tours-architecture.md` — code map for the tour abstraction
+ under `ui/lib/tours/`.
+- `assets/tour-template.ts` — boilerplate for authoring a new `*.tour.ts`.
diff --git a/skills/prowler-tour/assets/tour-template.ts b/skills/prowler-tour/assets/tour-template.ts
new file mode 100644
index 0000000000..cc264a4678
--- /dev/null
+++ b/skills/prowler-tour/assets/tour-template.ts
@@ -0,0 +1,51 @@
+// @ts-nocheck -- template only; resolves once copied into `ui/lib/tours/`
+/**
+ * Tour template — copy this file to `ui/lib/tours/<your-id>.tour.ts` and
+ * fill in the placeholders. See `references/tours-architecture.md` for the
+ * design context.
+ *
+ * Conventions:
+ * - Declare via `defineTour({...})` (NOT `: TourDefinition`) so TS
+ * preserves the literal union of `target` values. `useDriverTour` uses
+ * that union to validate `stepHandlers` keys and `waitForStep` args.
+ * - `id` is kebab-case and unique across all tours.
+ * - Anchored steps reference DOM via `data-tour-id="<id>-<step.target>"`;
+ * the hook composes the CSS selector automatically.
+ * - `coversFiles` lists the globs that describe the tour's surface; the
+ * `prowler-tour` skill consumes this to decide whether to evaluate
+ * drift on a given change.
+ * - Material flow changes bump `version`; cosmetic edits do not.
+ */
+import {
+ defineTour,
+ TOUR_STEP_ALIGNMENTS,
+ TOUR_STEP_SIDES,
+} from "@/lib/tours/tour-types";
+
+export const yourTour = defineTour({
+ id: "your-tour-id",
+ version: 1,
+ coversFiles: [
+ // List the UI files this tour describes, using globs under `ui/`.
+ // Example: "ui/app/(prowler)/your-feature/**"
+ ],
+ steps: [
+ {
+ // Modal step — no anchor. Use for intros, outros, and any step
+ // that does not point at a specific DOM element.
+ title: "Welcome",
+ description: "Short, plain-English description.",
+ },
+ {
+ // Anchored step. The hook resolves
+ // `[data-tour-id="your-tour-id-step-name"]` lazily, so the element
+ // can be conditionally rendered as long as it exists when the step
+ // becomes active.
+ target: "step-name",
+ side: TOUR_STEP_SIDES.BOTTOM,
+ align: TOUR_STEP_ALIGNMENTS.START,
+ title: "Where the action is",
+ description: "Tell the user what to look at here and why.",
+ },
+ ],
+});
diff --git a/skills/prowler-tour/references/output-format.md b/skills/prowler-tour/references/output-format.md
new file mode 100644
index 0000000000..ecd82c4d8e
--- /dev/null
+++ b/skills/prowler-tour/references/output-format.md
@@ -0,0 +1,31 @@
+# Tour Alignment Report — output format
+
+The report is consumed downstream. Field names, order, and headings are
+load-bearing — do not rename, reorder, or omit them.
+
+## Template
+
+```text
+## Tour Alignment Report
+**Tour:** `<tour-id>@v<version>`
+**Files touched:** <comma-separated list of files in the change>
+
+### Drift detected
+- <one bullet per drift item; include file:line where available>
+
+### Recommended actions
+1. <numbered, actionable steps the developer should take>
+
+### Version bump verdict
+- <BUMP | NO bump> — <one-line rationale>
+```
+
+## Rules
+
+- One report per affected tour. If multiple tours are affected, separate
+ reports with a `---` line.
+- If no drift is detected for an affected tour, still emit the report:
+ put "No drift detected." under "Drift detected" and "None required."
+ under "Recommended actions". The verdict line is still mandatory.
+- The verdict is exactly one of `BUMP` or `NO bump` — see the
+ version-bump decision tree in `SKILL.md`.
diff --git a/skills/prowler-tour/references/tours-architecture.md b/skills/prowler-tour/references/tours-architecture.md
new file mode 100644
index 0000000000..9a5c8f49e0
--- /dev/null
+++ b/skills/prowler-tour/references/tours-architecture.md
@@ -0,0 +1,44 @@
+# Tours Architecture
+
+The product-tour abstraction lives under [`ui/lib/tours/`](../../../ui/lib/tours/).
+This skill operates on tour definitions that follow this architecture.
+
+## Code map
+
+| File | Purpose |
+|---|---|
+| `ui/lib/tours/tour-types.ts` | Public type surface: `TourDefinition`, `TourStep`, `TourId`, `TourCompletionRecord`, completion-state const map. Also exports `defineTour(...)` — the required authoring helper that preserves literal step `target`s so `useDriverTour` can type-check `stepHandlers` keys and `waitForStep` arguments. |
+| `ui/lib/tours/tour-config.ts` | `baseDriverConfig`, `getDriverConfig(theme, overrides?)`, overlay-color map. |
+| `ui/lib/tours/store/tour-completion-store.ts` | Persistence interface — the swap point for future API adapters. |
+| `ui/lib/tours/store/local-storage-adapter.ts` | The only adapter in the PoC. Key format: `prowler.tour.<id>.v<version>`. |
+| `ui/lib/tours/use-driver-tour.ts` | React hook. Initializes driver.js, derives `overlayColor` from `useTheme()`, persists completion. |
+| `ui/lib/tours/<id>.tour.ts` | One file per tour. Declared via `defineTour({...})` (not `: TourDefinition`) and imported by the page that opts the user in. |
+| `ui/styles/tours.css` | `.driver-popover.prowler-theme` — every color resolved via `var(--...)` from `globals.css`. |
+
+## Selector convention
+
+Tour steps anchor via `data-tour-id="<tour-id>-<step.target>"`. The hook
+composes the CSS selector at runtime; tour authors only provide the step
+name in `step.target`. Class-based, ID-based, structural selectors are
+forbidden — they couple tours to styling decisions that legitimately
+change.
+
+## Identity and versioning
+
+A tour is `{ id, version }`. The localStorage key composes both. A
+**material content change** bumps `version`; cosmetic edits do not. The
+decision tree lives in the parent SKILL.md.
+
+## Persistence scope
+
+Per-user, cross-tenant. A user who completed `attack-paths@v1` in tenant
+A does not see the tour again in tenant B, even if they can access the
+feature there. The future `UserTourState` model (documented in
+`design.md`, not built) is FK to `User`, not `Membership`.
+
+## Drift = #1 risk
+
+Without the maintenance skill + the optional CI gate
+(`ui/scripts/check-tour-alignment.mjs`), tours decay silently as the
+covered UI evolves. The parent SKILL.md enumerates the six drift
+categories the skill checks for.
diff --git a/skills/prowler-ui/SKILL.md b/skills/prowler-ui/SKILL.md
index bde8c966db..18d37a9cd2 100644
--- a/skills/prowler-ui/SKILL.md
+++ b/skills/prowler-ui/SKILL.md
@@ -2,14 +2,15 @@
name: prowler-ui
description: >
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4.
- Trigger: When working inside ui/ on Prowler-specific conventions (shadcn vs HeroUI legacy, folder placement, actions/adapters, shared types/hooks/lib).
+ Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
license: Apache-2.0
metadata:
author: prowler-cloud
- version: "1.0"
+ version: "1.1"
scope: [root, ui]
auto_invoke:
- "Creating/modifying Prowler UI components"
+ - "Reviewing Prowler UI components"
- "Working on Prowler UI structure (actions/adapters/types/hooks)"
allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
---
@@ -27,34 +28,44 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## Tech Stack (Versions)
-```
+```text
Next.js 16.2.3 | React 19.2.5 | Tailwind 4.1.18 | shadcn/ui
Zod 4.1.11 | React Hook Form 7.62.0 | Zustand 5.0.8
NextAuth 5.0.0-beta.30 | Recharts 2.15.4
-HeroUI 2.8.4 (LEGACY - do not add new components)
```
## CRITICAL: Component Library Rule
- **ALWAYS**: Use `shadcn/ui` + Tailwind (`components/shadcn/`)
-- **NEVER**: Add new HeroUI components (`components/ui/` is legacy only)
+- **NEVER**: Add components to `components/ui/` (temporary re-export shims for the prowler-cloud overlay only)
+
+## Design System Discipline (REQUIRED)
+
+Applies to ALL UI work. The design system is the single source of truth — reuse it exactly, extend it deliberately.
+
+- **Reuse first, never reinvent.** Before building anything, search `components/shadcn/` and existing usages in the codebase for an equivalent. Do NOT create a custom component, modal wrapper, or primitive when one already exists.
+- **Use exactly the defined variants/styles — no more, no less.** At the call site, drive appearance through the component's `variant`/`size`/`tone` props. Never add ad-hoc visual `className` (color, opacity, hover/focus/disabled, spacing-for-looks) to shared controls (`Button`, `SelectTrigger`, `SelectItem`, `Modal`, badges…), and never skip the correct semantic variant.
+- **Modals**: only `@/components/shadcn/modal`. **Selects**: `components/shadcn/select`.
+- **Colors**: reuse existing semantic tokens from `ui/styles/globals.css`. No raw Tailwind color utilities (e.g. `bg-blue-950/40`), no hex. If no token fits, STOP and ask the design owner — do not invent or near-duplicate tokens.
+- **Need a genuinely new variant/token?** That is a design-system change: add it to the shared component API (with design sign-off), then consume it. It is never a call-site decision.
+
+When reviewing UI PRs, flag: custom modals/primitives that duplicate shadcn, call-site visual `className` on shared controls, raw color utilities, and new variants/tokens introduced without going through the shared component API.
## DECISION TREES
### Component Placement
-```
-New feature UI? → shadcn/ui + Tailwind
-Existing HeroUI feature? → Keep HeroUI (don't mix)
-Used 1 feature? → features/{feature}/components/
-Used 2+ features? → components/shared/
-Needs state/hooks? → "use client"
-Server component? → No directive needed
+```text
+New UI primitive? → components/shadcn/ (shadcn/ui + Tailwind)
+Used by 1 domain? → components/{domain}/
+Used by 2+ domains? → components/shared/
+Needs state/hooks? → "use client"
+Server component? → No directive needed
```
### Code Location
-```
+```text
Server action → actions/{feature}/{feature}.ts
Data transform → actions/{feature}/{feature}.adapter.ts
Types (shared 2+) → types/{domain}.ts
@@ -63,13 +74,19 @@ Utils (shared 2+) → lib/
Utils (local 1) → {feature}/utils/
Hooks (shared 2+) → hooks/
Hooks (local 1) → {feature}/hooks.ts
-shadcn components → components/shadcn/
-HeroUI components → components/ui/ (LEGACY)
+UI primitive → components/shadcn/
+Domain component → components/{domain}/
```
+> **Deprecated:** `components/ui/` is a temporary re-export shim that maps
+> legacy import paths to `components/shadcn/` for the prowler-cloud overlay.
+> HeroUI is fully removed. Never add or import components here — use
+> `@/components/shadcn` (primitives) or `@/components/{domain}` instead.
+> Delete the shim once the cloud repo migrates to `@/components/shadcn`.
+
### Styling Decision
-```
+```text
Tailwind class exists? → className
Dynamic value? → style prop
Conditional styles? → cn()
@@ -85,7 +102,7 @@ Recharts/library? → CHART_COLORS constant + var()
## Project Structure
-```
+```text
ui/
├── app/
│ ├── (auth)/ # Auth pages (login, signup)
@@ -97,8 +114,9 @@ ui/
│ ├── services/
│ └── integrations/
├── components/
-│ ├── shadcn/ # shadcn/ui (USE THIS)
-│ ├── ui/ # HeroUI (LEGACY)
+│ ├── shadcn/ # shadcn/ui primitives (USE THIS)
+│ ├── shared/ # Cross-domain composed components (2+ domains)
+│ ├── ui/ # DEPRECATED shim → re-exports shadcn (do not use)
│ ├── {domain}/ # Domain-specific (compliance, findings, providers, etc.)
│ ├── filters/ # Filter components
│ ├── graphs/ # Chart components
@@ -311,16 +329,6 @@ Before requesting re-review from a reviewer:
- [ ] If you disagreed: the reply explains why with clear reasoning — do not leave threads silently open
- [ ] Re-request review only after all threads are in a clean state
-## Migrations Reference
-
-| From | To | Key Changes |
-|------|-----|-------------|
-| React 18 | 19.1 | Async components, React Compiler (no useMemo/useCallback) |
-| Next.js 14 | 15.5 | Improved App Router, better streaming |
-| NextUI | HeroUI 2.8.4 | Package rename only, same API |
-| Zod 3 | 4 | `z.email()` not `z.string().email()`, `error` not `message` |
-| AI SDK 4 | 5 | `@ai-sdk/react`, `sendMessage` not `handleSubmit`, `parts` not `content` |
-
## Resources
- **Documentation**: See [references/](references/) for links to local developer guide
diff --git a/skills/skill-creator/SKILL.md b/skills/skill-creator/SKILL.md
index 11787abe2b..41b8e7e67d 100644
--- a/skills/skill-creator/SKILL.md
+++ b/skills/skill-creator/SKILL.md
@@ -29,7 +29,7 @@ Create a skill when:
## Skill Structure
-```
+```text
skills/{skill-name}/
├── SKILL.md # Required - main skill file
├── assets/ # Optional - templates, schemas, examples
@@ -43,7 +43,7 @@ skills/{skill-name}/
## SKILL.md Template
-```markdown
+````markdown
---
name: {skill-name}
description: >
@@ -77,7 +77,7 @@ metadata:
- **Templates**: See [assets/](assets/) for {description}
- **Documentation**: See [references/](references/) for local docs
-```
+````
---
@@ -94,7 +94,7 @@ metadata:
## Decision: assets/ vs references/
-```
+```text
Need code templates? → assets/
Need JSON schemas? → assets/
Need example configs? → assets/
@@ -108,7 +108,7 @@ Link to external guides? → references/ (with local path)
## Decision: Prowler-Specific vs Generic
-```
+```text
Patterns apply to ANY project? → Generic skill (e.g., pytest, typescript)
Patterns are Prowler-specific? → prowler-{name} skill
Generic skill needs Prowler info? → Add references/ pointing to Prowler docs
diff --git a/skills/skill-creator/assets/SKILL-TEMPLATE.md b/skills/skill-creator/assets/SKILL-TEMPLATE.md
index 7639240245..581cafd9c4 100644
--- a/skills/skill-creator/assets/SKILL-TEMPLATE.md
+++ b/skills/skill-creator/assets/SKILL-TEMPLATE.md
@@ -38,7 +38,7 @@ Use this skill when:
## Decision Tree
-```
+```text
{Question 1}? → {Action A}
{Question 2}? → {Action B}
Otherwise → {Default action}
diff --git a/skills/tailwind-4/SKILL.md b/skills/tailwind-4/SKILL.md
index 51f57576af..e67d2ea944 100644
--- a/skills/tailwind-4/SKILL.md
+++ b/skills/tailwind-4/SKILL.md
@@ -14,7 +14,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
## Styling Decision Tree
-```
+```text
Tailwind class exists? → className="..."
Dynamic value? → style={{ width: `${x}%` }}
Conditional styles? → cn("base", condition && "variant")
diff --git a/skills/tdd/SKILL.md b/skills/tdd/SKILL.md
index 0f84d5c5ed..6b82228c9f 100644
--- a/skills/tdd/SKILL.md
+++ b/skills/tdd/SKILL.md
@@ -20,7 +20,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, Task
## TDD Cycle (MANDATORY)
-```
+```text
+-----------------------------------------+
| RED -> GREEN -> REFACTOR |
| ^ | |
@@ -28,7 +28,7 @@ allowed-tools: Read, Edit, Write, Glob, Grep, Bash, Task
+-----------------------------------------+
```
-**The question is NOT "should I write tests?" but "what tests do I need?"**
+The question is NOT "should I write tests?" but "what tests do I need?"
---
@@ -94,7 +94,7 @@ uv run pytest api/src/backend/api/tests/test_models.py -v
### Decision Tree (All Stacks)
-```
+```text
+------------------------------------------+
| Does test file exist for this code? |
+----------+-----------------------+-------+
@@ -122,7 +122,7 @@ uv run pytest api/src/backend/api/tests/test_models.py -v
### For NEW Functionality
-**UI (Vitest)**
+#### UI (Vitest)
```typescript
describe("PriceCalculator", () => {
@@ -139,7 +139,7 @@ describe("PriceCalculator", () => {
});
```
-**SDK (pytest)**
+#### SDK (pytest)
```python
class Test_ec2_ami_public:
@@ -159,14 +159,14 @@ class Test_ec2_ami_public:
assert len(result) == 0
```
-**API (pytest-django)**
+#### API (pytest-django)
```python
@pytest.mark.django_db
class TestResourceModel:
- def test_create_resource_with_tags(self, providers_fixture):
+ def test_create_resource_with_tags(self, aws_provider):
# Given
- provider, *_ = providers_fixture
+ provider = aws_provider
tenant_id = provider.tenant_id
# When
@@ -192,18 +192,18 @@ Write a test that **reproduces the bug** first:
**API:** `assert response.status_code == 403 # Currently returns 200`
-**Run -> Should FAIL (reproducing the bug)**
+Run -> Should FAIL (reproducing the bug).
### For REFACTORING
Capture ALL current behavior BEFORE refactoring:
-```
+```text
# Any stack: run ALL existing tests, they should PASS
# This is your safety net - if any fail after refactoring, you broke something
```
-**Run -> All should PASS (baseline)**
+Run -> All should PASS (baseline).
---
@@ -288,13 +288,13 @@ Tests GREEN -> Improve code quality WITHOUT changing behavior.
- Add types/validation
- Reduce duplication
-**Run tests after EACH change -> Must stay GREEN**
+Run tests after EACH change -> Must stay GREEN.
---
## Quick Reference
-```
+```text
+------------------------------------------------+
| TDD WORKFLOW |
+------------------------------------------------+
@@ -320,7 +320,7 @@ Tests GREEN -> Improve code quality WITHOUT changing behavior.
## Anti-Patterns (NEVER DO)
-```
+```python
# ANY language:
# 1. Code first, tests after
diff --git a/skills/vitest/SKILL.md b/skills/vitest/SKILL.md
index 11190cbaef..29ad237a3e 100644
--- a/skills/vitest/SKILL.md
+++ b/skills/vitest/SKILL.md
@@ -181,7 +181,7 @@ expect(screen.getByRole("button")).toBeDisabled();
## File Organization
-```
+```text
components/
├── Button/
│ ├── Button.tsx
diff --git a/tests/config/config_test.py b/tests/config/config_test.py
index 1540ef6d5b..d10c384b0d 100644
--- a/tests/config/config_test.py
+++ b/tests/config/config_test.py
@@ -6,6 +6,7 @@ from unittest import mock
from requests import Response
from prowler.config.config import (
+ Provider,
check_current_version,
get_available_compliance_frameworks,
load_and_validate_config_file,
@@ -17,6 +18,12 @@ MOCK_OLD_PROWLER_VERSION = "0.0.0"
MOCK_PROWLER_MASTER_VERSION = "3.4.0"
+def test_provider_enum_includes_stackit_for_global_discovery():
+ providers = [provider.value for provider in Provider]
+
+ assert "stackit" in providers
+
+
def mock_prowler_get_latest_release(_, **_kwargs):
"""Mock requests.get() to get the Prowler latest release"""
response = Response()
@@ -313,6 +320,19 @@ config_aws = {
"minimum_snapshot_retention_period": 7,
"elb_min_azs": 2,
"elbv2_min_azs": 2,
+ "elbv2_listener_pqc_tls_allowed_policies": [
+ "ELBSecurityPolicy-TLS13-1-2-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext1-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext2-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-3-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext0-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext1-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Ext2-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-2-Res-FIPS-PQ-2025-09",
+ "ELBSecurityPolicy-TLS13-1-3-FIPS-PQ-2025-09",
+ ],
"secrets_ignore_patterns": [],
"max_days_secret_unused": 90,
"max_days_secret_unrotated": 90,
@@ -464,6 +484,58 @@ class Test_Config:
all_frameworks = get_available_compliance_frameworks()
assert "csa_ccm_4.0" in all_frameworks
+ @mock.patch("prowler.config.config._get_ep_compliance_dirs")
+ def test_get_available_compliance_frameworks_dedupes_ep_collisions_with_builtins(
+ self, mock_dirs
+ ):
+ """Entry-point compliance frameworks that collide with a built-in
+ name must appear only once in the available frameworks list.
+ Built-in wins silently — same policy as the universal frameworks
+ loop and as Compliance.get_bulk."""
+ import json
+ import tempfile
+
+ with tempfile.TemporaryDirectory() as tmpdir:
+ # cis_2.0_aws ships as a built-in under prowler/compliance/aws/
+ json_path = os.path.join(tmpdir, "cis_2.0_aws.json")
+ with open(json_path, "w") as f:
+ json.dump({"Framework": "CIS", "Provider": "aws"}, f)
+
+ mock_dirs.return_value = {"aws": [tmpdir]}
+
+ frameworks = get_available_compliance_frameworks("aws")
+
+ assert frameworks.count("cis_2.0_aws") == 1, (
+ f"Expected cis_2.0_aws to appear exactly once, got "
+ f"{frameworks.count('cis_2.0_aws')} occurrences in: {frameworks}"
+ )
+
+ @mock.patch("prowler.config.config._get_ep_compliance_dirs")
+ def test_get_available_compliance_frameworks_merges_multiple_ep_dirs_same_provider(
+ self, mock_dirs
+ ):
+ """Frameworks from every package contributing the same provider must
+ surface, not just the last directory discovered."""
+ import json
+ import tempfile
+
+ with (
+ tempfile.TemporaryDirectory() as pkg_a,
+ tempfile.TemporaryDirectory() as pkg_b,
+ ):
+ with open(os.path.join(pkg_a, "cis_1.0_template.json"), "w") as f:
+ json.dump({"Framework": "CIS", "Provider": "template"}, f)
+ with open(os.path.join(pkg_b, "nis2_1.0_template.json"), "w") as f:
+ json.dump({"Framework": "NIS2", "Provider": "template"}, f)
+
+ # Two packages register `prowler.compliance` with the same name.
+ mock_dirs.return_value = {"template": [pkg_a, pkg_b]}
+
+ frameworks = get_available_compliance_frameworks("template")
+
+ assert "cis_1.0_template" in frameworks
+ assert "nis2_1.0_template" in frameworks
+
def test_load_and_validate_config_file_aws(self):
path = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
config_test_file = f"{path}/fixtures/config.yaml"
@@ -501,6 +573,32 @@ class Test_Config:
assert load_and_validate_config_file("azure", config_test_file) == {}
assert load_and_validate_config_file("kubernetes", config_test_file) == {}
+ def test_load_and_validate_config_file_namespaced_non_listed_provider(self):
+ path = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
+ config_test_file = f"{path}/fixtures/config_namespaced_external.yaml"
+ # github is a built-in not in the legacy hardcoded list; namespaced format must unwrap it.
+ assert load_and_validate_config_file("github", config_test_file) == {
+ "token": "abc",
+ "org": "prowler-cloud",
+ }
+
+ def test_load_and_validate_config_file_namespaced_external_provider(self):
+ path = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
+ config_test_file = f"{path}/fixtures/config_namespaced_external.yaml"
+ # External plug-in provider: namespaced format must unwrap its block.
+ assert load_and_validate_config_file("custom_plugin", config_test_file) == {
+ "setting": "value",
+ "nested": {"key": 42},
+ }
+
+ def test_load_and_validate_config_file_namespaced_missing_provider(self):
+ path = pathlib.Path(os.path.dirname(os.path.realpath(__file__)))
+ config_test_file = f"{path}/fixtures/config_namespaced_external.yaml"
+ # Provider with no section in a namespaced file must return empty config,
+ # not the full file (prevents cross-provider config leakage).
+ assert load_and_validate_config_file("aws", config_test_file) == {}
+ assert load_and_validate_config_file("gcp", config_test_file) == {}
+
def test_load_and_validate_config_file_invalid_config_file_path(self, caplog):
provider = "aws"
config_file_path = "invalid/path/to/fixer_config.yaml"
diff --git a/tests/config/fixtures/config.yaml b/tests/config/fixtures/config.yaml
index 7305ed550b..df663e923a 100644
--- a/tests/config/fixtures/config.yaml
+++ b/tests/config/fixtures/config.yaml
@@ -362,6 +362,21 @@ aws:
# Minimum number of Availability Zones that an ELBv2 must be in
elbv2_min_azs: 2
+ # aws.elbv2_listener_pqc_tls_enabled
+ # Allowed post-quantum TLS security policies for ELBv2 HTTPS/TLS listeners
+ elbv2_listener_pqc_tls_allowed_policies:
+ - "ELBSecurityPolicy-TLS13-1-2-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext1-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext2-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-3-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext0-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext1-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Ext2-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-2-Res-FIPS-PQ-2025-09"
+ - "ELBSecurityPolicy-TLS13-1-3-FIPS-PQ-2025-09"
+
# AWS Elasticache Configuration
# aws.elasticache_redis_cluster_backup_enabled
# Minimum number of days that a Redis cluster must have backups retention period
@@ -493,3 +508,6 @@ okta:
# Okta Sign-On Policies
# okta.signon_global_session_idle_timeout_15min
okta_max_session_idle_minutes: 15
+ # Okta Applications
+ # okta.application_admin_console_session_idle_timeout_15min
+ okta_admin_console_idle_timeout_max_minutes: 15
diff --git a/tests/config/fixtures/config_namespaced_external.yaml b/tests/config/fixtures/config_namespaced_external.yaml
new file mode 100644
index 0000000000..ec9f75c698
--- /dev/null
+++ b/tests/config/fixtures/config_namespaced_external.yaml
@@ -0,0 +1,8 @@
+# Namespaced config covering a non-listed built-in (github) and an external plugin.
+github:
+ token: abc
+ org: prowler-cloud
+custom_plugin:
+ setting: value
+ nested:
+ key: 42
diff --git a/tests/config/schema/aws_schema_test.py b/tests/config/schema/aws_schema_test.py
new file mode 100644
index 0000000000..838853f52a
--- /dev/null
+++ b/tests/config/schema/aws_schema_test.py
@@ -0,0 +1,274 @@
+"""AWS-specific schema coverage — the biggest provider, with the richest
+constraint surface (CIDRs, account IDs, port ranges, enums, thresholds)."""
+
+import pytest
+
+from prowler.config.scan_config_schema import SCAN_CONFIG_SCHEMA
+from prowler.config.schema.aws import AWSProviderConfig
+from prowler.config.schema.validator import validate_provider_config
+
+
+def _validate(raw):
+ return validate_provider_config("aws", raw, AWSProviderConfig)
+
+
+RESOURCE_LIMIT_KEYS = [
+ "max_scanned_resources_per_service",
+ "max_ebs_snapshots",
+ "max_backup_recovery_points",
+ "max_cloudwatch_log_groups",
+ "max_lambda_functions",
+ "max_ecs_task_definitions",
+ "max_codeartifact_packages",
+]
+
+
+class Test_AWS_Resource_Limits:
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_positive_values_round_trip(self, key):
+ assert _validate({key: 100}) == {key: 100}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_null_values_round_trip(self, key):
+ assert _validate({key: None}) == {key: None}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_zero_disable_sentinel_round_trips(self, key):
+ assert _validate({key: 0}) == {key: 0}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_numeric_strings_are_coerced_to_int(self, key):
+ assert _validate({key: "100"}) == {key: 100}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_disable_sentinel_minus_one_round_trips(self, key):
+ assert _validate({key: -1}) == {key: -1}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ @pytest.mark.parametrize("value", [True, False])
+ def test_booleans_are_dropped_not_coerced_to_int(self, key, value):
+ assert _validate({key: value}) == {}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_invalid_strings_are_dropped(self, key):
+ assert _validate({key: "not-an-int"}) == {}
+
+ @pytest.mark.parametrize("key", RESOURCE_LIMIT_KEYS)
+ def test_keys_are_exposed_in_scan_config_schema(self, key):
+ assert key in SCAN_CONFIG_SCHEMA["properties"]["aws"]["properties"]
+
+
+class Test_AWS_Threat_Detection_Thresholds:
+ """All threat detection thresholds are documented as fractions in 0..1.
+ The biggest risk of mistyping them is silently disabling the check."""
+
+ @pytest.mark.parametrize(
+ "key",
+ [
+ "threat_detection_privilege_escalation_threshold",
+ "threat_detection_enumeration_threshold",
+ "threat_detection_llm_jacking_threshold",
+ ],
+ )
+ def test_valid_boundary_values(self, key):
+ assert _validate({key: 0.0}) == {key: 0.0}
+ assert _validate({key: 1.0}) == {key: 1.0}
+ assert _validate({key: 0.5}) == {key: 0.5}
+
+ @pytest.mark.parametrize(
+ "key",
+ [
+ "threat_detection_privilege_escalation_threshold",
+ "threat_detection_enumeration_threshold",
+ "threat_detection_llm_jacking_threshold",
+ ],
+ )
+ def test_invalid_values_are_dropped(self, key):
+ # 20 instead of 0.2 — would never trigger
+ assert _validate({key: 20}) == {}
+ # negative
+ assert _validate({key: -0.1}) == {}
+ # string
+ assert _validate({key: "high"}) == {}
+
+
+class Test_AWS_Trusted_Account_Ids:
+ def test_valid_twelve_digit_ids(self):
+ ids = ["123456789012", "098765432109"]
+ assert _validate({"trusted_account_ids": ids}) == {"trusted_account_ids": ids}
+
+ def test_empty_list_is_valid(self):
+ assert _validate({"trusted_account_ids": []}) == {"trusted_account_ids": []}
+
+ def test_short_id_is_dropped(self):
+ assert _validate({"trusted_account_ids": ["12345"]}) == {}
+
+ def test_non_numeric_id_is_dropped(self):
+ assert _validate({"trusted_account_ids": ["1234abcd5678"]}) == {}
+
+ def test_id_with_dashes_is_dropped(self):
+ # Some users format account IDs as "1234-5678-9012"
+ assert _validate({"trusted_account_ids": ["1234-5678-9012"]}) == {}
+
+
+class Test_AWS_Trusted_Ips:
+ def test_single_ipv4_address(self):
+ assert _validate({"trusted_ips": ["1.2.3.4"]}) == {"trusted_ips": ["1.2.3.4"]}
+
+ def test_ipv4_cidr(self):
+ assert _validate({"trusted_ips": ["10.0.0.0/8"]}) == {
+ "trusted_ips": ["10.0.0.0/8"]
+ }
+
+ def test_ipv6_address(self):
+ assert _validate({"trusted_ips": ["2001:db8::1"]}) == {
+ "trusted_ips": ["2001:db8::1"]
+ }
+
+ def test_ipv6_cidr(self):
+ assert _validate({"trusted_ips": ["2001:db8::/32"]}) == {
+ "trusted_ips": ["2001:db8::/32"]
+ }
+
+ def test_mixed_list(self):
+ ips = ["1.2.3.4", "10.0.0.0/8", "2001:db8::1"]
+ assert _validate({"trusted_ips": ips}) == {"trusted_ips": ips}
+
+ def test_garbage_entry_is_dropped(self):
+ assert _validate({"trusted_ips": ["definitely-not-an-ip"]}) == {}
+
+ def test_cidr_with_host_bits_is_accepted(self):
+ # We use strict=False so "10.0.0.5/8" is accepted. This matches the
+ # behaviour of most security tools and avoids surprising users who
+ # paste real-world allowlists with non-canonical CIDR notation.
+ assert _validate({"trusted_ips": ["10.0.0.5/8"]}) == {
+ "trusted_ips": ["10.0.0.5/8"]
+ }
+
+
+class Test_AWS_Ports:
+ def test_valid_ports_in_range(self):
+ ports = [25, 80, 443, 65535, 1]
+ assert _validate({"ec2_high_risk_ports": ports}) == {
+ "ec2_high_risk_ports": ports
+ }
+
+ def test_port_zero_is_dropped(self):
+ # Port 0 is reserved and not a valid security signal.
+ assert _validate({"ec2_high_risk_ports": [0]}) == {}
+
+ def test_out_of_range_port_is_dropped(self):
+ assert _validate({"ec2_high_risk_ports": [70000]}) == {}
+
+ def test_negative_port_is_dropped(self):
+ assert _validate({"ec2_high_risk_ports": [-1]}) == {}
+
+
+class Test_AWS_Enums:
+ @pytest.mark.parametrize("level", ["CRITICAL", "HIGH", "MEDIUM", "LOW"])
+ def test_valid_severity_levels(self, level):
+ assert _validate({"ecr_repository_vulnerability_minimum_severity": level}) == {
+ "ecr_repository_vulnerability_minimum_severity": level
+ }
+
+ @pytest.mark.parametrize("level", ["critical", "Medium", "ANY", "", "X"])
+ def test_invalid_severity_levels_are_dropped(self, level):
+ assert _validate({"ecr_repository_vulnerability_minimum_severity": level}) == {}
+
+
+class TestAWSELBv2PQCTLSAllowedPolicies:
+ def test_valid_policy_list_round_trips(self):
+ policies = [
+ "ELBSecurityPolicy-TLS13-1-2-Res-2021-06",
+ "ELBSecurityPolicy-TLS13-1-3-2021-06",
+ ]
+
+ assert _validate({"elbv2_listener_pqc_tls_allowed_policies": policies}) == {
+ "elbv2_listener_pqc_tls_allowed_policies": policies
+ }
+
+ def test_key_is_exposed_in_scan_config_schema(self):
+ aws_properties = SCAN_CONFIG_SCHEMA["properties"]["aws"]["properties"]
+
+ assert "elbv2_listener_pqc_tls_allowed_policies" in aws_properties
+
+ @pytest.mark.parametrize(
+ "value",
+ [
+ "ELBSecurityPolicy-TLS13-1-2-Res-2021-06",
+ ["ELBSecurityPolicy-TLS13-1-2-Res-2021-06", 123],
+ ],
+ )
+ def test_invalid_policy_values_are_dropped(self, value):
+ assert _validate({"elbv2_listener_pqc_tls_allowed_policies": value}) == {}
+
+
+class Test_AWS_Secrets_Ignore_Files:
+ def test_valid_file_patterns_round_trip(self):
+ files = ["*.deps.json", "vendor/*.js"]
+ assert _validate({"secrets_ignore_files": files}) == {
+ "secrets_ignore_files": files
+ }
+
+ def test_empty_list_is_valid(self):
+ assert _validate({"secrets_ignore_files": []}) == {"secrets_ignore_files": []}
+
+ def test_exposed_in_scan_config_schema(self):
+ aws_properties = SCAN_CONFIG_SCHEMA["properties"]["aws"]["properties"]
+
+ assert aws_properties["secrets_ignore_files"] == {
+ "anyOf": [
+ {"items": {"type": "string"}, "type": "array"},
+ {"type": "null"},
+ ],
+ "default": None,
+ "title": "Secrets Ignore Files",
+ }
+
+
+class Test_AWS_Booleans:
+ @pytest.mark.parametrize(
+ "key",
+ [
+ "mute_non_default_regions",
+ "verify_premium_support_plans",
+ "check_rds_instance_replicas",
+ ],
+ )
+ def test_true_and_false_round_trip(self, key):
+ assert _validate({key: True}) == {key: True}
+ assert _validate({key: False}) == {key: False}
+
+ def test_yaml_style_boolean_coercion(self):
+ # YAML can produce Python str "true"/"yes" if the user quoted it.
+ # Pydantic v2 deterministically coerces "yes"/"no"/"true"/"false" to a
+ # real bool in lax mode, so the value is normalized rather than passed
+ # through as a string (which would be dangerous for
+ # verify_premium_support_plans).
+ out = _validate({"verify_premium_support_plans": "yes"})
+ assert "verify_premium_support_plans" in out
+ assert isinstance(out["verify_premium_support_plans"], bool)
+ assert out["verify_premium_support_plans"] is True
+
+
+class Test_AWS_Full_Default_Config_Round_Trips:
+ """Loading the real shipped defaults through the schema must produce
+ exactly the same dict. This is the regression sentinel for backwards
+ compatibility."""
+
+ def test_full_default_config_round_trip(self):
+ # Subset that mirrors the shipped config.yaml semantics.
+ raw = {
+ "mute_non_default_regions": False,
+ "disallowed_regions": ["me-south-1", "me-central-1"],
+ "max_unused_access_keys_days": 45,
+ "max_ec2_instance_age_in_days": 180,
+ "trusted_account_ids": [],
+ "trusted_ips": [],
+ "ecr_repository_vulnerability_minimum_severity": "MEDIUM",
+ "threat_detection_privilege_escalation_threshold": 0.2,
+ "threat_detection_enumeration_threshold": 0.3,
+ "threat_detection_llm_jacking_threshold": 0.4,
+ "ec2_high_risk_ports": [25, 110, 8088],
+ }
+ assert _validate(raw) == raw
diff --git a/tests/config/schema/bounds_test.py b/tests/config/schema/bounds_test.py
new file mode 100644
index 0000000000..4d8d49bab2
--- /dev/null
+++ b/tests/config/schema/bounds_test.py
@@ -0,0 +1,378 @@
+"""Boundary tests for the safety bounds added on top of the upstream schemas.
+
+Each parametrised case checks (a) the min and max values are accepted and
+(b) one step outside the range is rejected. Custom validators (semver,
+EKS minor, dotted version, port range, account IDs, IPs) get focused
+positive/negative tests.
+
+Tests use the public adapter ``prowler.config.scan_config_schema``: a
+schema violation surfaces as a list of ``{"path", "message"}`` entries.
+This keeps the contract the Prowler App backend depends on under test.
+"""
+
+import pytest
+
+from prowler.config.scan_config_schema import validate_scan_config
+
+
+def _has_error_for(errors: list[dict], path_substr: str) -> bool:
+ return any(path_substr in e["path"] for e in errors)
+
+
+# Each tuple: (provider, key, min_allowed, max_allowed)
+INT_BOUND_CASES = [
+ # AWS
+ ("aws", "max_unused_access_keys_days", 30, 180),
+ ("aws", "max_console_access_days", 30, 180),
+ ("aws", "max_unused_sagemaker_access_days", 7, 180),
+ ("aws", "max_security_group_rules", 1, 1000),
+ ("aws", "max_ec2_instance_age_in_days", 1, 1095),
+ ("aws", "recommended_cdk_bootstrap_version", 1, 100),
+ ("aws", "max_idle_disconnect_timeout_in_seconds", 60, 1800),
+ ("aws", "max_disconnect_timeout_in_seconds", 60, 3600),
+ ("aws", "max_session_duration_seconds", 600, 86400),
+ ("aws", "lambda_min_azs", 1, 6),
+ ("aws", "threat_detection_privilege_escalation_minutes", 5, 43200),
+ ("aws", "threat_detection_enumeration_minutes", 5, 43200),
+ ("aws", "threat_detection_llm_jacking_minutes", 5, 43200),
+ ("aws", "days_to_expire_threshold", 7, 365),
+ ("aws", "elb_min_azs", 1, 6),
+ ("aws", "elbv2_min_azs", 1, 6),
+ ("aws", "minimum_snapshot_retention_period", 1, 35),
+ ("aws", "max_days_secret_unused", 7, 365),
+ ("aws", "max_days_secret_unrotated", 1, 180),
+ ("aws", "min_kinesis_stream_retention_hours", 24, 8760),
+ # Azure
+ ("azure", "vm_backup_min_daily_retention_days", 7, 9999),
+ ("azure", "apim_threat_detection_llm_jacking_minutes", 5, 43200),
+ # GCP
+ ("gcp", "mig_min_zones", 1, 5),
+ ("gcp", "max_snapshot_age_days", 1, 1095),
+ ("gcp", "max_unused_account_days", 30, 365),
+ ("gcp", "storage_min_retention_days", 1, 3650),
+ # Kubernetes
+ ("kubernetes", "audit_log_maxbackup", 2, 1000),
+ ("kubernetes", "audit_log_maxsize", 10, 10000),
+ ("kubernetes", "audit_log_maxage", 7, 3650),
+ # M365
+ ("m365", "sign_in_frequency", 1, 168),
+ ("m365", "recommended_mailtips_large_audience_threshold", 5, 10000),
+ ("m365", "audit_log_age", 30, 3650),
+ # GitHub
+ ("github", "inactive_not_archived_days_threshold", 30, 3650),
+ # MongoDB Atlas
+ ("mongodbatlas", "max_service_account_secret_validity_hours", 1, 720),
+ # Cloudflare
+ ("cloudflare", "max_retries", 0, 10),
+ # Vercel
+ ("vercel", "days_to_expire_threshold", 7, 365),
+ ("vercel", "stale_token_threshold_days", 30, 3650),
+ ("vercel", "stale_invitation_threshold_days", 7, 365),
+ ("vercel", "max_owner_percentage", 1, 50),
+ ("vercel", "max_owners", 1, 1000),
+ # Okta
+ ("okta", "okta_max_session_idle_minutes", 1, 1440),
+ ("okta", "okta_max_session_lifetime_minutes", 1, 43200),
+ ("okta", "okta_admin_console_idle_timeout_max_minutes", 1, 1440),
+ ("okta", "okta_user_inactivity_max_days", 1, 3650),
+ # Alibaba Cloud
+ ("alibabacloud", "max_cluster_check_days", 1, 365),
+ ("alibabacloud", "max_console_access_days", 30, 180),
+ ("alibabacloud", "min_log_retention_days", 1, 3650),
+ ("alibabacloud", "min_rds_audit_retention_days", 1, 3650),
+ # OpenStack
+ ("openstack", "image_sharing_threshold", 1, 1000),
+]
+
+
+FLOAT_THRESHOLD_FIELDS = [
+ ("aws", "threat_detection_privilege_escalation_threshold"),
+ ("aws", "threat_detection_enumeration_threshold"),
+ ("aws", "threat_detection_llm_jacking_threshold"),
+ ("azure", "apim_threat_detection_llm_jacking_threshold"),
+]
+
+
+class TestIntegerBounds:
+ """Each int field accepts both ends of its range and rejects ±1 outside."""
+
+ @pytest.mark.parametrize("provider, key, lo, hi", INT_BOUND_CASES)
+ def test_min_accepted(self, provider, key, lo, hi):
+ assert validate_scan_config({provider: {key: lo}}) == []
+
+ @pytest.mark.parametrize("provider, key, lo, hi", INT_BOUND_CASES)
+ def test_max_accepted(self, provider, key, lo, hi):
+ assert validate_scan_config({provider: {key: hi}}) == []
+
+ @pytest.mark.parametrize("provider, key, lo, hi", INT_BOUND_CASES)
+ def test_below_min_rejected(self, provider, key, lo, hi):
+ errors = validate_scan_config({provider: {key: lo - 1}})
+ assert _has_error_for(errors, f"{provider}.{key}"), errors
+
+ @pytest.mark.parametrize("provider, key, lo, hi", INT_BOUND_CASES)
+ def test_above_max_rejected(self, provider, key, lo, hi):
+ errors = validate_scan_config({provider: {key: hi + 1}})
+ assert _has_error_for(errors, f"{provider}.{key}"), errors
+
+
+class TestFloatThresholds:
+ """Threshold floats must stay within 0..1 inclusive."""
+
+ @pytest.mark.parametrize("provider, key", FLOAT_THRESHOLD_FIELDS)
+ def test_zero_and_one_accepted(self, provider, key):
+ assert validate_scan_config({provider: {key: 0.0}}) == []
+ assert validate_scan_config({provider: {key: 1.0}}) == []
+ assert validate_scan_config({provider: {key: 0.5}}) == []
+
+ @pytest.mark.parametrize("provider, key", FLOAT_THRESHOLD_FIELDS)
+ def test_negative_rejected(self, provider, key):
+ errors = validate_scan_config({provider: {key: -0.01}})
+ assert _has_error_for(errors, f"{provider}.{key}")
+
+ @pytest.mark.parametrize("provider, key", FLOAT_THRESHOLD_FIELDS)
+ def test_above_one_rejected(self, provider, key):
+ errors = validate_scan_config({provider: {key: 1.01}})
+ assert _has_error_for(errors, f"{provider}.{key}")
+
+
+class TestCloudWatchRetention:
+ """`log_group_retention_days` only accepts the AWS-approved enum values."""
+
+ @pytest.mark.parametrize("value", [1, 7, 30, 365, 731, 3653])
+ def test_valid_values_accepted(self, value):
+ assert validate_scan_config({"aws": {"log_group_retention_days": value}}) == []
+
+ @pytest.mark.parametrize("value", [0, 2, 42, 500, 999, 4000])
+ def test_invalid_values_rejected(self, value):
+ errors = validate_scan_config({"aws": {"log_group_retention_days": value}})
+ assert _has_error_for(errors, "aws.log_group_retention_days")
+
+
+class TestSemverValidator:
+ """AWS Fargate platform versions: X.Y.Z."""
+
+ @pytest.mark.parametrize("value", ["1.4.0", "1.0.0", "0.0.1", "10.20.30"])
+ def test_accepts_semver(self, value):
+ assert (
+ validate_scan_config({"aws": {"fargate_linux_latest_version": value}}) == []
+ )
+
+ @pytest.mark.parametrize("value", ["1.4", "1", "v1.4.0", "1.4.0-beta", "a.b.c", ""])
+ def test_rejects_non_semver(self, value):
+ errors = validate_scan_config({"aws": {"fargate_linux_latest_version": value}})
+ assert _has_error_for(errors, "aws.fargate_linux_latest_version")
+
+
+class TestEksVersionValidator:
+ """`eks_cluster_oldest_version_supported` expects MAJOR.MINOR."""
+
+ @pytest.mark.parametrize("value", ["1.28", "1.29", "1.30", "2.0"])
+ def test_accepts_minor(self, value):
+ assert (
+ validate_scan_config(
+ {"aws": {"eks_cluster_oldest_version_supported": value}}
+ )
+ == []
+ )
+
+ @pytest.mark.parametrize("value", ["1.28.0", "v1.28", "1", "1.x", ""])
+ def test_rejects_invalid(self, value):
+ errors = validate_scan_config(
+ {"aws": {"eks_cluster_oldest_version_supported": value}}
+ )
+ assert _has_error_for(errors, "aws.eks_cluster_oldest_version_supported")
+
+
+class TestEksLogTypesEnum:
+ """Only the documented log types are accepted."""
+
+ def test_full_enum_accepted(self):
+ assert (
+ validate_scan_config(
+ {
+ "aws": {
+ "eks_required_log_types": [
+ "api",
+ "audit",
+ "authenticator",
+ "controllerManager",
+ "scheduler",
+ ]
+ }
+ }
+ )
+ == []
+ )
+
+ def test_unknown_type_rejected(self):
+ errors = validate_scan_config(
+ {"aws": {"eks_required_log_types": ["api", "telemetry"]}}
+ )
+ assert _has_error_for(errors, "aws.eks_required_log_types")
+
+
+class TestAzureDottedVersion:
+ """App Service versions accept 'X' and 'X.Y' but not 'X.Y.Z' or junk."""
+
+ @pytest.mark.parametrize("value", ["8.2", "3.12", "17"])
+ def test_accepts(self, value):
+ assert validate_scan_config({"azure": {"php_latest_version": value}}) == []
+ assert validate_scan_config({"azure": {"python_latest_version": value}}) == []
+ assert validate_scan_config({"azure": {"java_latest_version": value}}) == []
+
+ @pytest.mark.parametrize("value", ["8.2.0", "v8", "8.x", ""])
+ def test_rejects(self, value):
+ errors = validate_scan_config({"azure": {"php_latest_version": value}})
+ assert _has_error_for(errors, "azure.php_latest_version")
+
+
+class TestAzureTlsLiteralEnum:
+ """Only TLS 1.2 and 1.3 are tolerated by the recommended list."""
+
+ def test_accepted_versions(self):
+ assert (
+ validate_scan_config(
+ {"azure": {"recommended_minimal_tls_versions": ["1.2", "1.3"]}}
+ )
+ == []
+ )
+
+ @pytest.mark.parametrize("value", ["1.0", "1.1", "2.0", ""])
+ def test_unknown_version_rejected(self, value):
+ errors = validate_scan_config(
+ {"azure": {"recommended_minimal_tls_versions": [value]}}
+ )
+ assert _has_error_for(errors, "azure.recommended_minimal_tls_versions")
+
+
+class TestAzureRiskLevelLiteral:
+ """Defender attack-path risk level is a closed enum."""
+
+ @pytest.mark.parametrize("value", ["Low", "Medium", "High", "Critical"])
+ def test_accepted(self, value):
+ assert (
+ validate_scan_config(
+ {"azure": {"defender_attack_path_minimal_risk_level": value}}
+ )
+ == []
+ )
+
+ @pytest.mark.parametrize("value", ["low", "CRITICAL", "Severe", ""])
+ def test_rejected(self, value):
+ errors = validate_scan_config(
+ {"azure": {"defender_attack_path_minimal_risk_level": value}}
+ )
+ assert _has_error_for(errors, "azure.defender_attack_path_minimal_risk_level")
+
+
+class TestECRSeverityLiteral:
+ """ECR severity is a closed enum (with INFORMATIONAL allowed)."""
+
+ @pytest.mark.parametrize(
+ "value",
+ ["CRITICAL", "HIGH", "MEDIUM", "LOW", "INFORMATIONAL"],
+ )
+ def test_accepted(self, value):
+ assert (
+ validate_scan_config(
+ {"aws": {"ecr_repository_vulnerability_minimum_severity": value}}
+ )
+ == []
+ )
+
+ @pytest.mark.parametrize("value", ["URGENT", "low", "Crit", ""])
+ def test_rejected(self, value):
+ errors = validate_scan_config(
+ {"aws": {"ecr_repository_vulnerability_minimum_severity": value}}
+ )
+ assert _has_error_for(
+ errors, "aws.ecr_repository_vulnerability_minimum_severity"
+ )
+
+
+class TestPortRangeValidator:
+ """Each entry of `ec2_high_risk_ports` must be 1..65535 (0 is reserved)."""
+
+ def test_valid_ports(self):
+ assert (
+ validate_scan_config({"aws": {"ec2_high_risk_ports": [1, 22, 8080, 65535]}})
+ == []
+ )
+
+ @pytest.mark.parametrize("value", [-1, 0, 65536, 99999])
+ def test_invalid_port_rejected(self, value):
+ errors = validate_scan_config({"aws": {"ec2_high_risk_ports": [80, value]}})
+ assert _has_error_for(errors, "aws.ec2_high_risk_ports")
+
+
+class TestAccountIdsValidator:
+ """AWS account IDs are 12-digit strings."""
+
+ def test_valid(self):
+ assert (
+ validate_scan_config(
+ {"aws": {"trusted_account_ids": ["123456789012", "098765432109"]}}
+ )
+ == []
+ )
+
+ @pytest.mark.parametrize(
+ "value", ["12345", "12345678901", "1234567890123", "12345678901a"]
+ )
+ def test_invalid_rejected(self, value):
+ errors = validate_scan_config({"aws": {"trusted_account_ids": [value]}})
+ assert _has_error_for(errors, "aws.trusted_account_ids")
+
+
+class TestTrustedIpsValidator:
+ """Trusted IPs accept IPv4, IPv6, and CIDR; reject junk."""
+
+ @pytest.mark.parametrize(
+ "value",
+ ["1.2.3.4", "10.0.0.0/8", "2001:db8::1", "2001:db8::/32"],
+ )
+ def test_valid(self, value):
+ assert validate_scan_config({"aws": {"trusted_ips": [value]}}) == []
+
+ @pytest.mark.parametrize(
+ "value", ["not.an.ip", "1.2.3.300", "10.0.0.0/40", "::ffff:::"]
+ )
+ def test_invalid_rejected(self, value):
+ errors = validate_scan_config({"aws": {"trusted_ips": [value]}})
+ assert _has_error_for(errors, "aws.trusted_ips")
+
+
+class TestAdapterRobustness:
+ """Top-level adapter behaviour the Prowler App backend depends on."""
+
+ def test_non_dict_payload(self):
+ errors = validate_scan_config([1, 2, 3])
+ assert len(errors) == 1
+ assert errors[0]["path"] == "<root>"
+
+ def test_unknown_provider_section_tolerated(self):
+ # additionalProperties: True at the root level by design.
+ assert validate_scan_config({"newprovider": {"foo": "bar"}}) == []
+
+ def test_unknown_key_tolerated_by_pydantic_extra_allow(self):
+ # ProviderConfigBase has extra="allow" for forward compatibility.
+ assert validate_scan_config({"aws": {"completely_new_knob": 1}}) == []
+
+ def test_provider_section_must_be_mapping(self):
+ errors = validate_scan_config({"aws": "not a mapping"})
+ assert _has_error_for(errors, "aws")
+
+ def test_multiple_errors_surfaced(self):
+ errors = validate_scan_config(
+ {
+ "aws": {
+ "max_unused_access_keys_days": 5, # below min 30
+ "max_security_group_rules": 99999, # above max 1000
+ "ec2_high_risk_ports": [80, 70000], # port out of range
+ }
+ }
+ )
+ # All three should surface independently.
+ assert _has_error_for(errors, "aws.max_unused_access_keys_days")
+ assert _has_error_for(errors, "aws.max_security_group_rules")
+ assert _has_error_for(errors, "aws.ec2_high_risk_ports")
diff --git a/tests/config/schema/exclusions_test.py b/tests/config/schema/exclusions_test.py
new file mode 100644
index 0000000000..a13ed2f786
--- /dev/null
+++ b/tests/config/schema/exclusions_test.py
@@ -0,0 +1,113 @@
+"""Coverage for the ``excluded_checks`` / ``excluded_services`` fields
+added to :class:`prowler.config.schema.base.ProviderConfigBase`.
+
+Because the fields live on the base class, every registered provider
+schema exposes them and every provider must therefore share the same
+whitespace / uniqueness / non-empty guarantees. These tests lock in that
+contract at the base level and at the JSON-Schema level (which the UI
+editor consumes via ``ajv``).
+"""
+
+import pytest
+from pydantic import ValidationError
+
+from prowler.config.scan_config_schema import SCAN_CONFIG_SCHEMA
+from prowler.config.schema.aws import AWSProviderConfig
+from prowler.config.schema.registry import SCHEMAS
+from prowler.config.schema.validator import validate_provider_config
+
+EXCLUSION_FIELDS = ("excluded_checks", "excluded_services")
+
+
+class Test_JSON_Schema_Exposes_Exclusion_Fields:
+ @pytest.mark.parametrize("provider", sorted(SCHEMAS))
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_field_shape(self, provider, field):
+ field_schema = SCAN_CONFIG_SCHEMA["properties"][provider]["properties"][field]
+ assert field_schema["type"] == "array"
+ assert field_schema["items"] == {"type": "string", "minLength": 1}
+ assert field_schema["uniqueItems"] is True
+ assert field_schema["default"] == []
+
+
+class Test_Exclusion_Field_Validation:
+ def _model(self, **kwargs):
+ return AWSProviderConfig.model_validate(kwargs)
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_empty_string_is_rejected(self, field):
+ with pytest.raises(ValidationError):
+ self._model(**{field: [""]})
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_whitespace_only_string_is_rejected(self, field):
+ with pytest.raises(ValidationError):
+ self._model(**{field: [" "]})
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_raw_duplicates_are_rejected(self, field):
+ with pytest.raises(ValidationError):
+ self._model(**{field: ["s3", "s3"]})
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_normalized_duplicates_are_rejected(self, field):
+ # After whitespace normalization ``" s3 "`` collapses to ``"s3"``
+ # and must be caught by the duplicate check.
+ with pytest.raises(ValidationError):
+ self._model(**{field: ["s3", " s3 "]})
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_whitespace_is_stripped(self, field):
+ model = self._model(**{field: [" identifier "]})
+ assert getattr(model, field) == ["identifier"]
+
+ @pytest.mark.parametrize("field", EXCLUSION_FIELDS)
+ def test_non_string_item_is_rejected(self, field):
+ with pytest.raises(ValidationError):
+ self._model(**{field: [123]})
+
+
+class Test_Exclusion_Defaults_Are_Not_Injected:
+ """The strict normalization path uses ``model_dump(exclude_unset=True)``
+ so pre-existing configs that never set an exclusion field must round-trip
+ without the default empty list being materialized."""
+
+ def test_absent_fields_are_not_injected_by_validator(self):
+ # The lenient SDK runtime path also uses ``exclude_unset=True`` under
+ # the hood; asserting on the validator output guards the promise
+ # against future refactors.
+ assert validate_provider_config("aws", {}, SCHEMAS["aws"]) == {}
+
+ def test_absent_fields_are_not_injected_when_other_keys_are_present(self):
+ assert validate_provider_config(
+ "aws",
+ {"max_ec2_instance_age_in_days": 180},
+ SCHEMAS["aws"],
+ ) == {"max_ec2_instance_age_in_days": 180}
+
+ def test_explicit_empty_list_round_trips(self):
+ # Explicitly setting ``excluded_checks: []`` is different from
+ # omitting it — the empty list is user-provided and must be
+ # preserved by the strict-normalization contract.
+ assert validate_provider_config(
+ "aws",
+ {"excluded_checks": []},
+ SCHEMAS["aws"],
+ ) == {"excluded_checks": []}
+
+
+class Test_Extra_Fields_Are_Preserved:
+ """``extra="allow"`` must keep plugin-provided keys around so the
+ ecosystem contract in ``validator_test.py`` still holds after adding
+ the exclusion fields."""
+
+ def test_unknown_keys_are_preserved_alongside_exclusions(self):
+ out = validate_provider_config(
+ "aws",
+ {"excluded_checks": ["s3_bucket_public_access"], "plugin_option": "kept"},
+ SCHEMAS["aws"],
+ )
+ assert out == {
+ "excluded_checks": ["s3_bucket_public_access"],
+ "plugin_option": "kept",
+ }
diff --git a/tests/config/schema/loader_integration_test.py b/tests/config/schema/loader_integration_test.py
new file mode 100644
index 0000000000..fa995fb9df
--- /dev/null
+++ b/tests/config/schema/loader_integration_test.py
@@ -0,0 +1,124 @@
+"""End-to-end tests that exercise the real ``load_and_validate_config_file``
+through a temp YAML file. Anything that breaks here would break the actual
+``prowler aws -c …`` code path."""
+
+import logging
+import os
+import pathlib
+from typing import Callable
+
+import pytest
+
+from prowler.config.config import load_and_validate_config_file
+
+
+@pytest.fixture
+def write_config(tmp_path: pathlib.Path) -> Callable[[str], str]:
+ def _write(content: str) -> str:
+ path = tmp_path / "config.yaml"
+ path.write_text(content)
+ return str(path)
+
+ return _write
+
+
+class Test_Loader_With_Schema_Integration:
+ def test_shipped_default_config_loads_without_warnings(self, caplog):
+ """The default ``prowler/config/config.yaml`` must round-trip every
+ provider WITHOUT emitting any schema warnings. If this fails,
+ someone added a key to the YAML without updating the schema."""
+ repo_root = pathlib.Path(os.path.dirname(os.path.realpath(__file__))).parents[2]
+ shipped = repo_root / "prowler" / "config" / "config.yaml"
+ with caplog.at_level(logging.WARNING, logger="prowler"):
+ for provider in [
+ "aws",
+ "azure",
+ "gcp",
+ "kubernetes",
+ "m365",
+ "github",
+ "mongodbatlas",
+ "cloudflare",
+ "vercel",
+ ]:
+ cfg = load_and_validate_config_file(provider, str(shipped))
+ # Provider always exists in the shipped file → non-empty.
+ assert cfg, f"{provider} returned an empty config"
+
+ offending = [
+ r.getMessage()
+ for r in caplog.records
+ if "prowler.config[" in r.getMessage()
+ ]
+ assert not offending, (
+ "Shipped config.yaml triggered schema warnings — schema or YAML out of sync:\n"
+ + "\n".join(offending)
+ )
+
+ def test_user_config_with_bad_threshold_falls_back(self, write_config, caplog):
+ path = write_config(
+ "aws:\n"
+ " threat_detection_privilege_escalation_threshold: 5.0\n"
+ " lambda_min_azs: 2\n"
+ )
+ with caplog.at_level(logging.WARNING, logger="prowler"):
+ cfg = load_and_validate_config_file("aws", path)
+ assert cfg == {"lambda_min_azs": 2}
+ assert any(
+ "threat_detection_privilege_escalation_threshold" in r.getMessage()
+ for r in caplog.records
+ )
+
+ def test_old_format_config_still_works(self, write_config):
+ # Old format = flat keys, no provider header.
+ path = write_config(
+ "max_ec2_instance_age_in_days: 90\n"
+ "ecr_repository_vulnerability_minimum_severity: HIGH\n"
+ )
+ cfg = load_and_validate_config_file("aws", path)
+ assert cfg == {
+ "max_ec2_instance_age_in_days": 90,
+ "ecr_repository_vulnerability_minimum_severity": "HIGH",
+ }
+
+ def test_unknown_keys_pass_through_via_loader(self, write_config):
+ path = write_config(
+ "aws:\n" " third_party_plugin_setting: hello\n" " lambda_min_azs: 2\n"
+ )
+ cfg = load_and_validate_config_file("aws", path)
+ assert cfg == {
+ "third_party_plugin_setting": "hello",
+ "lambda_min_azs": 2,
+ }
+
+ def test_quoted_numeric_is_coerced_via_loader(self, write_config):
+ # YAML quotes the number: ``"180"`` arrives as a Python str.
+ # The schema must coerce it to int so downstream comparisons work.
+ path = write_config('aws:\n max_ec2_instance_age_in_days: "180"\n')
+ cfg = load_and_validate_config_file("aws", path)
+ assert cfg == {"max_ec2_instance_age_in_days": 180}
+ assert isinstance(cfg["max_ec2_instance_age_in_days"], int)
+
+ def test_invalid_yaml_shape_list_as_string_drops_key(self, write_config, caplog):
+ path = write_config(
+ "aws:\n"
+ " disallowed_regions: me-south-1\n" # forgot list dashes
+ " lambda_min_azs: 2\n"
+ )
+ with caplog.at_level(logging.WARNING, logger="prowler"):
+ cfg = load_and_validate_config_file("aws", path)
+ assert cfg == {"lambda_min_azs": 2}
+ assert any("disallowed_regions" in r.getMessage() for r in caplog.records)
+
+ def test_other_providers_unaffected_by_aws_block(self, write_config):
+ path = write_config(
+ "aws:\n max_ec2_instance_age_in_days: 90\n" "gcp:\n mig_min_zones: 5\n"
+ )
+ assert load_and_validate_config_file("aws", path) == {
+ "max_ec2_instance_age_in_days": 90
+ }
+ assert load_and_validate_config_file("gcp", path) == {"mig_min_zones": 5}
+
+ def test_missing_provider_block_returns_empty(self, write_config):
+ path = write_config("aws:\n max_ec2_instance_age_in_days: 90\n")
+ assert load_and_validate_config_file("azure", path) == {}
diff --git a/tests/config/schema/other_providers_schema_test.py b/tests/config/schema/other_providers_schema_test.py
new file mode 100644
index 0000000000..0406776f57
--- /dev/null
+++ b/tests/config/schema/other_providers_schema_test.py
@@ -0,0 +1,276 @@
+"""Smaller-provider schema coverage. One happy path + one invalid path
+per field is enough to lock in the contract; the validator behaviour
+itself is covered exhaustively in validator_test.py."""
+
+import pytest
+
+from prowler.config.schema.registry import SCHEMAS
+from prowler.config.schema.validator import validate_provider_config
+
+
+def _validate(provider, raw):
+ return validate_provider_config(provider, raw, SCHEMAS[provider])
+
+
+class Test_Azure_Schema:
+ @pytest.mark.parametrize("level", ["Low", "Medium", "High", "Critical"])
+ def test_defender_risk_level_valid_values(self, level):
+ assert _validate(
+ "azure", {"defender_attack_path_minimal_risk_level": level}
+ ) == {"defender_attack_path_minimal_risk_level": level}
+
+ def test_defender_risk_level_lowercase_dropped(self):
+ # Case matters: the matching check uses Title-case comparison.
+ assert (
+ _validate("azure", {"defender_attack_path_minimal_risk_level": "high"})
+ == {}
+ )
+
+ def test_apim_threshold_in_range(self):
+ out = _validate("azure", {"apim_threat_detection_llm_jacking_threshold": 0.1})
+ assert out == {"apim_threat_detection_llm_jacking_threshold": 0.1}
+
+ def test_apim_threshold_out_of_range(self):
+ out = _validate("azure", {"apim_threat_detection_llm_jacking_threshold": 1.5})
+ assert out == {}
+
+ def test_vm_backup_retention_must_be_positive(self):
+ assert _validate("azure", {"vm_backup_min_daily_retention_days": 7}) == {
+ "vm_backup_min_daily_retention_days": 7
+ }
+ assert _validate("azure", {"vm_backup_min_daily_retention_days": 0}) == {}
+ assert _validate("azure", {"vm_backup_min_daily_retention_days": -1}) == {}
+
+
+class Test_GCP_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "mig_min_zones": 2,
+ "max_snapshot_age_days": 90,
+ "max_unused_account_days": 180,
+ "storage_min_retention_days": 90,
+ }
+ assert _validate("gcp", raw) == raw
+
+ def test_zero_zone_count_dropped(self):
+ assert _validate("gcp", {"mig_min_zones": 0}) == {}
+
+
+class Test_Kubernetes_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "audit_log_maxbackup": 10,
+ "audit_log_maxsize": 100,
+ "audit_log_maxage": 30,
+ }
+ assert _validate("kubernetes", raw) == raw
+
+ def test_negative_audit_log_dropped(self):
+ assert _validate("kubernetes", {"audit_log_maxage": -1}) == {}
+
+
+class Test_M365_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "sign_in_frequency": 4,
+ "recommended_mailtips_large_audience_threshold": 25,
+ "audit_log_age": 90,
+ }
+ assert _validate("m365", raw) == raw
+
+ def test_negative_audit_log_age_dropped(self):
+ assert _validate("m365", {"audit_log_age": -10}) == {}
+
+
+class Test_GitHub_Schema:
+ def test_valid_threshold(self):
+ assert _validate("github", {"inactive_not_archived_days_threshold": 180}) == {
+ "inactive_not_archived_days_threshold": 180
+ }
+
+ def test_zero_threshold_dropped(self):
+ assert _validate("github", {"inactive_not_archived_days_threshold": 0}) == {}
+
+
+class Test_MongoDBAtlas_Schema:
+ def test_valid(self):
+ assert _validate(
+ "mongodbatlas", {"max_service_account_secret_validity_hours": 8}
+ ) == {"max_service_account_secret_validity_hours": 8}
+
+ def test_invalid_negative(self):
+ assert (
+ _validate("mongodbatlas", {"max_service_account_secret_validity_hours": -1})
+ == {}
+ )
+
+
+class Test_Cloudflare_Schema:
+ def test_zero_retries_allowed(self):
+ # 0 is explicitly documented as "disable retries" in config.yaml.
+ assert _validate("cloudflare", {"max_retries": 0}) == {"max_retries": 0}
+
+ def test_positive_retries_allowed(self):
+ assert _validate("cloudflare", {"max_retries": 3}) == {"max_retries": 3}
+
+ def test_negative_retries_dropped(self):
+ assert _validate("cloudflare", {"max_retries": -1}) == {}
+
+
+class Test_Okta_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "okta_max_session_idle_minutes": 15,
+ "okta_max_session_lifetime_minutes": 18 * 60,
+ "okta_admin_console_idle_timeout_max_minutes": 15,
+ "okta_user_inactivity_max_days": 35,
+ "okta_dod_approved_ca_issuer_patterns": [r"\bOU=DoD\b", r"\bOU=ECA\b"],
+ }
+ assert _validate("okta", raw) == raw
+
+ def test_zero_idle_minutes_dropped(self):
+ assert _validate("okta", {"okta_max_session_idle_minutes": 0}) == {}
+
+ def test_negative_inactivity_days_dropped(self):
+ assert _validate("okta", {"okta_user_inactivity_max_days": -1}) == {}
+
+ def test_full_rate_limit_config_round_trip(self):
+ raw = {
+ "okta_requests_per_second": 4.0,
+ "okta_max_retries": 5,
+ "okta_request_timeout": 300,
+ }
+ assert _validate("okta", raw) == raw
+
+ def test_requests_per_second_zero_allowed(self):
+ # 0 is documented as "disable throttling" in config.yaml.
+ assert _validate("okta", {"okta_requests_per_second": 0}) == {
+ "okta_requests_per_second": 0
+ }
+
+ def test_requests_per_second_sub_one_allowed(self):
+ assert _validate("okta", {"okta_requests_per_second": 0.5}) == {
+ "okta_requests_per_second": 0.5
+ }
+
+ def test_requests_per_second_floor_allowed(self):
+ # 0.1 is the lowest non-zero rate accepted.
+ assert _validate("okta", {"okta_requests_per_second": 0.1}) == {
+ "okta_requests_per_second": 0.1
+ }
+
+ def test_requests_per_second_below_floor_dropped(self):
+ # A tiny rate (e.g. 0.001 -> ~1000s/request) would make scans take
+ # days or years; it must be rejected, not silently honoured.
+ assert _validate("okta", {"okta_requests_per_second": 0.001}) == {}
+ assert _validate("okta", {"okta_requests_per_second": 0.05}) == {}
+
+ def test_requests_per_second_above_max_dropped(self):
+ assert _validate("okta", {"okta_requests_per_second": 101}) == {}
+
+ def test_requests_per_second_negative_dropped(self):
+ assert _validate("okta", {"okta_requests_per_second": -1}) == {}
+
+ def test_max_retries_zero_allowed(self):
+ assert _validate("okta", {"okta_max_retries": 0}) == {"okta_max_retries": 0}
+
+ def test_max_retries_out_of_range_dropped(self):
+ assert _validate("okta", {"okta_max_retries": -1}) == {}
+ assert _validate("okta", {"okta_max_retries": 11}) == {}
+
+ def test_request_timeout_zero_allowed(self):
+ # 0 is documented as "disable the timeout" in config.yaml.
+ assert _validate("okta", {"okta_request_timeout": 0}) == {
+ "okta_request_timeout": 0
+ }
+
+ def test_request_timeout_in_range_allowed(self):
+ assert _validate("okta", {"okta_request_timeout": 300}) == {
+ "okta_request_timeout": 300
+ }
+
+ def test_request_timeout_out_of_range_dropped(self):
+ assert _validate("okta", {"okta_request_timeout": -1}) == {}
+ assert _validate("okta", {"okta_request_timeout": 3601}) == {}
+
+ def test_non_numeric_value_dropped(self):
+ # A typo'd string must not flow through to the limiter (it would crash
+ # the `> 0` comparison during provider init).
+ assert _validate("okta", {"okta_requests_per_second": "fast"}) == {}
+
+
+class Test_Vercel_Schema:
+ def test_owner_percentage_in_range(self):
+ assert _validate("vercel", {"max_owner_percentage": 20}) == {
+ "max_owner_percentage": 20
+ }
+ assert _validate("vercel", {"max_owner_percentage": 1}) == {
+ "max_owner_percentage": 1
+ }
+ assert _validate("vercel", {"max_owner_percentage": 50}) == {
+ "max_owner_percentage": 50
+ }
+
+ def test_owner_percentage_over_max_dropped(self):
+ # Tightened to 1..50 — anything above (incl. previous 100) is dropped.
+ assert _validate("vercel", {"max_owner_percentage": 51}) == {}
+ assert _validate("vercel", {"max_owner_percentage": 150}) == {}
+
+ def test_owner_percentage_zero_or_negative_dropped(self):
+ # 0 is no longer a valid configuration (defeats PoLP signal).
+ assert _validate("vercel", {"max_owner_percentage": 0}) == {}
+ assert _validate("vercel", {"max_owner_percentage": -1}) == {}
+
+ def test_full_default_config_round_trip(self):
+ raw = {
+ "stable_branches": ["main", "master"],
+ "days_to_expire_threshold": 7,
+ "stale_token_threshold_days": 90,
+ "stale_invitation_threshold_days": 30,
+ "max_owner_percentage": 20,
+ "max_owners": 3,
+ "secret_suffixes": ["_KEY", "_SECRET", "_TOKEN"],
+ }
+ assert _validate("vercel", raw) == raw
+
+
+class Test_AlibabaCloud_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "max_cluster_check_days": 7,
+ "max_console_access_days": 90,
+ "min_log_retention_days": 365,
+ "min_rds_audit_retention_days": 180,
+ }
+ assert _validate("alibabacloud", raw) == raw
+
+ def test_zero_cluster_check_days_dropped(self):
+ assert _validate("alibabacloud", {"max_cluster_check_days": 0}) == {}
+
+ def test_console_access_below_min_dropped(self):
+ # 30 is the documented floor; anything below produces false positives.
+ assert _validate("alibabacloud", {"max_console_access_days": 29}) == {}
+
+
+class Test_OpenStack_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {
+ "image_sharing_threshold": 5,
+ "secrets_ignore_patterns": ["AKIA[0-9A-Z]{16}"],
+ }
+ assert _validate("openstack", raw) == raw
+
+ def test_zero_threshold_dropped(self):
+ assert _validate("openstack", {"image_sharing_threshold": 0}) == {}
+
+
+class Test_E2ENetworks_Schema:
+ def test_valid_values_round_trip(self):
+ raw = {"require_bitninja_on_load_balancers": True}
+ assert _validate("e2enetworks", raw) == raw
+
+ def test_non_bool_value_dropped(self):
+ assert (
+ _validate("e2enetworks", {"require_bitninja_on_load_balancers": "maybe"})
+ == {}
+ )
diff --git a/tests/config/schema/scan_config_schema_test.py b/tests/config/schema/scan_config_schema_test.py
new file mode 100644
index 0000000000..037fcd9501
--- /dev/null
+++ b/tests/config/schema/scan_config_schema_test.py
@@ -0,0 +1,393 @@
+"""Coverage for the strict scan-config validation and normalization
+contract exposed to the Prowler App backend.
+
+Split from :mod:`tests.config.schema.validator_test` because the strict
+API (``validate_and_normalize_scan_config``) has different guarantees:
+it never silently drops keys, and it returns a JSON-serializable payload
+the backend can persist verbatim in a Django ``JSONField``.
+"""
+
+import json
+from unittest.mock import call, patch
+
+import pytest
+
+from prowler.config.scan_config_schema import (
+ _get_provider_check_ids,
+ _get_provider_services,
+ validate_and_normalize_scan_config,
+ validate_scan_config,
+)
+
+
+@pytest.fixture(autouse=True)
+def clear_provider_catalog_caches():
+ """Keep provider catalog cache state isolated between tests."""
+ _get_provider_check_ids.cache_clear()
+ _get_provider_services.cache_clear()
+ yield
+ _get_provider_check_ids.cache_clear()
+ _get_provider_services.cache_clear()
+
+
+class Test_Non_Dict_Root:
+ @pytest.mark.parametrize("payload", [None, "string", 42, [], (1, 2)])
+ def test_non_mapping_root_is_rejected(self, payload):
+ normalized, errors = validate_and_normalize_scan_config(payload)
+ assert normalized == {}
+ assert len(errors) == 1
+ assert errors[0]["path"] == "<root>"
+
+
+class Test_Registered_Provider_Section_Must_Be_Mapping:
+ @pytest.mark.parametrize("section", ["a-string", 42, ["s3"], None])
+ def test_non_mapping_section_reports_provider_path(self, section):
+ normalized, errors = validate_and_normalize_scan_config({"aws": section})
+ assert normalized == {}
+ assert errors == [{"path": "aws", "message": "section must be a mapping."}]
+
+
+class Test_Success_Path:
+ def test_whitespace_is_normalized_in_exclusions(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {
+ "aws": {
+ "excluded_checks": [" s3_bucket_default_encryption "],
+ "excluded_services": [" s3 "],
+ }
+ }
+ )
+ assert errors == []
+ assert normalized == {
+ "aws": {
+ "excluded_checks": ["s3_bucket_default_encryption"],
+ "excluded_services": ["s3"],
+ }
+ }
+
+ def test_plugin_options_are_preserved(self):
+ # Third-party plugins inject arbitrary keys inside a provider
+ # section; ``extra="allow"`` on the schema keeps them alive
+ # through the dump/normalize round-trip.
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"plugin_option": "preserved", "another": 42}}
+ )
+ assert errors == []
+ assert normalized == {"aws": {"plugin_option": "preserved", "another": 42}}
+
+ def test_plugin_catalog_identifiers_are_accepted_and_catalogs_are_cached(self):
+ payload = {
+ "aws": {
+ "excluded_checks": ["plugin_check"],
+ "excluded_services": ["plugin_service"],
+ }
+ }
+ with (
+ patch(
+ "prowler.config.scan_config_schema.CheckMetadata.get_bulk",
+ return_value={"plugin_check": object()},
+ ) as check_catalog,
+ patch(
+ "prowler.config.scan_config_schema.list_services",
+ return_value=["plugin_service"],
+ ) as service_catalog,
+ ):
+ first_result = validate_and_normalize_scan_config(payload)
+ second_result = validate_and_normalize_scan_config(payload)
+
+ normalized, errors = first_result
+ assert errors == []
+ assert normalized == {
+ "aws": {
+ "excluded_checks": ["plugin_check"],
+ "excluded_services": ["plugin_service"],
+ }
+ }
+ assert second_result == first_result
+ check_catalog.assert_called_once_with("aws")
+ service_catalog.assert_called_once_with("aws")
+
+ def test_catalog_caches_are_keyed_by_provider(self):
+ with (
+ patch(
+ "prowler.config.scan_config_schema.CheckMetadata.get_bulk",
+ side_effect=lambda provider: {f"{provider}_plugin_check": object()},
+ ) as check_catalog,
+ patch(
+ "prowler.config.scan_config_schema.list_services",
+ side_effect=lambda provider: [f"{provider}_plugin_service"],
+ ) as service_catalog,
+ ):
+ payload = {
+ "aws": {
+ "excluded_checks": ["aws_plugin_check"],
+ "excluded_services": ["aws_plugin_service"],
+ },
+ "azure": {
+ "excluded_checks": ["azure_plugin_check"],
+ "excluded_services": ["azure_plugin_service"],
+ },
+ }
+ first_result = validate_and_normalize_scan_config(payload)
+ second_result = validate_and_normalize_scan_config(payload)
+
+ assert first_result[1] == []
+ assert second_result == first_result
+ assert check_catalog.call_args_list == [call("aws"), call("azure")]
+ assert service_catalog.call_args_list == [call("aws"), call("azure")]
+
+ def test_omitted_defaults_are_not_injected(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"max_ec2_instance_age_in_days": 90}}
+ )
+ assert errors == []
+ assert normalized == {"aws": {"max_ec2_instance_age_in_days": 90}}
+ assert "excluded_checks" not in normalized["aws"]
+ assert "excluded_services" not in normalized["aws"]
+
+ def test_unknown_provider_sections_are_preserved_verbatim(self):
+ payload = {"future_provider": {"custom_option": True, "nested": {"k": 1}}}
+ normalized, errors = validate_and_normalize_scan_config(payload)
+ assert errors == []
+ assert normalized == payload
+
+ def test_normalized_payload_is_json_serializable(self):
+ normalized, _ = validate_and_normalize_scan_config(
+ {
+ "aws": {
+ "excluded_checks": ["s3_bucket_public_access"],
+ "excluded_services": ["s3"],
+ }
+ }
+ )
+ # If ``model_dump(mode="json", ...)`` is ever dropped this
+ # ``json.dumps`` call is what will notice.
+ json.dumps(normalized)
+
+ def test_input_payload_is_not_mutated(self):
+ payload = {
+ "aws": {
+ "excluded_checks": [" s3_bucket_public_access "],
+ "excluded_services": [" s3 "],
+ }
+ }
+ snapshot = json.loads(json.dumps(payload))
+ validate_and_normalize_scan_config(payload)
+ assert payload == snapshot
+
+
+class Test_Error_Path:
+ def test_unknown_excluded_check_is_rejected(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"excluded_checks": ["aws_check_that_does_not_exist"]}}
+ )
+ assert normalized == {}
+ assert errors == [
+ {
+ "path": "aws.excluded_checks[0]",
+ "message": (
+ "Unknown check 'aws_check_that_does_not_exist' for provider "
+ "'aws'."
+ ),
+ }
+ ]
+
+ def test_unknown_excluded_service_is_rejected(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"excluded_services": ["not_a_real_aws_service"]}}
+ )
+ assert normalized == {}
+ assert errors == [
+ {
+ "path": "aws.excluded_services[0]",
+ "message": (
+ "Unknown service 'not_a_real_aws_service' for provider 'aws'."
+ ),
+ }
+ ]
+
+ def test_multiple_unknown_exclusions_return_deterministic_errors(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {
+ "aws": {
+ "excluded_checks": [
+ "unknown_check_one",
+ "s3_bucket_default_encryption",
+ "unknown_check_two",
+ ],
+ "excluded_services": [
+ "unknown_service_one",
+ "s3",
+ "unknown_service_two",
+ ],
+ }
+ }
+ )
+ assert normalized == {}
+ assert errors == [
+ {
+ "path": "aws.excluded_checks[0]",
+ "message": "Unknown check 'unknown_check_one' for provider 'aws'.",
+ },
+ {
+ "path": "aws.excluded_checks[2]",
+ "message": "Unknown check 'unknown_check_two' for provider 'aws'.",
+ },
+ {
+ "path": "aws.excluded_services[0]",
+ "message": (
+ "Unknown service 'unknown_service_one' for provider 'aws'."
+ ),
+ },
+ {
+ "path": "aws.excluded_services[2]",
+ "message": (
+ "Unknown service 'unknown_service_two' for provider 'aws'."
+ ),
+ },
+ ]
+
+ def test_check_from_another_provider_is_rejected(self):
+ azure_check = "postgresql_flexible_server_allow_access_services_disabled"
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"excluded_checks": [azure_check]}}
+ )
+ assert normalized == {}
+ assert errors == [
+ {
+ "path": "aws.excluded_checks[0]",
+ "message": f"Unknown check '{azure_check}' for provider 'aws'.",
+ }
+ ]
+
+ def test_invalid_input_returns_empty_normalized_and_errors(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {"excluded_services": ["s3", " s3 "]}}
+ )
+ assert normalized == {}
+ assert errors
+ assert any(err["path"].startswith("aws.excluded_services") for err in errors)
+
+ def test_partial_error_zeros_the_normalized_payload(self):
+ # One valid provider + one invalid provider must not leak the
+ # valid section into a partially normalized result.
+ normalized, errors = validate_and_normalize_scan_config(
+ {
+ "aws": {"excluded_services": ["s3", "s3"]},
+ "azure": {"vm_backup_min_daily_retention_days": 7},
+ }
+ )
+ assert normalized == {}
+ assert errors
+ assert any(err["path"].startswith("aws.") for err in errors)
+
+ def test_value_error_prefix_is_stripped_from_user_facing_messages(self):
+ # Pydantic prefixes messages emitted from ``field_validator``
+ # ValueError with ``"Value error, "``. If this test starts to fail
+ # because the prefix reappears, either pydantic changed the format
+ # or the strip in ``validate_and_normalize_scan_config`` was
+ # dropped — either way the UI would render the noisy prefix, so
+ # we lock the cleaned message in explicitly.
+ _, errors = validate_and_normalize_scan_config(
+ {"aws": {"excluded_services": ["s3", "s3"]}}
+ )
+ assert errors
+ message = errors[0]["message"]
+ assert not message.startswith("Value error, ")
+ assert "duplicate values are not allowed" in message
+
+ def test_all_errors_are_reported_not_only_the_first(self):
+ normalized, errors = validate_and_normalize_scan_config(
+ {
+ "aws": {
+ "excluded_checks": ["", ""],
+ "excluded_services": ["", ""],
+ }
+ }
+ )
+ assert normalized == {}
+ # ``excluded_checks`` yields per-item empty-string errors AND a
+ # duplicate error; ``excluded_services`` yields the same set.
+ paths = {err["path"] for err in errors}
+ assert any(p.startswith("aws.excluded_checks") for p in paths)
+ assert any(p.startswith("aws.excluded_services") for p in paths)
+
+
+class Test_Non_String_Provider_Keys:
+ """The normalized payload is later persisted in a Django JSONField
+ keyed by provider. Two entries whose ``str()`` collide (e.g. ``123``
+ and ``"123"``) would silently overwrite each other, so non-string
+ keys are rejected up front instead of silently coerced."""
+
+ def test_non_string_key_is_rejected(self):
+ normalized, errors = validate_and_normalize_scan_config({123: {}})
+ assert normalized == {}
+ assert errors == [{"path": "123", "message": "provider keys must be strings."}]
+
+ def test_string_and_int_collision_does_not_silently_overwrite(self):
+ # If only ``str()`` coercion happened both keys would collapse to
+ # ``"aws"`` in the output — this test guards against that regression.
+ normalized, errors = validate_and_normalize_scan_config(
+ {"aws": {}, 123: {"a": 1}}
+ )
+ assert normalized == {}
+ assert any(err["path"] == "123" for err in errors)
+
+
+class Test_Unknown_Sections_Must_Be_JSON_Serializable:
+ """``normalized`` is persisted by the API in a Django JSONField, so
+ unknown provider sections must fail fast here instead of blowing up
+ at persist time. Registered sections cannot hit this path — they go
+ through ``model_dump(mode="json", ...)`` which already coerces."""
+
+ def test_set_inside_unknown_section_is_rejected(self):
+ # ``set`` is a common trap: ``yaml.safe_load`` never produces it,
+ # but a hand-built dict might.
+ normalized, errors = validate_and_normalize_scan_config(
+ {"future_provider": {"values": {1, 2, 3}}}
+ )
+ assert normalized == {}
+ assert errors
+ assert errors[0]["path"] == "future_provider"
+ assert "JSON-serializable" in errors[0]["message"]
+
+ def test_json_safe_unknown_section_is_still_preserved(self):
+ payload = {"future_provider": {"nested": {"k": [1, 2, 3]}}}
+ normalized, errors = validate_and_normalize_scan_config(payload)
+ assert errors == []
+ assert normalized == payload
+
+
+class Test_Backward_Compatible_Wrapper:
+ def test_valid_payload_yields_no_errors(self):
+ assert (
+ validate_scan_config(
+ {"aws": {"excluded_checks": ["s3_bucket_public_access"]}}
+ )
+ == []
+ )
+
+ def test_invalid_payload_yields_only_the_errors(self):
+ errors = validate_scan_config({"aws": {"excluded_checks": ["", ""]}})
+ assert errors
+ assert all(set(err) == {"path", "message"} for err in errors)
+
+ def test_unknown_exclusion_yields_the_semantic_error(self):
+ assert validate_scan_config(
+ {"aws": {"excluded_services": ["not_a_real_aws_service"]}}
+ ) == [
+ {
+ "path": "aws.excluded_services[0]",
+ "message": (
+ "Unknown service 'not_a_real_aws_service' for provider 'aws'."
+ ),
+ }
+ ]
+
+ def test_non_mapping_root_matches_new_contract(self):
+ assert validate_scan_config(None) == [
+ {
+ "path": "<root>",
+ "message": "Scan config must be a mapping with provider sections.",
+ }
+ ]
diff --git a/tests/config/schema/validator_test.py b/tests/config/schema/validator_test.py
new file mode 100644
index 0000000000..398a0d10e8
--- /dev/null
+++ b/tests/config/schema/validator_test.py
@@ -0,0 +1,175 @@
+"""Behavioural tests for ``validate_provider_config``.
+
+The validator is the gatekeeper for every provider schema: its job is to
+keep backwards-compatible behaviour (no exceptions, drop only the bad
+keys) while loudly logging type mistakes.
+"""
+
+import logging
+
+import pytest
+
+from prowler.config.schema.aws import AWSProviderConfig
+from prowler.config.schema.registry import SCHEMAS
+from prowler.config.schema.validator import validate_provider_config
+
+
+class Test_Validate_Provider_Config_Contract:
+ """Generic invariants that must hold for any schema."""
+
+ def test_returns_empty_dict_when_raw_is_not_a_dict(self):
+ assert validate_provider_config("aws", None, AWSProviderConfig) == {}
+ assert validate_provider_config("aws", "string", AWSProviderConfig) == {}
+ assert validate_provider_config("aws", 42, AWSProviderConfig) == {}
+ assert validate_provider_config("aws", [], AWSProviderConfig) == {}
+
+ def test_returns_raw_unchanged_when_no_schema_registered(self):
+ raw = {"anything": "goes", "even": [1, 2, 3]}
+ assert validate_provider_config("mystery_provider", raw, None) == raw
+
+ def test_unknown_keys_pass_through_for_plugin_compatibility(self):
+ # Third-party plugins inject arbitrary keys; the schema must NOT
+ # filter them. This is the contract that lets the plugin ecosystem
+ # keep working when we add validation.
+ raw = {"plugin_custom_key": "foo", "lambda_min_azs": 2}
+ assert validate_provider_config("aws", raw, AWSProviderConfig) == {
+ "plugin_custom_key": "foo",
+ "lambda_min_azs": 2,
+ }
+
+ def test_empty_dict_returns_empty_dict(self):
+ assert validate_provider_config("aws", {}, AWSProviderConfig) == {}
+
+ def test_known_valid_value_passes_through_unchanged(self):
+ raw = {"max_ec2_instance_age_in_days": 180}
+ assert validate_provider_config("aws", raw, AWSProviderConfig) == {
+ "max_ec2_instance_age_in_days": 180
+ }
+
+
+class Test_Validate_Provider_Config_Coercion:
+ """Pydantic v2 coerces common type-mistakes automatically. We want to
+ keep that behaviour so quoted numerics in user configs ``Just Work``."""
+
+ def test_string_numeric_is_coerced_to_int(self):
+ out = validate_provider_config(
+ "aws", {"max_ec2_instance_age_in_days": "180"}, AWSProviderConfig
+ )
+ assert out == {"max_ec2_instance_age_in_days": 180}
+ assert isinstance(out["max_ec2_instance_age_in_days"], int)
+
+ def test_string_numeric_is_coerced_to_float(self):
+ out = validate_provider_config(
+ "aws",
+ {"threat_detection_privilege_escalation_threshold": "0.4"},
+ AWSProviderConfig,
+ )
+ assert out == {"threat_detection_privilege_escalation_threshold": 0.4}
+
+
+class Test_Validate_Provider_Config_Drops_Invalid_Keys:
+ """When a field fails validation, only that key is dropped from the
+ returned dict. The rest of the user's config is preserved so the
+ consumer's ``audit_config.get(key, default)`` falls back to its own
+ built-in default for the offending field and uses user values for
+ everything else."""
+
+ def test_out_of_range_threshold_is_dropped(self, caplog):
+ with caplog.at_level(logging.WARNING):
+ out = validate_provider_config(
+ "aws",
+ {
+ "threat_detection_privilege_escalation_threshold": 2.0,
+ "lambda_min_azs": 2,
+ },
+ AWSProviderConfig,
+ )
+ assert out == {"lambda_min_azs": 2}
+ assert any(
+ "threat_detection_privilege_escalation_threshold" in r.getMessage()
+ for r in caplog.records
+ )
+
+ def test_invalid_enum_is_dropped(self):
+ out = validate_provider_config(
+ "aws",
+ {"ecr_repository_vulnerability_minimum_severity": "medum"},
+ AWSProviderConfig,
+ )
+ assert out == {}
+
+ def test_wrong_shape_list_as_string_is_dropped(self):
+ # Classic YAML mistake: ``disallowed_regions: me-south-1`` without dashes.
+ # Pydantic refuses to silently treat a str as a single-element list,
+ # which is exactly the safety guarantee we want.
+ out = validate_provider_config(
+ "aws",
+ {"disallowed_regions": "me-south-1", "lambda_min_azs": 2},
+ AWSProviderConfig,
+ )
+ assert out == {"lambda_min_azs": 2}
+
+ def test_negative_positive_int_is_dropped(self):
+ out = validate_provider_config(
+ "aws", {"max_ec2_instance_age_in_days": -1}, AWSProviderConfig
+ )
+ assert out == {}
+
+ def test_zero_is_dropped_for_strictly_positive_field(self):
+ # max_ec2_instance_age_in_days is gt=0. Zero would silently cause every
+ # instance to FAIL the age check.
+ out = validate_provider_config(
+ "aws", {"max_ec2_instance_age_in_days": 0}, AWSProviderConfig
+ )
+ assert out == {}
+
+ def test_multiple_invalid_keys_yield_multiple_warnings(self, caplog):
+ with caplog.at_level(logging.WARNING):
+ out = validate_provider_config(
+ "aws",
+ {
+ "max_ec2_instance_age_in_days": "nope",
+ "ecr_repository_vulnerability_minimum_severity": "medum",
+ "valid_extra_key": "kept",
+ },
+ AWSProviderConfig,
+ )
+ assert out == {"valid_extra_key": "kept"}
+ messages = " ".join(r.getMessage() for r in caplog.records)
+ assert "max_ec2_instance_age_in_days" in messages
+ assert "ecr_repository_vulnerability_minimum_severity" in messages
+
+ def test_warning_message_includes_provider_and_field(self, caplog):
+ with caplog.at_level(logging.WARNING):
+ validate_provider_config(
+ "aws",
+ {"threat_detection_privilege_escalation_threshold": 5.0},
+ AWSProviderConfig,
+ )
+ assert any(
+ "prowler.config[aws.threat_detection_privilege_escalation_threshold]"
+ in r.getMessage()
+ for r in caplog.records
+ )
+
+
+class Test_Schemas_Registry:
+ """Every provider mentioned in the YAML config must have a schema."""
+
+ @pytest.mark.parametrize(
+ "provider",
+ [
+ "aws",
+ "azure",
+ "gcp",
+ "kubernetes",
+ "m365",
+ "github",
+ "mongodbatlas",
+ "cloudflare",
+ "vercel",
+ ],
+ )
+ def test_schema_registered_for_provider(self, provider):
+ assert provider in SCHEMAS
+ assert SCHEMAS[provider] is not None
diff --git a/tests/dashboard/common_methods_test.py b/tests/dashboard/common_methods_test.py
new file mode 100644
index 0000000000..b2137589c5
--- /dev/null
+++ b/tests/dashboard/common_methods_test.py
@@ -0,0 +1,81 @@
+import pandas as pd
+from dash import dash_table
+
+from dashboard.common_methods import get_section_containers_generic
+
+
+def _datatable_column_ids(component):
+ """Collect the column ids of every DataTable in a Dash component tree."""
+ if isinstance(component, dash_table.DataTable):
+ return [[c["id"] for c in component.columns]]
+ children = getattr(component, "children", None)
+ if children is None:
+ return []
+ if not isinstance(children, (list, tuple)):
+ children = [children]
+ return [cols for child in children for cols in _datatable_column_ids(child)]
+
+
+def _df(**extra):
+ data = {
+ "REQUIREMENTS_ID": ["req1"],
+ "STATUS": ["PASS"],
+ "CHECKID": ["check1"],
+ "REGION": ["us-east-1"],
+ "ACCOUNTID": ["123"],
+ "RESOURCEID": ["res1"],
+ }
+ data.update(extra)
+ return pd.DataFrame(data)
+
+
+class TestGetSectionContainersGeneric:
+ def test_one_container_per_section(self):
+ """One outer container per distinct section value."""
+ df = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec A", "Sec B"],
+ "REQUIREMENTS_ID": ["req1", "req2", "req3"],
+ "STATUS": ["PASS", "FAIL", "PASS"],
+ "CHECKID": ["c1", "c2", "c3"],
+ "REGION": ["-"] * 3,
+ "ACCOUNTID": ["123"] * 3,
+ "RESOURCEID": ["r1", "r2", "r3"],
+ }
+ )
+ result = get_section_containers_generic(
+ df, "REQUIREMENTS_ATTRIBUTES_SECTION", "REQUIREMENTS_ID"
+ )
+ assert len(result.children) == 2
+
+ def test_inner_title_includes_id_and_description(self):
+ """Inner accordion title is '<id> - <description>'."""
+ df = _df(
+ REQUIREMENTS_ATTRIBUTES_SECTION=["Sec A"],
+ REQUIREMENTS_DESCRIPTION=["Ensure MFA"],
+ )
+ rendered = str(
+ get_section_containers_generic(
+ df, "REQUIREMENTS_ATTRIBUTES_SECTION", "REQUIREMENTS_ID"
+ )
+ )
+ assert "req1 - Ensure MFA" in rendered
+
+ def test_arbitrary_ids_do_not_crash(self):
+ """Non-numeric ids are sorted lexicographically without raising."""
+ df = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A"] * 3,
+ "REQUIREMENTS_ID": ["AC-2(1)", "foo-bar", "step.1.2"],
+ "STATUS": ["PASS", "FAIL", "PASS"],
+ "CHECKID": ["c1", "c2", "c3"],
+ "REGION": ["-"] * 3,
+ "ACCOUNTID": ["123"] * 3,
+ "RESOURCEID": ["r1", "r2", "r3"],
+ }
+ )
+ result = get_section_containers_generic(
+ df, "REQUIREMENTS_ATTRIBUTES_SECTION", "REQUIREMENTS_ID"
+ )
+ tables = _datatable_column_ids(result)
+ assert tables and all("CHECKID" in cols for cols in tables)
diff --git a/tests/dashboard/compliance/generic_test.py b/tests/dashboard/compliance/generic_test.py
new file mode 100644
index 0000000000..4e36833ada
--- /dev/null
+++ b/tests/dashboard/compliance/generic_test.py
@@ -0,0 +1,204 @@
+import pandas as pd
+from dash import dash_table, html
+
+from dashboard.compliance.generic import get_table
+
+
+def _make_minimal_df(**extra_cols):
+ """Create a minimal valid DataFrame for get_table tests."""
+ data = {
+ "REQUIREMENTS_ID": ["req1"],
+ "STATUS": ["PASS"],
+ "CHECKID": ["check1"],
+ "REGION": ["us-east-1"],
+ "ACCOUNTID": ["123456789"],
+ "RESOURCEID": ["res1"],
+ }
+ data.update(extra_cols)
+ return pd.DataFrame(data)
+
+
+def _datatable_column_ids(component):
+ """Collect the column ids of every DataTable in a Dash component tree."""
+ if isinstance(component, dash_table.DataTable):
+ return [[c["id"] for c in component.columns]]
+ children = getattr(component, "children", None)
+ if children is None:
+ return []
+ if not isinstance(children, (list, tuple)):
+ children = [children]
+ return [cols for child in children for cols in _datatable_column_ids(child)]
+
+
+class TestGetTable:
+ def test_groups_by_section(self):
+ """SC-001a: df with REQUIREMENTS_ATTRIBUTES_SECTION returns Div grouped by section."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": [
+ "Section A",
+ "Section A",
+ "Section A",
+ "Section B",
+ "Section B",
+ ],
+ "REQUIREMENTS_ID": [
+ "ctrl-alpha",
+ "ctrl-alpha",
+ "ctrl-alpha",
+ "ctrl-beta",
+ "ctrl-beta",
+ ],
+ "STATUS": ["PASS", "FAIL", "PASS", "FAIL", "FAIL"],
+ "CHECKID": ["check1", "check2", "check3", "check4", "check5"],
+ "REGION": ["us-east-1"] * 5,
+ "ACCOUNTID": ["123"] * 5,
+ "RESOURCEID": ["res1", "res2", "res3", "res4", "res5"],
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+ assert result.className == "compliance-data-layout"
+ assert len(result.children) == 2 # one container per distinct section
+
+ def test_flat_fallback_no_attributes(self):
+ """SC-001b: No REQUIREMENTS_ATTRIBUTES_* cols → grouped by REQUIREMENTS_ID."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ID": ["req1", "req1", "req2"],
+ "STATUS": ["PASS", "FAIL", "FAIL"],
+ "CHECKID": ["check1", "check2", "check3"],
+ "REGION": ["us-east-1"] * 3,
+ "ACCOUNTID": ["123"] * 3,
+ "RESOURCEID": ["res1", "res2", "res3"],
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+ assert result.className == "compliance-data-layout"
+ # 2 distinct REQUIREMENTS_ID values → 2 group containers
+ assert len(result.children) == 2
+
+ def test_arbitrary_ids_no_crash(self):
+ """ADR-2 / R1 regression guard: non-numeric REQUIREMENTS_IDs must not raise ValueError.
+
+ get_section_containers_cis sorts by version_tuple which calls int() on each
+ dotted/dashed segment and crashes on IDs like 'AC-2(1)'. Selecting format4
+ (no version sort) is the fix. This test is a permanent guard against regression.
+ """
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ID": ["AC-2(1)", "foo-bar", "step.1.2"],
+ "STATUS": ["PASS", "FAIL", "PASS"],
+ "CHECKID": ["check1", "check2", "check3"],
+ "REGION": ["us-east-1"] * 3,
+ "ACCOUNTID": ["123"] * 3,
+ "RESOURCEID": ["res1", "res2", "res3"],
+ }
+ )
+ # Must not raise ValueError
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+
+ def test_discovers_multiple_attribute_columns(self):
+ """SC-005a: Multiple REQUIREMENTS_ATTRIBUTES_* cols present → no AttributeError;
+ component tree is non-empty."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec B"],
+ "REQUIREMENTS_ATTRIBUTES_CATEGORY": ["Cat 1", "Cat 2"],
+ "REQUIREMENTS_ATTRIBUTES_CONTROL_ID": ["C1", "C2"],
+ "REQUIREMENTS_ID": ["req1", "req2"],
+ "STATUS": ["PASS", "FAIL"],
+ "CHECKID": ["check1", "check2"],
+ "REGION": ["us-east-1"] * 2,
+ "ACCOUNTID": ["123"] * 2,
+ "RESOURCEID": ["res1", "res2"],
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+ assert result.children # non-empty component tree
+
+ def test_novel_attribute_column_names(self):
+ """SC-005b: Novel attr col names without a SECTION col → first attr col used as
+ grouping; returns a valid html.Div without any code change required."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_DOMAIN": ["Domain A", "Domain B"],
+ "REQUIREMENTS_ATTRIBUTES_SUBDOMAIN": ["Sub 1", "Sub 2"],
+ "REQUIREMENTS_ID": ["req1", "req2"],
+ "STATUS": ["PASS", "FAIL"],
+ "CHECKID": ["check1", "check2"],
+ "REGION": ["us-east-1"] * 2,
+ "ACCOUNTID": ["123"] * 2,
+ "RESOURCEID": ["res1", "res2"],
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+ assert len(result.children) > 0
+
+ def test_manual_only_requirements(self):
+ """SC-008a: All rows have STATUS='MANUAL' → returns html.Div with non-empty
+ children; result is not the 'No data found' string."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec B"],
+ "REQUIREMENTS_ID": ["req1", "req2"],
+ "STATUS": ["MANUAL", "MANUAL"],
+ "CHECKID": ["check1", "check2"],
+ "REGION": ["us-east-1"] * 2,
+ "ACCOUNTID": ["123"] * 2,
+ "RESOURCEID": ["res1", "res2"],
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+ assert not isinstance(result, str)
+ assert result.children # non-empty
+
+ def test_empty_dataframe(self):
+ """SC-009a: Zero rows with correct column schema → valid html.Div; no exception."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": pd.Series([], dtype=str),
+ "REQUIREMENTS_ID": pd.Series([], dtype=str),
+ "STATUS": pd.Series([], dtype=str),
+ "CHECKID": pd.Series([], dtype=str),
+ "REGION": pd.Series([], dtype=str),
+ "ACCOUNTID": pd.Series([], dtype=str),
+ "RESOURCEID": pd.Series([], dtype=str),
+ }
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+
+ def test_get_table_returns_html_div(self):
+ """SC-012a: Smoke test — isinstance(get_table(df), html.Div) is True."""
+ data = _make_minimal_df(
+ REQUIREMENTS_ATTRIBUTES_SECTION=["Sec A"],
+ )
+ result = get_table(data)
+ assert isinstance(result, html.Div)
+
+
+class TestNestedRendering:
+ def test_section_and_requirement_id_are_separate_levels(self):
+ """Section is the outer level; requirement id + description the inner."""
+ data = _make_minimal_df(
+ REQUIREMENTS_ATTRIBUTES_SECTION=["3 Compute Services"],
+ REQUIREMENTS_DESCRIPTION=["Ensure only MFA enabled identities"],
+ )
+ rendered = str(get_table(data))
+ assert "3 Compute Services" in rendered
+ assert "req1 - Ensure only MFA enabled identities" in rendered
+
+ def test_checks_table_is_nested_under_requirement(self):
+ """The checks table sits at the innermost level."""
+ data = _make_minimal_df(
+ REQUIREMENTS_ATTRIBUTES_SECTION=["Sec A"],
+ REQUIREMENTS_DESCRIPTION=["Some requirement"],
+ )
+ tables = _datatable_column_ids(get_table(data))
+ assert tables and all("CHECKID" in cols for cols in tables)
diff --git a/tests/dashboard/pages/compliance_dispatch_test.py b/tests/dashboard/pages/compliance_dispatch_test.py
new file mode 100644
index 0000000000..78bd88ce68
--- /dev/null
+++ b/tests/dashboard/pages/compliance_dispatch_test.py
@@ -0,0 +1,179 @@
+from unittest.mock import MagicMock, patch
+
+import pandas as pd
+import pytest
+from dash import html
+
+from dashboard.pages.compliance import _dispatch_compliance_renderer
+
+
+def _make_dispatch_df(**extra_cols):
+ """Minimal DataFrame with the columns required by the dedup step."""
+ data = {
+ "REQUIREMENTS_ID": ["req1", "req2"],
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec A"],
+ "STATUS": ["PASS", "FAIL"],
+ "CHECKID": ["check1", "check2"],
+ "RESOURCEID": ["res1", "res2"],
+ "STATUSEXTENDED": ["", ""],
+ "REGION": ["us-east-1", "us-east-1"],
+ "ACCOUNTID": ["123456789", "123456789"],
+ }
+ data.update(extra_cols)
+ return pd.DataFrame(data)
+
+
+class TestDispatchComplianceRenderer:
+ def test_builtin_name_uses_builtin_module(self):
+ """SC-002a: analytics_input='cis_4_0_aws' resolves real builtin module;
+ returns (html.Div, DataFrame) 2-tuple."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ID": ["1.1", "1.2"],
+ "REQUIREMENTS_DESCRIPTION": ["Description 1", "Description 2"],
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Section A", "Section A"],
+ "CHECKID": ["check1", "check2"],
+ "STATUS": ["PASS", "FAIL"],
+ "REGION": ["us-east-1", "us-east-1"],
+ "ACCOUNTID": ["123456789", "123456789"],
+ "RESOURCEID": ["res1", "res2"],
+ "STATUSEXTENDED": ["Pass", "Fail"],
+ }
+ )
+ table, result_data = _dispatch_compliance_renderer(data, "cis_4_0_aws")
+ assert isinstance(table, html.Div)
+ assert isinstance(result_data, pd.DataFrame)
+
+ def test_unknown_name_falls_back_to_generic(self):
+ """SC-003a: Unknown analytics_input raises ModuleNotFoundError → generic
+ fallback is called with the deduped dataframe."""
+ data = _make_dispatch_df()
+ sentinel = MagicMock(
+ return_value=html.Div([], className="compliance-data-layout")
+ )
+
+ with patch("dashboard.compliance.generic.get_table", sentinel):
+ table, result_data = _dispatch_compliance_renderer(data, "myfw_dynprovider")
+
+ sentinel.assert_called_once()
+ assert isinstance(table, html.Div)
+ assert isinstance(result_data, pd.DataFrame)
+
+ def test_import_error_is_not_swallowed(self):
+ """SC-003b: ImportError (NOT ModuleNotFoundError) is re-raised; except clause
+ is exact — only ModuleNotFoundError routes to generic."""
+ data = _make_dispatch_df()
+
+ with patch(
+ "dashboard.pages.compliance.importlib.import_module",
+ side_effect=ImportError("custom error"),
+ ):
+ with pytest.raises(ImportError, match="custom error"):
+ _dispatch_compliance_renderer(data, "anything")
+
+ def test_get_table_error_in_generic_surfaces(self):
+ """SC-004a: ValueError from generic.get_table propagates (not swallowed);
+ get_table is called OUTSIDE the try block."""
+ data = _make_dispatch_df()
+
+ with patch(
+ "dashboard.compliance.generic.get_table",
+ side_effect=ValueError("boom"),
+ ):
+ with pytest.raises(ValueError, match="boom"):
+ _dispatch_compliance_renderer(data, "myfw_dynprovider")
+
+ def test_get_table_error_in_builtin_surfaces(self):
+ """REQ-004 / ADR-1: RuntimeError from a builtin get_table propagates;
+ proving get_table is called outside the try block."""
+ data = _make_dispatch_df()
+ mock_module = MagicMock()
+ mock_module.get_table.side_effect = RuntimeError("table error")
+
+ with patch(
+ "dashboard.pages.compliance.importlib.import_module",
+ return_value=mock_module,
+ ):
+ with pytest.raises(RuntimeError, match="table error"):
+ _dispatch_compliance_renderer(data, "some_builtin_fw")
+
+ def test_dedup_applied_before_get_table(self):
+ """ADR-1: Duplicate rows (identical CHECKID/STATUS/RESOURCEID/STATUSEXTENDED)
+ are dropped; returned data has the deduplicated row count."""
+ # Row 0 and row 1 are identical in all dedup-key columns; row 2 is unique.
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec A", "Sec B"],
+ "REQUIREMENTS_ID": ["req1", "req1", "req2"],
+ "STATUS": ["PASS", "PASS", "FAIL"],
+ "CHECKID": ["check1", "check1", "check2"],
+ "RESOURCEID": ["res1", "res1", "res2"],
+ "STATUSEXTENDED": ["", "", ""],
+ "REGION": ["us-east-1"] * 3,
+ "ACCOUNTID": ["123"] * 3,
+ }
+ )
+ mock_module = MagicMock()
+ mock_module.get_table.return_value = html.Div([])
+
+ with patch(
+ "dashboard.pages.compliance.importlib.import_module",
+ return_value=mock_module,
+ ):
+ table, result_data = _dispatch_compliance_renderer(data, "some_fw")
+
+ assert len(result_data) == 2 # one duplicate removed
+
+ def test_muted_column_added_to_dedup_when_present(self):
+ """ADR-1 edge case: When MUTED column is present, it is included in the dedup
+ subset at index 2; rows differing only in MUTED are kept as distinct rows."""
+ # Both rows share CHECKID/STATUS/RESOURCEID/STATUSEXTENDED but differ in MUTED.
+ # With MUTED in dedup_columns, both rows are kept (2 rows after dedup).
+ # Without MUTED in dedup_columns, they would be collapsed to 1 row.
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Sec A", "Sec A"],
+ "REQUIREMENTS_ID": ["req1", "req1"],
+ "STATUS": ["PASS", "PASS"],
+ "CHECKID": ["check1", "check1"],
+ "RESOURCEID": ["res1", "res1"],
+ "STATUSEXTENDED": ["", ""],
+ "MUTED": ["True", "False"],
+ "REGION": ["us-east-1", "us-east-1"],
+ "ACCOUNTID": ["123", "123"],
+ }
+ )
+ mock_module = MagicMock()
+ mock_module.get_table.return_value = html.Div([])
+
+ with patch(
+ "dashboard.pages.compliance.importlib.import_module",
+ return_value=mock_module,
+ ):
+ table, result_data = _dispatch_compliance_renderer(data, "some_fw")
+
+ # MUTED at idx 2 means these two rows have different dedup keys → both kept
+ assert len(result_data) == 2
+
+ def test_returns_table_and_data_tuple(self):
+ """ADR-1 interface contract: _dispatch_compliance_renderer returns a
+ 2-tuple (table, deduped_data)."""
+ data = pd.DataFrame(
+ {
+ "REQUIREMENTS_ID": ["1.1", "1.2"],
+ "REQUIREMENTS_DESCRIPTION": ["Desc 1", "Desc 2"],
+ "REQUIREMENTS_ATTRIBUTES_SECTION": ["Section A", "Section A"],
+ "CHECKID": ["check1", "check2"],
+ "STATUS": ["PASS", "FAIL"],
+ "REGION": ["us-east-1", "us-east-1"],
+ "ACCOUNTID": ["123456789", "123456789"],
+ "RESOURCEID": ["res1", "res2"],
+ "STATUSEXTENDED": ["", ""],
+ }
+ )
+ result = _dispatch_compliance_renderer(data, "cis_4_0_aws")
+ assert isinstance(result, tuple)
+ assert len(result) == 2
+ table, deduped_data = result
+ assert isinstance(table, html.Div)
+ assert isinstance(deduped_data, pd.DataFrame)
diff --git a/tests/dashboard/pages/conftest.py b/tests/dashboard/pages/conftest.py
new file mode 100644
index 0000000000..a5c674c7de
--- /dev/null
+++ b/tests/dashboard/pages/conftest.py
@@ -0,0 +1,7 @@
+import dash
+
+# Initialize a minimal Dash app so that dashboard page modules can call
+# dash.register_page() during import without raising PageError.
+# This module-level initialization runs during pytest collection, before
+# any test file in this directory is imported.
+_test_app = dash.Dash("prowler_test_app", use_pages=True, pages_folder="")
diff --git a/tests/dashboard/pages/scope_columns_test.py b/tests/dashboard/pages/scope_columns_test.py
new file mode 100644
index 0000000000..a8aea34221
--- /dev/null
+++ b/tests/dashboard/pages/scope_columns_test.py
@@ -0,0 +1,60 @@
+import pandas as pd
+
+from dashboard.pages.compliance import _ensure_scope_columns
+
+
+def _df(columns):
+ """Build a one-row DataFrame preserving the given column order."""
+ return pd.DataFrame({col: ["x"] for col in columns})
+
+
+class TestEnsureScopeColumns:
+ def test_aws_account_and_region_preserved(self):
+ """A provider that already emits ACCOUNTID and REGION is left untouched."""
+ df = _df(["PROVIDER", "DESCRIPTION", "ACCOUNTID", "REGION", "ASSESSMENTDATE"])
+ result = _ensure_scope_columns(df)
+ assert "ACCOUNTID" in result.columns
+ assert "REGION" in result.columns
+ assert result["ACCOUNTID"].iloc[0] == "x"
+
+ def test_okta_single_scope_column_becomes_accountid(self):
+ """Okta's ORGANIZATIONDOMAIN becomes ACCOUNTID; REGION falls back."""
+ df = _df(["PROVIDER", "DESCRIPTION", "ORGANIZATIONDOMAIN", "ASSESSMENTDATE"])
+ df["ORGANIZATIONDOMAIN"] = ["trial-123.okta.com"]
+ result = _ensure_scope_columns(df)
+ assert "ACCOUNTID" in result.columns
+ assert "ORGANIZATIONDOMAIN" not in result.columns
+ assert result["ACCOUNTID"].iloc[0] == "trial-123.okta.com"
+ assert result["REGION"].iloc[0] == "-"
+
+ def test_two_unknown_scope_columns_map_to_account_and_region(self):
+ """Two scope columns map positionally to ACCOUNTID and REGION."""
+ df = _df(["PROVIDER", "DESCRIPTION", "TENANCYID", "LOCATION", "ASSESSMENTDATE"])
+ df["TENANCYID"] = ["tenant-1"]
+ df["LOCATION"] = ["eu-west-1"]
+ result = _ensure_scope_columns(df)
+ assert result["ACCOUNTID"].iloc[0] == "tenant-1"
+ assert result["REGION"].iloc[0] == "eu-west-1"
+
+ def test_no_scope_columns_fall_back_to_dash(self):
+ """No scope columns → both ACCOUNTID and REGION fall back to '-'."""
+ df = _df(["PROVIDER", "DESCRIPTION", "ASSESSMENTDATE"])
+ result = _ensure_scope_columns(df)
+ assert result["ACCOUNTID"].iloc[0] == "-"
+ assert result["REGION"].iloc[0] == "-"
+
+ def test_missing_anchors_still_fall_back_to_dash(self):
+ """Without DESCRIPTION/ASSESSMENTDATE anchors, both fall back to '-'."""
+ df = _df(["PROVIDER", "FOO", "BAR"])
+ result = _ensure_scope_columns(df)
+ assert result["ACCOUNTID"].iloc[0] == "-"
+ assert result["REGION"].iloc[0] == "-"
+
+ def test_existing_accountid_does_not_consume_region_scope(self):
+ """An existing ACCOUNTID is kept; the leftover scope becomes REGION."""
+ df = _df(["PROVIDER", "DESCRIPTION", "ACCOUNTID", "LOCATION", "ASSESSMENTDATE"])
+ df["ACCOUNTID"] = ["acc-1"]
+ df["LOCATION"] = ["us-east-2"]
+ result = _ensure_scope_columns(df)
+ assert result["ACCOUNTID"].iloc[0] == "acc-1"
+ assert result["REGION"].iloc[0] == "us-east-2"
diff --git a/tests/github/changelog_attribution_test.py b/tests/github/changelog_attribution_test.py
new file mode 100644
index 0000000000..9cd8d016f0
--- /dev/null
+++ b/tests/github/changelog_attribution_test.py
@@ -0,0 +1,178 @@
+import importlib.util
+import shutil
+import sys
+from pathlib import Path
+
+MODULE_PATH = (
+ Path(__file__).resolve().parents[2]
+ / ".github"
+ / "scripts"
+ / "changelog_attribution.py"
+)
+SPEC = importlib.util.spec_from_file_location("changelog_attribution", MODULE_PATH)
+changelog_attribution = importlib.util.module_from_spec(SPEC)
+assert SPEC.loader is not None
+SPEC.loader.exec_module(changelog_attribution)
+
+
+def make_component(tmp_path):
+ component = tmp_path / "prowler"
+ fragments_dir = component / "changelog.d"
+ fragments_dir.mkdir(parents=True)
+ return component, fragments_dir
+
+
+def fake_git_mv(*args):
+ if args[0] != "mv":
+ raise AssertionError(f"Unexpected git command: {args}")
+ shutil.move(args[1], args[2])
+ return ""
+
+
+def fail_git(*args):
+ raise AssertionError(f"Unexpected git command: {args}")
+
+
+def fail_api(*args):
+ raise AssertionError(f"Unexpected GitHub API call: {args}")
+
+
+def run_main(monkeypatch, component, *extra_args):
+ monkeypatch.setattr(
+ sys,
+ "argv",
+ ["changelog_attribution.py", str(component), *extra_args],
+ )
+ return changelog_attribution.main()
+
+
+class TestChangelogAttribution:
+ def test_renames_slug_fragment_to_resolved_pr_number(self, tmp_path, monkeypatch):
+ component, fragments_dir = make_component(tmp_path)
+ fragment = fragments_dir / "add-workflow.fixed.md"
+ fragment.write_text("Fix changelog workflow.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution, "find_adding_commit", lambda path: "abc123"
+ )
+ monkeypatch.setattr(
+ changelog_attribution, "pr_from_api", lambda repo, sha: 11572
+ )
+ monkeypatch.setattr(changelog_attribution, "git", fake_git_mv)
+
+ assert run_main(monkeypatch, component) == 0
+ assert not fragment.exists()
+ assert (fragments_dir / "11572.fixed.md").read_text() == (
+ "Fix changelog workflow.\n"
+ )
+
+ def test_appends_counter_when_pr_fragment_already_exists(
+ self, tmp_path, monkeypatch
+ ):
+ component, fragments_dir = make_component(tmp_path)
+ (fragments_dir / "11572.fixed.md").write_text("Existing fix.\n")
+ fragment = fragments_dir / "another-fix.fixed.md"
+ fragment.write_text("Another fix.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution, "find_adding_commit", lambda path: "abc123"
+ )
+ monkeypatch.setattr(
+ changelog_attribution, "pr_from_api", lambda repo, sha: 11572
+ )
+ monkeypatch.setattr(changelog_attribution, "git", fake_git_mv)
+
+ assert run_main(monkeypatch, component) == 0
+ assert (fragments_dir / "11572.fixed.md").read_text() == "Existing fix.\n"
+ assert (fragments_dir / "11572.fixed.1.md").read_text() == "Another fix.\n"
+
+ def test_uses_subject_fallback_when_api_is_disabled(self, tmp_path, monkeypatch):
+ component, fragments_dir = make_component(tmp_path)
+ fragment = fragments_dir / "fallback.added.md"
+ fragment.write_text("Add fallback behavior.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution, "find_adding_commit", lambda path: "abc123"
+ )
+ monkeypatch.setattr(
+ changelog_attribution,
+ "pr_from_api",
+ fail_api,
+ )
+ monkeypatch.setattr(changelog_attribution, "pr_from_subject", lambda sha: 42)
+ monkeypatch.setattr(changelog_attribution, "git", fake_git_mv)
+
+ assert run_main(monkeypatch, component, "--no-api") == 0
+ assert not fragment.exists()
+ assert (fragments_dir / "42.added.md").read_text() == "Add fallback behavior.\n"
+
+ def test_renames_unresolved_fragment_to_orphan(self, tmp_path, monkeypatch, capsys):
+ component, fragments_dir = make_component(tmp_path)
+ fragment = fragments_dir / "manual.changed.md"
+ fragment.write_text("Change manual entry.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution, "find_adding_commit", lambda path: None
+ )
+ monkeypatch.setattr(changelog_attribution, "git", fake_git_mv)
+
+ assert run_main(monkeypatch, component) == 0
+ assert not fragment.exists()
+ assert (fragments_dir / "+manual.changed.md").read_text() == (
+ "Change manual entry.\n"
+ )
+ assert "Could not resolve a PR" in capsys.readouterr().out
+
+ def test_rejects_malformed_fragment_names(self, tmp_path, monkeypatch, capsys):
+ component, fragments_dir = make_component(tmp_path)
+ fragment = fragments_dir / "bad.bugfix.md"
+ fragment.write_text("Invalid type.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution,
+ "git",
+ fail_git,
+ )
+
+ assert run_main(monkeypatch, component) == 1
+ assert fragment.exists()
+ assert "Malformed fragment filename" in capsys.readouterr().out
+
+ def test_rejects_malformed_names_before_renaming_any_fragment(
+ self, tmp_path, monkeypatch, capsys
+ ):
+ component, fragments_dir = make_component(tmp_path)
+ valid_fragment = fragments_dir / "valid.fixed.md"
+ malformed_fragment = fragments_dir / "bad.bugfix.md"
+ valid_fragment.write_text("Valid fix.\n")
+ malformed_fragment.write_text("Invalid type.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution, "find_adding_commit", lambda path: "abc123"
+ )
+ monkeypatch.setattr(
+ changelog_attribution, "pr_from_api", lambda repo, sha: 11572
+ )
+ monkeypatch.setattr(changelog_attribution, "git", fail_git)
+
+ assert run_main(monkeypatch, component) == 1
+ assert valid_fragment.read_text() == "Valid fix.\n"
+ assert malformed_fragment.read_text() == "Invalid type.\n"
+ assert not (fragments_dir / "11572.fixed.md").exists()
+ assert "Malformed fragment filename" in capsys.readouterr().out
+
+ def test_skips_fragments_that_already_start_with_pr_number(
+ self, tmp_path, monkeypatch
+ ):
+ component, fragments_dir = make_component(tmp_path)
+ fragment = fragments_dir / "11572.added.md"
+ fragment.write_text("Already attributed.\n")
+
+ monkeypatch.setattr(
+ changelog_attribution,
+ "git",
+ fail_git,
+ )
+
+ assert run_main(monkeypatch, component) == 0
+ assert fragment.read_text() == "Already attributed.\n"
diff --git a/tests/github/changelog_fragments_test.py b/tests/github/changelog_fragments_test.py
new file mode 100644
index 0000000000..05a751125e
--- /dev/null
+++ b/tests/github/changelog_fragments_test.py
@@ -0,0 +1,379 @@
+import re
+import subprocess
+import sys
+import tomllib
+from pathlib import Path
+
+import pytest
+
+REPO_ROOT = Path(__file__).resolve().parents[2]
+EXPECTED_CHANGELOG_TYPE_ORDER = [
+ "added",
+ "changed",
+ "deprecated",
+ "removed",
+ "fixed",
+ "security",
+]
+EXPECTED_CHANGELOG_SECTION_NAMES = [
+ "🚀 Added",
+ "🔄 Changed",
+ "⚠️ Deprecated",
+ "❌ Removed",
+ "🐞 Fixed",
+ "🔐 Security",
+]
+COMPONENTS = ["prowler", "api", "ui", "mcp_server"]
+
+
+def read_workflow(name):
+ return (REPO_ROOT / ".github" / "workflows" / name).read_text()
+
+
+def render_towncrier(tmp_path, type_definitions, fragments):
+ pytest.importorskip("towncrier")
+
+ fragments_dir = tmp_path / "changelog.d"
+ fragments_dir.mkdir()
+ (tmp_path / "CHANGELOG.md").write_text(
+ "# Changelog\n\n<!-- changelog: release notes start -->\n"
+ )
+ for filename, content in fragments.items():
+ (fragments_dir / filename).write_text(f"{content}\n")
+
+ type_config = "\n".join(
+ "\n".join(
+ [
+ "[[tool.towncrier.type]]",
+ f'directory = "{directory}"',
+ f'name = "{name}"',
+ "showcontent = true",
+ ]
+ )
+ for directory, name in type_definitions
+ )
+ config = "\n".join(
+ [
+ "[tool.towncrier]",
+ 'directory = "changelog.d"',
+ 'filename = "CHANGELOG.md"',
+ 'start_string = "<!-- changelog: release notes start -->\\n"',
+ f'template = "{(REPO_ROOT / ".github/towncrier/template.md.jinja").as_posix()}"',
+ 'title_format = "## [{version}] ({name})"',
+ 'issue_format = "[(#{issue})](https://example.com/pull/{issue})"',
+ 'underlines = ["", "", ""]',
+ type_config,
+ ]
+ )
+ config_path = tmp_path / "towncrier.toml"
+ config_path.write_text(config)
+
+ result = subprocess.run(
+ [
+ sys.executable,
+ "-m",
+ "towncrier",
+ "build",
+ "--config",
+ str(config_path),
+ "--version",
+ "0.1.0",
+ "--name",
+ "Test",
+ "--draft",
+ ],
+ cwd=tmp_path,
+ check=True,
+ capture_output=True,
+ text=True,
+ )
+ return result.stdout.split("## [0.1.0] (Test)", 1)[1]
+
+
+def test_towncrier_template_uses_configured_changelog_section_order(tmp_path):
+ template = (REPO_ROOT / ".github/towncrier/template.md.jinja").read_text()
+
+ assert "{% set category_order = definitions.keys() %}" in template
+ assert (
+ "{% for category in category_order if category in sections[section] %}"
+ in template
+ )
+ assert "definitions.items()" not in template
+ assert (
+ '["added", "changed", "deprecated", "removed", "fixed", "security"]'
+ not in template
+ )
+
+ output = render_towncrier(
+ tmp_path,
+ [("fixed", "Fixed"), ("added", "Added"), ("custom", "Custom")],
+ {
+ "1.added.md": "Entry one",
+ "2.added.md": "Entry two",
+ "3.fixed.md": "Fix entry",
+ "4.custom.md": "Custom entry",
+ },
+ )
+
+ headings = re.findall(r"^### (.+)$", output, re.MULTILINE)
+ assert headings == ["Fixed", "Added", "Custom"]
+ assert (
+ "- Entry one [(#1)](https://example.com/pull/1)\n"
+ "- Entry two [(#2)](https://example.com/pull/2)"
+ ) in output
+ assert (
+ "- Entry one [(#1)](https://example.com/pull/1)\n\n"
+ "- Entry two [(#2)](https://example.com/pull/2)"
+ ) not in output
+
+
+def test_component_towncrier_configs_keep_changelog_section_order():
+ for component in COMPONENTS:
+ config = tomllib.loads((REPO_ROOT / component / "towncrier.toml").read_text())
+ type_definitions = config["tool"]["towncrier"]["type"]
+
+ assert [item["directory"] for item in type_definitions] == (
+ EXPECTED_CHANGELOG_TYPE_ORDER
+ )
+ assert [item["name"] for item in type_definitions] == (
+ EXPECTED_CHANGELOG_SECTION_NAMES
+ )
+
+
+def test_pull_request_template_links_to_all_fragment_locations():
+ template = (REPO_ROOT / ".github/pull_request_template.md").read_text()
+
+ assert "[Prowler Community Slack](https://goto.prowler.com/slack)" in template
+ assert "[Prowler Community Slack](goto.prowler.com/slack)" not in template
+ for component in COMPONENTS:
+ assert f"{component}/changelog.d/" in template
+
+
+def test_changelog_gate_rejects_direct_changelog_edits():
+ workflow = read_workflow("pr-check-changelog.yml")
+ has_update = re.search(
+ r"(?ms)^\s*has_changelog_update\(\) \{\n(?P<body>.*?)^\s*\}\n",
+ workflow,
+ )
+
+ assert has_update is not None
+ assert "CHANGELOG.md" not in has_update.group("body")
+ assert "handwritten_changelogs" in workflow
+ assert "Direct CHANGELOG.md edits are not allowed" in workflow
+ assert "direct CHANGELOG.md edit" not in workflow
+
+
+def test_changelog_gate_tests_compile_workflow_changes():
+ workflow = read_workflow("pr-check-changelog.yml")
+
+ assert ".github/workflows/compile-changelogs.yml" in workflow
+
+
+def test_changelog_attribution_tests_use_pinned_python():
+ workflow = read_workflow("pr-check-changelog.yml")
+ match = re.search(
+ r"(?ms)^ test-changelog-attribution:\n(?P<body>.*?)^ check-changelog:",
+ workflow,
+ )
+
+ assert match is not None
+ job = match.group("body")
+ assert "uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c" in job
+ assert "python-version: '3.12'" in job
+ assert "python3 -m pip install" in job
+ assert "python3 -m pytest tests/github" in job
+ assert "objects.githubusercontent.com:443" in job
+
+
+def test_changelog_gate_rejects_common_manual_pr_link_forms():
+ workflow = read_workflow("pr-check-changelog.yml")
+
+ assert "manual_pr_link_re=" in workflow
+ assert r"\[\(#[0-9]+\)\]" in workflow
+ assert r"\[#[0-9]+\]\(" in workflow
+ assert r"\(#[0-9]+\)" in workflow
+ assert r"github\.com/[^[:space:]/]+/[^[:space:]/]+/(pull|issues)/[0-9]+" in workflow
+
+
+def test_changelog_gate_derives_fragment_paths_from_monitored_folders():
+ workflow = read_workflow("pr-check-changelog.yml")
+
+ assert "folder_alt=$(echo \"$MONITORED_FOLDERS\" | tr ' ' '|')" in workflow
+ assert "^(api|ui|prowler|mcp_server)/changelog\\.d/" not in workflow
+
+
+def test_changelog_gate_lints_renamed_fragments():
+ workflow = read_workflow("pr-check-changelog.yml")
+
+ assert "STEPS_CHANGED_FILES_OUTPUTS_RENAMED_FILES" in workflow
+ assert "${{ steps.changed-files.outputs.renamed_files }}" in workflow
+ assert "added_or_renamed=" in workflow
+ assert "added_modified_or_renamed=" in workflow
+ assert (
+ 'echo "$added_or_renamed" | grep -E "^(${folder_alt})/changelog\\.d/"'
+ in workflow
+ )
+ assert (
+ 'echo "$added_modified_or_renamed" | grep -E "^(${folder_alt})/changelog\\.d/"'
+ in workflow
+ )
+
+
+def test_changelog_gate_uses_random_github_output_delimiters():
+ workflow = read_workflow("pr-check-changelog.yml")
+
+ assert "write_multiline_output()" in workflow
+ assert "openssl rand -hex 16" in workflow
+ assert '>> "$GITHUB_OUTPUT"' in workflow
+ assert "<<EOF" not in workflow
+
+
+def test_compile_workflow_blocks_egress_for_privileged_job():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert "Harden the runner (Block outbound calls)" in workflow
+ assert "egress-policy: block" in workflow
+ for endpoint in [
+ "api.github.com:443",
+ "github.com:443",
+ "objects.githubusercontent.com:443",
+ "pypi.org:443",
+ "files.pythonhosted.org:443",
+ ]:
+ assert endpoint in workflow
+
+
+def test_forward_sync_inserts_release_blocks_by_prowler_version_order():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert "insert_changelog_block_ordered()" in workflow
+ assert 'incoming_release=$(release_from_heading "$incoming_heading")' in workflow
+ assert 'incoming_key=$(version_key "$incoming_release")' in workflow
+ assert '[[ "$incoming_key" > "$existing_key" ]]' in workflow
+ assert "already contains a block for Prowler v${incoming_release}" in workflow
+ assert 'head -n "$marker_line" "$component/CHANGELOG.md"' not in workflow
+
+
+def test_compile_workflow_rejects_explicit_versions_that_do_not_bump():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert 'current=$(latest_released_version "$component")' in workflow
+ assert 'current_key=$(version_key "$current")' in workflow
+ assert 'effective_key=$(version_key "$effective")' in workflow
+ assert (
+ '[[ "$effective_key" < "$current_key" || "$effective_key" == "$current_key" ]]'
+ in workflow
+ )
+ assert (
+ "explicit version '${effective}' must be greater than the latest released version"
+ in workflow
+ )
+
+
+def test_compile_workflow_requires_target_branch_to_match_prowler_version():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert (
+ 'IFS=. read -r prowler_major prowler_minor prowler_patch <<< "$PROWLER_VERSION"'
+ in workflow
+ )
+ assert "prowler_patch=$((10#$prowler_patch))" in workflow
+ assert 'if [ "$prowler_patch" -eq 0 ]; then' in workflow
+ assert "target_branch must be 'master' for Prowler ${PROWLER_VERSION}" in workflow
+ assert 'expected_target_branch="v${prowler_major}.${prowler_minor}"' in workflow
+ assert 'if [ "$TARGET_BRANCH" != "$expected_target_branch" ]; then' in workflow
+ assert (
+ "target_branch must be '${expected_target_branch}' for Prowler ${PROWLER_VERSION}"
+ in workflow
+ )
+
+
+def test_compile_workflow_normalizes_version_segments_before_arithmetic():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert (
+ 'printf \'%06d.%06d.%06d\' "$((10#$major))" "$((10#$minor))" "$((10#$patch))"'
+ in workflow
+ )
+ assert "major=$((10#$major))" in workflow
+ assert "minor=$((10#$minor))" in workflow
+ assert "patch=$((10#$patch))" in workflow
+ assert "current_major=$((10#$current_major))" in workflow
+ assert "effective_major=$((10#$effective_major))" in workflow
+ assert "effective_minor=$((10#$effective_minor))" in workflow
+ assert "effective_patch=$((10#$effective_patch))" in workflow
+
+
+def test_compile_workflow_requires_removed_fragments_in_major_releases():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert "has_removed_fragments" in workflow
+ assert "removed fragments require a major component release" in workflow
+ assert "effective_major" in workflow
+ assert "effective_minor" in workflow
+ assert "effective_patch" in workflow
+
+
+def test_compile_workflow_prs_skip_cloud_sync():
+ workflow = read_workflow("compile-changelogs.yml")
+ labels_blocks = re.findall(r"labels: \|\n((?:\s+[a-z-]+\n)+)", workflow)
+
+ assert len(labels_blocks) == 2
+ for block in labels_blocks:
+ assert "no-changelog" in block.split()
+ assert "skip-sync" in block.split()
+
+
+def test_compile_workflow_auto_derives_versions_by_mirroring_prowler_version():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert 'prowler) effective="$PROWLER_VERSION" ;;' in workflow
+ assert 'ui) effective="1.${prowler_minor}.${prowler_patch}" ;;' in workflow
+ assert 'api) effective="1.$((prowler_minor + 1)).${prowler_patch}" ;;' in workflow
+ assert (
+ "auto-derived version '${effective}' is not greater than the latest released version"
+ in workflow
+ )
+
+
+def test_compile_workflow_auto_derives_mcp_patch_bumps_on_patch_releases():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert "'added'/'deprecated' fragments are shipping in a Prowler patch" in workflow
+ assert (
+ "elif echo \"$fragments\" | grep -qE '\\.(added|changed|deprecated)(\\.[0-9]+)?\\.md$'; then"
+ in workflow
+ )
+
+
+def test_forward_sync_pads_release_blocks_with_blank_lines():
+ workflow = read_workflow("compile-changelogs.yml")
+
+ assert "block-normalized.md" in workflow
+ assert 'total_lines=$(wc -l < "$changelog")' in workflow
+ assert '[ -n "$(sed -n "$((insertion_line - 1))p" "$changelog")" ]' in workflow
+ assert 'if [ "$insertion_line" -le "$total_lines" ]; then' in workflow
+
+
+def test_component_changelogs_separate_release_blocks_with_blank_lines():
+ for component in COMPONENTS:
+ lines = (REPO_ROOT / component / "CHANGELOG.md").read_text().splitlines()
+ marker_line = lines.index("<!-- changelog: release notes start -->")
+
+ assert (
+ lines[marker_line + 1] == ""
+ ), f"{component}/CHANGELOG.md: expected a blank line after the marker"
+ assert (
+ lines[marker_line + 2] != ""
+ ), f"{component}/CHANGELOG.md: expected a single blank line after the marker"
+ for index, line in enumerate(lines):
+ if line == "---" and index + 1 < len(lines):
+ assert lines[index + 1] == "", (
+ f"{component}/CHANGELOG.md line {index + 2}: "
+ "expected a blank line after '---'"
+ )
+ if line.startswith("## ["):
+ assert lines[index - 1] == "", (
+ f"{component}/CHANGELOG.md line {index}: "
+ "expected a blank line before a release heading"
+ )
diff --git a/tests/lib/check/compliance_check_test.py b/tests/lib/check/compliance_check_test.py
index 73f93e3b38..631c134302 100644
--- a/tests/lib/check/compliance_check_test.py
+++ b/tests/lib/check/compliance_check_test.py
@@ -540,7 +540,9 @@ class TestCompliance:
):
object = mock.Mock()
object.path = "/path/to/compliance"
- object.name = "framework1_aws"
+ # list_compliance_modules yields dotted module names; get_bulk matches
+ # the last segment exactly against the provider.
+ object.name = "prowler.compliance.aws"
mock_list_modules.return_value = [object]
mock_listdir.return_value = ["framework1_aws.json"]
diff --git a/tests/lib/check/compliance_config_constraint_model_test.py b/tests/lib/check/compliance_config_constraint_model_test.py
new file mode 100644
index 0000000000..48f67fd504
--- /dev/null
+++ b/tests/lib/check/compliance_config_constraint_model_test.py
@@ -0,0 +1,169 @@
+"""Validation coverage for the ConfigRequirements schema.
+
+``Compliance_Requirement_ConfigConstraint`` is the model behind every
+``ConfigRequirements`` entry in the compliance framework JSONs. These tests pin
+the operator vocabulary, the value-typing rules (notably that booleans are not
+coerced to integers), and that constraints survive the legacy → universal
+adaptation used by the App backend and the OCSF/table outputs.
+"""
+
+import json
+import pathlib
+
+import pytest
+from pydantic.v1 import ValidationError
+
+from prowler.lib.check.compliance_models import (
+ Compliance,
+ Compliance_Requirement_ConfigConstraint,
+ adapt_legacy_to_universal,
+)
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[3]
+_CIS_6_0 = _REPO_ROOT / "prowler" / "compliance" / "aws" / "cis_6.0_aws.json"
+
+
+def _load_cis():
+ """Load the CIS 6.0 AWS framework JSON via a context manager."""
+ with open(_CIS_6_0, encoding="utf-8") as f:
+ return json.load(f)
+
+
+class Test_Compliance_Requirement_ConfigConstraint:
+ @pytest.mark.parametrize(
+ "operator,value",
+ [
+ ("lte", 45),
+ ("gte", 365),
+ ("eq", False),
+ ("in", [1, 2, 3]),
+ ("subset", ["1.2", "1.3"]),
+ ("superset", ["RSA-1024", "P-192"]),
+ ],
+ )
+ def test_valid_operators(self, operator, value):
+ c = Compliance_Requirement_ConfigConstraint(
+ Check="some_check", ConfigKey="some_key", Operator=operator, Value=value
+ )
+ assert c.Operator == operator
+ assert c.Value == value
+
+ def test_invalid_operator_rejected(self):
+ with pytest.raises(ValidationError):
+ Compliance_Requirement_ConfigConstraint(
+ Check="c", ConfigKey="k", Operator="between", Value=1
+ )
+
+ @pytest.mark.parametrize(
+ "operator,value",
+ [
+ # numeric operators reject non-numeric / boolean values
+ ("gte", [1, 2]),
+ ("lte", ["45"]),
+ ("gte", True),
+ # set/list operators reject scalars
+ ("subset", 5),
+ ("superset", "x"),
+ ("in", 1),
+ # eq rejects lists
+ ("eq", [1, 2]),
+ ],
+ )
+ def test_value_type_inconsistent_with_operator_rejected(self, operator, value):
+ # A mistyped Value would otherwise be silently treated as "not satisfied"
+ # at runtime, forcing a spurious config-not-valid FAIL.
+ with pytest.raises(ValidationError):
+ Compliance_Requirement_ConfigConstraint(
+ Check="c", ConfigKey="k", Operator=operator, Value=value
+ )
+
+ def test_boolean_value_not_coerced_to_int(self):
+ # ``mute_non_default_regions == false`` must stay a bool, not become 0.
+ c = Compliance_Requirement_ConfigConstraint(
+ Check="securityhub_enabled",
+ ConfigKey="mute_non_default_regions",
+ Operator="eq",
+ Value=False,
+ )
+ assert c.Value is False
+ assert isinstance(c.Value, bool)
+
+ def test_list_value_preserved_for_set_operators(self):
+ c = Compliance_Requirement_ConfigConstraint(
+ Check="c", ConfigKey="k", Operator="subset", Value=["1.2", "1.3"]
+ )
+ assert isinstance(c.Value, list)
+ assert c.Value == ["1.2", "1.3"]
+
+ def test_missing_required_fields_rejected(self):
+ with pytest.raises(ValidationError):
+ Compliance_Requirement_ConfigConstraint(Check="c", ConfigKey="k")
+
+ def test_provider_defaults_to_none(self):
+ # Single-provider frameworks omit Provider; it is optional.
+ c = Compliance_Requirement_ConfigConstraint(
+ Check="c", ConfigKey="k", Operator="eq", Value=False
+ )
+ assert c.Provider is None
+
+ def test_provider_scopes_constraint(self):
+ # Universal frameworks tag each constraint with the provider it applies to.
+ c = Compliance_Requirement_ConfigConstraint(
+ Check="securityhub_enabled",
+ Provider="aws",
+ ConfigKey="mute_non_default_regions",
+ Operator="eq",
+ Value=False,
+ )
+ assert c.Provider == "aws"
+
+
+class Test_ConfigRequirements_On_Compliance:
+ def test_requirements_without_constraints_default_to_none(self):
+ compliance = Compliance(**_load_cis())
+ # Requirement without configurable checks → ConfigRequirements is None.
+ no_constraint = [r for r in compliance.Requirements if not r.ConfigRequirements]
+ assert no_constraint
+ assert no_constraint[0].ConfigRequirements is None
+
+ def test_requirement_with_constraints_parses(self):
+ compliance = Compliance(**_load_cis())
+ with_constraint = [r for r in compliance.Requirements if r.ConfigRequirements]
+ assert with_constraint, "cis_6.0_aws should declare ConfigRequirements"
+ constraint = with_constraint[0].ConfigRequirements[0]
+ assert isinstance(constraint, Compliance_Requirement_ConfigConstraint)
+ assert constraint.Check
+ assert constraint.Operator in {"lte", "gte", "eq", "in", "subset", "superset"}
+
+
+class Test_Adapt_Legacy_To_Universal:
+ def test_config_requirements_carried_to_universal(self):
+ legacy = Compliance(**_load_cis())
+ universal = adapt_legacy_to_universal(legacy)
+
+ legacy_with = {r.Id for r in legacy.Requirements if r.ConfigRequirements}
+ universal_with = {r.id for r in universal.requirements if r.config_requirements}
+ assert legacy_with == universal_with
+ assert universal_with, "expected at least one requirement with constraints"
+
+ # The constraint payload survives as the typed constraint model with the
+ # same fields (``Provider`` is carried through too, ``None`` for
+ # single-provider frameworks like CIS AWS).
+ sample = next(r for r in universal.requirements if r.config_requirements)
+ entry = sample.config_requirements[0]
+ assert isinstance(entry, Compliance_Requirement_ConfigConstraint)
+ assert set(entry.dict()) == {
+ "Check",
+ "Provider",
+ "ConfigKey",
+ "Operator",
+ "Value",
+ }
+ assert entry.Provider is None
+
+ def test_requirements_without_constraints_are_none_in_universal(self):
+ legacy = Compliance(**_load_cis())
+ universal = adapt_legacy_to_universal(legacy)
+ without = [r for r in universal.requirements if not r.config_requirements]
+ assert without
+ assert without[0].config_requirements is None
diff --git a/tests/lib/check/compliance_config_eval_test.py b/tests/lib/check/compliance_config_eval_test.py
new file mode 100644
index 0000000000..74537344c4
--- /dev/null
+++ b/tests/lib/check/compliance_config_eval_test.py
@@ -0,0 +1,439 @@
+from types import SimpleNamespace
+from unittest.mock import patch
+
+import pytest
+
+from prowler.lib.check.compliance_config_eval import (
+ CONFIG_NOT_VALID_PREFIX,
+ accumulate_group_status,
+ accumulate_overview_status,
+ apply_config_status,
+ build_requirement_config_status,
+ evaluate_config_constraints,
+ get_effective_status,
+ get_scan_audit_config,
+ get_scan_provider_type,
+ resolve_requirement_config_status,
+)
+
+CONSTRAINTS = [
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45,
+ }
+]
+
+
+class Test_evaluate_config_constraints:
+ def test_no_constraints_is_compliant(self):
+ assert evaluate_config_constraints(None, {}) == (True, "")
+ assert evaluate_config_constraints([], {"x": 1}) == (True, "")
+
+ def test_config_absent_assumes_default_ok(self):
+ # Key not explicitly set → default assumed adequate.
+ is_ok, reason = evaluate_config_constraints(CONSTRAINTS, {})
+ assert is_ok is True
+ assert reason == ""
+
+ def test_none_audit_config_is_compliant(self):
+ assert evaluate_config_constraints(CONSTRAINTS, None) == (True, "")
+
+ def test_lte_satisfied(self):
+ assert evaluate_config_constraints(
+ CONSTRAINTS, {"max_unused_access_keys_days": 45}
+ ) == (True, "")
+
+ def test_lte_violated(self):
+ is_ok, reason = evaluate_config_constraints(
+ CONSTRAINTS, {"max_unused_access_keys_days": 120}
+ )
+ assert is_ok is False
+ # Product-facing message: names the check, the applied value, what the
+ # requirement needs and how to fix it, in plain language.
+ assert reason.startswith(CONFIG_NOT_VALID_PREFIX)
+ assert "iam_user_accesskey_unused" in reason
+ assert "max_unused_access_keys_days" in reason
+ assert "set to 120" in reason
+ assert "45 or lower" in reason
+
+ def test_gte_operator(self):
+ c = [{"Check": "c", "ConfigKey": "k", "Operator": "gte", "Value": 10}]
+ assert evaluate_config_constraints(c, {"k": 10})[0] is True
+ assert evaluate_config_constraints(c, {"k": 9})[0] is False
+
+ def test_eq_operator(self):
+ c = [{"Check": "c", "ConfigKey": "k", "Operator": "eq", "Value": "HIGH"}]
+ assert evaluate_config_constraints(c, {"k": "HIGH"})[0] is True
+ assert evaluate_config_constraints(c, {"k": "LOW"})[0] is False
+
+ def test_in_operator(self):
+ c = [{"Check": "c", "ConfigKey": "k", "Operator": "in", "Value": [1, 2, 3]}]
+ assert evaluate_config_constraints(c, {"k": 2})[0] is True
+ assert evaluate_config_constraints(c, {"k": 9})[0] is False
+
+ def test_subset_operator_allowlist(self):
+ # Allowlist config: applied list must stay within the secure baseline.
+ c = [
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": ["1.2", "1.3"],
+ }
+ ]
+ assert (
+ evaluate_config_constraints(
+ c, {"recommended_minimal_tls_versions": ["1.2", "1.3"]}
+ )[0]
+ is True
+ )
+ # Stricter (subset) still passes.
+ assert (
+ evaluate_config_constraints(
+ c, {"recommended_minimal_tls_versions": ["1.3"]}
+ )[0]
+ is True
+ )
+ # Widening with a weaker value breaks it.
+ is_ok, reason = evaluate_config_constraints(
+ c, {"recommended_minimal_tls_versions": ["1.0", "1.2", "1.3"]}
+ )
+ assert is_ok is False
+ assert "recommended_minimal_tls_versions" in reason
+
+ def test_superset_operator_denylist(self):
+ # Denylist config: applied list must keep covering the forbidden baseline.
+ c = [
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": ["RSA-1024", "P-192"],
+ }
+ ]
+ assert (
+ evaluate_config_constraints(
+ c, {"insecure_key_algorithms": ["RSA-1024", "P-192"]}
+ )[0]
+ is True
+ )
+ # Extra forbidden values are fine.
+ assert (
+ evaluate_config_constraints(
+ c, {"insecure_key_algorithms": ["RSA-1024", "P-192", "P-224"]}
+ )[0]
+ is True
+ )
+ # Removing a forbidden value breaks it.
+ assert (
+ evaluate_config_constraints(c, {"insecure_key_algorithms": ["P-192"]})[0]
+ is False
+ )
+
+ def test_subset_superset_non_list_not_satisfied(self):
+ sub = [{"Check": "c", "ConfigKey": "k", "Operator": "subset", "Value": ["a"]}]
+ sup = [{"Check": "c", "ConfigKey": "k", "Operator": "superset", "Value": ["a"]}]
+ # A scalar applied value cannot satisfy a set constraint.
+ assert evaluate_config_constraints(sub, {"k": "a"})[0] is False
+ assert evaluate_config_constraints(sup, {"k": "a"})[0] is False
+
+ def test_mismatched_types_not_satisfied(self):
+ assert (
+ evaluate_config_constraints(
+ CONSTRAINTS, {"max_unused_access_keys_days": "x"}
+ )[0]
+ is False
+ )
+
+ def test_multiple_constraints_first_violation_reported(self):
+ constraints = [
+ {"Check": "a", "ConfigKey": "k1", "Operator": "lte", "Value": 45},
+ {"Check": "b", "ConfigKey": "k2", "Operator": "lte", "Value": 45},
+ ]
+ is_ok, reason = evaluate_config_constraints(constraints, {"k1": 45, "k2": 90})
+ assert is_ok is False
+ # The first violation (check "b", key "k2", applied 90) is the one reported.
+ assert "k2" in reason
+ assert "set to 90" in reason
+
+
+class Test_provider_scoping:
+ # An AWS-scoped constraint on a config key whose value is too loose.
+ AWS_CONSTRAINT = [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+ ]
+
+ def test_applies_when_provider_matches(self):
+ is_ok, _ = evaluate_config_constraints(
+ self.AWS_CONSTRAINT, {"mute_non_default_regions": True}, "aws"
+ )
+ assert is_ok is False
+
+ def test_skipped_when_provider_differs(self):
+ # Same loose value, but scanning GCP → the AWS constraint must not fire.
+ is_ok, reason = evaluate_config_constraints(
+ self.AWS_CONSTRAINT, {"mute_non_default_regions": True}, "gcp"
+ )
+ assert is_ok is True
+ assert reason == ""
+
+ def test_none_provider_type_disables_scoping(self):
+ # Without a known provider every constraint is evaluated (legacy default).
+ is_ok, _ = evaluate_config_constraints(
+ self.AWS_CONSTRAINT, {"mute_non_default_regions": True}, None
+ )
+ assert is_ok is False
+
+ def test_provider_match_is_case_insensitive(self):
+ # A constraint authored as "AWS" must still scope to the "aws" scan,
+ # not be silently bypassed by a casing mismatch.
+ constraint = [
+ {
+ "Check": "securityhub_enabled",
+ "Provider": "AWS",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+ ]
+ is_ok, _ = evaluate_config_constraints(
+ constraint, {"mute_non_default_regions": True}, "aws"
+ )
+ assert is_ok is False
+
+ def test_untagged_constraint_applies_to_any_provider(self):
+ # Single-provider frameworks omit Provider → always evaluated.
+ is_ok, _ = evaluate_config_constraints(
+ CONSTRAINTS, {"max_unused_access_keys_days": 120}, "aws"
+ )
+ assert is_ok is False
+
+
+# A constraint forcing FAIL when the applied value is too loose.
+REGION_CONSTRAINT = [
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+]
+
+
+def _legacy_req(req_id, constraints=None):
+ """Fake legacy Compliance_Requirement (``Id`` / ``ConfigRequirements``)."""
+ return SimpleNamespace(Id=req_id, ConfigRequirements=constraints)
+
+
+def _universal_req(req_id, constraints=None):
+ """Fake UniversalComplianceRequirement (``id`` / ``config_requirements``)."""
+ return SimpleNamespace(id=req_id, config_requirements=constraints)
+
+
+class Test_build_requirement_config_status:
+ def test_only_requirements_with_constraints_included(self):
+ reqs = [_legacy_req("1", CONSTRAINTS), _legacy_req("2", None)]
+ status = build_requirement_config_status(
+ reqs, {"max_unused_access_keys_days": 120}
+ )
+ assert set(status) == {"1"}
+ assert status["1"][0] is False
+
+ def test_supports_universal_requirements(self):
+ reqs = [_universal_req("u1", REGION_CONSTRAINT)]
+ status = build_requirement_config_status(
+ reqs, {"mute_non_default_regions": True}
+ )
+ assert status["u1"][0] is False
+
+ def test_compliant_when_config_satisfied(self):
+ reqs = [_legacy_req("1", CONSTRAINTS)]
+ status = build_requirement_config_status(
+ reqs, {"max_unused_access_keys_days": 30}
+ )
+ assert status["1"] == (True, "")
+
+
+class Test_resolve_requirement_config_status:
+ def test_memoises_by_requirement_id(self):
+ cache = {}
+ req = _legacy_req("1", CONSTRAINTS)
+ first = resolve_requirement_config_status(
+ req, {"max_unused_access_keys_days": 120}, cache
+ )
+ assert cache["1"] is first
+ assert first[0] is False
+ # A different audit_config is ignored once cached (intended for one build).
+ second = resolve_requirement_config_status(req, {}, cache)
+ assert second is first
+
+ def test_requirement_without_constraints_is_ok(self):
+ cache = {}
+ req = _legacy_req("1", None)
+ assert resolve_requirement_config_status(req, {}, cache) == (True, "")
+
+
+class Test_accumulate_overview_status:
+ def test_fail_wins_over_earlier_pass(self):
+ p, f, m = set(), set(), set()
+ accumulate_overview_status(0, "PASS", p, f, m)
+ accumulate_overview_status(0, "FAIL", p, f, m)
+ assert (p, f, m) == (set(), {0}, set())
+
+ def test_pass_after_fail_does_not_double_count(self):
+ p, f, m = set(), set(), set()
+ accumulate_overview_status(0, "FAIL", p, f, m)
+ accumulate_overview_status(0, "PASS", p, f, m)
+ assert (p, f, m) == (set(), {0}, set())
+
+ def test_pass_only(self):
+ p, f, m = set(), set(), set()
+ accumulate_overview_status(0, "PASS", p, f, m)
+ assert (p, f, m) == ({0}, set(), set())
+
+ def test_muted(self):
+ p, f, m = set(), set(), set()
+ accumulate_overview_status(0, "Muted", p, f, m)
+ assert (p, f, m) == (set(), set(), {0})
+
+
+class Test_accumulate_group_status:
+ def test_first_status_counted(self):
+ counts = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ seen = {}
+ accumulate_group_status(0, "PASS", counts, seen)
+ assert counts == {"FAIL": 0, "PASS": 1, "Muted": 0}
+ assert seen == {0: "PASS"}
+
+ def test_pass_upgraded_to_fail(self):
+ counts = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ seen = {}
+ accumulate_group_status(0, "PASS", counts, seen)
+ accumulate_group_status(0, "FAIL", counts, seen)
+ assert counts == {"FAIL": 1, "PASS": 0, "Muted": 0}
+ assert seen == {0: "FAIL"}
+
+ def test_fail_not_downgraded_by_later_pass(self):
+ counts = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ seen = {}
+ accumulate_group_status(0, "FAIL", counts, seen)
+ accumulate_group_status(0, "PASS", counts, seen)
+ assert counts == {"FAIL": 1, "PASS": 0, "Muted": 0}
+
+ def test_same_index_not_double_counted(self):
+ counts = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ seen = {}
+ accumulate_group_status(0, "PASS", counts, seen)
+ accumulate_group_status(0, "PASS", counts, seen)
+ assert counts["PASS"] == 1
+
+ def test_works_with_fail_pass_only_counts(self):
+ # Level-style counts (no "Muted" key) used by CIS / split tables.
+ counts = {"FAIL": 0, "PASS": 0}
+ seen = {}
+ accumulate_group_status(0, "PASS", counts, seen)
+ accumulate_group_status(0, "FAIL", counts, seen)
+ assert counts == {"FAIL": 1, "PASS": 0}
+
+ def test_muted_on_fail_pass_only_counts_raises(self):
+ # Level-style callers only ever pass PASS/FAIL (they guard on
+ # ``not finding.muted``). Passing "Muted" to a Muted-less counts must
+ # fail loudly rather than silently create a bogus key.
+ counts = {"FAIL": 0, "PASS": 0}
+ with pytest.raises(KeyError):
+ accumulate_group_status(0, "Muted", counts, {})
+
+ def test_manual_status_is_ignored_not_counted(self):
+ # A MANUAL finding (from a manual, checks-less requirement) has no
+ # PASS/FAIL/Muted column: it must be skipped, not raise KeyError, and
+ # not appear in the tally. Regression test for the M365 CIS compliance
+ # crash "KeyError: 'MANUAL'" (issue #11822).
+ counts = {"FAIL": 0, "PASS": 0}
+ seen = {}
+ accumulate_group_status(0, "MANUAL", counts, seen)
+ assert counts == {"FAIL": 0, "PASS": 0}
+ assert seen == {}
+
+ def test_manual_mixed_with_pass_and_fail(self):
+ # MANUAL findings interleaved with real PASS/FAIL ones only skip
+ # themselves; the PASS/FAIL tally is unaffected.
+ counts = {"FAIL": 0, "PASS": 0}
+ seen = {}
+ accumulate_group_status(0, "MANUAL", counts, seen)
+ accumulate_group_status(1, "PASS", counts, seen)
+ accumulate_group_status(2, "FAIL", counts, seen)
+ accumulate_group_status(3, "MANUAL", counts, seen)
+ assert counts == {"FAIL": 1, "PASS": 1}
+
+ def test_manual_ignored_on_counts_with_muted_key(self):
+ # MANUAL is skipped regardless of the counts shape (e.g. the universal
+ # table's PASS/FAIL/Muted buckets), never creating a "MANUAL" key.
+ counts = {"FAIL": 0, "PASS": 0, "Muted": 0}
+ seen = {}
+ accumulate_group_status(0, "MANUAL", counts, seen)
+ assert counts == {"FAIL": 0, "PASS": 0, "Muted": 0}
+ assert "MANUAL" not in counts
+
+
+class Test_apply_config_status:
+ def test_none_config_status_keeps_finding(self):
+ assert apply_config_status("PASS", "ext", None) == ("PASS", "ext")
+
+ def test_compliant_keeps_finding(self):
+ assert apply_config_status("PASS", "ext", (True, "")) == ("PASS", "ext")
+
+ def test_invalid_config_forces_fail_and_prepends_reason(self):
+ # The reason already carries the full product-facing message; it is
+ # prepended verbatim to the finding's extended status.
+ reason = f"{CONFIG_NOT_VALID_PREFIX} bad config"
+ status, extended = apply_config_status("PASS", "ext", (False, reason))
+ assert status == "FAIL"
+ assert extended.startswith(CONFIG_NOT_VALID_PREFIX)
+ assert reason in extended
+ assert "ext" in extended
+
+
+class Test_get_effective_status:
+ def test_none_and_compliant_keep_status(self):
+ assert get_effective_status("PASS", None) == "PASS"
+ assert get_effective_status("PASS", (True, "")) == "PASS"
+
+ def test_invalid_config_forces_fail(self):
+ assert get_effective_status("PASS", (False, "reason")) == "FAIL"
+
+
+class Test_get_scan_audit_config:
+ def test_returns_empty_without_global_provider(self):
+ # No global provider set → get_global_provider() returns None →
+ # ``None.audit_config`` raises AttributeError → safe empty mapping.
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider",
+ return_value=None,
+ ):
+ assert get_scan_audit_config() == {}
+
+
+class Test_get_scan_provider_type:
+ def test_returns_empty_when_no_global_provider(self):
+ # No global provider set → get_global_provider() returns None →
+ # ``None.type`` raises AttributeError → scoping disabled (empty string).
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider",
+ return_value=None,
+ ):
+ assert get_scan_provider_type() == ""
+
+ def test_returns_global_provider_type(self):
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider",
+ return_value=SimpleNamespace(type="aws"),
+ ):
+ assert get_scan_provider_type() == "aws"
diff --git a/tests/lib/check/compliance_config_requirements_data_test.py b/tests/lib/check/compliance_config_requirements_data_test.py
new file mode 100644
index 0000000000..3b3ba5757f
--- /dev/null
+++ b/tests/lib/check/compliance_config_requirements_data_test.py
@@ -0,0 +1,191 @@
+"""Data-integrity tests for every ``ConfigRequirements`` declared in the shipped
+compliance framework JSONs.
+
+These guard the ~700 constraints added across the frameworks against drift:
+- every constraint is well-formed (valid operator, value typed for its operator),
+- every constraint targets a check the requirement actually maps (no orphans),
+- the region-mute invariant holds (every requirement mapping a region-scoped
+ check carries the ``mute_non_default_regions == false`` constraint),
+- every framework still parses through its model.
+"""
+
+import glob
+import json
+import pathlib
+
+import pytest
+
+from prowler.lib.check.compliance_models import Compliance, ComplianceFramework
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[3]
+_COMPLIANCE_DIR = _REPO_ROOT / "prowler" / "compliance"
+
+_VALID_OPERATORS = {"lte", "gte", "eq", "in", "subset", "superset"}
+# Checks whose result is untrustworthy when non-default regions are muted.
+_REGION_CHECKS = {
+ "accessanalyzer_enabled",
+ "config_recorder_all_regions_enabled",
+ "drs_job_exist",
+ "guardduty_delegated_admin_enabled_all_regions",
+ "guardduty_is_enabled",
+ "securityhub_enabled",
+}
+
+_ALL_FILES = sorted(glob.glob(str(_COMPLIANCE_DIR / "**" / "*.json"), recursive=True))
+
+
+def _load(path):
+ with open(path, encoding="utf-8") as f:
+ return json.load(f)
+
+
+def _requirements(data):
+ return data.get("Requirements") or data.get("requirements") or []
+
+
+def _req_id(req):
+ return req.get("Id") or req.get("id")
+
+
+def _req_checks(req):
+ ch = req.get("Checks", req.get("checks"))
+ checks = set()
+ if isinstance(ch, dict):
+ for v in ch.values():
+ checks |= set(v or [])
+ elif isinstance(ch, list):
+ checks |= set(ch)
+ return checks
+
+
+def _req_constraints(req):
+ return req.get("ConfigRequirements") or req.get("config_requirements") or []
+
+
+def _iter_constraints():
+ """Yield (file, req_id, checks, constraint) for every constraint shipped."""
+ for path in _ALL_FILES:
+ data = _load(path)
+ for req in _requirements(data):
+ checks = _req_checks(req)
+ for c in _req_constraints(req):
+ yield pathlib.Path(path).name, _req_id(req), checks, c
+
+
+_ALL_CONSTRAINTS = list(_iter_constraints())
+
+
+def test_there_are_constraints_to_validate():
+ # Guards against the iteration silently finding nothing (e.g. path change).
+ assert len(_ALL_CONSTRAINTS) > 100
+
+
+@pytest.mark.parametrize(
+ "fname,req_id,checks,constraint",
+ _ALL_CONSTRAINTS,
+ ids=[f"{f}:{r}:{c['Check']}" for f, r, _, c in _ALL_CONSTRAINTS],
+)
+class Test_Constraint_Wellformed:
+ def test_has_required_keys(self, fname, req_id, checks, constraint):
+ required = {"Check", "ConfigKey", "Operator", "Value"}
+ # ``Provider`` is optional (universal frameworks set it, single-provider
+ # ones omit it); no other key is allowed.
+ assert required <= set(constraint) <= required | {
+ "Provider"
+ }, f"{fname}:{req_id} malformed constraint {constraint}"
+
+ def test_operator_valid(self, fname, req_id, checks, constraint):
+ assert constraint["Operator"] in _VALID_OPERATORS
+
+ def test_check_is_mapped_by_requirement(self, fname, req_id, checks, constraint):
+ # No orphan constraints: the target check must be one the requirement runs.
+ assert constraint["Check"] in checks, (
+ f"{fname}:{req_id} constraint targets {constraint['Check']} "
+ f"which the requirement does not map"
+ )
+
+ def test_value_type_matches_operator(self, fname, req_id, checks, constraint):
+ op, val = constraint["Operator"], constraint["Value"]
+ if op in ("subset", "superset", "in"):
+ assert isinstance(val, list), f"{fname}:{req_id} {op} needs a list value"
+ elif op in ("lte", "gte"):
+ # Numeric threshold; bool is not a valid threshold even though it is
+ # an int subclass.
+ assert isinstance(val, (int, float)) and not isinstance(
+ val, bool
+ ), f"{fname}:{req_id} {op} needs a numeric value, got {val!r}"
+ elif op == "eq":
+ assert isinstance(
+ val, (bool, int, float, str)
+ ), f"{fname}:{req_id} eq needs a scalar value"
+
+
+class Test_Region_Mute_Invariant:
+ """Every requirement mapping a region-scoped check must carry the
+ ``mute_non_default_regions == false`` constraint for it."""
+
+ def test_region_checks_always_constrained(self):
+ gaps = []
+ for path in _ALL_FILES:
+ data = _load(path)
+ for req in _requirements(data):
+ checks = _req_checks(req)
+ constrained = {
+ c["Check"]
+ for c in _req_constraints(req)
+ if c["ConfigKey"] == "mute_non_default_regions"
+ }
+ for region_check in checks & _REGION_CHECKS:
+ if region_check not in constrained:
+ gaps.append(
+ f"{pathlib.Path(path).name}:{_req_id(req)}:{region_check}"
+ )
+ assert not gaps, f"region-mute constraint missing for: {gaps}"
+
+ def test_region_mute_constraints_use_eq_false(self):
+ for fname, req_id, _checks, c in _ALL_CONSTRAINTS:
+ if c["ConfigKey"] == "mute_non_default_regions":
+ assert (
+ c["Operator"] == "eq" and c["Value"] is False
+ ), f"{fname}:{req_id} region-mute must be eq false"
+
+
+class Test_Universal_Provider_Scoping:
+ """Universal (multi-provider) frameworks map checks per provider, so every
+ constraint must declare which provider it scopes to and that provider must
+ actually map the targeted check. Without this a constraint authored for one
+ provider's check would wrongly apply to scans of every other provider."""
+
+ def test_multiprovider_constraints_declare_consistent_provider(self):
+ gaps = []
+ for path in _ALL_FILES:
+ data = _load(path)
+ for req in _requirements(data):
+ ch = req.get("Checks", req.get("checks"))
+ # Only universal frameworks key their checks by provider.
+ if not isinstance(ch, dict):
+ continue
+ for c in _req_constraints(req):
+ provider = c.get("Provider")
+ if not provider:
+ gaps.append(
+ f"{pathlib.Path(path).name}:{_req_id(req)}:"
+ f"{c['Check']} missing Provider"
+ )
+ elif c["Check"] not in set(ch.get(provider, [])):
+ gaps.append(
+ f"{pathlib.Path(path).name}:{_req_id(req)}:"
+ f"{c['Check']} not mapped under provider {provider}"
+ )
+ assert not gaps, f"universal constraints with bad Provider: {gaps}"
+
+
+@pytest.mark.parametrize(
+ "path", _ALL_FILES, ids=[pathlib.Path(p).name for p in _ALL_FILES]
+)
+def test_every_framework_parses_with_constraints(path):
+ data = _load(path)
+ if "Requirements" in data:
+ Compliance(**data)
+ else:
+ ComplianceFramework.parse_obj(data)
diff --git a/tests/lib/check/mitre_config_requirements_test.py b/tests/lib/check/mitre_config_requirements_test.py
new file mode 100644
index 0000000000..ef3b33a17f
--- /dev/null
+++ b/tests/lib/check/mitre_config_requirements_test.py
@@ -0,0 +1,148 @@
+"""Regression coverage for ConfigRequirements on MITRE requirements.
+
+``mitre_attack_aws.json`` declares ``ConfigRequirements`` on its requirements,
+but ``Mitre_Requirement`` historically did not define the field, so Pydantic
+silently dropped the constraints during MITRE parsing and the config validation
+logic never saw them. These tests prove the constraints survive parsing and that
+a violated MITRE config requirement forces the compliance result to FAIL through
+the universal output path.
+"""
+
+from datetime import datetime, timezone
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from py_ocsf_models.objects.compliance_status import StatusID as ComplianceStatusID
+
+from prowler.lib.check.compliance_models import (
+ Compliance,
+ Mitre_Requirement,
+ adapt_legacy_to_universal,
+)
+from prowler.lib.outputs.compliance.universal.ocsf_compliance import (
+ OCSFComplianceOutput,
+)
+
+_MODULE = "prowler.providers.common.provider.Provider.get_global_provider"
+
+
+def _mitre_compliance(check_id):
+ """A minimal one-requirement MITRE framework with a config constraint."""
+ return Compliance(
+ Framework="MITRE-ATTACK",
+ Name="MITRE ATT&CK",
+ Provider="AWS",
+ Version="",
+ Description="Test MITRE framework",
+ Requirements=[
+ {
+ "Name": "Test Technique",
+ "Id": "T9999",
+ "Tactics": ["initial-access"],
+ "SubTechniques": [],
+ "Platforms": ["AWS"],
+ "Description": "Requirement T9999",
+ "TechniqueURL": "https://attack.mitre.org/techniques/T9999",
+ "Checks": [check_id],
+ "ConfigRequirements": [
+ {
+ "Check": check_id,
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+ ],
+ "Attributes": [
+ {
+ "AWSService": "service",
+ "Category": "category",
+ "Value": "value",
+ "Comment": "comment",
+ }
+ ],
+ }
+ ],
+ )
+
+
+def _finding(check_id, status="PASS", provider="aws"):
+ finding = SimpleNamespace()
+ finding.provider = provider
+ finding.account_uid = "123456789012"
+ finding.account_name = "test-account"
+ finding.account_organization_uid = "org-123"
+ finding.account_organization_name = "test-org"
+ finding.region = "us-east-1"
+ finding.status = status
+ finding.status_extended = f"{check_id} is {status}"
+ finding.resource_uid = f"arn:aws:iam::123456789012:{check_id}"
+ finding.resource_name = check_id
+ finding.resource_details = "details"
+ finding.resource_metadata = {}
+ finding.resource_tags = {"Name": "test"}
+ finding.partition = "aws"
+ finding.muted = False
+ finding.check_id = check_id
+ finding.uid = "test-finding-uid"
+ finding.timestamp = datetime(2025, 1, 15, 12, 0, 0, tzinfo=timezone.utc)
+ finding.prowler_version = "5.0.0"
+ finding.metadata = SimpleNamespace(
+ CheckID=check_id,
+ CheckTitle=f"Title for {check_id}",
+ Description=f"Description for {check_id}",
+ Severity="medium",
+ ServiceName="iam",
+ ResourceType="aws-iam-role",
+ )
+ return finding
+
+
+class Test_Mitre_Config_Requirements:
+ def test_config_requirements_survive_mitre_parsing(self):
+ """Real mitre_attack_aws.json constraints must not be dropped on parse."""
+ compliance = Compliance.parse_file(
+ "prowler/compliance/aws/mitre_attack_aws.json"
+ )
+ requirement = next(r for r in compliance.Requirements if r.Id == "T1190")
+ assert isinstance(requirement, Mitre_Requirement)
+ assert requirement.ConfigRequirements
+ # And they propagate through the legacy -> universal adapter unchanged.
+ universal = adapt_legacy_to_universal(compliance)
+ universal_requirement = next(
+ r for r in universal.requirements if r.id == "T1190"
+ )
+ assert universal_requirement.config_requirements
+ assert len(universal_requirement.config_requirements) == len(
+ requirement.ConfigRequirements
+ )
+
+ def test_violating_mitre_config_forces_fail(self):
+ """A PASS finding becomes FAIL when the MITRE config constraint is violated."""
+ check_id = "drs_job_exist"
+ framework = adapt_legacy_to_universal(_mitre_compliance(check_id))
+ findings = [_finding(check_id, "PASS")]
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = {"mute_non_default_regions": True}
+ out = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider="aws"
+ )
+ event = out.data[0]
+ assert event.compliance.status_id == ComplianceStatusID.Fail
+ assert event.status_code == "FAIL"
+ assert "Configuration not valid" in event.message
+ # The nested Check object keeps the real (raw) finding status.
+ assert event.compliance.checks[0].status == "PASS"
+
+ def test_valid_mitre_config_keeps_pass(self):
+ check_id = "drs_job_exist"
+ framework = adapt_legacy_to_universal(_mitre_compliance(check_id))
+ findings = [_finding(check_id, "PASS")]
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = {"mute_non_default_regions": False}
+ out = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider="aws"
+ )
+ event = out.data[0]
+ assert event.compliance.status_id == ComplianceStatusID.Pass
+ assert event.status_code == "PASS"
+ assert "Configuration not valid" not in event.message
diff --git a/tests/lib/check/models_test.py b/tests/lib/check/models_test.py
index 71fd1f718b..f17e359441 100644
--- a/tests/lib/check/models_test.py
+++ b/tests/lib/check/models_test.py
@@ -95,6 +95,38 @@ class TestCheckMetada:
"/path/to/accessanalyzer_enabled/accessanalyzer_enabled.metadata.json"
)
+ @mock.patch("prowler.lib.check.models.logger")
+ @mock.patch("prowler.lib.check.models.load_check_metadata")
+ @mock.patch("prowler.lib.check.models.recover_checks_from_provider")
+ def test_get_bulk_builtin_wins_on_check_id_collision(
+ self, mock_recover_checks, mock_load_metadata, mock_logger
+ ):
+ """Regression guard: when an entry-point plug-in re-registers a
+ built-in CheckID, the BUILT-IN metadata wins (first-write-wins) and
+ the plug-in is IGNORED. The override is surfaced via a warning so
+ the user knows their plug-in duplicate is being skipped and can
+ rename it. Matches the precedence in `_resolve_check_module`. See
+ PR #10700 review (HugoPBrito)."""
+ # Built-in first, plug-in last (matches recover_checks_from_provider order)
+ mock_recover_checks.return_value = [
+ ("accessanalyzer_enabled", "/builtin/accessanalyzer_enabled"),
+ ("accessanalyzer_enabled", "/plugin/accessanalyzer_enabled"),
+ ]
+
+ builtin_metadata = mock.MagicMock(CheckID="accessanalyzer_enabled")
+ plugin_metadata = mock.MagicMock(CheckID="accessanalyzer_enabled")
+ mock_load_metadata.side_effect = [builtin_metadata, plugin_metadata]
+
+ result = CheckMetadata.get_bulk(provider="aws")
+
+ # Built-in wins (first-write-wins on CheckID), plug-in is ignored
+ assert result["accessanalyzer_enabled"] is builtin_metadata
+ # Override is surfaced via warning naming the plug-in metadata file
+ mock_logger.warning.assert_called_once()
+ warning_msg = mock_logger.warning.call_args.args[0]
+ assert "accessanalyzer_enabled" in warning_msg
+ assert "/plugin/accessanalyzer_enabled" in warning_msg
+
@mock.patch("prowler.lib.check.models.load_check_metadata")
@mock.patch("prowler.lib.check.models.recover_checks_from_provider")
def test_list(self, mock_recover_checks, mock_load_metadata):
diff --git a/tests/lib/check/tool_wrapper_test.py b/tests/lib/check/tool_wrapper_test.py
new file mode 100644
index 0000000000..5f4f0c7f88
--- /dev/null
+++ b/tests/lib/check/tool_wrapper_test.py
@@ -0,0 +1,124 @@
+"""Unit tests for prowler.lib.check.tool_wrapper.
+
+Covers the leaf helper directly (Provider.is_tool_wrapper_provider delegates
+to it). Tests the frozenset fast path, the entry-point fallback for external
+plug-ins, the broken-plug-in path, the no-match path, and the module-level
+cache.
+"""
+
+from unittest.mock import MagicMock, patch
+
+import pytest
+
+
+@pytest.fixture(autouse=True)
+def _clear_ep_class_cache():
+ """Reset the leaf module's cache between tests so they stay independent."""
+ from prowler.lib.check import tool_wrapper
+
+ tool_wrapper._ep_class_cache.clear()
+ yield
+ tool_wrapper._ep_class_cache.clear()
+
+
+def _make_entry_point(name, cls):
+ """Create a mock entry point whose `load()` returns `cls`."""
+ ep = MagicMock()
+ ep.name = name
+ ep.load.return_value = cls
+ return ep
+
+
+class TestIsToolWrapperProvider:
+ """is_tool_wrapper_provider: frozenset + entry-point fallback."""
+
+ @pytest.mark.parametrize("name", ["iac", "llm", "image"])
+ def test_returns_true_for_builtin_tool_wrappers(self, name):
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ assert is_tool_wrapper_provider(name) is True
+
+ @pytest.mark.parametrize("name", ["aws", "azure", "gcp", "github", "kubernetes"])
+ def test_returns_false_for_regular_builtins(self, name):
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ assert is_tool_wrapper_provider(name) is False
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_returns_true_for_external_plugin_with_flag(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ cls = MagicMock(is_external_tool_provider=True)
+ mock_eps.return_value = [_make_entry_point("custom_wrapper", cls)]
+
+ assert is_tool_wrapper_provider("custom_wrapper") is True
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_returns_false_for_external_plugin_without_flag(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ cls = MagicMock(is_external_tool_provider=False)
+ mock_eps.return_value = [_make_entry_point("vanilla_external", cls)]
+
+ assert is_tool_wrapper_provider("vanilla_external") is False
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_returns_false_for_unknown_provider(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ mock_eps.return_value = []
+
+ assert is_tool_wrapper_provider("does-not-exist") is False
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_builtin_name_shortcircuits_before_loading_same_name_plugin(self, mock_eps):
+ """A plug-in registered under a built-in's name cannot flip the
+ built-in onto the tool-wrapper path, and its module is never loaded."""
+ from prowler.lib.check.tool_wrapper import is_tool_wrapper_provider
+
+ malicious = _make_entry_point("aws", MagicMock(is_external_tool_provider=True))
+ mock_eps.return_value = [malicious]
+
+ # `aws` is a built-in, so classification short-circuits to False...
+ assert is_tool_wrapper_provider("aws") is False
+ # ...and the shadowing plug-in's code is never executed via ep.load().
+ malicious.load.assert_not_called()
+
+
+class TestLoadEpClass:
+ """_load_ep_class: cache, broken plug-ins, no-match."""
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_caches_result_across_calls(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import _load_ep_class
+
+ cls = MagicMock(is_external_tool_provider=True)
+ mock_eps.return_value = [_make_entry_point("cached_one", cls)]
+
+ first = _load_ep_class("cached_one")
+ second = _load_ep_class("cached_one")
+
+ assert first is cls
+ assert second is cls
+ # entry_points consulted only on the first call
+ assert mock_eps.call_count == 1
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_returns_none_for_broken_plugin(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import _load_ep_class
+
+ broken_ep = MagicMock()
+ broken_ep.name = "broken"
+ broken_ep.load.side_effect = ImportError("plug-in is broken")
+ mock_eps.return_value = [broken_ep]
+
+ assert _load_ep_class("broken") is None
+
+ @patch("prowler.lib.check.tool_wrapper.importlib.metadata.entry_points")
+ def test_returns_none_when_no_entry_point_matches(self, mock_eps):
+ from prowler.lib.check.tool_wrapper import _load_ep_class
+
+ cls = MagicMock()
+ mock_eps.return_value = [_make_entry_point("other_provider", cls)]
+
+ assert _load_ep_class("missing_provider") is None
diff --git a/tests/lib/check/universal_compliance_models_test.py b/tests/lib/check/universal_compliance_models_test.py
index 5a3e4aae56..c8f614488c 100644
--- a/tests/lib/check/universal_compliance_models_test.py
+++ b/tests/lib/check/universal_compliance_models_test.py
@@ -1,5 +1,7 @@
import json
import os
+import tempfile
+from unittest.mock import MagicMock, patch
import pytest
from pydantic.v1 import ValidationError
@@ -23,6 +25,7 @@ from prowler.lib.check.compliance_models import (
TableLabels,
UniversalComplianceRequirement,
adapt_legacy_to_universal,
+ get_bulk_compliance_frameworks_universal,
load_compliance_framework_universal,
)
from tests.lib.outputs.compliance.fixtures import (
@@ -1116,3 +1119,121 @@ class TestAttributesMetadataValidation:
],
attributes_metadata=self._metadata(enum=["high", "low"]),
)
+
+
+class TestGetBulkUniversalEntryPoints:
+ """Entry-point discovery for universal (multi-provider) compliance frameworks."""
+
+ @staticmethod
+ def _write_universal_json(directory, filename, framework, display_name):
+ data = {
+ "framework": framework,
+ "name": display_name,
+ "version": "1.0",
+ "description": "External multi-provider framework",
+ "requirements": [
+ {
+ "id": "1",
+ "name": "Requirement 1",
+ "description": "desc",
+ "checks": {"fakeexternal": ["check_a"]},
+ }
+ ],
+ }
+ with open(os.path.join(directory, filename), "w") as f:
+ json.dump(data, f)
+
+ @staticmethod
+ def _entry_point(path):
+ module = MagicMock()
+ module.__path__ = [path]
+ ep = MagicMock()
+ ep.name = "fakeexternal"
+ ep.group = "prowler.compliance.universal"
+ ep.load.return_value = module
+ return ep
+
+ @patch("prowler.lib.check.compliance_models.importlib.metadata.entry_points")
+ @patch("prowler.lib.check.compliance_models.list_compliance_modules")
+ def test_includes_external_universal_framework(self, mock_list_modules, mock_ep):
+ mock_list_modules.return_value = []
+ with tempfile.TemporaryDirectory() as ep_dir:
+ self._write_universal_json(
+ ep_dir, "customuniversal_1.0.json", "CustomUniversal", "Custom"
+ )
+ mock_ep.return_value = [self._entry_point(ep_dir)]
+
+ bulk = get_bulk_compliance_frameworks_universal("fakeexternal")
+
+ mock_ep.assert_called_with(group="prowler.compliance.universal")
+ assert "customuniversal_1.0" in bulk
+ assert bulk["customuniversal_1.0"].framework == "CustomUniversal"
+
+ @patch("prowler.lib.check.compliance_models.importlib.metadata.entry_points")
+ @patch("prowler.lib.check.compliance_models.list_compliance_modules")
+ def test_builtin_wins_over_external_on_name_collision(
+ self, mock_list_modules, mock_ep
+ ):
+ with (
+ tempfile.TemporaryDirectory() as root,
+ tempfile.TemporaryDirectory() as ep_dir,
+ ):
+ builtin_sub = os.path.join(root, "builtinprov")
+ os.makedirs(builtin_sub)
+ self._write_universal_json(
+ builtin_sub, "shared_1.0.json", "SharedFramework", "Built-in"
+ )
+ builtin_module = MagicMock()
+ builtin_module.module_finder.path = root
+ builtin_module.name = "prowler.compliance.builtinprov"
+ mock_list_modules.return_value = [builtin_module]
+
+ self._write_universal_json(
+ ep_dir, "shared_1.0.json", "SharedFramework", "External"
+ )
+ mock_ep.return_value = [self._entry_point(ep_dir)]
+
+ bulk = get_bulk_compliance_frameworks_universal("fakeexternal")
+
+ assert "shared_1.0" in bulk
+ assert bulk["shared_1.0"].name == "Built-in"
+
+ @patch("prowler.lib.check.compliance_models.importlib.metadata.entry_points")
+ @patch("prowler.lib.check.compliance_models.list_compliance_modules")
+ def test_loads_all_frameworks_in_a_single_entry_point_path(
+ self, mock_list_modules, mock_ep
+ ):
+ """All JSONs in one entry-point directory are added, not collapsed to one."""
+ mock_list_modules.return_value = []
+ with tempfile.TemporaryDirectory() as ep_dir:
+ self._write_universal_json(ep_dir, "fw_a_1.0.json", "FwA", "Framework A")
+ self._write_universal_json(ep_dir, "fw_b_1.0.json", "FwB", "Framework B")
+ mock_ep.return_value = [self._entry_point(ep_dir)]
+
+ bulk = get_bulk_compliance_frameworks_universal("fakeexternal")
+
+ assert "fw_a_1.0" in bulk
+ assert "fw_b_1.0" in bulk
+
+ @patch("prowler.lib.check.compliance_models.importlib.metadata.entry_points")
+ @patch("prowler.lib.check.compliance_models.list_compliance_modules")
+ def test_merges_frameworks_from_multiple_packages_same_provider(
+ self, mock_list_modules, mock_ep
+ ):
+ """Two packages under the same provider name are both discovered."""
+ mock_list_modules.return_value = []
+ with (
+ tempfile.TemporaryDirectory() as dir_a,
+ tempfile.TemporaryDirectory() as dir_b,
+ ):
+ self._write_universal_json(dir_a, "pkg_a_1.0.json", "PkgA", "Package A")
+ self._write_universal_json(dir_b, "pkg_b_1.0.json", "PkgB", "Package B")
+ mock_ep.return_value = [
+ self._entry_point(dir_a),
+ self._entry_point(dir_b),
+ ]
+
+ bulk = get_bulk_compliance_frameworks_universal("fakeexternal")
+
+ assert "pkg_a_1.0" in bulk
+ assert "pkg_b_1.0" in bulk
diff --git a/tests/lib/check_test_init_files_test.py b/tests/lib/check_test_init_files_test.py
new file mode 100644
index 0000000000..2dc4d77902
--- /dev/null
+++ b/tests/lib/check_test_init_files_test.py
@@ -0,0 +1,93 @@
+from importlib.util import module_from_spec, spec_from_file_location
+from pathlib import Path
+
+SCRIPT_PATH = (
+ Path(__file__).resolve().parents[2] / "scripts" / "check_test_init_files.py"
+)
+
+
+def load_guard_module():
+ spec = spec_from_file_location("check_test_init_files", SCRIPT_PATH)
+ assert spec is not None
+ assert spec.loader is not None
+
+ module = module_from_spec(spec)
+ spec.loader.exec_module(module)
+ return module
+
+
+def test_find_test_init_files_detects_only_root_test_directories(tmp_path):
+ guard = load_guard_module()
+
+ (tmp_path / "tests" / "providers" / "aws").mkdir(parents=True)
+ (tmp_path / "tests" / "providers" / "aws" / "__init__.py").write_text("")
+ (tmp_path / "api" / "tests" / "performance").mkdir(parents=True)
+ (tmp_path / "api" / "tests" / "performance" / "__init__.py").write_text("")
+ (tmp_path / "mcp_server" / "tests").mkdir(parents=True)
+ (tmp_path / "mcp_server" / "tests" / "__init__.py").write_text("")
+ (tmp_path / "prowler" / "providers" / "aws").mkdir(parents=True)
+ (tmp_path / "prowler" / "providers" / "aws" / "__init__.py").write_text("")
+ (
+ tmp_path / "tests" / "lib" / "check" / "fixtures" / "checks_folder" / "check11"
+ ).mkdir(parents=True)
+ (
+ tmp_path
+ / "tests"
+ / "lib"
+ / "check"
+ / "fixtures"
+ / "checks_folder"
+ / "check11"
+ / "__init__.py"
+ ).write_text("")
+
+ matches = guard.find_test_init_files(tmp_path)
+
+ assert [path.relative_to(tmp_path) for path in matches] == [
+ Path("tests/providers/aws/__init__.py"),
+ ]
+
+
+def test_find_test_init_files_ignores_virtualenv_test_packages(tmp_path):
+ guard = load_guard_module()
+
+ virtualenv_tests = (
+ tmp_path
+ / ".venv"
+ / "lib"
+ / "python3.12"
+ / "site-packages"
+ / "package"
+ / "tests"
+ )
+ virtualenv_tests.mkdir(parents=True)
+ (virtualenv_tests / "__init__.py").write_text("")
+ (tmp_path / "tests" / "providers" / "aws").mkdir(parents=True)
+ (tmp_path / "tests" / "providers" / "aws" / "__init__.py").write_text("")
+
+ matches = guard.find_test_init_files(tmp_path)
+
+ assert [path.relative_to(tmp_path) for path in matches] == [
+ Path("tests/providers/aws/__init__.py"),
+ ]
+
+
+def test_main_returns_error_when_test_init_files_exist(tmp_path, capsys):
+ guard = load_guard_module()
+
+ (tmp_path / "tests" / "config").mkdir(parents=True)
+ (tmp_path / "tests" / "config" / "__init__.py").write_text("")
+
+ assert guard.main([str(tmp_path)]) == 1
+
+ captured = capsys.readouterr()
+ assert "Remove __init__.py files from test directories" in captured.out
+ assert "tests/config/__init__.py" in captured.out
+
+
+def test_repository_has_no_test_init_files():
+ guard = load_guard_module()
+
+ repo_root = Path(__file__).resolve().parents[2]
+
+ assert guard.find_test_init_files(repo_root) == []
diff --git a/tests/lib/cli/parser_test.py b/tests/lib/cli/parser_test.py
index d667be9e66..549ca17727 100644
--- a/tests/lib/cli/parser_test.py
+++ b/tests/lib/cli/parser_test.py
@@ -17,7 +17,7 @@ prowler_command = "prowler"
# capsys
# https://docs.pytest.org/en/7.1.x/how-to/capture-stdout-stderr.html
-prowler_default_usage_error = "usage: prowler [-h] [--version] {aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,vercel,dashboard,iac,image,llm} ..."
+prowler_default_usage_error = "usage: prowler [-h] [--version] {aws,azure,gcp,kubernetes,m365,github,googleworkspace,okta,nhn,mongodbatlas,oraclecloud,alibabacloud,cloudflare,openstack,scaleway,stackit,vercel,linode,e2enetworks,dashboard,iac,image,llm} ..."
def mock_get_available_providers():
@@ -38,6 +38,9 @@ def mock_get_available_providers():
"llm",
"cloudflare",
"openstack",
+ "stackit",
+ "linode",
+ "e2enetworks",
]
diff --git a/tests/lib/cli/redact_test.py b/tests/lib/cli/redact_test.py
index 5de4cc8fd7..c7ff65a765 100644
--- a/tests/lib/cli/redact_test.py
+++ b/tests/lib/cli/redact_test.py
@@ -160,6 +160,7 @@ class TestGetSensitiveArguments:
assert "--atlas-private-key" in result
assert "--nhn-password" in result
assert "--os-password" in result
+ assert "--stackit-service-account-key" in result
def test_does_not_include_non_sensitive_flags(self):
"""Verify non-sensitive flags are not in the set."""
@@ -168,3 +169,4 @@ class TestGetSensitiveArguments:
assert "--region" not in result
assert "--profile" not in result
assert "--output-formats" not in result
+ assert "--stackit-service-account-key-path" not in result
diff --git a/tests/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_table_test.py b/tests/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_table_test.py
new file mode 100644
index 0000000000..6382dc1d2c
--- /dev/null
+++ b/tests/lib/outputs/compliance/asd_essential_eight/asd_essential_eight_table_test.py
@@ -0,0 +1,132 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.asd_essential_eight.asd_essential_eight import (
+ get_asd_essential_eight_table,
+)
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(provider, sections, framework="ASD-Essential-Eight"):
+ """Build a per-check compliance covering the given sections."""
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(Attributes=[SimpleNamespace(Section=section)])
+ for section in sections
+ ],
+ )
+
+
+class TestASDEssentialEightTable:
+ """Test cases verifying multi-section counting and provider-column attribution for the ASD Essential Eight compliance table."""
+
+ def test_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several sections must show FAIL(1) in
+ every section, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_asd_essential_eight_table(
+ findings,
+ bulk_metadata,
+ "asd_essential_eight_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Logging must report FAIL(1); before the fix Logging was
+ # undercounted because the per-section count was gated by the global
+ # dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several sections must increase the
+ per-section Muted count in every section, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_asd_essential_eight_table(
+ findings,
+ bulk_metadata,
+ "asd_essential_eight_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both IAM and Logging, so the Muted column
+ # must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched ASD-Essential-Eight
+ compliance, never from a different framework that happens to be the last
+ entry in the check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_asd_essential_eight_table(
+ findings,
+ bulk_metadata,
+ "asd_essential_eight_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/c5/c5_table_test.py b/tests/lib/outputs/compliance/c5/c5_table_test.py
new file mode 100644
index 0000000000..c423f5af0b
--- /dev/null
+++ b/tests/lib/outputs/compliance/c5/c5_table_test.py
@@ -0,0 +1,130 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.c5.c5 import get_c5_table
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(provider, sections, framework="C5"):
+ """Build a per-check compliance covering the given sections."""
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(Attributes=[SimpleNamespace(Section=section)])
+ for section in sections
+ ],
+ )
+
+
+class TestC5Table:
+ """Verify multi-section counting and provider-column attribution for the compliance table."""
+
+ def test_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several sections must show FAIL(1) in
+ every section, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_c5_table(
+ findings,
+ bulk_metadata,
+ "c5_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Logging must report FAIL(1); before the fix Logging was
+ # undercounted because the per-section count was gated by the global
+ # dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several sections must increase the
+ per-section Muted count in every section, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_c5_table(
+ findings,
+ bulk_metadata,
+ "c5_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both IAM and Logging, so the Muted column
+ # must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched C5 compliance, never
+ from a different framework that happens to be the last entry in the
+ check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_c5_table(
+ findings,
+ bulk_metadata,
+ "c5_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/ccc/ccc_table_test.py b/tests/lib/outputs/compliance/ccc/ccc_table_test.py
new file mode 100644
index 0000000000..f647aff3d0
--- /dev/null
+++ b/tests/lib/outputs/compliance/ccc/ccc_table_test.py
@@ -0,0 +1,130 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.ccc.ccc import get_ccc_table
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(provider, sections, framework="CCC"):
+ """Build a per-check compliance covering the given sections."""
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(Attributes=[SimpleNamespace(Section=section)])
+ for section in sections
+ ],
+ )
+
+
+class TestCCCTable:
+ """Test cases verifying multi-section counting and provider-column attribution for the compliance table."""
+
+ def test_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several sections must show FAIL(1) in
+ every section, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_ccc_table(
+ findings,
+ bulk_metadata,
+ "ccc_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Logging must report FAIL(1); before the fix Logging was
+ # undercounted because the per-section count was gated by the global
+ # dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several sections must increase the
+ per-section Muted count in every section, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_ccc_table(
+ findings,
+ bulk_metadata,
+ "ccc_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both IAM and Logging, so the Muted column
+ # must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched CCC compliance, never
+ from a different framework that happens to be the last entry in the
+ check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_ccc_table(
+ findings,
+ bulk_metadata,
+ "ccc_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/cis/cis_7_0_m365_test.py b/tests/lib/outputs/compliance/cis/cis_7_0_m365_test.py
new file mode 100644
index 0000000000..4fbebb49f6
--- /dev/null
+++ b/tests/lib/outputs/compliance/cis/cis_7_0_m365_test.py
@@ -0,0 +1,65 @@
+import json
+from pathlib import Path
+
+from prowler.lib.check.compliance_models import (
+ CIS_Requirement_Attribute_AssessmentStatus,
+ CIS_Requirement_Attribute_Profile,
+ Compliance,
+)
+
+PROWLER_ROOT = Path(__file__).parents[5] / "prowler"
+FRAMEWORK_PATH = PROWLER_ROOT / "compliance" / "m365" / "cis_7.0_m365.json"
+M365_SERVICES_PATH = PROWLER_ROOT / "providers" / "m365" / "services"
+
+VALID_PROFILES = {p.value for p in CIS_Requirement_Attribute_Profile}
+VALID_STATUSES = {s.value for s in CIS_Requirement_Attribute_AssessmentStatus}
+
+
+def _existing_m365_checks() -> set:
+ return {
+ metadata.stem.replace(".metadata", "")
+ for metadata in M365_SERVICES_PATH.rglob("*.metadata.json")
+ }
+
+
+class TestCIS7_0_M365:
+ def test_framework_is_discoverable(self):
+ frameworks = Compliance.get_bulk("m365")
+ assert "cis_7.0_m365" in frameworks
+
+ def test_framework_metadata(self):
+ framework = Compliance.get_bulk("m365")["cis_7.0_m365"]
+ assert framework.Framework == "CIS"
+ assert framework.Provider == "M365"
+ assert framework.Version == "7.0"
+ assert framework.Name == "CIS Microsoft 365 Foundations Benchmark v7.0.0"
+ assert len(framework.Requirements) == 160
+
+ def test_requirement_ids_are_unique(self):
+ framework = Compliance.get_bulk("m365")["cis_7.0_m365"]
+ ids = [req.Id for req in framework.Requirements]
+ assert len(ids) == len(set(ids))
+
+ def test_each_requirement_has_one_attribute_with_section(self):
+ framework = Compliance.get_bulk("m365")["cis_7.0_m365"]
+ for req in framework.Requirements:
+ assert len(req.Attributes) == 1, f"{req.Id} must have exactly one attribute"
+ attribute = req.Attributes[0]
+ assert attribute.Section, f"{req.Id} has an empty Section"
+ assert attribute.Profile in VALID_PROFILES
+ assert attribute.AssessmentStatus in VALID_STATUSES
+
+ def test_all_mapped_checks_exist(self):
+ # Every check referenced by the framework must resolve to a real M365 check,
+ # otherwise the requirement would never be evaluated.
+ existing = _existing_m365_checks()
+ framework = json.loads(FRAMEWORK_PATH.read_text())
+ unknown = {
+ check
+ for req in framework["Requirements"]
+ for check in req["Checks"]
+ if check not in existing
+ }
+ assert (
+ not unknown
+ ), f"Framework references unknown M365 checks: {sorted(unknown)}"
diff --git a/tests/lib/outputs/compliance/cis/cis_aws_config_requirements_test.py b/tests/lib/outputs/compliance/cis/cis_aws_config_requirements_test.py
new file mode 100644
index 0000000000..28cc3d2e1a
--- /dev/null
+++ b/tests/lib/outputs/compliance/cis/cis_aws_config_requirements_test.py
@@ -0,0 +1,89 @@
+"""Integration coverage for requirement-level config validation in the CIS AWS
+CSV output. Requirement CIS 6.0 AWS 2.11 maps two configurable checks; when the
+scan config is looser than the requirement demands, the requirement row must be
+FAIL even if the underlying finding is PASS. The applied config is read from the
+active provider's ``audit_config``."""
+
+import json
+import pathlib
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.check.compliance_models import Compliance
+from prowler.lib.outputs.compliance.cis.cis_aws import AWSCIS
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[5]
+_CIS_6_0 = _REPO_ROOT / "prowler" / "compliance" / "aws" / "cis_6.0_aws.json"
+
+
+def _load_cis_60() -> Compliance:
+ return Compliance(**json.load(open(_CIS_6_0)))
+
+
+def _finding(check_id: str, status: str):
+ return SimpleNamespace(
+ provider="aws",
+ account_uid="123456789012",
+ region="us-east-1",
+ check_id=check_id,
+ status=status,
+ status_extended=f"{check_id} {status}",
+ resource_uid="arn:aws:iam::123456789012:user/bob",
+ resource_name="bob",
+ muted=False,
+ )
+
+
+def _rows_for(requirement_id, findings, audit_config):
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider"
+ ) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ out = AWSCIS(findings=findings, compliance=_load_cis_60(), file_path=None)
+ return [r for r in out._data if r.Requirements_Id == requirement_id]
+
+
+class Test_CIS_AWS_Config_Requirements:
+ def test_loose_config_forces_requirement_fail(self):
+ findings = [_finding("iam_user_accesskey_unused", "PASS")]
+ rows = _rows_for("2.11", findings, {"max_unused_access_keys_days": 120})
+ assert rows, "expected a row for requirement 2.11"
+ assert all(r.Status == "FAIL" for r in rows)
+ assert all("Configuration not valid" in r.StatusExtended for r in rows)
+
+ def test_valid_config_keeps_finding_status(self):
+ findings = [_finding("iam_user_accesskey_unused", "PASS")]
+ rows = _rows_for("2.11", findings, {"max_unused_access_keys_days": 45})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
+ assert all("Configuration not valid" not in r.StatusExtended for r in rows)
+
+ def test_absent_config_assumes_default_ok(self):
+ findings = [_finding("iam_user_accesskey_unused", "PASS")]
+ rows = _rows_for("2.11", findings, {})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
+
+ def test_other_requirements_unaffected(self):
+ # A finding for a check without ConfigRequirements keeps its status even
+ # when the config is loose for a different requirement.
+ findings = [_finding("iam_rotate_access_key_90_days", "PASS")]
+ rows = _rows_for("2.13", findings, {"max_unused_access_keys_days": 120})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
+
+ def test_region_mute_constraint_forces_fail(self):
+ # Requirement 5.16 maps securityhub_enabled with a
+ # mute_non_default_regions == false constraint: muting non-default
+ # regions makes the PASS untrustworthy, so the row must be FAIL.
+ findings = [_finding("securityhub_enabled", "PASS")]
+ rows = _rows_for("5.16", findings, {"mute_non_default_regions": True})
+ assert rows, "expected a row for requirement 5.16"
+ assert all(r.Status == "FAIL" for r in rows)
+ assert all("Configuration not valid" in r.StatusExtended for r in rows)
+
+ def test_region_mute_constraint_default_passes(self):
+ findings = [_finding("securityhub_enabled", "PASS")]
+ rows = _rows_for("5.16", findings, {"mute_non_default_regions": False})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
diff --git a/tests/lib/outputs/compliance/cis/cis_azure_config_requirements_test.py b/tests/lib/outputs/compliance/cis/cis_azure_config_requirements_test.py
new file mode 100644
index 0000000000..a34402ec77
--- /dev/null
+++ b/tests/lib/outputs/compliance/cis/cis_azure_config_requirements_test.py
@@ -0,0 +1,75 @@
+"""Integration coverage for the ``subset`` set-operator in a CSV output.
+
+CIS Azure 5.0 requirement 9.1.3 maps ``storage_smb_channel_encryption_with_secure_algorithm``
+with a ``recommended_smb_channel_encryption_algorithms subset ["AES-256-GCM"]``
+constraint: widening the allowlist with a weaker algorithm makes the PASS
+untrustworthy, so the requirement row must be FAIL. Exercises the shared override
+path through a per-provider CSV class (not just OCSF)."""
+
+import json
+import pathlib
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.check.compliance_models import Compliance
+from prowler.lib.outputs.compliance.cis.cis_azure import AzureCIS
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[5]
+_CIS_5_0_AZURE = _REPO_ROOT / "prowler" / "compliance" / "azure" / "cis_5.0_azure.json"
+_REQUIREMENT_ID = "9.1.3"
+_CHECK = "storage_smb_channel_encryption_with_secure_algorithm"
+
+
+def _load():
+ return Compliance(**json.load(open(_CIS_5_0_AZURE)))
+
+
+def _finding(check_id, status):
+ return SimpleNamespace(
+ provider="azure",
+ account_uid="00000000-0000-0000-0000-000000000000",
+ region="eastus",
+ check_id=check_id,
+ status=status,
+ status_extended=f"{check_id} {status}",
+ resource_uid="/subscriptions/x/storageAccounts/sa",
+ resource_name="sa",
+ muted=False,
+ )
+
+
+def _rows_for(audit_config):
+ findings = [_finding(_CHECK, "PASS")]
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider"
+ ) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ out = AzureCIS(findings=findings, compliance=_load(), file_path=None)
+ return [r for r in out._data if r.Requirements_Id == _REQUIREMENT_ID]
+
+
+class Test_CIS_Azure_Subset_Constraint:
+ def test_widened_allowlist_forces_fail(self):
+ rows = _rows_for(
+ {
+ "recommended_smb_channel_encryption_algorithms": [
+ "AES-128-CCM",
+ "AES-256-GCM",
+ ]
+ }
+ )
+ assert rows, f"expected a row for requirement {_REQUIREMENT_ID}"
+ assert all(r.Status == "FAIL" for r in rows)
+ assert all("Configuration not valid" in r.StatusExtended for r in rows)
+
+ def test_secure_allowlist_keeps_pass(self):
+ rows = _rows_for(
+ {"recommended_smb_channel_encryption_algorithms": ["AES-256-GCM"]}
+ )
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
+
+ def test_absent_config_keeps_pass(self):
+ rows = _rows_for({})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
diff --git a/tests/lib/outputs/compliance/cis/cis_table_test.py b/tests/lib/outputs/compliance/cis/cis_table_test.py
new file mode 100644
index 0000000000..c47e1387a0
--- /dev/null
+++ b/tests/lib/outputs/compliance/cis/cis_table_test.py
@@ -0,0 +1,162 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.cis.cis import get_cis_table
+
+
+def _strip_ansi(text):
+ return re.sub(r"\x1b\[[0-9;]*m", "", text)
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _attr(section, profile="Level 1"):
+ return SimpleNamespace(Section=section, Profile=profile)
+
+
+def _make_compliance(provider, attributes, version="1.4", framework="CIS"):
+ """Build a per-check CIS compliance with the given (section, profile) attrs."""
+ return SimpleNamespace(
+ Framework=framework,
+ Version=version,
+ Provider=provider,
+ Requirements=[SimpleNamespace(Attributes=attributes)],
+ )
+
+
+def _make_compliance_multi_req(provider, attributes, version="1.4", framework="CIS"):
+ """Build a per-check CIS compliance where each attr is its own requirement,
+ simulating a check that appears in several requirements."""
+ return SimpleNamespace(
+ Framework=framework,
+ Version=version,
+ Provider=provider,
+ Requirements=[SimpleNamespace(Attributes=[attr]) for attr in attributes],
+ )
+
+
+class TestCISTable:
+ """Verify multi-section counting and provider-column attribution for the CIS compliance table."""
+
+ def test_muted_multi_section_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED finding mapped to several sections must increment the
+ per-section Muted column for every section, not only the first seen.
+
+ CIS counts FAIL/PASS through Level 1/Level 2 buckets, so only the Muted
+ per-section count was affected by the undercount bug.
+ """
+ bulk_metadata = {
+ # check_a is muted and belongs to two sections at once.
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("1 IAM"), _attr("2 Logging")])
+ ]
+ ),
+ # A real (non-muted) finding so the table is rendered.
+ "check_b": SimpleNamespace(
+ Compliance=[_make_compliance("aws", [_attr("1 IAM")])]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_cis_table(
+ findings,
+ bulk_metadata,
+ "cis_1.4_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # Both section rows must carry a Muted count of 1 in their last cell.
+ # Before the fix only the first section seen got incremented.
+ muted_one_rows = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_one_rows) == 2
+
+ def test_same_section_level_not_double_counted(self, capsys, tmp_path):
+ """A single finding whose check maps to several requirements that share
+ the same section and profile must count once for that section/level,
+ not once per requirement (FAIL(1), never FAIL(2))."""
+ bulk_metadata = {
+ # check_a is a single FAIL mapped to two requirements, both in the
+ # same section "1 IAM" and the same profile "Level 1".
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance_multi_req("aws", [_attr("1 IAM"), _attr("1 IAM")])
+ ]
+ ),
+ # A second finding in another section so the table renders.
+ "check_b": SimpleNamespace(
+ Compliance=[_make_compliance("aws", [_attr("2 Logging")])]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_cis_table(
+ findings,
+ bulk_metadata,
+ "cis_1.4_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # The "1 IAM" row must show FAIL(1) for Level 1, never FAIL(2).
+ assert "FAIL(1)" in plain
+ assert "FAIL(2)" not in plain
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched CIS compliance, not
+ from a different framework that trails it in the compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("1 IAM")]),
+ _make_compliance(
+ "gcp", [_attr("Other")], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("1 IAM")]),
+ _make_compliance(
+ "gcp", [_attr("Other")], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_cis_table(
+ findings,
+ bulk_metadata,
+ "cis_1.4_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The trailing unrelated framework's provider must not leak in.
+ assert "gcp" not in captured.out
diff --git a/tests/lib/outputs/compliance/config_status_dispatch_coverage_test.py b/tests/lib/outputs/compliance/config_status_dispatch_coverage_test.py
new file mode 100644
index 0000000000..a4f09551a5
--- /dev/null
+++ b/tests/lib/outputs/compliance/config_status_dispatch_coverage_test.py
@@ -0,0 +1,168 @@
+"""End-to-end coverage: every shipped framework that declares ``ConfigRequirements``
+must apply the config-status override through the *real* table dispatcher.
+
+The companion ``config_status_renderer_coverage_test`` proves no renderer file
+ignores the override. This test closes the other half of the gap that let
+``okta_idaas_stig`` ship ConfigRequirements its renderers never applied: it walks
+every per-provider compliance JSON that declares constraints, routes a synthetic
+PASS finding through ``display_compliance_table`` exactly as a scan would, and
+asserts the requirement is forced to FAIL when the scan's config is too loose.
+
+It runs each framework twice — once with a config that *violates* the first
+constraint and once with a config that *satisfies* it — and asserts the violating
+run reports strictly more failures. Comparing the two runs is language-neutral
+(only the parenthesised counts are read, never the localized PASS/FAIL labels) and
+self-checking (a renderer that ignored the override would report equal counts).
+
+Universal (multi-provider) frameworks render through a different path and are
+covered by ``universal/universal_table_config_requirements_test.py``.
+"""
+
+import glob
+import io
+import json
+import pathlib
+import re
+import tempfile
+from contextlib import redirect_stdout
+from types import SimpleNamespace
+from unittest.mock import patch
+
+import pytest
+
+from prowler.lib.check.compliance_models import Compliance
+from prowler.lib.outputs.compliance.compliance import display_compliance_table
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[4]
+_COMPLIANCE_DIR = _REPO_ROOT / "prowler" / "compliance"
+
+# Per-provider JSONs live in a provider subdir; top-level files are universal.
+_PROVIDER_JSONS = sorted(glob.glob(str(_COMPLIANCE_DIR / "*" / "*.json")))
+
+
+def _first_constraint(data):
+ """Return ``(check, config_key, operator, value)`` of the first declared
+ constraint, or ``None`` when the framework declares none."""
+ for requirement in data.get("Requirements", []):
+ constraints = requirement.get("ConfigRequirements")
+ if constraints:
+ c = constraints[0]
+ return c["Check"], c["ConfigKey"], c["Operator"], c["Value"]
+ return None
+
+
+def _violating_value(operator, value):
+ """A config value that breaks the constraint (forces the requirement FAIL)."""
+ if operator == "lte":
+ return value + 1
+ if operator == "gte":
+ return value - 1
+ if operator == "eq":
+ if isinstance(value, bool):
+ return not value
+ if isinstance(value, (int, float)):
+ return value + 1
+ return f"{value}__violates__"
+ if operator == "in":
+ return "__not_in_allowed_set__"
+ if operator == "subset":
+ return list(value) + ["__extra_not_allowed__"]
+ if operator == "superset":
+ return []
+ raise AssertionError(f"unhandled operator {operator}")
+
+
+def _satisfying_value(operator, value):
+ """A config value that satisfies the constraint (requirement keeps its status)."""
+ if operator in ("lte", "gte", "eq"):
+ return value
+ if operator == "in":
+ return value[0]
+ if operator == "subset":
+ return list(value)
+ if operator == "superset":
+ return list(value)
+ raise AssertionError(f"unhandled operator {operator}")
+
+
+def _fail_count(findings, bulk, name, provider, applied_config):
+ """Render the framework table with ``applied_config`` and return the FAIL
+ count from the overview, or ``None`` when the table renders nothing."""
+
+ def _not_implemented(*_a, **_k):
+ raise NotImplementedError
+
+ fake_provider = SimpleNamespace(
+ audit_config=applied_config,
+ type=provider,
+ display_compliance_table=_not_implemented,
+ )
+ buffer = io.StringIO()
+ with tempfile.TemporaryDirectory() as tmp:
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider",
+ return_value=fake_provider,
+ ):
+ with redirect_stdout(buffer):
+ display_compliance_table(findings, bulk, name, "output", tmp, False)
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", buffer.getvalue())
+ # The overview's first parenthesised count is always the FAIL tally, in
+ # every renderer and every locale (only the label is translated).
+ counts = re.findall(r"\(\s*(\d+)\s*\)", plain)
+ return int(counts[0]) if counts else None
+
+
+def _frameworks_with_constraints():
+ for path in _PROVIDER_JSONS:
+ with open(path, encoding="utf-8") as f:
+ data = json.load(f)
+ if _first_constraint(data):
+ name = pathlib.Path(path).stem
+ yield pytest.param(path, data, id=name)
+
+
+@pytest.mark.parametrize("path, data", list(_frameworks_with_constraints()))
+def test_framework_constraints_force_fail_through_dispatcher(path, data):
+ provider = pathlib.Path(path).parent.name
+ name = pathlib.Path(path).stem
+ check, config_key, operator, value = _first_constraint(data)
+ compliance = Compliance(**data)
+
+ def _finding():
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check),
+ check_id=check,
+ status="PASS",
+ muted=False,
+ )
+
+ # Two findings: the renderers only print the table when more than one
+ # finding maps to the framework.
+ findings = [_finding(), _finding()]
+ bulk = {check: SimpleNamespace(Compliance=[compliance])}
+
+ strict = _fail_count(
+ findings, bulk, name, provider, {config_key: _satisfying_value(operator, value)}
+ )
+ loose = _fail_count(
+ findings, bulk, name, provider, {config_key: _violating_value(operator, value)}
+ )
+
+ if strict is None and loose is None:
+ # The framework's renderer gates rendering on its name/version and does
+ # not paint a table for this framework id. There is no status to assert
+ # here; the renderer itself is still proven config-aware by
+ # config_status_renderer_coverage_test. Surfaced rather than silently
+ # passed so the skip is visible.
+ pytest.skip(f"{name}: renderer paints no table for this framework id")
+
+ assert strict == 0, (
+ f"{name}: PASS findings reported {strict} failures with a compliant "
+ "config; the control run should be clean."
+ )
+ assert loose and loose > 0, (
+ f"{name}: a PASS finding whose requirement maps {check} ran with "
+ f"{config_key} too loose for the constraint ({operator} {value}) was NOT "
+ "forced to FAIL. The framework declares ConfigRequirements its renderer "
+ "fails to apply — wire it through the config-status helpers."
+ )
diff --git a/tests/lib/outputs/compliance/config_status_renderer_coverage_test.py b/tests/lib/outputs/compliance/config_status_renderer_coverage_test.py
new file mode 100644
index 0000000000..ac0981c941
--- /dev/null
+++ b/tests/lib/outputs/compliance/config_status_renderer_coverage_test.py
@@ -0,0 +1,71 @@
+"""Guard that every dedicated compliance renderer applies the config-status rule.
+
+Declaring ``ConfigRequirements`` in a framework JSON is inert unless the renderer
+that builds its output actually evaluates them. A requirement whose configurable
+checks ran with a config too loose to trust must be forced to FAIL; that override
+lives in ``prowler.lib.check.compliance_config_eval`` and every renderer that
+emits a finding's status (CSV transform, CLI table, OCSF) must route through it.
+
+This test statically asserts the invariant: any renderer that reads a finding's
+raw ``status`` must also reference one of the config-status helpers. It mirrors
+the manual audit that caught ``okta_idaas_stig`` shipping ConfigRequirements that
+its CSV and table renderers never applied, so the gap cannot silently reopen.
+"""
+
+import pathlib
+
+import pytest
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[4]
+_RENDERER_DIR = _REPO_ROOT / "prowler" / "lib" / "outputs" / "compliance"
+
+# Base/dispatch modules that orchestrate renderers but never emit a status row.
+_EXCLUDED_BASENAMES = {
+ "__init__.py",
+ "models.py",
+ "compliance.py",
+ "compliance_check.py",
+ "compliance_output.py",
+}
+
+# Any one of these, present in the source, means the renderer wires the override.
+_CONFIG_STATUS_HELPERS = (
+ "apply_config_status",
+ "build_requirement_config_status",
+ "resolve_requirement_config_status",
+ "get_effective_status",
+)
+
+# A renderer builds its output from the finding's raw status via one of these.
+_RAW_STATUS_MARKERS = ("finding.status", "finding.status_extended")
+
+
+def _renderer_sources():
+ for path in sorted(_RENDERER_DIR.glob("**/*.py")):
+ if path.name in _EXCLUDED_BASENAMES or "__pycache__" in path.parts:
+ continue
+ yield path
+
+
+@pytest.mark.parametrize(
+ "renderer_path",
+ [
+ pytest.param(p, id=str(p.relative_to(_RENDERER_DIR)))
+ for p in _renderer_sources()
+ ],
+)
+def test_renderer_emitting_status_applies_config_status(renderer_path):
+ source = renderer_path.read_text(encoding="utf-8")
+
+ uses_raw_status = any(marker in source for marker in _RAW_STATUS_MARKERS)
+ if not uses_raw_status:
+ pytest.skip("renderer does not emit a finding's raw status")
+
+ applies_config_status = any(helper in source for helper in _CONFIG_STATUS_HELPERS)
+ assert applies_config_status, (
+ f"{renderer_path.relative_to(_REPO_ROOT)} emits a finding's raw status but "
+ "never applies the config-status override. Route it through "
+ "apply_config_status / build_requirement_config_status (CSV/OCSF) or "
+ "resolve_requirement_config_status / get_effective_status (CLI table), "
+ "otherwise its ConfigRequirements are silently ignored."
+ )
diff --git a/tests/lib/outputs/compliance/display_compliance_table_test.py b/tests/lib/outputs/compliance/display_compliance_table_test.py
index 0d2cd5313b..bd854d6d7d 100644
--- a/tests/lib/outputs/compliance/display_compliance_table_test.py
+++ b/tests/lib/outputs/compliance/display_compliance_table_test.py
@@ -96,25 +96,19 @@ class TestDispatchStartswith:
@pytest.mark.parametrize(
"framework_name",
- [
- "csa_ccm_4.0_aws",
- "csa_ccm_4.0_azure",
- "csa_ccm_4.0_gcp",
- "csa_ccm_4.0_oraclecloud",
- "csa_ccm_4.0_alibabacloud",
- ],
+ ["c5_aws", "c5_azure", "c5_gcp"],
)
- @patch(f"{MODULE}.get_csa_table")
- def test_csa_dispatch(self, mock_fn, framework_name):
+ @patch(f"{MODULE}.get_c5_table")
+ def test_c5_dispatch(self, mock_fn, framework_name):
display_compliance_table(compliance_framework=framework_name, **_COMMON)
mock_fn.assert_called_once()
@pytest.mark.parametrize(
"framework_name",
- ["c5_aws", "c5_azure", "c5_gcp"],
+ ["okta_idaas_stig_v1r2_okta"],
)
- @patch(f"{MODULE}.get_c5_table")
- def test_c5_dispatch(self, mock_fn, framework_name):
+ @patch(f"{MODULE}.get_okta_idaas_stig_table")
+ def test_okta_idaas_stig_dispatch(self, mock_fn, framework_name):
display_compliance_table(compliance_framework=framework_name, **_COMMON)
mock_fn.assert_called_once()
diff --git a/tests/lib/outputs/compliance/ens/ens_aws_config_requirements_test.py b/tests/lib/outputs/compliance/ens/ens_aws_config_requirements_test.py
new file mode 100644
index 0000000000..b09d9bc0b3
--- /dev/null
+++ b/tests/lib/outputs/compliance/ens/ens_aws_config_requirements_test.py
@@ -0,0 +1,61 @@
+"""Integration coverage proving the shared requirement-level config validation
+is applied beyond CIS. ENS RD2022 AWS requirement ``op.exp.1.aws.cfg.1`` maps
+``config_recorder_all_regions_enabled`` with a ``mute_non_default_regions ==
+false`` constraint; muting non-default regions makes a PASS untrustworthy, so
+the requirement row must be FAIL even when the finding PASSes. The applied
+config is read from the active provider's ``audit_config``."""
+
+import json
+import pathlib
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.check.compliance_models import Compliance
+from prowler.lib.outputs.compliance.ens.ens_aws import AWSENS
+
+_REPO_ROOT = pathlib.Path(__file__).resolve().parents[5]
+_ENS = _REPO_ROOT / "prowler" / "compliance" / "aws" / "ens_rd2022_aws.json"
+_REQUIREMENT_ID = "op.exp.1.aws.cfg.1"
+
+
+def _load_ens() -> Compliance:
+ return Compliance(**json.load(open(_ENS)))
+
+
+def _finding(check_id: str, status: str):
+ return SimpleNamespace(
+ provider="aws",
+ account_uid="123456789012",
+ region="us-east-1",
+ check_id=check_id,
+ status=status,
+ status_extended=f"{check_id} {status}",
+ resource_uid="arn:aws:config:us-east-1:123456789012:recorder/default",
+ resource_name="default",
+ muted=False,
+ )
+
+
+def _rows_for(requirement_id, findings, audit_config):
+ with patch(
+ "prowler.providers.common.provider.Provider.get_global_provider"
+ ) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ out = AWSENS(findings=findings, compliance=_load_ens(), file_path=None)
+ return [r for r in out._data if r.Requirements_Id == requirement_id]
+
+
+class Test_ENS_AWS_Config_Requirements:
+ def test_region_mute_constraint_forces_fail(self):
+ findings = [_finding("config_recorder_all_regions_enabled", "PASS")]
+ rows = _rows_for(_REQUIREMENT_ID, findings, {"mute_non_default_regions": True})
+ assert rows, f"expected a row for requirement {_REQUIREMENT_ID}"
+ assert all(r.Status == "FAIL" for r in rows)
+ assert all("Configuration not valid" in r.StatusExtended for r in rows)
+
+ def test_default_config_keeps_finding_status(self):
+ findings = [_finding("config_recorder_all_regions_enabled", "PASS")]
+ rows = _rows_for(_REQUIREMENT_ID, findings, {})
+ assert rows
+ assert all(r.Status == "PASS" for r in rows)
+ assert all("Configuration not valid" not in r.StatusExtended for r in rows)
diff --git a/tests/lib/outputs/compliance/ens/ens_table_test.py b/tests/lib/outputs/compliance/ens/ens_table_test.py
new file mode 100644
index 0000000000..2373885dbc
--- /dev/null
+++ b/tests/lib/outputs/compliance/ens/ens_table_test.py
@@ -0,0 +1,235 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.ens.ens import get_ens_table
+
+
+def _strip_ansi(text):
+ return re.sub(r"\x1b\[[0-9;]*m", "", text)
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _attr(marco, categoria, tipo="requisito", nivel="alto"):
+ return SimpleNamespace(Marco=marco, Categoria=categoria, Tipo=tipo, Nivel=nivel)
+
+
+def _make_compliance(provider, attributes, framework="ENS"):
+ """Build a per-check ENS compliance with the given marco/categoria attrs."""
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[SimpleNamespace(Attributes=attributes)],
+ )
+
+
+class TestENSTable:
+ """Test cases for ENS compliance table rendering.
+
+ Verify multi-marco counting and provider-column attribution for the
+ compliance table.
+ """
+
+ def test_no_cumple_marked_in_every_marco(self, capsys, tmp_path):
+ """A single failing finding mapped to several marcos must mark every
+ one of them as NO CUMPLE, not only the first marco seen."""
+ bulk_metadata = {
+ # check_a fails and belongs to two distinct marcos/categorias.
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "aws",
+ [
+ _attr("operacional", "control de acceso"),
+ _attr("organizativo", "politica de seguridad"),
+ ],
+ )
+ ]
+ ),
+ # A passing finding so the overview total reaches 2.
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("operacional", "control de acceso")])
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_ens_table(
+ findings,
+ bulk_metadata,
+ "ens_rd2022_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # Both marco rows the failing finding maps to must read NO CUMPLE.
+ # Before the fix only the first marco was marked, the second stayed
+ # CUMPLE. Anchor the assertion to the actual marco rows (not the
+ # overview header line which also mentions NO CUMPLE).
+ op_row = [
+ line
+ for line in plain.splitlines()
+ if "operacional/control de acceso" in line
+ ]
+ org_row = [
+ line
+ for line in plain.splitlines()
+ if "organizativo/politica de seguridad" in line
+ ]
+ assert len(op_row) == 1 and "NO CUMPLE" in op_row[0]
+ assert len(org_row) == 1 and "NO CUMPLE" in org_row[0]
+
+ def test_recomendacion_does_not_set_no_cumple(self, capsys, tmp_path):
+ """A FAIL on a 'recomendacion' attribute must not flip a marco to
+ NO CUMPLE (this path is intentionally excluded from the fix)."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "aws",
+ [
+ _attr(
+ "operacional", "control de acceso", tipo="recomendacion"
+ )
+ ],
+ )
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("organizativo", "politica")])
+ ]
+ ),
+ # A regular (non-recomendacion) check so the results table renders
+ # at least one marco row and the assertion below is not vacuous.
+ "check_c": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("operacional", "continuidad")])
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ _make_finding("check_c", "PASS"),
+ ]
+
+ get_ens_table(
+ findings,
+ bulk_metadata,
+ "ens_rd2022_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # The recomendacion FAIL must not appear as a NO CUMPLE marco row in the
+ # results table (the overview header line is allowed to mention it).
+ marco_rows = [
+ line
+ for line in plain.splitlines()
+ if "operacional" in line or "organizativo" in line
+ ]
+ # Guard against a vacuous pass: the table must actually render rows.
+ assert marco_rows
+ assert all("NO CUMPLE" not in line for line in marco_rows)
+
+ def test_muted_multi_marco_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED finding mapped to several marcos must increment the
+ per-marco Muted column for every marco, not only the first seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "aws",
+ [
+ _attr("operacional", "control de acceso"),
+ _attr("organizativo", "politica de seguridad"),
+ ],
+ )
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", [_attr("operacional", "control de acceso")])
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_ens_table(
+ findings,
+ bulk_metadata,
+ "ens_rd2022_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # Both marco rows the muted finding maps to must report a Muted count of
+ # 1 in their last cell.
+ muted_one_rows = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_one_rows) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Proveedor column must come from the matched ENS compliance, not
+ from a different framework that trails it in the compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "aws", [_attr("operacional", "control de acceso")]
+ ),
+ _make_compliance(
+ "gcp", [_attr("x", "y")], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "aws", [_attr("operacional", "control de acceso")]
+ ),
+ _make_compliance(
+ "gcp", [_attr("x", "y")], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_ens_table(
+ findings,
+ bulk_metadata,
+ "ens_rd2022_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ assert "gcp" not in captured.out
diff --git a/tests/lib/outputs/compliance/fixtures.py b/tests/lib/outputs/compliance/fixtures.py
index e1929ee4d4..a8fc7aa7e5 100644
--- a/tests/lib/outputs/compliance/fixtures.py
+++ b/tests/lib/outputs/compliance/fixtures.py
@@ -16,6 +16,7 @@ from prowler.lib.check.compliance_models import (
Mitre_Requirement_Attribute_Azure,
Mitre_Requirement_Attribute_GCP,
Prowler_ThreatScore_Requirement_Attribute,
+ STIG_Requirement_Attribute,
)
CIS_1_4_AWS = Compliance(
@@ -128,7 +129,7 @@ CIS_2_0_GCP = Compliance(
Description="This CIS Benchmark is the product of a community consensus process and consists of secure configuration guidelines developed for Google Cloud Computing Platform",
Requirements=[
Compliance_Requirement(
- Checks=["apikeys_key_exits"],
+ Checks=["apikeys_key_exits", "service_test_check_id"],
Id="2.13",
Description="Ensure That Microsoft Defender for Databases Is Set To 'On'",
Attributes=[
@@ -177,7 +178,7 @@ CIS_1_8_KUBERNETES = Compliance(
Description="This CIS Kubernetes Benchmark provides prescriptive guidance for establishing a secure configuration posture for Kubernetes v1.27.",
Requirements=[
Compliance_Requirement(
- Checks=["apiserver_always_pull_images_plugin"],
+ Checks=["apiserver_always_pull_images_plugin", "service_test_check_id"],
Id="1.1.3",
Description="Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive",
Attributes=[
@@ -259,6 +260,7 @@ CIS_4_0_M365 = Compliance(
Compliance_Requirement(
Checks=[
"mfa_delete_enabled",
+ "service_test_check_id",
],
Id="2.1.3",
Description="Ensure MFA Delete is enabled on S3 buckets",
@@ -336,6 +338,7 @@ MITRE_ATTACK_AWS = Compliance(
"inspector2_active_findings_exist",
"awslambda_function_not_publicly_accessible",
"ec2_instance_public_ip",
+ "service_test_check_id",
],
),
Mitre_Requirement(
@@ -412,6 +415,7 @@ MITRE_ATTACK_AZURE = Compliance(
"defender_ensure_notify_emails_to_owners",
"defender_ensure_system_updates_are_applied",
"defender_ensure_wdatp_is_enabled",
+ "service_test_check_id",
],
),
Mitre_Requirement(
@@ -467,6 +471,7 @@ MITRE_ATTACK_GCP = Compliance(
"compute_instance_public_ip",
"compute_public_address_shodan",
"kms_key_not_publicly_accessible",
+ "service_test_check_id",
],
),
Mitre_Requirement(
@@ -514,7 +519,7 @@ ENS_RD2022_AWS = Compliance(
Dependencias=[],
)
],
- Checks=["cloudtrail_log_file_validation_enabled"],
+ Checks=["cloudtrail_log_file_validation_enabled", "service_test_check_id"],
),
Compliance_Requirement(
Id="op.exp.8.aws.ct.4",
@@ -562,7 +567,7 @@ ENS_RD2022_AZURE = Compliance(
Dependencias=[],
)
],
- Checks=["cloudtrail_log_file_validation_enabled"],
+ Checks=["cloudtrail_log_file_validation_enabled", "service_test_check_id"],
),
Compliance_Requirement(
Id="op.exp.8.azure.ct.4",
@@ -609,7 +614,7 @@ ENS_RD2022_GCP = Compliance(
Dependencias=[],
)
],
- Checks=["cloudtrail_log_file_validation_enabled"],
+ Checks=["cloudtrail_log_file_validation_enabled", "service_test_check_id"],
),
Compliance_Requirement(
Id="op.exp.8.gcp.ct.4",
@@ -666,7 +671,10 @@ AWS_WELL_ARCHITECTED = Compliance(
ImplementationGuidanceUrl="https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/sec_securely_operate_multi_accounts.html#implementation-guidance.",
)
],
- Checks=["organizations_account_part_of_organizations"],
+ Checks=[
+ "organizations_account_part_of_organizations",
+ "service_test_check_id",
+ ],
),
Compliance_Requirement(
Id="SEC01-BP02",
@@ -709,7 +717,7 @@ ISO27001_2013_AWS = Compliance(
Check_Summary="Setup Encryption at rest for RDS instances",
)
],
- Checks=["rds_instance_storage_encrypted"],
+ Checks=["rds_instance_storage_encrypted", "service_test_check_id"],
),
Compliance_Requirement(
Id="A.10.2",
@@ -759,6 +767,7 @@ NIST_800_53_REVISION_4_AWS = Compliance(
"rds_instance_integration_cloudwatch_logs",
"redshift_cluster_audit_logging",
"securityhub_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -815,6 +824,7 @@ KISA_ISMSP_AWS = Compliance(
Checks=[
"cloudwatch_log_metric_filter_authentication_failures",
"cognito_user_pool_mfa_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -872,6 +882,7 @@ PROWLER_THREATSCORE_AWS = Compliance(
],
Checks=[
"iam_root_mfa_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -916,6 +927,7 @@ PROWLER_THREATSCORE_AZURE = Compliance(
],
Checks=[
"iam_root_mfa_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -960,6 +972,7 @@ PROWLER_THREATSCORE_GCP = Compliance(
],
Checks=[
"iam_root_mfa_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -1004,6 +1017,7 @@ PROWLER_THREATSCORE_M365 = Compliance(
],
Checks=[
"iam_root_mfa_enabled",
+ "service_test_check_id",
],
),
Compliance_Requirement(
@@ -1245,3 +1259,47 @@ ASD_ESSENTIAL_EIGHT_AWS = Compliance(
),
],
)
+
+OKTA_IDAAS_STIG_OKTA = Compliance(
+ Framework="Okta-IDaaS-STIG",
+ Name="DISA Okta Identity as a Service (IDaaS) STIG V1R2",
+ Version="1R2",
+ Provider="Okta",
+ Description="Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) for Okta Identity as a Service (IDaaS).",
+ Requirements=[
+ Compliance_Requirement(
+ Id="OKTA-APP-000020",
+ Name="Okta must log out a session after a 15-minute period of inactivity.",
+ Description="A session timeout lock is a temporary action taken when a user stops work and moves away from the immediate vicinity of the information system.",
+ Attributes=[
+ STIG_Requirement_Attribute(
+ Section="CAT II (Medium)",
+ Severity="medium",
+ RuleID="SV-273186r1098825_rule",
+ StigID="OKTA-APP-000020",
+ CCI=["CCI-000057", "CCI-001133"],
+ CheckText="Verify the Global Session Policy logs out a session after 15 minutes of inactivity.",
+ FixText="From the Admin Console configure the Global Session Policy idle timeout to 15 minutes.",
+ )
+ ],
+ Checks=["signon_global_session_idle_timeout_15min"],
+ ),
+ Compliance_Requirement(
+ Id="OKTA-APP-000650",
+ Name="Okta must enforce a minimum 15-character password length.",
+ Description="The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.",
+ Attributes=[
+ STIG_Requirement_Attribute(
+ Section="CAT II (Medium)",
+ Severity="medium",
+ RuleID="SV-273209r1098894_rule",
+ StigID="OKTA-APP-000650",
+ CCI=["CCI-000205"],
+ CheckText="Verify the password policy enforces a minimum length of 15 characters.",
+ FixText="From the Admin Console set the minimum password length to 15 characters.",
+ )
+ ],
+ Checks=[],
+ ),
+ ],
+)
diff --git a/tests/lib/outputs/compliance/generic/generic_aws_test.py b/tests/lib/outputs/compliance/generic/generic_aws_test.py
index cda9a08bd3..335a9ad17d 100644
--- a/tests/lib/outputs/compliance/generic/generic_aws_test.py
+++ b/tests/lib/outputs/compliance/generic/generic_aws_test.py
@@ -5,6 +5,12 @@ from unittest import mock
from freezegun import freeze_time
from mock import patch
+from prowler.lib.check.compliance_models import (
+ Compliance,
+ Compliance_Requirement,
+ Generic_Compliance_Requirement_Attribute,
+ ISO27001_2013_Requirement_Attribute,
+)
from prowler.lib.outputs.compliance.generic.generic import GenericCompliance
from prowler.lib.outputs.compliance.generic.models import GenericComplianceModel
from tests.lib.outputs.compliance.fixtures import NIST_800_53_REVISION_4_AWS
@@ -129,3 +135,111 @@ class TestAWSGenericCompliance:
expected_csv = f"PROVIDER;DESCRIPTION;ACCOUNTID;REGION;ASSESSMENTDATE;REQUIREMENTS_ID;REQUIREMENTS_DESCRIPTION;REQUIREMENTS_ATTRIBUTES_SECTION;REQUIREMENTS_ATTRIBUTES_SUBSECTION;REQUIREMENTS_ATTRIBUTES_SUBGROUP;REQUIREMENTS_ATTRIBUTES_SERVICE;REQUIREMENTS_ATTRIBUTES_TYPE;STATUS;STATUSEXTENDED;RESOURCEID;CHECKID;MUTED;RESOURCENAME;FRAMEWORK;NAME;REQUIREMENTS_ATTRIBUTES_COMMENT\r\naws;NIST 800-53 is a regulatory standard that defines the minimum baseline of security controls for all U.S. federal information systems except those related to national security. The controls defined in this standard are customizable and address a diverse set of security and privacy requirements.;123456789012;eu-west-1;{datetime.now()};ac_2_4;Account Management;Access Control (AC);Account Management (AC-2);;aws;;PASS;;;service_test_check_id;False;;NIST-800-53-Revision-4;National Institute of Standards and Technology (NIST) 800-53 Revision 4;\r\naws;NIST 800-53 is a regulatory standard that defines the minimum baseline of security controls for all U.S. federal information systems except those related to national security. The controls defined in this standard are customizable and address a diverse set of security and privacy requirements.;;;{datetime.now()};ac_2_5;Account Management;Access Control (AC);Account Management (AC-2);;aws;;MANUAL;Manual check;manual_check;manual;False;Manual check;NIST-800-53-Revision-4;National Institute of Standards and Technology (NIST) 800-53 Revision 4;\r\n"
assert content == expected_csv
+
+ def test_csv_row_count_matches_framework_checks_not_stored_compliance(self):
+ """Regression test for PROWLER-1763.
+
+ Ensures CSV emission is driven by the framework JSON's Requirements[].Checks
+ (the same source the UI uses) and not by the per-finding `finding.compliance`
+ snapshot stored at scan time. If `finding.check_id` is in a requirement's
+ Checks list, the row must be emitted regardless of what was stored in
+ `finding.compliance`. Conversely, a stale `finding.compliance` entry pointing
+ to a requirement whose Checks list no longer contains the finding's check_id
+ must not produce a row.
+ """
+ framework_name = "Test-Framework-1763"
+ compliance = Compliance(
+ Framework=framework_name,
+ Name=framework_name,
+ Provider="AWS",
+ Version="",
+ Description="Regression fixture for PROWLER-1763",
+ Requirements=[
+ Compliance_Requirement(
+ Id="req_in_framework",
+ Description="Requirement currently in framework",
+ Attributes=[
+ Generic_Compliance_Requirement_Attribute(
+ Section="Section A", Service="aws"
+ )
+ ],
+ Checks=["service_check_in_framework"],
+ ),
+ Compliance_Requirement(
+ Id="req_no_longer_in_framework",
+ Description="Requirement whose Checks list no longer includes the finding's check_id",
+ Attributes=[
+ Generic_Compliance_Requirement_Attribute(
+ Section="Section B", Service="aws"
+ )
+ ],
+ Checks=["service_different_check"],
+ ),
+ ],
+ )
+
+ # Snapshot drift case: finding.compliance maps to a requirement whose
+ # current Checks list no longer includes the finding's check_id, AND
+ # the finding belongs to a requirement that is NOT in the snapshot.
+ findings = [
+ generate_finding_output(
+ check_id="service_check_in_framework",
+ compliance={framework_name: ["req_no_longer_in_framework"]},
+ )
+ ]
+
+ output = GenericCompliance(findings, compliance)
+ rows = [
+ row
+ for row in output.data
+ if row.Status != "MANUAL" and row.ResourceName != "Manual check"
+ ]
+ assert (
+ len(rows) == 1
+ ), f"Expected 1 row driven by framework JSON, got {len(rows)}"
+ assert rows[0].Requirements_Id == "req_in_framework"
+ assert rows[0].CheckId == "service_check_in_framework"
+
+ def test_transform_tolerates_framework_specific_attribute_schema(self):
+ """GenericCompliance is the documented last-resort renderer, so it must not
+ crash on a framework whose attribute schema lacks the universal fields
+ (Section, SubSection, SubGroup, Service, Type, Comment). ISO27001 declares
+ none of them; missing fields must render as None instead of raising
+ AttributeError and dropping the whole CSV."""
+ framework_name = "ISO27001-2013-External"
+ compliance = Compliance(
+ Framework=framework_name,
+ Name=framework_name,
+ Provider="external",
+ Version="",
+ Description="Framework shipping a provider-specific attribute schema",
+ Requirements=[
+ Compliance_Requirement(
+ Id="A.5.1.1",
+ Description="Policies for information security",
+ Attributes=[
+ ISO27001_2013_Requirement_Attribute(
+ Category="Information security policies",
+ Objetive_ID="A.5.1",
+ Objetive_Name="Management direction",
+ Check_Summary="Policy is defined",
+ )
+ ],
+ Checks=["service_test_check_id"],
+ )
+ ],
+ )
+
+ findings = [generate_finding_output(check_id="service_test_check_id")]
+
+ output = GenericCompliance(findings, compliance)
+
+ rows = [row for row in output.data if row.Status != "MANUAL"]
+ assert len(rows) == 1
+ assert rows[0].Requirements_Id == "A.5.1.1"
+ assert rows[0].Requirements_Attributes_Section is None
+ assert rows[0].Requirements_Attributes_SubSection is None
+ assert rows[0].Requirements_Attributes_SubGroup is None
+ assert rows[0].Requirements_Attributes_Service is None
+ assert rows[0].Requirements_Attributes_Type is None
+ assert rows[0].Requirements_Attributes_Comment is None
diff --git a/tests/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_table_test.py b/tests/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_table_test.py
new file mode 100644
index 0000000000..be0fe25ad5
--- /dev/null
+++ b/tests/lib/outputs/compliance/kisa_ismsp/kisa_ismsp_table_test.py
@@ -0,0 +1,137 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.kisa_ismsp.kisa_ismsp import get_kisa_ismsp_table
+
+# The generator matches a compliance when its Framework starts with "KISA" and
+# its Version is contained in the compliance_framework argument.
+COMPLIANCE_FRAMEWORK = "kisa-isms-p-2023_aws"
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(
+ provider, sections, framework="KISA-ISMS-P", version="kisa-isms-p-2023"
+):
+ """Build a per-check compliance covering the given sections."""
+ return SimpleNamespace(
+ Framework=framework,
+ Version=version,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(Attributes=[SimpleNamespace(Section=section)])
+ for section in sections
+ ],
+ )
+
+
+class TestKISAISMSPTable:
+ """Verify multi-section counting and provider-column attribution for the KISA ISMS-P compliance table."""
+
+ def test_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several sections must show FAIL(1) in
+ every section, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_kisa_ismsp_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Logging must report FAIL(1); before the fix Logging was
+ # undercounted because the per-section count was gated by the global
+ # dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several sections must increase the
+ per-section Muted count in every section, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_kisa_ismsp_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both IAM and Logging, so the Muted column
+ # must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched KISA compliance, never
+ from a different framework that happens to be the last entry in the
+ check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_kisa_ismsp_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/mitre_attack/mitre_attack_table_test.py b/tests/lib/outputs/compliance/mitre_attack/mitre_attack_table_test.py
new file mode 100644
index 0000000000..3bd69b44e8
--- /dev/null
+++ b/tests/lib/outputs/compliance/mitre_attack/mitre_attack_table_test.py
@@ -0,0 +1,140 @@
+import re
+from types import SimpleNamespace
+
+from prowler.lib.outputs.compliance.mitre_attack.mitre_attack import (
+ get_mitre_attack_table,
+)
+
+# The generator matches a compliance when "MITRE-ATTACK" is in its Framework and
+# its Version is contained in the compliance_framework argument.
+COMPLIANCE_FRAMEWORK = "mitre_attack_aws"
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(
+ provider, tactics, framework="MITRE-ATTACK", version="mitre_attack"
+):
+ """Build a per-check compliance covering the given tactics."""
+ return SimpleNamespace(
+ Framework=framework,
+ Version=version,
+ Provider=provider,
+ Requirements=[SimpleNamespace(Tactics=tactics)],
+ )
+
+
+class TestMitreAttackTable:
+ """Test multi-section counting and provider-column attribution for the compliance table."""
+
+ def test_multi_tactic_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several tactics must show FAIL(1) in
+ every tactic, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["Persistence", "Execution"])]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["Persistence"])]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_mitre_attack_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both Persistence and Execution must report FAIL(1); before the fix
+ # Execution was undercounted because the per-tactic count was gated by
+ # the global dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_tactic_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several tactics must increase the
+ per-tactic Muted count in every tactic, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["Persistence", "Execution"])]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["Persistence"])]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A second finding is needed so the table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_mitre_attack_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both Persistence and Execution, so the
+ # Muted column must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched MITRE-ATTACK
+ compliance, never from a different framework that happens to be the last
+ entry in the check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["Persistence"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["Persistence"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_mitre_attack_table(
+ findings,
+ bulk_metadata,
+ COMPLIANCE_FRAMEWORK,
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta_test.py b/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta_test.py
new file mode 100644
index 0000000000..a6a0267851
--- /dev/null
+++ b/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_okta_test.py
@@ -0,0 +1,192 @@
+from datetime import datetime
+from io import StringIO
+from unittest import mock
+
+from freezegun import freeze_time
+from mock import patch
+
+from prowler.lib.check.compliance_config_eval import CONFIG_NOT_VALID_PREFIX
+from prowler.lib.check.compliance_models import (
+ Compliance_Requirement_ConfigConstraint,
+)
+from prowler.lib.outputs.compliance.okta_idaas_stig.models import OktaIDaaSSTIGModel
+from prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig_okta import (
+ OktaIDaaSSTIG,
+)
+from tests.lib.outputs.compliance.fixtures import OKTA_IDAAS_STIG_OKTA
+from tests.lib.outputs.fixtures.fixtures import generate_finding_output
+
+OKTA_ORG_DOMAIN = "dev-12345.okta.com"
+
+
+class TestOktaIDaaSSTIG:
+ def test_output_transform(self):
+ findings = [
+ generate_finding_output(
+ provider="okta",
+ account_uid=OKTA_ORG_DOMAIN,
+ account_name=OKTA_ORG_DOMAIN,
+ region="global",
+ service_name="signon",
+ check_id="signon_global_session_idle_timeout_15min",
+ resource_uid="okta-global-session-policy",
+ resource_name="Default Policy",
+ compliance={"Okta-IDaaS-STIG-1R2": ["OKTA-APP-000020"]},
+ )
+ ]
+
+ output = OktaIDaaSSTIG(findings, OKTA_IDAAS_STIG_OKTA)
+ output_data = output.data[0]
+ assert isinstance(output_data, OktaIDaaSSTIGModel)
+ assert output_data.Provider == "okta"
+ assert output_data.Framework == OKTA_IDAAS_STIG_OKTA.Framework
+ assert output_data.Name == OKTA_IDAAS_STIG_OKTA.Name
+ assert output_data.OrganizationDomain == OKTA_ORG_DOMAIN
+ assert output_data.Description == OKTA_IDAAS_STIG_OKTA.Description
+ assert output_data.Requirements_Id == OKTA_IDAAS_STIG_OKTA.Requirements[0].Id
+ assert (
+ output_data.Requirements_Name == OKTA_IDAAS_STIG_OKTA.Requirements[0].Name
+ )
+ assert (
+ output_data.Requirements_Description
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Description
+ )
+ assert (
+ output_data.Requirements_Attributes_Section
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].Section
+ )
+ assert (
+ output_data.Requirements_Attributes_Severity
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].Severity.value
+ )
+ assert (
+ output_data.Requirements_Attributes_RuleID
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].RuleID
+ )
+ assert (
+ output_data.Requirements_Attributes_StigID
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].StigID
+ )
+ assert (
+ output_data.Requirements_Attributes_CCI
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].CCI
+ )
+ assert (
+ output_data.Requirements_Attributes_CheckText
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].CheckText
+ )
+ assert (
+ output_data.Requirements_Attributes_FixText
+ == OKTA_IDAAS_STIG_OKTA.Requirements[0].Attributes[0].FixText
+ )
+ assert output_data.Status == "PASS"
+ assert output_data.StatusExtended == ""
+ assert output_data.ResourceId == "okta-global-session-policy"
+ assert output_data.ResourceName == "Default Policy"
+ assert output_data.CheckId == "signon_global_session_idle_timeout_15min"
+ assert output_data.Muted is False
+ # Test manual check
+ output_data_manual = output.data[1]
+ assert output_data_manual.Provider == "okta"
+ assert output_data_manual.Framework == OKTA_IDAAS_STIG_OKTA.Framework
+ assert output_data_manual.Name == OKTA_IDAAS_STIG_OKTA.Name
+ assert output_data_manual.OrganizationDomain == ""
+ assert (
+ output_data_manual.Requirements_Id
+ == OKTA_IDAAS_STIG_OKTA.Requirements[1].Id
+ )
+ assert (
+ output_data_manual.Requirements_Attributes_Severity
+ == OKTA_IDAAS_STIG_OKTA.Requirements[1].Attributes[0].Severity.value
+ )
+ assert (
+ output_data_manual.Requirements_Attributes_StigID
+ == OKTA_IDAAS_STIG_OKTA.Requirements[1].Attributes[0].StigID
+ )
+ assert output_data_manual.Status == "MANUAL"
+ assert output_data_manual.StatusExtended == "Manual check"
+ assert output_data_manual.ResourceId == "manual_check"
+ assert output_data_manual.ResourceName == "Manual check"
+ assert output_data_manual.CheckId == "manual"
+ assert output_data_manual.Muted is False
+
+ @freeze_time("2025-01-01 00:00:00")
+ @mock.patch(
+ "prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig_okta.timestamp",
+ "2025-01-01 00:00:00",
+ )
+ def test_batch_write_data_to_file(self):
+ mock_file = StringIO()
+ findings = [
+ generate_finding_output(
+ provider="okta",
+ account_uid=OKTA_ORG_DOMAIN,
+ account_name=OKTA_ORG_DOMAIN,
+ region="global",
+ service_name="signon",
+ check_id="signon_global_session_idle_timeout_15min",
+ resource_uid="okta-global-session-policy",
+ resource_name="Default Policy",
+ compliance={"Okta-IDaaS-STIG-1R2": ["OKTA-APP-000020"]},
+ )
+ ]
+ output = OktaIDaaSSTIG(findings, OKTA_IDAAS_STIG_OKTA)
+ output._file_descriptor = mock_file
+
+ with patch.object(mock_file, "close", return_value=None):
+ output.batch_write_data_to_file()
+
+ mock_file.seek(0)
+ content = mock_file.read()
+ expected_csv = f"PROVIDER;DESCRIPTION;ORGANIZATIONDOMAIN;ASSESSMENTDATE;REQUIREMENTS_ID;REQUIREMENTS_NAME;REQUIREMENTS_DESCRIPTION;REQUIREMENTS_ATTRIBUTES_SECTION;REQUIREMENTS_ATTRIBUTES_SEVERITY;REQUIREMENTS_ATTRIBUTES_RULEID;REQUIREMENTS_ATTRIBUTES_STIGID;REQUIREMENTS_ATTRIBUTES_CCI;REQUIREMENTS_ATTRIBUTES_CHECKTEXT;REQUIREMENTS_ATTRIBUTES_FIXTEXT;STATUS;STATUSEXTENDED;RESOURCEID;RESOURCENAME;CHECKID;MUTED;FRAMEWORK;NAME\r\nokta;Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) for Okta Identity as a Service (IDaaS).;{OKTA_ORG_DOMAIN};{datetime.now()};OKTA-APP-000020;Okta must log out a session after a 15-minute period of inactivity.;A session timeout lock is a temporary action taken when a user stops work and moves away from the immediate vicinity of the information system.;CAT II (Medium);medium;SV-273186r1098825_rule;OKTA-APP-000020;['CCI-000057', 'CCI-001133'];Verify the Global Session Policy logs out a session after 15 minutes of inactivity.;From the Admin Console configure the Global Session Policy idle timeout to 15 minutes.;PASS;;okta-global-session-policy;Default Policy;signon_global_session_idle_timeout_15min;False;Okta-IDaaS-STIG;DISA Okta Identity as a Service (IDaaS) STIG V1R2\r\nokta;Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) for Okta Identity as a Service (IDaaS).;;{datetime.now()};OKTA-APP-000650;Okta must enforce a minimum 15-character password length.;The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.;CAT II (Medium);medium;SV-273209r1098894_rule;OKTA-APP-000650;['CCI-000205'];Verify the password policy enforces a minimum length of 15 characters.;From the Admin Console set the minimum password length to 15 characters.;MANUAL;Manual check;manual_check;Manual check;manual;False;Okta-IDaaS-STIG;DISA Okta Identity as a Service (IDaaS) STIG V1R2\r\n"
+
+ assert content == expected_csv
+
+ def test_config_status_override_forces_fail(self):
+ """A PASS finding whose requirement declares a ConfigRequirements
+ constraint the scan's config violates must be reported as FAIL in the
+ CSV, with the config-not-valid reason prepended to StatusExtended."""
+ # Inject a config constraint on the first requirement (idle timeout must
+ # be <= 15 minutes) without mutating the shared fixture.
+ compliance = OKTA_IDAAS_STIG_OKTA.copy(deep=True)
+ compliance.Requirements[0].ConfigRequirements = [
+ Compliance_Requirement_ConfigConstraint(
+ Check="signon_global_session_idle_timeout_15min",
+ ConfigKey="okta_max_session_idle_minutes",
+ Operator="lte",
+ Value=15,
+ )
+ ]
+ findings = [
+ generate_finding_output(
+ provider="okta",
+ account_uid=OKTA_ORG_DOMAIN,
+ account_name=OKTA_ORG_DOMAIN,
+ region="global",
+ service_name="signon",
+ status="PASS",
+ status_extended="Idle timeout is configured.",
+ check_id="signon_global_session_idle_timeout_15min",
+ resource_uid="okta-global-session-policy",
+ resource_name="Default Policy",
+ compliance={"Okta-IDaaS-STIG-1R2": ["OKTA-APP-000020"]},
+ )
+ ]
+
+ # The scan applied a 30-minute idle timeout, too loose for the 15-minute
+ # requirement, so the PASS must be overridden to FAIL.
+ with (
+ patch(
+ "prowler.lib.check.compliance_config_eval.get_scan_audit_config",
+ return_value={"okta_max_session_idle_minutes": 30},
+ ),
+ patch(
+ "prowler.lib.check.compliance_config_eval.get_scan_provider_type",
+ return_value="okta",
+ ),
+ ):
+ output = OktaIDaaSSTIG(findings, compliance)
+
+ output_data = output.data[0]
+ assert output_data.Status == "FAIL"
+ assert output_data.StatusExtended.startswith(CONFIG_NOT_VALID_PREFIX)
diff --git a/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_table_test.py b/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_table_test.py
new file mode 100644
index 0000000000..0dd353760b
--- /dev/null
+++ b/tests/lib/outputs/compliance/okta_idaas_stig/okta_idaas_stig_table_test.py
@@ -0,0 +1,211 @@
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig import (
+ get_okta_idaas_stig_table,
+)
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ check_id=check_id,
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(
+ provider,
+ sections,
+ framework="Okta-IDaaS-STIG",
+ checks=None,
+ config_requirements=None,
+):
+ """Build a per-check compliance covering the given sections.
+
+ ``checks`` and ``config_requirements`` let a section's requirement declare
+ the checks it owns and the config constraints that gate it, so the table's
+ config-status override can be exercised.
+ """
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(
+ Id=f"REQ-{section}",
+ Checks=list(checks or []),
+ ConfigRequirements=list(config_requirements or []),
+ Attributes=[SimpleNamespace(Section=section)],
+ )
+ for section in sections
+ ],
+ )
+
+
+class TestOktaIDaaSSTIGTable:
+ """Test cases for Okta IDaaS STIG compliance table rendering."""
+
+ def test_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several sections must show FAIL(1) in
+ every section, not just the first one seen."""
+ bulk_metadata = {
+ # check_a belongs to two sections at once.
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("okta", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("okta", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_okta_idaas_stig_table(
+ findings,
+ bulk_metadata,
+ "okta_idaas_stig_1r2",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Logging must report FAIL(1); before the fix Logging
+ # was undercounted and rendered as plain PASS.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several sections must increase the
+ per-section Muted count in every section, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("okta", ["IAM", "Logging"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("okta", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ get_okta_idaas_stig_table(
+ findings,
+ bulk_metadata,
+ "okta_idaas_stig_1r2",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # The muted check belongs to both IAM and Logging, so the Muted column
+ # must read 1 in both rows. Before the fix only the first section seen
+ # was incremented, leaving the second at 0.
+ # Strip ANSI color codes before counting the bare values per row.
+ import re
+
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # Each section row ends with its Muted value in its own cell; both rows
+ # must carry a Muted count of 1.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched Okta-IDaaS-STIG
+ compliance, never from a different framework that happens to be the
+ last entry in the check's compliance list."""
+ # check_a maps to Okta-IDaaS-STIG (provider "okta") but its compliance
+ # list ends with a *different* framework whose provider is "aws". With
+ # the bug the leaked loop variable made the table render "aws".
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("okta", ["IAM"]),
+ _make_compliance("aws", ["Other"], framework="OtherFramework"),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("okta", ["IAM"]),
+ _make_compliance("aws", ["Other"], framework="OtherFramework"),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ get_okta_idaas_stig_table(
+ findings,
+ bulk_metadata,
+ "okta_idaas_stig_1r2",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "okta" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "aws" not in captured.out
+
+ def test_config_status_override_forces_fail(self, capsys, tmp_path):
+ """A configurable check that PASSes but ran with a config too loose for
+ its requirement must be forced to FAIL in the table, honouring the
+ requirement's ConfigRequirements. Without the override check_a would be
+ PASS and no results table would render at all."""
+ constraint = {
+ "Check": "check_a",
+ "ConfigKey": "okta_max_session_idle_minutes",
+ "Operator": "lte",
+ "Value": 15,
+ }
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance(
+ "okta",
+ ["IAM"],
+ checks=["check_a"],
+ config_requirements=[constraint],
+ )
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[_make_compliance("okta", ["Logging"])]
+ ),
+ }
+ # Both checks PASS on their own; the scan applied a 30-minute idle
+ # timeout, which is too loose for the 15-minute requirement.
+ findings = [
+ _make_finding("check_a", "PASS"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ with (
+ patch(
+ "prowler.lib.outputs.compliance.okta_idaas_stig.okta_idaas_stig.get_scan_audit_config",
+ return_value={"okta_max_session_idle_minutes": 30},
+ ),
+ patch(
+ "prowler.lib.check.compliance_config_eval.get_scan_provider_type",
+ return_value="okta",
+ ),
+ ):
+ get_okta_idaas_stig_table(
+ findings,
+ bulk_metadata,
+ "okta_idaas_stig_1r2",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # check_a was forced to FAIL by the config override, so its section
+ # (IAM) must report FAIL(1).
+ assert "FAIL(1)" in captured.out
diff --git a/tests/lib/outputs/compliance/process_universal_test.py b/tests/lib/outputs/compliance/process_universal_test.py
index fa8b737ddd..4dc957ed4f 100644
--- a/tests/lib/outputs/compliance/process_universal_test.py
+++ b/tests/lib/outputs/compliance/process_universal_test.py
@@ -12,6 +12,7 @@ Also validates that print_compliance_frameworks and print_compliance_requirement
work with universal ComplianceFramework objects (dict checks, None provider).
"""
+import csv
import json
import os
from datetime import datetime, timezone
@@ -124,6 +125,41 @@ def _make_universal_framework(name="TestFW", version="1.0", with_table_config=Tr
)
+def _make_framework_with_manual(name="MixedFW", version="1.0"):
+ """Framework with one aws-covered requirement and one manual one.
+
+ The manual requirement has no aws checks, so for provider ``aws`` it is
+ emitted as a manual row/event — used to assert manual requirements are
+ not duplicated when the writer is reused across streaming batches.
+ """
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="Covered requirement",
+ attributes={"Section": "IAM"},
+ checks={"aws": ["check_a"]},
+ ),
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="Manual requirement",
+ attributes={"Section": "GOV"},
+ checks={"aws": []},
+ ),
+ ]
+ metadata = [AttributeMetadata(key="Section", type="str")]
+ outputs = OutputsConfig(table_config=TableConfig(group_by="Section"))
+ return ComplianceFramework(
+ framework=name,
+ name=f"{name} Framework",
+ provider="AWS",
+ version=version,
+ description="Test framework",
+ requirements=reqs,
+ attributes_metadata=metadata,
+ outputs=outputs,
+ )
+
+
# ── Tests ────────────────────────────────────────────────────────────
@@ -728,3 +764,243 @@ class TestIdempotency:
# FW1 writer instances unchanged
assert second_writers[0] is first_writers[0]
assert second_writers[1] is first_writers[1]
+
+
+class TestStreamingBatches:
+ """Streaming-aware behaviour: ``from_cli`` / ``is_last`` / ``_flush``.
+
+ Regression coverage for the API streaming path where the helper is
+ invoked once per finding batch: before the fix only the first batch
+ was written (batches 2..N silently dropped) and manual requirements
+ were re-emitted on every batch.
+ """
+
+ def _run_batches(self, tmp_path, fw, key, batches):
+ """Invoke the helper once per (findings, is_last) batch, sharing
+ ``generated_outputs`` so writers are reused like the API does."""
+ generated = {"compliance": []}
+ for findings, is_last in batches:
+ process_universal_compliance_frameworks(
+ input_compliance_frameworks={key},
+ universal_frameworks={key: fw},
+ finding_outputs=findings,
+ output_directory=str(tmp_path),
+ output_filename="out",
+ provider="aws",
+ generated_outputs=generated,
+ from_cli=False,
+ is_last=is_last,
+ )
+ return generated
+
+ def test_defaults_preserve_cli_single_call(self, tmp_path):
+ """Defaults (``from_cli=True``, ``is_last=True``): a single call
+ still finalizes a valid, closed OCSF JSON array (CLI unchanged)."""
+ fw = _make_universal_framework()
+ generated = {"compliance": []}
+ process_universal_compliance_frameworks(
+ input_compliance_frameworks={"test_fw_1.0"},
+ universal_frameworks={"test_fw_1.0": fw},
+ finding_outputs=[_make_finding("check_a")],
+ output_directory=str(tmp_path),
+ output_filename="out",
+ provider="aws",
+ generated_outputs=generated,
+ )
+ ocsf_path = tmp_path / "compliance" / "out_test_fw_1.0.ocsf.json"
+ data = json.loads(ocsf_path.read_text())
+ assert isinstance(data, list) and len(data) >= 1
+
+ def test_multibatch_csv_keeps_every_batch(self, tmp_path):
+ """Findings from batches 2..N must not be dropped (the bug)."""
+ fw = _make_universal_framework()
+ f1 = _make_finding("check_a", status="PASS")
+ f2 = _make_finding("check_a", status="FAIL")
+ generated = self._run_batches(
+ tmp_path, fw, "fw_1.0", [([f1], False), ([f2], True)]
+ )
+ content = (tmp_path / "compliance" / "out_fw_1.0.csv").read_text()
+ assert "check_a is PASS" in content # batch 1
+ assert "check_a is FAIL" in content # batch 2 — regression
+ # writer reused, not recreated: still just 1 CSV + 1 OCSF
+ assert len(generated["compliance"]) == 2
+
+ def test_multibatch_ocsf_valid_array_with_every_batch(self, tmp_path):
+ """OCSF is a valid (closed) JSON array holding every batch's
+ events only after the ``is_last=True`` call."""
+ fw = _make_universal_framework()
+ f1 = _make_finding("check_a", status="PASS")
+ f2 = _make_finding("check_a", status="FAIL")
+ self._run_batches(tmp_path, fw, "fw_1.0", [([f1], False), ([f2], True)])
+ data = json.loads(
+ (tmp_path / "compliance" / "out_fw_1.0.ocsf.json").read_text()
+ )
+ assert isinstance(data, list)
+ assert len(data) >= 2 # one event per batch finding
+
+ def test_manual_requirement_not_duplicated_across_batches(self, tmp_path):
+ """Manual requirement is emitted once (first batch, via __init__),
+ never re-emitted when the writer is reused (``include_manual=False``)."""
+ fw = _make_framework_with_manual()
+ f1 = _make_finding("check_a", status="PASS")
+ f2 = _make_finding("check_a", status="FAIL")
+ self._run_batches(tmp_path, fw, "fw_1.0", [([f1], False), ([f2], True)])
+ rows = list(
+ csv.DictReader(
+ (tmp_path / "compliance" / "out_fw_1.0.csv").read_text().splitlines(),
+ delimiter=";",
+ )
+ )
+ manual_rows = [r for r in rows if r["STATUS"] == "MANUAL"]
+ assert len(manual_rows) == 1
+ assert manual_rows[0]["REQUIREMENTS_ID"] == "2.1"
+
+ ocsf = json.loads(
+ (tmp_path / "compliance" / "out_fw_1.0.ocsf.json").read_text()
+ )
+ manual_events = [
+ e
+ for e in ocsf
+ if (e.get("compliance") or {}).get("requirements") == ["2.1"]
+ ]
+ assert len(manual_events) == 1
+
+ def test_writer_reused_not_recreated_across_batches(self, tmp_path):
+ """Three batches still yield exactly one CSV + one OCSF writer,
+ and the same instances are reused throughout."""
+ fw = _make_universal_framework()
+ generated = self._run_batches(
+ tmp_path,
+ fw,
+ "fw_1.0",
+ [
+ ([_make_finding("check_a")], False),
+ ([_make_finding("check_a")], False),
+ ([_make_finding("check_a")], True),
+ ],
+ )
+ assert len(generated["compliance"]) == 2
+ assert isinstance(generated["compliance"][0], UniversalComplianceOutput)
+ assert isinstance(generated["compliance"][1], OCSFComplianceOutput)
+
+ def test_label_without_version_still_outputs(self, tmp_path):
+ """Empty framework version → label is the framework name only;
+ the helper still produces both artifacts without error."""
+ fw = _make_universal_framework(version="")
+ generated = {"compliance": []}
+ processed = process_universal_compliance_frameworks(
+ input_compliance_frameworks={"fw"},
+ universal_frameworks={"fw": fw},
+ finding_outputs=[_make_finding("check_a")],
+ output_directory=str(tmp_path),
+ output_filename="out",
+ provider="aws",
+ generated_outputs=generated,
+ from_cli=False,
+ is_last=True,
+ )
+ assert processed == {"fw"}
+ assert len(generated["compliance"]) == 2
+ assert (tmp_path / "compliance" / "out_fw.csv").exists()
+ assert (tmp_path / "compliance" / "out_fw.ocsf.json").exists()
+
+
+def _csa_like_framework() -> ComplianceFramework:
+ """Build a CSA CCM-style universal framework with checks across providers."""
+ requirement = UniversalComplianceRequirement(
+ id="A&A-01",
+ description="Audit and Assurance",
+ attributes={"Section": "Audit"},
+ checks={
+ "aws": ["aws_check"],
+ "azure": ["azure_check"],
+ "gcp": ["gcp_check"],
+ },
+ )
+ return ComplianceFramework(
+ framework="CSA_CCM",
+ name="CSA Cloud Controls Matrix",
+ version="4.0",
+ description="Multi-provider framework",
+ requirements=[requirement],
+ attributes_metadata=[AttributeMetadata(key="Section", type="str")],
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+class TestMultiProviderUniversalFramework:
+ """A top-level CSA-CCM-style framework produces a CSV+OCSF pair scoped
+ to the provider it is invoked with."""
+
+ @pytest.mark.parametrize(
+ "provider,check_id",
+ [
+ ("aws", "aws_check"),
+ ("azure", "azure_check"),
+ ("gcp", "gcp_check"),
+ ],
+ )
+ def test_per_provider_outputs_isolated(self, tmp_path, provider, check_id):
+ framework = _csa_like_framework()
+ generated = {"compliance": []}
+
+ process_universal_compliance_frameworks(
+ input_compliance_frameworks={"csa_ccm_4.0"},
+ universal_frameworks={"csa_ccm_4.0": framework},
+ finding_outputs=[_make_finding(check_id, provider=provider)],
+ output_directory=str(tmp_path),
+ output_filename="prowler_output",
+ provider=provider,
+ generated_outputs=generated,
+ )
+
+ ocsf_path = tmp_path / "compliance" / "prowler_output_csa_ccm_4.0.ocsf.json"
+ events = json.loads(ocsf_path.read_text())
+ assert isinstance(events, list)
+ non_manual = [event for event in events if event.get("status_code") != "MANUAL"]
+ assert len(non_manual) == 1
+ assert non_manual[0]["compliance"]["checks"][0]["uid"] == check_id
+
+
+class TestMitreStyleOCSFOutput:
+ """MITRE attrs wrapped as `{"_raw_attributes": [...]}` must not leak
+ the marker key through the OCSF pipeline."""
+
+ def test_mitre_raw_attributes_pass_through_pipeline(self, tmp_path):
+ mitre_requirement = UniversalComplianceRequirement(
+ id="T1078",
+ description="Valid Accounts",
+ attributes={
+ "_raw_attributes": [{"AWSService": "IAM", "Category": "Initial Access"}]
+ },
+ checks={"aws": ["check_a"]},
+ )
+ framework = ComplianceFramework(
+ framework="MITRE",
+ name="MITRE ATT&CK",
+ version="14",
+ description="Mitre",
+ requirements=[mitre_requirement],
+ outputs=OutputsConfig(table_config=TableConfig(group_by="AWSService")),
+ )
+ generated = {"compliance": []}
+
+ process_universal_compliance_frameworks(
+ input_compliance_frameworks={"mitre_attack_aws"},
+ universal_frameworks={"mitre_attack_aws": framework},
+ finding_outputs=[_make_finding("check_a", "PASS")],
+ output_directory=str(tmp_path),
+ output_filename="out",
+ provider="aws",
+ generated_outputs=generated,
+ )
+
+ ocsf_path = tmp_path / "compliance" / "out_mitre_attack_aws.ocsf.json"
+ events = json.loads(ocsf_path.read_text())
+ assert isinstance(events, list) and len(events) >= 1
+ for event in events:
+ requirement_attrs = (event.get("unmapped") or {}).get(
+ "requirement_attributes", {}
+ )
+ assert "_raw_attributes" not in requirement_attrs
+ assert "raw_attributes" not in requirement_attrs
diff --git a/tests/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_table_test.py b/tests/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_table_test.py
new file mode 100644
index 0000000000..d754395dc3
--- /dev/null
+++ b/tests/lib/outputs/compliance/prowler_threatscore/prowler_threatscore_table_test.py
@@ -0,0 +1,147 @@
+import re
+from types import SimpleNamespace
+from unittest import mock
+
+from prowler.lib.outputs.compliance.prowler_threatscore.prowler_threatscore import (
+ get_prowler_threatscore_table,
+)
+
+# Patch target for the Compliance.get_bulk lookup used to render pillars without
+# findings; the tests don't exercise that path so it returns nothing.
+COMPLIANCE_PATH = (
+ "prowler.lib.outputs.compliance.prowler_threatscore.prowler_threatscore.Compliance"
+)
+
+
+def _make_finding(check_id, status="PASS", muted=False):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=check_id),
+ status=status,
+ muted=muted,
+ )
+
+
+def _make_compliance(provider, pillars, framework="ProwlerThreatScore"):
+ """Build a per-check compliance covering the given pillars (Section)."""
+ return SimpleNamespace(
+ Framework=framework,
+ Provider=provider,
+ Requirements=[
+ SimpleNamespace(
+ Attributes=[SimpleNamespace(Section=pillar, LevelOfRisk=5, Weight=100)]
+ )
+ for pillar in pillars
+ ],
+ )
+
+
+class TestProwlerThreatScoreTable:
+ """Verify multi-section counting and provider-column attribution for the compliance table."""
+
+ def test_multi_pillar_fail_not_undercounted(self, capsys, tmp_path):
+ """A single FAIL check mapped to several pillars must show FAIL(1) in
+ every pillar, not just the first one seen."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Encryption"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ with mock.patch(COMPLIANCE_PATH) as compliance_mock:
+ compliance_mock.get_bulk.return_value = {}
+ get_prowler_threatscore_table(
+ findings,
+ bulk_metadata,
+ "prowler_threatscore_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ # Both IAM and Encryption must report FAIL(1); before the fix Encryption
+ # was undercounted because the per-pillar count was gated by the global
+ # dedup list.
+ assert captured.out.count("FAIL(1)") == 2
+
+ def test_multi_pillar_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED check mapped to several pillars must increase the
+ per-pillar Muted count in every pillar, not only the first one."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[_make_compliance("aws", ["IAM", "Encryption"])]
+ ),
+ "check_b": SimpleNamespace(Compliance=[_make_compliance("aws", ["IAM"])]),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ # A real FAIL is needed so the results table is rendered at all.
+ _make_finding("check_b", "FAIL"),
+ ]
+
+ with mock.patch(COMPLIANCE_PATH) as compliance_mock:
+ compliance_mock.get_bulk.return_value = {}
+ get_prowler_threatscore_table(
+ findings,
+ bulk_metadata,
+ "prowler_threatscore_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ plain = re.sub(r"\x1b\[[0-9;]*m", "", captured.out)
+ # The muted check belongs to both IAM and Encryption, so the Muted
+ # column must read 1 in both rows.
+ muted_cells = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_cells) == 2
+
+ def test_provider_column_not_leaked_from_other_framework(self, capsys, tmp_path):
+ """The Provider column must come from the matched ProwlerThreatScore
+ compliance, never from a different framework that happens to be the last
+ entry in the check's compliance list."""
+ bulk_metadata = {
+ "check_a": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ "check_b": SimpleNamespace(
+ Compliance=[
+ _make_compliance("aws", ["IAM"]),
+ _make_compliance(
+ "leaked_provider", ["Other"], framework="OtherFramework"
+ ),
+ ]
+ ),
+ }
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+
+ with mock.patch(COMPLIANCE_PATH) as compliance_mock:
+ compliance_mock.get_bulk.return_value = {}
+ get_prowler_threatscore_table(
+ findings,
+ bulk_metadata,
+ "prowler_threatscore_aws",
+ "output",
+ str(tmp_path),
+ False,
+ )
+
+ captured = capsys.readouterr()
+ assert "aws" in captured.out
+ # The provider of the unrelated trailing framework must NOT leak into
+ # the rendered table.
+ assert "leaked_provider" not in captured.out
diff --git a/tests/lib/outputs/compliance/universal/ocsf_compliance_config_requirements_test.py b/tests/lib/outputs/compliance/universal/ocsf_compliance_config_requirements_test.py
new file mode 100644
index 0000000000..c846385d88
--- /dev/null
+++ b/tests/lib/outputs/compliance/universal/ocsf_compliance_config_requirements_test.py
@@ -0,0 +1,191 @@
+"""Integration coverage for ConfigRequirements in the OCSF compliance output.
+
+OCSF is the universal output path every framework renders through, so it is the
+natural place to exercise the requirement-level config override end to end across
+all operators. When a requirement's configurable check ran with a config too
+loose to trust, the Compliance status must be FAIL (even on a PASS finding) and
+the message must carry the ``Configuration not valid`` marker. The Check status keeps
+the real finding status.
+"""
+
+from datetime import datetime, timezone
+from types import SimpleNamespace
+from unittest.mock import patch
+
+import pytest
+from py_ocsf_models.objects.compliance_status import StatusID as ComplianceStatusID
+
+from prowler.lib.check.compliance_models import (
+ ComplianceFramework,
+ OutputsConfig,
+ TableConfig,
+ UniversalComplianceRequirement,
+)
+from prowler.lib.outputs.compliance.universal.ocsf_compliance import (
+ OCSFComplianceOutput,
+)
+
+_MODULE = "prowler.providers.common.provider.Provider.get_global_provider"
+
+
+def _finding(check_id, status="PASS", provider="aws"):
+ finding = SimpleNamespace()
+ finding.provider = provider
+ finding.account_uid = "123456789012"
+ finding.account_name = "test-account"
+ finding.account_email = ""
+ finding.account_organization_uid = "org-123"
+ finding.account_organization_name = "test-org"
+ finding.account_tags = {"env": "test"}
+ finding.region = "us-east-1"
+ finding.status = status
+ finding.status_extended = f"{check_id} is {status}"
+ finding.resource_uid = f"arn:aws:iam::123456789012:{check_id}"
+ finding.resource_name = check_id
+ finding.resource_details = "details"
+ finding.resource_metadata = {}
+ finding.resource_tags = {"Name": "test"}
+ finding.partition = "aws"
+ finding.muted = False
+ finding.check_id = check_id
+ finding.uid = "test-finding-uid"
+ finding.timestamp = datetime(2025, 1, 15, 12, 0, 0, tzinfo=timezone.utc)
+ finding.prowler_version = "5.0.0"
+ finding.compliance = {}
+ finding.metadata = SimpleNamespace(
+ Provider=provider,
+ CheckID=check_id,
+ CheckTitle=f"Title for {check_id}",
+ CheckType=["test-type"],
+ Description=f"Description for {check_id}",
+ Severity="medium",
+ ServiceName="iam",
+ ResourceType="aws-iam-role",
+ Risk="risk",
+ RelatedUrl="https://example.com",
+ Remediation=SimpleNamespace(
+ Recommendation=SimpleNamespace(Text="Fix", Url="https://fix.com"),
+ ),
+ DependsOn=[],
+ RelatedTo=[],
+ Categories=["test"],
+ Notes="",
+ AdditionalURLs=[],
+ )
+ return finding
+
+
+def _framework(check_id, constraint):
+ req = UniversalComplianceRequirement(
+ id="REQ-1",
+ description="Requirement REQ-1",
+ attributes={},
+ checks={"aws": [check_id]},
+ config_requirements=[constraint],
+ )
+ return ComplianceFramework(
+ framework="TestFW",
+ name="Test Framework",
+ provider="AWS",
+ version="1.0",
+ description="Test framework",
+ requirements=[req],
+ attributes_metadata=None,
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+def _run(check_id, constraint, audit_config):
+ fw = _framework(check_id, constraint)
+ findings = [_finding(check_id, "PASS")]
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ out = OCSFComplianceOutput(findings=findings, framework=fw, provider="aws")
+ return out.data[0]
+
+
+# (check, constraint, violating_config, valid_config)
+_CASES = [
+ (
+ "securityhub_enabled",
+ {
+ "Check": "securityhub_enabled",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ },
+ {"mute_non_default_regions": True},
+ {"mute_non_default_regions": False},
+ ),
+ (
+ "iam_user_accesskey_unused",
+ {
+ "Check": "iam_user_accesskey_unused",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45,
+ },
+ {"max_unused_access_keys_days": 120},
+ {"max_unused_access_keys_days": 30},
+ ),
+ (
+ "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ {
+ "Check": "cloudwatch_log_group_retention_policy_specific_days_enabled",
+ "ConfigKey": "log_group_retention_days",
+ "Operator": "gte",
+ "Value": 365,
+ },
+ {"log_group_retention_days": 90},
+ {"log_group_retention_days": 365},
+ ),
+ (
+ "sqlserver_recommended_minimal_tls_version",
+ {
+ "Check": "sqlserver_recommended_minimal_tls_version",
+ "ConfigKey": "recommended_minimal_tls_versions",
+ "Operator": "subset",
+ "Value": ["1.2", "1.3"],
+ },
+ {"recommended_minimal_tls_versions": ["1.0", "1.2", "1.3"]},
+ {"recommended_minimal_tls_versions": ["1.3"]},
+ ),
+ (
+ "acm_certificates_with_secure_key_algorithms",
+ {
+ "Check": "acm_certificates_with_secure_key_algorithms",
+ "ConfigKey": "insecure_key_algorithms",
+ "Operator": "superset",
+ "Value": ["RSA-1024", "P-192"],
+ },
+ {"insecure_key_algorithms": ["P-192"]},
+ {"insecure_key_algorithms": ["RSA-1024", "P-192"]},
+ ),
+]
+
+
+class Test_OCSF_Config_Requirements:
+ @pytest.mark.parametrize(
+ "check,constraint,bad,ok",
+ _CASES,
+ ids=[c[1]["Operator"] for c in _CASES],
+ )
+ def test_violating_config_fails_requirement(self, check, constraint, bad, ok):
+ cf = _run(check, constraint, bad)
+ assert cf.compliance.status_id == ComplianceStatusID.Fail
+ assert "Configuration not valid" in cf.message
+
+ @pytest.mark.parametrize(
+ "check,constraint,bad,ok",
+ _CASES,
+ ids=[c[1]["Operator"] for c in _CASES],
+ )
+ def test_valid_config_keeps_pass(self, check, constraint, bad, ok):
+ cf = _run(check, constraint, ok)
+ assert cf.compliance.status_id == ComplianceStatusID.Pass
+ assert "Configuration not valid" not in cf.message
+
+ def test_absent_config_assumes_default_ok(self):
+ check, constraint, _bad, _ok = _CASES[0]
+ cf = _run(check, constraint, {})
+ assert cf.compliance.status_id == ComplianceStatusID.Pass
diff --git a/tests/lib/outputs/compliance/universal/ocsf_compliance_status_scoping_test.py b/tests/lib/outputs/compliance/universal/ocsf_compliance_status_scoping_test.py
new file mode 100644
index 0000000000..8408868296
--- /dev/null
+++ b/tests/lib/outputs/compliance/universal/ocsf_compliance_status_scoping_test.py
@@ -0,0 +1,129 @@
+"""Top-level status consistency and provider scoping for the OCSF output.
+
+Two regressions are covered here:
+
+1. The event's top-level ``status_code``/``status_detail`` must reflect the
+ effective (config-aware) status, so a config-invalid PASS cannot produce an
+ event where ``compliance.status_id`` says FAIL while ``status_code`` still
+ says PASS. The nested Check object keeps the raw finding status.
+2. Provider scoping: an Azure-scoped constraint must never affect an AWS output
+ even when the global provider would otherwise be relied upon.
+"""
+
+from datetime import datetime, timezone
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from py_ocsf_models.objects.compliance_status import StatusID as ComplianceStatusID
+
+from prowler.lib.check.compliance_models import (
+ ComplianceFramework,
+ OutputsConfig,
+ TableConfig,
+ UniversalComplianceRequirement,
+)
+from prowler.lib.outputs.compliance.universal.ocsf_compliance import (
+ OCSFComplianceOutput,
+)
+
+_MODULE = "prowler.providers.common.provider.Provider.get_global_provider"
+
+
+def _finding(check_id, status="PASS", provider="aws"):
+ finding = SimpleNamespace()
+ finding.provider = provider
+ finding.account_uid = "123456789012"
+ finding.account_name = "test-account"
+ finding.account_organization_uid = "org-123"
+ finding.account_organization_name = "test-org"
+ finding.region = "us-east-1"
+ finding.status = status
+ finding.status_extended = f"{check_id} is {status}"
+ finding.resource_uid = f"arn:aws:iam::123456789012:{check_id}"
+ finding.resource_name = check_id
+ finding.resource_details = "details"
+ finding.resource_metadata = {}
+ finding.resource_tags = {"Name": "test"}
+ finding.partition = "aws"
+ finding.muted = False
+ finding.check_id = check_id
+ finding.uid = "test-finding-uid"
+ finding.timestamp = datetime(2025, 1, 15, 12, 0, 0, tzinfo=timezone.utc)
+ finding.prowler_version = "5.0.0"
+ finding.metadata = SimpleNamespace(
+ CheckID=check_id,
+ CheckTitle=f"Title for {check_id}",
+ Description=f"Description for {check_id}",
+ Severity="medium",
+ ServiceName="iam",
+ ResourceType="aws-iam-role",
+ )
+ return finding
+
+
+def _framework(constraint, provider="AWS", check_provider="aws"):
+ req = UniversalComplianceRequirement(
+ id="REQ-1",
+ description="Requirement REQ-1",
+ attributes={},
+ checks={check_provider: ["check_a"]},
+ config_requirements=[constraint],
+ )
+ return ComplianceFramework(
+ framework="TestFW",
+ name="Test Framework",
+ provider=provider,
+ version="1.0",
+ description="Test framework",
+ requirements=[req],
+ attributes_metadata=None,
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+def _run(framework, audit_config, provider="aws", status="PASS"):
+ findings = [_finding("check_a", status, provider)]
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ mock_gp.return_value.type = provider
+ out = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider=provider
+ )
+ return out.data[0]
+
+
+_CONSTRAINT = {
+ "Check": "check_a",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45,
+}
+
+
+class Test_OCSF_TopLevel_Status:
+ def test_config_invalid_pass_forces_toplevel_fail(self):
+ event = _run(_framework(_CONSTRAINT), {"max_unused_access_keys_days": 120})
+ # Top-level and nested compliance status agree: both FAIL.
+ assert event.compliance.status_id == ComplianceStatusID.Fail
+ assert event.status_code == "FAIL"
+ assert "Configuration not valid" in event.status_detail
+ assert event.status_detail == event.message
+ # The nested Check preserves the raw finding result.
+ assert event.compliance.checks[0].status == "PASS"
+
+ def test_valid_config_keeps_toplevel_pass(self):
+ event = _run(_framework(_CONSTRAINT), {"max_unused_access_keys_days": 30})
+ assert event.compliance.status_id == ComplianceStatusID.Pass
+ assert event.status_code == "PASS"
+ assert "Configuration not valid" not in event.status_detail
+
+
+class Test_OCSF_Provider_Scoping:
+ def test_azure_constraint_does_not_affect_aws_output(self):
+ constraint = {**_CONSTRAINT, "Provider": "azure"}
+ event = _run(
+ _framework(constraint), {"max_unused_access_keys_days": 120}, provider="aws"
+ )
+ assert event.compliance.status_id == ComplianceStatusID.Pass
+ assert event.status_code == "PASS"
+ assert "Configuration not valid" not in event.status_detail
diff --git a/tests/lib/outputs/compliance/universal/ocsf_compliance_test.py b/tests/lib/outputs/compliance/universal/ocsf_compliance_test.py
index 71429fc1ca..db6b78de28 100644
--- a/tests/lib/outputs/compliance/universal/ocsf_compliance_test.py
+++ b/tests/lib/outputs/compliance/universal/ocsf_compliance_test.py
@@ -202,6 +202,26 @@ class TestOCSFComplianceOutput:
assert cf.status_code == "MANUAL"
assert cf.finding_info.uid == "manual-MANUAL-1"
+ def test_include_manual_false_skips_manual(self):
+ """``_transform(..., include_manual=False)`` emits check events but
+ NOT manual requirement events. The streaming caller passes ``False``
+ for batches 2..N so manual events are not duplicated."""
+ covered = _simple_requirement("REQ-1", ["check_a"])
+ manual = _simple_requirement("MANUAL-1", checks=[])
+ fw = _make_framework([covered, manual])
+ findings = [_make_finding("check_a")]
+
+ output = OCSFComplianceOutput(findings=findings, framework=fw, provider="aws")
+ # __init__ transforms with include_manual=True (default) → manual present
+ assert any(cf.status_code == "MANUAL" for cf in output.data)
+
+ # A subsequent batch re-transforms with include_manual=False
+ output._data.clear()
+ output._transform(findings, fw, "TestFW-1.0", include_manual=False)
+
+ assert len(output.data) == 1 # only the check event, no manual
+ assert all(cf.status_code != "MANUAL" for cf in output.data)
+
def test_multi_provider_checks_dict(self):
req = UniversalComplianceRequirement(
id="REQ-1",
@@ -631,3 +651,103 @@ class TestNoTopLevelOCSFImport:
import prowler.lib.outputs.compliance.universal.ocsf_compliance as mod
assert "OCSF" not in dir(mod)
+
+
+def _mitre_requirement(req_id="T1078", entries=None):
+ """Build a MITRE-style requirement with `_raw_attributes` wrapping."""
+ return UniversalComplianceRequirement(
+ id=req_id,
+ description="Valid Accounts",
+ attributes={
+ "_raw_attributes": entries
+ or [{"AWSService": "IAM", "Category": "Initial Access"}]
+ },
+ checks={"aws": ["check_a"]},
+ )
+
+
+class TestMitreRawAttributes:
+ """MITRE attrs wrapped as `{"_raw_attributes": [...]}` must not leak
+ the marker key into the OCSF payload."""
+
+ def test_raw_attributes_key_not_in_unmapped(self):
+ framework = _make_framework([_mitre_requirement()])
+ findings = [_make_finding("check_a", "PASS")]
+
+ output = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider="aws"
+ )
+
+ requirement_attrs = (output.data[0].unmapped or {}).get(
+ "requirement_attributes", {}
+ )
+ assert "_raw_attributes" not in requirement_attrs
+ assert "raw_attributes" not in requirement_attrs
+
+ def test_finding_serializes_with_raw_attributes(self):
+ framework = _make_framework(
+ [
+ _mitre_requirement(
+ entries=[
+ {"AWSService": "IAM", "Category": "Initial Access"},
+ {"AWSService": "STS", "Category": "Privilege Escalation"},
+ ]
+ )
+ ]
+ )
+ findings = [_make_finding("check_a", "PASS")]
+
+ output = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider="aws"
+ )
+ compliance_finding = output.data[0]
+ if hasattr(compliance_finding, "model_dump_json"):
+ payload = json.loads(compliance_finding.model_dump_json(exclude_none=True))
+ else:
+ payload = json.loads(compliance_finding.json(exclude_none=True))
+ assert payload["compliance"]["requirements"] == ["T1078"]
+
+
+class TestProviderFiltering:
+ """OCSF writer scopes findings against `requirement.checks[provider]`."""
+
+ def test_check_for_other_provider_not_emitted(self):
+ azure_only_requirement = UniversalComplianceRequirement(
+ id="REQ-1",
+ description="Azure-only requirement",
+ attributes={},
+ checks={"azure": ["check_a"]},
+ )
+ framework = _make_framework([azure_only_requirement])
+ findings = [_make_finding("check_a", "PASS", provider="aws")]
+
+ output = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider="aws"
+ )
+
+ assert all(
+ compliance_finding.status_code == "MANUAL"
+ for compliance_finding in output.data
+ )
+
+ def test_no_provider_aggregates_all_checks(self):
+ multi_provider_requirement = UniversalComplianceRequirement(
+ id="REQ-1",
+ description="Multi-provider requirement",
+ attributes={},
+ checks={"aws": ["check_a"], "azure": ["check_b"]},
+ )
+ framework = _make_framework([multi_provider_requirement])
+ findings = [
+ _make_finding("check_a", "PASS", provider="aws"),
+ _make_finding("check_b", "FAIL", provider="azure"),
+ ]
+
+ output = OCSFComplianceOutput(
+ findings=findings, framework=framework, provider=None
+ )
+
+ statuses = sorted(
+ compliance_finding.status_code for compliance_finding in output.data
+ )
+ assert statuses == ["FAIL", "PASS"]
diff --git a/tests/lib/outputs/compliance/universal/universal_output_config_requirements_test.py b/tests/lib/outputs/compliance/universal/universal_output_config_requirements_test.py
new file mode 100644
index 0000000000..dd83dad575
--- /dev/null
+++ b/tests/lib/outputs/compliance/universal/universal_output_config_requirements_test.py
@@ -0,0 +1,115 @@
+"""Coverage for ConfigRequirements + provider scoping in the universal CSV.
+
+The universal CSV must apply the same effective-status logic as the OCSF/table
+outputs: a config-invalid PASS is reported as FAIL instead of leaking the raw
+finding status. Provider scoping must also hold, so a constraint scoped to
+another provider (e.g. Azure) never affects this provider's output (e.g. AWS).
+"""
+
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.check.compliance_models import (
+ AttributeMetadata,
+ ComplianceFramework,
+ OutputsConfig,
+ TableConfig,
+ UniversalComplianceRequirement,
+)
+from prowler.lib.outputs.compliance.universal.universal_output import (
+ UniversalComplianceOutput,
+)
+
+_MODULE = "prowler.providers.common.provider.Provider.get_global_provider"
+
+
+def _make_finding(check_id, status="PASS", provider="aws"):
+ finding = SimpleNamespace()
+ finding.provider = provider
+ finding.account_uid = "123456789012"
+ finding.account_name = "test-account"
+ finding.region = "us-east-1"
+ finding.status = status
+ finding.status_extended = f"{check_id} is {status}"
+ finding.resource_uid = f"arn:aws:iam::123456789012:{check_id}"
+ finding.resource_name = check_id
+ finding.muted = False
+ finding.check_id = check_id
+ finding.metadata = SimpleNamespace(Provider=provider, CheckID=check_id)
+ finding.compliance = {}
+ return finding
+
+
+def _make_framework(constraint, provider="AWS", check_provider="aws"):
+ req = UniversalComplianceRequirement(
+ id="1.1",
+ description="test requirement",
+ attributes={"Section": "IAM"},
+ checks={check_provider: ["check_a"]},
+ config_requirements=[constraint],
+ )
+ return ComplianceFramework(
+ framework="TestFW",
+ name="Test Framework",
+ provider=provider,
+ version="1.0",
+ description="Test framework",
+ requirements=[req],
+ attributes_metadata=[AttributeMetadata(key="Section", type="str")],
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+def _run(framework, audit_config, provider="aws", status="PASS"):
+ findings = [_make_finding("check_a", status, provider)]
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ mock_gp.return_value.type = provider
+ out = UniversalComplianceOutput(
+ findings=findings, framework=framework, provider=provider
+ )
+ return out.data[0].dict()
+
+
+class Test_Universal_CSV_Config_Requirements:
+ _CONSTRAINT = {
+ "Check": "check_a",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45,
+ }
+
+ def test_violating_config_forces_fail(self):
+ fw = _make_framework(self._CONSTRAINT)
+ row = _run(fw, {"max_unused_access_keys_days": 120})
+ assert row["Status"] == "FAIL"
+ assert "Configuration not valid" in row["StatusExtended"]
+
+ def test_valid_config_keeps_pass(self):
+ fw = _make_framework(self._CONSTRAINT)
+ row = _run(fw, {"max_unused_access_keys_days": 30})
+ assert row["Status"] == "PASS"
+ assert "Configuration not valid" not in row["StatusExtended"]
+
+ def test_absent_config_assumes_default_ok(self):
+ fw = _make_framework(self._CONSTRAINT)
+ row = _run(fw, {})
+ assert row["Status"] == "PASS"
+
+
+class Test_Universal_CSV_Provider_Scoping:
+ def test_azure_constraint_does_not_affect_aws_output(self):
+ """An Azure-scoped constraint must not force an AWS output to FAIL."""
+ constraint = {
+ "Check": "check_a",
+ "ConfigKey": "max_unused_access_keys_days",
+ "Operator": "lte",
+ "Value": 45,
+ "Provider": "azure",
+ }
+ fw = _make_framework(constraint)
+ # Even with a config that *would* violate the constraint, the AWS output
+ # must keep PASS because the constraint is scoped to Azure.
+ row = _run(fw, {"max_unused_access_keys_days": 120}, provider="aws")
+ assert row["Status"] == "PASS"
+ assert "Configuration not valid" not in row["StatusExtended"]
diff --git a/tests/lib/outputs/compliance/universal/universal_output_test.py b/tests/lib/outputs/compliance/universal/universal_output_test.py
index 391a9015d7..d0fdf0f178 100644
--- a/tests/lib/outputs/compliance/universal/universal_output_test.py
+++ b/tests/lib/outputs/compliance/universal/universal_output_test.py
@@ -122,6 +122,43 @@ class TestManualRequirements:
assert manual_rows[0].dict()["Requirements_Id"] == "manual-1"
assert manual_rows[0].dict()["ResourceId"] == "manual_check"
+ def test_include_manual_false_skips_manual_rows(self, tmp_path):
+ """``_transform(..., include_manual=False)`` emits finding rows but
+ NOT manual requirements. The streaming caller passes ``False`` for
+ batches 2..N so manual rows are not duplicated across batches."""
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "IAM"},
+ checks={"aws": ["check_a"]},
+ ),
+ UniversalComplianceRequirement(
+ id="manual-1",
+ description="manual check",
+ attributes={"Section": "Governance"},
+ checks={},
+ ),
+ ]
+ metadata = [AttributeMetadata(key="Section", type="str")]
+ fw = _make_framework(reqs, metadata, TableConfig(group_by="Section"))
+ findings = [_make_finding("check_a", "PASS", {"TestFW-1.0": ["1.1"]})]
+
+ output = UniversalComplianceOutput(
+ findings=findings,
+ framework=fw,
+ file_path=str(tmp_path / "t.csv"),
+ )
+ # __init__ transforms with include_manual=True (default) → manual present
+ assert any(r.dict()["Status"] == "MANUAL" for r in output.data)
+
+ # A subsequent batch re-transforms with include_manual=False
+ output._data.clear()
+ output._transform(findings, fw, "TestFW-1.0", include_manual=False)
+
+ assert len(output.data) == 1 # only the finding row, no manual
+ assert all(r.dict()["Status"] != "MANUAL" for r in output.data)
+
class TestMITREExtraColumns:
def test_mitre_columns_present(self, tmp_path):
diff --git a/tests/lib/outputs/compliance/universal/universal_table_config_requirements_test.py b/tests/lib/outputs/compliance/universal/universal_table_config_requirements_test.py
new file mode 100644
index 0000000000..3ac8dc6d8b
--- /dev/null
+++ b/tests/lib/outputs/compliance/universal/universal_table_config_requirements_test.py
@@ -0,0 +1,155 @@
+"""Integration coverage for ConfigRequirements in the console table generators.
+
+The table generators aggregate pass/fail counts, so a requirement whose config
+is too loose must count its (otherwise PASS) finding as FAIL. Driven through the
+universal table renderer, which backs the table output for every framework using
+the shared ``get_effective_status`` helper."""
+
+from types import SimpleNamespace
+from unittest.mock import patch
+
+from prowler.lib.check.compliance_models import (
+ ComplianceFramework,
+ OutputsConfig,
+ TableConfig,
+ UniversalComplianceRequirement,
+)
+from prowler.lib.outputs.compliance.universal.universal_table import get_universal_table
+
+_MODULE = "prowler.providers.common.provider.Provider.get_global_provider"
+_CHECK = "securityhub_enabled"
+
+
+def _finding(status="PASS"):
+ return SimpleNamespace(
+ check_metadata=SimpleNamespace(CheckID=_CHECK), status=status, muted=False
+ )
+
+
+# The overview table is only printed when there is more than one finding, so the
+# tests use two PASS findings (both mapping the constrained check).
+_FINDINGS = [_finding("PASS"), _finding("PASS")]
+
+
+def _framework():
+ req = UniversalComplianceRequirement(
+ id="1.1",
+ description="region check",
+ attributes={"Section": "Monitoring"},
+ checks={"aws": [_CHECK]},
+ config_requirements=[
+ {
+ "Check": _CHECK,
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+ ],
+ )
+ return ComplianceFramework(
+ framework="TestFW",
+ name="Test Framework",
+ provider="AWS",
+ version="1.0",
+ description="Test",
+ requirements=[req],
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+def _render(audit_config, capsys, output_directory):
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = audit_config
+ get_universal_table(
+ findings=_FINDINGS,
+ bulk_checks_metadata={},
+ compliance_framework_name="testfw_1.0_aws",
+ output_filename="out",
+ output_directory=str(output_directory),
+ compliance_overview=False,
+ framework=_framework(),
+ provider="aws",
+ )
+ return capsys.readouterr().out
+
+
+class Test_Universal_Table_Config_Requirements:
+ def test_violating_config_counts_pass_finding_as_fail(self, capsys, tmp_path):
+ out = _render({"mute_non_default_regions": True}, capsys, tmp_path)
+ assert "FAIL(2)" in out
+ assert "PASS(2)" not in out
+
+ def test_valid_config_keeps_pass_count(self, capsys, tmp_path):
+ out = _render({"mute_non_default_regions": False}, capsys, tmp_path)
+ assert "PASS(2)" in out
+ assert "FAIL(2)" not in out
+
+ def test_absent_config_keeps_pass_count(self, capsys, tmp_path):
+ out = _render({}, capsys, tmp_path)
+ assert "PASS(2)" in out
+ assert "FAIL(2)" not in out
+
+
+def _framework_two_requirements():
+ """Same check evidences two requirements; only one carries a guardrail.
+
+ Drives the double-count scenario: with the config violated, the shared
+ finding is FAIL for the constrained requirement and PASS for the other, so
+ its index would land in both pass and fail counts without FAIL precedence.
+ """
+ constrained = UniversalComplianceRequirement(
+ id="1.1",
+ description="region check",
+ attributes={"Section": "Monitoring"},
+ checks={"aws": [_CHECK]},
+ config_requirements=[
+ {
+ "Check": _CHECK,
+ "Provider": "aws",
+ "ConfigKey": "mute_non_default_regions",
+ "Operator": "eq",
+ "Value": False,
+ }
+ ],
+ )
+ unconstrained = UniversalComplianceRequirement(
+ id="2.1",
+ description="other check",
+ attributes={"Section": "Logging"},
+ checks={"aws": [_CHECK]},
+ )
+ return ComplianceFramework(
+ framework="TestFW",
+ name="Test Framework",
+ provider="AWS",
+ version="1.0",
+ description="Test",
+ requirements=[constrained, unconstrained],
+ outputs=OutputsConfig(table_config=TableConfig(group_by="Section")),
+ )
+
+
+class Test_Universal_Table_Multi_Requirement_Dedup:
+ def test_finding_in_two_requirements_counted_once_with_fail_precedence(
+ self, capsys, tmp_path
+ ):
+ # mute=True violates the constrained requirement → each shared PASS
+ # finding must be counted once as FAIL in the overview, not double
+ # counted as both PASS and FAIL across the two requirements it maps.
+ with patch(_MODULE) as mock_gp:
+ mock_gp.return_value.audit_config = {"mute_non_default_regions": True}
+ mock_gp.return_value.type = "aws"
+ get_universal_table(
+ findings=_FINDINGS,
+ bulk_checks_metadata={},
+ compliance_framework_name="testfw_1.0_aws",
+ output_filename="out",
+ output_directory=str(tmp_path),
+ compliance_overview=True,
+ framework=_framework_two_requirements(),
+ provider="aws",
+ )
+ out = capsys.readouterr().out
+ # Two findings, each counted once as FAIL → 100% FAIL, 0 PASS.
+ assert "(2) FAIL" in out
+ assert "(0) PASS" in out
diff --git a/tests/lib/outputs/compliance/universal/universal_table_test.py b/tests/lib/outputs/compliance/universal/universal_table_test.py
index 7598c43c8b..abe3d0c3d0 100644
--- a/tests/lib/outputs/compliance/universal/universal_table_test.py
+++ b/tests/lib/outputs/compliance/universal/universal_table_test.py
@@ -1,3 +1,4 @@
+import re
from types import SimpleNamespace
from unittest.mock import MagicMock
@@ -26,6 +27,10 @@ def _make_finding(check_id, status="PASS", muted=False):
return finding
+def _strip_ansi(text):
+ return re.sub(r"\x1b\[[0-9;]*m", "", text)
+
+
def _make_framework(requirements, table_config, provider="AWS"):
return ComplianceFramework(
framework="TestFW",
@@ -39,6 +44,8 @@ def _make_framework(requirements, table_config, provider="AWS"):
class TestBuildRequirementCheckMap:
+ """Test cases for building the requirement-to-check map of a framework."""
+
def test_basic(self):
reqs = [
UniversalComplianceRequirement(
@@ -103,6 +110,8 @@ class TestBuildRequirementCheckMap:
class TestGetGroupKey:
+ """Test cases for resolving the group key of a requirement."""
+
def test_normal_field(self):
req = UniversalComplianceRequirement(
id="1.1",
@@ -124,7 +133,9 @@ class TestGetGroupKey:
class TestGroupedMode:
- def test_grouped_rendering(self, capsys):
+ """Test cases for grouped-mode universal compliance table rendering."""
+
+ def test_grouped_rendering(self, capsys, tmp_path):
reqs = [
UniversalComplianceRequirement(
id="1.1",
@@ -156,7 +167,7 @@ class TestGroupedMode:
bulk_metadata,
"test_fw",
"output",
- "/tmp",
+ str(tmp_path),
False,
framework=fw,
)
@@ -167,9 +178,118 @@ class TestGroupedMode:
assert "PASS" in captured.out
assert "FAIL" in captured.out
+ def test_grouped_multi_section_no_undercount(self, capsys, tmp_path):
+ """A single check mapped to several sections must be counted in
+ every section it belongs to, not only the first one seen."""
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "IAM"},
+ checks={"aws": ["check_a", "check_b"]},
+ ),
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="test2",
+ attributes={"Section": "Logging"},
+ checks={"aws": ["check_a"]},
+ ),
+ ]
+ tc = TableConfig(group_by="Section")
+ fw = _make_framework(reqs, tc)
+
+ # check_a (FAIL) belongs to both IAM and Logging sections; check_b
+ # (PASS, IAM only) is added so the overview total reaches 2 and the
+ # results table is rendered.
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+ bulk_metadata = {
+ "check_a": MagicMock(Compliance=[]),
+ "check_b": MagicMock(Compliance=[]),
+ }
+
+ get_universal_table(
+ findings,
+ bulk_metadata,
+ "test_fw",
+ "output",
+ str(tmp_path),
+ False,
+ framework=fw,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # Both the IAM and Logging rows must report FAIL(1). Before the fix the
+ # second section seen (Logging) was undercounted to FAIL(0) and rendered
+ # as PASS. Anchor each occurrence to its own table row so an unrelated
+ # "FAIL(1)" elsewhere cannot mask an undercount.
+ iam_row = [
+ line for line in plain.splitlines() if "IAM" in line and "FAIL(1)" in line
+ ]
+ logging_row = [
+ line
+ for line in plain.splitlines()
+ if "Logging" in line and "FAIL(1)" in line
+ ]
+ assert len(iam_row) == 1
+ assert len(logging_row) == 1
+
+ def test_grouped_multi_section_muted_not_undercounted(self, capsys, tmp_path):
+ """A single MUTED finding mapped to several groups must be counted in
+ the per-group Muted column of every group it belongs to."""
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "IAM"},
+ checks={"aws": ["check_a", "check_b"]},
+ ),
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="test2",
+ attributes={"Section": "Logging"},
+ checks={"aws": ["check_a"]},
+ ),
+ ]
+ tc = TableConfig(group_by="Section")
+ fw = _make_framework(reqs, tc)
+
+ # check_a is MUTED and belongs to both IAM and Logging; check_b is a
+ # plain FAIL so the overview total reaches 2 and the table is rendered.
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ _make_finding("check_b", "FAIL"),
+ ]
+ bulk_metadata = {
+ "check_a": MagicMock(Compliance=[]),
+ "check_b": MagicMock(Compliance=[]),
+ }
+
+ get_universal_table(
+ findings,
+ bulk_metadata,
+ "test_fw",
+ "output",
+ str(tmp_path),
+ False,
+ framework=fw,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # The muted finding belongs to both sections, so both the IAM row and
+ # the Logging row must carry a Muted count of 1 in their last cell.
+ muted_one_rows = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_one_rows) == 2
+
class TestSplitMode:
- def test_split_rendering(self, capsys):
+ """Test cases for split-mode universal compliance table rendering."""
+
+ def test_split_rendering(self, capsys, tmp_path):
reqs = [
UniversalComplianceRequirement(
id="1.1",
@@ -204,7 +324,7 @@ class TestSplitMode:
bulk_metadata,
"test_fw",
"output",
- "/tmp",
+ str(tmp_path),
False,
framework=fw,
)
@@ -214,9 +334,119 @@ class TestSplitMode:
assert "Level 1" in captured.out
assert "Level 2" in captured.out
+ def test_split_muted_multi_section_not_undercounted(self, capsys, tmp_path):
+ """In split mode a single MUTED finding mapped to several groups must
+ be counted in the Muted column of every group it belongs to."""
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "Storage", "Profile": "Level 1"},
+ checks={"aws": ["check_a", "check_b"]},
+ ),
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="test2",
+ attributes={"Section": "Logging", "Profile": "Level 1"},
+ checks={"aws": ["check_a"]},
+ ),
+ ]
+ tc = TableConfig(
+ group_by="Section",
+ split_by=SplitByConfig(field="Profile", values=["Level 1", "Level 2"]),
+ )
+ fw = _make_framework(reqs, tc)
+
+ # check_a is MUTED and belongs to both Storage and Logging; check_b is a
+ # plain FAIL so the table is rendered.
+ findings = [
+ _make_finding("check_a", "FAIL", muted=True),
+ _make_finding("check_b", "FAIL"),
+ ]
+ bulk_metadata = {
+ "check_a": MagicMock(Compliance=[]),
+ "check_b": MagicMock(Compliance=[]),
+ }
+
+ get_universal_table(
+ findings,
+ bulk_metadata,
+ "test_fw",
+ "output",
+ str(tmp_path),
+ False,
+ framework=fw,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # Both section rows must carry a Muted count of 1 (last cell). Before the
+ # fix only the first group seen incremented Muted, leaving the other 0.
+ muted_one_rows = re.findall(r"│\s*1\s*│\s*$", plain, flags=re.MULTILINE)
+ assert len(muted_one_rows) == 2
+
+ def test_split_same_group_value_not_double_counted(self, capsys, tmp_path):
+ """A single finding whose check maps to several requirements that share
+ the same group and split value must count once for that group/split,
+ not once per requirement (FAIL(1), never FAIL(2))."""
+ reqs = [
+ # check_a appears in two requirements, both Storage / Level 1.
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "Storage", "Profile": "Level 1"},
+ checks={"aws": ["check_a"]},
+ ),
+ UniversalComplianceRequirement(
+ id="1.2",
+ description="test2",
+ attributes={"Section": "Storage", "Profile": "Level 1"},
+ checks={"aws": ["check_a"]},
+ ),
+ # A second group so the table renders with more than one finding.
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="test3",
+ attributes={"Section": "Logging", "Profile": "Level 1"},
+ checks={"aws": ["check_b"]},
+ ),
+ ]
+ tc = TableConfig(
+ group_by="Section",
+ split_by=SplitByConfig(field="Profile", values=["Level 1", "Level 2"]),
+ )
+ fw = _make_framework(reqs, tc)
+
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+ bulk_metadata = {
+ "check_a": MagicMock(Compliance=[]),
+ "check_b": MagicMock(Compliance=[]),
+ }
+
+ get_universal_table(
+ findings,
+ bulk_metadata,
+ "test_fw",
+ "output",
+ str(tmp_path),
+ False,
+ framework=fw,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ # The Storage row must show FAIL(1) for Level 1, never FAIL(2).
+ assert "FAIL(1)" in plain
+ assert "FAIL(2)" not in plain
+
class TestScoredMode:
- def test_scored_rendering(self, capsys):
+ """Test cases for scored-mode universal compliance table rendering."""
+
+ def test_scored_rendering(self, capsys, tmp_path):
reqs = [
UniversalComplianceRequirement(
id="1.1",
@@ -251,7 +481,7 @@ class TestScoredMode:
bulk_metadata,
"test_fw",
"output",
- "/tmp",
+ str(tmp_path),
False,
framework=fw,
)
@@ -261,9 +491,68 @@ class TestScoredMode:
assert "Score" in captured.out
assert "Threat Score" in captured.out
+ def test_scored_multi_section_fail_not_undercounted(self, capsys, tmp_path):
+ """In scored mode a single FAIL finding mapped to several groups must
+ show FAIL(1) in every group it belongs to, not only the first one."""
+ reqs = [
+ UniversalComplianceRequirement(
+ id="1.1",
+ description="test",
+ attributes={"Section": "IAM", "LevelOfRisk": 5, "Weight": 100},
+ checks={"aws": ["check_a", "check_b"]},
+ ),
+ UniversalComplianceRequirement(
+ id="2.1",
+ description="test2",
+ attributes={"Section": "Logging", "LevelOfRisk": 3, "Weight": 50},
+ checks={"aws": ["check_a"]},
+ ),
+ ]
+ tc = TableConfig(
+ group_by="Section",
+ scoring=ScoringConfig(risk_field="LevelOfRisk", weight_field="Weight"),
+ )
+ fw = _make_framework(reqs, tc)
+
+ # check_a (FAIL) belongs to both IAM and Logging; check_b (PASS, IAM
+ # only) raises the overview total to 2 so the table is rendered.
+ findings = [
+ _make_finding("check_a", "FAIL"),
+ _make_finding("check_b", "PASS"),
+ ]
+ bulk_metadata = {
+ "check_a": MagicMock(Compliance=[]),
+ "check_b": MagicMock(Compliance=[]),
+ }
+
+ get_universal_table(
+ findings,
+ bulk_metadata,
+ "test_fw",
+ "output",
+ str(tmp_path),
+ False,
+ framework=fw,
+ )
+
+ captured = capsys.readouterr()
+ plain = _strip_ansi(captured.out)
+ iam_row = [
+ line for line in plain.splitlines() if "IAM" in line and "FAIL(1)" in line
+ ]
+ logging_row = [
+ line
+ for line in plain.splitlines()
+ if "Logging" in line and "FAIL(1)" in line
+ ]
+ assert len(iam_row) == 1
+ assert len(logging_row) == 1
+
class TestCustomLabels:
- def test_ens_spanish_labels(self, capsys):
+ """Test cases for custom-label universal compliance table rendering."""
+
+ def test_ens_spanish_labels(self, capsys, tmp_path):
reqs = [
UniversalComplianceRequirement(
id="1.1",
@@ -300,7 +589,7 @@ class TestCustomLabels:
bulk_metadata,
"test_fw",
"output",
- "/tmp",
+ str(tmp_path),
False,
framework=fw,
)
@@ -311,7 +600,9 @@ class TestCustomLabels:
class TestMultiProviderDictChecks:
- def test_only_aws_checks_matched(self, capsys):
+ """Test cases for multi-provider dict checks in the universal table."""
+
+ def test_only_aws_checks_matched(self, capsys, tmp_path):
"""With dict checks and provider='aws', only AWS checks match findings."""
reqs = [
UniversalComplianceRequirement(
@@ -352,7 +643,7 @@ class TestMultiProviderDictChecks:
bulk_metadata,
"multi_cloud",
"output",
- "/tmp",
+ str(tmp_path),
False,
framework=fw,
provider="aws",
@@ -366,7 +657,9 @@ class TestMultiProviderDictChecks:
class TestNoTableConfig:
- def test_returns_early_without_table_config(self, capsys):
+ """Test cases for the universal table when no table config is present."""
+
+ def test_returns_early_without_table_config(self, capsys, tmp_path):
fw = ComplianceFramework(
framework="TestFW",
name="Test",
@@ -374,11 +667,11 @@ class TestNoTableConfig:
description="Test",
requirements=[],
)
- get_universal_table([], {}, "test", "out", "/tmp", False, framework=fw)
+ get_universal_table([], {}, "test", "out", str(tmp_path), False, framework=fw)
captured = capsys.readouterr()
assert captured.out == ""
- def test_returns_early_without_framework(self, capsys):
- get_universal_table([], {}, "test", "out", "/tmp", False, framework=None)
+ def test_returns_early_without_framework(self, capsys, tmp_path):
+ get_universal_table([], {}, "test", "out", str(tmp_path), False, framework=None)
captured = capsys.readouterr()
assert captured.out == ""
diff --git a/tests/lib/outputs/finding_test.py b/tests/lib/outputs/finding_test.py
index fb75a1f705..1315970201 100644
--- a/tests/lib/outputs/finding_test.py
+++ b/tests/lib/outputs/finding_test.py
@@ -761,6 +761,87 @@ class TestFinding:
assert finding_output.metadata.Severity == Severity.high
assert finding_output.metadata.ResourceType == "mock_resource_type"
+ def _build_linode_check_output(self):
+ check_output = MagicMock()
+ check_output.resource_id = "12345"
+ check_output.resource_name = "test-instance"
+ check_output.resource_details = ""
+ check_output.resource_tags = {}
+ check_output.region = "us-east"
+ check_output.status = Status.PASS
+ check_output.status_extended = "Instance is compliant"
+ check_output.muted = False
+ check_output.check_metadata = mock_check_metadata(provider="linode")
+ check_output.resource = {}
+ check_output.compliance = {}
+ return check_output
+
+ def test_generate_output_linode(self):
+ """Test Linode output generation when the account ID is available."""
+ from prowler.providers.linode.models import LinodeIdentityInfo
+
+ provider = MagicMock()
+ provider.type = "linode"
+ provider.identity = LinodeIdentityInfo(
+ username="admin",
+ email="admin@example.com",
+ account_id="E1AF1B6C-1111-2222-3333-444455556666",
+ )
+
+ check_output = self._build_linode_check_output()
+ output_options = MagicMock()
+ output_options.unix_timestamp = False
+
+ finding_output = Finding.generate_output(provider, check_output, output_options)
+
+ assert finding_output.provider == "linode"
+ assert finding_output.auth_method == "api_token"
+ assert finding_output.account_uid == "E1AF1B6C-1111-2222-3333-444455556666"
+ assert finding_output.account_name == "admin"
+
+ def test_generate_output_linode_without_account_id_falls_back_to_username(self):
+ """account_uid is required; when account_id is None it must fall back to
+ the username so findings are never silently dropped."""
+ from prowler.providers.linode.models import LinodeIdentityInfo
+
+ provider = MagicMock()
+ provider.type = "linode"
+ provider.identity = LinodeIdentityInfo(
+ username="admin",
+ email="admin@example.com",
+ account_id=None,
+ )
+
+ check_output = self._build_linode_check_output()
+ output_options = MagicMock()
+ output_options.unix_timestamp = False
+
+ finding_output = Finding.generate_output(provider, check_output, output_options)
+
+ # Must not raise a ValidationError and must use the username fallback
+ assert finding_output.account_uid == "admin"
+
+ def test_generate_output_linode_without_account_id_or_username(self):
+ """When neither account_id nor username/email is available, account_uid
+ falls back to the literal provider name."""
+ from prowler.providers.linode.models import LinodeIdentityInfo
+
+ provider = MagicMock()
+ provider.type = "linode"
+ provider.identity = LinodeIdentityInfo(
+ username=None,
+ email=None,
+ account_id=None,
+ )
+
+ check_output = self._build_linode_check_output()
+ output_options = MagicMock()
+ output_options.unix_timestamp = False
+
+ finding_output = Finding.generate_output(provider, check_output, output_options)
+
+ assert finding_output.account_uid == "linode"
+
def test_generate_output_iac_remote(self):
# Mock provider
provider = MagicMock()
@@ -1507,3 +1588,140 @@ class TestFinding:
with pytest.raises(KeyError):
Finding.transform_api_finding(dummy_finding, provider)
+
+ @patch(
+ "prowler.lib.outputs.finding.get_check_compliance",
+ new=mock_get_check_compliance,
+ )
+ def test_generate_output_stackit(self):
+ provider = MagicMock()
+ provider.type = "stackit"
+ provider.auth_method = "service_account_key"
+ provider.identity.project_id = "test-project-id"
+ provider.identity.project_name = "test-project-name"
+
+ check_output = MagicMock()
+ check_output.resource_id = "test_resource_id"
+ check_output.resource_name = "test_resource_name"
+ check_output.resource_details = ""
+ check_output.location = "eu01"
+ check_output.status = Status.PASS
+ check_output.status_extended = "mock_status_extended"
+ check_output.muted = False
+ check_output.check_metadata = mock_check_metadata(provider="stackit")
+ check_output.resource = {}
+ check_output.compliance = {}
+
+ output_options = MagicMock()
+ output_options.unix_timestamp = True
+
+ finding_output = Finding.generate_output(provider, check_output, output_options)
+
+ assert isinstance(finding_output, Finding)
+ assert finding_output.auth_method == "service_account_key"
+ assert finding_output.account_uid == "test-project-id"
+ assert finding_output.account_name == "test-project-name"
+ assert finding_output.resource_name == "test_resource_name"
+ assert finding_output.resource_uid == "test_resource_id"
+ assert finding_output.region == "eu01"
+ assert finding_output.status == Status.PASS
+ assert finding_output.muted is False
+
+ @patch(
+ "prowler.lib.outputs.finding.get_check_compliance",
+ new=mock_get_check_compliance,
+ )
+ def test_generate_output_e2enetworks(self):
+ provider = MagicMock()
+ provider.type = "e2enetworks"
+ provider.identity.project_id = 12345
+
+ check_output = MagicMock()
+ check_output.resource_id = "test_resource_id"
+ check_output.resource_name = "test_resource_name"
+ check_output.resource_details = ""
+ check_output.location = "Delhi"
+ check_output.status = Status.PASS
+ check_output.status_extended = "mock_status_extended"
+ check_output.muted = False
+ check_output.check_metadata = mock_check_metadata(provider="e2enetworks")
+ check_output.resource = {}
+ check_output.compliance = {}
+
+ output_options = MagicMock()
+ output_options.unix_timestamp = True
+
+ finding_output = Finding.generate_output(provider, check_output, output_options)
+
+ assert isinstance(finding_output, Finding)
+ assert finding_output.auth_method == "api_key_and_bearer_token"
+ assert finding_output.account_uid == "12345"
+ assert finding_output.account_name == "12345"
+ assert finding_output.resource_name == "test_resource_name"
+ assert finding_output.resource_uid == "test_resource_id"
+ assert finding_output.region == "Delhi"
+
+ def test_transform_api_finding_stackit(self):
+ provider = MagicMock()
+ provider.type = "stackit"
+ provider.auth_method = "service_account_key"
+ provider.identity.project_id = "stackit-project-id"
+ provider.identity.project_name = "stackit-project-name"
+ dummy_finding = DummyAPIFinding()
+ dummy_finding.inserted_at = 1234567890
+ dummy_finding.scan = DummyScan(provider=provider)
+ dummy_finding.uid = "finding-uid-stackit"
+ dummy_finding.status = "PASS"
+ dummy_finding.status_extended = "StackIT check extended"
+ check_metadata = {
+ "provider": "stackit",
+ "checkid": "service_stackit_check_001",
+ "checktitle": "Test StackIT Check",
+ "checktype": [],
+ "servicename": "service",
+ "subservicename": "",
+ "severity": "high",
+ "resourcetype": "StackITResourceType",
+ "description": "StackIT check description",
+ "risk": "High risk",
+ "relatedurl": "",
+ "remediation": {
+ "code": {
+ "nativeiac": "",
+ "terraform": "",
+ "cli": "",
+ "other": "",
+ },
+ "recommendation": {
+ "text": "Fix it",
+ "url": "https://hub.prowler.com/check/service_stackit_check_001",
+ },
+ },
+ "resourceidtemplate": "template",
+ "categories": ["encryption"],
+ "dependson": [],
+ "relatedto": [],
+ "notes": "StackIT notes",
+ }
+ dummy_finding.check_metadata = check_metadata
+ dummy_finding.raw_result = {}
+ dummy_finding.resource_name = "stackit-resource-name"
+ dummy_finding.resource_id = "stackit-resource-uid"
+ dummy_finding.location = "eu01"
+ dummy_finding.project_id = "stackit-project-id"
+ resource = DummyResource(
+ uid="stackit-resource-uid",
+ name="stackit-resource-name",
+ resource_arn="",
+ region="eu01",
+ tags=[],
+ )
+ dummy_finding.resources = DummyResources(resource)
+ dummy_finding.muted = False
+ finding_obj = Finding.transform_api_finding(dummy_finding, provider)
+ assert finding_obj.auth_method == "service_account_key"
+ assert finding_obj.account_uid == "stackit-project-id"
+ assert finding_obj.account_name == "stackit-project-name"
+ assert finding_obj.resource_name == "stackit-resource-name"
+ assert finding_obj.resource_uid == "stackit-resource-uid"
+ assert finding_obj.region == "eu01"
diff --git a/tests/lib/outputs/html/html_test.py b/tests/lib/outputs/html/html_test.py
index c8d4ac199d..3eccc8ba8d 100644
--- a/tests/lib/outputs/html/html_test.py
+++ b/tests/lib/outputs/html/html_test.py
@@ -962,6 +962,75 @@ class TestHTML:
assert summary == image_list_html_assessment_summary
+ def test_stackit_get_assessment_summary(self):
+ """Test StackIT HTML assessment summary shows the project ID."""
+ findings = [generate_finding_output()]
+ output = HTML(findings)
+
+ provider = MagicMock()
+ provider.type = "stackit"
+ provider.identity.project_id = "f033ea6d-8697-40eb-a60e-acfa9128480d"
+ provider.identity.project_name = "ProwlerDev"
+ provider.identity.audited_regions = {"eu01", "eu02"}
+
+ summary = output.get_assessment_summary(provider)
+
+ assert "StackIT Assessment Summary" in summary
+ assert "StackIT Credentials" in summary
+ assert "<b>Project ID:</b> f033ea6d-8697-40eb-a60e-acfa9128480d" in summary
+ assert "<b>Project Name:</b> ProwlerDev" in summary
+ assert "<b>Regions:</b> eu01, eu02" in summary
+ assert "<b>Authentication Type:</b> Service Account Key" in summary
+
+ def test_stackit_get_assessment_summary_without_project_name(self):
+ """Project ID is always shown; the Project Name line is omitted when
+ the service account cannot read it from Resource Manager."""
+ findings = [generate_finding_output()]
+ output = HTML(findings)
+
+ provider = MagicMock()
+ provider.type = "stackit"
+ provider.identity.project_id = "f033ea6d-8697-40eb-a60e-acfa9128480d"
+ provider.identity.project_name = ""
+ provider.identity.audited_regions = {"eu01"}
+
+ summary = output.get_assessment_summary(provider)
+
+ assert "<b>Project ID:</b> f033ea6d-8697-40eb-a60e-acfa9128480d" in summary
+ assert "<b>Project Name:</b>" not in summary
+
+ def test_e2enetworks_get_assessment_summary(self):
+ """Test E2E Networks HTML assessment summary shows project and locations."""
+ findings = [generate_finding_output()]
+ output = HTML(findings)
+
+ provider = MagicMock()
+ provider.type = "e2enetworks"
+ provider.identity.project_id = 12345
+ provider.identity.locations = ["Delhi", "Chennai"]
+
+ summary = output.get_assessment_summary(provider)
+
+ assert "E2E Networks Assessment Summary" in summary
+ assert "<b>Project ID:</b> 12345" in summary
+ assert "<b>Locations:</b> Delhi, Chennai" in summary
+ assert "API Key + Bearer Token" in summary
+
+ def test_e2enetworks_get_assessment_summary_escapes_locations(self):
+ """Test E2E Networks HTML assessment summary escapes user-controlled locations."""
+ findings = [generate_finding_output()]
+ output = HTML(findings)
+
+ provider = MagicMock()
+ provider.type = "e2enetworks"
+ provider.identity.project_id = 12345
+ provider.identity.locations = ['Delhi"><script>alert(1)</script>']
+
+ summary = output.get_assessment_summary(provider)
+
+ assert "<script>alert(1)</script>" not in summary
+ assert "Delhi"><script>alert(1)</script>" in summary
+
def test_process_markdown_bold_text(self):
"""Test that **text** is converted to <strong>text</strong>"""
test_text = "This is **bold text** and this is **also bold**"
diff --git a/tests/lib/outputs/jira/jira_test.py b/tests/lib/outputs/jira/jira_test.py
index 03656891c8..f38c1ba376 100644
--- a/tests/lib/outputs/jira/jira_test.py
+++ b/tests/lib/outputs/jira/jira_test.py
@@ -16,8 +16,11 @@ from prowler.lib.outputs.jira.exceptions.exceptions import (
JiraGetProjectsError,
JiraGetProjectsResponseError,
JiraNoProjectsError,
+ JiraNoTokenError,
JiraRefreshTokenError,
+ JiraRefreshTokenResponseError,
JiraRequiredCustomFieldsError,
+ JiraSendFindingsResponseError,
JiraTestConnectionError,
)
from prowler.lib.outputs.jira.jira import Jira
@@ -53,7 +56,7 @@ class TestJiraIntegration:
self.user_mail = "test_user_mail"
self.api_token = "test_api_token"
- self.domain = "test_domain"
+ self.domain = "test-domain"
self.jira_integration_basic_auth = Jira(
user_mail=self.user_mail,
@@ -95,6 +98,41 @@ class TestJiraIntegration:
return found
return None
+ @staticmethod
+ def _find_link_mark_by_href(nodes: List[dict], href: str) -> Optional[dict]:
+ for node in nodes:
+ if node.get("type") == "text":
+ for mark in node.get("marks", []):
+ if (
+ mark.get("type") == "link"
+ and mark.get("attrs", {}).get("href") == href
+ ):
+ return mark
+ found = TestJiraIntegration._find_link_mark_by_href(
+ node.get("content", []), href
+ )
+ if found:
+ return found
+ return None
+
+ @staticmethod
+ def _collect_link_texts_by_href(nodes: List[dict], href: str) -> List[str]:
+ link_texts: List[str] = []
+
+ for node in nodes:
+ if node.get("type") == "text" and any(
+ mark.get("type") == "link" and mark.get("attrs", {}).get("href") == href
+ for mark in node.get("marks", [])
+ ):
+ link_texts.append(node.get("text", ""))
+ link_texts.extend(
+ TestJiraIntegration._collect_link_texts_by_href(
+ node.get("content", []), href
+ )
+ )
+
+ return link_texts
+
@staticmethod
def _find_table_row(rows: List[dict], header: str) -> dict:
for row in rows:
@@ -339,6 +377,117 @@ class TestJiraIntegration:
with pytest.raises(JiraRefreshTokenError):
self.jira_integration.refresh_access_token()
+ @patch("prowler.lib.outputs.jira.jira.requests.post")
+ @patch.object(Jira, "get_cloud_id", return_value="test_cloud_id")
+ def test_get_auth_sends_timeout(self, mock_get_cloud_id, mock_post):
+ """get_auth must pass a request timeout to avoid hanging on an unresponsive Jira."""
+ # To disable vulture
+ mock_get_cloud_id = mock_get_cloud_id
+
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = {
+ "access_token": "test_access_token",
+ "refresh_token": "test_refresh_token",
+ "expires_in": 3600,
+ }
+ mock_post.return_value = mock_response
+
+ self.jira_integration.get_auth("test_auth_code")
+
+ assert mock_post.call_args.kwargs["timeout"] == Jira.REQUEST_TIMEOUT
+
+ @patch("prowler.lib.outputs.jira.jira.requests.get")
+ def test_get_cloud_id_sends_timeout(self, mock_get):
+ """get_cloud_id (OAuth path) must pass a request timeout."""
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = [{"id": "test_cloud_id"}]
+ mock_get.return_value = mock_response
+
+ self.jira_integration.get_cloud_id("test_access_token")
+
+ assert mock_get.call_args.kwargs["timeout"] == Jira.REQUEST_TIMEOUT
+
+ @patch("prowler.lib.outputs.jira.jira.requests.get")
+ def test_get_cloud_id_basic_auth_sends_timeout(self, mock_get):
+ """get_cloud_id (basic-auth tenant_info path) must pass a request timeout."""
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = {"cloudId": "test_cloud_id"}
+ mock_get.return_value = mock_response
+
+ self.jira_integration_basic_auth.get_cloud_id(domain=self.domain)
+
+ assert mock_get.call_args.kwargs["timeout"] == Jira.REQUEST_TIMEOUT
+
+ @pytest.mark.parametrize(
+ "domain",
+ (
+ "169.254.169.254#",
+ "internal/service",
+ "internal?target",
+ "internal\\target",
+ "internal:8000",
+ "user@internal",
+ ),
+ )
+ @patch("prowler.lib.outputs.jira.jira.requests.get")
+ def test_get_cloud_id_basic_auth_rejects_invalid_domain(self, mock_get, domain):
+ with pytest.raises(JiraGetCloudIDError):
+ self.jira_integration_basic_auth.get_cloud_id(domain=domain)
+
+ mock_get.assert_not_called()
+
+ @patch("prowler.lib.outputs.jira.jira.requests.get")
+ def test_get_cloud_id_basic_auth_disables_redirects(self, mock_get):
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = {"cloudId": "test_cloud_id"}
+ mock_get.return_value = mock_response
+
+ self.jira_integration_basic_auth.get_cloud_id(domain=self.domain)
+
+ assert mock_get.call_args.kwargs["allow_redirects"] is False
+
+ @patch("prowler.lib.outputs.jira.jira.requests.post")
+ def test_refresh_access_token_sends_timeout(self, mock_post):
+ """refresh_access_token must pass a request timeout."""
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = {
+ "access_token": "new_access_token",
+ "refresh_token": "new_refresh_token",
+ "expires_in": 3600,
+ }
+ mock_post.return_value = mock_response
+
+ self.jira_integration.refresh_access_token()
+
+ assert mock_post.call_args.kwargs["timeout"] == Jira.REQUEST_TIMEOUT
+
+ @patch.object(Jira, "get_access_token", return_value="valid_access_token")
+ @patch.object(
+ Jira, "cloud_id", new_callable=PropertyMock, return_value="test_cloud_id"
+ )
+ @patch("prowler.lib.outputs.jira.jira.requests.get")
+ def test_get_projects_sends_timeout(
+ self, mock_get, mock_cloud_id, mock_get_access_token
+ ):
+ """get_projects must pass a request timeout."""
+ # To disable vulture
+ mock_cloud_id = mock_cloud_id
+ mock_get_access_token = mock_get_access_token
+
+ mock_response = MagicMock()
+ mock_response.status_code = 200
+ mock_response.json.return_value = [{"key": "PROJ1", "name": "Project One"}]
+ mock_get.return_value = mock_response
+
+ self.jira_integration.get_projects()
+
+ assert mock_get.call_args.kwargs["timeout"] == Jira.REQUEST_TIMEOUT
+
@patch.object(Jira, "get_auth", return_value=None)
@patch.object(
Jira,
@@ -804,6 +953,12 @@ class TestJiraIntegration:
intro_text = intro_paragraph["content"][0]
assert intro_text["type"] == "text"
assert intro_text["text"] == "Prowler has discovered the following finding:"
+ assert all(
+ self._collect_text_from_cell({"content": node.get("content", [])})
+ != "Summary"
+ for node in description_content
+ if node.get("type") == "heading"
+ )
table = description_content[1]
assert table["type"] == "table"
@@ -1004,6 +1159,301 @@ class TestJiraIntegration:
for mark in node.get("marks", [])
)
+ @staticmethod
+ def _find_empty_text_nodes(node) -> List[str]:
+ # ADF forbids empty text nodes; collect any to assert the document is valid.
+ empties: List[str] = []
+
+ def walk(current) -> None:
+ if isinstance(current, dict):
+ if current.get("type") == "text" and current.get("text", "") == "":
+ empties.append(current.get("text", ""))
+ for value in current.values():
+ walk(value)
+ elif isinstance(current, list):
+ for item in current:
+ walk(item)
+
+ walk(node)
+ return empties
+
+ def test_get_adf_description_empty_resource_name_has_no_empty_text_nodes(self):
+ # A resource without a name (e.g. an AWS-managed IAM policy) used to emit an
+ # empty ADF text node, making Jira reject the issue with 400 INVALID_INPUT.
+ adf_description = self.jira_integration.get_adf_description(
+ check_id="CHECK-1",
+ check_title="Sample check",
+ severity="CRITICAL",
+ severity_color="#FF0000",
+ status="FAIL",
+ status_color="#FF0000",
+ status_extended="Some status",
+ provider="aws",
+ region="eu-west-1",
+ resource_uid="arn:aws:iam::aws:policy/AdministratorAccess",
+ resource_name="",
+ recommendation_text="",
+ )
+
+ assert self._find_empty_text_nodes(adf_description) == []
+
+ table = adf_description["content"][1]
+ resource_name_row = self._find_table_row(table["content"], "Resource Name")
+ value_cell = resource_name_row["content"][1]
+ assert self._collect_text_from_cell(value_cell) == "-"
+
+ @pytest.mark.parametrize(
+ "field, header",
+ [
+ ("check_id", "Check Id"),
+ ("check_title", "Check Title"),
+ ("status_extended", "Status Extended"),
+ ("provider", "Provider"),
+ ("region", "Region"),
+ ("resource_uid", "Resource UID"),
+ ("resource_name", "Resource Name"),
+ ],
+ )
+ def test_get_adf_description_empty_plain_text_fields_render_placeholder(
+ self, field, header
+ ):
+ base_kwargs = dict(
+ check_id="CHECK-1",
+ check_title="Sample check",
+ severity="HIGH",
+ severity_color="#FF0000",
+ status="FAIL",
+ status_color="#00FF00",
+ status_extended="Some status",
+ provider="aws",
+ region="us-east-1",
+ resource_uid="resource-1",
+ resource_name="resource-name",
+ recommendation_text="",
+ )
+ base_kwargs[field] = ""
+
+ adf_description = self.jira_integration.get_adf_description(**base_kwargs)
+
+ assert self._find_empty_text_nodes(adf_description) == []
+
+ table = adf_description["content"][1]
+ row = self._find_table_row(table["content"], header)
+ value_cell = row["content"][1]
+ assert self._collect_text_from_cell(value_cell) == "-"
+
+ def test_get_grouped_adf_description_uses_capped_finding_group_link_copy(self):
+ finding_group_url = (
+ "https://security.example.com/findings?"
+ "filter%5Bcheck_id%5D=admincenter_users_admins_reduced_license_footprint&"
+ "expandedCheckId=admincenter_users_admins_reduced_license_footprint"
+ )
+ finding_group_link_text = "View the remaining grouped findings."
+ recommendation_url = (
+ "https://hub.prowler.com/check/"
+ "admincenter_users_admins_reduced_license_footprint"
+ )
+ adf_description = self.jira_integration.get_grouped_adf_description(
+ check_id="admincenter_users_admins_reduced_license_footprint",
+ check_title="Administrative user has no license or an allowed license",
+ check_description="Administrative users are assigned productivity licenses.",
+ severity="HIGH",
+ status="FAIL",
+ provider="m365",
+ service="exchange",
+ affected_failing_resources=123,
+ last_seen="Jul 09, 2026 11:38AM UTC",
+ failing_for="< 1 day",
+ grouped_resources=[
+ {
+ "resource_name": "rich@prowler.com",
+ "resource_uid": "3f9a216b-b66b-4d5d-a812-2ad538732cfb",
+ "provider": "m365",
+ "service": "exchange",
+ "provider_account": "ProwlerPro.onmicrosoft.com",
+ "status": "FAIL",
+ "severity": "high",
+ "region": "global",
+ "last_seen": "Jul 09, 2026 11:38AM UTC",
+ "failing_for": "< 1 day",
+ "triage": "Open",
+ }
+ ],
+ resources_total=123,
+ resources_shown=100,
+ finding_group_url=finding_group_url,
+ finding_group_link_text=finding_group_link_text,
+ risk="Productivity licenses on privileged identities create risk.",
+ recommendation_text="Maintain dedicated admin accounts.",
+ recommendation_url=recommendation_url,
+ )
+
+ assert adf_description["type"] == "doc"
+ assert self._find_empty_text_nodes(adf_description) == []
+
+ main_table = adf_description["content"][1]
+ main_rows = {}
+ for row in main_table["content"]:
+ key_cell, value_cell = row["content"]
+ main_rows[self._collect_text_from_cell(key_cell)] = (
+ self._collect_text_from_cell(value_cell)
+ )
+
+ assert (
+ main_rows["Check Id"]
+ == "admincenter_users_admins_reduced_license_footprint"
+ )
+ assert main_rows["Service"] == "exchange"
+ assert main_rows["Affected Failing Resources"] == "123"
+ assert (
+ main_rows["Risk"]
+ == "Productivity licenses on privileged identities create risk."
+ )
+ assert main_rows["Recommendation"] == (
+ "Maintain dedicated admin accounts. " + recommendation_url
+ )
+ assert "Finding Group Link" not in main_rows
+ assert "Region" not in main_rows
+
+ top_level_headings = [
+ self._collect_text_from_cell({"content": node.get("content", [])})
+ for node in adf_description["content"]
+ if node.get("type") == "heading"
+ ]
+ assert "Risk" not in top_level_headings
+ assert "Recommendation" not in top_level_headings
+ assert "Summary" not in top_level_headings
+
+ def text_marks(cell: dict) -> list[dict]:
+ return cell["content"][0]["content"][0]["marks"]
+
+ severity_marks = text_marks(
+ self._find_table_row(main_table["content"], "Severity")["content"][1]
+ )
+ status_marks = text_marks(
+ self._find_table_row(main_table["content"], "Status")["content"][1]
+ )
+ assert {
+ "type": "backgroundColor",
+ "attrs": {"color": "#FFA500"},
+ } in severity_marks
+ assert {"type": "textColor", "attrs": {"color": "#FF0000"}} in status_marks
+
+ resource_table = next(
+ node
+ for node in adf_description["content"]
+ if node.get("type") == "table"
+ and self._collect_text_from_cell(node["content"][0]["content"][0])
+ == "Resource"
+ )
+ resource_cells = resource_table["content"][1]["content"]
+ assert {"type": "textColor", "attrs": {"color": "#FF0000"}} in text_marks(
+ resource_cells[5]
+ )
+ assert {
+ "type": "backgroundColor",
+ "attrs": {"color": "#FFA500"},
+ } in text_marks(resource_cells[6])
+
+ document_text = self._collect_text_from_cell(
+ {"content": adf_description["content"]}
+ )
+ assert (
+ "Administrative users are assigned productivity licenses."
+ not in document_text
+ )
+ assert "Affected failing resources" in document_text
+ capped_link_copy = (
+ f"Showing 100 of 123 Findings in this Jira issue. {finding_group_link_text}"
+ )
+ assert document_text.count(capped_link_copy) == 1
+ assert "Finding Group Link" not in document_text
+ assert recommendation_url in document_text
+ recommendation_link_mark = self._find_link_mark_by_href(
+ adf_description["content"], recommendation_url
+ )
+ assert recommendation_link_mark is not None
+ link_mark = self._find_link_mark_by_href(
+ adf_description["content"], finding_group_url
+ )
+ assert link_mark is not None
+ assert link_mark["attrs"]["href"] == finding_group_url
+ assert self._collect_link_texts_by_href(
+ adf_description["content"], finding_group_url
+ ) == [finding_group_link_text]
+ assert (
+ len(
+ self._collect_link_texts_by_href(
+ adf_description["content"], finding_group_url
+ )
+ )
+ == 1
+ )
+ assert "filter%5Bcheck_id%5D=" in link_mark["attrs"]["href"]
+ assert "expandedCheckId=" in link_mark["attrs"]["href"]
+
+ def test_get_grouped_adf_description_includes_link_when_not_capped(self):
+ finding_group_url = (
+ "https://security.example.com/findings?"
+ "filter%5Bcheck_id%5D=s3_bucket_public_access&"
+ "expandedCheckId=s3_bucket_public_access"
+ )
+ finding_group_link_text = "View this grouped finding."
+ adf_description = self.jira_integration.get_grouped_adf_description(
+ check_id="s3_bucket_public_access",
+ check_title="S3 bucket public access",
+ severity="HIGH",
+ status="FAIL",
+ provider="aws",
+ service="s3",
+ affected_failing_resources=1,
+ grouped_resources=[
+ {
+ "resource_name": "bucket-a",
+ "resource_uid": "arn:aws:s3:::bucket-a",
+ "provider": "aws",
+ "service": "s3",
+ "provider_account": "production (123456789012)",
+ "status": "FAIL",
+ "severity": "high",
+ "region": "us-east-1",
+ "last_seen": "Jul 09, 2026 11:38AM UTC",
+ "failing_for": "< 1 day",
+ "triage": "Open",
+ }
+ ],
+ resources_total=1,
+ resources_shown=1,
+ finding_group_url=finding_group_url,
+ finding_group_link_text=finding_group_link_text,
+ )
+
+ document_text = self._collect_text_from_cell(
+ {"content": adf_description["content"]}
+ )
+ assert "Showing 1 of 1 Findings." not in document_text
+ assert "remaining Findings" not in document_text
+ assert document_text.count(finding_group_link_text) == 1
+ assert "Finding Group Link" not in document_text
+ main_table = adf_description["content"][1]
+ main_row_headers = [
+ self._collect_text_from_cell(row["content"][0])
+ for row in main_table["content"]
+ ]
+ assert "Finding Group Link" not in main_row_headers
+ link_mark = self._find_link_mark_by_href(
+ adf_description["content"], finding_group_url
+ )
+ assert link_mark is not None
+ assert link_mark["attrs"]["href"] == finding_group_url
+ assert self._collect_link_texts_by_href(
+ adf_description["content"], finding_group_url
+ ) == [finding_group_link_text]
+ assert (
+ "filter%5Bcheck_id%5D=s3_bucket_public_access" in link_mark["attrs"]["href"]
+ )
+ assert "expandedCheckId=s3_bucket_public_access" in link_mark["attrs"]["href"]
+
@patch.object(Jira, "get_access_token", return_value="valid_access_token")
@patch.object(
Jira, "get_available_issue_types", return_value=["Bug", "Task", "Story"]
@@ -1512,6 +1962,54 @@ class TestJiraIntegration:
assert result is True
mock_post.assert_called_once()
+ @patch.object(Jira, "get_access_token", return_value="valid_access_token")
+ @patch.object(
+ Jira, "cloud_id", new_callable=PropertyMock, return_value="test_cloud_id"
+ )
+ @patch.object(Jira, "get_projects", return_value={"TEST": {"name": "Test Project"}})
+ @patch.object(Jira, "get_available_issue_types", return_value=["Bug"])
+ @patch("prowler.lib.outputs.jira.jira.requests.post")
+ def test_send_finding_sanitizes_summary_control_characters(
+ self,
+ mock_post,
+ mock_get_issue_types,
+ mock_get_projects,
+ mock_cloud_id,
+ mock_get_access_token,
+ ):
+ """Test that Jira summary is sent as one line."""
+ # To disable vulture
+ mock_cloud_id = mock_cloud_id
+ mock_get_access_token = mock_get_access_token
+ mock_get_projects = mock_get_projects
+ mock_get_issue_types = mock_get_issue_types
+
+ mock_response = MagicMock()
+ mock_response.status_code = 201
+ mock_response.json.return_value = {"id": "ISSUE-123", "key": "TEST-123"}
+ mock_post.return_value = mock_response
+ long_check_id = "check\nwith\rcontrol\tcharacters " + "x" * 260
+
+ result = self.jira_integration.send_finding(
+ check_id=long_check_id,
+ check_title="Test Finding",
+ severity="High\n",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ affected_failing_resources=2,
+ grouped_resources=[],
+ )
+
+ assert result is True
+ payload = mock_post.call_args.kwargs["json"]
+ expected_summary = (
+ f"[Prowler] HIGH - {' '.join(long_check_id.split())} - "
+ "2 affected failing resources"
+ )[:255]
+ assert payload["fields"]["summary"] == expected_summary
+ assert len(payload["fields"]["summary"]) == 255
+
@patch.object(Jira, "get_access_token", return_value="valid_access_token")
@patch.object(
Jira, "cloud_id", new_callable=PropertyMock, return_value="test_cloud_id"
@@ -1527,7 +2025,7 @@ class TestJiraIntegration:
mock_cloud_id,
mock_get_access_token,
):
- """Test that send_finding returns False when the request fails."""
+ """Test that send_finding raises with Jira JSON error details."""
# To disable vulture
mock_cloud_id = mock_cloud_id
mock_get_access_token = mock_get_access_token
@@ -1537,19 +2035,66 @@ class TestJiraIntegration:
# Mock failed response
mock_response = MagicMock()
mock_response.status_code = 400
- mock_response.json.return_value = {"errors": {"summary": "Required field"}}
+ mock_response.json.return_value = {
+ "errors": {"Team": "Team is required."},
+ "errorMessages": ["Field 'Team' cannot be set."],
+ }
mock_post.return_value = mock_response
- result = self.jira_integration.send_finding(
- check_id="test-check",
- check_title="Test Finding",
- severity="High",
- status="FAIL",
- project_key="TEST",
- issue_type="Bug",
- )
+ with pytest.raises(JiraSendFindingsResponseError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
- assert result is False
+ assert "Failed to create Jira issue" in str(error.value)
+ assert "'Team': 'Team is required.'" in str(error.value)
+ assert "Field 'Team' cannot be set." in str(error.value)
+ mock_post.assert_called_once()
+
+ @patch.object(Jira, "get_access_token", return_value="valid_access_token")
+ @patch.object(
+ Jira, "cloud_id", new_callable=PropertyMock, return_value="test_cloud_id"
+ )
+ @patch.object(Jira, "get_projects", return_value={"TEST": {"name": "Test Project"}})
+ @patch.object(Jira, "get_available_issue_types", return_value=["Bug"])
+ @patch("prowler.lib.outputs.jira.jira.requests.post")
+ def test_send_finding_response_error_without_json_body(
+ self,
+ mock_post,
+ mock_get_issue_types,
+ mock_get_projects,
+ mock_cloud_id,
+ mock_get_access_token,
+ ):
+ """Test send_finding raises with status-code context for non-JSON errors."""
+ # To disable vulture
+ mock_cloud_id = mock_cloud_id
+ mock_get_access_token = mock_get_access_token
+ mock_get_projects = mock_get_projects
+ mock_get_issue_types = mock_get_issue_types
+
+ mock_response = MagicMock()
+ mock_response.status_code = 502
+ mock_response.json.side_effect = ValueError("No JSON body")
+ mock_post.return_value = mock_response
+
+ with pytest.raises(JiraSendFindingsResponseError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
+
+ assert "Failed to create Jira issue" in str(error.value)
+ assert "Jira returned status code 502" in str(error.value)
mock_post.assert_called_once()
@patch.object(Jira, "get_access_token", return_value="valid_access_token")
@@ -1567,7 +2112,7 @@ class TestJiraIntegration:
mock_cloud_id,
mock_get_access_token,
):
- """Test that send_finding returns False when custom fields cause an error."""
+ """Test that send_finding raises when custom fields cause an error."""
# To disable vulture
mock_cloud_id = mock_cloud_id
mock_get_access_token = mock_get_access_token
@@ -1585,18 +2130,89 @@ class TestJiraIntegration:
}
mock_post.return_value = mock_response
- result = self.jira_integration.send_finding(
- check_id="test-check",
- check_title="Test Finding",
- severity="High",
- status="FAIL",
- project_key="TEST",
- issue_type="Bug",
- )
+ with pytest.raises(JiraRequiredCustomFieldsError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
- assert result is False
+ assert "Jira project requires custom fields" in str(error.value)
+ assert "customfield_10001" in str(error.value)
mock_post.assert_called_once()
+ @patch.object(
+ Jira,
+ "get_access_token",
+ side_effect=JiraRefreshTokenError(message="Failed to refresh the access token"),
+ )
+ def test_send_finding_reraises_refresh_token_error(self, mock_get_access_token):
+ """Test send_finding re-raises refresh token errors for API propagation."""
+ # To disable vulture
+ mock_get_access_token = mock_get_access_token
+
+ with pytest.raises(JiraRefreshTokenError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
+
+ assert error.value.message == "Failed to refresh the access token"
+
+ @patch.object(Jira, "get_access_token", return_value=None)
+ def test_send_finding_reraises_no_token_error(self, mock_get_access_token):
+ """Test send_finding re-raises missing token errors for API propagation."""
+ # To disable vulture
+ mock_get_access_token = mock_get_access_token
+
+ with pytest.raises(JiraNoTokenError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
+
+ assert error.value.message == "No token was found"
+
+ @patch.object(
+ Jira,
+ "get_access_token",
+ side_effect=JiraRefreshTokenResponseError(
+ message="Failed to refresh the access token, response code did not match 200"
+ ),
+ )
+ def test_send_finding_reraises_refresh_token_response_error(
+ self, mock_get_access_token
+ ):
+ """Test send_finding re-raises refresh token response errors for API propagation."""
+ # To disable vulture
+ mock_get_access_token = mock_get_access_token
+
+ with pytest.raises(JiraRefreshTokenResponseError) as error:
+ self.jira_integration.send_finding(
+ check_id="test-check",
+ check_title="Test Finding",
+ severity="High",
+ status="FAIL",
+ project_key="TEST",
+ issue_type="Bug",
+ )
+
+ assert (
+ error.value.message
+ == "Failed to refresh the access token, response code did not match 200"
+ )
+
def test_get_headers_oauth_with_access_token(self):
"""Test get_headers returns correct OAuth headers with access token."""
self.jira_integration._using_basic_auth = False
diff --git a/tests/lib/outputs/ocsf/ocsf_test.py b/tests/lib/outputs/ocsf/ocsf_test.py
index 16ff1ce317..f449fd49f7 100644
--- a/tests/lib/outputs/ocsf/ocsf_test.py
+++ b/tests/lib/outputs/ocsf/ocsf_test.py
@@ -2,8 +2,10 @@ import json
from datetime import datetime, timezone
from io import StringIO
from typing import Optional
+from unittest.mock import MagicMock
from uuid import UUID
+import pytest
import requests
from freezegun import freeze_time
from mock import patch
@@ -300,6 +302,36 @@ class TestOCSF:
def test_batch_write_data_to_file_without_findings(self):
assert not OCSF([])._file_descriptor
+ def test_batch_write_data_to_file_propagates_oserror(self):
+ """An I/O error (e.g. ENOSPC) while writing a finding must propagate
+ instead of being swallowed, so the caller can fail fast."""
+ findings = [
+ generate_finding_output(
+ status="FAIL",
+ severity="low",
+ muted=False,
+ region=AWS_REGION_EU_WEST_1,
+ timestamp=datetime.now(),
+ resource_details="resource_details",
+ resource_name="resource_name",
+ resource_uid="resource-id",
+ status_extended="status extended",
+ )
+ ]
+
+ output = OCSF(findings)
+ mock_file = MagicMock()
+ mock_file.closed = False
+ # Non-zero so the "[" prelude is skipped and the failure happens on the
+ # per-finding write, the exact path that hit ENOSPC in production.
+ mock_file.tell.return_value = 1
+ mock_file.write.side_effect = OSError(28, "No space left on device")
+ output._file_descriptor = mock_file
+
+ with pytest.raises(OSError) as excinfo:
+ output.batch_write_data_to_file()
+ assert excinfo.value.errno == 28
+
def test_finding_output_cloud_pass_low_muted(self):
finding_output = generate_finding_output(
status="PASS",
diff --git a/tests/lib/outputs/outputs_test.py b/tests/lib/outputs/outputs_test.py
index 4aeccf1104..fad6f4d286 100644
--- a/tests/lib/outputs/outputs_test.py
+++ b/tests/lib/outputs/outputs_test.py
@@ -51,9 +51,7 @@ class TestOutputs:
def test_parse_html_string(self):
string = "CISA: your-systems-3, your-data-1, your-data-2 | CIS-1.4: 2.1.1 | CIS-1.5: 2.1.1 | GDPR: article_32 | AWS-Foundational-Security-Best-Practices: s3 | HIPAA: 164_308_a_1_ii_b, 164_308_a_4_ii_a, 164_312_a_2_iv, 164_312_c_1, 164_312_c_2, 164_312_e_2_ii | GxP-21-CFR-Part-11: 11.10-c, 11.30 | GxP-EU-Annex-11: 7.1-data-storage-damage-protection | NIST-800-171-Revision-2: 3_3_8, 3_5_10, 3_13_11, 3_13_16 | NIST-800-53-Revision-4: sc_28 | NIST-800-53-Revision-5: au_9_3, cm_6_a, cm_9_b, cp_9_d, cp_9_8, pm_11_b, sc_8_3, sc_8_4, sc_13_a, sc_16_1, sc_28_1, si_19_4 | ENS-RD2022: mp.si.2.aws.s3.1 | NIST-CSF-1.1: ds_1 | RBI-Cyber-Security-Framework: annex_i_1_3 | FFIEC: d3-pc-am-b-12 | PCI-3.2.1: s3 | FedRamp-Moderate-Revision-4: sc-13, sc-28 | FedRAMP-Low-Revision-4: sc-13 | KISA-ISMS-P-2023: 2.6.1 | KISA-ISMS-P-2023-korean: 2.6.1"
- assert (
- parse_html_string(string)
- == """
+ assert parse_html_string(string) == """
•CISA: your-systems-3, your-data-1, your-data-2
•CIS-1.4: 2.1.1
@@ -94,7 +92,6 @@ class TestOutputs:
•