This role was cloned from Florianutz (https://github.com/florianutz/Ubuntu2004_cis) repo and changed to work with Ubuntu 22.04. 98% of the work done on this role was done by him.
This role is based on 20.04 migration. The tasks are correct in content, but have to be re-sorted to fit the 22.04 Benchmark. Contribution welcome.
Configure Ubuntu 22.04 machine to be CIS compliant. Level 1 and 2 findings will be corrected by default.
This role will make changes to the system that could break things. This is not an auditing tool but rather a remediation tool to be used after an audit has been conducted.
Based on CIS Ubuntu Linux 20.04 LTS Benchmark - v1.0.0 - 07-21-2020 .
- If you like our work but cannot contribute to the code of the role by yourself, please take a moment to rate it in Ansible Galaxy. There you can easily give positive feedback to the developers about their work. Galaxy Community Score
- If you find a bug within the role, but can't fix it yourself, please create a ticket with as many details as possible. Please keep in mind that all developers work on the project in their spare time, and it may take some time to get feedback Issues Page
If you want to install this via the ansible-galaxy
command you'll need to run it like this:
ansible-galaxy install -p roles -r requirements.yml
With this in the file requirements.yml:
- src: https://github.com/florianutz/Ubuntu2004_cis.git
You can find an example playbook below. please read the documentation anyway and check the settings for your case. For example, the default settings uninstall the X server!
- name: Harden Server
hosts: servers
become: yes
roles:
- Ubuntu2204_cis
To run the tasks in this repository, first create this file one level above the repository
(i.e. the playbook .yml and the directory Ubuntu2204_cis
should be next to each other),
then review the file defaults/main.yml
and disable any rule/section you do not wish to execute.
Assuming you named the file site.yml
, run it with:
ansible-playbook site.yml
You should carefully read through the tasks to make sure these changes will not break your systems before running this playbook.
There are many role variables defined in defaults/main.yml. This list shows the most important.
ubuntu2204cis_notauto: Run CIS checks that we typically do NOT want to automate due to the high probability of breaking the system (Default: false)
ubuntu2204cis_section1: CIS - General Settings (Section 1) (Default: true)
ubuntu2204cis_section2: CIS - Services settings (Section 2) (Default: true)
ubuntu2204cis_section3: CIS - Network settings (Section 3) (Default: true)
ubuntu2204cis_section4: CIS - Logging and Auditing settings (Section 4) (Default: true)
ubuntu2204cis_section5: CIS - Access, Authentication and Authorization settings (Section 5) (Default: true)
ubuntu2204cis_section6: CIS - System Maintenance settings (Section 6) (Default: true)
ubuntu2204cis_selinux_disable: false
####These control whether a server should or should not be allowed to continue to run these services
ubuntu2204cis_avahi_server: false
ubuntu2204cis_cups_server: false
ubuntu2204cis_dhcp_server: false
ubuntu2204cis_ldap_server: false
ubuntu2204cis_telnet_server: false
ubuntu2204cis_nfs_server: false
ubuntu2204cis_rpc_server: false
ubuntu2204cis_ntalk_server: false
ubuntu2204cis_rsyncd_server: false
ubuntu2204cis_tftp_server: false
ubuntu2204cis_rsh_server: false
ubuntu2204cis_nis_server: false
ubuntu2204cis_snmp_server: false
ubuntu2204cis_squid_server: false
ubuntu2204cis_smb_server: false
ubuntu2204cis_dovecot_server: false
ubuntu2204cis_httpd_server: false
ubuntu2204cis_vsftpd_server: false
ubuntu2204cis_named_server: false
ubuntu2204cis_allow_autofs: false
ubuntu2204cis_is_mail_server: false
####System network parameters (host only OR host and router)
ubuntu2204cis_is_router: false
####IPv6 required
ubuntu2204cis_ipv6_required: true
ubuntu2204cis_config_aide: true
ubuntu2204cis_aide_cron:
cron_user: root
cron_file: /etc/crontab
aide_job: '/usr/sbin/aide --check'
aide_minute: 0
aide_hour: 5
aide_day: '*'
aide_month: '*'
aide_weekday: '*'
ubuntu2204cis_xwindows_required: no
ubuntu2204cis_openldap_clients_required: false
ubuntu2204cis_telnet_required: false
ubuntu2204cis_talk_required: false
ubuntu2204cis_rsh_required: false
ubuntu2204cis_ypbind_required: false
ubuntu2204cis_rpc_required: false
ubuntu2204cis_time_synchronization: chrony
ubuntu2204cis_time_Synchronization: ntp
ubuntu2204cis_time_synchronization_servers:
- uri: "0.pool.ntp.org"
config: "minpoll 8"
- uri: "1.pool.ntp.org"
config: "minpoll 8"
- uri: "2.pool.ntp.org"
config: "minpoll 8"
- uri: "3.pool.ntp.org"
config: "minpoll 8"
It is not implemented, noexec for /tmp will disrupt apt. /tmp contains executable scripts during package installation
It is disabled by default as it is setting random password for root. To enable it set:
ubuntu2204cis_rule_1_5_3: true
To use other than random password:
ubuntu2204cis_root_password: 'new password'
ubuntu2204cis_firewall: firewalld
ubuntu2204cis_firewall: iptables
ubuntu2204cis_pwquality:
- key: 'minlen'
value: '14'
- key: 'dcredit'
value: '-1'
- key: 'ucredit'
value: '-1'
- key: 'ocredit'
value: '-1'
- key: 'lcredit'
value: '-1'
Developed and testes with Ansible 2.10
Many tags are available for precise control of what is and is not changed.
Some examples of using tags:
# Audit and patch the site
ansible-playbook site.yml --tags="patch"
1 Initial Setup
- 1.1 Filesystem Configuration
- 1.1.1 Disable unused filesystems
- 1.1.1.1 Ensure mounting of cramfs filesystems is disabled (Automated)
- 1.1.1.2 Ensure mounting of freevxfs filesystems is disabled - (Automated)
- 1.1.1.3 Ensure mounting of jffs2 filesystems is disabled (Automated)
- 1.1.1.4 Ensure mounting of hfs filesystems is disabled (Automated)
- 1.1.1.5 Ensure mounting of hfsplus filesystems is disabled - (Automated)
- 1.1.1.6 Ensure mounting of udf filesystems is disabled (Automated)
- 1.1.1.7 Ensure mounting of FAT filesystems is limited (Manual)
- 1.1.2 Ensure /tmp is configured (Automated)
- 1.1.3 Ensure nodev option set on /tmp partition (Automated)
- 1.1.4 Ensure nosuid option set on /tmp partition (Automated)
- 1.1.5 Ensure noexec option set on /tmp partition (Automated)
- 1.1.6 Ensure /dev/shm is configured (Automated)
- 1.1.7 Ensure nodev option set on /dev/shm partition (Automated)
- 1.1.8 Ensure nosuid option set on /dev/shm partition (Automated)
- 1.1.9 Ensure noexec option set on /dev/shm partition (Automated)
- 1.1.10 Ensure separate partition exists for /var (Automated)
- 1.1.11 Ensure separate partition exists for /var/tmp (Automated)
- 1.1.12 Ensure nodev option set on /var/tmp partition (Automated)
- 1.1.13 Ensure nosuid option set on /var/tmp partition (Automated)
- 1.1.14 Ensure noexec option set on /var/tmp partition (Automated)
- 1.1.15 Ensure separate partition exists for /var/log (Automated)
- 1.1.16 Ensure separate partition exists for /var/log/audit - (Automated)
- 1.1.17 Ensure separate partition exists for /home (Automated)
- 1.1.18 Ensure nodev option set on /home partition (Automated)
1.1.19 Ensure nodev option set on removable media partitions (Manual)1.1.20 Ensure nosuid option set on removable media partitions - (Manual)1.1.21 Ensure noexec option set on removable media partitions - (Manual)- 1.1.22 Ensure sticky bit is set on all world-writable directories - (Automated)
- 1.1.23 Disable Automounting (Automated)
- 1.1.24 Disable USB Storage (Automated)
- 1.1.1 Disable unused filesystems
1.2 Configure Software Updates1.2.1 Ensure package manager repositories are configured (Manual)1.2.2 Ensure GPG keys are configured (Manual)
- 1.3 Configure sudo
- 1.3.1 Ensure sudo is installed (Automated)
- 1.3.2 Ensure sudo commands use pty (Automated)
- 1.3.3 Ensure sudo log file exists (Automated)
- 1.4 Filesystem Integrity Checking
- 1.4.1 Ensure AIDE is installed (Automated)
- 1.4.2 Ensure filesystem integrity is regularly checked (Automated)
- 1.5 Secure Boot Settings
- 1.5.1 Ensure bootloader password is set (Automated)
- 1.5.2 Ensure permissions on bootloader config are configured - (Automated)
- 1.5.3 Ensure authentication required for single user mode (Automated)
- 1.6 Additional Process Hardening
- 1.6.1 Ensure XD/NX support is enabled (Automated)
- 1.6.2 Ensure address space layout randomization (ASLR) is enabled - (Automated)
- 1.6.3 Ensure prelink is disabled (Automated)
- 1.6.4 Ensure core dumps are restricted (Automated)
- 1.7 Mandatory Access Control
- 1.7.1 Configure AppArmor
- 1.7.1.1 Ensure AppArmor is installed (Automated)
- 1.7.1.2 Ensure AppArmor is enabled in the bootloader configuration - (Automated)
1.7.1.3 Ensure all AppArmor Profiles are in enforce or complain mode - (Automated)1.7.1.4 Ensure all AppArmor Profiles are enforcing (Automated)
- 1.7.1 Configure AppArmor
- 1.8 Warning Banners
- 1.8.1 Command Line Warning Banners
- 1.8.1.1 Ensure message of the day is configured properly (Automated)
- 1.8.1.2 Ensure local login warning banner is configured properly - (Automated)
- 1.8.1.3 Ensure remote login warning banner is configured properly - (Automated)
- 1.8.1.4 Ensure permissions on /etc/motd are configured (Automated)
- 1.8.1.5 Ensure permissions on /etc/issue are configured (Automated)
- 1.8.1.6 Ensure permissions on /etc/issue.net are configured - (Automated)
- 1.8.1 Command Line Warning Banners
- 1.9 Ensure updates, patches, and additional security software are - installed (Manual)
- 1.10 Ensure GDM is removed or login is configured (Automated)
2 Services
- 2.1 inetd Services
- 2.1.1 Ensure xinetd is not installed (Automated)
- 2.1.2 Ensure openbsd-inetd is not installed (Automated)
- 2.2 Special Purpose Services
- 2.2.1 Time Synchronization
- 2.2.1.1 Ensure time synchronization is in use (Automated)
2.2.1.2 Ensure systemd-timesyncd is configured (Manual)- 2.2.1.3 Ensure chrony is configured (Automated)
- 2.2.1.4 Ensure ntp is configured (Automated)
- 2.2.2 Ensure X Window System is not installed (Automated)
- 2.2.3 Ensure Avahi Server is not installed (Automated)
- 2.2.4 Ensure CUPS is not installed (Automated)
- 2.2.5 Ensure DHCP Server is not installed (Automated)
- 2.2.6 Ensure LDAP server is not installed (Automated)
- 2.2.7 Ensure NFS is not installed (Automated)
- 2.2.8 Ensure DNS Server is not installed (Automated)
- 2.2.9 Ensure FTP Server is not installed (Automated)
- 2.2.10 Ensure HTTP server is not installed (Automated)
- 2.2.11 Ensure IMAP and POP3 server are not installed (Automated)
- 2.2.12 Ensure Samba is not installed (Automated)
- 2.2.13 Ensure HTTP Proxy Server is not installed (Automated)
- 2.2.14 Ensure SNMP Server is not installed (Automated)
- 2.2.15 Ensure mail transfer agent is configured for local-only mode - (Automated)
- 2.2.16 Ensure rsync service is not installed (Automated)
- 2.2.17 Ensure NIS Server is not installed (Automated)
- 2.2.1 Time Synchronization
- 2.3 Service Clients
- 2.3.1 Ensure NIS Client is not installed (Automated)
- 2.3.2 Ensure rsh client is not installed (Automated)
- 2.3.3 Ensure talk client is not installed (Automated)
- 2.3.4 Ensure telnet client is not installed (Automated)
- 2.3.5 Ensure LDAP client is not installed (Automated)
- 2.3.6 Ensure RPC is not installed (Automated)
- 2.4 Ensure nonessential services are removed or masked (Manual)
3 Network Configuration
- 3.1 Disable unused network protocols and devices
- 3.1.1 Disable IPv6 (Manual)
- 3.1.2 Ensure wireless interfaces are disabled (Automated)
- 3.2 Network Parameters (Host-Only)
- 3.2.1 Ensure packet redirect sending is disabled (Automated)
- 3.2.2 Ensure IP forwarding is disabled (Automated)
- 3.3 Network Parameters (Host and Router)
- 3.3.1 Ensure source-routed packets are not accepted (Automated)
- 3.3.2 Ensure ICMP redirects are not accepted (Automated)
- 3.3.3 Ensure secure ICMP redirects are not accepted (Automated)
- 3.3.4 Ensure suspicious packets are logged (Automated)
- 3.3.5 Ensure broadcast ICMP requests are ignored (Automated)
- 3.3.6 Ensure bogus ICMP responses are ignored (Automated)
- 3.3.7 Ensure Reverse Path Filtering is enabled (Automated)
- 3.3.8 Ensure TCP SYN Cookies is enabled (Automated)
- 3.3.9 Ensure IPv6 router advertisements are not accepted (Automated)
- 3.4 Uncommon Network Protocols
- 3.4.1 Ensure DCCP is disabled (Automated)
- 3.4.2 Ensure SCTP is disabled (Automated)
- 3.4.3 Ensure RDS is disabled (Automated)
- 3.4.4 Ensure TIPC is disabled (Automated)
- 3.5 Firewall Configuration
- 3.5.1 Configure UncomplicatedFirewall
- 3.5.1.1 Ensure Uncomplicated Firewall is installed (Automated)
- 3.5.1.2 Ensure iptables-persistent is not installed (Automated)
- 3.5.1.3 Ensure ufw service is enabled (Automated)
- 3.5.1.4 Ensure loopback traffic is configured (Automated)
- 3.5.1.5 Ensure outbound connections are configured (Manual)
- 3.5.1.6 Ensure firewall rules exist for all open ports (Manual)
- 3.5.1.7 Ensure default deny firewall policy (Automated)
3.5.2 Configure nftables3.5.2.1 Ensure nftables is installed (Automated)3.5.2.2 Ensure Uncomplicated Firewall is not installed or disabled - (Automated)3.5.2.3 Ensure iptables are flushed (Manual)3.5.2.4 Ensure a table exists (Automated)3.5.2.5 Ensure base chains exist (Automated)3.5.2.6 Ensure loopback traffic is configured (Automated)3.5.2.7 Ensure outbound and established connections are configured - (Manual)3.5.2.8 Ensure default deny firewall policy (Automated)3.5.2.9 Ensure nftables service is enabled (Automated)3.5.2.10 Ensure nftables rules are permanent (Automated)
3.5.3 Configure iptables3.5.3.1.1 Ensure iptables packages are installed (Automated)3.5.3.1.2 Ensure nftables is not installed (Automated)3.5.3.1.3 Ensure Uncomplicated Firewall is not installed or disabled - (Automated)3.5.3.2.1 Ensure default deny firewall policy (Automated)3.5.3.2.2 Ensure loopback traffic is configured (Automated)3.5.3.2.3 Ensure outbound and established connections are configured - (Manual)3.5.3.2.4 Ensure firewall rules exist for all open ports (Automated)3.5.3.3.1 Ensure IPv6 default deny firewall policy (Automated)3.5.3.3.2 Ensure IPv6 loopback traffic is configured (Automated)3.5.3.3.3 Ensure IPv6 outbound and established connections are - configured (Manual)3.5.3.3.4 Ensure IPv6 firewall rules exist for all open ports - (Manual)
- 3.5.1 Configure UncomplicatedFirewall
4 Logging and Auditing
- 4.1 Configure System Accounting (auditd)
- 4.1.1 Ensure auditing is enabled
- 4.1.1.1 Ensure auditd is installed (Automated)
- 4.1.1.2 Ensure auditd service is enabled (Automated)
- 4.1.1.3 Ensure auditing for processes that start prior to auditd is - enabled (Automated)
- 4.1.1.4 Ensure audit_backlog_limit is sufficient (Automated)
- 4.1.2 Configure Data Retention
- 4.1.2.1 Ensure audit log storage size is configured (Automated)
- 4.1.2.2 Ensure audit logs are not automatically deleted (Automated)
- 4.1.2.3 Ensure system is disabled when audit logs are full - (Automated)
- 4.1.3 Ensure events that modify date and time information are - collected (Automated)
- 4.1.4 Ensure events that modify user/group information are collected - (Automated)
- 4.1.5 Ensure events that modify the system's network environment are - collected (Automated)
- 4.1.6 Ensure events that modify the system's Mandatory Access - Controls are collected (Automated)
- 4.1.7 Ensure login and logout events are collected (Automated)
- 4.1.8 Ensure session initiation information is collected (Automated)
- 4.1.9 Ensure discretionary access control permission modification - events are collected (Automated)
- 4.1.10 Ensure unsuccessful unauthorized file access attempts are - collected (Automated)
- 4.1.11 Ensure use of privileged commands is collected (Automated)
- 4.1.12 Ensure successful file system mounts are collected (Automated)
- 4.1.13 Ensure file deletion events by users are collected (Automated)
- 4.1.14 Ensure changes to system administration scope (sudoers) is - collected (Automated)
- 4.1.15 Ensure system administrator command executions (sudo) are - collected (Automated)
- 4.1.16 Ensure kernel module loading and unloading is collected - (Automated)
- 4.1.17 Ensure the audit configuration is immutable (Automated)
- 4.1.1 Ensure auditing is enabled
- 4.2 Configure Logging
- 4.2.1 Configure rsyslog
- 4.2.1.1 Ensure rsyslog is installed (Automated)
- 4.2.1.2 Ensure rsyslog Service is enabled (Automated)
4.2.1.3 Ensure logging is configured (Manual)- 4.2.1.4 Ensure rsyslog default file permissions configured - (Automated)
4.2.1.5 Ensure rsyslog is configured to send logs to a remote log - host (Automated)4.2.1.6 Ensure remote rsyslog messages are only accepted on - designated log hosts. (Manual)
- 4.2.2 Configure journald
- 4.2.2.1 Ensure journald is configured to send logs to rsyslog - (Automated)
- 4.2.2.2 Ensure journald is configured to compress large log files - (Automated)
- 4.2.2.3 Ensure journald is configured to write logfiles to - persistent disk (Automated)
- 4.2.3 Ensure permissions on all logfiles are configured (Automated)
- 4.2.1 Configure rsyslog
- 4.3 Ensure logrotate is configured (Manual)
- 4.4 Ensure logrotate assigns appropriate permissions (Automated)
5 Access, Authentication and Authorization
- 5.1 Configure time-based job schedulers
- 5.1.1 Ensure cron daemon is enabled and running (Automated)
- 5.1.2 Ensure permissions on /etc/crontab are configured (Automated)
- 5.1.3 Ensure permissions on /etc/cron.hourly are configured - (Automated)
- 5.1.4 Ensure permissions on /etc/cron.daily are configured - (Automated)
- 5.1.5 Ensure permissions on /etc/cron.weekly are configured - (Automated)
- 5.1.6 Ensure permissions on /etc/cron.monthly are configured - (Automated)
- 5.1.7 Ensure permissions on /etc/cron.d are configured (Automated)
- 5.1.8 Ensure cron is restricted to authorized users (Automated)
- 5.1.9 Ensure at is restricted to authorized users (Automated)
- 5.2 Configure SSH Server
- 5.2.1 Ensure permissions on /etc/ssh/sshd_config are configured - (Automated)
- 5.2.2 Ensure permissions on SSH private host key files are - configured (Automated)
- 5.2.3 Ensure permissions on SSH public host key files are configured - (Automated)
- 5.2.4 Ensure SSH LogLevel is appropriate (Automated)
- 5.2.5 Ensure SSH X11 forwarding is disabled (Automated)
- 5.2.6 Ensure SSH MaxAuthTries is set to 4 or less (Automated)
- 5.2.7 Ensure SSH IgnoreRhosts is enabled (Automated)
- 5.2.8 Ensure SSH HostbasedAuthentication is disabled (Automated)
- 5.2.9 Ensure SSH root login is disabled (Automated)
- 5.2.10 Ensure SSH PermitEmptyPasswords is disabled (Automated)
- 5.2.11 Ensure SSH PermitUserEnvironment is disabled (Automated)
- 5.2.12 Ensure only strong Ciphers are used (Automated)
- 5.2.13 Ensure only strong MAC algorithms are used (Automated)
- 5.2.14 Ensure only strong Key Exchange algorithms are used - (Automated)
- 5.2.15 Ensure SSH Idle Timeout Interval is configured (Automated)
- 5.2.16 Ensure SSH LoginGraceTime is set to one minute or less - (Automated)
- 5.2.17 Ensure SSH access is limited (Automated)
- 5.2.18 Ensure SSH warning banner is configured (Automated)
- 5.2.19 Ensure SSH PAM is enabled (Automated)
- 5.2.20 Ensure SSH AllowTcpForwarding is disabled (Automated)
- 5.2.21 Ensure SSH MaxStartups is configured (Automated)
- 5.2.22 Ensure SSH MaxSessions is limited (Automated)
- 5.3 Configure PAM
- 5.3.1 Ensure password creation requirements are configured - (Automated)
- 5.3.2 Ensure lockout for failed password attempts is configured - (Automated)
- 5.3.3 Ensure password reuse is limited (Automated)
- 5.3.4 Ensure password hashing algorithm is SHA-512 (Automated)
- 5.4 User Accounts and Environment
- 5.4.1 Set Shadow Password Suite Parameters
- 5.4.1.1 Ensure password expiration is 365 days or less (Automated)
- 5.4.1.2 Ensure minimum days between password changes is configured - (Automated)
- 5.4.1.3 Ensure password expiration warning days is 7 or more - (Automated)
- 5.4.1.4 Ensure inactive password lock is 30 days or less (Automated)
- 5.4.1.5 Ensure all users last password change date is in the past - (Automated)
- 5.4.2 Ensure system accounts are secured (Automated)
- 5.4.3 Ensure default group for the root account is GID 0 (Automated)
- 5.4.4 Ensure default user umask is 027 or more restrictive - (Automated)
- 5.4.5 Ensure default user shell timeout is 900 seconds or less - (Automated)
- 5.4.1 Set Shadow Password Suite Parameters
5.5 Ensure root login is restricted to system console (Manual)- 5.6 Ensure access to the su command is restricted (Automated)
6 System Maintenance
- 6.1 System File Permissions
6.1.1 Audit system file permissions (Manual)- 6.1.2 Ensure permissions on /etc/passwd are configured (Automated)
- 6.1.3 Ensure permissions on /etc/gshadow- are configured Automated)
- 6.1.4 Ensure permissions on /etc/shadow are configured (Automated)
- 6.1.5 Ensure permissions on /etc/group are configured (Automated)
- 6.1.6 Ensure permissions on /etc/passwd- are configured (Automated)
- 6.1.7 Ensure permissions on /etc/shadow- are configured (Automated)
- 6.1.8 Ensure permissions on /etc/group- are configured (Automated)
- 6.1.9 Ensure permissions on /etc/gshadow are configured (Automated)
6.1.10 Ensure no world writable files exist (Automated)6.1.11 Ensure no unowned files or directories exist (Automated)6.1.12 Ensure no ungrouped files or directories exist (Automated)6.1.13 Audit SUID executables (Manual)6.1.14 Audit SGID executables (Manual)
- 6.2 User and Group Settings
- 6.2.1 Ensure password fields are not empty (Automated)
- 6.2.2 Ensure root is the only UID 0 account (Automated)
- 6.2.3 Ensure root PATH Integrity (Automated)
6.2.4 Ensure all users' home directories exist (Automated)- 6.2.5 Ensure users' home directories permissions are 750 or more - restrictive (Automated)
6.2.6 Ensure users own their home directories (Automated)6.2.7 Ensure users' dot files are not group or world writable - (Automated)- 6.2.8 Ensure no users have .forward files (Automated)
- 6.2.9 Ensure no users have .netrc files (Automated)
6.2.10 Ensure users' .netrc Files are not group or world accessible - (Automated)- 6.2.11 Ensure no users have .rhosts files (Automated)
6.2.12 Ensure aFor ll groups in /etc/passwd exist in /etc/group - (Automated)6.2.13 Ensure no duplicate UIDs exist (Automated)6.2.14 Ensure no duplicate GIDs exist (Automated)6.2.15 Ensure no duplicate user names exist (Automated)6.2.16 Ensure no duplicate group names exist (Automated)6.2.17 Ensure shadow group is empty (Automated)
MIT
This repo originated from work done by MindPointGroup