Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- The CIS CSC were never intended as a replacement for more encompassing cybersecurity frameworks such as the SP 800-53 or ISO 27001. Instead, they're meant to give businesses a list of tasks that they need to have done to secure their data and the data of their customers. This gives the business's cybersecurity team a solid foundation to build a more tailored approach to their security from, using frameworks like the SP 800-53. To quote CIS, one of the main advantages of the CSC " is that they prioritize and focus a smaller number of actions with a high pay-off, aiming for a “must do first” philosophy."
- With this background in mind, we can take a closer look at Control #15, Wireless Access Control. Working off of CIS CSC v6.1 (because it was far more easily accessible to find PDFs of, and information on), we can see that there are 9 parts to it. With the discussion prompting us to consider authentication protocols such as EAP, and encryption/privacy protocols/standards such as TLS and AES, the important parts of the control #15 to consider are 15.5 and 15.6
- CIS CSC 15.5 states that one should "Ensure that all wireless traffic leverages at least Advanced Encryption Standard (AES) encryption used with at least Wi-Fi Protected Access 2 (WPA2) protection." AES is a really neat standard when it comes to encryption. It was designed by the NIST (yes, the same NIST as the SP 800-53) in 2001. It's a family of ciphers that is a symmetric key algorithm, which is fairly common for encrpyting information.
- Its use is still pretty strongly recommended, as even AES-128 would take billions of years to brute force on current (and predicted) hardware. There have been some sidechannel attacks (attacks which exploit hardware, as opposed to software) that have been successful, however most modern CPUs have adjusted the firmware to account for AES and prevent timing-related sidechannel attacks.
- Implementing CSC 15 also requires that we use authentication protocols such as EAP/TLS. EAP/TLS is widely considered to be one of the most secure EAP standards available, although there are some possible issues that can arise if the user is not aware of the potential pitfalls.
- EAP/TLS does provide protection that I personally consider to be quite important for most users. Most EAP/TLS implementations also require client-side certificates (X.509 Public Key certificates, if you're curious as to which type! It's also used by any protocol that uses TLS, such as SMTP, POP, IMAP, since emails love to use TLS apparently), which means that a compromised password isn't enough alone.
- As with any control that one can possibly think of, Implementing CSC 15 does not minimize all risk. Even implementing all 20 of the CIS CSC wouldn't minimize all risk. Cybersecurity is an ever-evolving field, with both the red and blue sides constantly innovating to find new ways to break into systems and protect those same systems. The CIS CSC, as stated above, is merely a starting point. There are for more comprehensive frameworks designed to cover even more bases, the CIS CSC are meant to have you put out the fire before throw the burnt casserole away.
- I didn't expect to be writing an essay, but I ended up really enjoying reading about the Critical Security Controls, it gave me a lot more insight into the jobs that some of my friends do. To finish it off, I'll list off the NIST SP-800-53 controls that the CIS CSC # 15 can be mapped to.
- AC-18: Wireless Access
- AC-19: Access Control for Mobile Devices
- CA-3: System Interconnections
- CA-7: Continuous Monitoring
- CM-2: Baseline Configuration
- IA-3: Device Identification and Authentication
- SC-8: Transmission Confidentiality and Integrity
- SC-17: Public Key Infrastructure Certificates
- SC-40: Wireless Link Protection
- SI-4: Information System Monitoring
- Seeing the controls just as a list of numbers wasn't sitting right with me. Not having any understanding of what they meant and how they related to the CSC felt odd, almost like there shouldn't be a connection. Now that I can see the human-readable names of the controls, it's easy to connect them to CSC 15, especially taking into account the research I did with regards to 15.5 and 15.6, and how they can connect to IA-3, SC-8, and SC-17.
- References
- https://web.archive.org/web/20160919021105/https://www.cisecurity.org/critical-controls/documents/CSC-MASTER-VER61-FINAL.pdf
- https://www.cisecurity.org/wp-content/uploads/2017/03/Poster_Winter2016_CSCs.pdf
- https://tools.ietf.org/html/rfc4158
- https://en.wikipedia.org/wiki/Extensible_Authentication_Protocol#EAP_Transport_Layer_Security_(EAP-TLS)
- https://en.wikipedia.org/wiki/Advanced_Encryption_Standard
- https://cseweb.ucsd.edu/~kmowery/papers/aes-cache-timing.pdf
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53Ar4.pdf
Add Comment
Please, Sign In to add comment