Technical requirements - Information Technology Services

More documents

Recommendations

Info

5b What is the file naming convention needed to inform design solution, and based on customer requirements 6 Technical/Operational 6a 6b Service Availability (pick one) ● Tier 3 24x7x365, excluding maintenance window, incident response, and cold backups, see also 7b ● Tier 2 MF 77, excluding campus holidays or closures, maintenance window, incident response, cold backups, see also 7b ● Tier 1 MF 85, excluding campus holidays or closures, maintenance window, incident response, cold backups, see also 7b Maintenance Window (which may be defined to occur outside of business/service hours): 1. Frequency (pick one or more): Daily, Weekly, Monthly, Qrtly, Yearly 2. Day of Week (pick one or more, must be within Service Availability Tier): MTuWThFSaSu 3. Time of Day: based on Tier 1 or 2 Service Availability; if Tier 3 pick time range (must start after, and finish before) 4. Exception: Security patches will be applied
outside the regular maintenance window, depending on risk/vulnerability, and/or as directed by ITS Security or campus Information Security Officer (ISO) 6c 6d Incident/Response: 1. Response within eight business hours of receipt based on Service Availability Tier (see #6a, above), or Service Level Agreement (see #7, below) 2. Repairs may be effected during business hours and pending outage tolerance of steward ○ Mean Time To Repair (MTTR) is dependent on completion of root cause analysis, identification and execution of mitigation options, may be limited by vendor maintenance agreement 3. Repairs may be shortterm (e.g., bring system/service online, but additional repair work is required, and will be scheduled as needed) SHAWN TO WORDSMITH Privileged Access (Application,
Page 1 and 2: High Level Requirements Technica
Page 3 and 4: ● ● ● (HIPAA, restricted) Use
Page 5 and 6: ● data and directory structures.
Page 7 and 8: ● Use case (example): Group pwd f
Page 9: How do you support external users
Page 13 and 14: ● ○ Hardware refresh occurs on
Page 15 and 16: ● (dev/test and prod) ○ If "nec
Page 17 and 18: notification of pruning Data Securi
Page 19 and 20: available) 7b 7c 7d Utilize common
Page 21 and 22: engagement (e.g., before design, be
Page 23 and 24: account activation/revocation) ●
Page 25 and 26: and can RWXD/CRUD on dev/test and t
Page 27 and 28: 3 f Anonymous file drop/retrieve
Page 29 and 30: 2. Day of Week (pick one or more, m
Page 31 and 32: ● ○ Hardware refresh occurs on
Page 33 and 34: ○ ○ (e.g., use as an alternativ
Page 35 and 36: kup.html for default term) ○ Cons
Page 37: Assumptions 1. Business office will

Technical requirements - Information Technology Services

Create successful ePaper yourself

Delete template?

Save as template?