CrowdStrike Vulnerability Management Setup
Budget: ₹1,500 – ₹12,500 INR
I already have CrowdStrike in place; what is still missing is a properly configured Exposure Management module focused on vulnerability management. I want the console to surface the right risk insights, funnel them straight into our ticketing workflow, and give my team the clarity they need to act quickly.
Here is what I need from you:
• Turn on and fine-tune vulnerability management in CrowdStrike, making sure asset discovery, risk scoring, and prioritisation all align with best practice.
• Build and test the integration with our ticketing system so new findings are converted into trackable tickets automatically (we currently use ServiceNow, but I’m open to your suggestion if another connector is more efficient).
• Provide concise, step-by-step documentation of the configuration so we can maintain it in-house after hand-over.
Acceptance criteria
• All enabled policies and rules are visible in the console with no critical errors.
• A sample vulnerability successfully opens, updates, and closes a ticket inside the ticketing system.
• Final documentation clearly lists each setting changed and any service credentials used (with placeholders for secrets).
If you have recent experience rolling out CrowdStrike vulnerability management and linking it to a ticketing platform, I’d like to hear how you would approach this and how quickly you could have an initial build ready for testing.
Here is what I need from you:
• Turn on and fine-tune vulnerability management in CrowdStrike, making sure asset discovery, risk scoring, and prioritisation all align with best practice.
• Build and test the integration with our ticketing system so new findings are converted into trackable tickets automatically (we currently use ServiceNow, but I’m open to your suggestion if another connector is more efficient).
• Provide concise, step-by-step documentation of the configuration so we can maintain it in-house after hand-over.
Acceptance criteria
• All enabled policies and rules are visible in the console with no critical errors.
• A sample vulnerability successfully opens, updates, and closes a ticket inside the ticketing system.
• Final documentation clearly lists each setting changed and any service credentials used (with placeholders for secrets).
If you have recent experience rolling out CrowdStrike vulnerability management and linking it to a ticketing platform, I’d like to hear how you would approach this and how quickly you could have an initial build ready for testing.