Reader small image

You're reading from  Defending APIs

Product typeBook
Published inFeb 2024
PublisherPackt
ISBN-139781804617120
Edition1st Edition
Right arrow
Author (1)
Colin Domoney
Colin Domoney
author image
Colin Domoney

Colin Domoney (BSc. MSc. CSSLP, CEH) is an API Security Research Specialist and Developer Advocate with deep expertise in the development of secure software. As VP of AppSec, he took on the challenge of securing software on a large scale and running the global AppSec program at Deutsche Bank. At Veracode, as an evangelist, he produces countless webinars, and blog posts, and speak globally at conferences. Currently, he has embraced the challenge of securing APIs with 42Crunch where he has produced the API industry's first security maturity model and contributed to numerous webinars, talks, and blogs. Currently, he is working on the industry's first defensive API developer training course. He is also the curator of the APISecurity weekly newsletter.
Read more about Colin Domoney

Right arrow

Ownership of API security

Your API security strategy cannot exist in isolation from your organization’s API business and development strategy. As a security leader, you must understand the other stakeholders responsible for API strategy and delivery to ensure that your security strategy aligns with their objectives.

Ownership of APIs tends to vary from one organization to another, and there is no hard and fast rule regarding how it is assigned. In the Further reading section, there is a reference to a blog post from MuleSoft that describes a typical pattern for API ownership; we will use this to frame our discussion. This is shown visually in Figure 13.1:

Figure 13.1 – API ownership model

Figure 13.1 – API ownership model

There are three main API owners in this model:

  • IT-owned APIs: This ownership model aligns most closely with traditional IT systems where the IT department wholly owns the resources. These are core services such as infrastructure provisioning or...
lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Defending APIs
Published in: Feb 2024Publisher: PacktISBN-13: 9781804617120

Author (1)

author image
Colin Domoney

Colin Domoney (BSc. MSc. CSSLP, CEH) is an API Security Research Specialist and Developer Advocate with deep expertise in the development of secure software. As VP of AppSec, he took on the challenge of securing software on a large scale and running the global AppSec program at Deutsche Bank. At Veracode, as an evangelist, he produces countless webinars, and blog posts, and speak globally at conferences. Currently, he has embraced the challenge of securing APIs with 42Crunch where he has produced the API industry's first security maturity model and contributed to numerous webinars, talks, and blogs. Currently, he is working on the industry's first defensive API developer training course. He is also the curator of the APISecurity weekly newsletter.
Read more about Colin Domoney