Synopsys Enters into Definitive Agreement for Sale of Application Security (Software Integrity Group) Learn More

close search bar

Sorry, not available in this language yet

close language selection

Standards provide the basis for demonstrating compliance with laws, policies, and regulatory guidelines.

Synopsys DevSecOps tools and services can help organizations comply with laws, regulatory guidance, policies, and standards related to application security (AppSec), software quality, data protection, and privacy. Avoid exploits by finding and fixing weaknesses and vulnerabilities using DevSecOps tools that provide detailed reports listing the specific rules and categories of each standard that the tools address.

To help raise the bar for software security and stay informed about the latest security issues, Synopsys employees serve or have served as subject matter experts for the committees, boards, working groups, programs, and projects related to AppSec standards, policies, and regulatory guidelines listed below.

Automotive Industry Action Group

Automotive Industry Action Group (AIAG)

CERT

Carnegie Mellon University Software Engineering Institute (SEI) Computer Emergency Response Team (CERT) Division

CIS WorkBench

CIS WorkBench

Enterprise Singapore

Enterprise Singapore

incits

International Committee for Information Technology Standards (INCITS)

ITU

International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T)

MISRA

Motor Industry Software Reliability Association (MISRA)

Object Management Group

Object Management Group (OMG)

UL (formerly Underwriters Laboratories)

Auto-ISAC

Automotive Information Sharing and Analysis Center (Auto-ISAC)

Center for Internet Security

Center for Internet Security (CIS)

CISQ

Consortium for Information and Software Quality (CISQ)

IEC

International Electrotechnical Commission (IEC)

ISA

International Society of Automation (ISA)

JasPar

Japan Automotive Software Platform and Architecture (JASPAR)

NIST

National Institute of Standards and Technology (NIST)

SAE International

AutoSar

Automotive Open System Architecture (AUTOSAR)

CIS Benchmarks

CIS Benchmarks

CVE

Common Vulnerabilities and Exposures (CVE)

IEEE

Institute of Electrical and Electronics Engineers (IEEE)

ISO

International Standards Organization (ISO)

JNSA

Japan Network Security Association (JNSA)

NTIA

National Telecommunications and Information Administration (NTIA)

Singapore Standards Council

Singapore Standards Council

CAPEC

Common Attack Pattern Enumeration and Classification (CAPEC)

CIS Benchmarks Community

CIS Benchmarks Community

CWE

Common Weakness Enumeration (CWE)

IEEE Technical Committee

IEEE Technical Committee on Electric and Autonomous Vehicles (TC-EAV)

ITI

Information Technology Industry Council (ITI or ITI-C)

METI

Ministry of Economy, Trade, and Industry (METI)

Oasis Open

Organization for the Advancement of Structured Information Standards (OASIS) Open and SARIF

Standards Development Organization

Standards Development Organisation

<p>The <a href="https://www.aiag.org/" target="_blank">Automotive Industry Action Group (AIAG)</a> is a nonprofit organization comprised of original equipment manufacturers (OEMs), suppliers, service providers, government entities, and individuals in academia who work collaboratively to improve quality and reduce costs and complexity in the automotive supply chain. AIAG membership includes leading global manufacturers, parts suppliers, and service providers.</p>

AIAG
Member

The Automotive Industry Action Group (AIAG) is a nonprofit organization comprised of original equipment manufacturers (OEMs), suppliers, service providers, government entities, and individuals in academia who work collaboratively to improve quality and reduce costs and complexity in the automotive supply chain. AIAG membership includes leading global manufacturers, parts suppliers, and service providers.

<p>The <a href="https://automotiveisac.com/" target="_blank">Automotive Information Sharing and Analysis Center (Auto-ISAC)</a> is an industry-driven community that shares and analyzes intelligence about emerging cyber security risks to vehicles and collectively enhances vehicle cyber security capabilities across the global automotive industry, including light- and heavy-duty vehicle OEMs, suppliers, and the commercial vehicle sector. Auto-ISAC defines best practices that are well adopted among OEMs.</p>

Auto-ISAC community
Participant

The Automotive Information Sharing and Analysis Center (Auto-ISAC) is an industry-driven community that shares and analyzes intelligence about emerging cyber security risks to vehicles and collectively enhances vehicle cyber security capabilities across the global automotive industry, including light- and heavy-duty vehicle OEMs, suppliers, and the commercial vehicle sector. Auto-ISAC defines best practices that are well adopted among OEMs.

<p><a href="https://www.autosar.org/" target="_blank">Automotive Open System Architecture (AUTOSAR)</a> is a worldwide development partnership of vehicle manufacturers, suppliers, service providers, and companies from the automotive electronics, semiconductor, and software industries. AUTOSAR standards are used heavily in safety-critical automotive and aircraft applications.</p>
<p>The <a href="https://www.autosar.org/standards/classic-platform/" target="_blank">AUTOSAR Classic Platform</a> defines a standard architecture and API that ensures interoperability across vendor components. It distinguishes on the highest abstraction level between three software layers that run on a microcontroller: application, runtime environment, and basic software. The <a href="https://www.autosar.org/working-groups/classic-platform/" target="_blank">AUTOSAR Classic Platform Working Groups</a> develop and maintain the Classic Platform.</p>
<p>The <a href="https://www.autosar.org/standards/adaptive-platform/" target="_blank">AUTOSAR Adaptive Platform</a> for high-performance computing engine control units (ECUs) implements the AUTOSAR runtime for adaptive applications (ARA). The two types of interfaces include services and APIs. The <a href="https://www.autosar.org/working-groups/adaptive-platform/" target="_blank">AUTOSAR Adaptive Platform Working Groups</a> develop and maintain the Adaptive Platform.</p>
<p>AUTOSAR works closely with ISO/IEC JTC 1/SC 22/WG 14,&nbsp;&nbsp;the ISO C standards committee working group, and ISO/IEC JTC 1/SC 22/WG 21, the ISO C++ standards committee working group.</p>
<p><a></a><a href="https://www.synopsys.com/automotive/misra-autosar-standards.html" target="_blank">AUTOSAR and MISRA</a>&nbsp; announced that their industry standard for best practice in C++ will be integrated into one publication.</p>

AUTOSAR associate partner and working groups
Participant

Automotive Open System Architecture (AUTOSAR) is a worldwide development partnership of vehicle manufacturers, suppliers, service providers, and companies from the automotive electronics, semiconductor, and software industries. AUTOSAR standards are used heavily in safety-critical automotive and aircraft applications.

The AUTOSAR Classic Platform defines a standard architecture and API that ensures interoperability across vendor components. It distinguishes on the highest abstraction level between three software layers that run on a microcontroller: application, runtime environment, and basic software. The AUTOSAR Classic Platform Working Groups develop and maintain the Classic Platform.

The AUTOSAR Adaptive Platform for high-performance computing engine control units (ECUs) implements the AUTOSAR runtime for adaptive applications (ARA). The two types of interfaces include services and APIs. The AUTOSAR Adaptive Platform Working Groups develop and maintain the Adaptive Platform.

AUTOSAR works closely with ISO/IEC JTC 1/SC 22/WG 14,  the ISO C standards committee working group, and ISO/IEC JTC 1/SC 22/WG 21, the ISO C++ standards committee working group.

AUTOSAR and MISRA  announced that their industry standard for best practice in C++ will be integrated into one publication.

<p>The <a href="https://www.cisecurity.org/" target="_blank">Center for Internet Security (CIS)</a> is a community-driven nonprofit responsible for CIS Controls&nbsp;and CIS Benchmarks, globally recognized best practices for securing information technology (IT) systems and data.</p>
<p><a></a><a href="https://www.cisecurity.org/cis-benchmarks/" target="_blank">CIS Benchmarks</a>&nbsp;are consensus-developed, secure configuration guidelines for hardening of the cloud, operating systems, phone devices, applications, and middleware. Developed by cyber security professionals and subject matter experts, CIS Benchmarks are the only consensus-based, best-practice security configuration guides both developed and accepted by government, business, industry, and academia. The <a href="https://www.cisecurity.org/communities/benchmarks/" target="_blank">CIS Benchmarks community</a> develops and updates secure configuration guidelines for technology families.</p>
<p><a></a><a href="https://workbench.cisecurity.org/" target="_blank">CIS WorkBench</a>&nbsp;is a virtual place to network and collaborate with cyber security professionals from around the world. Activities include helping to draft configuration recommendations for the CIS Benchmarks, submitting tickets, and discussing best practices to secure a wide range of technologies.</p>

CIS Benchmarks community and CIS WorkBench
Participant

The Center for Internet Security (CIS) is a community-driven nonprofit responsible for CIS Controls and CIS Benchmarks, globally recognized best practices for securing information technology (IT) systems and data.

CIS Benchmarks are consensus-developed, secure configuration guidelines for hardening of the cloud, operating systems, phone devices, applications, and middleware. Developed by cyber security professionals and subject matter experts, CIS Benchmarks are the only consensus-based, best-practice security configuration guides both developed and accepted by government, business, industry, and academia. The CIS Benchmarks community develops and updates secure configuration guidelines for technology families.

CIS WorkBench is a virtual place to network and collaborate with cyber security professionals from around the world. Activities include helping to draft configuration recommendations for the CIS Benchmarks, submitting tickets, and discussing best practices to secure a wide range of technologies.

<p>The <a href="https://www.it-cisq.org/" target="_blank">Consortium for Information and Software Quality (CISQ)</a> is an industry leadership group that develops international standards to automate the measurement of software size and structural quality from the source code. CISQ standards enable organizations that develop or acquire software-intensive systems to measure the operational risk software poses to the business, as well as estimate the cost of ownership.</p>
<p>CISQ was co-founded by:</p>
<ul>
<li><a href="https://www.omg.org/" target="_blank">Object Management Group (OMG)</a>, an international, open membership, not-for-profit technology standards consortium. OMG standards are driven by vendors, end users, academic institutions, and government agencies. OMG task forces develop enterprise integration standards for a wide range of technologies and industries.</li>
<li><a href="https://www.sei.cmu.edu/" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Software Engineering Institute (SEI)</a><span style="font-family: inherit;"> at Carnegie Mellon University (CMU), a Federally Funded Research and Development Center (FFRDC) sponsored by the U.S. Department of Defense (DOD). FFRDC is a nonprofit, public/private partnership that conducts research for the U.S. government. SEI works with partners throughout the U.S. government, the private sector, and academia. The SEI </span><a href="https://www.sei.cmu.edu/about/divisions/cert/index.cfm" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Computer Emergency Response Team (CERT) Division</a><span style="font-family: inherit;"> partners with government, industry, law enforcement, and academia to improve the security and resilience of computer systems and networks. CERT studies problems that have widespread cyber security implications and develops advanced methods and tools to counter large-scale, sophisticated cyber threats.</span></li>
</ul>
<p><a></a><a href="https://www.it-cisq.org/membership/" target="_blank">CISQ members and sponsors</a>&nbsp;include software engineering, security, and quality management professionals and senior leadership responsible for major mission-critical systems from global enterprises, system integrators, service providers, software technology vendors, and public sector institutions. The CISQ roadmap includes the development of new standards, certification programs, and deployment activities to advance the state of practice in software engineering. CISQ sponsors participate in and influence standards development, including the identification of CISQ projects.</p>
<p><a>The </a><a href="https://www.it-cisq.org/governing-board/" target="_blank">CISQ governing board</a>&nbsp;sets the program direction, including the roadmap for standards development and publication of technical guidance. CISQ projects include the following:</p>
<ul>
<li>The <a href="https://www.it-cisq.org/automated-source-code-measure-data-protection/index.htm" target="_blank">Automated Source Code Data Protection Measure</a> by a CISQ working group is based on a collection of relevant CWEs that support enterprise and supply chain needs to protect data, confidential information, IP, and privacy.</li>
<li><span style="font-family: inherit;">The </span><a style="background-color: rgb(255, 255, 255); font-family: inherit;"></a><a href="https://www.it-cisq.org/software-bill-of-materials/" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Tool-to-Tool Software Bill of Materials Exchange</a><span style="font-family: inherit;">, a joint working group of CISQ, the OMG, and the Software Package Data Exchange (SPDX), develops a standard that defines a software Bill of Materials (BOM or SBOM) and other items needing BOMs.</span></li>
<li>The <a href="https://www.it-cisq.org/devops-productivity-and-efficiency-measures/index.htm" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Architecture and Flow Measures for Modernization and DevOps Pipelines</a><span style="font-family: inherit;"> working group develops international standards for a new generation of software measures targeted at DevOps and modernization.</span></li>
<li>“<a href="/content/synopsys/en-us/software-integrity/resources/analyst-reports/cost-poor-quality-software.html" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">The Cost of Poor Software Quality in the U.S.: A 2020 Report</a><span style="font-family: inherit;">” quantifies the impact of poor software quality on the U.S. economy referencing publicly available source material.</span></li>
</ul>

CISQ governing boards, working groups, and projects
Sponsor, participant

The Consortium for Information and Software Quality (CISQ) is an industry leadership group that develops international standards to automate the measurement of software size and structural quality from the source code. CISQ standards enable organizations that develop or acquire software-intensive systems to measure the operational risk software poses to the business, as well as estimate the cost of ownership.

CISQ was co-founded by:

  • Object Management Group (OMG), an international, open membership, not-for-profit technology standards consortium. OMG standards are driven by vendors, end users, academic institutions, and government agencies. OMG task forces develop enterprise integration standards for a wide range of technologies and industries.
  • Software Engineering Institute (SEI) at Carnegie Mellon University (CMU), a Federally Funded Research and Development Center (FFRDC) sponsored by the U.S. Department of Defense (DOD). FFRDC is a nonprofit, public/private partnership that conducts research for the U.S. government. SEI works with partners throughout the U.S. government, the private sector, and academia. The SEI Computer Emergency Response Team (CERT) Division partners with government, industry, law enforcement, and academia to improve the security and resilience of computer systems and networks. CERT studies problems that have widespread cyber security implications and develops advanced methods and tools to counter large-scale, sophisticated cyber threats.

CISQ members and sponsors include software engineering, security, and quality management professionals and senior leadership responsible for major mission-critical systems from global enterprises, system integrators, service providers, software technology vendors, and public sector institutions. The CISQ roadmap includes the development of new standards, certification programs, and deployment activities to advance the state of practice in software engineering. CISQ sponsors participate in and influence standards development, including the identification of CISQ projects.

The CISQ governing board sets the program direction, including the roadmap for standards development and publication of technical guidance. CISQ projects include the following:

<p>The study groups of the <a href="https://www.itu.int/en/ITU-T/about/Pages/default.aspx" target="_blank">International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T)</a> assemble experts from around the world to develop international standards known as ITU-T recommendations that act as defining elements in the global infrastructure of information and communication technologies (ICTs).</p>
<p>ITU-T SG 17 adopted the <a href="https://www.itu.int/en/ITU-T/studygroups/com17/Pages/cybex.aspx" target="_blank">Cybersecurity Information Exchange (CYBEX)</a> framework initiative that imports best-of-breed standards for platforms developed by government agencies and industry to enhance cyber security and infrastructure protection. The ITU-T CYBEX X.1500 standard series includes:</p>
<ul>
<li><a href="https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=12040&amp;lang=en" target="_blank">ITU-T X.1520</a> based on the <a href="http://cve.mitre.org/" target="_blank">Common Vulnerabilities and Exposures (CVE) list</a>, which includes records for publicly known vulnerabilities used in numerous global cyber security products and services such as the U.S. National Vulnerability Database (NVD)</li>
<li><a href="https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=11374" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">ITU-T X.1524</a><span style="font-family: inherit;"> based on the </span><a href="https://cwe.mitre.org/" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Common Weakness Enumeration (CWE) list</a><span style="font-family: inherit;">, which is a community-developed list of software and hardware weakness types that serves as a common language, measuring stick for security tools, and baseline for weakness identification, mitigation, and prevention efforts</span></li>
<li><a href="https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=11753" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">ITU-T X.1544</a><span style="font-family: inherit;"> based on the </span><a href="https://capec.mitre.org/" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">Common Attack Pattern Enumeration and Classification (CAPEC) list</a><span style="font-family: inherit;">, which is a publicly available catalog of common attack patterns that helps users understand how adversaries exploit weaknesses in applications and other cyber-enabled capabilities</span></li>
</ul>
<p>CVE, CWE, and CAPEC are sponsored by the U.S. Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA) and managed by the Homeland Security Systems Engineering and Development Institute (HSSEDI), which is operated by MITRE.</p>
<p><a></a><a href="https://cve.mitre.org/cve/request_id.html#cna_participants" target="_blank">CVE numbering authorities (CNAs)</a>&nbsp; are global organizations authorized to assign CVE IDs to vulnerabilities that affect products within their distinct, agreed-upon scope for inclusion in first-time public announcements of new vulnerabilities. These CVE IDs are provided to researchers, vulnerability disclosers, and IT vendors.</p>
<p>The <a></a><a href="http://cve.mitre.org/community/board/index.html" target="_blank">CVE board</a>&nbsp;is comprised of numerous cyber security–related organizations and provides critical input regarding the data sources, product coverage, coverage goals, operating structure, and strategic direction of the CVE list.</p>
<p><a></a><a href="https://cwe.mitre.org/about/board.html" target="_blank">CWE/CAPEC board</a>&nbsp;members include technical implementers, subject matter experts, and advocates who provide critical input regarding domain coverage, coverage goals, operating structure, and strategic direction for the CWE and CAPEC lists.</p>

CVE numbering authority, CVE board, and CWE/CAPEC board
Member

The study groups of the International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T) assemble experts from around the world to develop international standards known as ITU-T recommendations that act as defining elements in the global infrastructure of information and communication technologies (ICTs).

ITU-T SG 17 adopted the Cybersecurity Information Exchange (CYBEX) framework initiative that imports best-of-breed standards for platforms developed by government agencies and industry to enhance cyber security and infrastructure protection. The ITU-T CYBEX X.1500 standard series includes:

CVE, CWE, and CAPEC are sponsored by the U.S. Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA) and managed by the Homeland Security Systems Engineering and Development Institute (HSSEDI), which is operated by MITRE.

CVE numbering authorities (CNAs)  are global organizations authorized to assign CVE IDs to vulnerabilities that affect products within their distinct, agreed-upon scope for inclusion in first-time public announcements of new vulnerabilities. These CVE IDs are provided to researchers, vulnerability disclosers, and IT vendors.

The CVE board is comprised of numerous cyber security–related organizations and provides critical input regarding the data sources, product coverage, coverage goals, operating structure, and strategic direction of the CVE list.

CWE/CAPEC board members include technical implementers, subject matter experts, and advocates who provide critical input regarding domain coverage, coverage goals, operating structure, and strategic direction for the CWE and CAPEC lists.

<p>The <a href="https://www.iec.ch/" target="_blank">International Electrotechnical Commission (IEC)</a> is an international standards organization that prepares and publishes international standards for all electrical, electronic, and related technologies.</p>
<p>IEC develops many standards through joint technical committees including:</p>
<ul>
<li>ISA99 committee&nbsp; &nbsp; &nbsp; &nbsp;<br>
</li>
<li>ISO/IEC technical committees and working groups for programming languages</li>
<li>ISO/IEC technical committee and working group for IT, cyber security, and privacy protection</li>
<li>ISO/IEC technical committee for software and systems engineering</li>
</ul>

IEC committees and working groups
Member

The International Electrotechnical Commission (IEC) is an international standards organization that prepares and publishes international standards for all electrical, electronic, and related technologies.

IEC develops many standards through joint technical committees including:

  • ISA99 committee       ,
  • ISO/IEC technical committees and working groups for programming languages
  • ISO/IEC technical committee and working group for IT, cyber security, and privacy protection
  • ISO/IEC technical committee for software and systems engineering
<p>The <a href="https://www.ieee.org/" target="_blank">Institute of Electrical and Electronics Engineers (IEEE)</a> is a technical professional organization dedicated to advancing technology for the benefit of humanity.</p>
<p>The <a href="https://standards.ieee.org/about/corpchan/shwcse/synopsys.html" target="_blank">IEEE Standards Association (IEEE SA)</a> is a consensus-building organization that nurtures, develops, and advances global technologies through IEEE by bringing together a broad range of individuals and organizations to facilitate standards development and standards-related collaboration.</p>
<p>The <a href="https://standards.ieee.org/about/corpchan/index.html" target="_blank">IEEE SA corporate program</a> facilitates the exploration of new standards opportunities at IEEE, supporting the development of projects around the full life cycle of standards. Its international presence allows for a broad-based focus on new work areas and programs.</p>
<p>The <a href="http://ieee-eav.org/index.html" target="_blank">IEEE technical committee on electric and autonomous vehicles (TC-EAV)</a>&nbsp;under the IEEE Reliability Society (RS) brings researchers and practitioners together for interdisciplinary collaborations among academia, industry, and government agencies, including both private and public sectors in areas such as software engineering, communications and networking, computer visions, artificial intelligence and machine learning, cyber-physical systems, testing, validation, and formal verification.</p>

IEEE SA advanced corporate program and EAV technical committee
Member

The Institute of Electrical and Electronics Engineers (IEEE) is a technical professional organization dedicated to advancing technology for the benefit of humanity.

The IEEE Standards Association (IEEE SA) is a consensus-building organization that nurtures, develops, and advances global technologies through IEEE by bringing together a broad range of individuals and organizations to facilitate standards development and standards-related collaboration.

The IEEE SA corporate program facilitates the exploration of new standards opportunities at IEEE, supporting the development of projects around the full life cycle of standards. Its international presence allows for a broad-based focus on new work areas and programs.

The IEEE technical committee on electric and autonomous vehicles (TC-EAV) under the IEEE Reliability Society (RS) brings researchers and practitioners together for interdisciplinary collaborations among academia, industry, and government agencies, including both private and public sectors in areas such as software engineering, communications and networking, computer visions, artificial intelligence and machine learning, cyber-physical systems, testing, validation, and formal verification.

<p>The <a href="https://www.incits.org/" target="_blank">International Committee for Information Technology Standards (INCITS</a>)<a></a> is the U.S. forum dedicated to creating technology standards for the next generation of innovation. <a href="https://standards.incits.org/public/members" target="_blank">INCITS members</a> combine their expertise to create the building blocks for globally transformative technologies, from cloud computing to communications, from transportation to healthcare.</p>
<p>INCITS serves as the <a href="https://www.ansi.org/iso/ansi-activities/us-tags" target="_blank">U.S. Technical Advisory Group (TAG)</a> for ISO/IEC Joint Technical Committee 1.&nbsp;A U.S. TAG is a committee accredited by the <a href="https://www.ansi.org/" target="_blank">American National Standards Institute (ANSI)</a> to participate in ISO/IEC technical activities. ANSI-accredited U.S. TAGs include the range of U.S. parties interested in and affected by specific ISO/IEC standards.</p>

INCITS
Member

The International Committee for Information Technology Standards (INCITS) is the U.S. forum dedicated to creating technology standards for the next generation of innovation. INCITS members combine their expertise to create the building blocks for globally transformative technologies, from cloud computing to communications, from transportation to healthcare.

INCITS serves as the U.S. Technical Advisory Group (TAG) for ISO/IEC Joint Technical Committee 1. A U.S. TAG is a committee accredited by the American National Standards Institute (ANSI) to participate in ISO/IEC technical activities. ANSI-accredited U.S. TAGs include the range of U.S. parties interested in and affected by specific ISO/IEC standards.

<p>The <a href="https://www.isa.org/" target="_blank">International Society of Automation (ISA)</a> is a professional nonprofit association that develops widely used global standards, certifies industry professionals, provides education and training, publishes books and technical articles, hosts conferences and exhibits, and provides networking and career development programs for its global members and customers.</p>
<p>The <a href="https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees/isa99" target="_blank">ISA99 committee</a> brings together global industrial cyber security experts to develop ISA standards on industrial automation and control systems security. It draws on the input and knowledge of global industrial automation and control systems (IACS) security experts to develop consensus standards that are applicable to all industry sectors and critical infrastructure.</p>
<p>The ISA99 committee develops a series of standards adopted by the IEC including the <a href="https://www.isa.org/intech-home/2018/september-october/departments/new-standard-specifies-security-capabilities-for-c" target="_blank">ISA/IEC 62443</a> series of standards, which provide a flexible framework to address and mitigate current and future security vulnerabilities in IACS.</p>

ISA99 committee
Member

The International Society of Automation (ISA) is a professional nonprofit association that develops widely used global standards, certifies industry professionals, provides education and training, publishes books and technical articles, hosts conferences and exhibits, and provides networking and career development programs for its global members and customers.

The ISA99 committee brings together global industrial cyber security experts to develop ISA standards on industrial automation and control systems security. It draws on the input and knowledge of global industrial automation and control systems (IACS) security experts to develop consensus standards that are applicable to all industry sectors and critical infrastructure.

The ISA99 committee develops a series of standards adopted by the IEC including the ISA/IEC 62443 series of standards, which provide a flexible framework to address and mitigate current and future security vulnerabilities in IACS.

<p>The <a href="https://www.iso.org/home.html" target="_blank">International Standards Organization (ISO)</a> is an independent, nongovernmental, international&nbsp;organization of national standards bodies. Through its members, it brings together experts to share&nbsp;knowledge and develop voluntary, consensus-based, market-relevant international standards that support&nbsp;innovation and provide solutions to global challenges. ISO standards are developed by <a href="https://www.iso.org/technical-committees.html" target="_blank">ISO technical&nbsp;<span style="font-size: 0.8125rem;">committees</span></a><span style="font-size: 0.8125rem;">.</span></p>
<p><b>ISO/IEC technical committees for programming languages</b></p>
<p>The ISO/IEC <a href="http://www.iso.org/iso/standards_development/technical_committees/list_of_iso_technical_committees/iso_technical_committee.htm?commid=45020" target="_blank">Joint Technical Committee 1 (JTC 1)</a> <a href="http://www.iso.org/iso/standards_development/technical_committees/list_of_iso_technical_committees/iso_technical_committee.htm?commid=45202" target="_blank">Subcommittee 22 (SC 22)</a> is the international standardization subcommittee for programming languages, their environments, and system software interfaces. SC 22 is also known as the portability subcommittee. JTC 1/SC 22 has working groups (WGs) for various programming languages including:</p>
<ul>
<li><a></a><a href="http://www.open-std.org/jtc1/sc22/wg14/" target="_blank">ISO/IEC JTC 1/SC 22/WG 14</a>, the ISO C standards committee working group</li>
<li><a href="http://www.open-std.org/jtc1/sc22/wg21/" target="_blank">ISO/IEC JTC 1/SC 22/WG 21</a>, the <a href="https://isocpp.org/std/the-committee" target="_blank">ISO C++ standards committee (ISOCPP)</a> working group organized into a three-stage pipeline consisting of several subgroups or study groups, such as <a href="https://github.com/sg16-unicode/sg16" target="_blank">SG 16</a> for topics related to Unicode text processing in C++, that develops standards like <a href="https://www.iso.org/standard/79358.html" target="_blank">ISO/IEC 14882 C++ programming languages</a></li>
<li><a href="http://www.open-std.org/jtc1/sc22/wg23/" target="_blank">ISO/IEC JTC 1/SC 22/WG 23</a>, the ISO programming language vulnerabilities standards committee working group that develops TR 24772 for various programming languages</li>
</ul>
<p><b>ISO/IEC technical committee for IT, cyber security, and privacy protection</b></p>
<p>INCITS serves as the U.S. TAG to <a href="https://www.iso.org/committee/45306.html" target="_blank">ISO/IEC JTC 1/SC 27 for information security, cyber security, and privacy protection</a>. <a href="https://isotc.iso.org/livelink/livelink?func=ll&amp;objId=8916713&amp;objAction=browse&amp;sort=name" target="_blank">ISO/IEC JTC 1/SC 27/WG 3 security evaluation, testing and specification</a>&nbsp; codevelops standards for the protection of information and ICT including:</p>
<ul>
<li><a href="https://www.iso.org/standard/59648.html" target="_blank">ISO/IEC 27036 information security for supplier relationships standard for IT and security techniques</a>, a multipart supply chain standard that offers guidance on the evaluation and treatment of information risks involved in the acquisition of goods and services from suppliers</li>
<li><a href="https://www.iso.org/standard/72311.html" style="background-color: rgb(255, 255, 255); font-size: 0.8125rem;" target="_blank">ISO/IEC 29147 vulnerability standard for information technology and security techniques</a><span style="font-size: 0.8125rem;">, which provides requirements and recommendations to vendors on the disclosure of vulnerabilities in products and services</span></li>
</ul>
<p><b>ISO/IEC technical committee for software and systems engineering</b></p>
<p><a href="https://www.iso.org/committee/45086.html" target="_blank">ISO/IEC JTC 1/SC 7 for software and systems engineering</a> develops standards for processes, supporting tools, and supporting technologies for the engineering of software products and systems including <a href="https://www.iso.org/standard/73567.html" target="_blank">ISO/IEC/IEEE 15026</a>&nbsp;systems and software assurance<a></a>, which defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance.</p>
<p><b>ISO technical committee for E/E components and general system aspects</b></p>
<p><a href="https://www.iso.org/committee/5383636.html" target="_blank">ISO/TC 22/SC 32 for electrical and electronic (E/E) components and general system aspects</a> develops standards for E/E components and cross-sectional specifications for E/E systems and components including:</p>
<ul>
<li><a href="https://www.synopsys.com/automotive/what-is-iso-26262.html" target="_blank">ISO 26262 functional safety standard for road vehicles</a>, a multipart standard for safety-related systems that include one or more E/E systems and are installed in series production passenger cars</li>
<li><a href="https://www.iso.org/standard/77796.html" target="_blank">ISO/CD 24089 software update engineering standard for road vehicles</a>, which specifies requirements for cyber security risk management regarding engineering for concept, development, production, operation, maintenance, and decommissioning for road vehicle E/E systems, including their components and interfaces</li>
<li><a href="https://www.iso.org/standard/70918.html" target="_blank">ISO/SAE 21434 cyber security engineering standard for road vehicles</a>, which builds upon SAE J3061 and provides a similar framework for the entire life cycle of road vehicles</li>
</ul>

ISO technical committees and working groups
Member

The International Standards Organization (ISO) is an independent, nongovernmental, international organization of national standards bodies. Through its members, it brings together experts to share knowledge and develop voluntary, consensus-based, market-relevant international standards that support innovation and provide solutions to global challenges. ISO standards are developed by ISO technical committees.

ISO/IEC technical committees for programming languages

The ISO/IEC Joint Technical Committee 1 (JTC 1) Subcommittee 22 (SC 22) is the international standardization subcommittee for programming languages, their environments, and system software interfaces. SC 22 is also known as the portability subcommittee. JTC 1/SC 22 has working groups (WGs) for various programming languages including:

ISO/IEC technical committee for IT, cyber security, and privacy protection

INCITS serves as the U.S. TAG to ISO/IEC JTC 1/SC 27 for information security, cyber security, and privacy protection. ISO/IEC JTC 1/SC 27/WG 3 security evaluation, testing and specification  codevelops standards for the protection of information and ICT including:

ISO/IEC technical committee for software and systems engineering

ISO/IEC JTC 1/SC 7 for software and systems engineering develops standards for processes, supporting tools, and supporting technologies for the engineering of software products and systems including ISO/IEC/IEEE 15026 systems and software assurance, which defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance.

ISO technical committee for E/E components and general system aspects

ISO/TC 22/SC 32 for electrical and electronic (E/E) components and general system aspects develops standards for E/E components and cross-sectional specifications for E/E systems and components including:

<p>The <a href="https://www.itic.org/" target="_blank">Information Technology Industry Council (ITI or ITI-C)</a> is a global advocate for technology. ITI promotes public policies and industry standards that advance competition and innovation worldwide. <a href="https://www.itic.org/about/membership/iti-members" target="_blank">ITI members</a> include the world's leading innovation companies.</p>

ITI
Member

The Information Technology Industry Council (ITI or ITI-C) is a global advocate for technology. ITI promotes public policies and industry standards that advance competition and innovation worldwide. ITI members include the world's leading innovation companies.

<p>The <a href="https://www.jaspar.jp/en" target="_blank">Japan Automotive Software Platform and Architecture (JASPAR)</a> enables the standardization of electronic control systems and software for in-vehicle networks, thereby allowing industrywide common implementation, more efficient development, and increased reliability. Topics include E/E cyber security.</p>
<p>The <a href="https://www.jaspar.jp/english/activitiesWorkingGroups" target="_blank">JASPAR cyber security technical working group</a> works to define and validate the requirements of automotive cyber security technologies based on use cases, including projects like the “A-CST-07-0003 Fuzzing Test Guide.”</p>

JASPAR cyber security technical working group
Participant

The Japan Automotive Software Platform and Architecture (JASPAR) enables the standardization of electronic control systems and software for in-vehicle networks, thereby allowing industrywide common implementation, more efficient development, and increased reliability. Topics include E/E cyber security.

The JASPAR cyber security technical working group works to define and validate the requirements of automotive cyber security technologies based on use cases, including projects like the “A-CST-07-0003 Fuzzing Test Guide.”

<p>The <a href="https://www.jnsa.org/en/aboutus/" target="_blank">Japan Network Security Association (JNSA)</a> is a nonprofit organization that promotes network security standardization. JNSA is comprised of working groups including the <a href="https://www.jnsa.org/en/activities/committee.html" target="_blank">Survey and Research Committee IoT security working group</a>, which undertakes survey activities and research on information security issues.</p>

JNSA IoT security working group
Participant

The Japan Network Security Association (JNSA) is a nonprofit organization that promotes network security standardization. JNSA is comprised of working groups including the Survey and Research Committee IoT security working group, which undertakes survey activities and research on information security issues.

<p>The <a href="https://www.meti.go.jp/english/" target="_blank">Ministry of Economy, Trade, and Industry (METI)</a> helps develop the Japanese economy and industry by promoting economic vitality in private companies and advancing external economic relationships. METI also secures a stable and efficient supply of energy and mineral resources.</p><p>METI ensures security in the new supply chains (value creation processes) under the national <a href="https://www8.cao.go.jp/cstp/english/society5_0/index.html" target="_blank">Society 5.0</a> policy by integrating cyber space and physical space, as well as the national <a href="https://www.meti.go.jp/english/policy/mono_info_service/connected_industries/index.html" target="_blank">Connected Industries</a> policy for adding new value by connecting a variety of goods, industries, and people. METI develops the <a href="https://www.meti.go.jp/english/press/2019/0418_001.html" target="_blank">Cyber-Physical Security Framework (CPSF)</a>, an overview of required security measures.</p><p>The METI <a></a><a href="https://www.meti.go.jp/shingikai/mono_info_service/sangyo_cyber/wg_seido/wg_bunyaodan/index.html" target="_blank">WG 1 for systems, technologies, and standardization cross-disciplinary subworking group</a>&nbsp;under the <a href="https://www.meti.go.jp/shingikai/mono_info_service/sangyo_cyber/index.html" target="_blank">industrial cyber security study group</a> holds discussions on cyber-physical security measures to achieve security in the new supply chains under the Society 5.0 and Connected Industries policies. The <a href="https://www.meti.go.jp/shingikai/mono_info_service/sangyo_cyber/wg_seido/wg_bunyaodan/software/index.html" target="_blank">Task Force for Examining Software Management Methods for Ensuring Cyber-Physical Security</a> discusses SBOM to identify problems and bring them to the foreground, especially vulnerability in the supply chain.</p>

METI industrial cyber security study group, working group, and task force
Participant

The Ministry of Economy, Trade, and Industry (METI) helps develop the Japanese economy and industry by promoting economic vitality in private companies and advancing external economic relationships. METI also secures a stable and efficient supply of energy and mineral resources.

METI ensures security in the new supply chains (value creation processes) under the national Society 5.0 policy by integrating cyber space and physical space, as well as the national Connected Industries policy for adding new value by connecting a variety of goods, industries, and people. METI develops the Cyber-Physical Security Framework (CPSF), an overview of required security measures.

The METI WG 1 for systems, technologies, and standardization cross-disciplinary subworking group under the industrial cyber security study group holds discussions on cyber-physical security measures to achieve security in the new supply chains under the Society 5.0 and Connected Industries policies. The Task Force for Examining Software Management Methods for Ensuring Cyber-Physical Security discusses SBOM to identify problems and bring them to the foreground, especially vulnerability in the supply chain.

<p>The <a href="https://www.synopsys.com/automotive/what-is-misra.html" target="_blank">Motor Industry Software Reliability Association (MISRA)</a> is a collaboration between vehicle manufacturers, component suppliers, and engineering consultancies that seek to promote best practices for developing safety-related electronic systems in road vehicles and aircraft.</p>
<p>MISRA works closely with ISO/IEC JTC 1/SC 22/WG 14, the ISO C standards committee working group, and ISO/IEC JTC 1/SC 22/WG 21, the ISO C++ standards committee working group.</p>
<p><a href="https://www.synopsys.com/automotive/misra-autosar-standards.html" target="_blank">MISRA and AUTOSAR</a> announced that their industry standard for best practice in C++ will be integrated into one publication.</p>

MISRA steering committee
Participant

The Motor Industry Software Reliability Association (MISRA) is a collaboration between vehicle manufacturers, component suppliers, and engineering consultancies that seek to promote best practices for developing safety-related electronic systems in road vehicles and aircraft.

MISRA works closely with ISO/IEC JTC 1/SC 22/WG 14, the ISO C standards committee working group, and ISO/IEC JTC 1/SC 22/WG 21, the ISO C++ standards committee working group.

MISRA and AUTOSAR announced that their industry standard for best practice in C++ will be integrated into one publication.

<p>The <a href="https://www.nist.gov/" target="_blank">National Institute of Standards and Technology (NIST)</a> is a physical sciences laboratory and a nonregulatory agency of the U.S. Department of Commerce that promotes innovation and industrial competitiveness.</p>
<p>U.S. policies are created when the Office of Management and Budget (OMB) takes executive orders and turns them into mandates or policies that point to the NIST special publications (SPs), including the <a href="https://www.nist.gov/itl/publications-0/nist-special-publication-800-series-general-information" target="_blank">NIST SP 800 series</a> for the computer security community such as <a href="https://csrc.nist.gov/publications/detail/sp/800-161/final" target="_blank">NIST SP 800-161 Supply Chain Risk Management Practices for Federal Information Systems and Organizations</a>, which provides guidance to federal agencies on identifying, assessing, and mitigating ICT supply chain risks at all levels of their organizations.</p>
<p>The NIST <a href="https://csrc.nist.gov/projects/security-content-automation-protocol" target="_blank">Security Content Automation Protocol (SCAP)</a> is a synthesis of interoperable specifications derived from community ideas. Part of the NIST SCAP uses the CVE, CWE and CAPEC lists.</p>

NIST special publications
Contributor

The National Institute of Standards and Technology (NIST) is a physical sciences laboratory and a nonregulatory agency of the U.S. Department of Commerce that promotes innovation and industrial competitiveness.

U.S. policies are created when the Office of Management and Budget (OMB) takes executive orders and turns them into mandates or policies that point to the NIST special publications (SPs), including the NIST SP 800 series for the computer security community such as NIST SP 800-161 Supply Chain Risk Management Practices for Federal Information Systems and Organizations, which provides guidance to federal agencies on identifying, assessing, and mitigating ICT supply chain risks at all levels of their organizations.

The NIST Security Content Automation Protocol (SCAP) is a synthesis of interoperable specifications derived from community ideas. Part of the NIST SCAP uses the CVE, CWE and CAPEC lists.

<p>The <a href="https://www.ntia.doc.gov/" target="_blank">National Telecommunications and Information Administration (NTIA)</a>, located within the U.S. Department of Commerce, is the executive branch agency that is principally responsible by law for advising the President on telecommunications and information policy issues.</p>
<p>Stakeholders in <a href="https://www.ntia.doc.gov/SoftwareTransparency" target="_blank">NTIA software component transparency working groups</a> collaborate in an open and transparent process to address transparency around software components and advocate for software transparency throughout the supply chain, including <a href="https://www.ntia.doc.gov/SBOM" target="_blank">SBOM</a> standards. An SBOM is a list of all the open-source and third-party components present in a codebase, the licenses that govern those components, the versions of the components used in the codebase, and their patch status.</p>
<ul>
<li><a href="https://lists.sei.cmu.edu/mailman/listinfo/ntia-sbom-framing" target="_blank">NTIA SBOM framing working group</a> defines and refines the specification of SBOMs, with attention to broader, more scalable adoption obstacles. Topics include component identity and naming, how to share SBOMs, how to characterize nonexploitability vs. vulnerability, SBOM integrity and high-assurance data, SBOMs for the cloud/SaaS, and more.</li>
<li><a href="https://lists.sei.cmu.edu/mailman/listinfo/ntia-sbom-practices" target="_blank">NTIA SBOM awareness and adoption working group</a> promotes SBOM as an idea and a practice. Tasks include building a broader outreach strategy with outreach targets; creating shorter documents with specific outreach goals for sectors, organizational role, and so on; coordinating with related efforts; and providing more explicit business cases for SBOM adoption.</li>
<li><a href="https://lists.linuxfoundation.org/mailman/listinfo/ntia-sbom-formats" target="_blank">NTIA SBOM data formats and tooling working group</a> focuses on how to automate SBOM production and use. Goals include cataloging existing tools for SBOMs in the identified standards, developing a translator between these formats, providing a gap analysis in SBOM tools, and potentially exploring SBOM processes and playbooks.</li>
<li><a href="https://lists.sei.cmu.edu/mailman/listinfo/ntia-sbom-healthcare" target="_blank">NTIA SBOM healthcare proof of concept working group</a> plans and executes a second proof-of-concept exercise with an expanded set of healthcare participants and the inclusion of IT and security industry partners. It also advises other industry players interested in SBOM demonstrations.</li>
</ul>

NTIA software component transparency working groups
Member

The National Telecommunications and Information Administration (NTIA), located within the U.S. Department of Commerce, is the executive branch agency that is principally responsible by law for advising the President on telecommunications and information policy issues.

Stakeholders in NTIA software component transparency working groups collaborate in an open and transparent process to address transparency around software components and advocate for software transparency throughout the supply chain, including SBOM standards. An SBOM is a list of all the open-source and third-party components present in a codebase, the licenses that govern those components, the versions of the components used in the codebase, and their patch status.

  • NTIA SBOM framing working group defines and refines the specification of SBOMs, with attention to broader, more scalable adoption obstacles. Topics include component identity and naming, how to share SBOMs, how to characterize nonexploitability vs. vulnerability, SBOM integrity and high-assurance data, SBOMs for the cloud/SaaS, and more.
  • NTIA SBOM awareness and adoption working group promotes SBOM as an idea and a practice. Tasks include building a broader outreach strategy with outreach targets; creating shorter documents with specific outreach goals for sectors, organizational role, and so on; coordinating with related efforts; and providing more explicit business cases for SBOM adoption.
  • NTIA SBOM data formats and tooling working group focuses on how to automate SBOM production and use. Goals include cataloging existing tools for SBOMs in the identified standards, developing a translator between these formats, providing a gap analysis in SBOM tools, and potentially exploring SBOM processes and playbooks.
  • NTIA SBOM healthcare proof of concept working group plans and executes a second proof-of-concept exercise with an expanded set of healthcare participants and the inclusion of IT and security industry partners. It also advises other industry players interested in SBOM demonstrations.
<p>The <a href="https://www.oasis-open.org/" target="_blank">Organization for the Advancement of Structured Information Standards (OASIS)</a> aims to set the standard for open collaboration. OASIS Open is where individuals, organizations, and governments come together to solve technical challenges through the development of open code and open standards.</p>
<p>The <a href="https://sarifweb.azurewebsites.net/" target="_blank">Static Analysis Results Interchange Format (SARIF)</a> is an industry standard format for the output of static analysis tools. SARIF is an approved OASIS standard. It enables organizations in the safety and security communities to combine and compare the results from multiple competing tools more easily for a more accurate picture of their code issues.</p>
<p><a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif" target="_blank">OASIS SARIF technical committee</a> members develop the SARIF interoperability standard for detecting software defects and vulnerabilities. The goal is to define a common output format for static analysis tools that will make it feasible for developers and teams to view, understand, interact with, and manage the results produced by all their tools.</p>

OASIS SARIF technical committee
Participant

The Organization for the Advancement of Structured Information Standards (OASIS) aims to set the standard for open collaboration. OASIS Open is where individuals, organizations, and governments come together to solve technical challenges through the development of open code and open standards.

The Static Analysis Results Interchange Format (SARIF) is an industry standard format for the output of static analysis tools. SARIF is an approved OASIS standard. It enables organizations in the safety and security communities to combine and compare the results from multiple competing tools more easily for a more accurate picture of their code issues.

OASIS SARIF technical committee members develop the SARIF interoperability standard for detecting software defects and vulnerabilities. The goal is to define a common output format for static analysis tools that will make it feasible for developers and teams to view, understand, interact with, and manage the results produced by all their tools.

<p><a href="https://www.sae.org/" target="_blank">SAE International</a> (previously known as the Society for Automotive Engineers) is a global association of engineers and related technical experts that develops and publishes international standards for global transport industries such as aerospace, automotive, and commercial vehicles.</p>
<p><b>G-32 cyber-physical systems security committee</b></p>
<p>The <a></a><a href="https://www.sae.org/works/committeeHome.do?comtID=TEAG32" target="_blank">G-32 cyber-physical systems security committee</a>&nbsp;develops documents that address CPSS intended for multisector, cross-industry use to address weaknesses and vulnerabilities of the system and system elements including software, firmware, and hardware. Cross-industry/sector active participation in the committee includes members from industries like aerospace, automotive, defense, medical devices, industrial control devices, IoT, and banking and finance, as well as government and academia.</p>
<ul>
<li><a href="https://www.sae.org/standards/content/ja6678/?_ga=2.5649779.1356737007.1613780738-1363760153.1609974380" target="_blank">JA6678 for Cyber Physical Systems Security Software Assurance</a> standardizes practices to assess and address software vulnerabilities and weaknesses for a cyber-physical system using systems engineering principles to ensure security and resilience throughout the life cycle of the system; conducts software assurance and analysis, considering impact on the product’s software, hardware, and firmware; addresses different areas of concern that includes consideration of the interfaces and network of the system and command and control that could be manipulated through a physical process and/or physical input of the data flow and computation; and performs design validation and verification to assess security and resiliency of software impacting the cyber-physical system safety, security, and integrity across the complete life cycle.</li>
<li><a href="https://www.sae.org/standards/content/ja6801/?_ga=2.81100375.1356737007.1613780738-1363760153.1609974380" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">JA6801 Cyber Physical Systems Security Hardware Assurance</a><span style="font-family: inherit;"> standardizes practices to assess and address weaknesses and vulnerabilities of the hardware, specifically the EEE components, of a cyber-physical system using systems engineering principles to ensure security and resilience throughout the life cycle of the system; conducts EEE component level assurance and analysis, considering impact on the hardware, software, and firmware, in the product or system; addresses different areas of concern that includes consideration of the interfaces and network of the system and command and control that could be manipulated through a physical process and/or physical input of the data flow and computation; and performs design validation and verification to assess security and resiliency of the cyber-physical system.</span></li>
</ul>
<p><b>Vehicle cyber security systems engineering committee</b></p>
<p>The <a href="https://www.sae.org/works/committeeHome.do?comtID=TEVEES18A" target="_blank">vehicle cyber security systems engineering committee</a>&nbsp;WG TEVEES18A serving as the U.S. TAG to ISO, codevelops the Cyber Security Guidebook for Cyber-Physical Vehicle Systems (J3061).&nbsp;The ISO/SAE 21434 cyber security engineering standard for road vehicles&nbsp;builds upon SAE J3061 and provides a similar framework for the entire life cycle of road vehicles.</p>
<p><b>Data Link Connector vehicle security committee</b></p>
<p>The <a href="https://www.sae.org/works/committeeHome.do?comtID=TEVDS20" target="_blank">Data Link Connector vehicle security committee</a> WG TEVDS20 develops:</p>
<ul>
<li><a href="https://www.sae.org/standards/content/j3138_201806/?_ga=2.6781298.1356737007.1613780738-1363760153.1609974380" target="_blank">J3138 for Diagnostic Link Connector Security</a> describes some of the actions that can help ensure safe vehicle operation in the case that any such connected device (external test equipment, connected data collection device) is compromised by a source external to the vehicle. It describes those actions specifically related to SAE J1979, ISO 15765, and ISO 14229 standardized diagnostic services.</li>
<li><a href="https://www.sae.org/standards/content/j3146/?_ga=2.43529957.1356737007.1613780738-1363760153.1609974380" style="background-color: rgb(255, 255, 255); font-family: inherit;" target="_blank">J3146 for survey of practices for securing the interface through the DLC</a><span style="font-family: inherit;"> provides a reference or overview of some current practices for securing the vehicle’s interface with the Data Link Connector (DLC) from cyber security risks associated with external test equipment connections such as diagnostics scan tools or remotely connected applications such as telematics devices. The practices in this report are examples of some secured, in-vehicle data access methods in the automotive industry.</span></li>
</ul>

SAE committees and working groups
Member

SAE International (previously known as the Society for Automotive Engineers) is a global association of engineers and related technical experts that develops and publishes international standards for global transport industries such as aerospace, automotive, and commercial vehicles.

G-32 cyber-physical systems security committee

The G-32 cyber-physical systems security committee develops documents that address CPSS intended for multisector, cross-industry use to address weaknesses and vulnerabilities of the system and system elements including software, firmware, and hardware. Cross-industry/sector active participation in the committee includes members from industries like aerospace, automotive, defense, medical devices, industrial control devices, IoT, and banking and finance, as well as government and academia.

  • JA6678 for Cyber Physical Systems Security Software Assurance standardizes practices to assess and address software vulnerabilities and weaknesses for a cyber-physical system using systems engineering principles to ensure security and resilience throughout the life cycle of the system; conducts software assurance and analysis, considering impact on the product’s software, hardware, and firmware; addresses different areas of concern that includes consideration of the interfaces and network of the system and command and control that could be manipulated through a physical process and/or physical input of the data flow and computation; and performs design validation and verification to assess security and resiliency of software impacting the cyber-physical system safety, security, and integrity across the complete life cycle.
  • JA6801 Cyber Physical Systems Security Hardware Assurance standardizes practices to assess and address weaknesses and vulnerabilities of the hardware, specifically the EEE components, of a cyber-physical system using systems engineering principles to ensure security and resilience throughout the life cycle of the system; conducts EEE component level assurance and analysis, considering impact on the hardware, software, and firmware, in the product or system; addresses different areas of concern that includes consideration of the interfaces and network of the system and command and control that could be manipulated through a physical process and/or physical input of the data flow and computation; and performs design validation and verification to assess security and resiliency of the cyber-physical system.

Vehicle cyber security systems engineering committee

The vehicle cyber security systems engineering committee WG TEVEES18A serving as the U.S. TAG to ISO, codevelops the Cyber Security Guidebook for Cyber-Physical Vehicle Systems (J3061). The ISO/SAE 21434 cyber security engineering standard for road vehicles builds upon SAE J3061 and provides a similar framework for the entire life cycle of road vehicles.

Data Link Connector vehicle security committee

The Data Link Connector vehicle security committee WG TEVDS20 develops:

  • J3138 for Diagnostic Link Connector Security describes some of the actions that can help ensure safe vehicle operation in the case that any such connected device (external test equipment, connected data collection device) is compromised by a source external to the vehicle. It describes those actions specifically related to SAE J1979, ISO 15765, and ISO 14229 standardized diagnostic services.
  • J3146 for survey of practices for securing the interface through the DLC provides a reference or overview of some current practices for securing the vehicle’s interface with the Data Link Connector (DLC) from cyber security risks associated with external test equipment connections such as diagnostics scan tools or remotely connected applications such as telematics devices. The practices in this report are examples of some secured, in-vehicle data access methods in the automotive industry.
<p>The <a href="http://www.smf-sdo.org.sg/" target="_blank">Singapore Manufacturing Federation Standards Development Organisation (SMF-SDO)</a> administers the development, promotion, and implementation of standards to meet the needs of industry and regulators. SMF-SDO is guided by the industry-led <a href="https://www.enterprisesg.gov.sg/quality-standards/standards/for-partners/standards-development" target="_blank">Singapore Standards Council</a>, which provides advice on the directions, policies, strategies, and priorities for the Singapore Standardisation Programme, managed by <a href="https://www.enterprisesg.gov.sg/" target="_blank">Enterprise Singapore</a>, the national standards body.</p>
<p>The <a href="http://www.smf-sdo.org.sg/about-us/manufacturing-standards-committee-MSC" target="_blank">manufacturing standards committee (MSC)</a> identifies, develops, and promotes critical standards to support the growth of the manufacturing and general engineering sectors in Singapore. The MSC autonomous vehicle technical committee (AVTC) oversees the preparation of a new standard and includes the cyber security guidelines working group (WG3) that develops “<a href="https://www.enterprisesg.gov.sg/esghome/media-centre/media-releases/2019/january/singapore-develops-provisional-national-standards-to-guide-development-of-fully-autonomous-vehicles" target="_blank">Technical Reference 68 for Autonomous Vehicles – Part 3 (TR 68 – 3): Cyber Security Principles and Assessment Framework</a>” to promote the safe and secure deployment of fully autonomous vehicles in Singapore.</p>

Singapore standards council MSC AVTC working group
Member

The Singapore Manufacturing Federation Standards Development Organisation (SMF-SDO) administers the development, promotion, and implementation of standards to meet the needs of industry and regulators. SMF-SDO is guided by the industry-led Singapore Standards Council, which provides advice on the directions, policies, strategies, and priorities for the Singapore Standardisation Programme, managed by Enterprise Singapore, the national standards body.

The manufacturing standards committee (MSC) identifies, develops, and promotes critical standards to support the growth of the manufacturing and general engineering sectors in Singapore. The MSC autonomous vehicle technical committee (AVTC) oversees the preparation of a new standard and includes the cyber security guidelines working group (WG3) that develops “Technical Reference 68 for Autonomous Vehicles – Part 3 (TR 68 – 3): Cyber Security Principles and Assessment Framework” to promote the safe and secure deployment of fully autonomous vehicles in Singapore.

<p><a href="https://www.synopsys.com/software-integrity/partners/ul.html" target="_blank">UL (formerly Underwriters Laboratories)</a> is a global safety consulting and certification company. UL helps companies demonstrate safety, enhance sustainability, strengthen security, deliver quality, manage risk, and achieve regulatory compliance.</p><p><a href="https://www.synopsys.com/glossary/what-is-ul-2900.html" target="_blank">UL 2900</a>&nbsp;is a series of standards that present general software cyber security requirements for network-connectable products (UL 2900-1), as well as requirements specifically for medical and healthcare systems (UL 2900-2-1), industrial control systems (UL 2900-2-2), and security and life safety signaling systems (UL 2900-2-3).</p><p>The <a href="https://www.ul.com/resources/ul-cybersecurity-assurance-program-ul-cap" target="_blank">UL cyber security assurance program (UL CAP)</a> is a certification program that evaluates the IoT security of network-connectable products and systems. UL CAP uses the UL 2900 series of standards.</p>

UL cyber security assurance program
Member

UL (formerly Underwriters Laboratories) is a global safety consulting and certification company. UL helps companies demonstrate safety, enhance sustainability, strengthen security, deliver quality, manage risk, and achieve regulatory compliance.

UL 2900 is a series of standards that present general software cyber security requirements for network-connectable products (UL 2900-1), as well as requirements specifically for medical and healthcare systems (UL 2900-2-1), industrial control systems (UL 2900-2-2), and security and life safety signaling systems (UL 2900-2-3).

The UL cyber security assurance program (UL CAP) is a certification program that evaluates the IoT security of network-connectable products and systems. UL CAP uses the UL 2900 series of standards.