Skip to content

W-23435636 EME scanner read policy GA jh - #502

Merged
JennyHajee merged 14 commits into
W-23612601-EME-MS2026-08-R1-grfrom
w-23435636-eme-scanner-api-read-policies-ga-jh
Aug 5, 2026
Merged

W-23435636 EME scanner read policy GA jh#502
JennyHajee merged 14 commits into
W-23612601-EME-MS2026-08-R1-grfrom
w-23435636-eme-scanner-api-read-policies-ga-jh

Conversation

@JennyHajee

Copy link
Copy Markdown
Contributor

…and read policy creds

@JennyHajee
JennyHajee requested a review from a team as a code owner July 14, 2026 02:22
JennyHajee and others added 10 commits July 13, 2026 21:26
Document where users can view read policies imported by Amazon API Gateway, Google Apigee, Azure API Management, and Kong scanners so governance checks are easier to validate. Add practical guidance on what appears in the Policies tab and what affects visibility when scanner scopes or runs are incomplete.

Co-authored-by: Cursor <cursoragent@cursor.com>
Comment thread modules/ROOT/pages/exp-scanners-prerequisites-reference.adoc Outdated
@glenn-rodgers-sf
glenn-rodgers-sf changed the base branch from latest to W-23612601-EME-MS2026-08-R1-gr July 28, 2026 18:53
:keywords: scanners, providers, add scanner, scanner configuration, workflow, anypoint platform, security scanning

A scanner is the configured link between the system and a supported cloud provider that lets discovery jobs find services—such as APIs, agents, and MCP servers—and register them in the right *Portfolio* catalogs. Scanners enable automated discovery so your catalogs stay current without manual registration. Configure a scanner once to turn on discovery for a provider, then extend it as your organization adds catalogs or enabled features.
A scanner is the configured link between the system and a supported cloud provider that lets discovery jobs find services—such as APIs, agents, and MCP servers—and register them in the right *Portfolio* catalogs, and to discover and read policies from API configurations. Scanners enable automated discovery so your catalogs stay current without manual registration. Configure a scanner once to turn on discovery for a provider, then extend it as your organization adds catalogs or enabled features.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A scanner is the configured link between the system and a supported cloud provider that lets discovery jobs find services—such as APIs, agents, and MCP servers—and register them in the right *Portfolio* catalogs, and to discover and read policies from API configurations. Scanners enable automated discovery so your catalogs stay current without manual registration. Configure a scanner once to turn on discovery for a provider, then extend it as your organization adds catalogs or enabled features.
A scanner is the configured link between the system and a supported cloud provider. Discovery jobs use scanners to find services—such as APIs, agents, and MCP servers—and register them in the right *Portfolio* catalogs, and to discover and read policies from API configurations. Scanners enable automated discovery so your catalogs stay current without manual registration. Configure a scanner once to turn on discovery for a provider, then extend it as your organization adds catalogs or enabled features.

@JennyHajee
JennyHajee merged commit ad52ab7 into W-23612601-EME-MS2026-08-R1-gr Aug 5, 2026
2 checks passed
@JennyHajee
JennyHajee deleted the w-23435636-eme-scanner-api-read-policies-ga-jh branch August 5, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants