Skip to main content

ISMS Review Management Model

Goal

Use this repository for controlled ISMS documents and use core12-isms-management for action tracking, review evidence, and register records. The review system should be simple now and automation-friendly later.

Review Objects

ObjectWhere it livesReview triggerEvidence
ISMS documentcore12-isms Markdownreview_due frontmatter, material change, audit findingGitHub issue and PR link
AssetManagement issueAnnual/quarterly schedule, ownership change, disposalAsset review issue
IT serviceManagement issueQuarterly/new service/material changeIT Service review issue
Client/digital projectManagement issueQuarterly/new project/material changeWebsite/web app/client review issue
Personnel/vendorManagement issueOnboarding, annual review, termination, contract renewalPersonnel/vendor issue and signed agreement evidence
RiskManagement issueAnnual/quarterly schedule, incident, new service/projectRisk review issue
IncidentManagement issueAs reportedIncident and PIR issues

Minimum Workflow

  1. Document owner reviews policy/procedure content in this repo.
  2. If no content change is needed, open a document-review issue in core12-isms-management, record "no content change", and update last_reviewed/review_due by PR.
  3. If content changes are needed, update the Markdown document, open a PR, link the review issue, and update metadata.
  4. If the review identifies an operational gap, open or update a risk, asset, service, personnel, vendor, or migration issue in core12-isms-management.
  5. Monthly summary automation reports reviews due, overdue records, incidents, and high risks.

Automation Direction

  • Use frontmatter in this repo as the document-review source.
  • Use issue labels and project fields in core12-isms-management as the operational source.
  • Add register:documents and migration:legacy-isms labels to management repo.
  • Have the review-reminder workflow create document-review issues in core12-isms-management using a token with access to that repo.
  • Generate monthly summaries from the management repo, not from static files.