Many IT providers say they follow best practice. We would rather show you which practices, by name and version, and what following them means for you. This page is the one place where we keep that list. It names each framework, the version we use today, who publishes it, how it shows up in our work, and where it stops. Since 2017, the year Onward was founded, we have worked to ITIL, the NIST Cybersecurity Framework, the CIS Controls and the OWASP Top 10 for web applications. We also work to four more frameworks in the development and AI work they cover. Today we plan every step of our work and check it against the standards that apply to that step.
Last updated: November 20, 2026.
In short
As of November 20, 2026, Onward Technology Solutions works to eight published frameworks. In our managed IT and security work, we use ITIL 4 for how we run IT service, the NIST Cybersecurity Framework 2.0 for how we organize security outcomes, and the CIS Critical Security Controls v8.1 for the specific safeguards we put in place. In our DevOps, DevSecOps and AI development work, we use the NIST Secure Software Development Framework version 1.1 (SP 800-218, 2022) with its generative AI companion SP 800-218A, OWASP Top 10:2025, the OWASP Top 10 for LLM Applications (2025), the NIST AI Risk Management Framework 1.0 (2023) with its Generative AI Profile (AI 600-1), and the five DORA software delivery metrics. Since 2017, the year Onward was founded, we have worked to ITIL, the NIST Cybersecurity Framework, the CIS Controls and the OWASP Top 10 for web applications. ITIL 4 was released in 2019, and the NIST Cybersecurity Framework 2.0 and the CIS Controls v8.1 in 2024. Today we plan every step of our work and check it against the standards that apply to that step. Every request, incident and change is a ticket with a written plan. Onward claims no certification against any of these eight frameworks, for the company or for any individual. Alignment with a framework is not compliance with a law, regulation or contract. Your quote and service agreement name the systems and services this work applies to.
Managed IT and security: the standards we work to
These three frameworks shape our managed IT and security work for every client, across the systems and services your quote and service agreement name. Every request, incident and change is a ticket with a written plan, and each step names the practice, outcome or safeguard it follows. That reference stays with the work record.
ITIL 4: how we run IT service
Status. A standard we work to in managed IT and security.
What it is. A widely used framework for IT service management. ITIL 4 describes 34 management practices and a set of guiding principles for delivering IT as a service.
Who publishes it. PeopleCert, which owns ITIL. ITIL 4 was released in 2019 and remains available from PeopleCert, which has announced no retirement date for it. PeopleCert began a phased release of ITIL (Version 5) in 2026. Our practice map follows ITIL 4, and we will update it as the new edition settles.
How we apply it. Each step of a plan names the ITIL practice it follows. Incident management covers something that is broken. Service request management covers a new account or a how-to. Change enablement comes before we alter a system. Problem management applies when the same fault keeps returning. Service continuity management covers backups and recovery. IT asset management covers your device and license records. Supplier management applies when one of your vendors is involved. Service levels are written down in your quote and our Services Guide, not implied.
Source. ITIL at PeopleCert.
NIST Cybersecurity Framework 2.0: how we organize security
Status. A standard we work to in managed IT and security.
What it is. A voluntary framework from the US National Institute of Standards and Technology that describes cybersecurity outcomes in six functions: Govern, Identify, Protect, Detect, Respond and Recover.
Who publishes it. NIST. Version 2.0 was released on February 26, 2024, and is the current version.
How we apply it. When we plan a security task, we record which outcome it serves. Knowing which suppliers hold your data is a Govern outcome. Keeping a current record of your devices and software is an Identify outcome. Managing who can sign in, and with what rights, is an access outcome under Protect. A backup step serves the data security outcome under Protect, and so does a recovery test when a plan includes one. Watching devices and sign-ins for unusual activity is a Detect outcome. Handling a security incident follows Respond and Recover. Recovery from a security incident is part of our work where your quote includes it. Covering all six functions is how we check that our work covers the whole picture, not only the parts a tool happens to show.
Source. NIST Cybersecurity Framework.
CIS Critical Security Controls v8.1: the specific safeguards
Status. A standard we work to in managed IT and security.
What it is. A prioritized set of 18 controls, each with specific safeguards, grouped into three Implementation Groups so that a small business can start with the essentials and build from there.
Who publishes it. The Center for Internet Security. Version 8.1 was released on June 25, 2024, and is the current version.
How we apply it. The CIS Controls give us the checklist. Each kind of work in our plans cites the safeguard it serves, by number. The ones our everyday managed IT and security work cites most:
- An inventory of your devices (1.1) and your software (2.1).
- Software its maker no longer supports is identified (2.2) and removed when a plan calls for it (2.3).
- Unique passwords (5.2), administrator rights limited to dedicated accounts (5.4), and multi-factor authentication on applications reached from the internet (6.3).
- Automated patching of operating systems (7.3) and applications (7.4).
- Anti-malware on managed devices (10.1).
- Automated backups and protected recovery data (11.2, 11.3). When a plan includes a recovery test, it cites 11.5.
- Audit logs collected (8.2).
We apply the safeguards that match the services in your quote, on platforms such as Microsoft 365, Windows devices and Cisco Meraki networks. When we recommend a change, we can tell you which safeguard it satisfies and which Implementation Group it belongs to.
Source. CIS Critical Security Controls v8.1.
How the three fit together
ITIL 4 tells us how to run the work: tickets, plans, changes and reviews. The NIST framework tells us which security outcomes the work must cover. The CIS Controls tell us which specific safeguards achieve them. Your quote and service agreement name the systems and services we look after for your business, and the frameworks shape how we deliver it.
Development and AI work: the standards we work to
Some of our work goes beyond running IT: workflow automation, integrations, custom reports, web applications and tools that use AI. Three terms describe that work. DevOps brings software development and IT operations together, with automated build, test and release. DevSecOps builds security into that same pipeline. AI development covers tools that use a language model or another machine learning model. Our DevOps service is built on version control, reviewed changes, automated build and release pipelines, versioned releases and infrastructure defined as code, applied as your engagement needs them.
This work follows the five frameworks below. We list them separately because they apply to a different kind of work: the first three frameworks shape our managed IT and security work for every client, and these five apply when we build or test software, automations, integrations or AI tools for you. We plan each step of that work and check it against the standards that apply to that step.
NIST Secure Software Development Framework v1.1 and SP 800-218A: DevSecOps
Status. A standard we work to in our development work.
What it is. NIST Special Publication 800-218, the SSDF, is a set of secure development practices for the whole software life cycle: preparing the organization, protecting the software, producing well-secured software and responding to vulnerabilities. Its companion, NIST SP 800-218A, extends those practices to generative AI and dual-use foundation models.
Who publishes it. NIST. SSDF version 1.1 was published in February 2022 and is the current final version. SP 800-218A was published in July 2024. NIST published a draft of SSDF version 1.2 in December 2025; its comment period closed in January 2026 and it is not yet final.
How we apply it. The SSDF is the reference for how we build automations, integrations and tools. Code and configuration live in version control. Changes are reviewed before release. Secrets stay out of code. Releases can be rolled back. A reported vulnerability is handled as an incident. When a build includes an AI model, the AI Risk Management Framework below applies as well. SP 800-218A applies when the model is generative AI or a dual-use foundation model.
Source. NIST SP 800-218, SSDF version 1.1 and NIST SP 800-218A.
OWASP Top 10:2025: web application security
Status. A standard we work to in web application testing and in our own web builds.
What it is. The ten most critical web application security risks, ranked from real-world data and updated every few years. The current edition is OWASP Top 10:2025. Its first three risks are broken access control, security misconfiguration and software supply chain failures.
Who publishes it. The OWASP Foundation. OWASP Top 10:2025 is the current released edition.
How we apply it. Web application testing, when it is part of your quote, follows OWASP guidance. Our own web and integration work is checked against the 2025 list before each release.
Source. OWASP Top 10:2025.
OWASP Top 10 for LLM Applications (2025): AI application risks
Status. A standard we work to for tools that use a language model.
What it is. The ten most significant risks in applications built on large language models, such as prompt injection, sensitive information disclosure and excessive agency.
Who publishes it. The OWASP GenAI Security Project, part of the OWASP Foundation. The 2025 list was published in November 2024. A 2026 edition followed; our review follows the 2025 list until our practice moves to the new edition.
How we apply it. Every tool we build that calls a language model is reviewed against the ten risks before it goes live. The review includes what the model is allowed to do on its own, which data it can see, and how prompts and outputs are guarded.
Source. OWASP Top 10 for LLM Applications and the 2026 edition.
NIST AI Risk Management Framework 1.0 and AI 600-1: AI governance
Status. A standard we work to in our AI work.
What it is. A voluntary framework for managing the risks of AI systems through four functions: Govern, Map, Measure and Manage. The Generative AI Profile, NIST AI 600-1, adds the risks and actions specific to generative AI.
Who publishes it. NIST. AI RMF 1.0 was released on January 26, 2023. The Generative AI Profile, NIST AI 600-1, followed on July 26, 2024. NIST has said it is revising the framework and has published no draft; this page names the current published version.
How we apply it. We use it to decide what an AI tool may do, which data it may use and how a person checks its output, and we record those decisions.
Source. NIST AI Risk Management Framework.
DORA metrics: software delivery performance
Status. A standard we work to in our DevOps work.
What it is. DORA, DevOps Research and Assessment, is a long-running research program on software delivery performance. Its five metrics measure delivery throughput and stability: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate.
Who publishes it. The DORA research program. Its current model has five metrics, expanded from the original four.
How we apply it. We measure the five metrics on our automation and development work and report them in plain numbers.
Source. DORA metrics.
How we keep this page current
We name the version of each framework and the date we last reviewed this page. When a publisher releases a new version, we review the change, update our practice where it matters, and then update this page. Three changes are under way at the publishers today: ITIL (Version 5) is in phased release, SSDF version 1.2 is a draft, and NIST has announced a revision of the AI Risk Management Framework. OWASP has also released the 2026 edition of its Top 10 for LLM Applications. Until a release is complete and our practice has moved to it, this page keeps naming the version we use.
What alignment means, and where it stops
Alignment means our work follows these eight frameworks and we can show you where in the work record: the first three in our managed IT and security work for every client, and the five development and AI frameworks when we build or test software, automations, integrations or AI tools for you. Alignment has clear limits.
- No certification. Onward claims no certification against any framework named here, for the company or for any individual. The NIST Cybersecurity Framework and the CIS Controls are frameworks an organization aligns with, not certifications it earns. ITIL has individual qualifications and, through PeopleCert's ITIL Maturity Model, an organizational assessment; we claim neither.
- Not compliance, an audit or legal advice. Alignment does not by itself make your business compliant with any law, regulation or industry rule, such as HIPAA, PCI DSS or the terms of a cyber insurance policy. Compliance is your responsibility, with your advisers. Our work can support it, and we will tell you plainly where it does and where it does not.
- Your quote sets the boundary. The frameworks apply to the systems and services your quote and service agreement name. Systems we do not manage, and your other vendors' systems, are outside that boundary.
- Compliance and data retention, where quoted. Where your quote includes compliance and data retention, our work provides compliance monitoring, reporting and audit support for the frameworks your quote names, such as HIPAA, within that service.
- CMMC and SOC 2. Onward does not offer CMMC services, and it does not perform SOC 2 audits or issue SOC 2 reports. Monitoring, reporting and audit support for a regulatory framework come through the compliance and data retention service above, for the frameworks your quote names. If your business needs a CMMC assessment, the contract or subcontract that requires it sets the level and who performs it. A SOC 2 report comes from an independent CPA firm.
Questions about our standards
Are you certified in ITIL, NIST or CIS?
We claim no certification in ITIL, NIST or CIS, for the company or for any individual. The NIST Cybersecurity Framework and the CIS Controls are frameworks an organization aligns with, not certifications it earns. ITIL has individual qualifications and, through PeopleCert's ITIL Maturity Model, an organizational assessment; we claim neither. What we can show you is the practice, outcome or safeguard that each piece of planned work follows.
Does following these frameworks make my business compliant?
No. Compliance is measured against a law, regulation or contract, such as HIPAA or PCI DSS, and it is your responsibility with your advisers. Working to these frameworks gives you a documented, recognized way of running IT and security that supports compliance. It is not a substitute for an audit.
Do all of these frameworks apply to my business?
ITIL 4, the NIST Cybersecurity Framework 2.0 and the CIS Critical Security Controls v8.1 guide our managed IT and security work for every client, across the systems and services your quote names. The development and AI frameworks apply when we build or test software, automations, integrations or AI tools for you. Since 2017, the year Onward was founded, we have worked to ITIL, the NIST Cybersecurity Framework, the CIS Controls and the OWASP Top 10 for web applications. Today we plan every step of our work and check it against the standards that apply to that step.
Which version of ITIL do you follow?
ITIL 4. PeopleCert began a phased release of ITIL (Version 5) in 2026 and continues to offer ITIL 4. We will update our practice map and this page as the new edition settles.
Do you offer CMMC or SOC 2 services?
We do not offer CMMC services, and we do not perform SOC 2 audits or issue SOC 2 reports. Compliance monitoring, reporting and audit support, where your quote includes compliance and data retention, cover the frameworks your quote names. If your business needs a CMMC assessment, the contract or subcontract that requires it sets the level and who performs it. A SOC 2 report comes from an independent CPA firm.
How do I know a piece of work followed the standard?
Every request, incident and change is a ticket with a written plan, and each step names the practice, outcome or safeguard it follows. The record of what was done and what we checked stays with the ticket. Ask us for it and we will show you.