<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
	<id>https://www.insurerbrain.com/w/index.php?action=history&amp;feed=atom&amp;title=Definition%3ASingle_sign-on_%28SSO%29</id>
	<title>Definition:Single sign-on (SSO) - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.insurerbrain.com/w/index.php?action=history&amp;feed=atom&amp;title=Definition%3ASingle_sign-on_%28SSO%29"/>
	<link rel="alternate" type="text/html" href="https://www.insurerbrain.com/w/index.php?title=Definition:Single_sign-on_(SSO)&amp;action=history"/>
	<updated>2026-05-02T20:19:32Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://www.insurerbrain.com/w/index.php?title=Definition:Single_sign-on_(SSO)&amp;diff=20452&amp;oldid=prev</id>
		<title>PlumBot: Bot: Creating new article from JSON</title>
		<link rel="alternate" type="text/html" href="https://www.insurerbrain.com/w/index.php?title=Definition:Single_sign-on_(SSO)&amp;diff=20452&amp;oldid=prev"/>
		<updated>2026-03-18T01:18:33Z</updated>

		<summary type="html">&lt;p&gt;Bot: Creating new article from JSON&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;🔑 &amp;#039;&amp;#039;&amp;#039;Single sign-on (SSO)&amp;#039;&amp;#039;&amp;#039; is an authentication mechanism that allows users to access multiple applications and systems with a single set of credentials, eliminating the need to log in separately to each platform — a capability of particular value in the insurance industry, where professionals routinely navigate between [[Definition:Policy administration system (PAS) | policy administration systems]], [[Definition:Claims management system | claims platforms]], [[Definition:Bordereaux | bordereaux]] reporting tools, [[Definition:Reinsurance | reinsurance]] accounting modules, and [[Definition:Customer relationship management (CRM) | CRM]] systems throughout a single workday. For an [[Definition:Underwriter | underwriter]] at a [[Definition:Lloyd&amp;#039;s syndicate | Lloyd&amp;#039;s syndicate]] or a [[Definition:Claims adjuster | claims handler]] at a large composite [[Definition:Insurance carrier | insurer]], SSO transforms what would otherwise be a fragmented and time-consuming login ritual into seamless movement across interconnected tools.&lt;br /&gt;
&lt;br /&gt;
⚙️ SSO works by establishing a trust relationship between a central identity provider (IdP) and the various service providers (applications) an organization uses. When an insurance employee authenticates once — typically through protocols like SAML 2.0, OAuth 2.0, or OpenID Connect — the identity provider issues a security token that each connected application accepts as proof of identity, granting access according to the user&amp;#039;s [[Definition:Role-based access control (RBAC) | role-based permissions]]. In practice, this means a [[Definition:Managing general agent (MGA) | MGA]] employee logging into a carrier&amp;#039;s [[Definition:Delegated underwriting authority (DUA) | delegated authority]] portal might simultaneously gain access to a document management system, a [[Definition:Rating engine | rating engine]], and a [[Definition:Premium | premium]] accounting interface without re-entering credentials. Many [[Definition:Insurtech | insurtech]] platforms and modern core system vendors design their products to integrate with enterprise identity providers from the outset, recognizing that insurance organizations increasingly operate hybrid technology estates spanning legacy on-premises systems and cloud-based solutions.&lt;br /&gt;
&lt;br /&gt;
💼 Beyond convenience, SSO carries significant security and governance implications for insurers. Centralizing authentication reduces the proliferation of passwords across systems — a major vulnerability vector in an industry that handles vast quantities of sensitive personal and financial data subject to regulations like GDPR, HIPAA (for U.S. health insurers), and various [[Definition:National Association of Insurance Commissioners (NAIC) | NAIC]] data security model laws. When an employee departs or changes roles, a single deactivation at the identity provider level instantly revokes access to every connected system, closing a gap that manual deprovisioning across dozens of platforms would leave open for days or weeks. For [[Definition:Insurance broker | brokers]] and carriers participating in platforms like the London market&amp;#039;s [[Definition:Placing Platform Limited (PPL) | electronic placement]] systems or pan-Asian [[Definition:Insurance exchange | exchange]] portals, federated SSO enables cross-organizational access while keeping each entity&amp;#039;s identity governance intact — a practical necessity in an industry defined by complex multi-party relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Related concepts:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{{Div col|colwidth=20em}}&lt;br /&gt;
* [[Definition:Role-based access control (RBAC)]]&lt;br /&gt;
* [[Definition:Cyber insurance]]&lt;br /&gt;
* [[Definition:Data governance]]&lt;br /&gt;
* [[Definition:Application programming interface (API)]]&lt;br /&gt;
* [[Definition:Cloud computing]]&lt;br /&gt;
* [[Definition:Information security]]&lt;br /&gt;
{{Div col end}}&lt;/div&gt;</summary>
		<author><name>PlumBot</name></author>
	</entry>
</feed>