It makes sense that partners(consumers) of our SDK may want to have their VPN entries prefixed with their own signature, rather than the stock 'Guardian Firewall -' prefix on all IKEv2 entries in the default Windows RRAS pbk file.
When implementing this, look into changing from use of default pbk but a hidden pbk that isn't easily tampered with.
It makes sense that partners(consumers) of our SDK may want to have their VPN entries prefixed with their own signature, rather than the stock 'Guardian Firewall -' prefix on all IKEv2 entries in the default Windows RRAS pbk file.
When implementing this, look into changing from use of default pbk but a hidden pbk that isn't easily tampered with.