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.

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

Defender: Azure Cosmos DB should disable public network access #4322

Closed
jonnyry opened this issue Feb 5, 2025 · 3 comments · Fixed by #4324
Closed

Defender: Azure Cosmos DB should disable public network access #4322

jonnyry opened this issue Feb 5, 2025 · 3 comments · Fixed by #4324
Assignees
Labels
story Stories are the smallest unit of work to be done for a project.

Comments

@jonnyry
Copy link
Collaborator

jonnyry commented Feb 5, 2025

Azure Cosmos DB should disable public network access - cosmos-[treid], cosmos-mongo-[treid]

From the Defender list: #4303

@jonnyry jonnyry added the story Stories are the smallest unit of work to be done for a project. label Feb 5, 2025
@jonnyry jonnyry self-assigned this Feb 5, 2025
@marrobi
Copy link
Member

marrobi commented Feb 5, 2025

@jonnyry I'm sure the current config doesn't allow public access? Is this as we have the ability to add an IP to an allowed list?

@jonnyry
Copy link
Collaborator Author

jonnyry commented Feb 5, 2025

We're currently on "Selected Networks", whereas Defender wants "Disabled":

Image

I was planning to make the following change:

Image

@jonnyry
Copy link
Collaborator Author

jonnyry commented Feb 5, 2025

I realise it's hair splitting... since without any IPs it doesn't do anything. Perhaps we should log with the Defender team :-D

jonnyry added a commit that referenced this issue Feb 13, 2025
* Defender: Azure Cosmos DB should disable public network access #4322
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Stories are the smallest unit of work to be done for a project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants