SwiftID
SwiftID strengthened security and visibility across its Azure platform.
In a one month engagement, Vectorise worked with SwiftID to improve monitoring, automate security work and restructure part of its cloud environment.
Australian owned. Forward deployed engineers based in Australia.
- The problem
- The team needed a clearer view of service health and stronger controls as the platform developed.
- The work
- Vectorise brought 47 application services under centralised monitoring and migrated 300 Azure resources as part of the wider engagement.
- The outcome
- The team gained a more consistent way to monitor and manage its environment, supported by documented engineering changes.
- Client
- SwiftID
- Industry
- IT services and SaaS
- Platform
- Microsoft Azure
- Engagement
- One month
- Delivered
- Documented changes, in SwiftID’s own environment
In our one month engagement with Vectorise they raised the bar on how we operate, monitor and secure our platform, shipping a months-long migration in days and making manual security and operational work disappear.
The results.
What the engagement delivered, as counted at the time. These are the scope of the work, not a measure of uptime.
- Services monitored
- 47
- Application services brought under centralised monitoring during the one month engagement.
- Resources migrated
- 300
- Azure resources migrated and re-architected as infrastructure as code, as part of the wider engagement.
- Metrics aggregated
- 209
- Core resource metrics flowing into one observability layer, in place of manual log queries.
The estate, after the work
The platform’s resources as one observed system around a monitoring core, with telemetry flowing inward.
The picture illustrates the change in operating practice. It is not a live dashboard and it is not a measure of availability.
What changed, and why it mattered.
Four changes over the one month engagement, each tied to the operating problem it addressed.
What prompted the work.
- Preparation for certification
- Upcoming certification milestones created the moment to modernise the Azure platform and harden the network. The work described here is preparation. No certification is claimed on this page.
- Limited visibility
- Metrics were spread across environments with no unified view, which made it harder to stay on top of platform health and to catch issues early.
- Manual security work
- Security scanning and patching were manual and time consuming. The team wanted a more proactive, automated approach to stay ahead of vulnerabilities.
47
application services monitoredCentralised monitoring.
A clearer view of service health across environments.
Shared dashboards, automated workbooks and health endpoints across all 47 application services, per environment. 209 core resource metrics feed one view of the platform, replacing the manual log queries the team relied on before.30
repositories under automated scanningAutomated security scanning.
Less manual security work, with evidence that can be reviewed.
Vulnerability detection and policy enforcement across 30 repositories and their pipelines, backed by security auditing and automated reporting. Scanning and patching that were manual, recurring tasks now run automatically.300
Azure resources migratedMigration and re-architecture.
A cloud environment structured for the next stage of growth.
The Azure resources in one environment were migrated and re-architected into a hub and spoke network with VPN only access, orchestrated as infrastructure as code. 27 pipelines and 22 repositories moved with them.Network access controls.
Stronger controls as the platform developed.
Network segmentation, a VPN gateway and role based access control (RBAC) boundaries now govern access to the environment, and developer access stays auditable. These controls reduce exposure. They do not remove risk, and segmentation is not the same as complete isolation.
How a Vectorise engagement hands over is described in our Ways of Working.
Read Ways of WorkingHave a similar challenge?
- ProblemVectorise’s Accelerator SolutionRun ReliablyUnderstand service health, improve incident response and build confidence in production.Explore Run Reliably
The team needed a clearer view of service health and stronger controls as the platform developed.
Talk to a Director.
Tell us what your team is trying to achieve and what is getting in the way. We will contact you during Sydney business hours to arrange a short conversation. If there is a fit, we will agree the next scoping step.
Prefer email? [email protected]