Saturday, June 15, 2024

SMTP Strict Transport Security Comming soon for Gmail and Other Webmail Users

Google, Microsoft, Yahoo and Comcast are expected to adopt the standard Mail services and implement the SMTP Strict Transport Security following by  Gmail users soon.

Elie Bursztein, the head of Google’s anti-abuse research team, said at RSA Conference that SMTP STS will be a major impediment to man-in-the-middle attacks that rely on rogue certificates that are likely forged, stolen or otherwise untrusted.

All the webmail sevice providers bringing a measure of security similar to certificate pinning to the webmail services.

According to the Draft of which was submitted to the IETF in March 2016.

SMTP STS is a mechanism enabling mail service providers to declare their ability to receive TLS-secured connections, to declare particular methods for certificate validation, and to request sending  SMTP servers to report upon and/or refuse to deliver messages that cannot be delivered securely.

Bursztein’s declaration came during a discussion which he represented how diverse dangers to corporate and individual Gmail records, for example, spam, phishing, malware, pantomime and capture assaults change by industry and geology.

Bursztein’s said “Every minute, we have to stop more than 10 million attacks with 99.9 percent precision. The way we are doing this is reacting quickly to emerging threats.”

  The mechanism described is in draft separated into four logical components:

  • Policy semantics: whether senders can expect a server for the recipient domain tosupport TLS encryption and how to validate the TLS certificate presented
  • Policy authentication: how to determine the authenticity of  published policy delivered via DNS
  • Failure report format: a mechanism for informing recipient domains about aggregate failure statistics
  • Failure handling: what sending MTAs should do in the case of policy failures

Related Technologies of DANE Record designed to upgrade opportunistic encryption into required encryption.DANE requires DNSSEC [RFC4033] for the secure deliver of policies; the mechanism described here presents a variant for  systems not yet supporting DNSSEC, and specifies a method for reporting TLS negotiation failures.

According to the (IETF) The primary difference between the mechanism described here and DANE is that DANE requires the use of DNSSEC to authenticate DANE TLSA records, whereas SMTP STS relies on the certificate authority (CA) system and a trust-on-first-use (TOFU) approach to avoid  interception.

Burszstein said that , a decision to add visual cues to users that certain Gmail messages may be untrusted helped spike adoption of encryption. One such measure was a UI change to display a broken lock in the inbox indicating that the email about to be sent is being sent in the clear.

“This tells you the email you are about to send is not encrypted and could be intercepted in transit,” he said. “This helps the user make a better choice by highlighting this to the user.”

He also pointed to visual cues on the authentication front such as Gmail’s assigning of icons to trusted users while throwing up a red question mark for unauthenticated senders. This too was a driver in increasing adoption of all three protections, reducing the number of unauthenticated messages in 2014 (5.8 percent) to last year (1.8 percent).

Also Read :

Website

Latest articles

Sleepy Pickle Exploit Let Attackers Exploit ML Models And Attack End-Users

Hackers are targeting, attacking, and exploiting ML models. They want to hack into these...

SolarWinds Serv-U Vulnerability Let Attackers Access sensitive files

SolarWinds released a security advisory for addressing a Directory Traversal vulnerability which allows a...

Smishing Triad Hackers Attacking Online Banking, E-Commerce AND Payment Systems Customers

Hackers often attack online banking platforms, e-commerce portals, and payment systems for illicit purposes.Resecurity...

Threat Actor Claiming Leak Of 5 Million Ecuador’s Citizen Database

A threat actor has claimed responsibility for leaking the personal data of 5 million...

Ascension Hack Caused By an Employee Who Downloaded a Malicious File

Ascension, a leading healthcare provider, has made significant strides in its investigation and recovery...

AWS Announced Malware Detection Tool For S3 Buckets

Amazon Web Services (AWS) has announced the general availability of Amazon GuardDuty Malware Protection...

Hackers Exploiting MS Office Editor Vulnerability to Deploy Keylogger

Researchers have identified a sophisticated cyberattack orchestrated by the notorious Kimsuky threat group.The...
Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Free Webinar

API Vulnerability Scanning

71% of the internet traffic comes from APIs so APIs have become soft targets for hackers.Securing APIs is a simple workflow provided you find API specific vulnerabilities and protect them.In the upcoming webinar, join Vivek Gopalan, VP of Products at Indusface as he takes you through the fundamentals of API vulnerability scanning..
Key takeaways include:

  • Scan API endpoints for OWASP API Top 10 vulnerabilities
  • Perform API penetration testing for business logic vulnerabilities
  • Prioritize the most critical vulnerabilities with AcuRisQ
  • Workflow automation for this entire process

Related Articles