Serverless runtime issues - Administrator Guide - Cortex CLOUD

Cortex Cloud Runtime Security Documentation

Product
Cortex Cloud Application Security > Cortex CLOUD
License
Cloud Runtime Security
Creation date
2024-12-24
Last date published
2026-06-10
Category
Administrator Guide

You can view all serverless function issues detected by an agent and generated from policy violations under Issues (under Cases & Issues) inventories.

Every policy violation creates an issue per type:

  • Process activity - enables specifying specific allowed list processes, blocking all processes except the main process and detecting crypto mining attempts.

  • Network activity - enables monitoring and enforcement of DNS resolutions, inbound and outbound network connections.

  • Filesystem activity - enables defining specific paths in an allowed or denied list.

Additional issues from specific policy violation are raised, which include the same cloud provider, region, runtime, function name, function version, issue name and issue description, will be suppressed.

The Issues page includes the following information indicating unique serverless function issues raised by agents:

Field

Description

Domain

For serverless, this is set to Security.

Category

For serverless, this is set to Cloud.

Name

For serverless, the relevant issue name appears:

  • Serverless function Network Policy violation for outbound ports

  • Serverless function Network Policy violation for listening ports

  • Serverless function Network Policy violation for DNS

  • Serverless function Network Policy violation for IPs

  • Serverless function File system Policy violation

  • Serverless function Process Policy violation

Detection method

For serverless, this is set to XDR agent.

Severity

For serverless, this is always set to High.

Cloud Function Runtime

  • Python

  • Node.JS

Cloud Function Request ID

Instance id from the cloud provider.

Note

Issues triggered within 24 hours, sharing the same name and description, will be aggregated into cases along with issues from the same function per execution.