DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Securing Read-Only Systems

Get some practical, easy to follow advice from a security expert on how to secure your system, and keep your read-only files safe.

Christopher Lamb user avatar by
Christopher Lamb
CORE ·
Jun. 13, 17 · Opinion
Like (1)
Save
Tweet
Share
1.35K Views

Join the DZone community and get the full member experience.

Join For Free

Sometimes, you have a system you just can't update as quickly as you'd like. Maybe the system can never be taken down. Or it has to run an old operating system because of a specific software package.

These things happen.

But you still need to make sure these systems can't be compromised. After all, if it can't be taken down to be patched, you really don't want it to come down at all, right? and that includes being taken down by malware.

So, if you can't harden the system, you need to harden its surroundings. You'll need to depend on perimeter-based defenses. You'll need to isolate the system, monitor the environment, and track incoming and outgoing traffic. And you can't put software on the system to do it.

To start with, isolate the system. Put it behind a simple switch, and lock the switch down. You don't need to spend a ton of money on this either. A small, simple switch can be configured to only allow configuration from physically attached systems, for example, and you can then configure the switch by physically plugging in a laptop and using the ubiquitous web configuration interface. Only allow the traffic that must pass through the switch, nothing else.

You'll need to monitor the environment too, and the best way to do this without touching the read-only system is to track incoming and outgoing traffic. A way to do this is to configure one of the ports on your switch as a port mirror so that you can capture all the traffic coming into the switch for the read-only system and all the traffic sent by that system to the wider internet. This can end up being a large amount of information, potentially, so you'll need to decide how long you can maintain that information. This, of course, does require another PC, but that PC doesn't need to be expensive, and it can actually run a more modern operating system. You'll need to remove captured log files on a regular basis, and you'll likely need to spend some time analyzing the captured data for possible anomalies.

We have, of course, added new systems to secure the read-only box, but this results in a negligent increase in the overall attack surface. The new monitoring system should not expose services through the switch, although data will still need to be removed. This might be addressed either by USB-based data removal via sneakernet or a secondary NIC and a control network. Both of these possible configurations will require appropriate security controls, of course. And both the monitoring PC and the switch should run the most recent and patched operating systems available.

Read-only systems are a fact of life. But they don't need to be a point of failure.

operating system

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • RabbitMQ vs. Memphis.dev
  • Architectural Miscalculation and Hibernate Problem "Type UUID but Expression Is of Type Bytea"
  • Kubernetes vs Docker: Differences Explained
  • Why the World Is Moving Towards Serverless Computing

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: