New BIG-IP ASM v13 Outlook Web Access (OWA) 2016 Ready Template
F5 has created a specialized ASM template to simplify the configuration process of OWA 2016 with the new version of BIG-IP v13
Click here and download the latest version of XML file that contains the template: Outlook Web Access 2016 Ready Template v6.x
Goal: Quick OWA 2016 base line policy which set to Blocking from Day-One tuned to OWA 2016 environment.
Ready Template Deployment Steps
- Download the latest version of the policy XML file (click on the file --> Raw --> Save As) from the link above
- Update Attack Signature to the latest version: Click "Security Update" --> "Application Security" --> "Check for Updates" --> "Install Updates"
- Click "Application Security" --> "Import Policy" --> Select File" and choose the XML file
- Edit the policy name to the protected application name and click "Import Policy"
- Attach the policy to the appropriate virtual server
- Refine learning new records in "Application Security" --> "Policy Building" --> Traffic Learning"
- Observe no false positive occur by validating event logs: "Event Logs" --> "Application" --> "Request"
Important: If the policy is not working properly, please ensure you are using the latest version. If you have any issues or questions, please send any feedback to my email: n.ashkenazi@f5.com
Published Jan 24, 2018
Version 1.0
Nir_Ashkenazi
Employee
EmployeeNir_AshkenaziEmployee
Employee
gscholz_370150Nimbostratus
I am using the template for v13.1. I updated the attack signatures as described in step 2, and this is the first line of the readme:
Update: v13.1.0/ASM-SignatureFile_20180925_171453:Importing the policy (step 3) completes successfully, but gives me 64 lines of the following before the success message:
signature with id xxxxxxxxx (previously used in this security policy) does not exist on this system.I searched for a few IDs via Security ›› Application Security : Attack Signatures and saw that none of them seem to have an entry. What effect, if any, does it have on the policy if the XML file refers to attack signatures that are not defined on the box?
And does that mean the XML file is outdated (and with it the policy) every time the signature file gets updated?
Nir_AshkenaziThanks for the update Mr. Gundemarie, the logs are related to signatures that was removed, so it safe to ignore the logs. I would suggest to take the latest template 6.1.6 that was updated recently.
Andre-GermanyHello, have tried the Tamplate correspond. At the beginning, the call of OWA was also, but now I get a blocking. "Modiefied domain cookie Cookie Name: Clientid Reason: New Cookie" Why?
- Nir_Ashkenazi
Thanks Udo for reaching out, usually the alert is raised only after upgrading/changing the policy but it should stop after existing sessions are expired.
See https://support.f5.com/csp/article/K20323120 for more information.
If you think that is still occurs and it is a false-positive, you can remove the block protection: Security ›› Application Security : Policy Building : Learning and Blocking Settings >> Cookies >> Modified ASM cookie
- Andre-Germany
Modified ASM cookie is unplayed.
Now have Security >> Application Security: Headers: Cookies List ClientID set by Enforced Coolies to Allowed Cookies. Then the call goes again
- Ahmed_Al-Dhim_1
Thank you Nir for your great efforts. Can we know if this template for http or https ? or both ? As well as supporting OWA with ActiveSYNC or donot ?
- Nir_Ashkenazi
Thanks Ahmed, the policy support both "http"/"https" protocols and "ActiveSync".
- Balasundaram_32
Dear All,
I have BIG-IP 14.1.0 version will this Outlook Web Access 2016 Ready Template v6.x template be suitable;e as we have a customer where they want to go to OWA BLOCKING mode very urgently/Fastly . Kindly suggest..
- Nicol4s
Interesting.
We are gonna deploy this template in a few weeks.
I will let you know how it went.
efouliPage was not found , any alternative source of the template?
Thanks.