Date: Fri, 29 Mar 2024 15:45:03 +0000 (UTC) Message-ID: <1781580748.8195.1711727103096@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8194_2052994668.1711727103094" ------=_Part_8194_2052994668.1711727103094 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Recommended Practice
Federation software relies on an extensive technology stack. As with all= web-based software, vulnerabilities can be introduced in many places, and = a security flaw on one site can lead to the exposure of another. This is pa= rticularly true when web authentication software is involved.
In addition, as a still-evolving and expanding technology, federation is= not yet an area for "install and forget" technology management. New use ca= ses and new best practices continue to emerge, and federation software, if = viable, will continue to evolve to address these new requirements.
Carefully consider strategies for maintaining currency in your:
Avoid big-bang upgrades crossing multiple significant versions. Ensure s= taff are monitoring the appropriate mailing lists to stay abreast of securi= ty issues and patches. In general, treat your environment the way you would= treat any mission-critical system.