Security consulting covers everything from a two-day pentest to years of product security work. A step-by-step way to define what you need, compare suppliers on evidence and set up an engagement that leaves you stronger.
In short
Choose a cybersecurity consultant by first writing down the decision or risk you need help with, then matching it to the right type of expertise: testing, compliance, architecture or leadership. Ask for comparable work, named people and sample deliverables, check how knowledge transfers to your team, and agree scope, access and confidentiality before work starts.
Buying security help is harder than buying most consulting, because the result is often the absence of something. This guide is written by Devies, a Gothenburg-based product and engineering consultancy, for CTOs, IT managers and product leaders who are about to hire a cybersecurity consultant (in Swedish usually säkerhetskonsult) and want to avoid paying for a generic report that nobody acts on. It covers the main types of security consulting, a selection process step by step, the questions that reveal real competence, and the warning signs.
What kinds of cybersecurity consultant are there?
Cybersecurity consultants fall into a few distinct types, and most bad engagements start with hiring the wrong type for the problem.
A cybersecurity consultant is an external specialist who assesses, designs, implements or governs security controls for an organisation for a limited period. The label covers very different work:
Type
Typical question
Typical output
Watch out for
Offensive testing (pentest, red team)
Typical question
Can someone break in, and how?
Typical output
Findings report with evidence and severity
Watch out for
Scanner output sold as a pentest
Governance, risk and compliance
Typical question
Do we meet NIS2, ISO 27001 or customer demands?
Typical output
Gap analysis, policies, risk register, roadmap
Watch out for
Template documents not fitted to you
Security architecture and engineering
Typical question
How do we build or fix this securely?
Typical output
Designs, implemented controls, pipeline changes
Watch out for
Recommendations without implementation
Product security
Typical question
Is the product we sell secure and compliant?
Typical output
Threat models, SBOM process, vulnerability handling
Watch out for
Little experience of real release cycles
Security leadership (CISO as a service)
Typical question
Who owns security decisions?
Typical output
Strategy, priorities, steering of others
Watch out for
Unclear decision rights and accountability
Incident response
Typical question
We have an incident now
Typical output
Containment, forensics, recovery advice
Watch out for
Signing a retainer only after the crisis
Many needs span two types. A company preparing for ISO 27001 may also need engineering help to close the gaps, and a pentest is wasted if no one can fix the findings. For the testing options, see pentest, vulnerability scan or threat modeling.
How do you choose a cybersecurity consultant, step by step?
Run the selection as a short, structured process: define the outcome, shortlist on evidence, test with a small piece of work, then commit.
- Write a one-page brief. State the business reason (a customer demand, a regulation, a new product, an incident), the systems in scope, the decision you need to make and the deadline. If you cannot write it, the first engagement should be a short scoping exercise.
- Decide what "done" looks like. A report, a working control, a passed audit, or a team that can do it themselves? This decides the type of consultant and the contract.
- Map the frameworks that apply. NIS2, the Cyber Resilience Act, ISO 27001, IEC 62443 or customer questionnaires. A shared reference, such as the NIST Cybersecurity Framework 2.0, helps compare proposals.
- Shortlist three suppliers with comparable work in your industry and technology. Ask for references you can call.
- Meet the actual people. Ask who will do the work, their experience and their availability. The senior person in the sales meeting may not be on the project.
- Ask for sample deliverables. An anonymised report or roadmap shows more than a slide deck.
- Check credentials where they matter. For testing, look for individual certifications and established schemes; in the UK, the National Cyber Security Centre runs certification schemes for services and professionals. For compliance work, check experience with your specific standard and auditor.
- Start with a bounded first phase. Two to six weeks with a clear output lets both sides test the fit before a longer commitment.
- Agree the commercial and legal basics. Scope, rules of engagement for testing, data handling, confidentiality, liability, and who owns the deliverables.
Which questions reveal real competence?
The best questions ask a consultant to explain trade-offs and past decisions, because competent people can tell you what they would not do and why.
Useful questions in the first meeting:
- "What would you look at first in our situation, and what would you leave for later?"
- "Tell us about an engagement where your first recommendation turned out wrong."
- "How do you prioritise findings when we can only fix a third of them this quarter?"
- "What will our team be able to do without you at the end?"
- "How do you work with our developers and release process, not just our policies?"
- "Which parts would you hand to another specialist?"
Listen for specific answers tied to your context. Vague answers about "holistic security" or a quick promise of certification are warning signs. So is a proposal that recommends the supplier's own product before understanding your environment.
How should the engagement be set up?
Set the engagement up so that knowledge stays with you, because the most expensive outcome is a dependency on one external person for decisions only your organisation can own.
Practical points:
- Pair consultants with internal owners. Every deliverable should have a named person in your team who understands and maintains it.
- Prefer adapting existing processes. Security fits best when it is built into how teams already plan, build and release.
- Consider a team, not one individual. Different phases need different skills: risk analysis, implementation, audit support.
- Keep decision rights clear. Under NIS2, management remains accountable for cybersecurity risk measures even when work is outsourced; see NIS2 and the Swedish Cybersecurity Act in practice.
- Treat the consultant as a supplier risk. They may get privileged access. Article 21 of NIS2, Directive (EU) 2022/2555 lists supply chain security, including relationships with service providers, among the required measures. As of October 2026 this applies in Sweden through the Cybersecurity Act (cybersäkerhetslagen).
Devies saw these points in practice in its cybersecurity work with Consilium Safety Group, a provider of fire, flame and gas safety systems. According to Consilium, working with a team rather than a single individual increased efficiency, and the greatest value came from adapting existing processes instead of building new ones.
What are the warning signs?
The clearest warning sign is a supplier who offers a fixed answer before asking about your business, systems and obligations.
Others to note:
- Guaranteed certification or "full compliance" by a date.
- A pentest priced and scoped without knowing your applications.
- Reports that list hundreds of findings with no prioritisation.
- No plan for knowledge transfer or handover.
- Reluctance to name the people doing the work.
- Pressure to sign a long retainer before a first phase.
If ISO 27001 is your goal, read ISO 27001 explained before inviting proposals, so you can judge whether a plan is realistic.
Devies
Want a second opinion?
Devies, a Gothenburg-based product and engineering consultancy, works on questions like this with Nordic product and IT teams. Tell us where you are and we will suggest a sensible first step.
Frequently asked questions
What does a cybersecurity consultant do?
A cybersecurity consultant is an external specialist who helps an organisation understand and reduce security risk for a limited period. Depending on type, the work can be testing systems for weaknesses, preparing for standards such as ISO 27001, designing and implementing security controls, building product security processes, leading security strategy part-time or responding to incidents. Good consultants leave behind working controls and an internal team that can maintain them.
Should we hire a security consultant or an in-house specialist?
Hire in-house when you need continuous ownership and have enough work for a full-time role. Use a consultant for specialist skills you need occasionally, such as penetration testing or audit preparation, for a time-limited push like meeting a regulation, or to get senior judgement before you can recruit. Many mid-sized companies combine both: an internal owner with consultants for depth and peaks.
Which certifications should a cybersecurity consultant have?
It depends on the work. For penetration testing, look for recognised individual practical certifications and, where relevant, national schemes such as those run by the UK National Cyber Security Centre. For ISO 27001 work, look for lead implementer or lead auditor training and real audit experience. Certifications show baseline knowledge only, so always ask for comparable work, references and sample deliverables as well.
How long does a typical security engagement last?
A penetration test or gap analysis usually takes days to a few weeks. Preparing for ISO 27001 certification or a regulation such as NIS2 often takes several months, because controls must be implemented and operated before an audit. Product security work and part-time leadership are often ongoing. Start with a bounded first phase of a few weeks to test the fit before committing longer.










