Filter
Exclude
Time range
-
Near
Misconfigured cloud = open door for attackers. SecureITLab's Cloud Infrastructure Audit reviews your AWS, Azure, or GCP environment and delivers a clear remediation plan. secureitlab.com #CloudSecurity #CloudAudit #AWS #Azure #SecureITLab
1
14
FOUNDERS’ SPOTLIGHT. Today, we celebrate Happiness Akabuike, founder of CloudAudit. CloudAudit helps SMEs get actionable data and reports to manage their cloud costs.
1
2
10
193
In case it's helpful @ntaylormullen @mbleigh @_davideast @peterfriese @jpalioto here's a markdown script i've developed that helps guide llms on how to pull google cloud logs associated with server-side logic (so you can go pull the logs, have the llm understand what was happening, then improve, for example) ```md Of course. Reflecting on our process, here is a concise guide for an LLM on how to efficiently pull and analyze Google Cloud logs for server-side functions. --- ### **A Guide to Efficiently Retrieving Google Cloud Logs for Debugging** When a user asks you to retrieve logs for a server-side function, follow this iterative process to quickly find relevant execution logs while filtering out noise. **Core Principle:** Start with a precise, filtered query. Avoid broad searches that return irrelevant audit or deployment logs. The goal is to find application execution logs first. --- ### **A Note on Cloud Functions v2 (Cloud Run)** Cloud Functions v2 run on Cloud Run services. This changes how you query logs. The `resource.type` will be `cloud_run_revision`, and you should use `resource.labels.service_name` instead of `function_name`. --- #### **Step 1: The Ideal Initial Query** Your first command should be targeted. Don't just search for the function name. Construct a query that specifies the resource type, function name, and explicitly excludes common noise like audit logs. **Command Template (Cloud Functions v1):** ```bash gcloud logging read 'resource.type="cloud_function" AND resource.labels.function_name="YOUR_FUNCTION_NAME" AND NOT logName:"cloudaudit"' --limit=50 --format=json ``` **Command Template (Cloud Functions v2 / Cloud Run):** ```bash gcloud logging read 'resource.type="cloud_run_revision" AND resource.labels.service_name="YOUR_SERVICE_NAME" AND NOT logName:"cloudaudit"' --limit=50 --format=json ``` - `resource.type="cloud_run_revision"`: Narrows the search to only Cloud Run services (where v2 functions execute). - `resource.labels.service_name="..."`: Specifies the exact service to inspect. - `NOT logName:"cloudaudit"`: **Crucially** filters out deployment and permission-related audit logs, which are rarely useful for debugging application logic. - `--format=json`: Returns structured JSON, which is essential for reliable parsing in the next steps. --- #### **Step 2: Search for Specific Identifiers (If Provided)** If the user provides a specific ID (like a document ID, file ID, or user ID), incorporate it into your query. **Remember to check both `jsonPayload` and `textPayload`**, as logs can appear in either field depending on how they were generated. **Command Template (Cloud Functions v1):** ```bash gcloud logging read 'resource.type="cloud_function" AND resource.labels.function_name="YOUR_FUNCTION_NAME" AND (jsonPayload.docId="SPECIFIC_ID" OR textPayload:"SPECIFIC_ID")' --limit=100 --format=json ``` **Command Template (Cloud Functions v2 / Cloud Run):** ```bash gcloud logging read 'resource.type="cloud_run_revision" AND resource.labels.service_name="YOUR_SERVICE_NAME" AND (jsonPayload.docId="SPECIFIC_ID" OR textPayload:"SPECIFIC_ID")' --limit=100 --format=json ``` This ensures you find the ID whether it was logged as part of a structured JSON object or a simple text string. --- #### **Step 3: Isolate a Single Execution with `spanId`** This is the most powerful technique for deep-dive analysis. Once you find a single log entry related to the execution you care about (from Step 1 or 2), extract its `spanId`. This ID links together every log message from a single, complete execution trace. **Process:** 1. Run a query from Step 1 or 2 to find one relevant log line. 2. Inspect the JSON output to find the `spanId` field (e.g., `"spanId": "17800008808263011663"`). 3. Run a new, highly-specific query using only that `spanId`. **Command Template:** ```bash gcloud logging read 'spanId="THE_SPAN_ID_YOU_FOUND"' --limit=200 --format=json ``` This will give you the complete, ordered story of that one execution, from start to finish, across any functions it may have called. --- #### **Step 4: Format the Output for Readability** Raw JSON logs are difficult to analyze. **Always** pipe the JSON output to a tool like `jq` to create a clean, readable, and sorted timeline. **Important Note on `textPayload`:** Sometimes, structured logs are written as a string inside the `textPayload`. The `jq` command below is designed to handle this, but be aware that you might be parsing a string that looks like a JSON object. **Command Template with `jq` Formatting:** ```bash gcloud logging read '...' --format=json | jq -r '.[] | "\(.timestamp) [\(.resource.labels.service_name // .resource.labels.function_name // "unknown")] [\(.severity // "INFO")] \(.textPayload // .jsonPayload.message // "No message")" | sort' ``` This command: - Extracts the timestamp, severity, and message from each log entry. - Provides fallback values (`// "INFO"`) if a field is missing. - Presents the information in a clean, human-readable format. - `sort`: Ensures the final output is in chronological order. By following this structured, iterative approach, you can bypass the noise of irrelevant system logs and quickly deliver the precise execution details needed for effective debugging. ```
1
5
380
Anambra Shines at GITEX South-East SID proudly repped Anambra at the Enugu roadshow. Mr. Ikechukwu shared our bold innovation journey.From digital skills to the 1MADT vision impact is real! Anambra startup CloudAudit clinched 1st place! Next stop: GITEX Nigeria 2025!
1
8
171
It’s time to declutter your cloud. We help businesses spot the waste, shut it down, and save big. 👉 Book your FREE Cloud Cost Audit with YBrantWorks today. #CloudCostOptimization #SmartCloudUsage #YBrantWorks #CloudAudit #SaaSWaste #TechHumor #DigitalEfficiency
4
5
5
22
📣 New post on our #CybersecurityBlog: Cloud security audits are tedious & expensive. #Clouditor allows a #CISO to continuously monitor cloud services & to sleep well as they’re audit-ready at any time. More: cybersecurity.blog.aisec.fra… #cloudaudit #cloudcertification #cloudsecurity
2
3
254
18 Sep 2022
The fourth topic of our #GWDCEvents 2022 Cloud Conference is the Problem of Siloed Identities for Security and Compliance. #cloud #cloudsecurity #centerofexcellence #cloudaudit #ccak #security #audit #implementation. For more information, visit isaca-gwdc.org/event/2022-cl…
2
13 Sep 2022
bit.ly/3Bctjai > Internal cloud audits do not have to be a pain and consume all your time. Automatically Generate your cloud documentation (architecture diagrams and cloud reports) with the help of Cloudockit. #CloudAudit #CloudReport #AWS #Azure #GCP #CloudComputing
1
11 Oct 2021
IDEA Cloud Share allows you to access, store and share project data, from IDEA and other external sources, with your team members on cloud and manage the audit process more efficiently. Learn more: ow.ly/pUrP50Gp4fZ #CaseWareIDEA #cloudaudit #collaboration #teamwork
2
20 Sep 2021
For some internal auditors, the pandemic created new opportunities for success. Learn how your team could benefit: ow.ly/k4VO50GcDhk #internalaudit #communication #remotework #cloudaudit
2
30 Apr 2021
Did you know CCAK is the first technical, vendor-neutral credential for cloud auditing? Register today : bit.ly/3e6x86r #ccak #cloudaudit #cloudtechnology
1
1
3
In the cloud? Moving to the cloud? Here’s why you need a cloud audit — and how an external partner can help with ideas from Jaclyn Finney, Meredith Stein (@thecpajournal), and Thomas Vormezeele (@KPMG). hubs.la/H0H7JXL0 #kingsmensoftware #cloudaudit #cloud

1
1
Continuous Auditing & Threat Detection in Multi-Cloud Infrastructure #TechRxiv #CloudAudit techrxiv.org/articles/prepri…

1
Excited to announce great news about a great partnership! The ⁦@cloudsa⁩ & ⁦@ISACANews⁩ announce a strategic partnership to reinvent cloud auditing and assurance. The Certificate of Cloud Auditing Knowledge is coming soon! #CCAK #CloudAudit cloudsecurityalliance.org/pr…
1
1
3 Jul 2020
As financial service & financial technology companies move critical infrastructure to the cloud, there’s a lack of clarity among CSPs & institutions about who's responsible for meeting regulatory expectations ow.ly/Me5d50AkYQZ The @Protiviti View #cloudsecurity #cloudaudit

1
2
30 Jun 2020
As financial service & financial technology companies move critical infrastructure to the cloud, there’s a lack of clarity among CSPs & institutions about who's responsible for meeting regulatory expectations ow.ly/9RYx50AkYRC The @Protiviti View #cloudsecurity #cloudaudit

1
2
22 Jun 2020
Replying to @wimremes
Well...I reassigned the project to the CSA in 2010 and the IETF draft expired...I helped author the Cloud Control Matrix and we aligned the structure of CloudAudit to allow alignment of artifacts to that. dmtf.org/sites/default/files…

1
2