About CyberSafe

Overview

Our global team of experts are committed to remaining at the forefront of common authentication, encryption, reduced sign-on, and secure single sign-on technology.

The Kerberos protocol is included in Microsoft Windows & Active Directory, and used to authenticate users. Our TrustBroker family of Kerberos based security products deliver a comprehensive and flexible range of security solutions. Each solution is complemented by an after sales support service that customers can really rely on for fast resolution when using TrustBroker products to secure their critical business applications.

Our company background and technology experience

We were the first company to offer a commercial Kerberos-based security product in 1991, and the first to provide critical security interoperability between Microsoft Windows 2000 and non-Microsoft operating systems and applications. This experience and expertise in commercially supported Kerberos-based authentication and security is unsurpassed.

1991–1993

• The company CyberSafe Corporation (formerly Open Computing Security Group) was founded, and headquartered in Issaquah, Washington State, United States.
• The first product was released, and named Challenger. This product was based on an open source implementation of Kerberos from MIT, but the code quality was improved and turned into a commercially supported product. Challenger was sold to customers who had requirements for strong authentication and better security for their applications.
  

1993–1999

• CyberSafe re-wrote the Challenger product, creating a new product known as TrustBroker, which incorporated an implementation of Kerberos, not based on open source code.
• TrustBroker was sold to many companies, both in United States and internationally.
  

1999

• CyberSafe Limited in United Kingdom was formed, as the international office of CyberSafe Corporation.

2000

• Microsoft launched the Windows 2000 operating system, and Active Directory on Windows Servers. These were the first products from Microsoft to use the Kerberos protocol, and used to authenticate users to a Microsoft network. The user logs onto the Windows 2000 Workstations, and their Kerberos credentials are used to access certain services on Microsoft servers, such as file/print services.
• To coincide with the Windows 2000 launch, CyberSafe Corporation released verion 4 of their products (it was initially branded as ActiveTRUST, but then got renamed back to TrustBroker at a later date). The focus of version 4 was to provide Active Directory interoperability, and allow customers using applications on Unix or Linux to take advantage of an Active Directory infrastructure.

2001

• CyberSafe Limited acquired the source code for the TrustBroker products from CyberSafe Corporation, through a management buyout. The ongoing marketing, sales and development of the products continued, and support services were provided to the previous CyberSafe Corporation customers.
  

2001–2011

• Customers of Microsoft adopted Active Directory, replacing NT domains (using NTLM protocol). Microsoft continued to improve support for Kerberos in their products, and added it to Windows XP, Windows Vista, Windows 7 as well as Windows Server 2003, 2003 R2, 2008 and 2008 R2.
• CyberSafe Limited continued to develop and sell TrustBroker products to customers, using an Active Directory infrastructure for authentication and key management. Focusing on customers using SAP business applications allowed the company to gain valuable experience on what customers using critical business applications demand. This experience was used to enhance the TrustBroker products, so that they can be used for more than single sign-on.

2011

• The CyberSafe global team of experts is committed to remaining at the forefront of common authentication, encryption, reduced sign-on and secure single sign-on technology.
• CyberSafe’s TrustBroker family of Kerberos based security products continue to deliver a comprehensive and flexible range of security solutions. Each solution is complemented by an after sales support service that customers can really rely on for fast resolution when using TrustBroker to secure their critical business applications.

2012-2013

• CyberSafe's TrustBroker Secure Client product now includes FDA 21 CFR Part 11 compliance features, so that organizations can implement Single Sign-On or other forms of Active Directory integrated authentication, and also use electronic signatures for FDA compliance.

2014

• CyberSafe launches the TrustBroker One Credential product, which allows applications running on NetWeaver AS for ABAP to be accessed using a web browser and no Sign-On screen is shown to the user. It is particularly useful for applications like Fiori, NWBC, Web CRM UI, BSPs, WebDynpro ABAP, Web GUI etc.

2016

• CyberSafe TrustBroker products now support policy based authentication, where a user can be authenticated according to their SAP role assignment. The policy is configured in each SAP system, so each system can have a different policy. For example, an administrator can be forced to use two-factor authentication (e.g. RSA SecurID, or an X.509 certificate on smart card) if they logon to a system using SAP GUI and have an administrative role assigned.