DryDock: A Document Firewall

Auditing a web site’s content is an arduous task. For any given page on a web server, system administrators are often ill-equipped to determine who created the document, why it’s being served, how long it’s been publicly viewable, and how it’s changed over time. To police our web site, we created a secure web publishing application, DryDock, that governs the replication of content from an internal, developmental web server to a stripped-down, external, production web server. DryDock codifies a formal approval process that forces management to approve all web site changes before they are pushed out to the external machine. Users never interact directly with the production machine; DryDock updates the production server on their behalf. This allows administrators to operate their production web server in a more secure and regimented network environment than normally feasible. DryDock audits documents, tracks revisions, and notifies users of changes via email. Managers can approve...

• Type: Conference
• Year: 2003
• Where: LISA
• Authors: Deepak Giridharagopal
• Keywords: LISA 2003, Operating System, Production Web Server, Web Server, Web Site