Governments, Cyberattacks, and Cybersecurity: Is This a 007 film?
#Soul tech
06.06.2023 Reading time: 6 minutes
Estíbaliz Bartolome Fernández
Ilustration: Saioa Ispizua
GovTech is the buzzword that describes the urgent need to modernize and digitize the government and, of course, the benefits that this will bring to society.
Despite the fact that the opportunities offered by information technology and the globalization of telecommunications are unquestionable, experts in cybersecurity are quick to remind us that these possibilities also open up a range of opportunities for cyberespionage, sabotage, extortion, and violations of rights, among other things. Although this may sound like a science fiction film, it has, unfortunately, been a reality for years.
Paralyzing a country’s systems for energy distribution, transport, or health, or any other critical pieces of infrastructure by technological means, is becoming more feasible due to the connectivity of systems that until now had remained isolated. In the society we knew up until now, sabotaging a critical piece infrastructure was up to spies like James Bond, but today all this is possible at the click of a mouse.
In fact, this is not something new… there are several historic battles that we computer scientists like to blabber on about at Christmas dinners that illustrate this situation quite well.
THE STORY OF ESTONIA
We can go back to 2007 and travel to Estonia, a leading country in terms of governmental digitalization. As I already warned you at the beginning of this article, not everything that glitters is gold: due to the country’s great digital dependency, that year Estonia fell victim to several sustained Denial of Service attacks, for weeks, in which networks of computer bots sent massive amounts of messages and online requests to saturate the servers of various official bodies, financial entities, and commercial sites.
This prevented Estonian citizens from leading normal lives and carrying out daily activities such as accessing their bank accounts online and making online purchases. In the case of the Financial sector, the attack went even further: Estonian banks, fearing that their systems could be compromised, and following the principle of prudence, decided to put a hold on their services. That was when the team leading the attack decided to impersonate these organizations in order to attack other international entities, causing the international financial community to isolate Estonia’s banking network.
THE STORY OF NATANZ
Another of our favorite films is one called Blackhat, which features code from a 2010 virus known as Stuxnet that attacked an Iranian nuclear power plant in Natanz (that’s right, the attackers were thinking big). And yes, we’re talking about the year 2010… because, as I said, this is nothing new.
To give you a bit of context, in the 1980s Iran managed to get hold of designs stolen from Europe for centrifuges used in the uranium enrichment process. The complexity of the systems meant that they couldn’t be fully replicated by Iran. The Iranians had to establish procedures to work with what they had, and their versions often failed. These processes were complex and, basically, they had to stop phases of the production process in order to release some of the pressure generated using valves that they themselves had designed. These valves became the point of attack for Stuxnet.
The pressure valves were monitored with PLCs, and Stuxnet infiltrated the system by posing as a PLC configuration file. In this first version, the virus wasn’t able to spread, and acted discreetly:
- It let production take its course naturally.
- It would isolate the stages of the centrifuges so that the pressure would rise, and it would de-calibrate the sensors so that the pressure release valves wouldn’t work.
- It provided the control system with readings that it reproduced in a loop. In this way, to the engineering team, the system’s performance seemed normal.
- It decided when to stop the attack.
This was due to the fact that the aim was not to destroy the plant (which would have caused an investigation into the problem and brought about a solution to it), but rather to go unnoticed, causing many more problems in the rotors, generating system shutdowns and keeping the engineering team busy during all these system faults, thereby delaying the nuclear program.
The second version of Stuxnet, on the other hand, did spread by infecting USB drives so that it could travel between computers and eventually reach its final target: the high-speed PLCs for the centrifuge rotors, a weak point in the system.
Once a month Stuxnet would take control of the rotors and significantly reduce their speed, only to immediately speed them back up again, forcing the systems through critical speeds that would reduce their service life.
That is how the virus managed to slow down the nuclear power plant’s production – and James Bond didn’t even have to travel to Natanz.
THE STORY OF PARIS
But, it really isn’t necessary to go as far as Iran. During the 2011 presidential elections in France, our neighboring country, a cyberattack was carried out against the Elysée Palace’s systems using a simple method: phishing.
The victims received a false invitation to resources on the Palace’s local network by email. The attackers had secured the addresses by adding Facebook to their targets, and the link received by email led to a fake website requesting the victim’s username and password. After login credentials were stolen using this method, the attackers introduced a spy virus on the targeted computers, which then spread and infected other machines on the French presidential network.
Noteworthy capabilities of the virus included taking screenshots, copying files, and recording audio. Thus, the attackers managed to put a microphone in each and every office.
The computers affected included those of advisers to then-President Nicolas Sarkozy, from whom secret notes and strategic plans belonging to the French government were obtained.
Simple, cheap, effective, and without any risk. Bond may as well retire.
THE STORY OF THE USA
But, what about the plot to manipulate and propagate fake news through Facebook to influence American public opinion and the vote in the 2016 presidential election?
The scheme consisted of the massive creation of fake Facebook profiles (designed to appear to be of American origin, but instead managed from foreign countries) through which the attackers published fake news and controversial content.
With 2.9 billion active accounts around the world (175 million in the USA), Facebook’s power is enormous. False and misleading posts – often designed to be sensationalist and provocative – reach a massive audience in a matter of seconds, generating an information bubble that reinforces the beliefs and attitudes of those who consume them, thus increasing social polarization and misinformation. In this case, it was also possible to demonstrate the use of paid advertising to maximize diffusion and reach specific audiences that were of interest for the election.
WHO STARTED THE WAR?
Well, who knows? The attribution of these attacks to governments or specific interest groups is usually done by deducing who might be most interested in attacking, in terms of political strategy.
Many speculated that, in the case of Estonia, the attacks originated from Russia, and that Estonian security forces managed to identify the people involved, although the Russian government denied any involvement in the events, and refused to bring those people to justice. In the case of Stuxnet, despite the fact that it hasn’t been proven, all eyes are on the United States and Israel. In the case of the US elections, an intelligence report concluded that it was Russia that tried to influence the elections in favor of Trump.
But, as I said, there is no undeniable proof that it was the armies of these countries that started or carried out these attacks, of a type often carried out as false flag operations.
But, as I said, there is no undeniable proof that it was the armies of these countries that started or carried out these attacks, of a type often carried out as false flag operations.
So, as we have seen, locking up an entire country, attacking critical energy infrastructures, government espionage, manipulating public opinion, and interfering in presidential elections are just some of the examples of what can be done by computer. No biggie!
Although there is nothing we like more than a good classic, this article could fill pages and pages with other similar and more recent attacks. Unfortunately, we have more than enough material for a Netflix series.
But, if you don’t mind, we’ll leave that for the next season.
Labels
- #cultura
- #quantum
- #computación
- #estrategia
- #futuro
- #tecnólogas
- #govtech
Take our advice and check it out
Slide to show more
Cookies
We use proprietary and third-party cookies for technical, analytical and customisation purposes, such as choosing the language in which to display the website. For more information, please consult our cookies policy (Opens modal window).
Cookies policy
The website at https://www.bizkaia.eus (hereinafter, the Website) uses tools to track browsing activity on the website and the IP address of the service recipient for the purpose of improving and guaranteeing the provision of services or technical operation of the website, distinguishing you from other users and analysing your browsing habits.
This Cookies Policy seeks to inform you clearly and precisely about the operation and function of the cookies we use.
What are cookies and why do we use them?
A cookie is a file that is downloaded to your computer when accessing certain websites.
Cookies enable a website to, among other things, store and recover information about the browsing habits of a user or their device and, depending on the information contained and the way in which the same is used by the device, may be used to recognise the user.
Current law allows us to store cookies on your device if they are strictly necessary for operation of this website. However, we need permission for all other cookies.
Types of cookies based on the managing entity
Depending on who manages the computer or domain from where the cookies are sent and who processes the data obtained, a distinction can be made between the following types of cookies:
- Proprietary cookies: these are managed by the Provincial Council of Biscay.
-
Third-party cookies: these are managed by another entity, which processes the data obtained via the cookies.
This website may contain cookies belonging to the Basque Government, used for its own purposes and stored by domains other than those owned by the Bizkaia Provincial Council.
Types of cookies based on their purpose
- Technical cookies: these allow the user to browse a website, platform or application and to use the various options or services available, such as control data traffic and communication, identify the session, access restricted areas, request registration or participation in an event, use security elements while browsing, store content for video or audio playback, or share content via social media networks.
- Customisation cookies: these allow the user to access the service with some general characteristics predefined according to a series of criteria on the user’s device, such as the language, type of browser being used to access the service, regional configuration from where the service is accessed, etc.
- Analysis cookies: these allow the number of users to be counted and the browsing activity to be statistically measured and analysed for the purpose of improving the services made available. They may be proprietary or third-party cookies.
Duration of the cookies
- Session cookies: these collect and store data while the user is visiting a website.
- Persistent cookies: the data are stored on the device in an ongoing fashion and may be accessed and processed during a period defined by the cookie manager, which may range from a few minutes to several years.
Which cookies does this website use?
In each row you can find data relating to Technical cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| JSESSIONID | Session identifier | Session | Bizkaia Provincial Council |
| ASPSESSIONID | Session identifier | Session | Bizkaia Provincial Council |
| TS01 | Session identifier | Session | Bizkaia Provincial Council |
| LFR_SESSION_STATE | Session identifier | Session | Bizkaia Provincial Council |
| COOKIE_SUPPORT | Indicate whether the user has the cookie support activated | 1 year | Bizkaia Provincial Council |
| pc_tecnicas_bizkaia | Choose your preferences for acceptance of the block of technical cookies | 1 year | Bizkaia Provincial Council |
| pc_analitica_bizkaia | Choose your preferences for acceptance of the block of analytical cookies | 1 year | Bizkaia Provincial Council |
| pc_preferencias_bizkaia | Choose your preferences for acceptance/rejection of the block of preferential cookies | 1 year | Bizkaia Provincial Council |
| pc_terceros_bizkaia | Choose your preferences for acceptance/rejection of the block of third-party cookies | 1 year | Bizkaia Provincial Council |
| Kultursistema_session | Keeping the user’s session | 1 year | Kultursistema |
| CPLB | Contains information used by our load-balancing servers | Session | Provincial Council of Biscay |
| XSRF-TOKEN | To prevent CSRF (Cross-Site Request Forgery) attacks | 1 year | Kultursistema |
| _GRECAPTCHA | Protects the website from spam and brute-force attacks | 5 months |
In each row you can find data relating to Analysis cookies
| Name | Purpose | Duration | Owner | |
|---|---|---|---|---|
| dtCookie | Track a visit through multiple requests | Session | Bizkaia Provincial Council | |
| dtLatC | Measure the latency of the server to monitor performance | Session | Bizkaia Provincial Council | |
| dtPC | Necessary to identify the appropriate parameters for beacon transmission; includes session ID for correlation | Session | Bizkaia Provincial Council | |
| dtSa | Intermediate storage for actions spanning pages | Session | Bizkaia Provincial Council | |
| rxVisitor | Visitor ID to correlate sessions | Constantly | Bizkaia Provincial Council | |
| rxvt | Session waiting time | Session | Bizkaia Provincial Council | |
| iyrc-user-id | Distinguish users | 1 year | Bizkaia Provincial Council | |
| _ga, _ga_XXXXXXXXXXX | Analysis | To distinguish users | 2 years | Google Analytics |
| _gat, _gat_XXXXXXXXXXX | Analysis | To limit the percentage of requests | 1 minute | Google Analytics |
| _gid | Analysis | To distinguish users | 1 day | Google Analytics |
In each row you can find data relating to Personalisation cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| Idioma | Select the language preferred by the user | 1 year | Bizkaia Provincial Council |
| cookie-tramites-favs | Save favourite procedures in Prior Appointment | 1 year | Bizkaia Provincial Council |
In each row you can find data relating to Third-party cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| CLID | Identify a user’s first visit | 1 year | Microsoft Clarity |
| APISID | Store user preferences and information during page views with Google maps in them. | 2 years | |
| HSID | Store user preferences and information during page views with Google maps in them. | 2 years | |
| MUID | Store user preferences and information during page views with Google maps in them. | 1 year | Microsoft Clarity |
| NID | Remember their preferences and other information | 6 months | |
| SAPISID | Show personalised advertisements on Google sites | 2 years | |
| SID | Provide advertisement delivery or retargeting, provide fraud prevention. | 2 years | |
| SIDCC | Provide reliable web traffic identification. | 1 year | |
| SM | Used to synchronise the MUID between Microsoft domains. | Session | Microsoft Clarity |
| SSID | Provide advertisement delivery or retargeting, provide fraud prevention. | 2 years | |
| __Secure-1PAPISID | Create a website visitor interest profile to show relevant and personalised Google advertising. | 2 years | |
| __Secure-1PSID | Create a website visitor interest profile to show relevant and personalised Google advertising. | 2 years | |
| __Secure-1PSIDCC | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-1PSIDTS | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-3PSID | 2 years | ||
| __Secure-3PSIDCC | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-3PSIDTS | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-ENID | Necessary cookies to use website services and options | 1 year | |
| ar_debug | Refine advertisements. | 1 año | |
| MR | Indicate when MUID is refreshed | 6 months | Microsoft Clarity |
| XSRF-TOKEN | Indicate when MUID is refreshed | 1 hour | Kultursistema |
| _fbp | Store and track website visits | 1 year | |
| kultursistema_session | Keep the user’s session | 1 hour | Kultursistema |
| AEC | Detect spam, fraud, and abuse | 6 months | |
| SOCS | Store user cookies preferences | 13 months | |
| Locale | not available | Basque government | |
| _hegoa_coop_session | Create a session ID for users | Session | Basque government |
How to deactivate or delete cookies?
When first accessing the Website, the user may configure and accept or reject the cookies on this Website. Subsequently, the user may change or withdraw their consent at any time via this Cookies Policy or the settings page.
However, you may exercise your right to freely deactivate them and even delete the cookies on this Website at any time. This is done differently depending on which browser you are using. Here is a quick guide for the most popular browsers.
- Deactivate Cookies in Chrome
- Deactivate Cookies in Explorer
- Deactivate Cookies in Firefox
- Deactivate Cookies in Safari
- Deactivate Cookies in Edge
If you deactivate or delete cookies, certain features of the Website may no longer function correctly.
Changes to the Cookies Policy
The Website reserves the right to change this Cookies Policy under the terms provided for by current legislation. We therefore recommend that you revise this policy each time you access our website to see any changes and read the pertinent information.
Configure cookies
We show you hereinbelow the different categories of cookies that our web page uses. You can personalise your choice by accepting or rejecting these categories through the buttons enabled to that end. For more information, consult our cookies policy (Opens modal window).
-
Technical Always active
These are needed to allow browsing on our website and for basic tasks related to correct website operation.
