CyberStrikeus/CyberStrike - Page 160

cis-tomcat101-4-3

Restrict access to Tomcat configuration directory

cis-tomcat101-4-4

Restrict access to Tomcat logs directory

cis-tomcat101-4-5

Restrict access to Tomcat temp directory

cis-tomcat101-4-6

Restrict access to Tomcat binaries directory

cis-tomcat101-4-7

Restrict access to Tomcat web application directory

cis-tomcat101-4-8

Restrict access to Tomcat catalina.properties

cis-tomcat101-4-9

Restrict access to Tomcat catalina.policy

cis-tomcat101-5-1

Use secure Realms

cis-tomcat101-5-2

Use LockOut Realms

cis-tomcat101-6-1

Setup Client-cert Authentication

cis-tomcat101-6-2

Ensure SSLEnabled is set to True for Sensitive Connectors

cis-tomcat101-6-3

Ensure scheme is set accurately

cis-tomcat101-6-4

Ensure secure is set to true only for SSL-enabled Connectors

cis-tomcat101-6-5

Ensure 'sslProtocol' is Configured Correctly for Secure Connectors

cis-gcp-foundations-1-1

Ensure That Corporate Login Credentials Are Used

cis-gcp-foundations-1-10

Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days

cis-gcp-foundations-1-11

Ensure That Separation of Duties Is Enforced While Assigning KMS Related Roles to Users

cis-gcp-foundations-1-12

Ensure API Keys Only Exist for Active Services

cis-gcp-foundations-1-13

Ensure API Keys Are Restricted To Use by Only Specified Hosts and Apps

cis-gcp-foundations-1-14

Ensure API Keys Are Restricted to Only APIs That Application Needs Access

cis-gcp-foundations-1-15

Ensure API Keys Are Rotated Every 90 Days

cis-gcp-foundations-1-16

Ensure Essential Contacts is Configured for Organization

cis-gcp-foundations-1-17

Ensure Secrets are Not Stored in Cloud Functions Environment Variables by Using Secret Manager

cis-gcp-foundations-1-2

Ensure That Multi-Factor Authentication is Enabled for All Non-Service Accounts

cis-gcp-foundations-1-3

Ensure That Security Key Enforcement is Enabled for All Admin Accounts

cis-gcp-foundations-1-4

Ensure That There Are Only GCP-Managed Service Account Keys for Each Service Account

cis-gcp-foundations-1-5

Ensure That Service Account Has No Admin Privileges

cis-gcp-foundations-1-6

Ensure That IAM Users Are Not Assigned the Service Account User or Service Account Token Creator Roles at Project Level

cis-gcp-foundations-1-7

Ensure User-Managed/External Keys for Service Accounts Are Rotated Every 90 Days or Fewer

cis-gcp-foundations-1-8

Ensure That Separation of Duties Is Enforced While Assigning Service Account Related Roles to Users

cis-gcp-foundations-1-9

Ensure That Cloud KMS Cryptokeys Are Not Anonymously or Publicly Accessible

cis-gcp-foundations-2-1

Ensure That Cloud Audit Logging Is Configured Properly

cis-gcp-foundations-2-10

Ensure That the Log Metric Filter and Alerts Exist for Cloud Storage IAM Permission Changes

cis-gcp-foundations-2-11

Ensure That the Log Metric Filter and Alerts Exist for SQL Instance Configuration Changes

cis-gcp-foundations-2-12

Ensure That Cloud DNS Logging Is Enabled for All VPC Networks

cis-gcp-foundations-2-13

Ensure Cloud Asset Inventory Is Enabled

cis-gcp-foundations-2-14

Ensure 'Access Transparency' is 'Enabled'

cis-gcp-foundations-2-15

Ensure 'Access Approval' is 'Enabled'

cis-gcp-foundations-2-16

Ensure Logging is enabled for HTTP(S) Load Balancer

cis-gcp-foundations-2-2

Ensure That Sinks Are Configured for All Log Entries