{"id":17140,"date":"2023-10-04T12:46:25","date_gmt":"2023-10-04T11:46:25","guid":{"rendered":"https:\/\/staging2022.42crunch.com\/?page_id=17140"},"modified":"2024-04-29T14:39:37","modified_gmt":"2024-04-29T13:39:37","slug":"api-inventory-security","status":"publish","type":"page","link":"https:\/\/staging2022.42crunch.com\/api-inventory-security\/","title":{"rendered":"API Inventory"},"content":{"rendered":"\n\n\t\t

\n\t\t\tAPI Inventory\n\t\t<\/h1>\n\t\t\t

Understanding where your APIs are<\/p>\t\t\n\t\t\t\n\t\t\t\t\t\t\tAPI Inventory Datasheet\n\t\t\t\t\t<\/a>\n\t\t\t\t\"DevSecOps-API\n\t

The old adage of ‘you can’t protect what you can’t see’ applies perfectly to API security. As the number of APIs grows exponentially, fueled by business demand, it is increasingly difficult for the security teams to maintain visibility of what APIs exist and what risks they expose. Consequently,\u00a0 if an organization does not have up-to-date API inventory under version control, it could be at risk for things like shadow or zombie APIs, or unauthorized access to user data and Account Takeover (ATO) through the API. When older API versions are not properly retired or locked down, they may have security holes that malicious actors can exploit. By keeping an accurate inventory of APIs and using good version control, organizations can greatly reduce the risk of cyber attacks like these.<\/p>\n

\n\t\tKey elements of secure API inventory include: \n\t<\/h2>\n\t