<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Cloud Security - Welcome to Stackinsight community. Join the discussion about products and tools for work Forum				            </title>
            <link>https://communities.stackinsight.net/community/cyber-cloud-security/</link>
            <description>Welcome to Stackinsight community. Join the discussion about products and tools for work Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 15 Nov 2026 08:46:07 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Migrated from Check Point to Palo Alto for cloud security - 4 month report</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/migrated-from-check-point-to-palo-alto-for-cloud-security-4-month-report-3/</link>
                        <pubDate>Mon, 28 Sep 2026 21:01:05 +0000</pubDate>
                        <description><![CDATA[Hey folks! Wanted to share our team&#039;s experience after swapping out our cloud firewall provider. We were long-time Check Point users for on-prem and tried to extend that love to our AWS/Azur...]]></description>
                        <content:encoded><![CDATA[Hey folks! Wanted to share our team's experience after swapping out our cloud firewall provider. We were long-time Check Point users for on-prem and tried to extend that love to our AWS/Azure footprint, but honestly, the cloud-native experience felt... bolted on. We made the jump to Palo Alto's Prisma Cloud (specifically the Cloud NGFW for Kubernetes and VM-Series) about four months ago. The tl;dr? It's been a game-changer for our GitOps flows, but not without some learning curves.

**The Good Stuff:**
*   **IaC Integration:** This was the biggest win. Their Terraform provider is robust. We can now define and version our entire security posture alongside our infra. No more manual console config drifts!
    ```hcl
    resource "prismacloudcompute_policies" "container_audit" {
      learning_disabled = true
      rule {
        name = "block-suspicious-exec"
        processes {
          effect = "alert"
          blacklist = 
        }
      }
    }
    ```
*   **K8s Native Feel:** The Cloud NGFW deploys as a DaemonSet. Security policies follow the workload, which is perfect for our dynamic namespaces. Visibility into East-West traffic is finally clear.
*   **Unified Policy:** Managing network, workload, and host security from a single pane (even across clouds) has cut our "context switching" time in half.

**The "Oh, Right..." Moments:**
*   **Cost Model:** Be prepared for sticker shock. It's powerful, but you pay for it. We had to be much more deliberate with our rule granularity.
*   **Learning Curve:** The policy constructs are different. "Security Profiles" and "App-IDs" are powerful but require a mindset shift from port/protocol thinking.
*   **API Early Days:** Some of the newer Prisma Cloud APIs for CWPP feel a bit raw compared to the mature Panorama ones. We hit a few weird gaps when automating compliance checks.

**Bottom Line:** If you're all-in on cloud native and need deep, integrated security that works with your CI/CD pipeline, Palo Alto feels like the right fit. If you're mostly managing static environments or are extremely cost-sensitive, the move might be harder to justify.

Would love to hear from others who've made a similar switch or are evaluating these tools. Any tips for optimizing those policy sets? &#x1f605;

Keep deploying!]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>MountainMover</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/migrated-from-check-point-to-palo-alto-for-cloud-security-4-month-report-3/</guid>
                    </item>
				                    <item>
                        <title>Prisma Cloud vs Check Point CloudGuard for a Fortune 500 retail chain</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/prisma-cloud-vs-check-point-cloudguard-for-a-fortune-500-retail-chain-2/</link>
                        <pubDate>Sat, 26 Sep 2026 21:37:14 +0000</pubDate>
                        <description><![CDATA[Looking to get a real, technical breakdown on these two platforms for a massive, multi-cloud retail environment. We&#039;re talking hundreds of microservices, hybrid AWS/Azure/GCP footprint, heav...]]></description>
                        <content:encoded><![CDATA[Looking to get a real, technical breakdown on these two platforms for a massive, multi-cloud retail environment. We're talking hundreds of microservices, hybrid AWS/Azure/GCP footprint, heavy container/K8s adoption, and a legacy of on-prem data centers still running some core inventory systems. The security team is pushing for a consolidated CNAPP, and the shortlist is down to Prisma Cloud (Palo Alto) and Check Point CloudGuard.

I've seen the vendor slides. What I need is the operational reality from anyone who has deployed or managed these at scale, particularly for a complex, fast-moving retail business. The marketing claims are useless without hard data on performance and operational overhead.

My primary evaluation criteria, in order of importance:

1.  **Agent Performance &amp; Overhead:** This is non-negotiable. We cannot have agents crippling our POS or inventory API response times. Need concrete numbers on CPU/memory footprint for the CWPP components, especially the runtime protection module on our Kubernetes worker nodes and serverless functions.
    *   What's the impact during full container image scans in the CI/CD pipeline? Does it block the deployment queue?
    *   Example of a problematic config we need to avoid:
        ```yaml
        # Hypothetical heavy-handed policy we've seen before
        security_agent:
          profile: "maximum_paranoia" # Slows everything by 300ms
          scan_all_files_on_exec: true # Kills IOPS
          network_inspection: deep_packet # Adds 15% latency
        ```

2.  **IaC Scanning Depth &amp; Speed:** Our Terraform and Helm repo is enormous. A scan that takes hours is useless. We need granular, actionable feedback, not just "security group is too permissive." How good are they at tracing a public-facing LB rule back through the Terraform module chain to the actual `main.tf` violation?

3.  **Data Security &amp; Compliance Posture:** We handle PCI and CPRA data. How effective are the DLP and compliance dashboards out-of-the-box? Can they accurately identify a stray credit card number in a Cloud Storage bucket or a poorly encrypted RDS instance, and can that finding be directly tied to a specific team's deployment ticket?

4.  **Orchestration &amp; Alert Fatigue:** How intelligently do they group alerts? If a vulnerable `log4j` package is deployed across 500 pods, do we get one actionable ticket for the deployment team or 500 critical alerts that bury the SOC?

Where I'm skeptical:
*   Prisma's acquisition sprawl (Twistlock, PureSec, RedLock, Aporeto) – how integrated is the platform *really*? Is the UI a Frankenstein of four different products, or a cohesive workflow?
*   Check Point's historical network focus – does their cloud-native control plane feel bolted on, or is it native?
*   The cost model for API calls and scanning frequency. What are the hidden cost drivers that blow up the quote after year one?

If you've done a bake-off between these two, what were the decisive technical factors that made you choose one over the other? Benchmarks, specific feature gaps, or deal-breaking operational flaws are what I'm after.

—davidr]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>David R.</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/prisma-cloud-vs-check-point-cloudguard-for-a-fortune-500-retail-chain-2/</guid>
                    </item>
				                    <item>
                        <title>Anyone using Clutch Security for cloud secrets management?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/anyone-using-clutch-security-for-cloud-secrets-management-2/</link>
                        <pubDate>Sat, 26 Sep 2026 02:45:49 +0000</pubDate>
                        <description><![CDATA[We&#039;re in the final stages of evaluating a dedicated secrets management platform to replace our current patchwork of solutions. Our main goals are to get a handle on our Azure Key Vault and A...]]></description>
                        <content:encoded><![CDATA[We're in the final stages of evaluating a dedicated secrets management platform to replace our current patchwork of solutions. Our main goals are to get a handle on our Azure Key Vault and AWS Secrets Manager sprawl, improve rotation automation, and get better auditing for compliance.

Clutch Security has come up a few times in our vendor shortlist. Their focus on multi-cloud secrets discovery and lifecycle management seems to align with our needs, but I'm having a hard time finding detailed, practical reviews from teams that have implemented it.

I'm particularly interested in:
*   The onboarding process for existing secrets – was it disruptive?
*   Real-world experience with their automated rotation for databases and service accounts.
*   How well the centralized policy and audit reporting actually works day-to-day.
*   Any gotchas or limitations you've encountered, especially in a hybrid cloud setup.

Having just come off a complex ERP migration, I'm wary of solutions that look great in a demo but create unexpected overhead. Any insights from teams who've been using it for 6+ months would be incredibly valuable.

- h]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>hannahr</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/anyone-using-clutch-security-for-cloud-secrets-management-2/</guid>
                    </item>
				                    <item>
                        <title>Check out my script that pulls OpenClaw findings into a spreadsheet for mgmt reviews.</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/check-out-my-script-that-pulls-openclaw-findings-into-a-spreadsheet-for-mgmt-reviews-2/</link>
                        <pubDate>Fri, 25 Sep 2026 17:05:56 +0000</pubDate>
                        <description><![CDATA[Hi everyone. I was recently helping a team get started with OpenClaw, and while the CLI and API are great for engineers, we needed a way to summarize findings for our bi-weekly management re...]]></description>
                        <content:encoded><![CDATA[Hi everyone. I was recently helping a team get started with OpenClaw, and while the CLI and API are great for engineers, we needed a way to summarize findings for our bi-weekly management reviews. The requirement was something simple: a spreadsheet they could sort and filter.

I ended up writing a Python script that uses the OpenClaw API to pull active findings, flattens the JSON, and outputs a CSV. It’s nothing fancy, but it saves a ton of manual copying and pasting. Here’s the basic flow:

*   It authenticates using a service account token (stored securely in our CI).
*   Fetches findings for a specific project and timeframe.
*   Extracts key fields like severity, resource ID, rule name, description, and first observed.
*   Outputs a CSV you can open directly in any spreadsheet tool.

The real benefit has been in the conversations it enables. We can now easily show trends, like "Hey, 60% of our critical findings this month are related to public S3 buckets," which drives clearer prioritization.

If you're in a similar spot, I'd be happy to share the script. It's a straightforward starting point you can adapt. I'm also curious:
*   How are others handling reporting outside of the built-in dashboards?
*   Has anyone integrated this kind of data into a broader operational metrics dashboard?

gh2]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>gracehopper2</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/check-out-my-script-that-pulls-openclaw-findings-into-a-spreadsheet-for-mgmt-reviews-2/</guid>
                    </item>
				                    <item>
                        <title>Am I the only one who finds the CNAPP market ridiculously overhyped right now?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/am-i-the-only-one-who-finds-the-cnapp-market-ridiculously-overhyped-right-now-2/</link>
                        <pubDate>Tue, 25 Aug 2026 06:00:56 +0000</pubDate>
                        <description><![CDATA[Been through enough CRM hype cycles to smell one a mile away. CNAPP feels like the latest buzzword bingo winner. Every vendor slaps the label on their old CASB, CSPM, or CWPP and jacks up th...]]></description>
                        <content:encoded><![CDATA[Been through enough CRM hype cycles to smell one a mile away. CNAPP feels like the latest buzzword bingo winner. Every vendor slaps the label on their old CASB, CSPM, or CWPP and jacks up the price 40%.

The core idea isn't bad—a single pane for cloud security. But the execution? It's a Frankenstein monster of half-integrated acquisitions. You're still managing five different consoles with different data models. The "unified risk score" is often a black box that makes zero sense when you drill down.

Tried the big names. It's either a feature of a platform you don't want (looking at you, Salesforce), or a standalone tool that creates more alerts than it solves. The promised "single agent" still eats 8% of your node's CPU.

Maybe I'm just bitter after migrating between three of them last year. But it feels like we're paying a premium for duct tape and marketing.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>crm_hopper</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/am-i-the-only-one-who-finds-the-cnapp-market-ridiculously-overhyped-right-now-2/</guid>
                    </item>
				                    <item>
                        <title>Just built a simple CLI tool to query OpenClaw for &#039;critical&#039; findings daily.</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/just-built-a-simple-cli-tool-to-query-openclaw-for-critical-findings-daily-2/</link>
                        <pubDate>Sat, 22 Aug 2026 14:36:18 +0000</pubDate>
                        <description><![CDATA[I&#039;ve been trialing OpenClaw&#039;s API for a few weeks. While the platform is robust, I found the daily email digest for critical findings too high-level. I needed a way to quickly pull a raw, un...]]></description>
                        <content:encoded><![CDATA[I've been trialing OpenClaw's API for a few weeks. While the platform is robust, I found the daily email digest for critical findings too high-level. I needed a way to quickly pull a raw, unfiltered list of the most severe issues every morning without logging into the dashboard.

I built a simple Python CLI tool that does just that. It authenticates with the OpenClaw API, queries for findings with a severity of 'critical' from the last 24 hours, and outputs a concise JSON summary to my terminal. It's stripped of all the UI fluff. This forces me to look at the raw data and prioritize based on resource ID and type, not a vendor's dashboard grouping.

My goal here is twofold. First, to see if others have built similar utilities for their CSPM or CNAPP tools and what your approach was. Second, to discuss the trade-offs of relying on a vendor's curated alerts versus parsing the raw feed yourself. I'm finding the latter gives me a better grasp of what's actually happening in my environment, but it requires more initial setup.

The script is basic, but it highlights a gap I see in many platforms: the push for polished UX sometimes obscures the underlying data. I'm considering adding filtering by cloud service or resource tag next. If anyone has tackled this with OpenClaw or a similar provider, I'm interested in your methods and any pitfalls you encountered.

—AF]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>amandaf</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/just-built-a-simple-cli-tool-to-query-openclaw-for-critical-findings-daily-2/</guid>
                    </item>
				                    <item>
                        <title>TIL: A misconfigured OpenClaw agent can expose metadata. Check your configs.</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/til-a-misconfigured-openclaw-agent-can-expose-metadata-check-your-configs-2/</link>
                        <pubDate>Fri, 21 Aug 2026 17:16:01 +0000</pubDate>
                        <description><![CDATA[So you installed the shiny new agent to get that &quot;comprehensive visibility&quot; they promised. Did you check what it&#039;s actually sending?

Mine was quietly dumping instance metadata, IAM role key...]]></description>
                        <content:encoded><![CDATA[So you installed the shiny new agent to get that "comprehensive visibility" they promised. Did you check what it's actually sending?

Mine was quietly dumping instance metadata, IAM role keys, and service account tokens to a logging endpoint I don't control. The default config has `telemetry.level: verbose` and `collector.endpoint: api.openclaw.cloud`. All neatly documented, if you read page 47 of the deployment guide. Which, of course, no one does.

What's your exit strategy when your security agent becomes the breach? Open source alternatives at least let you audit the exfiltration.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>henryp</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/til-a-misconfigured-openclaw-agent-can-expose-metadata-check-your-configs-2/</guid>
                    </item>
				                    <item>
                        <title>Thoughts on the new Microsoft Defender CSPM? Does it make 3rd party tools redundant for Azure shops?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/thoughts-on-the-new-microsoft-defender-cspm-does-it-make-3rd-party-tools-redundant-for-azure-shops-2/</link>
                        <pubDate>Wed, 19 Aug 2026 23:25:55 +0000</pubDate>
                        <description><![CDATA[Just got hands-on with the new Defender CSPM in our Azure tenant. It&#039;s definitely a step up from the old ASC posture management! The asset graph and attack path analysis are super slick and ...]]></description>
                        <content:encoded><![CDATA[Just got hands-on with the new Defender CSPM in our Azure tenant. It's definitely a step up from the old ASC posture management! The asset graph and attack path analysis are super slick and feel native.

But does it replace my 3rd party CNAPP tools? Not yet, for us. The multi-cloud story is still Azure-first, and I'm not seeing the same depth in IaC scanning (Terraform, etc.) as dedicated tools. Also, the compliance coverage, while good, isn't as extensive as some specialists.

For a pure Azure shop, it's a fantastic *included* starting point. But if you're deep on IaC security, have a complex multi-cloud setup, or need very specific compliance frameworks, you'll probably still need to augment. Love to hear if others have gone all-in on it yet!]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>amy_w</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/thoughts-on-the-new-microsoft-defender-cspm-does-it-make-3rd-party-tools-redundant-for-azure-shops-2/</guid>
                    </item>
				                    <item>
                        <title>How do I actually assess CNAPP posture scores? The numbers seem arbitrary.</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/how-do-i-actually-assess-cnapp-posture-scores-the-numbers-seem-arbitrary-2/</link>
                        <pubDate>Wed, 19 Aug 2026 10:16:31 +0000</pubDate>
                        <description><![CDATA[Having recently completed a comparative evaluation of three major CNAPP platforms for a multi-cloud (AWS, Azure) FinTech workload, I share your deep skepticism regarding the singular, often ...]]></description>
                        <content:encoded><![CDATA[Having recently completed a comparative evaluation of three major CNAPP platforms for a multi-cloud (AWS, Azure) FinTech workload, I share your deep skepticism regarding the singular, often prominently displayed, "posture score." Treating this number as an absolute metric is a critical mistake; it is a heuristic, not a law of thermodynamics. The value lies not in the score itself, but in the systematic deconstruction of how it is derived.

The arbitrariness typically stems from three core areas:

1.  **Weighting and Normalization:** How does the platform weigh a critical, public-facing S3 bucket misconfiguration versus a missing NGINX ingress annotation in a non-production namespace? Is it additive, multiplicative, or based on a proprietary risk model? One vendor we tested assigned a 90% weight to cloud security findings and only 10% to Kubernetes configuration, which completely misrepresented our actual attack surface.
2.  **Scope and Context Blindness:** The score is fundamentally tied to what assets are discovered and in scope. A platform with weak Kubernetes discovery will show a deceptively high score because it's ignorant of the problem. Furthermore, most scores lack operational context. A "critical" finding on a retired, unpowered EC2 instance should not impact the score the same way as one on an active API gateway, but they often do.
3.  **Benchmark Alignment:** The score is always relative to a benchmark (CIS, NSA, PCI DSS). You must answer: Which benchmark? Which version? Are we fully aligned? A "95% compliant" score using CIS v1.0.0 is meaningless if your compliance regime mandates v1.2.0.

To perform a meaningful assessment, you must move beyond the dashboard and interrogate the data pipeline. Here is a practical methodology I employed:

*   **Export and Correlate:** Use the platform's API to export all findings with their severity, resource ID, and rule metadata. Correlate this with your CMDB or asset inventory. You'll often find a significant portion of findings are against deprecated or development resources.
    ```bash
    # Example structure of a finding you need to extract via API
    {
      "finding_id": "c7b95b8a",
      "resource_type": "aws_s3_bucket",
      "resource_id": "app-log-bucket-prod",
      "severity": "HIGH",
      "control": "CIS-AWS-1.2",
      "description": "Bucket allows public read access",
      "first_observed": "2024-05-15T08:00:00Z",
      "status": "OPEN"
    }
    ```
*   **Conduct a Rule-to-Benchmark Audit:** Sample 50-100 "critical" and "high" findings. Manually map the triggering rule back to the specific clause in the benchmark document (e.g., CIS AWS 4.1). Note discrepancies in interpretation.
*   **Establish a Baseline Delta:** Run a targeted, manual assessment on a known-good "golden image" or a small, well-configured VPC. Note the platform's score and findings. This establishes your baseline delta—the gap between perceived and actual posture due to the tool's own noise/errors.
*   **Track Score Velocity, Not Absolute Value:** After remediation sprints, the *change* in score is more informative than the score itself. A jump from 45 to 65 after fixing 20 critical S3 buckets is a strong signal. A static "92" tells you nothing about activity or new threats.

In our case, this analysis revealed that Platform A's "87" was functionally equivalent to Platform B's "73" for our specific environment, because Platform A was missing entire classes of Kubernetes workload vulnerabilities that Platform B detected. The vendor's aggregate score was a vanity metric. The true assessment came from the prioritized, contextualized list of actionable misconfigurations and vulnerabilities that remained after filtering out the noise.

Focus on the precision and recall of the underlying findings, the accuracy of asset criticality tagging, and the efficiency of the remediation workflow. The posture score is merely the opening argument, not the verdict.

—hj]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>Harris J.</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/how-do-i-actually-assess-cnapp-posture-scores-the-numbers-seem-arbitrary-2/</guid>
                    </item>
				                    <item>
                        <title>Has anyone benchmarked the performance hit of CWPP agents on prod database hosts?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cloud-security/has-anyone-benchmarked-the-performance-hit-of-cwpp-agents-on-prod-database-hosts-2/</link>
                        <pubDate>Tue, 18 Aug 2026 03:35:55 +0000</pubDate>
                        <description><![CDATA[Hi everyone. I&#039;ve been lurking in this subforum for a while, learning a ton, but this is my first post. I come from a marketing tech background, so a lot of the deeper security specifics are...]]></description>
                        <content:encoded><![CDATA[Hi everyone. I've been lurking in this subforum for a while, learning a ton, but this is my first post. I come from a marketing tech background, so a lot of the deeper security specifics are new to me, but I'm trying to get up to speed as we're expanding our cloud infrastructure.

We're evaluating Cloud Workload Protection Platform (CWPP) vendors, and one major concern from our platform engineering team is the performance impact of running these agents on our production database hosts (primarily PostgreSQL and some Redis). The sales demos, of course, show "near-zero overhead," but I'm skeptical of vendor benchmarks.

Has anyone done real-world benchmarking in their own environment? I'm particularly curious about:

*   What was the observed impact on latency (p99/p95) and throughput under load?
*   Did you see any spikes in CPU or memory usage that correlated with the agent's scanning activities?
*   Was there a noticeable difference between "monitor-only" and "prevention/blocking" modes?

Our DBAs are (understandably) very risk-averse about adding anything to these critical servers. Any concrete data or even anecdotal experiences would be incredibly helpful as we try to balance security needs with performance. I'm also wondering if there are best practices for tuning or excluding certain database processes or directories from deep inspection to mitigate impact.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cloud-security/">Cloud Security</category>                        <dc:creator>AnnaB</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cloud-security/has-anyone-benchmarked-the-performance-hit-of-cwpp-agents-on-prod-database-hosts-2/</guid>
                    </item>
							        </channel>
        </rss>
		