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

docs: update README.md with additional security measures #138

Merged
merged 2 commits into from
Nov 13, 2023

Conversation

anfibiacreativa
Copy link
Member

Propose additional security measures in the readme

README.md Outdated Show resolved Hide resolved
README.md Outdated
@@ -226,6 +226,10 @@ By default, the deployed Azure web app will have no authentication or access res

To then limit access to a specific set of users or groups, you can follow the steps from [Restrict your Azure AD app to a set of users](https://learn.microsoft.com/azure/active-directory/develop/howto-restrict-your-app-to-a-set-of-users) by changing "Assignment Required?" option under the Enterprise Application, and then assigning users/groups access. Users not granted explicit access will receive the error message -AADSTS50105: Your administrator has configured the application <app_name> to block users unless they are specifically granted ('assigned') access to the application.-

### Additional security considerations

We recommend deploying additional security mecahnisms. When applicable, consider setting up a [VNet](https://learn.microsoft.com/azure/virtual-network/virtual-networks-overview) or setting up a [Proxy Policy](https://learn.microsoft.com/en-us/azure/api-management/proxy-policy).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be useful to add a bit of context to explain the use cases? Like for the VNet saying that it's for restricting access to internal company network, and selectively expose public services through APIM?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm merging for now and evaluating. There are many potential use-cases and that's why the reference is "when applicable". You make a good point, though.

Co-authored-by: Yohan Lasorsa <noda@free.fr>
@anfibiacreativa anfibiacreativa merged commit d265680 into main Nov 13, 2023
6 checks passed
@anfibiacreativa anfibiacreativa deleted the docs/update-readme-security-section branch January 19, 2024 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants