The evolution of APIs calls for a drastically different approach to API security. Token-based architecture is the key to many security issues discussed throughout this presentation, which is increasingly prevalent in a world so widely dependent on cloud-based architecture and microservices.
APIs are much more widespread than they used to be and are limited to HTTP requests and JSON objects. Instead, APIs are a vital component of single-page applications and mobile applications as well as traditional websites.
API developers need to ensure these third-party applications interacting with an API are secure, as an API ecosystem is only as secure as its weakest link.
FAPI is a protocol that requires the use of JSON Web Tokens (JWTs) that enable different access levels, from baseline to advanced profiles and permission granting.
Sender-constrained tokens tether a user to the mutual TLS connection between the client and the authorization server. The token-handler pattern is a backend for frontend that solves the bulk of the security issues caused by single-page applications and mobile applications by attaching a simple backend.
Browser-based authorization became popular with the rise of single-page applications and mobile apps. Eliminating the browser from the equation removes virtually all the vulnerabilities.
To make mobile applications more secure, Jacob Ideskog recommends using a feature called attestation, which uses a mobile device’s hardware chip to validate transactions.
By implementing the strategies recommended by Ideskog, you can take full advantage of the exploding API market while ensuring business users and customers are secure.