<aside>
<img src="/icons/reorder_gray.svg" alt="/icons/reorder_gray.svg" width="40px" />
Menu
Home
About Us
Contacts
Sales Collateral
Customer FAQs
Partner FAQs
Competition/Battlecards
Common Objection Handling
G2 Reviews and Badges
Brand Assets
</aside>
Common objections and how to handle them
Business Size & Credibility
- “Why should we trust a smaller provider over established names like CompTIA, (ISC)², or SANS?”
- “Do Security Blue Team have enough qualified resources to deliver consistent training?”
- “Are Security Blue Team’s certifications actually recognized or valued by employers?”
- “How many organizations have actually used Security Blue Team courses?”
Content Quality & Relevance
- “How do I know Security Blue Team’s course content is up to date with the latest cyber threats?”
- “Are Security Blue Team’s courses aligned with any industry frameworks (e.g., NIST, ISO 27001, CIS Controls)?”
- “Is Security Blue Team’s training hands-on, or just theoretical?”
- “Who develops Security Blue Team’s training content? Are they actual cybersecurity professionals or generic educators?”
Pricing & Value
- “The price seems high; we can find cheaper courses online.”
- “What’s the ROI? How does this actually reduce risk or improve our compliance?”
- “We don’t have a big training budget; can we justify this cost?”
- “Why pay when there are free resources?”
Fit & Implementation Concerns
- “Our employees are too busy.”
- “Is Security Blue Team’s platform easy to deploy and manage?”
- “I / my team need support during and after training”
- “We want pilot the program before committing to a full rollout.”
Technical & tool-based Objections
- “Our team doesn’t use Splunk, this isn’t relevant to us”
- “We need some Cloud focused content for our analysts”
- “We only use commercial tooling like Magnet AXIOM”
- “We are an organisation who utilises EDR tooling on every endpoint, but it looks like SBT doesn’t cover that”
Download PDF Version of Common Objection Handling
SBT Objections.pdf
Back to Partner Portal