{"id":4361,"date":"2024-07-08T09:00:00","date_gmt":"2024-07-08T14:00:00","guid":{"rendered":"https:\/\/www.darkreading.com\/cyber-risk\/deconstructing-security-assumptions-to-ensure-future-resilience"},"modified":"2024-07-08T09:00:00","modified_gmt":"2024-07-08T14:00:00","slug":"deconstructing-security-assumptions-to-ensure-future-resilience","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/07\/08\/deconstructing-security-assumptions-to-ensure-future-resilience\/","title":{"rendered":"Deconstructing Security Assumptions to Ensure Future Resilience"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

COMMENTARY<\/span><\/span><\/p>\n

Second of two parts. (Read Part 1: “<\/span><\/span>Stress-Testing Our Security Assumptions in a World of New & Novel Risks<\/a><\/span>.<\/span>“)<\/span><\/span><\/p>\n

Achieving security in a future of “unseen until it’s too late” threats forces us to look beyond the endless cycles of discover and patch, identify and neutralize, and sense and respond, to build resilience by stress-testing assumptions and preparing for a future in which those assumptions have become unsustainable.<\/span><\/p>\n

By deconstructing fundamental assumptions, we can proactively plan for, and thus begin to achieve, future resilience. A basic framework for this work includes the following steps:<\/span><\/p>\n

\n
    \n
  1. \n
    <\/span><\/p>\n
    \n

    Identify a basic assumption and its associated dependencies.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

  2. \n
    <\/span><\/p>\n
    \n

    Stress-test the assumption through theoretical compromise or degradation, envisioning a future state in which the assumption is no longer valid.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

  3. \n
    <\/span><\/p>\n
    \n

    Identify the risks that emerge in that future state.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

  4. \n
    <\/span><\/p>\n
    \n

    Develop mitigations for those risks.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n<\/ol>\n<\/div>\n

    This approach is theoretical, and thus prone to error. Unrestrained imagination can lead to more fiction than reality. But the only way to prepare for unforeseen risks is to imagine the unimaginable and consider ways to mitigate those risks today, while we have the opportunity. <\/span><\/p>\n

    To illustrate this process, let’s look at some basic assumptions.<\/span><\/p>\n

    Enterprise-centric Cybersecurity<\/h2>\n

    We know that the enterprise is where most data is created, processed, managed, transmitted, and stored, thus, we assume the enterprise is the focal point of cybersecurity. Similarly, most critical infrastructure is built, operated, and maintained by enterprises \u2014 which include both public and private sector organizations \u2014 so efforts to secure the world’s central nervous system must be focused there. It remains a reasonable assumption. The <\/span>NIST Cybersecurity Framework<\/a><\/span>, <\/span>CIS Critical Security Controls<\/a><\/span>, and <\/span>ISO 2700 series guidelines<\/a><\/span> all focus on the enterprise. Even the <\/span>National Cybersecurity Strategy<\/a><\/span> assumes the primary role of the enterprise. Personal health information, protected by the Health Insurance Portability and Accountability Act (HIPAA), is assumed to be managed and protected by healthcare payers and providers. <\/span><\/p>\n

    But what if the forces of the information age and the AI revolution weaken the corporation, which gets eroded or replaced by networks of independent, distributed workers (which is already happening via remote work and the gig economy), or a growing public sector, or something else we don’t yet imagine?<\/span><\/p>\n

    There are numerous risks in this scenario. We are already seeing this with remote workers, who use insecure home or public networks. The human “attack surface” is already the most vulnerable part of the enterprise; the erosion of the enterprise will likely further expose humans to cyber exploitation.<\/span><\/p>\n

    One of the cybersecurity benefits of an enterprise-centric approach has been that experience and expertise can be concentrated where cybersecurity is “happening.” If the corporate structure erodes, so too could the associated ability to implement well-developed security controls (e.g., CIS Controls).<\/span><\/p>\n

    Mitigations could include increased efforts to make humans more cybersecure in settings outside the enterprise, such as in education, through public awareness and alerting protocols (similar to the 911 system for police or emergency medical response). While some of these are already happening, the focus, emphasis, and responsibility would shift away from corporations to public and nonprofit entities.<\/span><\/p>\n

    Data Ownership<\/h2>\n

    We generally assume that humans create data through decision-making, designing, building, organizing, and managing. It naturally follows that humans own (and must protect) that data. Even the ownership of machine-generated data is tied to the human owners of those machines.<\/span><\/p>\n

    But what if the generation of data shifts to non-human entities? We already see that happening with <\/span>generative AI (GenAI)<\/a><\/span>. For now, the GenAI data sphere remains relatively small and limited in scope. But we are not far from autonomous GenAI, which may be deployed to routinely and proactively generate new data, make recommendations, and even take steps to manage processes previously controlled by humans. <\/span><\/p>\n

    Given that GenAI platforms require vast computing resources and robust<\/span> large language models (LLMs)<\/a><\/span> to be useful, it’s likely that the most popular platforms are shared resources, much as <\/span>cloud computing<\/a><\/span> has become. Who, then, would own and protect that GenAI-produced data? What would prevent the generation and dissemination of data that might be flawed, or even dangerous?<\/span><\/p>\n

    Mitigating future risks could involve the implementation of secure-by-design principles to scale security controls as GenAI platforms “grow.” Proper segmentation could enable discrete users to leverage shared foundational LLMs, while preventing data leakage beyond that user’s scope (work that is already underway). There is also talk of AI “kill switches” to serve as emergency stop mechanisms to ensure human primacy. GenAI is an area where security considerations must be deliberated from the outset.<\/span><\/p>\n

    The Way Forward<\/h2>\n

    This basic framework for stress-testing assumptions is a way to build future resilience. Chief security officers (CSOs) and cybersecurity professionals must look carefully at the assumptions that they take for granted. Because, as reasonable as they may be, they have a shelf life. And we know from experience that the more basic the assumption, the more devastating the compromise. <\/span><\/p>\n

    Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    COMMENTARY Second of two parts. (Read Part 1: “Stress-Testing Our<\/p>\n","protected":false},"author":12,"featured_media":4362,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-4361","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=1800%2C1013&ssl=1",1800,1013,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=1800%2C1013&ssl=1",1800,1013,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/07\/deconstructing-security-assumptions-to-ensure-future-resilience.jpg?fit=1800%2C1013&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=4361"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4361\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/4362"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=4361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=4361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=4361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}