Vorpcel / Solutions / Protect endpoints
Many breaches use flaws that already had a fix. The hard part is knowing which of thousands of findings to fix first, and getting the update installed without breaking anything. Vorpcel keeps the whole cycle in one place, from the inventory to the confirmed patch.
At a glance
A scanner can report thousands of critical findings in a medium-sized company. Most will never be exploited, and a few are being used by attackers this week. Without that difference, teams spend their time on the wrong ones and the list never gets shorter.
Then comes the second problem: the fix. Updates are applied by another team, with another tool, on a schedule nobody in security controls, and the only way to know whether a flaw is gone is to scan again and compare spreadsheets.
The list is ordered by real-world risk, so the team knows which fixes to install this week instead of staring at thousands.
Packages that the distribution already patched without changing the version are not reported, so the team stops chasing fixes that are already there.
The agent reports from wherever the machine is, so remote laptops are covered without a VPN or a network scanner.
Updates run only inside the maintenance window of each group of machines, and only for the findings you chose.
Browsers, office suites and developer tools on Windows are updated from verified vendor installers, not only the operating system.
Every update is recorded per machine with its result, and reports show what was fixed, when and where.
The same cycle repeats every week, and each step happens in the same console.
One agent lists the system, every package and program, open ports and container images on each machine, without a network scanner or stored passwords.
Each vulnerability is checked against the vendor's own fixes and ranked by real-world risk, so the first page of the list is the work that matters this week.
Install operating system updates and updates for about 200 common Windows programs from the console, only inside the maintenance window of each group of machines.
The finding closes on its own when the next scan sees the new version, and reports show what was fixed, when and on which machines.
Each finding is checked against the fix published by the vendor of the system, so a package that was already patched by the distribution is not reported. The order then considers how the flaw is used in the real world and how important the machine is to you.
Some flaws cannot be fixed right away. Accept a finding with a reason and an end date. When the date passes, it comes back on its own.
Many breaches start with a weak setting, not a missing patch. Each machine is checked against CIS benchmark recommendations for its operating system.
On machines that run containers, the agent reads the images stored locally and reports their vulnerable packages, so a server and the containers it runs are reviewed together.
No. The agent reads the machine from the inside and sends the inventory over HTTPS. There is no scanner to place in each network and no administrator password stored anywhere.
Updates run only inside the maintenance window of each group of machines, and only for the findings you chose. The result of each update is recorded, and a failure is reported with its reason.
It can, for the operating system and the common Windows programs it covers. If you keep another tool, Vorpcel still confirms on its next scan whether each fix was installed.
The first ranked list appears within minutes after the agent is installed on a machine.
Install the agent on a few machines with one command and the first ranked list appears within minutes.