{
    "componentChunkName": "component---src-templates-landings-landing-template-js",
    "path": "/en/landings/dont_let_your_apis_turn_against_you",
    "result": {"data":{"sales_template":{"locale":"en","slug":"dont_let_your_apis_turn_against_you","title_color":"Don't let ","title_white":"Your internal APIs turn against you","description":"Designing and implementing the best functionality for your APIs may be much easier when you do it internally – business and development departments are much closer to each other. But even internal developers rarely give high priority to security, as businesses tend to focus on functionality, UX, and deadlines. As security teams typically have limited influence on the development process, APIs may be vulnerable to multiple attack vectors.\n \nMake sure you investigate these four aspects:\n1.\tControlling API traffic between your internal servers, and between the internal servers and the outside world – including non-public endpoints\n2.\tInspecting API messages based on the content to make sure even approved interactions cannot cause any harm – signatures are not enough\n3.\tSegmenting your microservices architecture to prevent lateral movement of malicious actors between your internal servers\n4.\tEnforcing security schemas to protect against rogue endpoints left in during development","form_title":"Schedule your personal demo","form_image":{"url":"https://balasysmediastorage.blob.core.windows.net/websiteimages/uploads/customer_story_IV_01_44331944a0.jpg"},"list_token":"v","SEO":{"title":"Don't let your APIs turn against you","isIndexable":true,"description":"Even internal developers rarely give high priority to security, as the business focuses on functionality, UX, and deadlines. As security teams typically have limited influence on the development process, APIs may be vulnerable to multiple attack vectors.","keywords":"API, internal, internal APIs, schema, enforcement","preview":null}}},"pageContext":{"locale":"en","slug":"dont_let_your_apis_turn_against_you"}},
    "staticQueryHashes": ["3233329270","3621970722","521397250","585144119"]}