CDM-CYBER-DEFENSE-eMAGAZINE-March-2019

More documents

Recommendations

Info

Software Should Come with a “Nutrition” Label By Tae Jin "TJ" Kang, CEO, Insignary, Inc. During the latter half of the 18 th Century and throughout the 19 th Century, the Industrial Revolution fundamentally changed the geographical, political and commercial landscape in Europe and the United States. Citizens that had previously lived in predominantly agrarian, rural societies found themselves in living in urban and industrial ones. This industrial and decidedly technological shift in the Western economies meant that people became focused on creating, building and selling more specialized products and services. While businesses produced a seemingly endless variety of higher quality products, the sheer amount of choice engendered consumer confusion and some fraud. By the start of the 20 th Century, consumers were often lied to in advertisements and the composition of the food and medicine they were consuming was difficult to determine. In 1906, the United States passed the Food and Drug Acts. Still in effect today, they prohibit interstate commerce in misbranded and adulterated foods, drinks and drugs. In 1990, the Nutrition Labeling and Education Act was passed. It required all packaged foods to bear nutrition labeling and all health claims for foods to be consistent with terms defined by the U.S. Government. As a result, the food ingredient panel, serving sizes and terms such as “low fat” and “light” were standardized. It is almost inconceivable that a consumer would purchase a product without this information today.
Why should software be any different? Consumer data and privacy is put at risk daily by the software they use in the PCs, smartphones, tablets and other consumer devices. The software-based services they use are also at risk. Their retailers’, banks’, credit monitors’ and governments’ systems are being hacked at a higher frequency and cost. Open Source Software – Boon & Bain A great deal of this is due to the increased use of open source code elements in software today. It is estimated that more than 90% of the software in development and use today contains open source. Its use is tied to its ability to be quickly integrated, delivering tremendous levels of innovation. However, this innovation comes with a cost. In 2018, 16,555 known software vulnerabilities were published by National Vulnerability Database (NVD), a new record. The open source community is now constantly finding and publishing new security vulnerabilities. Consequently, known open source software vulnerabilities become a road-map for hackers to target and attack businesses’ systems. Those systems that contain known vulnerabilities that have been left unpatched or unaddressed are likely to fall victim to data loss and theft. Build Your Own Software Composition “Nutrition” Label Be it developed in-house, custom-built by a third-party, off-the-shelf or some kind of amalgamation; the level of software sophistication and complexity continues to grow rapidly. Someday, in order to better protect businesses and consumers, governments may mandate, like they have in the food and medicine industries, software composition or “software nutrition” labeling. Until that day comes, businesses should require their software vendors to provide them with this information. Unfortunately, not all software vendors provide this information citing many reasons, such as protection of proprietary IP, among others. Smart businesses can take a more proactive approach by analyzing third-party software and building a software component list of their own. While a great deal of the code delivered today to enterprises is accompanied by documentation that lists the software components, many third-party vendors do not provide their clients the list of software components. Additionally, third-party software products are likely to be a combination of in-house developed and procured code. This makes analyzing and tracking open source software elements incredibly challenging. Given that this code is delivered in binary format, businesses have had to take the composition documentation on faith. New fingerprint-based binary scanning technologies make building a software “nutrition” composition label relatively easy and straightforward. Additionally, these scanners find small, open source code elements, catalog them and match them against databases of known security
Page 1 and 2:
Data Breaches: Beyond Exposing Iden
Page 3 and 4:
CONTENTS (cont') Prioritizing Secur
Page 5:
@CYBERDEFENSEMAG CYBER DEFENSE eMAG
Page 22 and 23:
Data Breaches: Beyond Exposing Iden
Page 24 and 25:
About the Author Kem Gay is an Inte
Page 26 and 27:
Rip Off the Band-Aid This leaves us
Page 28 and 29:
Why Biometric Data Use Poses Unique
Page 30 and 31:
• DNA Kits: If you purchased or u
Page 32 and 33:
How to be Workforce Ready and Stand
Page 34 and 35:
Maximiliano Gigli, a third-year cyb
Page 36 and 37:
Interestingly, the two groups diffe
Page 38 and 39:
Cross-site Scripting Is an Underrat
Page 40 and 41:
Stealing HTML5 web storage data: HT
Page 42 and 43:
Cybersecurity in New York City, the
Page 44 and 45:
A boom in cybersecurity startups se
Page 46 and 47:
illion risks and threats among its
Page 48 and 49:
Some Important Developments in the
Page 50 and 51:
About the Author Sharmistha Sarkar
Page 52 and 53:
employees to contractors and sub-co
Page 54 and 55:
The Internet of Things Engineering
Page 56 and 57: About The Author Milica D. Djekic i
Page 58 and 59: kind. Many of them require some kin
Page 60 and 61: 2019 Risks in Focus: Cyber Incident
Page 62 and 63: However, the past year has also wit
Page 64 and 65: Why Insider Threats Are One of the
Page 66 and 67: Unlike with outside security threat
Page 68 and 69: Organizations will also frequently
Page 70 and 71: The US Must Catch Up to Other Promi
Page 72 and 73: The fact is, the wider internationa
Page 74 and 75: Integrate Compliance and Regulation
Page 76 and 77: Security have and have-nots How org
Page 78 and 79: 1. People Having the right people c
Page 80 and 81: sources (such as syslog’s, Net Fl
Page 82 and 83: Limitations of Current Endpoint Sec
Page 84 and 85: For effective detection, most EDR s
Page 86 and 87: Why Wi-Fi Hacking Will Persist Desp
Page 88 and 89: About the Author Ryan Orsi is Direc
Page 90 and 91: questions such as, “Who added a w
Page 92 and 93: About the Author Josh Paape is an O
Page 94 and 95: for well-known, repeatable needs fi
Page 96 and 97: Overcoming Software Security Issues
Page 98 and 99: Implementing Security Checks at Str
Page 100 and 101: Phishing in the Dark: Employee Secu
Page 102 and 103: phishing threats. Furthermore, almo
Page 104 and 105: Unfortunately, once an application
Page 108 and 109: vulnerabilities. If they find vulne
Page 110 and 111: I can't get no satisfaction, I can'
Page 112 and 113: How Organizations Should Choose a L
Page 114 and 115: load balancers capable of integrati
Page 116 and 117: SaaS DNS Security: Are you Protecte
Page 118 and 119: associated with any security event
Page 120 and 121: 120
Page 122 and 123: 122
Page 124 and 125: 124
Page 126 and 127: 126
Page 128 and 129: 128
Page 130 and 131: 130
Page 132 and 133: 132
Page 134 and 135: 134
Page 136 and 137: 136
Page 138 and 139: 138
Page 140 and 141: 140
Page 142 and 143: 142
Page 144 and 145: 144
Page 146 and 147: 146
Page 148 and 149: 148
Page 150 and 151: We’ve launched http://www.CyberDe
Page 152 and 153: Marketing and Partnership Opportuni
Page 154 and 155: Regent University’s Institute for
Page 156 and 157:
156
show all

CDM-CYBER-DEFENSE-eMAGAZINE-March-2019

Create successful ePaper yourself

Delete template?

Save as template?