BizTalk Server Security Features

Financial Services applications and integration solutions developed by using BizTalk Accelerator for SWIFT (A4SWIFT) are BizTalk Server applications and are secured by native BizTalk Server security features. BizTalk Server applications are typically made up of messaging functionality (message processing, transformation, routing) and workflow automation (business process automation, business rules and logic evaluation). BizTalk Server provides general messaging and workflow automation security. A4SWIFT provides additional security features specific to securing end-user message entry, repair, approval, and submission. For more information about A4SWIFT-specific security, see A4SWIFT Security Features for Message Repair and New Submission.

BizTalk Server is designed around a messaging event model (centered on the MessageBox database and publisher-subscriber design pattern) in which the messages and documents, as well as the processing components that interact with them, are based on XML and Web services technologies. To help protect the integrity of any system made up of information, participants, and processes, the following primary requirements guide security mechanisms:

  • Protecting the privacy of system elements. Protecting the privacy of communications in an open computing and networking environment is the function of encryption. BizTalk Server supports encrypted communications through public key infrastructure (PKI), Secure Multipurpose Internet Mail Extensions (S/MIME), and Secure Sockets Layer (SSL). To authenticate and enhance protection of the privacy of messages, BizTalk Server makes extensive use of digital certificates (keys).

    PKI is the set of Internet protocols that address the methodologies that promote secure exchange of keys, the procedures and hierarchy of authority for authenticating keys, and the algorithms deployed for these purposes.

    BizTalk Server uses the S/MIME protocol to encrypt and decrypt messages sent and received in multi-step, multi-party processes, with Data Encryption Standard (DES), 3DES, and RC2 encryption algorithm support. For encrypted point-to-point communication between a Web client and a Web server, BizTalk Server uses the SSL protocol.

  • Authenticating information, participants, and processes. To authenticate information, participants, and processes, BizTalk Server relies on signing certificates, Windows Authentication, and an extended implementation of Windows Authentication in BizTalk Server known as Enterprise Single Sign-On (SSO). Signing certificates are digital certificates (or keys) that identify two parties to each other in a messaging exchange. A signing certificate also determines if a message was tampered with in transit.

    BizTalk Server can use stored public keys to decode digitally signed incoming messages, and can use private keys to sign outbound messages that it generates. SSO is the BizTalk Server extension to Windows Authentication that allows parties and messaging events that are engaged in multi-step BizTalk Server processes to authenticate themselves, at any step in the process, to any resource in the process, without requiring multiple logons.

  • Authorizing resource usage. Authorization is the allocation and management of usage rights to the resources of a system. The primary BizTalk Server authorization mechanisms are SQL Server Roles, Windows Authentication, and the MessageBox database. BizTalk Server stores all incoming and outgoing messages in its MessageBox database, before sending them to an orchestration process and after the orchestration sends the messages to a send pipeline. Access to BizTalk Server databases and resources is assigned to administrators, users, and host accounts using SQL Server Roles.

    The BizTalk Server security architecture is based on a robust set of mechanisms that are implemented throughout BizTalk Server using a variety of methodologies designed to increase security. The BizTalk Server components that incorporate the security mechanisms are send and receive adapters, pipelines, the MessageBox database, orchestrations, and message security context properties.

    These components use Authentication Required pipelines, multiple logical hosts and their "Authentication Trusted" property, and the Publish and Subscribe/Receive Authorization methodologies to deploy the security mechanisms. This multifaceted security architecture of BizTalk Server provides numerous options for helping to design and execute more secure Financial Services messaging and workflow automation applications.