Security & Compliance
Penetration testing
No penetration test of ArkCloud has been performed, and there is no report to share. This page says what is proposed, what testing exists in its place, and how to arrange your own.
Written for: Security reviewers · Procurement
Current status
ArkCloud's draft risk management plan proposes an external test covering authentication, isolation between organisations and the administrative screens, before the first covered-entity customer goes live and annually after that. No vendor or date has been chosen.
What is tested internally
| Field or control | What it means |
|---|---|
| Isolation between organisations | A program that connects as the application's own database role and proves that queries see only the current organisation's rows, and none without one. |
| Role checks on every data-changing action | An automated test fails if an action that writes data does not check the caller's role, and calls real actions as low-privilege roles to prove they are refused. |
| Tenant scoping of database access | Source-scanning tests fail if server code reads or writes organisation data outside the organisation's database scope. |
| Signed background jobs | Tests forge, tamper with and replay background-job messages and check that each is rejected. |
Arranging your own assessment
Write to [email protected] before testing, with the scope, dates, source addresses and the tester's contact. The hosted service is shared by several organisations, so testing must be agreed in writing first and must stay within your own organisation's accounts.