One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 1336807 |
| Date de publication | 2019-09-16 13:00:00 (vue: 2019-09-16 15:08:22) |
| Titre | Hacker prevention: tips to reduce your attack surface |
| Texte |
These days it seems that every time you open your favorite news source there is another data breach related headline. Victimized companies of all sizes, cities, counties, and even government agencies have all been the subject of the “headline of shame” over the past several months or years. With all this publicity and the increasing awareness of the general public about how data breaches can impact their personal privacy and financial wellbeing, it is no surprise that there is a lot of interest in preventing hacking. The trouble is that there is no way to prevent others from attempting to hack into any target they chose. Since there is a practically limitless number of targets to choose from, the attacker need only be lucky or skilled enough to succeed once. In addition, the risk of successful prosecution of perpetrators remains low. However, while you can’t prevent hacking, you can help to reduce your attack surface to make your organization less likely to be the subject of attacks.
At this point, lets differentiate between opportunistic attacks and targeted attacks. Opportunistic attacks are largely automated, low-complexity exploits against known vulnerable conditions and configurations. Ever wonder why a small business with a small geographic footprint and almost no online presence gets compromised? Chances are good they just had the right combination of issues that an automated attack bot was looking to exploit. These kinds of events can potentially end a small to medium business as a going concern while costing the attacker practically nothing.
Targeted attacks are a different story all together. These attacks are generally low, slow and persistent; targeting your organizations technical footprint as well as your employees, partners and supply chain. While targeted attacks may utilize some of the same exploitable conditions that opportunistic attacks use, they tend to be less automated in nature so as to avoid possible detection for as long as possible. In addition, they may involve a more frequent use of previously unknown exploit vectors (“zero day’s”) to reach their goals or abuse trusted connections with third parties to gain access to your organization. Ultimately it doesn’t matter which of these kinds of attacks results in a breach event, but it is important to think of both when aligning your people, processes and technology for maximum effect to mitigate that risk.
There have been many articles written regarding best practices for minimizing the risk of a cyber-security incident. Rather than recount a list of commonly cited controls, I would like to approach the topic from a slightly different perspective and focus on the top six technical controls that I feel are likely to help mitigate the most risk, provided that all the “table stakes” items are in place (i.e. you have a firewall, etc.).
Patch and Update Constantly: Ultimately the most hacker-resistant environment is the one that is best administered. Organizations are short cutting system and network administration activities through budget / staff reductions and lack of training. This practice often forces prioritization and choice about what tasks get done sooner, later or at all. Over time this creates a large, persistent baseline of low to medium risk issues in the environment that can contribute to a wildfire event under the right conditions. Lack |
| Envoyé | Oui |
| Condensat | “headline “table “the “zero email help lack mitigate reduce some ability able about abuse access accounts across action activities activity addition adjacent administered administration after against agencies alert aligning all allocate almost alone also always another any app application applications applied approach architecture are articles asset attachments attack attacker attackers attacks attempting attempts authentication authentication: automated avoid awareness back based baseline because become becoming been best between bot both breach breaches budget business but call calls can can’t capability cause cell centric certain chain chance chances characters check choice choices choose chose cited cities click clues combination combined coming common commonly communicate companies complete complexity comprise compromised concern conditions configuration configurations connections consistently constantly: consumers consuming content; contribute contributes control controls corporate costing counties cover cracked creates credentials critical current cutting cyber cybersecurity data day day’s” days decide decisions default defenders destined detect detection detective device device/carrier devices different differentiate difficult disclosed does doesn’t done double down dramatically driven early effect egress eliminate email employees enable end endpoint endpoints enough enterprise entire entirely entry environment environments eponymous etc even event events ever every execute exploit exploitable exploits exposures facebook™ faces factor factor/multi fail failed favorite feel filtering: financial firewall focus focused footprint forces frequent from fully further gain general generally geographic get gets given goals going good government hack hacker hacking had hardware hare” has have headline help history how however huddle identify impact implementations important incident includes inconsistently increase increasing individual infect infection infections informed infrastructure infrastructure: instagram™ intercepted interest internal inventory involve issues items its just kept kind kinds known lack large largely lastly later layered less lets like likely limit limited limiting limitless list login logs long looking lot low lucky maintain majority make makes making malicious malware management many matter maximizes maximum may mean media medium messages methods migrations minimize minimizing mission mitigate mobile model mole months more most multi nature need network never news next nodes nothing number often once one online only open opportunistic opportunity opposed organization organizations other others otherwise out outside over overlooked paired part parties partners past patch patched patching people perimeter perpetrators persist persistent persistent; personal perspective phase phone phones piece pin place platform point pointed policies port porting possible potentially practically practice practices presence prevent preventing prevention prevention: previously prioritization privacy processes programs prosecution protect protected provide provided provider proxy public publicity put race rather reach really receiving recount reduce reduction reductions regard regarding regardless regulated related remaining remains remediation reputable require requiring resistant resources; response response: result results right risk robust root run running same schemes second secure security security: seems segmentation sense servers several shame” short should shutdown siem/soapa/soar since single six size sizes skilled slightly slow small sms social software some something sooner source spread staff stakes” staying steadily step steps stores story strategies strong subject succeed successful such suite supply support/life sure surface surprise system system/application take target targeted targeting targets task tasks teaches technical technology tedious tend |
| Tags | Data Breach Malware Hack |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.