-
Notifications
You must be signed in to change notification settings - Fork 256
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4115 from cisagov/feature/mcet-366
Feature/mcet 366
- Loading branch information
Showing
12 changed files
with
341 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
117 changes: 117 additions & 0 deletions
117
CSETWebNg/src/app/reports/physical-summary/physical-summary.component.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,117 @@ | ||
<!---------------------- | ||
Copyright 2024 Battelle Energy Alliance, LLC | ||
Permission is hereby granted, free of charge, to any person obtaining a copy | ||
of this software and associated documentation files (the "Software"), to deal | ||
in the Software without restriction, including without limitation the rights | ||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
copies of the Software, and to permit persons to whom the Software is | ||
furnished to do so, subject to the following conditions: | ||
The above copyright notice and this permission notice shall be included in all | ||
copies or substantial portions of the Software. | ||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
SOFTWARE. | ||
--------------------------> | ||
<div class="report-body mb-5" *transloco="let t"> | ||
|
||
<div class="flex-container"> | ||
<div class="column mt-3"> | ||
<p class="report-title"> | ||
VULNERABILITIES AND OPTIONS FOR CONSIDERATION | ||
</p> | ||
</div> | ||
<div class="column"> | ||
<p style="text-align: center"> | ||
<img width="471" height="529" alt="cset" src="assets/images/SiteSummaryFiles/image002.jpg"> | ||
</p> | ||
</div> | ||
|
||
<div class="cover-page-bottom mb-4"> | ||
<app-logo-for-reports></app-logo-for-reports> | ||
<app-info-block [response]="response" /> | ||
</div> | ||
</div> | ||
|
||
|
||
|
||
<div class="page-break" *ngIf="configSvc.behaviors.showDisclaimer"> | ||
<p> | ||
During the assessment process, personnel conducting the assessment along with facility stakeholders identified potential vulnerabilities along with suggested options for consideration. The process and listed options for consideration provide an opportunity for the facility owners/operators (stakeholders) to mitigate vulnerabilities, increase resilience, and implement protective measures. This process involves an assessment of risk tailored to the facility that takes into consideration the threat, assets to be protected, facility characteristics and capital expenditures planning. The options for consideration are not prescriptive endorsements of specific protective measures to be installed and/or used at the facility. The critical infrastructure owner or operator determines for the facility whether the options for consideration provide the desired enhancements in light of the facility’s current security and resilience posture, anticipated growth or organizational changes, budgetary outlook, etc. No assessment process or respective options for consideration have the ability to provide solutions which fully eliminate the possibility of undesirable events or associated outcomes. | ||
</p> | ||
<app-report-disclaimer></app-report-disclaimer> | ||
</div> | ||
|
||
<div class="page-break"> | ||
<app-report-advisory></app-report-advisory> | ||
</div> | ||
|
||
|
||
|
||
<div class="page-break"> | ||
<h1>{{t('reports.site information')}}</h1> | ||
<app-site-information [response]="response"></app-site-information> | ||
</div> | ||
|
||
<div class="page-break" *ngIf="response?.information.useStandard"> | ||
<h1> | ||
Vulnerabilities and Options For Consideration | ||
</h1> | ||
|
||
<p> | ||
During the assessment process, personnel conducting the assessment along with facility stakeholders identified potential vulnerabilities | ||
along with suggested options for consideration. The process and listed options for consideration provide an opportunity for the facility | ||
owners/operators (stakeholders) to mitigate vulnerabilities, increase resilience, and implement protective measures. This process involves | ||
an assessment of risk tailored to the facility that takes into consideration the threat, assets to be protected, facility characteristics | ||
and capital expenditures planning. The options for consideration are <u>not prescriptive endorsements</u> of specific protective measures to be | ||
installed and/or used at the facility. The <u>critical infrastructure owner or operator</u> determines for the facility whether the options for | ||
consideration provide the desired enhancements in light of the facility’s current security and resilience posture, anticipated growth or | ||
organizational changes, budgetary outlook, etc. No assessment process or respective options for consideration have the ability to provide | ||
solutions which fully eliminate the possibility of undesirable events or associated outcomes. | ||
</p> | ||
|
||
<table *ngFor="let rq of response?.questionsWithSupplementals" class="cset-table-3"> | ||
<tr> | ||
<th style="width: 15%">{{t('reports.core.rank')}}: {{rq.rank}}</th> | ||
<th>{{rq.categoryAndNumber}}</th> | ||
<th style="width: 15%">{{t('reports.core.level')}}: {{t('titles.sal.level.' + rq.level.toLowerCase())}}</th> | ||
</tr> | ||
<tr> | ||
<td colspan="2" [innerHTML]="rq.question"></td> | ||
<td class="tint2">{{t('answer-options.labels.' + rq.answer.toLowerCase())}}</td> | ||
</tr> | ||
<tr> | ||
<td colspan="3" [innerHTML]="rq.supplemental"></td> | ||
</tr> | ||
<tr> | ||
<td class="tint2">{{t('reports.core.questions comments.comment')}}:</td> | ||
<td colspan="2" [innerHTML]="reportSvc.formatLinebreaks(rq.comment)"></td> | ||
</tr> | ||
</table> | ||
</div> | ||
|
||
|
||
|
||
<div class="page-break"> | ||
<app-question-comments [data]="response"></app-question-comments> | ||
</div> | ||
|
||
|
||
|
||
<div class="page-break"> | ||
<app-alt-justification-comments [data]="this.response"></app-alt-justification-comments> | ||
</div> | ||
|
||
|
||
<div class="page-break"> | ||
<app-questions-marked-for-review [data]="response"></app-questions-marked-for-review> | ||
</div> | ||
|
||
</div> |
Oops, something went wrong.