How to use top down service mapping through SaaS waf/LB

[guykl]

Hi

i have started service mapping, and I get errors on the entry point, and after talking to my architecture team, it seems I have a SaaS waf and LB before I get to the applications.

I tried to skip them, but the IIS server, only accepts the outside dns, so it won’t map unless I go through those applications. 

I was able to find documentation for their api, but i don’t know how to proceed from it, and i can’t find any documentation of how to do so.

any help is appreciated! And thank you in advance 

[shubhamseth]

@guykl 

What to Ask Your Architecture Team

• Which WAF/LB product is being used?
• Does it expose APIs for backend/origin servers?
• Can ServiceNow access those APIs through a MID Server?
• Is there an internal DNS name that resolves directly to the IIS servers?

If you already have API documentation. The next step is usually to build a custom Service Mapping pattern that calls the WAF/LB API and returns the backend IIS servers. Once Service Mapping can identify the relationship between the external endpoint and the backend nodes, the application service can be mapped correctly.

1. Use a Load Balancer Pattern
   • If ServiceNow has an OOB pattern for the technology, configure it and provide the required credentials/API access.
2. Create a Custom Pattern/API Integration
   • If the WAF/LB exposes APIs containing backend pool members, virtual servers, or origin servers, create a custom pattern to query the API and build relationships to the IIS servers.
3. Start Mapping from Infrastructure
   • If the IIS servers are discoverable internally, create the application service using a technical entry point (server, URL, process, or port) and then model the external WAF/LB relationship separately.
4. DNS Resolution Strategy
   • Sometimes an internal DNS record that bypasses the external WAF can be used as the entry point for mapping while still representing the same business application.