FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
Document Title:
Document Type:
Release:
Abstract:
Document Status:
Originator & Dept:
Contributors:
Internal Reviewers:
Secure Support Role Definitions for SECURENT Build
Requirement Definition
BI3S55/S60 onward
The ACP requires that access to POA systems be controlled by the
use of pre defined roles to which users can be assigned. Such roles
will allow users to access only those parts of the system, with
associated tool sets, they need in order to complete the tasks
associated with that particular role. This document summarises the
requirements and defines the roles specifically engaged in support
activities, with associated objects, domains and access
requirements.
APPROVED
Mark Ascott, DU Secure Builds
Simon Fawkes, Peter Robinson, Steve Parker, Alex Robinson
See section 0.2
External Reviewers: None
Approval Authorities:
Name Position Signature Date
Mik Peach SSC Manager
Steve Gardiner
Core Services Operational
Manager
Tan Cooley
SMC Manager
Bill Mitchell
POA Security Manager
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE Page: 1 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
0.0 Document Control
0.1 Document History
Version No. I Date Reason for Issue Associated
CP/PinICL
No.
0.1 10/01/02 First draft CP3283
0.2 19/10/02 Updated with comment received from PVCS review cycle. CP3283
0.3 04/02/03 Updated to reflect minor implementation changes to the CP3283
solution
0.4 15/07/03 Updated with new Riposte tools for counters. CP3482
1.0 08/08/03 I Updated to APRROVED with appropriate comments from P3482
PVCS review cycle addressed. from
LL 31/12/03 Updated with new roles for ADSL CHAP Password CP3584
Management.
Added new SAPSUP role CP3640
2.0 18/03/04 Updated to V2.0 APPROVED following PVCS Review cycle. I CP3584
CP3640
0.2 Review Details
Review Comments by:
Review Comments to:
Mark.ascott_
GRO
Mandatory Review Authority
Name
APDU Delivery Unit Manager
Mark Taylor
IPDU PIT Manager
Jim Stanton
RASD POA Security TDA
Alex Robinson
CS POA Security Manager
Peter Sewell
CS Systems Support Centre Manager
Mik Peach
DU Design Authority Support
Simon Fawkes
ITU PIT
Asad Sheikh
ITU PIT
Brian Bradley
DU Secure Builds
Mia Brittain, Stephen Sloan
RASD Systems Management TDA
Glenn Stephens
Core Services Operational Management
Steve Gardiner
Core Services SMC
Ian Cooley
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 2 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
Core Services SMG Mike Conneely
Core Services Operational Management Warren Welsh
Optional Review/Issued for Information
DU DCO Suzanne Gordon
ITU Test Debbie Richardson
ITU LST Pete Dreweatt
CS POA Security Chris Billings
CS Migration Implementation Manager Sheila Bamber
RASD Nial Finnegan
ITU LST Graham Jennings
SMG John Bradley
0.3 Associated Documents
Reference Tag I Version I Date Title Source
PA/TEM/001 {] This document is created from this version of PVCS.
PA/TEM/001
RS/POL/003 I [2] ‘Access Control Policy PVCS
RS/FSP/001 [3] Security Functional Specification PVCS
DE/HLD/002_‘I 14] OpenSSH Auditing and Logging Server PVCS
TD/ION/029 [6] FTMS Configurations for AP Clients at CSR+ PVCS.
RS/REQIO20 I [7] Implementation of Anti-Virus Requirements PVCS
RS/DES/075 [8] Communication Monitoring System DMZ Security PVCS
Overview
RS/DES/080 [9] BI3 NT Domain Design PVCS
RS/DES/081 [10] BI3 Implementation Guide for NT Platforms PVCS.
RS/DES/082 (11) BI3 NT Server and Workstation Names PVCS
RS/REQ/022 [12] BI3 Secure Role Definitions for SECURENT Build PVCS
SMG/DES/O1_I [13] I 0.1 Terminal Server Document SMG
7
[4] [03
RS/DES/093 HLD for CHAP Password Handling PVCS
Unless a specific version is referred to above, reference is made to the current versions of the
documents.
0.4 Abbreviations/Definitions
[Abbreviation I Definition I
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 3 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
BDC Windows NT Backup Domain Controller Server
BI3 Release Banking Increment 3
cP Change Proposal
CSR+ Core Services Release +
DCS Debit Card Services
DRS Data Reconciliation Services
ISD Abbreviation associated with Core Services staff
Local Access via the console attached directly to an NT platform
NWB Network Banking
PDC Windows NT Primary Domain Controller Server
SAS Secure Access Server
SSE Secure Support Environment
SSH Secure Shell
SSHC Secure Shell Client
SSHD / SSH Server Secure Shell Server
TS Terminal Server
0.5 Changes in this Version
Version I Changes
1.0 Updated to APPROVED
LL New PWYLoad role added. References to Pathway have been changed to POA. New SAPSUP
role added for Fujitsu Consulting SAP Support.
2.0 Updated to APPROVED
0.6 Changes Expected
Changes
For BI3S60 no further changes are expected prior to this document being set to APPROVED status.
For BI3S70, CP3652 and CP3653 which cover enhancents to the Cygwin Toolset and Riposte installation on
SAS servers will result in new drafts of this document being produced.
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 4 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
0.7 Table of Contents
1 INTRODUCTION.
3 REQUIREMENTS.
3.1 AFFECTED Support ROLES. 9
3.2 NEW SUPPORT ROLES... ssnnnnnnninnnnnnninnnnnnnnnnnnninnnnnnnnnnnnnnnnnnnnnnnnnnnnned)
3.3 REDUNDANT SUPPORT ROLES. - . 10
4 IMPLEMENTATION...
4.1 NT ADMINISTRATOR USER noone nnn eb
4.2 TSADMIN ROLE. 12
4.3. SSHADMIN ROLE. 12
4.4 PWYLoapD ROLE. 12
5 SUPPORT ROLE USERS.
5.1 PWYDCS Users. 13
5.2. HUTHTIP, PDRTIP Users. 13
5.3 PWYKMS USERS.....o.sscmennsnnnnnsennnneeenn sonnei sevens L
5.4. PWYCSM Users. 13
5.5. SYSMAN Usrrs. 14
5.6 SECURE ACCESS SERVER USERS. 14
5.7 COUNTER ACCESS USERS. oo nnn - ssnnnnnnnnnnsnnnnnnne LA
5.8 NT Data CENTRE SYSTEM ACCEsS USERS. 14
6 SUPPORT AUTHENTICATION PROCESS.....
6.1 LOGON AT DESKTOP... see - sons 14
6.2 LOGON AT SAS TERMINAL SERVER. 15
6.3. LOGON TO SSH SERVER. 15
6.4 PROCESS SUMMARY ...oonnnnnnnunnnnnnnnnnnn - ey
7 SUPPORT ROLE DESKTOPS..
7.1 STANDARD SECURE ROLE DeskTop. 17
711 * Apps MAN.....
7.1.2 SSC Apps SUP.
7.1.3 Operational MAN..
7.1.4 Application SUP.
7.1.5 PWYLoad.
7.1.6 SAPSUP....
7.2. TERMINAL SERVER CLIENT DESKTOP.
7.2.1 SSC Support Group..
7.2.2. SMC Support Group.
7.2.3 MSS Support Group.. .
7.2.4 Operational Management Support Group
7.2.5 Fujitsu Consulting SAP Support Group...
8 SUPPORT TOOLG..........004.
8.1 Too SET LOCATION AND ACCESS.
8.2 RIPOSTE TOOLS ON COUNTERS (CP3482).
8.3. TOOLS AVAILABLE. ....cseneo senna
8.4 UPDATING THE TOOL SET.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 5 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
8.4.1 Normal Circumstances.
8.4.2 Exceptional Circumstances.
9 APPENDIX A —- SUPPORT TOOL SET...
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 6 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
1 Introduction
The nature of the POA Horizon system requires that access to the counters and core
systems should be strictly controlled. [ACP] states that effective control depends on
having a clear definition of the roles and the responsibilities of all personnel who need
some form of access to the system. Users will gain access by being assigned to these
roles. This will be core to POA implementing the principles of least privilege as
described in [SFS]. POA will translate the human roles detailed in [ACP] into securely
configured roles, known as secure roles.
RS/REQ/022 defines the requirements for all POA human secure roles (except for
Support Roles) that access the POA data centre systems via an access point, which is
usually an NT workstation. These requirements are translated by IPDU Secure Builds
and IPDU PIT in order to generate a secure desktop for each role.
RS/REQ/023, this document defines the requirements of the human secure roles
involved with providing support of the POA Horizon solution. It describes for each of
the POA support groups the menus and tool sets required and the secure support
environment desktop access method used to connect to remote counters and data
centre systems.
2 Scope
This document only addresses the human user roles defined for use by the support
groups involved with supporting the POA Horizon solution systems. These support
roles are to be implemented as part of the POA central NT systems and access rights
assigned to cach role. Each support role specified within this document access
counters and the data centre NT systems through the POA NT Domain Structure
referenced in [9] and in accordance with the security configuration referenced in [10]
SMC and SMG support roles that authenticate in the SYSMAN domain are not
described in terms of their Secure Desktops. For these roles it is assumed that their
desktops include Terminal Server Client and that Terminal Server Client provides
these roles with access to the Secure Support Environment implemented within the
POA NT Domain Structure. Document reference [13] describes the configuration for
SYSMAN secure roles.
Non support roles used by SMC, SMG and Girobank are specifically excluded from
this document as they are authenticated on separate NT systems which form part of a
third party managed service. These roles are excluded from accessing the Secure
Support Environment.
This document does not describe the implementation or configuration of OpenSSH
components on the NT data centre systems or counters. This information is described
fully in reference [4].
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 7 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
3.1
3.2
3.3
Requirements
The requirement to implement a secure role based access control system emanates
from [ACP]. [ACP] further defines the roles that are required for access to the POA
Systems and the responsibilities of these roles.
Release BI3 Network Banking and release BI3S30 Debit Card System introduced
more stringent requirements regarding support access to counters and the data centre
NT systems. To satisfy these new requirements, a Secure Support Environment is
being introduced and as a result new user desktops and access mechanism are required
for the support groups. This document defines the new authentication processes,
desktops, and tool sets available to the support groups.
Affected Support Roles
The POA support roles affected by CP3283 are:
« PWYDCS\SSC Apps SUP
¢ PWYDCS\SSC Apps MAN
e PWYDCS\Operational MAN
e PWYDCS\Application SUP
In addition to the above two roles that authenticate in the SYSMAN third party
supplier domain are also affected. These two roles are:
e SYSMAN\SMC
e SYSMAN\MSS
New Support Roles
At Release BI3S55 a new privileged role is introduced for ADSL CHAP Password
Handling. See RS/DES/093 for more details concerning the use and procedures
associated with this new role. The role is named:
© PWYDCS\PWYLoad
At Release BI3S60 a new support role is introduced for Fujitsu Consulting staff who
will provide support for the new SAP financial system being introduced to the Horizon
data centres at BI3S60. This new will provide this group of support staff access to the
SAP Host via the SAS servers and SSH. The role is named:
e PWYDCS\SAPSUP
Redundant Support Roles
None of the existing support roles are made redundant.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 8 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 9 of 39
FU.
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
41
Implementation
For the four POA support roles, each support role will be set up as a Secure Role.
Secure Roles will be mapped very tightly on to the Group concept within NT.
Individual users will be assigned to these Groups in which access to objects, domains,
servers and associated privileges will be controlled. Reference [10] describes in more
detail the rules and methods for applying Secure Roles onto the NT Group concept.
These Secure Roles are defined in Section 7.
Secure Roles use defined access points that have an accompanying Physical Platform
Design Specification (PPDS) document. Access to objects will be made available to
each role at the relevant access point. This document specifically covers the Secure
Support Roles accessing the data centres and counters
The definition of the Secure Support Roles is maintained in a spreadsheet by IPDU
Secure Builds, this spreadsheet is converted to produce automated NT command files.
These command files will be made available to ITU PIT. The command scripts will be
incorporated into the POA SECURENT build process and into the specific platform
configuration builds by ITU PIT for deployment into test and live estate environments.
Secure Support Roles, as defined in this document, will be implemented using
automated command scripts. By doing this, it will simplify the implementation and
maintenance of the roles.
Human user accounts created from the defined roles may only be members of one
Role/Group definition. This is required to ensure the user is only provided with one
appropriate tool set. Implementation of the menu structure for each Group will ensure
that users assigned to that Group will be able to access the application set necessary
for them to fulfil their duties.
NT Administrator User
The Windows NT operating system is provided with a super user known as the
‘Administrator’. This user has full administration and configuration privileges which is
exercised at both system/server and domain level. This capability cannot be removed
from Windows NT. POA recognises the power that this user has and the ability that a
human user, using the administrator user, has to interfere with the day to day operation
of the POA solution.
To address this issue, POA will limit and restrict the use of the NT Administrator User.
This will be achieved by:
> Renaming the Administrator User on all NT Servers so that it is hidden from the
system. The account name and password will be specified by the POA Security
Manager, which will be strictly controlled and stored in a secure safe.
> Restrict full administrator privileges to the “Operational Management’ role. Use of
this role will be subject to the management and procedural controls set out in the
“POA Code of Practice’, PA/STD/010.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 10 of 39
FUJ00088104
IJ00088104
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
4.2
4.3
4.4
TSadmin Role
CP3283 introduces a new administrator role known as TSadmin. This new role will be
responsible for day to day operations and administration of the PWYSAS domain and
the Secure Access Servers. The security configuration will be setup to prevent
PWYDCS roles from administering PWYSAS. Likewise, PWYSAS\Admininistrator
whilst not being prevented from its administration capability by security configuration
changes, sufficient monitoring capability will be added to the Security Event Auditor
and POA Security Manager roles to ‘watch’ the use of this user.
The TSadmin role will be allocated to senior Core Services NT staff and will be limited
to no more than three individuals at any one point in time. It is this role that will create
and manage the terminal server user accounts. These individual accounts will be
created from the pre-defined TS user templates. Each individual user will be mapped
to a TS profile and will have a defined user home directory. Customer Services
Security will be responsible for TSAdmin user accounts are allocated, created and
managed.
SSHadmin Role
This new role is introduced for the purpose of managing the configuration of the SSH
Client and SSH Server components. Like the TSadmin role, this new role will be
limited for use by senior Core Services NT staff and will be limited to no more than
three individuals at any one point in time. This role will only be able to administer the
Secure Shell configuration files. Only this human role will be granted access control
permissions greater than Read and Execute. Customer Services Security will be
responsible for SSHAdmin user accounts are allocated, created and managed.
PWYLoad Role
This is a special role introduced for use by the Customer Services Security
Management team. The purpose of the role is to load obfuscated passwords into the
CHAP Password database. The role accesses the CHAP Password database by logon
at Release BI3S55 at the BootLoader Server console. Once logged on, an executable
is called to provide a GUI interface that enables passwords to be loaded into the
database. At Release BI3S60 the role will also be able to logon at the ADSL Radius
Servers and FRIACO/Dialled Radius Servers console.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 11 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
5 Support Role Users
5.1. PWYDCS Users
SSC support staff and Core Services operational management staff who access the
POA Horizon systems must have an individual user account registered in the
PWYDCS domain. Each user account is created from a pre-defined user template
which is described in Section 7 of this document. Associated with each NT user
account registered in PWYDCS is a SecurID Token and four digit PIN
Existing support user accounts remain unchanged within the SSE. New support user
accounts will be created using the existing and current processes.
User templates exist for the following support roles:
e Users assigned to SSC Apps SUP role have user accounts created from user
template ‘zzSSC Apps Sup’
e Users assigned to SSC Apps MAN role have user accounts created from user
template ‘zzSSC Apps MAN’
e Users assigned to Operational MAN role have user accounts created from user
template ‘zzOPSMAN’
e Users assigned to Application SUP role have user accounts created from user
template ‘zzAPPSUP’
5.2. HUTHTIP, PDRTIP Users
Both HUTHTIP and PDRTIP domains which contain the Remote TIP Gateway
systems at Post Office sites are authentication domains. Both are configured with
identical support roles to those described for PWYDCS Users above. Access to these
remote domains/systems using SSHD will require support staff to login and
authenticate using user accounts created in the HUTHTIP and PDRTIP domains.
5.3 PWYKMS Users
TBA following input from Graham Hooper and Geoffrey Vane.
5.4 PWYCSM Users
TBA
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 12 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
5.5 SYSMAN Users
5.6
5.7
5.8
6.1
User accounts registered in this third party supplier managed domain must comply
with the security policies defined in [ACP].
From the requirements specified in CP3283 the following support roles from this
domain are relevant to the SSE:
e SMC
e MSS
Secure Access Server Users
Changes to the solution implementation mean that user templates and user accounts
are no longer required within the PWYSAS domain and Secure Access Servers.
Counter Access Users
CP3283 specifies that only the SSC support group will be granted access to counters
using SSE.
At the counter only a common/shared user account is required. SSH Client will
capture the logon username from the Terminal Server Client session and will record
this user name in the command log files that SSH Client generates. The user account
defined for the SSC support group is:
@ sussc
NT Data Centre System Access Users
Access to Data Centre NT systems will in the main be achieved by support staff
logging on via SSHD using their PWYDCS user account. Exceptions to this will be
HUTHTIP and PDRTIP remote TIP FTMS Gateway domains, PWYKMS and
PWYCSM domains. Access to these four domains will be achieved by using
equivalent user accounts created in these domains.
Support Authentication Process
Logon at Desktop
All support users that logon with a PWYDCS user account will specify their unique
username and associated password. The system will then prompt for SECURID logon
using their assigned PIN with the token value displayed at the time of logon.
The same logon and authentication process should be followed for all support users
who authenticate in the SYSMAN domain.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 13 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
6.2
6.3
Once the identification and authentication process has completed the user is presented
with their usual desktop with an array of tools as specified in Section 7. One of the
tools available from this desktop is the Terminal Server Client. Executing the Terminal
Server Client tool will result in the system opening a new window at the workstation
that results from a connection to a Secure Access Server located in PWYSAS domain.
This new Terminal server window will display a prompt for a user name and password.
At Release BI3S30, Support Users can still access counters and NT data centre
systems using their pre BI3S30 desktops and tools. However from BI3S30 the only
approved and authorised support access method to counters and NT systems in the
PWYPUB and DCSSERV resource domains is via the Terminal Server/Secure Shell
access route.
Logon at SAS Terminal Server
At the Terminal Server window login prompt the support user should re-enter their
individual terminal server user account created in PWYDCS domain and its associated
password.
Successful logon will result in the SAS desktop being made available to the user.
From this desktop the Secure Shell Client (SSHC) will be available.
Logon to SSH Server
The user can invoke the SSHC by typing:
ssh -I <user name> <target-address>
where:
<user name> will equate to the support group users individual user account name
created in PWYDCS domain or the other authentication domains referred to in section
5 for NT data centre systems or user account sussc for counters.
<target-address> will equate to the IP address of the target counter or NT system.
Execution of the above causes the SSHC to make a connection with the SSH server
running on the target system. The user account specified will be authenticated at the
target-system and if successful a SSH session will be initiated. The SSHC will log
each command executed during the session recording the PWYDCS domain (or other
domain) logon user account name that has initiated the SSH session.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 14 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
6.4 Process Summary
See diagram below.
6
Lag ae.
CTRL + ALT + DEL te
f
y
Logon details entered
Domain: PWY5CS Pwypcs
SecurlD PIN a. eens user
SecurlD Token Value
Invoke Terminal
Server Client
PWYSAS Terminal
oon Server authenticates
Domain: PWYDtS = ay Server authe
< OK
Invoke Terminal SSH
Client
oe 41 susse <terget>
Execute required
support tools
SSH Server
authenticates SSH
Client logon
OK
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 15 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7 Support Role Desktops
7.1. Standard Secure Role Desktop
This section describes the desktop menu and tool set provided to the four POA
Support Roles as a result of logging on with their PWYDCS, PWYKMS, (HUTHTIP,
PDRTIP) user account, password and Securid Token. This logon will be conducted at
their normal access point workstation or server.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 16 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.1 SSC Apps MAN
Group Name to be Implemented SSC Apps MAN,
Last Updated
Secure Role Type Privileged Full Administrator eapable
Desk Top Type Restricted Desktop Menu
NT Servers ‘AILNT Servers, also needs acoess to Post Office Outlet Counters and
access to Sequent UNIX Servers
‘Access Rights Read, Write, Exeoute
‘Requires SecurID Authentication Yes
Authentication Domain PWYDCS, PWYHQ, PWYFTMS, HUTHTIP, PDRTIP-
Resouree Domain Access ‘Allresouree domains and NT data centre systems via SSH Client access
method
Access Point SSC NT Client PC SD/DES/172
‘ACP Equivalent “Application Support (SSC)
Change Triggers
‘Menus and Tools } Tivoli Remote Console
» — Relient
» — Reonsole
» — Terminal Server Client
+ — RiposteGetMessage.exe
> Ripostelndex.exe
> RiposteNode.exe
> _ RiposteObjectSecurity. Exe
© RiposteObject.exe
© RipostePing exe
© RipostePriorityMessage.exe
> RiposteQueryUK-exe
> _ RiposteNextMessage.exe
> RipostePutMessage.exe
> _ RiposteScanMessage
> — RiposteStatus.exe
>» RODBClient.exe
CMD prompt
> _ ExCeed for Windows NT (V6.1)
> — Visual Basic LD.E
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 17 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
FUJ00088104
FUJ00088104
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
> Telnet
> FIP (To Host Sequent, and other POL Services)
Microsoft Diagnosties
NT Event Viewer
WinZip/Pkzip
CD Rom writing software
Texipad
Microsoft Word
Microsoft Excel
Microsoft Access
‘Microsoft Explorer
Internet Explorer (e/w SSC default links page)
Full NT Control Panel
Performance Monitor
Registry editor
TIP Repair
Inchouse Utilities
> Archive Viewer
> Expiry Reporter
> Stops Reporter
ei
Formatted File Utility
F MessageStore Utility
> EndOtMay Reporter
> MessageStore Sort Utility
VPN Utilities
> VPNDiagClient.exe
> SVPNTSTN.exe
‘Athene Utilities
‘Athene Analyst
Analyst
ViewDB Storage
‘Athene Automatic Reporting
Define A Report
Schedule Editor
View Processed Reports
‘Athene Client-Server
Client-Server
‘Athene CustomDB
CustomDB
Schedule Editor
‘Web Log Parser
‘Athene Explorer
Define A Report
Explore Reports
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 18 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
“Athene Planner
Build Baseline Model
Calibrate Baseline Model
Delete Models,
Edit Baseline Model
Edit Reference Tables
Edit Thresholds
Evaluate Model
Modify Model
View Results
‘Athene Sentinel
Alert Summary
Sentinel
Requires Access to All systems
ZzSSCAPP_MAN
SSC Apps MAN
‘Domain Admins
‘Administrators
Domain Users Yes TSSC Apps MAN
Yes TeonfineLogin
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 19 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.2 SSC Apps SUP
‘Group Name to be Implemented SSC Apps SUP
Last Updated
Secure Role Type Privileged Full Administrator capable
Desk Top Type Restricted Desktop Menu
NT Servers ‘AINT Servers, also needs access to Sequent UNIX servers
‘Access Rights Read, Execute
Requires SecurlD Authentication Yes
‘Authentication Domain PWYDCS, PWYHQ, PWYFTMS, HUTHTIP, PORTIP
Resource Domain Access ‘Allresource domains and NT data centre systems via SSH Client access
method
Access Point SSC NT Client PC SD/DES/172
‘ACP Equivalent ‘Application Support (SSC)
‘Change Triggers
Menus and Tools © Tivoli Remote Console
» — Relient
© Reonsole
> Terminal Server Client
} RiposteGetMessage.exe
> Riposteindex.exe
® — RiposteNode.exe
RiposteObject.exe
> RipostePing.exe
> RipostePriorityMessage.exe
© RiposteNexiMessage exe
> RiposteQueryUK exe
> RiposteScanMessage.exe
RiposieStatus.exe
>» RODBClient.exe
‘CMD prompt
> ExCeed for Windows NT (V 6.1)
> Visual Basic LD-E.
> Telnet
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 20 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
FUJ00088104
FUJ00088104
— FIP (To Host Sequent, and other POL Services)
NE uilities
Microsoft Diagnostics
Event Viewer
WinZip Pkzip
‘CD Rom writing software
Textpad
Microsoft Word
‘Microsoft Excel
‘Microsoft Access
‘Microsoft Explorer
Tntemet Explorer (e/w SSC default links page)
Full NT Control Panel
Performance Monitor
Registry editor
TIP Repair
In-house Utilities
> Archve Viewer
> Expiry Reporter
> Stops Reporter
> — Formatted File Utility
> MessageStore Utility
¥ EndOiay Reporter
F MessageStore Sort Utility
VPN Utilities VPNDiagClient.exe
‘Athene Utilities ‘Athene Analyst
Analyst
ViewDB Storage
‘Athene Automatic Reporting
Define A Report
Schedule Editor
View Processed Reports
Athene Client-Server
Client-Server
‘Athene CustomDB
CustomDB
Schedule Editor
Web Log Parser
‘Athene Explorer
Define A Report
Explore Reports
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 21 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
“Athene Planner
Build Baseline Model
Calibrate Baseline Model
Delete Models,
Edit Baseline Model
Edit Reference Tables
Edit Thresholds
Evaluate Model
Modify Model
View Results
‘Athene Sentinel
Alert Summary
Sentinel
Requires Access to All systems
ZzSSCAPP_SUP
SSC App SUP.
‘Domain Admins
‘Adminstrators
Domain Users Yes TSSC Apps SUP
Yes TeonfineLogin
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 22 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
FUJ00088104
FUJ00088104
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.3. Operational MAN
Group Name to be Implemented ‘Operational MAN
Last Updated
Secure Role Type Privileged
Desk Top Type Restricted Desktop Menu
NT Servers AILNT Servers
Access to Sequent UNIX Servers.
Access Rights Full Administrator
Requires SecurID Authentication Yes
‘Authentication Domain
PWYDCS, PWYHQ, PWYFIMS, HUTHTIP, PDRTIP
Resource Domain Access
‘All resource domains and NT data centre systems
‘Access Point ‘Core Service NT Client PC
‘Third Party Supplier PC
NT server console
‘ACP Equivalent ‘Operational Management
Core Services Role
Change Triggers
‘Menus and Tools
> Compag systems reference library
> Insight Manager
> Terminal Server Client
> SQL Server Admin
> Technet
> Microsoft Office
> NT Resource Kit
> Onnnet (telnet/ftp)
> Patrol v3.2.05
> Legato Administrator
* nt stvtools
> Tivoli desktop
> TE5.5 for access to Tivoli web
> NT resource kit remote console server
PC Xware
CMD prompt
> VPNDiagClient.exe
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 23 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
FUJ00088104
FUJ00088104
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© Notepad
} SVPNTSTNexe (Utimaco API Function Tool)
‘Athene Utilities
‘Athene Analyst
Analyst
ViewDB Storage
‘Athene Automatic Reporting
Define A Report
Schedule Editor
View Processed Reports
Athene Client-Server
Client-Server
‘Athene CustomDB
CustomDB
Schedule Editor
Web Log Parser
‘Athene Explorer
Define A Report
Explore Reports
Athene Planner
Build Baseline Model
Calibrate Baseline Model
Delete Models
Edit baseline Model
Edit Reference Tables.
Edit Thresholds
Evaluate Model
Modify Model
View Results
‘Athene Sentinel
Alert Summary
Sentinel
Requires Access to
Floppy dise drive
Locally connected printer
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 24 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 25 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.4 Application SUP
Group Name to be Implemented ‘Application Sup
Last Updated
Secure Role Type Privileged
Desk Top Type Restricted Desktop Menu
NT Servers ‘Access to Sequent UNIX Servers
‘Access Rights Read, Write, Execute
Requires SecurlD) Authentication Yes
‘Authentication Domain PWYDCS, PWYHQ, HUTHTIP, PDRTIP
Resource Domain Access PERFMAN
‘Access Point
‘Core Services NT Client PC
‘Third Party Supplier PC
ACP Equivalent “Application Support
Core Services Role
Change Triggers
Menus and Tools > Discoverer 2000
> PC Xware
> Microsoft Office
> Onnnet (telnet/ftp)
> Patrol v3.2.05
> Legato Administrator
> IES
> SQ Server Admin
> Terminal Server Client
CMD prompt
Athene Utilities
‘Athene Analyst
Analyst
ViewDB Storage
‘Athene Automatic Reporting
Define A Report
Schedule Editor
View Processed Reports
‘Athene Client-Server
Client-Server
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 26 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
‘Athene CustomDB
CustomDB-
Schedule Editor
Web Log Parser
‘Athene Explorer
Define A Report
Explore Reports
‘Athene Planner
Build Baseline Model
Calibrate Baseline Model
Delete Models
Edit baseline Model
Edit Reference Tables
Edit Thresholds
Evaluate Model
Modify Model
View Results.
‘Athene Sentinel
Alert Summary
Sentinel
Requires Access to Floppy dise drive
Locally connected printer
‘Application SUP
‘Domain Users Lapplication SUP
TeonfineLogin
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 27 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
FUJ00088104
FUJ00088104
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.5 PWYLoad
Group Name to be Implemented PWYLoadGroup
Last Updated ‘08/01/04
Secure Role Type
Privileged Administrator access capable
Desk Top Type Restricted Desktop Menu
NT Servers Access to Bootloader Server , ADSL Radius Servers and
FRIACO/Dialled Radius Servers
‘Access Rights Read, Write, Execute
Requires SecurlD Authentication Yes
‘Authentication Domain PWYDCS
Resource Domain Access
BBOOT, WBOOT and PWYRAD systems via direct logon at server
console
‘Access Point
Server Console for Bootloader Servers, ADSL Radius Servers and
FRIACO/Dialled Radius Servers
‘ACP Equivalent
None
Change Triggers
CP3584
‘Menus and Tools
CMD prompt
Microsoft Diagnostics
NI Event Viewer
WinZip/Pkaip
Texipad
Microsoft Word
‘Microsoft Excel
Microsoft Access
Windows Explorer
Full NT Control Panel
Regisity editor
Password Loader executable (maps onto
CARADIUS_CFG\Bin\ReapPwdLoader.exe on the Bootloader
server)
Requires Access to
‘All systems in BBOOT, WBOOT and PWYRAD domains. Requires
access to floppy dise drive.
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 28 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 29 of 39
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
FUJ00088104
FUJ00088104
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.1.6 SAPSUP
Group Name to be Implemented GSAPSUP
Last Updated 26/02/04
Secure Role Type
Privileged Administrator access capable
Desk Top Type Restricted Desktop Menu
NT Servers ‘Access to SAP Host via dedicated SAS Servers MBOSASO3 or
MWISASO3
‘Access Rights Read, Write, Execute
Requires SecurlD Authentication Yes
‘Authentication Domain PWYDCS
Resource Domain Access PWYSAS
‘Access Point
Fujitsu Consulting Support Workstation + SecurlD ACE Agent
‘ACP Equivalent
None
Change Triggers
CP3640_
‘Menus and Tools
Terminal Server Client
SAP GUI Interface (maps onto an executable that needs to be supplied by
Fujitsu Consulting staff, may require FC to complete an installation to
obtain this piece of information.
FIP Client. Notes: 1, the SAP Host will be configured with FTP Server
Service and the FIC SAP Support user group on the Solaris SAP Hosts
must be granted permissions to access and execute FTP. 2, the DMZ
firewalls must be configured to allow inbound and outbound FTP traffic
for this support group.
In-house Utilities
> None requirements specified.
Requires Access to
FTP capability between SAP Hosts and FJC SAP Support
Workstations.
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 30 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 31 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
7.2 Terminal Server Client Desktop
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
This section describes the desktop available to each of the Support groups provided
with Terminal Server access to the SSH Client.
SSC Support Group
Access provided to SSH Client. The SSH Client can be used to access counters and
data centre NT systems.
SMC Support Group
No access to SSH Client provided.
MSS Support Group
No access to SSH Client provided.
Operational Management Support Group
Access provided to SSH Client. The SSH Client can only be used to access data
centre NT systems.
Fujitsu Consulting SAP Support Group
Access provided to SSH Client. The SSH Client can only be used to access the SAP
Host in the data centres.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 32 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
8.1
Support Tools
Tool Set Location and Access
The support tool set will be installed at the same location on all NT platforms.
The ‘root’ directory is known as:
e C:\Support
Underneath this directory is the following structure:
e C:\Support\Tools\Generic
¢ C:\Support\Tools\Generic\Cygwin
e C:\Support\Tools\Generic\Ntreskit
e C:\Support\Tools\Admin (only on Secure Access Servers)
As the directory names imply, Generic means that the tools are common and available
to all support groups. The Cygwin directory holds all the GNU tools generated and
delivered into PVCS by IPDU Estate Management Development team. The Ntreskit
directory holds all Windows NT resource kit utilities. These are made available to all
support groups.
In addition to the above ‘common’ directories, each support group will have a
dedicated directory to hold bespoke developed tools. The directories are:
e (C:\Support\Tools\SSCSUP
e C:\Support\Tools\SMCSUP
e C:\Support\Tools\SYSMANSUP.
e C:\Support\Tools\OPSMANSUP.
e C:\Support\Tools\SAPSUP
Each support group will be able to access tools located in their directory. They will
not be able to access the directories of the other support groups. All support group
access will be configured as Read and Execute. Only administrator privileged users
will be able to update the above directories and add further tools to the tool set.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 33 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
8.2 Riposte Tools on Counters (CP3482)
The following tools are added to all counters via the PIT build at Release BI3S40R as
aresult of CP3482. The tools are located in directory C:\Counters\Bin.
RiposteConfig.exe
RiposteGetMessage.exe
RiposteListen.exe
RiposteNextMessage.exe
RiposteNode.exe
RiposteObject.exe
RipostePutMessage.exe
RiposteScanMessage.exe
RiposteStatus.exe
8.3 Tools Available
A full list of the tools available is given in a table in Appendix A. This appendix will be
kept update as further tools are added in the future.
8.4 Updating the Tool Set
There are two situations in which the support tool set can be updated. These are
‘normal’ and ‘exceptional’ circumstances.
8.4.1 Normal Circumstances
This section gives a brief overview of the process that should be followed in normal
circumstances in order to add new tools to the tool set.
e The Support group identifies new tool(s).
e The Support group subject the tool(s) to local testing to ensure the tool(s) is/are fit
for purpose.
e¢ The Support group raise a CP to introduce the new tool(s), indicating whether it
is/they are generic tool(s) or specific to the support group and identifying the
target release.
e POA development impacts the CP. If the CP is approved
e IPDU Secure Build update this document [RS/REQ/023] and publish on PVCS
review cycle.
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 34 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
e The Security TDA and POA Security Manager are both Approval Authorities. In
addition each Support group will also have an Approval Authority for this
document. The IPDU PIT Manager will also be an Approval Authority.
e¢ Once this document has gained the necessary approval signatures, the IPDU PIT
Manager will authorise IPDU PIT to progress the updates necessary to add the
tool(s) to the tool set directories. IPDU Secure Build will adjust the security
configuration as necessary.
e The work packages are subjected to testing by IPDU System Test and on
completion of testing the new work packages are added to the SUPPORT TOOLS
platform configuration build for release to the live estate systems.
e The new tools are delivered and installed onto the NT platforms using Tivoli.
8.1.2. Exceptional Circumstances
There will always be emergency situations that will require new tools to be made
available urgently. At this point in time, no process for handling exceptional
circumstances has been identified. Simon Fawkes is leading the investigation into how
this situation will be dealt with and will identify the proposed solution once known.
9 Appendix A - Support Tool Set
This appendix lists the GNU tools available as part of the Support Tools platform
Configuration SPBV
The following detail is associated with the table on the next page.
The tools identified in the table are located in directory:
C:\Support\Tools\Generic\Cygwin (on all platforms)
A ‘Yes’ in the following column indicates that the program is to be executable by
members of the support group, while ‘No’ indicates that permission to execute the
commands is not to be granted.
The commands shown in the table do not have the ‘.exe’ suffix. The ‘.exe’ suffix will
be present for all executables when delivered to PVCS and installed on the platform.
Selected and where required, security approved NT Resource kit utilities provided by
Microsoft at Release Supplement 4 are made available in directory:
C:\Support\Tools\Generic\NTreskit (on all plat
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 35 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 36 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
Table 1
‘Support groups at Data Centre User groups at Counters
Commands SSC_I ISD _I MSS I Tivoli Maestro SSC ISD MSS. Tivoli Maestro
basename Yes_I Yes [No I No Yes Yes [No I No I No Yes
bash Yes Yes No No Yes Yes No No No Yes
cat Yes Yes No No Yes Yes No No No Yes
chgrp_ Yes Yes No No Yes Yes No. No No Yes
chmod Yes Yes No No Yes Yes No. No No Yes.
chown Yes_I Yes_I No I No Yes Yes__INo__I No__I No Yes
chroot Yes_I Yes I No_I No Yes Yes I No__I No I No Yes
emp Yes_I Yes I No_I No Yes Yes I No__I No__I No Yes
Dp Yes_I Yes I No_I No Yes Yes I No I No I No Yes
cut Yes Yes No No Yes Yes No No No Yes
cygpath Yes_I Yes_I No__I No Yes Yes I No__I No_I No ‘Yes
date Yes Yes No No Yes Yes No No No Yes
dd Yes Yes No No Yes Yes No. No. No. Yes.
df Yes Yes No No Yes Yes No No No Yes
iff Yes_[ Yes I No__[ No Yes Yes [No [No I No Yes
dirmame Yes Yes No No Yes Yes No. No No Yes
du Yes_I Yes I No__I No Yes Yes I No__I No_I No Yes
echo Yes Yes No No Yes Yes No No No Yes
grep Yes_I Yes I No I No Yes Yes I/No__I No__I No Yes
expr Yes Yes No No Yes Yes No No No Yes
false Yes_I Yes I No I No Yes Yes__I No I No I No Yes
find Yes Yes No No Yes Yes No No No Yes
fold Yes_I Yes [No I No Yes Yes [No I No [No Yes
gunzip Yes I Yes I No I No Yes Yes No ‘No No. Yes
szip Yes_I Yes I No_I No Yes Yes [No I No__I No Yes
head Yes Yes No No Yes Yes No No No Yes
hostname Yes_I Yes_I No I No Yes Yes I No__I No__I No Yes
kill Yes Yes No No Yes Yes No No No Yes
less Yes_I Yes I No I No Yes Yes I No I No I No Yes
In Yes Yes No No Yes Yes No No No Yes
login Yes_I Yes I No I No Yes Yes I No__I No I No Yes
Is. Yes Yes No No Yes Yes No No No Yes
mdSsum Yes_I Yes_[ No I No Yes Yes [No I No_I No Yes
mkdir Yes_I Yes I No I No Yes Yes I No_I No I No Yes
mount Yes_I Yes _[ No I No Yes Yes___ I No__[.No__I No Yes
mv Yes_I Yes I No I No Yes Yes [No [No I No Yes
awk Yes_I Yes I No I No Yes Yes I 'No__I No I No Yes
nice Yes Yes No No Yes Yes No No No Yes
nt Yes Yes No No Yes Yes No No No Yes
od Yes Yes No No Yes Yes No No No Yes
paste Yes I Yes [No I No Yes Yes ‘No No No Yes
printf Yes_I Yes I No I No Yes Yes [No I No I No Yes
ps Yes_I Yes_I No__I No Yes Yes___[No__I No__I No Yes
pwd Yes_I Yes I No__[ No Yes Yes I No I No_I No Yes
regtool Yes_I Yes I No_I No Yes Yes [/No_I No No Yes
m Yes Yes No No Yes Yes No No No Yes
rmdir Yes Yes No No Yes Yes No No No Yes
sed Yes Yes No No Yes Yes No No No Yes
sleep Yes Yes No No Yes Yes No No No Yes
sort Yes_I Yes I No__I No Yes Yes I No__I No_I No Yes
tail Yes_I Yes_I No__I No Yes Yes I No__I No_I No Yes
tar Yes_I Yes I No__I No Yes Yes I No I No__I No Yes
tee Yes_I Yes I No_I No Yes Yes. No__I No_I No Yes
test Yes_I Yes I No [No Yes Yes I No I No_I No ‘Yes
touch Yes Yes No No Yes Yes No No No Yes
iput Yes_I Yes_I No I No Yes Yes [No I No I No Yes
true Yes Yes No No Yes Yes No No No Yes
iset Yes_I Yes I No I No Yes Yes [No I No__I No Yes
umount Yes Yes No No Yes Yes No No No Yes
we Yes_I Yes I No I No Yes Yes [No I No I No Yes
Table 2
© 2004 Fujitsu Services COMPANY IN CONFIDENCE Page: 37 of 39
FUJ00088104
FUJ00088104
Fujitsu Services Secure Support Role Definitions for SECURENT Ref: RS/REQ/023
Build
Version: 2.0
COMPANY IN CONFIDENCE Date: 18/03/04
‘Support groups at Data Centre User groups at Counters
Commands SSC_I ISD_I MSS I Tivoli Maestro ssc IsD MSS. Tivoli Maestro
‘compreg Yes I Yes I No I No Yes ‘Yes ‘No No. ‘No Yes
disksave Yes Yes No No Yes Yes No No No Yes
dumpel Yes_I Yes [No I No Yes Yes [No I No I No Yes
etmac Yes Yes No No Yes Yes No No No Yes
gelsid Yes_I Yes_I No I No Yes Yes__INo__I No__I No Yes
ill Yes_I Yes I No__I No Yes Yes I No_I No I No Yes
pulist Yes_I Yes I No__I No Yes Yes__I No I No__I No Yes
kill Yes_I Yes [No I No Yes Yes [No I No__I No Yes
robocopy Yes_I Yes I No_I No Yes Yes I No I No_I No Yes
se Yes_I Yes I No_I No Yes Yes [No I No I No Yes
scanreg Yes Yes No No Yes Yes No No No Yes
selist Yes Yes No No Yes Yes No No. No Yes.
SCOP) Yes I Yes I No [No Yes Yes No No. No Yes
showaels Yes_I Yes [No [No ‘Yes Yes I No [No I No Yes
showdisk Yes_I Yes_I No I No Yes Yes___I.No__I No__I No Yes
showgrps Yes_I Yes I No_I No Yes Yes [No [No [No Yes
showmbrs Yes_I Yes I No__I No Yes Yes I No I No_I No Yes
shutdown Yes_I Yes [No I No Yes Yes I No [No I No ‘Yes
sleep Yes Yes No No Yes Yes No No No Yes
tlist Yes Yes No No Yes Yes No No No Yes
xcop) Yes Yes No No Yes Yes No No No Yes
© 2004 Fujitsu Services
COMPANY IN CONFIDENCE
Page: 38 of 39