Governance & Security

How do I convince my customers that Nuon is secure?

›

How are secrets added to a customer install?

›

Can customers restrict Nuon’s access to their infrastructure?

›

Can Nuon be used for hybrid or split-plane deployments where part of the application is in the vendor's cloud and part in the customer's cloud?

›

Can Nuon be integrated with existing identity providers for authentication?

›

Does Nuon support cross-account access?

›

Can customers enforce security policies in multi-cloud environments using Nuon?

›

Can customers enforce strict firewall rules to limit external access?

›

How does Nuon handle customer requests for a Software Bill of Materials (SBOM) for deployed services and components?

›

Can a customer's security policies be enforced?

›

Our Terraform requires extensive IAM permissions. If Nuon is running our Terraform, how do we enforce the customer's permission controls, since our Terraform could provision a role with full

›

How do I test Nuon without accidentally giving you customer credentials or production AWS tokens?

›

Will bringing in Nuon trigger a security review from our customers?

›

Can you have different permission sets for initial deployment versus ongoing maintenance — rather than a single always-on permission?

›

What are common customer security concerns around BYOC day-two operations?

›

How does Nuon address security and day-two operations concerns for BYOC vendors?

›