CDM-CYBER-DEFENSE-eMAGAZINE-March-2019

More documents

Recommendations

Info

Limitations of Current Endpoint Security Approaches Endpoint security has traditionally been about comparing an endpoint with a signature in a database. The signature database was initially downloaded from a central server to a local server in the organization. Every endpoint would then check with this database to compare file-hashes on their system with signatures to determine if a file was malicious or not. As the signatures went into billions of hashes, databases started growing bigger and bigger and started moving to the cloud where a central database served as a repository to all known good and bad file hashes. This did not solve the problem of zero-day malware which by-definition was a malicious file that has not been seen before, and hence does not have a hash in the cloud. To solve this problem, organizations started deploying machine learning and sandboxing solutions. Sandboxing
solutions simply played or executed this zero-day-file that was not seen before in a safe environment where its behavior was analyzed to see if it displayed malicious behavior. Likewise, machine learning was used to look at files that have taken source code from a known exploit but changed the code a bit to create a new executable and hence a new hash. This form of attack, where you changed a known malware slightly to create a brand-new malware with a new hash value, but the source code was essentially the same, was called polymorphism. The Birth of Endpoint Detection and Response (EDR) The security industry changed with Operation Aurora, a series of cyber-attacks conducted against well-known technology companies by a nation state. Operation Aurora exploited a well-known vulnerability in Internet Explorer to spawn a PowerShell that could be used to execute commands on the target system. The earlier approach of checking file hashes would not have worked as Internet Explorer and PowerShell are legitimate commands; it is the sequence that is illegitimate. A browser could spawn another browser, it could spawn a music player but should not be spawning a power-shell under normal circumstances. The rise of nation state attackers who kept infiltrating each other’s private enterprise and critical sectors such as finance and energy contributed to this trend. Endpoint detection and response tools work by monitoring endpoint and network events and recording the information in a central database where further analysis, detection, investigation, reporting, and alerting take place. Endpoint Detection and Response solutions had four components: 1. Detection 2. Threat hunting 3. Response & Remediation 4. Managed Services It all starts by recording everything at the endpoint – every file access, every registry call and every network connection was recorded from the endpoint and sent to the cloud. These actions were stitched together and scanned to see if there were malicious or suspicious sequences of activities, such as an internet browser spawning a PowerShell. Likewise, an attacker running port scans and scanning systems laterally using known windows utilities would evade signature defenses but be caught by an endpoint detection and response system as his behavior would trigger an alarm.
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 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 106 and 107: Software Should Come with a “Nutr
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?