Skip to content

IBM Cloud Security Engineer Certification - Fact Sheet

Quick Reference

  • Certification: IBM Certified Security Engineer - Cloud v2
  • Exam Code: C1000-173
  • Duration: 90 minutes
  • Questions: 60 multiple choice
  • Passing Score: 70%
  • Cost: $200 USD
  • Language: English
  • Delivery: Pearson VUE (online or test center)
  • Prerequisites: None (recommended 2+ years security experience)
  • Recertification: Every 3 years
  • Target Audience: Security engineers, cloud security specialists, security architects, compliance engineers

Official Resources

Exam Domains

1. Identity and Access Management (IAM) (25%)

  • IAM architecture and components
  • User and service ID management
  • Access groups and policies
  • API key management and rotation
  • Service-to-service authorization
  • Context-based restrictions
  • Trusted profiles
  • Multi-factor authentication (MFA)
  • Single sign-on (SSO) integration
  • Access policy design and best practices
  • Privilege escalation prevention
  • Identity federation

IAM Resources: - πŸ“– IAM Overview - πŸ“– IAM Concepts - πŸ“– IAM Roles - πŸ“– IAM Access Policies - πŸ“– Service IDs - πŸ“– API Keys - πŸ“– Access Groups - πŸ“– Context-Based Restrictions - πŸ“– Trusted Profiles - πŸ“– Multi-Factor Authentication - πŸ“– Service-to-Service Authorization - πŸ“– IAM Best Practices - πŸ“– Identity Federation

2. Data Protection and Encryption (20%)

  • Encryption at rest and in transit
  • Key management strategies
  • Key Protect service
  • Hyper Protect Crypto Services (HPCS)
  • Bring Your Own Key (BYOK)
  • Keep Your Own Key (KYOK)
  • Certificate management
  • Data classification and labeling
  • Data loss prevention (DLP)
  • Tokenization and masking
  • Secure data deletion

Data Protection Resources: - πŸ“– Data Encryption - πŸ“– Key Protect - πŸ“– Key Protect API - πŸ“– Hyper Protect Crypto Services - πŸ“– HPCS API - πŸ“– Bring Your Own Key - πŸ“– Keep Your Own Key - πŸ“– Certificate Manager - πŸ“– Secrets Manager - πŸ“– Secrets Manager API - πŸ“– SSL/TLS Certificates - πŸ“– Data Classification

3. Network Security (20%)

  • VPC security architecture
  • Security groups configuration
  • Network Access Control Lists (ACLs)
  • Virtual Private Networks (VPNs)
  • Direct Link security
  • Transit Gateway security
  • Public Gateway security
  • Floating IP management
  • Virtual Private Endpoints (VPE)
  • DDoS protection
  • Web Application Firewall (WAF)
  • Network segmentation and isolation
  • Bastion host architecture

Network Security Resources: - πŸ“– VPC Security - πŸ“– Security Groups - πŸ“– Security Group Rules - πŸ“– Network ACLs - πŸ“– VPN Gateway - πŸ“– VPN Security - πŸ“– Direct Link Security - πŸ“– Transit Gateway - πŸ“– Virtual Private Endpoints - πŸ“– Cloud Internet Services - πŸ“– DDoS Protection - πŸ“– Web Application Firewall - πŸ“– Network Segmentation

4. Security Monitoring and Compliance (15%)

  • Security and Compliance Center
  • Posture management
  • Compliance profiles and controls
  • Security event monitoring
  • Activity Tracker for auditing
  • Log Analysis for security logs
  • Threat detection and response
  • Vulnerability management
  • Security Information and Event Management (SIEM)
  • Compliance reporting
  • Security metrics and KPIs

Monitoring and Compliance Resources: - πŸ“– Security and Compliance Center - πŸ“– Compliance Posture Management - πŸ“– Compliance Profiles - πŸ“– Custom Profiles - πŸ“– Activity Tracker - πŸ“– Activity Tracker Events - πŸ“– Log Analysis - πŸ“– Security Monitoring - πŸ“– Flow Logs - πŸ“– Compliance Programs - πŸ“– ISO 27001 - πŸ“– SOC 2 - πŸ“– GDPR Compliance - πŸ“– HIPAA Compliance - πŸ“– PCI DSS

5. Application and Container Security (10%)

  • Container image security
  • Vulnerability Advisor
  • Image signing and verification
  • Kubernetes security best practices
  • Pod security policies
  • Network policies in Kubernetes
  • Secret management in containers
  • Security contexts and runtime security
  • App ID for application authentication
  • OAuth and OpenID Connect
  • API security

Application Security Resources: - πŸ“– Container Security - πŸ“– Vulnerability Advisor - πŸ“– Image Signing - πŸ“– Kubernetes Security - πŸ“– Pod Security - πŸ“– Network Policies - πŸ“– Secrets in Kubernetes - πŸ“– App ID - πŸ“– App ID Authentication - πŸ“– OAuth 2.0 - πŸ“– OpenID Connect - πŸ“– API Security

6. Specialized Security Services (10%)

  • Hyper Protect Services (DBaaS, Virtual Servers)
  • IBM Cloud Security Advisor (deprecated, now SCC)
  • Cloud Shell security
  • Satellite security
  • Watson AI service security
  • Database security and encryption
  • Object Storage security
  • Backup security and encryption

Specialized Services Resources: - πŸ“– Hyper Protect DBaaS - πŸ“– Hyper Protect Virtual Servers - πŸ“– Cloud Shell - πŸ“– Satellite Security - πŸ“– Database Encryption - πŸ“– Object Storage Encryption - πŸ“– Object Storage Access Control - πŸ“– Backup Encryption

Core Security Services

Identity and Access Services

Encryption and Key Management

Network Security Services

Monitoring and Compliance Services

Security Architecture Patterns

Zero Trust Architecture

Principle: Never trust, always verify

Implementation: - Verify every access request - Use least privilege access - Implement micro-segmentation - Continuous monitoring and validation - Multi-factor authentication - Assume breach mindset

Resources: - πŸ“– Zero Trust Architecture - πŸ“– Zero Trust Security

Defense in Depth

Layers: 1. Physical security 2. Network security (security groups, ACLs, VPN) 3. Host security (OS hardening, patch management) 4. Application security (secure coding, authentication) 5. Data security (encryption, DLP) 6. User security (IAM, MFA)

Resources: - πŸ“– Defense in Depth Strategy

Least Privilege Access

Implementation: - Grant minimum necessary permissions - Use access groups for role-based access - Regular access reviews - Time-bound access grants - Separate duties

Resources: - πŸ“– Least Privilege Best Practices

Secure by Design

Principles: - Security from the start - Threat modeling - Secure defaults - Privacy by design - Security testing in CI/CD

Resources: - πŸ“– Secure Application Development

Common Security Scenarios

Scenario 1: Securing Multi-Tier Application

Challenge: Secure a three-tier web application (web, app, database).

Security Controls: - Network Layer: - VPC with three subnets (web, app, data) - Security groups for each tier - Network ACLs for subnet isolation - Load balancer with SSL/TLS - No public access to app and data tiers

  • Access Control:
  • IAM policies with least privilege
  • Service IDs for app-to-service communication
  • MFA for administrative access
  • Context-based restrictions

  • Data Protection:

  • Encryption at rest with Key Protect
  • Encryption in transit (TLS 1.2+)
  • Certificate Manager for SSL certificates
  • Secrets Manager for credentials

  • Monitoring:

  • Activity Tracker for audit logs
  • Log Analysis for security logs
  • Flow logs for network traffic
  • Security and Compliance Center scans

Resources: - πŸ“– Multi-Tier Security

Scenario 2: Kubernetes Cluster Security

Challenge: Secure a Kubernetes cluster running microservices.

Security Controls: - Cluster Security: - Private cluster endpoint - Pod security policies - Network policies for pod isolation - RBAC for cluster access - Image vulnerability scanning

  • Image Security:
  • Private Container Registry
  • Vulnerability Advisor scanning
  • Image signing and verification
  • Base image hardening
  • Regular image updates

  • Runtime Security:

  • Security contexts for pods
  • Read-only root filesystems
  • Non-root containers
  • Resource limits
  • AppArmor/Seccomp profiles

  • Secret Management:

  • Secrets Manager integration
  • Encrypted secrets at rest
  • Short-lived credentials
  • Regular credential rotation

Resources: - πŸ“– Kubernetes Security Best Practices - πŸ“– Container Security

Scenario 3: Hybrid Cloud Security

Challenge: Secure connectivity between on-premises and IBM Cloud.

Security Controls: - Network Connectivity: - Direct Link with BGP authentication - VPN as backup with IPsec - Transit Gateway for multi-VPC - Private endpoints for services

  • Access Control:
  • Federated identity with SAML
  • Centralized IAM policies
  • Context-based restrictions
  • Network-based access control

  • Data Protection:

  • End-to-end encryption
  • KYOK for sensitive workloads
  • Data residency controls
  • Cross-site data replication security

  • Monitoring:

  • Centralized logging
  • Unified SIEM
  • Activity tracking across environments
  • Network flow monitoring

Resources: - πŸ“– Hybrid Cloud Security - πŸ“– Direct Link Security

Scenario 4: Compliance and Governance

Challenge: Implement controls for HIPAA compliance.

Security Controls: - Access Control: - MFA for all users - Role-based access control - Access request workflow - Regular access reviews

  • Data Protection:
  • Encryption for PHI data
  • Key management with HPCS
  • Data classification and labeling
  • Secure data deletion

  • Audit and Monitoring:

  • Activity Tracker for all events
  • Log retention for 7 years
  • Security event correlation
  • Compliance reporting

  • Network Security:

  • Network segmentation
  • Dedicated VPC for HIPAA workloads
  • VPN for remote access
  • DDoS protection

  • Continuous Compliance:

  • Security and Compliance Center
  • HIPAA profile scanning
  • Remediation tracking
  • Regular audits

Resources: - πŸ“– HIPAA Compliance - πŸ“– Compliance Automation

Scenario 5: API Security

Challenge: Secure public APIs for partner integration.

Security Controls: - Authentication: - OAuth 2.0 with client credentials - API key management - JWT token validation - App ID for user authentication

  • Authorization:
  • Scope-based access control
  • Rate limiting per client
  • Quota management
  • IP whitelisting

  • API Gateway:

  • API Connect for management
  • Request/response validation
  • Schema enforcement
  • Input sanitization

  • Monitoring:

  • API usage analytics
  • Anomaly detection
  • Security event logging
  • Performance monitoring

  • Data Protection:

  • TLS for all endpoints
  • Response data filtering
  • PII data masking
  • Secure credential exchange

Resources: - πŸ“– API Security - πŸ“– OAuth 2.0 Implementation

Security Best Practices

IAM Best Practices

  1. Use Access Groups: Group users with similar roles
  2. Least Privilege: Grant minimum necessary access
  3. Service IDs: Use for application authentication
  4. API Key Rotation: Rotate keys every 90 days
  5. MFA Enforcement: Enable for all users
  6. Context-Based Restrictions: Limit access by network
  7. Regular Audits: Review access quarterly
  8. Separation of Duties: No single user has full control

Resources: - πŸ“– IAM Best Practices Guide

Encryption Best Practices

  1. Encryption at Rest: Enable for all data stores
  2. Encryption in Transit: Use TLS 1.2 or higher
  3. Key Rotation: Rotate keys annually
  4. Key Backup: Backup root keys securely
  5. BYOK/KYOK: Use for sensitive workloads
  6. Certificate Management: Automate certificate renewal
  7. Algorithm Selection: Use AES-256 or equivalent

Resources: - πŸ“– Encryption Best Practices

Network Security Best Practices

  1. Network Segmentation: Isolate workloads by security level
  2. Defense in Depth: Security groups + ACLs
  3. Private Endpoints: Use VPE for services
  4. Bastion Hosts: Control administrative access
  5. Flow Logs: Monitor network traffic
  6. DDoS Protection: Enable with CIS
  7. WAF Rules: Protect web applications
  8. Regular Scanning: Vulnerability assessments

Resources: - πŸ“– Network Security Best Practices

Container Security Best Practices

  1. Minimal Base Images: Use distroless or minimal images
  2. Vulnerability Scanning: Scan before deployment
  3. Image Signing: Verify image integrity
  4. Non-Root Containers: Run as non-privileged user
  5. Read-Only Filesystem: Mount root as read-only
  6. Resource Limits: Set CPU and memory limits
  7. Network Policies: Restrict pod communication
  8. Secret Management: Use Secrets Manager

Resources: - πŸ“– Container Security Guide

Compliance Best Practices

  1. Security Posture: Regular SCC scans
  2. Compliance Profiles: Use predefined profiles
  3. Remediation: Track and fix findings
  4. Evidence Collection: Automate compliance evidence
  5. Audit Logging: Comprehensive Activity Tracker
  6. Log Retention: Meet compliance requirements
  7. Regular Assessments: Quarterly compliance reviews
  8. Documentation: Maintain security documentation

Resources: - πŸ“– Compliance Best Practices

Security Tools and CLIs

IBM Cloud CLI Security Commands

# IAM commands
ibmcloud iam users
ibmcloud iam access-groups
ibmcloud iam service-ids
ibmcloud iam api-keys

# Key Protect commands
ibmcloud kp keys
ibmcloud kp key create
ibmcloud kp key rotate

# Container Registry commands
ibmcloud cr images
ibmcloud cr vulnerability-assessment

Resources: - πŸ“– IBM Cloud CLI - πŸ“– Key Protect CLI

Security Scanning Tools

Exam Tips and Strategies

General Preparation

  1. Hands-On Practice: Configure security controls in IBM Cloud
  2. Documentation: Focus on security service documentation
  3. IAM Mastery: Deep understanding of IAM concepts
  4. Compliance: Understand compliance frameworks
  5. Security Patterns: Study security architecture patterns

Key Study Areas

  • IAM policies and access control design
  • Encryption services (Key Protect, HPCS, Secrets Manager)
  • Network security (security groups, ACLs, VPN)
  • Container and Kubernetes security
  • Security monitoring and logging
  • Compliance automation with SCC
  • Certificate and key management
  • App ID and application authentication
  • DDoS and WAF configuration
  • Security best practices for all services

Common Pitfalls to Avoid

  • Confusing security groups (stateful) with ACLs (stateless)
  • Not understanding IAM policy structure
  • Missing encryption key rotation requirements
  • Overlooking compliance requirements
  • Not implementing defense in depth
  • Ignoring audit logging requirements
  • Misconfiguring network security rules
  • Not using service-to-service authorization
  • Hardcoding credentials instead of using Secrets Manager

Exam Day Tips

  1. Read security scenarios carefully
  2. Identify all security requirements (confidentiality, integrity, availability)
  3. Consider defense in depth approach
  4. Look for least privilege principle
  5. Think about compliance implications
  6. Consider monitoring and auditing needs
  7. Evaluate encryption requirements
  8. Think about incident response
  9. Consider cost vs security trade-offs
  10. Review flagged questions

Additional Learning Resources

Training and Courses

Documentation and Guides

Community and Support

Compliance Resources

Important Exam Topics by Priority

High Priority (Study First)

  1. IAM policies and access control
  2. Key Protect and encryption at rest
  3. Security groups and network ACLs
  4. Security and Compliance Center
  5. Activity Tracker and audit logging
  6. Container image security
  7. Secrets Manager usage
  8. Certificate management
  9. VPN and network security
  10. Multi-factor authentication

Medium Priority (Study Second)

  1. Hyper Protect Crypto Services
  2. App ID authentication
  3. Context-based restrictions
  4. VPC security architecture
  5. Kubernetes security controls
  6. DDoS protection with CIS
  7. WAF configuration
  8. Flow logs and monitoring
  9. Compliance profiles
  10. Virtual Private Endpoints

Lower Priority (If Time Permits)

  1. Hyper Protect Virtual Servers
  2. Advanced HPCS features
  3. Satellite security
  4. Advanced compliance automation
  5. SIEM integration details
  6. Advanced network security scenarios

Security Checklists

Pre-Deployment Security Checklist

  • IAM policies reviewed and approved
  • Service IDs created for applications
  • MFA enabled for all users
  • Network security groups defined
  • Network ACLs configured
  • Encryption at rest enabled
  • Key management strategy defined
  • Certificates provisioned
  • Secrets Manager configured
  • Activity Tracker enabled
  • Log Analysis configured
  • Security scanning scheduled
  • Compliance profile selected
  • DDoS protection enabled
  • Backup encryption verified

Ongoing Security Operations Checklist

  • Weekly vulnerability scans
  • Monthly access reviews
  • Quarterly API key rotation
  • Annual key rotation
  • Daily log analysis
  • Real-time security monitoring
  • Incident response plan tested
  • Compliance scans current
  • Security patches applied
  • Backup restoration tested
  • Security metrics reviewed
  • Audit logs retained per policy

Final Preparation Checklist

  • Master IAM concepts and policies
  • Understand encryption services thoroughly
  • Practice network security configuration
  • Study compliance frameworks
  • Review container security best practices
  • Understand Security and Compliance Center
  • Practice with Activity Tracker
  • Review certificate management
  • Study App ID authentication flows
  • Understand DDoS and WAF
  • Review security architecture patterns
  • Practice security scenarios
  • Take practice exams
  • Review exam objectives
  • Schedule exam appointment

Good luck with your IBM Cloud Security Engineer certification exam!

Remember: Security is not a product but a process. Focus on defense in depth, least privilege, and continuous monitoring. Think like an attacker to defend like a professional.