AI agentide domeenikontroll: Veebijuurdepääsu turvamine AWS Network Firewalliga

3. samm: AWS Network Firewalli lubatud loendi konfigureerimine

Teie domeenikontrolli strateegia tuum seisneb olekuhoidva reegligrupi konfigureerimises AWS Network Firewallis. See reegligrupp määrab teie lubatud loendi – konkreetsed domeenid, millele teie AI agendid on lubatud ligi pääseda. Oluline on lisada domeenikirjetesse juhtiv punkt (.), et sobitada alamdomeene, tagades tervikliku katvuse.

Näiteks, et lubada juurdepääs Wikipediale ja Stack Overflow'le, näeks teie reeglite konfiguratsioon välja umbes selline:

{
  "RulesSource": {
    "RulesSourceList": {
      "Targets": [
        ".wikipedia.org",
        ".stackoverflow.com"
      ],
      "TargetType": "TLS_SNI",
      "GeneratedRulesType": "ALLOWLIST"
    }
  }
}

See konfiguratsioon tagab, et ainult nendele selgesõnaliselt lubatud domeenidele, sealhulgas nende alamdomeenidele, mõeldud liiklus on lubatud läbi tulemüüri. Kogu muu liikluse saab vaikimisi keelata vaikimisi keelamise poliitikaga.

Lisaks SNI-le: sügavuti kaitse lähenemine

Kuigi SNI-põhine filtreerimine on võimas, nõuab AI agentide tõeline nullusaldusarhitektuur mitut turvakihti. Nagu mainitud, lisab AWS Network Firewalli sidumine Amazon Route 53 Resolver DNS Firewalliga veel ühe kriitilise kontrollpunkti. See takistab agentidel blokeeritud domeenide lahendamist DNS-i kaudu, sulgedes tõhusalt potentsiaalse möödahiilimisvektori, kus agent võiks proovida otse IP-aadressiga ühendust luua, kui domeenilahendus pole samuti kontrollitud.

Lisaks tugevdab teie turvalisust teiste turvateenuste, näiteks AWS Web Application Firewalli (WAF) integreerimine HTTP/S-liikluse kontrollimiseks (kui liiklus on teises kihis kontrollimiseks lõpuks dekrüpteeritud) ja identiteedipõhised juurdepääsukontrollid agentide esilekutsumiseks. See mitmekihiline lähenemine on kooskõlas parimate tavadega nullusaldusarhitektuuri loomiseks konfidentsiaalsetele AI tehastele.

Kokkuvõte: Turvalise AI agentide juurutamise võimaldamine

Võimalus kontrollida, millistele domeenidele teie AI agendid pääsevad, ei ole lihtsalt funktsioon; see on ettevõtte AI kasutuselevõtu põhiline turvanõue. Rakendades AWS Network Firewalli koos Amazon Bedrock AgentCore'iga, saavad organisatsioonid detailse kontrolli agentide väljamineva liikluse üle, leevendavad olulisi turvariske, nagu andmete välja filtreerimine ja käsu süstimine, ning täidavad rangeid vastavuskohustusi.

Kuna AI agendid muutuvad üha keerukamaks ja integreeritumaks kriitilistesse äriprotsessidesse, muutub tugev turvaraamistik hädavajalikuks. See lahendus pakub ettevõtetele selget teed AI agentide võimsuse ärakasutamiseks, säilitades samal ajal kontrolli, nähtavuse ja kompromissitu turvalisuse. Selliste arhitektuurimustrite omaksvõtmine on võtmetähtsusega agentuurilise AI operatiivseks muutmisel 1. osa: sidusrühmade juhend ja turvalise, uuendusliku tuleviku edendamisel.

Korduma kippuvad küsimused

Why is domain-level control essential for AI agents browsing the internet?

AI agents with internet access offer powerful capabilities but also introduce significant security risks. Unrestricted web access can lead to unintended data exfiltration to unauthorized domains, exposure to malicious content, or exploitation through prompt injection attacks that trick agents into navigating to harmful sites. Domain-level control, specifically allowlisting, ensures that agents can only access pre-approved websites, drastically reducing the attack surface. This is critical for maintaining data privacy, adhering to regulatory compliance standards, and safeguarding sensitive enterprise information, especially in regulated industries where strict network egress policies are mandatory.

How does AWS Network Firewall enhance the security posture of AI agents using Amazon Bedrock AgentCore?

AWS Network Firewall acts as a crucial layer of defense for AI agents deployed via Amazon Bedrock AgentCore. By routing all outbound traffic from AgentCore Browser through the firewall, organizations can implement granular domain-based filtering rules. The firewall inspects TLS Server Name Indication (SNI) headers to identify destination domains and applies allowlist or denylist policies. This ensures that agents only connect to approved external resources, logs all connection attempts for auditing, and can block access to known malicious domains or undesirable categories, thereby bolstering the overall security and compliance of AI agent operations.

What are the primary challenges addressed by implementing domain-based egress filtering for AI agents?

Domain-based egress filtering addresses several critical challenges for AI agent deployments. Firstly, it mitigates the risk of data exfiltration and unauthorized access by ensuring agents only interact with trusted domains. Secondly, it helps prevent prompt injection attacks, where malicious prompts could instruct an agent to visit harmful or unintended sites, by enforcing an allowlist of approved URLs. Thirdly, it meets stringent enterprise security and compliance requirements, particularly in regulated sectors, by providing transparent control and auditability of agent network interactions. Finally, for multi-tenant SaaS providers, it allows for customized, per-customer network policies, enabling specific domain restrictions based on individual client needs.

Can SNI-based domain filtering completely prevent all unauthorized connections by AI agents, and if not, what are the limitations?

While SNI-based domain filtering is highly effective for controlling web access at the TLS layer, it does have a limitation: it relies on the Server Name Indication field during the TLS handshake. An advanced attacker or a sophisticated agent could potentially resolve a blocked domain's IP address through an uninspected DNS query and attempt to connect directly via IP, bypassing SNI inspection. To address this, a defense-in-depth strategy is recommended. This involves pairing SNI filtering with DNS-level controls, such as Amazon Route 53 Resolver DNS Firewall, which can block DNS queries for unauthorized domains and prevent DNS tunneling, ensuring comprehensive egress control.

What is the typical traffic flow for an AI agent's web request when using AWS Network Firewall for domain control?

When an AI agent within Amazon Bedrock AgentCore initiates a web request, the traffic flow is meticulously controlled. First, the AgentCore Browser, residing in a private subnet, attempts to establish an HTTPS connection. This request is routed to a NAT Gateway in a public subnet, which then forwards it to the Network Firewall endpoint. The AWS Network Firewall inspects the TLS SNI header to identify the target domain. If the domain is on the allowlist, the firewall permits the traffic to pass to an Internet Gateway, which then routes it to the external destination. All return traffic follows a symmetric path back through the firewall, ensuring continuous inspection and adherence to security policies.