- Reading time: 4 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 924 words
- File format: Text
Why do you want to study this course or subject?
Last winter my college IT service sent round a warning about phishing emails pretending to be from the exams office. Several people I knew clicked the link. What interested me was not that they were careless, but that the messages had been written well enough to survive a quick glance: correct logo, plausible deadline, a sender address that differed by one character. It struck me that security failures are rarely purely technical, and that as text generation tools get cheaper, convincing messages can be produced at scale by people with very little skill. That is the overlap I want to study: systems that use machine learning to find patterns in traffic and behaviour, and attackers who can now use similar tools themselves. I like that the field refuses to let me stay inside one subject. Detecting unusual login behaviour is a statistics problem; deciding what counts as unusual enough to lock someone out is a judgement about people and inconvenience. My Psychology A level has been unexpectedly useful here, particularly work on heuristics and how people assess risk under time pressure, which makes the success of a rushed phishing email much less surprising. I am also aware that machine learning introduces its own weaknesses. A classifier trained on last year's malicious traffic will not necessarily recognise this year's, and a model that can be queried repeatedly can be probed until its boundaries are known. A degree combining cybersecurity and artificial intelligence appeals because it treats those problems as connected rather than as separate modules, and because it should give me the mathematical grounding to test claims about detection accuracy instead of accepting them.
How have your qualifications and studies helped you to prepare?
I am studying Computer Science, Maths and Psychology at sixth form college. Computer Science has given me most of my practical grounding: I work in Python and have written my coursework project in it, and I have covered network protocols, the TCP/IP stack, hashing and public key encryption. Understanding how a hash function is used to store passwords, and why salting matters, was the first time a security idea felt properly concrete rather than something I had read about. Maths supports this more than I expected when I chose it. Working through binomial and normal distributions in the statistics units has made me cautious about how detection systems are described, because a test that sounds accurate can still generate a large number of false alarms when the thing it looks for is rare. I have also found the discrete work on modular arithmetic useful background for reading about RSA, even though we only touched the surface. Psychology contributes the human side: research methods has taught me about sampling, confounding variables and the difference between a correlation and a cause, all of which apply when someone claims a security tool reduced incidents. Outside lessons I attend our college coding club, where I have helped run two sessions for first-year students on version control and on writing readable functions, which forced me to be much clearer about ideas I thought I understood. I read around the subject in ordinary ways, mainly technical blogs, the National Cyber Security Centre's guidance pages and Michael Kearns and Aaron Roth's The Ethical Algorithm, which I found useful on the idea that fairness and privacy have to be built into a system deliberately rather than added afterwards.
What else have you done to prepare outside of education, and why are these experiences useful?
My independent project is a modest one: I set up an old laptop as a small server at home, ran a firewall on it and wrote Python scripts to parse the log files and count failed SSH login attempts by source address and hour. Over a few weeks I built up enough data to see a clear pattern of automated attempts against common usernames. I then tried a very simple threshold rule to flag suspicious addresses, and quickly discovered how easy it is to block yourself out of your own machine after mistyping a password three times. Working out sensible thresholds, and recording what the rule got wrong, taught me more about false positives than any exercise I have been set. I also disabled password login in favour of keys, which felt like a genuine improvement rather than a tidy exercise. I work Saturdays and some holidays on the shop floor of a supermarket, mainly on tills and self-service assistance. It has taught me patience and how to explain a process to someone who is annoyed and in a hurry, which I think matters in security work where the usual complaint is that the safe option is the slow one. I have watched customers read out card details aloud and hand phones to strangers to help with an app, and it has made me sceptical of advice that assumes everyone has time and confidence. At home I look after our family computers, which mostly means updates, backups and persuading relatives that a password manager is worth the initial nuisance. Away from computing I play in a local badminton league on Thursday evenings, which keeps me organised around shifts and coursework deadlines. I would come to this degree without professional experience, but with the habit of testing my own assumptions and writing down what happened.
This example has 5,154 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.
Why this example works — strengths and ways to improve
This is a thoughtful, credible statement built on modest evidence that is used well: a phishing warning, statistics coursework and a home log-parsing project all lead to real insight about false positives and human behaviour. Its main problem is length. At 5,154 characters it exceeds the 4,000 limit, so you need disciplined selection rather than new material.
Subject motivation
security failures are rarely purely technical
You turn an ordinary phishing incident into a genuine question about the overlap of machine learning, attackers and human judgement. The point about locking someone out being a judgement about inconvenience shows you understand the field's tensions. It is not a generic passion claim. The closing sentence about modules could be trimmed.
Academic preparation
a test that sounds accurate can still generate a large number of false alarms
Each subject is linked to a specific security idea: salting, base rates and confounding. These connections are precise and appropriate for your stage, so you avoid simply listing topics. The reading list is honest, and The Ethical Algorithm earns its place because you say what you took from it.
Evidence and reflection
how easy it is to block yourself out of your own machine
This is the strongest reflection in the statement. A small failure becomes a lesson about thresholds and false positives, and it connects back to the statistics in answer two. The coding club teaching point also reflects well. The supermarket observations about card details are sharper than the generic phrase about patience.
Relevant experience
wrote Python scripts to parse the log files
The home server project is well chosen: accessible, concrete and directly relevant. The supermarket job is used thoughtfully. Family IT support and badminton add less. Badminton serves only a time-management claim, and dropping it would help you meet the character limit without losing evidence of preparation.
Credibility and voice
I would come to this degree without professional experience
Your tone is appropriately modest. Phrases like 'only touched the surface' and 'a modest one' make the claims believable. You never sound like a security professional, and your voice stays curious and measured throughout. Keep this honesty as you cut.
Structure and format
You give no length statement yourself, but the supplied total of 5,154 characters is well over the 4,000 UCAS limit. Each answer comfortably exceeds 350 characters, and the coding club material sits under qualifications when it is arguably extracurricular. You need to cut roughly 1,150 characters while staying above the library's 3,500 minimum.
What you’ve done well
- You link evidence across the answers without repeating it: false positives appear as a statistical idea in answer two and as a practical discovery in answer three.
- You use your Psychology A level convincingly to explain why rushed phishing succeeds, which avoids a forced cross-subject link.
How this draft could improve
- Cut to under 4,000 characters by removing lower-value material such as badminton, the patience claim, the family computers line and the final sentence of answer one.
- Tighten the reading sentence by dropping the vague reference to technical blogs and keeping the one book where you explain what you learned.
- Consider moving the coding club teaching to answer three, then shorten it, so answer two stays focused on qualifications and studies.