One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 2102430 |
| Date de publication | 2020-12-15 11:00:00 (vue: 2020-12-15 12:05:38) |
| Titre | Why application-layer encryption is essential for securing confidential data |
| Texte | This blog was written by an independent guest blogger. Your business is growing at a steady rate, and you have big plans for the future. Then, your organization gets hit by a cyberattack, causing a massive data breach. Suddenly, your company’s focus is shifted to sending out letters to angry customers informing them of the incident - which is required by law in most states - and devising strategies to deal with the backlash. This is an all too common scenario for many businesses, and the unfortunate truth is that most organizations fail to adopt the correct cybersecurity procedures until after an attack. The good news is that with a proactive approach to protecting your data, these kinds of nightmares can be avoided. New technology is constantly providing hackers new opportunities to commit cybercrimes. Most organizations have encrypted their data whether it’s stored on the cloud or in a server provided by their web host, but this isn’t enough. Even properly encrypted disc level encryption is vulnerable to security breaches. In this article, we will discuss the weaknesses found in disc level encryption and why it’s best to ensure your data is encrypted at the application layer. We’ll also discuss the importance of active involvement from a cybersecurity team in the beginning stages of application development, and why developers need to have a renewed focus on cybersecurity in a “security-as-code” culture. The importance of application-layer security Organizations all too often have a piecemeal, siloed approach to security. Increasingly competitive tech environments have pushed developers into building new products at a pace cybersecurity experts sometimes can’t keep up with. This is why it’s becoming more common for vulnerabilities to be detected only after an application launches or a data breach occurs. Application layer encryption reduces surface area and encrypts data at the application level. That means if one application is compromised, the entire system does not become at risk. To reduce attack surfaces, individual users and third parties should not have access to encrypted data or keys. This leaves would-be cybercriminals with only the customer-facing end of the application for finding vulnerabilities, and this can be easily protected and audited for security. Building AI and application-layer security into code Application layer security and building security into the coding itself requires that your DevOps and cybersecurity experts work closely together to form a DevSecOps dream team. Developers are increasingly working hand-in-hand with cybersecurity experts from the very beginning stages of software development to ensure a “security-as-code” culture is upheld. However, there are some very interesting developments in AI that present opportunities to streamline this process. In fact, 78% of data scientists agree that artificial intelligence will have the greatest impact on data protection for the decade. Here are four ways AI is transforming application layer security: 1. Misuse detection or application security breach detection Also referred to as signature-based detection, AI systems alert teams when familiar attack patterns are noticed. |
| Envoyé | Oui |
| Condensat | “key “outliers “risk “security able abnormal about access accessed account achieve acknowledges active activities activity actor address adequately adopt adopting after agree alert all along also always among amount analogous analysis angry anomalies anomaly another any application approach are area argument article artificial attack attacks attributes audited automate avoid avoided backlash bare based because become becoming beginning behavior being best better big blog blogger breach breaches building business businesses but can can’t careful cause causing changes choose city” close closely cloud code code” coding commit common companies company’s compared competitive compromised confidential constantly constitutes contains continue continuous correct correlations could credentials credit culture customer customers cyberattack cybercrimes cybercriminals cybersecurity data database ddos deal decade decrypted deployment detect detected detection developer developers development developments devising devops devsecops disc discuss discussed does dollars downloaded dream earn easily education effective embeds enable encrypted encryption encrypts end enough ensure entire environments especially essential even expert experts exploiting exploration facing fact factor fail familiar finding fix flag floodgates focus form found four free from fundamental further future gain get gets glaring goal good great greatest growing guest hacker hackers hand hardware has have heavily here hit host hosts how however identified identify imagine impact importance important importantly incident incidents incoming increasingly independent individual informing intelligence interesting investigation involvement isn’t issues it’s itself keep key keys kinds launches law layer learn leaves less letters level likely locked low made malicious many massive means measures method methods millions minimum misuse monitoring more most necessary need network new news nightmares norm normal not noticed now observations obtain occurs offer offline often once one only open opportunities opposite organization organizations out own pace part parties partnership party past patterns piecemeal pinpointed plans practices predictive present prevention previously proactive proactively probability procedures process products properly protected protecting protection protections proverbial provide provided providing pushed quality quickly rate real really reduce reduces reducing referred relevant relies renewed reputable request required requires research risk run same scans scenario scientists score score” scoring secure securing security security: sell sending sensitive server servers sets several shifted should showing sight signature significant siloed similar simply single sites software some sometimes ssl stages states steady stealing stolen stored strategies streamline strong suddenly sure surface surfaces suspicious system systems team teams tech technology them then these third though threat tied time together too town track traditional training transforming troubling truth type understanding unfortunate unknown until unusual upheld user user’s users utilizing venue versus very views volume vulnerabilities vulnerability vulnerable wanted way ways we’ll weaknesses web what when whether which why wide will work working worse worst would writing written yet your |
| Tags | Data Breach Vulnerability Threat |
| Stories | Deloitte |
| 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.