Skip to content
-
Subscribe to our newsletter & never miss our best posts. Subscribe Now!
  • https://www.facebook.com/
  • https://twitter.com/
  • https://t.me/
  • https://www.instagram.com/
  • https://youtube.com/
Cloud Security Tips Cloud Security Tips

What is cloud security

Cloud Security Tips Cloud Security Tips

What is cloud security

  • Home
  • About us
  • Contact us
  • Home
  • About us
  • Contact us
Subscribe
Close

Search

Certificate of Networthiness (CoN): What It Is and How to Get One
Security Tips

Certificate of Networthiness (CoN): What It Is and How to Get One

By admin
November 2, 2026 6 Min Read
0

If you want to sell technology or IT services to the United States government, you will quickly meet a term that sounds like a formality but can decide whether you win work: the Certificate of Networthiness, usually shortened to CoN. A certificate of networthiness is an official confirmation that a product, system or service meets the technical, security and interoperability requirements of a particular government network or agency. Without it, an otherwise excellent product may simply not be allowed onto that network.

This guide explains what a CoN is, who issues it, what it covers, how the assessment process works, and the practical steps vendors and agency teams can take to get one. It also explains how a CoN differs from other certifications you may already hold, so you do not mistake one approval for another.

Table of Contents

Toggle
  • What Is a Certificate of Networthiness?
  • Why a CoN Matters
  • What the Assessment Covers
  • CoN vs. Other Certifications
  • How to Get a Certificate of Networthiness: Step by Step
    • 1. Confirm the requirement and the authority
    • 2. Gather your documentation
    • 3. Complete security testing and remediation
    • 4. Submit and respond to assessor questions
    • 5. Receive, maintain and renew the certificate
  • Common Reasons for Delay or Refusal
  • What a CoN Means for Buyers and Users
  • Frequently Asked Questions
    • What is a certificate of networthiness?
    • Who issues a Certificate of Networthiness?
    • How long does it take to get a CoN?
    • Does a CoN expire?
    • Is a CoN the same as an Authority to Operate?

What Is a Certificate of Networthiness?

A Certificate of Networthiness is a formal approval granted after an assessment of whether a technology solution is suitable, secure and supportable on a specific network. The term is most closely associated with the U.S. Army, where the Army’s network enterprise technology command and related authorities assess products before they are fielded on Army networks. Other military services and agencies use similar processes, sometimes under different names, but the underlying idea is the same: prove the product will work safely and reliably in the real operational environment.

Networthiness is broader than ordinary product testing. It looks at security, interoperability, supportability, usability and sustainability together. A product can pass a laboratory security test yet still fail networthiness if it cannot integrate with existing systems, if it creates an unsupportable burden for administrators, or if it depends on software that will soon be unsupported. The certificate therefore answers a practical question: is this solution fit to run on this network, for real users, over time?

Why a CoN Matters

For government customers, a CoN reduces risk. Networks that support defense, emergency response and critical services cannot afford to deploy tools that introduce vulnerabilities, break existing systems or cannot be patched and monitored. The assessment provides documented evidence that a solution has been reviewed against current standards and that known risks have been addressed or accepted by the right authority.

For vendors, a CoN is often a gateway to the market. Many solicitations and deployment approvals require it, and program managers may be unable to authorize purchase or installation without it. Holding a CoN also signals maturity: it shows that the vendor understands government security and interoperability requirements and is prepared to support the product in a demanding environment. That credibility can matter in competitive procurements, even where the certificate is not itself a scored criterion.

What the Assessment Covers

Although the exact checklist varies by agency and network, most networthiness assessments examine the same core areas. Security is central: authentication, encryption, vulnerability management, patching, logging and resistance to common attacks are all reviewed. Assessors check whether the product follows current security baselines, whether default credentials and unnecessary services are removed, and whether it can be monitored by the agency’s security tools.

Interoperability is equally important. A new tool must work with existing identity systems, directories, network services and applications. Assessors test data formats, protocols, bandwidth use and behavior under load. Supportability covers the full lifecycle: documentation, training, help-desk procedures, warranty, spare parts and the vendor’s ability to issue updates for the expected life of the product. Finally, assessors consider usability and mission impact, including how the tool affects workflows and whether administrators can operate it without excessive specialist effort.

CoN vs. Other Certifications

It is easy to confuse a CoN with other approvals, but they serve different purposes and one does not automatically replace another. Understanding the differences saves time and avoids costly assumptions during procurement.

Approval What It Proves Who Typically Requires It
Certificate of Networthiness Suitability for a specific government network Army and similar network authorities
Authority to Operate (ATO) Risk acceptance for a system in a specific environment Authorizing official for that system
SOC 2 report Controls over security, availability and privacy at a service provider Commercial and government customers
Common Criteria / FIPS validation Cryptographic or product assurance against a standard Agencies with specific product requirements

In practice, a vendor may need several of these at once. A strong SOC 2 report, for example, can support a networthiness submission by evidencing mature security controls, but it does not by itself prove that a product integrates safely with a particular network. Likewise, a CoN does not automatically grant an Authority to Operate for a full system, which involves a wider risk assessment of the deployed environment.

How to Get a Certificate of Networthiness: Step by Step

1. Confirm the requirement and the authority

Start by identifying which network, program and authority will assess the product. Ask the government customer or program office for the current networthiness guidance, submission portal and point of contact. Requirements change, so work from the current instruction rather than an older example.

2. Gather your documentation

Prepare a complete package before you submit. This typically includes product descriptions, architecture diagrams, network and data-flow diagrams, security configurations, hardening guides, vulnerability scan results, software bills of materials, support and lifecycle plans, and evidence of any existing certifications. Incomplete packages are a common cause of delay.

3. Complete security testing and remediation

Run the required scans and tests, fix findings, and document any remaining risks with mitigations. Pay special attention to encryption, authentication, patching and logging, because assessors return to these areas repeatedly. Keep evidence organized so assessors can trace each requirement to a test result or configuration.

4. Submit and respond to assessor questions

Submit through the designated channel and expect questions. Assessors may ask for clarifications, additional tests or configuration changes. Respond promptly and precisely, and keep a record of every change you make during the assessment, because those changes become part of the approved baseline.

5. Receive, maintain and renew the certificate

If approved, you will receive the certificate with any conditions, limitations and an expiry period. Maintain it by reporting significant product changes, applying security updates and preparing for renewal well before expiry. A major version change, a new architecture or a change in hosting model may trigger reassessment, so plan product roadmaps with the certificate lifecycle in mind.

Common Reasons for Delay or Refusal

Delays often come from avoidable problems: missing documentation, unpatched vulnerabilities, unsupported dependencies, unclear data flows, or a product that requires broad firewall exceptions or privileged access without justification. Vendors also underestimate the time needed for testing and for coordinating with their own engineering teams. Building networthiness into product design, rather than treating it as a final paperwork exercise, is far more efficient than retrofitting security and interoperability at the end of development.

It also helps to assign a single internal owner for the submission, maintain a checklist mapped to the assessor’s requirements, and test the product in an environment that closely resembles the target network. Early engagement with the assessing authority, where permitted, can surface issues while they are still cheap to fix.

What a CoN Means for Buyers and Users

For buyers, a current CoN is useful evidence, but it is not a substitute for due diligence. Check the certificate’s scope, date and conditions, and confirm that the version you are buying matches the version assessed. Ask how the vendor handles vulnerabilities, how quickly patches are released, and what support is available during deployment. For users, a CoN-backed deployment should mean a tool that has been tested for the network it runs on, with documented support and security controls, rather than an untested addition that creates hidden risk.

Related assurance work follows similar principles. To understand how independent audits evidence security controls, read about SOC 2 Type II audits and why customers ask for them. Infrastructure choices also affect assessment outcomes, as explained in this overview of what data centers are and how they work. And for smaller organizations building the same discipline, this guide to cloud security for small business covers the controls assessors most often expect.

Frequently Asked Questions

What is a certificate of networthiness?

A certificate of networthiness is an official approval confirming that a product or service is suitable, secure and supportable for use on a specific government network after assessment.

Who issues a Certificate of Networthiness?

It is issued by the relevant network authority, most notably for U.S. Army networks, after the product has passed security, interoperability and supportability assessment.

How long does it take to get a CoN?

Timelines vary with product complexity and package quality, but vendors should allow several months for testing, remediation and assessor review, especially for a first submission.

Does a CoN expire?

Yes. Certificates are typically time-limited and conditioned on the assessed version and configuration, so significant changes or expiry may require renewal or reassessment.

Is a CoN the same as an Authority to Operate?

No. A CoN addresses networthiness for a product on a network, while an Authority to Operate is a broader risk decision for a complete system in its operational environment.

Author

admin

Follow Me
Other Articles
IDF room concept: a data center corridor with server racks and glowing network cables
Previous

What Are Data Centers? Types, Components and How They Work

What Is CJIS? Security Policy Levels and Compliance Explained
Next

What Is CJIS? Security Policy Levels and Compliance Explained

No Comment! Be the first one.

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Recent Posts

    • Compliance Risk Assessment: A Complete Guide for 2026
    • SX SFP Module: What It Is, How It Works, and When to Use It
    • Hotspot 2.0 (Wi-Fi Passpoint): What It Is and How It Works
    • Volume Boot Record (VBR): What It Is, How It Works, and How to Fix It
    • Can Website Owners See Who Visits Their Website? What They Can (and Cannot) See

    Recent Comments

    1. Compliance Risk Assessment: A Complete Guide for 2026 on ISO 27001 Compliance: What It Is, How to Get Certified, and How to Stay Compliant
    2. SX SFP Module: What It Is, How It Works & When to Use It on Network Access Control: What It Is, How It Works, Types and Examples
    3. Hotspot 2.0 (Wi-Fi Passpoint): What It Is & How It Works on WIPS: What Is a Wireless Intrusion Prevention System?
    4. Volume Boot Record (VBR): What It Is & How to Fix It on Hypervisor: What It Is, Types, Security Risks and How to Harden It
    5. Can Website Owners See Who Visits? What They See & Can't See on California Consumer Privacy Act (CCPA): What It Is, Your Rights, and How to Comply in 2026

    Archives

    • November 2026
    • October 2026
    • September 2026
    • August 2026
    • July 2026
    • June 2026
    • May 2026
    • February 2026

    Categories

    • Blog
    • Business
    • Security Tips
    • Tech
    • Travel
    • Uncategorized
    Copyright 2026 — Cloud Security Tips. All rights reserved. Blogsy WordPress Theme

    Powered by CookieAdmin
    Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
    None
    Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
    None
    Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
    None
    Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
    None
    Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    None
    Powered by CookieAdmin