Secure Systems Group

Source for the Secure Systems Group (SSG) website.

This README covers editing content in the browser — no clone, no Node, no local build. If you maintain the website itself (layout, components, build, deploy), see CONTRIBUTING.md.

You need write access to this repository, which comes with membership of the ssg-research organisation. Ask a maintainer (see Contact) if GitHub says you cannot commit.

Edit a page

1. Click the Edit link for your page in the tables below.
2. Make the change. The Preview tab shows the rendered Markdown.
3. Click Commit changes…, choose Create a new branch and start a pull request, and commit.

A maintainer reviews the pull request and merges it. The site redeploys itself.

Pages

Page	Edit
About	about.md
MLSec	mlsec.md
PlatSec	platsec.md
Other	others.md
Dissemination	dissemination.md
Team	team.md
Maintainers	maintainer.md

Project pages

Project	Edit
Content Moderation for Generative Models	conceptfilter.md
Feature Locking for Language Models	featurelock.md
Unintended Interactions among ML Risks and Defenses	interactions.md
Machine Learning Property Attestations	mlattestation.md
Model Extraction Attacks and Defenses	modelExtDef.md
Blinded Memory	blime.md
Enhancing Memory-Safe Architectures	coloredcaps.md
Memory Allocation	memallo.md
Availability and Run-time Integrity Conflicts	pair.md
Probably Android	probandroid.md
FIAs	fias.md

Two pages are not hand-edited. The CS858 paper list body is generated by scripts/gen-papers-list.py, and the CS858 wiki lives in its own repository. Contact a maintainer for either.

Add a project page

1. Open template.md, copy its contents, and create a new file under src/content/projects/mlsec/, platsec/, or others/. In the GitHub editor, Add file → Create new file and typing the full path with slashes puts it in the right folder.
2. Set title (the page heading) and permalink (the live URL, e.g. /mlsec/yourproject), then delete the published: false line. A page that keeps that line is never built, which is useful while drafting.
3. Write the body in Markdown.
4. Link it from its section page — MLSec, PlatSec, or Other above — as [Your project](yourproject).

Conventions

Publications go on the project page they belong to, under ## Conference/journal paper publications, one bullet each:

- First Author, Second Author, N. Asokan: **Title of the Paper.** [Venue Year](https://example.org/paper). arXiv preprint [arXiv:0000.00000](https://arxiv.org/abs/0000.00000).

Link the venue to the publisher page or DOI, and the preprint to arXiv. Author names follow whatever form the paper itself uses.

Files — PDFs, posters, and slides go in public/assets/pdf/, referenced from a page as /assets/pdf/yourfile.pdf with a leading slash. Upload them through Add file → Upload files in the GitHub editor.

Links between pages use the permalink, e.g. [BliMe](/platsec/blime).

Section headings are ##. Each page opens with a single # matching its title.

What happens after you open a pull request

Two automated checks run and report on the pull request:

• ci builds the site and verifies that every internal link and asset reference resolves. This must pass before merging.
• links checks external URLs in the Markdown files you changed. It is advisory: publishers such as ACM and IEEE sometimes refuse automated requests, so read a failure here rather than trusting it blindly.

Contact

For anything else — a new section, styling or layout changes, removing a page, or a change you would rather not make yourself — contact Asim Waheed (Machine Learning), Adam Caulfield (Platform Security), or Michael (Other Topics), or open an issue.

License

Released under the MIT License.