From c802be7dfacc1f34687402e414cc764c6be1bfd1 Mon Sep 17 00:00:00 2001
From: Cryptography Sandbox
<74481788+CryptographySandbox@users.noreply.github.com>
Date: Fri, 1 Dec 2023 21:59:35 +0100
Subject: [PATCH 1/2] Prerelease
---
.devcontainer/devcontainer.json | 43 +
.gitignore | 172 +
CHANGELOG.md | 3 +
Dockerfile | 51 +
LICENSE | 847 +-
README.md | 189 +
c5dec/__init__.py | 36 +
c5dec/assets/acronyms/persons.json | 7 +
c5dec/assets/config.json | 6 +
.../database/KnowledgeBase/0_MapofContent.md | 50 +
c5dec/assets/database/KnowledgeBase/Asset.md | 88 +
.../database/KnowledgeBase/Assumption.md | 32 +
.../database/KnowledgeBase/AttackPotential.md | 0
.../database/KnowledgeBase/ComposedTOE.md | 0
.../KnowledgeBase/CompositeEvaluation.md | 19 +
.../KnowledgeBase/ConformanceClaim.md | 33 +
.../KnowledgeBase/ConformanceStatement.md | 27 +
.../database/KnowledgeBase/DirectRationale.md | 11 +
.../KnowledgeBase/DomainSeparation.md | 0
c5dec/assets/database/KnowledgeBase/EUCC.md | 0
.../KnowledgeBase/EvaluationAssuranceLevel.md | 31 +
.../KnowledgeBase/EvaluationEvidence.md | 0
.../KnowledgeBase/EvaluationEvidenceIndex.md | 0
.../KnowledgeBase/EvaluationMethods.md | 103 +
.../EvaluationTechnicalReport.md | 0
.../KnowledgeBase/Exactconformance-FAQ.md | 69 +
.../ExtendedComponentDefinition.md | 108 +
.../KnowledgeBase/MultiAssuranceEvaluation.md | 11 +
.../KnowledgeBase/NonBypassability.md | 0
.../database/KnowledgeBase/NonTSFPart.md | 0
.../KnowledgeBase/ObservationReport.md | 0
.../KnowledgeBase/Operation-Assignment.md | 16 +
.../KnowledgeBase/Operation-Iteration.md | 8 +
.../KnowledgeBase/Operation-Refinement.md | 14 +
.../KnowledgeBase/Operation-Selection.md | 15 +
.../database/KnowledgeBase/Operations.md | 10 +
.../OrganizationalSecurityPolicy.md | 32 +
.../database/KnowledgeBase/PPConfiguration.md | 0
.../KnowledgeBase/ProtectionProfile.md | 59 +
.../database/KnowledgeBase/Rationale.md | 22 +
.../SecurityAssuranceRequirement.md | 0
.../KnowledgeBase/SecurityComponent.md | 63 +
.../SecurityFunctionalRequirement.md | 0
.../KnowledgeBase/SecurityObjective.md | 48 +
.../SecurityProblemdefinition.md | 50 +
.../database/KnowledgeBase/SecurityTarget.md | 60 +
.../database/KnowledgeBase/SelfProtection.md | 0
.../SingleAssuranceEvaluation.md | 11 +
.../SubTOESecurityFunctionality.md | 0
.../database/KnowledgeBase/TOEBoundary.md | 58 +
.../database/KnowledgeBase/TOEDescription.md | 59 +
.../TOEOperationalEnvironment.md | 34 +
.../database/KnowledgeBase/TOEOverview.md | 71 +
.../database/KnowledgeBase/TOEReference.md | 23 +
.../KnowledgeBase/TOESecurityFunctionality.md | 37 +
.../KnowledgeBase/TOESummarySpecification.md | 114 +
.../database/KnowledgeBase/TSFInterface.md | 37 +
.../KnowledgeBase/TargetofEvaluation.md | 62 +
c5dec/assets/database/KnowledgeBase/Threat.md | 66 +
.../KnowledgeBase/ThreatModeling-TR15446.md | 146 +
.../KnowledgeBase/_figures/AssetDef.png | Bin 0 -> 72168 bytes
.../KnowledgeBase/_figures/MappingCCtoCEM.png | Bin 0 -> 12862 bytes
.../database/SecurityControls/.doorstop.yml | 6 +
.../SecurityControls/CC2022/.doorstop.yml | 6 +
.../SecurityControls/CC2022/CC-001.md | 13 +
.../SecurityControls/CC2022/SAR/.doorstop.yml | 15 +
.../SecurityControls/CC2022/SAR/ACC-001.md | 18 +
.../SecurityControls/CC2022/SAR/ACC-002.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-003.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-004.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-005.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-006.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-007.md | 17 +
.../SecurityControls/CC2022/SAR/ACC-008.md | 18 +
.../SecurityControls/CC2022/SAR/ACC-009.md | 17 +
.../CC2022/SAR/component/.doorstop.yml | 19 +
.../CC2022/SAR/component/ACOM-001.md | 17 +
.../CC2022/SAR/component/ACOM-002.md | 18 +
.../CC2022/SAR/component/ACOM-003.md | 17 +
.../CC2022/SAR/component/ACOM-004.md | 17 +
.../CC2022/SAR/component/ACOM-005.md | 17 +
.../CC2022/SAR/component/ACOM-006.md | 17 +
.../CC2022/SAR/component/ACOM-007.md | 18 +
.../CC2022/SAR/component/ACOM-008.md | 18 +
.../CC2022/SAR/component/ACOM-009.md | 17 +
.../CC2022/SAR/component/ACOM-010.md | 18 +
.../CC2022/SAR/component/ACOM-011.md | 17 +
.../CC2022/SAR/component/ACOM-012.md | 17 +
.../CC2022/SAR/component/ACOM-013.md | 17 +
.../CC2022/SAR/component/ACOM-014.md | 17 +
.../CC2022/SAR/component/ACOM-015.md | 18 +
.../CC2022/SAR/component/ACOM-016.md | 18 +
.../CC2022/SAR/component/ACOM-017.md | 18 +
.../CC2022/SAR/component/ACOM-018.md | 18 +
.../CC2022/SAR/component/ACOM-019.md | 17 +
.../CC2022/SAR/component/ACOM-020.md | 18 +
.../CC2022/SAR/component/ACOM-021.md | 17 +
.../CC2022/SAR/component/ACOM-022.md | 17 +
.../CC2022/SAR/component/ACOM-023.md | 17 +
.../CC2022/SAR/component/ACOM-024.md | 17 +
.../CC2022/SAR/component/ACOM-025.md | 17 +
.../CC2022/SAR/component/ACOM-026.md | 18 +
.../CC2022/SAR/component/ACOM-027.md | 18 +
.../CC2022/SAR/component/ACOM-028.md | 18 +
.../CC2022/SAR/component/ACOM-029.md | 17 +
.../CC2022/SAR/component/ACOM-030.md | 17 +
.../CC2022/SAR/component/ACOM-031.md | 17 +
.../CC2022/SAR/component/ACOM-032.md | 17 +
.../CC2022/SAR/component/ACOM-033.md | 17 +
.../CC2022/SAR/component/ACOM-034.md | 17 +
.../CC2022/SAR/component/ACOM-035.md | 19 +
.../CC2022/SAR/component/ACOM-036.md | 19 +
.../CC2022/SAR/component/ACOM-037.md | 18 +
.../CC2022/SAR/component/ACOM-038.md | 18 +
.../CC2022/SAR/component/ACOM-039.md | 20 +
.../CC2022/SAR/component/ACOM-040.md | 20 +
.../CC2022/SAR/component/ACOM-041.md | 20 +
.../CC2022/SAR/component/ACOM-042.md | 18 +
.../CC2022/SAR/component/ACOM-043.md | 17 +
.../CC2022/SAR/component/ACOM-044.md | 17 +
.../CC2022/SAR/component/ACOM-045.md | 17 +
.../CC2022/SAR/component/ACOM-046.md | 18 +
.../CC2022/SAR/component/ACOM-047.md | 18 +
.../CC2022/SAR/component/ACOM-048.md | 19 +
.../CC2022/SAR/component/ACOM-049.md | 18 +
.../CC2022/SAR/component/ACOM-050.md | 17 +
.../CC2022/SAR/component/ACOM-051.md | 17 +
.../CC2022/SAR/component/ACOM-052.md | 18 +
.../CC2022/SAR/component/ACOM-053.md | 18 +
.../CC2022/SAR/component/ACOM-054.md | 21 +
.../CC2022/SAR/component/ACOM-055.md | 21 +
.../CC2022/SAR/component/ACOM-056.md | 21 +
.../CC2022/SAR/component/ACOM-057.md | 19 +
.../CC2022/SAR/component/ACOM-058.md | 19 +
.../CC2022/SAR/component/ACOM-059.md | 19 +
.../CC2022/SAR/component/ACOM-060.md | 19 +
.../CC2022/SAR/component/ACOM-061.md | 19 +
.../CC2022/SAR/component/ACOM-062.md | 17 +
.../CC2022/SAR/component/ACOM-063.md | 17 +
.../CC2022/SAR/component/ACOM-064.md | 17 +
.../CC2022/SAR/component/ACOM-065.md | 17 +
.../CC2022/SAR/component/ACOM-066.md | 18 +
.../CC2022/SAR/component/ACOM-067.md | 18 +
.../CC2022/SAR/component/ACOM-068.md | 17 +
.../CC2022/SAR/component/ACOM-069.md | 17 +
.../CC2022/SAR/component/ACOM-070.md | 17 +
.../CC2022/SAR/component/ACOM-071.md | 17 +
.../CC2022/SAR/component/ACOM-072.md | 18 +
.../CC2022/SAR/component/ACOM-073.md | 17 +
.../CC2022/SAR/component/ACOM-074.md | 17 +
.../CC2022/SAR/component/ACOM-075.md | 17 +
.../CC2022/SAR/component/ACOM-076.md | 18 +
.../CC2022/SAR/component/ACOM-077.md | 20 +
.../CC2022/SAR/component/ACOM-078.md | 20 +
.../CC2022/SAR/component/ACOM-079.md | 20 +
.../CC2022/SAR/component/ACOM-080.md | 19 +
.../CC2022/SAR/component/ACOM-081.md | 19 +
.../CC2022/SAR/component/ACOM-082.md | 19 +
.../CC2022/SAR/component/ACOM-083.md | 19 +
.../CC2022/SAR/component/ACOM-084.md | 18 +
.../CC2022/SAR/component/ACOM-085.md | 19 +
.../CC2022/SAR/component/ACOM-086.md | 20 +
.../CC2022/SAR/component/ACOM-087.md | 20 +
.../CC2022/SAR/component/ACOM-088.md | 20 +
.../CC2022/SAR/component/ACOM-089.md | 17 +
.../CC2022/SAR/component/ACOM-090.md | 19 +
.../CC2022/SAR/component/ACOM-091.md | 19 +
.../CC2022/SAR/component/ACOM-092.md | 19 +
.../CC2022/SAR/component/ACOM-093.md | 19 +
.../CC2022/SAR/component/ACOM-094.md | 19 +
.../CC2022/SAR/component/ACOM-095.md | 17 +
.../CC2022/SAR/component/ACOM-096.md | 18 +
.../CC2022/SAR/component/ACOM-097.md | 18 +
.../CC2022/SAR/component/ACOM-098.md | 18 +
.../CC2022/SAR/component/ACOM-099.md | 18 +
.../CC2022/SAR/component/ACOM-100.md | 17 +
.../CC2022/SAR/component/ACOM-101.md | 17 +
.../CC2022/SAR/component/ACOM-102.md | 19 +
.../CC2022/SAR/component/ACOM-103.md | 19 +
.../CC2022/SAR/component/ACOM-104.md | 17 +
.../CC2022/SAR/component/ACOM-105.md | 17 +
.../CC2022/SAR/component/ACOM-106.md | 17 +
.../CC2022/SAR/creq/.doorstop.yml | 11 +
.../CC2022/SAR/creq/CREQ-001.md | 15 +
.../CC2022/SAR/creq/CREQ-002.md | 15 +
.../CC2022/SAR/creq/CREQ-003.md | 15 +
.../CC2022/SAR/creq/CREQ-004.md | 15 +
.../CC2022/SAR/creq/CREQ-005.md | 15 +
.../CC2022/SAR/creq/CREQ-006.md | 15 +
.../CC2022/SAR/creq/CREQ-007.md | 15 +
.../CC2022/SAR/creq/CREQ-008.md | 15 +
.../CC2022/SAR/creq/CREQ-009.md | 15 +
.../CC2022/SAR/creq/CREQ-010.md | 15 +
.../CC2022/SAR/creq/CREQ-011.md | 15 +
.../CC2022/SAR/creq/CREQ-012.md | 15 +
.../CC2022/SAR/creq/CREQ-013.md | 15 +
.../CC2022/SAR/creq/CREQ-014.md | 15 +
.../CC2022/SAR/creq/CREQ-015.md | 15 +
.../CC2022/SAR/creq/CREQ-016.md | 15 +
.../CC2022/SAR/creq/CREQ-017.md | 15 +
.../CC2022/SAR/creq/CREQ-018.md | 15 +
.../CC2022/SAR/creq/CREQ-019.md | 15 +
.../CC2022/SAR/creq/CREQ-020.md | 15 +
.../CC2022/SAR/creq/CREQ-021.md | 15 +
.../CC2022/SAR/creq/CREQ-022.md | 15 +
.../CC2022/SAR/creq/CREQ-023.md | 15 +
.../CC2022/SAR/creq/CREQ-024.md | 15 +
.../CC2022/SAR/creq/CREQ-025.md | 15 +
.../CC2022/SAR/creq/CREQ-026.md | 15 +
.../CC2022/SAR/creq/CREQ-027.md | 15 +
.../CC2022/SAR/creq/CREQ-028.md | 15 +
.../CC2022/SAR/creq/CREQ-029.md | 15 +
.../CC2022/SAR/creq/CREQ-030.md | 15 +
.../CC2022/SAR/creq/CREQ-031.md | 15 +
.../CC2022/SAR/creq/CREQ-032.md | 15 +
.../CC2022/SAR/creq/CREQ-033.md | 15 +
.../CC2022/SAR/creq/CREQ-034.md | 15 +
.../CC2022/SAR/creq/CREQ-035.md | 15 +
.../CC2022/SAR/creq/CREQ-036.md | 15 +
.../CC2022/SAR/creq/CREQ-037.md | 15 +
.../CC2022/SAR/creq/CREQ-038.md | 15 +
.../CC2022/SAR/creq/CREQ-039.md | 15 +
.../CC2022/SAR/creq/CREQ-040.md | 15 +
.../CC2022/SAR/creq/CREQ-041.md | 15 +
.../CC2022/SAR/creq/CREQ-042.md | 15 +
.../CC2022/SAR/creq/CREQ-043.md | 15 +
.../CC2022/SAR/creq/CREQ-044.md | 15 +
.../CC2022/SAR/creq/CREQ-045.md | 15 +
.../CC2022/SAR/creq/CREQ-046.md | 15 +
.../CC2022/SAR/creq/CREQ-047.md | 15 +
.../CC2022/SAR/creq/CREQ-048.md | 15 +
.../CC2022/SAR/creq/CREQ-049.md | 15 +
.../CC2022/SAR/creq/CREQ-050.md | 15 +
.../CC2022/SAR/creq/CREQ-051.md | 15 +
.../CC2022/SAR/creq/CREQ-052.md | 15 +
.../CC2022/SAR/creq/CREQ-053.md | 15 +
.../CC2022/SAR/creq/CREQ-054.md | 15 +
.../CC2022/SAR/creq/CREQ-055.md | 15 +
.../CC2022/SAR/creq/CREQ-056.md | 15 +
.../CC2022/SAR/creq/CREQ-057.md | 15 +
.../CC2022/SAR/creq/CREQ-058.md | 15 +
.../CC2022/SAR/creq/CREQ-059.md | 15 +
.../CC2022/SAR/creq/CREQ-060.md | 15 +
.../CC2022/SAR/creq/CREQ-061.md | 15 +
.../CC2022/SAR/creq/CREQ-062.md | 15 +
.../CC2022/SAR/creq/CREQ-063.md | 15 +
.../CC2022/SAR/creq/CREQ-064.md | 15 +
.../CC2022/SAR/creq/CREQ-065.md | 15 +
.../CC2022/SAR/creq/CREQ-066.md | 15 +
.../CC2022/SAR/creq/CREQ-067.md | 15 +
.../CC2022/SAR/creq/CREQ-068.md | 15 +
.../CC2022/SAR/creq/CREQ-069.md | 15 +
.../CC2022/SAR/creq/CREQ-070.md | 15 +
.../CC2022/SAR/creq/CREQ-071.md | 15 +
.../CC2022/SAR/creq/CREQ-072.md | 15 +
.../CC2022/SAR/creq/CREQ-073.md | 15 +
.../CC2022/SAR/creq/CREQ-074.md | 15 +
.../CC2022/SAR/creq/CREQ-075.md | 15 +
.../CC2022/SAR/creq/CREQ-076.md | 15 +
.../CC2022/SAR/creq/CREQ-077.md | 15 +
.../CC2022/SAR/creq/CREQ-078.md | 15 +
.../CC2022/SAR/creq/CREQ-079.md | 15 +
.../CC2022/SAR/creq/CREQ-080.md | 15 +
.../CC2022/SAR/creq/CREQ-081.md | 15 +
.../CC2022/SAR/creq/CREQ-082.md | 15 +
.../CC2022/SAR/creq/CREQ-083.md | 15 +
.../CC2022/SAR/creq/CREQ-084.md | 15 +
.../CC2022/SAR/creq/CREQ-085.md | 15 +
.../CC2022/SAR/creq/CREQ-086.md | 15 +
.../CC2022/SAR/creq/CREQ-087.md | 15 +
.../CC2022/SAR/creq/CREQ-088.md | 15 +
.../CC2022/SAR/creq/CREQ-089.md | 15 +
.../CC2022/SAR/creq/CREQ-090.md | 15 +
.../CC2022/SAR/creq/CREQ-091.md | 15 +
.../CC2022/SAR/creq/CREQ-092.md | 15 +
.../CC2022/SAR/creq/CREQ-093.md | 15 +
.../CC2022/SAR/creq/CREQ-094.md | 15 +
.../CC2022/SAR/creq/CREQ-095.md | 15 +
.../CC2022/SAR/creq/CREQ-096.md | 15 +
.../CC2022/SAR/creq/CREQ-097.md | 15 +
.../CC2022/SAR/creq/CREQ-098.md | 15 +
.../CC2022/SAR/creq/CREQ-099.md | 15 +
.../CC2022/SAR/creq/CREQ-100.md | 15 +
.../CC2022/SAR/creq/CREQ-101.md | 15 +
.../CC2022/SAR/creq/CREQ-102.md | 15 +
.../CC2022/SAR/creq/CREQ-103.md | 15 +
.../CC2022/SAR/creq/CREQ-104.md | 15 +
.../CC2022/SAR/creq/CREQ-105.md | 15 +
.../CC2022/SAR/creq/CREQ-106.md | 15 +
.../CC2022/SAR/creq/CREQ-107.md | 15 +
.../CC2022/SAR/creq/CREQ-108.md | 15 +
.../CC2022/SAR/creq/CREQ-109.md | 15 +
.../CC2022/SAR/creq/CREQ-110.md | 15 +
.../CC2022/SAR/creq/CREQ-111.md | 15 +
.../CC2022/SAR/creq/CREQ-112.md | 15 +
.../CC2022/SAR/creq/CREQ-113.md | 15 +
.../CC2022/SAR/creq/CREQ-114.md | 15 +
.../CC2022/SAR/creq/CREQ-115.md | 15 +
.../CC2022/SAR/creq/CREQ-116.md | 15 +
.../CC2022/SAR/creq/CREQ-117.md | 15 +
.../CC2022/SAR/creq/CREQ-118.md | 15 +
.../CC2022/SAR/creq/CREQ-119.md | 15 +
.../CC2022/SAR/creq/CREQ-120.md | 15 +
.../CC2022/SAR/creq/CREQ-121.md | 15 +
.../CC2022/SAR/creq/CREQ-122.md | 15 +
.../CC2022/SAR/creq/CREQ-123.md | 15 +
.../CC2022/SAR/creq/CREQ-124.md | 15 +
.../CC2022/SAR/creq/CREQ-125.md | 15 +
.../CC2022/SAR/creq/CREQ-126.md | 15 +
.../CC2022/SAR/creq/CREQ-127.md | 15 +
.../CC2022/SAR/creq/CREQ-128.md | 15 +
.../CC2022/SAR/creq/CREQ-129.md | 15 +
.../CC2022/SAR/creq/CREQ-130.md | 15 +
.../CC2022/SAR/creq/CREQ-131.md | 15 +
.../CC2022/SAR/creq/CREQ-132.md | 15 +
.../CC2022/SAR/creq/CREQ-133.md | 15 +
.../CC2022/SAR/creq/CREQ-134.md | 15 +
.../CC2022/SAR/creq/CREQ-135.md | 15 +
.../CC2022/SAR/creq/CREQ-136.md | 15 +
.../CC2022/SAR/creq/CREQ-137.md | 15 +
.../CC2022/SAR/creq/CREQ-138.md | 15 +
.../CC2022/SAR/creq/CREQ-139.md | 15 +
.../CC2022/SAR/creq/CREQ-140.md | 15 +
.../CC2022/SAR/creq/CREQ-141.md | 15 +
.../CC2022/SAR/creq/CREQ-142.md | 15 +
.../CC2022/SAR/creq/CREQ-143.md | 15 +
.../CC2022/SAR/creq/CREQ-144.md | 15 +
.../CC2022/SAR/creq/CREQ-145.md | 15 +
.../CC2022/SAR/creq/CREQ-146.md | 15 +
.../CC2022/SAR/creq/CREQ-147.md | 15 +
.../CC2022/SAR/creq/CREQ-148.md | 15 +
.../CC2022/SAR/creq/CREQ-149.md | 15 +
.../CC2022/SAR/creq/CREQ-150.md | 15 +
.../CC2022/SAR/creq/CREQ-151.md | 15 +
.../CC2022/SAR/creq/CREQ-152.md | 15 +
.../CC2022/SAR/creq/CREQ-153.md | 15 +
.../CC2022/SAR/creq/CREQ-154.md | 15 +
.../CC2022/SAR/creq/CREQ-155.md | 15 +
.../CC2022/SAR/creq/CREQ-156.md | 15 +
.../CC2022/SAR/creq/CREQ-157.md | 15 +
.../CC2022/SAR/creq/CREQ-158.md | 15 +
.../CC2022/SAR/creq/CREQ-159.md | 15 +
.../CC2022/SAR/creq/CREQ-160.md | 15 +
.../CC2022/SAR/creq/CREQ-161.md | 15 +
.../CC2022/SAR/creq/CREQ-162.md | 15 +
.../CC2022/SAR/creq/CREQ-163.md | 15 +
.../CC2022/SAR/creq/CREQ-164.md | 15 +
.../CC2022/SAR/creq/CREQ-165.md | 15 +
.../CC2022/SAR/creq/CREQ-166.md | 15 +
.../CC2022/SAR/creq/CREQ-167.md | 15 +
.../CC2022/SAR/creq/CREQ-168.md | 15 +
.../CC2022/SAR/creq/CREQ-169.md | 15 +
.../CC2022/SAR/creq/CREQ-170.md | 15 +
.../CC2022/SAR/creq/CREQ-171.md | 15 +
.../CC2022/SAR/creq/CREQ-172.md | 15 +
.../CC2022/SAR/creq/CREQ-173.md | 15 +
.../CC2022/SAR/creq/CREQ-174.md | 15 +
.../CC2022/SAR/creq/CREQ-175.md | 15 +
.../CC2022/SAR/creq/CREQ-176.md | 15 +
.../CC2022/SAR/creq/CREQ-177.md | 15 +
.../CC2022/SAR/creq/CREQ-178.md | 15 +
.../CC2022/SAR/creq/CREQ-179.md | 15 +
.../CC2022/SAR/creq/CREQ-180.md | 15 +
.../CC2022/SAR/creq/CREQ-181.md | 15 +
.../CC2022/SAR/creq/CREQ-182.md | 15 +
.../CC2022/SAR/creq/CREQ-183.md | 15 +
.../CC2022/SAR/creq/CREQ-184.md | 15 +
.../CC2022/SAR/creq/CREQ-185.md | 15 +
.../CC2022/SAR/creq/CREQ-186.md | 15 +
.../CC2022/SAR/creq/CREQ-187.md | 15 +
.../CC2022/SAR/creq/CREQ-188.md | 15 +
.../CC2022/SAR/creq/CREQ-189.md | 15 +
.../CC2022/SAR/creq/CREQ-190.md | 15 +
.../CC2022/SAR/creq/CREQ-191.md | 15 +
.../CC2022/SAR/creq/CREQ-192.md | 15 +
.../CC2022/SAR/creq/CREQ-193.md | 15 +
.../CC2022/SAR/creq/CREQ-194.md | 15 +
.../CC2022/SAR/creq/CREQ-195.md | 15 +
.../CC2022/SAR/creq/CREQ-196.md | 15 +
.../CC2022/SAR/creq/CREQ-197.md | 15 +
.../CC2022/SAR/creq/CREQ-198.md | 15 +
.../CC2022/SAR/creq/CREQ-199.md | 15 +
.../CC2022/SAR/creq/CREQ-200.md | 15 +
.../CC2022/SAR/creq/CREQ-201.md | 15 +
.../CC2022/SAR/creq/CREQ-202.md | 15 +
.../CC2022/SAR/creq/CREQ-203.md | 15 +
.../CC2022/SAR/creq/CREQ-204.md | 15 +
.../CC2022/SAR/creq/CREQ-205.md | 15 +
.../CC2022/SAR/creq/CREQ-206.md | 15 +
.../CC2022/SAR/creq/CREQ-207.md | 15 +
.../CC2022/SAR/creq/CREQ-208.md | 15 +
.../CC2022/SAR/creq/CREQ-209.md | 15 +
.../CC2022/SAR/creq/CREQ-210.md | 15 +
.../CC2022/SAR/creq/CREQ-211.md | 15 +
.../CC2022/SAR/creq/CREQ-212.md | 15 +
.../CC2022/SAR/creq/CREQ-213.md | 15 +
.../CC2022/SAR/creq/CREQ-214.md | 15 +
.../CC2022/SAR/creq/CREQ-215.md | 15 +
.../CC2022/SAR/creq/CREQ-216.md | 15 +
.../CC2022/SAR/creq/CREQ-217.md | 15 +
.../CC2022/SAR/creq/CREQ-218.md | 15 +
.../CC2022/SAR/creq/CREQ-219.md | 15 +
.../CC2022/SAR/creq/CREQ-220.md | 15 +
.../CC2022/SAR/creq/CREQ-221.md | 15 +
.../CC2022/SAR/creq/CREQ-222.md | 15 +
.../CC2022/SAR/creq/CREQ-223.md | 15 +
.../CC2022/SAR/creq/CREQ-224.md | 15 +
.../CC2022/SAR/creq/CREQ-225.md | 15 +
.../CC2022/SAR/creq/CREQ-226.md | 15 +
.../CC2022/SAR/creq/CREQ-227.md | 15 +
.../CC2022/SAR/creq/CREQ-228.md | 15 +
.../CC2022/SAR/creq/CREQ-229.md | 15 +
.../CC2022/SAR/creq/CREQ-230.md | 15 +
.../CC2022/SAR/creq/CREQ-231.md | 15 +
.../CC2022/SAR/creq/CREQ-232.md | 15 +
.../CC2022/SAR/creq/CREQ-233.md | 15 +
.../CC2022/SAR/creq/CREQ-234.md | 15 +
.../CC2022/SAR/creq/CREQ-235.md | 15 +
.../CC2022/SAR/creq/CREQ-236.md | 15 +
.../CC2022/SAR/creq/CREQ-237.md | 15 +
.../CC2022/SAR/creq/CREQ-238.md | 15 +
.../CC2022/SAR/creq/CREQ-239.md | 15 +
.../CC2022/SAR/creq/CREQ-240.md | 15 +
.../CC2022/SAR/creq/CREQ-241.md | 15 +
.../CC2022/SAR/creq/CREQ-242.md | 15 +
.../CC2022/SAR/creq/CREQ-243.md | 15 +
.../CC2022/SAR/creq/CREQ-244.md | 15 +
.../CC2022/SAR/creq/CREQ-245.md | 15 +
.../CC2022/SAR/creq/CREQ-246.md | 15 +
.../CC2022/SAR/creq/CREQ-247.md | 15 +
.../CC2022/SAR/creq/CREQ-248.md | 15 +
.../CC2022/SAR/creq/CREQ-249.md | 15 +
.../CC2022/SAR/creq/CREQ-250.md | 15 +
.../CC2022/SAR/creq/CREQ-251.md | 15 +
.../CC2022/SAR/creq/CREQ-252.md | 15 +
.../CC2022/SAR/creq/CREQ-253.md | 15 +
.../CC2022/SAR/creq/CREQ-254.md | 15 +
.../CC2022/SAR/creq/CREQ-255.md | 15 +
.../CC2022/SAR/creq/CREQ-256.md | 15 +
.../CC2022/SAR/creq/CREQ-257.md | 15 +
.../CC2022/SAR/creq/CREQ-258.md | 15 +
.../CC2022/SAR/creq/CREQ-259.md | 15 +
.../CC2022/SAR/creq/CREQ-260.md | 15 +
.../CC2022/SAR/creq/CREQ-261.md | 15 +
.../CC2022/SAR/creq/CREQ-262.md | 15 +
.../CC2022/SAR/creq/CREQ-263.md | 15 +
.../CC2022/SAR/creq/CREQ-264.md | 15 +
.../CC2022/SAR/creq/CREQ-265.md | 15 +
.../CC2022/SAR/creq/CREQ-266.md | 15 +
.../CC2022/SAR/creq/CREQ-267.md | 15 +
.../CC2022/SAR/creq/CREQ-268.md | 15 +
.../CC2022/SAR/creq/CREQ-269.md | 15 +
.../CC2022/SAR/creq/CREQ-270.md | 15 +
.../CC2022/SAR/creq/CREQ-271.md | 15 +
.../CC2022/SAR/creq/CREQ-272.md | 15 +
.../CC2022/SAR/creq/CREQ-273.md | 15 +
.../CC2022/SAR/creq/CREQ-274.md | 15 +
.../CC2022/SAR/creq/CREQ-275.md | 15 +
.../CC2022/SAR/creq/CREQ-276.md | 15 +
.../CC2022/SAR/creq/CREQ-277.md | 15 +
.../CC2022/SAR/creq/CREQ-278.md | 15 +
.../CC2022/SAR/creq/CREQ-279.md | 15 +
.../CC2022/SAR/creq/CREQ-280.md | 15 +
.../CC2022/SAR/creq/CREQ-281.md | 15 +
.../CC2022/SAR/creq/CREQ-282.md | 15 +
.../CC2022/SAR/creq/CREQ-283.md | 15 +
.../CC2022/SAR/creq/CREQ-284.md | 15 +
.../CC2022/SAR/creq/CREQ-285.md | 15 +
.../CC2022/SAR/creq/CREQ-286.md | 15 +
.../CC2022/SAR/creq/CREQ-287.md | 15 +
.../CC2022/SAR/creq/CREQ-288.md | 15 +
.../CC2022/SAR/creq/CREQ-289.md | 15 +
.../CC2022/SAR/creq/CREQ-290.md | 15 +
.../CC2022/SAR/creq/CREQ-291.md | 15 +
.../CC2022/SAR/creq/CREQ-292.md | 15 +
.../CC2022/SAR/creq/CREQ-293.md | 15 +
.../CC2022/SAR/creq/CREQ-294.md | 15 +
.../CC2022/SAR/creq/CREQ-295.md | 15 +
.../CC2022/SAR/creq/CREQ-296.md | 15 +
.../CC2022/SAR/creq/CREQ-297.md | 15 +
.../CC2022/SAR/creq/CREQ-298.md | 15 +
.../CC2022/SAR/creq/CREQ-299.md | 15 +
.../CC2022/SAR/creq/CREQ-300.md | 15 +
.../CC2022/SAR/creq/CREQ-301.md | 15 +
.../CC2022/SAR/creq/CREQ-302.md | 15 +
.../CC2022/SAR/creq/CREQ-303.md | 15 +
.../CC2022/SAR/creq/CREQ-304.md | 15 +
.../CC2022/SAR/creq/CREQ-305.md | 15 +
.../CC2022/SAR/creq/CREQ-306.md | 15 +
.../CC2022/SAR/creq/CREQ-307.md | 15 +
.../CC2022/SAR/creq/CREQ-308.md | 15 +
.../CC2022/SAR/creq/CREQ-309.md | 15 +
.../CC2022/SAR/creq/CREQ-310.md | 15 +
.../CC2022/SAR/creq/CREQ-311.md | 15 +
.../CC2022/SAR/creq/CREQ-312.md | 15 +
.../CC2022/SAR/creq/CREQ-313.md | 15 +
.../CC2022/SAR/creq/CREQ-314.md | 15 +
.../CC2022/SAR/creq/CREQ-315.md | 15 +
.../CC2022/SAR/creq/CREQ-316.md | 15 +
.../CC2022/SAR/creq/CREQ-317.md | 15 +
.../CC2022/SAR/creq/CREQ-318.md | 15 +
.../CC2022/SAR/creq/CREQ-319.md | 15 +
.../CC2022/SAR/creq/CREQ-320.md | 15 +
.../CC2022/SAR/creq/CREQ-321.md | 15 +
.../CC2022/SAR/creq/CREQ-322.md | 15 +
.../CC2022/SAR/creq/CREQ-323.md | 15 +
.../CC2022/SAR/creq/CREQ-324.md | 15 +
.../CC2022/SAR/creq/CREQ-325.md | 15 +
.../CC2022/SAR/creq/CREQ-326.md | 15 +
.../CC2022/SAR/creq/CREQ-327.md | 15 +
.../CC2022/SAR/creq/CREQ-328.md | 15 +
.../CC2022/SAR/creq/CREQ-329.md | 15 +
.../CC2022/SAR/creq/CREQ-330.md | 15 +
.../CC2022/SAR/creq/CREQ-331.md | 15 +
.../CC2022/SAR/creq/CREQ-332.md | 15 +
.../CC2022/SAR/creq/CREQ-333.md | 15 +
.../CC2022/SAR/creq/CREQ-334.md | 15 +
.../CC2022/SAR/creq/CREQ-335.md | 15 +
.../CC2022/SAR/creq/CREQ-336.md | 15 +
.../CC2022/SAR/creq/CREQ-337.md | 15 +
.../CC2022/SAR/creq/CREQ-338.md | 15 +
.../CC2022/SAR/creq/CREQ-339.md | 15 +
.../CC2022/SAR/creq/CREQ-340.md | 15 +
.../CC2022/SAR/creq/CREQ-341.md | 15 +
.../CC2022/SAR/creq/CREQ-342.md | 15 +
.../CC2022/SAR/creq/CREQ-343.md | 15 +
.../CC2022/SAR/creq/CREQ-344.md | 15 +
.../CC2022/SAR/creq/CREQ-345.md | 15 +
.../CC2022/SAR/creq/CREQ-346.md | 15 +
.../CC2022/SAR/creq/CREQ-347.md | 15 +
.../CC2022/SAR/creq/CREQ-348.md | 15 +
.../CC2022/SAR/creq/CREQ-349.md | 15 +
.../CC2022/SAR/creq/CREQ-350.md | 15 +
.../CC2022/SAR/creq/CREQ-351.md | 15 +
.../CC2022/SAR/creq/CREQ-352.md | 15 +
.../CC2022/SAR/creq/CREQ-353.md | 15 +
.../CC2022/SAR/creq/CREQ-354.md | 15 +
.../CC2022/SAR/creq/CREQ-355.md | 15 +
.../CC2022/SAR/creq/CREQ-356.md | 15 +
.../CC2022/SAR/creq/CREQ-357.md | 15 +
.../CC2022/SAR/creq/CREQ-358.md | 15 +
.../CC2022/SAR/creq/CREQ-359.md | 15 +
.../CC2022/SAR/creq/CREQ-360.md | 15 +
.../CC2022/SAR/creq/CREQ-361.md | 15 +
.../CC2022/SAR/creq/CREQ-362.md | 15 +
.../CC2022/SAR/creq/CREQ-363.md | 15 +
.../CC2022/SAR/creq/CREQ-364.md | 15 +
.../CC2022/SAR/creq/CREQ-365.md | 15 +
.../CC2022/SAR/creq/CREQ-366.md | 15 +
.../CC2022/SAR/creq/CREQ-367.md | 15 +
.../CC2022/SAR/creq/CREQ-368.md | 15 +
.../CC2022/SAR/creq/CREQ-369.md | 15 +
.../CC2022/SAR/creq/CREQ-370.md | 15 +
.../CC2022/SAR/creq/CREQ-371.md | 15 +
.../CC2022/SAR/creq/CREQ-372.md | 15 +
.../CC2022/SAR/creq/CREQ-373.md | 15 +
.../CC2022/SAR/creq/CREQ-374.md | 15 +
.../CC2022/SAR/creq/CREQ-375.md | 15 +
.../CC2022/SAR/creq/CREQ-376.md | 15 +
.../CC2022/SAR/creq/CREQ-377.md | 15 +
.../CC2022/SAR/creq/CREQ-378.md | 15 +
.../CC2022/SAR/creq/CREQ-379.md | 15 +
.../CC2022/SAR/creq/CREQ-380.md | 15 +
.../CC2022/SAR/creq/CREQ-381.md | 15 +
.../CC2022/SAR/creq/CREQ-382.md | 15 +
.../CC2022/SAR/creq/CREQ-383.md | 15 +
.../CC2022/SAR/creq/CREQ-384.md | 15 +
.../CC2022/SAR/creq/CREQ-385.md | 15 +
.../CC2022/SAR/creq/CREQ-386.md | 15 +
.../CC2022/SAR/creq/CREQ-387.md | 15 +
.../CC2022/SAR/creq/CREQ-388.md | 15 +
.../CC2022/SAR/creq/CREQ-389.md | 15 +
.../CC2022/SAR/creq/CREQ-390.md | 15 +
.../CC2022/SAR/creq/CREQ-391.md | 15 +
.../CC2022/SAR/creq/CREQ-392.md | 15 +
.../CC2022/SAR/creq/CREQ-393.md | 15 +
.../CC2022/SAR/creq/CREQ-394.md | 15 +
.../CC2022/SAR/creq/CREQ-395.md | 15 +
.../CC2022/SAR/creq/CREQ-396.md | 15 +
.../CC2022/SAR/creq/CREQ-397.md | 15 +
.../CC2022/SAR/creq/CREQ-398.md | 15 +
.../CC2022/SAR/creq/CREQ-399.md | 15 +
.../CC2022/SAR/creq/CREQ-400.md | 15 +
.../CC2022/SAR/creq/CREQ-401.md | 15 +
.../CC2022/SAR/creq/CREQ-402.md | 15 +
.../CC2022/SAR/creq/CREQ-403.md | 15 +
.../CC2022/SAR/creq/CREQ-404.md | 15 +
.../CC2022/SAR/creq/CREQ-405.md | 15 +
.../CC2022/SAR/creq/CREQ-406.md | 15 +
.../CC2022/SAR/creq/CREQ-407.md | 15 +
.../CC2022/SAR/creq/CREQ-408.md | 15 +
.../CC2022/SAR/creq/CREQ-409.md | 15 +
.../CC2022/SAR/creq/CREQ-410.md | 15 +
.../CC2022/SAR/creq/CREQ-411.md | 15 +
.../CC2022/SAR/creq/CREQ-412.md | 15 +
.../CC2022/SAR/creq/CREQ-413.md | 15 +
.../CC2022/SAR/creq/CREQ-414.md | 15 +
.../CC2022/SAR/creq/CREQ-415.md | 15 +
.../CC2022/SAR/creq/CREQ-416.md | 15 +
.../CC2022/SAR/creq/CREQ-417.md | 15 +
.../CC2022/SAR/creq/CREQ-418.md | 15 +
.../CC2022/SAR/creq/CREQ-419.md | 15 +
.../CC2022/SAR/creq/CREQ-420.md | 15 +
.../CC2022/SAR/creq/CREQ-421.md | 15 +
.../CC2022/SAR/creq/CREQ-422.md | 15 +
.../CC2022/SAR/creq/CREQ-423.md | 15 +
.../CC2022/SAR/creq/CREQ-424.md | 15 +
.../CC2022/SAR/creq/CREQ-425.md | 15 +
.../CC2022/SAR/creq/CREQ-426.md | 15 +
.../CC2022/SAR/creq/CREQ-427.md | 15 +
.../CC2022/SAR/creq/CREQ-428.md | 15 +
.../CC2022/SAR/creq/CREQ-429.md | 15 +
.../CC2022/SAR/creq/CREQ-430.md | 15 +
.../CC2022/SAR/creq/CREQ-431.md | 15 +
.../CC2022/SAR/creq/CREQ-432.md | 15 +
.../CC2022/SAR/creq/CREQ-433.md | 15 +
.../CC2022/SAR/creq/CREQ-434.md | 15 +
.../CC2022/SAR/creq/CREQ-435.md | 15 +
.../CC2022/SAR/creq/CREQ-436.md | 15 +
.../CC2022/SAR/creq/CREQ-437.md | 15 +
.../CC2022/SAR/creq/CREQ-438.md | 15 +
.../CC2022/SAR/creq/CREQ-439.md | 15 +
.../CC2022/SAR/creq/CREQ-440.md | 15 +
.../CC2022/SAR/creq/CREQ-441.md | 15 +
.../CC2022/SAR/creq/CREQ-442.md | 15 +
.../CC2022/SAR/creq/CREQ-443.md | 15 +
.../CC2022/SAR/creq/CREQ-444.md | 15 +
.../CC2022/SAR/creq/CREQ-445.md | 15 +
.../CC2022/SAR/creq/CREQ-446.md | 15 +
.../CC2022/SAR/creq/CREQ-447.md | 15 +
.../CC2022/SAR/creq/CREQ-448.md | 15 +
.../CC2022/SAR/creq/CREQ-449.md | 15 +
.../CC2022/SAR/creq/CREQ-450.md | 15 +
.../CC2022/SAR/creq/CREQ-451.md | 15 +
.../CC2022/SAR/creq/CREQ-452.md | 15 +
.../CC2022/SAR/creq/CREQ-453.md | 15 +
.../CC2022/SAR/creq/CREQ-454.md | 15 +
.../CC2022/SAR/creq/CREQ-455.md | 15 +
.../CC2022/SAR/creq/CREQ-456.md | 15 +
.../CC2022/SAR/creq/CREQ-457.md | 15 +
.../CC2022/SAR/creq/CREQ-458.md | 15 +
.../CC2022/SAR/creq/CREQ-459.md | 15 +
.../CC2022/SAR/creq/CREQ-460.md | 15 +
.../CC2022/SAR/creq/CREQ-461.md | 15 +
.../CC2022/SAR/creq/CREQ-462.md | 15 +
.../CC2022/SAR/creq/CREQ-463.md | 15 +
.../CC2022/SAR/creq/CREQ-464.md | 15 +
.../CC2022/SAR/creq/CREQ-465.md | 15 +
.../CC2022/SAR/creq/CREQ-466.md | 15 +
.../CC2022/SAR/creq/CREQ-467.md | 15 +
.../CC2022/SAR/creq/CREQ-468.md | 15 +
.../CC2022/SAR/creq/CREQ-469.md | 15 +
.../CC2022/SAR/creq/CREQ-470.md | 15 +
.../CC2022/SAR/creq/CREQ-471.md | 15 +
.../CC2022/SAR/creq/CREQ-472.md | 15 +
.../CC2022/SAR/creq/CREQ-473.md | 15 +
.../CC2022/SAR/creq/CREQ-474.md | 15 +
.../CC2022/SAR/creq/CREQ-475.md | 15 +
.../CC2022/SAR/creq/CREQ-476.md | 15 +
.../CC2022/SAR/creq/CREQ-477.md | 15 +
.../CC2022/SAR/creq/CREQ-478.md | 15 +
.../CC2022/SAR/creq/CREQ-479.md | 15 +
.../CC2022/SAR/creq/CREQ-480.md | 15 +
.../CC2022/SAR/creq/CREQ-481.md | 15 +
.../CC2022/SAR/creq/CREQ-482.md | 15 +
.../CC2022/SAR/creq/CREQ-483.md | 15 +
.../CC2022/SAR/creq/CREQ-484.md | 15 +
.../CC2022/SAR/creq/CREQ-485.md | 15 +
.../CC2022/SAR/creq/CREQ-486.md | 15 +
.../CC2022/SAR/creq/CREQ-487.md | 15 +
.../CC2022/SAR/creq/CREQ-488.md | 15 +
.../CC2022/SAR/creq/CREQ-489.md | 15 +
.../CC2022/SAR/creq/CREQ-490.md | 15 +
.../CC2022/SAR/creq/CREQ-491.md | 15 +
.../CC2022/SAR/creq/CREQ-492.md | 15 +
.../CC2022/SAR/creq/CREQ-493.md | 15 +
.../CC2022/SAR/creq/CREQ-494.md | 15 +
.../CC2022/SAR/creq/CREQ-495.md | 15 +
.../CC2022/SAR/creq/CREQ-496.md | 15 +
.../CC2022/SAR/creq/CREQ-497.md | 15 +
.../CC2022/SAR/creq/CREQ-498.md | 15 +
.../CC2022/SAR/creq/CREQ-499.md | 15 +
.../CC2022/SAR/creq/CREQ-500.md | 15 +
.../CC2022/SAR/creq/CREQ-501.md | 15 +
.../CC2022/SAR/creq/CREQ-502.md | 15 +
.../CC2022/SAR/creq/CREQ-503.md | 15 +
.../CC2022/SAR/creq/CREQ-504.md | 15 +
.../CC2022/SAR/creq/CREQ-505.md | 15 +
.../CC2022/SAR/creq/CREQ-506.md | 15 +
.../CC2022/SAR/creq/CREQ-507.md | 15 +
.../CC2022/SAR/creq/CREQ-508.md | 15 +
.../CC2022/SAR/creq/CREQ-509.md | 15 +
.../CC2022/SAR/creq/CREQ-510.md | 15 +
.../CC2022/SAR/creq/CREQ-511.md | 15 +
.../CC2022/SAR/creq/CREQ-512.md | 15 +
.../CC2022/SAR/creq/CREQ-513.md | 15 +
.../CC2022/SAR/creq/CREQ-514.md | 15 +
.../CC2022/SAR/creq/CREQ-515.md | 15 +
.../CC2022/SAR/creq/CREQ-516.md | 15 +
.../CC2022/SAR/creq/CREQ-517.md | 15 +
.../CC2022/SAR/creq/CREQ-518.md | 15 +
.../CC2022/SAR/creq/CREQ-519.md | 15 +
.../CC2022/SAR/creq/CREQ-520.md | 15 +
.../CC2022/SAR/creq/CREQ-521.md | 15 +
.../CC2022/SAR/creq/CREQ-522.md | 15 +
.../CC2022/SAR/creq/CREQ-523.md | 15 +
.../CC2022/SAR/dreq/.doorstop.yml | 11 +
.../CC2022/SAR/dreq/DREQ-001.md | 15 +
.../CC2022/SAR/dreq/DREQ-002.md | 15 +
.../CC2022/SAR/dreq/DREQ-003.md | 15 +
.../CC2022/SAR/dreq/DREQ-004.md | 15 +
.../CC2022/SAR/dreq/DREQ-005.md | 15 +
.../CC2022/SAR/dreq/DREQ-006.md | 15 +
.../CC2022/SAR/dreq/DREQ-007.md | 15 +
.../CC2022/SAR/dreq/DREQ-008.md | 15 +
.../CC2022/SAR/dreq/DREQ-009.md | 15 +
.../CC2022/SAR/dreq/DREQ-010.md | 15 +
.../CC2022/SAR/dreq/DREQ-011.md | 15 +
.../CC2022/SAR/dreq/DREQ-012.md | 15 +
.../CC2022/SAR/dreq/DREQ-013.md | 15 +
.../CC2022/SAR/dreq/DREQ-014.md | 15 +
.../CC2022/SAR/dreq/DREQ-015.md | 15 +
.../CC2022/SAR/dreq/DREQ-016.md | 15 +
.../CC2022/SAR/dreq/DREQ-017.md | 15 +
.../CC2022/SAR/dreq/DREQ-018.md | 15 +
.../CC2022/SAR/dreq/DREQ-019.md | 15 +
.../CC2022/SAR/dreq/DREQ-020.md | 15 +
.../CC2022/SAR/dreq/DREQ-021.md | 15 +
.../CC2022/SAR/dreq/DREQ-022.md | 15 +
.../CC2022/SAR/dreq/DREQ-023.md | 15 +
.../CC2022/SAR/dreq/DREQ-024.md | 15 +
.../CC2022/SAR/dreq/DREQ-025.md | 15 +
.../CC2022/SAR/dreq/DREQ-026.md | 15 +
.../CC2022/SAR/dreq/DREQ-027.md | 15 +
.../CC2022/SAR/dreq/DREQ-028.md | 15 +
.../CC2022/SAR/dreq/DREQ-029.md | 15 +
.../CC2022/SAR/dreq/DREQ-030.md | 15 +
.../CC2022/SAR/dreq/DREQ-031.md | 15 +
.../CC2022/SAR/dreq/DREQ-032.md | 15 +
.../CC2022/SAR/dreq/DREQ-033.md | 15 +
.../CC2022/SAR/dreq/DREQ-034.md | 15 +
.../CC2022/SAR/dreq/DREQ-035.md | 15 +
.../CC2022/SAR/dreq/DREQ-036.md | 15 +
.../CC2022/SAR/dreq/DREQ-037.md | 15 +
.../CC2022/SAR/dreq/DREQ-038.md | 15 +
.../CC2022/SAR/dreq/DREQ-039.md | 15 +
.../CC2022/SAR/dreq/DREQ-040.md | 15 +
.../CC2022/SAR/dreq/DREQ-041.md | 15 +
.../CC2022/SAR/dreq/DREQ-042.md | 15 +
.../CC2022/SAR/dreq/DREQ-043.md | 15 +
.../CC2022/SAR/dreq/DREQ-044.md | 15 +
.../CC2022/SAR/dreq/DREQ-045.md | 15 +
.../CC2022/SAR/dreq/DREQ-046.md | 15 +
.../CC2022/SAR/dreq/DREQ-047.md | 15 +
.../CC2022/SAR/dreq/DREQ-048.md | 15 +
.../CC2022/SAR/dreq/DREQ-049.md | 15 +
.../CC2022/SAR/dreq/DREQ-050.md | 15 +
.../CC2022/SAR/dreq/DREQ-051.md | 15 +
.../CC2022/SAR/dreq/DREQ-052.md | 15 +
.../CC2022/SAR/dreq/DREQ-053.md | 15 +
.../CC2022/SAR/dreq/DREQ-054.md | 15 +
.../CC2022/SAR/dreq/DREQ-055.md | 15 +
.../CC2022/SAR/dreq/DREQ-056.md | 15 +
.../CC2022/SAR/dreq/DREQ-057.md | 15 +
.../CC2022/SAR/dreq/DREQ-058.md | 15 +
.../CC2022/SAR/dreq/DREQ-059.md | 15 +
.../CC2022/SAR/dreq/DREQ-060.md | 15 +
.../CC2022/SAR/dreq/DREQ-061.md | 15 +
.../CC2022/SAR/dreq/DREQ-062.md | 15 +
.../CC2022/SAR/dreq/DREQ-063.md | 15 +
.../CC2022/SAR/dreq/DREQ-064.md | 15 +
.../CC2022/SAR/dreq/DREQ-065.md | 15 +
.../CC2022/SAR/dreq/DREQ-066.md | 15 +
.../CC2022/SAR/dreq/DREQ-067.md | 15 +
.../CC2022/SAR/dreq/DREQ-068.md | 15 +
.../CC2022/SAR/dreq/DREQ-069.md | 15 +
.../CC2022/SAR/dreq/DREQ-070.md | 15 +
.../CC2022/SAR/dreq/DREQ-071.md | 15 +
.../CC2022/SAR/dreq/DREQ-072.md | 15 +
.../CC2022/SAR/dreq/DREQ-073.md | 15 +
.../CC2022/SAR/dreq/DREQ-074.md | 15 +
.../CC2022/SAR/dreq/DREQ-075.md | 15 +
.../CC2022/SAR/dreq/DREQ-076.md | 15 +
.../CC2022/SAR/dreq/DREQ-077.md | 15 +
.../CC2022/SAR/dreq/DREQ-078.md | 15 +
.../CC2022/SAR/dreq/DREQ-079.md | 15 +
.../CC2022/SAR/dreq/DREQ-080.md | 15 +
.../CC2022/SAR/dreq/DREQ-081.md | 15 +
.../CC2022/SAR/dreq/DREQ-082.md | 15 +
.../CC2022/SAR/dreq/DREQ-083.md | 15 +
.../CC2022/SAR/dreq/DREQ-084.md | 15 +
.../CC2022/SAR/dreq/DREQ-085.md | 15 +
.../CC2022/SAR/dreq/DREQ-086.md | 15 +
.../CC2022/SAR/dreq/DREQ-087.md | 15 +
.../CC2022/SAR/dreq/DREQ-088.md | 15 +
.../CC2022/SAR/dreq/DREQ-089.md | 15 +
.../CC2022/SAR/dreq/DREQ-090.md | 15 +
.../CC2022/SAR/dreq/DREQ-091.md | 15 +
.../CC2022/SAR/dreq/DREQ-092.md | 15 +
.../CC2022/SAR/dreq/DREQ-093.md | 15 +
.../CC2022/SAR/dreq/DREQ-094.md | 15 +
.../CC2022/SAR/dreq/DREQ-095.md | 15 +
.../CC2022/SAR/dreq/DREQ-096.md | 15 +
.../CC2022/SAR/dreq/DREQ-097.md | 15 +
.../CC2022/SAR/dreq/DREQ-098.md | 15 +
.../CC2022/SAR/dreq/DREQ-099.md | 15 +
.../CC2022/SAR/dreq/DREQ-100.md | 15 +
.../CC2022/SAR/dreq/DREQ-101.md | 15 +
.../CC2022/SAR/dreq/DREQ-102.md | 15 +
.../CC2022/SAR/dreq/DREQ-103.md | 15 +
.../CC2022/SAR/dreq/DREQ-104.md | 15 +
.../CC2022/SAR/dreq/DREQ-105.md | 15 +
.../CC2022/SAR/dreq/DREQ-106.md | 15 +
.../CC2022/SAR/dreq/DREQ-107.md | 15 +
.../CC2022/SAR/dreq/DREQ-108.md | 15 +
.../CC2022/SAR/dreq/DREQ-109.md | 15 +
.../CC2022/SAR/dreq/DREQ-110.md | 15 +
.../CC2022/SAR/dreq/DREQ-111.md | 15 +
.../CC2022/SAR/dreq/DREQ-112.md | 15 +
.../CC2022/SAR/dreq/DREQ-113.md | 15 +
.../CC2022/SAR/dreq/DREQ-114.md | 15 +
.../CC2022/SAR/dreq/DREQ-115.md | 15 +
.../CC2022/SAR/dreq/DREQ-116.md | 15 +
.../CC2022/SAR/dreq/DREQ-117.md | 15 +
.../CC2022/SAR/dreq/DREQ-118.md | 15 +
.../CC2022/SAR/dreq/DREQ-119.md | 15 +
.../CC2022/SAR/dreq/DREQ-120.md | 15 +
.../CC2022/SAR/dreq/DREQ-121.md | 15 +
.../CC2022/SAR/dreq/DREQ-122.md | 15 +
.../CC2022/SAR/dreq/DREQ-123.md | 15 +
.../CC2022/SAR/dreq/DREQ-124.md | 15 +
.../CC2022/SAR/dreq/DREQ-125.md | 15 +
.../CC2022/SAR/dreq/DREQ-126.md | 15 +
.../CC2022/SAR/dreq/DREQ-127.md | 15 +
.../CC2022/SAR/dreq/DREQ-128.md | 15 +
.../CC2022/SAR/dreq/DREQ-129.md | 15 +
.../CC2022/SAR/dreq/DREQ-130.md | 15 +
.../CC2022/SAR/dreq/DREQ-131.md | 15 +
.../CC2022/SAR/dreq/DREQ-132.md | 15 +
.../CC2022/SAR/dreq/DREQ-133.md | 15 +
.../CC2022/SAR/dreq/DREQ-134.md | 15 +
.../CC2022/SAR/dreq/DREQ-135.md | 15 +
.../CC2022/SAR/dreq/DREQ-136.md | 15 +
.../CC2022/SAR/dreq/DREQ-137.md | 15 +
.../CC2022/SAR/dreq/DREQ-138.md | 15 +
.../CC2022/SAR/dreq/DREQ-139.md | 15 +
.../CC2022/SAR/dreq/DREQ-140.md | 15 +
.../CC2022/SAR/dreq/DREQ-141.md | 15 +
.../CC2022/SAR/dreq/DREQ-142.md | 15 +
.../CC2022/SAR/dreq/DREQ-143.md | 15 +
.../CC2022/SAR/dreq/DREQ-144.md | 15 +
.../CC2022/SAR/dreq/DREQ-145.md | 15 +
.../CC2022/SAR/dreq/DREQ-146.md | 15 +
.../CC2022/SAR/dreq/DREQ-147.md | 15 +
.../CC2022/SAR/dreq/DREQ-148.md | 15 +
.../CC2022/SAR/dreq/DREQ-149.md | 15 +
.../CC2022/SAR/dreq/DREQ-150.md | 15 +
.../CC2022/SAR/dreq/DREQ-151.md | 15 +
.../CC2022/SAR/dreq/DREQ-152.md | 15 +
.../CC2022/SAR/dreq/DREQ-153.md | 15 +
.../CC2022/SAR/dreq/DREQ-154.md | 15 +
.../CC2022/SAR/dreq/DREQ-155.md | 15 +
.../CC2022/SAR/dreq/DREQ-156.md | 15 +
.../CC2022/SAR/dreq/DREQ-157.md | 15 +
.../CC2022/SAR/dreq/DREQ-158.md | 15 +
.../CC2022/SAR/dreq/DREQ-159.md | 15 +
.../CC2022/SAR/dreq/DREQ-160.md | 15 +
.../CC2022/SAR/dreq/DREQ-161.md | 14 +
.../CC2022/SAR/dreq/DREQ-162.md | 15 +
.../CC2022/SAR/dreq/DREQ-163.md | 15 +
.../CC2022/SAR/dreq/DREQ-164.md | 15 +
.../CC2022/SAR/dreq/DREQ-165.md | 15 +
.../CC2022/SAR/dreq/DREQ-166.md | 15 +
.../CC2022/SAR/dreq/DREQ-167.md | 15 +
.../CC2022/SAR/dreq/DREQ-168.md | 15 +
.../CC2022/SAR/dreq/DREQ-169.md | 15 +
.../CC2022/SAR/dreq/DREQ-170.md | 15 +
.../CC2022/SAR/dreq/DREQ-171.md | 15 +
.../CC2022/SAR/dreq/DREQ-172.md | 15 +
.../CC2022/SAR/dreq/DREQ-173.md | 15 +
.../CC2022/SAR/dreq/DREQ-174.md | 15 +
.../CC2022/SAR/dreq/DREQ-175.md | 15 +
.../CC2022/SAR/dreq/DREQ-176.md | 15 +
.../CC2022/SAR/dreq/DREQ-177.md | 15 +
.../CC2022/SAR/dreq/DREQ-178.md | 15 +
.../CC2022/SAR/dreq/DREQ-179.md | 15 +
.../CC2022/SAR/dreq/DREQ-180.md | 15 +
.../CC2022/SAR/dreq/DREQ-181.md | 15 +
.../CC2022/SAR/dreq/DREQ-182.md | 15 +
.../CC2022/SAR/dreq/DREQ-183.md | 15 +
.../CC2022/SAR/dreq/DREQ-184.md | 15 +
.../CC2022/SAR/dreq/DREQ-186.md | 15 +
.../CC2022/SAR/dreq/DREQ-187.md | 15 +
.../CC2022/SAR/dreq/DREQ-188.md | 15 +
.../CC2022/SAR/dreq/DREQ-189.md | 15 +
.../CC2022/SAR/dreq/DREQ-190.md | 15 +
.../CC2022/SAR/dreq/DREQ-191.md | 15 +
.../CC2022/SAR/dreq/DREQ-192.md | 15 +
.../CC2022/SAR/dreq/DREQ-193.md | 15 +
.../CC2022/SAR/dreq/DREQ-194.md | 15 +
.../CC2022/SAR/dreq/DREQ-195.md | 15 +
.../CC2022/SAR/dreq/DREQ-196.md | 15 +
.../CC2022/SAR/dreq/DREQ-197.md | 15 +
.../CC2022/SAR/dreq/DREQ-198.md | 15 +
.../CC2022/SAR/dreq/DREQ-199.md | 15 +
.../CC2022/SAR/dreq/DREQ-200.md | 15 +
.../CC2022/SAR/dreq/DREQ-201.md | 15 +
.../CC2022/SAR/dreq/DREQ-202.md | 15 +
.../CC2022/SAR/dreq/DREQ-203.md | 15 +
.../CC2022/SAR/dreq/DREQ-204.md | 15 +
.../CC2022/SAR/dreq/DREQ-205.md | 15 +
.../CC2022/SAR/dreq/DREQ-206.md | 15 +
.../CC2022/SAR/dreq/DREQ-207.md | 15 +
.../CC2022/SAR/dreq/DREQ-208.md | 15 +
.../CC2022/SAR/dreq/DREQ-209.md | 15 +
.../CC2022/SAR/dreq/DREQ-210.md | 15 +
.../CC2022/SAR/dreq/DREQ-211.md | 15 +
.../CC2022/SAR/dreq/DREQ-212.md | 15 +
.../CC2022/SAR/dreq/DREQ-213.md | 15 +
.../CC2022/SAR/dreq/DREQ-214.md | 15 +
.../CC2022/SAR/dreq/DREQ-215.md | 15 +
.../CC2022/SAR/ereq/.doorstop.yml | 11 +
.../CC2022/SAR/ereq/EREQ-001.md | 15 +
.../CC2022/SAR/ereq/EREQ-002.md | 15 +
.../CC2022/SAR/ereq/EREQ-003.md | 15 +
.../CC2022/SAR/ereq/EREQ-004.md | 15 +
.../CC2022/SAR/ereq/EREQ-005.md | 15 +
.../CC2022/SAR/ereq/EREQ-006.md | 15 +
.../CC2022/SAR/ereq/EREQ-007.md | 15 +
.../CC2022/SAR/ereq/EREQ-008.md | 15 +
.../CC2022/SAR/ereq/EREQ-009.md | 15 +
.../CC2022/SAR/ereq/EREQ-010.md | 15 +
.../CC2022/SAR/ereq/EREQ-011.md | 15 +
.../CC2022/SAR/ereq/EREQ-012.md | 15 +
.../CC2022/SAR/ereq/EREQ-013.md | 15 +
.../CC2022/SAR/ereq/EREQ-014.md | 15 +
.../CC2022/SAR/ereq/EREQ-015.md | 15 +
.../CC2022/SAR/ereq/EREQ-016.md | 15 +
.../CC2022/SAR/ereq/EREQ-017.md | 15 +
.../CC2022/SAR/ereq/EREQ-018.md | 15 +
.../CC2022/SAR/ereq/EREQ-019.md | 15 +
.../CC2022/SAR/ereq/EREQ-020.md | 15 +
.../CC2022/SAR/ereq/EREQ-021.md | 15 +
.../CC2022/SAR/ereq/EREQ-022.md | 15 +
.../CC2022/SAR/ereq/EREQ-023.md | 15 +
.../CC2022/SAR/ereq/EREQ-024.md | 15 +
.../CC2022/SAR/ereq/EREQ-025.md | 15 +
.../CC2022/SAR/ereq/EREQ-026.md | 15 +
.../CC2022/SAR/ereq/EREQ-027.md | 15 +
.../CC2022/SAR/ereq/EREQ-028.md | 15 +
.../CC2022/SAR/ereq/EREQ-029.md | 15 +
.../CC2022/SAR/ereq/EREQ-030.md | 15 +
.../CC2022/SAR/ereq/EREQ-031.md | 15 +
.../CC2022/SAR/ereq/EREQ-032.md | 15 +
.../CC2022/SAR/ereq/EREQ-033.md | 15 +
.../CC2022/SAR/ereq/EREQ-034.md | 15 +
.../CC2022/SAR/ereq/EREQ-035.md | 15 +
.../CC2022/SAR/ereq/EREQ-036.md | 15 +
.../CC2022/SAR/ereq/EREQ-037.md | 15 +
.../CC2022/SAR/ereq/EREQ-038.md | 15 +
.../CC2022/SAR/ereq/EREQ-039.md | 15 +
.../CC2022/SAR/ereq/EREQ-040.md | 15 +
.../CC2022/SAR/ereq/EREQ-041.md | 15 +
.../CC2022/SAR/ereq/EREQ-042.md | 15 +
.../CC2022/SAR/ereq/EREQ-043.md | 15 +
.../CC2022/SAR/ereq/EREQ-044.md | 15 +
.../CC2022/SAR/ereq/EREQ-045.md | 15 +
.../CC2022/SAR/ereq/EREQ-046.md | 15 +
.../CC2022/SAR/ereq/EREQ-047.md | 15 +
.../CC2022/SAR/ereq/EREQ-048.md | 15 +
.../CC2022/SAR/ereq/EREQ-049.md | 15 +
.../CC2022/SAR/ereq/EREQ-050.md | 15 +
.../CC2022/SAR/ereq/EREQ-051.md | 15 +
.../CC2022/SAR/ereq/EREQ-052.md | 15 +
.../CC2022/SAR/ereq/EREQ-053.md | 15 +
.../CC2022/SAR/ereq/EREQ-054.md | 15 +
.../CC2022/SAR/ereq/EREQ-055.md | 15 +
.../CC2022/SAR/ereq/EREQ-056.md | 15 +
.../CC2022/SAR/ereq/EREQ-057.md | 15 +
.../CC2022/SAR/ereq/EREQ-058.md | 15 +
.../CC2022/SAR/ereq/EREQ-059.md | 15 +
.../CC2022/SAR/ereq/EREQ-060.md | 15 +
.../CC2022/SAR/ereq/EREQ-061.md | 15 +
.../CC2022/SAR/ereq/EREQ-062.md | 15 +
.../CC2022/SAR/ereq/EREQ-063.md | 15 +
.../CC2022/SAR/ereq/EREQ-064.md | 15 +
.../CC2022/SAR/ereq/EREQ-065.md | 15 +
.../CC2022/SAR/ereq/EREQ-066.md | 15 +
.../CC2022/SAR/ereq/EREQ-067.md | 15 +
.../CC2022/SAR/ereq/EREQ-068.md | 15 +
.../CC2022/SAR/ereq/EREQ-069.md | 15 +
.../CC2022/SAR/ereq/EREQ-070.md | 15 +
.../CC2022/SAR/ereq/EREQ-071.md | 15 +
.../CC2022/SAR/ereq/EREQ-072.md | 15 +
.../CC2022/SAR/ereq/EREQ-073.md | 15 +
.../CC2022/SAR/ereq/EREQ-074.md | 15 +
.../CC2022/SAR/ereq/EREQ-075.md | 15 +
.../CC2022/SAR/ereq/EREQ-076.md | 15 +
.../CC2022/SAR/ereq/EREQ-077.md | 15 +
.../CC2022/SAR/ereq/EREQ-078.md | 15 +
.../CC2022/SAR/ereq/EREQ-079.md | 15 +
.../CC2022/SAR/ereq/EREQ-080.md | 15 +
.../CC2022/SAR/ereq/EREQ-081.md | 15 +
.../CC2022/SAR/ereq/EREQ-082.md | 15 +
.../CC2022/SAR/ereq/EREQ-083.md | 15 +
.../CC2022/SAR/ereq/EREQ-084.md | 15 +
.../CC2022/SAR/ereq/EREQ-085.md | 15 +
.../CC2022/SAR/ereq/EREQ-086.md | 15 +
.../CC2022/SAR/ereq/EREQ-087.md | 15 +
.../CC2022/SAR/ereq/EREQ-088.md | 15 +
.../CC2022/SAR/ereq/EREQ-089.md | 15 +
.../CC2022/SAR/ereq/EREQ-090.md | 15 +
.../CC2022/SAR/ereq/EREQ-091.md | 15 +
.../CC2022/SAR/ereq/EREQ-092.md | 15 +
.../CC2022/SAR/ereq/EREQ-093.md | 15 +
.../CC2022/SAR/ereq/EREQ-094.md | 15 +
.../CC2022/SAR/ereq/EREQ-095.md | 15 +
.../CC2022/SAR/ereq/EREQ-096.md | 15 +
.../CC2022/SAR/ereq/EREQ-097.md | 15 +
.../CC2022/SAR/ereq/EREQ-098.md | 15 +
.../CC2022/SAR/ereq/EREQ-099.md | 15 +
.../CC2022/SAR/ereq/EREQ-100.md | 15 +
.../CC2022/SAR/ereq/EREQ-101.md | 15 +
.../CC2022/SAR/ereq/EREQ-102.md | 15 +
.../CC2022/SAR/ereq/EREQ-103.md | 15 +
.../CC2022/SAR/ereq/EREQ-104.md | 15 +
.../CC2022/SAR/ereq/EREQ-105.md | 15 +
.../CC2022/SAR/ereq/EREQ-106.md | 15 +
.../CC2022/SAR/ereq/EREQ-107.md | 15 +
.../CC2022/SAR/ereq/EREQ-108.md | 15 +
.../CC2022/SAR/ereq/EREQ-109.md | 15 +
.../CC2022/SAR/ereq/EREQ-110.md | 15 +
.../CC2022/SAR/ereq/EREQ-111.md | 15 +
.../CC2022/SAR/ereq/EREQ-112.md | 15 +
.../CC2022/SAR/ereq/EREQ-113.md | 15 +
.../CC2022/SAR/ereq/EREQ-114.md | 15 +
.../CC2022/SAR/ereq/EREQ-115.md | 15 +
.../CC2022/SAR/ereq/EREQ-116.md | 15 +
.../CC2022/SAR/ereq/EREQ-117.md | 15 +
.../CC2022/SAR/ereq/EREQ-118.md | 15 +
.../CC2022/SAR/ereq/EREQ-119.md | 15 +
.../CC2022/SAR/ereq/EREQ-120.md | 15 +
.../CC2022/SAR/ereq/EREQ-121.md | 15 +
.../CC2022/SAR/ereq/EREQ-122.md | 15 +
.../CC2022/SAR/ereq/EREQ-123.md | 15 +
.../CC2022/SAR/ereq/EREQ-124.md | 15 +
.../CC2022/SAR/ereq/EREQ-125.md | 15 +
.../CC2022/SAR/ereq/EREQ-126.md | 15 +
.../CC2022/SAR/ereq/EREQ-127.md | 15 +
.../CC2022/SAR/ereq/EREQ-128.md | 15 +
.../CC2022/SAR/ereq/EREQ-129.md | 15 +
.../CC2022/SAR/ereq/EREQ-130.md | 15 +
.../CC2022/SAR/ereq/EREQ-131.md | 15 +
.../CC2022/SAR/ereq/EREQ-132.md | 15 +
.../CC2022/SAR/ereq/EREQ-133.md | 15 +
.../CC2022/SAR/ereq/EREQ-134.md | 15 +
.../CC2022/SAR/ereq/EREQ-135.md | 15 +
.../CC2022/SAR/ereq/EREQ-136.md | 15 +
.../CC2022/SAR/ereq/EREQ-137.md | 15 +
.../CC2022/SAR/ereq/EREQ-138.md | 15 +
.../CC2022/SAR/ereq/EREQ-139.md | 15 +
.../CC2022/SAR/ereq/EREQ-140.md | 15 +
.../CC2022/SAR/ereq/EREQ-141.md | 15 +
.../CC2022/SAR/ereq/EREQ-142.md | 15 +
.../CC2022/SAR/ereq/EREQ-143.md | 15 +
.../CC2022/SAR/ereq/EREQ-144.md | 15 +
.../CC2022/SAR/ereq/EREQ-145.md | 15 +
.../CC2022/SAR/ereq/EREQ-146.md | 15 +
.../CC2022/SAR/ereq/EREQ-147.md | 15 +
.../CC2022/SAR/ereq/EREQ-148.md | 15 +
.../CC2022/SAR/ereq/EREQ-149.md | 15 +
.../CC2022/SAR/ereq/EREQ-150.md | 15 +
.../CC2022/SAR/ereq/EREQ-151.md | 15 +
.../CC2022/SAR/ereq/EREQ-152.md | 15 +
.../CC2022/SAR/ereq/EREQ-153.md | 15 +
.../CC2022/SAR/ereq/EREQ-154.md | 15 +
.../CC2022/SAR/ereq/EREQ-155.md | 15 +
.../CC2022/SAR/ereq/EREQ-156.md | 15 +
.../CC2022/SAR/ereq/EREQ-157.md | 15 +
.../CC2022/SAR/ereq/EREQ-158.md | 15 +
.../CC2022/SAR/ereq/EREQ-159.md | 15 +
.../CC2022/SAR/ereq/EREQ-160.md | 15 +
.../CC2022/SAR/ereq/EREQ-161.md | 15 +
.../CC2022/SAR/ereq/EREQ-162.md | 15 +
.../CC2022/SAR/ereq/EREQ-163.md | 15 +
.../CC2022/SAR/ereq/EREQ-164.md | 15 +
.../CC2022/SAR/ereq/EREQ-165.md | 15 +
.../CC2022/SAR/ereq/EREQ-166.md | 15 +
.../CC2022/SAR/ereq/EREQ-167.md | 15 +
.../CC2022/SAR/ereq/EREQ-168.md | 15 +
.../CC2022/SAR/ereq/EREQ-169.md | 15 +
.../CC2022/SAR/ereq/EREQ-170.md | 15 +
.../CC2022/SAR/ereq/EREQ-171.md | 15 +
.../CC2022/SAR/ereq/EREQ-172.md | 15 +
.../CC2022/SAR/ereq/EREQ-173.md | 15 +
.../CC2022/SAR/ereq/EREQ-174.md | 15 +
.../CC2022/SAR/ereq/EREQ-175.md | 15 +
.../CC2022/SAR/ereq/EREQ-176.md | 15 +
.../CC2022/SAR/ereq/EREQ-177.md | 15 +
.../CC2022/SAR/ereq/EREQ-178.md | 15 +
.../CC2022/SAR/ereq/EREQ-179.md | 15 +
.../CC2022/SAR/ereq/EREQ-180.md | 15 +
.../CC2022/SAR/ereq/EREQ-181.md | 15 +
.../CC2022/SAR/ereq/EREQ-182.md | 15 +
.../CC2022/SAR/ereq/EREQ-183.md | 15 +
.../CC2022/SAR/ereq/EREQ-184.md | 15 +
.../CC2022/SAR/ereq/EREQ-185.md | 15 +
.../CC2022/SAR/ereq/EREQ-186.md | 15 +
.../CC2022/SAR/ereq/EREQ-187.md | 15 +
.../CC2022/SAR/ereq/EREQ-188.md | 15 +
.../CC2022/SAR/ereq/EREQ-189.md | 15 +
.../CC2022/SAR/ereq/EREQ-190.md | 15 +
.../CC2022/SAR/ereq/EREQ-191.md | 15 +
.../CC2022/SAR/family/.doorstop.yml | 17 +
.../CC2022/SAR/family/AFML-001.md | 18 +
.../CC2022/SAR/family/AFML-002.md | 18 +
.../CC2022/SAR/family/AFML-003.md | 18 +
.../CC2022/SAR/family/AFML-004.md | 18 +
.../CC2022/SAR/family/AFML-005.md | 19 +
.../CC2022/SAR/family/AFML-006.md | 18 +
.../CC2022/SAR/family/AFML-007.md | 18 +
.../CC2022/SAR/family/AFML-008.md | 18 +
.../CC2022/SAR/family/AFML-009.md | 19 +
.../CC2022/SAR/family/AFML-010.md | 18 +
.../CC2022/SAR/family/AFML-011.md | 19 +
.../CC2022/SAR/family/AFML-012.md | 18 +
.../CC2022/SAR/family/AFML-013.md | 18 +
.../CC2022/SAR/family/AFML-014.md | 18 +
.../CC2022/SAR/family/AFML-015.md | 18 +
.../CC2022/SAR/family/AFML-016.md | 18 +
.../CC2022/SAR/family/AFML-017.md | 19 +
.../CC2022/SAR/family/AFML-018.md | 18 +
.../CC2022/SAR/family/AFML-019.md | 19 +
.../CC2022/SAR/family/AFML-020.md | 19 +
.../CC2022/SAR/family/AFML-021.md | 19 +
.../CC2022/SAR/family/AFML-022.md | 19 +
.../CC2022/SAR/family/AFML-023.md | 24 +
.../CC2022/SAR/family/AFML-024.md | 20 +
.../CC2022/SAR/family/AFML-025.md | 9 +
.../CC2022/SAR/family/AFML-026.md | 19 +
.../CC2022/SAR/family/AFML-027.md | 23 +
.../CC2022/SAR/family/AFML-028.md | 19 +
.../CC2022/SAR/family/AFML-029.md | 9 +
.../CC2022/SAR/family/AFML-030.md | 19 +
.../CC2022/SAR/family/AFML-031.md | 20 +
.../CC2022/SAR/family/AFML-032.md | 9 +
.../CC2022/SAR/family/AFML-033.md | 20 +
.../CC2022/SAR/family/AFML-034.md | 20 +
.../CC2022/SAR/family/AFML-035.md | 20 +
.../CC2022/SAR/family/AFML-036.md | 20 +
.../CC2022/SAR/family/AFML-037.md | 20 +
.../CC2022/SAR/family/AFML-038.md | 20 +
.../CC2022/SAR/family/AFML-039.md | 20 +
.../CC2022/SAR/family/AFML-040.md | 9 +
.../CC2022/SAR/family/AFML-041.md | 20 +
.../CC2022/SAR/family/AFML-042.md | 20 +
.../CC2022/SAR/family/AFML-043.md | 20 +
.../CC2022/SAR/family/AFML-044.md | 19 +
.../CC2022/SAR/family/AFML-045.md | 19 +
.../CC2022/SAR/family/AFML-046.md | 19 +
.../CC2022/SAR/family/AFML-047.md | 18 +
.../CC2022/SAR/family/AFML-048.md | 20 +
.../CC2022/SAR/family/AFML-049.md | 20 +
.../CC2022/SAR/family/AFML-050.md | 20 +
.../CC2022/SAR/family/AFML-051.md | 20 +
.../CC2022/SAR/family/AFML-052.md | 19 +
.../SecurityControls/CC2022/SFR/.doorstop.yml | 10 +
.../SecurityControls/CC2022/SFR/CCC-001.md | 27 +
.../SecurityControls/CC2022/SFR/CCC-002.md | 17 +
.../SecurityControls/CC2022/SFR/CCC-003.md | 18 +
.../SecurityControls/CC2022/SFR/CCC-004.md | 41 +
.../SecurityControls/CC2022/SFR/CCC-005.md | 18 +
.../SecurityControls/CC2022/SFR/CCC-006.md | 23 +
.../SecurityControls/CC2022/SFR/CCC-007.md | 18 +
.../SecurityControls/CC2022/SFR/CCC-008.md | 23 +
.../SecurityControls/CC2022/SFR/CCC-009.md | 19 +
.../SecurityControls/CC2022/SFR/CCC-010.md | 18 +
.../SecurityControls/CC2022/SFR/CCC-011.md | 24 +
.../CC2022/SFR/component/.doorstop.yml | 22 +
.../CC2022/SFR/component/COM-001.md | 22 +
.../CC2022/SFR/component/COM-002.md | 22 +
.../CC2022/SFR/component/COM-003.md | 23 +
.../CC2022/SFR/component/COM-004.md | 22 +
.../CC2022/SFR/component/COM-005.md | 22 +
.../CC2022/SFR/component/COM-006.md | 22 +
.../CC2022/SFR/component/COM-007.md | 22 +
.../CC2022/SFR/component/COM-008.md | 22 +
.../CC2022/SFR/component/COM-009.md | 22 +
.../CC2022/SFR/component/COM-010.md | 22 +
.../CC2022/SFR/component/COM-011.md | 22 +
.../CC2022/SFR/component/COM-012.md | 23 +
.../CC2022/SFR/component/COM-013.md | 22 +
.../CC2022/SFR/component/COM-014.md | 22 +
.../CC2022/SFR/component/COM-015.md | 22 +
.../CC2022/SFR/component/COM-016.md | 23 +
.../CC2022/SFR/component/COM-017.md | 22 +
.../CC2022/SFR/component/COM-018.md | 22 +
.../CC2022/SFR/component/COM-019.md | 22 +
.../CC2022/SFR/component/COM-020.md | 22 +
.../CC2022/SFR/component/COM-021.md | 23 +
.../CC2022/SFR/component/COM-022.md | 23 +
.../CC2022/SFR/component/COM-023.md | 23 +
.../CC2022/SFR/component/COM-024.md | 20 +
.../CC2022/SFR/component/COM-025.md | 23 +
.../CC2022/SFR/component/COM-026.md | 23 +
.../CC2022/SFR/component/COM-027.md | 23 +
.../CC2022/SFR/component/COM-028.md | 23 +
.../CC2022/SFR/component/COM-029.md | 22 +
.../CC2022/SFR/component/COM-030.md | 22 +
.../CC2022/SFR/component/COM-031.md | 23 +
.../CC2022/SFR/component/COM-032.md | 23 +
.../CC2022/SFR/component/COM-033.md | 22 +
.../CC2022/SFR/component/COM-034.md | 22 +
.../CC2022/SFR/component/COM-035.md | 22 +
.../CC2022/SFR/component/COM-036.md | 22 +
.../CC2022/SFR/component/COM-037.md | 22 +
.../CC2022/SFR/component/COM-038.md | 22 +
.../CC2022/SFR/component/COM-039.md | 22 +
.../CC2022/SFR/component/COM-040.md | 23 +
.../CC2022/SFR/component/COM-041.md | 23 +
.../CC2022/SFR/component/COM-042.md | 22 +
.../CC2022/SFR/component/COM-043.md | 22 +
.../CC2022/SFR/component/COM-044.md | 23 +
.../CC2022/SFR/component/COM-045.md | 23 +
.../CC2022/SFR/component/COM-046.md | 22 +
.../CC2022/SFR/component/COM-047.md | 22 +
.../CC2022/SFR/component/COM-048.md | 22 +
.../CC2022/SFR/component/COM-049.md | 22 +
.../CC2022/SFR/component/COM-050.md | 22 +
.../CC2022/SFR/component/COM-051.md | 23 +
.../CC2022/SFR/component/COM-052.md | 23 +
.../CC2022/SFR/component/COM-053.md | 23 +
.../CC2022/SFR/component/COM-054.md | 23 +
.../CC2022/SFR/component/COM-055.md | 23 +
.../CC2022/SFR/component/COM-056.md | 23 +
.../CC2022/SFR/component/COM-057.md | 22 +
.../CC2022/SFR/component/COM-058.md | 22 +
.../CC2022/SFR/component/COM-059.md | 23 +
.../CC2022/SFR/component/COM-060.md | 23 +
.../CC2022/SFR/component/COM-061.md | 22 +
.../CC2022/SFR/component/COM-062.md | 22 +
.../CC2022/SFR/component/COM-063.md | 22 +
.../CC2022/SFR/component/COM-064.md | 22 +
.../CC2022/SFR/component/COM-065.md | 23 +
.../CC2022/SFR/component/COM-066.md | 23 +
.../CC2022/SFR/component/COM-067.md | 23 +
.../CC2022/SFR/component/COM-068.md | 23 +
.../CC2022/SFR/component/COM-069.md | 22 +
.../CC2022/SFR/component/COM-070.md | 22 +
.../CC2022/SFR/component/COM-071.md | 22 +
.../CC2022/SFR/component/COM-072.md | 22 +
.../CC2022/SFR/component/COM-073.md | 22 +
.../CC2022/SFR/component/COM-074.md | 22 +
.../CC2022/SFR/component/COM-075.md | 22 +
.../CC2022/SFR/component/COM-076.md | 22 +
.../CC2022/SFR/component/COM-077.md | 22 +
.../CC2022/SFR/component/COM-078.md | 22 +
.../CC2022/SFR/component/COM-079.md | 22 +
.../CC2022/SFR/component/COM-080.md | 22 +
.../CC2022/SFR/component/COM-081.md | 22 +
.../CC2022/SFR/component/COM-082.md | 22 +
.../CC2022/SFR/component/COM-083.md | 22 +
.../CC2022/SFR/component/COM-084.md | 22 +
.../CC2022/SFR/component/COM-085.md | 21 +
.../CC2022/SFR/component/COM-086.md | 23 +
.../CC2022/SFR/component/COM-087.md | 23 +
.../CC2022/SFR/component/COM-088.md | 23 +
.../CC2022/SFR/component/COM-089.md | 23 +
.../CC2022/SFR/component/COM-090.md | 23 +
.../CC2022/SFR/component/COM-091.md | 23 +
.../CC2022/SFR/component/COM-092.md | 22 +
.../CC2022/SFR/component/COM-093.md | 22 +
.../CC2022/SFR/component/COM-094.md | 22 +
.../CC2022/SFR/component/COM-095.md | 22 +
.../CC2022/SFR/component/COM-096.md | 22 +
.../CC2022/SFR/component/COM-097.md | 22 +
.../CC2022/SFR/component/COM-098.md | 22 +
.../CC2022/SFR/component/COM-099.md | 22 +
.../CC2022/SFR/component/COM-100.md | 22 +
.../CC2022/SFR/component/COM-101.md | 22 +
.../CC2022/SFR/component/COM-102.md | 22 +
.../CC2022/SFR/component/COM-103.md | 22 +
.../CC2022/SFR/component/COM-104.md | 22 +
.../CC2022/SFR/component/COM-105.md | 22 +
.../CC2022/SFR/component/COM-106.md | 22 +
.../CC2022/SFR/component/COM-107.md | 22 +
.../CC2022/SFR/component/COM-108.md | 22 +
.../CC2022/SFR/component/COM-109.md | 22 +
.../CC2022/SFR/component/COM-110.md | 22 +
.../CC2022/SFR/component/COM-111.md | 22 +
.../CC2022/SFR/component/COM-112.md | 22 +
.../CC2022/SFR/component/COM-113.md | 22 +
.../CC2022/SFR/component/COM-114.md | 22 +
.../CC2022/SFR/component/COM-115.md | 22 +
.../CC2022/SFR/component/COM-116.md | 22 +
.../CC2022/SFR/component/COM-117.md | 22 +
.../CC2022/SFR/component/COM-118.md | 22 +
.../CC2022/SFR/component/COM-119.md | 22 +
.../CC2022/SFR/component/COM-120.md | 22 +
.../CC2022/SFR/component/COM-121.md | 22 +
.../CC2022/SFR/component/COM-122.md | 22 +
.../CC2022/SFR/component/COM-123.md | 22 +
.../CC2022/SFR/component/COM-124.md | 22 +
.../CC2022/SFR/component/COM-125.md | 22 +
.../CC2022/SFR/component/COM-126.md | 22 +
.../CC2022/SFR/component/COM-127.md | 22 +
.../CC2022/SFR/component/COM-128.md | 22 +
.../CC2022/SFR/component/COM-129.md | 22 +
.../CC2022/SFR/component/COM-130.md | 22 +
.../CC2022/SFR/component/COM-131.md | 22 +
.../CC2022/SFR/component/COM-132.md | 22 +
.../CC2022/SFR/component/COM-133.md | 22 +
.../CC2022/SFR/component/COM-134.md | 22 +
.../CC2022/SFR/component/COM-135.md | 22 +
.../CC2022/SFR/component/COM-136.md | 22 +
.../CC2022/SFR/component/COM-137.md | 22 +
.../CC2022/SFR/component/COM-138.md | 22 +
.../CC2022/SFR/component/COM-139.md | 22 +
.../CC2022/SFR/component/COM-140.md | 22 +
.../CC2022/SFR/component/COM-141.md | 22 +
.../CC2022/SFR/component/COM-142.md | 22 +
.../CC2022/SFR/component/COM-143.md | 22 +
.../CC2022/SFR/component/COM-144.md | 22 +
.../CC2022/SFR/component/COM-145.md | 22 +
.../CC2022/SFR/component/COM-146.md | 22 +
.../CC2022/SFR/component/COM-147.md | 22 +
.../CC2022/SFR/component/COM-148.md | 22 +
.../CC2022/SFR/component/COM-149.md | 22 +
.../CC2022/SFR/component/COM-150.md | 22 +
.../CC2022/SFR/component/COM-151.md | 22 +
.../CC2022/SFR/component/COM-152.md | 22 +
.../CC2022/SFR/component/COM-153.md | 23 +
.../CC2022/SFR/component/COM-154.md | 23 +
.../CC2022/SFR/component/COM-155.md | 23 +
.../CC2022/SFR/component/COM-156.md | 22 +
.../CC2022/SFR/family/.doorstop.yml | 13 +
.../CC2022/SFR/family/FML-001.md | 16 +
.../CC2022/SFR/family/FML-002.md | 16 +
.../CC2022/SFR/family/FML-003.md | 16 +
.../CC2022/SFR/family/FML-004.md | 16 +
.../CC2022/SFR/family/FML-005.md | 16 +
.../CC2022/SFR/family/FML-006.md | 16 +
.../CC2022/SFR/family/FML-007.md | 16 +
.../CC2022/SFR/family/FML-008.md | 16 +
.../CC2022/SFR/family/FML-009.md | 16 +
.../CC2022/SFR/family/FML-010.md | 16 +
.../CC2022/SFR/family/FML-011.md | 16 +
.../CC2022/SFR/family/FML-012.md | 16 +
.../CC2022/SFR/family/FML-013.md | 16 +
.../CC2022/SFR/family/FML-014.md | 18 +
.../CC2022/SFR/family/FML-015.md | 16 +
.../CC2022/SFR/family/FML-016.md | 17 +
.../CC2022/SFR/family/FML-017.md | 16 +
.../CC2022/SFR/family/FML-018.md | 16 +
.../CC2022/SFR/family/FML-019.md | 16 +
.../CC2022/SFR/family/FML-020.md | 16 +
.../CC2022/SFR/family/FML-021.md | 16 +
.../CC2022/SFR/family/FML-022.md | 17 +
.../CC2022/SFR/family/FML-023.md | 16 +
.../CC2022/SFR/family/FML-024.md | 16 +
.../CC2022/SFR/family/FML-025.md | 16 +
.../CC2022/SFR/family/FML-026.md | 16 +
.../CC2022/SFR/family/FML-027.md | 16 +
.../CC2022/SFR/family/FML-028.md | 16 +
.../CC2022/SFR/family/FML-029.md | 16 +
.../CC2022/SFR/family/FML-030.md | 16 +
.../CC2022/SFR/family/FML-031.md | 16 +
.../CC2022/SFR/family/FML-032.md | 16 +
.../CC2022/SFR/family/FML-033.md | 16 +
.../CC2022/SFR/family/FML-034.md | 16 +
.../CC2022/SFR/family/FML-035.md | 16 +
.../CC2022/SFR/family/FML-036.md | 16 +
.../CC2022/SFR/family/FML-037.md | 16 +
.../CC2022/SFR/family/FML-038.md | 16 +
.../CC2022/SFR/family/FML-039.md | 16 +
.../CC2022/SFR/family/FML-040.md | 16 +
.../CC2022/SFR/family/FML-041.md | 16 +
.../CC2022/SFR/family/FML-042.md | 16 +
.../CC2022/SFR/family/FML-043.md | 16 +
.../CC2022/SFR/family/FML-044.md | 16 +
.../CC2022/SFR/family/FML-045.md | 16 +
.../CC2022/SFR/family/FML-046.md | 16 +
.../CC2022/SFR/family/FML-047.md | 16 +
.../CC2022/SFR/family/FML-048.md | 16 +
.../CC2022/SFR/family/FML-049.md | 16 +
.../CC2022/SFR/family/FML-050.md | 17 +
.../CC2022/SFR/family/FML-051.md | 16 +
.../CC2022/SFR/family/FML-052.md | 16 +
.../CC2022/SFR/family/FML-053.md | 16 +
.../CC2022/SFR/family/FML-054.md | 16 +
.../CC2022/SFR/family/FML-055.md | 16 +
.../CC2022/SFR/family/FML-056.md | 16 +
.../CC2022/SFR/family/FML-057.md | 16 +
.../CC2022/SFR/family/FML-058.md | 16 +
.../CC2022/SFR/family/FML-059.md | 16 +
.../CC2022/SFR/family/FML-060.md | 16 +
.../CC2022/SFR/family/FML-061.md | 16 +
.../CC2022/SFR/family/FML-062.md | 16 +
.../CC2022/SFR/family/FML-063.md | 16 +
.../CC2022/SFR/family/FML-064.md | 16 +
.../CC2022/SFR/family/FML-065.md | 16 +
.../CC2022/SFR/family/FML-066.md | 16 +
.../CC2022/SFR/family/FML-067.md | 16 +
.../CC2022/SFR/family/FML-068.md | 16 +
.../CC2022/SFR/family/FML-069.md | 16 +
.../CC2022/SFR/family/FML-070.md | 16 +
.../CC2022/SFR/family/FML-071.md | 16 +
.../CC2022/SFR/family/FML-072.md | 16 +
.../CC2022/SFR/family/FML-073.md | 16 +
.../CC2022/SFR/family/FML-074.md | 16 +
.../CC2022/SFR/req/.doorstop.yml | 11 +
.../CC2022/SFR/req/REQ-001.md | 15 +
.../CC2022/SFR/req/REQ-002.md | 15 +
.../CC2022/SFR/req/REQ-003.md | 15 +
.../CC2022/SFR/req/REQ-004.md | 15 +
.../CC2022/SFR/req/REQ-005.md | 15 +
.../CC2022/SFR/req/REQ-006.md | 15 +
.../CC2022/SFR/req/REQ-007.md | 15 +
.../CC2022/SFR/req/REQ-008.md | 15 +
.../CC2022/SFR/req/REQ-009.md | 15 +
.../CC2022/SFR/req/REQ-010.md | 15 +
.../CC2022/SFR/req/REQ-011.md | 15 +
.../CC2022/SFR/req/REQ-012.md | 15 +
.../CC2022/SFR/req/REQ-013.md | 15 +
.../CC2022/SFR/req/REQ-014.md | 15 +
.../CC2022/SFR/req/REQ-015.md | 15 +
.../CC2022/SFR/req/REQ-016.md | 15 +
.../CC2022/SFR/req/REQ-017.md | 15 +
.../CC2022/SFR/req/REQ-018.md | 15 +
.../CC2022/SFR/req/REQ-019.md | 15 +
.../CC2022/SFR/req/REQ-020.md | 15 +
.../CC2022/SFR/req/REQ-021.md | 15 +
.../CC2022/SFR/req/REQ-022.md | 15 +
.../CC2022/SFR/req/REQ-023.md | 15 +
.../CC2022/SFR/req/REQ-024.md | 15 +
.../CC2022/SFR/req/REQ-025.md | 15 +
.../CC2022/SFR/req/REQ-026.md | 15 +
.../CC2022/SFR/req/REQ-027.md | 15 +
.../CC2022/SFR/req/REQ-028.md | 15 +
.../CC2022/SFR/req/REQ-029.md | 15 +
.../CC2022/SFR/req/REQ-030.md | 15 +
.../CC2022/SFR/req/REQ-031.md | 15 +
.../CC2022/SFR/req/REQ-032.md | 15 +
.../CC2022/SFR/req/REQ-033.md | 15 +
.../CC2022/SFR/req/REQ-034.md | 15 +
.../CC2022/SFR/req/REQ-035.md | 15 +
.../CC2022/SFR/req/REQ-036.md | 15 +
.../CC2022/SFR/req/REQ-037.md | 15 +
.../CC2022/SFR/req/REQ-038.md | 15 +
.../CC2022/SFR/req/REQ-039.md | 15 +
.../CC2022/SFR/req/REQ-040.md | 15 +
.../CC2022/SFR/req/REQ-041.md | 15 +
.../CC2022/SFR/req/REQ-042.md | 15 +
.../CC2022/SFR/req/REQ-043.md | 15 +
.../CC2022/SFR/req/REQ-044.md | 15 +
.../CC2022/SFR/req/REQ-045.md | 15 +
.../CC2022/SFR/req/REQ-046.md | 15 +
.../CC2022/SFR/req/REQ-047.md | 15 +
.../CC2022/SFR/req/REQ-048.md | 15 +
.../CC2022/SFR/req/REQ-049.md | 15 +
.../CC2022/SFR/req/REQ-050.md | 15 +
.../CC2022/SFR/req/REQ-051.md | 15 +
.../CC2022/SFR/req/REQ-052.md | 15 +
.../CC2022/SFR/req/REQ-053.md | 15 +
.../CC2022/SFR/req/REQ-054.md | 15 +
.../CC2022/SFR/req/REQ-055.md | 15 +
.../CC2022/SFR/req/REQ-056.md | 15 +
.../CC2022/SFR/req/REQ-057.md | 15 +
.../CC2022/SFR/req/REQ-058.md | 15 +
.../CC2022/SFR/req/REQ-059.md | 15 +
.../CC2022/SFR/req/REQ-060.md | 15 +
.../CC2022/SFR/req/REQ-061.md | 15 +
.../CC2022/SFR/req/REQ-062.md | 15 +
.../CC2022/SFR/req/REQ-063.md | 15 +
.../CC2022/SFR/req/REQ-064.md | 15 +
.../CC2022/SFR/req/REQ-065.md | 15 +
.../CC2022/SFR/req/REQ-066.md | 15 +
.../CC2022/SFR/req/REQ-067.md | 15 +
.../CC2022/SFR/req/REQ-068.md | 15 +
.../CC2022/SFR/req/REQ-069.md | 15 +
.../CC2022/SFR/req/REQ-070.md | 15 +
.../CC2022/SFR/req/REQ-071.md | 15 +
.../CC2022/SFR/req/REQ-072.md | 15 +
.../CC2022/SFR/req/REQ-073.md | 15 +
.../CC2022/SFR/req/REQ-074.md | 15 +
.../CC2022/SFR/req/REQ-075.md | 15 +
.../CC2022/SFR/req/REQ-076.md | 15 +
.../CC2022/SFR/req/REQ-077.md | 15 +
.../CC2022/SFR/req/REQ-078.md | 15 +
.../CC2022/SFR/req/REQ-079.md | 15 +
.../CC2022/SFR/req/REQ-080.md | 15 +
.../CC2022/SFR/req/REQ-081.md | 15 +
.../CC2022/SFR/req/REQ-082.md | 15 +
.../CC2022/SFR/req/REQ-083.md | 15 +
.../CC2022/SFR/req/REQ-084.md | 15 +
.../CC2022/SFR/req/REQ-085.md | 15 +
.../CC2022/SFR/req/REQ-086.md | 15 +
.../CC2022/SFR/req/REQ-087.md | 15 +
.../CC2022/SFR/req/REQ-088.md | 15 +
.../CC2022/SFR/req/REQ-089.md | 15 +
.../CC2022/SFR/req/REQ-090.md | 15 +
.../CC2022/SFR/req/REQ-091.md | 15 +
.../CC2022/SFR/req/REQ-092.md | 15 +
.../CC2022/SFR/req/REQ-093.md | 15 +
.../CC2022/SFR/req/REQ-094.md | 15 +
.../CC2022/SFR/req/REQ-095.md | 15 +
.../CC2022/SFR/req/REQ-096.md | 15 +
.../CC2022/SFR/req/REQ-097.md | 15 +
.../CC2022/SFR/req/REQ-098.md | 15 +
.../CC2022/SFR/req/REQ-099.md | 15 +
.../CC2022/SFR/req/REQ-100.md | 15 +
.../CC2022/SFR/req/REQ-101.md | 15 +
.../CC2022/SFR/req/REQ-102.md | 15 +
.../CC2022/SFR/req/REQ-103.md | 15 +
.../CC2022/SFR/req/REQ-104.md | 15 +
.../CC2022/SFR/req/REQ-105.md | 15 +
.../CC2022/SFR/req/REQ-106.md | 15 +
.../CC2022/SFR/req/REQ-107.md | 15 +
.../CC2022/SFR/req/REQ-108.md | 15 +
.../CC2022/SFR/req/REQ-109.md | 15 +
.../CC2022/SFR/req/REQ-110.md | 15 +
.../CC2022/SFR/req/REQ-111.md | 15 +
.../CC2022/SFR/req/REQ-112.md | 15 +
.../CC2022/SFR/req/REQ-113.md | 15 +
.../CC2022/SFR/req/REQ-114.md | 15 +
.../CC2022/SFR/req/REQ-115.md | 15 +
.../CC2022/SFR/req/REQ-116.md | 15 +
.../CC2022/SFR/req/REQ-117.md | 15 +
.../CC2022/SFR/req/REQ-118.md | 15 +
.../CC2022/SFR/req/REQ-119.md | 15 +
.../CC2022/SFR/req/REQ-120.md | 15 +
.../CC2022/SFR/req/REQ-121.md | 15 +
.../CC2022/SFR/req/REQ-122.md | 15 +
.../CC2022/SFR/req/REQ-123.md | 15 +
.../CC2022/SFR/req/REQ-124.md | 15 +
.../CC2022/SFR/req/REQ-125.md | 15 +
.../CC2022/SFR/req/REQ-126.md | 15 +
.../CC2022/SFR/req/REQ-127.md | 15 +
.../CC2022/SFR/req/REQ-128.md | 15 +
.../CC2022/SFR/req/REQ-129.md | 15 +
.../CC2022/SFR/req/REQ-130.md | 15 +
.../CC2022/SFR/req/REQ-131.md | 15 +
.../CC2022/SFR/req/REQ-132.md | 15 +
.../CC2022/SFR/req/REQ-133.md | 15 +
.../CC2022/SFR/req/REQ-134.md | 15 +
.../CC2022/SFR/req/REQ-135.md | 15 +
.../CC2022/SFR/req/REQ-136.md | 15 +
.../CC2022/SFR/req/REQ-137.md | 15 +
.../CC2022/SFR/req/REQ-138.md | 15 +
.../CC2022/SFR/req/REQ-139.md | 15 +
.../CC2022/SFR/req/REQ-140.md | 15 +
.../CC2022/SFR/req/REQ-141.md | 15 +
.../CC2022/SFR/req/REQ-142.md | 15 +
.../CC2022/SFR/req/REQ-143.md | 15 +
.../CC2022/SFR/req/REQ-144.md | 15 +
.../CC2022/SFR/req/REQ-145.md | 15 +
.../CC2022/SFR/req/REQ-146.md | 15 +
.../CC2022/SFR/req/REQ-147.md | 15 +
.../CC2022/SFR/req/REQ-148.md | 15 +
.../CC2022/SFR/req/REQ-149.md | 15 +
.../CC2022/SFR/req/REQ-150.md | 15 +
.../CC2022/SFR/req/REQ-151.md | 15 +
.../CC2022/SFR/req/REQ-152.md | 15 +
.../CC2022/SFR/req/REQ-153.md | 15 +
.../CC2022/SFR/req/REQ-154.md | 15 +
.../CC2022/SFR/req/REQ-155.md | 15 +
.../CC2022/SFR/req/REQ-156.md | 15 +
.../CC2022/SFR/req/REQ-157.md | 15 +
.../CC2022/SFR/req/REQ-158.md | 15 +
.../CC2022/SFR/req/REQ-159.md | 15 +
.../CC2022/SFR/req/REQ-160.md | 15 +
.../CC2022/SFR/req/REQ-161.md | 15 +
.../CC2022/SFR/req/REQ-162.md | 15 +
.../CC2022/SFR/req/REQ-163.md | 15 +
.../CC2022/SFR/req/REQ-164.md | 15 +
.../CC2022/SFR/req/REQ-165.md | 15 +
.../CC2022/SFR/req/REQ-166.md | 15 +
.../CC2022/SFR/req/REQ-167.md | 15 +
.../CC2022/SFR/req/REQ-168.md | 15 +
.../CC2022/SFR/req/REQ-169.md | 15 +
.../CC2022/SFR/req/REQ-170.md | 15 +
.../CC2022/SFR/req/REQ-171.md | 15 +
.../CC2022/SFR/req/REQ-172.md | 15 +
.../CC2022/SFR/req/REQ-173.md | 15 +
.../CC2022/SFR/req/REQ-174.md | 15 +
.../CC2022/SFR/req/REQ-175.md | 15 +
.../CC2022/SFR/req/REQ-176.md | 15 +
.../CC2022/SFR/req/REQ-177.md | 15 +
.../CC2022/SFR/req/REQ-178.md | 15 +
.../CC2022/SFR/req/REQ-179.md | 15 +
.../CC2022/SFR/req/REQ-180.md | 15 +
.../CC2022/SFR/req/REQ-181.md | 15 +
.../CC2022/SFR/req/REQ-182.md | 15 +
.../CC2022/SFR/req/REQ-183.md | 15 +
.../CC2022/SFR/req/REQ-184.md | 15 +
.../CC2022/SFR/req/REQ-185.md | 15 +
.../CC2022/SFR/req/REQ-186.md | 15 +
.../CC2022/SFR/req/REQ-187.md | 15 +
.../CC2022/SFR/req/REQ-188.md | 15 +
.../CC2022/SFR/req/REQ-189.md | 15 +
.../CC2022/SFR/req/REQ-190.md | 15 +
.../CC2022/SFR/req/REQ-191.md | 15 +
.../CC2022/SFR/req/REQ-192.md | 15 +
.../CC2022/SFR/req/REQ-193.md | 15 +
.../CC2022/SFR/req/REQ-194.md | 15 +
.../CC2022/SFR/req/REQ-195.md | 15 +
.../CC2022/SFR/req/REQ-196.md | 15 +
.../CC2022/SFR/req/REQ-197.md | 15 +
.../CC2022/SFR/req/REQ-198.md | 15 +
.../CC2022/SFR/req/REQ-199.md | 15 +
.../CC2022/SFR/req/REQ-200.md | 15 +
.../CC2022/SFR/req/REQ-201.md | 15 +
.../CC2022/SFR/req/REQ-202.md | 15 +
.../CC2022/SFR/req/REQ-203.md | 15 +
.../CC2022/SFR/req/REQ-204.md | 15 +
.../CC2022/SFR/req/REQ-205.md | 15 +
.../CC2022/SFR/req/REQ-206.md | 15 +
.../CC2022/SFR/req/REQ-207.md | 15 +
.../CC2022/SFR/req/REQ-208.md | 15 +
.../CC2022/SFR/req/REQ-209.md | 15 +
.../CC2022/SFR/req/REQ-210.md | 15 +
.../CC2022/SFR/req/REQ-211.md | 15 +
.../CC2022/SFR/req/REQ-212.md | 15 +
.../CC2022/SFR/req/REQ-213.md | 15 +
.../CC2022/SFR/req/REQ-214.md | 15 +
.../CC2022/SFR/req/REQ-215.md | 15 +
.../CC2022/SFR/req/REQ-216.md | 15 +
.../CC2022/SFR/req/REQ-217.md | 15 +
.../CC2022/SFR/req/REQ-218.md | 15 +
.../CC2022/SFR/req/REQ-219.md | 15 +
.../CC2022/SFR/req/REQ-220.md | 15 +
.../CC2022/SFR/req/REQ-221.md | 15 +
.../CC2022/SFR/req/REQ-222.md | 15 +
.../CC2022/SFR/req/REQ-223.md | 15 +
.../CC2022/SFR/req/REQ-224.md | 15 +
.../CC2022/SFR/req/REQ-225.md | 15 +
.../CC2022/SFR/req/REQ-226.md | 15 +
.../CC2022/SFR/req/REQ-227.md | 15 +
.../CC2022/SFR/req/REQ-228.md | 15 +
.../CC2022/SFR/req/REQ-229.md | 15 +
.../CC2022/SFR/req/REQ-230.md | 15 +
.../CC2022/SFR/req/REQ-231.md | 15 +
.../CC2022/SFR/req/REQ-232.md | 15 +
.../CC2022/SFR/req/REQ-233.md | 15 +
.../CC2022/SFR/req/REQ-234.md | 15 +
.../CC2022/SFR/req/REQ-235.md | 15 +
.../CC2022/SFR/req/REQ-236.md | 15 +
.../CC2022/SFR/req/REQ-237.md | 15 +
.../CC2022/SFR/req/REQ-238.md | 15 +
.../CC2022/SFR/req/REQ-239.md | 15 +
.../CC2022/SFR/req/REQ-240.md | 15 +
.../CC2022/SFR/req/REQ-241.md | 15 +
.../CC2022/SFR/req/REQ-242.md | 15 +
.../CC2022/SFR/req/REQ-243.md | 15 +
.../CC2022/SFR/req/REQ-244.md | 15 +
.../CC2022/SFR/req/REQ-245.md | 15 +
.../CC2022/SFR/req/REQ-246.md | 15 +
.../CC2022/SFR/req/REQ-247.md | 15 +
.../CC2022/SFR/req/REQ-248.md | 15 +
.../CC2022/SFR/req/REQ-249.md | 15 +
.../CC2022/SFR/req/REQ-250.md | 15 +
.../CC2022/SFR/req/REQ-251.md | 15 +
.../CC2022/SFR/req/REQ-252.md | 15 +
.../CC2022/SFR/req/REQ-253.md | 15 +
.../CC2022/SFR/req/REQ-254.md | 15 +
.../CC2022/SFR/req/REQ-255.md | 15 +
.../CC2022/SFR/req/REQ-256.md | 15 +
.../CC2022/SFR/req/REQ-257.md | 15 +
.../CC2022/SFR/req/REQ-258.md | 15 +
.../CC2022/SFR/req/REQ-259.md | 15 +
.../CC2022/SFR/req/REQ-260.md | 15 +
.../CC2022/SFR/req/REQ-261.md | 15 +
.../CC2022/SFR/req/REQ-262.md | 15 +
.../CC2022/SFR/req/REQ-263.md | 15 +
.../CC2022/SFR/req/REQ-264.md | 15 +
.../CC2022/SFR/req/REQ-265.md | 15 +
.../CC2022/SFR/req/REQ-266.md | 15 +
.../CC2022/SFR/req/REQ-267.md | 15 +
.../CC2022/SFR/req/REQ-268.md | 15 +
.../CC2022/SFR/req/REQ-269.md | 15 +
.../CC2022/SFR/req/REQ-270.md | 15 +
.../CC2022/SFR/req/REQ-271.md | 15 +
.../CC2022/SFR/req/REQ-272.md | 15 +
.../CC2022/SFR/req/REQ-273.md | 15 +
.../CC2022/SFR/req/REQ-274.md | 15 +
.../CC2022/SFR/req/REQ-275.md | 15 +
.../CC2022/SFR/req/REQ-276.md | 15 +
.../CC2022/SFR/req/REQ-277.md | 15 +
.../CC2022/SFR/req/REQ-278.md | 15 +
.../CC2022/SFR/req/REQ-279.md | 15 +
.../CC2022/SFR/req/REQ-280.md | 15 +
.../CC2022/SFR/req/REQ-281.md | 15 +
.../CC2022/SFR/req/REQ-282.md | 15 +
.../CC2022/SFR/req/REQ-283.md | 15 +
.../database/SecurityControls/cc3R1.xml | 55518 ++++++++++++++++
.../database/SecurityControls/cc3R2.xml | 54639 +++++++++++++++
.../database/SecurityControls/cc3R3.xml | 53805 +++++++++++++++
.../database/SecurityControls/cc3R4.xml | 53993 +++++++++++++++
.../database/SecurityControls/cc3R5.dtd | 498 +
.../database/SecurityControls/cc3R5.xml | 54377 +++++++++++++++
c5dec/assets/scripts/doorstop_mock.sh | 49 +
.../assets/translations/translations.de.json | 97 +
.../assets/translations/translations.en.json | 3 +
.../assets/translations/translations.fr.json | 54 +
c5dec/assets/tshparams/openproject_params.csv | 2 +
c5dec/assets/tshparams/tshformat.json | 36 +
c5dec/common.py | 133 +
c5dec/core/__init__.py | 0
c5dec/core/cct.py | 3605 +
c5dec/core/cpssa.py | 1 +
c5dec/core/cryptography.py | 1 +
c5dec/core/isms.py | 551 +
c5dec/core/pm.py | 205 +
c5dec/core/settings.py | 1 +
c5dec/core/ssdlc.py | 139 +
c5dec/core/transformer.py | 44 +
c5dec/frontend/__init__.py | 3 +
c5dec/frontend/cli/__init__.py | 0
c5dec/frontend/cli/commands.py | 132 +
c5dec/frontend/cli/main.py | 162 +
c5dec/frontend/cli/utils.py | 87 +
c5dec/frontend/tui/__init__.py | 0
c5dec/frontend/tui/application.py | 155 +
c5dec/frontend/tui/foundation/__init__.py | 0
c5dec/frontend/tui/foundation/builder.py | 550 +
c5dec/frontend/tui/foundation/menu.py | 469 +
c5dec/frontend/tui/main.py | 163 +
c5dec/frontend/tui/miniapps/cctapp.py | 1319 +
c5dec/frontend/tui/miniapps/cpssaapp.py | 1 +
.../frontend/tui/miniapps/cryptographyapp.py | 1 +
c5dec/frontend/tui/miniapps/ismsapp.py | 289 +
c5dec/frontend/tui/miniapps/miniappbase.py | 54 +
c5dec/frontend/tui/miniapps/pmapp.py | 175 +
c5dec/frontend/tui/miniapps/settingsapp.py | 0
c5dec/frontend/tui/miniapps/ssdlcapp.py | 373 +
c5dec/frontend/tui/miniapps/transformerapp.py | 298 +
c5dec/psi/__init__.py | 0
c5dec/psi/graph.py | 0
c5dec/psi/search.py | 0
c5dec/psi/security.py | 6 +
c5dec/settings.py | 77 +
docs/manual/_figures/CyFORT-logo.png | Bin 0 -> 75833 bytes
.../_figures/Python3-8-WindowsStore.png | Bin 0 -> 89844 bytes
docs/manual/_figures/c5dec-cad-pm.png | Bin 0 -> 31424 bytes
docs/manual/_figures/c5dec-cad-ssdlc.png | Bin 0 -> 31416 bytes
docs/manual/_figures/c5dec-cad-tui.png | Bin 0 -> 31360 bytes
docs/manual/_figures/c5dec-cad-vscode-gui.png | Bin 0 -> 374725 bytes
docs/manual/_figures/c5dec-cad-zettlr-gui.png | Bin 0 -> 141526 bytes
docs/manual/_figures/c5dec-cli.png | Bin 0 -> 20939 bytes
.../_figures/c5dec-isms-activity-report.png | Bin 0 -> 38553 bytes
.../c5dec-isms-document-list-assistant.png | Bin 0 -> 32511 bytes
.../_figures/c5dec-isms-tag-processor.png | Bin 0 -> 31248 bytes
.../c5dec-openproject-time-rep-assistant.png | Bin 0 -> 19814 bytes
...5dec-openproject-time-report-converter.png | Bin 0 -> 27475 bytes
.../_figures/c5dec-time-rep-consolidation.png | Bin 0 -> 36229 bytes
docs/manual/_figures/cctbrowser.png | Bin 0 -> 42566 bytes
docs/manual/_figures/cctsubmenu.png | Bin 0 -> 9359 bytes
docs/manual/_figures/checklist.png | Bin 0 -> 95033 bytes
docs/manual/_figures/d_evalitem.png | Bin 0 -> 98027 bytes
docs/manual/_figures/evalcreation.png | Bin 0 -> 88883 bytes
.../ssdlc-create-delete-artifact-document.png | Bin 0 -> 33404 bytes
.../_figures/ssdlc-create-item-link.png | Bin 0 -> 27607 bytes
.../ssdlc-manage-artifact-document.png | Bin 0 -> 25168 bytes
.../_figures/ssdlc-manage-artifact-items.png | Bin 0 -> 32893 bytes
.../ssdlc-manage-document-structure.png | Bin 0 -> 36034 bytes
.../ssdlc-transformer-convert-data.png | Bin 0 -> 24759 bytes
.../_figures/ssdlc-transformer-export.png | Bin 0 -> 21553 bytes
.../_figures/ssdlc-transformer-import.png | Bin 0 -> 26336 bytes
.../_figures/ssdlc-transformer-publish.png | Bin 0 -> 13030 bytes
.../_figures/ssdlc-view-child-items.png | Bin 0 -> 34493 bytes
docs/manual/cct.md | 153 +
docs/manual/cpssa.md | 7 +
docs/manual/cryptography.md | 11 +
docs/manual/installation.md | 110 +
docs/manual/isms.md | 40 +
docs/manual/overview.md | 33 +
docs/manual/pm.md | 52 +
docs/manual/setup.md | 22 +
docs/manual/ssdlc.md | 65 +
docs/manual/start.md | 65 +
docs/manual/transformer.md | 27 +
docs/reqs/mrs/.doorstop.yml | 29 +
docs/reqs/mrs/MRS-001.yml | 17 +
docs/reqs/mrs/MRS-002.yml | 17 +
docs/reqs/mrs/MRS-003.yml | 17 +
docs/reqs/mrs/MRS-004.yml | 17 +
docs/reqs/mrs/MRS-005.yml | 17 +
docs/reqs/mrs/MRS-006.yml | 17 +
docs/reqs/mrs/MRS-007.yml | 17 +
docs/reqs/mrs/MRS-008.yml | 17 +
docs/reqs/mrs/MRS-009.yml | 17 +
docs/reqs/mrs/MRS-010.yml | 17 +
docs/reqs/mrs/MRS-011.yml | 17 +
docs/reqs/mrs/MRS-012.yml | 17 +
docs/reqs/mrs/MRS-013.yml | 17 +
docs/reqs/mrs/MRS-014.yml | 17 +
docs/reqs/mrs/MRS-015.yml | 17 +
docs/reqs/mrs/MRS-016.yml | 17 +
docs/reqs/mrs/MRS-017.yml | 17 +
docs/reqs/mrs/MRS-018.yml | 17 +
docs/reqs/mrs/MRS-019.yml | 17 +
docs/reqs/mrs/MRS-020.yml | 17 +
docs/reqs/mrs/MRS-021.yml | 17 +
docs/reqs/mrs/MRS-022.yml | 17 +
docs/reqs/mrs/MRS-023.yml | 17 +
docs/reqs/mrs/MRS-024.yml | 17 +
docs/reqs/mrs/MRS-025.yml | 17 +
docs/reqs/mrs/MRS-026.yml | 17 +
docs/reqs/mrs/MRS-027.yml | 17 +
docs/reqs/mrs/MRS-028.yml | 17 +
docs/reqs/mrs/MRS-029.yml | 17 +
docs/reqs/mrs/MRS-030.yml | 17 +
docs/reqs/mrs/MRS-031.yml | 17 +
docs/reqs/mrs/MRS-032.yml | 17 +
docs/reqs/mrs/MRS-033.yml | 17 +
docs/reqs/mrs/MRS-034.yml | 17 +
docs/reqs/mrs/MRS-035.yml | 17 +
docs/reqs/mrs/MRS-036.yml | 17 +
docs/reqs/mrs/MRS-037.yml | 17 +
docs/reqs/mrs/MRS-038.yml | 17 +
docs/reqs/mrs/MRS-039.yml | 17 +
docs/reqs/mrs/MRS-040.yml | 17 +
docs/reqs/mrs/MRS-041.yml | 17 +
docs/reqs/mrs/MRS-042.yml | 17 +
docs/reqs/mrs/MRS-043.yml | 17 +
docs/reqs/mrs/MRS-044.yml | 17 +
docs/reqs/mrs/MRS-045.yml | 17 +
docs/reqs/mrs/MRS-046.yml | 17 +
docs/reqs/mrs/MRS-047.yml | 17 +
docs/reqs/mrs/MRS-048.yml | 17 +
docs/reqs/mrs/MRS-049.yml | 17 +
docs/reqs/mrs/MRS-050.yml | 17 +
docs/reqs/mrs/MRS-051.yml | 17 +
docs/reqs/mrs/MRS-052.yml | 17 +
docs/reqs/mrs/MRS-053.yml | 17 +
docs/reqs/mrs/MRS-054.yml | 17 +
docs/reqs/mrs/MRS-055.yml | 17 +
docs/reqs/mrs/MRS-056.yml | 18 +
docs/reqs/mrs/MRS-057.yml | 18 +
docs/reqs/mrs/MRS-058.yml | 32 +
docs/reqs/mrs/MRS-059.yml | 17 +
docs/reqs/mrs/MRS-060.yml | 17 +
docs/reqs/srs/.doorstop.yml | 46 +
docs/reqs/srs/SRS-001.yml | 51 +
docs/reqs/srs/SRS-002.yml | 44 +
docs/reqs/srs/SRS-003.yml | 49 +
docs/reqs/srs/SRS-004.yml | 56 +
docs/reqs/srs/SRS-014.yml | 41 +
docs/reqs/srs/SRS-015.yml | 38 +
docs/reqs/srs/SRS-016.yml | 49 +
docs/reqs/srs/SRS-017.yml | 37 +
docs/reqs/srs/SRS-018.yml | 40 +
docs/reqs/srs/SRS-019.yml | 38 +
docs/reqs/srs/SRS-020.yml | 37 +
docs/reqs/srs/SRS-021.yml | 39 +
docs/reqs/srs/SRS-022.yml | 36 +
docs/reqs/srs/SRS-023.yml | 39 +
docs/reqs/srs/SRS-024.yml | 39 +
docs/reqs/srs/SRS-025.yml | 39 +
docs/reqs/srs/SRS-026.yml | 38 +
docs/reqs/srs/SRS-027.yml | 45 +
docs/reqs/srs/SRS-028.yml | 36 +
docs/reqs/srs/SRS-029.yml | 36 +
docs/reqs/srs/SRS-030.yml | 35 +
docs/reqs/srs/SRS-031.yml | 38 +
docs/reqs/srs/SRS-032.yml | 40 +
docs/reqs/srs/SRS-033.yml | 34 +
docs/reqs/srs/SRS-034.yml | 33 +
docs/reqs/srs/SRS-035.yml | 47 +
docs/reqs/srs/SRS-036.yml | 44 +
docs/reqs/srs/SRS-037.yml | 57 +
docs/reqs/srs/SRS-038.yml | 36 +
docs/reqs/srs/SRS-039.yml | 38 +
docs/reqs/srs/SRS-040.yml | 40 +
docs/reqs/srs/SRS-041.yml | 33 +
docs/reqs/srs/SRS-042.yml | 34 +
docs/reqs/srs/SRS-043.yml | 36 +
docs/reqs/srs/SRS-044.yml | 48 +
docs/reqs/srs/SRS-045.yml | 41 +
docs/reqs/trp/.doorstop.yml | 29 +
docs/reqs/trp/TRP-001.yml | 21 +
docs/reqs/trp/TRP-002.yml | 21 +
docs/reqs/trp/TRP-003.yml | 18 +
docs/reqs/trp/TRP-004.yml | 16 +
docs/reqs/trp/TRP-005.yml | 16 +
docs/reqs/trp/TRP-006.yml | 16 +
docs/reqs/trp/TRP-007.yml | 17 +
docs/reqs/trp/TRP-008.yml | 16 +
docs/reqs/trp/TRP-009.yml | 16 +
docs/reqs/trp/TRP-010.yml | 18 +
docs/reqs/trp/TRP-011.yml | 18 +
docs/reqs/trp/TRP-012.yml | 17 +
docs/reqs/trp/TRP-013.yml | 17 +
docs/reqs/trp/TRP-014.yml | 16 +
docs/reqs/trp/TRP-015.yml | 16 +
docs/reqs/trp/TRP-016.yml | 17 +
docs/reqs/trp/TRP-017.yml | 16 +
docs/reqs/trp/TRP-018.yml | 16 +
docs/reqs/trp/TRP-019.yml | 16 +
docs/reqs/trp/TRP-020.yml | 16 +
docs/reqs/trp/TRP-021.yml | 21 +
docs/reqs/trp/TRP-022.yml | 17 +
docs/reqs/trp/TRP-023.yml | 17 +
docs/reqs/trp/TRP-024.yml | 17 +
docs/reqs/trp/TRP-025.yml | 18 +
docs/reqs/trp/TRP-026.yml | 16 +
docs/reqs/trp/TRP-027.yml | 16 +
docs/reqs/trp/TRP-028.yml | 16 +
docs/reqs/trp/TRP-029.yml | 16 +
docs/reqs/trp/TRP-030.yml | 16 +
docs/reqs/trp/TRP-031.yml | 17 +
docs/reqs/trp/TRP-032.yml | 16 +
docs/reqs/trp/TRP-033.yml | 16 +
docs/reqs/trp/TRP-034.yml | 16 +
docs/reqs/trp/evidence/testReport001.md | 81 +
docs/reqs/trp/evidence/trp-002-ev.png | Bin 0 -> 207709 bytes
docs/reqs/tst/.doorstop.yml | 32 +
docs/reqs/tst/TST-001.yml | 31 +
docs/reqs/tst/TST-002.yml | 29 +
docs/reqs/tst/TST-003.yml | 33 +
docs/reqs/tst/TST-004.yml | 23 +
docs/reqs/tst/TST-005.yml | 27 +
docs/reqs/tst/TST-006.yml | 27 +
docs/reqs/tst/TST-007.yml | 27 +
docs/reqs/tst/TST-008.yml | 27 +
docs/reqs/tst/TST-009.yml | 29 +
docs/reqs/tst/TST-010.yml | 40 +
docs/reqs/tst/TST-011.yml | 34 +
docs/reqs/tst/TST-012.yml | 38 +
docs/reqs/tst/TST-013.yml | 23 +
docs/reqs/tst/TST-014.yml | 23 +
docs/reqs/tst/TST-015.yml | 23 +
docs/reqs/tst/TST-016.yml | 25 +
docs/reqs/tst/TST-017.yml | 23 +
docs/reqs/tst/TST-018.yml | 23 +
docs/reqs/tst/TST-019.yml | 23 +
docs/reqs/tst/TST-020.yml | 23 +
docs/reqs/tst/TST-021.yml | 33 +
docs/reqs/tst/TST-022.yml | 23 +
docs/reqs/tst/TST-023.yml | 23 +
docs/reqs/tst/TST-024.yml | 35 +
docs/reqs/tst/TST-025.yml | 32 +
docs/reqs/tst/TST-026.yml | 33 +
docs/reqs/tst/TST-027.yml | 23 +
docs/reqs/tst/TST-028.yml | 23 +
docs/reqs/tst/TST-029.yml | 23 +
docs/reqs/tst/TST-030.yml | 38 +
docs/reqs/tst/TST-031.yml | 23 +
docs/reqs/tst/TST-032.yml | 23 +
docs/reqs/tst/TST-033.yml | 31 +
docs/reqs/tst/TST-034.yml | 23 +
docs/sdd/image/cad_context_diagram.png | Bin 0 -> 43064 bytes
docs/sdd/image/cct_class_diagram.png | Bin 0 -> 389179 bytes
docs/sdd/image/classes.png | Bin 0 -> 509000 bytes
docs/sdd/image/functional_tree.png | Bin 0 -> 233045 bytes
docs/sdd/image/packages.png | Bin 0 -> 174419 bytes
docs/sdd/image/subsystems.png | Bin 0 -> 61236 bytes
docs/sdd/image/system_architecture.png | Bin 0 -> 366177 bytes
docs/sdd/plantUML/baseclasses.puml | 370 +
docs/sdd/plantUML/cad_context_diagram.png | Bin 0 -> 43064 bytes
docs/sdd/plantUML/cad_context_diagram.puml | 41 +
docs/sdd/plantUML/cct_class_diagram.puml | 516 +
docs/sdd/plantUML/classes.puml | 280 +
docs/sdd/plantUML/functional_tree.puml | 68 +
docs/sdd/plantUML/packages.plantuml | 150 +
docs/sdd/plantUML/packages.puml | 268 +
docs/sdd/plantUML/subsystems.puml | 79 +
docs/sdd/plantUML/system_architecture.puml | 128 +
poetry.lock | 1423 +
pyproject.toml | 32 +
setup.py | 0
tests/__init__.py | 0
tests/cct_assurance_test.py | 474 +
tests/cct_basebuilder_test.py | 144 +
tests/cct_baseclass_test.py | 270 +
tests/cct_ccdocument_test.py | 105 +
tests/cct_functional_test.py | 735 +
tests/cct_index_test.py | 141 +
tests/cct_methods_tests.py | 199 +
tests/cct_operation_test.py | 117 +
tests/cct_pacakge_test.py | 279 +
tests/cct_uidmanager_test.py | 111 +
tests/content/acronyms/persons.json | 7 +
.../content/c5dec-isms-test/DocumentList.xlsx | Bin 0 -> 10896 bytes
.../subsubfolder/test-file_v1.1-dqw.txt | 0
.../Subfolder/test-file_v2.0-ega.txt | 0
.../tag-processing-test-file.docx | Bin 0 -> 12291 bytes
.../c5dec-isms-test/tag-to-link-mapping.csv | 4 +
.../c5dec-isms-test/test-file_v0.6-pfe.txt | 0
.../c5dec-isms-test/test-file_v1.1-cfg.txt | 0
.../c5dec-isms-test/test-file_v7.1-mbe.txt | 0
tests/content/openproject_params.csv | 2 +
.../content/translations/translations.de.json | 97 +
.../content/translations/translations.en.json | 3 +
.../content/translations/translations.fr.json | 54 +
tests/menu_tests.py | 56 +
.../export-29-06-2023-T-11-55-49.xls | Bin 0 -> 27648 bytes
.../source-TSH/Example-timesheet-01.xlsx | Bin 0 -> 10483 bytes
.../source-TSH/Example-timesheet-02.xlsx | Bin 0 -> 10484 bytes
1999 files changed, 321673 insertions(+), 661 deletions(-)
create mode 100644 .devcontainer/devcontainer.json
create mode 100644 .gitignore
create mode 100644 CHANGELOG.md
create mode 100644 Dockerfile
create mode 100644 README.md
create mode 100644 c5dec/__init__.py
create mode 100644 c5dec/assets/acronyms/persons.json
create mode 100644 c5dec/assets/config.json
create mode 100644 c5dec/assets/database/KnowledgeBase/0_MapofContent.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Asset.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Assumption.md
create mode 100644 c5dec/assets/database/KnowledgeBase/AttackPotential.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ComposedTOE.md
create mode 100644 c5dec/assets/database/KnowledgeBase/CompositeEvaluation.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ConformanceClaim.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ConformanceStatement.md
create mode 100644 c5dec/assets/database/KnowledgeBase/DirectRationale.md
create mode 100644 c5dec/assets/database/KnowledgeBase/DomainSeparation.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EUCC.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EvaluationAssuranceLevel.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EvaluationEvidence.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EvaluationEvidenceIndex.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EvaluationMethods.md
create mode 100644 c5dec/assets/database/KnowledgeBase/EvaluationTechnicalReport.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Exactconformance-FAQ.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ExtendedComponentDefinition.md
create mode 100644 c5dec/assets/database/KnowledgeBase/MultiAssuranceEvaluation.md
create mode 100644 c5dec/assets/database/KnowledgeBase/NonBypassability.md
create mode 100644 c5dec/assets/database/KnowledgeBase/NonTSFPart.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ObservationReport.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Operation-Assignment.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Operation-Iteration.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Operation-Refinement.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Operation-Selection.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Operations.md
create mode 100644 c5dec/assets/database/KnowledgeBase/OrganizationalSecurityPolicy.md
create mode 100644 c5dec/assets/database/KnowledgeBase/PPConfiguration.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ProtectionProfile.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Rationale.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityAssuranceRequirement.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityComponent.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityFunctionalRequirement.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityObjective.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityProblemdefinition.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SecurityTarget.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SelfProtection.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SingleAssuranceEvaluation.md
create mode 100644 c5dec/assets/database/KnowledgeBase/SubTOESecurityFunctionality.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOEBoundary.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOEDescription.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOEOperationalEnvironment.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOEOverview.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOEReference.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOESecurityFunctionality.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TOESummarySpecification.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TSFInterface.md
create mode 100644 c5dec/assets/database/KnowledgeBase/TargetofEvaluation.md
create mode 100644 c5dec/assets/database/KnowledgeBase/Threat.md
create mode 100644 c5dec/assets/database/KnowledgeBase/ThreatModeling-TR15446.md
create mode 100644 c5dec/assets/database/KnowledgeBase/_figures/AssetDef.png
create mode 100644 c5dec/assets/database/KnowledgeBase/_figures/MappingCCtoCEM.png
create mode 100644 c5dec/assets/database/SecurityControls/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/CC-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ACC-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/component/ACOM-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-107.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-108.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-109.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-110.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-111.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-112.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-113.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-114.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-115.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-116.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-117.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-118.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-119.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-120.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-121.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-122.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-123.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-124.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-125.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-126.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-127.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-128.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-129.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-130.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-131.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-132.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-133.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-134.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-135.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-136.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-137.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-138.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-139.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-140.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-141.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-142.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-143.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-144.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-145.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-146.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-147.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-148.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-149.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-150.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-151.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-152.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-153.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-154.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-155.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-156.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-157.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-158.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-159.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-160.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-161.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-162.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-163.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-164.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-165.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-166.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-167.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-168.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-169.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-170.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-171.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-172.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-173.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-174.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-175.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-176.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-177.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-178.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-179.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-180.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-181.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-182.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-183.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-184.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-185.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-186.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-187.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-188.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-189.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-190.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-191.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-192.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-193.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-194.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-195.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-196.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-197.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-198.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-199.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-200.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-201.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-202.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-203.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-204.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-205.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-206.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-207.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-208.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-209.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-210.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-211.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-212.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-213.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-214.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-215.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-216.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-217.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-218.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-219.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-220.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-221.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-222.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-223.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-224.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-225.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-226.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-227.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-228.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-229.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-230.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-231.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-232.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-233.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-234.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-235.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-236.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-237.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-238.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-239.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-240.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-241.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-242.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-243.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-244.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-245.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-246.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-247.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-248.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-249.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-250.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-251.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-252.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-253.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-254.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-255.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-256.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-257.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-258.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-259.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-260.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-261.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-262.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-263.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-264.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-265.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-266.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-267.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-268.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-269.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-270.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-271.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-272.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-273.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-274.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-275.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-276.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-277.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-278.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-279.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-280.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-281.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-282.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-283.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-284.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-285.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-286.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-287.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-288.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-289.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-290.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-291.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-292.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-293.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-294.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-295.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-296.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-297.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-298.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-299.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-300.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-301.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-302.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-303.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-304.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-305.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-306.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-307.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-308.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-309.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-310.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-311.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-312.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-313.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-314.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-315.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-316.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-317.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-318.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-319.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-320.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-321.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-322.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-323.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-324.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-325.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-326.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-327.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-328.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-329.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-330.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-331.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-332.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-333.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-334.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-335.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-336.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-337.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-338.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-339.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-340.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-341.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-342.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-343.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-344.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-345.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-346.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-347.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-348.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-349.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-350.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-351.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-352.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-353.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-354.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-355.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-356.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-357.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-358.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-359.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-360.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-361.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-362.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-363.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-364.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-365.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-366.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-367.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-368.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-369.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-370.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-371.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-372.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-373.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-374.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-375.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-376.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-377.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-378.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-379.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-380.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-381.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-382.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-383.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-384.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-385.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-386.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-387.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-388.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-389.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-390.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-391.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-392.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-393.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-394.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-395.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-396.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-397.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-398.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-399.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-400.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-401.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-402.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-403.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-404.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-405.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-406.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-407.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-408.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-409.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-410.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-411.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-412.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-413.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-414.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-415.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-416.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-417.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-418.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-419.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-420.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-421.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-422.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-423.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-424.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-425.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-426.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-427.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-428.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-429.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-430.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-431.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-432.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-433.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-434.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-435.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-436.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-437.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-438.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-439.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-440.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-441.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-442.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-443.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-444.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-445.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-446.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-447.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-448.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-449.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-450.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-451.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-452.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-453.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-454.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-455.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-456.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-457.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-458.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-459.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-460.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-461.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-462.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-463.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-464.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-465.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-466.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-467.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-468.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-469.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-470.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-471.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-472.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-473.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-474.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-475.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-476.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-477.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-478.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-479.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-480.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-481.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-482.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-483.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-484.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-485.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-486.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-487.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-488.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-489.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-490.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-491.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-492.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-493.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-494.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-495.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-496.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-497.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-498.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-499.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-500.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-501.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-502.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-503.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-504.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-505.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-506.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-507.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-508.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-509.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-510.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-511.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-512.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-513.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-514.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-515.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-516.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-517.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-518.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-519.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-520.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-521.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-522.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/creq/CREQ-523.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-107.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-108.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-109.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-110.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-111.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-112.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-113.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-114.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-115.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-116.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-117.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-118.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-119.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-120.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-121.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-122.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-123.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-124.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-125.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-126.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-127.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-128.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-129.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-130.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-131.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-132.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-133.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-134.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-135.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-136.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-137.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-138.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-139.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-140.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-141.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-142.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-143.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-144.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-145.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-146.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-147.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-148.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-149.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-150.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-151.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-152.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-153.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-154.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-155.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-156.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-157.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-158.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-159.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-160.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-161.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-162.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-163.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-164.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-165.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-166.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-167.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-168.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-169.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-170.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-171.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-172.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-173.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-174.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-175.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-176.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-177.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-178.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-179.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-180.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-181.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-182.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-183.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-184.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-186.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-187.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-188.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-189.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-190.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-191.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-192.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-193.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-194.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-195.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-196.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-197.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-198.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-199.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-200.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-201.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-202.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-203.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-204.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-205.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-206.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-207.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-208.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-209.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-210.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-211.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-212.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-213.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-214.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/dreq/DREQ-215.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-107.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-108.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-109.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-110.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-111.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-112.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-113.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-114.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-115.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-116.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-117.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-118.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-119.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-120.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-121.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-122.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-123.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-124.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-125.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-126.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-127.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-128.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-129.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-130.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-131.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-132.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-133.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-134.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-135.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-136.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-137.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-138.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-139.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-140.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-141.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-142.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-143.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-144.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-145.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-146.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-147.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-148.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-149.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-150.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-151.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-152.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-153.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-154.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-155.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-156.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-157.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-158.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-159.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-160.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-161.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-162.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-163.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-164.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-165.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-166.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-167.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-168.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-169.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-170.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-171.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-172.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-173.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-174.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-175.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-176.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-177.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-178.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-179.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-180.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-181.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-182.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-183.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-184.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-185.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-186.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-187.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-188.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-189.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-190.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/ereq/EREQ-191.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SAR/family/AFML-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/CCC-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-107.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-108.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-109.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-110.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-111.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-112.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-113.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-114.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-115.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-116.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-117.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-118.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-119.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-120.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-121.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-122.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-123.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-124.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-125.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-126.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-127.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-128.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-129.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-130.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-131.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-132.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-133.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-134.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-135.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-136.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-137.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-138.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-139.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-140.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-141.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-142.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-143.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-144.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-145.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-146.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-147.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-148.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-149.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-150.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-151.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-152.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-153.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-154.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-155.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/component/COM-156.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/family/FML-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/.doorstop.yml
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-001.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-002.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-003.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-004.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-005.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-006.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-007.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-008.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-009.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-010.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-011.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-012.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-013.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-014.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-015.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-016.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-017.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-018.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-019.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-020.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-021.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-022.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-023.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-024.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-025.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-026.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-027.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-028.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-029.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-030.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-031.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-032.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-033.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-034.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-035.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-036.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-037.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-038.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-039.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-040.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-041.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-042.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-043.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-044.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-045.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-046.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-047.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-048.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-049.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-050.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-051.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-052.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-053.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-054.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-055.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-056.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-057.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-058.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-059.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-060.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-061.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-062.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-063.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-064.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-065.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-066.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-067.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-068.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-069.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-070.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-071.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-072.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-073.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-074.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-075.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-076.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-077.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-078.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-079.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-080.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-081.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-082.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-083.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-084.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-085.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-086.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-087.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-088.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-089.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-090.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-091.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-092.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-093.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-094.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-095.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-096.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-097.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-098.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-099.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-100.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-101.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-102.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-103.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-104.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-105.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-106.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-107.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-108.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-109.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-110.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-111.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-112.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-113.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-114.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-115.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-116.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-117.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-118.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-119.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-120.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-121.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-122.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-123.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-124.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-125.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-126.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-127.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-128.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-129.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-130.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-131.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-132.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-133.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-134.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-135.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-136.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-137.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-138.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-139.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-140.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-141.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-142.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-143.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-144.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-145.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-146.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-147.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-148.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-149.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-150.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-151.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-152.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-153.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-154.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-155.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-156.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-157.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-158.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-159.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-160.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-161.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-162.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-163.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-164.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-165.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-166.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-167.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-168.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-169.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-170.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-171.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-172.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-173.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-174.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-175.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-176.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-177.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-178.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-179.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-180.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-181.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-182.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-183.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-184.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-185.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-186.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-187.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-188.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-189.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-190.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-191.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-192.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-193.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-194.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-195.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-196.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-197.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-198.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-199.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-200.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-201.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-202.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-203.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-204.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-205.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-206.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-207.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-208.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-209.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-210.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-211.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-212.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-213.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-214.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-215.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-216.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-217.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-218.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-219.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-220.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-221.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-222.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-223.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-224.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-225.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-226.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-227.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-228.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-229.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-230.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-231.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-232.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-233.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-234.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-235.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-236.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-237.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-238.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-239.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-240.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-241.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-242.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-243.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-244.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-245.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-246.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-247.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-248.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-249.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-250.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-251.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-252.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-253.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-254.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-255.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-256.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-257.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-258.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-259.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-260.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-261.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-262.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-263.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-264.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-265.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-266.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-267.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-268.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-269.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-270.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-271.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-272.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-273.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-274.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-275.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-276.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-277.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-278.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-279.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-280.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-281.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-282.md
create mode 100644 c5dec/assets/database/SecurityControls/CC2022/SFR/req/REQ-283.md
create mode 100644 c5dec/assets/database/SecurityControls/cc3R1.xml
create mode 100644 c5dec/assets/database/SecurityControls/cc3R2.xml
create mode 100644 c5dec/assets/database/SecurityControls/cc3R3.xml
create mode 100644 c5dec/assets/database/SecurityControls/cc3R4.xml
create mode 100644 c5dec/assets/database/SecurityControls/cc3R5.dtd
create mode 100644 c5dec/assets/database/SecurityControls/cc3R5.xml
create mode 100644 c5dec/assets/scripts/doorstop_mock.sh
create mode 100644 c5dec/assets/translations/translations.de.json
create mode 100644 c5dec/assets/translations/translations.en.json
create mode 100644 c5dec/assets/translations/translations.fr.json
create mode 100644 c5dec/assets/tshparams/openproject_params.csv
create mode 100644 c5dec/assets/tshparams/tshformat.json
create mode 100644 c5dec/common.py
create mode 100644 c5dec/core/__init__.py
create mode 100644 c5dec/core/cct.py
create mode 100644 c5dec/core/cpssa.py
create mode 100644 c5dec/core/cryptography.py
create mode 100644 c5dec/core/isms.py
create mode 100644 c5dec/core/pm.py
create mode 100644 c5dec/core/settings.py
create mode 100644 c5dec/core/ssdlc.py
create mode 100644 c5dec/core/transformer.py
create mode 100644 c5dec/frontend/__init__.py
create mode 100644 c5dec/frontend/cli/__init__.py
create mode 100644 c5dec/frontend/cli/commands.py
create mode 100644 c5dec/frontend/cli/main.py
create mode 100644 c5dec/frontend/cli/utils.py
create mode 100644 c5dec/frontend/tui/__init__.py
create mode 100644 c5dec/frontend/tui/application.py
create mode 100644 c5dec/frontend/tui/foundation/__init__.py
create mode 100644 c5dec/frontend/tui/foundation/builder.py
create mode 100644 c5dec/frontend/tui/foundation/menu.py
create mode 100644 c5dec/frontend/tui/main.py
create mode 100644 c5dec/frontend/tui/miniapps/cctapp.py
create mode 100644 c5dec/frontend/tui/miniapps/cpssaapp.py
create mode 100644 c5dec/frontend/tui/miniapps/cryptographyapp.py
create mode 100644 c5dec/frontend/tui/miniapps/ismsapp.py
create mode 100644 c5dec/frontend/tui/miniapps/miniappbase.py
create mode 100644 c5dec/frontend/tui/miniapps/pmapp.py
create mode 100644 c5dec/frontend/tui/miniapps/settingsapp.py
create mode 100644 c5dec/frontend/tui/miniapps/ssdlcapp.py
create mode 100644 c5dec/frontend/tui/miniapps/transformerapp.py
create mode 100644 c5dec/psi/__init__.py
create mode 100644 c5dec/psi/graph.py
create mode 100644 c5dec/psi/search.py
create mode 100644 c5dec/psi/security.py
create mode 100644 c5dec/settings.py
create mode 100644 docs/manual/_figures/CyFORT-logo.png
create mode 100644 docs/manual/_figures/Python3-8-WindowsStore.png
create mode 100644 docs/manual/_figures/c5dec-cad-pm.png
create mode 100644 docs/manual/_figures/c5dec-cad-ssdlc.png
create mode 100644 docs/manual/_figures/c5dec-cad-tui.png
create mode 100644 docs/manual/_figures/c5dec-cad-vscode-gui.png
create mode 100644 docs/manual/_figures/c5dec-cad-zettlr-gui.png
create mode 100644 docs/manual/_figures/c5dec-cli.png
create mode 100644 docs/manual/_figures/c5dec-isms-activity-report.png
create mode 100644 docs/manual/_figures/c5dec-isms-document-list-assistant.png
create mode 100644 docs/manual/_figures/c5dec-isms-tag-processor.png
create mode 100644 docs/manual/_figures/c5dec-openproject-time-rep-assistant.png
create mode 100644 docs/manual/_figures/c5dec-openproject-time-report-converter.png
create mode 100644 docs/manual/_figures/c5dec-time-rep-consolidation.png
create mode 100644 docs/manual/_figures/cctbrowser.png
create mode 100644 docs/manual/_figures/cctsubmenu.png
create mode 100644 docs/manual/_figures/checklist.png
create mode 100644 docs/manual/_figures/d_evalitem.png
create mode 100644 docs/manual/_figures/evalcreation.png
create mode 100644 docs/manual/_figures/ssdlc-create-delete-artifact-document.png
create mode 100644 docs/manual/_figures/ssdlc-create-item-link.png
create mode 100644 docs/manual/_figures/ssdlc-manage-artifact-document.png
create mode 100644 docs/manual/_figures/ssdlc-manage-artifact-items.png
create mode 100644 docs/manual/_figures/ssdlc-manage-document-structure.png
create mode 100644 docs/manual/_figures/ssdlc-transformer-convert-data.png
create mode 100644 docs/manual/_figures/ssdlc-transformer-export.png
create mode 100644 docs/manual/_figures/ssdlc-transformer-import.png
create mode 100644 docs/manual/_figures/ssdlc-transformer-publish.png
create mode 100644 docs/manual/_figures/ssdlc-view-child-items.png
create mode 100644 docs/manual/cct.md
create mode 100644 docs/manual/cpssa.md
create mode 100644 docs/manual/cryptography.md
create mode 100644 docs/manual/installation.md
create mode 100644 docs/manual/isms.md
create mode 100644 docs/manual/overview.md
create mode 100644 docs/manual/pm.md
create mode 100644 docs/manual/setup.md
create mode 100644 docs/manual/ssdlc.md
create mode 100644 docs/manual/start.md
create mode 100644 docs/manual/transformer.md
create mode 100644 docs/reqs/mrs/.doorstop.yml
create mode 100644 docs/reqs/mrs/MRS-001.yml
create mode 100644 docs/reqs/mrs/MRS-002.yml
create mode 100644 docs/reqs/mrs/MRS-003.yml
create mode 100644 docs/reqs/mrs/MRS-004.yml
create mode 100644 docs/reqs/mrs/MRS-005.yml
create mode 100644 docs/reqs/mrs/MRS-006.yml
create mode 100644 docs/reqs/mrs/MRS-007.yml
create mode 100644 docs/reqs/mrs/MRS-008.yml
create mode 100644 docs/reqs/mrs/MRS-009.yml
create mode 100644 docs/reqs/mrs/MRS-010.yml
create mode 100644 docs/reqs/mrs/MRS-011.yml
create mode 100644 docs/reqs/mrs/MRS-012.yml
create mode 100644 docs/reqs/mrs/MRS-013.yml
create mode 100644 docs/reqs/mrs/MRS-014.yml
create mode 100644 docs/reqs/mrs/MRS-015.yml
create mode 100644 docs/reqs/mrs/MRS-016.yml
create mode 100644 docs/reqs/mrs/MRS-017.yml
create mode 100644 docs/reqs/mrs/MRS-018.yml
create mode 100644 docs/reqs/mrs/MRS-019.yml
create mode 100644 docs/reqs/mrs/MRS-020.yml
create mode 100644 docs/reqs/mrs/MRS-021.yml
create mode 100644 docs/reqs/mrs/MRS-022.yml
create mode 100644 docs/reqs/mrs/MRS-023.yml
create mode 100644 docs/reqs/mrs/MRS-024.yml
create mode 100644 docs/reqs/mrs/MRS-025.yml
create mode 100644 docs/reqs/mrs/MRS-026.yml
create mode 100644 docs/reqs/mrs/MRS-027.yml
create mode 100644 docs/reqs/mrs/MRS-028.yml
create mode 100644 docs/reqs/mrs/MRS-029.yml
create mode 100644 docs/reqs/mrs/MRS-030.yml
create mode 100644 docs/reqs/mrs/MRS-031.yml
create mode 100644 docs/reqs/mrs/MRS-032.yml
create mode 100644 docs/reqs/mrs/MRS-033.yml
create mode 100644 docs/reqs/mrs/MRS-034.yml
create mode 100644 docs/reqs/mrs/MRS-035.yml
create mode 100644 docs/reqs/mrs/MRS-036.yml
create mode 100644 docs/reqs/mrs/MRS-037.yml
create mode 100644 docs/reqs/mrs/MRS-038.yml
create mode 100644 docs/reqs/mrs/MRS-039.yml
create mode 100644 docs/reqs/mrs/MRS-040.yml
create mode 100644 docs/reqs/mrs/MRS-041.yml
create mode 100644 docs/reqs/mrs/MRS-042.yml
create mode 100644 docs/reqs/mrs/MRS-043.yml
create mode 100644 docs/reqs/mrs/MRS-044.yml
create mode 100644 docs/reqs/mrs/MRS-045.yml
create mode 100644 docs/reqs/mrs/MRS-046.yml
create mode 100644 docs/reqs/mrs/MRS-047.yml
create mode 100644 docs/reqs/mrs/MRS-048.yml
create mode 100644 docs/reqs/mrs/MRS-049.yml
create mode 100644 docs/reqs/mrs/MRS-050.yml
create mode 100644 docs/reqs/mrs/MRS-051.yml
create mode 100644 docs/reqs/mrs/MRS-052.yml
create mode 100644 docs/reqs/mrs/MRS-053.yml
create mode 100644 docs/reqs/mrs/MRS-054.yml
create mode 100644 docs/reqs/mrs/MRS-055.yml
create mode 100644 docs/reqs/mrs/MRS-056.yml
create mode 100644 docs/reqs/mrs/MRS-057.yml
create mode 100644 docs/reqs/mrs/MRS-058.yml
create mode 100644 docs/reqs/mrs/MRS-059.yml
create mode 100644 docs/reqs/mrs/MRS-060.yml
create mode 100644 docs/reqs/srs/.doorstop.yml
create mode 100644 docs/reqs/srs/SRS-001.yml
create mode 100644 docs/reqs/srs/SRS-002.yml
create mode 100644 docs/reqs/srs/SRS-003.yml
create mode 100644 docs/reqs/srs/SRS-004.yml
create mode 100644 docs/reqs/srs/SRS-014.yml
create mode 100644 docs/reqs/srs/SRS-015.yml
create mode 100644 docs/reqs/srs/SRS-016.yml
create mode 100644 docs/reqs/srs/SRS-017.yml
create mode 100644 docs/reqs/srs/SRS-018.yml
create mode 100644 docs/reqs/srs/SRS-019.yml
create mode 100644 docs/reqs/srs/SRS-020.yml
create mode 100644 docs/reqs/srs/SRS-021.yml
create mode 100644 docs/reqs/srs/SRS-022.yml
create mode 100644 docs/reqs/srs/SRS-023.yml
create mode 100644 docs/reqs/srs/SRS-024.yml
create mode 100644 docs/reqs/srs/SRS-025.yml
create mode 100644 docs/reqs/srs/SRS-026.yml
create mode 100644 docs/reqs/srs/SRS-027.yml
create mode 100644 docs/reqs/srs/SRS-028.yml
create mode 100644 docs/reqs/srs/SRS-029.yml
create mode 100644 docs/reqs/srs/SRS-030.yml
create mode 100644 docs/reqs/srs/SRS-031.yml
create mode 100644 docs/reqs/srs/SRS-032.yml
create mode 100644 docs/reqs/srs/SRS-033.yml
create mode 100644 docs/reqs/srs/SRS-034.yml
create mode 100644 docs/reqs/srs/SRS-035.yml
create mode 100644 docs/reqs/srs/SRS-036.yml
create mode 100644 docs/reqs/srs/SRS-037.yml
create mode 100644 docs/reqs/srs/SRS-038.yml
create mode 100644 docs/reqs/srs/SRS-039.yml
create mode 100644 docs/reqs/srs/SRS-040.yml
create mode 100644 docs/reqs/srs/SRS-041.yml
create mode 100644 docs/reqs/srs/SRS-042.yml
create mode 100644 docs/reqs/srs/SRS-043.yml
create mode 100644 docs/reqs/srs/SRS-044.yml
create mode 100644 docs/reqs/srs/SRS-045.yml
create mode 100644 docs/reqs/trp/.doorstop.yml
create mode 100644 docs/reqs/trp/TRP-001.yml
create mode 100644 docs/reqs/trp/TRP-002.yml
create mode 100644 docs/reqs/trp/TRP-003.yml
create mode 100644 docs/reqs/trp/TRP-004.yml
create mode 100644 docs/reqs/trp/TRP-005.yml
create mode 100644 docs/reqs/trp/TRP-006.yml
create mode 100644 docs/reqs/trp/TRP-007.yml
create mode 100644 docs/reqs/trp/TRP-008.yml
create mode 100644 docs/reqs/trp/TRP-009.yml
create mode 100644 docs/reqs/trp/TRP-010.yml
create mode 100644 docs/reqs/trp/TRP-011.yml
create mode 100644 docs/reqs/trp/TRP-012.yml
create mode 100644 docs/reqs/trp/TRP-013.yml
create mode 100644 docs/reqs/trp/TRP-014.yml
create mode 100644 docs/reqs/trp/TRP-015.yml
create mode 100644 docs/reqs/trp/TRP-016.yml
create mode 100644 docs/reqs/trp/TRP-017.yml
create mode 100644 docs/reqs/trp/TRP-018.yml
create mode 100644 docs/reqs/trp/TRP-019.yml
create mode 100644 docs/reqs/trp/TRP-020.yml
create mode 100644 docs/reqs/trp/TRP-021.yml
create mode 100644 docs/reqs/trp/TRP-022.yml
create mode 100644 docs/reqs/trp/TRP-023.yml
create mode 100644 docs/reqs/trp/TRP-024.yml
create mode 100644 docs/reqs/trp/TRP-025.yml
create mode 100644 docs/reqs/trp/TRP-026.yml
create mode 100644 docs/reqs/trp/TRP-027.yml
create mode 100644 docs/reqs/trp/TRP-028.yml
create mode 100644 docs/reqs/trp/TRP-029.yml
create mode 100644 docs/reqs/trp/TRP-030.yml
create mode 100644 docs/reqs/trp/TRP-031.yml
create mode 100644 docs/reqs/trp/TRP-032.yml
create mode 100644 docs/reqs/trp/TRP-033.yml
create mode 100644 docs/reqs/trp/TRP-034.yml
create mode 100644 docs/reqs/trp/evidence/testReport001.md
create mode 100644 docs/reqs/trp/evidence/trp-002-ev.png
create mode 100644 docs/reqs/tst/.doorstop.yml
create mode 100644 docs/reqs/tst/TST-001.yml
create mode 100644 docs/reqs/tst/TST-002.yml
create mode 100644 docs/reqs/tst/TST-003.yml
create mode 100644 docs/reqs/tst/TST-004.yml
create mode 100644 docs/reqs/tst/TST-005.yml
create mode 100644 docs/reqs/tst/TST-006.yml
create mode 100644 docs/reqs/tst/TST-007.yml
create mode 100644 docs/reqs/tst/TST-008.yml
create mode 100644 docs/reqs/tst/TST-009.yml
create mode 100644 docs/reqs/tst/TST-010.yml
create mode 100644 docs/reqs/tst/TST-011.yml
create mode 100644 docs/reqs/tst/TST-012.yml
create mode 100644 docs/reqs/tst/TST-013.yml
create mode 100644 docs/reqs/tst/TST-014.yml
create mode 100644 docs/reqs/tst/TST-015.yml
create mode 100644 docs/reqs/tst/TST-016.yml
create mode 100644 docs/reqs/tst/TST-017.yml
create mode 100644 docs/reqs/tst/TST-018.yml
create mode 100644 docs/reqs/tst/TST-019.yml
create mode 100644 docs/reqs/tst/TST-020.yml
create mode 100644 docs/reqs/tst/TST-021.yml
create mode 100644 docs/reqs/tst/TST-022.yml
create mode 100644 docs/reqs/tst/TST-023.yml
create mode 100644 docs/reqs/tst/TST-024.yml
create mode 100644 docs/reqs/tst/TST-025.yml
create mode 100644 docs/reqs/tst/TST-026.yml
create mode 100644 docs/reqs/tst/TST-027.yml
create mode 100644 docs/reqs/tst/TST-028.yml
create mode 100644 docs/reqs/tst/TST-029.yml
create mode 100644 docs/reqs/tst/TST-030.yml
create mode 100644 docs/reqs/tst/TST-031.yml
create mode 100644 docs/reqs/tst/TST-032.yml
create mode 100644 docs/reqs/tst/TST-033.yml
create mode 100644 docs/reqs/tst/TST-034.yml
create mode 100644 docs/sdd/image/cad_context_diagram.png
create mode 100644 docs/sdd/image/cct_class_diagram.png
create mode 100644 docs/sdd/image/classes.png
create mode 100644 docs/sdd/image/functional_tree.png
create mode 100644 docs/sdd/image/packages.png
create mode 100644 docs/sdd/image/subsystems.png
create mode 100644 docs/sdd/image/system_architecture.png
create mode 100644 docs/sdd/plantUML/baseclasses.puml
create mode 100644 docs/sdd/plantUML/cad_context_diagram.png
create mode 100644 docs/sdd/plantUML/cad_context_diagram.puml
create mode 100644 docs/sdd/plantUML/cct_class_diagram.puml
create mode 100644 docs/sdd/plantUML/classes.puml
create mode 100644 docs/sdd/plantUML/functional_tree.puml
create mode 100644 docs/sdd/plantUML/packages.plantuml
create mode 100644 docs/sdd/plantUML/packages.puml
create mode 100644 docs/sdd/plantUML/subsystems.puml
create mode 100644 docs/sdd/plantUML/system_architecture.puml
create mode 100644 poetry.lock
create mode 100644 pyproject.toml
create mode 100644 setup.py
create mode 100644 tests/__init__.py
create mode 100644 tests/cct_assurance_test.py
create mode 100644 tests/cct_basebuilder_test.py
create mode 100644 tests/cct_baseclass_test.py
create mode 100644 tests/cct_ccdocument_test.py
create mode 100644 tests/cct_functional_test.py
create mode 100644 tests/cct_index_test.py
create mode 100644 tests/cct_methods_tests.py
create mode 100644 tests/cct_operation_test.py
create mode 100644 tests/cct_pacakge_test.py
create mode 100644 tests/cct_uidmanager_test.py
create mode 100644 tests/content/acronyms/persons.json
create mode 100644 tests/content/c5dec-isms-test/DocumentList.xlsx
create mode 100644 tests/content/c5dec-isms-test/Subfolder/subsubfolder/test-file_v1.1-dqw.txt
create mode 100644 tests/content/c5dec-isms-test/Subfolder/test-file_v2.0-ega.txt
create mode 100644 tests/content/c5dec-isms-test/tag-processing-test-file.docx
create mode 100644 tests/content/c5dec-isms-test/tag-to-link-mapping.csv
create mode 100644 tests/content/c5dec-isms-test/test-file_v0.6-pfe.txt
create mode 100644 tests/content/c5dec-isms-test/test-file_v1.1-cfg.txt
create mode 100644 tests/content/c5dec-isms-test/test-file_v7.1-mbe.txt
create mode 100644 tests/content/openproject_params.csv
create mode 100644 tests/content/translations/translations.de.json
create mode 100644 tests/content/translations/translations.en.json
create mode 100644 tests/content/translations/translations.fr.json
create mode 100644 tests/menu_tests.py
create mode 100644 tests/op_test_files/export-29-06-2023-T-11-55-49.xls
create mode 100644 tests/op_test_files/source-TSH/Example-timesheet-01.xlsx
create mode 100644 tests/op_test_files/source-TSH/Example-timesheet-02.xlsx
diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
new file mode 100644
index 0000000..8eb42a0
--- /dev/null
+++ b/.devcontainer/devcontainer.json
@@ -0,0 +1,43 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/docker-existing-dockerfile
+{
+ "name": "Existing Dockerfile",
+ "build": {
+ // Sets the run context to one level up instead of the .devcontainer folder.
+ "context": "..",
+ // Update the 'dockerFile' property if you aren't using the standard 'Dockerfile' filename.
+ "dockerfile": "../Dockerfile"
+ },
+
+ // Features to add to the dev container. More info: https://containers.dev/features.
+ // "features": {},
+
+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
+ // "forwardPorts": [],
+
+ // Uncomment the next line to run commands after the container is created.
+ // "postCreateCommand": "cat /etc/os-release",
+
+ // Configure tool-specific properties.
+ "customizations": {
+ "vscode": {
+ "extensions": [
+ "ms-python.python"
+ ],
+ "settings": {
+ "python.testing.pytestArgs": [
+ "."
+ ],
+ "python.testing.unittestEnabled": false,
+ "python.testing.pytestEnabled": true,
+ "python.formatting.provider": "black"
+ }
+ }
+ },
+
+ "workspaceMount": "source=${localWorkspaceFolder},target=/home/alab/c5dec,type=bind",
+ "workspaceFolder": "/home/alab/c5dec"
+
+ // Uncomment to connect as an existing user other than the container default. More info: https://aka.ms/dev-containers-non-root.
+ // "remoteUser": "devcontainer"
+}
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..f24bf05
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,172 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+publish/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+# Usually these files are written by a python script from a template
+# before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+# For a library or package, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+# However, in case of collaboration, if having platform-specific dependencies or dependencies
+# having no cross-platform support, pipenv may install dependencies that don't work, or not
+# install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+# This is especially recommended for binary packages to ensure reproducibility, and is more
+# commonly ignored for libraries.
+# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+# in version control.
+# https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+# and can be added to the global gitignore or merged into this file. For a more nuclear
+# option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# c5dec specific elements
+# Note: adding this folder causes warnings to doorstop.
+# It was left commented on purpose to prevent future inclusion.
+# evaluation/
+
+# macOS files
+.DS_Store
+
+# WSL stuff
+*:Zone.Identifier
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000..e350f7c
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,3 @@
+# 0.1 (2023-12-01)
+
+- Initial release of C5-DEC CAD
\ No newline at end of file
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 0000000..9b40783
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,51 @@
+FROM python:3.8
+
+ARG MY_ENV
+
+ENV MY_ENV=${MY_ENV} \
+ PYTHONFAULTHANDLER=1 \
+ PYTHONUNBUFFERED=1 \
+ PYTHONHASHSEED=random \
+ PIP_NO_CACHE_DIR=off \
+ PIP_DISABLE_PIP_VERSION_CHECK=on \
+ PIP_DEFAULT_TIMEOUT=100 \
+ POETRY_VERSION=1.5.0
+
+ENV user=alab
+ENV c5folder=c5dec
+
+# Update and install depencencies
+RUN apt update --fix-missing
+RUN apt-get install -y git python3-pip graphviz
+
+# Create a non-root user
+RUN useradd -ms /bin/bash ${user} && echo '${user} ALL=(ALL) NOPASSWD:ALL' >>/etc/sudoers
+
+# Add location where pip is installed to the PATH variable
+ENV PATH="/home/${user}/.local/bin:${PATH}"
+
+# Copy the files and install the python environment as user alab
+USER ${user}
+# RUN pip3 install pipenv
+RUN pip3 install "poetry==$POETRY_VERSION"
+
+WORKDIR /home/${user}/${c5dec}
+COPY poetry.lock pyproject.toml /home/${user}/${c5dec}/
+
+# Project initialization
+RUN poetry install
+
+# Creating folders, and files for a project
+COPY . /home/${user}/${c5dec}
+
+# Install python virtual environment for the project
+WORKDIR /home/${user}/${c5dec}
+# RUN pipenv install
+
+# Clean up unnecessary packages
+USER root
+RUN apt-get autoremove -y && apt-get autoclean -y
+
+# Set the container starting point, running the project as the user
+USER ${user}
+CMD ["poetry", "shell"]
\ No newline at end of file
diff --git a/LICENSE b/LICENSE
index 0ad25db..d773636 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,661 +1,186 @@
- GNU AFFERO GENERAL PUBLIC LICENSE
- Version 3, 19 November 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc.
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
- The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
- Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
- A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate. Many developers of free software are heartened and
-encouraged by the resulting cooperation. However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
- The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community. It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server. Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
- An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals. This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- TERMS AND CONDITIONS
-
- 0. Definitions.
-
- "This License" refers to version 3 of the GNU Affero General Public License.
-
- "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
- "The Program" refers to any copyrightable work licensed under this
-License. Each licensee is addressed as "you". "Licensees" and
-"recipients" may be individuals or organizations.
-
- To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy. The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
- A "covered work" means either the unmodified Program or a work based
-on the Program.
-
- To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
- To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
- An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
- 1. Source Code.
-
- The "source code" for a work means the preferred form of the work
-for making modifications to it. "Object code" means any non-source
-form of a work.
-
- A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
- The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
- The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
- The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
- The Corresponding Source for a work in source code form is that
-same work.
-
- 2. Basic Permissions.
-
- All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
- You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force. You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright. Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
- Conveying under any other circumstances is permitted solely under
-the conditions stated below. Sublicensing is not allowed; section 10
-makes it unnecessary.
-
- 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
- No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
- When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
- 4. Conveying Verbatim Copies.
-
- You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
- You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
- 5. Conveying Modified Source Versions.
-
- You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
- a) The work must carry prominent notices stating that you modified
- it, and giving a relevant date.
-
- b) The work must carry prominent notices stating that it is
- released under this License and any conditions added under section
- 7. This requirement modifies the requirement in section 4 to
- "keep intact all notices".
-
- c) You must license the entire work, as a whole, under this
- License to anyone who comes into possession of a copy. This
- License will therefore apply, along with any applicable section 7
- additional terms, to the whole of the work, and all its parts,
- regardless of how they are packaged. This License gives no
- permission to license the work in any other way, but it does not
- invalidate such permission if you have separately received it.
-
- d) If the work has interactive user interfaces, each must display
- Appropriate Legal Notices; however, if the Program has interactive
- interfaces that do not display Appropriate Legal Notices, your
- work need not make them do so.
-
- A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
- 6. Conveying Non-Source Forms.
-
- You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
- a) Convey the object code in, or embodied in, a physical product
- (including a physical distribution medium), accompanied by the
- Corresponding Source fixed on a durable physical medium
- customarily used for software interchange.
-
- b) Convey the object code in, or embodied in, a physical product
- (including a physical distribution medium), accompanied by a
- written offer, valid for at least three years and valid for as
- long as you offer spare parts or customer support for that product
- model, to give anyone who possesses the object code either (1) a
- copy of the Corresponding Source for all the software in the
- product that is covered by this License, on a durable physical
- medium customarily used for software interchange, for a price no
- more than your reasonable cost of physically performing this
- conveying of source, or (2) access to copy the
- Corresponding Source from a network server at no charge.
-
- c) Convey individual copies of the object code with a copy of the
- written offer to provide the Corresponding Source. This
- alternative is allowed only occasionally and noncommercially, and
- only if you received the object code with such an offer, in accord
- with subsection 6b.
-
- d) Convey the object code by offering access from a designated
- place (gratis or for a charge), and offer equivalent access to the
- Corresponding Source in the same way through the same place at no
- further charge. You need not require recipients to copy the
- Corresponding Source along with the object code. If the place to
- copy the object code is a network server, the Corresponding Source
- may be on a different server (operated by you or a third party)
- that supports equivalent copying facilities, provided you maintain
- clear directions next to the object code saying where to find the
- Corresponding Source. Regardless of what server hosts the
- Corresponding Source, you remain obligated to ensure that it is
- available for as long as needed to satisfy these requirements.
-
- e) Convey the object code using peer-to-peer transmission, provided
- you inform other peers where the object code and Corresponding
- Source of the work are being offered to the general public at no
- charge under subsection 6d.
-
- A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
- A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling. In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage. For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product. A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
- "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source. The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
- If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
- The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed. Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
- Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
- 7. Additional Terms.
-
- "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
- When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
- Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
- a) Disclaiming warranty or limiting liability differently from the
- terms of sections 15 and 16 of this License; or
-
- b) Requiring preservation of specified reasonable legal notices or
- author attributions in that material or in the Appropriate Legal
- Notices displayed by works containing it; or
-
- c) Prohibiting misrepresentation of the origin of that material, or
- requiring that modified versions of such material be marked in
- reasonable ways as different from the original version; or
-
- d) Limiting the use for publicity purposes of names of licensors or
- authors of the material; or
-
- e) Declining to grant rights under trademark law for use of some
- trade names, trademarks, or service marks; or
-
- f) Requiring indemnification of licensors and authors of that
- material by anyone who conveys the material (or modified versions of
- it) with contractual assumptions of liability to the recipient, for
- any liability that these contractual assumptions directly impose on
- those licensors and authors.
-
- All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
- If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
- Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
- 8. Termination.
-
- You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
- However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
- Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
- Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
- 9. Acceptance Not Required for Having Copies.
-
- You are not required to accept this License in order to receive or
-run a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
- 10. Automatic Licensing of Downstream Recipients.
-
- Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
- An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
- You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
- 11. Patents.
-
- A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's "contributor version".
-
- A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
- Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
- In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
- If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
- If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
- A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License. You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
- Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
- 12. No Surrender of Others' Freedom.
-
- If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all. For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
- 13. Remote Network Interaction; Use with the GNU General Public License.
-
- Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software. This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
- Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
- 14. Revised Versions of this License.
-
- The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
- Each version is given a distinguishing version number. If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation. If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
- If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
- Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
- 15. Disclaimer of Warranty.
-
- THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 16. Limitation of Liability.
-
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
- 17. Interpretation of Sections 15 and 16.
-
- If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
- END OF TERMS AND CONDITIONS
-
- How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-
- Copyright (C)
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU Affero General Public License as published
- by the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU Affero General Public License for more details.
-
- You should have received a copy of the GNU Affero General Public License
- along with this program. If not, see .
-
-Also add information on how to contact you by electronic and paper mail.
-
- If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source. For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code. There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
- You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-.
+GNU AFFERO GENERAL PUBLIC LICENSE
+
+Version 3, 19 November 2007
+
+Copyright © 2007 Free Software Foundation, Inc.
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+TERMS AND CONDITIONS
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+1. Source Code.
+
+The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+ b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
+ c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+ d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+ b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+ c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+ d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+ e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+7. Additional Terms.
+
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+ b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+ c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+ d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+ e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+ f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
\ No newline at end of file
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..6bb20f8
--- /dev/null
+++ b/README.md
@@ -0,0 +1,189 @@
+# C5-DEC CAD
+
+This repository hosts the source code of C5-DEC CAD, the software component of C5-DEC for computer-assisted design and development (CAD), along with its associated documentation and guides, developed in the context of the CyFORT project. The documentation includes the full technical specifications, requirements, user manual, test case specifications and test reports, thereby highlighting the C5-DEC method that builds on capturing, storing and processing all software development life cycle (SDLC) artifacts in a unified manner.
+
+**C5-DEC**, short for "Common Criteria for Cybersecurity, Cryptography, Clouds – Design, Evaluation and Certification", is a subproject of the CyFORT project, in turn short for "Cloud Cybersecurity Fortress of Open Resources and Tools for Resilience".
+
+
+
+
+## Overview
+
+C5-DEC is aimed at assisting both system/software designers/developers as well as system security analysts with creating and evaluating secure software systems. C5-DEC CAD can be used by evaluation laboratories for the execution of impartial assessments of the security of computer systems and software according to the Common Criteria (CC), a set of internationally recognized standards (ISO/IEC 15408), and the complementary ISO/IEC 18045, dealing with a common methodology for computer security evaluation (CEM). CC certification gives users the assurance that a product satisfies the security guarantees and properties it claims to possess. Among other things, C5-DEC is also aimed at providing tools for supporting a secure software development life cycle (SSDLC).
+
+C5-DEC consists of two key elements: a software component (C5-DEC CAD) and a knowledge base including guides and a wiki of key CC concepts. These elements complement each other to form a coherent set of tools aimed at supporting activities related to CC certification, SSDLC and security assessment of cyber-physical systems, based on the C5-DEC method for Cyber-Physical System Security Assessment (CPSSA).
+
+## Features
+
+- Free/libre and open source
+- Cross platform: works on GNU/Linux, MacOS and Windows
+- Easily and highly extensible due to a modular design and architecture
+- Advanced and extensible textual user interface (TUI), powered by the open-source [asciimatics](https://github.com/peterbrittain/asciimatics) framework
+- A command-line interface (CLI) for more efficient user interactions and scripting
+- Comprehensive [Common Criteria](https://www.commoncriteriaportal.org/index.cfm) Toolbox (CCT), with a focus on efficient browsing of the CC database, creating and processing evaluation checlists
+ - includes all baseline CC Security Functional Requirements (SFR) and Security Assurance Requirements (SAR)
+ - built-in capabilities for assisting the process of generating technical evaluationr reports (ETR)
+ - comes with a CC wiki capturing the key concepts of Common Criteria
+- Tools for enhancing secure software development life cycle (SSDLC), powered by the open-source [Doorstop](https://github.com/doorstop-dev/doorstop) tool
+- Complete integration of the CCT data store with the Doorstop data model and formats
+- Based on and designed around open data formats such as Markdown, (La)TeX, YAML, XML, JSON, CSV, HTML, txt, etc.
+- Straightforward integration into well-known Dev(Sec)Ops platforms such as GitHub and GitLab
+- Project (resource) management functionality
+- Import/export from and to open data formats
+- Cryptography-related functionality aimed at improving SSDLC (currently not implemented, but on the roadmap and planned for [future releases](./docs/manual/cryptography.md))
+- A method for Cyber-Physical System Security Assessment (CPSSA) and related functionality (see [CPSSA](./docs/manual/cpssa.md))
+
+## User manual
+
+Check the [CAD user manual](./docs/manual/overview.md) to learn more about the specific modules of C5-DEC CAD and its usage. The table of contents is also shown below:
+
+- [Installation](./docs/manual/installation.md)
+- [Setup](./docs/manual/setup.md)
+- [Quick start](./docs/manual/start.md)
+- [CCT: Common Criteria Toolbox](./docs/manual/cct.md)
+- [SSDLC: secure software development life cycle](./docs/manual/ssdlc.md)
+- [Cryptography](./docs/manual/cryptography.md)
+- [CPSSA: Cyber-Physical System Security Assessment](./docs/manual/cpssa.md)
+- [Transformer: import, export, publish](./docs/manual/transformer.md)
+- [ISMS: document management](./docs/manual/isms.md)
+- [PM: project (resource) management](./docs/manual/pm.md)
+- [C5-DEC Common Criteria wiki](./c5dec/assets/database/KnowledgeBase/0_MapofContent.md)
+
+## Getting Started
+
+C5-DEC CAD can be currently deployed using any of the following methods:
+
+- Installation via [pipx](https://pypa.github.io/pipx/) using the official [distribution file]() (recommended for end-users)
+- Installation in a containerized environment (recommended for developers)
+- Install via the official PyPI repository (**currently not available, coming soon**)
+
+### Installing C5-DEC CAD via pipx
+
+#### Requirements
+
+- [Python 3](https://www.python.org/)
+- [git](https://git-scm.com/), the distributed version control system
+
+##### Optional
+
+- [Doorstop](https://github.com/doorstop-dev/doorstop) (recommended to install via `pipx`)
+
+Strictly speaking, a Doorstop installation is not required; nevertheless, we strongly recommend installing Doorstop such that it can be used in combination with C5-DEC CAD. This is mainly due to the fact that the SSDLC module in the current implementation of C5-DEC CAD does not provide a full coverage of the Doorstop API, which is why users may find it easier to carry out certain complementary operations using Doorstop.
+
+To install Doorstop, we recommend the following method using [pipx](https://pypa.github.io/pipx/) as it is rather straightforward. Once `pipx` is installed, simply run the following command:
+```sh
+$ pipx install doorstop==3.0b10
+```
+
+#### Installation
+
+On a GNU/Linux distribution or MacOS, open a terminal (e.g., bash, Zsh) and execute the following commands:
+
+```sh
+python3 -m pip install --user pipx
+python3 -m pipx ensurepath
+```
+
+Run the following command, assuming that the Wheel distribution file (.whl) is placed in the current directory:
+
+```sh
+pipx install ./c5dec-0.1-py3-none-any.whl
+```
+
+#### Launching C5-DEC CAD
+
+You can start C5-DEC CAD by simply entering “c5dec” in an open terminal, with the current directory being an unpacked copy of the C5-DEC CAD [project folder](). For the sake of this example, we assume that the zip archive is unpacked at the following path `/home/user/c5dec-cad-alpha`; it then suffices to change to this directory and run `c5dec`:
+
+```sh
+$ cd /home/user/c5dec-cad-alpha
+$ c5dec
+```
+This would then launch the TUI by default, as shown below.
+
+
+
+For more details and installing on Windows, see the [Installation](./docs/manual/installation.md) page of the user manual.
+
+### Installation in a containerized environment
+
+The easiest and recommended way to get a local copy of the development environment up and running is described next.
+
+#### Requirements
+
+The following instructions explain how to build C5-DEC CAD from the source code. The following pieces of software are necessary for setting up the C5-DEC CAD containerized environment.
+
+* A local installation of [Docker Desktop](https://www.docker.com/products/docker-desktop/)
+* [Visual Studio Code](https://code.visualstudio.com/) (VS Code)
+* The [Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension for VS Code by Microsoft
+
+#### Installation
+
+1. Clone this repository
+```sh
+git clone http://gitlab.abstractionslab.com/cyfort/c5-dec/cad.git
+```
+2. Verify that your Docker Desktop instance is running (if not, start it).
+3. In VS Code, open the folder "cad", located at the root of the cloned project. This can be done directly in VS code or from the terminal, if the CLI of VS Code is installed:
+```sh
+code cad
+```
+4. In the notification that pops up in VS Code, select the option "Reopen in Container". This will create and run the project inside a Docker container; alternatively, the same command can be selected and invoked from the VS Code command palette.
+4. Open a terminal in VS Code and run the following command in the GNU/Linux container for which the local file system is automatically mapped by VS Code to that of the Ubuntu container:
+```sh
+poetry install
+```
+This verifies the correct installation of all the dependencies.
+
+_**Hint:**_ to solve warnings in the code related to missing imports, select the Python interpreter installed by poetry. This can be done quickly by clicking on the light bulb that appears next to the warnings.
+
+## Usage
+
+The C5-DEC CAD tool has two modes of operation: a textual user interface (TUI) and a command line interface (CLI).
+
+### Textual User Interface
+
+Once installed, the C5-DEC CAD tool can be launched from the VS Code terminal as follows:
+
+```sh
+$ cd c5dec
+$ poetry run c5dec
+```
+
+Alternatively, the tool can be executed from Docker Desktop:
+
+1. In the left-side menu, go to the tab "Containers".
+2. Open the container associated to C5-DEC CAD (the image name starts with "vsc-cad").
+3. Go to the "Exec" tab.
+4. Run the same commands as above.
+
+### Command Line Interface
+In a VS Code (or Docker Desktop) terminal run:
+
+```sh
+$ cd c5dec
+$ poetry run c5dec
+```
+To see the available commands run:
+```sh
+$ poetry run c5dec -h
+```
+
+_**Disclaimer:**_ For the moment, we recommend using the TUI for functionality related to the CCT module. This note will be updated as soon as a stable version of the CLI for the referred module becomes available.
+
+## Roadmap
+
+This information is available in the project [Wiki](https://gitlab.abstractionslab.com/cyfort/c5-dec/cad/-/wikis/Roadmap) of this repository.
+
+## License
+
+This piece of software is released under the [GNU Affero General Public License (AGPL) v3.0](LICENSE) license.
+
+## Contact
+
+If you wish to learn more about the project, feel free to contact us at Abstractions Lab: info@abstractionslab.lu
+
+## Design and development team
+
+The C5-DEC knowledge base and its CAD software component have been designed and developed by Abstractions Lab (ALab) and itrust consulting (ITR).
+
+Arash Atashpendar (ALab), Heinrich Fries (ITR), Itzel Vazquez Sandoval (ALab), Sven Angel (ex-ITR)
\ No newline at end of file
diff --git a/c5dec/__init__.py b/c5dec/__init__.py
new file mode 100644
index 0000000..29974ca
--- /dev/null
+++ b/c5dec/__init__.py
@@ -0,0 +1,36 @@
+"""Package for c5dec."""
+
+from pprint import pprint
+import sys, os
+
+from pkg_resources import DistributionNotFound, get_distribution
+from doorstop import DoorstopError, DoorstopInfo, DoorstopWarning
+from c5dec.core import (
+ cpssa,
+ ssdlc,
+ cryptography,
+ cct,
+ isms,
+ pm,
+ transformer
+)
+
+__project__ = "Doorstop"
+
+
+script_dir = os.path.dirname(__file__)
+mymodule_dir = os.path.join(script_dir, '.')
+sys.path.append(mymodule_dir)
+# pprint(sys.path)
+
+__project__ = "c5dec"
+
+try:
+ __version__ = get_distribution(__project__).version
+except DistributionNotFound:
+ __version__ = "(local)"
+
+CLI = "c5dec"
+TUI = "c5dec-tui"
+VERSION = "{0} v{1}".format(__project__, __version__)
+DESCRIPTION = "C5-DEC for computer-assisted design and development (C5-DEC CAD)."
\ No newline at end of file
diff --git a/c5dec/assets/acronyms/persons.json b/c5dec/assets/acronyms/persons.json
new file mode 100644
index 0000000..fe08508
--- /dev/null
+++ b/c5dec/assets/acronyms/persons.json
@@ -0,0 +1,7 @@
+{
+ "Alan Turing": "ATU",
+ "John von Neumann": "JVN",
+ "Pierre de Fermat": "PDF",
+ "Andrew Wiles": "AWI",
+ "Mathematicians": "MAT"
+}
\ No newline at end of file
diff --git a/c5dec/assets/config.json b/c5dec/assets/config.json
new file mode 100644
index 0000000..ae201a9
--- /dev/null
+++ b/c5dec/assets/config.json
@@ -0,0 +1,6 @@
+{
+ "width": 100,
+ "height": 100,
+ "language": "en",
+ "title": "C5-DEC CAD"
+}
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/0_MapofContent.md b/c5dec/assets/database/KnowledgeBase/0_MapofContent.md
new file mode 100644
index 0000000..e15c89f
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/0_MapofContent.md
@@ -0,0 +1,50 @@
+# Map of Content
+
+## CC-Concepts
+1. [Target of Evaluation](./TargetofEvaluation.md)
+ 1. [TOE Security Functionality](./TOESecurityFunctionality.md)
+ 1. [TSF Interface](./TSFInterface.md)
+ 3. [TOE Operational Environment](./TOEOperationalEnvironment.md)
+ 4. [TOE Boundary](./TOEBoundary.md)
+2. [Conformance Claims](./ConformanceClaim.md)
+1. [Conformance Statement](./ConformanceStatement.md)
+2. [Security Problem Definition](./SecurityProblemdefinition.md)
+ 1. [Asset](./Asset.md)
+ 2. [Threat](./Threat.md)
+ 3. [Organizational Security Policy](./OrganizationalSecurityPolicy.md)
+ 4. [Assumption](./Assumption.md)
+3. [Security Objectives](./SecurityObjective.md)
+4. [Security Components](./SecurityComponent.md)
+ 1. [Security Functional Requirements]
+ 2. [Security Assurance Requirements]
+ 3. [Requirement Operations](./Operations.md)
+ 1. [Refinement](./Operation-Refinement.md)
+ 2. [Iteration](./Operation-Iteration.md)
+ 3. [Assignment](./Operation-Assignment.md)
+ 4. [Selection](./Operation-Selection.md)
+ 4. [Extended Component Definition](./ExtendedComponentDefinition.md)
+4. [Rationales]
+5. [Evaluation]
+ 1. [Evaluation Methods and Activities](./EvaluationMethods.md)
+ 2. [Single-assurance Evaluation](./SingleAssuranceEvaluation.md)
+ 3. [Multi-assurance Evaluation](./MultiAssuranceEvaluation.md)
+ 4. [Composite Evaluation](./CompositeEvaluation.md)
+ 5. [Evaluation Assurance Levels](./EvaluationAssuranceLevel.md)
+ 6. [Attack Potential](./AttackPotential.md)
+9. [Direct Rationale](./DirectRationale.md)
+
+## Core Constructs
+
+1. [Security Target](SecurityTarget.md)
+2. [Protection Profile](ProtectionProfile.md)
+3. [PP-Configuration]
+2. [PP-Module]
+5. [Package]
+ 1. [Assurance Package - Definition]
+ 2. [Functional Package]
+6. [Observation Report](./ObservationReport.md)
+7. [Evaluation Technical Report](./EvaluationTechnicalReport.md)
+
+## Terms & Definitions
+
+- [Terms and Definition Register](./0_TermsandDefinitions-BOK.md)
diff --git a/c5dec/assets/database/KnowledgeBase/Asset.md b/c5dec/assets/database/KnowledgeBase/Asset.md
new file mode 100644
index 0000000..5b343fd
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Asset.md
@@ -0,0 +1,88 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Asset
+
+**Acronym:** A
+
+An **Asset** in cybersecurity refers to an item or information considered of value and thus necessitates protection. Assets, often in the form of information, are stored, processed, and transmitted by IT products and are vital to the functioning and continuity of an organization. The compromise of an asset, whether through loss of confidentiality, integrity, or availability, can result in a devaluation or potential operational disruptions. Protecting assets from [threats](./Threat.md) via security controls, usually referred to as [security objectives](./SecurityObjectives.md) in the context of CC, implemented in the [operational environment (OE)](./TOEOperationalEnvironment.md) is paramount.
+
+Assets, particularly within the realm of Common Criteria, serve as focal points around which threats and security objectives are defined and evaluated. Ensuring the protection of assets translates to preserving organizational value and maintaining operational integrity.
+
+## Practical Guidance
+
+Asset identification is a foundational step in the cybersecurity lifecycle, especially within the framework of Common Criteria. Assets usually fall into one of three classes:
+- **information assets** Data that is processed, stored, or transmitted by IT systems.
+- **process assets** Established procedures and methodologies vital for operational continuity.
+- **physical assets** Tangible items such as hardware, facilities, and physical infrastructure.
+
+Assets can further be categorised as:
+
+- **Primary assets** compromise of a primary asset will have immediate affect on the [Target of Evaluation (TOE)](./TargetofEvaluation.md).
+- **Secondary assets** compromise of a secondary asset will not have immediate affect on the TOE, but may affect a primary asset.
+- **TSF data** data for the operation of the TOE upon which the enforcement of the security functional requirement relies.
+- **User data** data received or produced by the TOE, which is meaningful to some external entity, but which do not affect the operation of the [TOE security funtionality (TSF)](./TOESecurityFunctionality.md).
+
+It is important not to identify too many assets or types of assets. If two assets or types of assets have the same potential for attack and consequences of attack, they should be grouped together into a composite asset type. Many TOEs will protect only two types of asset, TSF data and user data. More than six types of asset is probably inappropriate for anything other than a TOE that is expected to offer very complex or individualised protection capabilities.
+
+
+
+### Key Steps in Asset Identification
+
+1. **Understanding the Target of Evaluation (TOE):**
+ - Gain a thorough understanding of the TOE, including its functionality, data it processes, and its operating environment.
+ - Analyze the TOE’s functional and informational boundaries and the entities that interact with it.
+
+2. **Analyzing TOE’s Functional and Security Architecture:**
+ - Dive into the TOE's system architecture to understand data flow, storage, processing, and transmission aspects.
+ - Evaluate the security attributes (confidentiality, integrity, availability) that are applicable to each component of the TOE.
+
+3. **Engaging Stakeholders:**
+ - Convene with TOE stakeholders, such as developers, administrators, and users, to glean insights into key functional and data components.
+ - Ensure comprehensive awareness of user roles, data interactions, and functionalities by interacting with different stakeholders.
+
+4. **Identifying TOE’s Information Assets:**
+ - Identify information that the TOE processes, stores, or transmits which, if compromised, could impact the TOE or its stakeholders.
+ - Determine the forms in which information assets exist, e.g., databases, configurations, user data, logs, cryptographic keys, and identify their locations and states (transit/storage).
+ - Apply a preliminary risk outlook to guide prioritization in asset identification, especially for those handling sensitive or critical data.
+
+5. **Exploring Dependence on Physical and External Assets:**
+ - Identify physical assets (hardware, facilities) that are crucial for TOE’s operations and security.
+ - Determine the TOE's dependence on external assets such as external databases, network infrastructure, or external services.
+
+6. **Identifying Interconnections and Dependencies:**
+ - Establish a clear understanding of how the TOE interacts with external entities and other IT systems.
+ - Identify assets within these external entities that are crucial for the TOE’s operation and security.
+ - Pinpoint and document relevant security attributes and potential risk vectors emerging from interconnections and dependencies.
+
+7. **Develop an Asset Inventory:**
+ - **Catalog Assets:** List all identified items of value within the organization, providing a unique identifier, an asset definition, and the asset's need for protection (Confidentiality, Integrity, Authenticity).
+ - **Characterize and Group Assets:** Describe the nature, classification, and importance of each asset, and group similar assets accordingly.
+ - **Secure Asset Inventory Management:** Ensure the asset inventory itself is securely stored, with strict access controls and audit logging to safeguard information about organizational assets.
+
+### Additional Considerations:
+
+- **Documentation of Process:**
+ - Ensure systematic documentation of the asset identification process, capturing methods, data sources, interactions, and decisions, to facilitate auditability and future reference.
+
+- **Dynamic and Adaptive Asset Management:**
+ - Ensure that the asset identification process can dynamically adapt to technological, organizational, and environmental changes. Regularly review and adjust the asset inventory and characterizations in response to these changes.
+
+- **Communication and Feedback Loops:**
+ - Establish consistent communication channels and feedback mechanisms with asset owners and stakeholders to receive updates, insights, or alerts related to assets and to ensure the currency of the asset inventory and related attributes.
+
+## Additional Resources
+
+- **ISO/IEC 27001:** Provides guidelines on information security management and asset control.
+- **NIST SP 800-53:** A detailed guide on security controls and risk management.
+- **ISO/IEC TR 15446:** A Guide for the production of Protection Profiles and Security Targets.
+
+## Related Documents
+
+- [Deriving the Security Problem Definition](./SecurityProblemdefinition.md)
+- [Identifying Threats](./Threat.md)
+- [Deriving Security Objectives](./SecurityObjectives.md)
+- [Understanding the Operational Environment (OE)](./TOEOperationalEnvironment.md)
+
diff --git a/c5dec/assets/database/KnowledgeBase/Assumption.md b/c5dec/assets/database/KnowledgeBase/Assumption.md
new file mode 100644
index 0000000..8519895
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Assumption.md
@@ -0,0 +1,32 @@
+# Assumption
+
+**Acronym:** None
+
+Security rests on assumptions specific to the type of security required and the environement in which it is to be employed. Assumptions are treated as axioms, i.e., they are taken to be true, to serve as a premise for further reasoning and arguments. Assumptions provide a grounding, describing expected conditions in the [operational environment](TOEOperationalEnvironment.md) which are presumed to be true, and under which the [Target of Evaluation (TOE)](./TargetofEvaluation.md) will operate securely. These are essential in the construction of a [Security Problem Definition (SPD)](./SecurityProblemdefinition.md) and subsequently the entire security posture of the TOE.
+
+In the world of CC, assumptions are categorized based on aspects such as physical, personnel, and connectivity of the operational environment. However, these assumptions are not scrutinized or tested during the evaluation phase as they are regarded as fundamental truths, providing a reliable basis upon which the [TOE's security functionality](./TOESecurityFunctionality.md) is conceived and designed. Consequently, if a TOE is placed in an environment that does not adhere to these assumptions, its security functionality and reliability can be compromised.
+
+## Practical Guidance
+
+Navigating through the landscape of crafting and implementing assumptions within CC involves being mindful of their dual utility and strategic integration. Assumptions in CC are leveraged to:
+
+- **Dictate Environmental Controls**: Highlight specific controls or types of controls that are the responsibility of the operational environment and not the TOE.
+- **Dismiss Irrelevant Threats**: Specify threats or types of threats that can be disregarded, asserting that they either do not exist or are not pertinent in the context of the posited operational environment.
+
+### Identifying and Formulating Assumptions:
+- **Operational Insights:** Derive assumptions from an in-depth understanding of the physical, personnel, and connectivity aspects of the operational environment.
+- **Policy Alignment:** Shape assumptions that are in sync with organizational policies and user behaviors.
+- **Regulatory Adherence:** Ensure that assumptions are congruent with legal and regulatory requirements.
+- **Industry Benchmarking:** Evaluate industry best practices and historical incident data to extract relevant assumptions.
+- **Articulation into Security Objectives:** Ensure that assumptions are translated into actionable [security objective](./SecurityObjective.md) in the [Security Target (ST)](./SecurityTarget.md) or [Protection Profile (PP)](./ProtectionProfile.md). These security objectives should offer a clear, solution-oriented representation, elucidating how the TOE's operational environment will concretely upheld the assumptions.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** A Guide for the production of Protection Profiles and Security Targets.
+
+## Related Articles
+
+- [Deriving the Security Problem Definition](./SecurityProblemdefinition.md)
+- [Identifying Threats](./Threat.md)
+- [Deriving Security Objectives](./SecurityObjectives.md)
+- [Understanding the Operational Environment (OE)](./TOEOperationalEnvironment.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/AttackPotential.md b/c5dec/assets/database/KnowledgeBase/AttackPotential.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/ComposedTOE.md b/c5dec/assets/database/KnowledgeBase/ComposedTOE.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/CompositeEvaluation.md b/c5dec/assets/database/KnowledgeBase/CompositeEvaluation.md
new file mode 100644
index 0000000..76e6324
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/CompositeEvaluation.md
@@ -0,0 +1,19 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: CC 2022
+Tags: [Composite Evaluation]
+---
+
+# Composite Evaluation
+
+**Acronym:** None
+
+For IT products that are composed of several independent, already evaluated product components the composed security assurance can be evaluated. The composition of assurance is dependent upon:
+- Type of composition, it is differentiated between layered, network or bi-directional, and embedded compositions.
+- Security function policies, and [OSPs](./OrganizationalSecurityPolicy.md) that the component evaluation was based on:
+- Claimed security assurance, for example the [assurance level](./EvaluationAssuranceLevel.md)
+- The overall security policies for the entire product.
+
+The CC only explicitly addresses the layered composition model. For bi-directional and embedded composition models [extended components](./ExtendedComponentDefinition.md) and [evaluation methods](./EvaluationMethods.md) have to be defined.
+
+For the evaluation of layered [TOE](./TargetofEvaluation.md) compositions the CC defined the Composition class ACO in CC Part 3. In the layered composition two already evaluated TOEs are assumed one of which is defined to be the base TOE while the other is considered to be the dependent TOE. The evaluation of such a composed TOE consists of evaluating the interaction between both TOEs. CC Part 5 provides pre-defined Composition Assurance Packages that may be used for determining the composed TOE’s assurance level. The COMP related assurance families specified in CC Part 3 for the ADV, ALC, ASE, ATE and AVA classes provide evaluation criteria pertinent to composite products using this layered model.
diff --git a/c5dec/assets/database/KnowledgeBase/ConformanceClaim.md b/c5dec/assets/database/KnowledgeBase/ConformanceClaim.md
new file mode 100644
index 0000000..8228277
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/ConformanceClaim.md
@@ -0,0 +1,33 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# Conformance Claim
+
+A Conformance Claim serves as an explicit declaration by the develoepr, stipulating the degree and manner to which a [Target of Evaluation (TOE)](./TargetofEvaluation.md) adheres to a specific [Security Target (ST)](./SecurityTarget.md) or [Protection Profiles (PPs)](./ProtectionProfile.md). It delineates the exactness or latitude in compliance with the outlined security functionalities and assurance requirements, offering a structured perspective to evaluators and consumers regarding the TOE's security attributes and the breadth of its evaluation. The claim usually encompasses various conformance types, such as CC Conformance, Package Conformance, and PP Conformance, each offering distinct insights into the TOE’s alignment with the CC, particular [packages](./Package.md), or specific PPs, respectively. Consequently, the Conformance Claim becomes instrumental in establishing transparency and assurance in the TOE's security properties and evaluation scope, thereby facilitating informed decision-making for stakeholders in adopting secure products and solutions.
+
+## CC Conformance Claim
+
+The CC conformance claim specifies the version of CC Part 2 and CC Part 3 to which conformance is claimed. The recognized conformance claims are:
+
+- **CC Part x conformant**: All Security Requirements in the claiming document are based only upon components in CC Part x.
+- **CC Part x extended**: At least one Security Requirement in the claiming document is not based upon components in CC Part x.
+
+## Package Conformance Claim
+
+If package conformances are claimed, for each package the claim must be categorized as one of the following:
+
+- **Package conformant**
+ - For functional packages, all constituent parts ([SPD](./SecurityProblemdefinition.md), [Security Objectives](./SecurityObjective.md), and [SFRs](./SecurityFunctionalRequirement.md)) of the functional package are present without modification. PPs can restrict some selections of SFRs in a package and still claim to be package conformant.
+ - For assurance packages, the [SARs](./SecurityAssuranceRequirement.md) are identical to the SARs in the assurance package.
+- **Package augmented**
+ - For functional packages, all constituent parts (SPD, security objectives, and SFRs) of the functional package are present but at least one additional SFR or one SFR that is hierarchically higher than an SFR in the package is included;
+ - For assurance packages, all SARs in the assurance package are included but also at least one additional SAR or one SAR that is hierarchically higher than an SAR in the assurance package.
+- **Package tailored**
+ - For functional packages, all constituent parts (SPD, security objectives, and SFRs) are given in the functional package, but shall have additional selection items for an SFR with existing selections in the package, and optionally, at least one additional SFR and/or one SFR that is hierarchically higher than an SFR in the functional package;
+ - Not allowed for STs.
+
+## PP Conformance Claim
+
+PPs and PP-Configurations specify the type of conformance that is allowed in a conformance statement. Claiming to be PP Conformant requires compliance according to the conformance statement.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/ConformanceStatement.md b/c5dec/assets/database/KnowledgeBase/ConformanceStatement.md
new file mode 100644
index 0000000..fb8d817
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/ConformanceStatement.md
@@ -0,0 +1,27 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# Conformance Statement
+
+The Conformance Statement describes the manner in which an ST shall conform. The CC permits a conformance statement to be either exact, strict, or demonstrable.
+
+## Exact conformance
+ - The notion of exact conformance was introduced in the latest release of the Common Criteria (CC:2022). Exact conformance requires the ST claiming conformance to be an exact instantiation of the conformity enforcing PP(s), or PP-Configuration, i.e., that it contains all statements (SPD, Security Objective, and SFRs) without including any additional functionality.
+ - For SFRs the following applies:
+ - Selection-based SFRs in the PPs or PP-Modules shall be excluded if the selection that requires their inclusion is not chosen by the ST author;
+ - Optional SFRs in the PPs or PP-Modules may be included or excluded while maintaining its exact conformance claim.
+ - If a PP, PP-Configuration requires exact conformance it shall include an Allowed-with Statement that states which other PPs or PP-Configurations are allowed to be included in a conformance claim along with the PP.
+## Strict conformance
+ - Strict conformance requires that ST claiming conformance is an instantiation of the PP(s), or PP-Configurations though it can be broader, i.e., that it contains all statements (SPD, Security Objective, and SFRs) that are in the conformance enforcing document but can contain additional elements. Strict conformance is expected to be used for stringent requirements that are to be adhered to in a single manner.
+## Demonstrable conformance
+ - Demonstrable conformance means that ST claiming conformance to the PP(s), or PP-Configurations has to offer a solution to the generic security problem described in the conformance enforcing document(s), but can do so in any way equivalent or more restrictive to that described. More precisely, if demonstrable conformance is required, the ST shall contain an SPD, set of security objectives, and a set of SFRs that are equivalent to a superset of the enforcing document’s SPD, security objectives, and SFRs, where the new assumptions (if any) do not weaken the original SPD, and where the set of the ST’s SFRs imply the original SFRs.
+
+
+1. [Conformance Types]
+ 1. [Exact]
+ 1. [Allowed-with Statement]
+ 2. [Exact conformance - FAQ](./Exactconformance-FAQ.md)
+ 2. [Strict]
+ 3. [Demonstrable]
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/DirectRationale.md b/c5dec/assets/database/KnowledgeBase/DirectRationale.md
new file mode 100644
index 0000000..104a380
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/DirectRationale.md
@@ -0,0 +1,11 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: CC 2022
+Tags: [Evaluation Assurance Level, EAL]
+---
+
+# Direct Rationale Approach
+
+**Acronym:** None
+
+COMING SOON.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/DomainSeparation.md b/c5dec/assets/database/KnowledgeBase/DomainSeparation.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/EUCC.md b/c5dec/assets/database/KnowledgeBase/EUCC.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/EvaluationAssuranceLevel.md b/c5dec/assets/database/KnowledgeBase/EvaluationAssuranceLevel.md
new file mode 100644
index 0000000..d0f1753
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/EvaluationAssuranceLevel.md
@@ -0,0 +1,31 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC 2022
+Tags: [Evaluation Assurance Level, EAL]
+---
+
+# Evaluation Assurance Level
+
+**Acronym:** EAL
+
+An attack potential is a measure of the effort to be expended in attacking a TOE, expressed as the sum of the numerical values calculated for each of the five factors
+
+| Attack Factor | Value Range | Example Values |
+|----|----|----|
+| **Elapsed time** | (0-8) | It refers to the time required for mounting the attack. The value is weighted in accordance with the elapsed time. "less than one day" (value: 0), "between one day and one week" (value: 1), "between one week and two weeks" (value: 2), "between two weeks and one month" (value: 4) |
+| **Specialist expertise** | (0-11) | It refers to the generic technical knowledge required for mounting the attack. The value is weighted in accordance with the level of knowledge. "layman" (value: 0), "proficient person" (value: 3), "expert" (value: 6) |
+| **Knowledge of TOE** | (0-19) | It refers to knowledge of the design and operation of the target product that is required for successfully mounting the attack. The value is weighted in accordance with the difficulty in obtaining the product information. "public information" (value: 0), "restricted information" (value: 3), "sensitive information" (value: 7) |
+| **Window of opportunity** | (0-10) | It refers to the access opportunity to the target product that is required for the attack. The value is weighted in accordance with the difficulty involved in accessing the product without the attack being noticed until the success of the attack. "unnecessary/unlimited access" (value: 0), "easy access" (value: 1), "moderate access" (value: 4), "difficult access" (value: 10) |
+| **Equipment** | (0-9) | It refers to the software or hardware required for the attack. The value is weighted in accordance with the difficulty in obtaining the equipment. "standard equipment" (value:0), "specialized equipment" (value: 4), "bespoke equipment" (value: 7) |
+
+The calculated attack potential translates to a Vulnerability analysis (AVA_VAN) component, and indirectly to an [Evaluation Assurance Level](./EvaluationAssuranceLevel.md).
+
+| Values | Attack Potential required to exploit scenario | Meets assurance components | Failure of components|
+|---|---|---|---|
+| 0-9 | basic | - | AVA_VAN.1, AVA_VAN.2, AVA_VAN.3, AVA_VAN.4, AVA_VAN.5 |
+| 10-13 | enhanced-basic | AVA_VAN.1, AVA_VAN.2 | AVA_VAN.3, AVA_VAN.4, AVA_VAN.5 |
+| 14-19 | moderate | AVA_VAN.1, AVA_VAN.2, AVA_VAN.3 | AVA_VAN.4, AVA_VAN.5 |
+| 20-24 | high | AVA_VAN.1, AVA_VAN.2, AVA_VAN.3, AVA_VAN.4 | AVA_VAN.5 |
+| =>25 | beyond high | AVA_VAN.1, AVA_VAN.2, AVA_VAN.3, AVA_VAN.4, AVA_VAN.5 | - |
+
+The [TOE's](./TargetofEvaluation.md) resistance must be equal to the highest attack potential, i.e., the attack scenario with the highest attack potential is decisive for the determination of TOE resistance, vulnerability analysis component, and subsequently the TOE’s EAL.
diff --git a/c5dec/assets/database/KnowledgeBase/EvaluationEvidence.md b/c5dec/assets/database/KnowledgeBase/EvaluationEvidence.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/EvaluationEvidenceIndex.md b/c5dec/assets/database/KnowledgeBase/EvaluationEvidenceIndex.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/EvaluationMethods.md b/c5dec/assets/database/KnowledgeBase/EvaluationMethods.md
new file mode 100644
index 0000000..a968708
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/EvaluationMethods.md
@@ -0,0 +1,103 @@
+---
+Last Updated: October 4, 2023
+Relevant: CC Version 3.1 Revision 5, CC 2022
+Tags: [Evaluation Methods, Evaluation Activity, Evaluation Sub-activity, Evaluation Action, Work Unit, Evaluation Process, General Evaluation Model, Evaluation Input Task, Evaluation Output Task, Demonstration of Technical Competence Task, Evaluation Verdict, Evaluation Results, CEM]
+---
+
+# Evaluation Methods and Activities
+
+**Acronym:** EM, EA
+
+While CC sets the security standards for IT products, CEM provides a detailed roadmap for evaluators to assess whether a product meets these standards. To this end, an Evaluation Method in the CEM is the structured evaluation process that encompasses a sequence of related Evaluation Activities, Sub-activities, Actions, and Work Units (defined as explicit evaluation tasks) designed to facilitate the evaluation of a [Security Assurance Requirement (SAR)](./SecurityAssuranceRequirement.md). Here's a breakdown of the conceptual hierarchy of an Evaluation Method:
+
+1. **Evaluation Activity:** The high-level tasks or overarching actions that evaluators are expected to undertake to assess specific aspects of a TOE.
+2. **Evaluation Sub-Activity:** A defined subset of the activity that further breaks down the evaluation process by specifying the sub-activity's objective and the required evaluation evidence
+3. **Evaluation Action:** A container for all Work Units that exhaustively cover all aspects of an [Evaluation Action Element](./SecurityAssuranceRequirement.md).
+4. **Work Unit:** A concrete instruction of the evaluator's tasks to thoroughly assess the conformance of the evaluation evidence with the corresponding [Content and Presentation Element](./SecurityAssuranceRequirement.md).
+
+Drawing from the outlined structure of an Evaluation Method, it becomes apparent that there is a systematic mapping between Evaluation Methods in the Common Evaluation Methodology and the [Security Assurance Components](./SecurityComponent.md) in the Common Criteria. The mapping between these two structures is shown in the figure below.
+
+
+
+Each Assurance Component is mapped to an Evaluation Sub-Activity ensuring that every distinct assurance criterion is subjected to a specific evaluation sub-process. Analogously, each SAR is complemented by Evaluation Actions and Work Units corresponding respectively to the SARs Evaluation Action Elements and Developer and Content Elements.
+
+## Practical Guidance
+
+The CEM is fundamentally designed as a methodological guideline targeted towards evaluators, providing a structured and standardized pathway to evaluate IT products against the Common Criteria. It intends to establish a standardized evaluation process, aiming to enable comparability and consistency across evaluations, trying to ensure that irrespective of the evaluator or evaluation body, results are coherent and in alignment. However, the CEM only dictates the minimum requirements for an evaluation, making adherence to it a foundational necessity but not always sufficient, especially considering additional stipulations imposed by national certification schemes. Despite the foundational principle of ensuring comparability amongst CCRA participating members, the imposition of additional national requirements often impedes true comparability, introducing variations in the rigor and depth of evaluations. The European Union's [EUCC](./EUCC.md) (European Cybersecurity Certification) scheme aspires to bring about a more harmonized approach, aiming to unify the national schemes, at least within the European Union, and establish a common ground that allows for more genuine and unimpeded comparability between evaluations and certifications.
+
+The general evaluation model prescribed by the CEM consists of the
+1. **Evaluation Input Task:** ensure that the correct version of the [evaluation evidence](./EvaluationEvidence.md) is available and create an [evaluation evidence index](./EvaluationEvidenceIndex.md);
+2. **Evaluation Sub-activities:** depend on the type of evaluation (PP, PP-Configuration, or ST/TOE evaluation) and the selected assurance components
+3. **Evaluation Output Task:** report evaluation results, write [Observation Reports (OR)](./ObservationReport.md) if needed and [Evaluation Technical Reports (ETR)](./EvaluationTechnicalReport.md);
+4. **Demonstration of Technical Compotence Task:** validates the rigor and depth of the evaluation conducted.
+
+### Evaluation Input Task
+
+The core objective of the "Evaluation Input Task" is to ensure that the evaluator has access to the correct version of the necessary evaluation evidence and that this evidence is adequately protected to uphold the technical accuracy and repeatability of the evaluation. This involves organizing and indexing the required evaluation evidence, which must be stable and formally-issued, ensuring all relevant evaluation evidence pertaining to the Target of Evaluation (TOE) is readily available and safeguarded throughout the evaluation.
+
+### Evaluation Sub-activities - Determine the Evaluation Scope
+
+Although, the evaluation scope is determined by the type of evaluation, e.g. a document evalution such as PP, PP-Configuration or ST, or a TOE evaluation, ultimately it is explicitly defined by the set of selected Assurance Components. In the case of a document evaluation the evaluation scope is immediatley derived from the Assurance Classes APE: Protection Profile evaluation, ACE: PP-Configuration evaluation, or ASE: Security Target evaluation. These classes only differentiate between the standard and low-assurance (CCv3R5) or [direct rationale](./DirectRationale.md) (CC2022) approach and do not depend on an [Evaluation Assurance Level (EAL)](./EvaluationAssuranceLevel.md), i.e., they do not differ in rigour and depth with increasing EAL. TOE evaluations, however, are typically tied to a selected EAL. For example, the components of the AVA_VAN Vulnerability Analysis assurance family are levelled based on an inscreasing rigour of vulnerability analysis and consideration of increased levels of [attack potential](./AttackPotential.md). This is immediately reflected in the EALs such that with increasing EAL a higher levelled component is selected to be evaluated.
+
+Vulnerabliity Analysis Component | EAL Level
+--- | ---
+AVA_VAN.1 | EAL 1
+AVA_VAN.2 | EAL 2, EAL 3
+AVA_VAN.3 | EAL 4
+AVA_VAN.4 | EAL 5
+AVA_VAN.5 | EAL 6, EAL 7
+
+### The decadent significance of EAL
+
+Recent renovations in PP generation show that PPs do not claim EALs and assurance is rather gained by custom assurance/evaluation activities developed as part of the PP for the given TOE. In particular, NIAP does not recognize evaluation according to an EAL but only evaluation against a NIAP-approved technology-specific PP. With the release of CC2022 and the framework for the specification of evaluation methods and activities specified in Part 4, the CC supports this new notion.
+
+Concurrently, the EUCC scheme foresees recognition of two distinct assurance levels 'substantial' and 'high', both tied to Vulnerability Assessment Levels (VALs) (corresponding to the component levels) of the AVA_VAN family instead of EALs. The respective assurance level for a VAL is attained if all dependencies of the selected level are satisfied during evaluation. In concrete terms, for a VAL 3 corresponding to an assurance level of 'substantial', the following assurance components must be considered:
+
+AVA_VAN Component | Dependent Components
+--- | ---
+AVA_VAN.3 | ADV_FSP.3,
+| | ADV_FSP.4,
+| | AGD_PRE.1,
+| | ALC_TAT.1,
+| | ATE_FUN.1,
+| | ADV_IMP.1,
+| | ADV_ARC.1,
+| | ATE_COV.1,
+| | ADV_TDS.2,
+| | ADV_TDS.3,
+| | AGD_OPE.1,
+| | ATE_DPT.1
+
+However, the EUCC still prefers that all assurance components of the EAL that is associated with the selected VAL are applied. Where an VAL is associated with multiple EALs either EAL may be chosen, though it is still possible to choose an even lower EAL (>=lowest associated EAL-2). The resulting assurance level is treated as an augmentation of the chosen EAL. Augmentation is also no longer indicated by a “+” sign, instead all added assurance components are listed. Still, the EAL level is no longer of immediate importance, since the CSA assurance level no longer depends on it.
+
+### Evaluation Output Task
+
+Evaluators engage in two core sub-tasks to satisfy the documentation and reporting requirements:
+
+- **Write OR Sub-Task:** This involves creating an Observation Report, which is performed as required to request clarification or to identify a problem, see [Observation Report](./ObservationReport.md)
+- **Write ETR Sub-Task:** The Evaluation Technical Report must be compiled, serving as a detailed documentation of the evaluation results, see [Evaluation Technical Report](./EvaluationTechnicalReport.md)
+
+### Evaluation Verdict
+
+Evaluator action elements are assigned a verdict after performing the corresponding evaluation action and its constituent work units. A verdict, in this context, represents the outcome of the evaluation, indicating whether the element being evaluated has passed, failed, or requires further investigation (inconclusive). An evaluator action element can only be assigned the pass verdict if and only if the constituent Work Units and all evaluation evidence required are coherent, can be fully and completely understood and have no apparent (internal) inconsistencies with other evaluation evidence. All verdicts are initially inconclusive and remain so until either a pass or fail verdict is assigned. The overall verdict is pass, if and only if all the constituent verdicts are also pass.
+
+### Demonstration of Technical Compotence Task
+
+COMING SOON
+
+## Additional Resources
+
+- **Common Criteria Part 3 and Part 4**
+- **Common Evaluation Methodology (CEM)**
+- **European Cybersecurity Certification (EUCC) scheme**
+- **[NIAP Certification compared to EAL Certification](https://www.blackbox.co.uk/gb-gb/page/45890/Resources/Technical-Resources/Black-Box-Explains/KVM/NIAP-Certification-vs-EAL-Certification-for-Security-Testing)**
+
+## Related Articles
+
+- [Single Assurance Evaluation](./SingleAssuranceEvaluation.md)
+- [Multi Assurance Evaluation](./MultiAssuranceEvaluation.md)
+- [Composite Evaluation](./CompositeEvaluation.md)
+- [Observation Report](./ObservationReport.md)
+- [Evaluation Technical Report](./EvaluationTechnicalReport.md)
+- [Security Assurance Component](./SecurityComponent.md)
+- [Security Assurance Requirement](./SecurityAssuranceRequirement.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/EvaluationTechnicalReport.md b/c5dec/assets/database/KnowledgeBase/EvaluationTechnicalReport.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/Exactconformance-FAQ.md b/c5dec/assets/database/KnowledgeBase/Exactconformance-FAQ.md
new file mode 100644
index 0000000..d9f7940
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Exactconformance-FAQ.md
@@ -0,0 +1,69 @@
+# Exact conformance - FAQ
+
+The table below gives a summary of frequently asked questions about the exact confromance case.
+
+ ----------------------------------------------------------------------------------------------------------------------------------
+ PP-Configuration Allowed/Required
+ ---------------------------------------------------------------------------------------------- -----------------------------------
+ Can be used in multi-assurance - modular PP-Configuration Yes
+
+ Can be used in single-assurance - modular PP- Configuration Yes
+
+ Can mix EC with strict/demonstrable conformance types No
+
+ Other EC PPs allowed in EC PP-Configuration Yes
+
+
+
+ **EC PP**
+
+ Optional/Selection-based SFRs in EC PP Yes
+
+ Additional SPD elements associated with optional SFRs Yes
+
+ EC PP claim conformance to another EC PP? (Chained) No
+
+ Other EC PPs allowed in EC PP-Configuration Yes
+
+ PP build upon strict or demonstrable PP? No
+
+ Can be used in strict or demonstrable PP-Configuration? No
+
+ States which other EC PPs are "Allowed-with" Yes
+
+ States which other EC PP-Modules are "Allowed-with" Yes
+
+
+
+ **EC PP-Modules**
+
+ Optional/Selection-based SFRs in EC PP-Module Yes
+
+ EC PP-Module doesn't include components in its PP-Module Base in its allowed-with statement. Yes
+
+ States other EC PPs and PP-Modules are allowed-with Yes
+
+ All Allowed-with items also EC Yes
+
+
+
+ **EC functional Packages**
+
+ Optional/Selection-based SFRs allowed in EC functional Package Yes
+
+ Functional packages can be augmented in the ST No
+
+ Are claimed in a ST conformance claim No
+
+
+
+ **EC STs**
+
+ Contains the SPD of all EC PPs, and/or PP-Configuration components Yes
+
+ Additional or hierarchically higher security requirements? No
+
+ Includes only those selection-based requirements that have been selected Yes
+
+ Can be used with Direct Rationale approach Yes
+ ----------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/ExtendedComponentDefinition.md b/c5dec/assets/database/KnowledgeBase/ExtendedComponentDefinition.md
new file mode 100644
index 0000000..3dc2c76
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/ExtendedComponentDefinition.md
@@ -0,0 +1,108 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC 2022
+Tags: [Extended Components, Extended Security Requirements]
+---
+
+# Extended Component Definition
+
+**Acronym:** ECD
+
+Extended Components play a pivotal role in instances where the existing [security functional](./SecurityComponent.md) or [assurance components](./SecurityComponent.md), catalogued in the CC, do not adequately or accurately encapsulate the specific requirements of a particular [TOE](./TargetofEvaluation.md). In simpler terms, when a [Protection Profile (PP)](./ProtectionProfile.md) or [Security Target (ST)](./SecurityTarget.md) confronts a scenario where the [Security Objectives](./SecurityObjective.md) are not completely addressed by the pre-established components in the CC, the definition of Extended Components is required.
+
+Purposefully, an Extended Component serves to:
+- **Fill Gaps:** Address and articulate unique or specialized requirements that are not comprehensively covered by existing CC components.
+- **Maintain Rigor:** Ensure that these specialized requirements are subjected to the same level of rigor and structured evaluation as existing components.
+- **Facilitate Tailoring:** Enable the tailoring of PPs and STs to more accurately reflect the security landscape and requisites of specific IT products or systems.
+
+The Extended Component Definition (ECD) serves as a container for all Extended Components defined for a specifc TOE and is documented in a corresponding PP or ST. In that context, the ECD is composed of a **statement of security requirements**, identifying all Extended Security Requirements, and definitions of the Extended Components including theses Extended Security Requirements.
+
+## Practical Guidance
+
+Foremost, it is strongly advised to avoid the definition of Extended Components whenever possible. Instead, [requirement Operations](./Operations.md) should be used to tailor requirements to the specifc needs. Usually, such refinements already resolve the issue when no existing Security Component seems to address a particular Security Objective sufficiently. However, in instances where a refinement does not provide ample resolution, the following guidance may be leveraged to define Extended Components.
+
+### **Part I: Basic Tenets**
+
+1. **Opt for Existing Components**: Explore publicly available PPs and STs for Extended Components that fit your needs. Prioritize utilizing and refining existing components, reserving the definition of Extended Components as a last resort.
+2. **Maintain Consistency**: As required by APE_ECD.1.4C and ASE_ECD.1.4C, ensure alignment with existing CC Security Components in style, structure, and abstraction level.
+3. **Measurable and Objective Elements**: Facilitate evaluatability by establishing measurable and objective requirements (APE_ECD.1.5C and ASE_ECD.1.5C)
+
+### **Part II: Formulating Extended Security Functional Requirements (SFRs)**
+
+1. **Abstraction Level Adherence**: Preserve a level of abstraction commensurate with ISO/IEC 15408-2 components.
+2. **Consistent Style and Phraseology**: Maintain terminological and phraseological consistency, starting functional requirements, for instance, with phrases like “The TSF shall”.
+3. **Topological and Nomenclatural Consistency**: Align with ISO/IEC 15408-2 for topology and naming, see Part IV
+4. **Application Notes**: Provide application notes in PPs or STs to clarify the usage of the extended component.
+
+### **Part III: Developing Extended Security Assurance Requirements (SARs)**
+
+1. **Defining Actions**: Outline actions for developers and evaluators, ensuring that the former focuses on producing necessary evaluation evidence, while the latter verifies product conformity.
+2. **Precise Evidence Requirements**: Establish clear parameters for the content and presentation of developer evidence.
+3. **Objective Criteria**: Articulate SARs to offer unequivocal, objective criteria, minimizing the need for subjective evaluator judgement.
+4. **Defining Evaluator Work Units for SARs:**
+ - **Structural Consistency with ISO/IEC 18045**: Emulate the structure of work units from ISO/IEC 18045 when defining evaluator work units to demonstrate compliance.
+ - **Addressing All Aspects**: Ensure work units comprehensively address all facets of the extended assurance component.
+ - **Clear Guidance**: Provide unequivocal instructions on assessment execution to evaluators.
+
+### **Part IV: Practical Considerations**
+
+- **Promoting Reusability**: Strive for generic extended components, which allow for operations like [assignment](./Operation-Assignment.md) or [selection](./Operation-Selection.md), enhancing reusability across contexts.
+- **Naming Convention**:
+
+ [Type Identifier: F|A][Class Acronym: 2 characters]_[Family Acronym: 3 characters].[Component Number].[Element Number]
+
+
+### Example: CC PP Cryptographic Module, Security Level "High" BSI-PP-0042
+
+This Protection Profile was released in 2008 and claims conformance to CC version 2.3. It is immediately apparent just based on the Acronym that the defined Family is considered to be an extension of the Functional Class FCS: Cryptographic Support.
+
+#### Definition of the Family FCS_RNG
+
+**Family behaviour**
+
+This family defines requirements for the generation random number where the random
+numbers are intended to be used for cryptographic purposes. The requirements address the
+type of the random number generator as defined in AIS 20/315 and quality of the random
+numbers.
+
+**Component levelling:**
+
+FCS_RNG.1 Generation of random numbers requires that random numbers meet a defined quality metric.
+
+*Management:* FCS_RNG.1 There are no management activities foreseen.
+
+*Audit:* FCS_RNG.1 There are no actions defined to be auditable.
+
+**FCS_RNG.1 Random number generation**
+
+Hierarchical to: No other components.
+
+Dependencies: FPT_TST.1.
+
+FCS_RNG.1.1
+
+The TSF shall provide a [selection: physical, non-physical true,
+deterministic, hybrid] random number generator that meet [assignment:
+list of security capabilities].
+
+FCS_RNG.1.2
+
+The TSF shall provide random numbers that meet [assignment: a defined
+quality metric].
+
+
+## Additional Resources
+
+- **Common Criteria Part 1-3**
+- **Common Evaluation Methodology**
+- **ISO/IEC TR 15446**
+- **[The Common Criteria Portal](https://commoncriteriaportal.org/pps/)**
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
+- [Security Components](./SecurityComponent.md)
+- [Security Functional Requirements](./SecurityFunctionalRequirement.md)
+- [Security Assurance Requirements](./SecurityAssuranceRequirement.md)
+- [Requirement Operations](./Operations.md)
diff --git a/c5dec/assets/database/KnowledgeBase/MultiAssuranceEvaluation.md b/c5dec/assets/database/KnowledgeBase/MultiAssuranceEvaluation.md
new file mode 100644
index 0000000..b03d8ae
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/MultiAssuranceEvaluation.md
@@ -0,0 +1,11 @@
+---
+Last Updated: October 11, 2023
+Relevant: CC2022
+Tags: [Multi Assurance Evaluation]
+---
+
+# Multi Assurance Evaluation
+
+**Acronym:**
+
+In contrast to the [single assurance evaluation](./SingleAssuranceEvaluation.md), the multi assurance evaluation considers a global set of [SARs](./SecurityAssuranceRequirement.md) to apply to the entire [TOE](./TargetofEvaluation.md), while sets of SARs apply to individual [sub-TSFs](./SubTOESecurityFunctionality.md). In order to ensure that the set of SARs associated with a sub-TSF does not impact other sub-TSFs, multi assurance evaluations require an assurance rationale to demonstrate the consistency of the sets of SARs.
diff --git a/c5dec/assets/database/KnowledgeBase/NonBypassability.md b/c5dec/assets/database/KnowledgeBase/NonBypassability.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/NonTSFPart.md b/c5dec/assets/database/KnowledgeBase/NonTSFPart.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/ObservationReport.md b/c5dec/assets/database/KnowledgeBase/ObservationReport.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/Operation-Assignment.md b/c5dec/assets/database/KnowledgeBase/Operation-Assignment.md
new file mode 100644
index 0000000..838b80f
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Operation-Assignment.md
@@ -0,0 +1,16 @@
+# Operation - Assignment
+
+**Acronym:** None
+
+An assignment operation occurs where a given [security requirement](./SecurityRequirement.md) contains an element with a parameter that may be set by the author. The parameter may be an unrestricted variable, or a rule that narrows the variable to a specific range of values.
+Whenever an element in a [PP](../CoreConstructs/ProtectionProfile.md), [PP-Module](./PP-Module.md) or [Package](./Package.md) within a PP/PP-Module contains an assignment, the author shall do one of four things:
+1. leave the assignment uncompleted;
+2. complete the assignment;
+3. narrow the assignment to further limit the range of values that is allowed;
+4. transform the assignment to a selection, thereby narrowing the assignment."
+
+An [ST](./SecurityTarget.md) author shall complete all the assignments.
+The values chosen in options 2., and 4. shall conform to the indicated type required by the assignment.
+When an assignment is to be completed with a set, an author should provide a description of the set from which the elements of the set may be derived as long as it is clear which subjects are meant.
+
+**Note** - for the completion of assignments, the CC Part 2 annexes shall be consulted in order to determine when "None" would be a valid completion.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/Operation-Iteration.md b/c5dec/assets/database/KnowledgeBase/Operation-Iteration.md
new file mode 100644
index 0000000..ee7004f
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Operation-Iteration.md
@@ -0,0 +1,8 @@
+# Operation - Iteration
+
+**Acronym:** None
+
+The iteration operation may be performed on every [component](./SecurityComponent.md). The author performs an iteration operation by including multiple [requirements](./SecurityRequirement.md) based on the same component. Each iteration of a component shall be different from all other iterations of that component, which is realized by completing [assignments](Operation-Assignment.md) and [selections](Operation-Selection.md) in a different way, or by applying [refinements](Operation-Refinement.md) to it in a different way.
+Different iterations shall be uniquely identified to allow clear [rationales](./Rationale.md) and tracings to and from these requirements. Iteration identifiers should be meaningful to readers.
+
+**NOTE** - Sometimes an iteration operation can be used with components where it is also possible to perform an assignment operation with a range or list of values instead of iterating them. In that case, the author can select the most appropriate alternative, considering if there is a necessity of providing a whole rationale for the range of values or if it is necessary to have a separate one for each of them. The author considers if individual traces are required for those values.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/Operation-Refinement.md b/c5dec/assets/database/KnowledgeBase/Operation-Refinement.md
new file mode 100644
index 0000000..2b93a55
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Operation-Refinement.md
@@ -0,0 +1,14 @@
+# Operation - Refinement
+
+**Acronym:** None
+
+The refinement operation may be performed on every [requirement](./SecurityRequirement.md). The author performs a refinement by altering that requirement.
+
+**NOTE 1** A series of refined iteration operations can be used to cover all of the subjects, objects, operations, security attributes and/or external entities, but where each individual refinement does not.
+
+The first rule for a refinement is that a [TOE](TargetofEvaluation.md) meeting the refined requirement also meets the unrefined requirement in the context of the [PP](./ProtectionProfile.md), [PP-Module](./PP-Module.md), [Package](./Package.md) or [ST](./SecurityTarget.md), i.e. a refined requirement shall be "stricter" than the original requirement. If a refinement does not meet this rule, the resulting refined requirement is considered to be an [extended requirement](ExtendedSecurityRequirement.md) and shall be treated as such.
+
+The only exception to this rule is that an author can refine a [SFR](SecurityFunctionalRequirement.md) to apply to some but not all subjects, objects, operations, security attributes and/or external entities. However, this exception does not apply to refining SFRs that are taken from PPs, PP-Modules or package to which [conformance](./ConformanceClaims.md) is being claimed; these SFRs shall not be refined to apply to fewer subjects, objects, operations, security attributes and/or external entities than the SFR in the originating PP, PP-Module or package.
+
+The second rule for a refinement is that the refinement shall be related to the original [component](./SecurityComponent.md).
+A special case of refinement is an editorial refinement, where a small change may be made in a requirement, i.e. rephrasing a sentence due to adherence to proper English grammar, or to make it more understandable to the reader. This change is not allowed to modify the meaning of the requirement in any way.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/Operation-Selection.md b/c5dec/assets/database/KnowledgeBase/Operation-Selection.md
new file mode 100644
index 0000000..6d3bd71
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Operation-Selection.md
@@ -0,0 +1,15 @@
+# Operation - Selection
+
+**Acronym:** None
+
+The selection operation occurs where a given [component](./SecurityComponent.md) contains an element where a choice from several items has to be made by the author.
+Whenever an element in a [PP](./ProtectionProfile.md), [PP-Module](./PP-Module.md) or[Package](./Package.md) contains a selection, the author may do one of three things:
+1. leave the selection uncompleted;
+2. complete the selection by choosing one or more items;
+3. restrict the selection by removing some of the choices but leaving two or more.
+Whenever an element in a PP, PP-Module or package contains a selection, a [ST](./SecurityTarget.md) author shall complete that selection, as indicated in 2. above. Options 1. and 3. are not allowed for STs.
+The item or items chosen in 2. and 3. shall be taken from the items provided in the selection.
+
+**Note** - "None" is only available as a choice for the completion of a selection if explicitly provided;
+The lists provided for the completion of selections shall be non-empty. If a "None" option is chosen, no additional selection options may be chosen. If "None" is not given as an option in a selection, it is permissible to combine the choices in a selection with "and"s and "or"s, unless the selection explicitly states "choose one of".
+Selection operations may be combined by iteration where needed. In this case, the applicability of the option chosen for each iteration should not overlap the subject of the other iterated selection, since they are intended to be exclusive.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/Operations.md b/c5dec/assets/database/KnowledgeBase/Operations.md
new file mode 100644
index 0000000..c437232
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Operations.md
@@ -0,0 +1,10 @@
+# Operations
+
+**Acronym:** None
+
+CC allows the modification of [SFRs](SecurityFunctionalRequirement.md) and [SARs](SecurityAssuranceRequirement.md) by applying operations. The permitted operations are selected from the following set:
+- [Iteration](Operation-Iteration.md): allows a component to be used more than once with varying operations;
+- [Assignment](Operation-Assignment.md): allows the specification of parameters;
+- [Selection](Operation-Selection.md): allows the specification of one or more items from a list; and
+- [Refinement](Operation-Refinement.md): allows the addition of details.
+The assignment and selection operations are permitted only where specifically indicated in a security requirement. Iteration and refinement are permitted for all security requirements.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/OrganizationalSecurityPolicy.md b/c5dec/assets/database/KnowledgeBase/OrganizationalSecurityPolicy.md
new file mode 100644
index 0000000..c633cd7
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/OrganizationalSecurityPolicy.md
@@ -0,0 +1,32 @@
+# Organizational Security Policy
+
+**Acronym:** OSP
+
+Organizational Security Policy (OSP) within the Common Criteria framework is a fundamental construct, defined as a set of security rules, procedures, or guidelines for an organization. Embedded within the [Security Problem Definition (SPD)](./SecurityProblemdefinition.md) of both [Protection Profiles (PP)](./ProtectionProfiles.md) and [Security Targets (ST)](./SecurityTarget.md) to enforce compliance, mitigate potential threats, and ensure the protection of assets within a specified operational environment. Within the CC paradigm, OSPs are not merely declarative; they are enforced through defined [security objectives](./SecurityObjective.md) that are shouldered by the [Target of Evaluation (TOE)](./TargetofEvaluation.md), its [operational environment](./TOEOperationalEnvironment.md), or synergistically by both.
+
+## Practical Guidance
+
+While OSPs might initially be identified during the informal security requirement definition or threat analysis phases, a detailed revisit ensures that every relevant policy, whether mandating specific security functions, prescribing certain technologies, or strategically replacing threats, is encapsulated comprehensively within the Security Problem Definition (SPD).
+
+**1. Leveraging Existing Organizational Policies:**
+ Begin by exploring the existing set of security policies established within the organization. Assess their applicability and pertinence to the TOE. Where these pre-established policies align with TOE’s functionality and operational environment, tailor them accordingly to befit the specific requirements and contexts of the TOE under evaluation. This approach ensures that the OSPs formulated are not only aligned with organizational strategies and norms but are also tailored to effectively navigate the specific security contours and requirements of the TOE.
+
+**2. Policy Specification:**
+ Specify policies with a clear focus on mandatory security functions or technologies/techniques, ensuring they are directly tied to the TOE and its integral security functions.
+
+**3. Threat Replacement Consideration:**
+ Evaluate whether policies should replace threats based on certainty, pre-existing policy decisions about threat management, and the strategic approach to countering related threats.
+
+**4. Articulation into Security Objectives:**
+ Ensure that OSPs, which denote mandatory security functions or requisite technologies/techniques, are translated into actionable security objectives in the Security Target (ST) or Protection Profile (PP). These objectives should offer a clear, solution-oriented representation, elucidating how the TOE will concretely adhere to or implement the stipulated security functions and technologies elucidated in the OSPs.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** This technical report provides a methodical approach to creating an SPD, guiding users through the identification of informal security requirements, threats, policies, and assumptions.
+- **ISO/IEC 27001:** Guidelines on establishing, implementing, maintaining, and continuously improving an information security management system.
+- **NIST SP 800-53:** Guidance on security and privacy controls for federal information systems and organizations.
+
+## Related Articles
+
+- [Security Problem Definition](./SecurityProblemdefinition.md)
+- [Security Objectives](./SecurityObjectives)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/PPConfiguration.md b/c5dec/assets/database/KnowledgeBase/PPConfiguration.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/ProtectionProfile.md b/c5dec/assets/database/KnowledgeBase/ProtectionProfile.md
new file mode 100644
index 0000000..516fa15
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/ProtectionProfile.md
@@ -0,0 +1,59 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: CC2022
+---
+
+# Protection Profile
+
+**Acronym:** PP
+
+A Protection Profile is typically a statement of need where a user community, a regulatory entitiy, or a group of developers define a common set of security needs. A PP gives consumers a menas of referring to this set and facilitates future evaluation against these needs.
+Although this does not preclude other uses, a PP is typically used as:
+- part of a requirement specification for a specific consumer or group of consumers, who will only consider buying a specific type of IT product if it meets the PP;
+- part of a regulation from a specific regulatory entity, who will only allow a specific type of IT product to be used if it meets the PP;
+- to address a common security problem presented by a variety of consumers, and often defined by a group including several IT product developers, who then produce IT products of this type in order to meet the needs of their common market.
+
+Two types of PPs:
+- [Single-assurance Evaluation](./Single-assuranceEvaluation.md): evaluation of a TOE using one set of [assurance requirements](./SecurityAssuranceRequirement.md)
+- [Multi-assurance Evaluation](./Multi-assuranceEvaluation.md): evaluation of a TOE using a PP-Configuration where each PP-Configuration component is associated with its own set of assurance requirements.
+
+PPs can be defined using the [direct rationale](./DirectRationale.md) approach or the standard approach.
+
+## Collaborative Protection Profiles
+A collaborative Protection Profile (cPP) is a specialized protection profile developed by an international technical community within a particular technical domain. It defines security requirements and an evaluation methodology specific to that domain, allowing for consistent and recognized security evaluations and certifications in that area of expertise. The refined or specifically applicable evaluation methods within the cPP are defined in supporting documents and published individually.
+According to the German certification scheme , certification of a product according to a cPP under the recognition of the CCRA must maintain exact conformance. This means that the security requirements for the product certification process should not deviate from the cPP, neither in terms of functional security requirements nor testing requirements, even if the IT product provides higher security performance. In addition, the CCRA Supporting Documents associated with the cPP, which refine the evaluation methodology of the CEM in a technology-specific manner, must be applied. These documents can be found on the Common Criteria portal under the section "Collaborative PPs." Security features that go beyond the scope of the cPP can be granted in a second certificate as part of the same evaluation process, using the Re-Use processes. This certificate is either not recognized by the CCRA or is not compliant with the cPP and is recognized by the CCRA up to EAL 2.
+
+## Practical Guidance
+
+COMING SOON.
+
+## Document Outline
+
+1. [PP Introduction]
+ 1. PP Reference
+ 2. [TOE Overview](./TOEOverview.md)
+2. [Conformance Claims](./ConformanceClaim.md)
+ 1. CC Claim
+ 2. Package Claim
+ 3. PP Claim
+ 4. Conformance Claim rationale
+ 1. TOE Type consistency
+ 2. SPD Consistency
+ 3. SO Consistency
+ 4. SR Consistency
+3. [Conformance Statement](ConformanceStatement.md)
+ 1. [Allowed-with Statement]
+ 2. [Evaluation Methods](./EvaluationMethods.md)
+4. [Security Objectives](./SecurityObjective.md)
+ 1. [Security Objectives for the TOE]
+ 2. [Security Objectives for the Operational Environment]
+ 3. [Security Objectives Rationale](./Rationale.md)
+4. [Extended Component Definition](./ExtendedComponentDefinition.md)
+5. Security Requirements
+ 1. [Security Functional Requirements](./SecurityFunctionalRequirement.md)
+ 2. [Security Assurance Requirements](./SecurityAssuranceRequirement.md)
+ 3. [Security Requirements Rationale](./Rationale.md)
+
+## Document Template
+
+COMING SOON.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/Rationale.md b/c5dec/assets/database/KnowledgeBase/Rationale.md
new file mode 100644
index 0000000..8477969
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Rationale.md
@@ -0,0 +1,22 @@
+CC Part 1 section A.7.3 states that "a security objectives rationale [contains] two
+sections:
+- a tracing that shows which security objectives address which threats, OSPs
+and assumptions;
+- a set of justifications that shows that all threats, OSPs, and assumptions are
+effectively addressed by the security objectives.”
+210 The first one is best addressed by a table, having the threats, OSPs and assumptions
+on the rows, and the security objectives on the column, and "X" marking a place in
+the table if that security objective traces to that threat, OSP or assumption. Its
+purpose is to show that:
+- Each security objective traces to at least one threat, OSP or assumption. In
+other words, each column has to have at least one "X" in it.
+- Each threat, OSP and assumption has at least one security objective tracing to
+it. In other word, each row has to have at least one "X" in it.
+- Assumptions can only be traced to by security objectives for the operational
+environment.
+
+The second one is slightly harder. For each threat and OSP, you have to describe
+HOW the security objectives counter/meet it. If you have done the analysis
+prescribed by the explanation method, this can be derived from that analysis, as all
+the elements that are needed are there. They just need to be collected and described
+in a short, to-the-point, and understandable way.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityAssuranceRequirement.md b/c5dec/assets/database/KnowledgeBase/SecurityAssuranceRequirement.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityComponent.md b/c5dec/assets/database/KnowledgeBase/SecurityComponent.md
new file mode 100644
index 0000000..8bb0041
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/SecurityComponent.md
@@ -0,0 +1,63 @@
+---
+Last Updated: October 4, 2023
+Relevant: CC Version 3.1 Revision 5, CC 2022
+Tags: [Security Components, Classes, Families, Components, Elements, Security Functional Component, Security Assurance Component, Extended Components, Security Requirements, Security Functional Requirements, Security Assurance Requirements, Extended Security Requirements]
+---
+
+# Security Components
+
+**Acronym:** None
+
+The Common Criteria provides a catalogues of security components that serve as the structural foundation for specifying security requirements. These are organized in a hierarchical structure with four levels:
+- Classes, consisting of
+- Families, consisting of
+- Components, consisting of
+- Elements.
+
+Security Components are categorized as Security Functional Components and Security Assurance Components for which the Common Criteria provides individual catalogues, CC Part 2 and CC Part 3, respectively. Although, both component categories share the same hierarchical structure their content slightly differs. Below a side by side comparison.
+
+Hierarchical level | Security Functional Component | Security Assurance Component
+--- | --- | ---
+Class | Class Name, Class Introduction, Functional Families | Class Name, Class Introduction, Assurance Families
+Family | Family Name, Family Behaviour, Components Levelling and Description, Management, Audit, Functional Components | Family Name, Objectives, Component Levelling, Application Notes, Assurance Components
+Component | Component Identification, Dependencies, Functional Elements | Component Identification, Objectives, Application Notes, Dependencies, Assurance Elements
+Element | Element Identification, Functional Requirement | Element Identification, Element Type (Developer Action, Content and Presentation, Evaluator Action), Assurance Requirement
+
+Dependencies between components may exist if the component is not self-sufficient and relies upon the presence of another component to provide security functionality or assurance. Dependencies also include hierarchical relationships between components, i.e., that a component A that is hierarchical to component B, supersedes component B.
+
+## Security Functional Components
+
+Security Functional Components (SFCs) within the Common Criteria framework offer a methodologically robust and structured means to navigate the derivation and definition of [Security Functional Requirements (SFRs)](./SecurityFunctionalRequirement.md). Navigated through the hierarchical structure (Class > Family > Component > Element), SFCs facilitate a seamless, top-down progression from generalized security themes to nuanced, explicit functional requirements. Concurrently, this path facilitates the translation of [security objectives](./SecurityObjective.md), which are explicit responses to identified [threats](./Threat.md) and [policies](./OrganizationalSecurityPolicy.md), into tangible, evaluable security functions of a [Target of Evaluation (TOE)](./TargetofEvaluation.md) posing as concrete solutions to the identified [Security Problem](./SecurityProblemdefinition.md). Moreover, this hierarchical structure, while grounding SFRs in an established taxonomy, also provides the necessary scaffold to define user-specific Extended Components, ensuring the SFC's relevance and applicability across varied security contexts and TOEs. This marriage of structured, hierarchical standardization and flexible, tailored applicability underscores the pivotal role of SFCs in enabling, expressing, and validating the security posture of TOEs within the broader CC evaluation landscape.
+
+## Security Assurance Components
+
+Security Assurance Components (SACs) establish a systematic approach to validate the trustworthiness and efficacy of the security functions enacted by a TOE. Whereas Security Functional Components facilitate the definition and expression of security functions, SACs ensure that these are effectively enacted and verifiable, providing a reliable metric to gauge the TOE’s security posture against its claimed functionalities. These components assure that security functionalities, articulated through **Security Functional Requirements** are not only logically coherent but also practically viable and effective in mitigating identified [threats](./Threat.md) and aligning with [organizational security policies](./OrganizationalSecurityPolicy.md), thereby fulfilling Security Objectives.
+In contrast to SFCs, at the terminus of SACs hierarchical structure, three distinct assurance elements emerge that collectively represent a [Security Assurance Requirement](./SecurityAssuranceRequirement.md):
+
+- **Developer Action Elements** provide explicit instructions and expectations to developers to ensure security functionality is implemented and verified during development.
+- **Content and Presentation Elements** dictate the manner and substance of how the developers should present the evaluation evidence, ensuring coherence, and relevancy to the evaluator.
+- **Evaluator Action Elements** provide a methodological baseline for the evaluators, guiding them on how to verify the evidence presented against the TOE’s claimed security functionality.
+
+Moreover, SACs intrinsically intertwine with [Evaluation Methods and Activities](./EvaluationMethod.md), thereby establishing a symbiotic relationship that streamlines the TOE evaluation process. Particularly, Evaluator Action Elements serve as a nexus, directly linking SACs with Evaluation Methods through the specification of [Evaluation Actions](./EvaluationMethod.md) and corresponding [Work Units](./EvaluationMethod.md). These Work Units, which are either explicitly defined for Content and Presentation Elements or implicitly for Developer Action Elements, are paramount as they concretely delineate the evaluator's task.
+
+In a manner akin to SFCs, SACs also facilitate the provision for Extended Components, enabling adaptability and relevance across multifaceted security landscapes and diverse TOEs.
+
+## Extended Components
+
+For Security Objectives that cannot be translated or only with great difficulty and/or complexity to SFRs using components defined in CC Part 2, or if there are third party requirements that cannot be translated to SARs using component in CC Part 3, new components can be defined. These components are referred to as Extended Components and provide context and meaning to allow the derivation and definition of Extended Security Requirements. Extended Components are evaluated against the [Extended Components Definition](./ExtendedComponentDefinition.md) (APE_ECD) and (ASE_ECD) assurance families (see CC Part 3) to determine their necessity, clearness, and unambiguity.
+
+## Additional Resources
+
+- **Common Criteria Part 1-3**
+- **Common Evaluation Methodology**
+- **ISO/IEC TR 15446**
+
+
+## Related Articles
+
+- [Security Functional Requirements](./SecurityFunctionalRequirement.md)
+- [Security Assurance Requirements](./SecurityAssuranceRequirement.md)
+- [Extended Component Definition](./ExtendedComponentDefinition.md)
+- [Evaluation Methods and Activities](./EvaluationMethod.md)
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityFunctionalRequirement.md b/c5dec/assets/database/KnowledgeBase/SecurityFunctionalRequirement.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityObjective.md b/c5dec/assets/database/KnowledgeBase/SecurityObjective.md
new file mode 100644
index 0000000..a48e7a6
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/SecurityObjective.md
@@ -0,0 +1,48 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Security Objective
+
+**Acronym:** SO
+
+Security Objectives, within the context of the Common Criteria (CC), articulate the overarching security actions or attributes that are required to counter identified [threats](./Threat.md) and comply with defined [OSPs](./OrganizationalSecurityPolicy.md), as well as uphold any [assumptions](./Assumption.md) that are outlined in the [SPD](./SecurityProblemdefinition.md). Essentially, they translate the security problems into security solutions, expressed in a high-level, solution-oriented language.
+
+Security Objectives are separated into two categories:
+
+- **Security Objectives for the TOE:** These lay out what the [TOE](./TargetofEvaluation.md) itself must achieve to mitigate the identified threats and adhere to OSPs.
+- **Security Objectives for the Operational Environment:** These detail what needs to be achieved within the [TOE’s operational environment](./TOEOperationalEnvironment.md) to support the TOE in countering threats, adhering to OSPs, and maintaining assumptions.
+
+Each security objective should be traceable back to one or more elements of the SPD, ensuring that all identified security issues are being addressed. This traceability is typically captured in the [Security Objective Rationales](./Rationale.md), which demonstrate that the stated objectives are well-founded and suitable to address the identified security problems Moreover, they help define the [Security Functional Requirements (SFRs)](./SecurityFunctionalRequirement.md) and [Security Assurance Requirements (SARs)](./SecurityAssuranceRequirement.md) by providing a conceptual basis for what is required from the TOE and its operational environment in practical, implementable terms.
+
+In the development of a [Security Target (ST)](./SecurityTarget.md) or a [Protection Profile (PP)](./ProtectionProfile.md), security objectives serve to bridge the gap between the high-level security issues defined in the SPD and the detailed requirements that will be applied during the evaluation of the TOE.
+
+## Practical Guidance
+
+1. **Identify the What, Not the How:** Clearly understand that security objectives should articulate what needs to be achieved, not how to achieve it. Ensure they are implementation-independent and don't mirror SFRs or simply restate SPD elements.
+2. **Bridge the Gap:** Establish security objectives as a medium between the threats/OSPs and the semi-formalized model of SFRs, ensuring that they are set at an abstraction level that translates high-level security issues into actionable objectives.
+3. **In-depth Understanding of the TOE:** Answer key questions, such as:
+ - Where will the TOE be placed, and is it susceptible to physical attacks?
+ - What is the principal purpose of the TOE?
+ - How will the TOE be managed?
+4. **Mitigation and Addressal:** Derive security objectives that concretely address identified threats and comply with OSPs. Ensure each security objective is traceable back to one or more elements in the SPD and that they collectively cover all aspects of the SPD.
+5. **Iterative Refinement:** Engage in an iterative process between the security objectives, SFRs, and SPD to ensure all three components align perfectly and that the objectives aptly bridge the SPD and SFRs.
+6. **Rationale Development:**
+ - Ensure that all security objectives are mutually consistent and collectively exhaustive in addressing all elements of the SPD without unnecessary overlaps or gaps.
+ - Formulate a security objectives rationale that clearly demonstrates how each objective addresses specific threats, policies, and assumptions from the SPD. Ensure traceability and logical coherency in the rationale.
+
+
+## Additionoal Resources
+- **ISO/IEC TR 15446:** This technical report provides a methodical approach to creating an SPD, guiding users through the identification of informal security requirements, threats, policies, and assumptions.
+- [**BSI - The PP/ST Guide, Version 2.0**](https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zertifizierung/Interpretationen/AIS_41_BSI_PP_ST_Guide_pdf.pdf?__blob=publicationFile&v=1)
+- [**Cybersecurity Certification: Candidate EUCC Scheme**](https://www.enisa.europa.eu/publications/cybersecurity-certification-eucc-candidate-scheme)
+- [**Cybersecurity Act (CSA) - Article 51**](https://lexparency.org/eu/32019R0881/ART_51/)
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
+- [Security Problem Definition](./SecurityProblemdefinition.md)
+- [Rationale Definition](./Rationale.md)
+
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityProblemdefinition.md b/c5dec/assets/database/KnowledgeBase/SecurityProblemdefinition.md
new file mode 100644
index 0000000..a6cae3e
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/SecurityProblemdefinition.md
@@ -0,0 +1,50 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Security Problem Definition
+
+**Acronym:** SPD
+
+The **Security Problem Definition** (SPD) stands as a pivotal component within each [Protection Profile](./ProtectionProfile.md) and [Security Target](./SecurityTarget.md), anchoring the foundational understanding of the security context in which the [TOE](./TargetofEvaluation.md) operates. It rigorously elucidates the security challenges that the TOE seeks to navigate and provides a structured description of them via the lens of [threats](./Threat.md) to [assets](./Asset.md), adherence to [organizational security policies](./OrganizationalSecurityPolicy.md), and [assumptions](./Assumption.md) pertaining to the [operational environment](./TOEOperationalEnvironment.md).
+
+An effectively constructed SPD not only lends clarity to the evaluative context but also, significantly influences the utility of evaluation results. The CC, while emphasizing the pivotal role of the SPD, abstain from defining a structured process for its derivation, effectively treating the SPD as axiomatic. Nevertheless, ISO/IEC TR 15446, through its Clause 9, proposes a high-level framework that can guide the structuring of an SPD.
+
+## Practical Guidance
+
+Following the high-level framework proposed in ISO/IEC TR 15446, here's a step-by-step guide to deriving an SPD:
+
+1. **Informal Security Requirement Analysis:** Begin by capturing and validating general security needs. This could be through stakeholder interviews, risk assessments, and reviewing existing security documentation.
+2. **Risk and Threat Analysis:** Implement a robust and synchronized risk and threat analysis, ensuring that the identification of threats and the assessment of associated risks are both comprehensive and relevant.
+ - Threat Identification: Detail all conceivable threats related to the TOE, ensuring they are rooted in realistic and relevant scenarios.
+ - Risk Assessment: Evaluate the risks associated with each identified threat, considering both the likelihood of occurrence and the potential impact on assets.
+ - Risk Treatment: Determine how each identified risk will be managed – whether through mitigation, transfer, acceptance, or avoidance, and detail the rationale behind these decisions.
+ - Correlation and Relevance: Establish and document clear links between identified threats and assets, ensuring that the relevance and impact of each threat are clearly defined.
+3. **Policy Documentation:** List and detail any organizational, regulatory, or industry-specific policies that need to be considered for the TOE and its environment.
+4. **Assumption Recording:** Clearly specify any assumptions regarding the TOE's operational environment. These could be about the user base, network conditions, hardware specifications, or even geographical locations.
+5. **SPD Specification Check:** After drafting the SPD, review for completeness, clarity, and relevance. Engage different stakeholders for feedback, ensuring the SPD addresses all their concerns.
+
+## Tips for Beginners
+
+- **Start Broad, Then Narrow Down:** Begin your SPD with a wide perspective, capturing all potential concerns. Later, refine these into specific, actionable items.
+- **Engage Multiple Stakeholders:** Ensuring their concerns and perspectives are considered even in the technical aspects of the SPD.
+- **Stay Updated:** The threat landscape is ever-evolving. Regularly review and update the SPD, especially after significant changes in the organization or industry.
+- Leverage existing SPD examples and templates to guide your initial efforts in crafting an SPD.
+- Work closely with security analysts to understand common threats and to ground your SPD in realistic scenarios.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** This technical report provides a methodical approach to creating an SPD, guiding users through the identification of informal security requirements, threats, policies, and assumptions.
+- **Common Threat Databases:** Websites like the Common Vulnerabilities and Exposures (CVE) can provide insights into prevalent threats and vulnerabilities.
+- [**BSI - The PP/ST Guide, Version 2.0**](https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zertifizierung/Interpretationen/AIS_41_BSI_PP_ST_Guide_pdf.pdf?__blob=publicationFile&v=1)
+- **ENISA Interoperable EU Risk Management Toolbox:**
+
+## Related Articles
+
+- [Protection Profiles and Their Role](./ProtectionProfile.md)
+- [In-depth Exploration of Security Targets](./SecurityTarget.md)
+- [Identifying Threats](./Threat.md)
+- [Organizational Security Policies](./OrganizationalSecurityPolicy.md)
+- [Assumptions](./Assumptions.md)
+- [Threat Modeling](./ThreatModeling.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/SecurityTarget.md b/c5dec/assets/database/KnowledgeBase/SecurityTarget.md
new file mode 100644
index 0000000..9f61d1f
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/SecurityTarget.md
@@ -0,0 +1,60 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: CC2022
+---
+
+# Security Target
+
+**Acronym:** ST
+
+A ST is a document that describes a specific [TOE](./TargetofEvaluation.md), the [conformance claims](./ConformanceClaims.md) applicable to the evaluation of the TOE, the [security problem](./SecurityProblemDefinition.md) to be addressed, the [security objectives](./SecurityObjective.md) for the TOE and its operational environment, the [security requirements](./SecurityRequirement.md) applicable to solving the stated security problem, and additional material necessary to describe the TOE sufficiently for evaluation. STs are generally based upon [PPs](ProtectionProfile.md) or [PP-Configurations](PP-Configuration.md) that describe a security problem and security requirements for a TOE type that is relevant to the specific TOE, but can also be defined as standalone documents.
+A ST is typically produced by a [developer](./DefDeveloper.md) and the audience for the ST includes [evaluators](./DefEvaluator.md), [certifying body](./DefCertificationBody.md) and [end users](./DefEndUser.md) of the evaluated TOE.
+
+STs can be evaluated according to
+- [Single-assurance Evaluation](./Single-assuranceEvaluation.md): evaluation of a TOE using one set of [assurance requirements](./SecurityAssuranceRequirement.md)
+- [Multi-assurance Evaluation](./Multi-assuranceEvaluation.md): evaluation of a TOE using a PP-Configuration where each PP-Configuration component is associated with its own set of assurance requirements.
+
+A ST can either adopt the [direct rationale](./DirectRationale.md) model or the standard model.
+
+
+## Practical Guidance
+
+COMING SOON.
+
+
+## Document Outline
+
+1. [ST Introduction]
+ 1. [ST Reference]
+ 2. [TOE Reference](./TOEReference.md)
+ 3. [TOE Overview](./TOEOverview.md)
+ 4. [TOE Description](./TOEDescription.md)
+2. [Conformance Claims](./ConformanceClaim.md)
+ 1. CC Claim
+ 2. Package Claim
+ 3. PP Claim
+ 4. Conformance Claim rationale
+ 1. TOE Type consistency
+ 2. SPD Consistency
+ 3. SO Consistency
+ 4. SR Consistency
+ 5. [Evaluation Methods](./EvaluationMethods.md)
+3. [Security Problem Definition](./SecurityProblemdefinition.md)
+ 1. [Threats](./Threat.md)
+ 2. [Organizational Security Policies](./OrganizationalSecurityPolicy.md)
+ 3. [Assumptions](./Assumption.md)
+4. [Security Objectives](./SecurityObjective.md)
+ 1. [Security Objectives for the TOE]
+ 2. [Security Objectives for the Operational Environment]
+ 3. [Security Objectives Rationale](./Rationale.md)
+4. [Extended Component Definition](./ExtendedComponentDefinition.md)
+5. Security Requirements
+ 1. [Security Functional Requirements](./SecurityFunctionalRequirement.md)
+ 2. [Security Assurance Requirements](./SecurityAssuranceRequirement.md)
+ 3. [Security Requirements Rationale](./Rationale.md)
+6. [TOE Summary Specification](./TOESummarySpecification.md)
+
+## Document Template
+
+COMING SOON.
+
diff --git a/c5dec/assets/database/KnowledgeBase/SelfProtection.md b/c5dec/assets/database/KnowledgeBase/SelfProtection.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/SingleAssuranceEvaluation.md b/c5dec/assets/database/KnowledgeBase/SingleAssuranceEvaluation.md
new file mode 100644
index 0000000..30b467b
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/SingleAssuranceEvaluation.md
@@ -0,0 +1,11 @@
+---
+Last Updated: October 11, 2023
+Relevant: CC2022
+Tags: [Single Assurance Evaluation]
+---
+
+# Single Assurance Evaluation
+
+**Acronym:** None
+
+The Single Assurance Evaluation is considered to be the standard evaluation approach. It assumes that the [Target of Evaluation](./TargetofEvaluation.md) is evaluated on the basis of one set of [assurance requirements](./SecurityAssuranceRequirement.md).
diff --git a/c5dec/assets/database/KnowledgeBase/SubTOESecurityFunctionality.md b/c5dec/assets/database/KnowledgeBase/SubTOESecurityFunctionality.md
new file mode 100644
index 0000000..e69de29
diff --git a/c5dec/assets/database/KnowledgeBase/TOEBoundary.md b/c5dec/assets/database/KnowledgeBase/TOEBoundary.md
new file mode 100644
index 0000000..f6817c4
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOEBoundary.md
@@ -0,0 +1,58 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# TOE Boundary
+
+**Acronym:** None
+
+The TOE Boundary determines the physical and logical scope of the [TOE](TargetofEvaluation.md). All parts of an IT product that are not within the TOE Boundary are outside the scope of the evaluation.
+
+## Understanding the TOE Boundary
+
+Defining where your Target of Evaluation (TOE) starts and ends is crucial in the evaluation process. The TOE Boundary encompasses both physical and logical aspects and serves as a demarcation line that outlines the scope of the TOE when it’s handed to the customer.
+
+Imagine you’re evaluating a secure messaging app. The TOE Boundary may include the app itself and its integrated encryption technology but exclude the mobile device or network it operates on.
+
+## Why is it Significant?
+
+Identifying the TOE Boundary is pivotal for a few reasons:
+
+- **Scope Definition**: It clearly establishes what is being evaluated and what is not.
+- **Risk Management**: By understanding what's inside the boundary, we can better manage and evaluate the associated risks.
+- **Resource Allocation**: Ensures resources are focused on relevant areas during evaluation.
+
+## What’s Inside and Outside?
+
+Everything within the TOE Boundary is subject to evaluation under the Common Criteria. Conversely, elements outside the TOE Boundary are deemed part of the TOE’s operational environment and are considered during the evaluation but not tested.
+
+**Inside the TOE Boundary**:
+- Software components actively participating in security functions.
+- Hardware that is part of the TOE.
+- Security mechanisms employed by the TOE.
+
+**Outside the TOE Boundary**:
+- External systems interacting with the TOE.
+- Network infrastructure.
+- Non-TOE hardware and software components.
+
+## Practical Guidance
+
+### Defining the TOE Boundary:
+
+1. **Clarity is Key**: Ensure that boundaries are defined in a clear and unambiguous manner.
+2. **Detailed Documentation**: Provide thorough documentation highlighting what is included and excluded from the TOE, and justify the exclusions.
+3. **Security Functions**: Clearly document how each component within the TOE Boundary contributes to the TOE’s security functionality.
+4. **External Interaction**: Understand and document how the TOE interacts with elements outside the boundary.
+
+
+## Additional Resources
+
+- [Understandning TOE Operational Environement](./TOEOperationalEnvironment.md)
+- [Understanding Target of Evaluation](./TargetofEvaluation.md)
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TOEDescription.md b/c5dec/assets/database/KnowledgeBase/TOEDescription.md
new file mode 100644
index 0000000..ecd4b3a
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOEDescription.md
@@ -0,0 +1,59 @@
+---
+Last Updated: October 9, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TOE Description
+
+**Acronym:** None
+
+The TOE (Target of Evaluation) Description, embedded within the [Security Target (ST)](./SecurityTarget.md) Introduction, serves as a narrative exposition that navigates a middle ground, offering more detail than the [TOE Overview](./TOEOverview.md) while not delving as deep as the [TOE Summary Specification (TSS)](./TOESummarySpecification.md). It furnishes a panoramic view of the [TOE](./TargetofEvaluation.md), elucidating its inherent security functionalities and potentially exploring its applicability within a broader application context. The TOE Description meticulously parses through both the physical and logical scopes of the TOE. The physical scope delineates all constituent parts of the TOE, encapsulating hardware, firmware, software, and guidance parts, while the logical scope ventures into delineating major TOE functionalities and succinctly describing the [security features](./TOESecurityFunctionality.md). Intrinsically, the TOE Description is crafted to extirpate ambiguity, ensuring that the demarcation between what is enveloped within the TOE and what lies outside is lucidly clear and indisputable, thereby offering a coherent comprehension of the TOE’s capabilities and boundaries to evaluators and potential consumers.
+
+For [composed TOEs](./ComposedTOE.md), the description will also delve into the composed solution, discussing the physical and logical scopes, and identifying the logical boundaries between components. The role of each component in providing security functionality is also specified.
+
+## Practical Guidance
+
+### Reading a TOE Description
+
+For consumers seeking confidence in a TOE’s evaluated security features, the TOE Description emerges as an essential part of every ST, furnishing a detailed exposition of both its physical and logical security functionalities. Regarding the physical scope,all hardware, firmware, software, and guidance parts of the TOE are enumerated, providing not only their identifiers and formats but also their delivery mechanisms, ensuring that consumers are well-informed about each constituent part and its availability.
+In parallel, the logical scope gives consumers a clear picture of the TOE's security features, elucidating them to a degree that allows a general understanding.
+This detailed breakdown, coupled with clarifications on the evaluated TOE configurations, eliminates ambiguities regarding what is included in the TOE and hence in the evaluation.
+
+Particularly for composed TOEs, the TOE Description provides clarity on which features of individual components are encapsulated in the evaluated TOE, assuring that consumers can make enlightened decisions based on the actual evaluated security functionalities and configurations. Consequently, a careful reading of the TOE Description is indispensable for affirming that desired features and parts have been subjected to rigorous evaluation, thereby facilitating an informed selection and implementation of the TOE.
+
+### Writing a TOE Description
+
+1. Define the TOE’s Physical Scope
+**Objective:** Clearly detail all physical constituents of the TOE.
+- **List All Components:** Enumerate all hardware, firmware, and software parts.
+- **Detail Component Identifiers:** Include unique identifiers and formats (e.g., binary, *.pdf, etc.)
+- **Describe Delivery Methods:** Outline how each part is made available to the consumer (e.g., download link, physical delivery, etc.)
+- **Clarify Evaluated Configurations:** Provide descriptions and identifications of configurations evaluated, especially when multiple configurations are possible.
+2. Outline the TOE’s Logical Scope
+**Objective:** Present a detailed depiction of the TOE's logical security functionalities.
+- **Detail Security Features:** Describe the TOE's logical security features with sufficient detail for general understanding.
+- **Be Explicit About Included Features:** Ensure clarity about what logical security features are offered by the TOE.
+**Note:** In cases where an ST for a composed TOE is being developed, highlight which features of individual components are not within the composed TOE, and ensure clarity about the logical features that have been evaluated.
+3. Contextualize the TOE
+- **Position Within a Larger Context:** Describe how the TOE fits into a broader application or security context. This may provide clarity to consumers about its application and integration.
+- **Address User Needs:** Ensure that the TOE Description serves as a reliable reference for consumers to understand which features have been evaluated.
+4. Ensure Clarity and Lack of Ambiguity
+- **Avoid Misunderstandings:** Make sure that each part and feature is clearly identified as either being inside or outside the TOE. Eliminate any ambiguity.
+- **Provide Sufficient Detail:** Offer a level of detail that ensures readers can develop a broad understanding of the TOE's components and features without becoming bogged down in technicalities.
+5. Review and Validate
+- **Consumer-Centric Validation:** Ensure that the TOE Description aids consumers in affirming that the security features they intend to utilize have been evaluated.
+- **Evaluator-Friendly:** Facilitate the evaluators' work by clearly detailing what is included in the TOE, adhering to clarity and comprehensiveness.
+
+Creating a detailed and clear TOE Description is critical for ensuring that the evaluation of a product or system is both transparent and verifiable. This guide provides a structured approach to crafting a TOE Description that ensures both evaluators and consumers can discern what is part of the evaluation or what has been evaluated, facilitating confidence and informed decision-making. Always aim for clarity and completeness to ensure the TOE Description is both reliable and valid.
+
+
+## Additional Resources
+
+- **CC Part 3**
+- **ISO/IEC TR 15446**
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Target of Evaluation (TOE)](./TargetofEvaluation.md)
+- [TOE Security Functionality](./TOESecurityFunctionality.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TOEOperationalEnvironment.md b/c5dec/assets/database/KnowledgeBase/TOEOperationalEnvironment.md
new file mode 100644
index 0000000..72dd7b6
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOEOperationalEnvironment.md
@@ -0,0 +1,34 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# TOE Operational Environment
+
+The TOE Operational Environment encompasses all aspects that are presumed to exist in the environment where the [TOE](./TargetofEvaluation.md) will be deployed and operational. It encompasses physical, personnel, and technological aspects which are presumed to exist and safeguard security aspects which are outside the [TOE boundary](./TOEBoundary.md).
+
+In the context of the Common Criteria the TOE Operational Environment must meet certain constraints such as:
+
+- **Physical Aspect:** Includes the physical conditions and protections where the TOE is deployed and operated, such as secure installation sites, physical access controls, and environmental controls.
+- **Personnel Aspect:** Refers to the individuals who interact with or within the environment of the TOE, including administrators, users, and potential attackers. Their roles, responsibilities, and qualifications are defined to assure secure operation of the TOE.
+- **Technological Aspect:** Incorporates the IT environment, consisting of other IT products/systems (hardware and software) that interact with or support the TOE, such as operating systems, networks, and auxiliary storage devices.
+
+These aspects are meticulously addressed through the establishment of [assumptions](./Assumption.md) and adherence to [Organizational Security Policies (OSPs)](./OrganizationalSecurityPolicy.md). These elements collaboratively formulate a structured framework wherein assumptions delineate presumed conditions or attributes of the operational environment while OSPs impose specific procedural and security guidelines set by the overseeing organization or regulatory bodies. Consequently, to synthesize these provisions into a practical and implementable format, they are translated into [security objectives for the operational environment](./SecurityObjective.md).
+
+## Practical Considerations
+
+In practice, when dealing with TOE Operational Environment within CC:
+
+- While the TOE Operational Environment might not be explicitly defined within the [Security Target (ST)](./SecurityTarget.md) or [Protection Profile (PP)](./ProtectionProfile.md), its characteristics and expectations are implicitly conveyed through assumptions and Organizational Security Policies (OSPs), as well as through the derivation of security objectives for the operational environment. These elements collectively provide insights into the conditions and requirements of the TOE Operational Environment, influencing how the TOE is expected to achieve its specified [security functionalities](./TOESecurityFunctionality.md) within that environment.
+- The TOE Operational Environment is not tested during the evaluation but it’s vital to ensure that all the assumptions about the TOE Operational Environment are upheld in the actual deployment to ensure the TOE can provide the claimed security functionalities.
+- It's imperative to have a clear boundary definition between the TOE and its operational environment to clearly segregate the security functionalities provided by the TOE and those assumed to be provided by its operational environment.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** This technical report provides a methodical approach to creating an SPD, guiding users through the identification of informal security requirements, threats, policies, and assumptions.
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
+- [Security Objective for the Operational Environment](./SecurityObjective.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TOEOverview.md b/c5dec/assets/database/KnowledgeBase/TOEOverview.md
new file mode 100644
index 0000000..4398be2
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOEOverview.md
@@ -0,0 +1,71 @@
+---
+Last Updated: October 9, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TOE Overview
+
+**Acronym:** None
+
+The TOE Overview, positioned in the [Protection Profile (PP)](./ProtectionProfile.md) or [Security Target (ST)](./SecurityTarget.md) Introduction provides a succinct and clear description of the [TOE](./TargetofEvaluation.md) aimed at potential consumers and, in the context of a PP, developers. When part of a PP, the overview typically describes an implementation-independent TOE Type, while within an ST, it outlines a specific TOE implementation. This section is tailored to assist those who are exploring TOEs or TOE Types that align with their security requirements and are compatible with their hardware, software, and/or firmware environments.
+
+*CC2022 specific*
+
+For [multi-assurance](./MultiAssuranceEvaluation.md) STs, the TOE Overview also delineates the [TOE Security Functions (TSFs)](./TOESecurityFunctionality.md) organization into [sub-TSFs](./SubTOESecurityFunctionality.md), concretely defined in the [PP-Configuration](./PPConfiguration.md) to which the ST [claims conformance](./ConformanceClaim.md). Consequently, the TOE Overview serves as a pivotal section, articulating the TOE or TOE Type concerning its type, usage, principal security features, and notable dependencies, offering a focused and comprehensive snapshot imperative for evaluating its suitability and compliance with both consumer and developer needs.
+
+## Practical Guidance
+
+The TOE Overview, describes the TOE in terms of its usage and major security features, the TOE Type, alongside any required non-TOE hardware/software/firmware.
+
+### Reading a TOE Overview:
+
+1. **Commence with the TOE Overview:**
+ - Begin by reading the TOE Overview in a PP or ST as it offers an initial understanding of potential TOEs for your needs and informs about their compatibility with certain hardware, software, and firmware.
+
+2. **Understand Three Key Sections:**
+ a. **Usage and Major Security Features:**
+ - Gain a general insight into the TOE’s capabilities and applicability in a security context without delving into technical depths.
+ - This segment should be consumer-friendly and non-technical, providing a general, non-exhaustive overview.
+ b. **TOE Type:**
+ - Identify the broad category to which the TOE belongs (e.g., firewall, LAN, etc.).
+ - Heed any warnings about expected functionalities or usage environments that the TOE does not support, as these might be pivotal in your decision-making process.
+ c. **Required Non-TOE Hardware/Software/Firmware:**
+ - Identify essential external components needed to utilize the TOE, ensuring these elements align with your infrastructure and policies without necessitating exhaustive details.
+
+3. **Cautious Consideration:**
+ - Especially note any warnings or limitations mentioned in the TOE type section, weighing their impact against your operational needs and determining the TOE’s viability accordingly.
+
+### Writing a TOE Overview:
+
+1.** Summarizing Usage & Security Features (ASE_INT.1.4C)**
+- Provide a brief, non-technical summary of TOE usage and main security features.
+- Ensure consistency and explicit identification of evaluated/non-evaluated features across the ST.
+- In composed TOEs, focus on the overall TOE, not individual components.
+2. **Identifying TOE Type (ASE_INT.1.5C)**
+- Clearly identify the TOE type and ensure it is not misleading.
+- Discuss any absent functionality or operational environment limitations explicitly.
+3. **Specifying Non-TOE Hardware/Software/Firmware (ASE_INT.1.6C)**
+- Identify and briefly describe any non-TOE hardware, software, or firmware required.
+- Ensure clarity for consumers regarding what is needed for TOE operation.
+4. **Describing TSF Organization for Multi-Assurance STs (ASE_INT.1.7C)** [If applicable]
+- Detail the TSF organization according to sub-TSFs defined in the related PP Configuration.
+- Integrate any specific actual TOE details if relevant.
+
+#### Quick Tips for TOE Overview Writing
+- **Clarity:** Keep language clear and accessible for consumers.
+- **Transparency:** Be explicit and transparent about TOE limitations and non-supported functionalities.
+- **Consistency:** Maintain consistency in information and descriptions throughout the ST.
+
+This compact guide centralizes the fundamental aspects of writing a TOE Overview compliant with evaluator actions and work units outlined in the Common Criteria (CC) Part 3, balancing evaluation adherence with consumer-friendliness and information accessibility.
+
+## Additional Resources
+
+- **CC Part 1 and Part 3**
+- **ISO/IEC TR 15446**
+
+## Related Articles
+
+- [Security Target](./SecurityTarget.md)
+- [Protection Profile](./ProtectionProfile.md)
+- [Multi-Assurance Evaluation](./MultiAssuranceEvaluation.md)
+- [Single-Assurance Evaluation](./SingleAssuranceEvaluation.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TOEReference.md b/c5dec/assets/database/KnowledgeBase/TOEReference.md
new file mode 100644
index 0000000..d61f9cd
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOEReference.md
@@ -0,0 +1,23 @@
+---
+Last Updated: October 9, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TOE Reference
+
+**Acronym:** None
+
+The TOE Reference, a vital component of the [Security Target (ST)](./SecurityTarget.md) introduction, serves to distinctly identify a [TOE](./TargetofEvaluation.md) and typically comprises the developer name, TOE name, and TOE version number.
+
+## Practical Guidance
+
+For a robust and clear TOE identification, the TOE Reference should not only be concise but also adequately detailed. Although the basic identification involves the developer's name, TOE name, and version, embedding additional identifiers enhances clarity and specificity:
+
+- **Build Number & Release Date:** For detailed versioning and time-stamping the TOE status.
+- **Patch Level:** Indicates the application of specific patches.
+- **Configuration Details:** Offers insight into the TOE’s deployment and operational settings.
+- **Hardware/Software Dependencies:** Specifies any dependent hardware or software.
+- **Serial or Batch Number:** Particularly relevant for hardware TOEs, offering additional tracing capabilities.
+- **Hash Values:** For software TOEs, providing a cryptographic hash of the evaluated binary can be curcial to ensure the authenticity and integrity.
+
+These identifiers help safeguard against ambiguities and misidentifications, particularly crucial given that developers might circumvent misleading TOE reference prohibitions stipulated in subclause A.4.1 (CCv3R5 Part 1), and D.3.2.2 (CC2022 Part 1) by utilizing a product name. Thus, a thorough examination of the [TOE Overview](./TOEOverview.md) and/or [TOE Description](./TOEDescription.md) becomes imperative, ensuring that the TOE's deployment and use are not only consistent with its evaluated status but also transparently communicated to all relevant stakeholders.
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TOESecurityFunctionality.md b/c5dec/assets/database/KnowledgeBase/TOESecurityFunctionality.md
new file mode 100644
index 0000000..cddb09d
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOESecurityFunctionality.md
@@ -0,0 +1,37 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TOE Security Functionality
+
+**Acronym:** TSF
+
+ The TOE Security Functionality (TSF) within the context of the Common Criteria refers to a set of security-specific functions, mechanisms, and features that the [TOE](./TargetofEvaluation.md) implements to comply with the identified [security objectives](./SecurityObjective.md) and [requirements](./SecurityFunctionalRequirement.md). It represents the embodiment of all hardware, software, and firmware within the TOE that must be relied upon for the correct enforcement of the security objectives. Essentially, the TSF is responsible for the implementation of the security objectives that mitigate the identified [threats](./Threat.md), uphold [organizational security policies (OSPs)](./OrganizationalSecurityPolicy.md), and maintain environmental [assumptions](./Assumption.md). Depending on the TOE’s architecture, the TSF may represent the entirety of the TOE or a specific component thereof. If it only represents a portion, safeguarding measures must be instituted to ensure non-TSF parts do not manipulate or bypass the TSF, jeopardizing the fulfillment of security objectives. Notably, security objectives prescribed for the operational environment can augment the TSF by providing additional supportive functionalities.
+
+## Practical Guidance
+
+A TSF fundamentally represents the practical realization of security within the TOE, transmuting identified Security Functional Requirements (SFRs) into tangible security controls, mechanisms, and features. A TSF is intrinsically linked to and derived from the various hierarchical elements of the [Protection Profile](./ProtectionProfile.md) and/or [Security Target](./SecurityTarget.md), cascading from the [Security Problem Definition (SPD)](./SecurityProblemdefinition.md) down through Security Objectives (SOs), and SFRs.
+
+In essence, a TSF serves as the actual implementation of the specified SFRs, translating the theoretical and policy-level security necessities into concrete, enforceable security functionalities within the TOE. It emerges at the terminal point of a logical flow that spans:
+
+- **SPD:** Initial identification of threats, assumptions, and OSPs.
+- **SOs:** High-level security outcomes and objectives derived from the SPD.
+- **SFRs:** Detailed, standardized requirements that embody the practical realization of the SOs.
+- **TSF:** The physical and logical embodiment of the SFRs within the TOE, ensuring the realized security attributes and mechanisms adhere to the initially identified security objectives.
+
+
+The description and definition of the TSF are inherently multifaceted and spread across various domains, each contributing to a comprehensive understanding and depiction.
+- **TOE Design and Functional Specification:** The TOE Design, as required by ADV_TDS, identifies the actual parts that make up the TSF. Once the TSF has been defined in terms of constituting components, the [TSF Interfaces](./TSFInterface.md) are identified and described in accordance with the requirements stated in ADV_FSP Functional Specification.
+- **Implementation Representation:** Adhering to ADV_IMP, the transition from TSF design to physical implementation within the TOE is meticulously mapped and verified.
+- **Security Architecture:** In accordance with ADV_ARC, the TSF ensures unassailable architectural robustness, safeguarding [domain separation](./DomainSeparation.md), [self-protection](./SelfProtection.md), and preventing [bypassing](./NonBypassability.md) of security functionalities.
+- **Internal Structuring:** Through ADV_INT, the internal structuring of the TSF is highlighted, emphasizing principles like modularity and layering, which contribute to robust, secure, and maintainable implementations.
+- **Security Policy Model:** (If applicable) The ADV_SPM puts forth a model encapsulating the security policies that the TSF enforces, providing an abstracted view that maps to functional specifications, thereby enhancing understanding and verifiability.
+
+## Additional Resources
+
+- CC Part 3: Class ADV Development, Annex A
+
+## Related Articles
+- [Security Functional Requirement (SFR)](./SecurityFunctionalRequirement.md)
+- [Security Target](./SecurityTarget.md)
diff --git a/c5dec/assets/database/KnowledgeBase/TOESummarySpecification.md b/c5dec/assets/database/KnowledgeBase/TOESummarySpecification.md
new file mode 100644
index 0000000..c84dae3
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TOESummarySpecification.md
@@ -0,0 +1,114 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TOE Summary Specification
+
+**Acronym:** TSS
+
+The TOE Summary Specification (TSS), exclusive to the [Security Target (ST)](./SecurityTarget.md) delivers an abstract, security-centric model of the [Target of Evaluation (TOE)](./TargetofEvaluation.md). It delineates how [Security Functional Requirements (SFRs)](./SecurityFunctionalRequirement.md) are realized within the TOE, offering consumers an overview that intertwines the TOE’s overall functionality and architecture with the realization of the SFRs. Through offering a detailed context wherein subjects, objects, security attributes, and rules as determined by the SFRs are contextualized within the TOE’s architectural and functional framework, the TSS furnishes a model that, while possibly abstracting from numerous non-security functions, provides a thorough insight into the TOE’s security functionality.
+
+## Practical Guidance
+
+The TOE Summary Specification (TSS) provides a transparent and insightful description aimed at enabling potential TOE consumers to comprehend how the Security Functional Requirements (SFRs) are satisfied by detailing the associated technical mechanisms and implementations. Ensuring a balance in detail, the TSS employs natural language to describe the realization of the SFRs, illustrating how they amalgamate to deliver security functionality within the visible architecture of the TOE. This allows for a lucid understanding of how the TOE not only adheres to but implements the defined SFRs in a tangible, verifiable manner, thereby serving as a reliable guide for consumers and evaluators alike.
+
+In the subsequent structure of the TSS, consider commencing with a general overview of the TOE and its architectural boundaries, followed by a detailed exposition of the security functions in relation to the derived SFRs. Incorporating mappings that clearly trace the security functionalities to the respective SFRs, and where applicable, delineating the component interaction in a composed TOE, will enhance clarity and facilitate informed evaluation. Below you find a potential structure of the TSS.
+
+## Potential TSS Structure with example
+
+### 1. General Overview
+#### 1.1 TOE Architecture
+*Abstract description of the TOE architecture and the defined TSF boundary.*
+
+Example: The TOE is a cloud-based storage system, composed of distributed data centers, user interfaces (UI), application programming interfaces (APIs), user authentication mechanisms, and encryption modules. Here, the TSF boundary may delineate the interactions and communications between user devices and data centers, focusing on security enforcement during data transmission and storage.
+
+#### 1.2 TSF Protection Mechanisms
+*Explain how the TSF is safeguarded against tampering and bypass.*
+
+Example: The TOE employs multi-factor authentication (MFA) to protect against unauthorized access to admin panels and user accounts. Intrusion detection and prevention systems (IDPS) are utilized to safeguard the TSF from network-based attacks and anomalies.
+
+### 2. Functional Model
+*Functional model used to derive the SFRs with additional explanations to put the model into context of the entire TOE with all its functions and architecture.*
+
+```mermaid
+graph TB
+ subgraph "TOE Architecture"
+ UI(User Interface)
+ API(Application Programming Interface)
+ AM(Authentication Mechanisms)
+ EM(Encryption Modules)
+ DC(Data Centers)
+ end
+
+ subgraph "Security Functions"
+ SDT(Secure Data Transmission)
+ UDE(User Data Encryption)
+ UA(User Authentication)
+ end
+
+ subgraph "Security Functional Requirements (SFRs)"
+ FPT_ITC_1_1(FPT_ITC.1.1)
+ FPT_ITI_1_1(FPT_ITI.1.1)
+ FPT_ITT_1_1(FPT_ITT.1.1)
+ FCS_COP_1_1(FCS_COP.1.1)
+ FTP_TRP_1_1(FTP_TRP.1.1)
+ end
+
+ UI -->|Data Transmission| SDT
+ API -->|Data Transmission| SDT
+ DC -->|Data Storage & Retrieval| UDE
+ AM -->|Credential Verification| UA
+ EM -->|Encrypt/Decrypt Data| UDE
+
+ SDT -->|Mapped to| FPT_ITC_1_1
+ SDT -->|Mapped to| FPT_ITI_1_1
+ SDT -->|Mapped to| FPT_ITT_1_1
+ SDT -->|Mapped to| FCS_COP_1_1
+ SDT -->|Mapped to| FTP_TRP_1_1
+
+ UDE -->|Mapped to| FCS_COP_1_1
+ UA -->|Implicitly supports| FTP_TRP_1_1
+```
+
+#### 2.1 Security Functions
+*Detailed exposition of the security functions, ensuring clear linkages to the TOE’s broader functionality and architectural framework.*
+
+Example: Security functions for this TOE may include secure data transmission employing TLS, user data encryption utilizing AES-256, and user authentication via passwords and MFA. Each function would be described in context with its interactions and dependencies within the system, such as how user authentication is enforced prior to allowing access to stored data.
+
+### 3. Mapping to SFRs
+*Provide a mapping showcasing how each security functionality corresponds to and fulfills SFRs.*
+
+Example: For the cloud-based storage TOE, "Secure Data Transmission" as a security function could directly map to an SFR related to ensuring data confidentiality and integrity during transmission.
+
+Security Function | SFR ID | SFR
+---- | ---- | ----
+Secure Data Transmission | FPT_ITC.1.1 | The TSF shall protect all TSF data transmitted from the TSF to another trusted IT product from unauthorized disclosure during transmission.
+ | | FPT_ITI.1.1 | The TSF shall provide the capability to detect modification of all TSF data during transmission between the TSF and another trusted IT product within the following metric: [assignment: a defined modification metric].
+ | | FPT_ITT.1.1 | The TSF shall protect TSF data from [selection: disclosure, modification] when it is transmitted between separate parts of the TOE.
+ | | FCS_COP.1.1 | The TSF shall perform [assignment: list of cryptographic operations] in accordance with a specified cryptographic algorithm [assignment: cryptographic algorithm] and cryptographic key sizes [assignment: cryptographic key sizes] that meet the following: [assignment: list of standards].
+ | | FTP_TRP.1.1 | The TSF shall provide a communication path between itself and [selection: remote, local] users that is logically distinct from other communication paths and provides assured identification of its end points and protection of the communicated data from [selection: modification, disclosure, [assignment: other types of integrity or confidentiality violation]].
+
+### 4. Detailing Composition for Composed TOEs
+*Elaborate on the individual components and their interactions in providing SFRs for a composed TOE.*
+
+#### 4.1 Component Descriptions
+Example: The TOE, being a cloud storage solution, might consist of components such as a user access management module, a data storage module, and a data transmission module. Descriptions might explore the individual functionalities and inherent security aspects of each module, and how they interconnect.
+#### 4.2 SFR Mapping and Interaction for Composed TOEs
+*Describe how the SFRs for the composed TOE map to component SFRs and their collaborative interactions.*
+
+Example: The document may detail how the "User Authentication" SFR of the user access management module correlates and interacts with a "Data Encryption" SFR in the data storage module, ensuring that only authenticated users have access to decrypted data.
+
+**Note**: This template serves to structure and guide the content creation process, ensuring each critical aspect of the TSS is comprehensively addressed and documented in a clear, coherent manner.
+
+Each subsection should be rigorously developed to ensure the TSS provides not only a technical exposition but also facilitates clear comprehension for consumers regarding how the TOE implements and adheres to SFRs.
+
+## Additional Resources
+
+- ISO/IEC 15446: Guide for the production of Protection Profiles and Security Targets.
+- Common Criteria for Information Technology Security Evaluation.
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Security Functional Requirements (SFR)](./SecurityFunctionalRequirements.md)
\ No newline at end of file
diff --git a/c5dec/assets/database/KnowledgeBase/TSFInterface.md b/c5dec/assets/database/KnowledgeBase/TSFInterface.md
new file mode 100644
index 0000000..795df43
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TSFInterface.md
@@ -0,0 +1,37 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC2022
+---
+
+# TSF Interface
+
+**Acronym:** TSFI
+
+The **TSF Interface (TSFI)** within the context of the [Common Criteria (CC)](./CommonCriteria.md) pertains to the explicit detailing and specification of all interactions that occur between the [TOE Security Functionality (TSF)](./TOESecurityFunctionality.md) and external entities, as well as between TSF parts, and between TSF parts and [non-TSF parts](./NonTSFPart.md) within the TOE. Defined under the Development (ADV) class, particularly the Functional Specification (ADV_FSP) family, the TSFI is critical in describing how the TSF interacts and communicates, ensuring that all interactions are secure, controlled, and aligned with the [Security Functional Requirements (SFRs)](./SecurityFunctionalRequirement.md). Specifically, TSFI can be:
+
+- **SFR-Enforcing:** if services accessible through the interface can be directly traced to SFRs.
+- **SFR-Supporting:** interfaces that facilitate services that are not directly traced to SFRs but are essential for the functionality of SFR-enforcing services.
+- **SFR Non-Interfering:** interfaces that have no impact on or interaction with SFR-enforcing functionality.
+
+## Practical Guidance
+
+### Ensuring Traceability to SFRs
+One of the pivotal requisites in defining and detailing TSFI is establishing an explicit and clear traceability to the SFRs, ensuring that each interface either enforces, supports, or does not interfere with the defined security functional requirements. The ability to draw a coherent line from the TSFI to SFRs is not only essential for establishing a robust security architecture but also imperative to fulfill CC validation requirements.
+
+### Detailed Specifications
+To adequately define and evaluate TSFI, consider incorporating the following detailed attributes:
+- **Purpose:** Define the general functionalities it is designed to manage or facilitate.
+- **Method of Use:** Define how the interface is used, detailing available interactions and behaviors across interfaces.
+- **Parameters:** Identify and list inputs and outputs that govern the interface’s behaviors.
+- **Parameter Descriptions:** Provide comprehensive definitions of parameters, clarifying their role and importance.
+- **Actions:** Describe functionalities executed by the interface, indicating how these actions relate to SFRs or otherwise.
+- **Error Messages:** Detail conditions and methods under which error messages are generated and classified, differentiating between direct, indirect, and remaining errors.
+
+## Additional Resources
+
+- **CC Part 3: Security Assurance Requirements**: Providing detailed insight into ADV_FSP and the specification of the TSFI within the CC framework.
+
+## Related Articles
+
+- [TOE Security Functionality (TSF)](./TOESecurityFunctionality.md)
+- [Security Functional Requirements (SFRs)](./SecurityFunctionalRequirement.md)
diff --git a/c5dec/assets/database/KnowledgeBase/TargetofEvaluation.md b/c5dec/assets/database/KnowledgeBase/TargetofEvaluation.md
new file mode 100644
index 0000000..7a33c8e
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/TargetofEvaluation.md
@@ -0,0 +1,62 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5, CC 2022
+---
+
+# Target of Evaluation
+
+**Acronym:** TOE
+
+In the context of Common Criteria the product or system that is subject of the evaluation is called the Target of Evaluation (TOE).
+In other words, the TOE is what you're trying to evaluate under the Common Criteria. It might be a whole IT product, just a part of it, a combination of several products, or even a unique technology that isn't typically available as a product.
+
+- **Complete IT Product**: An entire software or hardware product.
+- **Part of IT Product**: A specific module or functionality within a product.
+- **Set of IT Products**: A suite of related software or hardware products.
+- **Unique Technology**: Specialized technologies, which might not be available to the broader market.
+
+The physical and logical scope of the TOE is determined by the [TOE's Boundary](TOEBoundary.md). Any parts of an IT product that are not within the TOE boundary are outside the scope of the evaluation and are called *non-TOE parts of the IT product* and considered to be part of the [TOE's Operational Environment](TOEOperationalEnvironment.md).
+
+## Practical Guidance
+
+### Points to Ponder While Defining TOE:
+
+1. **Functionality**: Ensure to dissect all functionalities the product is supposed to perform.
+2. **Security**: Highlight and document all security aspects that are intended to be evaluated.
+3. **Components**: Explicitly differentiate between what is TOE and what isn’t.
+4. **External Dependencies**: Be mindful of interactions or dependencies with external components, especially those in the TOE’s Operational Environment.
+
+### TOE Specification
+
+In the context of the Common Criteria (CC), the Target of Evaluation (TOE) is outlined in the [Protection Profile (PP)](./ProtectionProfile.md) and/or [Security Target (ST)](./SecurityTarget.md) in terms of a TOE overview, TOE description, and TOE Reference to provide a clear, comprehensive understanding of the product or system.
+
+- **[TOE Overview](./TOEOverview.md):** The TOE overview functions as an introductory section, offering a high-level glimpse into the TOE, and typically entails:
+ - TOE Usage: A description detailing how the TOE is utilized.
+ - Major Security Features: An exposition of principal security functionalities and features.
+ - TOE Type: A definition or categorization of the TOE.
+ - Non-TOE Hardware/Software/Firmware: Identifying any additional elements required for the TOE’s operation but not part of the evaluation.
+- **[TOE Reference (ST-specific)](./TOEReference.md):** The TOE reference acts as a unique identifier, ensuring clear and unambiguous identification of the specific TOE variant being evaluated by including:
+ - TOE Identifier: A unique name or label.
+ - Version Information: Specific version or release details.
+ - Developer/Manufacturer Information: Data pertaining to the entity responsible for the TOE’s development.
+ - Additional Identifiers: Any other pertinent reference data or identifiers.
+- **[TOE Description (ST-specific)](./TOEDescription.md):** This section delves into detailed information about the TOE, encompassing delineating the limits and extents of the TOE and distinguishing between what constitutes the TOE physically and logically and what lies outside of it.
+ - physical scope: a list of all hardware, firmware, software, and guidance parts that constitute the TOE.
+ - logical scope: major TOE functions and brief description of the [security features](./TOESecurityFunctionality.md)
+- **[TOE Summary Specification (ST-specifc):](./TOESummarySpecification.md)** This section provides a high-level description of how the TOE meets each [SFR](./SecurityFunctionalRequirement.md) through its TSF. It relates the SFRs to the actual security functions provided by the TSF, demonstrating that the implementation of the TSF satisfies the defined requirements.
+
+### Tips for Beginners:
+
+- Ensure that the TOE is distinctly and accurately defined to avoid ambiguity during evaluations.
+- Maintain clear documentation that precisely differentiates between TOE and non-TOE components.
+
+## Additional Resources
+
+- [Understanding TOE Boundaries](./TOEBoundary.md)
+- [Understandning TOE Operational Environement](./TOEOperationalEnvironment.md)
+- [Common Pitfalls while defining TOE](./404.md)
+
+## Related Articles
+
+- [Security Target (ST)](./SecurityTarget.md)
+- [Protection Profile (PP)](./ProtectionProfile.md)
diff --git a/c5dec/assets/database/KnowledgeBase/Threat.md b/c5dec/assets/database/KnowledgeBase/Threat.md
new file mode 100644
index 0000000..7d2c39e
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/Threat.md
@@ -0,0 +1,66 @@
+---
+Last Updated: October 4, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Threat
+
+**Acronym:** T
+
+In the domain of cybersecurity and within the context of [Security Problem Definition (SPD)](./SecurityProblemdefinition.md), threats are potential occurrences that could exploit [vulnerabilities](./Vulnerability.md) to adversely impact [assets](./Asset.md). Threats may intentionally or unintentionally compromise the confidentiality, integrity, or availability of assets, thus posing a risk to the [Target of Evaluation (TOE)](./TargetofEvaluation.md) and its [operational environment](./TOEOperationalEnvironment.md).
+Threats are indispensable in formulating the [Security Problem Definition](./SecurityProblemDefinition.md) (SPD).
+
+## Practical Guidance
+
+### Identification and Analysis of Threats
+
+Threat identification is a fundamental aspect of risk and threat analysis, acting as a precursor to conducting meaningful risk assessments and formulating security controls. Given the CC's asset-centric nature, threats are identified relative to assets. Once assets are identified, an orderly approach to discerning relevant threats involves iterating through all assets and adhering to the following steps:
+
+1. **Threat Source Identification:**
+ - _Adversarial:_ Consider intentional entities like hackers.
+ - _Non-Adversarial:_ Include non-intentional sources like system errors.
+2. **Threat Event Characterization:** Describe potential adverse events from each source and their impacts.
+3. **Utilize Threat Intelligence:** Leverage databases and forums for recognized threats.
+4. **Regulatory Consultation:** Explore guidelines from cybersecurity bodies.
+5. **Stakeholder Collaboration:** Employ insights from various stakeholders.
+6. **Articulation into Security Objectives:** Ensure that for each threat an actionable [security objective](./SecurityObjective.md) are defined in the [Security Target (ST)](./SecurityTarget.md) or [Protection Profile (PP)](./ProtectionProfile.md). These security objectives should offer a clear, solution-oriented representation, elucidating how the TOE, its operational environment, or the combination of both, will concretely counter or mitigate the identified threat.
+
+### Documentation of Threats
+
+In the context of CC, threats must be described as adverse actions executed by [threat agents](./ThreatAgent.md) to compromise an asset, as shown in the example below.
+
+**T.COMPROMISEDCOMMUNICATION**
+
+A network attacker may gain unauthorised logical access to communication channels in order to
+disclose or modify data exchanged between parts of the TOE and remote external entities.
+
+- **Threat Agent:** a network attacker
+- **Adverse Action:** unauthorised logical access to communication channels
+- **Asset:** data exchanged betweent parts of the TOE and remote external entities
+
+*Extracted from the Protection Profile Mobile Device Management - Trusted Server, BSI-CC-PP-0115, Version 1.0.
+
+### Techniques for Threat Analysis:
+
+- **Threat Modeling:** Utilize strategies like STRIDE, PASTA, LINDDUN, hTMM, or Attack Tree Modeling.
+- **Industry Threat Libraries:** Employ predefined libraries for relevant scenarios.
+
+## Beginners' Tips
+
+- **Adopt an Attacker’s Perspective:** Think like an adversary to uncover various compromising avenues.
+- **Simplicity First:** Start with clear, known threats, gradually advancing to nuanced scenarios.
+- **Ensure Holistic Perspectives:** Embed organizational, technical, and environmental contexts in threat identification.
+
+## Resources for Further Reading
+
+- **CVE Database:** A comprehensive source of publicly known cybersecurity vulnerabilities.
+- **MITRE ATT&CK:** A globally-accessible knowledge base of adversary tactics and techniques.
+- [**Threat Modeling-12 available methods**](https://insights.sei.cmu.edu/blog/threat-modeling-12-available-methods/)
+
+## Related Documents
+
+- [Defining Security Problem (SPD)](./SecurityProblemDefinition.md)
+- [Identifying Assets](./Asset.md)
+- [Understanding Vulnerabilities](./Vulnerability.md)
+- [Details about the Target of Evaluation (TOE)](./TargetofEvaluation.md)
+
diff --git a/c5dec/assets/database/KnowledgeBase/ThreatModeling-TR15446.md b/c5dec/assets/database/KnowledgeBase/ThreatModeling-TR15446.md
new file mode 100644
index 0000000..dbb60c7
--- /dev/null
+++ b/c5dec/assets/database/KnowledgeBase/ThreatModeling-TR15446.md
@@ -0,0 +1,146 @@
+---
+Last Updated: October 11, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Threat Modeling in the Context of ISO/IEC TR 15446
+
+**Acronym:** None
+
+In the formulation of a Security Problem Definition (SPD), threat modeling stands out as a pivotal component. Within ISO/IEC TR 15446, threat modeling is underscored as a methodical approach to identify, analyze, and prioritize potential threats to the Target of Evaluation (TOE). This involves a rigorous analysis phase where threats are systematically identified, followed by detailed documentation to serve as a foundational element of the SPD.
+
+## Practical Guidance
+
+Developing an adept threat model following TR 15446 involves:
+
+1. **Threat Identification:**
+ - **Asset Identification:** Recognize and categorize assets within the TOE and its operational environment.
+ - **Threat Agents:** Identify potential attackers, considering capabilities, intentions, and targets.
+ - **Attack Vectors:** Determine the potential pathways or methods that threat agents may employ.
+
+2. **Threat Analysis:**
+ - **Attack Tree Analysis:** Develop attack trees to visualize different paths an attacker might utilize to compromise assets.
+ - **Weakness Analysis:** Identify and analyze vulnerabilities or weak points within the TOE that might be exploited.
+
+3. **Threat Documentation:**
+ - **Clear Descriptions:** Provide detailed, clear, and comprehensive descriptions of each threat.
+ - **Prioritization:** Based on potential impact and likelihood, prioritize threats to guide focused mitigation efforts.
+
+4. **Integration into SPD:**
+ - **Alignment:** Ensure threats are aligned with assets, organizational policies, and environmental assumptions.
+ - **Inclusion of Mitigation:** Detail any existing or planned mitigation strategies or security controls against each threat.
+
+## Tips for Beginners
+
+- **Collaborative Approach:** Engage stakeholders from various domains (IT, business, compliance, etc.) to ensure a comprehensive threat model.
+- **Use of Tooling:** Employ threat modeling tools to document and analyze identified threats and attack paths systematically.
+- **Consistent Review:** Post-implementation, continuously review and update the threat model in response to changes in the environment or emerging threat vectors.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** Dive deep into its guidelines to understand nuanced aspects of conducting a detailed threat analysis.
+- **Threat Modeling Tools:** Explore tools that facilitate systematic threat modeling, analysis, and documentation.
+- **Industry Threat Reports:** Utilize reports and whitepapers from cybersecurity organizations to stay abreast of emerging threats.
+
+## Related Articles
+
+- [Security Problem Definition (SPD)](./SecurityProblemDefinition.md)
+- [Understanding and Managing Assets](./Asset.md)
+- [Navigating through Organizational Security Policies](./OrganizationalSecurityPolicy.md)
+
+
+---
+Last Updated: October 11, 2023
+Relevant CC Version: 3.1 Revision 5
+---
+
+# Security Problem Definition and Methodology according to ISO/IEC TR 15446
+
+**Acronym:** SPD
+
+ISO/IEC 15408 provides flexibility in the approach toward creating a Security Problem Definition (SPD). It does not stipulate a particular methodology but allows for various processes to be employed in defining the SPD. However, for those unfamiliar with preparing Protection Profiles (PPs) and Security Targets (STs), ISO/IEC TR 15446 offers a seasoned and pragmatic methodology, valid across numerous organizations and environments.
+
+ISO/IEC TR 15446 emphasizes utilizing the outcomes from a security risk assessment as a pivotal source for comprehending a security problem and formulating the SPD. This approach not only strives for comprehensiveness but also introduces the element of proportionality, identifying both acceptable and unacceptable risks, and enabling adaptable modifications through design trades based on the implementational and evaluational complexity of required controls.
+
+## Practical Guidance
+
+Based on ISO/IEC TR 15446, develop the SPD by:
+
+1. **Identifying and Confirming the Informal Security Requirement:**
+ - Acknowledge existing informal security needs, which might be unwritten or informally discussed among stakeholders.
+ - Secure confirmation from management and stakeholders that identified requirements genuinely represent their security needs.
+
+2. **Identifying and Specifying Threats via Formal Threat Analysis:**
+ - Perform a rigorous analysis to identify potential threats and their impacts on identified assets.
+
+3. **Documenting Applicable Policies and Assumptions:**
+ - Clearly detail relevant organizational security policies and assumptions regarding the operational environment.
+
+4. **Finalising and Checking the SPD Specification:**
+ - Ensure the finalized SPD aligns accurately with the previously established and confirmed informal requirement.
+
+In addition, the methodology embeds two supplementary aspects that, while not mandatory per ISO/IEC 15408, have proven beneficial in practice:
+
+- **Documenting Discounted Threats:**
+ - Detail threats that might or might not apply to the product but, if pertinent, would be countered by security functionality integrated into the TOE for varied reasons.
+
+- **Producing a Rationale:**
+ - Establish a coherent rationale that maps the SPD back to the informal security requirement, ensuring traceability and justifiability of the formalized SPD.
+
+## Tips for Beginners
+
+- **Informal Requirement Identification:** Engage stakeholders through workshops or interviews to elicit potential informal security requirements.
+- **Inclusivity:** Ensure that all discounted threats and applicable policies are exhaustively explored and documented to mitigate future challenges or overlooked aspects.
+- **Iteration:** Recognize that SPD development might necessitate iterative processes to refine and validate the documented requirements and threats.
+
+## Additional Resources
+
+- **ISO/IEC TR 15446:** Investigate its methodological insights and step-by-step guidance for a deeper, contextual understanding of SPD formulation.
+- **Threat Modeling Tools:** Utilize available tools to facilitate threat identification and analysis processes in a systematic manner.
+
+## Related Articles
+
+- [Formulating the Security Target (ST)](./SecurityTarget.md)
+- [Developing the Protection Profile (PP)](./ProtectionProfile.md)
+- [Understanding and Managing Assets](./Asset.md)
+
+
+## Practical Guidance
+
+### Utilizing Security Risk Assessment Findings
+
+1. **Leveraging Proportionality:**
+ - Assess risks considering their likelihood and significance of loss.
+ - Identify acceptable and unacceptable risks, facilitating adaptable security problem modifications.
+
+2. **Employing Informed Decision Making:**
+ - After gathering and validating all information, segregate it into:
+ a) Attacks the product must counteract.
+ b) Essential security attributes or features.
+ c) Non-essential security attributes or features.
+
+ - Understand that these distinctions guide varied treatments in subsequent development stages:
+ - **Attacks:** Treated as threats and need to be countered.
+ - **Essential Features:** Correspond to organizational security policies (OSPs).
+ - **Non-Essential Features:** Align with assumptions.
+
+### Integrating the Risk Assessment into SPD Development
+
+Ensure the risk assessment findings are intricately woven into the SPD development process, offering a robust foundation to define and differentiate between potential threats, obligatory security attributes, and assumptive attributes.
+
+## Tips for Beginners
+
+- **Leverage Existing Resources:** Maximize the use of available risk assessment results to guide the SPD development.
+- **Collaborate with Risk Teams:** Engage with risk assessment teams to gain insights into the identified risks and mitigation strategies.
+- **Iterative Validation:** Regularly verify for inconsistencies in collated information, ensuring a coherent and accurate SPD.
+
+## Additional Resources
+
+- **Security Risk Assessment Methodologies:** Explore and utilize standardized methodologies to facilitate a thorough and proportional risk assessment.
+- **ISO/IEC TR 15446:** A deeper dive will offer further detailed methodological insights.
+
+## Related Articles
+
+- [Understanding and Addressing Threats](./Threat.md)
+- [Formulating and Applying Organizational Security Policies (OSPs)](./OrganizationalSecurityPolicy.md)
+- [Developing and Validating Assumptions](./Assumption.md)
diff --git a/c5dec/assets/database/KnowledgeBase/_figures/AssetDef.png b/c5dec/assets/database/KnowledgeBase/_figures/AssetDef.png
new file mode 100644
index 0000000000000000000000000000000000000000..5b2aafa0358d0a624dffed384813a7eea57b1b59
GIT binary patch
literal 72168
zcmeEuc{rAD+wIdlku;d2L8wfTF;kO>q%vnnGK3H%WNH#2Q8EvO%t?~WN`^93NMH`#Zk<*ZyNa$NPJa%Hw(N`?}8SJl9(1I&TkUr4!WanbuP%6l!_7
zV`nLpmCO{%@}{+`@h>l2-i=WxJ1FwU4y)LO{%XEqr()Q$I6C>{x4_P8ew$2tRkv>1
zwo0GJ=XspQE7u>iI>+Zy^%y<#F1k%;w9jb9aPcf-|NV$^>(NQ3_;Xdm
zJ`!Ry2Cs%>xFYJV+v`{j1=-};e0UvN)igQzmcdP*(%IGJ8xi5-F1O?QP!nTFg<7kj
zJ9(9^yOc6tbb`(4G1L=d(SCd#T+d8CwbLsSAKxjucHKJtUq4bme*9=PULmrDiRom%^L&3c
zH@P0)Ek`8r=7+lr`6(t}pRc-l_3DJS_tMIFJX`whnfCi^6n7sVPARFp@WiEi5Ie9{
z*xjAwM0|Wa<;|7Gr*72D-))5cu9%yHuzM-vPHE|g&`_4~NqKqsyZ7z|ZwzVE@oJkqY`$8uT``dVy<>zvgBP20_?5=DqXGGI_xh@1XPxK@
z`G4T%`SRxkq~}If#KgqB)8p;Z7txYZ}q3%xGp{h
zcSiYGR8(6ZbFu6x4?^EnTyQH1|6(6Dnu2quC5w*INFFmc=MFn`Lpb1KXHU;!CiCA2
z*zxzWGHr~H9690|%u0QtF~gEAM8xvNWV#iuMJ9>YtU~m99n=!Sf#3yO+XJbm^kb&JMa5
z8NFy7eez_h?NHOFf?F#p*35NwUb4w7D)rqxKXZW6+1(xNMDHwhlN_w3Cha3fk5)KS
zpGa(ud5-vV7Tjf;vf<0Kqidc=MOAd@xy%do_4VO~hH@u$al0eaj_;Z+@Wn+q6Yid#
z22&&LF27zZrJI$3OvfISGVa;A^A;lY%-OTIt9lAe)6eSYRFnq^rZx^r%>GI{CM)}M
z)NZQn4vkf&Ha6gDm%sXVvAUUwfdf=`-n|oT$gmt1dFwQ5`}*~3lj;}L$>%fvFgNDj
z%n%!B|FD7YH*?viPx_NX%@m`EHE}_;Bi$jE%fG}Z(Ay3+6lGl>(8za|Y;~I4o_%AO
zWA9!M<8XVo@ha)X{QNUZr(to`J?dT7vhmGyualCze*V13By3*#Ek>dK&E+i}#omH<
zZtXtt@D-w!sxVR^fcN^-!%qSN((K2L@b~i>7T1f-j5!Zp{uW*N+O6S$XVC}yp0FN~
zr~dwiyrZHHZ;x46ysY=!DJdD&Xp!yx`n7!ZsS|Iew?vKQZ{k#oGC$yti)U
z(uMTZ#BWhfTV-f(FJ^CVKQ}+@5^LF-*L0)R$*A=nE=5^en@R@p=~Hj>?CtP}$isK~
zy;9C+Y>d-fPs_$;$vQdhn53Du8i&y8x4=5rDydm7e39>?M>0K?VHF+I)6-kGZoQDv
z7$j!Haii&KiHj58QjvH_|Ia#vzqU0hyg8g(@^Jehjn|hvGFPmUF*MxM)zw8gXwme8
zPZ1lQGt-}lqDafgC?Bg7Hdm~0@}!)C!iu&~o66B_XH=A%e|{~Ct1fFt*yPOrX_Ptj
zxP;?WaG(KBEDjd(uu0v^<^$3pbpt}ovJXhC)Nl&9Z}k;CS?ET+Zo`JC*RTET$GZ<0
zSF#M{FFLzXG5(ws&u)I$toyj+yW2+P@h^+t6!?&c6z%LpdCtF0s(##F!sc=?#b9DJAI86AlvYJ})
z9U3Y3>b`?FdD-{unZA--A9rRqlaT4L>(_-M9LLsSsqG|K6A}`phO&p>4Zdxh`dxiG
zJ|SWKFY2Z1o8E#7S;|<{ZncS-*|TwwLtH$#PWNU-)5dWVZ)TD1r{^u+8>OWhlx)np
zF{~88s}qR5=F6MfWs$)gP*&7lcwaNaB5eAR9*!YSS;e>`5@2U%XJEc%{p*-|PyL0t
zX(|@cFH{UI4g)-IEt=QMXlVu4PcDlzD0%3${SaMtb0t8}F`T)~U$4vLPM*Ao+-sMs
zODf%JDuzu{Aspmvjjh>hzR6ecL1BBO{9}%TCSP3FZQ%%{-tA-f?lw-XMfRXDa?o*P$x|W1F{dM>E*TpOTDC~!JIFp{`LuyAM+O`Hsj|{&
zqQCZ_WlJco=zzE*)67@p5>}X^HnW@#mHWO4tjWd!ZO#_u*J)
z&6Du(%IkGHC8wq5SIV3@LrcwcFs>(I>Ev`C`&Pbs=?K%(uH(Wf`up0fjQsoe#U4o@
z&C*Lw25a*7&Hn+b8Kw*`Ki2u%AYIGD%e~-Y>Z?nm#&_@EU+f4
zv?f0FO!$R_C}?VG;tRC|s8$s6_v8MaR`ncuR=0tMhLinw`C4nLLf0)*#&xFYn`voB
zLsA4Og*_eft2UU>*8QBK=ZHOsRo`sormw82v#Ma4UR&nQYU=*XU9_}fTl@q3A3uJ4
z4y*GNXYi(=0Qq#at5*+f+qP{&M|OMTTZ^u;7==+gi3yztq09enRO#it0{i^_oEaob
ztyZG6eIR?K*n26RckX-vyvf4?om-!66#l>3=YNmMpJ2=WzWzf1{h8sF=@+27^Zfa)
zyoDLFyxE~cI1;b4lHZusJyhV!ePUB3889+3GQ)fBZ=iJs9!zUz@0f6yMiG41c6-CS
z;k;R{y?fh#rB%H+d}lSc=IgsVkGfd_3ZBZ^Oh#%e7J)VD~dg^Pr+haK#i_;RLE0N|5fA@a%
zVwDW;?KPp?zH_IqE``lUdO`HenKRs4Z`|?6cj5c#{@!rBf_|a=B~;p^^BE6EMyznpu!|1CRP~azxX4es;UYQoc2A!r*1+0d_dhmOjcGfQmc4fd~!xY
z!h?i_eW6OmVO2{wZr82}g)%OsT?$XR-w)buVP-DN1U4(LJ81snk@Nga>g8&VZ`IZH
z@2>9F$+qpn&vuK6)jR5>8CBTL^u>Dk_^csBPccLo9A_;koH=j4Mux?9L8J1>=g*hB
zc2|Vh)T*iun$^vX_M4B(TQ4cnxM*(q=
zRlxS^+O@B8`16avPJ4VUV)2=ARXDd!))O}8sb%*I56jA~-mjK)Vc>f*w{A`#0SW1h
zZtwl}DA;xSo_M9f4VJ@tzwkZaBBQjk1Q3^De@#5t<`;l%t+(c%4h`qrsqX7+w9M}c
zyV0T#kORKdW}97~W=umWZr97~p^McoPBl3UBm?ejCrpk}(CC$E?LOXjZOi|at~uB7
zM2X4+(*UF{zu-K+r~stq8tnQL2nJO0Wmf+_S#PFQGN6U(dQRz?l12b%dXA&_GJju~
z9_#AP3_f`I0}8~N0=F06+hfwRw2?_4hEzEFl681EiyHkzep`J`)81Zqe;`d0~EfT
zk>w&yR(HfUMB#uOJAS-T^yx>iREopq6;-*FW>!K51NRhVqX8cNJ3Xj>ocfF#iNV0398QXThx*?
z4x5;8WwbaX+H*@tuw>^N{Ztrk$qf=PT#qtHF+Jk(J^B1OP0dgEnu4~=u2#0VaFGfMPckd^?T%Wv*15DQsN#pr$=Pu4pcPdEgR=p={$?5Rz@1heTQo1W>@SV%fOn^5x6yoScurdW*f8fgLFq#=9#@aw^m7bj^f|ygWRf
zsi)`y%g}D#d<3X@-MV${Q9e>XZ>?e70Xm$~cnU$&oOL})ztAmzAbg3)x|fc|hEsE{
z^DMf!Fw>JQJf}Sf5;b|=8j$*v>#`Mc^78r!+9yw*e2F}~f+T<7Dj8fb=?3%GsH5Fpu8mA++dW214#N=*ZO|aXZ-_G=D%%ekbjQr?H==hHb63DGN0LCQ|6Yq
zAZl=l3#>F7Hwp)A1Lq_%0aC(`bTfJyi4h8JKJ-S5J$^9Ke53Vh(KhuF1asSjLncyN
zdC<1SZ@$my$5faax3@Pr&kmM{i1^^9?&C|(;&ALw$vJCGckl07)vzHLeSxVBG8#$lO-#uXxXH_M
z1>iVID}8-PMe#(P-f0t)xK=wv4Won|KZV?EtMe?+cJXWc8D+m}6X^k24e?V_o*@od
zSDzA@|M|^Ln%t;bvR1ow<`2{W(1Po_9oCu7HbJFTpcE+6T>JO0*a33QZ1L_Ej?dS0
zGj$|-jns=pE;{*tuWzLrj=LNphrodmI|;|B_WRK>G5QQ{V!EoTMLG84rRC+(2w-iO
z`H2#Vs%`4pw~8+6R|E@@Bu%?pHqZe4D%z%}5+{f7F~TWQbaVSdJ9-CL6$Yoirg%Ph
zaIwI38Pa6lbT_kFimrD_$1>C9cOWIOI#21-@o0742yd|2x^3I`ajjLWRy83{65{W?
zOc81d*1ibHl8)|A;=~dYbT9RY!rAb}Ht9M|s3Jp15f#QFf8G}0L&nij0xZ&Tx+|bO
zRP1qdG`mq%_^E8$!H4$Y5T(Ao)HwvUcJ$)KUD#NWl3%um0<^8yML7Lo%*@P$JSTab
zNpQwd3IU)5y^XSFBTE}(5a>f8L`GbF0W1Mj=u3{h4SrRm)lqP9y2?c(-E9f6@xw5>nw381t=zJQR)#ml?8Z6GE8h0Ef?bq78qLXz%LlP`ZyVnix0
z9ECJ>6fJ{>QXy>x2b?!B6J|#zioGdaLCFq!$6L*{
z6i8@X?I;ES_XdW6QjtBB<%v@~O`j2eH~7oN-Y?H^*;XjA-<}`ekUx5B#hT5`%n)-|
z9(ALNPrLg(GSU?lg@~BDcJJ22{SZKQT5@8mn3$Mi@IjBcIY;t?Y+D{5iLtfgJymNW
z5tU?#LG_+MF9N$-HK$iPI#Nhu1HiK4l|{2S5QAw8mTE)ur?&fo(u_gcJ{ld
z1?N;$K0<1#y1i-xKh>R_9Eo5dv*ONAkNdtxosb#IFO4u{SdFc;%WaVsYUF@0#u?%0
zS6;5@D8-hVnkun4H(nBIe~m+YW??m=CTVBV5_)4Qi
z|NcE^XD~?kH4C0EF`9|C~qSg;H6>
zPv!8t_wbP;xAk7(zG$T8f1k^r6lZxTo~?TDO2ZSwvZrU1m1R&4gMxyP;~}ZaoIUHe
z@Qj!9UW4J0^KZ@d0Rzi}g~}`y8e6|5sO~4)|6oRICDsxvwFWh>B=zUHGNdcJwp(j{
zWZ&QecI-?oVck$_ub!+`6fOUl3*~C&cVBmTV#i)Fu^?Q>7CO3O!77PD!vG!IrWEM?
zyR4t@H5c_LDlQhdP~a*(-}2+f4}*vGgMak2Z!Z&SKa3jfJeoV$n6aoM#LmIt7Z^C@
z*#W?wZx?288IS`gGbCP1i?eD||16s|$NY$IA1E*wgsy>&D{
zRn9@yJ#u7uPuLCCo=_VlnaV!f?7duEk+?i)*dM7J9%dlc$)2GTur(Yhr}VOdAgKEC
zNFYIR_d1nS?Z>WPYrb4RIs{`~oZ@+oFvb5dAln%nQ`GeCF-!&~u3
z#^tv?)Q^W^=Q~hL@4C4y^eb+>UwEsqeX6*DZ8XK>=YNLokZwxxon9jK+CSm$yr~h_GwxV!Ofg
zx~aMGs!@kr!iS)r)CLtVfS(Y0K{S@QGg0Lo;6guJ7Z*fyQ|Mg*l>L#P!=3(U3bIoe
zgiN<0a1XYsD=QZ~Kkhm8(~}QzO9V4II$7jvvSdE%V
zL=Y7n?+je
zqVz6wj!%=5x`Cc|iCZDURMgeC(9@UXPPUYR6rHYLU?Ew>LAh!*t(ZZm%fd7k;3=P8
zC8X*T&d$zZbvd&`+1z@0p%oz_v)dQT^cHSc7#V;pk$*!qAWb+0MMW?Bxn9e!i3ths
zfDqpS>|YgSX@ZKb?a&v4P#;JAANzWOEhvR&|Nh;3_N;Q@aTA58XT57zqSa
zEq6w_xnL;kkJNST@1c%F8l4D065Rq=4g&D(*)!1J<%RrHXnZjqG}+Wq;!`qcYl9*o
z;5cRV*1Y}$$-3zC95*!VveZojvBI|8=_(6Iv+g0z(*&{(Orr)i
zxwD3bWB-0nT;Ai5kTO7@sffjCHfRhb0Hf1LibTV)pP#4`vudM2>0g73jDGd%5m;!8
z)1(fo)9*7UPo69{L*wre(UK4+WcQHl%A4&G>qQT?X**AM8ToiaN&beK_dQ9ouqo4~
zKKn+BJuh@*()ULDArLh1AJus$FYm)W3QzeRew%#z_RV?Rn8?7^+Kh_>xKRK)uE2
zoon?BHvmyFK)WIBWH0mu7*Ov-2*^ZJppbN+s0tuC6q}{w{t1alO-d?9S3?j~(UMY(
z+~NiBl)nh+37sWFw5GqWUB6y{_2#bwX|fSj#yJZ!1F{+#frK8J|9I7Yqq&jrdx{sd
zAcJqw^0LS#-dG(5bkB;RFMH!C?`CKJhz{j*-zQHl&2_LX^5d`@IAY)2iY^|&?R%jG
zS}Qh;c7X{+76{UNY|J`86;l2OcW-YY@$3DUBxZV}WI@Kg!B0vMBK*3}(}ro`>g
znd%%l>7_D3stEhr`6EVu-IFq#bo80
zHO!AWPYZ`C#e!f!O1bF8aNq+Ji&XLj-{*0T84)YOOd=NMjwA2a$l{Xl##F;HImB^KbOG?!#gCZBw>ffPl@ebK3
zbL{i}iaJ&_iIS4I_wC!K@#?~|4RqZ6B^^J1meYog(n!60XNl2|Te`JeP=e}>BTgaw$VtU!g*yGI&$n*|3rZ`-zK?)6@?Yy!
zra<32h5p68d-q6X1Fi4`XJCb1kAkvp{rV3*<3W>)8a;!5v7fU6%nTqJ!3yh<-_3?r
zTSGBiAtboQ*|`N5{lL?6ndm@L+FWsyg$T$DX&oS25xwfg=?Dv6&dXmSmr<~fQII=G
zDZG1kB~@V?>UfVQUtYn$#6W=ymOGp^Sc&$geOe>>1b3X!LmaaKSs`DR^h;XpG@jbX9>U_Hc7k
z#o3o8I_==*;%Xz%01gVYC9v9De0(CU88;^_K;jSo(@ZL#7(p=og3?gP53S>VtN1ij
zMBw|qd-sBn);P9NLtX);p1fJwoNBP<#6y<%rs>v=S29Szh8U!u>*b;I)C(LnLzz7d
z)Qz5>s8PpfA+zs9r-Wi;Q0z5b`{FjfC4V3|T|ojsf66fJs@vBJ}spW(%BtR2DxSwa$p#;3a;F4b}$1?tryTmwVftv
zWlja2#aDuGm2>z)a+-}{drY=t9dX-Ka_!u?)9A-5%T}rJXBJ(b{m~~bHlMix6(wJ2
zk}zaKhQn_TJwxT|9z}h5?Xu`hsg#`5&NtJs@AAjhp2Md@X8nXFT}82rw0h&pR49BB
zzrP%H7GxlqVqs>ooF5%xWWZ$sWyeE=uaw_!*V0W1fIM+VO-&XOTqcBw{?Nif+m2B?
z=W(rcX!S^Q)D+k%{@j$AbjXD~aRy5ZqK{ni=jJ9oXz0pm+q%Bev?~jm0Y$CBVZmz5
z7bDM1w=7$++6ubSOmha2afF@~R8?gos34C(5t=mXT>A>$dYlu&;-1}S9W&b%j4F$b
zqd+OW02*#o(0NT<{`BcJk${=kZT&PLqAJBc{_;f`WbFd057h1kvlIlf*Wz4{bdz-%
z50ssR%K55_3d8mf_sE`)G(eysSjmmq;sTi18}oWU$eO-^fkcIob0V%R<0pZE3^ww&
zs(MzKvL>|x#o^-%P(e|0{)ni(I1
z?mi`Xw=O&bI0DG3F21nu+H3TgajcLIb^_>$l%PJQ)aTy3k#EQj!57B_g08%xVv^uM
zd#}SnkIO=dB{$F$YAJjsj0Y~>C534f++HXi)i6YeryVz~YD9-4-*q<^mpk20eJxcH$PLjad|p@&c3J3>K5
z*#mfqkVQD3>j_Tp0ai+B?YSF#p#yD*D9~xr;_>pLA{yUM)XO}2{F{*8AuwLRQ{-Ku
zOe%$m*Y+9jL^(ejaWIV}A!rKS8BO4zznZfHT;>P#w5{H+(uR(@*Q$gNh9@98~Q_Ukj7
zFBuwMg*S?uP9dyidH$upR<0zq#CnYplluC4nNxgsBKUT?1}AR|;M3bE0~iiNPHl>A
z6+ac4dwcio6JWMtO}5>8x7i}4TKXb14wy(bxuXA98y{tBdj!$df0r7<1tiYsh}I0O
z0G8UT)-(nkRc8aNG3en2$R21#%^U3ig+Z%TD$>GdZEW=?=zoYjB+}V?93w7ehe7Xq
z!5_kIDr;!0RW?pi15wFnwq;Jq8C#FojDGXx2^j9jCWkk+vR;MlZSU8xT>@kyxgIIF
zgo??z3iz-ANg;;@l~DtM*XREtm6eslWc2?Eukc2kF;;hnrsoV50C6Pg@H;Mz`TyiC!WzXR;Y{!ReqNRifwinQF6d1FEXqKE-)H)i!#n(DFc(69xLOk=#obG
z?wXK?a1(kJeZJd87kBdTR5aaA{nOZuDlvX|lsJG$-~02Ey(LYnAfy&HIkolfxByuI
zeei}~p33|8?OTt7cj;1eeZer241qXtv!@_ZprE07CJ*JL-!W}b;o(LxXfd$90SF++
zmY_9;e(MWl8}RFmtP;JGSL~p_RmYwdG1i>RF@B#~GqnCpV{3cw!df@|z%oWOF6WA|
zz6jB0h@X!ij{$D~y3vBqd+^}FtH#0W%ZV5Zb5cZA3oLgy^yrt$%gId@g;OCWuD4{P
z?gL4iG`zVSW=2Ox=NBHXgbpCuA_?PpkZCAWLQn1nD-+WliQ?=>Mtz|OZoO2P5M$YMn*;u3)Zn@a~Ag3Cf*9xTzi5qcSuoK9az4d9F$jBt=fpgom-=iNxa4f!*
zB6%8kc@>U4`XX}<$Iy84g+i$u>vOAdkob)l+-{)*g-v(vK(Cu$I=iYzaG0-VC2jio
z^Bb8CmJT~19U=@?2+_=dS+k5gtX&iHDyOE9u4XHw{R#<6|EWi{reiy8m0XHG=wt(
zGoYDI1hlF%8X9t{s@qNlAB-QrVvj#T8+hMt^#~5i)hqMU=er<%*ddeEzrDgt8fTvL
zd`2jNbNP#ti{&xPCYx`tp$FgsHy&}65tt1(FoGBOT@*IYx#1S6142UE;53kvlMA~)
zg2)G=-*`W&GO(nB_!C80HsbBXCk(G-Qf3Vf?+U1>=z$^pVU4v$TRo&_!j5z`YJ$S7
zrbhIwZEPS?0j3^6tK|te6Sfm^SiO5vKdeaNiGqBXU
zjT^hce~jy28)6d(%JuMQw{)3h#=$(8QjI1?xXXe)lomxTEhduY)e`+*z2aX@!&(kM
z^b%KOG9-<*8hX#se7!PB&{xGU@olc39&-vJfjRIf9#c96kwW`M^Yw0(3GAgf&6SB{
zK)zKQ=*YnULe(M-qmU5T|1osXGWUng)QGBv_cCR!KjG!eZUh9HG&T|k
z4)|ixkVQ$?Mw^%Epoy|^pCX1JP~VZRrYczfwzLpBEl0%8t|CP`1QmO_8ejw*Y
zs_=ckY_q2sNe({N>2n4=Wf^<|?$deu6yv8#pYq87OyxCrAlchcjoaJxHF(tW
z=DV4>zi$ydTF^5A$I9u_^nOo7f6w@QT@O4lckkUdNDFsN?8Cad>CY|w8)w(igk@kN
zYYU92(Dv(OpYyu475x?EFMYFB+p;Cy;b%HhsMH!^U}eRR4eqd0qGPseKmO)&WA~Jf
z%&}t&uc{{(bB{;2U|%;Hp>Jt#why)y(VcZXFeAN-u76
zt=4QcWD(Jg2>6wB^qpjE%h>bQvaV~yz&?C%Xkz-5#s52Wt(Vy4V1AN7~?U_XgodZ%xG=R#kar2qE6cQ_%S6}&en@M
zf88*&Vln^TQu^Pr8vb{@s{i!|&!%p4kYEi}>hXAqi(LVm9&vS2EnRT@3CuSUqW~!R
z>81H5=s=tzA{peS@$z-JR{m-yY8T8eTXg<07`lh9t^s@a`&#}vw4UGm2mjBG4h&t1
ztpZ<5wXI-+BT*@~GK`#t5mqneuB^XBV}C!{>l
z5zmG1}mPs+NI?u^S`THg+nPkwty^L;|c%{^2WwBaLk&148j$COO}zN577nssNX
zFS%5u-N^A1I=3M*SrU=M`Zi$4S14UeKRkS&h7J5!hF^6O^R*J3e`S@#xZ=_^
zM3OEFG%cJ0>{fn=ZPX*_a*K=(E75<&3$2(uSswgjHMEldxjbk8{f++nvvB>hr4zxB
za7@U9tdj;h+K(@X{r(B5N|V^RayRG~q>}^tntQYJXJgK#_}R59Hs{<-U(>(@k;8~h
zA3ZWM$)@A?H&{v;ho5X@MvgX_XQV*~&yokntg&WDeXa9Ch%%XtWk1vmGv8?{5%#K9gx
zrsliHXbSn!QUbE9FdEMu;zOLEO#Ssigu>!kEOp<)KWMd!+IdKTrC%xmjkUmZ8orT0Si(%;y~QGZ
zOVN`CGSTLY!}owmle~a|1JqHpj&8#_^dp)*kF)2n4|DCCY~pE!ZVX}4`F0`e(O1u&FaoU{4e1#py{qC_$!aRPz*W(;TTA1
zr<7DU-ZqL(>1*r}EVuW>+wcC9$s)u2YzFS!zD;I8u#qcwU%9&1*6^XW+hzwzyGY@9N?~m65{|p$@2@97MpvUxjt~;F8;P{9LAqNLkJ
z{B@Z&Js3?OgS69VPEV8{Q*sFE?iiZM=V{v{WwA=taqS
z%iJPFWEI#@(80@_A@_6upZ-Lr3C{
z3K_IFqMk&Qh3kivh=$IVE!dv#;aV
zQ8vhM8z)8%NtVEbUeMvApnqgk4+rM=U}GH>=RaxeVeC0;##P|(9H81TpL|L2-Mtu*
zd&tK#t7%qxAzWW$<;s=YlsBy`uW6dBF&8@TGw5j;^z{5?BZqGX2jBeoTAr2W>|d`F
zWO6wuxcjNw<>2RgAH=oYUMs-8zO<4%Us|-1XH6Z`_OEs0DWL<|j(K+^ty*k!A{6}R
zH{jr1;%B%9208%o?V6Wnvf3UFj+1^E9>X}C=m|NvfBb`k6QE}cnbydG$|PGigLdyb
zbm;uh&=8Y^-75?*x->L+$wozqd_c~7138eaq6I5NA+*FtwRg=9=cm9&
zS3r9qv>(Jx+0iivzeF0${!gFo)S5Mw_``ar~?v|km2X8k`p!OK#jhY@#QB0lwTg}{G=MJhGd`y
zJ_XJSlcMKucmwzE-hC9;`{b)h4Nh$W>C$7!HS?7Sx}^yY{B3xmi_3B^uTMIX`sXwlOeh3~FxNE*_0ui@cwK
zvBzU?5~d^J%)rrKV%LrGk01&Vu;7S}7F3y6>L5c(c6F6T77bP2-}
z^18aZrqwUJsaD@H_=SFG13Cums(p)ANUDCwTRY_Yo3k^bl+x6Pu2DE+ttfAnE)2C0%pM_qWaBmmRGr1VZ
z^Wry#l8|B*5}Gb|bbebeKQ=j8hpO>BFfedmnmD`IjATuMYS~wlv6|Gv`!xF{C39y&
z){<*2IDU3_p&Nos-cOO^TsqAHFsB;YSnToWqNx@mEwS_zfBdL&-Z@pjaJ9U@;4Wa4
zL@(rUF{8cs%*4+>7UpLs0AxN}WF*46`><;h$Ky{2(sm)@@h;WM^SDCi#rYfdH*XHW
zfT%1d=MDwyH)g8(k?iANPZ;4}3^YqVnFT9yoY3=tT%lTDal{X9pywDjmc{i36kVJi
z&Y=Ap2hWS|QRA5cqZN5yO_GGqx4~QWxw7(UL_`F{<+FxK(b31yaeDme(ph-I6A#)+
zWZpfJ@XN)jf6Y7~Oo`Xpc6sZ*
zd_==*Lrtt(KOS$TJGqTXZ?2U@O2mw!Mt_4d&Os4WC{t-bu~CFC%N
z>eAW)WEwE0%^v^ejS5`IU&(etEB=I2h&J%&sw#CfbP}&jFtD+u0DeIciAVZWEe1!4
z1r{v13X`529HTEFN#d~qhh}7^a6^#T8}gj8b8>RF($mKR)1ptJh@*Pl+L#=dr#u@Tqgg3z*x(+?@_!RS_RA*j90*|YSfDZ00|yQ`%#D^*WgF?~={3XRnAPsaTsiOqy)X3;`>VoGkFypR
zX0Jn6jhGZ8Ye&)ME>D)GfrT(O`ZLXh@p|@`beu||%DAq?vcGRAUdvnwwU5-rN9^g4
z_8b2AsfQqHY?1fz3f-n(Cta6LyWyz~c3>@M@ae^5I9nS?q})t{b|ChF+q_pOr;LezCyt-~QgxXSS*QjW|j{{0}@G$2AdM
zVRcQ-AcPYBhkUnn)21CFNY(+k&X+QHv+I7X!-sF7=o<=$Kuy}l#FT)x)%5IacGepO
z=v~S%sy#!XMqxec2W_2zZB4&K-bz%!6|3*~u$oe^t;8Z@0C_4{(D)%4#z4U=HA;&|
zrb2ZN4-a?feRlsh#@{ouY7~ka8_&ay7K?s%G<;87+}w&tqc3?kV4t6@#j||Ww`MoL
zL`}X7@5M;`Xql~LL!bK%6KB*lq=x`2#~$vv4V
zC`e#iQLsxAsUn~=oI+{qCky`WIhw!ZQ%Qm#i3uR#D7;`uaqg%sXh!PtCZ^ziNt%R>
zYyz5l|BDcdtmsKgIQI7Bvf(qtv6%(-{KiK6^iSM={yYj5{BDzEla9{j$~GXDI#_SF
zvalrK@QdGGEib@8Wm@+#3>=m_q@vqz2K5lbxx4^fANQ0oc*zPsUrwRWvtjQ;@BjWy
zb;@~w$KO9-zl4N#^UZ7OiQlhmt!9_a%ge)9w9R#oM^A!+;sG1v{f6FkY((}|KU7>+
zrhr@|apear8c#w(5|QdYnWlffz+YNdrw$S|_WO5|b!ff0+L<%Hkiolf3XwAtur+{M
z`*?W#V`F3SObZReAdCs#L;j6Hefoq?HA>UOQSeh?Tn_Izfveah@_rN#s2uExwFyxt
zeE!KW7=$7Ssv`@7r~)As80mh>o|&D!pNmWG)~#FgEW9kz&f3uU6F1+rb8y(l&##PA
zPJfMuLa~~_nQ$EkN>Ag2|asIZJT2!21!1=0!wrDK-SY_m9uAeA-iNZ58X~kkpl8p!81q{IUb{rQ#qRh1E~|r8GweL)*F*&
z=%}4R{j33d7J_Rx7lVWZVq&fL0Hv*3xzYrxMMIjg4-6jHe)pd7W)zeq?}zUM{deJH
z-CQkLufoy)ii4fap9f6T?llUxDsPfeO}l}+9nbf_Gl
z9bCu!VJ^zaL*31K&eJhuLK%mzbGh?oWCc@_S=F$!@#kKs1f8YQ?!yW3kBD$79tDyD
zD%cB*hsKfCRN)b%!?MnHUOh|8Z41T@hj>|$q)0wA7hbhyjoz1UPYI7fJJc^4Q;Bh?
z`+iVt`H={FF&1A9W}l8O^u$o}c@$(UkqUsf~?BzK~JzrtXP~f!2*U45R09Ghp%!Fc8Ge7
z!&ignX_N?fW25#;O6nlJN)JzNK|Oi3j2&_0)BVUsU1$o=XUFFuFYl6OiIFc0r~
z0TtQ=64ZJssweEZm>hAySQohp_;*T|HwI^aA%
z@kaknety1I#^orSjrdd9Z%x73ckSA}N1i0-!LbdZ5noNN9pvZUzyER3MX{7|G$^;R
zvGIjeyg(r;tE7p4eA2pnVdhY_E*ck!a7HTWiWfZe(hRiMMcGQ{zxDgzkRJ6(&`;6Z>F2po`hZvAf0{Cx>If*BP$LN=xQNf
z?K_OZUogD`d3Qrwd;8AThV*TlH$R7(+B-AUT!R_7RjXHj%6My;ZkcnnkHK4(&_pZ_
zjv$W5p_Fkz#)oXuyz;Ts%n%?9z#VM|xn;yRoV{RX0B{hsfOw9r)S2B}QxCY2@BClg((ZS2l
zAtQVa3WXziZN+FMxh|NVm7&0f
z=}IHV3h4akZlqZGKX~ZzUAn}(cFTOYN}WaBmV??akRX4WT$+L;6Y+<^v*rYHrf!H-s$zN2&A#4v26Na$Ln;^l_ZO@_Q{8&3z>F0{03>?T)6*xS5(6Qb
z0$|wdi9k;QF0Y2nIg!6On~zhkVr~6e3Vc0ZM-Z3fuxSZ>1S$6X>ZYm7#xN2#hg1F=
zDPewoX9olE&D1QS%8Lt=`Fm9VsNsQF-q<66nZyYZG}7vz7&_Y
zWVQyGZ+EB+VckH%ur-x^{(KP6z!+@KRtK&iNsFZiuoIGsd_w5_NUOKZxpU|C$P?}zd@Ktn
zgPr{tgvJ?|R!C8X6ir$3!vbCkIDJ1Xcu(#{gon73+t|
z_7SNdL5dtia#Iaf?C$K8OQ1Rm7svJ#7mV=|jSd#{_PEKK9&yH>0NJ554nXuTx!_*?
zj>#*6Z1)NatHGq&54ib%gcKZEgQaj
zMOgT(LOYPfVKr4FlP4IjO}|*Q-rmlx6kGv@!a6*2=^1(nDw#ybCne)V^+((>Q8-rL
zISfl||F;-VlrZ)??;`;Yn(;7?vC&aqXqv=+gAzIb0^wI-bPgx~pjDfUkY$TDSxfkR
z!|i^qlm7;DALM#99`i@haL$wX#GJ<$s6Q-ejG(c&Om5Wf?9Z=#@SHs0GO?FB&;$Ye
z$fDq(PjASkqZfgcdzzJ%6|qwd>==I^%qi#TMG`WXUPYYtG^G^i30(bo47S!qKXz|6
zX-A4HxZb*AGCPZ
z?O`E@8m?rW3?=VfOqp3M+TFeNOWcq0@A>5a&I<|4!t1|JO#lA}VFmsR^8U{naj4Vd
z7-NMszbaV*cy9?6K>x)us3YXSP-W4*`Dq33o{eYzJc7Tstc>udW
zKX1iv;YGh4HBtK*(M8ZafxKW!QMh*;^<^xfYtNncZT;3(jAlPx?Q}Uop#(_c+`V&0
zOEeCd9uTF5qUSuCKXbMH$b6L-O)b~154Bxw0#Flp`S|$M1C~(=GzpxKV8r%OFBbo&Pa|tHbL*=oCx;^1tW}|1ZQ9@0MwMdpK}xu9F^t3&9hV
z01p%${{Z!OL_KlM_x^X9%YS+=LE1X_nK5~$BM|nd(H^A2W|zfz-Xx+g_Z%U@LXx48
zktt?98qgGh!h&uskwx%qR2F=F+iP2pAmF*vMERAKb;Bcv#MJ{<;^#I5gfS(&d#3>&
z`XoC$8_%2T@3-bnfNlvN8W)H%YK-l5B7=#pVLG;4h8hx_IDxpqQchWk3Yl@RXCbbx
z0}w$ENQ6H3l6M`sE*V^xkTOU=xYTa>e#{GbCT6|^fJ+B4LyPA4i4%#)_W!)QKwv#3
zP9L8Ib3+`|K?Tz4NXKI>OYG3HNpzgG%xFx4M+yfBr8n_Ox!e>Gs+}(1-%-e
z%EzdB05v<}U*9i8Tby)$_d>n#JBYp;YINz<3Q%gIXv1{-1>?*y@#kXIre*ZBv=XMr
zdj_D1t06|Q#6%_qn8H1s3gkabW}CK80CZuv@-iWBsCa~W;n5!`)V;VvH8hY71?DI8
z5+Po@Oly<)r$+qO>}Y9efwuk_bZ>$*^?>$>mlhwuE)QM-WgY#GGv?+=cuYV%I5k=L
zEIeHfyz7nK=*3(---Joh;SFxes?xG6C9|8UB2?@gMtL3q*Vf{BCg`i5Bnzy#W9B
zn1JUJkqF{qENGq?u8*jJ==s;c*aCoCH<}lkWC=t@G!$&)3(j!6BVYq?wgjsxFMWM)?BIsI34ukOoMw)!xC4Uyd{u_2BL_yj+f)f~^IE)zpSVHz=oi;6X7x?A;a7oFajzrobFt8TGPN%}eRpDVW
zZO%#uRUvPO`h#{69Q=9Tcru!H;bh*sdzWk9zLUW5e-%G9pjT*SODJx3a<~rd9U=Ii
z36J)x0c1l64?tRb;Nfw`#KgouOG)Y+W*Xqt)HVEtD<(Z@T*=_tBhjDvI|)C8DTgdH
z?E3K#Kv0q3e^o|ifM*8-09^8TmQVI?%y#V)6g)@TG3axF0Pcx@tyc_c3Azx26&hbW
zjEbw>j?xtA1`jF8(18EIiYj|d9_^D>%!fk)r=}Y7$#HN}M}N*haU3GJ9Q#kyBZwRk
zX?ikhYEMCWU*e0n{s(z)9@X>yzW=^tBN3UCGS5S%P>~^Hh7c7gQyEGqDn!bZS>_By
zC{4ReMaod75Sk4UrHuwrTd8g8JnroMUF)~jIqRI?`RlB8ti9Iv`=Q?N*YJGa&-=cv
z>%MLSgPB5G3jJf^j?iCkZoI;q?*`^Zm=LU;M;;($dMM@%lUU+#9(ztS!sssrG_aYD
zP6V)DLLW2P3
za`D8-nE$i@ze3x5n`{;57Qrf)S`;|K{HS_cbMHD`j(2|=IxX=+-0h<@aH3~Og8jvE
zm;w*HYW$&D({-()#z_)ZRwe*)v`c|mr!HNJAfQq<)U1d8FTMDayD>34R6z(9Ex-XDKU`d9
zjB{T9p;ri(NY|0nH`CAvc;i`RgD@?fek7Q$&TPX8kQ(mvJC_50`+XJ8KE{eHZ@9YI
z)TyTsM4O}`RhYBj!G`Gu({k-JQNX!o=`;|%073zz0E=T*4-_TBm1RH{Qz+h=>gaf6
z<#Ccz?RIWizcwe|Pc&@(j!vY^no33L!lDaua`*@6RirQWAW`yr}$%h|I}@YsQk+5uOhgg4pm>uY)FbzPEyZcGVW0B
zo(FbePXn98-%bDP*b=)Zj}AUwxbhmRhjZu>kXD4x{IYP7K`X^6^nBjq4V3#
zTv*uVy6lW}EI^wx1<4X{b2|=k?q&t@!zck&>g@L@d7*
zYWn)wvMYlZTKaV-a?>7@!RGB6+V7x#%RYbsFb~FN@9O*#4g}SiKN%6|dsrQznO1ZRb_1e5nZ7LBbP|X8i=N
zDWu7E{jYx(@w^ASEu{~8Q(nzza1F*m2&=-&0jZk|;h$sh+0w$|EWMhO%-%&d=yJtl
zh`+qkrCHMnTHo-viFPfrAYv^6?mX7l)>{}w$g?-8V{fq)NuNN4B%&jCJ;OF|fd7?@
zQ;;7{S@0;o!i=MJ$avES@1Y6;f$P}Yy!~)U<-5}fXU^FP1la}Zahx4%(XUZzz)|V@ex*w5IhY{70V5?
z4apr{3o}e4^SAw=N-`vbjATbd`7ns*uKM~j_#s>74dq7aDA*9c07q-?)PYWC&c68-UvTjsuH?
zti*Rl`_dT6H^@Lm5r%Yrmn_w2D*;0>kr6J)9cQ>-eUva9YHm*h!Z`;7H@BdocImyz>4PQW*eF8hffsckT8F^$_S56
zG?j#gE3_x+F#o3MH;KYa)B@B)<)7bF{W)v2R{h#i#{q?!AvA!pXQ6li6{0N~%
zK-j)=n)O53x8&@WDESaGuolDd2uOEM7GegXiSm4Zro$o8;kgu?rUkKpcJ*l#m3hzQ
zf(tW~Qi~Gi_6Z?*9bFWl3u4>aJ7G;}7+=U$x&N!a6kgdxfv3*Uj*xgauFFxQiooRTQUr
z1VNV{mCl)9=bh7!b_o@hkX#I?H7@YYSCDv)$%$jmlKDfO4+PKg5*zTHGl^!R
z$#Ck6JldFw=t6$&@4tC3$p${jNlDY}?F&Y~+&%ws;heIMUNx*@R$s7+UiPl6sHWw9
zPM+PXf7M$0D>+hce^X7(5Oq(-6;_IBKx~`l>&~T~8Dn1@>*~-n^}ZlPi2?|07-D1u
zHMHVMp1d&abpoz()gikWSDbAO7fAVcALVND9Q7g3l-pehqX68y?;&HA2?H
zXR$HuQLj{^NmKIv$f!Fd+~UyBNm|}py6sxJxJJ%J!Cb&iLZ=DKy5#tP?@2#rfs@tw
z{aJxem%e;>#ce5jZTouAw4?I|p@4OI@d9rmw26Ne_H#NqVc3dMEJ?F@Q}>~%&jms|
z`UQ@iYx|Y2GSr
zbeu7UB+EouKtEUr4Yw*
z#u>EA0oA$Q0Q(|0mJnj;t5`=1)*HXzjze^8tYAphaF$on
zxc8~``DaBbxgv5SrCZaD)dx@yiH;OxlMjer;FbOVRtTjix;2O1xKVv2@%FMHV(RPFUy?6Ssp9AT
zzlGz;Q;|RaPeoYOKm7kSaI*vL&(6Q!YBjRSMLKmq5RM{*M|GBHX7DSH*Pw-=SH18W
zUg5vDm+mp-5)Pcf7p)?Kbz~i}&|N^G&~N8NC5p+s5M>As!$6EmHZGyCHv^A>V;4G@
zr5N+a?-joDEJA$&6Xl==T(FQ+R#?bCXZBwM;Rl{A>PZeaAz0CXnaABjcq*ERt^)^t
z?VZ_2)ZZ{io)uHsv0k!Al$gbw{Bo>3KH7gQS0<@{8IkSn
zzz1a<(+_Xo9w|5^IdXI!eS!<3t;#uQ=ImHeLotniBwH`_Pm&XlpP7~pO&gsObr?O$
zu{UN78l5;Q=`j$}yWD=MxX^GC()KU`Yb5GCUkKh^t?GMs_pGg0|B~ezKU!o>MkXd%
z2Mz|F^zC(k0Eimca8+>_`pns>eN*8`_o-~!Xl>Ko`VL|?{^PC@UF@0L4m=bS!e=B_
z9ApE)Z`3g;b)F5TYY}N3it)!NawKz@G~wttPRX$&W?XptXS=%~BYI#jIz!hzFSX+P
z7C!L{1tqY#R;RXCxFV6qci-t-?TcStdX~9B|M7)auN=;ict{C4>{rRA!#%A6=^&7X
zg=f(Yp}HtLJ-#>44QU!F;x*F0Zcwg*X*|1q`!)<%TZv-GyQX2IaOjI@phTX-4@h|+
z7>)>TMdd=s346S^ayjiMg(;^tiHCx~59J
z`7UCOSJH3@k)b~-J6QVWy6p6{4m9s!dE$#c;#Z7-U5j4Z=nP(!cB_qN#{0@%z5&M8
z4mYcQ#l2qlWfJ`y$Q2d?rLS1E3N!!m-n`0Dou`$1o^W?}Kk?NHvE6%YfpL7#`Ep#%jNQ%VGK{;*XFnF_tivLMZ0|Pym9pU{*Iqs1(^r0F#@kt
z*BUt8WnxsUTX9(AvsKg1Y^$2pq3Y$ga!_X9$SKzSsAALbbZ8G!PF^MHH|%Ysv@lVX
z7j29L)>}!A}Df@GD&mpQtg=+KU1(
z;z#n8{uF2eb|O6fC@R^Ime;Od&!lvB{gh?CH0v_P4o5iA{l6Y}w7x2)qa?-7l+9?F
z55LB}hxA^sc21gW0XAL4gi$(Gc$1kFdeImQh?WWkqQ$6DckGi55Qd7;5N#3n6BEZ$
zgt$IE!(Mha|K)ZP*9ZFwr=iD%myp68NAL)gp*m$TuzBKrBC!%KvJ
zaGCec^9}TgXvz=;W@QG&+~L#Ze@b~mKBYviZhfLP2fgoA5s9B-<36L=w~WyN_viNM`nySJNZvnCq~AQNK35eWV^2kLhn!m`x@7u-#_e=K?mVL3YO-Yp0&^&bS
z)@@%${;zqxCMVW^v!^T)K`g_#XiZsisPw=k9aH~uAAaZ*m<)-#@&cBd#&QQoP{_xw7?3I_2N=O2kMdFOgud8sH#O{654UW5@B$AVhR*FbY
z95b$0q^6=g<;YE1tmi;#C!mt#0X8@eiRd$mP8!(+>~TwH=L;R_51*Ze1X`!RHVJGs
zz4tpUgb;qlQ2+%!SmF)TuC&d$xm_k%>w>re8C=SO&n*?}x{(jhC(MKyDQBuCoU$cc
z^;6OUVbbLm2msU1j5+ju%c_shr^*3C>o#vQc-F?>T3~Fow|w
z_V?GXPic7&%uyghM!|7t?koedknppwqllk@9S^WuhtWqXDH1{@LEZ$<gBcb2
zfx{J6>z%3^Yg)U)=%vLpdG=#`T1RlYe_ak_orECi!v4!T;
zM1?(42wGRBKP?u~9kCcM=4ciQVO{7my8oPCRe%-%9mySj@e*t@R%G|jDa$v%?z=p<`_PWnn5lUKETG0Pg+J?%AX(Bz4;FK^o4L2HHAG41Ad8Hmum0ak0aSOWFLZ
zq?eWqb_Qq%`uB5g9|7r{?tMqX9nrmOSN%mE)TWDk?LHGivmFP%JZHh)j;>R?c2=uj
zo?kx=HhkF6qfO<20SnRw*WGJ6PPJV|+tYJrHE;U8ee=1a?~b;d5}1E_+YVKgjUiqE
zs(*IvI?!!|<&;JpPiZ!3Z0z2y-F4G`M~_ZiyWaD!;}wZVyaE#1t?+nKs=d1Cr>Xw^
zwU58NnmlgXxJi?YK3@<%PHBtO;4YG{ZX8gf7Ay!_jpXAGCHLdUo??5t%9NyCv(H>F
zr7exYcNqVB7uNj_X~SmD+9RYq8phiQNqv#(<`x!qmp4-IgQ(LNGOZnE+O(Ah71N;7
ze8p93O!-DvR-(OMc~dJ9f|>-L2c)W1zyvdj{h~kdgXMV`@X!Z)NrcpZAl(xO`jH&c<)@uos=$
zfAijv-YHneMy*`2v`hB>#N3YU0KDxC4Yf!OVu~W;Qg}2oBA%KibqSr`y
z4D7P+vg@58o-jdXMu0kXwipSb$LT()m*Pb=w5!#i2K)mZmA;pKm^#+RqpXp*X@~9$
zI&h%LvY6c3tJkc7cpFjJsC4Z_KmA7X1C+^Iyu6fxqoVmCnQTj&c42LGg|ay$GI9(8
z51X6fT`I;2!@plkYEWKYF8;C;J2w%9NnB`qQe1wl4}JBvt4tFOv&RQDM!9&GOe+N&
z0$$uanx{+3%0{hU|7&!)6~*X*Z{stbJ{|v(h<#qnSMk*Yt!uH)sM_P;bdN^CQ-3r7
z|L(v!ANZyRuWs{Z8p56}i>&HxgD5raoO$;{dUK|pdzOb_x6kp%C8eb!=ncxQw|wjj
z8W8u;8-bTVht8dAQ{uTjYhfIpot+(d`ArW7zF|)0|EYuST>G#&g&{>B?OVZRr8q<@
zO0?B(fGqntBS+SxD}gE4_7zuIHjDMN;8$@$8m?Pa_2TIGpo`ysZXv7PIOfa5(=PwVmMRRt9P5yrVk@W{R~~z&%L76}RPkY?o70QQmA<_{-aMqC
zB7PUFJ|Q(t0&Niyo!j?`_RW6$-CF_WG+PtHSP9z{?-a^RJL4xF4_Ure%Fw(j0
zowRLykTFy+h8pz_jo*TL;$%gubq5}7rpa$E^^43F`}O@z)qI#3CCk!BKkjD2=Xn=q
zoX4?3#yt@p6=LO{@W@y-MaG6{lSifJ*XAhy)B0*--qa{YA9y!x(}2IpFL%c{Q%lH>
z?EAHm(RXdCmhWO%_9?qn&D!-iUsVy%Ke;YH|)IS}SD
z@ezLJJjxw?1A`Hr47XBX>fMV9
z4ddauz9TyyV78Gem3Pla3;TmzZ=l|ex_r5xqnLrUZ*SNza!jcwNoQ(Gir3}K1LM}K
z-pnWk%Op?
ztuZt(kby}~&d$V(qE098{kHwdNO!iYnRPR_iuAQc)VX!yrhtX^wItt%9J?7A8H$3;
z51W>tvwN)~ngiG?S#v5|wQ7}%E>`E|^XICHK9^*0Gw3G5v_9ft{Nhp_`b66c8_U@@
zB0RG_(?|Hl88_A$czyNFA?nCZr)C&EZCaCq<2!x*l)aOAqO?q(xpAX4Ocws*z80R$
zN4|yGbLq{hpA8X2ZM=DNm~2=3cU$JHaB~~Oyg9113z+tEmGLiMwxYt=^1|`3#SZb}
z<$O}RYTaN{g0l1OMpRVVaPldO_0r1!T46w@;ZziHDt;ls5ry{ONlhj`~mZqA8gtV-wXsi2@*iVW3b
zQkKcd3Npw#FrSn`xpZEP#WKnC#E`lug8ryo`!qKwH_pX#6;tp?f|6EhZ>mAyF!H_e
zdz$LEW@^gL4PSMCcz%ER=HqO&bAPC-tIvpWYPY^Jw+>I~c5-q?s`7|@K@#&C%{92b4&-TI^8IT{&qBcw8#;zuQZ
zo-Ew?Bns5&UdE^5sb6zg7y|}s8OO`Fe|xbV#Rh|H9%;9^spT$7r;%fDrJ^5MN3%WovSX|qn_#Oxp11wSGy_o;Ky
zt0|UC@pj5u3Sz(2D&q3X_pDOt!Iw){vaN%IyXa}D)4$^|sMg3+Q^q}WC)JJ}a;^s$
zlnmlCJvp@3q^Se|cK+tOcKtZ)+Un^wRn9Y*%3kZ$RVaU|kuCaw{>h4md)ZhvDIGA7?mx;q+X*
zY?;iQDtXjD`T6d*ArTRGsc*#26_J>&q-7NqTdj2y*(qDGnn6=?Yq6fOu5X97Z56C>
z+{)>7%mM$pbo^=V=g$ol36fM&%Pl>jqsx}Cxg;4y6g0@n$|~pW+l}467
zZarB7fyt)2zPAYqGKnqrug<>@u)dC7W}zI+cWUW`PwD#P>iCVE%;1nu*7)qSu}OIF
zpe{XTgFg&NZmy-(y;l82MXEK|n{W^T6{^+Noz5A~EcKJ7FVCDgQ@oxj@VhDEn({aI
zm@u`GBswzP0Nh=sX;B&nJS!^xiU@E*Lc&$DEdP~;n}UNsoa_8lYj{
z4av~YVpz`~mt`Ma#%4dU>n9W79HO(9jY@cdLEdH!%+4#C4RYODZBCY-yk}lb*TK8T
zY^qVSb^sBDLS0e-7egHe3OFoTasmB>jMbSEI-QHTH`?d??=$dp(#vMUc5jS5>Fe7<
z%x-C66gzF;QZagz2YL2vXVRJ5+1WZosk^|4AM;miul~}I<9!_imUZz>>WlDW9h(X&
z>=xFyr_u|i%$ehZo`M{3zO+c`%IFOK=r;0JcX>em!H~#R4sA_--=gQTk1vM*{(nbh
z@0eHf_nT?t+QVD@-@na>&>UFpXo;oymHE&AfB(Y=_vm`@IP=$0`?whTpGj(ax^+l&
zbY^NN4Vw$qk1BP+Qo5CA(4fmdwr_uWXS{vW|9P1D7dObu7)&NW7VG5Fa+L2b4Hc?^
z?uXR+9etGg&bkre)Kg}m+BUUQn{BFoBQ|c7sT(nUe37~!Wr3;chQDra?ORwFzV=nU
z@7O`y4#2vt%L%Wzty|9|U2U&FcrZs&a_RyNo4)^EPhxViPw!e~;aY{QobtDBiUH%#
zEzZl!U!l9>g`Ici{Lx&VPq_cKeB<+rs+T}HlF@fvyZ5}4+F>kpYNJL!Rc_aoysdDb
zT0J#(@rIFg8s1uX$sm^LX@>Rw`?viK+c3atGzN!!leSHRMveSO7rx*O+ra@ApOloe
zubi4V^ZE1q{Kh;&wFCS8>MQyy-`5{MVe;+dlO98PGA+!WQ`@YeC|DhL=+^DXx;NL2merlu
z{`9aOV2HtImQ<$iPx`CGrNYZBXk+@xPL5MT+gaXkIWT2SXr{whU$%hf{4r-5CHm<2
z!a3`&|ES4EZ>qMXW{(bB%tLnV*k>idnN#NYU>
ze4%`kXNR6cUI7s_YLwb6?DRDiETr6C;)dtkuYZ$GjhpC9hbi^nt*#|oH)L#RSlFlq
zqell97uef32zh^{iShH@PujNs)_>mb4QVv~VXocc=q%Hh4Szamj5(89quI}a>brNR
zI2_lpsof~GQ^I*!cH7(!mX($1Ucnn9Z{o}sZLA+JUlcuK?xmUk>kri@0(U&59
z>>Oq4fu57oTON^G#R
zw;HvozGQdh(u-YW1|0?sYQc8ot{2s;anAXHvIOs!+vnINrW{x0bH1
z?v(J%JzY<3i|kXsRsL!I<(A{X!Ljw(D5rZoM4Wa3@uI|ZW-=SAGVx|w*5{8OtLN`9
z{FO9i)cEmgG6+$7uv`5VSG7s$sT^c`UZCzOL*%t#^2kw^Dn#z7TCG~8K7IN=zn@%c
zWLN5>&9l#Ky>zL+!dQ&v6wrIW4rb?*6;S5Tu2~x~Se-4#8{kCe(bKfp!QmF|1{V-U
z^U`|Gx?CUG?jCpT_OU8`e%EBNkBq?9V~_`y($;Y5^l24<%syh$7-!3=Cp9l@o*c^z
zjISjuisGfA!oZjWP@xiXYg?LUs1jD(Iir!Sn>XXXd3p|2^Ga)Id9#RJXuZtEf
zvW39~uaVJZeW4TVPfqMSa>fiz`0Odw398?)i!NMO-~X18at
zndxv>ULsO4ytLjj%4>u1sq=%!bUr|#T0_Bq_}BTY?fDPy{QK_vEnO
z`0Me<3qQWO*@pK5)*znB!AtZ83^)}X-Au_TDq35xv-9a5TEAE4=_J3q^G7h0ps8A|
z$Q$1rVq#;niU(=!W~kn#iJfo5Qy4}JOzqq6bYx@$k_lFgr`%BMm_)HG|Nj)mlAOT<{8^Ck2BCYwvQIRuVwn0jUToH(x$s`FMw@+cX>P8qI{#=fF|gEYm{x^$Gw=(qQ)
zLq7Naz)nTMrC+MqrAwDSk9F-K2NFgEZ2T2%PE84*D8Of_3uS}U5(2BxWVm_EnFNOXoTsnK@l{MC
zfI(T9QWai9#uIYxT;iLmU#rMFa~cn8)@bVBf76u)0qF%~dcE_XV+z&^ica4pU*p)Z
zW0Fj<5pwaq+Wp!3EJl&=4s8PO6|CgW7KV4wu@_Q-qVY;>wvCJ(j
z3}gS0gS~zG*j=QQI~QJhp>6Z8@2btc|IO4drPj2rP5ylvKG@}FOCDVIlNR6hxQ(MY?9h1kWoV)o!Bc@ux~EAo!lDp%!@!hgZVrRB|?RuM9d
zvoHN(V|`TuuGhK8IVqI@9cUqvwETX^p4>ow!!Db>OoKP^-{XZuuuZH~C=PZG?s7r*
zwsU+?RRahTqNj9i3J_Z}<%TtF4mA~!zyvk`dFrQYd!obr{r!Oj0)OhbQo2M%MUC?h
zI5fT!e6DBt-It5?P7_UeG~~9Xrlx@NQoyfV*&ke50g2ZkR$4_^7+O%#QL^$QY2^eE
zN=Wj>?wNm1=}G{pkDRy
z)2)IA3K9>s5HP(vU+CE4v}XO<*Gg{HJHnJE;4i_)1!Cp-jo{4z_v`?C{_>QePT+R+
zI8v42&|>%rZNs3i?x1X!Y6^~^FJKtJ_8sn|ln#kpnm+EKJ3LRHS^d^SG!eV$G6lJg
zzv-%W!`A-}&>Nk!YS}~`K79C%%WI^QB^*^FA}qv6KIY4l!R>sne6S&t8B5e-kHJ9b
z`kzT%oI(q4OiT><`g{QAv6y^by6{&YJemXlgeGq|e!P{8k0Zlz%#Lja=OXBs
zFjrtA!y_y@px-*SLZekH$n%B;R+64_D)&LoA{$QW1AXi_WKCmK4R-;m6vfcL0Y~y(
zm?*h?v1|u~u9Gq}A{VP#A>4?+LB%##5w7$_JSC}|BKsBc=ybZXkW6R+)WL>P`Q$P!
zbN~9;N(qt&f$fEGg9i2fvVL}TP;^;95!E6h?Bd_2lgSto=!Hs2OWR0`vkIoe;n_RG
zts)N3uB1cNan-U36Y7Cy<-C9I4aj95N9d$kx~4*>aK4^LTeynmJ8PjeN!Zq?L)*>q
zI0l!XilAJuMcQtbqD1+uCK2Cg7D|5ePv)Yq&`?=5n>Co2d55zxcw;2mmwYKo$Wx{DEBlM1Ig)72&!5_Ll*ip?!VfC58Cv%rH8
zyv;OMil_>RR7H^?lKx+pL|a{BTrjNeJs#zD^1WxDKG5tW#3uoZx3K?r&eP~cuAW-#
zVx37Xd%v%QK~TY|C_gj21(K$D&(@_Zyu|ceRiJV($h0Katpo=evJ!~v7~%L{PI|Y3
z@}(ZT4P4yp%%}j5rtzeixkW`g<-zjzlvWAsE9B4HZ~l1KJBC-u^5Reh%RSt4=0;F-
zGF?@&#~+y=#54&GF2EwZlzz@U$+E0Z
zy}mYT@MhhY-Fn7nXs8Fa+&n&L{}?++GFyf~$K>r99OzrcJ`e-{lmZvP%8zTt4sby(
zv4yxn>l#`i!{REwao>RhH3K{{w$m||{p(UyeNefo!k@p7;)l2P0jxzwMdgrlj+`~C
zmF&Fh)~f{hPfp&-oD8oTHFF9I?5_+nGSX2rh&d>r<2*>*oK~zL-bZA-9Im>7G#c;z
z2@Y>n6)AIxyJRts{?g5=IhH$ZYm9-g{6`&BYBJg!wo!u`}CeE)qKbNZ9rUJMXFl
z7&VmGp7!PuBc7``p+uV`_6I;c@ZC{_6d~pJHl~-}Js#qC%hA1^Qx;edlqE
zA5z&0`fk#pgQQzB^_SXSRaI4{`#B+2$^lmR*i_pEDPe8;Dm9Gf($naKi0kDX7K(6NyVeIP*uLANH|?33OvXc~
z)9hz=e~r)5#fyhC8=C~0eG+earoY$M1qO6y?}jyh`~LXyF{EQdzklq{Icc$(Mz~dNItV9)h2eTKcMok{eY>>8Oq%uJUl;PKV
ztKa)QdAoZ1f{h|B4%)mkwRF-A(1DdJFGXF4ccjmB1o6x3s|KKqMb`3Yt9>U<>;Y>c
zk#YUU49>Yng!Vq@D~uItkiCETko>vK_;soJjR$u7&rb96IERkrE$-}lXMaq-JO4rs
zrfYpP>oXhgpUkPXh~$eMlkB$y{-*_S+zec4bL1k9HzJ#Gzdk#Qb+SdsJ0;LC!y#JF
zh`c#^+9p%-Wg_%jM2h>z%<@YnBq&k68)lWZ1Y0?L*qd+VT#1JXG**p!H)^mPs04+Q
zuV3#ORlG{K|Lb33KmZAcXsr>~-EGR&z-~g^kz&P@S)O`UBpI0H>@~G$=Iw>Ju}*-;
z{a-JB)--fC0y_{?!moF^PK~=*obBLR<|9KSDK6COBua}Z-4BI?h9)3)49e``;NT#~
z=6pQTD|wB9L0yxBU`-3xXtZci5uRjsHjpO(UZ4Rlw3IY%FoRxnNXsX@Bx~W9mEp%u
zwDnDD)S^Wl7Mb0`g;3t39iGgfCWD^KgHs+(BeLGl+;xU3e~=_(Wm&O|8MdhiJ1Mvs
zNex99QX9DCIP;t9&zK9K>2Amtw~
z?m>?}4}qlqy2?Jyd(Q9ziPL~`M9MZC3RG$p5*t^mUU|MzR=rSVa<_4gm8%CHf8063
z3Jyq+6gVJG0*Ki&Oo@TZy$zlckh)kjGIFZ`O{m=J1Qxw=d%0B99%Qp6C~C(gOk~^O
zOw|`9@1Hht&8b2@MCd5SBS)gIlXuJvi4N`Cs}Ki~*R_$$8!aD|q27#nLyOqfqwE}Z08CMcpu
zh`j#QDsJV{fvr?jR01=5NFslYzJzT%c3d1BIp^kjRdw~zB=~e2xIAf*Bi~II^6KK~
zXM6YW-$haLfI030dt9NUaoqp@ho15t#%pclCYT2B1bknf=DW2R6=G7DD(F93iUr>N5qUwux?L|BH?72sM
z5mWEk#hc+Rr$R4GdD-4lt
zUEwSlQ?CZ6dI$Di<@n>;!-fs3{O2E&@2-YAqWYGK5Y^(vmvy3UmV7Np|6uu78Rz(EH5eok=Bf=S?mk`n@??%pCg|+1A>0LA
zZ_tA63;Ib55y0Q4oQK=Q^W}+s$xFV8}ucaXGyXw
zwuEbeZ_O(#D(Z_H132qf!eY5`GH+ohV)Y
zHn96P1l&$!l%uCi(V)ljjCOfa=X4*UAc~q=gm})
zd$VxP(7l4{4Om8XA?Kd@AXd$pUqkoY|3Fd&*7U7SIg8B)~3!6{G7!*8goA!PC
zHZoRS9Bl>WrJ}HqlH<(iq#5%YINPj2$*_@Yw(HlDb(xEg)b61g#sOEawxp@BImaLR
zZc%e*2BD~U;du&>fd!~xtSmmMLIY_{L|Ei)Fq9m4_9ubDxdd+Q*zw~;0p58H>{V6{
z9NFAhV0j*qDC%Coe@szkcE+r#_bGG;HaV{uj$XnSc;0S32mk=6KA4+Zp6loRVU0oP&xO8b{
z@ON?sVcLSz6YTnpI5p+@0N)#pOLl6u|8~i?n)A$l54L)TjUmc!M#V$lAO{HQC5n(fkRl);a}h&6kFsyV44E2Nt@qHH^cEzkU`5z%vLPue1jnJsrE*qn
z*w8l;bCzn^hR~L1B`>V4SSHv8eTgaxr)nOVz;T!B5>cs+=ldqpMlw$ZPNJ`=rAR>J
z%q=M?8O}5?O8c$Im{i+=fb0Z4=|Cb&FU>6+m_)HlJKOw!{(c9<@!7=#3X)PVmj;SE
z5QtOF%v8uwILmiw_EnL(g~rjoOm1RG$Ou&ekLopy!7!MO=PcPtT6G#7856AI0pL`3
zkD+MoR!B3weB3A!Q-C!p(e3huzkd8f`gO6M3K96mkH06#y>a)z6UOY?$k@W}+(Qm0
zW+DTkc5voTNN+b`!UTERKhRB%w72iZ#=}FQ7ET}5ok$NGtY4PJjM3;I6I&Z7vdpFZ#jHf)kY-LV-4a{f|X4a5IgN4}c=ZE5A
zb)piH(cb`2Cw%2D+9%f}?4C3)*kybxDRdLzX)6;7^Y*-s)TGUS1
z5_o#{oPAA`vqY+SPC(Yr238Dnl^Ws>wh{ge25C1GRvk9E+p}d$m)>Q>-v&WISu3|}
zeT=+;L<9hm*CZO9DP08wV5~!3a1i-aXhcMj(5MS@Xd#kQotgp-5J9f(W*IvtcLvs}
zq6j7@U<^xyp0ITrn)R@N1$mL#55e}2FDI);vDy%!8%Tyn!X+$#v|*usM2NQegLLSt@yK9F{MLqn?{$gP{xSO?N!@?jWV_ii7|EiHG_e|*k3bovhI%aQE<
zJMn)slggB~;6|MZS;bGXv4cZG*NFb4w=`L`D4$4HN<}w{b6%tXE?F$hXY~{r059<8
zd``U6loB|(Y~ym&l(z`gKTc0);3SA#BXZ)mgmr{1b=z$oH+gak29wA|5`|0>>A$m5
zG*G*@K>s2l%hREuCfBeyRq>K8n#~&Wl(!RB)M!x=n}Ac94na#KRi(7rCXjcQp}%QQ
zJip0EQ-L)p4VPJdpfuK1w&Cfrk5P6@hdJeV5i~SFP^osuX01nGOwVtx*6T_}*w3Q7
zfy#HA(iRY|on#vx*gtD1cR(p<=6P4E%6dvSIavb>_M(3z?P1fKez$L8H@gl1CjaG?-lAbcv^ehjlTYe0kXLe@?}8g0JEn$o
zg6_*NUpMBDx3%p+jfO6DH{IxQ9?(O`S`{yRvU8v<64@`Evu~poP(FU^s>Daz7EU+@jBy{%-GJ27BOGHMN
zW#&_hTA1L$`4W1wR?3aQ4{Rah!4baUi7O;oX(`
zsWzY;O#xkI-dJZq`Xg#pdBN2j*-)#XurRgZYujwv^Pv;T%WjgFs7qT%l2Q6Uo_|5~
zyTIDC18%)?WtDHDKX^B_IfZW}%YP5%KTUYBinMCL?JI6Q#t0lnX~5Ih9JEXu%zpl=
z$FwckTg97O+AO$o4yhrlUBj4Js1J0v#b|&~Z+_wE?c>vs4&vgk^q3D1&s165(BOo7
zVYhCJDN#uT6)#AJ@yQ|2ib`P|M6@)#sms-Uu>XOm;A#WbSm1{M(9jV2UD5l!`^N$NC0Zo*N+#UXzN
zbch1p#Z1ogQAV9Rk2z+1k%n3cL-Y|y4vN!QU>@y)-gFYiXJ$478S(w*M3y3}OIk{5
zC~Uo(`6tzhDJQC#;;C2cIjq1Y0cn_T`Q+*?iK6utRZ1W5&f+mz|4Lb*K7c9HzDh#?
z-O=zrB0U*wBd-`d3E?>R>GoYqOKZyX>3_i4P=gwWUW@Tmp(m_{LhP`ucsx`=<784k
zlqt7vHMRp}QiwxU$;hPZuY6IL6Yv$~6%EHNqWUEe=E;pokxF5e6PTNk-j_m;(Jq}h
zG|Bn)?cFQ=0f?e)0Wc~FsiKmT1AvjQTc}1%OzJWmQBkOo4m7oL;m{fb)TPX&Kilm)
zjgijTuFrDO;`e4e-$nqYA6T^;GZDpRZmHCPfQT%Anl(mSSTv_;K{Tizv*TLumazAX
z-vqN2ep2$=`qgB5$V=$kwmc4!Wl^!~{rKf;ID6Rv@b5{{`7?sr^UB)8LV?lAOv5u2fMg19pyLl0ooF&)o@ghXV?DeOcBVql@}Fg4;f?9Fl;gU(rtUQmE{-Kn0oW8yG&J|^RZ=^i(rw3qwzPrD
zSk~Afk*s_Ocaa*x#{kj?n1yOIZoHAS`jvB{P7HZ(16M8UFn{X%Ia`?G*X!it&tPu`!1T41>9oL(LXO5rXVtRa_`oEki6hA5$
z6{=@yotOStysL+2ss(sh-Fd;1L?W+F=IQ0-Wjbw~f@)Po2uRV?)0ipgDm!b4U_1DY
zCCtANK+AzrP2Yi7QJ}GjIkmj-TMRx%V({U=6dkyk5G;*(OzQDXByFDX=3v8C10OAu
z20PXzxsZ^5_I8Nb#?n#X_4Vw&n~s+&Np5oJ0){izq#-`IGnsAcKNLDTY|5^DAWh{d
zaPB8?929@eeD>@NTol`wQ`6trizb9diUyp>P>*lVZJI1zeyuX8^AVd+5N&qV!SV0b
z1aCmF&`q=D0EdIwdIwk1l~JD<0�-GYAeZ&aHSOv<;6x`JWfqLB6G~*z~~e7XGRG
zjvW&%YXH6)G)x>mHnwxejxK7BC^C`@e%OB9_N4uR2ZlfM_V5>u9H!Dw*z57nD>Hhs
zO#~U{Yf$INUdQE-iuk$z9N;mgp#Y+{ZP#wZx2iqHr}obNOTG4{j6Y|nZot7$hHmp5
zq?EwxC_8F1%{kpd^yA)aq|E`iYo4A~@;^g}E;uoG0mi~M8I}h~R|F|B)dJA}vS+~o
zmoGPG^C^ZEhWVQ1rAg-6hC|PxA;8ULxM~fBnJZ(Ro%>R6l5KcAu_sVisaZu?Ee$^V
zgj4YOwKe^v``!LH)f=@Z!e^Ua(gTX^MaGX6WL9RH(p-Xl>bO%TTLn4;He{zC7-~rZ
z9r}7t?GuaAfgx!0p*3fp?nx=NJBvPu7^?E?+*&7PI!!`t2ZxAng2+a^sJ`M0)|1)t>${urA=i
z=(w{9bN8ODD@kP1FkQ5d(DnONHbm0J+m484tO}~JO6!v+RS2{e?E$W_%M-)2hp+8$
z_YylT9?c^#z&KOW!^Rt=?x5rnzOodyX~Ij$5P?C8iPJe
zAA18JKRP+A4INXr$k*HXr=z?>fXVvn*riL&#chg97{F>AWJac0gOnISP(agP%&wPQ
zMMSJY$;}rxY`_jB#^B7vpQ!ftq~M5+jjc+2?cqJv{KL;SRgWgRpX<1xc)oj%0ZYmSbsnq7}ck=Ie
zVBpbzezvhYnxq-lp#Hm`vAV7M1bZYu=-B_m%Jp}z|H7Fi5JC1RpP}DEWC+c|YbstV
zRmCpNE0IF94FBizXBUD-B_X~cIDZ5184$1o6xiV*5z(X92~?*7aFZQ
z78no+v4vsbWstjK?Yj2!fOL*Fr^Caw*y9r5>%
zz`=c0(l+b>Liw_9@C{`=ZgH>wySzM8%mX+wnd#^%_wi~_#ZCX~XE62{8!?EAMFtJa
zRQAOvS>?7lP0o^<;dDBJg%V44F@P5Nih)}f1t3uhknEklq6rwyT3|zpZ^tP(-20m1
zSSq6lDJZxHF`dK_wPv*A3p0kzh%uOCZj3@K5^IH8Ev$2f-oyVOm`r1a@Y>?YLV&={
z+yRNorTMG$IqY9bneMeLJ;u`k|&%G@EDGywO_8rCe|f%Q0?Jd5CFnK{5m;lceggm
zGJ3l4?)+5f(+Kt(<})V4umhzN(uJI@Nc<|fBaUY=aisA@W*UC_`3-w^an{DbihCC0
ze3|b{7g8)I&K^Ts@9Bg3(9L{~?B^hF2@E7|miai>IoI$t)p``jQwassXLz}|;UZQ^
zBQ1ZG-4q+B)71W>pUqwy!R?f@rixGoO{K3^?A@{Yc#z#M$4Li;M=bN*wdx!HGYjvB
zL9d)PiH8tOrnqx_zV>C04E#j3RYca10&!@$JnIo2DMqyZiU&W@JBpz{KHZsoGhpa-_wdQ*UTal+ytF@X*76%OJ>1KmMqAD~
z6Ewls{pxtX(4Oy|77br*J$2rxShvDIQyG;oV%4ip#VdYAjqKDZc6q*$ntHwTR@2^;
zxfw8CeQ)0}bdAesi@@09X~;!ZP4Fr#bddSu^Dj_HjwxR@PN%_ERFp-#TWPduGv{3S
zNa{}hceYJ0(rocbBdAq8SJ~gRNs}`mP!(1Fropl!fki7;H@>MeA!jlA95JP@sQUTi
zM@EdZZN>9ioZ4X#5$3B`$ISOk&rEr@q5!M|C#_G7k^ZO=7#P($|*Z06f^gob7dLw6q`5-E*z#USjYfV^6U7L^G}2rZRg9o2<;Vp{Y--iVwrg6v4M0h
zoNaPpVYybe=jZG0A4?N6tGtVsAwcchveWs}o7h}(yzPR?V(LW`$^Gts8rYdCG{MO4xIQ7KwfzHe&
zCGL)nj@OU>d~@lABN5JIQ;lvuT{?FBE2Mn9p~H1nD%e?Kwx^4W%XN#|V^{te*<|e7
zqM~r{@+QYDzLb0;Gc2#2a%JO}|GxT9&=Xuvu>z
z(ZV17_T-KW+=|@pEHDCs(zD!jsjhgEacd#&)~n}jx?q0n%HmUjcCn*#^Q%o!6=iH@
z*rcM`c}Yy!d}?&Jk5k8gr%azgIxzkC<)ztG6%2>`-k{jWz_rhR-xCHd!2Wn@WaDIK
z7nl{jylQK3#NB^3U?#^^Jnk8G+^U&=E9!UG!n7CJOWQMc^|4RiUVYmBw$2Rpzw2Ob
zoOkcFZcY7p`0$yRc-FkA>pz%z9%)IOXkxRV_bt)mBbv
z-FtMuCbN$euXMHpfkM}e1#4($w>nPSuNLK%@?1qg4Z;;(XLLc+}XRCpJ&9FOU(*$;(z&8ESVDe%lEN&NZ7zkzYC
z+o(L5OSZ^-+avUUzArXY{6@-z8;}Y2xcWJM7cp*`I%v$
z?V9|czS8AkflGHRdr^+P)~%)Ao8)8(^%l=Ce&&7rd%2xdu=b+srq7j}gWt$m*m>`Z
z`zd}4I1*f7ik6^Ess2@Pp2cwA)xSzwIT@$2E{=+mJD%PL*Bq(g7scU0Bj(yTh8&gD
zNxj^%%ai%142D!Mq?nkMcj|s&NjRPv!w1OUIeB+*jIWD2`cZJTeWD7_4#k$b?e^)uUA9vovZ$&
z-`=e(y5>8fPp&gF+ppiy*ShkF@oj8(O?`4gJM*cb3;+hfV+74|-&)FMb^SG*zdTB2
zQR*UyoyTiApU;K^XSVz`Ju+RJw;`VE=L8`#qJFBe0(o17sU
z&9%bz2DCM*c+_8BUnj7+gN&wa^ZIpx3nTBNUN2b?6x6*(FY`~YuUp01ZKq0-44{F|
z;4s(YPYaLiJ5^>8@yoG5ahfRaBWIVnl|}cpTWro<|E9I6AUDKtp-Y)tUC-xeq)*TK
z_2K=n8#QgUHml#XoHp$Y+B^2j0~&hg<>nIZ&E~K8n~9x@cC|&azOA{r<%Iq2Hfgh%
zPf@aBfY%4)s^vJ;M1M~CHMuzPT|cX@c|KNg3m?~wXv1jGdb%;gbqw7OUcdD#c#pc0
zSna>8_$?%QdS3l{&eMIEY4Ef|&6F=1Ulyv=nv9OWN{5O&P
z|K@|7(suRbxc+^qqz!znsnw)OyBmCb^OrX?Vp&
zzklhIJ0{zA?K+4f6<_Q0$30CC(oH@$5<3N){uYci0Hagk71g?RR=SGvwM#
zwXuo77L&2Kv!?;AGGB3sI9b13P-E<<=UxXIYc?I_uI6{jTGvY|4BA2J
z3V;7z3<&`O?SWez$T(9s4y6}lzccFYKL~3r3
zciS5Yhzt#7To_X^_dZ_u#mz*2lIEov@r^LdU;Js&$t8K-yO9P`DHH#5q!|(BQZ^lO8hGONI{MQGeY-&GSgoyEJr@Wf@{#l^ja>$II=dN4W
zCJw<Uau
z+cDliPuFaEO&{d7gfVZCF>lpCb#+!{_c(XW4D4^Zo!wvdVI>(n@KktO^O-Zd1*aDj
zuTXNLoUU4b`;k7Gi3L5S3Sv1}Uip-r+0V$PAR_G@V!qF`l5Jj0@kNxJE<
zBoWk|OIQqrFD`wUdS#`)w#<}}ArdBLxXI%1hu%76ZZ-uY!l21A@?`p;xh^tgN=wWA
zjz<+}w^-Dr7fgq`?b-9-^a`hrI0;)U$^P;g`GGxGA)kYG
zkrZ8~I|Kv-40B7!aV6^5^GHd)cf8VmS8V2_R{T18LW8Ym5{k$;WXKo|AI+L-|5TKC89c84W@wjA=}!3BWx{FQ<%#&RhwVhXe9G?Cm(g@TiTr
z(tYUA*Vmsg!@V3F{Gn!t>d;oZ8}l*dc>at=G!!PKE}A1L^8b(O-aMM?{q6VvXg9Z;
z=Ru>LXjCeNMu`$dX;e~*R1_*SXw;-Za|tCBq7sTkDGeerm8n4yO0{iizSlbU
zS?71oZ=H31fBaf|-QRBX@g82U>vdhv>v=t&ZfDrnzp1vdoH-^I43MA7gG0hh0RhSz
z^hoL?uToMM%3gsBD5)>8Ys+57#{(Hs534TOFZBj6hy^z$>V9;;LlDuN>c#OSwuVR`
z>VpF0Vxx8Y_t*I!Uqnm>L7Yi7D5{3wUg#WFA6($7_&nOpWvvE73itFp^E521?%IH-#?>bUxW?=D$NHq{YMN15@M0}D&3lzYl
zVv{|hk6dsDPp3Tv4ZB+^eet<~x7V&mk8of^F^_U3`(j62hlnP+XceOe$Gq=NVmFQV
z4izBHdz2$ZTgjMph~|rSx`?teT@m!jDshP<9oQ-QbkWVtvrb4R@I6j`JaeJBdB-t`
zYm=!3XxarfjkV~oZ)aGCg$_e6w<8nkGJJ*8J!`5fah}jzlJqB$&{mRM?9%ZCUg-95
zI6C`Nf}0JHw*+V+C%l9tbMxckY`=aEHW`8JEE-m3fGR^`4ihXO-9>9`xGo<27L~x(m{aAk#EoBWjRB03JDC<7eD~{kKS++Mx8ZA
zW_$un0G!1dHY{UT&4zp~7a+wvW?yN|N9OxcY={W}Q$Mj18}9BJMo2!AWtDzAf79RA
z?pA(EK^Xxsv0cN7P{G%(nNHfd^M`G6hZNV^O$ej(8>njm^UX{@$T-HYpuxi6PFo;a
zoRf|tZe0EGe533mYseN1jeS!_S9&HCx42cu2QLZ(Hj!{mIdz_+D-@p7ds+`Cgx7|z
z=8YVQ%vI2~F2afGg0~=zy-0M(WKbJP+^}jz8S<;yfD8UaviFP;&0^a~;VlBctk9YO
zN_$x&!C_(M=$|5I7y^$#EG+q5PGjE+rm3Ni+K!j_@<3)Wm*d6B={iKiz%4*rRe|r4
zUU-S
z8DR5Gx};hqb&3NH6EIJDE99a!=(V}NJ2qR+Gw}cy^&J&?@A5^FWtLNr5&p8mxL6r9
z7`W*60+EJ>I{23%&_&%Dvh-1#I0k~d0GERHh^TD&-u_`}PF?MUcn7psl!^*-c!L!>aQ_=Gi*&vBWV#dwL61ejPxN8!&5fr#sZAlq88H&Ln
zUNFXxgb=)i1kvJ5##hlhEcwrtMP^-9{~9yq_QJL+ykn#6^8%v_H%8nkHxG#no4c$e
zRW?P8pM`d$k;&|tGcBS|vlpJ}R1R3aA8M1APzI3PnCex-FsB`qB;NZGI+|}CI(-}$ppv)!)ImkGxGawenWnIbff{Eso6yBM1D
zlDebZod3H)FpDe(<=99frP$AzS~T;duTR+q8Ip1zfA?#5UIx>bC1R`5@&s*0xtRY}
z;7?C6u3zmtZ002EfE9MiF+U64+O<{w_;IcKumj1~*D1g*&%62ejdJE#{`yN*Y#7SY
zu5Kr+Uxy22GV$2Ah%vuDPo(fIXL{+_%<308m`zTaJlT#Ni{|pAxXuAYU*4_t{&XTf
z;=hAnpe^)ry3?Rz9dha%5)x8yxsmK5fu$)cjsd=cp_M!D%m>cncorcfi+1D&<
zWeuh)XgP4h>`B%;)zt&yX@k$ZZu7eCag!JsuKChBaTm7>^4A|ASXtZI
z)Hivs85thvU3&m$vZbjVaz}WVN`irw`9d;qb8Z}XS|w}eWLVO<80|=$E`R`E@d-bt
zX(ue!osuoVP=SRY!@}Z`kTAv2aE(WO(}Ia2@$?=*g)J3P7aKZhOpuJ9pjoylhw;U;
zVnx83q7!gO_qo3cmPr?*qQa^wU*G9>P?Z+Z?zI(iY=OR}+|mNhO&eW89IRcP~!Z$DU-WE1h?sJHh5``AP_qIkI*N_wwJ
z-_JF2U7GH5YRdyEbz?Jqx|U6BUJUj^5|7UE$H;#678
z%VSmWv*pLOid0SbJ$0MbF2`6|+qxeT;`oNR7x$Q6zC>dI1@6Rx
z_Scx#5r;&l#O5O(mc$o42Y*<)e+Dl~)CH@{J(O4L9zJ^1X+lW{a-av@-HgZvCGg3&
zNgj;o4(7-KNVYJ{|M6T5FcMndzyF{-%x%}>Wf3kMRe!LlW|^7cE{!Xl7#sHq>qwr(
zw6~%2_H?EaXM=Z`lbguOY1i&;i-E@G6yOUtewie=yrdNJ#w6PmCpCyT=RLZ+8l-Dx
zG;%n86*FU_DbGAd{+`A{nEhb?pOYp{R@2hDamTY~>KF)s&uIId11s=U){Yuqew*-D
z#$%s_&@yjgHVGryE271j^abUhq#mYr=UGF#|2nc9W+%H6|D^|1PzBl#a8VmQeYoul>h5T%lL1=-4m
zHtfb8x>LV&Y@E;<_ko%#iA%^sW37#5&O93Xv^4$s$8}MBd6y%PRzFaE?-oz#NhRZ31@5+32GhNwk_&j<;riE+--k)sZ-2P
zR}}nbFlH?-v*I!+BJf<%QPOzU*+G{9RFA98f6S-irMZC)HcrCn@T-cuA7Vf;=D|_w
zZ=)}?r^Hg0@oMMoe&d77iy=Eq?!4qWUASte<5VsrH{sV;z8Grg-10E3Finxwhwla)
zfWP#i3o+xCP(MhOIJ4t)A;O7IAyj*EoKLIIp2Xky;X?z;4?B2@Ye%20D#L^*_v#Xl
zpOwEp*O0=~&gp8j0VAGd#hdRWSSt@;Xt
zCe}ZI4FrXV@qQZA)O8)iG00;`KJWU^`(B1sw>v2*Uag|0JFV*$rK0S-%md~#?vGQw
zB;V&GG7K)?`~~!R1%xh&*UQnR}@vS1pE3w=dAdH;lWsW#7j@
zI;g9VST+neWzcdKV2dU)*@AeLi%+^34R9wI!5YXd5)=P2jIa3-Lf0}AZx=3_Qtc9e
zfmGh&wnY1wBF2W~GX@EP$j!f9ry<*pYf*(ue6yxa|6xl#&dHe#SGn}k4-L?GQyL&eNK^MD1JAb&E&hIX08v0#vu333uiQ2UMIoCvOg-+NT(DGSo@~sM=&z
zK7R5fb5YIT9jm{9WMS;60