This is an interesting list and a conversation worth having as we all plan for the future of mobile data.
Please review your environments and patch accordingly.
This is an interesting read – both the article and the draft provided by Microsoft – concerning patch development and an organization’s commitment to address bugs based on severity and defensive layers. I commend Microsoft for their willingness to release this draft and seek public / industry comments.
Read this article carefully. It appears to be a discussion of how a bank survived a cyber attack and is working to become stronger through lessons learned. The article discussed how preventative controls limited the attack and mitigated the losses. It even discusses two new lines of defense the bank intends to deploy – reaching out to the international community for guidance, and reviewing current cybersecurity frameworks to improve internal processes. What is buried in the last lines of the article is the scariest piece of information about the bank that is largely overlooked. The current existing cybersecurity regulations for the bank dates to 1993. Yes, you read that correctly – 1993.
Due diligence is not revisiting your cybersecurity plan once every couple of decades. Almost every modern security framework discusses at least an annual review with additional reviews any time a new, significant threat is discovered or when a significant change is deployed within the organization. Kudos to Chile for taking steps to modernize, but it never should have taken this long.
This is a wonderful illustration of the process that many of us should consider working through – how does a particular threat framework map to our existing security framework. In this situation, the author is attempting to map the ATT&CK framework to the CIS Critical Controls, but this exercise could just as easily have involved NIST or FFIEC or another framework. Consider the value of exploring and recognizing your strengths and weaknesses in a more real-time sense.