How to Write a Cybersecurity Award Submission That Judges Trust
To write a cybersecurity award submission that judges trust, describe one clearly defined piece of work, explain the problem it solved in plain language, show measurable or observable outcomes, and back every claim with evidence you can safely share. The challenge is that most security work is confidential by nature. The good news is that a strong entry rarely needs sensitive details. It needs a credible narrative, a logical structure and proof that a knowledgeable reader can follow. This guide walks through how to get there, whether you are a CISO, part of an in-house security team or a vendor building security products.
Start with what expert judges need to see
Entries to the Digital Security Innovators programme are assessed through a multi-phase evaluation process led by industry experts. That shapes how you should write. Experienced reviewers will quickly notice vague claims, inflated language and buzzwords used without substance. They will also recognise genuine judgement, sound trade-offs and honest reporting of results.
Before drafting, read the programme page, the judging process and the Competition Rules. Note what the programme asks for and make sure every section of your entry answers it directly. A submission that is easy to evaluate against the published requirements is a submission that respects the judges' time.
Then ask yourself three questions:
- What exactly is being entered? A product, a programme, a team, an individual's contribution or a specific initiative. Pick one.
- Why did it matter? The risk, gap or business problem that made the work necessary.
- What changed because of it? The outcome, stated as precisely as you can share.
A structure that makes security work easy to follow
Security narratives often collapse into a list of tools and controls. Judges need a story with a beginning, middle and end. A dependable structure looks like this:
- Context. The organisation or market, described at the level of detail you are comfortable disclosing: sector, scale band, regulatory environment, threat landscape.
- The challenge. What was at risk and why existing approaches were not enough. Be specific about the type of problem, even if you omit names.
- Your approach. The decisions you made and why. This is where expertise shows: the alternatives you considered, the constraints you worked within and how you balanced security, usability and cost.
- Execution. How it was delivered: phases, people involved, obstacles and how you overcame them.
- Results. What improved, supported by evidence.
- What comes next. Lessons learned and how the work continues to develop. This signals maturity rather than a one-off success.
Keep each section focused. If a paragraph does not help the judge understand the challenge, the approach or the result, cut it.
Turning confidential work into verifiable evidence
This is where many security entries struggle. You cannot publish incident details, architecture diagrams or client names, so the temptation is to stay general. General entries are hard to trust. The answer is to abstract the detail while keeping the substance.
Use relative and banded figures
Instead of exact numbers that could reveal sensitive information, use percentages, ranges or before-and-after comparisons. "Mean time to contain fell by more than half over two quarters" is both safer and more persuasive than a paragraph of adjectives.
Describe patterns, not incidents
Rather than recounting a specific breach attempt, describe the category of threat and how your approach handles that category. Judges with security backgrounds will understand the significance without needing indicators or timelines.
Anonymise with care
"A regulated financial services organisation operating in several EU member states" gives enough context to be meaningful. Check that the combination of details you provide does not make the organisation easy to identify if that would be a problem.
Choose evidence you are allowed to share
- Redacted or summarised audit outcomes and certification milestones
- Internal metrics expressed as trends
- Customer or stakeholder feedback, with permission
- Independent testing results or published research, where available
- Adoption, rollout or coverage figures presented as proportions
Get sign-off from legal, communications and, where relevant, clients before you submit. It is far better to agree boundaries early than to strip an entry at the last minute. It is also sensible to review the Regulations so you understand the terms that apply to submitted materials.
Plain-language framing for expert judges
Writing for experts does not mean writing in jargon. Even specialist judges read many entries, and clarity wins. A few principles help:
- Lead with the outcome, then explain the mechanism. "We reduced exposure from unmanaged devices across the estate" comes before the technical description of how.
- Define acronyms once and avoid stacking them. One unexplained term is tolerable; five in a sentence is not.
- Connect security to wider value. Resilience, regulatory readiness, customer confidence and operational continuity are outcomes that matter beyond the security team.
- Be honest about limits. Acknowledging what did not work, or what remains unsolved, makes the rest of your claims more believable.
- Avoid absolute claims. No serious practitioner believes anything is "unhackable". Overstatement erodes trust faster than anything else.
Common mistakes and a final check
Before submitting, review your draft against the pitfalls that most often weaken security entries:
- Listing products and frameworks without explaining decisions or results
- Entering an entire security function instead of a defined achievement
- Marketing copy repurposed from a website, especially for vendor entries
- Claims with no supporting evidence, or evidence that does not match the claim
- Leaving sign-off and redaction until the deadline is close
Ask a colleague outside the project, ideally someone technical but not involved, to read the entry. If they can explain back to you what was achieved and why it matters, the judges will be able to as well.
Finally, plan around the published dates. Each programme has its own timeline, and entry fees increase with each submission stage. For the Digital Security Innovators 2027 cycle, the Early Bird Submission Deadline is April 4, 2027 and the Final Submission Deadline is May 5, 2027. Always confirm dates on the Awards Timeline.
FAQ
Which NOVA Awards programme suits cybersecurity work?
The Digital Security Innovators programme is the dedicated home for security entries. Review its page to confirm your work fits before you begin drafting.
What are the key dates for the 2027 Digital Security Innovators cycle?
As published, the Early Bird Submission Deadline is April 4, 2027, the Regular Submission Deadline is April 14, 2027, the Late Submission Deadline is April 28, 2027 and the Final Submission Deadline is May 5, 2027. The Judging Period is May 6 – 16, 2027, and Winners Announced is May 19, 2027. Check the Awards Timeline for the latest information.
How much does it cost to enter?
Entry fees depend on the programme and the submission stage, and they increase with each stage. Current fees are listed on the Submit an entry page. For other questions, contact info@nova-awards.com.
Your security work deserves to be understood, not just described. Define the achievement, evidence it responsibly and explain it clearly, then submit your entry to the Digital Security Innovators programme at the stage that suits your timeline.