What is at stake
Nobody notices the platform until it stops.
A headquarters runs on a few dozen platforms that nobody thinks about until one of them stops: the directory, the mail system, the databases under the mission applications, the virtual servers under everything else. Each has to be current, redundant, and authorized, at every classification level the mission uses.
Meanwhile the mission keeps adding cloud services and applications on top. Each new one has to federate to the right identity, land on an approved platform, and be supported by someone who can restore it. The work is to keep the whole environment current without anyone noticing the change.
What we do
From the directory to the mission application to the dashboard.
Run the platforms
Windows Server and Active Directory, Group Policy, DNS, Exchange and SharePoint, file and print, and secure enterprise mail with gateways, spam filtering, archive journaling, and global address book synchronization across networks.Run the databases
SQL Server high-availability clusters and SQL, Oracle, Sybase, and MySQL application databases across classification levels, with replication, synchronization, and failover on virtual and physical servers.Virtualize and protect
VMware and virtual desktops, Citrix, storage, backup, and failover at primary and alternate sites. Standard images documented to the customer's baseline, and restores performed to prove the recovery, not just the backup.Operate in the cloud
AWS including classified regions, Azure and Microsoft 365, identity federation and conditional access with Microsoft Entra ID, bring-your-own-key encryption, and infrastructure as code so changes are version-controlled and repeatable.Build and run mission applications
Salesforce, SharePoint, .NET, Azure, and Kubernetes mission applications, Jira and Confluence workflow automation, and CI/CD pipelines built with the static and dynamic testing our security assessors require.Show leaders live data
Power BI dashboards with drill-down on direct queries, compliance heat maps that integrate patching, vulnerability, and baseline data, and AI-assisted summaries for the people who read them.How we do it
Current, redundant, and proven to recover.
A restore is the only proof of a backup
Every platform has a documented baseline image and a backup that has been restored from. Disaster recovery is validated by performing it, against recovery time and recovery point objectives agreed with the customer.Preventive maintenance by checklist
Disk and memory, dormant accounts, patch and firmware currency, STIG compliance, backup completion, agent health, certificates and passwords, high-availability features: checked and recorded as they happen, so the program is audit-ready at any time.Security and records in the workflow
Authorization artifacts kept current as the platform changes, security considerations entered at design review, and records obligations enforced during engineering rather than retrofitted at delivery.Dashboards that query the source
Direct connections to the operational databases, deployed on redundant servers, so leadership reporting survives peak demand and never shows a stale extract.Technologies we work in
The tools our people run today.
Listed by product so an evaluator can match us to a requirement and a candidate can find a role. Tools are named; the environments they run in are not.
Platforms and virtualization
- VMware
- Citrix
- Windows Server
- Linux and Unix
- Oracle Database Appliance
- Docker
Databases
- SQL Server HA clusters
- Oracle
- Sybase
- MySQL
Cloud and automation
- AWS, including classified regions
- Azure and Microsoft 365
- CloudFormation
- Ansible
- OctoDNS
Messaging and collaboration
- Exchange
- SharePoint
- Cisco Secure Email (IronPort)
- Jira and Confluence
Applications and data
- Salesforce
- .NET
- Kubernetes
- Power BI
- Azure OpenAI
- Microsoft Copilot
- SitScape
Storage, backup, and identity
- NetBackup
- Cohesity
- Brocade
- Spectra Logic
- DFS-R
- Microsoft Entra ID
- ADFS
- PKI
- BYOK key management
In practice
Where this has already been done.
Described without identifying the customer, as our release policy requires.
References for this work go to contracting officers and teaming partners on request. Request past performance
Careers
The people who do this work.
Systems, database, and virtualization administrators, cloud and identity engineers, developers, and data analysts, cleared to the level the program requires.
