Application Development on Power System (IBM i )

1. Application Development on Power System (IBM i) Application Development on Power System (IBM i) School of Software Engineering Tongji University HUANGJie

2. Syllabus 2014/11/27 2

3. Unit 2 IBM i Administration ABC Chapter 6 Security, Storage & Restore Management

4. Outline • 信息安全基础 • System i安全设计 • 访问控制(Access control) • 资源安全(Resource Security) • 管理控制(Administrative Control) • 备份与恢复 • 备份介质 • 备份示例 • 备份面临的挑战 • 备份策略 • 恢复示例 • 课堂练习

5. Information Securityis the protection of information assets from accidental or intentional (but authorized) disclosure, modification, or destruction and from inability to process that information. Information Security Information Forms • Written on paper • Stored electronically • On disks of server, notebooks, … • Backup medias • Transmitted by post • Films • Spoken word

6. Threats • Force majeure risk(不可抗力) • Organizational deficiencies • Human mistakes • Technical problems • Intentional actions

7. Security Threats and Business Risks • Unauthorized use of resources • Inappropriate disclosure of information • Modification or destruction of information • Denial(拒绝) of service • Failure of accountability(问责)

8. What is Security?

9. Security concepts and relationships value Owners wish to minimise impose to reduce Countermeasures 对策 that may possess that may be reduced by Vulnerabilities 漏洞 may be aware of leading to that Threat agents exploit risk give that increase to rise to threats assets to wish to abuse and/or may damage Source: Common Criteria for Information Technology Security Evaluation, Part 1: Introduction and general model

10. Basic Components of Computer Security Confidentiality Integrity Availability

11. Some Other Terms Frequently Used • Authentication(身份认证): when a person logs on to a system, authentication means checking and verifying the identity of the person logging on. The term is also used where the identity of IT components or application is checked. • Authorization(授权): authorization entails checking whether a person, IT component or application has permission to carry out a particular action. • Data protection: data protection refers to the protection of person-related data against misuse by third parties (not to be confused with data security). • Data security: data security refers to the protection of data in relation to the pertinent confidentiality, availability and integrity requirements. Another term for this is "IT security". • Data backup: during a backup, copies of existing data sets are created to protect against loss of data. • Penetration testing(渗透性测试): a penetration test is a deliberate, normally simulated, attempted attack on an IT system. It is used to check the effectiveness of existing security measures. Source: Federal Office for Information Security (BSI), IT Security Guidelines.

12. IT Security Costs Risks

13. The Main Ingredients of Success • Common sense • Well-thought out organizational procedures • Reliable, well informed staff who independently and expertly observe security requirements in a disciplined manner • Creation and implementation of an effective IT security concept does not have to be prohibitively expensive. The most effective safeguards are surprisingly simple and often do not actually cost anything! * Source: Federal Office for Information Security (BSI), IT Security Guidelines.

14. Common Sources for Security Problems • Lack of resources • Tight budgets • Increasing complexity of IT systems • Uneducated staff • Lack of awareness of potential problems • Undocumented security objectives • Standard settings of the manufacturer

15. Security is not a static condition but an ongoing process • Most of the tasks have to be repeated regularly • Updates of anti-virus software or firewall software • Monitoring and Maintaining IT Security • Security checks • Security Policies (out of date, incomplete or not practicable?) • Log files? • Using independent experts? • New Security threats • New Standards • Should be considered at the start of each project • Application development • New software deployment

16. Aspects of Security Policies • Risk Analysis • Assets (IT systems, data, know-how, etc.) • Evaluation of threats • Probability of security incident • Business and IT Requirements • Organizational charts • Password Rules • Application (“need to use”) • Data security (“need to know”) • User Roles • Network Security • Business Contingency(意外事故) Plan

17. Security Policies 1. General security objectives as organization‘s goals 2. Detailed security objectives, technical requirements and associated safeguards 3. Security requirements formulated in product settings Easier to update!

18. Outline • 信息安全基础 • System i安全设计 • 访问控制(System iAccess control) • 资源安全(Resource Security) • 管理控制(Administrative Control) • 备份与恢复 • 备份介质 • 备份示例 • 备份面临的挑战 • 备份策略 • 恢复示例 • 课堂练习

19. System i Access Control

20. Access control rules are implemented to determine the access privileges of a subject – a person – to an object, such as a file or other system resource.

21. Physical Control

22. Types of Physical Controls • Preventive controls • used to prevent unauthorized access to computing equipment • Examples: • badge systems • biometric access controls • double door systems • fences • locks and keys • security guards • Detective controls • alert security and system personnel to events that are damaging to the information system or system data • Examples: • alarms and sensors • closed-circuit television (CCTV) • motion detectors • smoke and fire detectors

23. Physical Access Control

24. System Keylock*

25. Technical Access Control

26. Types of Technical Control • Preventive technical controls • protect software resources from unauthorized access and modification, include access control software • Examples: • antivirus software • library control systems • encryption • Detective technical controls • alert system administrators to system intrusion or attempted intrusion. • Examples: • Audit trails • monitor network activity and uncover instances of unauthorized system access, attempted access by unauthorized parties, and breaches of system security policy. • Intrusion detection systems (IDSs) monitor user activity. • can terminate a user's session if that user's activity violates the system security policy

27. System-level Security

28. QSECURITY

29. Security System Values

30. Security Wizard and Planner eServer Security Planner: http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/secplanr/securwiz.htm

31. Identification and Authentication鉴别与身份认证

32. User Profile No need for a passwd file!

33. Group Profiles • Allows users with similar jobs to share permissions without having to share the same password • Should choose a naming convention which makes groups easily recognizable • Create with No password (sign-on not allowed) • Users can be a member of up to 16 group profiles • Should assign groups in order of use

34. Initial Program and Menus Sign-On Display User signs on with user password and user name. Initial Program Initial program (if any) in user profile is called. Initial Menu Initial menu in user Profile or *SIGNOFF is called. Signoff

35. Limited Capabilities

36. New User – Capabilities – Privileges

37. Defining Roles

38. IBM Supplied User Profiles

39. Internet User and Validation Lists Validation lists (*VLDL) • are lists of Internet user names and passwords used in conjunction with an authentication protocol type to limit access to server resources • validation lists are case-sensitive and reside in iSeries libraries • cannot be used as user profiles for executing a job on OS/400

40. Service Tools Dedicated service tools (DST) and system service tools (SST) are both used to access service tools and service functions. DST is available when the Licensed Internal Code has been started, even if i5/OS has not been loaded. SST is available from i5/OS. Service tools are used to do any of the following: • Diagnose server problems • Add hardware resources to the server • Manage disk units • Manage logical partition (LPAR) activities, including memory • Review the Licensed Internal Code and product activity logs • Trace Licensed Internal Code • Perform main storage dumps • Manage system security • Manage other service tools user IDs • …

41. SST/DST User Profiles

42. HMC User Roles HMC HMC • Task roles define what tasks an HMC account may perform • One role is assigned to each user account when the user account is created • Set of predefined user roles can be customized

43. Resource Security

44. User Owned Objects • Each object has one owner • When an object is created, an owner is assigned. The ownership may be transferred later • The owner initially has all object and data permission • The authority may be removed, but the owner may grant any authority back to himself at anytime • It is not possible to delete a user who owns objects. Two solutions are offered: • Transfer ownership • Delete owned objects

45. QDFTOWN • QDFTOWN is an IBM-supplied user profile used when: • An object has no owner • The object ownership might pose security exposure • The object ownership is assigned to QDFTOWN in the following case: • The owning profile becomes damaged and is deleted. The RCLSTG command assigns ownership of objects to QDFTOWN • An object is restored and the owner profile does not exist • A program that needs to be created again is restored, but program creation is not successful • The maximum storage limit is exceeded for the user profile that owns an authority holder that has same name as file being moved, renamed, or whose library is being renamed • Consider the following recommendations: • QDFTOWN should not normally own objects • Ownership can be transferred with the WRKOBJOWN command or by iSeries navigator

46. Specific Object Permissions

47. Object Management Permissions

48. Data Permissions

49. Commonly Used Permissions

50. Specifying Specific Authority for Objects In the Integrated File System • *RWX: object operational authority, and all the data authorities • *RX: object operational authority, read and execute • *RW: object operational authority, read add, update and delete • *WX: object operational authority, add, update, delete and execute • *R: object operational authority and read • *W: object operational, add, update, and delete • *X: object operational and execute • *EXCLUDE prevents access to object