Securing a proxy

This page applies to Apigee and Apigee hybrid.

View Apigee Edge documentation.

API security involves controlling access to your APIs, guarding against malicious message content, accessing and masking sensitive encrypted data at runtime, protecting your backend services against direct access, and other important safeguards.

OAuth home

Get links to introductory topics, examples, and how-to topics.

Using SAML policies

Get an overview of Apigee's support for SAML, along with a pointer to the policy you'll need.

Data-masking and hiding

Learn how to mask sensitive data such as credit card numbers or health information.

Last-mile security

Learn how to protect yourself against threats to your backend resources.

API keys

Get an introduction to the working of API keys, the simplest form of app-based security.

Content-based security

Learn about the Apigee policies you can use to protect your APIs against content-carried threats.

Key Value Maps and property sets

Store data that shouldn't be hard-coded in your API proxy logic for retrieval at runtime, such as credentials, private keys, or tokens

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025年10月29日 UTC.