Cis Azure Database 4.2

DevOps & Security

cis-azure-database-4.2

Cis Azure Database 4.2 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure Data Factory is using Managed Identities

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Database_Services_Benchmark_v2.0.0/cis-azure-database-4.2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-database-4-2, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

4.2 Ensure Data Factory is using Managed Identities (Automated)

Profile Applicability

Level 1

Description

Managed identities are the roles that Azure services assume to access other services or resources. Access and permissions may be set on these roles to set the scope and reach of what a service can access. Setting a service to use a managed identity also prevents the need to store credentials in code or other less secure options.

Rationale

Managed identities eliminate the need to store and manage credentials to access Azure resources. Scoping permissions of a managed identity to a specific set of resources also prevents unwanted access elsewhere.

Impact

Initial administrative overhead to configure and manage role assignments for managed identities.

Audit

Audit from Azure Portal

From Data Factories select a factory to audit.
In the left column expand > Settings.
Select Managed identities.
In the top System assigned menu, determine if the default identity is in use under Status, by whether this is set to On.
Determine if there are any custom identities assigned to this resource by selecting in the top menu User Assigned.

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: f78ccdb4-7bf4-4106-8647-270491d2978a - Name: 'Azure Data Factory linked services should use system-assigned managed identity authentication when it is supported'

Expected Result

The Status under System assigned should be set to On, indicating that a managed identity is in use for the Data Factory.

Remediation

Remediate from Azure Portal

From Data Factories select a factory to remediate.
In the left column expand > Settings.
Select Managed identities.
From the System Assigned tab, under Permissions select Azure role assignments.
Select + Add role assignments (Preview).
Select a Scope, Subscription and Role to be added.
Select Save.

Default Value

By default, Data Factories use a system assigned managed identity, with no permissions to resources set.