Security features of SuperOffice
Active Directory single sign-on
SuperOffice integrates well with existing Active Directory infrastructures allowing users to easily sign in using their existing domain credentials. This is a user-friendly and secure way to integrate SuperOffice into your environment and it does not impose new credentials for your users to remember. Another advantage is that the existing password policy is enforced making sure that users have strong passwords.Customizable password policy setting
If Active Directory integration is not a fit for your business, SuperOffice lets you define a strong password policy making sure the passwords used in SuperOffice comply with the information security policy of your organization.Customizable role-based permissions
SuperOffice comes with a highly customizable role-based CRUD permission matrix, allowing you to define granular levels of access for all your users. It is highly recommended to implement permissions with the principle of least privilege in mind as to not grant users excessive access to company data, but still allowing them to do their job effectively.Web application security
SuperOffice strives to follow security best practices for all of its components. A focus on the OWASP testing methodology and OWASPs Top 10 list of vulnerabilities enables SuperOffice to build secure and robust web applications. All components are regularly audited by security professionals and security testing is closely integrated with SuperOffice’s Software Development Lifecycle. This allows SuperOffice to discover and fix bugs in a timely manner, keeping the software secure.Encrypting traffic
SuperOffice servers communicate with each other, with clients, and potentially with outside services such as mail servers. To maintain the integrity and confidentiality of the communications, we recommend using HTTPS everywhere. Securing HTTPS correctly is not necessarily difficult, but recommendations change quickly as new vulnerabilities are discovered in encryption algorithms and protocols. We recommend using tools such as SSL Labs’ Server Test or SSLyze to test your configuration regularly. The Norwegian National Security Authority (NSM) has published a detailed guide on how to harden encryption on Windows systems and we recommend that you follow their advice when deploying SuperOffice. The process is simple and an be done by rolling out a Group Policy from a domain controller using the tool from NSM, or running a Powershell script that edits the registry on each server. Here is a set of recommendations that represent the current setup that is considered secure.HTTPS: Using strong ciphers to protect your data in transit
- TLS1.2, TLS1.1 should be enabled on all servers
- SSL2 and SSL3 should be disabled on all servers.
- Encryption ciphers should be strong with key size of 128-bits or more.
- Use of MD5, RC4 and DES should be avoided.
Certificates
The SuperOffice web application should use valid X.509 certificates. If SuperOffice is to be accessible on the internal network only, a certificate signed by an internal CA that is distributed to all clients could be used. Otherwise, if SuperOffice should be accessible from the Internet we recommend buying a certificate signed by a third-party CA. All certificates should be signed using the SHA256 algorithm and contain a full common name to make it valid and able to reassure users that they are connecting to the correct web server. This provides integrity of the data passed between your users and your CRM system.Hardening Windows servers
SuperOffice recommends using the latest Windows Server as your platform. Windows servers used in the SuperOffice deployment should be hardened as much as possible, and we recommend that you take the following into consideration:- Run the Security Configuration Wizard on the servers and apply SMB signing.
- Install the Enhanced Mitigation Experience Toolkit (EMET).
- Keep servers up to date with the latest updates from Windows.
- Install a recognized and proven anti-malware solution on the server.
- Set a strong password policy for the servers.