T. C. HOUSE
Copyright © 2013 SciRes. CN
businesses are attempting to solve the RBAC issues by
embedding the role implementation process within the
software. Many companies use proprietary RBAC soft-
ware, which has impeded RBAC standardization on a
larger scale. Dr. Strembeck [3] designed xoRBAC soft-
ware, which provides a flexibl e RBAC se rvic e. Du e to the
nature of combat and the type of information sent around
the world, all security objects must fit in the same access
architecture in order to communicate effectively and al-
low students to access their college classrooms across
different platforms [2] (Steven Greenwald).
4. What is RBAC?
Role Based Access Control is the use of generated tem-
plates of access authorizations and agreements applied to
a specific student or professor. In the past, network ad-
ministrators dealt with change after change; each new
user required a profile designed for their access authori-
ties. This new form of access control is a proven altern a-
tive to traditional discretionary and mandatory access con-
trol. RBAC technology has been around since 1990 as a
trusted way to manage databases and network access in
large corporations. The network administrator ensures that
each patron has access privileges to their information area
only. RBAC supports three essential security principles:
information hiding, least-privileges and separation of du-
ties. In Figure 1, the “Role” is a semantic concept forming
the basis of RBAC positions. The administrator’s initial
necessity is to build “Role” [7] (S and hu R).
In Figure 2, the instructor is the base role of the
classroom process, from this position of authorization,
the students and administrators are implemented into the
classroom as either learner or supporting entity to the
mobile classroom system.
A New Vision for S ecure RBAC
In a normal access controlled process, each user receives
approval to access specific information, based on the level
of trust placed in the user. In order for the administrator
Figure 1. Example roles in a MS-Ro-BAC system.
Figure 2. Relationship model of hierarchy.
to grant access to certain levels of information, the user
must have met certain attribute requirements. Those
attributes of the user are role, access identity and group
or clearance level. The ideology of students connecting
through secure authenticating hardware and software is a
vital design methodology of the MS-Ro-BAC system. The
device consists of three major concepts: Secure hardware,
software and satellite communications from anywhere I
the world. The user connects to secure LEO satellites by
network browser SHTTP connection. A network intelli-
gent agent controls the actual roles assigned to the users
in any domain [9] (Thomsen D).
5. The Mobile Secure RBAC Network
Ideology
The thought process behind this Device is to take the
server-pull technology design above and implement it
directly into a (firmware) product that is small and mo-
bile. This device concept would be directly in line with a
VPN concept that is supported by the Universities that
are part of the network of schools committed to support-
ing our Military forces around the world. The device
could resemble a laptop or tablet; however, it could also
be a “System on Stick”; meaning it could be a USB de-
vice active system that makes any device compliant with
the software needed to communicate with those institu-
tions that are part of the global VPN connectivity system.
On the university end of the connection process, would
be a high-speed network designed to support satellite
long-range communications with their students. The in-
stitutional side of the network would ensure that there is
always a VPN and server that control the data communi-
cations in proximity of the student. In a MS-Ro-BAC
Network environment, there are no dedicated hubs, serv-
ers, special hard-drives or local administrators. The Net-
work system will instantly provide users with the ability
to transmit data, instan t message and conduct live conf e-
rences while participating in a Distributed Compartment
(DISCOM) RBAC secure environment [3] (Greenwald S).
Software and Hardware Aspects
The university could create a system that is completely
self-contained, as it pertains to the hardware and software
needed to communicate directly to their institution’s sa-
tellite network. The system case could be lightweight and
very durable where field use is applicable. A small key-
board and GUI is available to send and receive data.
There are two USB ports to assist with uploading and
downloading of files. A proprietary operating system (OS)
that is similar to the Microsoft Pentium 4 processor New
Generation Secure Computing Base (NGSCB) will con-
trol the mobile device. A wireless network radio will
sustain LEO satellite connectivity. Biometric thumbprint