Blade and Rack

The Blade and Rack are two of the high-density mounting platforms that we are going to view from a physical security perspective. As always, location and placement really do matter when it comes to the physical security of core, mission critical and high-density components.

Having discussed core components and mission critical components and the ways in which to identify them it is now time to investigate the physical security aspects of Blades and rack mounted devices. Once again finding the “perfect” location and the “right” (orientation) placement at this location is crucial.

Remember always, that physical security encompasses both physical connectivity and availability. It is no good having the most physically secure components if they are inaccessible. The access types and capabilities will vary in accordance with the purpose of the access and the entity requesting that access.

Blades and Blade Enclosures

Rightly or wrongly, I am including Blade enclosures in this category. In essence, at least from a physical security perspective Blade enclosures and the Blade units they house are really just another type of rack mountable computing platform.

Concerning the physical location and physical placement of Blade enclosures and the Blades they house, the general trend has been to place them in the same location as the rack-mounted devices.

Blade servers are servers, designed for high density implementations. The Blade Enclosure provides all of the basic services (power, cooling, network connectivity etc.), management and administrative features common to all of that Blade Enclosure’s members.

This removes the need for certain common components such as bulky failure prone Power Supply Units (PSU) to be built into every Blade unit. External power supply sources, redundant Power Supply Units (PSU) both inside and outside of the Blade Enclosure are becoming the norm in respect to Blade Enclosures.

A direct result arising out of this is that higher densities of components are achievable.

The standard rack’s 1U minimum component size limit removed. Where the 1U minimum component size limit of the standard rack form factor dictates that a maximum of 42 1U devices can be housed in a single rack the Blade enclosure does not follow suit.

Thus, Blade unit densities of more than 100 Blade units per Blade Enclosure chassis are achievable. With these Blade unit densities per Blade Enclosure, a formal, regulated naming convention becomes essential.

Consider the difficulties of working on components from both the front and the back quickly reach nightmare proportions if your naming convention does not have this front and back naming and identification aspects built in. Device and label matching are your friends here.

For more on Building Your Own Naming Convention click here.

Racks and Rack Mountable Devices

The standard computer server-rack platform form factor uses 1U units, which have the following minimum dimensions 19″ (482.6 mm) wide and 1.75″ (44.45 mm) tall.

The most common computer rack server platform form factor uses a 42U configuration which means that each rack is capable of containing a maximum of 42 x 1U units. At the most this means a grand total of 42 rack mounted server computers per rack.

To ensure maximum physical security open racks (not encased) should never be located anywhere other than inside of a strict access regulated area.

For more about Blades, Blade enclosures and rack mount equipment see: The Server Platform

Blade and Rack Physical Security

Ensure that your Blade and rack mounted devices are located in secure environments

Blade enclosures and mounting racks make it considerably easier to ensure the physical security of multiple core mission critical devices. Once secured in their housing (Blade enclosure, rack etc.) you can demobilize them all at once using preset fittings fastened to floor, roof and walls.

Fast release locks and clamping systems work very well to secure the whole assembly whilst still permitting rapid access to all sides of the assembly should the need arise. Although, I do recommend that ample space be left so that all components are serviceable in situ.

Centralization

Here is a strategy that tells us that from a physical security perspective, locating core and mission critical devices in a few discrete locations is preferable to having them spread more or less willy-nilly around the organisation. I personally agree up to a point.

Larger Organizations – For the rack mounted or held in Blade enclosure devices it is a very good idea to locate them in two or three sites if your organisation is large enough to warrant this.

Smaller Organizations – For the majority of smaller organizations this is a practical unreality. In this case locating all such devices in a single location with strict access control is the best way to go.

Blade computing of its very nature demands that Blade components remain in the Blade enclosure in order to remain operative. Without it, they will not function. The location of the Blade enclosure itself is something that requires careful consideration as flexibility in location is another strong point for Blade computing.

Whenever the Blade enclosure is not located in a central controlled environment, ensure that unauthorized persons do not have access to the Blades contained therein nor should they be able to gain access to cabling and cords coming or going from the Blade enclosure.

In nearly all aspects by virtue of the very nature of Blade and rack mounted devices, it is imperative that any newly arising issues be promptly discussed amongst the security team. Your capacity to preemptively deal with any potential and existing threats rests upon it.

Location and Placement

When it comes to the physical security of your core, mission critical, blade and rack mounted components and infrastructure, location and placement really do matter. No other single factor weighs as heavily or pays as handsomely as wisely choosing the locations and placements of your key core components and infrastructure.

So until next time enjoy!

Leave Your Response