Secure Software Deployment Operations And Management practice questions

Upgrade the SSL/TLS certificate to a higher bit-length.

Why wrong: Upgrading the certificate does not fix insecure cryptographic usage within the application code.

Enable HTTP/2 protocol enforcement on the WAF load balancer.

Why wrong: Protocol enforcement does not address application-level cryptographic vulnerabilities.

Disable the WAF's logging feature to improve response time during the incident.

Why wrong: Disabling logging hinders forensic analysis and incident response.

Clear the application's cache to remove any temporary sensitive data.

Why wrong: Cache clearing does not address the underlying credential compromise.

Increase the logging level to 'DEBUG' to track the attacker's actions.

Why wrong: Increasing logging might reveal even more sensitive data in logs.

Re-deploy the application using the same configuration to ensure a clean state.

Why wrong: Re-deploying with the same credentials does not stop the attacker who already possesses them.

Check the file timestamp using the operating system's file system metadata.

Why wrong: Timestamps are easily manipulated by attackers.

Upload the artifact to a public VirusTotal scan before deploying.

Why wrong: VirusTotal checks for known malware, not the integrity of your specific build artifacts.

Compare the file size of the artifact with the size listed in the manifest file.

Why wrong: File size is trivial to spoof.

Enable the Kubernetes Audit Log and monitor for kubectl exec commands.

Why wrong: Audit logs detect the activity but do not provide network-level isolation.

Configure PodSecurityPolicies to restrict the containers to non-root users.

Why wrong: PodSecurityPolicies focus on runtime privilege, not network traffic egress.

Install a Service Mesh like Istio to enforce mTLS.

Why wrong: mTLS secures the communication channel, but does not inherently restrict egress destinations unless combined with egress gateways.

Reducing the total cost of ownership of the cloud infrastructure.

Why wrong: While cost is important, it is not the primary focus of security-focused configuration management.

Ensuring that developers have administrative access to production databases.

Why wrong: This would be a violation of the principle of least privilege.

Maximizing the number of features delivered in each release.

Why wrong: Feature delivery is a goal of development, not specifically secure configuration.

Configure a post-deployment notification to Slack using a webhook.

Why wrong: Notifications alert staff but do not prevent the insecure deployment.

Manually verify image signatures using Docker Content Trust after deployment.

Why wrong: Manual verification is not scalable and occurs after the risk has been introduced.

Enable Jenkins 'Build periodically' to scan images in the registry.

Why wrong: Periodic scanning is reactive, not a preventative gate in the deployment pipeline.

Rename the state file to 'secret.tfstate' to hide it from attackers.

Why wrong: Security through obscurity is ineffective.

Store state files in a version-controlled Git repository for change tracking.

Why wrong: Storing secrets in Git is a major security risk.

Manually delete the state file after every Terraform apply command.

Why wrong: Deleting the state file prevents subsequent infrastructure updates and is not a viable lifecycle practice.

Hardcode the credentials in the application code and use AWS KMS to encrypt the binary at rest.

Why wrong: Hardcoding credentials is a security anti-pattern, regardless of disk encryption.

Use the Elastic Beanstalk Console to set plain-text environment properties.

Why wrong: Plain-text environment variables are visible to anyone with console access.

Store credentials in the .ebextensions/environment.config file with read-only permissions.

Why wrong: Config files are stored in source control and are not suitable for sensitive secrets.

Immediately shut down the Blue environment to save costs.

Why wrong: Shutting down too early prevents an immediate rollback if the Green environment fails.

Update the load balancer configuration to point to both environments simultaneously.

Why wrong: This defeats the purpose of the traffic switch and may expose users to an unverified environment.

Ensure both environments use the same shared database instance.

Why wrong: Shared databases can lead to data corruption or cross-contamination during the transition.

Run all build processes in an isolated network segment without internet access.

Why wrong: While secure, this prevents the fetching of legitimate external dependencies.

Use only open-source software libraries.

Why wrong: Open-source libraries are the vector for dependency confusion.

Regularly scan the public registries for malicious packages.

Why wrong: Scanning public registries is reactive and cannot keep up with thousands of malicious uploads.

To act as a backup for the main container if it crashes.

Why wrong: This is the role of orchestration replication, not sidecars.

To provide additional CPU and memory resources to the main container.

Why wrong: Sidecars add overhead, they do not provide additional compute resources.

To store persistent data for the main application.

Why wrong: Persistent storage is managed via volumes and claims, not sidecars.

An increase in the number of developers logged into the system.

Why wrong: Developer login activity is generally unrelated to external DoS attacks.

A decrease in CPU utilization across all servers.

Why wrong: Lower utilization is the opposite of a typical DoS impact.

A reduction in database write operations.

Why wrong: This could be an application logic issue, not necessarily a security event.

A list of all developers who worked on the release.

Why wrong: Developer names are not part of the secure deployment plan.

A plan for decommissioning all previous versions of the software.

Why wrong: Decommissioning is important but secondary to the ability to recover from a bad release.

An automated script that changes the administrator password on every server.

Why wrong: Changing passwords blindly can break system dependencies.

Store all application logs in a publicly accessible S3 bucket for easy debugging.

Why wrong: Public buckets are a leading cause of data breaches.

Delete all logs after 24 hours to ensure compliance with the Right to be Forgotten.

Why wrong: Short retention periods may hinder incident investigation and compliance auditing.

Increase the log verbosity to the maximum level in production indefinitely.

Why wrong: Verbose logging can inadvertently capture sensitive data and consumes excessive storage.

Run the Java application as the root user to ensure all permissions are available.

Why wrong: Running as root is a critical security vulnerability.

Disable the Java Virtual Machine's garbage collection to prevent memory-based attacks.

Why wrong: Disabling garbage collection will cause a denial of service.

Assign a public IP address to the application server to facilitate remote debugging.

Why wrong: Exposing management interfaces to the internet is a severe security risk.

Embed hardcoded credentials for the database in the build artifact to ensure connectivity.

Why wrong: Hardcoded credentials are a major vulnerability.

Bypass unit tests to speed up the deployment pipeline.

Why wrong: Bypassing tests compromises quality and security assurance.

Compile the code with debugging symbols enabled for easier production troubleshooting.

Why wrong: Debugging symbols can leak intellectual property and assist attackers.

Disabling all automated deployment pipelines.

Why wrong: Manual deployment is prone to error and inconsistency.

Allowing manual configuration changes via the SSH console.

Why wrong: Manual changes lead directly to configuration drift.

Share all internal server IP addresses in the public DNS records.

Why wrong: This exposes internal topology to attackers.

Permit all inbound traffic on port 80 to ensure maximum availability.

Why wrong: Allowing all traffic on port 80 is insecure.

Disable all egress traffic from the application servers to prevent data exfiltration.

Why wrong: Total egress blocking breaks legitimate functionality; granular filtering is required.

Granting 'Admin' privileges to all developers on the CI/CD server.

Why wrong: Least privilege is required for the pipeline management.

Storing pipeline secrets in plain text within the Jenkinsfile.

Why wrong: Secrets must be stored in secure vaults.

Disabling all security logging to prevent alert fatigue.

Why wrong: Logging is critical for detecting zero-day exploitation.

Relying solely on perimeter-based firewalls for security.

Why wrong: Perimeter security is insufficient for internal or zero-day threats.

Updating the application to the latest version once per year.

Why wrong: Annual updates are insufficient for modern security threats.