Announcing ShardSecure 2.1.0
We are pleased to announce that ShardSecure 2.1.0 is now available. With a number of security-focused upgrades and improvements, the new version offers even more advanced data security, resilience, and trust. Among the Version 2.1.0 updates are enhancements to role-based access controls, FIPS 140-2 L1 certified libraries, IP whitelisting for improved frontend API security, and policy-based filtering.
ShardSecure 2.1.0 comes at a time when the company is drawing attention to the issue of trust for SaaS providers, multi-cloud resilience, and data loss protection (as opposed to traditional data loss prevention). We know the importance of advanced data protection in the face of rising cyberthreats, and we believe our new updates will help us continue to provide this data protection for our customers.
Below, we’ll explain the new features in detail.
Enhancements to role-based access controls (RBAC)
ShardSecure 2.1.0 offers more granular controls around who can access the platform and what they can do with that access. We also added RBAC for the Admin Interface, allowing fine-grained control of permissions within that interface.
These changes will help organizations restrict their user access to the minimum levels required and support security best practices.
FIPS 140-2 L1 certified libraries
ShardSecure 2.1.0 introduces Federal Information Processing Standard (FIPS) 140-2 L1 certified libraries. Specifically, FIPS 140-2 Level 1 support may be enabled for installations requiring this certification. This update helps government organizations and larger enterprises meet requirements for FIPS 140-2 certification, which demonstrates that an organization’s cybersecurity measures have been tested and formally validated by the National Institute of Standards and Technology (NIST).
IP whitelisting for improved frontend API security
ShardSecure 2.1.0 has also introduced IP restrictions for access to the S3 API. These restrictions can be enabled globally or by bucket and/or user, limiting the IP addresses that can access the ShardSecure platform. By introducing more frontend security at the API level, ShardSecure continues to harden the overall platform.
Lastly, ShardSecure 2.1.0 has introduced new policy-based filtering with S3 metadata to help companies more precisely manage how their data is accessed and managed. This enables organizations to achieve dynamic data routing and dynamic data protection based on tags or metadata. Organizations can use this policy-driven approach within the ShardSecure platform to enforce data security, data privacy, and data residency dynamically.
Conclusion: Looking to the future with ShardSecure 2.1.0
As with every major update of the ShardSecure platform, Version 2.1.0 is intended to further our mission of helping companies regain control of their data. By extending our capabilities, we’re supporting organizations in their mission to improve security and trust for data stored in cloud, on-premises, or hybrid- and multi-cloud architectures. With strong data security and resilience, advanced file-level protection, support for cross-border compliance, native ransomware protection, and a simple integration process, the ShardSecure platform will continue to offer an innovative, agentless approach to securing valuable data.