In my role as a Client Cybersecurity Engineer at Rackspace, I was tasked with assisting Cymbal Bank in identifying and remediating security threats within their cloud infrastructure. This involved collaborating closely with my team to ensure that all security measures were effectively implemented. Below, I outline the structured approach I took to address the critical findings, including strategically placed screenshots to enhance clarity and help hiring managers visualize the process and results
Misconfigured storage bucket: Sensitive customer documents were at risk of unauthorized access due to a misconfiguration.
Anomalous Activity Detection: Chronicle SIEM flagged an external email access issue where an external email account (cymbal.analyst.demo@gmail.com) was granted excessive privileges.
Client Cyber Security Engineer
Collaborating Team Lead
Google Cloud Security Command Center
Google Cloud Storage
Google cloud IAM
Google Big Query
Policy Analyzer
Corrected Cloud Storage configurations
Updated IAM roles
Security report detailing remediation steps and outcomes
First, I accessed the Threats dashboard within the Security Command Center (SCC). This dashboard is vital for monitoring potential security issues and compliance status
I opened the SCC dashboard and selected the Threats section.
Conducted a real -time scan to detect any ongoing threats.
Checked the security compliance status against the ISO/IEC 27001:2013 standards to ensure all necessary measures were in place.
Next, I addressed the misconfiguration of a Cloud Storage bucket containing sensitive customer documents.
I accessed the Cloud Storage settings and removed public access to the bucket as it posed a significant security risk.
I changed the access control to uniform and applied this as a policy constraint to limit interaction to authorized users only.
In response to the IAM anomalous grant identified earlier, I created a custom IAM role to provide the necessary permissions for the data analyst contractor.
I defined the role titled "Cymbal Analyst -Read Only" with a description that clarified it's purpose.
Assigned specific permissions to the role, focusing on read-only access.
To further secure the environment, I revoked any excessive permissions from the data analyst's account.
Revoke Permissions:
I accessed the IAM settings and removed the Editor role assigned to the external user
Asign Custom Role:
I then assigned the newly created "Cymbal Analyst-Read Only" role to ensure that the analyst had the appropriate access without excessive privileges.
Finally, I used the Google Cloud Policy Analyzer to confirm that the IAM role changes were effective.
Run Policy Analyzer:
I created a query to review the current permissions for the external data analyst's account.
In this lab, I demonstrated proficiency in applying ISO/IEC 27001:2013 standards and best practices to a real-world cloud security scenario. I successfully detected an IAM anomalous grant threat reported by Google Cloud SCC's Event Threat Detection service, implemented corrective measures for a Cloud Storage bucket misconfiguration, and verified the effectiveness of my solutions. These skills are crucial for any organization aiming to reduce cybersecurity risk and align with industry-leading security practices.
By following a structured approach and utilizing the appropriate tools, I was able to effectively mitigate potential threats, ensuring the security and integrity of Cymbal Bank's sensitive data.