Thinking Security: ClearPath MCP Release 17.0

April 29th, 2015ClearPath


This blog is a series about security and how security is about how you think. 

This is a special article about the recently released version of ClearPath MCP software.

Every time that I describe the MCP security architecture to someone, I’m amazed at how the designers (Bob Barton and his team) thought security and built in it to the architecture from the beginning.   Every aspect of the MCP architecture was designed in security in mind – an “object-oriented” architecture before object-oriented was an academic and industry buzzword.  For example, the designers of the MCP operating system invented virtual memory as another way of thinking about security – to abstract the actual memory from the user and allow the operating system to manage it properly and only give the user access to a description of the memory, not an actual pointer.  Other concepts about memory – a dedicated purpose (whether the memory contained code, data, or stack) was revolutionary and way ahead of its time.  In addition, the MCP operating system was architected with strong typing and checking – built to be secure from the start – and it still exudes those characteristics today.

Take this secure environment and add in a system audit trail that’s only capable of being written by the operating system and only allows trusted entities to pass the MCP new entries.  Compare this to other platforms where audit entries are placed in a normal file.  Plus, this audit trail (log file or in MCP terminology, the sumlog) has visibility and ownership built in – only the security administrator can read all entries; normal users only can read their own entries.

The latest release of this secure operating system is MCP 17.0 – it keeps this state-of-the art operating system at the head of the pack with regard to security.   Incremental features in Application Development, Web Services, databases, operations management and countless others add to an operating environment which protects the customer’s data and business logic. And new features like Connectivity Services directly benefit from the MCP’s secure architecture.

One of the trends in architectures today is the buzzword “integrated stack” – a hierarchy of modules which have been tested and validated together to ensure their interoperability and security.   But, how do you ensure this goal if this “integrated stack” comes from multiple vendors, who are each designing and implementing new areas?   The ClearPath MCP environment has been an integrated stack for decades.  The database, web tier, networking, management interfaces and operating system have all been designed, implemented, and tested together so that you are ensured that they work and are secure together.

There are some big benefits of using a secure operating system – less additional infrastructure needed (anti-virus, etc.) that has to be “bolted on” to your environment in order to provide a secure datacenter.    It also means that you have to think LESS about the security of your environment because it’s been built in from the start.

It all comes back to how you think security.  The MCP operating system has security thought and built in – does your operating system?  If not, contact your local Unisys representative and learn more about this amazing, secure architecture and environment for your mission critical and SECURE information.  More information on the ClearPath MCP environment and its products can be found at ClearPath Systems.


Tags-   ClearPath ClearPath MCP MCP Security Thinking Security


ABOUT THE AUTHOR

Michael Kain

Mike Kain is a distinguished engineer and security architect for the ClearPath MCP environment and has held various technical leadership positions during his 30 years of experience at Unisys.