An airport identity check and a government cloud deployment seem to belong to different universes. One involves a person, a document, perhaps a fingerprint. The other involves servers, security controls, and permission to operate. Yet both reach the same awkward moment: someone must decide whether the evidence is good enough to proceed. Telos Corporation works in that moment.
- Xacta organizes cyber risk, controls, and compliance evidence.
- Identity services support traveler enrollment and aviation worker vetting.
- Secure networks and messaging keep sensitive operations connected.
That connection helps explain a company whose portfolio can otherwise resemble a government technology catalog. Telos sells software and services for institutions that need security to be demonstrable, repeatable, and maintained. Its customers include federal agencies, enterprises, and airports. The interesting product, across those markets, is the machinery that makes a security decision possible.
The permission problem
Consider a hypothetical agency moving an application into the cloud. Engineers can provision infrastructure quickly. Approval requires another kind of construction: identifying applicable security requirements, documenting their implementation, testing controls, recording deficiencies, and assembling evidence for a decision. The application and its authorization package travel together, at different speeds.
Xacta, Telos’s cyber governance, risk, and compliance platform, tackles that second journey. Xacta 360 provides assessment and authorization workflows. Xacta.io brings security data together. Xacta.ai helps generate control statements and test procedures and answer questions about project data. The portfolio combines workflow, evidence, and analysis around a specific bureaucratic reality.
There are alternatives. Archer and ServiceNow offer risk management platforms with overlapping capabilities. Telos’s pitch concentrates on cyber risk and the federal authorization process. A buyer choosing between them should examine the actual work: frameworks, deployment constraints, integrations, and the people who approve a system. A long feature list cannot answer those questions by itself.
Do the work once. Keep the evidence alive.
The useful idea inside Xacta is control inheritance. A cloud provider or an internal shared service may already implement controls used by many applications. Repeating the same documentation separately wastes effort and creates opportunities for contradictions. Xacta lets systems inherit relevant implementations and tracks changes made by the provider.
Imagine three applications using one shared identity service. Evidence about that service can be reused where it applies; each application still owns its particular configuration and responsibilities. The saving comes from recognizing the common work. Telos has worked with AWS and Microsoft Azure on cloud compliance automation built around that distinction.
The limitation is equally practical. Inheritance only helps when the provider actually supplies the relevant control. Stale evidence remains stale when copied. And an AI-drafted implementation statement cannot establish that an implementation exists. Telos labels its AI time-saving claims as pilot results, with outcomes varying by system size, scope, and complexity. Buyers should preserve that qualification.
The receipt matters
Telos applies a related discipline to communications. Its Automated Message Handling System, AMHS, routes messages by content, supports security markings, provides certified delivery, and maintains searchable archives. A message can arrive at the relevant desktop with a record of its journey. For an institution issuing consequential instructions, that record has operational value.
On the identity side, Aviation Channeling Services handles background-check submissions for airport and airline workers. Telos says the service is used by more than 100 airports and airlines. Hawaii continued its relationship across five airports in July 2026, following work together since 2018. These checks concern the people behind airport operations, a different population from vacationers seeking shorter security lines.
Travelers encounter Telos through TSA PreCheck enrollment. By October 2025, it had passed 500 enrollment locations, including Office Depot and OfficeMax stores. Office Depot advertises new enrollment at $85 for five years. The distribution insight is pleasingly ordinary: a regulated service can become more convenient by occupying a place people already visit.
“TSA PreCheck removes friction from air travel, and enrolling in this trusted traveler program should be just as seamless.”John B. Wood, chairman and CEO · October 2025
A recovery with real costs
Telos’s own history contains plenty of rebuilding. Its official account begins in 1971 and includes telemetry and image-processing work for Voyager. During the 1990s, it moved resources toward network and information security. Xacta launched in 2000. Common-stock trading on Nasdaq began in November 2020; the IPO ultimately raised about $292.6 million gross, including the overallotment.
More recently, pruning became explicit. Under its 2024 restructuring, Telos discontinued selected solutions or components and reduced its workforce. It wrote off $6.4 million in previously capitalized software associated with that decision. That is a tangible cost of development that stopped earning its place in the portfolio.
Revenue rose from $108.3 million in 2024 to $164.8 million in 2025. Telos still recorded a $36.5 million net loss. The distinction matters when considering a vendor selling long-lived systems: growth and sustainable economics answer different questions.
Recent awards show the work arriving. In September 2026, HHS awarded Telos an 18-month, $13.7 million task order for the full Xacta suite plus integration, migration, training, and cybersecurity services. In October, a three-year, $13.5 million Air Force award covered license maintenance, training, and cyber services. Neither figure is a software sticker price.
Copy the method, not the paperwork
There is a useful lesson here even for a team that never buys Telos. Identify shared controls. Assign an owner. Reuse validated evidence where it belongs. Make changes visible to everyone depending on it. Then spend the recovered time testing the responsibilities that remain yours.
Telos’s culture page says more than a quarter of employees have stayed at least a decade. That continuity fits work in which institutional memory matters. The purchase makes most sense when authorization complexity, overlapping requirements, and repeated assessments justify a dedicated system. For a small organization with simple obligations, the process may deserve simplification before it deserves software.