Advisory & Delivery

Secure Application Development

When the requirement does not exist as a product, we build it. CDTS develops secure mobile applications for organisations that cannot use the consumer equivalent.

Some requirements have no commercial answer. A field team needs to capture imagery that must never touch the camera roll. A department needs contacts on a handset without exposing the whole directory. An agency needs protective markings enforced on a phone, not just in a desktop mail client.

CDTS builds those applications, and we have shipped three of them: Secure Your Contacts, MailGate and the CDTS Secure Camera Application. All three run in Australian government environments today.

We build for the environment we know — managed fleets, MDM-delivered configuration, enterprise identity, and an audit trail that someone will eventually have to produce.

What’s included

Scope of the service

The components we deliver and operate under this service. Scope is agreed per engagement — this is the standard shape.

01

Secure mobile applications

iOS and Android applications designed for managed fleets, delivered through your MDM with configuration applied at enrolment.

02

Secure content management

Containerised handling of documents, imagery and contact data with export and sharing controls that hold.

03

Enterprise integration

Identity, directory, SIEM and document management integration built in rather than bolted on afterwards.

04

Classification-aware design

Handling behaviour driven by protective markings and cohort policy, including EPMS-conformant parsing where relevant.

05

Audit & evidence

Logging designed around what your assessors and investigators will ask for, exported to your SIEM.

06

Ongoing maintenance

OS release compatibility, security patching and feature development under a support agreement.

Common questions

Do you build anything, or only mobile applications?

Our track record is in secure mobile applications for managed fleets — that is where our depth is, and we will say so if a requirement sits outside it rather than learning on your budget.

Who owns the intellectual property?

Agreed per engagement and written into the contract before work starts. For bespoke development commissioned by a customer, the default position is that you own it.

How do the applications get onto devices?

Through the MDM you already run, with configuration applied at enrolment. Users do not visit an app store or type in a server address — the app arrives configured.

What happens after launch?

OS release compatibility, security patching and feature development under a support agreement. Mobile applications that are not maintained break at the next major OS release, so this is not optional.

Next step

Talk to us about Secure Application Development

Tell us what the environment looks like today. We will tell you honestly whether this is the right place to start.