In this post
Why organisations choose it
- Data stays on systems the organisation controls.
- Data-residency and contract limits are easier to meet.
- The system can run in a network with no outside access.
- Costs are predictable once the hardware exists.
What you still have to do
- Access control. Restrict who can use the model and what documents it can read.
- Logging and retention. Decide what is recorded, who sees it and for how long.
- Isolation. Segment the network; log and review administrator access.
- Updates. You own patching for the runtime, the drivers and the model.
Questions to answer first
- What data will the system touch, and under which rules?
- Who may use it, and for what?
- What happens when it is wrong, and who checks?
- Who is accountable for the system?
A note on compliance
Regulations differ by country and sector. Ask your compliance or legal team what applies. Nothing in this post is legal advice.
Sources and further reading
- NIST. AI Risk Management Framework (AI RMF 1.0). nist.gov/itl/ai-risk-management-framework.
IICTP is a new independent credential and is not ISO/IEC 17024 accredited.