HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
CSRF (Cross Site Request Forgery) and MITM (Man-in-the-middle) are two different type of issues.
Counter-measures are:
Use SSL everywhere, which should be easy with the newly introduced management of TLS certificates: https://help.hcltechsw.com/domino/12.0.0/admin/wn_automating_cert_management.html
For current versions of Domino, use the default TLS ciphers which provide PFS (perfect forward secrecy)
https://help.hcltechsw.com/domino/12.0.0/admin/wn_new_curves_ecdhe.html
Enable HSTS (=HTTP Strict Transport Security)
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0074868 - but please also read this https://blog.nashcom.de/nashcomblog.nsf/dx/domino-12-beta-1-https-review-ratings.htm
Manage the SameSite cookie preference https://help.hcltechsw.com/domino/12.0.0/admin/conf_samesite_cookie.html
Nothing can fully prevent a man-in-the-middle attack, but can make it a lot harder. Still, please note that the weakest link is in front of the keyboard so dont forget end user security awareness & education to be taken into account.
As for CSRF, Domino is already preventing them for HCL top level applications like Verse. However any self developed Domino based web application will need to be taken care of by the developer of the app.
I am closing this idea as "shipped" because MiTM countermeasures are already in place and because CSRF countermeasures are the responsibility of the application developer.