Lead Data Security Solution Engineer

Responsibilities

• Review Data In-Licensing requirements, workflow maps, data flows, entitlement rules, and dependency records; assess relational database platforms, schemas, connectivity methods, query patterns, and identify where licensed data is stored, transformed, replicated, extracted, or backed up
• Assess current database security capabilities and identify gaps, constraints, risks, and prerequisites
• Design authentication for named users, service identities, workloads, and analytical tools accessing databases; evaluate OAuth/OIDC or token-based authentication; integrate enterprise identities, security groups, and database principals; reduce reliance on shared or long-lived credentials
• Design database-level controls restricting access to authorized users, groups, services, or licensing populations; implement row-level security, column-level security, dynamic masking, views, or policy-based filtering; ensure controls are enforced at the data layer, not solely dependent on application logic
• Design database auditing capturing who accessed data, what, when, and which identity was used; define logging for queries, exports, failed attempts, and permission changes; integrate audit telemetry with monitoring and reporting; ensure audit records are searchable, protected, and useful for investigation
• Design controls for access revocation when users change roles or licensing rights expire; design methods to identify and remove licensed data from primary stores and downstream copies; address deletion implications for backups, archives, replication, and referential integrity; define validation and evidence mechanisms
• Translate requirements into architectures, technical specifications, and implementation plans; compare solution options across security, feasibility, performance, scalability, and cost; collaborate with database, IAM, security architecture, infrastructure, application, and governance teams
• Select database and workflow candidates for POC; define POC architecture, test data, success criteria, and rollback approach; implement and validate authentication, fine-grained authorization, auditing, revocation, and deletion scenarios; document outcomes, limitations, and recommendations

Languages