October '23 Updates
  • 28 Feb 2024
  • 1 Minute to read
  • PDF

October '23 Updates

  • PDF

Article summary

Prisma Cloud DSPM released the following updates in October '23.

NEW FEATURES


PagerDuty Integration

It is now possible to effortlessly create PagerDuty tickets directly from Prisma Cloud DSPM Risk Findings.

  • Inclusive Ticket Details: Each ticket includes comprehensive risk information and remediation guidance.
  • Tracking Capabilities: Created tickets are seamlessly linked from Prisma Cloud DSPM and can be tracked within PagerDuty.

For further information refer to Integrate Prisma Cloud DSPM with PagerDuty


Integrate an Amazon SNS topic with Prisma Cloud DSPM

This feature enables you to integrate an Amazon SNS topic with Prisma Cloud DSPM.

  • Empower your data security teams to leverage SNS/SQS in order to automate workflows within AWS, based on notifications from Prisma Cloud DSPM.

For further information refer to Integrate an Amazon SNS topic with Prisma Cloud DSPM


Enhanced notification filtering with Cloud and Prisma Cloud DSPM Tags

It is now possible to filter email, Slack, webhook, Torq, and SNS notifications using tags.

This advanced capability allows for a more precise dissemination of notifications, ensuring that the right individuals receive the most pertinent information.


PRODUCT UPDATES

Permission update in Azure

We have introduced a new permission update in Azure:
Microsoft.Network/networkSecurityGroups/securityRules/write
This permission is limited to the Prisma Cloud DSPM resource group.

With this permission, Prisma Cloud DSPM can modify the Network Security Group (NSG) to establish outgoing SMB (port 445) connections to on-premises file shares for classification purposes.


Enhanced logic for 'Open to World' S3 bucket identification

We have enhanced the evaluation process for identifying 'Open to world' S3 buckets to ensure improved accuracy. This update now excludes listing permissions on buckets granted via bucket Access Control Lists (ACLs), which do not provide access to the objects within. Consequently, if any public objects are identified within private storage and are deemed sensitive, a corresponding 'Sensitive public object in private storage' finding is generated. Please be aware that this modification may impact risk assessments related to the 'Open to world' filter.


Was this article helpful?