Resolved! User is always getting access to API Key

I am inserting a user into "Prisma Cloud" through API (https://api.prismacloud.io/user) with the request body as,

var userDetails = {
"email": email,
"firstName": firstName,
"lastName": lastName,
"timeZone": "America/Los_Angeles",
"roleId": <role id of sys

Resolved! RQL - display all VPC's, except DEFAULT, that do not have FlowLogs

Hello all.

New to RQL.  I have the below RQL that identifies DEFAULT VPC's;

config where cloud.account IN ( 'AWS_EBU_Networked_Prod_DR_DA_01' ) and api.name = 'aws-ec2-describe-vpcs' AND json.rule = isDefault is true

I have the below RQL that shows al

Resolved! Prisma Cloud - Azure Scan Frequency and Config change detection

Hi, I'm using the Prisma Cloud (previously Redlock). Is there a way I can change the frequency of the scans to check for misconfiguration. Also where can I check the current frequency. Does the scan run every hr or every 24 hr. Is it the same for AWS

Resolved! Not able to access API with token

I have Access Key and Secret Key, with the help of these we are getting Token and we are trying to use this Token to access list of cloud account (https://api.prismacloud.io/cloud) from the API Docs (api.docs.prismacloud.io/v4.2.1/reference) and from

Resolved! Prisma/Redlock API documentation

Hi team.  

Can someone share the URI for Prisma Cloud API REST documentation please.

(Can't find it anywhere)