|
|
|
|
|
by yeukhon
3362 days ago
|
|
I didn't follow that discussion closely, so I will avoid the argument here on that subject. Overall, NIST is a good resource for comparison. If you work with government, enterprise security, or compliance, you want to go through NIST. If you have spare time I recommend read https://beta.csrc.nist.gov/publications. NIST is also responsible for running https://nvd.nist.gov/ which is a great asset for finding CVE. |
|
http://nvlpubs.nist.gov/nistpubs/ir/2016/NIST.IR.7621r1.pdf
DISA has the "STIG's" for security configuration:
http://iase.disa.mil/stigs/Pages/index.aspx
The NSA themselves, the Information Assurance Directorate, had guides on hardening various things. There's one for deploying Chrome in the link below that also references STIG on Chrome:
https://www.iad.gov/iad/library/ia-guidance/security-configu...
It would be straight-forward for INFOSEC people to vet the NIST or STIG guides for content accuracy then host that copy on their own sites. Or produce similar guides as some do. Just important to target them at people of low knowledge or competence so they know exactly what they need to do. It's them whose hardware will become part of the next DDOS due to configuration error.