Securing Monitoring

This topic provides security information and recommendations for the Oracle Cloud Infrastructure Monitoring service.

Security Responsibilities

To use Monitoring securely, learn about your security and compliance responsibilities.

In general, Oracle provides security of cloud infrastructure and operations, such as cloud operator access controls and infrastructure security patching. You are responsible for securely configuring your cloud resources. Security in the cloud is a shared responsibility between you and Oracle.

Oracle is responsible for the following security requirements:

  • Physical Security: Oracle is responsible for protecting the global infrastructure that runs all services offered in Oracle Cloud Infrastructure. This infrastructure consists of the hardware, software, networking, and facilities that run Oracle Cloud Infrastructure services.

Your security responsibilities are described on this page, which include the following areas:

  • Access Control: Limit privileges as much as possible. Users should be given only the access necessary to perform their work.

Initial Security Tasks

Use this checklist to identify the tasks you perform to secure Monitoring in a new Oracle Cloud Infrastructure tenancy.

Task More Information
Use IAM policies to grant access to users and resources IAM Policies

Routine Security Tasks

After getting started with Monitoring, use this checklist to identify security tasks that we recommend you perform regularly.

Monitoring does not have any security tasks that you need to perform regularly.

IAM Policies

Use policies to limit access to Monitoring.

A policy specifies who can access Oracle Cloud Infrastructure resources and how. For more information, see How Policies Work.

Assign a group the least privileges that are required to perform their responsibilities. Each policy has a verb that describes what actions the group is allowed to do. From the least amount of access to the most, the available verbs are: inspect, read, use, and manage.

For more information about Monitoring policies, see Details for Monitoring.

Basic Policies

Create this policy to allow group AlarmUsers to create alarms (including new topics).

Allow group AlarmUsers to manage alarms in tenancy
Allow group AlarmUsers to read metrics in tenancy
Allow group AlarmUsers to manage ons-topics in tenancy

Create this policy to allow group MetricDevelopers to publish custom metrics.

Allow group MetricDevelopers to use metrics in tenancy

Alarm Access for Groups

Following are common policies to authorize groups to access alarms:

Metric Access for Groups

Following are common policies to authorize groups to access metrics:

Metric Access for Resources

If you want compute instances or other resources to monitor metrics through API calls, then do the following.

  1. Add the resources to a dynamic group using its matching rules.
  2. Create a policy that allows that dynamic group to access metrics.

    For example, see Let instances make API calls to access monitoring metrics in the tenancy.