Summary
- Saviynt has launched its EU Sovereign Identity Security Cloud on S3NS's PREMI3NS platform, with Thales providing operational support.
- PREMI3NS holds France's SecNumCloud qualification; the qualification should not be represented as a separate certification of Saviynt's software.
- The offering addresses identity governance for users and automated systems, with deployment choices increasingly shaped by data control, jurisdiction, and operational resilience.
Saviynt has made its identity security platform available on a French trusted cloud service, extending the options for European organisations seeking tighter control over the systems that manage access to sensitive information. The new offering operates on S3NS’s PREMI3NS infrastructure, which holds France’s SecNumCloud qualification, with operational support from Thales.
Introduced on 19 November, the EU Sovereign Identity Security Cloud is intended for public authorities, critical infrastructure operators and regulated businesses whose requirements extend beyond selecting a conventional European hosting region. Saviynt’s software provides identity governance and access management capabilities, while the infrastructure arrangement is designed to address additional concerns about operational control and legal jurisdiction.
PREMI3NS is operated by S3NS, a French company controlled by Thales and developed through a partnership with Google Cloud. It received SecNumCloud 3.2 qualification from France’s national cybersecurity agency, ANSSI. That qualification applies to the specified cloud infrastructure service and should not be interpreted as an independent certification of every application running on it.
The distinction is important for customers assessing an identity security deployment. A qualified hosting environment provides assurances about particular infrastructure and operational controls, but organisations must also evaluate the software, its configuration and the connections through which it administers access to other systems.
Identity infrastructure becomes a sovereignty concern
Organisations often assess cloud sovereignty through the location of business records and the legal arrangements governing the providers that store them. However, identity systems can create dependencies extending beyond those records because they determine which users and applications are authorised to access information and perform operations.
An organisation might host sensitive databases in a controlled environment while relying on a separate provider for identity governance. That service can hold information about privileged accounts, employee access rights and connections between applications. Its administration and availability may therefore become relevant to the security of the wider technology estate.
Saviynt’s platform is designed to manage access across multiple business systems, including permissions associated with employees, contractors and non-human identities. The latter category includes software services and automated processes that require credentials or other mechanisms to interact with applications.
As organisations introduce AI agents capable of accessing data or initiating tasks, the management of these identities becomes more complicated. An automated system may need permission to retrieve selected information or execute particular operations, but that does not mean it should inherit unrestricted access to the accounts and applications available to its human operator.
Identity governance provides mechanisms for defining those permissions, reviewing access and withdrawing privileges that are no longer required. The effectiveness of such controls depends on the accuracy of the underlying identity information and the way applications enforce the decisions produced by the governance platform.
Operating that technology within a trusted cloud may address certain procurement and jurisdictional requirements, although it cannot remove weaknesses caused by excessive permissions, poor account management or incomplete integration with existing systems.
French qualification addresses specific operational controls
France’s SecNumCloud framework establishes requirements covering technical security, organisational arrangements and protection against specified legal and operational risks. For customers handling sensitive information, the qualification provides a defined assurance framework against which the underlying cloud service can be assessed.
PREMI3NS combines technology associated with Google Cloud with an operating model controlled through S3NS. Its qualification demonstrates that the service has been assessed against the relevant French requirements, including arrangements intended to protect customers from certain forms of external legal and operational influence.
This illustrates a distinction sometimes lost in discussions about European cloud infrastructure. A sovereign service does not necessarily require every software component to have originated within Europe, although its operating arrangements must satisfy the controls and legal requirements relevant to the promised level of sovereignty.
Customers will still need to understand who administers the service, how privileged access is managed and whether particular functions depend on infrastructure or suppliers outside the qualified environment. Those questions become more demanding when the deployed application connects with directories and business systems operated in other locations.
For Saviynt, the arrangement provides a route to customers who may otherwise find a conventional software-as-a-service deployment difficult to approve. The company already offers different hosting and deployment options, but the French trusted cloud expands its ability to address organisations with more restrictive infrastructure requirements.
Integration remains the substantial implementation task
Identity security projects can require extensive preparation because businesses rarely operate a single directory or application environment. Acquisitions, legacy systems and different departmental requirements may have produced inconsistent accounts and access controls over many years.
Introducing centralised governance involves identifying those systems, establishing appropriate permissions and deciding which individuals are responsible for approving access. Privileged accounts may require additional controls because misuse can expose administrative functions or sensitive information across several connected applications.
Automation can help manage reviews and access requests, but its usefulness depends on the quality of the information supplied. An organisation that has not established reliable records of account ownership or employee responsibilities may struggle to automate access decisions without reproducing existing weaknesses.
Operational resilience also requires attention. If an identity service becomes unavailable, users and automated applications may lose access to essential functions even where the underlying business systems remain operational. Customers need to examine the availability arrangements, recovery procedures and dependencies associated with the complete deployment.
Such assessments are relevant across public administration, financial services and critical infrastructure. These organisations may use different regulatory frameworks, but they share a requirement to establish how essential systems remain secure and accessible during disruptions.
Saviynt’s new offering provides another deployment environment for identity management under a French-qualified infrastructure framework. The company has not disclosed customer numbers, implementation costs or independent performance comparisons associated with the launch, leaving commercial adoption and operational results to be established.
The service’s practical value will depend on whether organisations can integrate it with their existing applications while satisfying the requirements governing sensitive information and critical access systems. The hosting qualification addresses an important part of that assessment, but effective identity governance remains dependent on the permissions, processes and operational controls established by each customer.












