| Verify only the runtime privileges needed for the current vCenter state, on either Oracle or Microsoft SQL Server, is assigned. |
Verify that the following permissions are granted to the vCenter user in the vCenter database.
GRANT ALTER ON SCHEMA :: to ;
GRANT REFERENCES ON SCHEMA :: to ;
GRANT INSERT ON SCHEMA :: to ;
GRANT CREATE TABLE to ;
GRANT CREATE VIEW to ;
GRANT CREATE Procedure to ;
For SQL, verify that the following permissions are granted to the user in the MSDB database. Note that the msdb database is used by SQL Server Agent for scheduling alerts and jobs.
GRANT SELECT on msdb.dbo.syscategories to ;
GRANT SELECT on msdb.dbo.sysjobsteps to ;
GRANT SELECT ON msdb.dbo.sysjobs to ;
GRANT EXECUTE ON msdb.dbo.sp_add_job TO ;
GRANT EXECUTE ON msdb.dbo.sp_delete_job TO ;
GRANT EXECUTE ON msdb.dbo.sp_add_jobstep TO ;
GRANT EXECUTE ON msdb.dbo.sp_update_job TO ;
GRANT EXECUTE ON msdb.dbo.sp_add_category TO ;
GRANT EXECUTE ON msdb.dbo.sp_add_jobserver TO ;
GRANT EXECUTE ON msdb.dbo.sp_add_jobschedule TO ;
For Oracle, verify that the following permissions (or DBA role) are granted to the user.
grant connect to
grant resource to
grant create view to
grant create materialized view to
grant execute on dbms_job to
grant execute on dbms_lock to
grant unlimited tablespace to
If the runtime privileges are not configured per the above guidelines, this is a finding.