This screen is used to record the security code associated with a particular S.W.I.F.T. message type/tag code combination. There are currently six security codes available for use. These security codes are used in conjunction with the access group functionality to control who can update specific fields of S.W.I.F.T. messages. See "Defining Access Security" in the Guide to Setting Up for details of access groups.
Particular uses of this message security feature are:
• If you set the same security level for a number of message type/tag code combinations, you can allow a user to update a number of fields
• If you do not apply a particular security level to a message type/tag code combination, then any user that can perform a change on the Settlement Message Review and Repair (MESSR) screen will be able to update them
• If you set a security level on a message type/tag code combination but do not authorise it for any access group, you can prevent a field from being updated by any user
The recommended procedure for setting the update protection on messages is as follows: • Identify those users that need to add messages using the Settlement Message Add (MESSA)
screen and identify the message types that they will need to add
• Identify those users that need to repair messages using the Settlement Message Review and Repair (MESSR) screen. Identify the message type and tag fields that each user is to be allowed to update. For example on a MT103 (EMU Customer Transfer) message, you may want a user to be able to update the Sender to Receiver Information field (tag code 72). • Highlight any message types and tag fields that no user must be allowed to update. For example on a MT103 (EMU Customer Transfer) message, you may not want any user to update the Amount field (tag code 32A).
• You now have details of the updating that is to be allowed for each message type and the users that are to perform the updates. You must now analyse the information according to the following rules:
- Determine the access groups of the users who will be performing the
updates/additions, so that you can see which access groups will need to be updated. It may be that you will have to add new access groups or change the access groups to which certain users are attached.
- If a message type/tag code combination can be added or updated by anyone it must not be allocated a security code.
- There are six security codes available (identified by numbers 5 through 10). - If only specific users are to be allowed to add or update a message type/tag code combination (for example, MT103/72), then it must be allocated a security code. - If different message type/tag code combinations (for example, MT103/56a and MT103/57a) are to be added or updated by the same group of users, then give them the same security code.
• Use the Security for SWIFT Tag Codes (STAGA) screen to set the security level identified for each message type/tag code combination for which adding/updating is to be restricted. For example, set a security level of 6 to the Sender to Receiver Information field (tag code 72) of the MT103 (Customer Transfer) message type.
Static Data
2–22 3937 0366–930
• Amend the access groups of the users who are to add or repair messages. For full details of how to set up/maintain access groups, see "Setting Up Access Groups" in the Guide to
Setting Up. Using the example above, if the operation number of the Settlement Message
Review and Repair (MESSR) screen is set to 111, then you could authorise operations 11103 (change) and 11106 for an access group named SETTLE2 using the Access Group
Authorisation (ACCES) screen. All users in access group SETTLE2 would then be able to update the Sender to Receiver Information field of Customer Transfer messages. Users in the SETTLE2 access group would also be able to update any other message/field combinations that have a security level of 6.
If the update of a tag field (such as, tag code 72) is to be restricted for all message types, then use the Security for SWIFT Tag Codes (STAGA) screen to set up a security level for a combination of the tag code and a 'Blank Message' (MT999) message type. This sets the security level for the tag code on all message types.
If a user is only to be allowed to add or update those tag code/message type combinations that can be updated by any user, then give the user update access to the Settlement Message Review and Repair (MESSR) screen using the standard security features described in "Defining Access Security" in the Guide to Setting Up. Do not give the user update access to any of the fields controlled by the use of the Security for SWIFT Tag Codes (STAGA) screen.
Notes: The Settlement Message Add (MESSA) screen and the Settlement Message Review and Repair (MESSR) screen will have different operation numbers. Therefore, if a user is to be allowed to add messages using the Settlement Message Add (MESSA) screen and repair messages of the same type on the Settlement Message Review and Repair (MESSR) screen, then separate entries will be required for the two operations in the access group.
3937 0366-930 3–1