Description

Fixes #274

Questions + ideas + notes:

• This doc is coming from Kong Gateway but the text keeps referring to "Kong Gateway and other Kong products". Can we rephrase this and make it a blanket statement without specifically mentioning Kong Gateway, or do we need to consult with someone in eng to make that decision?
• We should mark external links in some way, both in text and in info boxes. The "CVSS" link in this doc is external but there's no way to tell without clicking it.
• This isn't a reference or a landing page; it might actually be the first "concept" I've run into.
• Does this info belong on the dev site? I think yes, because it's no longer just a docs site. On the docs site, I might've said no.

@cloudjumpercat - this would be a good doc to link from the security landing page.

Preview Links

Checklist

• Every page is page one.
• [ N/A ] Tested how-to docs. If not, note why here.
• All pages contain metadata.
• Updated sources.yaml. For more info, review track docs changes
• Any new docs link to existing docs.
• All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
• Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.