-
JupiterOne Security Policies Format and Structure
Similar to the concept of "micro-services", the JupiterOne policies and procedures are written in "micro-docs" that are decoupled from the policies. They are mapped to each other via a JSON configuration. * All policies, procedures and reference documents are written in Markdown. * All configuration files are in JSON…
-
Linking Compliance Policies
In the J1 Compliance app, you can link related policies and procedures from the J1 Policies app to controls. J1 uses this data structure to make connections between written policies and compliance standards: |-- IMPLEMENTS -> security_policy |security_procedure | |-- IMPLEMENTS -> compliance requirement or control See this…
-
Linking Controls to Compliance Requirements
Compliance controls are a series of policies and guidelines that your organization uses to reduce risk and help attain compliance. The J1 centralized controls library provides a single location to manage and use controls across frameworks. At the top of the controls library, you can see the total number of controls in your…
-
Managing Policies and Procedures on JupiterOne
J1 Policies enables you to generate and manage corporate security policies and procedures. It has the following capabilities: * Generating policies and procedures from templates * Managing policies and procedures online * Mapping controls/procedures to compliance requirements * Using the Policy Builder CLI Generating…
-
Searching in the Policies App
The search function in the Policies app allows you to perform OR searches and exact-string searches. OR Searches When you want to perform an OR search, you do not need to use quotation marks. For example, if you are looking for results that contain either “partners”, or “vulnerability”, or both words but not necessarily in…
-
Starter Configurations for Insights Dashboards
J1 provides prebuilt starter configurations for you to use if you did not want to import the JSON file for the dashboard of your choice. The following prebuilt dashboards available are: * AWS Accounts Shows AWS master accounts, sub-accounts, as well as validated/unvalidated external accounts discovered by JupiterOne via…
-
Supporting SOC 2 Audits Using JupiterOne
There are several tasks involved in ensuring your SOC 2 compliance is current and complete. * Configure J1 integrations. * Review your compliance policies and procedures. * Import the SOC 2 compliance framework. * Link compliance controls. * Review linked evidence. * Add additional queries. Configure J1 Integrations The…
-
Using J1 Metadata
JupiterOne adds metadata properties to all data in the J1 system, regardless of how the data was created. All metadata properties begin with an underscore _ and are visible when you click on any asset in J1 Assets. The asset properties drawer opens, and the Metadata tab displays all the metadata for that asset. You can…
-
Using JupiterOne Assessments
JupiterOne Assessments enable you to run multiple questions at the same time to evaluate your security posture based on template, category, or tag. You can also create your own custom assessment by selecting any questions from the J1 managed questions library. Each selected question is evaluated similar to a compliance…
-
Using the Policy Builder CLI
Policy and procedure documents can be managed in code, checked into a Git repository, such that the Git Pull Request (PR) process can be leveraged for revisions and reviews. JupiterOne provides a command line for this purpose. Installing and Building Run the following command to install and build the policies for the first…