Securing Apigee Edge itself

Building Secure APIs are important but Securing Apigee Edge itself is equally important. There are access tokens, private keys in Apigee.

If the gateway itself is compromised, all else is irrelevant.

Other than regular patch updates and reducing attack surface (such as ports), what are other ways to secure the gateway from an end to end perspective?

What kind of hardening could one further do?

Thank you.

Nathan Aw (Singapore)

0 1 179
1 REPLY 1

Some other hardening options you might like to consider:

* Change default passwords:

https://docs.apigee.com/private-cloud/v4.19.01/resetting-passwords

* Configure Apigee to authenticate with a SAML provider that supports/requires multi-factor auth:

https://docs.apigee.com/private-cloud/v4.19.01/installation-and-configuration-saml-edge?hl=en

* Enable TLS for the Web UI & Management API

https://docs.apigee.com/private-cloud/v4.19.01/configuring-ssl-edge-premises?hl=en

* Ingest Management logs into your SIEM