API World 2023: Bringing together API, AI, and Secrets security
Tags: security, api, ai, cybersecurity
Published: 2023-11-20 16:31:27

When most people think of Santa Clara, they immediately think of the [San Francisco 49ers](https://www.49ers.com/tickets/suites/?ref=blog.gitguardian.com), as that is where their stadium sits. They might also think of [California's Great America](https://www.cagreatamerica.com/?ref=blog.gitguardian.com), an amusement park that has been keeping folks entertained since the 1970s. Given how many tech companies have headquarters there, including Advanced Micro Devices, Intel, and Nvidia, many people think of it as an important part of Silicon Valley. For a few thousand who gathered there in late October, it will always be associated with API and AI advancements, thanks to [API World 2023](https://apiworld.co/?ref=blog.gitguardian.com). 

This year's event was colocated with [AI Dev World](https://aidevworld.com/?ref=blog.gitguardian.com), bringing together practitioners from both, highly related realms. It makes sense as the largest innovations in the artificial intelligence and large learning model, LLM, space over the last few years have involved API integrations to services like [OpenAI's ChatGPT](https://platform.openai.com/docs/guides/gpt?ref=blog.gitguardian.com) and [IBM Watson](https://www.ibm.com/watson?ref=blog.gitguardian.com). It seems that developing any AI means also means building and maintaining an API as well. 

[![](https://lh7-us.googleusercontent.com/L8HubJ-VcZRtbMOyobYs8gQgkadrhSxk1y3-oIb8_WKUqfACTh7mH61qXgFk5CsY0RxMKW2h7TKQewWa0su3sNYU-tdpgTPH46ml_p9_bnfjAvMCPIbfuIOe3sVEJv8dlK2wrqv48rnunCCgdCNn-w)](https://twitter.com/Shivs_k/status/1717334001797730678?ref=blog.gitguardian.com)
*#APIWorld #AIDevWorld*

There were over 70 speakers throughout the 3-day event. That is far too much to cover in depth here in this article, but here are some of the highlights.

The future of AI is unpredictable
---------------------------------

In their opening keynote session, "Navigating Invention, Innovation & Disruption in the Age of AI," [Khurram Latif](https://www.linkedin.com/in/khurram-latif-3078853/?ref=blog.gitguardian.com), from Deloitte Consulting and [Justin Hiza](https://www.linkedin.com/in/justin-hiza/?ref=blog.gitguardian.com) and [Michaël Chaize](https://www.linkedin.com/in/mchaize/?ref=blog.gitguardian.com) of Shutterstock laid out some of the more exciting ways they are collaborating on products powered by AI and shared some thoughts about the future of the technology.

Shutterstock is a stock content company selling premade images, videos, audio, and many other types of media. They have been using AI for years, primarily to classify and suggest related content on their site automatically. Generative AI used for personalizing content is a new effort for them, though, and that is why they partnered with Deloitte.

They demonstrated some examples, including their "Magic Brush" feature that allows users to customize existing content based on provided prompts. For example, if someone needs to wear an "on-brand color" hat, you simply tell the AI what you want, and it will do the placement, lighting correction, and all the other touch-ups in seconds.  The other was a custom text creator that derives a theme from a given image, customizing the requested text to match the image's theme perfectly. 

The team shared some of the more significant takeaways they learned while embarking on many AI projects together.  One of the most prominent lessons is we are entering a world without all the answers. They concluded it is basically impossible to guess what will work and what will not with AI even a year out.  If you overdesign something early, you will spend a lot of time trying to make AI do something it might not be capable of.

What does work is prototyping fast and getting feedback as rapidly as they can.  Starting with the customer goals and objectives, they empowered their engineering to deliver proof of concepts on any idea they thought moved towards those ends; ultimately, the customer is the one who judges if an AI innovation is valuable.

[![](https://lh7-us.googleusercontent.com/Rg95Bqyhtu4nTvUW03wZAVK-K8SpEoq3L34gHofjSW__tLboWynr2Ei_3aBPRE-6XGXTuxe-Qlse7lNT5ICz87bmYzcBcRmINFX1D2HmpUbgbCbYURDwap00qp5mDsHtR7QNnaeP_NeFW7kDeQgnPQ)](https://mastodon.social/@mcdwayne/111291614490105245?ref=blog.gitguardian.com)
*#APIWorld has officially kicked off With the first workshop from #ShutterStock and Deloitte presenting: "Navigating Invention, Innovation & Disruption in the Age of AI" by Khurram Latif, Justin Hiza and Michaël Chaize*

Good API security takes more than tools
---------------------------------------

API World participants had the pleasure of seeing three different talks from [Isabelle Mauny, Field CTO and co-founder at 42Crunch](https://www.linkedin.com/in/isamauny/?ref=blog.gitguardian.com), that build upon one another.  In all of these sessions, she stressed the importance of API security and how we can use the recently updated [OWASP API Top 10](https://owasp.org/www-project-api-security/?ref=blog.gitguardian.com).

In her talk on the first day of the event, "Common API Security Pitfalls: Learning from Others' Mistakes," she walked us through several security incidents involving APIs. One case involved a microbrewery whose API allowed hackers to print thousands of free beer coupons. Another case involved a university's physical access control system that did not implement any authorization, meaning anyone with an account could gain admin rights. She summed up the main problem throughout all her examples was that API security was an afterthought. While starting our security work with the [general OWASP Top 10](https://owasp.org/www-project-top-ten/?ref=blog.gitguardian.com) is good, we need to focus on the issues presented by the [OWASP API Top 10](https://owasp.org/www-project-api-security/?ref=blog.gitguardian.com) earlier in the process, at the design phase. 

Later, she dug into the larger cultural issues of API security. In her session "Why So Many API Security Solutions Have Failed to Deliver," Isabelle said that one of the biggest concerns is that most organizations have no idea how many APIs they manage. This stems from a lack of governance, a lack of training, and a tendency just to try to solve problems with tech tools. Good governance means building and communicating documentation on how to build APIs properly, report they exist, and secure them.

[![](https://lh7-us.googleusercontent.com/gosZJR61bKeYkDzzIk6fjsrc9AJK13V_W24YHQYN6iryrSBivmQ2jte3HsRzHxL9GGiTLq031grCoSfVEALAbX-3TY_wg5mT8VHLpsaYLAwoBwtU7aWq_rIhJQRkK3z27G17KOvk-UWgksuY5RoL5g)](https://mastodon.social/@mcdwayne/111292054287203451?ref=blog.gitguardian.com)
*"Common API Security Pitfalls: Learning from Others' Mistakes" by Isabelle Mauny at [#APIWorld](https://mastodon.social/tags/APIWorld?ref=blog.gitguardian.com)*

Securing your API is not your app's concern
-------------------------------------------

The recommendation to address API security by leveraging the OWASP API Top 10 came up again in the session "Research Revelations: Emerging API Threats & How to Mitigate Them," from [Patrick Sullivan, CTO of Security Strategy at Akamai](https://www.linkedin.com/in/patricksully/?ref=blog.gitguardian.com). He stressed that traditional application security, which is what OWASP traditionally focused on, relied on WAF rules and gateways. But API threats are different. APIs can be used to scrape data, help attackers map a network, and make denial-of-service attacks easier to execute. 

Another major difference in security approaches is that while application security is something taken care of by the application, the app assumes no duty to secure the API. He said the most common thing he hears when confronting someone about an API vulnerability is, "I thought the app would take care of that." This is especially true when it comes to authorization. While traditional apps bake in logic, allowing a request to succeed only if certain conditions are met, most APIs allow anyone who can authenticate to make almost any call. It is up to the developer to handle this aspect of security via the code. 

[![](https://lh7-us.googleusercontent.com/rQBa_3UPZdPmMe9YLcI6V_c28z44duhOolz_4zZceEQELDOFzg5GBpr2mnAukXgwl9kN5JiGsx9hl3uuVJTyKRlWRCoyJnHN-wmanflU05CJ3OnC_rS74_VWOPmnoxp5LCUTBTigkxmjR31VE2l3Eg)](https://mastodon.social/@mcdwayne/111303578107723143?ref=blog.gitguardian.com)
*Research Revelations: Emerging API Threats & How to Mitigate Them by Patrick Sullivan, Chief Technology Officer of Security Strategy at Akamai at #APIWorld*

Don't just follow the happy testing path
----------------------------------------

In his session "Why You Should Hack Your Own APIs," [Dan Barahona, Founder of APIsec](https://www.linkedin.com/in/rdbarahona/?ref=blog.gitguardian.com), said one of the biggest issues with API security is a lack of testing. APIs are often tested to ensure they do what you want them to do, but all too often, Dan says, we don't test if it does what it's not designed to do. We tend to follow a happy path when we need to instead think like an attacker and see what unexpected behavior we can force. 

He talked through several recent examples of API security gone wrong, mostly from logic flaws associated with authorization. The companies he mentioned included [Coinbase](https://www.securityweek.com/coinbase-pays-250k-market-nuking-security-flaw/?ref=blog.gitguardian.com#:~:text=Cryptocurrency%20exchange%20Coinbase%20has%20shelled,bitcoins%20they%20didn't%20own.), where a researcher was paid $250K for finding a flaw that could have ended the company; [Duolingo](https://www.malwarebytes.com/blog/news/2023/08/2-6-million-duolingo-users-have-scraped-data-released?ref=blog.gitguardian.com), where guessing user IDs led to 2.6 Million users' emails and names being stolen; and [Peleton](https://techcrunch.com/2021/05/05/peloton-bug-account-data-leak/?ref=blog.gitguardian.com), where an authorization flaw caused a leak of over 4 Million users' data.

Our job in API security should be to find the flaws before they get into the wild. We heard that starting with the OWASP API Top 10 is good, but he said more consistent and automated testing of unintended uses is required. He concluded his talk by quickly laying out his own best practices top 10 that they use in the free courses at [APISEC University](https://www.apisecuniversity.com/?ref=blog.gitguardian.com):

1\. Start with Governance.\
2. Know your API ecosystem.
3. Get Security and Development teams talking.
4. API Documentation is non-negotiable
5. Train API developers and owners on API security
6. Centralize API management
7. Don't trust anything; validate everything.
8. Don't rely on UIs for security.
9. Authentication is NOT authorization. Authorization must happen in the logic.
10. Automate pre-production testing whenever possible. 

[![](https://lh7-us.googleusercontent.com/AH1YKzJAucpmRqSf9XVR6zeMpY44zp8ZhZ1liUHuV0cLBuEH8mjdjzeIychoIZlrzVM8S-2S0bpuWuuRqEl0A3a6Xvo6oPtP77T1C0hpdYbTNFg3ixpSTxbrhZMGWpDG-s9CXOoqu79RBfYCIfbXcA)](https://mastodon.social/@mcdwayne/111297691362751991?ref=blog.gitguardian.com)
*"Why You Should Hack Your Own APIs" from Dan Barahona, Founder of APIsec at #APIWorld*

The need for an API security purple team
----------------------------------------

An application is like an octopus. This is how [Jeremy Ventura, Director of Security Strategy & Field CISO at ThreatX](https://www.linkedin.com/in/jeremy-ventura-36204676/?ref=blog.gitguardian.com), began his session "Red + Blue = Purple: Strategies around API Security." Like an octopus, there is a central body and head which powers the application. APIs are like each outstretched arm that allows the octopus to move and interact with the world.

The traditional 'blue team' in security is focused on defending that central app, not the arms. Red teams are increasingly focused on getting in through any route they can. As API calls are now responsible for over 80% of web traffic, it is clear this is the new battlefront. We need to meet in the middle and shift the focus to securing and finding weaknesses in our APIs.

Jeremy said one of the largest issues is that most organizations do not know how many APIs they manage. This leads to a world of "zombie APIs" that should have been decommissioned, are unpatched, and still allow calls to be made. He said in an average engagement with a client, they find over 8x the number of APIs they first thought they had.

Aside from the OWASP API top 10, Jeremy said rate limiting and logging need to be addressed for most APIs. He said it is not enough to keep logs; you must actively act on any suspicious activity. The real way we can address these issues is to work together and set policies, train people, and use better testing tools earlier in the development process.  While admitting tech is important, he reminded us always to put people first when solving security concerns. 

[![](https://lh7-us.googleusercontent.com/vvmGceO-PLzcBHcKISBW1Sca5alzNG4H5cRk-61PczCZEMsTP2sciJeesGZOjs53_9xcxRhVeDknNmu5H-exFWcX3A-8EzeVCEbxszfNsPACWN8yc72yJseh2lTAu097cNuOBeBN6zU6SJPlFSAdPQ)](https://mastodon.social/@mcdwayne/111303141916173894?ref=blog.gitguardian.com)
*"Red + Blue = Purple: Strategies around API Security" by Jeremy Ventura, Director of Security Strategy & Field CISO at ThreatX At #APIWorld*

Good security starts with knowing what you have
-----------------------------------------------

Throughout the event, in any session about API or AI security, almost every speaker mentioned the importance of understanding your assets as the first major step on your security journey. After all, you can't defend it if you don't know it is there. This is something I brought up as well in my session "Do you know where your secrets are? Exploring the problem of secret sprawl and secret management maturity" based on the [Secret Management Maturity Model from GtiGuardian](https://blog.gitguardian.com/a-maturity-model-for-secrets-management/). In part of the talk, we walked through how mature organizations not only know where their secrets are, but they can audit and monitor their creation and use through a secret management service such as [Hashicorps' Vault Enterprise](https://www.hashicorp.com/products/vault?ref=blog.gitguardian.com) or [Doppler](https://www.doppler.com/?ref=blog.gitguardian.com). 

It is also important to know what secrets you have in code and other places where they should not be in plaintext. This is where automated secrets scanning comes in. For example, when connecting a repository to [the GitGuardian Secret Detection platform](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com), it will perform a historical scan, letting you know where those secrets exist in your git history. From there it will actively monitor for any new secrets entering the perimeter, alerting you to their whereabouts. 

In secrets management, API security, and AI security, bolting on security after the fact is not an option. We need to address the vulnerabilities enumerated in the [OWASP API Top 10](https://owasp.org/www-project-api-security/?ref=blog.gitguardian.com) earlier in the development lifecycle and stop treating every issue as one that can be solved by tech alone. We also need good governance that creates good processes that people are trained on. We have a long way to go with securing our code and our APIs, but together. By learning from one another, we can find the best path to protect our apps and our customers.