👀 AI spy with my little eye... Plerion's new AI-powered remediation feature ✨ 🚀 

The TL;DR

Pleri (our little astronaut) is getting smarter with generative AI! Our new AI-powered remediation feature provides actionable recommendations based on your environment and step-by-step instructions to help you understand and resolve your issues.

Try out the new AI feature today! Simply click on one of your findings under the Findings tab and select the Remediation by AI tab. 

Let us know what you think of this new feature! You can also read more about it here. Please note that using this feature will consume Plerion units.

It’s not a risky choice to improve our risk score algorithm – and that’s exactly what we did.

The TL;DR

We have enhanced the Plerion Risk Scoring algorithm to provide a more accurate, reliable and comprehensive assessment of your assets, integrations and risks. Our algorithm more precisely weighs publicly accessible workloads and vulnerabilities and includes a new banding system that presents a more accurate asset risk score.

The new Plerion algorithm is live! Hop onto the Plerion platform, enhance your security, and see your risk scores improve today! We are continuously improving our product for you, so please give us your feedback.

Give us your feedback!

To dive deeper into the technical details and changes, head over to our Resource Center!

Cut through the noise and focus on the 1% of risks that really matter.
 
Our advanced engine analyses multiple data sources and delivers clear,
actionable insights, so you can focus on what truly matters.

We begin with checking for one of the most commonly exploited scenarios -
Unauthorised access to data in an S3 bucket because it is publicly readable
from the Internet. 

Head to "Risks" from the main menu to see if you have any
buckets that require attention.

We're just getting started! Please share your experiences and feature
requests with us from the link on the risks dashboard.

Entitlements Analyzer helps customers with answering the crucial question of Who has access to what.

This powerful tool gives unparalleled insights into cloud entitlement access and permissions. Visualize access relationships, analyze permissions in detail, and take control of your cloud environment's access permissions like never before! 

Look at this short video to see how you can get started.

Effortlessly track all events associated with your assets. 

Previously, customers were not able to see who made what changes directly on an asset.

With Plerion Cloud Detection and Response (CDR) integration, customers can now see WHO performed WHAT action, WHEN, and from WHERE, providing invaluable insights into your asset management.

Getting started with Asset Event History is simple. Once CDR integration has been set up, navigate to the asset details view and click on the Event History tab. 

We’re excited for you to experience the power of Asset Event History. See a quick video on this new feature.

We Value Your Feedback Your input fuels our innovation. After trying out the new integration, please rate your experience below or contact us directly through support@plerion.com or our in app live chat feature.

We're excited to announce a new integration for Plerion customers: Direct vulnerability management within your Jira Security projects!

This feature allows your team to receive, track, and triage software vulnerabilities without ever leaving Jira.

Key Features:

• Automated Vulnerability Updates: As soon as Plerion detects new vulnerabilities, they are automatically pushed to your Jira Security page.
• Streamlined Workflow: By reducing the need to switch between tools, teams can address vulnerabilities faster and more efficiently.

Getting Started is Simple:

1. Install the Plerion Security App from your Jira toolchain.
2. Configure the integration using our step-by-step guide in the Resource Center: Integration > Outbound > Jira Security.

For a quick walkthrough, watch our short video tutorial on setting up and using this new feature.

We Value Your Feedback Your input drives our innovation. After trying out the new integration, please rate your experience below or contact us directly through support@plerion.com or our live chat feature.

In Plerion, an attack path is a path that exists from the internet to a vulnerable (Low, Medium, High, or Critical vulnerability) workload that could have access to sensitive data directly or via lateral movement.

In our mission to simplify cloud security, we have improved our analysis of attack paths. Attack paths now need to meet more specific criteria to ensure any remediation effort is spent on the top 1% of risk in your cloud environment. 

Low and Medium severity vulnerabilities will no longer be included in the analysis of an attack path. An attack path will only be shown if a path exists from the internet to a vulnerable (High or Critical vulnerability) workload, thereby reducing any noise from medium and low vulnerabilities.

If you would like to leave feedback on this feature, please use the faces below. Alternatively, don't hesitate to contact us at support@plerion.com or via our live chat within the console. 

Plerion is excited to announce the expansion of our Risk Score feature to include Azure assets. This enhancement provides you with a powerful metric to quickly assess the level of risk associated with each Azure asset and configure alerts based on that level.

For Azure organizations managing thousands or even tens of thousands of assets, pinpointing the riskiest ones can be challenging.

The Plerion Risk Score is a number between 1 and 10 which we assign to assets, with assets approaching 10 being deemed as the riskiest. With Azure Risk Scores, busy users can effortlessly view, filter, and set alerts for their Azure assets' risk levels.

There's nothing to enable – Plerion will automatically assign a Risk Score to your Azure assets if we detect failed findings.

Jump onto the platform today, and once your next Azure integration run has been completed, look for assets with a high risk score and start your triage work to address their risk.

If you would like to leave feedback on this feature, please use the faces below. Alternatively, don't hesitate to contact us at support@plerion.com or via our live chat within the console. 

Manage the CDR findings you see by setting exemption rules based on the principal creating the finding.

Certain legitimate activities may be performed regularly by known actors, leading to findings you do not want or need to see.

Customers can now set exemption rules for CDR detections so they are not alerted to expected behaviors. Customers can visit the detection settings for CDR detections to add exemption rules or use the action button on an existing finding to exempt any future findings by that principal. 🎥 See a short video here.

What other kinds of exemptions would you like to see for CDR detections? If you would like to leave feedback on this feature, please use the faces below. Alternatively, don't hesitate to contact us at support@plerion.com or via our live chat within the console. 

Understand the Principal (User) events surrounding a CDR finding with Principal Event History. 

When investigating a new CDR finding, without the context surrounding it, it can be hard to discern whether the intention behind it was legitimate.

Now, customers can see the principal's events before and after the finding to determine whether the principal was performing actions that were part of an attack or just routine business activity. 

Principal event history is available on the findings contextual view for all CDR findings where event history is available.  🎥 See a short video here.

Provide any feedback on this feature directly from the link provided at the bottom of the Principal History tab on the findings contextual view.