Policies applied by Active Directory such as multi-factor authentication and password complexity are applied to Blue Prism

It makes it possible to add custom security roles in Blue Prism

Users are assigned security roles based on their group membership in Active Directory

Data encryption between Blue Prism devices is provided by default

SQL Always on Availability Groups

Windows Clustering

Replication

Blue Prism Active Sync

Connect an application server to 2 Database Instances in parallel

Providing high availability for the Runtime Resource will guarantee the SLAs for a business process.

External Load balancing solutions may be used to direct connections from a runtime resource to an appropriate application server.

DNS round robin with a low Time to live (TTL) setting may be employed as a simple mechanism for distributing connections between multiple application servers.

Set each Runtime Resource to point to at least 2 application servers in its configuration file.

By default the connection is native TCP and not encrypted

The runtime resource can be configured to use certificate-based encryption for all inbound communication

The login agent will automatically use a certificate if the runtime resource is configured to use one

The connection will be established via .NET remoting and will be encrypted as long as the “Use Secure Connections” flag is set

A central setting within Blue Prism can be used to prevent all associated Runtime Resources from accepting any instructional communications which are not encrypted.

An underlying disk subsystem which hosts many virtual devices can be a performance bottleneck.

Often shared hardware is over-allocated resulting in less than expected available capacity (e.g. 2 vCPUs may equate to 0.1 physical cores)

It is important to validate the actual performance of the Runtime Resources when operating on shared hardware

The performance of the Runtime Resource can impact processing throughput

All of the above

There are no conditions, only one Runtime Resource can be set to listen per Windows session.

Each Runtime Resource must listen on a different port and the processes which run on the device must not impact other processes on the same device.

Each Runtime Resource must listen on the same port and the processes which run on the device must not impact other processes on the same device.

Each Runtime Resource must listen on a different port.

Runtime Resource

Interactive Client (for Monitoring and Control)

Interactive Client (for development)

Application Server

All of the above

Redundancy - e.g. to provide a level of continuity if one Application Server fails

To increase the overall security of the environment

The number of connected clients and runtime resources

The Application Server doubles up as a Web Server for a separate application

The key is always stored in the database

The key is always stored within the config file on the Application Server

The key can either be stored in the database, in the config file on the Application Server, or in a separate securable file on the Application Server

The key is hard-coded and stored securely within the Application. It is subjected to obfuscation to ensure it ' s protection

The key can only be stored in the database or in the config file on the Application Server

Blue Prism is licensed, based on the number of connections to the database

The number of processes executing in the production environment(s) at the same time.

The license implications of the software that will be automated by Blue Prism

The licensing of the SQL Server environment

The Blue Prism license includes everything that will be required for a production environment