Three Security Boundaries for Hosting Untrusted, AI-Generated HTML

Building a self-contained interactive page takes minutes now, and increasingly a model does it. The hosting was built on the assumption that whoever wrote the file, person or model, cannot be trusted.

One of our products lets a small team of admins publish self-contained HTML documents to their clients: interactive reports, prototypes, dashboards a designer built by hand. The ask sounded simple. Upload the file, get a link, send the link. The real work turned out to be everything behind that link.

An uploaded HTML file is a program. It runs JavaScript with whatever privileges the page it lands on happens to have. We were about to take those files and render them inside a platform holding confidential client data. "It's our own file, we trust it" is not a security model. Neither is "we'll sanitize it", because sanitizing away the scripts kills the feature.

The author is changing, too....

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE