> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/e/endpoint-security.md). # Endpoint Security The practice of securing endpoints or entry points of end-user devices such as desktops, laptops, and mobile devices from being exploited by malicious actors and campaigns. Endpoint security refers to the practice of protecting network entry points -- including end-user devices, servers, and API endpoints -- from unauthorized access and malicious activity. In the traditional IT sense, this involves securing laptops, desktops, and mobile devices with antivirus, encryption, and access controls. In the context of APIs, endpoint security focuses on protecting API endpoints from threats such as injection attacks, credential stuffing, data exfiltration, and denial-of-service attacks. This includes implementing authentication, input validation, encryption in transit (TLS), and monitoring for anomalous request patterns. API gateways serve as a centralized enforcement point for endpoint security. They can validate incoming requests, strip malicious headers, enforce content-type restrictions, and block suspicious traffic before it reaches backend services. In serverless architectures, where backend functions are stateless and ephemeral, the gateway is often the primary layer of defense. Web Application Firewall (WAF) rules can be applied at the gateway to protect against common attack vectors. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/e/endpoint-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.