Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Pulumi WASM/Rust devlog #1

Since my last post more than half a year have passed. The project is still going strong and a lot of improvements have been introduced. Builders Last time, all fields were required (even is they are empty): let…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Since my last post more than half a year have passed. The project is still going strong and a lot of improvements have been introduced.






Builders



Last time, all fields were required (even is they are empty):




    let random_string_1 = random_string(
"test_1",
RandomStringArgs {
keepers: None.into(),
length,
lower: None.into(),
min_lower: None.into(),
min_numeric: None.into(),
min_special: None.into(),
min_upper: None.into(),
number: None.into(),
numeric: None.into(),
override_special: None.into(),
special: None.into(),
upper: None.into(),
},
);






I've migrated all the structs to bon so now they look like this




    let random_string_1 = random_string::create(
"test_1",
RandomStringArgs::builder().length(length).build_struct(),
);






In the future I will experiment with Function Builder to see if it will be a better choice






Code generation



Last time provider was split into two parts - WASM based provider (generated on Pulumi WASM side and distributed as binary artifact) and glue code (potentially generated on user side, last time still generated by Pulumi WASM).



I've decided to go 100% for code generation on user side. Thanks to that user can use any provider they want in any version they want. In addition provider does not have to be available in public Pulumi registry - glue code can be generated from schema.json.




# build.rs
use std::error::Error;
fn main() -> Result<(), Box<dyn Error>> {
pulumi_wasm_build::generate("random", "4.15.0")?;
Ok(())
}









Examples



Currently Pulumi does not export code examples in easy to ingest format. I've decided to try reading YAML and the results are pretty good - for now it's very basic and things like variables, interpolation and complicated order does not work. Here is example of ACMPCA Permission




use pulumi_wasm_rust::Output;
use pulumi_wasm_rust::{add_export, pulumi_main};
#[pulumi_main]
fn test_main() -> Result<(), Error> {
let example = permission::create(
"example",
PermissionArgs::builder()
.actions(vec!["IssueCertificate", "GetCertificate", "ListPermissions",])
.certificate_authority_arn("${exampleCertificateAuthority. arn}")
.principal("acm.amazonaws.com")
.build_struct(),
);
let exampleCertificateAuthority = certificate_authority::create(
"exampleCertificateAuthority",
CertificateAuthorityArgs::builder()
.certificate_authority_configuration(
CertificateAuthorityCertificateAuthorityConfiguration::builder()
.keyAlgorithm("RSA_4096")
.signingAlgorithm("SHA512WITHRSA")
.subject(
CertificateAuthorityCertificateAuthorityConfigurationSubject::builder()
.commonName("example. com")
.build_struct(),
)
.build_struct(),
)
.build_struct(),
);
}









There are still a lot of things to do - generating the biggest providers (AWS almost works), core improvements (there are non-working edge cases,

like functions without inputs), example generation improvements, documentation and creating PoC of non-rust WASM language.



Links:

Main repository: https://github.com/andrzejressel/pulumi-wasm

Example: https://github.com/andrzejressel/pulumi-wasm-example

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - Pulumi WASM/Rust devlog #1
id: 90a8544c-99bd-4305-ab5e-db5106222112
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-27
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-27"
        description = "YARA Signature for "
    strings:
        $str = "Pulumi WASM/Rust devlog #1" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Pulumi WASMRust devlog 1")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Pulumi WASMRust devlog 1*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Pulumi WASMRust devlog 1"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Analyse für identifizierte Bedrohung auf Basis von Live-CTI (ENISA EUVD): CVSS 0.0 · EPSS 0.0% · CISA KEV: nein. Handlungsableitung aus den verlinkten Hersteller-Quellen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Pulumi WASM/Rust devlog #1

Thematisch verwandte Begriffe: Pulumi, WASMRust, devlog · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

💬 Kommentare werden geladen…
Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-100739 | A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag