Security Engineer, Vulnerability Management Focus (Middle / Senior)
Xsolla · Kuala Lumpur · Remote · Lever
About the job
Xsolla seeks a technically strong Security Engineer with a focus on vulnerability management to join a new security team during a critical build-out phase. You own the vulnerability management lifecycle across our infrastructure, cloud, container and application estate: from discovery and prioritization to validated findings, ready-to-apply fixes and verified closure.
We are not looking for someone who forwards scanner reports. We are looking for an engineer who can independently confirm that a vulnerability is real and exploitable in our environment, understand its root cause, and come to the development or infrastructure team with a concrete, tested solution: a patch plan, a configuration change, a pull request, a hardened image, or a compensating control. You earn trust with engineering teams by being technically right and by making the fix easy.
You work closely with the security program manager, platform and infrastructure teams, and application developers, and you help shape how vulnerability management is run at Xsolla as the program matures. Depending on your level, you will either drive the program day to day (Middle) or define its strategy, standards and tooling and mentor others (Senior).
Our tech stack includes GCP, vSphere/ESX, Kubernetes and container workloads, MariaDB, CockroachDB, Go, PHP, and Python. You do not need expertise in all of these, but you are comfortable navigating a mixed environment and learning what you need.
As always true in job descriptions, there is an intangible value that is hard to capture. We look for a diverse set of perspectives and skills. Even if you don't match every requirement, we encourage you to apply if you think you can be highly successful in this role.
Responsibilities-
Run the Vulnerability Management Lifecycle - Operate and continuously improve the end-to-end process: asset discovery, scanning, triage, prioritization, remediation, verification and reporting.
-
Scan Across the Whole Estate - Manage authenticated and unauthenticated scanning of hosts, network segments, cloud workloads, Kubernetes clusters, container images, and application dependencies (SCA), ensuring coverage and minimizing blind spots.
-
Validate Findings Technically - Reproduce and confirm vulnerabilities hands-on: analyze affected versions and configurations, check reachability and exploitability, build or adapt a proof of concept where appropriate, eliminate false positives, and document the evidence and real impact.
-
Deliver Ready-to-Use Solutions - Do not stop at "this is vulnerable". Propose and test the fix: package upgrades and patch procedures, base image and dependency updates, Kubernetes and OS hardening, configuration management and IaC changes (Puppet, Terraform, Helm), WAF virtual patching, network segmentation, or other compensating controls. Where it makes sense, submit the change yourself as a pull request or merge request, or hand over precise step-by-step instructions that the team can apply with confidence.
-
Prioritize by Real Risk - Go beyond CVSS. Combine exploitability (EPSS, CISA KEV, public exploits), validated impact, asset criticality, internet exposure, reachability and compensating controls to decide what must be fixed first.
-
Drive Remediation with Engineering - Partner with infrastructure, platform and development teams to agree on fixes, workarounds and timelines. Provide clear, actionable tickets with evidence, root cause and a recommended solution rather than raw scan output.
-
Define and Enforce SLAs - Establish, track and report remediation SLAs by severity and asset class, manage exceptions and risk acceptances, and escalate when deadlines are at risk.
-
Verify Remediation - Re-test after fixes are applied and confirm closure with evidence, including regression checks that the fix does not break the service.
-
Respond to New Threats - Monitor vulnerability intelligence and advisories, assess exposure to newly disclosed critical vulnerabilities (zero-days, actively exploited CVEs), and coordinate rapid response with relevant teams.
-
Automate and Integrate - Build automation and integrations (Python, APIs) that connect scanners, asset inventories, ticketing and chat systems to enrich findings, deduplicate, route to owners, auto-validate where possible and track SLAs.
-
Report on Posture and Trends - Build dashboards and metrics (coverage, MTTR, SLA compliance, risk burn-down, aging) for engineering leadership and the wider security team, and support audits.
-
Support Compliance and Assurance - Provide technical evidence for vulnerability scanning and patching requirements under PCI DSS and similar frameworks, and help triage penetration test findings.
-
Support Incident Response - Contribute exposure analysis during security incidents and help document root causes where vulnerabilities were involved.
-
Write Async Security Guidance - Produce advisories, remediation playbooks and best-practice documentation that help engineering teams across time zones.
-
Hands-on Vulnerability Management Experience - Practical experience running vulnerability management for infrastructure and/or cloud environments (Middle: 3+ years in security or a closely related field; Senior: 5+ years, with ownership of a program or major components).
-
Vulnerability Validation Skills - Proven ability to verify findings yourself: reading CVE and vendor advisories, understanding root cause, reproducing issues in a test environment, and judging real-world exploitability. Comfortable with tools such as Burp Suite, nmap, curl, Metasploit, Nuclei or similar, and with analyzing network traffic and logs.
-
Strong Linux and Systems Knowledge - Deep working knowledge of Linux (packages, services, kernel and OS hardening, permissions, systemd), plus networking fundamentals (TCP/IP, TLS, firewalls, segmentation), sufficient to validate findings, understand patching implications and design practical mitigations.
-
Remediation Engineering - Experience turning findings into working fixes: patching and upgrade procedures, configuration hardening, secure base images, and infrastructure-as-code changes. You can test a fix and explain its impact and rollback plan to the owning team.
-
Container and Cloud Security - Has worked with GCP or a similar cloud provider and is comfortable with IAM, cloud networking, and Kubernetes/container security concepts, including image and registry scanning and runtime configuration.
-
Code Literacy and Scripting - Writes and reads Python (or similar) to work with APIs, process scanner output and automate workflows. Reads code in Go, PHP or Python well enough to trace a vulnerable dependency or code path, understand a fix, and review or propose a patch. Comfortable with Git and the pull request workflow.
-
Scanner and Platform Experience - Experience with enterprise vulnerability and exposure management tooling (for example Tenable, Qualys, Rapid7, Wiz, or similar), including scan configuration, tuning and result analysis. Familiarity with open-source tools such as Trivy, Grype or OpenVAS is a plus.
-
Risk-Based Prioritization - Solid understanding of CVSS, EPSS, CISA KEV and how to translate technical severity into business risk.
-
Strong Written Communication - Writes clear, concise async documentation (findings, evidence, advisories, remediation guidance) that works across time zones and audiences.
-
Collaborative Mindset - Partners effectively with engineering teams and focuses on getting issues fixed, not just reported.
-
Self-Directed with Growth Mindset - Comfortable with ambiguity and able to make progress with minimal direction in a new and evolving team.
-
Has designed or significantly matured a vulnerability management program, including policy, SLAs, exception handling and metrics.
-
Handles complex, high-impact vulnerabilities end to end: deep root-cause analysis, validated exploitability, and cross-team remediation plans for critical systems.
-
Can set direction on tooling selection, coverage strategy and integration architecture.
-
Influences engineering leadership and handles difficult prioritization and risk-acceptance conversations.
-
Mentors other engineers and raises the overall security maturity of partner teams.
-
Anticipate the next generation of vulnerability risk. Bring a clear point of view on how AI-assisted development may introduce vulnerabilities, change the types of weaknesses we encounter, and increase the speed and volume of code entering production.
-
Build for velocity and scale. Design a vulnerability management approach that keeps pace with faster software delivery and a growing volume of findings. Identify where traditional scanning, manual triage, and remediation workflows will become bottlenecks, and evolve them accordingly.
-
Apply automation with judgment. Evaluate and use AI and automation to improve discovery, validation, prioritization, and remediation, while understanding their limitations and ensuring consequential decisions and fixes are appropriately verified.
-
Turn foresight into action. Translate emerging risks into practical changes to coverage, tooling, engineering practices, and measures of effectiveness. Help security and engineering leaders make informed decisions about where to invest before gaps become incidents.
-
Penetration testing, red team or exploit development background, used to validate exploitability and reduce false positives.
-
Experience with cloud-native exposure management and CSPM platforms (for example Wiz or similar), including attack-path analysis and toxic-combination triage.
-
Software composition analysis (SCA), SBOM and supply-chain security experience.
-
Application security background: SAST/DAST, code review, familiarity with common vulnerability classes.
-
Hands-on Kubernetes security experience (admission control, runtime and image scanning, CIS benchmarks).
-
Experience with configuration management and IaC (Puppet, Terraform, Helm) and CI/CD pipelines.
-
Familiarity with vSphere/ESX hardening and virtualization security.
-
Familiarity with PCI DSS (including scanning and patching requirements), SOC 2, ISO 27001 or NIST CSF from a technical perspective.
-
Experience with SIEM/logging, detection engineering, or incident response.
-
Experience building internal security tooling and integrations with ticketing systems such as Jira.
-
Relevant certifications (OSCP, GPEN, GWAPT, CKS, GCP security certifications, or similar hands-on certs).
-
Xsolla operates across multiple time zones, so strong written and asynchronous communication is essential.
-
We value clear thinking, accountability, and direct communication.
-
This role suits someone who wants to own a core security discipline, be technically credible with engineers, and shape how it operates over time.
Application
Posted 4 hours ago
Members feature · See plans
Remember: Vagaslume.Tech never charges fees, courses or payments to take part in hiring processes. If you are asked to pay anything related to being hired, do not make the payment.