What is production environment separation?
Production environment separation keeps live systems and customer data apart from development and testing environments. It is usually done with separate cloud accounts, networks, and access permissions. It prevents test code or developer mistakes from affecting customers.
What the buyer is really asking
Buyers want production kept apart from development and testing, ideally in separate cloud accounts with separate access. Say who can reach production and confirm that test environments do not hold production data.
Other ways buyers ask it
Every one of these wants the same answer:
- “How do you segregate production and non-production environments?”
- “Are development and production in separate accounts?”
- “Do developers have access to production?”
Evidence to have ready
- The cloud account structure
- Access policies for the production account
How Tyrvar answers this
Tyrvar treats every wording above as one question. You write the answer once, attach the evidence, and revisit it when your setup changes. Each buyer gets that approved answer no matter how their questionnaire words it. If you have not answered it yet, Tyrvar flags the question for you and does not make something up. Try it on your own questionnaire.
Related cloud and infrastructure questions
- Do you utilize a Web Application Firewall (WAF)?
- Can customers export their data programmatically, and what portability and exit provisions exist (formats, retention, deletion on termination)?
- Which cloud service providers (CSP) do you use to host your services?
- How do you document and apply the shared security responsibility model (SSRM) between your organization, your cloud providers, and your customers?