security.cs.berkeley.edu
The Security Group in the EECS Department at UC Berkeley
At a glance
- Category
- Security & Privacy
- Language
- English
- Paid-content signal
- No paid content foundObserved
- Registered
- Unknown
- Hosting
- berkeley.eduInferred
- HTTPS certificate trusted
- PassedObserved
- Last updated
Related questions
More questions →What is Security Research at UC Berkeley?
security.cs.berkeley.edu is the website of the Security Group in the EECS Department at UC Berkeley. It is an informational research hub, not a product or service: the site introduces the group's research areas, lists its faculty, affiliates, postdocs, staff, graduate students, and alumni, and points visitors to further pages for research details. It is worth browsing if you want to understand who works on security at Berkeley, what topics they cover, or how to follow their work; it is not a place to sign up for a tool or buy anything.
What the group studies
According to the site, the Security Group studies a wide variety of topics, including:
- Cryptography
- Network security
- Usable security
- Secure machine learning
The page frames this as an overview rather than a complete list, and directs readers to individual faculty and student pages for deeper research information.
Who is on the site
The page organizes people into several groups, which tells you how the lab is structured:
| Group | Role on the page | Examples named |
|---|---|---|
| Faculty | Core research leads | Henry Corrigan-Gibbs, Natacha Crooks, Chris Fletcher, Anthony Joseph, Vern Paxson, Raluca Ada Popa, Dawn Song, David Wagner |
| Affiliates | Associated researchers | Serge Egelman, Nicholas Weaver |
| Postdocs & staff | Research and support roles | Alisa Frik, Zhanhao Hu, Yiping Ma, Mona Wang, Primal Wijesekera |
| Graduate students | Current PhD researchers | Noura Alomar, Boru Chen, Sizhe Chen, Vivek Nair, Julien Piet, Chawin Sitawarin, and others |
| Alumni | Former members | A long list including Nicholas Carlini, David Fifield, Ian Goldberg, Prateek Mittal, Adrian Perrig, and many more |
The alumni list is unusually long, which is a useful signal if you are trying to trace where security researchers in this community have gone.
What else the page covers
Beyond people, the site states that Berkeley security research spans multiple labs, centers, departments, colleges, and schools, and it links out to related groups. It also highlights that the group hosts events and teaches courses, and closes with an invitation to join. Those sections are pointers rather than detailed content, so expect to click through for schedules, course listings, or collaboration details.
How to use the site
If you want to learn more about the research, the page's own recommendation is to visit the linked faculty and student pages. A practical path:
- Start with the faculty list to identify whose work matches your interest (for example, cryptography vs. usable security).
- Follow individual names to their pages for publications and projects.
- Check the affiliates, postdocs, and students if you are looking for collaborators or current work rather than established leads.
- Use the alumni list if you are researching the group's history or tracking specific researchers.
What it is not
The page contains no pricing, sign-up, or access-restriction information, so nothing here should be read as offering a free or paid service. It is a research group's public-facing overview page, and its value is in the people and topic pointers it provides.
What Security Research Topics Does the Berkeley Security Group Cover?
The UC Berkeley Security Group, part of the EECS Department, studies a broad range of security topics. Its stated areas include cryptography, network security, usable security, and secure machine learning. If you want to know whether your interests match the group's work, the most reliable path is to check the individual faculty and student pages linked from the group's site, since those pages describe specific projects rather than just broad labels.
The four named research areas
The group's own description lists these directions:
- Cryptography — the design and analysis of cryptographic systems.
- Network security — security issues in networked and distributed systems.
- Usable security — how people interact with security tools and how to make security practical.
- Secure machine learning — security and privacy concerns in machine learning systems.
These four labels are the group's own summary, not an exhaustive list. The phrase "a wide variety of topics" signals that work extends beyond them.
Why the breadth matters
Security research at Berkeley is not confined to one lab or department. The group notes that its work "spans a number of labs, centers, departments, colleges, and schools." That means a single research question may involve cryptography, systems, human factors, or ML depending on the project. For a prospective student or collaborator, this cross-cutting structure is useful: you are not limited to one narrow subfield.
How to find more specific topics
The homepage itself does not enumerate every project. To go deeper:
- Open the faculty pages linked from the group site. Faculty listed include Henry Corrigan-Gibbs, Natacha Crooks, Chris Fletcher, Anthony Joseph, Vern Paxson, Raluca Ada Popa, Dawn Song, and David Wagner.
- Check the graduate student pages. Students listed include Noura Alomar, Sizhe Chen, Vivek Nair, Chawin Sitawarin, and many others.
- Look at affiliates and postdocs for adjacent work.
Each person's page typically describes their current projects, which is where the broad categories turn into concrete research questions.
Who should pay attention
- Prospective graduate students — the faculty and student listings show who works on what, which helps you decide whom to contact.
- Researchers and collaborators — the cross-lab structure indicates where interdisciplinary security work happens.
- Industry and practitioners — the named areas (cryptography, network security, usable security, secure ML) map to common applied problems.
What the page does not tell you
The site describes research areas and people, but it does not publish pricing, admission requirements, or course schedules on this page. For those details you would need the relevant department or program pages. Treat the homepage as a map of who and what, not as an application guide.
Does the Berkeley Security Group offer courses, events, or ways to join?
Yes. The Berkeley Security Group's site explicitly signals all three: it says the group hosts events, teaches courses, and invites people to join. The page itself is a directory-style overview rather than a schedule, so the practical path is to use its people lists and outbound links to find the specific course, event, or contact you need.
What the group says it offers
The site's own section headings are the clearest evidence of what it provides:
- "We host events!" — the group runs events, though the page does not list dates or formats.
- "We teach courses!" — teaching is presented as an ongoing activity of the group.
- "We'd love for you to join us!" — an explicit open invitation to join.
The page also states the group studies "a wide variety of topics, including cryptography, network security, usable security, and secure machine learning." That matters for choosing a course or event: the group's work is broad, so you should match your interest to a specific faculty member or lab rather than to "security" in general.
How to find the right course or event
The page does not publish a course catalog or event calendar. Instead, it points you to the people involved and says: "To learn more about our research, we encourage you to visit the pages of our faculty and students, linked below."
A workable approach:
- Pick your subarea. Decide whether you care about cryptography, network security, usable security, or secure machine learning.
- Find the matching faculty. The page lists faculty including Henry Corrigan-Gibbs, Natacha Crooks, Chris Fletcher, Anthony Joseph, Vern Paxson, Raluca Ada Popa, Dawn Song, and David Wagner. Faculty pages are the most likely place to find current course listings and reading groups.
- Check affiliates and postdocs for applied or adjacent work. Affiliates listed include Serge Egelman and Nicholas Weaver; postdocs and staff include Alisa Frik, Zhanhao Hu, Yiping Ma, Mona Wang, and Primal Wijesekera.
- Look at the broader network. The page notes that "Security research at Berkeley spans a number of labs, centers, departments, colleges, and schools," and links out to related groups — so a course or event may sit outside the core group page.
Who this is for
| If you are… | What the page supports | What you still need to do |
|---|---|---|
| A prospective grad student | The group lists current grad students and says it welcomes joiners | Check faculty pages for admissions and research-fit guidance |
| A current Berkeley student | Courses and events are stated as group activities | Find the specific course number or event listing via faculty pages |
| An external researcher | The group names collaborators and affiliated labs | Use the linked lab and center pages to find seminars or joint events |
| Someone exploring the field | Topic areas are named (crypto, network, usable security, secure ML) | Read individual faculty and student pages for depth |
Practical caveats
- The page is a people-and-links hub, not a schedule. Treat any specific course title, term, or event date as something you must confirm on the linked page.
- The "join us" invitation is a general statement. It does not describe an application process, eligibility, or timeline — those details are not on this page.
- Because the group spans multiple departments and schools, the most reliable first step is to identify one person whose work matches your interest and follow their page outward.
If your goal is to take a course, attend an event, or join the group, start from the faculty and student lists on this page and work outward to their individual sites.
How to Find People and Collaborators in the Berkeley Security Group
The Berkeley Security Group's website (security.cs.berkeley.edu) organizes its people into clearly labeled categories on a single page, so you can locate a specific person or scan the team by role. The page lists faculty, affiliates, postdocs and staff, graduate students, and alumni, and it states that individual pages are linked from each name. It also notes that security research at Berkeley spans multiple labs, centers, departments, colleges, and schools, so collaborators may sit outside the core group.
What the page gives you
The page is a directory rather than a searchable database. Its value is the role-based grouping and the outbound links to individual pages.
| Category | What it tells you | Best use |
|---|---|---|
| Faculty | Core research leads | Finding an advisor or principal investigator |
| Affiliates | Associated researchers | Identifying collaborators outside the core faculty |
| Postdocs & staff | Early-career researchers and support | Reaching people closer to day-to-day project work |
| Graduate students | Current student researchers | Understanding active projects and student interests |
| Alumni | Former members | Tracing research lineage or past collaborations |
The page's own framing is informal — headings such as "We've got great people!" and "We have lots of friends!" — but the underlying structure is a standard academic roster.
Steps to find a person or collaborator
- Open the group's main page and scan the category headings.
- Identify the role that matches your goal: faculty for advising or high-level collaboration, students or postdocs for project-level contact, affiliates for cross-institution connections.
- Click the linked name to reach that person's individual page. The group states it encourages visitors to visit faculty and student pages for more on their research.
- If your interest is topical rather than personal, use the "friends" section, which points to related labs, centers, departments, colleges, and schools.
Expected result: you land on an individual or related-group page with that person's or group's own research description, rather than staying on the roster.
Choosing the right category for your goal
- Seeking a PhD advisor or faculty collaborator: start with the faculty list. These are the people who lead research directions.
- Looking for a co-author or someone to discuss a specific project: postdocs, staff, and graduate students are closer to active work.
- Tracing a research area's history or a former connection: the alumni list is the relevant section.
- Looking beyond the core group: the affiliates and the related labs/centers section cover people and units outside the immediate roster.
Common sticking points
- The page is a static roster, not a search tool. There is no filter by topic, so you match people to interests by opening their individual pages.
- Role labels are broad. "Affiliates" and "friends" do not specify the exact nature of each relationship, so the linked page is where you confirm the connection.
- The page does not list contact details directly; those live on individual pages.
- Because research spans multiple departments and schools, a collaborator you want may not appear on this roster at all — check the related-labs links.
What to do next
Pick the category that matches your intent, open the linked individual pages, and use the related-labs section when your target sits outside the core group. If you are deciding whom to contact, the faculty list is the starting point for research direction, while students and postdocs are the better entry point for ongoing project work.
Website Overview
Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.
Domain and Registration
Unknown
DNS and Email
Nameservers are provided by berkeley.edu, indicating managed DNS hosting. MX records point to the Google Workspace email service. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google, Apple, Atlassian, Microsoft. Such markers may also remain after a service stops being used. The lowest observed DNS TTL is 271 seconds.
TLS and Certificates
The certificate includes the organization field University of California, Berkeley. The certificate issuer is Sectigo Limited, a commercial certificate authority. The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. The certificate is valid for about 100 days in total, with 69 days remaining.
HTTP and Browser Security
The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header identifies Apache without an exact version. No explicit CDN or WAF marker was found in the response headers.
Technology Stack Analysis
The public page identifies Next.js, Bootstrap, Apache without precise versions, leaving fewer clues for version-specific scanning.
Search and Social Sharing
No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 55 characters, within a common display range. A meta description is present, with 56 characters. The observed directives allow indexing and link following.
Hosting and Email
Registration details
Unknown
DNS records
| Type | Name | Value | TTL | Priority |
|---|---|---|---|---|
| A | eecs-haproxy-vip.eecs.berkeley.edu | 128.32.139.28 | 300 | — |
| MX | berkeley.edu | aspmx.l.google.com | 271 | 1 |
| MX | berkeley.edu | alt1.aspmx.l.google.com | 271 | 5 |
| MX | berkeley.edu | alt2.aspmx.l.google.com | 271 | 5 |
| MX | berkeley.edu | alt3.aspmx.l.google.com | 271 | 10 |
| MX | berkeley.edu | alt4.aspmx.l.google.com | 271 | 10 |
| NS | berkeley.edu | adns1.berkeley.edu | 10800 | — |
| NS | berkeley.edu | adns2.berkeley.edu | 10800 | — |
| NS | berkeley.edu | adns3.berkeley.edu | 10800 | — |
| TXT | berkeley.edu | 896263912-18360412 | 3600 | — |
| TXT | berkeley.edu | MS=10BE0CF63C8BD5AFF9A6EF7B71763B098A905719 | 3600 | — |
| TXT | berkeley.edu | MS=ms19521665 | 3600 | — |
| TXT | berkeley.edu | MS=ms37758698 | 3600 | — |
| TXT | berkeley.edu | ZOOM_verify_RirbP7N1QWC3Zzm02oL4Cw | 3600 | — |
| TXT | berkeley.edu | adobe-idp-site-verification=a113c870-3c49-4b4a-b3a4-31e1cf1860cb | 3600 | — |
| TXT | berkeley.edu | amazonses:IuakF7FVH1Y7h0Kap7krqHwRvoXFOzSET+Ri1VBHziA= | 3600 | — |
| TXT | berkeley.edu | apple-domain-verification=ZDtApcKYPmKfYxn4 | 3600 | — |
| TXT | berkeley.edu | atlassian-domain-verification=RIwGoMGAwFoHKm3AJg0bhFvuzEkRseqI6LStzthTqt4dWfA6Mqm5OCHFbZd1BJ9e | 3600 | — |
| TXT | berkeley.edu | brevo-code:a2b2aef0282cf9caec92be7bed7630ad | 3600 | — |
| TXT | berkeley.edu | brevo-code:c6f4c03d44819f8975dc05ff6b3df3a9 | 3600 | — |
| TXT | berkeley.edu | brevo-code:e1e8345a4a2352cdbd9d6979093f2aec | 3600 | — |
| TXT | berkeley.edu | brevo-code:ee0b01818d57850991280d3999efc841 | 3600 | — |
| TXT | berkeley.edu | canva-site-verification=HJ933woS6KmNfYtvOaJHZA | 3600 | — |
| TXT | berkeley.edu | docusign=25bb9bc1-b377-48ce-a907-61472fca6261 | 3600 | — |
| TXT | berkeley.edu | docusign=31f4475e-737f-4a3a-b6ea-60b1ac273c95 | 3600 | — |
| TXT | berkeley.edu | google-site-verification=C4YkQW0t-gtD5FpVWdjxAipEUofVb2p0KmW3xFaUJeA | 3600 | — |
| TXT | berkeley.edu | google-site-verification=CDuttEoV44OF0dD7qwidnTj3wvYxIPz05W6MKEZfKYc | 3600 | — |
| TXT | berkeley.edu | google-site-verification=R5hbazPMfJqtXtm6OHprlDpBnSThQvYDrt-i-IqZvjE | 3600 | — |
| TXT | berkeley.edu | google-site-verification=fL93jj-VPnl_5wdFDh26YshzKVPraWAurHaBCu-k-Xw | 3600 | — |
| TXT | berkeley.edu | google-site-verification=loQrJWyMsMB249uINb-AsRGTWVoLdTc44Td3aMGn-NE | 3600 | — |
| TXT | berkeley.edu | iContact1393487 | 3600 | — |
| TXT | berkeley.edu | iContact1462072 | 3600 | — |
| TXT | berkeley.edu | iContact1583632 | 3600 | — |
| TXT | berkeley.edu | jamf-site-verification=2jicltwxCxH93ep4OhO0dA | 3600 | — |
| TXT | berkeley.edu | klaviyo-site-verification=SWYLuM | 3600 | — |
| TXT | berkeley.edu | sending_domain102272=da1fdb1bce80fcb235c498ec3ad47745fed6ea7c6dc03752d88318531e6b07b7 | 3600 | — |
| TXT | berkeley.edu | v=spf1 include:_spf.berkeley.edu include:_spf2.berkeley.edu include:_spf.google.com include:_spf.qualtrics.com include:servers.mcsv.net include:spf.mailjet.com a:c.spf.service-now.com ~all | 3600 | — |
| CNAME | security.cs.berkeley.edu | eecs-haproxy-vip.EECS.berkeley.edu | 7200 | — |
| DS | berkeley.edu | 10359 10 2 90c805bdf785312d7ce4af92d697cdb1e6f5228d7364dce259d0652b8579c65b | 86400 | — |
| DS | berkeley.edu | 17532 10 2 a6c9ec2b5ac641f87b436d2ff9adb8d5655bc8434de90cc47ed47f8bad65ae1f | 86400 | — |
| DMARC | _dmarc.berkeley.edu | v=DMARC1; p=reject; np=reject; psd=n; rua=mailto:[email protected]; ruf=mailto:[email protected] | 2348 | — |
TLS and certificates
HTTP response headers
| Header | Value |
|---|---|
| content-type | text/html |
| server | Apache |
Identified technologies
Pages, Search and Sharing
| Meta description | The Security Group in the EECS Department at UC Berkeley |
|---|---|
| Canonical URL | Not detected |
| Language | English (default) |
| Twitter Card | Not detected |
Unknown
robots.txt (opens in a new tab)
1 rulesAll bots 0 allowed · 1 disallowed
- Disallow
secrets.txt
No matching rules.
Sitemaps
0No sitemaps found
Recent Updates
- Website images
- Screenshots
- Network details
- Website Technologies
- Pages and Search Information
- HTTP Response Information
- TLS and certificates
- DNS Information
- Website profile
- Website Description
- Website Name
- Website profile
- Website Description
- Website Name
User reviews (0)