cyber_trackr_live 1.0.2 → 1.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (24) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG-GEM.md +8 -0
  3. data/cyber_trackr_live.gemspec +2 -2
  4. data/lib/cyber_trackr_client/api/api_documentation_api.rb +1 -1
  5. data/lib/cyber_trackr_client/api/cci_api.rb +1 -1
  6. data/lib/cyber_trackr_client/api/documents_api.rb +1 -1
  7. data/lib/cyber_trackr_client/api/rmf_controls_api.rb +1 -1
  8. data/lib/cyber_trackr_client/api/scap_api.rb +1 -1
  9. data/lib/cyber_trackr_client/api_client.rb +1 -1
  10. data/lib/cyber_trackr_client/api_error.rb +1 -1
  11. data/lib/cyber_trackr_client/configuration.rb +1 -1
  12. data/lib/cyber_trackr_client/models/api_documentation.rb +1 -1
  13. data/lib/cyber_trackr_client/models/assessment_procedure.rb +1 -1
  14. data/lib/cyber_trackr_client/models/cci_detail.rb +1 -1
  15. data/lib/cyber_trackr_client/models/document_detail.rb +1 -1
  16. data/lib/cyber_trackr_client/models/document_version.rb +1 -1
  17. data/lib/cyber_trackr_client/models/error.rb +1 -1
  18. data/lib/cyber_trackr_client/models/requirement_detail.rb +1 -1
  19. data/lib/cyber_trackr_client/models/requirement_summary.rb +1 -1
  20. data/lib/cyber_trackr_client/models/rmf_control_detail.rb +1 -1
  21. data/lib/cyber_trackr_client/models/rmf_control_list.rb +1 -1
  22. data/lib/cyber_trackr_client/version.rb +2 -2
  23. data/openapi/openapi.yaml +1 -1
  24. metadata +16 -16
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: '0656087226832cd0af299e492e5ff8ea28dd0917361afdea8670462f541e315c'
4
- data.tar.gz: 3bee6d5891a89adf6c4f642bec0b0da57c3fb9571dd32b8cbd171b23e9843a00
3
+ metadata.gz: 9de6b1d50d7a45088d7c2edc2ed83c60a941caa5263f36339bf6c6d46bfef378
4
+ data.tar.gz: 9ce44fef9ecfc3f5efd6689c37fcce019c54a23398a8923728780fbd223cdccb
5
5
  SHA512:
6
- metadata.gz: d6d2bcff53dcd942e76249019ac7006266a69f2bb19438d467ccc78e805b8ba6f916ad290b2cd47278f9f19b65c0babff3a86054958756fca5f28861b8e062cd
7
- data.tar.gz: c40895f9cb8951e8bc46ace5deaa0c5a8cb1e4943a918edf0d16a8a399e3d04177742668b90259212ff98ec2543822b4e5b2fa5c2c5644aa1b7c843e01f72a28
6
+ metadata.gz: 15b1ef805222208f6690ffad0e1fe03532f2d8ebf0c5dc6ff65885d155c703811ce95204419892baf4f4cac6f73c7f37c5def56f46993644e0fccdaf984bcff0
7
+ data.tar.gz: '050939dc960c00d450af4bf9631bd0fbc956cb2c43d0647bf3bcc4f74e0acbd79c22962a9944bdc1e6a9deba1a838c8331901164c6cd08e5df6c16268435b0fb'
data/CHANGELOG-GEM.md CHANGED
@@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [Unreleased]
9
+
10
+ ### Fix
11
+
12
+ - Prevent duplicate gem publication when using OIDC trusted publishing
13
+
14
+ ## [1.0.2] - 2025-08-02
15
+
8
16
  ## [1.0.1] - 2025-08-02
9
17
 
10
18
  ## [1.0.0] - 2025-08-02
data/cyber_trackr_live.gemspec CHANGED
@@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
18
18
  'bug_tracker_uri' => 'https://github.com/mitre/cyber-trackr-live/issues',
19
19
  'changelog_uri' => 'https://github.com/mitre/cyber-trackr-live/blob/main/CHANGELOG-GEM.md',
20
20
  'documentation_uri' => 'https://mitre.github.io/cyber-trackr-live/',
21
- 'homepage_uri' => 'https://github.com/mitre/cyber-trackr-live',
21
+ 'homepage_uri' => 'https://mitre.github.io/cyber-trackr-live/',
22
22
  'source_code_uri' => 'https://github.com/mitre/cyber-trackr-live',
23
23
  'rubygems_mfa_required' => 'true'
24
24
  }
@@ -42,7 +42,6 @@ Gem::Specification.new do |spec|
42
42
  spec.add_dependency 'faraday-follow_redirects', '~> 0.3'
43
43
  spec.add_dependency 'faraday-multipart', '~> 1.0'
44
44
  spec.add_dependency 'marcel', '~> 1.0'
45
- spec.add_dependency 'yard', '~> 0.9'
46
45
 
47
46
  # Development dependencies
48
47
  spec.add_development_dependency 'bundler', '~> 2.0'
@@ -53,4 +52,5 @@ Gem::Specification.new do |spec|
53
52
  spec.add_development_dependency 'rubocop-ast', '~> 1.28'
54
53
  spec.add_development_dependency 'simplecov', '~> 0.22'
55
54
  spec.add_development_dependency 'webmock', '~> 3.0'
55
+ spec.add_development_dependency 'yard', '~> 0.9'
56
56
  end
data/lib/cyber_trackr_client/api/api_documentation_api.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api/cci_api.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api/documents_api.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api/rmf_controls_api.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api/scap_api.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api_client.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/api_error.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/configuration.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/api_documentation.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/assessment_procedure.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/cci_detail.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/document_detail.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/document_version.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/error.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/requirement_detail.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/requirement_summary.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/rmf_control_detail.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/models/rmf_control_list.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
data/lib/cyber_trackr_client/version.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Complete OpenAPI 3.1.1 specification for cyber.trackr.live API. This API provides access to DISA STIGs, SRGs, RMF controls, CCIs, and SCAP data. ## DISA Cybersecurity Ecosystem Hierarchy ``` NIST RMF Controls (high-level policy framework) ↓ (decomposed into atomic, testable statements) CCIs (Control Correlation Identifiers - bridge policy to implementation) ↓ (grouped by technology class into generic requirements) SRGs (Security Requirements Guides - technology class \"what\" to do) ↓ (implemented as vendor-specific \"how\" to do it) STIGs (Security Technical Implementation Guides - vendor/product specific) ↓ (automated versions for scanning tools) SCAP (Security Content Automation Protocol documents) ``` ## Critical Relationships - **RMF Controls** contain assessment procedures that reference **CCIs** - **CCIs** map back to **RMF Controls** and forward to **STIG/SRG requirements** - **SRGs** define generic technology requirements that **STIGs** implement specifically - **V-IDs** can appear in both SRG and corresponding STIG (same requirement, different specificity) - **SV-IDs** are XCCDF rule identifiers with revision tracking across document releases
5
5
 
6
- The version of the OpenAPI document: 1.0.2
6
+ The version of the OpenAPI document: 1.0.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.14.0
@@ -11,5 +11,5 @@ Generator version: 7.14.0
11
11
  =end
12
12
 
13
13
  module CyberTrackrClient
14
- VERSION = '1.0.2'
14
+ VERSION = '1.0.3'
15
15
  end
data/openapi/openapi.yaml CHANGED
@@ -17,7 +17,7 @@ info:
17
17
  requirements that **STIGs** implement specifically\n- **V-IDs** can appear in
18
18
  both SRG and corresponding STIG (same requirement, different specificity)\n- **SV-IDs**
19
19
  are XCCDF rule identifiers with revision tracking across document releases\n"
20
- version: 1.0.2
20
+ version: 1.0.3
21
21
  contact:
22
22
  name: Community OpenAPI Documentation
23
23
  url: https://github.com/mitre/inspec-juniper/tree/main/tools/cyber-trackr-api
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cyber_trackr_live
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.2
4
+ version: 1.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - MITRE Corporation
@@ -66,20 +66,6 @@ dependencies:
66
66
  - - "~>"
67
67
  - !ruby/object:Gem::Version
68
68
  version: '1.0'
69
- - !ruby/object:Gem::Dependency
70
- name: yard
71
- requirement: !ruby/object:Gem::Requirement
72
- requirements:
73
- - - "~>"
74
- - !ruby/object:Gem::Version
75
- version: '0.9'
76
- type: :runtime
77
- prerelease: false
78
- version_requirements: !ruby/object:Gem::Requirement
79
- requirements:
80
- - - "~>"
81
- - !ruby/object:Gem::Version
82
- version: '0.9'
83
69
  - !ruby/object:Gem::Dependency
84
70
  name: bundler
85
71
  requirement: !ruby/object:Gem::Requirement
@@ -192,6 +178,20 @@ dependencies:
192
178
  - - "~>"
193
179
  - !ruby/object:Gem::Version
194
180
  version: '3.0'
181
+ - !ruby/object:Gem::Dependency
182
+ name: yard
183
+ requirement: !ruby/object:Gem::Requirement
184
+ requirements:
185
+ - - "~>"
186
+ - !ruby/object:Gem::Version
187
+ version: '0.9'
188
+ type: :development
189
+ prerelease: false
190
+ version_requirements: !ruby/object:Gem::Requirement
191
+ requirements:
192
+ - - "~>"
193
+ - !ruby/object:Gem::Version
194
+ version: '0.9'
195
195
  description: Provides OpenAPI 3.1.1 specification and Ruby client for accessing DISA
196
196
  STIGs, SRGs, RMF controls, CCIs, and SCAP data via the cyber.trackr.live API
197
197
  email:
@@ -244,7 +244,7 @@ metadata:
244
244
  bug_tracker_uri: https://github.com/mitre/cyber-trackr-live/issues
245
245
  changelog_uri: https://github.com/mitre/cyber-trackr-live/blob/main/CHANGELOG-GEM.md
246
246
  documentation_uri: https://mitre.github.io/cyber-trackr-live/
247
- homepage_uri: https://github.com/mitre/cyber-trackr-live
247
+ homepage_uri: https://mitre.github.io/cyber-trackr-live/
248
248
  source_code_uri: https://github.com/mitre/cyber-trackr-live
249
249
  rubygems_mfa_required: 'true'
250
250
  post_install_message: