Federated Data Sharing Appliance Full Guide

Product Summary Overview

Frequently Asked Questions

Introduction

Welcome to the FAQ for the Federated Data Sharing Appliance (FDSA). This document aims to provide an overview of the key features and functionalities of FDSA, addressing common questions and concerns about its usage. FDSA is designed to facilitate secure and efficient data sharing across organizations through federated data access.

Q1. What is a federated data sharing application?

• The federated data sharing application is a platform that enables multiple organizations or entities to securely and collaboratively share data while retaining control over their own data sources. It allows decentralized data sharing without the need to centralize all data in a single repository.

Q2. How does the federated data sharing application work?

• The application operates on a peer-to-peer model, where each participating organization maintains its data locally and establishes secure connections with other partners. These connections facilitate the exchange of data while adhering to privacy and security protocols.

Q3. What are the main benefits of using a federated data sharing application?

• Enhanced data privacy: Organizations can control access to their data, ensuring that sensitive information remains within their boundaries.
• Decentralized governance: Each participant maintains autonomy over their data, avoiding a single point of control.
• Improved collaboration: Facilitates cross-organizational data sharing and collaboration, fostering innovation and insights.

Q4. What types of data can be shared through this application?

• The application supports sharing structured data (database - PostgreSQL) at this point in time. There are plans for unstructured data (text, documents), and even multimedia content (images, videos), depending on the platform's capabilities, industry demand, resources, and cost in future releases.

Q5. Is data security ensured in a federated data sharing environment?

• Yes, data security is a top priority in a federated data sharing application.The system employs robust encryption, authentication mechanisms, and access controls to protect data during transmission and storage.

Q6. How is data ownership managed in the federated model?

• Each participating organization retains ownership of its data. The federated data sharing application facilitates secure access and usage of data by authorized entities without transferring ownership rights.

Q7. Can I control who accesses my organization's data?

• Absolutely. The application provides fine-grained access controls, allowing you to specify which organizations or users can access specific data sets and under what conditions.

Q8. Is the federated data sharing application compliant with data protection regulations (e.g., GDPR, HIPAA)?

• Yes, the application is designed with data protection regulations in mind. It allows organizations to adhere to relevant data protection laws while exchanging information with other entities.

Q9. How do I get started with the federated data sharing application?

• To get started, contact our team to discuss your organization's needs and see how the application can be tailored to fit your specific data sharing requirements. We will guide you through the setup and integration process to ensure a smooth experience.

Q10. Is FDSA available for download?

• FDSA is ready for consumption. Please follow the steps listed here.

Q11: Where can I learn more about FDSA installation and its features?

• For more information and updates about FDSA, please visit this link site or contact our support team at fdsa.support@alzheimersdata.org.

Q12: What security measures does FDSA offer?

• FDSA incorporates a Built-in Mobile Authenticator for 2-Factor Authentication (2FA), enhancing user login security by requiring a secondary authentication step through a mobile device.

Q13. How does FDSA simplify user administration?

• FDSA streamlines user management through features such as role changes, user disabling, and automatic end-user creation upon Data Access Requests (DAR).

Q14. How does FDSA handle data access requests?

• FDSA enables seamless review, approval, and denial of data access requests, ensuring adherence to data standards through API layers.

FDSA One Page Preview

Installation Guide

Prerequisites for Installing the Federated Data Sharing Appliance

Before you begin the installation process, there are several prerequisites you need to fulfill to ensure a smooth and secure deployment. In this section, we'll walk you through the necessary steps to prepare for the installation, including obtaining a License Key, SSH Key, SSL Certificate, and setting up a Fully Qualified Domain Name (FQDN) and SMTP Server.

Prerequisite 1: System requirements

• OS: Linux -> ubuntu 20.04 LTS or higher; Rocky OS version 8+
• CPU: 4 cores or more
• Memory: 8GB or higher
• Storage: 100GB (Min)
• Privileged access (root access)
• Libraries and Tools: Git 1.8+
• Open Port 443 accessible from the internet

Prerequisite 2: SSL Certificate

An SSL certificate ensures that data transmission between your appliance and users is encrypted and secure. You can obtain an SSL certificate in the following manner:

1. SSL Purchase: Purchase a public SSL/TLS v1.2+ CA Certificate (.crt and .key) from a reputable Certificate Authority (CA) like GoDaddy, DigiCert, or Comodo. Avoid using free solutions like 'Let's Encrypt.'
2. CSR generation: Follow the CA's instructions to generate a Certificate Signing Request (CSR) and submit it. Once approved, you'll receive the SSL certificate files, including the public key, private key, and intermediate certificates. Keep these secure.
3. Certificate Note: When obtaining your SSL certificate, remember to coordinate with your administrator to extract the private key.

Prerequisite 3: Fully Qualified Domain Name and Public IP Address

A Fully Qualified Domain Name (FQDN) is necessary to access your Federated Data Sharing Appliance over the internet. Here's how to set up an FQDN

1. DNS Selection: Choose a domain name registrar (e.g., GoDaddy, Namecheap) and register a domain name.
2. DNS Configuration: Configure the DNS records for your domain to point to your server's public IP address.
3. DNS Resolution: Ensure that your chosen FQDN resolves correctly to your server.
4. Email the FQDN to fdsa.support@alzheimersdata.org for ADWB FAIR Whitelisting. If using a Load Balancer, send the Public facing FQDN.

Prerequisite 4 (OPTIONAL): SMTP Mail Server

NOTE: When you install our default SMTP configuration emails could go to spam since it is a gmail.com address.

An SMTP (Simple Mail Transfer Protocol) mail server is essential for sending email notifications, alerts, and system updates from your Federated Data Sharing Appliance. Setting up an SMTP mail server is crucial for effective communication. Here's how to add it as a prerequisite:

1. Select an SMTP Server: Choose an SMTP server or service provider that meets your needs. Popular choices include Gmail, Microsoft Exchange, or a self-hosted server like Postfix or Sendgrid.
2. Configure SMTP Settings: Obtain SMTP server details such as the hostname or IP address, port number, and encryption settings (SSL/TLS). If you're using a third-party service like Gmail, ensure you have an email account and create an "App Password" or enable "Less Secure Apps" as needed.
3. Set Up SMTP Relay: Depending on your Federated Data Sharing Appliance's requirements, you may need to configure it to use the SMTP server as a relay. This typically involves specifying the SMTP server's details, username, and password for authentication.
4. Testing: Before proceeding with the installation, test your SMTP server's configuration by sending a test email from the command line or through the appliance's settings.
5. Secure SMTP Credentials: Ensure that any credentials (username and password) required to access the SMTP server are stored securely. Use environment variables or a secure credentials manager to protect sensitive information.

Prerequisite 5: SSH Key

In order to get the project we’ll need the SSH Key. Here's how to create one:

1. In the server where FDSA is going to be installed, start the root user mode: sudo su
2. Generate an SSH Key using your email (you can leave the passphrase empty, but it's optional): ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
3. View the generated SSH Key: cat /root/.ssh/id_rsa.pub
4. Copy and send the Public Key to fdsa.support@alzheimersdata.org. Our support team will add your key to the GitHub FDSA-Release repository and notify you when it's ready.

Conclusion:

With these prerequisites in place – your License Key, SSH Key, SSL Certificate, SMTP Server and a properly configured FQDN – you are now well-prepared to proceed with the installation of your Federated Data Sharing Appliance. These essential components will ensure the security, authentication, and accessibility of your data-sharing platform.

Installation Steps