# FIPS 140-2 compliance and OpenSSL

**URL:** <https://forum.scylladb.com/t/fips-140-2-compliance-and-openssl/773>\
**Category:** ScyllaDB\
**Tags:** security, compliance\
**Created:** [August 10, 2023, 5:04pm UTC](https://forum.scylladb.com/t/fips-140-2-compliance-and-openssl/773 "2023-08-10T17:04:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bill\_Dunmire](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/bill_dunmire/32/235_2.png) [@Bill\_Dunmire](https://forum.scylladb.com/u/Bill_Dunmire)\
**Post date:** [August 10, 2023, 5:04pm UTC](https://forum.scylladb.com/t/fips-140-2-compliance-and-openssl/773/1 "2023-08-10T17:04:44Z")

</div>

We are considering ScyllaDB Enterprise and want to understand your FIPS 140-2 compliance. For both system and table data, can you use different algorithms that are supported by OpenSSL in a file block encryption scheme?”

---

<div class="post-metadata">

**Author:** ![Guy](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/guy/32/9_2.png) [@Guy](https://forum.scylladb.com/u/Guy)\
**Post date:** [August 13, 2023, 8:24am UTC](https://forum.scylladb.com/t/fips-140-2-compliance-and-openssl/773/2 "2023-08-13T08:24:24Z")

</div>

Yes, OpenSSL for both encryptions. Once enabled, all communication between the client and the node is transmitted over TLS/SSL. The libraries used by Scylla for OpenSSL are FIPS 140-2 certified.

See more in the documentation about client-to-node[encryption](https://opensource.docs.scylladb.com/stable/operating-scylla/security/client-node-encryption.html) and[node-to-node encryption](https://enterprise.docs.scylladb.com/stable/operating-scylla/security/node-node-encryption.html).

ScyllaDB security features, including encryption, are covered in [this](https://university.scylladb.com/courses/scylla-operations/lessons/scylla-security-features/) ScyllaDB University lesson.