How to detect and reduce the damage if APIs are compromised? Before one finds out and revoke the develop app

[nathanaw]

A lot of emphasis has been put into authorisation of APIs -- grant types, etc. However, I wish to know what can one put in place to identify and reduce the damage done when an API is compromised.

Other than quota, spike arrest, concurrent rate limit, what can one do to:

1. Quickly identify that a once trusted API is now hijacked/compromised

2. Reduce the damage that these hijacked/compromised API may do before it is identified as hijacked/compromised

Sure, one could pipe the logs to ELK for analysis and alerts when an aberration is detected but does Apigee have any mechanism to address point 1 & point 2?

Thank you.

Nathan Aw (Singapore)

[dchiesa1]

I recommend that you look into the API Monitoring Dashboard.

https://docs.apigee.com/api-monitoring/alerts-notifications

Nathan, you seem to have LOTS of questions.

You would really benefit from a direct engagement with a Customer Success architect.