Working with Security

After you install WSO2 MB, it is recommended to change the default security settings according to the requirements of your production environment. As MB is built on top of the WSO2 Carbon Kernel (version 4.4.3), the main security configurations applicable to MB are inherited from the Carbon kernel.

You can find detailed information on how to configure security in your MB as explained below.

Configuration Description

Configuring keystores

A keystore is a repository that stores the cryptographic keys and certificates. These artifacts are used for encrypting sensitive information, and establishing trust between your server and outside parties that connect to your server.

All WSO2 products come with a default keystore (wso2carbon.jks). In a production environment, it is recommended to replace it with a new keystore. You can also configure multiple keystores for different purposes.

See the following in the WSO2 Carbon documentation:

Learn how public key encryption and keystores are used.
Learn how symmetric encryption can be used.
Learn how to create new keystores and replace the default one.
Learn how configuration files should be updated to use the relevant keystore for different purposes.

Securing sensitive passwords

As a secure vault implementation is available in all WSO2 products, you can encrypt the sensitive data such as passwords in configuration files using the Cipher tool.

See the following in the WSO2 Carbon documentation:

How the secure vault is implemented in WSO2 products.
How to encrypt passwords using the Cipher tool.
How to resolve encrypted passwords.

Enabling JAVA security manager See the topic enabling JAVA security manager in the WSO2 Carbon documentation on how to prevent untrusted code from manipulating your system.