La seguridad de las APIs implica controlar el acceso a tus APIs, protegerlas frente al contenido de mensajes maliciosos, acceder a datos sensibles cifrados y enmascararlos en el tiempo de ejecución, proteger tus servicios de backend frente al acceso directo y otras medidas de protección importantes.
Almacena datos que no deben estar codificados en la lógica de tu proxy de API para recuperarlos en el tiempo de ejecución, como credenciales, claves privadas o tokens.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-11 (UTC)."],[[["\u003cp\u003eThis documentation covers security aspects for both Apigee and Apigee hybrid platforms.\u003c/p\u003e\n"],["\u003cp\u003eApigee API security encompasses access control, protection against harmful content, sensitive data handling, and backend service security.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation offers guides on various security methods, including OAuth, SAML, data masking, last-mile security, API keys, and content-based security.\u003c/p\u003e\n"],["\u003cp\u003eLearn how to use Key Value Maps and property sets to dynamically store sensitive information, such as credentials or tokens, for API proxy runtime retrieval.\u003c/p\u003e\n"]]],[],null,["# Securing a proxy\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nAPI security involves controlling access to your APIs, guarding against malicious message\ncontent, accessing and masking sensitive encrypted data at runtime, protecting your backend\nservices against direct access, and other important safeguards.\n\n### [OAuth\nhome](/apigee/docs/api-platform/security/oauth/oauth-home)\n\nGet links to introductory topics, examples, and how-to topics.\n\n### [Using SAML policies](/apigee/docs/api-platform/security/saml)\n\nGet an overview of Apigee's support for SAML, along with a pointer to the policy you'll\nneed.\n\n### [Data-masking and hiding](/apigee/docs/api-platform/security/data-masking)\n\nLearn how to mask sensitive data such as credit card numbers or health information.\n\n### [Last-mile security](/apigee/docs/api-platform/security/last-mile-security)\n\nLearn how to protect yourself against threats to your backend resources.\n\n### [API keys](/apigee/docs/api-platform/security/api-keys)\n\nGet an introduction to the working of API keys, the simplest form of app-based security.\n\n### [Content-based security](/apigee/docs/api-platform/security/content-based-security)\n\nLearn about the Apigee policies you can use to protect your APIs against content-carried\nthreats.\n\n### [Key\nValue Maps](/apigee/docs/api-platform/cache/key-value-maps) and [property sets](/apigee/docs/api-platform/cache/property-sets)\n\nStore data that shouldn't be hard-coded in your API proxy logic for retrieval at runtime, such\nas credentials, private keys, or tokens"]]
