Operating System, Application and Network Hardening Resources

image_pdfimage_print

Information Technology is becoming more challenging these days, hence IT Security is a key area when it comes to Operating Systems, Applications and Networking.

The process of securing an operating system is referred to as “hardening” or at times as “lock down” It is important to an organization’s security because it reduces the chances of attack. Issues come up because various operating systems require different hardening processes within a data center. For example, a system administrator may have deep expertise in one operating system but may possess limited or even no expertise with the other operating systems. System administrators also have a task of ensuring that each server remains locked down consistently to avoid vulnerabilities.

Most of the IT Administrators will have difficulties finding the properly defined set of Hardening guides. To overcome the such issues, Center for Internet Security (CIS) has published well defined and detailed hardening guides to the public (FREE). 

https://nvd.nist.gov/ncp/repository

With the above repository, you will get the change to download all the hardening guides on Windows OS, Mac OS, Linux OS, Applications, Network devices & etc.

For the ease of access, i have attached two common hardening guides as below;

Permanent Device Loss (PDL) and All-Paths-Down (APD)

image_pdfimage_print

There is a new storage-related feature, VM Component Protection (VMCP), that protects virtual machines from possible storage issues.

There are two different types of methods that can be managed by VMCP:

PDL: It occurs when the storage array issues a SCSI sense code indicating that the device is unavailable (for example, a failed LUN).

APD: Usually, related to an underlying storage/networking issue, different from a PDL because the host doesn't have enough information to determine if the device loss is temporary or permanent.

The below URL will provide all the necessary information to drill down the issue and the resolution steps;

https://kb.vmware.com/s/article/2004684

[source: VMware]