0_1543246755510_Screenshot_4.jpg
A massive amount of data placed in Hadoop can be accessed by Tableau, a BI tool. Using Hive that supports SQL interface, data in each cluster can be retrieved. Such technology is called live connection. Tableau is directly linked to the data engine in order that big data processing is fluid. This mechanism is useful when data queries are slow, and the data result set is small to medium in size. It is also used for offline analysis. If fast data queries are required, Tableau supports in-memory data, which is placed in between Hadoop and Tableau layers. It is called an indexing engine, which supports data queries against 1,000,000,000 records in milliseconds.

Introducing Platform
a. HTTPS Protocol: Browsers request or upload data to web servers through either HTTP or HTTPS protocol. For HTTPS protocol, data is encrypted between the browser and web server. It stands for HTTP over SSL (Secure socket layer) and implements Public Key Infrastructure. Using the public key to encrypt, corresponding private key can be used to decrypt and vice versa. TEMCO will use HTTPS for all browser to web server communications.

b. Session cookie & HttpOnly flag: The communication between browser and server ends when data is requested and responded. After the communication is over, stateful data is deleted including the login state. To fix this issue, a tiny data file called a cookie file is made and placed on the browser. Permanent cookies have certain duration that can be specified. However, using long lasting cookie for login state can leave a user logged in when the user should be in the logged-out state. Instead, TEMCO will use a session cookie to be sure user’s logged-in session is merely valid for the duration of browser to web server connection. When the connection is closed, session cookies are deleted including any information in it. Since cookies are placed on the browser, they can be manipulated. By using the HttpOnly flag, only the web server can change the content and settings of the session cookies.

c. Log-in password hashing: Username and password are sent to the web server when a user logs in. If the password is placed as-is in the TEMCO’s database, it can be reused when hacked. By hashing the login password, we can protect our users when our database is compromised. During the login, we will hash the input password and match it with our database record.

d. Server security: TEMCO can structure our internal servers in two ways: hosting physical servers at one or more physical spots or by using a cloud service. The first method is susceptible to more attacks because we need to think about the security of the physical spots and the machines. Since TEMCO will own the servers, we must build additional layer of security services to protect us and our users. The problem is hacking technology is increasing at a fast rate, meaning we need one or more security professionals to actively manage the threats. It is not only costly but also ineffective. Instead, we intend to use infrastructure-as-a-service (IaaS) by by using a cloud service like Amazon’s AWS, Google’s Google Cloud, or Microsoft’s Azure.
0_1543246738023_Screenshot_1.jpg

Some special security
TEMCO’s platform proposes to use active and passive temperature loggers. It will make use of ultra-low power RFID to send data using Bluetooth technology. RFID software hacking: When the software installed on RFID is hacked, different data value can be uploaded. To protect it, firmware will be encrypted and only decrypted when activated. The firmware cannot be analyzed by accessing physical flash or memory. In addition, each RFID has different encryption key, which prevents duplication.

##FOR MORE INFORMATION ABOUT THIS PROJECT :

Website: https://www.temco.io/

Whitepaper: https://docsend.com/view/eiawynp

ANN Thread: https://bitcointalk.org/index.php?topic=5027072.0

Telegram: https://web.telegram.org/#/im?p=@temcolabs

Facebook: https://www.facebook.com/TEMCOLABS/

Twitter: https://twitter.com/temcolabs

Reddit: https://www.reddit.com/r/temcolabs/

##AUTHOR PROFILE INFO.:

BitcoinTalk ID: Akxenstrix

BitcoinTalk profile link: https://bitcointalk.org/index.php?action=profile;u=2399252

ETH WALLET ADDRESS: 0x4c04B1d0b2078671AB401a46A6b7200AD10902Ca