Professional Documents
Culture Documents
1 SecurityManagementSystem
1 SecurityManagementSystem
Warning: This document, is protected by copyright law and international treaties. No part of this
document may be reproduced or transmitted in any form or by any means, electronic or mechanical,
for any purpose, without the express written permission of TEMENOS Holdings NV Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and
criminal penalties, and will be prosecuted to the maximum Copyright © 2004under
extent possible TEMENOS HOLDINGS
applicable law.” NV
Information in this document is subject to change without notice.
¾ Secrecy
¾ Funds transferred correctly
• Control
¾ Different functions (Maker – Checker)
¾ Individual users
¾ Different departments
• Audit
¾ Internal & External
• Reporting
¾ MIS and Statutory
TREASURY Authorizer
Audit
or
Authorizer Queries
Transaction Input
Security Management System
RDBMS
APPLICATION LOGIC
COB
Accruals
Validation Maturity Control
Reporting
AUTHORIZED Revaluation
UNAUTHORIZED
Static Data
Risk Management Messages/Clearing Accounting
Product
Interest Rates Credit Risk Print General Ledger
Commissions Market Risk Debits/Credits
SWIFT SID Interface
Currency
etc...
User profiles
Authorizations
System Control
Overrides
Application
Sign On Name
Function
User profile
Data
Password
Time
Sign On Name
Password
Sign on Name
Security
Violation
Password
Sign on Name
Security
Violation
Password
Sign on Name
Too
Security
many
Violation
attempts
Password
Security Administrator
PASSWORD.RESET
¾ User Initiated
¾ An Inactive Session
¾ Hardware Failure
¾ User ID
¾ User Name
¾ Sign On Name
¾ Classification
¾ Company Code
¾ Department Code
¾ Password Validity
¾ Start time
¾ End time
¾ Attempts
¾ Company restriction
¾ Application
¾ Version
¾ Function
¾ Field Number
¾ Data Comparison
¾ Data From
¾ Data To
¾ Security Mgmt L
¾ Application Log
¾ Function Id Log
¾ Override class
¾ Attributes
Login as the same user and check whether you are able to
do a auditor review
User1 Teller
User2 Teller
USER.SMS.GROUP
User3 Teller
User4 Teller
¾ Non Blocking
Any user can approve the override
¾ Blocking
Only users with proper authentication are allowed
to approve the override
Historical activity
¾ This table will allow the user to specify for each T24 Application,
which field number(s) identify a 'Customer' or 'Account' field.
¾ Used by the Security Management System to control EXTERNAL
type users for whom specific Customer and account number(s)
have been specified on the profile
¾ An override will need to be approved when CUSTOMER.FD field
input is not of a 'CUS' type and ACCOUNT.FD field input is not of
‘ACC’ ‘ALL’ or ‘ANT’ type.
Restricted access
to records of
Customer(s)
Restricted Access
to Branch,
Applications and
functionalities