6.5.3 Securing the API Figure 6-142 Security definitions -1 A key benefit of using IBM API Connect to create and manage the API is the fact that you can  add security to the API. Instead of giving the responsibility to the API developer, you can have  a central location where you can enforce certain security policies that are applied globally  regardless of the actual API back end and how it was implemented. In this case we have added API key validation with Client Id and Client Secret. But APIC  supports other options, including OAuth, which is a common approach in the API world, and  is described in a later section. See Figure 6-142 on page 264. To enable the security definitions that are specified in 6.5.3, “Securing the API” on page 264,  you use the Security Tab. There, you have the opportunity to check which definitions that you  want to use as part of the security policies. In this case we have enabled both. See  Figure 6-143. 264  Accelerating Modernization with Agile Integration