Skip to content

Commit acdb403

Browse files
markz0rmarkz0r
committed
test
2 parents d78e17f + b9e9f29 commit acdb403

3 files changed

Lines changed: 132 additions & 94 deletions

File tree

‎.github/workflows/jekyll-gh-pages.yml‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# Sample workflow for building and deploying a Jekyll site to GitHub Pages
2+
name: Deploy Jekyll with GitHub Pages dependencies preinstalled
3+
4+
on:
5+
# Runs on pushes targeting the default branch
6+
push:
7+
branches: ["main"]
8+
9+
# Allows you to run this workflow manually from the Actions tab
10+
workflow_dispatch:
11+
12+
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
13+
permissions:
14+
contents: read
15+
pages: write
16+
id-token: write
17+
18+
# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
19+
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
20+
concurrency:
21+
group: "pages"
22+
cancel-in-progress: false
23+
24+
jobs:
25+
# Build job
26+
build:
27+
runs-on: ubuntu-latest
28+
steps:
29+
- name: Checkout
30+
uses: actions/checkout@v4
31+
- name: Setup Pages
32+
uses: actions/configure-pages@v5
33+
- name: Build with Jekyll
34+
uses: actions/jekyll-build-pages@v1
35+
with:
36+
source: ./
37+
destination: ./_site
38+
- name: Upload artifact
39+
uses: actions/upload-pages-artifact@v3
40+
41+
# Deployment job
42+
deploy:
43+
environment:
44+
name: github-pages
45+
url: ${{ steps.deployment.outputs.page_url }}
46+
runs-on: ubuntu-latest
47+
needs: build
48+
steps:
49+
- name: Deploy to GitHub Pages
50+
id: deployment
51+
uses: actions/deploy-pages@v4

‎CNAME‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
www.osm.dev

‎profile/README.md‎

Lines changed: 80 additions & 94 deletions
Original file line numberDiff line numberDiff line change
@@ -1,94 +1,80 @@
1-
<p align="center">
2-
<img src="https://raw.githubusercontent.com/OrganisationServiceManagement/.github/main/assets/osm-banner.svg" alt="Organisation Service Management (OSM)" width="100%">
3-
</p>
4-
5-
<h1 align="center">Organisation Service Management (OSM)</h1>
6-
7-
<p align="center">
8-
<em>Standards-aligned automation and configuration for Governance, Risk, Compliance, IT Operations, and Business Continuity</em>
9-
</p>
10-
11-
---
12-
13-
# Organisation Service Management (OSM)
14-
15-
**Organisation Service Management (OSM)** is a framework, methodology, and set of tools for aligning organisational governance, risk, compliance, IT operations, and business continuity into a cohesive system.
16-
17-
We build open, modular, and standards-aligned solutions that help organisations achieve:
18-
19-
- **ISO/IEC 27001:2022** Information Security Management
20-
- **ISO/IEC 27002:2022** Information Security Controls
21-
- **ISO 22301:2019** Business Continuity Management
22-
- **ACSC ISM & Essential Eight** uplift
23-
- Trusted Service Criteria and other regulatory/compliance mandates
24-
25-
---
26-
27-
## 🔹 What is OSM?
28-
29-
OSM is an **automation and configuration suite** that integrates:
30-
31-
- Governance, Risk, and Compliance (GRC)
32-
- IT operations and service management
33-
- Vendor and dependency management
34-
- Strategic objectives, enterprise reporting, and risk management
35-
36-
It uses a **configuration-as-code** approach to ensure:
37-
38-
- Repeatability
39-
- Auditability
40-
- Alignment to international standards
41-
- Full tenant ownership and portability (no vendor lock-in)
42-
43-
---
44-
45-
## 🔹 Why OSM?
46-
47-
Organisations today face duplicated, fragmented, and manual processes across compliance, risk, and IT service management. OSM:
48-
49-
- Automates manual repetition (e.g. “for all X with Y, conduct Z”)
50-
- Centralises and reconciles data from cloud, endpoint, and service providers
51-
- Provides executive visibility through structured reporting
52-
- Helps organisations evidence compliance and certification efficiently
53-
54-
---
55-
56-
## 🔹 Key Modules
57-
58-
- **GRCosm** – Information Security & Risk Management (ISO 27001 aligned)
59-
- **HRosm** – People, Roles, Training, and Competence Management
60-
- **VLNosm** – Vendor and Third-Party Management
61-
- **CMosm** – Configuration and Change Management
62-
- **OSM Orchestrator** – Automation, scheduling, synchronisation, and disaster recovery support
63-
64-
---
65-
66-
## 🔹 Who is OSM for?
67-
68-
- **Small to medium technology businesses** without dedicated security or risk teams
69-
- **Service providers and registrars** under ISO 27001, ACSC ISM, or auDA compliance requirements
70-
- **Organisations integrating with** Atlassian, Microsoft 365, AWS, Azure, PagerDuty, Tenable, Intruder.io, and other tooling
71-
72-
---
73-
74-
## 🔹 Our Difference
75-
76-
Unlike traditional GRC/IRM tools (e.g. ServiceNow, Archer, Vanta):
77-
78-
- OSM **integrates with your existing stack** rather than replacing or adding to it
79-
- Is **agnostic and customer-controlled** – your tenancy, your data
80-
- Includes an **OSM Guardian consultant model** for deployment, maintenance, and accreditation support
81-
82-
---
83-
84-
## 🚀 Get Involved
85-
86-
This GitHub organisation hosts:
87-
88-
- Core schemas and configuration templates
89-
- Reference implementations
90-
- Connectors and orchestrators
91-
- Documentation and knowledge artefacts
92-
93-
We welcome collaboration with organisations, auditors, and practitioners who want to streamline compliance and operations without unnecessary complexity, contact <tech@osm.dev>
94-
for more information.
1+
<p align="center">
2+
<img src="https://raw.githubusercontent.com/OrganisationServiceManagement/.github/main/assets/osm-logo.svg" alt="Organisation Service Management (OSM)" width="100%">
3+
</p>
4+
^M
5+
6+
<h1 align="center">Organisation Service Management (OSM)</h1>
7+
8+
<p align="center">
9+
<em>Standards-aligned automation and configuration for Governance, Risk, Compliance, IT Operations, and Business Continuity</em>
10+
</p>
11+
---
12+
13+
**Organisation Service Management (OSM)** is a framework, methodology, and set of tools for aligning organisational governance, risk, compliance, IT operations, and business continuity into a cohesive system.
14+
15+
We build open, modular, and standards-aligned solutions that help organisations achieve:
16+
17+
- **ISO/IEC 27001:2022** Information Security Management
18+
- **ISO/IEC 27002:2022** Information Security Controls
19+
- **ISO 22301:2019** Business Continuity Management
20+
- **ACSC ISM & Essential Eight** uplift
21+
- Trusted Service Criteria and other regulatory/compliance mandates
22+
23+
## 🔹 What is OSM?
24+
25+
OSM is an **automation and configuration suite** that integrates:
26+
27+
- Governance, Risk, and Compliance (GRC)
28+
- IT operations and service management
29+
- Vendor and dependency management
30+
- Strategic objectives, enterprise reporting, and risk management
31+
32+
It uses a **configuration-as-code** approach to ensure:
33+
34+
- Repeatability
35+
- Auditability
36+
- Alignment to international standards
37+
- Full tenant ownership and portability (no vendor lock-in)
38+
39+
## 🔹 Why OSM?
40+
41+
Organisations today face duplicated, fragmented, and manual processes across compliance, risk, and IT service management. OSM:
42+
43+
- Automates manual repetition (e.g. “for all X with Y, conduct Z”)
44+
- Centralises and reconciles data from cloud, endpoint, and service providers
45+
- Provides executive visibility through structured reporting
46+
- Helps organisations evidence compliance and certification efficiently
47+
48+
## 🔹 Key Modules
49+
50+
- **GRCosm** – Information Security & Risk Management (ISO 27001 aligned)
51+
- **HRosm** – People, Roles, Training, and Competence Management
52+
- **VLNosm** – Vendor and Third-Party Management
53+
- **CMosm** – Configuration and Change Management
54+
- **OSM Orchestrator** – Automation, scheduling, synchronisation, and disaster recovery support
55+
56+
## 🔹 Who is OSM for?
57+
58+
- **Small to medium technology businesses** without dedicated security or risk teams
59+
- **Service providers and registrars** under ISO 27001, ACSC ISM, or auDA compliance requirements
60+
- **Organisations integrating with** Atlassian, Microsoft 365, AWS, Azure, PagerDuty, Tenable, Intruder.io, and other tooling
61+
62+
## 🔹 Our Difference
63+
64+
Unlike traditional GRC/IRM tools (e.g. ServiceNow, Archer, Vanta):
65+
66+
- OSM **integrates with your existing stack** rather than replacing or adding to it
67+
- Is **agnostic and customer-controlled** – your tenancy, your data
68+
- Includes an **OSM Guardian consultant model** for deployment, maintenance, and accreditation support
69+
70+
## 🚀 Get Involved
71+
72+
This GitHub organisation hosts:
73+
74+
- Core schemas and configuration templates
75+
- Reference implementations
76+
- Connectors and orchestrators
77+
- Documentation and knowledge artefacts
78+
79+
We welcome collaboration with organisations, auditors, and practitioners who want to streamline compliance and operations without unnecessary complexity, contact <tech@osm.dev>
80+
for more information.

0 commit comments

Comments
 (0)