How to use ASM to protect Lync 2013?

R Marc is correct. ASM wouldn't play much against the SIP portions of Lync, and would only potentially protect the Lync web services defined against the front end "External web services" and "Internal web services". Since we'd assume using LTM as the reverse proxy, it may or may not be benefit to use ASM in this instance; especially since any "issues" may not be supported by MSFT until ASM is removed from the config. We are however, certified for reverse proxy by MSFT.

Specific question... Using the LTM as a reverse proxy, Would ASM be a good tool to protect against repeated unsuccessful login attempts, since Lync's lack of SAML compliance means that APM can't do the authentication for us. That authentication doesn't take place until the proxied connection gets all the way to the Lync Front End server that is part of internal AD domain. We have this running in a lab environment, and need to address this security issue prior to going to production.

Specific question... Using the LTM as a reverse proxy, Would ASM be a good tool to protect against repeated unsuccessful login attempts, since Lync's lack of SAML compliance means that APM can't do the authentication for us. That authentication doesn't take place until the proxied connection gets all the way to the Lync Front End server that is part of internal AD domain. We have this running in a lab environment, and need to address this security issue prior to going to production.