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
Thanks Walter for reaching out, we are always in ongoing process to improve security and reduce false positive of the templates. The update touch multiple areas of the policy but mainly updated attack signatures sets and change positive models to compact mode with staging state. As well URL`s was updated with common content types.
So, this would be considered a patched version of that template then? Is there a section of the F5 download site for updated (supported) ASM Templates like there is for iApps?
Yes, it a patched version that would finally will be updated into the device template repository.
The template was tested on OW16K so there is no guaranty it would work as expected in OWA13K.
Thanks Amir for updating about the issue with active-sync, As far as I understand you are testing in clear environment? could you please export the illegal logs and send it to my email nashkenazi@ so I will take a look (via Events Logs -> Applications -> Request -> Select All -> Export) ?
Hi Nir, thanks for the quick reply. Unfortunately I had no logging profiles bound currently. I've just changed it and I'm waiting for a few events to occur. I hope to send you the logs latest by tomorrow.
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?
Thanks 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.
Hello, 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?
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.
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
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..
