Security & Identity

Because every sign-in goes through one identity provider, keeping NIM available was treated as the first requirement of the design, and NIM runs redundant in production. Nesnet signs in to its own cloud portal with NIM too, so any outage hits Nesnet's team first, and they are first to respond.

Inspection starts in detect-only mode, and no traffic is cut during that period. A signature that trips on legitimate traffic is excluded or set to alert-only in that application's profile, and prevention starts only once tuning has settled.

No, you don't. The directory connector links to your AD, users keep signing in with their AD password, and password changes in NIM are written back to AD.

Inspection happens in the network layer, right next to the server and at the gateway, so your traffic isn't routed to a distant appliance. What happens to traffic beyond the engine's capacity at peak times is a separate setting, agreed with you in the protection workshop.

Not at all. The connector reaches NIM outbound only, over an encrypted connection on port 443, and no inbound rule is added to your firewall.

A firewall decides which address may pass on which port. Intrusion detection and prevention looks inside the traffic that's allowed: if a request on port 443 carries an attack, only this layer sees it.