For a long time, security patches were not that important, for a few years we notice a shift in perception has occurred. Big companies like Microsoft, Google, and Apple release new security updates on a frequent basis. For Microsoft, there is a “patch Tuesday” every 2nd Tuesday of the month.
If flaws are detected in an already released software they can be patched through a software patch. A patch is thus an adjustment in production software to clean bugs and errors or to create improvements in security.
• Patching of Windows Server installations with an OS version that is still supported by Microsoft.
• Installation and configuration of our own patch management software.
• Determining, installing, and configuring of the patch tiers on the Domain Controller, taking into account the backup timeframes of the different servers in collaboration with the customer’s IT department.
• Follow-up on new vulnerabilities and patches.
• Follow-up on patch planning and patched servers.
• Delivering reports of installed patches, server status, etc.
• If a patch fails, a rollback of the patch or server.
• Initial patch round(s) to get the servers to the latest patch level available.
• Providing backup schedule or taking backups of servers
• Testing of backup restores
Patch management is a process, not a product. Within Auxility this process is based on four steps.
We start with making an inventory of the Windows servers in the environment of the customer which are going to be included in the Patch Management Process (PMP).
2. Analysis, prioritization, and planning
Of course, not all servers have the same function and criticality, which makes it possible to divide the servers into different Tiers and Groups.
After patching the server it may occur that a reboot is necessary to activate the patch. Not every patch on the new Windows servers requires a reboot.
After each patch cycle, we deliver a report with all the servers handled through our PMP and their current status.