Forensia CTI Core

Summary

Ingested excerpt (first ~500 chars of normalized text).

The Risk of Exposed Cloud Functions and How to Harden Written by: Corné de Jong Introduction Mandiant security assessments frequently identify publicly exposed serverless applications that lack authentication, often as a result of specific business requirements. Serverless deployments typically run custom-developed code that incorporates third-party packages, making them targets for a wide range of application-level attacks, including: Local and Remote File Inclusion (LFI/RF…

https://cloud.google.com/blog/topics/threat-intelligence/exposed-cloud-functions-harden

sha256:03914a17b52617f275aed5c99b9135c00f820b82f1833a6d50d2b28e83423fe0

What we pulled out

Deterministic extractor (IOC + allowlisted tokens + ATT&CK IDs present in DB).

cve0
md50
url4
ipv40
ipv60
sha10
domain13
sha2560
malware_token0
attack_pattern0
threat_actor_token0

Indicators

Linked with report → mentions → indicator. Values open the indicator workspace.

Type	Value	Link
domain	package.json	Open →
domain	requirements.txt	Open →
domain	metadata.google.internal	Open →
domain	storage.objectviewer	Open →
domain	main.py	Open →
domain	subprocess.run	Open →
domain

Malware families

Allowlist token matches only.

None extracted.

Threat actors mentioned

Allowlist mentions — not a formal attribution verdict.

None extracted.

ATT&CK techniques

MITRE IDs referenced in text and present in local technique table.

None linked (import ATT&CK or adjust text).

CONTINUE INVESTIGATION

High-signal pivots without leaving the thread you started in search.

All reports
Browse the report corpus.
Intel graph (first IOC)
Neighborhood from the first linked indicator.

← Back to reports