Mission and owner requirements
Clarify intended use, stakeholders, applicable authorities, constraints, and decision rights.
SECURE-FACILITY LIFECYCLE INTEGRATION
Owner-side and program-team support across the secure-facility lifecycle.
Bedrock supports Government program offices, prime contractors, and delivery teams across SCIF and SAPF planning, acquisition, design, construction security, accreditation preparation, turnover, operation, and change.
WHERE BEDROCK FITS
Bedrock works at the decisions and handoffs that connect security requirements to delivery.
Risk concentrates at interfaces among the Government owner, security office, contracting team, designer, constructor, systems integrators, and accrediting authority. Bedrock helps make requirements, decisions, open conditions, responsibilities, and supporting records visible at those interfaces.
Owner-side describes whom Bedrock advises. It does not confer contracting, design, construction, acceptance, SSM, AO, SAO, CTTA, or RMF authorization authority.
LIFECYCLE SUPPORT
Site and acquisition considerations
Identify security conditions and interfaces that must be reflected in scope, procurement, schedule, and risk.
Design development
Review security requirements at program-defined design milestones and track comments through disposition.
Pre-construction preparation
For SCIF work, support Construction Security Plan development and quality review under the designated Site Security Manager and Accrediting Official process. For SAPF work, follow the applicable SAP accrediting official's direction.
Construction-security execution
Coordinate security-relevant submittals, RFIs, changes, designated observations, hold points, issues, and corrective actions.
Testing and supporting records
Track applicable inspection, test, acceptance, as-built, waiver, deviation, and corrective-action records.
Accreditation preparation
Organize current documentation and open conditions for customer submission through the designated security office and review by the applicable authority.
Turnover and controlled change
Preserve the configuration, decision, issue, and operating record needed for later modification, periodic review, reaccreditation when directed, and closure.
WORK PRODUCTS
The contract defines the records Bedrock prepares and who uses them.
- Authority and stakeholder map
- Requirements traceability matrix
- Interface register
- Decision log
- Risk, issue, and action register
- Design-comment and resolution log
- Submittal and RFI status
- Change and open-condition log
- Accreditation documentation register
- Turnover and configuration record
SPECIALTY COORDINATION
Coordination does not transfer another party's authority.
Bedrock can coordinate facility dependencies with RMF, electronic security systems, facility-related control-system cybersecurity, TEMPEST, commissioning, and other specialist workstreams when included in scope.
The appointed CTTA evaluates TEMPEST conditions and recommends countermeasures. Licensed designers retain design responsibility. Constructors and installers retain execution responsibility. Government authorities retain approval and accreditation decisions.
FREQUENTLY ASKED QUESTIONS
Questions Bedrock addresses before scope or award.
Does Bedrock accredit SCIFs or SAPFs?
No. The SCIF Accrediting Official, or the applicable SAP accrediting official for SAPF work, makes the decision. Bedrock supports security integration, readiness review, and accreditation-supporting documentation within the assigned scope.
Can Bedrock serve as the Site Security Manager?
Only when a qualified Bedrock individual is formally designated for that role. Otherwise Bedrock supports the designated SSM and the program team.
Does Bedrock make TEMPEST determinations?
Bedrock coordinates the TEMPEST Addendum and TCR process and helps implement resulting actions. The appointed CTTA evaluates the project and recommends countermeasures to the applicable authority.
DEFINE THE INTERFACE