NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Page info
title
title

Panel
titleContents of this Page
Table of Contents
minLevel2
Panel
titleDocument Information

Author: Craig Stancl
Email: Stancl.craig@mayo.edu
Team: LexEVS
Contract: ST12-1106
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Sign off

Date

Role

CBIIT or Stakeholder Organization

Reviewer's Comments (If disapproved indicate specific areas for improvement.)

---

---

---

---

The purpose of this document is to document the security plan for the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 6.1.

Information Systems Security Plan

A list of the industry standard security controls expected in this product

  • HTTPS
    Multiexcerpt include
    nopaneltrue
    MultiExcerptNameExitDisclaimer
    PageWithExcerptwikicontent:Exit Disclaimer to Include
    REST security (if needed)
    • Possible uses:
      • URI Resolver administration
      • CTS2 Development Framework administration
      • LexEVS REST secure ontology access/token transfer
  • RFC 2196
    Multiexcerpt include
    nopaneltrue
    MultiExcerptNameExitDisclaimer
    PageWithExcerptwikicontent:Exit Disclaimer to Include
    • Specifiically, section 3.1.2 Separation of Services
      Multiexcerpt include
      nopaneltrue
      MultiExcerptNameExitDisclaimer
      PageWithExcerptwikicontent:Exit Disclaimer to Include
      • This architecture will allow services to be separated to those needing to be exposed externally and those that do not.
      • Services NOT to expose externally:
        • URI Resolver administration
        • CTS2 Development Framework administration

The components of the CBIIT technologies used for security controls

None

Any expected deviation from the standards

None