Apple announced this week that the maximum
lifetime of SSL / TLS certificates on its devices and Safari browser would
be limited to 398 days (1 year, and 1 month to cover the renewal period). The
change, announced by Apple at the CA / Browser Forum meeting in Bratislava,
Slovakia, will take effect for certificates
issued after August 31, 2020.
Apple’s announcement follows a failure of the CA / B Forum’s vote on one-year certificates (Bulletin SC22), which was held in August 2019, and reflects a continuing trend to shorten lifespan certificates. Following this vote, Google had also expressed its intention to reduce certificate lifetime outside the framework of the CA / B forum if they do not position themselves quickly. This announcement is a bit of a surprise, we would rather have thought that Google or Mozilla would take the first step.
What are the consequences for companies and their SSL / TLS certificates?
Is shorter validity a good thing?
The shorter the validity period of a
certificate, the more secure the certificate. By requiring replacement of
certificates over a shorter period of time, security updates are made to
certificates, they deploy faster. The shorter private key lifetime of a
certificate is also a strong recommendation from online security players to
limit the potential duration of fraud following a compromise.
From a security perspective, everyone agrees
that reducing the life of certificates is a good thing. The problem lies on the
operational side with the consequences of this reduction being: more frequent
intervention on certificates, therefore greater complexity in keeping an up to
date inventory and the need for optimal organization with partners for
certificate issuance.
Should Apple’s announcement be taken into account?
Safari is one of the two main web browsers, with 17.7% in January 2020, behind Google Chrome (58.2%) and ahead of Microsoft Internet Explorer and Edge (7.1%). It is difficult to ignore the announcement as it will affect 1/5 of Internet users, what is more is that if Google does follow, it is better to anticipate and prepare. Nameshield’s has already adopted this stance.
Things to keep in mind
Certificates issued
before September 1, 2020 are not affected by this change. They will remain valid for the entire
two-year period. All certificates issued
on or after September 1 must be renewed each year to be considered reliable
by Safari.
We must therefore prepare to move towards
having certificates with a maximum duration of one year compared to the current
two years. Being able to rely on a partner and effective tools is more
essential than ever.
Towards the end of the correlation between authentication and technical
certificate management
What seems to be taking shape within the CA / B
Forum is the idea of allowing an authentication duration identical to that
which we know today (two years) while forcing the certificates to be replaced
several times during this same period.
The main Certification Authorities, the bodies
that issue certificates, anticipate these changes and are working on several
automation systems to manage certificate life cycle. They would thus limit the
need to go through a potentially cumbersome re-authentication procedure with
each replacement. Companies could replace their certificates as many times as
they want during this period. This would make it possible to anticipate possible
further reductions in the maximum lifetime of certificates.
The trend is also towards the installation of
automation tools for the maintenance of a precise inventory of certificates on
the one hand and technical reinstallation on the other. Nameshield is closely
monitoring these various developments and will allow you to continue working
with confidence.
Our team is also at your disposal to anticipate these changes and answer any questions you may have.
Following the announcement on Sunday February
16, of Agnès Buzyn’s candidacy to Paris municipal elections, several political journalists
discovered on Monday that the domain name buzyn2020.fr was registered but
redirected towards “Paris en commun”,
the campaign website of another candidate, Anne Hidalgo.
Several other names were registered on Sunday
night, also redirecting towards Paris en
commun’s homepage like buzyn2020.paris, agnesbuzyn2020.fr and
agnesbuzyn2020.com.
If several of these names were anonymously registered, two of them were registered by the association “Montreuil en Commun”, a group of “four municipal councilors” who claims to be “without any political label” and explains to Numerama the fact that these names were available “indicates the improvisation of her candidacy and LREM’s lightness regarding a serious matter such as a candidacy to run for Paris’ mayor”.
Raising awareness to cybersquatting risks
The LREM candidate will not be able to use the
domain name buzyn2020.com either, which was registered on Monday by Crisalyde, a
risk and crisis management consulting company.
“I took the opportunity to raise awareness. It’s my job, I saw a risk and I took advantage of it”, explains Selim Miled, Crisalyde’s CEO, to the Parisien.
Cybersquatting is a practice that consists in
taking a domain name by registering it, using or mentioning a trademark, a
business name, a patronym or any name on which the applicant has any right, in
order to make material or moral profit from its current or future notoriety.
Thus, Crisalyde registered 6 domain names: buzyn.paris,
agnesbuzyn2020.paris, buzynpourparis.com, buzynpourparis.fr, buzyn2020.info and
buzyn2020.com. “As soon as Agnès Buzyn’s
team contacts me, I will give them the domain name at the purchased price, with
a friendly advice” adds Selim Miled.
What strategy to adopt against cybersquatting?
Agnès Buzyn’s team will have to contact the
persons who registered these names, who may decide to graciously give them back
or resell them at prices they will have set.
However, legal actions exist aiming to retrieve a cybersquatted domain name, like the UDRP procedure (Uniform Domain Name Dispute Resolution Policy). This procedure will allow to suppress or transfer the domain name.
And lastly, in order to prevent any cybersquatting risk, it is recommended to implement a domain names registration monitoring to be immediately alerted of any new domain names registration that can potentially infringe your notoriety or your business.
For more information on our online brand protection expertise and domain names recovery procedures, don’t hesitate to contact a Nameshield consultant.
The 67th annual ICANN Summit, a summit dedicated to Internet naming regulations, was to be held in Cancún, Mexico, from 7th to 12th March. Often referred to by the acronym ICANN67, it is finally another acronym COVID19 that designates the now famous coronavirus that forced ICANN to reconsider all the logistics of this major event.
Since 1999,
ICANN has organised three annual meetings devoted to the regulations applicable
to Internet naming and a fourth devoted to more operational aspects, often
referred to as the GDD Summit (Global Domain Division Summit). These meetings
are an opportunity for participants from some 150 countries to discuss live the
hot topics related to the Domain Name System (DNS).
For the
past few weeks, however, world attention has focused on a completely different
subject: the ongoing spread of the coronavirus, which according to the latest
figures available has contaminated some 75,465 people in mainland China and
caused the death of 2,236 people since its emergence in December in Wuhan,
capital of Hubei province. While South Korea also now has more than 150
confirmed cases, the list of countries with confirmed cases keeps growing. More
than 30 countries are now in this situation.
Quite
logically, in recent weeks, behind the scenes of the ICANN organization,
coronavirus has been rising as a major concern for the players in the domain
name industry. More and more potential participants were talking about the fact
that they would prefer not to travel for this event, which is important to
them, while others were asking whether it was appropriate to hold this event in
such a context. Recent cancellations of similar events have indeed echoed their
concerns. Earlier this month, the GSMA, the organizers of the world’s largest
mobile industry exhibition, Mobile World Congress 2020, effectively cancelled
the event after more than 30 exhibitors and sponsors withdrew due to the
outbreak. The Fintech Festival of India (IFF 2020) organised by the government
of Maharashtra, the Ministry of Electronics and Information Technology (MeitY),
the National Payments Corporation of India (NPCI) and the Fintech Convergence
Council also similarly announced this week that it would postpone the event to
a “more appropriate time” due to coronavirus-related issues. The
event was scheduled to take place on 4-5 March 2020.
At the 19
February session of the ICANN Board, which was extended by one hour, ICANN
finally decided :
« Resolved
(2020.02.19.01), by virtue of the public health emergency of international
concern posed by COVID-19, the daily evolving developments, and the high global
risk still identified, the Board directs the ICANN President and CEO, or his
designees, to take all necessary actions to not hold ICANN67 as an in-person
meeting in Cancún, Mexico.
Resolved
(2020.02.19.02), as the Board has determined to not proceed to Cancun, Mexico
for ICANN67, the Board directs the ICANN President and CEO to move ICANN67 to
ICANN’s first fully remote public meeting. »
The ICANN Board
communiqué confirms that the summit, which is usually held in person, will for
the first time be entirely managed remotely with means still to be clarified.
If the
holding of such event in a remote mode is unprecedented, it should be noted
that in the past ICANN has already changed the organization of its meetings for
similar reasons. Indeed in June 2016, for example, ICANN decided to move
ICANN56 from Panama City to Helsinki in Finland because of the Zika virus. The
only difference is that their decision could have been anticipated earlier.
This is why
ICANN has already taken up the subject for the holding of the following events :
the GDD Summit planned in Paris in May and then the ICANN68 planned in Kuala
Lumpur in Malaysia in June.
The.TWregistry (TWNIC) offers grandfathering registrations for holders of existing ASCII.TW domains that wish to register the same ASCII domain under .台灣 (.xn--kpry57d).
Before the official opening, TWNIC provides
priority registration for registrants who meet the eligibility requirements.
For example, twnic.tw can be registered for
twnic.台灣 in the
grandfathering period.
The following eligibility criteria apply and
are checked by the registry:
The creation date for ACSII.tw should be earlier than the same ASCII name under .台灣 (.xn--kpry57d)
The registrant of ASCII.台灣 (.xn--kpry57d) should be the same as ASCII.tw
ASCII.tw and ASCII.台灣 (.xn--kpry57d) should be managed under the same registrar when creating ASCII.台灣.
Grandfathering Period : from January 7th, 2020 to February 10th, 2020.
The ASCII.tw Domain Name “.台灣(.xn--kpry57d)” will be starting on February 18, 2020.
For more information on the conditions for registration of your .台灣, don’t hesitate to contact us.
*An
internationalized domain name (IDN) is an Internet domain name that contains at
least one language-specific script or alphabet, such as Arabic, Chinese,
Cyrillic, Devanagari, Hebrew. It allows
the use of domain names in the native language of Internet users using special
characters such as Asian, Arab or African users.
Nameshield uses cookies
Nameshield wishes to use cookies to ensure the proper functioning of the site and, with our partners, to measure its audience🍪.
Nameshield wishes to use cookies to ensure the proper performance of the website and, with our partners, to monitor its audience. More information in our Cookie Policy 🍪.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gat_gtag_UA_25904574_14
1 minute
Set by Google to distinguish users.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
NID
6 months
NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.