Technical Report
Technical Report
Electronic Technology
Department of Communication
02/June/2023
i
Table of Contents
1.Introduction.........................................................................................1
2.Common Government Security Vulnerabilities................................3
2.1 The Usage of HTTP instead of HTTPS........................................3
2.2 Inactive Government sites not being disposed............................4
2.2.1 Risks of Inactive Governmental Sites....................................6
2.3 client-side authentication..............................................................6
2.3.1 vulnerabilities associated with client-side authentication....7
3. Solutions............................................................................................. 8
Reference:...............................................................................................9
ii
1.Introduction
Website security is crucial for governmental sites for several reasons.
Here are some of the reasons based on the search results:
2
2.Common Government Security
Vulnerabilities
[6]
The picture above is a governmental website that is used to publish
Results of Primary School Degree.
Where you can notice that there’s a lock saying that it’s insecure, that’s
because it uses HTTP instead of HTTPS, so why is it insecure and why
should governmental site avoid it, HTTP (Hyper Text Transfer Protocol)
and HTTPS (Hyper Text Transfer Protocol Secure) the only Difference
lays behind the s which means secure but how is it more secure.
3
1. Unencrypted HTTP connections create a privacy vulnerability and
expose potentially sensitive information about users of
unencrypted websites and services. Data sent over HTTP is
susceptible to interception, manipulation, and impersonation. The
people expect government websites to be secure and their
interactions with those websites to be private. [7]
[9]
4
[10]
Both of the picture above indicate that they are governmental website
used for the renewal process for a passport but which one is the real one
you my ask, well the answer is both one of them is an inactive site
without supervision, the picture below is of a website that scans domain
names and sees who’s the owner and if its active or not.
[11]
5
2.2.1 Risks of Inactive Governmental Sites
6
[12]
- Any attacker may read the source code and reverse-engineer the
authentication mechanism to access parts of the application which would
otherwise be protected.[13]
7
- Client-side authentication is extremely weak and may be breached
easily, which means that attackers can bypass the authentication check
by modifying the client code.[16]
3. Solutions
Here is a step-by-step guide on how to move a website from HTTP to
HTTPS:
1. Buy an SSL certificate: An SSL certificate is required to enable
HTTPS
on your website. You can buy an SSL certificate from a trusted
certificate authority or use a free SSL certificate provider like Let's
Encrypt.
2.Redirciting inactive website link to UpToDate website.
3.Having a banner telling incoming users that the site is inactive, and
they avoid interacting with it.
4. Redirect HTTP to HTTPS: You need to redirect all HTTP traffic to the
equivalent HTTPS page.
5. Migrating everything from the old into the new one, and shutting off
the old web server completely.
6. Governments should avoid using client-side authentication and
instead use server-side authentication to ensure the security of user data.
8
Reference:
[1] https://www.civicplus.com/blog/ce/the-importance-of-website-
security
[2] https://www.ifsight.com/insights/your-government-website-deserves-
expert-level-cybersecurity
[3] https://www.checkpoint.com/cyber-hub/cyber-security/what-is-
cybersecurity-for-governments/
[4] https://www.scarlettcybersecurity.com/why-is-cybersecurity-
important-to-the-government
[5] https://www.cisa.gov/news-events/news/website-security
[6] http://161.47.21.187/finalresults/
[7] https://https.cio.gov/
[8] https://parablu.com/what-is-port-443-and-why-it-is-imperative-to-
your-dr-plan/
[9] https://ejraat.gov.ly/procedure/48?l=ar
[10] https://lpa.gov.ly/
[11] https://who.is/whois/lpa.gov.ly
[12] https://tve.gov.ly/ar/STU/Index
[13] https://cwe.mitre.org/data/definitions/603.html
[14] https://www.strongdm.com/blog/authentication-vulnerabilities
[15] https://security.stackexchange.com/questions/213078/what-are-
client-side-exploits
[16] https://cwe.mitre.org/data/definitions/603.html
9
[17] https://security.stackexchange.com/questions/91762/what-are-the-
disadvantages-of-combining-client-side-and-server-side-authenticati
10