Who's reading?

Choose a view to put what you are looking for first. The page and the menu re-prioritise around it, and a margin note always says why.

Who's reading?
Research

Research project / In preparation

Web security of Sri Lankan state universities

Lead researcher

Status
In preparation
Role
Lead researcher
Years
2026
Themes
Web security, Human factors in security

Summary

University websites carry admissions notices, exam results and research, yet no one had checked how secure or how fast the websites of Sri Lanka's state universities are. This study measures all 17, using only the checks any visitor's browser could make, and recommends a simple security baseline for the whole sector.

A census-based, cross-sectional passive measurement study of the main websites of all 17 state universities under the University Grants Commission (.ac.lk). It assesses TLS configuration, HTTP security headers, email authentication (SPF, DMARC, DNSSEC), CMS and server software currency, potential exposure to known CVEs (NVD CPE matching), and mobile and desktop performance (Lighthouse and Chrome UX Report), with a review of publicly reported incidents and Spearman correlation between security and performance. Non-intrusive methods only, in line with the Computer Crime Act No. 24 of 2007. Submitted to ICARC 2027; results will be shared here after publication and after the universities and Sri Lanka CERT have been informed.

Why it matters

Students use university websites to apply, read examination notices and reach portals. When a site is compromised or slow, those services suffer, and students and staff can be exposed to phishing or malware. Sri Lankan public-sector websites have been attacked repeatedly in recent years, but no published study had measured the security and speed of the sector’s own websites.

Questions

  1. How well do the websites implement HTTPS/TLS, HTTP security headers and email authentication?
  2. Which content management systems and server software do they use, and how current are they?
  3. How much potential exposure to known vulnerabilities do the visible versions carry?
  4. How do the sites perform, and which incidents affecting them have been publicly reported?

Method

A census of all 17 universities, measured on one day with public, non-intrusive tools (Qualys SSL Labs, Mozilla HTTP Observatory, DNS over HTTPS, the NIST National Vulnerability Database and PageSpeed Insights), with key results cross-checked using curl, sslscan and WPScan in passive mode. No port scanning, exploitation, brute forcing or authenticated testing was carried out, and no personal or non-public data was accessed.

Responsible disclosure

Critical findings are reported privately to the affected universities and to Sri Lanka CERT before publication. Results and recommendations will appear here once the paper is published.

Back to top

Keyboard shortcuts

⌘ K / Ctrl K
Search the site and run commands
`
Open the terminal
?
Show these shortcuts
Esc
Close any panel or menu
Tab / Shift Tab
Move between links and buttons

Terminal

Type help to see what you can do here. Press Escape or type exit to close.