The Cyber Defense eMagazine November Edition for 2023

More documents

Recommendations

Info

Zombie APIs: The Scariest Threat Lurking in The Shadows? By Dan Hopkins, VP of Engineering at StackHawk IT modernization and digital transformation initiatives, combined with faster software deployment lifecycles, has caused an exponential increase in the size and scale of API ecosystems within organizations. Designed to rapidly and seamlessly connect consumers and businesses to vital data and services, APIs power modern enterprises and applications. APIs are constantly in action, working in the background for when consumers finally book that dream vacation or place an online takeout order after a long workday. With API usage so widespread, touching every industry, and the vast treasure troves of sensitive data they boast access to, it comes as no surprise that cyber criminals are increasingly exploiting and abusing APIs to execute malicious attacks. The velocity and scale of API attacks has caused many to question the strength of their API security posture and deeply analyze where most API-centric risks persist. That brings us to Zombies, Zombie APIs that is. If the name alone doesn’t initially spark fear, Zombie APIs are APIs that have become abandoned, outdated or forgotten by an organization. Similar to a Zombie who revives from the dead in a horror movie, Zombie APIs should be deceased but continue to lurk in the shadows within corporate environments. Recent research from Salt Security revealed that 54% of security leaders categorize Zombie APIs as their greatest concern when it comes to API security. Up from 42% in the previous report. Cyber Defense eMagazine – November 2023 Edition 60 Copyright © 2023, Cyber Defense Magazine. All rights reserved worldwide.
As Zombie APIs are essentially forgotten and out of mind, there is no regular patching or updates being made in either a functional or security capacity. Therefore, Zombie APIs boast the power to become an incremental security risk. They are removed from API documentation and security testing programs, leaving them to rot over time and expose new vulnerabilities. While Zombie APIs pose significant threats to cyber resilience, there is one other great cause for concern within API security - the presence of Shadow APIs. Shadow APIs can be defined as third-party APIs that exist outside of an organization's official API ecosystem, remaining invisible to most and void of security controls. Oftentimes, these types of APIs are created and deployed by well-meaning developers on a time crunch to meet business and application innovation demands. Despite no ill-intent from a developer, these unmanaged, non-restricted APIs have the potential to cause severe vulnerabilities. Shadow APIs often fail to adhere to correct API governance standards, may not meet security best practices such as those outlined in the OWASP API Security Top 10, and may also expose sensitive data. The presence of Zombie and Shadow APIs remains widespread across organizations, which in turn creates many opportunities for sly and sneaky bad actors to execute an attack. The root cause of both is simple: Broken and siloed communication between developers and security teams. Developers and engineering teams are rapidly creating APIs to keep pace with innovation, and security personnel are willfully trying to protect and manage them. But both play a significant role in securing the API ecosystem. Particularly in relation to API documentation and inventory management. As the saying goes, “you cannot protect what you cannot see”. Developers and engineers not only have a duty of care to keep a robust catalog of the APIs created and deployed, but also to brief the appropriate parties about deprecated APIs no longer being utilized. This intel should be continually shared with security teams to ensure API inventories remain complete, make certain appropriate patching and testing initiatives are carried out and allow the complete removal of expired APIs. Mitigating the volume of Zombie APIs requires developer and security teams to liaise with one another to comprehensively define and articulate robust API retirement policies and procedures and determine who is responsible for executing such activity. This practice will ensure that inactive APIs are formally taken out of an ecosystem and avoid future attacker retaliation. Similarly, alleviating the threat of Shadow APIs also calls for deep synergy and collaboration amongst teams and strong DevSecOps practices. Security teams must work with engineers and developers to define and enforce governance policies for APIs being created. These policies should clearly describe which individuals can create new APIs, how they should be designed, deployed and utilized, and offer insight into the required testing mechanisms new APIs must undergo prior to being pushed into production. The existence and proliferation of Zombie and Shadow APIs ultimately comes down to two factors: broken communication and human error. Breaking down the barriers of communication and solid collaboration amongst developers and security teams will significantly improve API documentation, inventory management and help enforce security best practices. Without it, organizations will continue to be plagued with API risk, and remain unsuspecting of possible threats and unprotected against exploits. Cyber Defense eMagazine – November 2023 Edition 61 Copyright © 2023, Cyber Defense Magazine. All rights reserved worldwide.
Page 1 and 2:
Artificial Deception: The State Of
Page 3 and 4:
OT Cybersecurity: Safeguarding Buil
Page 5 and 6:
The Crumbling Castle --------------
Page 7 and 8:
@CYBERDEFENSEMAG CYBER DEFENSE eMAG
Page 9 and 10: Cyber Defense eMagazine - November
Page 21 and 22: Artificial Deception: The State Of
Page 23 and 24: Human-in-the-Middle In creating AI
Page 25 and 26: effectiveness of defenses in place
Page 27 and 28: this information and related activi
Page 29 and 30: leading to the potential exploit of
Page 31 and 32: An Age-by-Age Guide to Online Safet
Page 33 and 34: Educate: It’s never too early to
Page 35 and 36: About the Author Chelsea Hopkins is
Page 37 and 38: Securing Infrastructure Against Bre
Page 39 and 40: AI And Ad Fraud: Growing Risks for
Page 41 and 42: enable organisations to make better
Page 43 and 44: Bolster an Organizational Cybersecu
Page 45 and 46: in EDP in addition to regular cyber
Page 47 and 48: prioritize a Secure Software Develo
Page 49 and 50: 6. Deployment: Once the software ha
Page 51 and 52: Beyond Passwords: AI-Enhanced Authe
Page 53 and 54: 3. Improving the Defensive Cybersec
Page 55 and 56: 7 Steps to Build a Defense in Depth
Page 57 and 58: The same risks associated with USB
Page 59: About the Author Mr. Spears has ove
Page 63 and 64: How To Combat the Mounting ‘Hackt
Page 65 and 66: y pro-Russia hacktivists. These hav
Page 67 and 68: Unlike IT cybersecurity attacks, wh
Page 69 and 70: The Cyber Risk Nightmare and Financ
Page 71 and 72: fell -11.3%, and underperformed the
Page 73 and 74: DevOps’ Big Challenge: Limiting R
Page 75 and 76: By making this single alteration to
Page 77 and 78: ChatGPT For Enterprises Is Here - B
Page 79 and 80: usiness email communication, data s
Page 81 and 82: Chromecast End-of-Life Announcement
Page 83 and 84: Going beyond awareness and fosterin
Page 85 and 86: But the most crucial innovations ha
Page 87 and 88: About the Author Vinaya is a highly
Page 89 and 90: card transactions often comprise a
Page 91 and 92: About the author Stefan Auerbach, C
Page 93 and 94: Consider the following data and rea
Page 95 and 96: 4. Create a digital estate plan. Th
Page 97 and 98: do untold damage to a company’s r
Page 99 and 100: About the Author Sean Newman is the
Page 101 and 102: eing monitored to protect against m
Page 103 and 104: Developers Hold the New Crown Jewel
Page 105 and 106: the fact that many organizations la
Page 107 and 108: Expect to Fail: How Organizations C
Page 109 and 110: The more personnel that you train t
Page 111 and 112:
How to Create a Threat Hunting Prog
Page 113 and 114:
5. Decide Whether to Automate Altho
Page 115 and 116:
How To Improve Security Capacities
Page 117 and 118:
eing noticed in a practice and some
Page 119 and 120:
In Pursuit of a Passwordless Future
Page 121 and 122:
than to guess their password, but i
Page 123 and 124:
configurable data privacy. These bu
Page 125 and 126:
It’s Time to Tear Down the Barrie
Page 127 and 128:
Is it Time to Re-evaluate Your Thre
Page 129 and 130:
Building For a More Secure Future:
Page 131 and 132:
OAuth 1.0 to OAuth 2.0, or increasi
Page 133 and 134:
About the Author Jeremy Butteriss a
Page 135 and 136:
which helped feed the development o
Page 137 and 138:
Protecting Your Business and Person
Page 139 and 140:
Mitigating Phishing with Domain Nam
Page 141 and 142:
About the Author Brian Lonergan, VP
Page 143 and 144:
adoption is more than just an IT tr
Page 145 and 146:
North Korea-Russia Summit A new all
Page 147 and 148:
factors on both sides of the confli
Page 149 and 150:
That being said, the Russian regime
Page 151 and 152:
Protecting Critical Infrastructure
Page 153 and 154:
spared from the wrath of Russian ha
Page 155 and 156:
About the Author Richard Staynings
Page 157 and 158:
The Illusion of Ruthless Prioritiza
Page 159 and 160:
Ditch the Worry - Switch to Secure
Page 161 and 162:
others are continuing to increase a
Page 163 and 164:
Shifting Left Means Shifting Smart:
Page 165 and 166:
triggers to allow for a more standa
Page 167 and 168:
• The Rise of Remote Work: The CO
Page 169 and 170:
About the Author Jaye Tillson is a
Page 171 and 172:
In terms of prioritization, out of
Page 173 and 174:
Three Things to Know About the New
Page 175 and 176:
For example, if a security leader n
Page 177 and 178:
Cloud adoption has witnessed a sign
Page 179 and 180:
The Tech Jobs That AI Will Not Disr
Page 181 and 182:
Examples of tech jobs that will sur
Page 183 and 184:
Cyber Defense eMagazine - November
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Free Monthly Cyber Defense eMagazin
Page 193 and 194:
Page 195 and 196:
show all

The Cyber Defense eMagazine November Edition for 2023

Create successful ePaper yourself

Delete template?

Save as template?