[IRQ-446] Answering the need to clarify allow-listing domain procedure #3392
Conversation
This file contains hidden or 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
yanjost
requested changes
Oct 23, 2025
It was redacted this way before: neutral way "The user" for pre-conditions, and direct way "Your company" for procedure |
EtienneM
requested changes
Oct 27, 2025
No specific reason, I agree with your recommendation Co-authored-by: Étienne M. <[email protected]>
Agree Co-authored-by: Étienne M. <[email protected]>
Agree Co-authored-by: Étienne M. <[email protected]>
SC-Jerome-S
requested review from
EtienneM and
yanjost
and removed request for
EtienneM
EtienneM
reviewed
Oct 28, 2025
SC-Jerome-S
changed the title
Sure - you're right, sorry (my fault, I missed it also) Co-authored-by: Étienne M. <[email protected]>
Thank you, you've got sharp eyes! |
EtienneM
approved these changes
Oct 29, 2025
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.
From: https://scalingo.atlassian.net/browse/IRQ-446
Internal procedure change: https://github.com/Scalingo/specifications/pull/486
Overview:
This commit significantly improves the documentation for accessing the SecNumCloud (osc-secnum-fr1) region by clarifying the domain whitelisting procedures and access requirements for users.
1. Enhanced user access section
Clarified Language and improved Clarity: made it clear that user accounts must be explicitly allow-listed before accessing the region
2. Refined "Pre-conditions" language
Enhanced the description for legitimate access reasons, domain verification and added requirement that company domains must already be associated with existing applications in the region.
3. Restructured access procedures
Streamlined process for users from companies with existing SecNumCloud presence
Access without whitelisted domain: Clear process for new domain requests
Domain declaration and regularization
Objectives:
Reduced Support Burden: clearer procedures reduce unclear requests - better explanation of verification requirements
Compliance documentation: better alignment with SecNumCloud security requirements