Secure AirWatch certificate management and SCEP in Australia
An Australian mobile fleet can include corporate phones, tablets, laptops, rugged devices and personal smartphones used for work. Certificates connect those endpoints to corporate Wi-Fi, VPNs, applications and cloud services, so their failure can interrupt access without exposing the underlying data. AirWatch certificate management and SCEP provide a practical way to automate issuance, renewal and revocation across this mixed environment.
A sound design separates certificate authority services, identity providers, endpoint enrolment and policy enforcement. It also establishes ownership for every stage of the lifecycle, including failed requests, departing employees and devices that remain offline. Without those controls, certificate management often becomes another collection of scripts and long-lived credentials maintained by a small IT team.
Australian organisations must balance this automation with privacy, security and connectivity requirements. The Privacy Act 1988, Australian Privacy Principles and the ASD Essential Eight all influence how identity and device records should be protected. Remote workers may rely on NBN services or mobile connections, while field staff can move between patchy coverage and fully offline periods.
The right approach treats certificates as governed enterprise assets rather than optional technical settings. Clear templates, least-privilege permissions and tested renewal procedures reduce manual work while preserving visibility. The result is a consistent security posture for applications, company data and business-critical access.
Why certificate controls need clear ownership
Certificates may sit at the centre of a Zero Trust strategy, but they are not the whole strategy. A valid certificate proves that a key is controlled by a particular device or service; it does not automatically prove that the user has appropriate access rights. Identity matching, device posture, application authorisation and certificate revocation therefore need to work together.
Common failure patterns include copying an old certificate profile, retaining default validity periods and sharing one SCEP account across multiple administrators. These choices can work in a small laboratory but create blind spots at scale. Operational ownership should cover certificate templates, SCEP endpoints, private keys, monitoring, incident response and periodic recertification.
Local terminology can also obscure responsibility. Australian IT teams commonly use plain terms such as “cert”, “enrolment” and “cert refresh”, so a runbook should still distinguish a routine renewal from a full reissue. The same discipline applies to managed service providers and regional support partners, which are prominent in the Australian market and need explicit boundaries for escalation.
Design the trust chain before creating profiles
Start by mapping the trust path from the certificate authority to the AirWatch console, enrolment service and managed endpoint. Identify which platform holds the signing key, whether the authority is part of Active Directory Certificate Services or a supported third-party service, and how devices receive revocation information. A diagram showing these dependencies is often more useful than a list of individual console settings.
Use separate trust relationships for workforce devices, corporate applications and specialised infrastructure. Personal devices may receive configuration and access to selected business services, but their trust should not extend beyond the permissions required for work. This separation makes certificate compromise easier to contain and gives privacy teams a clearer view of what organisational data the device can access.
A useful second pass is to compare the proposed design against independent AirWatch deployment guidance before changing production profiles. Confirm every assumption in a test tenant, including enrolment timing, profile dependencies, network requirements and behaviour during certificate expiry. Production automation should never be the first environment in which those assumptions are tested.
Harden SCEP enrolment without weakening automation
SCEP, the Simple Certificate Enrolment Protocol, supports automated certificate requests and renewals, including exchanges such as GetCACert and GetCert. Its original design has inherent security limitations, so an exposed SCEP endpoint should not be treated as trustworthy simply because the response contains a signed certificate. Controls around the service account, network path and issuing permissions are essential.
The following comparison shows sensible baselines for common design decisions:
| Design decision | Recommended baseline | Alternative | Main trade-off |
|---|---|---|---|
| Issuing authority | Approved enterprise CA with protected templates and keys | Separate issuing CA for mobile certificates | Isolation improves control but adds administration |
| Service identity | Dedicated least-privilege account with short-lived credentials or mutual TLS | Short-lived credentials when mutual TLS is unavailable | Stronger authentication can affect compatibility |
| Network access | Restrict requests to the AirWatch service and authorised administration paths | Private connection or VPN for the SCEP endpoint | More secure routes may require network changes |
| Cryptography | RSA 2048 with SHA-256, or ECDSA P-256 where supported | Approved organisational standard for specialist platforms | Legacy algorithms may ease migration but weaken assurance |
| Renewal policy | Validity aligned to risk, with renewal before expiry | Extended validity for devices with intermittent connectivity | Longer validity improves field reliability but increases exposure |
Protect the SCEP service account as an identity with its own access review and rotation process. Avoid embedding reusable credentials in scripts, documentation or support tickets. Where the platform supports it, use mutual TLS, private connectivity and source allowlists to prevent unauthorised hosts from reaching the enrolment service.
Template permissions deserve the same attention. Separate enrolment, renewal and revocation duties where the certificate authority permits it, and restrict administrators from approving their own exceptional requests. Log issuance, template changes, failed challenges and denials in a central system, then define how long those records must be retained.
Connect certificates to identity and device compliance
Bind each certificate to the appropriate device and, where needed, user identity without placing unnecessary personal information in the subject or SAN. Device-only templates suit continuous access to business resources, while user certificates may be required for strong authentication or regulated applications. Avoid templates that combine both identities when a simpler design would meet the requirement.
AirWatch compliance policies should check certificate presence, validity and revocation status before granting access to sensitive applications. Apply a sensible grace period for renewal, but do not let an expired certificate retain privileged access indefinitely. The same policy can restrict unmanaged or jailbroken devices, which is particularly important when personal smartphones participate in BYOD programmes.
Certificate metadata should be handled according to its actual sensitivity. Device identifiers, employee names and access histories may support legitimate security operations, but their collection and retention should follow the organisation’s Australian privacy obligations. State and sector-specific requirements may add further controls, particularly for healthcare, education and government workloads.
Operate renewal and recovery as one lifecycle
Automation succeeds when it can recover from predictable events. Set renewal windows based on certificate lifetime rather than a universal number of days, and create enough overlap for devices that sleep, travel or spend long periods outside cellular coverage. Production-ready templates should state their renewal behaviour, dependencies and escalation path.
Monitoring needs to cover both issued and missing certificates. Dashboards should reveal approaching expiry, failed enrolments, stale devices and unusual issuance volumes. Administrators should also test revocation, because a certificate can appear healthy until its associated access point receives an update. Runbook schedules should use UTC alongside local windows across Sydney, Melbourne and Brisbane, where daylight-saving rules differ.
These operational safeguards keep certificate services dependable:
- Run a staged pilot in a laboratory tenant, then expand through a controlled group before enabling broad enrolment.
- Rotate SCEP service credentials and certificate authority authorisation according to defined schedules.
- Alert on failed requests, expiring certificates, long-overdue devices and unexpected changes to templates.
- Maintain tested recovery steps, alternate connectivity and documented ownership for certificate revocation.
Start with a controlled AirWatch pilot
A fully functional 30-day free trial provides a useful structure for testing enrolment, renewal and revocation with a representative device mix. Include corporate handsets, BYOD endpoints and devices expected to work offline. Measure successful issuance, renewal lead time, administrator effort and application access rather than focusing only on initial deployment speed.
Package comparisons should account for the certificate authority, identity integration, support model and compliance requirements. Review customer stories from organisations with comparable remote-work patterns, and ask an Australian reseller to quote in Australian dollars with GST identified. Runbooks should also use the dd/mm/yyyy date format to prevent ambiguity when local teams coordinate support across states and countries.
Begin the trial with agreed success criteria, named certificate owners and a rollback plan. Use the results to finalise profiles and permissions, then schedule a production review after the first renewal cycle. Contact AirWatch sales with the tested design, device count and required outcomes so the proposal reflects operational requirements rather than a generic package.