Service design, build, test & deploy-
ment procedure(s)| Service design, build, test & deploy- |
| :--- |
| ment procedure(s) |
-
มีขั้นตอนที่ได้รับการอนุมัติอยู่ในสถานที่
บันทึกเหตุการณ์บริการ
หลักฐานการใช้งาน
No. Name Audit evidence
WP.16 Service design - Evidence of proper storage and protection
WP.17 "Service design, build, test & deploy-
ment procedure(s)" - Existence of approved procedure in place
Service incident record Evidence of usage| No. | Name | Audit evidence | |
| :--- | :--- | :--- | :--- | :--- |
| WP.16 | Service design | - | Evidence of proper storage and protection |
| WP.17 | Service design, build, test & deploy- <br> ment procedure(s) | - | Existence of approved procedure in place |
| | | Service incident record | Evidence of usage |
Profile reqr. ID ISO/IEC 29110-4-3 requirements ISO/IEC 20000-1:2011
GOVERNANCE PROCESS
P01 Top managementshall define the scope of the service delivery activities. "4.1.1 a)
4.2 (paragraph 1)
4.5.1"
P02 A Service Delivery policy, with information security element(s) shall be created, documented, implemented and reviewed based on the defined scope of the service delivery activities. 4.1.1a) 4.1 .2 4.3.1a) 4.3.1c) 4.3 .2 6.6.1 (paragraph 1)
P03 Responsibilities and authorities which support the Service Delivery policy, shall be assigned, monitored and managed. " 4.1.3 a)
4.1.4
4.5.2 e), f) "
P04 The Service Manager shall review and report to management on actions and achievements against Service Delivery objectives and update plans to achieve the objectives. 4.1.1 a), b), f) 4.1.2d) 4.1 .4 e) 4.5.3 f) 4.5.4.3 (paragraph 1)
P05 Top management shall review policies, processes, procedures and services to confirm compliance and continued relevance to meet changing circumstances or customer requirements. 4.1 .2 c ), f) 4.1.4 b) 4.5 .4 4.5 .5 .2| Profile reqr. ID | ISO/IEC 29110-4-3 requirements | ISO/IEC 20000-1:2011 |
| :---: | :---: | :---: |
| GOVERNANCE PROCESS | | |
| P01 | Top managementshall define the scope of the service delivery activities. | 4.1.1 a) <br> 4.2 (paragraph 1) <br> 4.5.1 |
| P02 | A Service Delivery policy, with information security element(s) shall be created, documented, implemented and reviewed based on the defined scope of the service delivery activities. | $4.1 .1 \mathrm{a})$ 4.1 .2 $4.3 .1 \mathrm{a})$ $4.3 .1 \mathrm{c})$ 4.3 .2 6.6.1 (paragraph 1$)$ |
| P03 | Responsibilities and authorities which support the Service Delivery policy, shall be assigned, monitored and managed. | $\begin{aligned} & \text { 4.1.3 a) } \\ & \text { 4.1.4 } \\ & 4.5 .2 \text { e), f) } \end{aligned}$ |
| P04 | The Service Manager shall review and report to management on actions and achievements against Service Delivery objectives and update plans to achieve the objectives. | 4.1.1 a), b), f) $4.1 .2 \mathrm{~d})$ 4.1 .4 e) 4.5.3 f) 4.5.4.3 (paragraph 1) |
| P05 | Top management shall review policies, processes, procedures and services to confirm compliance and continued relevance to meet changing circumstances or customer requirements. | 4.1 .2 c ), f) 4.1.4 b) 4.5 .4 4.5 .5 .2 |
Profile reqr. ID ISO/IEC 29110-4-3 requirements ISO/IEC 20000-1:2011
MAINTAIN CONTROL PROCESS
P06 Management shall define services and control the service component information. 4.1 .4 a) 4.3.1d) 4.5.2b) 5.2 (paragraph 1, 5) 5.3 j) 6.1 (paragraph 1, 2) 9.1 (paragraph 1,2) 9.2 a)
P07 The Control Manager shall evaluate service changes for approval or rejection based on established criteria and update the service change schedule. 9.2
P08 Service designs shall conform to documented design, build, test and deployment procedures. 5.2 h) 5.3 5.4 (paragraph 1) 9.2 (paragraph 6) 9.2 (paragraph 9) 9.3 (paragraph 4)
P09 Master copies of authorized service components (e.g., hardware, software, documentation, etc.) shall be available and protected. 9.1 (paragraph 8)
P10 The Control Manager shall approve or reject the deployment of a service change based on test results compared to acceptance criteria, customer agreement and service change schedule. "5.4 (paragraph 1)
9.3 (paragraph 5) "
MANAGE RELATIONSHIPS PROCESS
P11 All services offered shall be documented in business terms in one or more service catalogue(s) and made available to appropriate stakeholder groups. "4.3.1d)
5.3j)
6.1 (paragraph 2)
6.1 (paragraph 5)"
P12 Requirements for service delivery between the VSE and its customer(s) and/or supplier(s) shall be agreed, documented, reviewed and updated, as required. 4.1 .4 a) 4.5 .2 b) 5.2 (paragraph 1) 5.2 b) 5.3 b), g) 5.4 (paragraph 1) 6.1 (paragraph 5, 7) 7.1 (paragraph 3, 5) 7.2 c) 7.2 (paragraph 4)
P13 At a minimum, service reports to customers or from suppliers shall be produced for customer satisfaction, service complaints and performance against agreed service measures. 6.1 (paragraph 7) 6.2 7.2 (paragraph 6)| Profile reqr. ID | ISO/IEC 29110-4-3 requirements | ISO/IEC 20000-1:2011 |
| :---: | :---: | :---: |
| MAINTAIN CONTROL PROCESS | | |
| P06 | Management shall define services and control the service component information. | 4.1 .4 a) $4.3 .1 \mathrm{~d})$ $4.5 .2 \mathrm{~b})$ 5.2 (paragraph 1, 5) 5.3 j) 6.1 (paragraph 1, 2) 9.1 (paragraph 1,2$)$ 9.2 a) |
| P07 | The Control Manager shall evaluate service changes for approval or rejection based on established criteria and update the service change schedule. | 9.2 |
| P08 | Service designs shall conform to documented design, build, test and deployment procedures. | 5.2 h) 5.3 5.4 (paragraph 1) 9.2 (paragraph 6) 9.2 (paragraph 9) 9.3 (paragraph 4) |
| P09 | Master copies of authorized service components (e.g., hardware, software, documentation, etc.) shall be available and protected. | 9.1 (paragraph 8) |
| P10 | The Control Manager shall approve or reject the deployment of a service change based on test results compared to acceptance criteria, customer agreement and service change schedule. | $\begin{aligned} & 5.4 \text { (paragraph 1) } \\ & 9.3 \text { (paragraph 5) } \end{aligned}$ |
| MANAGE RELATIONSHIPS PROCESS | | |
| P11 | All services offered shall be documented in business terms in one or more service catalogue(s) and made available to appropriate stakeholder groups. | $4.3 .1 \mathrm{~d})$ <br> $5.3 \mathrm{j})$ <br> 6.1 (paragraph 2) <br> 6.1 (paragraph 5) |
| P12 | Requirements for service delivery between the VSE and its customer(s) and/or supplier(s) shall be agreed, documented, reviewed and updated, as required. | 4.1 .4 a) 4.5 .2 b) 5.2 (paragraph 1) 5.2 b) 5.3 b), g) 5.4 (paragraph 1) 6.1 (paragraph 5, 7) 7.1 (paragraph 3, 5) 7.2 c) 7.2 (paragraph 4$)$ |
| P13 | At a minimum, service reports to customers or from suppliers shall be produced for customer satisfaction, service complaints and performance against agreed service measures. | 6.1 (paragraph 7) 6.2 7.2 (paragraph 6) |
All reported or identified incidents that reduce the quality of or prevent
use of agreed services shall be recorded and managed to closure.| All reported or identified incidents that reduce the quality of or prevent |
| :--- |
| use of agreed services shall be recorded and managed to closure. |
8.1
P15
ทรัพยากรที่มีทักษะ ทั้งภายในหรือภายนอก VSE จะต้องตรวจสอบเหตุการณ์ที่เกิดขึ้นหรือที่อาจเกิดขึ้น โดยมีเจตนาในการฟื้นฟูบริการให้เร็วที่สุดเท่าที่จะเป็นไปได้。
Skilled resources, internal or external to the VSE, shall investigate in-
cidents, actual or potential, with the intent of restoring service as soon
as possible.| Skilled resources, internal or external to the VSE, shall investigate in- |
| :--- |
| cidents, actual or potential, with the intent of restoring service as soon |
| as possible. |
Incidents, actual or potential, with a significant impact on the organiza-
tion shall be investigated to discover root cause and a solution which
will be actioned, if approved, to prevent or minimize future occurrence.| Incidents, actual or potential, with a significant impact on the organiza- |
| :--- |
| tion shall be investigated to discover root cause and a solution which |
| will be actioned, if approved, to prevent or minimize future occurrence. |
8.1 (ย่อหน้า 6)
"Profile
reqr. ID" ISO/IEC 29110-4-3 requirements ISO/IEC 20000-1:2011
PREVENT OR MANAGE INCIDENTS PROCESS
P14 "All reported or identified incidents that reduce the quality of or prevent
use of agreed services shall be recorded and managed to closure." 8.1
P15 "Skilled resources, internal or external to the VSE, shall investigate in-
cidents, actual or potential, with the intent of restoring service as soon
as possible." "4.4.2
8.1"
P16 All steps taken to restore the service shall be documented and agreed. "8.1 (paragraph 4)
8.1 (paragraph 5)"
P17 "Incidents, actual or potential, with a significant impact on the organiza-
tion shall be investigated to discover root cause and a solution which
will be actioned, if approved, to prevent or minimize future occurrence." 8.1 (paragraph 6)| Profile <br> reqr. ID | ISO/IEC 29110-4-3 requirements | ISO/IEC 20000-1:2011 |
| :---: | :--- | :--- |
| PREVENT OR MANAGE INCIDENTS PROCESS | | |
| P14 | All reported or identified incidents that reduce the quality of or prevent <br> use of agreed services shall be recorded and managed to closure. | 8.1 |
| P15 | Skilled resources, internal or external to the VSE, shall investigate in- <br> cidents, actual or potential, with the intent of restoring service as soon <br> as possible. | 4.4.2 <br> 8.1 |
| P16 | All steps taken to restore the service shall be documented and agreed. | 8.1 (paragraph 4) <br> 8.1 (paragraph 5) |
| P17 | Incidents, actual or potential, with a significant impact on the organiza- <br> tion shall be investigated to discover root cause and a solution which <br> will be actioned, if approved, to prevent or minimize future occurrence. | 8.1 (paragraph 6) |
บรรณานุกรม
[1] ISO 9000, ระบบการจัดการคุณภาพ - หลักการและคำศัพท์