What processes do you rely on to address risks from rogue cloud tenants that the security team doesn’t have visibility of?

Threat & Vulnerability Management Threat Intelligence & Incident Response

1.9k views2 Comments

Sort by:

Director of Information Security in Finance (non-banking)4 months ago

I do not agree to @Adel Awad, it's not the Security that has to have the right to create new infrastructure in the cloud, but there has to be one dedicated and responsible team for the environment.
Architects build systems and services
Infrastructure team build templates for the container or cloud services
Security approves that
DevTeams just use templates and are not allowed to define their own infrastructure
CI/CD is an automated one-way street to PROD and the only way into it.
No interaktive service in PROD, if there is an error in PROD, fix it in DEV and start CI/CD

CIO in Banking4 months ago

You need to lockdown your cloud environment so that only the cybersecurity team is allowed to create an environment under your domain ownership, you also need to monitor the attack surface , such as storage buckets exposed to the outside world , lack of conditional access , etc… there are solutions that helps you monitor cloud security (Cloud Security Posture Monitoring)

Content you might like

For those in healthcare, are medical devices vulnerable to hackers or outside bad actors?

Yes56%

Not yet, but it's possible in the near future32%

No4%

Unsure6%

View Results

How do you manage risk with contractors in your supply chain?

Keep hard copies and file paperwork13%

Update spreadsheets to create reports44%

Use a digital supply chain management solution27%

Partner with a third-party vendor11%

Other (comment below)3%

View Results

What sorts of failsafe processes/controls, etc, do you rely on to make sure terminated or suspended employees’ access credentials are revoked immediately? Does your org generally rely on direct communications from HR or do you have an HRM or similar system to automate this?

Excluding CVE, what other vulnerability databases/info sources do you use currently? Have you developed any contingency plans to lean on in case the CVE program loses funding?