WebSocket Security Issues

Live streaming is conducted through:

• HTTP
• Websocket
• TCP
• UDP

Longpolling is the process of:

• Keeing an HTTP connection open until the server has data to push to the client
• Forcing the server to repeat data sends in a UDP model
• A server broadcast technique using TCP as the backbone protocol
• Repeatedly opening and closing sockets to randomize connections

WebSocket is:

• connectionless
• non-persistent
• persistent
• object-oriented

According to the article, which is true of WebSocket?

• Impervious to DDoS attacks
• Ripe for DoS attacks
• Encrypted and secure
• Provides organic authentication service

Which of these are true of WebSocket?

• It allows unencrypted TCP connections
• It is vulnerable to cross-site hijacking
• It allows for data masking as a security feature
• All of these

One security fix for WebSockets is:

• Only allow for secure TCP connections
• Only enable UDP connections
• Only enable one-way TCP connections
• Always use TDM packet switching to confuse external systems

How do you prevent spoofing when using WebSocket?

• Use session-individual, random tokens for authentication
• Use two-factor authentication
• Use HTTPS for handshake
• Disable JAVA scripting