alright learners, we all less than 6.4 additional service operations and processes. Alright, so are learning objectives. In this video, we will cover additional service operation processes as well as the key concepts of the event types and fulfillment requests.
Alright, so access management, right so access management. It grants the authorized users the right to use this service while preventing access to non authorized users. So the purpose does not extend to determining which users require access to services and data. They only enforces those decisions on a daily basis,
so excess management must operate within the policies and actions to find
by the service strategy in the service design phases. So that's including the information security management process.
So when we look into the objectives of access management, access management is a process which can be initiated by a service request, right. So manage access to a service based on policies and actions define in the Information Security Management, which you can see in the service design so efficiently
respond to the request by granting access to services,
changing access rights or restricting access, ensuring that the right that the right being provided or changed are properly annotated and granted. And then you can oversee access to services and to ensure the rights are being provided and not improperly being used. Okay,
so when we start going into the basic concepts of
access management, the point in terms to take away up here is definitely the access, right? So that's the level and extent of the functionality of its service users whose are entitled. And then you go into the identity, which is the information that is uniquely distinguishes a user or person or role.
And then you have your rights and your privileges,
which is the settings which such as, like rewrite, execute that a user is granted to have. And then you have your service groups, of course, is a set of services used by a user or group, and then your directory services, which is a specific tool used to manage
And then, of course, you already aware of our CIA, which is our confidentiality, our integrity and our availability. Now, those are definitely still important terms, toe always taking consideration when we are doing our information security management as well as these these processes. Okay,
so when we started looking into what is the scope of the access management right? So the access management enables the organization to manage the confidentiality and the availability and integrity of the organization data, intellectual property. So that's going from the information's security Management defines in that policy.
So access management
ensures that users are given the right to use the service at agreed times so that availability management ensures that service availability. And then you have the access management where it's executed by all technical and application management functions, so that the access management can be initiated by a service request
in the service deaths or the I T. Operation management can provide a single point of coordination within their
And then we start looking into what is out of scope, right? So deciding who should have the right to use that service and that, um, responsibility of strategy and design faces so notably information security, information management as well, and then ensuring the availability of that service.
Now that's the responsibility of them,
the availability management. So that is out of scope of the access management.
so then we go into the event management process now, the purpose of this particular is more to manage events throughout their life cycles by detecting events and making sense of them and determine the appropriate control action. So to provide the basis of the operation of monitoring and control. And
it can be used to all for automating normal operations as well detecting early warning signs and failures of the sea ice.
So the purpose of it event management processes to ensure that every service provider has that ability to manage events through the life cycle so the process can be can ensure that the service provider is approaching event detection or correlation or a response management that could be proactively or plan in the planning, the plant manner. Okay,
so the part in terms is what is the event?
So is there any change of state that is significant for the management of a C I or I t service?
And then the objectives of the information the event management process when we start looking to the objectives of it, you know, is a change of events. Events can require I t operation personnel to take action and often resulting events being logged.
So the event is a detectable and discernible occurrence that is significant
for the management of I t. Infrastructure or I t service.
but when we started looking into here, you know, you're determining you to take the significant chances of the state of of the sea ice, and you start noting, I tell list the following objectives for the event management process as far as you know, determining the appropriate
control actions, the responses or providing those trigger to initiate other operational processes.
And also to provide the means to compare extra performance against designs in tow to provide the basis of service, insurance and reporting, which is crucial to the event management process.
So when you look into the scope of the event management, so that's more so of a can support many activities in the service providers environment. So you have the configuration items,
right? So that's the CIA that we talked about monitoring operation of states and operating the updating those those statuses software lights and since
monitoring and environmental conditions and security monitoring. So those air to the tech intrusions and fire and smoke protections okay,
and then you would go into the basic concepts of event management, and we look into those more of the alert in the event types. So the Lord is actually just a warning. That threshold has been breached, something that has changed or a failure has occurred. And then you go into the vent types, which is informational, does signify regular operations.
Then you have warnings that signify unusual operations that you may need to look into later.
And then you have your exceptions, which more of signifies the abnormal operations. Okay,
so when we look into the basic concepts even further so, as you see indicates of information that could be used by trending analysis and then the warning event, since indicating early warning information and then exceptions events indicating abnormal situations or failures that require additional follow up
request fulfillment process and the purpose of that. So so, due to the wide range of service invited environments and services, the purpose is to Maine to manage life's like of all service requests from users. So the important terms to take care is the service request is a request from a user for information or advice
for standard change or access to in service.
so objectives of a request fulfillment. So those objectives for the request fulfillment is more in alliance to request can be broken down into a series of steps that are stored as a request from request models in the S kms. So while some
or may may let service requests be handled through their incident management processes and tools they need to be, they need to be conscious of the fact that whereas the incident is
unplanned, disruption to the business service request is something that can and should be planned for. So you handling efficient handling of those requests service and deliver those components of required services to their business
in the scope of requirements. Of course, that sometimes handled through the independent requests fulfillment, required processes and sometimes handled through the incident management and process tools.
So in summary, less than 6.4 touched on the key concepts. The process is the access management event management event types and request fulfillment.