What You Don't Log Will Hurt You - Webinar with Jeremy Snyder and John Tobin of Virtual Guardian
You'll find useful content about AI & API security, the cybersecurity landscape, news, events and much more updated regularly here.
We’ve talked before about the importance of logging in your AI and API security posture. But what happens when organizations fail to log their interactions adequately? And what can you do within your own organization to prevent this? Explore all this and more with the latest webinar from FireTail.
If you prefer to be notified of new posts via email, simply subscribe to our blog below.
Many application developers are still grappling with the integration challenge. Microsoft’s Graph API attempts to solve this problem, however, their solution comes with its own drawbacks.
We're excited to announce the release of our latest State of API Security 2024 report! With the rapid adoption of microservice-based architectures, cloud-native solutions, containerization, and AI, the API attack surface is expanding faster than ever.
In February of 2021, Postman launched a public API platform where developers could collaborate to build software. Now in 2024, Postman has the largest collection of public APIs. Naturally, this makes it a prime target for attackers.
The cloud might be a popular talking point, but the edge of the cloud – where APIs and distributed computing intersect – is the true unsung hero of modern cloud application development and deployment. Today, we’re going to look at APIs at the edge of modern cloud applications.
In the travel sector, securing a competitive edge is vital. In a hyperconnected industry, where demand fluctuates, pricing is dynamic and customers have endless options, efficient and well-secured APIs can make a huge difference.
The Cambridge Analytica Data Scandal led to the collapse of the company, court cases and massive fines for Meta. It highlighted the massive impact that technology was having on society, politics and democracy. Now, almost a decade later, we take a look at how a poorly configured API started it all.