Salient Systems: How TechProComp Co-Manages alongside the Internal Team

Executive Summary

Salient Systems is an Austin-based software company and a recognized leader in video surveillance management. Founded in 1995, Salient builds CompleteView VMS and the PowerProtect appliance platform – technology that some of the most demanding organizations in the world rely on to run their physical security operations.

That position carries a particular obligation. A company whose product is security does not get to have a weak network. Salient’s customers evaluate the company itself, not just the software: how the vendor runs its own infrastructure, how it manages vulnerabilities, and whether its operations would survive an outage or an incident.

Salient had internal technical capability – but internal teams at a growing software company are consumed by the product. Network administration, vulnerability management, and infrastructure projects need dedicated, consistent ownership that does not compete with release deadlines.

TechProComp was engaged in a co-managed model: functioning as Salient’s outsourced network administration arm, working alongside the internal team across the entire network. The initial assessment surfaced a significant number of vulnerabilities and configuration mismatches accumulated across the environment. TechProComp systematically remediated them, then shifted the engagement to where it lives today: engineering redundancy and business continuity into every layer of the company’s infrastructure, so that no single failure – hardware, link, power, or site – can take Salient offline.

The result is an environment that matches what Salient’s own product promises its customers: resilient, monitored, and built to keep running.

At a Glance

Client

Salient Systems

Industry

Physical Security / Video Surveillance Software

Location

Austin, Texas

Engagement

Co-managed IT - outsourced network administration, vulnerability remediation, infrastructure projects, redundancy and business continuity engineering

Primary Goal

Bring the network to the standard a security company’s customers expect - then make it resilient enough that nothing takes it down

Outcome

Vulnerabilities remediated across the environment; redundancy and business continuity engineered into every layer of the network

When Your Product Is Security, So Is Your Network

Salient’s platform manages video surveillance for major enterprises, universities, and logistics operations. Customers who trust a vendor with their physical security infrastructure hold that vendor’s own operations to the same standard. The initial TechProComp assessment showed the gap between that standard and reality.

Accumulated Vulnerabilities

Network scanning surfaced a significant number of unpatched and exploitable weaknesses across the environment - the normal sediment of years of growth without dedicated network ownership.

Configuration Mismatches

Inconsistent configurations across network devices - mismatched settings, undocumented changes, and drift between what the network was designed to do and what it actually did.

Product Team Pulled Both Ways

Internal technical staff were absorbed by the product. Network administration competed with release deadlines - and release deadlines won.

Single Points of Failure

Critical paths through the infrastructure depended on individual devices, links, and services. Any one failure could interrupt operations across the company.

No Dedicated Network Ownership

No one’s full-time job was the health of the network itself - monitoring it, documenting it, and driving a remediation and improvement roadmap.

A Customer-Facing Standard

Enterprise customers evaluate their security vendors’ own security posture. The environment had to withstand that scrutiny, not just internal expectations.

Core Problem

A security company’s network had accumulated the vulnerabilities and configuration drift of years of product-first growth - and the internal team had no capacity to fix it without stopping work on the product itself.

Co-Managed, Not Outsourced Away

The model matters. Salient did not hand off IT and walk away - and TechProComp did not replace anyone.

In a co-managed engagement, TechProComp functions as the dedicated network administration arm of the client’s team: same standards, same documentation, same accountability - without the client hiring, training, and retaining that capability internally.

For Salient, that meant TechProComp took ownership of the network layer and infrastructure projects while the internal team stayed focused on the product and the systems closest to it. Work happens when it needs to happen - including after hours, so remediation and cutover work never interrupts business operations.

This is the arrangement Salient described in its own words in an independently verified review: TechProComp filling in as an outsourced network administrator, making the network more secure by finding and fixing important vulnerabilities, responsive and willing to work after hours.

The Mandate

Own the network: administration, monitoring, documentation, and change control
Find and remediate every vulnerability the assessment surfaced
Eliminate configuration drift and bring devices to a consistent, documented standard
Engineer redundancy into every critical layer - no single point of failure
Build business continuity across the company, not just the server room
Execute infrastructure projects without disrupting product work or business hours

From Vulnerable to Resilient

The engagement followed TechProComp’s standard methodology – full assessment and scanning first, then a prioritized project roadmap executed quarter by quarter and reviewed with leadership.

1

Assess and Map

Full network assessment and vulnerability scanning across the environment. Every device, link, and configuration documented. Findings ranked by risk and mapped into a remediation roadmap.
2

Remediate

Systematic elimination of identified vulnerabilities and configuration mismatches - patching, reconfiguration, standardization, and hardening, executed after hours where cutover risk existed.
3

Stabilize and Own

Ongoing network administration established: monitoring, documentation, change control, and a consistent configuration standard maintained across every device.
4

Engineer Redundancy

Project-by-project elimination of single points of failure - redundant paths, failover capability, and continuity design across the company’s infrastructure.
5

Today - Continuity as Standard

Every new project is designed for redundancy and business continuity by default. The network is treated the way Salient’s product treats its customers’ video: it cannot be allowed to stop.

Solution Delivered

Securing the Network

The first mandate was closing the gap the assessment exposed – every vulnerability, every mismatch, across the entire network.

01 / Vulnerability Remediation

Close every finding, in risk order

Full vulnerability scanning across the environment
Risk-ranked remediation roadmap
Patching and firmware standardization
Verification scanning to confirm closure

02 / Configuration Standardization

One documented standard, every device

Elimination of configuration mismatches and drift
Documented baseline for every network device
Change control so drift cannot recur
Hardened configurations across the stack

03 / Network Administration

Dedicated ownership, finally

Continuous monitoring of the environment
Full network documentation maintained
Proactive maintenance and lifecycle planning
After-hours execution to protect business hours

04 / Co-Managed Alignment

One team, two organizations

Internal team freed for product-critical systems
Shared visibility into all changes and projects
Escalation paths defined in both directions
Leadership reviews of roadmap and progress

The Standard

A vendor whose customers include some of the largest enterprises in the world is held to their bar, not its own. The network had to be defensible in a customer’s vendor security review – not just functional on a normal Tuesday.

Engineering for Continuity

With the environment secured, the engagement shifted to its defining theme: redundancy. Every project since has been designed around a single question – what happens when this fails?

01 / Redundant Infrastructure

No single point of failure

Redundant network paths and links
Failover capability for critical devices
Power and connectivity resilience
Elimination of single-device dependencies

02 / Business Continuity Design

The company keeps operating

Continuity requirements built into every project
Recovery priorities documented and agreed
Backup and restoration capability verified
Failure scenarios planned, not improvised

03 / Downtime Prevention

Interruptions engineered out

Proactive replacement before failure
Maintenance windows outside business hours
Monitoring that catches degradation early
Unplanned downtime avoided across the engagement

04 / Project Execution

Improvement without disruption

Infrastructure projects delivered across the company
Cutover work staged and rehearsed
Zero-interruption migration approach
Documentation updated with every change

Design Philosophy

Redundancy is not a project – it is a requirement applied to every project. Each piece of work at Salient is designed so that no single failure of hardware, link, power, or site can stop the business.

The Environment Their Customers Expect

In Their Words

“TechProComp’s service level and responsiveness are impressive.” Salient’s verified review credits TechProComp with making the network more secure by finding and fixing important vulnerabilities – with a team that is responsive, communicative, and willing to work after hours.

Source: verified client review, Clutch.co.

Vulnerabilities Closed

The weaknesses the initial assessment surfaced were systematically remediated – and verification scanning plus ongoing monitoring keep the environment at that standard.

Downtime Avoided

Redundancy engineering and proactive maintenance have kept the business running – interruptions are prevented in design rather than recovered from in crisis.

A Credible Security Posture

A security software vendor can now demonstrate an internal environment consistent with what its own product promises customers.

Product Team Protected

Salient’s internal capability stays pointed at CompleteView and its customers – while the network has a dedicated owner who treats it as the product it effectively is.

Engagement details are summarized for case-study purposes and must be reviewed and approved by the client before external publication.

Before TechProComp vs. After

Area	Before TechProComp	After TechProComp
Network Ownership	No dedicated owner; administration competed with product deadlines and lost.	TechProComp functions as the dedicated network administration arm in a co-managed model.
Vulnerabilities	Significant accumulated vulnerabilities across the environment, unknown until scanned.	Systematically remediated in risk order, with verification scanning and continuous monitoring.
Configuration	Mismatched, undocumented configurations drifting across network devices.	One documented baseline per device, enforced through change control.
Resilience	Single points of failure in critical paths - one device or link could interrupt the company.	Redundant paths and failover engineered layer by layer; no single failure stops the business.
Continuity	Failure scenarios unplanned; recovery would have been improvised.	Business continuity designed into every project, with recovery priorities documented.
Downtime	Exposure to unplanned interruptions across the environment.	Downtime avoided through proactive replacement, monitoring, and after-hours maintenance.
Internal Team	Pulled between the product and the network, serving both poorly.	Focused on the product and product-adjacent systems, with clear escalation to TechProComp.
Customer Scrutiny	Internal environment inconsistent with the standard the product represents.	A posture the company can stand behind in enterprise vendor security reviews.

Network Ownership

Before TechProComp: No dedicated owner; administration competed with product deadlines and lost.
After TechProComp: TechProComp functions as the dedicated network administration arm in a co-managed model.

Vulnerabilities

Before TechProComp: Significant accumulated vulnerabilities across the environment, unknown until scanned.
After TechProComp: Systematically remediated in risk order, with verification scanning and continuous monitoring.

Configuration

Before TechProComp: Mismatched, undocumented configurations drifting across network devices.
After TechProComp: One documented baseline per device, enforced through change control.

Resilience

Before TechProComp: Single points of failure in critical paths - one device or link could interrupt the company.
After TechProComp: Redundant paths and failover engineered layer by layer; no single failure stops the business.

Continuity

Before TechProComp: Failure scenarios unplanned; recovery would have been improvised.
After TechProComp: Business continuity designed into every project, with recovery priorities documented.

Downtime

Before TechProComp: Exposure to unplanned interruptions across the environment.
After TechProComp: Downtime avoided through proactive replacement, monitoring, and after-hours maintenance.

Internal Team

Before TechProComp: Pulled between the product and the network, serving both poorly.
After TechProComp: Focused on the product and product-adjacent systems, with clear escalation to TechProComp.

Customer Scrutiny

Before TechProComp: Internal environment inconsistent with the standard the product represents.
After TechProComp: A posture the company can stand behind in enterprise vendor security reviews.

What Salient Gained

A Dedicated Network Owner: Full-time-caliber network administration - monitoring, documentation, remediation, and projects - without hiring and retaining it internally.

A Defensible Posture: An environment that withstands the scrutiny enterprise customers apply to their security vendors.

Resilience by Design: Redundancy and continuity engineered into every layer, so no single failure can stop the business.

Focus Where It Pays: The internal team’s time flows to the product and its customers - the work only they can do.

What Comes Next

The engagement continues on the same principle it established: every new project – every expansion, every refresh, every migration – is designed for redundancy and business continuity by default. As Salient grows, the network grows with a standing rule already in place: the business does not stop.

The TechProComp Difference

A security company cannot outsource its standards – but it can extend its team. Salient kept its people on the product and gave the network a dedicated owner who found the vulnerabilities, fixed them, and then rebuilt the environment so it cannot be taken down by any single failure. That is co-managed IT done the way it should be: one standard, two teams, zero excuses.

Transformation Delivered

Co-managed network administration established
Full network assessment and vulnerability scanning completed
Complete network documentation built
Risk-ranked remediation roadmap executed
Identified vulnerabilities remediated across the environment

Configuration mismatches eliminated
Documented configuration baseline enforced
Change control established to prevent drift
Continuous network monitoring in place
After-hours execution protecting business operations

Redundant paths and failover engineered
Single points of failure systematically removed
Business continuity designed into every project
Proactive lifecycle and replacement planning
Unplanned downtime avoided across the engagement

Ready to build yours?

Austin HQ: 512-488-1811

Houston: 281-957-0309

San Antonio: 726-222-4912

support@techprocomp.com