PDF p.277
In progress
Secure Protocols
Summary
PDF p.277Secure protocols are essential for protecting data transmitted over networks. Unlike insecure protocols, which transmit data in clear text, secure protocols use encryption to safeguard information. Implementing secure protocols can be complex but is crucial for maintaining network security.
In plain words
Supplementary — not from your PDFInsecure protocols such as HTTP and Telnet send everything, including passwords, in clear text. Secure versions such as HTTPS, SSH and SFTP encrypt it. They're harder to run (certificates, keys, harder troubleshooting), so choose protocols through a formal process: assess risk and data sensitivity, compare security features, decide on ports and TCP or UDP, check that existing security equipment supports them, and document the decision.
Detailed explanation
PDF p.277-
Insecure Protocols
- Examples: HTTP, Telnet.
- Risks: Transmit data in clear text, making it readable by anyone intercepting the data.
-
Secure Protocols
- Examples: HTTPS, SSH.
- Benefits: Use encryption to protect data, ensuring confidentiality and integrity.
- Implementation Challenges: Require obtaining and configuring SSL/TLS certificates, managing cryptographic keys, and troubleshooting encrypted data.
Importance of Secure Protocols
- Protect Sensitive Information: HTTPS protects login credentials and form data on webpages.
- Secure Connections: SSH ensures encrypted communication with servers and equipment.
Implementation Challenges
- Complexity: More difficult to implement and manage compared to insecure protocols.
- Certificate Management: Requires handling SSL/TLS certificates and ensuring they remain valid.
- Troubleshooting: Encrypted data packets are harder to inspect for issues.
Implementing Secure Protocols
Formal Processes
- Risk Assessment: Evaluate risks and review policies.
- Security Features: Assess different protocols' security features.
- Documentation: Document decisions for audits and compliance reviews.
Protocol Selection
- Data Sensitivity: Choose protocols based on data sensitivity (e.g., HTTPS, SSH, SFTP/FTPS).
- Port Configuration: Standard ports (HTTP: 80, HTTPS: 443) can be changed but may complicate configuration.
- Transport Methods: TCP (reliable, connection-oriented) vs. UDP (faster, connectionless).
Considerations
- Encryption Levels: Ensure suitable encryption for data protection.
- Authentication Methods: Implement strong authentication.
- Existing Security Equipment: Consider firewalls and other security measures.
- Balance: Optimize security, maintainability, performance, and cost.
Important terms
taken from the text above- Implementation Challenges
- Require obtaining and configuring SSL/TLS certificates, managing cryptographic keys, and troubleshooting encrypted data.
- Protect Sensitive Information
- HTTPS protects login credentials and form data on webpages.
- Secure Connections
- SSH ensures encrypted communication with servers and equipment.
- Certificate Management
- Requires handling SSL/TLS certificates and ensuring they remain valid.
- Troubleshooting
- Encrypted data packets are harder to inspect for issues.
- Risk Assessment
- Evaluate risks and review policies.
- Security Features
- Assess different protocols' security features.
- Documentation
- Document decisions for audits and compliance reviews.
- Data Sensitivity
- Choose protocols based on data sensitivity (e.g., HTTPS, SSH, SFTP/FTPS).
- Port Configuration
- Standard ports (HTTP: 80, HTTPS: 443) can be changed but may complicate configuration.
- Transport Methods
- TCP (reliable, connection-oriented) vs. UDP (faster, connectionless).
- Encryption Levels
- Ensure suitable encryption for data protection.
- Authentication Methods
- Implement strong authentication.
- Existing Security Equipment
- Consider firewalls and other security measures.
- Balance
- Optimize security, maintainability, performance, and cost.
Examples & real-world scenarios
Supplementary — not from your PDF- Replacing Telnet with SSH for device management.
- Moving an internal web app from HTTP to HTTPS.
- Documenting why SFTP was chosen over FTP.
Scenario
A packet capture on an internal network shows admin passwords in clear text from Telnet sessions. Switching to SSH encrypts the sessions and removes that exposure.
Common mistakes
Supplementary — not from your PDF- Assuming internal traffic doesn't need encryption.
- Forgetting certificate renewal, which causes outages when certificates expire.
Practical skills
Supplementary — not from your PDF- Map insecure protocols to their secure replacements.
What I should remember
Key Points PDF p.277-
Insecure vs. Secure Protocols
- Insecure: HTTP, Telnet (clear text).
- Secure: HTTPS, SSH (encrypted).
-
Implementation Challenges
- Complexity: More difficult to manage.
- Certificate Management: Requires handling SSL/TLS certificates.
- Troubleshooting: Encrypted data is harder to inspect.
-
Protocol Selection
- Data Sensitivity: Choose based on data type.
- Port Configuration: Standard vs. custom ports.
- Transport Methods: TCP vs. UDP.
- Considerations: Encryption, authentication, existing security, balance of factors.