{"id":5779,"date":"2024-10-15T09:00:00","date_gmt":"2024-10-15T14:00:00","guid":{"rendered":"https:\/\/www.darkreading.com\/vulnerabilities-threats\/llms-are-new-type-insider-adversary"},"modified":"2024-10-15T09:00:00","modified_gmt":"2024-10-15T14:00:00","slug":"llms-are-a-new-type-of-insider-adversary","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/10\/15\/llms-are-a-new-type-of-insider-adversary\/","title":{"rendered":"LLMs Are a New Type of Insider Adversary"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

Today, security teams are <\/span>treating large language models (LLMs)<\/a><\/span> as a vital and trusted business tool that can automate tasks, free up employees to do more strategic functions, and give their company a competitive edge. However, the inherent intelligence of LLMs gives them unprecedented capabilities like no other enterprise tool before. The models are inherently susceptible to manipulation, so they behave in ways they aren’t supposed to, and adding more capabilities makes the impact of that risk even more severe.<\/span><\/p>\n

This is particularly risky if the LLM is integrated with another system, such as a database containing sensitive financial information. It’s similar to an enterprise giving a random contractor access to sensitive systems, telling them to follow all orders given to them by anyone, and trusting them not to be susceptible to coercion.<\/span><\/p>\n

Because LLMs lack critical thinking capabilities and are designed to just respond to queries with guardrails of limited degrees of strength, they need to be treated as potential adversaries, and security architectures should be designed following a new “assume breach” paradigm. Security teams must operate under the assumption that the LLM can and will act in the best interest of an attacker and build protections around it.<\/span><\/p>\n

LLM Security Threats to the Enterprise<\/h2>\n

There are a number of security risks LLMs pose to enterprises.<\/a><\/span> One common risk is that they can be jailbroken and forced to operate in a way they were not intended for. This can be accomplished by inputting a prompt in a manner that breaks the model’s safety alignment. For example, many LLMs are designed to not provide detailed instructions when prompted for how to make a bomb. They respond that they can’t answer that prompt. But there are certain techniques that can be used to get around the guardrails. An LLM that has access to internal corporate user and HR data could conceivably be tricked into providing details and analysis about employee working hours, history, and the org chart to reveal information that could be used for phishing and other cyberattacks.<\/span><\/p>\n

A second, bigger threat to organizations is that LLMs can contribute to remote code execution (RCE) vulnerabilities in systems or environments. Threat researchers <\/span>presented a paper<\/a><\/span> at Black Hat Asia this spring that found that 31% of the targeted code bases \u2014 mostly GitHub repositories of frameworks and tools that companies deploy in their networks \u2014 had remote execution vulnerabilities caused by LLMs.<\/span><\/p>\n

When LLMs are integrated with other systems within the organization, the potential attack surface expands. For example, if an LLM is integrated with a core business operation like finance or auditing, a jailbreak can be used to trigger a particular action within that other system. This capability could lead to lateral movement to other applications, theft of sensitive data, and even making changes to data within financial documents that might be shared externally, impacting share price or otherwise causing harm to the business.<\/span><\/p>\n

Fixing the Root Cause Is More Than a Patch Away<\/h2>\n

These are not theoretical risks. A year ago, a vulnerability was <\/span>discovered in the popular LangChain framework<\/a><\/span> for developing LLM-integrated apps, and other iterations of it have <\/span>been reported recently.<\/a><\/span> The vulnerability could be used by an attacker to make the LLM execute code, say a reverse shell, which would give access to the server running the system.<\/span><\/p>\n

Currently, there aren’t sufficient security measures in place to address these issues. There are content filtering systems, designed to identify and block malicious or harmful content, possibly based on static analysis or filtering and block lists. And Meta offers <\/span>Llama Guard<\/a><\/span>, which is an LLM trained to identify jailbreaks and malicious attempts at manipulating other LLMs. But that is more of a holistic approach to treating the problem externally, rather than addressing the root cause.<\/span><\/p>\n

It’s not an easy problem to fix, because it’s difficult to detect the root cause. With traditional vulnerabilities, you can patch the specific line of code that is problematic. But LLMs are more obscure, and we don’t have visibility into the black box that we need to do specific code fixes like that. The big LLM vendors are working on security, but it’s not a top priority; they’re all competing for market share, so they’re focused on features.<\/span><\/p>\n

Despite these limitations, there are things enterprises can do to protect themselves. Here are five recommendations to help mitigate the insider threat that LLMs can become:<\/span><\/p>\n

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

    Enforce the privilege of least privilege:<\/span><\/span> Provide the bare minimum privilege needed to perform a task. Ask yourself: How does providing least privilege materially affect the functionality and reliability of the LLM?<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

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

    Don’t use an LLM as a security perimeter: <\/span><\/span>Only give it the abilities you intend it to use, and don’t rely on a system prompt or alignment to enforce security.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

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

    Limit the LLM’s scope of action:<\/span><\/span> Restrict its capabilities by making it impersonate the end user.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

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

    Sanitize the training data and LLM output and the training data:<\/span><\/span> Before using any LLM, make sure there is no sensitive data going into the system, and validate all output. For example, remove XSS payloads that are in the form of markdown syntax or HTML tags.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n

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

    Use a sandbox:<\/span><\/span> In the event you want to use the LLM to run code, you will want to keep the LLM in a protected area.<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n<\/ol>\n<\/div>\n

    The <\/span>OWASP Top 10 list for LLMs<\/a><\/span> has additional information and recommendations, but the industry is in the early stages of research in this field. The pace of development and adoption has happened so quickly that threat intel and risk mitigation haven’t been able to keep up. Until then, enterprises need to use the insider threat paradigm to protect against LLM threats.<\/span><\/p>\n

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

    Today, security teams are treating large language models (LLMs) as<\/p>\n","protected":false},"author":12,"featured_media":5780,"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-5779","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\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=1800%2C1013&ssl=1",1800,1013,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=1800%2C1013&ssl=1",1800,1013,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/llms-are-a-new-type-of-insider-adversary.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\/10\/llms-are-a-new-type-of-insider-adversary.jpg?fit=1800%2C1013&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5779","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=5779"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5779\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/5780"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=5779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=5779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=5779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}