![]() It doesn't exist as a standard feature of the technology. End-to-end encryptionĮncryption is a challenge in Kafka. With Conduktor Platform, you can see every action taking place within your Kafka ecosystem ensuring compliance and enhancing troubleshooting efforts. For example, if personal data was leaked, breaching GDPR, you can track the flow of data through Kafka. If a security breach occurs, an audit log provides a clear trail showing what occurred, when it occurred, and who was responsible. Audit logs include information about security for CIS, compliance with payment contracts (PCI DSS), and adherence to SOC 2.Īudit logs can be used to reconstruct the timeline of a system outage or incident and are used to differentiate between operator error and system errors. Having SSO is a necessary step in enabling RBAC, since it allows administrators to control registrations, instantly enabling or disabling users and assigning them to the correct roles.Ĭompliance regulations affect a wide variety of industries. Anyone with access to enterprise credentials will have access to Conduktor, and anyone you remove from your enterprise loses access. Once you've performed the necessary setup for these protocols, controlling access to the Platform is easy. The Conduktor Platform supports the LDAP and OpenId protocols for SSO. Single sign-on enables users to login to Conduktor Platform with a common set of credentials, for example, a Google or Microsoft account. And a "Business User" role could have read-only access to everything with no edit permissions. "QA" could be given access to Conduktor Testing and Conduktor Monitoring but not other parts of the Platform. "Junior Developer" is more limited, without edit access to mission-critical topics. A "Senior Developer" role would have edit access to everything in the Platform, but no admin permissions like deleting users or editing roles. One or more people will have "Admin" roles, having complete power over Conduktor Platform and the different roles. You can assign multiple users to roles at once by creating groups. ![]() In the Conduktor Platform, RBAC permissions can be set at the topic level, meaning different roles would have different levels of access to individual topics. Role-based access control allows administrators to assign specific roles to individual users, specifying what each role can access. Security for Kafka is provided through End-to-end encryption and Data masking. There are three key Platform security features: Role-based access control (RBAC), Single sign-on (SSO), and audit logs. We can divide security features into two areas: security for your Kafka, and security for the Platform itself. How the Conduktor Platform provides security In this blog, we'll be looking at the security features available for users of the Conduktor Platform. With so much of the world's infrastructure now involving Kafka in some way, enterprises need every tool at their disposal to help keep data safe. Conduktor Platform has introduced loads of impressive and innovative new solutions for Apache Kafka, but when it comes to importance, none will be as relevant as the security solutions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |