Australia · UK · Middle EastOffices: Sydney · Melbourne · Londonsales@commandpost.app
Trust centre

Answers for your security and procurement teams

How CommandPost® is hosted, secured, assessed and made accessible, in one place. Start your security review here, before the demo.

Download the capability statement
Security overview

Secure by design, and checked on every change

Security controls are designed against the Australian Government's PSPF, ISM and Essential Eight, and built into how the solution is written, tested and run.

  • Encryption

    Data is encrypted in transit with TLS 1.2 or higher (TLS 1.3 preferred), and sensitive fields are encrypted with AES-256.

  • Identity and access

    Multi-factor authentication and role-based permissions for every operation. Changing a password, role or MFA setting ends every existing session.

  • Organisation isolation

    Each organisation's data is kept apart from every other organisation's, with automated tests for isolation and access control.

  • Append-only audit trail

    Every change a user makes is recorded, cannot be altered and is kept for seven years.

  • Vulnerability management

    Critical vulnerabilities are patched within 48 hours and high ones within two weeks, in line with the Essential Eight.

  • Change control

    Every change is peer reviewed and tested, and each production release needs an independent approval.

Hosting and privacy

Your data stays in the region you choose

Each deployment is hosted on Amazon Web Services in its own region, and its data does not leave that region.

Global regional coverage, plus on-premises

Each organisation is hosted in the region it chooses, anywhere in the world - or deployed on-premises.

Provider
Amazon Web Services
Data residency
Data stays within that region
Operating somewhere else? Talk to our team about hosting in your region.

How we handle personal information

  • Only what is neededWe collect only the personal information an operation needs.
  • Only for its purposePersonal information is never reused for another purpose, in line with the Australian Privacy Principles.
  • Logs without personal detailsSystem logs carry user IDs, not names or contact details.
  • Classified appropriatelyIncident and personal information is handled as OFFICIAL: Sensitive, and never cached in the browser's local storage.
Compliance status

Where we stand, stated plainly

Our current position against the frameworks buyers ask about most. Ask us for the latest evidence for any of them.

FrameworkStatusDetail
NSW Government ICT Services SchemeApproved supplierListed on the Advanced Register.
PSPF, ISM and the Essential EightAlignedControls designed against the Australian Government's security frameworks.
Privacy Act 1988 and the Australian Privacy PrinciplesAlignedPersonal information handled in line with the APPs.
WCAG 2.2 AATarget standardSee the accessibility statement for known issues.

Status as at September 2026.

Accessibility statement

Built for everyone in the control room

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the CommandPost® web app, the mobile and desktop apps, and this website.

The web app is designed for keyboard-only use, screen readers and high-contrast settings, and supports right-to-left languages such as Arabic.

Parts of this website move on their own: the home page slideshow, background videos, the auto-advancing feature and scale tours, the world map's animated routes, and the live console preview. To pause all of them, select the accessibility button in the bottom corner of any page (for keyboard users, it is the first control after the Skip to content link) and turn on Pause all videos and animations. Your choice applies on every page and is remembered in this browser. If your device is set to reduce motion, you see them already paused.

Report a problem

If something is hard to use, email support@commandpost.app and tell us the page and what happened.

This statement was last reviewed in September 2026.

Documents

Take the answers with you

  • Capability statement

    Two pages on what CommandPost® does, who it serves, how it is hosted and secured, and our company details.

    PDF · 2 pagesDownload Capability statement
  • Security pack

    Architecture, controls and hosting in detail, with our answers to common security questionnaires.

    On request
  • Accessibility statement

    Our WCAG 2.2 AA position and the known issues we are fixing.

    On this pageRead Accessibility statement
  • Privacy Policy

    How we collect, use and protect personal information.

    Web pageRead Privacy Policy
  • Terms of Service

    The terms that apply to every CommandPost® account.

    Web pageRead Terms of Service

Request the security pack

This form needs scripts to send your enquiry, and they are not running. Please email sales@commandpost.app instead.

Your enquiry is stored in the region you select above. See our Privacy Policy for details. Enquiries for a region where CommandPost® is not yet hosted, and Other, are stored in Australia.

Schedule a demo

See CommandPost® set up for your agency. Tell us a little about you and our team will arrange a time.

This form needs scripts to send your enquiry, and they are not running. Please email sales@commandpost.app instead.

Step 1 of 2Your Details

Cookie preferences

We use cookies to improve your experience on this website. You may choose which types of cookies to allow and change your preferences at any time. Disabling cookies may impact your experience on this website.

You can learn more in the cookies section of our Privacy Policy.

Accessibility

We are committed to meeting the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard expected of government digital services, across the CommandPost® web app, admin console and mobile apps, and this website.

Stops background videos, auto-advancing tours, animated maps and the live console preview on every page. Saved in this browser.

How we build for accessibility

If something is hard to use, email support@commandpost.app and tell us the page and what happened.

Read our full accessibility statement