PSC 7J20

Overview

The Product Service Code (PSC) is the U.S. government’s standard taxonomy for classifying what agencies buy. PSCs support procurement reporting and analytics by identifying the products or services recorded for each contract action in the Federal Procurement Data System (FPDS) and are maintained through the PSC Manual on Acquisition.gov. ¹

PSC 7J20 is defined for “IT and Telecom – Security and Compliance Products (Hardware and Perpetual License Software).” Per the PSC Manual, this code covers hardware and perpetual software licenses for security functions such as Continuous Diagnostics and Mitigation (CDM), vulnerability scanning, firewall management, intrusion prevention, and security information and event management (SIEM). It also includes IT disaster‑recovery tools that enable backup and recovery and dedicated continuity infrastructure such as failover facilities, generators, and UPS systems; implementation activities and DR-designated equipment that belong to other towers are excluded. ²

What this PSC covers

• Security appliances providing network protection (e.g., firewalls and intrusion prevention systems). ²
• Perpetual-license cybersecurity software such as SIEM platforms and vulnerability scanning tools. ²
• CDM-aligned products that support real-time operational security monitoring. ²
• IT disaster‑recovery tools enabling backup, restore, and recovery of systems and data. ²
• Dedicated continuity-of-operations infrastructure, including failover facilities. ²
• Power continuity products used for IT DR, such as generators and uninterruptible power supplies (UPS). ²

Related NAICS and PSC codes

Descriptors are drawn from the PSC Manual’s service and product sections. ²

Scope boundaries and licensing

• Products under 7J20 include hardware and software licensed for use indefinitely (perpetual). Subscription, term, or “as‑a‑service” delivery falls under service PSCs rather than 7J‑product codes. ²
• Disaster‑recovery implementations and equipment that belong to other functional towers (e.g., compute, storage, network) are excluded from 7J20 and should be coded to their respective product PSCs. ²

FPDS reporting note

In FPDS, the PSC identifies what was bought and should reflect the predominant product or service on a given award. This selection principle applies when a buy includes multiple security items or mixes products and services; the PSC should align to the dominant component. ¹

Frequently asked questions

• What distinguishes PSC 7J20 from security services?

  • 7J20 is for products—hardware and perpetual-license software. Security support services are coded under DJ01, while subscription or other “as-a-service” delivery belongs under DJ10. If labor, management, or ongoing operations predominate, use a service PSC instead. ²

• Does 7J20 include generators and UPS for IT continuity?

  • Yes. The PSC Manual explicitly includes generators and UPS systems when they are part of IT disaster‑recovery or continuity infrastructure, alongside failover facilities and other dedicated continuity components tied to security and compliance product scope. Use service codes only when the acquisition is primarily labor or managed services. ²

• Are term‑licensed or subscription security tools coded under 7J20?

  • No. 7J20 covers perpetual licenses. Term licenses, subscriptions, and cloud-delivered offerings are treated as services and align to security “as a service” PSCs such as DJ10, even if software is delivered, because the right-to-use is time-bound. ²

• Is there an official NAICS mapping for 7J20?

  • Not specified by official sources. Agencies typically select NAICS based on the principal nature of the product or service and market research. Coordinate with the contracting officer and use the solicitation’s NAICS if prescribed, ensuring consistency with the predominant acquisition scope. ¹

• How should mixed product/service security buys be coded in FPDS?

  • Choose the PSC that represents the predominant component of the action. If services dominate, use the appropriate service PSC (e.g., DJ01 or DJ10); if products dominate and align to 7J20, use 7J20. Document the rationale in the file for auditability. ¹

Useful resources

• G2X — PSC 7J20 overview
• Product and Service Code (PSC) Manual library on Acquisition.gov. ¹
• PSC Manual April 2025 (current edition), including 7J20 definition. ²
• PSC April 2025 spreadsheet (current PSC data). ³

References

1. Acquisition.gov — Product and Service Code Manual library index, describing PSC purpose and FPDS use: https://www.acquisition.gov/psc-manual
2. Acquisition.gov — PSC Manual April 2025 (PDF), Section D “IT and Telecom – Security and Compliance,” code 7J20 definition and notes: https://login.acquisition.gov/sites/default/files/manual/PSC%20Manual%20April%202025.pdf
3. Acquisition.gov — PSC April 2025.xlsx (current PSC data): https://www.acquisition.gov/content/psc-april-2025.xlsx