Application Security , Next-Generation Technologies & Secure Development

Why Doesn't Software Get Sold With a List of Ingredients?

Allan Friedman Details the 'Software Bill of Materials' Initiative
Allan Friedman, director of cybersecurity initiatives, NTIA

Just as consumers can look at a box of Twinkies and read a list of ingredients, so too should software makers provide users with a "bill of materials" explaining their composition, says Allan Friedman, director of cybersecurity initiatives at the U.S. National Telecommunications and Information Administration.

See Also: Redefining Security Analytics

In a video interview with Information Security Media Group at RSA 2020, Friedman also discusses:

Friedman is the director of cybersecurity initiatives at NTIA, which part of the U.S. Department of Commerce, where he coordinates NTIA's multistakeholder processes, bringing together industry and the security community on issues such as vulnerability disclosure and IoT security. Previously, Friedman spent over 15 years as a noted security and technology policy expert, conducting research at Harvard's Computer Science Department, the Brookings Institution and George Washington University's Engineering School. In 2014, he co-authored Oxford Press's "Cybersecurity and Cyberwar: What Everyone Needs to Know."


About the Author

Mathew J. Schwartz

Mathew J. Schwartz

Executive Editor, DataBreachToday & Europe

Schwartz is an award-winning journalist with two decades of experience in magazines, newspapers and electronic media. He has covered the information security and privacy sector throughout his career. Before joining Information Security Media Group in 2014, where he now serves as the executive editor, DataBreachToday and for European news coverage, Schwartz was the information security beat reporter for InformationWeek and a frequent contributor to DarkReading, among other publications. He lives in Scotland.




Around the Network

Our website uses cookies. Cookies enable us to provide the best experience possible and help us understand how visitors use our website. By browsing bankinfosecurity.com, you agree to our use of cookies.