When to discuss this
A useful starting point
Useful whenever security requirements must be translated into an architecture review and an evidence request.
Loading…
Infrastructure Security
Review the proposed hosting architecture with your IT and security teams. Agree controls for the actual deployment rather than assuming a certification or standard service profile.
Discussion diagram · configuration and responsibilities to agree.
Decide with your IT team
When to discuss this
Useful whenever security requirements must be translated into an architecture review and an evidence request.
What to examine
A diagram or product page cannot establish a certification or confirm a control in your deployment. Review the agreed architecture and evidence.
Name the owners
These are discussion roles, not a promised service arrangement. Agree the actual division of work for your project.
| Role | Discussion responsibility |
|---|---|
| Security team | Define required controls, review evidence and approve testing scope. |
| Technical operator | Identify control ownership and operating procedures. |
| Business owner | Agree risk decisions and escalation responsibilities. |
Agree what good looks like
Discuss network exposure, administrative access and identity controls.
Review patching, monitoring and incident-response ownership.
Agree the documents and checks needed for procurement review.
Your security requirements
Architecture and control review
Agreed responsibilities and evidence
Conceptual flow — subject to requirements review.
Plan your learning program
Hosting availability, certifications, security controls, data residency, uptime and recovery targets must be confirmed for the agreed project.
Talk through your learning goals, content and deployment needs.