83_FR_26544 83 FR 26434 - Multistakeholder Process on Promoting Software Component Transparency

83 FR 26434 - Multistakeholder Process on Promoting Software Component Transparency

DEPARTMENT OF COMMERCE
National Telecommunications and Information Administration

Federal Register Volume 83, Issue 110 (June 7, 2018)

Page Range26434-26436
FR Document2018-12261

The National Telecommunications and Information Administration (NTIA) will convene meetings of a multistakeholder process on promoting software component transparency. This Notice announces the first meeting, which is scheduled for July 19, 2018.

Federal Register, Volume 83 Issue 110 (Thursday, June 7, 2018)
[Federal Register Volume 83, Number 110 (Thursday, June 7, 2018)]
[Notices]
[Pages 26434-26436]
From the Federal Register Online  [www.thefederalregister.org]
[FR Doc No: 2018-12261]


-----------------------------------------------------------------------

DEPARTMENT OF COMMERCE

National Telecommunications and Information Administration


Multistakeholder Process on Promoting Software Component 
Transparency

AGENCY: National Telecommunications and Information Administration, 
U.S. Department of Commerce.

ACTION: Notice of Open Meeting.

-----------------------------------------------------------------------

SUMMARY: The National Telecommunications and Information Administration 
(NTIA) will convene meetings of a multistakeholder process on promoting 
software component transparency. This Notice announces the first 
meeting, which is scheduled for July 19, 2018.

DATES: The meeting will be held on July 19, 2018, from 10:00 a.m. to 
4:00 p.m., Eastern Daylight Time.

ADDRESSES: The meeting will be held at the American Institute of 
Architects, 1735 New York Ave. NW, Washington, DC 20006.

FOR FURTHER INFORMATION CONTACT: Allan Friedman, National 
Telecommunications and Information Administration, U.S. Department of 
Commerce, 1401 Constitution Avenue NW, Room 4725, Washington, DC 20230; 
telephone: (202) 482-4281; email: [email protected]. Please direct 
media inquiries to NTIA's Office of Public Affairs: (202) 482-7002; 
email: [email protected].

SUPPLEMENTARY INFORMATION: 
    Background: Since 2015, the National Telecommunications and 
Information Administration has sought public comment on several matters 
around information and cyber policy and security, the Internet of 
Things (IoT), and the health of the digital ecosystem. In 2015, NTIA 
issued a Request for Comment to ``identify substantive cybersecurity 
issues that affect the digital ecosystem and digital economic growth 
where broad consensus, coordinated action, and the development of best 
practices could substantially improve security for organizations and 
consumers.'' \1\ In a separate but related matter in April 2016, NTIA, 
along with the Department's internet Policy Task Force, sought comments 
on the ``benefits, challenges, and potential roles for the government 
in fostering the advancement of the Internet of Things.'' \2\ Lastly, 
as part of Executive Order 13800, NTIA requested comments on 
``Promoting Stakeholder Action Against Botnets and Other Automated 
Threats.'' \3\
---------------------------------------------------------------------------

    \1\ U.S. Department of Commerce, internet Policy Task Force, 
Request for Public Comment, Stakeholder Engagement on Cybersecurity 
in the Digital Ecosystem, 80 FR 14360, Docket No. 150312253-5253-01 
(Mar. 19, 2015), available at: https://www.ntia.doc.gov/files/ntia/publications/cybersecurity_rfc_03192015.pdf.
    \2\ U.S. Department of Commerce, internet Policy Task Force, 
Request for Public Comment, Benefits, Challenges, and Potential 
Roles for the Government in Fostering the Advancement of the 
Internet of Things, 81 FR 19956, Docket No 160331306-6306-01 (Apr. 
5, 2016), available at: https://www.ntia.doc.gov/federal-register-notice/2016/rfc-potential-roles-government-fostering-advancement-internet-of-things.
    \3\ U.S. Department of Commerce, internet Policy Task Force, 
Request for Public Comment, Promoting Stakeholder Action Against 
Botnets and Other Automated Threats, 82 FR 27042, Docket No. 
170602536-7536-01 (Mar. 19, 2015), available at: https://www.ntia.doc.gov/files/ntia/publications/fr-ntia-cyber-eo-rfc-06132017.pdf.
---------------------------------------------------------------------------

    Several themes emerged from these three public consultations. Many 
stakeholders emphasized the importance of community-led, consensus-
driven, and risk-based solutions to address information security 
challenges, highlighting the role NTIA should play in convening 
multistakeholder processes. In the digital ecosystem, particular 
challenges were identified: Understanding and handling vulnerability 
information, addressing the insecurities in the growing IoT 
marketplace, and fostering a secure development lifecycle. NTIA has 
convened two multistakeholder processes to address these policy and 
market challenges. The first focused on how to promote collaboration 
around communicating vulnerability information, and the second helped 
vendors and consumers understand policy and market concerns related to 
patching vulnerabilities.
    The next initiative will focus on promoting software component 
transparency. Stakeholders will engage in an open and transparent 
process to explore the benefits and any potential risks of greater 
transparency. They may focus on incentives and barriers to adoption of 
transparency practices. The scope could include policy and 
international components. Transparency-driven solutions need not be 
prescriptive or regulatory, and can accommodate an ecosystem without a 
one-size-fits-all approach. The goal of this initiative is to foster a 
market that

[[Page 26435]]

offers greater transparency on software components.
    Most modern software is not written completely from scratch, but 
includes existing components, modules, and libraries from the open 
source and commercial software world. Modern development practices such 
as code reuse, and a dynamic IT marketplace with acquisitions and 
mergers, make it challenging to track the use of software components. 
The Internet of Things compounds this phenomenon, as new organizations, 
enterprises and innovators take on the role of software developer to 
add ``smart'' features or connectivity to their products. While the 
majority of libraries and components do not have known vulnerabilities, 
many do, and the sheer quantity of software means that some software 
products ship with vulnerable or out-of-date components. Many technical 
solutions to aid in this have already been developed by industry and 
the standards community.
    Vendors and developers also would find software component data 
useful. Cataloging the inputs to a software product is recognized as an 
important part of a secure development life cycle.\4\ Indeed, many 
organizations have developed internal processes to capture and manage 
this data for security purposes. Many others do so to manage licensing 
issues around third-party software components and intellectual property 
rights. Communicating information about the underlying components can 
be a strong security signifier, while still protecting the valuable 
intellectual property and source code in software and devices.
---------------------------------------------------------------------------

    \4\ The Software Assurance Forum for Excellence in Code 
(SAFECode), an industry consortium, has released a report on third 
party components that cites a range of standards. Managing Security 
Risks Inherent in the Use of Third-party Components, SAFECode (May 
2017), available at https://www.safecode.org/wp-content/uploads/2017/05/SAFECode_TPC_Whitepaper.pdf.
---------------------------------------------------------------------------

    The importance of transparency in information security is widely 
recognized, and the notion of transparency around components of 
software and connected devices is not new. Academics identified the 
potential value of a ``software bill of materials'' as far back as 
1995,\5\ and there are a growing number of commercial solutions for 
security, licensing, and asset management. The International Standards 
Organization (ISO) first standardized software identification (SWID) 
tags in 2009.\6\ In 2015, NIST published Guidelines for the Creation of 
Interoperable Software Identification (SWID) Tags,\7\ and their use has 
been slowly increasing. The open source community has also developed 
the Software Package Data Exchange.\8\ This process will explore 
successful examples of use, and market barriers to increased adoption. 
From the perspective of the enterprise customer, it is hard to defend 
what one does not know. Transparency itself is not sufficient; the data 
must be useful and actionable. Understanding what is on an enterprise 
network is a key part of a security program. Having data about software 
components allows the enterprise customer to better understand the 
risks of potentially vulnerable software and devices.
---------------------------------------------------------------------------

    \5\ Leblang D.B., Levine P.H., Software configuration 
management: Why is it needed and what should it do? In: Estublier J. 
(eds) Software Configuration Management Lecture Notes in Computer 
Science, vol. 1005, Springer, Berlin, Heidelberg (1995).
    \6\ ISO/IEC 19770 ``Software Identification Tag,'' originally 
published in 2009, updated in 2015, https://www.iso.org/standard/65666.html.
    \7\ U.S. Department of Commerce, Guidelines for the Creation of 
Interoperable Software Identification (SWID) Tags, National 
Institute of Standards and Technology Internal Report 8060 (Dec. 
2015), available at: https://csrc.nist.gov/csrc/media/publications/nistir/8060/final/documents/nistir_8060_draft_fourth.pdf.
    \8\ More information on the Software Package Data Exchange 
project is available at https://spdx.org.
---------------------------------------------------------------------------

    Any conversation around transparency must include a discussion of 
the needs of the diverse set of enterprise software users. Data about 
the underlying code can help both the customer and the vendor. It 
should be incorporated into a security-mature organization's existing 
vulnerability management solutions, and can help foster further 
innovation. Having access to this data can help organizations mitigate 
concerns around orphaned devices and products, and lower the risks of 
investing in new products by increasing capabilities to deal with 
future security issues.
    NTIA will act as the convener, but stakeholders will drive the 
outcomes. Stakeholders will determine how to scope and organize the 
work through subgroups or other means. Success of the process will be 
evaluated by the extent to which broader findings on software component 
transparency are implemented across the ecosystem.
    This multistakeholder process is not a standards development 
process and will not supplant ongoing standards efforts or discussions. 
NTIA will frame the initial conversation around the policy and market 
considerations for greater software component transparency. NTIA 
encourages cross-sector participation as this will help to prevent 
sector-specific solutions that could fragment the marketplace. NTIA 
encourages discussion of approaches and considerations from diverse 
sectors such as the medical device community, where the applicability 
of a ``bill of materials'' has garnered increased discussion and 
interest.\9\ This approach can promote a more efficient and adaptive 
marketplace for new products.
    Matters to Be Considered: The July 19, 2018, meeting will be the 
first in a series of NTIA-convened multistakeholder discussions on 
promoting software component transparency. Subsequent meetings will 
follow on a schedule determined by those participating in the first 
meeting. Stakeholders will engage in an open, transparent, and 
consensus-driven process to understand the range of issues involved. 
The multistakeholder process will involve hearing and understanding the 
perspectives of diverse stakeholders, explicitly sharing the 
perspectives of a range of software and IoT vendors and enterprise 
customers from across the digital economy.
    The July 19, 2018, meeting is intended to bring stakeholders 
together to share the range of views on software component 
transparency, and to establish more concrete goals and structure of the 
process. The objectives of this first meeting are to: (1) Share the 
perspectives and concerns of both the vendor and enterprise customer 
communities; (2) discuss and acknowledge what is already working; (3) 
explore obstacles and challenges for greater transparency and better 
risk decisions; (4) identify promising areas of potential 
collaboration; (5) engage stakeholders in a discussion of logistical 
issues, including internal structures such as a small drafting 
committee or various working groups, and the location and frequency of 
future meetings; and (6) identify concrete goals and stakeholder work 
following the first meeting. These topics could include, but are in no 
way limited to, an inventory of existing statutory, policy, regulatory, 
and market efforts to increase software component transparency; 
identification of incentives and disincentives for market adoption of 
approaches for software component transparency; exploration of 
statutory, policy, and regulatory activities that may inhibit adoption; 
accessible high-level guidance for strategic decision-makers; and 
review of international approaches to understand statutory, policy, and 
regulatory environments to understand effects on market adoption.
    The main objective of further meetings will be to encourage and 
facilitate continued discussion among stakeholders to map the range of 
issues, and develop a consensus view for some

[[Page 26436]]

determined aspects of transparency. This discussion may include the 
appropriate scope of the initiative and circulation of stakeholder-
developed drafts. Stakeholders may also agree on procedural work plans 
for the group, including additional meetings or modified logistics for 
future meetings. NTIA suggests that stakeholders consider setting clear 
deadlines for working drafts and a phase for external review of such 
drafts, before reconvening to take account of external feedback.
    More information about stakeholders' work will be available at: 
https://www.ntia.doc.gov/other-publication/2018/SoftwareTransparency.
    Time and Date: NTIA will convene the first meeting of the 
multistakeholder process on Software Component Transparency on July 19, 
2018, from 10:00 a.m. to 4:00 p.m. Eastern Daylight Time. Please refer 
to NTIA's website, https://www.ntia.doc.gov/other-publication/2018/SoftwareTransparency, for the most current information.
    Place: The meeting will be held at the American Institute of 
Architects, 1735 New York Ave. NW, Washington, DC 20006. The location 
of the meeting is subject to change. Please refer to NTIA's website, 
https://www.ntia.doc.gov/other-publication/2018/SoftwareTransparency, 
for the most current information.
    Other Information: The meeting is open to the public and the press 
on a first-come, first-served basis. Space is limited.
    The meeting is physically accessible to people with disabilities. 
Requests for sign language interpretation or other auxiliary aids 
should be directed to Allan Friedman at (202) 482-4281 or 
[email protected] at least seven (7) business days prior to each 
meeting. The meetings will also be webcast. Requests for real-time 
captioning of the webcast or other auxiliary aids should be directed to 
Allan Friedman at (202) 482-4281 or [email protected] at least 
seven (7) business days prior to each meeting. There will be an 
opportunity for stakeholders viewing the webcast to participate 
remotely in the meetings through a moderated conference bridge, 
including polling functionality. Access details for the meetings are 
subject to change. Please refer to NTIA's website, https://www.ntia.doc.gov/other-publication/2018/SoftwareTransparency, for the 
most current information.

    Dated: June 4, 2018.
David J. Redl,
Assistant Secretary for Communication and Information, National 
Telecommunications and Information Administration.
[FR Doc. 2018-12261 Filed 6-6-18; 8:45 am]
BILLING CODE 3510-60-P



                                                26434                          Federal Register / Vol. 83, No. 110 / Thursday, June 7, 2018 / Notices

                                                  4. August 21, 2018, 9 a.m.–5 p.m.,                      Dated: June 4, 2018.                                 separate but related matter in April
                                                DoubleTree Hotel, 1702 Seawall                          Jennifer M. Wallace,                                   2016, NTIA, along with the
                                                Boulevard, Galveston, TX 77550.                         Acting Director, Office of Sustainable                 Department’s internet Policy Task
                                                  5. September 5, 2018, 9 a.m.–5 p.m.,                  Fisheries, National Marine Fisheries Service.          Force, sought comments on the
                                                Hilton Garden Inn, 1101 US Highway                      [FR Doc. 2018–12275 Filed 6–6–18; 8:45 am]             ‘‘benefits, challenges, and potential
                                                231, Panama City, FL 32405.                             BILLING CODE 3510–22–P                                 roles for the government in fostering the
                                                                                                                                                               advancement of the Internet of
                                                  6. September 19, 2018, 9 a.m.–5 p.m.,                                                                        Things.’’ 2 Lastly, as part of Executive
                                                Hilton Garden Inn, 1 Thurber Street,                    DEPARTMENT OF COMMERCE                                 Order 13800, NTIA requested comments
                                                Warwick, RI 02886.                                                                                             on ‘‘Promoting Stakeholder Action
                                                Registration                                            National Telecommunications and                        Against Botnets and Other Automated
                                                                                                        Information Administration                             Threats.’’ 3
                                                  To register for a scheduled Safe                                                                                Several themes emerged from these
                                                Handling, Release, and Identification                   Multistakeholder Process on                            three public consultations. Many
                                                Workshop, please contact Angler                         Promoting Software Component                           stakeholders emphasized the
                                                Conservation Education at (386) 682–                    Transparency                                           importance of community-led,
                                                0158. Pre-registration is highly                        AGENCY:  National Telecommunications                   consensus-driven, and risk-based
                                                recommended, but not required.                          and Information Administration, U.S.                   solutions to address information
                                                                                                        Department of Commerce.                                security challenges, highlighting the
                                                Registration Materials                                                                                         role NTIA should play in convening
                                                                                                        ACTION: Notice of Open Meeting.
                                                  To ensure that workshop certificates                                                                         multistakeholder processes. In the
                                                are linked to the correct permits,                      SUMMARY:   The National                                digital ecosystem, particular challenges
                                                participants will need to bring the                     Telecommunications and Information                     were identified: Understanding and
                                                                                                        Administration (NTIA) will convene                     handling vulnerability information,
                                                following specific items with them to
                                                                                                        meetings of a multistakeholder process                 addressing the insecurities in the
                                                the workshop:
                                                                                                        on promoting software component                        growing IoT marketplace, and fostering
                                                  • Individual vessel owners must                       transparency. This Notice announces                    a secure development lifecycle. NTIA
                                                bring a copy of the appropriate                         the first meeting, which is scheduled for              has convened two multistakeholder
                                                swordfish and/or shark permit(s), a copy                July 19, 2018.                                         processes to address these policy and
                                                of the vessel registration or                                                                                  market challenges. The first focused on
                                                                                                        DATES: The meeting will be held on July
                                                documentation, and proof of                                                                                    how to promote collaboration around
                                                                                                        19, 2018, from 10:00 a.m. to 4:00 p.m.,
                                                identification.                                                                                                communicating vulnerability
                                                                                                        Eastern Daylight Time.
                                                  • Representatives of a business-                      ADDRESSES: The meeting will be held at
                                                                                                                                                               information, and the second helped
                                                owned or co-owned vessel must bring                                                                            vendors and consumers understand
                                                                                                        the American Institute of Architects,
                                                proof that the individual is an agent of                                                                       policy and market concerns related to
                                                                                                        1735 New York Ave. NW, Washington,
                                                the business (such as articles of                                                                              patching vulnerabilities.
                                                                                                        DC 20006.
                                                incorporation), a copy of the applicable                                                                          The next initiative will focus on
                                                                                                        FOR FURTHER INFORMATION CONTACT:                       promoting software component
                                                swordfish and/or shark permit(s), and                   Allan Friedman, National
                                                proof of identification.                                                                                       transparency. Stakeholders will engage
                                                                                                        Telecommunications and Information                     in an open and transparent process to
                                                  • Vessel operators must bring proof of                Administration, U.S. Department of                     explore the benefits and any potential
                                                identification.                                         Commerce, 1401 Constitution Avenue                     risks of greater transparency. They may
                                                                                                        NW, Room 4725, Washington, DC                          focus on incentives and barriers to
                                                Workshop Objectives
                                                                                                        20230; telephone: (202) 482–4281;                      adoption of transparency practices. The
                                                  The Safe Handling, Release, and                       email: afriedman@ntia.doc.gov. Please                  scope could include policy and
                                                Identification Workshops are designed                   direct media inquiries to NTIA’s Office                international components.
                                                to teach longline and gillnet fishermen                 of Public Affairs: (202) 482–7002; email:              Transparency-driven solutions need not
                                                the required techniques for the safe                    press@ntia.doc.gov.                                    be prescriptive or regulatory, and can
                                                handling and release of entangled and/                  SUPPLEMENTARY INFORMATION:                             accommodate an ecosystem without a
                                                or hooked protected species, such as sea                   Background: Since 2015, the National                one-size-fits-all approach. The goal of
                                                turtles, marine mammals, and                            Telecommunications and Information                     this initiative is to foster a market that
                                                smalltooth sawfish, and prohibited                      Administration has sought public
                                                sharks. In an effort to improve reporting,              comment on several matters around                      Digital Ecosystem, 80 FR 14360, Docket No.
                                                the proper identification of protected                  information and cyber policy and                       150312253–5253–01 (Mar. 19, 2015), available at:
                                                                                                        security, the Internet of Things (IoT),                https://www.ntia.doc.gov/files/ntia/publications/
                                                species and prohibited sharks will also                                                                        cybersecurity_rfc_03192015.pdf.
                                                be taught at these workshops.                           and the health of the digital ecosystem.                 2 U.S. Department of Commerce, internet Policy
                                                Additionally, individuals attending                     In 2015, NTIA issued a Request for                     Task Force, Request for Public Comment, Benefits,
                                                these workshops will gain a better                      Comment to ‘‘identify substantive                      Challenges, and Potential Roles for the Government
                                                understanding of the requirements for                   cybersecurity issues that affect the                   in Fostering the Advancement of the Internet of
                                                                                                                                                               Things, 81 FR 19956, Docket No 160331306–6306–
                                                participating in these fisheries. The                   digital ecosystem and digital economic                 01 (Apr. 5, 2016), available at: https://
                                                overall goal of these workshops is to                   growth where broad consensus,                          www.ntia.doc.gov/federal-register-notice/2016/rfc-
sradovich on DSK3GMQ082PROD with NOTICES




                                                provide participants with the skills                    coordinated action, and the                            potential-roles-government-fostering-advancement-
                                                needed to reduce the mortality of                       development of best practices could                    internet-of-things.
                                                                                                                                                                 3 U.S. Department of Commerce, internet Policy
                                                protected species and prohibited sharks,                substantially improve security for
                                                                                                                                                               Task Force, Request for Public Comment, Promoting
                                                which may prevent additional                            organizations and consumers.’’ 1 In a                  Stakeholder Action Against Botnets and Other
                                                regulations on these fisheries in the                                                                          Automated Threats, 82 FR 27042, Docket No.
                                                                                                          1 U.S. Department of Commerce, internet Policy       170602536–7536–01 (Mar. 19, 2015), available at:
                                                future.
                                                                                                        Task Force, Request for Public Comment,                https://www.ntia.doc.gov/files/ntia/publications/fr-
                                                   Authority: 16 U.S.C. 1801 et seq.                    Stakeholder Engagement on Cybersecurity in the         ntia-cyber-eo-rfc-06132017.pdf.



                                           VerDate Sep<11>2014   17:19 Jun 06, 2018   Jkt 244001   PO 00000   Frm 00025   Fmt 4703   Sfmt 4703   E:\FR\FM\07JNN1.SGM   07JNN1


                                                                               Federal Register / Vol. 83, No. 110 / Thursday, June 7, 2018 / Notices                                              26435

                                                offers greater transparency on software                 (SWID) tags in 2009.6 In 2015, NIST                     considerations from diverse sectors such
                                                components.                                             published Guidelines for the Creation of                as the medical device community,
                                                   Most modern software is not written                  Interoperable Software Identification                   where the applicability of a ‘‘bill of
                                                completely from scratch, but includes                   (SWID) Tags,7 and their use has been                    materials’’ has garnered increased
                                                existing components, modules, and                       slowly increasing. The open source                      discussion and interest.9 This approach
                                                libraries from the open source and                      community has also developed the                        can promote a more efficient and
                                                commercial software world. Modern                       Software Package Data Exchange.8 This                   adaptive marketplace for new products.
                                                development practices such as code                      process will explore successful                            Matters to Be Considered: The July 19,
                                                reuse, and a dynamic IT marketplace                     examples of use, and market barriers to                 2018, meeting will be the first in a series
                                                with acquisitions and mergers, make it                  increased adoption. From the                            of NTIA-convened multistakeholder
                                                challenging to track the use of software                perspective of the enterprise customer,                 discussions on promoting software
                                                components. The Internet of Things                      it is hard to defend what one does not                  component transparency. Subsequent
                                                compounds this phenomenon, as new                       know. Transparency itself is not                        meetings will follow on a schedule
                                                organizations, enterprises and                          sufficient; the data must be useful and                 determined by those participating in the
                                                innovators take on the role of software                 actionable. Understanding what is on an                 first meeting. Stakeholders will engage
                                                developer to add ‘‘smart’’ features or                  enterprise network is a key part of a                   in an open, transparent, and consensus-
                                                connectivity to their products. While                   security program. Having data about                     driven process to understand the range
                                                the majority of libraries and components                software components allows the                          of issues involved. The
                                                do not have known vulnerabilities,                      enterprise customer to better understand                multistakeholder process will involve
                                                many do, and the sheer quantity of                      the risks of potentially vulnerable                     hearing and understanding the
                                                software means that some software                       software and devices.                                   perspectives of diverse stakeholders,
                                                products ship with vulnerable or out-of-                   Any conversation around                              explicitly sharing the perspectives of a
                                                date components. Many technical                         transparency must include a discussion                  range of software and IoT vendors and
                                                solutions to aid in this have already                   of the needs of the diverse set of                      enterprise customers from across the
                                                been developed by industry and the                      enterprise software users. Data about the               digital economy.
                                                standards community.                                    underlying code can help both the                          The July 19, 2018, meeting is
                                                   Vendors and developers also would                    customer and the vendor. It should be                   intended to bring stakeholders together
                                                find software component data useful.                    incorporated into a security-mature                     to share the range of views on software
                                                Cataloging the inputs to a software                     organization’s existing vulnerability                   component transparency, and to
                                                product is recognized as an important                   management solutions, and can help                      establish more concrete goals and
                                                part of a secure development life cycle.4               foster further innovation. Having access                structure of the process. The objectives
                                                Indeed, many organizations have                         to this data can help organizations                     of this first meeting are to: (1) Share the
                                                developed internal processes to capture                 mitigate concerns around orphaned                       perspectives and concerns of both the
                                                and manage this data for security                       devices and products, and lower the                     vendor and enterprise customer
                                                purposes. Many others do so to manage                   risks of investing in new products by                   communities; (2) discuss and
                                                licensing issues around third-party                     increasing capabilities to deal with                    acknowledge what is already working;
                                                software components and intellectual                    future security issues.                                 (3) explore obstacles and challenges for
                                                property rights. Communicating                             NTIA will act as the convener, but                   greater transparency and better risk
                                                information about the underlying                        stakeholders will drive the outcomes.                   decisions; (4) identify promising areas
                                                components can be a strong security                     Stakeholders will determine how to                      of potential collaboration; (5) engage
                                                signifier, while still protecting the                   scope and organize the work through                     stakeholders in a discussion of logistical
                                                valuable intellectual property and                      subgroups or other means. Success of                    issues, including internal structures
                                                source code in software and devices.                    the process will be evaluated by the                    such as a small drafting committee or
                                                   The importance of transparency in                    extent to which broader findings on                     various working groups, and the
                                                information security is widely                          software component transparency are                     location and frequency of future
                                                recognized, and the notion of                           implemented across the ecosystem.                       meetings; and (6) identify concrete goals
                                                transparency around components of                          This multistakeholder process is not a               and stakeholder work following the first
                                                software and connected devices is not                   standards development process and will                  meeting. These topics could include,
                                                new. Academics identified the potential                 not supplant ongoing standards efforts                  but are in no way limited to, an
                                                value of a ‘‘software bill of materials’’ as            or discussions. NTIA will frame the                     inventory of existing statutory, policy,
                                                                                                        initial conversation around the policy                  regulatory, and market efforts to
                                                far back as 1995,5 and there are a
                                                                                                        and market considerations for greater                   increase software component
                                                growing number of commercial
                                                                                                        software component transparency. NTIA                   transparency; identification of
                                                solutions for security, licensing, and
                                                                                                        encourages cross-sector participation as                incentives and disincentives for market
                                                asset management. The International
                                                                                                        this will help to prevent sector-specific               adoption of approaches for software
                                                Standards Organization (ISO) first
                                                                                                        solutions that could fragment the                       component transparency; exploration of
                                                standardized software identification
                                                                                                        marketplace. NTIA encourages                            statutory, policy, and regulatory
                                                   4 The Software Assurance Forum for Excellence
                                                                                                        discussion of approaches and                            activities that may inhibit adoption;
                                                in Code (SAFECode), an industry consortium, has                                                                 accessible high-level guidance for
                                                released a report on third party components that          6 ISO/IEC 19770 ‘‘Software Identification Tag,’’
                                                                                                                                                                strategic decision-makers; and review of
                                                cites a range of standards. Managing Security Risks     originally published in 2009, updated in 2015,          international approaches to understand
                                                Inherent in the Use of Third-party Components,          https://www.iso.org/standard/65666.html.
sradovich on DSK3GMQ082PROD with NOTICES




                                                SAFECode (May 2017), available at https://                7 U.S. Department of Commerce, Guidelines for
                                                                                                                                                                statutory, policy, and regulatory
                                                www.safecode.org/wp-content/uploads/2017/05/            the Creation of Interoperable Software Identification   environments to understand effects on
                                                SAFECode_TPC_Whitepaper.pdf.                            (SWID) Tags, National Institute of Standards and        market adoption.
                                                   5 Leblang D.B., Levine P.H., Software                Technology Internal Report 8060 (Dec. 2015),               The main objective of further
                                                configuration management: Why is it needed and          available at: https://csrc.nist.gov/csrc/media/         meetings will be to encourage and
                                                what should it do? In: Estublier J. (eds) Software      publications/nistir/8060/final/documents/nistir_
                                                Configuration Management Lecture Notes in               8060_draft_fourth.pdf.                                  facilitate continued discussion among
                                                Computer Science, vol. 1005, Springer, Berlin,            8 More information on the Software Package Data       stakeholders to map the range of issues,
                                                Heidelberg (1995).                                      Exchange project is available at https://spdx.org.      and develop a consensus view for some


                                           VerDate Sep<11>2014   17:19 Jun 06, 2018   Jkt 244001   PO 00000   Frm 00026   Fmt 4703   Sfmt 4703   E:\FR\FM\07JNN1.SGM   07JNN1


                                                26436                          Federal Register / Vol. 83, No. 110 / Thursday, June 7, 2018 / Notices

                                                determined aspects of transparency.                       Dated: June 4, 2018.                                 Information Act, a petition for
                                                This discussion may include the                         David J. Redl,                                         confidential treatment of the exempt
                                                appropriate scope of the initiative and                 Assistant Secretary for Communication and              information may be submitted according
                                                circulation of stakeholder-developed                    Information, National Telecommunications               to the procedures established in § 145.9
                                                drafts. Stakeholders may also agree on                  and Information Administration.                        of the Commission’s regulations.1
                                                procedural work plans for the group,                    [FR Doc. 2018–12261 Filed 6–6–18; 8:45 am]                The Commission reserves the right,
                                                including additional meetings or                        BILLING CODE 3510–60–P                                 but shall have no obligation, to review,
                                                modified logistics for future meetings.                                                                        pre-screen, filter, redact, refuse or
                                                NTIA suggests that stakeholders                                                                                remove any or all of your submission
                                                consider setting clear deadlines for                    COMMODITY FUTURES TRADING                              from http://www.cftc.gov that it may
                                                                                                        COMMISSION                                             deem to be inappropriate for
                                                working drafts and a phase for external
                                                                                                                                                               publication, such as obscene language.
                                                review of such drafts, before
                                                                                                        Agency Information Collection                          All submissions that have been redacted
                                                reconvening to take account of external                                                                        or removed that contain comments on
                                                feedback.                                               Activities: Notice of Intent To Renew
                                                                                                        Collection 3038–0093, Part 40,                         the merits of the Information Collection
                                                   More information about stakeholders’                 Provisions Common to Registered                        Request will be retained in the public
                                                work will be available at: https://                     Entities                                               comment file and will be considered as
                                                www.ntia.doc.gov/other-publication/                                                                            required under the Administrative
                                                2018/SoftwareTransparency.                              AGENCY: Commodity Futures Trading                      Procedure Act and other applicable
                                                                                                        Commission.                                            laws, and may be accessible under the
                                                   Time and Date: NTIA will convene
                                                                                                        ACTION: Notice.                                        Freedom of Information Act.
                                                the first meeting of the multistakeholder
                                                process on Software Component                                                                                  FOR FURTHER INFORMATION CONTACT: Lois
                                                                                                        SUMMARY:   The Commodity Futures
                                                Transparency on July 19, 2018, from                     Trading Commission (‘‘Commission’’ or                  J. Gregory, Associate Director, Division
                                                10:00 a.m. to 4:00 p.m. Eastern Daylight                                                                       of Market Oversight, Commodity
                                                                                                        ‘‘CFTC’’) is announcing an opportunity
                                                Time. Please refer to NTIA’s website,                                                                          Futures Trading Commission, (202)
                                                                                                        for public comment on the proposed
                                                                                                                                                               418–5092; email: lgregory@cftc.gov.
                                                https://www.ntia.doc.gov/other-                         collection of certain information by the
                                                                                                        agency. Under the Paperwork Reduction                  SUPPLEMENTARY INFORMATION: Under the
                                                publication/2018/Software
                                                Transparency, for the most current                      Act (‘‘PRA’’), Federal agencies are                    PRA, 44 U.S.C. 3501 et seq., Federal
                                                                                                        required to publish notice in the                      agencies must obtain approval from the
                                                information.
                                                                                                        Federal Register concerning each                       Office of Management and Budget
                                                   Place: The meeting will be held at the                                                                      (OMB) for each collection of
                                                American Institute of Architects, 1735                  proposed collection of information,
                                                                                                        including each proposed extension of an                information they conduct or sponsor.
                                                New York Ave. NW, Washington, DC                                                                               ‘‘Collection of Information’’ is defined
                                                                                                        existing collection, and to allow 60 days
                                                20006. The location of the meeting is                                                                          in 44 U.S.C. 3502(3) and 5 CFR 1320.3
                                                                                                        for public comment. This notice solicits
                                                subject to change. Please refer to NTIA’s                                                                      and includes agency requests or
                                                                                                        comments on collections of information
                                                website, https://www.ntia.doc.gov/                      provided for by Part 40, Provisions                    requirements that members of the public
                                                other-publication/2018/Software                                                                                submit reports, keep records, or provide
                                                                                                        Common to Registered Entities.
                                                Transparency, for the most current                                                                             information to a third party. Section
                                                                                                        DATES: Comments must be submitted on
                                                information.                                                                                                   3506(c)(2)(A) of the PRA, 44 U.S.C.
                                                                                                        or before August 6, 2018.                              3506(c)(2)(A), requires Federal agencies
                                                   Other Information: The meeting is                    ADDRESSES: You may submit comments,                    to provide a 60-day notice in the
                                                open to the public and the press on a                   identified by OMB Control No. 3038–                    Federal Register concerning each
                                                first-come, first-served basis. Space is                0093 by any of the following methods:                  proposed collection of information
                                                limited.                                                   • The Agency’s website, at http://                  before submitting the collection to OMB
                                                   The meeting is physically accessible                 comments.cftc.gov/. Follow the                         for approval. To comply with this
                                                to people with disabilities. Requests for               instructions for submitting comments                   requirement, the CFTC is publishing
                                                sign language interpretation or other                   through the website.                                   notice of the proposed collection of
                                                auxiliary aids should be directed to                       • Mail: Christopher Kirkpatrick,                    information listed below.
                                                Allan Friedman at (202) 482–4281 or                     Secretary of the Commission,                              Title: Part 40, Provisions Common to
                                                afriedman@ntia.doc.gov at least seven                   Commodity Futures Trading                              Registered Entities (OMB Control No.
                                                (7) business days prior to each meeting.                Commission, Three Lafayette Centre,                    3038–0093). This is a request for
                                                                                                        1155 21st Street NW, Washington, DC                    extension of a currently approved
                                                The meetings will also be webcast.
                                                                                                        20581.                                                 information collection.
                                                Requests for real-time captioning of the
                                                                                                           • Hand Delivery/Courier: Same as                       Abstract: This collection of
                                                webcast or other auxiliary aids should                  Mail above.
                                                be directed to Allan Friedman at (202)                                                                         information involves the collection and
                                                                                                           Please submit your comments using                   submission to the Commission of
                                                482–4281 or afriedman@ntia.doc.gov at                   only one method and identify that it is                information from registered entities
                                                least seven (7) business days prior to                  for the renewal of Collection Number                   concerning new products, rules, and
                                                each meeting. There will be an                          3038–0093.                                             rule amendments pursuant to the
                                                opportunity for stakeholders viewing                       All comments must be submitted in                   procedures outlined in §§ 40.2, 40.3,
                                                the webcast to participate remotely in                  English, or if not, accompanied by an                  40.5, 40.6, and 40.10 found in 17 CFR
                                                the meetings through a moderated                        English translation. Comments will be
sradovich on DSK3GMQ082PROD with NOTICES




                                                                                                                                                               part 40.
                                                conference bridge, including polling                    posted as received to http://                             With respect to the collection of
                                                functionality. Access details for the                   www.cftc.gov. You should submit only                   information, the CFTC invites
                                                meetings are subject to change. Please                  information that you wish to make                      comments on:
                                                refer to NTIA’s website, https://                       available publicly. If you wish the                       • Whether the proposed collection of
                                                www.ntia.doc.gov/other-publication/                     Commission to consider information                     information is necessary for the proper
                                                2018/SoftwareTransparency, for the                      that you believe is exempt from
                                                most current information.                               disclosure under the Freedom of                         1   17 CFR 145.9.



                                           VerDate Sep<11>2014   17:19 Jun 06, 2018   Jkt 244001   PO 00000   Frm 00027   Fmt 4703   Sfmt 4703   E:\FR\FM\07JNN1.SGM   07JNN1



Document Created: 2018-06-07 00:51:04
Document Modified: 2018-06-07 00:51:04
CategoryRegulatory Information
CollectionFederal Register
sudoc ClassAE 2.7:
GS 4.107:
AE 2.106:
PublisherOffice of the Federal Register, National Archives and Records Administration
SectionNotices
ActionNotice of Open Meeting.
DatesThe meeting will be held on July 19, 2018, from 10:00 a.m. to 4:00 p.m., Eastern Daylight Time.
ContactAllan Friedman, National Telecommunications and Information Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Room 4725, Washington, DC 20230; telephone: (202) 482-4281; email: [email protected] Please direct media inquiries to NTIA's Office of Public Affairs: (202) 482-7002; email: [email protected]
FR Citation83 FR 26434 

2025 Federal Register | Disclaimer | Privacy Policy
USC | CFR | eCFR