Roles, Responsibilities and Training


Security and compliance is everyone’s responsibility. JupiterOne is committed to ensuring all workforce members actively address security and compliance in their roles. Statistically, cybersecurity breaches typically start with compromise of end-user computing devices, social engineering, human error or insider threat. Therefore, users are the first line of defense and yet usually the weakest link. As such, training is imperative to assuring an understanding of current best practices, the different types and sensitivities of data, and the sanctions associated with non-compliance.

In this and all related policy documents, the term “employees” and “workforce members” may be used interchangeably to include all full-time and part-time employees in all job roles, contractors and subcontractors, volunteers, interns, managers and executives at JupiterOne.

The Security Officer is responsible for facilitating the development, testing, implementation, training, and oversight of all activities pertaining to JupiterOne’s efforts to be compliant with security and compliance frameworks such as SOC2 Security. The intent of the Security Officer’s responsibilities is to maintain the confidentiality, integrity, and availability of customer data. The Security Officer is appointed by and reports to the Board of Directors and/or the CEO.

JupiterOne has appointed Sounil Yu as the Security Officer. The security committee is chaired by the Security Officer, and represented by the select members of the senior leadership team (Security Officer, Director of Engineering, and Director of Security Engineering).

Policy Statements

JupiterOne policy requires that:

(a) A Security Officer must be appointed to assist in maintaining and enforcing safeguards towards security and compliance.

(b) Security and compliance is the responsibility of all workforce members (including employees, contractors, interns, and managers/executives). All workforce members are required to:

(c) All workforce members are required to report non-compliance of JupiterOne’s policies and procedures to the Security Officer or designee. Individuals that report violations in good faith may not be subjected to intimidation, threats, coercion, discrimination against, or any other retaliatory action as a consequence.

(d) All workforce members are required to cooperate with federal, state and local law enforcement activities and legal investigations. It is strictly prohibited to interfere with investigations through willful misrepresentation, omission of facts, or by the use of threats against any person.

(e) Workforce members found to be in violation of this policy will be subject to sanctions.

(f) Segregation of Duties shall be maintained when applicable to ensure proper checks and balances and minimize conflict of interests. This helps reduces the possibility of fraud and insider threat considerably, and eliminates single points of compromise to critical systems.

Controls and Procedures

Assignment of Roles and the Security Committee

JupiterOne has appointed Sounil Yu as the Security Officer and Deputy Privacy Officer.

The Security Committee is chaired by the Security Officer, and represented by the select members of the senior leadership team, including the Security Officer, Director of Engineering, and Director of Security Engineering.

The Risk Management Team is formed from members of the Security Committee, including the Security Officer, Director of Engineering, and Director of Security Engineering.

Several of these role functions participate in regular review actions, which may be referenced in §Defined Review Periods.

General Responsibilities of the Security Officer

The authority and accountability for JupiterOne’s information security program and privacy program is delegated to the Security Officer. The Security Officer and the security team are required to perform or delegate the following responsibilities:

Workforce Supervision Responsibilities

Although the Security Officer is responsible for implementing and overseeing all activities related to maintaining compliance, it is everyone’s responsibility (i.e. team leaders, supervisors, managers, co-workers, etc.) to supervise all workforce members and any other user of JupiterOne’s systems, applications, servers, workstations, etc. that contain sensitive data.

  1. Monitor workstations and applications for unauthorized use, tampering, and theft and report non-compliance according to the Employee Handbook guidelines.
  2. Assist the Security Officer to ensure appropriate role-based access is provided to all users.
  3. Take all reasonable steps to hire, retain, and promote workforce members and provide access to users who comply with Security regulations and JupiterOne’s security policies and procedures.

Segregation of Duties

JupiterOne has dedicated personnel who have been assigned the job function of security and compliance. Segregation of duties is achieved via a combination of assignment of roles and responsibilities to different personnel, and automated enforcement for software-defined processes.

Segregation of duties and cross-functional review and approval processes serve as a “checks and balances” system: Whenever applicable, reviews and approvals must be obtained from designated personnel separate from the individual performing work on a JupiterOne system or process.

Policy and Compliance Training

  1. The Security Officer facilitates the security training of all workforce members as follows:

    1. New workforce members within their first month of employment.
    2. Existing workforce members annually.
    3. Existing workforce members whose functions are affected by a material change in the policies and procedures, within a month after the material change becomes effective.
    4. Existing workforce members as needed due to changes in security and risk posture of JupiterOne.
  2. The Security Officer reviews the above training requirements annually. RAR1

  3. Documentation of the training session materials and attendees is retained for a minimum of 2 years.

  4. The training sessions focus on, but are not limited to, the following subjects defined in JupiterOne’s security policies and procedures:

    1. NIST Security Rules.
    2. Risk Management procedures and documentation.
    3. Auditing. JupiterOne may monitor access and activities of all users.
    4. Workstations may only be used to perform assigned job responsibilities.
    5. Users are required to report malicious software to the Security Officer immediately.
    6. Users are required to report unauthorized attempts, uses of, and theft of JupiterOne’s systems and/or workstations.
    7. Users are required to report unauthorized access to facilities
    8. Users are required to report noted log-in discrepancies (i.e. application states users last log-in was on a date user was on vacation).
    9. Users may not alter production data, unless authorized to do so by a JupiterOne Customer.
    10. Users are required to understand their role in JupiterOne’s contingency plan.
    11. Users may not share their user names nor passwords with anyone.
    12. Requirements for users to create and change passwords.
    13. Supervisors are required to report terminations of workforce members and other outside users.
    14. Supervisors are required to report a change in a users title, role, department, and/or location.
    15. Procedures to backup customer data.
    16. Secrets management (such as API tokens) and sensitive document encryption procedures.

Ongoing Awareness Training

JupiterOne leverages KnowBe4 to deliver innovative, fun and engaging security awareness content to all employees monthly. Progress is tracked individually for each employee and reported on KnowBe4’s cloud-managed learning platform.

Internal Business Communications

Company-wide updates

JupiterOne holds a company-wide roundtable on a bi-weekly basis (other than holidays and other exceptions) to communicate updates across all aspects of business operations, performance and objectives.

Senior management sends out additional company-wide announcement as appropriate through pre-established internal communication channels such as email or messaging (e.g. Slack #general channel).

Departmental, team and/or project status updates

Regular performance and status updates are communicated by each department, functional team, and/or designated individuals through pre-established channels.

Additionally, each project team maintains team updates at their own committed cadence and channel – for example, daily development standups/scrum or weekly team meetings.