Knowledge Base

Topic: Arcus
Terms of Service

Terms of Service All users registering for an account with CONS3RT are required to review and accept the CONS3RT terms of service and terms of use. Existing users logging into CONS3RT will also be prompted to review and accept the CONS3RT terms of service. This step cannot be bypassed, and accepting the terms of service is required to access CONS3RT. The CONS3RT terms of service governs your use of the websites, content, software, and services offered through CONS3RT.
Software Licenses

Software Licensing in CONS3RT Licensing for systems within CONS3RT falls into one of the 4 categories listed below: 1. Operating Systems – Covered by the cloud provider 2. DoD Wide Licenses – If there is an available DoD wide license (e.g. Tenable Nessus, Java) CONS3RT will take care of the paperwork and request to make it available to the user community 3. Other DoD Licenses – CONS3RT will coordinate user requirements with resources like the Mythics program office so the Government does not pay for licenses it already has
Package Repository

Overview CONS3RT has a package repository available for Red Hat systems. CONS3RT provided Red Hat 7 and Red Hat 6 templates are already registered with this service. Available Packages Packages are available from the following channels: rhel-6-server-rpms rhel-6-server-optional-rpms rhel-6-server-supplementary-rpms rhel-6-server-rh-common-rpms rhel-6-server-extras-rpms rhel-6-server-debug-rpms rhel-7-server-rpms rhel-7-server-optional-rpms rhel-7-server-supplementary-rpms rhel-7-server-rh-common-rpms rhel-7-server-extras-rpms rhel-7-server-debug-rpms rhel-7-server-ansible-2.6-rpms rhel-7-server-dotnet-rpms rhel-7-server-ose-3.11-rpms epel-6 epel-7 Reference The following details about the repository service are for reference: The CONS3RT repository is located here: Arcus Repo.
Storage Service

CONS3RT provides a persistent storage service as an add-on feature. Use this for: Storing persistent data Data accessibility across deployment runs Loading large files (> 3 GB) as part of asset Data backup To request the storage service for your team, please enter a contact support. The CONS3RT team will provide a URL and credentials to access your storage. You can connect to your CONS3RT storage service from Linux using NFS or CIFS (with credentials), or Windows using SMB.
Logging in to Arcus with a Certificate

Arcus uses certificate-based authentication only. There is no username/password access to Arcus. Certificate options are: DoD Common Access Card (CAC) External Certificate Authority (ECA) certificate (more info about obtaining an ECA certificate) Logging in to Arcus First an foremost, ensure your certificate is loaded into your browser If using a CAC, ensure you have the proper middleware installed, and your CAC is inserted into your CAC reader If using an ECA certificate, ensure the certificate has been imported into your browser Navigate to the Arcus site URL https://arcus-cloud.
Deployed System Connectivity

Outbound Connectivity Systems deployed into a cloudspace in one of the local CONS3RT clouds or commercial providers (e.g. AWS GovCloud, Azure, etc.) have the ability to reach out of the enclave to the greater network to access resources. Systems deployed in other DoD cloud providers (e.g. DISA milCloud) are subject to the providers standard rules. Most ports and traffic are allowed, per the latest DoD PPS. If outbound traffic is blocked, submit a support ticket and the request will be reviewed.
vGPU Capabilities

Overview A GPU is a Graphical Processing Unit. It allows computers to better handle graphics-intensive applications, such as web design, video editing, and 3D rendering. A virtual GPU – a vGPU – brings the same functionality to a virtualized system with much greater flexibility in overall capacity and resource availability. CONS3RT has implemented virtual Graphics Processing Unit (vGPU) capabilities to support those users who require additional resources for graphical- or computational-intensive applications.
Source Code Accounts

CONS3RT provides built-in integrations with SoftwareForge and DI2E for building and deploying Source Code assets that use SoftwareForge Subversion or Bitbucket (Stash) as a source code repository. This is done via a site specific account in SoftwareForge and DI2E and simplifies the process for managing the required credentials. To use this integration, the site account must be allowed to access your source code project. SoftwareForge Subversion Access If your subversion repository is open to the Software Forge community, no additonal steps are required If your subversion repository is private: Add the CONS3RTbuildservice user to your Software Forge project Grant the role “Contributor” to the CONS3RTbuildservice user.