The Required Software Policy is designed to distribute and install software to the endpoints in your organization. You can deploy software to an unlimited number of systems by uploading an installation binary and setting the package name and version number, providing an installation command, and setting a patching schedule.
Required software policies require a package name, version number, and installation command to properly execute on the system.
- The package name is used to identify if the software package has been installed on the endpoint. The name in the policy must match the installed name otherwise the associated devices will show as non-compliant in the Automox Console.
- The version number is required to guarantee compliance. The version number in the policy must match or exceed the version number of the software package otherwise the associated devices will show as non-compliant in the Automox console.
- The installation command is a script containing the necessary command(s) used to install the software package on the endpoint. It is necessary that the installation commands use silent or quiet mode in order to remove the need for user input and maximize the automated capacity of the Automox service.
Currently, the required software policy automatically populates the package name, version number, and installation command for the following installation binaries.
- MSI (Microsoft Windows installer package)
- .deb (Debian Software package)
- .rpm (RPM Package Manager)
When an installer of one of these types is uploaded to the Automox platform, we inspect the installer and pre-populate these fields with values found inside the installation package. We also provide a script in the installation command field. Before the system sets these values, you are prompted to accept the installation.
Working with Other Types of Installers
For .exe, .pkg, .dmg and other installer types not listed above, follow these steps to ensure you can populate the package name and version number fields for the required software policy:
- Use the command line to install the software package locally and check the package name and version number.
- Enter the software package name and version number in the correct fields on the Create Policy page.
- The commands used to install the software package can be used as a guide for the creation of the installation script.
Facing growing threats and a rapidly expanding attack surface, understaffed and alert-fatigued organizations need more efficient ways to eliminate their exposure to vulnerabilities. Automox is a modern cyber hygiene platform that closes the aperture of attack by more than 80% with just half the effort of traditional solutions.
Cloud-native and globally available, Automox enforces OS & third-party patch management, security configurations, and custom scripting across Windows, Mac, and Linux from a single intuitive console. IT and SecOps can quickly gain control and share visibility of on-prem, remote and virtual endpoints without the need to deploy costly infrastructure.
Experience modern, cloud-native patch management today with a 15-day free trial of Automox and start recapturing more than half the time you're currently spending on managing your attack surface. Automox dramatically reduces corporate risk while raising operational efficiency to deliver best-in-class security outcomes, faster and with fewer resources.