Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix output + branding for Azure examples #227

Merged
merged 1 commit into from
Jun 12, 2024
Merged

Fix output + branding for Azure examples #227

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions docs/cnspec/cloud/azure/README.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,18 +173,22 @@ From the resulting list, you can drill down even further. You can also learn abo

Now that you know how to discover what's possible with cnspec, let's run some actual tests in the shell.

#### Assess SQL server auditing
#### Assess Azure SQL Database auditing policy

This test assures that auditing is turned on for your SQL servers:
This test assures that auditing is turned on for your Azure SQL Database instances:

```bash
azure.subscription.sql.servers { auditingPolicy['state'] == "Enabled" }
```

If the test passes (all SQL servers have auditing enabled) then cnspec returns `ok`:
If the test passes (all servers have auditing enabled) then cnspec returns `true` for each server:

```coffeescript
[ok] value: true
azure.subscription.sql.servers: [
0: {
auditingPolicy.state == "Enabled": true
}
]
```

If the test fails, (one or more Cloud Storage buckets don't use uniform bucket-level access) then cnspec provides details about the failure.
Expand Down
Loading