[AGENTLESS][SEC-17683] Add Azure onboarding to Agentless documentation #26786
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Making it cloud provider agnostic
Also updated the page to remove AWS-specifics (except for lambdas as we don't support azure serverless)
aviat
reviewed
Dec 17, 2024
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
kacembouhmadi
changed the title
diogocp
reviewed
Dec 18, 2024
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
|
|
||
| 1. On the [Cloud Security Management Setup][1] page, click **Cloud Integrations** > **Azure**. | ||
| 1. Locate the tenant id of your subscription. | ||
| 1. **[OPTIONAL]** you can enable **Resource Scanning** for the tenant to also enable misconfigurations detection. |
There was a problem hiding this comment.
Suggested change
| 1. **[OPTIONAL]** you can enable **Resource Scanning** for the tenant to also enable misconfigurations detection. |
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Diogo Pereira <[email protected]>
drichards-87
requested changes
Dec 20, 2024
content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/terraform.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/quick_start.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/setup/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: DeForest Richards <[email protected]>
drichards-87
requested changes
Dec 24, 2024
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/agentless_scanning/_index.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
Comment on lines
17
to
21
| <div class="alert alert-info">This article provides instructions for the new user quick start workflow that uses AWS CloudFormation to set up Agentless Scanning. | ||
| For existing users who want to add a new AWS account or enable Agentless Scanning on an existing integrated AWS account, see the instructions for | ||
| <a href="/security/cloud_security_management/setup/agentless_scanning/terraform">Terraform</a>, | ||
| <a href="/security/cloud_security_management/setup/agentless_scanning/cloudformation">AWS CloudFormation</a>, | ||
| or <a href="/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager">Azure Resource Manager</a>.</div> |
There was a problem hiding this comment.
I created a test org. and it looks like the quick start workflow is only available for AWS right now? If that's correct, then I think we should remove Azure Resource Manager from the note, or reword the note so that it's not specific to AWS.
There was a problem hiding this comment.
Yes, the quick start workflow is not available on Azure yet. I think the paragraph above is a generic paragraph we tried to reuse in most setup pages, but it can lead to some confusion indeed.
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Show resolved
Hide resolved
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
Co-authored-by: DeForest Richards <[email protected]>
...ent/en/security/cloud_security_management/setup/agentless_scanning/azure_resource_manager.md
Outdated
Show resolved
Hide resolved
k3nz0
approved these changes
Jan 2, 2025
mohamed-challal
approved these changes
Jan 2, 2025
drichards-87
approved these changes
Jan 2, 2025
|
/merge |
Devflow running:
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
This PR mainly document the support of Azure cloud provider in the K9 Agentless solution.
We tried to make most of the Agentless docs cloud-agnostic, although we might want to revisit the structure of the documentation later on.
Why does it matter?
We'll soon support Azure onboarding from the UI for existing subscriptions.
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/descriptionnaming convention) and then add the following PR comment:Additional notes