myViewBoard Descripción General de Implementacion de Seguridad

From myViewBoard
Jump to navigation Jump to search

Este documento se proporciona en respuesta a la consulta realizada a ViewSonic para solicitar el desarrollo de seguridad y la arquitectura de implementación para el proyecto myViewBoard. La seguridad y la privacidad son componentes de myViewBoard TM en el diseño, desarrollo y entrega de este servicio.


En este documento describiremos cómo integramos Github, Docker y Circle CI, implementamos una arquitectura segura y escalable en la plataforma Web Service Cloud de Amazon, el protocolo de WebRTC para asegurar nuestro servicio de transmisión y cómo PGP (Pretty GoodPrivacy) está integrado en nuestro archivo seguro compartir y transmitir casos de uso. Este enfoque está diseñado para equilibrar las necesidades de seguridad y confidencialidad de los clientes con la información pública con respecto a las tecnologías y soluciones de terceros que integra myViewBoard.


Ciclo de vida de Implementacion de Seguridad

Security Development Lifecycle es un conjunto de actividades e hitos que pueden generar resultados de seguridad de alta calidad en el desarrollo de productos y servicios. Se puede subdividir en 4 secciones distintas: Arquitectura y diseño, implementación, validación y lanzamiento. Se realiza una revisión después de completar cada etapa. A continuación se detallan las actividades que se deben atender en cada etapa del proceso del Ciclo de vida de desarrollo seguro:

Security lifecycle stages.png

Integración Continua y Pruebas con Servicios en la Nube

Security docker.png

Arquitectura del Producto

Almacenamiento y Gestión de Cifrado de Contraseñas en la Nube

Las medidas de seguridad que dependen del cifrado requieren claves de cifrado. En la nube, como en un sistema local, es esencial que las claves de acceso sean seguras. Al aprovechar el cifrado del lado del servidor con capacidades de almacenamiento y administración de claves de AWS, Amazon Web Services ofrece un servicio HSM en la nube, conocido como AWS CloudHSM.


AWS employs a private network with ssh support for secure access between tiers and is configurable to limit access between tiers.

Referencia: Amazon Web Services


Protegiendo Datos en Transito de Amazon S3

Al igual que la administración de servicios de AWS, se accede a Amazon S3 a través de HTTPS. Esto incluye todas las solicitudes de administración de servicios de Amazon S3, así como la carga útil del usuario, como el contenido de los objetos que se almacenan / recuperan de Amazon S3 y los metadatos asociados. Cuando la consola de servicio de AWS se usa para administrar Amazon S3, se establece una conexión segura SSL / TLS entre el navegador del cliente y el punto final de la consola de servicio. Todo el tráfico posterior está protegido dentro de esta conexión. Cuando las API de Amazon S3 se usan directa o indirectamente, se establece una conexión SSL / TLS entre el cliente y el punto final de Amazon S3. Todo el tráfico subsiguiente HTTP y de carga útil del usuario se encapsula dentro de la sesión protegida.

Reference: Amazon Web Services



Protecting Data in Transit to Amazon RDS

Connecting to Amazon RDS from Amazon EC2 in the same region relies on the security of the AWS network. Connection from the internet uses SSL/TLS for additional protection. SSL/TLS provides peer authentication via server X.509 certificates, data integrity authentication, and data encryption for the client-server connection. SSL/TLS is currently supported for connections to Amazon RDS MySQL and Microsoft SQL instances. For both products, Amazon Web Services provides a single self-signed certificate associated with the MySQL or Microsoft SQL listener. Amazon RDS for Oracle Native Network Encryption encrypts the data as it moves into and out of the database. Oracle Native Network Encryption encrypts network traffic travelling over Oracle Net Services using industry standard encryption algorithms such as AES and Triple DES.

Amazon RDS VPC



Protecting Data in Transit to Amazon DynamoDB

Connecting to DynamoDB from other services from AWS in the same region relies on the security of the AWS network. Connecting to DynamoDB across the internet uses HTTP over SSL/TLS (HTTPS) to connect to DynamoDB service endpoints. Avoid any HTTP for access to DynamoDB and for all connections across the internet.



Secure Streaming Service

WebRTC is a standard drafted by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF) to overcome adoption barriers. The open standard framework eliminates the need for special-purpose client software and onerous plug-ins and downloads. Instead, interactive voice, video, and data-sharing functions are delivered as standard components of the Web developer's toolkit. Ordinary Web developers, who aren't necessarily versed in telephony, can create multimedia communications-enabled applications using simple HTML and JavaScript APIs. End users enjoy an improved experience with no interruptions for downloads, consistent operation across devices and browsers, and immersive communications capabilities.


Browser-based communications eliminates cost and complexity by breaking vendor and platform dependencies, WebRTC fundamentally transforms enterprise communications. Until now, businesses have been limited to expensive PBX desk phones and proprietary softphone clients. While legacy IP-PBX and UC vendors support open standards such as SIP (Session Initiation Protocol), many lock in customers and maximize product margins by reserving full-feature support for proprietary endpoints and separately licensed softphone clients. With more and more workers using smartphones as their primary handset, expensive PBX desk phones are becoming increasingly difficult to justify. What businesses need instead is a way to make smartphones and tablets full-fledged alternatives to traditional PBX phones, however traditional solutions for extending enterprise communications services to mobile devices are costly and inefficient.


Most UC vendors offer operating-system-specific soft clients that take time and money to qualify, deploy, and support. WebRTC overcomes these limitations by bringing real-time communications directly to the browser, eliminating special purpose, OS-specific clients. With WebRTC, IT organizations can accelerate time- to-market and contain costs by efficiently extending enterprise communications services to any browser-enabled device – smartphone, tablet, or PC.


Users can access the WebRTC-enabled service over any network – public or private; WiFi, mobile broadband, or wired LAN. WebRTC reduces upfront IT expenses by containing client licensing fees, qualification efforts, and deployment costs. There are no proprietary clients to purchase, roll out, update, or support. The client application runs on an off-the-shelf “free" browser. Qualification, deployment, and maintenance costs are contained to the Web site. New features and fixes are implemented right on the Web page.



WebRTC Built-in Security Features

In essence, downloading any software from the internet carries an inherent risk that your PC may become infected by a virus, malware, spyware or various other 'bugs'that threaten the security of your data. As such, the principal solution to combat viruses is to install firewalls and anti-malware software that work to defend your computer against any potential threats.


With WebRTC however, there's no need to worry about any of that because since WebRTC works from browser to browser, you don't need to download any software or plugins in order to set up a video conference or VOIP call. All the security that you need is already contained within your browser and the WebRTC platform. Some of the in-built security features contained within the WebRTC platform include:


  • End-to-end encryption between peers
  • Datagram Transport Layer Security (DTLS)
  • Secure Real-Time Protocol (SRTP)


End-to-End Encryption

Encryption is built in to WebRTC as a permanent feature and addresses all security concerns effectively. Regardless of what server or compatible browser you're using, private peer-to-peer communication is safe thanks to WebRTC's advanced end-to-end encryption features.


Data Transport Layer Security (DTLS)

Any data that is transferred through a WebRTC system is encrypted using the Datagram Transport Layer Security method. This encryption is already built into compatible web browsers (Firefox, Chrome, Opera), so that eavesdropping or data manipulation can't happen.


Secure Real-Time Protocol (SRTP)

In addition to offering DTLS encryption, WebRTC also encrypts data through Secure Real-Time Protocol, which safeguards IP communications from hackers, so that your video and audio data is kept private.


Signalling Server

Security signalling server.png


WebRTC Default Case - P2P

This is a true End-To-End encryption (E2E)

Security E2E.png


WebRTC Default Case - TURN

A TURN Sever DOES NOT terminate the encryption. In this case, it's a true End-To- End encryption (E2E)

Security TURN.png


WebRTC Default Case - P2

Security default case p2.png


Addendum

Changes to the system environment:

This document relates exclusively to the details of the product or project specified above. This section is designed to provide requested details on how the product in question interacts with the system environment in question.


This product has software components that are installed in standard user directories. Any exceptions to this are listed below:

  • Crossmatch Fingerprint SDK
  • SQLCipher


This software component also adds or makes modifications to the following system attributes and configurations (such as registry entries, firewall settings, digital certificates, kernel mode drivers, and browser plugins):

  • Registry Keys:
HKEY_LOCAL_MACHINE\SOFTWARE\DigitalPersona\Products\U.are.U RTE 


Services: The following are uses of cryptography:

  • Hashing Algorithms: SHA25
  • Public-Key Algorithms: RSA-204
  • SSL Schemes: TLS 1.2


The following is a list of all known third party components used in this product:

  • WebRTC
  • mqtt
- MQTT 3.1 and 3.1.1 compliant
- QoS 0 and QoS 1