Corporate Software Inspector, often called CSI or Secunia CSI, was a business tool for finding vulnerable software and managing security patches. Secunia launched it in 2008 as a scanning engine that checked the patch status of applications. Over the years it grew into a wider vulnerability and patch management product. In 2018, Flexera renamed it Software Vulnerability Manager (SVM).
That history matters if you are looking at an old CSI setup. The CSI name belongs to the older product, while newer Flexera guides use the SVM name. Features, system requirements, and support dates can differ from one release to the next, so the exact version always counts.
What Was Corporate Software Inspector?
CSI was a vulnerability and patch management tool for IT and security teams in organizations that needed to manage software across multiple computers. Tools designed for these business environments are commonly part of enterprise software. It checked business computers for installed software, compared what it found with known security issues, and helped teams plan updates. Flexera’s 2018 release notes say it covered Microsoft and third-party products on Windows, Mac OS X, and Red Hat Enterprise Linux.
Third-party software was a big part of its value. A company might keep Windows current through Patch Tuesday but still have an old PDF reader or Java install on a few laptops. Windows updates will not fix those programs, and that is the kind of gap CSI was built to find.
How Corporate Software Inspector Worked
CSI moved from discovery to verification in five steps.
1. Scan for Installed Software
CSI used scanning methods to identify installed products and plugins. Understanding the difference between applications and software helps explain what the scanner was looking for. Agent-based setups used a local agent to collect information from target computers. The exact scanning method depended on the product edition and setup. Flexera’s release notes describe these scans as non-intrusive, and they aimed to identify installed products and plugins. The result was a list of what each machine had and which version it ran. That list often shows uneven results, such as one employee on a current browser and another several releases behind.
How the Scanner Identified Software
CSI’s 2018 release notes describe non-intrusive scans that identified installed products and plugins. Later SVM technical guides explain the detection process in more detail. For example, Windows scanning can use file names and metadata, macOS scanning can read application property-list files, and RHEL scanning can check installed packages. These methods help identify software even when a simple application list does not show the full picture.
2. Match Versions to Vulnerability Data
After CSI knew the product and version, it compared them with vulnerability research from Secunia. Version matters because a flaw may affect some releases of a program but not others. A correct match tells the team whether a computer is truly exposed.
3. Review and Prioritize
A single scan can turn up many problem programs. Advisory details help a team see which product is affected and what the issue is. The final order of work still depends on the company’s systems, business needs, and security policy.
4. Prepare and Deploy Patches
CSI grew beyond scanning to help teams package updates. Flexera’s notes mention patch packages and links to Microsoft WSUS and SCCM for deployment. Teams still had to review, approve, and schedule each update, because finding a patch is not the same as installing it.
5. Verify the Results
A follow-up scan shows whether the software was updated and which computers still need work. Reports and dashboards help teams track open items and share progress with other departments.
Key Features of Corporate Software Inspector
The features below describe what CSI was documented to do. Exact options varied by release.
Software Inventory and Vulnerability Assessment
CSI gave IT teams a view of the applications across their computers and tied each product and version to known vulnerabilities. This is most useful on large networks, where departments run different programs in different versions. A plain list of installed programs would not show risk, and the vulnerability link is what added that.
Secunia Vulnerability Intelligence
Secunia Research supplied the vulnerability data behind CSI. Flexera’s notes describe features such as showing all advisories that affect a product. The scanner finds software on a machine, while the research explains the security issues tied to it.
Third-Party Patch Management
Many security gaps sit in non-Microsoft programs, even on well-maintained systems. CSI connected scan results with patch information so teams could handle updates from many vendors in one process. Flexera’s 2018 notes also mention patch templates and a packaging wizard for building update packages.
Reporting
CSI included a dashboard, and its release notes mention CSV exports of scan data. These help teams see what a scan found, track fixes, and report to managers. The exact reports and fields depend on the version in use.
CSI and SCCM or WSUS
Flexera’s 2018 documentation describes integration with two Microsoft tools. System Center Configuration Manager (SCCM) manages computers, software, and updates across an organization. Windows Server Update Services (WSUS) manages and distributes supported updates.
These tools handle the delivery side of patching. The vulnerability tool finds the problem, and the deployment tool sends the approved update to the affected computers. Supported steps depend on the release and on how the company’s Microsoft environment is set up.
Operating System Support: What to Check
Flexera’s CSI 2018 notes list Windows, Mac OS X, and Red Hat Enterprise Linux. Even so, support is not one simple list. Server requirements, agent requirements, and console requirements can each be different, and they can change by edition and release.
Old requirements age quickly. A February 2018 CSI cloud release note, for example, listed Internet Explorer 11 or higher for the console. Do not copy details like that into a plan for a newer SVM release. Check the official guide for the exact edition and version first.
Corporate Software Inspector vs. Antivirus Software
The two tools do different jobs, and one does not replace the other.
| Tool | Main job |
|---|---|
| CSI / SVM | Finds vulnerable software and supports patch work |
| Antivirus software | Detects, blocks, or removes malware |
| Patch deployment tool | Sends approved updates to computers |
For example, antivirus may block a harmful file. CSI could flag an old browser with a known flaw. A deployment tool then helps install the update that fixes it.
Is Corporate Software Inspector Still Available?
Flexera announced the change in April 2018 and made it effective with the May 2018 release. Its stated reason was that the old name no longer matched how the product had grown. Flexera continued documenting the product as Software Vulnerability Manager after the rename. Older CSI installations still need to be checked against their own release and support records.
Flexera lists CSI and SVM releases separately and gives each one its own support dates. Some older releases are past those dates. Cloud and on-premises editions are also tracked on their own.
CSI vs. SVM at a Glance
| Area | Corporate Software Inspector | Software Vulnerability Manager |
|---|---|---|
| Name | Original Secunia product name, launched in 2008 | Flexera’s name from the May 2018 release |
| Guides | Older CSI guides and release notes | Later SVM guides and release notes |
| Support | Depends on the exact CSI release | Depends on the edition and release |
What to Check If You Still Run CSI
- Find the exact product name, edition, and version you have.
- Look up that release in Flexera’s lifecycle records.
- Review the matching server and agent requirements.
- List the integrations your team uses, such as SCCM or WSUS.
- Ask Flexera about upgrade or migration options.
Flexera keeps these records on its Software Vulnerability Manager lifecycle page.
What to Consider Before Replacing an Old CSI Installation
Start by deciding which parts of the old workflow you still need. A replacement may have to do more than find vulnerable programs.
- Software coverage: Can it find the programs your teams actually use, including uncommon ones and those installed outside standard folders?
- Vulnerability data: Where does the data come from, and how does the tool match products and versions? A wrong match leads to a wrong decision.
- Patch workflow: Does it only report problems, or can it also build, approve, and deploy fixes?
- Integrations: Does it work with the endpoint and update tools you already run? Confirm this for the exact release, not just from an old guide.
- Reporting: Can it show which computers are affected, what was patched, and what is still open?
- Support and licensing: What are the support period, update policy, cost, and upgrade path?
Frequently Asked Questions
What does Secunia CSI stand for?
It stands for Secunia Corporate Software Inspector. People shortened it to CSI.
What replaced Corporate Software Inspector?
Flexera renamed it Software Vulnerability Manager in 2018. Later guides and release notes use the SVM name.
Was Corporate Software Inspector an antivirus program?
No. It focused on finding vulnerable software and supporting patch work. Antivirus tools focus on malware.
Did CSI scan third-party applications?
Yes. Flexera’s notes say it covered both Microsoft and non-Microsoft products. That let teams look past operating system updates.
Does a vulnerability scan fix problems on its own?
No. A team still has to review each finding, choose an update, deploy it, and check the result.
Conclusion
Corporate Software Inspector helped businesses find vulnerable applications and manage the work of fixing them. It linked software discovery with Secunia research and patch workflows, which went well beyond a basic inventory list.
Flexera later renamed it Software Vulnerability Manager, but old CSI releases have their own features and support dates. If you manage one, start with the exact version, then check the matching lifecycle and technical guides before you upgrade, migrate, or replace it.
You Might Also Like:
How to Create Short AI Videos That Make a Joke or Punchline Work
Lines on Your Monitor: Causes and How to Fix Them
I’m Emma Rose, the founder of Punstation. I cover technology, digital trends, business, and online tools, creating practical guides and thoughtful reviews to help readers understand their options and make informed decisions. For more on how I approach my content, see our Editorial Standards.