Deployment, Cryptography, and AI

Question 1

Secure Installation Practices

Answer 1

Use HTTPS for file downloads and updates
Environment isolation (e.g., dev/test/prod separation)
Database hardening: remove default creds, enforce permissions
Set least privilege access control
Ensure compliance (e.g., GDPR)

Question 2

Confidentiality & Integrity via Cryptography

Answer 2

Confidentiality: Use encryption (AES, RSA) to protect data in transit and storage
Integrity: Use hashing (SHA-256) to ensure data hasn’t changed
Examples:
Encrypted messaging app (confidentiality)
File checksum verification (integrity)

Question 3

Sandboxing & Cryptography

Answer 3

Sandboxing: Runs code in isolated environment to prevent system-wide damage
Cryptography: Secures communication and storage (encryption + hashing)
Examples:
Browser sandboxing tabs
TLS in banking websites

Question 4

Proactive vs Reactive Security

Answer 4

Proactive: Prevent attacks (firewalls, secure coding, training)
Reactive: Respond after attack (incident response, patching)
Comparison:
Proactive: ✅ Safer, ❌ Higher upfront cost
Reactive: ✅ Cheaper upfront, ❌ More damage control

Question 5

Audit Trails and Logging

Answer 5

Audit Trails: Records of actions in system (who did what)
Logs: Data about events and errors
Importance:
Detect intrusions
Aid in debugging
Ensure accountability
Support compliance (e.g., PCI-DSS)