Security

Brit borough council apologizes for telling website users to disable HTTPS

Planning portal back online with a more secure connection


Reading Borough Council has securely restored its planning portal after facing criticism for recommending questionable tech security practices to users.

Before the fixed version went live this morning, the English local authority's online planning application portal had been offline due to "technical issues," an outage that had persisted for nearly a month.

Responding to a discussion related to the issue via a now-deleted post on X, the council's official account recommended users disable HTTPS in their browser as a way around the technical issues disrupting access to the planning portal.

Reading Borough Council's X post that instructed users to disable HTTPS

Until November 26, the same advice appeared in a yellow banner sprawled across the planning portal's homepage.

The council advised users to access the service using Chrome rather than Safari, since Safari does not allow users to turn off HTTPS, before listing the instructions on how to switch off the security feature.

Chrome has used HTTPS for its default navigation protocol since 2021, offering better load speeds for websites and protections from data interception or manipulation.

HTTPS builds on HTTP by using TLS encryption for requests and responses, meaning any sensitive data submitted to a website is encrypted rather than being sent in plaintext. An intercepted HTTP request, which lacks encryption, could provide cybercriminals with sensitive information like passwords, potentially leading to more severe attacks.

While the likelihood of users submitting sensitive information on a council's website for planning applications is low, if they forget to re-enable HTTPS afterward, they could remain vulnerable to online attacks.

More than anything else, Reading council was promoting embarrassingly bad security hygiene.

The council has since apologized for publishing this information, calling it "incorrect."

In the latest update on November 24, the council tweeted posted: "Apologies for the incorrect information that was tweeted."

The council sent a statement to The Register today: "The Council's Planning Portal is back online with a secure connection restored at 10:08 am on 27 November following the successful completion of remedial work.

"A planning portal website update was required as access from some internet browsers was being blocked.

"We apologize for the obvious inconvenience and confusion caused and the portal should now be fully operational with no special action on the part of users being necessary."

The local authority declined to provide an answer on how the original advice to disable HTTPS was approved internally.

The Register approached the National Cyber Security Centre (NCSC) but it did not respond. 

The official advice from GCHQ's cybersecurity arm to website operators is to always use HTTPS, even if the website is basic enough to not include private content, sign-in pages, or other sensitive information like credit card details.

UK public sector organizations, like Reading Borough Council, have access to the NCSC's Web Check service, which can audit a website and identify misconfigurations as well as whether HTTPS is in use or not. ®

Send us news
53 Comments

Watchdog claims retaliation from military after questioning cushy federal IT contracts

IT-AAC had a hand in scrutinizing JEDI, now faces probe for challenging $300M+ single-source deals

Five Eyes nations warn Moscow's mates at the Star Blizzard gang have new phishing targets

The Russians are coming! Err, they've already infiltrated UK, US inboxes

UK and US lead international efforts to raise AI security standards

17 countries agree to adopt vision for artificial intelligence security as fears mount over pace of development

Competing Section 702 surveillance bills on collision path for US House floor

End-of-year deadline looms on US surveillance

UK government denies China/Russia nuke plant hack claim

Report suggests Sellafield compromised since 2015, response seems worryingly ignorant of Stuxnet

Proposed US surveillance regime would enlist more businesses

Expanded service provider definition could force cafes and hotels to spy for the feds

Two years on, 1 in 4 apps still vulnerable to Log4Shell

Lack of awareness still blamed for patching apathy despite it being among most infamous bugs of all time

Belgian man charged with smuggling sanctioned military tech to Russia and China

Indictments allege plot to shift FPGAs, accelerometers, and spycams

A year on, CISA realizes debunked vuln actually a dud and removes it from must-patch list

Apparently no one thought to check if this D-Link router 'issue' was actually exploitable

Leader of pro-Russia DDoS crew Killnet 'unmasked' by Russian state media

Also: NXP China attack, Australia can't deliver on ransom payment ban (yet), and Justin Sun's very bad month

23andMe responds to breach with new suit-limiting user terms

Also: 'well-known Bay Area tech' firm's laptops stolen and check out some critical vulns

Polish train maker denies claims its software bricked rolling stock maintained by competitor

Says it was probably hacked, which isn't good news either