Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Create a new account
      Forgot your password?

Side Menu

  • Overview
  • Roadmap
  • Work packages
  • News
  • Wiki
    • Table of contents
      • Hierarchy leafSprint 1
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leafProduct Requirements
You are here:
  • Wiki
  • Product Requirements

Content

Product Requirements

  • More
    • Print
    • Table of contents
  1. Security event logs collected by the cloud provider are at least: privileged and non-privileged user access activities, authorized and unauthorized access attempts, credentials management operations, system exceptions, information security events retained, traffic related to virtual machines motion.
  2. The cloud provider implements an automated security information and event management / SIEM tool to help identify anomalies and constantly monitoring and detect attacks, potential attacks, and unauthorized connections.
  3. The cloud provider supports delegated authentication for its cloud management system.
  4. The cloud provider ensures that concurrent login sessions are restricted for each user ID.
  5. Security event logs collected by the external supplier’s software are at least: privileged and non-privileged user access activities, authorized and unauthorized access attempts, credentials management operations, system exceptions, information security events retained
  6. The application shall use cryptographic/protection mechanisms (e.g.  cryptographic-signed hash using asymmetric cryptography etc.) to protect the integrity of audit records.
  7. The application shall log authenticated activities (whether successful or not) in order to have evidence of attack attempts or possible abuses.
  8. The application shall be characterized by a detailed data-level analysis (e.g. CRUD matrix etc.).
  9. The application shall be analyzed using automatic code analysis tool to statically identify bugs and vulnerabilities (e.g. through Data Flow Analysis, Control Flow Graph, etc.).
  10. The application components shall be cryptographically signed to ensure integrity and authenticity of modules and releases.
Loading...