Discover Tability: the AI platform that turns OKRs into resultsLearn more →

3 OKR examples for Security Controls

What are Security Controls OKRs?

The Objective and Key Results (OKR) framework is a simple goal-setting methodology that was introduced at Intel by Andy Grove in the 70s. It became popular after John Doerr introduced it to Google in the 90s, and it's now used by teams of all sizes to set and track ambitious goals at scale.

Writing good OKRs can be hard, especially if it's your first time doing it. You'll need to center the focus of your plans around outcomes instead of projects.

We understand that setting OKRs can be challenging, so we have prepared a set of examples tailored for Security Controls. Take a peek at the templates below to find inspiration and kickstart your goal-setting process.

If you want to learn more about the framework, you can read our OKR guide online.

How to write your own Security Controls OKRs

Option 1. Turn ideas into OKRs with Tability AI

While we have some examples available, it's likely that you'll have specific scenarios that aren't covered here.

You can use Tability's AI generator to create tailored OKRs based on your specific context. Tability can turn your objective description into a fully editable OKR template -- including tips to help you refine your goals.

Tability will then use your prompt to generate a fully editable OKR template.

Watch the video below to see it in action 👇

Option 2. Optimise existing OKRs with Tability Feedback tool

If you already have existing goals, and you want to improve them. You can use Tability's AI feedback to help you.

AI feedback for OKRs in TabilityTability's Strategy Map makes it easy to see all your org's OKRs

Tability will scan your OKRs and offer different suggestions to improve them. This can range from a small rewrite of a statement to make it clearer to a complete rewrite of the entire OKR.

You can then decide to accept the suggestions or dismiss them if you don't agree.

Option 3. Use the free OKR generator

If you're just looking for some quick inspiration, you can also use our free OKR generator to get a template.

Unlike with Tability, you won't be able to iterate on the templates, but this is still a great way to get started.

Security Controls OKRs examples

We've added many examples of Security Controls Objectives and Key Results, but we did not stop there. Understanding the difference between OKRs and projects is important, so we also added examples of strategic initiatives that relate to the OKRs.

Hope you'll find this helpful!

OKRs to establish robust security controls for DHS/ATO and NATO contracts

  • ObjectiveEstablish robust security controls for DHS/ATO and NATO contracts
  • KRConduct quarterly maintenance on all the security controls and document findings
  • TaskDocument observations and any maintenance executed
  • TaskReview all security control systems thoroughly
  • TaskPerform necessary maintenance on security controls
  • KRImplement 5 new security measures aligned with DHS/ATO requirements by a 100%
  • TaskIdentify potential security measures that align with DHS/ATO requirements
  • TaskImplement and test the newly identified security measures
  • TaskReview existing security measures for any DHS/ATO non-compliance
  • KRAchieve zero security breaches related to the NATO contracts information
  • TaskImplement strong encryption on all NATO-related digital communication
  • TaskTrain staff in counter-intelligence and data protection practices
  • TaskRegularly perform rigorous security audits and fix vulnerabilities

OKRs to integrate security controls into development sprints

  • ObjectiveIntegrate security controls into development sprints
  • KRSuccessfully incorporate security controls into two sprints by end of Week 6
  • TaskImplement security controls into sprints in Weeks 4-6
  • TaskDevelop detailed security control integration plans by Week 3
  • TaskIdentify security control requirements for both sprints in Week 1
  • KRFully train the team on security control integration by end of Week 3
  • TaskProvide comprehensive learning materials and resources for the team
  • TaskEvaluate team members' comprehensive understanding by end of Week 3
  • TaskSchedule mandatory team training sessions on security control integration
  • KRAchieve a decrease in security incidents by 40% by end of Week 9
  • TaskImplement a comprehensive cybersecurity training program for all employees
  • TaskFoster a company-wide culture of security vigilance
  • TaskUpgrade existing security infrastructure and software

OKRs to implement and maintain SOCII compliance measures

  • ObjectiveEnsure ongoing SOCII compliance
  • KRConduct regular testing and auditing to assess SOCII compliance status
  • KRTrain and educate all relevant teams on SOCII compliance regulations and best practices
  • KRMonitor and promptly address any SOCII compliance gaps or violations identified
  • TaskEstablish a dedicated team to promptly address and resolve any identified SOCII compliance issues
  • TaskImplement corrective measures to address identified SOCII compliance gaps promptly
  • TaskConduct regular audits to identify any SOCII compliance gaps or violations
  • TaskMaintain a vigilant monitoring system to detect any new SOCII compliance violations
  • KRImplement and maintain necessary controls and processes to meet SOCII requirements
  • TaskConduct initial assessment of current controls and processes to identify gaps
  • TaskDevelop and document new controls and processes to fulfill SOCII requirements
  • TaskRegularly monitor and evaluate controls and processes to ensure ongoing compliance
  • TaskTrain and educate employees on the importance and execution of SOCII controls

Security Controls OKR best practices

Generally speaking, your objectives should be ambitious yet achievable, and your key results should be measurable and time-bound (using the SMART framework can be helpful). It is also recommended to list strategic initiatives under your key results, as it'll help you avoid the common mistake of listing projects in your KRs.

Here are a couple of best practices extracted from our OKR implementation guide 👇

Tip #1: Limit the number of key results

The #1 role of OKRs is to help you and your team focus on what really matters. Business-as-usual activities will still be happening, but you do not need to track your entire roadmap in the OKRs.

We recommend having 3-4 objectives, and 3-4 key results per objective. A platform like Tability can run audits on your data to help you identify the plans that have too many goals.

Tip #2: Commit to weekly OKR check-ins

Don't fall into the set-and-forget trap. It is important to adopt a weekly check-in process to get the full value of your OKRs and make your strategy agile – otherwise this is nothing more than a reporting exercise.

Being able to see trends for your key results will also keep yourself honest.

Tip #3: No more than 2 yellow statuses in a row

Yes, this is another tip for goal-tracking instead of goal-setting (but you'll get plenty of OKR examples above). But, once you have your goals defined, it will be your ability to keep the right sense of urgency that will make the difference.

As a rule of thumb, it's best to avoid having more than 2 yellow/at risk statuses in a row.

Make a call on the 3rd update. You should be either back on track, or off track. This sounds harsh but it's the best way to signal risks early enough to fix things.

How to track your Security Controls OKRs

The rules of OKRs are simple. Quarterly OKRs should be tracked weekly, and yearly OKRs should be tracked monthly. Reviewing progress periodically has several advantages:

We recommend using a spreadsheet for your first OKRs cycle. You'll need to get familiar with the scoring and tracking first. Then, you can scale your OKRs process by using a proper OKR-tracking tool for it.

If you're not yet set on a tool, you can check out the 5 best OKR tracking templates guide to find the best way to monitor progress during the quarter.

More Security Controls OKR templates

We have more templates to help you draft your team goals and OKRs.

Table of contents