White Paper

Buy versus build: A faster, lower-risk path to implementing your program’s ATO technical controls

Issue link: https://read.uberflip.com/i/1545918

Contents of this Issue

Navigation

Page 2 of 3

WHITE PAPER Buy vs. Build: A Faster Path to ATO mrcy.com 3 WHERE RELIANCEONE CONCENTRATES ITS VALUE: THE 49 TECHNICAL CONTROLS Technical controls are where custom kernel work, hand-built access-control policy, encryption integration, and maintenance traditionally consume the most engineering time. RelianceOne addresses 46 of these 49 controls (94%), spanning 14 of the 20 NIST SP 800-53 control families — including Access Control, Configuration Management, System and Communications Protection, System and Information Integrity, and Supply Chain Risk Management. Rating Count What it means Strong fit 20 Directly and fully implements the control's technical intent out of the box. Exceeds the control 12 Satisfies the control's purpose through a more rigorous mechanism than the literal text requires — for example, cr yptographic hardware-binding in place of an anti-counter feit inspection policy. Partial fit 14 Provides a meaningful technical contribution; remaining procedural or OS-identity elements complete the control. Not addressed 3 Out of software scope by design — e.g., physical TEMPEST shielding, screen banners, auto-locking upon inactivity. BUILT TO FIT INSIDE YOUR EXISTING PROGRAM RelianceOne installs on the RHEL and STIG-compatible baselines your team already runs — there is no fork, no custom operating system, and no rebuilt tool chain to maintain. It works alongside the security tools you already use, including SELinux, rather than replacing them. Programs interact with their operating environment the way they do today; RelianceOne adds protection and survivability underneath, not a new layer your team has to relearn. ▪ No custom OS or kernel to maintain — drop-in deployment on RHEL, binary-compatible distributions, and embedded Linux builds ▪ Works with, not around, SELinux and existing STIG hardening guidance ▪ Every mapped control comes with a ready-to-use implementation narrative your ISSM can tailor directly into the System Security Plan — turning a blank-page writing exercise into a review-and-tailor exercise ARTIFACTS THAT STRENGTHEN YOUR ASSESSMENT PACKAGE RelianceOne is delivered with supporting evidence your program's body of evidence can build on directly, rather than create from a blank page: ▪ Threat models documenting the assumptions and attack paths the product is designed against — useful input to your own system- level threat model and risk assessment ▪ Test plans and test evidence demonstrating that the protections function as claimed, available to support your assessor and authorizing official's review ▪ Configuration and evaluation documentation showing how the product was itself assessed by DoW evaluation teams Your team still tailors these artifacts to your system's specific mission and threat model, but tailoring a vetted starting point is a fundamentally different and faster exercise than originating one. RelianceOne covers 46 controls your engineering team doesn't have to design, implement, test, and maintain from scratch — all addressed by a single, pre- evaluated product instead of months of bespoke development.

Articles in this issue

Links on this page

view archives of White Paper - Buy versus build: A faster, lower-risk path to implementing your program’s ATO technical controls