📄
Content Library
  • Uncanny Software
  • Blog Posts
    • Using 1Password to share local secrets
    • How I Maintain OSS Projects
    • A Style Guide For HTML & CSS
    • The Reddit blackout is a lesson in risk management
  • Developer Documentation
    • Balena Push
    • Card Dealer
    • A Guide to Story Point Estimation
    • Guidelines for Translating Your Project using i18next
  • InfoSec Policies
    • Access Control Policy
    • Information Classification Policy
    • Password Management Policy
    • Physical Security Policy
    • Business Continuity Policy
    • Information Security Policy
    • Data Classification Standard
    • System Change Management Policy
    • Vendor Management Policy
    • Removable Media
    • Mobile Device Policy
    • Vulnerability Scanning Policy
    • Media Disposal Policy
    • System Hardening Policy
    • Encryption Policy
    • Intellectual Property Policy
  • Management
    • finops
    • information-technology
    • Operations
    • People Management
    • Program Scaling
Powered by GitBook
On this page
  • Purpose
  • Scope
  • Policy
  • Licensed Software
  • Open Source Libraries
  • Roles and Responsibilities
  • Violations
  • References
  • Related Documents
  • Revision History
  1. InfoSec Policies

Intellectual Property Policy

Purpose

The purpose of this policy is to ensure compliance with all legal and contractual requirements related to Intellectual Property (IP) rights and use of proprietary software products.

Scope

This policy covers those software products and libraries utilized in the building of SaaS product offerings to customers and does not include software utilized outside of software development.

Policy

Licensed Software

Where applicable the use of commercial software must comply with all license criteria specified by the vendor (typically through a EULA). If it is source code we will not publish or share the code without the express permission of the vendor. We will not use software that would not allow us to use their libraries or code in a commercial product. All software licenses and/or contracts for usage must be approved by in-house legal and the CFO for signature.

Open Source Libraries

Uncanny Software embraces the open source concept for utilization as long as the open source license does not restrict use in a commercial product. All open source code to be used must be reviewed by the an authorized code owner and tested in a non-client facing environment before utilization in our final product.

Roles and Responsibilities

Uncanny Software Engineering personnel will provide, install, and maintain any such libraries. This is usually done in conjunction with Site Reliability Engineers (SRE) to ensure there is no disruption to service or requires the access only SREs have to production systems

Violations

Any violation of this policy may result in disciplinary action, up to and including termination of employment. Uncanny Software reserves the right to notify the appropriate law enforcement authorities of any unlawful activity and to cooperate in any investigation of such activity. Uncanny Software does not consider conduct in violation of this policy to be within an employee’s or partner’s course and scope of employment, or the direct consequence of the discharge of the employee’s or partner’s duties. Accordingly, to the extent permitted by law, Uncanny Software reserves the right not to defend or pay any damages awarded against employees or partners that result from violation of this policy.

Any employee or partner who is requested to undertake an activity which he or she believes is in violation of this policy, must provide a written or verbal complaint to his or her manager, any other manager or the Human Resources Department as soon as possible.

References

  • ISO 27001:2013 A.18.1.1 Intellectual Property Rights

Related Documents

No documents listed

Revision History

Last updated 1 year ago

Document history via Github