{"id":9620,"date":"2020-10-07T08:45:13","date_gmt":"2020-10-07T07:45:13","guid":{"rendered":"https:\/\/staging-site.42crunch.com\/?p=9620"},"modified":"2022-09-24T13:23:34","modified_gmt":"2022-09-24T12:23:34","slug":"new-openapi-static-security-audit-in-github-code-scanning","status":"publish","type":"post","link":"https:\/\/staging2022.42crunch.com\/new-openapi-static-security-audit-in-github-code-scanning\/","title":{"rendered":"42Crunch Releases OpenAPI Static Security Audit in GitHub Code Scanning"},"content":{"rendered":"

IRVINE, CA, OCTOBER 7, 2020<\/b> \u2014 <\/span>Today, the API security leader and creator of the industry\u2019s first API Firewall, 42Crunch,<\/span> announced the availability of its <\/span>REST API Static Security Testing<\/span><\/a> with\u00a0 <\/span>GitHub code scanning<\/span><\/a>. By adding 42Crunch to code scanning, developers can include REST API OpenAPI \/ Swagger definitions within static security tests.<\/span><\/p>\n

Most of today\u2019s applications are driven by APIs. The transition to cloud-native architectures, microservices, serverless, single-page, IoT, and mobile applications lead to proliferation of APIs. What used to be components of monolithic applications communicating within a single server are now standalone APIs talking to each other over the network.<\/span><\/p>\n

This significantly expanded the attack area and led to the rise of API attacks. In fact, there\u2019s now not a single week without new high profile API vulnerabilities reported by the popular API security news site <\/span>APIsecurity.io<\/span><\/a>.<\/span><\/p>\n

Gartner estimates<\/span><\/a> that by 2022 APIs will become the most common attack vector.<\/span><\/p>\n

Having direct access to applications\u2019 backend services and databases with sensitive customer data, APIs are a lucrative target. API breaches can have significant business, public image, and financial impact.<\/span><\/p>\n

At the same time, companies now have hundreds if not thousands of APIs. These APIs are constantly changing as teams adopt agile methodologies and continuously iterate over their functionality. Old approaches of manual review and approval processes and static runtime rules can no longer serve as the foundation for securing such complex dynamic systems.<\/span><\/p>\n

The best way to provide cost-effective security for APIs is to \u201cshift-left\u201d and establish security measures across the whole API lifecycle: from design, to development, testing, and run-time protection and ideally doing so automatically without human interaction<\/span><\/p>\n

Available as a GitHub Action, <\/span>REST API Static Security Testing<\/span><\/a> allows users to:<\/span><\/p>\n